Skip to content

CSTACKEX-241: adding in the updatestoragepool of provider's lifecycle - #90

Open
sathvikaragi wants to merge 2 commits into
mainfrom
fix/CSTACKEX-241
Open

CSTACKEX-241: adding in the updatestoragepool of provider's lifecycle#90
sathvikaragi wants to merge 2 commits into
mainfrom
fix/CSTACKEX-241

Conversation

@sathvikaragi

Copy link
Copy Markdown
Collaborator

Description

While implementing storage pool resize via the updateStoragePool API,
StorageManagerImpl.updateStoragePool()updates the database but never calls PrimaryDataStoreLifeCycle.updateStoragePool() on the storage plugin.
adding that call in here.
This PR...

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

Copilot AI lite review requested due to automatic review settings August 10, 2026 18:07

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates CloudStack’s updateStoragePool flow to invoke the storage provider lifecycle (PrimaryDataStoreLifeCycle.updateStoragePool) so plugins are notified when a primary storage pool is updated (e.g., during resize via capacityBytes/capacityIops).

Changes:

  • Calls PrimaryDataStoreLifeCycle.updateStoragePool(pool, details) during StorageManagerImpl.updateStoragePool.
  • Propagates updated capacity values into the in-memory StoragePoolVO before persisting.
  • Persists merged storage pool details after invoking the lifecycle update.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +1288 to +1292
if (changes) {
DataStoreProvider dataStoreProvider = _dataStoreProviderMgr.getDataStoreProvider(pool.getStorageProviderName());
DataStoreLifeCycle dataStoreLifeCycle = dataStoreProvider.getDataStoreLifeCycle();
if (dataStoreLifeCycle instanceof PrimaryDataStoreLifeCycle) {
if (updatedCapacityBytes != null) {
Comment on lines +1303 to +1305
((PrimaryDataStoreLifeCycle)dataStoreLifeCycle).updateStoragePool(pool, details);
_storagePoolDao.update(id, pool);
_storagePoolDao.updateDetails(id, details);
Copilot AI review requested due to automatic review settings August 11, 2026 03:20

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comment on lines +1303 to 1305
((PrimaryDataStoreLifeCycle)dataStoreLifeCycle).updateStoragePool(pool, details);
_storagePoolDao.update(id, pool);
_storagePoolDao.updateDetails(id, details);
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants