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

Add my_queue_name for ems_operations miq_requests #19739

Merged
merged 8 commits into from
Jan 28, 2020

Conversation

agrare
Copy link
Member

@agrare agrare commented Jan 21, 2020

Add a queue name for all of the ems_operations MiqRequest classes

#19543

Copy link
Member

@lfu lfu left a comment

Choose a reason for hiding this comment

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

I'm wondering whether all MiqRequest classes belong to ems_operations. If that is the case, the same change would/should be applied to all MiqRequest classes? @gmcculloug What do you think?

@gmcculloug
Copy link
Member

Here is the list of classes that derive from MiqRequest. Most, but not all use ems_operations.

  • MiqRequest (role = nil)
    • AutomationRequest (role = automate)
    • MiqProvisionConfiguredSystemRequest
    • MiqProvisionRequest
      • MiqProvisionRequestTemplate
    • MiqRetireRequest (inherits from parent)
      • OrchestrationStackRetireRequest (inherits from parent)
      • ServiceRetireRequest (inherits from parent)
      • VmRetireRequest (inherits from parent)
    • PhysicalServerFirmwareUpdateRequest
    • PhysicalServerProvisionRequest
    • ServiceReconfigureRequest
    • ServiceTemplateProvisionRequest (conditional either 'automate' : 'ems_operations')
      • ServiceTemplateTransformationPlanRequest (inherits from parent)
    • VmCloudReconfigureRequest
    • VmMigrateRequest
    • VmReconfigureRequest

@agrare
Copy link
Member Author

agrare commented Jan 23, 2020

Yeah I was going through the obvious ones first, ones with a clear "source" object that I can use to get the queue_name from. But intend to go through all of the MiqRequestTask classes that have the ems_operations role.

@agrare agrare force-pushed the add_my_queue_name_to_vm_migrate branch 2 times, most recently from 7e2bb77 to 6bc4102 Compare January 27, 2020 18:51
@agrare agrare force-pushed the add_my_queue_name_to_vm_migrate branch 2 times, most recently from 89539ef to ec12b7f Compare January 27, 2020 19:21
@gmcculloug
Copy link
Member

gmcculloug commented Jan 27, 2020

@agrare As discussed can you add tests for the classes that have existing specs. Looks like that would include these:

app/models/configured_system.rb
app/models/physical_server.rb
app/models/physical_server_firmware_update_request.rb

I opened issue #19771 to create tests for the following classes that do not have tests today:

app/models/miq_provision_configured_system_request.rb
app/models/vm_cloud_reconfigure_request.rb
app/models/vm_migrate_request.rb

@agrare agrare force-pushed the add_my_queue_name_to_vm_migrate branch from ec12b7f to 197e18c Compare January 28, 2020 13:28
@miq-bot
Copy link
Member

miq-bot commented Jan 28, 2020

Checked commits agrare/manageiq@6cb7e9c~...197e18c with ruby 2.5.5, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
11 files checked, 0 offenses detected
Everything looks fine. ⭐

@agrare
Copy link
Member Author

agrare commented Jan 28, 2020

@gmcculloug 👍 done

@gmcculloug gmcculloug merged commit f01197e into ManageIQ:master Jan 28, 2020
@gmcculloug gmcculloug added this to the Sprint 129 Ending Feb 3, 2020 milestone Jan 28, 2020
@agrare agrare deleted the add_my_queue_name_to_vm_migrate branch January 28, 2020 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants