Руководство Разработчика для Cisco Cisco Elastic Services Controller 1.0
5.1.1.3 Configuration Activation
On Success:
Event notification
An escEvent of type CREATE_TENANT with a status of SUCCESS will be sent to Netconf subscribers once
the configuration activation has completed. This indicates that the activation workflow is complete and
the configuration resource has been successfully created in the VIM.
the configuration activation has completed. This indicates that the activation workflow is complete and
the configuration resource has been successfully created in the VIM.
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-05-05T19:38:27.71+00:00</eventTime>
<eventTime>2015-05-05T19:38:27.71+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>Tenant successfully created</status_message>
<tenant>mytenant</tenant>
<vm_source/>
<vm_target/>
<event>
<type>CREATE_TENANT</type>
<status>SUCCESS</status>
<status_message>Tenant successfully created</status_message>
<tenant>mytenant</tenant>
<vm_source/>
<vm_target/>
<event>
<type>CREATE_TENANT</type>
</event>
</escEvent>
</notification>
</escEvent>
</notification>
Operational data
After a tenant creation configuration has been successfully activated, the operational data for the
tenant will show the name and the tenant_id:
tenant will show the name and the tenant_id:
Netconf Request
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter select="esc_datamodel/opdata/tenants/tenant[name=’mytenant’]"
type="xpath"/>
</get>
</rpc>
<get>
<filter select="esc_datamodel/opdata/tenants/tenant[name=’mytenant’]"
type="xpath"/>
</get>
</rpc>
Netconf Response
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<data>
<data>
<esc_datamodel xmlns="http://www.cisco.com/esc/esc">
<opdata>
<tenants>
<tenant>
<opdata>
<tenants>
<tenant>
<name>mytenant</name>
<tenant_id>dccd22a13cc64e388a4b8d39e6a8fa7f</tenant_id>
</tenant>
</tenants>
</esc_datamodel>
</data>
</rpc-reply>
<tenant_id>dccd22a13cc64e388a4b8d39e6a8fa7f</tenant_id>
</tenant>
</tenants>
</esc_datamodel>
</data>
</rpc-reply>