Re: [Gluster-infra] Request for a Gerrit account for the CentOS CI Jenkins

2016-01-04 Thread Kaushal M 
On Mon, Jan 4, 2016 at 9:58 PM, Michael Scherer  wrote:
> Le lundi 04 janvier 2016 à 16:33 +0100, Niels de Vos a écrit :
>> On Mon, Jan 04, 2016 at 04:16:14PM +0100, Michael Scherer wrote:
>> > Le lundi 04 janvier 2016 à 09:24 +0530, Kaushal M a écrit :
>> > > On Sun, Jan 3, 2016 at 6:34 PM, Niels de Vos  wrote:
>> > > > Hi!
>> > > >
>> > > > I would like to request a Gerrit account for the CentOS CI Jenkins
>> > > > (ci.centos.org) so that we can setup jobs based on Gerrit triggers.
>> > > > Could you please create an account with the following details?
>> > > >
>> > > >   Username: centos-ci
>> > > >   Email: (hmm, maybe a new list, or alias like centos...@gluster.org?)
>> > > >   Public-key: ssh-rsa 
>> > > > B3NzaC1yc2EDAQABAAABAQDCu9qWPHYJm+s4Nq1seE82Q+m3Ilq82Z+GkK88tgy7aNMeJ5DWeHMTo+jCu+sV68uXXAGIC0IvGeQPeTae1Rk6WYyPz+l/LQUME051i/ke0wG/1SaaWkduK6KDqnC9xi4Ud/ZDF+/StIqlSKM7/FIPzcqOV3TAEU4B82MRA3NaNJrTHLgdTqqDXZc9snEp7pBsWfTu4ojeV/Nv2dcdfcdWkT9VSDIUmhfGYODAnEQACrw0P4V17gkPMYV96jgU06HIXiSz20JnA1E6PazAtHLEPOfQR4D5csJ+3DpoBek3PUB8E4kqRAouz4qIWzum4Sc2d1AE8UTkxIWBXjf5bkGd
>> > > >  centos...@review.gluster.org
>> > > >   See-also: 
>> > > > http://review.gluster.org/Documentation/access-control.html#examples_cisystem
>> > > >
>> > >
>> > > I can create the bot account, but someone else (Misc) needs to create
>> > > the mail alias/list.
>> >
>> > Well, what do we want to do with it ?
>> >
>> > And what kind of information will be sent to that email ?
>>
>> Not sure... Anything that gets sent to Gerrit users, I guess? If a
>> Gerrit account does not require an email address, that would probably be
>> easier. Email addresses need to be unique, I think, otherwise it'll be a
>> weird auto-competion in the Gerrit UI.
>
> But so, who need to read that, and is there some "reset password" system
> using this email ? ( in which case, we shouldn't maybe push that to a
> public ml)

AFAIK emails are only sent if you register for alerts. Bot accounts
are created under  the 'Non interactive users' group by gerrit admins.
I believe you wouldn't be able to login to the account via the
web-interface, so there is no way to register for alerts. I'll check
if I can create  the account without providing an email address.

> --
> 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] Switching from salt to ansible ?

2016-01-04 Thread Kaushal M 
On Mon, Jan 4, 2016 at 9:57 PM, Michael Scherer  wrote:
> Hi,
>
> so over the holidays, I was pondering on moving to ansible from salt.

I'd like this as well, as I'm more familiar with Ansible as well. If
switching to Ansible helps reduce the burden on you, I think we should
do the switch.

