| 2014-04-07 08:17:08 |
Bogdan Dobrelya |
description |
Development documentation must contain a section about adding new role, and links to all implications.
Adding new role starts from modification of YAML file for role to appear in UI. Following questions should be addressed in documentation:
* Role weight to provide proper order of deployment
* How to configure Fuel to provide restrictions for this role (can it coexist with other roles, hardware limitations for role, if role added - what other UI elements are changed, etc.)
* What changes are required in Nailgun
* What if role requires special disk partition. Default disk allocation. Min/max size, collocation with other LVMs, etc.
* What networks are required for role: both L2 & L3.
* What data about other roles is required, such as endpoints, etc. Where it can be fetched, what are the standards here.
* Role deployment implementation. Existing approach with puppet modules - reference to puppet module development guide, alternatives to puppet. |
Development documentation must contain a section about adding new role or puppet module, and links to all implications.
Adding new role starts from modification of YAML file for role to appear in UI. Following questions should be addressed in documentation:
* Role weight to provide proper order of deployment
* How to configure Fuel to provide restrictions for this role (can it coexist with other roles, hardware limitations for role, if role added - what other UI elements are changed, etc.)
* What changes are required in Nailgun
* What if role requires special disk partition. Default disk allocation. Min/max size, collocation with other LVMs, etc.
* What networks are required for role: both L2 & L3.
* What data about other roles is required, such as endpoints, etc. Where it can be fetched, what are the standards here.
* Role deployment implementation. Existing approach with puppet modules - reference to puppet module development guide, alternatives to puppet. |
|
