Thanks Eric, I see. Yes, this can make sure the user would not need to
contact the server using bay-show/baymode-show to get UUID of bay/baymodel,
but Magnum need to be updated to make the bay/baymodel uuid generate logic.
2015-06-05 13:42 GMT+08:00 Eric Windisch e...@windisch.us:
I think
it is different on every cloud.
Thanks,
Kevin
--
*From:* Jay Lau [jay.lau@gmail.com]
*Sent:* Tuesday, June 02, 2015 12:33 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Thanks Adrian, imho making name as required can bring more convenient to end
users because UUID is difficult
I think this is perfectly fine, as long as it's reasonably large and
the algorithm is sufficiently intelligent. The UUID algorithm is good at
this, for instance, although it fails at readability. Docker's is not
terribly great and could be limiting if you were looking to run several
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should
be a required option when creating a Bay/Baymodel
Thanks Adrian, imho making name as required can bring more
convenient to end users because UUID is difficult
Some comments and questions in line. Thanks.
2015-06-03 11:27 GMT+08:00 Adrian Otto adrian.o...@rackspace.com:
Eric,
On Jun 2, 2015, at 10:07 PM, Eric Windisch e...@windisch.us wrote:
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto adrian.o...@rackspace.com
wrote:
I have reflected on
--
*From:* Jay Lau [jay.lau@gmail.com]
*Sent:* Tuesday, June 02, 2015 12:33 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be
a required option when creating a Bay/Baymodel
Thanks Adrian, imho making
questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
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
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
Eric,
On Jun 2, 2015, at 10:07 PM, Eric Windisch
e...@windisch.usmailto:e...@windisch.us wrote:
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto
adrian.o...@rackspace.commailto:adrian.o...@rackspace.com wrote:
I have reflected on this further and offer this suggestion:
1) Add a feature to
: [openstack-dev] [Magnum] Does Bay/Baymodel name should be
a required option when creating a Bay/Baymodel
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
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto adrian.o...@rackspace.com
wrote:
I have reflected on this further and offer this suggestion:
1) Add a feature to Magnum to auto-generate human readable names, like
Docker does for un-named containers, and ElasticSearch does for naming
cluster
Lau [jay.lau@gmail.commailto:jay.lau@gmail.com]
Sent: Tuesday, June 02, 2015 12:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Thanks Adrian, imho
at 6:11 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
+1 about Jay option.
BTW
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, June 1, 2015 at 11:08 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when
that with a UUID
since it is different on every cloud.
Thanks,
Kevin
From: Jay Lau [jay.lau@gmail.com]
Sent: Tuesday, June 02, 2015 12:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name
: Steven Dake (stdake) [std...@cisco.com]
Sent: Tuesday, June 02, 2015 4:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Kennan,
Agree on no requirement
-1. I disagree.
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.
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.
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/
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
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required
option when creating a Bay/Baymodel
Just want to use ML to trigger more discussion here. There are now bugs
: Sunday, May 31, 2015 at 2:38 PM
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Just want to use ML to trigger more discussion here. There are now
bugs
-dev@lists.openstack.org
Date: Sunday, May 31, 2015 at 2:38 PM
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Just want to use ML to trigger more
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/
25 matches
Mail list logo
