<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Doug,<div><br></div><div>That's the behavior I'd like to see and think it makes the most sense. It's really a requirement if we want a great cells implementation. instance_types table should only be used at the top level API cell. The data contained in the table is passed in the messaging and stored with the newly built, re-built, or re-sized instance. I brought this up a couple days ago internally at Rackspace while this current patch was being developed and I think we were going to start to look at that next…. assuming everyone loves the idea. :)</div><div><br></div><div>- Chris</div><div><br></div><div><br><div><div>On Jun 1, 2012, at 9:54 AM, Doug Davis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<br><font size="2" face="sans-serif">Just wondering, is there any reason
flavors are not limited to just create-time? Meaning, use it to create
a new instance and then copy all of the flavor data into the new instance's
data. This breaks the relationship between the instance and the flavor,
allow each to be changed independently - or even deleted. Doing this
would mean you wouldn't need to add a "disabled" flag at all
- just delete the flavor if you don't want anyone to use it. This
would also allow for an easier modification of existing instances - just
modify the instance's property that needs to change w/o creating a whole
new flavor (avoids the proliferation of flavors too).</font>
<br><font size="2" face="sans-serif"><br>
thanks<br>
-Doug<br>
______________________________________________________<br>
STSM | Standards Architect | IBM Software Group<br>
(919) 254-6905 | IBM 444-6905 | <a href="mailto:dug@us.ibm.com">dug@us.ibm.com</a><br>
The more I'm around some people, the more I like my dog.</font>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="40%"><font size="1" face="sans-serif"><b>Matthew Sherborne <<a href="mailto:matt.sherborne@rackspace.com">matt.sherborne@rackspace.com</a>></b>
</font>
<br><font size="1" face="sans-serif">Sent by: <a href="mailto:openstack-bounces+dug=us.ibm.com@lists.launchpad.net">openstack-bounces+dug=us.ibm.com@lists.launchpad.net</a></font><p><font size="1" face="sans-serif">06/01/2012 10:41 AM</font>
</p></td><td width="59%">
<table width="100%">
<tbody><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">To</font></div>
</td><td><font size="1" face="sans-serif"><a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></font>
</td></tr><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">cc</font></div>
</td><td>
</td></tr><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">Subject</font></div>
</td><td><font size="1" face="sans-serif">[Openstack] hidden / phasing out instance_types/flavors</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign="top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table>
<br>
<br>
<br><font size="3">Hi Openstack community,</font>
<br>
<br><font size="3">We recently uploaded this change: </font><a href="https://review.openstack.org/#/c/8007/"><font size="3" color="blue"><u>https://review.openstack.org/#/c/8007/</u></font></a>
<br>
<br><font size="3">It adds a 'disabled' field to the 'instance_type' or 'flavor'
concept.</font>
<br>
<br><font size="3">The usage scenario we had in mind was to phase out a flavor
that's already in use; people shouldn't be able to build new instances
from that flavor, nor should customers see it in the list of available
flavors. But when they view an existing instance with that flavor type,
they should still be able to see the name of it at least. But should you
change your mind later and wish to re-enable it, it's easy to just flip
the flag.</font>
<br>
<br><font size="3">We'd appreciate feedback on the added field and the use
of the namespace in the core code. (Line 56 here: </font><a href="https://review.openstack.org/#/c/8007/1/nova/api/openstack/compute/views/flavors.py"><font size="3" color="blue"><u>https://review.openstack.org/#/c/8007/1/nova/api/openstack/compute/views/flavors.py</u></font></a><font size="3"> )</font>
<br>
<br><font size="3">The reasoning behind this is:</font>
<br><font size="3"> * If we did it as an extension, it would greatly
complicate the code. The code is much simpler being right in the core code.</font>
<br><font size="3"> * We can't just add a field to the API quickly,
so we need to use the namespace.</font>
<br><font size="3"> * The hope is that eventually it would be accepted
into the main API anyway, then the coding would be just removing
the namespace.</font>
<br>
<br><font size="3">Many thanks in for reading. All feedback appreciated.</font>
<br>
<br><font size="3">Kind Regards,<br>
Matthew Sherborne</font><tt><font size="2">_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
</font></tt>
<br>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></body></html>