[Gluster-infra] glusterfs github is out of sync.

[Kaushal M]

On Tue, Nov 24, 2015 at 7:37 PM, Michael Scherer <mscherer at redhat.com> wrote:
> Le lundi 23 novembre 2015 à 15:28 +0530, Kaushal M a écrit :
>> On Mon, Nov 23, 2015 at 3:09 PM, Michael Scherer <mscherer at redhat.com>
>> wrote:
>> > Le lundi 23 novembre 2015 à 09:18 +0530, Kaushal M a écrit :
>> >> On Wed, Oct 28, 2015 at 4:48 PM, Michael Scherer <mscherer at redhat.com>
>> wrote:
>> >> > Le mercredi 28 octobre 2015 à 16:24 +0530, Kaushal M a écrit :
>> >> >> On Wed, Oct 28, 2015 at 4:01 PM, Michael Scherer <mscherer at redhat.com>
>> wrote:
>> >> >> > Le mercredi 28 octobre 2015 à 15:57 +0530, Kaushal M a écrit :
>> >> >> >> Authentication failure is causing the replication plugin pushes to
>> fail.
>> >> >> >>
>> >> >> >> The gerrit ssh key was attached to Avati's account IIRC. Maybe he's
>> >> >> >> removed the key by mistake.
>> >> >> >
>> >> >> > Nope.
>> >> >> > The key was removed due to the compromise Amye posted about on
>> >> >> > gluster-users. You can ask her details, cause she will likely be
>> much
>> >> >> > more polite than me to explain the whole topic :)
>> >> >>
>> >> >> An ssh key pair is still present on review.gluster.org though.
>> >> >
>> >> > So maybe not the same key. Which one is it ?
>> >> >
>> >> >> >
>> >> >> >> It'll be good if we add keys to an org instead of individual user's
>> >> >> >> account.  But as we can't do that, what do people feel about
>> creating
>> >> >> >> a `glusterbot` or `glusterant` account controlled by the community?
>> >> >> >
>> >> >> > I am ok with the idea but:
>> >> >> > - it need to be a account using a email the project can recover,
>> not a
>> >> >> > personal one
>> >> >>
>> >> >> I think we can setup an email alias or a mailing list on the gluster
>> >> >> mail infra, which includes the admins of the Gluster org in Github.
>> >> >
>> >> > I am fine with the idea. But now, that mean we will have a official
>> >> > group of people, and I rather not have a group "admin of github and
>> adin
>> >> > of gerrit and admin of rackspace and admin of the infra".
>> >> >
>> >> > So if we go this way, I will likely start to remove people access and
>> >> > centralize all in a ldap. (sync between github/rackspace and that list
>> >> > is a open problem).
>> >> >
>> >>
>> >> Michael, can we get this done now?
>> >>  Or do we need to wait for the
>> >> community ldap to be setup?
>> >
>> > The ldap is here ( need to create accounts, but I need to know who want
>> > one, so we get back on the start, ie a list of people).
>> >
>> > But there is no need for a ldap to decide who is in that group. You just
>> > need to decide who go in the group, and what the group do cover, which
>> > is something that can be done by mail.
>> >
>> > rest is a technical details I can fix later, but I can't (or rather I do
>> > not want) decide who is volunteer for the duty.
>> >
>>
>> We can start by creating accounts for people managing the infra. The
>> members of the Admin/owners groups in Github/Gerrit can be used as a seed
>> for this.
>>
>> >> We don't want to keep pushing to Github
>> >> manually.
>> >
>> > So count that as a incentive for giving the list of people, and how we
>> > decide who go in the group.
>>
>> Well I had to manually push this time. I wouldn't want to do it again.
>> Comparing the two lists above, I get the following common names.
>> - Avati
>> - Humble
>> - Justin
>> - Me
>> - You
>> - Vijay
>>
>> Avati and Justin are no longer heavily involved in the community, so they
>> could be dropped. I'd add Neils and Kaleb, as they've also done some(~)
>> infra management. And Amye as well.
>
> Perfect :)
>
> So I need for each:
> - preferred username
> - a email where I can send the temp password
> - if people want to have some information

Cool! I'll ask everyone to do this right away.

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