[Openstack] [OpenStack][Neutron] Creation of the qr interface fails sometimes

[Balamurugan V G]

Hi,

I have a 3 nodes Grizzly setup with one Controller, Network and
Compute(KVM) node. I am using VLAN mode. It works fine most of the time.
But occasionally when an instance is launched, the instance is unable to
reach the external network. When this happens I see that the 'qr-x'
interface is not created as shown below:

root@openstack-dev-network# ip netns exec
qrouter-81c474cb-acad-42b4-bc78-875992fa33f6 route -n

Kernel IP routing table

Destination Gateway Genmask Flags Metric RefUse
Iface

0.0.0.0 10.5.60.1   0.0.0.0 UG0  00
qg-81e2a77d-71

1.1.1.0 0.0.0.0 255.255.252.0   U 0  00
qg-81e2a77d-71

root@openstack-dev-network #

I see the following error in /var/log/quantum/openvswitch-agent.log

Stderr: 'ovs-vsctl: no row "qr-fb582b82-f7" in table Interface\n'

2013-07-29 06:14:18ERROR [quantum.agent.linux.ovs_lib] Unable to
execute ['ovs-vsctl', '--timeout=2', 'get', 'Interface', 'qr-a4f24e08-aa',
'external_ids']. Exception:

Command: ['sudo', '/usr/bin/quantum-rootwrap',
'/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'get',
'Interface', 'qr-a4f24e08-aa', 'external_ids']

Exit code: 1

Stdout: ''

Stderr: 'ovs-vsctl: no row "qr-a4f24e08-aa" in table Interface\n'


And on restarting the quantum services, the interface gets created and the
instance is able to reach the external network.


root@openstack-dev-network:~# cd /etc/init.d/; for i in $( ls quantum-* );
do sudo service $i restart; done
quantum-dhcp-agent stop/waiting
quantum-dhcp-agent start/running, process 20872
quantum-l3-agent stop/waiting
quantum-l3-agent start/running, process 20885
quantum-metadata-agent stop/waiting
quantum-metadata-agent start/running, process 20894
quantum-plugin-openvswitch-agent stop/waiting
quantum-plugin-openvswitch-agent start/running, process 20903
root@openstack-dev-network:/etc/init.d#


root@openstack-dev-network# ip netns exec
qrouter-81c474cb-acad-42b4-bc78-875992fa33f6 route -n

Kernel IP routing table

Destination Gateway Genmask Flags Metric RefUse
Iface

0.0.0.0 10.5.60.1   0.0.0.0 UG0  00
qg-81e2a77d-71

1.1.1.0 0.0.0.0 255.255.252.0   U 0  00
qg-81e2a77d-71

192.168.3.0 0.0.0.0 255.255.255.0   U 0  00
qr-a4f24e08-aa

root@openstack-dev-network #



I do have the root_helper in
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini.


Any help will be greatly appreciated.


Regards,

Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack][Neutron] Cleanup of network namespaces not happening

[Balamurugan V G]

Hi,

I have a 3 nodes Grizzly 2013.1.1 setup and I see that the network
namespaces are not getting deleted even after the networks/subnets are
deleted. When I run 'quantum-netns-cleanup', I get the following error:

root@openstack-dev-network:~# quantum-netns-cleanup
2013-07-25 12:51:25 CRITICAL [quantum]
Command: ['sudo', 'ip', 'netns', 'exec',
'qdhcp-b9c30f80-8643-4a20-b43c-1f3d861eea63', 'ip', '-o', 'link', 'list']
Exit code: 1
Stdout: ''
Stderr: 'seting the network namespace failed: Invalid argument\n'
root@openstack-dev-network:~#

I see that there are number of bugs reports on this issue but non seem to
have been addressed. For example, the ones at:

https://bugs.launchpad.net/neutron/+bug/1052535
https://bugzilla.redhat.com/show_bug.cgi?id=972689

I tried the patch in the first bug above and also added root_helper in
/etc/quantum/dhcp_agent.ini but to no luck.

Has anyone got this issues fixed?

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] custom url for openstack dashboard

[Balamurugan V G]

You can try Apache's mod rewrite and do URL rewrites as desired.

Regards,
Balu


On Fri, Jun 21, 2013 at 1:05 PM, Anshul Gangwar  wrote:
> I want to give custom url for openstack dashboard, say
>
> http://10.1.1.1/os
>
> How can I acheive this?
>
> Thanks,
> Anshul
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Issues with openvswitch agent on Quantum/network node

[Balamurugan V G]

Run a ping in your VM to its network gateway and do the following:

root@openstack-network:~# quantum router-list
+--+--++
| id   | name |
external_gateway_info  |
+--+--++
| 2abf6d6d-b2ac-4fad-99e5-ebf96e1ce167 | auto_router_1 |
{"network_id": "d7d40dba-6d14-4ba5-89dd-972fde4361ab"} |
+--+--++
root@openstack-network:~# ip netns exec
qrouter-2abf6d6d-b2ac-4fad-99e5-ebf96e1ce167 route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 1.1.1.1   0.0.0.0 UG0  00
qg-ec4cd5f1-e6
1.1.1.0   0.0.0.0 255.255.255.0   U 0  00
qg-ec4cd5f1-e6
2.2.2.0 0.0.0.0 255.255.255.0   U 0  00
qr-272f8aec-37
root@openstack-network:~# ip netns exec
qrouter-2abf6d6d-b2ac-4fad-99e5-ebf96e1ce167 tcpdump -i qr-272f8aec-37
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on qr-272f8aec-37, link-type EN10MB (Ethernet), capture size
65535 bytes
^C18:44:26.406660 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008,
seq 56, length 64
18:44:26.406692 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
56, length 64
18:44:27.406690 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
57, length 64
18:44:27.406724 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
57, length 64
18:44:28.406695 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
58, length 64
18:44:28.406721 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
58, length 64
18:44:29.406683 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
59, length 64
18:44:29.406716 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
59, length 64
18:44:30.406668 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
60, length 64
18:44:30.406690 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
60, length 64
18:44:31.40 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
61, length 64
18:44:31.406701 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
61, length 64
18:44:32.406688 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
62, length 64
18:44:32.406709 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
62, length 64
18:44:32.461101 IP 2.2.2.4.627 > 10.203.15.14.31995: UDP, length 100
18:44:33.406671 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
63, length 64
18:44:33.406704 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
63, length 64
18:44:34.40 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
64, length 64
18:44:34.406692 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
64, length 64
18:44:35.406674 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
65, length 64
18:44:35.406708 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
65, length 64
18:44:36.406687 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
66, length 64
18:44:36.406719 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
66, length 64
18:44:37.406672 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
67, length 64
18:44:37.406698 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
67, length 64
18:44:38.406669 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
68, length 64
18:44:38.406695 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
68, length 64
18:44:39.406712 IP 2.2.2.4 > 2.2.2.1: ICMP echo request, id 38008, seq
69, length 64
18:44:39.406747 IP 2.2.2.1 > 2.2.2.4: ICMP echo reply, id 38008, seq
69, length 64

29 packets captured
29 packets received by filter
0 packets dropped by kernel
root@openstack-network:~#

2.2.2.0/24 is my VM's network.

You should see that the packets are reaching the the network node from
the compute node where your VM is running. This might help to narrow
down.

Hope this helps. I do not know of any tools as such except general
linux commands to debug the issues.

Regards,
Balu



On Thu, Jun 20, 2013 at 6:36 PM, Sreerekha Shenoy (sresheno)
 wrote:
> Hi,
>
> It’s been a week since we are stuck in getting this setup working
>
> Any pointers on tools / document to move further would be really
> appreciated.
>
>
>
> (currently we are lagging in getting our hands onto tools that can help
> tracing the packets inside OVS to and from VMs….)
>
>
>
> Thanks,
>
> Best Regards,
>
> Rekha
>
>
>
> From: Sreerekha Shenoy (sresheno)
> Sent: Thursday, June 20, 2013 6:19 PM
> To: openstack@lists.launchpad.net
> Subject: RE: Issues with openvswitch agent on Quantum/network node
>
>
>
> Hi,
>
> What are the good to know tools and networking concepts for me to be able to
> debug connectivity issues inside Openstack VLAN mode 

Re: [Openstack] Download a specific image from Glance to local hard drive

[Balamurugan V G]

Those are your complete/actual image files. They are named by the
UUIDs they use. You can copy these and rename to appropriate name with
the suitable extension, .img or .qcow2 etc depending on what format
they actually are.

Regards,
Balu

On Thu, Jun 20, 2013 at 5:17 PM, Narayanan, Krishnaprasad
 wrote:
> Hi,
>
> If I get it correctly, the folder /var/lib/glance/images has only the UUID 
> inside it. Where will I able to see the complete image (.img or .tar.gz)?
>
> Thanks
> Krishnaprasad
>
> -Original Message-
> From: Sylvain Bauza [mailto:sylvain.ba...@digimind.com]
> Sent: Donnerstag, 20. Juni 2013 12:53
> To: Michael Still
> Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
> Subject: Re: [Openstack] Download a specific image from Glance to local hard 
> drive
>
> Hi,
>
> While I was working on Essex, I was simply looking at the image UUID and 
> copying it from /var/lib/glance/images, that's it.
>
> I was not aware of glance image-download, which is great (same command for 
> all Glance backends).
>
> -Sylvain
>
> Le 20/06/2013 11:53, Michael Still a écrit :
>> I'm not sure. Essex is very old now. Try running "glance help" and see
>> what happens?
>>
>> Michael
>>
>> On Thu, Jun 20, 2013 at 7:49 PM, Narayanan, Krishnaprasad
>>  wrote:
>>> Hi Michael,
>>>
>>> Is this command valid in OpenStack ESSEX?
>>>
>>> Thanks
>>> Krishnaprasad
>>>
>>> -Original Message-
>>> From: mikalst...@gmail.com [mailto:mikalst...@gmail.com] On Behalf Of
>>> Michael Still
>>> Sent: Donnerstag, 20. Juni 2013 11:46
>>> To: Narayanan, Krishnaprasad
>>> Cc: openstack@lists.launchpad.net
>>> Subject: Re: [Openstack] Download a specific image from Glance to
>>> local hard drive
>>>
>>> On Thu, Jun 20, 2013 at 7:33 PM, Narayanan, Krishnaprasad 
>>>  wrote:
 Hallo All,

 I am using OpenStack ESSEX and want to download an image from glance
 to my local hard drive. Can I get to know any commands in glance (in
 ESSEX) using which I can perform this operation?
>>> Take a look at the image-download command to the glance command line client.
>>>
>>> Cheers,
>>> Michael
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] SWIFT Object Store spanning multiple data centers

[Balamurugan V G]

Thanks John for the quick response and update.

I followed the guide at
http://docs.openstack.org/grizzly/openstack-compute/install/apt/content/ch_installing-openstack-object-storage.html
and I am using Grizzly on Ubuntu 12.04LTS. Two replicas in A and one
replica in B is what I intended so looks like that's working as
intended.

I dont think I am using separate replication network feature. I'll
explore that. I have a 20meg link between the DCs and I see the usage
go up to 8meg only(not sure if this answers your question on latency).

I even tried to manually copy the image file(the object which was
stored in SWIFT) using rsync(not rsyncd as used by SWIFT) and it
copied the 5Gb file in under 15mins with no issues. So I guess this
rules out any network issue.

Regards,
Balu

On Mon, Jun 17, 2013 at 10:39 AM, John Dickinson  wrote:
> The global clusters feature is Swift is very new and just now being finished 
> up. We are finishing up the last part of it and will have it completed in our 
> next release (tentatively scheduled for June 27). The last part is the 
> affinity write (ie don't write to a WAN region).
>
> The regions concept is exactly as you have described it: use it for separate 
> DCs. With 3 replicas, you'll have 2 replicas in one DC and one in the other. 
> In your case, because of the way you have configured zones, it looks like 
> you'll always have 2 replicas in A and one in B. Note that this is not a 
> requirement of the system: you should set up your zones to match your failure 
> domains.
>
> Are you using the separate replication network feature (it's not required, 
> but it may allow you some more control over the cross-DC replication)?
>
> What is the latency between your DCs?
>
> --John
>
>
>
> On Jun 16, 2013, at 9:58 PM, Balamurugan V G  wrote:
>
>> Hi,
>>
>> I am exploring setting up a SWIFT Object Store across two data
>> centers. Lets say I have DC-A and DC-B. I have setup a swift-proxy and
>> two swift-storage nodes in DC-A. And I have setup one storage node in
>> DC-B. This is just an experimental setup and if this works well, will
>> have more storage nodes and proxy nodes in each DC. I have added the
>> storage nodes in DC-A in Zone1 and Zone2. And storage nodes in DC-B is
>> in Zone3. The replication count has been set to 3. My goal is to setup
>> a multi site OpenStack and I am exploring using SWIFT to store the
>> images such that the images can be shared across the DCs.
>>
>> Here are my questions:
>>
>>   1. There seems to be a concept of regions. How do I use that with
>> SWIFT in this case. I cant find any good documentation on it.
>>   2. In my current setup explained above, I can see that the
>> partitions are getting copied(and synced) fine between the nodes in
>> DC-A as confirmed by the used size returned by 'df -h /srv/node/sdb1'
>> (I know its crube but its good enough). I see that the node in DC-B
>> behaves differently. I see that the partitions are copied to this node
>> and then removed again continuously. It never settles. That is for
>> example, if I have a 5G content stored in the system, the DC-A nodes
>> shows that 5Gb is used. But the DC-B node shows that it increases to
>> 5Gb and it then drops again to say 2Gb and then again increases to 5gb
>> and then drop again and so forth.The rsyncd logs shows few errors as
>> shown below:
>>
>> 2013/06/17 04:38:54 [6965] receiving file list
>> 2013/06/17 04:53:52 [6963] rsync: connection unexpectedly closed
>> (731405377 bytes received so far) [receiver]
>> 2013/06/17 04:53:52 [6963] rsync error: error in rsync protocol data
>> stream (code 12) at io.c(605) [receiver=3.0.9]
>> 2013/06/17 04:53:52 [6963] rsync: connection unexpectedly closed (87
>> bytes received so far) [generator]
>> 2013/06/17 04:53:52 [6963] rsync error: error in rsync protocol data
>> stream (code 12) at io.c(605) [generator=3.0.9]
>> 2013/06/17 04:53:54 [6965] rsync: connection unexpectedly closed
>> (716563202 bytes received so far) [receiver]
>> 2013/06/17 04:53:54 [6965] rsync error: error in rsync protocol data
>> stream (code 12) at io.c(605) [receiver=3.0.9]
>> 2013/06/17 04:53:54 [6965] rsync: connection unexpectedly closed (87
>> bytes received so far) [generator]
>> 2013/06/17 04:53:54 [6965] rsync error: error in rsync protocol data
>> stream (code 12) at io.c(605) [generator=3.0.9]
>> 2013/06/16 21:54:24 [6996] name lookup failed for 10.5.64.47:
>> Temporary failure in name resolution
>> 2013/06/16 21:54:24 [6996] connect from UNKNOWN (10.5.64.47)
>> 2013/06/16 21:54:24 [6997] name lookup failed for 10.5.64.48:
>> Tempor

[Openstack] [OpenStack] SWIFT Object Store spanning multiple data centers

[Balamurugan V G]

Hi,

I am exploring setting up a SWIFT Object Store across two data
centers. Lets say I have DC-A and DC-B. I have setup a swift-proxy and
two swift-storage nodes in DC-A. And I have setup one storage node in
DC-B. This is just an experimental setup and if this works well, will
have more storage nodes and proxy nodes in each DC. I have added the
storage nodes in DC-A in Zone1 and Zone2. And storage nodes in DC-B is
in Zone3. The replication count has been set to 3. My goal is to setup
a multi site OpenStack and I am exploring using SWIFT to store the
images such that the images can be shared across the DCs.

Here are my questions:

   1. There seems to be a concept of regions. How do I use that with
SWIFT in this case. I cant find any good documentation on it.
   2. In my current setup explained above, I can see that the
partitions are getting copied(and synced) fine between the nodes in
DC-A as confirmed by the used size returned by 'df -h /srv/node/sdb1'
(I know its crube but its good enough). I see that the node in DC-B
behaves differently. I see that the partitions are copied to this node
and then removed again continuously. It never settles. That is for
example, if I have a 5G content stored in the system, the DC-A nodes
shows that 5Gb is used. But the DC-B node shows that it increases to
5Gb and it then drops again to say 2Gb and then again increases to 5gb
and then drop again and so forth.The rsyncd logs shows few errors as
shown below:

2013/06/17 04:38:54 [6965] receiving file list
2013/06/17 04:53:52 [6963] rsync: connection unexpectedly closed
(731405377 bytes received so far) [receiver]
2013/06/17 04:53:52 [6963] rsync error: error in rsync protocol data
stream (code 12) at io.c(605) [receiver=3.0.9]
2013/06/17 04:53:52 [6963] rsync: connection unexpectedly closed (87
bytes received so far) [generator]
2013/06/17 04:53:52 [6963] rsync error: error in rsync protocol data
stream (code 12) at io.c(605) [generator=3.0.9]
2013/06/17 04:53:54 [6965] rsync: connection unexpectedly closed
(716563202 bytes received so far) [receiver]
2013/06/17 04:53:54 [6965] rsync error: error in rsync protocol data
stream (code 12) at io.c(605) [receiver=3.0.9]
2013/06/17 04:53:54 [6965] rsync: connection unexpectedly closed (87
bytes received so far) [generator]
2013/06/17 04:53:54 [6965] rsync error: error in rsync protocol data
stream (code 12) at io.c(605) [generator=3.0.9]
2013/06/16 21:54:24 [6996] name lookup failed for 10.5.64.47:
Temporary failure in name resolution
2013/06/16 21:54:24 [6996] connect from UNKNOWN (10.5.64.47)
2013/06/16 21:54:24 [6997] name lookup failed for 10.5.64.48:
Temporary failure in name resolution
2013/06/16 21:54:24 [6997] connect from UNKNOWN (10.5.64.48)
2013/06/17 04:54:25 [6996] rsync to object/sdb1/objects/189659 from
UNKNOWN (10.5.64.47)
2013/06/17 04:54:25 [6996] receiving file list
2013/06/17 04:54:25 [6997] rsync to object/sdb1/objects/189659 from
UNKNOWN (10.5.64.48)
2013/06/17 04:54:25 [6997] receiving file list

I even tried to increase the timeout value of rsync from default
30sec to 600 sec but I still see the same issue. What could be wrong
here?


Any help will be greatly appreciated. Also any pointers to good
documentation on how to setup a multi site OpenStack deployment will
be very helpful. I see that there is good documentation to getup and
runing with a single or 3 nodes OpenStack setup, there is not much to
know how to deploy a large scale multi site OpenStack deployment :-(

Regards,
Balu

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] JSON Naming convention

[Balamurugan V G]

Yes I meant the future versions of the APIs.

Regards,
Balu

On Tue, May 28, 2013 at 5:32 PM, Joe Gordon  wrote:
> We cannot go back and change past APIs, but standardization would be nice
> for future APIs such as nova V3.
>
>
> On Fri, May 17, 2013 at 1:20 PM, Balamurugan V G 
> wrote:
>>
>> Hi,
>>
>> I see that the REST API using both the camelCase and underscore separated
>> names for the JSON attributes. An example is below:
>>
>>
>> curl  -X 'POST' http://1.1.1.1:5000/v2.0/tokens -d
>> '{"auth":{"passwordCredentials":{"username": "admin",
>> "password":"admin_pass"}, "tenantName":"test"}}' -H 'Content-type:
>> application/json'
>> {"access": {"token": {"expires": "2013-05-18T06:10:07Z", "id":
>> "d92aebd5112f44b9b13dfabbf4283110", "tenant": {"enabled": true,
>> "description": null, "name": "automation", "id":
>> "4a8c3029619e4afbaa39f85fcd121003"}}, "serviceCatalog": [{"endpoints":
>> [{"adminURL": "http://2.2.2.2:8774/v2/4a8c3029619e4afbaa39f85fcd121003";,
>> "region": "RegionOne", "internalURL":
>> "http://2.2.2.2:8774/v2/4a8c3029619e4afbaa39f85fcd121003";, "id":
>> "5c3598dc6b384a598046471858b55417", "publicURL":
>> "http://1.1.1.1:8774/v2/4a8c3029619e4afbaa39f85fcd121003"}],
>> "endpoints_links": [], "type": "compute", "name": "nova"}, {"endpoints":
>> [{"adminURL": "http://2.2.2.2:9696/";, "region": "RegionOne", "internalURL":
>> "http://2.2.2.2:9696/";, "id": "18ffe92b8db242d8b39991b4dceafe6c",
>> "publicURL": "http://1.1.1.1:9696/"}], "endpoints_links": [], "type":
>> "network", "name": "quantum"}, {"endpoints": [{"adminURL":
>> "http://2.2.2.2:9292/v2";, "region": "RegionOne", "internalURL":
>> "http://2.2.2.2:9292/v2";, "id": "91bce3f20f704165bd430629a1446baf",
>> "publicURL": "http://1.1.1.1:9292/v2"}], "endpoints_links": [], "type":
>> "image", "name": "glance"}, {"endpoints": [{"adminURL":
>> "http://2.2.2.2:8776/v1/4a8c3029619e4afbaa39f85fcd121003";, "region":
>> "RegionOne", "internalURL":
>> "http://2.2.2.2:8776/v1/4a8c3029619e4afbaa39f85fcd121003";, "id":
>> "710bb818196f4f06a12f4efc4e32b47a", "publicURL":
>> "http://1.1.1.1:8776/v1/4a8c3029619e4afbaa39f85fcd121003"}],
>> "endpoints_links": [], "type": "volume", "name": "cinder"}, {"endpoints":
>> [{"adminURL": "http://2.2.2.2:8773/services/Admin";, "region": "RegionOne",
>> "internalURL": "http://2.2.2.2:8773/services/Cloud";, "id":
>> "01b49f1552dd486cba9499e567aa3774", "publicURL":
>> "http://1.1.1.1:8773/services/Cloud"}], "endpoints_links": [], "type":
>> "ec2", "name": "ec2"}, {"endpoints": [{"adminURL":
>> "http://2.2.2.2:35357/v2.0";, "region": "RegionOne", "internalURL":
>> "http://2.2.2.2:5000/v2.0";, "id": "f6305996eb8a49ff8fca9c40f1a78ae8",
>> "publicURL": "http://1.1.1.1:5000/v2.0"}], "endpoints_links": [], "type":
>> "identity", "name": "keystone"}], "user": {"username": "admin",
>> "roles_links": [], "id": "b254901420994f3895fed48073761b00", "roles":
>> [{"name": "admin"}], "name": "admin"}, "metadata": {"is_admin": 0, "roles":
>> ["55e3d24acce64b8bb29955945de47d21"]}}}
>>
>> For example, 'publicURL' and 'endpoint_links'.
>>
>> Is there any plan/blueprint to standardize on one naming convention?
>>
>> Regards,
>> Balu
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Internet access within launched instances too slow

