[Piuparts-devel] Thoughts on piattiNG

[Dave Steele]

>From the recent DSA missive:

     DSA's intention is to leverage these data centres
     for the bulk of our core infrastructure, primarily by
     deploying a standardized virtual machine hosting
     infrastructure and migrating the majority of Debian's
     core services onto virtual machines.

Some questions:

When do you expect the transition to happen for piuparts? How firm is
the schedule?

Is there a standard/preferred provisioning mechanism for defining the
VMs (i.e. puppet, chef), or is it to be hand-rolled? Is there any prep
work that needs to be considered for this?

Do you see separate VM slave instances in the short term, or is that a
farther out thing?

What is the recovery strategy, should the master logs be lost?
1) No strategy. Start up another instance. It will catch up in a
couple of months.
2) Resources can be lined up to release a horde of slaves to catch up,
in about a week.
3) Implement a log/config backup process on a slave or other VM.
Recovery in hours.

How much concern is there about configuration concurrency across
master and slave VMs? What is the preferred strategy for keeping them
in sync? Are provisions needed to be able to isolate the output of a
rogue slave (I am Spartacus!)?

     On several debian.org machines, services are currently located
     in the /org directory. With the release of 'wheezy', DSA will no
     longer support this directory and also begin removing existing
     symlinks from /org to /srv. Please check which directory your
     service is currently using and update your
     scripts/configuration where neccesary.

Do you expect to move to /srv, or use stock locations?