Key Concepts






Edit this page on GitHub

Home > user > transition > Create an Environment

Create an Environment

An Environment captures your operational requirements for an instance of your Assembly. Examples of Environments are dev, qa, or prod environments. Because all environments use the same base application model, the overall effort to maintain all of the environments is minimized.


To create an environment, follow these steps:

  1. Go to the assembly.
  2. In the Transition phase, click create environment.
  3. Select the appropriate environment profile
  4. Click New Environment.

  5. Enter the properties for the new environment.

  6. Include the following:
    • Environment name that is unique to your Assembly
    • Description
    • Administrative Status from the options listed below.
      • Provision: Environment is under provisioning state
      • Active: Environment is up and serving production traffic
      • Inactive: Environment is up however doesn’t serve production traffic
      • Decommission: Environment is no longer in use and can be removed.
    • Continuous Deployment: Not in use
    • DNS
      • DNS Subdomain: Makes the environment unique
      • Global DNS: If checked, creates the GLB

    For a new environment, “Provision” is the correct status value. Other values should be used after the environment is created and functioning. This status value is used only for administrative purpose by NOC or OneOps admins to understand the state of the environment.

  7. Configure the availability.
    • Availability mode:
      • Single: Generates an environment without load balancers, clusters, etc.
      • Redundant: Inserts and configures clusters, load balancers, rings, etc., depending on what the best practice is for each platform.
      • High-Availability: Adds multi-provider or multi-region to a redundant environment. Availability can only be changed when creating the environment.

  8. Select one or more primary and secondary clouds from the list of available options.

    Debug should not be used by users. It is used to debug OpenStack issues.

  9. To save the environment, click Save.

    A new Environment manifest is generated and the Environment details page is shown.

  10. Review the changes, which are now a set of add Actions.
  11. Click Commit and Deploy.

    The deployment plan is generated.

  12. Review the deployment steps and then click Deploy.