Abstract

Now that you've graduated from 101 and have some basic idea on CloudStack, let's take a look at what makes CloudStack flexible: adapters and plugins.  In 101, we've talked about CloudStack needs to interface with a wide variety of physical and virtual resources.  This is implemented by two different class of objects.  The first class is ServerResource, a translation layer that has no access to the database.  The second type is Adapters or now commonly (or maybe confusingly) known as Plugins, business logic inserted into CloudStack to change its behavior.  In 201, we will go deeper into these two types of objects and their relationship with CloudStack Orchestration.

CloudStack Orchestration

CloudStack presents a cloud abstraction layer that contains familiar concepts such as Virtual Machine, Nic, Network, Volume, Snapshot, Templates, IP Addresses, and different network rules.  CloudStack orchestration is the process through which this cloud abstraction layer materializes on the physical elements.  

is the CloudStack is built on the idea that cloud orchestration and the actual implementation of each orchestration step must be separate.  CloudStack achieves this by declaring adapter interfaces and pushing the implementation into adapters.

  • No labels