[Balamurugan V G]

Check if you have the right DNS server settings on your VM. Sometimes
even that can slow the access.

Regards,
Balu

On Tue, May 28, 2013 at 3:31 PM, Rahul Sharma  wrote:
> Yes, I am using KVM.
>
> -Regards
> Rahul Sharma
>
>
> On Tue, May 28, 2013 at 2:49 PM, JuanFra Rodriguez Cardoso
>  wrote:
>>
>> Hi:
>>
>> Which hypervisor are you using? KVM with virtio driver?
>>
>> ---
>> JuanFra
>>
>>
>> 2013/5/28 Rahul Sharma 
>>>
>>> Hi All,
>>>
>>> I have a multinode setup of Openstack-Grizzly release with Networking
>>> node as a separate machine. I am able to successfully bring up instances and
>>> ping to google from within the instances. Everything is working fine except
>>> the speed of internet access from within the instances.
>>>
>>> When I try to "wget " or do "apt-get update", its taking a lot of
>>> time(1 hr 40 mins for apt-get update). However, if I do the same on the
>>> physical compute-nodes or on the network-node, it updates within seconds. I
>>> am not sure why the network access within the instances is so slow which on
>>> the other hand is quite fast on the hosts.
>>>
>>> Any pointers or steps to debug the issue would be really helpful. Please
>>> let me know how I can debug this scenario.
>>>
>>> Thanks and Regards
>>> Rahul Sharma
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dual network connections on hypervisor

[Balamurugan V G]

Hi Tim.

I am assuming that you are using Quantum for networking. And if you
are using Grizzly release you can do it from the Dashboard UI itself.
If not use the command like as shown below:

nova boot --image  --flavor  --nic net-id= --nic
net-id= 

Here, net1 and net2 are two different networks to which you want to
hook up your VM.

You can refer to the link
http://docs.openstack.org/trunk/openstack-network/admin/content/advanced_vm.html
for more on this.

Regards,
Balu


On Tue, May 28, 2013 at 1:19 PM, Tim Bell  wrote:
>
>
>
> I have a hypervisor running KVM with two network interfaces to two 
> independent networks.
>
>
>
> I could not find any documentation on how to configure a set up such as this 
> so the guests could also be configured with IPs on the two networks.
>
>
>
> Any pointers ?
>
>
>
> Tim
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] JSON Naming convention

[Balamurugan V G]

Hi,

I see that the REST API using both the camelCase and underscore separated
names for the JSON attributes. An example is below:


curl  -X 'POST' http://1.1.1.1:5000/v2.0/tokens -d
'{"auth":{"passwordCredentials":{"username": "admin",
"password":"admin_pass"}, "tenantName":"test"}}' -H 'Content-type:
application/json'
{"access": {"token": {"expires": "2013-05-18T06:10:07Z", "id":
"d92aebd5112f44b9b13dfabbf4283110", "tenant": {"enabled": true,
"description": null, "name": "automation", "id":
"4a8c3029619e4afbaa39f85fcd121003"}}, "serviceCatalog": [{"endpoints":
[{"adminURL": "http://2.2.2.2:8774/v2/4a8c3029619e4afbaa39f85fcd121003";,
"region": "RegionOne", "internalURL": "
http://2.2.2.2:8774/v2/4a8c3029619e4afbaa39f85fcd121003";, "id":
"5c3598dc6b384a598046471858b55417", "publicURL": "
http://1.1.1.1:8774/v2/4a8c3029619e4afbaa39f85fcd121003"}],
"endpoints_links": [], "type": "compute", "name": "nova"}, {"endpoints":
[{"adminURL": "http://2.2.2.2:9696/";, "region": "RegionOne", "internalURL":
"http://2.2.2.2:9696/";, "id": "18ffe92b8db242d8b39991b4dceafe6c",
"publicURL": "http://1.1.1.1:9696/"}], "endpoints_links": [], "type":
"network", "name": "quantum"}, {"endpoints": [{"adminURL": "
http://2.2.2.2:9292/v2";, "region": "RegionOne", "internalURL": "
http://2.2.2.2:9292/v2";, "id": "91bce3f20f704165bd430629a1446baf",
"publicURL": "http://1.1.1.1:9292/v2"}], "endpoints_links": [], "type":
"image", "name": "glance"}, {"endpoints": [{"adminURL": "
http://2.2.2.2:8776/v1/4a8c3029619e4afbaa39f85fcd121003";, "region":
"RegionOne", "internalURL": "
http://2.2.2.2:8776/v1/4a8c3029619e4afbaa39f85fcd121003";, "id":
"710bb818196f4f06a12f4efc4e32b47a", "publicURL": "
http://1.1.1.1:8776/v1/4a8c3029619e4afbaa39f85fcd121003"}],
"endpoints_links": [], "type": "volume", "name": "cinder"}, {"endpoints":
[{"adminURL": "http://2.2.2.2:8773/services/Admin";, "region": "RegionOne",
"internalURL": "http://2.2.2.2:8773/services/Cloud";, "id":
"01b49f1552dd486cba9499e567aa3774", "publicURL": "
http://1.1.1.1:8773/services/Cloud"}], "endpoints_links": [], "type":
"ec2", "name": "ec2"}, {"endpoints": [{"adminURL": "
http://2.2.2.2:35357/v2.0";, "region": "RegionOne", "internalURL": "
http://2.2.2.2:5000/v2.0";, "id": "f6305996eb8a49ff8fca9c40f1a78ae8",
"publicURL": "http://1.1.1.1:5000/v2.0"}], "endpoints_links": [], "type":
"identity", "name": "keystone"}], "user": {"username": "admin",
"roles_links": [], "id": "b254901420994f3895fed48073761b00", "roles":
[{"name": "admin"}], "name": "admin"}, "metadata": {"is_admin": 0, "roles":
["55e3d24acce64b8bb29955945de47d21"]}}}

For example, 'publicURL' and 'endpoint_links'.

Is there any plan/blueprint to standardize on one naming convention?

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] can two tenants create two identical network?

[Balamurugan V G]

I am assuming you are using Quantum for networking, in which case make sure
you have enable overlapping IPs by setting:

allow_overlapping_ips = True

in /etc/quantum/quantum.conf

You also need to enable namespaces:

use_namespaces = True

in /etc/quantum/l3_agent.ini

Regards
Balu

On Fri, May 17, 2013 at 3:22 PM, Liu Wenmao  wrote:

> Hi
>
> Suppose there are two tenants: A and B, they can create their own
> networks, but the networks are both 100.0.0.0/24, I think it is possible
> in multi-tenant scenarios since networks of different tenants are isolated,
> But in openstack, I have a network creation error, which says there is an
> existing network already.
>
> I wonder is it possible to create two identical networks for two tenant?
>
> Liu Wenmao
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

[Balamurugan V G]

Is there was way to inject in to the regular filesystem(C: drive) in
Windows7/Windows8?

Regards,
Balu


On Thu, Apr 25, 2013 at 11:46 AM, Balamurugan V G
wrote:

> Thanks for link! By running the OpenHiddenSystemDrive exe, I am able to
> see the injected file.
>
> Regards,
> Balu
>
>
> On Thu, Apr 25, 2013 at 10:30 AM, Wangpan wrote:
>
>> **
>> have you open and check the 'system reserved partition'? see the refer at
>> bellow:
>>
>> http://www.techfeb.com/how-to-open-windows-7-hidden-system-reserved-partition/
>>
>> 2013-04-25
>>  ----------
>>  Wangpan
>>  --
>>  *发件人：*Balamurugan V G
>> *发送时间：*2013-04-25 12:34
>> *主题：*Re: [Openstack] [OpenStack] Files Injection in to Windows VMs
>> *收件人：*"Wangpan"
>> *抄送：*"openstack@lists.launchpad.net"
>>
>>  Hi Wanpan,
>>
>> While I am able to inject files in to WindowsXP, CentOS5.9 and
>> Ubuntu12.04. I am unable to do it for Windows8Entrprise OS. I did
>> search the entire drive for the file I injected but couldnt file.
>> Below is the log from nova-compute.log.
>>
>>
>> 2013-04-24 01:41:27.973 AUDIT nova.compute.manager
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Starting instance...
>> 2013-04-24 01:41:28.170 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Attempting claim:
>> memory 1024 MB, disk 10 GB, VCPUs 1
>> 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Memory: 3953
>> MB, used: 2048 MB
>> 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Memory limit: 5929
>> MB, free: 3881 MB
>> 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Disk: 225 GB,
>> used: 15 GB
>> 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Disk limit not
>> specified, defaulting to unlimited
>> 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total CPU: 2 VCPUs,
>> used: 2 VCPUs
>> 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] CPU limit not
>> specified, defaulting to unlimited
>> 2013-04-24 01:41:28.174 AUDIT nova.compute.claims
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Claim successful
>> 2013-04-24 01:41:33.998 INFO nova.virt.libvirt.driver
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Creating image
>> 2013-04-24 01:41:34.281 INFO nova.virt.libvirt.driver
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Injecting files into
>> image 65eaa160-d0e7-403e-a52c-90bea3c22cf7
>> 2013-04-24 01:41:36.534 INFO nova.virt.libvirt.firewall
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Called
>> setup_basic_filtering in nwfilter
>> 2013-04-24 01:41:36.535 INFO nova.virt.libvirt.firewall
>> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
>> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
>> [instance: aa46445e-1f86-4a5a-8002-a77

Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

[Balamurugan V G]

Thanks for link! By running the OpenHiddenSystemDrive exe, I am able to see
the injected file.

Regards,
Balu


On Thu, Apr 25, 2013 at 10:30 AM, Wangpan wrote:

> **
> have you open and check the 'system reserved partition'? see the refer at
> bellow:
>
> http://www.techfeb.com/how-to-open-windows-7-hidden-system-reserved-partition/
>
> 2013-04-25
>  --
>  Wangpan
>  ----------
>  *发件人：*Balamurugan V G
> *发送时间：*2013-04-25 12:34
> *主题：*Re: [Openstack] [OpenStack] Files Injection in to Windows VMs
> *收件人：*"Wangpan"
> *抄送：*"openstack@lists.launchpad.net"
>
>  Hi Wanpan,
>
> While I am able to inject files in to WindowsXP, CentOS5.9 and
> Ubuntu12.04. I am unable to do it for Windows8Entrprise OS. I did
> search the entire drive for the file I injected but couldnt file.
> Below is the log from nova-compute.log.
>
>
> 2013-04-24 01:41:27.973 AUDIT nova.compute.manager
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Starting instance...
> 2013-04-24 01:41:28.170 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Attempting claim:
> memory 1024 MB, disk 10 GB, VCPUs 1
> 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Memory: 3953
> MB, used: 2048 MB
> 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Memory limit: 5929
> MB, free: 3881 MB
> 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Disk: 225 GB,
> used: 15 GB
> 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Disk limit not
> specified, defaulting to unlimited
> 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total CPU: 2 VCPUs,
> used: 2 VCPUs
> 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] CPU limit not
> specified, defaulting to unlimited
> 2013-04-24 01:41:28.174 AUDIT nova.compute.claims
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Claim successful
> 2013-04-24 01:41:33.998 INFO nova.virt.libvirt.driver
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Creating image
> 2013-04-24 01:41:34.281 INFO nova.virt.libvirt.driver
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Injecting files into
> image 65eaa160-d0e7-403e-a52c-90bea3c22cf7
> 2013-04-24 01:41:36.534 INFO nova.virt.libvirt.firewall
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Called
> setup_basic_filtering in nwfilter
> 2013-04-24 01:41:36.535 INFO nova.virt.libvirt.firewall
> [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
> 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Ensuring static
> filters
> 2013-04-24 01:41:38.555 13316 INFO nova.compute.manager [-] Lifecycle
> event 0 on VM aa46445e-1f86-4a5a-8002-a7703ff98648
> 2013-04-24 01:41:38.763 13316 INFO nova.virt.libvirt.driver [-]
> [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Instance spawned
> successfully.
> 2013-04-24 01:41:38.996 13316 INFO nova.compute.manager [-] [instance:
> aa46445e-1f86-4a5a-8002-a7703ff98648] During sync_power_state the
> instance has a pending task. Skip.
> 2013-04-24 01:41:59.494 13

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

nstack-dev:~# ip netns exec
qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 ifconfig
loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

qg-193bb8ee-f5 Link encap:Ethernet  HWaddr fa:16:3e:91:3d:c0
  inet addr:10.5.12.21  Bcast:10.5.12.255  Mask:255.255.255.0
  inet6 addr: fe80::f816:3eff:fe91:3dc0/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:121097 errors:0 dropped:104 overruns:0 frame:0
  TX packets:38777 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:88797723 (88.7 MB)  TX bytes:3112197 (3.1 MB)

qr-59e69986-6e Link encap:Ethernet  HWaddr fa:16:3e:91:ee:76
  inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
  inet6 addr: fe80::f816:3eff:fe91:ee76/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:101615 errors:0 dropped:0 overruns:0 frame:0
  TX packets:68028 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:12476279 (12.4 MB)  TX bytes:83025755 (83.0 MB)

root@openstack-dev:~#

Regards,
Balu



On Wed, Apr 24, 2013 at 11:32 PM, Aaron Rosen  wrote:

> Can you show us a quantum subnet-show for the subnet your vm has an ip on.
> Is it possible that you added a host_route to the subnet for 169.254/16?
>
> Or could you try this image:
> http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img
>
>
> On Wed, Apr 24, 2013 at 1:06 AM, Balamurugan V G 
> wrote:
>
>> I booted a Ubuntu Image in which I had made sure that there was no
>> pre-existing route for 169,254.0.0/16. But its getting the route from DHCP
>> once its boots up. So its the DHCP server which is sending this route to
>> the VM.
>>
>> Regards,
>> Balu
>>
>>
>> On Wed, Apr 24, 2013 at 12:47 PM, Balamurugan V G <
>> balamuruga...@gmail.com> wrote:
>>
>>> Hi Salvatore,
>>>
>>> Thanks for the response. I do not have enable_isolated_metadata_proxy
>>> anywhere under /etc/quantum and /etc/nova. The closest I see is
>>> 'enable_isolated_metadata' in /etc/quantum/dhcp_agent.ini and even that is
>>> commented out. What do you mean by link-local address?
>>>
>>> Like you said, I suspect that the image has the route. This was was a
>>> snapshot taken in a Folsom setup. So its possible that Folsom has injected
>>> this route and when I took the snapshot, it became part of the snapshot. I
>>> then copied over this snapshot to a new Grizzly setup. Let me check the
>>> image and remove it from the image if it has the route. Thanks for the hint
>>> again.
>>>
>>> Regards,
>>> Balu
>>>
>>>
>>>
>>> On Wed, Apr 24, 2013 at 12:38 PM, Salvatore Orlando >> > wrote:
>>>
>>>> The dhcp agent will set a route to 169.254.0.0/16 if
>>>> enable_isolated_metadata_proxy=True.
>>>> In that case the dhcp port ip will be the nexthop for that route.
>>>>
>>>> Otherwise, it might be your image might have a 'builtin' route to such
>>>> cidr.
>>>> What's your nexthop for the link-local address?
>>>>
>>>> Salvatore
>>>>
>>>>
>>>> On 24 April 2013 08:00, Balamurugan V G wrote:
>>>>
>>>>> Thanks for the hint Aaron. When I deleted the route for 
>>>>> 169.254.0.0/16from the VMs routing table, I could access the metadata 
>>>>> service!
>>>>>
>>>>> The route for 169.254.0.0/16 is added automatically when the instance
>>>>> boots up, so I assume its coming from the DHCP. Any idea how this can be
>>>>> suppressed?
>>>>>
>>>>> Strangely though, I do not see this route in a WindowsXP VM booted in
>>>>> the same network as the earlier Ubuntu VM and the Windows VM can reach the
>>>>> metadata service with out me doing anything. The issue is with the Ubuntu
>>>>> VM.
>>>>>
>>>>> Thanks,
>>>>> Balu
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen wrote:
>>>>>
>>>>>> The vm should 

Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

[Balamurugan V G]

-dev.com
2013-04-24 01:43:07.267 13316 INFO nova.compute.manager [-] Updating host status

Regards,
Balu

On Wed, Apr 24, 2013 at 12:19 PM, Balamurugan V G
 wrote:
> Hi Wangpan,
>
> Thanks for the response. The file injection is actually working, sorry my
> bad I was setting the dst-path incorrectly. I am using Nova 2013.1(Grizzly)
> and Windows XP 32bit VM.
>
> When I used the following command, it worked:
>
> nova boot --flavor f43c36f9-de6a-42f4--edcedafe371a --image
> 3872c4c9-d8f7-4a18-a2cc-0406765d9379 --file balu.txt=balu.txt VM2
>
> The file balu.txt ended up in C: drive.
>
> Thanks again.
>
> Regards,
> Balu
>
>
>
>
>
>
>
>
> On Wed, Apr 24, 2013 at 12:07 PM, Wangpan 
> wrote:
>>
>> Hi Balamurugan,
>> What the edition of nova you are running? is there any trace log in
>> nova-compute.log(default path: /var/log/nova/nova-compute.log)?
>> and what the edition of your windows VM(winxp/win7/win8)? if it is win7 or
>> win8, the injected files may exist in the system reserved partition, you can
>> google to open and check the injected files is there.(this may be a bug we
>> need to fix)
>>
>>
>> 2013-04-24
>> 
>> Wangpan
>> 
>> 发件人：Balamurugan V G
>> 发送时间：2013-04-24 14:19
>> 主题：[Openstack] [OpenStack] Files Injection in to Windows VMs
>> 收件人："openstack@lists.launchpad.net"
>> 抄送：
>>
>> Hi,
>>
>> I am able to get File Injection to work during a CentOS or Ubuntu VM
>> instance creation. But it doesnt work for a Windows VM. Is there a way to
>> get it to work for windows VM or it going to be a limitation we have to live
>> with, perhaps due to filesystem differences?
>>
>> Regards,
>> Balu
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] What is the best place to run quantum-ovs-cleanup

[Balamurugan V G]

Ok thanks, this helps a lot. But isnt this being done to avoid those
disruptions/issues with networking after a restart. Do you mean do
doing this will result in disruptions after a restart?

Regards,
Balu

On Wed, Apr 24, 2013 at 9:12 PM, Steve Heistand  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The network node probably wont be running quantum server just one
> of the agents, so you put the command in one of those configs not
> quantum-server.
>
> That is what Im doing currently and it is working for me.
> at some point if you have running VMs with active network
> connections and need to restart quantum for some reason this
> 'may' interrupt their connections. something to keep in mind.
>
> steve
>
>
> On 04/24/2013 08:32 AM, Balamurugan V G wrote:
>> Right now, I have a single node setup on which I am qualifying my use cases 
>> but
>> eventually I will have a controller node, network node and several compute 
>> nodes. In
>> that case, do you mean it should something like this?
>>
>> Controller : post-start of quantum-server.cong Network :   post-start of
>> quantum-server.cong Compute:  pre-start of  
>> quantum-plugin-openvswitch-agent.conf
>>
>> Thanks, Balu
>>
>> On Wed, Apr 24, 2013 at 8:52 PM, Steve Heistand  
>> wrote: it
>> was mentioned to me (by Mr Mihaiescu) that this only works if controller and 
>> network
>> node are on the same machine. For the compute nodes I had forgotten its in a
>> different place. On them I am doing it in a pre-start script in
>> quantum-plugin-openvswitch-agent.conf. if the controller/network are on 
>> different
>> machines certainly in the quantum-server.conf work on which ever one of them 
>> is
>> actually using it, if it doesnt the command will have to be in a different 
>> startup
>> script.
>>
>> It was also mentioned that putting things in /etc/rc.local and then 
>> restarting all
>> the quantum related services might work too.
>>
>> steve
>>
>> On 04/24/2013 08:15 AM, Balamurugan V G wrote:
>>>>> Thanks Steve.
>>>>>
>>>>> I came across another way at
>>>>> https://bugs.launchpad.net/quantum/+bug/1084355/comments/15. It seems to 
>>>>> work
>>>>> as well. But your solution is simpler :)
>>>>>
>>>>> Regards, Balu
>>>>>
>>>>>
>>>>> On Wed, Apr 24, 2013 at 7:41 PM, Steve Heistand 
>>>>> wrote: I put it in the file:/etc/init/quantum-server.conf
>>>>>
>>>>> post-start script /usr/bin/quantum-ovs-cleanup exit 1 end script
>>>>>
>>>>>
>>>>> On 04/24/2013 02:45 AM, Balamurugan V G wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> It seems due to an OVS quantum bug, we need to run the utility
>>>>>>>> quantum-ovs-cleanup before any of the quantum services start, upon a
>>>>>>>> server reboot.
>>>>>>>>
>>>>>>>> Where is the best place to put this utility to run automatically when a
>>>>>>>> server reboots so that the OVS issue is automatically addressed? A 
>>>>>>>> script
>>>>>>>> in /etc/init.d or just plugging in a call for quantum-ovs-cleanup in an
>>>>>>>> existing script?
>>>>>>>>
>>>>>>>> Thanks, Balu
>>>>>>>>
>>>>>>>> ___ Mailing list:
>>>>>>>> https://launchpad.net/~openstack Post to :
>>>>>>>> openstack@lists.launchpad.net Unsubscribe :
>>>>>>>> https://launchpad.net/~openstack More help   :
>>>>>>>> https://help.launchpad.net/ListHelp
>>>>>>>>
>>>>>
>>
>
> - --
> 
>  Steve Heistand  NASA Ames Research Center
>  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
>  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
>  Scientific & HPC ApplicationP.O. Box 1
>  Development/OptimizationMoffett Field, CA 94035-0001
> 
>  "Any opinions expressed are those of our alien overlords, not my own."
>
> # For Remedy#
> #Action: Resolve#
> #Resolution: Resolved   #
> #Reason: No Further Action Required #
> #Tier1: User Code   #
> #Tier2: Other   #
> #Tier3: Assistance  #
> #Notification: None #
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEARECAAYFAlF3/W0ACgkQoBCTJSAkVrHdnwCgrnCfjN1NKCml+jFPtHk0s4iA
> Nx0An3g6abwQons0jMXkJLu4oBhiZ4ot
> =zh9U
> -END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] What is the best place to run quantum-ovs-cleanup

[Balamurugan V G]

Right now, I have a single node setup on which I am qualifying my use
cases but eventually I will have a controller node, network node and
several compute nodes. In that case, do you mean it should something
like this?

Controller : post-start of quantum-server.cong
Network :   post-start of quantum-server.cong
Compute:  pre-start of  quantum-plugin-openvswitch-agent.conf

Thanks,
Balu

On Wed, Apr 24, 2013 at 8:52 PM, Steve Heistand  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> it was mentioned to me (by Mr Mihaiescu) that this only works if controller 
> and network node
> are on the same machine. For the compute nodes I had forgotten its in a 
> different
> place. On them I am doing it in a pre-start script in 
> quantum-plugin-openvswitch-agent.conf.
> if the controller/network are on different machines certainly in the 
> quantum-server.conf
> work on which ever one of them is actually using it, if it doesnt the command 
> will have
> to be in a different startup script.
>
> It was also mentioned that putting things in /etc/rc.local and then restarting
> all the quantum related services might work too.
>
> steve
>
> On 04/24/2013 08:15 AM, Balamurugan V G wrote:
>> Thanks Steve.
>>
>> I came across another way at
>> https://bugs.launchpad.net/quantum/+bug/1084355/comments/15. It seems to 
>> work as
>> well. But your solution is simpler :)
>>
>> Regards, Balu
>>
>>
>> On Wed, Apr 24, 2013 at 7:41 PM, Steve Heistand  
>> wrote: I
>> put it in the file:/etc/init/quantum-server.conf
>>
>> post-start script /usr/bin/quantum-ovs-cleanup exit 1 end script
>>
>>
>> On 04/24/2013 02:45 AM, Balamurugan V G wrote:
>>>>> Hi,
>>>>>
>>>>> It seems due to an OVS quantum bug, we need to run the utility
>>>>> quantum-ovs-cleanup before any of the quantum services start, upon a 
>>>>> server
>>>>> reboot.
>>>>>
>>>>> Where is the best place to put this utility to run automatically when a 
>>>>> server
>>>>> reboots so that the OVS issue is automatically addressed? A script in
>>>>> /etc/init.d or just plugging in a call for quantum-ovs-cleanup in an 
>>>>> existing
>>>>> script?
>>>>>
>>>>> Thanks, Balu
>>>>>
>>>>> ___ Mailing list:
>>>>> https://launchpad.net/~openstack Post to : 
>>>>> openstack@lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~openstack More help   :
>>>>> https://help.launchpad.net/ListHelp
>>>>>
>>
>
> - --
> 
>  Steve Heistand  NASA Ames Research Center
>  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
>  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
>  Scientific & HPC ApplicationP.O. Box 1
>  Development/OptimizationMoffett Field, CA 94035-0001
> 
>  "Any opinions expressed are those of our alien overlords, not my own."
>
> # For Remedy#
> #Action: Resolve#
> #Resolution: Resolved   #
> #Reason: No Further Action Required #
> #Tier1: User Code   #
> #Tier2: Other   #
> #Tier3: Assistance  #
> #Notification: None #
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEARECAAYFAlF3+K8ACgkQoBCTJSAkVrFfRACgjiiRXjyRGfc2fGPJWTmJTjnK
> 89cAnRnstn0e/GiYz0Go13R2B+lBUWWw
> =HmUJ
> -END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] What is the best place to run quantum-ovs-cleanup

[Balamurugan V G]

Thanks Steve.

I came across another way at
https://bugs.launchpad.net/quantum/+bug/1084355/comments/15. It seems
to work as well. But your solution is simpler :)

