> >We currently use our own custom puppet modules to deploy openstack, I >have been looking into the official openstack modules and have a few >barriers to switching. > >We are looking at doing this at a project at a time but the modules have >a lot of dependencies. Eg. they all depend on the keystone module and try >to do things in keystone suck as create users, service endpoints etc. > >This is a pain as I don¹t want it to mess with keystone (for one we don¹t >support setting endpoints via an API) but also we don¹t want to move to >the official keystone module at the same time. We have some custom >keystone stuff which means we¹ll may never move to the official keystone >puppet module. > >The neutron module pulls in the vswitch module but we don¹t use vswitch >and it doesn¹t seem to be a requirement of the module so maybe doesn¹t >need to be in metadata dependencies? > >It looks as if all the openstack puppet modules are designed to all be >used at once? Does anyone else have these kind of issues? It would be >great if eg. the neutron module would just manage neutron and not try and >do things in nova, keystone, mysql etc. > > >The other issue we have is that we have different services in openstack >running different versions. Currently we have Kilo, Juno and Icehouse >versions of different bits in the same cloud. It seems as if the puppet >modules are designed just to manage one openstack version? Is there any >thoughts on making it support different versions at the same time? Does >this work?
Hi, In my experience (I am setting up a new environment) the modules can be used ³stand-alone². It is the OpenStack module itself that comes with a combined server example. The separate modules (nova, glance, etc) are very configurable and don¹t necessarily need to setup e.g. keystone. >From the OpenStack module you can modify the profiles and it will not do the keystone stuff / database, etc.. E.g. Remove the ³:nova::keystone::auth² part in the nova profile. We use r10k to select which versions to install and it should be trivial to use Juno / Kilo stuff together (have not tested this myself). Regarding the vswich module I *guess* that that is regulated by the following: neutron/manifests/agents/ml2/ovs.pp: if $::neutron::params::ovs_agent_package So unsetting that variable should not pull the package. Cheers, Robert van Leeuwen _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
