Cobbler node define shouldn't be in site.pp

Bug #1159602 reported by Michael Chapman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
Fix Released
Wishlist
Michael Chapman
Folsom
Fix Committed
Wishlist
Michael Chapman
Grizzly
Fix Released
High
Chris Ricker

Bug Description

Move cobbler node definition out of site.pp and into cobbler_node.pp and add extra parameters for clients to override.

Revision history for this message
Michael Chapman (michaeltchapman) wrote :
Revision history for this message
Ian Wells (ijw-ubuntu) wrote :

Yes, but this still doesn't work if I have a completely different node (i.e. it's not a UCS), or two sorts of hardware mixed together, or nodes with different admin passwords...

For a good chunk of people installing, cobbler_node is completely fine and putting it in front of them is presenting them with complexity they don't need to see. For another chunk of people, cobbler_node is something that needs customising, which is why I put it in site.pp in the first place.

It's basically a judgement call. Someone make a judgement.

Revision history for this message
Chris Ricker (chris-ricker) wrote :

everyone will have to define their power management so I'd say it should stay in site.pp

Revision history for this message
Michael Chapman (michaeltchapman) wrote :

You can still define your power management:

cobbler_node { "control-server": node_type => "control", mac => "00:11:22:33:44:55", ip => "192.168.242.10", power_address => "192.168.242.110", power_user => "administrator", power_password => "super_secure_password" }

I should add another argument for the management type, though.

Revision history for this message
Chris Ricker (chris-ricker) wrote :

right, it's the type stuff I was referring to -- particularly since I'd expect most of our customers change that to ucsm

Revision history for this message
Michael Chapman (michaeltchapman) wrote :

New PR is here: https://github.com/CiscoSystems/folsom-manifests/pull/52

I've added the power_type argument and split it off from the other changes.

My motivation is twofold:
1- that site.pp should only contain site config and node definitions. The cobbler_node define is similar to every other define we use, and they are all put in either core.pp or cobbler_node.pp. I don't think it's any different.
2- If a customer is deploying to heterogeneous hardware they have to make multiple defines under the current scheme. This can be avoided by adding all the needed parameters to the define.

An alternative is to keep the parameters, but set them to default to a global variable in site.pp. This would make the node definition smaller but add three more global variables, while maintaining the ability to have different power options for each node.

Revision history for this message
Chris Ricker (chris-ricker) wrote :
Revision history for this message
Chip (cbaesema) wrote :

Merged to grizzly branch

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.