Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processor pools support for PowerVS #443

Merged
merged 6 commits into from Feb 1, 2023

Conversation

miyamotoh
Copy link
Contributor

@miyamotoh miyamotoh commented Jan 31, 2023

Aggregated PR with 6 commits from 3 developers, adding support for "shared processor pools" in PowerVS.

  • inventory code written by @alizapeikes
  • VCR cassette updated by @jaywcarman to support the new resources
  • processor pool specific code added to specs by @miyamotoh, along with another VCR cassette refresh

This supersedes #431 which has been gating;

alizapeikes and others added 5 commits January 27, 2023 05:49
Update refresher VCR cassette to include new shared processor pool API
calls.
Unfortunately, the PowerVS region we use for testing has limited
capacity and setting too many affinity controls in the specs makes
re-recording them a pain.
Only one cloud subnet is expected here - fixing the spec and removing
the old TODO.
The "specific" VM used in the refresher spec was no longer a member of a
placement group (see bed18fd). Using another VM in order to keep the
placement_group lazy find spec coverage.
@@ -158,6 +158,10 @@ def assert_specific_vm
)

expect(vm.snapshots.first.total_size).to be > 0

instance_name = "test-instance-rhel-s922-shared-tier3"
Copy link
Member

Choose a reason for hiding this comment

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

Could we put test-instance-ibmi-s922-capped-tier1 in a resource_pool so that we don't have to check a second vm?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried once, but if placement_group and spp_placement_group contradict each other, trying to put the VM on this or that host, then it'd fail, and it did fail on me trying to provision a VM with both specified. I figured that'd be just asking for a trouble at a later time, kinda relying on a luck.

Signed-off-by: Hiro Miyamoto <miyamotoh@us.ibm.com>
@miq-bot
Copy link
Member

miq-bot commented Jan 31, 2023

Some comments on commits miyamotoh/manageiq-providers-ibm_cloud@fdd3d4c~...780f8ad

lib/tasks_private/power_virtual_servers.rake

  • ⚠️ - 302 - Detected puts. Remove all debugging statements.
  • ⚠️ - 304 - Detected puts. Remove all debugging statements.
  • ⚠️ - 324 - Detected puts. Remove all debugging statements.
  • ⚠️ - 326 - Detected puts. Remove all debugging statements.

@miq-bot
Copy link
Member

miq-bot commented Jan 31, 2023

Checked commits miyamotoh/manageiq-providers-ibm_cloud@fdd3d4c~...780f8ad with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint
7 files checked, 0 offenses detected
Everything looks fine. 👍

@agrare agrare self-assigned this Feb 1, 2023
@agrare agrare added the enhancement New feature or request label Feb 1, 2023
@agrare agrare merged commit f736ca5 into ManageIQ:master Feb 1, 2023
@Fryguy Fryguy added this to the Petrosian milestone Sep 14, 2023
@Fryguy Fryguy added this to In progress in Roadmap Sep 14, 2023
@Fryguy Fryguy moved this from In progress to Petrosian in Roadmap Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Roadmap
  
Petrosian
Development

Successfully merging this pull request may close these issues.

None yet

6 participants