settingsLogin | Registersettings

[openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

0 votes

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed & open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Apr 20, 2015 in openstack-dev by Asselin,_Ramy (4,700 points)   1 2 5
retagged Jan 26, 2017 by admin

12 Responses

0 votes

Hi Ramy,

Soon I'll be the responsible of the Midokura's third-party CI, which has been
mute for a while because a flaky physical resources that our sys admins
couldn't take care because they are overloaded of work...

Count on me!

On Mon, 20 Apr 2015 05:17, Asselin, Ramy wrote:
All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed & open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Jaume Devesa
Software Engineer at Midokura


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 20, 2015 by Jaume_Devesa (1,820 points)   1 3
0 votes

On 04/20/2015 03:19 AM, Jaume Devesa wrote:
Hi Ramy,

Soon I'll be the responsible of the Midokura's third-party CI, which has been
mute for a while because a flaky physical resources that our sys admins
couldn't take care because they are overloaded of work...

Count on me!
I do hope luqas will still be available some times, he has been so
proactive. It has been wonderful to work with him. I'm looking forward
to getting to know you as well, Jaume.

Thanks Asselin, for kicking off this thread, you have been doing
wonderful work here. It is great to see you have reached this place. I
am really looking forward to your work continuing, making installing and
maintaining a ci easier for both operators and for infra.

Thank you,
Anita.

On Mon, 20 Apr 2015 05:17, Asselin, Ramy wrote:

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed & open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 20, 2015 by Anita_Kuno (21,320 points)   3 3 4
0 votes

You rock, Ramy. Seriously, awesome work.

-jay

On 04/20/2015 01:17 AM, Asselin, Ramy wrote:
All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of
them running a variety of closed & open-source solutions.

Instead of individually maintaining all those similar solutions, let’s
join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved
[2] to refactor much of what the Infrastructure team uses for the
upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using
the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”,
which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply,
or ping me IRC (asselin) on Freenode #openstack-infra, or join some of
the third party ci meetings [5].

Thanks!

Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems

[2]
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html

[3] https://storyboard.openstack.org/#!/story/2000101

[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z

[5]
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 20, 2015 by Jay_Pipes (59,760 points)   3 11 14
0 votes

Thanks Ramy!

I'd suggest that we use the cross-project session I proposed [1] for
Liberty summit as a working session primarily focused on this work [2].

[1]
https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit?usp=sharing
[2] https://etherpad.openstack.org/p/liberty-third-party-ci-working-group

On Mon, Apr 20, 2015 at 8:40 AM, Jay Pipes jaypipes@gmail.com wrote:

You rock, Ramy. Seriously, awesome work.

-jay

On 04/20/2015 01:17 AM, Asselin, Ramy wrote:

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of
them running a variety of closed & open-source solutions.

Instead of individually maintaining all those similar solutions, let’s
join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved
[2] to refactor much of what the Infrastructure team uses for the
upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using
the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”,
which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply,
or ping me IRC (asselin) on Freenode #openstack-infra, or join some of
the third party ci meetings [5].

Thanks!

Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems

[2]

http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html

[3] https://storyboard.openstack.org/#!/story/2000101

[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z

[5]

https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 20, 2015 by Kurt_Taylor (1,280 points)   2
0 votes

Hi Ramy,

While I agree, in principal, with this line of thinking and goal, my
concern will be how much extra work is it going to create for existing CI
owners?
Our Ci system has been stable for a long time, and we put in a good amount
of effort to get it to that point. Our CI is not based upon zuul framework.
Zuul was still under discussion at the time when we put together our CI. We
use Jenkins as front end, along with Gerrit triggers, and AWS for
posting/preserving results/log. We have dedicated back-end servers for
testing.

My paranoia at this point will be to learn a new framework, risk breaking
things and taking a huge effort to get things stabilized - without much
additional ROI.
Am I overreacting here or does my argument makes sense?

I wonder how many folks will be in that camp?

Sukhdev

On Sun, Apr 19, 2015 at 10:17 PM, Asselin, Ramy ramy.asselin@hp.com wrote:

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them
running a variety of closed & open-source solutions.

Instead of individually maintaining all those similar solutions, let’s
join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2]
to refactor much of what the Infrastructure team uses for the upstream
“Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using
the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”,
which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or
ping me IRC (asselin) on Freenode #openstack-infra, or join some of the
third party ci meetings [5].

Thanks!

Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems

[2]
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html

[3] https://storyboard.openstack.org/#!/story/2000101

[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z

[5]
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 20, 2015 by Sukhdev_Kapur (3,240 points)   6 8
0 votes

HI Sukhdev,

I also wonder how many folks are in that camp.
Regardless, if we can go from 85 --> 2 (or any other much smaller number), then that is a good thing.
Also, from an open source point of view, I’d like to see new contributors/vendors contributing effort on value-add innovation, and less on recreating/maintaining the ‘common’ portions of 3rd party ci.

Ramy

From: Sukhdev Kapur [mailto:sukhdevkapur@gmail.com]
Sent: Monday, April 20, 2015 1:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

Hi Ramy,

While I agree, in principal, with this line of thinking and goal, my concern will be how much extra work is it going to create for existing CI owners?
Our Ci system has been stable for a long time, and we put in a good amount of effort to get it to that point. Our CI is not based upon zuul framework. Zuul was still under discussion at the time when we put together our CI. We use Jenkins as front end, along with Gerrit triggers, and AWS for posting/preserving results/log. We have dedicated back-end servers for testing.

My paranoia at this point will be to learn a new framework, risk breaking things and taking a huge effort to get things stabilized - without much additional ROI.
Am I overreacting here or does my argument makes sense?

I wonder how many folks will be in that camp?

Sukhdev

On Sun, Apr 19, 2015 at 10:17 PM, Asselin, Ramy ramy.asselin@hp.com wrote:
All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed & open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 21, 2015 by Asselin,_Ramy (4,700 points)   1 2 5
0 votes

Hello Ramy

Take me in account ☺
We used puppet modules located in system-config to install zuul and nodepool. Also there were a lot manual configuration.
Maybe someday there will be a “green button” to set it up in moment.

Thanks!

From: Asselin, Ramy [mailto:ramy.asselin@hp.com]
Sent: Monday, April 20, 2015 8:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed & open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 21, 2015 by Nikolay_Fedotov_(nfe (140 points)   1
0 votes

Hi Ramy,
Will there be any discussions of this issue on the Vancouver Summit?

Lenny Verkhovsky
SW Engineer, Mellanox Technologies

From: Nikolay Fedotov (nfedotov) [mailto:nfedotov@cisco.com]
Sent: Tuesday, April 21, 2015 8:10 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

Hello Ramy

Take me in account ☺
We used puppet modules located in system-config to install zuul and nodepool. Also there were a lot manual configuration.
Maybe someday there will be a “green button” to set it up in moment.

Thanks!

From: Asselin, Ramy [mailto:ramy.asselin@hp.com]
Sent: Monday, April 20, 2015 8:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed & open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 21, 2015 by Lenny_Verkhovsky (1,460 points)   1 4
0 votes

On Tue, Apr 21, 2015 at 12:14 PM, Lenny Verkhovsky lennyb@mellanox.com
wrote:

Hi Ramy,

Will there be any discussions of this issue on the Vancouver Summit?

See previous email in this thread, I have proposed a cross-project session
to discuss third party CI topics.

Lenny Verkhovsky

SW Engineer, Mellanox Technologies

From: Nikolay Fedotov (nfedotov) [mailto:nfedotov@cisco.com]
Sent: Tuesday, April 21, 2015 8:10 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI
Operators: Let's use a common CI Solution!

Hello Ramy

Take me in account J

We used puppet modules located in system-config to install zuul and
nodepool. Also there were a lot manual configuration.

Maybe someday there will be a “green button” to set it up in moment.

Thanks!

From: Asselin, Ramy [mailto:ramy.asselin@hp.com ramy.asselin@hp.com]
Sent: Monday, April 20, 2015 8:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party][infra] Third-Party CI Operators:
Let's use a common CI Solution!

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them
running a variety of closed & open-source solutions.

Instead of individually maintaining all those similar solutions, let’s
join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2]
to refactor much of what the Infrastructure team uses for the upstream
“Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using
the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”,
which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or
ping me IRC (asselin) on Freenode #openstack-infra, or join some of the
third party ci meetings [5].

Thanks!

Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems

[2]
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html

[3] https://storyboard.openstack.org/#!/story/2000101

[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z

[5]
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 21, 2015 by Kurt_Taylor (1,280 points)   2
0 votes

On 04/20/2015 04:39 PM, Sukhdev Kapur wrote:
Hi Ramy,

While I agree, in principal, with this line of thinking and goal, my
concern will be how much extra work is it going to create for existing CI
owners?
Our Ci system has been stable for a long time, and we put in a good amount
of effort to get it to that point. Our CI is not based upon zuul framework.
Zuul was still under discussion at the time when we put together our CI. We
use Jenkins as front end, along with Gerrit triggers, and AWS for
posting/preserving results/log. We have dedicated back-end servers for
testing.

My paranoia at this point will be to learn a new framework, risk breaking
things and taking a huge effort to get things stabilized - without much
additional ROI.
Am I overreacting here or does my argument makes sense?

I wonder how many folks will be in that camp?

Sukhdev
Hi Sukhdev:

What is being offered is an opportunity to pool efforts for those who
wish to participate. There is no pressure to participate if you are
concerned that you would compromise the integrity of a stable system.
You and others that have put in so much work are to be lauded for your
commitment to your goal, thank you. Ramy's efforts in no way are an
attempt to degrade the stability you have created.

Part of the exhaustion level folks feel in this space, at all points in
the spectrum, is the cost of maintenance. In infra we are constantly
dealing with problems from operators and it would reduce the burden on
us, as well as reduce the tension on operators, if we had a solution
that was easier to maintain. The more people running the same structure,
the easier any one issue is to solve (hopefully).

The goal is once the structure is in place that OpenStack's Infra would
also consume it, enabling common bugs to be discovered and fixed upstream.

Noone is forced to participate nor are they going to be forced to
operate this structure. This is simply a chance to work together on a
direction which infra would very much like to see in place.

Thanks Sukhdev,
Anita.

On Sun, Apr 19, 2015 at 10:17 PM, Asselin, Ramy ramy.asselin@hp.com wrote:

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them
running a variety of closed & open-source solutions.

Instead of individually maintaining all those similar solutions, let’s
join together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2]
to refactor much of what the Infrastructure team uses for the upstream
“Jenkins” CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using
the gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”,
which creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or
ping me IRC (asselin) on Freenode #openstack-infra, or join some of the
third party ci meetings [5].

Thanks!

Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems

[2]
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html

[3] https://storyboard.openstack.org/#!/story/2000101

[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z

[5]
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 21, 2015 by Anita_Kuno (21,320 points)   3 3 4
...