Help me name a class in the new puppetdb module!

[Chris Price]

Anyone interested in helping me name a class in the forthcoming puppetdb module?

There are 2 major parts to the module... the part that sets up puppetdb itself, and the part that sets up the puppet master to talk to puppetdb.  I'm brainstorming names for the latter... a class that you would apply on your puppet master machine to tell it how to find and use puppetdb.

Any suggestions?

[Ashley Penney]

I kind of feel like the reason you're having a problem naming this is
that it doesn't really belong in the puppetdb class but in the puppet
module that sets up the server. :)

That's how I did this, I have a puppetdb module that purely sets up
puppetdb and then puppet::server::puppetdb to handle that other stuff.
Failing that I guess I nominate the name puppetdb::puppetmaster
despite the ugliness!

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

[Stefan Goethals]

Why not simply puppetdb::server for the ... well, puppetdb server and puppetdb::client for... the client, as that is exactly what the puppetmaster is to puppetdb?

Regards,

Stefan.

[Chris Price]

That's a fair statement; it's been brought up around the office.  The goal for now is to have a single puppetdb module that is capable of managing everything related to puppetdb, and then potentially later wrap some subset of the puppetdb classes in the puppet/master module.  For the short term, I'm just trying to name the class inside of the puppetdb module.

Thanks for the suggestion!

[Chris Price]

Not a bad idea, thanks for the suggestion!