<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 2, 2013 at 10:48 AM, Joe Topjian <span dir="ltr"><<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div class="im">On Tue, Apr 2, 2013 at 9:15 AM, Joe Topjian <span dir="ltr"><<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Jon,<br><div class="gmail_extra"><br><div class="gmail_quote">
<div>On Tue, Apr 2, 2013 at 8:47 AM, Jonathan Proulx <span dir="ltr"><<a href="mailto:jon@jonproulx.com" target="_blank">jon@jonproulx.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>It would be nice to do per project flavors, wouldn't it...<br>
<br></div>Currently all our cloud hardware is homogeneous so we divide available resources into proportional chunks, so mcuh memory and ephemeral disk (provided from node local storage) per vCPU. It's rather simplistic and still heavily influenced by the default flavors (all have a 10G root with the rest of the block storage as an ephemeral vdb)<br>
<div><div><div><br></div><div>We do have one flavor with a 40G root named "m1.windows" but don't provide a public windows image and as far as I know noone but administrators in my group have used it for testing (not a big windows demand here).<br>
</div></div></div></div></blockquote><div><br></div></div><div>Interesting. We had a "w1.large" flavor for a short period but ended up removing it because we wanted all flavors to be able to work with all images.</div>
<div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div>
</div><div><div><br>On Mon, Apr 1, 2013 at 6:22 PM, Joe Topjian <span dir="ltr"><<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</a>></span> wrote:<br></div><div class="gmail_extra">
<div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><br><div dir="ltr"><br><div>Boot from Volume might be a possibility, but does anyone have a procedure to create a Windows bootable volume?</div>
<div><br></div></div></blockquote><div><br></div></div><div>With the large caveat that I don't have any Windows instances I do have a thought on where I'd start, given there's been no other response (on list anyway)<br>
<br></div><div>1st cinder is meant to be able to create volumes based on glance images (--image-id <image-id>), which would be delightful, but hasn't worked for me and I haven't had a chance to look at why, so unsure if this is a local issue for me or a bug.<br>
</div></div></div></div></div></div></div></blockquote><div><br></div></div><div>Thanks for the tip. I'm going to give this a shot.</div></div></div></div></blockquote><div><br></div></div><div>This worked for me. </div>
</div></div></div></blockquote><div><br></div><div style>Spoke too soon. This does indeed work for standard LVM/iSCSI configurations, like how my test environment is set up, but it is failing immediately when using the NetApp driver. The error I am getting is:</div>
<div style><br></div><div style>OSError: [Errno 2] No such file or directory: '/dev/mapper/cinder--volumes-volume--2c8e5316--5a94--4c7a--9ef7--0663c49feecf'<br></div><div style><br></div><div style>From what I can tell, there isn't a proper local_path() function for iSCSI and/or NetApp and so Cinder is falling back to the default driver's local_path, which is LVM. Opening a bug now.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>The only change I had to make was adding "glance_host=" to my cinder.conf file. There are some other glance options (<a href="https://github.com/openstack/cinder/blob/master/etc/cinder/cinder.conf.sample#L92-L111" target="_blank">https://github.com/openstack/cinder/blob/master/etc/cinder/cinder.conf.sample#L92-L111</a>) but once glance_host was set, the defaults were applicable to my environment.</div>
<div><br></div><div>Next, I created a volume using the --image-id flag:</div><div><br></div><div>cinder create --image-id=a9b4535f-c56e-4816-b6aa-a3caef7dbba4 --display-name=win2k8r2vol 30<br></div>
<div><br></div><div>Does anyone know off of the top of their head if this is possible to do through Horizon in Grizzly?</div><div><br></div><div>Finally, I launched an instance via Horizon. The only clunky thing was having to specify an image even though it's ignored. The docs correctly mention that this is a bug (<a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-from-volume.html" target="_blank">http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-from-volume.html</a>), but it's supposed to have been fixed in Grizzly. Does anyone have a Grizzly environment to test this out and confirm it's fixed (especially in Horizon)? If not, I'll try to do this relatively soon.</div>
<div class="im">
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div class="gmail_extra"><div class="gmail_quote"><div>
<br></div><div>Failing that I'd create the volume in cinder then attach it directly to a linux host somewhere and either run the install directly using appropriate virtualization tools or grab an existing windows image from glance (either just by grabbing the file or using glance image-download depending on your setup)<br>
<br>-Jon<br></div></div></div></div></div></div></div>
</blockquote></div></div><br><br clear="all"><div><div><br></div>-- <br>Joe Topjian<div>Systems Administrator</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></div></div><div class="im"><br><br clear="all"><div><br></div>-- <br>Joe Topjian<div>Systems Administrator</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></div><br><br clear="all"><div><br></div>-- <br>Joe Topjian<div>Systems Administrator</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>