<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 15 September 2015 at 16:01, Monty Taylor <span dir="ltr"><<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>On 09/15/2015 06:16 PM, Armando M. wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>
<br>
<br>
On 15 September 2015 at 08:27, Mike Spreitzer <<a href="mailto:mspreitz@us.ibm.com" target="_blank">mspreitz@us.ibm.com</a><br></span>
<mailto:<a href="mailto:mspreitz@us.ibm.com" target="_blank">mspreitz@us.ibm.com</a>>> wrote:<br>
<br>
    Monty Taylor <<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a> <mailto:<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>>><span><br>
    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<br>
    places the Neutron CLI insists on a UUID when a name could be used.<br>
    Three cheers for any campaign to fix that.<br>
<br>
<br>
The client is not particularly tied to a specific version of the server,<br>
so we don't have a Juno version, or a Kilo version, etc. (even though<br>
they are aligned, see [1] for more details).<br>
<br>
Having said that, you could use names in place of uuids pretty much<br>
anywhere. If your experience says otherwise, please consider filing a<br>
bug against the client [2] and we'll get it fixed.<br>
</span></blockquote>
<br>
May just be a help-text bug in novaclient then:<br>
<br>
  --nic <net-id=net-uuid,v4-fixed-ip=ip-addr,v6-fixed-ip=ip-addr,port-id=port-uuid><br>
                                Create a NIC on the server. Specify option<br>
                                multiple times to create multiple NICs. net-<br>
                                id: attach NIC to network with this UUID<br>
                                (either port-id or net-id must be provided),<br>
                                v4-fixed-ip: IPv4 fixed address for NIC<br>
                                (optional), v6-fixed-ip: IPv6 fixed address<br>
                                for NIC (optional), port-id: attach NIC to<br>
                                port with this UUID (either port-id or net-id<br>
                                must be provided).<br></blockquote><div><br></div><div>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!</div><div><br></div><div>[1] <a href="https://bugs.launchpad.net/python-novaclient/+bug/1496180">https://bugs.launchpad.net/python-novaclient/+bug/1496180</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>
Thanks,<br>
Armando<br>
<br>
[1] <a href="https://launchpad.net/python-neutronclient/+series" rel="noreferrer" target="_blank">https://launchpad.net/python-neutronclient/+series</a><br>
[2] <a href="https://bugs.launchpad.net/python-neutronclient/+filebug" rel="noreferrer" target="_blank">https://bugs.launchpad.net/python-neutronclient/+filebug</a><br>
<br>
<br>
<br>
    And, yeah, creating VMs on a shared public network is good too.<br>
<br>
    Thanks,<br>
    mike<br>
<br>
    __________________________________________________________________________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe:<br>
    <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br></span>
    <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
    <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><span><br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</span></blockquote><div><div>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>