[Openstack] A strange quantum agent-list.
Hi, I installed a Grizzly Quantum server node and a Quantum network node based on Ubuntu 12.04, it can works. When I used CML quantum agent-list, I got the strange result as below: *root@nnode01:~# quantum agent-list* * +--++---+---++ * *| id | agent_type | host | alive | admin_state_up |* * +--++---+---++ * *| 0e541238-2e3d-4e51-8bde-ecc9831d8498 | Open vSwitch agent | nnode01.ctrl.cloud.huawei.com | :-)| True |* *| 47ac932f-5f87-4e8f-b6d2-1fe06aaa2b16 | L3 agent | nnode01| xxx | True |* *| 498a10dd-76af-49b0-89a2-3a1e481183e4 | DHCP agent| nnode01.ctrl.cloud.huawei.com| :-) | True |* *| 551690c1-25bb-410a-a6a6-75264335fb18 | Open vSwitch agent | nnode01 | xxx | True |* *| 7c2a1c43-513d-48f9-9ffe-fd69c0c0da2f | Open vSwitch agent | abc.ctrl.cloud.huawei.com | xxx | True |* *| b0b62895-432a-49b7-b806-427715860c37 | DHCP agent| nnode01| xxx | True |* *| babfd8ef-a349-4faa-aa1d-4c80a216c00c | L3 agent | nnode01.ctrl.cloud.huawei.com| :-) | True |* *| bf1a0bf9-9269-4224-b212-9339a89666b7 | Open vSwitch agent | abc | :-) | True |* * +--++---+---++ * Every host get two records in the agent list, the only difference is the field host and the field alive. As my understanding, each host should only get one record in the agent-list table. I am wondering how to just get one record per host. If need more info, please let me know. Much appreciated for any hints. Thanks, Sam ___ 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] Cannot start nova-api service
Hi, I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? Any help is appreciated. From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.* *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.* I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam ___ 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] Cannot start nova-api service
Thank you for your response. I just checked the port 8774, it is available. *root@cctrl-01:/var/log/nova# lsof -i :8774* *root@cctrl-01:/var/log/nova# netstat -anp | grep 8774* *root@cctrl-01:/var/log/nova# service nova-api status* *nova-api stop/waiting* *root@cctrl-01:/var/log/nova# * If need check more things, please let me know. Thanks, Sam On Wed, May 15, 2013 at 10:32 AM, Aaron Rosen aro...@nicira.com wrote: Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote: Hi, I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? Any help is appreciated. From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__ * *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.* *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.* I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam ___ 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] Cannot start nova-api service
Sure, here are my nova-api.log file and nova.conf file: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam On Wed, May 15, 2013 at 10:39 AM, Schwartz, Philip Marc (RIS-BCT) philip.schwa...@lexisnexis.com wrote: Mind sharing your nova.conf with us. You have a misconfiguration of which api’s should be exposed which is causing 2 to use the same port. ** ** **-**Philip ** ** *From:* Openstack [mailto:openstack-bounces+philip.schwartz= lexisnexis@lists.launchpad.net] *On Behalf Of *Aaron Rosen *Sent:* Wednesday, May 15, 2013 1:33 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] Cannot start nova-api service ** ** Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api ** ** On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote: Hi, ** ** I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node.** ** Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql ** ** All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? ** ** Any help is appreciated. ** ** ** ** From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__ * *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server. * *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server. * ** ** I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga ** ** Thanks, Sam ** ** ___ 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
Re: [Openstack] Cannot start nova-api service
Nova-api service can start now. I replace the line enabled_apis=ec2,osapi_compute,metadata with enabled_apis=ec2,osapi_compute at the file nova.conf, the service nova-api can be started. Thanks for all you guys help. Sam On Wed, May 15, 2013 at 1:19 PM, Aaron Rosen aro...@nicira.com wrote: Weird looks fine to me. What happens if you do: sudo service nova-api stop; and then run nova-api in the foreground. $ nova-api Aaron On Wed, May 15, 2013 at 10:58 AM, Sam Su susltd...@gmail.com wrote: Sure, here are my nova-api.log file and nova.conf file: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam On Wed, May 15, 2013 at 10:39 AM, Schwartz, Philip Marc (RIS-BCT) philip.schwa...@lexisnexis.com wrote: Mind sharing your nova.conf with us. You have a misconfiguration of which api’s should be exposed which is causing 2 to use the same port.** ** ** ** **-**Philip ** ** *From:* Openstack [mailto:openstack-bounces+philip.schwartz= lexisnexis@lists.launchpad.net] *On Behalf Of *Aaron Rosen *Sent:* Wednesday, May 15, 2013 1:33 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] Cannot start nova-api service ** ** Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api ** ** On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote:*** * Hi, ** ** I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql ** ** All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? ** ** Any help is appreciated. ** ** ** ** From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__ * *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)*** ** *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__** *** *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.** *** *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.** *** ** ** I also post my nova-api.log file and nova.conf file at pastebin.com
Re: [Openstack] [openstack-dev] Nova PTL candidacy
+1 On Wed, Sep 5, 2012 at 12:19 AM, Michael Still michael.st...@canonical.comwrote: On 09/05/2012 06:03 AM, Matt Joyce wrote: Vish is also a pretty cool guy and doesn't afraid of anything. Vish does a great job -- many hours a day of code review and mentoring, puts up with criticism much more calmly than I think many would, and is a pleasure to work with. Mikal ___ 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] Where can I get start guide about multi-zone.
Hi, I am interesting how to build a multi zone Openstack cluster, but I cannot find a start guide. If someone can give me some links, it will be much appreciated. Thanks, Sam ___ 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] Horizon PTL Candidacy
+1 ;) , if I am a qualified voter. On Fri, Aug 31, 2012 at 5:59 PM, Bhandaru, Malini K malini.k.bhand...@intel.com wrote: +1 :-) -Original Message- From: openstack-bounces+malini.k.bhandaru=intel@lists.launchpad.net[mailto: openstack-bounces+malini.k.bhandaru=intel@lists.launchpad.net] On Behalf Of Devin Carlen Sent: Friday, August 31, 2012 5:52 PM To: Gabriel Hurley Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Horizon PTL Candidacy +1 :) On Aug 31, 2012, at 5:14 PM, Gabriel Hurley wrote: I hereby officially throw my hat in the ring to be Horizon's PTL. Qualifications: I'm a highly active developer on Horizon, and a member of the Horizon Drivers group. I wrote the initial version of python-keystoneclient, and I'm a member of the Keystone Core group as well. I'm also a core committer for the Django web framework on which Horizon is based. I work hard to understand the workings of the entire stack and the needs of the ecosystem at large so we can work together to make the entirety of OpenStack consistent, stable and amazing. I believe VERY strongly in stability, backwards-compatibility, and consistent, properly-versioned APIs. I also have a strong belief in the importance of translation, internationalization and localization to support our international userbases. Contribution over the last six months: I've been the implementer on the majority of the large Folsom blueprints, most of which had to do with improving the flow and ease-of-use of various complicated workflows. I also re-implemented the keystone authentication in Horizon to be dramatically more robust and secure. I've provided a lot of feedback on API revisions in other projects (e.g. Keystone) since those APIs deeply affect Horizon's ability to deliver on a high quality experience. I guided the community's initiative to nail down a complete set of guidelines for developers around internationalization. I've been largely leading the Horizon project in terms of architecture and code review during the Folsom timeframe despite not being the official PTL. Most critical aspects for Horizon in the next 6 months: Full RBAC support; continued focus on reducing the user frustration in complex workflows and interactions; adding more introspective features to reduce boilerplate; cleaner separation of end-user and admin code flows; making the admin dashboard more useful to admins as opposed to just being the same user dashboard except you can see everything in the system; improved file upload mechanisms; Philosophical ideas regarding being a PTL: The foremost role of the PTL is to maintain and convey the long-term vision of the project through day-to-day work (in code, in architecture, in reviews, in answering questions, etc.). Right behind that it is crucial that the PTLs work to guide the community (in gathering consensus on difficult topics, in supporting community members of all types, in maintaining the principles of our community). A close third is that the PTLs must work with each other to ensure the consistency, compatibility, and commonality of all core projects. I'm more than happy to answer any questions or address any concerns people may have. :-) All the best, - 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 ___ 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] After deleted an instance, nobody can create any instance.
Thank you so much for you guys help. I will do these later. Actually this problem can be reproduced in my Essex environment, and I have no idea about how to figure out why it happened, but I'd like to try it. It is highly appreciated if someone can give me some suggestions. Thanks, Sam On Tue, Aug 28, 2012 at 11:08 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- A solution would be deleting the instance table record. Instances table in database has two relational tables. [1] security_group_instance_association [2] instance_info_caches along with the tuples from instances table. - TNS On Wed, Aug 29, 2012 at 11:00 AM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi, I think the best way is to delete the instance from the database : Look at the nova database and fixed_ips table. If you have the old instance number here, try put the instance_id filed into NULL where instance_id is 603. If you have still this issue, find every field corresponding to 603 into the database and delete it. Restart nova-api service, and that should be good. Good luck ! Regards On Wed, Aug 29, 2012 at 4:44 AM, Sam Su susltd...@gmail.com wrote: Hi, I have an Essex cluster with 6 compute nodes and one control node, and it worked fine in the past several months. Last week, since someone deleted an instance in a project, no new instance can be launched in that project. When create a new instance in the project, it displays: *Error: *An error occurred. Please try again. the following error info will come up in the file nova-api.log: 2012-08-28 19:14:23 ERROR nova.api.openstack [req-6fb211c1-60cf-4a69-83e1-f9e7da30b458 6023cea36f784448b667922894ca7102 afdee06258774b2d9e768c08b62dbbf2] Caught error: Remote error: InstanceNotFound Instance 603 could not be found. Here is the info of nova-api.log : http://pastebin.com/evuDMdrU . Actually this instance with id 603 has been deleted, it's very strange. Does anyone has any idea about this issue? By the way, if an existing instance in another project is terminated, the same problem occurs in that project. Thanks ahead, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Emilien Macchi *System Engineer* *www.stackops.com | *emilien.mac...@stackops.com** *|* skype:emilien.macchi* * http://www.stackops.com * * ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. ___ 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] After deleted an instance, nobody can create any instance.
Hi, Thank you all for you suggestions. After updated the table fixed_ips and floating_ips, this problem was eventually fixed. I finally figure out how to reproduce this problem: If an instance associated with a floating IP is terminated, the instance can be successfully terminated, but the floating IP is also associated with the deleted instance in database. Also this is a known issue:https://bugs.launchpad.net/nova/+bug/997763 If someone can make a backport for Essex, that will be great. Thanks, Sam On Tue, Aug 28, 2012 at 10:30 PM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi, I think the best way is to delete the instance from the database : Look at the nova database and fixed_ips table. If you have the old instance number here, try put the instance_id filed into NULL where instance_id is 603. If you have still this issue, find every field corresponding to 603 into the database and delete it. Restart nova-api service, and that should be good. Good luck ! Regards On Wed, Aug 29, 2012 at 4:44 AM, Sam Su susltd...@gmail.com wrote: Hi, I have an Essex cluster with 6 compute nodes and one control node, and it worked fine in the past several months. Last week, since someone deleted an instance in a project, no new instance can be launched in that project. When create a new instance in the project, it displays: *Error: *An error occurred. Please try again. the following error info will come up in the file nova-api.log: 2012-08-28 19:14:23 ERROR nova.api.openstack [req-6fb211c1-60cf-4a69-83e1-f9e7da30b458 6023cea36f784448b667922894ca7102 afdee06258774b2d9e768c08b62dbbf2] Caught error: Remote error: InstanceNotFound Instance 603 could not be found. Here is the info of nova-api.log : http://pastebin.com/evuDMdrU . Actually this instance with id 603 has been deleted, it's very strange. Does anyone has any idea about this issue? By the way, if an existing instance in another project is terminated, the same problem occurs in that project. Thanks ahead, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Emilien Macchi *System Engineer* *www.stackops.com | *emilien.mac...@stackops.com** *|* skype:emilien.macchi* * http://www.stackops.com * * ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. ___ 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] After deleted an instance, nobody can create any instance.
Hi, I have an Essex cluster with 6 compute nodes and one control node, and it worked fine in the past several months. Last week, since someone deleted an instance in a project, no new instance can be launched in that project. When create a new instance in the project, it displays: *Error: *An error occurred. Please try again. the following error info will come up in the file nova-api.log: 2012-08-28 19:14:23 ERROR nova.api.openstack [req-6fb211c1-60cf-4a69-83e1-f9e7da30b458 6023cea36f784448b667922894ca7102 afdee06258774b2d9e768c08b62dbbf2] Caught error: Remote error: InstanceNotFound Instance 603 could not be found. Here is the info of nova-api.log : http://pastebin.com/evuDMdrU . Actually this instance with id 603 has been deleted, it's very strange. Does anyone has any idea about this issue? By the way, if an existing instance in another project is terminated, the same problem occurs in that project. Thanks ahead, Sam ___ 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] VM can't ping self floating IP after a snapshot is taken
Hi, Thank you so much for your help. I replaced the file /usr/share/pyshared/nova/virt/libvirt/connection.py with yours, but it looks like not worked for me. Does it need do any additional thing? Thanks, Sam On Sat, Aug 25, 2012 at 7:03 PM, heut2008 heut2...@gmail.com wrote: for stable/essex the patach is here https://review.openstack.org/#/c/11986/, 2012/8/25 Sam Su susltd...@gmail.com: That's great, thank you for your efforts. Can you make a backport for essex? Sent from my iPhone On Aug 24, 2012, at 7:15 PM, heut2008 heut2...@gmail.com wrote: I have fixed it here https://review.openstack.org/#/c/11925/ 2012/8/25 Sam Su susltd...@gmail.com: Hi, I also reported this bug: https://bugs.launchpad.net/nova/+bug/1040255 If someone can combine you guys solution and get a perfect way to fix this bug, that will be great. BRs, Sam On Thu, Aug 23, 2012 at 9:27 PM, heut2008 heut2...@gmail.com wrote: this bug has been filed here https://bugs.launchpad.net/nova/+bug/1040537 2012/8/24 Vishvananda Ishaya vishvana...@gmail.com: +1 to this. Evan, can you report a bug (if one hasn't been reported yet) and propose the fix? Or else I can find someone else to propose it. Vish On Aug 23, 2012, at 1:38 PM, Evan Callicoat diop...@gmail.com wrote: Hello all! I'm the original author of the hairpin patch, and things have changed a little bit in Essex and Folsom from the original Diablo target. I believe I can shed some light on what should be done here to solve the issue in either case. --- For Essex (stable/essex), in nova/virt/libvirt/connection.py: --- Currently _enable_hairpin() is only being called from spawn(). However, spawn() is not the only place that vifs (veth#) get added to a bridge (which is when we need to enable hairpin_mode on them). The more relevant function is _create_new_domain(), which is called from spawn() and other places. Without changing the information that gets passed to _create_new_domain() (which is just 'xml' from to_xml()), we can easily rewrite the first 2 lines in _enable_hairpin(), as follows: def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) Then, we can move the self._enable_hairpin(instance) call from spawn() up into _create_new_domain(), and pass it xml as follows: [...] self._enable_hairpin(xml) return domain This will run the hairpin code every time a domain gets created, which is also when the domain's vif(s) gets inserted into the bridge with the default of hairpin_mode=0. --- For Folsom (trunk), in nova/virt/libvirt/driver.py: --- There've been a lot more changes made here, but the same strategy as above should work. Here, _create_new_domain() has been split into _create_domain() and _create_domain_and_network(), and _enable_hairpin() was moved from spawn() to _create_domain_and_network(), which seems like it'd be the right thing to do, but doesn't quite cover all of the cases of vif reinsertion, since _create_domain() is the only function which actually creates the domain (_create_domain_and_network() just calls it after doing some pre-work). The solution here is likewise fairly simple; make the same 2 changes to _enable_hairpin(): def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) And move it from _create_domain_and_network() to _create_domain(), like before: [...] self._enable_hairpin(xml) return domain I haven't yet tested this on my Essex clusters and I don't have a Folsom cluster handy at present, but the change is simple and makes sense. Looking at to_xml() and _prepare_xml_info(), it appears that the 'xml' variable _create_[new_]domain() gets is just a python dictionary, and xml['name'] = instance['name'], exactly what _enable_hairpin() was using the 'instance' variable for previously. Let me know if this works, or doesn't work, or doesn't make sense, or if you need an address to send gifts, etc. Hope it's solved! -Evan On Thu, Aug 23, 2012 at 11:20 AM, Sam Su susltd...@gmail.com wrote: Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.com wrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow
[Openstack] HELP: All instances automatically rebooted.
Hi, I have an Essex cluster with 6 compute nodes and one control nodes. All compute nodes are working not any interrupted, for some reason all instances in my cluster automatically rebooted. I am trying to but not figured out why this happened in these couple of days. It's much appreciated if someone can give me some hints about how to deal with this situation. Logs in my /var/log/upstart/nova-compute.log: http://pastebin.com/WYJtS5a5 Let me know if need more info. TIA, Sam ___ 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] HELP: All instances automatically rebooted.
Thanks for your guys help! I guess this problem may be caused by nova packages auto upgrade. I just found these two lines in the file /var/log/kern.log: Aug 23 06:34:33 cnode-01 kernel: [4955691.256036] init: nova-network main process (9191) terminated with status 143 Aug 23 06:34:35 cnode-01 kernel: [4955693.402082] init: nova-compute main process (9275) terminated with status 143 Here is the link for detail of /var/log/kern.log http://pastebin.com/GqH1ju1R Also found these info in /var/log/dpkg.log: 2012-08-23 06:34:33 upgrade nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012.1+stable~20120612-3ee026e-0ubuntu1.3 2012-08-23 06:34:33 status half-configured nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:33 status unpacked nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:33 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:34 status triggers-pending ureadahead 0.100.0-12 2012-08-23 06:34:34 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:34 status triggers-pending ureadahead 0.100.0-12 2012-08-23 06:34:34 status triggers-pending man-db 2.6.1-2 2012-08-23 06:34:34 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:34 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:34 status unpacked nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.3 2012-08-23 06:34:34 status unpacked nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.3 2012-08-23 06:34:34 upgrade nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012.1+stable~20120612-3ee026e-0ubuntu1.3 2012-08-23 06:34:34 status half-configured nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:35 status unpacked nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:35 status half-installed nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:35 status half-installed nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012-08-23 06:34:35 status unpacked nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.3 2012-08-23 06:34:35 status unpacked nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.3 2012-08-23 06:34:35 upgrade nova-compute 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012.1+stable~20120612-3ee026e-0ubuntu1.3 Here is detail: http://pastebin.com/juiSxCue But I am not 100% sure of this. Does anyone knows what it means that a process was terminated with status 143 in Ubuntu 12.04? Thanks ahead, Sam On Mon, Aug 27, 2012 at 5:56 PM, Alejandro Comisario alejandro.comisa...@mercadolibre.com wrote: One of the things i dont like in essex. That the autostart flag in nova.conf with KVM doesnt work with the autostart feature of libvirt/kvm, so if, for some reason you need to restart nova-compute to apply some kind of modification, the instances get soft/hard rebooted because now nova-compute handles the autostart flag from nova.conf Why is that if some one can explain ? On Mon, Aug 27, 2012 at 9:21 PM, Gabe Westmaas gabe.westm...@rackspace.com wrote: Hey Sam, ** ** Is it possible your hypervisors restarted? I see this entry in the logs: ** ** 2012-08-23 06:35:02 INFO nova.compute.manager [req-f1598257-3f35-40e6-b5aa-d47a0e93bfba None None] [instance: ce00ff1d-cf46-44de-9557-c5a0f91c8d67] Rebooting instance after nova-compute restart. ** ** Gabe ** ** *From:* openstack-bounces+gabe.westmaas=rackspace@lists.launchpad.net[mailto: openstack-bounces+gabe.westmaas=rackspace@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Monday, August 27, 2012 8:10 PM *To:* openstack *Subject:* [Openstack] HELP: All instances automatically rebooted. ** ** Hi, ** ** I have an Essex cluster with 6 compute nodes and one control nodes. All compute nodes are working not any interrupted, for some reason all instances in my cluster automatically rebooted. I am trying to but not figured out why this happened in these couple of days. ** ** It's much appreciated if someone can give me some hints about how to deal with this situation. ** ** Logs in my /var/log/upstart/nova-compute.log: http://pastebin.com/WYJtS5a5 ** ** Let me know if need more info. TIA, Sam ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *Alejandro* ___ 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] VM can't ping self floating IP after a snapshot is taken
Hi, I also reported this bug: https://bugs.launchpad.net/nova/+bug/1040255 If someone can combine you guys solution and get a perfect way to fix this bug, that will be great. BRs, Sam On Thu, Aug 23, 2012 at 9:27 PM, heut2008 heut2...@gmail.com wrote: this bug has been filed here https://bugs.launchpad.net/nova/+bug/1040537 2012/8/24 Vishvananda Ishaya vishvana...@gmail.com: +1 to this. Evan, can you report a bug (if one hasn't been reported yet) and propose the fix? Or else I can find someone else to propose it. Vish On Aug 23, 2012, at 1:38 PM, Evan Callicoat diop...@gmail.com wrote: Hello all! I'm the original author of the hairpin patch, and things have changed a little bit in Essex and Folsom from the original Diablo target. I believe I can shed some light on what should be done here to solve the issue in either case. --- For Essex (stable/essex), in nova/virt/libvirt/connection.py: --- Currently _enable_hairpin() is only being called from spawn(). However, spawn() is not the only place that vifs (veth#) get added to a bridge (which is when we need to enable hairpin_mode on them). The more relevant function is _create_new_domain(), which is called from spawn() and other places. Without changing the information that gets passed to _create_new_domain() (which is just 'xml' from to_xml()), we can easily rewrite the first 2 lines in _enable_hairpin(), as follows: def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) Then, we can move the self._enable_hairpin(instance) call from spawn() up into _create_new_domain(), and pass it xml as follows: [...] self._enable_hairpin(xml) return domain This will run the hairpin code every time a domain gets created, which is also when the domain's vif(s) gets inserted into the bridge with the default of hairpin_mode=0. --- For Folsom (trunk), in nova/virt/libvirt/driver.py: --- There've been a lot more changes made here, but the same strategy as above should work. Here, _create_new_domain() has been split into _create_domain() and _create_domain_and_network(), and _enable_hairpin() was moved from spawn() to _create_domain_and_network(), which seems like it'd be the right thing to do, but doesn't quite cover all of the cases of vif reinsertion, since _create_domain() is the only function which actually creates the domain (_create_domain_and_network() just calls it after doing some pre-work). The solution here is likewise fairly simple; make the same 2 changes to _enable_hairpin(): def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) And move it from _create_domain_and_network() to _create_domain(), like before: [...] self._enable_hairpin(xml) return domain I haven't yet tested this on my Essex clusters and I don't have a Folsom cluster handy at present, but the change is simple and makes sense. Looking at to_xml() and _prepare_xml_info(), it appears that the 'xml' variable _create_[new_]domain() gets is just a python dictionary, and xml['name'] = instance['name'], exactly what _enable_hairpin() was using the 'instance' variable for previously. Let me know if this works, or doesn't work, or doesn't make sense, or if you need an address to send gifts, etc. Hope it's solved! -Evan On Thu, Aug 23, 2012 at 11:20 AM, Sam Su susltd...@gmail.com wrote: Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.com wrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: I ran into some similar issues with the _enable_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though
Re: [Openstack] VM can't ping self floating IP after a snapshot is taken
That's great, thank you for your efforts. Can you make a backport for essex? Sent from my iPhone On Aug 24, 2012, at 7:15 PM, heut2008 heut2...@gmail.com wrote: I have fixed it here https://review.openstack.org/#/c/11925/ 2012/8/25 Sam Su susltd...@gmail.com: Hi, I also reported this bug: https://bugs.launchpad.net/nova/+bug/1040255 If someone can combine you guys solution and get a perfect way to fix this bug, that will be great. BRs, Sam On Thu, Aug 23, 2012 at 9:27 PM, heut2008 heut2...@gmail.com wrote: this bug has been filed here https://bugs.launchpad.net/nova/+bug/1040537 2012/8/24 Vishvananda Ishaya vishvana...@gmail.com: +1 to this. Evan, can you report a bug (if one hasn't been reported yet) and propose the fix? Or else I can find someone else to propose it. Vish On Aug 23, 2012, at 1:38 PM, Evan Callicoat diop...@gmail.com wrote: Hello all! I'm the original author of the hairpin patch, and things have changed a little bit in Essex and Folsom from the original Diablo target. I believe I can shed some light on what should be done here to solve the issue in either case. --- For Essex (stable/essex), in nova/virt/libvirt/connection.py: --- Currently _enable_hairpin() is only being called from spawn(). However, spawn() is not the only place that vifs (veth#) get added to a bridge (which is when we need to enable hairpin_mode on them). The more relevant function is _create_new_domain(), which is called from spawn() and other places. Without changing the information that gets passed to _create_new_domain() (which is just 'xml' from to_xml()), we can easily rewrite the first 2 lines in _enable_hairpin(), as follows: def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) Then, we can move the self._enable_hairpin(instance) call from spawn() up into _create_new_domain(), and pass it xml as follows: [...] self._enable_hairpin(xml) return domain This will run the hairpin code every time a domain gets created, which is also when the domain's vif(s) gets inserted into the bridge with the default of hairpin_mode=0. --- For Folsom (trunk), in nova/virt/libvirt/driver.py: --- There've been a lot more changes made here, but the same strategy as above should work. Here, _create_new_domain() has been split into _create_domain() and _create_domain_and_network(), and _enable_hairpin() was moved from spawn() to _create_domain_and_network(), which seems like it'd be the right thing to do, but doesn't quite cover all of the cases of vif reinsertion, since _create_domain() is the only function which actually creates the domain (_create_domain_and_network() just calls it after doing some pre-work). The solution here is likewise fairly simple; make the same 2 changes to _enable_hairpin(): def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) And move it from _create_domain_and_network() to _create_domain(), like before: [...] self._enable_hairpin(xml) return domain I haven't yet tested this on my Essex clusters and I don't have a Folsom cluster handy at present, but the change is simple and makes sense. Looking at to_xml() and _prepare_xml_info(), it appears that the 'xml' variable _create_[new_]domain() gets is just a python dictionary, and xml['name'] = instance['name'], exactly what _enable_hairpin() was using the 'instance' variable for previously. Let me know if this works, or doesn't work, or doesn't make sense, or if you need an address to send gifts, etc. Hope it's solved! -Evan On Thu, Aug 23, 2012 at 11:20 AM, Sam Su susltd...@gmail.com wrote: Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.com wrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote
Re: [Openstack] VM can't ping self floating IP after a snapshot is taken
Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.comwrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: I ran into some similar issues with the _*enable*_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. ** ** Just thought I’d share my similar pain. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 19, 2012 11:50 AM *To:* Brian Haley *Cc:* openstack *Subject:* Re: [Openstack] VM can't ping self floating IP after a snapshot is taken ** ** Thank you for your support. ** ** I checked the file nova/virt/libvirt/connection.py, the sentence self._enable_hairpin(instance) is already added to the function _hard_reboot(). It looks like there are some difference between taking snapshot and reboot instance. I tried to figure out how to fix this bug but failed. * *** ** ** It will be much appreciated if anyone can give some hints. ** ** Thanks, Sam ** ** On Thu, Jul 19, 2012 at 8:37 AM, Brian Haley brian.ha...@hp.com wrote: On 07/17/2012 05:56 PM, Sam Su wrote: Hi, Just This always happens in Essex release. After I take a snapshot of my VM ( I tried Ubuntu 12.04 or CentOS 5.8), VM can't ping its self floating IP; before I take a snapshot though, VM can ping its self floating IP. This looks closely related to https://bugs.launchpad.net/nova/+bug/933640, but still a little different. In 933640, it sounds like VM can't ping its self floating IP regardless whether we take a snapshot or not. Any suggestion to make an easy fix? And what is the root cause of the problem? It might be because there's a missing _enable_hairpin() call in the reboot() function. Try something like this... nova/virt/libvirt/connection.py, _hard_reboot(): self._create_new_domain(xml) +self._enable_hairpin(instance) self.firewall_driver.apply_instance_filter(instance, network_info) At least that's what I remember doing myself recently when testing after a reboot, don't know about snapshot. Folsom has changed enough that something different would need to be done there. -Brian ** ** ___ 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] VM can't ping self floating IP after a snapshot is taken
My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote: I ran into some similar issues with the _*enable*_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. ** ** Just thought I’d share my similar pain. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 19, 2012 11:50 AM *To:* Brian Haley *Cc:* openstack *Subject:* Re: [Openstack] VM can't ping self floating IP after a snapshot is taken ** ** Thank you for your support. ** ** I checked the file nova/virt/libvirt/connection.py, the sentence self._enable_hairpin(instance) is already added to the function _hard_reboot(). It looks like there are some difference between taking snapshot and reboot instance. I tried to figure out how to fix this bug but failed. ** ** It will be much appreciated if anyone can give some hints. ** ** Thanks, Sam ** ** On Thu, Jul 19, 2012 at 8:37 AM, Brian Haley brian.ha...@hp.com wrote:** ** On 07/17/2012 05:56 PM, Sam Su wrote: Hi, Just This always happens in Essex release. After I take a snapshot of my VM ( I tried Ubuntu 12.04 or CentOS 5.8), VM can't ping its self floating IP; before I take a snapshot though, VM can ping its self floating IP. This looks closely related to https://bugs.launchpad.net/nova/+bug/933640, but still a little different. In 933640, it sounds like VM can't ping its self floating IP regardless whether we take a snapshot or not. Any suggestion to make an easy fix? And what is the root cause of the problem? It might be because there's a missing _enable_hairpin() call in the reboot() function. Try something like this... nova/virt/libvirt/connection.py, _hard_reboot(): self._create_new_domain(xml) +self._enable_hairpin(instance) self.firewall_driver.apply_instance_filter(instance, network_info) At least that's what I remember doing myself recently when testing after a reboot, don't know about snapshot. Folsom has changed enough that something different would need to be done there. -Brian ** ** ___ 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] Cannot associate/dissociate an floating IP to an instance from API
Hi,
I am trying to associate an floating IP to an instance from API in my Essex
environment, and get the error 404 Not Found. I found someone have filed
an invalid bug (the link is https://bugs.launchpad.net/nova/+bug/917064), I
followed the information and tried several request formats as below, but
all are failed.
1. curl -k -D - -H X-Auth-Token: 7f48c07af3b842d1b9c0f15a37ddd956 -X
'POST' -d @test.json -v
http://localhost:8774/v1.1/53869b3cd0cc40a28a826422a37622da/os-floating-ips/1/associate-H
'Content-type: application/json'
The file test.json:
*{*
*associate_address : {*
* fixed_ip : 192.168.20.3*
*}*
*}*
*
*
2. curl -k -D - -H X-Auth-Token: 7f48c07af3b842d1b9c0f15a37ddd956 -X
'POST' -d @test.json -v
http://localhost:8774/v1.1/53869b3cd0cc40a28a826422a37622da/os-floating-ips/1/action
-H 'Content-type: application/json'
The file test.json:
*{*
*addFloatingIp: {*
* address : 10.100.20.17*
*},*
*associate_address : {*
* fixed_ip : 192.168.20.3*
*}*
*}*
3. curl -k -D - -H X-Auth-Token: 7f48c07af3b842d1b9c0f15a37ddd956 -X
'POST' -d @test.json -v
http://localhost:8774/v1.1/53869b3cd0cc40a28a826422a37622da/os-floating-ips/1/addFloatingIp
-H 'Content-type: application/json'
The file test.json:
*{*
*associate_address : {*
* fixed_ip : 192.168.20.3*
*}*
*}*
I am wondering what is the correct request format or just a bug? It will
be much appreciated if someone can give me some hints.
Thanks,
Sam
___
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] VM can't ping self floating IP after a snapshot is taken
Hi, Just This always happens in Essex release. After I take a snapshot of my VM ( I tried Ubuntu 12.04 or CentOS 5.8), VM can't ping its self floating IP; before I take a snapshot though, VM can ping its self floating IP. This looks closely related to https://bugs.launchpad.net/nova/+bug/933640, but still a little different. In 933640, it sounds like VM can't ping its self floating IP regardless whether we take a snapshot or not. Any suggestion to make an easy fix? And what is the root cause of the problem? Thanks, Sam ___ 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] About images list in dashboard
I tried this backport in my mini environment, it looks like works fine. Thank you, Gabriel. Thanks, Sam On Sun, Jul 15, 2012 at 12:19 AM, Gabriel Hurley gabriel.hur...@nebula.comwrote: Already happened. https://github.com/openstack/horizon/commit/fec36c45dbbca4f3b446cdb231f53e4ab2f6f507 ** ** Since they didn’t specify when/how they installed Essex, I’m going to assume they got a version that did not include this backport. ** ** All the best, ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Matt Joyce *Sent:* Friday, July 13, 2012 5:13 PM *To:* Christian Parpart *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] About images list in dashboard ** ** I agree if someone wants to commit a backported fix. This makes sense to do. It's a pretty significant bug for essex users. -Matt On Fri, Jul 13, 2012 at 3:00 PM, Christian Parpart tra...@gmail.com wrote: On Fri, Jul 13, 2012 at 10:56 PM, John Postlethwait john.postlethw...@nebula.com wrote: Well, it sounds like this issue only happens in Essex, and is no longer an issue in Folsom, so the bug will just be closed as invalid, as it is now fixed in the newer code... ** ** Please backport this bug then. That is, the bug report indeed makes absolutely sense to me. :-) ** ** John Postlethwait Nebula, Inc. 206-999-4492 ** ** On Friday, July 13, 2012 at 1:36 PM, Sam Su wrote: Thank you for you guys' suggestions. ** ** Even so, I'd like to file a bug to track this issue, if someone else have the same problem, they would know what happened and what progressed from the bug trace. ** ** Sam ** ** On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: Glance pagination was added in Folsom. Adding a bug for this won’t help since it’s already been added in the current code. - Gabriel *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *John Postlethwait *Sent:* Friday, July 13, 2012 12:05 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] About images list in dashboard Hi Sam, Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug John Postlethwait Nebula, Inc. 206-999-4492 On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. Sam On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.com wrote: Thank you for your suggestion. I can see all images in other tenants from dashboard, so I think the images type should be ok. On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.com wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 05, 2012 11:20 AM *To:* openstack *Subject:* [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: *Image Name Type Status Public Container Format Actions* CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images
Re: [Openstack] About images list in dashboard
Thank you for you guys' suggestions. Even so, I'd like to file a bug to track this issue, if someone else have the same problem, they would know what happened and what progressed from the bug trace. Sam On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote: Glance pagination was added in Folsom. Adding a bug for this won’t help since it’s already been added in the current code. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *John Postlethwait *Sent:* Friday, July 13, 2012 12:05 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] About images list in dashboard ** ** Hi Sam, ** ** Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug ** ** ** ** ** ** John Postlethwait Nebula, Inc. 206-999-4492 ** ** On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. ** ** If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. ** ** ** ** Sam ** ** ** ** On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.com wrote: Thank you for your suggestion. ** ** I can see all images in other tenants from dashboard, so I think the images type should be ok. ** ** ** ** ** ** On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.com wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 05, 2012 11:20 AM *To:* openstack *Subject:* [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: *Image Name Type Status Public Container Format Actions* CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result)* *** # nova image-list +-+--+- --+--+ | ID | Name | Status |Server | +-+--+--- +--+ | 18b130ce-a815-4671-80e8-9308a7b6fc6d | ubuntu-12.04-server-amd64 | ACTIVE | | | 388d16ce-b80b-4e9e-b8db-db6dce6f4a83 | ubuntu-12.04-server-amd64-kernel | ACTIVE | | | 8d9505ce-0974-431d-a53d-e9ed6dc89033 | CentOS-6.2-x86_64 | ACTIVE | | | 99be14c0-3b15-470b-9e2d-a9d7e2242c7a | CentOS-5.8-x86_64 | ACTIVE | | | a486733f-c011-4fa1-8ce2-553084f9bc0e | ubuntu-11.10-server-amd64 | ACTIVE | | | ec7f9c5d-48b4-40e3-8e36-87fbdd099fee | ubuntu-12.04-server-amd64-ramdisk | ACTIVE | | | fbb3a182-e610-448f-8042-0b1addb90750 | ubuntu-12.04-server-amd64-hostname | ACTIVE | | +-+--+--- +--+ I am wondering how
[Openstack] About images list in dashboard
Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: *Image Name Type Status Public Container Format Actions* CentOS-6.2-x86_64 Image Active Yes OVF Launch CentOS-5.8-x86_64 Image Active Yes OVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result) # nova image-list +-+--+- --+--+ | ID | Name | Status |Server | +-+--+--- +--+ | 18b130ce-a815-4671-80e8-9308a7b6fc6d | ubuntu-12.04-server-amd64 | ACTIVE | | | 388d16ce-b80b-4e9e-b8db-db6dce6f4a83 | ubuntu-12.04-server-amd64-kernel | ACTIVE | | | 8d9505ce-0974-431d-a53d-e9ed6dc89033 | CentOS-6.2-x86_64 | ACTIVE | | | 99be14c0-3b15-470b-9e2d-a9d7e2242c7a | CentOS-5.8-x86_64 | ACTIVE | | | a486733f-c011-4fa1-8ce2-553084f9bc0e | ubuntu-11.10-server-amd64 | ACTIVE | | | ec7f9c5d-48b4-40e3-8e36-87fbdd099fee | ubuntu-12.04-server-amd64-ramdisk | ACTIVE | | | fbb3a182-e610-448f-8042-0b1addb90750 | ubuntu-12.04-server-amd64-hostname | ACTIVE | | +-+--+--- +--+ I am wondering how to make all these images seen in my the dashboard? It will be much appreciated if someone can give me some hints about this. Thanks, Sam ___ 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] Where can I get the nova-volumes info?
Hi, I have a formatted nova-volume disk, if cannot associate the volume disk to a VM, does anyone knows where can I find out the volume disk format (such as ext3 or ext4)? Thanks ahead, Sam ___ 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] About volume recover after reboot a compute node.
Hi, I have a mini Openstack cloud based on Essex, there are one compute node with nova-volumes and one control node in this environment. In the compute node, there is an instance attached it's volume. After reboot the compute node, the instance lost it's volume, but the instance is still attached the volume in the database. I am wondering how to recover volume to attach it's instance after the host compute node is rebooted? It's much appreciated if someone can give me some tips. Thanks, Sam ___ 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] About over-commit memory
Hi, I have a mini openstack environment with one compute node and one nova control node. There is 4G memory in the compute node, and I have allocated 2 VMs with 2G memory for each VM. When I try to create another VM , I get the error as below: http://pastebin.com/QZMQvXtB I am wondering whether Openstack has support memory overcommit? How to do this? It will be much appreciated If someone can give me some hints about this in convenience. Thanks, Sam ___ 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] About over-commit memory
Hi Vish, Thank you for your response. I added a 'line ram_allocation_ratio=10' in nova.conf, then restarted nova-scheduler in control node. after that was done, I tried to create a VM, but it still failed, and the debug info is showing as below: http://pastebin.com/RDHb9fDU Can you help me to take a look at the error info at your convenience? Thanks, Sam On Thu, Jun 21, 2012 at 12:23 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: Try setting: ram_allocation_ratio=10 in your nova.conf (it defaults to 1.5) Vish On Jun 21, 2012, at 11:34 AM, Sam Su wrote: Hi, I have a mini openstack environment with one compute node and one nova control node. There is 4G memory in the compute node, and I have allocated 2 VMs with 2G memory for each VM. When I try to create another VM , I get the error as below: http://pastebin.com/QZMQvXtB I am wondering whether Openstack has support memory overcommit? How to do this? It will be much appreciated If someone can give me some hints about this in convenience. Thanks, Sam ___ 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] About over-commit memory
Hi Wolf, I used the flavor m1.tiny to create the third VM so it only need 512M RAM. I am using the qemu in my mini openstack environment. If need more further info, please let me know. Thanks, Sam On Thu, Jun 21, 2012 at 3:29 PM, Wolfgang Richter w...@cs.cmu.edu wrote: The third VM is of the same flavor as the other two? At least, it is only trying to use 2GB RAM as well? Which hypervisor is in use (kvm)? -- Wolf On Thu, Jun 21, 2012 at 6:03 PM, Sam Su susltd...@gmail.com wrote: Hi Vish, Thank you for your response. I added a 'line ram_allocation_ratio=10' in nova.conf, then restarted nova-scheduler in control node. after that was done, I tried to create a VM, but it still failed, and the debug info is showing as below: http://pastebin.com/RDHb9fDU Can you help me to take a look at the error info at your convenience? Thanks, Sam On Thu, Jun 21, 2012 at 12:23 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Try setting: ram_allocation_ratio=10 in your nova.conf (it defaults to 1.5) Vish On Jun 21, 2012, at 11:34 AM, Sam Su wrote: Hi, I have a mini openstack environment with one compute node and one nova control node. There is 4G memory in the compute node, and I have allocated 2 VMs with 2G memory for each VM. When I try to create another VM , I get the error as below: http://pastebin.com/QZMQvXtB I am wondering whether Openstack has support memory overcommit? How to do this? It will be much appreciated If someone can give me some hints about this in convenience. Thanks, Sam ___ 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] About over-commit memory
Hi Vish, Great, it works now, thank you so much for your help. Does it means there is not any limit for the the memory overcommit ratio? If the physical memory is 4G in compute node and the swap partition is 4G as well, whether can I use more than 8G RAM for VMs? Thanks, Sam On Thu, Jun 21, 2012 at 3:13 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: I just noticed there is a bug in ram_allocation_ratio, it actually only multiplies the check for free ram which doen't do a lot. Bug filed here: https://bugs.launchpad.net/nova/+bug/1016273 In the meantime, to overcommit you will have to disable the ram check completely by setting the following set of enabled filters in conf. scheduler_default_filters=AvailabilityZoneFilter,ComputeFilter Vish On Jun 21, 2012, at 3:03 PM, Sam Su wrote: Hi Vish, Thank you for your response. I added a 'line ram_allocation_ratio=10' in nova.conf, then restarted nova-scheduler in control node. after that was done, I tried to create a VM, but it still failed, and the debug info is showing as below: http://pastebin.com/RDHb9fDU Can you help me to take a look at the error info at your convenience? Thanks, Sam On Thu, Jun 21, 2012 at 12:23 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Try setting: ram_allocation_ratio=10 in your nova.conf (it defaults to 1.5) Vish On Jun 21, 2012, at 11:34 AM, Sam Su wrote: Hi, I have a mini openstack environment with one compute node and one nova control node. There is 4G memory in the compute node, and I have allocated 2 VMs with 2G memory for each VM. When I try to create another VM , I get the error as below: http://pastebin.com/QZMQvXtB I am wondering whether Openstack has support memory overcommit? How to do this? It will be much appreciated If someone can give me some hints about this in convenience. Thanks, Sam ___ 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] HELP: About Nova long time response when taking snapshot
Hi, I have a multi-nodes openstack environment, including a control node running Glance, nova-api, nova-scheduler, nova-network, rabbitmq, mysql, keystone and dashboard services, and two compute nodes running nova-compute and nova-network services. When someone is taking a snapshot for his/her VMs, the Openstack system looks like very busy and it will take a long time (at least 3 to 4 minutes in this situation and regular time is in 30 seconds) to create a VM. I wonder is there any solution to optimize this system so that it can response quickly. it will be much appreciated if someone could give me some hints about this. Thanks, Sam ___ 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] HELP: About Nova long time response when taking snapshot
Hi Yun, Thank you for your quick response. Yes, I am using essex release. I added one line 'libvirt_nonblocking=true' in nova.conf, took a snapshot, then created a VM, it also needs a long time(about 3 minutes) during the task of 'networking' and 'spawning' -- I think this is because I was snapshoting at the same time. I am thinking whether it can get better response time if move the glance service to another server or deploy multi-node glance. I wonder whether glance support multi-nodes mode and where can I get the instruction. All help are appreciated. Thanks, sam On Tue, May 15, 2012 at 4:43 AM, Yun Mao yun...@gmail.com wrote: If you are using the essex release, have you tried to enable the libvirt_nonblocking option? Yun On Tue, May 15, 2012 at 2:18 AM, Sam Su susltd...@gmail.com wrote: Hi, I have a multi-nodes openstack environment, including a control node running Glance, nova-api, nova-scheduler, nova-network, rabbitmq, mysql, keystone and dashboard services, and two compute nodes running nova-compute and nova-network services. When someone is taking a snapshot for his/her VMs, the Openstack system looks like very busy and it will take a long time (at least 3 to 4 minutes in this situation and regular time is in 30 seconds) to create a VM. I wonder is there any solution to optimize this system so that it can response quickly. it will be much appreciated if someone could give me some hints about this. Thanks, Sam ___ 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] Laptop Demo Environment
I also recommend you use devstack to build an all-in-one Openstack environment. I have searched so many instructions in Google, but few of them can works fine. Sam On Tue, Apr 10, 2012 at 6:34 AM, Lance Haig lh...@haigmail.com wrote: On 10/04/12 14:09, Vaze, Mandar wrote: Would http://devstack.org/guides/**single-machine.htmlhttp://devstack.org/guides/single-machine.htmlwork for you ? (Or does it need to be installed from packages) -Mandar Hi Mandar, I used devstack before and I would prefer to build the environment manually to learn how each piece behaves and integrates Thanks Lance -- This message was scanned by Better Hosted and is believed to be clean. http://www.betterhosted.com __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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
