Deployment

Provided Makefile offers various targets to automate the standalone and advanced, Cloudify Manager serviced, deployment. You nearly don't need to directly deal with the Cloudify CLI (cfy). If all requirements are met, the deploy is just one simple command.

Access to the gromacs portal repository

The deployment includes checkout of the gromacs portal repository. Make sure you are granted access and that a registered ssh key is used.

Eventually, a clone of the portal repository can be injected as resources/gromacs-portal.

Standalone

Note: If x509 VOMS authentication is used, you need to have a valid certificate in the path specified by occi_user_cred in the inputs file.

• make cfy-deploy - deploy portal environment
• make cfy-undeploy - destroy portal environment

On successful deployment, you get a JSON structure with the Gromacs portal endpoint by running:

• make cfy-outputs

Advanced (Cloudify Manager)

First, you need to specify the Cloudify Manager server:

without security

cfy use -t myhost.mydomain.com

secured Cloudify Manager

export CLOUDIFY_USERNAME='admin'
export CLOUDIFY_PASSWORD='put configured password'
export CLOUDIFY_SSL_TRUST_ALL=true    # only in case self-signed certificate is used for web/API

cfy use -t myhost.mydomain.com --port 443

Note: If x509 VOMS authentication is used, you need to have a valid certificate in the path specified by occi_user_cred in the inputs file on Cloudify Manager host not only for initial deploy but all time while the deployment is alive!

• make cfm-deploy - deploy portal environment
• make cfm-undeploy - destroy portal environment
• make cfm-scale-out - manually scale out worker nodes (+1)
• make cfm-scale-in - manually scale in worker nodes (-1)

On successful deployment, you get a JSON structure with the Gromacs portal endpoint by running:

• make cfm-outputs