Feature #4240
Clone support for OneFlow templates
| Status: | Closed | Start date: | 12/11/2015 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Daniel Molina | % Done: | 100% | |
| Category: | OneFlow | |||
| Target version: | Release 5.0 | |||
| Resolution: | fixed | Pull request: |
Description
With the possiblity of cloning of OneFlow templates you would be able to create a "golden-OneFlow-template" and just change some parameters for a specific service / customer / use case and speedup deployment.
Related issues
Associated revisions
feature #4240: Add Service Template clone dialog
feature #4240: Unlock Document after a clone action
feature #4240: Return service template info after clone action
feature #4240: Add service template clone to the CLI
History
#1
Updated by Ruben S. Montero over 5 years ago
- Tracker changed from Feature to Backlog
- Category set to OneFlow
- Priority changed from Normal to High
#2
Updated by EOLE Team over 5 years ago
+1
We will use flows to deploy virtual infrastructures per version of our linux distribution.
Creating a flow template take some time and the roles are fixed for us, we only need to change the VM template based on the version of our distribution.
So, we could create a reference template for roles, their relations (parents) and their cardinalities, then clone it with any new distribution version and change the VM template for the desired version.
Regards.
#3
Updated by Carlos MartÃn over 5 years ago
- Related to Feature #2123: Port features of templates and VMs to appflow added
#4
Updated by Daniel Molina over 5 years ago
- Tracker changed from Backlog to Feature
- Status changed from Pending to New
- Assignee set to Daniel Molina
- Target version set to Release 5.0
#5
Updated by Daniel Molina over 5 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Resolution set to fixed