Introduction Elasticsearch is an opensource distributed, multi-tenant search engine based on Lucene.  It provides a RESTful API through which users can ingest unstructured documents in JSON format and then retrieve them in real time. You can also use ingestion tools like Logstash, fluentd that gather logs from multiple sources, transform and ingest into Elasticsearch in realtime.     Kibana is an open source analytics and visualization platform that runs with Elasticsearch.  The users can use its browser-based interface to search, view and analyze data that was ingested into Elasticsearch in real time.   Elasticsearch is designed to be distributed and highly available.  For load balancing and reliability, a cluster can be setup which is a group of Elasticsearch nodes that are connected with each other. Nodes can be added and removed at any time.  Each node in the Elasticsearch cluster can be assigned a role based on its responsibilities. Data - Data nodes store data and handle data related operations like indexing, search and aggregations Master - Master nodes handles cluster wide metadata management and configuration actions like node addition and removal.   Pre-Requistes CloudCenter CloudCenter 4.8 and above Knowledge on how to use CloudCenter OS Ubuntu 14.04 Application Profile Package   The application profile package (elastic_local.zip) consists of the following folder: elastic_local - Ansible playbooks and scripts  that run during the Node Initialization lifecycle.  Please make sure to upload the file specified in the Downloads section to your artifact repository.   Application Profile   Import the application profile (es_appprofile.zip) specified in the Downloads section into CloudCenter   Choose your local artifact repository where you have stored the package.  The following app profile will be imported to your CloudCenter    Make sure the tier names stay intact. The tier names are used to determine which playbook to execute on the given VM Click on the Basic Information tab and  modify the path to your application package in your artifact repository   Save the application profile    Testing Deployment Once the application is deployed, you can run the following curl command to ingest a document in Elasticsearch curl -X POST -H "Content-Type: application/json" -d '{ "user" : "CloudCenter", "post_date" : "2018-07-23T12:30:00", "message" : "First document in Elasticsearch" }' "http://<ELASTICSEARCH_IP>:9200/sampleIndex/sampleType/"   where ELASTICSEARCH_IP is the ip address of the top most tier which is Kibana.  To see the indexed document in Kibana, add ‘sampleIndex’ as the index pattern   Testing Deployment Application Profile Package Application Profile    **App Profile Created by Johnu George. ... View more

Overview The CloudCenter platform allows you to define your own parameters or use the CloudCenter-supported parameters as identified in Parameters and Macros > Parameter Type. The webservice option is listed in the Parameter Type dropdown. If you configure this option, you must provide the Protocol (HTTP or HTTPS), Web Service URL, and the credentials (Username and Password) for the webservice. To do this, y ou can optionally launch an isolated Arcus server and configure the webservice to point to the Arcus server. Arcus is an API broker and translator. While the CloudCenter platform provides the Arcus integration, it is up to the customer using this feature to address the following dependencies: Send requests to the device's API URL Call the correct device-specific webservice method Convert the webservice response to the format expected by CloudCenter This document describes how to import device types and templates into Arcus and use it with Cisco CloudCenter. In this document we will use an integration with AVI Networks as an example. A list of device types and templates can be found at Arcus - Device Types and Templates Device Types The first step in this process is to import a Device Type. To import a device type follow these steps: Download the AVI Controller device type Log into your Arcus portal Click on Device Types in the left navigation and then the "Import from JSON" button Choose the file you download from the first step and click Submit The new device type will now show up in the list Devices Once the device type is uploaded, we need to create a device. Here will put in the information of the device such as IP, login user and password. Click on the Devices link on the left navigation pane Click on the New Device button located on the top right of the page Fill in the form as follows: Device Type: AVI Controller Name: <Name you want to give the Device> Base URL/IP: <URL of the AVI Controller or the device> SSL Validation: Check the box if required Device Account Username: <device username> Password: <device password> Blank password: Check the box if required Templates With the Device and Device Types created we will now create a template. The purpose of the template is to make specific API calls to the device and return the data to Cisco Cloud Center in the following format: [{"name":"p1","displayName":"Param 1"},{"name":"p2","displayName":"Param 2"}] Click on the Templates link on the left navigation pane and then the "Import from JSON" button on the top right. Choose the downloaded JSON file for the template. In this case we are going to use the template to get the Health Monitors for the AVI Controllers Click on the View button to see the details of the template Usage in Cisco CloudCenter Now that we have all the components in Arcus we can now integrate it with CloudCenter. This integration will happen when we use the parameter of type "webservice". Before integrating with CloudCenter make sure to create an API Account in Arcus. Click on the Devices link on the left navigation pane For the device that was created, click on the View button You should not see the list of templates created for this device. Copy the URL of the template you want to use (10.x.x.x/devices/1/templates/16/results.c3) Log into your Cisco CloudCenter setup. We will use that URL when we create a web service parameter type either in the application profile or a service. Create a parameter of type webservice. Fill in the following info related to the webservice: Protocol: <choose HTTP or HTTPS>. Web Service URL: <Tempalte URL from Arcus> Username: <Arcus API User> Password: <Arcus API User Password> Once created this will invoke the template in Arcus which will interact with the AVI controller to pull down the list of health monitors and present to the user at the time of deployment ... View more

