[英]UML Deployment Diagram for IaaS and PaaS Cloud Systems
I would like to model the following situation using a UML deployment diagram. 我想使用UML部署图为以下情况建模。
A small command and control machine instance is spawned on an Infrastructure as a Service cloud platform such as Amazon EC2 . 在诸如Amazon EC2之类的基础架构即服务云平台上产生了一个小的命令和控制机器实例。 This instance is in turn responsible for spawning additional instances and providing them with a control script NumberCruncher.py
either via something like S3 or directly as a start up script parameter if the program is small enough to fit into that field. 反过来,此实例负责产生其他实例,并通过诸如S3之类的东西为它们提供控制脚本NumberCruncher.py
或者如果程序足够小以适合该字段,则直接将它们作为启动脚本参数。 My attempt to model the situation using UML deployment diagrams under the working assumption that a Machine Instance is a Node is unsatisfying for the following reasons. 由于以下原因,在基于计算机实例是节点的工作假设下,我尝试使用UML部署图对情况进行建模无法令人满意。
Lastly: 最后:
What about Platform as a Service? 平台即服务又如何呢? The whole Machine Instance is a Node idea completely breaks down at that point. 整个Machine Instance是一个Node想法,到那时就完全崩溃了。 What on earth do you do in that case? 在这种情况下,您会做什么? Treat the entire PaaS provider as a single node and forget about the details? 将整个PaaS提供程序视为一个节点,而忘记细节了吗?
Regarding your first question: 关于第一个问题:
Is there anyway to show the equivalent of deployment regions / data-centres in the deployment diagram? 无论如何,在部署图中是否显示等效的部署区域/数据中心?
I generally use Notes for that. 我通常使用Notes。
And your second question: 还有第二个问题:
What about Platform as a Service? 平台即服务又如何呢? The whole Machine Instance is a Node idea completely breaks down at that point. 整个Machine Instance是一个Node想法,到那时就完全崩溃了。 What on earth do you do in that case? 在这种情况下,您会做什么? Treat the entire PaaS provider as a single node and forget about the details? 将整个PaaS提供程序视为一个节点,而忘记细节了吗?
I would say, yes for your last question. 我会说,对你的最后一个问题。 And I suppose you could take more details from the definition of the deployment model and its elements. 我想您可以从部署模型及其元素的定义中获得更多细节。 Specially at the end of this paragraph: 特别是在本段末:
They [Nodes] can be nested and can be connected into systems of arbitrary complexity using communication paths. 它们[节点]可以嵌套,并且可以使用通信路径连接到任意复杂的系统中。 Typically, Nodes represent either hardware devices or software execution environments . 通常,节点代表硬件设备或软件执行环境 。
and 和
ExecutionEnvironments represent standard software systems that application components may require at execution time. ExecutionEnvironments表示应用程序组件在执行时可能需要的标准软件系统。
source: http://www.omg.org/spec/UML/2.5/Beta1/ 来源: http : //www.omg.org/spec/UML/2.5/Beta1/
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.