A while back I stumbled on http://projects.puppetlabs.com/projects/puppet/wiki/CatalogServiceArchitecture. What''s the status of the Catalog Service Architecture? I couldn''t find references to it on this list I ask because I''ve been working on part of the Aeolus Project (www.aeolusproject.org) for post launch bootstrapping called Audrey (https://github.com/aeolusproject/audrey). Part of the functionality provided by Audrey''s configuration server is to coordinate configuration parameters between various launching guests in a cloud provider. We''re looking to more closely integrate with established configuration engines (such as puppet). If there is work underway on the Catalog Service Architecture, it would be nice to see how we could tie in our concept of sharing configuration parameters. At the moment, our idea of integrating with configuration engines is a very loosely defined idea. So, there''s a decent amount of room for interpretation. I understand that storeconfigs is the current mechanism for sharing configuration values between puppet-configured systems. But, that those configuration values are not collected in a central location for reporting, etc... Any information that can be provided about the Catalog Service, the status, how it''s going to work, etc., is much appreciated! (Also, if this should actually be posted to puppet-developers, please let me know) Thanks! --- Greg -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Jan 31, 2012 at 10:53 AM, blomquisg <blomquisg@gmail.com> wrote:> A while back I stumbled on > http://projects.puppetlabs.com/projects/puppet/wiki/CatalogServiceArchitecture > . > > What''s the status of the Catalog Service Architecture? I couldn''t > find references to it on this list >It''s rather out of date, and we''re going to update/delete that doc to make it clear.> > I ask because I''ve been working on part of the Aeolus Project > (www.aeolusproject.org) for post launch bootstrapping called Audrey > (https://github.com/aeolusproject/audrey). Part of the functionality > provided by Audrey''s configuration server is to coordinate > configuration parameters between various launching guests in a cloud > provider. > > We''re looking to more closely integrate with established configuration > engines (such as puppet). If there is work underway on the Catalog > Service Architecture, it would be nice to see how we could tie in our > concept of sharing configuration parameters. At the moment, our idea > of integrating with configuration engines is a very loosely defined > idea. So, there''s a decent amount of room for interpretation. > > I understand that storeconfigs is the current mechanism for sharing > configuration values between puppet-configured systems. But, that > those configuration values are not collected in a central location for > reporting, etc... > > Any information that can be provided about the Catalog Service, the > status, how it''s going to work, etc., is much appreciated! > > (Also, if this should actually be posted to puppet-developers, please > let me know) >This is fine :) Greg, I''m going to set up some off-list chats with you, not out of any sense of secrecy, but to get some higher-bandwidth discussion going that I''ll be happy to talk back to the list on.> > Thanks! > > --- > Greg > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- Nigel Kersten Product Manager, Puppet Labs -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Feb 1, 2012 at 17:01, Nigel Kersten <nigel@puppetlabs.com> wrote:> On Tue, Jan 31, 2012 at 10:53 AM, blomquisg <blomquisg@gmail.com> wrote: >> >> A while back I stumbled on >> http://projects.puppetlabs.com/projects/puppet/wiki/CatalogServiceArchitecture. >> >> What''s the status of the Catalog Service Architecture? I couldn''t >> find references to it on this list > > It''s rather out of date, and we''re going to update/delete that doc to make > it clear.I had a look over it, and while it lives on in the history of the wiki, it is far enough from current thoughts that removing it was the better option. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.