UML Deployment Scheme for IaaS and PaaS Cloud

I would like to simulate the following situation using the UML deployment diagram.

A small instance of the management and management machine is generated on the infrastructure platform as a cloud service, such as Amazon EC2 . This instance, in turn, is responsible for NumberCruncher.py additional instances and providing them with the NumberCruncher.py script NumberCruncher.py either through something like S3 or directly as a script launch parameter if the program is small enough to fit into this field. My attempt is to simulate a situation using UML deployment diagrams under the working assumption that a Node Machine instance is unsatisfactory for the following reasons.

  • The diagram seems to suggest that there will be exactly three numbers of cruncher nodes. Is it possible to illustrate the many nodes in the deployment diagram, as shown in the example of the multi-object instance. If this is not possible for nodes, this seems like a Long Standing Issue
  • In any case, show the equivalent of deployment regions / data centers in the deployment diagram ?

Finally:

How about a platform as a service? The whole Machine Instance is a Node idea that is completely collapsing at that moment. What are you doing in this case? Call the whole PaaS provider as a single node and forget about the details?

IaaS Nodes are Machine Instances

+7
source share
1 answer

Regarding your first question:

In any case, to show the equivalent of deployment areas / data centers in the deployment diagram?

I usually use Notes for this.

And your second question:

How about a platform as a service? The entire Machine instance is a Node idea that is completely destroyed at that moment. What are you doing in this case? Treat the entire PaaS provider as the only node and forget about the details?

I would say yes for your last answer. And I suppose you could take more detailed information from the definition of the deployment model and its elements. Specifically at the end of this paragraph:

They [Nodes] can be nested and can be connected in arbitrary complexity systems using communication paths. Typically, nodes represent either hardware devices or software runtimes .

and

ExecutionEnvironments are standard software systems that application components may require at runtime.

source: http://www.omg.org/spec/UML/2.5/Beta1/

+1
source

All Articles