Release NotesTable of ContentsCisco Elastic Services Controller 2.2.9 Release Notes1Introduction1New Features and Enhancements of 2.2.91Deprecated Features2Cisco Elastic Services Controller Bugs2Cisco Bug Search Tool3Accessibility Features in Cisco ESC3Related Documentation4Size: 354 KBPages: 5Language: EnglishOpen manual
Release NotesTable of ContentsCisco Elastic Services Controller 2.2 Release Notes1Introduction1New Features and Enhancements1Cisco Elastic Services Controller Bugs3Cisco Bug Search Tool4Related Documentation4Accessibility Features in Cisco ESC5Size: 359 KBPages: 7Language: EnglishOpen manual
Developer's GuideTable of ContentsCisco Systems, Inc.11- Tenants : Manage ESC tenants7Implementation Notes9Creates a tenant which will be managed by ESC and can be used for creating other resources under it.Example request:9length 72 characters)11network (max length 72 characters)11(max length 72 characters)13Response Messages13Implementation Notes15Delete a subnet from ESC15subnet (max length 72 characters)15length 72 characters)15Response Messages1772 characters)18Parameters2072 characters)20notifications2272 characters)22Implementation Notes23Creates a Flavor which could be used for creating instance VMs. Example request:23notifications32event notifications32deployment (max length 72 characters)32Implementation Notes33Updates an existing deployment. Updates could be addition or removal of VM groups, interfaces, networks, KPIs and Rules, Day 0 config. After the service update operation is done, ESC will send a callback to the client with the result.33deployment (max length 72 characters)42notifications46length 72 characters)46Response Messages46Response Messages47length 72 characters)49Response Messages49category52Implementation Notes55Creates a dynamic mapping action(s). Example request:55to retrieve60Response Messages81Response Messages82Response Messages84Response Messages85Response Messages86Implementation Notes87This model schema displays details of ESC's response for Tenant Operations. ESC sends a payload response to the request header provided Callback URL87Response Messages88Size: 1.15 MBPages: 88Language: EnglishOpen manual
Developer's GuideTable of ContentsElastic Service Controller (ESC)1Netconf API - Release 2.211 Introduction41.1 Using NETCONF API41.1.1 Get configuration41.1.2 Get non-configurable data41.1.3 Subscribe ESC notifications41.1.4 Make RPC calls41.1.5 Push in configurations41.2 ConfD CLI41.3 Change ConfD Admin Password51.4 NETCONF Protocol Operations51.5 NETCONF Capabilities62 ESC Datamodel83 Configuration Data83.1 Reading Configuration Data83.1.1 Fetching all config data83.1.1.1 Netconf Request83.1.1.2 Netconf Response93.1.2 Example: Fetching deployed services by network name113.1.2.1 Netconf Request113.1.2.2 Netconf Response113.2 Writing Configuration Data (CRUD operations)123.2.1 Stage 1: Acceptance or Rejection of a Configuration Request123.2.2 Stage 2: Activation of a new Configuration133.2.2.1 Event Notifications133.2.2.2 Operational Data133.2.2.3 Activation Failures133.2.3 Configuration Workflows133.2.4 Combining Workflows134 Operational Data154.1 Reading Operational Data154.1.1 Fetching all operational data154.1.1.1 Netconf Request154.1.1.2 Netconf Response155 Custom RPC Methods175.1 serviceAction method175.2 vmAction method176 ESC Workflows using Netconf176.1 Configuration Workflows176.1.1 Create Tenant176.1.1.1 Netconf Request176.1.1.2 Netconf Response176.1.1.3 Configuration Activation18On Success:18Event notification18Operational data18Netconf Request18Netconf Response18On Failure:19Event notification19Operational data19Handling Activation Failures196.1.2 Delete Tenant206.1.2.1 Netconf Request206.1.2.2 Netconf Response206.1.2.3 Configuration Activation20On Success:20Event notification20Operational data21On Failure:21Event notification21Operational data21Handling Activation Failures216.1.3 Create Network226.1.3.1 Netconf Request226.1.3.2 Netconf Response226.1.3.3 Configuration Activation22On Success:22Note: attributes ‘vlan_id’, ‘switch_name’ and ‘number_of_ports’ are required for VMware VIM22Event notification22On Failure:23Event notification23Handling Activation Failures236.1.4 Delete Network246.1.4.1 Netconf Request246.1.4.2 Netconf Response246.1.4.3 Configuration Activation24On Success:24Event notification24On Failure:25Event notification25Handling Activation Failures256.1.5 Create Subnet266.1.5.1 Netconf Request266.1.5.2 Netconf Response266.1.5.3 Configuration Activation26On Success:26Event notification26On Failure:27Event notification27Handling Activation Failures276.1.6 Delete Subnet286.1.6.1 Netconf Request286.1.6.2 Netconf Response286.1.6.3 Configuration Activation28On Success:28Event notification28On Failure:29Event notification29Handling Activation Failures296.1.7 Create Image306.1.7.1 Netconf Request306.1.7.2 Netconf Response306.1.7.3 Configuration Activation30On Success:30Event notification30Operational data31Netconf Request31Netconf Response31On Failure:31Event notification31Operational data31Handling Activation Failures316.1.8 Delete Image326.1.8.1 Netconf Request326.1.8.2 Netconf Response326.1.8.3 Configuration Activation32On Success:32Event notification32Operational data32On Failure:33Event notification33Operational data33Handling Activation Failures336.1.9 Create Flavor346.1.9.1 Netconf Request346.1.9.2 Netconf Response346.1.9.3 Configuration Activation34On Success:34Event notification34Operational data35Netconf Request35Netconf Response35On Failure:35Event notification35Operational data35Handling Activation Failures356.1.10 Delete Flavor366.1.10.1 Netconf Request366.1.10.2 Netconf Response366.1.10.3 Configuration Activation36On Success:36Event notification36Operational data36On Failure:37Event notification37Operational data37Handling Activation Failures376.1.11 [DEPRECATED] Register Service with the Service Catalog386.1.11.1 Netconf Request386.1.11.2 Netconf Response386.1.11.3 Configuration Activation39On Success:39Event notification39Operational data39Not applicable. There is no operational data for service registration.39On Failure:39Event notification39Operational data40Not applicable. There is no operational data for service registration.40Handling Activation Failures406.1.12 [DEPRECATED] Unregister Service from the Service Catalog416.1.12.1 Netconf Request416.1.12.2 Netconf Response416.1.12.3 Configuration Activation41On Success:41Event notification41Operational data42Not applicable. There is no operational data for service registration.42On Failure:42Event notification42Operational data42Not applicable. There is no operational data for service registration.42Handling Activation Failures426.1.13 Deploy Service436.1.13.1 Netconf Request436.1.13.2 Netconf Response456.1.13.3 Configuration Activation45Workflow Aggregation:45On Success:45Event notification46Operational data47Netconf Request47Netconf Response48On Failure:49Event notification49Operational data49Handling Activation Failures506.1.14 Un-deploy Service506.1.14.1 Netconf Request506.1.14.2 Netconf Response506.1.14.3 Configuration Activation51Workflow Aggregation:51On Success:51Event notification51Operational data52On Failure:52Event notification52Operational data52Handling Activation Failures526.1.15 Update Service536.1.15.1 Netconf Request536.1.15.2 Netconf Response556.1.15.3 Configuration Activation56On Success:56Event notification56Operational data56Netconf Request56Netconf Response56On Failure:58Event notification58Operational data58Handling Acti vation Failures586.2 Operational Workflows586.2.1 Service Operations596.2.1.1 Stop Service596.2.1.1.1 Netconf Request596.2.1.1.2 Netconf Response596.2.1.1.3 Event Notifications596.2.1.2 Start Service606.2.1.2.1 Netconf Request606.2.1.2.2 Netconf Response606.2.1.2.3 Event Notifications616.2.1.3 Reboot Service626.2.1.3.1 Netconf Request626.2.1.3.2 Netconf Response626.2.1.3.3 Event Notifications626.2.1.4 Disable Service Monitor646.2.1.4.1 Netconf Request646.2.1.4.2 Netconf Response646.2.1.4.3 Event Notifications646.2.1.5 Enable Service Monitor656.2.1.5.1 Netconf Response666.2.1.5.2 Event Notifications666.2.2 VM operations676.2.2.1 Stop VM676.2.2.1.1 Netconf Request67The “force” option in the request decides if ESC considers the min_vm requirement for the service. Since stopping a VM would affect the service availability, after the VM is stopped the min_vm requirement specified in the datamodel may not be satisfit...676.2.2.1.2 Netconf Response676.2.2.1.3 Event Notifications686.2.2.2 Start VM686.2.2.2.1 Netconf Request686.2.2.2.2 Netconf Response696.2.2.2.3 Event Notifications696.2.2.3 Reboot VM706.2.2.3.1 Netconf Request70The “force” option in the request decides if ESC considers the min_vm requirement for the service. Since stopping a VM would affect the service availability, after the VM is rebooted the min_vm requirement specified in the datamodel may not be satisfi...706.2.2.3.2 Netconf Response716.2.2.3.3 Event Notifications716.2.2.4 Disable VM Monitor726.2.2.4.1 Netconf Request726.2.2.4.2 Netconf Response726.2.2.4.3 Event Notifications726.2.2.5 Enable VM Monitor736.2.2.5.1 Netconf Request736.2.2.5.2 Netconf Response736.2.2.5.3 Event Notifications746.2.2.6 Recovery VM756.2.2.6.1 Netconf Request756.2.2.6.2 Netconf Response756.2.2.6.3 Event Notifications757 ESC Triggered Workflows787.1 Recovery (Healing) Workflow78Recovery Initialize78Attempts for recovery79Recovery complete79Success Event notifications79On Failure:80Event notification80Handling Recovery Failures817.2 Scale Out/Scale in Work Flows817.2.1 Scale Out Work Flow817.2.1.1 Event Notifications817.2.2 Scale In Work Flow827.2.2.1 Event Notifications83Size: 1.1 MBPages: 84Language: EnglishOpen manual
