Description of problem: It would be helpful to include the Owner value from a job class ad in the Aviary JobId structure. This would allow the owner of a job to be examined in job summaries for a submission. At present, the Owner value is only available in a full job ad from the GetJobDetails method.
Actually, the SubmissionID is a field of a returned and fully-formed JobID and it contains an owner value. Is this somehow insufficient?
Proposal: Jobs with different owners can attach to a submission which has an originating owner. The model of a single originating owner will be maintained, however the Aviary API will be modified to reflect that several jobs and more specifically several owners are potentially part of a submission. <xs:complexType name="SubmissionID"> <xs:sequence> <xs:element name="name" type="xs:string" minOccurs="0"/> <xs:element name="owner" type="xs:string" minOccurs="0"/> <xs:element name="qdate" type="xs:int" minOccurs="0"/> <!-- new --> <xs:element name="others" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="JobID"> <xs:sequence> <xs:element name="job" type="xs:string"/> <!-- new --> <xs:element name="owner" type="xs:string" minOccurs="0"/> <xs:element name="pool" type="xs:string" minOccurs="0"/> <xs:element name="scheduler" type="xs:string" minOccurs="0"/> <xs:element name="submission" type="tns:SubmissionID" minOccurs="0"/> </xs:sequence> </xs:complexType>
Ignore comment #3. Since a job summary returns a job id which in turn contains a submission id containing an owner name, this should suffice for the time being. The issue of submission name+owner scoping will be addressed in a future release under a different BZ.
(In reply to comment #4) Have you number of that BZ for the future release? If this is duplicate of any other BZ, please mark it as duplicate. If that BZ doesn't exist, please move this BZ to future release.
Bug 839305 comment 4 mentions the name+owner scope issue.
Apologies, bug 893027 is the forward bz.