These blueprints demonstrate various methods for creating a virtual machine in different clouds.

For example, you may use the Cloudify node type for an AWS Instance in the aws.yaml or use a Cloud Formation template in aws-cloudformation.yaml.

If you have already ensured these requirements are met, skip to installation steps.

• You will need a Cloudify Manager v5.0.5 or higher. See install Cloudify Manager.

• You must install the following plugins on your Cloudify Manager, however you may skip the Cloud plugin if the Cloud is not relevant to you.

  • cloudify-aws-plugin, version 2.3.0 or higher, see releases.
  • cloudify-azure-plugin, version 2.1.7 or higher, see releases.
  • cloudify-gcp-plugin, version 1.4.4 or higher, see releases.
  • cloudify-openstack-plugin, version 3.2.2 or higher, see releases.
  • cloudify-utilites-plugin, version 1.22.1 or higher, see releases.
  • cloudify-fabric-plugin, version 1.5.3 or higher, see releases.

To learn how to upload plugins, see uploading plugins.

• You must create the following secrets, however, you may skip those cloud secrets that are not for your cloud.

  • If you wish to use AWS, please create the required AWS secrets.
  • If you wish to use Azure, please create the required Azure secrets.
  • If you wish to use GCP, please create the required GCP secrets.
  • If you wish to use Openstack, please create the required Openstack secrets.

To learn how to create secrets, see creating secrets.

First you will need to make sure that you have the latest getting-started blueprint. These are located at Blueprint Examples Releases. Look for the zip archive with a name similar to getting-started-5.0.5-24.zip. Copy the link URL. You will need it to complete these steps.

There are two methods to install the getting started application:

1. Install getting started with the CLI.
2. Install getting started with the UI.

Upload the blueprint to you Cloudify Manager with the following command:

cfy blueprints upload [BLUEPRINT URL] -b [BLUEPRINT ID]

You can provide any ID you like for the blueprint. You will need it in the following steps.

Create the deployment on your Cloudify Manager with the following command:

cfy deployments create -b [BLUEPRINT ID]

Execute the install workflow on your deployment:

cfy executions start install -d [BLUEPRINT ID]

If you have Docker, you can install a Cloudify Manager with the following command:

sudo docker run --name cfy_manager_local -d --restart unless-stopped -v /sys/fs/cgroup:/sys/fs/cgroup:ro --tmpfs /run --tmpfs /run/lock --security-opt seccomp:unconfined --cap-add SYS_ADMIN -p 80:80 -p 8000:8000 cloudifyplatform/community-cloudify-manager-aio

There are two methods to upload a plugin on your Cloudify manager:

1. Uploading plugins with the Cloudify CLI.
2. Uploading plugins with the Cloudify UI.

Return to requirements.

If you know the path or URL of the Cloudify Plugin Wagon and Plugin YAML, then you may run the following command:

cfy plugins upload [URL OR PATH TO PLUGIN WAGON] -y [URL OR PATH TO PLUGIN YAML]

Select System Resources from the menu on the left.

Find the Plugins widget. By default, this is the first widget on the system resources page.

Click on Upload.

Paste the URL of a plugin wagon in the Wagon file field.

Paste the URL of the plugin YAML in the YAML file field.

Click Upload.

There are two methods to create a secret on your Cloudify manager:

1. Create secrets with the Cloudify CLI.
2. Create secrets with the Cloudify UI.

Return to requirements.

You can create secrets with the following CLI commands.

If the secret content is a string:

cfy secrets create [SECRET NAME] -s [SECRET CONTENT]

If the secret content is in a file, for example if the secret is a RSA key:

cfy secrets create [SECRET NAME] -f [PATH TO FILE CONTAINING SECRET CONTENT]

Select System Resources from the menu on the left.

Find the Plugins widget. By default, this is the first widget on the system resources page.

Click on Secrets.

Provide the secret key in the Secret key field.

Provide the secret value in the Secret value field. Alternately, provide a local file path in the Get secret value from file menu.

Click Create.

If you are an AWS user, you must create the following secrets:

• aws_access_key_id AWS Access Key, e.g.: cfy secrets create -u aws_access_key_id -s ....................
• aws_secret_access_key: AWS Secret Access Key, e.g.: cfy secrets create -u aws_secret_access_key -s ....................

If you need help locating your credentials, read about AWS Access Key.

Return to requirements.

If you are an Azure user, you must create the following secrets:

• azure_subscription_id: Azure subscription ID: cfy secrets create -u azure_subscription_id -s 00000000-0000-0000-0000-000000000000.
• azure_tenant_id: Azure subscription ID: cfy secrets create -u azure_tenant_id -s 00000000-0000-0000-0000-000000000000.
• azure_client_id: Azure subscription ID: cfy secrets create -u azure_client_id -s 00000000-0000-0000-0000-000000000000.
• azure_client_secret: Azure subscription ID: cfy secrets create -u azure_client_secret -s ............
• azure_location: Azure subscription ID: cfy secrets create -u azure_location -s westeurope.

If you need help locating your credentials, read about Azure Plugin Configuration:

Return to requirements.

If you are a GCP user, you must create the following secrets:

• gcp_credentials: A GCP service account key in JSON format. Hint: Create this secret from a file:

`cfy secrets create gcp_credentials -f ./path/to/JSON key`.

If you need help locating your credentials, read about GCP Plugin Configuration.

Return to requirements.

If you are an Openstack user, you must create the following secrets:

• openstack_auth_url: Openstack Auth URL: cfy secrets create -u openstack_auth_url -s https://my.openstack.com:5000/v3
• openstack_tenant_name: Openstack Tenant Name: cfy secrets create -u openstack_tenant_name -s tenant
• openstack_username: Openstack Username: cfy secrets create -u openstack_username -s janedoe
• openstack_password: Openstack Password: cfy secrets create -u openstack_password -s peacelove
• openstack_region: Openstack Region Name: cfy secrets create -u openstack_region -s RegionOne
• openstack_external_network: The ID of the floating IP network that you will use to connect to the internet.
• base_image_id: The image ID of a Centos 7 that supports Cloud Init.
• openstack_user_domain_name: OS_USER_DOMAIN_NAME as specified in Openstack RC file, most of the time this value is "default".
• openstack_project_domain_name: openstack project domain name, most of the time this value is "default".

If you need help locating your credentials, read about Openstack RC File, although sourcing is not enough, these values must be created as secrets:

Return to requirements.

Notes:

1. Use v3 authentication url.

2. If v2 authentication url used, remove user_domain_name and project_domain_name from client_config.