Updating policy release notes to remove multi-tenancy
from Guilin release as we don't support it yet.
Issue-ID: POLICY-3493
Change-Id: Ie55d978757680634988dabb23184d66bca9a8f91
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
- All components return with non-zero exit code in case of application failure
- All components log to standard out (i.e., k8s logs) by default
- Continue to write log files inside individual pods, as well
- All components return with non-zero exit code in case of application failure
- All components log to standard out (i.e., k8s logs) by default
- Continue to write log files inside individual pods, as well
-* Multi-tenancy
- - Basic initial support using the existing features
* E2E Network Slicing
- Added ModifyNSSI operation to SO actor
* Consolidated health check
* E2E Network Slicing
- Added ModifyNSSI operation to SO actor
* Consolidated health check