Date
at 9:30am PST
Tucson Location: LSST Conference Room
Videocom: IP 140.252.24.8 (Direct Dial)
Call 1-866-330-1200, Participant Number 518-2287#
Attendees
Lynne, Cathy, Steve, Peter, Michael, Kem, George, Francisco
Agenda & Notes
Update on Scheduler/OCS issues and code modifications for testing filter change limits (Francisco)
- Moving issues full time. Will define parameters and needs in new JIRA item for next Wednesday w/ Pat. Estimates coding straight forward, but finding best set of parameters for simulation will be hard.
Update on moving production machines to the DMS and the requirement to use ssh-keys for access to those machines as well the requirement for review of what is on those machines (!?) (Cathy).
- ops1 backups on hold for hardware. probably move to ssh-keys when ops1 is backed up. can use VPN account to set up keys, or have to talk to Iain. will enigma move to dmz? Kem/Cathy will get w/ Iain re details of dmz and costs.
Maf versioning control and maf status wrt to productioin machines (Cathy & Lynne).
- there are different maf versions and purposes for analysis
- new features have come fast and furious, maybe time for a ‘real’ release
- Lynne will tag an sstar release after one loop back from Cathy & Kem
Report on DM meeting (Michael).
- repository management, package naming and management —> names caused a lot of discussion
- names get entrenched, hard to make changes if wrong, are important
- CCS will not use DDS internally (?)
- someone at NCSA having issues implementing DDS
Github status (Michael).
- Frossie converting stash and will implement a plugin for JIRA to create branches etc
- old versions cloned can remain, only active dev will go to github
- can v3.3 (filter behavior) be done w/ stash? Francisco prefers
- in github anyone can see, but still need push access to be granted
- in principle github operates the same as stash
- review comments need to be preserved (not sure how)
brief aside about track=yes option in v3.3
- decide to implement track=yes as the default
Brief look at configuration parameter definition document (Michael and see attached file [opens in textedit]).
Scheduler naming discussion (all).
AOB