Unified Management Platform (CMS)

1. cormorantCMS
   1. CMS

cormorantCMS alleviates the challenges posed by microservices in a private cloud, which is very difficult with the traditional hardware/VLB acquisition model.

50. each application.ADC: Use a dedicated ADC to provide a one-to-one matching deployment pattern for applications.
50. CI/CD: Adapt to the continuous integration and delivery requirements of ADC configurations.
50. Kubernetes Ingress Controller: Agent-free K8S Ingress Controller, used to publish K8S services (whether HTTP or non-HTTP services), with comprehensive load balancing functions, including AAA, QoS, third-party (ELK, etc.) integration, etc.
    2. cormorant loadCMSvirtualServices
       1. cormorantCMS Virtual Services

cormorantCMSis a virtualization platform (can support ESXi,KVM and Hyper-V), eachcormorantCMScan provide automated support, up300 VLB instances, each CMS can manage up to 500 hardware/VLB instances simultaneously.

1. 1. 2. cormorantCMS Deploy ADC on Demand

cormorantCMS can automatically deploy VLB instances in a private cloud (VMware ESXi/vCenter,KVM) within a minute, or manually deploy VLB instances in a private cloud (VMware/ESXi/vCenter,KVM,XEN,Hyper-V,VirtualBox).

automatically or manually deployedVLB instances can directly deploy authorized licenses without limiting the number of VLB instances, and the throughput/SSL TPS of VLB instances is not limited.

automatically or manually deployedVLB instances do not need to invest funds in advance, and customers can be "charged" through the consumption (bandwidth usage) of VLB instances, which is convenient and flexible for on-demand use, on-demand deployment, on-demand and on-demand.

on-demand deploymentADC can perfectly match the application service delivery structure in the private cloud. Each application service model can have a separate ADC. ADC templates can be configured in a pre-made way or by migrating/copying existing deployment configurations.

1. 3. cormorantCMS Deployment Capabilities
      1. automatic configuration

cormorantCMS automatically (manually) deploys VLB (stand-alone or HA mode) outside the K8S cluster, so that each service to be published in the corresponding K8S cluster can have its own exclusive ADC,

cormorantCMS supports the monitoring and management of ADC in VMWare EXSi/vCenter/KVM environment. It can refine and customize the management, customize the configuration file of ADC (support single VLB and HA VLB), prefabricate templating, template copy and template migration, and support hot configuration for immediate effect.

50. management configuration:

50. ADC customization:

50. Automated Deployment& Authorization (ESXI):

1. 1. 2. Manual Configuration

cormorantCMS supports the monitoring and management of ADC in VMWare EXSi/vCenter/KVM environment. You can refine and customize the management and customize the configuration file of ADC (single VLB and HA VLB are supported).

definedADC can generate image files and support download, manual configuration can also be done at any time, as a supplement to automatic configuration.

1. 4. Application Template Deployment

cormorantCMS supports application template deployment on VLB instances. For application template deployment, you can use template version control to enable VLB configurationAdapt to the flexibility requirements of the application business development cycle., cormorantsCMS can centrally control all managed hardware/VLB instances.

1. 1. 1. Application Template Import

application template can be a pre-made dedicated template, or it can be used.VS configuration as a template.

1. from cormorantsCMS Import Private VS Configuration Template to VLB

2. from existingVS Configuration Import Template

1. 1. 2. Application Configuration
1. application configuration mappingADC Configuration

2. application configuration version control

application configuration version control adapts to the flexibility requirements of the application business development cycle, and supports flexible operations such as version iteration and rollback.

1. 1. 3. Application Configuration Deployment

application configurations to hardware/VLB instance.

By applying a template, you can configurethe actual VS configuration released by ADC, including VIP, port, RS pool, etc. After importing the template, you can directly configure and deploy the application. At the same time, the cormorant CMS system will automatically record for version control, and version replacement can be completed after "COMMIT" after configuration.

1. 1. 4. Application Configuration History

