The first order problem was:
- OpenStackSDK was not updated to permit querying by shards, and various overrides for forcing microversion and acceptance unknown fields were not functioning.
While this has been fixed in openstacksdk (and 2023.2, which is landing now), we would have to perform a release, get an RFE just to land a minimally tested feature. As a result, we decided to revert sharding as a feature until CI can be introduced that validates it separates nova-computes properly.
Next cycle, we will land sharding alongside support CI to ensure it's fully working before releasing it to users.
Tracking some followups to this here: https:/ /etherpad. opendev. org/p/nova- sharding- rca
The first order problem was:
- OpenStackSDK was not updated to permit querying by shards, and various overrides for forcing microversion and acceptance unknown fields were not functioning.
While this has been fixed in openstacksdk (and 2023.2, which is landing now), we would have to perform a release, get an RFE just to land a minimally tested feature. As a result, we decided to revert sharding as a feature until CI can be introduced that validates it separates nova-computes properly.
Next cycle, we will land sharding alongside support CI to ensure it's fully working before releasing it to users.