Automation
When migrating multiple servers, using the command line to run the AWS App2Container workflow is not a scalable solution. For example, manually managing and tracking the progress of each workflow can become overwhelming. The migration can be further complicated if the application server doesn’t have internet access or sufficient hardware resources, or if the Docker engine can’t be installed. If you manage servers by using Red Hat Ansible or Jenkins, you can use that tool to orchestrate the App2Container workflow.
Automation using Ansible
Ansible Playbook automates serial performance of tasks, monitoring migration progress
for each application, which reduces human intervention and eventually speeds up
migration. The playbook can be run from the worker machine or a proxy instance that can
communicate with both the application server and the worker machine. The playbook can
containerize multiple application servers in parallel. For more insight on how Ansible
can be used to automate the App2Container end to end workflow, see the Automate AWS App2Container workflow using Ansible
Automation using Jenkins
Using Jenkins, you can centralize control and manage modernization of multiple application servers. You can use the Jenkins user interface to visualize the App2Container workflow. Jenkins facilitates the integration of the existing continuous integration pipeline of the application to one that is created by App2Container.
