APPLICATION COMPONENT DEPLOYMENT SEQUENCES
FIG2 is a block diagram of an example of a memory resource for generating deployment sequences consistent with the disclosure
FIG2 is a block diagram of an example of a memory resource 220 for generating deployment sequences consistent with the disclosure. In some examples, the memory resource 220 can be utilized to store instructions 224, 226 that can be executed by a processing resource to perform functions described herein. In some examples, the processing resource can be coupled to the memory resource 220 via a connection. A processing resource may be a central processing unit (CPU), microprocessor, and/or other hardware device suitable for retrieval and execution of instructions stored in memory resource 220. Memory resource 320 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions 338, 340, 342, 344. In some examples, the memory resource 320 can be the same or similar as memory resource 220 as referenced in FIG2.
block diagram
220
memory resource
224
instructions
['1. A non-transitory machine-readable storage medium having stored thereon machine-readable instructions to cause a computer processor to: determine dependencies between a plurality of application components of an application solution to be deployed on a plurality of hardware components of a computing system; and generate a deployment sequence for the plurality of application components based on the determined dependencies between the plurality of application components, wherein the deployment sequence includes a portion of the plurality of applications to be deployed on each of the plurality of hardware components and a sequence to deploy the portion of the plurality of application components based on the determined dependencies.', '7. A system comprising: a processing resource; and a memory resource storing machine readable instructions to cause the processing resource to: identify application components of an application solution to be applied to a hardware component of a hardware topology; determine dependencies between the identified application components to be applied to the hardware component; determine an order of deployment based on the determined dependencies between the identified application components; and deploy the identified application components on the hardware component based on the determined order of deployment.']