Lifecycle Manager: Cloning Configuration Profiles

Problem

Introduction

Sometimes, you may need to clone a configuration profile in Lifecycle Manager. This is useful when you want to update the DSE version during manual upgrades or create variations of an existing configuration without modifying the original. Support for cloning configuration profiles was completed in OPSC-6428 and is available in OpsCenter 6.5.0 or later. However, if you use OpsCenter 6.1.x or older versions, you must clone configuration profiles manually.

OpsCenter 6.5.0 and Greater

For instructions on cloning configuration profiles automatically, see the OpsCenter documentation at https://docs.datastax.com/en/opscenter/6.5/opsc/LCM/opscLCMcloneConfigProfile.html

OpsCenter 6.1.x and Lower

Graphical Method

If you know all the settings you wish to modify, creating a new configuration profile in the web interface is a viable method of cloning and is the easiest method to occasionally clone a configuration profile containing only a few customized settings.

API Method

If you don't remember all the settings you wish to customize, if there are many of them, or if you want to automate the cloning process because you do it frequently, the API is the best method to clone configuration profiles. The steps below will demonstrate how to clone configuration profiles using the command-line tool 'curl', though any http client that can craft GET and POST requests can be used. Piping output through json_pp or another JSON formatter is optional but can make reading and editing the JSON content much easier.

1. Fetch the list of available configuration profiles: curl 127.0.0.1:8888/api/v1/lcm/config_profiles | json_pp
2. Identify the configuration profile that you wish to migrate by examining the "name" field of each entry in the list.
3. Identify the URL to the configuration profile that you wish to migrate by examining the "href" field of the relevant entry in the list.
4. Using the URL from step-3, download the configuration profile in it's entirety to the local file "cp-migrate.json": curl http://127.0.0.1:8888/api/v1/lcm/config_profiles/f177c211-7ebd-4dd9-a6e… | json_pp > cp-migrate.json
5. Edit cp-migrate.json using the editor of your choice:
   1. Remove the href, type, id, and related_resources fields.
   2. Update the "name" field so that it does not conflict when any existing configuration profiles.
   3. Optionally, update the 'datastax-version' field, which cannot be edited once the configuration profile is added to Lifecycle Manager.
   4. Optionally, add/update/remove other fields that you wish to change. Note that for fields other than 'datastax-version', you can also update them using the web-interface after adding the configuration-profile.
6. Add the new configuration profile to LCM: curl -X POST -d @cp-migrate.json http://127.0.0.1:8888/api/v1/lcm/config_profiles/
7. Edit your clusters, datacenters, or node to use the new configuration profile.

At this point, the new configuration profile is available in the web-interface and may be managed as you would any other configuration profile.

Last Reviewed Date: 2023/12/12