[Gluster-infra] configuration management for the gluster infra, RFC
mscherer at redhat.com
Wed Aug 20 14:47:28 UTC 2014
Le mercredi 20 août 2014 à 15:19 +0530, Humble Chirammal a écrit :
> On 08/20/2014 02:42 PM, Michael Scherer wrote:
> > Le mardi 19 août 2014 à 18:24 +0100, Justin Clift a écrit :
> > > On 19/08/2014, at 5:29 PM, Michael Scherer wrote:
> > > <snip>
> > > > On term of constraints, I suppose that we need something that work on
> > > > RHEL and Netbsd.
> > > For the Jenkins slave infrastructure we have various Fedora slaves,
> > > some CentOS 6.5 slaves, and other bits:
> > >
> > > * We have a Jenkins NetBSD slave in Rackspace - manually created from an
> > > initial CentOS install - since Rackspace doesn't offer NetBSD.
> > >
> > > * We also have a Jenkins FreeBSD slave in Rackspace.
> > >
> > > * GlusterFS 3.6 will support OSX fuse clients natively, so we've been
> > > getting some OSX VM's set up to become Jenkins slaves. (still needs
> > > work)
> Hi Michael,
> Thanks for bringing this up.
> I have configured Jenkins instance for a job in an internal server
> ( http://rhs-client34.lab.eng.blr.redhat.com:8080/job/libgfapi-qemu/)
> which I would like to get migrated to an external server.
> During this configuration I have learnt something about Jenkins, so I
> can offer some help if required.
Indeed, having some help on jenkins would be good. I didn't used it much
personally, so the more we are, the better.
> > Technically, we can decide to manage os installation and provisioning,
> > especially if we want to test and spin VMs, but this would requires
> > something like cobbler, etc and a more complex setup. I guess we can
> > safely push that to later :)
> We can also consider docker .
We wouldn't be able to dockerize the non linux os, and we would still
need to manage docker containers hosts anyway :)
And I am personally not very convinced of docker for regular packaged
rpms. At least, using apache outside of docker mean there is proper
selinux containment, which is lacking on the docker side ( ie, ther eis
just generic svirt support ).
> iic, most people struggle on:
> * Unawareness of the infrastructure we have .
> * Who owns those.
> * No proper documentation of what exist for gluster , where it is and
> whom to contact.
> * Who is responsible for keeping things updated...etc
yeah, having a list would help. We discussed that in the past, Justin
gave a few servers, but no one else chimed in, so i guess the list was
> If we sort above, we will be in a better position to draw the line.
Open Source and Standards, Sysadmin
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the Gluster-infra