Regards,
Balu


On Wed, Apr 24, 2013 at 7:41 PM, Steve Heistand  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I put it in the file:/etc/init/quantum-server.conf
>
> post-start script
> /usr/bin/quantum-ovs-cleanup
> exit 1
> end script
>
>
> On 04/24/2013 02:45 AM, Balamurugan V G wrote:
>> Hi,
>>
>> It seems due to an OVS quantum bug, we need to run the utility 
>> quantum-ovs-cleanup
>> before any of the quantum services start, upon a server reboot.
>>
>> Where is the best place to put this utility to run automatically when a 
>> server
>> reboots so that the OVS issue is automatically addressed? A script in 
>> /etc/init.d or
>> just plugging in a call for quantum-ovs-cleanup in an existing script?
>>
>> Thanks, Balu
>>
>> ___ Mailing list:
>> https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack More help   :
>> https://help.launchpad.net/ListHelp
>>
>
> - --
> 
>  Steve Heistand  NASA Ames Research Center
>  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
>  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
>  Scientific & HPC ApplicationP.O. Box 1
>  Development/OptimizationMoffett Field, CA 94035-0001
> 
>  "Any opinions expressed are those of our alien overlords, not my own."
>
> # For Remedy#
> #Action: Resolve#
> #Resolution: Resolved   #
> #Reason: No Further Action Required #
> #Tier1: User Code   #
> #Tier2: Other   #
> #Tier3: Assistance  #
> #Notification: None #
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEARECAAYFAlF36C8ACgkQoBCTJSAkVrGqMACg3Jm7tTBwx08oOSaiTVux7sRl
> cNMAn0OMrAElV2CZgqZFaayoeOitQMUn
> =TGy3
> -END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] What is the best place to run quantum-ovs-cleanup

[Balamurugan V G]

Hi,

It seems due to an OVS quantum bug, we need to run the utility
quantum-ovs-cleanup before any of the quantum services start, upon a
server reboot.

Where is the best place to put this utility to run automatically when
a server reboots so that the OVS issue is automatically addressed? A
script in /etc/init.d or just plugging in a call for
quantum-ovs-cleanup in an existing script?

Thanks,
Balu

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

[Balamurugan V G]

Thanks Razique, I'll try this as well. I am also trying for out of the box
options like file injection and meta-data service.

Regards,
Balu


On Wed, Apr 24, 2013 at 1:57 PM, Razique Mahroua
wrote:

> Hi Balu,
> check this out
> http://www.cloudbase.it/cloud-init-for-windows-instances/
>
> It's a great tool, I just had issues myself with the Admin. password
> changing
>
> Regards,
> Razique
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 24 avr. 2013 à 08:17, Balamurugan V G  a
> écrit :
>
> Hi,
>
> I am able to get File Injection to work during a CentOS or Ubuntu VM
> instance creation. But it doesnt work for a Windows VM. Is there a way to
> get it to work for windows VM or it going to be a limitation we have to
> live with, perhaps due to filesystem differences?
>
> Regards,
> Balu
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
<>___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

I booted a Ubuntu Image in which I had made sure that there was no
pre-existing route for 169,254.0.0/16. But its getting the route from DHCP
once its boots up. So its the DHCP server which is sending this route to
the VM.

Regards,
Balu


On Wed, Apr 24, 2013 at 12:47 PM, Balamurugan V G
wrote:

> Hi Salvatore,
>
> Thanks for the response. I do not have enable_isolated_metadata_proxy
> anywhere under /etc/quantum and /etc/nova. The closest I see is
> 'enable_isolated_metadata' in /etc/quantum/dhcp_agent.ini and even that is
> commented out. What do you mean by link-local address?
>
> Like you said, I suspect that the image has the route. This was was a
> snapshot taken in a Folsom setup. So its possible that Folsom has injected
> this route and when I took the snapshot, it became part of the snapshot. I
> then copied over this snapshot to a new Grizzly setup. Let me check the
> image and remove it from the image if it has the route. Thanks for the hint
> again.
>
> Regards,
> Balu
>
>
>
> On Wed, Apr 24, 2013 at 12:38 PM, Salvatore Orlando 
> wrote:
>
>> The dhcp agent will set a route to 169.254.0.0/16 if
>> enable_isolated_metadata_proxy=True.
>> In that case the dhcp port ip will be the nexthop for that route.
>>
>> Otherwise, it might be your image might have a 'builtin' route to such
>> cidr.
>> What's your nexthop for the link-local address?
>>
>> Salvatore
>>
>>
>> On 24 April 2013 08:00, Balamurugan V G  wrote:
>>
>>> Thanks for the hint Aaron. When I deleted the route for 169.254.0.0/16from 
>>> the VMs routing table, I could access the metadata service!
>>>
>>> The route for 169.254.0.0/16 is added automatically when the instance
>>> boots up, so I assume its coming from the DHCP. Any idea how this can be
>>> suppressed?
>>>
>>> Strangely though, I do not see this route in a WindowsXP VM booted in
>>> the same network as the earlier Ubuntu VM and the Windows VM can reach the
>>> metadata service with out me doing anything. The issue is with the Ubuntu
>>> VM.
>>>
>>> Thanks,
>>> Balu
>>>
>>>
>>>
>>> On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen  wrote:
>>>
>>>> The vm should not have a routing table entry for 169.254.0.0/16  if it
>>>> does i'm not sure how it got there unless it was added by something other
>>>> than dhcp. It seems like that is your problem as the vm is arping directly
>>>> for that address rather than the default gw.
>>>>
>>>>
>>>> On Tue, Apr 23, 2013 at 11:34 PM, Balamurugan V G <
>>>> balamuruga...@gmail.com> wrote:
>>>>
>>>>> Thanks Aaron.
>>>>>
>>>>> I am perhaps not configuring it right then. I am using Ubuntu 12.04
>>>>> host and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see
>>>>> that the VM's routing table has an entry for 169.254.0.0/16 but I
>>>>> cant ping 169.254.169.254 from the VM. I am using a single node setup with
>>>>> two NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP
>>>>>
>>>>> These are my metadata related configurations.
>>>>>
>>>>> */etc/nova/nova.conf *
>>>>> metadata_host = 10.5.12.20
>>>>> metadata_listen = 127.0.0.1
>>>>> metadata_listen_port = 8775
>>>>> metadata_manager=nova.api.manager.MetadataManager
>>>>> service_quantum_metadata_proxy = true
>>>>> quantum_metadata_proxy_shared_secret = metasecret123
>>>>>
>>>>> */etc/quantum/quantum.conf*
>>>>> allow_overlapping_ips = True
>>>>>
>>>>> */etc/quantum/l3_agent.ini*
>>>>> use_namespaces = True
>>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>>> auth_region = RegionOne
>>>>> admin_tenant_name = service
>>>>> admin_user = quantum
>>>>> admin_password = service_pass
>>>>> metadata_ip = 10.5.12.20
>>>>>
>>>>> */etc/quantum/metadata_agent.ini*
>>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>>> auth_region = RegionOne
>>>>> admin_tenant_name = service
>>>>> admin_user = quantum
>>>>> admin_password = service_pass
>>>>> nova_metadata_ip = 127.0.0.1
>>>>> nova_metadata_port = 8775
>>>>> metadata_proxy_shared_secret = metasecret123
&

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

The routing table in the VM is:

root@vm:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0
192.168.2.0 0.0.0.0 255.255.255.0   U 1  00 eth0
root@vm:~#

And the routing table in the OpenStack node(single node host) is:

root@openstack-dev:~# ip netns exec
qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 10.5.12.1   0.0.0.0 UG0  00
qg-193bb8ee-f5
10.5.12.0   0.0.0.0 255.255.255.0   U 0  00
qg-193bb8ee-f5
192.168.2.0 0.0.0.0 255.255.255.0   U 0  00
qr-59e69986-6e
root@openstack-dev:~#

Regards,
Balu




On Wed, Apr 24, 2013 at 12:41 PM, Aaron Rosen  wrote:

> Yup,  That's only if your subnet does not have a default gateway set.
> Providing the output of route -n would be helpful .
>
>
> On Wed, Apr 24, 2013 at 12:08 AM, Salvatore Orlando 
> wrote:
>
>> The dhcp agent will set a route to 169.254.0.0/16 if
>> enable_isolated_metadata_proxy=True.
>> In that case the dhcp port ip will be the nexthop for that route.
>>
>> Otherwise, it might be your image might have a 'builtin' route to such
>> cidr.
>> What's your nexthop for the link-local address?
>>
>> Salvatore
>>
>>
>> On 24 April 2013 08:00, Balamurugan V G  wrote:
>>
>>> Thanks for the hint Aaron. When I deleted the route for 169.254.0.0/16from 
>>> the VMs routing table, I could access the metadata service!
>>>
>>> The route for 169.254.0.0/16 is added automatically when the instance
>>> boots up, so I assume its coming from the DHCP. Any idea how this can be
>>> suppressed?
>>>
>>> Strangely though, I do not see this route in a WindowsXP VM booted in
>>> the same network as the earlier Ubuntu VM and the Windows VM can reach the
>>> metadata service with out me doing anything. The issue is with the Ubuntu
>>> VM.
>>>
>>> Thanks,
>>> Balu
>>>
>>>
>>>
>>> On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen  wrote:
>>>
>>>> The vm should not have a routing table entry for 169.254.0.0/16  if it
>>>> does i'm not sure how it got there unless it was added by something other
>>>> than dhcp. It seems like that is your problem as the vm is arping directly
>>>> for that address rather than the default gw.
>>>>
>>>>
>>>> On Tue, Apr 23, 2013 at 11:34 PM, Balamurugan V G <
>>>> balamuruga...@gmail.com> wrote:
>>>>
>>>>> Thanks Aaron.
>>>>>
>>>>> I am perhaps not configuring it right then. I am using Ubuntu 12.04
>>>>> host and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see
>>>>> that the VM's routing table has an entry for 169.254.0.0/16 but I
>>>>> cant ping 169.254.169.254 from the VM. I am using a single node setup with
>>>>> two NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP
>>>>>
>>>>> These are my metadata related configurations.
>>>>>
>>>>> */etc/nova/nova.conf *
>>>>> metadata_host = 10.5.12.20
>>>>> metadata_listen = 127.0.0.1
>>>>> metadata_listen_port = 8775
>>>>> metadata_manager=nova.api.manager.MetadataManager
>>>>> service_quantum_metadata_proxy = true
>>>>> quantum_metadata_proxy_shared_secret = metasecret123
>>>>>
>>>>> */etc/quantum/quantum.conf*
>>>>> allow_overlapping_ips = True
>>>>>
>>>>> */etc/quantum/l3_agent.ini*
>>>>> use_namespaces = True
>>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>>> auth_region = RegionOne
>>>>> admin_tenant_name = service
>>>>> admin_user = quantum
>>>>> admin_password = service_pass
>>>>> metadata_ip = 10.5.12.20
>>>>>
>>>>> */etc/quantum/metadata_agent.ini*
>>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>>> auth_region = RegionOne
>>>>> admin_tenant_name = service
>>>>> admin_user = quantum
>>>>> admin_password = service_pass
>>>>> nova_metadata_ip = 127.0.0.1
>>>>> nov

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

I do not have any thing running in the VM which could add this route. With
the route removed, when I disable and enable networking, so that it gets
back the details from DHCP server, I see that the route is getting added
again.

So DHCP seems to be my issue. I guess this rules out any pre-existing route
in the image as well.

Regards,
Balu


On Wed, Apr 24, 2013 at 12:39 PM, Aaron Rosen  wrote:

