Home - dewayneh/testing GitHub Wiki

CDP (Continuous Deployment Platform) is a framework and integration of many open-source tools and products to provide the complete development, construction, packaging, deployment, and monitoring of microServices.

 

CDP is:

An integration of multiple open-source products and tools, combined with AT&T developed tools, to provide:

  • The ability to rapidly generate a new microService using templates.
  • Standardized software development kits (SDK's) for specific languages and capabilities, including:
    • Spring Boot for JAX-RS-based RESTful services
    • Camunda for modeled workflows
  • Standard runtime management (Kubernetes) technologies for running the microServices
  • Build coordination and automation
  • A Kubernetes-based runtime for managing deployments of these Microservices.
  • The tools and utilities needed to setup the Kubernetes-based runtime on AIC, Amazon, and "bring your own" VMs and servers.
  • Runtime integration with monitoring and logging operational systems.
  • Security integration for ASPR compliance within AT&T.
  • Intra/inter-cluster discovery, routing, and failover.

 

CDP is not:

  • A cloud or cloud provider. It can utilize the cloud to host the microServices, and even CDP itself, but it is not required.
  • A business service. No business-specific capabilities are part of the platform. You can implement business-specific capabilities as microServices that are hosted on the platform.
  • Just CI/CD. While a perfect target platform for implementing a CI/CD pipeline, CDP includes template SDKs for building specific types of microServices, pre-integrated runtimes for any application to build microServices, and so forth.
  • A mobile device platform. While a mobile device application can utilize microServices hosted on an instance of CDP runtime, CDP itself does not run on mobile devices.
  • A customer premise device platform. While a customer-premise device can utilize microServices hosted on an instance of CDP, CDP itself does not run on-premise in the customer-facing device.
  • A VNF (Virtual Network Facility) platform. ECOMP is the target VNF platform for AT&T.

 

Attachments:

{width="8" height="8"} image2018-2-9 15:30:33.png (image/png)
{width="8" height="8"} image2018-1-17 9:46:29.png (image/png)
{width="8" height="8"} image2018-1-17 11:11:10.png (image/png)
{width="8" height="8"} event processing.png (image/png)
{width="8" height="8"} Heterogeneous Batch Refactoring.png (image/png)
{width="8" height="8"} testing1.png (image/png)
{width="8" height="8"} testing2.png (image/png)
{width="8" height="8"} code2flow_18cde.png (image/png)
{width="8" height="8"} token.PNG (image/png)
{width="8" height="8"} enfocer.PNG (image/png)
{width="8" height="8"} image2017-3-6 13:17:58.png (image/png)
{width="8" height="8"} image2017-3-6 13:24:56.png (image/png)
{width="8" height="8"} aafroutes.PNG (image/png)
{width="8" height="8"} aafroutes2.PNG (image/png)
{width="8" height="8"} userpermission.PNG (image/png)
{width="8" height="8"} image2018-1-5 12:45:53.png (image/png)
{width="8" height="8"} image2018-1-5 12:49:34.png (image/png)
{width="8" height="8"} helloprom.PNG (image/png)
{width="8" height="8"} exampleprom.PNG (image/png)
{width="8" height="8"} prom.PNG (image/png)
{width="8" height="8"} scrape.PNG (image/png)
{width="8" height="8"} k8sprom.PNG (image/png)
{width="8" height="8"} image2017-8-22 22_13_3.png (image/png)
{width="8" height="8"} image2017-8-23 9_11_44.png (image/png)
{width="8" height="8"} image2017-8-23 9_15_33.png (image/png)
{width="8" height="8"} image2017-9-1 15:30:34.png (image/png)
{width="8" height="8"} image2017-9-1 14:44:56.png (image/png)
{width="8" height="8"} 3configmaps.png (image/png)
{width="8" height="8"} image2017-11-16 10:16:44.png (image/png)
{width="8" height="8"} seedbundle.PNG (image/png)
{width="8" height="8"} configrole.PNG (image/png)
{width="8" height="8"} playbook.PNG (image/png)
{width="8" height="8"} image2018-1-24 14:27:4.png (image/png)