<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none;"></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 Ivan Chavero <ichavero@redhat.com><br> <b>Sent:</b> Wednesday, June 8, 2016 3:27 PM<br> <b>To:</b> Javier Pena<br> <b>Cc:</b> rdo-list<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> > From: "Javier Pena" <javier.pena@redhat.com><br> > To: "rdo-list" <rdo-list@redhat.com><br> > Sent: Wednesday, June 8, 2016 11:29:54 AM<br> > Subject: [rdo-list] Packstack refactor and future ideas<br> > <br> > Hi RDO,<br> > <br> > After some discussions about the way Packstack was (mis)using Puppet, and how<br> > to improve it, I've been working on a refactor. Its current state is<br> > available at<br> > <a id="LPlnk540530" href="https://github.com/javierpena/packstack/tree/feature/manifest_refactor"> https://github.com/javierpena/packstack/tree/feature/manifest_refactor</a>, and <div style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;" id="LPBorder_GT_14654208015700.17279813404339184"> <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_14654208015600.07586536262975985" cellspacing="0"> <tbody> <tr style="border-spacing: 0px;" valign="top"> <td colspan="1" style="width: 250px; position: relative; display: table-cell; padding-right: 20px;" id="ImageCell_14654208015620.8754502755502804"> <div style="background-color: rgb(255, 255, 255); height: 250px; position: relative; margin: auto; display: table; width: 250px;" id="LPImageContainer_14654208015620.498242716191425"> <a target="_blank" href="https://github.com/javierpena/packstack/tree/feature/manifest_refactor" style="display: table-cell; text-align: center;" id="LPImageAnchor_14654208015650.42913866750725405"><img aria-label="Preview image with link selected. Double-tap to open the link." style="display: inline-block; margin-left: auto; margin-right: auto; max-width: 250px; max-height: 250px; height: 250px; width: 250px; border-width: 0px; vertical-align: bottom;" height="250" width="250" src="https://avatars2.githubusercontent.com/u/8833973?v=3&s=400"></a></div> </td> <td colspan="2" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" id="TextCell_14654208015660.1040043844776074"> <div id="LPRemovePreviewContainer_14654208015660.20893159442824483"></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_14654208015660.09766320395452133"> <a target="_blank" href="https://github.com/javierpena/packstack/tree/feature/manifest_refactor" style="text-decoration: none;" id="LPUrlAnchor_14654208015670.1749774567793">javierpena/packstack</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_14654208015670.36692218818714595"> github.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_14654208015680.8823138030386747"> packstack - Install utility to deploy openstack on multiple hosts.</div> </td> </tr> </tbody> </table> </div> <br> > as soon as it is polished it will go to Gerrit. It basically tries to reduce<br> > the number of Puppet executions to one per server role (controller, network<br> > node, compute), instead of multiple individual runs.<br> <br> I think it can be reduced to a single manifest per node.<br> Also, when a review is created it would be easier to check if you create one <br> review for the python, puppet, tests and release notes.<br> <br> > While talking about the refactor, a second discussion about a deeper change<br> > was started. I'd like to summarize the current concerns and ideas in this<br> > mail, so we can follow-up and make a decision:<br> > <br> > - Currently, the Packstack CI is only testing single-node installs. Testing<br> > multi-node installs upstream has been challenging, and multi-node may go<br> > beyond the PoC target of Packstack. So, one proposal is to keep all-in-one<br> > single node only, add Ansible wrapper (in unsupported contrib/ subfolder)<br> > reading *_HOSTS parameters for backward compat.<br> > <br> <br> I would like to have packstack to be multi node since the requirements for <br> TripleO are still to big for PoC.<br> <br> But it is :-<br> <br> RDO Mitaka ML2&OVS&VXLAN (VLAN) <br> Controller+Network+N*Compute+Storage (CONFIG_UNSUPORTED=y)<br> Controller/Network+N*Compute+Storage <font size="2"><span style="font-size:10pt;">(CONFIG_UNSUPORTED=y)</span></font><br> Just external OVS bridge on Controller/Network ( Network) has to be configured manually.<br> It works fine unless HA Controller(s) is a must.<br> Some posts to this thread sound like intend to drop features present and working all way long <br> in packstack. I hardly understand why working features should be dropped due to not passing through CI.<br> Yes , conversion system to DVR requires several updates after packstack pre-deployment,<br> but I would never compare Packstack with Devstack due to<br> <br> 1. Packstack installs different services on different nodes exactly as answer-file instructs it to do.<br> 2. Devstack starts a bunch of non-restart able ( in meantime ) daemons on one or several nodes, <br> <br> Thanks.<br> Boris.<br> <br> > - Another idea was to refactor the Packstack Python part around Ansible,<br> > summarized at <a title="Ctrl+Click or tap to follow the link" href="https://etherpad.openstack.org/p/packstack-refactor-take2"> https://etherpad.openstack.org/p/packstack-refactor-take2</a> .<br> > This proposal aims at keeping multi-node support, since Ansible makes it<br> > easy anyway.<br> <br> Does it make sense to convert packstack to an ansible module?<br> <br> <br> > <br> > Any other ideas/concerns? Pros and cons of each?<br> <br> I started a refactor [1] as part of a manifest cleanup, unifcation and to<br> start de refactor discussion, i'm happy that Javier took the puppet-openstack-integration<br> road. <br> Another idea around this refactor is to make packstack create manifests<br> that can be used even without packstack runs, installing them in the proper puppet <br> environment directories and setting the OPM path as part of the this OpenStack? environment,<br> thus making packstack a puppet manifest generator...<br> <br> Cheers,<br> Ivan<br> <br> <br> <br> [1] <a href="https://review.openstack.org/#/c/307519/">https://review.openstack.org/#/c/307519/</a><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>