Additional Information

Manually Setting up Configuration Manager

Although Configuration Manager enables you to use specific commands in order to automatically set up repositories and specify your environments respectively, you can also do it manually if you prefer. This requires you to manually create the file structure that is needed, and so, it is recommended that you only perform a manual setup if you are more familiar with the tool.

There are a number of steps that you must carry out. First of all, you will receive the Configuration Manager package via your preferred method of delivery. This package will contain:

  • The .jar file
  • The miocm-config.yml file
  • The environment.yml file.
  1. Copy both the .jar file and the miocm-config.yml file into your local home directory. Example: In Windows: C:\Users\<<Username>>. Below is the format for the miocm-config.yml file:

    • default Path: C:\miocm_repos
    • default Repository: defaultRepository: mio-Dev-REPO-01
  2. Next you must create a working directory in which Configuration Manager will store Ooyala Flex environment configurations, change sets, and logs.

Manually Setting up the Repository

Inside your C:/ drive, create the following folder structure:

Notes:

  • You can have any number of environments, within any number of repositories. In the example above, we have shown what the folder structure would look like if you had one repository with only two environments.
  • You can use any other path and repository, but you must update the miocm-config.yml file in order for Configuration Manager to work.

A. Root Folder: This folder represents a workspace in which to manage one or more repositories.

B. Repository: As previously mentioned, you can have multiple repositories. Within each repository you can have two or more environments depending on your needs.

C. Source Environment: This folder represents your source environment. You can make changes and then pull configuration from the source environment.

D. Target Environment: This folder represents the target environment. You can pull configuration from the source environment and apply it to the target environment.

E. environment.yml for Source Environment: This is a .yml file that you place inside your the source environment folder. This must be configured with the details of your source environment, These details are as follows:

  • Endpoint: e.g. myenvironment.ooyala.com/api
  • Password: The password you use to login to the environment
  • Name: The name of your environment e.g. my_source_env
  • UUID: e.g. c4a1ea01-f42d-4683-8aeb-1cdfdbdf716e
  • Username: The username you use to login to the environment

F. environment.yml for Target Environment: This is a .yml file that you place inside your the target environment folder. This must be configured with the details of your target environment. These details are as follows:

  • Endpoint: For example: myenvironment.ooyala.com/api
  • Password: The password you use to login to the environment
  • Name: The name of your environment e.g. my_source_env
  • UUID: e.g. c4a1ea01-f42d-4683-8aeb-1cdfdbdf716e
  • Username: The username you use to login to the environment

Configure each environment manually by opening the enviroment.yml files in a text editor, and adjust the details accordingly. The configuration of the environment .yml files should be as follows:

Once you apply this configuration to the environment .yml files, you will have a repository with two environments.