Open Stack

On 17 May 2013 05:38, Russell Bryant <rbryant at redhat.com> wrote:

> On 05/16/2013 10:16 PM, Dan Smith wrote:
> > I think that the general consensus is that the notion of dynamic
> > flavors is an unfavorable approach. Since we happen to be having this
> > discussion while an API redesign is happening, I'd say the more
> > productive path forward is to figure out how we want per-instance usage
> > to be exposed which makes sense both with and without fine-grained
> > resource tweaks. Perhaps a flavorRef is the wrong way.
> >
> > Right now, if you create an instance from flavor 1, then change the
> > parameters of flavor 1, the flavorRef will be wrong anyway. Before I
> > moved instance_type information to system_metadata, doing that would
> > even cause billing stuff to be incorrect. Lets figure out how to
> > represent the actual instance parameters in APIv3, which I think will
> > serve everyone's needs.
>
> Sounds like a good plan to me.
>
> As you said, given the timing with the v3 API work, we have an
> opportunity to do some refactoring here and do it "right".
>
>
Sounds good to me. It's also become clear to me through this discussion
that we have two separate problems here that need to be solved. The one
relates to nova, the API and everything that's been the main focus of
discussion. The other relates to an end-user experience in Horizon.

For the first I trust that the team working on the new API will include
Michael in the development process and will come up with something suitable.

For the second I have a solution in mind which I'll register in a separate
blueprint in the Horizon project.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130517/ddc3d222/attachment.html>