Overview The CloudCenter platform allows you to define your own parameters or use the CloudCenter-supported parameters as identified in Parameters and Macros > Parameter Type. The webservice option is listed in the Parameter Type dropdown. If you configure this option, you must provide the Protocol (HTTP or HTTPS), Web Service URL, and the credentials (Username and Password) for the webservice. To do this, y ou can optionally launch an isolated Arcus server and configure the webservice to point to the Arcus server. Arcus is an API broker and translator. While the CloudCenter platform provides the Arcus integration, it is up to the customer using this feature to address the following dependencies: Send requests to the device's API URL Call the correct device-specific webservice method Convert the webservice response to the format expected by CloudCenter For details on how to use Arcus with CloudCenter please refer to the CloudCenter Documentation This document list various Device types and templates that you can import into Arcus and use with Cloud Center.  Device Types and Templates The following content is listed by the devices. Please refer to this sample document on how to import these device types and templates into Arcus. Device: AVI Networks Device Type: AVI Controller Templates: Template Name Description AVI-GetHealthMonitor Get the list of health monitors from AVI Controller AVI-GetApplicationProfile Get list of application profiles from AVI Controller AVI-GetPersistenceProfile Get list of persistence profiles from AVI Controller Device: F5 Networks Device Type: F5 Templates: Template Name Description F5-GetNodeByName Get the list Nodes by Name F5-GetNodeByFullPath Get list of Nodes by Node's full Path Device Type: F5 iWorkflow Templates: Template Name Description F5W-GetCloudConnectors Get the list of Cloud Connectors F5W-GetTenantNames Get list of Tenant Names F5W-GetIappTemplateNames Get list of (iApp) Templates Device: Cisco ACI Device Type: ACI Templates: Template Name Description ACI-GetVlanPoolNames Get list of VLAN Pool names from the ACI Fabric ACI-GetLeaPolicyGroupNames Get list of Leaf Policy Group names from the ACI Fabric ACI-GetTenantNames Get list of Tenant from the ACI Fabric Device: EMC ViPR Device Type: EMC ViPR Templates: Template Name Description VIPR-GetHosts Get the list of hosts that ViPR has in inventory VIPR-GetHostIpInterfaces Get a list of IP interfaces based off of the host_id specified VIPR-GetVirtualArrays Get list of Virtual Arrays that ViPR has in inventory VIPR-GetVcenterList Get a list of vCenters that ViPR has in inventory ViPR-GetVirtualBlockPools Get a list of the Virtual Block Pools Device: Cisco UCS Central Device Type: UCS Central Templates: Template Name Description UCSC-GetPermittedVlans Get a list of Permitted VLANs from UCS Central UCSC-GetMacPools Get a list of MAC Pools from UCS Central UCSC-GetServiceProfiles Get a list of Service Profiles from UCS Central UCSC-GetOrgs Get the list of Orgs from UCS Central Device: VMware vCenter Device Type: vSphere Templates: Template Name Description VC-GetVMList Get a list of Virtual Machines VC-GetVMListNoBlanks Get a list of Virtual Machines and remove blank entries Device: Cisco HyperFlex Device Type: HyperFlex Controller Templates: Template Name Description HX-GetDatastoreCommonName Get a list of HyperFlex Datastores Device: NetApp Device Type: NetApp SolidFire Templates: Template Name Description SF-GetActiveVolumes Get the list of active Volumes from the SolidFire Controller Device: CloudCenter Device Type: CloudCenter Templates: Template Name Description C3-GetJobsList Get the list of Jobs from CloudCenter Manager C3-GetUsersList Get the list of Users from CloudCenter Manager ... View more

Introduction The CloudCenter platform supports integration to various Load Balancers. This document provides information on integration with F5 by creating an external service in CloudCenter. F5 BIG-IP provides a wide range of application delivery services, such as server load balancing (SLB), L4-L7 firewall and SSL VPN. With the use of iApps and rich foundation of F5 API, Cisco Cloud Center can deploy F5 virtual servers to provide SLB, FW and SSL VPN services to the applications. Cisco Cloud Center will maintain the application services catalog, provide consistent and agile L4-L7 services to application deployment in both private and public cloud environments. Prerequisites CloudCenter CloudCenter 4.8 and above Knowledge on how to use CloudCenter F5 BIG-IP Release 12.1.x Download App Services iApps 2.0 from GitHub and import into BIG-IP BIG-IP management interface must be configured and reachable by Cloud Center BIG-IP must be licensed Service Package Bundle The Packer Service bundle consists of the following files: service - The main script that has the logic for the integration serviceDictionary.csv - The dictionary CSV file that has the list of all the parameters and their defaults. If you want to get addition input from the user, they need to be added to this file and also in the UI. The format of this file is as follows: DisplayName,paramName,paramType,defaultValue,visible,optional e.g. Root Volume Size,root_volume_size,10,Y,N       The parameter name is key here and should match the parameter name in the UI bigip_rest.py - script that calls the F5 APIs. This python script is called from the main service script cliqr.template - F5 template file use by bigip_rest.py Service Description To add this service login to CloudCenter as an administrator and click on Admin->Services->Add Service. Use the information listed below to create the service. Service Type: External Service Name: F5-LB Service ID: f5lb Description: F5 Load Balancer Category: Load Balancer External Lifecycle Actions: External Action Bundle : <location of f5lb.zip> Update:      Script from Bundle: service update Start:      Script from Bundle: service start Stop:      Script from Bundle: service stop Service Parameters Parameter Name bigIPAddress Display Name IP Address of BIG-IP Type string                               Default Value User Options Parameter Name bigIPuser Display Name   User Name for BIG IP      Type string Default Value admin User Options Parameter Name bigIPPassword Display Name Password for BIG-IP        Type password Default Value User Options Deployment Parameters Parameter Name pool__addr Display Name              Virtual Server Address                    Type string Default Value User Options Visible, Editable Parameter Name name Display Name                 Application Services Name                   Type string Default Value User Options Visible, Editable Parameter Name pool__port Display Name VIP Pool Port                    Type string Default Value 80 User Options Visible, Editable Downloads AppServices iApp F5 External Service Bundle Appendix Importing iApps into BIG-IP Go to BIG-IP -> iApps -> Template -> Import: Click “Choose File” After locate and select the iApps, click “Upload” Now the iApps is ready to be deployed through Cisco Cloud Center ... View more

