Data Management
Space shortcuts
Page tree
Skip to end of metadata
Go to start of metadata

Location

Zoom link available on Slack channel.

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesday, July 21st 2021.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescription

CCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-771 - Getting issue details... STATUS Planned end: Apr/21/2021

  • RFC-783 - Getting issue details... STATUS Planned end: July/31/2021

  • RFC-790 - Getting issue details... STATUS
  • RFC-791 - Getting issue details... STATUS

GPDF on vacation



790 board recommend - can now use locked envs but worry it may cause a problem when people install..


791 - tootling needed on summit - has been reviewed. Name may be confusing - but it does verify a flat or bias is useful.  Board recommend

Board Recommended RFCs
  • RFC-785 - Getting issue details... STATUS



Adopted but not implemented LDM RFCs (only document RFCs)



Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021

  • RFC-776 - Getting issue details... STATUS  Planned end: May/21/2021

RFC-638 likely to be withdrawn Yusra thinking about it.

T-Mobile phones are only ipv6 ..

 Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)



RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)

  • RFC-789 - Getting issue details... STATUS
  • RFC-780 - Getting issue details... STATUS





Releases

  • Planned
  • Changes to the release schedule

v23 is the version we think we will use for DP0.2 - it will be driven by dp0.2

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-12250 - Getting issue details... STATUS
  2. DM-91 - Getting issue details... STATUS
  3. DM-12259 - Getting issue details... STATUS
  4. DM-11509 - Getting issue details... STATUS
  5. DM-7540 - Getting issue details... STATUS
  6. DM-7283 - Getting issue details... STATUS
  7. DM-6586 - Getting issue details... STATUS
  8. DM-8058 - Getting issue details... STATUS
  9. DM-12244 - Getting issue details... STATUS
  10. DM-12088 - Getting issue details... STATUS

Unresolved issues: 4080

Many joint_cal –

Open Actions

AOB
  • Not a formal RFC, but Kian-Tat Lim would like confirmation that DM-31157 - Getting issue details... STATUS is the proper path to take.
  • Lot of PanDA requiremetns in conda - should these go in runbin_env ?  or solely on data-int?
    • Sergey has an ssh node manually set up.
    • panda_client and idds - needed by BPS for PanDA submission.
    • It is the one we will use for the next 3 years.
    • Tim will raise an RFC RFC-792 - Getting issue details... STATUS : 

This is not a single line change to JSON dump - would have to do a convert .. so half day work.. not sure what squash does.  This can keep for a while - validate_drp fails but the weekly is built ..



Next DM-CCB July 28th


Pending Flagged RFCs

Key Summary
Refresh

Pending Proposed RFCs

Key Summary
Refresh

Oldest issues

Key Summary
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
 Tim JennessDMCCB#51 (2020 - 05 - 27)