Re: [Openstack] Routed provider networks

2017-06-18 Thread Kevin Benton 
command while tailing the
>>>>>> log:
>>>>>>
>>>>>> *2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource
>>>>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 
>>>>>> 7e7176b79f94483c8b802a7004466e66
>>>>>> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The
>>>>>> server could not comply with the request since it is either malformed or
>>>>>> otherwise incorrect.*
>>>>>> *2017-06-18 10:24:51.843 12018 INFO neutron.wsgi
>>>>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 
>>>>>> 7e7176b79f94483c8b802a7004466e66
>>>>>> 664dc5e6023140eca0faeb2d0ecc31c2 - *
>>>>>>
>>>>>>
>>>>>> As for the ocata config, this was built by using the ocata:
>>>>>>
>>>>>> https://docs.openstack.org/ocata/install-guide-ubuntu/
>>>>>>
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com> wr
>>>>>> ote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Please look in /var/log/neutron/neutron-server.log
>>>>>>>
>>>>>>> That should provide and exception trace
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From: *Alex Evonosky <alex.evono...@gmail.com>
>>>>>>> *Date: *Sunday, June 18, 2017 at 5:04 PM
>>>>>>> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org
>>>>>>> >
>>>>>>> *Subject: *[Openstack] Routed provider networks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hello-
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I wanted to test the routed provider networks of Ocata, and
>>>>>>> following the example config:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://docs.openstack.org/ocata/networking-guide/config-rou
>>>>>>> ted-networks.html
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I typed in the following on my controller node:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> @openstack-controller1:~# openstack network create --share
>>>>>>> --provider-physical-network provider1 --provider-network-type vlan
>>>>>>> --provider-segment 2016 multisegment1
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> and I receive this:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *Error while executing command: Bad Request*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Is there a log that may show what this error is referring to?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thank you.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/op
>>>>>> enstack
>>>>>> Post to : openstack@lists.openstack.org
>>>>>> Unsubscribe : http://lists.openstack.org/c
>>>>>> gi-bin/mailman/listinfo/openstack
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>> !DSPAM:1,5946a6cb169661288915335! __
>> _
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/op
>> enstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openst
>> ack
>>
>> !DSPAM:1,5946a6cb169661288915335!
>>
>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Alex Evonosky 
gt;>>>
>>>>>
>>>>> As for the ocata config, this was built by using the ocata:
>>>>>
>>>>> https://docs.openstack.org/ocata/install-guide-ubuntu/
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com> wr
>>>>> ote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Please look in /var/log/neutron/neutron-server.log
>>>>>>
>>>>>> That should provide and exception trace
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From: *Alex Evonosky <alex.evono...@gmail.com>
>>>>>> *Date: *Sunday, June 18, 2017 at 5:04 PM
>>>>>> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org>
>>>>>> *Subject: *[Openstack] Routed provider networks
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hello-
>>>>>>
>>>>>>
>>>>>>
>>>>>> I wanted to test the routed provider networks of Ocata, and following
>>>>>> the example config:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://docs.openstack.org/ocata/networking-guide/config-rou
>>>>>> ted-networks.html
>>>>>>
>>>>>>
>>>>>>
>>>>>> I typed in the following on my controller node:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> @openstack-controller1:~# openstack network create --share
>>>>>> --provider-physical-network provider1 --provider-network-type vlan
>>>>>> --provider-segment 2016 multisegment1
>>>>>>
>>>>>>
>>>>>>
>>>>>> and I receive this:
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Error while executing command: Bad Request*
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Is there a log that may show what this error is referring to?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
>>>>> openstack
>>>>> Post to : openstack@lists.openstack.org
>>>>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
>>>>> openstack
>>>>>
>>>>>
>>>>
>>>
>>
> !DSPAM:1,5946a6cb169661288915335! __
> _
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
> !DSPAM:1,5946a6cb169661288915335!
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Kevin Benton 
It may be in /etc/neutron/plugins/ml2_conf.ini or somewhere in there. Run
'ps -ef | grep neutron-server' to see which config files are being
referenced in your deployment.

On Sun, Jun 18, 2017 at 9:13 AM, Alex Evonosky <alex.evono...@gmail.com>
wrote:

> Thank you Kevin,
>
> In the /etc/neutron/neutron.conf file, there is no [ml2_type_vlan]
> section under ocata.  Do I need to add this section in?
>
> Thank you.
>
> On Sun, Jun 18, 2017 at 12:08 PM, Kevin Benton <ke...@benton.pub> wrote:
>
>> Ok. So the actual error message is "Invalid input for operation:
>> physical_network 'provider1' unknown  for VLAN provider network.".
>>
>> That means that in your Neutron server configuration file under the
>> [ml2_type_vlan] section you need to add 'provider1' to the
>> 'network_vlan_ranges' option.
>>
>>
>>
>> On Sun, Jun 18, 2017 at 9:04 AM, Alex Evonosky <alex.evono...@gmail.com>
>> wrote:
>>
>>> Kevin-
>>>
>>> Thank you for the tip.  The Debug is attached as well.
>>>
>>> Thank you.
>>>
>>> On Sun, Jun 18, 2017 at 11:54 AM, Kevin Benton <ke...@benton.pub> wrote:
>>>
>>>> The openstack command should have an option to enable debugging so you
>>>> can get the error message. Try openstack --debug
>>>>
>>>>
>>>>
>>>> On Sun, Jun 18, 2017 at 7:27 AM, Alex Evonosky <alex.evono...@gmail.com
>>>> > wrote:
>>>>
>>>>> Gary-
>>>>>
>>>>> Thank you for the feedback.  I issued the command while tailing the
>>>>> log:
>>>>>
>>>>> *2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource
>>>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>>>>> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The
>>>>> server could not comply with the request since it is either malformed or
>>>>> otherwise incorrect.*
>>>>> *2017-06-18 10:24:51.843 12018 INFO neutron.wsgi
>>>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>>>>> 664dc5e6023140eca0faeb2d0ecc31c2 - *
>>>>>
>>>>>
>>>>> As for the ocata config, this was built by using the ocata:
>>>>>
>>>>> https://docs.openstack.org/ocata/install-guide-ubuntu/
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Please look in /var/log/neutron/neutron-server.log
>>>>>>
>>>>>> That should provide and exception trace
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From: *Alex Evonosky <alex.evono...@gmail.com>
>>>>>> *Date: *Sunday, June 18, 2017 at 5:04 PM
>>>>>> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org>
>>>>>> *Subject: *[Openstack] Routed provider networks
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hello-
>>>>>>
>>>>>>
>>>>>>
>>>>>> I wanted to test the routed provider networks of Ocata, and following
>>>>>> the example config:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://docs.openstack.org/ocata/networking-guide/config-rou
>>>>>> ted-networks.html
>>>>>>
>>>>>>
>>>>>>
>>>>>> I typed in the following on my controller node:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> @openstack-controller1:~# openstack network create --share
>>>>>> --provider-physical-network provider1 --provider-network-type vlan
>>>>>> --provider-segment 2016 multisegment1
>>>>>>
>>>>>>
>>>>>>
>>>>>> and I receive this:
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Error while executing command: Bad Request*
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Is there a log that may show what this error is referring to?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> Mailing list: http://lists.openstack.org/cgi
>>>>> -bin/mailman/listinfo/openstack
>>>>> Post to : openstack@lists.openstack.org
>>>>> Unsubscribe : http://lists.openstack.org/cgi
>>>>> -bin/mailman/listinfo/openstack
>>>>>
>>>>>
>>>>
>>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Remo Mattei 
Its not going to be there.. you need to look into the plugins directory. 


 grep provider *