Introduction   The CloudCenter platform supports integration to various load balancers. This document provides information on integration with Avi Networks to handle creating virtual services, pools, pool servers, and adding or removing servers from pools during a scaling operation.   The Avi Vantage Platform delivers automated application services including load balancing , application analytics , predictive autoscaling , and security for on-premises or public cloud applications. The platform is built on software-defined principles, runs on commodity x86 servers, VMs, or containers, and matches the automation and self-service goals of modern enterprises.     Prerequisites   CloudCenter CloudCenter 4.8.x and above Knowledge of Cisco CloudCenter and how to create services   Avi Networks Avi Controller with VMware or LSC integration     Service Package Bundle   The Packer Service bundle consists of the following files:   service - The main script that has the logic for the integration serviceDictionary.csv - The dictionary CSV file that has the list of all the parameters and their defaults. If you want to get addition input from the user, they need to be added to this file and also in the UI. The format of this file is as follows: DisplayName,paramName,paramType,defaultValue,visible,optional e.g. Root Volume Size,root_volume_size,10,Y,N       The parameter name is key here and should match the parameter name in the UI avi_install.py - Script to install prerequisites avi_python_client.py - Main script to parse the parameters and call the Avi Controller endpoint api_endpoint.py - Avi controller endpoint script sample_lib.py - Avi SDK   Service Description   To add this service login to CloudCenter as an administrator and click on Admin->Services->Add Service. Use the information listed below to create the service.     Service Type: External Service Name: Avi Networks Service ID: avinetworks Description: The Avi Vantage Platform delivers automated application services including load balancing , application analytics , predictive autoscaling , and security for on-premises or public cloud applications . Category: Load Balancer   External Lifecycle Actions:   External Action Bundle : <location of avinetworks.zip>   Update:      Script from Bundle: service update   Start:      Script from Bundle: service start   Stop:      Script from Bundle: service stop     Service Parameters       Parameter Name aviControllerIp Display Name Avi Controller IP Type string                                Default Value   User Options         Parameter Name aviControllerUserName Display Name    Avi Controller User Name Type string Default Value admin User Options         Parameter Name aviPassword Display Name Avi Controller Password   Type password Default Value   User Options       Deployment Parameters       Parameter Name aviTenantName Display Name               Avi Controller Tenant Name                Type string Default Value   User Options Visible, Editable       Parameter Name vipName Display Name              Virtual Service Name                            Type string Default Value   User Options Visible, Editable       Parameter Name vipIp Display Name Virtual Service IP                 Type string Default Value   User Options Visible, Editable       Parameter Name vipPort Display Name Virtual Service Port               Type string Default Value 80 User Options Visible, Editable       Parameter Name sslEnable Display Name          Enable SSL                 Type list List Values Yes,No                                            Default Value No User Options Visible, Editable       Parameter Name sslCert Display Name          SSL Certificate                                Type path Default Value   User Options Visible, Editable       Parameter Name sslKey Display Name       SSL Key                                      Type path Default Value   User Options Visible, Editable       Parameter Name appProfile Display Name             Avi Application Profile                         Type list List Values       System-DNS,System-HTTP,System-L4-Application,System-SSL-Application,System-Secure-HTTP Default Value System-HTTP User Options Visible, Editable       Parameter Name persistence Display Name           Persistence                Type list List Values System-Persistence-App-Cookie,System- Persistence-Client-IP ,System-Persistence-Custom-Http-Header,System-Persistence-Http-Cookie,System-Persistence-TLD Default Value System-Persistence-Http-Cookie User Options Visible, Editable         Parameter Name lbMethod Display Name      Load Balancing Method Type list List Values Round Robin,Least Load,Fewest Servers, Consistent Hash,Fastest Response,Core Affinity,Least Connections Default Value Least Connections User Options Visible, Editable       Parameter Name listenPort Display Name                    Pool Server Port             Type string                                                    Default Value 80 User Options Visible, Editable       Parameter Name poolMembers Display Name            Pool Servers Type string                                           Default Value   User Options           Parameter Name poolMonitor DisplayName     Health Monitor                                             Type   list List Values System-DNS,System-HTTP,System-HTTPS,System-Ping,System-TCP,System-UDP       Default Value System-TCP User Options Visible, Editable     Downloads     avicontroller.zip ... View more

Introduction Packer is an open source tool for creating identical machine images for multiple platforms from a single source configuration. Packer is lightweight, runs on every major operating system, and is highly performant, creating machine images for multiple platforms in parallel.  Using the CloudCenter platform we can directly use packer to create AMIs in AWS and add the image mapping to CloudCenter to be used by various application profiles. This helps with image management in the public cloud using CloudCenter. Note in this example, during image mapping we will leave the mapping of the instance types empty. Once the images are mapped, the user will have to edit the mapping to choose the right instance type they would like to make available for this image. The service highlights how we can use packer to create a Centos image in AWS.  This script is an example usage of Packer. You can leverage this integration to create more advance deployments. Prerequisites CloudCenter CloudCenter 4.8.x and above CloudCenter Orchestrator running on AWS Service Package Bundle The Packer Service bundle consists of the following files: service - The main script that has the logic for the integration serviceDictionary.csv - The dictionary CSV file that has the list of all the parameters and their defaults. If you want to get addition input from the user, they need to be added to this file and also in the UI. The format of this file is as follows: DisplayName,paramName,paramType,defaultValue,visible,optional e.g. Root Volume Size,root_volume_size,10,Y,N       The parameter name is key here and should match the parameter name in the UI packer-builder-amazon-ebs - The amazon-ebs Packer builder is able to create Amazon AMIs backed by EBS volumes for use in EC2 Service Description When using Packer we need to provide parameters for the template that is used to build the image. This example integration provides a sample template to create a Centos image. Users can modify these parameters and create their own templates based on their use case To add this service login to CloudCenter as an administrator and click on Admin->Services->Add Service. Use the information listed below to create the service. Service Type: External Service Name: Packer Service ID: packerbuild Description: Packer is an open source tool for creating identical machine images for multiple platforms from a single source configuration. Category: Custom Service External Lifecycle Actions: External Action Bundle : <location of packerbuild.zip> Start:      Script from Bundle: service start Service Parameters Parameter Name PACKER_ZIP_URL Display Name PACKER ZIP URL Type string Default Value https://releases.hashicorp.com/packer/1.1.3/packer_1.1.3_linux_amd64.zip User Options Parameter Name api_user Display Name     CloudCenter API User Type string Default Value cliqradmin User Options Parameter Name api_key Display Name CloudCenter API Key Type string Default Value User Options Parameter Name ccm_url Display Name CloudCenter CCM URL Type string Default Value <your ccm ip> User Options Deployment Parameters Parameter Name ami_name Display Name AMI Name                   Type string Default Value User Options Visible, Editable Parameter Name source_ami Display Name      Source AMI                  Type string Default Value User Options Visible, Editable Parameter Name subnet_id Display Name Subnet ID                  Type string Default Value User Options Visible, Editable Parameter Name vpc_id Display Name VPC ID                       Type string Default Value User Options Visible, Editable Parameter Name instance_type Display Name           Instance Type                    Type string Default Value User Options Visible, Editable Parameter Name ssh_username Display Name           SSH Username                   Type string Default Value User Options Visible, Editable Parameter Name virtualization Display Name        Virtualization                Type string Default Value User Options Visible, Editable Parameter Name root_volume_size Display Name              Root Volume Size                  Type string Default Value 10 User Options Visible, Editable Parameter Name log_volume_size Display Name            Log Volume Size                  Type string Default Value 10 User Options Visible, Editable Parameter Name region Display Name       AWS Region                  Type string Default Value User Options Visible, Editable Parameter Name template_url Display Name                     Packer Template Location                Type path Default Value User Options Visible, Editable Parameter Name provisioner_script_url Display Name           Provisioner Script Location Type path Default Value User Options Visible, Editable Parameter Name image_name Display Name                      CloudCenter Image Name                  Type string Default Value User Options Visible, Editable Parameter Name image_desc Display Name                CloudCenter Image Description Type string Default Value User Options Visible, Editable Parameter Name os_type Display Name            CloudCenter Image OS Type Type list List Values LINUX,WINDOW Default Value LINUX User Options Visible, Editable Downloads packerbuild.zip Sample Packer Template Sample Provisioner Script ... View more

Introduction The CloudCenter platform supports integration to various Load Balancers. This document provides information on integration with A10 Lightning ADC and Harmony Controller by creating an external service in CloudCenter. A10 Lightning ADC is cloud-native and is a software that can be installed on a Linux machine. It is a state-less data-plane device. Configuration of Lightning ADC is fully managed by Harmony Controller that is available as SaaS. Lightning ADC is purpose-built for containers & micro-services and includes  Advanced traffic management: elastic load balancing, content based switching, AWS zone-based affinity, automated Blue/Green deployments Performance optimization: compression, caching, connection multiplexing Application security: WAF for protecting OWASP top 10 vulnerabilities like sql- injection, XSS, CSRF, protection against bad BOTs, malware, application DDoS attacks Harmony Controller (SaaS) provides
 Simplified operations with centralized policy management across AWS regions, clouds and datacenters Visibility into distributed environment with per-application metrics, analytics & insights Automation via APIs & integration's with devops tools 
 Prerequisites CloudCenter CloudCenter 4.6.x and above A10 Networks A tenant account on SaaS Harmony Controller Internet connectivity for calling Harmony controller APIs and Installing Lightning ADC software Service Description Configuring A10 Lightning ADC consists of various steps Create a Lightning ADC Cluster object in the Harmony Controller and retrieve the cluster ID This cluster ID will be used to install the Lightning ADC instances. All instances with the same cluster ID will become part of the cluster on connection to the Harmony Controller Launch Lightning ADC instances Create a minimal application configuration with default policies in the Harmony Controller and attach the Lightning ADC cluster. These steps will be divided into 3 services: Lightning ADC Cluster Creation (External Service) A10 Lightning ADC (Virtual Machine with agent) Harmony App Creation (External Service) __________________________________________________ Harmony Cluster Creation To add this service login to CloudCenter as an administrator and click on Admin->Services->Add Service. Use the information listed below to create the service. Service Type: External Service Name: Harmony Cluster Creation Service ID: a10clustercreation Description: Create a Lightning ADC cluster under the tenant for which credentials. Multiple Lightning ADCs can be launched with one cluster ID. All these Lightning ADCs will form a logical cluster and handle the traffic in active-active configuration. Category: Custom Service External Lifecycle Actions: External Action Bundle : <location of a10clustercreation.zip> Start:      Script from Bundle: controllerservice start Service Parameters Parameter Name a10_api_server Display Name A10 API Server Type string Default Value https://api.a10networks.com/api/v2 User Options Parameter Name a10_user Display Name A10 User Type string Default Value                                                               User Options Parameter Name a10_user_passwd Display Name A10 User Password Type password Default Value                                                               User Options Deployment Parameters Parameter Name provider Display Name Provider Type string Default Value                                                               User Options Visible, Editable Parameter Name tenant Display Name Tenant Type string Default Value                                                               User Options Visible, Editable Parameter Name cluster_name Display Name Cluster Name Type string Default Value                                                               User Options Visible, Editable __________________________________________________ A10 Lightning ADC To add this service login to CloudCenter as an administrator and click on Admin->Services->Add Service. Use the information listed below to create the service. Note: You can attach a scaling policy to this tier. Service Type:Virtual Machine Name: A10 Lightning ADC Service ID: a10lightningADC Description: Install Lightning ADC software on the virtual machine.The launched Lightning ADC will automatically attach itself to the cluster whose cluster ID is provided. Category: Custom Service Supported Images: CentOS 7.x Agent Lifecycle Actions: Start:      URL: <location of adcclusterservice.sh> Service Parameters Parameter Name a10_api_server Display Name A10 API Server Type string Default Value https://api.a10networks.com/api/v2 User Options Parameter Name minClusterSize Display Name Minimum Number of Nodes Type number Default Value 1                                                         User Options Visible, Editable Parameter Name maxClusterSize Display Name Maximum Cluster Size Type number Default Value 1                                                         User Options Visible, Editable ___________________________________________________ Harmony App Creation To add this service login to CloudCenter as an administrator and click on Admin->Services->Add Service. Use the information listed below to create the service. Service Type: External Service Name: Harmony App Creation Service ID: a10appcreation Description: Create an application and associated configuration hierarchy (with defaults) in Harmony Controller. It also attaches the Lightning ADC cluster to the application and makes it ready to use. Category: Load Balancer External Lifecycle Actions: External Action Bundle : <location of a10appcreation.zip> Update:      Script from Bundle: controllerservice update Start:      Script from Bundle: controllerservice start Stop:      Script from Bundle: controllerservice stop Service Parameters Parameter Name a10_api_server Display Name A10 API Server Type string Default Value https://api.a10networks.com/api/v2 User Options Parameter Name a10_user Display Name A10 User Type string Default Value                                                               User Options Parameter Name a10_user_passwd Display Name A10 User Password Type password Default Value                                                               User Options Deployment Parameters Parameter Name provider Display Name Provider Type string Default Value                                                               User Options Visible, Editable Parameter Name tenant Display Name Tenant Type string Default Value                                                               User Options Visible, Editable Parameter Name cluster_name Display Name Cluster Name Type string Default Value                                                               User Options Visible, Editable                                               Parameter Name app_name Display Name Application Name Type string Default Value                                                               User Options Visible, Editable Parameter Name domain_name Display Name Domain Name Type string Default Value                                                               User Options Visible, Editable Parameter Name service_name Display Name Service Name Type string Default Value                                                               User Options Visible, Editable Sample Application Here is an sample application profile that uses these services: Downloads a10clustercreation.zip a10appcreation.zip adcclusterservice.sh ... View more

