<html><body><p><tt>"Fox, Kevin M" <Kevin.Fox@pnnl.gov> wrote on 09/15/2015 02:57:10 PM:<br><br>> From: "Fox, Kevin M" <Kevin.Fox@pnnl.gov></tt><br><tt>> To: "OpenStack Development Mailing List (not for usage questions)" <br>> <openstack-dev@lists.openstack.org></tt><br><tt>> Date: 09/15/2015 02:59 PM</tt><br><tt>> Subject: Re: [openstack-dev] [nova][neutron][devstack] New proposed <br>> 'default' network model</tt><br><tt>> <br>> Most projects let you specify a name, and only force you to use a <br>> uuid IFF there is a conflict, leaving it up to the user to decide if<br>> they want the ease of use of names and being careful to name things,<br>> or having to use uuid's and not.</tt><br><br><tt>That is how Neutron works as well. If it doesn't in some cases, then those are bugs that need to be filed and fixed.</tt><br><br><tt>mb@ubuntu14:~$ neutron net-create x1</tt><br><tt>Created a new network:</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>| Field | Value |</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>| admin_state_up | True |</tt><br><tt>| id | 02fd014d-3a84-463f-a158-317411528ff3 |</tt><br><tt>| mtu | 0 |</tt><br><tt>| name | x1 |</tt><br><tt>| port_security_enabled | True |</tt><br><tt>| provider:network_type | vxlan |</tt><br><tt>| provider:physical_network | |</tt><br><tt>| provider:segmentation_id | 1037 |</tt><br><tt>| router:external | False |</tt><br><tt>| shared | False |</tt><br><tt>| status | ACTIVE |</tt><br><tt>| subnets | |</tt><br><tt>| tenant_id | ce56abd5661f4140a5df98927a6f54d8 |</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>mb@ubuntu14:~$ neutron net-delete x1</tt><br><tt>Deleted network: x1</tt><br><br><tt>mb@ubuntu14:~$ neutron net-create x1</tt><br><tt>Created a new network:</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>| Field | Value |</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>| admin_state_up | True |</tt><br><tt>| id | db95539c-1c33-4791-a87f-608872ed3e86 |</tt><br><tt>| mtu | 0 |</tt><br><tt>| name | x1 |</tt><br><tt>| port_security_enabled | True |</tt><br><tt>| provider:network_type | vxlan |</tt><br><tt>| provider:physical_network | |</tt><br><tt>| provider:segmentation_id | 1010 |</tt><br><tt>| router:external | False |</tt><br><tt>| shared | False |</tt><br><tt>| status | ACTIVE |</tt><br><tt>| subnets | |</tt><br><tt>| tenant_id | ce56abd5661f4140a5df98927a6f54d8 |</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>mb@ubuntu14:~$ neutron net-create x1</tt><br><tt>Created a new network:</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>| Field | Value |</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>| admin_state_up | True |</tt><br><tt>| id | b2b3dd55-0f6f-46e7-aaef-c4a89a5d1ef9 |</tt><br><tt>| mtu | 0 |</tt><br><tt>| name | x1 |</tt><br><tt>| port_security_enabled | True |</tt><br><tt>| provider:network_type | vxlan |</tt><br><tt>| provider:physical_network | |</tt><br><tt>| provider:segmentation_id | 1071 |</tt><br><tt>| router:external | False |</tt><br><tt>| shared | False |</tt><br><tt>| status | ACTIVE |</tt><br><tt>| subnets | |</tt><br><tt>| tenant_id | ce56abd5661f4140a5df98927a6f54d8 |</tt><br><tt>+---------------------------+--------------------------------------+</tt><br><tt>mb@ubuntu14:~$ neutron net-delete x1</tt><br><tt>Multiple network matches found for name 'x1', use an ID to be more specific.</tt><br><tt>mb@ubuntu14:~$ neutron net-delete db95539c-1c33-4791-a87f-608872ed3e86</tt><br><tt>Deleted network: db95539c-1c33-4791-a87f-608872ed3e86</tt><br><tt>mb@ubuntu14:~$ neutron net-delete x1</tt><br><tt>Deleted network: x1</tt><br><tt>mb@ubuntu14:~$</tt><br><br><br><tt>Best,</tt><br><br><tt>Mohammad</tt><br><br><br><tt><br>> <br>> Neutron also has the odd wrinkle in that if your a cloud admin, it <br>> always gives you all the resources back in a listing rather then <br>> just the current tenant with a flag saying all.<br>> <br>> This means if you try to use the "default" security group for <br>> example, it may work as a user, and then fail as an admin on the <br>> same tenant. very annoying. :/<br>> <br>> I've had to work around that in heat templates before.<br>> <br>> Thanks,<br>> Kevin<br>> <br>> <br>> ________________________________________<br>> From: Matt Riedemann [mriedem@linux.vnet.ibm.com]<br>> Sent: Tuesday, September 15, 2015 11:28 AM<br>> To: openstack-dev@lists.openstack.org<br>> Subject: Re: [openstack-dev] [nova][neutron][devstack] New proposed <br>> 'default' network model<br>> <br>> On 9/15/2015 10:27 AM, Mike Spreitzer wrote:<br>> > Monty Taylor <mordred@inaugust.com> wrote on 09/15/2015 11:04:07 AM:<br>> ><br>> > > a) an update to python-novaclient to allow a named network to be passed<br>> > > to satisfy the "you have more than one network" - the nics argument is<br>> > > still useful for more complex things<br>> ><br>> > I am not using the latest, but rather Juno. I find that in many places<br>> > the Neutron CLI insists on a UUID when a name could be used. Three<br>> > cheers for any campaign to fix that.<br>> <br>> It's my understanding that network names in neutron, like security<br>> groups, are not unique, that's why you have to specify a UUID.<br>> <br>> ><br>> > And, yeah, creating VMs on a shared public network is good too.<br>> ><br>> > Thanks,<br>> > mike<br>> ><br>> ><br>> > __________________________________________________________________________<br>> > OpenStack Development Mailing List (not for usage questions)<br>> > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>> ><br>> <br>> --<br>> <br>> Thanks,<br>> <br>> Matt Riedemann<br>> <br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>> <br></tt><BR>
</body></html>