Hi Matt & Richard, thank you very much for the suggestion. We are trying to achieve something like you describe - just that I didn't know how to ... describe what we want :).
Your sugestion is very, very interesting. So from where do you advice that we start from? I'm looking at https://launchpad.net/puppet-openstack and https://github.com/openstack?utf8=%E2%9C%93&query=puppet - Are those the right places? Thank you very much ...again, Cris On Mon, Jun 15, 2015 at 8:08 PM, Richard Raseley <[email protected]> wrote: > Cristina Aiftimiei wrote: > >> The puppetlabs-openstack clearly states: >> >> >> """""" >> >> >> Limitations >> >> * High availability and SSL-enabled endpoints are not provided by this >> module. >> >> """"""" >> > > As Matt touched on, you really should be building your own 'composition > layer' for deploying production services and their supporting components, > not consuming a pre-canned composition layer like 'puppetlabs-openstack', > which has value - but primarily as a demonstration and testing tool. > > In this model, each of the classes contained puppet-* module (e.g. > puppet-nova, puppet-keystone, et. al.) will be wrapped with your own custom > classes (likely in a role and profile pattern) in order to define those > relationships. > > Regards, > > Richard > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