> Hrm, I'd do quantum subnet-list and see if you happened to create a subnet
> 169.254.0.0/16? Otherwise I think there is probably some software in your
> vm image that is adding this route. One thing to test is if you delete this
> route and then rerun dhclient to see if it's added again via dhcp.
>
>
> On Wed, Apr 24, 2013 at 12:00 AM, Balamurugan V G  > wrote:
>
>> Thanks for the hint Aaron. When I deleted the route for 169.254.0.0/16from 
>> the VMs routing table, I could access the metadata service!
>>
>> The route for 169.254.0.0/16 is added automatically when the instance
>> boots up, so I assume its coming from the DHCP. Any idea how this can be
>> suppressed?
>>
>> Strangely though, I do not see this route in a WindowsXP VM booted in the
>> same network as the earlier Ubuntu VM and the Windows VM can reach the
>> metadata service with out me doing anything. The issue is with the Ubuntu
>> VM.
>>
>> Thanks,
>> Balu
>>
>>
>>
>> On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen  wrote:
>>
>>> The vm should not have a routing table entry for 169.254.0.0/16  if it
>>> does i'm not sure how it got there unless it was added by something other
>>> than dhcp. It seems like that is your problem as the vm is arping directly
>>> for that address rather than the default gw.
>>>
>>>
>>> On Tue, Apr 23, 2013 at 11:34 PM, Balamurugan V G <
>>> balamuruga...@gmail.com> wrote:
>>>
>>>> Thanks Aaron.
>>>>
>>>> I am perhaps not configuring it right then. I am using Ubuntu 12.04
>>>> host and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see
>>>> that the VM's routing table has an entry for 169.254.0.0/16 but I cant
>>>> ping 169.254.169.254 from the VM. I am using a single node setup with two
>>>> NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP
>>>>
>>>> These are my metadata related configurations.
>>>>
>>>> */etc/nova/nova.conf *
>>>> metadata_host = 10.5.12.20
>>>> metadata_listen = 127.0.0.1
>>>> metadata_listen_port = 8775
>>>> metadata_manager=nova.api.manager.MetadataManager
>>>> service_quantum_metadata_proxy = true
>>>> quantum_metadata_proxy_shared_secret = metasecret123
>>>>
>>>> */etc/quantum/quantum.conf*
>>>> allow_overlapping_ips = True
>>>>
>>>> */etc/quantum/l3_agent.ini*
>>>> use_namespaces = True
>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>> auth_region = RegionOne
>>>> admin_tenant_name = service
>>>> admin_user = quantum
>>>> admin_password = service_pass
>>>> metadata_ip = 10.5.12.20
>>>>
>>>> */etc/quantum/metadata_agent.ini*
>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>> auth_region = RegionOne
>>>> admin_tenant_name = service
>>>> admin_user = quantum
>>>> admin_password = service_pass
>>>> nova_metadata_ip = 127.0.0.1
>>>> nova_metadata_port = 8775
>>>> metadata_proxy_shared_secret = metasecret123
>>>>
>>>>
>>>> I see that /usr/bin/quantum-ns-metadata-proxy process is running. When
>>>> I ping 169.254.169.254 from VM, in the host's router namespace, I see the
>>>> ARP request but no response.
>>>>
>>>> root@openstack-dev:~# ip netns exec
>>>> qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n
>>>> Kernel IP routing table
>>>> Destination Gateway Genmask Flags Metric RefUse
>>>> Iface
>>>> 0.0.0.0 10.5.12.1   0.0.0.0 UG0  00
>>>> qg-193bb8ee-f5
>>>> 10.5.12.0   0.0.0.0 255.255.255.0   U 0  00
>>>> qg-193bb8ee-f5
>>>> 192.168.2.0 0.0.0.0 255.255.255.0   U 0  00
>>>> qr-59e69986-6e
>>>> root@openstack-dev:~# ip netns exec
>>>> qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 tcpdump -i qr-59e69986-6e
>>>> tcpdu

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

Hi Salvatore,

Thanks for the response. I do not have enable_isolated_metadata_proxy
anywhere under /etc/quantum and /etc/nova. The closest I see is
'enable_isolated_metadata' in /etc/quantum/dhcp_agent.ini and even that is
commented out. What do you mean by link-local address?

Like you said, I suspect that the image has the route. This was was a
snapshot taken in a Folsom setup. So its possible that Folsom has injected
this route and when I took the snapshot, it became part of the snapshot. I
then copied over this snapshot to a new Grizzly setup. Let me check the
image and remove it from the image if it has the route. Thanks for the hint
again.

Regards,
Balu



On Wed, Apr 24, 2013 at 12:38 PM, Salvatore Orlando wrote:

> The dhcp agent will set a route to 169.254.0.0/16 if
> enable_isolated_metadata_proxy=True.
> In that case the dhcp port ip will be the nexthop for that route.
>
> Otherwise, it might be your image might have a 'builtin' route to such
> cidr.
> What's your nexthop for the link-local address?
>
> Salvatore
>
>
> On 24 April 2013 08:00, Balamurugan V G  wrote:
>
>> Thanks for the hint Aaron. When I deleted the route for 169.254.0.0/16from 
>> the VMs routing table, I could access the metadata service!
>>
>> The route for 169.254.0.0/16 is added automatically when the instance
>> boots up, so I assume its coming from the DHCP. Any idea how this can be
>> suppressed?
>>
>> Strangely though, I do not see this route in a WindowsXP VM booted in the
>> same network as the earlier Ubuntu VM and the Windows VM can reach the
>> metadata service with out me doing anything. The issue is with the Ubuntu
>> VM.
>>
>> Thanks,
>> Balu
>>
>>
>>
>> On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen  wrote:
>>
>>> The vm should not have a routing table entry for 169.254.0.0/16  if it
>>> does i'm not sure how it got there unless it was added by something other
>>> than dhcp. It seems like that is your problem as the vm is arping directly
>>> for that address rather than the default gw.
>>>
>>>
>>> On Tue, Apr 23, 2013 at 11:34 PM, Balamurugan V G <
>>> balamuruga...@gmail.com> wrote:
>>>
>>>> Thanks Aaron.
>>>>
>>>> I am perhaps not configuring it right then. I am using Ubuntu 12.04
>>>> host and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see
>>>> that the VM's routing table has an entry for 169.254.0.0/16 but I cant
>>>> ping 169.254.169.254 from the VM. I am using a single node setup with two
>>>> NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP
>>>>
>>>> These are my metadata related configurations.
>>>>
>>>> */etc/nova/nova.conf *
>>>> metadata_host = 10.5.12.20
>>>> metadata_listen = 127.0.0.1
>>>> metadata_listen_port = 8775
>>>> metadata_manager=nova.api.manager.MetadataManager
>>>> service_quantum_metadata_proxy = true
>>>> quantum_metadata_proxy_shared_secret = metasecret123
>>>>
>>>> */etc/quantum/quantum.conf*
>>>> allow_overlapping_ips = True
>>>>
>>>> */etc/quantum/l3_agent.ini*
>>>> use_namespaces = True
>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>> auth_region = RegionOne
>>>> admin_tenant_name = service
>>>> admin_user = quantum
>>>> admin_password = service_pass
>>>> metadata_ip = 10.5.12.20
>>>>
>>>> */etc/quantum/metadata_agent.ini*
>>>> auth_url = http://10.5.3.230:35357/v2.0
>>>> auth_region = RegionOne
>>>> admin_tenant_name = service
>>>> admin_user = quantum
>>>> admin_password = service_pass
>>>> nova_metadata_ip = 127.0.0.1
>>>> nova_metadata_port = 8775
>>>> metadata_proxy_shared_secret = metasecret123
>>>>
>>>>
>>>> I see that /usr/bin/quantum-ns-metadata-proxy process is running. When
>>>> I ping 169.254.169.254 from VM, in the host's router namespace, I see the
>>>> ARP request but no response.
>>>>
>>>> root@openstack-dev:~# ip netns exec
>>>> qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n
>>>> Kernel IP routing table
>>>> Destination Gateway Genmask Flags Metric RefUse
>>>> Iface
>>>> 0.0.0.0 10.5.12.1   0.0.0.0 UG0  00
>>>> qg-193bb8ee-f5
>>>> 10.5.12.0   0.0.0.0

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

Thanks for the hint Aaron. When I deleted the route for 169.254.0.0/16 from
the VMs routing table, I could access the metadata service!

The route for 169.254.0.0/16 is added automatically when the instance boots
up, so I assume its coming from the DHCP. Any idea how this can be
suppressed?

Strangely though, I do not see this route in a WindowsXP VM booted in the
same network as the earlier Ubuntu VM and the Windows VM can reach the
metadata service with out me doing anything. The issue is with the Ubuntu
VM.

Thanks,
Balu



On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen  wrote:

> The vm should not have a routing table entry for 169.254.0.0/16  if it
> does i'm not sure how it got there unless it was added by something other
> than dhcp. It seems like that is your problem as the vm is arping directly
> for that address rather than the default gw.
>
>
> On Tue, Apr 23, 2013 at 11:34 PM, Balamurugan V G  > wrote:
>
>> Thanks Aaron.
>>
>> I am perhaps not configuring it right then. I am using Ubuntu 12.04 host
>> and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see that
>> the VM's routing table has an entry for 169.254.0.0/16 but I cant ping
>> 169.254.169.254 from the VM. I am using a single node setup with two
>> NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP
>>
>> These are my metadata related configurations.
>>
>> */etc/nova/nova.conf *
>> metadata_host = 10.5.12.20
>> metadata_listen = 127.0.0.1
>> metadata_listen_port = 8775
>> metadata_manager=nova.api.manager.MetadataManager
>> service_quantum_metadata_proxy = true
>> quantum_metadata_proxy_shared_secret = metasecret123
>>
>> */etc/quantum/quantum.conf*
>> allow_overlapping_ips = True
>>
>> */etc/quantum/l3_agent.ini*
>> use_namespaces = True
>> auth_url = http://10.5.3.230:35357/v2.0
>> auth_region = RegionOne
>> admin_tenant_name = service
>> admin_user = quantum
>> admin_password = service_pass
>> metadata_ip = 10.5.12.20
>>
>> */etc/quantum/metadata_agent.ini*
>> auth_url = http://10.5.3.230:35357/v2.0
>> auth_region = RegionOne
>> admin_tenant_name = service
>> admin_user = quantum
>> admin_password = service_pass
>> nova_metadata_ip = 127.0.0.1
>> nova_metadata_port = 8775
>> metadata_proxy_shared_secret = metasecret123
>>
>>
>> I see that /usr/bin/quantum-ns-metadata-proxy process is running. When I
>> ping 169.254.169.254 from VM, in the host's router namespace, I see the ARP
>> request but no response.
>>
>> root@openstack-dev:~# ip netns exec
>> qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric RefUse
>> Iface
>> 0.0.0.0 10.5.12.1   0.0.0.0 UG0  00
>> qg-193bb8ee-f5
>> 10.5.12.0   0.0.0.0 255.255.255.0   U 0  00
>> qg-193bb8ee-f5
>> 192.168.2.0 0.0.0.0 255.255.255.0   U 0  00
>> qr-59e69986-6e
>> root@openstack-dev:~# ip netns exec
>> qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 tcpdump -i qr-59e69986-6e
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on qr-59e69986-6e, link-type EN10MB (Ethernet), capture size
>> 65535 bytes
>> ^C23:32:09.638289 ARP, Request who-has 192.168.2.3 tell 192.168.2.1,
>> length 28
>> 23:32:09.650043 ARP, Reply 192.168.2.3 is-at fa:16:3e:4f:ad:df (oui
>> Unknown), length 28
>> 23:32:15.768942 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
>> length 28
>> 23:32:16.766896 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
>> length 28
>> 23:32:17.766712 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
>> length 28
>> 23:32:18.784195 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
>> length 28
>>
>> 6 packets captured
>> 6 packets received by filter
>> 0 packets dropped by kernel
>> root@openstack-dev:~#
>>
>>
>> Any help will be greatly appreciated.
>>
>> Thanks,
>> Balu
>>
>>
>> On Wed, Apr 24, 2013 at 11:48 AM, Aaron Rosen  wrote:
>>
>>> Yup, If your host supports namespaces this can be done via the
>>> quantum-metadata-agent.  The following setting is also required in your
>>>  nova.conf: service_quantum_metadata_proxy=True
>>>
>>>
>>> On Tue, Apr 23, 2013 at 10:44 PM, Balamurugan V G <
>>> balamuruga...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> In Grizzly, when using quantum and overlapping IPs, does metadata
>>>> service work? This wasnt working in Folsom.
>>>>
>>>> Thanks,
>>>> Balu
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

[Balamurugan V G]

Hi Wangpan,

Thanks for the response. The file injection is actually working, sorry my
bad I was setting the dst-path incorrectly. I am using Nova 2013.1(Grizzly)
and Windows XP 32bit VM.

When I used the following command, it worked:

nova boot --flavor f43c36f9-de6a-42f4--edcedafe371a --image
3872c4c9-d8f7-4a18-a2cc-0406765d9379 --file balu.txt=balu.txt VM2

The file balu.txt ended up in C: drive.

Thanks again.

Regards,
Balu








On Wed, Apr 24, 2013 at 12:07 PM, Wangpan wrote:

> **
>  Hi Balamurugan,
> What the edition of nova you are running? is there any trace log in
> nova-compute.log(default path: /var/log/nova/nova-compute.log)?
> and what the edition of your windows VM(winxp/win7/win8)? if it is win7 or
> win8, the injected files may exist in the system reserved partition, you
> can google to open and check the injected files is there.(this may be a bug
> we need to fix)
>
>
> 2013-04-24
>  --
>  Wangpan
>  ------
>  *发件人：*Balamurugan V G
> *发送时间：*2013-04-24 14:19
> *主题：*[Openstack] [OpenStack] Files Injection in to Windows VMs
> *收件人：*"openstack@lists.launchpad.net"
> *抄送：*
>
>   Hi,
>
> I am able to get File Injection to work during a CentOS or Ubuntu VM
> instance creation. But it doesnt work for a Windows VM. Is there a way to
> get it to work for windows VM or it going to be a limitation we have to
> live with, perhaps due to filesystem differences?
>
> Regards,
> Balu
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

Thanks Aaron.

I am perhaps not configuring it right then. I am using Ubuntu 12.04 host
and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see that
the VM's routing table has an entry for 169.254.0.0/16 but I cant ping
169.254.169.254 from the VM. I am using a single node setup with two
NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP

These are my metadata related configurations.

*/etc/nova/nova.conf *
metadata_host = 10.5.12.20
metadata_listen = 127.0.0.1
metadata_listen_port = 8775
metadata_manager=nova.api.manager.MetadataManager
service_quantum_metadata_proxy = true
quantum_metadata_proxy_shared_secret = metasecret123

*/etc/quantum/quantum.conf*
allow_overlapping_ips = True

*/etc/quantum/l3_agent.ini*
use_namespaces = True
auth_url = http://10.5.3.230:35357/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = quantum
admin_password = service_pass
metadata_ip = 10.5.12.20

*/etc/quantum/metadata_agent.ini*
auth_url = http://10.5.3.230:35357/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = quantum
admin_password = service_pass
nova_metadata_ip = 127.0.0.1
nova_metadata_port = 8775
metadata_proxy_shared_secret = metasecret123


I see that /usr/bin/quantum-ns-metadata-proxy process is running. When I
ping 169.254.169.254 from VM, in the host's router namespace, I see the ARP
request but no response.

root@openstack-dev:~# ip netns exec
qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 10.5.12.1   0.0.0.0 UG0  00
qg-193bb8ee-f5
10.5.12.0   0.0.0.0 255.255.255.0   U 0  00
qg-193bb8ee-f5
192.168.2.0 0.0.0.0 255.255.255.0   U 0  00
qr-59e69986-6e
root@openstack-dev:~# ip netns exec
qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 tcpdump -i qr-59e69986-6e
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on qr-59e69986-6e, link-type EN10MB (Ethernet), capture size
65535 bytes
^C23:32:09.638289 ARP, Request who-has 192.168.2.3 tell 192.168.2.1, length
28
23:32:09.650043 ARP, Reply 192.168.2.3 is-at fa:16:3e:4f:ad:df (oui
Unknown), length 28
23:32:15.768942 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
length 28
23:32:16.766896 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
length 28
23:32:17.766712 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
length 28
23:32:18.784195 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
length 28

6 packets captured
6 packets received by filter
0 packets dropped by kernel
root@openstack-dev:~#


Any help will be greatly appreciated.

Thanks,
Balu


On Wed, Apr 24, 2013 at 11:48 AM, Aaron Rosen  wrote:

> Yup, If your host supports namespaces this can be done via the
> quantum-metadata-agent.  The following setting is also required in your
>  nova.conf: service_quantum_metadata_proxy=True
>
>
> On Tue, Apr 23, 2013 at 10:44 PM, Balamurugan V G  > wrote:
>
>> Hi,
>>
>> In Grizzly, when using quantum and overlapping IPs, does metadata service
>> work? This wasnt working in Folsom.
>>
>> Thanks,
>> Balu
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Files Injection in to Windows VMs

[Balamurugan V G]

Hi,

I am able to get File Injection to work during a CentOS or Ubuntu VM
instance creation. But it doesnt work for a Windows VM. Is there a way to
get it to work for windows VM or it going to be a limitation we have to
live with, perhaps due to filesystem differences?

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

[Balamurugan V G]

Hi,

In Grizzly, when using quantum and overlapping IPs, does metadata service
work? This wasnt working in Folsom.

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Open vSwitch features

[Balamurugan V G]

Hi,

While using the OVS plugin and quantum for networking, is it possible to
use some of the features of OVS like STP, LACP etc (basically the ones
listed at http://openvswitch.org/features/) via OpenStack API? Or should
one have to use OVS API to achieve most of these?

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Re-using VLAN ranges acorss physnet in OVS Quantum plugin based setup

[Balamurugan V G]

Hi,

While using a OVS plugin based Quantum setup, will it be possible to go
beyond 4095 vlans by re-using them across multiple physnets. For example,
is something like the setting below possible?

network_vlan_ranges = physnet1:1:4094, physnet2:1:4094,

Or will this not be allowed due to conflicting VLANs?

Thanks
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Assigning specific networks while creating instances using nova REST API in Folsom - SOLVED

[Balamurugan V G]

Looking in to
/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/servers.py gave
some insights and found that the API can take a parameter 'networks' as
shown below:

curl  -X 'POST'
http://1.1.1.1:8774/v2/4a8c3029619e4afbaa39f85fcd121003/servers -d '{
"server": { "flavorRef": "6", "imageRef":
"dd13a38c-3e1f-49f1-afbe-c6f62cd46ffb", "name": "test4", "*networks*": [{"*
uuid*": "02016649-f9a6-4623-b82f-f5a2c95d2b7a"}, {"*uuid*":
"4784ed46-7f09-4e57-b279-e65529442bd5"}] } }' -H 'Accept: application/json'
-H "X-Auth-Token: 7738bc36849f4b35bd4623e50b249ff3" -H 'Content-type:
application/json'

This associated the desired networks in the order specified, exactly what I
wanted.

Wish this has been documented. I'll file a documentation bug.

Regards,
Balu


On Thu, Mar 21, 2013 at 9:00 PM, Balamurugan V G wrote:

> Hi,
>
> I have a Folsom 2012.2 with Quantum and trying to create the instances
> using the REST API as below:
>
> curl  -X 'POST'
> http://1.1.1.1:8774/v2/4a8c3029619e4afbaa39f85fcd121003/servers -d '{
> "server": { "flavorRef": "6", "imageRef":
> "dd13a38c-3e1f-49f1-afbe-c6f62cd46ffb", "name": "test" } }' -H 'Accept:
> application/json' -H "X-Auth-Token: 1b5f64418cdf4a99a79aada03621cfa9" -H
> 'Content-type: application/json'
>
> But this assigns the instance to all networks available for the tenant. So
> if I have multiple networks for a tenant, how do I assign the instance to
> specific networks. I am referring to the documentation at
> http://docs.openstack.org/api/openstack-compute/2/content/CreateServers.htmlbut
>  do not see anything for this.
>
> I can achieve this using CLI but I need to use the REST API to achieve the
> same.
>
> Is this not implemented in Folsom? If so, would it be implemented in
> Grizzly?
>
> Thanks,
> Balu
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Assigning specific networks while creating instances using nova REST API in Folsom

[Balamurugan V G]

Hi,

I have a Folsom 2012.2 with Quantum and trying to create the instances
using the REST API as below:

curl  -X 'POST'
http://1.1.1.1:8774/v2/4a8c3029619e4afbaa39f85fcd121003/servers -d '{
"server": { "flavorRef": "6", "imageRef":
"dd13a38c-3e1f-49f1-afbe-c6f62cd46ffb", "name": "test" } }' -H 'Accept:
application/json' -H "X-Auth-Token: 1b5f64418cdf4a99a79aada03621cfa9" -H
'Content-type: application/json'

But this assigns the instance to all networks available for the tenant. So
if I have multiple networks for a tenant, how do I assign the instance to
specific networks. I am referring to the documentation at
http://docs.openstack.org/api/openstack-compute/2/content/CreateServers.htmlbut
do not see anything for this.

I can achieve this using CLI but I need to use the REST API to achieve the
same.

Is this not implemented in Folsom? If so, would it be implemented in
Grizzly?

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Images need to be stored in Glance or SWIFT?

[Balamurugan V G]

Ok, got some info at
http://docs.openstack.org/diablo/openstack-image-service/admin/content/configuring-the-swift-storage-backend.html
.

