locked
About the tag "ExtendedTerms" in the job schema of HPCS 2008 RRS feed

  • Question

  • Hi everyone,

    Sorry for post almost the same question again, since I didn't get my answer in the last one.

    Let me make my question simple: Is tag "ExtendedTerms" still supported in the job schema of Windows HPC Server 2008?

    I have a job submission filter and want to re-assign certain kind of job to some other cluster. In order to distinguish them out, I add ExtendedTerms information in the job template file. Then I submit the job through command: job submit /jobfile:jt.xml.

    For debugging I make a copy of the job template file provided to my filter. But in the copy, I cannot find any ExtendedTerms information.

    E.g. my original jt.xml is
    <?xml version="1.0" encoding="utf-8"?> 
    <Job xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Name="ExtendedTermsName" JobTemplate="Default" > 
      <ExtendedTerms xmlns="http://www.microsoft.com/ComputeCluster/"
        <Term> 
          <Name>term1</Name> 
          <Value>Vaule1</Value> 
        </Term> 
      </ExtendedTerms> 
      <Tasks xmlns="http://www.microsoft.com/ComputeCluster/"
        <Task Id="1" Name="task1" MinCores="1" MaxCores="1" CommandLine="hostname.exe"
           <EnvironmentVariables> 
           <Variable> 
              <Name>MDCE_DECODE_FUNCTION</Name> 
              <Value>decodeCcsSingleTask</Value> 
            </Variable> 
           </EnvironmentVariables> 
        </Task> 
      </Tasks> 
    </Job> 
    But the copy job template file is:
    <?xml version="1.0" encoding="utf-8"?> 
    <Job Id="6" IsBackfill="false" Name="ExtendedTermsName" Project="" SubmittedBy="TESTDOMAIN\Administrator" User="TESTDOMAIN\Administrator"
      <Tasks> 
        <Task AllocatedNodes="" Id="6" CommandLine="hostname.exe" MaximumNumberOfProcessors="1" MinimumNumberOfProcessors="1" Name="task1" ParentJobId="6" State="Submitted"
          <EnvironmentVariables> 
            <Variable> 
              <Name>MDCE_DECODE_FUNCTION</Name> 
              <Value>decodeCcsSingleTask</Value> 
            </Variable> 
          </EnvironmentVariables> 
        </Task> 
      </Tasks> 
    </Job> 
    You can find the ExtendedTerms block is missing.

    Any help will be much appreciated! Thanks.

    - Woody
    Friday, September 12, 2008 7:38 AM

Answers

All replies

  • Hi,

    I am trying the submission filter on Windows HPC server 2008 these days.

    I learned from http://technet.microsoft.com/en-us/library/cc720068.aspx that I can add new terms to the job template xml file so that my submission filter can capture those terms when the job is submitted.

    But it doesn't work in my place. 
    My submission filter cannot find those new terms ,I added in the job template file, in the job template file provided by Windows HPC server 2008. 

    Is there a switch or sth I missed?

    Thanks in advance!

    -Woody
    Monday, September 8, 2008 7:47 AM
  • Hi Woody,
    We have a number of tests internally that test this, and they all seem to be working.  Can you give us more specific repro steps?  Specifically:
    • Exactly what actions did you take, in order?
    • The Job Description (XML) file that you used
    • Code for the Submission Filter application that you used

    Thanks,
    Josh


    -Josh
    Monday, September 8, 2008 9:03 PM
    Moderator
  • Hi Josh,

    Thanks for your reply.

    The Code I used for the submission filter application is almost same as the Job Submission Filter Example in the windowshpc.net (http://archives.windowshpc.net/files/4/sdk/entry897.aspx), especially the JobTerm class which is used to analyze the job template file, I just copy the class from example to my application.

    I simulate the submission filter working process by typing command like "mysubmissionfilter jobtemplate.xml" in the CMD, it works fine. But when I submit job through "job submit /jobfile:jt.xml" and copy the job template file automatically provided to my submission filter to somewhere,I am surprised to find that that job template file doesn't contain any ExtendedTerms information.  But if I export the job which created by the command "job submit /jobfile:jt.xml" out from the Job Manager, I find all those EntendedTerms inforamtion are there. That's weird!

    The job template I used is:
    1<?xml version="1.0" encoding="utf-8"?> 
    2<Job xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Name="ExtendedTermsName" JobTemplate="Default" > 
    3  <ExtendedTerms xmlns="http://www.microsoft.com/ComputeCluster/"
    4    <Term> 
    5      <Name>JobType0</Name> 
    6      <Value>Hadoop</Value> 
    7    </Term> 
    8    <Term> 
    9      <Name>JSDLFile0</Name>  
    10      <Value>C:\HomeofYang\TestEnvs\HadoopJobSubmissionFilter\JSDL.xml</Value>  
    11    </Term> 
    12    <Term> 
    13      <Name>UserName0</Name>  
    14      <Value>woodyzhou</Value>  
    15    </Term> 
    16    <Term> 
    17      <Name>Password0</Name>  
    18      <Value>123456</Value>  
    19    </Term> 
    20    <Term> 
    21      <Name>ActivityIdentifyLocation0</Name>  
    22      <Value>C:\HomeofYang\TestEnvs\HadoopJobSubmissionFilter\ActivityIdentify</Value>  
    23    </Term> 
    24    <Term> 
    25      <Name>HPCBPURL0</Name>  
    26      <Value>https://d-shc-yangzhou:8443/hadoop/services/BESService</Value>  
    27    </Term> 
    28  </ExtendedTerms> 
    29  <Tasks xmlns="http://www.microsoft.com/ComputeCluster/"
    30    <Task Id="1" Name="task1" MinCores="1" MaxCores="1" CommandLine="hostname.exe"
    31       <EnvironmentVariables /> 
    32    </Task> 
    33  </Tasks> 
    34</Job> 
    BTW, why must I follow very Term name with a number?

    Thanks.
    - Woody
    • Edited by Zhou Yang Tuesday, September 9, 2008 7:17 AM for some reason
    Tuesday, September 9, 2008 12:39 AM
  • Looks like you may have found a bug . . . I'm following up with Test and Development and we'll get back to you.

    Thanks for the dilligent testing!

    -Josh
    -Josh
    Tuesday, September 16, 2008 9:45 PM
    Moderator
  • Ho, it's not a good news to me!:-(
    Waiting for your progress... Thanks!
    Tuesday, September 23, 2008 5:38 AM
  • FYI we are still looking into this.  I hope to have an answer soon.
    -Josh
    Friday, October 10, 2008 12:15 AM
    Moderator
  • Woody,
    We are planning on releasing a product update which will fix this issue.  After the fix, the XML which is input to the Submission Filter will use the same schema as that which is input to the Activation Filter and when you export a job.

    Thanks for catching this bug so early!  I will try to post back here when the fix is ready (should be within 2 weeks or so) with more details.

    Thanks!
    Josh


    -Josh
    Wednesday, October 15, 2008 5:40 PM
    Moderator
  • Thank you!
    Monday, October 20, 2008 4:35 AM
  • Thursday, November 6, 2008 7:27 PM
    Moderator