The alarm parameters are used in service scaling and are not included in the service chaining environment files. These parameters define the thresholds used by Contrail to determine when scaling should take place. This set of parameters is only used the service scaling heat template.
The default time configured under the cooldown parameters is intended to allow the firewall enough time to boot up. If you change the cooldown values, leave sufficient time for each new firewall instance to boot up.
|meter_name||The metric monitored by Ceilometer and used by contrail to determine when an additional VM-Series firewall should be deployed or brought down. The heat template uses CPU utilization or bytes per second as metrics for service scaling.|
|cooldown_initial||The amount time Contrail waits before launching a additional service instance after the initial service instance is launched. The default is 1200 seconds.|
|cooldown_scaleup||The amount of time Contrail waits between launching additional service instance after the first scale up service instance launch. The default is 1200 seconds.|
|cooldown_scaledown||The amount of time Contrail waits between shutting down additional service instances after the first scale up service instance shut down. The default is 1200 seconds.|
|period_high||The interval during which the average CPU load is calculated as high before triggering an alarm. The default value is 300 seconds.|
|period_low||The interval during which the average CPU load is calculated as low before triggering an alarm. The default value is 300 seconds.|
|threshold_high||The value of CPU utilization in percentage or bytes per second that Contrail references before launching a scale up event. The default is 40% CPU utilization or 2800 bytes per second.|
|threshold_low||The value of CPU utilization in percentage or bytes per second that Contrail references before launching a scale down event. The default is 20% CPU utilization or 12000 bytes per second.|
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 ...
Customize the Firewall Template Before Launch (v2.0 and v2.1)
Lists the settings you can modify before you launch the template ...
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: ...
Enable CloudWatch Monitoring on the VM-Series Firewall
Enable CloudWatch Monitoring on the VM-Series Firewall The VM-Series firewall on AWS can publish native PAN-OS metrics to AWS CloudWatch, which you can use to ...
Heat Templates for Service Chaining andService Scaling
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 ...
Launch the VM-Series Auto Scaling Template for AWS (v2.0)
Launch the VM-Series Auto Scaling Template for AWS (v2.0) You can choose to deploy the firewall template in one VPC and the sample application template ...
Session Settings The following table describes session settings. Session Settings Description Rematch Sessions Click Edit and select Rematch Sessions to cause the firewall to apply ...
Custom PAN-OS Metrics Published for Monitoring
PAN-OS® metrics published to public cloud monitoring systems such as AWS® CloudWatch, Azure® Application Insights, and Google® Stackdriver. ...
Stack Update with VM-Series Auto Scaling Template for AWS (v2.0)
Stack Update with VM-Series Auto Scaling Template for AWS (v2.0) A stack update allows you to modify the resources that the VM-Series Auto Scaling template—firewall-v2.0.template—deploys. ...