(back to the list of all DMLT meeting minutes)

NOTE: For this meeting and future dates we are conducting the meeting on Blue Jeans (use web browser or below):

Web Browser:

https://bluejeans.com/293724745/

> Connecting directly from a room system?

> 1) Dial: 199.48.152.152 or bjn.vc
> 2) Enter Meeting ID: 293724745 -or- use the pairing code

 
> Just want to dial in? (all numbers)
> 1) Direct-dial with my iPhone or 
> +1 408 740 7256+1 408 740 7256 
> +1 888 240 2560+1 888 240 2560 (US Toll Free)
> +1 408 317 9253+1 408 317 9253 (Alternate Number)

> 2) Enter Meeting ID: 293724745

Date

Attendees

(sorry if I missed anyone)

 

Goals
  • Weekly coordination meeting to discuss and resolve management items, project communications, external contacts, etc.

Discussion items

 

Item
Who
Notes
LSST 2015 MeetingKian-Tat Lim

DM Attendance at sessions:

LSST 2015 Meeting - DM session planning

Reminder: All DMLT list the sessions they plan to attend (and non-DMLT if possible)

JIRA, LDM-240 updates

Jeff Kantor

T/CAMs finish working intra-WBS dependencies, KPMs.

Need to capture past milestones that are completed (S14, W15).

Kian-Tat Lim, Jeff Kantor, Kevin Long working on incorporating Level 2 Milestones and release information (goals, interfaces, input data, output data) from PMCS and LDM-240 sheet, linking JIRA Level 3 Milestones in DLP

Deadline is Aug 10, to be ready to work on them at LSST 2015.

 Another AMCL presentation will be delivered after LSST 2015 at September 3 meeting at SLAC. Several key points are to be emphasized, addressing how Level 3 Milestones are measurable, non-subjective to the maximum extent possible.

Infrastructure

Jeff Kantor

Donald Petravick

NCSA procurement amendment is signed. Need to prepare FY15 and FY16 acquisition plans. Set up discussion of OpenStack and interim outsourced solutions.

Near-term planning needs:

  1. Understand what to do with "legacy infrastructure", what to modernize
  2. Understand trajectory, steps to mature shared NCSA OpenStack development environment
  3.  Develop FY16 infrastructure requirements, including identifying large-scale runs, "mini-productions"

Address in regular Infrastructure meetings going forward.

There is a separate ticket system (RT) in NCSA. Some work is not single-ticket oriented (e.g. recent network issue). NCSA will be liaison for LSST tickets re OpenStack. Greg Daues is POC for these while Don is out. Prefer that Greg Daues "gate" the entry to tickets into RT to retain prioritization, but not opposed to direct contact with OpenStack group once ticket is entered. Will decide over time whether this works well or needs augmentation.

(Don on vacation two weeks starting   Working on inputting input to TOWG into EA this week.)

November DMLT meeting at PrincetonJohn Swinbank

November 16 afternoon - November 18 morning, with T/CAM sessions November 18 afternoon.

Logistics, meals in work. Need to establish agenda.

Contacts database and mailing listsJeff Kantor

The LSST Project Office maintains a central Contacts database that is accessible via the project.lsst.org web site. This list includes Contact information for anyone known to be associated with the LSST Project, Science Collaborations, etc. Mailing list membership can be linked to this database so that when someone is added, changes status, or leaves, their mailling list membership is automatically updated. This also allows the Project Office and subsystem managers, scientists, and engineers to ensure that communications targeted to a specific audience are routed properly.

I recently was asked to update the DM entries in the database and got input from the T/CAMs. We need to decide which mailing lists to link to the database.

dm-staff, DMLT managed with Contacts database

dm-announce, dm-devel push Contacts database into list, but no unsubscribe

 

 Action items


1 Comment

  1. Yes. It's unfortunate I am  off  on Friday for a two week vacation.   Also, Bill G, the Lead in the group that is targeted on supporting the development group has a critical family emergency, and has been dealing with this for a few weeks and more time in the future will be needed.    We should discuss priorities at the meeting.   Our initial proposal, for the initial planning period envisioned spending most of these funds on

    replacing the bulk of the obsolete computing equipment,  upgrading the VMware administration, and working towards an openstack.  The Openstack si being commissioned and the proposal is that it will be extended with LSST supplied hardware once it is establlished as functional.

    The remainder of the procurments need to be re-vetted by Bill  once he is available.