I can't seem to find a sane way of running storeconfigs on the new AWS
server environment I'm working on.
- SQLite is not an option. It becomes unusable far too quickly.
- Using a mysql adapter doesn't seem to work properly.
- I quickly run into bug
#9290<http://projects.puppetlabs.com/issues/9290>again and again. Which after 2
years STILL hasn't been fixed.
- The top of
this<http://projects.puppetlabs.com/projects/1/wiki/using_stored_configuration>seems
to imply that these ActiveRecord storeconfigs adapters are being
deprecated.
- The recommendation seems to be to use PuppetDB however from the looks
of it, I can't even use PuppetDB.
- I'm not going to use the embedded DB and fall right back into the
trap with SQLite again.
- PuppetDB only appears to support PostgreSQL and does not support
MySQL.
- I already have a MySQL database in AWS' RDS I would like to use.
And RDS does not support PostgreSQL.
- And I am NOT going to go right back to going and installing a
separate database server on the local node. That kind of thing has given
me
problem after problem.
Please tell me I'm missing something and there's a way I can get this to
work in this AWS environment. Cause otherwise the idea of puppet running
any type of server at all – rather than simply working as a local
filesystem `puppet apply` – looks so unreliable (as I've also had some
issues with the puppetmaster) that I should just dump every bit of
server/client software puppetlabs has and write my own custom way of
distributing configs and data.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" 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-users.
For more options, visit https://groups.google.com/groups/opt_out.
