[Gluster-infra] Marcelo Barbosa presentation

[Michael Scherer]

Le mercredi 11 février 2015 à 21:29 +0100, Niels de Vos a écrit :
> On Wed, Feb 11, 2015 at 01:37:35PM +0100, Michael Scherer wrote:
> > Le mercredi 11 février 2015 à 11:47 +0100, Niels de Vos a écrit :
> > > On Wed, Feb 11, 2015 at 11:24:43AM +0100, Michael Scherer wrote:
> > > > Le mercredi 11 février 2015 à 11:22 +0100, Niels de Vos a écrit :
> > > > > On Wed, Feb 11, 2015 at 12:19:32AM -0200, Marcelo Barbosa wrote:
> > > > > > Hey Infra guys,
> > > > > > 
> > > > > >    My names is Marcelo Barbosa, my nickname in Fedora Project is
> > > > > > "firemanxbr"(https://fedoraproject.org/wiki/User:Firemanxbr), my friend
> > > > > > Niels talk about Gluster project and your infra for engineers support, I
> > > > > > think can help with some time and working for tools much better for
> > > > > > engineers.
> > > > > >    About me: I work with Linux since 1998, my first Job was in Conectiva
> > > > > > Linux distribution in Brazil, in this time I working in Datacom.ind.br, a
> > > > > > brazilian company that make hardware and software to switches core for top
> > > > > > 100 telecom companys in latin america, my team is DevOps and my principal
> > > > > > job is create and maintenance this tools for all our engineers:
> > > > > 
> > > > > Hi Marcelo!
> > > > > 
> > > > > Thanks for sending your introduction. I think your assistence is very
> > > > > welcome for the long pending Gerrit update that is needed. Justin and
> > > > > Michael were looking into this, but I think they got side tracked with
> > > > > other work.
> > > > > 
> > > > > Would you be willing to help getting our Gettit instance updated to a
> > > > > current version? I think it also includes moving Gerrit to a different
> > > > > hosting provider/VM. Justin and Michael should be able to explain more
> > > > > details. I hope you guys can work out a a plan and some rough timeline
> > > > > for this topic.
> > > > 
> > > > I do think Justin is more able than me to speak of gerrit. I am not sure
> > > > I have access to that VM. But ideally, if we could set it on a fresh
> > > > server ( managed by salt ), it would be better. I can give access to the
> > > > VM, to the salt master and stuff ( and give access to others, i just got
> > > > side tracked by others projects for announcing properly the setup ).
> > > 
> > > That definitely sounds like a very good way forward! It would be great
> > > if you can post some documentation about the salt setup in the wiki or
> > > somewhere else.
> > 
> > When it is finished, yes :)
> > 
> > ( and when we decide if we keep wiki, use something else, etc )
> 
> I do not think it needs to be finished. Something, somewhere where
> others can add more notes/details would be helpful. It's all about
> getting a start for it available, and give others the ability to
> contribute.

So, to quickly explain.

We have salt-master.gluster.org, on rackspace. There is 3 git
repositories ( in /srv/git_repos/, I think ) :
- one for gluster states ( ie, the code )
- one for data (  pillars, in saltstack terms )
- one for private data, same as the 2nd, but not to be published.

There is post commit magic extracting all of this and triggering run
from the master to the minion, applying states and stuff. 

However, currently, the server is set as "log as root with key", and I
would want to have a set of user in a group to be able to push. But for
that, I need to double/triple check permission on the repo, and make
sure salt do not helpfully fix them ( the salt-master is managed by
saltstack ).  I did sent a patch to them for that, who was merged and
likely in a release now. 

But before that, no one can contribute much.
And of course, I need to explain how saltstack work, and document what
is currently managed, which servers, etc :)

Would people need more informations ( as it is not obvious what is
missing right away ) ?

I would ideally have some kind of ldap ( maybe go with freeipa ), and
more important, having a place to publish the configuration ( rather not
do that from slat-master ), and I am not sure if we want to do that from
the forge, github or something else.

-- 
Michael Scherer
Open Source and Standards, Sysadmin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://www.gluster.org/pipermail/gluster-infra/attachments/20150212/8b54da9b/attachment.sig>