Looks like Glance supports multiple storage backends (Filesystem storage
being the default) and it can be configured to use SWIFT. So then SWIFT is
a complementary project for OpenStack and not really an absolute
requirement!

Regards,
Balu

On Thu, Mar 14, 2013 at 11:07 AM, Balamurugan V G
wrote:

> Hi,
>
> The OpenStack Installation document at
> http://docs.openstack.org/folsom/basic-install/content/ as well as the
> guide at
> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
>   do not talk about installing SWIFT. And in my setup (going by the install
> guide in git), I see that the images are stored in Glance. How does SWIFT
> come in to the picture, my understanding was that the Images will be stored
> in SWIFT and Glance is a catalog only.
>
> Can some one throw some light on how to use SWIFT? I need to create a
> multi site storage for Images and SWIFT can perhaps help me with it.
>
> Regards,
> Balu
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Images need to be stored in Glance or SWIFT?

[Balamurugan V G]

Hi,

The OpenStack Installation document at
http://docs.openstack.org/folsom/basic-install/content/ as well as the
guide at
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
 do not talk about installing SWIFT. And in my setup (going by the
install
guide in git), I see that the images are stored in Glance. How does SWIFT
come in to the picture, my understanding was that the Images will be stored
in SWIFT and Glance is a catalog only.

Can some one throw some light on how to use SWIFT? I need to create a multi
site storage for Images and SWIFT can perhaps help me with it.

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] VMWare ESXi plugin for Quantum

[Balamurugan V G]

Hi,

Do any of you know if there is anybody working on a Quantum plugin for
VMWare ESXi? And if yes, when it may be available?

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] How can I know the version if I installed from source code?

[Balamurugan V G]

Try this: 'nova-manage version'

Regards,
Balu

