Project

General

Profile

Feature #6517

add --user flag to jobsub_q.py

Added by Dennis Box about 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
06/18/2014
Due date:
% Done:

100%

Estimated time:
1.00 h
Spent time:
Stakeholders:
Duration:

Description

This feature has already been tagged and released but not deployed as there are questions about its RESTfulness. The ticket is being created after the fact to document the work done and identify where it lives in git.

The URL that jobsub_q.py uses for this release (v0.3.1.2) actually works for all of the v0.3* servers and some of the v0.2x servers. I.e. the /jobsub/jobs/ URL basically does condor_q -g for these servers, /jobsub/jobs/?user=fred does condor_q fred, /jobsub/jobs/?group=fred does condor_q -constraint 'AccountingGroup == "fred"' , /jobsub/jobs/?job_id=X' does condor_q cluster.process after decoding the cluster and process from X which is different in the 2.0 and 3.0 servers but usually works.

/jobsub/jobs/?user=fred&group=nova&job_id= and all permutations work correctly on all v0.3 servers and some v0.2 servers, but are not RESTful.

I am going to create a branch with all of the client-side changes in them to make backing it out of the main branch easier. There is already a branch with 6512, a server side bug isolated in it, which I want to keep in the main branch. These two branches are the whole of the changes for v0.3.1.2 from v0.3.1.1

History

#1 Updated by Dennis Box about 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
  • Estimated time set to 1.00 h

#2 Updated by Dennis Box almost 5 years ago

  • Status changed from Resolved to Assigned
  • Target version changed from v0.3.1.2 to v1.0

A much more restful URL for this functionality would be /jobsub/users/<user>/jobs/, and in v0.4 this returns 501 not implemented instead of 404 not found. Make this work for v1.0

#3 Updated by Dennis Box almost 5 years ago

  • Status changed from Assigned to Resolved

#4 Updated by Dennis Box almost 5 years ago

see branch 6517-newer . I didn't want to figure out how to merge the conflicts right now I am trying to get a release out.

#5 Updated by Parag Mhashilkar almost 5 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF