<br><font size=2 face="sans-serif">Glad to hear that. Just FYI, CIMI
[1] does this type of thing so if we ever do manage to harmonize
the two APIs this might be a good place to start.</font>
<br>
<br><font size=2 face="sans-serif">[1] http://dmtf.org/sites/default/files/standards/documents/DSP0263_1.0.0d.pdf</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 | dug@us.ibm.com<br>
The more I'm around some people, the more I like my dog.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Chris Behrens <cbehrens@codestud.com></b>
</font>
<p><font size=1 face="sans-serif">06/01/2012 02:42 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Doug Davis/Raleigh/IBM@IBMUS</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">Chris Behrens <cbehrens@codestud.com>,
Matthew Sherborne <matt.sherborne@rackspace.com>, openstack@lists.launchpad.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Openstack] hidden / phasing out
instance_types/flavors</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3>Doug,</font>
<br>
<br><font size=3>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. :)</font>
<br>
<br><font size=3>- Chris</font>
<br>
<br>
<br><font size=3>On Jun 1, 2012, at 9:54 AM, Doug Davis wrote:</font>
<br>
<br><font size=2 face="sans-serif"><br>
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><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
thanks<br>
-Doug<br>
______________________________________________________<br>
STSM | Standards Architect | IBM Software Group<br>
(919) 254-6905 | IBM 444-6905 | </font><a href=mailto:dug@us.ibm.com><font size=2 color=blue face="sans-serif"><u>dug@us.ibm.com</u></font></a><font size=2 face="sans-serif"><br>
The more I'm around some people, the more I like my dog.</font><font size=3>
<br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=51%><font size=1 face="sans-serif"><b>Matthew Sherborne <</b></font><a href=mailto:matt.sherborne@rackspace.com><font size=1 color=blue face="sans-serif"><b><u>matt.sherborne@rackspace.com</u></b></font></a><font size=1 face="sans-serif"><b>></b>
<br>
Sent by: </font><a href="mailto:openstack-bounces+dug=us.ibm.com@lists.launchpad.net"><font size=1 color=blue face="sans-serif"><u>openstack-bounces+dug=us.ibm.com@lists.launchpad.net</u></font></a>
<p><font size=1 face="sans-serif">06/01/2012 10:41 AM</font><font size=3>
</font>
<td width=48%>
<br>
<table width=100%>
<tr valign=top>
<td width=12%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=87%><a href=mailto:openstack@lists.launchpad.net><font size=1 color=blue face="sans-serif"><u>openstack@lists.launchpad.net</u></font></a><font size=3>
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[Openstack] hidden / phasing out instance_types/flavors</font></table>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br></table>
<br><font size=3><br>
<br>
<br>
Hi Openstack community, <br>
<br>
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><font size=3>
<br>
<br>
It adds a 'disabled' field to the 'instance_type' or 'flavor' concept.
<br>
<br>
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. <br>
<br>
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>
) <br>
<br>
The reasoning behind this is: <br>
* If we did it as an extension, it would greatly complicate the code.
The code is much simpler being right in the core code. <br>
* We can't just add a field to the API quickly, so we need to use the
namespace. <br>
* The hope is that eventually it would be accepted into the main
API anyway, then the coding would be just removing the namespace. <br>
<br>
Many thanks in for reading. All feedback appreciated. <br>
<br>
Kind Regards,<br>
Matthew Sherborne</font><tt><font size=2>_______________________________________________<br>
Mailing list: </font></tt><a href=https://launchpad.net/~openstack><tt><font size=2 color=blue><u>https://launchpad.net/~openstack</u></font></tt></a><tt><font size=2><br>
Post to : </font></tt><a href=mailto:openstack@lists.launchpad.net><tt><font size=2 color=blue><u>openstack@lists.launchpad.net</u></font></tt></a><tt><font size=2><br>
Unsubscribe : </font></tt><a href=https://launchpad.net/~openstack><tt><font size=2 color=blue><u>https://launchpad.net/~openstack</u></font></tt></a><tt><font size=2><br>
More help : </font></tt><a href=https://help.launchpad.net/ListHelp><tt><font size=2 color=blue><u>https://help.launchpad.net/ListHelp</u></font></tt></a><font size=3><br>
<br>
_______________________________________________<br>
Mailing list: </font><a href=https://launchpad.net/~openstack><font size=3 color=blue><u>https://launchpad.net/~openstack</u></font></a><font size=3><br>
Post to : </font><a href=mailto:openstack@lists.launchpad.net><font size=3 color=blue><u>openstack@lists.launchpad.net</u></font></a><font size=3><br>
Unsubscribe : </font><a href=https://launchpad.net/~openstack><font size=3 color=blue><u>https://launchpad.net/~openstack</u></font></a><font size=3><br>
More help : </font><a href=https://help.launchpad.net/ListHelp><font size=3 color=blue><u>https://help.launchpad.net/ListHelp</u></font></a>
<br>
<br>