Cisco Cisco Elastic Services Controller 2.3 개발자 가이드
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>
<esc_datamodel xmlns="http://www.cisco.com/esc/esc">
<opdata>
<tenants>
<tenant>
<name>mytenant</name>
<tenant_id>dccd22a13cc64e388a4b8d39e6a8fa7f</tenant_id>
</tenant>
<data>
<esc_datamodel xmlns="http://www.cisco.com/esc/esc">
<opdata>
<tenants>
<tenant>
<name>mytenant</name>
<tenant_id>dccd22a13cc64e388a4b8d39e6a8fa7f</tenant_id>
</tenant>
</tenants>
</esc_datamodel>
</data>
</rpc-reply>
</esc_datamodel>
</data>
</rpc-reply>
On Failure:
Event notification
An escEvent of type CREATE_TENANT with a status of FAILURE will be sent to Netconf subscribers if the
configuration action cannot be complete for some reason. If a FAILURE event occurs, there may be
cleanup required as described below under Handling Activation Failures
configuration action cannot be complete for some reason. If a FAILURE event occurs, there may be
cleanup required as described below under Handling Activation Failures
Operational data
After a tenant creation configuration has failed activation, there will be no change to the operational
data.
data.
Handling Activation Failures
If a failure occurs while activating a Create Tenant configuration change, the Netconf client should
explicitly bring the configuration back to a consistent state by sending the corresponding Delete Tenant
configuration change. A Delete Tenant sent at this stage should return an <ok> status, but will not
generate a Notification. The configuration change can then be retried explicitly by the Netconf client
once the underlying issue is resolved.
explicitly bring the configuration back to a consistent state by sending the corresponding Delete Tenant
configuration change. A Delete Tenant sent at this stage should return an <ok> status, but will not
generate a Notification. The configuration change can then be retried explicitly by the Netconf client
once the underlying issue is resolved.