Cloud Deployment Manager

Features of Cloud Deployment Manager 

• You can make deployments that use a bunch of Google Cloud services in unison by writing template and configuration files and using them, for example:
  
  • Cloud Storage
     
  • Compute Engine
     
  • Cloud SQL
     
• A configuration specifies how your deployment will be organized. To create a deployment, you must define a configuration in a YAML file. It has the following in it:
  
  • Type and properties of the deployment-related resources.
     
  • Templates that the configuration file will use 
     
  • Additional executable subfiles that can be used to build your final configuration.
     
• The resources that you specified in a configuration are created when you build a deployment.
   
• It has some important features as well e.g., Declarative Language, focus on the application and Parallel Deployment.

Deployment Management Roles

Following are the four roles that are in Deployment Management:

• Deployment Manager Editor: It gives the permissions to create as well as manage the deployments.
   
• Deployment Manager Type Editor: It gives read as well as write access to all the Type Registry resources.
   
• Deployment Manager Type Viewer: It gives read-only access to all the Type Registry resources.
   
• Deployment Manager Viewer: It gives read-only access to all the Deployment Manager-related resources.

Configuration

All the resources you need for a single deployment are listed in a configuration. A configuration is a YAML-formatted file that contains a list of all the resources you want to build together with each resource's associated properties. 

The list of resources to create must be accompanied by a resources: section in a configuration.

Each resource must consist of three components. These are:

• name: It is a string created by the user to identify this resource, like project-data-disk, etc.
   
• type: It is the type of the resource that is being deployed, such as compute.v1.instance and compute.v1.disk.
   
• properties: These are the parameters for this resource type. They need to match the type's properties, such as zone: asia-east1-a and boot: true.

Templates

Templates can be present in configurations; they are simply configuration file components that have been abstracted into smaller building elements. When a template is created, you can use it again and again for different deployments as per your need.

Templates are designed to facilitate simple portability across deployments and are far more flexible than individual configuration files.

A template file is created using Jinja2 or Python. Each template will be interpreted recursively by the Deployment Manager system, and the outcomes will be inlined in the configuration file. 

As a result, each template is finally interpreted to produce resources that use the same YAML syntax as the configuration file itself.

Resource

A resource is an individual API resource. This might be either an API resource supplied by a base type managed by Google or an API resource provided by a Type Provider. 

For example, a Compute Engine instance can be seen as a single resource. Also, a Cloud SQL instance can also be seen as a single resource.

How to use a deployment manager in GCP?

Before we move on to the step, you need to log in to your account. If you don't have an account, you can easily create it on the Google Cloud Platform.

After login, you need to Create a Google Cloud Project and enable the Compute Engine APIs and Deployment Manager.

Then you can install Google Cloud CLI on your system and configure it to use your project.

After all, that, let us move to the steps of using the deployment manager:

• Defining your resources: In this step, you will describe your resources in a configuration file, which is written in the YAML syntax.
   
• Deploying your resources: In this step, you will deploy the resources, and to do that, you can use the Google Cloud CLI to create a new deployment using your configuration file: 
   

gcloud deployment-manager deployments create quickstart-deployment --config vm.yaml

 

• Checking in on your new deployment: After the deployment, you can check the status of the deployments. To do that, run the command that is below:
   

gcloud deployment-manager deployments describe quickstart-deployment

 

• Review your resources: After you have created the deployment, you can review your resources in the console. To do that, open the Deployment Manager page and check the information.
   
• Clean up: After all that, we need to wipe the plates clean to avoid charges to your Google Cloud account for the resources that you used; follow these steps:
   

gcloud deployment-manager deployments delete quickstart-deployment

 

The deployment, as well as the resources you created, have now been permanently deleted.

Using deployment-specific environment variables

Deployment Manager produces pre-defined environment variables for each of your deployments that each contain data deduced from your deployment. To know further about your project or deployment, use these environment variables in your Python or Jinja2 templates.

Environment variable	Value
deployment	This is the name of the deployment.
name	This is the name declared in the configuration which is using the template. It can be useful if you want the name you declare in the configuration to be the name of the resource in the underlying templates.
project	This is the project ID for this deployment.
project_number	This is the project number for this deployment.
current_time	This is the UTC timestamp when expansion started for the deployment.
type	This is the resource type declared in the top-level configuration.
username	This is the current Deployment Manager user.

Benefits of Deployment Manager

When it comes to providing resources to your GCP environment, Deployment Manager has a number of important advantages, including:

• By using a RESTful API or the command line, deploy your infrastructure using a template you've created.
   
• Templates accept Jinja or Python for deployments that require logic, enabling you to employ programming constructs like loops, conditionals, and parameterized inputs.
   
• The ability to review and remove deployments through the user interface has been added to Google Developers Console.
   
• Resources on the Google Cloud Platform are tightly interconnected, enabling faster deployment administration and visibility across computing, storage, and networking.
   
• The architecture of your deployments can now be seen thanks to Developers Console's UI support for Deployment Manager.

Frequently Asked Questions

What is Deployment Manager software?

The Software Deployment Manager (SDM) is a tool with which you can manage and deploy software packages (Software Deployment Archives and Software Component Archives) that you receive from SAP. Features. The SDM consists of SDM Server and SDM GUI.

What are the types of cloud deployment models?

Public, private, community, and hybrid are the four cloud deployment models. The location of the environment's infrastructure determines the specifics of each deployment model.

Which deployment model is best?

The most prominent deployment model is the public cloud. You don't own any hardware in a public cloud deployment model because the cloud service provider provides all of the resources.

Which cloud deployment model is most widespread?

The most widespread type of cloud service is the public cloud model. This category of cloud is a well-liked choice for online applications, file sharing, and storing non-sensitive data, and also, all of the equipment required to host a public cloud is owned and managed by the service provider.

What is AWS deployment?

AWS CodeDeploy is a service that automates the deployment of code to any instance, including instances hosted on-premises and in Amazon EC2.

Conclusion

In this article, we have studied about Cloud Deployment Manager in detail. We have also discussed configuration files, resources and templates.

We hope that this article has provided you with the help to enhance your knowledge regarding Cloud Deployment Manager and if you would like to learn more, check out our articles on cloud domains and cloud hypervisor.

Refer to our guided paths on Coding Ninjas Studio to learn more about DSA, Competitive Programming, JavaScript, System Design, etc. Enrol in our courses and refer to the mock test and problems available, Take a look at the interview experiences and interview bundle for placement preparations.

Do upvote our blog to help other ninjas grow.

Merry Learning!