>
> So the reasons are numerous:
>
> - I am personally much more efficient with ansible than with salt
> (despite using salt for 1 year). While the 2 tools do the same basic
> stuff, there is always some difference (like user vs owner), and there
> is a totally different philosophy when it come to multiple servers
> orchestration (one example is how I do deploy freeipa on salt vs
> ansible).
>
> - Since I use ansible for most others projects, I do already have a few
> roles for most of the thing I want to deploy (freeipa, nagios, etc), and
> adding features on them and then again on salt is not very efficient.
>
> - One of the initial reasons to choose salt was a tiny margin of people
> who know it in the community, vs ansible. I suspect this is no longer
> valid. For example, the vagrant image for developper is made using
> ansible, and I know a few people in the dev community who use ansible. I
> still think no one grok salt.
>
> - Another of the reason of using salt vs ansible is that salt was much
> faster to apply configuration, especially if done on git commit. While
> that's true, I managed to make it good enough on manageiq.org using
> smart post-commit hook, and salt is getting also slower the more stuff
> we add to configuration.
>
> - salt in epel is still using a old version ( for dependencies reasons
> ). While this is working well enough, it make contributing quite
> difficult, and prevent using some new features that are needed.
>
> - having a client/server model is something that caused trouble with
> puppet when they decided to support only 1 version of ruby (around the
> ruby 2.0 time frame). And given the transition of python2 and 3 is
> happening right now in Fedora, I foresee this might be the same kind of
> issue for salt.

I think this would be a problem with Ansible as well, as it depends on
python2. I've faced some small hiccups getting ansible to manage Arch
Linux which uses python3 by default.

>
> - Fedora is using ansible, and while we can't reuse their code that
> much, we can at least take it and adapt.
>
> Now, there is a few downsides:
>
> - it mean rewriting most of the stuff we already have
>
> - it mean that we depend on sshd to be running. IE, if we screwed ssh
> config (happened in the past), we can't just use salt to fix it.
>
> - it also mean that we will have a ssh key to connect as root on a
> server, and i am not that confortable with the idea (provided that we
> use the regular method of using ansible, ie push based)
>
> and maybe other I didn't think of.

I've sometime had Ansible modules which failed to run on the remote
host because it lacked some python packages. This could be a problem
for Ansible. I've not faced this with Salt yet, maybe because the
remote hosts need to have salt installed which would pull in all
dependencies.

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

Re: [Gluster-infra] Request for a Gerrit account for the CentOS CI Jenkins

2016-01-04 Thread Kaushal M 
On Tue, Jan 5, 2016 at 10:52 AM, Kaushal M  wrote:
> On Tue, Jan 5, 2016 at 9:30 AM, Kaushal M  wrote:
>> On Mon, Jan 4, 2016 at 9:58 PM, Michael Scherer  wrote:
>>> Le lundi 04 janvier 2016 à 16:33 +0100, Niels de Vos a écrit :
 On Mon, Jan 04, 2016 at 04:16:14PM +0100, Michael Scherer wrote:
 > Le lundi 04 janvier 2016 à 09:24 +0530, Kaushal M a écrit :
 > > On Sun, Jan 3, 2016 at 6:34 PM, Niels de Vos  wrote:
 > > > Hi!
 > > >
 > > > I would like to request a Gerrit account for the CentOS CI Jenkins
 > > > (ci.centos.org) so that we can setup jobs based on Gerrit triggers.
 > > > Could you please create an account with the following details?
 > > >
 > > >   Username: centos-ci
 > > >   Email: (hmm, maybe a new list, or alias like 
 > > > centos...@gluster.org?)
 > > >   Public-key: ssh-rsa 
 > > > B3NzaC1yc2EDAQABAAABAQDCu9qWPHYJm+s4Nq1seE82Q+m3Ilq82Z+GkK88tgy7aNMeJ5DWeHMTo+jCu+sV68uXXAGIC0IvGeQPeTae1Rk6WYyPz+l/LQUME051i/ke0wG/1SaaWkduK6KDqnC9xi4Ud/ZDF+/StIqlSKM7/FIPzcqOV3TAEU4B82MRA3NaNJrTHLgdTqqDXZc9snEp7pBsWfTu4ojeV/Nv2dcdfcdWkT9VSDIUmhfGYODAnEQACrw0P4V17gkPMYV96jgU06HIXiSz20JnA1E6PazAtHLEPOfQR4D5csJ+3DpoBek3PUB8E4kqRAouz4qIWzum4Sc2d1AE8UTkxIWBXjf5bkGd
 > > >  centos...@review.gluster.org
 > > >   See-also: 
 > > > http://review.gluster.org/Documentation/access-control.html#examples_cisystem
 > > >
 > >
 > > I can create the bot account, but someone else (Misc) needs to create
 > > the mail alias/list.
 >
 > Well, what do we want to do with it ?
 >
 > And what kind of information will be sent to that email ?

 Not sure... Anything that gets sent to Gerrit users, I guess? If a
 Gerrit account does not require an email address, that would probably be
 easier. Email addresses need to be unique, I think, otherwise it'll be a
 weird auto-competion in the Gerrit UI.
