diff --git a/ansible/roles/slat/README.md b/ansible/roles/slat/README.md index acbd1db7890842b84adc20fdeadd1937041bb59d..7099fae9bc41db611b8cad81bc7fe2a4a25a75c9 100644 --- a/ansible/roles/slat/README.md +++ b/ansible/roles/slat/README.md @@ -67,17 +67,17 @@ Once deployed, slat won't contain any sla, so one thing to do is to insert it ma 3. In order to complete the creation of a new SLA, you have to specify: -Â - Service: you can only choose from the services provided from the cmdb (to see which ones are available you can see the "Provider" section in the SLAT upper menu) + Â - Service: you can only choose from the services provided from the cmdb (to see which ones are available you can see the "Provider" section in the SLAT upper menu) -Â - Customer Group: the IAM group that allow to deploy in the choosen service (you must be part of that group to define a SLA for it). + Â - Customer Group: the IAM group that allow to deploy in the choosen service (you must be part of that group to define a SLA for it). -Â - Effective from: starting date of validity. + Â - Effective from: starting date of validity. -Â - Expiration Date: date of expiration of the sla. + Â - Expiration Date: date of expiration of the sla. -Â - Allocated resources: in this subsection you have to establish the maximum number of resources (VMÂ , vCPUs, RAM, Public IPs, Storage) available for the sla, the PaaS will allow deployments until the total sum of the active deployments resources exceded the number agreed in the SLA. + Â - Allocated resources: in this subsection you have to establish the maximum number of resources (VMÂ , vCPUs, RAM, Public IPs, Storage) available for the sla, the PaaS will allow deployments until the total sum of the active deployments resources exceded the number agreed in the SLA. -When you filled all fields click the SEND button below to confirm the creation. + When you filled all fields click the SEND button below to confirm the creation. 4. If all goes as expected, a green banner on top of the SLAs Page appears.