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

Allow Batch Connect apps to dynamically choose cluster #282

nickjer opened this issue Oct 31, 2017 · 2 comments


None yet
4 participants
Copy link

commented Oct 31, 2017

We want to support an optional dropdown list to choose the cluster to submit to.

screen 2018-09-12 at 10 58 58 am

There are challenges with this:

  1. The web form and submission handling assumes its dealing with a single cluster; we will now have to support adding to these config files the config for multiple clusters (default for all, optional per-cluster overrides)
  2. The web view would need to update the form dynamically based on the cluster selected
  3. The cluster configs provide the ability to "hide" clusters or "invalidate" clusters i.e. if a user doesn't have access to a cluster, so the list of clusters the user can choose (and associated web forms they can see) would need to
  4. The form.yml needs to be able to specify to use all clusters or an array of clusters instead of just 1 cluster. For example instead of cluster: owens it might be cluster: [ owens, ruby ] or cluster: * or even cluster: foo* with glob arg (though the last could be dropped if there wasn't a dead simple way to apply those without conflicting with the simple cluster: owens).
  5. Getting status of running jobs (the cluster submitted to needs to be stored)
  6. The deprecated "smart attributes" still in use may need to be addressed, since currently these have adapter specific differences that change based on the cluster.

Original description:

A suggestion by one of our OOD partners is to allow for the user to choose the cluster to run the app on from a list of clusters.

This will affect:

  • app authorization
  • smart attributes
  • getting status of running jobs

So care must be taken in the redesign to cover these topics

@ericfranz, @basilgohar, @brianmcmichael

@nickjer nickjer added the enhancement label Oct 31, 2017

@ericfranz ericfranz added this to the OOD1.3 milestone Nov 16, 2017

@ericfranz ericfranz modified the milestones: OOD1.3, NEXT Apr 17, 2018

@ericfranz ericfranz modified the milestones: NEXT, OOD1.4 Aug 14, 2018

@OSC OSC deleted a comment from nickjer Sep 12, 2018

@OSC OSC deleted a comment from nickjer Sep 12, 2018


This comment has been minimized.

Copy link

commented Dec 4, 2018

To accomplish this lets create an example batch connect app and modify the dashboard to make it work. Requirements:

  1. Owens, Ruby, Pitzer VDI app called VDI
  2. You select the cluster as the first option
  3. If you select Ruby the Desktop option is hidden
  4. The session that is submitted displays the cluster in the title i.e. Owens VDI or it says VDI and (owens - is displayed for the cluster and job id.

@ericfranz ericfranz self-assigned this Dec 4, 2018


This comment has been minimized.

Copy link

commented Dec 4, 2018

screen 2018-12-04 at 3 24 48 pm
screen 2018-12-04 at 3 23 54 pm

@ericfranz ericfranz modified the milestones: OOD1.4, NEXT Dec 19, 2018

@ericfranz ericfranz modified the milestones: NEXT, OOD1.5 Jan 9, 2019

@ericfranz ericfranz modified the milestones: OOD1.5, OOD1.6 Feb 26, 2019

@ericfranz ericfranz referenced a pull request that will close this issue Mar 2, 2019


iHPC apps to submit to multiple clusters #424

@ericfranz ericfranz modified the milestones: OOD1.6, NEXT Mar 25, 2019

@ericfranz ericfranz modified the milestones: NEXT, OOD1.6 Apr 23, 2019

@ericfranz ericfranz removed this from the OOD1.6 milestone May 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.