Please use F5 BIG-IP Introduction The CloudCenter platform supports integration to various Load Balancers. This document provides information on integration with F5 by creating an external service in CloudCenter. F5 BIG-IP provides a wide range of application delivery services, such as server load balancing (SLB), L4-L7 firewall and SSL VPN. With the use of iApps and rich foundation of F5 API, Cisco Cloud Center can deploy F5 virtual servers to provide SLB, FW and SSL VPN services to the applications. Cisco Cloud Center will maintain the application services catalog, provide consistent and agile L4-L7 services to application deployment in both private and public cloud environments. Prerequisites CloudCenter CloudCenter 4.6.x and above F5 BIG-IP Release 12.0 and above Download App Services iApps 1.0 and import into BIG-IP BIG-IP management interface must be configured and reachable by Cloud Center Service Description To add this service login to CloudCenter as an administrator and click on Admin->Services->Add Service. Use the information listed below to create the service. Service Type: External Service Name: F5-LB Service ID: f5lb Description: F5 Load Balancer Category: Load Balancer External Lifecycle Actions: External Action Bundle: f5lb.zip Service Parameters Display Name Parameter Name Description Type Default Value Visible Editable Optional BIG IP Address bigIPAddress IP address of BIG IP string BIG IP User bigIPUser Username of BIG IP string BIG IP Password bigIPPassword Password of BIG IP password VIP vip Virtual Server Address string Load Balancing Method lbMethod Load Balancing Method string round-robin * * Default Persistence defaultPersistence Default Persistence Profile string * * * Fallback Persistence fallbackPersistence Fallback Persistence Profile string * * * iRules iRules string * * * VIP Name vipName Name of Virtual Server string * * VIP Port vipPort VIP Port string 80 * * Member Default Port listenPort Member Default Port string 80 * * Pool Member poolMember Pool Member String /Common/http * * Appendix Downloads AppServices iApp F5 External Service Bundle Importing iApps into BIG-IP Go to BIG-IP -> iApps -> Template -> Import: Click “Choose File” After locate and select the iApps, click “Upload” Now the iApps is ready to be deployed through Cisco Cloud Center ... View more