Open Stack

Hi,

Flavors are intended to be setup by the operator/admin only.  They
capture details of the load balancer offering and any local specific
configuration.  The intent here is the flavor options and descriptions
will be visible to end users, but creation/modification would require
an admin role.  End users will be able to specify the flavor they
would like to use for the load balancer at load balancer creation time
via the load balancer create API.

We are just now starting to work on providers.  The providers
implementation needs a spec and review process. I hope we can create
this spec and create the providers interface during the Queens series.

Michael


On Tue, Aug 15, 2017 at 7:09 PM, 何庆 <tsinghe.7 at gmail.com> wrote:
> Hi, I'm trying to figure out how the flavor will be implemented and have few
> questions about the flavor spec[1]
>
> 1. What does "RO" mean in API /flavors? Is it short for ReadOnly?
> In my understanding, user need create flavor by himself, so the flavor API
> should not be readonly.
>
> FLAVOR(/flavors)
>
> +-----------------+-------+---------+---------+------------+-----------------+
> |Attribute        |Type   |Access   |Default  |Validation/ |Description
> |
> |Name             |       |         |Value    |Conversion  |
> |
> +=================+=======+=========+=========+============+=================+
> |id               |string |RO, admin|generated|N/A         |identity
> |
> |                 |(UUID) |         |         |            |
> |
> +-----------------+-------+---------+---------+------------+-----------------+
> |name             |string |RO, admin|''       |string      |human-readable
> |
> |                 |       |         |         |            |name
> |
> +-----------------+-------+---------+---------+------------+-----------------+
> |description      |string |RO, admin|''       |string      |human-readable
> |
> |                 |       |         |         |            |description
> |
> +-----------------+-------+---------+---------+------------+-----------------+
> |enabled          |bool   |RO, admin|true     |bool        |toggle
> |
> |                 |       |         |         |            |
> |
> +-----------------+-------+---------+---------+------------+-----------------+
> |flavor_profile_id|string |RO, admin|         |string      |human-readable
> |
> |                 |       |         |         |
> |flavor_profile_id|
> +-----------------+-------+---------+---------+------------+-----------------+
>
> 2. Do we also need an API like /providers to query providers and metadata
> available？
>
>
>
> [1] https://review.openstack.org/#/c/392485/
>
>
> __________________________________________________________________________
> 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
>