Re: [Gluster-infra] Migrating Gerrit and Jenkins out of iWeb

[Michael Scherer]

Le mercredi 10 février 2016 à 19:18 +0530, Kaushal M a écrit :
> On Wed, Feb 10, 2016 at 1:53 PM, Michael Scherer  wrote:
> > Le mercredi 10 février 2016 à 11:44 +0530, Kaushal M a écrit :
> >> On Sun, Feb 7, 2016 at 2:34 PM, Michael Scherer  
> >> wrote:
> >> > Le samedi 06 février 2016 à 18:17 -0500, Vijay Bellur a écrit :
> >> >> I think starting around 0900 UTC on Friday of next week (12th Feb)
> >> >> should be possible. We should be done with 3.7.8 before that and can
> >> >> afford a bit of downtime then. In case any assistance is needed post the
> >> >> migration, we can have folks around the clock to help.
> >> >>
> >> >> If migration fails for an unforeseen reason, would we be able to
> >> >> rollback and maintain status quo?
> >> >
> >> > Yes. Worst case, I think people would just redo a few reviews or push
> >> > again patch.
> >> >
> >> > Also, since gerrit is critical, I wonder what is the support of gerrit
> >> > for slaves and replication.
> >>
> >> Michael are you okay with the time? If you are, I think we should
> >> announce the migration.
> >
> > I am ok.
> 
> So as discussed in the community meeting, we will be announcing the
> migration and downtime. Vijay, you said you required the exact
> schedule? This is what I expect
> 
> Friday 12th Feb 2016
> 
> 0900 UTC : build.gluster.org and review.gluster.org are taken down and
> migration begins.
> <1-2 hrs?>: Michael copies over data onto the RH community infra and
> sets up the VMs.
> : The DNS records are updated, and some time is for it to propogate.
> <3hr?>: Verify everything is working well (I can help with this). We'd
> possibly need to run a regression job, so this will take longest I
> think.
> 
> 1700UTC : We announce the finish of the migration and open
> the services back up. If migration failed, we bring the existing
> servers back on, and continue on.
> 
> 
> Also, Michael are you happy migrating just one server or both?

ideally, I would prefer both, but as i had trouble to move the jenkins
VM while it was running, I couldn't prepare the network setup. I would
need to open a few ports, etc, so that requires tickets to IT.

>  I case
> you can only do one server we'd like Jenkins to migrated out.

The problem is that this requires tome network changes, unlike the
gerrit one, where the work was already done.


-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-Maintainers] Gluster community and external test infra

[Sankarshan Mukhopadhyay]

On Wed, Feb 10, 2016 at 6:45 PM, Kaushal M  wrote:
> On Wed, Feb 10, 2016 at 6:29 PM, Raghavendra Talur  wrote:
>> Hi,
>>
>> I read about openstack community and how they allow external test infra to
>> report back on the main CI.
>>
>> Read more here:
>> https://www.mirantis.com/blog/setting-external-openstack-testing-system-part-1/
>>

It would be relevant to highlight "In short, an external testing
platform enables third parties to run tests — ostensibly against an
OpenStack environment that is configured with that third party’s
drivers or hardware — and report the results of those tests on the
code review of a proposed patch."

The 3rd party integration and scenario testing path works for a
project like OpenStack because there are (i) such drivers from third
parties which need to be merged into upstream/mainline after sanity
checks and (ii) the distributions/flavors of OpenStack would need
testing as well.

>> I have setup a jenkins server in RedHat blr lab which has 27 slaves.
>> Also, the jenkins server is intelligent enough to distribute tests across 27
>> nodes for the same patch set so that the run completes in ~30mins.
>>
>>
>> Now onto the questions:
>> 1. Would gluster community accept a +1 from this jenkins, if we follow
>> similar policy like openstack does with external test infra?
>> 2. Would RedHat allow a such thing if it is promised that trigger won't
>> happen from Gerrit server but manually from within the VPN of RedHat?
>>

