Re: [Openstack] curl example for quantum api create port
the fastest way to learn the API is to run quantum client with -v: # quantum port-create --request-format xml net1 -v . REQ: curl -i http://localhost:9696/v2.0/ports.xml -X POST -H X-Auth-Token: 22ac5a38128949adaa852282a9ec8bd3 -H Content-Type: application/xml -H Accept: application/xml -H User-Agent: python-quantumclient -d '?xml version=1.0 encoding=UTF-8? port xmlns=http://openstack.org/quantum/api/v2.0; xmlns:quantum=http://openstack.org/quantum/api/v2.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;network_id671cc79b-5f53-4e68-ba35-7effbe015706/network_idadmin_state_up quantum:type=boolTrue/admin_state_up/port' On 05/24/2013 06:47 PM, Thomas Kärgel wrote: Hi, i'm tryning to create a port in quantum via a curl: curl -H X-Auth-Token: 978ed39cd13645c5a7024ad9d954c914 -d '?xml version=1.0 encoding=UTF-8?port admin_state_up=true device_id=d21f15c5-a7f0-47eb-854d-330e1227f572 name=test network_id=9e770d5c-238a-4317-a129-9fd96dca8a6b/port' -H Content-Type: application/xml; charset=UTF-8 -H Accept: application/xml http://quantumserver:9696/v2.0/ports.xml the answer i get from quantum is: QuantumError Unable to find 'port' in request body /QuantumError What am i doing wrong? I think I'm not seeing the forest for the trees. Best regards Thomas ___ 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 Agents and Reporting State
It seems there is a gap between these two packages, can u upgrade the openstack quantum to latest git repo? On 05/23/2013 08:08 AM, Craig E. Ward wrote: I'm configuring a single-node installation of the Grizzly release and I am having some strange issues with the Quantum agents. The install using quantum-linuxbridge-agent, quantum-l3-agent, and quantum-dhcp-agent. Each on is logging the error: Failed reporting state! The end of the stack trace indicates that the number arguments to some call was incorrect. dhcp-agent:TypeError: lambda() takes exactly 2 arguments (3 given) l3_agent: TypeError: lambda() takes exactly 2 arguments (3 given) linuxbridge-agent: TypeError: lambda() takes exactly 2 arguments (3 given) The services are connecting to the RabbitMQ server. Does this indicate a mismatch in some driver that sites between the agents and the RabbitMQ server? Has anyone else seen this type of error before? The packages I'm using are openstack-quantum-2013.1-3.el6.noarch and openstack-quantum-linuxbridge-2013.1-3.el6.noarch. Any suggestions will be appreciated. Thanks, Craig ___ 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 rpc timeout problem
Can u give us your quantum server log? On 04/02/2013 04:35 PM, Dennis Højgaard wrote: I really need some help on quantum.. i've been trying to find a solution on an error for many days now, but google has really betrayed me. I hope there is someone who can help me: I have quantum-server on my cloud-controller node and a network node with quantum-dhcp and l3 agent. It is set up according to this guide: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst In my quantum l3 and dhcp logs i get the following error: Timeout: Timeout while waiting on RPC response I know that the network node establishes the connection to rabbitmq because it says so in the rabbitmq-server log... I hope someone can help me... This is the log from dhcp-agent on network node: 2013-04-02 10:33:13DEBUG [amqplib] Closed channel #1 2013-04-02 10:33:13DEBUG [amqplib] using channel_id: 1 2013-04-02 10:33:13DEBUG [amqplib] Channel open 2013-04-02 10:33:13ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 112, in sync_state active_networks = set(self.plugin_rpc.get_active_networks()) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 260, in get_active_networks topic=self.topic) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/proxy.py, line 80, in call return rpc.call(context, self._get_topic(topic), msg, timeout) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/__init__.py, line 102, in call return _get_impl().call(cfg.CONF, context, topic, msg, timeout) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 712, in call rpc_amqp.get_connection_pool(conf, Connection)) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 368, in call rv = list(rv) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 329, in __iter__ self.done() File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ self.gen.next() File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py, line 326, in __iter__ self._iterator.next() File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 595, in iterconsume yield self.ensure(_error_callback, _consume) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 526, in ensure error_callback(e) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/impl_kombu.py, line 576, in _error_callback raise rpc_common.Timeout() Timeout: Timeout while waiting on RPC response. ___ 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] Grizzly G3+RC1 - Quantum DHCP problem...
It seems be about sudo. to create one sudo file under /etc/sudoers.d mine is: nova_sudoers: Defaults:gongysh !requiretty gongysh ALL = (ALL) NOPASSWD: ALL On 03/20/2013 09:37 AM, Martinx - ジェームズ wrote: Hi! I just rollback to the default namespace options, my Instance now get its IP without problem. But, the message from my first e-mail on this thread, still persist... I tried to enable quantum metadata proxy stuff but, nothing changes... The following error keeps rolling at my /var/log/quantum/dhcp-agent.log: --- ... Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' --- I tried everything I could... But this message persist... The namespaces are enabled, look: ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r 10.33.14.0/24 http://10.33.14.0/24 dev tapeb27823a-5e proto kernel scope link src 10.33.14.2 What can I do? Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
that depends what user is running the dhcp agent. On 03/20/2013 09:52 AM, Martinx - ジェームズ wrote: My /etc/sudoers.d/nova_sudoers contains: -- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap -- Do I need to change it? Tks! Thiago On 19 March 2013 22:46, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: It seems be about sudo. to create one sudo file under /etc/sudoers.d mine is: nova_sudoers: Defaults:gongysh !requiretty gongysh ALL = (ALL) NOPASSWD: ALL On 03/20/2013 09:37 AM, Martinx - ジェームズ wrote: Hi! I just rollback to the default namespace options, my Instance now get its IP without problem. But, the message from my first e-mail on this thread, still persist... I tried to enable quantum metadata proxy stuff but, nothing changes... The following error keeps rolling at my /var/log/quantum/dhcp-agent.log: --- ... Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' --- I tried everything I could... But this message persist... The namespaces are enabled, look: ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r 10.33.14.0/24 http://10.33.14.0/24 dev tapeb27823a-5e proto kernel scope link src 10.33.14.2 What can I do? Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48 DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48 DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48 ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
we can deploy many dhcp agents and l3 agents. for multihost, we are doing: https://review.openstack.org/#/c/24771/ On 03/20/2013 10:13 AM, tommy(小包) wrote: i worry about performance of quantum use subnet in one dhcp l3 agent work for it(more dhcp l3 just for backup) if quantum have any solution to performance about quantum dhcp l3 (may be one compute node have dhcp l3 agent work for local VMs) Thanks, Tommy 2013/3/20 Martinx - ジェ�`ムズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com User quantum running `python /usr/bin/quantum-dhcp-agent'... On 19 March 2013 22:55, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: that depends what user is running the dhcp agent. On 03/20/2013 09:52 AM, Martinx - ジェ�`ムズ wrote: My /etc/sudoers.d/nova_sudoers contains: -- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap -- Do I need to change it? Tks! Thiago On 19 March 2013 22:46, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: It seems be about sudo. to create one sudo file under /etc/sudoers.d mine is: nova_sudoers: Defaults:gongysh !requiretty gongysh ALL = (ALL) NOPASSWD: ALL On 03/20/2013 09:37 AM, Martinx - ジェ�`ムズ wrote: Hi! I just rollback to the default namespace options, my Instance now get its IP without problem. But, the message from my first e-mail on this thread, still persist... I tried to enable quantum metadata proxy stuff but, nothing changes... The following error keeps rolling at my /var/log/quantum/dhcp-agent.log: --- ... Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' --- I tried everything I could... But this message persist... The namespaces are enabled, look: ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r 10.33.14.0/24 http://10.33.14.0/24 dev tapeb27823a-5e proto kernel scope link src 10.33.14.2 What can I do? Tks, Thiago On 19 March 2013 20:35, Martinx - ジェ�`ムズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェ�`ムズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48 DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91
Re: [Openstack] glance error......
It seems the error is related to sql_connection for your glance. On 12/03/2012 08:21 PM, Chris St wrote: Hello, I am a newbie in Openstack and I try to get a first overview. For my overview I want to install and implement OpenStack. I have installed two CentOS Server (Version 6.3) with all actual updates. For the installation I followed the documentation for the Fedora/RHEL/CentOS here: http://docs.openstack.org/folsom/openstack-compute/install/yum/content/ Now I have a problem after the glance installation, but couldn't figure out why this error happens or what's the problem. I am at the point were I try to upload a Image (http://docs.openstack.org/folsom/openstack-compute/install/yum/content/images-verifying-install.html). When I try to do this after a long time period I run into a timeout. The api.log gives me this errors: 2012-12-03 13:16:53 18450 TRACE glance Traceback (most recent call last): 2012-12-03 13:16:53 18450 TRACE glance File /usr/bin/glance-api, line 57, in module 2012-12-03 13:16:53 18450 TRACE glance server.wait() 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/glance/common/wsgi.py, line 241, in wait 2012-12-03 13:16:53 18450 TRACE glance self.wait_on_children() 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/glance/common/wsgi.py, line 226, in wait_on_children 2012-12-03 13:16:53 18450 TRACE glance self.run_child() 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/glance/common/wsgi.py, line 256, in run_child 2012-12-03 13:16:53 18450 TRACE glance self.run_server() 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/glance/common/wsgi.py, line 275, in run_server 2012-12-03 13:16:53 18450 TRACE glance eventlet.wsgi.server(self.sock, self.app_func(), 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/glance/common/config.py, line 186, in load_paste_app 2012-12-03 13:16:53 18450 TRACE glance app = deploy.loadapp(config:%s % conf_file, name=app_name) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 247, in loadapp 2012-12-03 13:16:53 18450 TRACE glance return loadobj(APP, uri, name=name, **kw) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 272, in loadobj 2012-12-03 13:16:53 18450 TRACE glance return context.create() 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 710, in create 2012-12-03 13:16:53 18450 TRACE glance return self.object_type.invoke(self) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 203, in invoke 2012-12-03 13:16:53 18450 TRACE glance app = context.app_context.create() 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 710, in create 2012-12-03 13:16:53 18450 TRACE glance return self.object_type.invoke(self) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 144, in invoke 2012-12-03 13:16:53 18450 TRACE glance **context.local_conf) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/util.py, line 56, in fix_call 2012-12-03 13:16:53 18450 TRACE glance val = callable(*args, **kw) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/glance/api/__init__.py, line 31, in root_app_factory 2012-12-03 13:16:53 18450 TRACE glance return paste.urlmap.urlmap_factory(loader, global_conf, **local_conf) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/paste/urlmap.py, line 25, in urlmap_factory 2012-12-03 13:16:53 18450 TRACE glance app = loader.get_app(app_name, global_conf=global_conf) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 350, in get_app 2012-12-03 13:16:53 18450 TRACE glance name=name, global_conf=global_conf).create() 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 710, in create 2012-12-03 13:16:53 18450 TRACE glance return self.object_type.invoke(self) 2012-12-03 13:16:53 18450 TRACE glance File /usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py, line 146, in invoke 2012-12-03 13:16:53 18450 TRACE glance return fix_call(context.object, context.global_conf, **context.local_conf) 2012-12-03 13:16:53 18450 TRACE glance File
Re: [Openstack] [Quantum] questions about private, external network
On 11/29/2012 07:56 AM, Ahmed Al-Mehdi wrote: Hello, I have a few questions related to private and external network in Quantum. I am running into some odd behavior with networking related to my VM instance that I am trying to resolve. I used the following commands to create a private network and a router to which it is attached: # quantum net-create --tenant-id $put_id_of_project_one net_proj_one --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 1024 # quantum subnet-create --tenant-id $put_id_of_project_one net_proj_one 10.10.10.0/24 http://10.10.10.0/24 (step a) # quantum router-create --tenant-id $put_id_of_project_one router_proj_one # quantum router-interface-add $put_router_proj_one_id_here $put_subnet_id_here Q: Upon executing step a, does Quantum reserve the first IP address from the subnet's cidr range as a gateway_ip addr? If so, why? Does that happen even if the subnet is not attached to a router? Yes. the first IP address is reserved as default gateway ip. If no quantum router needed, you can set a true physical router on it. If you don't want a gateway at all, you can create a subnet without gateway ip reserved. I then used the following steps to create an external network: # quantum net-create --tenant-id $put_id_of_service_tenant ext_net --router:external=True # quantum subnet-create --tenant-id $put_id_of_service_tenant --allocation-pool start=192.168.50.102,end=192.168.50.126 --gateway 192.168.50.1 ext_net192.168.50.100/24 http://192.168.50.100/24 --enable_dhcp=False (step b) Q: I am trying to understand the different options passed to quantum subnet-create for an external network: - start=192.168.50.102,end=192.168.50.126 : Is this the list of floating-IPs that are accessible from outside world? And these would be mapped to a private IP addr? allocation pool is a range for inner IPAM. In fact you can assign an IP beyond this range to a Port as long as it is under the cidr of a given subnet. - 192.168.50.1 http://192.168.50.1/: Is this the outside gateway IP addr (provided by our IT)? It should be. - 192.168.50.100/24 http://192.168.50.100/24: Is 192.168.50.100 assigned (reserved) for any purpose? What is this cidr represent? It should be a wrong cidr. I think if you are using 192.168.50.100/30, the 192.168.59.101 will be reserved. - enable_dhcp=False : What is the effect of setting this to true? I mean how does Quantum dole out a floating IP mapping to which private IP, randomly? If the network is just for floatingips, there is no need to run dhcp server for the ips on this network. only ips allocated to VMs' port needed to be in dhcp server if you want to use dhcp. Thank you, Ahmed. ___ 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 Database and RPC error
Hi, can u give out more traceback? quantum context has a session attribute. It seems this context is not quantum context. On 11/21/2012 07:54 PM, Trinath Somanchi wrote: Hi- With respect to folsom release, . What does this sqlalchemy and rpc based error denote. File /usr/lib/python2.7/dist-packages/quantum/db/db_base_plugin_v2.py, line 90, in _model_query query = context.session.query(model) File /usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/common.py, line 276, in __getattr__ raise AttributeError(key) AttributeError: session Please help me understand this error? What might cause this kind of exception. Thanks in advance -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Help with debug in RPC message timeout
On 11/21/2012 04:15 AM, Ahmed Al-Mehdi wrote: Hello, I am getting a RPC message timeout in nova-network. 2012-11-18 15:50:29 DEBUG nova.openstack.common.rpc.amqp [-] Making asynchronous call on network.sonoma ... from (pid=1375) multicall /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py:351 2012-11-18 15:50:29 DEBUG nova.openstack.common.rpc.amqp [-] MSG_ID is d73be9ea76b3412493d0752abb9d5a02 from (pid=1375) multicall /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py:354 2012-11-18 15:50:52 DEBUG nova.utils [req-22e6e99a-c582-449c-8d61-d4ee57f1ac57 None None] Got semaphore get_dhcp for method _get_dhcp_ip... from (pid=1375) inner /usr/lib/python2.7/dist-packages/nova/utils.py:713 2012-11-18 15:50:52 DEBUG nova.utils [req-22e6e99a-c582-449c-8d61-d4ee57f1ac57 None None] Got semaphore get_dhcp for method _get_dhcp_ip... from (pid=1375) inner /usr/lib/python2.7/dist-packages/nova/utils.py:713 2012-11-18 15:51:09 DEBUG nova.manager [-] Running periodic task FlatDHCPManager._publish_service_capabilities from (pid=1375) periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:172 2012-11-18 15:51:09 DEBUG nova.manager [-] Running periodic task FlatDHCPManager._disassociate_stale_fixed_ips from (pid=1375) periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:172 2012-11-18 15:51:29 ERROR nova.openstack.common.rpc.common [-] Timed out waiting for RPC response: timed out Is there a way I can enable further logging to find out which queue the message is being sent to (put on). Also, the contents one the message? Do u have a host name like sonoma. It is trying to send the message to this host. Thank you, Ahmed. ___ 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 networking question..
On 11/22/2012 08:23 AM, Ahmed Al-Mehdi wrote: Hello, I have a question about setting up Quantum, following the steps described by Bilel Msekni ( https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst ), which uses 3 NICs. (Similar document/setup is also described by OpenStack.org also - https://review.openstack.org/#/c/16096/ ) Based on the node diagram in Bilel's document, I understand why eth0 needs an IP address that is accessible to internet. However, - Why does eth1 need an IP address, since it will be used for VM network? - Why does eth2 not need an IP address (set to 0.0.0.0) since it is connected to the internet. In my setup, I set an IP address to eth0 through my corp. DHCP server. Can I similarly assign an IP address to the other eth port (be it 1 or 2) that needs connection to the internet? eth1 should not have IP since it will be added into br-eth1. If you want eth1 have IP, you can move the ip to br-eth1: sudo ip addr ip dev br-eth1 sudo ifconfig br-eth1 up eth2 is connected to br-ex bridge. If u don't need the host to access the internet via eth2, there is no need to assign an IP to eth2 or br-ex the VM's will be able to access the internet via br-ex, which is via eth2 in turn to access internet. You can assign an IP to br-ex so that your host can use it. Thank you, Ahmed. ___ 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] Command to find out list of compute nodes
Can u check if the time is synchronized? Times on compute node and control node should be synchronized. On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote: Hi Narayanan, Awesome, thank you. There reason I was not seeing the nova-compute listed is because it did not launch on the compute node. I did a manual start of nova-compute on the compute node, and I do see it listed on the control-node but with XXX State. root@bodega:~/ahmed/new_guide# nova-manage service list Binary HostZone Status State Updated_At nova-networkbodega nova enabled:-) 2012-11-15 23:49:28 nova-scheduler bodega nova enabled:-) 2012-11-15 23:49:28 nova-computesonoma nova enabledXXX 2012-11-15 23:46:46 = compute-node What I don't understand is even though nova-compute is listed on the control-node, the service is not running on the compute node. That does not seem right. root@sonoma:~# service nova-compute status nova-compute stop/waiting root@sonoma:~# date; service nova-compute start Thu Nov 15 15:48:08 PST 2012 nova-compute start/running, process 2785 root@sonoma:~# service nova-compute status nova-compute stop/waiting root@sonoma:~# ps aux | grep nova root 2810 0.0 0.0 9384 924 pts/0S+ 15:49 0:00 grep --color=auto nova root@sonoma:~# service nova-compute status nova-compute stop/waiting root@sonoma:~# There are no log entries in the log files on compute-node or control-node. Any ideas please? Thank you, Ahmed. On 11/15/12 3:29 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de wrote: Hi Ahmed, You can use the command nova-manage service list from the command line of control node to get the list of compute nodes along with the nova-compute service status. Thanks Krishnaprasad Narayanan From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on behalf of Ahmed Al-Mehdi [ah...@coraid.com] Sent: Friday, November 16, 2012 12:19 AM To: openstack@lists.launchpad.net Subject: [Openstack] Command to find out list of compute nodes Hello, Is there a command I can issue on the control node to find out the list of compute node(s) (nodes running nova-compute), and potentially any additional info about the compute node(s)? Thank you, Ahmed. ___ 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] Compute node not able to connect to AMQP server (trying to connect to localhost)
Trye to start your nova-compute with --config-file {your nova.conf}. and
look at the log at the beginning to see what options values are used truly.
On 11/16/2012 06:17 AM, Ahmed Al-Mehdi wrote:
Hello,
On the compute node (IP addr : 10.176.20.4) I am seeing the following
error message in /var/log/nova/nova-compute.log:
2012-11-15 14:11:12 INFO nova.openstack.common.rpc.common [-]
*Reconnecting to AMQP server on localhost:5672*
2012-11-15 14:11:12 ERROR nova.openstack.common.rpc.common [-] AMQP
server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED.
Trying again in 30 seconds.
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common Traceback
(most recent call last):
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_kombu.py,
line 469, in reconnect
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self._connect()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_kombu.py,
line 446, in _connect
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self.connection.connect()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 154, in
connect
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common return
self.connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 560, in
connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self._connection = self._establish_connection()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 521, in
_establish_connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common conn =
self.transport.establish_connection()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line
255, in establish_connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
connect_timeout=conninfo.connect_timeout)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line
52, in __init__
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
super(Connection, self).__init__(*args, **kwargs)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py,
line 129, in __init__
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self.transport = create_transport(host, connect_timeout, ssl)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py,
line 281, in create_transport
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common return
TCPTransport(host, connect_timeout)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py,
line 85, in __init__
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common raise
socket.error, msg
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common error:
[Errno 111] ECONNREFUSED
The rabbitmq server is running on the controller node (10.176.20.158),
which is reachable from the compute node. Can someone please help me
understand why the compute node is trying to connect to AMQP server on
localhost.
nova.conf file is below:
[DEFAULT]
# LOGS/STATE
verbose=True
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
rootwrap_config=/etc/nova/rootwrap.conf
# AUTHENTICATION
auth_strategy=keystone
# [keystone_authtoken]
auth_host = 127.0.0.1
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = nova
admin_password = nova
signing_dirname = /tmp/keystone-signing-nova
# SCHEDULER
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
# Cinder - VOLUMES
#volume_driver=nova.volume.driver.ISCSIDriver
#volume_group=nova-volumes
#volume_name_template=volume-%08x
#iscsi_helper=tgtadm
volume_api_class=nova.volume.cinder.API
# DATABASE
sql_connection=mysql://nova:novadbsecret@10.176.20.158/nova
# COMPUTE
libvirt_type=kvm
compute_driver=libvirt.LibvirtDriver
instance_name_template=instance-%08x
api_paste_config=/etc/nova/api-paste.ini
# COMPUTE/APIS: if you have separate configs for separate services
# this flag is required for both nova-api and nova-compute
allow_resize_to_same_host=True
# APIS
enabled_apis=ec2,osapi_compute,metadata
osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
ec2_dmz_host=10.176.20.158
s3_host=10.176.20.158
# RABBITMQ
rabbit_host=10.176.20.158
# GLANCE
image_service=nova.image.glance.GlanceImageService
glance_api_servers=10.176.20.158:9292
# NETWORK
Re: [Openstack] Compute node not able to connect to AMQP server (trying to connect to localhost)
I don't know there exists a such command. But these values will be
printed during nova-computer starting.
I think nova-compute is using db to report its existence, and using MQ
to reports its capabilities to nova-scheduler
On 11/16/2012 06:47 AM, Ahmed Al-Mehdi wrote:
Thank you for your help. Actually, I just restarted the service (
service nova-compute restart ), I am not seeing the error anymore.
Do you know if there is a command to get a list of the current config
values in nova?
Does nova-compute running on the compute node register itself with
the control node (using the rabbitmq-server)? If so, is that how the
control node knows of all the compute node that it can talk to?
Thank you,
Ahmed.
From: gong yong sheng gong...@linux.vnet.ibm.com
mailto:gong...@linux.vnet.ibm.com
Date: Thursday, November 15, 2012 3:39 PM
To: Ahmed Al-Mehdi ah...@coraid.com mailto:ah...@coraid.com
Cc: openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] Compute node not able to connect to AMQP
server (trying to connect to localhost)
Trye to start your nova-compute with --config-file {your
nova.conf}. and look at the log at the beginning to see what
options values are used truly.
On 11/16/2012 06:17 AM, Ahmed Al-Mehdi wrote:
Hello,
On the compute node (IP addr : 10.176.20.4) I am seeing the
following error message in /var/log/nova/nova-compute.log:
2012-11-15 14:11:12 INFO nova.openstack.common.rpc.common [-]
*Reconnecting to AMQP server on localhost:5672*
2012-11-15 14:11:12 ERROR nova.openstack.common.rpc.common [-]
AMQP server on localhost:5672 is unreachable: [Errno 111]
ECONNREFUSED. Trying again in 30 seconds.
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
Traceback (most recent call last):
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_kombu.py,
line 469, in reconnect
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self._connect()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_kombu.py,
line 446, in _connect
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self.connection.connect()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 154,
in connect
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
return self.connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 560,
in connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self._connection = self._establish_connection()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 521,
in _establish_connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
conn = self.transport.establish_connection()
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py,
line 255, in establish_connection
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
connect_timeout=conninfo.connect_timeout)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py,
line 52, in __init__
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
super(Connection, self).__init__(*args, **kwargs)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py,
line 129, in __init__
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
self.transport = create_transport(host, connect_timeout, ssl)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py,
line 281, in create_transport
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
return TCPTransport(host, connect_timeout)
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py,
line 85, in __init__
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common
raise socket.error, msg
2012-11-15 14:11:12 TRACE nova.openstack.common.rpc.common error:
[Errno 111] ECONNREFUSED
The rabbitmq server is running on the controller node
(10.176.20.158), which is reachable from the compute node. Can
someone please help me understand why the compute node is trying
to connect to AMQP server on localhost
Re: [Openstack] Command to find out list of compute nodes
Hi Ahmed, and with nova host-xxx as assistance. On 11/16/2012 07:29 AM, Narayanan, Krishnaprasad wrote: Hi Ahmed, You can use the command nova-manage service list from the command line of control node to get the list of compute nodes along with the nova-compute service status. Thanks Krishnaprasad Narayanan From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on behalf of Ahmed Al-Mehdi [ah...@coraid.com] Sent: Friday, November 16, 2012 12:19 AM To: openstack@lists.launchpad.net Subject: [Openstack] Command to find out list of compute nodes Hello, Is there a command I can issue on the control node to find out the list of compute node(s) (nodes running nova-compute), and potentially any additional info about the compute node(s)? Thank you, Ahmed. ___ 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 Suggestion
I think we have already Bp for this: https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler also the quantum agents multi-hosts and multiple dhcp agents and l3 agents will depend on it. On 11/16/2012 08:02 AM, Dan Wendlandt wrote: Yes, this has been suggested before and I think would be valuable. One complication is that in quantum, there are multiple possible implementations (e.g., some plugins require agents, others don't), but I think it would be possible to abstract things in a way that are useful (e.g., show the status of various devices, and what functions they are implementing). dan On Thu, Nov 15, 2012 at 6:22 AM, Skible OpenStack skible.openst...@gmail.com mailto:skible.openst...@gmail.com wrote: Hi stackers, Just like Nova does have the nova-manage service list to check on how well the nova-services are running in all the nodes, i suggest that quantum does the same. After all, we have the l3-agent, dhcp agent, quantum server and many plugin agents running in different nodes and it will be nice to have a common monitoring function which checks the state of each service The blueprint is registered here: https://blueprints.launchpad.net/quantum/+spec/quantum-monitoring-function if anyone is interested. Best regards ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com http://www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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 configure l3_agent when you have Per-tenant Routers !
There is a router_id in l3_agent.ini, You can create a router for a tenant and then start a l3 agent for it. On 11/11/2012 01:34 AM, Skible OpenStack wrote: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst i have set my namespace in l3 agent and dhcp agent to true. set external network id to my external network id in the l3 agent file do i need to run multiple l3 agents to have the per tenant router usecase ? Le 10/11/2012 18:29, Razique Mahroua a crit: Hey there, which guide did you followed ? Nuage Co - Razique Mahroua razique.mahr...@gmail.com Le 10 nov. 2012 17:57, Skible OpenStack skible.openst...@gmail.com a crit : Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet ! please help ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Openstack :: Folsom] Quantum Network Node setup
On 11/10/2012 10:06 PM, balaji patnala wrote: Hi Yong, I downloaded the Quantum Architecture in Folsom Powerpoint prepared by you and found that in slide-10: lL3-agent lTo implement floating Ipsand other L3 features, such as NAT _lOne per network_ Can you elaborate on the comment 'one per network' for L3-Agent. # If use_namespaces is set as False then the agent can only configure one router. # This is done by setting the specific router_id. # router_id = # Each L3 agent can be associated with at most one external network. This # value should be set to the UUID of that external network. If empty, # the agent will enforce that only a single external networks exists and # use that external network id # gateway_external_network_id = two options: 1. use namespace = False and set router_id to specific one can support multi l3-agent, or 2. create multiples external networks, and use gateway_external_network_id = to run multil3-agent This way, we must set router's gateway port: we can create router with external_gateway_info: such as quantum router-create router1 --external_gateway_info network_id=id or quantum router-create router2 quantum router-gateway-set As i understood that the L3-Agent will be only one for complete setup. If we have more than one Network Node then we must install dhcp-agent and L3-Agent in each of these Network Nodes. So, the comment of 'one per network' is like we can have one router/gateway per tenant network. Can you give us your comments on this. you can reach at this target by creating a router or external network per tenant. bye, balaji On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala patnala...@gmail.com mailto:patnala...@gmail.com wrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to understand what will be the advantages we are thinking of by doing so. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.com mailto:sorla...@nicira.com wrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me
Re: [Openstack] Error in l3_agent
I think we already fixed this bug. please see if it helps: https://review.openstack.org/#/c/14756/ On 11/05/2012 05:52 PM, Skible OpenStack wrote: Hello Stackers ! i am finding a weird error in my l3_agent.log file: Stderr: '' 2012-11-05 10:22:59ERROR [quantum.agent.l3_agent] Error running l3_nat daemon_loop Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py, line 170, in daemon_loop self.do_single_loop() File /usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py, line 227, in do_single_loop self.process_router(ri) File /usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py, line 300, in process_router self.external_gateway_added(ri, ex_gw_port, internal_cidrs) File /usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py, line 398, in external_gateway_added ri.iptables_manager.apply() File /usr/lib/python2.7/dist-packages/quantum/agent/linux/iptables_manager.py, line 282, in apply root_helper=self.root_helper)) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py, line 55, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', '/sbin/iptables-save', '-t', 'filter'] Exit code: 99 Stdout: 'Unauthorized command: /sbin/iptables-save -t filter\n' Stderr: '' == I can't seem to find any documentation about this problem. Can anyone please shed some light on this ? Best regards, Bilel ___ 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 :: Folsom] Quantum Network Node setup
On 10/31/2012 01:08 PM, balaji patnala wrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to un derstand what will be the advantages we are thinking of by doing so. TO have multiple l3 agent nodes, we can distribute traffic from VMs among l3 agent nodes. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.com mailto:sorla...@nicira.com wrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 tel:%2B91%209866%20235%20130 ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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-dev] Writing Plug-ins to Quantum
On 10/31/2012 05:00 PM, Trinath Somanchi wrote: Hi Stackers- I'm testing a dummy plugin which does and RPC based communication with Quantum. I have done this following: [1] I have written dummy agent like DHCP agent - Present in HOST [2] I have written dummy_rpc_base like the db/dhcp_rpc_base.py - Present in Controller [3] I have written an testing method to the db/db_base_plugin_v2.py - Present in Controller But when I restart the quantum-server, I get this error: root@user-P2020Build:/usr/lib/python2.7/dist-packages/quantum/db# python /usr/bin/quantum-server -- --config-file /etc/quantum/quantum.conf --log-file /var/log/quantum/server.log --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini 2012-10-31 14:20:30DEBUG [quantum.service] 2012-10-31 14:20:30DEBUG [quantum.service] Configuration options gathered from config file: 2012-10-31 14:20:30DEBUG [quantum.service] 2012-10-31 14:20:30DEBUG [quantum.service] allow_bulk True 2012-10-31 14:20:30DEBUG [quantum.service] allow_overlapping_ips False 2012-10-31 14:20:30DEBUG [quantum.service] api_extensions_path 2012-10-31 14:20:30DEBUG [quantum.service] api_paste_config /etc/quantum/api-paste.ini 2012-10-31 14:20:30DEBUG [quantum.service] auth_strategy keystone 2012-10-31 14:20:30DEBUG [quantum.service] base_mac fa:16:3e:00:00:00 2012-10-31 14:20:30DEBUG [quantum.service] bind_host 0.0.0.0 2012-10-31 14:20:30DEBUG [quantum.service] bind_port 9696 2012-10-31 14:20:30DEBUG [quantum.service] config_dir None 2012-10-31 14:20:30DEBUG [quantum.service] config_file ['/etc/quantum/quantum.conf'] 2012-10-31 14:20:30DEBUG [quantum.service] core_plugin quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 2012-10-31 14:20:30DEBUG [quantum.service] debug True 2012-10-31 14:20:30DEBUG [quantum.service] dhcp_lease_duration 120 2012-10-31 14:20:30DEBUG [quantum.service] log_config None 2012-10-31 14:20:30DEBUG [quantum.service] log_date_format %Y-%m-%d %H:%M:%S 2012-10-31 14:20:30DEBUG [quantum.service] log_dir None 2012-10-31 14:20:30DEBUG [quantum.service] log_file None 2012-10-31 14:20:30DEBUG [quantum.service] log_format %(asctime)s %(levelname)8s [%(name)s] %(message)s 2012-10-31 14:20:30DEBUG [quantum.service] mac_generation_retries 16 2012-10-31 14:20:30DEBUG [quantum.service] max_dns_nameservers 5 2012-10-31 14:20:30DEBUG [quantum.service] max_subnet_host_routes 20 2012-10-31 14:20:30DEBUG [quantum.service] policy_file policy.json 2012-10-31 14:20:30DEBUG [quantum.service] state_path . 2012-10-31 14:20:30DEBUG [quantum.service] syslog_log_facility LOG_USER 2012-10-31 14:20:30DEBUG [quantum.service] use_syslog False 2012-10-31 14:20:30DEBUG [quantum.service] verbose True 2012-10-31 14:20:30DEBUG [quantum.service] 2012-10-31 14:20:30 INFO [quantum.common.config] Config paste file: /etc/quantum/api-paste.ini 2012-10-31 14:20:30DEBUG [quantum.manager] Plugin location:quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 2012-10-31 14:20:30 INFO [quantum.manager] Loading Plugin: quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 Traceback (most recent call last): File /usr/bin/quantum-server, line 26, in module server() File /usr/lib/python2.7/dist-packages/quantum/server/__init__.py, line 40, in main quantum_service = service.serve_wsgi(service.QuantumApiService) File /usr/lib/python2.7/dist-packages/quantum/service.py, line 83, in serve_wsgi service.start() File /usr/lib/python2.7/dist-packages/quantum/service.py, line 42, in start self.wsgi_app = _run_wsgi(self.app_name) File /usr/lib/python2.7/dist-packages/quantum/service.py, line 89, in _run_wsgi app = config.load_paste_app(app_name) File /usr/lib/python2.7/dist-packages/quantum/common/config.py, line 133, in load_paste_app app = deploy.loadapp(config:%s % config_path, name=app_name) File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247, in loadapp return loadobj(APP, uri, name=name, **kw) File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 272, in loadobj return context.create() File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in create return
Re: [Openstack] RPC setup for Quantum
to run quantum-server, dhcp agent, ovs and linuxbridge agent, we need to specify the quantum.conf as one of the configure files. Besides the RPC sections, some of other parts are useful too. RPC parts are used for communication between quantum-server and dhcp agent, ovs agent or linux bridge agent. On 10/30/2012 03:37 PM, Trinath Somanchi wrote: Hi Stackers- With respect to the Folsom Quantum Admin Manual (http://docs.openstack.org/trunk/openstack-network/admin/content/rpc_setup.html) , the RPC setup section. The lines , [Important] Important This /etc/quantum/quantum.conf file should be copied to and used on all hosts running quantum-server, quantum-dhcp-agent, quantum-openvswitch-agent, or quantum-linuxbridge-agent (see below). Specify that the quantum.conf should be copied to all Network Nodes if the Agents doesn't run in the Controller node. Also in the same way, IF we have the DHCP/OVS agents running in the HOST nodes itself the same scenario works for it. I'm thinking that, this configuration copy to the HOST/NETWORK nodes is to support the RABBITMQ linking between the Controller and the NETWORK/HOST nodes, in order to enable RPC based communication between the Controller and the Agents running in the Network/Host nodes. Please correct my understanding briefed above. Thanking you- -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Openstack :: Folsom] Quantum DHCP Agent in Compute HOST
Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.com mailto:sorla...@nicira.com wrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 tel:%2B91%209866%20235%20130 ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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] RPC setup for Quantum
On 10/30/2012 04:53 PM, Trinath Somanchi wrote: True said. I'm clear with this point. But My doubt is that, for every HOST node, we need to have quantum.conf if the HOST node has the DHCP-Agent and the OVS-Agent running in them. dhcp-agent and ovs-agent will need the quantum.conf as one of their configure files. for example dhcp-agent --config-file quantum.conf --config-file dhcp.ini So if the Host node has these agents running on them, we need to have quantum.conf on host node. these agents will use the configuration in quantum.conf, such as logging settings, RPC settings. Hope this explanation helps. Please help me in this regard. - Trinath On Tue, Oct 30, 2012 at 1:58 PM, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: to run quantum-server, dhcp agent, ovs and linuxbridge agent, we need to specify the quantum.conf as one of the configure files. Besides the RPC sections, some of other parts are useful too. RPC parts are used for communication between quantum-server and dhcp agent, ovs agent or linux bridge agent. On 10/30/2012 03:37 PM, Trinath Somanchi wrote: Hi Stackers- With respect to the Folsom Quantum Admin Manual (http://docs.openstack.org/trunk/openstack-network/admin/content/rpc_setup.html) , the RPC setup section. The lines , [Important] Important This /etc/quantum/quantum.conf file should be copied to and used on all hosts running quantum-server, quantum-dhcp-agent, quantum-openvswitch-agent, or quantum-linuxbridge-agent (see below). Specify that the quantum.conf should be copied to all Network Nodes if the Agents doesn't run in the Controller node. Also in the same way, IF we have the DHCP/OVS agents running in the HOST nodes itself the same scenario works for it. I'm thinking that, this configuration copy to the HOST/NETWORK nodes is to support the RABBITMQ linking between the Controller and the NETWORK/HOST nodes, in order to enable RPC based communication between the Controller and the Agents running in the Network/Host nodes. Please correct my understanding briefed above. Thanking you- -- Regards, -- Trinath Somanchi, +91 9866 235 130 tel:%2B91%209866%20235%20130 ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help :https://help.launchpad.net/ListHelp -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] about nova-schedule queues
Following is my understanding:
usage:
scheduler queue is used for compute api server. For example of nova
boot, API server will send a msg to scheduler queue for a booting
scheduler_*fanout_ is used for service*s to report service
capability. For example, nova compute **will use scheduler_fanout to
publish its capabilities.
scheduler.{hostname} seemingly is not used now.
we can deploy many schedulers into a Openstack cloud. All the schedulers
will listen on scheduler msg queue. AMQP server (rabbitmq) will adopt
round robin way to
dispatch the msg to these schedulers. But since the capabilities are fan
outed, all the schedulers can receive these capabilities.
On 10/30/2012 06:55 PM, 韦远科 wrote:
hi all,
I read into the source code for nova-scheduler and found there
actually exists three msg queues, like
scheduler
scheduler.node70
scheduler_*fanout_bd738fedcdf344d9bb3cb580657f54e0*.
what's the functions for each queue and are there connections??
thanks,
___
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] Not able to get IP address for VM
can u send out nova.conf file? On 10/22/2012 07:30 PM, Srikanth Kumar Lingala wrote: Hi, I am using latest devstack I am trying to create a VM with one Ethernet interface card. I am able to create the VM successfully, but not able to get IP for the ethernet interface. I have Openstack Controller running the following: * nova-api * nova-cert * nova-consoleauth * nova-scheduler * quantum-dhcp-agent * quantum-openvswitch-agent And O also have Openstack Host Node running the following: * nova-api * nova-compute * quantum-openvswitch-agent I am not seeing any kind of errors in logs related nova as well as quantum. I observed that when I execute 'dhclient' in VM, 'br-int' interface in 'Openstack Controller' getting DHCP requests, but not sending reply. Please let me know, what I am doing wrong here. Thanks in advance. -- Srikanth. ___ 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 networking
In fact you can run multiple nova-networks, which I call it as multiple instances mode, and multi-host mode with each nova-network on each nova-compute. in multiple instance mode, you can use nova-manage network modify to host a given network on a given host, which is running a nova-network: ./bin/nova-manage network modify --help Usage: nova-manage network modify args [options] Options: -h, --helpshow this help message and exit --fixed_range=x.x.x.x/yy Network to modify --project=project name Project name to associate --host=host Host to associate --disassociate-project Disassociate Network from Project --disassociate-host Disassociate Host from Project On 10/21/2012 11:19 PM, Egoitz Aurrekoetxea Aurre wrote: t Or does each nova-compute node has to have it's own nova network service in the same vm??? El 21/10/2012, a las 15:55, Egoitz Aurrekoetxea Aurre ego...@ramattack.net escribió: Good afternoon, Is it anyway of avoid redirecting and managing all the traffic with just one vm?. I mean can I have several nova-networks for handling the traffic??. I'm going to use XenAPI and XenCloudPlatform, and going to have an vlan per project. I would like to know how to make the bridging, vlan, etc components on Linux scalable…. for just avoiding depending all the network traffic in just one machine…. Is that possible in Openstack? How other network configs could I do for scaling better?. Another aspect I would like too know if it's possible too… is the fact of just directly assigning public ip to instances… and avoiding having a public and a private ip…..Is all this possible??. Best regards, ___ 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 create_net- creates network for non-existing tenant also.
Yes, it does work. the quantum will not check if the tenant id specified is in keystone or other Auth system. On 10/18/2012 04:25 AM, Raja Gajju wrote: Hi, Many thanks for your reply. But we are using Quantum CLIs V1.0 and we are having Quantum V1.0 only in our set up. So, these CLIs should work for the corresponding Quantum version. Regards, Girija Sharan Singh *From:* gong yong sheng gong...@linux.vnet.ibm.com *To:* Raja Gajju gajjur...@yahoo.com *Cc:* openstack@lists.launchpad.net openstack@lists.launchpad.net; mahesh.kur...@oneconvergence.com mahesh.kur...@oneconvergence.com; shyam.tod...@oneconvergence.com shyam.tod...@oneconvergence.com *Sent:* Thursday, 18 October 2012 12:35 AM *Subject:* Re: [Openstack] quantum create_net- creates network for non-existing tenant also. It seems that you are using quantum cli v1.0, which is not supported in new quantum version v2.0 API. Are u using quantum v1.x, right? On 10/16/2012 10:39 AM, Raja Gajju wrote: Hi All, I am testing the Quantum CLIs in my set up. When I am creating a new network using create_net CLI for an non-existing tenant, it is showing successful creation. It should not do so. It is something unexpected. And again when I am doing list_nets it is showing that network under the specified non-existing tenant. Here is the snippet of the commans and their results : --- ~/devstack$ quantum create_net hjbddsbfikeoqjroijmfgvkmgfv fake_net Created a new Virtual Network with ID: f3b1d829-009d-45b5-9108-01722539135e for Tenant: hjbddsbfikeoqjroijmfgvkmgfv ~/devstack$ quantum list_nets hjbddsbfikeoqjroijmfgvkmgfv Virtual Networks for Tenant hjbddsbfikeoqjroijmfgvkmgfv Network ID: f3b1d829-009d-45b5-9108-01722539135e --- Any effort to explain this inconsistency issue will be highly appreciated. Many thanks in advance. Thanks and Regards, Girija Sharan Singh ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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 create_net- creates network for non-existing tenant also.
It seems that you are using quantum cli v1.0, which is not supported in new quantum version v2.0 API. Are u using quantum v1.x, right? On 10/16/2012 10:39 AM, Raja Gajju wrote: Hi All, I am testing the Quantum CLIs in my set up. When I am creating a new network using create_net CLI for an non-existing tenant, it is showing successful creation. It should not do so. It is something unexpected. And again when I am doing list_nets it is showing that network under the specified non-existing tenant. Here is the snippet of the commans and their results : --- ~/devstack$ quantum create_net hjbddsbfikeoqjroijmfgvkmgfv fake_net Created a new Virtual Network with ID: f3b1d829-009d-45b5-9108-01722539135e for Tenant: hjbddsbfikeoqjroijmfgvkmgfv ~/devstack$ quantum list_nets hjbddsbfikeoqjroijmfgvkmgfv Virtual Networks for Tenant hjbddsbfikeoqjroijmfgvkmgfv Network ID: f3b1d829-009d-45b5-9108-01722539135e --- Any effort to explain this inconsistency issue will be highly appreciated. Many thanks in advance. Thanks and Regards, Girija Sharan Singh ___ 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] Creating networks with same subnet across Tenants
Try to define allow_overlapping_ips = True On 10/12/2012 09:37 PM, Srikanth Kumar Lingala wrote: Hi all, Is it possible to create two networks with same subnet across two different tenants? I tried this with latest quantum, but got the following error: */ Invalid input for operation: Requested subnet with cidr: 25.25.0.0/24 http://25.25.0.0/24 for network: 7263582f-cb57-47a2-86cf-97a4ab40de52 overlaps with another subnet./* I think it is quite possible case across multiple tenants. Please clarify. -- Srikanth. ___ 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] some question with nova schedule
read on:
we will send the host to compute manager:
def _provision_resource(self, context, weighted_host, request_spec,
filter_properties, requested_networks, injected_files,
admin_password, is_first_time, instance_uuid=None):
Create the requested resource in this Zone.
# Add a retry entry for the selected compute host:
self._add_retry_host(filter_properties,
weighted_host.host_state.host)
self._add_oversubscription_policy(filter_properties,
weighted_host.host_state)
payload = dict(request_spec=request_spec,
weighted_host=weighted_host.to_dict(),
instance_id=instance_uuid)
notifier.notify(context, notifier.publisher_id(scheduler),
'scheduler.run_instance.scheduled', notifier.INFO,
payload)
updated_instance = driver.instance_update_db(context,
instance_uuid)
self.compute_rpcapi.run_instance(context,
instance=updated_instance,
host=weighted_host.host_state.host,
request_spec=request_spec,
filter_properties=filter_properties,
requested_networks=requested_networks,
injected_files=injected_files,
admin_password=admin_password, is_first_time=is_first_time)
On 10/12/2012 09:54 AM, 韦远科 wrote:
hi,
I read the following code in nova scheduler and have some questions
with the code marked in yellow.
the following code can be found at
https://github.com/openstack/nova/blob/master/nova/scheduler/filter_scheduler.py;
def _provision_resource(self, context, weighted_host, request_spec,
filter_properties, requested_networks, injected_files,
admin_password, is_first_time, instance_uuid=None):
Create the requested resource in this Zone.
# Add a retry entry for the selected compute host:
self._add_retry_host(filter_properties, weighted_host.host_state.host)
self._add_oversubscription_policy(filter_properties,
weighted_host.host_state)
payload = dict(request_spec=request_spec,
weighted_host=weighted_host.to_dict(),
instance_id=instance_uuid)
notifier.notify(context, notifier.publisher_id(scheduler),
'scheduler.run_instance.scheduled', notifier.INFO,
payload)
updated_instance = driver.instance_update_db(context, instance_uuid)
#at this point, we already know the host which will provision the
instance, that is recorded in variable /weighted_host./
//But actually, the /instance_update_db/ function only update values
= {'host': None, 'scheduled_at': now} in database,
So why
can someone give me some help? thanks very much!
-
韦远科
中国科学院 计算机网络信息中心
北京市海淀区中关村南四街四号 349信箱(100190)
Yuanke Wei (Wei)
Computer Network Information Center,Chinese Academy of Sciences
4 Zhongguancun Nansijie, Haidian District, Beijing 100190, China
P.O. Box 349
gtalk: weiyuanke...@gmail.com mailto:weiyuanke...@gmail.com
msn: weiyuanke...@hotmail.com mailto:weiyuanke...@hotmail.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
Re: [Openstack] Help about Quantum Conf
Hi, quantum.conf: core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 ovs_quantum_plugin.ini: network_vlan_ranges = physnet1 enable_tunneling = False bridge_mappings = physnet1:br-eth0 To create a shared provider network: quantum net-create sharednet1 --shared --provider:network_type flat --provider:physical_network physnet1 Before we can run, create br-eth0: sudo ovs-vsctl add-br br-eth0 sudo ovs-vsctl add-port br-eth0 eth0 we don't need br-ex since we don't use router and floatingip and br-tun since we don't use GRE. Regards, Yong Sheng Gong On 10/09/2012 03:29 PM, Bilel Msekni wrote: Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Network http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.html but i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. Thanks. ___ 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
