Heat Templates for Service Chaining and Service Scaling
The heat template environment file defines the parameters specific to the VM-Series firewall instance deployed through service chaining or service scaling. The parameters defined in the environment file are divided into sections described below. There are two versions of the heat templates for service chaining—vwire and L3— and one for service scaling.
Service chaining requires the heat template files and two bootstrap files to launch the VM-Series firewall service instance and two Linux servers in the left and right networks.
- Template files—This template defines the resources created to support the VM-Series firewall and two Linux servers, such as interfaces and IP addresses.
- service_chaining_template_vm.yaml for vwire deployments.
- service_chaining_template_L3.yaml for L3 deployments.
- service_scaling_template.yaml for service scaling deployments.
- Environment file—This environment file defines the environment that the VM-Series firewall and Linux servers exist in. Many parameters in the template reference the parameters defined in this file, such as flavor for the VM-Series and the names of the Linux servers.
- service_chaining_env_vm.yaml for vwire deployments.
- service_chaining_env_L3.yaml for L3 deployments.
- service_scaling_env.yaml for service scaling deployments.
- service_instance.yaml—(Service Scaling only) This is a nested heat template that is reference by Service_Scaling_template.yaml to deploy the service instance. It provides the necessary information to deploy service instances for scaling events.
- init-cfg.txt—Provides the minimum information required to bootstrap a VM-Series firewall. The init-cfg.txt provided only includes the operational command to enable DHCP on the firewall management interface.
- <file_name>_bootstrap.xml—Provides basic configuration for the VM-Series firewall. The bootstrap.xml file configures the data interfaces. These values must match the corresponding values in the heat templates files.
For more information about the init-cfg.txt and bootstrap.xml files, see Bootstrap Configuration Files.
The following tables describe the parameters of the environment file.
VM-Series Firewall for OpenStack
VM-Series Deployments in OpenStack The Heat Orchestration templates provided by Palo Alto Networks allow you to deploy the VM-Series firewall individually, through service chaining, or ...
Set Up the VM-Series Firewall on OpenStack
Set Up the VM-Series Firewall on OpenStack The VM-Series firewall for OpenStack allows you to deploy the VM-Series firewall in your OpenStack environment to provide ...
Service Chaining and Service Scaling
Service Chaining and Service Scaling Service chaining is a Contrail feature that deploys a VM-Series firewall as a service instance in your OpenStack environment. A ...
Components of the VM-Series for OpenStack Solution
Components of the VM-Series for OpenStack Solution The VM-Series firewall in an OpenStack environment has been tested with the following components. Component Description Software Hypervisor: ...
Alarm The alarm parameters are used in service scaling and are not included in the service chaining environment files. These parameters define the thresholds used ...
Install the VM-Series Firewall with ServiceChaining or Scaling
Install the VM-Series Firewall with Service Chaining or Scaling Complete the following steps to prepare the heat templates, bootstrap files, and software images needed to ...
Service Instance The service instance portion of the heat template environment file provides the name of the individual instance deployed by the heat template and ...
Heat Template for a Basic GatewayDeployment
Heat Template for a Basic Gateway Deployment The heat template file includes the following four files to help you launch the VM-Series firewall on KVM ...
Virtual Machine The virtual machine parameters define the left and right Linux servers. The name of the port tuple is defined here and referenced by ...