This harness could also reside in any world-available service
instances, if they are available and maintained. It would be
appropriate to check with the specific teams dealing with instances of
internal hosted services reaching out to externally available ones
before arriving at a decision.

>> NOTE: This mail is sent to maintain...@gluster.org keeping in view the
>> security concerns before asking opinion from wider audience. Also don't
>> reply back with any RedHat confidential informantion.

> +gluster-infra

Perhaps Michael or, anyone else could provide a preliminary guidance.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Migrating Gerrit and Jenkins out of iWeb

[Kaushal M]

On Wed, Feb 10, 2016 at 1:53 PM, Michael Scherer  wrote:
> Le mercredi 10 février 2016 à 11:44 +0530, Kaushal M a écrit :
>> On Sun, Feb 7, 2016 at 2:34 PM, Michael Scherer  wrote:
>> > Le samedi 06 février 2016 à 18:17 -0500, Vijay Bellur a écrit :
>> >> I think starting around 0900 UTC on Friday of next week (12th Feb)
>> >> should be possible. We should be done with 3.7.8 before that and can
>> >> afford a bit of downtime then. In case any assistance is needed post the
>> >> migration, we can have folks around the clock to help.
>> >>
>> >> If migration fails for an unforeseen reason, would we be able to
>> >> rollback and maintain status quo?
>> >
>> > Yes. Worst case, I think people would just redo a few reviews or push
>> > again patch.
>> >
>> > Also, since gerrit is critical, I wonder what is the support of gerrit
>> > for slaves and replication.
>>
>> Michael are you okay with the time? If you are, I think we should
>> announce the migration.
>
> I am ok.

So as discussed in the community meeting, we will be announcing the
migration and downtime. Vijay, you said you required the exact
schedule? This is what I expect

Friday 12th Feb 2016

0900 UTC : build.gluster.org and review.gluster.org are taken down and
migration begins.
<1-2 hrs?>: Michael copies over data onto the RH community infra and
sets up the VMs.
: The DNS records are updated, and some time is for it to propogate.
<3hr?>: Verify everything is working well (I can help with this). We'd
possibly need to run a regression job, so this will take longest I
think.

1700UTC : We announce the finish of the migration and open
the services back up. If migration failed, we bring the existing
servers back on, and continue on.


Also, Michael are you happy migrating just one server or both? I case
you can only do one server we'd like Jenkins to migrated out.


> --
> Michael Scherer
> Sysadmin, Community Infrastructure and Platform, OSAS
>
>
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Migrating Gerrit and Jenkins out of iWeb

[Michael Scherer]

Le mercredi 10 février 2016 à 11:44 +0530, Kaushal M a écrit :
> On Sun, Feb 7, 2016 at 2:34 PM, Michael Scherer  wrote:
> > Le samedi 06 février 2016 à 18:17 -0500, Vijay Bellur a écrit :
> >> I think starting around 0900 UTC on Friday of next week (12th Feb)
> >> should be possible. We should be done with 3.7.8 before that and can
> >> afford a bit of downtime then. In case any assistance is needed post the
> >> migration, we can have folks around the clock to help.
> >>
> >> If migration fails for an unforeseen reason, would we be able to
> >> rollback and maintain status quo?
> >
> > Yes. Worst case, I think people would just redo a few reviews or push
> > again patch.
> >
> > Also, since gerrit is critical, I wonder what is the support of gerrit
> > for slaves and replication.
> 
> Michael are you okay with the time? If you are, I think we should
> announce the migration.

I am ok.
-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1291537] [RFE] Provide mechanism to spin up reproducible test environment for all developers

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1291537



--- Comment #12 from Vijay Bellur  ---
REVIEW: http://review.gluster.org/13251 (vagrant-test: Use pre-baked box for
better perf) posted (#4) for review on master by Raghavendra Talur
(rta...@redhat.com)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=9mXfcRwOUx=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra