Cisco Cisco Elastic Services Controller 1.1 开发者指南
Operational data
After a flavor creation configuration has been successfully activated, the operational data for the flavor
will show the name, flavor_id and visibility of the flavor:
will show the name, flavor_id and visibility of the flavor:
Netconf Request
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter select=" esc_datamodel/opdata/flavors/flavor[name='myflavor']"
<get>
<filter select=" esc_datamodel/opdata/flavors/flavor[name='myflavor']"
</get>
</rpc>
</rpc>
Netconf Response
<rpc-reply message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data>
<esc_datamodel xmlns="http://www.cisco.com/esc/esc">
<opdata>
<flavors>
<flavor>
<name>myflavor</name>
<data>
<esc_datamodel xmlns="http://www.cisco.com/esc/esc">
<opdata>
<flavors>
<flavor>
<name>myflavor</name>
<flavor_id>db0209a5-cf8a-4eaa-89a1-64511519486a</flavor_id>
<public>true</public>
</flavor>
</flavors>
</opdata>
</esc_datamodel>
</data>
<public>true</public>
</flavor>
</flavors>
</opdata>
</esc_datamodel>
</data>
</rpc-reply>
On Failure:
Event notification
An escEvent of type CREATE_FLAVOR 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 flavor 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 Flavor configuration change, the Netconf client should
explicitly bring the configuration back to a consistent state by sending the corresponding Delete Flavor
configuration change. 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 Flavor
configuration change. The configuration change can then be retried explicitly by the Netconf client once
the underlying issue is resolved.