On Nov 28, 2009, at 1:57 PM, Brice Figureau wrote: >> This basically says that multiple masters is really complicated and >> you shouldn't do it, which is not where we want to end up. >> >> IMO, the right approach is to have a node manager capable of >> functioning as an inventory server (holdiing all fact/node data), and >> then have the servers query that (with the same kind of caching >> they're doing now). >> >> This gets you essentially everything you need, and all it says is: >> If >> you want multimaster, you have to have an inventorying node manager. > > But people running multi master mainly do this for failure resistance, > and we're just adding a single point of failure... Don't you think > this > is a problem?
Yeah, it is, I guess. My plan was always to punt with "scale it like you would any rails app", but i know that's a cop-out. You're right that, in the end, the structure of the interactions shouldn't require that separate system. -- There are three kinds of death in this world. There's heart death, there's brain death, and there's being off the network. -- Guy Almes --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
