<div dir="ltr">Indeed. I believe there's currently no quota for root disk size ("gigabytes" is only for volumes), so if this feature was implemented, it would have to account for that.</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 9:42 AM, Warren Wang <span dir="ltr"><<a href="mailto:warren@wangspeed.com" target="_blank">warren@wangspeed.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>I agree with Joe. It would be a nice to have, though it tends to lead to abuse by users, but that is a totally different issue. <br><br>--<div>Warren</div></div><div><div class="h5"><div><br>On Aug 6, 2013, at 11:35 AM, Joe Topjian <<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</a>> wrote:<br>
<br></div><blockquote type="cite"><div><div dir="ltr">Hi,<div><br></div><div>Yes, that's correct.</div><div><br></div><div>However, what I'm looking for is the ability to change the "Disk" portion of the flavor on the fly while keeping the rest of the flavor attributes intact. This is possible in AWS.</div>
<div><br></div><div>While I could create a new flavors for various root disk sizes (m1.tiny-10, m1.tiny-20, m1.tiny-30, m1.xlarge-10, m1.xlarge-20, etc etc), this still only allows for certain given sizes and wouldn't allow a user to specify a root disk of, say, 11 or 12gb. Not to mention the complexity of managing so many different flavors.</div>
<div><br></div><div>Thanks,</div><div>Joe</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 9:30 AM, JuanFra Rodriguez Cardoso <span dir="ltr"><<a href="mailto:juanfra.rodriguez.cardoso@gmail.com" target="_blank">juanfra.rodriguez.cardoso@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi Joe,<br><br></div>OpenStack make use of 'flavors' for defining sizes such as RAM, root disk, swap... in your instances.<br>
</div>You can look <a href="http://docs.openstack.org/trunk/openstack-ops/content/flavors.html" target="_blank">http://docs.openstack.org/trunk/openstack-ops/content/flavors.html</a> for extend the info.<br>
<div class="gmail_extra"><br></div><div class="gmail_extra">Regards,<br clear="all"></div><div class="gmail_extra"><div><div>---</div>JuanFra</div>
<br><br><div class="gmail_quote">2013/8/6 Joe Topjian <span dir="ltr"><<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
<div dir="ltr">Hello,<div><br></div><div>In Amazon AWS, when a user launches an instance, they have the ability to specify a custom root disk size. All other aspects of the flavor will stay the same.</div><div><br></div>
<div>
Is this currently possible to do (Folsom+) or is there a blueprint to implement this? I apologize if there is -- I was unable to find one.</div><div><br></div><div>Thanks,</div><div>Joe<span><font color="#888888"><br clear="all">
<div><br></div>-- <br>
<div dir="ltr">Joe Topjian<div>Systems Architect</div><div>Cybera Inc.</div><div><br></div><div><a href="http://www.cybera.ca" target="_blank">www.cybera.ca</a></div><div><br></div><div><font color="#666666"><span>Cybera</span><span> is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.</span></font></div>
</div>
</font></span></div></div>
<br></div></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>
<br></blockquote></div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Joe Topjian<div>Systems Architect</div><div>Cybera Inc.</div><div><br></div><div><a href="http://www.cybera.ca" target="_blank">www.cybera.ca</a></div>
<div><br></div><div><font color="#666666"><span>Cybera</span><span> is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.</span></font></div>
</div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OpenStack-operators mailing list</span><br><span><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a></span><br>
<span><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></span><br></div></blockquote></div></div>
</div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Joe Topjian<div>Systems Architect</div><div>Cybera Inc.</div><div><br></div><div><a href="http://www.cybera.ca" target="_blank">www.cybera.ca</a></div>
<div><br></div><div><font color="#666666"><span>Cybera</span><span> is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.</span></font></div>
</div>
</div>