Hi Puppeteers,
I am working with a team to manage a large, complex infra covering
several thousand VMs plus specialized hardware boxes in several data
centers. I have some backstory with Puppet (and isconf2, and
infrastructures.org) and I authored several tools in the
git-swiss-army-chainsaw.
Our current approach is to avoid master/server due to scalability
issues and not-always-reliable connectivity across locations.
So our (trivial) plan is
- setup a "gold" git server, where changes are published
- each datacenter has a "proxy" (git mirror, or similar) that pulls
from gold server
- each client pulls from their local proxy
In case of problems with the gold server or connectivity (outage,
DDoS), the "proxy" can be detached and updated independently.
However I am planning to do two things differently (from what I have
seen discussed):
- Starting to draft some scaffolding ("gp" for gitpuppet) to allow us to say
gp commit --deploy-at "05-01-2013 12:00:00" -m "Strangle the frog at
the strike of midnight"
Is there any existing tool that will provide scheduled rollouts?
Searching around I haven't found anything...
- Looking into whether I can feed data from the puppet client runs
back to the dashboard. My current plan is to push that data back the
same way -- store-and-forward style through the proxy to the gold
server, then to a machine running the dashboard.
Is anyone working on a similar track? Hints?
cheers,
m
--
martin.langh...@gmail.com
- ask interesting questions
- don't get distracted with shiny stuff - working code first
~ http://docs.moodle.org/en/User:Martin_Langhoff
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
