Orchestration Using CloudScript
Contents
Overview
CloudScript is a new paradigm for programmable control of your cloud infrastructure. Much like a programming language needs IDEs, build tools, and version control, CloudScript has additional systems to make it a useful tool for team collaboration. In the cloud these suites of tools are referred to as Orchestration. And, in this guide you will learn about some of the tools that support CloudScript development including an IDE, projects, templates, jobs, and callbacks.
CloudScript IDE
To make development of your CloudScript easy we have included an IDE interface in the customer portal where you can edit your project files, including CloudScript, but also any other languages you want to include in your infrastructure code base, such as Shell, Puppet, Chef, or even Ruby, Java, and Python.
Projects
A project is a collection of scripts, recipes, and includes the execution history of the CloudScript for the project. To create a new project select the New option under Project.
Templates
A template is a project based on a pre-configured CloudScript provided by NephoScale to install an application stack on one or more servers. To create a new template select the Template option under Project. You will then select a template from the list of available options.
Running the Project
Once the project has been created, you must run it. Within the CloudScript IDE, click the scripts tab underneath the project and press run.
Your portal will notify you with a run result when the project has been run. To see the progress of your CloudScript and the resulting jobs click the Job Manager button arrow on the right side of the portal.
Your run result will include any passwords, usernames, and information needed to finish configuration of your application stack
Once the run result tab has been closed, you can access that same information under that template within orchestration by opening its history tab.
Callbacks
If you are writing your own CloudScript or are interested in the output of the scripts run as part of the recipe, then go to the Callback section under the Orchestration tab to see the output of the scripts that were run on the server.
Post Installation Steps
Post installation steps vary depending on template. We've included brief descriptions within each cloudscript template guide if more configuration is necessary. For more in-depth configuration and trouble shooting information, you should look to each program's documentation and support. In the case of CMS templates (Drupal, Joomla, and WordPress), you will now have a live website.