vRA Cloud + GCP: Using Security Groups
Let’s explore how you can apply existing Google Cloud Platform (GCP) network tags when deploying machines to a GCP environment with a vRA cloud template.
Demo Product Versions
- vRA Cloud
- GCP Environment
- Active GCP project
- Service account with appropriate roles for connectivity with vRA cloud
- Basic infrastructure configured for the GCP environment (Cloud Account, Project, Cloud Zone, Flavor Mapping, Image Mapping)
Note: If you need help setting up a GCP cloud account, you can use Gary Flynn’s blog as a resource.
- Using vRA template
- Using vRA network profile
Demos / Examples
Method 1: Using vRA Template
- Ensure that you have a network tag in the GCP environment that you’d like to use in a vRA template. The network tag must be in use by at least one firewall rule for it to be discovered by vRA during data collection.
Below is an example of a network tag applied to an existing instance in GCP.
Note that a GCP network tag is not a separate resource by itself. You can only create a GCP network tag when you’re creating an instance or if you’re adding a new network tag to an existing instance. For example, when you’re creating an instance, find the “Networking” section and you can create tags under “Network tags”.
- In vRA Cloud Assembly, go to “Resources” > “Security” and add a vRA tag to the GCP network tag you’d like to use in a vRA template.
If you’ve just made a new network tag in GCP, you might have to wait until another data collection has been done for that GCP environment. Data collection occurs every 10 minutes automatically. You can check when the last data collection has been done by viewing the cloud account details from “Infrastructure” > “Cloud Accounts” in vRA Cloud Assembly.
- In a vRA Cloud template in vRA Cloud Assembly, drag a Cloud Agnostic Security Group resource on the canvas and connect it to the machine you’d like to apply the GCP network tag. I only use one security group in this example but you can have multiple security groups attached to one machine.
constraints:, add the line
- tag: <insert tag name>.
- Make sure the value for
Creating on-demand security groups (or GCP network tags) is not supported with GCP. If you try to set the value for
newand deploy the template, it will fail and give the error like below.
- After you deploy the template and the deployment is finished, go to the GCP UI > “Compute Engine” > “VM instances” and click instance that has been created by the vRA deployment.
- Scroll down to “Network interfaces” section and click “View details”.
- Under “VM instance details” > “Network tags”, you should see that the network tag has been applied by the vRA template on this instance.
Method 1 YAML
Method 2: Using vRA Network Profile
- In vRA Cloud Assembly, go to “Infrastructure” then “Network Profiles”. Create a network profile or edit an existing one.
- Under “Security Groups”, add existing security group(s) that you want to use.
- In a vRA Cloud template in vRA Cloud Assembly, make sure that the machine(s) being deployed will use the network profile you’ve created. In this example, I have created a capability tag on the network profile and the machine is using that capability tag under
constraints. Note that you do not need a security group resource in the template.
- After you deploy the template, go to “Deployments"in vRA Cloud Assembly and click on the deployment that you’ve created. From there, under “Network” for the machine that has been deployed, you will see that the network tag has been applied.
- You can also verify that the network tag has been added to the instance deployed by the vRA template in the GCP UI.
At the time of this blogpost, vRA does not support reconfiguring or updating security group(s) of an existing deployment for public clouds. For example, if you change the security group in a vRA cloud template and try to update an existing deployment, it will fail with the error below.
Method 2 YAML