Versions Compared

Old Version 6

changes.mady.by.user Jacek Becla

Saved on

compared with

New Version Current

changes.mady.by.user Kian-Tat Lim

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

, 11am-12pm pacific.

 ls.st/sup

Attendees

Goals

  • To start getting on the same page with regards to butler, with focus on what butler really is, what it does, what its roles are, what APIs is has, and most importantly what it will and will not do in the future.

...

TimeItemWhoNotes
5minIntroK-T or NateP or Jacek

 

10minUW  
  • Easily specify new outputs from tasks (no need to edit obs_ packages)
  • butler.get should fail immediately if the data is not available
  • Easily iterate over partial IDs for all dataset types
  • Simplify the way IDs are normalized (?), and document the system better; also preferably make it easier to know when you have an ID that has been normalized or not.
  • Handling of bitemporal calibration products including camera descriptions. N.b. calibration products can be lots of different things: objects, images, telemetry data, sky model, etc.
  • Butlerized access to logs, configs, stack version, etc.
10minPrinceton DRP Butler Requirements / Feature Requests
10minIPAC  SUI / Level 3 and SuperTask feedback on the Butler
10minSQUARE  
  • isolate in-memory from IO, architecture for plugging other protocols (like S3)
10minNCSA

 

 
 Architecture 

Tim Jenness : I feel strongly that we should have two persistable file format options designed in to the butler (FITS and HDF5 say) so that we can be sure we have a flexible design that is not wedded to a single file format.

Unknown User (npease): 

  • Jira
    serverJIRA
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-4543
  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-4542
  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-4541
    (not butler work, has an AFW component tag)
 Discussion 
  • Carry technical discussions via community
  • Next meeting: Tuesday Dec 8, 12:30pm, via bluejeans. Focus: (a) check if created stories adequately cover all requests, (b) finalize prioritization

Children Display
styleh3

Random notes

Butler (not-done) stories:

Jira
serverJIRA
jqlQueryfilter=13800
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Action items

  •  Unknown User (npease), turn the requirements discussed / input received into JIRA stories
  •  Identify core architectural issues
  •  Design core architectural issues
  •  Write a comprehensible high level design document
  •  Create interface definition (we will defer remote butler & URL interface definition)
    •  Application Interface
    •  Configuration Interface
    •  Back-end interface. Include what can be plugged in, and where.
      •  transport
      •  serialization
      •  storage
  •  Unknown User (npease) and Kian-Tat Lim - propose prioritization of all butler stories
  •  Work on top-priority item for each group:
    •  Princeton:
      Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyDM-4181
      (epic S16) (Serge Monkewitz is working on kind-of-related
      Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyDM-3472
      )
    •  SUI: Multiple repositories: finish defining, create story, work on partial implementation TBD.
      •  
        Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-4625
      •  Implement 
        Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-4682
        (epic W16) (might get broken into 2 stories and delivered over 2 sprints)
    •  UW: 
      Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyDM-4168
       (epic Butler W16), also "if time": 
      Jira
      serverJIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyDM-4180
       (epic S16)
    •  Tuscon: define interface for 
      Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyDM-4555
      (epic S16, assigned to BVK)
    •  NCSA: (nothing at this time)

...