Skip to content

gerardo-versa/vos-azure-single-branch

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Deploy a VOS Device as a Branch Using Terraform Templates

This section describes how to use Terraform templates to automatically deploy a Versa Operating SystemTM (VOSTM) device as a branch. You obtain the Terraform template files from Versa Networks Customer Support. To deploy a VOS device as a branch, ask for the Versa_FlexVNF_SingleBranch_Staging.zip file, which contains the Terraform templates for the branch deployment.

To deploy a VOS device as a branch using Terraform templates, follow Step 1 to Step 6 as described in Create VMs for Versa Headend Components.

The following table describes the contents of each Terraform template file and the actions performed by each file.

**Filename** **Description or Action**
vars.tf Definitions of all variables defined and used in the template. Do not make any changes to this file.
terraform.tfvars

User-defined input variables that are used to populate the Terraform templates. Edit this file to set or change the following variables:

  • subscription_id—Subscription identifier information for the Azure account.
  • client_id—Client identifier information obtained as part of setting up Terraform access.
  • client_secret—Client secret information obtained as part of setting up Terraform access.
  • tenant_id—Tenant identifier information obtained as part of Setting up Terraform access.
  • location—Enter the string that identifies the VOS device location. For example, west-us or west-europe.
  • resource_group—Name of the resource group in which to place the resources for the VOS device. The default is Versa_FlexVNF_RG.
  • ssh_key—SSH public key. This key is required to log in to the VOS instances. To generate the SSH key, use the sshkey-gen or putty key generator command. You cannot generate keys within Azure.
  • vm_name—Name of the VM that is displayed in the VM list of the Azure Portal. The default is Versa_FlexVNF.
  • flexvnf_vm_size—Instance type and size used to provision the FlexVNF-1 VM. The default is Standard_F4s.
  • local_authentication_id authentication at the branch used for staging.
  • local_authentication_id authentication to use for staging. This is Controller-side authentication key used during staging of the branch.
  • serial_num number of branch to be set. This must be the same as the serial number that is provided during the corresponding Workflow device deployment in Versa Director.
output.tf Output parameters, including management IP address, public IP address, WAN IP address, LAN IP address, and CLI commands, for all instances. Do not make any changes to this file.
flexvnf.sh Bash script that runs as part of cloud-init script on the VOS instance. Do not make any changes to this file.
main.tf
  • Provision one resource group, called Versa_FlexVNF_RG. To change the resource group name, edit the terraform.tfvars file.
  • Assign a public IP address on the management port of the VOS device instance.
  • Assign a static public IP address for the VOS device WAN port.
  • Provision a network security group, and add all the firewall rules required to set up the VOS device.
  • Install a VOS instance and run the cloud-init script to:
    • Update the /etc/network/interface file.
    • Add the SSH key for the admin user.
    • Add a cron job to trigger the staging.py script required for ZTP.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published