<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> rdo-list-bounces@redhat.com <rdo-list-bounces@redhat.com> on behalf of Javier Pena <javier.pena@redhat.com><br>
<b>Sent:</b> Friday, June 17, 2016 10:45 AM<br>
<b>To:</b> rdo-list<br>
<b>Cc:</b> 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"><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 as<br>
> > controller.<br>
> ><br>
> > This would allow us to reuse the same answer file on all runs (one per host<br>
> > as you proposed), eliminate the ssh code as we are always running 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>
<br>
Now that the phase 1 refactor is under review and passing CI, I think it's time to come to a conclusion on this.<br>
<br>
This option looks like the best compromise between keeping it simple and dropping the least possible amount of features. So unless someone has a better idea, I'll work on that as soon as the current review is merged.<br>
<br>
Would it be possible :-<br>
<br>
<font size="2"><span style="font-size:10pt;"> - 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>
<b><i> </i><font size="2"><span style="font-size:10pt;"><font size="2"><span style="font-size:10pt;">-
<font size="2"><span style="font-size:10pt;"><font size="2"><span style="font-size:10pt;">If our host is not CONFIG_CONTROLLER_HOST but is part of</span></font></span></font>
<br>
CONFIG_STORAGE_HOSTS</span></font></span></font>, <font size="2"><span style="font-size:10pt;"><font size="2"><span style="font-size:10pt;">we apply the storage manifest</span></font></span></font><br>
<br>
Just one more role. May we have 4 roles ?<br>
<br>
<br>
</b>Thanks<br>
Boris.<b><br>
</b></span></font><b></b><br>
Regards,<br>
Javier<br>
<br>
> Alan<br>
> <br>
<br>
_______________________________________________<br>
rdo-list mailing list<br>
rdo-list@redhat.com<br>
<a id="LPlnk526260" 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_14661761015270.5898847231423053">
<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_14661761015250.646438316745729" 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_14661761015260.9619421414386667">
<div id="LPRemovePreviewContainer_14661761015260.7345379591819875"></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_14661761015260.5716309583906074">
<a target="_blank" href="https://www.redhat.com/mailman/listinfo/rdo-list" style="text-decoration: none;" id="LPUrlAnchor_14661761015260.8318824132799589">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_14661761015270.3032671184595831">
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_14661761015270.8826079948491818">
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>
To unsubscribe: rdo-list-unsubscribe@redhat.com<br>
</div>
</span></font></div>
</div>
</body>
</html>