On Thu, Mar 7, 2013 at 7:37 PM, Martinx - ジェ�`ムズ
wrote:

> --version isn't working here (Openstack Folsom @ Ubuntu 12.04)  :-/
>
> *nova --version*
> Unknown, couldn't find versioninfo file at /usr/lib/python2.7/dist-
> packages/novaclient/versioninfo
>
>
> On 7 March 2013 00:09, Ray Sun  wrote:
>
>> Is there any method to get the openstack version if I installed from
>> openstack source code?
>>
>> Thanks a lot.
>>
>> - Ray
>> Best Regards
>>
>> CIeNET Technologies (Beijing) Co., Ltd
>> Technical Manager
>> Email: qsun01...@cienet.com.cn
>> Office Phone: +86-01081470088-7079
>> Mobile Phone: +86-13581988291
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] How to speed up the instance launch time?

[Balamurugan V G]

Yes it makes sense to have /var/lib/glance/images and
/var/lib/nova/instances/_base on the same network file system. But Quantum
network node being a bottle neck today, would the benefits be nullified by
a choked network?

Regards,
Balu

On Wed, Mar 6, 2013 at 9:42 PM, Mark Lehrer  wrote:

>
>  The change I made that helped the most was to disable NBD.  You have
>>>
>>
>> Was that to disable injection at startup?
>>
>
> No, NBD is just slow and unreliable for some reason.  Disabling it made
> my users happy.  I haven't had time to find out why NBD is so horrible.
>
> Eventually I would like to see /var/lib/glance/images and
> /var/lib/nova/instances/_base be on the same BTRFS file system and use
> reflink copies.
>
> Mark
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] How to speed up the instance launch time?

[Balamurugan V G]

Thanks for the responses and the link to pixelbeat. Its very helpful.

Start with QCOW, even before image is uploaded to Glance, dit help since
the image size camedown from 20Gb to 8+Gb. I even set the the
force_raw_images=False, and use_cow_images=True in nova.conf and restarted
nova services. I still see that the image is copied to _base and then
copied again to instances folder. This is probably expected and is the
caching feature. But under _base I see two files one with the underscore
suffix and one without. Does it mean that each time I launch an instance
with a diferent flavour(say disk set to 30Gb), another copy will be created
in _base?

root@openstack-kvm1:/var/lib/nova/instances# ls -l _base/ | grep
2b4a8e97317619077645de369a8f9fd63acd1f05
-rw-rw-r-- 1 nova nova  8691056640 Mar  5 19:23
2b4a8e97317619077645de369a8f9fd63acd1f05
-rw-rw-r-- 1 libvirt-qemu kvm   8691056640 Mar  5 19:23
2b4a8e97317619077645de369a8f9fd63acd1f05_20
root@openstack-kvm1:/var/lib/nova/instances#

Thanks for all the valuable suggestions. I'll explore the disk merging or
separate HDD options as well when possible.

Regards,
Balu




On Tue, Mar 5, 2013 at 6:09 PM, Sylvain Bauza wrote:

>  Another option is to merge both Glance and Nova datadirs on GlusterFS in
> distributed/replicated array.
> That way, all _base images and glance images are on the same "filesystem"
> but with distributed I/O.
>
> -Sylvain
>
>  Le 05/03/2013 13:10, Staicu Gabriel a écrit :
>
>  Hi,
>
> As a rule of thumb how I worked around this issue was to add a new hdd. I
> allocated this new hdd only to /var/lib/nova/instances/_base and the other
> hdd to /var/lib/nova/instances/ so in this manner to the first time a
> instance  is spawn on server the process use the full capacity of a hdd.
>
>  Regards,
> Gabriel
>
>
>    --
> *From:* Pádraig Brady  
> *To:* Balamurugan V G  
> *Cc:* openstack@lists.launchpad.net
> *Sent:* Tuesday, March 5, 2013 1:20 PM
> *Subject:* Re: [Openstack] [OpenStack] How to speed up the instance
> launch time?
>
> On 03/05/2013 11:03 AM, Balamurugan V G wrote:
> > Hi,
> >
> > I have a Folsom 2012.2 3 nodes setup like the one specified at
> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst.
> Each node has a 1Tb hard disk with no raid.
> >
> > Be it the image creation or the Instance creation, takes a long
> time(factor of the disk size of the image), about 15mins for a 20gb image.
> I can understand the slow image creation due to the http transfer of the
> file from a seperate web server hosting my images to the controller node.
> But even the instance creation takes that much or even a bit longer. I see
> that the image is copied from the Controller to Compute node and multiple
> copies are make in the compute node. So all this takes long an dis
> proportional to the image size. Is there any way to speed up this process?
> Is a SAN based backend the only way to go?
>
> It sounds like you're using raw images throughout?
> You might consider using qcow2 images in glance.
> Then you can avoid the conversion to raw in the libvirt base
> directory by setting force_raw_images=False in nova.conf
> That will avoid some of the initial caching penalty.
>
> Ensuring that you have use_cow_images=True set,
> with use CoW images for the instances and improve
> instance startup latency.
>
> Details of the operations and tradeoffs involved are at:
> http://www.pixelbeat.org/docs/openstack_libvirt_images/
>
> thanks,
> Pádraig.
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to: openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help  : https://help.launchpad.net/ListHelp
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Guest OS shows just one CPU core instead of two

[Balamurugan V G]

I initially did not have this setting in the nova.conf. I then read the
OpenStack docs and set it to as below and resstarted nova services and
re-created the instance but with same outcome.

libvirt_cpu_mode=host-passthrough

But I didnt have this issue with Windows Server 2012, it reported 2 virtal
CPUs correctly.

Regards,
Balu

On Tue, Mar 5, 2013 at 6:10 PM, Sylvain Bauza wrote:

>  Could you please tell us what is your libvirt_cpu_model ?
> Please check both nova.conf and instance's libvirt.xml.
>
> -Sylvain
>
> Le 05/03/2013 11:30, Balamurugan V G a écrit :
>
> Hi,
>
> I am running Folsom 2.2 with a KVM compute node. When I launch a windows
> instance with flavor that has 2 VCPUs and 2Gb RAM, the guest seems the RAM
> fine but not the 2 CPUs. It reports only one Virtual processor. Whne I look
> at the command line options with which KVM has launched the instance, I see
> that in -smp argument, sockets is set to 2 and core is set to 1. How can I
> get the core to be 2 so that the guest OS can see it?
>
>
> 107   7764 1 14 14:35 ?00:11:27 /usr/bin/kvm -name
> instance-000e -S -M pc-1.0 -cpu
> core2duo,+lahf_lm,+osxsave,+xsave,+sse4.1,+dca,+pdcm,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds
> -enable-kvm -m 2048* -smp 2,sockets=2,cores=1,threads=1* -uuid
> cd6dd64c-d792-4b31-92bf-ed8ad1ea46cb -nodefconfig -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-000e.monitor,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device
> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
> file=/var/lib/nova/instances/instance-000e/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -netdev tap,fd=24,id=hostnet0 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:46:68:2e,bus=pci.0,addr=0x3
> -chardev
> file,id=charserial0,path=/var/lib/nova/instances/instance-000e/console.log
> -device isa-serial,chardev=charserial0,id=serial0 -chardev
> pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1
> -device usb-tablet,id=input0 -vnc 0.0.0.0:3 -k en-us -vga cirrus -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
> root@openstack-kvm1:~#
>
>
>
> Regards,
> Balu
>
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Guest OS shows just one CPU core instead of two

[Balamurugan V G]

I had Windows 8 64bit which shows just 1 Virtual Core and 1 Socket in the
task manager->Performance->CPU tab. I then tried Windows Server 2012 which
shows 2 sockets and 2 Virtual Cores for the same flavor. So it must be some
compatibility issue with KVM and certain versions of Windows.

Thanks for the response.

Regards,
Balu

On Tue, Mar 5, 2013 at 6:19 PM, Daniel P. Berrange wrote:

> On Tue, Mar 05, 2013 at 04:00:06PM +0530, Balamurugan V G wrote:
> > Hi,
> >
> > I am running Folsom 2.2 with a KVM compute node. When I launch a windows
> > instance with flavor that has 2 VCPUs and 2Gb RAM, the guest seems the
> RAM
> > fine but not the 2 CPUs. It reports only one Virtual processor. Whne I
> look
> > at the command line options with which KVM has launched the instance, I
> see
> > that in -smp argument, sockets is set to 2 and core is set to 1. How can
> I
> > get the core to be 2 so that the guest OS can see it?
>
> There's nothing wrong with what the command line set here. It is
> simply configuring 2 vCPUS where each vCPU is represented as a
> separate socket to the guest, rather than what you describe which
> would be 1 socket with dual-cores.
>
> You don't mention what Windows version you are using, but some versions
> are not clever enough to switch between a uniprocessor config and SMP
> config. So if you installed those versions on a 1 CPU guest, then even
> if you later boot the image on 1 CPU guest, it won't see the extra CPUs.
> There are hacks you can do to "upgrade" a windows install from the
> uniprocessor to multiprocessor HAL - see the microsoft kbase for more
> info
>
> Regards,
> Daniel
> --
> |: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/:|
> |: http://libvirt.org  -o- http://virt-manager.org:|
> |: http://autobuild.org   -o- http://search.cpan.org/~danberr/:|
> |: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc:|
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] How to speed up the instance launch time?

[Balamurugan V G]

Thanks for the response. I have the images as .img in the web server which
is external to OpenStack nodes. But while I create the image in Horizon, I
set the format to QCOW2. So once th image is created it shows as QCOW2.
Then the instance is launched from this QCOW2 image.

Do you mean that I original image should also be QCOW2?

I will also try the settings which you recommended.

Regards,
Balu

On Tue, Mar 5, 2013 at 4:50 PM, Pádraig Brady  wrote:

> On 03/05/2013 11:03 AM, Balamurugan V G wrote:
> > Hi,
> >
> > I have a Folsom 2012.2 3 nodes setup like the one specified at
> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst.
> Each node has a 1Tb hard disk with no raid.
> >
> > Be it the image creation or the Instance creation, takes a long
> time(factor of the disk size of the image), about 15mins for a 20gb image.
> I can understand the slow image creation due to the http transfer of the
> file from a seperate web server hosting my images to the controller node.
> But even the instance creation takes that much or even a bit longer. I see
> that the image is copied from the Controller to Compute node and multiple
> copies are make in the compute node. So all this takes long an dis
> proportional to the image size. Is there any way to speed up this process?
> Is a SAN based backend the only way to go?
>
> It sounds like you're using raw images throughout?
> You might consider using qcow2 images in glance.
> Then you can avoid the conversion to raw in the libvirt base
> directory by setting force_raw_images=False in nova.conf
> That will avoid some of the initial caching penalty.
>
> Ensuring that you have use_cow_images=True set,
> with use CoW images for the instances and improve
> instance startup latency.
>
> Details of the operations and tradeoffs involved are at:
> http://www.pixelbeat.org/docs/openstack_libvirt_images/
>
> thanks,
> Pádraig.
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] How to speed up the instance launch time?

[Balamurugan V G]

Hi,

I have a Folsom 2012.2 3 nodes setup like the one specified at
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst.
Each node has a 1Tb hard disk with no raid.

Be it the image creation or the Instance creation, takes a long time(factor
of the disk size of the image), about 15mins for a 20gb image. I can
understand the slow image creation due to the http transfer of the file
from a seperate web server hosting my images to the controller node. But
even the instance creation takes that much or even a bit longer. I see that
the image is copied from the Controller to Compute node and multiple copies
are make in the compute node. So all this takes long an dis proportional to
the image size. Is there any way to speed up this process? Is a SAN based
backend the only way to go?

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Guest OS shows just one CPU core instead of two

[Balamurugan V G]

Hi,

I am running Folsom 2.2 with a KVM compute node. When I launch a windows
instance with flavor that has 2 VCPUs and 2Gb RAM, the guest seems the RAM
fine but not the 2 CPUs. It reports only one Virtual processor. Whne I look
at the command line options with which KVM has launched the instance, I see
that in -smp argument, sockets is set to 2 and core is set to 1. How can I
get the core to be 2 so that the guest OS can see it?


107   7764 1 14 14:35 ?00:11:27 /usr/bin/kvm -name
instance-000e -S -M pc-1.0 -cpu
core2duo,+lahf_lm,+osxsave,+xsave,+sse4.1,+dca,+pdcm,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds
-enable-kvm -m 2048* -smp 2,sockets=2,cores=1,threads=1* -uuid
cd6dd64c-d792-4b31-92bf-ed8ad1ea46cb -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-000e.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/var/lib/nova/instances/instance-000e/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=24,id=hostnet0 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:46:68:2e,bus=pci.0,addr=0x3
-chardev
file,id=charserial0,path=/var/lib/nova/instances/instance-000e/console.log
-device isa-serial,chardev=charserial0,id=serial0 -chardev
pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1
-device usb-tablet,id=input0 -vnc 0.0.0.0:3 -k en-us -vga cirrus -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
root@openstack-kvm1:~#



Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Rebooted, now can't ping my guest

[Balamurugan V G]

It says its fixed in quantum
2012.2.3as well.
How do we get 2012.3 in Ubuntu 12.04?

Regrads,
Balu

On Fri, Mar 1, 2013 at 8:51 PM, Brad Knowles wrote:

> On Mar 1, 2013, at 9:11 AM, Sylvain Bauza 
> wrote:
>
> > There is a known bug for the network bridges, when rebooting :
> > https://bugs.launchpad.net/quantum/+bug/1091605
>
> Hmm.  Reading that page, it's not clear to me exactly where this bug is
> actually fixed.  From what I can tell, it looks like it was rolled into
> grizzly-2, but was it ever actually backported to Folsom?
>
> It looks like that was the intent but then perhaps it was never done.  I
> dunno.  I'm new at reading these bug reports, so I'm trying to understand
> exactly what the current status is.
>
> Thanks!
>
> --
> Brad Knowles 
> Senior Consultant
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack] Memory use in Controller and Compute nodes

[Balamurugan V G]

Never mind, Looks like I should be looking at this line which gives the
correct usage which is more or less what I expect.

-/+ buffers/cache:   2009  30163

Regards,
Balu


On Thu, Feb 28, 2013 at 10:18 AM, Balamurugan V G
wrote:

> Hi,
>
> I have a 3 node Folsom with Quantum setup. One is a controller node, one
> is a quantum networking node and the other is a  KVM compute node. I see
> that on the Controller and Compute nodes, the memory usage is very high,
> based on the free command output. I have about 8gb RAM in the controller
> node and 32gb in the Compute node.  For example the compute node returns
> this:
>
> root@openstack-kvm1:~# free -m
>  total   used   free sharedbuffers cached
> Mem: 32173  31619553  0115  29494
> -/+ buffers/cache:   2009  30163
> Swap:0  0  0
> root@openstack-kvm1:~#
>
>
> I am not sure if my interpretation if the output is wrong or if I have a
> genuine memory issue. Any pointers will help.
>
> Thanks,
> Balu
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Back porting the floating ip related changes to Folsom

[Balamurugan V G]

Hi,

We know that in Folsom Horizon, though there is interface for Floating ip
association/disassociation, it doesnt work due to missing integration in
Nova. But in the Grizzly, based on the release notes, this seems to have
been implemented. Can this feature can be back ported to Folsom? has
anybody tried it?

I came across this port
http://cloudistic.me/blog/openstack-folsom-backporting-quantum-floating-ips-to-nova-on-ubuntu-12-04/but
wanted to check with the community before trying it since I do not
have
much flexibility to play with my setup(dont want to mess up my current
setup). Has anybody tried this?

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack] Memory use in Controller and Compute nodes

[Balamurugan V G]

Hi,

I have a 3 node Folsom with Quantum setup. One is a controller node, one is
a quantum networking node and the other is a  KVM compute node. I see that
on the Controller and Compute nodes, the memory usage is very high, based
on the free command output. I have about 8gb RAM in the controller node and
32gb in the Compute node.  For example the compute node returns this:

root@openstack-kvm1:~# free -m
 total   used   free sharedbuffers cached
Mem: 32173  31619553  0115  29494
-/+ buffers/cache:   2009  30163
Swap:0  0  0
root@openstack-kvm1:~#


I am not sure if my interpretation if the output is wrong or if I have a
genuine memory issue. Any pointers will help.

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] multiple public ip

[Balamurugan V G]

"The doc cited explains how this works with Quantum, but not with
Openstack."
-As of Folsom, you have the option of using Quantum for networking or Nova
Network and I believe Nova network will eventually be deprecated.

"VM1 is shown as being accessible via two VNICs, that implies that their is
a Hypervisor that is available by two NICs"
-There can be any number of vNICs while using just one physical NIC. Each
port created in quantum is a vNIC. However the illustration showed 3
physical NICs all of which could have been on a single hypervisor or each
on it sown hypervisor.

Looks like we are deviating from the original question which was posed by
Umar.

Regards,
Balu

On Thu, Jan 31, 2013 at 11:18 PM, Caitlin Bestler <
caitlin.best...@nexenta.com> wrote:

> The doc cited explains how this works with Quantum, but not with Openstack.
>
> VM1 is shown as being accessible via two VNICs, that implies that their is
> a Hypervisor that is available by two NICs. How does Nova know that this is
> in fact one Hypervisor and not two?
>
> Similar question must be addressed for Cinder and Swift. I am most
> familiar with Swift, and it really does not address this situation.
>
>
> Balamurugan V G  wrote:
>
> Perhaps you can use the multiple flat network model shown here:
>
>
> http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_multi_flat.html
>
> The TenantC VM1 gets two IPs, one from each net. But in this case each net
> is in a different subnet.
>
> May be you can create the nets for the same subet but with diff ranges or
> even just one IP(/32) and disable DHCP.
>
> Basically the idea is to use multiple vNICs.
>
> Just throwing at you, I am not entirely sure if it will work, I havent
> tried it.
>
> Regards,
> Balu
>
> On Thu, Jan 31, 2013 at 1:51 PM, Umar Draz  wrote:
>
>> Hi Vish,
>>
>> Assign direct/static IP address to Instance something like bridge rather
>> than nating is possible? Same like vSphare
>>
>> Best Regards,
>>
>> Umar
>> On Thu, Jan 31, 2013 at 8:37 AM, Vishvananda Ishaya <
>> vishvana...@gmail.com> wrote:
>>
>>>
>>> On Jan 30, 2013, at 11:35 AM, Umar Draz  wrote:
>>>
>>> > Hi Caitlin,
>>> >
>>> > I need multiple ip address for my Haproxy server.
>>> >
>>> > Here is my senario
>>> >
>>> > I have already running Haproxy Server virtual machine for web load
>>> balancing on vSphare with 45 public ip address. We are running 45 diffrent
>>> websites and we required diffrent ips for each webiste.
>>> >
>>> > We have 6 webservers with only local ip address. These 6 webservers
>>> holding all 45 websites. Haproxy just forward the request to local
>>> webservers accorindg to DNS.
>>>
>>> You can associate multiple floating ips to a single instance. Floating
>>> ips just create natting entries. Keep in mind that traffic that originates
>>> from the server will only come from one of these ips.  Also there is no way
>>> for the server to determine which ip address the traffic came in on so you
>>> will need to do the forwarding at the HTTP layer which has access to the
>>> domain name used for the request.
>>>
>>> Vish
>>>
>>>
>>
>>
>> --
>> Umar Draz
>> Network Architect
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] multiple public ip

[Balamurugan V G]

Perhaps you can use the multiple flat network model shown here:

http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_multi_flat.html

The TenantC VM1 gets two IPs, one from each net. But in this case each net
is in a different subnet.

May be you can create the nets for the same subet but with diff ranges or
even just one IP(/32) and disable DHCP.

Basically the idea is to use multiple vNICs.

Just throwing at you, I am not entirely sure if it will work, I havent
tried it.

Regards,
Balu

On Thu, Jan 31, 2013 at 1:51 PM, Umar Draz  wrote:

> Hi Vish,
>
> Assign direct/static IP address to Instance something like bridge rather
> than nating is possible? Same like vSphare
>
> Best Regards,
>
> Umar
> On Thu, Jan 31, 2013 at 8:37 AM, Vishvananda Ishaya  > wrote:
>
>>
>> On Jan 30, 2013, at 11:35 AM, Umar Draz  wrote:
>>
>> > Hi Caitlin,
>> >
>> > I need multiple ip address for my Haproxy server.
>> >
>> > Here is my senario
>> >
>> > I have already running Haproxy Server virtual machine for web load
>> balancing on vSphare with 45 public ip address. We are running 45 diffrent
>> websites and we required diffrent ips for each webiste.
>> >
>> > We have 6 webservers with only local ip address. These 6 webservers
>> holding all 45 websites. Haproxy just forward the request to local
>> webservers accorindg to DNS.
>>
>> You can associate multiple floating ips to a single instance. Floating
>> ips just create natting entries. Keep in mind that traffic that originates
>> from the server will only come from one of these ips.  Also there is no way
>> for the server to determine which ip address the traffic came in on so you
>> will need to do the forwarding at the HTTP layer which has access to the
>> domain name used for the request.
>>
>> Vish
>>
>>
>
>
> --
> Umar Draz
> Network Architect
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Multi-site OpenStack deployments

[Balamurugan V G]

Hi,

Is there a recommended way to deploy OpenStack at multiple sites/data
centers? Basically I want to have just one cluster of SWIFT, Glance etc so
that the images do not have to be maintained by me and I can still deploy
those images on compute nodes at any site.

Any thoughts on this will be helpful.

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] What scheduler should be used while using availability_zones

[Balamurugan V G]

Hi,

I have two compute nodes in my setup each one is separate zones. I am using
the following setting in the nova.conf.

 scheduler_driver=nova.scheduler.simple.SimpleScheduler

But when I launch instance and specify a zone, i still see that some times
it creates the instance in the wrong zone. Could this be due to the
scheduler? What scheduler should I use for this?

I want a deterministic way to create instances in specific zones.

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] I dont see authentication being handled while copying images from glance to esxi

[Balamurugan V G]

HI,

In the file
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/read_write_util.py,
the code which copying the image from Glance to the ESXi datastore doesnt
seem to handle the authentication.

class VMWareHTTPWriteFile(VMwareHTTPFile):
"""VMWare file write handler class."""

def __init__(self, host, data_center_name, datastore_name, cookies,
 file_path, file_size, scheme="https"):
base_url = "%s://%s/folder/%s" % (scheme, host, file_path)
param_list = {"dcPath": data_center_name, "dsName": datastore_name}
base_url = base_url + "?" + urllib.urlencode(param_list)
_urlparse = urlparse.urlparse(base_url)
scheme, netloc, path, params, query, fragment = _urlparse
if scheme == "http":
conn = httplib.HTTPConnection(netloc)
elif scheme == "https":
conn = httplib.HTTPSConnection(netloc)
conn.putrequest("PUT", path + "?" + query)
conn.putheader("User-Agent", USER_AGENT)
conn.putheader("Content-Length", file_size)
conn.putheader("Cookie", self._build_vim_cookie_headers(cookies))
conn.endheaders()
self.conn = conn
VMwareHTTPFile.__init__(self, conn)


Can some one enlighten me on how this works? When I manually tried the same
using curl and provided the username/password, the file upload worked just
fine. But when I create an instance in OpenStack, the image copy to ESXi is
not working.

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack Folsom Release

[Balamurugan V G]

Follow this guide.

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

Regards,
Balu

On Fri, Jan 25, 2013 at 10:24 AM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:

> Hi-
>
> How to Download the Openstack Folsom Release and setup the openstack
> environment.
>
> I see that, the Code base I have a week back which installed for Folsom
> release is not there today using the same apt-get.
>
> How to get the code base stable one of folsom release
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Compute node is unable to copy image from Glance to ESXi

[Balamurugan V G]

Hi,

I have a two node Folsom Setup(with Quantum) where one nodes runs all
services(including KVM) and the other is a compute node for ESXi 5.1. When
I try creating an instance on the ESXi, the compute node is  unable to copy
the image from glance to the ESXi. Though the call to fetch_image in
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmware_images.py is
triggered, the actual copy doesnt seem to happen. The file is created in
the ESXi datastore but the size remains zero.

Any help is greatly appreciated.

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Windows instance licensing in OpenStack

[Balamurugan V G]

Thanks for the inputs everyone.

My concern is if the activation/licence key input needs to be done on each
VM after they boot up or its just as simple as having as many licences as
the VMs before hand and nothing needs to be done after the instance boots
up.

Regards,
Balu

On Wed, Jan 23, 2013 at 10:31 PM, Peter Pouliot wrote:

> Ok,
>
> I am no MS licensing expert, however.   Here is my understanding of it.
>
> If you are using a windows vm on a hypervisor other than windows server
> with the Hyper-V role enabled you need to license per vm.
>
>
>
> If you are using windows server with Hyper-V enable you can license at the
> hypervisor/server rather than at the vm level.
>
> This does not include Hyper-V server, which only requires licensing of the
> windows guests.
>
> p
>
>
>
> Peter J. Pouliot, CISSP
> Senior SDET, OpenStack
>
> Microsoft
> New England Research & Development Center
> One Memorial Drive,Cambridge, MA 02142
> ppoul...@microsoft.com | Tel: +1(857) 453 6436
>
> -Original Message-
> From: openstack-bounces+ppouliot=microsoft@lists.launchpad.net[mailto:
> openstack-bounces+ppouliot=microsoft@lists.launchpad.net] On Behalf
> Of Jay Pipes
> Sent: Wednesday, January 23, 2013 9:31 AM
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Windows instance licensing in OpenStack
>
> On 01/23/2013 08:41 AM, Balamurugan V G wrote:
> > Hi,
> >
> > I wonder how the Windows Licensing would work in OpenStack. Lets say I
> > have a Windows Image which I have already activated. Now if I launch N
> > instances of this image, what are the SO licensing implications? Will I
> > have to license/re-activate on each of the instances after they boot up?
>
> If you use XenServer or KVM, I believe so, yes. I've heard that if you
> use ESXi you can get some sort of license for all Windows images on a
> host. Not sure of the details of this, though, I've just heard it
> through the IT grapevine...
>
> Best,
> -jay
>
> p.s. If you find out any more solid info, please do post back :)
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack with ESXi - NetworkNotFoundForBridge: Network could not be found for bridge

[Balamurugan V G]

When i temporarily hard code the network_name variable in
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py as below:

def _get_vif_infos():
vif_infos = []
for (network, mapping) in network_info:
mac_address = mapping['mac']
#Balu
#network_name = network['bridge']
network_name = 'br-eth1'

The instance creation proceeds and then errors for another reason as shown
below:

2013-01-23 08:35:12 DEBUG nova.virt.vmwareapi.read_write_util
[req-ec9d0530-ca3d-4a8e-8166-834f6e11ed32 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] Exception during HTTP connection close in
VMWareHTTpWrite. Exception is '' from (pid=14354) close
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/read_write_util.py:146
2013-01-23 08:35:12 DEBUG nova.virt.vmwareapi.vmware_images
[req-ec9d0530-ca3d-4a8e-8166-834f6e11ed32 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] [instance:
6a0bfd1b-e4c4-4430-8898-312e73decd62] Downloaded image
4d70a998-a51e-4557-81fa-23747db12305 from glance image server from
(pid=14354) fetch_image
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmware_images.py:109
2013-01-23 08:35:12 DEBUG nova.virt.vmwareapi.read_write_util
[req-ec9d0530-ca3d-4a8e-8166-834f6e11ed32 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] Exception during HTTP connection close in
VMWareHTTpWrite. Exception is  from (pid=14354) close
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/read_write_util.py:146
2013-01-23 08:35:12 DEBUG nova.virt.vmwareapi.vmops
[req-ec9d0530-ca3d-4a8e-8166-834f6e11ed32 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] [instance:
6a0bfd1b-e4c4-4430-8898-312e73decd62] Downloaded image file data
4d70a998-a51e-4557-81fa-23747db12305 to the ESX data store datastore1 from
(pid=14354) _fetch_image_on_esx_datastore
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py:308
2013-01-23 08:35:19 DEBUG nova.virt.vmwareapi.vmops
[req-ec9d0530-ca3d-4a8e-8166-834f6e11ed32 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] [instance:
6a0bfd1b-e4c4-4430-8898-312e73decd62] Reconfiguring VM instance to attach
the image disk from (pid=14354) _attach_vmdk_to_the_vm
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py:323
2013-01-23 08:35:27 WARNING nova.virt.vmwareapi.driver [-] Task
[ReconfigVM_Task] (returnval){
   value = "haTask-23-vim.VirtualMachine.reconfigure-449287255"
   _type = "Task"
 } status: error Unable to access file
/vmfs/volumes/5088d916-58b2aa06-6a35-d4ae52a0f879/instance-003f/instance-003f.vmdk
2013-01-23 08:35:27 ERROR nova.compute.manager
[req-ec9d0530-ca3d-4a8e-8166-834f6e11ed32 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] [instance:
6a0bfd1b-e4c4-4430-8898-312e73decd62] Instance failed to spawn


The file actually exists on the ESXi Server, but its size is just a few
bytes. So looks like it was still copying when it aborted. There are a few
exception in VMWareHTTpWrite as well.

So there are two issues:
   1. Its not picking up the bridge name
   2. Unable to access(or copy) the vmdk instance file

Regards,
Balu
On Wed, Jan 23, 2013 at 4:08 PM, Balamurugan V G wrote:

> I see that there is no value being passed for 'bridge'. The snippet from
> the nova-compute log just before the Execption is below:
>
>
> 2013-01-23 02:33:37 DEBUG nova.compute.manager
> [req-9c972e4e-3f8b-4cc3-b151-963b71f0b9a2 9ac7dbe62fb349ce84927598a0f54d68
> b439758af3814f739fe7ab09b98a0120] [instance:
> ad7a8f84-f303-4733-9822-2e81b7cbc407] Instance network_info:
> |[VIF({'network': Network({*'bridge': '',* 'subnets': [Subnet({'ips':
> [FixedIP({'meta': {}, 'version': 4, 'type': 'fixed', 'floating_ips': [],
> 'address': u'50.50.1.4'})], 'version': 4, 'meta': {'dhcp_server':
> u'50.50.1.2'}, 'dns': [], 'routes': [], 'cidr': u'50.50.1.0/24',
> 'gateway': IP({'meta': {}, 'version': 4, 'type': 'gateway', 'address':
> u'50.50.1.1'})})], 'meta': {'injected': False, 'tenant_id':
> u'b439758af3814f739fe7ab09b98a0120'}, 'id':
> u'dcef8ce4-dff0-4a54-9112-9695c28c02d5', 'label': u'net1'}), 'meta': {},
> 'id': u'0c68ea85-b289-486e-bdaf-999bc35256a9', 'address':
> u'fa:16:3e:45:e5:6b'})]| from (pid=13103) _allocate_network
> /usr/lib/python2.7/dist-packages/nova/compute/manager.py:715
>
> What could be going wrong here?
>
> Regards,
> Balu
>
> On Wed, Jan 23, 

[Openstack] Windows instance licensing in OpenStack

[Balamurugan V G]

Hi,

I wonder how the Windows Licensing would work in OpenStack. Lets say I have
a Windows Image which I have already activated. Now if I launch N instances
of this image, what are the SO licensing implications? Will I have to
license/re-activate on each of the instances after they boot up?

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Unable to create a vm

[Balamurugan V G]

Try this as well:

chown root:kvm /dev/kvm

-Balu

On Wed, Jan 23, 2013 at 4:51 PM, Razique Mahroua
wrote:

> Ok,
> now :
>
> sudo modprobe kvm
> sudo modprobe kvm-intel
>
>
> You should be good I think
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 23 janv. 2013 à 10:34, Alexandre De Carvalho <
> alexandre7.decarva...@gmail.com> a écrit :
>
> Hi Razique,
>
> I ran this command :
>
> alex@alex-X9SCD:~$ egrep '^flags.*(vmx|svm)' /proc/cpuinfo
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx
> f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
> flexpriority ept vpid fsgsbase smep erms
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx
> f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
> flexpriority ept vpid fsgsbase smep erms
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx
> f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
> flexpriority ept vpid fsgsbase smep erms
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx
> f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
> flexpriority ept vpid fsgsbase smep erms
> alex@alex-X9SCD:~$
>
>
>
>
> Alex
>
>
> 2013/1/22 Razique Mahroua 
>
>> Hi Alexandre,
>> can you run the following command?
>>
>> egrep '^flags.*(vmx|svm)' /proc/cpuinfo
>>
>>
>> thanks !
>>
>> *Razique Mahroua** - **Nuage & Co*
>> razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>> 
>>
>> Le 22 janv. 2013 à 22:35, Alexandre De Carvalho <
>> alexandre7.decarva...@gmail.com> a écrit :
>>
>> Hi,
>>
>> I have this problem when i want to create a vm.
>>
>> Could not access KVM kernel module: Permission denied failed to
>> initialize
>> KVM: Permission denied
>> No accelerator found!
>>
>> Can you help me, please ?
>>
>> best regards,
>> Alexandre
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>
>
> --
> Cordialement,
> Alexandre DE CARVALHO
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack with ESXi - NetworkNotFoundForBridge: Network could not be found for bridge

[Balamurugan V G]

I see that there is no value being passed for 'bridge'. The snippet from
the nova-compute log just before the Execption is below:


2013-01-23 02:33:37 DEBUG nova.compute.manager
[req-9c972e4e-3f8b-4cc3-b151-963b71f0b9a2 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] [instance:
ad7a8f84-f303-4733-9822-2e81b7cbc407] Instance network_info:
|[VIF({'network': Network({*'bridge': '',* 'subnets': [Subnet({'ips':
[FixedIP({'meta': {}, 'version': 4, 'type': 'fixed', 'floating_ips': [],
'address': u'50.50.1.4'})], 'version': 4, 'meta': {'dhcp_server':
u'50.50.1.2'}, 'dns': [], 'routes': [], 'cidr': u'50.50.1.0/24', 'gateway':
IP({'meta': {}, 'version': 4, 'type': 'gateway', 'address':
u'50.50.1.1'})})], 'meta': {'injected': False, 'tenant_id':
u'b439758af3814f739fe7ab09b98a0120'}, 'id':
u'dcef8ce4-dff0-4a54-9112-9695c28c02d5', 'label': u'net1'}), 'meta': {},
'id': u'0c68ea85-b289-486e-bdaf-999bc35256a9', 'address':
u'fa:16:3e:45:e5:6b'})]| from (pid=13103) _allocate_network
/usr/lib/python2.7/dist-packages/nova/compute/manager.py:715

What could be going wrong here?

Regards,
Balu

On Wed, Jan 23, 2013 at 1:08 PM, Balamurugan V G wrote:

> Hi,
>
> I have a two node OpenStack Folsom Setup. One node runs all services with
> KVM. The other nodes is a Compute Node for ESXi 5.1. I have set the
> availabality_zones for each of this so that I can schedule instances as per
> my need. I am able to operate the instances on the KVM just fine. But when
> I launch an instance for ESXi, it goes to ERROR state with the error
> 'NetworkNotFoundForBridge: Network could not be found for bridge'.
>
> After the vanilla Folsom installation, I was getting an AttribueError
> which got fixed after applying the patch at
> https://bugs.launchpad.net/nova/+bug/1063885
>
> But then after that, I am seeing this error.
>
> root@openstack-kvm:~# nova show 8110c50c-ed26-48dd-886b-71b44ee382dd
>
> +-+-+
> | Property| Value
>
>   |
>
> +-+-+
> | OS-DCF:diskConfig   | MANUAL
>
>  |
> | OS-EXT-SRV-ATTR:host| openstack-esxi
>
>  |
> | OS-EXT-SRV-ATTR:hypervisor_hostname | None
>
>  |
> | OS-EXT-SRV-ATTR:instance_name   | instance-0016
>
>   |
> | OS-EXT-STS:power_state  | 0
>
>   |
> | OS-EXT-STS:task_state   | None
>
>  |
> | OS-EXT-STS:vm_state | error
>
>   |
> | accessIPv4  |
>
>   |
> | accessIPv6  |
>
>   |
> | config_drive|
>
>   |
> | created | 2013-01-23T07:13:11Z
>
>  |
> | fault   | {u'message':
> u'NetworkNotFoundForBridge', u'code': 404, u'details': u'Network could not
> be found for bridge ', u'created': u'2013-01-23T07:13:14Z'} |
> | flavor  | m1.tiny (6)
>
>   |
> | hostId  |
> a9edbd6bb1136ff3bcf5225d1f6a34e0d18cc21eb9837acd67dec105
>  |
> | id  |
> 8110c50c-ed26-48dd-886b-71b44ee382dd
>  |
> | image   | Ubuntu1204
> (4d70a998-a51e-4557-81fa-23747db12305)
>   |
> | key_name| None
>
>  

[Openstack] Openstack with ESXi - NetworkNotFoundForBridge: Network could not be found for bridge

[Balamurugan V G]

Hi,

I have a two node OpenStack Folsom Setup. One node runs all services with
KVM. The other nodes is a Compute Node for ESXi 5.1. I have set the
availabality_zones for each of this so that I can schedule instances as per
my need. I am able to operate the instances on the KVM just fine. But when
I launch an instance for ESXi, it goes to ERROR state with the error
'NetworkNotFoundForBridge: Network could not be found for bridge'.

After the vanilla Folsom installation, I was getting an AttribueError which
got fixed after applying the patch at
https://bugs.launchpad.net/nova/+bug/1063885

But then after that, I am seeing this error.

root@openstack-kvm:~# nova show 8110c50c-ed26-48dd-886b-71b44ee382dd
+-+-+
| Property| Value

|
+-+-+
| OS-DCF:diskConfig   | MANUAL

 |
| OS-EXT-SRV-ATTR:host| openstack-esxi

 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None

 |
| OS-EXT-SRV-ATTR:instance_name   | instance-0016

|
| OS-EXT-STS:power_state  | 0

|
| OS-EXT-STS:task_state   | None

 |
| OS-EXT-STS:vm_state | error

|
| accessIPv4  |

|
| accessIPv6  |

|
| config_drive|

|
| created | 2013-01-23T07:13:11Z

 |
| fault   | {u'message':
u'NetworkNotFoundForBridge', u'code': 404, u'details': u'Network could not
be found for bridge ', u'created': u'2013-01-23T07:13:14Z'} |
| flavor  | m1.tiny (6)

|
| hostId  |
a9edbd6bb1136ff3bcf5225d1f6a34e0d18cc21eb9837acd67dec105
 |
| id  |
8110c50c-ed26-48dd-886b-71b44ee382dd
 |
| image   | Ubuntu1204
(4d70a998-a51e-4557-81fa-23747db12305)
  |
| key_name| None

 |
| metadata| {}

 |
| name| VM2

|
| security_groups | [{u'name': u'default'}]

|
| status  | ERROR

|
| tenant_id   | b439758af3814f739fe7ab09b98a0120

 |
| updated | 2013-01-23T07:13:14Z

 |
| user_id | 9ac7dbe62fb349ce84927598a0f54d68

 |
+-+-+
root@openstack-kvm:~#

My /etc/nova/nova.conf on the ESXi compute nodes is:

[DEFAULT]
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/run/lock/nova
verbose=True
api_paste_config=/etc/nova/api-paste.ini
scheduler_driver=nova.scheduler.simple.SimpleScheduler
s3_host=10.5.3.230
ec2_host=10.5.3.230
ec2_dmz_host=10.5.3.230
rabbit_host=10.5.3.230
cc_host=10.5.3.230
dmz_cidr=169.254.169.254/32
metadata_host=10.5.3.230
metadata_listen=0.0.0.0
nova_url=http://10.5.3.230:8774/v1.1/
sql_connection=mysql://novaUser:novaPass@10.5.3.230/nova
ec2_url=http://10.5.3.230:8773/services/Cloud
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
my_ip=10.5.3.231

# Auth
use_deprecated_auth=false
auth_strategy=keystone
keystone_ec2_url=http://10.5.3.230:5000/v2.0/ec2tokens
# Imaging service
glance_api_servers=10.5.3.230:9292
image_service=nova.image.glance.GlanceImageService

# Vnc configuration
novnc_enabled=true
novncproxy_base_url=http://10.5.12.20:6080/vnc_auto.html
novncproxy_port=6080
vncserver_proxyclient_address=10.5.12.20
vncserver_listen=0.0.0.0

# Network settings
network_api_class=nova.network.quantumv2.api.API
quantum_url=http://10.5.3

Re: [Openstack] Bypassing the keypair in Folsom

[Balamurugan V G]

My ssh debug logs are below:

$ ssh -vvv root@1.1.1.1
OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 1.1.1.1 [1.1.1.1] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/balu/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /home/balu/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/balu/.ssh/id_rsa-cert type -1
debug1: identity file /home/balu/.ssh/id_dsa type -1
debug1: identity file /home/balu/.ssh/id_dsa-cert type -1
debug1: identity file /home/balu/.ssh/id_ecdsa type -1
debug1: identity file /home/balu/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1
Debian-5ubuntu1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "1.1.1.1" from file
"/home/balu/.ssh/known_hosts"
debug3: load_hostkeys: loaded 0 keys
debug1: SSH2_MSG_KEXINIT sent
Connection closed by 1.1.1.1

Regards,
Balu

On Tue, Jan 22, 2013 at 10:31 PM, Balamurugan V G
wrote:

> Yes but I want to skip this feature of keypairs. I want to be able to SSH
> with out needing the keypairs since security is not a concern in my private
> cloud.
>
> Thanks,
> Balu
>
> On Tue, Jan 22, 2013 at 10:29 PM, JuanFra Rodriguez Cardoso <
> juanfra.rodriguez.card...@gmail.com> wrote:
>
>> Hi Balu:
>>
>> Before launching an instance, you have to create a keypair
>> (YOUR_DASHBOARD_IP/dashboard/nova/access_and_security/).
>> Then, next time you launch an instance, you can choose that keypair
>> created previously.
>>
>> Regards,
>> JuanFra.
>>
>> 2013/1/22 Balamurugan V G 
>>
>>> Hi,
>>>
>>> I have a Folsom private openstack cloud in which security is not a
>>> concern. That is I dont really need the security groups and keypairs etc
>>> offered by openstack. So all my instances are launched as part of the
>>> default security group. I have even allowed all TCP and UDP ports(1 to
>>> 65535) and ICMP.
>>>
>>> But when I try to SSH to the floating IP assigned to a Ubuntu instance,
>>> I get connection refused. When I so 'ssh -vvv', I can see that the
>>> connection is getting establish but is getting terminated. It seems due to
>>> missing key pair.
>>>
>>> Is there a way to bypass the keypairs.
>>>
>>> Regards,
>>> Balu
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> JuanFra
>>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Bypassing the keypair in Folsom

[Balamurugan V G]

Yes but I want to skip this feature of keypairs. I want to be able to SSH
with out needing the keypairs since security is not a concern in my private
cloud.

Thanks,
Balu

On Tue, Jan 22, 2013 at 10:29 PM, JuanFra Rodriguez Cardoso <
juanfra.rodriguez.card...@gmail.com> wrote:

> Hi Balu:
>
> Before launching an instance, you have to create a keypair
> (YOUR_DASHBOARD_IP/dashboard/nova/access_and_security/).
> Then, next time you launch an instance, you can choose that keypair
> created previously.
>
> Regards,
> JuanFra.
>
> 2013/1/22 Balamurugan V G 
>
>> Hi,
>>
>> I have a Folsom private openstack cloud in which security is not a
>> concern. That is I dont really need the security groups and keypairs etc
>> offered by openstack. So all my instances are launched as part of the
>> default security group. I have even allowed all TCP and UDP ports(1 to
>> 65535) and ICMP.
>>
>> But when I try to SSH to the floating IP assigned to a Ubuntu instance, I
>> get connection refused. When I so 'ssh -vvv', I can see that the connection
>> is getting establish but is getting terminated. It seems due to missing key
>> pair.
>>
>> Is there a way to bypass the keypairs.
>>
>> Regards,
>> Balu
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> JuanFra
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Nova compute for ESXi

[Balamurugan V G]

Hi,

 I am trying to add a ESXi compute node to the stack. So I have a Ubuntu VM
inside the ESXi which I plan to use as the compute node for the ESXi. So on
this Ubuntu VM, I need to install nova-compute. Since there are various
flavors of nova-compute, I assume that I should be installing just the
'nova-compute' from the list below:

root@openstack-esxi:~# apt-cache search nova-compute
nova-compute - OpenStack Compute - compute node
nova-compute-kvm - OpenStack Compute - compute node (KVM)
nova-compute-lxc - OpenStack Compute - compute node (LXC)
nova-compute-qemu - OpenStack Compute - compute node (QEmu)
nova-compute-uml - OpenStack Compute - compute node (UserModeLinux)
nova-compute-xcp - OpenStack Compute - compute node (XCP)
nova-compute-xen - OpenStack Compute - compute node (Xen)
nova-xcp-plugins - OpenStack Compute plugin for the Xen Cloud Platform
root@openstack-esxi:~#

Is my assumption right?

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Is the Quantum a network bottleneck

[Balamurugan V G]

Hi,

In an Openstack deployment using Quantum, the compute nodes access the
public/external network via the network node (as per the diagram
http://docs.openstack.org/trunk/openstack-network/admin/content/connectivity.html
).

So if I have a hundred compute nodes each running hundred instances,
wouldn't the link to the network node choke? Also wouldnt the network
node's resources be a bottleneck?

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Bypassing the keypair in Folsom

[Balamurugan V G]

Hi,

I have a Folsom private openstack cloud in which security is not a concern.
That is I dont really need the security groups and keypairs etc offered by
openstack. So all my instances are launched as part of the default security
group. I have even allowed all TCP and UDP ports(1 to 65535) and ICMP.

But when I try to SSH to the floating IP assigned to a Ubuntu instance, I
get connection refused. When I so 'ssh -vvv', I can see that the connection
is getting establish but is getting terminated. It seems due to missing key
pair.

Is there a way to bypass the keypairs.

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Devstack with ESXi Compute Node

[Balamurugan V G]

Looks like its due to difference in the devstack src versions in the two
nodes (i am trying to update the other old node and try again).

-Balu

On Mon, Jan 21, 2013 at 3:02 PM, Balamurugan V G wrote:

> Hi,
>
> I started with a single node Devstack(with quantum) on a Ubuntu12.0 server
> and used a Flat network. It worked fine as I could launch instances and
> cover many use cases.
>
> Now I want to added a second compute node to this stack but it has to be
> an ESXi. So I launched a Ubuntu12.10 VM (using VMWare client) on ESXi and
> installed Devstack on it aswell(I intended to not start the services which
> are not needed on it). I then copied over the nova.conf from the first all
> in one stack node to this and modified the my_ip, VMWare fields etc as per
> http://docs.openstack.org/trunk/openstack-compute/admin/content/vmware.html
> .
>
> I then modified the devstack/stack-screenrc file to hold just these lines
> below and started rejoin-stack.sh.
>
> screen -t q-agt bash
> stuff "python /opt/stack/quantum/bin/quantum-openvswitch-agent
> --config-file /etc/quantum/quantum.conf --config-file
> /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini^M"
> screen -t n-cpu bash
> stuff "cd /opt/stack/nova && sg libvirtd
> /opt/stack/nova/bin/nova-compute^M"
>
>
> But I get the following error:
>
> root@ubuntu1210srvr:/home/stack/devstack# 2013-01-21 22:55:02 INFO
> nova.virt.driver [-] Loading compute driver 'libvirt.LibvirtDriver'
> 2013-01-21 22:55:02 INFO nova.manager [-] Skipping periodic task
> _periodic_update_dns because its interval is negative
> 2013-01-21 22:55:03 INFO nova.network.driver [-] Loading network driver
> 'nova.network.linux_net'
> 2013-01-21 22:55:03 INFO nova.openstack.common.rpc.common
> [req-06c8f346-9939-429c-8f1a-8b7ebfa127b0 None None] Connected to AMQP
> server on 10.5.12.20:5672
> 2013-01-21 22:55:03 CRITICAL nova
> [req-06c8f346-9939-429c-8f1a-8b7ebfa127b0 None None] *Remote error:
> UnsupportedRpcVersion Specified RPC version, 1.22, not supported by this
> endpoint.*
> [u'Traceback (most recent call last):\n', u'  File
> "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 277, in
> _process_data\nrval = self.proxy.dispatch(ctxt, version, method,
> **args)\n', u'  File
> "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 152, in
> dispatch\nraise rpc_common.UnsupportedRpcVersion(version=version)\n',
> u'UnsupportedRpcVersion: Specified RPC version, 1.22, not supported by this
> endpoint.\n'].
> 2013-01-21 22:55:03 TRACE nova Traceback (most recent call last):
> 2013-01-21 22:55:03 TRACE nova   File "/opt/stack/nova/bin/nova-compute",
> line 59, in 
> 2013-01-21 22:55:03 TRACE nova db_allowed=False)
> 2013-01-21 22:55:03 TRACE nova   File "/opt/stack/nova/nova/service.py",
> line 525, in create
> 2013-01-21 22:55:03 TRACE nova db_allowed=db_allowed)
> 2013-01-21 22:55:03 TRACE nova   File "/opt/stack/nova/nova/service.py",
> line 413, in __init__
> 2013-01-21 22:55:03 TRACE nova
> self.conductor_api.wait_until_ready(context.get_admin_context())
> 2013-01-21 22:55:03 TRACE nova   File
> "/opt/stack/nova/nova/conductor/api.py", line 320, in wait_until_ready
> 2013-01-21 22:55:03 TRACE nova self.ping(context, '1.21 GigaWatts',
> timeout=timeout)
> 2013-01-21 22:55:03 TRACE nova   File
> "/opt/stack/nova/nova/conductor/api.py", line 328, in ping
> 2013-01-21 22:55:03 TRACE nova return
> self.conductor_rpcapi.ping(context, arg, timeout)
> 2013-01-21 22:55:03 TRACE nova   File
> "/opt/stack/nova/nova/conductor/rpcapi.py", line 82, in ping
> 2013-01-21 22:55:03 TRACE nova return self.call(context, msg,
> version='1.22', timeout=timeout)
> 2013-01-21 22:55:03 TRACE nova   File
> "/opt/stack/nova/nova/openstack/common/rpc/proxy.py", line 80, in call
> 2013-01-21 22:55:03 TRACE nova return rpc.call(context,
> self._get_topic(topic), msg, timeout)
> 2013-01-21 22:55:03 TRACE nova   File
> "/opt/stack/nova/nova/openstack/common/rpc/__init__.py", line 109, in call
> 2013-01-21 22:55:03 TRACE nova return _get_impl().call(cfg.CONF,
> context, topic, msg, timeout)
> 2013-01-21 22:55:03 TRACE nova   File
> "/opt/stack/nova/nova/openstack/common/rpc/impl_kombu.py", line 765, in call
> 2013-01-21 22:55:03 TRACE nova rpc_amqp.get_connection_pool(conf,
> Connection))
> 2013-01-21 22:55:03 TRACE nova   File
> "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 379, in call
> 2013-01-21 22:55:03 TRACE nova rv = list(rv)
> 2013-01-21 22:55:03 TRAC

[Openstack] Devstack with ESXi Compute Node

[Balamurugan V G]

Hi,

I started with a single node Devstack(with quantum) on a Ubuntu12.0 server
and used a Flat network. It worked fine as I could launch instances and
cover many use cases.

Now I want to added a second compute node to this stack but it has to be an
ESXi. So I launched a Ubuntu12.10 VM (using VMWare client) on ESXi and
installed Devstack on it aswell(I intended to not start the services which
are not needed on it). I then copied over the nova.conf from the first all
in one stack node to this and modified the my_ip, VMWare fields etc as per
http://docs.openstack.org/trunk/openstack-compute/admin/content/vmware.html.

I then modified the devstack/stack-screenrc file to hold just these lines
below and started rejoin-stack.sh.

screen -t q-agt bash
stuff "python /opt/stack/quantum/bin/quantum-openvswitch-agent
--config-file /etc/quantum/quantum.conf --config-file
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini^M"
screen -t n-cpu bash
stuff "cd /opt/stack/nova && sg libvirtd /opt/stack/nova/bin/nova-compute^M"


But I get the following error:

root@ubuntu1210srvr:/home/stack/devstack# 2013-01-21 22:55:02 INFO
nova.virt.driver [-] Loading compute driver 'libvirt.LibvirtDriver'
2013-01-21 22:55:02 INFO nova.manager [-] Skipping periodic task
_periodic_update_dns because its interval is negative
2013-01-21 22:55:03 INFO nova.network.driver [-] Loading network driver
'nova.network.linux_net'
2013-01-21 22:55:03 INFO nova.openstack.common.rpc.common
[req-06c8f346-9939-429c-8f1a-8b7ebfa127b0 None None] Connected to AMQP
server on 10.5.12.20:5672
2013-01-21 22:55:03 CRITICAL nova [req-06c8f346-9939-429c-8f1a-8b7ebfa127b0
None None] *Remote error: UnsupportedRpcVersion Specified RPC version,
1.22, not supported by this endpoint.*
[u'Traceback (most recent call last):\n', u'  File
"/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 277, in
_process_data\nrval = self.proxy.dispatch(ctxt, version, method,
**args)\n', u'  File
"/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 152, in
dispatch\nraise rpc_common.UnsupportedRpcVersion(version=version)\n',
u'UnsupportedRpcVersion: Specified RPC version, 1.22, not supported by this
endpoint.\n'].
2013-01-21 22:55:03 TRACE nova Traceback (most recent call last):
2013-01-21 22:55:03 TRACE nova   File "/opt/stack/nova/bin/nova-compute",
line 59, in 
2013-01-21 22:55:03 TRACE nova db_allowed=False)
2013-01-21 22:55:03 TRACE nova   File "/opt/stack/nova/nova/service.py",
line 525, in create
2013-01-21 22:55:03 TRACE nova db_allowed=db_allowed)
2013-01-21 22:55:03 TRACE nova   File "/opt/stack/nova/nova/service.py",
line 413, in __init__
2013-01-21 22:55:03 TRACE nova
self.conductor_api.wait_until_ready(context.get_admin_context())
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/conductor/api.py", line 320, in wait_until_ready
2013-01-21 22:55:03 TRACE nova self.ping(context, '1.21 GigaWatts',
timeout=timeout)
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/conductor/api.py", line 328, in ping
2013-01-21 22:55:03 TRACE nova return
self.conductor_rpcapi.ping(context, arg, timeout)
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/conductor/rpcapi.py", line 82, in ping
2013-01-21 22:55:03 TRACE nova return self.call(context, msg,
version='1.22', timeout=timeout)
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/openstack/common/rpc/proxy.py", line 80, in call
2013-01-21 22:55:03 TRACE nova return rpc.call(context,
self._get_topic(topic), msg, timeout)
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/openstack/common/rpc/__init__.py", line 109, in call
2013-01-21 22:55:03 TRACE nova return _get_impl().call(cfg.CONF,
context, topic, msg, timeout)
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/openstack/common/rpc/impl_kombu.py", line 765, in call
2013-01-21 22:55:03 TRACE nova rpc_amqp.get_connection_pool(conf,
Connection))
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 379, in call
2013-01-21 22:55:03 TRACE nova rv = list(rv)
2013-01-21 22:55:03 TRACE nova   File
"/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 347, in __iter__
2013-01-21 22:55:03 TRACE nova raise result
2013-01-21 22:55:03 TRACE nova RemoteError: Remote error:
UnsupportedRpcVersion Specified RPC version, 1.22, not supported by this
endpoint.
2013-01-21 22:55:03 TRACE nova [u'Traceback (most recent call last):\n',
u'  File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 277, in
_process_data\nrval = self.proxy.dispatch(ctxt, version, method,
**args)\n', u'  File
"/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 152, in
dispatch\nraise rpc_common.UnsupportedRpcVersion(version=version)\n',
u'UnsupportedRpcVersion: Specified RPC version, 1.22, not supported by this
endpoint.\n'].
2013-01-21 22:55:03 TRACE nova
root@ubuntu1210srvr:/opt/stack/nova#

This is my nova.conf lines related to vmware.

Re: [Openstack] Quantum duplicate subnet creation

[Balamurugan V G]

I have a related question. Though setting allow_overlapping_ips to True
works, the comment above this setting states that this should be left as
False if nova security and/or metadata service is used.


# Enable or disable bulk create/update/delete operations
# allow_bulk = True
# Enable or disable overlapping IPs for subnets
# Attention: the following parameter MUST be set to False if Quantum is
# being used in conjunction with nova security groups and/or metadata
service.
# allow_overlapping_ips = False
allow_overlapping_ips = True

Can some one thought more light on this?

Regards,
Balu


On Thu, Jan 17, 2013 at 3:05 PM, Balamurugan V G wrote:

> Thanks a lot Aaron and Robert. That worked like a charm!
>
> I set the 'allow_overlapping_ips = True' in quantum.conf and rebooted the
> stack(wish there was an easy cli to restart individual projects/services or
> may be I dont know if one exists).
>
> And while still in a Flat network setup I could create the duplicate
> networks.
>
> root@openstack:~# nova list
>
> +--+--++---+
> | ID   | Name | Status |
> Networks  |
>
> +--+--++---+
> | f4762c79-e322-4ec5-8f62-ab2cbe156363 | A1 | ACTIVE | labnet=10.5.12.24;
> private1=192.168.168.4 |
> | 4bac873f-e081-460b-8bf8-95f8719081c7  | A2 | ACTIVE | labnet=10.5.12.22;
> private1=192.168.168.3 |
> | d7e47567-81eb-48a3-a2ca-63e1b5df8a08 | B1 | ACTIVE | labnet=10.5.12.23;
> private2=192.168.168.3 |
>
> +--+--++---+
> root@openstack:~#
>
> Instances A1 and* *A2 can communicate over the private network while B1
> cannot talk to A2 as desired and it doesnt complain about conflicting IP
> either.
>
> I am using the
> quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 plugin.
>
> Regards,
> Balu
>
>
>
>
> On Thu, Jan 17, 2013 at 2:17 PM, Aaron Rosen  wrote:
>
>> Hi,
>>
>> Yup this is definitely possible. The reason why this isn't set by default
>> is that some distros don't ship kernels that build with CONFIG_NET_NS=y or
>> their iproute2 package is to outdated to support linux namespaces.  Also,
>> until recently nova's metadata service didn't support overlapping ips. If
>> you are running ubuntu 12.04 you should be able to set:
>>
>> Q_ALLOW_OVERLAPPING_IP=True
>>
>> in your localrc to enable this.
>>
>> or edit your quantum.conf here and restart quantum to enable overlapping
>> ips.
>>
>> # Enable or disable overlapping IPs for subnets
>> # Attention: the following parameter MUST be set to False if Quantum is
>> # being used in conjunction with nova security groups and/or metadata
>> service.
>> # allow_overlapping_ips = False
>>
>>
>> Aaron
>>
>> p.s: I don't think this will work in a flat network setup though since
>> there is no way to isolate that. What plugin are you using?
>> > I have the following networks in a flat network setup.
>>
>>
>> On Thu, Jan 17, 2013 at 2:52 AM, Balamurugan V G > > wrote:
>>
>>> Hi,
>>>
>>> Is there a way to create a duplicate network/subnet for tenant in
>>> quantum. Basically for a tenant, I want to have some instances(GroupA)
>>> share a subnet and another set of instances(GroupB) share the
>>> same(duplicate) subnet but GroupA and GroupB should be isolated. I have
>>> labnet which is the flat network to which one instance from each group is
>>> assigned for external connectivity. Then I want to have two private
>>> networks private1 and private2 both sharing the same subnet but I was to
>>> assign some instances to private1 and some in private2.
>>>
>>> I have the following networks in a flat network setup.
>>>
>>> root@openstack:~# quantum subnet-list
>>>
>>> +--+--+--+--+
>>> | id   | name | cidr |
>>> allocation_pools |
>>>
>>> +--+--+--+--+
>>> | abb62a74-ad15-452c-857f-ee0a1b388ede |  | 192.168.168.0/24 |
>>> {"start": "192.168.168.2", 

Re: [Openstack] Quantim duplicate subnet creation

[Balamurugan V G]

Thanks a lot Aaron and Robert. That worked like a charm!

I set the 'allow_overlapping_ips = True' in quantum.conf and rebooted the
stack(wish there was an easy cli to restart individual projects/services or
may be I dont know if one exists).

And while still in a Flat network setup I could create the duplicate
networks.

root@openstack:~# nova list
+--+--++---+
| ID   | Name | Status |
Networks  |
+--+--++---+
| f4762c79-e322-4ec5-8f62-ab2cbe156363 | A1 | ACTIVE | labnet=10.5.12.24;
private1=192.168.168.4 |
| 4bac873f-e081-460b-8bf8-95f8719081c7  | A2 | ACTIVE | labnet=10.5.12.22;
private1=192.168.168.3 |
| d7e47567-81eb-48a3-a2ca-63e1b5df8a08 | B1 | ACTIVE | labnet=10.5.12.23;
private2=192.168.168.3 |
+--+--++---+
root@openstack:~#

Instances A1 and* *A2 can communicate over the private network while B1
cannot talk to A2 as desired and it doesnt complain about conflicting IP
either.

I am using the
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 plugin.

Regards,
Balu




On Thu, Jan 17, 2013 at 2:17 PM, Aaron Rosen  wrote:

> Hi,
>
> Yup this is definitely possible. The reason why this isn't set by default
> is that some distros don't ship kernels that build with CONFIG_NET_NS=y or
> their iproute2 package is to outdated to support linux namespaces.  Also,
> until recently nova's metadata service didn't support overlapping ips. If
> you are running ubuntu 12.04 you should be able to set:
>
> Q_ALLOW_OVERLAPPING_IP=True
>
> in your localrc to enable this.
>
> or edit your quantum.conf here and restart quantum to enable overlapping
> ips.
>
> # Enable or disable overlapping IPs for subnets
> # Attention: the following parameter MUST be set to False if Quantum is
> # being used in conjunction with nova security groups and/or metadata
> service.
> # allow_overlapping_ips = False
>
>
> Aaron
>
> p.s: I don't think this will work in a flat network setup though since
> there is no way to isolate that. What plugin are you using?
> > I have the following networks in a flat network setup.
>
>
> On Thu, Jan 17, 2013 at 2:52 AM, Balamurugan V G 
> wrote:
>
>> Hi,
>>
>> Is there a way to create a duplicate network/subnet for tenant in
>> quantum. Basically for a tenant, I want to have some instances(GroupA)
>> share a subnet and another set of instances(GroupB) share the
>> same(duplicate) subnet but GroupA and GroupB should be isolated. I have
>> labnet which is the flat network to which one instance from each group is
>> assigned for external connectivity. Then I want to have two private
>> networks private1 and private2 both sharing the same subnet but I was to
>> assign some instances to private1 and some in private2.
>>
>> I have the following networks in a flat network setup.
>>
>> root@openstack:~# quantum subnet-list
>>
>> +--+--+--+--+
>> | id   | name | cidr |
>> allocation_pools |
>>
>> +--+--+--+--+
>> | abb62a74-ad15-452c-857f-ee0a1b388ede |  | 192.168.168.0/24 |
>> {"start": "192.168.168.2", "end": "192.168.168.254"} |
>> | eedc0c12-c3ed-42ce-a860-692e766087a2 |  | 10.5.12.0/24 |
>> {"start": "10.5.12.21", "end": "10.5.12.25"} |
>>
>> +--+--+--+--+
>> root@openstack:~#
>>
>>
>> Now, the following gets denied.
>>
>> root@openstack:~# quantum subnet-create --tenant-id
>> 7cda178971e84c5194c8531bf4f229d7  private2 192.168.168.0/24
>> Invalid input for operation: Requested subnet with cidr: 192.168.168.0/24for 
>> network: 64ec75d6-0c6f-44e1-a268-b573324c4160 overlaps with another
>> subnet.
>> root@openstack:~#
>>
>> I understand that a duplicate network with a tenant is not a common
>> scenario and perhaps by design its not allowed.
>>
>> But there could be cases like I mentioned.
>>
>> Strangely, I am not allowed to create 

[Openstack] Quantim duplicate subnet creation

[Balamurugan V G]

Hi,

Is there a way to create a duplicate network/subnet for tenant in quantum.
Basically for a tenant, I want to have some instances(GroupA) share a
subnet and another set of instances(GroupB) share the same(duplicate)
subnet but GroupA and GroupB should be isolated. I have labnet which is the
flat network to which one instance from each group is assigned for external
connectivity. Then I want to have two private networks private1 and
private2 both sharing the same subnet but I was to assign some instances to
private1 and some in private2.

I have the following networks in a flat network setup.

root@openstack:~# quantum subnet-list
+--+--+--+--+
| id   | name | cidr |
allocation_pools |
+--+--+--+--+
| abb62a74-ad15-452c-857f-ee0a1b388ede |  | 192.168.168.0/24 |
{"start": "192.168.168.2", "end": "192.168.168.254"} |
| eedc0c12-c3ed-42ce-a860-692e766087a2 |  | 10.5.12.0/24 |
{"start": "10.5.12.21", "end": "10.5.12.25"} |
+--+--+--+--+
root@openstack:~#


Now, the following gets denied.

root@openstack:~# quantum subnet-create --tenant-id
7cda178971e84c5194c8531bf4f229d7  private2 192.168.168.0/24
Invalid input for operation: Requested subnet with cidr:
192.168.168.0/24for network: 64ec75d6-0c6f-44e1-a268-b573324c4160
overlaps with another
subnet.
root@openstack:~#

I understand that a duplicate network with a tenant is not a common
scenario and perhaps by design its not allowed.

But there could be cases like I mentioned.

Strangely, I am not allowed to create the duplicate network even across
tenants. Atleast this should be allowed.

BTW, I am running a single node Devstack.

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] User-Data for MS Windows Instances

[Balamurugan V G]

Hi,

To get the user-data working for a MS Windows Instance, I found this
http://www.cloudbase.it/cloud-init-for-windows-instances/ and yet to test
it.

Is there a better way to do it. I basically want start a few applications
after booting the instance. I do not prefer the inbuilt startup-tasks since
I may have to pass certain parameters for the applications start up which
may not be known beforehand.

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] What is the typical way to deploy OpenStack Compute with ESXi

[Balamurugan V G]

I saw this diagram but it is not very clear if the nova.compute block is on
a separate physical server or can be  installed on a VM inside ESXi.

Regards,
Balu

On Thu, Jan 3, 2013 at 4:40 PM, Andrew Holway  wrote:

> Hi,
>
> http://docs.openstack.org/trunk/openstack-compute/admin/content/vmware.html
>
> Thanks,
>
> Andrew
> On Jan 3, 2013, at 11:38 AM, Balamurugan V G wrote:
>
> > I would like to deploy OpenStack with two compute nodes; one using
> KVM(which seems to be default) and one using VMware ESXi. I am clear on how
> to use KVM compute nodes but its not clear on how to deploy the compute for
> ESXi.
> >
> > Assumptions
> > I cant install compute software on the ESXi server directly since ESXi
> runs a proprietary baremetal OS.
> > I dont need any other proprietary software/license other than ESXi. That
> is I dont need vSphere or vCenter etc.
> >
> > These are some of the questions that I have:
> > Do I need another physical server to install compute which then points
> to the ESXi?
> > Or Do I need to create a Ubuntu(lets say) VM with in ESXi host and
> install compute inside this Ubuntu VM?
> >
> > Any help in clarifying these will be greatly appreciated. Also if there
> is a pointer to a deployment diagram for such a case, that will be great as
> well.
> >
> > Regards,
> > Balu
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] What is the typical way to deploy OpenStack Compute with ESXi

[Balamurugan V G]

I would like to deploy OpenStack with two compute nodes; one using
KVM(which seems to be default) and one using VMware ESXi. I am clear on how
to use KVM compute nodes but its not clear on how to deploy the compute for
ESXi.

Assumptions
I cant install compute software on the ESXi server directly since ESXi runs
a proprietary baremetal OS.
I dont need any other proprietary software/license other than ESXi. That is
I dont need vSphere or vCenter etc.

These are some of the questions that I have:
Do I need another physical server to install compute which then points to
the ESXi?
Or Do I need to create a Ubuntu(lets say) VM with in ESXi host and install
compute inside this Ubuntu VM?

Any help in clarifying these will be greatly appreciated. Also if there is
a pointer to a deployment diagram for such a case, that will be great as
well.

Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Cinder] ISCSITargetCreateFailed: Failed to create iscsi target for volume

[Balamurugan V G]

Try restarting your 'tgt' and other cinder services. That is all I can
think of.

I had similar issue and after I set the path right and restarted the
services, it worked fine.

Regards,
Balu

On Wed, Jan 2, 2013 at 4:23 PM, Leander Bessa Beernaert  wrote:

>
> Reply is inlined below.
>
> On Wed, Jan 2, 2013 at 10:41 AM, Balamurugan V G 
> wrote:
>
>> Is that a typo in your configuration or a copy pase error:
>>
>> # /etc/tgt/conf.d/cinder_tgt.conf
>> nclude /var/lib/cinder/volumes/*
>>
>> The 'i' is missing in 'include'. If its only a copy paste error in the
>> mail, make sure you have the following running:
>>
>
> That was a copy & paste typo, the original file is correct.
>
>
>>
>> root@openstack-vm:~# ps -ef | grep cinder
>> root  3636 1  0 06:53 ?00:00:33 /usr/bin/python
>> /usr/local/bin/cinder-volume
>> root 25433 1  0 06:46 ?00:00:01 /usr/bin/python
>> /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf
>> root 25937 1  0 06:46 ?00:00:32 /usr/bin/python
>> /usr/local/bin/cinder-scheduler --config-file /etc/cinder/cinder.conf
>> root@openstack-vm:~# ps -ef | grep tgt
>> root 31176 31174  0 06:49 ?00:00:03 tgtd
>> root@openstack-vm:~#
>>
> # ps -ef | grep cinder:
> cinder   14315 1  0 10:12 ?00:00:00 su -s /bin/sh -c exec
> cinder-volume --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-volume.log cinder
> cinder   14316 14315  0 10:12 ?00:00:01 /usr/bin/python
> /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-volume.log
> cinder   14336 1  0 10:12 ?00:00:00 su -s /bin/sh -c exec
> cinder-api --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-api.log cinder
> cinder   14337 14336  0 10:12 ?00:00:00 /usr/bin/python
> /usr/bin/cinder-api --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-api.log
> cinder   14358 1  0 10:12 ?00:00:00 su -s /bin/sh -c exec
> cinder-scheduler --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-scheduler.log cinder
> cinder   14359 14358  0 10:12 ?00:00:01 /usr/bin/python
> /usr/bin/cinder-scheduler --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-scheduler.log
> root 21026  6073  0 10:49 pts/200:00:00 grep --color=auto cinder
>
> # ps -ef | grep tgt
> root 13648 1  0 10:09 ?00:00:00 tgtd
> root 13650 13648  0 10:09 ?00:00:00 tgtd
> root 21369  6073  0 10:51 pts/200:00:00 grep --color=auto tgt
>
> # cinder.conf: [user] and [pass] omitted
> [DEFAULT]
> rootwrap_config = /etc/cinder/rootwrap.conf
> api_paste_confg = /etc/cinder/api-paste.ini
> sql_connection = mysql://[user]:[pass]@192.168.111.218/cinder
> iscsi_helper = tgtadm
> volume_name_template = volume-%s
> volume_group = cinder-volumes
> verbose = True
> auth_strategy = keystone
> state_path = /var/lib/cinder
> volumes_dir = /var/lib/cinder/volumes
>
>
>> Also, in my case(devstack install), the path is
>> '/opt/stack/data/cinder/volumes/*' and not ' /var/lib/cinder/volumes/*'. So
>> make sure your path is right.
>>
>>
> I'm using a custom install script to setup a single install of OpenStack
> using the packages provided by Ubuntu 12.04.
>
>
>> Hope this helps.
>>
>> Regards,
>> Balu
>>
>>
>> On Wed, Jan 2, 2013 at 3:47 PM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> # /etc/tgt/conf.d/cinder_tgt.conf
>>> nclude /var/lib/cinder/volumes/*
>>>
>>
>>
>
> Regards,
>
> Leander
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Cinder] ISCSITargetCreateFailed: Failed to create iscsi target for volume

[Balamurugan V G]

Is that a typo in your configuration or a copy pase error:

# /etc/tgt/conf.d/cinder_tgt.conf
nclude /var/lib/cinder/volumes/*

The 'i' is missing in 'include'. If its only a copy paste error in the
mail, make sure you have the following running:

root@openstack-vm:~# ps -ef | grep cinder
root  3636 1  0 06:53 ?00:00:33 /usr/bin/python
/usr/local/bin/cinder-volume
root 25433 1  0 06:46 ?00:00:01 /usr/bin/python
/usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf
root 25937 1  0 06:46 ?00:00:32 /usr/bin/python
/usr/local/bin/cinder-scheduler --config-file /etc/cinder/cinder.conf
root@openstack-vm:~# ps -ef | grep tgt
root 31176 31174  0 06:49 ?00:00:03 tgtd
root@openstack-vm:~#

Also, in my case(devstack install), the path is
'/opt/stack/data/cinder/volumes/*' and not ' /var/lib/cinder/volumes/*'. So
make sure your path is right.

Hope this helps.

Regards,
Balu


On Wed, Jan 2, 2013 at 3:47 PM, Leander Bessa Beernaert  wrote:

> # /etc/tgt/conf.d/cinder_tgt.conf
> nclude /var/lib/cinder/volumes/*
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Associating virtual instance NICs to specific networks in quantum

[Balamurugan V G]

Thanks Dan. For the widget, something like this (
http://quasipartikel.at/multiselect/) should work well. It offers both
selecting a subset of options as well as ordering them.

I am evaluating OpenStack for a private cloud and if the POC goes through
fine and we get to actual deployment, hopefully I can contribute back
something.

Thanks,
Balu


On Mon, Dec 31, 2012 at 11:54 PM, Dan Wendlandt  wrote:

>
>
> On Sun, Dec 30, 2012 at 8:54 PM, Balamurugan V G 
> wrote:
>
>> Thanks Itzik. This basically goes by the order. Though this should
>> suffice for most cases, it would have been nice to have more fine grain
>> control and specify the interface names as well.
>>
>> Also, we cant achieve this in Horizon yet. Any idea when Horizon will
>> reach feature parity with CLI?
>>
>
> It is targeted for Grizzly, but progress has been slow:
> https://blueprints.launchpad.net/horizon/+spec/quantum-vnic-ordering
>
> One of the reasons for the delay is that this requires a new horizon
> widget (
> https://blueprints.launchpad.net/horizon/+spec/orderable-mutiple-choice-field),
> so if someone wants to work on this, that would speed things up :)
>
> Dan
>
>
>
>>
>> Regards,
>> Balu
>>
>>
>> On Mon, Dec 31, 2012 at 3:35 AM, Itzik Brown 
>> wrote:
>>
>>>  Hi,
>>>
>>> What about running nova boot:
>>> #nova boot --flavor m1.tiny --image myimage --nic
>>> net-id=e7038a3b-cd45-4795-83ec-02b0a11a9bf1 --nic
>>> net-id=dc95727d-9495-44e8-9b27-0a942cd671fc vm1.
>>>
>>> Here the first NIC will be connected to Network with ID
>>> e7038a3b-cd45-4795-83ec-02b0a11a9bf1 and the second to Network with ID
>>> dc95727d-9495-44e8-9b27-0a942cd671fc.
>>>
>>> Hope it helps,
>>> Itzik
>>>
>>> On 28/12/2012 06:26, Balamurugan V G wrote:
>>>
>>> Lets says, I create a Linux virtual Instance in an OpenStack private
>>> cloud and associate the instance with two networks; A & B. It seems to
>>> associate eth0 and eth1 to A and B respectively. But is there any way in
>>> which I can specify that eth0 should be attached to network B and eth1
>>> should be attached to network A.
>>>
>>> The quantum CLI 'quantum port-create' accepts just device-id and
>>> network-id which is not sufficient to achieve the level of specificity I
>>> believe. Can this be achieved today?
>>>
>>> Also when will the Horizon UI and Quantum REST API reach feature parity
>>> with the Quantum CLI? will it be in Grizzly or later?
>>>
>>> Thanks,
>>> Balu
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> ~~~
> Dan Wendlandt
> Nicira, Inc: www.nicira.com
> twitter: danwendlandt
> ~~~
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Associating virtual instance NICs to specific networks in quantum

[Balamurugan V G]

Thanks Itzik. This basically goes by the order. Though this should suffice
for most cases, it would have been nice to have more fine grain control and
specify the interface names as well.

Also, we cant achieve this in Horizon yet. Any idea when Horizon will reach
feature parity with CLI?

Regards,
Balu

On Mon, Dec 31, 2012 at 3:35 AM, Itzik Brown wrote:

>  Hi,
>
> What about running nova boot:
> #nova boot --flavor m1.tiny --image myimage --nic
> net-id=e7038a3b-cd45-4795-83ec-02b0a11a9bf1 --nic
> net-id=dc95727d-9495-44e8-9b27-0a942cd671fc vm1.
>
> Here the first NIC will be connected to Network with ID
> e7038a3b-cd45-4795-83ec-02b0a11a9bf1 and the second to Network with ID
> dc95727d-9495-44e8-9b27-0a942cd671fc.
>
> Hope it helps,
> Itzik
>
> On 28/12/2012 06:26, Balamurugan V G wrote:
>
> Lets says, I create a Linux virtual Instance in an OpenStack private cloud
> and associate the instance with two networks; A & B. It seems to associate
> eth0 and eth1 to A and B respectively. But is there any way in which I can
> specify that eth0 should be attached to network B and eth1 should be
> attached to network A.
>
> The quantum CLI 'quantum port-create' accepts just device-id and
> network-id which is not sufficient to achieve the level of specificity I
> believe. Can this be achieved today?
>
> Also when will the Horizon UI and Quantum REST API reach feature parity
> with the Quantum CLI? will it be in Grizzly or later?
>
> Thanks,
> Balu
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] How to create vm instance to specific compute node?

[Balamurugan V G]

Also, perhaps the filters can be used. Check the documentation at:

http://docs.openstack.org/trunk/openstack-compute/admin/content/scheduler-filters.html

I haven't tried it though.

Regards,
Balu

On Fri, Dec 28, 2012 at 4:09 AM, Jay Pipes  wrote:

> No.
>
> Use nova boot --availability_zone=nova:hostname where nova: is your
> availability zone and hostname is the hostname of the compute node you
> wish to put the instance on.
>
> Note this is an admin-only ability by default and can oversubscribe the
> compute node the instance goes on.
>
> Best,
> -jay
>
> On 12/27/2012 02:45 PM, Rick Jones wrote:
> > Does the convention of adding --onhost--computenodename to the instanc
> > name being created still work?
> >
> > rick jones
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Associating virtual instance NICs to specific networks in quantum

[Balamurugan V G]

Lets says, I create a Linux virtual Instance in an OpenStack private cloud
and associate the instance with two networks; A & B. It seems to associate
eth0 and eth1 to A and B respectively. But is there any way in which I can
specify that eth0 should be attached to network B and eth1 should be
attached to network A.

The quantum CLI 'quantum port-create' accepts just device-id and network-id
which is not sufficient to achieve the level of specificity I believe. Can
this be achieved today?

Also when will the Horizon UI and Quantum REST API reach feature parity
with the Quantum CLI? will it be in Grizzly or later?

Thanks,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp