Uploading a Blueprint

As a first step a blueprint should be uploaded to the Conductor Manager. Deployment services and deployment environments are spinned up from uploaded blueprints.

The blueprint can be uploaded to the Conductor Manager with Conductor CLI, Conductor Management Console, or Conductor API.

The blueprint can be provided as an archive, or a link to github site, or just a YAML file.

Single blueprint YAML file can be uploaded without packaging them through the Conductor Management Console.

Uploading a blueprint from Blueprints marketplace

1. On the Blueprints page click Upload button and choose Upload from Marketplace option.
2. On the Marketplace select a blueprint and click to the “Upload blueprint” button. After this the blueprint will be uploaded and the service create wizard will be opened.

Uploading a Blueprint using the Conductor Management Console

Supported archive formats: TAR, TAR.GZ, TAR.BZ2, ZIP

1. On the Blueprints page click Upload button and choose Upload a blueprint package option.
2. Select a blueprint package from a local folder or providing URL to the archive.
3. Enter an unique name for the blueprint. For example, you can upload one instance of the blueprint as blueprint-template and another instance as a blueprint-with-input.
4. Select the YAML filename of the blueprint. This field refers to the .yaml file that contains the application topology.
5. Click Upload to upload the blueprint package.

Uploading a Blueprint using the Conductor CLI

The Conductor CLI allows to upload packaged blueprints and unpackaged blueprints.

The blueprint uploading command examples

The packaged blueprint:

cfy blueprints upload -b BLUEPRINT_ID -n BLUEPRINT_FILENAME PATH_OR_URL_OF_BLUEPRINT_PACKAGE

The unpackaged blueprint:

cfy blueprint upload -b BLUEPRINT_ID BLUEPRINT_FILENAME

Additional examples:

The cloudify-nodecellar-example from GitHub:

1. Download the cloudify-nodecellar-example as a ZIP file.
2. Enter the command for your IaaS:

OpenStack

  cfy blueprints upload -b nodecellar -n openstack-blueprint.yaml PATH_OR_URL_OF_BLUEPRINT_ARCHIVE
  

SoftLayer

  cfy blueprints upload -b nodecellar -n softlayer-blueprint.yaml PATH_OR_URL_OF_BLUEPRINT_ARCHIVE
  

Amazon Web Service

  cfy blueprints upload -b nodecellar -n aws-ec2-blueprint.yaml PATH_OR_URL_OF_BLUEPRINT_ARCHIVE
  

vCloud

  cfy blueprints upload -b nodecellar -n vcloud-blueprint.yaml PATH_OR_URL_OF_BLUEPRINT_ARCHIVE
  

The -b flag assigns a unique name to the blueprint on Conductor Manager.

You can navigate to the Conductor Manager URL and see the nodecellar blueprint in your list of blueprints.

Click the blueprint to view its topology. A topology consists of elements called nodes. The nodecellar example, includes these nodes:

• Two VMs (one for MongoDB and one for Node.js)
• A Node.js server
• A MongoDB database
• A Node.js application called nodecellar (A sample Node.js application)

Next Steps

You can now deploy your blueprint.