ml2_conf.ini:# Default network type for external networks when no provider 
attributes are
ml2_conf.ini:# specified. By default it is None, which means that if provider 
attributes are
ml2_conf.ini:# specifying physical_network names usable for VLAN provider and 
tenant




> On Jun 18, 2017, at 9:13 AM, Alex Evonosky <alex.evono...@gmail.com> wrote:
> 
> Thank you Kevin,
> 
> In the /etc/neutron/neutron.conf file, there is no [ml2_type_vlan]  section 
> under ocata.  Do I need to add this section in?
> 
> Thank you.
> 
> On Sun, Jun 18, 2017 at 12:08 PM, Kevin Benton <ke...@benton.pub 
> <mailto:ke...@benton.pub>> wrote:
> Ok. So the actual error message is "Invalid input for operation: 
> physical_network 'provider1' unknown  for VLAN provider network.".
> 
> That means that in your Neutron server configuration file under the 
> [ml2_type_vlan] section you need to add 'provider1' to the 
> 'network_vlan_ranges' option. 
> 
> 
> 
> On Sun, Jun 18, 2017 at 9:04 AM, Alex Evonosky <alex.evono...@gmail.com 
> <mailto:alex.evono...@gmail.com>> wrote:
> Kevin-
> 
> Thank you for the tip.  The Debug is attached as well.
> 
> Thank you.
> 
> On Sun, Jun 18, 2017 at 11:54 AM, Kevin Benton <ke...@benton.pub 
> <mailto:ke...@benton.pub>> wrote:
> The openstack command should have an option to enable debugging so you can 
> get the error message. Try openstack --debug
> 
> 
> 
> On Sun, Jun 18, 2017 at 7:27 AM, Alex Evonosky <alex.evono...@gmail.com 
> <mailto:alex.evono...@gmail.com>> wrote:
> Gary-
> 
> Thank you for the feedback.  I issued the command while tailing the log:
> 
> 2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource 
> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66 
> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The 
> server could not comply with the request since it is either malformed or 
> otherwise incorrect.
> 2017-06-18 10:24:51.843 12018 INFO neutron.wsgi 
> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66 
> 664dc5e6023140eca0faeb2d0ecc31c2 - 
> 
> 
> As for the ocata config, this was built by using the ocata:
> 
> https://docs.openstack.org/ocata/install-guide-ubuntu/ 
> <https://docs.openstack.org/ocata/install-guide-ubuntu/>
> 
> 
> Thank you.
> 
> 
> 
> 
> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com 
> <mailto:gkot...@vmware.com>> wrote:
> Hi,
> 
> Please look in /var/log/neutron/neutron-server.log
> 
> That should provide and exception trace
> 
> Thanks
> 
> Gary
> 
>  
> 
> From: Alex Evonosky <alex.evono...@gmail.com <mailto:alex.evono...@gmail.com>>
> Date: Sunday, June 18, 2017 at 5:04 PM
> To: "openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>" 
> <openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>>
> Subject: [Openstack] Routed provider networks
> 
>  
> 
> Hello- 
> 
>  
> 
> I wanted to test the routed provider networks of Ocata, and following the 
> example config:
> 
>  
> 
> https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html 
> <https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html>
>  
> 
> I typed in the following on my controller node:
> 
>  
> 
>  
> 
> @openstack-controller1:~# openstack network create --share 
> --provider-physical-network provider1 --provider-network-type vlan 
> --provider-segment 2016 multisegment1
> 
>  
> 
> and I receive this:
> 
>  
> 
> Error while executing command: Bad Request
> 
>  
> 
>  
> 
> Is there a log that may show what this error is referring to?
> 
>  
> 
>  
> 
> Thank you.
> 
>  
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> Post to : openstack@lists.openstack.org 
> <mailto:openstack@lists.openstack.org>
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> 
> 
> 
> 
> 
> !DSPAM:1,5946a6cb169661288915335! 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> Post to : openstack@lists.openstack.org 
> <mailto:openstack@lists.openstack.org>
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> 
> !DSPAM:1,5946a6cb169661288915335!

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Alex Evonosky 
Thank you Kevin,

In the /etc/neutron/neutron.conf file, there is no [ml2_type_vlan]  section
under ocata.  Do I need to add this section in?

Thank you.

On Sun, Jun 18, 2017 at 12:08 PM, Kevin Benton <ke...@benton.pub> wrote:

