<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Dec 13, 2013, at 8:56 AM, devdatta kulkarni <<a href="mailto:devdatta.kulkarni@rackspace.com">devdatta.kulkarni@rackspace.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">-----Original Message-----<br>From: "Krishna Raman" <<a href="mailto:kraman@gmail.com">kraman@gmail.com</a>><br>Sent: Friday, December 13, 2013 9:44am<br>To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>Subject: Re: [openstack-dev] [Solum] Using Zuul in the Git-pull blueprint<br><br>On Dec 12, 2013, at 1:39 PM, devdatta kulkarni <<a href="mailto:devdatta.kulkarni@rackspace.com">devdatta.kulkarni@rackspace.com</a>> wrote:<br><br><blockquote type="cite">We followed on the Zuul question in this week's git-integration working group meeting.<br><br>mordred has created an etherpad with a high-level description of Zuul and how it might<br>fit with Solum't git integration workflow<br><br><a href="https://etherpad.openstack.org/p/ZuulSolum">https://etherpad.openstack.org/p/ZuulSolum</a><br><br>The working group seemed to be coming to the consensus that we want to use a single workflow<br>engine, as far as possible, for all of Solum's workflow needs.<br>This brought up the question about, what are really Solum's workflow requirements.<span class="Apple-converted-space"> </span><br></blockquote><br>Hi<br><br>I had a long conversation with Monty yesterday and we flushed out a few things I would like to run by the group.<br>I have also included answers to the questions below.<br><br><blockquote type="cite"><br>At a high-level, I think that Solum has three different kinds of workflows.<br><br>1) Workflow around getting user code into Solum<br> - This is the git integration piece being worked out in the git-integration<br> working group.<br></blockquote><br>This is possible using the Zuul workflows. Would potentially require a little work in Zuul.<br><br><blockquote type="cite"><br>2) Workflow around creating language pack(s).<br> - The main workflow requirement here involves ability to run tests before creating a language pack.<br> There was some discussion in language-pack working group about this requirement.<br></blockquote><br>This is also possible using Zuul and in-fact would benefit Solum by providing config file based build workflows<br>that could be customized by ops personelle. For e.g.. one DU might require SVN, another might require git<span class="Apple-converted-space"> </span><br>and a jenkins CI based unit test before triggering Langpack, other DUs might wish to leverage gerrit etc.<br>This would be possible through Zuul without having to reinvent it on the other workflow engine.<br><br><blockquote type="cite"><br>3) Workflow around deploying created language pack(s) in order to instantiate an assembly.<br> - The deployment may potentially contain several steps, some of which may be long running, such as<br> populating a database. Further, there may be a need to checkpoint intermediate steps<br> and retry the workflow from the failed point.<br></blockquote><br>This is probably not a very good fit for Zuul. It can handle simple workflow but won’t be able to do the<br>complex checkpointing, rollback, retry logic etc.<br><br><blockquote type="cite"><br><br>mordred mentioned that #1 can be achieved by Zuul (both, push-to-solum and pull-by-solum)<br>We want to know if #2 and #3 can also be achieved by Zuul.<br>If not, we want to know what are the available options.<br><br>mordred, thanks for the etherpad; looking forward to the digram :)<br></blockquote><br><br>Zuul is workflow engine capable of running simple workflows. It is probably not suitable for all of Solum but would<br>manage the source -> DU flow quite nicely. Initially my thoughts were that I wanted to avoid having 2 workflow<br>engines in Solum but there is another way to look at it…<br><br>During out F2F, we had said that we should have a Solum API where we could just post DU images. This would<br>allow someone to build the DU outside Solum and just provide it. We could use this same API as a clean interface to<br>separated out the DU build flow from the DU deploy flow. Once this is done, the DU build flow (#1, #2 above)<br>could be cleanly handled by Zuul and the DU deploy flow by whatever complex engine the rest of Solum would<br>use.<br><br><blockquote type="cite"><blockquote type="cite">I think this makes sense.<br></blockquote></blockquote><br>If I were to tie this discussion back to the various working groups and blueprints, I think<br>the git-integration and language-pack working groups are targeting the "DU build flow" (#1 and #2).<br>On the other hand, the work being done as part of 'specify-lang-pack' blueprint and 'pluggable-template-generation'<br>are targeting parts of #3. There would be additional blueprints for other aspects of #3.<br></div></blockquote><div><br></div><div>+1</div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>- Devdatta<br><br><br>This approach has a few advantages:<br><span class="Apple-tab-span" style="white-space: pre;"> </span>* Re-uses what Openstack already uses but its build & CI process (and potentially makes it better)<br><span class="Apple-tab-span" style="white-space: pre;"> </span>* Allows operations who deploy Solum to customize their build process without having to change Solum<br><span class="Apple-tab-span" style="white-space: pre;"> </span>* Allows us to leverage the Zuul/OpenStack-infra team to help us solve the DU build flow instead of having<span class="Apple-converted-space"> </span><br><span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-converted-space"> </span> to go alone<br><br>—Krishna<br><br><blockquote type="cite"><br><br>thanks,<br>devkulkarni<br><br><br>-----Original Message-----<br>From: "Roshan Agrawal" <<a href="mailto:roshan.agrawal@RACKSPACE.COM">roshan.agrawal@RACKSPACE.COM</a>><br>Sent: Monday, December 9, 2013 10:57am<br>To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>Subject: Re: [openstack-dev] [Solum] Using Zuul in the Git-pull blueprint<br><br><br><blockquote type="cite">-----Original Message-----<br>From: Krishna Raman [<a href="mailto:kraman@gmail.com">mailto:kraman@gmail.com</a>]<br>Sent: Sunday, December 08, 2013 11:24 PM<br>To: OpenStack Development Mailing List (not for usage questions)<br>Subject: [openstack-dev] [Solum] Using Zuul in the Git-pull blueprint<br><br>Hi all,<br><br>We had a very good meeting last week around the git-pull blueprint. During<br>the discussion, Monty suggested using Zuul to manage the git repository<br>access and workflow.<br>While he is working on sending the group a diagram and description of what<br>he has in mind, I had a couple of other questions which I am hoping the<br>extended group will be able to answer.<br><br>1) Zuul is currently an infrastructure project.<br><span class="Apple-tab-span" style="white-space: pre;"> </span>- Is there anything that prevents us from using it in Solum?<br><span class="Apple-tab-span" style="white-space: pre;"> </span>- Does it need to be moved to a normal OpenStack project?<br><br>2) Zuul provides a sort of workflow engine. This workflow engine could<br>potentially be used to initiate and manage: API Post -> git flow -> lang pack<br>flow.<br><span class="Apple-tab-span" style="white-space: pre;"> </span>- Have there been any discussion after the F2F where we have<br>discussed using some other workflow engine?<br></blockquote><br>There hasn't been further discussion since F2F.<br>Most of the processes in Solum will really be customizable workflows, and use of a generic workflow engine is definitely worth discussing. We may still use to leverage Zuul for the gerrit/git/checkin piece, but Solum will have workflow needs beyond that.<span class="Apple-converted-space"> </span><br><br><blockquote type="cite"><span class="Apple-tab-span" style="white-space: pre;"> </span>- Is Zuul's engine generic enough to be used in Solum? (Hoping<br>Monty can help with this one)<br><span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"> </span>- Perhaps only use it to manage the API post -> git flow<br>stages?<br><br>Thanks<br>-Krishna<br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br><br><br><br>_______________________________________________<br>OpenStack-dev mailing list<br>OpenStack-dev@lists.openstack.org<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><br><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br><br><br><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div></blockquote></div><br></body></html>