Working with Cloudify
Packaging a Blueprint A blueprint can contain multiple files. These files can reside under a single directory with subdirectories or in an archive. Although the Cloudify CLI can manage the archiving process for you during upload, you might want to create archives prior to uploading the blueprint, so that you can keep them in a fileserver, upload them via the Cloudify Console, or send them to others. Single YAML file blueprints Cloudify Console supports single YAML file blueprints.
Overview of Cloudify Plugins
The Cloudify Console provides a streamlined experience for managing and analyzing your applications. In addition to being able to upload blueprints, create deployments and execute workflows, the interface provides metrics visualization, log and events views, application and network topology visualization, and more. To view a video about the functionalities of the Cloudify Manager user interface click here. The Cloudify Console requires a Cloudify Manager to run. It provides most features available in the command-line interface and more.
Workflows are automation process algorithms. They describe the flow of the automation by determining which tasks will be executed and when. A task may be an operation (implemented by a plugin), or other actions including running arbitrary code. Workflows are written in Python, using a dedicated framework and APIs. Workflows are deployment-specific. Each deployment has its own set of workflows, which are declared in the Blueprint. Executions of a workflow are in the context of that deployment.
Introduction Applications, network services and most software solutions are typically composed of multiple components. These may be cloud-native micro-services or simply smaller scale services leveraged by the overarching service to create a composite solution. Typically there are two types of such services: A shared resource, is a service used by multiple other services, for example a database which is leveraged by multiple applications. The shared resource is usually an existing entity and deployment of the application service will not provision the shared resource, it will only interact with it.
Cloudify provides integration with various CI/CD platforms. Jenkins Plugin Introduction to Jenkins' Cloudify integration GitHub Actions Introduction to Cloudify's GitHub Actions CircleCI Introduction to Cloudify's CircleCI Integration The cli Docker Image With the exception of Jenkins, the integration between CI/CD tools and Cloudify is encapsulated in a Docker image. The Docker image contains the standard Cloudify CLI, as well as a wrapper script (called cfyci) that provides a few shortcuts and sugaring for simplified Cloudify access.