It's not quite *static* content. I can see a lot of ways that this might be useful to users. For example, I host yum/apt/DMG repos (and maybe nuget too!) on my puppet masters, and as I scale puppet masters I will want to use shared storage for those - probably NFS. So being able to add the state of that NFS mount to my server status would be useful -- if the mount is unavailable, the load balancer should skip that master and I should get an alert via the monitoring system. But, I could do that with a crontask that just kills the puppetmaster if the mount is inaccessible. The effect would be the same, and probably just as quick.
Another use is to take a master out of service gracefully, manually. That's the original motivation for this ARM. However, it occurs to me that this is usually best done via the load balancer itself - it should have some UI for removing a node or nodes from the pool. The more we discuss this, as written, the less useful it sounds. Morphing it into a "make puppet monitorable as a rack app" seems like a *big* change. 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.
