Re: [Openstack] [Quantum/Neutron] VM cannot get IP address from DHCP server
Hi, Please can you look up in the iptables? Normally on a working openstack host the packets comming in the filter table in the input chain are directed to the nova-network-INPUT which has a rule to accept dhcp packets. On my setup is something like: -A INPUT -j nova-network-INPUT . . . -A nova-network-INPUT -i br100 -p udp -m udp --dport 67 -j ACCEPT So I think you have to look somewhere else for your issue. Regards, Gabriel From: David Kang dk...@isi.edu To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) openstack@lists.launchpad.net Sent: Tuesday, July 23, 2013 7:22 PM Subject: [Openstack] [Quantum/Neutron] VM cannot get IP address from DHCP server Hi, We are running OpenStack Folsom on CentOS 6.4. Quantum-linuxbridge-agent is used. By default, the Quantum node has the following entries in its /etc/sysconfig/iptables file. -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited With those two lines, VM cannot get IP address from the DHCP server running on the Quantum node. More specifically, the first line prevents a VM from getting IP address from DHCP server. The second line prevents a VM from talking to other VMs and external worlds. Is there a better way to make the Quantum network work well than just commenting them out? I'll appreciate your help. David -- -- Dr. Dong-In David Kang Computer Scientist USC/ISI ___ 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] [Quantum/Neutron] VM cannot get IP address from DHCP server
Hi, This is very interesting..:) I am using openstack grizzly allinone with quantum/neutron. Look what I am observing. -before starting an instance on the server root@ubuntu1204:~# iptables-save -t filter # Generated by iptables-save v1.4.12 on Tue Jul 23 20:22:55 2013 *filter :INPUT ACCEPT [62981:17142030] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [62806:17138989] :nova-api-FORWARD - [0:0] :nova-api-INPUT - [0:0] :nova-api-OUTPUT - [0:0] :nova-api-local - [0:0] :nova-filter-top - [0:0] -A INPUT -j nova-api-INPUT -A INPUT -p gre -j ACCEPT -A FORWARD -j nova-filter-top -A FORWARD -j nova-api-FORWARD -A OUTPUT -j nova-filter-top -A OUTPUT -j nova-api-OUTPUT -A nova-api-INPUT -d 10.200.10.10/32 -p tcp -m tcp --dport 8775 -j ACCEPT -A nova-filter-top -j nova-api-local COMMIT # Completed on Tue Jul 23 20:22:55 2013 root@ubuntu1204:~# -after starting an instance on the host root@ubuntu1204:~# iptables-save -t filter # Generated by iptables-save v1.4.12 on Tue Jul 23 20:24:42 2013 *filter :INPUT ACCEPT [90680:24989889] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [90482:24984752] :nova-api-FORWARD - [0:0] :nova-api-INPUT - [0:0] :nova-api-OUTPUT - [0:0] :nova-api-local - [0:0] :nova-compute-FORWARD - [0:0] :nova-compute-INPUT - [0:0] :nova-compute-OUTPUT - [0:0] :nova-compute-inst-35 - [0:0] :nova-compute-local - [0:0] :nova-compute-provider - [0:0] :nova-compute-sg-fallback - [0:0] :nova-filter-top - [0:0] -A INPUT -j nova-compute-INPUT -A INPUT -j nova-api-INPUT -A INPUT -p gre -j ACCEPT -A FORWARD -j nova-filter-top -A FORWARD -j nova-compute-FORWARD -A FORWARD -j nova-api-FORWARD -A OUTPUT -j nova-filter-top -A OUTPUT -j nova-compute-OUTPUT -A OUTPUT -j nova-api-OUTPUT -A nova-api-INPUT -d 10.200.10.10/32 -p tcp -m tcp --dport 8775 -j ACCEPT -A nova-compute-FORWARD -s 0.0.0.0/32 -d 255.255.255.255/32 -p udp -m udp --sport 68 --dport 67 -j ACCEPT -A nova-compute-INPUT -s 0.0.0.0/32 -d 255.255.255.255/32 -p udp -m udp --sport 68 --dport 67 -j ACCEPT -A nova-compute-inst-35 -m state --state INVALID -j DROP -A nova-compute-inst-35 -m state --state RELATED,ESTABLISHED -j ACCEPT -A nova-compute-inst-35 -j nova-compute-provider -A nova-compute-inst-35 -s 172.24.17.2/32 -p udp -m udp --sport 67 --dport 68 -j ACCEPT -A nova-compute-inst-35 -s 172.24.17.0/24 -j ACCEPT -A nova-compute-inst-35 -p tcp -m tcp --dport 22 -j ACCEPT -A nova-compute-inst-35 -p icmp -j ACCEPT -A nova-compute-inst-35 -j nova-compute-sg-fallback -A nova-compute-local -d 172.24.17.1/32 -j nova-compute-inst-35 -A nova-compute-sg-fallback -j DROP -A nova-filter-top -j nova-compute-local -A nova-filter-top -j nova-api-local COMMIT # Completed on Tue Jul 23 20:24:42 2013 It seams that the rule that accepts dhcp packets is created once an instance is spawned. I will try the same thing on an centos64. Regards, Gabriel From: David Kang dk...@isi.edu To: Staicu Gabriel gabriel_sta...@yahoo.com Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) openstack@lists.launchpad.net Sent: Tuesday, July 23, 2013 7:59 PM Subject: Re: [Openstack] [Quantum/Neutron] VM cannot get IP address from DHCP server Thank you for your suggestion. We are using Quantum/Neutron not nova-network. So, we don't use br100. (I believe you are using nova-network.) And the firewall rules that cause problem reside on the Quantum node not on the nova-compute node. I cannot find any rule for --dport 67 on my Quantum node. I used service iptables status command to check the firewall rules. Thanks, David - Original Message - Hi, Please can you look up in the iptables? Normally on a working openstack host the packets comming in the filter table in the input chain are directed to the nova-network-INPUT which has a rule to accept dhcp packets. On my setup is something like: -A INPUT -j nova-network-INPUT . . . -A nova-network-INPUT -i br100 -p udp -m udp --dport 67 -j ACCEPT So I think you have to look somewhere else for your issue. Regards, Gabriel From: David Kang dk...@isi.edu To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) openstack@lists.launchpad.net Sent: Tuesday, July 23, 2013 7:22 PM Subject: [Openstack] [Quantum/Neutron] VM cannot get IP address from DHCP server Hi, We are running OpenStack Folsom on CentOS 6.4. Quantum-linuxbridge-agent is used. By default, the Quantum node has the following entries in its /etc/sysconfig/iptables file. -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited With those two lines, VM cannot get IP address from the DHCP server running on the Quantum node. More specifically, the first line prevents a VM from getting IP address from DHCP server. The second line prevents a VM from talking to other VMs and external worlds. Is there a better way to make the Quantum network work well than just commenting them out? I'll appreciate your help
Re: [Openstack] How to create image for first instance (CentOS 6.4)
Yes it's ok. Or you can use another computer with virt-manager installed which supports running windows virtual machines on it. In other words another computer with cpu with virtualization feature + kvm + virt-manager. If you use the option with another computer you will have to copy the resulted qcow2 file resulted from the installation of win7 with virtio drivers for net and disk from the computer with virt-manager to the glance server. Regards, Gabriel From: Jake G. dj_dark_jungl...@yahoo.com To: Brian Schott brian.sch...@nimbisservices.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Thursday, July 18, 2013 4:54 PM Subject: Re: [Openstack] How to create image for first instance (CentOS 6.4) I saw that but I don't have virt-manager on my compute node. Is it ok to install it? On 2013/07/18, at 22:19, Brian Schott brian.sch...@nimbisservices.com wrote: Did this work for you? http://docs.openstack.org/trunk/openstack-image/content/centos-image.html - Brian Schott, CTO Nimbis Services, Inc. brian.sch...@nimbisservices.com ph: 443-274-6064 fx: 443-274-6060 On Jul 18, 2013, at 5:28 AM, Jake G. dj_dark_jungl...@yahoo.com wrote: Hi All, I figured this would be the easiest part, but seems not to be. So creating an instance and booting from a CentOS installation disk doesn't work the way I imagined, How would you create the image template to use to deploy instances of CentOS 6.4? The specs are below: OS: CentOS 6.4 x8664 RAM: 1024MB HDD: 40GB NIC: 1 Thank you! Jake___ 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] Quantum question
Hi Remo, If your talking about this document: http://docs.openstack.org/grizzly/openstack-network/admin/content/use_cases_single_flat.html I think that in that case you don't have something from the logical point of view something like a router. You just have L2 segments so there is no place where NAT can happen and therefore you can not use floating ip notion. In floating ip case practically the framework creates a static NAT between the floating ip and the private ip that the instance receive when boots up. Regards, Gabriel From: Remo Mattei r...@mattei.org To: openstack@lists.launchpad.net Sent: Saturday, July 13, 2013 11:23 PM Subject: [Openstack] Quantum question Hello everyone I was reading the doc and it was saying that model one on quantum does not support floating ip address and I wonder why this limitation Thanks Remo ___ 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] Quantum question
With the second question I think you touched the right spot. I will try to clarify using an example. Let's imagine the following situation: You have to deploy openstack in an environment where you don't have any type of the control of the network side. I am referring here to the control on the routers, switches, firewall. You are just a consumer of an IP space which is administered by the network department. You can just plug physical cable in the switch they tell you and by means of the dhcp they will provide you with all the information for your physical servers and also for the virtual ones. In this case the openstack model you can use is: flat_network (the one you specified in your first message). The openstack framework will just create for you a virtual bridge (a L2 segment) which will be connected by the physical network card of the host to the physical network in your enterprise. The virtual machines will receive IP addresses from an DHCP server that you do not control. So your virtual machines will have IP addresses from the enterprise space, and will be accessible directly from inside like any other machine without NAT. From the openstack perspective will be just a forwarding at L2 level. This is flat network. In the above example let's suppose that you can negotiate with the network department to reserve you a subspace of the enterprise space: a continuous ip addresses range that they won't allocate from their DHCP server. In this case you can use in openstack flat_dhcp option. The openstack framework will use dnsmasq to simulate dhcp service. This means that openstack will simulate a virtual bridge but in plus of the above situation in this virtual switch it will plug virtually also a dhcp service that you will manage and which it will provide ip addresses to your virtual machines. From here it is exactly like the first case. So to answer to your question you can not do a port mapping on the physical router because you do not have access to that equipment. All you administer in those to cases is the openstack environment and on it from the networking point of view you just have a virtual switch in the first case, a virtual switch and a dhcp in the second one and there is no place to do NAT so no floating in those 2 cases. Spero che sia piu chiaro adesso .. :), Ciao Gabriel From: Remo Mattei r...@mattei.org To: Staicu Gabriel gabriel_sta...@yahoo.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Sunday, July 14, 2013 1:48 AM Subject: Re: [Openstack] Quantum question One more thing to this slide there is a physical router that can be configured by the admin etc and I can do a port mapping from there so why the floating will not be an option? Not clear again. Inviato da iPad () Il giorno Jul 13, 2013, alle ore 15:26, Remo Mattei r...@mattei.org ha scritto: So if I add a virtual router I will have this working the models are not well describe why and that is a problem not only to me but others as well when to choose which one etc. Inviato da iPad () Il giorno Jul 13, 2013, alle ore 13:44, Staicu Gabriel gabriel_sta...@yahoo.com ha scritto: Hi Remo, If your talking about this document: http://docs.openstack.org/grizzly/openstack-network/admin/content/use_cases_single_flat.html I think that in that case you don't have something from the logical point of view something like a router. You just have L2 segments so there is no place where NAT can happen and therefore you can not use floating ip notion. In floating ip case practically the framework creates a static NAT between the floating ip and the private ip that the instance receive when boots up. Regards, Gabriel From: Remo Mattei r...@mattei.org To: openstack@lists.launchpad.net Sent: Saturday, July 13, 2013 11:23 PM Subject: [Openstack] Quantum question Hello everyone I was reading the doc and it was saying that model one on quantum does not support floating ip address and I wonder why this limitation Thanks Remo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp !DSPAM:2,51e1d470163683301363137! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp !DSPAM:2,51e1d470163683301363137! ___ 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] Remote access to the windows virtual machine
Hi,
From the openstack documentation:
(http://docs.openstack.org/folsom/openstack-compute/install/apt/content/faq-about-vnc.html)
A: These values are hard-coded in a Django HTML template. To alter them, you
must edit the template file _detail_vnc.html. The location of this file will
vary based on Linux distribution. On Ubuntu 12.04, the file can be found
at/usr/share/pyshared/horizon/dashboards/nova/templates/nova/instances_and_volumes/instances/_detail_vnc.html.
Modify the width and height parameters:
iframe src={{ vnc_url }} width=720 height=430/iframe
Regards,
Gabriel
From: Brian Schott brian.sch...@nimbisservices.com
To: Narayanan, Krishnaprasad naray...@uni-mainz.de
Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net
Sent: Friday, May 31, 2013 12:02 AM
Subject: Re: [Openstack] Remote access to the windows virtual machine
For windows, you could add TCP port 3389 to your security group and enable
remote desktop access in windows. The VNC console access in Horizon is really
intended for administrative/management access rather than production usage.
Brian
-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
ph: 443-274-6064 fx: 443-274-6060
On May 30, 2013, at 3:58 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de
wrote:
Hallo All,
Currently, I use VNC to access the windows virtual machine deployed in
OpenStack. But this gives me a smaller view of the Windows GUI or Desktop. Is
there any way from the Horizon GUI to have an enlarged view of the Windows
Desktop?
Can I get any suggestions to connect to the windows virtual machine remotely
apart from using VNC?
Thanks
Krishnaprasad
From: Narayanan, Krishnaprasad
Sent: Dienstag, 28. Mai 2013 02:42
To: 'JuanFra Rodriguez Cardoso'
Cc: openstack@lists.launchpad.net
Subject: RE: [Openstack] Windows Image 2008 in OpenStack
Hi JuanFra,
Thanks for the suggestion regarding the usage of cloudinit for windows
instances.
For all Stackers - I found this URI useful where there is a Windows Server
2012 Evaluation image available for download and it can be directly deployed
to OpenStack. I was able to download and deploy the image in our ESSEX cloud
and create a VM successfully out of the image.
Thanks
Krishnaprasad
From: JuanFra Rodriguez Cardoso [mailto:juanfra.rodriguez.card...@gmail.com]
Sent: Montag, 27. Mai 2013 23:41
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Windows Image 2008 in OpenStack
I think a great tool would be Cloudbase's cloud-init for windows instances:
http://www.cloudbase.it/cloud-init-for-windows-instances/
Regards,
---
JuanFra
2013/5/27 Narayanan, Krishnaprasad naray...@uni-mainz.de
Hallo All,
Can somebody guide me to create a virtual machine using Windows 2008 image?
Thanks
Krishnaprasad
___
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] nova-network no ip for vm
Hi, A place to look for eventually error messages is also /var/log/messages. Look for dnsmasq related message and post them here. Regards, Gabriel From: Arindam Choudhury arin...@live.com To: openstack openstack@lists.launchpad.net Sent: Thursday, April 25, 2013 11:10 AM Subject: [Openstack] nova-network no ip for vm Hi, I am really stuck, any help will be highly appreciated. I installed a two node openstack deployment on debian wheezy: # nova-manage service list Binary Host Zone Status State Updated_At nova-network aopcach internal enabled :-) 2013-04-25 08:05:18 nova-cert aopcach internal enabled :-) 2013-04-25 08:05:18 nova-conductor aopcach internal enabled :-) 2013-04-25 08:05:18 nova-consoleauth aopcach internal enabled :-) 2013-04-25 08:05:18 nova-scheduler aopcach internal enabled :-) 2013-04-25 08:05:18 nova-network aopcso1 internal enabled :-) 2013-04-25 08:05:15 nova-compute aopcso1 nova enabled :-) 2013-04-25 08:05:15 # nova-manage network list id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid 1 192.168.100.0/24 None 192.168.100.2 8.8.4.4 None None None 5f6a8ef4-7003-48f8-8922-5303f37d0ce8 But when boot up a vm(the cirros from the tutorial), it dont get any ip. Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40network failed ### ifconfig a eth0 Link encap:Ethernet HWaddr FA:16:3E:CD:3B:97 inet6 addr: fe80::f816:3eff:fecd:3b97/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1361 errors:0 dropped:6 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:159974 (156.2 KiB) TX bytes:902 (902.0 B) lo Link 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) In controller or compute node the nova-network.log does not generate any logging of events. on the horizon I dont have any network listing. ___ 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?
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 p...@draigbrady.com To: Balamurugan V G balamuruga...@gmail.com 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
Re: [Openstack] How to Query Nova Instance Faults
Hi, 1) connect to mysql database: mysql -uroot -p 2) use nova database once in mysql prompt mysql use nova; 3) find the error values mysql select * from instance_faults; Regards, Gabriel From: Malek Mushleh mmus...@isi.edu To: openstack@lists.launchpad.net Sent: Thursday, February 7, 2013 5:14 PM Subject: [Openstack] How to Query Nova Instance Faults Hi, I am getting an error when performing nova boot ...: on an image that I have confirmed is in my glance repository. However, the corresponding logs do not indicate why or what the error is. Is there a way and how to query the database for the nova instance error as alluded to here: http://stackoverflow.com/questions/13954539/nova-boot-error-devstack Thanks, Malek ___ 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] Is the Quantum a network bottleneck
These are great news Gary. Do you happen to know if the patch will be also available for folsom? Thanks, Gabriel From: Gary Kotton gkot...@redhat.com To: jian@canonical.com Cc: openstack@lists.launchpad.net Sent: Wednesday, January 23, 2013 10:08 AM Subject: Re: [Openstack] Is the Quantum a network bottleneck On 01/22/2013 07:02 PM, Jian Wen wrote: On 2013年01月22日 10:56, Balamurugan V G wrote: 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 Quantum Multi-host DHCP and L3 https://blueprints.launchpad.net/quantum/+spec/quantum-multihost Yes. At the moment the network node is the bottleneck. There is a patch upstream in review that will solve this issue: https://review.openstack.org/#/c/18216/ Hopefully this will be ready in the Grizzly cycle. In addition to this it also provides HA for the L3 and DHCP agents. Thanks Gary -- Jian Wen ___ 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] Problem hen running VM instances
Hi,
The simplest way to check is to have a look at /var/log/nova/nova-compute.log
Regards,
Gabriel
From: Guilherme Russi luisguilherme...@gmail.com
To: openstack@lists.launchpad.net
Sent: Monday, December 10, 2012 6:15 PM
Subject: [Openstack] Problem hen running VM instances
Hi again guys,
I'm sorry for all these questions, but when I learn how to install it I'll
help people with these same problems, well, I'm trying to run a VM instance on
Essex, a ubuntu image, but when I try to boot it the OS-EXT-STS:vm_state is
error.
What am I missing?
Thank you all again.
Guilherme Russi.
nova --os_tenant_name cloud image-list
+--+---+++
| ID | Name
| Status | Server |
+--+---+++
| 31d45bd5-5ba5-45b6-814e-54eef1699074 | tty-linux-ramdisk | ACTIVE | |
| b54cd532-20c2-4b48-a735-6d7fd6b083b8 | tty-linux-kernel | ACTIVE | |
| c16e7a7a-3c21-44db-8a38-5a49fa262ac9 | tty-linux-kernel | SAVING | |
| d5220087-89ce-486f-a98e-3eb2c367d7ba | tty-linux | ACTIVE |
|
+--+---+++
nova --os_tenant_name cloud boot --flavor 2 --image
b54cd532-20c2-4b48-a735-6d7fd6b083b8 --security_group default imagem
+-+--+
| Property | Value |
+-+--+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-SRV-ATTR:host | None |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
| OS-EXT-SRV-ATTR:instance_name | instance-0001 |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | error |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | V4oFZcgLjrYn |
| config_drive | |
| created | 2012-12-10T15:56:44Z |
| flavor | m1.small |
| hostId | |
| id | f43f77e7-1e36-4e19-b752-2e4c3ba7c076 |
| image | tty-linux-kernel |
| key_name | |
| metadata | {} |
| name | imagem |
| progress | 0 |
| status | BUILD |
| tenant_id | d52768c939ee4a1b8dc82182a29df8d2 |
| updated | 2012-12-10T15:56:44Z |
| user_id | 830ae8bc830440c28372066bdf20d9bc |
+-+--+
nova --os_tenant_name cloud list
+--+++--+
| ID | Name | Status | Networks |
+--+++--+
| f43f77e7-1e36-4e19-b752-2e4c3ba7c076 | imagem | ERROR | |
+--+++--+
___
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 deploy openstack automatically in your env.
Hi, Also to get starting you can use openstack-demo-install which comes in the packet openstack-utils. Regards, Gabriel From: Lei Zhang zhang.lei@gmail.com To: Tim Bell tim.b...@cern.ch Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Tuesday, December 4, 2012 4:08 AM Subject: Re: [Openstack] How to deploy openstack automatically in your env. Thanks all guys. Finally, I will try the puppet on the RHEL today and check whether it works. On Mon, Dec 3, 2012 at 11:59 PM, Tim Bell tim.b...@cern.ch wrote: Lei, At CERN, we run our RHEL-based OpenStack instance with the puppetlabs modules. They work very well and simplify the multi-node deployments. We've got around 200 hypervisors deployed with this method. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Derek Higgins Sent: 03 December 2012 16:37 To: Lei Zhang Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] How to deploy openstack automatically in your env. Hi Lei, On 12/03/2012 09:15 AM, Lei Zhang wrote: Hi all, I search the internet for days and found several automatically tool. Including * devstack * puppet+pupet-openstack * stackops * OneStack But It seems that all the scripts are well tested on ubuntu not RHEL. How could you guys to deploy the openstack automatically, especially on RHEL. a lot of work has gone into the puppetlabs puppet modules so that they work on RHEL, you can download the modules from their github account https://github.com/puppetlabs/ alternatively, I have been working on a tool to deploy openstack on RHEL and Fedora, its still at early stages and probably a bit rough around the edges but if your interested you can try it out https://github.com/fedora- openstack/packstack currently you can use packstack to install folsom keystone, glance, nova, cinder, horizon and swift on Multiple RHEL or Fedora servers. If you want to try it out it would be great to get any feedback you have. packstack uses the puppetlabs modules to apply puppet manifests to individual servers without the requirement of having a puppet master server. thanks, Derek. -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ 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 -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ 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] Questions about novnc with multihost OpenStack Nova Compute(Essex) in multihost
Hi Olivier, Which version of openstack are you using? Essex or Folsom? On which operating system is your cloud installed (Fedora or Ubuntu)? In my setup, which is Openstack Essex on Ubuntu12.04 I obtain: root@hltopenstack01:~$ nova get-vnc-console 1fc2cea1-9aec-4d7d-b80e-eab436ae3246 novnc +---+---+ | Type | Url | +---+---+ | novnc | http://10.205.16.18:6080/vnc_auto.html?token=17210200-4622-4480-9b0f-1ca4ffe6fc75 | The value http://10.205.16.18:6080/vnc_auto.html corresponds in nova.conf to the parameter: --novncproxy_base_url=http://10.205.16.18:6080/vnc_auto.html Beside this I saw that you are from France. It will be an event regarding openstack in Paris on 29 November. Are you interested?...:) Regards, Gabriel From: Olivier Archer olivier.arc...@ifremer.fr To: Staicu Gabriel gabriel_sta...@yahoo.com Cc: 张家龙 zhan...@awcloud.com; openstack openstack@lists.launchpad.net Sent: Friday, October 26, 2012 11:36 AM Subject: Re: [Openstack] Questions about novnc with multihost OpenStack Nova Compute(Essex) in multihost Hi, This work also for me exept tha the url is localhost based: $nova get-vnc-console landsat01 novnc | novnc | http://127.0.0.1:6080/vnc_auto.html?token=6137dcb5-41b4-46fb-9c42-76c97e961e69 | So it doesn't work in the dashboard or if i copy/paste into a browser. But it works if i change 127.0.0.1 to the public ip of the compute node. (I am in a multi host config). But from where is taken the value of 127.0.0.1 in the config file ? You have no references to it in the configuration you posted... Regards, 2012/10/25 Staicu Gabriel gabriel_sta...@yahoo.com Hi, I have a cloud constructed on ubuntu12.04 with openstack essex. -controller node: 10.205.16.18 The configuration regarding vnc: --vncserver_host=0.0.0.0 --vncproxy_url=http://10.205.16.18:6080 --ajax_console_proxy_url=http://10.205.16.18:8000 --novnc_enabled=true --novncproxy_base_url=http://10.205.16.18:6080/vnc_auto.html --vncserver_proxyclient_address=10.205.16.18 --vncserver_listen=10.205.16.18 -compute node:10.205.16.241 --vncproxy_url=http://10.205.16.18:6080 --ajax_console_proxy_url=http://10.205.16.18:8000 --novnc_enabled=true --novncproxy_base_url=http://10.205.16.18:6080/vnc_auto.html --vncserver_proxyclient_address=10.205.16.241 --vncserver_listen=10.205.16.241 And everything works ok. Hope this help. Regards, Gabriel From: 张家龙 zhan...@awcloud.com To: openstack openstack@lists.launchpad.net Sent: Thursday, October 25, 2012 9:43 AM Subject: [Openstack] Questions about novnc with multihost OpenStack Nova Compute(Essex) in multihost Dear all, I have some questions about OpenStack Nova Compute(Essex) using novnc. I build a cluster using 4 computers with OpenStack Nova Compute in multihost. The follows were informations of my cluster: nova01:compute server,api server,controller server 192.168.3.3 nova02:compute server 192.168.3.4 nova03:compute server 192.168.3.5 nova04:compute server 192.168.3.6 And the vms`s fixed was 10.0.0.0/8 Here was my nova.conf: http://pastebin.com/K6ArR1HA While,when i executed the command nova get-vnc-console servername novnc then,error occured. Here were the error informations: 2012-10-25 14:25:27 ERROR nova.rpc.impl_qpid [req-1ad62be7-8eeb-43a5-898c-f3552b9f7748 3faf7062208c456c9a9365ee50bf15cd 561a547e94c7 4ce797d0ef1f4bc91f91] Timed out waiting for RPC response: None 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid Traceback (most recent call last): 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File /usr/lib/python2.6/site-packages/nova/rpc/impl_qpid.py, line 364, in ensure 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid return method(*args, **kwargs) 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File /usr/lib/python2.6/site-packages/nova/rpc/impl_qpid.py, line 413, in _consume 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid nxt_receiver = self.session.next_receiver(timeout=timeout) 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File string, line 6, in next_receiver 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 651, in nex t_receiver 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid raise Empty 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid Empty: None 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid 2012-10-25 14:25:27 ERROR nova.api.openstack [req-1ad62be7-8eeb-43a5-898c
Re: [Openstack] Questions about novnc with multihost OpenStack Nova Compute(Essex) in multihost
Hi, I have a cloud constructed on ubuntu12.04 with openstack essex. -controller node: 10.205.16.18 The configuration regarding vnc: --vncserver_host=0.0.0.0 --vncproxy_url=http://10.205.16.18:6080 --ajax_console_proxy_url=http://10.205.16.18:8000 --novnc_enabled=true --novncproxy_base_url=http://10.205.16.18:6080/vnc_auto.html --vncserver_proxyclient_address=10.205.16.18 --vncserver_listen=10.205.16.18 -compute node:10.205.16.241 --vncproxy_url=http://10.205.16.18:6080 --ajax_console_proxy_url=http://10.205.16.18:8000 --novnc_enabled=true --novncproxy_base_url=http://10.205.16.18:6080/vnc_auto.html --vncserver_proxyclient_address=10.205.16.241 --vncserver_listen=10.205.16.241 And everything works ok. Hope this help. Regards, Gabriel From: 张家龙 zhan...@awcloud.com To: openstack openstack@lists.launchpad.net Sent: Thursday, October 25, 2012 9:43 AM Subject: [Openstack] Questions about novnc with multihost OpenStack Nova Compute(Essex) in multihost Dear all, I have some questions about OpenStack Nova Compute(Essex) using novnc. I build a cluster using 4 computers with OpenStack Nova Compute in multihost. The follows were informations of my cluster: nova01:compute server,api server,controller server 192.168.3.3 nova02:compute server 192.168.3.4 nova03:compute server 192.168.3.5 nova04:compute server 192.168.3.6 And the vms`s fixed was 10.0.0.0/8 Here was my nova.conf: http://pastebin.com/K6ArR1HA While,when i executed the command nova get-vnc-console servername novnc then,error occured. Here were the error informations: 2012-10-25 14:25:27 ERROR nova.rpc.impl_qpid [req-1ad62be7-8eeb-43a5-898c-f3552b9f7748 3faf7062208c456c9a9365ee50bf15cd 561a547e94c7 4ce797d0ef1f4bc91f91] Timed out waiting for RPC response: None 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid Traceback (most recent call last): 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File /usr/lib/python2.6/site-packages/nova/rpc/impl_qpid.py, line 364, in ensure 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid return method(*args, **kwargs) 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File /usr/lib/python2.6/site-packages/nova/rpc/impl_qpid.py, line 413, in _consume 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid nxt_receiver = self.session.next_receiver(timeout=timeout) 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File string, line 6, in next_receiver 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 651, in nex t_receiver 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid raise Empty 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid Empty: None 2012-10-25 14:25:27 TRACE nova.rpc.impl_qpid 2012-10-25 14:25:27 ERROR nova.api.openstack [req-1ad62be7-8eeb-43a5-898c-f3552b9f7748 3faf7062208c456c9a9365ee50bf15cd 561a547e94c7 4ce797d0ef1f4bc91f91] Caught error: Timeout while waiting on RPC response. 2012-10-25 14:25:27 TRACE nova.api.openstack Traceback (most recent call last): 2012-10-25 14:25:27 TRACE nova.api.openstack File /usr/lib/python2.6/site-packages/nova/api/openstack/__init__.py, line 82, in _ _call__ 2012-10-25 14:25:27 TRACE nova.api.openstack return req.get_response(self.application) 2012-10-25 14:25:27 TRACE nova.api.openstack File /usr/lib/python2.6/site-packages/WebOb-1.0.8-py2.6.egg/webob/request.py, line 1053, in get_response 2012-10-25 14:25:27 TRACE nova.api.openstack application, catch_exc_info=False) 2012-10-25 14:25:27 TRACE nova.api.openstack File /usr/lib/python2.6/site-packages/WebOb-1.0.8-py2.6.egg/webob/request.py, line 1022, in call_application 2012-10-25 14:25:27 TRACE nova.api.openstack app_iter = application(self.environ, start_response) 2012-10-25 14:25:27 TRACE nova.api.openstack File /usr/lib/python2.6/site-packages/keystone/middleware/auth_token.py, line 176, in __call__ 2012-10-25 14:25:27 TRACE nova.api.openstack return self.app(env, start_response) 2012-10-25 14:25:27 TRACE nova.api.openstack File /usr/lib/python2.6/site-packages/WebOb-1.0.8-py2.6.egg/webob/dec.py, line 159, in __call__ 2012-10-25 14:25:27 TRACE nova.api.openstack return resp(environ, start_response) 2012-10-25 14:25:27 TRACE nova.api.openstack File /usr/lib/python2.6/site-packages/WebOb-1.0.8-py2.6.egg/webob/dec.py, line 159, in __call__ 2012-10-25 14:25:27 TRACE nova.api.openstack return resp(environ, start_response) 2012-10-25 14:25:27 TRACE nova.api.openstack File /usr/lib/python2.6/site-packages/WebOb-1.0.8-py2.6.egg/webob/dec.py, line 159, in __call__ 2012-10-25 14:25:27 TRACE
Re: [Openstack] [OpenStack][Glance][Nova] How to export images created from running instances?
Hi, I did that. Create snapshot from the running machine, identify the file corresponding to the snapshot. In my case was a qcow2 file and then add to essex with glance add Regards, Gabriel From: Leander Bessa Beernaert leande...@gmail.com To: openstack@lists.launchpad.net Sent: Tuesday, May 29, 2012 2:19 PM Subject: [Openstack] [OpenStack][Glance][Nova] How to export images created from running instances? Hello, Is there any way to export an image created from another instance so that it can be upload elsewhere? In this particular case, i want to export a snapshot created in diablo to use in essex. 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___ 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] Nova-compute doesn't start on reboot, only manually
Hi, It happend to me in case of a server. Investigating I found out that libvirt-bin isn't starting fast enough for nova-compute. So I added this line in /etc/init/nova-compute.conf start libvirt-bin to look as: pre-start script mkdir -p /var/run/nova chown nova:root /var/run/nova/ mkdir -p /var/lock/nova chown nova:root /var/lock/nova/ modprobe nbd start libvirt-bin end script Regards, Gabriel From: Alessandro Tagliapietra tagliapietra.alessan...@gmail.com To: openstack@lists.launchpad.net Sent: Monday, May 28, 2012 11:41 AM Subject: [Openstack] Nova-compute doesn't start on reboot, only manually Hello, i've installed openstack following the ubuntu 12.04 deploy guide, only problem is that nova-compute has to be started manually, by default it doesn't start on boot, this is the error log: 2012-05-27 23:47:14 INFO nova.rpc.common [req-46624af9-9d2a-4901-b635-66f557d3b54c None None] Connected to AMQP server on 10.8.0.1:5672 2012-05-27 23:48:14 ERROR nova.rpc.common [req-46624af9-9d2a-4901-b635-66f557d3b54c None None] Timed out waiting for RPC response: timed out 2012-05-27 23:48:14 TRACE nova.rpc.common Traceback (most recent call last): 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 490, in ensure 2012-05-27 23:48:14 TRACE nova.rpc.common return method(*args, **kwargs) 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 567, in _consume 2012-05-27 23:48:14 TRACE nova.rpc.common return self.connection.drain_events(timeout=timeout) 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/connection.py, line 175, in drain_events 2012-05-27 23:48:14 TRACE nova.rpc.common return self.transport.drain_events(self.connection, **kwargs) 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 238, in drain_events 2012-05-27 23:48:14 TRACE nova.rpc.common return connection.drain_events(**kwargs) 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 57, in drain_events 2012-05-27 23:48:14 TRACE nova.rpc.common return self.wait_multi(self.channels.values(), timeout=timeout) 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 63, in wait_multi 2012-05-27 23:48:14 TRACE nova.rpc.common chanmap.keys(), allowed_methods, timeout=timeout) 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 120, in _wait_multiple 2012-05-27 23:48:14 TRACE nova.rpc.common channel, method_sig, args, content = read_timeout(timeout) 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 94, in read_timeout 2012-05-27 23:48:14 TRACE nova.rpc.common return self.method_reader.read_method() 2012-05-27 23:48:14 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/amqplib/client_0_8/method_framing.py, line 221, in read_method 2012-05-27 23:48:14 TRACE nova.rpc.common raise m 2012-05-27 23:48:14 TRACE nova.rpc.common timeout: timed out 2012-05-27 23:48:14 TRACE nova.rpc.common 2012-05-27 23:48:14 CRITICAL nova [-] Timeout while waiting on RPC response. 2012-05-27 23:48:14 TRACE nova Traceback (most recent call last): 2012-05-27 23:48:14 TRACE nova File /usr/bin/nova-compute, line 49, in module 2012-05-27 23:48:14 TRACE nova service.wait() 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 413, in wait 2012-05-27 23:48:14 TRACE nova _launcher.wait() 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 131, in wait 2012-05-27 23:48:14 TRACE nova service.wait() 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2012-05-27 23:48:14 TRACE nova return self._exit_event.wait() 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2012-05-27 23:48:14 TRACE nova return hubs.get_hub().switch() 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2012-05-27 23:48:14 TRACE nova return self.greenlet.switch() 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2012-05-27 23:48:14 TRACE nova result = function(*args, **kwargs) 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server 2012-05-27 23:48:14 TRACE nova server.start() 2012-05-27 23:48:14 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line
Re: [Openstack] libvirt.xml.template
Hi, On the server when I installed from packages it is in this location: /usr/share/pyshared/nova/virt/libvirt.xml.template Regards, Gabriel From: Razique Mahroua razique.mahr...@gmail.com To: williamherrych...@gmail.com Cc: openstack@lists.launchpad.net Sent: Wednesday, May 23, 2012 10:29 AM Subject: Re: [Openstack] libvirt.xml.template Hi William, as far as I recall, it is not a template, rather a generated template that contains the basic infos of the instance you just spawn. Now if you want to update a running instance properties (dirty way) #1- Connect to the hypervisor #2- $ virsh list- retrieve the domain #3- $virsh edit $domain #4- Shutdown the instance #5- Power on the instance Let me know, Razique William Herry 23 mai 2012 09:18 Hi, I can't find this libvirt.xml.template file with git install, I change this file to make my vm show real cpu rather than QEMU, now, I can't find that file, some one know where it is? I use the recent git packages which is 2012.2 Thanks -- === William Herry williamherrych...@gmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Nuage Co - Razique Mahroua razique.mahr...@gmail.com ___ 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] error in documentation regarding novnc configuration on newly added compute node
Hi all, I observed an error in documentation regarding the configuration needed to be done on additional compute-nodes in order to allow vnc access to instances. From what I understood from doc you just have to copy nova.conf on additional nodes. However there are some changes to made in the nova.conf of the node you want to add or the cloud. The parameters to be changed are:--vncserver_proxyclient_address;--vncserver_listen If on the cloud master they have the values: --vncserver_proxyclient_address=$ip_cloud_master --vncserver_listen=$ip_cloud_master On the newly added compute node they have to be: --vncserver_proxyclient_address=$ip_compute_node --vncserver_listen=$ip_compute_node From my testing and small understanding :) these values are as such: -vncserver_listen is the address that you will find in libvirt.xml corresponding to the instance started on this server. If you put a value different from the ip addresses on this server the instances won't come up. -vncserver_proxyclient_address is the address that nova-consoleauth will associate with the requested token. I don't know if I explained clearly enough so I will give an example. I have 2 servers in my cloud, node01(master_cloud), node02(compute_node). If on node02 the value vncserver_proxyclient_address is $ip_cloud_master after I start an instance on node02 vnc will direct me to $ip_cloud_master:5900 which is an old instance created on node01. If If on node02 the value vncserver_proxyclient_address is $ip_compute_node after I start an instance on node02 vnc will direct me to $ip_compute_node:5900 which is what I am looking for. BINGO!! Regards, Gabriel___ 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] [Compute] nova-compute does not show up as :-) in nova-manage service list
Thanks a lot Joe! Since yesterday I had this issue with nova-compute and after I synchronized the clock on the servers and restart nova-compute on the server with the issue it works great. Thanks a lot! Gabriel From: Joseph Heck he...@me.com To: Gurjar, Unmesh unmesh.gur...@nttdata.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, May 16, 2012 6:41 PM Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list A completely separate potential cause - make sure the time is synchronized between the various hosts. I significant discrepancy there (over 30 seconds I think), will also result in the services thinking they're offline. -joe (this one from hard experience) On May 16, 2012, at 6:48 AM, Gurjar, Unmesh wrote: Restarting libvirt service seemed to resolve the issue for me in the past. Thanks Regards, Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 | unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas From: Leander Bessa Beernaert [mailto:leande...@gmail.com] Sent: Wednesday, May 16, 2012 5:54 PM To: Day, Phil Cc: Gurjar, Unmesh; openstack@lists.launchpad.net Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list I tried 'virsh list', and the command hangs. At first i thought it was because of KVM, since the vm does not support it. I remember having the same problem with diablo, but it would only result in error when the instance was being launched on the compute service. So i changed libvirt_type=kvm to libvirt_type=qemu. However, the problem still remains: virsh list still hangs and compute refuses to leave the state XXX. On Wed, May 16, 2012 at 12:51 PM, Day, Phil philip@hp.com wrote: So the things to check are: - Is the nova-compute service running ? If not the nova-compute.log should show why its failing - If it is running then it probably means that its getting stuck on some long running issue (e.g as down loading an image, problems talking to libvirt, slow response from the DB, etc). XXX in this case means that its slow in updating its services entry rather than failed as such Phil From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf OfLeander Bessa Beernaert Sent: 16 May 2012 12:19 To: Gurjar, Unmesh Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list Shouldn't nova-network and nova-scheduler also fail then, since they share the same config file? If so, that's not what's happening with me, only the compute service is listed as XXX. On Wed, May 16, 2012 at 12:10 PM, Gurjar, Unmesh unmesh.gur...@nttdata.com wrote: Hi Leander, The issue is the Compute is not updating its heartbeat (services table in the nova database), which is causing this. You probably need to check database connection string in the nova.conf on the Compute host and the db connection from the Compute host is working. Thanks Regards, Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 | unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas From: openstack-bounces+unmesh.gurjar=nttdata@lists.launchpad.net [mailto:openstack-bounces+unmesh.gurjar=nttdata@lists.launchpad.net]On Behalf Of Leander Bessa Beernaert Sent: Wednesday, May 16, 2012 4:30 PM To: openstack@lists.launchpad.net Subject: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list Hello, I can't get nova-compute to show up as :-) under 'nova-manager service list'. I've checked the logs and can't find any error or warning. I'm using the default packages shipped with ubuntu 12.04 and have installed everything in a virtual machine. Regards, Leander __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding
[Openstack] instance hangs when registering image
Hi, I have a server on which I run all the the services of openstack. The characteristics of the server are: -cpu:12 cores -ram:24 GB -hdd: 500GB -ubuntu12.04 64bits -openstack essex installed from default repository I observed the following behavior: If while I am registering an image, I am working on a winxp running instance (for example, starting an application) the working instance hangs. Since now I didn't discover a method to regain access to it. I tried to reboot it but without success. In the same context while the glance is registering the image the iostat shows 100% utilization for I/O. Has anyone else observed the issue? Regards, Gabriel ___ 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] dimenssion of vnc console window
Hi, I found a way to change the dimenssion of the window image for the vnc console. The file to be changed is: /usr/share/pyshared/horizon/dashboards/nova/templates/nova/instances_and_volumes/instances/_detail_vnc.html. The parameters are: width=1280 height=900 Regards, Gabriel ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
