Cisco Cisco Prime Network Services Controller 3.0 Guide Du Développeur
Page 60
OL-28369-01
name="Create Vm :TestVM"
opState="running"
operationType="unknown"
requestTime="2013-09-26T04:13:09.129"
startTime="2013-09-26T04:13:09.433"
status="created"
tryCount="0"/>
</inConfig>
</configMoChangeEvent>
opState="running"
operationType="unknown"
requestTime="2013-09-26T04:13:09.129"
startTime="2013-09-26T04:13:09.433"
status="created"
tryCount="0"/>
</inConfig>
</configMoChangeEvent>
After having the Task Mo, user must subscribe to the event on Task Mo. When the Task is done, the user will get a
completed response from Prime Network Services Controller.
completed response from Prime Network Services Controller.
InterCloud VM Status Monitoring
To monitor InterCloud VM status, the API user needs to set the collectStats attribute
to “Yes” on the
hcloudVmStatsCollection Mo.
<configConfMos
cookie="<real_cookie>"
commCookie="5/12/0/a0"
srcExtSys="172.25.97.162"
destExtSys="172.25.97.162"
srcSvc="sam_extXMLApi"
destSvc="resource-mgr_dme"
inHierarchical="no">
<inConfigs>
<pair key="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll">
<hcloudVmStatsCollection
collectStats="yes"
dn="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll"
status="modified"/>
</pair>
</inConfigs>
</configConfMos>
cookie="<real_cookie>"
commCookie="5/12/0/a0"
srcExtSys="172.25.97.162"
destExtSys="172.25.97.162"
srcSvc="sam_extXMLApi"
destSvc="resource-mgr_dme"
inHierarchical="no">
<inConfigs>
<pair key="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll">
<hcloudVmStatsCollection
collectStats="yes"
dn="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll"
status="modified"/>
</pair>
</inConfigs>
</configConfMos>
After this API request, Prime Network Services Controller immediately replies with the following API response:
<configConfMos
cookie="<real_cookie>"
commCookie="5/12/0/a0"
srcExtSys="172.25.97.162"
destExtSys="172.25.97.162"
srcSvc="sam_extXMLApi"
destSvc="resource-mgr_dme"
response="yes"
errorCode="0"
errorDescr="">
<outConfigs>
<pair key="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll">
<hcloudVmStatsCollection
collectStats="yes"
dn="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll"
lastStatsRequest="1970-01-01T00:00:00.000"
status="modified"
throttleIntervalInSeconds="00:00:00:15"/>
</pair>
</outConfigs>
</configConfMos>
cookie="<real_cookie>"
commCookie="5/12/0/a0"
srcExtSys="172.25.97.162"
destExtSys="172.25.97.162"
srcSvc="sam_extXMLApi"
destSvc="resource-mgr_dme"
response="yes"
errorCode="0"
errorDescr="">
<outConfigs>
<pair key="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll">
<hcloudVmStatsCollection
collectStats="yes"
dn="hcloud-root/vpc-VPc1/icl-Cne1/vm-stats-coll"
lastStatsRequest="1970-01-01T00:00:00.000"
status="modified"
throttleIntervalInSeconds="00:00:00:15"/>
</pair>
</outConfigs>
</configConfMos>
After receiving an immediate response from Prime Network Services Controller, the API user must subscribe to
events on the following Mos to get VM status: monitorInterfaceStatistics, monitorComputeResourceStatistics.
events on the following Mos to get VM status: monitorInterfaceStatistics, monitorComputeResourceStatistics.
<configMoChangeEvent
cookie=""
cookie=""