Minutes from SSS Mtg 2009-Feb-03

Attendees: B.Butler,    B.Clark,      M.Claussen, D.Harland,
           G.v.Moorsel, L.Sjouwerman, B.Truitt,   S.Witz

Remark

Prior to the meeting it was mentioned that the main topic of the meeting would be the technical interaction between the OPT and Dynamic Scheduler and that scientists need not attend.

Single Sign-On

Stephan has seen progress on this front by Open Sky. Dave is working on an automated process for turning the XML schema files into java classes that applications can then use to parse the XMl returned from the user database web service. Dave wants to ask Open Sky for cooperation on using namespaces and on the location (URL) of the user.xsd file.

OPT - Dynamic Scheduler Communication (Special Guest Columnist: Brian Truitt)

Schedule Re-submission (dynamic):

* Once an SB is submitted it is permanently read only.
  To resubmit, you must unsubmit the SB.
  This process will create a read/write copy of the submitted SB in the OPT.
  From this point on, the submitted SB is immutable in every aspect.

* The process of unsubmitting an SB will make the following updates to the
  dynamic scheduler DB:

  -- Set the SB's repeat count to 0

* The unsubmit process will make the following updates to the OPT's DB:

  -- update the SB's completed count to reflect what was already executed if anything

  -- Update the authorized count to be equal to the completed count

The above changes have the effect of stopping the SB from being scheduled any
further and allows the OPT's Program Block to properly restrict the amount of
time the user uses in further SB's.

* Unsubmitting an SB should probably send an e-mail.

* When the copied SB is submitted, it will act as a new SB with no knowledge
  of the unsubmitted SB.  Only difference will be that it has less allocated
  time to use.

* For testing we'll just hard code the trimester (program field) to "A".
  In the future this information will come out of the proposal.


Schedule Re-submission (fixed):

* Again, submitted SBs are read only.
  You can only unsubmit one if the fixed start time has not passed already.
  In this case, authorized and completed counts are just set to 0.

* Resubmitting works just like submitting the original accept that the file
  name will likely have to be different (appending a letter, etc.)

* Fixed scripts will go into /home/mchost/evla/scripts/opt///

* Scripts will be named:
  .evla


Automated Correspondence:

* autogenerated e-mails will contain the following information to start with:
 
    proposal code,
    project code,
    program (i.e. trimester as used currently in the DB),
    SB id,
    authorized count,
    and number of hours a single iteration takes.

  -- For the hours, I assume we want it rounded up to the nearest half hour,
     just like the current hours field of the scheduler DB.


Misc.

* It was agreed on for now that the dynamic scheduler relying on
  resources at the SOC is ok.  (I.E. we don't have to mirror the
  OPT's database out at the site yet.)

* Submitted SB's should have red text in the OPT's tree.
  We don't need to bother having a consolidated list of the submitted
  SBs somewhere in the OPT.

* It was mentioned that it may be better to just import/export Scheduling
  Blocks, not entire projects.  This is fairly low priority as we are
  currently erring on the side of sending too much rather than not enough information.