[data processing] Job type dropdown needs to be data plugin specific

[Chad Roberts]

*wishlist for Juno, more likely for Kilo*

When choosing the job type (project -> data processing -> Jobs -> Create Job), right now all job types display, even if there is no plugin present to support that job type. The best example of this is Spark. Right now, even if you do not have the spark plugin loaded, the spark job type still shows up. This is mostly harmless, but is misleading to the user and will likely lead to frustration when they discover that they can not run their job.

[Andrew Lazarev (alazarev)]

Currently there is no backend support for that. Sahara doesn't have information about job types supported by plugins. Plugin can only answer "I don't support job type X for cluster Y", but there is no way to ask list of types.

[Andrew Lazarev (alazarev)]

As a simple solution I could suggest config parameter.

[Chad Roberts (croberts)]

I believe the new job-types endpoint that will be implemented for Kilo will be the answer for this. Since it is already late in Kilo, this bug fix will not make it for Kilo, but instead should be fixed early in Liberty.

[Chad Roberts (croberts)]

Ok, finally going to get started on this.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/174479

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/174479
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=e81e1e8307a1dfd8cc3b3addc434f5b8e1040bc6
Submitter: Jenkins
Branch: master

commit e81e1e8307a1dfd8cc3b3addc434f5b8e1040bc6
Author: Chad Roberts <email address hidden>
Date: Thu Apr 16 13:34:58 2015 -0400

    Populating job type choices via api call

    Rather than hard-code the choices for the job type
    dropdown, they are now generated from an api call
    that factors-in currently loaded plugins. Also updated
    the tests to utilize the new call.

    Change-Id: I69f7100335bd35a891f23efd286da784c3d34e9f
    Closes-Bug: #1371285