diff --git a/QoDProvisioning/README.md b/QoDProvisioning/README.md index 0b395f203578d5c7390fbedd79ad3ab838abd177..e7e162c33faa989aae66fa9d7eb99f722696af1f 100644 --- a/QoDProvisioning/README.md +++ b/QoDProvisioning/README.md @@ -228,10 +228,10 @@ If everything went ok, you should have a new CRD in your Kubernetes cluster. Run Before designing the service in OSL, let us first create a CR of type `CAMARAaaS-QoDProvisiongAPI` to validate that the operator is behaving according to what is expected. To this end, you may use the test custom resource available at `/QoDProvisioningAPI/Operator/test-cr.yaml` . Before creating the resource, you need to update the fields: *spec.messageBroker.address*, *spec.messageBroker.port, spec.messageBroker.username, spec.messageBroker.password*, with the values that relate with your OSL instance. The default values will be the following ones: -- *spec.messageBroker.address: <your OSL address>* -- *pec.messageBroker.port*: 61613 -- *spec.messageBroker.username: artemis* -- *spec.messageBroker.password: artemis* +- *spec.messageBroker.address:* <your OSL address> +- *spec.messageBroker.port*: 61613 +- *spec.messageBroker.username*: artemis +- *spec.messageBroker.password*: artemis For now, you do not need to update the field serviceUnderControl.uuid. You may leave it as is.