Open Stack

On Thu, Oct 29, 2015 at 07:14:00AM +0300, Ilya Shakhat wrote:
> Hi Paul,
> 
> Using existing dump makes the cold start much more pleasant. Full data
> reload usually needed only when some incompatible changes are introduced. I
> mark such commits with the warning note and bump release number. To help
> you with the initial setup I can grab the dump from production and share it
> with you. The raw size is about 2G, hope it compressible.
> 
Great. I'm sure if you jump into #openstack-infra we can find a
location to upload it too.

> This week I'm at the summit. If you are not, we can schedule a chat next
> week, e.g. on Thu would be ok.
> 
Yup, that works for me too. Again, I'll be idling in #openstack-infra when you
have free time.

> Thanks,
> Ilya
> 
> 2015-10-28 18:20 GMT+03:00 Paul Belanger <pabelanger at redhat.com>:
> 
> > Greetings Ilya,
> >
> > I was hoping you could help save me some time doing the initial import of
> > stackalytics.o.o by using a stackalytics-dump from your instance? If I
> > understand correctly, this is how you currently do backups / persistent
> > data
> > from memcached?
> >
> > Additionally, maybe we could setup some time next week to chat about how to
> > currently do maintenance on stackalytics.org, so I can include that
> > functionality
> > into puppet-stackalytics[1]. Things like how often you dump memcached
> > data, if
> > any existing scripts exists, current backup / restore procedures.
> >
> > PB
> >
> > [1] https://github.com/openstack-infra/puppet-stackalytics
> >