On Tue, Mar 12, 2013 at 2:26 AM, Erik Dalén <[email protected]> wrote: > Couldn't the synced filebucket issue with the static compiled be solved by > using some sort of shared storage for it? >
That would solve one aspect, namely an efficient distribution/storage mechanism, which I've intentionally left out of the bundle ARM. Really what I was trying to get at with this was having a way of a complete artifact that can be independently created, versioned, distributed, signed, encrypted, and so on. A side effect of doing this is to solve the same problem that the static compiler was solving, which was to reduce the number of network calls. An advantage that I see in the bundle idea is the ability to completely decouple applying a catalog from producing a catalog, both in time and in access. A catalog bundle would not need access to any central servers, the static compiler requires access to a shared file server. A catalog bundle would not need to make assumptions about what plugins to use, they are packaged with the catalog. A catalog bundle can be archived away and still be understandable by itself later on, the static compiler would require a filebucket infrastructure to be usable later. > I've been thinking a bit about implementing a cassandra backend for that here > at spotify as we use cassandra a lot already. Once you have that in place I'm > not sure catalog bundles would bring enough benefits to warrant the extra > bandwidth they would require. But that depends on the catalog contents of > course. The bundles would need a lot more bandwidth if the distribution of them was done with a copy of the entire bundle each time, but I can also see them being distributed with rsync or checked into a git repo and pulled down onto the node. > > Another simpler option would of course be to load balance using srv records > and use the same host for every connection during the agent run. > > But so far other bugs like https://projects.puppetlabs.com/issues/17183 have > stopped us from using the static compiler. > I'm not sure if my POC falls prey to that bug or not. I'll have to keep it in mind. > -- > Erik Dalén > > > On Monday 11 March 2013 at 23:10, Andy Parker wrote: > >> I've been putting together some thoughts on a different way of >> distributing catalogs and files. This is similar to the static >> compiler that has been floating around inside puppet for a while, but >> I think this proposal opens up a lot more possibilities around making >> things asynchronous and distribution of the data. >> >> The proposal hasn't been merged into the puppetlabs/armatures repo >> yet, and my POC branch isn't in a working state at the moment. You can >> find what I've got so far at: >> https://github.com/zaphod42/armatures/blob/master/arm-draft.catalog_bundles/index.md >> >> Andy >> >> -- >> 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] >> (mailto:[email protected]). >> To post to this group, send email to [email protected] >> (mailto:[email protected]). >> Visit this group at http://groups.google.com/group/puppet-dev?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > 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?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
