search

rubrikinc / rubrik-extension-for-vcd

VMware Cloud Director Extension for Rubrik CDM
https://build.rubrik.com/tooling-integrations/rubrik-extension-for-vcloud-director/
MIT License
8 stars 3 forks source link

Inconsistency in the display of SLAs (in one case) between Rubrik extension for VCD and Rubrik CDM UI #55

Open rmjstn opened 2 years ago

rmjstn commented 2 years ago

What happened :

Not all SLAs displayed through the Rubrik extention for VCD are identicals to those presented by Rubrik CDM UI.

What you expected to happen :

Have the same display rules.

How to reproduce it :

If a vApp with SLA Bronze (for example) and existing snapshots is set to DoNotProtect by choosing the option "Preserve retention from previous SLA" (from Rubrik CDM UI) or "Retain Snapshots with Existing SLA" (from Rubrik extension for VCD), it appears with "No SLA Domain" in Rubrik. In the Rubrik extension for VCD it appears with the previous SLA (in this case Bronze) in the tab "Protection > vApps".

If you choose the option "Expire Immediately", the SLA appears well as "Do Not Protect" in Rubrik UI and as "Unprotected" in the Rubrik Extension for VCD. What is consistent.

Anything else we need to know ? :

The method API called in both case is : https://***/api/v1/vcd/hierarchy/VcdOrgVdc:::***/children

The response for the vApp is (extract) :

"id": "VcdVapp:::***",
"configuredSlaDomainId": "***",
"configuredSlaDomainName": "Bronze",
"configuredSlaDomainType": "RetentionSla",
"isConfiguredSlaDomainRetentionLocked": false,
"effectiveSlaDomainId": "UNPROTECTED",
"effectiveSlaDomainName": "Unprotected",
"isEffectiveSlaDomainRetentionLocked": false,
"slaAssignment": "Direct",
...

The Rubrik Extension must show the configuredSlaDomainName field, not the Rubrik CDM UI.

Environment :

Thanks,

Rémy

rummtron commented 2 years ago

The SLA Domain shown in the vApp protection dashboard should represent the currently assigned/effective SLA. There is an issue where the plugin was showing the retention SLA. This is incorrect and will be resolved in the next release (v2.0.4).

"Snapshot Management" was also introduced in v2.0.2 to perform actions for relics. This mirrors behavior in CDM for the same Snapshot Management module.