<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<br>
<br>
<div style="color: rgb(49, 55, 57);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Javier Pena <javier.pena@redhat.com><br>
<b>Sent:</b> Monday, June 20, 2016 7:44 AM<br>
<b>To:</b> Boris Derzhavets<br>
<b>Cc:</b> rdo-list; alan pevec<br>
<b>Subject:</b> Re: [rdo-list] Packstack refactor and future ideas</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">----- Original Message ----- <br>
<br>
> From: rdo-list-bounces@redhat.com <rdo-list-bounces@redhat.com> on behalf of<br>
> Javier Pena <javier.pena@redhat.com><br>
> Sent: Friday, June 17, 2016 10:45 AM<br>
> To: rdo-list<br>
> Cc: alan pevec<br>
> Subject: Re: [rdo-list] Packstack refactor and future ideas<br>
<br>
> ----- Original Message -----<br>
> > > We could take an easier way and assume we only have 3 roles, as in the<br>
> > > current refactored code: controller, network, compute. The logic would<br>
> > > then be:<br>
> > > - By default we install everything, so all in one<br>
> > > - If our host is not CONFIG_CONTROLLER_HOST but is part of<br>
> > > CONFIG_NETWORK_HOSTS, we apply the network manifest<br>
> > > - Same as above if our host is part of CONFIG_COMPUTE_HOSTS<br>
> > ><br>
> > > Of course, the last two options would assume a first server is installed<br>
> > > as<br>
> > > controller.<br>
> > ><br>
> > > This would allow us to reuse the same answer file on all runs (one per<br>
> > > host<br>
> > > as you proposed), eliminate the ssh code as we are always running<br>
> > > locally,<br>
> > > and make some assumptions in the python code, like expecting OPM to be<br>
> > > deployed and such. A contributed ansible wrapper to automate the runs<br>
> > > would be straightforward to create.<br>
> > ><br>
> > > What do you think? Would it be worth the effort?<br>
> ><br>
> > +2 I like that proposal a lot! An ansible wrapper is then just an<br>
> > example playbook in docs but could be done w/o ansible as well,<br>
> > manually or using some other remote execution tooling of user's<br>
> > choice.<br>
> ><br>
> Now that the phase 1 refactor is under review and passing CI, I think it's<br>
> time to come to a conclusion on this.<br>
> This option looks like the best compromise between keeping it simple and<br>
> dropping the least possible amount of features. So unless someone has a<br>
> better idea, I'll work on that as soon as the current review is merged.<br>
><br>
> Would it be possible :-<br>
><br>
> - By default we install everything, so all in one<br>
> - If our host is not CONFIG_CONTROLLER_HOST but is part of<br>
> CONFIG_NETWORK_HOSTS, we apply the network manifest<br>
> - Same as above if our host is part of CONFIG_COMPUTE_HOSTS<br>
> - If our host is not CONFIG_CONTROLLER_HOST but is part of<br>
> CONFIG_STORAGE_HOSTS , we apply the storage manifest<br>
><br>
> Just one more role. May we have 4 roles ?<br>
<br>
This is a tricky one. There used to be support for separate CONFIG_STORAGE_HOSTS, but I think it has been removed (or at least not tested for quite a long time).<br>
<br>
However, this feature currently works for RDO Mitaka ( as well it woks for Liberty)<br>
It's even possible to add Storage Node via packstack , taking care of glance and swift proxy<br>
keystone endpoints manually .<br>
For small prod deployments like several (5-10) Haswell Xeon boxes. ( no HA requirements from<br>
customer's side ). <b>Ability to split Storage specifically Swift (AIO) instances or Cinder iSCSILVM
<br>
back ends hosting Node from Controller is extremely critical feature.</b><br>
What I am writing is based on several projects committed in South America's countries.<br>
<b> No complaints from site support stuff to myself for configurations deployed via Packstack.</b><br>
Dropping this feature ( unsupported , but stable working ) will for sure make Packstack<br>
almost useless toy . <br>
In situation when I am able only play with TripleO QuickStart due to Upstream docs
<br>
( Mitaka trunk instructions set) for instack-virt-setup don't allow to commit <br>
`openstack undercloud install` makes Howto :-<br>
<br>
<a title="Ctrl+Click or tap to follow the link" id="LPlnk312342" href="https://remote-lab.net/rdo-manager-ha-openstack-deployment" class="OWAAutoLink">
https://remote-lab.net/rdo-manager-ha-openstack-deployment</a><br>
<br>
<a title="Ctrl+Click or tap to follow the link" id="LPlnk312342" href="https://remote-lab.net/rdo-manager-ha-openstack-deployment" class="OWAAutoLink"></a> non reproducible.
<b>I have nothing against TripleO turn, but absence of Red Hat<br>
high quality manuals for TripleO bare metal / TripleO Instak-virt-setup <br>
will affect RDO Community in wide spread way. I mean first all countries<br>
like Chile, Brazil, China and etc.</b><br>
<br>
Thank you.<br>
Boris.<br>
<br>
This would need to be a follow-up review, if it is finally decided to do so.<br>
<br>
Regards,<br>
Javier <br>
<br>
> Thanks<br>
> Boris.<br>
<br>
> Regards,<br>
> Javier<br>
<br>
> > Alan<br>
> ><br>
<br>
> _______________________________________________<br>
> rdo-list mailing list<br>
> rdo-list@redhat.com<br>
> <a id="LPlnk32200" href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a>
<div style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;" id="LPBorder_GT_14664265996240.4297769040565229">
<table style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" id="LPContainer_14664265996190.3908928940857602" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td colspan="2" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" id="TextCell_14664265996200.10899356645835223">
<div id="LPRemovePreviewContainer_14664265996200.47202268095541633"></div>
<div style="top: 0px; color: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;" id="LPTitle_14664265996200.18114437476284706">
<a target="_blank" href="https://www.redhat.com/mailman/listinfo/rdo-list" style="text-decoration: none;" id="LPUrlAnchor_14664265996210.9609004906827358">rdo-list Info Page - Red Hat</a></div>
<div style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;" id="LPMetadata_14664265996220.7014206578996421">
www.redhat.com</div>
<div style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;" id="LPDescription_14664265996230.2056587324917163">
The rdo-list mailing list provides a forum for discussions about installing, running, and using OpenStack on Red Hat based distributions. To see the collection of ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
> rdo-list Info Page - Red Hat<br>
> <a href="http://www.redhat.com">www.redhat.com</a><br>
> The rdo-list mailing list provides a forum for discussions about installing,<br>
> running, and using OpenStack on Red Hat based distributions. To see the<br>
> collection of ...<br>
<br>
> To unsubscribe: rdo-list-unsubscribe@redhat.com<br>
<br>
> _______________________________________________<br>
> rdo-list mailing list<br>
> rdo-list@redhat.com<br>
> <a href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
<br>
> To unsubscribe: rdo-list-unsubscribe@redhat.com<br>
</div>
</span></font></div>
</div>
</body>
</html>