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 Management Console, or send them to others. Single YAML file blueprints Cloudify Management Console supports single YAML file blueprints.
Overview of Cloudify Plugins
The Cloudify Management Console provides a streamlined experience for managing and analyzing your applications. It requires a Cloudify Manager to run. In addition to being able to upload blueprints, create deployments and execute workflows, the interface provides log and events views, application and network topology visualization, and more. It provides most features available in the command-line interface and more. Getting Started Cloudify Manager supports user management, so users must log in with user credentials.
Workflow and Execution Parameters Workflows can have parameters. Workflow parameters are declared in the blueprint, and each parameter can be declared as either mandatory or optional with a default value. To learn more about parameter declaration please refer to Creating your own workflow. Viewing a workflow’s parameters can be done in the CLI using the following command: cfy workflows get my_workflow -d my_deployment This command shows information on the my_workflow workflow of the my_deployment deployment, including the workflow’s mandatory parameters as well as the optional parameters and their default values.
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.