<p dir="ltr">Another remove vote. The only people this may affect are people standing up test clouds or new to OpenStack.</p>
<p dir="ltr">For those folks that use puppet, the puppet community will be adding a provider to setup flavors since it's a feature that's been missing. </p>
<div class="gmail_quot<blockquote class=" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'll add a vote for removal, given how varied private clouds tend to be, the flavors are often "wrong" for any one particular purpose.<div><br></div><div>R</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 2, 2016 at 8:41 PM, Mike Smith <span dir="ltr"><<a href="mailto:mismith@overstock.com" target="_blank">mismith@overstock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div style="word-wrap:break-word">
+1 from me.  We always just remove them and add our own.  Like Dan said, it’s consistent with populating your own images.<span><font color="#888888"><br>
<div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
Mike Smith<br>
Lead Cloud Systems Architect</div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<a href="http://Overstock.com" target="_blank">Overstock.com</a><br>
<br>
<br>
</div>
</div>
</div>
</div></font></span><div><div>
<br>
<div>
<blockquote type="cite">
<div>On Apr 2, 2016, at 8:33 PM, Eric Windisch <<a href="mailto:eric@windisch.us" target="_blank">eric@windisch.us</a>> wrote:</div>
<br>
<div>
<p dir="ltr">I recall these being embedded being a real operational pain when my team wanted to replace the defaults. +1 on removal</p>
<div class="gmail_quote">On Mar 31, 2016 2:27 PM, "Dan Smith" <<a href="mailto:dms@danplanet.com" target="_blank">dms@danplanet.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
I just wanted to float this past the operators list for visibility:<br>
<br>
Historically Nova has seeded some default flavors in an initial install.<br>
The way it has done this is really atypical of anything else we do, as<br>
it's embedded in the initial database schema migration. Since we're<br>
moving where we store those flavors now, leaving their creation in the<br>
original migration means even new deploys will just have to move them to<br>
the new location. That, and we don't even use them for our own testing<br>
as they're too large.<br>
<br>
So, this will involve removing them from that migration, making sure<br>
that devstack creates you some flavors to use if you're going that<br>
route, and updates to the manuals describing the creation of base<br>
flavors alongside getting an image set up to use.<br>
<br>
For real deployments, there should be little or no effect, but PoC type<br>
deploys that are used to those flavors being present may need to run a<br>
couple of flavor-create commands when bootstrapping, just like you have<br>
to do for images.<br>
<br>
Thanks!<br>
<br>
--Dan<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote>
</div>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div>
</blockquote>
</div>
<br>
</div></div></div>

<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></div>