Describe virtual devops environments using templates instead of hardcoded generators with some external parameters
Currently, we make virtual devops environments for run system tests, where a small amount of parameters can be used for configure nodes and networks in the virtual environment. This approach is hard to scale and cannot be used for making detailed hardware/network configs for each node in the environment.
Template based approach allows to make unique configuration for each node, make non-standard network topologies without re-writing the #fuel-devops code for each particular case, add new roles for nodes to get environment with pre-installed operation systems or use some external image to get prepared software on some nodes.
Blueprint information
- Status:
- Not started
- Approver:
- Nastya Urlapova
- Priority:
- High
- Drafter:
- Dennis Dmitriev
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Review
- Series goal:
- Accepted for future
- Implementation:
-
Unknown
- Milestone target:
-
next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Describe virtual devops environments using YAML templates
Addressed by: https:/
Move to template-based configuration of devops environments
Gerrit topic: https:/
Addressed by: https:/
Flexible object schema for template-based virtual environments
Addressed by: https:/
Update usage documentation for v3.0.0
Addressed by: https:/
v3.0.0: Additional changes to helpers
Addressed by: https:/
ParamedModel - Parameterizable model class
Addressed by: https:/
New Libvirt Driver Model
Addressed by: https:/
New Network Models
Addressed by: https:/
Volume model changes
Addressed by: https:/
Node model changes
Addressed by: https:/
New LibvirtXMLBuilder
Addressed by: https:/
Group and Environment changes
Addressed by: https:/
shell.py changes
Addressed by: https:/
Migration for new model schema.
Addressed by: https:/
Update unit tests Update verion to 3.0.0
Addressed by: https:/
Update dummy_driver
Addressed by: https:/
Add ip_reserved and ip_ranges attributes to AddressPool
Addressed by: https:/
Template validation
Addressed by: https:/
Use physical host interfaces to connect virtual and baremetal networks
Addressed by: https:/
Validator for test configurations
Addressed by: https:/
Remove deprecated 'verbose' argument
Addressed by: https:/
Do not raise exceptions if object not found in Libvirt for erase
Addressed by: https:/
Add a new option 'bootmenu_timeout' for libvirt Node
Addressed by: https:/
Define and start networks and nodes separatelly
Addressed by: https:/
Generate 'network_config' in compatibility layer
Work Items
Dependency tree
* Blueprints in grey have been implemented.
