Allow generic linux install with no additional packages on a node (empty/blank role)

Registered by Gregory Elkinbard on 2014-04-04

Currently, it is not possible to easily extend a fuel deployment with field customization, you have to understand fuel code and be ready to hack it in the field. What if there was a blank role.
a linux node that fuel could install, whose personality can then be set by hand. Then this node can be turned into what ever additional service node that fuel does not support yet. for example elastic search node.

* by default Fuel allocates minimal disk size for OS
* plugin's post and pre deployment hooks should work for this role

Blueprint information

Status:
Complete
Approver:
Mike Scherbakov
Priority:
Essential
Drafter:
Gregory Elkinbard
Direction:
Approved
Assignee:
Evgeniy L
Definition:
Approved
Series goal:
Accepted for 6.1.x
Implementation:
Implemented
Milestone target:
milestone icon 6.1
Started by
Evgeniy L on 2015-01-13
Completed by
Evgeniy L on 2015-01-15

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/blank-role-node,n,z

Addressed by: https://review.openstack.org/147230
    Add new role "Operating System" role in Fuel

Addressed by: https://review.openstack.org/150456
    Added new test for base os deploy.Some fixes Change-Id: Iae041fbdfd3a2347fd6e88c871404d3bf805a3a9 Implements: blueprint blank-role-node

Addressed by: https://review.openstack.org/150856
    Add workaround for plugin developer to deploy custom role

Addressed by: https://review.openstack.org/156169
    Replace test for base-os node from fuel-main

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.