Unless something's changed, the Puppetca only needs to be available for certificate *management*. if it were down, you couldn't create a certificate for a new node or revoke for an old one. And I'm pretty sure the CRL has to be actively distributed to Puppetmasters. (Meaning, if you revoke a certificate on the CA you have to copy the crl.pem to all your Puppetmasters yourself.)
Puppet should still work. On Wed, Aug 3, 2011 at 11:28 AM, Jared Curtis <ja...@shift-e.info> wrote: > Having the CA down would be a problem, dashboard can be unavailable > temporarily. I plan to overcome the CA issue by creating a hot standby > CA. > > On Aug 1, 5:57 pm, vagn scott <vagnsc...@gmail.com> wrote: > > On 08/01/2011 05:04 PM, Jared Curtis wrote: > > > > > * Central Dashboard instance > > > * Central CA > > > > Would it be a problem if your central > > CA and dashboard became unavailable? > > > > -v > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
