+1 about Jay option.
BTW, as nova and glance all allow same name for instance or image, So name
seems not need to be unique, it is OK I think.
Thanks
Best Wishes,
--------------------------------------------------------------------------------
Kai Qiang Wu (吴开强 Kennan）
IBM China System and Technology Lab, Beijing
E-mail: wk...@cn.ibm.com
Tel: 86-10-82451647
Address: Building 28(Ring Building), ZhongGuanCun Software Park,
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China
100193
--------------------------------------------------------------------------------
Follow your heart. You are miracle!
From: Jay Lau <jay.lau....@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 06/01/2015 11:17 PM
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
2015-06-01 21:54 GMT+08:00 Jay Pipes <jaypi...@gmail.com>:
On 05/31/2015 05:38 PM, Jay Lau wrote:
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.
https://bugs.launchpad.net/magnum/+bug/1453732
https://review.openstack.org/#/c/181839/
https://review.openstack.org/#/c/181837/
https://review.openstack.org/#/c/181847/
https://review.openstack.org/#/c/181843/
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.
Perhaps we can borrow some iead from nova, the concept in magnum can be
mapped to nova as following:
1) instance => bay
2) flavor => baymodel
So I think that a solution might be as following:
1) Make name as a MUST for both bay/baymodel
2) Update magnum client to use following style for bay-create and
baymodel-create: DO NOT add "--name" option
You should decide whether name would be unique -- either globally or
within a tenant.
Note that Nova's instance names (the display_name model field) are *not*
unique, neither globally nor within a tenant. I personally believe this
was a mistake.
The decision affects your data model and constraints.
Yes, my thinking is to enable Magnum has same behavior with nova. The name
can be managed by the end user and the end user can specify the name as
they want, it is end user's responsibility to make sure there are no
duplicate names. Actually, I think that the name do not need to be unique
but UUID.
Best,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks,
Jay Lau (Guangya Liu)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
