<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is partly related to a previous submission “Mitaka to Newton networking issues” by a colleague of mine, Grant Morley.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We had to rebuild our ansible server due to issues experienced when reverting from the Newton to Mitaka versions, which left ansible in an unworkable state. Our osa (/opt/openstack-ansible ) and openstack_deploy (/etc/openstack_deploy)
are stored on a local git repository, which we pushed to the new ansible server and successfully deployed our Mitaka Openstack environment. Since the initial build however we have pushed some changes from our openstack_deploy repository, and this seems to
have had the effect of overwriting the inventory with the hostnames and IPs of our previous Newton build.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are now unable to run any playbooks from ansible as it is trying to connect to the incorrect hosts/IPs. Can anyone please advise if there is a way to regenerate the inventory from the live containers currently running. All attempts have
resulted in the incorrect old inventory being generated. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Also can anyone advise where dynamic_inventory.py retrieves data to generate the inventory?<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-GB">Regards,<br>
<br>
Ian Banks<br>
<br>
Senior Systems Engineer<br>
<br>
ServerChoice Ltd<br>
<br>
Unit H, J and K<br>
Gateway 1000<br>
Whittle Way<br>
Stevenage<br>
Hertfordshire<br>
SG1 2FP<br>
<br>
Please note we have new telephone numbers. <br>
<br>
Direct: 01438 532 307<br>
Office: 01438 532 300 <br>
Support: 01438 342 310 <br>
<br>
http://www.serverchoice.com<br>
ian.banks@serverchoice.com<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>