From dpkshetty at gmail.com Thu Jan 1 03:03:06 2015 From: dpkshetty at gmail.com (Deepak Shetty) Date: Thu, 1 Jan 2015 08:33:06 +0530 Subject: [Rdo-list] Query regarding RDO Juno-1 install on CentOS7 In-Reply-To: <54A480E6.2000901@redhat.com> References: <54A16517.60803@laimbock.com> <54A3FF86.5090208@redhat.com> <54A480E6.2000901@redhat.com> Message-ID: Thanks perry, i googled too, but having instructions as part of the rdo quickstart is ideal as it is in the flow of things. For eg. I installed centos7 via pxe install and since rdo quick start didn't say anything specific abt Nm i just followed basic install process, only to know later that nm need to be disabled, which is not easy for someone not fairly expert in networking stuff so having the right cmds as part of rdo quick start pre reqs would help rdo beginerrs a lot On Jan 1, 2015 4:34 AM, "Perry Myers" wrote: > On 12/31/2014 09:34 AM, Deepak Shetty wrote: > > In which case RDO quickstart or some other place should have good info > > on how to disable NM and enable ifcfg networking for started who look at > > quickstart or RDO faqs to get hints > > google search for 'rdo disable network manager' turned up this: > https://openstack.redhat.com/Fedora_20_with_existing_network > > it's a bit more than you would need, but in there are simple steps for > disabling network manager > > But I agree that having more accessible HOWTOs for this specific area > would make sense. This wiki page is Fedora specific (though the same > steps should work on CentOS 7 I believe) and doesn't cover initial > installation, only after install how to disable NM. > > I believe though, that removing network manager in a kickstart based > installation of CentOS or Fedora is as simple as adding NetworkManager > to the list of blacklisted packages. > > (i.e. under %packages add -NetworkManager) [1] > > Perry > > [1] > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-packageselection.html > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lpeer at redhat.com Mon Jan 5 11:11:12 2015 From: lpeer at redhat.com (Livnat Peer) Date: Mon, 05 Jan 2015 13:11:12 +0200 Subject: [Rdo-list] Query regarding RDO Juno-1 install on CentOS7 In-Reply-To: References: <54A16517.60803@laimbock.com> <54A3FF86.5090208@redhat.com> <54A480E6.2000901@redhat.com> Message-ID: <54AA7150.40301@redhat.com> On 01/01/2015 05:03 AM, Deepak Shetty wrote: > Thanks perry, i googled too, but having instructions as part of the rdo > quickstart is ideal as it is in the flow of things. For eg. I installed > centos7 via pxe install and since rdo quick start didn't say anything > specific abt Nm i just followed basic install process, only to know > later that nm need to be disabled, which is not easy for someone not > fairly expert in networking stuff so having the right cmds as part of > rdo quick start pre reqs would help rdo beginerrs a lot > I agree we should document that in the quick start. Kuba - can you please add the steps to turn-off NM in the quickstart page. Also the current list of bugs that blocks us from enabling NM are - https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&list_id=3123976&namedcmd=openstack-nm&remaction=run&sharer_id=287527 Livnat > On Jan 1, 2015 4:34 AM, "Perry Myers" > wrote: > > On 12/31/2014 09:34 AM, Deepak Shetty wrote: > > In which case RDO quickstart or some other place should have good info > > on how to disable NM and enable ifcfg networking for started who > look at > > quickstart or RDO faqs to get hints > > google search for 'rdo disable network manager' turned up this: > https://openstack.redhat.com/Fedora_20_with_existing_network > > it's a bit more than you would need, but in there are simple steps for > disabling network manager > > But I agree that having more accessible HOWTOs for this specific area > would make sense. This wiki page is Fedora specific (though the same > steps should work on CentOS 7 I believe) and doesn't cover initial > installation, only after install how to disable NM. > > I believe though, that removing network manager in a kickstart based > installation of CentOS or Fedora is as simple as adding NetworkManager > to the list of blacklisted packages. > > (i.e. under %packages add -NetworkManager) [1] > > Perry > > [1] > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-packageselection.html > From patrick at laimbock.com Mon Jan 5 13:05:19 2015 From: patrick at laimbock.com (Patrick Laimbock) Date: Mon, 05 Jan 2015 14:05:19 +0100 Subject: [Rdo-list] Query regarding RDO Juno-1 install on CentOS7 In-Reply-To: <54AA7150.40301@redhat.com> References: <54A16517.60803@laimbock.com> <54A3FF86.5090208@redhat.com> <54A480E6.2000901@redhat.com> <54AA7150.40301@redhat.com> Message-ID: <54AA8C0F.2010104@laimbock.com> Hi Livnat, On 05-01-15 12:11, Livnat Peer wrote: [snip] > > Also the current list of bugs that blocks us from enabling NM are - > > https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&list_id=3123976&namedcmd=openstack-nm&remaction=run&sharer_id=287527 That links gives: "The search named openstack-nm has not been made visible to you.". Any chance you could make it public? Best, Patrick From rdo-info at redhat.com Mon Jan 5 18:49:03 2015 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 5 Jan 2015 18:49:03 +0000 Subject: [Rdo-list] [RDO] Blog roundup, closing out 2014 Message-ID: <0000014abb6dcd26-73b0722d-10eb-4388-90fb-dd983cc9e2b1-000000@email.amazonses.com> rbowen started a discussion. Blog roundup, closing out 2014 --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/997/blog-roundup-closing-out-2014 Have a great day! From rbowen at redhat.com Mon Jan 5 20:12:27 2015 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 05 Jan 2015 15:12:27 -0500 Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 5, 2015) Message-ID: <54AAF02B.1080906@redhat.com> The following are the meetups I'm aware of in the coming week where RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If there's a meetup in your area, please consider attending. It's the best way to find out what interesting things are going on in the larger community, and a great way to make contacts that will help you solve your own problems in the future. And don't forget to blog about it, tweet about it, G+ about it. --Rich * Wednesday, January 07 in Tel Aviv-Yafo, IL: OpenStack in the Real World with Guy Daley, Cisco & Expert Panel - http://www.meetup.com/OpenStack-Israel/events/219529193/ * Thursday, January 08 in Richardson, TX, US: January 2015 OpenStack Meetup - neutron networking presentation - http://www.meetup.com/OpenStack-DFW/events/218257912/ * Thursday, January 08 in Mountain View, CA, US: Scalable Multi-tenant Logging, Metrics and Monitoring as a Service for OpenStack - http://www.meetup.com/Cloud-Platform-at-Symantec/events/218914623/ * Friday, January 09 in San Francisco, CA, US: Let's talk about identity management in the cloud - http://www.meetup.com/Cloud-Builders/events/218844510/ * Friday, January 09 in Whittier, CA, US: Introduction to Red Hat and OpenShift (cohost with SGVLUG) - http://www.meetup.com/Greater-Los-Angeles-Area-Red-Hat-User-Group-RHUG/events/216795442/ * Saturday, January 10 in Beijing, CN: #??OpenStack SuperUser#??? - http://www.meetup.com/China-OpenStack-User-Group/events/219586084/ * Saturday, January 10 in Chennai, IN: OpenStack Mini Meetup, Chennai - http://www.meetup.com/Indian-OpenStack-User-Group/events/219428900/ * Sunday, January 11 in Bangalore, IN: OpenStack India Meetup, Bangalore - http://www.meetup.com/Indian-OpenStack-User-Group/events/219475318/ * Monday, January 12 in Tel Aviv-Yafo, IL: NFV & Open Networking Meet-up @Red Hat - http://www.meetup.com/IGTCloud/events/219419466/ * Monday, January 12 in Ra'anana, IL: NFV & Open Networking Meet-up @Red Hat - http://www.meetup.com/Open-Source-Israel/events/219459741/ * Tuesday, January 13 in Washington, DC, US: OpenStackDC Meetup #17 - http://www.meetup.com/OpenStackDC/events/218760179/ -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From vhosakot at cisco.com Tue Jan 6 02:34:14 2015 From: vhosakot at cisco.com (Vikram Hosakote (vhosakot)) Date: Tue, 6 Jan 2015 02:34:14 +0000 Subject: [Rdo-list] RDO neutron bug 1087589 Message-ID: Hi, I have been hitting the RDO bug https://bugzilla.redhat.com/show_bug.cgi?id=1087589, and not able to boot a nova instance. I see that the fix https://review.openstack.org/#/c/92387/ was merged on May 29th 2014. Is this fix available in the latest RDO ? Below are the package versions of neutron and nova in my RHEL 7 IceHouse setup. How can I check if the fix is available in my packages below ? Nova: ===== [root at compute1 nova(keystone_admin)]# rpm -qa | grep -i openstack | grep neutron openstack-neutron-openvswitch-2014.1.2-2.el7ost.noarch openstack-neutron-2014.1.2-2.el7ost.noarch [root at compute1 nova(keystone_admin)]# yum info openstack-neutron-openvswitch-2014.1.2-2.el7ost.noarch Name : openstack-neutron-openvswitch Arch : noarch Version : 2014.1.2 Release : 2.el7ost >From repo : rhel-7-server-openstack-5.0-rpms [root at compute1 nova(keystone_admin)]# yum info openstack-neutron-2014.1.2-2.el7ost.noarch Name : openstack-neutron Arch : noarch Version : 2014.1.2 Release : 2.el7ost >From repo : rhel-7-server-openstack-5.0-rpms Neutron: ======== [root at compute1 nova(keystone_admin)]# rpm -qa | grep -i openstack | grep nova openstack-nova-common-2014.1.2-1.el7ost.noarch openstack-nova-compute-2014.1.2-1.el7ost.noarch [root at compute1 nova(keystone_admin)]# yum info openstack-nova-common-2014.1.2-1.el7ost.noarch Name : openstack-nova-common Arch : noarch Version : 2014.1.2 Release : 1.el7ost >From repo : rhel-7-server-openstack-5.0-rpms [root at compute1 nova(keystone_admin)]# yum info openstack-nova-compute-2014.1.2-1.el7ost.noarch Name : openstack-nova-compute Arch : noarch Version : 2014.1.2 Release : 1.el7ost >From repo : rhel-7-server-openstack-5.0-rpms Below are the errors of the above bug I see when I boot an instance. Please let me know the solution/work-around. Thanks a lot! In /var/log/nova/nova-compute.log: ============================== 2015-01-05 11:31:15.870 5275 ERROR nova.compute.manager [req-9dee8033-a261-4a89-9477-772141cb747e ca5d4869d4e2464bb6e1e3c12a82c3a2 4dd830d71afb48d6a5e3970249669970] [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Instance failed to spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Traceback (most recent call last): 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1738, in _spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2289, in spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3710, in _create_domain_and_network 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] raise exception.VirtualInterfaceCreateException() 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] VirtualInterfaceCreateException: Virtual Interface creation failed In /var/log/neutron/server.log: ========================= 2015-01-05 11:11:40.321 3888 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'cc051252-1147-43a7-8cb2-0c9f2aa26c1c', 'name': 'network-vif-unplugged', 'server_uuid': u'13cfb377-4fc4-4fbf-ac53-c0a0d7904b93'}] 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova Traceback (most recent call last): 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/neutron/notifiers/nova.py", line 221, in send_events 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova batched_events) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/v1_1/contrib/server_external_events.py", line 39, in create 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova return_raw=True) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 152, in _create 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova _resp, body = self.api.client.post(url, body=body) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 312, in post 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova return self._cs_request(url, 'POST', **kwargs) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 286, in _cs_request 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova **kwargs) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 268, in _time_request 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova resp, body = self.request(url, method, **kwargs) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 262, in request 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova raise exceptions.from_response(resp, body, url, method) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova NotFound: No instances found for any event (HTTP 404) (Request-ID: req-240de890-6511-4acc-b873-49deb7c6ae56) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova Regards, Vikram Hosakote OpenStack Software Engineer | vhosakot at cisco.com Cloud and Virtualization Group | Cisco Systems Boxborough MA | Work : 978-936-8799 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vhosakot at cisco.com Tue Jan 6 02:35:47 2015 From: vhosakot at cisco.com (Vikram Hosakote (vhosakot)) Date: Tue, 6 Jan 2015 02:35:47 +0000 Subject: [Rdo-list] RDO neutron bug 1087589 In-Reply-To: References: Message-ID: Hi, I have been hitting the RDO bug https://bugzilla.redhat.com/show_bug.cgi?id=1087589, and not able to boot a nova instance. I see that the fix https://review.openstack.org/#/c/92387/ was merged on May 29th 2014. Is this fix available in the latest RDO ? Below are the package versions of neutron and nova in my RHEL 7 IceHouse setup. How can I check if the fix is available in my packages below ? Nova: ===== [root at compute1 nova(keystone_admin)]# rpm -qa | grep -i openstack | grep neutron openstack-neutron-openvswitch-2014.1.2-2.el7ost.noarch openstack-neutron-2014.1.2-2.el7ost.noarch [root at compute1 nova(keystone_admin)]# yum info openstack-neutron-openvswitch-2014.1.2-2.el7ost.noarch Name : openstack-neutron-openvswitch Arch : noarch Version : 2014.1.2 Release : 2.el7ost >From repo : rhel-7-server-openstack-5.0-rpms [root at compute1 nova(keystone_admin)]# yum info openstack-neutron-2014.1.2-2.el7ost.noarch Name : openstack-neutron Arch : noarch Version : 2014.1.2 Release : 2.el7ost >From repo : rhel-7-server-openstack-5.0-rpms Neutron: ======== [root at compute1 nova(keystone_admin)]# rpm -qa | grep -i openstack | grep nova openstack-nova-common-2014.1.2-1.el7ost.noarch openstack-nova-compute-2014.1.2-1.el7ost.noarch [root at compute1 nova(keystone_admin)]# yum info openstack-nova-common-2014.1.2-1.el7ost.noarch Name : openstack-nova-common Arch : noarch Version : 2014.1.2 Release : 1.el7ost >From repo : rhel-7-server-openstack-5.0-rpms [root at compute1 nova(keystone_admin)]# yum info openstack-nova-compute-2014.1.2-1.el7ost.noarch Name : openstack-nova-compute Arch : noarch Version : 2014.1.2 Release : 1.el7ost >From repo : rhel-7-server-openstack-5.0-rpms Below are the errors of the above bug I see when I boot an instance. Please let me know the solution/work-around. Thanks a lot! In /var/log/nova/nova-compute.log: ============================== 2015-01-05 11:31:15.870 5275 ERROR nova.compute.manager [req-9dee8033-a261-4a89-9477-772141cb747e ca5d4869d4e2464bb6e1e3c12a82c3a2 4dd830d71afb48d6a5e3970249669970] [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Instance failed to spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Traceback (most recent call last): 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1738, in _spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2289, in spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3710, in _create_domain_and_network 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] raise exception.VirtualInterfaceCreateException() 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] VirtualInterfaceCreateException: Virtual Interface creation failed In /var/log/neutron/server.log: ========================= 2015-01-05 11:11:40.321 3888 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'cc051252-1147-43a7-8cb2-0c9f2aa26c1c', 'name': 'network-vif-unplugged', 'server_uuid': u'13cfb377-4fc4-4fbf-ac53-c0a0d7904b93'}] 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova Traceback (most recent call last): 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/neutron/notifiers/nova.py", line 221, in send_events 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova batched_events) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/v1_1/contrib/server_external_events.py", line 39, in create 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova return_raw=True) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 152, in _create 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova _resp, body = self.api.client.post(url, body=body) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 312, in post 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova return self._cs_request(url, 'POST', **kwargs) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 286, in _cs_request 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova **kwargs) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 268, in _time_request 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova resp, body = self.request(url, method, **kwargs) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 262, in request 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova raise exceptions.from_response(resp, body, url, method) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova NotFound: No instances found for any event (HTTP 404) (Request-ID: req-240de890-6511-4acc-b873-49deb7c6ae56) 2015-01-05 11:11:40.321 3888 TRACE neutron.notifiers.nova Regards, Vikram Hosakote OpenStack Software Engineer | vhosakot at cisco.com Cloud and Virtualization Group | Cisco Systems Boxborough MA | Work : 978-936-8799 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kchamart at redhat.com Tue Jan 6 10:35:30 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Tue, 6 Jan 2015 11:35:30 +0100 Subject: [Rdo-list] RDO neutron bug 1087589 In-Reply-To: References: Message-ID: <20150106103530.GC16996@tesla.home> On Tue, Jan 06, 2015 at 02:34:14AM +0000, Vikram Hosakote (vhosakot) wrote: > Hi, > > I have been hitting the RDO bug > https://bugzilla.redhat.com/show_bug.cgi?id=1087589, and not able to > boot a nova instance. As you might have noticed, that bug is fixed upstream more than 6 months ago, so it's reasonable to expect to have it in current RDO stable versions for sure (Juno). > I see that the fix https://review.openstack.org/#/c/92387/ was merged > on May 29th 2014. Is this fix available in the latest RDO ? I checked the source of python-neutron RPM for for both CentOS (from latest RDO) and your package version -- the above fix is available in both. - python-neutron-2014.2.1-1.el7.centos.noarch.rpm (From here https://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/) - python-neutron-2014.1.2-2.el7ost.noarch.rpm > Below are the package versions of neutron and nova in my RHEL 7 > IceHouse setup. How can I check if the fix is available in my packages > below ? That fix is part of this file: usr/lib/python2.7/site-packages/neutron/common/config.py You can try two things: - In this file /usr/lib/python2.7/site-packages/neutron/common/config.py, you can check if you have the relevant code snippet: . . . cfg.StrOpt('nova_url', default='http://127.0.0.1:8774/v2', . . . - In your /etc/neutron.conf, ensure the 'nova_url' config parameter has the Nova v2 API version number in the URL: nova_url = http://127.0.0.1:8774/v2 [. . .] > Below are the errors of the above bug I see when I boot an instance. Please let me know the solution/work-around. Thanks a lot! > > In /var/log/nova/nova-compute.log: > ============================== > > 2015-01-05 11:31:15.870 5275 ERROR nova.compute.manager [req-9dee8033-a261-4a89-9477-772141cb747e ca5d4869d4e2464bb6e1e3c12a82c3a2 4dd830d71afb48d6a5e3970249669970] [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Instance failed to spawn > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Traceback (most recent call last): > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1738, in _spawn > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2289, in spawn > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3710, in _create_domain_and_network > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] raise exception.VirtualInterfaceCreateException() > 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] VirtualInterfaceCreateException: Virtual Interface creation failed Are you able to consistently reproduce this issue in a different test environment? -- /kashyap From rbowen at redhat.com Tue Jan 6 14:28:19 2015 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 06 Jan 2015 09:28:19 -0500 Subject: [Rdo-list] [Rdo-newsletter] RDO Community newsletter, January 2015 Message-ID: <54ABF103.6080102@redhat.com> January 2015 RDO Community Newsletter Thanks for being part of the RDO community. 2015 is already shaping up to be an exciting year for RDO, and for OpenStack in general. In this first newsletter of the year, we'd like to talk about some of what's coming this year. Quick links: * Quick Start - http://openstack.redhat.com/quickstart * Mailing Lists - https://openstack.redhat.com/Mailing_lists * RDO packages - https://repos.fedorapeople.org/repos/openstack/openstack-juno/ * RDO blog - http://rdoproject.org/blog * Q&A - http://ask.openstack.org/ * RDO and CentOS We've been talking for a long time about the relationship between RDO and CentOS. CentOS is where you get the best experience with RDO, because it's where it's getting the most testing. It's the perfect platform to do your testing and proof of concept installs. Then, when you're ready to go to production, you can stick with CentOS, or, if you want a supported enterprise platform, the transition to RHEL is a is a simple one because of how close it is to Red Hat Enterprise Linux. In the last few weeks of 2014, we strengthened that relationship with CentOS in several ways, largely as a result of conversations in Paris, at the OpenStack Summit in November. The first of these shifts is that we've moved the CI (Continuous Integration) effort to the CentOS community, where we can get a wider involvement in the process from people outside of Red Hat. So, starting early this year, you'll find RDO testing happening on http://ci.centos.org/ so that we're always certain that everything is working on this important platform. Then, at our meeting in Paris, many people said that the packaging effort needed to be entirely in the open, whereas we'd been doing some of it "behind the wall" at Red Hat. So we're moving the RDO packaging effort into the CentOS CBS - the Community Build System. You can read more about the CBS at http://wiki.centos.org/HowTos/CommunityBuildSystem and you can read our documentation about packaging RDO at http://openstack.redhat.com/packaging/ We need your feedback about this document, and your experiences as you try it out, so that we can improve that process, and get more people involved in packaging RDO. And, as an umbrella for these efforts, we're working to create a Cloud Infrastructure SIG to coordinate the efforts of packaging OpenStack, and other cloud infrastructures, on the CentOS platform, as well as the interactions with other SIGs to ensure interoperability, so that people running CentOS can use all of these various things together seamlessly. You can read more about the Cloud SIG effort at http://wiki.centos.org/SpecialInterestGroup/Cloud and expect that to progress rapidly in the coming weeks and months. * Juno, Kilo, L___ In October 2014, OpenStack Juno was released, and the OpenStack Summit in Paris focuses on planning for the next release, code-named Kilo. On April 30th, OpenStack Kilo will be released - https://wiki.openstack.org/wiki/Kilo_Release_Schedule - featuring many significant improvements that were planned at the OpenStack Summit in Paris. Starting in February of this year, expect a series of posts by various OpenStack engineers telling you what will be coming in Kilo. Then, in May (18th - 22nd), we'll be gathering in Vancouver for the OpenStack Summit,/ where work will begin on the 'L' version. You'll find some preliminary information about the event at https://www.openstack.org/summit/vancouver-2015/ If you're looking for RDO enthusiasts, we'll be at lots of other events, too, including: * FOSDEM - http://fosdem.org/ where we're hoping to find a room for an RDO community meetup. While you're there, drop by the CentOS table, and the OpenStack table, as well as the numerous other great community projects that will be represented. January 31 and February 1, in Brussels, Belgium. * SCALE - The Southern California Linux Expo - http://www.socallinuxexpo.org/scale13x , February 19-22 in Los Angeles. * Meetups - there are dozens of OpenStack meetups every week, around the world. Some of these include deep technical content, while others are primarily social in nature. These informal gatherings are the best place to get together with other OpenStack enthusiasts and discuss the daily struggle. If you're presenting at a Meetup, please let me know so that I can help you get the word out to the community. And if you attend an OpenStack meetup, we'd like to hear about your experience, and what you learned. Find meetups in your area at http://meetup.com/ or look for our weekly meetup announcements on the rdo-list mailing list. * Ask.OpenStack.org As you're no doubt aware, the very best place to ask questions about OpenStack is the site that says it in its name - http://ask.openstack.org/ We've long encouraged RDO users to ask their questions there, because it gives a wider pool of experts to answer the questions. Also, since RDO is a packaging of OpenStack, without any changes or patches, most of the questions that you might ask about it are, in fact, questions about upstream OpenStack. It's also a great way to sharpen your own expertise, by trying to answer the questions that you know something about, or identify questions that have already been answered, and direct the asker to the answer that's already been provided. If you're interested in being on the list of people that I contact with unanswered questions, please let me know, along with what topics you'd like to be contacted for. This helps us get people's questions answered quickly without you having to check the site every day. * Keep in touch There's lots of ways to stay in in touch with what's going in in the RDO community. The best ways are ... * Follow us on Twitter - http://twitter.com/rdocommunity * Google+ - http://tm3.org/rdogplus * Facebook - http://facebook.com/rdocommunity * rdo-list mailing list - http://www.redhat.com/mailman/listinfo/rdo-list * This newsletter - http://www.redhat.com/mailman/listinfo/rdo-newsletter * RDO Q&A - http://ask.openstack.org/ * IRC - #rdo on Freenode.irc.net Finally, remember that the OpenStack User Survey is always open, so every time you deploy a new OpenStack cloud, go update your records at https://www.openstack.org/user-survey/ so that, when Vancouver rolls around, we have a clearer picture of the OpenStack usage out in the wild. Thanks again for being part of the RDO community! -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ _______________________________________________ Rdo-newsletter mailing list Rdo-newsletter at redhat.com https://www.redhat.com/mailman/listinfo/rdo-newsletter From vhosakot at cisco.com Tue Jan 6 17:54:23 2015 From: vhosakot at cisco.com (Vikram Hosakote (vhosakot)) Date: Tue, 6 Jan 2015 17:54:23 +0000 Subject: [Rdo-list] RDO neutron bug 1087589 In-Reply-To: <20150106103530.GC16996@tesla.home> References: <20150106103530.GC16996@tesla.home> Message-ID: [Removed rhos-maint at redhat.com as I saw an email sent to it failed and could not be delivered] Hi Kashyap, Thanks a lot for your reply. I do see the fix in my environment. In /usr/lib/python2.7/site-packages/neutron/common/config.py, I see the following code snippet at line numbers 89 and 90. 89 cfg.StrOpt('nova_url', 90 default='http://127.0.0.1:8774/v2', In /etc/neutron/neutron.conf, I do have the Nova v2 API version number in the URL below. But, instead of 127.0.0.1, I have the IP address of the network host which is same as CONFIG_NETWORK_HOSTS in my packstack-answers.txt. # URL for connection to nova (Only supports one nova region currently). nova_url = http://172.29.68.136:8774/v2 I have the below line in my packstack-answers.txt. CONFIG_NETWORK_HOSTS=172.29.68.136 Yes, I can reproduce this issue every single time. Am I seeing a new bug ? Please let me know if there is any work-around, and also if I need to send any logs/debugs. Regards, Vikram Hosakote OpenStack Software Engineer | vhosakot at cisco.com Cloud and Virtualization Group | Cisco Systems Boxborough MA | Work : 978-936-8799 From: Kashyap Chamarthy > Date: Tuesday, January 6, 2015 at 5:35 AM To: Vikram Hosakote > Cc: "rdo-list at redhat.com" >, "rhos-maint at redhat.com" > Subject: Re: [Rdo-list] RDO neutron bug 1087589 On Tue, Jan 06, 2015 at 02:34:14AM +0000, Vikram Hosakote (vhosakot) wrote: Hi, I have been hitting the RDO bug https://bugzilla.redhat.com/show_bug.cgi?id=1087589, and not able to boot a nova instance. As you might have noticed, that bug is fixed upstream more than 6 months ago, so it's reasonable to expect to have it in current RDO stable versions for sure (Juno). I see that the fix https://review.openstack.org/#/c/92387/ was merged on May 29th 2014. Is this fix available in the latest RDO ? I checked the source of python-neutron RPM for for both CentOS (from latest RDO) and your package version -- the above fix is available in both. - python-neutron-2014.2.1-1.el7.centos.noarch.rpm (From here https://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/) - python-neutron-2014.1.2-2.el7ost.noarch.rpm Below are the package versions of neutron and nova in my RHEL 7 IceHouse setup. How can I check if the fix is available in my packages below ? That fix is part of this file: usr/lib/python2.7/site-packages/neutron/common/config.py You can try two things: - In this file /usr/lib/python2.7/site-packages/neutron/common/config.py, you can check if you have the relevant code snippet: . . . cfg.StrOpt('nova_url', default='http://127.0.0.1:8774/v2', . . . - In your /etc/neutron.conf, ensure the 'nova_url' config parameter has the Nova v2 API version number in the URL: nova_url = http://127.0.0.1:8774/v2 [. . .] Below are the errors of the above bug I see when I boot an instance. Please let me know the solution/work-around. Thanks a lot! In /var/log/nova/nova-compute.log: ============================== 2015-01-05 11:31:15.870 5275 ERROR nova.compute.manager [req-9dee8033-a261-4a89-9477-772141cb747e ca5d4869d4e2464bb6e1e3c12a82c3a2 4dd830d71afb48d6a5e3970249669970] [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Instance failed to spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Traceback (most recent call last): 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1738, in _spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2289, in spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3710, in _create_domain_and_network 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] raise exception.VirtualInterfaceCreateException() 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] VirtualInterfaceCreateException: Virtual Interface creation failed Are you able to consistently reproduce this issue in a different test environment? -- /kashyap -------------- next part -------------- An HTML attachment was scrubbed... URL: From dneary at redhat.com Tue Jan 6 20:23:12 2015 From: dneary at redhat.com (Dave Neary) Date: Tue, 06 Jan 2015 15:23:12 -0500 Subject: [Rdo-list] Strange question: multiple NICs in VMs? Message-ID: <54AC4430.6080504@redhat.com> Hi, I am trying to automate the deployment of RDO on top of RDO, using OpenDaylight for networking - not for real work, just for validating the installation procedure. I would like to have the instances I create in the OpenStack cloud to have 2 NICs each so that I can simulate a management & data network configuration, but I don't know how to create a virtual NIC in an instance (or even if this is possible, or maybe doesn't make any sense). Has anyone ever done this? Any tips on making it work? Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338 From marius at remote-lab.net Tue Jan 6 20:40:07 2015 From: marius at remote-lab.net (Marius Cornea) Date: Tue, 6 Jan 2015 21:40:07 +0100 Subject: [Rdo-list] Strange question: multiple NICs in VMs? In-Reply-To: <54AC4430.6080504@redhat.com> References: <54AC4430.6080504@redhat.com> Message-ID: Hi Dave, You can try attaching 2 different networks to the instances. This way you should get a nic for each of the network inside the VMs. Thanks, Marius On Tue, Jan 6, 2015 at 9:23 PM, Dave Neary wrote: > Hi, > > I am trying to automate the deployment of RDO on top of RDO, using > OpenDaylight for networking - not for real work, just for validating the > installation procedure. > > I would like to have the instances I create in the OpenStack cloud to > have 2 NICs each so that I can simulate a management & data network > configuration, but I don't know how to create a virtual NIC in an > instance (or even if this is possible, or maybe doesn't make any sense). > > Has anyone ever done this? Any tips on making it work? > > Thanks, > Dave. > > -- > Dave Neary - NFV/SDN Community Strategy > Open Source and Standards, Red Hat - http://community.redhat.com > Ph: +1-978-399-2182 / Cell: +1-978-799-3338 > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars at redhat.com Tue Jan 6 21:50:05 2015 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Tue, 6 Jan 2015 16:50:05 -0500 Subject: [Rdo-list] Strange question: multiple NICs in VMs? In-Reply-To: <54AC4430.6080504@redhat.com> References: <54AC4430.6080504@redhat.com> Message-ID: <20150106215005.GB11004@redhat.com> On Tue, Jan 06, 2015 at 03:23:12PM -0500, Dave Neary wrote: > I am trying to automate the deployment of RDO on top of RDO, using > OpenDaylight for networking - not for real work, just for validating the > installation procedure. > > I would like to have the instances I create in the OpenStack cloud to > have 2 NICs each so that I can simulate a management & data network > configuration, but I don't know how to create a virtual NIC in an > instance (or even if this is possible, or maybe doesn't make any sense). If you have multiple networks avaiable: $ nova net-list +--------------------------------------+----------+------+ | ID | Label | CIDR | +--------------------------------------+----------+------+ | ba4d7bd0-95de-4527-8ae8-c7f640fd2561 | net1 | None | | 02d13742-c783-4927-82df-bb7c30394f12 | ext-host | None | | 028d70dd-67b8-4901-8bdd-0c62b06cce2d | ext-nat | None | | 18fc1b31-9b2c-4b6e-8dea-7e04bfd1eb43 | net0 | None | +--------------------------------------+----------+------+ Then when you boot an instance you can specify a NIC for each network: $ nova boot \ --nic net-id=18fc1b31-9b2c-4b6e-8dea-7e04bfd1eb43 \ --nic net-id=ba4d7bd0-95de-4527-8ae8-c7f640fd2561 \ --flavor m1.small --image someimage my-nova-server This would result in: $ ssh (ip address of my-nova-server) $ ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether fa:16:3e:4b:86:0f brd ff:ff:ff:ff:ff:ff inet 10.0.0.101/24 brd 10.0.0.255 scope global dynamic eth0 valid_lft 86396sec preferred_lft 86396sec inet6 fe80::f816:3eff:fe4b:860f/64 scope link valid_lft forever preferred_lft forever 3: eth1: mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether fa:16:3e:9a:f8:07 brd ff:ff:ff:ff:ff:ff inet 10.1.0.2/24 brd 10.1.0.255 scope global dynamic eth1 valid_lft 86396sec preferred_lft 86396sec inet6 fe80::f816:3eff:fe9a:f807/64 scope link valid_lft forever preferred_lft forever You will want to make sure that either (a) you create all but one of your subnets with --no-gateway or (b) you boot images that won't try to use dhcp on all available interfaces, because otherwise you don't know which interface will get used for the default route and things like floating ip association may not functional properly. -- Lars Kellogg-Stedman | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lpeer at redhat.com Wed Jan 7 08:42:07 2015 From: lpeer at redhat.com (Livnat Peer) Date: Wed, 07 Jan 2015 10:42:07 +0200 Subject: [Rdo-list] Query regarding RDO Juno-1 install on CentOS7 In-Reply-To: <54AA7150.40301@redhat.com> References: <54A16517.60803@laimbock.com> <54A3FF86.5090208@redhat.com> <54A480E6.2000901@redhat.com> <54AA7150.40301@redhat.com> Message-ID: <54ACF15F.6040600@redhat.com> On 01/05/2015 01:11 PM, Livnat Peer wrote: > On 01/01/2015 05:03 AM, Deepak Shetty wrote: >> Thanks perry, i googled too, but having instructions as part of the rdo >> quickstart is ideal as it is in the flow of things. For eg. I installed >> centos7 via pxe install and since rdo quick start didn't say anything >> specific abt Nm i just followed basic install process, only to know >> later that nm need to be disabled, which is not easy for someone not >> fairly expert in networking stuff so having the right cmds as part of >> rdo quick start pre reqs would help rdo beginerrs a lot >> > > I agree we should document that in the quick start. > Kuba - can you please add the steps to turn-off NM in the quickstart page. > > Also the current list of bugs that blocks us from enabling NM are - > > https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&list_id=3123976&namedcmd=openstack-nm&remaction=run&sharer_id=287527 > The above is a search result, instead we can use a tracker bug - Bug 1179614 - Tracker - Network Manager can not be used in openstack deployments (https://bugzilla.redhat.com/show_bug.cgi?id=1179614) Livnat > Livnat >> On Jan 1, 2015 4:34 AM, "Perry Myers" > > wrote: >> >> On 12/31/2014 09:34 AM, Deepak Shetty wrote: >> > In which case RDO quickstart or some other place should have good info >> > on how to disable NM and enable ifcfg networking for started who >> look at >> > quickstart or RDO faqs to get hints >> >> google search for 'rdo disable network manager' turned up this: >> https://openstack.redhat.com/Fedora_20_with_existing_network >> >> it's a bit more than you would need, but in there are simple steps for >> disabling network manager >> >> But I agree that having more accessible HOWTOs for this specific area >> would make sense. This wiki page is Fedora specific (though the same >> steps should work on CentOS 7 I believe) and doesn't cover initial >> installation, only after install how to disable NM. >> >> I believe though, that removing network manager in a kickstart based >> installation of CentOS or Fedora is as simple as adding NetworkManager >> to the list of blacklisted packages. >> >> (i.e. under %packages add -NetworkManager) [1] >> >> Perry >> >> [1] >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-packageselection.html >> > From joubert at redrat.com.br Wed Jan 7 11:28:36 2015 From: joubert at redrat.com.br (Joubert RedRat) Date: Wed, 7 Jan 2015 09:28:36 -0200 Subject: [Rdo-list] possible workaround on RDO to install in CentOS 7 Message-ID: Hi guys, I'm Joubert and is my first post here. A few days I tried to run RDO on CentOS 7 but don't work to run instance ( https://ask.openstack.org/en/question/56572/no-valid-host-was-found-on-start-instance/ ) Yesterday I tried to install RDO on CentOS 7 in EC2 instance and ... runs normally! Then I decided to see all possible logs and compare. I found a error that not had in RDO EC2, "qemu-kvm: -chardev pty,id=charserial1: Failed to create chardev" https://gist.github.com/joubertredrat/f2863c9105385beb5ae6 Based on this I searched a lot and found this article https://www.centos.org/forums/viewtopic.php?f=48&t=48075#p206211 I reinstalled 3 times my server, RDO, changed fstab file, rebooted server and on 3 times worked fine, as in log https://gist.github.com/joubertredrat/7e32056a2ecdec1d61fb Then in this case isn't a good way to put this on RDO workarounds to CentOS 7 users? Regards -- "O que quer que voc? fa?a na vida, ser? insignificante. Mas ? muito importante que voc? o fa?a... por que ningu?m mais o far?." Gandhi "Whatever you do will be insignificant, but it is very important that you do it... because no one else will it." Gandhi ___________________________________________________________________ *Joubert "RedRat"* - Consultor em tecnologia - Technology consultant /me at Linkedin and Github *~(,,">* RedRat Consultoria -------------- next part -------------- An HTML attachment was scrubbed... URL: From marius at remote-lab.net Wed Jan 7 11:44:21 2015 From: marius at remote-lab.net (Marius Cornea) Date: Wed, 7 Jan 2015 12:44:21 +0100 Subject: [Rdo-list] possible workaround on RDO to install in CentOS 7 In-Reply-To: References: Message-ID: Hi Joubert, What are you SELinux settings? If set to Enforcing try changing it to Permissive (setenforce 0) and see if it helps. Thanx, Marius On Wed, Jan 7, 2015 at 12:28 PM, Joubert RedRat wrote: > Hi guys, > > I'm Joubert and is my first post here. > > A few days I tried to run RDO on CentOS 7 but don't work to run instance ( > https://ask.openstack.org/en/question/56572/no-valid-host-was-found-on-start-instance/ > ) > Yesterday I tried to install RDO on CentOS 7 in EC2 instance and ... runs > normally! Then I decided to see all possible logs and compare. > > I found a error that not had in RDO EC2, "qemu-kvm: -chardev > pty,id=charserial1: Failed to create chardev" > https://gist.github.com/joubertredrat/f2863c9105385beb5ae6 > > Based on this I searched a lot and found this article > https://www.centos.org/forums/viewtopic.php?f=48&t=48075#p206211 > > I reinstalled 3 times my server, RDO, changed fstab file, rebooted server > and on 3 times worked fine, as in log > https://gist.github.com/joubertredrat/7e32056a2ecdec1d61fb > > > Then in this case isn't a good way to put this on RDO workarounds to > CentOS 7 users? > > > Regards > > -- > "O que quer que voc? fa?a na vida, ser? insignificante. Mas ? muito > importante que voc? o fa?a... por que ningu?m mais o far?." Gandhi > "Whatever you do will be insignificant, but it is very important that you > do it... because no one else will it." Gandhi > ___________________________________________________________________ > *Joubert "RedRat"* - Consultor em tecnologia - Technology consultant > /me at Linkedin and Github > > *~(,,">* RedRat Consultoria > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Wed Jan 7 12:33:30 2015 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Wed, 7 Jan 2015 07:33:30 -0500 Subject: [Rdo-list] Strange question: multiple NICs in VMs? In-Reply-To: <54AC4430.6080504@redhat.com> References: <54AC4430.6080504@redhat.com> Message-ID: Not sure , it's that what you want, but libguestfs-tools (CentOS 7) or qemu-nbd (Fedora) allows modify qcow2 image for 2 NICs before uploading to glance with no problems. Than glance image may have as many NICs as you need. http://bderzhavets.blogspot.com/2014/08/setup-qcow2-standard-centos-7-image-to.html Boris > Date: Tue, 6 Jan 2015 15:23:12 -0500 > From: dneary at redhat.com > To: rdo-list at redhat.com > Subject: [Rdo-list] Strange question: multiple NICs in VMs? > > Hi, > > I am trying to automate the deployment of RDO on top of RDO, using > OpenDaylight for networking - not for real work, just for validating the > installation procedure. > > I would like to have the instances I create in the OpenStack cloud to > have 2 NICs each so that I can simulate a management & data network > configuration, but I don't know how to create a virtual NIC in an > instance (or even if this is possible, or maybe doesn't make any sense). > > Has anyone ever done this? Any tips on making it work? > > Thanks, > Dave. > > -- > Dave Neary - NFV/SDN Community Strategy > Open Source and Standards, Red Hat - http://community.redhat.com > Ph: +1-978-399-2182 / Cell: +1-978-799-3338 > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Wed Jan 7 21:55:26 2015 From: rbowen at redhat.com (Rich Bowen) Date: Wed, 07 Jan 2015 16:55:26 -0500 Subject: [Rdo-list] Fwd: [OpenStack Marketing] Call for Speakers - Vancouver OpenStack Summit In-Reply-To: <89604C09-6AAA-4185-88EA-EBB905FB30D8@openstack.org> References: <89604C09-6AAA-4185-88EA-EBB905FB30D8@openstack.org> Message-ID: <54ADAB4E.6090001@redhat.com> FYI, in case you had not seen this yet. -------- Forwarded Message -------- Subject: [OpenStack Marketing] Call for Speakers - Vancouver OpenStack Summit Date: Wed, 7 Jan 2015 15:44:08 -0600 From: Claire Massey To: marketing at lists.openstack.org Hi everyone, The Call for Speakers is now open for the May 2014 OpenStack Summit in Vancouver. Submit talks HERE: https://www.openstack.org/summit/vancouver-2015/call-for-speakers. Hurry - February 9 is the deadline to submit. Stay tuned to openstack.org/summit for updates and additional info. Cheers, Claire -------------- next part -------------- _______________________________________________ Marketing mailing list Marketing at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/marketing From vhosakot at cisco.com Thu Jan 8 05:12:53 2015 From: vhosakot at cisco.com (Vikram Hosakote (vhosakot)) Date: Thu, 8 Jan 2015 05:12:53 +0000 Subject: [Rdo-list] RDO neutron bug 1087589 In-Reply-To: References: <20150106103530.GC16996@tesla.home> Message-ID: Hi Kashyap, Could you please let me know if I?m seeing a new bug, and if there is any work-around for this issue. I can reproduce this every single time. Regards, Vikram Hosakote OpenStack Software Engineer | vhosakot at cisco.com Cloud and Virtualization Group | Cisco Systems Boxborough MA | Work : 978-936-8799 From: Vikram Hosakote > Date: Tuesday, January 6, 2015 at 12:54 PM To: Kashyap Chamarthy > Cc: "rdo-list at redhat.com" > Subject: Re: [Rdo-list] RDO neutron bug 1087589 [Removed rhos-maint at redhat.com as I saw an email sent to it failed and could not be delivered] Hi Kashyap, Thanks a lot for your reply. I do see the fix in my environment. In /usr/lib/python2.7/site-packages/neutron/common/config.py, I see the following code snippet at line numbers 89 and 90. 89 cfg.StrOpt('nova_url', 90 default='http://127.0.0.1:8774/v2', In /etc/neutron/neutron.conf, I do have the Nova v2 API version number in the URL below. But, instead of 127.0.0.1, I have the IP address of the network host which is same as CONFIG_NETWORK_HOSTS in my packstack-answers.txt. # URL for connection to nova (Only supports one nova region currently). nova_url = http://172.29.68.136:8774/v2 I have the below line in my packstack-answers.txt. CONFIG_NETWORK_HOSTS=172.29.68.136 Yes, I can reproduce this issue every single time. Am I seeing a new bug ? Please let me know if there is any work-around, and also if I need to send any logs/debugs. Regards, Vikram Hosakote OpenStack Software Engineer | vhosakot at cisco.com Cloud and Virtualization Group | Cisco Systems Boxborough MA | Work : 978-936-8799 From: Kashyap Chamarthy > Date: Tuesday, January 6, 2015 at 5:35 AM To: Vikram Hosakote > Cc: "rdo-list at redhat.com" >, "rhos-maint at redhat.com" > Subject: Re: [Rdo-list] RDO neutron bug 1087589 On Tue, Jan 06, 2015 at 02:34:14AM +0000, Vikram Hosakote (vhosakot) wrote: Hi, I have been hitting the RDO bug https://bugzilla.redhat.com/show_bug.cgi?id=1087589, and not able to boot a nova instance. As you might have noticed, that bug is fixed upstream more than 6 months ago, so it's reasonable to expect to have it in current RDO stable versions for sure (Juno). I see that the fix https://review.openstack.org/#/c/92387/ was merged on May 29th 2014. Is this fix available in the latest RDO ? I checked the source of python-neutron RPM for for both CentOS (from latest RDO) and your package version -- the above fix is available in both. - python-neutron-2014.2.1-1.el7.centos.noarch.rpm (From here https://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/) - python-neutron-2014.1.2-2.el7ost.noarch.rpm Below are the package versions of neutron and nova in my RHEL 7 IceHouse setup. How can I check if the fix is available in my packages below ? That fix is part of this file: usr/lib/python2.7/site-packages/neutron/common/config.py You can try two things: - In this file /usr/lib/python2.7/site-packages/neutron/common/config.py, you can check if you have the relevant code snippet: . . . cfg.StrOpt('nova_url', default='http://127.0.0.1:8774/v2', . . . - In your /etc/neutron.conf, ensure the 'nova_url' config parameter has the Nova v2 API version number in the URL: nova_url = http://127.0.0.1:8774/v2 [. . .] Below are the errors of the above bug I see when I boot an instance. Please let me know the solution/work-around. Thanks a lot! In /var/log/nova/nova-compute.log: ============================== 2015-01-05 11:31:15.870 5275 ERROR nova.compute.manager [req-9dee8033-a261-4a89-9477-772141cb747e ca5d4869d4e2464bb6e1e3c12a82c3a2 4dd830d71afb48d6a5e3970249669970] [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Instance failed to spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] Traceback (most recent call last): 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1738, in _spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2289, in spawn 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] block_device_info) 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3710, in _create_domain_and_network 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] raise exception.VirtualInterfaceCreateException() 2015-01-05 11:31:15.870 5275 TRACE nova.compute.manager [instance: 228289f2-d3c2-401d-b779-f359121b4e71] VirtualInterfaceCreateException: Virtual Interface creation failed Are you able to consistently reproduce this issue in a different test environment? -- /kashyap -------------- next part -------------- An HTML attachment was scrubbed... URL: From swapnil at linux.com Thu Jan 8 09:11:44 2015 From: swapnil at linux.com (Swapnil Jain) Date: Thu, 8 Jan 2015 14:41:44 +0530 Subject: [Rdo-list] Error: Could not find command 'systemctl' Message-ID: <3CA49604-03A7-4C91-9618-E0EBCC9AAD8A@Linux.com> Hi, I am getting the below error while install icehouse on RHEL6. its looking for systemctl which is not available. 172.16.254.2_osclient.pp: [ DONE ] 172.16.254.2_horizon.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 172.16.254.2_horizon.pp Error: Could not find command 'systemctl' You will find full trace in log /var/tmp/packstack/20150108-222031-ha6FwJ/manifests/172.16.254.2_horizon.pp.log Please check log file /var/tmp/packstack/20150108-222031-ha6FwJ/openstack-setup.log for more information ? Swapnil Jain | Swapnil at Linux.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: From Yaniv.Kaul at emc.com Thu Jan 8 12:12:02 2015 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Thu, 8 Jan 2015 07:12:02 -0500 Subject: [Rdo-list] tempest_config fails if network service is not enabled Message-ID: <648473255763364B961A02AC3BE1060D03C9B16E22@MX19A.corp.emc.com> Not everyone needs network for testing... [root at lgdrm1499 tempest(keystone_admin)]# tools/config_tempest.py --create identity.uri $OS_AUTH_URL identity.admin_username $OS_USERNAME identity.admin_password $OS_PASSWORD identity.admin_tenant_name $OS_TENANT_NAME 2015-01-08 14:10:41,932 - tempest.common.api_discovery - ERROR - Request on service 'network' with url 'http://10.102.37.163:9696/v2.0/extensions.json' failed Traceback (most recent call last): File "tools/config_tempest.py", line 782, in main() File "tools/config_tempest.py", line 137, in main services = api_discovery.discover(clients.identity) File "/root/tempest/tempest/common/api_discovery.py", line 143, in discover services[name]['extensions'] = service.get_extensions() File "/root/tempest/tempest/common/api_discovery.py", line 83, in get_extensions body = self.do_get(self.service_url + 'v2.0/extensions.json') File "/root/tempest/tempest/common/api_discovery.py", line 47, in do_get raise e socket.error: [Errno 111] Connection refused (I believe it used to work in the past, so it's most likely a regression). TIA, Y. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkranz at redhat.com Thu Jan 8 14:03:56 2015 From: dkranz at redhat.com (David Kranz) Date: Thu, 08 Jan 2015 09:03:56 -0500 Subject: [Rdo-list] tempest_config fails if network service is not enabled In-Reply-To: <648473255763364B961A02AC3BE1060D03C9B16E22@MX19A.corp.emc.com> References: <648473255763364B961A02AC3BE1060D03C9B16E22@MX19A.corp.emc.com> Message-ID: <54AE8E4C.5080500@redhat.com> On 01/08/2015 07:12 AM, Kaul, Yaniv wrote: > > Not everyone needs network for testing... > > [root at lgdrm1499 tempest(keystone_admin)]# tools/config_tempest.py > --create identity.uri $OS_AUTH_URL identity.admin_username > $OS_USERNAME identity.admin_password $OS_PASSWORD > identity.admin_tenant_name $OS_TENANT_NAME > > 2015-01-08 14:10:41,932 - tempest.common.api_discovery - ERROR - > Request on service 'network' with url > 'http://10.102.37.163:9696/v2.0/extensions.json' failed > > Traceback (most recent call last): > > File "tools/config_tempest.py", line 782, in > > main() > > File "tools/config_tempest.py", line 137, in main > > services = api_discovery.discover(clients.identity) > > File "/root/tempest/tempest/common/api_discovery.py", line 143, in > discover > > services[name]['extensions'] = service.get_extensions() > > File "/root/tempest/tempest/common/api_discovery.py", line 83, in > get_extensions > > body = self.do_get(self.service_url + 'v2.0/extensions.json') > > File "/root/tempest/tempest/common/api_discovery.py", line 47, in do_get > > raise e > > socket.error: [Errno 111] Connection refused > > (I believe it used to work in the past, so it's most likely a regression). > The discovery is done for each service listed in the keystone catalog. Is it possible that your catalog lists a neutron endpoint but neutron was not configured or its port is blocked? -David > > TIA, > > Y. > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From Yaniv.Kaul at emc.com Thu Jan 8 14:33:20 2015 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Thu, 8 Jan 2015 09:33:20 -0500 Subject: [Rdo-list] tempest_config fails if network service is not enabled In-Reply-To: <54AE8E4C.5080500@redhat.com> References: <648473255763364B961A02AC3BE1060D03C9B16E22@MX19A.corp.emc.com> <54AE8E4C.5080500@redhat.com> Message-ID: <648473255763364B961A02AC3BE1060D03C9B16E60@MX19A.corp.emc.com> Correct - just found out that Neutron is installed, for some reason, but fails to connect to the AMQP server for some unknown reason. Investigating... Y. From: David Kranz [mailto:dkranz at redhat.com] Sent: Thursday, January 08, 2015 4:04 PM To: Kaul, Yaniv; rdo-list at redhat.com Subject: Re: [Rdo-list] tempest_config fails if network service is not enabled On 01/08/2015 07:12 AM, Kaul, Yaniv wrote: Not everyone needs network for testing... [root at lgdrm1499 tempest(keystone_admin)]# tools/config_tempest.py --create identity.uri $OS_AUTH_URL identity.admin_username $OS_USERNAME identity.admin_password $OS_PASSWORD identity.admin_tenant_name $OS_TENANT_NAME 2015-01-08 14:10:41,932 - tempest.common.api_discovery - ERROR - Request on service 'network' with url 'http://10.102.37.163:9696/v2.0/extensions.json' failed Traceback (most recent call last): File "tools/config_tempest.py", line 782, in main() File "tools/config_tempest.py", line 137, in main services = api_discovery.discover(clients.identity) File "/root/tempest/tempest/common/api_discovery.py", line 143, in discover services[name]['extensions'] = service.get_extensions() File "/root/tempest/tempest/common/api_discovery.py", line 83, in get_extensions body = self.do_get(self.service_url + 'v2.0/extensions.json') File "/root/tempest/tempest/common/api_discovery.py", line 47, in do_get raise e socket.error: [Errno 111] Connection refused (I believe it used to work in the past, so it's most likely a regression). The discovery is done for each service listed in the keystone catalog. Is it possible that your catalog lists a neutron endpoint but neutron was not configured or its port is blocked? -David TIA, Y. _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Thu Jan 8 16:55:37 2015 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Thu, 08 Jan 2015 17:55:37 +0100 Subject: [Rdo-list] Error: Could not find command 'systemctl' In-Reply-To: <3CA49604-03A7-4C91-9618-E0EBCC9AAD8A@Linux.com> References: <3CA49604-03A7-4C91-9618-E0EBCC9AAD8A@Linux.com> Message-ID: <54AEB689.5030602@redhat.com> Please report a bug for this behaviour. But first check that you run against correct repo (el6, not el7). On 01/08/2015 10:11 AM, Swapnil Jain wrote: > Hi, > > I am getting the below error while install icehouse on RHEL6. its looking for systemctl which is not available. > > 172.16.254.2_osclient.pp: [ DONE ] > 172.16.254.2_horizon.pp: [ ERROR ] > Applying Puppet manifests [ ERROR ] > > ERROR : Error appeared during Puppet run: 172.16.254.2_horizon.pp > Error: Could not find command 'systemctl' > You will find full trace in log /var/tmp/packstack/20150108-222031-ha6FwJ/manifests/172.16.254.2_horizon.pp.log > Please check log file /var/tmp/packstack/20150108-222031-ha6FwJ/openstack-setup.log for more information > > > ? > Swapnil Jain | Swapnil at Linux.com > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From swapnil at linux.com Fri Jan 9 09:19:53 2015 From: swapnil at linux.com (Swapnil Jain) Date: Fri, 9 Jan 2015 14:49:53 +0530 Subject: [Rdo-list] Error: Could not find command 'systemctl' In-Reply-To: <54AEB689.5030602@redhat.com> References: <3CA49604-03A7-4C91-9618-E0EBCC9AAD8A@Linux.com> <54AEB689.5030602@redhat.com> Message-ID: Theres already an open bug assigned but no fix yet. I fooled it by creating a bash script as /usr/bin/systemctl. A bad way of doing it but it worked ;) #!/bin/bash SER=`echo $2 |gawk -F. '{print $1}'` service $SER $1 ? Swapnil Jain | Swapnil at Linux.com RHC{A,DS,E,SA,SA-RHOS,VA}, CC{DA,NA}, MCSE, CNE > On 08-Jan-2015, at 10:25 pm, Ihar Hrachyshka wrote: > > Please report a bug for this behaviour. But first check that you run against correct repo (el6, not el7). > > On 01/08/2015 10:11 AM, Swapnil Jain wrote: >> Hi, >> >> I am getting the below error while install icehouse on RHEL6. its looking for systemctl which is not available. >> >> 172.16.254.2_osclient.pp: [ DONE ] >> 172.16.254.2_horizon.pp: [ ERROR ] >> Applying Puppet manifests [ ERROR ] >> >> ERROR : Error appeared during Puppet run: 172.16.254.2_horizon.pp >> Error: Could not find command 'systemctl' >> You will find full trace in log /var/tmp/packstack/20150108-222031-ha6FwJ/manifests/172.16.254.2_horizon.pp.log >> Please check log file /var/tmp/packstack/20150108-222031-ha6FwJ/openstack-setup.log for more information >> >> >> ? >> Swapnil Jain | Swapnil at Linux.com >> >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: From ihrachys at redhat.com Fri Jan 9 10:25:19 2015 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 09 Jan 2015 11:25:19 +0100 Subject: [Rdo-list] Error: Could not find command 'systemctl' In-Reply-To: References: <3CA49604-03A7-4C91-9618-E0EBCC9AAD8A@Linux.com> <54AEB689.5030602@redhat.com> Message-ID: <54AFAC8F.6020501@redhat.com> Do you have a link to the bug? On 01/09/2015 10:19 AM, Swapnil Jain wrote: > Theres already an open bug assigned but no fix yet. I fooled it by > creating a bash script as /usr/bin/systemctl. A bad way of doing it > but it worked ;) > > #!/bin/bash > SER=`echo $2 |gawk -F. '{print $1}'` > service $SER $1 > > > > > ? > *Swapnil Jain | Swapnil at Linux.com * > RHC{A,DS,E,SA,SA-RHOS,VA}, CC{DA,NA}, MCSE, CNE > > >> On 08-Jan-2015, at 10:25 pm, Ihar Hrachyshka > > wrote: >> >> Please report a bug for this behaviour. But first check that you run >> against correct repo (el6, not el7). >> >> On 01/08/2015 10:11 AM, Swapnil Jain wrote: >>> Hi, >>> >>> I am getting the below error while install icehouse on RHEL6. its looking for systemctl which is not available. >>> >>> 172.16.254.2_osclient.pp: [ DONE ] >>> 172.16.254.2_horizon.pp: [ ERROR ] >>> Applying Puppet manifests [ ERROR ] >>> >>> ERROR : Error appeared during Puppet run: 172.16.254.2_horizon.pp >>> Error: Could not find command 'systemctl' >>> You will find full trace in log /var/tmp/packstack/20150108-222031-ha6FwJ/manifests/172.16.254.2_horizon.pp.log >>> Please check log file /var/tmp/packstack/20150108-222031-ha6FwJ/openstack-setup.log for more information >>> >>> >>> ? >>> Swapnil Jain |Swapnil at Linux.com >>> >>> >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Fri Jan 9 21:22:04 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 21:22:04 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. Message-ID: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: From marius at remote-lab.net Fri Jan 9 21:47:49 2015 From: marius at remote-lab.net (Marius Cornea) Date: Fri, 9 Jan 2015 22:47:49 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: > Hi Support, > > I have a problem that a launched instance from openstack cannot > connect to SSH or PING > > First of all I have dump question whether my system should be NOVA > network or Neutron network. Well to keep everyone on the same page. Here is > my history. > > > 1. I did install RDO (allinone host) using the bellow steps > https://openstack.redhat.com/Quickstart > 2. Then I have used the following steps for floating IP > https://openstack.redhat.com/Floating_IP_range. > > My situtation is as follows. > * Floating IP address assignment: > I have assigned a floating IP , I did follow this steps. > https://openstack.redhat.com/Floating_IP_range > > * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it > is eno1 name)is on the same bridge as the compute host > Yes, ethernet device on 10.48.146.78 address and br-ex interface on > 10.48.146.112 > > * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing > and responding to DHCP > requests and the instance is getting IP from 10.48.146.113 (next hop) > however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed > rule on default security group) > > Here is the little diagram of my system. > > Can someone help to find what is missing. > > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: From kchamart at redhat.com Fri Jan 9 22:04:20 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Fri, 9 Jan 2015 23:04:20 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: <20150109220420.GA23907@tesla.redhat.com> On Fri, Jan 09, 2015 at 09:22:04PM +0000, Ns, Rushi wrote: > Hi Support, [A gentle note: addresing community mailing lists as "Support" is not a nice netiquette.] That said, a couple of comments in line. > I have a problem that a launched instance from openstack cannot connect to SSH or PING > > First of all I have dump question whether my system should be NOVA > network or Neutron network. If you mean, you're not sure whether to choose Nova or Neutron networking, it really depends what you're trying to do. Just to note, Nova networking will be deprecated in future in favor of Neutron, so getting familiar with Neutron will be useful. > Well to keep everyone on the same page. Here is my history. > > > 1. I did install RDO (allinone host) using the bellow steps > https://openstack.redhat.com/Quickstart 2. Then I have used the > following steps for floating IP > https://openstack.redhat.com/Floating_IP_range. > > My situtation is as follows. * Floating IP address assignment: I have > assigned a floating IP , I did follow this steps. > https://openstack.redhat.com/Floating_IP_range > > * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it > is eno1 name)is on the same bridge as the compute host Yes, ethernet > device on 10.48.146.78 address and br-ex interface on 10.48.146.112 > > * DHCP configuration: Yes, DHCP configuration is set and Neutron > hearing and responding to DHCP requests and the instance is getting IP > from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP > address (ICMP/SSH is added allowed rule on default security group) > > > Here is the little diagram of my system. > [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] > > Can someone help to find what is missing. If this is your first attempt at setting up Neutron, you might want to go through this: http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html Here's some old example of some `tcpdump` analysis[*] on different interfaces: https://gist.github.com/kashyapc/7926517 In general, when dealing with Neutron, systematic debugging will help a lot to narrow down the root cause. [*] https://gist.github.com/kashyapc/7926517 -- /kashyap From rushi.ns at sap.com Fri Jan 9 22:17:46 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 22:17:46 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: <20150109220420.GA23907@tesla.redhat.com> References: <20150109220420.GA23907@tesla.redhat.com> Message-ID: Well, I agree and admit that I shouldn?t call community as SUPPORT. My sincere apologies for that. Well going through I did all kinds of tests that are part of network neutron and read all most all the links from redhat relates the links you provided already, however my issues seems to be simple but not getting to solve as I was working on this for last 10 days and finally thought of putting into rdo-list. Yes, I agree that I am getting familiar with NEUTRON only . For now my simple issue is that I have my openstack interface eno1 on 10.48.146.77 and br-ex is : 10.48.146.112 and the VM instance is 10.48.146.113 however I cannot ssh /PING that 10.48.146.113 address ? Any ideas. Here are the commands and outputs. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------- -----------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------- -----------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------- -----------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+ ----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+ ----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+ ??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- -----------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- -----------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- -----------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race On 1/9/15, 2:04 PM, "Kashyap Chamarthy" wrote: >On Fri, Jan 09, 2015 at 09:22:04PM +0000, Ns, Rushi wrote: >> Hi Support, > >[A gentle note: addresing community mailing lists as "Support" is not a >nice netiquette.] > >That said, a couple of comments in line. > >> I have a problem that a launched instance from openstack cannot >>connect to SSH or PING >> >> First of all I have dump question whether my system should be NOVA >> network or Neutron network. > >If you mean, you're not sure whether to choose Nova or Neutron >networking, it really depends what you're trying to do. Just to note, >Nova networking will be deprecated in future in favor of Neutron, so >getting familiar with Neutron will be useful. > >> Well to keep everyone on the same page. Here is my history. >> >> >> 1. I did install RDO (allinone host) using the bellow steps >> https://openstack.redhat.com/Quickstart 2. Then I have used the >> following steps for floating IP >> https://openstack.redhat.com/Floating_IP_range. >> >> My situtation is as follows. * Floating IP address assignment: I have >> assigned a floating IP , I did follow this steps. >> https://openstack.redhat.com/Floating_IP_range >> >> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it >> is eno1 name)is on the same bridge as the compute host Yes, ethernet >> device on 10.48.146.78 address and br-ex interface on 10.48.146.112 >> >> * DHCP configuration: Yes, DHCP configuration is set and Neutron >> hearing and responding to DHCP requests and the instance is getting IP >> from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP >> address (ICMP/SSH is added allowed rule on default security group) >> >> >> Here is the little diagram of my system. >> [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] >> >> Can someone help to find what is missing. > >If this is your first attempt at setting up Neutron, you might want to >go through this: > > >http://docs.openstack.org/openstack-ops/content/network_troubleshooting.ht >ml > >Here's some old example of some `tcpdump` analysis[*] on different >interfaces: > > https://gist.github.com/kashyapc/7926517 > >In general, when dealing with Neutron, systematic debugging will help a >lot to narrow down the root cause. > >[*] https://gist.github.com/kashyapc/7926517 > >-- >/kashyap From marius at remote-lab.net Fri Jan 9 22:30:27 2015 From: marius at remote-lab.net (Marius Cornea) Date: Fri, 9 Jan 2015 23:30:27 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: > Hi Marius, > > Here are the outputs. Is it possible to reach you on phone so that I can > explain more than email. You can call me at 650 849 3915 or let me know > your number. > > #ip a > > [root at lspal117 network-scripts(keystone_admin)]# ip a > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: eno1: mtu 1500 qdisc mq state UP qlen > 1000 > link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff > inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 > valid_lft forever preferred_lft forever > inet6 fe80::da9d:67ff:fe29:c694/64 scope link > valid_lft forever preferred_lft forever > 3: eno2: mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff > 4: eno3: mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff > 5: eno4: mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff > 6: ens1f0: mtu 1500 qdisc mq state > DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff > 7: ens1f1: mtu 1500 qdisc mq state > DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff > 8: ens2f0: mtu 1500 qdisc mq state > DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff > 9: ens2f1: mtu 1500 qdisc mq state > DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff > 10: ovs-system: mtu 1500 qdisc noop state DOWN > link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff > 11: br-ex: mtu 1500 qdisc noqueue state > UNKNOWN > link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff > inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex > valid_lft forever preferred_lft forever > inet6 fe80::bc8b:24ff:fe03:a947/64 scope link > valid_lft forever preferred_lft forever > 12: br-int: mtu 1500 qdisc noop state DOWN > link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff > 16: br-tun: mtu 1500 qdisc noop state DOWN > link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff > 17: qbr63bd6704-47: mtu 1500 qdisc > noqueue state UP > link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff > inet6 fe80::3822:bcff:fe6a:b74f/64 scope link > valid_lft forever preferred_lft forever > 18: qvo63bd6704-47: mtu 1500 > qdisc pfifo_fast master ovs-system state UP qlen 1000 > link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff > 19: qvb63bd6704-47: mtu 1500 > qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 > link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff > 22: tap63bd6704-47: mtu 1500 qdisc > pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 > link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc16:3eff:fed9:5eba/64 scope link > valid_lft forever preferred_lft forever > > # ovs-vsctl show > > [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show > c5bcc161-86cd-4004-9729-c1ba05d28569 > Bridge br-ex > Port br-ex > Interface br-ex > type: internal > Port "qg-c3a1b534-36" > Interface "qg-c3a1b534-36" > type: internal > Bridge br-int > fail_mode: secure > Port patch-tun > Interface patch-tun > type: patch > options: {peer=patch-int} > Port "tape386c0cb-d8" > tag: 1 > Interface "tape386c0cb-d8" > type: internal > Port br-int > Interface br-int > type: internal > Port "qvo63bd6704-47" > tag: 1 > Interface "qvo63bd6704-47" > Port "tap44dd465f-d4" > tag: 4095 > Interface "tap44dd465f-d4" > type: internal > Port "qr-e0ac3c25-2b" > tag: 2 > Interface "qr-e0ac3c25-2b" > type: internal > Bridge br-tun > Port br-tun > Interface br-tun > type: internal > Port patch-int > Interface patch-int > type: patch > options: {peer=patch-tun} > ovs_version: ?2.1.3" > > # neutron net-list > [root at lspal117 network-scripts(keystone_admin)]# neutron net-list > > +--------------------------------------+---------+------------------------------------------------------+ > | id | name | subnets > | > > +--------------------------------------+---------+------------------------------------------------------+ > | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | > 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | > | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | > f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | > | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | > ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | > > +--------------------------------------+---------+------------------------------------------------------+ > > # neutron subnet-list > [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list > > +--------------------------------------+----------------+-----------------+----------------------------------------------------+ > | id | name | cidr > | allocation_pools | > > +--------------------------------------+----------------+-----------------+----------------------------------------------------+ > | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 > | {"start": "172.24.4.226", "end": "172.24.4.238"} | > | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 > | {"start": "10.0.0.2", "end": "10.0.0.254"} | > | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 > | {"start": "10.48.146.112", "end": "10.48.146.120"} | > > +--------------------------------------+----------------+-----------------+??????????????????????????+ > > #neutron router-list > [root at lspal117 network-scripts(keystone_admin)]# neutron router-list > > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | id | name | external_gateway_info > > > | distributed | ha | > > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": > "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, > "external_fixed_ips": [{"subnet_id": > "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | > False | False | > > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ > > In my system I have IP address for BR-ex and ENO1 (interface connecting > ), should I disable eno1 as I can ping both (br-ex and eno1) from my > network to reach to this host ? Probably its a dump question. > > Here are the outputs. > > br-ex: flags=4163 mtu 1500 > inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 > inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 > ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) > RX packets 10 bytes 864 (864.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 25 bytes 3767 (3.6 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > br-int: flags=4098 mtu 1500 > ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) > RX packets 135 bytes 7574 (7.3 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > br-tun: flags=4098 mtu 1500 > ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > eno1: flags=4163 mtu 1500 > inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 > inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 > ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) > RX packets 467319 bytes 48391354 (46.1 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 14794 bytes 5238733 (4.9 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 32 > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM > To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Hi Rushi, > > Can you provide the output of the following commands on your node ? > > # ip a > # ovs-vsctl show > # neutron net-list > # neutron subnet-list > # neutron router-list > > Please note that only the br-ex bridge requires an IP address, the > interface that's part of it shouldn't have one assigned. Also the floating > IP addresses will be used for DNAT on the tenant router. You can check the > documentation here[1] that describes the use of floating IPs. > > You can also check the upstream documentation[2] on how to create the > networks. > > [1] > https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP > [2] > http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html > > > Tnx, > Marius > > On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: > >> Hi Support, >> >> I have a problem that a launched instance from openstack cannot >> connect to SSH or PING >> >> First of all I have dump question whether my system should be NOVA >> network or Neutron network. Well to keep everyone on the same page. Here is >> my history. >> >> >> 1. I did install RDO (allinone host) using the bellow steps >> https://openstack.redhat.com/Quickstart >> 2. Then I have used the following steps for floating IP >> https://openstack.redhat.com/Floating_IP_range. >> >> My situtation is as follows. >> * Floating IP address assignment: >> I have assigned a floating IP , I did follow this steps. >> https://openstack.redhat.com/Floating_IP_range >> >> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it >> is eno1 name)is on the same bridge as the compute host >> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >> 10.48.146.112 >> >> * DHCP configuration: Yes, DHCP configuration is set and Neutron >> hearing and responding to DHCP >> requests and the instance is getting IP from 10.48.146.113 (next hop) >> however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >> rule on default security group) >> >> Here is the little diagram of my system. >> >> Can someone help to find what is missing. >> >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: From rushi.ns at sap.com Fri Jan 9 22:31:46 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 22:31:46 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: <20150109220420.GA23907@tesla.redhat.com> Message-ID: Hi All I need is the folowing. 1) my openstack is on : 10.48.146.77 (my corporate network) 2) I need a VM to be on the same network 10.48.146.112(available from my DHCP or manual) Can someone help me how to do the above as I don?t want to confuse with external-ip ..all I need is a VM spin with my corporate network and how can I accomplish that? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race On 1/9/15, 2:17 PM, "Ns, Rushi" wrote: >Well, I agree and admit that I shouldn?t call community as SUPPORT. My >sincere apologies for that. > >Well going through I did all kinds of tests that are part of network >neutron and read all most all the links from redhat relates the links you >provided already, however my issues seems to be simple but not getting to >solve as I was working on this for last 10 days and finally thought of >putting into rdo-list. > >Yes, I agree that I am getting familiar with NEUTRON only . For now my >simple issue is that > >I have my openstack interface eno1 on 10.48.146.77 and br-ex is : >10.48.146.112 and the VM instance is 10.48.146.113 however I cannot ssh >/PING that 10.48.146.113 address ? > >Any ideas. > >Here are the commands and outputs. > > >#ip a > >[root at lspal117 network-scripts(keystone_admin)]# ip a >1: lo: mtu 65536 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever >2: eno1: mtu 1500 qdisc mq state UP qlen >1000 > link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff > inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 > valid_lft forever preferred_lft forever > inet6 fe80::da9d:67ff:fe29:c694/64 scope link > valid_lft forever preferred_lft forever >3: eno2: mtu 1500 qdisc mq state DOWN >qlen 1000 > link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >4: eno3: mtu 1500 qdisc mq state DOWN >qlen 1000 > link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >5: eno4: mtu 1500 qdisc mq state DOWN >qlen 1000 > link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >6: ens1f0: mtu 1500 qdisc mq state >DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >7: ens1f1: mtu 1500 qdisc mq state >DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >8: ens2f0: mtu 1500 qdisc mq state >DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >9: ens2f1: mtu 1500 qdisc mq state >DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >10: ovs-system: mtu 1500 qdisc noop state DOWN > link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >11: br-ex: mtu 1500 qdisc noqueue state >UNKNOWN > link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff > inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex > valid_lft forever preferred_lft forever > inet6 fe80::bc8b:24ff:fe03:a947/64 scope link > valid_lft forever preferred_lft forever >12: br-int: mtu 1500 qdisc noop state DOWN > link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >16: br-tun: mtu 1500 qdisc noop state DOWN > link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >17: qbr63bd6704-47: mtu 1500 qdisc >noqueue state UP > link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff > inet6 fe80::3822:bcff:fe6a:b74f/64 scope link > valid_lft forever preferred_lft forever >18: qvo63bd6704-47: mtu 1500 >qdisc pfifo_fast master ovs-system state UP qlen 1000 > link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >19: qvb63bd6704-47: mtu 1500 >qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 > link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >22: tap63bd6704-47: mtu 1500 qdisc >pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 > link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc16:3eff:fed9:5eba/64 scope link > valid_lft forever preferred_lft forever > > ># ovs-vsctl show > >[root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >c5bcc161-86cd-4004-9729-c1ba05d28569 > Bridge br-ex > Port br-ex > Interface br-ex > type: internal > Port "qg-c3a1b534-36" > Interface "qg-c3a1b534-36" > type: internal > Bridge br-int > fail_mode: secure > Port patch-tun > Interface patch-tun > type: patch > options: {peer=patch-int} > Port "tape386c0cb-d8" > tag: 1 > Interface "tape386c0cb-d8" > type: internal > Port br-int > Interface br-int > type: internal > Port "qvo63bd6704-47" > tag: 1 > Interface "qvo63bd6704-47" > Port "tap44dd465f-d4" > tag: 4095 > Interface "tap44dd465f-d4" > type: internal > Port "qr-e0ac3c25-2b" > tag: 2 > Interface "qr-e0ac3c25-2b" > type: internal > Bridge br-tun > Port br-tun > Interface br-tun > type: internal > Port patch-int > Interface patch-int > type: patch > options: {peer=patch-tun} > ovs_version: ?2.1.3" > > ># neutron net-list >[root at lspal117 network-scripts(keystone_admin)]# neutron net-list >+--------------------------------------+---------+------------------------ >- >-----------------------------+ >| id | name | subnets > | >+--------------------------------------+---------+------------------------ >- >-----------------------------+ >| 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >| d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >| 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >+--------------------------------------+---------+------------------------ >- >-----------------------------+ > > ># neutron subnet-list >[root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list >+--------------------------------------+----------------+----------------- >+ >----------------------------------------------------+ >| id | name | cidr >| allocation_pools | >+--------------------------------------+----------------+----------------- >+ >----------------------------------------------------+ >| 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 >| {"start": "172.24.4.226", "end": "172.24.4.238"} | >| f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 >| {"start": "10.0.0.2", "end": "10.0.0.254"} | >| ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 >| {"start": "10.48.146.112", "end": "10.48.146.120"} | >+--------------------------------------+----------------+----------------- >+ >??????????????????????????+ > > >#neutron router-list >[root at lspal117 network-scripts(keystone_admin)]# neutron router-list >+--------------------------------------+---------+------------------------ >- >-------------------------------------------------------------------------- >- >-------------------------------------------------------------------------- >- >-----------+-------------+-------+ >| id | name | external_gateway_info > > > | distributed | ha | >+--------------------------------------+---------+------------------------ >- >-------------------------------------------------------------------------- >- >-------------------------------------------------------------------------- >- >-----------+-------------+-------+ >| d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >"5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >"external_fixed_ips": [{"subnet_id": >"79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >False | False | >+--------------------------------------+---------+------------------------ >- >-------------------------------------------------------------------------- >- >-------------------------------------------------------------------------- >- >-----------+-------------+???+ > > >In my system I have IP address for BR-ex and ENO1 (interface connecting ), >should I disable eno1 as I can ping both (br-ex and eno1) from my network >to reach to this host ? Probably its a dump question. > >Here are the outputs. > >br-ex: flags=4163 mtu 1500 > inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 > inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 > ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) > RX packets 10 bytes 864 (864.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 25 bytes 3767 (3.6 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > >br-int: flags=4098 mtu 1500 > ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) > RX packets 135 bytes 7574 (7.3 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > >br-tun: flags=4098 mtu 1500 > ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > >eno1: flags=4163 mtu 1500 > inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 > inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 > ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) > RX packets 467319 bytes 48391354 (46.1 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 14794 bytes 5238733 (4.9 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 32 > > > > > >Best Regards, > > > >Rushi. > >Success is not a matter of being the best & winning the race. Success is a >matter of handling the worst & finishing the race > > > > > > > >On 1/9/15, 2:04 PM, "Kashyap Chamarthy" wrote: > >>On Fri, Jan 09, 2015 at 09:22:04PM +0000, Ns, Rushi wrote: >>> Hi Support, >> >>[A gentle note: addresing community mailing lists as "Support" is not a >>nice netiquette.] >> >>That said, a couple of comments in line. >> >>> I have a problem that a launched instance from openstack cannot >>>connect to SSH or PING >>> >>> First of all I have dump question whether my system should be NOVA >>> network or Neutron network. >> >>If you mean, you're not sure whether to choose Nova or Neutron >>networking, it really depends what you're trying to do. Just to note, >>Nova networking will be deprecated in future in favor of Neutron, so >>getting familiar with Neutron will be useful. >> >>> Well to keep everyone on the same page. Here is my history. >>> >>> >>> 1. I did install RDO (allinone host) using the bellow steps >>> https://openstack.redhat.com/Quickstart 2. Then I have used the >>> following steps for floating IP >>> https://openstack.redhat.com/Floating_IP_range. >>> >>> My situtation is as follows. * Floating IP address assignment: I have >>> assigned a floating IP , I did follow this steps. >>> https://openstack.redhat.com/Floating_IP_range >>> >>> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it >>> is eno1 name)is on the same bridge as the compute host Yes, ethernet >>> device on 10.48.146.78 address and br-ex interface on 10.48.146.112 >>> >>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>> hearing and responding to DHCP requests and the instance is getting IP >>> from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP >>> address (ICMP/SSH is added allowed rule on default security group) >>> >>> >>> Here is the little diagram of my system. >>> [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] >>> >>> Can someone help to find what is missing. >> >>If this is your first attempt at setting up Neutron, you might want to >>go through this: >> >> >>http://docs.openstack.org/openstack-ops/content/network_troubleshooting.h >>t >>ml >> >>Here's some old example of some `tcpdump` analysis[*] on different >>interfaces: >> >> https://gist.github.com/kashyapc/7926517 >> >>In general, when dealing with Neutron, systematic debugging will help a >>lot to narrow down the root cause. >> >>[*] https://gist.github.com/kashyapc/7926517 >> >>-- >>/kashyap > From vedsarkushwaha at gmail.com Fri Jan 9 22:46:52 2015 From: vedsarkushwaha at gmail.com (Vedsar Kushwaha) Date: Sat, 10 Jan 2015 04:16:52 +0530 Subject: [Rdo-list] error with glance during installation phase Message-ID: I'm getting following error during openstack stackpack all in one june installation. ....... ....... Applying 10.0.3.15_provision_glance 10.0.3.15_swift.pp: [ DONE ] 10.0.3.15_provision_glance: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 10.0.3.15_provision_glance Error: Execution of '/usr/bin/glance --os-tenant-name services --os-username glance --os-password 4c010f3a88c04c80 --os-region-name RegionOne --os-auth-url http://10.0.3.15:35357/v2.0/ image-create --name=cirros --is-public=Yes --container-format=bare --disk-format=qcow2 --copy-from= http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img' returned 1: You will find full trace in log /var/tmp/packstack/20150110-035555-RQVs7N/manifests/10.0.3.15_provision_glance.log Please check log file /var/tmp/packstack/20150110-035555-RQVs7N/openstack-setup.log for more information please help.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.haller at alcatel-lucent.com Fri Jan 9 22:52:15 2015 From: john.haller at alcatel-lucent.com (Haller, John H (John)) Date: Fri, 9 Jan 2015 22:52:15 +0000 Subject: [Rdo-list] error with glance during installation phase In-Reply-To: References: Message-ID: <7C1824C61EE769448FCE74CD83F0CB4F58218C1E@US70TWXCHMBA11.zam.alcatel-lucent.com> Are you behind a firewall and using a proxy server? If so, Glance does not allow downloading the cirros image through a proxy. A recent change to RDO allow one to download the cirros image locally before starting packstack, and use a local file or local URL per a configuration in packstack. Alternatively, you can turn off the demo project in the packstack configuration, which is what pulls in the cirros image. Regards, John Haller From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Vedsar Kushwaha Sent: Friday, January 09, 2015 4:47 PM To: rdo-list at redhat.com Subject: [Rdo-list] error with glance during installation phase I'm getting following error during openstack stackpack all in one june installation. ....... ....... Applying 10.0.3.15_provision_glance 10.0.3.15_swift.pp: [ DONE ] 10.0.3.15_provision_glance: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 10.0.3.15_provision_glance Error: Execution of '/usr/bin/glance --os-tenant-name services --os-username glance --os-password 4c010f3a88c04c80 --os-region-name RegionOne --os-auth-url http://10.0.3.15:35357/v2.0/ image-create --name=cirros --is-public=Yes --container-format=bare --disk-format=qcow2 --copy-from=http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img' returned 1: You will find full trace in log /var/tmp/packstack/20150110-035555-RQVs7N/manifests/10.0.3.15_provision_glance.log Please check log file /var/tmp/packstack/20150110-035555-RQVs7N/openstack-setup.log for more information please help.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Fri Jan 9 22:58:25 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 22:58:25 +0000 Subject: [Rdo-list] error with glance during installation phase In-Reply-To: <7C1824C61EE769448FCE74CD83F0CB4F58218C1E@US70TWXCHMBA11.zam.alcatel-lucent.com> References: <7C1824C61EE769448FCE74CD83F0CB4F58218C1E@US70TWXCHMBA11.zam.alcatel-lucent.com> Message-ID: Yes, its true that you can?t get the image using proxy. I had the same error after getting into openstack dashboard I manually added images by downloading to my host. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , "John H (John)" > Date: Friday, January 9, 2015 at 2:52 PM To: Vedsar Kushwaha >, "rdo-list at redhat.com" > Subject: Re: [Rdo-list] error with glance during installation phase Are you behind a firewall and using a proxy server? If so, Glance does not allow downloading the cirros image through a proxy. A recent change to RDO allow one to download the cirros image locally before starting packstack, and use a local file or local URL per a configuration in packstack. Alternatively, you can turn off the demo project in the packstack configuration, which is what pulls in the cirros image. Regards, John Haller From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Vedsar Kushwaha Sent: Friday, January 09, 2015 4:47 PM To: rdo-list at redhat.com Subject: [Rdo-list] error with glance during installation phase I'm getting following error during openstack stackpack all in one june installation. ....... ....... Applying 10.0.3.15_provision_glance 10.0.3.15_swift.pp: [ DONE ] 10.0.3.15_provision_glance: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 10.0.3.15_provision_glance Error: Execution of '/usr/bin/glance --os-tenant-name services --os-username glance --os-password 4c010f3a88c04c80 --os-region-name RegionOne --os-auth-url http://10.0.3.15:35357/v2.0/ image-create --name=cirros --is-public=Yes --container-format=bare --disk-format=qcow2 --copy-from=http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img' returned 1: You will find full trace in log /var/tmp/packstack/20150110-035555-RQVs7N/manifests/10.0.3.15_provision_glance.log Please check log file /var/tmp/packstack/20150110-035555-RQVs7N/openstack-setup.log for more information please help.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Fri Jan 9 23:20:18 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 23:20:18 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: From rushi.ns at sap.com Fri Jan 9 23:22:50 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 23:22:50 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Forgot to add, I can ping the router ip: 10.48.146.113 but not the instance IP; 10.48.146.115 ? [root at lspal117 ~(keystone_admin)]# ping 10.48.146.113 PING 10.48.146.113 (10.48.146.113) 56(84) bytes of data. 64 bytes from 10.48.146.113: icmp_seq=1 ttl=64 time=0.951 ms 64 bytes from 10.48.146.113: icmp_seq=2 ttl=64 time=0.023 ms Also I cannot associate the floating IP to instance as there is no port available. [cid:B1C70DA2-C38D-480D-BB8E-C09DCC0E16C9] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:20 PM To: Marius Cornea >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: B1C70DA2-C38D-480D-BB8E-C09DCC0E16C9.png Type: image/png Size: 41626 bytes Desc: B1C70DA2-C38D-480D-BB8E-C09DCC0E16C9.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: From marius at remote-lab.net Fri Jan 9 23:48:43 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 00:48:43 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: > Hi Marius, > > I did this first and now can see the BR-ex is the same IP as my eno1 > interface , you are right I lost first while doing the first command(ip > addr del 10.48.146.77/24 dev eno1) and then conneting to console I did > the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP > address of br-ex to 10.48.146.77) > > ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 > > Then after I removed all the routers, networks and interfaces from > openstack and ran the following 4 commands. > > 1) source /root/keystonerc_admin > 2) neutron net-create public --router:external=True > 3) neutron subnet-create public 10.48.146.0/24 --name vlan > --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 > --gateway 10.48.146.1 > 4) neutron router-create router1 > 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 > 1605ac0b-4f59-473d-b20f-911c3401dc2c > 6) neutron floatingip-create public > > The above command generated a floating IP 10.48.146.115 > > Then I spin up a new instance and it got IP assigned automatically > 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? > > Here are the screenshots > > > > > [root at lspal117 ~(keystone_admin)]# neutron net-list > > +--------------------------------------+--------+-----------------------------------------------------+ > | id | name | subnets > | > > +--------------------------------------+--------+-----------------------------------------------------+ > | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | > 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | > > +--------------------------------------+--------+??????????????????????????+ > > [root at lspal117 ~(keystone_admin)]# neutron subnet-list > > +--------------------------------------+------+----------------+----------------------------------------------------+ > | id | name | cidr | > allocation_pools | > > +--------------------------------------+------+----------------+----------------------------------------------------+ > | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | > {"start": "10.48.146.113", "end": "10.48.146.130"} | > > +--------------------------------------+------+----------------+----------------------------------------------------+ > > [root at lspal117 ~(keystone_admin)]# neutron router-list > > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | id | name | external_gateway_info > > > | distributed | ha | > > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": > "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, > "external_fixed_ips": [{"subnet_id": > "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | > False | False | > > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > > Any ideas what is going wrong, I still can?t ping or ssh to that IP > address and its not listening anywhere ? > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM > To: SAP SAP , rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > As Kashyap kindly suggested we're not a support line and information > here should be available for all the community members. First, I don't see > how you can ping the br-ex IP address from an external network since it > doesn't contain any physical interface. Make sure that 10.48.146.112 isn't > used by other host on you network segment. You can do the following to > remove the ip address from the physical interface and add it to the br-ex > bridge. Please make sure that you've got console access to the server > before doing this as you may lose connectivity. > > # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 > > You should then follow the documentation[1] to recreate the > public/tenant networks and router. In your > case FLOATING_IP_START, FLOATING_IP_END should be part of the > 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of > the 10.48.146.200 - 10.48.146.210 range to your Openstack > routers/instances, then FLOATING_IP_START=10.48.146.200 and > FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to > what 'ip r | grep default | awk {'print $3'}' outputs > and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. > > Note that the instance will get an IP address of the tenant network. By > assigning a floating IP you will be able to access it through an IP address > from your physical network segment. > > [1] > http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html > > > > On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: > >> Hi Marius, >> >> Here are the outputs. Is it possible to reach you on phone so that I >> can explain more than email. You can call me at 650 849 3915 or let me >> know your number. >> >> #ip a >> >> [root at lspal117 network-scripts(keystone_admin)]# ip a >> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> inet 127.0.0.1/8 scope host lo >> valid_lft forever preferred_lft forever >> inet6 ::1/128 scope host >> valid_lft forever preferred_lft forever >> 2: eno1: mtu 1500 qdisc mq state UP >> qlen 1000 >> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >> valid_lft forever preferred_lft forever >> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >> valid_lft forever preferred_lft forever >> 3: eno2: mtu 1500 qdisc mq state DOWN >> qlen 1000 >> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >> 4: eno3: mtu 1500 qdisc mq state DOWN >> qlen 1000 >> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >> 5: eno4: mtu 1500 qdisc mq state DOWN >> qlen 1000 >> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >> 6: ens1f0: mtu 1500 qdisc mq state >> DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >> 7: ens1f1: mtu 1500 qdisc mq state >> DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >> 8: ens2f0: mtu 1500 qdisc mq state >> DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >> 9: ens2f1: mtu 1500 qdisc mq state >> DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >> 10: ovs-system: mtu 1500 qdisc noop state DOWN >> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >> 11: br-ex: mtu 1500 qdisc noqueue state >> UNKNOWN >> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >> valid_lft forever preferred_lft forever >> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >> valid_lft forever preferred_lft forever >> 12: br-int: mtu 1500 qdisc noop state DOWN >> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >> 16: br-tun: mtu 1500 qdisc noop state DOWN >> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >> 17: qbr63bd6704-47: mtu 1500 qdisc >> noqueue state UP >> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >> valid_lft forever preferred_lft forever >> 18: qvo63bd6704-47: mtu 1500 >> qdisc pfifo_fast master ovs-system state UP qlen 1000 >> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >> 19: qvb63bd6704-47: mtu 1500 >> qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >> 22: tap63bd6704-47: mtu 1500 qdisc >> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >> valid_lft forever preferred_lft forever >> >> # ovs-vsctl show >> >> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >> c5bcc161-86cd-4004-9729-c1ba05d28569 >> Bridge br-ex >> Port br-ex >> Interface br-ex >> type: internal >> Port "qg-c3a1b534-36" >> Interface "qg-c3a1b534-36" >> type: internal >> Bridge br-int >> fail_mode: secure >> Port patch-tun >> Interface patch-tun >> type: patch >> options: {peer=patch-int} >> Port "tape386c0cb-d8" >> tag: 1 >> Interface "tape386c0cb-d8" >> type: internal >> Port br-int >> Interface br-int >> type: internal >> Port "qvo63bd6704-47" >> tag: 1 >> Interface "qvo63bd6704-47" >> Port "tap44dd465f-d4" >> tag: 4095 >> Interface "tap44dd465f-d4" >> type: internal >> Port "qr-e0ac3c25-2b" >> tag: 2 >> Interface "qr-e0ac3c25-2b" >> type: internal >> Bridge br-tun >> Port br-tun >> Interface br-tun >> type: internal >> Port patch-int >> Interface patch-int >> type: patch >> options: {peer=patch-tun} >> ovs_version: ?2.1.3" >> >> # neutron net-list >> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >> >> +--------------------------------------+---------+------------------------------------------------------+ >> | id | name | subnets >> | >> >> +--------------------------------------+---------+------------------------------------------------------+ >> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >> >> +--------------------------------------+---------+------------------------------------------------------+ >> >> # neutron subnet-list >> [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list >> >> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >> | id | name | cidr >> | allocation_pools | >> >> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 >> | {"start": "172.24.4.226", "end": "172.24.4.238"} | >> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 >> | {"start": "10.0.0.2", "end": "10.0.0.254"} | >> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 >> | {"start": "10.48.146.112", "end": "10.48.146.120"} | >> >> +--------------------------------------+----------------+-----------------+??????????????????????????+ >> >> #neutron router-list >> [root at lspal117 network-scripts(keystone_admin)]# neutron router-list >> >> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> | id | name | external_gateway_info >> >> >> | distributed | ha | >> >> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >> "external_fixed_ips": [{"subnet_id": >> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >> False | False | >> >> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >> >> In my system I have IP address for BR-ex and ENO1 (interface connecting >> ), should I disable eno1 as I can ping both (br-ex and eno1) from my >> network to reach to this host ? Probably its a dump question. >> >> Here are the outputs. >> >> br-ex: flags=4163 mtu 1500 >> inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 >> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 >> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >> RX packets 10 bytes 864 (864.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 25 bytes 3767 (3.6 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> br-int: flags=4098 mtu 1500 >> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >> RX packets 135 bytes 7574 (7.3 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> br-tun: flags=4098 mtu 1500 >> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >> RX packets 0 bytes 0 (0.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> eno1: flags=4163 mtu 1500 >> inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 >> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 >> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >> RX packets 467319 bytes 48391354 (46.1 MiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 14794 bytes 5238733 (4.9 MiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> device interrupt 32 >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 1:46 PM >> To: SAP SAP >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Hi Rushi, >> >> Can you provide the output of the following commands on your node ? >> >> # ip a >> # ovs-vsctl show >> # neutron net-list >> # neutron subnet-list >> # neutron router-list >> >> Please note that only the br-ex bridge requires an IP address, the >> interface that's part of it shouldn't have one assigned. Also the floating >> IP addresses will be used for DNAT on the tenant router. You can check the >> documentation here[1] that describes the use of floating IPs. >> >> You can also check the upstream documentation[2] on how to create the >> networks. >> >> [1] >> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >> [2] >> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >> >> >> Tnx, >> Marius >> >> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: >> >>> Hi Support, >>> >>> I have a problem that a launched instance from openstack cannot >>> connect to SSH or PING >>> >>> First of all I have dump question whether my system should be NOVA >>> network or Neutron network. Well to keep everyone on the same page. Here is >>> my history. >>> >>> >>> 1. I did install RDO (allinone host) using the bellow steps >>> https://openstack.redhat.com/Quickstart >>> 2. Then I have used the following steps for floating IP >>> https://openstack.redhat.com/Floating_IP_range. >>> >>> My situtation is as follows. >>> * Floating IP address assignment: >>> I have assigned a floating IP , I did follow this steps. >>> https://openstack.redhat.com/Floating_IP_range >>> >>> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it >>> is eno1 name)is on the same bridge as the compute host >>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >>> 10.48.146.112 >>> >>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>> hearing and responding to DHCP >>> requests and the instance is getting IP from 10.48.146.113 (next hop) >>> however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>> rule on default security group) >>> >>> Here is the little diagram of my system. >>> >>> Can someone help to find what is missing. >>> >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: From rushi.ns at sap.com Fri Jan 9 23:55:35 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 23:55:35 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: From rushi.ns at sap.com Fri Jan 9 23:58:03 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 9 Jan 2015 23:58:03 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: From marius at remote-lab.net Sat Jan 10 00:02:46 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 01:02:46 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-tenant-network.html The tenant subnet should be different than the external network so you should try something like: neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 Attach the network to the existing router that has connectivity to the external network: neutron router-interface-add router1 demo-subnet Boot the instance with the demo-net network and then assign a floating IP. On Sat, Jan 10, 2015 at 12:58 AM, Ns, Rushi wrote: > Ok I did the folowing steps for tenant. > > 1) neutron net-create demo-net > 2) neutron subnet-create demo-net --name demo-subnet --gateway > 10.48.146.1 10.48.146.0/24 > 3) neutron router-create demo-router > 4) neutron router-interface-add demo-router demo-subnet > > Anything left .? > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM > To: Marius Cornea > > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Hi Marius, > > Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide > the comamnds or link to create tenant network, subjet and attach to router > ? > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Can you ping 10.48.146.113 from your network? You also need to create a > tenant network, subnet and attach it to the router. Boot the instance with > the tenant network attached and then assign it the floating IP. > > > On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: > >> Hi Marius, >> >> I did this first and now can see the BR-ex is the same IP as my eno1 >> interface , you are right I lost first while doing the first command(ip >> addr del 10.48.146.77/24 dev eno1) and then conneting to console I did >> the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP >> address of br-ex to 10.48.146.77) >> >> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >> >> Then after I removed all the routers, networks and interfaces from >> openstack and ran the following 4 commands. >> >> 1) source /root/keystonerc_admin >> 2) neutron net-create public --router:external=True >> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >> --gateway 10.48.146.1 >> 4) neutron router-create router1 >> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >> 1605ac0b-4f59-473d-b20f-911c3401dc2c >> 6) neutron floatingip-create public >> >> The above command generated a floating IP 10.48.146.115 >> >> Then I spin up a new instance and it got IP assigned automatically >> 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? >> >> Here are the screenshots >> >> >> >> >> [root at lspal117 ~(keystone_admin)]# neutron net-list >> >> +--------------------------------------+--------+-----------------------------------------------------+ >> | id | name | subnets >> | >> >> +--------------------------------------+--------+-----------------------------------------------------+ >> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >> >> +--------------------------------------+--------+??????????????????????????+ >> >> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >> >> +--------------------------------------+------+----------------+----------------------------------------------------+ >> | id | name | cidr | >> allocation_pools | >> >> +--------------------------------------+------+----------------+----------------------------------------------------+ >> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >> {"start": "10.48.146.113", "end": "10.48.146.130"} | >> >> +--------------------------------------+------+----------------+----------------------------------------------------+ >> >> [root at lspal117 ~(keystone_admin)]# neutron router-list >> >> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> | id | name | >> external_gateway_info >> >> | distributed | ha | >> >> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >> "external_fixed_ips": [{"subnet_id": >> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >> False | False | >> >> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> >> Any ideas what is going wrong, I still can?t ping or ssh to that IP >> address and its not listening anywhere ? >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 2:30 PM >> To: SAP SAP , rdo-list >> >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> As Kashyap kindly suggested we're not a support line and information >> here should be available for all the community members. First, I don't see >> how you can ping the br-ex IP address from an external network since it >> doesn't contain any physical interface. Make sure that 10.48.146.112 isn't >> used by other host on you network segment. You can do the following to >> remove the ip address from the physical interface and add it to the br-ex >> bridge. Please make sure that you've got console access to the server >> before doing this as you may lose connectivity. >> >> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >> >> You should then follow the documentation[1] to recreate the >> public/tenant networks and router. In your >> case FLOATING_IP_START, FLOATING_IP_END should be part of the >> 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of >> the 10.48.146.200 - 10.48.146.210 range to your Openstack >> routers/instances, then FLOATING_IP_START=10.48.146.200 and >> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >> what 'ip r | grep default | awk {'print $3'}' outputs >> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >> >> Note that the instance will get an IP address of the tenant network. By >> assigning a floating IP you will be able to access it through an IP address >> from your physical network segment. >> >> [1] >> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >> >> >> >> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: >> >>> Hi Marius, >>> >>> Here are the outputs. Is it possible to reach you on phone so that I >>> can explain more than email. You can call me at 650 849 3915 or let me >>> know your number. >>> >>> #ip a >>> >>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>> inet 127.0.0.1/8 scope host lo >>> valid_lft forever preferred_lft forever >>> inet6 ::1/128 scope host >>> valid_lft forever preferred_lft forever >>> 2: eno1: mtu 1500 qdisc mq state UP >>> qlen 1000 >>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>> valid_lft forever preferred_lft forever >>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>> valid_lft forever preferred_lft forever >>> 3: eno2: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>> 4: eno3: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>> 5: eno4: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>> 6: ens1f0: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>> 7: ens1f1: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>> 8: ens2f0: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>> 9: ens2f1: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>> 10: ovs-system: mtu 1500 qdisc noop state DOWN >>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>> 11: br-ex: mtu 1500 qdisc noqueue >>> state UNKNOWN >>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>> valid_lft forever preferred_lft forever >>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>> valid_lft forever preferred_lft forever >>> 12: br-int: mtu 1500 qdisc noop state DOWN >>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>> 17: qbr63bd6704-47: mtu 1500 qdisc >>> noqueue state UP >>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>> valid_lft forever preferred_lft forever >>> 18: qvo63bd6704-47: mtu 1500 >>> qdisc pfifo_fast master ovs-system state UP qlen 1000 >>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>> 19: qvb63bd6704-47: mtu 1500 >>> qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>> 22: tap63bd6704-47: mtu 1500 qdisc >>> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>> valid_lft forever preferred_lft forever >>> >>> # ovs-vsctl show >>> >>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>> Bridge br-ex >>> Port br-ex >>> Interface br-ex >>> type: internal >>> Port "qg-c3a1b534-36" >>> Interface "qg-c3a1b534-36" >>> type: internal >>> Bridge br-int >>> fail_mode: secure >>> Port patch-tun >>> Interface patch-tun >>> type: patch >>> options: {peer=patch-int} >>> Port "tape386c0cb-d8" >>> tag: 1 >>> Interface "tape386c0cb-d8" >>> type: internal >>> Port br-int >>> Interface br-int >>> type: internal >>> Port "qvo63bd6704-47" >>> tag: 1 >>> Interface "qvo63bd6704-47" >>> Port "tap44dd465f-d4" >>> tag: 4095 >>> Interface "tap44dd465f-d4" >>> type: internal >>> Port "qr-e0ac3c25-2b" >>> tag: 2 >>> Interface "qr-e0ac3c25-2b" >>> type: internal >>> Bridge br-tun >>> Port br-tun >>> Interface br-tun >>> type: internal >>> Port patch-int >>> Interface patch-int >>> type: patch >>> options: {peer=patch-tun} >>> ovs_version: ?2.1.3" >>> >>> # neutron net-list >>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>> >>> +--------------------------------------+---------+------------------------------------------------------+ >>> | id | name | subnets >>> | >>> >>> +--------------------------------------+---------+------------------------------------------------------+ >>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>> >>> +--------------------------------------+---------+------------------------------------------------------+ >>> >>> # neutron subnet-list >>> [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list >>> >>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>> | id | name | cidr >>> | allocation_pools | >>> >>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | >>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 >>> | {"start": "10.0.0.2", "end": "10.0.0.254"} | >>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 >>> | {"start": "10.48.146.112", "end": "10.48.146.120"} | >>> >>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>> >>> #neutron router-list >>> [root at lspal117 network-scripts(keystone_admin)]# neutron router-list >>> >>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>> | id | name | external_gateway_info >>> >>> >>> | distributed | ha | >>> >>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>> "external_fixed_ips": [{"subnet_id": >>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>> False | False | >>> >>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>> >>> In my system I have IP address for BR-ex and ENO1 (interface >>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>> from my network to reach to this host ? Probably its a dump question. >>> >>> Here are the outputs. >>> >>> br-ex: flags=4163 mtu 1500 >>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>> 10.48.146.255 >>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 >>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>> RX packets 10 bytes 864 (864.0 B) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 25 bytes 3767 (3.6 KiB) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> br-int: flags=4098 mtu 1500 >>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>> RX packets 135 bytes 7574 (7.3 KiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 0 bytes 0 (0.0 B) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> br-tun: flags=4098 mtu 1500 >>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>> RX packets 0 bytes 0 (0.0 B) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 0 bytes 0 (0.0 B) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> eno1: flags=4163 mtu 1500 >>> inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 >>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>> 0x20 >>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>> RX packets 467319 bytes 48391354 (46.1 MiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 14794 bytes 5238733 (4.9 MiB) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> device interrupt 32 >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 1:46 PM >>> To: SAP SAP >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Hi Rushi, >>> >>> Can you provide the output of the following commands on your node ? >>> >>> # ip a >>> # ovs-vsctl show >>> # neutron net-list >>> # neutron subnet-list >>> # neutron router-list >>> >>> Please note that only the br-ex bridge requires an IP address, the >>> interface that's part of it shouldn't have one assigned. Also the floating >>> IP addresses will be used for DNAT on the tenant router. You can check the >>> documentation here[1] that describes the use of floating IPs. >>> >>> You can also check the upstream documentation[2] on how to create the >>> networks. >>> >>> [1] >>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>> [2] >>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>> >>> >>> Tnx, >>> Marius >>> >>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: >>> >>>> Hi Support, >>>> >>>> I have a problem that a launched instance from openstack cannot >>>> connect to SSH or PING >>>> >>>> First of all I have dump question whether my system should be NOVA >>>> network or Neutron network. Well to keep everyone on the same page. Here is >>>> my history. >>>> >>>> >>>> 1. I did install RDO (allinone host) using the bellow steps >>>> https://openstack.redhat.com/Quickstart >>>> 2. Then I have used the following steps for floating IP >>>> https://openstack.redhat.com/Floating_IP_range. >>>> >>>> My situtation is as follows. >>>> * Floating IP address assignment: >>>> I have assigned a floating IP , I did follow this steps. >>>> https://openstack.redhat.com/Floating_IP_range >>>> >>>> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 >>>> it is eno1 name)is on the same bridge as the compute host >>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >>>> 10.48.146.112 >>>> >>>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>>> hearing and responding to DHCP >>>> requests and the instance is getting IP from 10.48.146.113 (next hop) >>>> however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>> rule on default security group) >>>> >>>> Here is the little diagram of my system. >>>> >>>> Can someone help to find what is missing. >>>> >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> _______________________________________________ >>>> Rdo-list mailing list >>>> Rdo-list at redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 00:03:43 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 00:03:43 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: From marius at remote-lab.net Sat Jan 10 00:06:58 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 01:06:58 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: > I can?t run this command > > > $ neutron router-gateway-set demo-router ext-net > > Its getting error (ext-net not found) ? What is the ext-net in this case > ? > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM > > To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Ok I did the folowing steps for tenant. > > 1) neutron net-create demo-net > 2) neutron subnet-create demo-net --name demo-subnet --gateway > 10.48.146.1 10.48.146.0/24 > 3) neutron router-create demo-router > 4) neutron router-interface-add demo-router demo-subnet > > Anything left .? > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM > To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Hi Marius, > > Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide > the comamnds or link to create tenant network, subjet and attach to router > ? > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Can you ping 10.48.146.113 from your network? You also need to create a > tenant network, subnet and attach it to the router. Boot the instance with > the tenant network attached and then assign it the floating IP. > > > On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: > >> Hi Marius, >> >> I did this first and now can see the BR-ex is the same IP as my eno1 >> interface , you are right I lost first while doing the first command(ip >> addr del 10.48.146.77/24 dev eno1) and then conneting to console I did >> the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP >> address of br-ex to 10.48.146.77) >> >> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >> >> Then after I removed all the routers, networks and interfaces from >> openstack and ran the following 4 commands. >> >> 1) source /root/keystonerc_admin >> 2) neutron net-create public --router:external=True >> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >> --gateway 10.48.146.1 >> 4) neutron router-create router1 >> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >> 1605ac0b-4f59-473d-b20f-911c3401dc2c >> 6) neutron floatingip-create public >> >> The above command generated a floating IP 10.48.146.115 >> >> Then I spin up a new instance and it got IP assigned automatically >> 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? >> >> Here are the screenshots >> >> >> >> >> [root at lspal117 ~(keystone_admin)]# neutron net-list >> >> +--------------------------------------+--------+-----------------------------------------------------+ >> | id | name | subnets >> | >> >> +--------------------------------------+--------+-----------------------------------------------------+ >> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >> >> +--------------------------------------+--------+??????????????????????????+ >> >> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >> >> +--------------------------------------+------+----------------+----------------------------------------------------+ >> | id | name | cidr | >> allocation_pools | >> >> +--------------------------------------+------+----------------+----------------------------------------------------+ >> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >> {"start": "10.48.146.113", "end": "10.48.146.130"} | >> >> +--------------------------------------+------+----------------+----------------------------------------------------+ >> >> [root at lspal117 ~(keystone_admin)]# neutron router-list >> >> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> | id | name | >> external_gateway_info >> >> | distributed | ha | >> >> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >> "external_fixed_ips": [{"subnet_id": >> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >> False | False | >> >> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >> >> Any ideas what is going wrong, I still can?t ping or ssh to that IP >> address and its not listening anywhere ? >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 2:30 PM >> To: SAP SAP , rdo-list >> >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> As Kashyap kindly suggested we're not a support line and information >> here should be available for all the community members. First, I don't see >> how you can ping the br-ex IP address from an external network since it >> doesn't contain any physical interface. Make sure that 10.48.146.112 isn't >> used by other host on you network segment. You can do the following to >> remove the ip address from the physical interface and add it to the br-ex >> bridge. Please make sure that you've got console access to the server >> before doing this as you may lose connectivity. >> >> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >> >> You should then follow the documentation[1] to recreate the >> public/tenant networks and router. In your >> case FLOATING_IP_START, FLOATING_IP_END should be part of the >> 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of >> the 10.48.146.200 - 10.48.146.210 range to your Openstack >> routers/instances, then FLOATING_IP_START=10.48.146.200 and >> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >> what 'ip r | grep default | awk {'print $3'}' outputs >> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >> >> Note that the instance will get an IP address of the tenant network. By >> assigning a floating IP you will be able to access it through an IP address >> from your physical network segment. >> >> [1] >> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >> >> >> >> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: >> >>> Hi Marius, >>> >>> Here are the outputs. Is it possible to reach you on phone so that I >>> can explain more than email. You can call me at 650 849 3915 or let me >>> know your number. >>> >>> #ip a >>> >>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>> inet 127.0.0.1/8 scope host lo >>> valid_lft forever preferred_lft forever >>> inet6 ::1/128 scope host >>> valid_lft forever preferred_lft forever >>> 2: eno1: mtu 1500 qdisc mq state UP >>> qlen 1000 >>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>> valid_lft forever preferred_lft forever >>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>> valid_lft forever preferred_lft forever >>> 3: eno2: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>> 4: eno3: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>> 5: eno4: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>> 6: ens1f0: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>> 7: ens1f1: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>> 8: ens2f0: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>> 9: ens2f1: mtu 1500 qdisc mq state >>> DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>> 10: ovs-system: mtu 1500 qdisc noop state DOWN >>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>> 11: br-ex: mtu 1500 qdisc noqueue >>> state UNKNOWN >>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>> valid_lft forever preferred_lft forever >>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>> valid_lft forever preferred_lft forever >>> 12: br-int: mtu 1500 qdisc noop state DOWN >>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>> 17: qbr63bd6704-47: mtu 1500 qdisc >>> noqueue state UP >>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>> valid_lft forever preferred_lft forever >>> 18: qvo63bd6704-47: mtu 1500 >>> qdisc pfifo_fast master ovs-system state UP qlen 1000 >>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>> 19: qvb63bd6704-47: mtu 1500 >>> qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>> 22: tap63bd6704-47: mtu 1500 qdisc >>> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>> valid_lft forever preferred_lft forever >>> >>> # ovs-vsctl show >>> >>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>> Bridge br-ex >>> Port br-ex >>> Interface br-ex >>> type: internal >>> Port "qg-c3a1b534-36" >>> Interface "qg-c3a1b534-36" >>> type: internal >>> Bridge br-int >>> fail_mode: secure >>> Port patch-tun >>> Interface patch-tun >>> type: patch >>> options: {peer=patch-int} >>> Port "tape386c0cb-d8" >>> tag: 1 >>> Interface "tape386c0cb-d8" >>> type: internal >>> Port br-int >>> Interface br-int >>> type: internal >>> Port "qvo63bd6704-47" >>> tag: 1 >>> Interface "qvo63bd6704-47" >>> Port "tap44dd465f-d4" >>> tag: 4095 >>> Interface "tap44dd465f-d4" >>> type: internal >>> Port "qr-e0ac3c25-2b" >>> tag: 2 >>> Interface "qr-e0ac3c25-2b" >>> type: internal >>> Bridge br-tun >>> Port br-tun >>> Interface br-tun >>> type: internal >>> Port patch-int >>> Interface patch-int >>> type: patch >>> options: {peer=patch-tun} >>> ovs_version: ?2.1.3" >>> >>> # neutron net-list >>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>> >>> +--------------------------------------+---------+------------------------------------------------------+ >>> | id | name | subnets >>> | >>> >>> +--------------------------------------+---------+------------------------------------------------------+ >>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>> >>> +--------------------------------------+---------+------------------------------------------------------+ >>> >>> # neutron subnet-list >>> [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list >>> >>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>> | id | name | cidr >>> | allocation_pools | >>> >>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | >>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 >>> | {"start": "10.0.0.2", "end": "10.0.0.254"} | >>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 >>> | {"start": "10.48.146.112", "end": "10.48.146.120"} | >>> >>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>> >>> #neutron router-list >>> [root at lspal117 network-scripts(keystone_admin)]# neutron router-list >>> >>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>> | id | name | external_gateway_info >>> >>> >>> | distributed | ha | >>> >>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>> "external_fixed_ips": [{"subnet_id": >>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>> False | False | >>> >>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>> >>> In my system I have IP address for BR-ex and ENO1 (interface >>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>> from my network to reach to this host ? Probably its a dump question. >>> >>> Here are the outputs. >>> >>> br-ex: flags=4163 mtu 1500 >>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>> 10.48.146.255 >>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 >>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>> RX packets 10 bytes 864 (864.0 B) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 25 bytes 3767 (3.6 KiB) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> br-int: flags=4098 mtu 1500 >>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>> RX packets 135 bytes 7574 (7.3 KiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 0 bytes 0 (0.0 B) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> br-tun: flags=4098 mtu 1500 >>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>> RX packets 0 bytes 0 (0.0 B) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 0 bytes 0 (0.0 B) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> eno1: flags=4163 mtu 1500 >>> inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 >>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>> 0x20 >>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>> RX packets 467319 bytes 48391354 (46.1 MiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 14794 bytes 5238733 (4.9 MiB) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> device interrupt 32 >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 1:46 PM >>> To: SAP SAP >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Hi Rushi, >>> >>> Can you provide the output of the following commands on your node ? >>> >>> # ip a >>> # ovs-vsctl show >>> # neutron net-list >>> # neutron subnet-list >>> # neutron router-list >>> >>> Please note that only the br-ex bridge requires an IP address, the >>> interface that's part of it shouldn't have one assigned. Also the floating >>> IP addresses will be used for DNAT on the tenant router. You can check the >>> documentation here[1] that describes the use of floating IPs. >>> >>> You can also check the upstream documentation[2] on how to create the >>> networks. >>> >>> [1] >>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>> [2] >>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>> >>> >>> Tnx, >>> Marius >>> >>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: >>> >>>> Hi Support, >>>> >>>> I have a problem that a launched instance from openstack cannot >>>> connect to SSH or PING >>>> >>>> First of all I have dump question whether my system should be NOVA >>>> network or Neutron network. Well to keep everyone on the same page. Here is >>>> my history. >>>> >>>> >>>> 1. I did install RDO (allinone host) using the bellow steps >>>> https://openstack.redhat.com/Quickstart >>>> 2. Then I have used the following steps for floating IP >>>> https://openstack.redhat.com/Floating_IP_range. >>>> >>>> My situtation is as follows. >>>> * Floating IP address assignment: >>>> I have assigned a floating IP , I did follow this steps. >>>> https://openstack.redhat.com/Floating_IP_range >>>> >>>> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 >>>> it is eno1 name)is on the same bridge as the compute host >>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >>>> 10.48.146.112 >>>> >>>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>>> hearing and responding to DHCP >>>> requests and the instance is getting IP from 10.48.146.113 (next hop) >>>> however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>> rule on default security group) >>>> >>>> Here is the little diagram of my system. >>>> >>>> Can someone help to find what is missing. >>>> >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> _______________________________________________ >>>> Rdo-list mailing list >>>> Rdo-list at redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: From kchamart at redhat.com Sat Jan 10 00:07:50 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Sat, 10 Jan 2015 01:07:50 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: <20150110000750.GB438@tesla.redhat.com> On Fri, Jan 09, 2015 at 11:58:03PM +0000, Ns, Rushi wrote: > Ok I did the folowing steps for tenant. > > 1) neutron net-create demo-net > 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 > 3) neutron router-create demo-router > 4) neutron router-interface-add demo-router demo-subnet > > Anything left .? Usually, in a developer setup, I do the below once I have Neutron installed - Create a new private network - Create a new private subnet (on the above private network) - Create a router - Associate the router to an existing external network by setting it as its gateway - Associate the private network interface to the router - Add Neutron security group rules for ICMP and SSH Maybe this notes which talks about creating repeated Neutron tenant networks might have clues http://kashyapc.com/2013/12/13/script-to-create-neutron-tenant-networks/ PS: Please do not top post on technical lists - it really makes the discussoin hard to follow. -- /kashyap From rushi.ns at sap.com Sat Jan 10 00:16:45 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 00:16:45 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: From marius at remote-lab.net Sat Jan 10 00:18:51 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 01:18:51 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: > I can?t assign a port to the floating ip . I don?t? see any ports > available ? > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM > > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > You've already defined router1 which is already connected to the > external network. You can use that. ext-net is the 'public' network in your > case. > > On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: > >> I can?t run this command >> >> >> $ neutron router-gateway-set demo-router ext-net >> >> Its getting error (ext-net not found) ? What is the ext-net in this >> case ? >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> From: , SAP SAP >> Date: Friday, January 9, 2015 at 3:58 PM >> >> To: Marius Cornea >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Ok I did the folowing steps for tenant. >> >> 1) neutron net-create demo-net >> 2) neutron subnet-create demo-net --name demo-subnet --gateway >> 10.48.146.1 10.48.146.0/24 >> 3) neutron router-create demo-router >> 4) neutron router-interface-add demo-router demo-subnet >> >> Anything left .? >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: , SAP SAP >> Date: Friday, January 9, 2015 at 3:55 PM >> To: Marius Cornea >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Hi Marius, >> >> Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide >> the comamnds or link to create tenant network, subjet and attach to router >> ? >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 3:48 PM >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Can you ping 10.48.146.113 from your network? You also need to create >> a tenant network, subnet and attach it to the router. Boot the instance >> with the tenant network attached and then assign it the floating IP. >> >> >> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: >> >>> Hi Marius, >>> >>> I did this first and now can see the BR-ex is the same IP as my eno1 >>> interface , you are right I lost first while doing the first command(ip >>> addr del 10.48.146.77/24 dev eno1) and then conneting to console I did >>> the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP >>> address of br-ex to 10.48.146.77) >>> >>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >>> >>> Then after I removed all the routers, networks and interfaces from >>> openstack and ran the following 4 commands. >>> >>> 1) source /root/keystonerc_admin >>> 2) neutron net-create public --router:external=True >>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>> --gateway 10.48.146.1 >>> 4) neutron router-create router1 >>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>> 6) neutron floatingip-create public >>> >>> The above command generated a floating IP 10.48.146.115 >>> >>> Then I spin up a new instance and it got IP assigned automatically >>> 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? >>> >>> Here are the screenshots >>> >>> >>> >>> >>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>> >>> +--------------------------------------+--------+-----------------------------------------------------+ >>> | id | name | subnets >>> | >>> >>> +--------------------------------------+--------+-----------------------------------------------------+ >>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>> >>> +--------------------------------------+--------+??????????????????????????+ >>> >>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>> >>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>> | id | name | cidr | >>> allocation_pools | >>> >>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>> >>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>> >>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>> >>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>> | id | name | >>> external_gateway_info >>> >>> | distributed | ha | >>> >>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>> "external_fixed_ips": [{"subnet_id": >>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>> False | False | >>> >>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>> >>> Any ideas what is going wrong, I still can?t ping or ssh to that IP >>> address and its not listening anywhere ? >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 2:30 PM >>> To: SAP SAP , rdo-list >>> >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> As Kashyap kindly suggested we're not a support line and information >>> here should be available for all the community members. First, I don't see >>> how you can ping the br-ex IP address from an external network since it >>> doesn't contain any physical interface. Make sure that 10.48.146.112 isn't >>> used by other host on you network segment. You can do the following to >>> remove the ip address from the physical interface and add it to the br-ex >>> bridge. Please make sure that you've got console access to the server >>> before doing this as you may lose connectivity. >>> >>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >>> >>> You should then follow the documentation[1] to recreate the >>> public/tenant networks and router. In your >>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>> 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of >>> the 10.48.146.200 - 10.48.146.210 range to your Openstack >>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>> what 'ip r | grep default | awk {'print $3'}' outputs >>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>> >>> Note that the instance will get an IP address of the tenant network. >>> By assigning a floating IP you will be able to access it through an IP >>> address from your physical network segment. >>> >>> [1] >>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>> >>> >>> >>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: >>> >>>> Hi Marius, >>>> >>>> Here are the outputs. Is it possible to reach you on phone so that I >>>> can explain more than email. You can call me at 650 849 3915 or let me >>>> know your number. >>>> >>>> #ip a >>>> >>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>> inet 127.0.0.1/8 scope host lo >>>> valid_lft forever preferred_lft forever >>>> inet6 ::1/128 scope host >>>> valid_lft forever preferred_lft forever >>>> 2: eno1: mtu 1500 qdisc mq state UP >>>> qlen 1000 >>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>> valid_lft forever preferred_lft forever >>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>> valid_lft forever preferred_lft forever >>>> 3: eno2: mtu 1500 qdisc mq state >>>> DOWN qlen 1000 >>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>> 4: eno3: mtu 1500 qdisc mq state >>>> DOWN qlen 1000 >>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>> 5: eno4: mtu 1500 qdisc mq state >>>> DOWN qlen 1000 >>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>> 6: ens1f0: mtu 1500 qdisc mq state >>>> DOWN qlen 1000 >>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>> 7: ens1f1: mtu 1500 qdisc mq state >>>> DOWN qlen 1000 >>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>> 8: ens2f0: mtu 1500 qdisc mq state >>>> DOWN qlen 1000 >>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>> 9: ens2f1: mtu 1500 qdisc mq state >>>> DOWN qlen 1000 >>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>> 10: ovs-system: mtu 1500 qdisc noop state DOWN >>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>> 11: br-ex: mtu 1500 qdisc noqueue >>>> state UNKNOWN >>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>> valid_lft forever preferred_lft forever >>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>> valid_lft forever preferred_lft forever >>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>> 17: qbr63bd6704-47: mtu 1500 qdisc >>>> noqueue state UP >>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>> valid_lft forever preferred_lft forever >>>> 18: qvo63bd6704-47: mtu 1500 >>>> qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>> 19: qvb63bd6704-47: mtu 1500 >>>> qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>> 22: tap63bd6704-47: mtu 1500 qdisc >>>> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>> valid_lft forever preferred_lft forever >>>> >>>> # ovs-vsctl show >>>> >>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>> Bridge br-ex >>>> Port br-ex >>>> Interface br-ex >>>> type: internal >>>> Port "qg-c3a1b534-36" >>>> Interface "qg-c3a1b534-36" >>>> type: internal >>>> Bridge br-int >>>> fail_mode: secure >>>> Port patch-tun >>>> Interface patch-tun >>>> type: patch >>>> options: {peer=patch-int} >>>> Port "tape386c0cb-d8" >>>> tag: 1 >>>> Interface "tape386c0cb-d8" >>>> type: internal >>>> Port br-int >>>> Interface br-int >>>> type: internal >>>> Port "qvo63bd6704-47" >>>> tag: 1 >>>> Interface "qvo63bd6704-47" >>>> Port "tap44dd465f-d4" >>>> tag: 4095 >>>> Interface "tap44dd465f-d4" >>>> type: internal >>>> Port "qr-e0ac3c25-2b" >>>> tag: 2 >>>> Interface "qr-e0ac3c25-2b" >>>> type: internal >>>> Bridge br-tun >>>> Port br-tun >>>> Interface br-tun >>>> type: internal >>>> Port patch-int >>>> Interface patch-int >>>> type: patch >>>> options: {peer=patch-tun} >>>> ovs_version: ?2.1.3" >>>> >>>> # neutron net-list >>>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>>> >>>> +--------------------------------------+---------+------------------------------------------------------+ >>>> | id | name | subnets >>>> | >>>> >>>> +--------------------------------------+---------+------------------------------------------------------+ >>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>> >>>> +--------------------------------------+---------+------------------------------------------------------+ >>>> >>>> # neutron subnet-list >>>> [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list >>>> >>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>> | id | name | cidr >>>> | allocation_pools | >>>> >>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | >>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 >>>> | {"start": "10.0.0.2", "end": "10.0.0.254"} | >>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | >>>> >>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>> >>>> #neutron router-list >>>> [root at lspal117 network-scripts(keystone_admin)]# neutron router-list >>>> >>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>> | id | name | >>>> external_gateway_info >>>> >>>> | distributed | ha | >>>> >>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>> "external_fixed_ips": [{"subnet_id": >>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>> False | False | >>>> >>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>> >>>> In my system I have IP address for BR-ex and ENO1 (interface >>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>> from my network to reach to this host ? Probably its a dump question. >>>> >>>> Here are the outputs. >>>> >>>> br-ex: flags=4163 mtu 1500 >>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>> 10.48.146.255 >>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>> 0x20 >>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>> RX packets 10 bytes 864 (864.0 B) >>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>> TX packets 25 bytes 3767 (3.6 KiB) >>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>> >>>> br-int: flags=4098 mtu 1500 >>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>> RX packets 135 bytes 7574 (7.3 KiB) >>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>> TX packets 0 bytes 0 (0.0 B) >>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>> >>>> br-tun: flags=4098 mtu 1500 >>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>> RX packets 0 bytes 0 (0.0 B) >>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>> TX packets 0 bytes 0 (0.0 B) >>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>> >>>> eno1: flags=4163 mtu 1500 >>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>> 10.48.146.255 >>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>> 0x20 >>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>> device interrupt 32 >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 1:46 PM >>>> To: SAP SAP >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> Hi Rushi, >>>> >>>> Can you provide the output of the following commands on your node ? >>>> >>>> # ip a >>>> # ovs-vsctl show >>>> # neutron net-list >>>> # neutron subnet-list >>>> # neutron router-list >>>> >>>> Please note that only the br-ex bridge requires an IP address, the >>>> interface that's part of it shouldn't have one assigned. Also the floating >>>> IP addresses will be used for DNAT on the tenant router. You can check the >>>> documentation here[1] that describes the use of floating IPs. >>>> >>>> You can also check the upstream documentation[2] on how to create the >>>> networks. >>>> >>>> [1] >>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>> [2] >>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>> >>>> >>>> Tnx, >>>> Marius >>>> >>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: >>>> >>>>> Hi Support, >>>>> >>>>> I have a problem that a launched instance from openstack cannot >>>>> connect to SSH or PING >>>>> >>>>> First of all I have dump question whether my system should be NOVA >>>>> network or Neutron network. Well to keep everyone on the same page. Here is >>>>> my history. >>>>> >>>>> >>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>> https://openstack.redhat.com/Quickstart >>>>> 2. Then I have used the following steps for floating IP >>>>> https://openstack.redhat.com/Floating_IP_range. >>>>> >>>>> My situtation is as follows. >>>>> * Floating IP address assignment: >>>>> I have assigned a floating IP , I did follow this steps. >>>>> https://openstack.redhat.com/Floating_IP_range >>>>> >>>>> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 >>>>> it is eno1 name)is on the same bridge as the compute host >>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >>>>> 10.48.146.112 >>>>> >>>>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>>>> hearing and responding to DHCP >>>>> requests and the instance is getting IP from 10.48.146.113 (next hop) >>>>> however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>> rule on default security group) >>>>> >>>>> Here is the little diagram of my system. >>>>> >>>>> Can someone help to find what is missing. >>>>> >>>>> >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> _______________________________________________ >>>>> Rdo-list mailing list >>>>> Rdo-list at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 00:21:08 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 00:21:08 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: From marius at remote-lab.net Sat Jan 10 00:27:31 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 01:27:31 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi wrote: > Yes, I did boot the instance but its getting 10.48.146.4 address rather > 192.168.*** that you gave me ? I can logon to the instance console > 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from > host? > > Is it possible I share my screen, so that you can guide me what wrong > thing that stops and bother me ? > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM > > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Did you boot the instance with the demo-net attached ? > > On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: > >> I can?t assign a port to the floating ip . I don?t? see any ports >> available ? >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 4:06 PM >> >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> You've already defined router1 which is already connected to the >> external network. You can use that. ext-net is the 'public' network in your >> case. >> >> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: >> >>> I can?t run this command >>> >>> >>> $ neutron router-gateway-set demo-router ext-net >>> >>> Its getting error (ext-net not found) ? What is the ext-net in this >>> case ? >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> From: , SAP SAP >>> Date: Friday, January 9, 2015 at 3:58 PM >>> >>> To: Marius Cornea >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Ok I did the folowing steps for tenant. >>> >>> 1) neutron net-create demo-net >>> 2) neutron subnet-create demo-net --name demo-subnet --gateway >>> 10.48.146.1 10.48.146.0/24 >>> 3) neutron router-create demo-router >>> 4) neutron router-interface-add demo-router demo-subnet >>> >>> Anything left .? >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: , SAP SAP >>> Date: Friday, January 9, 2015 at 3:55 PM >>> To: Marius Cornea >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Hi Marius, >>> >>> Yes, I can ping 10.48.146.113 (gateway) from the host , can you >>> provide the comamnds or link to create tenant network, subjet and attach to >>> router ? >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 3:48 PM >>> To: SAP SAP >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Can you ping 10.48.146.113 from your network? You also need to create >>> a tenant network, subnet and attach it to the router. Boot the instance >>> with the tenant network attached and then assign it the floating IP. >>> >>> >>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: >>> >>>> Hi Marius, >>>> >>>> I did this first and now can see the BR-ex is the same IP as my eno1 >>>> interface , you are right I lost first while doing the first command(ip >>>> addr del 10.48.146.77/24 dev eno1) and then conneting to console I did >>>> the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP >>>> address of br-ex to 10.48.146.77) >>>> >>>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >>>> >>>> Then after I removed all the routers, networks and interfaces from >>>> openstack and ran the following 4 commands. >>>> >>>> 1) source /root/keystonerc_admin >>>> 2) neutron net-create public --router:external=True >>>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>> --gateway 10.48.146.1 >>>> 4) neutron router-create router1 >>>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>>> 6) neutron floatingip-create public >>>> >>>> The above command generated a floating IP 10.48.146.115 >>>> >>>> Then I spin up a new instance and it got IP assigned automatically >>>> 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? >>>> >>>> Here are the screenshots >>>> >>>> >>>> >>>> >>>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>>> >>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>> | id | name | subnets >>>> | >>>> >>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>>> >>>> +--------------------------------------+--------+??????????????????????????+ >>>> >>>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>>> >>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>> | id | name | cidr | >>>> allocation_pools | >>>> >>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>>> >>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>> >>>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>>> >>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>> | id | name | >>>> external_gateway_info >>>> >>>> | distributed | ha | >>>> >>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>>> "external_fixed_ips": [{"subnet_id": >>>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>>> False | False | >>>> >>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>> >>>> Any ideas what is going wrong, I still can?t ping or ssh to that IP >>>> address and its not listening anywhere ? >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 2:30 PM >>>> To: SAP SAP , rdo-list >>>> >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> As Kashyap kindly suggested we're not a support line and information >>>> here should be available for all the community members. First, I don't see >>>> how you can ping the br-ex IP address from an external network since it >>>> doesn't contain any physical interface. Make sure that 10.48.146.112 isn't >>>> used by other host on you network segment. You can do the following to >>>> remove the ip address from the physical interface and add it to the br-ex >>>> bridge. Please make sure that you've got console access to the server >>>> before doing this as you may lose connectivity. >>>> >>>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >>>> >>>> You should then follow the documentation[1] to recreate the >>>> public/tenant networks and router. In your >>>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>>> 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of >>>> the 10.48.146.200 - 10.48.146.210 range to your Openstack >>>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>>> what 'ip r | grep default | awk {'print $3'}' outputs >>>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>>> >>>> Note that the instance will get an IP address of the tenant network. >>>> By assigning a floating IP you will be able to access it through an IP >>>> address from your physical network segment. >>>> >>>> [1] >>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>> >>>> >>>> >>>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: >>>> >>>>> Hi Marius, >>>>> >>>>> Here are the outputs. Is it possible to reach you on phone so that I >>>>> can explain more than email. You can call me at 650 849 3915 or let >>>>> me know your number. >>>>> >>>>> #ip a >>>>> >>>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>>> inet 127.0.0.1/8 scope host lo >>>>> valid_lft forever preferred_lft forever >>>>> inet6 ::1/128 scope host >>>>> valid_lft forever preferred_lft forever >>>>> 2: eno1: mtu 1500 qdisc mq state UP >>>>> qlen 1000 >>>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>>> valid_lft forever preferred_lft forever >>>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> 3: eno2: mtu 1500 qdisc mq state >>>>> DOWN qlen 1000 >>>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>>> 4: eno3: mtu 1500 qdisc mq state >>>>> DOWN qlen 1000 >>>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>>> 5: eno4: mtu 1500 qdisc mq state >>>>> DOWN qlen 1000 >>>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>>> 6: ens1f0: mtu 1500 qdisc mq state >>>>> DOWN qlen 1000 >>>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>>> 7: ens1f1: mtu 1500 qdisc mq state >>>>> DOWN qlen 1000 >>>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>>> 8: ens2f0: mtu 1500 qdisc mq state >>>>> DOWN qlen 1000 >>>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>>> 9: ens2f1: mtu 1500 qdisc mq state >>>>> DOWN qlen 1000 >>>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>>> 10: ovs-system: mtu 1500 qdisc noop state DOWN >>>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>>> 11: br-ex: mtu 1500 qdisc noqueue >>>>> state UNKNOWN >>>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>>> valid_lft forever preferred_lft forever >>>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>>> 17: qbr63bd6704-47: mtu 1500 qdisc >>>>> noqueue state UP >>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> 18: qvo63bd6704-47: mtu 1500 >>>>> qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>>> 19: qvb63bd6704-47: mtu 1500 >>>>> qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>> 22: tap63bd6704-47: mtu 1500 qdisc >>>>> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> >>>>> # ovs-vsctl show >>>>> >>>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>>> Bridge br-ex >>>>> Port br-ex >>>>> Interface br-ex >>>>> type: internal >>>>> Port "qg-c3a1b534-36" >>>>> Interface "qg-c3a1b534-36" >>>>> type: internal >>>>> Bridge br-int >>>>> fail_mode: secure >>>>> Port patch-tun >>>>> Interface patch-tun >>>>> type: patch >>>>> options: {peer=patch-int} >>>>> Port "tape386c0cb-d8" >>>>> tag: 1 >>>>> Interface "tape386c0cb-d8" >>>>> type: internal >>>>> Port br-int >>>>> Interface br-int >>>>> type: internal >>>>> Port "qvo63bd6704-47" >>>>> tag: 1 >>>>> Interface "qvo63bd6704-47" >>>>> Port "tap44dd465f-d4" >>>>> tag: 4095 >>>>> Interface "tap44dd465f-d4" >>>>> type: internal >>>>> Port "qr-e0ac3c25-2b" >>>>> tag: 2 >>>>> Interface "qr-e0ac3c25-2b" >>>>> type: internal >>>>> Bridge br-tun >>>>> Port br-tun >>>>> Interface br-tun >>>>> type: internal >>>>> Port patch-int >>>>> Interface patch-int >>>>> type: patch >>>>> options: {peer=patch-tun} >>>>> ovs_version: ?2.1.3" >>>>> >>>>> # neutron net-list >>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>>>> >>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>> | id | name | subnets >>>>> | >>>>> >>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>>> >>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>> >>>>> # neutron subnet-list >>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list >>>>> >>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>> | id | name | cidr >>>>> | allocation_pools | >>>>> >>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | >>>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 >>>>> | {"start": "10.0.0.2", "end": "10.0.0.254"} | >>>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | >>>>> >>>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>>> >>>>> #neutron router-list >>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron router-list >>>>> >>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>> | id | name | >>>>> external_gateway_info >>>>> >>>>> | distributed | ha | >>>>> >>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>>> "external_fixed_ips": [{"subnet_id": >>>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>>> False | False | >>>>> >>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>>> >>>>> In my system I have IP address for BR-ex and ENO1 (interface >>>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>>> from my network to reach to this host ? Probably its a dump question. >>>>> >>>>> Here are the outputs. >>>>> >>>>> br-ex: flags=4163 mtu 1500 >>>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>>> 10.48.146.255 >>>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>>> 0x20 >>>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>>> RX packets 10 bytes 864 (864.0 B) >>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>> TX packets 25 bytes 3767 (3.6 KiB) >>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>> >>>>> br-int: flags=4098 mtu 1500 >>>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>>> RX packets 135 bytes 7574 (7.3 KiB) >>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>> TX packets 0 bytes 0 (0.0 B) >>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>> >>>>> br-tun: flags=4098 mtu 1500 >>>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>>> RX packets 0 bytes 0 (0.0 B) >>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>> TX packets 0 bytes 0 (0.0 B) >>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>> >>>>> eno1: flags=4163 mtu 1500 >>>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>>> 10.48.146.255 >>>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>>> 0x20 >>>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>> device interrupt 32 >>>>> >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: Marius Cornea >>>>> Date: Friday, January 9, 2015 at 1:46 PM >>>>> To: SAP SAP >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> Hi Rushi, >>>>> >>>>> Can you provide the output of the following commands on your node ? >>>>> >>>>> # ip a >>>>> # ovs-vsctl show >>>>> # neutron net-list >>>>> # neutron subnet-list >>>>> # neutron router-list >>>>> >>>>> Please note that only the br-ex bridge requires an IP address, the >>>>> interface that's part of it shouldn't have one assigned. Also the floating >>>>> IP addresses will be used for DNAT on the tenant router. You can check the >>>>> documentation here[1] that describes the use of floating IPs. >>>>> >>>>> You can also check the upstream documentation[2] on how to create >>>>> the networks. >>>>> >>>>> [1] >>>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>>> [2] >>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>> >>>>> >>>>> Tnx, >>>>> Marius >>>>> >>>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: >>>>> >>>>>> Hi Support, >>>>>> >>>>>> I have a problem that a launched instance from openstack cannot >>>>>> connect to SSH or PING >>>>>> >>>>>> First of all I have dump question whether my system should be NOVA >>>>>> network or Neutron network. Well to keep everyone on the same page. Here is >>>>>> my history. >>>>>> >>>>>> >>>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>>> https://openstack.redhat.com/Quickstart >>>>>> 2. Then I have used the following steps for floating IP >>>>>> https://openstack.redhat.com/Floating_IP_range. >>>>>> >>>>>> My situtation is as follows. >>>>>> * Floating IP address assignment: >>>>>> I have assigned a floating IP , I did follow this steps. >>>>>> https://openstack.redhat.com/Floating_IP_range >>>>>> >>>>>> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 >>>>>> it is eno1 name)is on the same bridge as the compute host >>>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >>>>>> 10.48.146.112 >>>>>> >>>>>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>>>>> hearing and responding to DHCP >>>>>> requests and the instance is getting IP from 10.48.146.113 (next hop) >>>>>> however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>>> rule on default security group) >>>>>> >>>>>> Here is the little diagram of my system. >>>>>> >>>>>> Can someone help to find what is missing. >>>>>> >>>>>> >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Rdo-list mailing list >>>>>> Rdo-list at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 00:35:55 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 00:35:55 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: From marius at remote-lab.net Sat Jan 10 00:46:01 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 01:46:01 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi wrote: > I have deleted all network (admin) and tenant as I wanted your guidance > to do further > > Can you help to give steps to add the network again (10.48.146.0/24) and > tenant 192.168.10.0/24 after floating ip to 10.48.146.113) > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM > > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Let's keep the troubleshooting steps on the list. What's the output of > 'nova list' ? > > On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi wrote: > >> Yes, I did boot the instance but its getting 10.48.146.4 address >> rather 192.168.*** that you gave me ? I can logon to the instance console >> 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from >> host? >> >> Is it possible I share my screen, so that you can guide me what wrong >> thing that stops and bother me ? >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 4:18 PM >> >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Did you boot the instance with the demo-net attached ? >> >> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: >> >>> I can?t assign a port to the floating ip . I don?t? see any ports >>> available ? >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 4:06 PM >>> >>> To: SAP SAP >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> You've already defined router1 which is already connected to the >>> external network. You can use that. ext-net is the 'public' network in your >>> case. >>> >>> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: >>> >>>> I can?t run this command >>>> >>>> >>>> $ neutron router-gateway-set demo-router ext-net >>>> >>>> Its getting error (ext-net not found) ? What is the ext-net in this >>>> case ? >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> From: , SAP SAP >>>> Date: Friday, January 9, 2015 at 3:58 PM >>>> >>>> To: Marius Cornea >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> Ok I did the folowing steps for tenant. >>>> >>>> 1) neutron net-create demo-net >>>> 2) neutron subnet-create demo-net --name demo-subnet --gateway >>>> 10.48.146.1 10.48.146.0/24 >>>> 3) neutron router-create demo-router >>>> 4) neutron router-interface-add demo-router demo-subnet >>>> >>>> Anything left .? >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: , SAP SAP >>>> Date: Friday, January 9, 2015 at 3:55 PM >>>> To: Marius Cornea >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> Hi Marius, >>>> >>>> Yes, I can ping 10.48.146.113 (gateway) from the host , can you >>>> provide the comamnds or link to create tenant network, subjet and attach to >>>> router ? >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 3:48 PM >>>> To: SAP SAP >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> Can you ping 10.48.146.113 from your network? You also need to >>>> create a tenant network, subnet and attach it to the router. Boot the >>>> instance with the tenant network attached and then assign it the floating >>>> IP. >>>> >>>> >>>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: >>>> >>>>> Hi Marius, >>>>> >>>>> I did this first and now can see the BR-ex is the same IP as my eno1 >>>>> interface , you are right I lost first while doing the first command(ip >>>>> addr del 10.48.146.77/24 dev eno1) and then conneting to console I >>>>> did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the >>>>> IP address of br-ex to 10.48.146.77) >>>>> >>>>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >>>>> >>>>> Then after I removed all the routers, networks and interfaces from >>>>> openstack and ran the following 4 commands. >>>>> >>>>> 1) source /root/keystonerc_admin >>>>> 2) neutron net-create public --router:external=True >>>>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>>> --gateway 10.48.146.1 >>>>> 4) neutron router-create router1 >>>>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>>>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>>>> 6) neutron floatingip-create public >>>>> >>>>> The above command generated a floating IP 10.48.146.115 >>>>> >>>>> Then I spin up a new instance and it got IP assigned automatically >>>>> 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? >>>>> >>>>> Here are the screenshots >>>>> >>>>> >>>>> >>>>> >>>>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>>>> >>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>> | id | name | subnets >>>>> | >>>>> >>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>>>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>>>> >>>>> +--------------------------------------+--------+??????????????????????????+ >>>>> >>>>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>>>> >>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>> | id | name | cidr | >>>>> allocation_pools | >>>>> >>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>>>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>>>> >>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>> >>>>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>>>> >>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>> | id | name | >>>>> external_gateway_info >>>>> >>>>> | distributed | ha | >>>>> >>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>>>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>>>> "external_fixed_ips": [{"subnet_id": >>>>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>>>> False | False | >>>>> >>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>> >>>>> Any ideas what is going wrong, I still can?t ping or ssh to that IP >>>>> address and its not listening anywhere ? >>>>> >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: Marius Cornea >>>>> Date: Friday, January 9, 2015 at 2:30 PM >>>>> To: SAP SAP , rdo-list >>>>> >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> As Kashyap kindly suggested we're not a support line and >>>>> information here should be available for all the community members. First, >>>>> I don't see how you can ping the br-ex IP address from an external network >>>>> since it doesn't contain any physical interface. Make sure that >>>>> 10.48.146.112 isn't used by other host on you network segment. You can do >>>>> the following to remove the ip address from the physical interface and add >>>>> it to the br-ex bridge. Please make sure that you've got console access to >>>>> the server before doing this as you may lose connectivity. >>>>> >>>>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >>>>> >>>>> You should then follow the documentation[1] to recreate the >>>>> public/tenant networks and router. In your >>>>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>>>> 10.48.146.0/24 network. Let's say you wish to allocate IP addresses >>>>> of the 10.48.146.200 - 10.48.146.210 range to your Openstack >>>>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>>>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>>>> what 'ip r | grep default | awk {'print $3'}' outputs >>>>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>>>> >>>>> Note that the instance will get an IP address of the tenant network. >>>>> By assigning a floating IP you will be able to access it through an IP >>>>> address from your physical network segment. >>>>> >>>>> [1] >>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>> >>>>> >>>>> >>>>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: >>>>> >>>>>> Hi Marius, >>>>>> >>>>>> Here are the outputs. Is it possible to reach you on phone so that >>>>>> I can explain more than email. You can call me at 650 849 3915 or >>>>>> let me know your number. >>>>>> >>>>>> #ip a >>>>>> >>>>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>>>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>>>> inet 127.0.0.1/8 scope host lo >>>>>> valid_lft forever preferred_lft forever >>>>>> inet6 ::1/128 scope host >>>>>> valid_lft forever preferred_lft forever >>>>>> 2: eno1: mtu 1500 qdisc mq state UP >>>>>> qlen 1000 >>>>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>>>> valid_lft forever preferred_lft forever >>>>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>>>> valid_lft forever preferred_lft forever >>>>>> 3: eno2: mtu 1500 qdisc mq state >>>>>> DOWN qlen 1000 >>>>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>>>> 4: eno3: mtu 1500 qdisc mq state >>>>>> DOWN qlen 1000 >>>>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>>>> 5: eno4: mtu 1500 qdisc mq state >>>>>> DOWN qlen 1000 >>>>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>>>> 6: ens1f0: mtu 1500 qdisc mq >>>>>> state DOWN qlen 1000 >>>>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>>>> 7: ens1f1: mtu 1500 qdisc mq >>>>>> state DOWN qlen 1000 >>>>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>>>> 8: ens2f0: mtu 1500 qdisc mq >>>>>> state DOWN qlen 1000 >>>>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>>>> 9: ens2f1: mtu 1500 qdisc mq >>>>>> state DOWN qlen 1000 >>>>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>>>> 10: ovs-system: mtu 1500 qdisc noop state DOWN >>>>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>>>> 11: br-ex: mtu 1500 qdisc noqueue >>>>>> state UNKNOWN >>>>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>>>> valid_lft forever preferred_lft forever >>>>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>>>> valid_lft forever preferred_lft forever >>>>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>>>> 17: qbr63bd6704-47: mtu 1500 qdisc >>>>>> noqueue state UP >>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>>>> valid_lft forever preferred_lft forever >>>>>> 18: qvo63bd6704-47: mtu >>>>>> 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>>>> 19: qvb63bd6704-47: mtu >>>>>> 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>> 22: tap63bd6704-47: mtu 1500 qdisc >>>>>> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>>>> valid_lft forever preferred_lft forever >>>>>> >>>>>> # ovs-vsctl show >>>>>> >>>>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>>>> Bridge br-ex >>>>>> Port br-ex >>>>>> Interface br-ex >>>>>> type: internal >>>>>> Port "qg-c3a1b534-36" >>>>>> Interface "qg-c3a1b534-36" >>>>>> type: internal >>>>>> Bridge br-int >>>>>> fail_mode: secure >>>>>> Port patch-tun >>>>>> Interface patch-tun >>>>>> type: patch >>>>>> options: {peer=patch-int} >>>>>> Port "tape386c0cb-d8" >>>>>> tag: 1 >>>>>> Interface "tape386c0cb-d8" >>>>>> type: internal >>>>>> Port br-int >>>>>> Interface br-int >>>>>> type: internal >>>>>> Port "qvo63bd6704-47" >>>>>> tag: 1 >>>>>> Interface "qvo63bd6704-47" >>>>>> Port "tap44dd465f-d4" >>>>>> tag: 4095 >>>>>> Interface "tap44dd465f-d4" >>>>>> type: internal >>>>>> Port "qr-e0ac3c25-2b" >>>>>> tag: 2 >>>>>> Interface "qr-e0ac3c25-2b" >>>>>> type: internal >>>>>> Bridge br-tun >>>>>> Port br-tun >>>>>> Interface br-tun >>>>>> type: internal >>>>>> Port patch-int >>>>>> Interface patch-int >>>>>> type: patch >>>>>> options: {peer=patch-tun} >>>>>> ovs_version: ?2.1.3" >>>>>> >>>>>> # neutron net-list >>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>>>>> >>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>> | id | name | subnets >>>>>> | >>>>>> >>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>>>> >>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>> >>>>>> # neutron subnet-list >>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list >>>>>> >>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>> | id | name | cidr >>>>>> | allocation_pools | >>>>>> >>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} >>>>>> | >>>>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 >>>>>> | {"start": "10.0.0.2", "end": "10.0.0.254"} | >>>>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} >>>>>> | >>>>>> >>>>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>>>> >>>>>> #neutron router-list >>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron router-list >>>>>> >>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>> | id | name | >>>>>> external_gateway_info >>>>>> >>>>>> | distributed | ha | >>>>>> >>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>>>> "external_fixed_ips": [{"subnet_id": >>>>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>>>> False | False | >>>>>> >>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>>>> >>>>>> In my system I have IP address for BR-ex and ENO1 (interface >>>>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>>>> from my network to reach to this host ? Probably its a dump question. >>>>>> >>>>>> Here are the outputs. >>>>>> >>>>>> br-ex: flags=4163 mtu 1500 >>>>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>>>> 10.48.146.255 >>>>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>>>> 0x20 >>>>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>>>> RX packets 10 bytes 864 (864.0 B) >>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>> TX packets 25 bytes 3767 (3.6 KiB) >>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>> >>>>>> br-int: flags=4098 mtu 1500 >>>>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>>>> RX packets 135 bytes 7574 (7.3 KiB) >>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>> >>>>>> br-tun: flags=4098 mtu 1500 >>>>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>>>> RX packets 0 bytes 0 (0.0 B) >>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>> >>>>>> eno1: flags=4163 mtu 1500 >>>>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>>>> 10.48.146.255 >>>>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>>>> 0x20 >>>>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>> device interrupt 32 >>>>>> >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> From: Marius Cornea >>>>>> Date: Friday, January 9, 2015 at 1:46 PM >>>>>> To: SAP SAP >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> Hi Rushi, >>>>>> >>>>>> Can you provide the output of the following commands on your node ? >>>>>> >>>>>> # ip a >>>>>> # ovs-vsctl show >>>>>> # neutron net-list >>>>>> # neutron subnet-list >>>>>> # neutron router-list >>>>>> >>>>>> Please note that only the br-ex bridge requires an IP address, the >>>>>> interface that's part of it shouldn't have one assigned. Also the floating >>>>>> IP addresses will be used for DNAT on the tenant router. You can check the >>>>>> documentation here[1] that describes the use of floating IPs. >>>>>> >>>>>> You can also check the upstream documentation[2] on how to create >>>>>> the networks. >>>>>> >>>>>> [1] >>>>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>>>> [2] >>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>> >>>>>> >>>>>> Tnx, >>>>>> Marius >>>>>> >>>>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: >>>>>> >>>>>>> Hi Support, >>>>>>> >>>>>>> I have a problem that a launched instance from openstack cannot >>>>>>> connect to SSH or PING >>>>>>> >>>>>>> First of all I have dump question whether my system should be NOVA >>>>>>> network or Neutron network. Well to keep everyone on the same page. Here is >>>>>>> my history. >>>>>>> >>>>>>> >>>>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>>>> https://openstack.redhat.com/Quickstart >>>>>>> 2. Then I have used the following steps for floating IP >>>>>>> https://openstack.redhat.com/Floating_IP_range. >>>>>>> >>>>>>> My situtation is as follows. >>>>>>> * Floating IP address assignment: >>>>>>> I have assigned a floating IP , I did follow this steps. >>>>>>> https://openstack.redhat.com/Floating_IP_range >>>>>>> >>>>>>> * Bridge configuration:My Ethernet device eth0(actually in Redhat >>>>>>> 7 it is eno1 name)is on the same bridge as the compute host >>>>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >>>>>>> 10.48.146.112 >>>>>>> >>>>>>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>>>>>> hearing and responding to DHCP >>>>>>> requests and the instance is getting IP from 10.48.146.113 (next >>>>>>> hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>>>> rule on default security group) >>>>>>> >>>>>>> Here is the little diagram of my system. >>>>>>> >>>>>>> Can someone help to find what is missing. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Rdo-list mailing list >>>>>>> Rdo-list at redhat.com >>>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 00:50:33 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 00:50:33 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: From marius at remote-lab.net Sat Jan 10 00:52:22 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 01:52:22 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi wrote: > Thanks, I did this step . So what is next ? Sorry to bother but you are > really a life saver to me (thanks to you a ton) as well kashyap . > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > neutron net-create public --router:external=True > neutron subnet-create public 10.48.146.0/24 --name vlan > --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 > --gateway 10.48.146.1 > > neutron net-create demo-net > neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 > 192.168.1.0/24 > > neutron router-create demo-router > neutron router-interface-add demo-router demo-subnet > neutron router-gateway-set demo-router public > > > On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi wrote: > >> I have deleted all network (admin) and tenant as I wanted your >> guidance to do further >> >> Can you help to give steps to add the network again (10.48.146.0/24) >> and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 4:27 PM >> >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Let's keep the troubleshooting steps on the list. What's the output of >> 'nova list' ? >> >> On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi wrote: >> >>> Yes, I did boot the instance but its getting 10.48.146.4 address >>> rather 192.168.*** that you gave me ? I can logon to the instance console >>> 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from >>> host? >>> >>> Is it possible I share my screen, so that you can guide me what wrong >>> thing that stops and bother me ? >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 4:18 PM >>> >>> To: SAP SAP >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Did you boot the instance with the demo-net attached ? >>> >>> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: >>> >>>> I can?t assign a port to the floating ip . I don?t? see any ports >>>> available ? >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 4:06 PM >>>> >>>> To: SAP SAP >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> You've already defined router1 which is already connected to the >>>> external network. You can use that. ext-net is the 'public' network in your >>>> case. >>>> >>>> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: >>>> >>>>> I can?t run this command >>>>> >>>>> >>>>> $ neutron router-gateway-set demo-router ext-net >>>>> >>>>> Its getting error (ext-net not found) ? What is the ext-net in this >>>>> case ? >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> From: , SAP SAP >>>>> Date: Friday, January 9, 2015 at 3:58 PM >>>>> >>>>> To: Marius Cornea >>>>> Cc: rdo-list >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> Ok I did the folowing steps for tenant. >>>>> >>>>> 1) neutron net-create demo-net >>>>> 2) neutron subnet-create demo-net --name demo-subnet --gateway >>>>> 10.48.146.1 10.48.146.0/24 >>>>> 3) neutron router-create demo-router >>>>> 4) neutron router-interface-add demo-router demo-subnet >>>>> >>>>> Anything left .? >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: , SAP SAP >>>>> Date: Friday, January 9, 2015 at 3:55 PM >>>>> To: Marius Cornea >>>>> Cc: rdo-list >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> Hi Marius, >>>>> >>>>> Yes, I can ping 10.48.146.113 (gateway) from the host , can you >>>>> provide the comamnds or link to create tenant network, subjet and attach to >>>>> router ? >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: Marius Cornea >>>>> Date: Friday, January 9, 2015 at 3:48 PM >>>>> To: SAP SAP >>>>> Cc: rdo-list >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> Can you ping 10.48.146.113 from your network? You also need to >>>>> create a tenant network, subnet and attach it to the router. Boot the >>>>> instance with the tenant network attached and then assign it the floating >>>>> IP. >>>>> >>>>> >>>>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: >>>>> >>>>>> Hi Marius, >>>>>> >>>>>> I did this first and now can see the BR-ex is the same IP as my >>>>>> eno1 interface , you are right I lost first while doing the first >>>>>> command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to >>>>>> console I did the second comand (ovs-vsctl add-port br-ex eno1 and also >>>>>> changed the IP address of br-ex to 10.48.146.77) >>>>>> >>>>>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 >>>>>> >>>>>> Then after I removed all the routers, networks and interfaces from >>>>>> openstack and ran the following 4 commands. >>>>>> >>>>>> 1) source /root/keystonerc_admin >>>>>> 2) neutron net-create public --router:external=True >>>>>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>>>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>>>> --gateway 10.48.146.1 >>>>>> 4) neutron router-create router1 >>>>>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>>>>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>>>>> 6) neutron floatingip-create public >>>>>> >>>>>> The above command generated a floating IP 10.48.146.115 >>>>>> >>>>>> Then I spin up a new instance and it got IP assigned automatically >>>>>> 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? >>>>>> >>>>>> Here are the screenshots >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>>>>> >>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>> | id | name | subnets >>>>>> | >>>>>> >>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>>>>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>>>>> >>>>>> +--------------------------------------+--------+??????????????????????????+ >>>>>> >>>>>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>>>>> >>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>> | id | name | cidr | >>>>>> allocation_pools | >>>>>> >>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>>>>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>>>>> >>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>> >>>>>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>>>>> >>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>> | id | name | >>>>>> external_gateway_info >>>>>> >>>>>> | distributed | ha | >>>>>> >>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>>>>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>>>>> "external_fixed_ips": [{"subnet_id": >>>>>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>>>>> False | False | >>>>>> >>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>> >>>>>> Any ideas what is going wrong, I still can?t ping or ssh to that IP >>>>>> address and its not listening anywhere ? >>>>>> >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> From: Marius Cornea >>>>>> Date: Friday, January 9, 2015 at 2:30 PM >>>>>> To: SAP SAP , rdo-list >>>>>> >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> As Kashyap kindly suggested we're not a support line and >>>>>> information here should be available for all the community members. First, >>>>>> I don't see how you can ping the br-ex IP address from an external network >>>>>> since it doesn't contain any physical interface. Make sure that >>>>>> 10.48.146.112 isn't used by other host on you network segment. You can do >>>>>> the following to remove the ip address from the physical interface and add >>>>>> it to the br-ex bridge. Please make sure that you've got console access to >>>>>> the server before doing this as you may lose connectivity. >>>>>> >>>>>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>> eno1 >>>>>> >>>>>> You should then follow the documentation[1] to recreate the >>>>>> public/tenant networks and router. In your >>>>>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>>>>> 10.48.146.0/24 network. Let's say you wish to allocate IP addresses >>>>>> of the 10.48.146.200 - 10.48.146.210 range to your Openstack >>>>>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>>>>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>>>>> what 'ip r | grep default | awk {'print $3'}' outputs >>>>>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>>>>> >>>>>> Note that the instance will get an IP address of the tenant >>>>>> network. By assigning a floating IP you will be able to access it through >>>>>> an IP address from your physical network segment. >>>>>> >>>>>> [1] >>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: >>>>>> >>>>>>> Hi Marius, >>>>>>> >>>>>>> Here are the outputs. Is it possible to reach you on phone so that >>>>>>> I can explain more than email. You can call me at 650 849 3915 or >>>>>>> let me know your number. >>>>>>> >>>>>>> #ip a >>>>>>> >>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>>>>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>>>>> inet 127.0.0.1/8 scope host lo >>>>>>> valid_lft forever preferred_lft forever >>>>>>> inet6 ::1/128 scope host >>>>>>> valid_lft forever preferred_lft forever >>>>>>> 2: eno1: mtu 1500 qdisc mq state >>>>>>> UP qlen 1000 >>>>>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>>>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>>>>> valid_lft forever preferred_lft forever >>>>>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>>>>> valid_lft forever preferred_lft forever >>>>>>> 3: eno2: mtu 1500 qdisc mq state >>>>>>> DOWN qlen 1000 >>>>>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>>>>> 4: eno3: mtu 1500 qdisc mq state >>>>>>> DOWN qlen 1000 >>>>>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>>>>> 5: eno4: mtu 1500 qdisc mq state >>>>>>> DOWN qlen 1000 >>>>>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>>>>> 6: ens1f0: mtu 1500 qdisc mq >>>>>>> state DOWN qlen 1000 >>>>>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>>>>> 7: ens1f1: mtu 1500 qdisc mq >>>>>>> state DOWN qlen 1000 >>>>>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>>>>> 8: ens2f0: mtu 1500 qdisc mq >>>>>>> state DOWN qlen 1000 >>>>>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>>>>> 9: ens2f1: mtu 1500 qdisc mq >>>>>>> state DOWN qlen 1000 >>>>>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>>>>> 10: ovs-system: mtu 1500 qdisc noop state DOWN >>>>>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>>>>> 11: br-ex: mtu 1500 qdisc noqueue >>>>>>> state UNKNOWN >>>>>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>>>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>>>>> valid_lft forever preferred_lft forever >>>>>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>>>>> valid_lft forever preferred_lft forever >>>>>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>>>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>>>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>>>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>>>>> 17: qbr63bd6704-47: mtu 1500 qdisc >>>>>>> noqueue state UP >>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>>>>> valid_lft forever preferred_lft forever >>>>>>> 18: qvo63bd6704-47: mtu >>>>>>> 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>>>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>>>>> 19: qvb63bd6704-47: mtu >>>>>>> 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>> 22: tap63bd6704-47: mtu 1500 qdisc >>>>>>> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>>>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>>>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>>>>> valid_lft forever preferred_lft forever >>>>>>> >>>>>>> # ovs-vsctl show >>>>>>> >>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>>>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>>>>> Bridge br-ex >>>>>>> Port br-ex >>>>>>> Interface br-ex >>>>>>> type: internal >>>>>>> Port "qg-c3a1b534-36" >>>>>>> Interface "qg-c3a1b534-36" >>>>>>> type: internal >>>>>>> Bridge br-int >>>>>>> fail_mode: secure >>>>>>> Port patch-tun >>>>>>> Interface patch-tun >>>>>>> type: patch >>>>>>> options: {peer=patch-int} >>>>>>> Port "tape386c0cb-d8" >>>>>>> tag: 1 >>>>>>> Interface "tape386c0cb-d8" >>>>>>> type: internal >>>>>>> Port br-int >>>>>>> Interface br-int >>>>>>> type: internal >>>>>>> Port "qvo63bd6704-47" >>>>>>> tag: 1 >>>>>>> Interface "qvo63bd6704-47" >>>>>>> Port "tap44dd465f-d4" >>>>>>> tag: 4095 >>>>>>> Interface "tap44dd465f-d4" >>>>>>> type: internal >>>>>>> Port "qr-e0ac3c25-2b" >>>>>>> tag: 2 >>>>>>> Interface "qr-e0ac3c25-2b" >>>>>>> type: internal >>>>>>> Bridge br-tun >>>>>>> Port br-tun >>>>>>> Interface br-tun >>>>>>> type: internal >>>>>>> Port patch-int >>>>>>> Interface patch-int >>>>>>> type: patch >>>>>>> options: {peer=patch-tun} >>>>>>> ovs_version: ?2.1.3" >>>>>>> >>>>>>> # neutron net-list >>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>>>>>> >>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>> | id | name | subnets >>>>>>> | >>>>>>> >>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>>>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>>>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>>>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>>>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>>>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>>>>> >>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>> >>>>>>> # neutron subnet-list >>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>> subnet-list >>>>>>> >>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>> | id | name | cidr >>>>>>> | allocation_pools | >>>>>>> >>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>>>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} >>>>>>> | >>>>>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | >>>>>>> 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} >>>>>>> | >>>>>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>>>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": >>>>>>> "10.48.146.120"} | >>>>>>> >>>>>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>>>>> >>>>>>> #neutron router-list >>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>> router-list >>>>>>> >>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>> | id | name | >>>>>>> external_gateway_info >>>>>>> >>>>>>> | distributed | ha | >>>>>>> >>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>>>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>>>>> False | False | >>>>>>> >>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>>>>> >>>>>>> In my system I have IP address for BR-ex and ENO1 (interface >>>>>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>>>>> from my network to reach to this host ? Probably its a dump question. >>>>>>> >>>>>>> Here are the outputs. >>>>>>> >>>>>>> br-ex: flags=4163 mtu 1500 >>>>>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>>>>> 10.48.146.255 >>>>>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>>>>> 0x20 >>>>>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>>>>> RX packets 10 bytes 864 (864.0 B) >>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>> TX packets 25 bytes 3767 (3.6 KiB) >>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>> >>>>>>> br-int: flags=4098 mtu 1500 >>>>>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>>>>> RX packets 135 bytes 7574 (7.3 KiB) >>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>> >>>>>>> br-tun: flags=4098 mtu 1500 >>>>>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>>>>> RX packets 0 bytes 0 (0.0 B) >>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>> >>>>>>> eno1: flags=4163 mtu 1500 >>>>>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>>>>> 10.48.146.255 >>>>>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>>>>> 0x20 >>>>>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>>>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>> device interrupt 32 >>>>>>> >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> From: Marius Cornea >>>>>>> Date: Friday, January 9, 2015 at 1:46 PM >>>>>>> To: SAP SAP >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> Hi Rushi, >>>>>>> >>>>>>> Can you provide the output of the following commands on your node ? >>>>>>> >>>>>>> # ip a >>>>>>> # ovs-vsctl show >>>>>>> # neutron net-list >>>>>>> # neutron subnet-list >>>>>>> # neutron router-list >>>>>>> >>>>>>> Please note that only the br-ex bridge requires an IP address, the >>>>>>> interface that's part of it shouldn't have one assigned. Also the floating >>>>>>> IP addresses will be used for DNAT on the tenant router. You can check the >>>>>>> documentation here[1] that describes the use of floating IPs. >>>>>>> >>>>>>> You can also check the upstream documentation[2] on how to create >>>>>>> the networks. >>>>>>> >>>>>>> [1] >>>>>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>>>>> [2] >>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>> >>>>>>> >>>>>>> Tnx, >>>>>>> Marius >>>>>>> >>>>>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi wrote: >>>>>>> >>>>>>>> Hi Support, >>>>>>>> >>>>>>>> I have a problem that a launched instance from openstack cannot >>>>>>>> connect to SSH or PING >>>>>>>> >>>>>>>> First of all I have dump question whether my system should be >>>>>>>> NOVA network or Neutron network. Well to keep everyone on the same page. >>>>>>>> Here is my history. >>>>>>>> >>>>>>>> >>>>>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>>>>> https://openstack.redhat.com/Quickstart >>>>>>>> 2. Then I have used the following steps for floating IP >>>>>>>> https://openstack.redhat.com/Floating_IP_range. >>>>>>>> >>>>>>>> My situtation is as follows. >>>>>>>> * Floating IP address assignment: >>>>>>>> I have assigned a floating IP , I did follow this steps. >>>>>>>> https://openstack.redhat.com/Floating_IP_range >>>>>>>> >>>>>>>> * Bridge configuration:My Ethernet device eth0(actually in Redhat >>>>>>>> 7 it is eno1 name)is on the same bridge as the compute host >>>>>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on >>>>>>>> 10.48.146.112 >>>>>>>> >>>>>>>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>>>>>>> hearing and responding to DHCP >>>>>>>> requests and the instance is getting IP from 10.48.146.113 (next >>>>>>>> hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>>>>> rule on default security group) >>>>>>>> >>>>>>>> Here is the little diagram of my system. >>>>>>>> >>>>>>>> Can someone help to find what is missing. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Rushi. >>>>>>>> >>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Rdo-list mailing list >>>>>>>> Rdo-list at redhat.com >>>>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 00:56:48 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 00:56:48 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: From rushi.ns at sap.com Sat Jan 10 01:02:12 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:02:12 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Also I cannot ssh to the instance ..its hung ?I have added ssh and ICMP rules allow from default security group? [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 192.168.1.2 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 4:56 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: From marius at remote-lab.net Sat Jan 10 01:02:20 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 02:02:20 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi wrote: > I did that, launch instance got IP: 192.168.1.2 then I did floating_IP > which I got 10.48.146.114 , however I cannot assign to the instance as > there are no ports avilable.? > > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM > > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Next launch an instance with demo-net attached. Then assign it a > floating IP. You should get 10.48.146.114 as the floating IP. > > On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi wrote: > >> Thanks, I did this step . So what is next ? Sorry to bother but you >> are really a life saver to me (thanks to you a ton) as well kashyap . >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 4:46 PM >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> neutron net-create public --router:external=True >> neutron subnet-create public 10.48.146.0/24 --name vlan >> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >> --gateway 10.48.146.1 >> >> neutron net-create demo-net >> neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 >> 192.168.1.0/24 >> >> neutron router-create demo-router >> neutron router-interface-add demo-router demo-subnet >> neutron router-gateway-set demo-router public >> >> >> On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi wrote: >> >>> I have deleted all network (admin) and tenant as I wanted your >>> guidance to do further >>> >>> Can you help to give steps to add the network again (10.48.146.0/24) >>> and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 4:27 PM >>> >>> To: SAP SAP >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Let's keep the troubleshooting steps on the list. What's the output >>> of 'nova list' ? >>> >>> On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi wrote: >>> >>>> Yes, I did boot the instance but its getting 10.48.146.4 address >>>> rather 192.168.*** that you gave me ? I can logon to the instance console >>>> 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from >>>> host? >>>> >>>> Is it possible I share my screen, so that you can guide me what wrong >>>> thing that stops and bother me ? >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 4:18 PM >>>> >>>> To: SAP SAP >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> Did you boot the instance with the demo-net attached ? >>>> >>>> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: >>>> >>>>> I can?t assign a port to the floating ip . I don?t? see any ports >>>>> available ? >>>>> >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: Marius Cornea >>>>> Date: Friday, January 9, 2015 at 4:06 PM >>>>> >>>>> To: SAP SAP >>>>> Cc: rdo-list >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> You've already defined router1 which is already connected to the >>>>> external network. You can use that. ext-net is the 'public' network in your >>>>> case. >>>>> >>>>> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: >>>>> >>>>>> I can?t run this command >>>>>> >>>>>> >>>>>> $ neutron router-gateway-set demo-router ext-net >>>>>> >>>>>> Its getting error (ext-net not found) ? What is the ext-net in this >>>>>> case ? >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> From: , SAP SAP >>>>>> Date: Friday, January 9, 2015 at 3:58 PM >>>>>> >>>>>> To: Marius Cornea >>>>>> Cc: rdo-list >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> Ok I did the folowing steps for tenant. >>>>>> >>>>>> 1) neutron net-create demo-net >>>>>> 2) neutron subnet-create demo-net --name demo-subnet --gateway >>>>>> 10.48.146.1 10.48.146.0/24 >>>>>> 3) neutron router-create demo-router >>>>>> 4) neutron router-interface-add demo-router demo-subnet >>>>>> >>>>>> Anything left .? >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> From: , SAP SAP >>>>>> Date: Friday, January 9, 2015 at 3:55 PM >>>>>> To: Marius Cornea >>>>>> Cc: rdo-list >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> Hi Marius, >>>>>> >>>>>> Yes, I can ping 10.48.146.113 (gateway) from the host , can you >>>>>> provide the comamnds or link to create tenant network, subjet and attach to >>>>>> router ? >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> From: Marius Cornea >>>>>> Date: Friday, January 9, 2015 at 3:48 PM >>>>>> To: SAP SAP >>>>>> Cc: rdo-list >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> Can you ping 10.48.146.113 from your network? You also need to >>>>>> create a tenant network, subnet and attach it to the router. Boot the >>>>>> instance with the tenant network attached and then assign it the floating >>>>>> IP. >>>>>> >>>>>> >>>>>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi wrote: >>>>>> >>>>>>> Hi Marius, >>>>>>> >>>>>>> I did this first and now can see the BR-ex is the same IP as my >>>>>>> eno1 interface , you are right I lost first while doing the first >>>>>>> command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to >>>>>>> console I did the second comand (ovs-vsctl add-port br-ex eno1 and also >>>>>>> changed the IP address of br-ex to 10.48.146.77) >>>>>>> >>>>>>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>> eno1 >>>>>>> >>>>>>> Then after I removed all the routers, networks and interfaces from >>>>>>> openstack and ran the following 4 commands. >>>>>>> >>>>>>> 1) source /root/keystonerc_admin >>>>>>> 2) neutron net-create public --router:external=True >>>>>>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>>>>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>>>>> --gateway 10.48.146.1 >>>>>>> 4) neutron router-create router1 >>>>>>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>>>>>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>>>>>> 6) neutron floatingip-create public >>>>>>> >>>>>>> The above command generated a floating IP 10.48.146.115 >>>>>>> >>>>>>> Then I spin up a new instance and it got IP assigned automatically >>>>>>> 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? >>>>>>> >>>>>>> Here are the screenshots >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>>>>>> >>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>> | id | name | subnets >>>>>>> | >>>>>>> >>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>>>>>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>>>>>> >>>>>>> +--------------------------------------+--------+??????????????????????????+ >>>>>>> >>>>>>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>>>>>> >>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>> | id | name | cidr | >>>>>>> allocation_pools | >>>>>>> >>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>>>>>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>>>>>> >>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>> >>>>>>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>>>>>> >>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>> | id | name | >>>>>>> external_gateway_info >>>>>>> >>>>>>> | distributed | ha | >>>>>>> >>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>>>>>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>>>>>> False | False | >>>>>>> >>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>> >>>>>>> Any ideas what is going wrong, I still can?t ping or ssh to that >>>>>>> IP address and its not listening anywhere ? >>>>>>> >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> From: Marius Cornea >>>>>>> Date: Friday, January 9, 2015 at 2:30 PM >>>>>>> To: SAP SAP , rdo-list >>>>>>> >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> As Kashyap kindly suggested we're not a support line and >>>>>>> information here should be available for all the community members. First, >>>>>>> I don't see how you can ping the br-ex IP address from an external network >>>>>>> since it doesn't contain any physical interface. Make sure that >>>>>>> 10.48.146.112 isn't used by other host on you network segment. You can do >>>>>>> the following to remove the ip address from the physical interface and add >>>>>>> it to the br-ex bridge. Please make sure that you've got console access to >>>>>>> the server before doing this as you may lose connectivity. >>>>>>> >>>>>>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>> eno1 >>>>>>> >>>>>>> You should then follow the documentation[1] to recreate the >>>>>>> public/tenant networks and router. In your >>>>>>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>>>>>> 10.48.146.0/24 network. Let's say you wish to allocate IP addresses >>>>>>> of the 10.48.146.200 - 10.48.146.210 range to your Openstack >>>>>>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>>>>>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>>>>>> what 'ip r | grep default | awk {'print $3'}' outputs >>>>>>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>>>>>> >>>>>>> Note that the instance will get an IP address of the tenant >>>>>>> network. By assigning a floating IP you will be able to access it through >>>>>>> an IP address from your physical network segment. >>>>>>> >>>>>>> [1] >>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi wrote: >>>>>>> >>>>>>>> Hi Marius, >>>>>>>> >>>>>>>> Here are the outputs. Is it possible to reach you on phone so >>>>>>>> that I can explain more than email. You can call me at 650 849 3915 >>>>>>>> or let me know your number. >>>>>>>> >>>>>>>> #ip a >>>>>>>> >>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>>>>>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>>>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>>>>>> inet 127.0.0.1/8 scope host lo >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> inet6 ::1/128 scope host >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> 2: eno1: mtu 1500 qdisc mq state >>>>>>>> UP qlen 1000 >>>>>>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>>>>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> 3: eno2: mtu 1500 qdisc mq >>>>>>>> state DOWN qlen 1000 >>>>>>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>>>>>> 4: eno3: mtu 1500 qdisc mq >>>>>>>> state DOWN qlen 1000 >>>>>>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>>>>>> 5: eno4: mtu 1500 qdisc mq >>>>>>>> state DOWN qlen 1000 >>>>>>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>>>>>> 6: ens1f0: mtu 1500 qdisc mq >>>>>>>> state DOWN qlen 1000 >>>>>>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>> 7: ens1f1: mtu 1500 qdisc mq >>>>>>>> state DOWN qlen 1000 >>>>>>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>>>>>> 8: ens2f0: mtu 1500 qdisc mq >>>>>>>> state DOWN qlen 1000 >>>>>>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>>>>>> 9: ens2f1: mtu 1500 qdisc mq >>>>>>>> state DOWN qlen 1000 >>>>>>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>>>>>> 10: ovs-system: mtu 1500 qdisc noop state DOWN >>>>>>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>>>>>> 11: br-ex: mtu 1500 qdisc noqueue >>>>>>>> state UNKNOWN >>>>>>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>>>>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>>>>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>>>>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>>>>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>>>>>> 17: qbr63bd6704-47: mtu 1500 >>>>>>>> qdisc noqueue state UP >>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> 18: qvo63bd6704-47: mtu >>>>>>>> 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>>>>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>> 19: qvb63bd6704-47: mtu >>>>>>>> 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>> 22: tap63bd6704-47: mtu 1500 >>>>>>>> qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>>>>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>>>>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>>>>>> valid_lft forever preferred_lft forever >>>>>>>> >>>>>>>> # ovs-vsctl show >>>>>>>> >>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>>>>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>>>>>> Bridge br-ex >>>>>>>> Port br-ex >>>>>>>> Interface br-ex >>>>>>>> type: internal >>>>>>>> Port "qg-c3a1b534-36" >>>>>>>> Interface "qg-c3a1b534-36" >>>>>>>> type: internal >>>>>>>> Bridge br-int >>>>>>>> fail_mode: secure >>>>>>>> Port patch-tun >>>>>>>> Interface patch-tun >>>>>>>> type: patch >>>>>>>> options: {peer=patch-int} >>>>>>>> Port "tape386c0cb-d8" >>>>>>>> tag: 1 >>>>>>>> Interface "tape386c0cb-d8" >>>>>>>> type: internal >>>>>>>> Port br-int >>>>>>>> Interface br-int >>>>>>>> type: internal >>>>>>>> Port "qvo63bd6704-47" >>>>>>>> tag: 1 >>>>>>>> Interface "qvo63bd6704-47" >>>>>>>> Port "tap44dd465f-d4" >>>>>>>> tag: 4095 >>>>>>>> Interface "tap44dd465f-d4" >>>>>>>> type: internal >>>>>>>> Port "qr-e0ac3c25-2b" >>>>>>>> tag: 2 >>>>>>>> Interface "qr-e0ac3c25-2b" >>>>>>>> type: internal >>>>>>>> Bridge br-tun >>>>>>>> Port br-tun >>>>>>>> Interface br-tun >>>>>>>> type: internal >>>>>>>> Port patch-int >>>>>>>> Interface patch-int >>>>>>>> type: patch >>>>>>>> options: {peer=patch-tun} >>>>>>>> ovs_version: ?2.1.3" >>>>>>>> >>>>>>>> # neutron net-list >>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>>>>>>> >>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>> | id | name | subnets >>>>>>>> | >>>>>>>> >>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>>>>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>>>>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>>>>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>>>>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>>>>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>>>>>> >>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>> >>>>>>>> # neutron subnet-list >>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>> subnet-list >>>>>>>> >>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>> | id | name | cidr >>>>>>>> | allocation_pools | >>>>>>>> >>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>>>>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} >>>>>>>> | >>>>>>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | >>>>>>>> 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} >>>>>>>> | >>>>>>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>>>>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": >>>>>>>> "10.48.146.120"} | >>>>>>>> >>>>>>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>>>>>> >>>>>>>> #neutron router-list >>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>> router-list >>>>>>>> >>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> | id | name | >>>>>>>> external_gateway_info >>>>>>>> >>>>>>>> | distributed | ha | >>>>>>>> >>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>>>>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>>>>>> False | False | >>>>>>>> >>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>>>>>> >>>>>>>> In my system I have IP address for BR-ex and ENO1 (interface >>>>>>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>>>>>> from my network to reach to this host ? Probably its a dump question. >>>>>>>> >>>>>>>> Here are the outputs. >>>>>>>> >>>>>>>> br-ex: flags=4163 mtu 1500 >>>>>>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>>>>>> 10.48.146.255 >>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>>>>>> 0x20 >>>>>>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>>>>>> RX packets 10 bytes 864 (864.0 B) >>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>> TX packets 25 bytes 3767 (3.6 KiB) >>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>> >>>>>>>> br-int: flags=4098 mtu 1500 >>>>>>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>>>>>> RX packets 135 bytes 7574 (7.3 KiB) >>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>> >>>>>>>> br-tun: flags=4098 mtu 1500 >>>>>>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>>>>>> RX packets 0 bytes 0 (0.0 B) >>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>> >>>>>>>> eno1: flags=4163 mtu 1500 >>>>>>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>>>>>> 10.48.146.255 >>>>>>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>>>>>> 0x20 >>>>>>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>>>>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>> device interrupt 32 >>>>>>>> >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Rushi. >>>>>>>> >>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>> >>>>>>>> >>>>>>>> From: Marius Cornea >>>>>>>> Date: Friday, January 9, 2015 at 1:46 PM >>>>>>>> To: SAP SAP >>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>> openstack. >>>>>>>> >>>>>>>> Hi Rushi, >>>>>>>> >>>>>>>> Can you provide the output of the following commands on your node >>>>>>>> ? >>>>>>>> >>>>>>>> # ip a >>>>>>>> # ovs-vsctl show >>>>>>>> # neutron net-list >>>>>>>> # neutron subnet-list >>>>>>>> # neutron router-list >>>>>>>> >>>>>>>> Please note that only the br-ex bridge requires an IP address, >>>>>>>> the interface that's part of it shouldn't have one assigned. Also the >>>>>>>> floating IP addresses will be used for DNAT on the tenant router. You can >>>>>>>> check the documentation here[1] that describes the use of floating IPs. >>>>>>>> >>>>>>>> You can also check the upstream documentation[2] on how to create >>>>>>>> the networks. >>>>>>>> >>>>>>>> [1] >>>>>>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>>>>>> [2] >>>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>>> >>>>>>>> >>>>>>>> Tnx, >>>>>>>> Marius >>>>>>>> >>>>>>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Support, >>>>>>>>> >>>>>>>>> I have a problem that a launched instance from openstack >>>>>>>>> cannot connect to SSH or PING >>>>>>>>> >>>>>>>>> First of all I have dump question whether my system should be >>>>>>>>> NOVA network or Neutron network. Well to keep everyone on the same page. >>>>>>>>> Here is my history. >>>>>>>>> >>>>>>>>> >>>>>>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>>>>>> https://openstack.redhat.com/Quickstart >>>>>>>>> 2. Then I have used the following steps for floating IP >>>>>>>>> https://openstack.redhat.com/Floating_IP_range. >>>>>>>>> >>>>>>>>> My situtation is as follows. >>>>>>>>> * Floating IP address assignment: >>>>>>>>> I have assigned a floating IP , I did follow this steps. >>>>>>>>> https://openstack.redhat.com/Floating_IP_range >>>>>>>>> >>>>>>>>> * Bridge configuration:My Ethernet device eth0(actually in >>>>>>>>> Redhat 7 it is eno1 name)is on the same bridge as the compute host >>>>>>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface >>>>>>>>> on 10.48.146.112 >>>>>>>>> >>>>>>>>> * DHCP configuration: Yes, DHCP configuration is set and Neutron >>>>>>>>> hearing and responding to DHCP >>>>>>>>> requests and the instance is getting IP from 10.48.146.113 (next >>>>>>>>> hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>>>>>> rule on default security group) >>>>>>>>> >>>>>>>>> Here is the little diagram of my system. >>>>>>>>> >>>>>>>>> Can someone help to find what is missing. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Rushi. >>>>>>>>> >>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Rdo-list mailing list >>>>>>>>> Rdo-list at redhat.com >>>>>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 01:03:38 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:03:38 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: From marius at remote-lab.net Sat Jan 10 01:12:21 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 02:12:21 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: hmm.. what about 'neutron floatingip-list' -> get floatingip_id try 'neutron floatingip-associate {floatingip_id} 1939479b-78d7-4d7a-94da-006ef732e6d7' On Sat, Jan 10, 2015 at 2:03 AM, Ns, Rushi wrote: > Here is it > > [root at lspal117 tmp(keystone_admin)]# neutron port-list > > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | id | name | mac_address | > fixed_ips > | > > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.2"} | > | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.1"} | > | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.114"} | > | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.113"} | > | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.3"} | > > +--------------------------------------+------+-------------------+???????????????????????????????????????????+ > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM > > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > What does 'neutron port-list' show ? > > On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi wrote: > >> I did that, launch instance got IP: 192.168.1.2 then I did floating_IP >> which I got 10.48.146.114 , however I cannot assign to the instance as >> there are no ports avilable.? >> >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 4:52 PM >> >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Next launch an instance with demo-net attached. Then assign it a >> floating IP. You should get 10.48.146.114 as the floating IP. >> >> On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi wrote: >> >>> Thanks, I did this step . So what is next ? Sorry to bother but you >>> are really a life saver to me (thanks to you a ton) as well kashyap . >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 4:46 PM >>> To: SAP SAP >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> neutron net-create public --router:external=True >>> neutron subnet-create public 10.48.146.0/24 --name vlan >>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>> --gateway 10.48.146.1 >>> >>> neutron net-create demo-net >>> neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 >>> 192.168.1.0/24 >>> >>> neutron router-create demo-router >>> neutron router-interface-add demo-router demo-subnet >>> neutron router-gateway-set demo-router public >>> >>> >>> On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi wrote: >>> >>>> I have deleted all network (admin) and tenant as I wanted your >>>> guidance to do further >>>> >>>> Can you help to give steps to add the network again (10.48.146.0/24) >>>> and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 4:27 PM >>>> >>>> To: SAP SAP >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> Let's keep the troubleshooting steps on the list. What's the output >>>> of 'nova list' ? >>>> >>>> On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi wrote: >>>> >>>>> Yes, I did boot the instance but its getting 10.48.146.4 address >>>>> rather 192.168.*** that you gave me ? I can logon to the instance console >>>>> 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from >>>>> host? >>>>> >>>>> Is it possible I share my screen, so that you can guide me what >>>>> wrong thing that stops and bother me ? >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: Marius Cornea >>>>> Date: Friday, January 9, 2015 at 4:18 PM >>>>> >>>>> To: SAP SAP >>>>> Cc: rdo-list >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> Did you boot the instance with the demo-net attached ? >>>>> >>>>> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: >>>>> >>>>>> I can?t assign a port to the floating ip . I don?t? see any ports >>>>>> available ? >>>>>> >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> From: Marius Cornea >>>>>> Date: Friday, January 9, 2015 at 4:06 PM >>>>>> >>>>>> To: SAP SAP >>>>>> Cc: rdo-list >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> You've already defined router1 which is already connected to the >>>>>> external network. You can use that. ext-net is the 'public' network in your >>>>>> case. >>>>>> >>>>>> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: >>>>>> >>>>>>> I can?t run this command >>>>>>> >>>>>>> >>>>>>> $ neutron router-gateway-set demo-router ext-net >>>>>>> >>>>>>> Its getting error (ext-net not found) ? What is the ext-net in >>>>>>> this case ? >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> From: , SAP SAP >>>>>>> Date: Friday, January 9, 2015 at 3:58 PM >>>>>>> >>>>>>> To: Marius Cornea >>>>>>> Cc: rdo-list >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> Ok I did the folowing steps for tenant. >>>>>>> >>>>>>> 1) neutron net-create demo-net >>>>>>> 2) neutron subnet-create demo-net --name demo-subnet --gateway >>>>>>> 10.48.146.1 10.48.146.0/24 >>>>>>> 3) neutron router-create demo-router >>>>>>> 4) neutron router-interface-add demo-router demo-subnet >>>>>>> >>>>>>> Anything left .? >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> From: , SAP SAP >>>>>>> Date: Friday, January 9, 2015 at 3:55 PM >>>>>>> To: Marius Cornea >>>>>>> Cc: rdo-list >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> Hi Marius, >>>>>>> >>>>>>> Yes, I can ping 10.48.146.113 (gateway) from the host , can you >>>>>>> provide the comamnds or link to create tenant network, subjet and attach to >>>>>>> router ? >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> From: Marius Cornea >>>>>>> Date: Friday, January 9, 2015 at 3:48 PM >>>>>>> To: SAP SAP >>>>>>> Cc: rdo-list >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> Can you ping 10.48.146.113 from your network? You also need to >>>>>>> create a tenant network, subnet and attach it to the router. Boot the >>>>>>> instance with the tenant network attached and then assign it the floating >>>>>>> IP. >>>>>>> >>>>>>> >>>>>>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Marius, >>>>>>>> >>>>>>>> I did this first and now can see the BR-ex is the same IP as my >>>>>>>> eno1 interface , you are right I lost first while doing the first >>>>>>>> command(ip addr del 10.48.146.77/24 dev eno1) and then conneting >>>>>>>> to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also >>>>>>>> changed the IP address of br-ex to 10.48.146.77) >>>>>>>> >>>>>>>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>>> eno1 >>>>>>>> >>>>>>>> Then after I removed all the routers, networks and interfaces >>>>>>>> from openstack and ran the following 4 commands. >>>>>>>> >>>>>>>> 1) source /root/keystonerc_admin >>>>>>>> 2) neutron net-create public --router:external=True >>>>>>>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>>>>>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>>>>>> --gateway 10.48.146.1 >>>>>>>> 4) neutron router-create router1 >>>>>>>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>>>>>>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>>>>>>> 6) neutron floatingip-create public >>>>>>>> >>>>>>>> The above command generated a floating IP 10.48.146.115 >>>>>>>> >>>>>>>> Then I spin up a new instance and it got IP assigned >>>>>>>> automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : >>>>>>>> 10.48.146.115 ? >>>>>>>> >>>>>>>> Here are the screenshots >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>>>>>>> >>>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>>> | id | name | subnets >>>>>>>> | >>>>>>>> >>>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>>>>>>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>>>>>>> >>>>>>>> +--------------------------------------+--------+??????????????????????????+ >>>>>>>> >>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>>>>>>> >>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>> | id | name | cidr | >>>>>>>> allocation_pools | >>>>>>>> >>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>>>>>>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>>>>>>> >>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>> >>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>>>>>>> >>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> | id | name | >>>>>>>> external_gateway_info >>>>>>>> >>>>>>>> | distributed | ha | >>>>>>>> >>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>>>>>>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>>>>>>> False | False | >>>>>>>> >>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> >>>>>>>> Any ideas what is going wrong, I still can?t ping or ssh to that >>>>>>>> IP address and its not listening anywhere ? >>>>>>>> >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Rushi. >>>>>>>> >>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>> >>>>>>>> >>>>>>>> From: Marius Cornea >>>>>>>> Date: Friday, January 9, 2015 at 2:30 PM >>>>>>>> To: SAP SAP , rdo-list >>>>>>>> >>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>> openstack. >>>>>>>> >>>>>>>> As Kashyap kindly suggested we're not a support line and >>>>>>>> information here should be available for all the community members. First, >>>>>>>> I don't see how you can ping the br-ex IP address from an external network >>>>>>>> since it doesn't contain any physical interface. Make sure that >>>>>>>> 10.48.146.112 isn't used by other host on you network segment. You can do >>>>>>>> the following to remove the ip address from the physical interface and add >>>>>>>> it to the br-ex bridge. Please make sure that you've got console access to >>>>>>>> the server before doing this as you may lose connectivity. >>>>>>>> >>>>>>>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>>> eno1 >>>>>>>> >>>>>>>> You should then follow the documentation[1] to recreate the >>>>>>>> public/tenant networks and router. In your >>>>>>>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>>>>>>> 10.48.146.0/24 network. Let's say you wish to allocate IP >>>>>>>> addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack >>>>>>>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>>>>>>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>>>>>>> what 'ip r | grep default | awk {'print $3'}' outputs >>>>>>>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>>>>>>> >>>>>>>> Note that the instance will get an IP address of the tenant >>>>>>>> network. By assigning a floating IP you will be able to access it through >>>>>>>> an IP address from your physical network segment. >>>>>>>> >>>>>>>> [1] >>>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Marius, >>>>>>>>> >>>>>>>>> Here are the outputs. Is it possible to reach you on phone so >>>>>>>>> that I can explain more than email. You can call me at 650 849 >>>>>>>>> 3915 or let me know your number. >>>>>>>>> >>>>>>>>> #ip a >>>>>>>>> >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>>>>>>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>>>>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>>>>>>> inet 127.0.0.1/8 scope host lo >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> inet6 ::1/128 scope host >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 2: eno1: mtu 1500 qdisc mq state >>>>>>>>> UP qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 3: eno2: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 4: eno3: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 5: eno4: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 6: ens1f0: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 7: ens1f1: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 8: ens2f0: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 9: ens2f1: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 10: ovs-system: mtu 1500 qdisc noop state >>>>>>>>> DOWN >>>>>>>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 11: br-ex: mtu 1500 qdisc >>>>>>>>> noqueue state UNKNOWN >>>>>>>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>>>>>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>>>>>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>>>>>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 17: qbr63bd6704-47: mtu 1500 >>>>>>>>> qdisc noqueue state UP >>>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 18: qvo63bd6704-47: mtu >>>>>>>>> 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>>>>>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 19: qvb63bd6704-47: mtu >>>>>>>>> 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>>> 22: tap63bd6704-47: mtu 1500 >>>>>>>>> qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>>>>>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> >>>>>>>>> # ovs-vsctl show >>>>>>>>> >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>>>>>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>>>>>>> Bridge br-ex >>>>>>>>> Port br-ex >>>>>>>>> Interface br-ex >>>>>>>>> type: internal >>>>>>>>> Port "qg-c3a1b534-36" >>>>>>>>> Interface "qg-c3a1b534-36" >>>>>>>>> type: internal >>>>>>>>> Bridge br-int >>>>>>>>> fail_mode: secure >>>>>>>>> Port patch-tun >>>>>>>>> Interface patch-tun >>>>>>>>> type: patch >>>>>>>>> options: {peer=patch-int} >>>>>>>>> Port "tape386c0cb-d8" >>>>>>>>> tag: 1 >>>>>>>>> Interface "tape386c0cb-d8" >>>>>>>>> type: internal >>>>>>>>> Port br-int >>>>>>>>> Interface br-int >>>>>>>>> type: internal >>>>>>>>> Port "qvo63bd6704-47" >>>>>>>>> tag: 1 >>>>>>>>> Interface "qvo63bd6704-47" >>>>>>>>> Port "tap44dd465f-d4" >>>>>>>>> tag: 4095 >>>>>>>>> Interface "tap44dd465f-d4" >>>>>>>>> type: internal >>>>>>>>> Port "qr-e0ac3c25-2b" >>>>>>>>> tag: 2 >>>>>>>>> Interface "qr-e0ac3c25-2b" >>>>>>>>> type: internal >>>>>>>>> Bridge br-tun >>>>>>>>> Port br-tun >>>>>>>>> Interface br-tun >>>>>>>>> type: internal >>>>>>>>> Port patch-int >>>>>>>>> Interface patch-int >>>>>>>>> type: patch >>>>>>>>> options: {peer=patch-tun} >>>>>>>>> ovs_version: ?2.1.3" >>>>>>>>> >>>>>>>>> # neutron net-list >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>> | id | name | subnets >>>>>>>>> | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>>>>>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>>>>>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>>>>>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>>>>>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>>>>>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>> >>>>>>>>> # neutron subnet-list >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>>> subnet-list >>>>>>>>> >>>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>>> | id | name | cidr >>>>>>>>> | allocation_pools | >>>>>>>>> >>>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>>>>>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": >>>>>>>>> "172.24.4.238"} | >>>>>>>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | >>>>>>>>> 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} >>>>>>>>> | >>>>>>>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>>>>>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": >>>>>>>>> "10.48.146.120"} | >>>>>>>>> >>>>>>>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>>>>>>> >>>>>>>>> #neutron router-list >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>>> router-list >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>> | id | name | >>>>>>>>> external_gateway_info >>>>>>>>> >>>>>>>>> | distributed | ha | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>>>>>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>>>>>>> False | False | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>>>>>>> >>>>>>>>> In my system I have IP address for BR-ex and ENO1 (interface >>>>>>>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>>>>>>> from my network to reach to this host ? Probably its a dump question. >>>>>>>>> >>>>>>>>> Here are the outputs. >>>>>>>>> >>>>>>>>> br-ex: flags=4163 mtu 1500 >>>>>>>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>>>>>>> 10.48.146.255 >>>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>>>>>>> 0x20 >>>>>>>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>>>>>>> RX packets 10 bytes 864 (864.0 B) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 25 bytes 3767 (3.6 KiB) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> >>>>>>>>> br-int: flags=4098 mtu 1500 >>>>>>>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>>>>>>> RX packets 135 bytes 7574 (7.3 KiB) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> >>>>>>>>> br-tun: flags=4098 mtu 1500 >>>>>>>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>>>>>>> RX packets 0 bytes 0 (0.0 B) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> >>>>>>>>> eno1: flags=4163 mtu 1500 >>>>>>>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>>>>>>> 10.48.146.255 >>>>>>>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>>>>>>> 0x20 >>>>>>>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>>>>>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> device interrupt 32 >>>>>>>>> >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Rushi. >>>>>>>>> >>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>> >>>>>>>>> >>>>>>>>> From: Marius Cornea >>>>>>>>> Date: Friday, January 9, 2015 at 1:46 PM >>>>>>>>> To: SAP SAP >>>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>>> openstack. >>>>>>>>> >>>>>>>>> Hi Rushi, >>>>>>>>> >>>>>>>>> Can you provide the output of the following commands on your >>>>>>>>> node ? >>>>>>>>> >>>>>>>>> # ip a >>>>>>>>> # ovs-vsctl show >>>>>>>>> # neutron net-list >>>>>>>>> # neutron subnet-list >>>>>>>>> # neutron router-list >>>>>>>>> >>>>>>>>> Please note that only the br-ex bridge requires an IP address, >>>>>>>>> the interface that's part of it shouldn't have one assigned. Also the >>>>>>>>> floating IP addresses will be used for DNAT on the tenant router. You can >>>>>>>>> check the documentation here[1] that describes the use of floating IPs. >>>>>>>>> >>>>>>>>> You can also check the upstream documentation[2] on how to >>>>>>>>> create the networks. >>>>>>>>> >>>>>>>>> [1] >>>>>>>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>>>>>>> [2] >>>>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>>>> >>>>>>>>> >>>>>>>>> Tnx, >>>>>>>>> Marius >>>>>>>>> >>>>>>>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Support, >>>>>>>>>> >>>>>>>>>> I have a problem that a launched instance from openstack >>>>>>>>>> cannot connect to SSH or PING >>>>>>>>>> >>>>>>>>>> First of all I have dump question whether my system should be >>>>>>>>>> NOVA network or Neutron network. Well to keep everyone on the same page. >>>>>>>>>> Here is my history. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>>>>>>> https://openstack.redhat.com/Quickstart >>>>>>>>>> 2. Then I have used the following steps for floating IP >>>>>>>>>> https://openstack.redhat.com/Floating_IP_range. >>>>>>>>>> >>>>>>>>>> My situtation is as follows. >>>>>>>>>> * Floating IP address assignment: >>>>>>>>>> I have assigned a floating IP , I did follow this steps. >>>>>>>>>> https://openstack.redhat.com/Floating_IP_range >>>>>>>>>> >>>>>>>>>> * Bridge configuration:My Ethernet device eth0(actually in >>>>>>>>>> Redhat 7 it is eno1 name)is on the same bridge as the compute host >>>>>>>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface >>>>>>>>>> on 10.48.146.112 >>>>>>>>>> >>>>>>>>>> * DHCP configuration: Yes, DHCP configuration is set and >>>>>>>>>> Neutron hearing and responding to DHCP >>>>>>>>>> requests and the instance is getting IP from 10.48.146.113 (next >>>>>>>>>> hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>>>>>>> rule on default security group) >>>>>>>>>> >>>>>>>>>> Here is the little diagram of my system. >>>>>>>>>> >>>>>>>>>> Can someone help to find what is missing. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Best Regards, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Rushi. >>>>>>>>>> >>>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Rdo-list mailing list >>>>>>>>>> Rdo-list at redhat.com >>>>>>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 01:12:47 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:12:47 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Hi Marius, Sorry I can assign the floating ip to the instnace (demo user launched insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping other instance 192.168.1.4 ? Can you help in this final step what is missing > [cid:0E7F5284-9B90-46DA-B1CE-824110D267B8] root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.115"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.4"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: From rushi.ns at sap.com Sat Jan 10 01:17:21 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:17:21 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Here is the console, I can ping gateway of my host : 10.48.146.1 and others but I cannot ssh to that instance from oopensetack host. [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 10.48.146.115 ssh: connect to host 10.48.146.115 port 22: Connection refused [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 192.168.1.4 [cid:9B3B10A4-4C8D-472C-9B21-C82D718CC6E0] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:12 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Sorry I can assign the floating ip to the instnace (demo user launched insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping other instance 192.168.1.4 ? Can you help in this final step what is missing > [cid:0E7F5284-9B90-46DA-B1CE-824110D267B8] root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.115"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.4"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png URL: From rushi.ns at sap.com Sat Jan 10 01:18:10 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:18:10 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Here are my allowed port list but I can?t ping or I can?t ssh ? [cid:81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:17 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is the console, I can ping gateway of my host : 10.48.146.1 and others but I cannot ssh to that instance from oopensetack host. [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 10.48.146.115 ssh: connect to host 10.48.146.115 port 22: Connection refused [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 192.168.1.4 [cid:9B3B10A4-4C8D-472C-9B21-C82D718CC6E0] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:12 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Sorry I can assign the floating ip to the instnace (demo user launched insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping other instance 192.168.1.4 ? Can you help in this final step what is missing > [cid:0E7F5284-9B90-46DA-B1CE-824110D267B8] root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.115"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.4"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png Type: image/png Size: 61042 bytes Desc: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png URL: From marius at remote-lab.net Sat Jan 10 01:23:01 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 02:23:01 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: I see that you get a 'connection refused' message which means that the VM responds. Is the ssh service running on the VM or is there any firewall on the VM that might prevent connectivity? You could run tcpdump inside the VM to see if any of your packets reach it. On Sat, Jan 10, 2015 at 2:18 AM, Ns, Rushi wrote: > Here are my allowed port list but I can?t ping or I can?t ssh ? > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: , SAP SAP > Date: Friday, January 9, 2015 at 5:17 PM > > To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Here is the console, I can ping gateway of my host : 10.48.146.1 and > others but I cannot ssh to that instance from oopensetack host. > > > [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem > 10.48.146.115 > ssh: connect to host 10.48.146.115 port 22: Connection refused > > > [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem > 192.168.1.4 > > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: , SAP SAP > Date: Friday, January 9, 2015 at 5:12 PM > To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Hi Marius, > > Sorry I can assign the floating ip to the instnace (demo user launched > insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ > 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping > other instance 192.168.1.4 ? > > Can you help in this final step what is missing > > > > > > root at lspal117 tmp(keystone_admin)]# neutron port-list > > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | id | name | mac_address | > fixed_ips > | > > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.2"} | > | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.1"} | > | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.114"} | > | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.115"} | > | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.113"} | > | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.4"} | > | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.3"} | > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM > To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Here is it > > [root at lspal117 tmp(keystone_admin)]# neutron port-list > > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | id | name | mac_address | > fixed_ips > | > > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.2"} | > | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.1"} | > | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.114"} | > | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.113"} | > | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.3"} | > > +--------------------------------------+------+-------------------+???????????????????????????????????????????+ > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > What does 'neutron port-list' show ? > > On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi wrote: > >> I did that, launch instance got IP: 192.168.1.2 then I did floating_IP >> which I got 10.48.146.114 , however I cannot assign to the instance as >> there are no ports avilable.? >> >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 4:52 PM >> >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Next launch an instance with demo-net attached. Then assign it a >> floating IP. You should get 10.48.146.114 as the floating IP. >> >> On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi wrote: >> >>> Thanks, I did this step . So what is next ? Sorry to bother but you >>> are really a life saver to me (thanks to you a ton) as well kashyap . >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 4:46 PM >>> To: SAP SAP >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> neutron net-create public --router:external=True >>> neutron subnet-create public 10.48.146.0/24 --name vlan >>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>> --gateway 10.48.146.1 >>> >>> neutron net-create demo-net >>> neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 >>> 192.168.1.0/24 >>> >>> neutron router-create demo-router >>> neutron router-interface-add demo-router demo-subnet >>> neutron router-gateway-set demo-router public >>> >>> >>> On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi wrote: >>> >>>> I have deleted all network (admin) and tenant as I wanted your >>>> guidance to do further >>>> >>>> Can you help to give steps to add the network again (10.48.146.0/24) >>>> and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 4:27 PM >>>> >>>> To: SAP SAP >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> Let's keep the troubleshooting steps on the list. What's the output >>>> of 'nova list' ? >>>> >>>> On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi wrote: >>>> >>>>> Yes, I did boot the instance but its getting 10.48.146.4 address >>>>> rather 192.168.*** that you gave me ? I can logon to the instance console >>>>> 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from >>>>> host? >>>>> >>>>> Is it possible I share my screen, so that you can guide me what >>>>> wrong thing that stops and bother me ? >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: Marius Cornea >>>>> Date: Friday, January 9, 2015 at 4:18 PM >>>>> >>>>> To: SAP SAP >>>>> Cc: rdo-list >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> Did you boot the instance with the demo-net attached ? >>>>> >>>>> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: >>>>> >>>>>> I can?t assign a port to the floating ip . I don?t? see any ports >>>>>> available ? >>>>>> >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> From: Marius Cornea >>>>>> Date: Friday, January 9, 2015 at 4:06 PM >>>>>> >>>>>> To: SAP SAP >>>>>> Cc: rdo-list >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> You've already defined router1 which is already connected to the >>>>>> external network. You can use that. ext-net is the 'public' network in your >>>>>> case. >>>>>> >>>>>> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: >>>>>> >>>>>>> I can?t run this command >>>>>>> >>>>>>> >>>>>>> $ neutron router-gateway-set demo-router ext-net >>>>>>> >>>>>>> Its getting error (ext-net not found) ? What is the ext-net in >>>>>>> this case ? >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> From: , SAP SAP >>>>>>> Date: Friday, January 9, 2015 at 3:58 PM >>>>>>> >>>>>>> To: Marius Cornea >>>>>>> Cc: rdo-list >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> Ok I did the folowing steps for tenant. >>>>>>> >>>>>>> 1) neutron net-create demo-net >>>>>>> 2) neutron subnet-create demo-net --name demo-subnet --gateway >>>>>>> 10.48.146.1 10.48.146.0/24 >>>>>>> 3) neutron router-create demo-router >>>>>>> 4) neutron router-interface-add demo-router demo-subnet >>>>>>> >>>>>>> Anything left .? >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> From: , SAP SAP >>>>>>> Date: Friday, January 9, 2015 at 3:55 PM >>>>>>> To: Marius Cornea >>>>>>> Cc: rdo-list >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> Hi Marius, >>>>>>> >>>>>>> Yes, I can ping 10.48.146.113 (gateway) from the host , can you >>>>>>> provide the comamnds or link to create tenant network, subjet and attach to >>>>>>> router ? >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> From: Marius Cornea >>>>>>> Date: Friday, January 9, 2015 at 3:48 PM >>>>>>> To: SAP SAP >>>>>>> Cc: rdo-list >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> Can you ping 10.48.146.113 from your network? You also need to >>>>>>> create a tenant network, subnet and attach it to the router. Boot the >>>>>>> instance with the tenant network attached and then assign it the floating >>>>>>> IP. >>>>>>> >>>>>>> >>>>>>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Marius, >>>>>>>> >>>>>>>> I did this first and now can see the BR-ex is the same IP as my >>>>>>>> eno1 interface , you are right I lost first while doing the first >>>>>>>> command(ip addr del 10.48.146.77/24 dev eno1) and then conneting >>>>>>>> to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also >>>>>>>> changed the IP address of br-ex to 10.48.146.77) >>>>>>>> >>>>>>>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>>> eno1 >>>>>>>> >>>>>>>> Then after I removed all the routers, networks and interfaces >>>>>>>> from openstack and ran the following 4 commands. >>>>>>>> >>>>>>>> 1) source /root/keystonerc_admin >>>>>>>> 2) neutron net-create public --router:external=True >>>>>>>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>>>>>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>>>>>> --gateway 10.48.146.1 >>>>>>>> 4) neutron router-create router1 >>>>>>>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>>>>>>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>>>>>>> 6) neutron floatingip-create public >>>>>>>> >>>>>>>> The above command generated a floating IP 10.48.146.115 >>>>>>>> >>>>>>>> Then I spin up a new instance and it got IP assigned >>>>>>>> automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : >>>>>>>> 10.48.146.115 ? >>>>>>>> >>>>>>>> Here are the screenshots >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>>>>>>> >>>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>>> | id | name | subnets >>>>>>>> | >>>>>>>> >>>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>>>>>>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>>>>>>> >>>>>>>> +--------------------------------------+--------+??????????????????????????+ >>>>>>>> >>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>>>>>>> >>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>> | id | name | cidr | >>>>>>>> allocation_pools | >>>>>>>> >>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>>>>>>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>>>>>>> >>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>> >>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>>>>>>> >>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> | id | name | >>>>>>>> external_gateway_info >>>>>>>> >>>>>>>> | distributed | ha | >>>>>>>> >>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>>>>>>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>>>>>>> False | False | >>>>>>>> >>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>> >>>>>>>> Any ideas what is going wrong, I still can?t ping or ssh to that >>>>>>>> IP address and its not listening anywhere ? >>>>>>>> >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Rushi. >>>>>>>> >>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>> >>>>>>>> >>>>>>>> From: Marius Cornea >>>>>>>> Date: Friday, January 9, 2015 at 2:30 PM >>>>>>>> To: SAP SAP , rdo-list >>>>>>>> >>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>> openstack. >>>>>>>> >>>>>>>> As Kashyap kindly suggested we're not a support line and >>>>>>>> information here should be available for all the community members. First, >>>>>>>> I don't see how you can ping the br-ex IP address from an external network >>>>>>>> since it doesn't contain any physical interface. Make sure that >>>>>>>> 10.48.146.112 isn't used by other host on you network segment. You can do >>>>>>>> the following to remove the ip address from the physical interface and add >>>>>>>> it to the br-ex bridge. Please make sure that you've got console access to >>>>>>>> the server before doing this as you may lose connectivity. >>>>>>>> >>>>>>>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>>> eno1 >>>>>>>> >>>>>>>> You should then follow the documentation[1] to recreate the >>>>>>>> public/tenant networks and router. In your >>>>>>>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>>>>>>> 10.48.146.0/24 network. Let's say you wish to allocate IP >>>>>>>> addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack >>>>>>>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>>>>>>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>>>>>>> what 'ip r | grep default | awk {'print $3'}' outputs >>>>>>>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>>>>>>> >>>>>>>> Note that the instance will get an IP address of the tenant >>>>>>>> network. By assigning a floating IP you will be able to access it through >>>>>>>> an IP address from your physical network segment. >>>>>>>> >>>>>>>> [1] >>>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Marius, >>>>>>>>> >>>>>>>>> Here are the outputs. Is it possible to reach you on phone so >>>>>>>>> that I can explain more than email. You can call me at 650 849 >>>>>>>>> 3915 or let me know your number. >>>>>>>>> >>>>>>>>> #ip a >>>>>>>>> >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>>>>>>> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN >>>>>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>>>>>>> inet 127.0.0.1/8 scope host lo >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> inet6 ::1/128 scope host >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 2: eno1: mtu 1500 qdisc mq state >>>>>>>>> UP qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 3: eno2: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 4: eno3: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 5: eno4: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 6: ens1f0: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 7: ens1f1: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 8: ens2f0: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 9: ens2f1: mtu 1500 qdisc mq >>>>>>>>> state DOWN qlen 1000 >>>>>>>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 10: ovs-system: mtu 1500 qdisc noop state >>>>>>>>> DOWN >>>>>>>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 11: br-ex: mtu 1500 qdisc >>>>>>>>> noqueue state UNKNOWN >>>>>>>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>>>>>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>>>>>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>>>>>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 17: qbr63bd6704-47: mtu 1500 >>>>>>>>> qdisc noqueue state UP >>>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> 18: qvo63bd6704-47: mtu >>>>>>>>> 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>>>>>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>>> 19: qvb63bd6704-47: mtu >>>>>>>>> 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>>> 22: tap63bd6704-47: mtu 1500 >>>>>>>>> qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>>>>>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>>>>>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>> >>>>>>>>> # ovs-vsctl show >>>>>>>>> >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>>>>>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>>>>>>> Bridge br-ex >>>>>>>>> Port br-ex >>>>>>>>> Interface br-ex >>>>>>>>> type: internal >>>>>>>>> Port "qg-c3a1b534-36" >>>>>>>>> Interface "qg-c3a1b534-36" >>>>>>>>> type: internal >>>>>>>>> Bridge br-int >>>>>>>>> fail_mode: secure >>>>>>>>> Port patch-tun >>>>>>>>> Interface patch-tun >>>>>>>>> type: patch >>>>>>>>> options: {peer=patch-int} >>>>>>>>> Port "tape386c0cb-d8" >>>>>>>>> tag: 1 >>>>>>>>> Interface "tape386c0cb-d8" >>>>>>>>> type: internal >>>>>>>>> Port br-int >>>>>>>>> Interface br-int >>>>>>>>> type: internal >>>>>>>>> Port "qvo63bd6704-47" >>>>>>>>> tag: 1 >>>>>>>>> Interface "qvo63bd6704-47" >>>>>>>>> Port "tap44dd465f-d4" >>>>>>>>> tag: 4095 >>>>>>>>> Interface "tap44dd465f-d4" >>>>>>>>> type: internal >>>>>>>>> Port "qr-e0ac3c25-2b" >>>>>>>>> tag: 2 >>>>>>>>> Interface "qr-e0ac3c25-2b" >>>>>>>>> type: internal >>>>>>>>> Bridge br-tun >>>>>>>>> Port br-tun >>>>>>>>> Interface br-tun >>>>>>>>> type: internal >>>>>>>>> Port patch-int >>>>>>>>> Interface patch-int >>>>>>>>> type: patch >>>>>>>>> options: {peer=patch-tun} >>>>>>>>> ovs_version: ?2.1.3" >>>>>>>>> >>>>>>>>> # neutron net-list >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron net-list >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>> | id | name | subnets >>>>>>>>> | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>>>>>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>>>>>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>>>>>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>>>>>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>>>>>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>> >>>>>>>>> # neutron subnet-list >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>>> subnet-list >>>>>>>>> >>>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>>> | id | name | cidr >>>>>>>>> | allocation_pools | >>>>>>>>> >>>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>>>>>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": >>>>>>>>> "172.24.4.238"} | >>>>>>>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | >>>>>>>>> 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} >>>>>>>>> | >>>>>>>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>>>>>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": >>>>>>>>> "10.48.146.120"} | >>>>>>>>> >>>>>>>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>>>>>>> >>>>>>>>> #neutron router-list >>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>>> router-list >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>> | id | name | >>>>>>>>> external_gateway_info >>>>>>>>> >>>>>>>>> | distributed | ha | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>>>>>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>>>>>>> False | False | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>>>>>>> >>>>>>>>> In my system I have IP address for BR-ex and ENO1 (interface >>>>>>>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>>>>>>> from my network to reach to this host ? Probably its a dump question. >>>>>>>>> >>>>>>>>> Here are the outputs. >>>>>>>>> >>>>>>>>> br-ex: flags=4163 mtu 1500 >>>>>>>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>>>>>>> 10.48.146.255 >>>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>>>>>>> 0x20 >>>>>>>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>>>>>>> RX packets 10 bytes 864 (864.0 B) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 25 bytes 3767 (3.6 KiB) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> >>>>>>>>> br-int: flags=4098 mtu 1500 >>>>>>>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>>>>>>> RX packets 135 bytes 7574 (7.3 KiB) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> >>>>>>>>> br-tun: flags=4098 mtu 1500 >>>>>>>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>>>>>>> RX packets 0 bytes 0 (0.0 B) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> >>>>>>>>> eno1: flags=4163 mtu 1500 >>>>>>>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>>>>>>> 10.48.146.255 >>>>>>>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>>>>>>> 0x20 >>>>>>>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>>>>>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> device interrupt 32 >>>>>>>>> >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Rushi. >>>>>>>>> >>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>> >>>>>>>>> >>>>>>>>> From: Marius Cornea >>>>>>>>> Date: Friday, January 9, 2015 at 1:46 PM >>>>>>>>> To: SAP SAP >>>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>>> openstack. >>>>>>>>> >>>>>>>>> Hi Rushi, >>>>>>>>> >>>>>>>>> Can you provide the output of the following commands on your >>>>>>>>> node ? >>>>>>>>> >>>>>>>>> # ip a >>>>>>>>> # ovs-vsctl show >>>>>>>>> # neutron net-list >>>>>>>>> # neutron subnet-list >>>>>>>>> # neutron router-list >>>>>>>>> >>>>>>>>> Please note that only the br-ex bridge requires an IP address, >>>>>>>>> the interface that's part of it shouldn't have one assigned. Also the >>>>>>>>> floating IP addresses will be used for DNAT on the tenant router. You can >>>>>>>>> check the documentation here[1] that describes the use of floating IPs. >>>>>>>>> >>>>>>>>> You can also check the upstream documentation[2] on how to >>>>>>>>> create the networks. >>>>>>>>> >>>>>>>>> [1] >>>>>>>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>>>>>>> [2] >>>>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>>>> >>>>>>>>> >>>>>>>>> Tnx, >>>>>>>>> Marius >>>>>>>>> >>>>>>>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Support, >>>>>>>>>> >>>>>>>>>> I have a problem that a launched instance from openstack >>>>>>>>>> cannot connect to SSH or PING >>>>>>>>>> >>>>>>>>>> First of all I have dump question whether my system should be >>>>>>>>>> NOVA network or Neutron network. Well to keep everyone on the same page. >>>>>>>>>> Here is my history. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>>>>>>> https://openstack.redhat.com/Quickstart >>>>>>>>>> 2. Then I have used the following steps for floating IP >>>>>>>>>> https://openstack.redhat.com/Floating_IP_range. >>>>>>>>>> >>>>>>>>>> My situtation is as follows. >>>>>>>>>> * Floating IP address assignment: >>>>>>>>>> I have assigned a floating IP , I did follow this steps. >>>>>>>>>> https://openstack.redhat.com/Floating_IP_range >>>>>>>>>> >>>>>>>>>> * Bridge configuration:My Ethernet device eth0(actually in >>>>>>>>>> Redhat 7 it is eno1 name)is on the same bridge as the compute host >>>>>>>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface >>>>>>>>>> on 10.48.146.112 >>>>>>>>>> >>>>>>>>>> * DHCP configuration: Yes, DHCP configuration is set and >>>>>>>>>> Neutron hearing and responding to DHCP >>>>>>>>>> requests and the instance is getting IP from 10.48.146.113 (next >>>>>>>>>> hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>>>>>>> rule on default security group) >>>>>>>>>> >>>>>>>>>> Here is the little diagram of my system. >>>>>>>>>> >>>>>>>>>> Can someone help to find what is missing. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Best Regards, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Rushi. >>>>>>>>>> >>>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Rdo-list mailing list >>>>>>>>>> Rdo-list at redhat.com >>>>>>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png Type: image/png Size: 61042 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: not available URL: From rushi.ns at sap.com Sat Jan 10 01:24:03 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:24:03 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: I am leaving for the day, if you can help this showstopper would be great help to me. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:18 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here are my allowed port list but I can?t ping or I can?t ssh ? [cid:81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:17 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is the console, I can ping gateway of my host : 10.48.146.1 and others but I cannot ssh to that instance from oopensetack host. [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 10.48.146.115 ssh: connect to host 10.48.146.115 port 22: Connection refused [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 192.168.1.4 [cid:9B3B10A4-4C8D-472C-9B21-C82D718CC6E0] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:12 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Sorry I can assign the floating ip to the instnace (demo user launched insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping other instance 192.168.1.4 ? Can you help in this final step what is missing > [cid:0E7F5284-9B90-46DA-B1CE-824110D267B8] root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.115"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.4"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png Type: image/png Size: 61042 bytes Desc: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png URL: From rushi.ns at sap.com Sat Jan 10 01:31:32 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:31:32 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: I did verified on the VM., No fiewall enable (this is suse create with SUSE Studio) SSH is listening on the VM and I can ssh to the local host [cid:3DBCBF54-A0DD-43A7-A793-4E902C409617] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:23 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. I see that you get a 'connection refused' message which means that the VM responds. Is the ssh service running on the VM or is there any firewall on the VM that might prevent connectivity? You could run tcpdump inside the VM to see if any of your packets reach it. On Sat, Jan 10, 2015 at 2:18 AM, Ns, Rushi > wrote: Here are my allowed port list but I can?t ping or I can?t ssh ? [cid:81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:17 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is the console, I can ping gateway of my host : 10.48.146.1 and others but I cannot ssh to that instance from oopensetack host. [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 10.48.146.115 ssh: connect to host 10.48.146.115 port 22: Connection refused [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 192.168.1.4 [cid:9B3B10A4-4C8D-472C-9B21-C82D718CC6E0] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:12 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Sorry I can assign the floating ip to the instnace (demo user launched insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping other instance 192.168.1.4 ? Can you help in this final step what is missing > [cid:0E7F5284-9B90-46DA-B1CE-824110D267B8] root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.115"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.4"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3DBCBF54-A0DD-43A7-A793-4E902C409617.png Type: image/png Size: 135378 bytes Desc: 3DBCBF54-A0DD-43A7-A793-4E902C409617.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png Type: image/png Size: 61042 bytes Desc: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: From rushi.ns at sap.com Sat Jan 10 01:44:49 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 10 Jan 2015 01:44:49 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: By the way, My openstack host is : REDHAT7 ? Do you think is there any settings on sshd preventing to connet to VM (to check to see this VM?? ssh ? ) I did checked and making sure iptables off on the openstack host ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:31 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. I did verified on the VM., No fiewall enable (this is suse create with SUSE Studio) SSH is listening on the VM and I can ssh to the local host [cid:3DBCBF54-A0DD-43A7-A793-4E902C409617] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:23 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. I see that you get a 'connection refused' message which means that the VM responds. Is the ssh service running on the VM or is there any firewall on the VM that might prevent connectivity? You could run tcpdump inside the VM to see if any of your packets reach it. On Sat, Jan 10, 2015 at 2:18 AM, Ns, Rushi > wrote: Here are my allowed port list but I can?t ping or I can?t ssh ? [cid:81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:17 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is the console, I can ping gateway of my host : 10.48.146.1 and others but I cannot ssh to that instance from oopensetack host. [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 10.48.146.115 ssh: connect to host 10.48.146.115 port 22: Connection refused [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 192.168.1.4 [cid:9B3B10A4-4C8D-472C-9B21-C82D718CC6E0] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:12 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Sorry I can assign the floating ip to the instnace (demo user launched insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping other instance 192.168.1.4 ? Can you help in this final step what is missing > [cid:0E7F5284-9B90-46DA-B1CE-824110D267B8] root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.115"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.4"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png Type: image/png Size: 61042 bytes Desc: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3DBCBF54-A0DD-43A7-A793-4E902C409617.png Type: image/png Size: 135378 bytes Desc: 3DBCBF54-A0DD-43A7-A793-4E902C409617.png URL: From marius at remote-lab.net Sat Jan 10 02:01:29 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 10 Jan 2015 03:01:29 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: Well neutron uses iptables to implement the security groups so I'm not sure what's the result of removing the iptables rules from the openstack host. Since the ssh connection to 10.48.146.115 was getting a connection refused I would have checked first the VM to see if any packets reach its interface. You could do that by 'tcpdump -i {interface_name}' inside the VM. On Sat, Jan 10, 2015 at 2:44 AM, Ns, Rushi wrote: > By the way, My openstack host is : REDHAT7 ? Do you think is there any > settings on sshd preventing to connet to VM (to check to see this VM?? ssh > ? ) > > I did checked and making sure iptables off on the openstack host ? > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: , SAP SAP > Date: Friday, January 9, 2015 at 5:31 PM > > To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > I did verified on the VM., > > No fiewall enable (this is suse create with SUSE Studio) > SSH is listening on the VM and I can ssh to the local host > > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > From: Marius Cornea > Date: Friday, January 9, 2015 at 5:23 PM > To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > I see that you get a 'connection refused' message which means that the > VM responds. Is the ssh service running on the VM or is there any firewall > on the VM that might prevent connectivity? You could run tcpdump inside the > VM to see if any of your packets reach it. > > On Sat, Jan 10, 2015 at 2:18 AM, Ns, Rushi wrote: > >> Here are my allowed port list but I can?t ping or I can?t ssh ? >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: , SAP SAP >> Date: Friday, January 9, 2015 at 5:17 PM >> >> To: Marius Cornea >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Here is the console, I can ping gateway of my host : 10.48.146.1 and >> others but I cannot ssh to that instance from oopensetack host. >> >> >> [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem >> 10.48.146.115 >> ssh: connect to host 10.48.146.115 port 22: Connection refused >> >> >> [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem >> 192.168.1.4 >> >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: , SAP SAP >> Date: Friday, January 9, 2015 at 5:12 PM >> To: Marius Cornea >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Hi Marius, >> >> Sorry I can assign the floating ip to the instnace (demo user launched >> insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ >> 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping >> other instance 192.168.1.4 ? >> >> Can you help in this final step what is missing > >> >> >> >> >> root at lspal117 tmp(keystone_admin)]# neutron port-list >> >> +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ >> | id | name | mac_address | >> fixed_ips >> | >> >> +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ >> | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.2"} | >> | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.1"} | >> | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.114"} | >> | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.115"} | >> | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.113"} | >> | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.4"} | >> | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.3"} | >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: , SAP SAP >> Date: Friday, January 9, 2015 at 5:03 PM >> To: Marius Cornea >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Here is it >> >> [root at lspal117 tmp(keystone_admin)]# neutron port-list >> >> +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ >> | id | name | mac_address | >> fixed_ips >> | >> >> +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ >> | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.2"} | >> | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.1"} | >> | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.114"} | >> | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.113"} | >> | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.3"} | >> >> +--------------------------------------+------+-------------------+???????????????????????????????????????????+ >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> From: Marius Cornea >> Date: Friday, January 9, 2015 at 5:02 PM >> To: SAP SAP >> Cc: rdo-list >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> What does 'neutron port-list' show ? >> >> On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi wrote: >> >>> I did that, launch instance got IP: 192.168.1.2 then I did >>> floating_IP which I got 10.48.146.114 , however I cannot assign to the >>> instance as there are no ports avilable.? >>> >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> From: Marius Cornea >>> Date: Friday, January 9, 2015 at 4:52 PM >>> >>> To: SAP SAP >>> Cc: rdo-list >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Next launch an instance with demo-net attached. Then assign it a >>> floating IP. You should get 10.48.146.114 as the floating IP. >>> >>> On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi wrote: >>> >>>> Thanks, I did this step . So what is next ? Sorry to bother but you >>>> are really a life saver to me (thanks to you a ton) as well kashyap . >>>> >>>> >>>> Best Regards, >>>> >>>> >>>> >>>> Rushi. >>>> >>>> Success is not a matter of being the best & winning the race. Success >>>> is a matter of handling the worst & finishing the race >>>> >>>> >>>> From: Marius Cornea >>>> Date: Friday, January 9, 2015 at 4:46 PM >>>> To: SAP SAP >>>> Cc: rdo-list >>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>> >>>> neutron net-create public --router:external=True >>>> neutron subnet-create public 10.48.146.0/24 --name vlan >>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>> --gateway 10.48.146.1 >>>> >>>> neutron net-create demo-net >>>> neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 >>>> 192.168.1.0/24 >>>> >>>> neutron router-create demo-router >>>> neutron router-interface-add demo-router demo-subnet >>>> neutron router-gateway-set demo-router public >>>> >>>> >>>> On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi wrote: >>>> >>>>> I have deleted all network (admin) and tenant as I wanted your >>>>> guidance to do further >>>>> >>>>> Can you help to give steps to add the network again (10.48.146.0/24) >>>>> and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) >>>>> >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> >>>>> Rushi. >>>>> >>>>> Success is not a matter of being the best & winning the race. Success >>>>> is a matter of handling the worst & finishing the race >>>>> >>>>> >>>>> From: Marius Cornea >>>>> Date: Friday, January 9, 2015 at 4:27 PM >>>>> >>>>> To: SAP SAP >>>>> Cc: rdo-list >>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>> >>>>> Let's keep the troubleshooting steps on the list. What's the output >>>>> of 'nova list' ? >>>>> >>>>> On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi wrote: >>>>> >>>>>> Yes, I did boot the instance but its getting 10.48.146.4 address >>>>>> rather 192.168.*** that you gave me ? I can logon to the instance console >>>>>> 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from >>>>>> host? >>>>>> >>>>>> Is it possible I share my screen, so that you can guide me what >>>>>> wrong thing that stops and bother me ? >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> >>>>>> Rushi. >>>>>> >>>>>> Success is not a matter of being the best & winning the race. Success >>>>>> is a matter of handling the worst & finishing the race >>>>>> >>>>>> >>>>>> From: Marius Cornea >>>>>> Date: Friday, January 9, 2015 at 4:18 PM >>>>>> >>>>>> To: SAP SAP >>>>>> Cc: rdo-list >>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>> >>>>>> Did you boot the instance with the demo-net attached ? >>>>>> >>>>>> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi wrote: >>>>>> >>>>>>> I can?t assign a port to the floating ip . I don?t? see any ports >>>>>>> available ? >>>>>>> >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rushi. >>>>>>> >>>>>>> Success is not a matter of being the best & winning the race. >>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>> >>>>>>> >>>>>>> From: Marius Cornea >>>>>>> Date: Friday, January 9, 2015 at 4:06 PM >>>>>>> >>>>>>> To: SAP SAP >>>>>>> Cc: rdo-list >>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>>>>>> >>>>>>> You've already defined router1 which is already connected to the >>>>>>> external network. You can use that. ext-net is the 'public' network in your >>>>>>> case. >>>>>>> >>>>>>> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi wrote: >>>>>>> >>>>>>>> I can?t run this command >>>>>>>> >>>>>>>> >>>>>>>> $ neutron router-gateway-set demo-router ext-net >>>>>>>> >>>>>>>> Its getting error (ext-net not found) ? What is the ext-net in >>>>>>>> this case ? >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Rushi. >>>>>>>> >>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>> >>>>>>>> From: , SAP SAP >>>>>>>> Date: Friday, January 9, 2015 at 3:58 PM >>>>>>>> >>>>>>>> To: Marius Cornea >>>>>>>> Cc: rdo-list >>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>> openstack. >>>>>>>> >>>>>>>> Ok I did the folowing steps for tenant. >>>>>>>> >>>>>>>> 1) neutron net-create demo-net >>>>>>>> 2) neutron subnet-create demo-net --name demo-subnet --gateway >>>>>>>> 10.48.146.1 10.48.146.0/24 >>>>>>>> 3) neutron router-create demo-router >>>>>>>> 4) neutron router-interface-add demo-router demo-subnet >>>>>>>> >>>>>>>> Anything left .? >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Rushi. >>>>>>>> >>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>> >>>>>>>> >>>>>>>> From: , SAP SAP >>>>>>>> Date: Friday, January 9, 2015 at 3:55 PM >>>>>>>> To: Marius Cornea >>>>>>>> Cc: rdo-list >>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>> openstack. >>>>>>>> >>>>>>>> Hi Marius, >>>>>>>> >>>>>>>> Yes, I can ping 10.48.146.113 (gateway) from the host , can you >>>>>>>> provide the comamnds or link to create tenant network, subjet and attach to >>>>>>>> router ? >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Rushi. >>>>>>>> >>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>> >>>>>>>> >>>>>>>> From: Marius Cornea >>>>>>>> Date: Friday, January 9, 2015 at 3:48 PM >>>>>>>> To: SAP SAP >>>>>>>> Cc: rdo-list >>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>> openstack. >>>>>>>> >>>>>>>> Can you ping 10.48.146.113 from your network? You also need to >>>>>>>> create a tenant network, subnet and attach it to the router. Boot the >>>>>>>> instance with the tenant network attached and then assign it the floating >>>>>>>> IP. >>>>>>>> >>>>>>>> >>>>>>>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Marius, >>>>>>>>> >>>>>>>>> I did this first and now can see the BR-ex is the same IP as my >>>>>>>>> eno1 interface , you are right I lost first while doing the first >>>>>>>>> command(ip addr del 10.48.146.77/24 dev eno1) and then conneting >>>>>>>>> to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also >>>>>>>>> changed the IP address of br-ex to 10.48.146.77) >>>>>>>>> >>>>>>>>> ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>>>> eno1 >>>>>>>>> >>>>>>>>> Then after I removed all the routers, networks and interfaces >>>>>>>>> from openstack and ran the following 4 commands. >>>>>>>>> >>>>>>>>> 1) source /root/keystonerc_admin >>>>>>>>> 2) neutron net-create public --router:external=True >>>>>>>>> 3) neutron subnet-create public 10.48.146.0/24 --name vlan >>>>>>>>> --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 >>>>>>>>> --gateway 10.48.146.1 >>>>>>>>> 4) neutron router-create router1 >>>>>>>>> 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>>>>>>>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>>>>>>>> 6) neutron floatingip-create public >>>>>>>>> >>>>>>>>> The above command generated a floating IP 10.48.146.115 >>>>>>>>> >>>>>>>>> Then I spin up a new instance and it got IP assigned >>>>>>>>> automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : >>>>>>>>> 10.48.146.115 ? >>>>>>>>> >>>>>>>>> Here are the screenshots >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron net-list >>>>>>>>> >>>>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>>>> | id | name | subnets >>>>>>>>> | >>>>>>>>> >>>>>>>>> +--------------------------------------+--------+-----------------------------------------------------+ >>>>>>>>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | >>>>>>>>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | >>>>>>>>> >>>>>>>>> +--------------------------------------+--------+??????????????????????????+ >>>>>>>>> >>>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron subnet-list >>>>>>>>> >>>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>>> | id | name | cidr | >>>>>>>>> allocation_pools | >>>>>>>>> >>>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | >>>>>>>>> {"start": "10.48.146.113", "end": "10.48.146.130"} | >>>>>>>>> >>>>>>>>> +--------------------------------------+------+----------------+----------------------------------------------------+ >>>>>>>>> >>>>>>>>> [root at lspal117 ~(keystone_admin)]# neutron router-list >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>> | id | name | >>>>>>>>> external_gateway_info >>>>>>>>> >>>>>>>>> | distributed | ha | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": >>>>>>>>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, >>>>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>>>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | >>>>>>>>> False | False | >>>>>>>>> >>>>>>>>> +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>> >>>>>>>>> Any ideas what is going wrong, I still can?t ping or ssh to that >>>>>>>>> IP address and its not listening anywhere ? >>>>>>>>> >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Rushi. >>>>>>>>> >>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>> >>>>>>>>> >>>>>>>>> From: Marius Cornea >>>>>>>>> Date: Friday, January 9, 2015 at 2:30 PM >>>>>>>>> To: SAP SAP , rdo-list >>>>>>>>> >>>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>>> openstack. >>>>>>>>> >>>>>>>>> As Kashyap kindly suggested we're not a support line and >>>>>>>>> information here should be available for all the community members. First, >>>>>>>>> I don't see how you can ping the br-ex IP address from an external network >>>>>>>>> since it doesn't contain any physical interface. Make sure that >>>>>>>>> 10.48.146.112 isn't used by other host on you network segment. You can do >>>>>>>>> the following to remove the ip address from the physical interface and add >>>>>>>>> it to the br-ex bridge. Please make sure that you've got console access to >>>>>>>>> the server before doing this as you may lose connectivity. >>>>>>>>> >>>>>>>>> # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex >>>>>>>>> eno1 >>>>>>>>> >>>>>>>>> You should then follow the documentation[1] to recreate the >>>>>>>>> public/tenant networks and router. In your >>>>>>>>> case FLOATING_IP_START, FLOATING_IP_END should be part of the >>>>>>>>> 10.48.146.0/24 network. Let's say you wish to allocate IP >>>>>>>>> addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack >>>>>>>>> routers/instances, then FLOATING_IP_START=10.48.146.200 and >>>>>>>>> FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to >>>>>>>>> what 'ip r | grep default | awk {'print $3'}' outputs >>>>>>>>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. >>>>>>>>> >>>>>>>>> Note that the instance will get an IP address of the tenant >>>>>>>>> network. By assigning a floating IP you will be able to access it through >>>>>>>>> an IP address from your physical network segment. >>>>>>>>> >>>>>>>>> [1] >>>>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Marius, >>>>>>>>>> >>>>>>>>>> Here are the outputs. Is it possible to reach you on phone so >>>>>>>>>> that I can explain more than email. You can call me at 650 849 >>>>>>>>>> 3915 or let me know your number. >>>>>>>>>> >>>>>>>>>> #ip a >>>>>>>>>> >>>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ip a >>>>>>>>>> 1: lo: mtu 65536 qdisc noqueue state >>>>>>>>>> UNKNOWN >>>>>>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>>>>>>>> inet 127.0.0.1/8 scope host lo >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> inet6 ::1/128 scope host >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> 2: eno1: mtu 1500 qdisc mq >>>>>>>>>> state UP qlen 1000 >>>>>>>>>> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> inet6 fe80::da9d:67ff:fe29:c694/64 scope link >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> 3: eno2: mtu 1500 qdisc mq >>>>>>>>>> state DOWN qlen 1000 >>>>>>>>>> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 4: eno3: mtu 1500 qdisc mq >>>>>>>>>> state DOWN qlen 1000 >>>>>>>>>> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 5: eno4: mtu 1500 qdisc mq >>>>>>>>>> state DOWN qlen 1000 >>>>>>>>>> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 6: ens1f0: mtu 1500 qdisc mq >>>>>>>>>> state DOWN qlen 1000 >>>>>>>>>> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 7: ens1f1: mtu 1500 qdisc mq >>>>>>>>>> state DOWN qlen 1000 >>>>>>>>>> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 8: ens2f0: mtu 1500 qdisc mq >>>>>>>>>> state DOWN qlen 1000 >>>>>>>>>> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 9: ens2f1: mtu 1500 qdisc mq >>>>>>>>>> state DOWN qlen 1000 >>>>>>>>>> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 10: ovs-system: mtu 1500 qdisc noop state >>>>>>>>>> DOWN >>>>>>>>>> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 11: br-ex: mtu 1500 qdisc >>>>>>>>>> noqueue state UNKNOWN >>>>>>>>>> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> 12: br-int: mtu 1500 qdisc noop state DOWN >>>>>>>>>> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 16: br-tun: mtu 1500 qdisc noop state DOWN >>>>>>>>>> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 17: qbr63bd6704-47: mtu 1500 >>>>>>>>>> qdisc noqueue state UP >>>>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>>>> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> 18: qvo63bd6704-47: mtu >>>>>>>>>> 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 >>>>>>>>>> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 19: qvb63bd6704-47: mtu >>>>>>>>>> 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 >>>>>>>>>> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff >>>>>>>>>> 22: tap63bd6704-47: mtu 1500 >>>>>>>>>> qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 >>>>>>>>>> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff >>>>>>>>>> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link >>>>>>>>>> valid_lft forever preferred_lft forever >>>>>>>>>> >>>>>>>>>> # ovs-vsctl show >>>>>>>>>> >>>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show >>>>>>>>>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>>>>>>>>> Bridge br-ex >>>>>>>>>> Port br-ex >>>>>>>>>> Interface br-ex >>>>>>>>>> type: internal >>>>>>>>>> Port "qg-c3a1b534-36" >>>>>>>>>> Interface "qg-c3a1b534-36" >>>>>>>>>> type: internal >>>>>>>>>> Bridge br-int >>>>>>>>>> fail_mode: secure >>>>>>>>>> Port patch-tun >>>>>>>>>> Interface patch-tun >>>>>>>>>> type: patch >>>>>>>>>> options: {peer=patch-int} >>>>>>>>>> Port "tape386c0cb-d8" >>>>>>>>>> tag: 1 >>>>>>>>>> Interface "tape386c0cb-d8" >>>>>>>>>> type: internal >>>>>>>>>> Port br-int >>>>>>>>>> Interface br-int >>>>>>>>>> type: internal >>>>>>>>>> Port "qvo63bd6704-47" >>>>>>>>>> tag: 1 >>>>>>>>>> Interface "qvo63bd6704-47" >>>>>>>>>> Port "tap44dd465f-d4" >>>>>>>>>> tag: 4095 >>>>>>>>>> Interface "tap44dd465f-d4" >>>>>>>>>> type: internal >>>>>>>>>> Port "qr-e0ac3c25-2b" >>>>>>>>>> tag: 2 >>>>>>>>>> Interface "qr-e0ac3c25-2b" >>>>>>>>>> type: internal >>>>>>>>>> Bridge br-tun >>>>>>>>>> Port br-tun >>>>>>>>>> Interface br-tun >>>>>>>>>> type: internal >>>>>>>>>> Port patch-int >>>>>>>>>> Interface patch-int >>>>>>>>>> type: patch >>>>>>>>>> options: {peer=patch-tun} >>>>>>>>>> ovs_version: ?2.1.3" >>>>>>>>>> >>>>>>>>>> # neutron net-list >>>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>>>> net-list >>>>>>>>>> >>>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>>> | id | name | subnets >>>>>>>>>> | >>>>>>>>>> >>>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | >>>>>>>>>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | >>>>>>>>>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | >>>>>>>>>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | >>>>>>>>>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | >>>>>>>>>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | >>>>>>>>>> >>>>>>>>>> +--------------------------------------+---------+------------------------------------------------------+ >>>>>>>>>> >>>>>>>>>> # neutron subnet-list >>>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>>>> subnet-list >>>>>>>>>> >>>>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>>>> | id | name | cidr >>>>>>>>>> | allocation_pools | >>>>>>>>>> >>>>>>>>>> +--------------------------------------+----------------+-----------------+----------------------------------------------------+ >>>>>>>>>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | >>>>>>>>>> 172.24.4.224/28 | {"start": "172.24.4.226", "end": >>>>>>>>>> "172.24.4.238"} | >>>>>>>>>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | >>>>>>>>>> 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} >>>>>>>>>> | >>>>>>>>>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | >>>>>>>>>> 10.48.146.0/24 | {"start": "10.48.146.112", "end": >>>>>>>>>> "10.48.146.120"} | >>>>>>>>>> >>>>>>>>>> +--------------------------------------+----------------+-----------------+??????????????????????????+ >>>>>>>>>> >>>>>>>>>> #neutron router-list >>>>>>>>>> [root at lspal117 network-scripts(keystone_admin)]# neutron >>>>>>>>>> router-list >>>>>>>>>> >>>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>>> | id | name | >>>>>>>>>> external_gateway_info >>>>>>>>>> >>>>>>>>>> | distributed | ha | >>>>>>>>>> >>>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ >>>>>>>>>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": >>>>>>>>>> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, >>>>>>>>>> "external_fixed_ips": [{"subnet_id": >>>>>>>>>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | >>>>>>>>>> False | False | >>>>>>>>>> >>>>>>>>>> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ >>>>>>>>>> >>>>>>>>>> In my system I have IP address for BR-ex and ENO1 (interface >>>>>>>>>> connecting ), should I disable eno1 as I can ping both (br-ex and eno1) >>>>>>>>>> from my network to reach to this host ? Probably its a dump question. >>>>>>>>>> >>>>>>>>>> Here are the outputs. >>>>>>>>>> >>>>>>>>>> br-ex: flags=4163 mtu 1500 >>>>>>>>>> inet 10.48.146.112 netmask 255.255.255.0 broadcast >>>>>>>>>> 10.48.146.255 >>>>>>>>>> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid >>>>>>>>>> 0x20 >>>>>>>>>> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) >>>>>>>>>> RX packets 10 bytes 864 (864.0 B) >>>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>>> TX packets 25 bytes 3767 (3.6 KiB) >>>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>>> >>>>>>>>>> br-int: flags=4098 mtu 1500 >>>>>>>>>> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) >>>>>>>>>> RX packets 135 bytes 7574 (7.3 KiB) >>>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>>> >>>>>>>>>> br-tun: flags=4098 mtu 1500 >>>>>>>>>> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) >>>>>>>>>> RX packets 0 bytes 0 (0.0 B) >>>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>>> TX packets 0 bytes 0 (0.0 B) >>>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>>> >>>>>>>>>> eno1: flags=4163 mtu 1500 >>>>>>>>>> inet 10.48.146.77 netmask 255.255.255.0 broadcast >>>>>>>>>> 10.48.146.255 >>>>>>>>>> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid >>>>>>>>>> 0x20 >>>>>>>>>> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) >>>>>>>>>> RX packets 467319 bytes 48391354 (46.1 MiB) >>>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>>> TX packets 14794 bytes 5238733 (4.9 MiB) >>>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>>> device interrupt 32 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Best Regards, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Rushi. >>>>>>>>>> >>>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> From: Marius Cornea >>>>>>>>>> Date: Friday, January 9, 2015 at 1:46 PM >>>>>>>>>> To: SAP SAP >>>>>>>>>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>>>>>>>>> openstack. >>>>>>>>>> >>>>>>>>>> Hi Rushi, >>>>>>>>>> >>>>>>>>>> Can you provide the output of the following commands on your >>>>>>>>>> node ? >>>>>>>>>> >>>>>>>>>> # ip a >>>>>>>>>> # ovs-vsctl show >>>>>>>>>> # neutron net-list >>>>>>>>>> # neutron subnet-list >>>>>>>>>> # neutron router-list >>>>>>>>>> >>>>>>>>>> Please note that only the br-ex bridge requires an IP address, >>>>>>>>>> the interface that's part of it shouldn't have one assigned. Also the >>>>>>>>>> floating IP addresses will be used for DNAT on the tenant router. You can >>>>>>>>>> check the documentation here[1] that describes the use of floating IPs. >>>>>>>>>> >>>>>>>>>> You can also check the upstream documentation[2] on how to >>>>>>>>>> create the networks. >>>>>>>>>> >>>>>>>>>> [1] >>>>>>>>>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP >>>>>>>>>> [2] >>>>>>>>>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Tnx, >>>>>>>>>> Marius >>>>>>>>>> >>>>>>>>>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Support, >>>>>>>>>>> >>>>>>>>>>> I have a problem that a launched instance from openstack >>>>>>>>>>> cannot connect to SSH or PING >>>>>>>>>>> >>>>>>>>>>> First of all I have dump question whether my system should be >>>>>>>>>>> NOVA network or Neutron network. Well to keep everyone on the same page. >>>>>>>>>>> Here is my history. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 1. I did install RDO (allinone host) using the bellow steps >>>>>>>>>>> https://openstack.redhat.com/Quickstart >>>>>>>>>>> 2. Then I have used the following steps for floating IP >>>>>>>>>>> https://openstack.redhat.com/Floating_IP_range. >>>>>>>>>>> >>>>>>>>>>> My situtation is as follows. >>>>>>>>>>> * Floating IP address assignment: >>>>>>>>>>> I have assigned a floating IP , I did follow this steps. >>>>>>>>>>> https://openstack.redhat.com/Floating_IP_range >>>>>>>>>>> >>>>>>>>>>> * Bridge configuration:My Ethernet device eth0(actually in >>>>>>>>>>> Redhat 7 it is eno1 name)is on the same bridge as the compute host >>>>>>>>>>> Yes, ethernet device on 10.48.146.78 address and br-ex interface >>>>>>>>>>> on 10.48.146.112 >>>>>>>>>>> >>>>>>>>>>> * DHCP configuration: Yes, DHCP configuration is set and >>>>>>>>>>> Neutron hearing and responding to DHCP >>>>>>>>>>> requests and the instance is getting IP from 10.48.146.113 (next >>>>>>>>>>> hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed >>>>>>>>>>> rule on default security group) >>>>>>>>>>> >>>>>>>>>>> Here is the little diagram of my system. >>>>>>>>>>> >>>>>>>>>>> Can someone help to find what is missing. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Best Regards, >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Rushi. >>>>>>>>>>> >>>>>>>>>>> Success is not a matter of being the best & winning the race. >>>>>>>>>>> Success is a matter of handling the worst & finishing the race >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Rdo-list mailing list >>>>>>>>>>> Rdo-list at redhat.com >>>>>>>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3DBCBF54-A0DD-43A7-A793-4E902C409617.png Type: image/png Size: 135378 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png Type: image/png Size: 61042 bytes Desc: not available URL: From swapnil at linux.com Sat Jan 10 05:16:31 2015 From: swapnil at linux.com (Swapnil Jain) Date: Sat, 10 Jan 2015 10:46:31 +0530 Subject: [Rdo-list] Error: Could not find command 'systemctl' In-Reply-To: <54AFAC8F.6020501@redhat.com> References: <3CA49604-03A7-4C91-9618-E0EBCC9AAD8A@Linux.com> <54AEB689.5030602@redhat.com> <54AFAC8F.6020501@redhat.com> Message-ID: <71583FFA-F9A7-4A35-9ECF-8EE09C47CA6A@Linux.com> https://bugzilla.redhat.com/show_bug.cgi?id=1172876 ? Swapnil Jain | Swapnil at Linux.com RHC{A,DS,E,SA,SA-RHOS,VA}, CC{DA,NA}, MCSE, CNE > On 09-Jan-2015, at 3:55 pm, Ihar Hrachyshka wrote: > > Do you have a link to the bug? > > On 01/09/2015 10:19 AM, Swapnil Jain wrote: >> Theres already an open bug assigned but no fix yet. I fooled it by creating a bash script as /usr/bin/systemctl. A bad way of doing it but it worked ;) >> >> #!/bin/bash >> SER=`echo $2 |gawk -F. '{print $1}'` >> service $SER $1 >> >> >> >> >> ? >> Swapnil Jain | Swapnil at Linux.com >> RHC{A,DS,E,SA,SA-RHOS,VA}, CC{DA,NA}, MCSE, CNE >> >> >>> On 08-Jan-2015, at 10:25 pm, Ihar Hrachyshka > wrote: >>> >>> Please report a bug for this behaviour. But first check that you run against correct repo (el6, not el7). >>> >>> On 01/08/2015 10:11 AM, Swapnil Jain wrote: >>>> Hi, >>>> >>>> I am getting the below error while install icehouse on RHEL6. its looking for systemctl which is not available. >>>> >>>> 172.16.254.2_osclient.pp: [ DONE ] >>>> 172.16.254.2_horizon.pp: [ ERROR ] >>>> Applying Puppet manifests [ ERROR ] >>>> >>>> ERROR : Error appeared during Puppet run: 172.16.254.2_horizon.pp >>>> Error: Could not find command 'systemctl' >>>> You will find full trace in log /var/tmp/packstack/20150108-222031-ha6FwJ/manifests/172.16.254.2_horizon.pp.log >>>> Please check log file /var/tmp/packstack/20150108-222031-ha6FwJ/openstack-setup.log for more information >>>> >>>> >>>> ? >>>> Swapnil Jain | Swapnil at Linux.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> Rdo-list mailing list >>>> Rdo-list at redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: From david.hill at ubisoft.com Mon Jan 12 05:11:57 2015 From: david.hill at ubisoft.com (David Hill) Date: Mon, 12 Jan 2015 05:11:57 +0000 Subject: [Rdo-list] Juno EPEL packages Message-ID: Hi guys, I'm volunteering to maintain Centos/RHEL/OEL 6 packages for Juno if nobody's doing it yet. How do I proceed to get involved in this project? We're already building packages internally with a set of custom patches and I feel like moving to RHEL 7.x will take lots of effort to lots of people. There's already a python-2.7 package in EPEL (I think) if Juno/Kilo/Lima/Mike requires python-2.7 there's always ways of getting around those requirements. BTW, I would like to know if there're lots of people using RHEL 6.X or are we only a small subset of the community? Thank you very much, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From Yaniv.Kaul at emc.com Mon Jan 12 08:28:59 2015 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Mon, 12 Jan 2015 03:28:59 -0500 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: <648473255763364B961A02AC3BE1060D03C9CD89BA@MX19A.corp.emc.com> I wouldn't mind working with Juno on EL6. I think there are bugs on EL7 that I'd like to avoid for the time being and it allows me to use a single platform for running both IceHouse and Juno tests. If could provide those packages, I can easily test some storage related tests on it. Y. From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of David Hill Sent: Monday, January 12, 2015 7:12 AM To: rdo-list at redhat.com Subject: [Rdo-list] Juno EPEL packages Hi guys, I'm volunteering to maintain Centos/RHEL/OEL 6 packages for Juno if nobody's doing it yet. How do I proceed to get involved in this project? We're already building packages internally with a set of custom patches and I feel like moving to RHEL 7.x will take lots of effort to lots of people. There's already a python-2.7 package in EPEL (I think) if Juno/Kilo/Lima/Mike requires python-2.7 there's always ways of getting around those requirements. BTW, I would like to know if there're lots of people using RHEL 6.X or are we only a small subset of the community? Thank you very much, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.oulevey at cern.ch Mon Jan 12 08:44:56 2015 From: thomas.oulevey at cern.ch (Thomas Oulevey) Date: Mon, 12 Jan 2015 09:44:56 +0100 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: <54B38988.5080601@cern.ch> Hi David, We have a lot of interest in the Juno for el6 packages at CERN. It would be great if you can share the patches and we can work together to build it in a central way. What is your approach in the current patchset ? rebuild python 2.7 or patch openstack to work with python 2.6 ? I am working as well with the CentOS team. I am part of the team that maintain the build system (http://wiki.centos.org/HowTos/CommunityBuildSystem). RDO started to rebuild their packages with this system for the cloud SIG effort (http://wiki.centos.org/SpecialInterestGroup/Cloud). I'll let Rich or someone more involved in the cloud sig to comment on this effort as I have not all latest details/plan. You can catch me on irc (alphacc on freenode) any time. cheers, -- Thomas. On 01/12/2015 06:11 AM, David Hill wrote: > Hi guys, > > I?m volunteering to maintain Centos/RHEL/OEL 6 packages for Juno if > nobody?s doing it yet. > > How do I proceed to get involved in this project? We?re already > building packages internally with a > > set of custom patches and I feel like moving to RHEL 7.x will take lots > of effort to lots of people. > > There?s already a python-2.7 package in EPEL (I think) if > Juno/Kilo/Lima/Mike requires python-2.7 > > there?s always ways of getting around those requirements. > > BTW, I would like to know if there?re lots of people using RHEL 6.X or > are we only a small subset > > of the community? > > Thank you very much, > > Dave > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From rigvedh79 at gmail.com Mon Jan 12 08:57:30 2015 From: rigvedh79 at gmail.com (Rigvedh chakroborty) Date: Mon, 12 Jan 2015 14:27:30 +0530 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: Hello david, I am using rhel 6.5 and I am sure moving to rhel 7 will be challenge. Cheers Rajiv On Jan 12, 2015 10:44 AM, "David Hill" wrote: > Hi guys, > > > > I?m volunteering to maintain Centos/RHEL/OEL 6 packages > for Juno if nobody?s doing it yet. > > How do I proceed to get involved in this project? We?re already building > packages internally with a > > set of custom patches and I feel like moving to RHEL 7.x will take lots of > effort to lots of people. > > There?s already a python-2.7 package in EPEL (I think) if > Juno/Kilo/Lima/Mike requires python-2.7 > > there?s always ways of getting around those requirements. > > > > BTW, I would like to know if there?re lots of people using RHEL 6.X or are > we only a small subset > > of the community? > > > > Thank you very much, > > Dave > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at gmail.com Mon Jan 12 10:02:24 2015 From: apevec at gmail.com (Alan Pevec) Date: Mon, 12 Jan 2015 11:02:24 +0100 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: > I?m volunteering to maintain Centos/RHEL/OEL 6 packages for > Juno if nobody?s doing it yet. Thanks for stepping up, I've created a trello card for this effort and added initial notes: https://trello.com/c/L0X5bU5s/25-el6-juno-packages Repeating here: * python27 is not there yet in EPEL6 (under review https://bugzilla.redhat.com/show_bug.cgi?id=829892 ) but it would also require to rebuild ALL python deps as python27-* so not an option * Juno is still python 2.6 compatible so single spec should work (see f21 branch for examples where single spec is used to build all of Fedora/el6/el7 builds of Icehouse > How do I proceed to get involved in this project? We?re already building > packages internally with a > set of custom patches and I feel like moving to RHEL 7.x will take lots of > effort to lots of people. There are also benefits (newer kernel/qemu-kvm/libvirt) on EL7 which you should consider also you'll have to make a switch at one point. > There?s already a python-2.7 package in EPEL (I think) if python27 is still under review, but even if it gets into EPEL7 soon I wouldn't suggest that route (see above) > Juno/Kilo/Lima/Mike requires python-2.7 Juno still works with python 2.6, >= Kilo requires python >= 2.7 > there?s always ways of getting around those requirements. Supporting py26 where upstream abandoned it would be a fork and RDO strives to be close to upstream. Way forward here would be to check Fedora Rawhide (f22 i.e. master branch) openstack-* specs and add support to build on el6. Also you might want to consider keeping only Compute nodes on EL6 and migrate Controllers to EL7. In that case we would need to maintain only openstack-nova Juno for EL6. Cheers, Alan From apevec at gmail.com Mon Jan 12 10:03:59 2015 From: apevec at gmail.com (Alan Pevec) Date: Mon, 12 Jan 2015 11:03:59 +0100 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: > python27 is still under review, but even if it gets into EPEL7 soon s/EPEL7/EPEL6/ of course! From dpkshetty at gmail.com Mon Jan 12 12:17:20 2015 From: dpkshetty at gmail.com (Deepak Shetty) Date: Mon, 12 Jan 2015 17:47:20 +0530 Subject: [Rdo-list] [Manila] Don't see python-manilaclient package Message-ID: Hi, I installed RDO juno-1 (2 weeks back) on a 3-node setup. I don't see the python-manilaclient package per the `yum search` i did, hence cannot use Manila from command line. I don't think Manila is yet integrated into horizon, so have to use manila cmdline to test the validity of some of the glusterfs drivers that recently went into Manila NOTE: manila specific packages were installed using `yum install ...` after RDO 3 node setup was created. I understand that Manila is still a tech preview/beta but i think manilaclient python package is missing.. Can someone confirm pls ? Below is some data from my setup: ========================== [root at rhsdev1 ~]# yum search manila Loaded plugins: fastestmirror, langpacks, priorities Loading mirror speeds from cached hostfile * base: mirror-fpt-telecom.fpt.net * epel: mirror.nus.edu.sg * extras: mirror.nbrc.ac.in * updates: mirror.nbrc.ac.in ============================================================================================================ N/S matched: manila ============================================================================================================ openstack-manila.noarch : OpenStack Shared Filesystem Service openstack-manila-doc.noarch : Documentation for OpenStack Shared Filesystem Service openstack-manila-share.noarch : An implementation of OpenStack Shared Filesystem Service python-manila.noarch : Python libraries for OpenStack Shared Filesystem Service [root at rhsdev1 ~]# rpm -qa| grep rdo rubygem-rdoc-4.0.0-22.el7_0.noarch rdo-release-juno-1.noarch [root at rhsdev1 ~]# rpm -qa| grep cinder python-cinderclient-1.1.1-1.el7.centos.noarch openstack-cinder-2014.2.1-1.el7.centos.noarch python-cinder-2014.2.1-1.el7.centos.noarch [root at rhsdev1 ~]# rpm -qa| grep manila openstack-manila-2014.2-0.3.el7.centos.noarch python-manila-2014.2-0.3.el7.centos.noarch openstack-manila-doc-2014.2-0.3.el7.centos.noarch openstack-manila-share-2014.2-0.3.el7.centos.noarch [root at rhsdev1 ~]# yum install python-manilaclient Loaded plugins: fastestmirror, langpacks, priorities Loading mirror speeds from cached hostfile * base: mirror.nbrc.ac.in * epel: mirror.nus.edu.sg * extras: mirror.nbrc.ac.in * updates: mirror.nbrc.ac.in No package python-manilaclient available. Error: Nothing to do [root at rhsdev1 ~(keystone_admin)]# cinder list +----+--------+--------------+------+-------------+----------+-------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +----+--------+--------------+------+-------------+----------+-------------+ +----+--------+--------------+------+-------------+----------+-------------+ [root at rhsdev1 ~(keystone_admin)]# manila list -bash: manila: command not found [root at rhsdev1 ~(keystone_admin)]# [root at rhsdev1 ~(keystone_admin)]# file /usr/bin/cinder /usr/bin/cinder: Python script, ASCII text executable [root at rhsdev1 ~(keystone_admin)]# file /usr/bin/manila /usr/bin/manila: cannot open (No such file or directory) [root at rhsdev1 ~(keystone_admin)]# thanx, deepak -------------- next part -------------- An HTML attachment was scrubbed... URL: From hguemar at fedoraproject.org Mon Jan 12 12:21:07 2015 From: hguemar at fedoraproject.org (=?windows-1252?Q?Ha=EFkel_Gu=E9mar?=) Date: Mon, 12 Jan 2015 13:21:07 +0100 Subject: [Rdo-list] [Manila] Don't see python-manilaclient package In-Reply-To: References: Message-ID: <54B3BC33.1040504@fedoraproject.org> Le 12/01/2015 13:17, Deepak Shetty a ?crit : > Hi, > I installed RDO juno-1 (2 weeks back) on a 3-node setup. > > I don't see the python-manilaclient package per the `yum search` i > did, hence cannot use Manila from command line. I don't think Manila > is yet integrated into horizon, so have to use manila cmdline to test > the validity of some of the glusterfs drivers that recently went into > Manila > > NOTE: manila specific packages were installed using `yum install ...` > after RDO 3 node setup was created. I understand that Manila is still > a tech preview/beta but i think manilaclient python package is > missing.. Can someone confirm pls ? > > Pete Zaitcev packaged python-manilaclient (available on rawhide), so it should not be a problem to have it into RDO. I'll do the builds and submit them today. You're right, there's no integration in Horizon yet. Regards, H. From hguemar at fedoraproject.org Mon Jan 12 14:56:40 2015 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Mon, 12 Jan 2015 15:56:40 +0100 Subject: [Rdo-list] [Manila] Don't see python-manilaclient package In-Reply-To: <54B3BC33.1040504@fedoraproject.org> References: <54B3BC33.1040504@fedoraproject.org> Message-ID: @Deepak: rebuilt and merged, it should be included in the RDO repository during the next refresh. Regards, H. From david.hill at ubisoft.com Mon Jan 12 16:18:57 2015 From: david.hill at ubisoft.com (David Hill) Date: Mon, 12 Jan 2015 16:18:57 +0000 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: Hello Alan, I think dropping Centos6/RHEL6/OEL6 support at this time is premature (IMHO). I don't think we'll be updating to Centos7 this year and for this reason, I'll be maintaining packages on my side for internal use so... if I can give a little time home to get these packages done for the community while using community build system, it would be awesome and give me the opportunity to learn new stuff. I'm already familiar with build systems (spec files, rpms, signature, Jenkins, etc) so it wouldn't be that much of an effort (I guess). If we don't need python27 it's even better. Dave -----Original Message----- From: Alan Pevec [mailto:apevec at gmail.com] Sent: 12-Jan-15 5:02 AM To: David Hill Cc: rdo-list at redhat.com Subject: Re: [Rdo-list] Juno EPEL packages > I?m volunteering to maintain Centos/RHEL/OEL 6 packages for > Juno if nobody?s doing it yet. Thanks for stepping up, I've created a trello card for this effort and added initial notes: https://trello.com/c/L0X5bU5s/25-el6-juno-packages Repeating here: * python27 is not there yet in EPEL6 (under review https://bugzilla.redhat.com/show_bug.cgi?id=829892 ) but it would also require to rebuild ALL python deps as python27-* so not an option * Juno is still python 2.6 compatible so single spec should work (see f21 branch for examples where single spec is used to build all of Fedora/el6/el7 builds of Icehouse > How do I proceed to get involved in this project? We?re already building > packages internally with a > set of custom patches and I feel like moving to RHEL 7.x will take lots of > effort to lots of people. There are also benefits (newer kernel/qemu-kvm/libvirt) on EL7 which you should consider also you'll have to make a switch at one point. > There?s already a python-2.7 package in EPEL (I think) if python27 is still under review, but even if it gets into EPEL7 soon I wouldn't suggest that route (see above) > Juno/Kilo/Lima/Mike requires python-2.7 Juno still works with python 2.6, >= Kilo requires python >= 2.7 > there?s always ways of getting around those requirements. Supporting py26 where upstream abandoned it would be a fork and RDO strives to be close to upstream. Way forward here would be to check Fedora Rawhide (f22 i.e. master branch) openstack-* specs and add support to build on el6. Also you might want to consider keeping only Compute nodes on EL6 and migrate Controllers to EL7. In that case we would need to maintain only openstack-nova Juno for EL6. Cheers, Alan From rbowen at redhat.com Mon Jan 12 18:51:59 2015 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 12 Jan 2015 13:51:59 -0500 Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 12, 2015) Message-ID: <54B417CF.9070000@redhat.com> The following are the meetups I'm aware of in the coming week where RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If there's a meetup in your area, please consider attending. It's the best way to find out what interesting things are going on in the larger community, and a great way to make contacts that will help you solve your own problems in the future. And don't forget to blog about it, tweet about it, G+ about it. --Rich * Tuesday, January 13 in Mountain View, CA, US: Online Meetup: Build a rock-solid foundation under your OpenStack cloud - http://www.meetup.com/Cloud-Online-Meetup/events/219714843/ * Tuesday, January 13 in Bangalore, IN: OpenStack India Meetup, New Delhi - http://www.meetup.com/Indian-OpenStack-User-Group/events/219637729/ * Tuesday, January 13 in Washington, DC, US: OpenStackDC Meetup #17 - http://www.meetup.com/OpenStackDC/events/218760179/ * Thursday, January 15 in Calgary, AB, CA: First Calgary OpenStack Meetup! - http://www.meetup.com/Calgary-OpenStack-Meetup/events/219503704/ * Wednesday, January 14 in Boston, MA, US: OpenStack Neutron networking and more - double header event! - http://www.meetup.com/Openstack-Boston/events/218862617/ * Wednesday, January 14 in Tel Aviv-Yafo, IL: DevOps for OpenStack - Migrating a Major Bank to OpenStack, with Vassil Avramov - http://www.meetup.com/OpenStack-Israel/events/219611133/ * Thursday, January 15 in Chicago, IL, US: At the Crossroads of HPC and Cloud Computing with OpenStack - http://www.meetup.com/chicagoacm/events/219410203/ * Thursday, January 15 in New York, NY, US: "Mix-and-match your Cloud" - http://www.meetup.com/OpenStack-for-Enterprises-NYC/events/219241367/ * Friday, January 16 in Austin, TX, US: Deep Dive into Trove and Preview OpenStack Kilo - http://www.meetup.com/OpenStack-Austin/events/218860202/ * Thursday, January 15 in London, 17, GB: 2nd OpenDaylight and SDN meetup - http://www.meetup.com/London-SDN-ODLUG/events/218972643/ * Thursday, January 15 in Dublin, IE: Social Network Event - http://www.meetup.com/Dublin-PaaS-Meetup/events/219614711/ * Friday, January 16 in Atlanta, GA, US: OpenStack Meetup (Topic TBD) - http://www.meetup.com/openstack-atlanta/events/218782169/ * Friday, January 16 in Chicago, IL, US: January 15th meetup with Red Hat - http://www.meetup.com/meetup-group-NjZdcegA/events/219665949/ * Friday, January 16 in Lahore, PK: Openstack Introductory Meetup - http://www.meetup.com/Lahore-OpenStack-Meetup/events/219586680/ * Friday, January 16 in Versailles, FR: Meetup pour le Cloud Openstack & Eureka - http://www.meetup.com/Versailles-Cloud-based-Social-Media-Meetup/events/219600743/ * Saturday, January 17 in Fort Collins, CO, US: DevStack Saturday Jan 17 Harmony Lib Fort Collins - http://www.meetup.com/OpenStack-Colorado/events/219497398/ * Monday, January 19 in M?nchen, DE: OpenStack Meetup N?rnberg - http://www.meetup.com/OpenStack-Munich/events/219374402/ -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From Arkady_Kanevsky at dell.com Mon Jan 12 18:55:55 2015 From: Arkady_Kanevsky at dell.com (Arkady_Kanevsky at dell.com) Date: Mon, 12 Jan 2015 12:55:55 -0600 Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 12, 2015) In-Reply-To: <54B417CF.9070000@redhat.com> References: <54B417CF.9070000@redhat.com> Message-ID: <336424C1A5A44044B29030055527AA7504B13842C5@AUSX7MCPS301.AMER.DELL.COM> Correction: *Thursday, January 15 in Austin, TX, US: Deep Dive into Trove and Preview OpenStack Kilo - http://www.meetup.com/OpenStack-Austin/events/218860202/ -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Rich Bowen Sent: Monday, January 12, 2015 12:52 PM To: rdo-list at redhat.com Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 12, 2015) The following are the meetups I'm aware of in the coming week where RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If there's a meetup in your area, please consider attending. It's the best way to find out what interesting things are going on in the larger community, and a great way to make contacts that will help you solve your own problems in the future. And don't forget to blog about it, tweet about it, G+ about it. --Rich * Tuesday, January 13 in Mountain View, CA, US: Online Meetup: Build a rock-solid foundation under your OpenStack cloud - http://www.meetup.com/Cloud-Online-Meetup/events/219714843/ * Tuesday, January 13 in Bangalore, IN: OpenStack India Meetup, New Delhi - http://www.meetup.com/Indian-OpenStack-User-Group/events/219637729/ * Tuesday, January 13 in Washington, DC, US: OpenStackDC Meetup #17 - http://www.meetup.com/OpenStackDC/events/218760179/ * Thursday, January 15 in Calgary, AB, CA: First Calgary OpenStack Meetup! - http://www.meetup.com/Calgary-OpenStack-Meetup/events/219503704/ * Wednesday, January 14 in Boston, MA, US: OpenStack Neutron networking and more - double header event! - http://www.meetup.com/Openstack-Boston/events/218862617/ * Wednesday, January 14 in Tel Aviv-Yafo, IL: DevOps for OpenStack - Migrating a Major Bank to OpenStack, with Vassil Avramov - http://www.meetup.com/OpenStack-Israel/events/219611133/ * Thursday, January 15 in Chicago, IL, US: At the Crossroads of HPC and Cloud Computing with OpenStack - http://www.meetup.com/chicagoacm/events/219410203/ * Thursday, January 15 in New York, NY, US: "Mix-and-match your Cloud" - http://www.meetup.com/OpenStack-for-Enterprises-NYC/events/219241367/ * Friday, January 16 in Austin, TX, US: Deep Dive into Trove and Preview OpenStack Kilo - http://www.meetup.com/OpenStack-Austin/events/218860202/ * Thursday, January 15 in London, 17, GB: 2nd OpenDaylight and SDN meetup - http://www.meetup.com/London-SDN-ODLUG/events/218972643/ * Thursday, January 15 in Dublin, IE: Social Network Event - http://www.meetup.com/Dublin-PaaS-Meetup/events/219614711/ * Friday, January 16 in Atlanta, GA, US: OpenStack Meetup (Topic TBD) - http://www.meetup.com/openstack-atlanta/events/218782169/ * Friday, January 16 in Chicago, IL, US: January 15th meetup with Red Hat - http://www.meetup.com/meetup-group-NjZdcegA/events/219665949/ * Friday, January 16 in Lahore, PK: Openstack Introductory Meetup - http://www.meetup.com/Lahore-OpenStack-Meetup/events/219586680/ * Friday, January 16 in Versailles, FR: Meetup pour le Cloud Openstack & Eureka - http://www.meetup.com/Versailles-Cloud-based-Social-Media-Meetup/events/219600743/ * Saturday, January 17 in Fort Collins, CO, US: DevStack Saturday Jan 17 Harmony Lib Fort Collins - http://www.meetup.com/OpenStack-Colorado/events/219497398/ * Monday, January 19 in M?nchen, DE: OpenStack Meetup N?rnberg - http://www.meetup.com/OpenStack-Munich/events/219374402/ -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list From rbowen at redhat.com Mon Jan 12 19:00:56 2015 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 12 Jan 2015 14:00:56 -0500 Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 12, 2015) In-Reply-To: <336424C1A5A44044B29030055527AA7504B13842C5@AUSX7MCPS301.AMER.DELL.COM> References: <54B417CF.9070000@redhat.com> <336424C1A5A44044B29030055527AA7504B13842C5@AUSX7MCPS301.AMER.DELL.COM> Message-ID: <54B419E8.1010200@redhat.com> On 01/12/2015 01:55 PM, Arkady_Kanevsky at dell.com wrote: > Correction: > *Thursday, January 15 in Austin, TX, US: Deep Dive into Trove and Preview OpenStack Kilo - http://www.meetup.com/OpenStack-Austin/events/218860202/ > Thanks for the correction. I'll bet that's a timezone bug in my web scraping script, because it's after midnight UTC. --Rich > -----Original Message----- > From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Rich Bowen > Sent: Monday, January 12, 2015 12:52 PM > To: rdo-list at redhat.com > Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 12, 2015) > > The following are the meetups I'm aware of in the coming week where RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events > > If there's a meetup in your area, please consider attending. It's the best way to find out what interesting things are going on in the larger community, and a great way to make contacts that will help you solve your own problems in the future. > > And don't forget to blog about it, tweet about it, G+ about it. > > --Rich > > * Tuesday, January 13 in Mountain View, CA, US: Online Meetup: Build a rock-solid foundation under your OpenStack cloud - http://www.meetup.com/Cloud-Online-Meetup/events/219714843/ > > * Tuesday, January 13 in Bangalore, IN: OpenStack India Meetup, New Delhi - http://www.meetup.com/Indian-OpenStack-User-Group/events/219637729/ > > * Tuesday, January 13 in Washington, DC, US: OpenStackDC Meetup #17 - http://www.meetup.com/OpenStackDC/events/218760179/ > > * Thursday, January 15 in Calgary, AB, CA: First Calgary OpenStack Meetup! - http://www.meetup.com/Calgary-OpenStack-Meetup/events/219503704/ > > * Wednesday, January 14 in Boston, MA, US: OpenStack Neutron networking > and more - double header event! - > http://www.meetup.com/Openstack-Boston/events/218862617/ > > * Wednesday, January 14 in Tel Aviv-Yafo, IL: DevOps for OpenStack - Migrating a Major Bank to OpenStack, with Vassil Avramov - http://www.meetup.com/OpenStack-Israel/events/219611133/ > > * Thursday, January 15 in Chicago, IL, US: At the Crossroads of HPC and Cloud Computing with OpenStack - http://www.meetup.com/chicagoacm/events/219410203/ > > * Thursday, January 15 in New York, NY, US: "Mix-and-match your Cloud" - http://www.meetup.com/OpenStack-for-Enterprises-NYC/events/219241367/ > > * Friday, January 16 in Austin, TX, US: Deep Dive into Trove and Preview OpenStack Kilo - http://www.meetup.com/OpenStack-Austin/events/218860202/ > > * Thursday, January 15 in London, 17, GB: 2nd OpenDaylight and SDN meetup - http://www.meetup.com/London-SDN-ODLUG/events/218972643/ > > * Thursday, January 15 in Dublin, IE: Social Network Event - http://www.meetup.com/Dublin-PaaS-Meetup/events/219614711/ > > * Friday, January 16 in Atlanta, GA, US: OpenStack Meetup (Topic TBD) - http://www.meetup.com/openstack-atlanta/events/218782169/ > > * Friday, January 16 in Chicago, IL, US: January 15th meetup with Red Hat - http://www.meetup.com/meetup-group-NjZdcegA/events/219665949/ > > * Friday, January 16 in Lahore, PK: Openstack Introductory Meetup - http://www.meetup.com/Lahore-OpenStack-Meetup/events/219586680/ > > * Friday, January 16 in Versailles, FR: Meetup pour le Cloud Openstack & Eureka - http://www.meetup.com/Versailles-Cloud-based-Social-Media-Meetup/events/219600743/ > > * Saturday, January 17 in Fort Collins, CO, US: DevStack Saturday Jan 17 Harmony Lib Fort Collins - http://www.meetup.com/OpenStack-Colorado/events/219497398/ > > * Monday, January 19 in M?nchen, DE: OpenStack Meetup N?rnberg - http://www.meetup.com/OpenStack-Munich/events/219374402/ > > -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From rushi.ns at sap.com Mon Jan 12 19:11:33 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Mon, 12 Jan 2015 19:11:33 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: HI Marius I cannot run tcpdump on the VM? as it appear it doenst have the package ? I have the same problem on the 3 images that I have instances (cirros, suse , redhat) I am assuming something was not right on the network for tenant ? Can you help me . Is is possible if I send you my LYNC share so that I can show the screen ? Also I don?t see any router in Tenant (demo user) network ? Is that required like below point 3 I am reading all these from redhat ? Is there something that is not correct in my configuration? * I can create an instance, but cannot SSH or ping it * 1) Verify that traffic to port 22 and ICMP traffic of any type (-1:-1) is allowed in the default security groupIn the dashboard, in the Project tab, under "Access and Security", check the rules which are active on the security group you are using with your instances (typically "default"). You should see a rule allowing traffic to port 22 over tcp from all hosts, and a port enabling icmp traffic of all types (-1). If you don't, create the necessary rules, and try again. * 2) Verify that you can ping and SSH the host where the instance is runningFrom the host where you are attempting to connect to your instance, verify that network traffic is being correctly routed to the compute node in question. * 3) Ensure that the router is correctly created, that the internal subnet and external subnet are attached to it, and that it can route traffic from your IP to the instance IPIf your VM is in the 192.168.1.x subnet, and the host from which you are trying to connect is in the 192.168.0.x subnet, then you will need to have a route from one to the other. Ensure that the subnet 192.168.1.x and 192.168.0.x are both added to a router which you create in Neutron * 4) Check that you can ping an instance from inside its network namespace.If you are using network namespaces, then each VLAN will have its own namespace, and entities inside that namespace will be invisible from outside. You can check whether you can ping an instance from inside the namespace by first finding the namespace identifier, and then using the iproute toolset to execute a "ping" inside that namespace: Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 6:01 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Well neutron uses iptables to implement the security groups so I'm not sure what's the result of removing the iptables rules from the openstack host. Since the ssh connection to 10.48.146.115 was getting a connection refused I would have checked first the VM to see if any packets reach its interface. You could do that by 'tcpdump -i {interface_name}' inside the VM. On Sat, Jan 10, 2015 at 2:44 AM, Ns, Rushi > wrote: By the way, My openstack host is : REDHAT7 ? Do you think is there any settings on sshd preventing to connet to VM (to check to see this VM?? ssh ? ) I did checked and making sure iptables off on the openstack host ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:31 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. I did verified on the VM., No fiewall enable (this is suse create with SUSE Studio) SSH is listening on the VM and I can ssh to the local host [cid:3DBCBF54-A0DD-43A7-A793-4E902C409617] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:23 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. I see that you get a 'connection refused' message which means that the VM responds. Is the ssh service running on the VM or is there any firewall on the VM that might prevent connectivity? You could run tcpdump inside the VM to see if any of your packets reach it. On Sat, Jan 10, 2015 at 2:18 AM, Ns, Rushi > wrote: Here are my allowed port list but I can?t ping or I can?t ssh ? [cid:81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:17 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is the console, I can ping gateway of my host : 10.48.146.1 and others but I cannot ssh to that instance from oopensetack host. [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 10.48.146.115 ssh: connect to host 10.48.146.115 port 22: Connection refused [root at lspal117 tmp(keystone_admin)]# ssh -l root -i lvmgrouplatest.pem 192.168.1.4 [cid:9B3B10A4-4C8D-472C-9B21-C82D718CC6E0] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:12 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Sorry I can assign the floating ip to the instnace (demo user launched insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ 10.48.146.115) from the host but from the instance (192.168.1.2) I can ping other instance 192.168.1.4 ? Can you help in this final step what is missing > [cid:0E7F5284-9B90-46DA-B1CE-824110D267B8] root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.115"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.4"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 5:03 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Here is it [root at lspal117 tmp(keystone_admin)]# neutron port-list +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.2"} | | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.1"} | | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.114"} | | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": "10.48.146.113"} | | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": "192.168.1.3"} | +--------------------------------------+------+-------------------+???????????????????????????????????????????+ Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 5:02 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. What does 'neutron port-list' show ? On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: I did that, launch instance got IP: 192.168.1.2 then I did floating_IP which I got 10.48.146.114 , however I cannot assign to the instance as there are no ports avilable.? [cid:6447492F-6F53-4921-912B-DF3C14ECB8AA] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:52 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Next launch an instance with demo-net attached. Then assign it a floating IP. You should get 10.48.146.114 as the floating IP. On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: Thanks, I did this step . So what is next ? Sorry to bother but you are really a life saver to me (thanks to you a ton) as well kashyap . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:46 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. neutron net-create public --router:external=True neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 neutron net-create demo-net neutron subnet-create demo-net --name demo-subnet --gateway 192.168.1.1 192.168.1.0/24 neutron router-create demo-router neutron router-interface-add demo-router demo-subnet neutron router-gateway-set demo-router public On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: I have deleted all network (admin) and tenant as I wanted your guidance to do further Can you help to give steps to add the network again (10.48.146.0/24) and tenant 192.168.10.0/24 after floating ip to 10.48.146.113) Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:27 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Let's keep the troubleshooting steps on the list. What's the output of 'nova list' ? On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: Yes, I did boot the instance but its getting 10.48.146.4 address rather 192.168.*** that you gave me ? I can logon to the instance console 10.48.146.4 and can ping gateway 10.48.146.1 but I cannot ssh or ping from host? Is it possible I share my screen, so that you can guide me what wrong thing that stops and bother me ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:18 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Did you boot the instance with the demo-net attached ? On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > wrote: I can?t assign a port to the floating ip . I don?t? see any ports available ? [cid:CD828843-4C9C-442E-9F18-65F4084FCB55] Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 4:06 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. You've already defined router1 which is already connected to the external network. You can use that. ext-net is the 'public' network in your case. On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > wrote: I can?t run this command $ neutron router-gateway-set demo-router ext-net Its getting error (ext-net not found) ? What is the ext-net in this case ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:58 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Ok I did the folowing steps for tenant. 1) neutron net-create demo-net 2) neutron subnet-create demo-net --name demo-subnet --gateway 10.48.146.1 10.48.146.0/24 3) neutron router-create demo-router 4) neutron router-interface-add demo-router demo-subnet Anything left .? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: , SAP SAP > Date: Friday, January 9, 2015 at 3:55 PM To: Marius Cornea > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Marius, Yes, I can ping 10.48.146.113 (gateway) from the host , can you provide the comamnds or link to create tenant network, subjet and attach to router ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 3:48 PM To: SAP SAP > Cc: rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Can you ping 10.48.146.113 from your network? You also need to create a tenant network, subnet and attach it to the router. Boot the instance with the tenant network attached and then assign it the floating IP. On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > wrote: Hi Marius, I did this first and now can see the BR-ex is the same IP as my eno1 interface , you are right I lost first while doing the first command(ip addr del 10.48.146.77/24 dev eno1) and then conneting to console I did the second comand (ovs-vsctl add-port br-ex eno1 and also changed the IP address of br-ex to 10.48.146.77) ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 Then after I removed all the routers, networks and interfaces from openstack and ran the following 4 commands. 1) source /root/keystonerc_admin 2) neutron net-create public --router:external=True 3) neutron subnet-create public 10.48.146.0/24 --name vlan --enable_dhcp=False --allocation_pool start=10.48.146.113,end=10.48.146.130 --gateway 10.48.146.1 4) neutron router-create router1 5) neutron router-gateway-set 7e07fef0-e92b-4956-9b23-82157d81ebf3 1605ac0b-4f59-473d-b20f-911c3401dc2c 6) neutron floatingip-create public The above command generated a floating IP 10.48.146.115 Then I spin up a new instance and it got IP assigned automatically 10.48.146.115, howevr I cannot ping or ssh to that ip : 10.48.146.115 ? Here are the screenshots [cid:964628AC-2686-40F5-B655-00EAF252B65D] [cid:2B55990D-8C1A-445B-8C55-BF8428FCA0F2] [root at lspal117 ~(keystone_admin)]# neutron net-list +--------------------------------------+--------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+-----------------------------------------------------+ | 1605ac0b-4f59-473d-b20f-911c3401dc2c | public | 24f385ad-bfeb-4c62-91ff-ab8756d3983b 10.48.146.0/24 | +--------------------------------------+--------+??????????????????????????+ [root at lspal117 ~(keystone_admin)]# neutron subnet-list +--------------------------------------+------+----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+----------------+----------------------------------------------------+ | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | vlan | 10.48.146.0/24 | {"start": "10.48.146.113", "end": "10.48.146.130"} | +--------------------------------------+------+----------------+----------------------------------------------------+ [root at lspal117 ~(keystone_admin)]# neutron router-list +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | router1 | {"network_id": "1605ac0b-4f59-473d-b20f-911c3401dc2c", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "24f385ad-bfeb-4c62-91ff-ab8756d3983b", "ip_address": "10.48.146.113"}]} | False | False | +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ Any ideas what is going wrong, I still can?t ping or ssh to that IP address and its not listening anywhere ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 2:30 PM To: SAP SAP >, rdo-list > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. As Kashyap kindly suggested we're not a support line and information here should be available for all the community members. First, I don't see how you can ping the br-ex IP address from an external network since it doesn't contain any physical interface. Make sure that 10.48.146.112 isn't used by other host on you network segment. You can do the following to remove the ip address from the physical interface and add it to the br-ex bridge. Please make sure that you've got console access to the server before doing this as you may lose connectivity. # ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1 You should then follow the documentation[1] to recreate the public/tenant networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack routers/instances, then FLOATING_IP_START=10.48.146.200 and FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to what 'ip r | grep default | awk {'print $3'}' outputs and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24. Note that the instance will get an IP address of the tenant network. By assigning a floating IP you will be able to access it through an IP address from your physical network segment. [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > wrote: Hi Marius, Here are the outputs. Is it possible to reach you on phone so that I can explain more than email. You can call me at 650 849 3915 or let me know your number. #ip a [root at lspal117 network-scripts(keystone_admin)]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq state UP qlen 1000 link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::da9d:67ff:fe29:c694/64 scope link valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff 4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff 5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff 6: ens1f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff 7: ens1f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff 8: ens2f0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff 9: ens2f1: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff 10: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff 11: br-ex: mtu 1500 qdisc noqueue state UNKNOWN link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::bc8b:24ff:fe03:a947/64 scope link valid_lft forever preferred_lft forever 12: br-int: mtu 1500 qdisc noop state DOWN link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff 16: br-tun: mtu 1500 qdisc noop state DOWN link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff 17: qbr63bd6704-47: mtu 1500 qdisc noqueue state UP link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff inet6 fe80::3822:bcff:fe6a:b74f/64 scope link valid_lft forever preferred_lft forever 18: qvo63bd6704-47: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000 link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff 19: qvb63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000 link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff 22: tap63bd6704-47: mtu 1500 qdisc pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500 link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fed9:5eba/64 scope link valid_lft forever preferred_lft forever # ovs-vsctl show [root at lspal117 network-scripts(keystone_admin)]# ovs-vsctl show c5bcc161-86cd-4004-9729-c1ba05d28569 Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-c3a1b534-36" Interface "qg-c3a1b534-36" type: internal Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tape386c0cb-d8" tag: 1 Interface "tape386c0cb-d8" type: internal Port br-int Interface br-int type: internal Port "qvo63bd6704-47" tag: 1 Interface "qvo63bd6704-47" Port "tap44dd465f-d4" tag: 4095 Interface "tap44dd465f-d4" type: internal Port "qr-e0ac3c25-2b" tag: 2 Interface "qr-e0ac3c25-2b" type: internal Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: ?2.1.3" # neutron net-list [root at lspal117 network-scripts(keystone_admin)]# neutron net-list +--------------------------------------+---------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+------------------------------------------------------+ | 5abe660b-52da-4d36-8275-4c1488df88b4 | public | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 | | d825e820-66e5-44b1-a91d-0c660aa822a5 | private | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 | | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 | +--------------------------------------+---------+------------------------------------------------------+ # neutron subnet-list [root at lspal117 network-scripts(keystone_admin)]# neutron subnet-list +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+----------------+-----------------+----------------------------------------------------+ | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28 | {"start": "172.24.4.226", "end": "172.24.4.238"} | | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} | | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24 | {"start": "10.48.146.112", "end": "10.48.146.120"} | +--------------------------------------+----------------+-----------------+??????????????????????????+ #neutron router-list [root at lspal117 network-scripts(keystone_admin)]# neutron router-list +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | id | name | external_gateway_info | distributed | ha | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id": "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} | False | False | +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ In my system I have IP address for BR-ex and ENO1 (interface connecting ), should I disable eno1 as I can ping both (br-ex and eno1) from my network to reach to this host ? Probably its a dump question. Here are the outputs. br-ex: flags=4163 mtu 1500 inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20 ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet) RX packets 10 bytes 864 (864.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 3767 (3.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-int: flags=4098 mtu 1500 ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet) RX packets 135 bytes 7574 (7.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-tun: flags=4098 mtu 1500 ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255 inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20 ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet) RX packets 467319 bytes 48391354 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14794 bytes 5238733 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 32 Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race From: Marius Cornea > Date: Friday, January 9, 2015 at 1:46 PM To: SAP SAP > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. Hi Rushi, Can you provide the output of the following commands on your node ? # ip a # ovs-vsctl show # neutron net-list # neutron subnet-list # neutron router-list Please note that only the br-ex bridge requires an IP address, the interface that's part of it shouldn't have one assigned. Also the floating IP addresses will be used for DNAT on the tenant router. You can check the documentation here[1] that describes the use of floating IPs. You can also check the upstream documentation[2] on how to create the networks. [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP [2] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html Tnx, Marius On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi > wrote: Hi Support, I have a problem that a launched instance from openstack cannot connect to SSH or PING First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history. 1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart 2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range. My situtation is as follows. * Floating IP address assignment: I have assigned a floating IP , I did follow this steps. https://openstack.redhat.com/Floating_IP_range * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112 * DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed rule on default security group) Here is the little diagram of my system. [cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA] Can someone help to find what is missing. Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png Type: image/png Size: 44997 bytes Desc: 6447492F-6F53-4921-912B-DF3C14ECB8AA.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png Type: image/png Size: 91398 bytes Desc: 0E7F5284-9B90-46DA-B1CE-824110D267B8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png Type: image/png Size: 460559 bytes Desc: 9B3B10A4-4C8D-472C-9B21-C82D718CC6E0.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3DBCBF54-A0DD-43A7-A793-4E902C409617.png Type: image/png Size: 135378 bytes Desc: 3DBCBF54-A0DD-43A7-A793-4E902C409617.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 964628AC-2686-40F5-B655-00EAF252B65D.png Type: image/png Size: 73280 bytes Desc: 964628AC-2686-40F5-B655-00EAF252B65D.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg Type: image/jpeg Size: 31140 bytes Desc: EB813931-0B05-459C-A0B6-DE7C98D3D2FA.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CD828843-4C9C-442E-9F18-65F4084FCB55.png Type: image/png Size: 44700 bytes Desc: CD828843-4C9C-442E-9F18-65F4084FCB55.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png Type: image/png Size: 35381 bytes Desc: 2B55990D-8C1A-445B-8C55-BF8428FCA0F2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png Type: image/png Size: 61042 bytes Desc: 81EE88AC-CCAA-4B7B-A380-CF9DCAE5702F.png URL: From rbowen at redhat.com Mon Jan 12 20:13:19 2015 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 12 Jan 2015 15:13:19 -0500 Subject: [Rdo-list] Hangouts: Request for speakers Message-ID: <54B42ADF.6050305@redhat.com> I'd like to start doing some hangouts in the coming months leading up to Kilo, covering what we can expect to see coming in that release. If you're willing to give a 30 minute (or more) presentation on a particular OpenStack project, please let me know off-list, so that we can begin to schedule these and begin to educate people on what they can expect in April. Thanks. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From dsneddon at redhat.com Mon Jan 12 20:44:50 2015 From: dsneddon at redhat.com (Dan Sneddon) Date: Mon, 12 Jan 2015 12:44:50 -0800 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: <54B43242.5080204@redhat.com> On 01/12/2015 11:11 AM, Ns, Rushi wrote: > HI Marius > > I cannot run tcpdump on the VM? as it appear it doenst have the package > ? I have the same problem on the 3 images that I have instances (cirros, > suse , redhat) I am assuming something was not right on the network for > tenant ? > > Can you help me . Is is possible if I send you my LYNC share so that I > can show the screen ? > > Also I don?t see any router in Tenant (demo user) network ? Is that > required like below point 3 > I am reading all these from redhat ? Is there something that is not > correct in my configuration? > > > > * I can create an instance, but cannot SSH or ping it > o 1) Verify that traffic to port 22 and ICMP traffic of any type > (-1:-1) is allowed in the default security group > > In the dashboard, in the Project tab, under "Access and > Security", check the rules which are active on the security > group you are using with your instances (typically "default"). > You should see a rule allowing traffic to port 22 over tcp from > all hosts, and a port enabling icmp traffic of all types (-1). > If you don't, create the necessary rules, and try again. > > o 2) Verify that you can ping and SSH the host where the instance > is running > > From the host where you are attempting to connect to your > instance, verify that network traffic is being correctly routed > to the compute node in question. > > o 3) Ensure that the router is correctly created, that the > internal subnet and external subnet are attached to it, and that > it can route traffic from your IP to the instance IP > > If your VM is in the 192.168.1.x subnet, and the host from which > you are trying to connect is in the 192.168.0.x subnet, then you > will need to have a route from one to the other. Ensure that the > subnet 192.168.1.x and 192.168.0.x are both added to a router > which you create in Neutron > > o 4) Check that you can ping an instance from inside its network > namespace. > > If you are using network namespaces, then each VLAN will have > its own namespace, and entities inside that namespace will be > invisible from outside. You can check whether you can ping an > instance from inside the namespace by first finding the > namespace identifier, and then using the iproute toolset to > execute a "ping" inside that namespace: > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is > a matter of handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 6:01 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Well neutron uses iptables to implement the security groups so I'm not > sure what's the result of removing the iptables rules from the openstack > host. Since the ssh connection to 10.48.146.115 was getting a connection > refused I would have checked first the VM to see if any packets reach > its interface. You could do that by 'tcpdump -i {interface_name}' inside > the VM. > > On Sat, Jan 10, 2015 at 2:44 AM, Ns, Rushi > wrote: > > By the way, My openstack host is : REDHAT7 ? Do you think is there > any settings on sshd preventing to connet to VM (to check to see > this VM?? ssh ? ) > > I did checked and making sure iptables off on the openstack host ? > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 5:31 PM > > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > I did verified on the VM., > > No fiewall enable (this is suse create with SUSE Studio) > SSH is listening on the VM and I can ssh to the local host > > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 5:23 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > I see that you get a 'connection refused' message which means that > the VM responds. Is the ssh service running on the VM or is there > any firewall on the VM that might prevent connectivity? You could > run tcpdump inside the VM to see if any of your packets reach it. > > On Sat, Jan 10, 2015 at 2:18 AM, Ns, Rushi > wrote: > > Here are my allowed port list but I can?t ping or I can?t ssh ? > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 5:17 PM > > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Here is the console, I can ping gateway of my host : 10.48.146.1 > and others but I cannot ssh to that instance from oopensetack host. > > > [root at lspal117 tmp(keystone_admin)]# ssh -l root -i > lvmgrouplatest.pem 10.48.146.115 > ssh: connect to host 10.48.146.115 port 22: Connection refused > > > [root at lspal117 tmp(keystone_admin)]# ssh -l root -i > lvmgrouplatest.pem 192.168.1.4 > > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 5:12 PM > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Hi Marius, > > Sorry I can assign the floating ip to the instnace (demo user > launched insetance) , however I cannot ping or ssh to the > instances (192.168.1.4/ 10.48.146.115) > from the host but from the instance (192.168.1.2) I can ping > other instance 192.168.1.4 ? > > Can you help in this final step what is missing > > > > > > root at lspal117 tmp(keystone_admin)]# neutron port-list > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | id | name | mac_address > | fixed_ips > | > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | > fa:16:3e:61:95:bd | {"subnet_id": > "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.2"} | > | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | > fa:16:3e:64:da:11 | {"subnet_id": > "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.1"} | > | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | > fa:16:3e:25:2f:46 | {"subnet_id": > "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.114"} | > | 65d568f4-d737-4f35-ab47-13042e3b6733 | | > fa:16:3e:c9:dd:a9 | {"subnet_id": > "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.115"} | > | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | > fa:16:3e:25:73:00 | {"subnet_id": > "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.113"} | > | c02da939-99da-44c8-b462-9da7938626ba | | > fa:16:3e:83:9e:77 | {"subnet_id": > "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.4"} | > | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | > fa:16:3e:17:84:4c | {"subnet_id": > "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.3"} | > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 5:03 PM > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Here is it > > [root at lspal117 tmp(keystone_admin)]# neutron port-list > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | id | name | mac_address > | fixed_ips > | > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | > fa:16:3e:61:95:bd | {"subnet_id": > "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.2"} | > | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | > fa:16:3e:64:da:11 | {"subnet_id": > "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.1"} | > | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | > fa:16:3e:25:2f:46 | {"subnet_id": > "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.114"} | > | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | > fa:16:3e:25:73:00 | {"subnet_id": > "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.113"} | > | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | > fa:16:3e:17:84:4c | {"subnet_id": > "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.3"} | > +--------------------------------------+------+-------------------+???????????????????????????????????????????+ > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 5:02 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > What does 'neutron port-list' show ? > > On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: > > I did that, launch instance got IP: 192.168.1.2 then I did > floating_IP which I got 10.48.146.114 , however I cannot > assign to the instance as there are no ports avilable.? > > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the > race. Success is a matter of handling the worst & finishing > the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:52 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead > openstack. > > Next launch an instance with demo-net attached. Then assign > it a floating IP. You should get 10.48.146.114 as the > floating IP. > > On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: > > Thanks, I did this step . So what is next ? Sorry to > bother but you are really a life saver to me (thanks to > you a ton) as well kashyap . > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the > race. Success is a matter of handling the worst & > finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:46 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO > redhead openstack. > > neutron net-create public --router:external=True > neutron subnet-create public 10.48.146.0/24 > --name vlan --enable_dhcp=False > --allocation_pool start=10.48.146.113,end=10.48.146.130 > --gateway 10.48.146.1 > > neutron net-create demo-net > neutron subnet-create demo-net --name demo-subnet > --gateway 192.168.1.1 192.168.1.0/24 > > neutron router-create demo-router > neutron router-interface-add demo-router demo-subnet > neutron router-gateway-set demo-router public > > > On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > > wrote: > > I have deleted all network (admin) and tenant as I > wanted your guidance to do further > > Can you help to give steps to add the network again > (10.48.146.0/24 ) and tenant > 192.168.10.0/24 after > floating ip to 10.48.146.113) > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning > the race. Success is a matter of handling the worst > & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:27 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO > redhead openstack. > > Let's keep the troubleshooting steps on the list. > What's the output of 'nova list' ? > > On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > > wrote: > > Yes, I did boot the instance but its getting > 10.48.146.4 address rather 192.168.*** that you > gave me ? I can logon to the instance console > 10.48.146.4 and can ping gateway 10.48.146.1 but > I cannot ssh or ping from host? > > Is it possible I share my screen, so that you > can guide me what wrong thing that stops and > bother me ? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & > winning the race. Success is a matter of > handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:18 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on > JUNO redhead openstack. > > Did you boot the instance with the demo-net > attached ? > > On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > > wrote: > > I can?t assign a port to the floating ip . I > don?t? see any ports available ? > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & > winning the race. Success is a matter of > handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:06 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on > JUNO redhead openstack. > > You've already defined router1 which is > already connected to the external network. > You can use that. ext-net is the 'public' > network in your case. > > On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > > > wrote: > > I can?t run this command > > > $ neutron router-gateway-set demo-router > ext-net > > Its getting error (ext-net not found) ? > What is the ext-net in this case ? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the > best & winning the race. Success is a > matter of handling the worst & finishing > the race > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 3:58 PM > > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking > issues on JUNO redhead openstack. > > Ok I did the folowing steps for tenant. > > 1) neutron net-create demo-net > 2) neutron subnet-create demo-net > --name demo-subnet --gateway 10.48.146.1 > 10.48.146.0/24 > 3) neutron router-create demo-router > 4) neutron router-interface-add > demo-router demo-subnet > > Anything left .? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the > best & winning the race. Success is a > matter of handling the worst & finishing > the race > > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 3:55 PM > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking > issues on JUNO redhead openstack. > > Hi Marius, > > Yes, I can ping 10.48.146.113 (gateway) > from the host , can you provide the > comamnds or link to create tenant > network, subjet and attach to router ? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the > best & winning the race. Success is a > matter of handling the worst & finishing > the race > > > > From: Marius Cornea > > > Date: Friday, January 9, 2015 at 3:48 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking > issues on JUNO redhead openstack. > > Can you ping 10.48.146.113 from your > network? You also need to create a > tenant network, subnet and attach it to > the router. Boot the instance with the > tenant network attached and then assign > it the floating IP. > > > On Sat, Jan 10, 2015 at 12:20 AM, Ns, > Rushi > wrote: > > Hi Marius, > > I did this first and now can see the > BR-ex is the same IP as my eno1 > interface , you are right I lost > first while doing the first > command(ip addr del 10.48.146.77/24 > dev eno1) > and then conneting to console I did > the second comand (ovs-vsctl > add-port br-ex eno1 and also changed > the IP address of br-ex to > 10.48.146.77) > > ip addr del 10.48.146.77/24 > dev eno1; > ovs-vsctl add-port br-ex eno1 > > Then after I removed all the > routers, networks and interfaces > from openstack and ran the following > 4 commands. > > 1) source /root/keystonerc_admin > 2) neutron net-create public > --router:external=True > 3) neutron subnet-create public > 10.48.146.0/24 > --name vlan > --enable_dhcp=False > --allocation_pool > start=10.48.146.113,end=10.48.146.130 --gateway > 10.48.146.1 > 4) neutron router-create router1 > 5) neutron router-gateway-set > 7e07fef0-e92b-4956-9b23-82157d81ebf3 > 1605ac0b-4f59-473d-b20f-911c3401dc2c > 6) neutron floatingip-create public > > The above command generated a > floating IP 10.48.146.115 > > Then I spin up a new instance and it > got IP assigned automatically > 10.48.146.115, howevr I cannot ping > or ssh to that ip : 10.48.146.115 ? > > Here are the screenshots > > > > > [root at lspal117 ~(keystone_admin)]# > neutron net-list > +--------------------------------------+--------+-----------------------------------------------------+ > | id > | name | subnets > | > +--------------------------------------+--------+-----------------------------------------------------+ > | > 1605ac0b-4f59-473d-b20f-911c3401dc2c > | public | > 24f385ad-bfeb-4c62-91ff-ab8756d3983b > 10.48.146.0/24 | > +--------------------------------------+--------+??????????????????????????+ > > [root at lspal117 ~(keystone_admin)]# > neutron subnet-list > +--------------------------------------+------+----------------+----------------------------------------------------+ > | id > | name | cidr | > allocation_pools > | > +--------------------------------------+------+----------------+----------------------------------------------------+ > | > 24f385ad-bfeb-4c62-91ff-ab8756d3983b > | vlan | 10.48.146.0/24 > | {"start": > "10.48.146.113", "end": > "10.48.146.130"} | > +--------------------------------------+------+----------------+----------------------------------------------------+ > > [root at lspal117 > ~(keystone_admin)]#neutron router-list > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | id > | name | external_gateway_info > > > > > | distributed | > ha | > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | > 7e07fef0-e92b-4956-9b23-82157d81ebf3 > | router1 | {"network_id": > "1605ac0b-4f59-473d-b20f-911c3401dc2c", > "enable_snat": true, > "external_fixed_ips": [{"subnet_id": > "24f385ad-bfeb-4c62-91ff-ab8756d3983b", > "ip_address": "10.48.146.113"}]} | > False | False | > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > > Any ideas what is going wrong, I > still can?t ping or ssh to that IP > address and its not listening anywhere ? > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the > best & winning the race. Success is > a matter of handling the worst & > finishing the race > > > > From: Marius Cornea > > > Date: Friday, January 9, 2015 at 2:30 PM > To: SAP SAP >, rdo-list > > > > Subject: Re: [Rdo-list] networking > issues on JUNO redhead openstack. > > As Kashyap kindly suggested we're > not a support line and information > here should be available for all the > community members. First, I don't > see how you can ping the br-ex IP > address from an external network > since it doesn't contain any > physical interface. Make sure that > 10.48.146.112 isn't used by other > host on you network segment. You > can do the following to remove the > ip address from the physical > interface and add it to the br-ex > bridge. Please make sure that you've > got console access to the server > before doing this as you may lose > connectivity. > > # ip addr del 10.48.146.77/24 > dev eno1; > ovs-vsctl add-port br-ex eno1 > > You should then follow the > documentation[1] to recreate the > public/tenant networks and router. > In your > case FLOATING_IP_START, FLOATING_IP_END > should be part of the 10.48.146.0/24 > network. > Let's say you wish to allocate IP > addresses of the 10.48.146.200 - > 10.48.146.210 range to your > Openstack routers/instances, then > FLOATING_IP_START=10.48.146.200 and > FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY > should be set to what 'ip r | grep > default | awk {'print $3'}' outputs > and EXTERNAL_NETWORK_CIDR > is 10.48.146.0/24 > . > > Note that the instance will get an > IP address of the tenant network. By > assigning a floating IP you will be > able to access it through an IP > address from your physical network > segment. > > [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html > > > > On Fri, Jan 9, 2015 at 10:52 PM, Ns, > Rushi > wrote: > > Hi Marius, > > Here are the outputs. Is it > possible to reach you on phone > so that I can explain more than > email. You can call me at 650 > 849 3915 > or let me know your number. > > #ip a > > [root at lspal117 > network-scripts(keystone_admin)]# ip > a > 1: lo: > mtu 65536 qdisc noqueue state > UNKNOWN > link/loopback > 00:00:00:00:00:00 brd > 00:00:00:00:00:00 > inet 127.0.0.1/8 > scope host lo > valid_lft forever > preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever > preferred_lft forever > 2: eno1: > mtu > 1500 qdisc mq state UP qlen 1000 > link/ether d8:9d:67:29:c6:94 > brd ff:ff:ff:ff:ff:ff > inet 10.48.146.77/24 > brd > 10.48.146.255 scope global eno1 > valid_lft forever > preferred_lft forever > inet6 > fe80::da9d:67ff:fe29:c694/64 > scope link > valid_lft forever > preferred_lft forever > 3: eno2: > > mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether d8:9d:67:29:c6:95 > brd ff:ff:ff:ff:ff:ff > 4: eno3: > > mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether d8:9d:67:29:c6:96 > brd ff:ff:ff:ff:ff:ff > 5: eno4: > > mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether d8:9d:67:29:c6:97 > brd ff:ff:ff:ff:ff:ff > 6: ens1f0: > > mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether 38:ea:a7:8f:bf:b4 > brd ff:ff:ff:ff:ff:ff > 7: ens1f1: > > mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether 38:ea:a7:8f:bf:b5 > brd ff:ff:ff:ff:ff:ff > 8: ens2f0: > > mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether 38:ea:a7:8f:bf:40 > brd ff:ff:ff:ff:ff:ff > 9: ens2f1: > > mtu 1500 qdisc mq state DOWN > qlen 1000 > link/ether 38:ea:a7:8f:bf:41 > brd ff:ff:ff:ff:ff:ff > 10: ovs-system: > mtu 1500 > qdisc noop state DOWN > link/ether 16:02:ac:3f:05:f4 > brd ff:ff:ff:ff:ff:ff > 11: br-ex: > mtu > 1500 qdisc noqueue state UNKNOWN > link/ether be:8b:24:03:a9:47 > brd ff:ff:ff:ff:ff:ff > inet 10.48.146.112/24 > brd > 10.48.146.255 scope global br-ex > valid_lft forever > preferred_lft forever > inet6 > fe80::bc8b:24ff:fe03:a947/64 > scope link > valid_lft forever > preferred_lft forever > 12: br-int: > mtu 1500 > qdisc noop state DOWN > link/ether 02:35:a4:7c:e5:4c > brd ff:ff:ff:ff:ff:ff > 16: br-tun: > mtu 1500 > qdisc noop state DOWN > link/ether fe:61:30:fb:a3:47 > brd ff:ff:ff:ff:ff:ff > 17: qbr63bd6704-47: > mtu > 1500 qdisc noqueue state UP > link/ether 8e:fe:6e:19:61:5c > brd ff:ff:ff:ff:ff:ff > inet6 > fe80::3822:bcff:fe6a:b74f/64 > scope link > valid_lft forever > preferred_lft forever > 18: qvo63bd6704-47: > > mtu 1500 qdisc pfifo_fast master > ovs-system state UP qlen 1000 > link/ether a2:fe:04:5f:04:b4 > brd ff:ff:ff:ff:ff:ff > 19: qvb63bd6704-47: > > mtu 1500 qdisc pfifo_fast master > qbr63bd6704-47 state UP qlen 1000 > link/ether 8e:fe:6e:19:61:5c > brd ff:ff:ff:ff:ff:ff > 22: tap63bd6704-47: > mtu > 1500 qdisc pfifo_fast master > qbr63bd6704-47 state UNKNOWN > qlen 500 > link/ether fe:16:3e:d9:5e:ba > brd ff:ff:ff:ff:ff:ff > inet6 > fe80::fc16:3eff:fed9:5eba/64 > scope link > valid_lft forever > preferred_lft forever > > # ovs-vsctl show > > [root at lspal117 > network-scripts(keystone_admin)]# ovs-vsctl > show > c5bcc161-86cd-4004-9729-c1ba05d28569 > Bridge br-ex > Port br-ex > Interface br-ex > type: internal > Port "qg-c3a1b534-36" > Interface > "qg-c3a1b534-36" > type: internal > Bridge br-int > fail_mode: secure > Port patch-tun > Interface patch-tun > type: patch > options: > {peer=patch-int} > Port "tape386c0cb-d8" > tag: 1 > Interface > "tape386c0cb-d8" > type: internal > Port br-int > Interface br-int > type: internal > Port "qvo63bd6704-47" > tag: 1 > Interface > "qvo63bd6704-47" > Port "tap44dd465f-d4" > tag: 4095 > Interface > "tap44dd465f-d4" > type: internal > Port "qr-e0ac3c25-2b" > tag: 2 > Interface > "qr-e0ac3c25-2b" > type: internal > Bridge br-tun > Port br-tun > Interface br-tun > type: internal > Port patch-int > Interface patch-int > type: patch > options: > {peer=patch-tun} > ovs_version: ?2.1.3" > > # neutron net-list > [root at lspal117 > network-scripts(keystone_admin)]# neutron > net-list > +--------------------------------------+---------+------------------------------------------------------+ > | id > | name | subnets > > | > +--------------------------------------+---------+------------------------------------------------------+ > | > 5abe660b-52da-4d36-8275-4c1488df88b4 > | public | > 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a > 172.24.4.224/28 > | > | > d825e820-66e5-44b1-a91d-0c660aa822a5 > | private | > f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 > 10.0.0.0/24 > | > | > 6eb6d123-8fec-4984-986a-5eeabf895883 > | sap | > ea2b21e0-bf9f-4195-b210-b75b6f9f7943 > 10.48.146.0/24 > | > +--------------------------------------+---------+------------------------------------------------------+ > > # neutron subnet-list > [root at lspal117 > network-scripts(keystone_admin)]# neutron > subnet-list > +--------------------------------------+----------------+-----------------+----------------------------------------------------+ > | id > | name | cidr > | allocation_pools > | > +--------------------------------------+----------------+-----------------+----------------------------------------------------+ > | > 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a > | public_subnet | > 172.24.4.224/28 > | > {"start": "172.24.4.226", "end": > "172.24.4.238"} | > | > f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 > | private_subnet | 10.0.0.0/24 > | > {"start": "10.0.0.2", "end": > "10.0.0.254"} | > | > ea2b21e0-bf9f-4195-b210-b75b6f9f7943 > | sap_local | > 10.48.146.0/24 > | > {"start": "10.48.146.112", > "end": "10.48.146.120"} | > +--------------------------------------+----------------+-----------------+??????????????????????????+ > > #neutron router-list > [root at lspal117 > network-scripts(keystone_admin)]# neutron > router-list > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | id > | name | > external_gateway_info > > > > > | > distributed | ha | > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | > d6325c88-e5b0-448e-8ab1-af5908a189d4 > | router1 | {"network_id": > "5abe660b-52da-4d36-8275-4c1488df88b4", > "enable_snat": true, > "external_fixed_ips": > [{"subnet_id": > "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", > "ip_address": "172.24.4.226"}]} > | False | False | > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ > > In my system I have IP address > for BR-ex and ENO1 (interface > connecting ), should I disable > eno1 as I can ping both (br-ex > and eno1) from my network to > reach to this host ? Probably > its a dump question. > > Here are the outputs. > > br-ex: > flags=4163 > mtu 1500 > inet 10.48.146.112 > netmask 255.255.255.0 > broadcast 10.48.146.255 > inet6 > fe80::bc8b:24ff:fe03:a947 > prefixlen 64 scopeid 0x20 > ether be:8b:24:03:a9:47 > txqueuelen 0 (Ethernet) > RX packets 10 bytes 864 > (864.0 B) > RX errors 0 dropped 0 > overruns 0 frame 0 > TX packets 25 bytes > 3767 (3.6 KiB) > TX errors 0 dropped 0 > overruns 0 carrier 0 collisions 0 > > br-int: > flags=4098 > mtu 1500 > ether 02:35:a4:7c:e5:4c > txqueuelen 0 (Ethernet) > RX packets 135 bytes > 7574 (7.3 KiB) > RX errors 0 dropped 0 > overruns 0 frame 0 > TX packets 0 bytes 0 > (0.0 B) > TX errors 0 dropped 0 > overruns 0 carrier 0 collisions 0 > > br-tun: > flags=4098 > mtu 1500 > ether fe:61:30:fb:a3:47 > txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 > (0.0 B) > RX errors 0 dropped 0 > overruns 0 frame 0 > TX packets 0 bytes 0 > (0.0 B) > TX errors 0 dropped 0 > overruns 0 carrier 0 collisions 0 > > eno1: > flags=4163 > mtu 1500 > inet 10.48.146.77 > netmask 255.255.255.0 > broadcast 10.48.146.255 > inet6 > fe80::da9d:67ff:fe29:c694 > prefixlen 64 scopeid 0x20 > ether d8:9d:67:29:c6:94 > txqueuelen 1000 (Ethernet) > RX packets 467319 bytes > 48391354 (46.1 MiB) > RX errors 0 dropped 0 > overruns 0 frame 0 > TX packets 14794 bytes > 5238733 (4.9 MiB) > TX errors 0 dropped 0 > overruns 0 carrier 0 collisions 0 > device interrupt 32 > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being > the best & winning the race. > Success is a matter of handling > the worst & finishing the race > > > > From: Marius Cornea > > > Date: Friday, January 9, 2015 at > 1:46 PM > To: SAP SAP > > Subject: Re: [Rdo-list] > networking issues on JUNO > redhead openstack. > > Hi Rushi, > > Can you provide the output of > the following commands on your > node ? > > # ip a > # ovs-vsctl show > # neutron net-list > # neutron subnet-list > # neutron router-list > > Please note that only the br-ex > bridge requires an IP address, > the interface that's part of it > shouldn't have one assigned. > Also the floating IP addresses > will be used for DNAT on the > tenant router. You can check the > documentation here[1] that > describes the use of floating IPs. > > You can also check the upstream > documentation[2] on how to > create the networks. > > [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP > [2] > http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html > > Tnx, > Marius > > On Fri, Jan 9, 2015 at 10:22 PM, > Ns, Rushi > wrote: > > Hi Support, > > I have a problem that a > launched instance from > openstack cannot connect to > SSH or PING > > First of all I have dump > question whether my system > should be NOVA network or > Neutron network. Well to > keep everyone on the same > page. Here is my history. > > 1. I did install RDO > (allinone host) using > the bellow steps > https://openstack.redhat.com/Quickstart > 2. Then I have used the > following steps for > floating > IP https://openstack.redhat.com/Floating_IP_range. > > My situtation is as follows. > * Floating IP address > assignment: > I have assigned a floating > IP , I did follow this steps. > https://openstack.redhat.com/Floating_IP_range > > * Bridge configuration:My > Ethernet device > eth0(actually in Redhat 7 it > is eno1 name)is on the same > bridge as the compute host > Yes, ethernet device on > 10.48.146.78 address and > br-ex interface on > 10.48.146.112 > > * DHCP configuration: Yes, > DHCP configuration is set > and Neutron hearing and > responding to DHCP > requests and the instance is > getting IP from > 10.48.146.113 (next hop) > however I cannot ping/ssh to > that IP address (ICMP/SSH is > added allowed > rule on default security group) > > Here is the little diagram > of my system. > > Can someone help to find > what is missing. > > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of > being the best & winning the > race. Success is a matter of > handling the worst & > finishing the race > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > > > > > > > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > I think you are not understanding how floating IPs work. The VM will not be attached to the public network at all. The VMs will be attached to a tenant network (demo-net). A router will be attached to demo-net and the public net. A floating IP will allow NAT between the floating IP and the VM IP on the demo-net. Steps: 1) Create demo-net, assign subnet with private IPs 2) Create public net, assign subnet with public IPs 3) Create a router attached to demo-net and public 4) Launch a VM with an interface on the demo-net 5) Create a floating IP, and assign it to the port that the VM uses on the demo-net Only the routers get attached directly to the public net, and the floating IPs are just NAT addresses on the public net that get forwarded to the VM. Also, when the VM tries to access the Internet, NAT will change the source address of the traffic to make it the floating IP. From the outside world, it will look like the floating IP is actually the VM IP, but the VM is really using a private IP on the demo-net. -- Dan Sneddon | Principal OpenStack Engineer dsneddon at redhat.com | redhat.com/openstack 650.254.4025 | @dxs on twitter -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From hguemar at fedoraproject.org Tue Jan 13 00:06:32 2015 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Tue, 13 Jan 2015 01:06:32 +0100 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: As Alan said, we're willing to support a community Juno/EL6 effort, but this is a little more than just rebuilding packages. That includes packaging and maintaining missing dependencies on EL6. At some point, you'll want to migrate to Kilo or later releases, and by that time, you should consider moving to EL7. Bringing Kilo to EL6 is too much work for little gain (and you'll miss features from newer kernels & stuff anyway) H. From mriedem at linux.vnet.ibm.com Tue Jan 13 03:27:09 2015 From: mriedem at linux.vnet.ibm.com (Matt Riedemann) Date: Mon, 12 Jan 2015 21:27:09 -0600 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: Message-ID: <54B4908D.4090807@linux.vnet.ibm.com> On 1/12/2015 6:06 PM, Ha?kel wrote: > As Alan said, we're willing to support a community Juno/EL6 effort, but > this is a little more than just rebuilding packages. > That includes packaging and maintaining missing dependencies on EL6. > > At some point, you'll want to migrate to Kilo or later releases, and by that > time, you should consider moving to EL7. > Bringing Kilo to EL6 is too much work for little gain (and you'll miss > features from newer kernels & stuff anyway) > > H. > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > I'm not using RDO but our team has packaged Juno just fine on RHEL 6.5 with additional packages from epel 6, plus probably some updated source packages that aren't in the fedora repos to satisfy runtime dependencies, e.g. various oslo libraries. For Kilo we've moved to RHEL 7 mainly because of the support for python 2.7 being dropped in the community, nova has explicitly broken support for py27 for example, so unless you're going to maintain patches to revert those changes the code at runtime might have problems on py26. -- Thanks, Matt Riedemann From dpkshetty at gmail.com Tue Jan 13 06:52:13 2015 From: dpkshetty at gmail.com (Deepak Shetty) Date: Tue, 13 Jan 2015 12:22:13 +0530 Subject: [Rdo-list] [Manila] Don't see python-manilaclient package In-Reply-To: References: <54B3BC33.1040504@fedoraproject.org> Message-ID: Haikel, I am new to RDO, any idea when would that next refresh be ? I believe it will get into the testing-updates repo or is the process different for RDO In other words, Do I need to add a new repo to my RDO setup to pull the latest RPM ? On Mon, Jan 12, 2015 at 8:26 PM, Ha?kel wrote: > @Deepak: rebuilt and merged, it should be included in the RDO > repository during the next refresh. > > Regards, > H. > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at gmail.com Tue Jan 13 11:37:54 2015 From: apevec at gmail.com (Alan Pevec) Date: Tue, 13 Jan 2015 12:37:54 +0100 Subject: [Rdo-list] [Manila] Don't see python-manilaclient package In-Reply-To: References: <54B3BC33.1040504@fedoraproject.org> Message-ID: > I am new to RDO, any idea when would that next refresh be ? There aren't scheduled refreshes, we push updates when they pass rdopkg CI update process [1]. This is currently running on internal RHT systems and we're working on opening it up for external contributors, tasks are tracked on a public board [2] Haikel's manilaclient has passed Phase1 and Phase2 will run today on queued updates. I'll update this thread when updates hit the public repo. In the meantime, you can grab the el7 package from Copr [3] Cheers, Alan [1] http://apevec.github.io/rdo-intro.html#8 [2] https://trello.com/b/HhXlqdiu/rdo [3] https://copr-be.cloud.fedoraproject.org/results/jruzicka/rdo-juno-epel-7/epel-7-x86_64/python-manilaclient-1.0.1-3.el7/ From rbowen at redhat.com Tue Jan 13 15:12:05 2015 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 13 Jan 2015 10:12:05 -0500 Subject: [Rdo-list] RDO at the CentOS Dojo in Brussels, pre-FOSDEM Message-ID: <54B535C5.50806@redhat.com> In case you're not on the various CentOS mailing lists: If you're coming to FOSDEM in a few weeks, you should make time to come to the CentOS Dojo on Friday, where there will be, among other great content, the following: OpenStack Quickstart with RDO on CentOS :: Ha?kel Guemar CentOS Linux 7 is a great platform for running OpenStack and in this two hour session we will introduce the basics of OpenStack and run through a demo of installing !RDO ( http://openstack.redhat.com ) on CentOS Linux 7. The session will run in a tutorial format, so everyone with a laptop in the audience will be able to join and implement their own OpenStack in a VM. The focus will be on ensuring everyone has a basic setup, to include: Nova : The OpenStack Compute platform Glance : The OpenStack image delivery service Keystone : The OpenStack identity and authentication service Horizon : The OpenStack Web based management interface We will finish the session with a 15 min speaker session on how to get involved with RDO development, packaging and testing and what the CentOS Cloud SIG is doing in this area. In order to run the tutorial on your machine, we recommend a VM on your laptop that has 20GB+ of disk space, 2GB of ram and atleast 1 dedicated cpu core. If your laptop has the ability to run nested-virt, please enable that and use it. It will make a large difference to performance of the overall setup. We would also like to request everyone to setup these VMs ahead of time, in either KVM or Xen or any other virtualisation technology you might use. A basic CentOS-7 minimal install is sufficient to start from. More details about the CentOS Dojo may be found at http://wiki.centos.org/Events/Dojo/Brussels2015 We hope to see you there! -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From kchamart at redhat.com Tue Jan 13 16:13:05 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Tue, 13 Jan 2015 17:13:05 +0100 Subject: [Rdo-list] RDO at the CentOS Dojo in Brussels, pre-FOSDEM In-Reply-To: <54B535C5.50806@redhat.com> References: <54B535C5.50806@redhat.com> Message-ID: <20150113161305.GI5466@tesla.redhat.com> On Tue, Jan 13, 2015 at 10:12:05AM -0500, Rich Bowen wrote: [. . .] > In order to run the tutorial on your machine, we recommend a VM on your > laptop that has 20GB+ of disk space, 2GB of ram Rich, 2GB of memory won't suffice, I'm afraid. Why? In a DevStack environment (a more restricted developer setup) with a single Nova instance (running CirrOS), here's the memory profile of services that consume more than 70MB, namely: (Note, I removed out other serivces like systemd, libvirt, etc below, they're noted here[1]). $ sudo ps_mem Private + Shared = RAM used Program [. . .] Nova, Python process, MariaDB, Glance: 69.1 MiB + 990.5 KiB = 70.1 MiB nova-cert 71.4 MiB + 990.0 KiB = 72.4 MiB nova-scheduler 76.7 MiB + 820.0 KiB = 77.5 MiB ovs-vswitchd 90.4 MiB + 2.6 MiB = 93.0 MiB qemu-system-x86_64 64.1 MiB + 57.3 MiB = 121.3 MiB glance-api (5) 116.6 MiB + 59.6 MiB = 176.2 MiB glance-registry (9) 180.6 MiB + 385.0 KiB = 181.0 MiB mysqld 373.2 MiB + 108.1 MiB = 481.3 MiB nova-api (13) 407.5 MiB + 78.5 MiB = 486.0 MiB python2.7 (22) 571.3 MiB + 17.2 MiB = 588.5 MiB nova-conductor (9) --------------------------------- 2.3 GiB ================================= So, given the above, I'd suggest the virtual machine has at-least 4 GB or above memory to have a reasonably smooth experience of bringing up a Nova instance. [1] https://kashyapc.fedorapeople.org/virt/openstack/DevStack-memory-profile.txt > and atleast 1 dedicated cpu > core. If your laptop has the ability to run nested-virt, please enable that > and use it. It will make a large difference to performance of the overall > setup. Yep, that's correct. -- /kashyap From rbowen at redhat.com Tue Jan 13 17:07:57 2015 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 13 Jan 2015 12:07:57 -0500 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: <54B38988.5080601@cern.ch> References: <54B38988.5080601@cern.ch> Message-ID: <54B550ED.6050201@redhat.com> On 01/12/2015 03:44 AM, Thomas Oulevey wrote: > Hi David, > > We have a lot of interest in the Juno for el6 packages at CERN. > > It would be great if you can share the patches and we can work together > to build it in a central way. > > What is your approach in the current patchset ? rebuild python 2.7 or > patch openstack to work with python 2.6 ? > > I am working as well with the CentOS team. I am part of the team that > maintain the build system > (http://wiki.centos.org/HowTos/CommunityBuildSystem). RDO started to > rebuild their packages with this system for the cloud SIG effort > (http://wiki.centos.org/SpecialInterestGroup/Cloud). I'll let Rich or > someone more involved in the cloud sig to comment on this effort as I > have not all latest details/plan. It's really great to have you all step up to do this, and we want to help in any way we can getting you started. The packaging docs are at https://openstack.redhat.com/packaging/ and hopefully that's enough to get started, but we acknowledge that it's a work in progress and needs help. If there's anything you need, or anyone's attention you're having trouble getting, please ping me and I'll be glad to help make things happen. Will you be at FOSDEM? -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From Brian.Afshar at emc.com Tue Jan 13 22:43:50 2015 From: Brian.Afshar at emc.com (Afshar, Brian) Date: Tue, 13 Jan 2015 17:43:50 -0500 Subject: [Rdo-list] Glance filesystem_store_datadir Message-ID: <9E8EE5E176B2BD49913B2F69B369AD8302136BD803@MX02A.corp.emc.com> Can somebody provide an example of how we can specify multiple directories for Filesystem_store_datadir in glance-api.conf file? The section for "Filesystem Store Options" indicates the following: # Directory that the Filesystem backend store writes image data to filesystem_store_datadir=/var/lib/glance/images/ # A list of directories where image data can be stored. # This option may be specified multiple times for specifying multiple store directories. Either one of filesystem_store_datadirs or # filesystem_store_datadir option is required. A priority number may be given after each directory entry, separated by a ":". Is this a correct format? /var/lib/glance/images/: /var/lib/glance/images1/. If this is incorrect please provide the correct format. Regards, -Brian From dpkshetty at gmail.com Wed Jan 14 05:35:20 2015 From: dpkshetty at gmail.com (Deepak Shetty) Date: Wed, 14 Jan 2015 11:05:20 +0530 Subject: [Rdo-list] Glance filesystem_store_datadir In-Reply-To: <9E8EE5E176B2BD49913B2F69B369AD8302136BD803@MX02A.corp.emc.com> References: <9E8EE5E176B2BD49913B2F69B369AD8302136BD803@MX02A.corp.emc.com> Message-ID: Per http://docs.openstack.org/juno/config-reference/content/section_glance-api.conf.html (line 450 onwards) "Either one of filesystem_store_datadirs or # filesystem_store_datadir option is required." So if you want to specify multiple dirs, i think it should be like this: filesystem_store_datadirs = /var/lib/glance/images1/:1 filesystem_store_datadirs = /var/lib/glance/images2/:2 and so on thanx, deepak On Wed, Jan 14, 2015 at 4:13 AM, Afshar, Brian wrote: > Can somebody provide an example of how we can specify multiple directories > for Filesystem_store_datadir in glance-api.conf file? > > The section for "Filesystem Store Options" indicates the following: > # Directory that the Filesystem backend store writes image data to > filesystem_store_datadir=/var/lib/glance/images/ > # A list of directories where image data can be stored. > # This option may be specified multiple times for specifying multiple > store directories. Either one of filesystem_store_datadirs or # > filesystem_store_datadir option is required. A priority number may be given > after each directory entry, separated by a ":". > > Is this a correct format? > > /var/lib/glance/images/: /var/lib/glance/images1/. If this is incorrect > please provide the correct format. > > Regards, > -Brian > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at gmail.com Wed Jan 14 11:38:35 2015 From: apevec at gmail.com (Alan Pevec) Date: Wed, 14 Jan 2015 12:38:35 +0100 Subject: [Rdo-list] RDO Packaging IRC meeting Message-ID: Hi all, I propose to have an IRC meeting today 1500 UTC. Sorry for the short notice, we can discuss format/time on IRC and move discussion on the list. Scheduling is always a challenge so let's see how this works :) I've put proposed agenda at https://etherpad.openstack.org/p/RDO-Packaging please add topics if you have them! Cheers, Alan From hguemar at fedoraproject.org Wed Jan 14 16:07:51 2015 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Wed, 14 Jan 2015 17:07:51 +0100 Subject: [Rdo-list] [meeting] RDO Packaging meeting minutes (2015-01-14) Message-ID: ======================================== #rdo: RDO Packaging meeting (2015-01-15) ======================================== Meeting started by number80 at 15:00:44 UTC. The full logs are available at http://meetbot.fedoraproject.org/rdo/2015-01-14/rdo.2015-01-14-15.00.log.html . Meeting summary --------------- * roll call (number80, 15:00:59) * pending RDO updates (number80, 15:07:00) * LINK: https://etherpad.openstack.org/p/RDO-Packaging (rbowen, 15:07:44) * LINK: https://etherpad.openstack.org/p/RDO-Packaging (number80, 15:08:22) * apevec will post update on what's in the queue until RDO CI goes public (number80, 15:09:25) * RDO CI: phase1: smoke test, phase2: full tempest run, and then there is one more CI on the stage repo before pushing (apevec, 15:12:21) * public trello board for tracking task (number80, 15:13:00) * https://trello.com/b/HhXlqdiu/rdo (apevec, 15:13:14) * EL6 Juno (number80, 15:15:03) * ACTION: apevec moving forward the EL6/Juno discussion to the list (number80, 15:19:04) * ACTION: apevec contact RH Legal about patch sent through mailing-list (number80, 15:20:55) * LINK: https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement (number80, 15:24:03) * rdopkg update CI public (number80, 15:29:21) * ACTION: apevec eggmaster jruzicka to switch rdo-update.git to public gerrit next week (apevec, 15:45:01) * LINK: http://wiki.centos.org/QaWiki/PubHardware (number80, 15:49:28) * Kilo milestone packages (number80, 15:50:26) * ACTION: kbsingh to work with weshay to get rdo-ci access to a node on ci.centos.org (rbowen, 15:54:28) * ACTION: gchamoul to look at making Packstack working against Delorean repo for Kilo snapshots (apevec, 15:55:59) * public RDO call (number80, 15:57:26) * ACTION: slinaber to start email thread describing current rdopkg CI setup (eggmaster, 15:59:59) * RDO irc weekly status will be every wednesday at 15:00 UTC on #rdo at freenode (number80, 16:00:29) * ACTION: apevec to post conf# details to try Bluejeans next week (apevec, 16:00:50) * open discussions (number80, 16:01:51) Meeting ended at 16:03:43 UTC. Action Items ------------ * apevec moving forward the EL6/Juno discussion to the list * apevec contact RH Legal about patch sent through mailing-list * apevec eggmaster jruzicka to switch rdo-update.git to public gerrit next week * kbsingh to work with weshay to get rdo-ci access to a node on ci.centos.org * gchamoul to look at making Packstack working against Delorean repo for Kilo snapshots * slinaber to start email thread describing current rdopkg CI setup * apevec to post conf# details to try Bluejeans next week Action Items, by person ----------------------- * apevec * apevec moving forward the EL6/Juno discussion to the list * apevec contact RH Legal about patch sent through mailing-list * apevec eggmaster jruzicka to switch rdo-update.git to public gerrit next week * apevec to post conf# details to try Bluejeans next week * eggmaster * apevec eggmaster jruzicka to switch rdo-update.git to public gerrit next week * gchamoul * gchamoul to look at making Packstack working against Delorean repo for Kilo snapshots * jruzicka * apevec eggmaster jruzicka to switch rdo-update.git to public gerrit next week * kbsingh * kbsingh to work with weshay to get rdo-ci access to a node on ci.centos.org * weshay * kbsingh to work with weshay to get rdo-ci access to a node on ci.centos.org * **UNASSIGNED** * slinaber to start email thread describing current rdopkg CI setup People Present (lines said) --------------------------- * apevec (100) * number80 (61) * eggmaster (44) * kashyap (26) * weshay (25) * rbowen (19) * kbsingh (17) * jruzicka (16) * zodbot (12) * gchamoul (7) * mrunge (1) * chandankumar (1) * DV (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From invite at bluejeans.com Wed Jan 14 16:50:38 2015 From: invite at bluejeans.com (Alan Pevec via Blue Jeans Network) Date: Wed, 14 Jan 2015 16:50:38 +0000 (UTC) Subject: [Rdo-list] RDO meeting Message-ID: <1733521424.204141421254238269.JavaMail.denimuser@sj1-app-01-14> Alan Pevec (apevec at redhat.com) has invited you to a video meeting. To join from a Red Hat Deskphone or Softphone, dial: 84336. Meeting Title: RDO meeting Meeting Time: Every 2nd week on Wednesday from January 21, 2015 3 p.m. GMT / 1 hr ************************************************ To join or start the meeting, go to: https://bluejeans.com/948098149?ll=en&g=ojsg6llmnfzxiqdsmvsgqylufzrw63i= Connecting directly from a room system? 1) Dial: 199.48.152.152 or bjn.vc 2) Enter Meeting ID: 948098149 -or- use the pairing code Just want to dial in? (https://www.intercallonline.com/listNumbersByCode.action?confCode=4929648579) 1) +442035746870 2) Enter Meeting ID: 4929648579 ************************************************ First time joining a Blue Jeans Video Meeting? http://bluejeans.com/support ************************************************ Want to test your video connection? http://bluejeans.com/111 ************************************************ Visit bluejeans.com ************************************************ Blue Jeans Network 2014 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1943 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1943 bytes Desc: not available URL: From rbowen at redhat.com Wed Jan 14 19:42:57 2015 From: rbowen at redhat.com (Rich Bowen) Date: Wed, 14 Jan 2015 14:42:57 -0500 Subject: [Rdo-list] Hangout: What's coming for Ceilometer in Kilo. February 9th Message-ID: <54B6C6C1.6080405@redhat.com> Mark your calendars: On February 9th, at 14:00 UTC, Eoghan Glynn will present a hangout covering what's coming for Ceilometer in the Kilo release of OpenStack. https://plus.google.com/events/cht3k5nr5u73pv3d08i7vq5m570 Kilo milestone 2 is due on February 5, so this is traditionally around the time that mid-cycle meetings happen to evaluate the status of projects, and set expectations for what will actually make it into the release. So I hope that we'll be able to schedule more of these hangouts in time between Milestone 2 and the release on April 30th. (See https://wiki.openstack.org/wiki/Kilo_Release_Schedule for the release schedule.) -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From dneary at redhat.com Wed Jan 14 20:05:25 2015 From: dneary at redhat.com (Dave Neary) Date: Wed, 14 Jan 2015 15:05:25 -0500 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: <54B6CC05.8080105@redhat.com> Hi, Have you checked the security rules to ensure that port 22 (ssh), port 80 (http) and ICMP are all allowed through to the instance? Tose rules are not enforces in the instance, they're enforced with iptables in the host. You might also try to connect to the instance from inside the same network namespace - just to check that you can. On the host, as root: ip netns list # Identify the network namespace corresponding to your instance # - look for a qrouter namespace # - List all of the routes in the namespace ip netns exec qrouter-1fabd5f0-f80b-468d-b733-1b80d0c3e80f \ ip r # ssh into guest $ ip netns exec qdhcp-4a04382f-03bf-49a9-9d4a-35ab9ffc22ad ssh cirros@${instance_ip_addr} This will at least eliminate the possibility that your instance is somehow broken. Thanks, Dave. On 01/09/2015 08:12 PM, Ns, Rushi wrote: > Hi Marius, > > Sorry I can assign the floating ip to the instnace (demo user launched > insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ > 10.48.146.115) from the host but from the instance (192.168.1.2) I can > ping other instance 192.168.1.4 ? > > Can you help in this final step what is missing > > > > > > root at lspal117 tmp(keystone_admin)]# neutron port-list > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | id | name | mac_address | > fixed_ips > | > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.2"} | > | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.1"} | > | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.114"} | > | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.115"} | > | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.113"} | > | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.4"} | > | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.3"} | > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is > a matter of handling the worst & finishing the race > > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 5:03 PM > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Here is it > > [root at lspal117 tmp(keystone_admin)]# neutron port-list > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | id | name | mac_address | > fixed_ips > | > +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ > | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.2"} | > | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.1"} | > | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.114"} | > | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | > {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": > "10.48.146.113"} | > | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | > {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": > "192.168.1.3"} | > +--------------------------------------+------+-------------------+???????????????????????????????????????????+ > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is > a matter of handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 5:02 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > What does 'neutron port-list' show ? > > On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > wrote: > > I did that, launch instance got IP: 192.168.1.2 then I did > floating_IP which I got 10.48.146.114 , however I cannot assign to > the instance as there are no ports avilable.? > > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:52 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > Next launch an instance with demo-net attached. Then assign it a > floating IP. You should get 10.48.146.114 as the floating IP. > > On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > wrote: > > Thanks, I did this step . So what is next ? Sorry to bother but > you are really a life saver to me (thanks to you a ton) as well > kashyap . > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:46 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. > > neutron net-create public --router:external=True > neutron subnet-create public 10.48.146.0/24 > --name vlan --enable_dhcp=False > --allocation_pool start=10.48.146.113,end=10.48.146.130 > --gateway 10.48.146.1 > > neutron net-create demo-net > neutron subnet-create demo-net --name demo-subnet --gateway > 192.168.1.1 192.168.1.0/24 > > neutron router-create demo-router > neutron router-interface-add demo-router demo-subnet > neutron router-gateway-set demo-router public > > > On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > wrote: > > I have deleted all network (admin) and tenant as I wanted > your guidance to do further > > Can you help to give steps to add the network again > (10.48.146.0/24 ) and tenant > 192.168.10.0/24 after floating ip > to 10.48.146.113) > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the > race. Success is a matter of handling the worst & finishing > the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:27 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO redhead > openstack. > > Let's keep the troubleshooting steps on the list. What's the > output of 'nova list' ? > > On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > wrote: > > Yes, I did boot the instance but its getting 10.48.146.4 > address rather 192.168.*** that you gave me ? I can > logon to the instance console 10.48.146.4 and can ping > gateway 10.48.146.1 but I cannot ssh or ping from host? > > Is it possible I share my screen, so that you can guide > me what wrong thing that stops and bother me ? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning the > race. Success is a matter of handling the worst & > finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:18 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO > redhead openstack. > > Did you boot the instance with the demo-net attached ? > > On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi > > wrote: > > I can?t assign a port to the floating ip . I don?t? > see any ports available ? > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & winning > the race. Success is a matter of handling the worst > & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 4:06 PM > > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on JUNO > redhead openstack. > > You've already defined router1 which is already > connected to the external network. You can use that. > ext-net is the 'public' network in your case. > > On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi > > wrote: > > I can?t run this command > > > $ neutron router-gateway-set demo-router ext-net > > Its getting error (ext-net not found) ? What is > the ext-net in this case ? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & > winning the race. Success is a matter of > handling the worst & finishing the race > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 3:58 PM > > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on > JUNO redhead openstack. > > Ok I did the folowing steps for tenant. > > 1) neutron net-create demo-net > 2) neutron subnet-create demo-net --name > demo-subnet --gateway 10.48.146.1 10.48.146.0/24 > > 3) neutron router-create demo-router > 4) neutron router-interface-add demo-router > demo-subnet > > Anything left .? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & > winning the race. Success is a matter of > handling the worst & finishing the race > > > > From: , SAP SAP > > Date: Friday, January 9, 2015 at 3:55 PM > To: Marius Cornea > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on > JUNO redhead openstack. > > Hi Marius, > > Yes, I can ping 10.48.146.113 (gateway) from the > host , can you provide the comamnds or link to > create tenant network, subjet and attach to > router ? > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & > winning the race. Success is a matter of > handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 3:48 PM > To: SAP SAP > > Cc: rdo-list > > Subject: Re: [Rdo-list] networking issues on > JUNO redhead openstack. > > Can you ping 10.48.146.113 from your network? > You also need to create a tenant network, subnet > and attach it to the router. Boot the instance > with the tenant network attached and then assign > it the floating IP. > > > On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi > > wrote: > > Hi Marius, > > I did this first and now can see the BR-ex > is the same IP as my eno1 interface , you > are right I lost first while doing the first > command(ip addr del 10.48.146.77/24 > dev eno1) and then > conneting to console I did the second comand > (ovs-vsctl add-port br-ex eno1 and also > changed the IP address of br-ex to > 10.48.146.77) > > ip addr del 10.48.146.77/24 > dev eno1; > ovs-vsctl add-port br-ex eno1 > > Then after I removed all the routers, > networks and interfaces from openstack and > ran the following 4 commands. > > 1) source /root/keystonerc_admin > 2) neutron net-create public > --router:external=True > 3) neutron subnet-create public > 10.48.146.0/24 > --name vlan --enable_dhcp=False > --allocation_pool > start=10.48.146.113,end=10.48.146.130 > --gateway 10.48.146.1 > 4) neutron router-create router1 > 5) neutron router-gateway-set > 7e07fef0-e92b-4956-9b23-82157d81ebf3 > 1605ac0b-4f59-473d-b20f-911c3401dc2c > 6) neutron floatingip-create public > > The above command generated a floating IP > 10.48.146.115 > > Then I spin up a new instance and it got IP > assigned automatically 10.48.146.115, howevr > I cannot ping or ssh to that ip : > 10.48.146.115 ? > > Here are the screenshots > > > > > [root at lspal117 ~(keystone_admin)]# neutron > net-list > +--------------------------------------+--------+-----------------------------------------------------+ > | id | > name | subnets > | > +--------------------------------------+--------+-----------------------------------------------------+ > | 1605ac0b-4f59-473d-b20f-911c3401dc2c | > public | > 24f385ad-bfeb-4c62-91ff-ab8756d3983b > 10.48.146.0/24 | > +--------------------------------------+--------+??????????????????????????+ > > [root at lspal117 ~(keystone_admin)]# neutron > subnet-list > +--------------------------------------+------+----------------+----------------------------------------------------+ > | id | > name | cidr | allocation_pools > | > +--------------------------------------+------+----------------+----------------------------------------------------+ > | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | > vlan | 10.48.146.0/24 > | {"start": > "10.48.146.113", "end": "10.48.146.130"} | > +--------------------------------------+------+----------------+----------------------------------------------------+ > > [root at lspal117 ~(keystone_admin)]#neutron > router-list > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | id | > name | external_gateway_info > > > > | distributed | ha | > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | > router1 | {"network_id": > "1605ac0b-4f59-473d-b20f-911c3401dc2c", > "enable_snat": true, "external_fixed_ips": > [{"subnet_id": > "24f385ad-bfeb-4c62-91ff-ab8756d3983b", > "ip_address": "10.48.146.113"}]} | False > | False | > +--------------------------------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > > Any ideas what is going wrong, I still can?t > ping or ssh to that IP address and its not > listening anywhere ? > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the best & > winning the race. Success is a matter of > handling the worst & finishing the race > > > > From: Marius Cornea > > Date: Friday, January 9, 2015 at 2:30 PM > To: SAP SAP >, rdo-list > > > > Subject: Re: [Rdo-list] networking issues on > JUNO redhead openstack. > > As Kashyap kindly suggested we're not a > support line and information here should be > available for all the community members. > First, I don't see how you can ping the > br-ex IP address from an external network > since it doesn't contain any physical > interface. Make sure that 10.48.146.112 > isn't used by other host on you network > segment. You can do the following to remove > the ip address from the physical interface > and add it to the br-ex bridge. Please make > sure that you've got console access to the > server before doing this as you may lose > connectivity. > > # ip addr del 10.48.146.77/24 > dev eno1; > ovs-vsctl add-port br-ex eno1 > > You should then follow the documentation[1] > to recreate the public/tenant networks and > router. In your > case FLOATING_IP_START, FLOATING_IP_END > should be part of the 10.48.146.0/24 > network. Let's say > you wish to allocate IP addresses of the > 10.48.146.200 - 10.48.146.210 range to your > Openstack routers/instances, then > FLOATING_IP_START=10.48.146.200 and > FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY > should be set to what 'ip r | grep default | > awk {'print $3'}' outputs > and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24 > . > > Note that the instance will get an IP > address of the tenant network. By assigning > a floating IP you will be able to access it > through an IP address from your physical > network segment. > > [1] http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html > > > > On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi > > > wrote: > > Hi Marius, > > Here are the outputs. Is it possible to > reach you on phone so that I can explain > more than email. You can call me at 650 > 849 3915 or let > me know your number. > > #ip a > > [root at lspal117 > network-scripts(keystone_admin)]# ip a > 1: lo: mtu 65536 > qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd > 00:00:00:00:00:00 > inet 127.0.0.1/8 > scope host lo > valid_lft forever preferred_lft > forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft > forever > 2: eno1: > mtu > 1500 qdisc mq state UP qlen 1000 > link/ether d8:9d:67:29:c6:94 brd > ff:ff:ff:ff:ff:ff > inet 10.48.146.77/24 > brd > 10.48.146.255 scope global eno1 > valid_lft forever preferred_lft > forever > inet6 fe80::da9d:67ff:fe29:c694/64 > scope link > valid_lft forever preferred_lft > forever > 3: eno2: > mtu > 1500 qdisc mq state DOWN qlen 1000 > link/ether d8:9d:67:29:c6:95 brd > ff:ff:ff:ff:ff:ff > 4: eno3: > mtu > 1500 qdisc mq state DOWN qlen 1000 > link/ether d8:9d:67:29:c6:96 brd > ff:ff:ff:ff:ff:ff > 5: eno4: > mtu > 1500 qdisc mq state DOWN qlen 1000 > link/ether d8:9d:67:29:c6:97 brd > ff:ff:ff:ff:ff:ff > 6: ens1f0: > mtu > 1500 qdisc mq state DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:b4 brd > ff:ff:ff:ff:ff:ff > 7: ens1f1: > mtu > 1500 qdisc mq state DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:b5 brd > ff:ff:ff:ff:ff:ff > 8: ens2f0: > mtu > 1500 qdisc mq state DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:40 brd > ff:ff:ff:ff:ff:ff > 9: ens2f1: > mtu > 1500 qdisc mq state DOWN qlen 1000 > link/ether 38:ea:a7:8f:bf:41 brd > ff:ff:ff:ff:ff:ff > 10: ovs-system: > mtu 1500 qdisc noop state DOWN > link/ether 16:02:ac:3f:05:f4 brd > ff:ff:ff:ff:ff:ff > 11: br-ex: > mtu > 1500 qdisc noqueue state UNKNOWN > link/ether be:8b:24:03:a9:47 brd > ff:ff:ff:ff:ff:ff > inet 10.48.146.112/24 > brd > 10.48.146.255 scope global br-ex > valid_lft forever preferred_lft > forever > inet6 fe80::bc8b:24ff:fe03:a947/64 > scope link > valid_lft forever preferred_lft > forever > 12: br-int: mtu > 1500 qdisc noop state DOWN > link/ether 02:35:a4:7c:e5:4c brd > ff:ff:ff:ff:ff:ff > 16: br-tun: mtu > 1500 qdisc noop state DOWN > link/ether fe:61:30:fb:a3:47 brd > ff:ff:ff:ff:ff:ff > 17: qbr63bd6704-47: > mtu > 1500 qdisc noqueue state UP > link/ether 8e:fe:6e:19:61:5c brd > ff:ff:ff:ff:ff:ff > inet6 fe80::3822:bcff:fe6a:b74f/64 > scope link > valid_lft forever preferred_lft > forever > 18: qvo63bd6704-47: > mtu > 1500 qdisc pfifo_fast master ovs-system > state UP qlen 1000 > link/ether a2:fe:04:5f:04:b4 brd > ff:ff:ff:ff:ff:ff > 19: qvb63bd6704-47: > mtu > 1500 qdisc pfifo_fast master > qbr63bd6704-47 state UP qlen 1000 > link/ether 8e:fe:6e:19:61:5c brd > ff:ff:ff:ff:ff:ff > 22: tap63bd6704-47: > mtu > 1500 qdisc pfifo_fast master > qbr63bd6704-47 state UNKNOWN qlen 500 > link/ether fe:16:3e:d9:5e:ba brd > ff:ff:ff:ff:ff:ff > inet6 fe80::fc16:3eff:fed9:5eba/64 > scope link > valid_lft forever preferred_lft > forever > > # ovs-vsctl show > > [root at lspal117 > network-scripts(keystone_admin)]# > ovs-vsctl show > c5bcc161-86cd-4004-9729-c1ba05d28569 > Bridge br-ex > Port br-ex > Interface br-ex > type: internal > Port "qg-c3a1b534-36" > Interface "qg-c3a1b534-36" > type: internal > Bridge br-int > fail_mode: secure > Port patch-tun > Interface patch-tun > type: patch > options: {peer=patch-int} > Port "tape386c0cb-d8" > tag: 1 > Interface "tape386c0cb-d8" > type: internal > Port br-int > Interface br-int > type: internal > Port "qvo63bd6704-47" > tag: 1 > Interface "qvo63bd6704-47" > Port "tap44dd465f-d4" > tag: 4095 > Interface "tap44dd465f-d4" > type: internal > Port "qr-e0ac3c25-2b" > tag: 2 > Interface "qr-e0ac3c25-2b" > type: internal > Bridge br-tun > Port br-tun > Interface br-tun > type: internal > Port patch-int > Interface patch-int > type: patch > options: {peer=patch-tun} > ovs_version: ?2.1.3" > > # neutron net-list > [root at lspal117 > network-scripts(keystone_admin)]# > neutron net-list > +--------------------------------------+---------+------------------------------------------------------+ > | id | > name | subnets > | > +--------------------------------------+---------+------------------------------------------------------+ > | 5abe660b-52da-4d36-8275-4c1488df88b4 | > public | > 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a > 172.24.4.224/28 | > | d825e820-66e5-44b1-a91d-0c660aa822a5 | > private | > f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 > 10.0.0.0/24 | > | 6eb6d123-8fec-4984-986a-5eeabf895883 | > sap | > ea2b21e0-bf9f-4195-b210-b75b6f9f7943 > 10.48.146.0/24 | > +--------------------------------------+---------+------------------------------------------------------+ > > # neutron subnet-list > [root at lspal117 > network-scripts(keystone_admin)]# > neutron subnet-list > +--------------------------------------+----------------+-----------------+----------------------------------------------------+ > | id | > name | cidr | > allocation_pools > | > +--------------------------------------+----------------+-----------------+----------------------------------------------------+ > | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | > public_subnet | 172.24.4.224/28 > | {"start": > "172.24.4.226", "end": "172.24.4.238"} | > | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | > private_subnet | 10.0.0.0/24 > | {"start": > "10.0.0.2", "end": "10.0.0.254"} | > | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | > sap_local | 10.48.146.0/24 > | {"start": > "10.48.146.112", "end": "10.48.146.120"} | > +--------------------------------------+----------------+-----------------+??????????????????????????+ > > #neutron router-list > [root at lspal117 > network-scripts(keystone_admin)]# > neutron router-list > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | id | > name | external_gateway_info > > > > | > distributed | ha | > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+ > | d6325c88-e5b0-448e-8ab1-af5908a189d4 | > router1 | {"network_id": > "5abe660b-52da-4d36-8275-4c1488df88b4", > "enable_snat": true, > "external_fixed_ips": [{"subnet_id": > "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", > "ip_address": "172.24.4.226"}]} | False > | False | > +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+???+ > > In my system I have IP address for BR-ex > and ENO1 (interface connecting ), should > I disable eno1 as I can ping both (br-ex > and eno1) from my network to reach to > this host ? Probably its a dump question. > > Here are the outputs. > > br-ex: > flags=4163 > mtu 1500 > inet 10.48.146.112 netmask > 255.255.255.0 broadcast 10.48.146.255 > inet6 fe80::bc8b:24ff:fe03:a947 > prefixlen 64 scopeid 0x20 > ether be:8b:24:03:a9:47 > txqueuelen 0 (Ethernet) > RX packets 10 bytes 864 (864.0 B) > RX errors 0 dropped 0 overruns > 0 frame 0 > TX packets 25 bytes 3767 (3.6 KiB) > TX errors 0 dropped 0 overruns > 0 carrier 0 collisions 0 > > br-int: flags=4098 > mtu 1500 > ether 02:35:a4:7c:e5:4c > txqueuelen 0 (Ethernet) > RX packets 135 bytes 7574 (7.3 KiB) > RX errors 0 dropped 0 overruns > 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns > 0 carrier 0 collisions 0 > > br-tun: flags=4098 > mtu 1500 > ether fe:61:30:fb:a3:47 > txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns > 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns > 0 carrier 0 collisions 0 > > eno1: > flags=4163 > mtu 1500 > inet 10.48.146.77 netmask > 255.255.255.0 broadcast 10.48.146.255 > inet6 fe80::da9d:67ff:fe29:c694 > prefixlen 64 scopeid 0x20 > ether d8:9d:67:29:c6:94 > txqueuelen 1000 (Ethernet) > RX packets 467319 bytes > 48391354 (46.1 MiB) > RX errors 0 dropped 0 overruns > 0 frame 0 > TX packets 14794 bytes 5238733 > (4.9 MiB) > TX errors 0 dropped 0 overruns > 0 carrier 0 collisions 0 > device interrupt 32 > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the > best & winning the race. Success is a > matter of handling the worst & finishing > the race > > > > From: Marius Cornea > > > Date: Friday, January 9, 2015 at 1:46 PM > To: SAP SAP > > Subject: Re: [Rdo-list] networking > issues on JUNO redhead openstack. > > Hi Rushi, > > Can you provide the output of the > following commands on your node ? > > # ip a > # ovs-vsctl show > # neutron net-list > # neutron subnet-list > # neutron router-list > > Please note that only the br-ex bridge > requires an IP address, the interface > that's part of it shouldn't have one > assigned. Also the floating IP addresses > will be used for DNAT on the tenant > router. You can check the documentation > here[1] that describes the use of > floating IPs. > > You can also check the upstream > documentation[2] on how to create the > networks. > > [1] https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP > [2] > http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_initial-external-network.html > > Tnx, > Marius > > On Fri, Jan 9, 2015 at 10:22 PM, Ns, > Rushi > wrote: > > Hi Support, > > I have a problem that a launched > instance from openstack cannot > connect to SSH or PING > > First of all I have dump question > whether my system should be NOVA > network or Neutron network. Well to > keep everyone on the same page. Here > is my history. > > 1. I did install RDO (allinone > host) using the bellow steps > https://openstack.redhat.com/Quickstart > 2. Then I have used the following > steps for floating > IP https://openstack.redhat.com/Floating_IP_range. > > My situtation is as follows. > * Floating IP address assignment: > I have assigned a floating IP , I > did follow this steps. > https://openstack.redhat.com/Floating_IP_range > > * Bridge configuration:My Ethernet > device eth0(actually in Redhat 7 it > is eno1 name)is on the same bridge > as the compute host > Yes, ethernet device on 10.48.146.78 > address and br-ex interface on > 10.48.146.112 > > * DHCP configuration: Yes, DHCP > configuration is set and Neutron > hearing and responding to DHCP > requests and the instance is getting > IP from 10.48.146.113 (next hop) > however I cannot ping/ssh to that IP > address (ICMP/SSH is added allowed > rule on default security group) > > Here is the little diagram of my system. > > Can someone help to find what is > missing. > > > > Best Regards,____ > > > > Rushi.____ > > Success is not a matter of being the > best & winning the race. Success is > a matter of handling the worst & > finishing the race > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > > > > > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338 From rushi.ns at sap.com Wed Jan 14 20:15:54 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Wed, 14 Jan 2015 20:15:54 +0000 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: <54B6CC05.8080105@redhat.com> References: <54B6CC05.8080105@redhat.com> Message-ID: Hi Dave, I tried the steps you provided and at the end I see that its the port 22 not listening [root at lspal117 ~(keystone_demo)]# ip netns list qrouter-9babbc60-1be0-42bc-8891-93e82b266f04 qdhcp-5af3918a-8848-4678-9bf0-dcfcba5b280e qrouter-5fc00c74-9277-4ddb-998e-2872ed2b3c90 qdhcp-3af0fbce-b839-4323-b28a-525d7a3e4fbb qrouter-51233ace-a447-4427-951d-848297092710 qrouter-8728570d-1763-40c3-b162-f4932ef5aa9a qdhcp-06541261-b30d-4656-9b4b-fe30566656ab qrouter-6eea5082-e3f0-4a5f-a3b0-fb6110b97b9f qrouter-7e07fef0-e92b-4956-9b23-82157d81ebf3 qrouter-e05b9c4e-ee5e-4c02-b16a-099063f2ba66 qrouter-d6325c88-e5b0-448e-8ab1-af5908a189d4 qdhcp-6eb6d123-8fec-4984-986a-5eeabf895883 qdhcp-d825e820-66e5-44b1-a91d-0c660aa822a5 root at lspal117 ~(keystone_demo)]# ip netns list |grep qrouter qrouter-9babbc60-1be0-42bc-8891-93e82b266f04 qrouter-5fc00c74-9277-4ddb-998e-2872ed2b3c90 [root at lspal117 ~(keystone_demo)]# ip netns exec qdhcp-5af3918a-8848-4678-9bf0-dcfcba5b280e ssh root at 192.168.2.0 ssh: connect to host 192.168.2.0 port 22: Network is unreachable Any ideas how to resolve to ssh to tenant IP: 192.168.2.0 from openstack SSH. FYI< last 2 days I did fix some issues and I was able to logon to SSH of the tenant instance via floating IP: 10.48.146.119 but I cannot ssh to tenant private IP: 192.168.2.0 from openstack node ? Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race On 1/14/15, 12:05 PM, "Dave Neary" wrote: >Hi, > >Have you checked the security rules to ensure that port 22 (ssh), port >80 (http) and ICMP are all allowed through to the instance? Tose rules >are not enforces in the instance, they're enforced with iptables in the >host. > >You might also try to connect to the instance from inside the same >network namespace - just to check that you can. > >On the host, as root: >ip netns list ># Identify the network namespace corresponding to your instance ># - look for a qrouter namespace ># - List all of the routes in the namespace >ip netns exec qrouter-1fabd5f0-f80b-468d-b733-1b80d0c3e80f \ > ip r > ># ssh into guest >$ ip netns exec qdhcp-4a04382f-03bf-49a9-9d4a-35ab9ffc22ad ssh >cirros@${instance_ip_addr} > >This will at least eliminate the possibility that your instance is >somehow broken. > >Thanks, >Dave. >On 01/09/2015 08:12 PM, Ns, Rushi wrote: >> Hi Marius, >> >> Sorry I can assign the floating ip to the instnace (demo user launched >> insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ >> 10.48.146.115) from the host but from the instance (192.168.1.2) I can >> ping other instance 192.168.1.4 ? >> >> Can you help in this final step what is missing > >> >> >> >> >> root at lspal117 tmp(keystone_admin)]# neutron port-list >> >>+--------------------------------------+------+-------------------+------ >>------------------------------------------------------------------------- >>-------+ >> | id | name | mac_address | >> fixed_ips >> | >> >>+--------------------------------------+------+-------------------+------ >>------------------------------------------------------------------------- >>-------+ >> | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.2"} | >> | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.1"} | >> | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.114"} | >> | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.115"} | >> | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.113"} | >> | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.4"} | >> | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.3"} | >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> >> From: , SAP SAP > >> Date: Friday, January 9, 2015 at 5:03 PM >> To: Marius Cornea > >> Cc: rdo-list > >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Here is it >> >> [root at lspal117 tmp(keystone_admin)]# neutron port-list >> >>+--------------------------------------+------+-------------------+------ >>------------------------------------------------------------------------- >>-------+ >> | id | name | mac_address | >> fixed_ips >> | >> >>+--------------------------------------+------+-------------------+------ >>------------------------------------------------------------------------- >>-------+ >> | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.2"} | >> | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.1"} | >> | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.114"} | >> | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | >> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >> "10.48.146.113"} | >> | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | >> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >> "192.168.1.3"} | >> >>+--------------------------------------+------+-------------------+?????? >>?????????????????????????????????????+ >> >> >> Best Regards, >> >> >> >> Rushi. >> >> Success is not a matter of being the best & winning the race. Success is >> a matter of handling the worst & finishing the race >> >> >> >> From: Marius Cornea >> >> Date: Friday, January 9, 2015 at 5:02 PM >> To: SAP SAP > >> Cc: rdo-list > >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> What does 'neutron port-list' show ? >> >> On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi > > wrote: >> >> I did that, launch instance got IP: 192.168.1.2 then I did >> floating_IP which I got 10.48.146.114 , however I cannot assign to >> the instance as there are no ports avilable.? >> >> >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & winning the race. >> Success is a matter of handling the worst & finishing the race >> >> >> >> From: Marius Cornea > > >> Date: Friday, January 9, 2015 at 4:52 PM >> >> To: SAP SAP > >> Cc: rdo-list > >> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >> >> Next launch an instance with demo-net attached. Then assign it a >> floating IP. You should get 10.48.146.114 as the floating IP. >> >> On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi > > wrote: >> >> Thanks, I did this step . So what is next ? Sorry to bother but >> you are really a life saver to me (thanks to you a ton) as well >> kashyap . >> >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & winning the race. >> Success is a matter of handling the worst & finishing the race >> >> >> >> From: Marius Cornea > > >> Date: Friday, January 9, 2015 at 4:46 PM >> To: SAP SAP > >> Cc: rdo-list > >> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>openstack. >> >> neutron net-create public --router:external=True >> neutron subnet-create public 10.48.146.0/24 >> --name vlan --enable_dhcp=False >> --allocation_pool start=10.48.146.113,end=10.48.146.130 >> --gateway 10.48.146.1 >> >> neutron net-create demo-net >> neutron subnet-create demo-net --name demo-subnet --gateway >> 192.168.1.1 192.168.1.0/24 >> >> neutron router-create demo-router >> neutron router-interface-add demo-router demo-subnet >> neutron router-gateway-set demo-router public >> >> >> On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi > > wrote: >> >> I have deleted all network (admin) and tenant as I wanted >> your guidance to do further >> >> Can you help to give steps to add the network again >> (10.48.146.0/24 ) and tenant >> 192.168.10.0/24 after floating ip >> to 10.48.146.113) >> >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & winning the >> race. Success is a matter of handling the worst & finishing >> the race >> >> >> >> From: Marius Cornea > > >> Date: Friday, January 9, 2015 at 4:27 PM >> >> To: SAP SAP > >> Cc: rdo-list >> >> Subject: Re: [Rdo-list] networking issues on JUNO redhead >> openstack. >> >> Let's keep the troubleshooting steps on the list. What's the >> output of 'nova list' ? >> >> On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi > > wrote: >> >> Yes, I did boot the instance but its getting 10.48.146.4 >> address rather 192.168.*** that you gave me ? I can >> logon to the instance console 10.48.146.4 and can ping >> gateway 10.48.146.1 but I cannot ssh or ping from host? >> >> Is it possible I share my screen, so that you can guide >> me what wrong thing that stops and bother me ? >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & winning the >> race. Success is a matter of handling the worst & >> finishing the race >> >> >> >> From: Marius Cornea > > >> Date: Friday, January 9, 2015 at 4:18 PM >> >> To: SAP SAP > >> Cc: rdo-list > > >> Subject: Re: [Rdo-list] networking issues on JUNO >> redhead openstack. >> >> Did you boot the instance with the demo-net attached ? >> >> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi >> > wrote: >> >> I can?t assign a port to the floating ip . I don?t? >> see any ports available ? >> >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & winning >> the race. Success is a matter of handling the worst >> & finishing the race >> >> >> >> From: Marius Cornea > > >> Date: Friday, January 9, 2015 at 4:06 PM >> >> To: SAP SAP >> >> Cc: rdo-list > > >> Subject: Re: [Rdo-list] networking issues on JUNO >> redhead openstack. >> >> You've already defined router1 which is already >> connected to the external network. You can use that. >> ext-net is the 'public' network in your case. >> >> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi >> > wrote: >> >> I can?t run this command >> >> >> $ neutron router-gateway-set demo-router ext-net >> >> Its getting error (ext-net not found) ? What is >> the ext-net in this case ? >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & >> winning the race. Success is a matter of >> handling the worst & finishing the race >> >> >> From: , SAP SAP > > >> Date: Friday, January 9, 2015 at 3:58 PM >> >> To: Marius Cornea > > >> Cc: rdo-list > > >> Subject: Re: [Rdo-list] networking issues on >> JUNO redhead openstack. >> >> Ok I did the folowing steps for tenant. >> >> 1) neutron net-create demo-net >> 2) neutron subnet-create demo-net --name >> demo-subnet --gateway 10.48.146.1 10.48.146.0/24 >> >> 3) neutron router-create demo-router >> 4) neutron router-interface-add demo-router >> demo-subnet >> >> Anything left .? >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & >> winning the race. Success is a matter of >> handling the worst & finishing the race >> >> >> >> From: , SAP SAP > > >> Date: Friday, January 9, 2015 at 3:55 PM >> To: Marius Cornea > > >> Cc: rdo-list > > >> Subject: Re: [Rdo-list] networking issues on >> JUNO redhead openstack. >> >> Hi Marius, >> >> Yes, I can ping 10.48.146.113 (gateway) from the >> host , can you provide the comamnds or link to >> create tenant network, subjet and attach to >> router ? >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & >> winning the race. Success is a matter of >> handling the worst & finishing the race >> >> >> >> From: Marius Cornea > > >> Date: Friday, January 9, 2015 at 3:48 PM >> To: SAP SAP > > >> Cc: rdo-list > > >> Subject: Re: [Rdo-list] networking issues on >> JUNO redhead openstack. >> >> Can you ping 10.48.146.113 from your network? >> You also need to create a tenant network, subnet >> and attach it to the router. Boot the instance >> with the tenant network attached and then assign >> it the floating IP. >> >> >> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi >> > >>wrote: >> >> Hi Marius, >> >> I did this first and now can see the BR-ex >> is the same IP as my eno1 interface , you >> are right I lost first while doing the first >> command(ip addr del 10.48.146.77/24 >> dev eno1) and then >> conneting to console I did the second comand >> (ovs-vsctl add-port br-ex eno1 and also >> changed the IP address of br-ex to >> 10.48.146.77) >> >> ip addr del 10.48.146.77/24 >> dev eno1; >> ovs-vsctl add-port br-ex eno1 >> >> Then after I removed all the routers, >> networks and interfaces from openstack and >> ran the following 4 commands. >> >> 1) source /root/keystonerc_admin >> 2) neutron net-create public >> --router:external=True >> 3) neutron subnet-create public >> 10.48.146.0/24 >> --name vlan --enable_dhcp=False >> --allocation_pool >> start=10.48.146.113,end=10.48.146.130 >> --gateway 10.48.146.1 >> 4) neutron router-create router1 >> 5) neutron router-gateway-set >> 7e07fef0-e92b-4956-9b23-82157d81ebf3 >> 1605ac0b-4f59-473d-b20f-911c3401dc2c >> 6) neutron floatingip-create public >> >> The above command generated a floating IP >> 10.48.146.115 >> >> Then I spin up a new instance and it got IP >> assigned automatically 10.48.146.115, howevr >> I cannot ping or ssh to that ip : >> 10.48.146.115 ? >> >> Here are the screenshots >> >> >> >> >> [root at lspal117 ~(keystone_admin)]# neutron >> net-list >> >>+--------------------------------------+--------+------------------------ >>-----------------------------+ >> | id | >> name | subnets >> | >> >>+--------------------------------------+--------+------------------------ >>-----------------------------+ >> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | >> public | >> 24f385ad-bfeb-4c62-91ff-ab8756d3983b >> 10.48.146.0/24 | >> >>+--------------------------------------+--------+???????????????????????? >>??+ >> >> [root at lspal117 ~(keystone_admin)]# neutron >> subnet-list >> >>+--------------------------------------+------+----------------+--------- >>-------------------------------------------+ >> | id | >> name | cidr | allocation_pools >> | >> >>+--------------------------------------+------+----------------+--------- >>-------------------------------------------+ >> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | >> vlan | 10.48.146.0/24 >> | {"start": >> "10.48.146.113", "end": "10.48.146.130"} | >> >>+--------------------------------------+------+----------------+--------- >>-------------------------------------------+ >> >> [root at lspal117 ~(keystone_admin)]#neutron >> router-list >> >>+--------------------------------------+---------+----------------------- >>------------------------------------------------------------------------- >>------------------------------------------------------------------------- >>------------------+-------------+-------+ >> | id | >> name | external_gateway_info >> >> >> >> | distributed | ha | >> >>+--------------------------------------+---------+----------------------- >>------------------------------------------------------------------------- >>------------------------------------------------------------------------- >>------------------+-------------+-------+ >> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | >> router1 | {"network_id": >> "1605ac0b-4f59-473d-b20f-911c3401dc2c", >> "enable_snat": true, "external_fixed_ips": >> [{"subnet_id": >> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", >> "ip_address": "10.48.146.113"}]} | False >> | False | >> >>+--------------------------------------+---------+----------------------- >>------------------------------------------------------------------------- >>------------------------------------------------------------------------- >>------------------+-------------+-------+ >> >> Any ideas what is going wrong, I still can?t >> ping or ssh to that IP address and its not >> listening anywhere ? >> >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the best & >> winning the race. Success is a matter of >> handling the worst & finishing the race >> >> >> >> From: Marius Cornea > > >> Date: Friday, January 9, 2015 at 2:30 PM >> To: SAP SAP > >, rdo-list >> > > >> >> Subject: Re: [Rdo-list] networking issues on >> JUNO redhead openstack. >> >> As Kashyap kindly suggested we're not a >> support line and information here should be >> available for all the community members. >> First, I don't see how you can ping the >> br-ex IP address from an external network >> since it doesn't contain any physical >> interface. Make sure that 10.48.146.112 >> isn't used by other host on you network >> segment. You can do the following to remove >> the ip address from the physical interface >> and add it to the br-ex bridge. Please make >> sure that you've got console access to the >> server before doing this as you may lose >> connectivity. >> >> # ip addr del 10.48.146.77/24 >> dev eno1; >> ovs-vsctl add-port br-ex eno1 >> >> You should then follow the documentation[1] >> to recreate the public/tenant networks and >> router. In your >> case FLOATING_IP_START, FLOATING_IP_END >> should be part of the 10.48.146.0/24 >> network. Let's say >> you wish to allocate IP addresses of the >> 10.48.146.200 - 10.48.146.210 range to your >> Openstack routers/instances, then >> FLOATING_IP_START=10.48.146.200 and >> FLOATING_IP_END=10.48.146.210. >>EXTERNAL_NETWORK_GATEWAY >> should be set to what 'ip r | grep default | >> awk {'print $3'}' outputs >> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24 >> . >> >> Note that the instance will get an IP >> address of the tenant network. By assigning >> a floating IP you will be able to access it >> through an IP address from your physical >> network segment. >> >> [1] >>http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_ >>initial-external-network.html >> >> >> >> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi >> > >> wrote: >> >> Hi Marius, >> >> Here are the outputs. Is it possible to >> reach you on phone so that I can explain >> more than email. You can call me at 650 >> 849 3915 or let >> me know your number. >> >> #ip a >> >> [root at lspal117 >> network-scripts(keystone_admin)]# ip a >> 1: lo: mtu 65536 >> qdisc noqueue state UNKNOWN >> link/loopback 00:00:00:00:00:00 brd >> 00:00:00:00:00:00 >> inet 127.0.0.1/8 >> scope host lo >> valid_lft forever preferred_lft >> forever >> inet6 ::1/128 scope host >> valid_lft forever preferred_lft >> forever >> 2: eno1: >> mtu >> 1500 qdisc mq state UP qlen 1000 >> link/ether d8:9d:67:29:c6:94 brd >> ff:ff:ff:ff:ff:ff >> inet 10.48.146.77/24 >> brd >> 10.48.146.255 scope global eno1 >> valid_lft forever preferred_lft >> forever >> inet6 fe80::da9d:67ff:fe29:c694/64 >> scope link >> valid_lft forever preferred_lft >> forever >> 3: eno2: >> mtu >> 1500 qdisc mq state DOWN qlen 1000 >> link/ether d8:9d:67:29:c6:95 brd >> ff:ff:ff:ff:ff:ff >> 4: eno3: >> mtu >> 1500 qdisc mq state DOWN qlen 1000 >> link/ether d8:9d:67:29:c6:96 brd >> ff:ff:ff:ff:ff:ff >> 5: eno4: >> mtu >> 1500 qdisc mq state DOWN qlen 1000 >> link/ether d8:9d:67:29:c6:97 brd >> ff:ff:ff:ff:ff:ff >> 6: ens1f0: >> mtu >> 1500 qdisc mq state DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:b4 brd >> ff:ff:ff:ff:ff:ff >> 7: ens1f1: >> mtu >> 1500 qdisc mq state DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:b5 brd >> ff:ff:ff:ff:ff:ff >> 8: ens2f0: >> mtu >> 1500 qdisc mq state DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:40 brd >> ff:ff:ff:ff:ff:ff >> 9: ens2f1: >> mtu >> 1500 qdisc mq state DOWN qlen 1000 >> link/ether 38:ea:a7:8f:bf:41 brd >> ff:ff:ff:ff:ff:ff >> 10: ovs-system: >> mtu 1500 qdisc noop state DOWN >> link/ether 16:02:ac:3f:05:f4 brd >> ff:ff:ff:ff:ff:ff >> 11: br-ex: >> mtu >> 1500 qdisc noqueue state UNKNOWN >> link/ether be:8b:24:03:a9:47 brd >> ff:ff:ff:ff:ff:ff >> inet 10.48.146.112/24 >> brd >> 10.48.146.255 scope global br-ex >> valid_lft forever preferred_lft >> forever >> inet6 fe80::bc8b:24ff:fe03:a947/64 >> scope link >> valid_lft forever preferred_lft >> forever >> 12: br-int: mtu >> 1500 qdisc noop state DOWN >> link/ether 02:35:a4:7c:e5:4c brd >> ff:ff:ff:ff:ff:ff >> 16: br-tun: mtu >> 1500 qdisc noop state DOWN >> link/ether fe:61:30:fb:a3:47 brd >> ff:ff:ff:ff:ff:ff >> 17: qbr63bd6704-47: >> mtu >> 1500 qdisc noqueue state UP >> link/ether 8e:fe:6e:19:61:5c brd >> ff:ff:ff:ff:ff:ff >> inet6 fe80::3822:bcff:fe6a:b74f/64 >> scope link >> valid_lft forever preferred_lft >> forever >> 18: qvo63bd6704-47: >> >> mtu >> 1500 qdisc pfifo_fast master ovs-system >> state UP qlen 1000 >> link/ether a2:fe:04:5f:04:b4 brd >> ff:ff:ff:ff:ff:ff >> 19: qvb63bd6704-47: >> >> mtu >> 1500 qdisc pfifo_fast master >> qbr63bd6704-47 state UP qlen 1000 >> link/ether 8e:fe:6e:19:61:5c brd >> ff:ff:ff:ff:ff:ff >> 22: tap63bd6704-47: >> mtu >> 1500 qdisc pfifo_fast master >> qbr63bd6704-47 state UNKNOWN qlen 500 >> link/ether fe:16:3e:d9:5e:ba brd >> ff:ff:ff:ff:ff:ff >> inet6 fe80::fc16:3eff:fed9:5eba/64 >> scope link >> valid_lft forever preferred_lft >> forever >> >> # ovs-vsctl show >> >> [root at lspal117 >> network-scripts(keystone_admin)]# >> ovs-vsctl show >> c5bcc161-86cd-4004-9729-c1ba05d28569 >> Bridge br-ex >> Port br-ex >> Interface br-ex >> type: internal >> Port "qg-c3a1b534-36" >> Interface "qg-c3a1b534-36" >> type: internal >> Bridge br-int >> fail_mode: secure >> Port patch-tun >> Interface patch-tun >> type: patch >> options: >>{peer=patch-int} >> Port "tape386c0cb-d8" >> tag: 1 >> Interface "tape386c0cb-d8" >> type: internal >> Port br-int >> Interface br-int >> type: internal >> Port "qvo63bd6704-47" >> tag: 1 >> Interface "qvo63bd6704-47" >> Port "tap44dd465f-d4" >> tag: 4095 >> Interface "tap44dd465f-d4" >> type: internal >> Port "qr-e0ac3c25-2b" >> tag: 2 >> Interface "qr-e0ac3c25-2b" >> type: internal >> Bridge br-tun >> Port br-tun >> Interface br-tun >> type: internal >> Port patch-int >> Interface patch-int >> type: patch >> options: >>{peer=patch-tun} >> ovs_version: ?2.1.3" >> >> # neutron net-list >> [root at lspal117 >> network-scripts(keystone_admin)]# >> neutron net-list >> >>+--------------------------------------+---------+----------------------- >>-------------------------------+ >> | id | >> name | subnets >> | >> >>+--------------------------------------+---------+----------------------- >>-------------------------------+ >> | 5abe660b-52da-4d36-8275-4c1488df88b4 | >> public | >> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a >> 172.24.4.224/28 >> | >> | d825e820-66e5-44b1-a91d-0c660aa822a5 | >> private | >> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 >> 10.0.0.0/24 | >> | 6eb6d123-8fec-4984-986a-5eeabf895883 | >> sap | >> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 >> 10.48.146.0/24 >>| >> >>+--------------------------------------+---------+----------------------- >>-------------------------------+ >> >> # neutron subnet-list >> [root at lspal117 >> network-scripts(keystone_admin)]# >> neutron subnet-list >> >>+--------------------------------------+----------------+---------------- >>-+----------------------------------------------------+ >> | id | >> name | cidr | >> allocation_pools >> | >> >>+--------------------------------------+----------------+---------------- >>-+----------------------------------------------------+ >> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | >> public_subnet | 172.24.4.224/28 >> | {"start": >> "172.24.4.226", "end": "172.24.4.238"} >> | >> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | >> private_subnet | 10.0.0.0/24 >> | {"start": >> "10.0.0.2", "end": "10.0.0.254"} >> | >> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | >> sap_local | 10.48.146.0/24 >> | {"start": >> "10.48.146.112", "end": >>"10.48.146.120"} | >> >>+--------------------------------------+----------------+---------------- >>-+??????????????????????????+ >> >> #neutron router-list >> [root at lspal117 >> network-scripts(keystone_admin)]# >> neutron router-list >> >>+--------------------------------------+---------+----------------------- >>------------------------------------------------------------------------- >>------------------------------------------------------------------------- >>-----------------+-------------+-------+ >> | id | >> name | external_gateway_info >> >> >> >> | >> distributed | ha | >> >>+--------------------------------------+---------+----------------------- >>------------------------------------------------------------------------- >>------------------------------------------------------------------------- >>-----------------+-------------+-------+ >> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | >> router1 | {"network_id": >> "5abe660b-52da-4d36-8275-4c1488df88b4", >> "enable_snat": true, >> "external_fixed_ips": [{"subnet_id": >> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", >> "ip_address": "172.24.4.226"}]} | False >> | False | >> >>+--------------------------------------+---------+----------------------- >>------------------------------------------------------------------------- >>------------------------------------------------------------------------- >>-----------------+-------------+???+ >> >> In my system I have IP address for BR-ex >> and ENO1 (interface connecting ), should >> I disable eno1 as I can ping both (br-ex >> and eno1) from my network to reach to >> this host ? Probably its a dump >>question. >> >> Here are the outputs. >> >> br-ex: >> >>flags=4163 >> mtu 1500 >> inet 10.48.146.112 netmask >> 255.255.255.0 broadcast 10.48.146.255 >> inet6 fe80::bc8b:24ff:fe03:a947 >> prefixlen 64 scopeid 0x20 >> ether be:8b:24:03:a9:47 >> txqueuelen 0 (Ethernet) >> RX packets 10 bytes 864 (864.0 >>B) >> RX errors 0 dropped 0 overruns >> 0 frame 0 >> TX packets 25 bytes 3767 (3.6 >>KiB) >> TX errors 0 dropped 0 overruns >> 0 carrier 0 collisions 0 >> >> br-int: flags=4098 >> mtu 1500 >> ether 02:35:a4:7c:e5:4c >> txqueuelen 0 (Ethernet) >> RX packets 135 bytes 7574 (7.3 >>KiB) >> RX errors 0 dropped 0 overruns >> 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns >> 0 carrier 0 collisions 0 >> >> br-tun: flags=4098 >> mtu 1500 >> ether fe:61:30:fb:a3:47 >> txqueuelen 0 (Ethernet) >> RX packets 0 bytes 0 (0.0 B) >> RX errors 0 dropped 0 overruns >> 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns >> 0 carrier 0 collisions 0 >> >> eno1: >> >>flags=4163 >> mtu 1500 >> inet 10.48.146.77 netmask >> 255.255.255.0 broadcast 10.48.146.255 >> inet6 fe80::da9d:67ff:fe29:c694 >> prefixlen 64 scopeid 0x20 >> ether d8:9d:67:29:c6:94 >> txqueuelen 1000 (Ethernet) >> RX packets 467319 bytes >> 48391354 (46.1 MiB) >> RX errors 0 dropped 0 overruns >> 0 frame 0 >> TX packets 14794 bytes 5238733 >> (4.9 MiB) >> TX errors 0 dropped 0 overruns >> 0 carrier 0 collisions 0 >> device interrupt 32 >> >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the >> best & winning the race. Success is a >> matter of handling the worst & finishing >> the race >> >> >> >> From: Marius Cornea >> > > >> Date: Friday, January 9, 2015 at 1:46 PM >> To: SAP SAP > > >> Subject: Re: [Rdo-list] networking >> issues on JUNO redhead openstack. >> >> Hi Rushi, >> >> Can you provide the output of the >> following commands on your node ? >> >> # ip a >> # ovs-vsctl show >> # neutron net-list >> # neutron subnet-list >> # neutron router-list >> >> Please note that only the br-ex bridge >> requires an IP address, the interface >> that's part of it shouldn't have one >> assigned. Also the floating IP addresses >> will be used for DNAT on the tenant >> router. You can check the documentation >> here[1] that describes the use of >> floating IPs. >> >> You can also check the upstream >> documentation[2] on how to create the >> networks. >> >> [1] >>https://openstack.redhat.com/Difference_between_Floating_IP_and_private_I >>P >> [2] >> >>http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_ >>initial-external-network.html >> >> Tnx, >> Marius >> >> On Fri, Jan 9, 2015 at 10:22 PM, Ns, >> Rushi > > wrote: >> >> Hi Support, >> >> I have a problem that a launched >> instance from openstack cannot >> connect to SSH or PING >> >> First of all I have dump question >> whether my system should be NOVA >> network or Neutron network. Well to >> keep everyone on the same page. Here >> is my history. >> >> 1. I did install RDO (allinone >> host) using the bellow steps >> >>https://openstack.redhat.com/Quickstart >> 2. Then I have used the following >> steps for floating >> IP >>https://openstack.redhat.com/Floating_IP_range. >> >> My situtation is as follows. >> * Floating IP address assignment: >> I have assigned a floating IP , I >> did follow this steps. >> >>https://openstack.redhat.com/Floating_IP_range >> >> * Bridge configuration:My Ethernet >> device eth0(actually in Redhat 7 it >> is eno1 name)is on the same bridge >> as the compute host >> Yes, ethernet device on 10.48.146.78 >> address and br-ex interface on >> 10.48.146.112 >> >> * DHCP configuration: Yes, DHCP >> configuration is set and Neutron >> hearing and responding to DHCP >> requests and the instance is getting >> IP from 10.48.146.113 (next hop) >> however I cannot ping/ssh to that IP >> address (ICMP/SSH is added allowed >> rule on default security group) >> >> Here is the little diagram of my >>system. >> >> Can someone help to find what is >> missing. >> >> >> >> Best Regards,____ >> >> >> >> Rushi.____ >> >> Success is not a matter of being the >> best & winning the race. Success is >> a matter of handling the worst & >> finishing the race >> >> >> >> >>_______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> >> >>https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > >-- >Dave Neary - NFV/SDN Community Strategy >Open Source and Standards, Red Hat - http://community.redhat.com >Ph: +1-978-399-2182 / Cell: +1-978-799-3338 From dneary at redhat.com Wed Jan 14 20:21:00 2015 From: dneary at redhat.com (Dave Neary) Date: Wed, 14 Jan 2015 15:21:00 -0500 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: <54B6CC05.8080105@redhat.com> Message-ID: <54B6CFAC.3000701@redhat.com> Hi, Check you're in the right namespace first - "Network is unreachable" just means you can't route traffic there. Did you try the other qrouter(s)? Dave. On 01/14/2015 03:15 PM, Ns, Rushi wrote: > Hi Dave, > > I tried the steps you provided and at the end I see that its the port 22 > not listening > > > > [root at lspal117 ~(keystone_demo)]# ip netns list > qrouter-9babbc60-1be0-42bc-8891-93e82b266f04 > qdhcp-5af3918a-8848-4678-9bf0-dcfcba5b280e > qrouter-5fc00c74-9277-4ddb-998e-2872ed2b3c90 > qdhcp-3af0fbce-b839-4323-b28a-525d7a3e4fbb > qrouter-51233ace-a447-4427-951d-848297092710 > qrouter-8728570d-1763-40c3-b162-f4932ef5aa9a > qdhcp-06541261-b30d-4656-9b4b-fe30566656ab > qrouter-6eea5082-e3f0-4a5f-a3b0-fb6110b97b9f > qrouter-7e07fef0-e92b-4956-9b23-82157d81ebf3 > qrouter-e05b9c4e-ee5e-4c02-b16a-099063f2ba66 > qrouter-d6325c88-e5b0-448e-8ab1-af5908a189d4 > qdhcp-6eb6d123-8fec-4984-986a-5eeabf895883 > qdhcp-d825e820-66e5-44b1-a91d-0c660aa822a5 > > > > root at lspal117 ~(keystone_demo)]# ip netns list |grep qrouter > qrouter-9babbc60-1be0-42bc-8891-93e82b266f04 > qrouter-5fc00c74-9277-4ddb-998e-2872ed2b3c90 > > > > [root at lspal117 ~(keystone_demo)]# ip netns exec > qdhcp-5af3918a-8848-4678-9bf0-dcfcba5b280e ssh root at 192.168.2.0 > ssh: connect to host 192.168.2.0 port 22: Network is unreachable > > > > Any ideas how to resolve to ssh to tenant IP: 192.168.2.0 from openstack > SSH. > FYI< last 2 days I did fix some issues and I was able to logon to SSH of > the tenant instance via floating IP: 10.48.146.119 but I cannot ssh to > tenant private IP: 192.168.2.0 from openstack node ? > > > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > > > > > > > On 1/14/15, 12:05 PM, "Dave Neary" wrote: > >> Hi, >> >> Have you checked the security rules to ensure that port 22 (ssh), port >> 80 (http) and ICMP are all allowed through to the instance? Tose rules >> are not enforces in the instance, they're enforced with iptables in the >> host. >> >> You might also try to connect to the instance from inside the same >> network namespace - just to check that you can. >> >> On the host, as root: >> ip netns list >> # Identify the network namespace corresponding to your instance >> # - look for a qrouter namespace >> # - List all of the routes in the namespace >> ip netns exec qrouter-1fabd5f0-f80b-468d-b733-1b80d0c3e80f \ >> ip r >> >> # ssh into guest >> $ ip netns exec qdhcp-4a04382f-03bf-49a9-9d4a-35ab9ffc22ad ssh >> cirros@${instance_ip_addr} >> >> This will at least eliminate the possibility that your instance is >> somehow broken. >> >> Thanks, >> Dave. >> On 01/09/2015 08:12 PM, Ns, Rushi wrote: >>> Hi Marius, >>> >>> Sorry I can assign the floating ip to the instnace (demo user launched >>> insetance) , however I cannot ping or ssh to the instances (192.168.1.4/ >>> 10.48.146.115) from the host but from the instance (192.168.1.2) I can >>> ping other instance 192.168.1.4 ? >>> >>> Can you help in this final step what is missing > >>> >>> >>> >>> >>> root at lspal117 tmp(keystone_admin)]# neutron port-list >>> >>> +--------------------------------------+------+-------------------+------ >>> ------------------------------------------------------------------------- >>> -------+ >>> | id | name | mac_address | >>> fixed_ips >>> | >>> >>> +--------------------------------------+------+-------------------+------ >>> ------------------------------------------------------------------------- >>> -------+ >>> | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | >>> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >>> "192.168.1.2"} | >>> | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | >>> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >>> "192.168.1.1"} | >>> | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | >>> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >>> "10.48.146.114"} | >>> | 65d568f4-d737-4f35-ab47-13042e3b6733 | | fa:16:3e:c9:dd:a9 | >>> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >>> "10.48.146.115"} | >>> | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | >>> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >>> "10.48.146.113"} | >>> | c02da939-99da-44c8-b462-9da7938626ba | | fa:16:3e:83:9e:77 | >>> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >>> "192.168.1.4"} | >>> | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | >>> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >>> "192.168.1.3"} | >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> >>> From: , SAP SAP > >>> Date: Friday, January 9, 2015 at 5:03 PM >>> To: Marius Cornea > >>> Cc: rdo-list > >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Here is it >>> >>> [root at lspal117 tmp(keystone_admin)]# neutron port-list >>> >>> +--------------------------------------+------+-------------------+------ >>> ------------------------------------------------------------------------- >>> -------+ >>> | id | name | mac_address | >>> fixed_ips >>> | >>> >>> +--------------------------------------+------+-------------------+------ >>> ------------------------------------------------------------------------- >>> -------+ >>> | 1939479b-78d7-4d7a-94da-006ef732e6d7 | | fa:16:3e:61:95:bd | >>> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >>> "192.168.1.2"} | >>> | 1986b9ae-543d-4f01-8f5a-ccf05bed3141 | | fa:16:3e:64:da:11 | >>> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >>> "192.168.1.1"} | >>> | 4706b287-d019-4b74-a8b6-e2e9f37eb74c | | fa:16:3e:25:2f:46 | >>> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >>> "10.48.146.114"} | >>> | 863e8fbc-5be4-408d-9945-3fb35dbd2052 | | fa:16:3e:25:73:00 | >>> {"subnet_id": "8b285f3a-ad73-4d2b-8e1e-dd59af16c463", "ip_address": >>> "10.48.146.113"} | >>> | dcaabff2-f21a-4ae0-9a1d-3a97def708e0 | | fa:16:3e:17:84:4c | >>> {"subnet_id": "0f5a93a6-a5f1-43a1-9a84-1ecc3aa6ac19", "ip_address": >>> "192.168.1.3"} | >>> >>> +--------------------------------------+------+-------------------+?????? >>> ?????????????????????????????????????+ >>> >>> >>> Best Regards, >>> >>> >>> >>> Rushi. >>> >>> Success is not a matter of being the best & winning the race. Success is >>> a matter of handling the worst & finishing the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 5:02 PM >>> To: SAP SAP > >>> Cc: rdo-list > >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> What does 'neutron port-list' show ? >>> >>> On Sat, Jan 10, 2015 at 1:56 AM, Ns, Rushi >> > wrote: >>> >>> I did that, launch instance got IP: 192.168.1.2 then I did >>> floating_IP which I got 10.48.146.114 , however I cannot assign to >>> the instance as there are no ports avilable.? >>> >>> >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & winning the race. >>> Success is a matter of handling the worst & finishing the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 4:52 PM >>> >>> To: SAP SAP > >>> Cc: rdo-list > >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack. >>> >>> Next launch an instance with demo-net attached. Then assign it a >>> floating IP. You should get 10.48.146.114 as the floating IP. >>> >>> On Sat, Jan 10, 2015 at 1:50 AM, Ns, Rushi >> > wrote: >>> >>> Thanks, I did this step . So what is next ? Sorry to bother but >>> you are really a life saver to me (thanks to you a ton) as well >>> kashyap . >>> >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & winning the race. >>> Success is a matter of handling the worst & finishing the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 4:46 PM >>> To: SAP SAP > >>> Cc: rdo-list > >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>> openstack. >>> >>> neutron net-create public --router:external=True >>> neutron subnet-create public 10.48.146.0/24 >>> --name vlan --enable_dhcp=False >>> --allocation_pool start=10.48.146.113,end=10.48.146.130 >>> --gateway 10.48.146.1 >>> >>> neutron net-create demo-net >>> neutron subnet-create demo-net --name demo-subnet --gateway >>> 192.168.1.1 192.168.1.0/24 >>> >>> neutron router-create demo-router >>> neutron router-interface-add demo-router demo-subnet >>> neutron router-gateway-set demo-router public >>> >>> >>> On Sat, Jan 10, 2015 at 1:35 AM, Ns, Rushi >> > wrote: >>> >>> I have deleted all network (admin) and tenant as I wanted >>> your guidance to do further >>> >>> Can you help to give steps to add the network again >>> (10.48.146.0/24 ) and tenant >>> 192.168.10.0/24 after floating ip >>> to 10.48.146.113) >>> >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & winning the >>> race. Success is a matter of handling the worst & finishing >>> the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 4:27 PM >>> >>> To: SAP SAP > >>> Cc: rdo-list >> > >>> Subject: Re: [Rdo-list] networking issues on JUNO redhead >>> openstack. >>> >>> Let's keep the troubleshooting steps on the list. What's the >>> output of 'nova list' ? >>> >>> On Sat, Jan 10, 2015 at 1:21 AM, Ns, Rushi >> > wrote: >>> >>> Yes, I did boot the instance but its getting 10.48.146.4 >>> address rather 192.168.*** that you gave me ? I can >>> logon to the instance console 10.48.146.4 and can ping >>> gateway 10.48.146.1 but I cannot ssh or ping from host? >>> >>> Is it possible I share my screen, so that you can guide >>> me what wrong thing that stops and bother me ? >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & winning the >>> race. Success is a matter of handling the worst & >>> finishing the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 4:18 PM >>> >>> To: SAP SAP > >>> Cc: rdo-list >> > >>> Subject: Re: [Rdo-list] networking issues on JUNO >>> redhead openstack. >>> >>> Did you boot the instance with the demo-net attached ? >>> >>> On Sat, Jan 10, 2015 at 1:16 AM, Ns, Rushi >>> > wrote: >>> >>> I can?t assign a port to the floating ip . I don?t? >>> see any ports available ? >>> >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & winning >>> the race. Success is a matter of handling the worst >>> & finishing the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 4:06 PM >>> >>> To: SAP SAP >> > >>> Cc: rdo-list >> > >>> Subject: Re: [Rdo-list] networking issues on JUNO >>> redhead openstack. >>> >>> You've already defined router1 which is already >>> connected to the external network. You can use that. >>> ext-net is the 'public' network in your case. >>> >>> On Sat, Jan 10, 2015 at 1:03 AM, Ns, Rushi >>> > wrote: >>> >>> I can?t run this command >>> >>> >>> $ neutron router-gateway-set demo-router ext-net >>> >>> Its getting error (ext-net not found) ? What is >>> the ext-net in this case ? >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & >>> winning the race. Success is a matter of >>> handling the worst & finishing the race >>> >>> >>> From: , SAP SAP >> > >>> Date: Friday, January 9, 2015 at 3:58 PM >>> >>> To: Marius Cornea >> > >>> Cc: rdo-list >> > >>> Subject: Re: [Rdo-list] networking issues on >>> JUNO redhead openstack. >>> >>> Ok I did the folowing steps for tenant. >>> >>> 1) neutron net-create demo-net >>> 2) neutron subnet-create demo-net --name >>> demo-subnet --gateway 10.48.146.1 10.48.146.0/24 >>> >>> 3) neutron router-create demo-router >>> 4) neutron router-interface-add demo-router >>> demo-subnet >>> >>> Anything left .? >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & >>> winning the race. Success is a matter of >>> handling the worst & finishing the race >>> >>> >>> >>> From: , SAP SAP >> > >>> Date: Friday, January 9, 2015 at 3:55 PM >>> To: Marius Cornea >> > >>> Cc: rdo-list >> > >>> Subject: Re: [Rdo-list] networking issues on >>> JUNO redhead openstack. >>> >>> Hi Marius, >>> >>> Yes, I can ping 10.48.146.113 (gateway) from the >>> host , can you provide the comamnds or link to >>> create tenant network, subjet and attach to >>> router ? >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & >>> winning the race. Success is a matter of >>> handling the worst & finishing the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 3:48 PM >>> To: SAP SAP >> > >>> Cc: rdo-list >> > >>> Subject: Re: [Rdo-list] networking issues on >>> JUNO redhead openstack. >>> >>> Can you ping 10.48.146.113 from your network? >>> You also need to create a tenant network, subnet >>> and attach it to the router. Boot the instance >>> with the tenant network attached and then assign >>> it the floating IP. >>> >>> >>> On Sat, Jan 10, 2015 at 12:20 AM, Ns, Rushi >>> > >>> wrote: >>> >>> Hi Marius, >>> >>> I did this first and now can see the BR-ex >>> is the same IP as my eno1 interface , you >>> are right I lost first while doing the first >>> command(ip addr del 10.48.146.77/24 >>> dev eno1) and then >>> conneting to console I did the second comand >>> (ovs-vsctl add-port br-ex eno1 and also >>> changed the IP address of br-ex to >>> 10.48.146.77) >>> >>> ip addr del 10.48.146.77/24 >>> dev eno1; >>> ovs-vsctl add-port br-ex eno1 >>> >>> Then after I removed all the routers, >>> networks and interfaces from openstack and >>> ran the following 4 commands. >>> >>> 1) source /root/keystonerc_admin >>> 2) neutron net-create public >>> --router:external=True >>> 3) neutron subnet-create public >>> 10.48.146.0/24 >>> --name vlan --enable_dhcp=False >>> --allocation_pool >>> start=10.48.146.113,end=10.48.146.130 >>> --gateway 10.48.146.1 >>> 4) neutron router-create router1 >>> 5) neutron router-gateway-set >>> 7e07fef0-e92b-4956-9b23-82157d81ebf3 >>> 1605ac0b-4f59-473d-b20f-911c3401dc2c >>> 6) neutron floatingip-create public >>> >>> The above command generated a floating IP >>> 10.48.146.115 >>> >>> Then I spin up a new instance and it got IP >>> assigned automatically 10.48.146.115, howevr >>> I cannot ping or ssh to that ip : >>> 10.48.146.115 ? >>> >>> Here are the screenshots >>> >>> >>> >>> >>> [root at lspal117 ~(keystone_admin)]# neutron >>> net-list >>> >>> +--------------------------------------+--------+------------------------ >>> -----------------------------+ >>> | id | >>> name | subnets >>> | >>> >>> +--------------------------------------+--------+------------------------ >>> -----------------------------+ >>> | 1605ac0b-4f59-473d-b20f-911c3401dc2c | >>> public | >>> 24f385ad-bfeb-4c62-91ff-ab8756d3983b >>> 10.48.146.0/24 | >>> >>> +--------------------------------------+--------+???????????????????????? >>> ??+ >>> >>> [root at lspal117 ~(keystone_admin)]# neutron >>> subnet-list >>> >>> +--------------------------------------+------+----------------+--------- >>> -------------------------------------------+ >>> | id | >>> name | cidr | allocation_pools >>> | >>> >>> +--------------------------------------+------+----------------+--------- >>> -------------------------------------------+ >>> | 24f385ad-bfeb-4c62-91ff-ab8756d3983b | >>> vlan | 10.48.146.0/24 >>> | {"start": >>> "10.48.146.113", "end": "10.48.146.130"} | >>> >>> +--------------------------------------+------+----------------+--------- >>> -------------------------------------------+ >>> >>> [root at lspal117 ~(keystone_admin)]#neutron >>> router-list >>> >>> +--------------------------------------+---------+----------------------- >>> ------------------------------------------------------------------------- >>> ------------------------------------------------------------------------- >>> ------------------+-------------+-------+ >>> | id | >>> name | external_gateway_info >>> >>> >>> >>> | distributed | ha | >>> >>> +--------------------------------------+---------+----------------------- >>> ------------------------------------------------------------------------- >>> ------------------------------------------------------------------------- >>> ------------------+-------------+-------+ >>> | 7e07fef0-e92b-4956-9b23-82157d81ebf3 | >>> router1 | {"network_id": >>> "1605ac0b-4f59-473d-b20f-911c3401dc2c", >>> "enable_snat": true, "external_fixed_ips": >>> [{"subnet_id": >>> "24f385ad-bfeb-4c62-91ff-ab8756d3983b", >>> "ip_address": "10.48.146.113"}]} | False >>> | False | >>> >>> +--------------------------------------+---------+----------------------- >>> ------------------------------------------------------------------------- >>> ------------------------------------------------------------------------- >>> ------------------+-------------+-------+ >>> >>> Any ideas what is going wrong, I still can?t >>> ping or ssh to that IP address and its not >>> listening anywhere ? >>> >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the best & >>> winning the race. Success is a matter of >>> handling the worst & finishing the race >>> >>> >>> >>> From: Marius Cornea >> > >>> Date: Friday, January 9, 2015 at 2:30 PM >>> To: SAP SAP >> >, rdo-list >>> >> > >>> >>> Subject: Re: [Rdo-list] networking issues on >>> JUNO redhead openstack. >>> >>> As Kashyap kindly suggested we're not a >>> support line and information here should be >>> available for all the community members. >>> First, I don't see how you can ping the >>> br-ex IP address from an external network >>> since it doesn't contain any physical >>> interface. Make sure that 10.48.146.112 >>> isn't used by other host on you network >>> segment. You can do the following to remove >>> the ip address from the physical interface >>> and add it to the br-ex bridge. Please make >>> sure that you've got console access to the >>> server before doing this as you may lose >>> connectivity. >>> >>> # ip addr del 10.48.146.77/24 >>> dev eno1; >>> ovs-vsctl add-port br-ex eno1 >>> >>> You should then follow the documentation[1] >>> to recreate the public/tenant networks and >>> router. In your >>> case FLOATING_IP_START, FLOATING_IP_END >>> should be part of the 10.48.146.0/24 >>> network. Let's say >>> you wish to allocate IP addresses of the >>> 10.48.146.200 - 10.48.146.210 range to your >>> Openstack routers/instances, then >>> FLOATING_IP_START=10.48.146.200 and >>> FLOATING_IP_END=10.48.146.210. >>> EXTERNAL_NETWORK_GATEWAY >>> should be set to what 'ip r | grep default | >>> awk {'print $3'}' outputs >>> and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24 >>> . >>> >>> Note that the instance will get an IP >>> address of the tenant network. By assigning >>> a floating IP you will be able to access it >>> through an IP address from your physical >>> network segment. >>> >>> [1] >>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_ >>> initial-external-network.html >>> >>> >>> >>> On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi >>> > >>> wrote: >>> >>> Hi Marius, >>> >>> Here are the outputs. Is it possible to >>> reach you on phone so that I can explain >>> more than email. You can call me at 650 >>> 849 3915 or let >>> me know your number. >>> >>> #ip a >>> >>> [root at lspal117 >>> network-scripts(keystone_admin)]# ip a >>> 1: lo: mtu 65536 >>> qdisc noqueue state UNKNOWN >>> link/loopback 00:00:00:00:00:00 brd >>> 00:00:00:00:00:00 >>> inet 127.0.0.1/8 >>> scope host lo >>> valid_lft forever preferred_lft >>> forever >>> inet6 ::1/128 scope host >>> valid_lft forever preferred_lft >>> forever >>> 2: eno1: >>> mtu >>> 1500 qdisc mq state UP qlen 1000 >>> link/ether d8:9d:67:29:c6:94 brd >>> ff:ff:ff:ff:ff:ff >>> inet 10.48.146.77/24 >>> brd >>> 10.48.146.255 scope global eno1 >>> valid_lft forever preferred_lft >>> forever >>> inet6 fe80::da9d:67ff:fe29:c694/64 >>> scope link >>> valid_lft forever preferred_lft >>> forever >>> 3: eno2: >>> mtu >>> 1500 qdisc mq state DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:95 brd >>> ff:ff:ff:ff:ff:ff >>> 4: eno3: >>> mtu >>> 1500 qdisc mq state DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:96 brd >>> ff:ff:ff:ff:ff:ff >>> 5: eno4: >>> mtu >>> 1500 qdisc mq state DOWN qlen 1000 >>> link/ether d8:9d:67:29:c6:97 brd >>> ff:ff:ff:ff:ff:ff >>> 6: ens1f0: >>> mtu >>> 1500 qdisc mq state DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:b4 brd >>> ff:ff:ff:ff:ff:ff >>> 7: ens1f1: >>> mtu >>> 1500 qdisc mq state DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:b5 brd >>> ff:ff:ff:ff:ff:ff >>> 8: ens2f0: >>> mtu >>> 1500 qdisc mq state DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:40 brd >>> ff:ff:ff:ff:ff:ff >>> 9: ens2f1: >>> mtu >>> 1500 qdisc mq state DOWN qlen 1000 >>> link/ether 38:ea:a7:8f:bf:41 brd >>> ff:ff:ff:ff:ff:ff >>> 10: ovs-system: >>> mtu 1500 qdisc noop state DOWN >>> link/ether 16:02:ac:3f:05:f4 brd >>> ff:ff:ff:ff:ff:ff >>> 11: br-ex: >>> mtu >>> 1500 qdisc noqueue state UNKNOWN >>> link/ether be:8b:24:03:a9:47 brd >>> ff:ff:ff:ff:ff:ff >>> inet 10.48.146.112/24 >>> brd >>> 10.48.146.255 scope global br-ex >>> valid_lft forever preferred_lft >>> forever >>> inet6 fe80::bc8b:24ff:fe03:a947/64 >>> scope link >>> valid_lft forever preferred_lft >>> forever >>> 12: br-int: mtu >>> 1500 qdisc noop state DOWN >>> link/ether 02:35:a4:7c:e5:4c brd >>> ff:ff:ff:ff:ff:ff >>> 16: br-tun: mtu >>> 1500 qdisc noop state DOWN >>> link/ether fe:61:30:fb:a3:47 brd >>> ff:ff:ff:ff:ff:ff >>> 17: qbr63bd6704-47: >>> mtu >>> 1500 qdisc noqueue state UP >>> link/ether 8e:fe:6e:19:61:5c brd >>> ff:ff:ff:ff:ff:ff >>> inet6 fe80::3822:bcff:fe6a:b74f/64 >>> scope link >>> valid_lft forever preferred_lft >>> forever >>> 18: qvo63bd6704-47: >>> >>> mtu >>> 1500 qdisc pfifo_fast master ovs-system >>> state UP qlen 1000 >>> link/ether a2:fe:04:5f:04:b4 brd >>> ff:ff:ff:ff:ff:ff >>> 19: qvb63bd6704-47: >>> >>> mtu >>> 1500 qdisc pfifo_fast master >>> qbr63bd6704-47 state UP qlen 1000 >>> link/ether 8e:fe:6e:19:61:5c brd >>> ff:ff:ff:ff:ff:ff >>> 22: tap63bd6704-47: >>> mtu >>> 1500 qdisc pfifo_fast master >>> qbr63bd6704-47 state UNKNOWN qlen 500 >>> link/ether fe:16:3e:d9:5e:ba brd >>> ff:ff:ff:ff:ff:ff >>> inet6 fe80::fc16:3eff:fed9:5eba/64 >>> scope link >>> valid_lft forever preferred_lft >>> forever >>> >>> # ovs-vsctl show >>> >>> [root at lspal117 >>> network-scripts(keystone_admin)]# >>> ovs-vsctl show >>> c5bcc161-86cd-4004-9729-c1ba05d28569 >>> Bridge br-ex >>> Port br-ex >>> Interface br-ex >>> type: internal >>> Port "qg-c3a1b534-36" >>> Interface "qg-c3a1b534-36" >>> type: internal >>> Bridge br-int >>> fail_mode: secure >>> Port patch-tun >>> Interface patch-tun >>> type: patch >>> options: >>> {peer=patch-int} >>> Port "tape386c0cb-d8" >>> tag: 1 >>> Interface "tape386c0cb-d8" >>> type: internal >>> Port br-int >>> Interface br-int >>> type: internal >>> Port "qvo63bd6704-47" >>> tag: 1 >>> Interface "qvo63bd6704-47" >>> Port "tap44dd465f-d4" >>> tag: 4095 >>> Interface "tap44dd465f-d4" >>> type: internal >>> Port "qr-e0ac3c25-2b" >>> tag: 2 >>> Interface "qr-e0ac3c25-2b" >>> type: internal >>> Bridge br-tun >>> Port br-tun >>> Interface br-tun >>> type: internal >>> Port patch-int >>> Interface patch-int >>> type: patch >>> options: >>> {peer=patch-tun} >>> ovs_version: ?2.1.3" >>> >>> # neutron net-list >>> [root at lspal117 >>> network-scripts(keystone_admin)]# >>> neutron net-list >>> >>> +--------------------------------------+---------+----------------------- >>> -------------------------------+ >>> | id | >>> name | subnets >>> | >>> >>> +--------------------------------------+---------+----------------------- >>> -------------------------------+ >>> | 5abe660b-52da-4d36-8275-4c1488df88b4 | >>> public | >>> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a >>> 172.24.4.224/28 >>> | >>> | d825e820-66e5-44b1-a91d-0c660aa822a5 | >>> private | >>> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 >>> 10.0.0.0/24 | >>> | 6eb6d123-8fec-4984-986a-5eeabf895883 | >>> sap | >>> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 >>> 10.48.146.0/24 >>> | >>> >>> +--------------------------------------+---------+----------------------- >>> -------------------------------+ >>> >>> # neutron subnet-list >>> [root at lspal117 >>> network-scripts(keystone_admin)]# >>> neutron subnet-list >>> >>> +--------------------------------------+----------------+---------------- >>> -+----------------------------------------------------+ >>> | id | >>> name | cidr | >>> allocation_pools >>> | >>> >>> +--------------------------------------+----------------+---------------- >>> -+----------------------------------------------------+ >>> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | >>> public_subnet | 172.24.4.224/28 >>> | {"start": >>> "172.24.4.226", "end": "172.24.4.238"} >>> | >>> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | >>> private_subnet | 10.0.0.0/24 >>> | {"start": >>> "10.0.0.2", "end": "10.0.0.254"} >>> | >>> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | >>> sap_local | 10.48.146.0/24 >>> | {"start": >>> "10.48.146.112", "end": >>> "10.48.146.120"} | >>> >>> +--------------------------------------+----------------+---------------- >>> -+??????????????????????????+ >>> >>> #neutron router-list >>> [root at lspal117 >>> network-scripts(keystone_admin)]# >>> neutron router-list >>> >>> +--------------------------------------+---------+----------------------- >>> ------------------------------------------------------------------------- >>> ------------------------------------------------------------------------- >>> -----------------+-------------+-------+ >>> | id | >>> name | external_gateway_info >>> >>> >>> >>> | >>> distributed | ha | >>> >>> +--------------------------------------+---------+----------------------- >>> ------------------------------------------------------------------------- >>> ------------------------------------------------------------------------- >>> -----------------+-------------+-------+ >>> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | >>> router1 | {"network_id": >>> "5abe660b-52da-4d36-8275-4c1488df88b4", >>> "enable_snat": true, >>> "external_fixed_ips": [{"subnet_id": >>> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", >>> "ip_address": "172.24.4.226"}]} | False >>> | False | >>> >>> +--------------------------------------+---------+----------------------- >>> ------------------------------------------------------------------------- >>> ------------------------------------------------------------------------- >>> -----------------+-------------+???+ >>> >>> In my system I have IP address for BR-ex >>> and ENO1 (interface connecting ), should >>> I disable eno1 as I can ping both (br-ex >>> and eno1) from my network to reach to >>> this host ? Probably its a dump >>> question. >>> >>> Here are the outputs. >>> >>> br-ex: >>> >>> flags=4163 >>> mtu 1500 >>> inet 10.48.146.112 netmask >>> 255.255.255.0 broadcast 10.48.146.255 >>> inet6 fe80::bc8b:24ff:fe03:a947 >>> prefixlen 64 scopeid 0x20 >>> ether be:8b:24:03:a9:47 >>> txqueuelen 0 (Ethernet) >>> RX packets 10 bytes 864 (864.0 >>> B) >>> RX errors 0 dropped 0 overruns >>> 0 frame 0 >>> TX packets 25 bytes 3767 (3.6 >>> KiB) >>> TX errors 0 dropped 0 overruns >>> 0 carrier 0 collisions 0 >>> >>> br-int: flags=4098 >>> mtu 1500 >>> ether 02:35:a4:7c:e5:4c >>> txqueuelen 0 (Ethernet) >>> RX packets 135 bytes 7574 (7.3 >>> KiB) >>> RX errors 0 dropped 0 overruns >>> 0 frame 0 >>> TX packets 0 bytes 0 (0.0 B) >>> TX errors 0 dropped 0 overruns >>> 0 carrier 0 collisions 0 >>> >>> br-tun: flags=4098 >>> mtu 1500 >>> ether fe:61:30:fb:a3:47 >>> txqueuelen 0 (Ethernet) >>> RX packets 0 bytes 0 (0.0 B) >>> RX errors 0 dropped 0 overruns >>> 0 frame 0 >>> TX packets 0 bytes 0 (0.0 B) >>> TX errors 0 dropped 0 overruns >>> 0 carrier 0 collisions 0 >>> >>> eno1: >>> >>> flags=4163 >>> mtu 1500 >>> inet 10.48.146.77 netmask >>> 255.255.255.0 broadcast 10.48.146.255 >>> inet6 fe80::da9d:67ff:fe29:c694 >>> prefixlen 64 scopeid 0x20 >>> ether d8:9d:67:29:c6:94 >>> txqueuelen 1000 (Ethernet) >>> RX packets 467319 bytes >>> 48391354 (46.1 MiB) >>> RX errors 0 dropped 0 overruns >>> 0 frame 0 >>> TX packets 14794 bytes 5238733 >>> (4.9 MiB) >>> TX errors 0 dropped 0 overruns >>> 0 carrier 0 collisions 0 >>> device interrupt 32 >>> >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the >>> best & winning the race. Success is a >>> matter of handling the worst & finishing >>> the race >>> >>> >>> >>> From: Marius Cornea >>> >> > >>> Date: Friday, January 9, 2015 at 1:46 PM >>> To: SAP SAP >> > >>> Subject: Re: [Rdo-list] networking >>> issues on JUNO redhead openstack. >>> >>> Hi Rushi, >>> >>> Can you provide the output of the >>> following commands on your node ? >>> >>> # ip a >>> # ovs-vsctl show >>> # neutron net-list >>> # neutron subnet-list >>> # neutron router-list >>> >>> Please note that only the br-ex bridge >>> requires an IP address, the interface >>> that's part of it shouldn't have one >>> assigned. Also the floating IP addresses >>> will be used for DNAT on the tenant >>> router. You can check the documentation >>> here[1] that describes the use of >>> floating IPs. >>> >>> You can also check the upstream >>> documentation[2] on how to create the >>> networks. >>> >>> [1] >>> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_I >>> P >>> [2] >>> >>> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_ >>> initial-external-network.html >>> >>> Tnx, >>> Marius >>> >>> On Fri, Jan 9, 2015 at 10:22 PM, Ns, >>> Rushi >> > wrote: >>> >>> Hi Support, >>> >>> I have a problem that a launched >>> instance from openstack cannot >>> connect to SSH or PING >>> >>> First of all I have dump question >>> whether my system should be NOVA >>> network or Neutron network. Well to >>> keep everyone on the same page. Here >>> is my history. >>> >>> 1. I did install RDO (allinone >>> host) using the bellow steps >>> >>> https://openstack.redhat.com/Quickstart >>> 2. Then I have used the following >>> steps for floating >>> IP >>> https://openstack.redhat.com/Floating_IP_range. >>> >>> My situtation is as follows. >>> * Floating IP address assignment: >>> I have assigned a floating IP , I >>> did follow this steps. >>> >>> https://openstack.redhat.com/Floating_IP_range >>> >>> * Bridge configuration:My Ethernet >>> device eth0(actually in Redhat 7 it >>> is eno1 name)is on the same bridge >>> as the compute host >>> Yes, ethernet device on 10.48.146.78 >>> address and br-ex interface on >>> 10.48.146.112 >>> >>> * DHCP configuration: Yes, DHCP >>> configuration is set and Neutron >>> hearing and responding to DHCP >>> requests and the instance is getting >>> IP from 10.48.146.113 (next hop) >>> however I cannot ping/ssh to that IP >>> address (ICMP/SSH is added allowed >>> rule on default security group) >>> >>> Here is the little diagram of my >>> system. >>> >>> Can someone help to find what is >>> missing. >>> >>> >>> >>> Best Regards,____ >>> >>> >>> >>> Rushi.____ >>> >>> Success is not a matter of being the >>> best & winning the race. Success is >>> a matter of handling the worst & >>> finishing the race >>> >>> >>> >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> >>> >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >> >> -- >> Dave Neary - NFV/SDN Community Strategy >> Open Source and Standards, Red Hat - http://community.redhat.com >> Ph: +1-978-399-2182 / Cell: +1-978-799-3338 > -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338 From kchamart at redhat.com Wed Jan 14 21:15:42 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Wed, 14 Jan 2015 22:15:42 +0100 Subject: [Rdo-list] networking issues on JUNO redhead openstack. In-Reply-To: References: Message-ID: <20150114211542.GA8495@tesla.redhat.com> Rushi, A gentle reminder: This is a community mailing list and is best-effort based. If you noticed, on this mailing list, by far, the level of community effort on this thread had the most back and forth. Maintaining a sense of balance in taking vs. giving from the community is important. One cannot make excessive demands on time or instant reactions. If you need timely responses there are other avenues of support that you can explore. Some useful reading in the context of community mailing lists: https://rwmj.wordpress.com/2010/11/08/want-help-dont-email-me-directly/ -- /kashyap From waltervalenti at yahoo.it Thu Jan 15 11:04:58 2015 From: waltervalenti at yahoo.it (Walter Valenti) Date: Thu, 15 Jan 2015 11:04:58 +0000 (UTC) Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph Message-ID: <1535060816.1565352.1421319898465.JavaMail.yahoo@jws11125.mail.ir2.yahoo.com> Hi, we're trying Juno with Ceph (Giant) integration on Centos7. The problem is that Cinder-Volume ignores, the directives for use rbd protocol, but every uses LVM. This is our rbd configuration in cinder.conf: [DEFAULT] volume_driver=cinder.volume.drivers.rbd.RBDDriver [rbd] rbd_pool=volumes rbd_user=cinder rbd_ceph_conf=etc/ceph/ceph.conf rbd_flatten_volume_from_snapshot=false rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471 rbd_max_clone_depth=5 rbd_store_chunk_size=4 rados_connect_timeout=-1 We also tried with all configuration in "rdb" section, and with all configuration in DEFAULT section, but the problem is the same. Any ideas?? Thanks Walter From docana at ebi.ac.uk Thu Jan 15 15:38:00 2015 From: docana at ebi.ac.uk (David Ocana) Date: Thu, 15 Jan 2015 15:38:00 +0000 Subject: [Rdo-list] Can't delete network from neutron Message-ID: <54B7DED8.7000700@ebi.ac.uk> Hi everyone, I installed juno rdo and I was playing with it until I got stuck trying to delete a private network. I have been googling around I found possible reasons but none of the solutions worked for me. Here is what I did: # neutron net-delete 9a427447-3f9f-4dc5-94f8-bc273a7e7cf0 Conflict (HTTP 409) (Request-ID: req-d1c79aaa-25f4-40cf-91c4-fde63d54708a) So I thought I had to delete the subnet first: # neutron subnet-delete 329476b1-7ea7-41e5-a357-445b143086fe Conflict (HTTP 409) (Request-ID: req-7ff81f34-10ee-4eb1-b3f0-ebbc7283af4e) Then I checked if there were any ports for this subnet: # neutron port-list | grep 329 | e5d4effb-6a67-4f90-ad2c-01dca00c9e42 | | fa:16:3e:ff:ee:1d | {"subnet_id": "329476b1-7ea7-41e5-a357-445b143086fe", "ip_address": "192.168.1.1"} | Then I tried to delete the port but I get the same: # neutron port-delete e5d4effb-6a67-4f90-ad2c-01dca00c9e42 Conflict (HTTP 409) (Request-ID: req-6e8789f4-cd92-46fb-9ff4-db14faeb6503) I tried disabling the port first but it didn't work either. Tenant is brand new, has no instances, no volumes, nothing besides the network. Any ideas? Thanks, David From waltervalenti at yahoo.it Thu Jan 15 15:42:03 2015 From: waltervalenti at yahoo.it (Walter Valenti) Date: Thu, 15 Jan 2015 15:42:03 +0000 (UTC) Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph In-Reply-To: <1595951232.9765758.1421335804310.JavaMail.zimbra@redhat.com> References: <1595951232.9765758.1421335804310.JavaMail.zimbra@redhat.com> Message-ID: <729757159.1708607.1421336523279.JavaMail.yahoo@jws11166.mail.ir2.yahoo.com> Yes, I've installed. ----- Messaggio originale ----- > Da: Yogev Rabl > A: Walter Valenti > Cc: > Inviato: Gioved? 15 Gennaio 2015 16:30 > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph > > did you install ceph-common & python-ceph? > > > ----- Original Message ----- >> From: "Walter Valenti" >> To: "Yogev Rabl" >> Sent: Thursday, January 15, 2015 5:08:51 PM >> Subject: Re: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> Yes, with enabled_backends = rbd, >> Cinder-Volume tries to use Ceph, but now I've >> got the following error: >> >> WARNING cinder.volume.manager [-] Unable to update volume replication > status, >> RBDDriver -1.1.0 (config name rbd) driver is uninitialized. >> >> >> >> Walter >> >> >> >> >> >> >> ----- Messaggio originale ----- >> > Da: Yogev Rabl >> > A: waltervalenti at yahoo.itYe >> > Cc: >> > Inviato: Gioved? 15 Gennaio 2015 14:18 >> > Oggetto: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph >> > >> > Hi Walter, >> > >> > You this configuration is incorrect from what I know. >> > >> > try this: >> > >> > [DEFAULT] >> > >> > enabled_backends = rbd >> > >> > [rbd] >> > volume_driver=cinder.volume.drivers.rbd.RBDDriver >> > rbd_pool=volumes >> > rbd_ceph_conf=etc/ceph/ceph.conf >> > rbd_flatten_volume_from_snapshot=false >> > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf747 >> > rbd_max_clone_depth=5 >> > rbd_store_chunk_size=4 >> > rados_connect_timeout=-1 >> > >> > >> > In addition, I've just finish to write a small tool in python that >> > configures Ceph in Openstack components configuration files (and set > the >> > pools + >> > keyrings in the Ceph server). >> > You can have a look at it in github: >> > https://github.com/yorabl/Openstack-Ceph >> > >> > Good luck, >> > Yogev Rabl >> > Quality Engineer, >> > RHOS storage >> > Red Hat >> > >> >> ----- Forwarded Message ----- >> >> From: "Walter Valenti" >> >> To: rdo-list at redhat.com >> >> Sent: Thursday, January 15, 2015 1:04:58 PM >> >> Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> >> >> Hi, >> >> we're trying Juno with Ceph (Giant) integration on Centos7. >> >> >> >> The problem is that Cinder-Volume ignores, the directives >> >> for use rbd protocol, but every uses LVM. >> >> >> >> This is our rbd configuration in cinder.conf: >> >> >> >> [DEFAULT] >> >> >> >> volume_driver=cinder.volume.drivers.rbd.RBDDriver >> >> [rbd] >> >> rbd_pool=volumes >> >> rbd_user=cinder >> >> rbd_ceph_conf=etc/ceph/ceph.conf >> >> rbd_flatten_volume_from_snapshot=false >> >> rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471 >> >> rbd_max_clone_depth=5 >> >> rbd_store_chunk_size=4 >> >> rados_connect_timeout=-1 >> >> >> >> We also tried with all configuration in "rdb" section, > and >> >> with all configuration in DEFAULT section, but the problem is the > same. >> >> >> >> >> >> Any ideas?? >> >> >> >> Thanks >> >> Walter >> >> >> >> _______________________________________________ >> >> Rdo-list mailing list >> >> Rdo-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> > >> > From rushi.ns at sap.com Thu Jan 15 15:51:39 2015 From: rushi.ns at sap.com (Ns, Rushi) Date: Thu, 15 Jan 2015 15:51:39 +0000 Subject: [Rdo-list] Can't delete network from neutron In-Reply-To: <54B7DED8.7000700@ebi.ac.uk> References: <54B7DED8.7000700@ebi.ac.uk> Message-ID: You need remove router and interface then remove subnet as well others, you can do all these on dashboard with user admin, please remove router first . Let me know. BR, Rushi Sent from my iPhone please excuse typos and brevity > On Jan 15, 2015, at 7:42 AM, David Ocana wrote: > > Hi everyone, > > I installed juno rdo and I was playing with it until I got stuck trying to delete a private network. I have been googling around I found possible reasons but none of the solutions worked for me. > > Here is what I did: > > # neutron net-delete 9a427447-3f9f-4dc5-94f8-bc273a7e7cf0 > Conflict (HTTP 409) (Request-ID: req-d1c79aaa-25f4-40cf-91c4-fde63d54708a) > > So I thought I had to delete the subnet first: > > # neutron subnet-delete 329476b1-7ea7-41e5-a357-445b143086fe > Conflict (HTTP 409) (Request-ID: req-7ff81f34-10ee-4eb1-b3f0-ebbc7283af4e) > > Then I checked if there were any ports for this subnet: > > # neutron port-list | grep 329 > | e5d4effb-6a67-4f90-ad2c-01dca00c9e42 | | fa:16:3e:ff:ee:1d | {"subnet_id": "329476b1-7ea7-41e5-a357-445b143086fe", "ip_address": "192.168.1.1"} | > > Then I tried to delete the port but I get the same: > > # neutron port-delete e5d4effb-6a67-4f90-ad2c-01dca00c9e42 > Conflict (HTTP 409) (Request-ID: req-6e8789f4-cd92-46fb-9ff4-db14faeb6503) > > I tried disabling the port first but it didn't work either. Tenant is brand new, has no instances, no volumes, nothing besides the network. > > Any ideas? > > Thanks, > David > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From yrabl at redhat.com Thu Jan 15 15:53:05 2015 From: yrabl at redhat.com (Yogev Rabl) Date: Thu, 15 Jan 2015 10:53:05 -0500 (EST) Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph In-Reply-To: <729757159.1708607.1421336523279.JavaMail.yahoo@jws11166.mail.ir2.yahoo.com> References: <1595951232.9765758.1421335804310.JavaMail.zimbra@redhat.com> <729757159.1708607.1421336523279.JavaMail.yahoo@jws11166.mail.ir2.yahoo.com> Message-ID: <63638320.9786450.1421337185983.JavaMail.zimbra@redhat.com> Did you go through 4th point in section, Install Virtualization for Ceph Block Devices, in this manual: https://openstack.redhat.com/Using_Ceph_for_block_storage_with_RDO ? Yogev ----- Original Message ----- > From: "Walter Valenti" > To: "Yogev Rabl" > Cc: rdo-list at redhat.com > Sent: Thursday, January 15, 2015 5:42:03 PM > Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph > > > > Yes, I've installed. > > > > > > ----- Messaggio originale ----- > > Da: Yogev Rabl > > A: Walter Valenti > > Cc: > > Inviato: Gioved? 15 Gennaio 2015 16:30 > > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph > > > > did you install ceph-common & python-ceph? > > > > > > ----- Original Message ----- > >> From: "Walter Valenti" > >> To: "Yogev Rabl" > >> Sent: Thursday, January 15, 2015 5:08:51 PM > >> Subject: Re: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph > >> > >> Yes, with enabled_backends = rbd, > >> Cinder-Volume tries to use Ceph, but now I've > >> got the following error: > >> > >> WARNING cinder.volume.manager [-] Unable to update volume replication > > status, > >> RBDDriver -1.1.0 (config name rbd) driver is uninitialized. > >> > >> > >> > >> Walter > >> > >> > >> > >> > >> > >> > >> ----- Messaggio originale ----- > >> > Da: Yogev Rabl > >> > A: waltervalenti at yahoo.itYe > >> > Cc: > >> > Inviato: Gioved? 15 Gennaio 2015 14:18 > >> > Oggetto: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph > >> > > >> > Hi Walter, > >> > > >> > You this configuration is incorrect from what I know. > >> > > >> > try this: > >> > > >> > [DEFAULT] > >> > > >> > enabled_backends = rbd > >> > > >> > [rbd] > >> > volume_driver=cinder.volume.drivers.rbd.RBDDriver > >> > rbd_pool=volumes > >> > rbd_ceph_conf=etc/ceph/ceph.conf > >> > rbd_flatten_volume_from_snapshot=false > >> > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf747 > >> > rbd_max_clone_depth=5 > >> > rbd_store_chunk_size=4 > >> > rados_connect_timeout=-1 > >> > > >> > > >> > In addition, I've just finish to write a small tool in python that > >> > configures Ceph in Openstack components configuration files (and set > > the > >> > pools + > >> > keyrings in the Ceph server). > >> > You can have a look at it in github: > >> > https://github.com/yorabl/Openstack-Ceph > >> > > >> > Good luck, > >> > Yogev Rabl > >> > Quality Engineer, > >> > RHOS storage > >> > Red Hat > >> > > >> >> ----- Forwarded Message ----- > >> >> From: "Walter Valenti" > >> >> To: rdo-list at redhat.com > >> >> Sent: Thursday, January 15, 2015 1:04:58 PM > >> >> Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph > >> >> > >> >> Hi, > >> >> we're trying Juno with Ceph (Giant) integration on Centos7.RBDDriver -1.1.0 (config name rbd) driver is uninitialized > >> >> > >> >> The problem is that Cinder-Volume ignores, the directives > >> >> for use rbd protocol, but every uses LVM. > >> >> > >> >> This is our rbd configuration in cinder.conf: > >> >> > >> >> [DEFAULT] > >> >> > >> >> volume_driver=cinder.volume.drivers.rbd.RBDDriver > >> >> [rbd] > >> >> rbd_pool=volumes > >> >> rbd_user=cinder > >> >> rbd_ceph_conf=etc/ceph/ceph.conf > >> >> rbd_flatten_volume_from_snapshot=false > >> >> rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471 > >> >> rbd_max_clone_depth=5 > >> >> rbd_store_chunk_size=4 > >> >> rados_connect_timeout=-1 > >> >> > >> >> We also tried with all configuration in "rdb" section, > > and > >> >> with all configuration in DEFAULT section, but the problem is the > > same. > >> >> > >> >> > >> >> Any ideas?? > >> >> > >> >> Thanks > >> >> Walter > >> >> > >> >> _______________________________________________ > >> >> Rdo-list mailing list > >> >> Rdo-list at redhat.com > >> >> https://www.redhat.com/mailman/listinfo/rdo-list > >> >> > >> > > >> > > > From waltervalenti at yahoo.it Thu Jan 15 16:29:32 2015 From: waltervalenti at yahoo.it (Walter Valenti) Date: Thu, 15 Jan 2015 16:29:32 +0000 (UTC) Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph In-Reply-To: <63638320.9786450.1421337185983.JavaMail.zimbra@redhat.com> References: <63638320.9786450.1421337185983.JavaMail.zimbra@redhat.com> Message-ID: <1387038938.1784088.1421339372824.JavaMail.yahoo@jws11134.mail.ir2.yahoo.com> I've followed directly the ceph documentation. Reading the RDO documentation, at point 4 of "Install Virtualization for Ceph Block Devices" tells: Older releases of RHEL and CentOS don't provide the rbd format required for use with Ceph. Now, I think: Centos7 isn't a older release. But the execution of "qemu-img -f", give me: vvfat vpc vmdk vhdx vdi sheepdog sheepdog sheepdog raw host_cdrom host_floppy host_device file qed qcow2 qcow parallels nbd nbd nbd iscsi gluster gluster gluster gluster dmg cow cloop bochs blkverify blkdebug There isn't "rdb".... Why ???? Walter ----- Messaggio originale ----- > Da: Yogev Rabl > A: Walter Valenti > Cc: rdo-list at redhat.com > Inviato: Gioved? 15 Gennaio 2015 16:53 > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph > > Did you go through 4th point in section, Install Virtualization for Ceph Block > Devices, in this manual: > https://openstack.redhat.com/Using_Ceph_for_block_storage_with_RDO ? > > Yogev > > ----- Original Message ----- >> From: "Walter Valenti" >> To: "Yogev Rabl" >> Cc: rdo-list at redhat.com >> Sent: Thursday, January 15, 2015 5:42:03 PM >> Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> >> >> Yes, I've installed. >> >> >> >> >> >> ----- Messaggio originale ----- >> > Da: Yogev Rabl >> > A: Walter Valenti >> > Cc: >> > Inviato: Gioved? 15 Gennaio 2015 16:30 >> > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >> > >> > did you install ceph-common & python-ceph? >> > >> > >> > ----- Original Message ----- >> >> From: "Walter Valenti" >> >> To: "Yogev Rabl" >> >> Sent: Thursday, January 15, 2015 5:08:51 PM >> >> Subject: Re: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> >> >> Yes, with enabled_backends = rbd, >> >> Cinder-Volume tries to use Ceph, but now I've >> >> got the following error: >> >> >> >> WARNING cinder.volume.manager [-] Unable to update volume > replication >> > status, >> >> RBDDriver -1.1.0 (config name rbd) driver is uninitialized. >> >> >> >> >> >> >> >> Walter >> >> >> >> >> >> >> >> >> >> >> >> >> >> ----- Messaggio originale ----- >> >> > Da: Yogev Rabl >> >> > A: waltervalenti at yahoo.itYe >> >> > Cc: >> >> > Inviato: Gioved? 15 Gennaio 2015 14:18 >> >> > Oggetto: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> > >> >> > Hi Walter, >> >> > >> >> > You this configuration is incorrect from what I know. >> >> > >> >> > try this: >> >> > >> >> > [DEFAULT] >> >> > >> >> > enabled_backends = rbd >> >> > >> >> > [rbd] >> >> > volume_driver=cinder.volume.drivers.rbd.RBDDriver >> >> > rbd_pool=volumes >> >> > rbd_ceph_conf=etc/ceph/ceph.conf >> >> > rbd_flatten_volume_from_snapshot=false >> >> > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf747 >> >> > rbd_max_clone_depth=5 >> >> > rbd_store_chunk_size=4 >> >> > rados_connect_timeout=-1 >> >> > >> >> > >> >> > In addition, I've just finish to write a small tool in > python that >> >> > configures Ceph in Openstack components configuration files > (and set >> > the >> >> > pools + >> >> > keyrings in the Ceph server). >> >> > You can have a look at it in github: >> >> > https://github.com/yorabl/Openstack-Ceph >> >> > >> >> > Good luck, >> >> > Yogev Rabl >> >> > Quality Engineer, >> >> > RHOS storage >> >> > Red Hat >> >> > >> >> >> ----- Forwarded Message ----- >> >> >> From: "Walter Valenti" > >> >> >> To: rdo-list at redhat.com >> >> >> Sent: Thursday, January 15, 2015 1:04:58 PM >> >> >> Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> >> >> >> >> Hi, >> >> >> we're trying Juno with Ceph (Giant) integration on > Centos7.RBDDriver -1.1.0 (config name rbd) driver is uninitialized > >> >> >> >> >> >> The problem is that Cinder-Volume ignores, the > directives >> >> >> for use rbd protocol, but every uses LVM. >> >> >> >> >> >> This is our rbd configuration in cinder.conf: >> >> >> >> >> >> [DEFAULT] >> >> >> >> >> >> volume_driver=cinder.volume.drivers.rbd.RBDDriver >> >> >> [rbd] >> >> >> rbd_pool=volumes >> >> >> rbd_user=cinder >> >> >> rbd_ceph_conf=etc/ceph/ceph.conf >> >> >> rbd_flatten_volume_from_snapshot=false >> >> >> rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471 >> >> >> rbd_max_clone_depth=5 >> >> >> rbd_store_chunk_size=4 >> >> >> rados_connect_timeout=-1 >> >> >> >> >> >> We also tried with all configuration in "rdb" > section, >> > and >> >> >> with all configuration in DEFAULT section, but the > problem is the >> > same. >> >> >> >> >> >> >> >> >> Any ideas?? >> >> >> >> >> >> Thanks >> >> >> Walter >> >> >> >> >> >> _______________________________________________ >> >> >> Rdo-list mailing list >> >> >> Rdo-list at redhat.com >> >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> >> >> > >> >> >> > >> > From docana at ebi.ac.uk Thu Jan 15 16:44:17 2015 From: docana at ebi.ac.uk (David Ocana) Date: Thu, 15 Jan 2015 16:44:17 +0000 Subject: [Rdo-list] Can't delete network from neutron In-Reply-To: References: <54B7DED8.7000700@ebi.ac.uk> Message-ID: <54B7EE61.9000104@ebi.ac.uk> Hi Rushi, Thanks for the quick reply. Actually the router was removed before trying to delete the subnet , and I tried removing it all first from the UI but as I coudln't, I started using the neutron commands. I think there is still some trace of the relationship between the port and the router and that may be the reason why I can't delete it, but that's my guess # neutron port-show e5d4effb-6a67-4f90-ad2c-01dca00c9e42 +-----------------------+------------------------------------------------------------------------------------+ | Field | Value | +-----------------------+------------------------------------------------------------------------------------+ | admin_state_up | False | | allowed_address_pairs | | | binding:host_id | intcl01-hyp02.ebi.ac.uk | | binding:profile | {} | | binding:vif_details | {"port_filter": true, "ovs_hybrid_plug": true} | | binding:vif_type | ovs | | binding:vnic_type | normal | | device_id | e5057310-02a0-447c-ab77-4528e821cd84 | | device_owner | network:router_interface | (this one here) | extra_dhcp_opts | | | fixed_ips | {"subnet_id": "329476b1-7ea7-41e5-a357-445b143086fe", "ip_address": "192.168.1.1"} | | id | e5d4effb-6a67-4f90-ad2c-01dca00c9e42 | | mac_address | fa:16:3e:ff:ee:1d | | name | to_delete | | network_id | 9a427447-3f9f-4dc5-94f8-bc273a7e7cf0 | | security_groups | | | status | DOWN | | tenant_id | beea649440944f8ab232c0f8cf84d54d | +-----------------------+------------------------------------------------------------------------------------+ Cheers, David On 15/01/15 15:51, Ns, Rushi wrote: > You need remove router and interface then remove subnet as well others, you can do all these on dashboard with user admin, please remove router first . Let me know. > > BR, > Rushi > Sent from my iPhone > please excuse typos and brevity > >> On Jan 15, 2015, at 7:42 AM, David Ocana wrote: >> >> Hi everyone, >> >> I installed juno rdo and I was playing with it until I got stuck trying to delete a private network. I have been googling around I found possible reasons but none of the solutions worked for me. >> >> Here is what I did: >> >> # neutron net-delete 9a427447-3f9f-4dc5-94f8-bc273a7e7cf0 >> Conflict (HTTP 409) (Request-ID: req-d1c79aaa-25f4-40cf-91c4-fde63d54708a) >> >> So I thought I had to delete the subnet first: >> >> # neutron subnet-delete 329476b1-7ea7-41e5-a357-445b143086fe >> Conflict (HTTP 409) (Request-ID: req-7ff81f34-10ee-4eb1-b3f0-ebbc7283af4e) >> >> Then I checked if there were any ports for this subnet: >> >> # neutron port-list | grep 329 >> | e5d4effb-6a67-4f90-ad2c-01dca00c9e42 | | fa:16:3e:ff:ee:1d | {"subnet_id": "329476b1-7ea7-41e5-a357-445b143086fe", "ip_address": "192.168.1.1"} | >> >> Then I tried to delete the port but I get the same: >> >> # neutron port-delete e5d4effb-6a67-4f90-ad2c-01dca00c9e42 >> Conflict (HTTP 409) (Request-ID: req-6e8789f4-cd92-46fb-9ff4-db14faeb6503) >> >> I tried disabling the port first but it didn't work either. Tenant is brand new, has no instances, no volumes, nothing besides the network. >> >> Any ideas? >> >> Thanks, >> David >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list From rbowen at redhat.com Thu Jan 15 21:23:45 2015 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 15 Jan 2015 16:23:45 -0500 Subject: [Rdo-list] CentOS Cloud SIG meeting minutes Message-ID: <54B82FE1.5010505@redhat.com> The minutes from the CentOS Cloud SIG meeting are here: http://lists.centos.org/pipermail/centos-devel/2015-January/012630.html The full transcript is at http://www.centos.org/minutes/2015/january/centos-devel.2015-01-15-15.02.log.html This meeting, which discusses various cloud infrastructure projects, including OpenStack, in CentOS, is held each Thursday at 15:00 UTC, on the #centos-devel channel on Freenode IRC. If you're interested in packaging RDO on CentOS, you should try to attend. This is in addition to the RDO packaging meeting mentioned earlier, because it covers the larger cloud ecosystem, including Eucalyptus, and possibly other projects in the future. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From dpkshetty at gmail.com Fri Jan 16 06:24:04 2015 From: dpkshetty at gmail.com (Deepak Shetty) Date: Fri, 16 Jan 2015 11:54:04 +0530 Subject: [Rdo-list] [Manila] Unable to start Manila scheduler [ was: Don't see python-manilaclient package] Message-ID: Thanks Alan, I was able to pick & install the manilaclient packages from the copr link. Going ahead, i was able to start the manila-api service but manila-scheduler and manila-share service errored out *First things first, looks like m-sch errored due as the manila DB is not present.* *Who/Which package is responsible for creating the manila db and its associated tables in the mysql ?* Pls see the debug info below taken from my setup: [root at rhsdev1 packstack(keystone_admin)]# systemctl start openstack-manila-scheduler.service [root at rhsdev1 packstack(keystone_admin)]# systemctl status openstack-manila-scheduler.service openstack-manila-scheduler.service - OpenStack Manila Scheduler Loaded: loaded (/usr/lib/systemd/system/openstack-manila-scheduler.service; enabled) Active: failed (Result: exit-code) since Fri 2015-01-16 11:39:15 IST; 20s ago Process: 8302 ExecStart=/usr/bin/manila-scheduler --config-file /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf --logfile /var/log/manila/scheduler.log (code=exited, status=1/FAILURE) Main PID: 8302 (code=exited, status=1/FAILURE) CGroup: /system.slice/openstack-manila-scheduler.service Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 199, in raise_from_cause Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila reraise(type(exception), exception, tb=exc_tb) Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 951, in _execute_context Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila context) Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 436, in do_execute Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila cursor.execute(statement, parameters) Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila OperationalError: (OperationalError) no such table: services u'SELECT services.created_at AS services_creat...d, services.id Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: 2015-01-16 11:39:15.531 8302 TRACE manila Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com systemd[1]: openstack-manila-scheduler.service: main process exited, code=exited, status=1/FAILURE Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit openstack-manila-scheduler.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. MariaDB [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | cinder | | glance | | keystone | | mysql | | neutron | | nova | | performance_schema | | test | +--------------------+ 9 rows in set (0.00 sec) MariaDB [(none)]> ================================================== On a related note: there were some warnings & errors from the -api and -share service respectively (i guess these can be handled once the DB issue is resolved?) [root at rhsdev1 packstack(keystone_admin)]# systemctl status openstack-manila-api.service openstack-manila-api.service - OpenStack Manila API Server Loaded: loaded (/usr/lib/systemd/system/openstack-manila-api.service; disabled) Active: active (running) since Fri 2015-01-16 11:36:54 IST; 32s ago Main PID: 8075 (manila-api) CGroup: /system.slice/openstack-manila-api.service ??8075 /usr/bin/python2 /usr/bin/manila-api --config-file /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf --logfile /var/log/manila/api.log Jan 16 11:36:54 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Started OpenStack Manila API Server. Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token [-] This middleware module is deprecated as of v0.10.0 in favor of keystonemiddl...leware package. Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead. Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token [-] Configuring auth_uri to point to the public identity endpoint is required; c... admin endpoint Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: 2015-01-16 11:36:55.325 8075 WARNING keystoneclient.middleware.auth_token [-] signing_dir mode is 0755 instead of 0700 Hint: Some lines were ellipsized, use -l to show in full. [root at rhsdev1 packstack(keystone_admin)]# systemctl status openstack-manila-share.service openstack-manila-share.service - OpenStack Manila Share Service Loaded: loaded (/usr/lib/systemd/system/openstack-manila-share.service; enabled) Active: failed (Result: exit-code) since Fri 2015-01-16 11:39:20 IST; 50s ago Process: 8317 ExecStart=/usr/bin/manila-share --config-file /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf --logfile /var/log/manila/share.log (code=exited, status=1/FAILURE) Main PID: 8317 (code=exited, status=1/FAILURE) Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila File "/usr/lib/python2.7/site-packages/manila/openstack/common/importutils.py", line 38, in import_object Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila return import_class(import_str)(*args, **kwargs) Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila File "/usr/lib/python2.7/site-packages/manila/share/drivers/generic.py", line 116, in *init* Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila self.db, driver_config=self.configuration)) Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila File "/usr/lib/python2.7/site-packages/manila/share/drivers/service_instance.py", line 133, in *init* Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila raise exception.ServiceInstanceException(_('Service instance user ' Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila ServiceInstanceException: Service instance user is not specified Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: 2015-01-16 11:39:20.248 8317 TRACE manila Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com systemd[1]: openstack-manila-share.service: main process exited, code=exited, status=1/FAILURE Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit openstack-manila-share.service entered failed state. thanx, deepak On Tue, Jan 13, 2015 at 5:07 PM, Alan Pevec wrote: > > I am new to RDO, any idea when would that next refresh be ? > > There aren't scheduled refreshes, we push updates when they pass > rdopkg CI update process [1]. > This is currently running on internal RHT systems and we're working on > opening it up for external contributors, tasks are tracked on a public > board [2] > Haikel's manilaclient has passed Phase1 and Phase2 will run today on > queued updates. > I'll update this thread when updates hit the public repo. In the > meantime, you can grab the el7 package from Copr [3] > > > Cheers, > Alan > > > [1] http://apevec.github.io/rdo-intro.html#8 > [2] https://trello.com/b/HhXlqdiu/rdo > [3] > https://copr-be.cloud.fedoraproject.org/results/jruzicka/rdo-juno-epel-7/epel-7-x86_64/python-manilaclient-1.0.1-3.el7/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dpkshetty at gmail.com Fri Jan 16 08:38:33 2015 From: dpkshetty at gmail.com (Deepak Shetty) Date: Fri, 16 Jan 2015 14:08:33 +0530 Subject: [Rdo-list] [Manila] Unable to start Manila scheduler [ was: Don't see python-manilaclient package] In-Reply-To: References: Message-ID: Dumping some more stuff that I tried to do for creating a new DB.. but all of the below failed. [root at rhsdev1 packstack(keystone_admin)]# manila-manage db sync [root at rhsdev1 packstack(keystone_admin)]# mysql -u root Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 157546 Server version: 5.5.40-MariaDB-wsrep MariaDB Server, wsrep_25.11.r4026 Copyright (c) 2000, 2014, Oracle, Monty Program Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | cinder | | glance | | keystone | | mysql | | neutron | | nova | | performance_schema | | test | +--------------------+ 9 rows in set (0.00 sec) MariaDB [(none)]> Bye [root at rhsdev1 packstack(keystone_admin)]# openstack-db --service manila --init Unrecognized --service manila Please specify nova|glance|keystone|cinder|heat|neutron|trove [root at rhsdev1 packstack(keystone_admin)]# On Fri, Jan 16, 2015 at 11:54 AM, Deepak Shetty wrote: > Thanks Alan, I was able to pick & install the manilaclient packages from > the copr link. > > Going ahead, i was able to start the manila-api service but > manila-scheduler and manila-share service errored out > > *First things first, looks like m-sch errored due as the manila DB is not > present.* > *Who/Which package is responsible for creating the manila db and its > associated tables in the mysql ?* > > Pls see the debug info below taken from my setup: > > [root at rhsdev1 packstack(keystone_admin)]# systemctl start > openstack-manila-scheduler.service > > [root at rhsdev1 packstack(keystone_admin)]# systemctl status > openstack-manila-scheduler.service > openstack-manila-scheduler.service - OpenStack Manila Scheduler > Loaded: loaded > (/usr/lib/systemd/system/openstack-manila-scheduler.service; enabled) > Active: failed (Result: exit-code) since Fri 2015-01-16 11:39:15 IST; 20s > ago > Process: 8302 ExecStart=/usr/bin/manila-scheduler --config-file > /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf > --logfile /var/log/manila/scheduler.log (code=exited, status=1/FAILURE) > Main PID: 8302 (code=exited, status=1/FAILURE) > CGroup: /system.slice/openstack-manila-scheduler.service > > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila File > "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 199, > in raise_from_cause > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila reraise(type(exception), > exception, tb=exc_tb) > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila File > "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 951, > in _execute_context > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila context) > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila File > "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line > 436, in do_execute > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila cursor.execute(statement, > parameters) > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila OperationalError: > (OperationalError) no such table: services u'SELECT services.created_at AS > services_creat...d, services.id > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com manila-scheduler[8302]: > 2015-01-16 11:39:15.531 8302 TRACE manila > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com systemd[1]: > openstack-manila-scheduler.service: main process exited, code=exited, > status=1/FAILURE > Jan 16 11:39:15 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit > openstack-manila-scheduler.service entered failed state. > Hint: Some lines were ellipsized, use -l to show in full. > MariaDB [(none)]> show databases; > +--------------------+ > | Database | > +--------------------+ > | information_schema | > | cinder | > | glance | > | keystone | > | mysql | > | neutron | > | nova | > | performance_schema | > | test | > +--------------------+ > 9 rows in set (0.00 sec) > > MariaDB [(none)]> > > > ================================================== > > On a related note: there were some warnings & errors from the -api and > -share service respectively (i guess these can be handled once the DB issue > is resolved?) > > [root at rhsdev1 packstack(keystone_admin)]# systemctl status > openstack-manila-api.service > openstack-manila-api.service - OpenStack Manila API Server > Loaded: loaded (/usr/lib/systemd/system/openstack-manila-api.service; > disabled) > Active: active (running) since Fri 2015-01-16 11:36:54 IST; 32s ago > Main PID: 8075 (manila-api) > CGroup: /system.slice/openstack-manila-api.service > ??8075 /usr/bin/python2 /usr/bin/manila-api --config-file > /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf > --logfile /var/log/manila/api.log > > Jan 16 11:36:54 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Started > OpenStack Manila API Server. > Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: > 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token > [-] This middleware module is deprecated as of v0.10.0 in favor of > keystonemiddl...leware package. > Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: > 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token > [-] Configuring admin URI using auth fragments. This is deprecated, use > 'identity_uri' instead. > Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: > 2015-01-16 11:36:55.324 8075 WARNING keystoneclient.middleware.auth_token > [-] Configuring auth_uri to point to the public identity endpoint is > required; c... admin endpoint > Jan 16 11:36:55 rhsdev1.lab.eng.blr.redhat.com manila-api[8075]: > 2015-01-16 11:36:55.325 8075 WARNING keystoneclient.middleware.auth_token > [-] signing_dir mode is 0755 instead of 0700 > Hint: Some lines were ellipsized, use -l to show in full. > > [root at rhsdev1 packstack(keystone_admin)]# systemctl status > openstack-manila-share.service > openstack-manila-share.service - OpenStack Manila Share Service > Loaded: loaded (/usr/lib/systemd/system/openstack-manila-share.service; > enabled) > Active: failed (Result: exit-code) since Fri 2015-01-16 11:39:20 IST; 50s > ago > Process: 8317 ExecStart=/usr/bin/manila-share --config-file > /usr/share/manila/manila-dist.conf --config-file /etc/manila/manila.conf > --logfile /var/log/manila/share.log (code=exited, status=1/FAILURE) > Main PID: 8317 (code=exited, status=1/FAILURE) > > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila File > "/usr/lib/python2.7/site-packages/manila/openstack/common/importutils.py", > line 38, in import_object > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila return > import_class(import_str)(*args, **kwargs) > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila File > "/usr/lib/python2.7/site-packages/manila/share/drivers/generic.py", line > 116, in *init* > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila self.db, > driver_config=self.configuration)) > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila File > "/usr/lib/python2.7/site-packages/manila/share/drivers/service_instance.py", > line 133, in *init* > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila raise > exception.ServiceInstanceException(_('Service instance user ' > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila ServiceInstanceException: Service > instance user is not specified > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com manila-share[8317]: > 2015-01-16 11:39:20.248 8317 TRACE manila > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com systemd[1]: > openstack-manila-share.service: main process exited, code=exited, > status=1/FAILURE > Jan 16 11:39:20 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit > openstack-manila-share.service entered failed state. > > thanx, > deepak > > > > > On Tue, Jan 13, 2015 at 5:07 PM, Alan Pevec wrote: > >> > I am new to RDO, any idea when would that next refresh be ? >> >> There aren't scheduled refreshes, we push updates when they pass >> rdopkg CI update process [1]. >> This is currently running on internal RHT systems and we're working on >> opening it up for external contributors, tasks are tracked on a public >> board [2] >> Haikel's manilaclient has passed Phase1 and Phase2 will run today on >> queued updates. >> I'll update this thread when updates hit the public repo. In the >> meantime, you can grab the el7 package from Copr [3] >> >> >> Cheers, >> Alan >> >> >> [1] http://apevec.github.io/rdo-intro.html#8 >> [2] https://trello.com/b/HhXlqdiu/rdo >> [3] >> https://copr-be.cloud.fedoraproject.org/results/jruzicka/rdo-juno-epel-7/epel-7-x86_64/python-manilaclient-1.0.1-3.el7/ >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From waltervalenti at yahoo.it Fri Jan 16 10:59:44 2015 From: waltervalenti at yahoo.it (Walter Valenti) Date: Fri, 16 Jan 2015 10:59:44 +0000 (UTC) Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph In-Reply-To: <41020A578D080940B8D09FB06F63EC862409209D@S00EXC001.ormuco.lcl> References: <41020A578D080940B8D09FB06F63EC862409209D@S00EXC001.ormuco.lcl> Message-ID: <1258727837.2177727.1421405984284.JavaMail.yahoo@jws11108.mail.ir2.yahoo.com> I've tried to compile it, the same version of Centos7 package: 1.5.3 but there's a problem: qumu 1.5.3 requires glib-2.12, but on Centos7 there's 2.36.3 Which version of qemu are you compiled? Thanks Walter ----- Messaggio originale ----- > Da: Pascal Bernier > A: Walter Valenti > Cc: > Inviato: Gioved? 15 Gennaio 2015 18:05 > Oggetto: RE: [Rdo-list] Problem with Cinder (Juno) and Ceph > > Hi Walter, > > I faced the same issue. The maintainers of the package for CentOS didn't > compiled it with rbd support. I recompiled it with the rbd option and it was > working propery. You also need to use the CentOSPlus repo for rbd kernel > support. > > > Pascal Bernier > > ________________________________________ > > From: rdo-list-bounces at redhat.com [rdo-list-bounces at redhat.com] on behalf of > Walter Valenti [waltervalenti at yahoo.it] > Sent: Thursday, January 15, 2015 11:29 AM > To: Yogev Rabl > Cc: rdo-list at redhat.com > Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph > > I've followed directly the ceph documentation. > Reading the RDO documentation, at point 4 of > "Install Virtualization for Ceph Block Devices" tells: > Older releases of RHEL and CentOS don't provide the rbd format required for > use with Ceph. > Now, I think: Centos7 isn't a older release. > But the execution of "qemu-img -f", give me: > vvfat vpc vmdk vhdx vdi sheepdog sheepdog sheepdog raw host_cdrom host_floppy > host_device file qed qcow2 qcow parallels nbd nbd nbd iscsi gluster gluster > gluster gluster dmg cow cloop bochs blkverify blkdebug > There isn't "rdb".... Why ???? > > Walter > > > > > > > > ----- Messaggio originale ----- >> Da: Yogev Rabl >> A: Walter Valenti >> Cc: rdo-list at redhat.com >> Inviato: Gioved? 15 Gennaio 2015 16:53 >> Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> Did you go through 4th point in section, Install Virtualization for Ceph > Block >> Devices, in this manual: >> https://openstack.redhat.com/Using_Ceph_for_block_storage_with_RDO ? >> >> Yogev >> >> ----- Original Message ----- >>> From: "Walter Valenti" >>> To: "Yogev Rabl" >>> Cc: rdo-list at redhat.com >>> Sent: Thursday, January 15, 2015 5:42:03 PM >>> Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >>> >>> >>> >>> Yes, I've installed. >>> >>> >>> >>> >>> >>> ----- Messaggio originale ----- >>> > Da: Yogev Rabl >>> > A: Walter Valenti >>> > Cc: >>> > Inviato: Gioved? 15 Gennaio 2015 16:30 >>> > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >>> > >>> > did you install ceph-common & python-ceph? >>> > >>> > >>> > ----- Original Message ----- >>> >> From: "Walter Valenti" > >>> >> To: "Yogev Rabl" >>> >> Sent: Thursday, January 15, 2015 5:08:51 PM >>> >> Subject: Re: Fwd: [Rdo-list] Problem with Cinder (Juno) and > Ceph >>> >> >>> >> Yes, with enabled_backends = rbd, >>> >> Cinder-Volume tries to use Ceph, but now I've >>> >> got the following error: >>> >> >>> >> WARNING cinder.volume.manager [-] Unable to update volume >> replication >>> > status, >>> >> RBDDriver -1.1.0 (config name rbd) driver is uninitialized. >>> >> >>> >> >>> >> >>> >> Walter >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> ----- Messaggio originale ----- >>> >> > Da: Yogev Rabl >>> >> > A: waltervalenti at yahoo.itYe >>> >> > Cc: >>> >> > Inviato: Gioved? 15 Gennaio 2015 14:18 >>> >> > Oggetto: Fwd: [Rdo-list] Problem with Cinder (Juno) and > Ceph >>> >> > >>> >> > Hi Walter, >>> >> > >>> >> > You this configuration is incorrect from what I know. >>> >> > >>> >> > try this: >>> >> > >>> >> > [DEFAULT] >>> >> > >>> >> > enabled_backends = rbd >>> >> > >>> >> > [rbd] >>> >> > volume_driver=cinder.volume.drivers.rbd.RBDDriver >>> >> > rbd_pool=volumes >>> >> > rbd_ceph_conf=etc/ceph/ceph.conf >>> >> > rbd_flatten_volume_from_snapshot=false >>> >> > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf747 >>> >> > rbd_max_clone_depth=5 >>> >> > rbd_store_chunk_size=4 >>> >> > rados_connect_timeout=-1 >>> >> > >>> >> > >>> >> > In addition, I've just finish to write a small tool > in >> python that >>> >> > configures Ceph in Openstack components configuration > files >> (and set >>> > the >>> >> > pools + >>> >> > keyrings in the Ceph server). >>> >> > You can have a look at it in github: >>> >> > https://github.com/yorabl/Openstack-Ceph >>> >> > >>> >> > Good luck, >>> >> > Yogev Rabl >>> >> > Quality Engineer, >>> >> > RHOS storage >>> >> > Red Hat >>> >> > >>> >> >> ----- Forwarded Message ----- >>> >> >> From: "Walter Valenti" >> >>> >> >> To: rdo-list at redhat.com >>> >> >> Sent: Thursday, January 15, 2015 1:04:58 PM >>> >> >> Subject: [Rdo-list] Problem with Cinder (Juno) and > Ceph >>> >> >> >>> >> >> Hi, >>> >> >> we're trying Juno with Ceph (Giant) > integration on >> Centos7.RBDDriver -1.1.0 (config name rbd) driver is uninitialized >> >>> >> >> >>> >> >> The problem is that Cinder-Volume ignores, the >> directives >>> >> >> for use rbd protocol, but every uses LVM. >>> >> >> >>> >> >> This is our rbd configuration in cinder.conf: >>> >> >> >>> >> >> [DEFAULT] >>> >> >> >>> >> >> volume_driver=cinder.volume.drivers.rbd.RBDDriver >>> >> >> [rbd] >>> >> >> rbd_pool=volumes >>> >> >> rbd_user=cinder >>> >> >> rbd_ceph_conf=etc/ceph/ceph.conf >>> >> >> rbd_flatten_volume_from_snapshot=false >>> >> >> > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471 >>> >> >> rbd_max_clone_depth=5 >>> >> >> rbd_store_chunk_size=4 >>> >> >> rados_connect_timeout=-1 >>> >> >> >>> >> >> We also tried with all configuration in > "rdb" >> section, >>> > and >>> >> >> with all configuration in DEFAULT section, but the >> problem is the >>> > same. >>> >> >> >>> >> >> >>> >> >> Any ideas?? >>> >> >> >>> >> >> Thanks >>> >> >> Walter >>> >> >> >>> >> >> _______________________________________________ >>> >> >> Rdo-list mailing list >>> >> >> Rdo-list at redhat.com >>> >> >> https://www.redhat.com/mailman/listinfo/rdo-list >>> >> >> >>> >> > >>> >> >>> > >>> >> > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From waltervalenti at yahoo.it Fri Jan 16 13:42:06 2015 From: waltervalenti at yahoo.it (Walter Valenti) Date: Fri, 16 Jan 2015 13:42:06 +0000 (UTC) Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph In-Reply-To: <1258727837.2177727.1421405984284.JavaMail.yahoo@jws11108.mail.ir2.yahoo.com> References: <1258727837.2177727.1421405984284.JavaMail.yahoo@jws11108.mail.ir2.yahoo.com> Message-ID: <328192309.2284627.1421415726528.JavaMail.yahoo@jws11105.mail.ir2.yahoo.com> I was wrong: On centos7 glib-1.2.10 not 2.36.3 Walter ----- Messaggio originale ----- > Da: Walter Valenti > A: Pascal Bernier > Cc: "rdo-list at redhat.com" > Inviato: Venerd? 16 Gennaio 2015 11:59 > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph > > I've tried to compile it, the same version of > Centos7 package: 1.5.3 > > but there's a problem: > > qumu 1.5.3 requires glib-2.12, but on Centos7 > there's 2.36.3 > Which version of qemu are you compiled? > > > > > Thanks > Walter > > > > > > ----- Messaggio originale ----- >> Da: Pascal Bernier >> A: Walter Valenti >> Cc: >> Inviato: Gioved? 15 Gennaio 2015 18:05 >> Oggetto: RE: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> Hi Walter, >> >> I faced the same issue. The maintainers of the package for CentOS > didn't >> compiled it with rbd support. I recompiled it with the rbd option and it > was >> working propery. You also need to use the CentOSPlus repo for rbd kernel >> support. >> >> >> Pascal Bernier >> >> ________________________________________ >> >> From: rdo-list-bounces at redhat.com [rdo-list-bounces at redhat.com] on behalf > of >> Walter Valenti [waltervalenti at yahoo.it] >> Sent: Thursday, January 15, 2015 11:29 AM >> To: Yogev Rabl >> Cc: rdo-list at redhat.com >> Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >> >> I've followed directly the ceph documentation. >> Reading the RDO documentation, at point 4 of >> "Install Virtualization for Ceph Block Devices" tells: >> Older releases of RHEL and CentOS don't provide the rbd format required > for >> use with Ceph. >> Now, I think: Centos7 isn't a older release. >> But the execution of "qemu-img -f", give me: >> vvfat vpc vmdk vhdx vdi sheepdog sheepdog sheepdog raw host_cdrom > host_floppy >> host_device file qed qcow2 qcow parallels nbd nbd nbd iscsi gluster gluster > >> gluster gluster dmg cow cloop bochs blkverify blkdebug >> There isn't "rdb".... Why ???? >> >> Walter >> >> >> >> >> >> >> >> ----- Messaggio originale ----- >>> Da: Yogev Rabl >>> A: Walter Valenti >>> Cc: rdo-list at redhat.com >>> Inviato: Gioved? 15 Gennaio 2015 16:53 >>> Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >>> >>> Did you go through 4th point in section, Install Virtualization for > Ceph >> Block >>> Devices, in this manual: >>> https://openstack.redhat.com/Using_Ceph_for_block_storage_with_RDO ? >>> >>> Yogev >>> >>> ----- Original Message ----- >>>> From: "Walter Valenti" >>>> To: "Yogev Rabl" >>>> Cc: rdo-list at redhat.com >>>> Sent: Thursday, January 15, 2015 5:42:03 PM >>>> Subject: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >>>> >>>> >>>> >>>> Yes, I've installed. >>>> >>>> >>>> >>>> >>>> >>>> ----- Messaggio originale ----- >>>> > Da: Yogev Rabl >>>> > A: Walter Valenti >>>> > Cc: >>>> > Inviato: Gioved? 15 Gennaio 2015 16:30 >>>> > Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph >>>> > >>>> > did you install ceph-common & python-ceph? >>>> > >>>> > >>>> > ----- Original Message ----- >>>> >> From: "Walter Valenti" >> >>>> >> To: "Yogev Rabl" >>>> >> Sent: Thursday, January 15, 2015 5:08:51 PM >>>> >> Subject: Re: Fwd: [Rdo-list] Problem with Cinder (Juno) > and >> Ceph >>>> >> >>>> >> Yes, with enabled_backends = rbd, >>>> >> Cinder-Volume tries to use Ceph, but now I've >>>> >> got the following error: >>>> >> >>>> >> WARNING cinder.volume.manager [-] Unable to update > volume >>> replication >>>> > status, >>>> >> RBDDriver -1.1.0 (config name rbd) driver is > uninitialized. >>>> >> >>>> >> >>>> >> >>>> >> Walter >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> ----- Messaggio originale ----- >>>> >> > Da: Yogev Rabl >>>> >> > A: waltervalenti at yahoo.itYe >>>> >> > Cc: >>>> >> > Inviato: Gioved? 15 Gennaio 2015 14:18 >>>> >> > Oggetto: Fwd: [Rdo-list] Problem with Cinder > (Juno) and >> Ceph >>>> >> > >>>> >> > Hi Walter, >>>> >> > >>>> >> > You this configuration is incorrect from what I > know. >>>> >> > >>>> >> > try this: >>>> >> > >>>> >> > [DEFAULT] >>>> >> > >>>> >> > enabled_backends = rbd >>>> >> > >>>> >> > [rbd] >>>> >> > volume_driver=cinder.volume.drivers.rbd.RBDDriver >>>> >> > rbd_pool=volumes >>>> >> > rbd_ceph_conf=etc/ceph/ceph.conf >>>> >> > rbd_flatten_volume_from_snapshot=false >>>> >> > > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf747 >>>> >> > rbd_max_clone_depth=5 >>>> >> > rbd_store_chunk_size=4 >>>> >> > rados_connect_timeout=-1 >>>> >> > >>>> >> > >>>> >> > In addition, I've just finish to write a small > tool >> in >>> python that >>>> >> > configures Ceph in Openstack components > configuration >> files >>> (and set >>>> > the >>>> >> > pools + >>>> >> > keyrings in the Ceph server). >>>> >> > You can have a look at it in github: >>>> >> > https://github.com/yorabl/Openstack-Ceph >>>> >> > >>>> >> > Good luck, >>>> >> > Yogev Rabl >>>> >> > Quality Engineer, >>>> >> > RHOS storage >>>> >> > Red Hat >>>> >> > >>>> >> >> ----- Forwarded Message ----- >>>> >> >> From: "Walter Valenti" >>> >>>> >> >> To: rdo-list at redhat.com >>>> >> >> Sent: Thursday, January 15, 2015 1:04:58 PM >>>> >> >> Subject: [Rdo-list] Problem with Cinder > (Juno) and >> Ceph >>>> >> >> >>>> >> >> Hi, >>>> >> >> we're trying Juno with Ceph (Giant) >> integration on >>> Centos7.RBDDriver -1.1.0 (config name rbd) driver is uninitialized >>> >>>> >> >> >>>> >> >> The problem is that Cinder-Volume ignores, > the >>> directives >>>> >> >> for use rbd protocol, but every uses LVM. >>>> >> >> >>>> >> >> This is our rbd configuration in cinder.conf: >>>> >> >> >>>> >> >> [DEFAULT] >>>> >> >> >>>> >> >> > volume_driver=cinder.volume.drivers.rbd.RBDDriver >>>> >> >> [rbd] >>>> >> >> rbd_pool=volumes >>>> >> >> rbd_user=cinder >>>> >> >> rbd_ceph_conf=etc/ceph/ceph.conf >>>> >> >> rbd_flatten_volume_from_snapshot=false >>>> >> >> >> rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471 >>>> >> >> rbd_max_clone_depth=5 >>>> >> >> rbd_store_chunk_size=4 >>>> >> >> rados_connect_timeout=-1 >>>> >> >> >>>> >> >> We also tried with all configuration in >> "rdb" >>> section, >>>> > and >>>> >> >> with all configuration in DEFAULT section, > but the >>> problem is the >>>> > same. >>>> >> >> >>>> >> >> >>>> >> >> Any ideas?? >>>> >> >> >>>> >> >> Thanks >>>> >> >> Walter >>>> >> >> >>>> >> >> > _______________________________________________ >>>> >> >> Rdo-list mailing list >>>> >> >> Rdo-list at redhat.com >>>> >> >> > https://www.redhat.com/mailman/listinfo/rdo-list > >>>> >> >> >>>> >> > >>>> >> >>>> > >>>> >>> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From bderzhavets at hotmail.com Sat Jan 17 08:19:47 2015 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Sat, 17 Jan 2015 03:19:47 -0500 Subject: [Rdo-list] Failure to resume instance on RDO Juno TwoNode F21 Cluster In-Reply-To: <9E8EE5E176B2BD49913B2F69B369AD8302136BD803@MX02A.corp.emc.com> References: <9E8EE5E176B2BD49913B2F69B369AD8302136BD803@MX02A.corp.emc.com> Message-ID: Attempting to resume instance via dashboard on Controller&&Network Node (ML2&OVS&VXLAN setup) I get Server code 1006 on VNC console. On Compute Node :- [root at juno2f21 ~]# service libvirtd status Redirecting to /bin/systemctl status libvirtd.service ? libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Sat 2015-01-17 09:51:01 MSK; 24min ago Docs: man:libvirtd(8) http://libvirt.org Main PID: 1035 (libvirtd) CGroup: /system.slice/libvirtd.service ??1035 /usr/sbin/libvirtd --listen Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: libvirt version: 1.2.9.1, package: 2.fc...g) Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: Unable to read from monitor: Connection...er Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: internal error: early end of file from ...m: qemu-system-x86_64: /builddir/build/BUI...d. Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: error from service: TerminateMachine: N...wn Hint: Some lines were ellipsized, use -l to show in full. Workaround :- Hard reboot Bug has been reproduced twice ( two different installations ) Thanks Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Sat Jan 17 09:15:04 2015 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Sat, 17 Jan 2015 04:15:04 -0500 Subject: [Rdo-list] The most recent `yum update` on CentOS 7 crash httpd Service In-Reply-To: References: <9E8EE5E176B2BD49913B2F69B369AD8302136BD803@MX02A.corp.emc.com>, Message-ID: [root at juno2 ~]# /usr/sbin/httpd -D FOREGROUND AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/httpd/conf/ports.conf:7 AH00526: Syntax error on line 18 of /etc/httpd/conf.d/ssl.conf: Invalid command 'SSLPassPhraseDialog', perhaps misspelled or defined by a module not included in the server configuration [root at juno2 ~]# rpm -qa | grep http rubygem-net-http-persistent-2.8-5.el7.noarch httpd-2.4.6-19.el7.centos.x86_64 httpd-tools-2.4.6-19.el7.centos.x86_64 python-httplib2-0.7.7-3.el7.noarch libmicrohttpd-0.9.33-2.el7.x86_64 httpd-manual-2.4.6-19.el7.centos.noarch Thanks Boris -------------- next part -------------- An HTML attachment was scrubbed... URL: From nux at li.nux.ro Sat Jan 17 19:42:39 2015 From: nux at li.nux.ro (Nux!) Date: Sat, 17 Jan 2015 19:42:39 +0000 (GMT) Subject: [Rdo-list] "Manual" installation of Juno Message-ID: <660433606.26416.1421523759309.JavaMail.zimbra@li.nux.ro> Hi guys, I'm looking to install Openstack Juno from the RDO RPMs, but without packstack/puppet/foreman. Are there any "usable" docs for this? Cheers, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro From marius at remote-lab.net Sat Jan 17 20:02:47 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 17 Jan 2015 21:02:47 +0100 Subject: [Rdo-list] "Manual" installation of Juno In-Reply-To: <660433606.26416.1421523759309.JavaMail.zimbra@li.nux.ro> References: <660433606.26416.1421523759309.JavaMail.zimbra@li.nux.ro> Message-ID: Hi Lucian, You can check the upstream documentation. It's pretty good if you want to install the components manually: http://docs.openstack.org/juno/install-guide/install/yum/content/ On Sat, Jan 17, 2015 at 8:42 PM, Nux! wrote: > Hi guys, > > I'm looking to install Openstack Juno from the RDO RPMs, but without > packstack/puppet/foreman. > Are there any "usable" docs for this? > > Cheers, > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nux at li.nux.ro Sat Jan 17 22:04:44 2015 From: nux at li.nux.ro (Nux!) Date: Sat, 17 Jan 2015 22:04:44 +0000 (GMT) Subject: [Rdo-list] "Manual" installation of Juno In-Reply-To: References: <660433606.26416.1421523759309.JavaMail.zimbra@li.nux.ro> Message-ID: <2010250668.26459.1421532284396.JavaMail.zimbra@li.nux.ro> Hi Marius, Thanks, I'll give that a go. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Marius Cornea" > To: "Nux!" > Cc: "rdo-list" > Sent: Saturday, 17 January, 2015 20:02:47 > Subject: Re: [Rdo-list] "Manual" installation of Juno > Hi Lucian, > > You can check the upstream documentation. It's pretty good if you want to > install the components manually: > > http://docs.openstack.org/juno/install-guide/install/yum/content/ > > On Sat, Jan 17, 2015 at 8:42 PM, Nux! wrote: > >> Hi guys, >> >> I'm looking to install Openstack Juno from the RDO RPMs, but without >> packstack/puppet/foreman. >> Are there any "usable" docs for this? >> >> Cheers, >> Lucian >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list From kchamart at redhat.com Sun Jan 18 12:28:00 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Sun, 18 Jan 2015 13:28:00 +0100 Subject: [Rdo-list] "Manual" installation of Juno In-Reply-To: <660433606.26416.1421523759309.JavaMail.zimbra@li.nux.ro> References: <660433606.26416.1421523759309.JavaMail.zimbra@li.nux.ro> Message-ID: <20150118122800.GG4593@tesla.redhat.com> On Sat, Jan 17, 2015 at 07:42:39PM +0000, Nux! wrote: > Hi guys, > > I'm looking to install Openstack Juno from the RDO RPMs, but without > packstack/puppet/foreman. Are there any "usable" docs for this? Slightly dated (IceHouse - AUG2014) notes to setup a minimal Keystone, Neutron, Nova, Glance minimal environment in two Fedora 20 virtual machines: https://kashyapc.fedorapeople.org/virt/openstack/rdo/Minimal-OpenStack-IceHouse-setup.rst.txt -- /kashyap From nux at li.nux.ro Sun Jan 18 12:37:19 2015 From: nux at li.nux.ro (Nux!) Date: Sun, 18 Jan 2015 12:37:19 +0000 (GMT) Subject: [Rdo-list] "Manual" installation of Juno In-Reply-To: <20150118122800.GG4593@tesla.redhat.com> References: <660433606.26416.1421523759309.JavaMail.zimbra@li.nux.ro> <20150118122800.GG4593@tesla.redhat.com> Message-ID: <1964745427.26635.1421584639473.JavaMail.zimbra@li.nux.ro> Thanks Kashyap, that looks promising. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Kashyap Chamarthy" > To: "Nux!" > Cc: rdo-list at redhat.com > Sent: Sunday, 18 January, 2015 12:28:00 > Subject: Re: [Rdo-list] "Manual" installation of Juno > On Sat, Jan 17, 2015 at 07:42:39PM +0000, Nux! wrote: >> Hi guys, >> >> I'm looking to install Openstack Juno from the RDO RPMs, but without >> packstack/puppet/foreman. Are there any "usable" docs for this? > > Slightly dated (IceHouse - AUG2014) notes to setup a minimal Keystone, > Neutron, Nova, Glance minimal environment in two Fedora 20 virtual > machines: > > https://kashyapc.fedorapeople.org/virt/openstack/rdo/Minimal-OpenStack-IceHouse-setup.rst.txt > > > -- > /kashyap From bderzhavets at hotmail.com Sun Jan 18 20:16:13 2015 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Sun, 18 Jan 2015 15:16:13 -0500 Subject: [Rdo-list] Failure to resume instance on RDO Juno TwoNode F21 Cluster In-Reply-To: References: <9E8EE5E176B2BD49913B2F69B369AD8302136BD803@MX02A.corp.emc.com>, Message-ID: /var/log/libvirt/qemu/instance-0000000b.log An exact (reproducible ) error during resuming instance experiencing by qemu on Compute Node :- qemu-system-x86_64: /builddir/build/BUILD/qemu-2.1.2/hw/i386/kvm/clock.c:69: kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc' failed. I am not filing bug report due to announcement @https://openstack.redhat.com/Quickstart Boris. From: bderzhavets at hotmail.com To: rdo-list at redhat.com Date: Sat, 17 Jan 2015 03:19:47 -0500 Subject: [Rdo-list] Failure to resume instance on RDO Juno TwoNode F21 Cluster Attempting to resume instance via dashboard on Controller&&Network Node (ML2&OVS&VXLAN setup) I get Server code 1006 on VNC console. On Compute Node :- [root at juno2f21 ~]# service libvirtd status Redirecting to /bin/systemctl status libvirtd.service ? libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Sat 2015-01-17 09:51:01 MSK; 24min ago Docs: man:libvirtd(8) http://libvirt.org Main PID: 1035 (libvirtd) CGroup: /system.slice/libvirtd.service ??1035 /usr/sbin/libvirtd --listen Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: libvirt version: 1.2.9.1, package: 2.fc...g) Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: Unable to read from monitor: Connection...er Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: internal error: early end of file from ...m: qemu-system-x86_64: /builddir/build/BUI...d. Jan 17 10:15:07 juno2f21.localdomain libvirtd[1035]: error from service: TerminateMachine: N...wn Hint: Some lines were ellipsized, use -l to show in full. Workaround :- Hard reboot Bug has been reproduced twice ( two different installations ) Thanks Boris. _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From kchamart at redhat.com Mon Jan 19 08:49:04 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Mon, 19 Jan 2015 09:49:04 +0100 Subject: [Rdo-list] RDO Bug triage day tomorrow [19JAN2015] Message-ID: <20150119084904.GK4593@tesla.redhat.com> Heya! Tomorrow (3rd Tuesday of the month), 19JAN2015, is the monthly RDO bug triage day. If you have some spare cycles, please join in helping triage bugs/root-cause analysis in your area of expertise. Here's some details to get started[1] with bug triaging. Briefly, current state[2] of RDO bugs as of today: - NEW, ASSIGNED, ON_DEV : 219 - MODIFIED, POST, ON_QA : 140 - VERIFIED : 14 A good number of bugs are installer components (openstack-packstack, packstack-puppet-modules, openstack-foreman-installer), so it'd be nice if we can get to close some of those. [1] Bugzilla queries -- https://openstack.redhat.com/RDO-BugTriage#Bugzilla_queries [2] All bugs and their descriptions in plain text -- https://kashyapc.fedorapeople.org/virt/openstack/rdo-bug-status/2015/all-rdo-bugs-19-JAN-2015.txt -- /kashyap From rdo-info at redhat.com Mon Jan 19 16:58:01 2015 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 19 Jan 2015 16:58:01 +0000 Subject: [Rdo-list] [RDO] Blog roundup - January 19th 2015 Message-ID: <0000014b03212e22-f621714a-ce9c-4de6-b10d-4eaa3a796e75-000000@email.amazonses.com> rbowen started a discussion. Blog roundup - January 19th 2015 --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/998/blog-roundup-january-19th-2015 Have a great day! From rbowen at redhat.com Mon Jan 19 19:48:56 2015 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 19 Jan 2015 14:48:56 -0500 Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 19, 2015) Message-ID: <54BD5FA8.1060202@redhat.com> The following are the meetups I'm aware of in the coming week where RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If there's a meetup in your area, please consider attending. It's the best way to find out what interesting things are going on in the larger community, and a great way to make contacts that will help you solve your own problems in the future. And don't forget to blog about it, tweet about it, G+ about it. --Rich * Monday, January 19 in San Francisco, CA, US: Come Join Us to Hear About HyperFast OpenStack Storage with CloudFounders! - http://www.meetup.com/openstack/events/219308937/ * Monday, January 19 in M?nchen, DE: OpenStack Meetup N?rnberg - http://www.meetup.com/OpenStack-Munich/events/219374402/ * Monday, January 19 in Guadalajara, MX: Implementaci?nes de OpenStack, consideraciones basicas - http://www.meetup.com/OpenStack-GDL/events/219763969/ * Tuesday, January 20 in Tel Aviv-Yafo, IL: OpenStack 3 Days Training - http://www.meetup.com/IGTCloud/events/218924765/ * Tuesday, January 20 in Austin, TX, US: State of the Cloudy Union - http://www.meetup.com/CloudAustin/events/218793700/ * Tuesday, January 20 in Chesterfield, MO, US: January Openstack meetup - http://www.meetup.com/OpenStack-STL/events/219684702/ * Tuesday, January 20 in Paris, FR: Meetup #13 Ops : Comment g?rer une production OpenStack - http://www.meetup.com/OpenStack-France/events/219689511/ * Wednesday, January 21 in Mountain View, CA, US: Online Meetup: Introduction into Ceph storage for OpenStack - http://www.meetup.com/Cloud-Online-Meetup/events/219855488/ * Wednesday, January 21 in Shanghai, CN: 1/21 Afternoon Meet w/ You @ Shanghai JiaoTong University - http://www.meetup.com/Shanghai-OpenStack-Meetup/events/219803691/ * Wednesday, January 21 in Oslo, NO: January: The Future of Storage and PaaS Case Study. - http://www.meetup.com/RedHatOslo/events/219061905/ * Wednesday, January 21 in Berlin, DE: 7th OpenStack User Group Berlin - http://www.meetup.com/OpenStack-User-Group-Berlin/events/218681700/ * Wednesday, January 21 in Washington, DC, US: OpenStackDC Meetup #18 - http://www.meetup.com/OpenStackDC/events/218827000/ * Wednesday, January 21 in San Francisco, CA, US: Breaking the Neutron Barrier: Delivering Heterogenous Clouds - http://www.meetup.com/openstack/events/219067928/ * Thursday, January 22 in Mountain View, CA, US: Online Meetup: An Introduction to Platform-as-a-Service (PaaS) on OpenStack - http://www.meetup.com/Cloud-Online-Meetup/events/219851567/ * Thursday, January 22 in Raleigh, NC, US: January Red Hat Convergence Event - http://www.meetup.com/Raleigh-Red-Hat-User-Group/events/215314042/ * Thursday, January 22 in Helsinki, FI: Ceph & Gluster FS - Software Defined Storage Meetup - http://www.meetup.com/RedHatFinland/events/218774694/ * Thursday, January 22 in Henrico, VA, US: OpenStack Richmond Meetup #1 - http://www.meetup.com/OpenStack-Richmond/events/219346809/ * Thursday, January 22 in New York, NY, US: Using Ansible to Deploy OpenStack - http://www.meetup.com/Ansible-NYC/events/219791589/ * Thursday, January 22 in San Francisco, CA, US: South Bay OpenStack Meetup, Beginner track - http://www.meetup.com/openstack/events/219341335/ * Thursday, January 22 in San Francisco, CA, US: SFBay OpenStack Hackathon #OSSFO - http://www.meetup.com/openstack/events/176812172/ * Thursday, January 22 in Pasadena, CA, US: A DevOps State of Mind. OpenStack L.A. January '15 Meetup - http://www.meetup.com/OpenStack-LA/events/219699801/ * Thursday, January 22 in Herriman, UT, US: Monthly Meetup - http://www.meetup.com/openstack-utah/events/219336902/ * Thursday, January 22 in Whittier, CA, US: A DevOps State of Mind with Red Hat OpenShift - http://www.meetup.com/Greater-Los-Angeles-Area-Red-Hat-User-Group-RHUG/events/219703914/ * Saturday, January 24 in Palo Alto, CA, US: How OpenStack does Continuous Integration - http://www.meetup.com/cloudcomputing/events/219651605/ * Saturday, January 24 in Beijing, CN: OpenStack?????? - http://www.meetup.com/China-OpenStack-User-Group/events/219849812/ -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From dpkshetty at gmail.com Tue Jan 20 07:31:07 2015 From: dpkshetty at gmail.com (Deepak Shetty) Date: Tue, 20 Jan 2015 13:01:07 +0530 Subject: [Rdo-list] Query regarding RDO Juno-1 install on CentOS7 In-Reply-To: <54AA7150.40301@redhat.com> References: <54A16517.60803@laimbock.com> <54A3FF86.5090208@redhat.com> <54A480E6.2000901@redhat.com> <54AA7150.40301@redhat.com> Message-ID: On Mon, Jan 5, 2015 at 4:41 PM, Livnat Peer wrote: > On 01/01/2015 05:03 AM, Deepak Shetty wrote: > > Thanks perry, i googled too, but having instructions as part of the rdo > > quickstart is ideal as it is in the flow of things. For eg. I installed > > centos7 via pxe install and since rdo quick start didn't say anything > > specific abt Nm i just followed basic install process, only to know > > later that nm need to be disabled, which is not easy for someone not > > fairly expert in networking stuff so having the right cmds as part of > > rdo quick start pre reqs would help rdo beginerrs a lot > > > > I agree we should document that in the quick start. > Kuba - can you please add the steps to turn-off NM in the quickstart page. > Just wanted to check if the steps were added. I see that it would be very helpful as many RDO starters will stumble upon the same issue as this, so documenting the steps in quick start is a must thanx, deepak -------------- next part -------------- An HTML attachment was scrubbed... URL: From niyiallen at gmail.com Tue Jan 20 14:20:12 2015 From: niyiallen at gmail.com (Allen Efienokwu) Date: Tue, 20 Jan 2015 09:20:12 -0500 Subject: [Rdo-list] RDO Message-ID: *Hello all,* *Below is the steps I use to install OpenStack on Ubuntu and it never worked for me. It started well and in Step 1 but got stocked in Step2. I also tried in Fedora and CentOS. Got stock in step 2. Please help me out. Thanks* Step 1: Software repositories sudo yum update -y sudo yum install -y https://rdo.fedorapeople.org/rdo-release.rpm Step 2: Install Packstack Installer sudo yum install -y openstack-packstack Step 3: Run Packstack to install OpenStack Packstack takes the work out of manually setting up OpenStack. For a single node OpenStack deployment, run the following command. packstack --allinone *OpenStack {Ubuntu 14.04 LTS} Installation Steps* *OpenStack for ubuntu # sudo apt-get update # sudo apt-get install git # git clone **https://www.github.com/openstack-dev/devstack.git* * -b stable/juno # ls # cd devstack # ls # sudo apt-get install vim # apt-get installl libvirt-bin # sudo vim stackrc under "Base GIT Repo URL add '**https://www.github.com* * # under /devstack directory # ls # ./stack.sh* *Allen EfienokwuAnd we know that all things work together as fitting into a plan for us who love God and have been called according to his purpose-Rm8:28* -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Tue Jan 20 14:40:27 2015 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 20 Jan 2015 09:40:27 -0500 Subject: [Rdo-list] RDO In-Reply-To: References: Message-ID: <54BE68DB.1050202@redhat.com> On 01/20/2015 09:20 AM, Allen Efienokwu wrote: > > ** > > *Below is the steps I use to install OpenStack on Ubuntu and it never > worked for me. It started well and in Step 1 but got stocked in Step2. I > also tried in Fedora and CentOS. Got stock in step 2. Please help me > out. Thanks > * > > If you can provide more details - error messages, log files, and so on - that would greatly assist us in pointing you in the right direction. --Rich -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From tolivares at gmail.com Tue Jan 20 14:45:31 2015 From: tolivares at gmail.com (=?UTF-8?Q?Tom=C3=A1s?= Olivares) Date: Tue, 20 Jan 2015 06:45:31 -0800 (PST) Subject: [Rdo-list] RDO In-Reply-To: References: Message-ID: <1421765130519.6a3fcfe@Nodemailer> What?s the error you are getting? Also please note you may get a lot more help if you write to https://ask.openstack.org as it receives much more traffic/people. ? Sent from Mailbox On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu wrote: > *Hello all,* > *Below is the steps I use to install OpenStack on Ubuntu and it never > worked for me. It started well and in Step 1 but got stocked in Step2. I > also tried in Fedora and CentOS. Got stock in step 2. Please help me out. > Thanks* > Step 1: Software repositories > sudo yum update -y > sudo yum install -y https://rdo.fedorapeople.org/rdo-release.rpm > Step 2: Install Packstack Installer sudo yum install -y > openstack-packstack Step > 3: Run Packstack to install OpenStack > Packstack takes the work out of manually setting up OpenStack. For a single > node OpenStack deployment, run the following command. > packstack --allinone > *OpenStack {Ubuntu 14.04 LTS} Installation Steps* > *OpenStack for ubuntu # sudo apt-get update # sudo apt-get install git # > git clone **https://www.github.com/openstack-dev/devstack.git* > > * -b stable/juno # ls # cd devstack # ls # sudo apt-get install vim # > apt-get installl libvirt-bin # sudo vim stackrc under "Base GIT Repo URL > add '**https://www.github.com* > * # under /devstack directory # ls # ./stack.sh* > *Allen EfienokwuAnd we know that all things work together as fitting into a > plan for us who love God and have been called according to his > purpose-Rm8:28* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mohammed.sabuwala at cloudfx.com Tue Jan 20 14:49:54 2015 From: mohammed.sabuwala at cloudfx.com (Mohammed Sabuwala) Date: Tue, 20 Jan 2015 14:49:54 +0000 Subject: [Rdo-list] RDO In-Reply-To: <1421765130519.6a3fcfe@Nodemailer> References: <1421765130519.6a3fcfe@Nodemailer> Message-ID: I am not sure if I am the intended recipient, can someone remove off this list please. Best Regards, Mohammed Sabuwala Director, CloudFX Group Main Line: +65 6733 9886 | Mobile: +65 9114 0021 E-mail: Mohammed.Sabuwala at CloudFX.com | Website: www.CloudFX.com CloudConsult: www.cloudfxconsult.com CloudSelect: www.cloudselect.com CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, #04-05, Singapore, 239519 [slide1_logo.png] [http://www.cloudfx.com/images/social_icons/twitter.png] [http://www.cloudfx.com/images/social_icons/linkedin.png] [http://www.cloudfx.com/images/social_icons/facebook.png] From: Tom?s Olivares > Date: Tuesday, 20 January 2015 10:45 pm To: Allen Efienokwu > Cc: "rdo-list at redhat.com" > Subject: Re: [Rdo-list] RDO What's the error you are getting? Also please note you may get a lot more help if you write to https://ask.openstack.org as it receives much more traffic/people. - Sent from Mailbox On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > wrote: Hello all, Below is the steps I use to install OpenStack on Ubuntu and it never worked for me. It started well and in Step 1 but got stocked in Step2. I also tried in Fedora and CentOS. Got stock in step 2. Please help me out. Thanks Step 1: Software repositories sudo yum update -y sudo yum install -y https://rdo.fedorapeople.org/rdo-release.rpm Step 2: Install Packstack Installer sudo yum install -y openstack-packstack Step 3: Run Packstack to install OpenStack Packstack takes the work out of manually setting up OpenStack. For a single node OpenStack deployment, run the following command. packstack --allinone OpenStack {Ubuntu 14.04 LTS} Installation Steps OpenStack for ubuntu # sudo apt-get update # sudo apt-get install git # git clone https://www.github.com/openstack-dev/devstack.git -b stable/juno # ls # cd devstack # ls # sudo apt-get install vim # apt-get installl libvirt-bin # sudo vim stackrc under "Base GIT Repo URL add 'https://www.github.com # under /devstack directory # ls # ./stack.sh Allen Efienokwu And we know that all things work together as fitting into a plan for us who love God and have been called according to his purpose-Rm8:28 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6CAF0990-B924-4A52-9293-E325CA856FCE[42].png Type: image/png Size: 13184 bytes Desc: 6CAF0990-B924-4A52-9293-E325CA856FCE[42].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FFB4A3CD-486E-40F4-885C-134FF2FBA141[42].png Type: image/png Size: 3990 bytes Desc: FFB4A3CD-486E-40F4-885C-134FF2FBA141[42].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: E4EA9C3E-3D3C-4D73-95DF-B0B446D011EF[42].png Type: image/png Size: 3917 bytes Desc: E4EA9C3E-3D3C-4D73-95DF-B0B446D011EF[42].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 91596782-003A-4C17-9479-1F7240B909AA[42].png Type: image/png Size: 3865 bytes Desc: 91596782-003A-4C17-9479-1F7240B909AA[42].png URL: From rbowen at rcbowen.com Tue Jan 20 14:54:10 2015 From: rbowen at rcbowen.com (Rich Bowen) Date: Tue, 20 Jan 2015 09:54:10 -0500 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> Message-ID: <54BE6C12.9030009@rcbowen.com> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: > I am not sure if I am the intended recipient, can someone remove off > this list please. > To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com --Rich > > *Best Regards,* > > ** > > *Mohammed Sabuwala* > > *Director, CloudFX Group* > > *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 > > *E-mail:*Mohammed.Sabuwala at CloudFX.com > | *Website:* www.CloudFX.com > > > *CloudConsult:* www.cloudfxconsult.com > *CloudSelect:* www.cloudselect.com > > CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, > #04-05, Singapore, 239519 > > slide1_logo.png > http://www.cloudfx.com/images/social_icons/twitter.png > http://www.cloudfx.com/images/social_icons/linkedin.png > http://www.cloudfx.com/images/social_icons/facebook.png > > > > From: Tom?s Olivares > > Date: Tuesday, 20 January 2015 10:45 pm > To: Allen Efienokwu > > Cc: "rdo-list at redhat.com " > > > Subject: Re: [Rdo-list] RDO > > What?s the error you are getting? Also please note you may get a lot > more help if you write to https://ask.openstack.org as it receives much > more traffic/people. > > ? > Sent from Mailbox > > > On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > wrote: > > *Hello all,* > > > ** > > *Below is the steps I use to install OpenStack on Ubuntu and it > never worked for me. It started well and in Step 1 but got stocked > in Step2. I also tried in Fedora and CentOS. Got stock in step 2. > Please help me out. Thanks > * > > > ** > > > ** > > > Step 1: Software repositories > > sudo yum update -y > > sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm > > > Step 2: Install Packstack Installer > > sudo yum install -y openstack-packstack > > > Step 3: Run Packstack to install OpenStack > > Packstack takes the work out of manually setting up OpenStack. For a > single node OpenStack deployment, run the following command. > > packstack --allinone > > * > * > > * > * > > *OpenStack {Ubuntu 14.04 LTS} Installation Steps* > > * > * > > *OpenStack for ubuntu > > # sudo apt-get update > > # sudo apt-get install git > > # git clone **https://www.github.com/openstack-dev/devstack.git**-b > stable/juno > > # ls > > # cd devstack > > # ls > > # sudo apt-get install vim > > # apt-get installl libvirt-bin > > # sudo vim stackrc > under "Base GIT Repo URL > add '**https://www.github.com* * > > # under /devstack directory > # ls > # ./stack.sh* > > *Allen Efienokwu > And we know that all things work together as fitting into a plan for > us who love God and have been called according to his purpose-Rm8:28 > * > > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -- Rich Bowen - rbowen at rcbowen.com - @rbowen http://apachecon.com/ - @apachecon From mohammed.sabuwala at cloudfx.com Tue Jan 20 14:55:43 2015 From: mohammed.sabuwala at cloudfx.com (Mohammed Sabuwala) Date: Tue, 20 Jan 2015 14:55:43 +0000 Subject: [Rdo-list] RDO In-Reply-To: <54BE6C12.9030009@rcbowen.com> References: <1421765130519.6a3fcfe@Nodemailer> , <54BE6C12.9030009@rcbowen.com> Message-ID: <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Cannot send emails to that dl Regards, Mohammed Sabuwala Director, CloudFX Group +6591140021 | www.cloudfx.com On 20 Jan 2015, at 10:54 pm, Rich Bowen > wrote: On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: I am not sure if I am the intended recipient, can someone remove off this list please. To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com --Rich *Best Regards,* ** *Mohammed Sabuwala* *Director, CloudFX Group* *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 *E-mail:*Mohammed.Sabuwala at CloudFX.com | *Website:* www.CloudFX.com *CloudConsult:* www.cloudfxconsult.com *CloudSelect:* www.cloudselect.com CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, #04-05, Singapore, 239519 slide1_logo.png http://www.cloudfx.com/images/social_icons/twitter.png http://www.cloudfx.com/images/social_icons/linkedin.png http://www.cloudfx.com/images/social_icons/facebook.png From: Tom?s Olivares > Date: Tuesday, 20 January 2015 10:45 pm To: Allen Efienokwu > Cc: "rdo-list at redhat.com " > Subject: Re: [Rdo-list] RDO What's the error you are getting? Also please note you may get a lot more help if you write to https://ask.openstack.org as it receives much more traffic/people. - Sent from Mailbox On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > wrote: *Hello all,* ** *Below is the steps I use to install OpenStack on Ubuntu and it never worked for me. It started well and in Step 1 but got stocked in Step2. I also tried in Fedora and CentOS. Got stock in step 2. Please help me out. Thanks * ** ** Step 1: Software repositories sudo yum update -y sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm Step 2: Install Packstack Installer sudo yum install -y openstack-packstack Step 3: Run Packstack to install OpenStack Packstack takes the work out of manually setting up OpenStack. For a single node OpenStack deployment, run the following command. packstack --allinone * * * * *OpenStack {Ubuntu 14.04 LTS} Installation Steps* * * *OpenStack for ubuntu # sudo apt-get update # sudo apt-get install git # git clone **https://www.github.com/openstack-dev/devstack.git**-b stable/juno # ls # cd devstack # ls # sudo apt-get install vim # apt-get installl libvirt-bin # sudo vim stackrc under "Base GIT Repo URL add '**https://www.github.com* * # under /devstack directory # ls # ./stack.sh* *Allen Efienokwu And we know that all things work together as fitting into a plan for us who love God and have been called according to his purpose-Rm8:28 * _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -- Rich Bowen - rbowen at rcbowen.com - @rbowen http://apachecon.com/ - @apachecon -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at gmail.com Tue Jan 20 15:06:00 2015 From: apevec at gmail.com (Alan Pevec) Date: Tue, 20 Jan 2015 16:06:00 +0100 Subject: [Rdo-list] List of pending RDO updates as of Jan 20, 2015 Message-ID: > * apevec will post update on what's in the queue until RDO CI goes public CI is not public yet, here's an update as of Jan 20, 2015 ( Reference for CI stages http://apevec.github.io/rdo-intro.html#8 ) * PHASE1 - updates passed smoke test openstack-cinder-2014.2.1-2 python-taskflow-0.5.0-1 --- Missing requirements in openstack-cinder 2014.2.1 (RHBZ #1174760 #1175368 #1179060) updates/p656.yml by Haikel Guemar openstack-glance-2014.1.3-3.fc21 @ koji -> icehouse / fedora-20 openstack-glance-2014.1.3-3.el6 @ copr-jruzicka -> icehouse / epel-6 openstack-glance-2014.1.3-3.el7 @ copr-jruzicka -> icehouse / epel-7 --- fix CVE-2014-9493 openstack-glance - unrestricted path traversal flaw (RHBZ * STAGE openstack-glance-2014.2.1-2 fix CVE-2014-9493 openstack-glance - unrestricted path traversal flaw (RHBZ openstack-heat-gbp-2014.2-1 openstack-neutron-gbp-2014.2-1 python-django-horizon-gbp-2014.2-1 python-gbpclient-0.9.0-1 Neutron Group Based Policy 2014.2 from rkukura python-glanceclient-0.15.0-1 Latest glanceclient for Juno openstack-packstack-2014.2-0.14.dev1401.gdd19d48 Update packstack to fix rhbz#1172241 python-manilaclient-1.0.1-3 initial import in RDO Juno of python-manila python-glance-store-0.1.10-2 New upstream version (fixes RHBZ #1169145 #1175419) python-oslo-messaging-1.4.1-3 Fix reconnect exception handler (Dan Smith) rhbz#1175685 From jasonmicron at gmail.com Tue Jan 20 17:19:09 2015 From: jasonmicron at gmail.com (Jason Harris) Date: Tue, 20 Jan 2015 11:19:09 -0600 Subject: [Rdo-list] RDO In-Reply-To: <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: Same with me. I don't know how I got on here, and I can't unsubscribe. On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala < mohammed.sabuwala at cloudfx.com> wrote: > Cannot send emails to that dl > > Regards, Mohammed Sabuwala > Director, CloudFX Group > +6591140021 | www.cloudfx.com > > > On 20 Jan 2015, at 10:54 pm, Rich Bowen wrote: > > > > On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: > > I am not sure if I am the intended recipient, can someone remove off > > this list please. > > > > > To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com > > --Rich > > > > > *Best Regards,* > > > ** > > > *Mohammed Sabuwala* > > > *Director, CloudFX Group* > > > *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 > > > *E-mail:*Mohammed.Sabuwala at CloudFX.com > > > | > *Website:* www.CloudFX.com > > > > > *CloudConsult:* www.cloudfxconsult.com > > *CloudSelect:* www.cloudselect.com > > > CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, > > #04-05, Singapore, 239519 > > > slide1_logo.png > > > http://www.cloudfx.com/images/social_icons/twitter.png > > > http://www.cloudfx.com/images/social_icons/linkedin.png > > < > http://www.linkedin.com/company/cloudfx-pte-ltd?trk=hb_tab_compy_id_2665577 > >http://www.cloudfx.com/images/social_icons/facebook.png > > > > > > From: Tom?s Olivares >> > > Date: Tuesday, 20 January 2015 10:45 pm > > To: Allen Efienokwu >> > > Cc: "rdo-list at redhat.com > >" > > >> > > Subject: Re: [Rdo-list] RDO > > > What?s the error you are getting? Also please note you may get a lot > > more help if you write to https://ask.openstack.org as it receives much > > more traffic/people. > > > ? > > Sent from Mailbox > > > > On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > >> wrote: > > > *Hello all,* > > > > ** > > > *Below is the steps I use to install OpenStack on Ubuntu and it > > never worked for me. It started well and in Step 1 but got stocked > > in Step2. I also tried in Fedora and CentOS. Got stock in step 2. > > Please help me out. Thanks > > * > > > > ** > > > > ** > > > > Step 1: Software repositories > > > sudo yum update -y > > > sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm > > > > Step 2: Install Packstack Installer > > > sudo yum install -y openstack-packstack > > > > Step 3: Run Packstack to install OpenStack > > > Packstack takes the work out of manually setting up OpenStack. For a > > single node OpenStack deployment, run the following command. > > > packstack --allinone > > > * > > * > > > * > > * > > > *OpenStack {Ubuntu 14.04 LTS} Installation Steps* > > > * > > * > > > *OpenStack for ubuntu > > > # sudo apt-get update > > > # sudo apt-get install git > > > # git clone **https://www.github.com/openstack-dev/devstack.git**-b > > stable/juno > > > # ls > > > # cd devstack > > > # ls > > > # sudo apt-get install vim > > > # apt-get installl libvirt-bin > > > # sudo vim stackrc > > under "Base GIT Repo URL > > add '**https://www.github.com* * > > > # under /devstack directory > > # ls > > # ./stack.sh* > > > *Allen Efienokwu > > And we know that all things work together as fitting into a plan for > > us who love God and have been called according to his purpose-Rm8:28 > > * > > > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > -- > Rich Bowen - rbowen at rcbowen.com - @rbowen > http://apachecon.com/ - @apachecon > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adam.fyfe1 at gmail.com Tue Jan 20 17:22:55 2015 From: adam.fyfe1 at gmail.com (Adam Fyfe) Date: Tue, 20 Jan 2015 17:22:55 +0000 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: It's an invasion ..... I shall invoice red hat $25 for every email received by me from now On 20 Jan 2015 17:21, "Jason Harris" wrote: > > Same with me. I don't know how I got on here, and I can't unsubscribe. > > On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala < mohammed.sabuwala at cloudfx.com> wrote: >> >> Cannot send emails to that dl >> >> Regards, Mohammed Sabuwala >> Director, CloudFX Group >> +6591140021 | www.cloudfx.com >> >> >> On 20 Jan 2015, at 10:54 pm, Rich Bowen wrote: >> >>> >>> >>> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: >>>> >>>> I am not sure if I am the intended recipient, can someone remove off >>>> >>>> this list please. >>>> >>>> >>> >>> >>> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com >>> >>> --Rich >>> >>> >>> >>>> >>>> *Best Regards,* >>>> >>>> >>>> ** >>>> >>>> >>>> *Mohammed Sabuwala* >>>> >>>> >>>> *Director, CloudFX Group* >>>> >>>> >>>> *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 >>>> >>>> >>>> *E-mail:*Mohammed.Sabuwala at CloudFX.com >>>> >>>> | *Website:* www.CloudFX.com >>>> >>>> >>>> >>>> >>>> *CloudConsult:* www.cloudfxconsult.com >>>> >>>> *CloudSelect:* www.cloudselect.com >>>> >>>> >>>> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, >>>> >>>> #04-05, Singapore, 239519 >>>> >>>> >>>> slide1_logo.png >>>> >>>> http://www.cloudfx.com/images/social_icons/twitter.png >>>> >>>> http://www.cloudfx.com/images/social_icons/linkedin.png >>>> >>>> < http://www.linkedin.com/company/cloudfx-pte-ltd?trk=hb_tab_compy_id_2665577> http://www.cloudfx.com/images/social_icons/facebook.png >>>> >>>> >>>> >>>> >>>> >>>> From: Tom?s Olivares > >>>> >>>> Date: Tuesday, 20 January 2015 10:45 pm >>>> >>>> To: Allen Efienokwu > >>>> >>>> Cc: "rdo-list at redhat.com " >>>> >>>> > >>>> >>>> Subject: Re: [Rdo-list] RDO >>>> >>>> >>>> What's the error you are getting? Also please note you may get a lot >>>> >>>> more help if you write to https://ask.openstack.org as it receives much >>>> >>>> more traffic/people. >>>> >>>> >>>> -- >>>> >>>> Sent from Mailbox >>>> >>>> >>>> >>>> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu >>> >>>> > wrote: >>>> >>>> >>>> *Hello all,* >>>> >>>> >>>> >>>> ** >>>> >>>> >>>> *Below is the steps I use to install OpenStack on Ubuntu and it >>>> >>>> never worked for me. It started well and in Step 1 but got stocked >>>> >>>> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. >>>> >>>> Please help me out. Thanks >>>> >>>> * >>>> >>>> >>>> >>>> ** >>>> >>>> >>>> >>>> ** >>>> >>>> >>>> >>>> Step 1: Software repositories >>>> >>>> >>>> sudo yum update -y >>>> >>>> >>>> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm >>>> >>>> >>>> >>>> Step 2: Install Packstack Installer >>>> >>>> >>>> sudo yum install -y openstack-packstack >>>> >>>> >>>> >>>> Step 3: Run Packstack to install OpenStack >>>> >>>> >>>> Packstack takes the work out of manually setting up OpenStack. For a >>>> >>>> single node OpenStack deployment, run the following command. >>>> >>>> >>>> packstack --allinone >>>> >>>> >>>> * >>>> >>>> * >>>> >>>> >>>> * >>>> >>>> * >>>> >>>> >>>> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* >>>> >>>> >>>> * >>>> >>>> * >>>> >>>> >>>> *OpenStack for ubuntu >>>> >>>> >>>> # sudo apt-get update >>>> >>>> >>>> # sudo apt-get install git >>>> >>>> >>>> # git clone **https://www.github.com/openstack-dev/devstack.git**-b >>>> >>>> stable/juno >>>> >>>> >>>> # ls >>>> >>>> >>>> # cd devstack >>>> >>>> >>>> # ls >>>> >>>> >>>> # sudo apt-get install vim >>>> >>>> >>>> # apt-get installl libvirt-bin >>>> >>>> >>>> # sudo vim stackrc >>>> >>>> under "Base GIT Repo URL >>>> >>>> add '**https://www.github.com* * >>>> >>>> >>>> # under /devstack directory >>>> >>>> # ls >>>> >>>> # ./stack.sh* >>>> >>>> >>>> *Allen Efienokwu >>>> >>>> And we know that all things work together as fitting into a plan for >>>> >>>> us who love God and have been called according to his purpose-Rm8:28 >>>> >>>> * >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> Rdo-list mailing list >>>> >>>> Rdo-list at redhat.com >>>> >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>> >>>> >>> >>> >>> -- >>> Rich Bowen - rbowen at rcbowen.com - @rbowen >>> http://apachecon.com/ - @apachecon >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From luis.munoz.hdez at gmail.com Tue Jan 20 17:26:29 2015 From: luis.munoz.hdez at gmail.com (=?utf-8?Q?Luis_Mu=C3=B1oz_Hern=C3=A1ndez?=) Date: Tue, 20 Jan 2015 18:26:29 +0100 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: <9FF72EEA-E4E1-4CC7-B816-F6FC11844367@gmail.com> To manage your subscriptions go to: http://www.redhat.com/mailman/listinfo/rdo-list > El 20/1/2015, a las 18:19, Jason Harris escribi?: > > Same with me. I don't know how I got on here, and I can't unsubscribe. > > On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala > wrote: > Cannot send emails to that dl > > Regards, Mohammed Sabuwala > Director, CloudFX Group > +6591140021 | www.cloudfx.com > > > On 20 Jan 2015, at 10:54 pm, Rich Bowen > wrote: > >> >> >> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: >>> I am not sure if I am the intended recipient, can someone remove off >>> this list please. >>> >> >> >> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com >> >> --Rich >> >> >> >>> >>> *Best Regards,* >>> >>> ** >>> >>> *Mohammed Sabuwala* >>> >>> *Director, CloudFX Group* >>> >>> *Main Line: *+65 6733 9886 * | Mobile:* +65 9114 0021 >>> >>> *E-mail:*Mohammed.Sabuwala at CloudFX.com >>> > | *Website:* www.CloudFX.com >>> > >>> >>> *CloudConsult:* www.cloudfxconsult.com > >>> *CloudSelect:* www.cloudselect.com > >>> >>> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, >>> #04-05, Singapore, 239519 >>> >>> slide1_logo.png >>> >http://www.cloudfx.com/images/social_icons/twitter.png >>> >http://www.cloudfx.com/images/social_icons/linkedin.png >>> >http://www.cloudfx.com/images/social_icons/facebook.png >>> > >>> >>> >>> From: Tom?s Olivares >> >>> Date: Tuesday, 20 January 2015 10:45 pm >>> To: Allen Efienokwu >> >>> Cc: "rdo-list at redhat.com >" >>> >> >>> Subject: Re: [Rdo-list] RDO >>> >>> What?s the error you are getting? Also please note you may get a lot >>> more help if you write to https://ask.openstack.org as it receives much >>> more traffic/people. >>> >>> ? >>> Sent from Mailbox > >>> >>> >>> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu >>> >> wrote: >>> >>> *Hello all,* >>> >>> >>> ** >>> >>> *Below is the steps I use to install OpenStack on Ubuntu and it >>> never worked for me. It started well and in Step 1 but got stocked >>> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. >>> Please help me out. Thanks >>> * >>> >>> >>> ** >>> >>> >>> ** >>> >>> >>> Step 1: Software repositories >>> >>> sudo yum update -y >>> >>> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm >>> >>> >>> Step 2: Install Packstack Installer >>> >>> sudo yum install -y openstack-packstack >>> >>> >>> Step 3: Run Packstack to install OpenStack >>> >>> Packstack takes the work out of manually setting up OpenStack. For a >>> single node OpenStack deployment, run the following command. >>> >>> packstack --allinone >>> >>> * >>> * >>> >>> * >>> * >>> >>> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* >>> >>> * >>> * >>> >>> *OpenStack for ubuntu >>> >>> # sudo apt-get update >>> >>> # sudo apt-get install git >>> >>> # git clone **https://www.github.com/openstack-dev/devstack.git**-b >>> stable/juno >>> >>> # ls >>> >>> # cd devstack >>> >>> # ls >>> >>> # sudo apt-get install vim >>> >>> # apt-get installl libvirt-bin >>> >>> # sudo vim stackrc >>> under "Base GIT Repo URL >>> add '**https://www.github.com* >* >>> >>> # under /devstack directory >>> # ls >>> # ./stack.sh* >>> >>> *Allen Efienokwu >>> And we know that all things work together as fitting into a plan for >>> us who love God and have been called according to his purpose-Rm8:28 >>> * >>> >>> >>> >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >> >> >> -- >> Rich Bowen - rbowen at rcbowen.com - @rbowen >> http://apachecon.com/ - @apachecon > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From mohitdavra at gmail.com Tue Jan 20 17:28:09 2015 From: mohitdavra at gmail.com (Mohit Davra) Date: Tue, 20 Jan 2015 22:58:09 +0530 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: Please don't send me mail On Tuesday, January 20, 2015, Jason Harris wrote: > Same with me. I don't know how I got on here, and I can't unsubscribe. > > On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala < > mohammed.sabuwala at cloudfx.com > > wrote: > >> Cannot send emails to that dl >> >> Regards, Mohammed Sabuwala >> Director, CloudFX Group >> +6591140021 | www.cloudfx.com >> >> >> On 20 Jan 2015, at 10:54 pm, Rich Bowen > > wrote: >> >> >> >> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: >> >> I am not sure if I am the intended recipient, can someone remove off >> >> this list please. >> >> >> >> >> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com >> >> >> --Rich >> >> >> >> >> *Best Regards,* >> >> >> ** >> >> >> *Mohammed Sabuwala* >> >> >> *Director, CloudFX Group* >> >> >> *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 >> >> >> *E-mail:*Mohammed.Sabuwala at CloudFX.com >> >> >> > > | >> *Website:* www.CloudFX.com >> >> >> >> >> *CloudConsult:* www.cloudfxconsult.com >> >> *CloudSelect:* www.cloudselect.com >> >> >> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, >> >> #04-05, Singapore, 239519 >> >> >> slide1_logo.png >> >> >> http://www.cloudfx.com/images/social_icons/twitter.png >> >> >> http://www.cloudfx.com/images/social_icons/linkedin.png >> >> < >> http://www.linkedin.com/company/cloudfx-pte-ltd?trk=hb_tab_compy_id_2665577 >> >http://www.cloudfx.com/images/social_icons/facebook.png >> >> >> >> >> >> From: Tom?s Olivares > < >> mailto:tolivares at gmail.com >> >> >> >> Date: Tuesday, 20 January 2015 10:45 pm >> >> To: Allen Efienokwu > < >> mailto:niyiallen at gmail.com >> >> >> >> Cc: "rdo-list at redhat.com >> < >> mailto:rdo-list at redhat.com >> >" >> >> > < >> mailto:rdo-list at redhat.com >> >> >> >> Subject: Re: [Rdo-list] RDO >> >> >> What?s the error you are getting? Also please note you may get a lot >> >> more help if you write to https://ask.openstack.org as it receives much >> >> more traffic/people. >> >> >> ? >> >> Sent from Mailbox >> >> >> >> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > >> >> > >> wrote: >> >> >> *Hello all,* >> >> >> >> ** >> >> >> *Below is the steps I use to install OpenStack on Ubuntu and it >> >> never worked for me. It started well and in Step 1 but got stocked >> >> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. >> >> Please help me out. Thanks >> >> * >> >> >> >> ** >> >> >> >> ** >> >> >> >> Step 1: Software repositories >> >> >> sudo yum update -y >> >> >> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm >> >> >> >> Step 2: Install Packstack Installer >> >> >> sudo yum install -y openstack-packstack >> >> >> >> Step 3: Run Packstack to install OpenStack >> >> >> Packstack takes the work out of manually setting up OpenStack. For a >> >> single node OpenStack deployment, run the following command. >> >> >> packstack --allinone >> >> >> * >> >> * >> >> >> * >> >> * >> >> >> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* >> >> >> * >> >> * >> >> >> *OpenStack for ubuntu >> >> >> # sudo apt-get update >> >> >> # sudo apt-get install git >> >> >> # git clone **https://www.github.com/openstack-dev/devstack.git**-b >> >> stable/juno >> >> >> # ls >> >> >> # cd devstack >> >> >> # ls >> >> >> # sudo apt-get install vim >> >> >> # apt-get installl libvirt-bin >> >> >> # sudo vim stackrc >> >> under "Base GIT Repo URL >> >> add '**https://www.github.com* * >> >> >> # under /devstack directory >> >> # ls >> >> # ./stack.sh* >> >> >> *Allen Efienokwu >> >> And we know that all things work together as fitting into a plan for >> >> us who love God and have been called according to his purpose-Rm8:28 >> >> * >> >> >> >> >> >> _______________________________________________ >> >> Rdo-list mailing list >> >> Rdo-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> >> >> -- >> Rich Bowen - rbowen at rcbowen.com >> - @rbowen >> http://apachecon.com/ - @apachecon >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mohitdavra at gmail.com Tue Jan 20 17:32:01 2015 From: mohitdavra at gmail.com (Mohit Davra) Date: Tue, 20 Jan 2015 23:02:01 +0530 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: Please don't send me mail On Tuesday, January 20, 2015, Jason Harris wrote: > Same with me. I don't know how I got on here, and I can't unsubscribe. > > On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala < > mohammed.sabuwala at cloudfx.com > > wrote: > >> Cannot send emails to that dl >> >> Regards, Mohammed Sabuwala >> Director, CloudFX Group >> +6591140021 | www.cloudfx.com >> >> >> On 20 Jan 2015, at 10:54 pm, Rich Bowen > > wrote: >> >> >> >> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: >> >> I am not sure if I am the intended recipient, can someone remove off >> >> this list please. >> >> >> >> >> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com >> >> >> --Rich >> >> >> >> >> *Best Regards,* >> >> >> ** >> >> >> *Mohammed Sabuwala* >> >> >> *Director, CloudFX Group* >> >> >> *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 >> >> >> *E-mail:*Mohammed.Sabuwala at CloudFX.com >> >> >> > > | >> *Website:* www.CloudFX.com >> >> >> >> >> *CloudConsult:* www.cloudfxconsult.com >> >> *CloudSelect:* www.cloudselect.com >> >> >> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, >> >> #04-05, Singapore, 239519 >> >> >> slide1_logo.png >> >> >> http://www.cloudfx.com/images/social_icons/twitter.png >> >> >> http://www.cloudfx.com/images/social_icons/linkedin.png >> >> < >> http://www.linkedin.com/company/cloudfx-pte-ltd?trk=hb_tab_compy_id_2665577 >> >http://www.cloudfx.com/images/social_icons/facebook.png >> >> >> >> >> >> From: Tom?s Olivares > < >> mailto:tolivares at gmail.com >> >> >> >> Date: Tuesday, 20 January 2015 10:45 pm >> >> To: Allen Efienokwu > < >> mailto:niyiallen at gmail.com >> >> >> >> Cc: "rdo-list at redhat.com >> < >> mailto:rdo-list at redhat.com >> >" >> >> > < >> mailto:rdo-list at redhat.com >> >> >> >> Subject: Re: [Rdo-list] RDO >> >> >> What?s the error you are getting? Also please note you may get a lot >> >> more help if you write to https://ask.openstack.org as it receives much >> >> more traffic/people. >> >> >> ? >> >> Sent from Mailbox >> >> >> >> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > >> >> > >> wrote: >> >> >> *Hello all,* >> >> >> >> ** >> >> >> *Below is the steps I use to install OpenStack on Ubuntu and it >> >> never worked for me. It started well and in Step 1 but got stocked >> >> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. >> >> Please help me out. Thanks >> >> * >> >> >> >> ** >> >> >> >> ** >> >> >> >> Step 1: Software repositories >> >> >> sudo yum update -y >> >> >> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm >> >> >> >> Step 2: Install Packstack Installer >> >> >> sudo yum install -y openstack-packstack >> >> >> >> Step 3: Run Packstack to install OpenStack >> >> >> Packstack takes the work out of manually setting up OpenStack. For a >> >> single node OpenStack deployment, run the following command. >> >> >> packstack --allinone >> >> >> * >> >> * >> >> >> * >> >> * >> >> >> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* >> >> >> * >> >> * >> >> >> *OpenStack for ubuntu >> >> >> # sudo apt-get update >> >> >> # sudo apt-get install git >> >> >> # git clone **https://www.github.com/openstack-dev/devstack.git**-b >> >> stable/juno >> >> >> # ls >> >> >> # cd devstack >> >> >> # ls >> >> >> # sudo apt-get install vim >> >> >> # apt-get installl libvirt-bin >> >> >> # sudo vim stackrc >> >> under "Base GIT Repo URL >> >> add '**https://www.github.com* * >> >> >> # under /devstack directory >> >> # ls >> >> # ./stack.sh* >> >> >> *Allen Efienokwu >> >> And we know that all things work together as fitting into a plan for >> >> us who love God and have been called according to his purpose-Rm8:28 >> >> * >> >> >> >> >> >> _______________________________________________ >> >> Rdo-list mailing list >> >> Rdo-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> >> >> -- >> Rich Bowen - rbowen at rcbowen.com >> - @rbowen >> http://apachecon.com/ - @apachecon >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shrini.sastha at gmail.com Tue Jan 20 17:33:41 2015 From: shrini.sastha at gmail.com (shrini sastha) Date: Tue, 20 Jan 2015 12:33:41 -0500 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: Same here as we'll this is like a spam for Me .. On Jan 20, 2015 12:23 PM, "Jason Harris" wrote: > Same with me. I don't know how I got on here, and I can't unsubscribe. > > On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala < > mohammed.sabuwala at cloudfx.com> wrote: > >> Cannot send emails to that dl >> >> Regards, Mohammed Sabuwala >> Director, CloudFX Group >> +6591140021 | www.cloudfx.com >> >> >> On 20 Jan 2015, at 10:54 pm, Rich Bowen wrote: >> >> >> >> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: >> >> I am not sure if I am the intended recipient, can someone remove off >> >> this list please. >> >> >> >> >> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com >> >> --Rich >> >> >> >> >> *Best Regards,* >> >> >> ** >> >> >> *Mohammed Sabuwala* >> >> >> *Director, CloudFX Group* >> >> >> *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 >> >> >> *E-mail:*Mohammed.Sabuwala at CloudFX.com >> >> > | >> *Website:* www.CloudFX.com >> >> >> >> >> *CloudConsult:* www.cloudfxconsult.com >> >> *CloudSelect:* www.cloudselect.com >> >> >> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, >> >> #04-05, Singapore, 239519 >> >> >> slide1_logo.png >> >> >> http://www.cloudfx.com/images/social_icons/twitter.png >> >> >> http://www.cloudfx.com/images/social_icons/linkedin.png >> >> < >> http://www.linkedin.com/company/cloudfx-pte-ltd?trk=hb_tab_compy_id_2665577 >> >http://www.cloudfx.com/images/social_icons/facebook.png >> >> >> >> >> >> From: Tom?s Olivares > >> >> >> Date: Tuesday, 20 January 2015 10:45 pm >> >> To: Allen Efienokwu > >> >> >> Cc: "rdo-list at redhat.com > >" >> >> >> >> >> Subject: Re: [Rdo-list] RDO >> >> >> What?s the error you are getting? Also please note you may get a lot >> >> more help if you write to https://ask.openstack.org as it receives much >> >> more traffic/people. >> >> >> ? >> >> Sent from Mailbox >> >> >> >> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > >> >> wrote: >> >> >> *Hello all,* >> >> >> >> ** >> >> >> *Below is the steps I use to install OpenStack on Ubuntu and it >> >> never worked for me. It started well and in Step 1 but got stocked >> >> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. >> >> Please help me out. Thanks >> >> * >> >> >> >> ** >> >> >> >> ** >> >> >> >> Step 1: Software repositories >> >> >> sudo yum update -y >> >> >> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm >> >> >> >> Step 2: Install Packstack Installer >> >> >> sudo yum install -y openstack-packstack >> >> >> >> Step 3: Run Packstack to install OpenStack >> >> >> Packstack takes the work out of manually setting up OpenStack. For a >> >> single node OpenStack deployment, run the following command. >> >> >> packstack --allinone >> >> >> * >> >> * >> >> >> * >> >> * >> >> >> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* >> >> >> * >> >> * >> >> >> *OpenStack for ubuntu >> >> >> # sudo apt-get update >> >> >> # sudo apt-get install git >> >> >> # git clone **https://www.github.com/openstack-dev/devstack.git**-b >> >> stable/juno >> >> >> # ls >> >> >> # cd devstack >> >> >> # ls >> >> >> # sudo apt-get install vim >> >> >> # apt-get installl libvirt-bin >> >> >> # sudo vim stackrc >> >> under "Base GIT Repo URL >> >> add '**https://www.github.com* * >> >> >> # under /devstack directory >> >> # ls >> >> # ./stack.sh* >> >> >> *Allen Efienokwu >> >> And we know that all things work together as fitting into a plan for >> >> us who love God and have been called according to his purpose-Rm8:28 >> >> * >> >> >> >> >> >> _______________________________________________ >> >> Rdo-list mailing list >> >> Rdo-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> >> >> -- >> Rich Bowen - rbowen at rcbowen.com - @rbowen >> http://apachecon.com/ - @apachecon >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ramdaskhatake at gmail.com Tue Jan 20 17:35:52 2015 From: ramdaskhatake at gmail.com (Ramdas Khatake) Date: Tue, 20 Jan 2015 23:05:52 +0530 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: Pls don't send me mail On Jan 20, 2015 10:55 PM, "Adam Fyfe" wrote: > It's an invasion ..... > > I shall invoice red hat $25 for every email received by me from now > > > On 20 Jan 2015 17:21, "Jason Harris" wrote: > > > > Same with me. I don't know how I got on here, and I can't unsubscribe. > > > > On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala < > mohammed.sabuwala at cloudfx.com> wrote: > >> > >> Cannot send emails to that dl > >> > >> Regards, Mohammed Sabuwala > >> Director, CloudFX Group > >> +6591140021 | www.cloudfx.com > >> > >> > >> On 20 Jan 2015, at 10:54 pm, Rich Bowen wrote: > >> > >>> > >>> > >>> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: > >>>> > >>>> I am not sure if I am the intended recipient, can someone remove off > >>>> > >>>> this list please. > >>>> > >>>> > >>> > >>> > >>> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com > >>> > >>> --Rich > >>> > >>> > >>> > >>>> > >>>> *Best Regards,* > >>>> > >>>> > >>>> ** > >>>> > >>>> > >>>> *Mohammed Sabuwala* > >>>> > >>>> > >>>> *Director, CloudFX Group* > >>>> > >>>> > >>>> *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 > >>>> > >>>> > >>>> *E-mail:*Mohammed.Sabuwala at CloudFX.com > >>>> > >>>> | *Website:* www.CloudFX.com > >>>> > >>>> > >>>> > >>>> > >>>> *CloudConsult:* www.cloudfxconsult.com < > http://www.cloudfxconsult.com/> > >>>> > >>>> *CloudSelect:* www.cloudselect.com > >>>> > >>>> > >>>> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, > >>>> > >>>> #04-05, Singapore, 239519 > >>>> > >>>> > >>>> slide1_logo.png > >>>> > >>>> > http://www.cloudfx.com/images/social_icons/twitter.png > >>>> > >>>> > http://www.cloudfx.com/images/social_icons/linkedin.png > >>>> > >>>> < > http://www.linkedin.com/company/cloudfx-pte-ltd?trk=hb_tab_compy_id_2665577 > >http://www.cloudfx.com/images/social_icons/facebook.png > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> From: Tom?s Olivares >> > >>>> > >>>> Date: Tuesday, 20 January 2015 10:45 pm > >>>> > >>>> To: Allen Efienokwu >> > >>>> > >>>> Cc: "rdo-list at redhat.com " > >>>> > >>>> > > >>>> > >>>> Subject: Re: [Rdo-list] RDO > >>>> > >>>> > >>>> What?s the error you are getting? Also please note you may get a lot > >>>> > >>>> more help if you write to https://ask.openstack.org as it receives > much > >>>> > >>>> more traffic/people. > >>>> > >>>> > >>>> ? > >>>> > >>>> Sent from Mailbox > >>>> > >>>> > >>>> > >>>> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu < > niyiallen at gmail.com > >>>> > >>>> > wrote: > >>>> > >>>> > >>>> *Hello all,* > >>>> > >>>> > >>>> > >>>> ** > >>>> > >>>> > >>>> *Below is the steps I use to install OpenStack on Ubuntu and it > >>>> > >>>> never worked for me. It started well and in Step 1 but got stocked > >>>> > >>>> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. > >>>> > >>>> Please help me out. Thanks > >>>> > >>>> * > >>>> > >>>> > >>>> > >>>> ** > >>>> > >>>> > >>>> > >>>> ** > >>>> > >>>> > >>>> > >>>> Step 1: Software repositories > >>>> > >>>> > >>>> sudo yum update -y > >>>> > >>>> > >>>> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm > >>>> > >>>> > >>>> > >>>> Step 2: Install Packstack Installer > >>>> > >>>> > >>>> sudo yum install -y openstack-packstack > >>>> > >>>> > >>>> > >>>> Step 3: Run Packstack to install OpenStack > >>>> > >>>> > >>>> Packstack takes the work out of manually setting up OpenStack. For > a > >>>> > >>>> single node OpenStack deployment, run the following command. > >>>> > >>>> > >>>> packstack --allinone > >>>> > >>>> > >>>> * > >>>> > >>>> * > >>>> > >>>> > >>>> * > >>>> > >>>> * > >>>> > >>>> > >>>> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* > >>>> > >>>> > >>>> * > >>>> > >>>> * > >>>> > >>>> > >>>> *OpenStack for ubuntu > >>>> > >>>> > >>>> # sudo apt-get update > >>>> > >>>> > >>>> # sudo apt-get install git > >>>> > >>>> > >>>> # git clone ** > https://www.github.com/openstack-dev/devstack.git**-b > >>>> > >>>> stable/juno > >>>> > >>>> > >>>> # ls > >>>> > >>>> > >>>> # cd devstack > >>>> > >>>> > >>>> # ls > >>>> > >>>> > >>>> # sudo apt-get install vim > >>>> > >>>> > >>>> # apt-get installl libvirt-bin > >>>> > >>>> > >>>> # sudo vim stackrc > >>>> > >>>> under "Base GIT Repo URL > >>>> > >>>> add '**https://www.github.com* * > >>>> > >>>> > >>>> # under /devstack directory > >>>> > >>>> # ls > >>>> > >>>> # ./stack.sh* > >>>> > >>>> > >>>> *Allen Efienokwu > >>>> > >>>> And we know that all things work together as fitting into a plan > for > >>>> > >>>> us who love God and have been called according to his > purpose-Rm8:28 > >>>> > >>>> * > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> > >>>> Rdo-list mailing list > >>>> > >>>> Rdo-list at redhat.com > >>>> > >>>> https://www.redhat.com/mailman/listinfo/rdo-list > >>>> > >>>> > >>> > >>> > >>> -- > >>> Rich Bowen - rbowen at rcbowen.com - @rbowen > >>> http://apachecon.com/ - @apachecon > >> > >> > >> _______________________________________________ > >> Rdo-list mailing list > >> Rdo-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/rdo-list > >> > > > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yogesh_modii at yahoo.com Tue Jan 20 17:38:12 2015 From: yogesh_modii at yahoo.com (Yogesh Modi) Date: Tue, 20 Jan 2015 23:08:12 +0530 Subject: [Rdo-list] RDO In-Reply-To: References: <1421765130519.6a3fcfe@Nodemailer> <54BE6C12.9030009@rcbowen.com> <43FDF06F-E4B9-4EE4-B216-4A2CEF71E185@cloudfx.com> Message-ID: I don't know how i got subscribed to this, please unsubscribe me or stop sending me emails. Thanks! Sent from my iPhone > On 20-Jan-2015, at 11:02 pm, Mohit Davra wrote: > > Please don't send me mail > >> On Tuesday, January 20, 2015, Jason Harris wrote: >> Same with me. I don't know how I got on here, and I can't unsubscribe. >> >>> On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala wrote: >>> Cannot send emails to that dl >>> >>> Regards, Mohammed Sabuwala >>> Director, CloudFX Group >>> +6591140021 | www.cloudfx.com >>> >>> >>> On 20 Jan 2015, at 10:54 pm, Rich Bowen wrote: >>> >>>> >>>> >>>>> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: >>>>> I am not sure if I am the intended recipient, can someone remove off >>>>> this list please. >>>> >>>> >>>> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com >>>> >>>> --Rich >>>> >>>> >>>> >>>>> *Best Regards,* >>>>> ** >>>>> *Mohammed Sabuwala* >>>>> *Director, CloudFX Group* >>>>> *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 >>>>> *E-mail:*Mohammed.Sabuwala at CloudFX.com >>>>> | *Website:* www.CloudFX.com >>>>> >>>>> *CloudConsult:* www.cloudfxconsult.com >>>>> *CloudSelect:* www.cloudselect.com >>>>> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, >>>>> #04-05, Singapore, 239519 >>>>> slide1_logo.png >>>>> http://www.cloudfx.com/images/social_icons/twitter.png >>>>> http://www.cloudfx.com/images/social_icons/linkedin.png >>>>> http://www.cloudfx.com/images/social_icons/facebook.png >>>>> >>>>> From: Tom?s Olivares > >>>>> Date: Tuesday, 20 January 2015 10:45 pm >>>>> To: Allen Efienokwu > >>>>> Cc: "rdo-list at redhat.com " >>>>> > >>>>> Subject: Re: [Rdo-list] RDO >>>>> What?s the error you are getting? Also please note you may get a lot >>>>> more help if you write to https://ask.openstack.org as it receives much >>>>> more traffic/people. >>>>> ? >>>>> Sent from Mailbox >>>>> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu >>>> > wrote: >>>>> *Hello all,* >>>>> ** >>>>> *Below is the steps I use to install OpenStack on Ubuntu and it >>>>> never worked for me. It started well and in Step 1 but got stocked >>>>> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. >>>>> Please help me out. Thanks >>>>> * >>>>> ** >>>>> ** >>>>> Step 1: Software repositories >>>>> sudo yum update -y >>>>> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm >>>>> Step 2: Install Packstack Installer >>>>> sudo yum install -y openstack-packstack >>>>> Step 3: Run Packstack to install OpenStack >>>>> Packstack takes the work out of manually setting up OpenStack. For a >>>>> single node OpenStack deployment, run the following command. >>>>> packstack --allinone >>>>> * >>>>> * >>>>> * >>>>> * >>>>> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* >>>>> * >>>>> * >>>>> *OpenStack for ubuntu >>>>> # sudo apt-get update >>>>> # sudo apt-get install git >>>>> # git clone **https://www.github.com/openstack-dev/devstack.git**-b >>>>> stable/juno >>>>> # ls >>>>> # cd devstack >>>>> # ls >>>>> # sudo apt-get install vim >>>>> # apt-get installl libvirt-bin >>>>> # sudo vim stackrc >>>>> under "Base GIT Repo URL >>>>> add '**https://www.github.com* * >>>>> # under /devstack directory >>>>> # ls >>>>> # ./stack.sh* >>>>> *Allen Efienokwu >>>>> And we know that all things work together as fitting into a plan for >>>>> us who love God and have been called according to his purpose-Rm8:28 >>>>> * >>>>> _______________________________________________ >>>>> Rdo-list mailing list >>>>> Rdo-list at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>> >>>> >>>> -- >>>> Rich Bowen - rbowen at rcbowen.com - @rbowen >>>> http://apachecon.com/ - @apachecon >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From tolivares at gmail.com Tue Jan 20 17:40:08 2015 From: tolivares at gmail.com (=?UTF-8?Q?Tom=C3=A1s?= Olivares) Date: Tue, 20 Jan 2015 09:40:08 -0800 (PST) Subject: [Rdo-list] RDO In-Reply-To: References: Message-ID: <1421775608101.e9d8e3fe@Nodemailer> People, please unsubscribe in the following link: http://www.redhat.com/mailman/options/rdo-list Just put your email address and done! You are ?spamming? everyone instead of just going to that link.? Thanks. ? Sent from Mailbox On Tue, Jan 20, 2015 at 2:38 PM, Ramdas Khatake wrote: > Pls don't send me mail > On Jan 20, 2015 10:55 PM, "Adam Fyfe" wrote: >> It's an invasion ..... >> >> I shall invoice red hat $25 for every email received by me from now >> >> >> On 20 Jan 2015 17:21, "Jason Harris" wrote: >> > >> > Same with me. I don't know how I got on here, and I can't unsubscribe. >> > >> > On Tue, Jan 20, 2015 at 8:55 AM, Mohammed Sabuwala < >> mohammed.sabuwala at cloudfx.com> wrote: >> >> >> >> Cannot send emails to that dl >> >> >> >> Regards, Mohammed Sabuwala >> >> Director, CloudFX Group >> >> +6591140021 | www.cloudfx.com >> >> >> >> >> >> On 20 Jan 2015, at 10:54 pm, Rich Bowen wrote: >> >> >> >>> >> >>> >> >>> On 01/20/2015 09:49 AM, Mohammed Sabuwala wrote: >> >>>> >> >>>> I am not sure if I am the intended recipient, can someone remove off >> >>>> >> >>>> this list please. >> >>>> >> >>>> >> >>> >> >>> >> >>> To unsubscribe, send mail to rdo-list-unbsubscribe at redhat.com >> >>> >> >>> --Rich >> >>> >> >>> >> >>> >> >>>> >> >>>> *Best Regards,* >> >>>> >> >>>> >> >>>> ** >> >>>> >> >>>> >> >>>> *Mohammed Sabuwala* >> >>>> >> >>>> >> >>>> *Director, CloudFX Group* >> >>>> >> >>>> >> >>>> *Main Line: *+65 6733 9886* | Mobile:* +65 9114 0021 >> >>>> >> >>>> >> >>>> *E-mail:*Mohammed.Sabuwala at CloudFX.com >> >>>> >> >>>> | *Website:* www.CloudFX.com >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> *CloudConsult:* www.cloudfxconsult.com < >> http://www.cloudfxconsult.com/> >> >>>> >> >>>> *CloudSelect:* www.cloudselect.com >> >>>> >> >>>> >> >>>> CloudFX Pte Ltd, Singapore HQ, Winsland House I, 3 Killiney Road, >> >>>> >> >>>> #04-05, Singapore, 239519 >> >>>> >> >>>> >> >>>> slide1_logo.png >> >>>> >> >>>> >> http://www.cloudfx.com/images/social_icons/twitter.png >> >>>> >> >>>> >> http://www.cloudfx.com/images/social_icons/linkedin.png >> >>>> >> >>>> < >> http://www.linkedin.com/company/cloudfx-pte-ltd?trk=hb_tab_compy_id_2665577 >> >http://www.cloudfx.com/images/social_icons/facebook.png >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> From: Tom?s Olivares > >> >> >>>> >> >>>> Date: Tuesday, 20 January 2015 10:45 pm >> >>>> >> >>>> To: Allen Efienokwu > >> >> >>>> >> >>>> Cc: "rdo-list at redhat.com " >> >>>> >> >>>> > >> >>>> >> >>>> Subject: Re: [Rdo-list] RDO >> >>>> >> >>>> >> >>>> What?s the error you are getting? Also please note you may get a lot >> >>>> >> >>>> more help if you write to https://ask.openstack.org as it receives >> much >> >>>> >> >>>> more traffic/people. >> >>>> >> >>>> >> >>>> ? >> >>>> >> >>>> Sent from Mailbox >> >>>> >> >>>> >> >>>> >> >>>> On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu < >> niyiallen at gmail.com >> >>>> >> >>>> > wrote: >> >>>> >> >>>> >> >>>> *Hello all,* >> >>>> >> >>>> >> >>>> >> >>>> ** >> >>>> >> >>>> >> >>>> *Below is the steps I use to install OpenStack on Ubuntu and it >> >>>> >> >>>> never worked for me. It started well and in Step 1 but got stocked >> >>>> >> >>>> in Step2. I also tried in Fedora and CentOS. Got stock in step 2. >> >>>> >> >>>> Please help me out. Thanks >> >>>> >> >>>> * >> >>>> >> >>>> >> >>>> >> >>>> ** >> >>>> >> >>>> >> >>>> >> >>>> ** >> >>>> >> >>>> >> >>>> >> >>>> Step 1: Software repositories >> >>>> >> >>>> >> >>>> sudo yum update -y >> >>>> >> >>>> >> >>>> sudo yum install -yhttps://rdo.fedorapeople.org/rdo-release.rpm >> >>>> >> >>>> >> >>>> >> >>>> Step 2: Install Packstack Installer >> >>>> >> >>>> >> >>>> sudo yum install -y openstack-packstack >> >>>> >> >>>> >> >>>> >> >>>> Step 3: Run Packstack to install OpenStack >> >>>> >> >>>> >> >>>> Packstack takes the work out of manually setting up OpenStack. For >> a >> >>>> >> >>>> single node OpenStack deployment, run the following command. >> >>>> >> >>>> >> >>>> packstack --allinone >> >>>> >> >>>> >> >>>> * >> >>>> >> >>>> * >> >>>> >> >>>> >> >>>> * >> >>>> >> >>>> * >> >>>> >> >>>> >> >>>> *OpenStack {Ubuntu 14.04 LTS} Installation Steps* >> >>>> >> >>>> >> >>>> * >> >>>> >> >>>> * >> >>>> >> >>>> >> >>>> *OpenStack for ubuntu >> >>>> >> >>>> >> >>>> # sudo apt-get update >> >>>> >> >>>> >> >>>> # sudo apt-get install git >> >>>> >> >>>> >> >>>> # git clone ** >> https://www.github.com/openstack-dev/devstack.git**-b >> >>>> >> >>>> stable/juno >> >>>> >> >>>> >> >>>> # ls >> >>>> >> >>>> >> >>>> # cd devstack >> >>>> >> >>>> >> >>>> # ls >> >>>> >> >>>> >> >>>> # sudo apt-get install vim >> >>>> >> >>>> >> >>>> # apt-get installl libvirt-bin >> >>>> >> >>>> >> >>>> # sudo vim stackrc >> >>>> >> >>>> under "Base GIT Repo URL >> >>>> >> >>>> add '**https://www.github.com* * >> >>>> >> >>>> >> >>>> # under /devstack directory >> >>>> >> >>>> # ls >> >>>> >> >>>> # ./stack.sh* >> >>>> >> >>>> >> >>>> *Allen Efienokwu >> >>>> >> >>>> And we know that all things work together as fitting into a plan >> for >> >>>> >> >>>> us who love God and have been called according to his >> purpose-Rm8:28 >> >>>> >> >>>> * >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> >> >>>> Rdo-list mailing list >> >>>> >> >>>> Rdo-list at redhat.com >> >>>> >> >>>> https://www.redhat.com/mailman/listinfo/rdo-list >> >>>> >> >>>> >> >>> >> >>> >> >>> -- >> >>> Rich Bowen - rbowen at rcbowen.com - @rbowen >> >>> http://apachecon.com/ - @apachecon >> >> >> >> >> >> _______________________________________________ >> >> Rdo-list mailing list >> >> Rdo-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> > >> > >> > _______________________________________________ >> > Rdo-list mailing list >> > Rdo-list at redhat.com >> > https://www.redhat.com/mailman/listinfo/rdo-list >> > >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Tue Jan 20 17:39:18 2015 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 20 Jan 2015 12:39:18 -0500 Subject: [Rdo-list] Unsubscribe requests Message-ID: <54BE92C6.5000208@redhat.com> I'm not sure what has happened, but I'm getting a large number of people suddenly contacting me saying that they didn't intend to subscribe. To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, if you prefer, simply respond directly to me (not to the list) and let me know that you'd like to be removed, and I'll take care of it. I'm terribly sorry for the inconvenience. --Rich -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From Kevin.Bush at nexusis.com Tue Jan 20 17:50:19 2015 From: Kevin.Bush at nexusis.com (Bush, Kevin) Date: Tue, 20 Jan 2015 17:50:19 +0000 Subject: [Rdo-list] RDO In-Reply-To: <1421765130519.6a3fcfe@Nodemailer> References: <1421765130519.6a3fcfe@Nodemailer> Message-ID: I have ran into the same issues when using packstack on Fedora. I am interested to see how this is resolved. Thanks for the email! From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Tom?s Olivares Sent: Tuesday, January 20, 2015 9:46 AM To: Allen Efienokwu Cc: rdo-list at redhat.com Subject: Re: [Rdo-list] RDO What?s the error you are getting? Also please note you may get a lot more help if you write to https://ask.openstack.org as it receives much more traffic/people. ? Sent from Mailbox On Tue, Jan 20, 2015 at 11:38 AM, Allen Efienokwu > wrote: Hello all, Below is the steps I use to install OpenStack on Ubuntu and it never worked for me. It started well and in Step 1 but got stocked in Step2. I also tried in Fedora and CentOS. Got stock in step 2. Please help me out. Thanks Step 1: Software repositories sudo yum update -y sudo yum install -y https://rdo.fedorapeople.org/rdo-release.rpm Step 2: Install Packstack Installer sudo yum install -y openstack-packstack Step 3: Run Packstack to install OpenStack Packstack takes the work out of manually setting up OpenStack. For a single node OpenStack deployment, run the following command. packstack --allinone OpenStack {Ubuntu 14.04 LTS} Installation Steps OpenStack for ubuntu # sudo apt-get update # sudo apt-get install git # git clone https://www.github.com/openstack-dev/devstack.git -b stable/juno # ls # cd devstack # ls # sudo apt-get install vim # apt-get installl libvirt-bin # sudo vim stackrc under "Base GIT Repo URL add 'https://www.github.com # under /devstack directory # ls # ./stack.sh Allen Efienokwu And we know that all things work together as fitting into a plan for us who love God and have been called according to his purpose-Rm8:28 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmyers at redhat.com Tue Jan 20 17:54:05 2015 From: pmyers at redhat.com (Perry Myers) Date: Tue, 20 Jan 2015 12:54:05 -0500 Subject: [Rdo-list] RDO In-Reply-To: <1421775608101.e9d8e3fe@Nodemailer> References: <1421775608101.e9d8e3fe@Nodemailer> Message-ID: <54BE963D.2030900@redhat.com> On 01/20/2015 12:40 PM, Tom?s Olivares wrote: > People, please unsubscribe in the following link: > > http://www.redhat.com/mailman/options/rdo-list > > Just put your email address and done! You are ?spamming? everyone > instead of just going to that link. We are investigating the issue with our mailing list administrators. It looks like perhaps people who are users on github are being mass-added using their github email addresses. In the meantime, we have changed mailing list subscriptions to require confirmation, hopefully this should prevent further people from being inadvertently added to the mailing list. To individually unsubscribe please use the url above. But, posting complaints to the list just exacerbates the problem for everyone else. Aside from traffic on this particular topic, this list tends to be very low traffic. So if folks who were added somehow by github can just unsubscribe via the url above, we can hopefully fix the issue. Perry From john.h.thompson at nasa.gov Tue Jan 20 18:02:16 2015 From: john.h.thompson at nasa.gov (Thompson, John H. (GSFC-606.2)[PATUXENT TECHNOLOGY PARTNERS]) Date: Tue, 20 Jan 2015 18:02:16 +0000 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: <54BE92C6.5000208@redhat.com> References: <54BE92C6.5000208@redhat.com> Message-ID: Please unsubscribe me Hoot at ptpnow.com John.h.thompson at nasa.gov THanks On 1/20/15 12:39 PM, "Rich Bowen" wrote: >I'm not sure what has happened, but I'm getting a large number of people >suddenly contacting me saying that they didn't intend to subscribe. > >To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, >if you prefer, simply respond directly to me (not to the list) and let >me know that you'd like to be removed, and I'll take care of it. > >I'm terribly sorry for the inconvenience. > >--Rich > >-- >Rich Bowen - rbowen at redhat.com >OpenStack Community Liaison >http://openstack.redhat.com/ > >_______________________________________________ >Rdo-list mailing list >Rdo-list at redhat.com >https://www.redhat.com/mailman/listinfo/rdo-list From mewald at evoila.de Tue Jan 20 18:39:39 2015 From: mewald at evoila.de (Mathias Ewald) Date: Tue, 20 Jan 2015 19:39:39 +0100 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> Message-ID: <54BEA0EB.6090206@evoila.de> Me too please. I have no idea how I landed here. On 20.01.2015 19:02, Thompson, John H. (GSFC-606.2)[PATUXENT TECHNOLOGY PARTNERS] wrote: > Please unsubscribe me > > > Hoot at ptpnow.com > John.h.thompson at nasa.gov > > > THanks > > On 1/20/15 12:39 PM, "Rich Bowen" wrote: > >> I'm not sure what has happened, but I'm getting a large number of people >> suddenly contacting me saying that they didn't intend to subscribe. >> >> To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, >> if you prefer, simply respond directly to me (not to the list) and let >> me know that you'd like to be removed, and I'll take care of it. >> >> I'm terribly sorry for the inconvenience. >> >> --Rich >> >> -- >> Rich Bowen - rbowen at redhat.com >> OpenStack Community Liaison >> http://openstack.redhat.com/ >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From pmyers at redhat.com Tue Jan 20 19:34:16 2015 From: pmyers at redhat.com (Perry Myers) Date: Tue, 20 Jan 2015 14:34:16 -0500 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: <54BEA0EB.6090206@evoila.de> References: <54BE92C6.5000208@redhat.com> <54BEA0EB.6090206@evoila.de> Message-ID: <54BEADB8.1050709@redhat.com> On 01/20/2015 01:39 PM, Mathias Ewald wrote: > Me too please. I have no idea how I landed here. Hi, please don't email the list to ask to be unsubscribed or to complain about being inadvertently subscribed. There appears to have been either a hack or some sort of error and that caused many people to be subscribed when they should not have. Please read: https://www.redhat.com/archives/rdo-list/2015-January/msg00141.html As I said in that email, replying to the list with "Me too! Me too!" just exacerbates the problem for everyone else. So, please, refrain from replying to the threads with that. :) We're trying to work on figuring out the root cause here, so we can correct the situation and mass-unsubscribe everyone that was accidentally subscribed. Apologies for the issue, more information will be provided as we get it. Perry From mohammed.arafa at gmail.com Tue Jan 20 20:38:59 2015 From: mohammed.arafa at gmail.com (Mohammed Arafa) Date: Tue, 20 Jan 2015 15:38:59 -0500 Subject: [Rdo-list] staypuft distribution list Message-ID: hello does staypuft have its own distribution list or does it use this one? thanks -- *805010942448935* *GR750055912MA* *Link to me on LinkedIn * -------------- next part -------------- An HTML attachment was scrubbed... URL: From misu124 at gmail.com Tue Jan 20 22:09:46 2015 From: misu124 at gmail.com (=?UTF-8?Q?Miroslav_Such=C3=BD?=) Date: Tue, 20 Jan 2015 23:09:46 +0100 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: <54BE92C6.5000208@redhat.com> References: <54BE92C6.5000208@redhat.com> Message-ID: I used this email when registering to https://ask.openstack.org/en/questions/ Can it be that everybody registered there have been subscribed to rdo mailing list by some error? Miroslav 2015-01-20 18:39 GMT+01:00 Rich Bowen : > I'm not sure what has happened, but I'm getting a large number of people > suddenly contacting me saying that they didn't intend to subscribe. > > To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, > if you prefer, simply respond directly to me (not to the list) and let me > know that you'd like to be removed, and I'll take care of it. > > I'm terribly sorry for the inconvenience. > > --Rich > > -- > Rich Bowen - rbowen at redhat.com > OpenStack Community Liaison > http://openstack.redhat.com/ > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Tue Jan 20 22:15:33 2015 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 20 Jan 2015 17:15:33 -0500 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> Message-ID: <54BED385.3020706@redhat.com> On 01/20/2015 05:09 PM, Miroslav Such? wrote: > I used this email when registering to > https://ask.openstack.org/en/questions/ > Can it be that everybody registered there have been subscribed to rdo > mailing list by some error? I don't think that could happen, since that's a completely separate site, run by a completely separate organization. > > Miroslav > > 2015-01-20 18:39 GMT+01:00 Rich Bowen >: > > I'm not sure what has happened, but I'm getting a large number of > people suddenly contacting me saying that they didn't intend to > subscribe. > > To unsubscribe, please send email to > rdo-list-unsubscribe at redhat.__com > or, if you prefer, simply > respond directly to me (not to the list) and let me know that you'd > like to be removed, and I'll take care of it. > > I'm terribly sorry for the inconvenience. > -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From ihrachys at redhat.com Wed Jan 21 13:27:03 2015 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Wed, 21 Jan 2015 14:27:03 +0100 Subject: [Rdo-list] Can't delete network from neutron In-Reply-To: <54B7EE61.9000104@ebi.ac.uk> References: <54B7DED8.7000700@ebi.ac.uk> <54B7EE61.9000104@ebi.ac.uk> Message-ID: <54BFA927.8080308@redhat.com> Hi David, Your issue is very interesting. I thought port cleanup was fixed with: https://review.openstack.org/#/c/127357/ And the fix is included in Juno. It would be interesting to see whether there are any routers in your database, and whether there are any objects in 'routerports' table (those are expected to be purged once a router is deleted). If you need help in identifying commands that are needed to get the needed info, please tell me. Thanks, /Ihar On 01/15/2015 05:44 PM, David Ocana wrote: > Hi Rushi, > > Thanks for the quick reply. Actually the router was removed before > trying to delete the subnet , and I tried removing it all first from > the UI but as I coudln't, I started using the neutron commands. > > I think there is still some trace of the relationship between the port > and the router and that may be the reason why I can't delete it, but > that's my guess > > # neutron port-show e5d4effb-6a67-4f90-ad2c-01dca00c9e42 > +-----------------------+------------------------------------------------------------------------------------+ > > | Field | Value | > +-----------------------+------------------------------------------------------------------------------------+ > > | admin_state_up | False | > | allowed_address_pairs | | > | binding:host_id | intcl01-hyp02.ebi.ac.uk | > | binding:profile | {} | > | binding:vif_details | {"port_filter": true, "ovs_hybrid_plug": > true} | > | binding:vif_type | ovs | > | binding:vnic_type | normal | > | device_id | e5057310-02a0-447c-ab77-4528e821cd84 | > | device_owner | network:router_interface | (this one here) > | extra_dhcp_opts | | > | fixed_ips | {"subnet_id": > "329476b1-7ea7-41e5-a357-445b143086fe", "ip_address": "192.168.1.1"} | > | id | e5d4effb-6a67-4f90-ad2c-01dca00c9e42 | > | mac_address | fa:16:3e:ff:ee:1d | > | name | to_delete | > | network_id | 9a427447-3f9f-4dc5-94f8-bc273a7e7cf0 | > | security_groups | | > | status | DOWN | > | tenant_id | beea649440944f8ab232c0f8cf84d54d | > +-----------------------+------------------------------------------------------------------------------------+ > > > Cheers, > David > > On 15/01/15 15:51, Ns, Rushi wrote: >> You need remove router and interface then remove subnet as well >> others, you can do all these on dashboard with user admin, please >> remove router first . Let me know. >> >> BR, >> Rushi >> Sent from my iPhone >> please excuse typos and brevity >> >>> On Jan 15, 2015, at 7:42 AM, David Ocana wrote: >>> >>> Hi everyone, >>> >>> I installed juno rdo and I was playing with it until I got stuck >>> trying to delete a private network. I have been googling around I >>> found possible reasons but none of the solutions worked for me. >>> >>> Here is what I did: >>> >>> # neutron net-delete 9a427447-3f9f-4dc5-94f8-bc273a7e7cf0 >>> Conflict (HTTP 409) (Request-ID: >>> req-d1c79aaa-25f4-40cf-91c4-fde63d54708a) >>> >>> So I thought I had to delete the subnet first: >>> >>> # neutron subnet-delete 329476b1-7ea7-41e5-a357-445b143086fe >>> Conflict (HTTP 409) (Request-ID: >>> req-7ff81f34-10ee-4eb1-b3f0-ebbc7283af4e) >>> >>> Then I checked if there were any ports for this subnet: >>> >>> # neutron port-list | grep 329 >>> | e5d4effb-6a67-4f90-ad2c-01dca00c9e42 | | fa:16:3e:ff:ee:1d | >>> {"subnet_id": "329476b1-7ea7-41e5-a357-445b143086fe", "ip_address": >>> "192.168.1.1"} | >>> >>> Then I tried to delete the port but I get the same: >>> >>> # neutron port-delete e5d4effb-6a67-4f90-ad2c-01dca00c9e42 >>> Conflict (HTTP 409) (Request-ID: >>> req-6e8789f4-cd92-46fb-9ff4-db14faeb6503) >>> >>> I tried disabling the port first but it didn't work either. Tenant >>> is brand new, has no instances, no volumes, nothing besides the >>> network. >>> >>> Any ideas? >>> >>> Thanks, >>> David >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From rdo-info at redhat.com Wed Jan 21 15:56:42 2015 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 21 Jan 2015 15:56:42 +0000 Subject: [Rdo-list] [RDO] Creation of Sahara-Compatible HDP 2.0 Images on RHEL 6.6 Message-ID: <0000014b0d35c3d6-78fba0c0-0919-414b-ba8d-2792c1034959-000000@email.amazonses.com> egafford started a discussion. Creation of Sahara-Compatible HDP 2.0 Images on RHEL 6.6 --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/999/creation-of-sahara-compatible-hdp-2-0-images-on-rhel-6-6 Have a great day! From hguemar at fedoraproject.org Wed Jan 21 16:29:33 2015 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Wed, 21 Jan 2015 17:29:33 +0100 Subject: [Rdo-list] [meeting] RDO Packaging meeting minutes (2015-01-14) Message-ID: This is an (imperfect) retranscription of today's call. ======================================== #rdo: RDO Packaging meeting (2015-01-21) ======================================== Meeting started by number80 at 14:59:53 UTC. The full logs are available at http://meetbot.fedoraproject.org/rdo/2015-01-21/rdo.2015-01-21-14.59.log.html . Meeting summary --------------- * agenda is here: https://etherpad.openstack.org/p/RDO-Packaging (number80, 15:05:19) * Review RDO packaging guidelines (number80, 15:08:27) * discussion about relaxing some fedora packaging guidelines (number80, 15:09:04) * bundling is an issue with various packages (ie: puppetdb, opendaylight) (number80, 15:10:20) * we need to track security issues anyway in bundled code (number80, 15:10:44) * discussion about dist-git (keeping with dist-git or moving to github) (number80, 15:14:12) * apevec suggests using delorean repositories (number80, 15:15:49) * Update on Fedora/CentOS dist-git licensing/contributor agreement (number80, 15:17:01) * Fedora Legal requires signing FPCA (number80, 15:17:46) * ACTION: Rich will ask directly Red Hat Legal about that matter (number80, 15:18:10) * Mailing-list issue (number80, 15:20:39) * Rich is following this issue with Red Hat IT (number80, 15:21:12) * LINK: http://meetbot.fedoraproject.org/rdo/2015-01-14/rdo.2015-01-14-15.00.log.html (apevec, 15:21:26) * LINK: http://meetbot.fedoraproject.org/rdo/2015-01-14/rdo.2015-01-14-15.00.html (apevec, 15:22:25) * ACTION: Rich will follow up on DNS record creation for delorean.rdoproject.org (rbowen, 15:22:34) * follow-up with last week actions (number80, 15:22:57) * slinabery eggmaster has started revising internal RH doc on rdopkg CI overview for consumption on list. Not ready to email public yet. (eggmaster, 15:24:53) Meeting ended at 15:27:55 UTC. Action Items ------------ * Rich will ask directly Red Hat Legal about that matter * Rich will follow up on DNS record creation for delorean.rdoproject.org Action Items, by person ----------------------- * **UNASSIGNED** * Rich will ask directly Red Hat Legal about that matter * Rich will follow up on DNS record creation for delorean.rdoproject.org People Present (lines said) --------------------------- * number80 (34) * apevec (10) * rbowen (7) * zodbot (4) * ryansb (3) * kashyap (3) * eggmaster (3) * gchamoul (3) * weshay_mtg (2) * pmyers (2) * chandankumar (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From ihrachys at redhat.com Wed Jan 21 16:35:18 2015 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Wed, 21 Jan 2015 17:35:18 +0100 Subject: [Rdo-list] [meeting] RDO Packaging meeting minutes (2015-01-14) In-Reply-To: References: Message-ID: <54BFD546.8040608@redhat.com> Hi, Why don't we have those meetings held in irc, as in upstream projects? It's hard to understand anything that was decided from those irc logs attached. I think it would be better to have proper logs collected. /Ihar On 01/21/2015 05:29 PM, Ha?kel wrote: > This is an (imperfect) retranscription of today's call. > > ======================================== > #rdo: RDO Packaging meeting (2015-01-21) > ======================================== > > > Meeting started by number80 at 14:59:53 UTC. The full logs are available > at > http://meetbot.fedoraproject.org/rdo/2015-01-21/rdo.2015-01-21-14.59.log.html > . > > > > Meeting summary > --------------- > * agenda is here: https://etherpad.openstack.org/p/RDO-Packaging > (number80, 15:05:19) > * Review RDO packaging guidelines (number80, 15:08:27) > * discussion about relaxing some fedora packaging guidelines > (number80, 15:09:04) > * bundling is an issue with various packages (ie: puppetdb, > opendaylight) (number80, 15:10:20) > * we need to track security issues anyway in bundled code (number80, > 15:10:44) > * discussion about dist-git (keeping with dist-git or moving to > github) (number80, 15:14:12) > * apevec suggests using delorean repositories (number80, 15:15:49) > > * Update on Fedora/CentOS dist-git licensing/contributor agreement > (number80, 15:17:01) > * Fedora Legal requires signing FPCA (number80, 15:17:46) > * ACTION: Rich will ask directly Red Hat Legal about that matter > (number80, 15:18:10) > > * Mailing-list issue (number80, 15:20:39) > * Rich is following this issue with Red Hat IT (number80, 15:21:12) > * LINK: > http://meetbot.fedoraproject.org/rdo/2015-01-14/rdo.2015-01-14-15.00.log.html > (apevec, 15:21:26) > * LINK: > http://meetbot.fedoraproject.org/rdo/2015-01-14/rdo.2015-01-14-15.00.html > (apevec, 15:22:25) > * ACTION: Rich will follow up on DNS record creation for > delorean.rdoproject.org (rbowen, 15:22:34) > > * follow-up with last week actions (number80, 15:22:57) > * slinabery eggmaster has started revising internal RH doc on rdopkg > CI overview for consumption on list. Not ready to email public yet. > (eggmaster, 15:24:53) > > Meeting ended at 15:27:55 UTC. > > > > > Action Items > ------------ > * Rich will ask directly Red Hat Legal about that matter > * Rich will follow up on DNS record creation for delorean.rdoproject.org > > > > > Action Items, by person > ----------------------- > * **UNASSIGNED** > * Rich will ask directly Red Hat Legal about that matter > * Rich will follow up on DNS record creation for > delorean.rdoproject.org > > > > > People Present (lines said) > --------------------------- > * number80 (34) > * apevec (10) > * rbowen (7) > * zodbot (4) > * ryansb (3) > * kashyap (3) > * eggmaster (3) > * gchamoul (3) > * weshay_mtg (2) > * pmyers (2) > * chandankumar (1) > > > > > Generated by `MeetBot`_ 0.1.4 > > .. _`MeetBot`: http://wiki.debian.org/MeetBot > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From rbowen at redhat.com Wed Jan 21 17:02:40 2015 From: rbowen at redhat.com (Rich Bowen) Date: Wed, 21 Jan 2015 12:02:40 -0500 Subject: [Rdo-list] [meeting] RDO Packaging meeting minutes (2015-01-14) In-Reply-To: <54BFD546.8040608@redhat.com> References: <54BFD546.8040608@redhat.com> Message-ID: <54BFDBB0.8080206@redhat.com> On 01/21/2015 11:35 AM, Ihar Hrachyshka wrote: > Hi, > > Why don't we have those meetings held in irc, as in upstream projects? > > It's hard to understand anything that was decided from those irc logs > attached. I think it would be better to have proper logs collected. +1 The detail that was in the voice call and is missing from the transcript makes the meeting minutes confusing. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From apevec at gmail.com Wed Jan 21 17:21:50 2015 From: apevec at gmail.com (Alan Pevec) Date: Wed, 21 Jan 2015 18:21:50 +0100 Subject: [Rdo-list] [meeting] RDO Packaging meeting minutes (2015-01-14) In-Reply-To: <54BFDBB0.8080206@redhat.com> References: <54BFD546.8040608@redhat.com> <54BFDBB0.8080206@redhat.com> Message-ID: >> Why don't we have those meetings held in irc, as in upstream projects? So the idea was to have it on IRC in parallel for keeping notes with meetbot but that didn't work well. >> It's hard to understand anything that was decided from those irc logs >> attached. I think it would be better to have proper logs collected. > > +1 > > The detail that was in the voice call and is missing from the transcript > makes the meeting minutes confusing. After quick post-mortem on #rdo I propose we keep weekly meetings IRC only. BJ meeting will stay open for high-bandwidth meeting when needed to discuss important/urgent issues. Cheers, Alan From mysterious.samudrala at gmail.com Thu Jan 22 04:27:24 2015 From: mysterious.samudrala at gmail.com (Samudrala Prasad) Date: Thu, 22 Jan 2015 09:57:24 +0530 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> Message-ID: HI Rich, Please unsubscribe me from this mailing list.... I am getting lot of mails which I am not intended to receive. Regards, Samudrala On Tue, Jan 20, 2015 at 11:32 PM, Thompson, John H. (GSFC-606.2)[PATUXENT TECHNOLOGY PARTNERS] wrote: > Please unsubscribe me > > > Hoot at ptpnow.com > John.h.thompson at nasa.gov > > > THanks > > On 1/20/15 12:39 PM, "Rich Bowen" wrote: > > >I'm not sure what has happened, but I'm getting a large number of people > >suddenly contacting me saying that they didn't intend to subscribe. > > > >To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, > >if you prefer, simply respond directly to me (not to the list) and let > >me know that you'd like to be removed, and I'll take care of it. > > > >I'm terribly sorry for the inconvenience. > > > >--Rich > > > >-- > >Rich Bowen - rbowen at redhat.com > >OpenStack Community Liaison > >http://openstack.redhat.com/ > > > >_______________________________________________ > >Rdo-list mailing list > >Rdo-list at redhat.com > >https://www.redhat.com/mailman/listinfo/rdo-list > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From martim at martimramos.pt Thu Jan 22 04:35:00 2015 From: martim at martimramos.pt (Martim Ramos) Date: Thu, 22 Jan 2015 04:35:00 +0000 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> Message-ID: me too Enviado da minha iBimby, ?The moment you doubt whether you can fly, you cease for ever to be able to do it.? ? J.M. Barrie , *Peter Pan * *Martim Ramos /|\* *E-mail:* martim at martimramos.pt *Skype: *martim_ramos On Thu, Jan 22, 2015 at 4:27 AM, Samudrala Prasad < mysterious.samudrala at gmail.com> wrote: > HI Rich, > > Please unsubscribe me from this mailing list.... > I am getting lot of mails which I am not intended to receive. > > Regards, > Samudrala > > On Tue, Jan 20, 2015 at 11:32 PM, Thompson, John H. (GSFC-606.2)[PATUXENT > TECHNOLOGY PARTNERS] wrote: > >> Please unsubscribe me >> >> >> Hoot at ptpnow.com >> John.h.thompson at nasa.gov >> >> >> THanks >> >> On 1/20/15 12:39 PM, "Rich Bowen" wrote: >> >> >I'm not sure what has happened, but I'm getting a large number of people >> >suddenly contacting me saying that they didn't intend to subscribe. >> > >> >To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, >> >if you prefer, simply respond directly to me (not to the list) and let >> >me know that you'd like to be removed, and I'll take care of it. >> > >> >I'm terribly sorry for the inconvenience. >> > >> >--Rich >> > >> >-- >> >Rich Bowen - rbowen at redhat.com >> >OpenStack Community Liaison >> >http://openstack.redhat.com/ >> > >> >_______________________________________________ >> >Rdo-list mailing list >> >Rdo-list at redhat.com >> >https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From venu.murthy at thoughtworks.com Thu Jan 22 04:41:06 2015 From: venu.murthy at thoughtworks.com (Venu Murthy) Date: Thu, 22 Jan 2015 10:11:06 +0530 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> Message-ID: Same here, not sure how I got added to this mailing group. Best regards, Venu [image: ThoughtWorks] --- *?Excellence is never an accident. It is always the result of high intention, sincere effort, and intelligent execution.... ? Aristotle* On Thu, Jan 22, 2015 at 9:57 AM, Samudrala Prasad < mysterious.samudrala at gmail.com> wrote: > HI Rich, > > Please unsubscribe me from this mailing list.... > I am getting lot of mails which I am not intended to receive. > > Regards, > Samudrala > > On Tue, Jan 20, 2015 at 11:32 PM, Thompson, John H. (GSFC-606.2)[PATUXENT > TECHNOLOGY PARTNERS] wrote: > >> Please unsubscribe me >> >> >> Hoot at ptpnow.com >> John.h.thompson at nasa.gov >> >> >> THanks >> >> On 1/20/15 12:39 PM, "Rich Bowen" wrote: >> >> >I'm not sure what has happened, but I'm getting a large number of people >> >suddenly contacting me saying that they didn't intend to subscribe. >> > >> >To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, >> >if you prefer, simply respond directly to me (not to the list) and let >> >me know that you'd like to be removed, and I'll take care of it. >> > >> >I'm terribly sorry for the inconvenience. >> > >> >--Rich >> > >> >-- >> >Rich Bowen - rbowen at redhat.com >> >OpenStack Community Liaison >> >http://openstack.redhat.com/ >> > >> >_______________________________________________ >> >Rdo-list mailing list >> >Rdo-list at redhat.com >> >https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bhavinpatel323 at yahoo.com Thu Jan 22 04:44:58 2015 From: bhavinpatel323 at yahoo.com (bhavin Patel) Date: Wed, 21 Jan 2015 20:44:58 -0800 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: Message-ID: <1421901898.40461.YahooMailAndroidMobile@web140603.mail.bf1.yahoo.com> All please remove me? from this contact group Sent from Yahoo Mail on Android -------------- next part -------------- An HTML attachment was scrubbed... URL: From venu.murthy at thoughtworks.com Thu Jan 22 09:12:14 2015 From: venu.murthy at thoughtworks.com (Venu Murthy) Date: Thu, 22 Jan 2015 14:42:14 +0530 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: <20150122081739.GH12638@tesla.redhat.com> References: <54BE92C6.5000208@redhat.com> <20150122081739.GH12638@tesla.redhat.com> Message-ID: This mail was rather rude Kashyap, and I would have expected a little more considerate reply, because it is your company that is at fault here. Why is it so much a trouble for you go ahead and investigate and remove all those IDs that were added in by mistake? Or update all on what has been done so far? Btw when we go to unsubscribe it asks for a password, and then we have to do a password reset and so on to unsubscribe from a mailing list, that we've never subscribed to and I don't even know how my email id has landed up with your company. That's another can of worms to investigate I suppose, or is that too my fault. Best regards, Venu [image: ThoughtWorks] --- *?Excellence is never an accident. It is always the result of high intention, sincere effort, and intelligent execution.... ? Aristotle* On Thu, Jan 22, 2015 at 1:47 PM, Kashyap Chamarthy wrote: > On Thu, Jan 22, 2015 at 10:11:06AM +0530, Venu Murthy wrote: > > Same here, not sure how I got added to this mailing group. > > Please do NOT email to the list. If you paid any attention, it was > already repeated multiple times that it's accidental and is being > investigated > > Just go this URL and click "Unsuscribe" > > http://www.redhat.com/mailman/options/rdo-list > > These "me too, me too" emails just spam the list even more. > > https://www.redhat.com/archives/rdo-list/2015-January/msg00141.html > > Thanks for your understanding! > > -- > /kashyap > > > > On Thu, Jan 22, 2015 at 9:57 AM, Samudrala Prasad < > > mysterious.samudrala at gmail.com> wrote: > > > > > HI Rich, > > > > > > Please unsubscribe me from this mailing list.... > > > I am getting lot of mails which I am not intended to receive. > > > > > > Regards, > > > Samudrala > > > > > > On Tue, Jan 20, 2015 at 11:32 PM, Thompson, John H. > (GSFC-606.2)[PATUXENT > > > TECHNOLOGY PARTNERS] wrote: > > > > > >> Please unsubscribe me > > >> > > >> > > >> Hoot at ptpnow.com > > >> John.h.thompson at nasa.gov > > >> > > >> > > >> THanks > > >> > > >> On 1/20/15 12:39 PM, "Rich Bowen" wrote: > > >> > > >> >I'm not sure what has happened, but I'm getting a large number of > people > > >> >suddenly contacting me saying that they didn't intend to subscribe. > > >> > > > >> >To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com > or, > > >> >if you prefer, simply respond directly to me (not to the list) and > let > > >> >me know that you'd like to be removed, and I'll take care of it. > > >> > > > >> >I'm terribly sorry for the inconvenience. > > >> > > > >> >--Rich > > >> > > > >> >-- > > >> >Rich Bowen - rbowen at redhat.com > > >> >OpenStack Community Liaison > > >> >http://openstack.redhat.com/ > > >> > > > >> >_______________________________________________ > > >> >Rdo-list mailing list > > >> >Rdo-list at redhat.com > > >> >https://www.redhat.com/mailman/listinfo/rdo-list > > >> > > >> > > >> _______________________________________________ > > >> Rdo-list mailing list > > >> Rdo-list at redhat.com > > >> https://www.redhat.com/mailman/listinfo/rdo-list > > >> > > > > > > > > > _______________________________________________ > > > Rdo-list mailing list > > > Rdo-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > To unsubscribe: rdo-list-unsubscribe at redhat.com > > > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > To unsubscribe: rdo-list-unsubscribe at redhat.com > > > -- > /kashyap > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kchamart at redhat.com Thu Jan 22 09:42:39 2015 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Thu, 22 Jan 2015 10:42:39 +0100 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> <20150122081739.GH12638@tesla.redhat.com> Message-ID: <20150122094239.GI12638@tesla.redhat.com> On Thu, Jan 22, 2015 at 02:42:14PM +0530, Venu Murthy wrote: > This mail was rather rude Kashyap, and I would have expected a little more > considerate reply, Hmm, you're right. maybe it's the sheer volume of email I deal with that prompted me with that tone. Sorry about that, didn't mean any malice there. > because it is your company that is at fault here. I don't really agree. Red Hat is not at _fault_. It's a community mailing list, and why would a fair-playing community open source project want to mass-subscribe people thoso who didn't intend to? > Why is it so much a trouble for you go ahead and investigate and remove all > those IDs that were added in by mistake? Or update all on what has been > done so far? Venu, as you can imagine, that's exactly the intention. There was even a publicly recorded IRC meeting last evening (doesn't imply everyone needs to keep an eye on it) to update the community mailing list (as the info arrives) and mass-unsubscribe those didn't intend to. The news is still: Mailing list infrastructure team is investigating in a systematic manner to identify the root cause. > Btw when we go to unsubscribe it asks for a password, I think you're looking at the wrong place, unsubscribing doesn't need any password. Here's the correct procedure: Second section on this page is where you see "Unsubscribe" http://www.redhat.com/mailman/options/rdo-list and it clearly says: "By clicking on the Unsubscribe button, a confirmation message will be emailed to you. This message will have a link that you should click on to complete the removal process (you can also confirm by email; see the instructions in the confirmation message)." > and then we have to do a password reset and so on to unsubscribe from > a mailing list, that we've never subscribed to and I don't even know > how my email id has landed up with your company. That's another can of > worms to investigate I suppose, or is that too my fault. It's a community mailing list adminstered publicly. On the surface, it appears to be a crack that unfortunately mass-subscribed a bunch of people that didn't intend to. Most community mailing lists go through something like this at some point in time. Blaming won't get us anywhere, some patience is appreciated. Hope you agree there. Again, this was not intended by the RDO project, sorry about that. -- /kashyap From berendt at b1-systems.de Thu Jan 22 09:50:25 2015 From: berendt at b1-systems.de (Christian Berendt) Date: Thu, 22 Jan 2015 10:50:25 +0100 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: <20150122094239.GI12638@tesla.redhat.com> References: <54BE92C6.5000208@redhat.com> <20150122081739.GH12638@tesla.redhat.com> <20150122094239.GI12638@tesla.redhat.com> Message-ID: <54C0C7E1.7010808@b1-systems.de> On 01/22/2015 10:42 AM, Kashyap Chamarthy wrote: > I think you're looking at the wrong place, unsubscribing doesn't need > any password. Here's the correct procedure: Second section on this page > is where you see "Unsubscribe" Simply sending a mail to rdo-list-unsubscribe at redhat.com should work as well. Christian. -- Christian Berendt Cloud Solution Architect Mail: berendt at b1-systems.de B1 Systems GmbH Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 From lionel.bartlett at gmail.com Thu Jan 22 10:00:57 2015 From: lionel.bartlett at gmail.com (Lionel Bartlett) Date: Thu, 22 Jan 2015 21:00:57 +1100 (EST) Subject: [Rdo-list] Unsubscribe requests In-Reply-To: <54BE92C6.5000208@redhat.com> Message-ID: <28545426.43.1421920852114.JavaMail.Notebook1@Notebook1-PC> Rich, This email business is a huge mess. Can you guys not kill the list and have people re-subscribe? I don't even know why RH have my details, I don't use RH. Or are people replaying to all? What about all the millions of new virus opportunities this is generating... I do not want the entire RH community to have my email address! Thanks Lionel ----- Original Message ----- From: "Rich Bowen" To: rdo-list at redhat.com Sent: Wednesday, 21 January, 2015 4:39:18 AM Subject: [Rdo-list] Unsubscribe requests I'm not sure what has happened, but I'm getting a large number of people suddenly contacting me saying that they didn't intend to subscribe. To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, if you prefer, simply respond directly to me (not to the list) and let me know that you'd like to be removed, and I'll take care of it. I'm terribly sorry for the inconvenience. --Rich -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list From tolivares at gmail.com Thu Jan 22 13:33:20 2015 From: tolivares at gmail.com (=?UTF-8?Q?Tom=C3=A1s?= Olivares) Date: Thu, 22 Jan 2015 05:33:20 -0800 (PST) Subject: [Rdo-list] Massive Un-Subscriptions? Message-ID: <1421933600359.277d5a7f@Nodemailer> Looks like I was unsubscribed to the list somehow. Maybe it has to do with the issue we were having a couple of days ago? Anyways, I just re-subscribed but wanted to know if everyone got the same email. Good to be back though :) ? Sent from Mailbox -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Thu Jan 22 13:42:09 2015 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 22 Jan 2015 08:42:09 -0500 Subject: [Rdo-list] Massive Un-Subscriptions? In-Reply-To: <1421933600359.277d5a7f@Nodemailer> References: <1421933600359.277d5a7f@Nodemailer> Message-ID: <54C0FE31.9020007@redhat.com> On 01/22/2015 08:33 AM, Tom?s Olivares wrote: > Looks like I was unsubscribed to the list somehow. Maybe it has to do > with the issue we were having a couple of days ago? Anyways, I just > re-subscribed but wanted to know if everyone got the same email. > > Good to be back though :) Once again, we're very sorry for the noise and the inconvenience. It appears that the addresses were subscribed in error, and they have all been removed, along with, apparently, a few false positives into the batch. We're still investigating how that happened, so that we can ensure that it doesn't happen again, but for now, the unsubscribe noise should be ended. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From pmyers at redhat.com Thu Jan 22 14:02:30 2015 From: pmyers at redhat.com (Perry Myers) Date: Thu, 22 Jan 2015 09:02:30 -0500 Subject: [Rdo-list] Massive Un-Subscriptions? In-Reply-To: <54C0FE31.9020007@redhat.com> References: <1421933600359.277d5a7f@Nodemailer> <54C0FE31.9020007@redhat.com> Message-ID: <54C102F6.7020708@redhat.com> On 01/22/2015 08:42 AM, Rich Bowen wrote: > > > On 01/22/2015 08:33 AM, Tom?s Olivares wrote: >> Looks like I was unsubscribed to the list somehow. Maybe it has to do >> with the issue we were having a couple of days ago? Anyways, I just >> re-subscribed but wanted to know if everyone got the same email. >> >> Good to be back though :) > > Once again, we're very sorry for the noise and the inconvenience. It > appears that the addresses were subscribed in error, and they have all > been removed, along with, apparently, a few false positives into the batch. > > We're still investigating how that happened, so that we can ensure that > it doesn't happen again, but for now, the unsubscribe noise should be > ended. Thanks Rich. For transparency, I was the one who did the mass unsubscribe of about 1100 email addresses. I got a list of emails from our IT department of folks that were added in a single transaction on Jan 19th. Unfortunately, I couldn't differentiate between folks that were added that day in that transaction vs. folks who were already on the list previously and were re-added by that transaction. So, unfortunately, as Rich mentions, there were a few people removed who should not have been. Hopefully all of those folks just resubscribe quickly, and then we'll be back to normal :) Cheers, Perry From tolivares at gmail.com Thu Jan 22 14:03:49 2015 From: tolivares at gmail.com (=?UTF-8?Q?Tom=C3=A1s?= Olivares) Date: Thu, 22 Jan 2015 06:03:49 -0800 (PST) Subject: [Rdo-list] Massive Un-Subscriptions? In-Reply-To: <54C102F6.7020708@redhat.com> References: <54C102F6.7020708@redhat.com> Message-ID: <1421935428538.3d1f42@Nodemailer> Understood. Thanks for the hard work to both of you guys. People makes mistakes so it?s all good here :) ? Sent from Mailbox On Thu, Jan 22, 2015 at 11:02 AM, Perry Myers wrote: > On 01/22/2015 08:42 AM, Rich Bowen wrote: >> >> >> On 01/22/2015 08:33 AM, Tom?s Olivares wrote: >>> Looks like I was unsubscribed to the list somehow. Maybe it has to do >>> with the issue we were having a couple of days ago? Anyways, I just >>> re-subscribed but wanted to know if everyone got the same email. >>> >>> Good to be back though :) >> >> Once again, we're very sorry for the noise and the inconvenience. It >> appears that the addresses were subscribed in error, and they have all >> been removed, along with, apparently, a few false positives into the batch. >> >> We're still investigating how that happened, so that we can ensure that >> it doesn't happen again, but for now, the unsubscribe noise should be >> ended. > Thanks Rich. > For transparency, I was the one who did the mass unsubscribe of about > 1100 email addresses. > I got a list of emails from our IT department of folks that were added > in a single transaction on Jan 19th. Unfortunately, I couldn't > differentiate between folks that were added that day in that transaction > vs. folks who were already on the list previously and were re-added by > that transaction. > So, unfortunately, as Rich mentions, there were a few people removed who > should not have been. Hopefully all of those folks just resubscribe > quickly, and then we'll be back to normal :) > Cheers, > Perry -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michael.Feldpusch at Level3.com Thu Jan 22 14:57:16 2015 From: Michael.Feldpusch at Level3.com (Feldpusch, Michael) Date: Thu, 22 Jan 2015 14:57:16 +0000 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> Message-ID: Please unsubscribe me from this list From: Samudrala Prasad > Date: Wednesday, January 21, 2015 at 9:27 PM To: "Thompson, John H. (GSFC-606.2)[PATUXENT TECHNOLOGY PARTNERS]" > Cc: "rdo-list at redhat.com" > Subject: Re: [Rdo-list] Unsubscribe requests HI Rich, Please unsubscribe me from this mailing list.... I am getting lot of mails which I am not intended to receive. Regards, Samudrala On Tue, Jan 20, 2015 at 11:32 PM, Thompson, John H. (GSFC-606.2)[PATUXENT TECHNOLOGY PARTNERS] > wrote: Please unsubscribe me Hoot at ptpnow.com John.h.thompson at nasa.gov THanks On 1/20/15 12:39 PM, "Rich Bowen" > wrote: >I'm not sure what has happened, but I'm getting a large number of people >suddenly contacting me saying that they didn't intend to subscribe. > >To unsubscribe, please send email to rdo-list-unsubscribe at redhat.com or, >if you prefer, simply respond directly to me (not to the list) and let >me know that you'd like to be removed, and I'll take care of it. > >I'm terribly sorry for the inconvenience. > >--Rich > >-- >Rich Bowen - rbowen at redhat.com >OpenStack Community Liaison >http://openstack.redhat.com/ > >_______________________________________________ >Rdo-list mailing list >Rdo-list at redhat.com >https://www.redhat.com/mailman/listinfo/rdo-list _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list From rbowen at redhat.com Thu Jan 22 15:18:30 2015 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 22 Jan 2015 10:18:30 -0500 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: <54B550ED.6050201@redhat.com> References: <54B38988.5080601@cern.ch> <54B550ED.6050201@redhat.com> Message-ID: <54C114C6.4080207@redhat.com> On 01/13/2015 12:07 PM, Rich Bowen wrote: > > > On 01/12/2015 03:44 AM, Thomas Oulevey wrote: >> Hi David, >> >> We have a lot of interest in the Juno for el6 packages at CERN. >> >> It would be great if you can share the patches and we can work together >> to build it in a central way. >> >> What is your approach in the current patchset ? rebuild python 2.7 or >> patch openstack to work with python 2.6 ? >> >> I am working as well with the CentOS team. I am part of the team that >> maintain the build system >> (http://wiki.centos.org/HowTos/CommunityBuildSystem). RDO started to >> rebuild their packages with this system for the cloud SIG effort >> (http://wiki.centos.org/SpecialInterestGroup/Cloud). I'll let Rich or >> someone more involved in the cloud sig to comment on this effort as I >> have not all latest details/plan. > > > It's really great to have you all step up to do this, and we want to > help in any way we can getting you started. > > The packaging docs are at https://openstack.redhat.com/packaging/ and > hopefully that's enough to get started, but we acknowledge that it's a > work in progress and needs help. > > If there's anything you need, or anyone's attention you're having > trouble getting, please ping me and I'll be glad to help make things > happen. > > Will you be at FOSDEM? Hey, David, Thomas, et al, I wonder if you've had any chance to look at this, and whether you need anything to get started. As you may have seen, we're having a weekly Cloud SIG meeting on #centos-devel (on Freenode) every Thursday at 15:00 UTC, and there's also a bi-weekly RDO packaging meeting, every other Wednesday, also at 15:00 UTC, on #rdo. If there's anything we can do to help you, please let us know -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From pmyers at redhat.com Thu Jan 22 15:25:13 2015 From: pmyers at redhat.com (Perry Myers) Date: Thu, 22 Jan 2015 10:25:13 -0500 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> Message-ID: <54C11659.6000604@redhat.com> On 01/22/2015 09:57 AM, Feldpusch, Michael wrote: > Please unsubscribe me from this list You're not subscribed to the list. I just checked. Did you perhaps not read the note I sent this morning about this (to the list, in fact) https://www.redhat.com/archives/rdo-list/2015-January/msg00164.html Ah, maybe you didn't get it, since you've already been unsubscribed from the list as of this morning... From dneedles at gmail.com Thu Jan 22 17:32:52 2015 From: dneedles at gmail.com (Daniel L. Needles) Date: Thu, 22 Jan 2015 09:32:52 -0800 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: <20150122094239.GI12638@tesla.redhat.com> References: <54BE92C6.5000208@redhat.com> <20150122081739.GH12638@tesla.redhat.com> <20150122094239.GI12638@tesla.redhat.com> Message-ID: <09ea01d03669$735cec40$5a16c4c0$@com> And 100 emails later, it is clear that the majority of folks "perceive" they forcibly subscribed to this list.. >>I don't really agree. Red Hat is not at _fault_. It's a community mailing list, and why would a >>fair-playing community open source project want to mass-subscribe people those who didn't intend to? So you want to be a Wall-Mart, the low price leader - not Nordstrom's? The customer relationship is not one transaction. When I recommend systems to my fortune 500 clients, government agencies, and military projects what will stick in my mind is the 100 emails and Red Hat doesn't give a crap what I want only what it can get away with in this case. This didn't work so well for Toyota when they doubled production and breaks stuck and they also said - not our fault, not happening. And it didn't work too well for Starbucks when they stuck their coffee in gas stations. Redhat went from A to B in my book. HP, SUSE and other OpenStack solutions are feeling better at this point. I guess I will burn time, jump through your hoops, to correct your mistake, if it was a mistake. Good luck with the "screw you customer" strategy. That won't work in the USA. We tend to be brand loyal except when loyalty isn't returned. Thanks, DANIEL L. NEEDLES Principal Consultant NMSGuru, Inc. -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Kashyap Chamarthy Sent: Thursday, January 22, 2015 1:43 AM To: Venu Murthy Cc: rdo-list at redhat.com Subject: Re: [Rdo-list] Unsubscribe requests On Thu, Jan 22, 2015 at 02:42:14PM +0530, Venu Murthy wrote: > This mail was rather rude Kashyap, and I would have expected a little > more considerate reply, Hmm, you're right. maybe it's the sheer volume of email I deal with that prompted me with that tone. Sorry about that, didn't mean any malice there. > because it is your company that is at fault here. I don't really agree. Red Hat is not at _fault_. It's a community mailing list, and why would a fair-playing community open source project want to mass-subscribe people thoso who didn't intend to? > Why is it so much a trouble for you go ahead and investigate and > remove all those IDs that were added in by mistake? Or update all on > what has been done so far? Venu, as you can imagine, that's exactly the intention. There was even a publicly recorded IRC meeting last evening (doesn't imply everyone needs to keep an eye on it) to update the community mailing list (as the info arrives) and mass-unsubscribe those didn't intend to. The news is still: Mailing list infrastructure team is investigating in a systematic manner to identify the root cause. > Btw when we go to unsubscribe it asks for a password, I think you're looking at the wrong place, unsubscribing doesn't need any password. Here's the correct procedure: Second section on this page is where you see "Unsubscribe" http://www.redhat.com/mailman/options/rdo-list and it clearly says: "By clicking on the Unsubscribe button, a confirmation message will be emailed to you. This message will have a link that you should click on to complete the removal process (you can also confirm by email; see the instructions in the confirmation message)." > and then we have to do a password reset and so on to unsubscribe from > a mailing list, that we've never subscribed to and I don't even know > how my email id has landed up with your company. That's another can of > worms to investigate I suppose, or is that too my fault. It's a community mailing list adminstered publicly. On the surface, it appears to be a crack that unfortunately mass-subscribed a bunch of people that didn't intend to. Most community mailing lists go through something like this at some point in time. Blaming won't get us anywhere, some patience is appreciated. Hope you agree there. Again, this was not intended by the RDO project, sorry about that. -- /kashyap _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe at redhat.com ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5645 / Virus Database: 4260/8933 - Release Date: 01/15/15 Internal Virus Database is out of date. From hguemar at fedoraproject.org Thu Jan 22 17:42:08 2015 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Thu, 22 Jan 2015 18:42:08 +0100 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: <54C114C6.4080207@redhat.com> References: <54B38988.5080601@cern.ch> <54B550ED.6050201@redhat.com> <54C114C6.4080207@redhat.com> Message-ID: 2015-01-22 16:18 GMT+01:00 Rich Bowen : > > > Hey, David, Thomas, et al, > > I wonder if you've had any chance to look at this, and whether you need > anything to get started. As you may have seen, we're having a weekly Cloud > SIG meeting on #centos-devel (on Freenode) every Thursday at 15:00 UTC, and > there's also a bi-weekly RDO packaging meeting, every other Wednesday, also > at 15:00 UTC, on #rdo. > small correction, it's now weekly (reminders will be sent to this list two days before). > If there's anything we can do to help you, please let us know > As for packaging-related topic feel free to reach me out, I'm more than happy to help you get started. H. > > -- > Rich Bowen - rbowen at redhat.com > OpenStack Community Liaison > http://openstack.redhat.com/ > From tolivares at gmail.com Thu Jan 22 18:01:00 2015 From: tolivares at gmail.com (Tomas Olivares) Date: Thu, 22 Jan 2015 18:01:00 +0000 Subject: [Rdo-list] Unsubscribe requests References: <54BE92C6.5000208@redhat.com> <20150122081739.GH12638@tesla.redhat.com> <20150122094239.GI12638@tesla.redhat.com> <09ea01d03669$735cec40$5a16c4c0$@com> Message-ID: >> And 100 emails later, it is clear that the majority of folks "perceive" they >> forcibly subscribed to this list.. Note that Perry already said it was some sort of error. They are not trying to convince people otherwise: https://www.redhat.com/archives/rdo-list/2015-January/msg00144.html >>So you want to be a Wall-Mart, the low price leader - not Nordstrom's >>The customer relationship is not one transaction. When I recommend >>systems to my fortune 500 clients, government agencies, and military >>projects what will stick in my mind is the 100 emails and Red Hat >>doesn't give a crap what I want only what it can get away with in this case. It's been said numerous times they are looking into the problem. I'm not sure where you are seeing this "doesn't give a crap" strategy. IMO, it's your "perception" and that's fine. >>This didn't work so well for Toyota when they doubled production and >>breaks stuck and they also said - not our fault, not happening. And it >>didn't work too well for Starbucks when they stuck their coffee in gas >>stations. Redhat went from A to B in my book. HP, SUSE and other >>OpenStack solutions are feeling better at this point. So you are blaming Red Hat for a mailing list issue and will be giving advice to customers based on it? Not on the fact that your customers need the best quality product? And I'm not saying it has to be Red Hat, but it could've been SUSE, HP, or any other. You're mixing concepts again. >>I guess I will burn time, jump through your hoops, to correct your >>mistake, if it was a mistake. Good luck with the "screw you customer" >>strategy. That won't work in the USA. We tend to be brand loyal except >>when loyalty isn't returned. Once again, community vs Red Hat is a very different label. And the "screw you Red Hat due to a mistake" isn't the best approach either. Cheers, PS: I'm removing the cc to customerservice at redhat.com as it has absolutely no business to do with this issue. On Thu Jan 22 2015 at 2:34:51 PM Daniel L. Needles wrote: > And 100 emails later, it is clear that the majority of folks "perceive" > they > forcibly subscribed to this list.. > > >>I don't really agree. Red Hat is not at _fault_. It's a community mailing > list, and why would a > >>fair-playing community open source project want to mass-subscribe people > those who didn't intend to? > > So you want to be a Wall-Mart, the low price leader - not Nordstrom's? The > customer relationship is not one transaction. When I recommend systems to > my > fortune 500 clients, government agencies, and military projects what will > stick in my mind is the 100 emails and Red Hat doesn't give a crap what I > want only what it can get away with in this case. > > This didn't work so well for Toyota when they doubled production and breaks > stuck and they also said - not our fault, not happening. And it didn't work > too well for Starbucks when they stuck their coffee in gas stations. > Redhat > went from A to B in my book. HP, SUSE and other OpenStack solutions are > feeling better at this point. > > I guess I will burn time, jump through your hoops, to correct your mistake, > if it was a mistake. Good luck with the "screw you customer" strategy. That > won't work in the USA. We tend to be brand loyal except when loyalty isn't > returned. > > Thanks, > DANIEL L. NEEDLES > Principal Consultant > NMSGuru, Inc. > > > > > -----Original Message----- > From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On > Behalf Of Kashyap Chamarthy > Sent: Thursday, January 22, 2015 1:43 AM > To: Venu Murthy > Cc: rdo-list at redhat.com > Subject: Re: [Rdo-list] Unsubscribe requests > > On Thu, Jan 22, 2015 at 02:42:14PM +0530, Venu Murthy wrote: > > This mail was rather rude Kashyap, and I would have expected a little > > more considerate reply, > > Hmm, you're right. maybe it's the sheer volume of email I deal with that > prompted me with that tone. Sorry about that, didn't mean any malice there. > > > because it is your company that is at fault here. > > I don't really agree. Red Hat is not at _fault_. It's a community mailing > list, and why would a fair-playing community open source project want to > mass-subscribe people thoso who didn't intend to? > > > Why is it so much a trouble for you go ahead and investigate and > > remove all those IDs that were added in by mistake? Or update all on > > what has been done so far? > > Venu, as you can imagine, that's exactly the intention. There was even a > publicly recorded IRC meeting last evening (doesn't imply everyone needs to > keep an eye on it) to update the community mailing list (as the info > arrives) and mass-unsubscribe those didn't intend to. > > The news is still: Mailing list infrastructure team is investigating in a > systematic manner to identify the root cause. > > > Btw when we go to unsubscribe it asks for a password, > > I think you're looking at the wrong place, unsubscribing doesn't need any > password. Here's the correct procedure: Second section on this page is > where > you see "Unsubscribe" > > http://www.redhat.com/mailman/options/rdo-list > > and it clearly says: > > "By clicking on the Unsubscribe button, a confirmation message will > be emailed to you. This message will have a link that you should > click on to complete the removal process (you can also confirm by > email; see the instructions in the confirmation message)." > > > and then we have to do a password reset and so on to unsubscribe from > > a mailing list, that we've never subscribed to and I don't even know > > how my email id has landed up with your company. That's another can of > > worms to investigate I suppose, or is that too my fault. > > It's a community mailing list adminstered publicly. On the surface, it > appears to be a crack that unfortunately mass-subscribed a bunch of people > that didn't intend to. > > Most community mailing lists go through something like this at some point > in > time. Blaming won't get us anywhere, some patience is appreciated. Hope you > agree there. > > Again, this was not intended by the RDO project, sorry about that. > > -- > /kashyap > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2015.0.5645 / Virus Database: 4260/8933 - Release Date: 01/15/15 > Internal Virus Database is out of date. > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dneedles at gmail.com Thu Jan 22 18:04:19 2015 From: dneedles at gmail.com (Daniel L. Needles) Date: Thu, 22 Jan 2015 10:04:19 -0800 Subject: [Rdo-list] Unsubscribe requests In-Reply-To: References: <54BE92C6.5000208@redhat.com> <20150122081739.GH12638@tesla.redhat.com> <20150122094239.GI12638@tesla.redhat.com> <09ea01d03669$735cec40$5a16c4c0$@com> Message-ID: <0a6b01d0366d$d84637c0$88d2a740$@com> We are in violent agreement. RedHat doesn't give a crap about its brand perception. If it did, it would understand why Customer Service is the issue AND would want to mend the "emotions" rather than argue with the customer. Good luck with that. http://www.nmsguru.com/DanNeedles.jpg DANIEL L. NEEDLES Principal Consultant NMSGuru, Inc. 512.627.6694 guru at nmsguru.com http://www.nmsguru.com/TerminalConnectionBanner.png http://www.nmsguru.com/EMAIL/LinkedIn-high-detail-32.png http://www.nmsguru.com/EMAIL/Facebook-high-detail-32.png http://www.nmsguru.com/EMAIL/Twitter-high-detail-32.png From: Tomas Olivares [mailto:tolivares at gmail.com] Sent: Thursday, January 22, 2015 10:01 AM To: Daniel L. Needles; Kashyap Chamarthy; Venu Murthy Cc: customerservice at redhat.com; rdo-list at redhat.com Subject: Re: [Rdo-list] Unsubscribe requests >> And 100 emails later, it is clear that the majority of folks "perceive" they >> forcibly subscribed to this list.. Note that Perry already said it was some sort of error. They are not trying to convince people otherwise: https://www.redhat.com/archives/rdo-list/2015-January/msg00144.html >>So you want to be a Wall-Mart, the low price leader - not Nordstrom's >>The customer relationship is not one transaction. When I recommend >>systems to my fortune 500 clients, government agencies, and military >>projects what will stick in my mind is the 100 emails and Red Hat >>doesn't give a crap what I want only what it can get away with in this case. It's been said numerous times they are looking into the problem. I'm not sure where you are seeing this "doesn't give a crap" strategy. IMO, it's your "perception" and that's fine. >>This didn't work so well for Toyota when they doubled production and >>breaks stuck and they also said - not our fault, not happening. And it >>didn't work too well for Starbucks when they stuck their coffee in gas >>stations. Redhat went from A to B in my book. HP, SUSE and other >>OpenStack solutions are feeling better at this point. So you are blaming Red Hat for a mailing list issue and will be giving advice to customers based on it? Not on the fact that your customers need the best quality product? And I'm not saying it has to be Red Hat, but it could've been SUSE, HP, or any other. You're mixing concepts again. >>I guess I will burn time, jump through your hoops, to correct your >>mistake, if it was a mistake. Good luck with the "screw you customer" >>strategy. That won't work in the USA. We tend to be brand loyal except >>when loyalty isn't returned. Once again, community vs Red Hat is a very different label. And the "screw you Red Hat due to a mistake" isn't the best approach either. Cheers, PS: I'm removing the cc to customerservice at redhat.com as it has absolutely no business to do with this issue. On Thu Jan 22 2015 at 2:34:51 PM Daniel L. Needles wrote: And 100 emails later, it is clear that the majority of folks "perceive" they forcibly subscribed to this list.. >>I don't really agree. Red Hat is not at _fault_. It's a community mailing list, and why would a >>fair-playing community open source project want to mass-subscribe people those who didn't intend to? So you want to be a Wall-Mart, the low price leader - not Nordstrom's? The customer relationship is not one transaction. When I recommend systems to my fortune 500 clients, government agencies, and military projects what will stick in my mind is the 100 emails and Red Hat doesn't give a crap what I want only what it can get away with in this case. This didn't work so well for Toyota when they doubled production and breaks stuck and they also said - not our fault, not happening. And it didn't work too well for Starbucks when they stuck their coffee in gas stations. Redhat went from A to B in my book. HP, SUSE and other OpenStack solutions are feeling better at this point. I guess I will burn time, jump through your hoops, to correct your mistake, if it was a mistake. Good luck with the "screw you customer" strategy. That won't work in the USA. We tend to be brand loyal except when loyalty isn't returned. Thanks, DANIEL L. NEEDLES Principal Consultant NMSGuru, Inc. -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Kashyap Chamarthy Sent: Thursday, January 22, 2015 1:43 AM To: Venu Murthy Cc: rdo-list at redhat.com Subject: Re: [Rdo-list] Unsubscribe requests On Thu, Jan 22, 2015 at 02:42:14PM +0530, Venu Murthy wrote: > This mail was rather rude Kashyap, and I would have expected a little > more considerate reply, Hmm, you're right. maybe it's the sheer volume of email I deal with that prompted me with that tone. Sorry about that, didn't mean any malice there. > because it is your company that is at fault here. I don't really agree. Red Hat is not at _fault_. It's a community mailing list, and why would a fair-playing community open source project want to mass-subscribe people thoso who didn't intend to? > Why is it so much a trouble for you go ahead and investigate and > remove all those IDs that were added in by mistake? Or update all on > what has been done so far? Venu, as you can imagine, that's exactly the intention. There was even a publicly recorded IRC meeting last evening (doesn't imply everyone needs to keep an eye on it) to update the community mailing list (as the info arrives) and mass-unsubscribe those didn't intend to. The news is still: Mailing list infrastructure team is investigating in a systematic manner to identify the root cause. > Btw when we go to unsubscribe it asks for a password, I think you're looking at the wrong place, unsubscribing doesn't need any password. Here's the correct procedure: Second section on this page is where you see "Unsubscribe" http://www.redhat.com/mailman/options/rdo-list and it clearly says: "By clicking on the Unsubscribe button, a confirmation message will be emailed to you. This message will have a link that you should click on to complete the removal process (you can also confirm by email; see the instructions in the confirmation message)." > and then we have to do a password reset and so on to unsubscribe from > a mailing list, that we've never subscribed to and I don't even know > how my email id has landed up with your company. That's another can of > worms to investigate I suppose, or is that too my fault. It's a community mailing list adminstered publicly. On the surface, it appears to be a crack that unfortunately mass-subscribed a bunch of people that didn't intend to. Most community mailing lists go through something like this at some point in time. Blaming won't get us anywhere, some patience is appreciated. Hope you agree there. Again, this was not intended by the RDO project, sorry about that. -- /kashyap _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe at redhat.com ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5645 / Virus Database: 4260/8933 - Release Date: 01/15/15 Internal Virus Database is out of date. _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe at redhat.com _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5645 / Virus Database: 4260/8933 - Release Date: 01/15/15 Internal Virus Database is out of date. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 2144 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 12067 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5270 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 5135 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 5314 bytes Desc: not available URL: From rbowen at rcbowen.com Thu Jan 22 18:22:03 2015 From: rbowen at rcbowen.com (Rich Bowen) Date: Thu, 22 Jan 2015 13:22:03 -0500 Subject: [Rdo-list] Mailing list incident, post mortem Message-ID: <54C13FCB.1000605@rcbowen.com> Thank you all for your patience over the last few days with the unsubscribe messages. I've been working with Red Hat infosec to figure out what happened, and I want to let you know what we found out, and allay your concerns. First of all, it appears that this incident was 100% my fault. It appears, from server logs, very clear that I pasted a list of email addresses into a subscribe form and pressed submit, or enter, or otherwise submitted the form. That I didn't do this intentionally, I hope you can believe, but, rather, that it happened in a moment of stupidity or absentmindedness of something. So, the good news is, it doesn't appear that the list was compromised in any way. What is not clear at this moment is where these email addresses came from, and how they got into my paste buffer, since some of them were familiar to me, and others were not. I'm still trying to find the common thread. With the help of Red Hat IT, we've identified the entire list of addresses, and unsubscribed them. There were, apparently some false positives in there, and some of those people have resubscribed. To them, again, I'm very sorry. -- Rich Bowen - rbowen at rcbowen.com - @rbowen http://apachecon.com/ - @apachecon From mohammed.arafa at gmail.com Thu Jan 22 19:33:26 2015 From: mohammed.arafa at gmail.com (Mohammed Arafa) Date: Thu, 22 Jan 2015 14:33:26 -0500 Subject: [Rdo-list] Mailing list incident, post mortem In-Reply-To: <54C13FCB.1000605@rcbowen.com> References: <54C13FCB.1000605@rcbowen.com> Message-ID: Rich Thank you for the RCA :) We are all human and all is forgiven Thanks On Thu, Jan 22, 2015 at 1:22 PM, Rich Bowen wrote: > Thank you all for your patience over the last few days with the > unsubscribe messages. I've been working with Red Hat infosec to figure out > what happened, and I want to let you know what we found out, and allay your > concerns. > > First of all, it appears that this incident was 100% my fault. It appears, > from server logs, very clear that I pasted a list of email addresses into a > subscribe form and pressed submit, or enter, or otherwise submitted the > form. > > That I didn't do this intentionally, I hope you can believe, but, rather, > that it happened in a moment of stupidity or absentmindedness of something. > > So, the good news is, it doesn't appear that the list was compromised in > any way. > > What is not clear at this moment is where these email addresses came from, > and how they got into my paste buffer, since some of them were familiar to > me, and others were not. I'm still trying to find the common thread. > > With the help of Red Hat IT, we've identified the entire list of > addresses, and unsubscribed them. There were, apparently some false > positives in there, and some of those people have resubscribed. To them, > again, I'm very sorry. > > -- > Rich Bowen - rbowen at rcbowen.com - @rbowen > http://apachecon.com/ - @apachecon > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -- *805010942448935* *GR750055912MA* *Link to me on LinkedIn * -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.oulevey at cern.ch Thu Jan 22 20:14:05 2015 From: thomas.oulevey at cern.ch (Thomas Oulevey) Date: Thu, 22 Jan 2015 21:14:05 +0100 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: <54C114C6.4080207@redhat.com> References: <54B38988.5080601@cern.ch> <54B550ED.6050201@redhat.com> <54C114C6.4080207@redhat.com> Message-ID: <54C15A0D.9080707@cern.ch> Hi All, > > Hey, David, Thomas, et al, > > I wonder if you've had any chance to look at this, and whether you need > anything to get started. As you may have seen, we're having a weekly > Cloud SIG meeting on #centos-devel (on Freenode) every Thursday at 15:00 > UTC, and there's also a bi-weekly RDO packaging meeting, every other > Wednesday, also at 15:00 UTC, on #rdo. I think it would be 2 different steps now : - Identify the patch that David already have. Contribute them to the list and review them. - In parallel I can assist to try to rebuild source RPMs, in cbs.centos.org. We have can test packages within a repo (unsigned) quickly to validate if something is wrong and then iterate. > > If there's anything we can do to help you, please let us know > It would be nice for each contributor to open a bugs.centos.org ticket, to request access to the building system, a Cloud SIG member could validate the account. Then I can do basic training :) -- Thomas. From xzhao at bnl.gov Fri Jan 23 16:10:35 2015 From: xzhao at bnl.gov (Zhao, Xin) Date: Fri, 23 Jan 2015 11:10:35 -0500 Subject: [Rdo-list] instances stuck in BUILD state Message-ID: <54C2727B.3010409@bnl.gov> Hello, I am having a problem with my icehouse testbed, which has one controller, one network node (OVS/VLAN) and ~50 compute nodes. It runs fine for some time, but then recently, only a small portion of new instances can start, most of the new instances are stuck in BUILD forever, without an IP assigned. The scheduler log shows the scheduler has chosen the compute node to start the instance, but the neutron server log shows no sign of allocating MAC/IP addresses for it, I suspect the neutron server didn't get the request for some reason. Any suggestions on how to debug this? Thanks, Xin From lars at redhat.com Fri Jan 23 16:26:33 2015 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Fri, 23 Jan 2015 11:26:33 -0500 Subject: [Rdo-list] instances stuck in BUILD state In-Reply-To: <54C2727B.3010409@bnl.gov> References: <54C2727B.3010409@bnl.gov> Message-ID: <20150123162633.GC23684@redhat.com> On Fri, Jan 23, 2015 at 11:10:35AM -0500, Zhao, Xin wrote: > without an IP assigned. The scheduler log shows the scheduler has chosen > the compute node to start the instance, but the neutron server log shows no > sign of allocating MAC/IP addresses for it, I suspect the neutron server > didn't get the request for some reason. > > Any suggestions on how to debug this? Are there any relevant errors in the nova-compute log on the target compute hosts? -- Lars Kellogg-Stedman | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From xzhao at bnl.gov Fri Jan 23 16:33:28 2015 From: xzhao at bnl.gov (Zhao, Xin) Date: Fri, 23 Jan 2015 11:33:28 -0500 Subject: [Rdo-list] instances stuck in BUILD state In-Reply-To: <20150123162633.GC23684@redhat.com> References: <54C2727B.3010409@bnl.gov> <20150123162633.GC23684@redhat.com> Message-ID: <54C277D8.6050701@bnl.gov> On 1/23/2015 11:26 AM, Lars Kellogg-Stedman wrote: > On Fri, Jan 23, 2015 at 11:10:35AM -0500, Zhao, Xin wrote: >> without an IP assigned. The scheduler log shows the scheduler has chosen >> the compute node to start the instance, but the neutron server log shows no >> sign of allocating MAC/IP addresses for it, I suspect the neutron server >> didn't get the request for some reason. >> >> Any suggestions on how to debug this? > Are there any relevant errors in the nova-compute log on the target > compute hosts? Nothing in the compute.log on the compute host. But, I don't have debug turned on there, I will turn it on and see if there are anything... Thanks, Xin From sdake at redhat.com Fri Jan 23 19:49:31 2015 From: sdake at redhat.com (Steven Dake) Date: Fri, 23 Jan 2015 12:49:31 -0700 Subject: [Rdo-list] instances stuck in BUILD state In-Reply-To: <54C277D8.6050701@bnl.gov> References: <54C2727B.3010409@bnl.gov> <20150123162633.GC23684@redhat.com> <54C277D8.6050701@bnl.gov> Message-ID: <54C2A5CB.2050302@redhat.com> On 01/23/2015 09:33 AM, Zhao, Xin wrote: > > On 1/23/2015 11:26 AM, Lars Kellogg-Stedman wrote: >> On Fri, Jan 23, 2015 at 11:10:35AM -0500, Zhao, Xin wrote: >>> without an IP assigned. The scheduler log shows the scheduler has >>> chosen >>> the compute node to start the instance, but the neutron server log >>> shows no >>> sign of allocating MAC/IP addresses for it, I suspect the neutron >>> server >>> didn't get the request for some reason. >>> >>> Any suggestions on how to debug this? >> Are there any relevant errors in the nova-compute log on the target >> compute hosts? > > Nothing in the compute.log on the compute host. But, I don't have > debug turned on there, I will turn it on and see if there are anything... > > Thanks, > Xin > Are you using qpid or rabbitmq? Does restarting either allow the rest of the compute services to proceed? (OpenStack will reconnect when you restart the amqp service). Regards -steve > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From xzhao at bnl.gov Fri Jan 23 20:19:49 2015 From: xzhao at bnl.gov (Zhao, Xin) Date: Fri, 23 Jan 2015 15:19:49 -0500 Subject: [Rdo-list] instances stuck in BUILD state In-Reply-To: <54C2A5CB.2050302@redhat.com> References: <54C2727B.3010409@bnl.gov> <20150123162633.GC23684@redhat.com> <54C277D8.6050701@bnl.gov> <54C2A5CB.2050302@redhat.com> Message-ID: <54C2ACE5.2050202@bnl.gov> On 1/23/2015 2:49 PM, Steven Dake wrote: > On 01/23/2015 09:33 AM, Zhao, Xin wrote: >> >> On 1/23/2015 11:26 AM, Lars Kellogg-Stedman wrote: >>> On Fri, Jan 23, 2015 at 11:10:35AM -0500, Zhao, Xin wrote: >>>> without an IP assigned. The scheduler log shows the scheduler has >>>> chosen >>>> the compute node to start the instance, but the neutron server log >>>> shows no >>>> sign of allocating MAC/IP addresses for it, I suspect the neutron >>>> server >>>> didn't get the request for some reason. >>>> >>>> Any suggestions on how to debug this? >>> Are there any relevant errors in the nova-compute log on the target >>> compute hosts? >> >> Nothing in the compute.log on the compute host. But, I don't have >> debug turned on there, I will turn it on and see if there are >> anything... >> >> Thanks, >> Xin >> > Are you using qpid or rabbitmq? Does restarting either allow the rest > of the compute services to proceed? (OpenStack will reconnect when > you restart the amqp service). > Yes I tried restarting rabbitmq, but that doesn't help. Thanks, Xin > Regards > -steve > >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com > From xzhao at bnl.gov Fri Jan 23 21:59:20 2015 From: xzhao at bnl.gov (Zhao, Xin) Date: Fri, 23 Jan 2015 16:59:20 -0500 Subject: [Rdo-list] instances stuck in BUILD state In-Reply-To: <54C2ACE5.2050202@bnl.gov> References: <54C2727B.3010409@bnl.gov> <20150123162633.GC23684@redhat.com> <54C277D8.6050701@bnl.gov> <54C2A5CB.2050302@redhat.com> <54C2ACE5.2050202@bnl.gov> Message-ID: <54C2C438.6060002@bnl.gov> Well, as I turn on debug mode and restart services (both nova-compute and neutron-ovs-agent) on the compute nodes, things get better, so far all new instances start fine. We will see how long this lasts ... Thanks, Xin On 1/23/2015 3:19 PM, Zhao, Xin wrote: > > On 1/23/2015 2:49 PM, Steven Dake wrote: >> On 01/23/2015 09:33 AM, Zhao, Xin wrote: >>> >>> On 1/23/2015 11:26 AM, Lars Kellogg-Stedman wrote: >>>> On Fri, Jan 23, 2015 at 11:10:35AM -0500, Zhao, Xin wrote: >>>>> without an IP assigned. The scheduler log shows the scheduler has >>>>> chosen >>>>> the compute node to start the instance, but the neutron server log >>>>> shows no >>>>> sign of allocating MAC/IP addresses for it, I suspect the neutron >>>>> server >>>>> didn't get the request for some reason. >>>>> >>>>> Any suggestions on how to debug this? >>>> Are there any relevant errors in the nova-compute log on the target >>>> compute hosts? >>> >>> Nothing in the compute.log on the compute host. But, I don't have >>> debug turned on there, I will turn it on and see if there are >>> anything... >>> >>> Thanks, >>> Xin >>> >> Are you using qpid or rabbitmq? Does restarting either allow the >> rest of the compute services to proceed? (OpenStack will reconnect >> when you restart the amqp service). >> > > Yes I tried restarting rabbitmq, but that doesn't help. > > Thanks, > Xin > >> Regards >> -steve >> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> To unsubscribe: rdo-list-unsubscribe at redhat.com >> > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From hguemar at fedoraproject.org Sat Jan 24 00:05:29 2015 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Sat, 24 Jan 2015 01:05:29 +0100 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: <54C15A0D.9080707@cern.ch> References: <54B38988.5080601@cern.ch> <54B550ED.6050201@redhat.com> <54C114C6.4080207@redhat.com> <54C15A0D.9080707@cern.ch> Message-ID: We could discuss this topic during the RDO packaging weekly meeting and start planning the next practical steps. Agenda: https://etherpad.openstack.org/p/RDO-Packaging Next meeting: wednesday, 28th 15:00 UTC on #rdo @freenode --- If you're attending FOSDEM, there are various meetings interesting for RDO contributors. * CentOS dojo: we'll have an empty time slot in the cloud track to hack on RDO http://wiki.centos.org/Events/Dojo/Brussels2015 * CentOS/EPEL meeting (saturday night), RDO relies on packages from EPEL, so this is an important discussion. http://wiki.centos.org/Events/Fosdem2015 * RDO meetup: Rich will publish details later Regards, H. From vedsarkushwaha at gmail.com Sat Jan 24 21:44:56 2015 From: vedsarkushwaha at gmail.com (Vedsar Kushwaha) Date: Sun, 25 Jan 2015 03:14:56 +0530 Subject: [Rdo-list] error with dependencies Message-ID: Adding post install manifest entries [ DONE ] Installing Dependencies [ ERROR ] ERROR : Failed to run remote script, stdout: Loaded plugins: fastestmirror, langpacks, priorities Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#7 - "Failed to connect to 2a02:2498:1:3d:5054:ff:fed3:e91a: Network is unreachable" stderr: Warning: Permanently added '10.0.2.15' (ECDSA) to the list of known hosts. + trap t ERR + yum install -y puppet hiera openssh-clients tar nc rubygem-json please help.. -- Vedsar Kushwaha M.Tech-Computational Science Indian Institute of Science -------------- next part -------------- An HTML attachment was scrubbed... URL: From marius at remote-lab.net Sat Jan 24 21:54:49 2015 From: marius at remote-lab.net (Marius Cornea) Date: Sat, 24 Jan 2015 22:54:49 +0100 Subject: [Rdo-list] error with dependencies In-Reply-To: References: Message-ID: Hi Vedsar, Try disabling IPv6 if not using it, it appears that you're trying to acess the repo by its IPv6 address. Tnx, Marius On Sat, Jan 24, 2015 at 10:44 PM, Vedsar Kushwaha wrote: > Adding post install manifest entries [ DONE ] > Installing Dependencies [ ERROR ] > > ERROR : Failed to run remote script, stdout: Loaded plugins: > fastestmirror, langpacks, priorities > Could not retrieve mirrorlist > http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock > error was > 14: curl#7 - "Failed to connect to 2a02:2498:1:3d:5054:ff:fed3:e91a: > Network is unreachable" > > stderr: Warning: Permanently added '10.0.2.15' (ECDSA) to the list of > known hosts. > + trap t ERR > + yum install -y puppet hiera openssh-clients tar nc rubygem-json > > > please help.. > > -- > Vedsar Kushwaha > M.Tech-Computational Science > Indian Institute of Science > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick at laimbock.com Sun Jan 25 11:13:22 2015 From: patrick at laimbock.com (Patrick Laimbock) Date: Sun, 25 Jan 2015 12:13:22 +0100 Subject: [Rdo-list] error with dependencies In-Reply-To: References: Message-ID: <54C4CFD2.7000405@laimbock.com> On 01/24/2015 10:54 PM, Marius Cornea wrote: > Hi Vedsar, > > Try disabling IPv6 if not using it, it appears that you're trying to > acess the repo by its IPv6 address. mirrorlist.centos.org has an IPv6 address so should work: mirrorlist.centos.org. 216 IN AAAA 2a02:2498:1:3d:5054:ff:fed3:e91a I have seen package installs fail sometimes too so I now use a local mirror. Try running packstack again or failing that you can also install those packages manually and then rerun packstack (with the same answer file). Cheers, Patrick From vedsarkushwaha at gmail.com Sun Jan 25 13:24:39 2015 From: vedsarkushwaha at gmail.com (Vedsar Kushwaha) Date: Sun, 25 Jan 2015 18:54:39 +0530 Subject: [Rdo-list] error with dependencies In-Reply-To: <54C4CFD2.7000405@laimbock.com> References: <54C4CFD2.7000405@laimbock.com> Message-ID: Thank you for quick response. after disabling IPV6, error is still there. I disabled IPV6 by vi /etc/sysctl.conf net.ipv6.conf.all.disable_ipv6 = 1 The complete error is: Adding post install manifest entries [ DONE ] Installing Dependencies [ ERROR ] ERROR : Failed to run remote script, stdout: Loaded plugins: fastestmirror, langpacks, priorities Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#7 - "Failed to connect to 2a02:2498:1:3d:5054:ff:fed3:e91a: Network is unreachable" stderr: Warning: Permanently added '10.0.2.15' (ECDSA) to the list of known hosts. + trap t ERR + yum install -y puppet hiera openssh-clients tar nc rubygem-json One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 ++ t ++ exit 1 I'm behind a proxy as well. But when I execute yum install -y puppet hiera openssh-clients tar nc rubygem-json, it completes successfully. when I do, wget http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock it download a html page index.html?release=7.2, that contains Test mode - must specify ip/cc, arch and repo as parameters On Sun, Jan 25, 2015 at 4:43 PM, Patrick Laimbock wrote: > On 01/24/2015 10:54 PM, Marius Cornea wrote: > >> Hi Vedsar, >> >> Try disabling IPv6 if not using it, it appears that you're trying to >> acess the repo by its IPv6 address. >> > > mirrorlist.centos.org has an IPv6 address so should work: > > mirrorlist.centos.org. 216 IN AAAA > 2a02:2498:1:3d:5054:ff:fed3:e91a > > I have seen package installs fail sometimes too so I now use a local > mirror. Try running packstack again or failing that you can also install > those packages manually and then rerun packstack (with the same answer > file). > > Cheers, > Patrick > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -- Vedsar Kushwaha M.Tech-Computational Science Indian Institute of Science -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick at laimbock.com Sun Jan 25 14:03:34 2015 From: patrick at laimbock.com (Patrick Laimbock) Date: Sun, 25 Jan 2015 15:03:34 +0100 Subject: [Rdo-list] error with dependencies In-Reply-To: References: <54C4CFD2.7000405@laimbock.com> Message-ID: <54C4F7B6.1040904@laimbock.com> On 25-01-15 14:24, Vedsar Kushwaha wrote: > Thank you for quick response. > > after disabling IPV6, error is still there. I disabled IPV6 by > > vi /etc/sysctl.conf > net.ipv6.conf.all.disable_ipv6 = 1 IIRC that requires a reboot before it becomes active. On a live system try something like: echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 And then run packstack again. Cheers, Patrick From mohammed.arafa at gmail.com Mon Jan 26 11:56:28 2015 From: mohammed.arafa at gmail.com (Mohammed Arafa) Date: Mon, 26 Jan 2015 06:56:28 -0500 Subject: [Rdo-list] staypuft on centos 6 Message-ID: hi i am trying to install staypuft on centos 6 and it is failing. it also tells me to look in the logs for "ERROR" messages. which i cant find. would appreciate some help. the steps i took to reach the failure yum -y update yum -y install centos-release-SCL.x86_64 ftp://ftp.muug.mb.ca/mirror/fedora/epel/6/i386/epel-release-6-8.noarch.rpm http://yum.theforeman.org/releases/latest/el6/x86_64/foreman-release.rpm yum -y update hostname -f #verify hostname is in fqdn format in /etc/sysconfig/network and /etc/hosts if there is no dns yum -y install foreman-installer-staypuft staypuft-installer --foreman-plugin-discovery-install-images=true the error output is 1 Starting networking setup Networking setup has finished Preparing installation Done Something went wrong! Check the log for ERROR-level output * Foreman is running at https://staypuft.marafa.vm Initial credentials are admin / ru4jvHvkewz4Lfdz * Foreman Proxy is running at https://staypuft.marafa.vm:8443 * Puppetmaster is running at port 8140 The full log is at /var/log/foreman-installer/foreman-installer.log Not running provisioning configuration since installation encountered errors, exit code was 1 Something went wrong! Check the log for ERROR-level output The full log is at /var/log/foreman-installer/foreman-installer.log [root at staypuft ~]# cat /var/log/foreman-installer/foreman-installer.log |grep -i error [root at staypuft ~]# netstat -tupane |grep -E "8443|8140" if it is useful to know this is of course a VM also .. nothing was installed so nothing is running on ports 8443 nor 8140. which means the output is 100% misleading your help and input is much appreciated. thank you -- *805010942448935* *GR750055912MA* *Link to me on LinkedIn * -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Mon Jan 26 13:59:37 2015 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 26 Jan 2015 08:59:37 -0500 Subject: [Rdo-list] Juno EPEL packages In-Reply-To: References: <54B38988.5080601@cern.ch> <54B550ED.6050201@redhat.com> <54C114C6.4080207@redhat.com> <54C15A0D.9080707@cern.ch> Message-ID: <54C64849.2040903@redhat.com> On 01/23/2015 07:05 PM, Ha?kel wrote: > * RDO meetup: Rich will publish details later Unfortunately, meetup time/space is something you sign up for on-site, which doesn't leave any time to work with peoples' schedules much. Hopefully there will be information about this Saturday morning, but I can't promise much in terms of how convenient the available times will be. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From hguemar at fedoraproject.org Mon Jan 26 15:00:03 2015 From: hguemar at fedoraproject.org (hguemar at fedoraproject.org) Date: Mon, 26 Jan 2015 15:00:03 +0000 (UTC) Subject: [Rdo-list] [Fedocal] Reminder meeting : RDO packaging meeting Message-ID: <20150126150003.1CFBC6004C68@fedocal02.phx2.fedoraproject.org> Dear all, You are kindly invited to the meeting: RDO packaging meeting on 2015-01-28 from 15:00:00 to 16:00:00 UTC The meeting will be about: RDO packaging irc meeting ([agenda](https://etherpad.openstack.org/p/RDO-Packaging)) Every week on #rdo on freenode Source: https://apps.fedoraproject.org/calendar//meeting/2024/ From rbowen at redhat.com Mon Jan 26 19:25:25 2015 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 26 Jan 2015 14:25:25 -0500 Subject: [Rdo-list] RDO/OpenStack meetups coming up (January 26, 2015) Message-ID: <54C694A5.6070302@redhat.com> The following are the meetups I'm aware of in the coming week where RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If there's a meetup in your area, please consider attending. It's the best way to find out what interesting things are going on in the larger community, and a great way to make contacts that will help you solve your own problems in the future. And don't forget to blog about it, tweet about it, G+ about it. --Rich * Tuesday, January 27 in Mountain View, CA, US: Online Meetup: Auto-scaling MySQL Database Services on OpenStack with ScaleDB - http://www.meetup.com/Cloud-Online-Meetup/events/219983542/ * Tuesday, January 27 in Sydney, AU: Do you want to help organise a Melbourne OpenStack Meetup in 2015? - http://www.meetup.com/Australian-OpenStack-User-Group/events/219282263/ * Tuesday, January 27 in Budapest, HU: OpenStack 2015 Jan - http://www.meetup.com/OpenStack-Hungary-Meetup-Group/events/220088735/ * Tuesday, January 27 in Tel Aviv-Yafo, IL: Auto-scaling MySQL Database Services on OpenStack with ScaleDB, Ronen Ariely - http://www.meetup.com/OpenStack-Israel/events/219391328/ * Wednesday, January 28 in Mountain View, CA, US: Online Meetup: MidoNet gives OpenStack Neutron a Boost - http://www.meetup.com/Cloud-Online-Meetup/events/220006786/ * Wednesday, January 28 in Mountain View, CA, US: Online Meetup: Unlock Your Cloud Potential w/ Mirantis OpenStack & Cumulus Linux - http://www.meetup.com/Cumulus-Linux-Open-Networking-User-Group-Bay-Area/events/220010052/ * Wednesday, January 28 in Vancouver, BC, CA: OpenStack plays well with others - http://www.meetup.com/Vancouver-OpenStack-Meetup/events/219622935/ * Wednesday, January 28 in Las Vegas, NV, US: Platform as a Service and Identity Management - http://www.meetup.com/Las-Vegas-Red-Hat-User-Group/events/218703467/ * Thursday, January 29 in Mountain View, CA, US: Online Meetup: The Latest on OpenStack Trove in the Upcoming Kilo Release - http://www.meetup.com/Cloud-Online-Meetup/events/220007088/ * Thursday, January 29 in Sydney, AU: Do you want to help organise a Sydney OpenStack Meetup in 2015? - http://www.meetup.com/Australian-OpenStack-User-Group/events/219814136/ * Thursday, January 29 in Whittier, CA, US: Introduction to Red Hat and OpenShift (cohost with OC MongoDB UG) - http://www.meetup.com/Greater-Los-Angeles-Area-Red-Hat-User-Group-RHUG/events/218765670/ * Friday, January 30 in Pittsburgh, PA, US: OpenStack Projects: Ideas and Implementations - http://www.meetup.com/openstack-pittsburgh/events/220036464/ * Saturday, January 31 in Xian, CN: OpenStack Xian Meetup 2015 ?? - http://www.meetup.com/Xian-OpenStack-Meetup/events/220086059/ * Saturday, January 31 in Delhi, IN: Intros and Kickoff - http://www.meetup.com/SDN-OpenDayLight-Delhi-User-Group/events/219875181/ * Monday, February 02 in Seattle, WA, US: OpenStack Seattle Meetup: Tech Duo Featuring PLUMgrid and Tesora - http://www.meetup.com/OpenStack-Seattle/events/198405792/ -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From ak at cloudssky.com Mon Jan 26 22:51:44 2015 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Mon, 26 Jan 2015 23:51:44 +0100 Subject: [Rdo-list] Current Status on RDO HA deployment w/ or w/o Foreman (documentation) Message-ID: Hello together, Any new news about RDO HA deployment guide with or without Foreman? Thanks! Arah -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at gmail.com Wed Jan 28 15:56:09 2015 From: apevec at gmail.com (Alan Pevec) Date: Wed, 28 Jan 2015 16:56:09 +0100 Subject: [Rdo-list] [meeting] RDO Packaging meeting minutes (2015-01-28) Message-ID: ================================ #rdo: RDO packaging (2015-01-28) ================================ Meeting started by number80 at 15:01:05 UTC. The full logs are available at http://meetbot.fedoraproject.org/rdo/2015-01-28/rdo.2015-01-28-15.01.log.html . Meeting summary --------------- * roll call (number80, 15:01:15) * FPCA legal stuff (number80, 15:05:01) * IDEA: moving primary RDO dist-git completely to github/openstack-packages/ then sync to Fedora (number80, 15:07:48) * LINK: http://ltsi.linuxfoundation.org/developers/signed-process (number80, 15:09:17) * ACTION: apevec request input on s-o-b policy on rdo m-l (number80, 15:12:14) * trunk.rdoproject.org (number80, 15:14:42) * ACTION: jruzicka to poke csim about trunk.rdoproject.org vhost on rdo site (apevec, 15:20:18) * installer for trunk aka Packstack against Delorean repo (apevec, 15:21:18) * ACTION: gchamoul will fix the beast (apevec, 15:22:44) * Packstack master to work with Delorean repo by EOW (apevec, 15:27:11) * rdopkg CI docs (apevec, 15:27:26) * expecting CI doc today (apevec, 15:29:43) * moving to CBS builds for RDO Juno EL7 updates (apevec, 15:32:28) * ACTION: jruzicka to add rdoupdate cbs source (apevec, 15:36:57) * ACTION: jruzicka to acquire CBS account (jruzicka, 15:37:41) * Juno/EL6 packages (apevec, 15:41:39) Meeting ended at 15:48:26 UTC. Action Items ------------ * apevec request input on s-o-b policy on rdo m-l * jruzicka to poke csim about trunk.rdoproject.org vhost on rdo site * gchamoul will fix the beast * jruzicka to add rdoupdate cbs source * jruzicka to acquire CBS account Action Items, by person ----------------------- * apevec * apevec request input on s-o-b policy on rdo m-l * gchamoul * gchamoul will fix the beast * jruzicka * jruzicka to poke csim about trunk.rdoproject.org vhost on rdo site * jruzicka to add rdoupdate cbs source * jruzicka to acquire CBS account * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * apevec (97) * number80 (35) * gchamoul (17) * jruzicka (11) * zodbot (5) * kashyap (5) * eggmaster (4) * trown (1) * ryansb (1) * chandankumar (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From slinaber at redhat.com Thu Jan 29 21:48:43 2015 From: slinaber at redhat.com (Steve Linabery) Date: Thu, 29 Jan 2015 15:48:43 -0600 Subject: [Rdo-list] rdopkg overview Message-ID: <20150129214843.GG24719@redhat.com> I have been struggling with the amount of information to convey and what level of detail to include. Since I can't seem to get it perfect to my own satisfaction, here is the imperfect (and long, sorry) version to begin discussion. This is an overview of where things stand (rdopkg CI 'v0.1'). Terminology: 'Release' refers to an OpenStack release (e.g. havana,icehouse,juno) 'Dist' refers to a distro supported by RDO (e.g. fedora-20, epel-6, epel-7) 'phase1' is the initial smoketest for an update submitted via `rdopkg update` 'phase2' is a full-provision test for accumulated updates that have passed phase1 'snapshot' means an OpenStack snapshot of a running instance, i.e. a disk image created from a running OS instance. The very broad strokes: ----------------------- rdopkg ci is triggered when a packager uses `rdopkg update`. When a review lands in the rdo-update gerrit project, a 'phase1' smoketest is initiated via jenkins for each Release/Dist combination present in the update (e.g. if the update contains builds for icehouse/fedora-20 and icehouse/epel-6, each set of RPMs from each build will be smoketested on an instance running the associated Release/Dist). If *all* supported builds from the update pass phase1, then the update is merged into rdo-update. Updates that pass phase1 accumulate in the updates/ directory in the rdo-update project. Periodically, a packager may run 'phase2'. This takes everything in updates/ and uses those RPMs + RDO production repo to provision a set of base images with packstack aio. Again, a simple tempest test is run against the packstack aio instances. If all pass, then phase2 passes, and the `rdopkg update` yaml files are moved from updates/ to ready/. At that point, someone with the keys to the stage repos will push the builds in ready/ to the stage repo. If CI against stage repo passes, stage is rsynced to production. Complexity, Part 1: ------------------- Rdopkg CI v0.1 was designed around the use of OpenStack VM disk snapshots. On a periodic basis, we provision two nodes for each supported combination in [Releases] X [Dists] (e.g. "icehouse, fedora-20" "juno, epel-7" etc). One node is a packstack aio instance built against RDO production repos, and the other is a node running tempest. After a simple tempest test passes for all the packstack aio nodes, we would snapshot the set of instances. Then when we want to do a 'phase1' test for e.g. "icehouse, fedora-20", we can spin up the instances previously snapshotted and save the time of re-running packstack aio. Using snapshots saves approximately 30 min of wait time per test run by skipping provisioning. Using snapshots imposes a few substantial costs/complexities though. First and most significant, snapshots need to be reinstantiated using the same IP addresses that were present when packstack and tempest were run during the provisioning. This means we have to have concurrency control around running only one phase1 run at a time; otherwise an instance might fail to provision because its 'static' IP address is already in use by another run. The second cost is that in practice, a) our OpenStack infrastructure has been unreliable, b) not all Release/Dist combinations reliably provision. So it becomes hard to create a full set of snapshots reliably. Additionally, some updates (e.g. when an update comes in for openstack-puppet-modules) prevent the use of a previously-provisioned packstack instance. Continuing with the o-p-m example: that package is used for provisioning. So simply updating the RPM for that package after running packstack aio doesn't tell us anything about the package sanity (other than perhaps if a new, unsatisfied RPM dependency was introduced). Another source of complexity comes from the nature of the rdopkg update 'unit'. Each yaml file created by `rdopkg update` can contain multiple builds for different Release,Dist combinations. So there must be a way to 'collate' the results of each smoketest for each Release,Dist and pass phase1 only if all updates pass. Furthermore, some combinations of Release,Dist are known (at times, for various ad hoc reasons) to fail testing, and those combinations sometimes need to be 'disabled'. For example, if we know that icehouse/f20 is 'red' on a given day, we might want an update containing icehouse/fedora-20,icehouse/epel-6 to test only the icehouse/epel-6 combination and pass if that passes. Finally, pursuant to the previous point, there need to be 'control' structure jobs for provision/snapshot, phase1, and phase2 runs that pass (and perform some action upon passing) only when all their 'child' jobs have passed. The way we have managed this complexity to date is through the use of the jenkins BuildFlow plugin. Here's some ASCII art (courtesy of 'tree') to show how the jobs are structured now (these are descriptive job names, not the actual jenkins job names). BuildFlow jobs are indicated by (bf). . `-- rdopkg_master_flow (bf) |-- provision_and_snapshot (bf) | |-- provision_and_snapshot_icehouse_epel6 | |-- provision_and_snapshot_icehouse_f20 | |-- provision_and_snapshot_juno_epel7 | `-- provision_and_snapshot_juno_f21 |-- phase1_flow (bf) | |-- phase1_test_icehouse_f20 | `-- phase1_test_juno_f21 `-- phase2_flow (bf) |-- phase2_test_icehouse_epel6 |-- phase2_test_icehouse_f20 |-- phase2_test_juno_epel7 `-- phase2_test_juno_f21 When a change comes in from `rdopkg update`, the rdopkg_master_flow job is triggered. It's the only job that gets triggered from gerrit, so it kicks off phase1_flow. phase1_flow runs 'child' jobs (normal jenkins jobs, not buildflow) for each Release,Dist combination present in the update. provision_and_snapshot is run by manually setting a build parameter (BUILD_SNAPS) in the rdopkg_master_flow job, and triggering the build of rdopkg_master_flow. phase2 is invoked similar to the provision_and_snapshot build, by checking 'RUN_PHASE2' in the rdopkg_master_flow build parameters before executing a build thereof. Concurrency control is a side effect of requiring the user or gerrit to execute rdopkg_master_flow for every action. There can be only one rdopkg_master_flow build executing at any given time. Complexity, Part 2: ------------------- In addition to the nasty complexity of using nested BuildFlow type jobs, each 'worker' job (i.e. the non-buildflow type jobs) has some built in complexity that is reflected in the amount of logic in each job's bash script definition. Some of this has been alluded to in previous points. For instance, each job in the phase1 flow needs to determine, for each update, if the update contains a package that requires full packstack aio provisioning from a base image (e.g. openstack-puppet-modules). This 'must provision' list needs to be stored somewhere that all jobs can read it, and it needs to be dynamic enough to add to it as requirements dictate. But additionally, for package sets not requiring provisioning a base image, phase1 job needs to query the backing OpenStack instance to see if there exists a 'known good' snapshot, get the images' UUIDs from OpenStack, and spin up the instances using the snapshot images. This baked-in complexity in the 'worker' jenkins jobs has made it difficult to maintain the job definitions, and more importantly difficult to run using jjb or in other more 'orthodox' CI-type ways. The rdopkg CI stuff is a bastard child of a fork. It lives in its own mutant gene pool. A Way Forward...? ---------------- Wes Hayutin had a good idea that might help reduce some of the complexity here as we contemplate a) making rdopkg CI public, b) moving toward rdopkg CI 0.2. His idea was a) stop using snapshots since the per-test-run savings doesn't seem to justify the burden they create, b) do away with BuildFlow by including the 'this update contains builds for (Release1,Dist2),...,(ReleaseN,DistM)' information in the gerrit change topic. I think that's a great idea, but I have a superstitious gut feeling that we may lose some 'transaction'y-ness from the current setup. For example, what happens if phase1 and phase2 overlap their execution? It's not that I have evidence that this will be a problem; it's more that we had these issues worked out fairly well with rdopkg CI 0.1, and I think the change warrants some scrutiny/thought (which clearly I have not done!). We'd still need to work out a way to execute phase2, though. There would be no `rdopkg update` event to trigger phase2 runs. I'm not sure how we'd do that without a BuildFlow. BuildFlow jobs also allow parallelization of the child jobs, and I'm not sure how we could replicate that without using that type of job. Whew. I hope this was helpful. I'm saving a copy of this text to http://slinabery.fedorapeople.org/rdopkg-overview.txt Cheers, Steve Linabery (freenode: eggmaster) Senior Software Engineer, Red Hat, Inc. From jruzicka at redhat.com Fri Jan 30 13:52:55 2015 From: jruzicka at redhat.com (Jakub Ruzicka) Date: Fri, 30 Jan 2015 14:52:55 +0100 Subject: [Rdo-list] rdopkg overview In-Reply-To: <20150129214843.GG24719@redhat.com> References: <20150129214843.GG24719@redhat.com> Message-ID: <54CB8CB7.6030004@redhat.com> Very nice overview Steve, thanks for writing this down! My random thoughts on the matter inline. On 29.1.2015 22:48, Steve Linabery wrote: > I have been struggling with the amount of information to convey and what level of detail to include. Since I can't seem to get it perfect to my own satisfaction, here is the imperfect (and long, sorry) version to begin discussion. > > This is an overview of where things stand (rdopkg CI 'v0.1'). For some time, I'm wondering if we should really call it rdopkg CI since it's not really tied to rdopkg but to RDO. You can use most of rdopkg on any distgit. I reckon we should simply call it RDO CI to avoid confusion. I for one don't underestimate the impact of naming stuff ;) > Terminology: > 'Release' refers to an OpenStack release (e.g. havana,icehouse,juno) > 'Dist' refers to a distro supported by RDO (e.g. fedora-20, epel-6, epel-7) > 'phase1' is the initial smoketest for an update submitted via `rdopkg update` > 'phase2' is a full-provision test for accumulated updates that have passed phase1 > 'snapshot' means an OpenStack snapshot of a running instance, i.e. a disk image created from a running OS instance. > > The very broad strokes: > ----------------------- > > rdopkg ci is triggered when a packager uses `rdopkg update`. > > When a review lands in the rdo-update gerrit project, a 'phase1' smoketest is initiated via jenkins for each Release/Dist combination present in the update (e.g. if the update contains builds for icehouse/fedora-20 and icehouse/epel-6, each set of RPMs from each build will be smoketested on an instance running the associated Release/Dist). If *all* supported builds from the update pass phase1, then the update is merged into rdo-update. Updates that pass phase1 accumulate in the updates/ directory in the rdo-update project. > > Periodically, a packager may run 'phase2'. This takes everything in updates/ and uses those RPMs + RDO production repo to provision a set of base images with packstack aio. Again, a simple tempest test is run against the packstack aio instances. If all pass, then phase2 passes, and the `rdopkg update` yaml files are moved from updates/ to ready/. > > At that point, someone with the keys to the stage repos will push the builds in ready/ to the stage repo. If CI against stage repo passes, stage is rsynced to production. > > Complexity, Part 1: > ------------------- > > Rdopkg CI v0.1 was designed around the use of OpenStack VM disk snapshots. On a periodic basis, we provision two nodes for each supported combination in [Releases] X [Dists] (e.g. "icehouse, fedora-20" "juno, epel-7" etc). One node is a packstack aio instance built against RDO production repos, and the other is a node running tempest. After a simple tempest test passes for all the packstack aio nodes, we would snapshot the set of instances. Then when we want to do a 'phase1' test for e.g. "icehouse, fedora-20", we can spin up the instances previously snapshotted and save the time of re-running packstack aio. > > Using snapshots saves approximately 30 min of wait time per test run by skipping provisioning. Using snapshots imposes a few substantial costs/complexities though. First and most significant, snapshots need to be reinstantiated using the same IP addresses that were present when packstack and tempest were run during the provisioning. This means we have to have concurrency control around running only one phase1 run at a time; otherwise an instance might fail to provision because its 'static' IP address is already in use by another run. The second cost is that in practice, a) our OpenStack infrastructure has been unreliable, b) not all Release/Dist combinations reliably provision. So it becomes hard to create a full set of snapshots reliably. > > Additionally, some updates (e.g. when an update comes in for openstack-puppet-modules) prevent the use of a previously-provisioned packstack instance. Continuing with the o-p-m example: that package is used for provisioning. So simply updating the RPM for that package after running packstack aio doesn't tell us anything about the package sanity (other than perhaps if a new, unsatisfied RPM dependency was introduced). > > Another source of complexity comes from the nature of the rdopkg update 'unit'. Each yaml file created by `rdopkg update` can contain multiple builds for different Release,Dist combinations. So there must be a way to 'collate' the results of each smoketest for each Release,Dist and pass phase1 only if all updates pass. Furthermore, some combinations of Release,Dist are known (at times, for various ad hoc reasons) to fail testing, and those combinations sometimes need to be 'disabled'. For example, if we know that icehouse/f20 is 'red' on a given day, we might want an update containing icehouse/fedora-20,icehouse/epel-6 to test only the icehouse/epel-6 combination and pass if that passes. > > Finally, pursuant to the previous point, there need to be 'control' structure jobs for provision/snapshot, phase1, and phase2 runs that pass (and perform some action upon passing) only when all their 'child' jobs have passed. > > The way we have managed this complexity to date is through the use of the jenkins BuildFlow plugin. Here's some ASCII art (courtesy of 'tree') to show how the jobs are structured now (these are descriptive job names, not the actual jenkins job names). BuildFlow jobs are indicated by (bf). > > . > `-- rdopkg_master_flow (bf) > |-- provision_and_snapshot (bf) > | |-- provision_and_snapshot_icehouse_epel6 > | |-- provision_and_snapshot_icehouse_f20 > | |-- provision_and_snapshot_juno_epel7 > | `-- provision_and_snapshot_juno_f21 > |-- phase1_flow (bf) > | |-- phase1_test_icehouse_f20 > | `-- phase1_test_juno_f21 > `-- phase2_flow (bf) > |-- phase2_test_icehouse_epel6 > |-- phase2_test_icehouse_f20 > |-- phase2_test_juno_epel7 > `-- phase2_test_juno_f21 As a consumer of CI results, my main problem with this is it takes about 7 clicks to get to the actual error. > When a change comes in from `rdopkg update`, the rdopkg_master_flow job is triggered. It's the only job that gets triggered from gerrit, so it kicks off phase1_flow. phase1_flow runs 'child' jobs (normal jenkins jobs, not buildflow) for each Release,Dist combination present in the update. > > provision_and_snapshot is run by manually setting a build parameter (BUILD_SNAPS) in the rdopkg_master_flow job, and triggering the build of rdopkg_master_flow. > > phase2 is invoked similar to the provision_and_snapshot build, by checking 'RUN_PHASE2' in the rdopkg_master_flow build parameters before executing a build thereof. > > Concurrency control is a side effect of requiring the user or gerrit to execute rdopkg_master_flow for every action. There can be only one rdopkg_master_flow build executing at any given time. > > Complexity, Part 2: > ------------------- > > In addition to the nasty complexity of using nested BuildFlow type jobs, each 'worker' job (i.e. the non-buildflow type jobs) has some built in complexity that is reflected in the amount of logic in each job's bash script definition. > > Some of this has been alluded to in previous points. For instance, each job in the phase1 flow needs to determine, for each update, if the update contains a package that requires full packstack aio provisioning from a base image (e.g. openstack-puppet-modules). This 'must provision' list needs to be stored somewhere that all jobs can read it, and it needs to be dynamic enough to add to it as requirements dictate. > > But additionally, for package sets not requiring provisioning a base image, phase1 job needs to query the backing OpenStack instance to see if there exists a 'known good' snapshot, get the images' UUIDs from OpenStack, and spin up the instances using the snapshot images. > > This baked-in complexity in the 'worker' jenkins jobs has made it difficult to maintain the job definitions, and more importantly difficult to run using jjb or in other more 'orthodox' CI-type ways. The rdopkg CI stuff is a bastard child of a fork. It lives in its own mutant gene pool. lolololol > A Way Forward...? > ---------------- > > Wes Hayutin had a good idea that might help reduce some of the complexity here as we contemplate a) making rdopkg CI public, b) moving toward rdopkg CI 0.2. > > His idea was a) stop using snapshots since the per-test-run savings doesn't seem to justify the burden they create, b) do away with BuildFlow by including the 'this update contains builds for (Release1,Dist2),...,(ReleaseN,DistM)' information in the gerrit change topic. It's easy to modify `rdopkg update` to include this information. However, it's redundant so you can (in theory) submit an update where this summary won't match the actual YAML data. That's probably completely irrelevant, but I'm mentioning it nonetheless :) > I think that's a great idea, but I have a superstitious gut feeling that we may lose some 'transaction'y-ness from the current setup. For example, what happens if phase1 and phase2 overlap their execution? It's not that I have evidence that this will be a problem; it's more that we had these issues worked out fairly well with rdopkg CI 0.1, and I think the change warrants some scrutiny/thought (which clearly I have not done!). Worth a try if you ask me. I'll gladly help with any scripts/helpers needed, so just let me know. > We'd still need to work out a way to execute phase2, though. There would be no `rdopkg update` event to trigger phase2 runs. I'm not sure how we'd do that without a BuildFlow. BuildFlow jobs also allow parallelization of the child jobs, and I'm not sure how we could replicate that without using that type of job. There can be rdopkg action (i.e. rdopkg update --phase2) to do whatever you need if that helps. > Whew. I hope this was helpful. I'm saving a copy of this text to http://slinabery.fedorapeople.org/rdopkg-overview.txt Sure is, thanks! Cheers, Jakub From slinaber at redhat.com Fri Jan 30 14:53:25 2015 From: slinaber at redhat.com (Steve Linabery) Date: Fri, 30 Jan 2015 08:53:25 -0600 Subject: [Rdo-list] rdopkg overview In-Reply-To: <54CB8CB7.6030004@redhat.com> References: <20150129214843.GG24719@redhat.com> <54CB8CB7.6030004@redhat.com> Message-ID: <20150130145325.GL24719@redhat.com> On Fri, Jan 30, 2015 at 02:52:55PM +0100, Jakub Ruzicka wrote: > Very nice overview Steve, thanks for writing this down! > > My random thoughts on the matter inline. > > On 29.1.2015 22:48, Steve Linabery wrote: > > I have been struggling with the amount of information to convey and what level of detail to include. Since I can't seem to get it perfect to my own satisfaction, here is the imperfect (and long, sorry) version to begin discussion. > > > > This is an overview of where things stand (rdopkg CI 'v0.1'). > > For some time, I'm wondering if we should really call it rdopkg CI since > it's not really tied to rdopkg but to RDO. You can use most of rdopkg on > any distgit. I reckon we should simply call it RDO CI to avoid > confusion. I for one don't underestimate the impact of naming stuff ;) > > > Terminology: > > 'Release' refers to an OpenStack release (e.g. havana,icehouse,juno) > > 'Dist' refers to a distro supported by RDO (e.g. fedora-20, epel-6, epel-7) > > 'phase1' is the initial smoketest for an update submitted via `rdopkg update` > > 'phase2' is a full-provision test for accumulated updates that have passed phase1 > > 'snapshot' means an OpenStack snapshot of a running instance, i.e. a disk image created from a running OS instance. > > > > The very broad strokes: > > ----------------------- > > > > rdopkg ci is triggered when a packager uses `rdopkg update`. > > > > When a review lands in the rdo-update gerrit project, a 'phase1' smoketest is initiated via jenkins for each Release/Dist combination present in the update (e.g. if the update contains builds for icehouse/fedora-20 and icehouse/epel-6, each set of RPMs from each build will be smoketested on an instance running the associated Release/Dist). If *all* supported builds from the update pass phase1, then the update is merged into rdo-update. Updates that pass phase1 accumulate in the updates/ directory in the rdo-update project. > > > > Periodically, a packager may run 'phase2'. This takes everything in updates/ and uses those RPMs + RDO production repo to provision a set of base images with packstack aio. Again, a simple tempest test is run against the packstack aio instances. If all pass, then phase2 passes, and the `rdopkg update` yaml files are moved from updates/ to ready/. > > > > At that point, someone with the keys to the stage repos will push the builds in ready/ to the stage repo. If CI against stage repo passes, stage is rsynced to production. > > > > Complexity, Part 1: > > ------------------- > > > > Rdopkg CI v0.1 was designed around the use of OpenStack VM disk snapshots. On a periodic basis, we provision two nodes for each supported combination in [Releases] X [Dists] (e.g. "icehouse, fedora-20" "juno, epel-7" etc). One node is a packstack aio instance built against RDO production repos, and the other is a node running tempest. After a simple tempest test passes for all the packstack aio nodes, we would snapshot the set of instances. Then when we want to do a 'phase1' test for e.g. "icehouse, fedora-20", we can spin up the instances previously snapshotted and save the time of re-running packstack aio. > > > > Using snapshots saves approximately 30 min of wait time per test run by skipping provisioning. Using snapshots imposes a few substantial costs/complexities though. First and most significant, snapshots need to be reinstantiated using the same IP addresses that were present when packstack and tempest were run during the provisioning. This means we have to have concurrency control around running only one phase1 run at a time; otherwise an instance might fail to provision because its 'static' IP address is already in use by another run. The second cost is that in practice, a) our OpenStack infrastructure has been unreliable, b) not all Release/Dist combinations reliably provision. So it becomes hard to create a full set of snapshots reliably. > > > > Additionally, some updates (e.g. when an update comes in for openstack-puppet-modules) prevent the use of a previously-provisioned packstack instance. Continuing with the o-p-m example: that package is used for provisioning. So simply updating the RPM for that package after running packstack aio doesn't tell us anything about the package sanity (other than perhaps if a new, unsatisfied RPM dependency was introduced). > > > > Another source of complexity comes from the nature of the rdopkg update 'unit'. Each yaml file created by `rdopkg update` can contain multiple builds for different Release,Dist combinations. So there must be a way to 'collate' the results of each smoketest for each Release,Dist and pass phase1 only if all updates pass. Furthermore, some combinations of Release,Dist are known (at times, for various ad hoc reasons) to fail testing, and those combinations sometimes need to be 'disabled'. For example, if we know that icehouse/f20 is 'red' on a given day, we might want an update containing icehouse/fedora-20,icehouse/epel-6 to test only the icehouse/epel-6 combination and pass if that passes. > > > > Finally, pursuant to the previous point, there need to be 'control' structure jobs for provision/snapshot, phase1, and phase2 runs that pass (and perform some action upon passing) only when all their 'child' jobs have passed. > > > > The way we have managed this complexity to date is through the use of the jenkins BuildFlow plugin. Here's some ASCII art (courtesy of 'tree') to show how the jobs are structured now (these are descriptive job names, not the actual jenkins job names). BuildFlow jobs are indicated by (bf). > > > > . > > `-- rdopkg_master_flow (bf) > > |-- provision_and_snapshot (bf) > > | |-- provision_and_snapshot_icehouse_epel6 > > | |-- provision_and_snapshot_icehouse_f20 > > | |-- provision_and_snapshot_juno_epel7 > > | `-- provision_and_snapshot_juno_f21 > > |-- phase1_flow (bf) > > | |-- phase1_test_icehouse_f20 > > | `-- phase1_test_juno_f21 > > `-- phase2_flow (bf) > > |-- phase2_test_icehouse_epel6 > > |-- phase2_test_icehouse_f20 > > |-- phase2_test_juno_epel7 > > `-- phase2_test_juno_f21 > > As a consumer of CI results, my main problem with this is it takes about > 7 clicks to get to the actual error. > > > > When a change comes in from `rdopkg update`, the rdopkg_master_flow job is triggered. It's the only job that gets triggered from gerrit, so it kicks off phase1_flow. phase1_flow runs 'child' jobs (normal jenkins jobs, not buildflow) for each Release,Dist combination present in the update. > > > > provision_and_snapshot is run by manually setting a build parameter (BUILD_SNAPS) in the rdopkg_master_flow job, and triggering the build of rdopkg_master_flow. > > > > phase2 is invoked similar to the provision_and_snapshot build, by checking 'RUN_PHASE2' in the rdopkg_master_flow build parameters before executing a build thereof. > > > > Concurrency control is a side effect of requiring the user or gerrit to execute rdopkg_master_flow for every action. There can be only one rdopkg_master_flow build executing at any given time. > > > > Complexity, Part 2: > > ------------------- > > > > In addition to the nasty complexity of using nested BuildFlow type jobs, each 'worker' job (i.e. the non-buildflow type jobs) has some built in complexity that is reflected in the amount of logic in each job's bash script definition. > > > > Some of this has been alluded to in previous points. For instance, each job in the phase1 flow needs to determine, for each update, if the update contains a package that requires full packstack aio provisioning from a base image (e.g. openstack-puppet-modules). This 'must provision' list needs to be stored somewhere that all jobs can read it, and it needs to be dynamic enough to add to it as requirements dictate. > > > > But additionally, for package sets not requiring provisioning a base image, phase1 job needs to query the backing OpenStack instance to see if there exists a 'known good' snapshot, get the images' UUIDs from OpenStack, and spin up the instances using the snapshot images. > > > > This baked-in complexity in the 'worker' jenkins jobs has made it difficult to maintain the job definitions, and more importantly difficult to run using jjb or in other more 'orthodox' CI-type ways. The rdopkg CI stuff is a bastard child of a fork. It lives in its own mutant gene pool. > > lolololol > > > > A Way Forward...? > > ---------------- > > > > Wes Hayutin had a good idea that might help reduce some of the complexity here as we contemplate a) making rdopkg CI public, b) moving toward rdopkg CI 0.2. > > > > His idea was a) stop using snapshots since the per-test-run savings doesn't seem to justify the burden they create, b) do away with BuildFlow by including the 'this update contains builds for (Release1,Dist2),...,(ReleaseN,DistM)' information in the gerrit change topic. > > It's easy to modify `rdopkg update` to include this information. > However, it's redundant so you can (in theory) submit an update where > this summary won't match the actual YAML data. That's probably > completely irrelevant, but I'm mentioning it nonetheless :) > This is less a response to Jakub's comment here and more an additional explanation of why this idea is so nice. Currently, when phase1_flow is triggered, it ssh's to a separate host to run `rdoupdate check` (because BuildFlow jobs execute on the jenkins master node, disregarding any setting to run them on a particular slave), and parse the output to determine what Release,Dist combinations need to be tested. The gerrit topic approach would allow us to have N jobs listening to gerrit trigger events, but e.g. the juno/epel-7 job would only execute if the gerrit topic matched that job's regexp. The gerrit review would only get its +2 when these jobs complete successfully. It would be nice to decide what that topic string ought to look like so that a) we have sanity in the regexp, b) we are sure gerrit will support long strings with whatever odd chars we may wish to use, etc. > > > I think that's a great idea, but I have a superstitious gut feeling that we may lose some 'transaction'y-ness from the current setup. For example, what happens if phase1 and phase2 overlap their execution? It's not that I have evidence that this will be a problem; it's more that we had these issues worked out fairly well with rdopkg CI 0.1, and I think the change warrants some scrutiny/thought (which clearly I have not done!). > > Worth a try if you ask me. I'll gladly help with any scripts/helpers > needed, so just let me know. > > > > We'd still need to work out a way to execute phase2, though. There would be no `rdopkg update` event to trigger phase2 runs. I'm not sure how we'd do that without a BuildFlow. BuildFlow jobs also allow parallelization of the child jobs, and I'm not sure how we could replicate that without using that type of job. > > There can be rdopkg action (i.e. rdopkg update --phase2) to do whatever > you need if that helps. > > > > Whew. I hope this was helpful. I'm saving a copy of this text to http://slinabery.fedorapeople.org/rdopkg-overview.txt > > Sure is, thanks! > > > Cheers, > Jakub > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com