Cisco Cisco Elastic Services Controller 2.3 Developer's Guide
</rule>
<rule>
<event_name>VM_UNDERLOADED</event_name>
<action>ALWAYS log</action>
</rule>
</admin_rules>
</rules>
<config_data>
<configuration>
<dst>iosxe_config.txt</dst>
<file>file://cisco/images/csr_config.sh</file>
</configuration>
<rule>
<event_name>VM_UNDERLOADED</event_name>
<action>ALWAYS log</action>
</rule>
</admin_rules>
</rules>
<config_data>
<configuration>
<dst>iosxe_config.txt</dst>
<file>file://cisco/images/csr_config.sh</file>
</configuration>
</config_data>
<scaling>
<min_active>1</min_active>
<max_active>5</max_active>
<elastic>true</elastic>
</scaling>
</vm_group>
</deployment>
</deployments>
<scaling>
<min_active>1</min_active>
<max_active>5</max_active>
<elastic>true</elastic>
</scaling>
</vm_group>
</deployment>
</deployments>
</tenant>
</tenants>
</esc_datamodel>
</config>
</edit-config>
</rpc>
</tenants>
</esc_datamodel>
</config>
</edit-config>
</rpc>
6.1.15.2 Netconf Response
An rpc-reply response is returned with a status of ok if the request was accepted for activation, or a
status of rpc-error if the request was rejected. See section
status of rpc-error if the request was rejected. See section
6.1.15.3 Configuration Activation
Workflow Aggregation:
For each dependent workflow specified in the configuration, a separate workflow is submitted. Refer to
the specific workflow description for information on configuration activation of each of these optional
workflows. As required, dependent workflows will be processed in the following order:
the specific workflow description for information on configuration activation of each of these optional
workflows. As required, dependent workflows will be processed in the following order:
Section 5.1.1: Create a Tenant (zero or one)
Section 5.1.3: Create a Network for a Tenant (zero or more)
Section 5.1.5: Create a Subnet for a Tenant (zero or more)
Multiple workflows of the same type are executed in parallel, and a failure in any workflow results in a
Deploy Service activation failure once the remaining workflows of the same type have finished.
Deploy Service activation failure once the remaining workflows of the same type have finished.
Workflows of different types are processed in sequence, and a failure in any of these workflows will
result in an immediate Deploy Service activation failure. Once all of these dependent workflows have
been successfully activated, the Deploy Service workflow is activated.
result in an immediate Deploy Service activation failure. Once all of these dependent workflows have
been successfully activated, the Deploy Service workflow is activated.