Cristina Aiftimiei wrote:
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://l
I have to agree, every one's composition layer tends to come out
differently and your mileage will vary using some one elses.
You can examine the diverged fork of puppet-openstack that fuel uses at
https://github.com/stackforge/fuel-library/tree/master/deployment/puppet/openstack
which does ha, bu
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
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 producti
