Modeling choices or defects?

[philippemerle]

I used our tosca toolbox to automatically generate visual diagrams in order to study modeling choices and identify modeling defects in TOSCA types and topologies of all xOpera examples.

Following is a UML2 component diagram representing the TOSCA topology of the cloud/aws/thumbnail-generator-with-vm example:

Following is a proprietary diagram representing the same topology (only node templates are represented):

On both diagrams, we could observe that:

• some node templates (bucket_notification, ec2_docker, ec2_web_app, bucket_out, bucket_in, prerequisites) have no business specific capabilities, except for the standard feature capability.
• some node templates (lambda, lambda_role, ec2_keypair, vpc_subnet, ec2_role) have only one business specific capability, except for the standard feature capability. But these business capabilities are the target of no relationship.
• No business specific relationship templates are present in this example, except for both standard DependsOn and HostedOn relationships.

Are those modeling choices or modeling defects?

[anzoman]

@philippemerle we developed this example to showcase the xOpera deployment on AWS and it seems that we focused more on the Ansible playbook executors within TOSCA interface operations. So, we tried to create a valid TOSCA structure, but if you see that there are some possible improvements or fixes for those modeling defects, you can express them here (also feel free to correct them yourself).

[philippemerle]

I will propose you (asap) some improvements fixing those modeling defects.
Moreover these improvements should be reuseable for all other cloud examples.

[philippemerle]

I see another different modeling defect in two other examples.

Following is a UML2 component diagram representing the tosca/policy-triggers/service.yaml topology:

This diagram shows that the AutoScale policy targets the openstack_vm node template.
But we also see that both ScaleDown and ScaleUp policies target no node template.
This should be a modeling defect: ScaleDown and ScaleUp policies should target openstack_vm too.

Following is a UML2 component diagram representing the misc/scaling/service.yaml topology:

Here we see that both ScaleDown and ScaleUp policies target no node template.
They both should target some node templates.

[anzoman]

Aha, yes @philippemerle thanks for finding another modeling defect.

[philippemerle]

@anzoman could this issue reopened as most of modeling defects were not fixed?

[anzoman]

Sure, let's reopen this.