application configuration history can be used for auditing purposes.

1. 5. CMS Centralized Management

in cormorantsCMS, you can perform centralized management of hardware/VLB instance nodes.

lcommon operations include hardware/VLB instanceFirmware Upgrade,Configuration Backup/Restore(Full Backup/Restore),Restart/Shutdown Nodesand so on.

1. 6. Multi-Tenant Management

cormorantCMS can be assigned to different user groups to manage tenants, groups, and permissions.

2. cormorantCMS - Kubernetes
   1. entrance control

cormorant loadKubernetes an external ingress controller, works in a single-tier topology, and does not require any form of agent to be installed in the K8S cluster.

cormorant loads can passK8S API automatically recognizes the configuration of the adaptation K8S in real time, including service changes, POD status, and POD changes (add/delete).

Cormorant load supports two modes to implement the function:

50. lIngress: This is the traditional mode. Like NGINX/HAProxy working mode, VS and POD (RS mapped to load) are dynamically generated by synchronizing with K8S Ingress objects only for HTTP applications.
50. lService: This is our unique feature, Service object synchronization for K8S, supporting all four-layer to seven-layer applications.
    2. Application Release Mode
       1. Ingress mode

throughYAML configuration file, inK8S.

1. 1. 2. Service mode

throughYAML profiles, publishing in K8SClusterIP Services, and markAPADCK8S: Enabled AnnotationsandexistingVS ID.

1. 1. 3. Ingress mode and Service mode

	Ingressmode	Servicemode
advantage	VS/Ingress rules are automatically added	streamlined load balancing inKubernetes; only needVS ID is controlled, DevOps does not require knowledge of load configuration. If VS ID does not change (NetOps is easy to control), only DevOps makes changes on VS IP/Port, it is transparent to DevOps operation; nonhttp(s) service support;
Disadvantages	double load overhead, as both the ingress and cormorant loads are inKubernetes; there is overlap between DevOps and NetOps. As shown above, DevOps needs to know the VIP/VS port/protocol to publish services through the cormorant load; whenVIP/VS port changes, DevOps must publish comments to the Kubernetes accordingly; onlyhttp(s) service support;	vs must pre-exist

1. 3. Network Connection
      1. POD CIDR Connection

using an external ingress controller is throughhow the IP address of the Kubernetes node is routed to the POD network.

cormorant load supportVXLAN to solve problems between overlay and underlay networks.

ConfigurationVXLAN network:

1. inADC.

2. ineth1VXLAN.

%note that in this exampleVXLAN ID is the VNI of the peer (Linux vxlan0), which is 42 in this example. VTEP is the IP address of the network port of Linux, which is the IP address of ens33 in this example, 192.168.0.222 (not the IP 172.18.1.3 of Linux vxlan0).

3. in Load Newvxlan must be in the same segment as the IP address of the peer VNI.

4. Test connection on load (non-essential step)

1. 1. 2. automatic routing

cormorant load throughK8S API to analyze CNI usage and CIDR distribution, and automatically synchronize routing information to load devices, thus realizing automatic routing function, which can automatically arrange used routes.

Common SupportCNI includes, flannel, calico(bgp mode), weave.

3. Summary

cormorantCMS further templates ADC configuration and application configuration to quickly adapt to the challenges brought by new application services in private cloud platforms. Different from the traditional hardware mode, it is more flexible and convenient.

cormorantCMS can simultaneously provide and manage multiple agentless K8S portal controllers for publishing K8S services (whether HTTP or non-HTTP services), with comprehensive load balancing functions, including AAA, QoS, third-party (ELK, etc.) integration, etc.

cormorantCMS is responsible for centralized management, especially for large-scale cloud platform networking scenarios. With the powerful function and adaptability of the cormorant load itself, through the support of VXLAN technology, the communication problem between the overlay network and the underlay network can be solved, and the comprehensive load balancing capability with professional, perfect and powerful performance can be provided.