[openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

Armando M. armamig at gmail.com
Wed Sep 16 00:02:29 UTC 2015


On 15 September 2015 at 16:01, Monty Taylor <mordred at inaugust.com> wrote:

> On 09/15/2015 06:16 PM, Armando M. wrote:
>
>>
>>
>> On 15 September 2015 at 08:27, Mike Spreitzer <mspreitz at us.ibm.com
>> <mailto:mspreitz at us.ibm.com>> wrote:
>>
>>     Monty Taylor <mordred at inaugust.com <mailto:mordred at inaugust.com>>
>>     wrote on 09/15/2015 11:04:07 AM:
>>
>>     > a) an update to python-novaclient to allow a named network to be
>> passed
>>     > to satisfy the "you have more than one network" - the nics
>> argument is
>>     > still useful for more complex things
>>
>>     I am not using the latest, but rather Juno.  I find that in many
>>     places the Neutron CLI insists on a UUID when a name could be used.
>>     Three cheers for any campaign to fix that.
>>
>>
>> The client is not particularly tied to a specific version of the server,
>> so we don't have a Juno version, or a Kilo version, etc. (even though
>> they are aligned, see [1] for more details).
>>
>> Having said that, you could use names in place of uuids pretty much
>> anywhere. If your experience says otherwise, please consider filing a
>> bug against the client [2] and we'll get it fixed.
>>
>
> May just be a help-text bug in novaclient then:
>
>   --nic
> <net-id=net-uuid,v4-fixed-ip=ip-addr,v6-fixed-ip=ip-addr,port-id=port-uuid>
>                                 Create a NIC on the server. Specify option
>                                 multiple times to create multiple NICs.
> net-
>                                 id: attach NIC to network with this UUID
>                                 (either port-id or net-id must be
> provided),
>                                 v4-fixed-ip: IPv4 fixed address for NIC
>                                 (optional), v6-fixed-ip: IPv6 fixed address
>                                 for NIC (optional), port-id: attach NIC to
>                                 port with this UUID (either port-id or
> net-id
>                                 must be provided).
>

Ok, if you're asking for the ability to boot network by name (assumed
that's unique), then that can be sorted. I filed a novaclient bug [1].
Volunteers welcome!

[1] https://bugs.launchpad.net/python-novaclient/+bug/1496180


>
>
>
> Thanks,
>> Armando
>>
>> [1] https://launchpad.net/python-neutronclient/+series
>> [2] https://bugs.launchpad.net/python-neutronclient/+filebug
>>
>>
>>
>>     And, yeah, creating VMs on a shared public network is good too.
>>
>>     Thanks,
>>     mike
>>
>>
>> __________________________________________________________________________
>>     OpenStack Development Mailing List (not for usage questions)
>>     Unsubscribe:
>>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
>> >
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150915/9ba41b91/attachment-0001.html>


More information about the OpenStack-dev mailing list