>>>
>>> But so, who need to read that, and is there some "reset password" system
>>> using this email ? ( in which case, we shouldn't maybe push that to a
>>> public ml)
>>
>> AFAIK emails are only sent if you register for alerts. Bot accounts
>> are created under  the 'Non interactive users' group by gerrit admins.
>> I believe you wouldn't be able to login to the account via the
>> web-interface, so there is no way to register for alerts. I'll check
>> if I can create  the account without providing an email address.
>
> Huh, our old version of gerrit doesn't have a non-interactive users group :-(
> Another reason to update gerrit.
>

I created the account and added it to the 'Event Streaming Users'
group. This should allow the ci.centos.org to stream events from
review.gluster.org. It did not require an email address to be created.
We can add and address later if required.

>>
>>> --
>>> 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] Jenkins has lost its connection to Gerrit again :-/

2016-01-04 Thread Kaushal M 
On Mon, Jan 4, 2016 at 4:58 PM, Niels de Vos  wrote:
> On Wed, Dec 30, 2015 at 11:47:14AM +0100, Niels de Vos wrote:
>> Jenkins is not triggering smoke and regression tests at the moment. I
>> have triggered smoke and regression tests for many patch sets manually
>> through:
>>
>>  1. open https://build.gluster.org/gerrit_manual_trigger/
>>  2. search: "status:open after:2015-12-27 label:Verified=0 NOT 
>> label:Code-Review=-1"
>>  3. select all changes
>>  4. click "trigger selected"
>>
>> Could someone look into getting the connection between Jenkins and
>> Gerrit up again?
>>
>> Thanks,
>> Niels
>
> This does not seem to have been resolved yet. I've executed the above
> procedure again. Many regression tests have been scheduled now.
>
> Niels
>

I've scheduled a Jenkins restart, which should fix the connection.
I've also aborted the following hung netbsd regression runs, they can
be retriggered after Jenkins restarts.
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13124/
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13126/
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13130/
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13132/

~kaushal

> ___
> Gluster-infra mailing list
> Gluster-infra@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-infra
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Request for a Gerrit account for the CentOS CI Jenkins

2016-01-04 Thread Michael Scherer 
Le lundi 04 janvier 2016 à 09:24 +0530, Kaushal M a écrit :
> On Sun, Jan 3, 2016 at 6:34 PM, Niels de Vos  wrote:
> > Hi!
> >
> > I would like to request a Gerrit account for the CentOS CI Jenkins
> > (ci.centos.org) so that we can setup jobs based on Gerrit triggers.
> > Could you please create an account with the following details?
> >
> >   Username: centos-ci
> >   Email: (hmm, maybe a new list, or alias like centos...@gluster.org?)
> >   Public-key: ssh-rsa 
> > B3NzaC1yc2EDAQABAAABAQDCu9qWPHYJm+s4Nq1seE82Q+m3Ilq82Z+GkK88tgy7aNMeJ5DWeHMTo+jCu+sV68uXXAGIC0IvGeQPeTae1Rk6WYyPz+l/LQUME051i/ke0wG/1SaaWkduK6KDqnC9xi4Ud/ZDF+/StIqlSKM7/FIPzcqOV3TAEU4B82MRA3NaNJrTHLgdTqqDXZc9snEp7pBsWfTu4ojeV/Nv2dcdfcdWkT9VSDIUmhfGYODAnEQACrw0P4V17gkPMYV96jgU06HIXiSz20JnA1E6PazAtHLEPOfQR4D5csJ+3DpoBek3PUB8E4kqRAouz4qIWzum4Sc2d1AE8UTkxIWBXjf5bkGd
> >  centos...@review.gluster.org
> >   See-also: 
> > http://review.gluster.org/Documentation/access-control.html#examples_cisystem
> >
> 
> I can create the bot account, but someone else (Misc) needs to create
> the mail alias/list.

