[openstack-dev] [Solum] Gated Source Code Flow (was: Weekly Team Meeting)

Georgy Okrokvertskhov gokrokvertskhov at mirantis.com
Wed Nov 13 20:48:09 UTC 2013

Hi Adrian,

It looks like that the final stage on all pictures is a "Deploy" stage.
What kind of process do you have in mind for CI\CD?
When you use "gate" system it is typical to have multiple gates. The usual
ones are: "code review\approved", "smoke test \ unit test pass",
"integration test pass", "performance\scalability test pass", "accepted for
production". Each gate might be a quite complex process for the large
application including multiple deployment to different stage environments.
Also it is typical to have one build and then promote it between different

Will Solum API support flexible CI\CD flows where user can define specific
stages and gates and actions for each of them?


On Wed, Nov 13, 2013 at 12:27 PM, Adrian Otto <adrian.otto at rackspace.com>wrote:

> Clayton,
> On Nov 13, 2013, at 11:41 AM, Clayton Coleman <ccoleman at redhat.com>
>  wrote:
> > ----- Original Message -----
> >> Hello,
> >>
> >> Solum meets Tuesdays at 1600 UTC in #openstack-meeting-alt (formerly in
> >> #solum)
> >>
> >>
> >> Note: Due to the Nov 3rd change in Daylight Savings Time, this now
> happens at
> >> 08:00 US/Pacific (starts in about 45 minutes from now)
> >>
> >>
> >> Agenda: https://wiki.openstack.org/wiki/Meetings/Solum
> >
> > In the meeting yesterday there was a mention of a "gated" source code
> flow (where a push might go to an external system, and the gate system
> github/gerritt/etc would control when the commit goes back to the primary
> repository).  I've added that flow to
> https://wiki.openstack.org/wiki/File:Solum_r01_flow.jpeg as well as a
> mention of the DNS abstraction (a deployed assembly may or may not have an
> assigned DNS identity).
> Are the two "source change notification abstraction" flows really
> different? Could we express this with two lines converging on "Notify Solum
> API …" in a single flow with two similar entrances.
> One key difference that I noticed between those two proposed flows are
> that the "gate" type uses the Solum API to test code, and the "push" one
> does not. Perhaps both should run unit tests in the same way with an option
> to bypass steps for those who don't want them?
> Adrian
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Georgy Okrokvertskhov
Technical Program Manager,
Cloud and Infrastructure Services,
Tel. +1 650 963 9828
Mob. +1 650 996 3284
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131113/a407fb58/attachment.html>

More information about the OpenStack-dev mailing list