Cloudify's packager provides tools and configuration objects we use to build Cloudify's Management environments, agents and demo images.
Please see Bootstrapping using Docker for information on our transition from packages to container-based installations.
To generate our Dockerfile.template file, we're using Jocker.
packman configuration
Package based provisioning will be deprecated in Cloudify 3.2!
Packman is used to generate Cloudify's packages. This repository contains packman's configuration for creating the packages.
The package-configuration folder contains the init scripts and configuration files for Cloudify's management environment components.
The package-templates folder contains the bootstrap scripts that are used to install Cloudify's management environment.
The packages.py file is the base packman configuration file containing the configuration of the entire stack (including agents).
Cloudify's packages are created using vagrant VM's (currently on AWS).
The Vagrant folder contains vagrant configuration for different components that are generated using packman:
- A Vagrant VM is initialized.
- Packman is installed on the machine alongside its requirements.
- If a virtualenv is required, it is created and the relevant modules are installed in it.
- Packman is used to create the environment into which the components are retrieved.
- Packman is used to create the package.
NOTE: the Windows Agent Vagrantfile uses a premade image already containing the basic requirements for creating the Windows agent.
Create Vagrant box with Cloudify Manager installed for Virtualbox, AWS, HPCloud