Obtain the MSR license¶
After you install MSR, download your new MSR license and apply it using a Helm command.
Warning
Users are not authorized to run MSR without a valid license. For more information, refer to Mirantis Agreements and Terms.
Download your MSR license¶
Note
If you do not have the CloudCare Portal welcome email, contact your designated administrator.
Log in to the Mirantis CloudCare Portal.
In the top navigation bar, click Environments.
Click the Environment Name associated with the license you want to download.
Scroll down to Licenses and click the License File URL. A new tab opens in your browser.
Click View file to download your license file.
Update your license settings¶
The procedure for updating your MSR license differs, depending on whether you are deploying the software with Kubernetes or Swarm.
Kubernetes deployments¶
Insert the contents of your MSR license in the
license
field of your custom resource definition manifest:spec: license: '<license-string>'
Apply the changes to the custom resource:
kubectl apply -f cr-sample-manifest.yaml
Verify completion of the reconciliation process for the custom resource:
kubectl get msrs.msr.mirantis.com kubectl get rethinkdbs.rethinkdb.com
Apply your MSR license to an unlicensed MSR instance:
helm upgrade msr msr --repo https://registry.mirantis.com/charts/msr/msr \
--version 1.0.0 \
--set-file license=path/to/file/license.lic
Swarm deployments¶
SSH into a manager node on the Swarm cluster on which MSR is running.
Insert your license information into the
license
section of yourvalues.yaml
file:license: '<license-string>'
Obtain a list of non-manager nodes along with their node IDs, noting the IDs of the nodes on which MSR is installed:
docker node ls --format "{{ .ID }}" --filter "role=worker"
Upgrade MSR, specifying a node ID for each node on which MSR is installed:
docker run \ --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ -v <path-to-values.yml>:/config/values.yml \ registry.mirantis.com/msr/msr-installer:<new-msr-version> \ apply \ --node <node-id>
Note
For MSR 3.1.4 or earlier, use the upgrade command instead of the apply command.
Review the status of the deployed services:
docker stack services msr