[openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel
Haiwei Xu
hai-xu at xr.jp.nec.com
Mon Jun 1 01:04:03 UTC 2015
+1 for Jay's suggestion.
xuhaiwei
-----Original Message-----
From: Davanum Srinivas [mailto:davanum at gmail.com]
Sent: Monday, June 01, 2015 8:26 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
+1 from me as well
On Sun, May 31, 2015 at 6:08 PM, Steven Dake (stdake) <stdake at cisco.com> wrote:
> Jay 513
>
> +1 on mandatory name requirement.
>
> From: Jay Lau <jay.lau.513 at gmail.com>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Date: Sunday, May 31, 2015 at 2:38 PM
> To: OpenStack Development Mailing List
> <openstack-dev at 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/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
>
> root at devstack007:/tmp# nova boot
> usage: nova boot [--flavor <flavor>] [--image <image>]
> [--image-with <key=value>] [--boot-volume <volume_id>]
> [--snapshot <snapshot_id>] [--min-count <number>]
> [--max-count <number>] [--meta <key=value>]
> [--file <dst-path=src-path>] [--key-name <key-name>]
> [--user-data <user-data>]
> [--availability-zone <availability-zone>]
> [--security-groups <security-groups>]
> [--block-device-mapping <dev-name=mapping>]
> [--block-device key1=value1[,key2=value2...]]
> [--swap <swap_size>]
> [--ephemeral size=<size>[,format=<format>]]
> [--hint <key=value>]
> [--nic
> <net-id=net-uuid,v4-fixed-ip=ip-addr,v6-fixed-ip=ip-addr,port-id=port-uuid>]
> [--config-drive <value>] [--poll]
> <name>
> error: too few arguments
> Try 'nova help boot' for more information.
> root at devstack007:/tmp# nova flavor-create
> usage: nova flavor-create [--ephemeral <ephemeral>] [--swap <swap>]
> [--rxtx-factor <factor>] [--is-public <is-public>]
> <name> <id> <ram> <disk> <vcpus>
>
> Please show your comments if any.
>
> --
> Thanks,
>
> Jay Lau (Guangya Liu)
>
>
> ______________________________________________________________________
> ____ 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
>
--
Davanum Srinivas :: https://twitter.com/dims
__________________________________________________________________________
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
More information about the OpenStack-dev
mailing list