Open Stack

Hi Ramy,

Take me in account. I'm interested in a common solution and I'm trying to
get more involved in the community, so I think that could be a nice
initiative to contribute to the community. If I can help, would be awesome.
I'll start to attend to third party ci meetings.


Regards

On Fri, Apr 24, 2015 at 3:45 PM, Sukhdev Kapur <sukhdevkapur at gmail.com>
wrote:

> Hi Anita,
>
> Thanks for the clarification. I will plan on attending the summit session
> on this topic (proposed by Kurt, I believe).
> I have to admit that I have to always keep an eye out to ensure nothing is
> broken in our CI because of any upgrade of packages, etc. and act
> accordingly. If new unified framework can reduce/eliminate this effort, I
> would like to at least understand it and discuss with the participants -
> and, may join in.
>
> Thanks for the good work.
> -Sukhdev
>
>
>
> On Tue, Apr 21, 2015 at 11:25 AM, Anita Kuno <anteaya at anteaya.info> wrote:
>
>> 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 at 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 at 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 at 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 at 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 at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
*Marcus Vinícius Ramires do Nascimento*
marcusvrn at gmail.com

Cel: (11) 97396-4018
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150424/8553943e/attachment.html>