> Ok. So the actual error message is "Invalid input for operation:
> physical_network 'provider1' unknown  for VLAN provider network.".
>
> That means that in your Neutron server configuration file under the
> [ml2_type_vlan] section you need to add 'provider1' to the
> 'network_vlan_ranges' option.
>
>
>
> On Sun, Jun 18, 2017 at 9:04 AM, Alex Evonosky <alex.evono...@gmail.com>
> wrote:
>
>> Kevin-
>>
>> Thank you for the tip.  The Debug is attached as well.
>>
>> Thank you.
>>
>> On Sun, Jun 18, 2017 at 11:54 AM, Kevin Benton <ke...@benton.pub> wrote:
>>
>>> The openstack command should have an option to enable debugging so you
>>> can get the error message. Try openstack --debug
>>>
>>>
>>>
>>> On Sun, Jun 18, 2017 at 7:27 AM, Alex Evonosky <alex.evono...@gmail.com>
>>> wrote:
>>>
>>>> Gary-
>>>>
>>>> Thank you for the feedback.  I issued the command while tailing the log:
>>>>
>>>> *2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource
>>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>>>> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The
>>>> server could not comply with the request since it is either malformed or
>>>> otherwise incorrect.*
>>>> *2017-06-18 10:24:51.843 12018 INFO neutron.wsgi
>>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>>>> 664dc5e6023140eca0faeb2d0ecc31c2 - *
>>>>
>>>>
>>>> As for the ocata config, this was built by using the ocata:
>>>>
>>>> https://docs.openstack.org/ocata/install-guide-ubuntu/
>>>>
>>>>
>>>> Thank you.
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Please look in /var/log/neutron/neutron-server.log
>>>>>
>>>>> That should provide and exception trace
>>>>>
>>>>> Thanks
>>>>>
>>>>> Gary
>>>>>
>>>>>
>>>>>
>>>>> *From: *Alex Evonosky <alex.evono...@gmail.com>
>>>>> *Date: *Sunday, June 18, 2017 at 5:04 PM
>>>>> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org>
>>>>> *Subject: *[Openstack] Routed provider networks
>>>>>
>>>>>
>>>>>
>>>>> Hello-
>>>>>
>>>>>
>>>>>
>>>>> I wanted to test the routed provider networks of Ocata, and following
>>>>> the example config:
>>>>>
>>>>>
>>>>>
>>>>> https://docs.openstack.org/ocata/networking-guide/config-rou
>>>>> ted-networks.html
>>>>>
>>>>>
>>>>>
>>>>> I typed in the following on my controller node:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> @openstack-controller1:~# openstack network create --share
>>>>> --provider-physical-network provider1 --provider-network-type vlan
>>>>> --provider-segment 2016 multisegment1
>>>>>
>>>>>
>>>>>
>>>>> and I receive this:
>>>>>
>>>>>
>>>>>
>>>>> *Error while executing command: Bad Request*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Is there a log that may show what this error is referring to?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ___
>>>> Mailing list: http://lists.openstack.org/cgi
>>>> -bin/mailman/listinfo/openstack
>>>> Post to : openstack@lists.openstack.org
>>>> Unsubscribe : http://lists.openstack.org/cgi
>>>> -bin/mailman/listinfo/openstack
>>>>
>>>>
>>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Remo Mattei 
You need to enable the VLAN option restart neutron and then you are good to go!

> On Jun 18, 2017, at 9:08 AM, Kevin Benton <ke...@benton.pub> wrote:
> 
> Ok. So the actual error message is "Invalid input for operation: 
> physical_network 'provider1' unknown  for VLAN provider network.".
> 
> That means that in your Neutron server configuration file under the 
> [ml2_type_vlan] section you need to add 'provider1' to the 
> 'network_vlan_ranges' option. 
> 
> 
> 
> On Sun, Jun 18, 2017 at 9:04 AM, Alex Evonosky <alex.evono...@gmail.com 
> <mailto:alex.evono...@gmail.com>> wrote:
> Kevin-
> 
> Thank you for the tip.  The Debug is attached as well.
> 
> Thank you.
> 
> On Sun, Jun 18, 2017 at 11:54 AM, Kevin Benton <ke...@benton.pub 
> <mailto:ke...@benton.pub>> wrote:
> The openstack command should have an option to enable debugging so you can 
> get the error message. Try openstack --debug
> 
> 
> 
> On Sun, Jun 18, 2017 at 7:27 AM, Alex Evonosky <alex.evono...@gmail.com 
> <mailto:alex.evono...@gmail.com>> wrote:
> Gary-
> 
> Thank you for the feedback.  I issued the command while tailing the log:
> 
> 2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource 
> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66 
> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The 
> server could not comply with the request since it is either malformed or 
> otherwise incorrect.
> 2017-06-18 10:24:51.843 12018 INFO neutron.wsgi 
> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66 
> 664dc5e6023140eca0faeb2d0ecc31c2 - 
> 
> 
> As for the ocata config, this was built by using the ocata:
> 
> https://docs.openstack.org/ocata/install-guide-ubuntu/ 
> <https://docs.openstack.org/ocata/install-guide-ubuntu/>
> 
> 
> Thank you.
> 
> 
> 
> 
> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com 
> <mailto:gkot...@vmware.com>> wrote:
> Hi,
> 
> Please look in /var/log/neutron/neutron-server.log
> 
> That should provide and exception trace
> 
> Thanks
> 
> Gary
> 
>  
> 
> From: Alex Evonosky <alex.evono...@gmail.com <mailto:alex.evono...@gmail.com>>
> Date: Sunday, June 18, 2017 at 5:04 PM
> To: "openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>" 
> <openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>>
> Subject: [Openstack] Routed provider networks
> 
>  
> 
> Hello-
> 
>  
> 
> I wanted to test the routed provider networks of Ocata, and following the 
> example config:
> 
>  
> 
> https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html 
> <https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html>
>  
> 
> I typed in the following on my controller node:
> 
>  
> 
>  
> 
> @openstack-controller1:~# openstack network create --share 
> --provider-physical-network provider1 --provider-network-type vlan 
> --provider-segment 2016 multisegment1
> 
>  
> 
> and I receive this:
> 
>  
> 
> Error while executing command: Bad Request
> 
>  
> 
>  
> 
> Is there a log that may show what this error is referring to?
> 
>  
> 
>  
> 
> Thank you.
> 
>  
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> Post to : openstack@lists.openstack.org 
> <mailto:openstack@lists.openstack.org>
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> 
> 
> 
> 
> !DSPAM:1,5946a8b7174771029252334! 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
> !DSPAM:1,5946a8b7174771029252334!

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Alex Evonosky 
Kevin-

Thank you for the tip.  The Debug is attached as well.

Thank you.

On Sun, Jun 18, 2017 at 11:54 AM, Kevin Benton <ke...@benton.pub> wrote:

