Guía Del DesarrolladorTabla de contenidos1 Introduction41.1 Using NETCONF41.1.1 Get configuration51.1.2 Get non-configurable data51.1.3 Subscribe ESC notifications51.1.4 Make RPC calls51.1.5 Push in configurations51.2 ConfD CLI51.3 Change ConfD Admin Password51.4 NETCONF Protocol Operations51.5 NETCONF Capabilities62 Configuration Data92.1 Reading Configuration Data92.1.1 Fetching all config data92.1.1.1 Netconf Request92.1.1.2 Netconf Response92.1.2 Example: Fetching deployed services by network name122.1.2.1 Netconf Request122.1.2.2 Netconf Response122.2 Writing Configuration Data (CRUD operations)132.2.1 Stage 1: Acceptance or Rejection of a Configuration Request132.2.2 Stage 2: Activation of a new Configuration142.2.2.1 Event Notifications142.2.2.2 Operational Data142.2.2.3 Activation Failures142.2.3 Configuration Workflows142.2.4 Combining Workflows143 Operational Data163.1 Reading Operational Data163.1.1 Fetching all operational data163.1.1.1 Netconf Request163.1.1.2 Netconf Response164 Custom RPC Methods184.1 serviceAction method184.2 vmAction method185 ESC Workflows using Netconf185.1 Configuration Workflows185.1.1 Create Tenant185.1.1.1 Netconf Request185.1.1.2 Netconf Response185.1.1.3 Configuration Activation19On Success:19Event notification19Operational data19Netconf Request19Netconf Response19On Failure:20Event notification20Operational data20Handling Activation Failures205.1.2 Delete Tenant215.1.2.1 Netconf Request215.1.2.2 Netconf Response215.1.2.3 Configuration Activation21On Success:21Event notification21Operational data22On Failure:22Event notification22Operational data22Handling Activation Failures225.1.3 Create Network235.1.3.1 Netconf Request235.1.3.2 Netconf Response235.1.3.3 Configuration Activation23On Success:23Note: attributes ‘vlan_id’, ‘switch_name’ and ‘number_of_ports’ are required for VMware VIM23Event notification23On Failure:24Event notification24Handling Activation Failures245.1.4 Delete Network255.1.4.1 Netconf Request255.1.4.2 Netconf Response255.1.4.3 Configuration Activation25On Success:25Event notification25On Failure:26Event notification26Handling Activation Failures265.1.5 Create Subnet275.1.5.1 Netconf Request275.1.5.2 Netconf Response275.1.5.3 Configuration Activation27On Success:27Event notification27On Failure:28Event notification28Handling Activation Failures285.1.6 Delete Subnet295.1.6.1 Netconf Request295.1.6.2 Netconf Response295.1.6.3 Configuration Activation29On Success:29Event notification29On Failure:30Event notification30Handling Activation Failures305.1.7 Create Image315.1.7.1 Netconf Request315.1.7.2 Netconf Response315.1.7.3 Configuration Activation31On Success:31Event notification31Operational data32Netconf Request32Netconf Response32On Failure:32Event notification32Operational data32Handling Activation Failures325.1.8 Delete Image335.1.8.1 Netconf Request335.1.8.2 Netconf Response335.1.8.3 Configuration Activation33On Success:33Event notification33Operational data33On Failure:34Event notification34Operational data34Handling Activation Failures345.1.9 Create Flavor355.1.9.1 Netconf Request355.1.9.2 Netconf Response355.1.9.3 Configuration Activation35On Success:35Event notification35Operational data36Netconf Request36Netconf Response36On Failure:36Event notification36Operational data36Handling Activation Failures365.1.10 Delete Flavor385.1.10.1 Netconf Request385.1.10.2 Netconf Response385.1.10.3 Configuration Activation38On Success:38Event notification38Operational data38On Failure:39Event notification39Operational data39Handling Activation Failures395.1.11 [DEPRECATED] Register Service with the Service Catalog405.1.11.1 Netconf Request405.1.11.2 Netconf Response405.1.11.3 Configuration Activation41On Success:41Event notification41Operational data41Not applicable. There is no operational data for service registration.41On Failure:41Event notification41Operational data42Not applicable. There is no operational data for service registration.42Handling Activation Failures425.1.12 [DEPRECATED] Unregister Service from the Service Catalog435.1.12.1 Netconf Request435.1.12.2 Netconf Response435.1.12.3 Configuration Activation43On Success:43Event notification43Operational data44Not applicable. There is no operational data for service registration.44On Failure:44Event notification44Operational data44Not applicable. There is no operational data for service registration.44Handling Activation Failures445.1.13 Deploy Service455.1.13.1 Netconf Request455.1.13.2 Netconf Response475.1.13.3 Configuration Activation47Workflow Aggregation:47On Success:47Event notification47Operational data49Netconf Request49Netconf Response49On Failure:50Event notification50Operational data51Handling Activation Failures515.1.14 Un-deploy Service525.1.14.1 Netconf Request525.1.14.2 Netconf Response525.1.14.3 Configuration Activation52Workflow Aggregation:52On Success:53Event notification53Operational data54On Failure:54Event notification54Operational data54Handling Activation Failures545.1.15 Update Service545.1.15.1 Netconf Request555.1.15.2 Netconf Response575.1.15.3 Configuration Activation57On Success:57Event notification57Operational data58Netconf Request58Netconf Response58On Failure:59Event notification59Operational data60Handling Activation Failures605.2 Operational Workflows605.2.1 Service Operations605.2.1.1 Stop Service605.2.1.1.1 Netconf Request605.2.1.1.2 Netconf Response615.2.1.1.3 Event Notifications615.2.1.2 Start Service625.2.1.2.1 Netconf Request625.2.1.2.2 Netconf Response625.2.1.2.3 Event Notifications625.2.1.3 Reboot Service645.2.1.3.1 Netconf Request645.2.1.3.2 Netconf Response645.2.1.3.3 Event Notifications645.2.1.4 Disable Service Monitor665.2.1.4.1 Netconf Request665.2.1.4.2 Netconf Response665.2.1.4.3 Event Notifications665.2.1.5 Enable Service Monitor675.2.1.5.1 Netconf Response675.2.1.5.2 Event Notifications685.2.2 VM operations695.2.2.1 Stop VM695.2.2.1.1 Netconf Request69The “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...695.2.2.1.2 Netconf Response695.2.2.1.3 Event Notifications695.2.2.2 Start VM705.2.2.2.1 Netconf Request705.2.2.2.2 Netconf Response705.2.2.2.3 Event Notifications705.2.2.3 Reboot VM725.2.2.3.1 Netconf Request72The “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...725.2.2.3.2 Netconf Response725.2.2.3.3 Event Notifications725.2.2.4 Disable VM Monitor735.2.2.4.1 Netconf Request735.2.2.4.2 Netconf Response745.2.2.4.3 Event Notifications745.2.2.5 Enable VM Monitor755.2.2.5.1 Netconf Request755.2.2.5.2 Netconf Response755.2.2.5.3 Event Notifications756 ESC Triggered Workflows766.1 Recovery (Healing) Workflow76Recovery Initialize77Attempts for recovery77Recovery complete77Success Event notifications77On Failure:79Event notification79Handling Recovery Failures796.2 Scale Out/Scale in Work Flows796.2.1 Scale Out Work Flow796.2.1.1 Event Notifications796.2.2 Scale In Work Flow816.2.2.1 Event Notifications81Tamaño: 2 MBPáginas: 82Language: EnglishManuales abiertas
Notas de publicaciónTabla de contenidosCisco Elastic Services Controller 2.1 Release Notes1Introduction1New Features and Enhancements1VMware Features1OpenStack Features2Deprecated Features2Limitations3ESC Interface Limitations3Feature Limitations4VMware Limitations5Smart License De-registration6Cisco Elastic Services Controller Bugs7Cisco Bug Search Tool7Related Documentation8Accessibility Features in Cisco ESC8Tamaño: 400 KBPáginas: 9Language: EnglishManuales abiertas
Notas de publicaciónTabla de contenidosCisco Elastic Services Controller 2.1.5 Release Notes1Introduction1What's New in Cisco Elastic Services Controller1Deprecated Features2Limitations2ESC Interface Limitations2Feature Limitations3VMware Limitations4Smart License De-registration5Cisco Elastic Services Controller Bugs6Cisco Bug Search Tool7Related Documentation8Accessibility Features in Cisco ESC8Tamaño: 400 KBPáginas: 9Language: EnglishManuales abiertas
