n-paladi's profile - activity

2017-06-05 04:17:50 -0600 received badge  Good Question (source)
2014-07-31 15:22:13 -0600 received badge  Commentator
2013-12-30 09:34:35 -0600 received badge  Famous Question (source)
2013-12-18 06:56:10 -0600 received badge  Enthusiast
2013-12-17 06:34:15 -0600 commented question How can i inject a file into windows instance in openstack?
2013-12-09 18:43:47 -0600 received badge  Famous Question (source)
2013-12-07 23:59:04 -0600 received badge  Taxonomist
2013-10-29 10:07:51 -0600 answered a question How can i inject a file into windows instance in openstack?

is it possible to inject files without the metadata service? Like, directly from Nova (i'm working on some own extensions here..)

Thanks, /Nico

2013-10-23 11:40:16 -0600 received badge  Notable Question (source)
2013-10-23 11:40:16 -0600 received badge  Popular Question (source)
2013-10-22 07:28:57 -0600 received badge  Notable Question (source)
2013-10-12 02:22:50 -0600 received badge  Popular Question (source)
2013-10-11 18:05:01 -0600 received badge  Nice Question (source)
2013-10-08 02:03:24 -0600 answered a question How to connect to windows VM ?

If you are using the installer from CloudBase ( http://www.cloudbase.it/cloud-init-for-windows-instances/ ) then you can configure user data (such as password) to be inserted at boot time.

2013-10-07 22:20:28 -0600 received badge  Good Answer (source)
2013-10-07 10:12:09 -0600 commented question Windows instance can not reach metadata?

they are Win 7 and Win Server 2012

2013-10-07 09:57:15 -0600 asked a question Windows instance can not reach metadata?

I am using a CentOS-based OpenStack deployment and am running both Linux and Windows instances. I've used the installer from CloudBase for the Windows instances (Win 7 and Win Server 2012).

However, when booting up, the windows instances can not reach the metadata (identical log as specified by user "George", December 19, 2012 at 7:21 on http://www.cloudbase.it/cloud-init-for-windows-instances/ )

Important to note is that the linux test instances DO get access to the metadata in the same deployment.

2013-09-18 10:08:37 -0600 commented question no ssh or ping to instance and vnc console shows wget: can't connect to remote host (169.254.169.254): No route to host

This seems like an issue for many people so I've filed a bug: https://bugs.launchpad.net/neutron/+bug/1226651

2013-09-18 10:07:55 -0600 commented question no ssh or ping to instance and vnc console shows wget: can't connect to remote host (169.254.169.254): No route to host

'provider:network_type': u'vlan', 'router:external': False, 'shared': False, 'id': u'409c22e7-d1ca-46d2-ad49-6e26f26d0286', 'provider:segmentation_id': 401L}

2013-09-18 10:07:49 -0600 commented question no ssh or ping to instance and vnc console shows wget: can't connect to remote host (169.254.169.254): No route to host

2013-09-17 16:50:58 WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'792aa923-a38a-4918-a108-bff0ec11f6f5'], 'name': u'fe_net01', 'provider:physical_network': u'physnet2', 'admin_state_up': True, 'tenant_id': u'8e6aa410c7e9464fa4d32b14f77f9571',

2013-09-18 10:07:14 -0600 commented question no ssh or ping to instance and vnc console shows wget: can't connect to remote host (169.254.169.254): No route to host

Hi, do you get any warnings in the quantum log? I have a very similar problem and also get the following warning when launching the instance:

2013-09-18 08:17:03 -0600 commented answer unable to ping my instance after creating it

Hi, the link you posted ( https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/ch11s02.html) is "11.2. Disabling vhost-net", how does this clarify the iptables change, or am i missing something?

2013-09-05 03:32:47 -0600 received badge  Scholar (source)
2013-09-04 12:18:13 -0600 received badge  Student (source)
2013-09-04 08:21:13 -0600 asked a question Resource not found when calling quantum net-gateway-list

Hello,

I am using quantum on CentOS 6.4 installed via packstack.

I have configured a network, router and subnets with quantum. However, when calling quantum-net-gateway-list I get: 404 Not Found // The resource could not be found. Is this a bug or a misconfiguration?

Thanks, /Nicolae

2013-08-05 07:20:34 -0600 commented question Vlan Network Create Fails With Unknown Error

I had a similar issue but it seems to have disappeared when I restarted nova-compute and nova-network (and ensured they work properly)

2013-07-09 03:31:44 -0600 answered a question 401 on "glance image-list"

FYI

I had a similar issue, however the value auth_host was already 127.0.0.1;

Changing this to the host's public IP solved the issue and it kept working after changing the value back to 127.0.0.1.

2013-07-06 18:57:45 -0600 received badge  Nice Answer (source)
2013-07-05 12:03:31 -0600 received badge  Teacher (source)
2013-07-05 10:25:35 -0600 received badge  Editor (source)
2013-07-05 10:24:59 -0600 answered a question How to solve broken dependencies for Swift RPM packages?

As mentioned in the comment, had the exact same issue when following the http://docs.openstack.org/trunk/openstack-compute/install/yum/content/install-keystone.html (installation guide) on a CentOS 6.4

Adding the epel repository solved the issue:

  • Download the latest epel-release rpm from:

http://dl.fedoraproject.org/pub/epel/6/i386/

  • Install epel-release rpm:

rpm -Uvh epel-release*rpm

The http://docs.openstack.org/trunk/openstack-compute/install/yum/content/install-keystone.html (installation guide) should be updated imo

2013-07-05 10:10:43 -0600 commented question How to solve broken dependencies for Swift RPM packages?

have the exactly same issue here on fresh install of CentOS 6.4

2013-07-05 10:10:09 -0600 received badge  Supporter (source)
2012-11-13 10:45:32 -0600 answered a question "glance index" returns "Invalid OpenStack Identity credentials."

I have had a similar issue and tried to nail it down, but after some attempts gave up and made a fresh deployment, which solved the problem.