> The openstack command should have an option to enable debugging so you can
> get the error message. Try openstack --debug
>
>
>
> On Sun, Jun 18, 2017 at 7:27 AM, Alex Evonosky <alex.evono...@gmail.com>
> wrote:
>
>> Gary-
>>
>> Thank you for the feedback.  I issued the command while tailing the log:
>>
>> *2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource
>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The
>> server could not comply with the request since it is either malformed or
>> otherwise incorrect.*
>> *2017-06-18 10:24:51.843 12018 INFO neutron.wsgi
>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>> 664dc5e6023140eca0faeb2d0ecc31c2 - *
>>
>>
>> As for the ocata config, this was built by using the ocata:
>>
>> https://docs.openstack.org/ocata/install-guide-ubuntu/
>>
>>
>> Thank you.
>>
>>
>>
>>
>> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com> wrote:
>>
>>> Hi,
>>>
>>> Please look in /var/log/neutron/neutron-server.log
>>>
>>> That should provide and exception trace
>>>
>>> Thanks
>>>
>>> Gary
>>>
>>>
>>>
>>> *From: *Alex Evonosky <alex.evono...@gmail.com>
>>> *Date: *Sunday, June 18, 2017 at 5:04 PM
>>> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org>
>>> *Subject: *[Openstack] Routed provider networks
>>>
>>>
>>>
>>> Hello-
>>>
>>>
>>>
>>> I wanted to test the routed provider networks of Ocata, and following
>>> the example config:
>>>
>>>
>>>
>>> https://docs.openstack.org/ocata/networking-guide/config-rou
>>> ted-networks.html
>>>
>>>
>>>
>>> I typed in the following on my controller node:
>>>
>>>
>>>
>>>
>>>
>>> @openstack-controller1:~# openstack network create --share
>>> --provider-physical-network provider1 --provider-network-type vlan
>>> --provider-segment 2016 multisegment1
>>>
>>>
>>>
>>> and I receive this:
>>>
>>>
>>>
>>> *Error while executing command: Bad Request*
>>>
>>>
>>>
>>>
>>>
>>> Is there a log that may show what this error is referring to?
>>>
>>>
>>>
>>>
>>>
>>> Thank you.
>>>
>>>
>>>
>>
>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>>
>
openstack --debug network create --share --provider-physical-network provider1 
--provider-network-type vlan --provider-segment 2016 multisegment1
START with options: [u'--debug', u'network', u'create', u'--share', 
u'--provider-physical-network', u'provider1', u'--provider-network-type', 
u'vlan', u'--provider-segment', u'2016', u'multisegment1']
options: Namespace(access_key='', access_secret='***', access_token='***', 
access_token_endpoint='', access_token_type='', auth_type='', 
auth_url='http://controller:35357/v3', cacert=None, cert='', client_id='', 
client_secret='***', cloud='', code='', consumer_key='', consumer_secret='***', 
debug=True, default_domain='default', default_domain_id='', 
default_domain_name='', deferred_help=False, discovery_endpoint='', 
domain_id='', domain_name='', endpoint='', identity_provider='', 
identity_provider_url='', insecure=None, interface='', key='', log_file=None, 
old_profile=None, openid_scope='', os_beta_command=False, 
os_compute_api_version='', os_dns_api_version='2', os_identity_api_version='3', 
os_image_api_version='2', os_network_api_version='', os_object_api_version='', 
os_orchestration_api_version='1', os_project_id=None, os_project_name=None, 
os_volume_api_version='', passcode='', password='***', profile=None, 
project_domain_id='', project_domain_name='Default', project_id='', 
project_name='admin', protocol='', redirect_uri='', region_name='', 
timing=False, token='***', trust_id='', url='', user_domain_id='', 
user_domain_name='Default', user_id='', username='admin', verbose_le

Re: [Openstack] Routed provider networks

2017-06-18 Thread Gary Kotton 
Hi,
Is there any trace? That will help troubleshoot.
Thanks
gary

From: Alex Evonosky <alex.evono...@gmail.com>
Date: Sunday, June 18, 2017 at 5:27 PM
To: Gary Kotton <gkot...@vmware.com>
Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>
Subject: Re: [Openstack] Routed provider networks

Gary-

Thank you for the feedback.  I issued the command while tailing the log:

2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource 
[req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66 
664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The 
server could not comply with the request since it is either malformed or 
otherwise incorrect.
2017-06-18 10:24:51.843 12018 INFO neutron.wsgi 
[req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66 
664dc5e6023140eca0faeb2d0ecc31c2 -


As for the ocata config, this was built by using the ocata:

https://docs.openstack.org/ocata/install-guide-ubuntu/


Thank you.




On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton 
<gkot...@vmware.com<mailto:gkot...@vmware.com>> wrote:
Hi,
Please look in /var/log/neutron/neutron-server.log
That should provide and exception trace
Thanks
Gary

From: Alex Evonosky <alex.evono...@gmail.com<mailto:alex.evono...@gmail.com>>
Date: Sunday, June 18, 2017 at 5:04 PM
To: "openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>" 
<openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>>
Subject: [Openstack] Routed provider networks

Hello-

I wanted to test the routed provider networks of Ocata, and following the 
example config:

https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html

I typed in the following on my controller node:


@openstack-controller1:~# openstack network create --share 
--provider-physical-network provider1 --provider-network-type vlan 
--provider-segment 2016 multisegment1

and I receive this:

Error while executing command: Bad Request


Is there a log that may show what this error is referring to?


Thank you.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Kevin Benton 
Ok. So the actual error message is "Invalid input for operation:
physical_network 'provider1' unknown  for VLAN provider network.".

That means that in your Neutron server configuration file under the
[ml2_type_vlan] section you need to add 'provider1' to the
'network_vlan_ranges' option.



On Sun, Jun 18, 2017 at 9:04 AM, Alex Evonosky <alex.evono...@gmail.com>
wrote:

> Kevin-
>
> Thank you for the tip.  The Debug is attached as well.
>
> Thank you.
>
> On Sun, Jun 18, 2017 at 11:54 AM, Kevin Benton <ke...@benton.pub> wrote:
>
>> The openstack command should have an option to enable debugging so you
>> can get the error message. Try openstack --debug
>>
>>
>>
>> On Sun, Jun 18, 2017 at 7:27 AM, Alex Evonosky <alex.evono...@gmail.com>
>> wrote:
>>
>>> Gary-
>>>
>>> Thank you for the feedback.  I issued the command while tailing the log:
>>>
>>> *2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource
>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>>> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The
>>> server could not comply with the request since it is either malformed or
>>> otherwise incorrect.*
>>> *2017-06-18 10:24:51.843 12018 INFO neutron.wsgi
>>> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
>>> 664dc5e6023140eca0faeb2d0ecc31c2 - *
>>>
>>>
>>> As for the ocata config, this was built by using the ocata:
>>>
>>> https://docs.openstack.org/ocata/install-guide-ubuntu/
>>>
>>>
>>> Thank you.
>>>
>>>
>>>
>>>
>>> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Please look in /var/log/neutron/neutron-server.log
>>>>
>>>> That should provide and exception trace
>>>>
>>>> Thanks
>>>>
>>>> Gary
>>>>
>>>>
>>>>
>>>> *From: *Alex Evonosky <alex.evono...@gmail.com>
>>>> *Date: *Sunday, June 18, 2017 at 5:04 PM
>>>> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org>
>>>> *Subject: *[Openstack] Routed provider networks
>>>>
>>>>
>>>>
>>>> Hello-
>>>>
>>>>
>>>>
>>>> I wanted to test the routed provider networks of Ocata, and following
>>>> the example config:
>>>>
>>>>
>>>>
>>>> https://docs.openstack.org/ocata/networking-guide/config-rou
>>>> ted-networks.html
>>>>
>>>>
>>>>
>>>> I typed in the following on my controller node:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> @openstack-controller1:~# openstack network create --share
>>>> --provider-physical-network provider1 --provider-network-type vlan
>>>> --provider-segment 2016 multisegment1
>>>>
>>>>
>>>>
>>>> and I receive this:
>>>>
>>>>
>>>>
>>>> *Error while executing command: Bad Request*
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Is there a log that may show what this error is referring to?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thank you.
>>>>
>>>>
>>>>
>>>
>>>
>>> ___
>>> Mailing list: http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe : http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>>
>>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Kevin Benton 
The openstack command should have an option to enable debugging so you can
get the error message. Try openstack --debug



On Sun, Jun 18, 2017 at 7:27 AM, Alex Evonosky <alex.evono...@gmail.com>
wrote:

> Gary-
>
> Thank you for the feedback.  I issued the command while tailing the log:
>
> *2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource
> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
> 664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The
> server could not comply with the request since it is either malformed or
> otherwise incorrect.*
> *2017-06-18 10:24:51.843 12018 INFO neutron.wsgi
> [req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
> 664dc5e6023140eca0faeb2d0ecc31c2 - *
>
>
> As for the ocata config, this was built by using the ocata:
>
> https://docs.openstack.org/ocata/install-guide-ubuntu/
>
>
> Thank you.
>
>
>
>
> On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com> wrote:
>
>> Hi,
>>
>> Please look in /var/log/neutron/neutron-server.log
>>
>> That should provide and exception trace
>>
>> Thanks
>>
>> Gary
>>
>>
>>
>> *From: *Alex Evonosky <alex.evono...@gmail.com>
>> *Date: *Sunday, June 18, 2017 at 5:04 PM
>> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org>
>> *Subject: *[Openstack] Routed provider networks
>>
>>
>>
>> Hello-
>>
>>
>>
>> I wanted to test the routed provider networks of Ocata, and following the
>> example config:
>>
>>
>>
>> https://docs.openstack.org/ocata/networking-guide/config-rou
>> ted-networks.html
>>
>>
>>
>> I typed in the following on my controller node:
>>
>>
>>
>>
>>
>> @openstack-controller1:~# openstack network create --share
>> --provider-physical-network provider1 --provider-network-type vlan
>> --provider-segment 2016 multisegment1
>>
>>
>>
>> and I receive this:
>>
>>
>>
>> *Error while executing command: Bad Request*
>>
>>
>>
>>
>>
>> Is there a log that may show what this error is referring to?
>>
>>
>>
>>
>>
>> Thank you.
>>
>>
>>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Routed provider networks

2017-06-18 Thread Alex Evonosky 
Gary-

Thank you for the feedback.  I issued the command while tailing the log:

*2017-06-18 10:24:51.841 12018 INFO neutron.api.v2.resource
[req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
664dc5e6023140eca0faeb2d0ecc31c2 - - -] create failed (client error): The
server could not comply with the request since it is either malformed or
otherwise incorrect.*
*2017-06-18 10:24:51.843 12018 INFO neutron.wsgi
[req-da8fa8be-1cae-4b5e-a1cf-2206a284476a 7e7176b79f94483c8b802a7004466e66
664dc5e6023140eca0faeb2d0ecc31c2 - *


As for the ocata config, this was built by using the ocata:

https://docs.openstack.org/ocata/install-guide-ubuntu/


Thank you.




On Sun, Jun 18, 2017 at 10:17 AM, Gary Kotton <gkot...@vmware.com> wrote:

> Hi,
>
> Please look in /var/log/neutron/neutron-server.log
>
> That should provide and exception trace
>
> Thanks
>
> Gary
>
>
>
> *From: *Alex Evonosky <alex.evono...@gmail.com>
> *Date: *Sunday, June 18, 2017 at 5:04 PM
> *To: *"openstack@lists.openstack.org" <openstack@lists.openstack.org>
> *Subject: *[Openstack] Routed provider networks
>
>
>
> Hello-
>
>
>
> I wanted to test the routed provider networks of Ocata, and following the
> example config:
>
>
>
> https://docs.openstack.org/ocata/networking-guide/config-
> routed-networks.html
>
>
>
> I typed in the following on my controller node:
>
>
>
>
>
> @openstack-controller1:~# openstack network create --share
> --provider-physical-network provider1 --provider-network-type vlan
> --provider-segment 2016 multisegment1
>
>
>
> and I receive this:
>
>
>
> *Error while executing command: Bad Request*
>
>
>
>
>
> Is there a log that may show what this error is referring to?
>
>
>
>
>
> Thank you.
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Routed provider networks

2017-06-18 Thread Alex Evonosky 
Hello-

I wanted to test the routed provider networks of Ocata, and following the
example config:

https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html

I typed in the following on my controller node:


@openstack-controller1:~# openstack network create --share
--provider-physical-network provider1 --provider-network-type vlan
--provider-segment 2016 multisegment1

and I receive this:


*Error while executing command: Bad Request*


Is there a log that may show what this error is referring to?


Thank you.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-23 Thread Kevin Benton 
>Then describing the 'segment ID' as a VLAN ID

Segment ID is not a VLAN ID. A segment ID is a UUID for a segment, which
can contain a segmentation ID of a VLAN ID or VXLAN VNI or it might even be
a flat network.

It is unfortunate that we have both segment ID and segmentation ID, which
is what let to your confusion. The first uniquely identifies the segment,
the second describes how things will be encapsulated on the wire. I think
updating the docs to refer to the first as segment UUID might go a long
ways to help disambiguate.

>Then using the same 'VLAN ID' for different segments (even though its a
segment ID) on different networks implies that they might even be the same
VLAN, which they are not.

With VLANs the segmentation ID can be re-used on different physical
networks because they are not wired to the same L2 domain. They will have
different segment UUIDs and different 'physical_network' values, but may
have the same VLAN ID (segmentation_id).

On Tue, May 23, 2017 at 6:31 AM, Chris Marino  wrote:

> Thanks Kevin, very helpfulother comments in line.
> CM
>
> On Mon, May 22, 2017 at 9:15 PM, Kevin Benton  wrote:
>
>> On May 22, 2017 9:34 AM, "Chris Marino"  wrote:
>>
>> I'm digging into how Routed Provider Networks work and have some
>> questions as well. I will presenting at the OpenStack Meetup
>> on Wed on this and
>> want to make sure I have my facts straight..
>>
>> From the doc page
>> 
>>  it
>> shows a multi-segment network with segment 1 on 203.0.113.0/24 and
>> segment 2 on 198.51.100.0/24. It also suggests using the same VLAN ID
>> for these segments.
>>
>> I find both of these things really confusing.
>>
>>
>> What do you find confusing about this? It's a pretty standard L3 to ToR
>> and L2 in rack setup. L2 is limited to the rack so you can use or not use
>> whatever VLANs in that scope. We can fix the docs to clear up whatever
>> confusion you have.
>>
>
> My confusion was based on my somewhat narrow understanding of the use
> case. My thinking was that the current L2 provider networks would be cast
> as set of L2 segments (with contiguous CIDRs) on an L3 network. Seeing both
> the 203. and 198. networks getting consolidated into a single network is
> pretty disorienting. Together they are not a single network by the
> traditional definition of a network. Then describing the 'segment ID' as a
> VLAN ID was confusing for two reasons. First, it carries forward the idea
> that the segments are VLANs, which they might be, but don't have to be.
> Then using the same 'VLAN ID' for different segments (even though its a
> segment ID) on different networks implies that they might even be the same
> VLAN, which they are not.
>
>
>> But ignoring that for a minute, I'm more interested in the expected use
>> case for this feature. I see from the original spec/blueprint
>> 
>>  that the goal was to allow for a single Provider Network to be made up
>> from multiple network segments, where external routing provided
>> connectivity among the segments. And Routed Provider Networks provide
>> this.  Great.
>>
>> But the use cases I'm curious about are where the operator wants to take
>> their current L2/VLAN Provider Networks, but deploy it as an L3 Provider
>> Network. Same CIDR as the L2 provider network, but in a fully routed
>> deployment (i.e. no L2 adjacency). It might be L3 to the ToR and (untagged)
>> L2 to the host. Or L3 to the host.
>>
>> Both of these configurations are gaining popularity and wondering how
>> they would need to be configured. For the L3 to ToR, the network segments
>> would have to be split across the ToRs as described in the doc, but what
>> about L3 to host? Guessing a segment per host, but wondering how practical
>> that's going to be without better coordination of IP/segments with Nova?
>>
>>
>> L3 to the host and one segment per host is possible, but it's going to
>> have a severe limitation of not being able to migrate VMs without an IP
>> change. To get migration at that point you will need some form of dynamic
>> routing.
>>
>
> Yes, dynamic routing is going to help here as well as the config/setup.
>
>
>>
>> L3 to ToR and L2 in rack is definitely the target use case as of now.
>>
>
> Yes, I see that more clearly now.
>
>
>>
>> On May 22, 2017 9:34 AM, "Chris Marino"  wrote:
>>
>>> I'm digging into how Routed Provider Networks work and have some
>>> questions as well. I will presenting at the OpenStack Meetup
>>> on Wed on this and
>>> want to make sure I have my facts straight..
>>>
>>> From the doc page
>>> 
>>>  it
>>> shows a multi-segment

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-23 Thread Sławek Kapłoński 
Hello,

Vrack based networks are little bit different. We made it by self in OVH. It 
allows users to create tenant networks and connect them with e.g. dedicated 
servers. From Openstack user point of view it is similar to vlan network but 
it’s done littlebit different. Traffic from host in different racks can be 
tagged with different vlan id for ports from same network.
For user it’s L2 network everywhere.

—
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl




> Wiadomość napisana przez Chris Marino  w dniu 23.05.2017, o 
> godz. 17:10:
> 
> John, not really familiar with the OVH offering, but my quick scan indicated 
> their vRack is a collection of servers on one or more VLANs.  Doubt that 
> these vRacks are tied in any way to actual physical racks. My use of the term 
> 'top of rack' and ToR is meant to be the physical devices and would not apply 
> to these virtual racks.
> 
> CM
> ᐧ
> 
> On Tue, May 23, 2017 at 7:45 AM, John Griessen  wrote:
> On 05/23/2017 08:31 AM, Chris Marino wrote:
> L3 to ToR and L2 in rack
> 
> So, when you refer to providers of VMs do you still use these terms?  ovh.com 
> offers VMs built on openstack
> where one can create a vrack, (virtual rack). Does L3 to top of rack and L2 
> in rack apply to such vracks,
> or only physical networks.
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



signature.asc
Description: Message signed with OpenPGP
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-23 Thread Chris Marino 
John, not really familiar with the OVH offering, but my quick scan
indicated their vRack is a
collection of servers on one or more VLANs.  Doubt that these vRacks are
tied in any way to actual physical racks. My use of the term 'top of rack'
and ToR is meant to be the physical devices and would not apply to these
virtual racks.

CM
ᐧ

On Tue, May 23, 2017 at 7:45 AM, John Griessen  wrote:

> On 05/23/2017 08:31 AM, Chris Marino wrote:
>
>> L3 to ToR and L2 in rack
>>
>
> So, when you refer to providers of VMs do you still use these terms?
> ovh.com offers VMs built on openstack
> where one can create a vrack, (virtual rack). Does L3 to top of rack and
> L2 in rack apply to such vracks,
> or only physical networks.
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-23 Thread Chris Marino 
Thanks Kevin, very helpfulother comments in line.
CM

On Mon, May 22, 2017 at 9:15 PM, Kevin Benton  wrote:

> On May 22, 2017 9:34 AM, "Chris Marino"  wrote:
>
> I'm digging into how Routed Provider Networks work and have some questions
> as well. I will presenting at the OpenStack Meetup
> on Wed on this and
> want to make sure I have my facts straight..
>
> From the doc page
> 
>  it
> shows a multi-segment network with segment 1 on 203.0.113.0/24 and
> segment 2 on 198.51.100.0/24. It also suggests using the same VLAN ID for
> these segments.
>
> I find both of these things really confusing.
>
>
> What do you find confusing about this? It's a pretty standard L3 to ToR
> and L2 in rack setup. L2 is limited to the rack so you can use or not use
> whatever VLANs in that scope. We can fix the docs to clear up whatever
> confusion you have.
>

My confusion was based on my somewhat narrow understanding of the use case.
My thinking was that the current L2 provider networks would be cast as set
of L2 segments (with contiguous CIDRs) on an L3 network. Seeing both the
203. and 198. networks getting consolidated into a single network is pretty
disorienting. Together they are not a single network by the traditional
definition of a network. Then describing the 'segment ID' as a VLAN ID was
confusing for two reasons. First, it carries forward the idea that the
segments are VLANs, which they might be, but don't have to be. Then using
the same 'VLAN ID' for different segments (even though its a segment ID) on
different networks implies that they might even be the same VLAN, which
they are not.


> But ignoring that for a minute, I'm more interested in the expected use
> case for this feature. I see from the original spec/blueprint
> 
>  that the goal was to allow for a single Provider Network to be made up
> from multiple network segments, where external routing provided
> connectivity among the segments. And Routed Provider Networks provide
> this.  Great.
>
> But the use cases I'm curious about are where the operator wants to take
> their current L2/VLAN Provider Networks, but deploy it as an L3 Provider
> Network. Same CIDR as the L2 provider network, but in a fully routed
> deployment (i.e. no L2 adjacency). It might be L3 to the ToR and (untagged)
> L2 to the host. Or L3 to the host.
>
> Both of these configurations are gaining popularity and wondering how they
> would need to be configured. For the L3 to ToR, the network segments would
> have to be split across the ToRs as described in the doc, but what about L3
> to host? Guessing a segment per host, but wondering how practical that's
> going to be without better coordination of IP/segments with Nova?
>
>
> L3 to the host and one segment per host is possible, but it's going to
> have a severe limitation of not being able to migrate VMs without an IP
> change. To get migration at that point you will need some form of dynamic
> routing.
>

Yes, dynamic routing is going to help here as well as the config/setup.


>
> L3 to ToR and L2 in rack is definitely the target use case as of now.
>

Yes, I see that more clearly now.


>
> On May 22, 2017 9:34 AM, "Chris Marino"  wrote:
>
>> I'm digging into how Routed Provider Networks work and have some
>> questions as well. I will presenting at the OpenStack Meetup
>> on Wed on this and
>> want to make sure I have my facts straight..
>>
>> From the doc page
>> 
>>  it
>> shows a multi-segment network with segment 1 on 203.0.113.0/24 and
>> segment 2 on 198.51.100.0/24. It also suggests using the same VLAN ID
>> for these segments.
>>
>> I find both of these things really confusing. But ignoring that for a
>> minute, I'm more interested in the expected use case for this feature. I
>> see from the original spec/blueprint
>> 
>>  that the
>> goal was to allow for a single Provider Network to be made up from multiple
>> network segments, where external routing provided connectivity among the
>> segments. And Routed Provider Networks provide this.  Great.
>>
>> But the use cases I'm curious about are where the operator wants to take
>> their current L2/VLAN Provider Networks, but deploy it as an L3 Provider
>> Network. Same CIDR as the L2 provider network, but in a fully routed
>> deployment (i.e. no L2 adjacency). It might be L3 to the ToR and (untagged)
>> L2 to the host. Or L3 to the host.
>>
>> Both of these configurations are gaining popularity and wondering how
>> they would need to be configured. For the L3 to ToR, the network

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-22 Thread Kevin Benton 
On May 22, 2017 9:34 AM, "Chris Marino"  wrote:

I'm digging into how Routed Provider Networks work and have some questions
as well. I will presenting at the OpenStack Meetup
on Wed on this and want
to make sure I have my facts straight..

>From the doc page

it
shows a multi-segment network with segment 1 on 203.0.113.0/24 and segment
2 on 198.51.100.0/24. It also suggests using the same VLAN ID for these
segments.

I find both of these things really confusing.


What do you find confusing about this? It's a pretty standard L3 to ToR and
L2 in rack setup. L2 is limited to the rack so you can use or not use
whatever VLANs in that scope. We can fix the docs to clear up whatever
confusion you have.

But ignoring that for a minute, I'm more interested in the expected use
case for this feature. I see from the original spec/blueprint

that the
goal was to allow for a single Provider Network to be made up from multiple
network segments, where external routing provided connectivity among the
segments. And Routed Provider Networks provide this.  Great.

But the use cases I'm curious about are where the operator wants to take
their current L2/VLAN Provider Networks, but deploy it as an L3 Provider
Network. Same CIDR as the L2 provider network, but in a fully routed
deployment (i.e. no L2 adjacency). It might be L3 to the ToR and (untagged)
L2 to the host. Or L3 to the host.

Both of these configurations are gaining popularity and wondering how they
would need to be configured. For the L3 to ToR, the network segments would
have to be split across the ToRs as described in the doc, but what about L3
to host? Guessing a segment per host, but wondering how practical that's
going to be without better coordination of IP/segments with Nova?


L3 to the host and one segment per host is possible, but it's going to have
a severe limitation of not being able to migrate VMs without an IP change.
To get migration at that point you will need some form of dynamic routing.

L3 to ToR and L2 in rack is definitely the target use case as of now.

On May 22, 2017 9:34 AM, "Chris Marino"  wrote:

> I'm digging into how Routed Provider Networks work and have some questions
> as well. I will presenting at the OpenStack Meetup
> on Wed on this and
> want to make sure I have my facts straight..
>
> From the doc page
> 
>  it
> shows a multi-segment network with segment 1 on 203.0.113.0/24 and
> segment 2 on 198.51.100.0/24. It also suggests using the same VLAN ID for
> these segments.
>
> I find both of these things really confusing. But ignoring that for a
> minute, I'm more interested in the expected use case for this feature. I
> see from the original spec/blueprint
> 
>  that the
> goal was to allow for a single Provider Network to be made up from multiple
> network segments, where external routing provided connectivity among the
> segments. And Routed Provider Networks provide this.  Great.
>
> But the use cases I'm curious about are where the operator wants to take
> their current L2/VLAN Provider Networks, but deploy it as an L3 Provider
> Network. Same CIDR as the L2 provider network, but in a fully routed
> deployment (i.e. no L2 adjacency). It might be L3 to the ToR and (untagged)
> L2 to the host. Or L3 to the host.
>
> Both of these configurations are gaining popularity and wondering how they
> would need to be configured. For the L3 to ToR, the network segments would
> have to be split across the ToRs as described in the doc, but what about L3
> to host? Guessing a segment per host, but wondering how practical that's
> going to be without better coordination of IP/segments with Nova?
>
> CM
> ᐧ
>
> On Sun, May 21, 2017 at 6:12 AM, Alex Evonosky 
> wrote:
>
>> Thank you Yura.
>>
>> A
>>
>> On Thu, May 18, 2017 at 3:24 AM, Yura Poltoratskiy > > wrote:
>>
>>> Hi
>>>
>>> On 17.05.2017 21:56, Alex Evonosky wrote:
>>>
 Hello fellow Openstackers-

 I have a quick question regarding routed provider networks.  I am
 looking at this
 page: https://docs.openstack.org/ocata/networking-guide/config-rou
 ted-networks.html

 I configured the controller as stated in the docs, however this line is
 somewhat vaugue:

 "


   Network or compute nodes¶
   

   * Configure the layer-2 agent on each node to map one or more segments
 to the

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-22 Thread Chris Marino 
I'm digging into how Routed Provider Networks work and have some questions
as well. I will presenting at the OpenStack Meetup
on Wed on this and want
to make sure I have my facts straight..

>From the doc page

it
shows a multi-segment network with segment 1 on 203.0.113.0/24 and segment
2 on 198.51.100.0/24. It also suggests using the same VLAN ID for these
segments.

I find both of these things really confusing. But ignoring that for a
minute, I'm more interested in the expected use case for this feature. I
see from the original spec/blueprint

that the
goal was to allow for a single Provider Network to be made up from multiple
network segments, where external routing provided connectivity among the
segments. And Routed Provider Networks provide this.  Great.

But the use cases I'm curious about are where the operator wants to take
their current L2/VLAN Provider Networks, but deploy it as an L3 Provider
Network. Same CIDR as the L2 provider network, but in a fully routed
deployment (i.e. no L2 adjacency). It might be L3 to the ToR and (untagged)
L2 to the host. Or L3 to the host.

Both of these configurations are gaining popularity and wondering how they
would need to be configured. For the L3 to ToR, the network segments would
have to be split across the ToRs as described in the doc, but what about L3
to host? Guessing a segment per host, but wondering how practical that's
going to be without better coordination of IP/segments with Nova?

CM
ᐧ

On Sun, May 21, 2017 at 6:12 AM, Alex Evonosky 
wrote:

> Thank you Yura.
>
> A
>
> On Thu, May 18, 2017 at 3:24 AM, Yura Poltoratskiy 
> wrote:
>
>> Hi
>>
>> On 17.05.2017 21:56, Alex Evonosky wrote:
>>
>>> Hello fellow Openstackers-
>>>
>>> I have a quick question regarding routed provider networks.  I am
>>> looking at this
>>> page: https://docs.openstack.org/ocata/networking-guide/config-rou
>>> ted-networks.html
>>>
>>> I configured the controller as stated in the docs, however this line is
>>> somewhat vaugue:
>>>
>>> "
>>>
>>>
>>>   Network or compute nodes¶
>>>   >> uted-networks.html#network-or-compute-nodes>
>>>
>>>   * Configure the layer-2 agent on each node to map one or more segments
>>> to the appropriate physical network bridge or interface and restart
>>> the agent."
>>>
>>>
>>> Which file am I editing on the compute nodes to answer the above
>>> question?
>>>
>> If you are using OpenVSwitch agent, then on compute/network node you
>> should modify:
>> /etc/neutron/plugins/ml2/openvswitch_agent.ini
>> /etc/neutron/plugins/ml2/ml2_conf.ini
>>
>>
>>>
>>> Thank you,
>>> A
>>>
>>>
>>> ___
>>> Mailing list: http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe : http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>>
>>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-21 Thread Alex Evonosky 
Thank you Yura.

A

On Thu, May 18, 2017 at 3:24 AM, Yura Poltoratskiy 
wrote:

> Hi
>
> On 17.05.2017 21:56, Alex Evonosky wrote:
>
>> Hello fellow Openstackers-
>>
>> I have a quick question regarding routed provider networks.  I am
>> looking at this
>> page: https://docs.openstack.org/ocata/networking-guide/config-rou
>> ted-networks.html
>>
>> I configured the controller as stated in the docs, however this line is
>> somewhat vaugue:
>>
>> "
>>
>>
>>   Network or compute nodes¶
>>   > uted-networks.html#network-or-compute-nodes>
>>
>>   * Configure the layer-2 agent on each node to map one or more segments
>> to the appropriate physical network bridge or interface and restart
>> the agent."
>>
>>
>> Which file am I editing on the compute nodes to answer the above question?
>>
> If you are using OpenVSwitch agent, then on compute/network node you
> should modify:
> /etc/neutron/plugins/ml2/openvswitch_agent.ini
> /etc/neutron/plugins/ml2/ml2_conf.ini
>
>
>>
>> Thank you,
>> A
>>
>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack Routed Provider Networks Question

2017-05-18 Thread Yura Poltoratskiy 

Hi

On 17.05.2017 21:56, Alex Evonosky wrote:

Hello fellow Openstackers-

I have a quick question regarding routed provider networks.  I am
looking at this
page: 
https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html

I configured the controller as stated in the docs, however this line is
somewhat vaugue:

"


  Network or compute nodes¶
  


  * Configure the layer-2 agent on each node to map one or more segments
to the appropriate physical network bridge or interface and restart
the agent."


Which file am I editing on the compute nodes to answer the above question?
If you are using OpenVSwitch agent, then on compute/network node you 
should modify:

/etc/neutron/plugins/ml2/openvswitch_agent.ini
/etc/neutron/plugins/ml2/ml2_conf.ini




Thank you,
A


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Openstack Routed Provider Networks Question

2017-05-17 Thread Alex Evonosky 
Hello fellow Openstackers-

I have a quick question regarding routed provider networks.  I am looking
at this page:
https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html

I configured the controller as stated in the docs, however this line is
somewhat vaugue:

"
Network or compute nodes¶


   - Configure the layer-2 agent on each node to map one or more segments
   to the appropriate physical network bridge or interface and restart the
   agent."


Which file am I editing on the compute nodes to answer the above question?


Thank you,
A
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack