[Gluster-infra] Backup strategy for our infrastructure?

[Michael Scherer]

Le mardi 19 août 2014 à 22:19 +0100, Justin Clift a écrit :
> On 13/08/2014, at 10:01 PM, Justin Clift wrote:
> <snip>
> > These pieces spring to mind immediately:
> > 
> > * Gluster Forge (repo data + all Gitorious config)
> > 
> >   Unless we're sure Gitorious AS is backing it up well enough.
> > 
> > * Gluster Wiki
> > 
> > * Jenkins (configuration, and all of the build artifacts)
> > 
> >   The user list + authentication for Jenkins is its hosts /etc/passwd
> >   file, so backing up the auth info for the local box will capture
> >   that ok.
> > 
> > * Gerrit
> > 
> > * Our Mailman mailing lists (config and data)
> 
> 
> * The www.gluster.org apache and varnish configuration
> 
> * The download.gluster.org website (no idea which) configuration

IMNSHO, configuration should not need to be backed up by using a
configuration management system. But that's only if we decide to use
one.
-- 
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/20140819/898de1a2/attachment.sig>