I thought I'd kick off discussion of this ARM, https://github.com/puppetlabs/armatures/pull/60/files (I started discussion in the pull req, but this is probably a better place for it)
First, the summary is about the implementation - it should probably start with the goal: "load balancers should be able to poll masters for their status, to support removal of malfunctioning masters from the pool" or the like. The summary's the first (and sometimes only) place people will look, so you have to hook them in early. Then you can go on to discuss implementation. Let me know if I've mischaracterized the intent. Second, as someone who had never heard of the status indirection, the description is confusing as to what exists and what doesn't. It might be nice to split that up into "current functionality" and "proposed functionality". Perhaps include an example of both -- for me: dmitchell@releng-puppet2 ~ $ curl -k https://puppet:8140/production/status/no_key Forbidden request: releng-puppet2.srv.releng.scl3.mozilla.com(10.26.48.50) access to /status/no_key [find] at :115 I think you're also suggesting additional keys beyond `is_alive`. Again, an example might make that clearer. Finally, on a technical basis, I'm not clear on how command-line switches would translate into changes of state for a running master. Is that through another operation on the REST endpoint? I think this sounds like a great idea. Will you be able to implement it, once the ARM is ironed out? Dustin -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
