Sascha Vogt wrote:
>
> At this point the provisioning on server 1 should pause, until server 2
> and 3 are provisioned and after that server 1 should complete the setup
> (basically "activating" server 2 and 3).
That feels a little clumsy, for most environments where you need to
activate or enable a server in a registry, (eg signing puppet keys or
salt keys from a minion), it's either an explicit step, or the
siging/activating process has a development mode that is insecure, i.e.
it signs/activates anything that comes in - is ther such an option for
your activate process?
Could you fake one by leaving a shell script running that activates any
incoming registrations?
> Is there any Vagrant or Puppet magic I'm missing which could be used for
> something like that, or would I need to setup server 2 and server 3 as
> Puppet slaves and server 1 as Puppet master and do not use the Vagrant
> built-in provisioning for server 2 and 3?
Not that I know of - you can't block a puppet run at a certain point
(well, you can with an exec with crazy sleep, but then you never get as
far as provisioning your 2nd & 3rd boxes)
Would "vagrant up" followed by a "vagrant provision server1" help - so
that server1 gets a second go at completing?
Simon.
--
Simon McCartney
si...@mccartney.ie
+44 7710 836 915