Well, what do we want to do with it ?

And what kind of information will be sent to that email ?
-- 
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] Request for a Gerrit account for the CentOS CI Jenkins

2016-01-04 Thread Niels de Vos 
On Mon, Jan 04, 2016 at 04:16:14PM +0100, Michael Scherer wrote:
> Le lundi 04 janvier 2016 à 09:24 +0530, Kaushal M a écrit :
> > On Sun, Jan 3, 2016 at 6:34 PM, Niels de Vos  wrote:
> > > Hi!
> > >
> > > I would like to request a Gerrit account for the CentOS CI Jenkins
> > > (ci.centos.org) so that we can setup jobs based on Gerrit triggers.
> > > Could you please create an account with the following details?
> > >
> > >   Username: centos-ci
> > >   Email: (hmm, maybe a new list, or alias like centos...@gluster.org?)
> > >   Public-key: ssh-rsa 
> > > B3NzaC1yc2EDAQABAAABAQDCu9qWPHYJm+s4Nq1seE82Q+m3Ilq82Z+GkK88tgy7aNMeJ5DWeHMTo+jCu+sV68uXXAGIC0IvGeQPeTae1Rk6WYyPz+l/LQUME051i/ke0wG/1SaaWkduK6KDqnC9xi4Ud/ZDF+/StIqlSKM7/FIPzcqOV3TAEU4B82MRA3NaNJrTHLgdTqqDXZc9snEp7pBsWfTu4ojeV/Nv2dcdfcdWkT9VSDIUmhfGYODAnEQACrw0P4V17gkPMYV96jgU06HIXiSz20JnA1E6PazAtHLEPOfQR4D5csJ+3DpoBek3PUB8E4kqRAouz4qIWzum4Sc2d1AE8UTkxIWBXjf5bkGd
> > >  centos...@review.gluster.org
> > >   See-also: 
> > > http://review.gluster.org/Documentation/access-control.html#examples_cisystem
> > >
> > 
> > I can create the bot account, but someone else (Misc) needs to create
> > the mail alias/list.
> 
> Well, what do we want to do with it ?
> 
> And what kind of information will be sent to that email ?

Not sure... Anything that gets sent to Gerrit users, I guess? If a
Gerrit account does not require an email address, that would probably be
easier. Email addresses need to be unique, I think, otherwise it'll be a
weird auto-competion in the Gerrit UI.

Niels


signature.asc
Description: PGP signature
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Revive gluster-swift repo

2016-01-04 Thread Vijay Bellur 

On 01/04/2016 03:38 AM, Prashanth Pai wrote:


we need to revive gluster-swift repo 
(http://review.gluster.org/#/admin/projects/gluster-swift,access) which has lagged far 
behind it's parent (https://github.com/openstack/swiftonfile/commits/icehouse). Could you 
add me to "Gluster-Swift-Admin" group on Gerrit so that I can get the repo up 
to date ? The rebase to kilo work would be sent to gluster-swift repo for review once 
it's up to date.



Have added Prashanth as admin for gluster-swift repo in gerrit. Adding 
gluster-infra to notify this change.


Regards,
Vijay

___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra