Bug 1711950

Misc, can you please take a look at it.

Ok so before opening a account, I would like to discuss the plan for automating that.
I kinda feel unease of the fact we are still doing everything manually (especially after the nfs ganesha issue that we found internally), and while I do not have personnaly the ressources nor time to automate (was on TODO list, but after Nigel departure and the migration to AWS, this was pushed down the line), I would like to take on this opportunity to first discuss that, and then open the account. 

In that order, because experience show that the reverse order is not consecutive of any action (curiously, folks listen to me more when they wait on me for something, so I hope folks will excuse me for that obvious blackmail, but ot should be quick).

So, how long would it take to automate the release from Jenkins to download.gluster, and who would be dedicated on it on the gluster side ?
(once we agree on a deadline, I will create a account that expire automatically after that time, just to make sure we do not leave a gapping hole open)

Hi Misc,

We have built the debian packages for glusterfs 6.2, and waiting for the creation of accounts to upload the packages. Here, https://github.com/gluster/glusterfs/issues/683 is a github issue, asking reasons for delay on the same. It will be helpful if we are unblocked by this soon. Can you do the needful?

About automating the procedure, I will initiate a discussion with the team, and get back to you.

Sure give me a deadline, and I will create the account. I mean, I do not even need a precise one.

Would you agree on "We do in 3 months", in which case I create the account right now (with expiration as set).

(I need a public ssh key and a username)

(In reply to M. Scherer from comment #2)
> Ok so before opening a account, I would like to discuss the plan for
> automating that.
> I kinda feel unease of the fact we are still doing everything manually
> (especially after the nfs ganesha issue that we found internally), and while
> I do not have personnaly the ressources nor time to automate (was on TODO
> list, but after Nigel departure and the migration to AWS, this was pushed
> down the line), I would like to take on this opportunity to first discuss
> that, and then open the account. 
> 
> In that order, because experience show that the reverse order is not
> consecutive of any action (curiously, folks listen to me more when they wait
> on me for something, so I hope folks will excuse me for that obvious
> blackmail, but ot should be quick).
> 
> So, how long would it take to automate the release from Jenkins to
> download.gluster, and who would be dedicated on it on the gluster side ?
> (once we agree on a deadline, I will create a account that expire
> automatically after that time, just to make sure we do not leave a gapping
> hole open)

You, NIgel, and I had a discussion in Berlin over two years ago about this and Nigel was supposed to automate it in Jenkins.

Someone like Sankarshan will have to identify a resource for doing the work now.

Yup, but clearly, as long as someone was doing the job manually, this was set as a lesser priority than a lot of things (like fixing the fires all over the place). The increasing backlog of tasks do not make me think we can do it without someone taking ownership of that, and as you rightfully point, that's something we all want since more than 2 years :/

@misc (In reply to M. Scherer from comment #4)
> Sure give me a deadline, and I will create the account. I mean, I do not
> even need a precise one.
> 
> Would you agree on "We do in 3 months", in which case I create the account
> right now (with expiration as set).
> 
> (I need a public ssh key and a username)

We have already taken up the task of automating building and packaging. Details can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1727727. 

Please create the account.
Below are the required details:
Public ssh key: 
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCifwFXjkLXFwnlTBMXFgTEHAA1Vavzti41B4Yp1RJYtCuJ91s+P5YHc2j4a/wpVquPJboNuv9wtqknmd5SJYBXB11dinNfHfvE+gCN9Osdn64/om9i3pIpQQeY6uvF4MF9yfyx8huEWFZeaOiljvmTZ3//4kzsJHK2yKCmJFhy5Zcg9+WMM2bjfACjlFDIuOG2kqaRM8tGggOQG9iQ/VElWOTxJkHUJaP50PWdwEHHoiCKmipe5xEcSR/6qubaF6VpMfBLmrjmJMqkjVozryVweHBLn3oQfOkJmlErwJox7hLFuk5V4fvVine5xrWKygw/kA2Mpr7Q1zXg5moZHbCP root

User name: sacharya

As said in the comment #2 and comment #4, what is the deadline for the account closure ? 

If I do not get a answer, then I will just decide on "3 month after the creation" and then deploy.

Hari, Can you please address the above query?

We are trying to finish it within this sprint (each sprint is for 3 weeks).
So we will assume that we should be done in a month with the automation.

ok so 3 months is enougn (cause i also do not want to push unrealisitic deadline or more pressure, plus shit happen), I will add the account as soon as the previous ansible run finish. And if that's not enough, we can of course keep it open longer, just to be clear. But after jenkins issue last month, and the old compromise last time, we can't let stuff open too long if they are not going to clean themself.

I created the user, tell me if it doesn't work. The server is download.rht.gluster.org (not download.gluster, who is a proxy).

Hi Misc, 

We are almost done with the automation work. It may take a while for completion. Please revive the the account for 3 more months, as we need to upload the packages on scheduled dates.

I have been working on the requirement for automation here (https://github.com/harigowtham/ubuntu-debian-build-glusterfs) as of now. 
Will send it to gerrit once i feel its in a state to review.

Need to work on the signing the packages and the ansible file to get the builder machine ready.

ok, done, I extended to 3 mor emonths, so around march.

Hi misc, 

As shwetha and me are handling package building together, Please create the account for me as well so that whole load will not be on her and in her absence we won't be blocked

Below are the required details:
Public ssh key: 
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHKKTwASBKVg4nN3p1vUj87906qFi8KQb/gTmt7ITPDg1GAvVhMJhbC4pT58/k9YjDf2Ez07VZ7fTYs9hqWHF4ZsJ2rbO2MPaHl4Fnfb8MP+Wq33juiznKRZU9+TRTFt83rDoRjDFwzhfGt6zdBPam6Etu0mR55OvWg8XM35wbdW0OP/pjIdQdjVoDp+YdpaX43lCr3M80NsbjAxk7xcPTrpqAK90qpVw1C5mqwHNeqJIGK/enADhaDaMhBPoNpWK1cy5xMnJcBbYXjrUZ4yqmhzJ48yUQiHYzlZZkx4JirbdZzE7FfRZt88crec9KTp1a/GLznP3L0dFA59SWAMKV root@shep-mac 

User name: spamecha

ok, that should be done now I wrote a role to handle that.

Hi Misc,

Can you create please passwordless login for the accounts or give the temporary password, so that we can change it later. Though the account is created, I am unable to login, because I do not know what the password is.

[sacharya@localhost ~]$ ssh download.rht.gluster.org
sacharya.gluster.org's password: 
Permission denied, please try again.

Indeed, I need to set password expiration. I did fix for sacharya manually, I need to atumate that. Sorry for forgetting that step, tell me if it work (it will ask for a password on first login, or you can use "passwd" to set the password)

It is asking for a password, but I do not know what is the password. If you had set one, please let me know what it is.

Mhh, it should let you connect without password, and then "passwd" shouldn't ask for a password. Let me test again, cause I did that using "su", but maybe there is something I missed with openssh.

So after adding my ssh key, I was able to connect, and then use "passwd" to set the new password. Can you detail what you did and where it did fail so I can replicate the problem ?

I see that I am able to connect now. ssh is allowing me to connect without password. Somehow, it was not the case before.

This bug is moved to https://github.com/gluster/project-infrastructure/issues/14, and will be tracked there from now on. Visit GitHub issues URL for further details