Skip to content
This repository has been archived by the owner on May 14, 2019. It is now read-only.

Remove setup classes #182

Merged

Conversation

cmurphy
Copy link
Contributor

@cmurphy cmurphy commented Apr 24, 2015

Depends on #179.

The goal here is to enhance configurability while reducing code complexity. The user
should now be able to create as many images or networking resources as they want,
instead of having them hard coded. We still provide the original values as examples
in hiera, but default to creating nothing.

This is backwards incompatible as it will no longer create these resources by default.

Having a class that sets up a single hard-coded image is not very
useful, except for demos. This change moves the image data into the
example hiera files and uses create_resources on a hash of data to
create as many images as the user wants. We move this into
openstack::profile::glance::api since now a one-line function does not
need its own class.
The openstack::setup::router and openstack::setup::sharednetwork
classes only create two networks and one router with very little
configuration options. This change moves the network data into the
example hiera files and uses create_resources on a hash to create as
many networks, subnets, and routers are the user wants. We move this
into openstack::profile::neutron::router since these resources will
always reside on the network node.
underscorgan pushed a commit that referenced this pull request Apr 24, 2015
@underscorgan underscorgan merged commit 4c6607e into puppetlabs-toy-chest:master Apr 24, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants