-
Epic
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
None
-
Combination of multiple components
-
To Do
as a designer,
i want to be able to create combinations of frequently used instances in a service and to store them as a combination.
the combination will allow facilitating service design.
the combination is a logical entity with now Tosca representation.
once the combination is used it becomes a seamless part of the service with no effect to the service Tosca representation.
open issues:
- How is the life cycle managed for the combination? how can i edit a combination or remove it? will it be versioned?
- Clearly define the life cycle of combination: create/use/delete/version, and the interactions/dependency between combination and service using it, the way it is stored.
- How does combination affects the model: the internal database storage and TOSCA model?
- How are name conflicts solved? each time you create an instance it has a name assigned to it including a numbering when I drag it to a service how is this addressed.
- How is the combination works in case of changes in the parts? will it stop being a combination?
- How the combination works after dragging it?
- Where are the combinations shown and where are they managed?
- if i update values of items in the combination will it be stored?
requirements:
provide a design on how will this be implemented.
1.
|
Artifacts and Other Components in a Combination | Closed | satyaki_huawei | |
2.
|
Unit Test for Combination related classes | Closed | satyaki_huawei |