Drootoo has a centralized Cloud Resource provisioning section. All create and launch/deploy operations are performed from this section. Once a resource is deployed to a cloud provider, the details regarding their state and other operations including how to access them is available from specific resource sections like Storage, Network, etc.
Top level organization element for cloud resources is a Blueprint. It is used to group together resources required for a particular employee/ job function/ task/ project/ company division or the usual collection of cloud computing resources that have to work together.
A Blueprint is the basic unit which can be deployed from Drootoo to a cloud service. A collection of cloud resources like Compute Instances, VMs, Network, Storage, etc. across vendors like Amazon Web Services (AWS) / Azure/ etc. can be organized together in a blueprint, previously called a Resource Template.
Each Resource Template needs to have a name, version and at least one resource added. Description is optional.
These cloud resources can be distributed over the various available geographic regions and cloud services. Deploying them together is one of the main reasons for keeping them together in a Resource Template.
For example, a multi-location business could create a Resource Template that sets up everything needed for a branch office to function. Once that is deployed via the Launch button, the users in the branch office can access those cloud resources.
The Cloud Resources page lists all the Resource Templates that have been created by users having permissions to do so. Actions available for each Resource Template are listed next to them. A list of Resource Templates are shown along with their Name, Description, Version and Actions that can be performed on them like Edit, Delete, etc. Clicking the available action will show the Resource Template definition.
New Resource Template button is used to get started. Invoking the New Resource Template option gives a blank Resource Template to work with.
Please note that a Resource Template needs to have at least one Resource added before it can be saved. Duplicate names are allowed. Version info is available along with Description to differentiate between different templates.
Launch option deploys the Resources included in the template to the selected cloud providers. Resource Template List gets the user back to the listing of templates created by or made available to the user.
Launch at Lightning Speed
A well planned list of Resource Templates can reduce deployment time to hours and minutes, from days and weeks.
For example, we can create a Resource Template containing all cloud resources like Instance, Network and Storage for a Sales employee of a Retail brand. This can be deployed each time a new branch or outlet of the brand is to be opened. The Sales employee is given an IP address to access from any device preferred by the organization.
It beats creating the resources one at a time or writing scripts to deploy it in numbers, or the alarming possibility of that IT infrastructure (servers, applications and networking) having to be deployed locally in that new location.
Navigate back to – Help Topics