Add orchestration_stacks to ServiceAnsiblePlaybook

[jntullo]

The SUI needs to be able to access the jobs on a ServiceAnsiblePlaybook. This returns them as an array:

[
  #<ManageIQ::Providers::AnsibleTower::AutomationManager::Job:0x007fe6608789c8
   id: 371,
   name: "miq-playbook-demo_provision_hd2g8j13",
   type: "ManageIQ::Providers::AnsibleTower::AutomationManager::Job",
   description: nil,
   status: "successful",
   ems_ref: "114",
   ancestry: nil,
   ems_id: 10,
   orchestration_template_id: 516,
   created_at: Tue, 14 Feb 2017 19:20:42 UTC +00:00,
   updated_at: Fri, 24 Feb 2017 16:45:02 UTC +00:00,
   retired: nil,
   retires_on: nil,
   retirement_warn: nil,
   retirement_last_warn: nil,
   retirement_state: nil,
   retirement_requester: nil,
   status_reason: nil,
   cloud_tenant_id: nil,
   resource_group: nil,
   start_time: Tue, 14 Feb 2017 20:20:55 UTC +00:00,
   finish_time: Tue, 14 Feb 2017 20:20:58 UTC +00:00,
   configuration_script_base_id: 488,
   verbosity: 0,
   hosts: ["localhost"]>
]

cc: @AllenBW
thoughts @bzwei ?
@miq-bot add_label enhancement, services

[AllenBW]

Well put @jntullo SUI NEEDS 🌮 💃

[bzwei]

change :jobs to :orchestration_stacks

[bzwei]

def orchestration_stacks
  service_resources.where(:resource_type => 'OrchestrationStack').each_with_object({}) do |sr, hash|
    hash[sr.name] = sr.resource
  end
end

[jntullo]

@bzwei I had this initially, but I found that my sample data had multiple resources for the same action, which is why I thought I'd utilize job. Is this just an anomaly due to bad data?

[bzwei]

We should have one Provision and one Retirement job, but for Reconfigure that we may support in the future, it can have multiple jobs.
I am hesitated too about this matter. We don't have clear answer whether we want to support Reconfigure. If so, even the existing job method needs to return an array.

[jntullo]

@miq-bot assign @gmcculloug

[bzwei]

A second thought - the method should not return a hash. Just like vms, an array is better. And this method can be moved to Service thus good for Orchestration and AnsibleTower services too.

[miq-bot]

Checked commit jntullo@b92057d with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 0 offenses detected
Everything looks good. 🍪

[gmcculloug]

@jntullo Please update the description to reflect the updated return format.

Looks like we lose the action with the recent change. Not sure if that is required information to retain here. cc @bzwei

[jntullo]

@gmcculloug done 👍

[jntullo]

while it would be nice to retain the action, the action can be retrieved from the service resource

[AllenBW]

OH GLORIOUS DAY!!!! 🌮 💃