phdata-logo Docs About phData
Quick Start

Cloud Foundation Quickstart #

Overview #

This document contains quickstart instructions for learning, testing, and demonstration of phData Cloud Foundation tool. Before you get started please refer to the Cloud Foundation overview at cloudfoundation. This document helps our customers better understand the phData Cloud Foundation tool.

Note that in a production setting, you will need to make minor changes to the configuration which allows you to use phData gold templates (infrastructure patterns developed by phData)

Prerequisites #

To configure and allow the tool to operate in a given aws environment, a set of instrutions are required which are just onetime activity. Please follow the instructions provided on the page prerequisites

Cloud Foundation Provisioning Demo #

Once the prerequisites are completed, follow the below instruction to run the Cloud Foundation.

  1. Create a branch for Cloud Foundation template repository that you cloned from phData github account.
  2. In the deployment descriptor file(deployment.yaml) move the below entry from undeploy section to deploy section.
    { name: s3bucket1.yaml, phdata_gold_template: true, version: 1.1.1, deploy_env: [all] }
  3. Create a merge request/pull request depending on your source control system.
  4. Since plan_all attribute is set to true in your buildspec file, Cloud Foundation generates the DEPLOY PLAN (execution plan) for all environments defined in your deployment descriptor. The DEPLOY plan is posted to your merge request as a comment (takes 3 to 4 minutes)
  5. After reviewing the DEPLOY PLAN, merge the merge-request.
  6. Now the change is deployed in your first environment and the DEPLOY SUMMARY is posted back as a comment. Also the DEPLOY PLAN is generated for next environment defined in your deployment descriptor.
  7. Also, your next environment(Prod) waits for manual approval, the approval link is available in the comment.
  8. Go to the approval link and approve the change.
  9. Now the change is deployed in the PROD environment, and the DEPLOY SUMMARY is posted back as a comment.