Oracle have introduced a new resource model for Exadata Cloud Systems. In the new model, the DB system is split into two resources, the Cloud Exadata Infrastructure resource, and the Cloud VM Cluster resource. Next month (May 15th 2021) support for the existing DbSystem API will end for Exadata Cloud Services. Further details are available here:
This pull request adds support for scaling the new Cloud VM Cluster resource and has been tested scaling up and down an Exadata system that has been migrated from the old resource model to the new model. Only one test is outstanding and that's scaling down to 0 (shut down) and then back up again. This can't be tested until I have a suitable window to take my system down. Hopefully within the next 48 hours. This last test is to verify that when shutdown, the resource lifecycle_state still shows as available.
@AnykeyNL
Oracle have introduced a new resource model for Exadata Cloud Systems. In the new model, the DB system is split into two resources, the Cloud Exadata Infrastructure resource, and the Cloud VM Cluster resource. Next month (May 15th 2021) support for the existing DbSystem API will end for Exadata Cloud Services. Further details are available here:
https://docs.oracle.com/en-us/iaas/Content/Database/Concepts/exaflexsystem.htm#exaflexsystem_topic-resource_model
Deprecation of the API is mentioned here: https://docs.oracle.com/en-us/iaas/api/#/en/database/20160918/DbSystem/
This pull request adds support for scaling the new Cloud VM Cluster resource and has been tested scaling up and down an Exadata system that has been migrated from the old resource model to the new model. Only one test is outstanding and that's scaling down to 0 (shut down) and then back up again. This can't be tested until I have a suitable window to take my system down. Hopefully within the next 48 hours. This last test is to verify that when shutdown, the resource lifecycle_state still shows as available.
Regards Richard