Integrating with the CenturyLink Cloud Blueprints orchestration engine enables customers to deploy your software on their existing servers or to create the workflow for a complex multi-server/multi-service solution suite. This integration format provides a unified deployment experience for users and is the preferred integration method when available.
Reference the following key pages from the CenturyLink Cloud Knowledge Base:
- Blueprints Category in the Knowledge Base
- Best Practices in Packages and Blueprints
- Package and Blueprint maximums
- Naming conventions for Public Packages and Blueprints
- How to Build a Blueprint
- bpformation - CLI and Python SDK used for managing Blueprints and Packages. Easily and repeatably import, export, and update using a json object file as the authoritative representation of your Blueprint in lieu of using the web-based control portal
- Blueprint Package Manifest Builder Wizard (KB Instructions for use)
- CenturyLink Cloud Ecosystem Github Repo containing reference patterns, support tools, and the actual packages used in some of our public Blueprints
- Blueprint Broker is a cross-platform toolset that includes a discovery service, encrypted key-value store to maintain state, and a mailer tool enabling high-impact post-deployment communication
Blueprint QA Process Requirements
Before a Blueprint can be publicly published it must pass a CenturyLink led QA process which reviews functionality, compliance, and documentation:
- QA analyst can deploy without errors.
- Deployment user experience in line with customer expectations
- Any new servers deployed as part of the Blueprint must be be fully patched before release. Blueprint packages exist for Linux and Windows to support this.
- Allocates public IP address only if public access is required. Default access mechanism is via private IP (using client/remote VPN or other direct connect method).
- Some integrations may require reviews from Security, Commercial Compliance, or other subject matter experts
- Naming adheres to the Naming conventions for Public Packages and Blueprints style guide.
- Knowedgebase article content provides the information necessary to successfully deploy and get started with the solution. Links to more in-depth general documentation or CenturyLink Cloud specific language is encouraged.
- Documentation supports deployment experience
Ongoing Blueprints QA
CenturyLink customers trust that all services available as part of the Marketplace Provider Program
will deploy and function as expected. To that end CenturyLink maintains quality throughout the Marketplace by executring an ongoing testing service
that validates successful deployment and operation of all public Blueprints on a regular basis.