Setting Up Configuration Manager

Setting up a Repository

For each environment you are going to connect to, Configuration Manager will need a folder containing the configuration, to connect to this environment in your Configuration Manager repository.

Depending on the change request, the source and target environments are interchangeable. When you go to make a specific change request, you can specify which environment is the source, and which is the target.

To set up the working directory

  1. Run the following command: repository --defaultPath <absolute_dir> --defaultRepository <name_of_repository>. This will create the folder and produce a miocm-config.yml file in ~/miocm-config.yml (this is the home directory).

  2. When the repository has been created, you will see a confirmation message which reads Repository created, as shown in the example below:

Configuration Manager will store Ooyala Flex environment configurations, change sets, and logs in your repository.

Creating an Environment Structure Inside the Repository

Next, you will need to set up an environment structure inside your repository. This means you will need to specify a source environment and a target environment.

  1. Run the following command: environment --envname <name_of_environment> --endpoint <endpoint> --username <username> --password <password>

  2. If the command has been run successfully, you should see the following response: Environment created: Environment(name=my_source_env, uuid=12dafb34-5678-9123-4d5c-be6ef7ab89b1, dirName=C:\my_new_repo,, username=mypassword, password=myusername, hostHeaderParam=null, isReady=true)

  3. Now, a folder will be created in your repository for each environment you have specified. In the example below, you can see a folder for a source environment, and one for a target environment.

  4. Each environment folder will have a .yml file inside. This .yml file will contain the information for that specific environment. This information in each .yml file can be altered at any time, simply by opening it in a text editor.

The information in each .yml file must be accurate. For example, if the password for one of your environments you are using changes, you must open the .yml file associated with that environment, and update that piece of information.