Roadmap about migration of public services into the cloudA step by step roadmap for Public Authorities to help them as they plan, determine effort and budget, select the appropriate services, make the required internal organisational changes and finally execute the migration into cloud.
The next step in the migration process is the deployment in the new environment. Depending on the type of workload being considered and the type of target cloud environment chosen, migration might be moving from the non-cloud environment to the cloud environment, cross-platform migration or application only migration (Writer, 2013).
During the migration process considerations arise with regards to privacy, interoperability, data integrity, data application portability and security which may cause a high level of complexity. Over the last years a large numer of online tools and services help to simplify this process.
Automated tools can help design the cloud environment and plan the migration. Such tools may be of general purpose or application specific. Most common are automated tools that help setting up the replication of Virtual Machines from on-premises installations to the cloud. For example, automatic deployment can be implemented using OpenStack Heat, the “orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code”. The aim of orchestration is to create a human -and machine- accessible service for managing the entire lifecycle of infrastructure and applications within the SCP Cloud environment.
MAIN STEPS FOR AUTOMATING THE DEPLOYMENT OF SERVICES TO THE CLOUD USING HEAT
The main steps needed for automating the deployment of services to the cloud are presented below.
- Step 1: Automate software installation and configuration. Before the automation process bash shell scripts should be implemented to a) configure the VM hosting the application and b) install and configure the application and its dependencies. This is a necessary step as it will ensure that the bash scripts are working properly before moving into creating the Heat template. This way we reduce the complexity of having to identify what went wrong in case the deployment was unsuccessful.
- Step 2: Integrate with Heat and execute the template. Create Heat scripts, using the Heat template format that describe the infrastructure (servers, floating IPs, security groups, ports) of the cloud applications, integrating the software installation and configuration scripts made at the previous step.
- Step 3: Validation. Validation of the automation process includes functional tests in order to ensure that the deployed application performs as designed.