<div dir="ltr">Thanks Adrian, imho making name as required can bring more convenient to end users because UUID is difficult to use. Without name, the end user need to retrieve the UUID of the bay/baymodel first before he did some operations for the bay/baymodel, its really time consuming. We can discuss more in this week's IRC meeting. Thanks.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-02 14:08 GMT+08:00 Adrian Otto <span dir="ltr"><<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div>-1. I disagree.</div>
<div><br>
</div>
<div>I am not convinced that requiring names is a good idea. I've asked several times why there is a desire to require names, and I'm not seeing any persuasive arguments that are not already addressed by UUIDs. We have UUID values to allow for acting upon an
individual resource. Names are there as a convenience. Requiring names, especially unique names, would make Magnum harder to use for API users driving Magnum from other systems. I want to keep the friction as low as possible.<br>
<br>
I'm fine with replacing "None" with an empty string.</div>
<div><br>
</div>
<div>Consistency with Nova would be a valid argument if we were being more restrictive, but that's not the case. We are more permissive. You can use Magnum in the same way you use Nova if you want, by adding names to all resources. I don't see the wisdom in
forcing that style of use without a technical reason for it.</div>
<div><br>
Thanks,</div>
<div><br>
<div>Adrian</div>
</div><div><div class="h5">
<div><br>
On May 31, 2015, at 4:43 PM, Jay Lau <<a href="mailto:jay.lau.513@gmail.com" target="_blank">jay.lau.513@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>
<div><br>
</div>
Just want to use ML to trigger more discussion here. There are now bugs/patches tracing this, but seems more discussions are needed before we come to a conclusion.<br>
<br>
<a href="https://bugs.launchpad.net/magnum/+bug/1453732" target="_blank">https://bugs.launchpad.net/magnum/+bug/1453732</a><br>
<a href="https://review.openstack.org/#/c/181839/" target="_blank">https://review.openstack.org/#/c/181839/</a><br>
<a href="https://review.openstack.org/#/c/181837/" target="_blank">https://review.openstack.org/#/c/181837/</a><br>
<a href="https://review.openstack.org/#/c/181847/" target="_blank">https://review.openstack.org/#/c/181847/</a><br>
<a href="https://review.openstack.org/#/c/181843/" target="_blank">https://review.openstack.org/#/c/181843/</a><br>
<br>
</div>
IMHO, making the Bay/Baymodel name as a MUST will bring more flexibility to end user as Magnum also support operating Bay/Baymodel via names and the name might be more meaningful to end users.<br>
<p>Perhaps we can borrow some iead from nova, the concept in magnum can be mapped to nova as following:</p>
<p>1) instance => bay<br>
2) flavor => baymodel</p>
<p>So I think that a solution might be as following:<br>
1) Make name as a MUST for both bay/baymodel<br>
2) Update magnum client to use following style for bay-create and baymodel-create: DO NOT add "--name" option</p>
<p>root@devstack007:/tmp# nova boot<br>
usage: nova boot [--flavor <flavor>] [--image <image>]<br>
[--image-with <key=value>] [--boot-volume <volume_id>]<br>
[--snapshot <snapshot_id>] [--min-count <number>]<br>
[--max-count <number>] [--meta <key=value>]<br>
[--file <dst-path=src-path>] [--key-name <key-name>]<br>
[--user-data <user-data>]<br>
[--availability-zone <availability-zone>]<br>
[--security-groups <security-groups>]<br>
[--block-device-mapping <dev-name=mapping>]<br>
[--block-device key1=value1[,key2=value2...]]<br>
[--swap <swap_size>]<br>
[--ephemeral size=<size>[,format=<format>]]<br>
[--hint <key=value>]<br>
[--nic <net-id=net-uuid,v4-fixed-ip=ip-addr,v6-fixed-ip=ip-addr,port-id=port-uuid>]<br>
[--config-drive <value>] [--poll]<br>
<name><br>
error: too few arguments<br>
Try 'nova help boot' for more information.<br>
root@devstack007:/tmp# nova flavor-create<br>
usage: nova flavor-create [--ephemeral <ephemeral>] [--swap <swap>]<br>
[--rxtx-factor <factor>] [--is-public <is-public>]<br>
<name> <id> <ram> <disk> <vcpus></p>
Please show your comments if any.<br>
</div>
<div>
<div>
<div><br>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>Thanks,<br>
<br>
</div>
Jay Lau (Guangya Liu)<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div></div><blockquote type="cite">
<div><span>__________________________________________________________________________</span><span class=""><br>
<span>OpenStack Development Mailing List (not for usage questions)</span><br>
<span>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br>
</span></div>
</blockquote>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Thanks,<br><br></div>Jay Lau (Guangya Liu)<br></div></div></div></div>
</div>