<div dir="ltr"><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">Hi,</p><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">I have an icehouse openstack setup.</p><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">I have the following lines in nova.conf:</p><pre class="" style="font-family:Menlo,Monaco,'Courier New',monospace;font-size:12.025px;margin-top:0px;margin-bottom:18px;padding:2px;color:rgb(51,51,51);border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px;line-height:18px;border:1px solid rgb(136,136,136);white-space:pre-wrap;word-break:break-all;word-wrap:break-word;clear:both;background-color:rgb(245,245,245)"><code style="font-family:Menlo,Monaco,'Courier New',monospace;padding:0px;color:inherit;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;border:0px;clear:both;background-color:transparent"><span class="" style="color:rgb(0,0,0)">force_config_drive </span><span class="" style="color:rgb(102,102,0)">=</span><span class="" style="color:rgb(0,0,0)"> always
config_drive_cdrom </span><span class="" style="color:rgb(102,102,0)">=</span><span class="" style="color:rgb(0,0,0)"> </span><span class="" style="color:rgb(0,0,136)">True</span></code></pre><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">Whenever I launch an instance, I can see a content directory in the config drive</p><pre class="" style="font-family:Menlo,Monaco,'Courier New',monospace;font-size:12.025px;margin-top:0px;margin-bottom:18px;padding:2px;color:rgb(51,51,51);border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px;line-height:18px;border:1px solid rgb(136,136,136);white-space:pre-wrap;word-break:break-all;word-wrap:break-word;clear:both;background-color:rgb(245,245,245)"><code style="font-family:Menlo,Monaco,'Courier New',monospace;padding:0px;color:inherit;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;border:0px;clear:both;background-color:transparent"><span class="" style="color:rgb(0,0,0)">openstack</span><span class="" style="color:rgb(102,102,0)">/</span><span class="" style="color:rgb(0,0,0)">content</span><span class="" style="color:rgb(102,102,0)">/</span><span class="" style="color:rgb(0,102,102)">0000</span><span class="" style="color:rgb(0,0,0)"> contains all network interfaces</span><span class="" style="color:rgb(102,102,0)">.</span></code></pre><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">I can simply configure the static IP address from openstack/content/0000.</p><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">Now I have a new openstack cluster setup and I cannot see this content directory when I launch a VM.</p><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">I checked my configuration files and I can't find any difference with my old cluster.</p><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">Any ideas?</p><p style="margin:0px 0px 14px;padding:0px 5px 5px 0px;border:none;font-size:14px;line-height:1.4;color:rgb(75,75,75)">Thanks</p></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 16, 2015 at 7:46 AM, Richard Raseley <span dir="ltr"><<a href="mailto:richard@raseley.com" target="_blank">richard@raseley.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As part of wrapping up the few remaining 'loose ends' in moving the Puppet modules under the big tent, we are pressing forward with deprecating the previously used '<a href="mailto:puppet-openstack@puppetlabs.com" target="_blank">puppet-openstack@puppetlabs.com</a>' mailing list in favor of both the openstack-dev and openstack-operators lists with the '[puppet]' tag.<br>
<br>
Usage of the openstack-dev list seems pretty straight forward, but we wanted to confirm with the broader community that this list (openstack-operators) was the appropriate venue for Puppet and OpenStack related usage questions.<br>
<br>
Any objections to this model?<br>
<br>
Regards,<br>
<br>
Richard Raseley<br>
<br>
Systems Operations Engineer @ Puppet Labs<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></div>