diff --git a/404.html b/404.html index f204357e3..5bbbadd77 100644 --- a/404.html +++ b/404.html @@ -529,6 +529,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/documentation/markdown-migration/index.html b/documentation/markdown-migration/index.html index 77a1974f9..1348d65e7 100644 --- a/documentation/markdown-migration/index.html +++ b/documentation/markdown-migration/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/documentation/publish-osg-pages/index.html b/documentation/publish-osg-pages/index.html index cfaf15bcc..81156eb55 100644 --- a/documentation/publish-osg-pages/index.html +++ b/documentation/publish-osg-pages/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/documentation/reviewing-documentation/index.html b/documentation/reviewing-documentation/index.html index 22e609f9c..cbc332751 100644 --- a/documentation/reviewing-documentation/index.html +++ b/documentation/reviewing-documentation/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/documentation/style-guide/index.html b/documentation/style-guide/index.html index 670dfb06d..48bbba6af 100644 --- a/documentation/style-guide/index.html +++ b/documentation/style-guide/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/documentation/writing-documentation/index.html b/documentation/writing-documentation/index.html index 8ec0a8904..9cfc9a5ff 100644 --- a/documentation/writing-documentation/index.html +++ b/documentation/writing-documentation/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/index.html b/index.html index d55b6a213..cae3bf7b1 100644 --- a/index.html +++ b/index.html @@ -589,6 +589,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200106/index.html b/meetings/2020/TechArea20200106/index.html index dfd8debe3..ea5c565cd 100644 --- a/meetings/2020/TechArea20200106/index.html +++ b/meetings/2020/TechArea20200106/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200113/index.html b/meetings/2020/TechArea20200113/index.html index 697d9f431..1a18f06c6 100644 --- a/meetings/2020/TechArea20200113/index.html +++ b/meetings/2020/TechArea20200113/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200127/index.html b/meetings/2020/TechArea20200127/index.html index 9761187f9..5939d42a4 100644 --- a/meetings/2020/TechArea20200127/index.html +++ b/meetings/2020/TechArea20200127/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200203/index.html b/meetings/2020/TechArea20200203/index.html index db9be029b..71d5359a9 100644 --- a/meetings/2020/TechArea20200203/index.html +++ b/meetings/2020/TechArea20200203/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200210/index.html b/meetings/2020/TechArea20200210/index.html index b6102b8aa..547513d79 100644 --- a/meetings/2020/TechArea20200210/index.html +++ b/meetings/2020/TechArea20200210/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200217/index.html b/meetings/2020/TechArea20200217/index.html index 94705f23e..055071806 100644 --- a/meetings/2020/TechArea20200217/index.html +++ b/meetings/2020/TechArea20200217/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200224/index.html b/meetings/2020/TechArea20200224/index.html index 34771f9cf..11dfcf08b 100644 --- a/meetings/2020/TechArea20200224/index.html +++ b/meetings/2020/TechArea20200224/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200302/index.html b/meetings/2020/TechArea20200302/index.html index 8182c4685..3276fc45b 100644 --- a/meetings/2020/TechArea20200302/index.html +++ b/meetings/2020/TechArea20200302/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200309/index.html b/meetings/2020/TechArea20200309/index.html index 7f9e111d8..d6b87656e 100644 --- a/meetings/2020/TechArea20200309/index.html +++ b/meetings/2020/TechArea20200309/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200316/index.html b/meetings/2020/TechArea20200316/index.html index 508c1a784..a3a47a412 100644 --- a/meetings/2020/TechArea20200316/index.html +++ b/meetings/2020/TechArea20200316/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200323/index.html b/meetings/2020/TechArea20200323/index.html index ab77ad7d7..40e73da7f 100644 --- a/meetings/2020/TechArea20200323/index.html +++ b/meetings/2020/TechArea20200323/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200330/index.html b/meetings/2020/TechArea20200330/index.html index 0598e2110..13cb12a3c 100644 --- a/meetings/2020/TechArea20200330/index.html +++ b/meetings/2020/TechArea20200330/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200406/index.html b/meetings/2020/TechArea20200406/index.html index 7b65f0725..7b6d39900 100644 --- a/meetings/2020/TechArea20200406/index.html +++ b/meetings/2020/TechArea20200406/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200413/index.html b/meetings/2020/TechArea20200413/index.html index 2ae093ee6..34d3c5572 100644 --- a/meetings/2020/TechArea20200413/index.html +++ b/meetings/2020/TechArea20200413/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200420/index.html b/meetings/2020/TechArea20200420/index.html index 12830ec93..112a1aa5b 100644 --- a/meetings/2020/TechArea20200420/index.html +++ b/meetings/2020/TechArea20200420/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200427/index.html b/meetings/2020/TechArea20200427/index.html index e91afb29e..a8bcce09f 100644 --- a/meetings/2020/TechArea20200427/index.html +++ b/meetings/2020/TechArea20200427/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200504/index.html b/meetings/2020/TechArea20200504/index.html index edffd9bbc..a4eef5b4b 100644 --- a/meetings/2020/TechArea20200504/index.html +++ b/meetings/2020/TechArea20200504/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200511/index.html b/meetings/2020/TechArea20200511/index.html index a9e11b3f1..343a21c2c 100644 --- a/meetings/2020/TechArea20200511/index.html +++ b/meetings/2020/TechArea20200511/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200518/index.html b/meetings/2020/TechArea20200518/index.html index e0fcf74b5..a850471c3 100644 --- a/meetings/2020/TechArea20200518/index.html +++ b/meetings/2020/TechArea20200518/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200601/index.html b/meetings/2020/TechArea20200601/index.html index aec3d610a..6b994f712 100644 --- a/meetings/2020/TechArea20200601/index.html +++ b/meetings/2020/TechArea20200601/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200608/index.html b/meetings/2020/TechArea20200608/index.html index 6b637c4a8..ea8fd23a6 100644 --- a/meetings/2020/TechArea20200608/index.html +++ b/meetings/2020/TechArea20200608/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200615/index.html b/meetings/2020/TechArea20200615/index.html index 6e5766746..4816d69d5 100644 --- a/meetings/2020/TechArea20200615/index.html +++ b/meetings/2020/TechArea20200615/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200622/index.html b/meetings/2020/TechArea20200622/index.html index 345ec586d..b5890aa18 100644 --- a/meetings/2020/TechArea20200622/index.html +++ b/meetings/2020/TechArea20200622/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200629/index.html b/meetings/2020/TechArea20200629/index.html index 29b145d4a..2d367f62d 100644 --- a/meetings/2020/TechArea20200629/index.html +++ b/meetings/2020/TechArea20200629/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200706/index.html b/meetings/2020/TechArea20200706/index.html index f7dc6efd8..96b223826 100644 --- a/meetings/2020/TechArea20200706/index.html +++ b/meetings/2020/TechArea20200706/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200713/index.html b/meetings/2020/TechArea20200713/index.html index acd1e4ee7..6ee407de5 100644 --- a/meetings/2020/TechArea20200713/index.html +++ b/meetings/2020/TechArea20200713/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200720/index.html b/meetings/2020/TechArea20200720/index.html index 21a5fdd95..211ced80f 100644 --- a/meetings/2020/TechArea20200720/index.html +++ b/meetings/2020/TechArea20200720/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200727/index.html b/meetings/2020/TechArea20200727/index.html index 3f02448ec..c3eb8c892 100644 --- a/meetings/2020/TechArea20200727/index.html +++ b/meetings/2020/TechArea20200727/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200803/index.html b/meetings/2020/TechArea20200803/index.html index 3dfd2323b..104df23e6 100644 --- a/meetings/2020/TechArea20200803/index.html +++ b/meetings/2020/TechArea20200803/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200810/index.html b/meetings/2020/TechArea20200810/index.html index eedcfad7c..48ddea5e4 100644 --- a/meetings/2020/TechArea20200810/index.html +++ b/meetings/2020/TechArea20200810/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200817/index.html b/meetings/2020/TechArea20200817/index.html index 0457726de..f3ee99fb3 100644 --- a/meetings/2020/TechArea20200817/index.html +++ b/meetings/2020/TechArea20200817/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200824/index.html b/meetings/2020/TechArea20200824/index.html index 466a982fc..89db142be 100644 --- a/meetings/2020/TechArea20200824/index.html +++ b/meetings/2020/TechArea20200824/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200914/index.html b/meetings/2020/TechArea20200914/index.html index 8e522d59b..0b9647482 100644 --- a/meetings/2020/TechArea20200914/index.html +++ b/meetings/2020/TechArea20200914/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20200928/index.html b/meetings/2020/TechArea20200928/index.html index d7e7d0ddf..8a00ddb9c 100644 --- a/meetings/2020/TechArea20200928/index.html +++ b/meetings/2020/TechArea20200928/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201005/index.html b/meetings/2020/TechArea20201005/index.html index 39fe1d926..0ac2ae0c5 100644 --- a/meetings/2020/TechArea20201005/index.html +++ b/meetings/2020/TechArea20201005/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201012/index.html b/meetings/2020/TechArea20201012/index.html index cc4e7502a..98ca94818 100644 --- a/meetings/2020/TechArea20201012/index.html +++ b/meetings/2020/TechArea20201012/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201019/index.html b/meetings/2020/TechArea20201019/index.html index ed92a0016..85ae81ba6 100644 --- a/meetings/2020/TechArea20201019/index.html +++ b/meetings/2020/TechArea20201019/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201026/index.html b/meetings/2020/TechArea20201026/index.html index eb14e6107..ad804733a 100644 --- a/meetings/2020/TechArea20201026/index.html +++ b/meetings/2020/TechArea20201026/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201102/index.html b/meetings/2020/TechArea20201102/index.html index 069c0bfa0..3f896725b 100644 --- a/meetings/2020/TechArea20201102/index.html +++ b/meetings/2020/TechArea20201102/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201109/index.html b/meetings/2020/TechArea20201109/index.html index 5397751d2..b9fa8ddc1 100644 --- a/meetings/2020/TechArea20201109/index.html +++ b/meetings/2020/TechArea20201109/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201116/index.html b/meetings/2020/TechArea20201116/index.html index f927544e2..db520590a 100644 --- a/meetings/2020/TechArea20201116/index.html +++ b/meetings/2020/TechArea20201116/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201123/index.html b/meetings/2020/TechArea20201123/index.html index a08c4e959..3735529e1 100644 --- a/meetings/2020/TechArea20201123/index.html +++ b/meetings/2020/TechArea20201123/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201130/index.html b/meetings/2020/TechArea20201130/index.html index a8c036d39..5b2f508b7 100644 --- a/meetings/2020/TechArea20201130/index.html +++ b/meetings/2020/TechArea20201130/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201207/index.html b/meetings/2020/TechArea20201207/index.html index 0fe71f0db..114b01402 100644 --- a/meetings/2020/TechArea20201207/index.html +++ b/meetings/2020/TechArea20201207/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201214/index.html b/meetings/2020/TechArea20201214/index.html index 7023b63a7..b6dac75e0 100644 --- a/meetings/2020/TechArea20201214/index.html +++ b/meetings/2020/TechArea20201214/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2020/TechArea20201221/index.html b/meetings/2020/TechArea20201221/index.html index cc46dce84..618d93352 100644 --- a/meetings/2020/TechArea20201221/index.html +++ b/meetings/2020/TechArea20201221/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210104/index.html b/meetings/2021/TechArea20210104/index.html index b1bf05e60..8f88024f5 100644 --- a/meetings/2021/TechArea20210104/index.html +++ b/meetings/2021/TechArea20210104/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210112/index.html b/meetings/2021/TechArea20210112/index.html index f1294eb9f..e7c27cd57 100644 --- a/meetings/2021/TechArea20210112/index.html +++ b/meetings/2021/TechArea20210112/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210119/index.html b/meetings/2021/TechArea20210119/index.html index ea3191264..dc79d81fc 100644 --- a/meetings/2021/TechArea20210119/index.html +++ b/meetings/2021/TechArea20210119/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210126/index.html b/meetings/2021/TechArea20210126/index.html index cefdf85cf..45e4e3c92 100644 --- a/meetings/2021/TechArea20210126/index.html +++ b/meetings/2021/TechArea20210126/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210202/index.html b/meetings/2021/TechArea20210202/index.html index 62a15057e..18755056b 100644 --- a/meetings/2021/TechArea20210202/index.html +++ b/meetings/2021/TechArea20210202/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210209/index.html b/meetings/2021/TechArea20210209/index.html index d0abe42aa..d85b4f989 100644 --- a/meetings/2021/TechArea20210209/index.html +++ b/meetings/2021/TechArea20210209/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210216/index.html b/meetings/2021/TechArea20210216/index.html index 7fea9aed7..8bbe04b8d 100644 --- a/meetings/2021/TechArea20210216/index.html +++ b/meetings/2021/TechArea20210216/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210223/index.html b/meetings/2021/TechArea20210223/index.html index 2468addbd..31bb04c4f 100644 --- a/meetings/2021/TechArea20210223/index.html +++ b/meetings/2021/TechArea20210223/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210302/index.html b/meetings/2021/TechArea20210302/index.html index 70513ea3d..77d547857 100644 --- a/meetings/2021/TechArea20210302/index.html +++ b/meetings/2021/TechArea20210302/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210309/index.html b/meetings/2021/TechArea20210309/index.html index 8f8ed49c0..4b7762a3e 100644 --- a/meetings/2021/TechArea20210309/index.html +++ b/meetings/2021/TechArea20210309/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210323/index.html b/meetings/2021/TechArea20210323/index.html index 6778f0756..95d273989 100644 --- a/meetings/2021/TechArea20210323/index.html +++ b/meetings/2021/TechArea20210323/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210330/index.html b/meetings/2021/TechArea20210330/index.html index caa9b483d..3e004492f 100644 --- a/meetings/2021/TechArea20210330/index.html +++ b/meetings/2021/TechArea20210330/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210406/index.html b/meetings/2021/TechArea20210406/index.html index 39b0c7bbd..a44d17184 100644 --- a/meetings/2021/TechArea20210406/index.html +++ b/meetings/2021/TechArea20210406/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210413/index.html b/meetings/2021/TechArea20210413/index.html index 3336c87ab..268a6687a 100644 --- a/meetings/2021/TechArea20210413/index.html +++ b/meetings/2021/TechArea20210413/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210420/index.html b/meetings/2021/TechArea20210420/index.html index 9e3ec8c46..9c28abfd1 100644 --- a/meetings/2021/TechArea20210420/index.html +++ b/meetings/2021/TechArea20210420/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210504/index.html b/meetings/2021/TechArea20210504/index.html index 35392abfc..55f2ba76d 100644 --- a/meetings/2021/TechArea20210504/index.html +++ b/meetings/2021/TechArea20210504/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210511/index.html b/meetings/2021/TechArea20210511/index.html index 1e86c3c6f..1c4468239 100644 --- a/meetings/2021/TechArea20210511/index.html +++ b/meetings/2021/TechArea20210511/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210518/index.html b/meetings/2021/TechArea20210518/index.html index c141951f6..b3f153a18 100644 --- a/meetings/2021/TechArea20210518/index.html +++ b/meetings/2021/TechArea20210518/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210608/index.html b/meetings/2021/TechArea20210608/index.html index c8b03aa2e..a8967f3dc 100644 --- a/meetings/2021/TechArea20210608/index.html +++ b/meetings/2021/TechArea20210608/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210615/index.html b/meetings/2021/TechArea20210615/index.html index d8e9d0f6f..5006a41f7 100644 --- a/meetings/2021/TechArea20210615/index.html +++ b/meetings/2021/TechArea20210615/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210622/index.html b/meetings/2021/TechArea20210622/index.html index bf059f929..c9b9e27ce 100644 --- a/meetings/2021/TechArea20210622/index.html +++ b/meetings/2021/TechArea20210622/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210629/index.html b/meetings/2021/TechArea20210629/index.html index 085005af6..f3681a478 100644 --- a/meetings/2021/TechArea20210629/index.html +++ b/meetings/2021/TechArea20210629/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210706/index.html b/meetings/2021/TechArea20210706/index.html index 88d9966c4..6ccdb47e9 100644 --- a/meetings/2021/TechArea20210706/index.html +++ b/meetings/2021/TechArea20210706/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210713/index.html b/meetings/2021/TechArea20210713/index.html index 02557d0b8..1ef545f97 100644 --- a/meetings/2021/TechArea20210713/index.html +++ b/meetings/2021/TechArea20210713/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210720/index.html b/meetings/2021/TechArea20210720/index.html index 172d9e9bc..15260efb5 100644 --- a/meetings/2021/TechArea20210720/index.html +++ b/meetings/2021/TechArea20210720/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210727/index.html b/meetings/2021/TechArea20210727/index.html index a7d7355f0..85c144284 100644 --- a/meetings/2021/TechArea20210727/index.html +++ b/meetings/2021/TechArea20210727/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210803/index.html b/meetings/2021/TechArea20210803/index.html index 4849c4ff1..991fbd9a1 100644 --- a/meetings/2021/TechArea20210803/index.html +++ b/meetings/2021/TechArea20210803/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210810/index.html b/meetings/2021/TechArea20210810/index.html index 38b1d3368..fef9af3ef 100644 --- a/meetings/2021/TechArea20210810/index.html +++ b/meetings/2021/TechArea20210810/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210817/index.html b/meetings/2021/TechArea20210817/index.html index a829d322c..2f8a070b5 100644 --- a/meetings/2021/TechArea20210817/index.html +++ b/meetings/2021/TechArea20210817/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210824/index.html b/meetings/2021/TechArea20210824/index.html index e0ac202c0..d037a0341 100644 --- a/meetings/2021/TechArea20210824/index.html +++ b/meetings/2021/TechArea20210824/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210831/index.html b/meetings/2021/TechArea20210831/index.html index 78a4724f3..88eb5ca24 100644 --- a/meetings/2021/TechArea20210831/index.html +++ b/meetings/2021/TechArea20210831/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210907/index.html b/meetings/2021/TechArea20210907/index.html index 2e4dfc961..5c25450a9 100644 --- a/meetings/2021/TechArea20210907/index.html +++ b/meetings/2021/TechArea20210907/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210914/index.html b/meetings/2021/TechArea20210914/index.html index ad9e1fe97..a322711e8 100644 --- a/meetings/2021/TechArea20210914/index.html +++ b/meetings/2021/TechArea20210914/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20210928/index.html b/meetings/2021/TechArea20210928/index.html index c2357347c..c750d4acb 100644 --- a/meetings/2021/TechArea20210928/index.html +++ b/meetings/2021/TechArea20210928/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211005/index.html b/meetings/2021/TechArea20211005/index.html index b32ef9f6f..d5e5a9d3a 100644 --- a/meetings/2021/TechArea20211005/index.html +++ b/meetings/2021/TechArea20211005/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211012/index.html b/meetings/2021/TechArea20211012/index.html index 75929f5ed..8f8249653 100644 --- a/meetings/2021/TechArea20211012/index.html +++ b/meetings/2021/TechArea20211012/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211019/index.html b/meetings/2021/TechArea20211019/index.html index 72f2e74cc..b8290e7c9 100644 --- a/meetings/2021/TechArea20211019/index.html +++ b/meetings/2021/TechArea20211019/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211026/index.html b/meetings/2021/TechArea20211026/index.html index 17c83b120..c3b7e50f2 100644 --- a/meetings/2021/TechArea20211026/index.html +++ b/meetings/2021/TechArea20211026/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211102/index.html b/meetings/2021/TechArea20211102/index.html index 5fe06a36c..010055439 100644 --- a/meetings/2021/TechArea20211102/index.html +++ b/meetings/2021/TechArea20211102/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211109/index.html b/meetings/2021/TechArea20211109/index.html index 385776166..e296b6b44 100644 --- a/meetings/2021/TechArea20211109/index.html +++ b/meetings/2021/TechArea20211109/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211116/index.html b/meetings/2021/TechArea20211116/index.html index d1553324b..25b0fca6c 100644 --- a/meetings/2021/TechArea20211116/index.html +++ b/meetings/2021/TechArea20211116/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211123/index.html b/meetings/2021/TechArea20211123/index.html index 5ab2bdb38..9d7dc3d61 100644 --- a/meetings/2021/TechArea20211123/index.html +++ b/meetings/2021/TechArea20211123/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211130/index.html b/meetings/2021/TechArea20211130/index.html index 72f393db0..5fadaf407 100644 --- a/meetings/2021/TechArea20211130/index.html +++ b/meetings/2021/TechArea20211130/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211207/index.html b/meetings/2021/TechArea20211207/index.html index 3b96ca35c..d579b6713 100644 --- a/meetings/2021/TechArea20211207/index.html +++ b/meetings/2021/TechArea20211207/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2021/TechArea20211214/index.html b/meetings/2021/TechArea20211214/index.html index 50fa4b8ae..32779c41e 100644 --- a/meetings/2021/TechArea20211214/index.html +++ b/meetings/2021/TechArea20211214/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220104/index.html b/meetings/2022/TechArea20220104/index.html index 7110e3820..ab4f62f82 100644 --- a/meetings/2022/TechArea20220104/index.html +++ b/meetings/2022/TechArea20220104/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220111/index.html b/meetings/2022/TechArea20220111/index.html index 0afa84e7b..c3f271c07 100644 --- a/meetings/2022/TechArea20220111/index.html +++ b/meetings/2022/TechArea20220111/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220118/index.html b/meetings/2022/TechArea20220118/index.html index 38ba7343f..c71f34304 100644 --- a/meetings/2022/TechArea20220118/index.html +++ b/meetings/2022/TechArea20220118/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220125/index.html b/meetings/2022/TechArea20220125/index.html index f3d7f5851..7855b5f00 100644 --- a/meetings/2022/TechArea20220125/index.html +++ b/meetings/2022/TechArea20220125/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220201/index.html b/meetings/2022/TechArea20220201/index.html index f54d1a24a..5e2e6befd 100644 --- a/meetings/2022/TechArea20220201/index.html +++ b/meetings/2022/TechArea20220201/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220208/index.html b/meetings/2022/TechArea20220208/index.html index 14501706a..4a74cc15b 100644 --- a/meetings/2022/TechArea20220208/index.html +++ b/meetings/2022/TechArea20220208/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220222/index.html b/meetings/2022/TechArea20220222/index.html index 2f3c02cbe..f8d8ea3de 100644 --- a/meetings/2022/TechArea20220222/index.html +++ b/meetings/2022/TechArea20220222/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220301/index.html b/meetings/2022/TechArea20220301/index.html index 7544ea91e..4ca1a1dcb 100644 --- a/meetings/2022/TechArea20220301/index.html +++ b/meetings/2022/TechArea20220301/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220308/index.html b/meetings/2022/TechArea20220308/index.html index 5ece3110f..ffa779fd8 100644 --- a/meetings/2022/TechArea20220308/index.html +++ b/meetings/2022/TechArea20220308/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220322/index.html b/meetings/2022/TechArea20220322/index.html index 01d6e32d3..dff8a1f24 100644 --- a/meetings/2022/TechArea20220322/index.html +++ b/meetings/2022/TechArea20220322/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220329/index.html b/meetings/2022/TechArea20220329/index.html index cb17586d3..636eb89be 100644 --- a/meetings/2022/TechArea20220329/index.html +++ b/meetings/2022/TechArea20220329/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220405/index.html b/meetings/2022/TechArea20220405/index.html index c011206ee..e3917ef47 100644 --- a/meetings/2022/TechArea20220405/index.html +++ b/meetings/2022/TechArea20220405/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220419/index.html b/meetings/2022/TechArea20220419/index.html index e8d4c0b19..6c29b204f 100644 --- a/meetings/2022/TechArea20220419/index.html +++ b/meetings/2022/TechArea20220419/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220426/index.html b/meetings/2022/TechArea20220426/index.html index d21cc486b..882563228 100644 --- a/meetings/2022/TechArea20220426/index.html +++ b/meetings/2022/TechArea20220426/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220503/index.html b/meetings/2022/TechArea20220503/index.html index f7056bd88..3dbc7e67e 100644 --- a/meetings/2022/TechArea20220503/index.html +++ b/meetings/2022/TechArea20220503/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220510/index.html b/meetings/2022/TechArea20220510/index.html index bb73c9e7a..15c24b30a 100644 --- a/meetings/2022/TechArea20220510/index.html +++ b/meetings/2022/TechArea20220510/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220531/index.html b/meetings/2022/TechArea20220531/index.html index 9732c12e7..149a9de0e 100644 --- a/meetings/2022/TechArea20220531/index.html +++ b/meetings/2022/TechArea20220531/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220607/index.html b/meetings/2022/TechArea20220607/index.html index 2e3999613..cb49153b9 100644 --- a/meetings/2022/TechArea20220607/index.html +++ b/meetings/2022/TechArea20220607/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220621/index.html b/meetings/2022/TechArea20220621/index.html index 20d678a5b..57fbb6d6a 100644 --- a/meetings/2022/TechArea20220621/index.html +++ b/meetings/2022/TechArea20220621/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220628/index.html b/meetings/2022/TechArea20220628/index.html index 4b1d14f8f..b4062ce8d 100644 --- a/meetings/2022/TechArea20220628/index.html +++ b/meetings/2022/TechArea20220628/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220726/index.html b/meetings/2022/TechArea20220726/index.html index ddc231e34..b8d21a582 100644 --- a/meetings/2022/TechArea20220726/index.html +++ b/meetings/2022/TechArea20220726/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220802/index.html b/meetings/2022/TechArea20220802/index.html index 5155913d6..ff5adf95f 100644 --- a/meetings/2022/TechArea20220802/index.html +++ b/meetings/2022/TechArea20220802/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220809/index.html b/meetings/2022/TechArea20220809/index.html index 78f2b7842..5ab7a4e34 100644 --- a/meetings/2022/TechArea20220809/index.html +++ b/meetings/2022/TechArea20220809/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220816/index.html b/meetings/2022/TechArea20220816/index.html index 8549b4962..b6e3df36a 100644 --- a/meetings/2022/TechArea20220816/index.html +++ b/meetings/2022/TechArea20220816/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220823/index.html b/meetings/2022/TechArea20220823/index.html index 1884dc8a0..e50b2fcfe 100644 --- a/meetings/2022/TechArea20220823/index.html +++ b/meetings/2022/TechArea20220823/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220830/index.html b/meetings/2022/TechArea20220830/index.html index f050856ea..31e4b935a 100644 --- a/meetings/2022/TechArea20220830/index.html +++ b/meetings/2022/TechArea20220830/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220906/index.html b/meetings/2022/TechArea20220906/index.html index 102591cea..504fb0026 100644 --- a/meetings/2022/TechArea20220906/index.html +++ b/meetings/2022/TechArea20220906/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220913/index.html b/meetings/2022/TechArea20220913/index.html index 70c0e2dcb..4689ae3bf 100644 --- a/meetings/2022/TechArea20220913/index.html +++ b/meetings/2022/TechArea20220913/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220920/index.html b/meetings/2022/TechArea20220920/index.html index 90718676a..f8510f760 100644 --- a/meetings/2022/TechArea20220920/index.html +++ b/meetings/2022/TechArea20220920/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20220927/index.html b/meetings/2022/TechArea20220927/index.html index efc8685e9..0a249ad7a 100644 --- a/meetings/2022/TechArea20220927/index.html +++ b/meetings/2022/TechArea20220927/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221004/index.html b/meetings/2022/TechArea20221004/index.html index f9a97391d..710e11abc 100644 --- a/meetings/2022/TechArea20221004/index.html +++ b/meetings/2022/TechArea20221004/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221018/index.html b/meetings/2022/TechArea20221018/index.html index 962182b83..8a8741d51 100644 --- a/meetings/2022/TechArea20221018/index.html +++ b/meetings/2022/TechArea20221018/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221101/index.html b/meetings/2022/TechArea20221101/index.html index 3fd86f5da..5551b6e91 100644 --- a/meetings/2022/TechArea20221101/index.html +++ b/meetings/2022/TechArea20221101/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221108/index.html b/meetings/2022/TechArea20221108/index.html index 062534a1c..0e994a088 100644 --- a/meetings/2022/TechArea20221108/index.html +++ b/meetings/2022/TechArea20221108/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221115/index.html b/meetings/2022/TechArea20221115/index.html index 84a2c3a06..0ef2e477c 100644 --- a/meetings/2022/TechArea20221115/index.html +++ b/meetings/2022/TechArea20221115/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221122/index.html b/meetings/2022/TechArea20221122/index.html index f91a99d12..d8e35dbda 100644 --- a/meetings/2022/TechArea20221122/index.html +++ b/meetings/2022/TechArea20221122/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221129/index.html b/meetings/2022/TechArea20221129/index.html index 813f3ebe6..95d47432f 100644 --- a/meetings/2022/TechArea20221129/index.html +++ b/meetings/2022/TechArea20221129/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221206/index.html b/meetings/2022/TechArea20221206/index.html index a2139368d..9c8dbf8ba 100644 --- a/meetings/2022/TechArea20221206/index.html +++ b/meetings/2022/TechArea20221206/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221213/index.html b/meetings/2022/TechArea20221213/index.html index 99aab0610..f260a1251 100644 --- a/meetings/2022/TechArea20221213/index.html +++ b/meetings/2022/TechArea20221213/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2022/TechArea20221220/index.html b/meetings/2022/TechArea20221220/index.html index 3992958e5..265f8d711 100644 --- a/meetings/2022/TechArea20221220/index.html +++ b/meetings/2022/TechArea20221220/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230103/index.html b/meetings/2023/TechArea20230103/index.html index 7a3e0d2f7..25878de28 100644 --- a/meetings/2023/TechArea20230103/index.html +++ b/meetings/2023/TechArea20230103/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230117/index.html b/meetings/2023/TechArea20230117/index.html index 793fee174..2513bca4e 100644 --- a/meetings/2023/TechArea20230117/index.html +++ b/meetings/2023/TechArea20230117/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230124/index.html b/meetings/2023/TechArea20230124/index.html index 4a92e1c0c..139088735 100644 --- a/meetings/2023/TechArea20230124/index.html +++ b/meetings/2023/TechArea20230124/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230131/index.html b/meetings/2023/TechArea20230131/index.html index d2498b7a4..c458c2eb6 100644 --- a/meetings/2023/TechArea20230131/index.html +++ b/meetings/2023/TechArea20230131/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230207/index.html b/meetings/2023/TechArea20230207/index.html index 5e91d2a71..19eb54afc 100644 --- a/meetings/2023/TechArea20230207/index.html +++ b/meetings/2023/TechArea20230207/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230214/index.html b/meetings/2023/TechArea20230214/index.html index 8fd89653a..ce4dbdaa5 100644 --- a/meetings/2023/TechArea20230214/index.html +++ b/meetings/2023/TechArea20230214/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230221/index.html b/meetings/2023/TechArea20230221/index.html index 2236659fa..9d64d749c 100644 --- a/meetings/2023/TechArea20230221/index.html +++ b/meetings/2023/TechArea20230221/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230228/index.html b/meetings/2023/TechArea20230228/index.html index a2a1aff51..88ccfefc3 100644 --- a/meetings/2023/TechArea20230228/index.html +++ b/meetings/2023/TechArea20230228/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230314/index.html b/meetings/2023/TechArea20230314/index.html index 320bd06bd..aace4aa4b 100644 --- a/meetings/2023/TechArea20230314/index.html +++ b/meetings/2023/TechArea20230314/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230328/index.html b/meetings/2023/TechArea20230328/index.html index 4caa5cb92..807ce676f 100644 --- a/meetings/2023/TechArea20230328/index.html +++ b/meetings/2023/TechArea20230328/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230404/index.html b/meetings/2023/TechArea20230404/index.html index 060fb24f0..b946772e0 100644 --- a/meetings/2023/TechArea20230404/index.html +++ b/meetings/2023/TechArea20230404/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230418/index.html b/meetings/2023/TechArea20230418/index.html index 00de3778c..ebc62d115 100644 --- a/meetings/2023/TechArea20230418/index.html +++ b/meetings/2023/TechArea20230418/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230509/index.html b/meetings/2023/TechArea20230509/index.html index 0ea90e928..3a3913573 100644 --- a/meetings/2023/TechArea20230509/index.html +++ b/meetings/2023/TechArea20230509/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230516/index.html b/meetings/2023/TechArea20230516/index.html index 8209c81cc..17f346f4d 100644 --- a/meetings/2023/TechArea20230516/index.html +++ b/meetings/2023/TechArea20230516/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230523/index.html b/meetings/2023/TechArea20230523/index.html index c85bb6961..edbc0ac00 100644 --- a/meetings/2023/TechArea20230523/index.html +++ b/meetings/2023/TechArea20230523/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230530/index.html b/meetings/2023/TechArea20230530/index.html index 988ce2459..52a1f6814 100644 --- a/meetings/2023/TechArea20230530/index.html +++ b/meetings/2023/TechArea20230530/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230606/index.html b/meetings/2023/TechArea20230606/index.html index 79b958943..579484580 100644 --- a/meetings/2023/TechArea20230606/index.html +++ b/meetings/2023/TechArea20230606/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230613/index.html b/meetings/2023/TechArea20230613/index.html index 2be6b02e9..ae0f3580e 100644 --- a/meetings/2023/TechArea20230613/index.html +++ b/meetings/2023/TechArea20230613/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230620/index.html b/meetings/2023/TechArea20230620/index.html index 76567a4aa..208c26dfc 100644 --- a/meetings/2023/TechArea20230620/index.html +++ b/meetings/2023/TechArea20230620/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230627/index.html b/meetings/2023/TechArea20230627/index.html index 19a69a080..da470ba2a 100644 --- a/meetings/2023/TechArea20230627/index.html +++ b/meetings/2023/TechArea20230627/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230718/index.html b/meetings/2023/TechArea20230718/index.html index 1e4554921..afcda090c 100644 --- a/meetings/2023/TechArea20230718/index.html +++ b/meetings/2023/TechArea20230718/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230725/index.html b/meetings/2023/TechArea20230725/index.html index e98334d9f..7132df2f2 100644 --- a/meetings/2023/TechArea20230725/index.html +++ b/meetings/2023/TechArea20230725/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230801/index.html b/meetings/2023/TechArea20230801/index.html index 09b90da23..9844cc0d7 100644 --- a/meetings/2023/TechArea20230801/index.html +++ b/meetings/2023/TechArea20230801/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230808/index.html b/meetings/2023/TechArea20230808/index.html index ac22d90dd..dcd711bac 100644 --- a/meetings/2023/TechArea20230808/index.html +++ b/meetings/2023/TechArea20230808/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230815/index.html b/meetings/2023/TechArea20230815/index.html index fcd118570..358950516 100644 --- a/meetings/2023/TechArea20230815/index.html +++ b/meetings/2023/TechArea20230815/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230829/index.html b/meetings/2023/TechArea20230829/index.html index 138097316..0f464a462 100644 --- a/meetings/2023/TechArea20230829/index.html +++ b/meetings/2023/TechArea20230829/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230905/index.html b/meetings/2023/TechArea20230905/index.html index 6d0c522ed..99130399f 100644 --- a/meetings/2023/TechArea20230905/index.html +++ b/meetings/2023/TechArea20230905/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230919/index.html b/meetings/2023/TechArea20230919/index.html index 4a28a2f22..bb7b45c94 100644 --- a/meetings/2023/TechArea20230919/index.html +++ b/meetings/2023/TechArea20230919/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20230926/index.html b/meetings/2023/TechArea20230926/index.html index 751a4cb35..eb26aae35 100644 --- a/meetings/2023/TechArea20230926/index.html +++ b/meetings/2023/TechArea20230926/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231003/index.html b/meetings/2023/TechArea20231003/index.html index 905ce622b..bcc024a24 100644 --- a/meetings/2023/TechArea20231003/index.html +++ b/meetings/2023/TechArea20231003/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231010/index.html b/meetings/2023/TechArea20231010/index.html index 2aa852d3c..2a66430d4 100644 --- a/meetings/2023/TechArea20231010/index.html +++ b/meetings/2023/TechArea20231010/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231017/index.html b/meetings/2023/TechArea20231017/index.html index 6df68aef2..4b9196c2f 100644 --- a/meetings/2023/TechArea20231017/index.html +++ b/meetings/2023/TechArea20231017/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231024/index.html b/meetings/2023/TechArea20231024/index.html index a9dd505f8..2592ea6ad 100644 --- a/meetings/2023/TechArea20231024/index.html +++ b/meetings/2023/TechArea20231024/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231031/index.html b/meetings/2023/TechArea20231031/index.html index d9449afca..0b703901a 100644 --- a/meetings/2023/TechArea20231031/index.html +++ b/meetings/2023/TechArea20231031/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231107/index.html b/meetings/2023/TechArea20231107/index.html index dee669602..bae41f567 100644 --- a/meetings/2023/TechArea20231107/index.html +++ b/meetings/2023/TechArea20231107/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231114/index.html b/meetings/2023/TechArea20231114/index.html index d6acc1a98..a373589f5 100644 --- a/meetings/2023/TechArea20231114/index.html +++ b/meetings/2023/TechArea20231114/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231128/index.html b/meetings/2023/TechArea20231128/index.html index 6a564a999..98cea450f 100644 --- a/meetings/2023/TechArea20231128/index.html +++ b/meetings/2023/TechArea20231128/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231205/index.html b/meetings/2023/TechArea20231205/index.html index 8bc5fb289..5fea30acb 100644 --- a/meetings/2023/TechArea20231205/index.html +++ b/meetings/2023/TechArea20231205/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231212/index.html b/meetings/2023/TechArea20231212/index.html index d7c547878..1bcf2e415 100644 --- a/meetings/2023/TechArea20231212/index.html +++ b/meetings/2023/TechArea20231212/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2023/TechArea20231219/index.html b/meetings/2023/TechArea20231219/index.html index aea357b35..1b93eb4ac 100644 --- a/meetings/2023/TechArea20231219/index.html +++ b/meetings/2023/TechArea20231219/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2024/TechArea20240102/index.html b/meetings/2024/TechArea20240102/index.html index e3aeea3ba..a68935add 100644 --- a/meetings/2024/TechArea20240102/index.html +++ b/meetings/2024/TechArea20240102/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/2024/TechArea20240109/index.html b/meetings/2024/TechArea20240109/index.html index fb02654a4..e90fd0059 100644 --- a/meetings/2024/TechArea20240109/index.html +++ b/meetings/2024/TechArea20240109/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/meetings/TechAreaTemplate/index.html b/meetings/TechAreaTemplate/index.html index 517f0c745..71de0dd64 100644 --- a/meetings/TechAreaTemplate/index.html +++ b/meetings/TechAreaTemplate/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/operations/comanage/index.html b/operations/comanage/index.html index 1b1459a92..84f1916d0 100644 --- a/operations/comanage/index.html +++ b/operations/comanage/index.html @@ -606,6 +606,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + @@ -3489,13 +3501,13 @@

    The COManage peti -
  • + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/campus-cyberinfrastructure/index.html b/policy/campus-cyberinfrastructure/index.html index 175d3e232..c06bcce5c 100644 --- a/policy/campus-cyberinfrastructure/index.html +++ b/policy/campus-cyberinfrastructure/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/collab-bearer-tokens/index.html b/policy/collab-bearer-tokens/index.html index 5408ea09b..d00311f07 100644 --- a/policy/collab-bearer-tokens/index.html +++ b/policy/collab-bearer-tokens/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/community-testing/index.html b/policy/community-testing/index.html index 0b97f23a0..2b12a530f 100644 --- a/policy/community-testing/index.html +++ b/policy/community-testing/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/container-release/index.html b/policy/container-release/index.html index 616b2560e..458cfba1e 100644 --- a/policy/container-release/index.html +++ b/policy/container-release/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/cream-support/index.html b/policy/cream-support/index.html index 6200648ae..b72c42ef9 100644 --- a/policy/cream-support/index.html +++ b/policy/cream-support/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/external-oasis-repos/index.html b/policy/external-oasis-repos/index.html index a7f240d96..820c79381 100644 --- a/policy/external-oasis-repos/index.html +++ b/policy/external-oasis-repos/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/flexible-release-model/index.html b/policy/flexible-release-model/index.html index fd59a7f9c..f0c13b14b 100644 --- a/policy/flexible-release-model/index.html +++ b/policy/flexible-release-model/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/globus-toolkit/index.html b/policy/globus-toolkit/index.html index a733796eb..df49c96ed 100644 --- a/policy/globus-toolkit/index.html +++ b/policy/globus-toolkit/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/gridftp-gsi-migration/index.html b/policy/gridftp-gsi-migration/index.html index 575cf9a29..ee41f1c77 100644 --- a/policy/gridftp-gsi-migration/index.html +++ b/policy/gridftp-gsi-migration/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/gums-retire/index.html b/policy/gums-retire/index.html index 11ea342a3..ca1249a2f 100644 --- a/policy/gums-retire/index.html +++ b/policy/gums-retire/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/new-ospool-user/index.html b/policy/new-ospool-user/index.html index d3e723368..c0d563006 100644 --- a/policy/new-ospool-user/index.html +++ b/policy/new-ospool-user/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/service-migrations-spring-2018/index.html b/policy/service-migrations-spring-2018/index.html index 8137046f3..102a36c35 100644 --- a/policy/service-migrations-spring-2018/index.html +++ b/policy/service-migrations-spring-2018/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/software-release/index.html b/policy/software-release/index.html index 78c78a582..1345513de 100644 --- a/policy/software-release/index.html +++ b/policy/software-release/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/software-support/index.html b/policy/software-support/index.html index d592c333c..81b8db1aa 100644 --- a/policy/software-support/index.html +++ b/policy/software-support/index.html @@ -539,6 +539,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + @@ -3614,7 +3626,7 @@

    Jira&par

    diff --git a/policy/topology-registration/index.html b/policy/topology-registration/index.html index 61e250f30..406f88705 100644 --- a/policy/topology-registration/index.html +++ b/policy/topology-registration/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/policy/voms-admin-retire/index.html b/policy/voms-admin-retire/index.html index 927c6e902..a322f6eca 100644 --- a/policy/voms-admin-retire/index.html +++ b/policy/voms-admin-retire/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/projects/sha2-support/index.html b/projects/sha2-support/index.html index 9002aaa95..81e0dc815 100644 --- a/projects/sha2-support/index.html +++ b/projects/sha2-support/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/acceptance-testing/index.html b/release/acceptance-testing/index.html index 9e12109a7..87e3ec1e4 100644 --- a/release/acceptance-testing/index.html +++ b/release/acceptance-testing/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/announce-rft-packages/index.html b/release/announce-rft-packages/index.html index 970bfbfaf..a6b86a52e 100644 --- a/release/announce-rft-packages/index.html +++ b/release/announce-rft-packages/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/cut-sw-release/index.html b/release/cut-sw-release/index.html index 25e67bd43..025fb5cda 100644 --- a/release/cut-sw-release/index.html +++ b/release/cut-sw-release/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/empty-pkgs/index.html b/release/empty-pkgs/index.html index dd0941eda..b54d0e7b6 100644 --- a/release/empty-pkgs/index.html +++ b/release/empty-pkgs/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/itb-testing/index.html b/release/itb-testing/index.html index 420a888ca..6a6a36476 100644 --- a/release/itb-testing/index.html +++ b/release/itb-testing/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/new-os-series/index.html b/release/new-os-series/index.html index b295c711a..3a36c31d0 100644 --- a/release/new-os-series/index.html +++ b/release/new-os-series/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/new-release-series/index.html b/release/new-release-series/index.html index 7e475eb32..d6ffdff0c 100644 --- a/release/new-release-series/index.html +++ b/release/new-release-series/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/release/release-eol/index.html b/release/release-eol/index.html index 4297f10c7..d81bd371e 100644 --- a/release/release-eol/index.html +++ b/release/release-eol/index.html @@ -537,6 +537,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/search/search_index.json b/search/search_index.json index a3a9aed9c..7bcb1b83c 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -1 +1 @@ -{"config":{"lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"OSG Technology Area \u00b6 Welcome to the home page of the OSG Technology Team documentation area! If you are looking for site administrator documentation, please visit the OSG Documentation page . The Team \u00b6 Software and Release Technology Brian Lin (software manager) Brian Bockelman (manager) (15%) Mat Selmeci Derek Weitzel (50%) Matt Westphall (50%) Diego Davila (50%) Tim Theisen (release manager) (50%) Contact Us \u00b6 software-discuss@osg-htc.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org Meetings \u00b6 When: Every Tuesday, 9:30 a.m. (U.S. Central) Where: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Meeting note archives can be found directly in the GitHub repository .","title":"Home"},{"location":"#osg-technology-area","text":"Welcome to the home page of the OSG Technology Team documentation area! If you are looking for site administrator documentation, please visit the OSG Documentation page .","title":"OSG Technology Area"},{"location":"#the-team","text":"Software and Release Technology Brian Lin (software manager) Brian Bockelman (manager) (15%) Mat Selmeci Derek Weitzel (50%) Matt Westphall (50%) Diego Davila (50%) Tim Theisen (release manager) (50%)","title":"The Team"},{"location":"#contact-us","text":"software-discuss@osg-htc.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org","title":"Contact Us"},{"location":"#meetings","text":"When: Every Tuesday, 9:30 a.m. (U.S. Central) Where: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Meeting note archives can be found directly in the GitHub repository .","title":"Meetings"},{"location":"documentation/markdown-migration/","text":"Migrating to Markdown \u00b6 As part of the TWiki retirement (the read-only target date of Oct 1, 2017, with a shutdown date in 2018), we will need to convert the OSG Software and Release3 docs from TWiki syntax to Markdown . The following document outlines the conversion process and conventions. Choosing the git repository \u00b6 First you will need to choose which git repoository you will be working with: If you are converting a document from... Use this github repository... SoftwareTeam technology Release3 docs Once you've chosen the target repository for your document, move onto the next section and pick your conversion method. Automatic TWiki conversion \u00b6 Note If you are only archiving the documents, skip to this section . Choose one of the following methods for converting TWiki documents: Using our own docker conversion image (recommended) Directly using pandoc and mkdocs on your own machine Using docker \u00b6 The twiki-converter docker image can be used to preview the document tree via a mkdocs development server, archive TWiki documents, and convert documents to Markdown via pandoc . The image is available on osghost , otherwise, it is availble on dockerhub . user@host $ docker pull opensciencegrid/docker-twiki-converter Requirements \u00b6 To perform a document migration using docker, you will need the following tools and accounts: Fork and clone the repository that you chose in the above section A host with a running docker service sudo or membership in the docker group If you cannot install the above tools locally, they are available on osghost . Speak with Brian L for access. Preparing the git repository \u00b6 cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch master Replace with a name of your choice Change to the branch you just created user@host $ git checkout Replace with the name you chose in the step above Previewing the document tree \u00b6 When starting a twiki-converter docker container, it expects your local github repository to be mounted in /source so that any changes made to the repository are reflected in the mkdocs development server. To start a docker container based off of the twiki-converter docker image: Create a container from the image with the following command: user@host $ docker run -d -v :/source -p 8000 opensciencegrid/docker-twiki-converter Change for the directory where you have cloned the repo. The above command should return the container ID, which will be used in subsequent commands. Note If the docker container exits immediately, remove the -d option for details. If you see permission denied errors, you may need to disable SELinux or put it in permissive mode. To find the port that your development server is listening on, use the container ID (you should only need the first few chars of the ID) returned from the previous command: user@host $ docker port Change for the value returned by the execution of the previous command Access the development server in your browser via http://osghost.chtc.wisc.edu: or localhost: for containers run on osghost or locally, respectively. osghost has a restrictive firewall so if you have issues accessing your container from outside of the UW-Madison campus, use an SSH tunnel to map the osghost port to a local port. Converting documents \u00b6 The docker image contains a convenience script, convert-twiki for saving archives and converting them to Markdown. To run the script in a running container, run the following command: user@host $ docker exec convert-twiki Where is the docker container ID and is the link to the TWiki document that you want to convert, e.g. https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess . This will result in an archive of the twiki doc, archive/SoftwareDevelopmentProcess , in your local repo and a converted copy, SoftwareDevelopmentProcess.md , placed into the root of your local github repository. If the twiki url is for a specific revision of the document, a .rNN will be included in the output filenames. Warning If the above command does not complete quickly, it means that Pandoc is having an issue with a specific section of the document. See Troubleshooting conversion for next steps. To see the converted document in your browser: Rename, move the converted document into a folder in docs/ . Document file names should be lowercase, - delimited, and descriptive but concise, e.g. markdown-migration.md or cutting-release.md It's not important to get the name/location correct on the first try as this can be discussed in the pull request sudo chown the archived and converted documents to be owned by you Add the document to the pages: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Refresh the document tree in your browser Once you can view the converted document in your browser, move onto the next section Troubleshooting conversion \u00b6 Pandoc sometimes has issues converting documents and requires manual intervention by removing whichever section is causing issues in the conversion. Copy the archive of the document into the root of your git repository Kill the process in the docker container: user@host $ docker exec pkill -9 pandoc Where is the docker container ID Remove a section from the copy of the archive to find the problematic section (recommendation: use a binary search strategy) Run pandoc manually: user@host $ docker exec pandoc -f twiki -t markdown_github > Where is the docker container ID, is the the file you copied in the first step and is the resulting .md file Repeat steps 2-4 until you've narrowed down the problematic section Manually convert the offending section Conversion without Docker \u00b6 If you've already used the docker method , skip to the section about completing the conversion . Requirements \u00b6 This method requires the following: Fork and clone the repository that you chose in the above section pandoc (> 1.16) mkdocs MarkdownHighlight pygments Preparing the git repository \u00b6 cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch master Replace with a name of your choice 5. Change to the branch you just created user@host $ git checkout Replace with the name you chose in the step above Archiving the TWiki document \u00b6 Follow the instructions for archival then continue to the next section to convert the document with pandoc. Initial conversion with Pandoc \u00b6 Pandoc is a tool that's useful for automated conversion of markdown languages. Once installed (alternatively, run pandoc via docker ), run the following command to convert TWiki to Markdown: $ pandoc -f twiki -t markdown_github > Where is the path to initial document in raw TWiki and is the path to the resulting document in GitHub Markdown. Note If you don't see output from the above command quickly, it means that Pandoc is having an issue with a specific section of the document. Stop the command (or docker container), find and temporarily remove the offending section, convert the remainder of the document with Pandoc, and manually convert the offending section. Previewing your document(s) with Mkdocs \u00b6 Mkdocs has a development mode that can be used to preview documents as you work on them and is available via package manager or pip . Once installed , add your document(s) to the pages section of mkdocs.yml and launch the mkdocs server with the following command from the dir containing mkdocs.yml : $ PYTHONPATH = src/ mkdocs serve Access the server at http://127.0.0.1:8000 and navigate to the document you're working on. It's useful to open the original TWiki doc in an adjacent tab or window to quickly compare the two. Completing the conversion \u00b6 Manual review of the automatically converted documents are required since the automatic conversion process isn't perfect. This section contains a list of problems commonly encountered in automatically converted documents. Visit the style guide to ensure that the document meets all style guidelines. Archiving Documents \u00b6 If the document is slated for archival (check if it says \"yes\" in the \"archived\" column of the spreadsheet), just download the document to the archive folder of your local git repository: user@host $ cd technology/ user@host $ curl '?raw=text' | iconv -f windows-1252 > archive/ Where is the link to the TWiki document that you want to download and is the name that will receive the archived file For example: user@host $ cd technology user@host $ curl 'https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/SHA2Compliance?raw=text' | iconv -f windows-1252 > archive/SHA2Compliance After downloading the document, continue onto the next section to walk through pull request submission. Submitting the pull request \u00b6 Stage the archived raw TWiki (as well as the converted Markdown document(s) and mkdocs.yml if you are converting the document): user@host $ git add mkdocs.yml archive/ Where is the name of the archived document and is the path to the .md file Commit and push your changes to your GitHub repo: user@host $ git commit -m \"\" user@host $ git push origin Change for a meaningful text that describes the conversion done and with the name chosen in the 3rd step of the Preparing the git repository section Open your browser and navigate to your GitHub fork Submit a pull request containing with the following body: - [ ] Enter date into \"Migrated\" column of google sheet An example of is: https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess If you are migrating a document, also add this task: - [ ] Add migration header to TWiki document If you are archiving a document, add this task: - [ ] Move TWiki document to the trash See an example pull request here . After the pull request \u00b6 After the pull request is merged, replace the contents of TWiki document with the div if you're migrating the document, linking to the location of the migrated document:
    This document has been migrated to !GitHub (). If you wish to see the old TWiki document, use the TWiki history below. Background: At the end of year (2017), the TWiki will be retired in favor of !GitHub. You can find the various TWiki webs and their new !GitHub locations listed below: * Release3: https://www.opensciencegrid.org/docs ([[https://github.com/opensciencegrid/docs/tree/master/archive][archive]]) * !SoftwareTeam: https://www.opensciencegrid.org/technology ([[https://github.com/opensciencegrid/technology/tree/master/archive][archive]])
    If you are archiving a document, move it to the trash instead. Once the document has been updated or trashed, add the date to the spreadsheet and go back to your pull request and mark your tasks as complete. For example, if you completed the migration of a document: - [X] Enter date into \"Migrated\" column of google sheet - [X] Add migration div to TWiki document Currently, we do not recommend changing backlinks (links on other twiki pages that refer to the Twiki page you are migrating) to point at the new GitHub URL. This is to provide a simple reminder to users that the migration will occur, and also is likely low priority regardless as all pages will eventually migrate to GitHub. This advice may change in the future as we gain experience with this transition. Reviewing pull requests \u00b6 To review pull requests, cd into the dir containing your git repository and check out the requester's branch, which the twiki-converter container should automatically notice. Here's an example checking out Brian's cut-sw-release branch of the technology repository: # Add the requester 's repo as a remote if you haven' t already user@host $ git remote add blin https://www.github.com/brianhlin/technology.git user@host $ git fetch --all user@host $ git checkout blin/cut-sw-release Refresh your browser and navigate to the document in the request.","title":"Migrating Documents to Markdown"},{"location":"documentation/markdown-migration/#migrating-to-markdown","text":"As part of the TWiki retirement (the read-only target date of Oct 1, 2017, with a shutdown date in 2018), we will need to convert the OSG Software and Release3 docs from TWiki syntax to Markdown . The following document outlines the conversion process and conventions.","title":"Migrating to Markdown"},{"location":"documentation/markdown-migration/#choosing-the-git-repository","text":"First you will need to choose which git repoository you will be working with: If you are converting a document from... Use this github repository... SoftwareTeam technology Release3 docs Once you've chosen the target repository for your document, move onto the next section and pick your conversion method.","title":"Choosing the git repository"},{"location":"documentation/markdown-migration/#automatic-twiki-conversion","text":"Note If you are only archiving the documents, skip to this section . Choose one of the following methods for converting TWiki documents: Using our own docker conversion image (recommended) Directly using pandoc and mkdocs on your own machine","title":"Automatic TWiki conversion"},{"location":"documentation/markdown-migration/#using-docker","text":"The twiki-converter docker image can be used to preview the document tree via a mkdocs development server, archive TWiki documents, and convert documents to Markdown via pandoc . The image is available on osghost , otherwise, it is availble on dockerhub . user@host $ docker pull opensciencegrid/docker-twiki-converter","title":"Using docker"},{"location":"documentation/markdown-migration/#requirements","text":"To perform a document migration using docker, you will need the following tools and accounts: Fork and clone the repository that you chose in the above section A host with a running docker service sudo or membership in the docker group If you cannot install the above tools locally, they are available on osghost . Speak with Brian L for access.","title":"Requirements"},{"location":"documentation/markdown-migration/#preparing-the-git-repository","text":"cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch master Replace with a name of your choice Change to the branch you just created user@host $ git checkout Replace with the name you chose in the step above","title":"Preparing the git repository"},{"location":"documentation/markdown-migration/#previewing-the-document-tree","text":"When starting a twiki-converter docker container, it expects your local github repository to be mounted in /source so that any changes made to the repository are reflected in the mkdocs development server. To start a docker container based off of the twiki-converter docker image: Create a container from the image with the following command: user@host $ docker run -d -v :/source -p 8000 opensciencegrid/docker-twiki-converter Change for the directory where you have cloned the repo. The above command should return the container ID, which will be used in subsequent commands. Note If the docker container exits immediately, remove the -d option for details. If you see permission denied errors, you may need to disable SELinux or put it in permissive mode. To find the port that your development server is listening on, use the container ID (you should only need the first few chars of the ID) returned from the previous command: user@host $ docker port Change for the value returned by the execution of the previous command Access the development server in your browser via http://osghost.chtc.wisc.edu: or localhost: for containers run on osghost or locally, respectively. osghost has a restrictive firewall so if you have issues accessing your container from outside of the UW-Madison campus, use an SSH tunnel to map the osghost port to a local port.","title":"Previewing the document tree"},{"location":"documentation/markdown-migration/#converting-documents","text":"The docker image contains a convenience script, convert-twiki for saving archives and converting them to Markdown. To run the script in a running container, run the following command: user@host $ docker exec convert-twiki Where is the docker container ID and is the link to the TWiki document that you want to convert, e.g. https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess . This will result in an archive of the twiki doc, archive/SoftwareDevelopmentProcess , in your local repo and a converted copy, SoftwareDevelopmentProcess.md , placed into the root of your local github repository. If the twiki url is for a specific revision of the document, a .rNN will be included in the output filenames. Warning If the above command does not complete quickly, it means that Pandoc is having an issue with a specific section of the document. See Troubleshooting conversion for next steps. To see the converted document in your browser: Rename, move the converted document into a folder in docs/ . Document file names should be lowercase, - delimited, and descriptive but concise, e.g. markdown-migration.md or cutting-release.md It's not important to get the name/location correct on the first try as this can be discussed in the pull request sudo chown the archived and converted documents to be owned by you Add the document to the pages: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Refresh the document tree in your browser Once you can view the converted document in your browser, move onto the next section","title":"Converting documents"},{"location":"documentation/markdown-migration/#troubleshooting-conversion","text":"Pandoc sometimes has issues converting documents and requires manual intervention by removing whichever section is causing issues in the conversion. Copy the archive of the document into the root of your git repository Kill the process in the docker container: user@host $ docker exec pkill -9 pandoc Where is the docker container ID Remove a section from the copy of the archive to find the problematic section (recommendation: use a binary search strategy) Run pandoc manually: user@host $ docker exec pandoc -f twiki -t markdown_github > Where is the docker container ID, is the the file you copied in the first step and is the resulting .md file Repeat steps 2-4 until you've narrowed down the problematic section Manually convert the offending section","title":"Troubleshooting conversion"},{"location":"documentation/markdown-migration/#conversion-without-docker","text":"If you've already used the docker method , skip to the section about completing the conversion .","title":"Conversion without Docker"},{"location":"documentation/markdown-migration/#requirements_1","text":"This method requires the following: Fork and clone the repository that you chose in the above section pandoc (> 1.16) mkdocs MarkdownHighlight pygments","title":"Requirements"},{"location":"documentation/markdown-migration/#preparing-the-git-repository_1","text":"cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch master Replace with a name of your choice 5. Change to the branch you just created user@host $ git checkout Replace with the name you chose in the step above","title":"Preparing the git repository"},{"location":"documentation/markdown-migration/#archiving-the-twiki-document","text":"Follow the instructions for archival then continue to the next section to convert the document with pandoc.","title":"Archiving the TWiki document"},{"location":"documentation/markdown-migration/#initial-conversion-with-pandoc","text":"Pandoc is a tool that's useful for automated conversion of markdown languages. Once installed (alternatively, run pandoc via docker ), run the following command to convert TWiki to Markdown: $ pandoc -f twiki -t markdown_github > Where is the path to initial document in raw TWiki and is the path to the resulting document in GitHub Markdown. Note If you don't see output from the above command quickly, it means that Pandoc is having an issue with a specific section of the document. Stop the command (or docker container), find and temporarily remove the offending section, convert the remainder of the document with Pandoc, and manually convert the offending section.","title":"Initial conversion with Pandoc"},{"location":"documentation/markdown-migration/#previewing-your-documents-with-mkdocs","text":"Mkdocs has a development mode that can be used to preview documents as you work on them and is available via package manager or pip . Once installed , add your document(s) to the pages section of mkdocs.yml and launch the mkdocs server with the following command from the dir containing mkdocs.yml : $ PYTHONPATH = src/ mkdocs serve Access the server at http://127.0.0.1:8000 and navigate to the document you're working on. It's useful to open the original TWiki doc in an adjacent tab or window to quickly compare the two.","title":"Previewing your document(s) with Mkdocs"},{"location":"documentation/markdown-migration/#completing-the-conversion","text":"Manual review of the automatically converted documents are required since the automatic conversion process isn't perfect. This section contains a list of problems commonly encountered in automatically converted documents. Visit the style guide to ensure that the document meets all style guidelines.","title":"Completing the conversion"},{"location":"documentation/markdown-migration/#archiving-documents","text":"If the document is slated for archival (check if it says \"yes\" in the \"archived\" column of the spreadsheet), just download the document to the archive folder of your local git repository: user@host $ cd technology/ user@host $ curl '?raw=text' | iconv -f windows-1252 > archive/ Where is the link to the TWiki document that you want to download and is the name that will receive the archived file For example: user@host $ cd technology user@host $ curl 'https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/SHA2Compliance?raw=text' | iconv -f windows-1252 > archive/SHA2Compliance After downloading the document, continue onto the next section to walk through pull request submission.","title":"Archiving Documents"},{"location":"documentation/markdown-migration/#submitting-the-pull-request","text":"Stage the archived raw TWiki (as well as the converted Markdown document(s) and mkdocs.yml if you are converting the document): user@host $ git add mkdocs.yml archive/ Where is the name of the archived document and is the path to the .md file Commit and push your changes to your GitHub repo: user@host $ git commit -m \"\" user@host $ git push origin Change for a meaningful text that describes the conversion done and with the name chosen in the 3rd step of the Preparing the git repository section Open your browser and navigate to your GitHub fork Submit a pull request containing with the following body: - [ ] Enter date into \"Migrated\" column of google sheet An example of is: https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess If you are migrating a document, also add this task: - [ ] Add migration header to TWiki document If you are archiving a document, add this task: - [ ] Move TWiki document to the trash See an example pull request here .","title":"Submitting the pull request"},{"location":"documentation/markdown-migration/#after-the-pull-request","text":"After the pull request is merged, replace the contents of TWiki document with the div if you're migrating the document, linking to the location of the migrated document:
    This document has been migrated to !GitHub (). If you wish to see the old TWiki document, use the TWiki history below. Background: At the end of year (2017), the TWiki will be retired in favor of !GitHub. You can find the various TWiki webs and their new !GitHub locations listed below: * Release3: https://www.opensciencegrid.org/docs ([[https://github.com/opensciencegrid/docs/tree/master/archive][archive]]) * !SoftwareTeam: https://www.opensciencegrid.org/technology ([[https://github.com/opensciencegrid/technology/tree/master/archive][archive]])
    If you are archiving a document, move it to the trash instead. Once the document has been updated or trashed, add the date to the spreadsheet and go back to your pull request and mark your tasks as complete. For example, if you completed the migration of a document: - [X] Enter date into \"Migrated\" column of google sheet - [X] Add migration div to TWiki document Currently, we do not recommend changing backlinks (links on other twiki pages that refer to the Twiki page you are migrating) to point at the new GitHub URL. This is to provide a simple reminder to users that the migration will occur, and also is likely low priority regardless as all pages will eventually migrate to GitHub. This advice may change in the future as we gain experience with this transition.","title":"After the pull request"},{"location":"documentation/markdown-migration/#reviewing-pull-requests","text":"To review pull requests, cd into the dir containing your git repository and check out the requester's branch, which the twiki-converter container should automatically notice. Here's an example checking out Brian's cut-sw-release branch of the technology repository: # Add the requester 's repo as a remote if you haven' t already user@host $ git remote add blin https://www.github.com/brianhlin/technology.git user@host $ git fetch --all user@host $ git checkout blin/cut-sw-release Refresh your browser and navigate to the document in the request.","title":"Reviewing pull requests"},{"location":"documentation/publish-osg-pages/","text":"Publishing OSG Pages with MkDocs \u00b6 The OSG uses MkDocs for site documentation and team-specific web pages (e.g. https://osg-htc.org/technology/ ). This document contains instructions for creating a new OSG area through GitHub and transitioning an existing MkDocs GitHub repository from Travis CI to GitHub Actions . Creating New Pages \u00b6 Need assistance? If you need any assistance with setting up your GitHub repository, please reach out to help@osg-htc.org . This document assumes that you are an administrator of the opensciencegrid GitHub organization. Before starting, make sure that you have the git and gem tools installed. Create a new public repository in the opensciencegrid organization (referred to as in the rest of this document) Check the box marked Initialize this repository with a README Identify the repository as using mkdocs: On the repository home page (i.e., https://github.com/opensciencegrid/ ), click the gear button in the top right (next to \"About\") In the topics field, add mkdocs Click the \u201cSave Changes\u201d button Clone the repository and cd into the directory: git clone https://github.com/opensciencegrid/.git cd Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md and populate the LICENSE file with a Creative Commons Attribution 4.0 license : wget https://creativecommons.org/licenses/by/4.0/legalcode.txt > LICENSE Create and encrypt the repository deploy key Generate the repository deploy key: ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-key -N '' Install the travis gem: gem install travis Login using your GitHub credentials: travis login --com Enable the repository in Travis: travis enable --com -r opensciencegrid/ Encrypt the deploy key and temporarily save the output (you will need the hashes later for .travis.env ): travis encrypt-file --com deploy-key Stage and commit your files: git add LICENSE README.md deploy-key.enc git commit -m \"Prepare the repository for Travis-CI deployment\" Danger Do NOT commit the unencrypted deploy-key ! Add the contents of deploy-key.pub to your repository's list of deploy keys . Make sure to check Allow write access . Follow these instructions to add the doc-ci-scripts sub-module Use the mkdocs-v1 branch of the doc-ci-scripts submodule. Create mkdocs.yml containing the following: site_name: site_url: https://osg-htc.org/<REPO NAME> repo_name: https://github.com/osg-htc/<REPO NAME> theme: name: material nav: - Home: 'index.md' markdown_extensions: - admonition - codehilite: guess_lang: False - meta - toc: permalink: True Create a docs directory containing an index.md that will be your home page. Stage and commit these changes: git add mkdocs.yml docs/index.md git commit -m \"Staging initial web page contents\" Push local changes to the GitHub repository: git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME> Contact help@osg-htc.org to request repository backups to UW-Madison. Creating an ITB Area \u00b6 This section describes creating an ITB repository for a documentation area created in the previous section Create a new repository in the opensciencegrid organization and name it <REPO NAME>-itb . For example, an ITB area for the docs repository has a repository name of docs-itb . The ITB repository will be referred to as <ITB REPO NAME> in the rest of this document. Check the box marked Initialize this repository with a README Once created, add the mkdocs topic by clicking on the \"Add topics\" button Clone the repository and cd into the directory: git clone git@github.com:opensciencegrid/<ITB REPO NAME> cd <ITB REPO NAME> Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md In the non-ITB repository, create and encrypt the ITB repository deploy key cd into the non-ITB repository and generate the ITB deploy key cd <REPO NAME> ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-itb Install the travis gem: gem install travis Encrypt the deploy key: travis encrypt-file deploy-itb Update .travis.env with the appropriate ITB values Add and commit your files: git add .travis.env deploy-itb.enc git commit -m \"Add ITB deployment\" Danger Do NOT commit the unencrypted deploy-itb ! Add deploy-itb.pub to the ITB repository's list of deploy keys . Make sure to check Allow write access . Still in the non-ITB repository, push your local changes to the GitHub repository git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME> Transitioning to GitHub Actions \u00b6 Need assistance? If you need any assistance with transitioning your repository to GitHub actions, please reach out to help@osg-htc.org . When originally developed, OSG MkDocs repositories were set up to automatically publish web page changes through Travis CI . But in November 2020, Travis CI changed their pricing model so we are moving the automatic publishing infrastructure to GitHub Actions and using this opportunity to also upgrade the version of MkDocs. To ensure that your pages continue to be autmoatically published you will need to prepare your repository for the new version of MkDocs, disable Travis CI, and enable GitHub Actions. Preparing the repository \u00b6 Before upgrading, you must fix the following incompatibilities: Rename the pages: section of mkdocs.yml to nav: . The section contents are identical; only the name is changing. Update all of the links in the documents as follows: Ensure links end in .md Ensure links are document-relative, not site-relative For example, links should be of the form ../software/development-process.md instead of /software/development-process . Push your changes to your fork and create a pull request Previewing your pages with Docker If you would like to ensure the correctness of your fixes, run the following command: docker run -it -v ${PWD}/docs -p 8000:8000 squidfunk/mkdocs-material:6.1.4 After running this command, enter localhost:8000 in your browser to preview your pages. Saved changes made to .md files are automatically updated in your browser! Disabling Travis CI \u00b6 After you've prepared your repository for the transition, disable Travis CI by removing related files from it. Perform the following actions from the command-line: Create a fresh clone of the repository that is still using Travis CI: git clone https://github.com/opensciencegrid/<GIT REPOSITORY> Important For the rest of the steps in this documentation to work, you should create a new clone of the repository using the above command, even if you already have an existing copy! cd into the directory containing the repository (should be the same as <GIT REPOSITORY> by default) Remove all of the Travs CI related files: git rm ci git rm .travis.env deploy-key.enc .travis.yml Commit your changes: git commit -am \"Disable Travis CI\" Push your changes (you will be prompted for your GitHub credentials): git push origin master Enabling GitHub Actions \u00b6 The new method for validating and publishing OSG pages for a MkDocs repository can be enabled entirely through the GitHub web interface : Navigate to the opensciencegrid fork of the GitHub repository in your web browser, e.g. https://github.com/opensciencegrid/docs/ Click on the Actions tab: Find the Publish MkDocs static HTML workflow by the Open Science Grid and click the Set up this workflow button: Click on the Start commit drop-down button then click Commit new file : Navigate to the Actions tab to verify your transition. If you see green check marks, your pages are now being published with GitHub Actions! (Optional) Enable the Validate MkDocs Static HTML workflow to check for broken links and markdown correctness of pull requests to the repository. Navigate to the Actions tab as before Click on the New Workflow button: Find the Validate MkDocs static HTML workflow by the Open Science Grid and click Set up this workflow As before, click on the Start commit drop-down button then click Commit new file","title":"Publishing OSG pages"},{"location":"documentation/publish-osg-pages/#publishing-osg-pages-with-mkdocs","text":"The OSG uses MkDocs for site documentation and team-specific web pages (e.g. https://osg-htc.org/technology/ ). This document contains instructions for creating a new OSG area through GitHub and transitioning an existing MkDocs GitHub repository from Travis CI to GitHub Actions .","title":"Publishing OSG Pages with MkDocs"},{"location":"documentation/publish-osg-pages/#creating-new-pages","text":"Need assistance? If you need any assistance with setting up your GitHub repository, please reach out to help@osg-htc.org . This document assumes that you are an administrator of the opensciencegrid GitHub organization. Before starting, make sure that you have the git and gem tools installed. Create a new public repository in the opensciencegrid organization (referred to as <REPO NAME> in the rest of this document) Check the box marked Initialize this repository with a README Identify the repository as using mkdocs: On the repository home page (i.e., https://github.com/opensciencegrid/<REPO NAME> ), click the gear button in the top right (next to \"About\") In the topics field, add mkdocs Click the \u201cSave Changes\u201d button Clone the repository and cd into the directory: git clone https://github.com/opensciencegrid/<REPO NAME>.git cd <REPO NAME> Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md and populate the LICENSE file with a Creative Commons Attribution 4.0 license : wget https://creativecommons.org/licenses/by/4.0/legalcode.txt > LICENSE Create and encrypt the repository deploy key Generate the repository deploy key: ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-key -N '' Install the travis gem: gem install travis Login using your GitHub credentials: travis login --com Enable the repository in Travis: travis enable --com -r opensciencegrid/<REPO NAME> Encrypt the deploy key and temporarily save the output (you will need the hashes later for .travis.env ): travis encrypt-file --com deploy-key Stage and commit your files: git add LICENSE README.md deploy-key.enc git commit -m \"Prepare the repository for Travis-CI deployment\" Danger Do NOT commit the unencrypted deploy-key ! Add the contents of deploy-key.pub to your repository's list of deploy keys . Make sure to check Allow write access . Follow these instructions to add the doc-ci-scripts sub-module Use the mkdocs-v1 branch of the doc-ci-scripts submodule. Create mkdocs.yml containing the following: site_name: <TITLE OF YOUR SITE> site_url: https://osg-htc.org/<REPO NAME> repo_name: https://github.com/osg-htc/<REPO NAME> theme: name: material nav: - Home: 'index.md' markdown_extensions: - admonition - codehilite: guess_lang: False - meta - toc: permalink: True Create a docs directory containing an index.md that will be your home page. Stage and commit these changes: git add mkdocs.yml docs/index.md git commit -m \"Staging initial web page contents\" Push local changes to the GitHub repository: git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME> Contact help@osg-htc.org to request repository backups to UW-Madison.","title":"Creating New Pages"},{"location":"documentation/publish-osg-pages/#creating-an-itb-area","text":"This section describes creating an ITB repository for a documentation area created in the previous section Create a new repository in the opensciencegrid organization and name it <REPO NAME>-itb . For example, an ITB area for the docs repository has a repository name of docs-itb . The ITB repository will be referred to as <ITB REPO NAME> in the rest of this document. Check the box marked Initialize this repository with a README Once created, add the mkdocs topic by clicking on the \"Add topics\" button Clone the repository and cd into the directory: git clone git@github.com:opensciencegrid/<ITB REPO NAME> cd <ITB REPO NAME> Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md In the non-ITB repository, create and encrypt the ITB repository deploy key cd into the non-ITB repository and generate the ITB deploy key cd <REPO NAME> ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-itb Install the travis gem: gem install travis Encrypt the deploy key: travis encrypt-file deploy-itb Update .travis.env with the appropriate ITB values Add and commit your files: git add .travis.env deploy-itb.enc git commit -m \"Add ITB deployment\" Danger Do NOT commit the unencrypted deploy-itb ! Add deploy-itb.pub to the ITB repository's list of deploy keys . Make sure to check Allow write access . Still in the non-ITB repository, push your local changes to the GitHub repository git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME>","title":"Creating an ITB Area"},{"location":"documentation/publish-osg-pages/#transitioning-to-github-actions","text":"Need assistance? If you need any assistance with transitioning your repository to GitHub actions, please reach out to help@osg-htc.org . When originally developed, OSG MkDocs repositories were set up to automatically publish web page changes through Travis CI . But in November 2020, Travis CI changed their pricing model so we are moving the automatic publishing infrastructure to GitHub Actions and using this opportunity to also upgrade the version of MkDocs. To ensure that your pages continue to be autmoatically published you will need to prepare your repository for the new version of MkDocs, disable Travis CI, and enable GitHub Actions.","title":"Transitioning to GitHub Actions"},{"location":"documentation/publish-osg-pages/#preparing-the-repository","text":"Before upgrading, you must fix the following incompatibilities: Rename the pages: section of mkdocs.yml to nav: . The section contents are identical; only the name is changing. Update all of the links in the documents as follows: Ensure links end in .md Ensure links are document-relative, not site-relative For example, links should be of the form ../software/development-process.md instead of /software/development-process . Push your changes to your fork and create a pull request Previewing your pages with Docker If you would like to ensure the correctness of your fixes, run the following command: docker run -it -v ${PWD}/docs -p 8000:8000 squidfunk/mkdocs-material:6.1.4 After running this command, enter localhost:8000 in your browser to preview your pages. Saved changes made to .md files are automatically updated in your browser!","title":"Preparing the repository"},{"location":"documentation/publish-osg-pages/#disabling-travis-ci","text":"After you've prepared your repository for the transition, disable Travis CI by removing related files from it. Perform the following actions from the command-line: Create a fresh clone of the repository that is still using Travis CI: git clone https://github.com/opensciencegrid/<GIT REPOSITORY> Important For the rest of the steps in this documentation to work, you should create a new clone of the repository using the above command, even if you already have an existing copy! cd into the directory containing the repository (should be the same as <GIT REPOSITORY> by default) Remove all of the Travs CI related files: git rm ci git rm .travis.env deploy-key.enc .travis.yml Commit your changes: git commit -am \"Disable Travis CI\" Push your changes (you will be prompted for your GitHub credentials): git push origin master","title":"Disabling Travis CI"},{"location":"documentation/publish-osg-pages/#enabling-github-actions","text":"The new method for validating and publishing OSG pages for a MkDocs repository can be enabled entirely through the GitHub web interface : Navigate to the opensciencegrid fork of the GitHub repository in your web browser, e.g. https://github.com/opensciencegrid/docs/ Click on the Actions tab: Find the Publish MkDocs static HTML workflow by the Open Science Grid and click the Set up this workflow button: Click on the Start commit drop-down button then click Commit new file : Navigate to the Actions tab to verify your transition. If you see green check marks, your pages are now being published with GitHub Actions! (Optional) Enable the Validate MkDocs Static HTML workflow to check for broken links and markdown correctness of pull requests to the repository. Navigate to the Actions tab as before Click on the New Workflow button: Find the Validate MkDocs static HTML workflow by the Open Science Grid and click Set up this workflow As before, click on the Start commit drop-down button then click Commit new file","title":"Enabling GitHub Actions"},{"location":"documentation/reviewing-documentation/","text":"Reviewing Software Documentation \u00b6 To maintain quality documentation, we regularly review our documentation for clarity and correctness. Performing a Review \u00b6 When reviewing a document, follow the instructions of the document to a tee as if you were completely new to the OSG. Some common things to note and/or fix: After completing the instructions in the document: Does the document inform you how to use the product? Does the document tell you how to verify that the product is functioning? Does the product work? Incorrect or out of date instructions Steps that may be particularly conducive to software or default configuration as a solution Lack of clarity or any other confusion you may have Additionally, ensure that the document meets our style and layout guidelines, as well as correct spelling and grammar. Completing a Review \u00b6 Upon completion of the review: Update (or add) the review date in the metadata at the top of the document above the h1 : DateReviewed: YYYY-MM-DD Submit a pull request with the above change and any other improvements from the review","title":"Reviewing Documentation"},{"location":"documentation/reviewing-documentation/#reviewing-software-documentation","text":"To maintain quality documentation, we regularly review our documentation for clarity and correctness.","title":"Reviewing Software Documentation"},{"location":"documentation/reviewing-documentation/#performing-a-review","text":"When reviewing a document, follow the instructions of the document to a tee as if you were completely new to the OSG. Some common things to note and/or fix: After completing the instructions in the document: Does the document inform you how to use the product? Does the document tell you how to verify that the product is functioning? Does the product work? Incorrect or out of date instructions Steps that may be particularly conducive to software or default configuration as a solution Lack of clarity or any other confusion you may have Additionally, ensure that the document meets our style and layout guidelines, as well as correct spelling and grammar.","title":"Performing a Review"},{"location":"documentation/reviewing-documentation/#completing-a-review","text":"Upon completion of the review: Update (or add) the review date in the metadata at the top of the document above the h1 : DateReviewed: YYYY-MM-DD Submit a pull request with the above change and any other improvements from the review","title":"Completing a Review"},{"location":"documentation/style-guide/","text":"Markdown Style Guide \u00b6 This document contains markdown conventions that are used in OSG Software documentation. Meta \u00b6 Run a spellchecker to catch any obvious spelling mistakes. Use official capitalizations when referring to titles (i.e., HTTPS, HTCondor) Start each new sentence on a new line. Lines should not exceed 120 characters, except in the case of link text , but may be split at earlier points (e.g. punctuation). Headings \u00b6 Use the following conventions for headings: The title should be the only level 1 heading Level 1 headings should use the ==== format Level 2 headings should use the ---- format Use APA-style title case for level 1 and level 2 headings. Only capitalize the first word for all other headings. Other heading levels should use the appropriate number of # Go no deeper than of level 5 headings Spin-off a new document or re-organize the existing document if you find that you regularly need level 5 headings. Links \u00b6 Only use document relative links in MkDocs 1.0.0 and newer MkDocs 1.0.0 does not support site-relative links (e.g. /software/development-process.md ). You must use document-relative links (e.g. ../software/development-process.md ) instead. Earlier versions of this guide recommended site-relative links; these only worked in earlier versions of MkDocs. Document-relative links work in all versions of MkDocs. Please convert any site-relative links to document-relative links before updating the doc-ci-scripts submodule to use MkDocs 1.0.0+. Links to internal pages must have the .md extension. (Earlier versions of this guide said links should not have the .md extension, but adding the .md extension is required for MkDocs 1.0.0+. Links with the .md extension work in all versions of MkDocs.) Links to the area's homepage (e.g. https://osg-htc.org/technology/) need to be of the form [link text](/) Links to other areas (like from https://osg-htc.org/technology/ to https://osg-htc.org/operations/) need to be absolute links (i.e. include the domain name) Section links \u00b6 To link sections within a page, lowercase the entire section name and replace spaces with dashes. If there are multiple sections with the same name you can link the subsequent sections by appending _N where N is the section's ordinal number minus one, e.g. append _1 for the second section. For example, if you have three sections named \"Optional Configuration\", link them like so: [1st section](#optional-configuration) [2nd section](#optional-configuration_1) [3rd section](#optional-configuration_2) Command blocks and file snippets \u00b6 Command blocks and file snippets outside of lists should be wrapped in three back-ticks (```) followed by an optional code highlighting format: ```console # stuff ``` Command blocks and file snippets inside of a list should use the appropriate number of spaces before three colons followed by an optional code highlighting format: # stuff See the lists section for details on properly formatting command blocks within a list. We use the Pygments highlighting library for syntax; it knows about 100 different languages. The Pygments website contains a live renderer if you want to see how your text will come out. Please use the console language for shell sessions. Root and user prompts \u00b6 When specifying instructions for the command-line, indicate to users whether the commands can be run as root ( root@host # ) or as an unprivileged user ( user@host $ ). For example: root@host # useradd -m osguser root@host # su - osguser user@host $ whoami osguser It can provide helpful context to use a more specific hostname in the prompt than host . For example, if you're writing a doc for setting up a Storage Element and a command is run as root on the SE, use root@se # . Or if you're testing the SE from the client side and the command is run as a normal user on a client, use user@client $ . Highlighting user input \u00b6 Use descriptive, all-caps text wrapped in angle brackets to to highlight areas that users would have to insert text specific to their site, e.g. <REMOTE SSH HOSTNAME> . The same text should be cited verbatim in surrounding prose with further explanation with examples of appropriate values. For additional visual highlighting, use hl_lines=\"N\" , where N can indicate multiple line numbers: ```console hl_lines=\"1 3\" root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME> ```` Similarly, you may also specify :::console hl_lines=\"N\" for indented command blocks, replacing console with any language supported by Pygments . The above block is rendered below: root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME> Lists \u00b6 When constructing lists, use the following guidelines: Use 1. for each item in a numbered list To make sure the contents of code blocks, file snippets, and subsequent paragraphs are indented properly, use the following formatting: For code blocks or file snippets, add an empty line after any regular text, then insert (N+1)*4 spaces at the beginning of each line, where N is the level of the item in the list. To apply code highlighting, start the code block with :::<FORMAT> ; see this page for details, including possible highlighting formats. For an example of formatting a code section inside a list, see the release series document . For additional text (i.e. after a code block), insert N*4 spaces at the beginning of each line, where N is the level of the item in the list. For example: 1. Foo - Bar :::console COMMAND BLOCK text associated with Bar text associated with Foo 1. Baz FILE SNIPPET There are 12 spaces and 8 spaces in front of the command block and text associated with Bar , respectively; 4 spaces in front of the text associated with Foo ; and 8 spaces in front of the file snippet associated with Baz . The above block is rendered below: Foo Bar COMMAND BLOCK text associated with Bar text associated with Foo Baz FILE SNIPPET Notes \u00b6 To catch the user's attention for important items or pitfalls, we used %NOTE% TWiki macros, these can be replaced with admonition-style notes and warnings: !!! note things to note or !!! warning if a user doesn't do this thing, bad stuff will happen The above blocks are rendered below as an example. Note things to note and Warning if a user doesn't do this thing, bad stuff will happen For a full list of admonition styles, see the documentation here .","title":"Markdown Style Guide"},{"location":"documentation/style-guide/#markdown-style-guide","text":"This document contains markdown conventions that are used in OSG Software documentation.","title":"Markdown Style Guide"},{"location":"documentation/style-guide/#meta","text":"Run a spellchecker to catch any obvious spelling mistakes. Use official capitalizations when referring to titles (i.e., HTTPS, HTCondor) Start each new sentence on a new line. Lines should not exceed 120 characters, except in the case of link text , but may be split at earlier points (e.g. punctuation).","title":"Meta"},{"location":"documentation/style-guide/#headings","text":"Use the following conventions for headings: The title should be the only level 1 heading Level 1 headings should use the ==== format Level 2 headings should use the ---- format Use APA-style title case for level 1 and level 2 headings. Only capitalize the first word for all other headings. Other heading levels should use the appropriate number of # Go no deeper than of level 5 headings Spin-off a new document or re-organize the existing document if you find that you regularly need level 5 headings.","title":"Headings"},{"location":"documentation/style-guide/#links","text":"Only use document relative links in MkDocs 1.0.0 and newer MkDocs 1.0.0 does not support site-relative links (e.g. /software/development-process.md ). You must use document-relative links (e.g. ../software/development-process.md ) instead. Earlier versions of this guide recommended site-relative links; these only worked in earlier versions of MkDocs. Document-relative links work in all versions of MkDocs. Please convert any site-relative links to document-relative links before updating the doc-ci-scripts submodule to use MkDocs 1.0.0+. Links to internal pages must have the .md extension. (Earlier versions of this guide said links should not have the .md extension, but adding the .md extension is required for MkDocs 1.0.0+. Links with the .md extension work in all versions of MkDocs.) Links to the area's homepage (e.g. https://osg-htc.org/technology/) need to be of the form [link text](/) Links to other areas (like from https://osg-htc.org/technology/ to https://osg-htc.org/operations/) need to be absolute links (i.e. include the domain name)","title":"Links"},{"location":"documentation/style-guide/#section-links","text":"To link sections within a page, lowercase the entire section name and replace spaces with dashes. If there are multiple sections with the same name you can link the subsequent sections by appending _N where N is the section's ordinal number minus one, e.g. append _1 for the second section. For example, if you have three sections named \"Optional Configuration\", link them like so: [1st section](#optional-configuration) [2nd section](#optional-configuration_1) [3rd section](#optional-configuration_2)","title":"Section links"},{"location":"documentation/style-guide/#command-blocks-and-file-snippets","text":"Command blocks and file snippets outside of lists should be wrapped in three back-ticks (```) followed by an optional code highlighting format: ```console # stuff ``` Command blocks and file snippets inside of a list should use the appropriate number of spaces before three colons followed by an optional code highlighting format: # stuff See the lists section for details on properly formatting command blocks within a list. We use the Pygments highlighting library for syntax; it knows about 100 different languages. The Pygments website contains a live renderer if you want to see how your text will come out. Please use the console language for shell sessions.","title":"Command blocks and file snippets"},{"location":"documentation/style-guide/#root-and-user-prompts","text":"When specifying instructions for the command-line, indicate to users whether the commands can be run as root ( root@host # ) or as an unprivileged user ( user@host $ ). For example: root@host # useradd -m osguser root@host # su - osguser user@host $ whoami osguser It can provide helpful context to use a more specific hostname in the prompt than host . For example, if you're writing a doc for setting up a Storage Element and a command is run as root on the SE, use root@se # . Or if you're testing the SE from the client side and the command is run as a normal user on a client, use user@client $ .","title":"Root and user prompts"},{"location":"documentation/style-guide/#highlighting-user-input","text":"Use descriptive, all-caps text wrapped in angle brackets to to highlight areas that users would have to insert text specific to their site, e.g. <REMOTE SSH HOSTNAME> . The same text should be cited verbatim in surrounding prose with further explanation with examples of appropriate values. For additional visual highlighting, use hl_lines=\"N\" , where N can indicate multiple line numbers: ```console hl_lines=\"1 3\" root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME> ```` Similarly, you may also specify :::console hl_lines=\"N\" for indented command blocks, replacing console with any language supported by Pygments . The above block is rendered below: root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME>","title":"Highlighting user input"},{"location":"documentation/style-guide/#lists","text":"When constructing lists, use the following guidelines: Use 1. for each item in a numbered list To make sure the contents of code blocks, file snippets, and subsequent paragraphs are indented properly, use the following formatting: For code blocks or file snippets, add an empty line after any regular text, then insert (N+1)*4 spaces at the beginning of each line, where N is the level of the item in the list. To apply code highlighting, start the code block with :::<FORMAT> ; see this page for details, including possible highlighting formats. For an example of formatting a code section inside a list, see the release series document . For additional text (i.e. after a code block), insert N*4 spaces at the beginning of each line, where N is the level of the item in the list. For example: 1. Foo - Bar :::console COMMAND BLOCK text associated with Bar text associated with Foo 1. Baz FILE SNIPPET There are 12 spaces and 8 spaces in front of the command block and text associated with Bar , respectively; 4 spaces in front of the text associated with Foo ; and 8 spaces in front of the file snippet associated with Baz . The above block is rendered below: Foo Bar COMMAND BLOCK text associated with Bar text associated with Foo Baz FILE SNIPPET","title":"Lists"},{"location":"documentation/style-guide/#notes","text":"To catch the user's attention for important items or pitfalls, we used %NOTE% TWiki macros, these can be replaced with admonition-style notes and warnings: !!! note things to note or !!! warning if a user doesn't do this thing, bad stuff will happen The above blocks are rendered below as an example. Note things to note and Warning if a user doesn't do this thing, bad stuff will happen For a full list of admonition styles, see the documentation here .","title":"Notes"},{"location":"documentation/writing-documentation/","text":"Writing OSG Documentation \u00b6 Many OSG pages are written in markdown , built using MkDocs , and served via GitHub Pages . To contribute content , submit a pull request to the relevant GitHub repository, which are tagged with \"mkdocs\". List of documentation repos This document contains instructions, recommendations, and guidelines for writing OSG content. Contributing Content \u00b6 To contribute minor content changes (e.g., fixing typos, changing a couple of sentences), we recommend using the GitHub web interface to submit a pull request. To contribute major content changes to one of the above OSG areas, make sure you and the machine you'll be working on meet the following requirements: Have a Github account Installations of the following tools: Docker git Preparing the git repository \u00b6 Before making any content changes, you will need to prepare a local git clone: Fork and clone the GitHub repository that you'd like to contribute to Add the upstream Github repository as a remote . For example, if you are working on the User School 2018 pages: $ git remote add upstream https://github.com/opensciencegrid/user-school-2018 Previewing the pages \u00b6 To preview the pages, start a MkDocs development server. The development server will automatically detect any content changes and make them viewable in your browser. cd into the directory containing the local clone of your GitHub fork Start a MkDocs development server to preview your changes: $ docker run --rm -p 8000 :8000 -v ${ PWD } :/docs squidfunk/mkdocs-material:7.1.0 To preview your changes visit localhost:8000 in the browser of your choice. The server can be stopped with Ctrl-C . Making content changes \u00b6 To contribute content to the OSG, follow these steps to submit a pull request with your desired changes: cd into the directory containing the local clone of your Github fork Create a branch based on a branch from the upstream repository: $ git fetch --all $ git checkout -b <BRANCH NAME> upstream/<UPSTREAM BRANCH NAME> Replace <BRANCH NAME> with a name of your choice and <UPSTREAM BRANCH NAME> with a branch name from the upstream repository. For example, instructors for the 2018 User School should use the materials branch: $ git checkout -b example_branch_name upstream/materials If you do not know which upstream branch to use, pick master . Make your changes in the docs/ directory of your local clone, following the style guide : If you are making changes to an existing page: Open mkdocs.yml and find the location of the file relative to the docs/ directory Make your changes to that file and move onto the next step If you are contributing a new page: Name the page. Page file names should be lowercase, - delimited, and concise but descriptive, e.g. markdown-migration.md or cutting-release.md Place the page in the relevant sub-folder of the docs/ directory. If you are unsure of the appropriate location, note that in the description of the pull request. Add the document to the nav: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Note If mkdocs.yml contains does not contain a nav: section, add the above to the pages: section instead. This means that the repository is using an older version of MkDocs and will need to be transitioned to GitHub Actions . If you are writing site administrator documentation, following the suggested document layout If you haven't already, start a Mkdocs development server to preview your changes . Continue making changes until you are satisfied with the preview, then stage your changes in git: $ git add <YOUR FILE> <YOUR 2nd FILE>...<YOUR Nth FILE> Where <YOUR * FILE> is any file that contains changes that you'd wish to make. If you are adding a new page, one of the files should be mkdocs.yml . Commit your changes and push them to your Github fork: $ git commit -m \"<DESCRIPTIVE COMMIT MESSAGE>\" $ git push origin Where <DESCRIPTIVE COMMIT MESSAGE> is a meaningful short text that identifies the changes applied, it is a good practice, to concatenate the ticket number associated e.g. \"Removing color macros (SOFTWARE-3739)\" From your Github fork, submit a pull request Document Layout \u00b6 This section contains suggested layouts of externally-facing, site administrator documentation . The introduction is the only layout requirement for documents except for installation guides. Introductions \u00b6 All documents should start with an introduction that explains what the document contains, what the product does, and why someone may want to use it. In the past, document introductions were included in About this... sections due to the layout of the table of contents. Since the table of contents is included in the sidebar this is unnecessary and introduction content should go directly below the title heading without any second-level headings. The HTCondor-CE installation guide is an example that meet all of the above criteria. Installation guides \u00b6 In addition to the introduction above, installation documents should have the following sections: Before Starting: This section should contain information for any prepatory work that the site administrator should do or consider before proceeding with the installation ( example ). Installation: Procedural instructions that tell the user how to install the software ( example ) Validation: How does the user make sure their installation is functional? Optionally, the following sections should be included as necessary. Overview: if the introduction becomes large and unwieldy, extract the details of what the product does into an overview section Configuration: required configuration steps ( example ) as well as a sub-section for optional configurations. For long optional configuration sections, consider creating alist of contents at the top of the sub-section ( example ). Troubleshooting: common issues that users encounter and their fixes Reference: Details about configuration and log files, unix users, certificates, networking, links to relevant upstream documentation, etc. ( example ) If any of the sections become too large, consider separating them out and linking to the new documents ( example ). Tips for Writing Procedural Instructions \u00b6 Title the procedure with the user goal, usually starting with a gerund; e.g.: Installing the Frobnosticator Number all steps (as opposed to using bullets) List steps in order in which they are performed Each step should begin with a single-line instruction in plain English, in command form; e.g.: Make sure that the Frobnosticator configuration file is world-writable If the means of carrying out the instruction is unclear or complex, include clarification, ideally in the form of a working example; e.g.: chmod a+x /usr/share/frobnosticator/frob.conf Put clarifying information in separate paragraphs within the step Put critical information about the whole procedure in one or more paragraphs before the numbered steps Put supplemental information about the whole procedure in one or more paragraphs after the numbered steps Avoid pronouns when writing technical articles or documentation e.g., install foo rather than install it . Avoid superfluous statements like you will want , you want , you should e.g., install foo rather than you will want to install foo . Use the imperative form in step-by-step instructions, e.g. install package foo rather than the package foo should be installed","title":"Writing Documentation"},{"location":"documentation/writing-documentation/#writing-osg-documentation","text":"Many OSG pages are written in markdown , built using MkDocs , and served via GitHub Pages . To contribute content , submit a pull request to the relevant GitHub repository, which are tagged with \"mkdocs\". List of documentation repos This document contains instructions, recommendations, and guidelines for writing OSG content.","title":"Writing OSG Documentation"},{"location":"documentation/writing-documentation/#contributing-content","text":"To contribute minor content changes (e.g., fixing typos, changing a couple of sentences), we recommend using the GitHub web interface to submit a pull request. To contribute major content changes to one of the above OSG areas, make sure you and the machine you'll be working on meet the following requirements: Have a Github account Installations of the following tools: Docker git","title":"Contributing Content"},{"location":"documentation/writing-documentation/#preparing-the-git-repository","text":"Before making any content changes, you will need to prepare a local git clone: Fork and clone the GitHub repository that you'd like to contribute to Add the upstream Github repository as a remote . For example, if you are working on the User School 2018 pages: $ git remote add upstream https://github.com/opensciencegrid/user-school-2018","title":"Preparing the git repository"},{"location":"documentation/writing-documentation/#previewing-the-pages","text":"To preview the pages, start a MkDocs development server. The development server will automatically detect any content changes and make them viewable in your browser. cd into the directory containing the local clone of your GitHub fork Start a MkDocs development server to preview your changes: $ docker run --rm -p 8000 :8000 -v ${ PWD } :/docs squidfunk/mkdocs-material:7.1.0 To preview your changes visit localhost:8000 in the browser of your choice. The server can be stopped with Ctrl-C .","title":"Previewing the pages"},{"location":"documentation/writing-documentation/#making-content-changes","text":"To contribute content to the OSG, follow these steps to submit a pull request with your desired changes: cd into the directory containing the local clone of your Github fork Create a branch based on a branch from the upstream repository: $ git fetch --all $ git checkout -b <BRANCH NAME> upstream/<UPSTREAM BRANCH NAME> Replace <BRANCH NAME> with a name of your choice and <UPSTREAM BRANCH NAME> with a branch name from the upstream repository. For example, instructors for the 2018 User School should use the materials branch: $ git checkout -b example_branch_name upstream/materials If you do not know which upstream branch to use, pick master . Make your changes in the docs/ directory of your local clone, following the style guide : If you are making changes to an existing page: Open mkdocs.yml and find the location of the file relative to the docs/ directory Make your changes to that file and move onto the next step If you are contributing a new page: Name the page. Page file names should be lowercase, - delimited, and concise but descriptive, e.g. markdown-migration.md or cutting-release.md Place the page in the relevant sub-folder of the docs/ directory. If you are unsure of the appropriate location, note that in the description of the pull request. Add the document to the nav: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Note If mkdocs.yml contains does not contain a nav: section, add the above to the pages: section instead. This means that the repository is using an older version of MkDocs and will need to be transitioned to GitHub Actions . If you are writing site administrator documentation, following the suggested document layout If you haven't already, start a Mkdocs development server to preview your changes . Continue making changes until you are satisfied with the preview, then stage your changes in git: $ git add <YOUR FILE> <YOUR 2nd FILE>...<YOUR Nth FILE> Where <YOUR * FILE> is any file that contains changes that you'd wish to make. If you are adding a new page, one of the files should be mkdocs.yml . Commit your changes and push them to your Github fork: $ git commit -m \"<DESCRIPTIVE COMMIT MESSAGE>\" $ git push origin Where <DESCRIPTIVE COMMIT MESSAGE> is a meaningful short text that identifies the changes applied, it is a good practice, to concatenate the ticket number associated e.g. \"Removing color macros (SOFTWARE-3739)\" From your Github fork, submit a pull request","title":"Making content changes"},{"location":"documentation/writing-documentation/#document-layout","text":"This section contains suggested layouts of externally-facing, site administrator documentation . The introduction is the only layout requirement for documents except for installation guides.","title":"Document Layout"},{"location":"documentation/writing-documentation/#introductions","text":"All documents should start with an introduction that explains what the document contains, what the product does, and why someone may want to use it. In the past, document introductions were included in About this... sections due to the layout of the table of contents. Since the table of contents is included in the sidebar this is unnecessary and introduction content should go directly below the title heading without any second-level headings. The HTCondor-CE installation guide is an example that meet all of the above criteria.","title":"Introductions"},{"location":"documentation/writing-documentation/#installation-guides","text":"In addition to the introduction above, installation documents should have the following sections: Before Starting: This section should contain information for any prepatory work that the site administrator should do or consider before proceeding with the installation ( example ). Installation: Procedural instructions that tell the user how to install the software ( example ) Validation: How does the user make sure their installation is functional? Optionally, the following sections should be included as necessary. Overview: if the introduction becomes large and unwieldy, extract the details of what the product does into an overview section Configuration: required configuration steps ( example ) as well as a sub-section for optional configurations. For long optional configuration sections, consider creating alist of contents at the top of the sub-section ( example ). Troubleshooting: common issues that users encounter and their fixes Reference: Details about configuration and log files, unix users, certificates, networking, links to relevant upstream documentation, etc. ( example ) If any of the sections become too large, consider separating them out and linking to the new documents ( example ).","title":"Installation guides"},{"location":"documentation/writing-documentation/#tips-for-writing-procedural-instructions","text":"Title the procedure with the user goal, usually starting with a gerund; e.g.: Installing the Frobnosticator Number all steps (as opposed to using bullets) List steps in order in which they are performed Each step should begin with a single-line instruction in plain English, in command form; e.g.: Make sure that the Frobnosticator configuration file is world-writable If the means of carrying out the instruction is unclear or complex, include clarification, ideally in the form of a working example; e.g.: chmod a+x /usr/share/frobnosticator/frob.conf Put clarifying information in separate paragraphs within the step Put critical information about the whole procedure in one or more paragraphs before the numbered steps Put supplemental information about the whole procedure in one or more paragraphs after the numbered steps Avoid pronouns when writing technical articles or documentation e.g., install foo rather than install it . Avoid superfluous statements like you will want , you want , you should e.g., install foo rather than you will want to install foo . Use the imperative form in step-by-step instructions, e.g. install package foo rather than the package foo should be installed","title":"Tips for Writing Procedural Instructions"},{"location":"meetings/TechAreaTemplate/","text":"OSG Technology Area Meeting, 17 July 2017 \u00b6 Coordinates: Conference: 719-284-5267, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianB, BrianL, Carl, Derek, Edgar, Jeff, Marian, Marty, Mat, Suchandra, TimC, TimT, Xin Announcements \u00b6 Triage Duty \u00b6 This week: Next week: ( ) open tickets JIRA \u00b6 # of tickets \u0394 State 141 -17 Open 33 +9 In Progress 4 +2 Ready for Testing 0 -12 Ready for Release Release Schedule \u00b6 Name Version Development Freeze Package Freeze Release Notes August 3.4.2, 3.3.27 2017-07-24 2017-07-31 2017-08-08 September 3.4.3, 3.3.28 2017-08-28 2017-09-05 2017-09-12 5 week cycle October 3.4.4, 3.3.29 2017-09-25 2017-10-02 2017-10-10 Notes: Additional \u201curgent\u201d releases may be scheduled for the 4th Tuesday of each month. The Testing date is when acceptance testing will be scheduled for releasable packages; if a package is added after this date, it may not be possible to schedule adequate testing time, thereby forcing it into the next release. OSG Software Team \u00b6 Discussions \u00b6 Support Update \u00b6 OSG Release Team \u00b6 3.3.27 \u0394 Both \u0394 3.4.2 \u0394 Total \u0394 Status 1 +0 4 +0 2 +0 7 +0 Open 0 +0 10 +0 4 +0 14 +0 In Progress 2 +0 1 +0 1 +0 4 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +0 15 +0 7 +0 25 +0 Total Discussions \u00b6 OSG Investigations Team \u00b6 Last Week \u00b6 This Week \u00b6 Ongoing \u00b6","title":"OSG Technology Area Meeting, 17 July 2017"},{"location":"meetings/TechAreaTemplate/#osg-technology-area-meeting-17-july-2017","text":"Coordinates: Conference: 719-284-5267, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianB, BrianL, Carl, Derek, Edgar, Jeff, Marian, Marty, Mat, Suchandra, TimC, TimT, Xin","title":"OSG Technology Area Meeting, 17 July 2017"},{"location":"meetings/TechAreaTemplate/#announcements","text":"","title":"Announcements"},{"location":"meetings/TechAreaTemplate/#triage-duty","text":"This week: Next week: ( ) open tickets","title":"Triage Duty"},{"location":"meetings/TechAreaTemplate/#jira","text":"# of tickets \u0394 State 141 -17 Open 33 +9 In Progress 4 +2 Ready for Testing 0 -12 Ready for Release","title":"JIRA"},{"location":"meetings/TechAreaTemplate/#release-schedule","text":"Name Version Development Freeze Package Freeze Release Notes August 3.4.2, 3.3.27 2017-07-24 2017-07-31 2017-08-08 September 3.4.3, 3.3.28 2017-08-28 2017-09-05 2017-09-12 5 week cycle October 3.4.4, 3.3.29 2017-09-25 2017-10-02 2017-10-10 Notes: Additional \u201curgent\u201d releases may be scheduled for the 4th Tuesday of each month. The Testing date is when acceptance testing will be scheduled for releasable packages; if a package is added after this date, it may not be possible to schedule adequate testing time, thereby forcing it into the next release.","title":"Release Schedule"},{"location":"meetings/TechAreaTemplate/#osg-software-team","text":"","title":"OSG Software Team"},{"location":"meetings/TechAreaTemplate/#discussions","text":"","title":"Discussions"},{"location":"meetings/TechAreaTemplate/#support-update","text":"","title":"Support Update"},{"location":"meetings/TechAreaTemplate/#osg-release-team","text":"3.3.27 \u0394 Both \u0394 3.4.2 \u0394 Total \u0394 Status 1 +0 4 +0 2 +0 7 +0 Open 0 +0 10 +0 4 +0 14 +0 In Progress 2 +0 1 +0 1 +0 4 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +0 15 +0 7 +0 25 +0 Total","title":"OSG Release Team"},{"location":"meetings/TechAreaTemplate/#discussions_1","text":"","title":"Discussions"},{"location":"meetings/TechAreaTemplate/#osg-investigations-team","text":"","title":"OSG Investigations Team"},{"location":"meetings/TechAreaTemplate/#last-week","text":"","title":"Last Week"},{"location":"meetings/TechAreaTemplate/#this-week","text":"","title":"This Week"},{"location":"meetings/TechAreaTemplate/#ongoing","text":"","title":"Ongoing"},{"location":"meetings/2020/TechArea20200106/","text":"OSG Technology Area Meeting, 6 January 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Edgar, Diego, Marian, Marco Mambelli, Mat Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: Carl 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 162 +2 Open 35 +0 In Progress 12 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.8/3.4.42 AI (Mat): Package default XRootD standalone auth file (SOFTWARE-3951) AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Carl): HTCondor 8.9.5 and 8.8.7 releases (SOFTWARE-3929, SOFTWARE-3957) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment AI (Brian): Working on serving HTML results from osg-sw-submit web server Discussion \u00b6 None this week Support Update \u00b6 None last week OSG Release Team \u00b6 3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 1 +1 11 +11 1 +1 13 +13 Open 0 +0 4 +4 2 +2 6 +6 In Progress 1 +1 9 +9 2 +2 12 +12 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 2 +2 24 +24 5 +5 31 +31 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 3.4.42 Hosted CE Tools 0.5-2 osg-tested-internal 3.4-8 OSG XRootD 3.4-10 Ready for Release Nothing Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing Discussion \u00b6 UCSD is running the latest osg-xrootd-standalone package in production and will update the relevant tickets with testing notes AI (Diego): Test the xrootd-standalone fresh container AI (Diego, Edgar): Test XRootD 4.11.1 OSG Investigations Team \u00b6 No updates this week Discussion \u00b6 None this week","title":"January, 6 2020"},{"location":"meetings/2020/TechArea20200106/#osg-technology-area-meeting-6-january-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Edgar, Diego, Marian, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 6 January 2020"},{"location":"meetings/2020/TechArea20200106/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200106/#triage-duty","text":"This week: Mat Next week: Carl 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200106/#jira","text":"# of tickets \u0394 State 162 +2 Open 35 +0 In Progress 12 +0 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200106/#osg-software-team","text":"OSG 3.5.8/3.4.42 AI (Mat): Package default XRootD standalone auth file (SOFTWARE-3951) AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Carl): HTCondor 8.9.5 and 8.8.7 releases (SOFTWARE-3929, SOFTWARE-3957) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment AI (Brian): Working on serving HTML results from osg-sw-submit web server","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200106/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200106/#support-update","text":"None last week","title":"Support Update"},{"location":"meetings/2020/TechArea20200106/#osg-release-team","text":"3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 1 +1 11 +11 1 +1 13 +13 Open 0 +0 4 +4 2 +2 6 +6 In Progress 1 +1 9 +9 2 +2 12 +12 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 2 +2 24 +24 5 +5 31 +31 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 3.4.42 Hosted CE Tools 0.5-2 osg-tested-internal 3.4-8 OSG XRootD 3.4-10 Ready for Release Nothing Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200106/#discussion_1","text":"UCSD is running the latest osg-xrootd-standalone package in production and will update the relevant tickets with testing notes AI (Diego): Test the xrootd-standalone fresh container AI (Diego, Edgar): Test XRootD 4.11.1","title":"Discussion"},{"location":"meetings/2020/TechArea20200106/#osg-investigations-team","text":"No updates this week","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200106/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200113/","text":"OSG Technology Area Meeting, 13 January 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Marian, Tim Announcements \u00b6 Meeting canceled next week (UW on holiday for MLK Jr Day) Triage Duty \u00b6 This week: Carl Next week: Brian 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 155 -7 Open 33 -2 In Progress 21 +9 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.8/3.4.42 AI (Carl): Drop instructions for commenting out all.export /tmp (SOFTWARE-3858) OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) AI (Diego): Add osg-xrootd-standalone to osg-tested-internal (SOFTWARE-3964) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment GridFTP/GSI transition AI (Edgar): OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Generate list of registered, supported GridFTP servers (SOFTWARE-3942) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) AI (Brian): Working on serving HTML results from osg-sw-submit web server Fill out doc focus doodle poll: https://doodle.com/poll/puy4rtfnrmuvhmzx Discussion \u00b6 Carl was wondering if GRACC records had GPU information. Derek: Yes, they do. glidein-monitor is in osg-development but Marco needs to do some more testing but when it's ready, he'll send an email to interesting parties Support Update \u00b6 Purdue (Derek): Adding new sites to Topology requires mapping on the WLCG side. In the future, we need to coordinate with the WLCG if an existing site would like to change its name. GRACC (Derek): user wanted a custom GRACC dashboard but needs to coordinate with user support and FKW (Freshdesk #63926) OSG Release Team \u00b6 3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 0 -1 1 -10 0 -1 1 -12 Open 0 +0 1 -3 0 -2 1 -5 In Progress 0 -1 15 +6 5 +3 20 +8 Ready for Testing 1 +1 0 +0 0 +0 1 +1 Ready for Release 1 -1 17 -7 5 +0 23 -8 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Upcoming HTCondor 8.9.5 Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 HTCondor 8.8.7 osg-ce osg-xrootd 3.4.42 Hosted CE Tools 0.5-2 OSG XRootD 3.4-10 Ready for Release 3.4.42 osg-tested-internal 3.4-8 Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing Discussion \u00b6 AI (Diego, Edgar): Test XRootD 4.11.1 AI (TimT): Test HTCondor 8.9.5 on the ITB AI (TimT): Reach out to admins for testing of HTCondor 8.8.7 OSG Investigations Team \u00b6 Assisted user support in stashcache transition, writable and origin Moving scitokens-cpp to epel. EPEL-7 EPEL-8 GRACC transition to gracc2 Discussion \u00b6 None this week","title":"January, 13 2020"},{"location":"meetings/2020/TechArea20200113/#osg-technology-area-meeting-13-january-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Marian, Tim","title":"OSG Technology Area Meeting, 13 January 2020"},{"location":"meetings/2020/TechArea20200113/#announcements","text":"Meeting canceled next week (UW on holiday for MLK Jr Day)","title":"Announcements"},{"location":"meetings/2020/TechArea20200113/#triage-duty","text":"This week: Carl Next week: Brian 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200113/#jira","text":"# of tickets \u0394 State 155 -7 Open 33 -2 In Progress 21 +9 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200113/#osg-software-team","text":"OSG 3.5.8/3.4.42 AI (Carl): Drop instructions for commenting out all.export /tmp (SOFTWARE-3858) OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) AI (Diego): Add osg-xrootd-standalone to osg-tested-internal (SOFTWARE-3964) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment GridFTP/GSI transition AI (Edgar): OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Generate list of registered, supported GridFTP servers (SOFTWARE-3942) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) AI (Brian): Working on serving HTML results from osg-sw-submit web server Fill out doc focus doodle poll: https://doodle.com/poll/puy4rtfnrmuvhmzx","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200113/#discussion","text":"Carl was wondering if GRACC records had GPU information. Derek: Yes, they do. glidein-monitor is in osg-development but Marco needs to do some more testing but when it's ready, he'll send an email to interesting parties","title":"Discussion"},{"location":"meetings/2020/TechArea20200113/#support-update","text":"Purdue (Derek): Adding new sites to Topology requires mapping on the WLCG side. In the future, we need to coordinate with the WLCG if an existing site would like to change its name. GRACC (Derek): user wanted a custom GRACC dashboard but needs to coordinate with user support and FKW (Freshdesk #63926)","title":"Support Update"},{"location":"meetings/2020/TechArea20200113/#osg-release-team","text":"3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 0 -1 1 -10 0 -1 1 -12 Open 0 +0 1 -3 0 -2 1 -5 In Progress 0 -1 15 +6 5 +3 20 +8 Ready for Testing 1 +1 0 +0 0 +0 1 +1 Ready for Release 1 -1 17 -7 5 +0 23 -8 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Upcoming HTCondor 8.9.5 Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 HTCondor 8.8.7 osg-ce osg-xrootd 3.4.42 Hosted CE Tools 0.5-2 OSG XRootD 3.4-10 Ready for Release 3.4.42 osg-tested-internal 3.4-8 Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200113/#discussion_1","text":"AI (Diego, Edgar): Test XRootD 4.11.1 AI (TimT): Test HTCondor 8.9.5 on the ITB AI (TimT): Reach out to admins for testing of HTCondor 8.8.7","title":"Discussion"},{"location":"meetings/2020/TechArea20200113/#osg-investigations-team","text":"Assisted user support in stashcache transition, writable and origin Moving scitokens-cpp to epel. EPEL-7 EPEL-8 GRACC transition to gracc2","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200113/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200127/","text":"OSG Technology Area Meeting, 27 January 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Derek, Diego, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Edgar 5 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 147 -3 Open 40 -1 In Progress 1 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Release osg-system-profiler 1.5.0+ (SOFTWARE-3970) Hosted CE Hosted CE containers accepting jobs and reporting to the GRACC ! Next steps: Reorganize Utah topology AI (Brian): Simplify remote user configuration (SOFTWARE-3960) Documentation for OSG Ops Push HTCondor-CE logs to ElasticSearch GridFTP/GSI transition AI (Brian, Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd Discussion \u00b6 GlidenWMS 3.6.2 release candidate expected this week Support Update \u00b6 Brown (Marian): Marian had a long meeting with them to work through some site.xml issues and they're looking to fix them XRootD < 4.9 clients have issues with a Polish CA that has an expiration time after 2038 ( https://github.com/xrootd/xrootd/issues/1110 ). OSG Release Team \u00b6 3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +1 10 +10 1 +1 12 +12 Open 2 +2 5 +5 4 +4 11 +11 In Progress 0 +0 1 +1 0 +0 1 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +3 16 +16 5 +5 24 +24 Total Software Ready for Testing 3.5.9 Nothing yet Both XCache 1.2.1 3.4.43 Nothing yet Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data IGTF 1.103 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 Scitokens-cpp is in epel. EPEL-7 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6756584348) EPEL-8 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a4bf7c5d9c) GRACC transition to gracc2 Discussion \u00b6 None this week","title":"January, 27 2020"},{"location":"meetings/2020/TechArea20200127/#osg-technology-area-meeting-27-january-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Derek, Diego, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 27 January 2020"},{"location":"meetings/2020/TechArea20200127/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200127/#triage-duty","text":"This week: Brian Next week: Edgar 5 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200127/#jira","text":"# of tickets \u0394 State 147 -3 Open 40 -1 In Progress 1 -1 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200127/#osg-software-team","text":"OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Release osg-system-profiler 1.5.0+ (SOFTWARE-3970) Hosted CE Hosted CE containers accepting jobs and reporting to the GRACC ! Next steps: Reorganize Utah topology AI (Brian): Simplify remote user configuration (SOFTWARE-3960) Documentation for OSG Ops Push HTCondor-CE logs to ElasticSearch GridFTP/GSI transition AI (Brian, Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200127/#discussion","text":"GlidenWMS 3.6.2 release candidate expected this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200127/#support-update","text":"Brown (Marian): Marian had a long meeting with them to work through some site.xml issues and they're looking to fix them XRootD < 4.9 clients have issues with a Polish CA that has an expiration time after 2038 ( https://github.com/xrootd/xrootd/issues/1110 ).","title":"Support Update"},{"location":"meetings/2020/TechArea20200127/#osg-release-team","text":"3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +1 10 +10 1 +1 12 +12 Open 2 +2 5 +5 4 +4 11 +11 In Progress 0 +0 1 +1 0 +0 1 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +3 16 +16 5 +5 24 +24 Total Software Ready for Testing 3.5.9 Nothing yet Both XCache 1.2.1 3.4.43 Nothing yet Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data IGTF 1.103 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200127/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200127/#osg-investigations-team","text":"Scitokens-cpp is in epel. EPEL-7 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6756584348) EPEL-8 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a4bf7c5d9c) GRACC transition to gracc2","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200127/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200203/","text":"OSG Technology Area Meeting, 3 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! Moria access is flaky, we're in touch with UW CS Lab Triage Duty \u00b6 This week: Carl Next week: Edgar 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 149 +2 Open 44 +4 In Progress 3 +2 Ready for Testing 1 +1 Ready for Release JIRA ticket reporter didn't fire this week. Numbers updated manually. OSG Software Team \u00b6 OSG 3.5.9/3.4.43 AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd Discussion \u00b6 XCache validator has a lot of non-packaged RPM dependencies as Python libs. Diego will install the dependencies into a Python virtualenv and determine which libs are needed. AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena. Support Update \u00b6 Czech Site (Marian): They had some questions about Gratia vs APEL accounting. They may follow-up with other tickets via Freshdesk. EIC (Mat): Registered new contacts, waiting on some answers from Jerome Geant4 (Marian, Carl): Need to register contacts for their OASIS repo Purdue (Derek): Completed site rename and coordination with WLCG: https://ggus.eu/index.php?mode=ticket_info&ticket_id=144769 UCSD (Carl): Provided OSG-specific patches for our version of Hadoop UFL (Brian, Derek): Issues with Slurm job statuses not updating for short-running (~10min) jobs OSG Release Team \u00b6 3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +0 11 +1 1 +0 13 +1 Open 2 +0 6 +1 3 -1 11 +0 In Progress 1 +1 4 +3 2 +2 7 +6 Ready for Testing 0 +0 1 +1 0 +0 1 +1 Ready for Release 4 +1 22 +6 6 +1 32 +8 Total Software Ready for Testing 3.5.9 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.43 osg-configure 2.5.1 Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (BrianL): coordinate Frontier Squid testing with Igor and Edgar OSG Investigations Team \u00b6 New scitokens-cpp and xrootd-scitokens. GRACC transition to gracc2 Working on SciTokens + StashCache Discussion \u00b6 None this week","title":"February 3, 2020"},{"location":"meetings/2020/TechArea20200203/#osg-technology-area-meeting-3-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 3 February 2020"},{"location":"meetings/2020/TechArea20200203/#announcements","text":"OSG All Hands meeting registration open! Moria access is flaky, we're in touch with UW CS Lab","title":"Announcements"},{"location":"meetings/2020/TechArea20200203/#triage-duty","text":"This week: Carl Next week: Edgar 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200203/#jira","text":"# of tickets \u0394 State 149 +2 Open 44 +4 In Progress 3 +2 Ready for Testing 1 +1 Ready for Release JIRA ticket reporter didn't fire this week. Numbers updated manually.","title":"JIRA"},{"location":"meetings/2020/TechArea20200203/#osg-software-team","text":"OSG 3.5.9/3.4.43 AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200203/#discussion","text":"XCache validator has a lot of non-packaged RPM dependencies as Python libs. Diego will install the dependencies into a Python virtualenv and determine which libs are needed. AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena.","title":"Discussion"},{"location":"meetings/2020/TechArea20200203/#support-update","text":"Czech Site (Marian): They had some questions about Gratia vs APEL accounting. They may follow-up with other tickets via Freshdesk. EIC (Mat): Registered new contacts, waiting on some answers from Jerome Geant4 (Marian, Carl): Need to register contacts for their OASIS repo Purdue (Derek): Completed site rename and coordination with WLCG: https://ggus.eu/index.php?mode=ticket_info&ticket_id=144769 UCSD (Carl): Provided OSG-specific patches for our version of Hadoop UFL (Brian, Derek): Issues with Slurm job statuses not updating for short-running (~10min) jobs","title":"Support Update"},{"location":"meetings/2020/TechArea20200203/#osg-release-team","text":"3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +0 11 +1 1 +0 13 +1 Open 2 +0 6 +1 3 -1 11 +0 In Progress 1 +1 4 +3 2 +2 7 +6 Ready for Testing 0 +0 1 +1 0 +0 1 +1 Ready for Release 4 +1 22 +6 6 +1 32 +8 Total Software Ready for Testing 3.5.9 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.43 osg-configure 2.5.1 Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200203/#discussion_1","text":"AI (BrianL): coordinate Frontier Squid testing with Igor and Edgar","title":"Discussion"},{"location":"meetings/2020/TechArea20200203/#osg-investigations-team","text":"New scitokens-cpp and xrootd-scitokens. GRACC transition to gracc2 Working on SciTokens + StashCache","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200203/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200210/","text":"OSG Technology Area Meeting, 10 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! BrianL OOO Thu-Fri Triage Duty \u00b6 This week: Edgar Next week: TimT 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 147 -2 Open 42 -2 In Progress 7 +4 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.10/3.4.44 AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Derek): Review CE -> Central Collector SSL advertising PR ( https://github.com/htcondor/htcondor-ce/pull/300 ) Discussion \u00b6 Marco expects a new GlideinWMS 3.6 and 3.7 RC expected soon AI (BrianL): Get DockerHub accounts from team AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena. Support Update \u00b6 EIC (Mat): Jerome is getting info from their admin for further registration Topology (Carl): Various contact database additions and a deletion OSG Release Team \u00b6 3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 -2 1 +0 11 -2 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 4 +0 2 +0 7 +0 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 20 -2 6 +0 30 -2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related) Discussion \u00b6 None this week","title":"February 10, 2020"},{"location":"meetings/2020/TechArea20200210/#osg-technology-area-meeting-10-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 10 February 2020"},{"location":"meetings/2020/TechArea20200210/#announcements","text":"OSG All Hands meeting registration open! BrianL OOO Thu-Fri","title":"Announcements"},{"location":"meetings/2020/TechArea20200210/#triage-duty","text":"This week: Edgar Next week: TimT 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200210/#jira","text":"# of tickets \u0394 State 147 -2 Open 42 -2 In Progress 7 +4 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200210/#osg-software-team","text":"OSG 3.5.10/3.4.44 AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Derek): Review CE -> Central Collector SSL advertising PR ( https://github.com/htcondor/htcondor-ce/pull/300 )","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200210/#discussion","text":"Marco expects a new GlideinWMS 3.6 and 3.7 RC expected soon AI (BrianL): Get DockerHub accounts from team AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena.","title":"Discussion"},{"location":"meetings/2020/TechArea20200210/#support-update","text":"EIC (Mat): Jerome is getting info from their admin for further registration Topology (Carl): Various contact database additions and a deletion","title":"Support Update"},{"location":"meetings/2020/TechArea20200210/#osg-release-team","text":"3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 -2 1 +0 11 -2 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 4 +0 2 +0 7 +0 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 20 -2 6 +0 30 -2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200210/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200210/#osg-investigations-team","text":"TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200210/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200217/","text":"OSG Technology Area Meeting, 17 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! UCSD out for President's day Triage Duty \u00b6 This week: TimT Next week: Mat 11 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 146 -1 Open 39 -3 In Progress 10 +3 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.10/3.4.44 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) Discussion \u00b6 None this week Support Update \u00b6 Florida (BrianL, Derek): Working to speed up startup of SAM test jobs in their CE; waiting on feedback Purdue (Mat): Helped debug authentication issues with their local HTCondor pool and the new OSG default authentication UIUC (Carl): Debugging quoting issues with condor blahp submission (Derek) Update WLCG report. Stalled uploader which was corrected, and fixed from happening again. OSG Release Team \u00b6 3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 +0 1 +0 11 +0 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 6 +2 2 +0 9 +2 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 22 +2 6 +0 32 +2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XRootD 4.11.2 uberftp 2.8-3 XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data HCC VOMS cert Operations Nothing Contrib Nothing Discussion \u00b6 AI (Tim): Create a JIRA ticket to automate packages ready for testing list OSG Investigations Team \u00b6 (lots of people outages) TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related) IRIS-HEP Posters! Discussion \u00b6 None this week","title":"February 17, 2020"},{"location":"meetings/2020/TechArea20200217/#osg-technology-area-meeting-17-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Mat, TimT","title":"OSG Technology Area Meeting, 17 February 2020"},{"location":"meetings/2020/TechArea20200217/#announcements","text":"OSG All Hands meeting registration open! UCSD out for President's day","title":"Announcements"},{"location":"meetings/2020/TechArea20200217/#triage-duty","text":"This week: TimT Next week: Mat 11 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200217/#jira","text":"# of tickets \u0394 State 146 -1 Open 39 -3 In Progress 10 +3 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200217/#osg-software-team","text":"OSG 3.5.10/3.4.44 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200217/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200217/#support-update","text":"Florida (BrianL, Derek): Working to speed up startup of SAM test jobs in their CE; waiting on feedback Purdue (Mat): Helped debug authentication issues with their local HTCondor pool and the new OSG default authentication UIUC (Carl): Debugging quoting issues with condor blahp submission (Derek) Update WLCG report. Stalled uploader which was corrected, and fixed from happening again.","title":"Support Update"},{"location":"meetings/2020/TechArea20200217/#osg-release-team","text":"3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 +0 1 +0 11 +0 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 6 +2 2 +0 9 +2 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 22 +2 6 +0 32 +2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XRootD 4.11.2 uberftp 2.8-3 XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data HCC VOMS cert Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200217/#discussion_1","text":"AI (Tim): Create a JIRA ticket to automate packages ready for testing list","title":"Discussion"},{"location":"meetings/2020/TechArea20200217/#osg-investigations-team","text":"(lots of people outages) TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related) IRIS-HEP Posters!","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200217/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200224/","text":"OSG Technology Area Meeting, 24 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! Carl OOO Mon-Tue BrianL and Diego at the IRIS-HEP review Wed-Fri TimT out Friday and next week, returning March 9 Triage Duty \u00b6 This week: Mat Next week: Diego 12 (+1) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 153 +7 Open 41 +2 In Progress 2 -8 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 2020 Technology Area WBS: https://docs.google.com/spreadsheets/d/1pwJXu1tWnfFrSUPXkuV-fYXJg1RLY3n50XxF85AhUT4/edit?usp=sharing InCommon subject DN format change (state abbreviation -> full state name) will result in a number of vo-client updates in the next few months so we can transition VOs Critical bug/security fix only support for OSG 3.4 starts at the beginning of next month. Double-check ticket labels for release series to build for. OSG 3.5.11 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) Discussion \u00b6 Next GlideinWMS version expected at the end of this week There were questions about how to separate the XRootD TPC transfers for production from XRootD client transfers. We think that we can get the production transfer data from FTS and subtract that from the data uploaded to get the XRootD client numbers. Support Update \u00b6 Florida (BrianL, Derek): Investigating delays in SAM test job startup Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD OSG Release Team \u00b6 3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 2 +0 12 +0 2 +0 16 +0 Open 2 +0 5 +0 5 +0 12 +0 In Progress 0 +0 1 +0 0 +0 1 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 4 +0 18 +0 7 +0 29 +0 Total Software Ready for Testing 3.5.11 Nothing yet Both XCache validation tool 3.4.45 Nothing yet Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data Nothing Operations osg-notify smart quotes Contrib Nothing Discussion \u00b6 AI (Tim): Draft OSG 3.4 Limited Support Announcement. OSG Investigations Team \u00b6 TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 - March 4th Mid-point: Working on SciTokens + StashCache (Globus transition related) Discussion \u00b6 xrootd-scitokens with XCache work will require a lot of testing and is initially targeted for Stash Caches and Origins","title":"February 24, 2020"},{"location":"meetings/2020/TechArea20200224/#osg-technology-area-meeting-24-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 24 February 2020"},{"location":"meetings/2020/TechArea20200224/#announcements","text":"OSG All Hands meeting registration open! Carl OOO Mon-Tue BrianL and Diego at the IRIS-HEP review Wed-Fri TimT out Friday and next week, returning March 9","title":"Announcements"},{"location":"meetings/2020/TechArea20200224/#triage-duty","text":"This week: Mat Next week: Diego 12 (+1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200224/#jira","text":"# of tickets \u0394 State 153 +7 Open 41 +2 In Progress 2 -8 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200224/#osg-software-team","text":"2020 Technology Area WBS: https://docs.google.com/spreadsheets/d/1pwJXu1tWnfFrSUPXkuV-fYXJg1RLY3n50XxF85AhUT4/edit?usp=sharing InCommon subject DN format change (state abbreviation -> full state name) will result in a number of vo-client updates in the next few months so we can transition VOs Critical bug/security fix only support for OSG 3.4 starts at the beginning of next month. Double-check ticket labels for release series to build for. OSG 3.5.11 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200224/#discussion","text":"Next GlideinWMS version expected at the end of this week There were questions about how to separate the XRootD TPC transfers for production from XRootD client transfers. We think that we can get the production transfer data from FTS and subtract that from the data uploaded to get the XRootD client numbers.","title":"Discussion"},{"location":"meetings/2020/TechArea20200224/#support-update","text":"Florida (BrianL, Derek): Investigating delays in SAM test job startup Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD","title":"Support Update"},{"location":"meetings/2020/TechArea20200224/#osg-release-team","text":"3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 2 +0 12 +0 2 +0 16 +0 Open 2 +0 5 +0 5 +0 12 +0 In Progress 0 +0 1 +0 0 +0 1 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 4 +0 18 +0 7 +0 29 +0 Total Software Ready for Testing 3.5.11 Nothing yet Both XCache validation tool 3.4.45 Nothing yet Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data Nothing Operations osg-notify smart quotes Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200224/#discussion_1","text":"AI (Tim): Draft OSG 3.4 Limited Support Announcement.","title":"Discussion"},{"location":"meetings/2020/TechArea20200224/#osg-investigations-team","text":"TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 - March 4th Mid-point: Working on SciTokens + StashCache (Globus transition related)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200224/#discussion_2","text":"xrootd-scitokens with XCache work will require a lot of testing and is initially targeted for Stash Caches and Origins","title":"Discussion"},{"location":"meetings/2020/TechArea20200302/","text":"OSG Technology Area Meeting, 2 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marco, Marian, Mat Announcements \u00b6 TimT OOO this week BrianL OOO Friday and next Monday Triage Duty \u00b6 This week: Diego Next week: ??? 10 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 159 +6 Open 43 +2 In Progress 2 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Did everyone get an email from Freshworks about account migration? OSG 3.5.11/3.4.45 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE Fixed some WN client and host cert/key mounting issues last week AI (Brian): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) Discussion \u00b6 AI (BrianL): Write tickets for TPC config.d and self-registration improvements UCSD and UNL aren't interested in a standalone XRootD container for the time being XCache SciTokens waiting on XRootD RC2, which is expected this week GlideinWMS 3.6.2 RC expected this week Support Update \u00b6 Florida (BrianL, Derek): Investigating delays in SAM test job startup FNAL (Marian): hitting issues with IPv6 due to reverse DNS lookups similar to what we saw at UCSD some time ago (possibly fixed in XRootD 5). For now FNL has turned off IPv6 support on the redirectors. Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD Purdue (Edgar): reinstalled the CMS XCache with all the new redirectors; had documentation requests and notes UConn (Derek): troubleshooting potential issues with yearly summaries OSG Release Team \u00b6 3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 -2 3 -9 11 +9 14 -2 Open 0 -2 2 -3 7 +2 9 -3 In Progress 1 +1 0 -1 4 +4 5 +5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 -3 5 -13 22 +15 28 -1 Total Software Ready for Testing 3.5.11 CCTools 7.0.22 CVMFS 2.7.1 oidc-agent 3.3.1 osg-oasis 16-2 XCache validation tool Both Nothing yet 3.4.45 Singularity 3.5.3 Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data vo-client 100 Operations osg-notify smart quotes Contrib Nothing Discussion \u00b6 AI (BrianL): Contact ET about OSG 3.4 end of regular support dates AI (BrianL): Write weekly ready for testing email AI (BrianL): Prepare for vo-client release Wednesday OSG Investigations Team \u00b6 scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition to gracc2 - March 4th SciTokens+XrootD requires xrootd 5.0. RC2 was suppose to be out last week, maybe this week? (from xcache meeting) Discussion \u00b6 None this week","title":"March 2, 2020"},{"location":"meetings/2020/TechArea20200302/#osg-technology-area-meeting-2-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marco, Marian, Mat","title":"OSG Technology Area Meeting, 2 March 2020"},{"location":"meetings/2020/TechArea20200302/#announcements","text":"TimT OOO this week BrianL OOO Friday and next Monday","title":"Announcements"},{"location":"meetings/2020/TechArea20200302/#triage-duty","text":"This week: Diego Next week: ??? 10 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200302/#jira","text":"# of tickets \u0394 State 159 +6 Open 43 +2 In Progress 2 +4 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200302/#osg-software-team","text":"Did everyone get an email from Freshworks about account migration? OSG 3.5.11/3.4.45 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE Fixed some WN client and host cert/key mounting issues last week AI (Brian): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200302/#discussion","text":"AI (BrianL): Write tickets for TPC config.d and self-registration improvements UCSD and UNL aren't interested in a standalone XRootD container for the time being XCache SciTokens waiting on XRootD RC2, which is expected this week GlideinWMS 3.6.2 RC expected this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200302/#support-update","text":"Florida (BrianL, Derek): Investigating delays in SAM test job startup FNAL (Marian): hitting issues with IPv6 due to reverse DNS lookups similar to what we saw at UCSD some time ago (possibly fixed in XRootD 5). For now FNL has turned off IPv6 support on the redirectors. Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD Purdue (Edgar): reinstalled the CMS XCache with all the new redirectors; had documentation requests and notes UConn (Derek): troubleshooting potential issues with yearly summaries","title":"Support Update"},{"location":"meetings/2020/TechArea20200302/#osg-release-team","text":"3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 -2 3 -9 11 +9 14 -2 Open 0 -2 2 -3 7 +2 9 -3 In Progress 1 +1 0 -1 4 +4 5 +5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 -3 5 -13 22 +15 28 -1 Total Software Ready for Testing 3.5.11 CCTools 7.0.22 CVMFS 2.7.1 oidc-agent 3.3.1 osg-oasis 16-2 XCache validation tool Both Nothing yet 3.4.45 Singularity 3.5.3 Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data vo-client 100 Operations osg-notify smart quotes Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200302/#discussion_1","text":"AI (BrianL): Contact ET about OSG 3.4 end of regular support dates AI (BrianL): Write weekly ready for testing email AI (BrianL): Prepare for vo-client release Wednesday","title":"Discussion"},{"location":"meetings/2020/TechArea20200302/#osg-investigations-team","text":"scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition to gracc2 - March 4th SciTokens+XrootD requires xrootd 5.0. RC2 was suppose to be out last week, maybe this week? (from xcache meeting)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200302/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200309/","text":"OSG Technology Area Meeting, 9 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Mat, Carl, Edgar, Derek, Diego Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Brian 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 163 +4 Open 41 -2 In Progress 5 +3 Ready for Testing 4 +4 Ready for Release OSG Software Team \u00b6 AI (Carl): Release new VO client OSG 3.5.11/3.4.45 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) need to figure out how to get Hadoop working with the container before any Hadoop site can test it Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE AI (Brian (not here)): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Brian (not here)): Demonstrate an HTCondor-CE reporting to the central collector via SSL (SOFTWARE-3939) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) (which is blocked on XRootD RC2) Discussion \u00b6 None this week Support Update \u00b6 None this week OSG Release Team \u00b6 3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 +0 3 +0 9 -2 12 -2 Open 0 +0 2 +0 8 +1 10 +1 In Progress 0 -1 0 +0 4 +0 4 -1 Ready for Testing 1 +1 0 +0 3 +3 4 +4 Ready for Release 1 +0 5 +0 24 +2 30 +2 Total Software Ready for Testing 3.5.11 Pegasus 4.9.3 scitokens-cpp 0.5.0 CCTools 7.0.22 XCache validation tool Both Nothing yet Ready for Release 3.5.11 CVMFS 2.7.1 osg-oasis 16-2 oidc-agent 3.3.1 gsi-openssh 7.4p1-5 Both Nothing yet 3.4.45 Singularity 3.5.3 Data vo-client 101 Operations osg-notify smart quotes Contrib Nothing Sent OSG 3.4 end of regular support date email. Discussion \u00b6 None this week OSG Investigations Team \u00b6 scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released... Discussion \u00b6 None this week","title":"March 9, 2020"},{"location":"meetings/2020/TechArea20200309/#osg-technology-area-meeting-9-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Mat, Carl, Edgar, Derek, Diego","title":"OSG Technology Area Meeting, 9 March 2020"},{"location":"meetings/2020/TechArea20200309/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200309/#triage-duty","text":"This week: Carl Next week: Brian 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200309/#jira","text":"# of tickets \u0394 State 163 +4 Open 41 -2 In Progress 5 +3 Ready for Testing 4 +4 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200309/#osg-software-team","text":"AI (Carl): Release new VO client OSG 3.5.11/3.4.45 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) need to figure out how to get Hadoop working with the container before any Hadoop site can test it Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE AI (Brian (not here)): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Brian (not here)): Demonstrate an HTCondor-CE reporting to the central collector via SSL (SOFTWARE-3939) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) (which is blocked on XRootD RC2)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200309/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200309/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2020/TechArea20200309/#osg-release-team","text":"3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 +0 3 +0 9 -2 12 -2 Open 0 +0 2 +0 8 +1 10 +1 In Progress 0 -1 0 +0 4 +0 4 -1 Ready for Testing 1 +1 0 +0 3 +3 4 +4 Ready for Release 1 +0 5 +0 24 +2 30 +2 Total Software Ready for Testing 3.5.11 Pegasus 4.9.3 scitokens-cpp 0.5.0 CCTools 7.0.22 XCache validation tool Both Nothing yet Ready for Release 3.5.11 CVMFS 2.7.1 osg-oasis 16-2 oidc-agent 3.3.1 gsi-openssh 7.4p1-5 Both Nothing yet 3.4.45 Singularity 3.5.3 Data vo-client 101 Operations osg-notify smart quotes Contrib Nothing Sent OSG 3.4 end of regular support date email.","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200309/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200309/#osg-investigations-team","text":"scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released...","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200309/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200316/","text":"OSG Technology Area Meeting, 16 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Edgar 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 161 -2 Open 40 -1 In Progress 2 -3 Ready for Testing 0 -4 Ready for Release OSG Software Team \u00b6 OSG 3.5.12/3.4.46 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Carl): Various blahp tickets AI (Diego): Release XRootD 4.11.3 (SOFTWARE-4017) AI (BrianL): Release HTCondor-CE (SOFTWARE-4009) AI (Derek): Update XRootD SciTokens 1.2.0 GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts Discussion \u00b6 None this week Support Update \u00b6 Nebraska (Diego): Found a bug with the Phedex download script in the production agent that fixed transfer issues Purdue (Diego): Opened a ticket because there are issues with FTS transfers OSG Release Team \u00b6 3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 5 +2 7 -2 12 +0 Open 0 +0 2 +0 9 +1 11 +1 In Progress 0 +0 0 +0 2 -2 2 -2 Ready for Testing 0 -1 0 +0 0 -3 0 -4 Ready for Release 0 -1 7 +2 18 -6 25 -5 Total Software Ready for Testing 3.5.12 scitokens-cpp 0.5.0 XCache validation tool Both Nothing yet Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 scitokens-cpp update now in EPEL stable EPEL-7 EPEL-8 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA 4030 Discussion \u00b6 None this week","title":"March 16, 2020"},{"location":"meetings/2020/TechArea20200316/#osg-technology-area-meeting-16-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 16 March 2020"},{"location":"meetings/2020/TechArea20200316/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200316/#triage-duty","text":"This week: Brian Next week: Edgar 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200316/#jira","text":"# of tickets \u0394 State 161 -2 Open 40 -1 In Progress 2 -3 Ready for Testing 0 -4 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200316/#osg-software-team","text":"OSG 3.5.12/3.4.46 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Carl): Various blahp tickets AI (Diego): Release XRootD 4.11.3 (SOFTWARE-4017) AI (BrianL): Release HTCondor-CE (SOFTWARE-4009) AI (Derek): Update XRootD SciTokens 1.2.0 GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200316/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200316/#support-update","text":"Nebraska (Diego): Found a bug with the Phedex download script in the production agent that fixed transfer issues Purdue (Diego): Opened a ticket because there are issues with FTS transfers","title":"Support Update"},{"location":"meetings/2020/TechArea20200316/#osg-release-team","text":"3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 5 +2 7 -2 12 +0 Open 0 +0 2 +0 9 +1 11 +1 In Progress 0 +0 0 +0 2 -2 2 -2 Ready for Testing 0 -1 0 +0 0 -3 0 -4 Ready for Release 0 -1 7 +2 18 -6 25 -5 Total Software Ready for Testing 3.5.12 scitokens-cpp 0.5.0 XCache validation tool Both Nothing yet Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200316/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200316/#osg-investigations-team","text":"scitokens-cpp update now in EPEL stable EPEL-7 EPEL-8 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA 4030","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200316/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200323/","text":"OSG Technology Area Meeting, 23 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Edgar Next week: Mat 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 158 -3 Open 38 -2 In Progress 11 +9 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus this Thursday, 26 Mar at 1:30pm Central! OSG 3.5.12/3.4.46 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts Discussion \u00b6 None this week Support Update \u00b6 ALICE (Carl, Derek): they want two different facilities to report under the same name to the WLCG; investigating possibilities LIGO (Edgar, Derek): discussing OASIS manager contact registrations with LIGO management Purdue (Diego): wrote some manual tests for direct transfers and uncovered some issues that he's forwarded onto the GGUS ticket OSG Release Team \u00b6 3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 3 -2 7 +0 10 -2 Open 0 +0 3 +1 4 -5 7 -4 In Progress 0 +0 2 +2 8 +6 10 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 8 +1 19 +1 27 +2 Total Software Ready for Testing 3.5.12 HTCondor CE 4.2.1 Pegasus 4.9.3 lcmaps 1.6.6 scitokens-cpp 0.5.0 XRootD 4.11.3 (Release Candidate 2) XCache validation tool Both XRootD SciTokens 1.2.0 Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA-4030 300+ corrections latter, we are in a good place! Need to evaluate HTCondor-CE tests for availability Discussion \u00b6 None this week","title":"March 23, 2020"},{"location":"meetings/2020/TechArea20200323/#osg-technology-area-meeting-23-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Mat, TimT","title":"OSG Technology Area Meeting, 23 March 2020"},{"location":"meetings/2020/TechArea20200323/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200323/#triage-duty","text":"This week: Edgar Next week: Mat 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200323/#jira","text":"# of tickets \u0394 State 158 -3 Open 38 -2 In Progress 11 +9 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200323/#osg-software-team","text":"Doc focus this Thursday, 26 Mar at 1:30pm Central! OSG 3.5.12/3.4.46 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200323/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200323/#support-update","text":"ALICE (Carl, Derek): they want two different facilities to report under the same name to the WLCG; investigating possibilities LIGO (Edgar, Derek): discussing OASIS manager contact registrations with LIGO management Purdue (Diego): wrote some manual tests for direct transfers and uncovered some issues that he's forwarded onto the GGUS ticket","title":"Support Update"},{"location":"meetings/2020/TechArea20200323/#osg-release-team","text":"3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 3 -2 7 +0 10 -2 Open 0 +0 3 +1 4 -5 7 -4 In Progress 0 +0 2 +2 8 +6 10 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 8 +1 19 +1 27 +2 Total Software Ready for Testing 3.5.12 HTCondor CE 4.2.1 Pegasus 4.9.3 lcmaps 1.6.6 scitokens-cpp 0.5.0 XRootD 4.11.3 (Release Candidate 2) XCache validation tool Both XRootD SciTokens 1.2.0 Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200323/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200323/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA-4030 300+ corrections latter, we are in a good place! Need to evaluate HTCondor-CE tests for availability","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200323/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200330/","text":"OSG Technology Area Meeting, 30 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, TimT Announcements \u00b6 Mat OOO today Switching meeting to Zoom next week OSG support for COVID-19 research: assign any tickets for users or sites to me and set the prio to \"Urgent\" Triage Duty \u00b6 This week: Mat Next week: TimT 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 157 -1 Open 42 +4 In Progress 11 +0 Ready for Testing 2 +2 Ready for Release OSG Software Team \u00b6 OSG 3.5.13/3.4.47 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) AI (Diego): Build XRootD-4.11.3-1.2 (SOFTWARE-4017) with redirector fix GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process AI (Edgar): Try out the self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts New OSG Software testing host (osg-sw-submit.chtc.wisc.edu) is up and ready! Next doc focus 9 Apr 2020 @ 1:30pm Discussion \u00b6 AI (Marian): Add BrianL and Andy to discussion about CMS monitoring configuration AI (Diego): Send BrianL local UCSD XRootD standalone and redirector configurations AI (BrianL): Verify non-UW Software Team access to the new OSG Software testing host Support Update \u00b6 Caltech, Nebraska (Mat): issue with missing GridFTP logs; we have a package that addresses this issue Notre Dame (Edgar): pilots landing on GPU nodes but not able to use the GPUs; we suspect that it's a wrapper script issue Purdue (Diego): saw 5-6 different issues and saw that the first two accounted for 70% of the errors. The next build of XRootD should solve the first issue and they are increasing the # of TCP connections to address the second. OSG Release Team \u00b6 3.4.47 \u0394 Both \u0394 3.5.13 \u0394 Total \u0394 Status 0 +0 0 -3 13 +6 13 +3 Open 0 +0 2 -1 5 +1 7 +0 In Progress 0 +0 1 -1 8 +0 9 -1 Ready for Testing 0 +0 0 +0 2 +2 2 +2 Ready for Release 0 +0 3 -5 28 +9 31 +4 Total Software Ready for Testing 3.5.13 XRootD 4.11.3 HTCondor CE 4.2.1 lcmaps 1.6.6 scitokens-cpp 0.5.0 XCache validation tool osg-xrootd 3.5-12 - osg standalone config Both Nothing yet Ready for Release 3.5.13 Pegasus 4.9.3 globus-gridftp-server-13.20-1.1 Both Nothing yet Data IGTF 1.105 Operations gsi-openssh-7.4p1-5 vm-test-runs-1.1-1 Contrib Nothing Discussion \u00b6 One release this week including software and CA certificates OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 78% SciTokens+XrootD requires xrootd 5.0. RC2 still not released Need to evaluate HTCondor-CE tests for availability Discussion \u00b6 None this week","title":"March 30, 2020"},{"location":"meetings/2020/TechArea20200330/#osg-technology-area-meeting-30-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, TimT","title":"OSG Technology Area Meeting, 30 March 2020"},{"location":"meetings/2020/TechArea20200330/#announcements","text":"Mat OOO today Switching meeting to Zoom next week OSG support for COVID-19 research: assign any tickets for users or sites to me and set the prio to \"Urgent\"","title":"Announcements"},{"location":"meetings/2020/TechArea20200330/#triage-duty","text":"This week: Mat Next week: TimT 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200330/#jira","text":"# of tickets \u0394 State 157 -1 Open 42 +4 In Progress 11 +0 Ready for Testing 2 +2 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200330/#osg-software-team","text":"OSG 3.5.13/3.4.47 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) AI (Diego): Build XRootD-4.11.3-1.2 (SOFTWARE-4017) with redirector fix GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process AI (Edgar): Try out the self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts New OSG Software testing host (osg-sw-submit.chtc.wisc.edu) is up and ready! Next doc focus 9 Apr 2020 @ 1:30pm","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200330/#discussion","text":"AI (Marian): Add BrianL and Andy to discussion about CMS monitoring configuration AI (Diego): Send BrianL local UCSD XRootD standalone and redirector configurations AI (BrianL): Verify non-UW Software Team access to the new OSG Software testing host","title":"Discussion"},{"location":"meetings/2020/TechArea20200330/#support-update","text":"Caltech, Nebraska (Mat): issue with missing GridFTP logs; we have a package that addresses this issue Notre Dame (Edgar): pilots landing on GPU nodes but not able to use the GPUs; we suspect that it's a wrapper script issue Purdue (Diego): saw 5-6 different issues and saw that the first two accounted for 70% of the errors. The next build of XRootD should solve the first issue and they are increasing the # of TCP connections to address the second.","title":"Support Update"},{"location":"meetings/2020/TechArea20200330/#osg-release-team","text":"3.4.47 \u0394 Both \u0394 3.5.13 \u0394 Total \u0394 Status 0 +0 0 -3 13 +6 13 +3 Open 0 +0 2 -1 5 +1 7 +0 In Progress 0 +0 1 -1 8 +0 9 -1 Ready for Testing 0 +0 0 +0 2 +2 2 +2 Ready for Release 0 +0 3 -5 28 +9 31 +4 Total Software Ready for Testing 3.5.13 XRootD 4.11.3 HTCondor CE 4.2.1 lcmaps 1.6.6 scitokens-cpp 0.5.0 XCache validation tool osg-xrootd 3.5-12 - osg standalone config Both Nothing yet Ready for Release 3.5.13 Pegasus 4.9.3 globus-gridftp-server-13.20-1.1 Both Nothing yet Data IGTF 1.105 Operations gsi-openssh-7.4p1-5 vm-test-runs-1.1-1 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200330/#discussion_1","text":"One release this week including software and CA certificates","title":"Discussion"},{"location":"meetings/2020/TechArea20200330/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 78% SciTokens+XrootD requires xrootd 5.0. RC2 still not released Need to evaluate HTCondor-CE tests for availability","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200330/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200406/","text":"OSG Technology Area Meeting, 6 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 New COVID-19 site documentation available: https://osg-htc.org/docs/compute-element/covid-19/ Triage Duty \u00b6 This week: TimT Next week: Diego 9 (-2) open FreshDesk tickets 0 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 157 +0 Open 40 -2 In Progress 8 -3 Ready for Testing 0 -2 Ready for Release OSG Software Team \u00b6 COVID-19 Open Science CE AI (Mat): add POOL secret volume mount and generate a new token for Mats AI (Mat): Create a gittrac ticket for the HTCondor security session string comparison bug AI (BrianL): Advertise consistent schedd name between instances OSG 3.5.15/3.4.49 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Next doc focus 9 Apr 2020 @ 1:30pm Discussion \u00b6 AI (Edgar): Build ENMR singularity image AI (BrianL): Follow-up with Diego about running tests manually to troubleshoot XRootD 5 issues AI (BrianL): Create GlideinWMS 3.7 ticket and assign it to Edgar Diego spoke with XRootD devs about xrootd-lcmaps linked libraries. It built without the libraries so we will test to see it if it stil works. Support Update \u00b6 GlueX (Edgar): Had issues with signing VOMS attributes \u2013 will investigate with BrianL and Carl Purdue, UCSD (Diego): Having issues reproducing the XRootD failures \u2013 we decided that if there aren't regressions, we should just move forward with the release OSG Release Team \u00b6 3.4.48 \u0394 Both \u0394 3.5.14 \u0394 Total \u0394 Status 0 +0 0 +0 10 -3 10 -3 Open 0 +0 0 -2 6 +1 6 -1 In Progress 0 +0 2 +1 4 -4 6 -3 Ready for Testing 0 +0 0 +0 0 -2 0 -2 Ready for Release 0 +0 2 -1 20 -8 22 -9 Total Software Ready for Testing 3.5.14 osg-ce 3.5-5 XRootD 4.11.3 osg-xrootd 3.5-12 - osg standalone config Both Frontier Squid 4.10-3.1 Data VO Packge v103 - Wednesday Operations Nothing Contrib Nothing Discussion \u00b6 AI (Edgar): Get Igor to update to a container with the latest frontier-squid, verify it works, and tag it as stable AI (Edgar): Comment in SOFTWARE-4017 with the results of the UCSD XRootD update OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 91% SciTokens+XrootD requires xrootd 5.0. RC2 is out, in development. Need to evaluate HTCondor-CE tests for availability. Folding@Home is running on the OSG within Singularity. Discussion \u00b6 None this week","title":"April 6, 2020"},{"location":"meetings/2020/TechArea20200406/#osg-technology-area-meeting-6-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 6 April 2020"},{"location":"meetings/2020/TechArea20200406/#announcements","text":"New COVID-19 site documentation available: https://osg-htc.org/docs/compute-element/covid-19/","title":"Announcements"},{"location":"meetings/2020/TechArea20200406/#triage-duty","text":"This week: TimT Next week: Diego 9 (-2) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200406/#jira","text":"# of tickets \u0394 State 157 +0 Open 40 -2 In Progress 8 -3 Ready for Testing 0 -2 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200406/#osg-software-team","text":"COVID-19 Open Science CE AI (Mat): add POOL secret volume mount and generate a new token for Mats AI (Mat): Create a gittrac ticket for the HTCondor security session string comparison bug AI (BrianL): Advertise consistent schedd name between instances OSG 3.5.15/3.4.49 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Next doc focus 9 Apr 2020 @ 1:30pm","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200406/#discussion","text":"AI (Edgar): Build ENMR singularity image AI (BrianL): Follow-up with Diego about running tests manually to troubleshoot XRootD 5 issues AI (BrianL): Create GlideinWMS 3.7 ticket and assign it to Edgar Diego spoke with XRootD devs about xrootd-lcmaps linked libraries. It built without the libraries so we will test to see it if it stil works.","title":"Discussion"},{"location":"meetings/2020/TechArea20200406/#support-update","text":"GlueX (Edgar): Had issues with signing VOMS attributes \u2013 will investigate with BrianL and Carl Purdue, UCSD (Diego): Having issues reproducing the XRootD failures \u2013 we decided that if there aren't regressions, we should just move forward with the release","title":"Support Update"},{"location":"meetings/2020/TechArea20200406/#osg-release-team","text":"3.4.48 \u0394 Both \u0394 3.5.14 \u0394 Total \u0394 Status 0 +0 0 +0 10 -3 10 -3 Open 0 +0 0 -2 6 +1 6 -1 In Progress 0 +0 2 +1 4 -4 6 -3 Ready for Testing 0 +0 0 +0 0 -2 0 -2 Ready for Release 0 +0 2 -1 20 -8 22 -9 Total Software Ready for Testing 3.5.14 osg-ce 3.5-5 XRootD 4.11.3 osg-xrootd 3.5-12 - osg standalone config Both Frontier Squid 4.10-3.1 Data VO Packge v103 - Wednesday Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200406/#discussion_1","text":"AI (Edgar): Get Igor to update to a container with the latest frontier-squid, verify it works, and tag it as stable AI (Edgar): Comment in SOFTWARE-4017 with the results of the UCSD XRootD update","title":"Discussion"},{"location":"meetings/2020/TechArea20200406/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 91% SciTokens+XrootD requires xrootd 5.0. RC2 is out, in development. Need to evaluate HTCondor-CE tests for availability. Folding@Home is running on the OSG within Singularity.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200406/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200413/","text":"OSG Technology Area Meeting, 13 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Edgar OOO today Carl OOO Friday and next Monday Triage Duty \u00b6 This week: Diego Next week: BrianL (?) 11 (+2) open FreshDesk tickets 2 (+2) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 147 +0 Open 46 +6 In Progress 3 -5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 COVID-19 Open Science CE AI (Mat): send BrianL list of technical debt AI (BrianL): Begin work on persisting jobs across instances OSG 3.5.16/3.4.50 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Carl): Various gratia-probe tickets (SOFTWARE-3980) AI (Diego): Kick off OSG 3.4 tests for XRootD 4.11.3 for 3.4 (SOFTWARE-3056) AI (BrianL): Release GlideinWMS 3.7 (SOFTWARE-4051) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Doc focus postponed to 7 May 2020 @ 1:30pm Discussion \u00b6 None this week Support Update \u00b6 Harvester (BrianL): Worked with Harvester developers to troubleshoot an issue where clients failed to connect to the SciTokens test CE. Turned out to be an authentication failure that resulted in an unhelpful client error message. SWT2 (Carl): Continued troubleshooting missing March accounting data. UCSD (Diego): CMS load test transfers were failing due to mismatched checksums. Turned out to be a problem with the source files and HDFS checksums needing to be updated rather than an issue in the transfer itself. OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 1 +1 0 +0 10 +4 11 +5 In Progress 0 +0 0 -2 1 -3 1 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +1 0 -2 23 +3 24 +2 Total Software Ready for Testing 3.5.16 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 97% GRACC reports pruning this week. SciTokens + XCache - no progress last week. LIGO is waiting on me. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effor from Diego and Derek. Discussion \u00b6 None this week","title":"April 13, 2020"},{"location":"meetings/2020/TechArea20200413/#osg-technology-area-meeting-13-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 13 April 2020"},{"location":"meetings/2020/TechArea20200413/#announcements","text":"Edgar OOO today Carl OOO Friday and next Monday","title":"Announcements"},{"location":"meetings/2020/TechArea20200413/#triage-duty","text":"This week: Diego Next week: BrianL (?) 11 (+2) open FreshDesk tickets 2 (+2) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200413/#jira","text":"# of tickets \u0394 State 147 +0 Open 46 +6 In Progress 3 -5 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200413/#osg-software-team","text":"COVID-19 Open Science CE AI (Mat): send BrianL list of technical debt AI (BrianL): Begin work on persisting jobs across instances OSG 3.5.16/3.4.50 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Carl): Various gratia-probe tickets (SOFTWARE-3980) AI (Diego): Kick off OSG 3.4 tests for XRootD 4.11.3 for 3.4 (SOFTWARE-3056) AI (BrianL): Release GlideinWMS 3.7 (SOFTWARE-4051) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Doc focus postponed to 7 May 2020 @ 1:30pm","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200413/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200413/#support-update","text":"Harvester (BrianL): Worked with Harvester developers to troubleshoot an issue where clients failed to connect to the SciTokens test CE. Turned out to be an authentication failure that resulted in an unhelpful client error message. SWT2 (Carl): Continued troubleshooting missing March accounting data. UCSD (Diego): CMS load test transfers were failing due to mismatched checksums. Turned out to be a problem with the source files and HDFS checksums needing to be updated rather than an issue in the transfer itself.","title":"Support Update"},{"location":"meetings/2020/TechArea20200413/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 1 +1 0 +0 10 +4 11 +5 In Progress 0 +0 0 -2 1 -3 1 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +1 0 -2 23 +3 24 +2 Total Software Ready for Testing 3.5.16 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200413/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200413/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 97% GRACC reports pruning this week. SciTokens + XCache - no progress last week. LIGO is waiting on me. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effor from Diego and Derek.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200413/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200420/","text":"OSG Technology Area Meeting, 20 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Carl OOO today Triage Duty \u00b6 This week: BrianL Next week: Edgar 6 (-5) open FreshDesk tickets 1 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 152 -5 Open 50 +4 In Progress 3 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG Release tickets AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Mat): troubleshoot issue with EL8 builds due to dependencies being satisfied by modules instead of by repositories AI (BrianL): Begin work on persisting jobs across Open Science CE instances Discussion \u00b6 None this week Support Update \u00b6 AGLT2, BNL, MWT2 (BrianL): negotiator bug in the latest HTCondor 8.8 versions that prevent some jobs from matching when using hierarchical accounting group quotas. HTCondor team working on verifying a fix. AMNH (Derek, Edgar): now running their squid at Manhattan Internet2 node. New CE being added as well. Brown (Marian): had Webex troubleshooting session last week and will have a follow-up this week. Has some XRootD + NFS configuration that we may want to add to our own documentation. Cybera (Diego): having some issues setting up COVID-19 routes and will discuss with BrianL offline GlideinWMS (Marco, Edgar): a few proxy different proxy issues (missing pathlen, cannot generate VO proxies for a sub-vo, and proxy lifetime not getting passed along properly) that are expected to make it into the next 3.6 and 3.7 releases Purdue (Diego): was able to produce an issue similar to transfers getting stuck by setting and removing network bandwidth restrictions. Will discuss short timeouts with gfal2 client developers. Rutgers (Derek, BrianL): Issues with Accounting groups, prioritization of COVID research. OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 9 -3 9 -3 Open 1 +0 0 +0 14 +4 15 +4 In Progress 0 +0 0 +0 2 +1 2 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +0 0 +0 25 +2 26 +2 Total Software Ready for Testing 3.5.16 GlideinWMS 3.7 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) Significant GRACC reports refactor. SciTokens + XCache - no progress last week. Goal for this week. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Validation presentation this week to CMS / FNAL. Discussion \u00b6 None this week","title":"April 20, 2020"},{"location":"meetings/2020/TechArea20200420/#osg-technology-area-meeting-20-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 20 April 2020"},{"location":"meetings/2020/TechArea20200420/#announcements","text":"Carl OOO today","title":"Announcements"},{"location":"meetings/2020/TechArea20200420/#triage-duty","text":"This week: BrianL Next week: Edgar 6 (-5) open FreshDesk tickets 1 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200420/#jira","text":"# of tickets \u0394 State 152 -5 Open 50 +4 In Progress 3 +0 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200420/#osg-software-team","text":"OSG Release tickets AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Mat): troubleshoot issue with EL8 builds due to dependencies being satisfied by modules instead of by repositories AI (BrianL): Begin work on persisting jobs across Open Science CE instances","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200420/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200420/#support-update","text":"AGLT2, BNL, MWT2 (BrianL): negotiator bug in the latest HTCondor 8.8 versions that prevent some jobs from matching when using hierarchical accounting group quotas. HTCondor team working on verifying a fix. AMNH (Derek, Edgar): now running their squid at Manhattan Internet2 node. New CE being added as well. Brown (Marian): had Webex troubleshooting session last week and will have a follow-up this week. Has some XRootD + NFS configuration that we may want to add to our own documentation. Cybera (Diego): having some issues setting up COVID-19 routes and will discuss with BrianL offline GlideinWMS (Marco, Edgar): a few proxy different proxy issues (missing pathlen, cannot generate VO proxies for a sub-vo, and proxy lifetime not getting passed along properly) that are expected to make it into the next 3.6 and 3.7 releases Purdue (Diego): was able to produce an issue similar to transfers getting stuck by setting and removing network bandwidth restrictions. Will discuss short timeouts with gfal2 client developers. Rutgers (Derek, BrianL): Issues with Accounting groups, prioritization of COVID research.","title":"Support Update"},{"location":"meetings/2020/TechArea20200420/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 9 -3 9 -3 Open 1 +0 0 +0 14 +4 15 +4 In Progress 0 +0 0 +0 2 +1 2 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +0 0 +0 25 +2 26 +2 Total Software Ready for Testing 3.5.16 GlideinWMS 3.7 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200420/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200420/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) Significant GRACC reports refactor. SciTokens + XCache - no progress last week. Goal for this week. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Validation presentation this week to CMS / FNAL.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200420/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200427/","text":"OSG Technology Area Meeting, 27 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT Announcements \u00b6 BrianL OOO Wednesday Triage Duty \u00b6 This week: Edgar Next week: Carl 8 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 -6 Open 45 -5 In Progress 10 +7 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.16 AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): need to find testers for the EL8 WN RPM and container (we suggested LIGO and Mat, respectively). Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins Discussion \u00b6 None this week Support Update \u00b6 Alice T2 (Derek): Naming consistency with WLCG. Brown (Marian): working on Topology registration and finishing touches on remaining CMS issues Networking (Derek): Pipeline malfunctioned last week, may take surgery to recover data. SWT2 CPB (Derek): Accounting malfunction may require gratia-probe slurm surgery OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 8 -1 8 -1 Open 0 -1 0 +0 9 -5 9 -6 In Progress 0 +0 0 +0 6 +4 6 +4 Ready for Testing 1 +1 0 +0 1 +1 2 +2 Ready for Release 1 +0 0 +0 24 -1 25 -1 Total Software Ready for Testing 3.5.16 CVMFS 2.7.2 Frontier Squid 4.11-2.1 blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) SciTokens + XCache - no progress last week. Goal for this week. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure. Discussion \u00b6 None this week","title":"April 27, 2020"},{"location":"meetings/2020/TechArea20200427/#osg-technology-area-meeting-27-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 27 April 2020"},{"location":"meetings/2020/TechArea20200427/#announcements","text":"BrianL OOO Wednesday","title":"Announcements"},{"location":"meetings/2020/TechArea20200427/#triage-duty","text":"This week: Edgar Next week: Carl 8 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200427/#jira","text":"# of tickets \u0394 State 146 -6 Open 45 -5 In Progress 10 +7 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200427/#osg-software-team","text":"OSG 3.5.16 AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): need to find testers for the EL8 WN RPM and container (we suggested LIGO and Mat, respectively). Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200427/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200427/#support-update","text":"Alice T2 (Derek): Naming consistency with WLCG. Brown (Marian): working on Topology registration and finishing touches on remaining CMS issues Networking (Derek): Pipeline malfunctioned last week, may take surgery to recover data. SWT2 CPB (Derek): Accounting malfunction may require gratia-probe slurm surgery","title":"Support Update"},{"location":"meetings/2020/TechArea20200427/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 8 -1 8 -1 Open 0 -1 0 +0 9 -5 9 -6 In Progress 0 +0 0 +0 6 +4 6 +4 Ready for Testing 1 +1 0 +0 1 +1 2 +2 Ready for Release 1 +0 0 +0 24 -1 25 -1 Total Software Ready for Testing 3.5.16 CVMFS 2.7.2 Frontier Squid 4.11-2.1 blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200427/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200427/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) SciTokens + XCache - no progress last week. Goal for this week. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200427/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200504/","text":"OSG Technology Area Meeting, 4 May 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 8 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 +0 Open 45 -1 In Progress 12 +2 Ready for Testing 2 +1 Ready for Release OSG Software Team \u00b6 AI (BrianL, Carl, Mat): Release IGTF CA update, making sure to test InCommon certs between EL6 and EL7 hosts OSG 3.5.17 AI (Edgar): XRootD 4.12.0 RC2 ready upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor_ce_info_status (SOFTWARE-3963) Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins Old Fermicloud VMs have old DNs, need to be rebooted for new DNs Doc focus this Thursday @ 1:30pm CDT Discussion \u00b6 AI (TimT): transition OSG Travis repos from .org to .com Support Update \u00b6 Clarkson, Old Dominion, Portland State (BrianL, Derek): engagements with new Slurm sites. Clarkson and Portland asked for examples of Slurm config \"for the OSG\", which brought up the question of whether or not we should document these recommendations. We don't want to take on the batch system support burden but this is something that sites are asking for. SWT2 (Derek): Old records are now in the GRACC, waiting for EGI numbers to be updated OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 1 -7 1 -7 Open 0 +0 0 +0 0 -9 0 -9 In Progress 0 +0 0 +0 11 +5 11 +5 Ready for Testing 1 +0 0 +0 1 +0 2 +0 Ready for Release 1 +0 0 +0 13 -11 14 -11 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 CMVFS 2.7.2 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data IGTF 1.106 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Paused while Marian is in transition to Europe. SciTokens + XCache - Lots of progress. Back and forth with XRootD devs. TLS is not well documented. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure. Discussion \u00b6 None this week","title":"May 4, 2020"},{"location":"meetings/2020/TechArea20200504/#osg-technology-area-meeting-4-may-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 4 May 2020"},{"location":"meetings/2020/TechArea20200504/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200504/#triage-duty","text":"This week: Carl Next week: Mat 8 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200504/#jira","text":"# of tickets \u0394 State 146 +0 Open 45 -1 In Progress 12 +2 Ready for Testing 2 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200504/#osg-software-team","text":"AI (BrianL, Carl, Mat): Release IGTF CA update, making sure to test InCommon certs between EL6 and EL7 hosts OSG 3.5.17 AI (Edgar): XRootD 4.12.0 RC2 ready upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor_ce_info_status (SOFTWARE-3963) Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins Old Fermicloud VMs have old DNs, need to be rebooted for new DNs Doc focus this Thursday @ 1:30pm CDT","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200504/#discussion","text":"AI (TimT): transition OSG Travis repos from .org to .com","title":"Discussion"},{"location":"meetings/2020/TechArea20200504/#support-update","text":"Clarkson, Old Dominion, Portland State (BrianL, Derek): engagements with new Slurm sites. Clarkson and Portland asked for examples of Slurm config \"for the OSG\", which brought up the question of whether or not we should document these recommendations. We don't want to take on the batch system support burden but this is something that sites are asking for. SWT2 (Derek): Old records are now in the GRACC, waiting for EGI numbers to be updated","title":"Support Update"},{"location":"meetings/2020/TechArea20200504/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 1 -7 1 -7 Open 0 +0 0 +0 0 -9 0 -9 In Progress 0 +0 0 +0 11 +5 11 +5 Ready for Testing 1 +0 0 +0 1 +0 2 +0 Ready for Release 1 +0 0 +0 13 -11 14 -11 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 CMVFS 2.7.2 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data IGTF 1.106 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200504/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200504/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Paused while Marian is in transition to Europe. SciTokens + XCache - Lots of progress. Back and forth with XRootD devs. TLS is not well documented. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200504/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200511/","text":"OSG Technology Area Meeting, 11 May 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 13 (+5) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 147 +1 Open 45 +1 In Progress 13 +1 Ready for Testing 3 +1 Ready for Release OSG Software Team \u00b6 Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins OSG 3.5.16 AI (Mat): Release HTCondor 8.8.9 and 8.9.7 (SOFTWARE-4079, SOFTWARE-4080) AI (Edgar): Release vo-client with EIC VOMS (SOFTWARE-4097) OSG 3.5.17 AI (Edgar): XRootD 4.12.0 officially released upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Carl): Release gratia-probe 1.20.13+ (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor ce info status (SOFTWARE-3963) Discussion \u00b6 Marco has some Singularity and condor_chirp fixes and updates in GlideinWMS 3.6.3 (expected in 2-3 weeks) Support Update \u00b6 Brown (Marian): waiting on a response from Brown about registering their XRootD in Topology JLab (Edgar): actively troubleshooting issues with submit hosts authenticating with different hosts with Let's Encrypt certs LIGO (Carl, Derek): followed up on some extra VO attribtues showing up in the accounting dashboards Notre Dame (Carl): answered questions about passing along AccountingGroup via the BLAH SWT2 (Derek): had to do Slurm Gratia probe surgery for Oklahoma and UTA. We're getting tired of doing this so UNL is going to pilot using the HTCondor-CE Gratia probe at their Slurm site. OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 2 +1 2 +1 Open 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 8 -3 8 -3 Ready for Testing 1 +0 0 +0 2 +1 3 +1 Ready for Release 1 +0 0 +0 12 -1 13 -1 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 GlideinWMS 3.7 Ready for Release 3.5.16 CMVFS 2.7.2 CCTools 7.1.5 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (Carl): Create a follow-on ticket to fix the INDEX in the CA certificate packaging AI (Edgar): Test the latest Frontier Squid package via the fresh container OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - As always, very complicated... Need to figure out the singularity container pruning. Turned on garbage collection on the CVMFS repo. Cleaned up a TON of space, no longer need to worry so much about pruning. XRootD monitoring collector validation is starting. Parallel infrastructure is 90% up and running. Slurm gratia probe considerations Discussion \u00b6 None this week","title":"May 11, 2020"},{"location":"meetings/2020/TechArea20200511/#osg-technology-area-meeting-11-may-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 11 May 2020"},{"location":"meetings/2020/TechArea20200511/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200511/#triage-duty","text":"This week: Mat Next week: TimT 13 (+5) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200511/#jira","text":"# of tickets \u0394 State 147 +1 Open 45 +1 In Progress 13 +1 Ready for Testing 3 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200511/#osg-software-team","text":"Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins OSG 3.5.16 AI (Mat): Release HTCondor 8.8.9 and 8.9.7 (SOFTWARE-4079, SOFTWARE-4080) AI (Edgar): Release vo-client with EIC VOMS (SOFTWARE-4097) OSG 3.5.17 AI (Edgar): XRootD 4.12.0 officially released upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Carl): Release gratia-probe 1.20.13+ (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor ce info status (SOFTWARE-3963)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200511/#discussion","text":"Marco has some Singularity and condor_chirp fixes and updates in GlideinWMS 3.6.3 (expected in 2-3 weeks)","title":"Discussion"},{"location":"meetings/2020/TechArea20200511/#support-update","text":"Brown (Marian): waiting on a response from Brown about registering their XRootD in Topology JLab (Edgar): actively troubleshooting issues with submit hosts authenticating with different hosts with Let's Encrypt certs LIGO (Carl, Derek): followed up on some extra VO attribtues showing up in the accounting dashboards Notre Dame (Carl): answered questions about passing along AccountingGroup via the BLAH SWT2 (Derek): had to do Slurm Gratia probe surgery for Oklahoma and UTA. We're getting tired of doing this so UNL is going to pilot using the HTCondor-CE Gratia probe at their Slurm site.","title":"Support Update"},{"location":"meetings/2020/TechArea20200511/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 2 +1 2 +1 Open 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 8 -3 8 -3 Ready for Testing 1 +0 0 +0 2 +1 3 +1 Ready for Release 1 +0 0 +0 12 -1 13 -1 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 GlideinWMS 3.7 Ready for Release 3.5.16 CMVFS 2.7.2 CCTools 7.1.5 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200511/#discussion_1","text":"AI (Carl): Create a follow-on ticket to fix the INDEX in the CA certificate packaging AI (Edgar): Test the latest Frontier Squid package via the fresh container","title":"Discussion"},{"location":"meetings/2020/TechArea20200511/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - As always, very complicated... Need to figure out the singularity container pruning. Turned on garbage collection on the CVMFS repo. Cleaned up a TON of space, no longer need to worry so much about pruning. XRootD monitoring collector validation is starting. Parallel infrastructure is 90% up and running. Slurm gratia probe considerations","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200511/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200518/","text":"OSG Technology Area Meeting, 18 May 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 Next week's meeting canceled (Memorial Day) HTCondor Week Tuesday and Wednesday: https://agenda.hep.wisc.edu/event/1440/overview IRIS-HEP planning retreat next Tuesday - Thursday BrianL out Friday Triage Duty \u00b6 This week: TimT Next week: Diego 8 (-5) open FreshDesk tickets 0 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 143 -4 Open 43 -2 In Progress 16 +3 Ready for Testing 1 -2 Ready for Release OSG Software Team \u00b6 Nightly VMU tests are delayed due to image creation failures due to lack of resources. Adding retries and limits to the number of local universe jobs Please fill out the next doc focus doodle poll OSG 3.5.17 AI (Mat): Release HTCondor 8.9.7 (SOFTWARE-4080) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Mat): Update de-osgify HTCondor-CE ticket with investigation notes. We can punt on condor ce info status but not on HTCondor-CE View (SOFTWARE-3963) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Edgar): Build OASIS packages for EL8 (JIRA ticket incoming) AI (Carl): Finish up new CE emailer (SOFTWARE-4057) Discussion \u00b6 None this week Support Update \u00b6 EIC (Edgar): working on getting pilots into JLab with EIC and JLab admins; separately, planning on how to do two origins serving the same data (one at BNL and one at JLab) FNAL (Carl): abandoned tracking down UCLA Frontier Squid (not an OSG site, no longer a problem for CVMFS ops groups) Nebraska, SurfSARA (Edgar): troubleshooting various issues with authenticated CVMFS cache issues OSG Release Team \u00b6 3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +1 0 +0 7 +5 8 +6 Open 0 +0 0 +0 10 +10 10 +10 In Progress 0 +0 3 +3 10 +2 13 +5 Ready for Testing 0 -1 0 +0 1 -1 1 -2 Ready for Release 1 +0 3 +3 28 +16 32 +19 Total Software Ready for Testing 3.5.17 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 gratia-probe 1.20.13 Upcoming XRootD 5.0.0 EL8 wn client blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.17 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - Document incoming. Talking with Andy about schedules. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations Guinea Pig Nebraska Discussion \u00b6 None this week","title":"May 18, 2020"},{"location":"meetings/2020/TechArea20200518/#osg-technology-area-meeting-18-may-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 18 May 2020"},{"location":"meetings/2020/TechArea20200518/#announcements","text":"Next week's meeting canceled (Memorial Day) HTCondor Week Tuesday and Wednesday: https://agenda.hep.wisc.edu/event/1440/overview IRIS-HEP planning retreat next Tuesday - Thursday BrianL out Friday","title":"Announcements"},{"location":"meetings/2020/TechArea20200518/#triage-duty","text":"This week: TimT Next week: Diego 8 (-5) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200518/#jira","text":"# of tickets \u0394 State 143 -4 Open 43 -2 In Progress 16 +3 Ready for Testing 1 -2 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200518/#osg-software-team","text":"Nightly VMU tests are delayed due to image creation failures due to lack of resources. Adding retries and limits to the number of local universe jobs Please fill out the next doc focus doodle poll OSG 3.5.17 AI (Mat): Release HTCondor 8.9.7 (SOFTWARE-4080) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Mat): Update de-osgify HTCondor-CE ticket with investigation notes. We can punt on condor ce info status but not on HTCondor-CE View (SOFTWARE-3963) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Edgar): Build OASIS packages for EL8 (JIRA ticket incoming) AI (Carl): Finish up new CE emailer (SOFTWARE-4057)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200518/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200518/#support-update","text":"EIC (Edgar): working on getting pilots into JLab with EIC and JLab admins; separately, planning on how to do two origins serving the same data (one at BNL and one at JLab) FNAL (Carl): abandoned tracking down UCLA Frontier Squid (not an OSG site, no longer a problem for CVMFS ops groups) Nebraska, SurfSARA (Edgar): troubleshooting various issues with authenticated CVMFS cache issues","title":"Support Update"},{"location":"meetings/2020/TechArea20200518/#osg-release-team","text":"3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +1 0 +0 7 +5 8 +6 Open 0 +0 0 +0 10 +10 10 +10 In Progress 0 +0 3 +3 10 +2 13 +5 Ready for Testing 0 -1 0 +0 1 -1 1 -2 Ready for Release 1 +0 3 +3 28 +16 32 +19 Total Software Ready for Testing 3.5.17 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 gratia-probe 1.20.13 Upcoming XRootD 5.0.0 EL8 wn client blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.17 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200518/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200518/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - Document incoming. Talking with Andy about schedules. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations Guinea Pig Nebraska","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200518/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200601/","text":"OSG Technology Area Meeting, 1 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Mat, Marian, Marco Mambelli, TimT Announcements \u00b6 Carl OOO Mon/Tue Triage Duty \u00b6 This week: BrianL Next week: Carl 12 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 147 -1 Open 44 +1 In Progress 9 +1 Ready for Testing 11 +0 Ready for Release OSG Software Team \u00b6 BrianL working on IRIS-HEP quarterly report this week Due to the CA expiration, Koji builds from moria hang. Workaround is to hit t followed by Enter to accept the moria certificate. OSG 3.5.17 AI (Diego): Move XCache 1.4-related tickets to RFT AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Carl): Finish up new CE emailer (SOFTWARE-4057) Discussion \u00b6 None this week Support Update \u00b6 BNL (Edgar): Working on LIGO data frame data working, which is difficult because they get CVMFS config from EGI but cvmfs-x509-helper from OSG. CMS (Marco): helped troubleshoot an issue due to CA expiration over the weekend because of stale CAs in a CMS docker container FNAL (Derek): Worked to get accounting up and running on new cluster using HTCondor-CE probe with SLURM. OSGConnect (Derek): SciTokens CredMon fixes. Causing user submission issues, to top priority. OU (Derek): Helped Horst get a CE up and running on an old cluster. Though, Horst did most of the work. Syracuse (Edgar, Derek): submit host reporting records as pilots UFL (Marco): Troubleshooting issues finding local Singularity with SAM tests Utah (BrianL): Pilots fail to report back to the gWMS collector due to a bad X509_USER_CERT set by Bosco. This is due to a bad Bosco tarball from the CHTC at least 2 weeks ago so any Hosted CEs instantiated during this time may experience these same failures. OSG Release Team \u00b6 3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +0 0 +0 5 -2 6 -2 Open 0 +0 0 +0 10 +0 10 +0 In Progress 0 +0 1 -2 6 -4 7 -6 Ready for Testing 0 +0 3 +3 7 +6 10 +9 Ready for Release 1 +0 4 +1 28 +0 33 +1 Total Software Ready for Testing 3.5.17 Upcoming: HTCondor 8.9.7 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release 3.5.17 GlideinWMS 3.7 gratia-probe 1.20.13 blahp 1.18.46 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations FNAL is up and running successfully. Nebraska is next, then the world! New GRACC report for Tim sent out this morning! Investigations team is helping with IRIS-HEP Analysis cluster demo at Nebraska. BrianB and Derek are helping. Derek mostly for xcache + tokens components. Discussion \u00b6 None this week","title":"June 1, 2020"},{"location":"meetings/2020/TechArea20200601/#osg-technology-area-meeting-1-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Mat, Marian, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 1 June 2020"},{"location":"meetings/2020/TechArea20200601/#announcements","text":"Carl OOO Mon/Tue","title":"Announcements"},{"location":"meetings/2020/TechArea20200601/#triage-duty","text":"This week: BrianL Next week: Carl 12 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200601/#jira","text":"# of tickets \u0394 State 147 -1 Open 44 +1 In Progress 9 +1 Ready for Testing 11 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200601/#osg-software-team","text":"BrianL working on IRIS-HEP quarterly report this week Due to the CA expiration, Koji builds from moria hang. Workaround is to hit t followed by Enter to accept the moria certificate. OSG 3.5.17 AI (Diego): Move XCache 1.4-related tickets to RFT AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Carl): Finish up new CE emailer (SOFTWARE-4057)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200601/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200601/#support-update","text":"BNL (Edgar): Working on LIGO data frame data working, which is difficult because they get CVMFS config from EGI but cvmfs-x509-helper from OSG. CMS (Marco): helped troubleshoot an issue due to CA expiration over the weekend because of stale CAs in a CMS docker container FNAL (Derek): Worked to get accounting up and running on new cluster using HTCondor-CE probe with SLURM. OSGConnect (Derek): SciTokens CredMon fixes. Causing user submission issues, to top priority. OU (Derek): Helped Horst get a CE up and running on an old cluster. Though, Horst did most of the work. Syracuse (Edgar, Derek): submit host reporting records as pilots UFL (Marco): Troubleshooting issues finding local Singularity with SAM tests Utah (BrianL): Pilots fail to report back to the gWMS collector due to a bad X509_USER_CERT set by Bosco. This is due to a bad Bosco tarball from the CHTC at least 2 weeks ago so any Hosted CEs instantiated during this time may experience these same failures.","title":"Support Update"},{"location":"meetings/2020/TechArea20200601/#osg-release-team","text":"3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +0 0 +0 5 -2 6 -2 Open 0 +0 0 +0 10 +0 10 +0 In Progress 0 +0 1 -2 6 -4 7 -6 Ready for Testing 0 +0 3 +3 7 +6 10 +9 Ready for Release 1 +0 4 +1 28 +0 33 +1 Total Software Ready for Testing 3.5.17 Upcoming: HTCondor 8.9.7 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release 3.5.17 GlideinWMS 3.7 gratia-probe 1.20.13 blahp 1.18.46 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200601/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200601/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations FNAL is up and running successfully. Nebraska is next, then the world! New GRACC report for Tim sent out this morning! Investigations team is helping with IRIS-HEP Analysis cluster demo at Nebraska. BrianB and Derek are helping. Derek mostly for xcache + tokens components.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200601/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200608/","text":"OSG Technology Area Meeting, 8 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Mat, Marian, TimT Announcements \u00b6 If you are taking Wednesday Jun 10 off for #ShutDownSTEM, please let me know and try to keep an eye on critical infrastructure or urgent items during the day Triage Duty \u00b6 This week: Carl Next week: Edgar 7 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 148 +1 Open 43 -1 In Progress 14 +5 Ready for Testing 0 -11 Ready for Release OSG Software Team \u00b6 OSG 3.5.18 AI (BrianL): Automatically remove completed jobs after 30 days (SOFTWARE-4108) AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) Discussion \u00b6 xrootd-hdfs and xrootd-lcmaps currently don't create versioned shared libs. Now that XRootD advertises its major version, it should be reflected in the plugin shared libs. AI (BrianL): create ticket for testing GFAL client for Edgar AI (BrianL): discuss Cybera CE management with Jeff and Igor AI (Diego): noticed that development label of the atlas-xcache container is old. This is expected so he should delete that label from Docker Hub and update the documentation to use fresh instead. EL8 Bosco tarballs fail to build with the new BLAHP source. We don't have a pressing need for this yet but would like this to be resolved in the HTCondor 9.0.0 release Support Update \u00b6 Bellarmine (Mat): CE wasn't accepting pilots, turned out to be an old osg-ca-certs version GLOW (Mat): GLOW cache also experienced problems due to the out-of-date osg-ca-certs. Mat will follow-up with Operations to see why check_mk tests didn't catch this JLab (Edgar): working on security questionnaires so that he can continue setting up services (also has to fill out questionnaires for BNL and FNAL) OSG Release Team \u00b6 3.4.52 \u0394 Both \u0394 3.5.18 \u0394 Total \u0394 Status 0 -1 1 +1 5 +0 6 +0 Open 0 +0 0 +0 8 -2 8 -2 In Progress 0 +0 2 +1 8 +2 10 +3 Ready for Testing 0 +0 0 -3 0 -7 0 -10 Ready for Release 0 -1 3 -1 21 -7 24 -9 Total Software Ready for Testing 3.5.18 VOMS 2.0.14-1.6 Frontier Squid 4.11-3.1 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): assign Frontier Squid, XCache, and xrootd-lcmaps tickets to Edgar so he can let us know if he's testing the latest versions in his container deployments HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required Horst has tested and verified the VOMS update OSG Investigations Team \u00b6 Derek out today Want to do gracc 2 switchover soon; will wait until Derek's back and also need (another) reindex. Discussion \u00b6 None this week","title":"June 8, 2020"},{"location":"meetings/2020/TechArea20200608/#osg-technology-area-meeting-8-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Mat, Marian, TimT","title":"OSG Technology Area Meeting, 8 June 2020"},{"location":"meetings/2020/TechArea20200608/#announcements","text":"If you are taking Wednesday Jun 10 off for #ShutDownSTEM, please let me know and try to keep an eye on critical infrastructure or urgent items during the day","title":"Announcements"},{"location":"meetings/2020/TechArea20200608/#triage-duty","text":"This week: Carl Next week: Edgar 7 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200608/#jira","text":"# of tickets \u0394 State 148 +1 Open 43 -1 In Progress 14 +5 Ready for Testing 0 -11 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200608/#osg-software-team","text":"OSG 3.5.18 AI (BrianL): Automatically remove completed jobs after 30 days (SOFTWARE-4108) AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200608/#discussion","text":"xrootd-hdfs and xrootd-lcmaps currently don't create versioned shared libs. Now that XRootD advertises its major version, it should be reflected in the plugin shared libs. AI (BrianL): create ticket for testing GFAL client for Edgar AI (BrianL): discuss Cybera CE management with Jeff and Igor AI (Diego): noticed that development label of the atlas-xcache container is old. This is expected so he should delete that label from Docker Hub and update the documentation to use fresh instead. EL8 Bosco tarballs fail to build with the new BLAHP source. We don't have a pressing need for this yet but would like this to be resolved in the HTCondor 9.0.0 release","title":"Discussion"},{"location":"meetings/2020/TechArea20200608/#support-update","text":"Bellarmine (Mat): CE wasn't accepting pilots, turned out to be an old osg-ca-certs version GLOW (Mat): GLOW cache also experienced problems due to the out-of-date osg-ca-certs. Mat will follow-up with Operations to see why check_mk tests didn't catch this JLab (Edgar): working on security questionnaires so that he can continue setting up services (also has to fill out questionnaires for BNL and FNAL)","title":"Support Update"},{"location":"meetings/2020/TechArea20200608/#osg-release-team","text":"3.4.52 \u0394 Both \u0394 3.5.18 \u0394 Total \u0394 Status 0 -1 1 +1 5 +0 6 +0 Open 0 +0 0 +0 8 -2 8 -2 In Progress 0 +0 2 +1 8 +2 10 +3 Ready for Testing 0 +0 0 -3 0 -7 0 -10 Ready for Release 0 -1 3 -1 21 -7 24 -9 Total Software Ready for Testing 3.5.18 VOMS 2.0.14-1.6 Frontier Squid 4.11-3.1 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200608/#discussion_1","text":"AI (TimT): assign Frontier Squid, XCache, and xrootd-lcmaps tickets to Edgar so he can let us know if he's testing the latest versions in his container deployments HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required Horst has tested and verified the VOMS update","title":"Discussion"},{"location":"meetings/2020/TechArea20200608/#osg-investigations-team","text":"Derek out today Want to do gracc 2 switchover soon; will wait until Derek's back and also need (another) reindex.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200608/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200615/","text":"OSG Technology Area Meeting, 15 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Mat, BrianL, Diego, TimT, Carl, Edgar, Marian, Marco Mambelli Announcements \u00b6 Brian giving HTCondor-CE webinar at EGI; reached out to team members for help during Q&A. Doc focus this Thursday Triage Duty \u00b6 This week: Edgar Next week: Mat 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 150 +2 Open 42 -1 In Progress 10 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.18 AI (BrianL): Release HTCondor-CE 4.3.0+ AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Waiting on review from Derek on HDFS plugin. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 There does not seem to be a new GFAL client in EPEL testing for EL 7 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages for EL8 (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) Discussion \u00b6 CentOS repos were broken Friday/weekend, causing false errors in VMU tests. BrianL sent team members filtered spreadsheets for the SW WBS; please prioritize tasks marked OVERDUE. GlideinWMS Marco found problem that when a grid universe job lands against an invalid grid resource, it remains idle forever, instead of going on hold. Try reproducing on 8.8 and send email to condor-users. Denis still working on token auth between frontend and collector; might be a good idea to do some pair programming with an OSG developer so we can help with HTCondor config etc. Support Update \u00b6 BrianL: helped AGLT2 with problem where home dir was on a shared file system and condor was incorrectly assuming the shared file system was mounted on the execute host as well as the submit host, and not doing file transfer. Edgar: helped LIGO with interpreting graphs. We have some bad names in there like how \"batch records\" are actually \"pilot records\". Also the meaning of \"dedicated\" vs \"opportunistic\" isn't obvious. Also Syracuse is listed as owned by LIGO which is wrong. Edgar should talk to Derek about making some of these easier to understand. Marco: GlideinWMS 3.7: using TOKEN auth results in tarballs that have some libraries from the OS. This should be fixed in 3.7.1. OSG Release Team \u00b6 3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 -1 5 +0 5 -1 Open 0 +0 0 +0 10 +2 10 +2 In Progress 0 +0 0 -2 4 -4 4 -6 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -3 19 -2 19 -5 Total Software Ready for Testing 3.5.19 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required OSG Investigations Team \u00b6 Derek was on slate training. GRACC 2 switch was performed today. Lots of investigation effort to figure out bottlenecks. Lots of communication with XRootD team on TLS + Tokens support. Discussion \u00b6 Edgar's student starts in July to do scale testing for HTTP third party copy. Considering testing authenticated CVMFS but might not be worth doing it until the SciTokens switch (since we'd just have to do it again).","title":"June 15, 2020"},{"location":"meetings/2020/TechArea20200615/#osg-technology-area-meeting-15-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Mat, BrianL, Diego, TimT, Carl, Edgar, Marian, Marco Mambelli","title":"OSG Technology Area Meeting, 15 June 2020"},{"location":"meetings/2020/TechArea20200615/#announcements","text":"Brian giving HTCondor-CE webinar at EGI; reached out to team members for help during Q&A. Doc focus this Thursday","title":"Announcements"},{"location":"meetings/2020/TechArea20200615/#triage-duty","text":"This week: Edgar Next week: Mat 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200615/#jira","text":"# of tickets \u0394 State 150 +2 Open 42 -1 In Progress 10 -4 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200615/#osg-software-team","text":"OSG 3.5.18 AI (BrianL): Release HTCondor-CE 4.3.0+ AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Waiting on review from Derek on HDFS plugin. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 There does not seem to be a new GFAL client in EPEL testing for EL 7 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages for EL8 (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200615/#discussion","text":"CentOS repos were broken Friday/weekend, causing false errors in VMU tests. BrianL sent team members filtered spreadsheets for the SW WBS; please prioritize tasks marked OVERDUE. GlideinWMS Marco found problem that when a grid universe job lands against an invalid grid resource, it remains idle forever, instead of going on hold. Try reproducing on 8.8 and send email to condor-users. Denis still working on token auth between frontend and collector; might be a good idea to do some pair programming with an OSG developer so we can help with HTCondor config etc.","title":"Discussion"},{"location":"meetings/2020/TechArea20200615/#support-update","text":"BrianL: helped AGLT2 with problem where home dir was on a shared file system and condor was incorrectly assuming the shared file system was mounted on the execute host as well as the submit host, and not doing file transfer. Edgar: helped LIGO with interpreting graphs. We have some bad names in there like how \"batch records\" are actually \"pilot records\". Also the meaning of \"dedicated\" vs \"opportunistic\" isn't obvious. Also Syracuse is listed as owned by LIGO which is wrong. Edgar should talk to Derek about making some of these easier to understand. Marco: GlideinWMS 3.7: using TOKEN auth results in tarballs that have some libraries from the OS. This should be fixed in 3.7.1.","title":"Support Update"},{"location":"meetings/2020/TechArea20200615/#osg-release-team","text":"3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 -1 5 +0 5 -1 Open 0 +0 0 +0 10 +2 10 +2 In Progress 0 +0 0 -2 4 -4 4 -6 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -3 19 -2 19 -5 Total Software Ready for Testing 3.5.19 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200615/#discussion_1","text":"HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required","title":"Discussion"},{"location":"meetings/2020/TechArea20200615/#osg-investigations-team","text":"Derek was on slate training. GRACC 2 switch was performed today. Lots of investigation effort to figure out bottlenecks. Lots of communication with XRootD team on TLS + Tokens support.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200615/#discussion_2","text":"Edgar's student starts in July to do scale testing for HTTP third party copy. Considering testing authenticated CVMFS but might not be worth doing it until the SciTokens switch (since we'd just have to do it again).","title":"Discussion"},{"location":"meetings/2020/TechArea20200622/","text":"OSG Technology Area Meeting, 22 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 151 +1 Open 36 -6 In Progress 18 +8 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Carl): Release CCTools 7.1.6+ (SOFTWARE-4132) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Also remove the XRootD version requirement that was causing upgrade issues. The changes can be tested together. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 The new client works with XRootD 4; still cannot test on XRootD 5rc4. Edgar is in communication with Andy to debug and fix. Two problems with XRootD: HTTPS is not recognized as a plugin and the proxy is being rejected. AI (Edgar): Update a VO frontend to GlideinWMS 3.7 Edgar updated the JLab frontend to GlideinWMS 3.7-1. Seems stable but there are other, unrelated issues at JLab. AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Some back and forth with Dave Dykstra, who is experiencing authorization issues. Since the data is public, it's possible that the authorization check can be dropped. Should check that it causes no privacy issues (for example). AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) The tagging will be done on the Resource level, not Resource Group; Derek will have to adjust GRACC import script appropriately, though it's low priority. Discussion \u00b6 None this week. Support Update \u00b6 None this week. OSG Release Team \u00b6 3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 -5 0 -5 Open 0 +0 0 +0 0 -10 0 -10 In Progress 0 +0 1 +1 11 +7 12 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +1 11 -8 12 -7 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC2 transition tasks are still ongoing. XRootD Monitoring Validation is ongoing, and take significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested properties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Lots of communication with XRootD team on TLS + Tokens support. Discussion \u00b6 None this week","title":"June 22, 2020"},{"location":"meetings/2020/TechArea20200622/#osg-technology-area-meeting-22-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 22 June 2020"},{"location":"meetings/2020/TechArea20200622/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200622/#triage-duty","text":"This week: Mat Next week: TimT 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200622/#jira","text":"# of tickets \u0394 State 151 +1 Open 36 -6 In Progress 18 +8 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200622/#osg-software-team","text":"OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Carl): Release CCTools 7.1.6+ (SOFTWARE-4132) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Also remove the XRootD version requirement that was causing upgrade issues. The changes can be tested together. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 The new client works with XRootD 4; still cannot test on XRootD 5rc4. Edgar is in communication with Andy to debug and fix. Two problems with XRootD: HTTPS is not recognized as a plugin and the proxy is being rejected. AI (Edgar): Update a VO frontend to GlideinWMS 3.7 Edgar updated the JLab frontend to GlideinWMS 3.7-1. Seems stable but there are other, unrelated issues at JLab. AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Some back and forth with Dave Dykstra, who is experiencing authorization issues. Since the data is public, it's possible that the authorization check can be dropped. Should check that it causes no privacy issues (for example). AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) The tagging will be done on the Resource level, not Resource Group; Derek will have to adjust GRACC import script appropriately, though it's low priority.","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200622/#discussion","text":"None this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200622/#support-update","text":"None this week.","title":"Support Update"},{"location":"meetings/2020/TechArea20200622/#osg-release-team","text":"3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 -5 0 -5 Open 0 +0 0 +0 0 -10 0 -10 In Progress 0 +0 1 +1 11 +7 12 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +1 11 -8 12 -7 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200622/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200622/#osg-investigations-team","text":"GRACC2 transition tasks are still ongoing. XRootD Monitoring Validation is ongoing, and take significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested properties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Lots of communication with XRootD team on TLS + Tokens support.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200622/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200629/","text":"OSG Technology Area Meeting, 29 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian, Derek, Diego, Marian, Mat, Edgar, TimT, Marco Mambelli Announcements \u00b6 Carl OOO today Edgar OOO Tue + Wed afternoons; Thu UCSD, UNL out Friday Mat out Friday Brian out next Mon and Tue Tim out for two weeks starting next Mon Triage Duty \u00b6 This week: TimT Next week: Diego 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 152 +1 Open 40 +4 In Progress 20 +2 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): verify the version of GFAL client you tested so we can give it karma (SOFTWARE-4120) Edgar will also test GFAL client + xrootd 5 on the same machine AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Finish doc for VM base images, separating out the effort required to building EL8 vs the rest (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) Discussion \u00b6 Support Update \u00b6 Edgar: - Georgia Tech StashCache using very old version of the packages; the error is about not being able to get an Authfile from topology. - Clas12 is registered as a project but not a VO, which was causing issues because they are sending batch records tagged with a \"Clas12\" VO. Since they are part of JLab, they should be under the JLab umbrella but they are using their own top-level VOMS attribute. Clas12 will be registered as a VO under the JLab VO in topology (similar to how DUNE is registered). Diego: - Helped Riccardo di Maria set up an XRootD dev environment. Riccardo was compiling XRootD himself, which resulted in a different version number for XRootD and this led to dependency resolution issues when installing the plugins. - Worked with JINR sysadmin to test HTTP transfers between UCSD and JINR. OSG Release Team \u00b6 3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 +0 0 +0 Open 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 1 +0 11 +0 12 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +0 12 +1 13 +1 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 OSG Investigations Team \u00b6 GRACC2 Transitioned! Still some services have not completely transitioned. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is this week. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Wroking with interested parties. No XRootD 5 RC5 yet for TLS testing Discussion \u00b6 None this week","title":"June 29, 2020"},{"location":"meetings/2020/TechArea20200629/#osg-technology-area-meeting-29-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian, Derek, Diego, Marian, Mat, Edgar, TimT, Marco Mambelli","title":"OSG Technology Area Meeting, 29 June 2020"},{"location":"meetings/2020/TechArea20200629/#announcements","text":"Carl OOO today Edgar OOO Tue + Wed afternoons; Thu UCSD, UNL out Friday Mat out Friday Brian out next Mon and Tue Tim out for two weeks starting next Mon","title":"Announcements"},{"location":"meetings/2020/TechArea20200629/#triage-duty","text":"This week: TimT Next week: Diego 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200629/#jira","text":"# of tickets \u0394 State 152 +1 Open 40 +4 In Progress 20 +2 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200629/#osg-software-team","text":"OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): verify the version of GFAL client you tested so we can give it karma (SOFTWARE-4120) Edgar will also test GFAL client + xrootd 5 on the same machine AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Finish doc for VM base images, separating out the effort required to building EL8 vs the rest (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200629/#discussion","text":"","title":"Discussion"},{"location":"meetings/2020/TechArea20200629/#support-update","text":"Edgar: - Georgia Tech StashCache using very old version of the packages; the error is about not being able to get an Authfile from topology. - Clas12 is registered as a project but not a VO, which was causing issues because they are sending batch records tagged with a \"Clas12\" VO. Since they are part of JLab, they should be under the JLab umbrella but they are using their own top-level VOMS attribute. Clas12 will be registered as a VO under the JLab VO in topology (similar to how DUNE is registered). Diego: - Helped Riccardo di Maria set up an XRootD dev environment. Riccardo was compiling XRootD himself, which resulted in a different version number for XRootD and this led to dependency resolution issues when installing the plugins. - Worked with JINR sysadmin to test HTTP transfers between UCSD and JINR.","title":"Support Update"},{"location":"meetings/2020/TechArea20200629/#osg-release-team","text":"3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 +0 0 +0 Open 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 1 +0 11 +0 12 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +0 12 +1 13 +1 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200629/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2020/TechArea20200629/#osg-investigations-team","text":"GRACC2 Transitioned! Still some services have not completely transitioned. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is this week. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Wroking with interested parties. No XRootD 5 RC5 yet for TLS testing","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200629/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200706/","text":"OSG Technology Area Meeting, 6 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Marco Mambelli, Marian, Mat Announcements \u00b6 Tim out for two weeks starting today Brian out today and tomorrow Triage Duty \u00b6 This week: Diego Next week: Brian 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 155 +3 Open 45 +5 In Progress 17 -3 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Create VMU test images EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) AI (Diego): Build gfal2-plugin-xrootd for upcoming (SOFTWARE-4160) Discussion \u00b6 None. Support Update \u00b6 None. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 5 +5 5 +0 Open 0 +0 0 +0 6 +5 6 +5 In Progress 0 +0 0 -1 11 +0 11 -1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -1 22 +11 22 +9 Total Software Ready for Testing 3.5.20 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens-cpp 0.5.1 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 OSG Investigations Team \u00b6 GRACC2 Transition is complete. Two students are working with Derek: IRIS-HEP fellowship for \"Proactive site monitoring\": Using outlier analysis and ML to find problem sites from accounting data Other student is attempting to re-write stashcp in Go: statically compiled and allow for inclusion of libraries. With XRootD 5 rc5 candidate, update testbed with TLS support and upstream changes. XRootD validation: Beginning report writing. Discussion \u00b6 None this week","title":"July 6, 2020"},{"location":"meetings/2020/TechArea20200706/#osg-technology-area-meeting-6-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Marco Mambelli, Marian, Mat","title":"OSG Technology Area Meeting, 6 July 2020"},{"location":"meetings/2020/TechArea20200706/#announcements","text":"Tim out for two weeks starting today Brian out today and tomorrow","title":"Announcements"},{"location":"meetings/2020/TechArea20200706/#triage-duty","text":"This week: Diego Next week: Brian 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200706/#jira","text":"# of tickets \u0394 State 155 +3 Open 45 +5 In Progress 17 -3 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200706/#osg-software-team","text":"OSG 3.5.20 AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Create VMU test images EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) AI (Diego): Build gfal2-plugin-xrootd for upcoming (SOFTWARE-4160)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200706/#discussion","text":"None.","title":"Discussion"},{"location":"meetings/2020/TechArea20200706/#support-update","text":"None.","title":"Support Update"},{"location":"meetings/2020/TechArea20200706/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 5 +5 5 +0 Open 0 +0 0 +0 6 +5 6 +5 In Progress 0 +0 0 -1 11 +0 11 -1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -1 22 +11 22 +9 Total Software Ready for Testing 3.5.20 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens-cpp 0.5.1 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200706/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2020/TechArea20200706/#osg-investigations-team","text":"GRACC2 Transition is complete. Two students are working with Derek: IRIS-HEP fellowship for \"Proactive site monitoring\": Using outlier analysis and ML to find problem sites from accounting data Other student is attempting to re-write stashcp in Go: statically compiled and allow for inclusion of libraries. With XRootD 5 rc5 candidate, update testbed with TLS support and upstream changes. XRootD validation: Beginning report writing.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200706/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200713/","text":"OSG Technology Area Meeting, 13 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Marco Mambelli, Mat Announcements \u00b6 Mat OOO tomorrow TimT OOO until next Monday Derek OOO next week OSG User School this week and next week Triage Duty \u00b6 This week: Edgar Next week: Carl 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 164 +9 Open 45 +5 In Progress 11 -6 Ready for Testing 10 +9 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Diego): Investigate XRootD 5 VMU failures (SOFTWARE-3923) AI (Edgar): Work with XRootD developers to obtain a patch for XRootD 5 and build it in OSG Containers AI (Edgar): Review XCache default directories PR (SOFTWARE-4159) AI (Edgar): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (Edgar): Promote frontier-squid container to stable (SOFTWARE-4156) AI (Carl): Transition software base and Frontier Squid to GitHub Actions (SOFTWARE-4171, SOFTWARE-4172) Enterprise Linux 8 AI (Edgar): Test OpenSSL 1.1.1 support for xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (BrianL): Design a plan with Derek/BrianB to generate pilot records in the OSG pilot container (SOFTWARE-4169) Discussion \u00b6 The task of tagging CC resources will be performed by Hosted CE operators (for Hosted CEs) or by BrianL or delegate for other resources. Actual tagging will wait until the site's CC status is public. GlideinWMS \u00b6 Developers continuing to work on Python 3 migration Marco will build test versions of GlideinWMS into the osg-contrib repos Support Update \u00b6 Edgar working with Georgia Tech for fixing their cache; will set up a screen sharing session in order to speed up communication with admins. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 6 +1 6 +1 Open 0 +0 0 +0 8 +2 8 +2 In Progress 0 +0 0 +0 4 -7 4 -7 Ready for Testing 0 +0 0 +0 9 +9 9 +9 Ready for Release 0 +0 0 +0 27 +5 27 +5 Total Software Ready for Testing 3.5.20 osg-xrootd 3.5-13 scitokens-cpp 0.5.1 Upcoming: XRootD 5.0.0 Ready for Release HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 Edgar will check if the logging changes in osg-xrootd 3.5-13 are included in his current containers. No release this week. OSG Investigations Team \u00b6 OSG Summer School is this week, Derek is participating. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is continuing. Several patches accepted upstream. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Working with interested parties, some are slow to respond. But, Mats is happy. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list). Discussion \u00b6 None this week","title":"July 13, 2020"},{"location":"meetings/2020/TechArea20200713/#osg-technology-area-meeting-13-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 13 July 2020"},{"location":"meetings/2020/TechArea20200713/#announcements","text":"Mat OOO tomorrow TimT OOO until next Monday Derek OOO next week OSG User School this week and next week","title":"Announcements"},{"location":"meetings/2020/TechArea20200713/#triage-duty","text":"This week: Edgar Next week: Carl 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200713/#jira","text":"# of tickets \u0394 State 164 +9 Open 45 +5 In Progress 11 -6 Ready for Testing 10 +9 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200713/#osg-software-team","text":"OSG 3.5.20 AI (Diego): Investigate XRootD 5 VMU failures (SOFTWARE-3923) AI (Edgar): Work with XRootD developers to obtain a patch for XRootD 5 and build it in OSG Containers AI (Edgar): Review XCache default directories PR (SOFTWARE-4159) AI (Edgar): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (Edgar): Promote frontier-squid container to stable (SOFTWARE-4156) AI (Carl): Transition software base and Frontier Squid to GitHub Actions (SOFTWARE-4171, SOFTWARE-4172) Enterprise Linux 8 AI (Edgar): Test OpenSSL 1.1.1 support for xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (BrianL): Design a plan with Derek/BrianB to generate pilot records in the OSG pilot container (SOFTWARE-4169)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200713/#discussion","text":"The task of tagging CC resources will be performed by Hosted CE operators (for Hosted CEs) or by BrianL or delegate for other resources. Actual tagging will wait until the site's CC status is public.","title":"Discussion"},{"location":"meetings/2020/TechArea20200713/#glideinwms","text":"Developers continuing to work on Python 3 migration Marco will build test versions of GlideinWMS into the osg-contrib repos","title":"GlideinWMS"},{"location":"meetings/2020/TechArea20200713/#support-update","text":"Edgar working with Georgia Tech for fixing their cache; will set up a screen sharing session in order to speed up communication with admins.","title":"Support Update"},{"location":"meetings/2020/TechArea20200713/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 6 +1 6 +1 Open 0 +0 0 +0 8 +2 8 +2 In Progress 0 +0 0 +0 4 -7 4 -7 Ready for Testing 0 +0 0 +0 9 +9 9 +9 Ready for Release 0 +0 0 +0 27 +5 27 +5 Total Software Ready for Testing 3.5.20 osg-xrootd 3.5-13 scitokens-cpp 0.5.1 Upcoming: XRootD 5.0.0 Ready for Release HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200713/#discussion_1","text":"Edgar will check if the logging changes in osg-xrootd 3.5-13 are included in his current containers. No release this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200713/#osg-investigations-team","text":"OSG Summer School is this week, Derek is participating. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is continuing. Several patches accepted upstream. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Working with interested parties, some are slow to respond. But, Mats is happy. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list).","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200713/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200720/","text":"OSG Technology Area Meeting, 20 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT Announcements \u00b6 Derek OOO this week OSG User School ongoing this week Triage Duty \u00b6 This week: Carl Next week: BrianL 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 166 +2 Open 44 -1 In Progress 15 +4 Ready for Testing 11 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.21 AI (Diego): Add package NVR table to XRootD plugin tickets and mark RFT (SOFTWARE-4093, SOFTWARE-4137) Diego is ready to promote plugins but is waiting on a PR review for xrootd-cmstfc. AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (Diego): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (BrianL): Add XRootD 5 based XCache image builds (SOFTWARE-4181) AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) Close to working; needs cleanup and PR review. AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169) Discussion \u00b6 Ongoing storage ticket with Brown; currently it's not OSG-related troubleshooting, so it would be better served if it's tracked by CMS coordinators. Carl working on moving building container to GitHub actions; this enables us to make updates to the software-base image and have them trigger builds for all descendent images. Edgar will be working on DOMA tasks so will not have time for software work. BrianL and Marian are interested in seeing XCache-related documentation that Edgar writes. Edgar has been running an XRootD 5 cache in Sunnyvale. No problems so far but there have been auth issues reported against XRootD 5; BrianL will find the GitHub issue so Edgar can test. Support Update \u00b6 Edgar: - #65322 -- CMU is having difficulties with GridFTP and XRootD. - Multi-core pilots at Syracuse not matching; Edgar requests help from HTCondor developers, who request additional logs from Syracuse. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 1 -5 1 -5 Open 0 +0 0 +0 5 -3 5 -3 In Progress 0 +0 0 +0 4 +0 4 +0 Ready for Testing 0 +0 0 +0 10 +1 10 +1 Ready for Release 0 +0 0 +0 20 -7 20 -7 Total Software Ready for Testing 3.5.20 ATLAS and CMS XCache containers osg-xrootd 3.5-13 Upcoming: XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations osg-build 1.16.2 Frontier-Squid 4.12-2 Contrib Nothing Discussion \u00b6 Release this week. OSG Investigations Team \u00b6 Outage of personel last week, Marian was available only on Monday last week OSG Summer School is ongoing this week. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list). organizing presentation on http://gitbhub.com/xrootd/xrootd-k8s-operator on next xcache meeting, IN2P3 folks involved GRACC tape backup broke last week, investigated root cause, turned out to be FNAL issue and fixed by the end of business day on last Friday (operations effort) Discussion \u00b6 None this week","title":"July 20, 2020"},{"location":"meetings/2020/TechArea20200720/#osg-technology-area-meeting-20-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 20 July 2020"},{"location":"meetings/2020/TechArea20200720/#announcements","text":"Derek OOO this week OSG User School ongoing this week","title":"Announcements"},{"location":"meetings/2020/TechArea20200720/#triage-duty","text":"This week: Carl Next week: BrianL 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200720/#jira","text":"# of tickets \u0394 State 166 +2 Open 44 -1 In Progress 15 +4 Ready for Testing 11 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200720/#osg-software-team","text":"OSG 3.5.21 AI (Diego): Add package NVR table to XRootD plugin tickets and mark RFT (SOFTWARE-4093, SOFTWARE-4137) Diego is ready to promote plugins but is waiting on a PR review for xrootd-cmstfc. AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (Diego): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (BrianL): Add XRootD 5 based XCache image builds (SOFTWARE-4181) AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) Close to working; needs cleanup and PR review. AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200720/#discussion","text":"Ongoing storage ticket with Brown; currently it's not OSG-related troubleshooting, so it would be better served if it's tracked by CMS coordinators. Carl working on moving building container to GitHub actions; this enables us to make updates to the software-base image and have them trigger builds for all descendent images. Edgar will be working on DOMA tasks so will not have time for software work. BrianL and Marian are interested in seeing XCache-related documentation that Edgar writes. Edgar has been running an XRootD 5 cache in Sunnyvale. No problems so far but there have been auth issues reported against XRootD 5; BrianL will find the GitHub issue so Edgar can test.","title":"Discussion"},{"location":"meetings/2020/TechArea20200720/#support-update","text":"Edgar: - #65322 -- CMU is having difficulties with GridFTP and XRootD. - Multi-core pilots at Syracuse not matching; Edgar requests help from HTCondor developers, who request additional logs from Syracuse.","title":"Support Update"},{"location":"meetings/2020/TechArea20200720/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 1 -5 1 -5 Open 0 +0 0 +0 5 -3 5 -3 In Progress 0 +0 0 +0 4 +0 4 +0 Ready for Testing 0 +0 0 +0 10 +1 10 +1 Ready for Release 0 +0 0 +0 20 -7 20 -7 Total Software Ready for Testing 3.5.20 ATLAS and CMS XCache containers osg-xrootd 3.5-13 Upcoming: XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations osg-build 1.16.2 Frontier-Squid 4.12-2 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200720/#discussion_1","text":"Release this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200720/#osg-investigations-team","text":"Outage of personel last week, Marian was available only on Monday last week OSG Summer School is ongoing this week. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list). organizing presentation on http://gitbhub.com/xrootd/xrootd-k8s-operator on next xcache meeting, IN2P3 folks involved GRACC tape backup broke last week, investigated root cause, turned out to be FNAL issue and fixed by the end of business day on last Friday (operations effort)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200720/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200727/","text":"OSG Technology Area Meeting, 27 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL OOO next week Mat OOO Monday and Friday Doc focus doodle poll sent Triage Duty \u00b6 This week: BrianL Next week: Mat 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 167 +1 Open 41 -3 In Progress 18 +3 Ready for Testing 4 -7 Ready for Release OSG Software Team \u00b6 OSG 3.5.21 AI (Carl): Release gratia-probe 1.20.14+, create ticket for 4af0a53 (SOFTWARE-4193) AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) HTCondor in osg-development for EL8; Edgar can now build the XRootD metapackages and use them for testing AI (Diego): Release scitokens for EL8 (SOFTWARE-4126) AI (Diego): Kick off Frontier Squid EL8 VMU (SOFTWARE-4105) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (Mat, Edgar): Change osg-test tests that are marked \"el7 only\" to \"el7 and el8\" AI (Mat, TimT): Build condor 8.9 for el8 AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169) Discussion \u00b6 Marco: No Fermicloud EL8 template available yet, nor is there an ETA; admins planning to upgrade OpenNebula before starting work GlideinWMS release coming soon Support Update \u00b6 None this week OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.21 \u0394 Total \u0394 Status 0 +0 0 +0 5 +4 5 +4 Open 0 +0 0 +0 3 -2 3 -2 In Progress 0 +0 0 +0 17 +13 17 +13 Ready for Testing 0 +0 0 +0 4 -6 4 -6 Ready for Release 0 +0 0 +0 29 +9 29 +9 Total Software Ready for Testing 3.5.21 osg-wn-client 3.5-4 on EL8 stashcache-client 6.0.0 (EL8) osg-flock 1.1 osg-update-vos 1.4.0 (EL8) oidc-agent 3.3.3 xrootd-lcmaps (EL8) XRootD plugins - version matching VOMS 2.1.0 (EL8) osg-xrootd 3.5-13 - reduce logging CVMFS 2.7.3 / cvmfs-config-2.4-4 / osg-oasis 16-5 (EL8) Upcoming XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.1 osg-pki-tools 3.4.0 osg-system-profiler 1.6.0 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 Release this week. OSG Investigations Team \u00b6 Outage of personel last week, Marian was available only on Monday last week Top priority for Deigo and Derek: XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming. Discussion \u00b6 None this week","title":"July 27, 2020"},{"location":"meetings/2020/TechArea20200727/#osg-technology-area-meeting-27-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 27 July 2020"},{"location":"meetings/2020/TechArea20200727/#announcements","text":"BrianL OOO next week Mat OOO Monday and Friday Doc focus doodle poll sent","title":"Announcements"},{"location":"meetings/2020/TechArea20200727/#triage-duty","text":"This week: BrianL Next week: Mat 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200727/#jira","text":"# of tickets \u0394 State 167 +1 Open 41 -3 In Progress 18 +3 Ready for Testing 4 -7 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200727/#osg-software-team","text":"OSG 3.5.21 AI (Carl): Release gratia-probe 1.20.14+, create ticket for 4af0a53 (SOFTWARE-4193) AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) HTCondor in osg-development for EL8; Edgar can now build the XRootD metapackages and use them for testing AI (Diego): Release scitokens for EL8 (SOFTWARE-4126) AI (Diego): Kick off Frontier Squid EL8 VMU (SOFTWARE-4105) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (Mat, Edgar): Change osg-test tests that are marked \"el7 only\" to \"el7 and el8\" AI (Mat, TimT): Build condor 8.9 for el8 AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200727/#discussion","text":"Marco: No Fermicloud EL8 template available yet, nor is there an ETA; admins planning to upgrade OpenNebula before starting work GlideinWMS release coming soon","title":"Discussion"},{"location":"meetings/2020/TechArea20200727/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2020/TechArea20200727/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.21 \u0394 Total \u0394 Status 0 +0 0 +0 5 +4 5 +4 Open 0 +0 0 +0 3 -2 3 -2 In Progress 0 +0 0 +0 17 +13 17 +13 Ready for Testing 0 +0 0 +0 4 -6 4 -6 Ready for Release 0 +0 0 +0 29 +9 29 +9 Total Software Ready for Testing 3.5.21 osg-wn-client 3.5-4 on EL8 stashcache-client 6.0.0 (EL8) osg-flock 1.1 osg-update-vos 1.4.0 (EL8) oidc-agent 3.3.3 xrootd-lcmaps (EL8) XRootD plugins - version matching VOMS 2.1.0 (EL8) osg-xrootd 3.5-13 - reduce logging CVMFS 2.7.3 / cvmfs-config-2.4-4 / osg-oasis 16-5 (EL8) Upcoming XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.1 osg-pki-tools 3.4.0 osg-system-profiler 1.6.0 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200727/#discussion_1","text":"Release this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200727/#osg-investigations-team","text":"Outage of personel last week, Marian was available only on Monday last week Top priority for Deigo and Derek: XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200727/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200803/","text":"OSG Technology Area Meeting, 3 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Edgar, Marian, Tim Announcements \u00b6 BrianL OOO this week Mat OOO Monday Carl OOO Thursday Triage Duty \u00b6 This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 166 -1 Open 41 +0 In Progress 20 +2 Ready for Testing 0 -4 Ready for Release OSG Software Team \u00b6 AI (Derek): XCache 1.5.0 breaks osg-test tests and docker-xcache CI (preventing image tag updates!), probably due to hardcoded Authfiles in the tests of both: https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache_origin.sh#L10 https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache.sh#L9 https://github.com/opensciencegrid/osg-test/blob/master/osgtest/tests/test_155_stashcache.py#L81-L100 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Doc Focus scheduled for August 13 1:30pm CDT Discussion \u00b6 Derek: scitokens-cpp is already in EPEL 7 and 8. Do we need it in OSG 3.5? Support Update \u00b6 Edgar: Helping SDSC with some CC* grant work OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 7 +2 7 +2 Open 0 +0 0 +0 6 +3 6 +3 In Progress 0 +0 0 +0 12 -5 12 -5 Ready for Testing 0 +0 0 +0 0 -4 0 -4 Ready for Release 0 +0 0 +0 25 -4 25 -4 Total Software Ready for Testing 3.5.21 oidc-agent 3.3.3 XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 XRootD 5.0.0 is ready for release OSG Investigations Team \u00b6 Validation document is in \"Draft\" CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. Derek needs help with XCache test failures. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. Discussion \u00b6 None this week","title":"August 3, 2020"},{"location":"meetings/2020/TechArea20200803/#osg-technology-area-meeting-3-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Edgar, Marian, Tim","title":"OSG Technology Area Meeting, 3 August 2020"},{"location":"meetings/2020/TechArea20200803/#announcements","text":"BrianL OOO this week Mat OOO Monday Carl OOO Thursday","title":"Announcements"},{"location":"meetings/2020/TechArea20200803/#triage-duty","text":"This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200803/#jira","text":"# of tickets \u0394 State 166 -1 Open 41 +0 In Progress 20 +2 Ready for Testing 0 -4 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200803/#osg-software-team","text":"AI (Derek): XCache 1.5.0 breaks osg-test tests and docker-xcache CI (preventing image tag updates!), probably due to hardcoded Authfiles in the tests of both: https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache_origin.sh#L10 https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache.sh#L9 https://github.com/opensciencegrid/osg-test/blob/master/osgtest/tests/test_155_stashcache.py#L81-L100 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Doc Focus scheduled for August 13 1:30pm CDT","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200803/#discussion","text":"Derek: scitokens-cpp is already in EPEL 7 and 8. Do we need it in OSG 3.5?","title":"Discussion"},{"location":"meetings/2020/TechArea20200803/#support-update","text":"Edgar: Helping SDSC with some CC* grant work","title":"Support Update"},{"location":"meetings/2020/TechArea20200803/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 7 +2 7 +2 Open 0 +0 0 +0 6 +3 6 +3 In Progress 0 +0 0 +0 12 -5 12 -5 Ready for Testing 0 +0 0 +0 0 -4 0 -4 Ready for Release 0 +0 0 +0 25 -4 25 -4 Total Software Ready for Testing 3.5.21 oidc-agent 3.3.3 XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200803/#discussion_1","text":"XRootD 5.0.0 is ready for release","title":"Discussion"},{"location":"meetings/2020/TechArea20200803/#osg-investigations-team","text":"Validation document is in \"Draft\" CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. Derek needs help with XCache test failures. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200803/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200810/","text":"OSG Technology Area Meeting, 10 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Doc focus this Thursday starting at 13:30 CDT OSG All Hands Aug 31 - Sep 3 Release of vo-client as soon as possible today because of SLAC VOMS server cert expiration Triage Duty \u00b6 This week: TimT Next week: Diego 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 165 -1 Open 41 +0 In Progress 19 -1 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 AI: Carl - Release IGTF certs today. This includes EL8 builds. AI: Carl - Tracking CC* GPU jobs (in progress). AI: Mat - Update osg-test to handle StashCache and SciTokens integration. AI: Diego - Build scitokens packages for EL8. This includes scitokens-credmon for EL8, which requires Python 3 support. AI: Diego - Run VMU tests for frontier squid. Edgar tested XCache for XRootD 4 in EL8; it needed condor and blahp built for EL8 but it is successfully running. AI: Edgar - Send BrianL an rpm -qa dump to help get a list of all the packages that were touched. Edgar tested XCache 1.5.0 but found some issues; will make a PR. TimT - built HTCondor 8.9 in upcoming for EL8; will make a patch to fix permission issues that cause RPM verification to fail. BLAHP needs to built for upcoming; BrianL will investigate if there are any related tickets. Discussion \u00b6 None this week Support Update \u00b6 TimT: Received a ticket for XRootD Ceph support; will route it to BrianL. Edgar: Wesley Smith at JLab is installing the origin and has some questions about the documentation, specifically about Topology registration. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 8 +1 8 +1 Open 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 11 -1 11 -1 Ready for Testing 0 +0 0 +0 1 +1 1 +1 Ready for Release 0 +0 0 +0 26 +1 26 +1 Total Software Ready for Testing 3.5.22 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data VO Package v107 IGTF 1.107 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 XRootD Validation document is in \"Draft\" (Will go out this week) (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. We have a prototype, who would like to play with it? Proactive site monitoring is progressing nicely. May present at operations meeting this week. Discussion \u00b6 None this week","title":"August 10, 2020"},{"location":"meetings/2020/TechArea20200810/#osg-technology-area-meeting-10-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 10 August 2020"},{"location":"meetings/2020/TechArea20200810/#announcements","text":"Doc focus this Thursday starting at 13:30 CDT OSG All Hands Aug 31 - Sep 3 Release of vo-client as soon as possible today because of SLAC VOMS server cert expiration","title":"Announcements"},{"location":"meetings/2020/TechArea20200810/#triage-duty","text":"This week: TimT Next week: Diego 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200810/#jira","text":"# of tickets \u0394 State 165 -1 Open 41 +0 In Progress 19 -1 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200810/#osg-software-team","text":"Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 AI: Carl - Release IGTF certs today. This includes EL8 builds. AI: Carl - Tracking CC* GPU jobs (in progress). AI: Mat - Update osg-test to handle StashCache and SciTokens integration. AI: Diego - Build scitokens packages for EL8. This includes scitokens-credmon for EL8, which requires Python 3 support. AI: Diego - Run VMU tests for frontier squid. Edgar tested XCache for XRootD 4 in EL8; it needed condor and blahp built for EL8 but it is successfully running. AI: Edgar - Send BrianL an rpm -qa dump to help get a list of all the packages that were touched. Edgar tested XCache 1.5.0 but found some issues; will make a PR. TimT - built HTCondor 8.9 in upcoming for EL8; will make a patch to fix permission issues that cause RPM verification to fail. BLAHP needs to built for upcoming; BrianL will investigate if there are any related tickets.","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200810/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200810/#support-update","text":"TimT: Received a ticket for XRootD Ceph support; will route it to BrianL. Edgar: Wesley Smith at JLab is installing the origin and has some questions about the documentation, specifically about Topology registration.","title":"Support Update"},{"location":"meetings/2020/TechArea20200810/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 8 +1 8 +1 Open 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 11 -1 11 -1 Ready for Testing 0 +0 0 +0 1 +1 1 +1 Ready for Release 0 +0 0 +0 26 +1 26 +1 Total Software Ready for Testing 3.5.22 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data VO Package v107 IGTF 1.107 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200810/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200810/#osg-investigations-team","text":"XRootD Validation document is in \"Draft\" (Will go out this week) (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. We have a prototype, who would like to play with it? Proactive site monitoring is progressing nicely. May present at operations meeting this week.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200810/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200817/","text":"OSG Technology Area Meeting, 17 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, TimT Announcements \u00b6 OSG All Hands Aug 31 - Sep 3 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Mat OOO today Triage Duty \u00b6 This week: Diego Next week: BrianL (???) 8 (+0) open FreshDesk tickets 1 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 169 +4 Open 1 +1 Selected for Dev 27 -14 In Progress 6 +6 Dev Complete 20 +1 Ready for Testing 2 +1 Ready for Release OSG Software Team \u00b6 Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 AI (BrianL): Revisit Carl's plate AI (Edgar): Finish up bookkeeping for EL8 tickets; kick off tests for GlideinWMS 3.6.3 AI (Diego): Kick off builds for the XRootD 4.12.4 RC1 AI (TimT): Build HTCondor 8.8.10 for 3.4; also release GlideinWMS for 3.4 Support Update \u00b6 Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Still investigating. Marco suggested checking with the factory + frontend to see if they've set an aggressive pilot expiration time University of Florida (BrianL): Dynamic WN env functionality broke with a blahp update to 1.18.46. Bockjoo needed to update his configuration from blah.config.rpmnew OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +2 10 +2 Open 0 +0 0 +0 0 +0 0 +0 Selected for Development 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 2 +2 2 +2 Development Complete 0 +0 0 +0 14 +3 14 +3 Ready for Testing 0 +0 0 +0 1 +0 1 +0 Ready for Release 0 +0 0 +0 33 +7 33 +7 Total Software Ready for Testing 3.5.22 HTCondor 8.8.10 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 XRootD Validation document is released: (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. Added cvmfs and check for xrootd functionality. Proactive site monitoring is progressing nicely. Goal: Present this week GPUs for Folding@Home took some debugging with Mats, but as of this morning, seem to be working great. Discussion \u00b6 None this week","title":"August 17, 2020"},{"location":"meetings/2020/TechArea20200817/#osg-technology-area-meeting-17-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, TimT","title":"OSG Technology Area Meeting, 17 August 2020"},{"location":"meetings/2020/TechArea20200817/#announcements","text":"OSG All Hands Aug 31 - Sep 3 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Mat OOO today","title":"Announcements"},{"location":"meetings/2020/TechArea20200817/#triage-duty","text":"This week: Diego Next week: BrianL (???) 8 (+0) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200817/#jira","text":"# of tickets \u0394 State 169 +4 Open 1 +1 Selected for Dev 27 -14 In Progress 6 +6 Dev Complete 20 +1 Ready for Testing 2 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200817/#osg-software-team","text":"Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200817/#discussion","text":"AI (BrianL): Revisit Carl's plate AI (Edgar): Finish up bookkeeping for EL8 tickets; kick off tests for GlideinWMS 3.6.3 AI (Diego): Kick off builds for the XRootD 4.12.4 RC1 AI (TimT): Build HTCondor 8.8.10 for 3.4; also release GlideinWMS for 3.4","title":"Discussion"},{"location":"meetings/2020/TechArea20200817/#support-update","text":"Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Still investigating. Marco suggested checking with the factory + frontend to see if they've set an aggressive pilot expiration time University of Florida (BrianL): Dynamic WN env functionality broke with a blahp update to 1.18.46. Bockjoo needed to update his configuration from blah.config.rpmnew","title":"Support Update"},{"location":"meetings/2020/TechArea20200817/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +2 10 +2 Open 0 +0 0 +0 0 +0 0 +0 Selected for Development 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 2 +2 2 +2 Development Complete 0 +0 0 +0 14 +3 14 +3 Ready for Testing 0 +0 0 +0 1 +0 1 +0 Ready for Release 0 +0 0 +0 33 +7 33 +7 Total Software Ready for Testing 3.5.22 HTCondor 8.8.10 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200817/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200817/#osg-investigations-team","text":"XRootD Validation document is released: (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. Added cvmfs and check for xrootd functionality. Proactive site monitoring is progressing nicely. Goal: Present this week GPUs for Folding@Home took some debugging with Mats, but as of this morning, seem to be working great.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200817/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200824/","text":"OSG Technology Area Meeting, 24 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T Announcements \u00b6 OSG All Hands Aug 31 - Sep 4 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Register ASAP! https://osg-htc.org/all-hands/2020/registration/ Triage Duty \u00b6 This week: BrianL Next week: Carl 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 173 +4 Open 7 +6 Selected for Dev 14 -13 In Progress 7 +1 Dev Complete 32 +12 Ready for Testing 2 +0 Ready for Release OSG Software Team \u00b6 Next doc focus Sep 17 13:30 - 17:30 CDT Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 AI (Diego): Continue to build and scitokens packages for EL8. Contact Jason Patton for software help. AI (Edgar): Build scitokens-issuer for EL8; Derek to merge pull request and make a new release. AI (Edgar): Build osg-gridftp for EL8 since osg-xrootd-standalone is blocked by osg-configure. Support Update \u00b6 JLab (BrianL): Walked the admin through setting up an Origin container. Topology registration is done; Derek will work on CVMFS. JLab will have their own CVMFS endpoint at jlab.opensciencegrid.org, with per-experiment directories. Takeaway: we really need to improve the container so that it's easier to test before Topology registration. Our current policy is to require registration before installing the software; we will revisit the policy. Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Investigating with the HTCondor team. Edgar: Working on giving UC-Irvine a hosted CE on SLATE. Also planning to set up a hosted CE for EXPANSE, but needs to do it without SLATE. Martin Kandes has complained about the install instructions for the worker node client. Brian L would like additional information; for a hosted CE, the site admin shouldn't have to install worker node client. Marco Mambelli: Planning to release glideinWMS 3.6.3; there is a known issue with a missing dependency in the spec file, which will be fixed in the next release. glideinWMS 3.7.1-rc1 has been released. Tim T: Built Bosco tarballs for EL8 per Ops request for Clemson. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +0 10 +0 Open 0 +0 0 +0 2 +2 2 +2 Selected for Development 0 +0 0 +0 1 -5 1 -5 In Progress 0 +0 0 +0 1 -1 1 -1 Development Complete 0 +0 0 +0 16 +2 16 +2 Ready for Testing 0 +0 1 +1 5 +4 5 +4 Ready for Release 0 +0 1 +1 35 +2 36 +3 Total Software Ready for Testing 3.5.22 XCache 1.5.2 xrootd-scitokens 1.2.2 Bunch of EL8 stuff tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.1 Ready for Release oidc-agent 3.3.3 HTCondor 8.8.10 gratia-probe-1.20.14 blahp 1.18.47 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation is ongoing. Proactive site monitoring is progressing nicely. Presented last week at Ops, good feedback! UNL's production cache is 5.0.1, with SciTokens enabled. Discussion \u00b6 Tim T discovered that the HTCondor Campus Factory subpackage is broken; was wondering what it was, and if it was still in use, or required for BOSCO. Derek (original author) said it was a way for campuses to set up a mini-Glidein Factory. bosco_cluster has callouts to it but they can be removed with minimal effort.","title":"August 24, 2020"},{"location":"meetings/2020/TechArea20200824/#osg-technology-area-meeting-24-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 24 August 2020"},{"location":"meetings/2020/TechArea20200824/#announcements","text":"OSG All Hands Aug 31 - Sep 4 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Register ASAP! https://osg-htc.org/all-hands/2020/registration/","title":"Announcements"},{"location":"meetings/2020/TechArea20200824/#triage-duty","text":"This week: BrianL Next week: Carl 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200824/#jira","text":"# of tickets \u0394 State 173 +4 Open 7 +6 Selected for Dev 14 -13 In Progress 7 +1 Dev Complete 32 +12 Ready for Testing 2 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200824/#osg-software-team","text":"Next doc focus Sep 17 13:30 - 17:30 CDT Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200824/#discussion","text":"AI (Diego): Continue to build and scitokens packages for EL8. Contact Jason Patton for software help. AI (Edgar): Build scitokens-issuer for EL8; Derek to merge pull request and make a new release. AI (Edgar): Build osg-gridftp for EL8 since osg-xrootd-standalone is blocked by osg-configure.","title":"Discussion"},{"location":"meetings/2020/TechArea20200824/#support-update","text":"JLab (BrianL): Walked the admin through setting up an Origin container. Topology registration is done; Derek will work on CVMFS. JLab will have their own CVMFS endpoint at jlab.opensciencegrid.org, with per-experiment directories. Takeaway: we really need to improve the container so that it's easier to test before Topology registration. Our current policy is to require registration before installing the software; we will revisit the policy. Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Investigating with the HTCondor team. Edgar: Working on giving UC-Irvine a hosted CE on SLATE. Also planning to set up a hosted CE for EXPANSE, but needs to do it without SLATE. Martin Kandes has complained about the install instructions for the worker node client. Brian L would like additional information; for a hosted CE, the site admin shouldn't have to install worker node client. Marco Mambelli: Planning to release glideinWMS 3.6.3; there is a known issue with a missing dependency in the spec file, which will be fixed in the next release. glideinWMS 3.7.1-rc1 has been released. Tim T: Built Bosco tarballs for EL8 per Ops request for Clemson.","title":"Support Update"},{"location":"meetings/2020/TechArea20200824/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +0 10 +0 Open 0 +0 0 +0 2 +2 2 +2 Selected for Development 0 +0 0 +0 1 -5 1 -5 In Progress 0 +0 0 +0 1 -1 1 -1 Development Complete 0 +0 0 +0 16 +2 16 +2 Ready for Testing 0 +0 1 +1 5 +4 5 +4 Ready for Release 0 +0 1 +1 35 +2 36 +3 Total Software Ready for Testing 3.5.22 XCache 1.5.2 xrootd-scitokens 1.2.2 Bunch of EL8 stuff tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.1 Ready for Release oidc-agent 3.3.3 HTCondor 8.8.10 gratia-probe-1.20.14 blahp 1.18.47 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200824/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200824/#osg-investigations-team","text":"(No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation is ongoing. Proactive site monitoring is progressing nicely. Presented last week at Ops, good feedback! UNL's production cache is 5.0.1, with SciTokens enabled.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200824/#discussion_2","text":"Tim T discovered that the HTCondor Campus Factory subpackage is broken; was wondering what it was, and if it was still in use, or required for BOSCO. Derek (original author) said it was a way for campuses to set up a mini-Glidein Factory. bosco_cluster has callouts to it but they can be removed with minimal effort.","title":"Discussion"},{"location":"meetings/2020/TechArea20200914/","text":"OSG Technology Area Meeting, 14 September 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T Announcements \u00b6 Next week's meeting canceled (HTCondor Week Europe) PATh grant has been awarded! Triage Duty \u00b6 This week: Mat Next week: Diego 8 (+1) open FreshDesk tickets 3 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 166 +2 Open 12 -4 Selected for Dev 14 -1 In Progress 5 +1 Dev Complete 23 +4 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Doc focus Sep 17 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 UCSD team members (Edgar, Diego) will be moving to the GIL project, which is primarily involved in network and software performance testing; they will continue to provide OSG Software effort until the end of October. AI (Diego): Build XRootD 5.0.2 rc1 for upcoming. Build python-scitokens. AI (Edgar): Release vo-client in time for this week's release. Review and merge documentation PR about prescribed xcache locations. Present Data Lake talk at WLCG meeting tomorrow. AI (Mat): Build osg-configure once Python 3 conversion PR is merged. Continue to work on OIDC auth for Topology. Write talks for HTCondor Week Europe. Marco Mambelli: - Working on GWMS 3.7 release candidate and GWMS 3.6.4. - Troubleshooting condor_chirp issue with Marco Mascheroni. Support Update \u00b6 Georgia State (BrianL): investigated Hosted CE SSH issues (in progress) Georgia Tech (BrianL): assisted with their self-deployed SLATE Hosted CE with Lincoln + Judith Swinburne University (BrianL): setting up a new Hosted CE for them via the CHTC Tiger k8s cluster LHCb @ MIT (Derek): Usage is still not showing up. May be related first to EGI portal problems, which caused them to restart it, which caused it to not get the topology information because wrong URL. belle2 @ BNL (Derek): Not showing up as well, may be related to EGI portal and now topology problems. CalTech (Edgar): Working with Justas to help him set up xrootd-multiuser with checksums, but running into a bug in xrootd/xrootd-multiuser that gives the wrong checksums. Running into GWMS problems after upgrading the HTCondor central manager to 8.9; will debug with Marco. CMU (Mat): gfal-ls ticket given to Wei, but waiting on debug information; Mat will ping user. Cesga (Mat): script trying to contact Topology via the old iu.edu address. Mat will help them switch over to the current address. OSG Release Team \u00b6 3.4.55 \u0394 Both \u0394 3.5.24 \u0394 Total \u0394 Status 0 +0 0 +0 11 +1 11 +1 Open 0 +0 0 +0 1 -1 1 -1 Selected for Development 0 +0 0 +0 3 +2 3 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 7 -9 7 -9 Ready for Testing 0 +0 0 -1 1 -4 1 -5 Ready for Release 0 +0 0 -1 24 -11 24 -12 Total Software Ready for Testing 3.5.24 hosted-ce-tools 0.8-2 stashcache-client 6.1.0 XRootD 4.12.4 CCTools 7.1.1 EL8: Frontier Squid 4.12-2.1 EL8: lcmaps 1.6.6 Upcoming XRootD 5.0.1-1.4 (xrootd4 compat packages) Ready for Release 3.5.24 CVMFS 2.7.4 Data VO Package v108 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 CVMFS singularity building is now in production! StashCP Go implementation is ongoing. Discussion \u00b6 Planning to upgrade XCache redirectors to XRootD 5 and change the config to require cache<->redirector commuication to use TLS. This will break XRootD 4 caches; almost all caches have been moved to XRootD 5, except for ItalianGrid. Edgar will get in touch with them.","title":"September 14, 2020"},{"location":"meetings/2020/TechArea20200914/#osg-technology-area-meeting-14-september-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 14 September 2020"},{"location":"meetings/2020/TechArea20200914/#announcements","text":"Next week's meeting canceled (HTCondor Week Europe) PATh grant has been awarded!","title":"Announcements"},{"location":"meetings/2020/TechArea20200914/#triage-duty","text":"This week: Mat Next week: Diego 8 (+1) open FreshDesk tickets 3 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200914/#jira","text":"# of tickets \u0394 State 166 +2 Open 12 -4 Selected for Dev 14 -1 In Progress 5 +1 Dev Complete 23 +4 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200914/#osg-software-team","text":"Doc focus Sep 17 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200914/#discussion","text":"UCSD team members (Edgar, Diego) will be moving to the GIL project, which is primarily involved in network and software performance testing; they will continue to provide OSG Software effort until the end of October. AI (Diego): Build XRootD 5.0.2 rc1 for upcoming. Build python-scitokens. AI (Edgar): Release vo-client in time for this week's release. Review and merge documentation PR about prescribed xcache locations. Present Data Lake talk at WLCG meeting tomorrow. AI (Mat): Build osg-configure once Python 3 conversion PR is merged. Continue to work on OIDC auth for Topology. Write talks for HTCondor Week Europe. Marco Mambelli: - Working on GWMS 3.7 release candidate and GWMS 3.6.4. - Troubleshooting condor_chirp issue with Marco Mascheroni.","title":"Discussion"},{"location":"meetings/2020/TechArea20200914/#support-update","text":"Georgia State (BrianL): investigated Hosted CE SSH issues (in progress) Georgia Tech (BrianL): assisted with their self-deployed SLATE Hosted CE with Lincoln + Judith Swinburne University (BrianL): setting up a new Hosted CE for them via the CHTC Tiger k8s cluster LHCb @ MIT (Derek): Usage is still not showing up. May be related first to EGI portal problems, which caused them to restart it, which caused it to not get the topology information because wrong URL. belle2 @ BNL (Derek): Not showing up as well, may be related to EGI portal and now topology problems. CalTech (Edgar): Working with Justas to help him set up xrootd-multiuser with checksums, but running into a bug in xrootd/xrootd-multiuser that gives the wrong checksums. Running into GWMS problems after upgrading the HTCondor central manager to 8.9; will debug with Marco. CMU (Mat): gfal-ls ticket given to Wei, but waiting on debug information; Mat will ping user. Cesga (Mat): script trying to contact Topology via the old iu.edu address. Mat will help them switch over to the current address.","title":"Support Update"},{"location":"meetings/2020/TechArea20200914/#osg-release-team","text":"3.4.55 \u0394 Both \u0394 3.5.24 \u0394 Total \u0394 Status 0 +0 0 +0 11 +1 11 +1 Open 0 +0 0 +0 1 -1 1 -1 Selected for Development 0 +0 0 +0 3 +2 3 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 7 -9 7 -9 Ready for Testing 0 +0 0 -1 1 -4 1 -5 Ready for Release 0 +0 0 -1 24 -11 24 -12 Total Software Ready for Testing 3.5.24 hosted-ce-tools 0.8-2 stashcache-client 6.1.0 XRootD 4.12.4 CCTools 7.1.1 EL8: Frontier Squid 4.12-2.1 EL8: lcmaps 1.6.6 Upcoming XRootD 5.0.1-1.4 (xrootd4 compat packages) Ready for Release 3.5.24 CVMFS 2.7.4 Data VO Package v108 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200914/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200914/#osg-investigations-team","text":"CVMFS singularity building is now in production! StashCP Go implementation is ongoing.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200914/#discussion_2","text":"Planning to upgrade XCache redirectors to XRootD 5 and change the config to require cache<->redirector commuication to use TLS. This will break XRootD 4 caches; almost all caches have been moved to XRootD 5, except for ItalianGrid. Edgar will get in touch with them.","title":"Discussion"},{"location":"meetings/2020/TechArea20200928/","text":"OSG Technology Area Meeting, 28 September 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Diego, Edgar, Marco Mambelli, Mat, Tim T Announcements \u00b6 None this week. Triage Duty \u00b6 This week: Tim T Carl to send out email for the next rotation. 7 (-1) open FreshDesk tickets 3 (+0) open GGUS tickets JIRA \u00b6 # of tickets \u0394 State 166 +0 Open 15 +3 Selected for Dev 15 +1 In Progress 4 -1 Dev Complete 17 -6 Ready for Testing 6 +5 Ready for Release OSG Software Team \u00b6 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 None. Support Update \u00b6 Edgar: StashCache at PIC upgraded to the upcoming-fresh version but it's broken for them. Edgar is troubleshooting; will reach out to XRootD developers for assistance. The symptom is an SSL permission denied, but the error only shows up in XRootD 5 and goes away when they downgrade. GlideinWMS News \u00b6 Marco Mascheroni testing 3.6.4 in the ITB. (This will be in OSG 3.4 and OSG 3.5.) 3.9 now in osg-contrib (this includes Python 3 support). Continuing work on 3.7; integrating some work from the recent tokens hackathon. OSG Release Team \u00b6 3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 0 +0 10 -1 10 -1 Open 0 +0 0 +0 3 +2 3 +2 Selected for Development 0 +0 0 +0 1 -2 1 -2 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 1 +1 4 -3 5 -2 Ready for Testing 1 +1 0 +0 0 -1 1 +0 Ready for Release 1 +1 1 +1 18 -6 20 -4 Total Software Ready for Testing Both GlideinWMS 3.6.4 3.5.25 blahp 1.18.48 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 Next week we have the stashcp-go presentation. Tackling some GRACC technical debt (RabbitMQ library changed a lot between versions) IRIS-HEP Fellows presentation today Converted perfsonar ingesters over to K8s Much work on perfsonar collector. Now using multi-processing, and a thread pool (DNS lookup are slow!) Consulting on the gratia probe for containers","title":"September 28, 2020"},{"location":"meetings/2020/TechArea20200928/#osg-technology-area-meeting-28-september-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Diego, Edgar, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 28 September 2020"},{"location":"meetings/2020/TechArea20200928/#announcements","text":"None this week.","title":"Announcements"},{"location":"meetings/2020/TechArea20200928/#triage-duty","text":"This week: Tim T Carl to send out email for the next rotation. 7 (-1) open FreshDesk tickets 3 (+0) open GGUS tickets","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200928/#jira","text":"# of tickets \u0394 State 166 +0 Open 15 +3 Selected for Dev 15 +1 In Progress 4 -1 Dev Complete 17 -6 Ready for Testing 6 +5 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200928/#osg-software-team","text":"Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200928/#discussion","text":"None.","title":"Discussion"},{"location":"meetings/2020/TechArea20200928/#support-update","text":"Edgar: StashCache at PIC upgraded to the upcoming-fresh version but it's broken for them. Edgar is troubleshooting; will reach out to XRootD developers for assistance. The symptom is an SSL permission denied, but the error only shows up in XRootD 5 and goes away when they downgrade.","title":"Support Update"},{"location":"meetings/2020/TechArea20200928/#glideinwms-news","text":"Marco Mascheroni testing 3.6.4 in the ITB. (This will be in OSG 3.4 and OSG 3.5.) 3.9 now in osg-contrib (this includes Python 3 support). Continuing work on 3.7; integrating some work from the recent tokens hackathon.","title":"GlideinWMS News"},{"location":"meetings/2020/TechArea20200928/#osg-release-team","text":"3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 0 +0 10 -1 10 -1 Open 0 +0 0 +0 3 +2 3 +2 Selected for Development 0 +0 0 +0 1 -2 1 -2 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 1 +1 4 -3 5 -2 Ready for Testing 1 +1 0 +0 0 -1 1 +0 Ready for Release 1 +1 1 +1 18 -6 20 -4 Total Software Ready for Testing Both GlideinWMS 3.6.4 3.5.25 blahp 1.18.48 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200928/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200928/#osg-investigations-team","text":"Next week we have the stashcp-go presentation. Tackling some GRACC technical debt (RabbitMQ library changed a lot between versions) IRIS-HEP Fellows presentation today Converted perfsonar ingesters over to K8s Much work on perfsonar collector. Now using multi-processing, and a thread pool (DNS lookup are slow!) Consulting on the gratia probe for containers","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201005/","text":"OSG Technology Area Meeting, 5 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 CC spin-up meeting for the 2020 CC recipients later this month -- requests for materials will be high-priority. Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (-3) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 173 +7 Open 15 +0 Selected for Dev 14 -1 In Progress 6 +2 Dev Complete 17 +0 Ready for Testing 6 +0 Ready for Release OSG Software Team \u00b6 Doc focus Oct 22 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 AI (Edgar): merge https://opensciencegrid.atlassian.net/browse/SOFTWARE-4203 Does XRootD 4.12.5 fix issues found with XRootD 4.12.4? No; the error seems to affect TPC in the entire 4.12.X series. For some reason, nightly VMU tests (which test TPC) have not detected the issue. AI (Edgar/Diego): Investigate why VMU tests do not catch this issue. AI (Edgar/Diego): Report problem to XRootD developers as a GitHub issue. Discussion \u00b6 Diego: PR for Python 3 support for SciTokens was merged. AI (Diego): Rebuild XRootD plugins for XRootD 5 (except XRootD-HDFS). AI (Edgar): Build osg-xrootd and x509-scitokens-issuer for EL8, since they are no longer blocked by osg-configure. (This is lower priority than XRootD issues mentioned above.) AI (BrianL): Coordinate improvement of cache federation registration process. AI (Mat): Investigate stale URLs in technology docs. TimT: Encountering build failures for HTCondor on EL8 -- these appear to be random (i.e. rebuilds succeed). HTCondor-CE tests with HTCondor 8.9.9 are brittle and randomly fail to run. BrianL will investigate. GlideinWMS \u00b6 Will release 3.6.5, which includes a fix for a bind-mount issue encountered by Marco Mascheroni. Support Update \u00b6 Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. Edgar: Continuing to debug issues with XRootD 5 in the CNAF StashCache -- maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB. OSG Release Team \u00b6 3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 1 +1 10 +0 11 +1 Open 0 +0 0 +0 4 +1 4 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 -1 4 +0 4 -1 Ready for Testing 1 +0 0 +0 1 +1 2 +1 Ready for Release 1 +0 1 +0 20 +2 22 +2 Total Software Ready for Testing 3.5.25 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.25 blahp 1.18.48 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 StashCP Go presentation planned for next week. Redirectors with TLS turned on test is planned for today. Lets see what breaks! Discussion \u00b6 None this week","title":"October 5, 2020"},{"location":"meetings/2020/TechArea20201005/#osg-technology-area-meeting-5-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 5 October 2020"},{"location":"meetings/2020/TechArea20201005/#announcements","text":"CC spin-up meeting for the 2020 CC recipients later this month -- requests for materials will be high-priority.","title":"Announcements"},{"location":"meetings/2020/TechArea20201005/#triage-duty","text":"This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (-3) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201005/#jira","text":"# of tickets \u0394 State 173 +7 Open 15 +0 Selected for Dev 14 -1 In Progress 6 +2 Dev Complete 17 +0 Ready for Testing 6 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201005/#osg-software-team","text":"Doc focus Oct 22 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 AI (Edgar): merge https://opensciencegrid.atlassian.net/browse/SOFTWARE-4203 Does XRootD 4.12.5 fix issues found with XRootD 4.12.4? No; the error seems to affect TPC in the entire 4.12.X series. For some reason, nightly VMU tests (which test TPC) have not detected the issue. AI (Edgar/Diego): Investigate why VMU tests do not catch this issue. AI (Edgar/Diego): Report problem to XRootD developers as a GitHub issue.","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201005/#discussion","text":"Diego: PR for Python 3 support for SciTokens was merged. AI (Diego): Rebuild XRootD plugins for XRootD 5 (except XRootD-HDFS). AI (Edgar): Build osg-xrootd and x509-scitokens-issuer for EL8, since they are no longer blocked by osg-configure. (This is lower priority than XRootD issues mentioned above.) AI (BrianL): Coordinate improvement of cache federation registration process. AI (Mat): Investigate stale URLs in technology docs. TimT: Encountering build failures for HTCondor on EL8 -- these appear to be random (i.e. rebuilds succeed). HTCondor-CE tests with HTCondor 8.9.9 are brittle and randomly fail to run. BrianL will investigate.","title":"Discussion"},{"location":"meetings/2020/TechArea20201005/#glideinwms","text":"Will release 3.6.5, which includes a fix for a bind-mount issue encountered by Marco Mascheroni.","title":"GlideinWMS"},{"location":"meetings/2020/TechArea20201005/#support-update","text":"Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. Edgar: Continuing to debug issues with XRootD 5 in the CNAF StashCache -- maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB.","title":"Support Update"},{"location":"meetings/2020/TechArea20201005/#osg-release-team","text":"3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 1 +1 10 +0 11 +1 Open 0 +0 0 +0 4 +1 4 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 -1 4 +0 4 -1 Ready for Testing 1 +0 0 +0 1 +1 2 +1 Ready for Release 1 +0 1 +0 20 +2 22 +2 Total Software Ready for Testing 3.5.25 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.25 blahp 1.18.48 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201005/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201005/#osg-investigations-team","text":"StashCP Go presentation planned for next week. Redirectors with TLS turned on test is planned for today. Lets see what breaks!","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201005/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201012/","text":"OSG Technology Area Meeting, 12 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, Mat, Salman Djingueinabaye, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Edgar 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 157 -16 Open 16 +1 Selected for Dev 18 +4 In Progress 12 +12 Dev Complete 17 +0 Ready for Testing 0 +0 Ready for Release StashCP in Go Presentation \u00b6 WIP source ; slides Due to a number of benefits of Golang as opposed to Python, stashcp is being reimplemented in Golang. This is primarily performance (since it's built for concurrency) and ease of installation (since it's a statically linked binary.) Some features that have yet to be implemented are: finding the \"best\" cache stashcp_single Timeline of release is \"weeks, not months.\" Good documentation and well-commented code is a high priority. OSG Software Team \u00b6 Doc focus Oct 22 canceled due to OSG CC* Workshop Oct 22-23 Oct 29 is a good cadidate date for a reschedule. CVMFS + EL6 nightly failures currently under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 OSG-Display (the software) is deployed by a Git checkout that is picked up by an Apache server. John Thiltges is working on moving it to Kubernetes. AI (Carl): Deploy repo generation changes to repo-itb. AI (Diego): Build python-scitokens for EL7 and xrootd 5 and plugins for EL8. AI (Edgar): Debug why XRootD fails to start in EL8 VMU tests. In time crunch to get EXPANSE going. They require hosted CEs and use EL8 head nodes. All the software should be ready. AI (Mat): Implement token auth for topology. AI (Mat): Update the state of WLCG VO proxy support ticket (SOFTWARE-4113). Support Update \u00b6 Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. CNAF (Edgar): Continuing to debug issues with XRootD 5 in the CNAF StashCache \u2013 maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB. OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 -1 9 -1 9 -2 Open 0 +0 0 +0 5 +1 5 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 5 +1 5 +1 Ready for Testing 0 -1 0 +0 0 -1 0 -2 Ready for Release 0 -1 0 -1 20 +0 20 -2 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 StashCP Go presentation! TLS on redirectors is done. No reports of breakage. Elasticsearch on Kubernetes! Discussion \u00b6 None this week","title":"October 12, 2020"},{"location":"meetings/2020/TechArea20201012/#osg-technology-area-meeting-12-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, Mat, Salman Djingueinabaye, TimT","title":"OSG Technology Area Meeting, 12 October 2020"},{"location":"meetings/2020/TechArea20201012/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20201012/#triage-duty","text":"This week: Carl Next week: Edgar 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201012/#jira","text":"# of tickets \u0394 State 157 -16 Open 16 +1 Selected for Dev 18 +4 In Progress 12 +12 Dev Complete 17 +0 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201012/#stashcp-in-go-presentation","text":"WIP source ; slides Due to a number of benefits of Golang as opposed to Python, stashcp is being reimplemented in Golang. This is primarily performance (since it's built for concurrency) and ease of installation (since it's a statically linked binary.) Some features that have yet to be implemented are: finding the \"best\" cache stashcp_single Timeline of release is \"weeks, not months.\" Good documentation and well-commented code is a high priority.","title":"StashCP in Go Presentation"},{"location":"meetings/2020/TechArea20201012/#osg-software-team","text":"Doc focus Oct 22 canceled due to OSG CC* Workshop Oct 22-23 Oct 29 is a good cadidate date for a reschedule. CVMFS + EL6 nightly failures currently under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201012/#discussion","text":"OSG-Display (the software) is deployed by a Git checkout that is picked up by an Apache server. John Thiltges is working on moving it to Kubernetes. AI (Carl): Deploy repo generation changes to repo-itb. AI (Diego): Build python-scitokens for EL7 and xrootd 5 and plugins for EL8. AI (Edgar): Debug why XRootD fails to start in EL8 VMU tests. In time crunch to get EXPANSE going. They require hosted CEs and use EL8 head nodes. All the software should be ready. AI (Mat): Implement token auth for topology. AI (Mat): Update the state of WLCG VO proxy support ticket (SOFTWARE-4113).","title":"Discussion"},{"location":"meetings/2020/TechArea20201012/#support-update","text":"Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. CNAF (Edgar): Continuing to debug issues with XRootD 5 in the CNAF StashCache \u2013 maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB.","title":"Support Update"},{"location":"meetings/2020/TechArea20201012/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 -1 9 -1 9 -2 Open 0 +0 0 +0 5 +1 5 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 5 +1 5 +1 Ready for Testing 0 -1 0 +0 0 -1 0 -2 Ready for Release 0 -1 0 -1 20 +0 20 -2 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201012/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201012/#osg-investigations-team","text":"StashCP Go presentation! TLS on redirectors is done. No reports of breakage. Elasticsearch on Kubernetes!","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201012/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201019/","text":"OSG Technology Area Meeting, 19 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Oct 22-23 Workshop: Supporting Campus Researchers with dHTC and the OSG Triage Duty \u00b6 This week: Edgar Next week: Diego 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 169 +12 Open 15 -1 Selected for Dev 20 +2 In Progress 11 -1 Dev Complete 21 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus Oct 29 1:30pm CVMFS + EL6 nightly failures still under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 There will be upcoming changes to Freshdesk SLAs and policies; exact details to come later. XRootD 4.12.5 release is out. Derek: LIGO dataframe access with SciTokens is at a roadblock because LIGO shares an origin with CMS; LIGO wants TLS enabled but CMS is not ready for it. LIGO will move to their own origin server. AI (Diego): Continue building XRootD 5 plugins for EL8, and updating xrootd-multiuser. AI (Edgar): Push xrootd-standalone and x509-scitokens-issuer over the finish line AI (Mat): Document building xrootd-compat packages; build Ubuntu containers. GlideinWMS: 3.7.1 work continuing. 3.6.5 released recently and has been stable in production. Jeff having trouble restricting disk usage on a site; Marco will debug and seek help from HTCondor developers. Support Update \u00b6 Expanse (Edgar, BrianL): Tracked down some EL8 Bosco incompatibilities. These fixes need to be included in Bosco override files until they're fixed upstream. JLab (Derek): JLab Origin much more stable this week. Continuing to aggressively monitor, but so far so good. OSG Connect (Derek): StashCP issue when the writeback address is a directory and not a file. Curl doesn't give an error message, it just gives a non-zero exit code. So the error from stashcp is cryptic. Will investigate solution. OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! Elasticsearch upgrade upcoming on OSG GRACC coming the end of this month. Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +2 11 +2 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 6 +1 6 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 23 +0 23 +3 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"October 19, 2020"},{"location":"meetings/2020/TechArea20201019/#osg-technology-area-meeting-19-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 19 October 2020"},{"location":"meetings/2020/TechArea20201019/#announcements","text":"Oct 22-23 Workshop: Supporting Campus Researchers with dHTC and the OSG","title":"Announcements"},{"location":"meetings/2020/TechArea20201019/#triage-duty","text":"This week: Edgar Next week: Diego 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201019/#jira","text":"# of tickets \u0394 State 169 +12 Open 15 -1 Selected for Dev 20 +2 In Progress 11 -1 Dev Complete 21 +4 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201019/#osg-software-team","text":"Doc focus Oct 29 1:30pm CVMFS + EL6 nightly failures still under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201019/#discussion","text":"There will be upcoming changes to Freshdesk SLAs and policies; exact details to come later. XRootD 4.12.5 release is out. Derek: LIGO dataframe access with SciTokens is at a roadblock because LIGO shares an origin with CMS; LIGO wants TLS enabled but CMS is not ready for it. LIGO will move to their own origin server. AI (Diego): Continue building XRootD 5 plugins for EL8, and updating xrootd-multiuser. AI (Edgar): Push xrootd-standalone and x509-scitokens-issuer over the finish line AI (Mat): Document building xrootd-compat packages; build Ubuntu containers. GlideinWMS: 3.7.1 work continuing. 3.6.5 released recently and has been stable in production. Jeff having trouble restricting disk usage on a site; Marco will debug and seek help from HTCondor developers.","title":"Discussion"},{"location":"meetings/2020/TechArea20201019/#support-update","text":"Expanse (Edgar, BrianL): Tracked down some EL8 Bosco incompatibilities. These fixes need to be included in Bosco override files until they're fixed upstream. JLab (Derek): JLab Origin much more stable this week. Continuing to aggressively monitor, but so far so good. OSG Connect (Derek): StashCP issue when the writeback address is a directory and not a file. Curl doesn't give an error message, it just gives a non-zero exit code. So the error from stashcp is cryptic. Will investigate solution.","title":"Support Update"},{"location":"meetings/2020/TechArea20201019/#osg-investigations-team","text":"Elasticsearch on Kubernetes! Elasticsearch upgrade upcoming on OSG GRACC coming the end of this month.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201019/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201019/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +2 11 +2 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 6 +1 6 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 23 +0 23 +3 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201019/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201026/","text":"OSG Technology Area Meeting, 26 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Diego, Edgar, Marco Mambell, Marian, Mat, TimT Announcements \u00b6 This is Diego and Edgar's last week on the Software and Release team! Triage Duty \u00b6 This week: Diego Next week: TimT 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 154 -15 Open 16 +1 Selected for Dev 18 -2 In Progress 12 +1 Dev Complete 23 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus this Thursday Oct 29 1:30pm Kubernetes hackathon tomorrow Oct 27 1:00pm CVMFS + EL6 nightly failures due to SELinux issue and newly changed OSG CVMFS config; workaround in place Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 Our VIRGO contact is the VIRGO Computing Coordinator Stefano Bagnasco (bagnasco@to.infn.it). IRIS-HEP Analysis Systems workshop today and tomorrow. AI (Diego): diagnose XRootD 5 on EL8 issues. AI (Edgar): debug why xrootd-multiuser plugin keeps XRootD server from starting. debug why binary used to generate macaroons is core dumping; contact Zach Miller for assistance. AI (Mat): help Mark Coatsworth with EL8/Python3 support for HTCondor-CE. Multiple issues with BOSCO/Hosted-CEs: Job persistence hasn't been implemented for Hosted-CE containers yet, which means restarts kill jobs. This makes testing and config updates somewhat harmful. A potential solution is using a PersistendVolumeClaim but that's not easy on SLATE. Bosco keeps persistent state in /tmp ; Expanse had their submit node set up with DNS round-robin which means state was sometimes there, sometimes not. Edgar added a manual workaround. Support Update \u00b6 Expanse (Edgar, BrianL): CMS user not being set up properly and PATH being overriden: PRs in to fix both JLab (Edgar): Figured out origin port re-use issue: problem with the site config OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! OASIS upgrade last week (supports SSH logins via authorized keys registered in COmanage!). OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2. Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 0 +0 8 +2 8 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +2 25 +2 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"October 26, 2020"},{"location":"meetings/2020/TechArea20201026/#osg-technology-area-meeting-26-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Diego, Edgar, Marco Mambell, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 26 October 2020"},{"location":"meetings/2020/TechArea20201026/#announcements","text":"This is Diego and Edgar's last week on the Software and Release team!","title":"Announcements"},{"location":"meetings/2020/TechArea20201026/#triage-duty","text":"This week: Diego Next week: TimT 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201026/#jira","text":"# of tickets \u0394 State 154 -15 Open 16 +1 Selected for Dev 18 -2 In Progress 12 +1 Dev Complete 23 +2 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201026/#osg-software-team","text":"Doc focus this Thursday Oct 29 1:30pm Kubernetes hackathon tomorrow Oct 27 1:00pm CVMFS + EL6 nightly failures due to SELinux issue and newly changed OSG CVMFS config; workaround in place Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201026/#discussion","text":"Our VIRGO contact is the VIRGO Computing Coordinator Stefano Bagnasco (bagnasco@to.infn.it). IRIS-HEP Analysis Systems workshop today and tomorrow. AI (Diego): diagnose XRootD 5 on EL8 issues. AI (Edgar): debug why xrootd-multiuser plugin keeps XRootD server from starting. debug why binary used to generate macaroons is core dumping; contact Zach Miller for assistance. AI (Mat): help Mark Coatsworth with EL8/Python3 support for HTCondor-CE. Multiple issues with BOSCO/Hosted-CEs: Job persistence hasn't been implemented for Hosted-CE containers yet, which means restarts kill jobs. This makes testing and config updates somewhat harmful. A potential solution is using a PersistendVolumeClaim but that's not easy on SLATE. Bosco keeps persistent state in /tmp ; Expanse had their submit node set up with DNS round-robin which means state was sometimes there, sometimes not. Edgar added a manual workaround.","title":"Discussion"},{"location":"meetings/2020/TechArea20201026/#support-update","text":"Expanse (Edgar, BrianL): CMS user not being set up properly and PATH being overriden: PRs in to fix both JLab (Edgar): Figured out origin port re-use issue: problem with the site config","title":"Support Update"},{"location":"meetings/2020/TechArea20201026/#osg-investigations-team","text":"Elasticsearch on Kubernetes! OASIS upgrade last week (supports SSH logins via authorized keys registered in COmanage!). OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201026/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201026/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 0 +0 8 +2 8 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +2 25 +2 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201026/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201102/","text":"OSG Technology Area Meeting, 2 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marian, Marco Mambelli, TimT Announcements \u00b6 Travis CI has a new pricing model ( https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing ) that affects us: The OSG org has 1000 minutes off the bat and we can apply for OSS minutes All new container builds should be set up using GitHub actions We are discussing consolidating this meeting with 9am Monday morning stand-ups Triage Duty \u00b6 This week: TimT Next week: Mat 7 (-4) open FreshDesk tickets 1 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 137 -14 Open 17 +1 Selected for Dev 21 +3 In Progress 12 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 WN client installs and StashCache tests fail in the release due to EPEL gfal requiring XRootD 5 Workaround: yum install osg-wn-client --enablerepo=osg-upcoming We'll need to build gfal2-plugin-xrootd for OSG 3.5 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 AI (TimT): give BrianL HTCondor yum repo URLs to include in the OSG nightly tests Support Update \u00b6 CMS (Marian, Derek): Running into issues with XRootD 5 and GSI/VOMS authN; perhaps related to an xrootd-lcmaps config issue that John Thiltges ran into FNAL (Derek): CVMFS sync stopped working and they switched to another one and has been resolved JLab (Carl): still waiting on JLab to sort out DNS and firewall issues before we can verify their CE OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! Need to add logstash XRootD 5 on the LIGO origin (Thanks John) xrootd-scitokens requires some work requested from Andy about renaming things to be consistent with XRootD. OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2. Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 -2 3 -2 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 11 +3 11 +3 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +0 25 +0 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 XRootD 4.12.5 osg-flock 1.2-2 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) Upcoming: HTCondor 8.9.9 Upcoming: XRootD 5.0.2 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"November 2, 2020"},{"location":"meetings/2020/TechArea20201102/#osg-technology-area-meeting-2-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marian, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 2 November 2020"},{"location":"meetings/2020/TechArea20201102/#announcements","text":"Travis CI has a new pricing model ( https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing ) that affects us: The OSG org has 1000 minutes off the bat and we can apply for OSS minutes All new container builds should be set up using GitHub actions We are discussing consolidating this meeting with 9am Monday morning stand-ups","title":"Announcements"},{"location":"meetings/2020/TechArea20201102/#triage-duty","text":"This week: TimT Next week: Mat 7 (-4) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201102/#jira","text":"# of tickets \u0394 State 137 -14 Open 17 +1 Selected for Dev 21 +3 In Progress 12 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201102/#osg-software-team","text":"WN client installs and StashCache tests fail in the release due to EPEL gfal requiring XRootD 5 Workaround: yum install osg-wn-client --enablerepo=osg-upcoming We'll need to build gfal2-plugin-xrootd for OSG 3.5 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201102/#discussion","text":"AI (TimT): give BrianL HTCondor yum repo URLs to include in the OSG nightly tests","title":"Discussion"},{"location":"meetings/2020/TechArea20201102/#support-update","text":"CMS (Marian, Derek): Running into issues with XRootD 5 and GSI/VOMS authN; perhaps related to an xrootd-lcmaps config issue that John Thiltges ran into FNAL (Derek): CVMFS sync stopped working and they switched to another one and has been resolved JLab (Carl): still waiting on JLab to sort out DNS and firewall issues before we can verify their CE","title":"Support Update"},{"location":"meetings/2020/TechArea20201102/#osg-investigations-team","text":"Elasticsearch on Kubernetes! Need to add logstash XRootD 5 on the LIGO origin (Thanks John) xrootd-scitokens requires some work requested from Andy about renaming things to be consistent with XRootD. OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201102/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201102/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 -2 3 -2 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 11 +3 11 +3 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +0 25 +0 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 XRootD 4.12.5 osg-flock 1.2-2 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) Upcoming: HTCondor 8.9.9 Upcoming: XRootD 5.0.2 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201102/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201109/","text":"OSG Technology Area Meeting, 9 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 We are discussing consolidating this meeting with 9am Monday morning stand-ups Triage Duty \u00b6 This week: Mat Next week: BrianL 11 (+4) open FreshDesk tickets 1 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 +14 Open 16 +1 Selected for Dev 20 +3 In Progress 14 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 Considering releasing XRootD for EL8 AI (Mat): Finish releasing osg-build into devops-production. AI (Mat): Add additional features to OSG-Configure (see tickets) AI (TimT): Write release policy for OSG 3.6 (high priority -- we want to send it out for review soon) AI (Derek): Assist LIGO. Potential Kubernetes Hackathon tomorrow. Shreyas Bharat may join the hackathon to work on factory items. GlideinWMS 3.7.1 has been released and is in osg-upcoming-development. Support Update \u00b6 Derek: continued assisting AMNH with their hosted CE. Mat: assisting Vlad at IceCube for setting up their StashCache Origin. OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! May not use logstash, more to follow XRootD 5 on the LIGO origin, now on Derek to configure for TLS and do all the ligo things . xrootd-scitokens - round 2. OSG GRACC upgraded: v7.8.2 -> v7.9.2. Investigated possible status sites, best option may be Cachet Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.57 \u0394 Both \u0394 3.5.27 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 7 -4 7 -4 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 -3 22 -3 Total Software Ready for Testing 3.5.27 XRootD 4.12.5 Upcoming: HTCondor 8.9.9 EL8: bunch of stuff (still waiting for HTCondor-CE) xrootd-cmstfc 1.5.2-6 (contrib in upcoming) Ready for Release 3.5.27 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"November 9, 2020"},{"location":"meetings/2020/TechArea20201109/#osg-technology-area-meeting-9-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 9 November 2020"},{"location":"meetings/2020/TechArea20201109/#announcements","text":"We are discussing consolidating this meeting with 9am Monday morning stand-ups","title":"Announcements"},{"location":"meetings/2020/TechArea20201109/#triage-duty","text":"This week: Mat Next week: BrianL 11 (+4) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201109/#jira","text":"# of tickets \u0394 State 146 +14 Open 16 +1 Selected for Dev 20 +3 In Progress 14 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201109/#osg-software-team","text":"Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201109/#discussion","text":"Considering releasing XRootD for EL8 AI (Mat): Finish releasing osg-build into devops-production. AI (Mat): Add additional features to OSG-Configure (see tickets) AI (TimT): Write release policy for OSG 3.6 (high priority -- we want to send it out for review soon) AI (Derek): Assist LIGO. Potential Kubernetes Hackathon tomorrow. Shreyas Bharat may join the hackathon to work on factory items. GlideinWMS 3.7.1 has been released and is in osg-upcoming-development.","title":"Discussion"},{"location":"meetings/2020/TechArea20201109/#support-update","text":"Derek: continued assisting AMNH with their hosted CE. Mat: assisting Vlad at IceCube for setting up their StashCache Origin.","title":"Support Update"},{"location":"meetings/2020/TechArea20201109/#osg-investigations-team","text":"Elasticsearch on Kubernetes! May not use logstash, more to follow XRootD 5 on the LIGO origin, now on Derek to configure for TLS and do all the ligo things . xrootd-scitokens - round 2. OSG GRACC upgraded: v7.8.2 -> v7.9.2. Investigated possible status sites, best option may be Cachet","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201109/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201109/#osg-release-team","text":"3.4.57 \u0394 Both \u0394 3.5.27 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 7 -4 7 -4 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 -3 22 -3 Total Software Ready for Testing 3.5.27 XRootD 4.12.5 Upcoming: HTCondor 8.9.9 EL8: bunch of stuff (still waiting for HTCondor-CE) xrootd-cmstfc 1.5.2-6 (contrib in upcoming) Ready for Release 3.5.27 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201109/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201116/","text":"OSG Technology Area Meeting, 16 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 Tech Area meeting merged into Monday morning 9am CST stand-ups! Please provide any feedback to BrianL BrianL OOO next week, Mat and BrianB to act as back-up Triage Duty \u00b6 This week: BrianL Next week: Carl 4 (-7) open FreshDesk tickets 0 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA Discussion \u00b6 AI (Junheng): work on osg-notify bug-fix AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. GlideinWMS Mat found a GlideinWMS bug when working on Ubuntu support; Marco to review and merge, which should get us further along since the affected script is pulled from the master branch 3.7.1 got promoted to production. Working on merging the changes to the Python 3 version. UCSD factories are both running the 3.7 series. CERN factory still running 3.6 series. 3.7.2 expected to handle missing GSI infrastructure. Support Update \u00b6 IceCube (Mat) - playing whack-a-mole with Stash Origin issues (docs have already been improved as a result). Currently investigating permission issues that are likely in the XRootD configuration layer. OSG Investigations Team \u00b6 BrianB has made quite a bit of progress on the OS pool registry: Almost has an end-to-end proof of concept working in the osgdev namespace on Tiger Put together a development container so that work can be handed off Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 2 +2 2 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 5 -2 5 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 +0 22 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): Build HTCondor 8.8 and 8.9 in OSG & run VMU tests Talk to Horst about testing XRootD 4 Difficult to find to find willing testers for XRootD 4 since XCache servers are all using XRootD 5 on the other hand, non-XCache servers are reluctant to upgrade; talk to Dave Mason for help. Look at EL 6 retirement spreadsheet Move cronjobs from ingwe to moria","title":"November 16, 2020"},{"location":"meetings/2020/TechArea20201116/#osg-technology-area-meeting-16-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 16 November 2020"},{"location":"meetings/2020/TechArea20201116/#announcements","text":"Tech Area meeting merged into Monday morning 9am CST stand-ups! Please provide any feedback to BrianL BrianL OOO next week, Mat and BrianB to act as back-up","title":"Announcements"},{"location":"meetings/2020/TechArea20201116/#triage-duty","text":"This week: BrianL Next week: Carl 4 (-7) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201116/#jira","text":"# of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201116/#osg-software-team","text":"Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201116/#discussion","text":"AI (Junheng): work on osg-notify bug-fix AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. GlideinWMS Mat found a GlideinWMS bug when working on Ubuntu support; Marco to review and merge, which should get us further along since the affected script is pulled from the master branch 3.7.1 got promoted to production. Working on merging the changes to the Python 3 version. UCSD factories are both running the 3.7 series. CERN factory still running 3.6 series. 3.7.2 expected to handle missing GSI infrastructure.","title":"Discussion"},{"location":"meetings/2020/TechArea20201116/#support-update","text":"IceCube (Mat) - playing whack-a-mole with Stash Origin issues (docs have already been improved as a result). Currently investigating permission issues that are likely in the XRootD configuration layer.","title":"Support Update"},{"location":"meetings/2020/TechArea20201116/#osg-investigations-team","text":"BrianB has made quite a bit of progress on the OS pool registry: Almost has an end-to-end proof of concept working in the osgdev namespace on Tiger Put together a development container so that work can be handed off","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201116/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201116/#osg-release-team","text":"3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 2 +2 2 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 5 -2 5 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 +0 22 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201116/#discussion_2","text":"AI (TimT): Build HTCondor 8.8 and 8.9 in OSG & run VMU tests Talk to Horst about testing XRootD 4 Difficult to find to find willing testers for XRootD 4 since XCache servers are all using XRootD 5 on the other hand, non-XCache servers are reluctant to upgrade; talk to Dave Mason for help. Look at EL 6 retirement spreadsheet Move cronjobs from ingwe to moria","title":"Discussion"},{"location":"meetings/2020/TechArea20201123/","text":"OSG Technology Area Meeting, 23 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, Carl, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL out all week; Mat out Wednesday and Friday. (TODO numbers) Triage Duty \u00b6 This week: Carl Next week: Mat 8 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 +5 Open 13 -2 Selected for Dev 23 +1 In Progress 17 +1 Dev Complete 16 -6 Ready for Testing 7 +7 Ready for Release OSG Software Team \u00b6 Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA Discussion \u00b6 AI (Carl): Continue working on Gratia probes. Move cron jobs from ingwe to moria. AI (Junheng): OSG-Notify and packages emailer cronjob close to being merged. AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. Test, finish Ubuntu Submit host and inform Old Dominion University of status. Work on Open Pool Negotiator. Kubernetes documentation for the OSG Worker Node. GlideinWMS: Integrate IDTOKEN fixes for 3.7.2. Update Glidein-in-Vacuum and add it to the main release (instead of having it be a separate project). Currently, frontend user needs to be added to sudoers for token generation; working on a way to remove that requirement. GLOW frontend upgraded to 3.7.1; no major problems found. Fermicloud will shut off all EL6 VMs and remove images; Marco will continue to maintain some Docker/Singularity images (since they are still used by experiments). Support Update \u00b6 GlideinWMS: the factory was using 3.7.0rc9 let to some errors due to compatibility issues with the 3.6 series. OSG Investigations Team \u00b6 Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 1 -1 1 -1 In Progress 0 +0 0 +0 2 +1 2 +1 Development Complete 0 +0 0 +0 5 +0 5 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 24 +2 24 +2 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"November 23, 2020"},{"location":"meetings/2020/TechArea20201123/#osg-technology-area-meeting-23-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, Carl, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 23 November 2020"},{"location":"meetings/2020/TechArea20201123/#announcements","text":"BrianL out all week; Mat out Wednesday and Friday. (TODO numbers)","title":"Announcements"},{"location":"meetings/2020/TechArea20201123/#triage-duty","text":"This week: Carl Next week: Mat 8 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201123/#jira","text":"# of tickets \u0394 State 146 +5 Open 13 -2 Selected for Dev 23 +1 In Progress 17 +1 Dev Complete 16 -6 Ready for Testing 7 +7 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201123/#osg-software-team","text":"Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201123/#discussion","text":"AI (Carl): Continue working on Gratia probes. Move cron jobs from ingwe to moria. AI (Junheng): OSG-Notify and packages emailer cronjob close to being merged. AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. Test, finish Ubuntu Submit host and inform Old Dominion University of status. Work on Open Pool Negotiator. Kubernetes documentation for the OSG Worker Node. GlideinWMS: Integrate IDTOKEN fixes for 3.7.2. Update Glidein-in-Vacuum and add it to the main release (instead of having it be a separate project). Currently, frontend user needs to be added to sudoers for token generation; working on a way to remove that requirement. GLOW frontend upgraded to 3.7.1; no major problems found. Fermicloud will shut off all EL6 VMs and remove images; Marco will continue to maintain some Docker/Singularity images (since they are still used by experiments).","title":"Discussion"},{"location":"meetings/2020/TechArea20201123/#support-update","text":"GlideinWMS: the factory was using 3.7.0rc9 let to some errors due to compatibility issues with the 3.6 series.","title":"Support Update"},{"location":"meetings/2020/TechArea20201123/#osg-investigations-team","text":"","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201123/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201123/#osg-release-team","text":"3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 1 -1 1 -1 In Progress 0 +0 0 +0 2 +1 2 +1 Development Complete 0 +0 0 +0 5 +0 5 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 24 +2 24 +2 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201123/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201130/","text":"OSG Technology Area Meeting, 30 November 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 Second Kubernetes-HEP meetup Dec 1 and 2: https://indico.cern.ch/event/968726/ Triage Duty \u00b6 This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 HTCondor-CE + PBS EPEL testing nightlies job submissions are failing Software base image builds are failing due to \"invalid tag\" (maybe leading space?): https://github.com/opensciencegrid/docker-software-base/runs/1437033352?check_suite_focus=true#step:7:16 Discussion \u00b6 AI (TimT): will investigate HTCondor-CE + PBS EPEL testing failures; may require BLAHP fixes AI (Marco): Contact Mats Rynge for TOKEN support for the ITB FE. AI (Carl): Multi site support for pilot probe GHA for per-commit builds for gratia-probe Support Update \u00b6 None this week OSG Investigations Team \u00b6 No updates Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.28 \u0394 Status 8 -4 Open 3 +0 Selected for Development 2 +1 In Progress 5 +3 Development Complete 5 +0 Ready for Testing 0 +0 Ready for Release 23 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 No release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"November 30, 2020"},{"location":"meetings/2020/TechArea20201130/#osg-technology-area-meeting-30-november-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 30 November 2020"},{"location":"meetings/2020/TechArea20201130/#announcements","text":"Second Kubernetes-HEP meetup Dec 1 and 2: https://indico.cern.ch/event/968726/","title":"Announcements"},{"location":"meetings/2020/TechArea20201130/#triage-duty","text":"This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201130/#jira","text":"# of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201130/#osg-software-team","text":"HTCondor-CE + PBS EPEL testing nightlies job submissions are failing Software base image builds are failing due to \"invalid tag\" (maybe leading space?): https://github.com/opensciencegrid/docker-software-base/runs/1437033352?check_suite_focus=true#step:7:16","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201130/#discussion","text":"AI (TimT): will investigate HTCondor-CE + PBS EPEL testing failures; may require BLAHP fixes AI (Marco): Contact Mats Rynge for TOKEN support for the ITB FE. AI (Carl): Multi site support for pilot probe GHA for per-commit builds for gratia-probe","title":"Discussion"},{"location":"meetings/2020/TechArea20201130/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2020/TechArea20201130/#osg-investigations-team","text":"No updates","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201130/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201130/#osg-release-team","text":"3.5.28 \u0394 Status 8 -4 Open 3 +0 Selected for Development 2 +1 In Progress 5 +3 Development Complete 5 +0 Ready for Testing 0 +0 Ready for Release 23 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201130/#discussion_2","text":"No release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"Discussion"},{"location":"meetings/2020/TechArea20201207/","text":"OSG Technology Area Meeting, 7 December 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Tim Next week: BrianL (?) 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 144 +0 Open 12 -1 Selected for Dev 26 +2 In Progress 18 -1 Dev Complete 22 +6 Ready for Testing 7 +7 Ready for Release OSG Software Team \u00b6 EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 Marco: GWMS 3.7.2 released, includes bugfixes for IDTOKEN support; in upcoming-testing.AI (Mat): Submit bug report for XRootD 5.1.0rc1 problem detected in VMU tests. AI (Mat): Mail GridCF list about Travis CI's policy changes. AI (Mat): Ask Marco Mascheroni if he's happy with the new Pilot sections for OSG Configure. AI (Mat): Continue work on OSG flocking negotiator. AI (BrianL): Investigate webapp frameworks and EL 8 compatibility for HTCondor CE View. AI (Junheng): Investigate registry logout error. AI (TimT): Add PowerPC support to EPEL HTCondor packages. VPN access now required to log in to Fermicloud head node (fcluigpvm01.fnal.gov). 2FA required to access Fermi VPN. Steve Timm's suggested solution is to create a (persistent) VM for creating other VMs if that's not possible. Marco will send instructions on how to get access to Fermi VPN. Support Update \u00b6 IceCube (Mat, Derek): Stash Origin now appears to work after creating dummy SciTokens information in Topology. UCL stash origin needed the same fix but needs additional debugging; Derek is providing assistance. JLab (BrianL): blahp status queries time out trying to populate the Slurm job status cache. Opened a ticket with the the HTCondor team: https://opensciencegrid.atlassian.net/browse/HTCONDOR-104 OSG Investigations Team \u00b6 No updates Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.28 \u0394 Status 7 -1 Open 2 -1 Selected for Development 4 +2 In Progress 5 +0 Development Complete 9 +4 Ready for Testing 0 +0 Ready for Release 27 +4 Total Software Ready for Testing 3.5.28 HTCondor 8.8.12 Upcoming: HTCondor 8.9.10 hosted-ce-tools 0.9 htgettoken 1.0 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Containers opensciencegrid/atlas-xcache:fresh opensciencegrid/cms-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI(TimT): promote osg-build to devops Release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"December 7, 2020"},{"location":"meetings/2020/TechArea20201207/#osg-technology-area-meeting-7-december-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 7 December 2020"},{"location":"meetings/2020/TechArea20201207/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20201207/#triage-duty","text":"This week: Tim Next week: BrianL (?) 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201207/#jira","text":"# of tickets \u0394 State 144 +0 Open 12 -1 Selected for Dev 26 +2 In Progress 18 -1 Dev Complete 22 +6 Ready for Testing 7 +7 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201207/#osg-software-team","text":"EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201207/#discussion","text":"Marco: GWMS 3.7.2 released, includes bugfixes for IDTOKEN support; in upcoming-testing.AI (Mat): Submit bug report for XRootD 5.1.0rc1 problem detected in VMU tests. AI (Mat): Mail GridCF list about Travis CI's policy changes. AI (Mat): Ask Marco Mascheroni if he's happy with the new Pilot sections for OSG Configure. AI (Mat): Continue work on OSG flocking negotiator. AI (BrianL): Investigate webapp frameworks and EL 8 compatibility for HTCondor CE View. AI (Junheng): Investigate registry logout error. AI (TimT): Add PowerPC support to EPEL HTCondor packages. VPN access now required to log in to Fermicloud head node (fcluigpvm01.fnal.gov). 2FA required to access Fermi VPN. Steve Timm's suggested solution is to create a (persistent) VM for creating other VMs if that's not possible. Marco will send instructions on how to get access to Fermi VPN.","title":"Discussion"},{"location":"meetings/2020/TechArea20201207/#support-update","text":"IceCube (Mat, Derek): Stash Origin now appears to work after creating dummy SciTokens information in Topology. UCL stash origin needed the same fix but needs additional debugging; Derek is providing assistance. JLab (BrianL): blahp status queries time out trying to populate the Slurm job status cache. Opened a ticket with the the HTCondor team: https://opensciencegrid.atlassian.net/browse/HTCONDOR-104","title":"Support Update"},{"location":"meetings/2020/TechArea20201207/#osg-investigations-team","text":"No updates","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201207/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201207/#osg-release-team","text":"3.5.28 \u0394 Status 7 -1 Open 2 -1 Selected for Development 4 +2 In Progress 5 +0 Development Complete 9 +4 Ready for Testing 0 +0 Ready for Release 27 +4 Total Software Ready for Testing 3.5.28 HTCondor 8.8.12 Upcoming: HTCondor 8.9.10 hosted-ce-tools 0.9 htgettoken 1.0 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Containers opensciencegrid/atlas-xcache:fresh opensciencegrid/cms-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201207/#discussion_2","text":"AI(TimT): promote osg-build to devops Release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"Discussion"},{"location":"meetings/2020/TechArea20201214/","text":"OSG Technology Area Meeting, 14 December 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Junheng, Marco Mambelli, Marian, Mat, Tim C, Tim T Announcements \u00b6 Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts Triage Duty \u00b6 This week: Carl Next week: BrianL 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 145 +1 Open 12 +0 Selected for Dev 25 -1 In Progress 16 -2 Dev Complete 17 -5 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 AI (Carl): New IGTF CA release; update XRootD to 4.12.6. AI (Carl): Investigate bug in generating the CA certs website (lower priority since we can fix it manually) AI (Junheng): Fix location for registry PR; apply changes from review of 'outdated packages' Marco: Working on adding GitHub Actions and plans to use artifacts instead of caches since the former is longer lived AI (Mat): Ensure GridCF can make a GCT release AI (TimT): Prepare for new CA release. AI (TimT): Automate BOSCO and tarball updates; create tarballs for PPC architecture.Announcements: Support Update \u00b6 CMS (Marian): European CMS still mostly on XRootD 4 due to AAA dependency; still discussing migration plans. Miron (Carl): Continue investigating issues with Compute Canada sites erroneously showing up in the CC* dashboard UCL (Mat): Help UCL test authenticated stash origin. Discuss with Derek and Brian B about what kind of authentication is desired. OSG Investigations Team \u00b6 Focus on migrating more GRACC services to Tiger Establish documentation for the GRACC rolling update and fresh install Added and deployed SciToken helper support to OASIS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 10 +3 Open 2 +0 Selected for Development 5 +1 In Progress 5 +0 Development Complete 4 -5 Ready for Testing 0 +0 Ready for Release 26 -1 Total Software Ready for Testing 3.5.29 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data IGTF 1.108 Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"December 14, 2020"},{"location":"meetings/2020/TechArea20201214/#osg-technology-area-meeting-14-december-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Junheng, Marco Mambelli, Marian, Mat, Tim C, Tim T","title":"OSG Technology Area Meeting, 14 December 2020"},{"location":"meetings/2020/TechArea20201214/#announcements","text":"Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts","title":"Announcements"},{"location":"meetings/2020/TechArea20201214/#triage-duty","text":"This week: Carl Next week: BrianL 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201214/#jira","text":"# of tickets \u0394 State 145 +1 Open 12 +0 Selected for Dev 25 -1 In Progress 16 -2 Dev Complete 17 -5 Ready for Testing 7 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201214/#osg-software-team","text":"EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201214/#discussion","text":"AI (Carl): New IGTF CA release; update XRootD to 4.12.6. AI (Carl): Investigate bug in generating the CA certs website (lower priority since we can fix it manually) AI (Junheng): Fix location for registry PR; apply changes from review of 'outdated packages' Marco: Working on adding GitHub Actions and plans to use artifacts instead of caches since the former is longer lived AI (Mat): Ensure GridCF can make a GCT release AI (TimT): Prepare for new CA release. AI (TimT): Automate BOSCO and tarball updates; create tarballs for PPC architecture.Announcements:","title":"Discussion"},{"location":"meetings/2020/TechArea20201214/#support-update","text":"CMS (Marian): European CMS still mostly on XRootD 4 due to AAA dependency; still discussing migration plans. Miron (Carl): Continue investigating issues with Compute Canada sites erroneously showing up in the CC* dashboard UCL (Mat): Help UCL test authenticated stash origin. Discuss with Derek and Brian B about what kind of authentication is desired.","title":"Support Update"},{"location":"meetings/2020/TechArea20201214/#osg-investigations-team","text":"Focus on migrating more GRACC services to Tiger Establish documentation for the GRACC rolling update and fresh install Added and deployed SciToken helper support to OASIS","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201214/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201214/#osg-release-team","text":"3.5.29 \u0394 Status 10 +3 Open 2 +0 Selected for Development 5 +1 In Progress 5 +0 Development Complete 4 -5 Ready for Testing 0 +0 Ready for Release 26 -1 Total Software Ready for Testing 3.5.29 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data IGTF 1.108 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201214/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201221/","text":"OSG Technology Area Meeting, 21 December 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Carl, Irene, Junheng, Marco, Marian, TimT Announcements \u00b6 Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts Cancelling next week's meeting, to resume on Jan 4 Triage Duty \u00b6 This week: BrianL Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 133 -12 Open 12 +0 Selected for Dev 31 +6 In Progress 17 +1 Dev Complete 18 +1 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 AI (BrianL): Move new site onboarding engagement Freshdesk tickets to the Operations group Support Update \u00b6 IceCube (BrianL): completing request to require Singularity for IceCube pilots; continuing a discussion with David to see how we should manage the shared IceCube/GLOW pilots MIT (BrianL): troubleshooting GPU jobs not matching, turned out to be due to an old version of HTCondor OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January XCache(s): deployed new Wisconsin cache to osg-config repo XRootD data transfer monitor close to complete (testing and validation) GRACC (continued progress): migrating more GRACC services to Tiger documentation for the GRACC rolling update and fresh install Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 4 +6 Open 1 -1 Selected for Development 6 +1 In Progress 5 +0 Development Complete 4 +0 Ready for Testing 0 +0 Ready for Release 20 -6 Total Software Ready for Testing 3.5.29 EL8: various things, needs review Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"December 21, 2020"},{"location":"meetings/2020/TechArea20201221/#osg-technology-area-meeting-21-december-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Carl, Irene, Junheng, Marco, Marian, TimT","title":"OSG Technology Area Meeting, 21 December 2020"},{"location":"meetings/2020/TechArea20201221/#announcements","text":"Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts Cancelling next week's meeting, to resume on Jan 4","title":"Announcements"},{"location":"meetings/2020/TechArea20201221/#triage-duty","text":"This week: BrianL Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201221/#jira","text":"# of tickets \u0394 State 133 -12 Open 12 +0 Selected for Dev 31 +6 In Progress 17 +1 Dev Complete 18 +1 Ready for Testing 7 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201221/#osg-software-team","text":"Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201221/#discussion","text":"AI (BrianL): Move new site onboarding engagement Freshdesk tickets to the Operations group","title":"Discussion"},{"location":"meetings/2020/TechArea20201221/#support-update","text":"IceCube (BrianL): completing request to require Singularity for IceCube pilots; continuing a discussion with David to see how we should manage the shared IceCube/GLOW pilots MIT (BrianL): troubleshooting GPU jobs not matching, turned out to be due to an old version of HTCondor","title":"Support Update"},{"location":"meetings/2020/TechArea20201221/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January XCache(s): deployed new Wisconsin cache to osg-config repo XRootD data transfer monitor close to complete (testing and validation) GRACC (continued progress): migrating more GRACC services to Tiger documentation for the GRACC rolling update and fresh install","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201221/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201221/#osg-release-team","text":"3.5.29 \u0394 Status 4 +6 Open 1 -1 Selected for Development 6 +1 In Progress 5 +0 Development Complete 4 +0 Ready for Testing 0 +0 Ready for Release 20 -6 Total Software Ready for Testing 3.5.29 EL8: various things, needs review Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201221/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210104/","text":"OSG Technology Area Meeting, 4 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Derek, Marian, Mat, Tim T Announcements \u00b6 Moving this meeting to Tuesdays after standup starting next week (Jan 12) Triage Duty \u00b6 This week: BrianL Next week: Mat 12 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Switching to a rolling releases within a release series Separate upcoming repositories for 3.5 and 3.6 Docker tags switching to release/testing, tracking the RPM repos Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 AI (Carl): test partial records for Condor Gratia probe AI (Carl): GHA for per-commit builds for Gratia probes Support Update \u00b6 None this week OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. Will catch up on status at later standup. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Next rolling update date? APEL Reporting - Should we update to the new AMS. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 6 +2 Open 0 -1 Selected for Development 6 +0 In Progress 5 +0 Development Complete 5 +1 Ready for Testing 0 +0 Ready for Release 22 +2 Total Software Ready for Testing 3.5.29 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 4, 2021"},{"location":"meetings/2021/TechArea20210104/#osg-technology-area-meeting-4-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Derek, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 4 January 2021"},{"location":"meetings/2021/TechArea20210104/#announcements","text":"Moving this meeting to Tuesdays after standup starting next week (Jan 12)","title":"Announcements"},{"location":"meetings/2021/TechArea20210104/#triage-duty","text":"This week: BrianL Next week: Mat 12 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210104/#jira","text":"# of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210104/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Switching to a rolling releases within a release series Separate upcoming repositories for 3.5 and 3.6 Docker tags switching to release/testing, tracking the RPM repos Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210104/#discussion","text":"AI (Carl): test partial records for Condor Gratia probe AI (Carl): GHA for per-commit builds for Gratia probes","title":"Discussion"},{"location":"meetings/2021/TechArea20210104/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210104/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. Will catch up on status at later standup. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Next rolling update date? APEL Reporting - Should we update to the new AMS.","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210104/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210104/#osg-release-team","text":"3.5.29 \u0394 Status 6 +2 Open 0 -1 Selected for Development 6 +0 In Progress 5 +0 Development Complete 5 +1 Ready for Testing 0 +0 Ready for Release 22 +2 Total Software Ready for Testing 3.5.29 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210104/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210112/","text":"OSG Technology Area Meeting, 12 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 Kubernetes hackathon today UCSD, UNL, UW-Madison all OOO for MLK day next Monday Triage Duty \u00b6 Freshdesk priority increased for Software team This week: Mat Next week: Carl 12 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI TimT/BrianL: Release/container policy docs Koji infrastructure setup tasks TimT noticed XRootD TPC test failures in the nightlies: Edgar added a test for multi-stream TPC that is known to be an issue and we're waiting on an upstream fix Discussion \u00b6 Marco: Testing Python 3 version of GWMS 3.9.1 (rc3); also making the periodic setup script working under Singularity. Had some difficulty splitting out HTTPD parts into a separate RPM, but fixed now. Dennis working on contacting schedds with SciTokens. Support Update \u00b6 IceCube (BrianL): having authentication/certs issues with the CHTC GWMS pool; suspecting old versions of EL6/OSG/Condor. NDSU (BrianL): will be contributing their resources via a private cloud (Lancium) and a custom scheduler; BrianL helping with registration details, and we Carl verified that we're seeing accounting records from them in Kibana. UCSD (Carl): Assist HPC cluster admins with Gratia probe issues OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 5 -1 Open 0 +0 Selected for Development 5 -1 In Progress 3 -2 Development Complete 11 +6 Ready for Testing 0 +0 Ready for Release 24 +2 Total Software Ready for Testing 3.5.29 htgettoken 1.1 osg-configure 3.11.0 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 12, 2021"},{"location":"meetings/2021/TechArea20210112/#osg-technology-area-meeting-12-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 12 January 2021"},{"location":"meetings/2021/TechArea20210112/#announcements","text":"Kubernetes hackathon today UCSD, UNL, UW-Madison all OOO for MLK day next Monday","title":"Announcements"},{"location":"meetings/2021/TechArea20210112/#triage-duty","text":"Freshdesk priority increased for Software team This week: Mat Next week: Carl 12 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210112/#jira","text":"# of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210112/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI TimT/BrianL: Release/container policy docs Koji infrastructure setup tasks TimT noticed XRootD TPC test failures in the nightlies: Edgar added a test for multi-stream TPC that is known to be an issue and we're waiting on an upstream fix","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210112/#discussion","text":"Marco: Testing Python 3 version of GWMS 3.9.1 (rc3); also making the periodic setup script working under Singularity. Had some difficulty splitting out HTTPD parts into a separate RPM, but fixed now. Dennis working on contacting schedds with SciTokens.","title":"Discussion"},{"location":"meetings/2021/TechArea20210112/#support-update","text":"IceCube (BrianL): having authentication/certs issues with the CHTC GWMS pool; suspecting old versions of EL6/OSG/Condor. NDSU (BrianL): will be contributing their resources via a private cloud (Lancium) and a custom scheduler; BrianL helping with registration details, and we Carl verified that we're seeing accounting records from them in Kibana. UCSD (Carl): Assist HPC cluster admins with Gratia probe issues","title":"Support Update"},{"location":"meetings/2021/TechArea20210112/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210112/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210112/#osg-release-team","text":"3.5.29 \u0394 Status 5 -1 Open 0 +0 Selected for Development 5 -1 In Progress 3 -2 Development Complete 11 +6 Ready for Testing 0 +0 Ready for Release 24 +2 Total Software Ready for Testing 3.5.29 htgettoken 1.1 osg-configure 3.11.0 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210112/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210119/","text":"OSG Technology Area Meeting, 19 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Marian, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 10 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 133 -2 Open 17 +2 Selected for Dev 30 +1 In Progress 16 -3 Dev Complete 29 +4 Ready for Testing 8 +1 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT/BrianL): Release/container policy docs AI (Mat): Add support to osg-build for 3.5-upcoming AI (Carl): Set up 3.6 and 3.6-upcoming SVN branches; begin putting together 3.6 Koji tags and repos AI (Mat): Review Derek's multiuser PR AI (Carl): XRootD 5.1.0 RC5 is ready to be built and tested OSG and GLOW VO certificates expire on Feb 23 Discussion \u00b6 AI (Brian): IGTF has a new release Marco was wondering about the status of GlideinWMS 3.7.2: external testing has passed and it is ready to be released Support Update \u00b6 None this week OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 5 +0 Open 1 +1 Selected for Development 7 +2 In Progress 1 -1 Development Complete 11 +6 Ready for Testing 1 +1 Ready for Release 32 +8 Total Software Ready for Testing 3.5.29 Upcoming: HTCondor 8.9.11 htgettoken 1.1 osg-configure 3.11.0 Ready for Release 3.5.29 GlideinWMS 3.7.2 (EL7 Only) Data IGTF 1.109 Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 19, 2021"},{"location":"meetings/2021/TechArea20210119/#osg-technology-area-meeting-19-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Marian, TimT","title":"OSG Technology Area Meeting, 19 January 2021"},{"location":"meetings/2021/TechArea20210119/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210119/#triage-duty","text":"This week: Carl Next week: Mat 10 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210119/#jira","text":"# of tickets \u0394 State 133 -2 Open 17 +2 Selected for Dev 30 +1 In Progress 16 -3 Dev Complete 29 +4 Ready for Testing 8 +1 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210119/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT/BrianL): Release/container policy docs AI (Mat): Add support to osg-build for 3.5-upcoming AI (Carl): Set up 3.6 and 3.6-upcoming SVN branches; begin putting together 3.6 Koji tags and repos AI (Mat): Review Derek's multiuser PR AI (Carl): XRootD 5.1.0 RC5 is ready to be built and tested OSG and GLOW VO certificates expire on Feb 23","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210119/#discussion","text":"AI (Brian): IGTF has a new release Marco was wondering about the status of GlideinWMS 3.7.2: external testing has passed and it is ready to be released","title":"Discussion"},{"location":"meetings/2021/TechArea20210119/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210119/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210119/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210119/#osg-release-team","text":"3.5.29 \u0394 Status 5 +0 Open 1 +1 Selected for Development 7 +2 In Progress 1 -1 Development Complete 11 +6 Ready for Testing 1 +1 Ready for Release 32 +8 Total Software Ready for Testing 3.5.29 Upcoming: HTCondor 8.9.11 htgettoken 1.1 osg-configure 3.11.0 Ready for Release 3.5.29 GlideinWMS 3.7.2 (EL7 Only) Data IGTF 1.109 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210119/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210126/","text":"OSG Technology Area Meeting, 26 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 4 (-6) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 134 +1 Open 15 -2 Selected for Dev 30 +0 In Progress 21 +5 Dev Complete 21 -8 Ready for Testing 8 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Rolling release policy doc AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming OSG 3.5.30 AI (Carl): Add missing LE root cert (SOFTWARE-4436) AI (Mat): Review Derek's multiuser PR ( https://github.com/opensciencegrid/xrootd-multiuser/pull/17 ) AI (Carl): Release gratia-probe (SOFTWARE-4348) AI (Carl): Uppdate SciTokens library to 1.3.1 (SOFTWARE-4439) OSG and GLOW VO certificates expire on Feb 23 Discussion \u00b6 AI (Brian): Debug crashes in new Python 3 version of HTCondor-CE AI (Brian): Update XCache configuration to work with XRootD 5.1 Marco is testing a full GWMS system without X.509 Support Update \u00b6 Carl: Gratia Probe issues noticed by Marty Kandes (fixed) Marco: GlideinWMS issues brought up by user support OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.30 \u0394 Status 8 +3 Open 2 +1 Selected for Development 10 +3 In Progress 4 +3 Development Complete 6 -5 Ready for Testing 1 +0 Ready for Release 31 +5 Total Software Ready for Testing 3.5.30 Upcoming: HTCondor 8.9.11 Ready for Release 3.5.30 XRootD 4.12.6 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 26, 2021"},{"location":"meetings/2021/TechArea20210126/#osg-technology-area-meeting-26-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 26 January 2021"},{"location":"meetings/2021/TechArea20210126/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210126/#triage-duty","text":"This week: Mat Next week: TimT 4 (-6) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210126/#jira","text":"# of tickets \u0394 State 134 +1 Open 15 -2 Selected for Dev 30 +0 In Progress 21 +5 Dev Complete 21 -8 Ready for Testing 8 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210126/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Rolling release policy doc AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming OSG 3.5.30 AI (Carl): Add missing LE root cert (SOFTWARE-4436) AI (Mat): Review Derek's multiuser PR ( https://github.com/opensciencegrid/xrootd-multiuser/pull/17 ) AI (Carl): Release gratia-probe (SOFTWARE-4348) AI (Carl): Uppdate SciTokens library to 1.3.1 (SOFTWARE-4439) OSG and GLOW VO certificates expire on Feb 23","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210126/#discussion","text":"AI (Brian): Debug crashes in new Python 3 version of HTCondor-CE AI (Brian): Update XCache configuration to work with XRootD 5.1 Marco is testing a full GWMS system without X.509","title":"Discussion"},{"location":"meetings/2021/TechArea20210126/#support-update","text":"Carl: Gratia Probe issues noticed by Marty Kandes (fixed) Marco: GlideinWMS issues brought up by user support","title":"Support Update"},{"location":"meetings/2021/TechArea20210126/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210126/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210126/#osg-release-team","text":"3.5.30 \u0394 Status 8 +3 Open 2 +1 Selected for Development 10 +3 In Progress 4 +3 Development Complete 6 -5 Ready for Testing 1 +0 Ready for Release 31 +5 Total Software Ready for Testing 3.5.30 Upcoming: HTCondor 8.9.11 Ready for Release 3.5.30 XRootD 4.12.6 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210126/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210202/","text":"OSG Technology Area Meeting, 2 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Tim T Announcements \u00b6 dHTC campus workshop Feb 8-9 OSG All Hands March 1-5 Triage Duty \u00b6 This week: TimT Next week: ??? 5 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 130 -1 Open 15 +0 Selected for Dev 32 +2 In Progress 13 -8 Dev Complete 37 +16 Ready for Testing 8 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming/3.6 AI (Mat): Token issuer packaging Release-specific devops tags voted unnecessary Time to start building! Spreadsheet incoming Still need to add token tests Dev work still needed for gratia-probe, osg-configure, and HTCondor-CE OSG 3.5.31 AI (Carl): Convert SGE Gratia probe to be Python 2/3 compatible AI (Carl): Fix repo-update-cadist link generation bug. OSG and GLOW VO certificates expire on Feb 23 AI (Mat): Help UW infrastructure team with the renewal process. Discussion \u00b6 Marco attending the CVMFS workshop; gave a presentation on cvmfs-exec yesterday. Carl will shadow Marian during the GRACC upgrade. Support Update \u00b6 Brian L: Call with Villanova about setting up a submit node dedicated to OSG. Marco: Adding a fix to the Singularity wrapper that was requested by Mats Rynge. Mat: Debugging LCMAPS for UFlorida. OSG DevOps \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: In production on tiger. Let us know if you see problems! GRACC (continued progress): GRACC Request is on tiger now. migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.31 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 -6 In Progress 2 -2 Development Complete 18 +12 Ready for Testing 5 +4 Ready for Release 39 +8 Total Software Ready for Testing 3.5.31 gratia-probe 1.22.3 osg-flock 1.3 scitokens Python library 1.3.1 Ready for Release 3.5.31 CVMFS 2.8.0 osg-release 3.5-5 XRootD 4.12.6 lcmaps for EL8 Data osg-ca-certs 1.94 Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"February 2, 2021"},{"location":"meetings/2021/TechArea20210202/#osg-technology-area-meeting-2-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Tim T","title":"OSG Technology Area Meeting, 2 February 2021"},{"location":"meetings/2021/TechArea20210202/#announcements","text":"dHTC campus workshop Feb 8-9 OSG All Hands March 1-5","title":"Announcements"},{"location":"meetings/2021/TechArea20210202/#triage-duty","text":"This week: TimT Next week: ??? 5 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210202/#jira","text":"# of tickets \u0394 State 130 -1 Open 15 +0 Selected for Dev 32 +2 In Progress 13 -8 Dev Complete 37 +16 Ready for Testing 8 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210202/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming/3.6 AI (Mat): Token issuer packaging Release-specific devops tags voted unnecessary Time to start building! Spreadsheet incoming Still need to add token tests Dev work still needed for gratia-probe, osg-configure, and HTCondor-CE OSG 3.5.31 AI (Carl): Convert SGE Gratia probe to be Python 2/3 compatible AI (Carl): Fix repo-update-cadist link generation bug. OSG and GLOW VO certificates expire on Feb 23 AI (Mat): Help UW infrastructure team with the renewal process.","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210202/#discussion","text":"Marco attending the CVMFS workshop; gave a presentation on cvmfs-exec yesterday. Carl will shadow Marian during the GRACC upgrade.","title":"Discussion"},{"location":"meetings/2021/TechArea20210202/#support-update","text":"Brian L: Call with Villanova about setting up a submit node dedicated to OSG. Marco: Adding a fix to the Singularity wrapper that was requested by Mats Rynge. Mat: Debugging LCMAPS for UFlorida.","title":"Support Update"},{"location":"meetings/2021/TechArea20210202/#osg-devops","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: In production on tiger. Let us know if you see problems! GRACC (continued progress): GRACC Request is on tiger now. migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210202/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210202/#osg-release-team","text":"3.5.31 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 -6 In Progress 2 -2 Development Complete 18 +12 Ready for Testing 5 +4 Ready for Release 39 +8 Total Software Ready for Testing 3.5.31 gratia-probe 1.22.3 osg-flock 1.3 scitokens Python library 1.3.1 Ready for Release 3.5.31 CVMFS 2.8.0 osg-release 3.5-5 XRootD 4.12.6 lcmaps for EL8 Data osg-ca-certs 1.94 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210202/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210209/","text":"OSG Technology Area Meeting, 9 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 dHTC campus workshop today! OSG All Hands March 1-5 Mat, BrianL out this Friday Triage Duty \u00b6 This week: Carl Next week: BrianL 3 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 138 +8 Open 12 -3 Selected for Dev 34 +2 In Progress 15 +2 Dev Complete 34 -3 Ready for Testing 1 -7 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Carl, Mat): Make upcoming \u2190\u2192 3.5-upcoming switch (tomorrow 2/10) OSG 3.5.32 AI (Mat): Token issuer packaging AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25 Discussion \u00b6 Doc focus will concentrate on 3.6 documentation; those who can make it should use the whole day GlideinWMS 3.9.1 will be released later today Support Update \u00b6 Carl: Support ticket for batch vs payload core hour discrepancy (needs further investigation and will be tracked in JIRA instead) Helping Daniel Caunt at Harvard with Topology registration Working with Lincoln B to help UIUC work around CE problems caused by deletion of state at boot time Derek: Working with Purdue to try and resolve missing Gratia data caused by their SLURM database going down and the CE not creating history entries on job removal; BrianL says the latter may be by design These kinds of issues should stop happening once we move to the HTCondor-CE probe instead of the batch system probes OSG DevOps \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. XRootD Monitoring collector changes from validation. So far, just monitoring updates, no functionality changes. Will deploy as necessary. Discussion with John about persistent state Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 +0 In Progress 2 +0 Development Complete 17 -1 Ready for Testing 0 -5 Ready for Release 33 -6 Total Software Ready for Testing gratia-probe 1.22.3 (partially) osg-ce 3.5-6 xcache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale RFT tickets","title":"February 9, 2021"},{"location":"meetings/2021/TechArea20210209/#osg-technology-area-meeting-9-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 9 February 2021"},{"location":"meetings/2021/TechArea20210209/#announcements","text":"dHTC campus workshop today! OSG All Hands March 1-5 Mat, BrianL out this Friday","title":"Announcements"},{"location":"meetings/2021/TechArea20210209/#triage-duty","text":"This week: Carl Next week: BrianL 3 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210209/#jira","text":"# of tickets \u0394 State 138 +8 Open 12 -3 Selected for Dev 34 +2 In Progress 15 +2 Dev Complete 34 -3 Ready for Testing 1 -7 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210209/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Carl, Mat): Make upcoming \u2190\u2192 3.5-upcoming switch (tomorrow 2/10) OSG 3.5.32 AI (Mat): Token issuer packaging AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210209/#discussion","text":"Doc focus will concentrate on 3.6 documentation; those who can make it should use the whole day GlideinWMS 3.9.1 will be released later today","title":"Discussion"},{"location":"meetings/2021/TechArea20210209/#support-update","text":"Carl: Support ticket for batch vs payload core hour discrepancy (needs further investigation and will be tracked in JIRA instead) Helping Daniel Caunt at Harvard with Topology registration Working with Lincoln B to help UIUC work around CE problems caused by deletion of state at boot time Derek: Working with Purdue to try and resolve missing Gratia data caused by their SLURM database going down and the CE not creating history entries on job removal; BrianL says the latter may be by design These kinds of issues should stop happening once we move to the HTCondor-CE probe instead of the batch system probes","title":"Support Update"},{"location":"meetings/2021/TechArea20210209/#osg-devops","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. XRootD Monitoring collector changes from validation. So far, just monitoring updates, no functionality changes. Will deploy as necessary. Discussion with John about persistent state","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210209/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210209/#osg-release-team","text":"3.5.32 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 +0 In Progress 2 +0 Development Complete 17 -1 Ready for Testing 0 -5 Ready for Release 33 -6 Total Software Ready for Testing gratia-probe 1.22.3 (partially) osg-ce 3.5-6 xcache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210209/#discussion_2","text":"AI (TimT): clean up stale RFT tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210216/","text":"OSG Technology Area Meeting, 16 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 OSG All Hands March 1-5 Triage Duty \u00b6 This week: BrianL Next week: Mat 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 134 -4 Open 16 +4 Selected for Dev 31 -3 In Progress 14 -1 Dev Complete 39 +5 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) New column added for EL8 success/failure AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming OSG 3.5.32 AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25 (all day if possible) Discussion \u00b6 Container backfill: GRACC can handle the new 'Execution Endpoint' service. GlideinWMS 3.9.1 is out; HTTP service has been split out of the default RPM to make containerization easier. Q (Marian): How does the factory know how much disk space is available for a slot? A (Marco): Uses what HTCondor reports (which is dynamically measured). Open HTCondor ticket (HTCONDOR-174) for adding a way to set a disk quota for a slot. HTCondor 8.9.12 will not be ready for 3.6 so we will ship 8.9.11. Support Update \u00b6 SIUE (Southern Illinois University Edwardsville) (BrianL): discussing CE support for Ubuntu CU Boulder (BrianL, Carl, Derek): some 0 CPU usage records with non-zero walltimes OSG DevOps \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): documentation for the GRACC rolling update and fresh install APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. Discussion of the Zoom attendees script Derek wrote. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 7 -1 Open 3 +1 Selected for Development 3 -1 In Progress 1 -1 Development Complete 22 +5 Ready for Testing 0 +0 Ready for Release 36 +3 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale RFT tickets","title":"February 16, 2021"},{"location":"meetings/2021/TechArea20210216/#osg-technology-area-meeting-16-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 16 February 2021"},{"location":"meetings/2021/TechArea20210216/#announcements","text":"OSG All Hands March 1-5","title":"Announcements"},{"location":"meetings/2021/TechArea20210216/#triage-duty","text":"This week: BrianL Next week: Mat 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210216/#jira","text":"# of tickets \u0394 State 134 -4 Open 16 +4 Selected for Dev 31 -3 In Progress 14 -1 Dev Complete 39 +5 Ready for Testing 1 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210216/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) New column added for EL8 success/failure AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming OSG 3.5.32 AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25 (all day if possible)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210216/#discussion","text":"Container backfill: GRACC can handle the new 'Execution Endpoint' service. GlideinWMS 3.9.1 is out; HTTP service has been split out of the default RPM to make containerization easier. Q (Marian): How does the factory know how much disk space is available for a slot? A (Marco): Uses what HTCondor reports (which is dynamically measured). Open HTCondor ticket (HTCONDOR-174) for adding a way to set a disk quota for a slot. HTCondor 8.9.12 will not be ready for 3.6 so we will ship 8.9.11.","title":"Discussion"},{"location":"meetings/2021/TechArea20210216/#support-update","text":"SIUE (Southern Illinois University Edwardsville) (BrianL): discussing CE support for Ubuntu CU Boulder (BrianL, Carl, Derek): some 0 CPU usage records with non-zero walltimes","title":"Support Update"},{"location":"meetings/2021/TechArea20210216/#osg-devops","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): documentation for the GRACC rolling update and fresh install APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. Discussion of the Zoom attendees script Derek wrote.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210216/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210216/#osg-release-team","text":"3.5.32 \u0394 Status 7 -1 Open 3 +1 Selected for Development 3 -1 In Progress 1 -1 Development Complete 22 +5 Ready for Testing 0 +0 Ready for Release 36 +3 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210216/#discussion_2","text":"AI (TimT): clean up stale RFT tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210223/","text":"OSG Technology Area Meeting, 23 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 OSG All Hands March 1-5 Triage Duty \u00b6 This week: Mat Next week: TimT 2 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 132 -2 Open 18 +2 Selected for Dev 34 +3 In Progress 12 -2 Dev Complete 45 +6 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (BrianL): Update osg-test to use scitokens AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Carl): Freshen the GPG key ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-3275 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Mat): osg-ca-certs-updater build for EL7 AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming Punt on osg-obsoletes and osg-next for the initial release Doc Focus Feb 25 (all day if possible) Carl: Document changes in Gratia Probe 2 and provide upgrade instructions Carl: Add material admonitions to the deprecated 3.5 documents All: Fill in upgrade instructions for OSG 3.6 components Discussion \u00b6 In the HTCondor-CE Gratia Probe ProbeConfig, the data folder should match the per-job history dir. Support Update \u00b6 SIUE (Southern Illinois University Edwardsville) (BrianL): got successful Ubuntu 20 pilots with patches to HTCondor Purdue (Carl, Derek): Custom Gratia probe to fill in gap in usage without the DN information. OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches, deployed on topology-itb. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 7 +0 Open 2 -1 Selected for Development 2 -1 In Progress 1 +0 Development Complete 24 +2 Ready for Testing 0 +0 Ready for Release 36 +0 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale RFT tickets","title":"February 23, 2021"},{"location":"meetings/2021/TechArea20210223/#osg-technology-area-meeting-23-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 23 February 2021"},{"location":"meetings/2021/TechArea20210223/#announcements","text":"OSG All Hands March 1-5","title":"Announcements"},{"location":"meetings/2021/TechArea20210223/#triage-duty","text":"This week: Mat Next week: TimT 2 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210223/#jira","text":"# of tickets \u0394 State 132 -2 Open 18 +2 Selected for Dev 34 +3 In Progress 12 -2 Dev Complete 45 +6 Ready for Testing 1 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210223/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (BrianL): Update osg-test to use scitokens AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Carl): Freshen the GPG key ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-3275 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Mat): osg-ca-certs-updater build for EL7 AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming Punt on osg-obsoletes and osg-next for the initial release Doc Focus Feb 25 (all day if possible) Carl: Document changes in Gratia Probe 2 and provide upgrade instructions Carl: Add material admonitions to the deprecated 3.5 documents All: Fill in upgrade instructions for OSG 3.6 components","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210223/#discussion","text":"In the HTCondor-CE Gratia Probe ProbeConfig, the data folder should match the per-job history dir.","title":"Discussion"},{"location":"meetings/2021/TechArea20210223/#support-update","text":"SIUE (Southern Illinois University Edwardsville) (BrianL): got successful Ubuntu 20 pilots with patches to HTCondor Purdue (Carl, Derek): Custom Gratia probe to fill in gap in usage without the DN information.","title":"Support Update"},{"location":"meetings/2021/TechArea20210223/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches, deployed on topology-itb.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210223/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210223/#osg-release-team","text":"3.5.32 \u0394 Status 7 +0 Open 2 -1 Selected for Development 2 -1 In Progress 1 +0 Development Complete 24 +2 Ready for Testing 0 +0 Ready for Release 36 +0 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210223/#discussion_2","text":"AI (TimT): clean up stale RFT tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210302/","text":"OSG Technology Area Meeting, 2 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Mat OOO next week BrianL OOO next Monday Triage Duty \u00b6 This week: TimT Next week: Carl (?) 4 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 131 -1 Open 14 -4 Selected for Dev 28 -6 In Progress 5 -7 Dev Complete 51 +6 Ready for Testing 10 +9 Ready for Release OSG Software Team \u00b6 OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 ) Discussion \u00b6 GlideinWMS 3.7.3 expected next week; will not include cvmfsexec integration but HTCondor version comparison bugs should be fixed. New Docker version 20.10.4 caused hung jobs all over CHTC. TimT dealing with the fallout -- others should avoid upgrading. Debian build files have been merged into scitokens-cpp; Derek should tag a new release. HTCondor 8.9.12 in progress; developers working on updating the default security configuration. Many EL8 tickets in Ready for Testing will be moved back to Open to update package versions. Support Update \u00b6 Mat: Misconfigured CVMFS/Squid at Wisconsin; Mat will register CHTC Squid in Topology; CHTC infrastructure will take care of more involved config changes. Derek: Debugging Folding@Home issues at Syracuse; likely requires Folding@Home configuration change to deal with consumer GPUs at Syracuse. Derek/Carl: Continuing to debug Purdue accounting discrepancy -- urgent because the WLCG is finalizing monthly accounting info soon. Marian: Assisting IGWN users at Georgia Tech with getting jobs running from their submit host. (https://support.opensciencegrid.org/a/tickets/66744) Marian: Debugging OASIS issues with jobs running at CRUSH. (https://support.opensciencegrid.org/a/tickets/66839) OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger (on-going) DONE: Gratia probe update for queue time metric XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. DONE: Map of StashCache origins and caches, deployed and done! Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 9 +2 Open 12 +10 Selected for Development 4 +2 In Progress 1 +0 Development Complete 14 -10 Ready for Testing 0 +0 Ready for Release 40 +4 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"March 2, 2021"},{"location":"meetings/2021/TechArea20210302/#osg-technology-area-meeting-2-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 2 March 2021"},{"location":"meetings/2021/TechArea20210302/#announcements","text":"Mat OOO next week BrianL OOO next Monday","title":"Announcements"},{"location":"meetings/2021/TechArea20210302/#triage-duty","text":"This week: TimT Next week: Carl (?) 4 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210302/#jira-as-of-monday","text":"# of tickets \u0394 State 131 -1 Open 14 -4 Selected for Dev 28 -6 In Progress 5 -7 Dev Complete 51 +6 Ready for Testing 10 +9 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210302/#osg-software-team","text":"OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210302/#discussion","text":"GlideinWMS 3.7.3 expected next week; will not include cvmfsexec integration but HTCondor version comparison bugs should be fixed. New Docker version 20.10.4 caused hung jobs all over CHTC. TimT dealing with the fallout -- others should avoid upgrading. Debian build files have been merged into scitokens-cpp; Derek should tag a new release. HTCondor 8.9.12 in progress; developers working on updating the default security configuration. Many EL8 tickets in Ready for Testing will be moved back to Open to update package versions.","title":"Discussion"},{"location":"meetings/2021/TechArea20210302/#support-update","text":"Mat: Misconfigured CVMFS/Squid at Wisconsin; Mat will register CHTC Squid in Topology; CHTC infrastructure will take care of more involved config changes. Derek: Debugging Folding@Home issues at Syracuse; likely requires Folding@Home configuration change to deal with consumer GPUs at Syracuse. Derek/Carl: Continuing to debug Purdue accounting discrepancy -- urgent because the WLCG is finalizing monthly accounting info soon. Marian: Assisting IGWN users at Georgia Tech with getting jobs running from their submit host. (https://support.opensciencegrid.org/a/tickets/66744) Marian: Debugging OASIS issues with jobs running at CRUSH. (https://support.opensciencegrid.org/a/tickets/66839)","title":"Support Update"},{"location":"meetings/2021/TechArea20210302/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger (on-going) DONE: Gratia probe update for queue time metric XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. DONE: Map of StashCache origins and caches, deployed and done!","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210302/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210302/#osg-release-team","text":"3.5.32 \u0394 Status 9 +2 Open 12 +10 Selected for Development 4 +2 In Progress 1 +0 Development Complete 14 -10 Ready for Testing 0 +0 Ready for Release 40 +4 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210302/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210309/","text":"OSG Technology Area Meeting, 9 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, TimT Announcements \u00b6 Mat OOO this week Triage Duty \u00b6 This week: Carl Next week: BrianL 7 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 133 +2 Open 23 +9 Selected for Dev 28 +0 In Progress 5 +0 Dev Complete 20 -31 Ready for Testing 1 -9 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today 2-6pm Central OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Gratia probe 1.23.2 with fixe to QueueTime collection AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 ) Discussion \u00b6 We only need to build xrootd-hdfs build for 3.5 EL7 upcoming, can be ignored for 3.6 and 3.5 EL8 upcoming Support Update \u00b6 AGLT2 (BrianL): helped them downgrade to OSG 3.5 after an upgrade to 3.6. In addition to downgrading RPMs, they had to uncomment the line in /etc/grid-security/gsi-authz.conf to re-enable LCMAPS Purdue (BrianL): ran into issues with the new supervisord backfill container not having rootly permissions Purdue (Carl, Derek): made custom Gratia probe to generate missed February records OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger (pull request submitted) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics writing is ongoing for user \"wait time\" Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"March 9, 2021"},{"location":"meetings/2021/TechArea20210309/#osg-technology-area-meeting-9-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, TimT","title":"OSG Technology Area Meeting, 9 March 2021"},{"location":"meetings/2021/TechArea20210309/#announcements","text":"Mat OOO this week","title":"Announcements"},{"location":"meetings/2021/TechArea20210309/#triage-duty","text":"This week: Carl Next week: BrianL 7 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210309/#jira-as-of-monday","text":"# of tickets \u0394 State 133 +2 Open 23 +9 Selected for Dev 28 +0 In Progress 5 +0 Dev Complete 20 -31 Ready for Testing 1 -9 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210309/#osg-software-team","text":"Kubernetes Hackathon today 2-6pm Central OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Gratia probe 1.23.2 with fixe to QueueTime collection AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210309/#discussion","text":"We only need to build xrootd-hdfs build for 3.5 EL7 upcoming, can be ignored for 3.6 and 3.5 EL8 upcoming","title":"Discussion"},{"location":"meetings/2021/TechArea20210309/#support-update","text":"AGLT2 (BrianL): helped them downgrade to OSG 3.5 after an upgrade to 3.6. In addition to downgrading RPMs, they had to uncomment the line in /etc/grid-security/gsi-authz.conf to re-enable LCMAPS Purdue (BrianL): ran into issues with the new supervisord backfill container not having rootly permissions Purdue (Carl, Derek): made custom Gratia probe to generate missed February records","title":"Support Update"},{"location":"meetings/2021/TechArea20210309/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger (pull request submitted) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics writing is ongoing for user \"wait time\"","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210309/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210309/#osg-release-team","text":"3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210309/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210323/","text":"OSG Technology Area Meeting, 23 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco, Marian, Mat, TimT Announcements \u00b6 Kubernetes Hackathon today 1-5pm TimT OOO starting Mar 26, returning Apr 6 Triage Duty \u00b6 This week: TimT Next week: Mat 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 136 +4 Open 12 -2 Selected for Dev 27 -7 In Progress 9 +4 Dev Complete 39 +9 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 AI (Carl, with help from Mat): Enable networking in Koji builds Kubernetes Hackathon AI (Mat): put together Hosted CE submitting to the CHTC Slurm cluster AI (Carl): create koji builder pod in production namespace AI (BrianL): deploy ITB central collector Discussion \u00b6 The new version of HTCondor-CE 5 should be pulled from testing due to bugs found. AI (Marco): Add check to frontend to make sure the VOMS signing certificate is valid. Support Update \u00b6 SDSC Expanse (BrianL): Released production tarballs are broken for the OSG case but there is a workaround for Hosted CEs Marian: Public links to Freshdesk tickets don't work for some people; the workaround for them is to use incognito mode. Freshdesk refuses to fix the issue so for now we have to remind people to use incognito mode. Purdue records (Derek, Carl): Gratia probe seemed to be sending records for local usage, not just OSG. Carl will investigate and provide a software fix. LBL (Carl): Continuing to help with Squid registration; some of their Squids are internal and should not be registered. OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger, merged. XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics: Waittime has gone through a few iterations. Pull request ready for review: https://github.com/path-cc/metric-tools/pull/22 Discussion \u00b6 gracc-status RPM can be dropped from OSG devops repo, but gracc-archive RPM should be kept. OSG Release Team \u00b6 3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"March 23, 2021"},{"location":"meetings/2021/TechArea20210323/#osg-technology-area-meeting-23-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 23 March 2021"},{"location":"meetings/2021/TechArea20210323/#announcements","text":"Kubernetes Hackathon today 1-5pm TimT OOO starting Mar 26, returning Apr 6","title":"Announcements"},{"location":"meetings/2021/TechArea20210323/#triage-duty","text":"This week: TimT Next week: Mat 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210323/#jira-as-of-monday","text":"# of tickets \u0394 State 136 +4 Open 12 -2 Selected for Dev 27 -7 In Progress 9 +4 Dev Complete 39 +9 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210323/#osg-software-team","text":"AI (Carl, with help from Mat): Enable networking in Koji builds Kubernetes Hackathon AI (Mat): put together Hosted CE submitting to the CHTC Slurm cluster AI (Carl): create koji builder pod in production namespace AI (BrianL): deploy ITB central collector","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210323/#discussion","text":"The new version of HTCondor-CE 5 should be pulled from testing due to bugs found. AI (Marco): Add check to frontend to make sure the VOMS signing certificate is valid.","title":"Discussion"},{"location":"meetings/2021/TechArea20210323/#support-update","text":"SDSC Expanse (BrianL): Released production tarballs are broken for the OSG case but there is a workaround for Hosted CEs Marian: Public links to Freshdesk tickets don't work for some people; the workaround for them is to use incognito mode. Freshdesk refuses to fix the issue so for now we have to remind people to use incognito mode. Purdue records (Derek, Carl): Gratia probe seemed to be sending records for local usage, not just OSG. Carl will investigate and provide a software fix. LBL (Carl): Continuing to help with Squid registration; some of their Squids are internal and should not be registered.","title":"Support Update"},{"location":"meetings/2021/TechArea20210323/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger, merged. XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics: Waittime has gone through a few iterations. Pull request ready for review: https://github.com/path-cc/metric-tools/pull/22","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210323/#discussion_1","text":"gracc-status RPM can be dropped from OSG devops repo, but gracc-archive RPM should be kept.","title":"Discussion"},{"location":"meetings/2021/TechArea20210323/#osg-release-team","text":"3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210323/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210330/","text":"OSG Technology Area Meeting, 30 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Jason Patton, Marco, Marian, Mat Announcements \u00b6 IRIS-HEP full team retreat Apr 27-30 canceled TimT OOO, returning Apr 6 Triage Duty \u00b6 This week: Mat Next week: BrianL (?) 7 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 139 +3 Open 15 +3 Selected for Dev 27 +0 In Progress 8 -1 Dev Complete 29 -10 Ready for Testing 9 +8 Ready for Release OSG Software Team \u00b6 OSG 3.5.33/3.6 xrootd-multiuser is broken for XRootD 5. Should we delay the release? osg-xrootd needs to be updated to fix its use of ofs.authlib Anything else we should document in the update notes? AI (Carl): Rebuild condor RPM AI (Mat): Add multiple config directories to HTCondor packaging AI (Carl, with help from Mat): Enable networking in Koji builds AI (Mat): Finish adding CVMFS to the OSG backfill container Discussion \u00b6 kojibuilder2 (new K8s builder in the production namespace) not reporting to the koji hub. GlideinWMS: 3.7.3 release candidate is in testing. New 3.9 release needed to fix the following bugs: https://cdcvs.fnal.gov/redmine/issues/25620, https://cdcvs.fnal.gov/redmine/issues/25619 String encoding issue at glideFactoryLib.py, Update LDAP module for Python 3, both affect only AWS submission, not regular grid submission. Support Update \u00b6 Chameleon Cloud (BrianL): investigating an issue where the OSG validation script is failing so the container isn't running jobs Purdue (Carl, Derek): Derek successfully removed the errant local records for Purdue; Carl will ask Purdue to re-run the custom Gratia probe he provided to them. AMNH (Derek): Assisting them with SLURM configuration. Might be worthwhile to write a 'recommended SLURM configuration' document, even if it's not widely publicized. OzSTAR (Marian): Assisting them with stash cache setup. OSG DevOps \u00b6 XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming Discussion \u00b6 None this week","title":"March 30, 2021"},{"location":"meetings/2021/TechArea20210330/#osg-technology-area-meeting-30-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Jason Patton, Marco, Marian, Mat","title":"OSG Technology Area Meeting, 30 March 2021"},{"location":"meetings/2021/TechArea20210330/#announcements","text":"IRIS-HEP full team retreat Apr 27-30 canceled TimT OOO, returning Apr 6","title":"Announcements"},{"location":"meetings/2021/TechArea20210330/#triage-duty","text":"This week: Mat Next week: BrianL (?) 7 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210330/#jira-as-of-monday","text":"# of tickets \u0394 State 139 +3 Open 15 +3 Selected for Dev 27 +0 In Progress 8 -1 Dev Complete 29 -10 Ready for Testing 9 +8 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210330/#osg-software-team","text":"OSG 3.5.33/3.6 xrootd-multiuser is broken for XRootD 5. Should we delay the release? osg-xrootd needs to be updated to fix its use of ofs.authlib Anything else we should document in the update notes? AI (Carl): Rebuild condor RPM AI (Mat): Add multiple config directories to HTCondor packaging AI (Carl, with help from Mat): Enable networking in Koji builds AI (Mat): Finish adding CVMFS to the OSG backfill container","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210330/#discussion","text":"kojibuilder2 (new K8s builder in the production namespace) not reporting to the koji hub. GlideinWMS: 3.7.3 release candidate is in testing. New 3.9 release needed to fix the following bugs: https://cdcvs.fnal.gov/redmine/issues/25620, https://cdcvs.fnal.gov/redmine/issues/25619 String encoding issue at glideFactoryLib.py, Update LDAP module for Python 3, both affect only AWS submission, not regular grid submission.","title":"Discussion"},{"location":"meetings/2021/TechArea20210330/#support-update","text":"Chameleon Cloud (BrianL): investigating an issue where the OSG validation script is failing so the container isn't running jobs Purdue (Carl, Derek): Derek successfully removed the errant local records for Purdue; Carl will ask Purdue to re-run the custom Gratia probe he provided to them. AMNH (Derek): Assisting them with SLURM configuration. Might be worthwhile to write a 'recommended SLURM configuration' document, even if it's not widely publicized. OzSTAR (Marian): Assisting them with stash cache setup.","title":"Support Update"},{"location":"meetings/2021/TechArea20210330/#osg-devops","text":"XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210330/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210330/#osg-release-team","text":"Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210330/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210406/","text":"OSG Technology Area Meeting, 6 April 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 138 -1 Open 15 +0 Selected for Dev 26 -1 In Progress 12 +3 Dev Complete 26 -3 Ready for Testing 0 -9 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today at 1pm, same coordinates AI (Carl): Fix kojibuilder2, test prescribed token location container AI (Mat): CHTC \"Canary\" SLURM CE OSG 3.5.33/3.6 AI (BrianL): Build blahp 2.0.0 Discussion \u00b6 AI (BrianL): Review XRootD software support policy. HTCondor 8.9.13 has been tested but we are likely to skip it since 9.0.0 is imminent and we're waiting on upgrade instructions from the developers. Support Update \u00b6 Carl: Continuing to work with Purdue on accounting; waiting for logs. Mat: Helping ICTS-TIFR (LIGO site in India) with Topology registartion. OSG DevOps \u00b6 XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming Discussion \u00b6 None this week","title":"April 6, 2021"},{"location":"meetings/2021/TechArea20210406/#osg-technology-area-meeting-6-april-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 6 April 2021"},{"location":"meetings/2021/TechArea20210406/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210406/#triage-duty","text":"This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210406/#jira-as-of-monday","text":"# of tickets \u0394 State 138 -1 Open 15 +0 Selected for Dev 26 -1 In Progress 12 +3 Dev Complete 26 -3 Ready for Testing 0 -9 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210406/#osg-software-team","text":"Kubernetes hackathon today at 1pm, same coordinates AI (Carl): Fix kojibuilder2, test prescribed token location container AI (Mat): CHTC \"Canary\" SLURM CE OSG 3.5.33/3.6 AI (BrianL): Build blahp 2.0.0","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210406/#discussion","text":"AI (BrianL): Review XRootD software support policy. HTCondor 8.9.13 has been tested but we are likely to skip it since 9.0.0 is imminent and we're waiting on upgrade instructions from the developers.","title":"Discussion"},{"location":"meetings/2021/TechArea20210406/#support-update","text":"Carl: Continuing to work with Purdue on accounting; waiting for logs. Mat: Helping ICTS-TIFR (LIGO site in India) with Topology registartion.","title":"Support Update"},{"location":"meetings/2021/TechArea20210406/#osg-devops","text":"XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210406/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210406/#osg-release-team","text":"Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210406/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210413/","text":"OSG Technology Area Meeting, 13 April 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T Announcements \u00b6 BrianL out this Thu/Fri Marian on extended leave Triage Duty \u00b6 This week: Carl Next week: Mat 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 143 +5 Open 14 -1 Selected for Dev 27 +1 In Progress 12 +0 Dev Complete 28 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.33/3.6 AI (Carl): Promote Frontier Squid to testing AI (Carl): Rebuild Blahp 2.0.1 in OSG 3.6 AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Mat): Build HTCondor-CE 5.1.0 once released upstream AI (Carl): Kick off VMU tests for htvault-config and htgettoken AI (Mat): Debug Tiger Slurm Hosted CE failure to start Discussion \u00b6 None this week Support Update \u00b6 SIUE (BrianL): they're trying out a self-hosted CE in front of their Ubuntu 20 cluster University of Tennessee Chattanooga (BrianL): multi-VO Hosted CEs don't work because HTCondor-CE sets HOME from the CE by default. Fixed in to-be-released versions of HTCondor-CE Lancium (Mat): debug low contributions after updating to the latest backfill container image OSG DevOps \u00b6 XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming Discussion \u00b6 None this week","title":"April 13, 2021"},{"location":"meetings/2021/TechArea20210413/#osg-technology-area-meeting-13-april-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 13 April 2021"},{"location":"meetings/2021/TechArea20210413/#announcements","text":"BrianL out this Thu/Fri Marian on extended leave","title":"Announcements"},{"location":"meetings/2021/TechArea20210413/#triage-duty","text":"This week: Carl Next week: Mat 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210413/#jira-as-of-monday","text":"# of tickets \u0394 State 143 +5 Open 14 -1 Selected for Dev 27 +1 In Progress 12 +0 Dev Complete 28 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210413/#osg-software-team","text":"OSG 3.5.33/3.6 AI (Carl): Promote Frontier Squid to testing AI (Carl): Rebuild Blahp 2.0.1 in OSG 3.6 AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Mat): Build HTCondor-CE 5.1.0 once released upstream AI (Carl): Kick off VMU tests for htvault-config and htgettoken AI (Mat): Debug Tiger Slurm Hosted CE failure to start","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210413/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210413/#support-update","text":"SIUE (BrianL): they're trying out a self-hosted CE in front of their Ubuntu 20 cluster University of Tennessee Chattanooga (BrianL): multi-VO Hosted CEs don't work because HTCondor-CE sets HOME from the CE by default. Fixed in to-be-released versions of HTCondor-CE Lancium (Mat): debug low contributions after updating to the latest backfill container image","title":"Support Update"},{"location":"meetings/2021/TechArea20210413/#osg-devops","text":"XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210413/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210413/#osg-release-team","text":"Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210413/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210420/","text":"OSG Technology Area Meeting, 20 April 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 Mat out Friday and next Monday Triage Duty \u00b6 This week: Mat Next week: Tim 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 143 +0 Open 18 +4 Selected for Dev 28 +1 In Progress 10 -2 Dev Complete 17 -11 Ready for Testing 14 +14 Ready for Release OSG Software Team \u00b6 Need highlights of accomplishments since Jan 13 for AC meeting Kubernetes hackathon this afternoon AI (Brian): Test latest Bosco tarballs AI (Mat): Debug Tiger Slurm Hosted CE failure to start AI (Carl): Test Hosted CE SciTokens changes Doc focus this Thursday starting at 1:30pm OSG 3.5.33/3.6 AI (Brian): Kick off HTCondor-CE/HTCondor VMU tests AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Carl): Kick off VMU tests for htvault-config Discussion \u00b6 None this week Support Update \u00b6 Purdue (Carl): discuss with Derek if it's acceptable to interpolate missing data; note that the switch from batch system probes to the HTCondor-CE probe in OSG 3.6 should prevent issues like this in the future. Lancium (Mat): debug low contributions after updating to the latest backfill container image OSG Release Team \u00b6 3.5.34 \u0394 Status 10 +0 Open 5 +0 Selected for Development 3 +0 In Progress 5 +0 Development Complete 8 +0 Ready for Testing 14 +0 Ready for Release 45 +0 Total Software Ready for Testing frontier-squid-4.13-5.1 HTCondor 8.8.13 vault 1.7.0 osg-xrootd for EL8 osg-gridftp for EL8 Upcoming: xrootd-hdfs 2.2.0 Ready for Release CVMFS 2.8.1 gratia-probe 1.23.2 Data vo-client 111 Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"April 20, 2021"},{"location":"meetings/2021/TechArea20210420/#osg-technology-area-meeting-20-april-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 20 April 2021"},{"location":"meetings/2021/TechArea20210420/#announcements","text":"Mat out Friday and next Monday","title":"Announcements"},{"location":"meetings/2021/TechArea20210420/#triage-duty","text":"This week: Mat Next week: Tim 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210420/#jira-as-of-monday","text":"# of tickets \u0394 State 143 +0 Open 18 +4 Selected for Dev 28 +1 In Progress 10 -2 Dev Complete 17 -11 Ready for Testing 14 +14 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210420/#osg-software-team","text":"Need highlights of accomplishments since Jan 13 for AC meeting Kubernetes hackathon this afternoon AI (Brian): Test latest Bosco tarballs AI (Mat): Debug Tiger Slurm Hosted CE failure to start AI (Carl): Test Hosted CE SciTokens changes Doc focus this Thursday starting at 1:30pm OSG 3.5.33/3.6 AI (Brian): Kick off HTCondor-CE/HTCondor VMU tests AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Carl): Kick off VMU tests for htvault-config","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210420/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210420/#support-update","text":"Purdue (Carl): discuss with Derek if it's acceptable to interpolate missing data; note that the switch from batch system probes to the HTCondor-CE probe in OSG 3.6 should prevent issues like this in the future. Lancium (Mat): debug low contributions after updating to the latest backfill container image","title":"Support Update"},{"location":"meetings/2021/TechArea20210420/#osg-release-team","text":"3.5.34 \u0394 Status 10 +0 Open 5 +0 Selected for Development 3 +0 In Progress 5 +0 Development Complete 8 +0 Ready for Testing 14 +0 Ready for Release 45 +0 Total Software Ready for Testing frontier-squid-4.13-5.1 HTCondor 8.8.13 vault 1.7.0 osg-xrootd for EL8 osg-gridftp for EL8 Upcoming: xrootd-hdfs 2.2.0 Ready for Release CVMFS 2.8.1 gratia-probe 1.23.2 Data vo-client 111 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210420/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210504/","text":"OSG Technology Area Meeting, 4 May 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Mat, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Carl 5 (-6) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 147 +6 Open 11 -1 Selected for Dev 23 -4 In Progress 16 +4 Dev Complete 24 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon this afternoon AI (Brian): Test Hosted CE PVCs AI (Mat): Update Ubuntu WN containers and automate pushes to the OSG Harbor instance AI (Carl): Fixup production Koji builder OSG 3.5.35/3.5.36/3.6 AI (Carl): Build new XCache for upcoming/3.6 (SOFTWARE-4476) Time to get to work on verifying EL8 packages (SOFTWARE-3308) Discussion \u00b6 hosted-ce35 not reporting in - Carl to investigate since it's running the Python 3 version of the Gratia probe. Support Update \u00b6 BrianL, Mat - Lancium was seeing multiple issues for backfill containers; one of the issues was having newlines in the token, which caused HTCondor to report failure to parse. Will ask developers how HTCondor parses tokens. Carl - Purdue's gap records will be filled in from the previous day. OSG Release Team \u00b6 3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 -1 0 +0 3 +3 12 +2 Open 2 +0 2 -1 1 +1 5 +0 Selected for Development 0 +0 2 +1 3 +1 5 +2 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 7 +6 12 +6 1 +0 20 +12 Ready for Testing 0 -13 0 -1 0 +0 0 -14 Ready for Release 20 -8 19 +5 8 +5 47 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.13-5.2 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing Discussion \u00b6 HTCondor 9.0.0 bug: AES encryption + x509 proxy refresh crashes the starter. Brian L will discuss it with developers to see if it affects the OSG infrastructure. This may be fixed in 9.0.1 (expected next week); if not, we will mention it as a known issue in the release notes.","title":"May 4, 2021"},{"location":"meetings/2021/TechArea20210504/#osg-technology-area-meeting-4-may-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Mat, Tim T","title":"OSG Technology Area Meeting, 4 May 2021"},{"location":"meetings/2021/TechArea20210504/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210504/#triage-duty","text":"This week: Brian Next week: Carl 5 (-6) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210504/#jira-as-of-monday","text":"# of tickets \u0394 State 147 +6 Open 11 -1 Selected for Dev 23 -4 In Progress 16 +4 Dev Complete 24 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210504/#osg-software-team","text":"Kubernetes hackathon this afternoon AI (Brian): Test Hosted CE PVCs AI (Mat): Update Ubuntu WN containers and automate pushes to the OSG Harbor instance AI (Carl): Fixup production Koji builder OSG 3.5.35/3.5.36/3.6 AI (Carl): Build new XCache for upcoming/3.6 (SOFTWARE-4476) Time to get to work on verifying EL8 packages (SOFTWARE-3308)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210504/#discussion","text":"hosted-ce35 not reporting in - Carl to investigate since it's running the Python 3 version of the Gratia probe.","title":"Discussion"},{"location":"meetings/2021/TechArea20210504/#support-update","text":"BrianL, Mat - Lancium was seeing multiple issues for backfill containers; one of the issues was having newlines in the token, which caused HTCondor to report failure to parse. Will ask developers how HTCondor parses tokens. Carl - Purdue's gap records will be filled in from the previous day.","title":"Support Update"},{"location":"meetings/2021/TechArea20210504/#osg-release-team","text":"3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 -1 0 +0 3 +3 12 +2 Open 2 +0 2 -1 1 +1 5 +0 Selected for Development 0 +0 2 +1 3 +1 5 +2 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 7 +6 12 +6 1 +0 20 +12 Ready for Testing 0 -13 0 -1 0 +0 0 -14 Ready for Release 20 -8 19 +5 8 +5 47 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.13-5.2 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210504/#discussion_1","text":"HTCondor 9.0.0 bug: AES encryption + x509 proxy refresh crashes the starter. Brian L will discuss it with developers to see if it affects the OSG infrastructure. This may be fixed in 9.0.1 (expected next week); if not, we will mention it as a known issue in the release notes.","title":"Discussion"},{"location":"meetings/2021/TechArea20210511/","text":"OSG Technology Area Meeting, 11 May 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Mat, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 11 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 149 +2 Open 15 +4 Selected for Dev 32 +9 In Progress 12 -4 Dev Complete 25 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 GSI Transition AI (Carl): will Gratia ignore SciTokens-based pilots? AI (Carl): HTCondor-CE Gratia probe should avoid use of condor_ce_q XRootD in 3.6 Need to document native VOMS and SciTokens auth. Upstream docs? SciTokens osg-xrootd needs to be updated (at least removing LCMAPS + config) Topology changes probably need to be made to also support the new format Any new sites/CEs should be directed to the \"Campus Facilitation\" FD group Discussion \u00b6 HTCondor service startup tests in osg-test for 9.0.1 need updates to work with new upstream configuration. XRootD-TPC tests should be split into single-stream and multi-stream. GlideinWMS: GlideinWMS 3.7.4rc1 now available; fixes a regression with 3.6 frontend compatibility. OSG Scitokens patches, X509-less submission, and CVMFSEXEC will go into 3.7.5. 3.7.5 expected in a month and a half. Redmine currently locked down to people with service accounts. Some issues can be tracked in GitHub. Future authentication policy has not been decided yet. Support Update \u00b6 (Mat) Justas at CalTech is having STARTD_CRON issues; investigating with help from the HTCondor developers. (Derek) ORNL is running a patched slurm gratia probe. We should engage with them to run a production probe, if we can. But their use case complicates things. OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu... Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 3 +0 13 +1 Open 2 +0 1 -1 1 +0 4 -1 Selected for Development 0 +0 3 +1 3 +0 6 +1 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 8 +1 12 +0 1 +0 21 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 20 +1 20 +1 8 +0 49 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.15-1.1 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"May 11, 2021"},{"location":"meetings/2021/TechArea20210511/#osg-technology-area-meeting-11-may-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Mat, Tim T","title":"OSG Technology Area Meeting, 11 May 2021"},{"location":"meetings/2021/TechArea20210511/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210511/#triage-duty","text":"This week: Carl Next week: Mat 11 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210511/#jira-as-of-monday","text":"# of tickets \u0394 State 149 +2 Open 15 +4 Selected for Dev 32 +9 In Progress 12 -4 Dev Complete 25 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210511/#osg-software-team","text":"GSI Transition AI (Carl): will Gratia ignore SciTokens-based pilots? AI (Carl): HTCondor-CE Gratia probe should avoid use of condor_ce_q XRootD in 3.6 Need to document native VOMS and SciTokens auth. Upstream docs? SciTokens osg-xrootd needs to be updated (at least removing LCMAPS + config) Topology changes probably need to be made to also support the new format Any new sites/CEs should be directed to the \"Campus Facilitation\" FD group","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210511/#discussion","text":"HTCondor service startup tests in osg-test for 9.0.1 need updates to work with new upstream configuration. XRootD-TPC tests should be split into single-stream and multi-stream. GlideinWMS: GlideinWMS 3.7.4rc1 now available; fixes a regression with 3.6 frontend compatibility. OSG Scitokens patches, X509-less submission, and CVMFSEXEC will go into 3.7.5. 3.7.5 expected in a month and a half. Redmine currently locked down to people with service accounts. Some issues can be tracked in GitHub. Future authentication policy has not been decided yet.","title":"Discussion"},{"location":"meetings/2021/TechArea20210511/#support-update","text":"(Mat) Justas at CalTech is having STARTD_CRON issues; investigating with help from the HTCondor developers. (Derek) ORNL is running a patched slurm gratia probe. We should engage with them to run a production probe, if we can. But their use case complicates things.","title":"Support Update"},{"location":"meetings/2021/TechArea20210511/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu... Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210511/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210511/#osg-release-team","text":"3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 3 +0 13 +1 Open 2 +0 1 -1 1 +0 4 -1 Selected for Development 0 +0 3 +1 3 +0 6 +1 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 8 +1 12 +0 1 +0 21 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 20 +1 20 +1 8 +0 49 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.15-1.1 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210511/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210518/","text":"OSG Technology Area Meeting, 18 May 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim Announcements \u00b6 Next week's meeting canceled for HTCondor week, to resume June 1 BrianL OOO May 28 and June 1 Triage Duty \u00b6 This week: Mat Next week: TimT 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 155 +6 Open 16 +1 Selected for Dev 31 -1 In Progress 12 +0 Dev Complete 9 -16 Ready for Testing 11 +11 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34&sprint=32 AI (Carl): Production Koji builder Release AI (Mat): osg-xrootd and documentation need to be updated to use the voms-xrootd-plugin for 3.6 AI (Mat): XRootD for EL8 AI (Carl): Gratia probe Hosted CE quarantine issues AI (Carl): Gratia probe collection of VO data for token-based pilots Do we need to update the Gratia dirs for OSG 3.6? https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 Discussion \u00b6 Nightly XRootD multistream TPC tests are still failing; Derek will investigate since it might be related to xrootd-multiuser. However, this may have only been used for performance tests; Derek will ask Brian B. about real-world use cases and adjust priority accordingly. xrootd-multiuser 1.0.1 expected soon. SciTokens VO mapping: right now, pilots contain both X.509 and SciTokens credentials; Gratia prefers the former, so it may be difficult to do an integration test; adding unit tests will provide sufficient coverage for now. AI (Carl): Run VMU tests for GlideinWMS 3.7.4. Support Update \u00b6 Hosted CEs (BrianL): cert-manager changes (?) resulted in a slightly different LE chain being advertised from the CEs, requiring an update to osg-ca-certs-1.96 on the client side XRootD (Derek): Justas opened tickets with XRootD, watching to see if OSG can contribute to debugging / development for fixes. OzStar (Marian): Debugging Singularity; this may be due to attempting to run unprivileged Singularity without user namespaces. The ticket should be reassigned to the Software group; Dave Dykstra may be able to help. CalTech (Mat): Problem with long lines in STARTD_CRON output causing startd ads not to get updated; created HTCondor ticket to fix and gave Justas a workaround. LBL (Carl): Continuing to support LBL with setting up Squid. Dave Dykstra may be able to help. OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira GRACC S3 (CEPH) backup coming up, will coordinate a disaster recovery drill. XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 2 +1 5 +2 16 +3 Open 5 +3 1 +0 1 +0 7 +3 Selected for Development 0 +0 2 -1 2 -1 4 -2 In Progress 3 +1 1 -2 0 +0 4 -1 Development Complete 5 -3 2 -10 0 -1 7 -14 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 22 +1 8 -12 8 +0 38 -11 Total Software Ready for Testing OSG 3.5 HTCondor-CE 4.5.2 osg-gridftp on EL8 OSG 3.5-upcoming HTCondor 9.0.1 GlideinWMS 3.7.4 XRootD 5.2.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.1 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"May 18, 2021"},{"location":"meetings/2021/TechArea20210518/#osg-technology-area-meeting-18-may-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim","title":"OSG Technology Area Meeting, 18 May 2021"},{"location":"meetings/2021/TechArea20210518/#announcements","text":"Next week's meeting canceled for HTCondor week, to resume June 1 BrianL OOO May 28 and June 1","title":"Announcements"},{"location":"meetings/2021/TechArea20210518/#triage-duty","text":"This week: Mat Next week: TimT 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210518/#jira-as-of-monday","text":"# of tickets \u0394 State 155 +6 Open 16 +1 Selected for Dev 31 -1 In Progress 12 +0 Dev Complete 9 -16 Ready for Testing 11 +11 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210518/#osg-software-team","text":"Kubernetes Hackathon this afternoon: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34&sprint=32 AI (Carl): Production Koji builder Release AI (Mat): osg-xrootd and documentation need to be updated to use the voms-xrootd-plugin for 3.6 AI (Mat): XRootD for EL8 AI (Carl): Gratia probe Hosted CE quarantine issues AI (Carl): Gratia probe collection of VO data for token-based pilots Do we need to update the Gratia dirs for OSG 3.6? https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210518/#discussion","text":"Nightly XRootD multistream TPC tests are still failing; Derek will investigate since it might be related to xrootd-multiuser. However, this may have only been used for performance tests; Derek will ask Brian B. about real-world use cases and adjust priority accordingly. xrootd-multiuser 1.0.1 expected soon. SciTokens VO mapping: right now, pilots contain both X.509 and SciTokens credentials; Gratia prefers the former, so it may be difficult to do an integration test; adding unit tests will provide sufficient coverage for now. AI (Carl): Run VMU tests for GlideinWMS 3.7.4.","title":"Discussion"},{"location":"meetings/2021/TechArea20210518/#support-update","text":"Hosted CEs (BrianL): cert-manager changes (?) resulted in a slightly different LE chain being advertised from the CEs, requiring an update to osg-ca-certs-1.96 on the client side XRootD (Derek): Justas opened tickets with XRootD, watching to see if OSG can contribute to debugging / development for fixes. OzStar (Marian): Debugging Singularity; this may be due to attempting to run unprivileged Singularity without user namespaces. The ticket should be reassigned to the Software group; Dave Dykstra may be able to help. CalTech (Mat): Problem with long lines in STARTD_CRON output causing startd ads not to get updated; created HTCondor ticket to fix and gave Justas a workaround. LBL (Carl): Continuing to support LBL with setting up Squid. Dave Dykstra may be able to help.","title":"Support Update"},{"location":"meetings/2021/TechArea20210518/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira GRACC S3 (CEPH) backup coming up, will coordinate a disaster recovery drill. XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210518/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210518/#osg-release-team","text":"3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 2 +1 5 +2 16 +3 Open 5 +3 1 +0 1 +0 7 +3 Selected for Development 0 +0 2 -1 2 -1 4 -2 In Progress 3 +1 1 -2 0 +0 4 -1 Development Complete 5 -3 2 -10 0 -1 7 -14 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 22 +1 8 -12 8 +0 38 -11 Total Software Ready for Testing OSG 3.5 HTCondor-CE 4.5.2 osg-gridftp on EL8 OSG 3.5-upcoming HTCondor 9.0.1 GlideinWMS 3.7.4 XRootD 5.2.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.1 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210518/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210608/","text":"OSG Technology Area Meeting, 8 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Marco, Marian, Mat, TimT Announcements \u00b6 TimT OOO June 14-18 Triage Duty \u00b6 This week: TimT Next week: Carl 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 156 -5 Open 21 +5 Selected for Dev 31 +1 In Progress 10 -2 Dev Complete 8 -5 Ready for Testing 2 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): Review scitokens-cpp promotion request (should we release it for EL8?) AI (Mat): XRootD for EL8 for OSG 3.5 Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): walk Lehigh/SIUE through recovering their old accounting records Discussion \u00b6 We should release scitokens-cpp for EL8 in order to maintain symmetry with EL7 GlideinWMS 3.9.2 is in osg-development and has passed internal testing; TimT will promote it to contrib Support Update \u00b6 SIUE/Lehigh (Carl, BrianL): identified pilot accounting upload bugs (fixed in gratia-probe-1.23.3 and the HTCondor versions in testing) PSU (BrianL): $HOME expansion doesn't work for Hosted CEs submitting to local HTCondor batch systems CIT/IGWN (Marian): Marian is providing assistance with upgrading to HTCondor 9 GlideinWMS (Marco): Found a bug where temporary errors contacting the frontend collectors would get cached, causing further queries to fail until the cache expired or the frontend was restarted. This will be fixed in 3.7.5 OZStar (Derek): StashCache is not connecting to the ligo origin correctly. Difficult to iterate since in Australia. Diego and I setup a time to meet that works for all. KSU / JLab (Derek/Marian): Failures at KSU. Difficult to tell what exactly the failures are, but the faliure has something to do with xrootd, the posix preload, and downloading a file from jalb. OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira . Pull request: https://github.com/opensciencegrid/tiger-osg-config/pull/173 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! Bluepring meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.38 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 -2 4 -1 13 -3 Open 6 +1 3 +2 2 +1 11 +4 Selected for Development 0 +0 1 -1 2 +0 3 -1 In Progress 3 +0 1 +0 0 +0 4 +0 Development Complete 2 -3 3 +1 1 +1 6 -1 Ready for Testing 2 +2 0 +0 0 +0 2 +2 Ready for Release 22 +0 8 +0 9 +1 39 +1 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) xrootd-hdfs 2.2.0-1.1 (get correct username from token) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release OSG 3.5 HTCondor 8.8.13-1.1 OSG 3.5-upcoming XRootD 5.2.0 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"June 8, 2021"},{"location":"meetings/2021/TechArea20210608/#osg-technology-area-meeting-8-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 8 June 2021"},{"location":"meetings/2021/TechArea20210608/#announcements","text":"TimT OOO June 14-18","title":"Announcements"},{"location":"meetings/2021/TechArea20210608/#triage-duty","text":"This week: TimT Next week: Carl 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210608/#jira-as-of-monday","text":"# of tickets \u0394 State 156 -5 Open 21 +5 Selected for Dev 31 +1 In Progress 10 -2 Dev Complete 8 -5 Ready for Testing 2 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210608/#osg-software-team","text":"Release AI (Mat): Review scitokens-cpp promotion request (should we release it for EL8?) AI (Mat): XRootD for EL8 for OSG 3.5 Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): walk Lehigh/SIUE through recovering their old accounting records","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210608/#discussion","text":"We should release scitokens-cpp for EL8 in order to maintain symmetry with EL7 GlideinWMS 3.9.2 is in osg-development and has passed internal testing; TimT will promote it to contrib","title":"Discussion"},{"location":"meetings/2021/TechArea20210608/#support-update","text":"SIUE/Lehigh (Carl, BrianL): identified pilot accounting upload bugs (fixed in gratia-probe-1.23.3 and the HTCondor versions in testing) PSU (BrianL): $HOME expansion doesn't work for Hosted CEs submitting to local HTCondor batch systems CIT/IGWN (Marian): Marian is providing assistance with upgrading to HTCondor 9 GlideinWMS (Marco): Found a bug where temporary errors contacting the frontend collectors would get cached, causing further queries to fail until the cache expired or the frontend was restarted. This will be fixed in 3.7.5 OZStar (Derek): StashCache is not connecting to the ligo origin correctly. Difficult to iterate since in Australia. Diego and I setup a time to meet that works for all. KSU / JLab (Derek/Marian): Failures at KSU. Difficult to tell what exactly the failures are, but the faliure has something to do with xrootd, the posix preload, and downloading a file from jalb.","title":"Support Update"},{"location":"meetings/2021/TechArea20210608/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira . Pull request: https://github.com/opensciencegrid/tiger-osg-config/pull/173 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! Bluepring meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210608/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210608/#osg-release-team","text":"3.5.38 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 -2 4 -1 13 -3 Open 6 +1 3 +2 2 +1 11 +4 Selected for Development 0 +0 1 -1 2 +0 3 -1 In Progress 3 +0 1 +0 0 +0 4 +0 Development Complete 2 -3 3 +1 1 +1 6 -1 Ready for Testing 2 +2 0 +0 0 +0 2 +2 Ready for Release 22 +0 8 +0 9 +1 39 +1 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) xrootd-hdfs 2.2.0-1.1 (get correct username from token) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release OSG 3.5 HTCondor 8.8.13-1.1 OSG 3.5-upcoming XRootD 5.2.0 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210608/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210615/","text":"OSG Technology Area Meeting, 15 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Marian, Mat Announcements \u00b6 TimT OOO June 14-18 CHTC team OOO Thu Jun 17 BrianL OOO Fri and Mon Mat OOO Fri afternoon Triage Duty \u00b6 This week: Carl Next week: BrianL 9 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 154 -2 Open 21 +0 Selected for Dev 34 +3 In Progress 6 -4 Dev Complete 9 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Release AI (BrianL): Add new EIC VO DN ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4666 ) AI (Mat): Build empty-condor package AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Ensure that Gratia accounts for SciTokens-based pilots ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4615 ) Discussion \u00b6 GlideinWMS 3.7 release expected later this month. Dennis is reviewing a PR for the frontend to increase admin control over SciToken generation ( https://github.com/glideinWMS/glideinwms/pull/52 ) Support Update \u00b6 SIUE/Lehigh (Carl): provided instructions for restoring missing pilot data OzStar (Derek, Marian): Cert was communicated incorrectly, and osg-xrootd-standalone was conflicting with the stash cache auth. ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4668 ) OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Blueprint meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. Added new wait time metrics: https://github.com/path-cc/metric-tools/pull/26 (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week","title":"June 15, 2021"},{"location":"meetings/2021/TechArea20210615/#osg-technology-area-meeting-15-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Marian, Mat","title":"OSG Technology Area Meeting, 15 June 2021"},{"location":"meetings/2021/TechArea20210615/#announcements","text":"TimT OOO June 14-18 CHTC team OOO Thu Jun 17 BrianL OOO Fri and Mon Mat OOO Fri afternoon","title":"Announcements"},{"location":"meetings/2021/TechArea20210615/#triage-duty","text":"This week: Carl Next week: BrianL 9 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210615/#jira-as-of-monday","text":"# of tickets \u0394 State 154 -2 Open 21 +0 Selected for Dev 34 +3 In Progress 6 -4 Dev Complete 9 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210615/#osg-software-team","text":"Kubernetes Hackathon today: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Release AI (BrianL): Add new EIC VO DN ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4666 ) AI (Mat): Build empty-condor package AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Ensure that Gratia accounts for SciTokens-based pilots ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4615 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210615/#discussion","text":"GlideinWMS 3.7 release expected later this month. Dennis is reviewing a PR for the frontend to increase admin control over SciToken generation ( https://github.com/glideinWMS/glideinwms/pull/52 )","title":"Discussion"},{"location":"meetings/2021/TechArea20210615/#support-update","text":"SIUE/Lehigh (Carl): provided instructions for restoring missing pilot data OzStar (Derek, Marian): Cert was communicated incorrectly, and osg-xrootd-standalone was conflicting with the stash cache auth. ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4668 )","title":"Support Update"},{"location":"meetings/2021/TechArea20210615/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Blueprint meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. Added new wait time metrics: https://github.com/path-cc/metric-tools/pull/26 (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210615/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210622/","text":"OSG Technology Area Meeting, 22 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Jack Yuan, Marian, Tim Announcements \u00b6 Carl OOO Wed-Fri Triage Duty \u00b6 This week: BrianL Next week: ??? 9 (-0) open FreshDesk tickets 0 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +6 Open 21 +0 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Doc focus this Friday afternoon Release AI (BrianL): kick off Vault VMU tests (SOFTWARE-4677) AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (TimT): Rebuild new HTCondor daily into the devops repo so it can be tested in the OSG Open Pool Discussion \u00b6 None this week Support Update \u00b6 BrianL (NDSU Lancium): Backfill container not detecting their GPUs; Brian will consult Mats for assistance. Carl (Lehigh): Successfully resent old records. Carl will double-check that current records are working correctly.f Carl, Derek (SIUE): No longer receiving records, planning a live debugging session this afternoon OSG DevOps \u00b6 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Design document is done and is being distributed. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 +0 4 +0 13 +0 Open 2 -4 4 +1 1 -1 7 -4 Selected for Development 2 +2 1 +0 3 +1 6 +3 In Progress 0 -3 1 +0 0 +0 1 -3 Development Complete 5 +3 4 +1 2 +1 11 +5 Ready for Testing 0 -2 0 +0 0 +0 0 -2 Ready for Release 18 -4 10 +2 10 +1 38 -1 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 scitokens-cpp 0.6.2 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"June 22, 2021"},{"location":"meetings/2021/TechArea20210622/#osg-technology-area-meeting-22-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Jack Yuan, Marian, Tim","title":"OSG Technology Area Meeting, 22 June 2021"},{"location":"meetings/2021/TechArea20210622/#announcements","text":"Carl OOO Wed-Fri","title":"Announcements"},{"location":"meetings/2021/TechArea20210622/#triage-duty","text":"This week: BrianL Next week: ??? 9 (-0) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210622/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +6 Open 21 +0 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210622/#osg-software-team","text":"Doc focus this Friday afternoon Release AI (BrianL): kick off Vault VMU tests (SOFTWARE-4677) AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (TimT): Rebuild new HTCondor daily into the devops repo so it can be tested in the OSG Open Pool","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210622/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210622/#support-update","text":"BrianL (NDSU Lancium): Backfill container not detecting their GPUs; Brian will consult Mats for assistance. Carl (Lehigh): Successfully resent old records. Carl will double-check that current records are working correctly.f Carl, Derek (SIUE): No longer receiving records, planning a live debugging session this afternoon","title":"Support Update"},{"location":"meetings/2021/TechArea20210622/#osg-devops","text":"XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Design document is done and is being distributed. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210622/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210622/#osg-release-team","text":"3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 +0 4 +0 13 +0 Open 2 -4 4 +1 1 -1 7 -4 Selected for Development 2 +2 1 +0 3 +1 6 +3 In Progress 0 -3 1 +0 0 +0 1 -3 Development Complete 5 +3 4 +1 2 +1 11 +5 Ready for Testing 0 -2 0 +0 0 +0 0 -2 Ready for Release 18 -4 10 +2 10 +1 38 -1 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 scitokens-cpp 0.6.2 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210622/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210629/","text":"OSG Technology Area Meeting, 29 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Marian, Mat, Tim T Announcements \u00b6 Carl OOO July 2-7 Triage Duty \u00b6 This week: Carl Next week: BrianL 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +0 Open 19 -2 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon. Prioritize working on fallout from the recent outage, otherwise see tasks on https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Tim makeup doc focus Release AI (Mat): XRootD for EL8 for OSG 3.5. What's left? AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) Discussion \u00b6 ATLAS and CMS have tested IAM vo-client updates; Brian L will mail CERN folks to ask if they're ready for the transition XRootD 5.2 for OSG 3.5 has already been released xrootd-multiuser 1.1.0 in the 3.5 upcoming-testing repos; we're asking Justas from Caltech to test XRootD 5.3.0rc1 release candidate in the 3.5 upcoming-testing repos; Horst at OU was the most affected by bugs in previous versions so he is a good testing candidate AI (Mat): Create automated Koji user for doing CI builds Support Update \u00b6 MWT2 (BrianL): merged in .rpmsave containing a config fix for held job pile-up due to `SYSTEM PERIODIC ` expressions fighting Lehigh (Derek): (DONE) Removed extranous records GLOW (Derek): Submitted GRACC records with start date in 2008. Caused by node coming up after power outage with date set to 2008, so jobs will have \"started\" in 2008, and run until now, resulting in huge walltimes. Will remove. KSU (Derek): Likely IDS blocking access to data for JLAB jobs running at KSU. Not sure how to solve other than have JLAB blacklist KSU. OSG DevOps \u00b6 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Debugging of gracc nodes after tiger update resulted in restarting a few pods, and 1 typo discovered. Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +1 Open 2 +0 4 +0 1 +0 7 +0 Selected for Development 1 -1 0 -1 3 +0 4 -2 In Progress 0 +0 2 +1 0 +0 2 +1 Development Complete 5 +0 2 -2 2 +0 9 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 17 -1 9 -1 10 +0 36 -2 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 gfal2 in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 Release this week Push out HTCondor 9.1.0 into EL6 with minimal testing","title":"June 29, 2021"},{"location":"meetings/2021/TechArea20210629/#osg-technology-area-meeting-29-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 29 June 2021"},{"location":"meetings/2021/TechArea20210629/#announcements","text":"Carl OOO July 2-7","title":"Announcements"},{"location":"meetings/2021/TechArea20210629/#triage-duty","text":"This week: Carl Next week: BrianL 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210629/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +0 Open 19 -2 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210629/#osg-software-team","text":"Kubernetes Hackathon this afternoon. Prioritize working on fallout from the recent outage, otherwise see tasks on https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Tim makeup doc focus Release AI (Mat): XRootD for EL8 for OSG 3.5. What's left? AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210629/#discussion","text":"ATLAS and CMS have tested IAM vo-client updates; Brian L will mail CERN folks to ask if they're ready for the transition XRootD 5.2 for OSG 3.5 has already been released xrootd-multiuser 1.1.0 in the 3.5 upcoming-testing repos; we're asking Justas from Caltech to test XRootD 5.3.0rc1 release candidate in the 3.5 upcoming-testing repos; Horst at OU was the most affected by bugs in previous versions so he is a good testing candidate AI (Mat): Create automated Koji user for doing CI builds","title":"Discussion"},{"location":"meetings/2021/TechArea20210629/#support-update","text":"MWT2 (BrianL): merged in .rpmsave containing a config fix for held job pile-up due to `SYSTEM PERIODIC ` expressions fighting Lehigh (Derek): (DONE) Removed extranous records GLOW (Derek): Submitted GRACC records with start date in 2008. Caused by node coming up after power outage with date set to 2008, so jobs will have \"started\" in 2008, and run until now, resulting in huge walltimes. Will remove. KSU (Derek): Likely IDS blocking access to data for JLAB jobs running at KSU. Not sure how to solve other than have JLAB blacklist KSU.","title":"Support Update"},{"location":"meetings/2021/TechArea20210629/#osg-devops","text":"XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Debugging of gracc nodes after tiger update resulted in restarting a few pods, and 1 typo discovered. Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210629/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210629/#osg-release-team","text":"3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +1 Open 2 +0 4 +0 1 +0 7 +0 Selected for Development 1 -1 0 -1 3 +0 4 -2 In Progress 0 +0 2 +1 0 +0 2 +1 Development Complete 5 +0 2 -2 2 +0 9 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 17 -1 9 -1 10 +0 36 -2 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 gfal2 in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210629/#discussion_2","text":"Release this week Push out HTCondor 9.1.0 into EL6 with minimal testing","title":"Discussion"},{"location":"meetings/2021/TechArea20210706/","text":"OSG Technology Area Meeting, 6 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco, Marian, Mat, TimT Announcements \u00b6 Carl OOO until Thursday Mat OOO Jul 9-14 TimT OOO Jul 9 Triage Duty \u00b6 This week: BrianL Next week: TimT 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 152 -8 Open 24 +5 Selected for Dev 36 +1 In Progress 9 +1 Dev Complete 8 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus Release AI (Mat): XRootD 5.3.0 RC4 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Remove deps needed for Globus from HTCondor in 3.6 Discussion \u00b6 Madison would like GlideinWMS container images with immutable tags for their production frontends. Currently the images are contributed by Diego, but BrianL will make a ticket for tracking the issue. GlideinWMS 3.7 series release not expected until a few weeks from now. Upstream HTCondor 9.0.2 and BLAHP 2.1.0 release planned for tomorrow (7/7); TimT will provide BrianL with a BLAHP tarball for testing. Support Update \u00b6 SUT (BrianL): remote host missing libltdl IGWN frontend (Marian): proxy was not getting renewed, but a pod redeploy fixed the issue. Investigate the original cause; BrianL thinks it might have been a Fetch-CRL error. GLOW (Derek): Removed abnormal CMS records (900,000+ hours for 1 job), and re-uploaded WLCG records for June. OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +0 Open 1 -1 3 -1 2 +1 6 -1 Selected for Development 0 -1 0 -1 3 +0 3 -1 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 -3 1 -1 1 -1 4 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 -5 7 -2 10 +0 29 -7 Total Software Ready for Testing OSG 3.5-upcoming XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"July 6, 2021"},{"location":"meetings/2021/TechArea20210706/#osg-technology-area-meeting-6-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 6 July 2021"},{"location":"meetings/2021/TechArea20210706/#announcements","text":"Carl OOO until Thursday Mat OOO Jul 9-14 TimT OOO Jul 9","title":"Announcements"},{"location":"meetings/2021/TechArea20210706/#triage-duty","text":"This week: BrianL Next week: TimT 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210706/#jira-as-of-monday","text":"# of tickets \u0394 State 152 -8 Open 24 +5 Selected for Dev 36 +1 In Progress 9 +1 Dev Complete 8 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210706/#osg-software-team","text":"Tim makeup doc focus Release AI (Mat): XRootD 5.3.0 RC4 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Remove deps needed for Globus from HTCondor in 3.6","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210706/#discussion","text":"Madison would like GlideinWMS container images with immutable tags for their production frontends. Currently the images are contributed by Diego, but BrianL will make a ticket for tracking the issue. GlideinWMS 3.7 series release not expected until a few weeks from now. Upstream HTCondor 9.0.2 and BLAHP 2.1.0 release planned for tomorrow (7/7); TimT will provide BrianL with a BLAHP tarball for testing.","title":"Discussion"},{"location":"meetings/2021/TechArea20210706/#support-update","text":"SUT (BrianL): remote host missing libltdl IGWN frontend (Marian): proxy was not getting renewed, but a pod redeploy fixed the issue. Investigate the original cause; BrianL thinks it might have been a Fetch-CRL error. GLOW (Derek): Removed abnormal CMS records (900,000+ hours for 1 job), and re-uploaded WLCG records for June.","title":"Support Update"},{"location":"meetings/2021/TechArea20210706/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210706/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210706/#osg-release-team","text":"3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +0 Open 1 -1 3 -1 2 +1 6 -1 Selected for Development 0 -1 0 -1 3 +0 3 -1 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 -3 1 -1 1 -1 4 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 -5 7 -2 10 +0 29 -7 Total Software Ready for Testing OSG 3.5-upcoming XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210706/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210713/","text":"OSG Technology Area Meeting, 13 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, TimT Announcements \u00b6 Mat OOO Jul 9-14 BrianL OOO Friday Triage Duty \u00b6 This week: TimT Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 151 -1 Open 24 +0 Selected for Dev 40 +4 In Progress 11 +2 Dev Complete 7 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Kubernetes Hackathon Release AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Tag and build VO client Discussion \u00b6 None this week Support Update \u00b6 None this week OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 4 +0 14 +0 Open 1 +0 3 +0 1 -1 5 -1 Selected for Development 0 +0 1 +1 4 +1 5 +2 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 +0 3 +2 0 -1 5 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 +0 10 +3 9 -1 31 +2 Total Software Ready for Testing OSG 3.5-upcoming XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing Discussion \u00b6 VO Package v114 should go out this week","title":"July 13, 2021"},{"location":"meetings/2021/TechArea20210713/#osg-technology-area-meeting-13-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, TimT","title":"OSG Technology Area Meeting, 13 July 2021"},{"location":"meetings/2021/TechArea20210713/#announcements","text":"Mat OOO Jul 9-14 BrianL OOO Friday","title":"Announcements"},{"location":"meetings/2021/TechArea20210713/#triage-duty","text":"This week: TimT Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210713/#jira-as-of-monday","text":"# of tickets \u0394 State 151 -1 Open 24 +0 Selected for Dev 40 +4 In Progress 11 +2 Dev Complete 7 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210713/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Kubernetes Hackathon Release AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Tag and build VO client","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210713/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210713/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210713/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210713/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210713/#osg-release-team","text":"3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 4 +0 14 +0 Open 1 +0 3 +0 1 -1 5 -1 Selected for Development 0 +0 1 +1 4 +1 5 +2 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 +0 3 +2 0 -1 5 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 +0 10 +3 9 -1 31 +2 Total Software Ready for Testing OSG 3.5-upcoming XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210713/#discussion_2","text":"VO Package v114 should go out this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210720/","text":"OSG Technology Area Meeting, 20 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Carl OOO Jul 26-30 Triage Duty \u00b6 This week: Mat Next week: BrianL (?) 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 147 -4 Open 27 +3 Selected for Dev 37 -3 In Progress 10 -1 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Fill out doc focus poll: https://terminplaner.dfn.de/RxlXW8dscNfMXaMx Release AI (Carl): Follow-up on Lincoln's gratia-probe stacktrace reported in #software AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Release gratia-probe 1.23.4+, 2.0.1+ AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Missing zero walltime records AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Give GlideinWMS team JIRA access. Discussion \u00b6 GlideinWMS 3.7 release candidate planned for tomorrow (7/21). Support Update \u00b6 (Derek) SIUE - Discovered bug in gratia probe, fixed locally and submitted upstream: https://github.com/opensciencegrid/gratia-probe/pull/107 BrianL: We are currently only sending LIGO jobs to Georgia Tech to avoid having OSG (and other VO) jobs run on LIGO pilots. Marian: Continuing to debug JLab submissions at Georgia Tech. Lamar (CLAS12) does not have any pilots or show any HTCondor activity. Finish setting up ICTS; it is registered in Topology so only the factory config needs to be updated. Mat: Lancium not seeing enough jobs again; Brian will investigate further. OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the typ rather than ver . (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 3 -1 13 -1 Open 2 +1 2 -1 1 +0 5 +0 Selected for Development 0 +0 2 +1 5 +1 7 +2 In Progress 0 +0 3 +1 0 +0 3 +1 Development Complete 3 +1 4 +1 0 +0 7 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 14 +2 12 +2 9 +0 35 +4 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.2 + blahp 2.1.0 XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing Discussion \u00b6 VO Package v114 should go out this week","title":"July 20, 2021"},{"location":"meetings/2021/TechArea20210720/#osg-technology-area-meeting-20-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 20 July 2021"},{"location":"meetings/2021/TechArea20210720/#announcements","text":"Carl OOO Jul 26-30","title":"Announcements"},{"location":"meetings/2021/TechArea20210720/#triage-duty","text":"This week: Mat Next week: BrianL (?) 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210720/#jira-as-of-monday","text":"# of tickets \u0394 State 147 -4 Open 27 +3 Selected for Dev 37 -3 In Progress 10 -1 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210720/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Fill out doc focus poll: https://terminplaner.dfn.de/RxlXW8dscNfMXaMx Release AI (Carl): Follow-up on Lincoln's gratia-probe stacktrace reported in #software AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Release gratia-probe 1.23.4+, 2.0.1+ AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Missing zero walltime records AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Give GlideinWMS team JIRA access.","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210720/#discussion","text":"GlideinWMS 3.7 release candidate planned for tomorrow (7/21).","title":"Discussion"},{"location":"meetings/2021/TechArea20210720/#support-update","text":"(Derek) SIUE - Discovered bug in gratia probe, fixed locally and submitted upstream: https://github.com/opensciencegrid/gratia-probe/pull/107 BrianL: We are currently only sending LIGO jobs to Georgia Tech to avoid having OSG (and other VO) jobs run on LIGO pilots. Marian: Continuing to debug JLab submissions at Georgia Tech. Lamar (CLAS12) does not have any pilots or show any HTCondor activity. Finish setting up ICTS; it is registered in Topology so only the factory config needs to be updated. Mat: Lancium not seeing enough jobs again; Brian will investigate further.","title":"Support Update"},{"location":"meetings/2021/TechArea20210720/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the typ rather than ver . (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210720/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210720/#osg-release-team","text":"3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 3 -1 13 -1 Open 2 +1 2 -1 1 +0 5 +0 Selected for Development 0 +0 2 +1 5 +1 7 +2 In Progress 0 +0 3 +1 0 +0 3 +1 Development Complete 3 +1 4 +1 0 +0 7 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 14 +2 12 +2 9 +0 35 +4 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.2 + blahp 2.1.0 XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210720/#discussion_2","text":"VO Package v114 should go out this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210727/","text":"OSG Technology Area Meeting, 27 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT Announcements \u00b6 Carl OOO Jul 26-30 Party at Tim's house with three racks of ribs Triage Duty \u00b6 This week: BrianL Next week: Carl 6 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 148 +1 Open 25 -2 Selected for Dev 36 -1 In Progress 12 +2 Dev Complete 3 -4 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Verify that HTCondor got updated on the OS registry AT (BrianL): Create ticket for pushing to OSG Hub as well as Docker Hub in automated builds Discussion \u00b6 GlideinWMS release candidate expected later this week SSH to tiger cluster head node only available from select CHTC hosts; kubectl access has not been changed Support Update \u00b6 None this week OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.42 and OSG 3.6 (today) HTCondor Security Release 8.8.14, 9.0.3, 9.1.1 OSG 3.5.43 and OSG 3.6 (Thursday) Ready for Testing OSG 3.5 and 3.6 gratia-probe 1.24.0 Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 Discussion \u00b6 None this week","title":"July 27, 2021"},{"location":"meetings/2021/TechArea20210727/#osg-technology-area-meeting-27-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 27 July 2021"},{"location":"meetings/2021/TechArea20210727/#announcements","text":"Carl OOO Jul 26-30 Party at Tim's house with three racks of ribs","title":"Announcements"},{"location":"meetings/2021/TechArea20210727/#triage-duty","text":"This week: BrianL Next week: Carl 6 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210727/#jira-as-of-monday","text":"# of tickets \u0394 State 148 +1 Open 25 -2 Selected for Dev 36 -1 In Progress 12 +2 Dev Complete 3 -4 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210727/#osg-software-team","text":"Kubernetes Hackathon this afternoon Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Verify that HTCondor got updated on the OS registry AT (BrianL): Create ticket for pushing to OSG Hub as well as Docker Hub in automated builds","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210727/#discussion","text":"GlideinWMS release candidate expected later this week SSH to tiger cluster head node only available from select CHTC hosts; kubectl access has not been changed","title":"Discussion"},{"location":"meetings/2021/TechArea20210727/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210727/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210727/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210727/#osg-release-team","text":"OSG 3.5.42 and OSG 3.6 (today) HTCondor Security Release 8.8.14, 9.0.3, 9.1.1 OSG 3.5.43 and OSG 3.6 (Thursday) Ready for Testing OSG 3.5 and 3.6 gratia-probe 1.24.0 Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210727/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210803/","text":"OSG Technology Area Meeting, 3 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 7 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 153 +5 Open 26 +1 Selected for Dev 39 +3 In Progress 11 -1 Dev Complete 3 +0 Ready for Testing 5 +2 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens credmon? AI (Carl): Move Gratia sub-tickets into RFT AI (Carl): Improve default ProbeConfig directory configuration GSI Transition AI (Carl): Directly query OSG COManage's LDAP for OSGID (SOFTWARE-4528) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) OSG VO Backfill Containers AI (Mat): Add support for limiting resources available to the osgvo-docker-pilot (SOFTWARE-4634) AI (BrianL): Add CI tests Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies Discussion \u00b6 GlideinWMS 3.7.5 still in progress; release candidate expected today/tomorrow; rc will contain cvmfsexec support Support Update \u00b6 Georgia Tech (BrianL): Gave them some AP HTCondor config that should prevent pilots from flocking out to pilots Lancium (BrianL, Mats): live backfill container debugging session that uncovered issues in the periodic health check not properly detecting unpriv Singularity. Multiple (Derek): Several sites had failed gratia probes over the last week. All isolated events, but I think there were 4 at the same time. OSG DevOps \u00b6 Elasticsearch will need to be updated. Working on a schedule. StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 50% done. Design document is still not reviewed, but moving foward anyways. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming) Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 Discussion \u00b6 None this week","title":"August 3, 2021"},{"location":"meetings/2021/TechArea20210803/#osg-technology-area-meeting-3-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 3 August 2021"},{"location":"meetings/2021/TechArea20210803/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210803/#triage-duty","text":"This week: Carl Next week: Mat 7 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210803/#jira-as-of-monday","text":"# of tickets \u0394 State 153 +5 Open 26 +1 Selected for Dev 39 +3 In Progress 11 -1 Dev Complete 3 +0 Ready for Testing 5 +2 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210803/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens credmon? AI (Carl): Move Gratia sub-tickets into RFT AI (Carl): Improve default ProbeConfig directory configuration GSI Transition AI (Carl): Directly query OSG COManage's LDAP for OSGID (SOFTWARE-4528) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) OSG VO Backfill Containers AI (Mat): Add support for limiting resources available to the osgvo-docker-pilot (SOFTWARE-4634) AI (BrianL): Add CI tests Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210803/#discussion","text":"GlideinWMS 3.7.5 still in progress; release candidate expected today/tomorrow; rc will contain cvmfsexec support","title":"Discussion"},{"location":"meetings/2021/TechArea20210803/#support-update","text":"Georgia Tech (BrianL): Gave them some AP HTCondor config that should prevent pilots from flocking out to pilots Lancium (BrianL, Mats): live backfill container debugging session that uncovered issues in the periodic health check not properly detecting unpriv Singularity. Multiple (Derek): Several sites had failed gratia probes over the last week. All isolated events, but I think there were 4 at the same time.","title":"Support Update"},{"location":"meetings/2021/TechArea20210803/#osg-devops","text":"Elasticsearch will need to be updated. Working on a schedule. StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 50% done. Design document is still not reviewed, but moving foward anyways. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210803/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210803/#osg-release-team","text":"Ready for Testing gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming) Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210803/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210810/","text":"OSG Technology Area Meeting, 10 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT Announcements \u00b6 OSG User School in session until the end of the week Triage Duty \u00b6 This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 155 +2 Open 26 +0 Selected for Dev 39 +0 In Progress 6 -5 Dev Complete 8 +3 Ready for Testing 6 +1 Ready for Release OSG Software Team \u00b6 Kuberentes Hackathon today 1-5pm Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens update for EL8 (SOFTWARE-4126) AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add CI tests Discussion \u00b6 GRACC upgrade is planned for the end of August Support Update \u00b6 Georgia Tech (BrianL, Mats): Need to verify that the config worked to prevent pilots from running in pilots Lancium (BrianL, Mats): their GPUs are still going unused, it seems that RecentJobStarts is frequently at its limit of 400 starts/20 min JLab (Marian): Fixed HTCondor configuration; JLab admins should be informed to expect some downtime and manual changes between OSG release series upgrades Lamar (Marian): Jobs are running but requesting Software Team help to examine job classads for anything unexpected BNL (Marian): Troubleshooting with John de Stefano and other BNL admins; getting unexpected behavior from Freshdesk with notes or replies not getting to everyone on the ticket. Marian will notify Freshdesk support about the strange behavior. Hosted CEs (Carl): Investigate hosted-ce35 not reporting to GRACC. University of Illinois (Mat): Undesired XRootD HTTP plugin behavior; Mat is following discussion between XRootD developers OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 80% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.45 and OSG 3.6 (Thursday) Ready for Release gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming) Discussion \u00b6 None this week","title":"August 10, 2021"},{"location":"meetings/2021/TechArea20210810/#osg-technology-area-meeting-10-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 10 August 2021"},{"location":"meetings/2021/TechArea20210810/#announcements","text":"OSG User School in session until the end of the week","title":"Announcements"},{"location":"meetings/2021/TechArea20210810/#triage-duty","text":"This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210810/#jira-as-of-monday","text":"# of tickets \u0394 State 155 +2 Open 26 +0 Selected for Dev 39 +0 In Progress 6 -5 Dev Complete 8 +3 Ready for Testing 6 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210810/#osg-software-team","text":"Kuberentes Hackathon today 1-5pm Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens update for EL8 (SOFTWARE-4126) AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add CI tests","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210810/#discussion","text":"GRACC upgrade is planned for the end of August","title":"Discussion"},{"location":"meetings/2021/TechArea20210810/#support-update","text":"Georgia Tech (BrianL, Mats): Need to verify that the config worked to prevent pilots from running in pilots Lancium (BrianL, Mats): their GPUs are still going unused, it seems that RecentJobStarts is frequently at its limit of 400 starts/20 min JLab (Marian): Fixed HTCondor configuration; JLab admins should be informed to expect some downtime and manual changes between OSG release series upgrades Lamar (Marian): Jobs are running but requesting Software Team help to examine job classads for anything unexpected BNL (Marian): Troubleshooting with John de Stefano and other BNL admins; getting unexpected behavior from Freshdesk with notes or replies not getting to everyone on the ticket. Marian will notify Freshdesk support about the strange behavior. Hosted CEs (Carl): Investigate hosted-ce35 not reporting to GRACC. University of Illinois (Mat): Undesired XRootD HTTP plugin behavior; Mat is following discussion between XRootD developers","title":"Support Update"},{"location":"meetings/2021/TechArea20210810/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 80% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210810/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210810/#osg-release-team","text":"OSG 3.5.45 and OSG 3.6 (Thursday) Ready for Release gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming)","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210810/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210817/","text":"OSG Technology Area Meeting, 17 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: BrianL? 13 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 156 +1 Open 26 +0 Selected for Dev 39 +0 In Progress 9 +3 Dev Complete 0 -8 Ready for Testing 0 -6 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Planning to add a \"doc pending\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL, Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add backfill container CI tests Discussion \u00b6 GRACC upgrade is planned for the end of August Diego noticed some condor_mapfile entries weren't matching if the incoming cert had both commas and VOMS attributes. There's a regex recipe that fixes it, which needs to be documented (HTCONDOR-651) Support Update \u00b6 Brown (BrianL): authN failures with their GridFTP + XRootD setup Caltech (BrianL): investigated 8.8.15 stacktrace LIGO-WA & LIGO-LA (Carl): invstigating missing probes in the payload summary page GlideinWMS (Marco): removed the code section in the user job wrapper that tried to add condor_chirp; will be replaced with a Python version 3.7 release candidate still in progress OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.45-2 and OSG 3.6 (2021-08-16) CA Certificates based on IGTF 1.112 OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 None this week","title":"August 17, 2021"},{"location":"meetings/2021/TechArea20210817/#osg-technology-area-meeting-17-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 17 August 2021"},{"location":"meetings/2021/TechArea20210817/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210817/#triage-duty","text":"This week: TimT Next week: BrianL? 13 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210817/#jira-as-of-monday","text":"# of tickets \u0394 State 156 +1 Open 26 +0 Selected for Dev 39 +0 In Progress 9 +3 Dev Complete 0 -8 Ready for Testing 0 -6 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210817/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Planning to add a \"doc pending\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL, Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add backfill container CI tests","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210817/#discussion","text":"GRACC upgrade is planned for the end of August Diego noticed some condor_mapfile entries weren't matching if the incoming cert had both commas and VOMS attributes. There's a regex recipe that fixes it, which needs to be documented (HTCONDOR-651)","title":"Discussion"},{"location":"meetings/2021/TechArea20210817/#support-update","text":"Brown (BrianL): authN failures with their GridFTP + XRootD setup Caltech (BrianL): investigated 8.8.15 stacktrace LIGO-WA & LIGO-LA (Carl): invstigating missing probes in the payload summary page GlideinWMS (Marco): removed the code section in the user job wrapper that tried to add condor_chirp; will be replaced with a Python version 3.7 release candidate still in progress","title":"Support Update"},{"location":"meetings/2021/TechArea20210817/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210817/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210817/#osg-release-team","text":"OSG 3.5.45-2 and OSG 3.6 (2021-08-16) CA Certificates based on IGTF 1.112 OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210817/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210824/","text":"OSG Technology Area Meeting, 24 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim Announcements \u00b6 Carl OOO Wed-Thu TimT OOO Fri afternoon Triage Duty \u00b6 This week: BrianL Next week: Carl 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 156 +0 Open 35 +9 Selected for Dev 38 -1 In Progress 10 +1 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (BrianL): Review the osg-token-renewer package AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Other AI (BrianL): Add backfill container CI tests AI (TimT): Release HTCondor 9.1.4; add a fix/patch for proxy delegation Discussion \u00b6 None this week Support Update \u00b6 Colorado (BrianL): OSG-issued IGTF certs won't work because their IT won't issue a PTR pointing to the OSG domain Brown (Derek): Supporting XRootD configuration. Using standalone config, but also copied from other server that was working before. Old LCMaps configuration. Caltech (Derek)/LIGO (Carl): Debugging accounting information not showing up in the GRACC or in Gratia logs. (These are two separate tickets for the same issue; BrianL will merge them) UERJ (Carl): Provided support for tuning GridFTP configuration Hosted CEs (Carl): Hosted CEs failed to quarantine history files because the Gratia probes run as the 'condor' user and do not have write permission to the quarantine directory. This results in zero-length jobs not being reported to GRACC OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - StashCP Go client is now being used and distributed with every OSPool Glidein! Being used in the stash:/// transfer plugin and starting to be used by Mats on his singularity image distribution. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 HTCondor 9.0.5, HTCondor 9.1.3, and blahp 2.1.1 should be ready for testing today Proxy delegation problem with mixed versions in HTCondor 9.1.3","title":"August 24, 2021"},{"location":"meetings/2021/TechArea20210824/#osg-technology-area-meeting-24-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim","title":"OSG Technology Area Meeting, 24 August 2021"},{"location":"meetings/2021/TechArea20210824/#announcements","text":"Carl OOO Wed-Thu TimT OOO Fri afternoon","title":"Announcements"},{"location":"meetings/2021/TechArea20210824/#triage-duty","text":"This week: BrianL Next week: Carl 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210824/#jira-as-of-monday","text":"# of tickets \u0394 State 156 +0 Open 35 +9 Selected for Dev 38 -1 In Progress 10 +1 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210824/#osg-software-team","text":"Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (BrianL): Review the osg-token-renewer package AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Other AI (BrianL): Add backfill container CI tests AI (TimT): Release HTCondor 9.1.4; add a fix/patch for proxy delegation","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210824/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210824/#support-update","text":"Colorado (BrianL): OSG-issued IGTF certs won't work because their IT won't issue a PTR pointing to the OSG domain Brown (Derek): Supporting XRootD configuration. Using standalone config, but also copied from other server that was working before. Old LCMaps configuration. Caltech (Derek)/LIGO (Carl): Debugging accounting information not showing up in the GRACC or in Gratia logs. (These are two separate tickets for the same issue; BrianL will merge them) UERJ (Carl): Provided support for tuning GridFTP configuration Hosted CEs (Carl): Hosted CEs failed to quarantine history files because the Gratia probes run as the 'condor' user and do not have write permission to the quarantine directory. This results in zero-length jobs not being reported to GRACC","title":"Support Update"},{"location":"meetings/2021/TechArea20210824/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - StashCP Go client is now being used and distributed with every OSPool Glidein! Being used in the stash:/// transfer plugin and starting to be used by Mats on his singularity image distribution. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210824/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210824/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210824/#discussion_2","text":"HTCondor 9.0.5, HTCondor 9.1.3, and blahp 2.1.1 should be ready for testing today Proxy delegation problem with mixed versions in HTCondor 9.1.3","title":"Discussion"},{"location":"meetings/2021/TechArea20210831/","text":"OSG Technology Area Meeting, 31 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim Announcements \u00b6 CE Token Hackathon 1-5pm today Triage Duty \u00b6 This week: Carl Next week: Mat 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 162 +6 Open 34 -1 Selected for Dev 41 +3 In Progress 9 -1 Dev Complete 5 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Address osg-token-renewer review comments AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Add backfill container CI tests AI (Carl, Mat): Review OS Pool AP Topology PR Discussion \u00b6 Mat and Marco should attend CE hackathon today; frontend admins should consider briefly joining. Marco investigating an incompatibility between a 3.6.5 factory (used at FNAL) and newer frontends. Support Update \u00b6 Marian: Singularity issues at Utah. Should assign ticket to Mats Rynge and add Mat as a watcher. HTCondor not properly handling CNAMEs in the IGWN central manager. Admins should create an A record for now, but BrianB will ask the HTCondor developers to address the issue. Carl: Waiting for response from LIGO about their accounting issue. No follow-up yet from HTCondor devs for DUNE/TIFR. Carl will examine the schedd log for any clues. Mat: Helping Andrew Melo with an overloaded schedd; HTCondor developers have joined the conversation. Greg Daues at U Illinois hasn't responded regarding minor XRootD security issue they found. Fix expected in XRootD 5.4.0; since it's security-related, it will also go into OSG 3.5-upcoming. OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Elasticsearch is being from 7.10.2 to 7.14.1. Some downtime expected, but only momentarily. No gratia probes or clients should notice. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 70% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing Discussion \u00b6 None this week","title":"August 31, 2021"},{"location":"meetings/2021/TechArea20210831/#osg-technology-area-meeting-31-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim","title":"OSG Technology Area Meeting, 31 August 2021"},{"location":"meetings/2021/TechArea20210831/#announcements","text":"CE Token Hackathon 1-5pm today","title":"Announcements"},{"location":"meetings/2021/TechArea20210831/#triage-duty","text":"This week: Carl Next week: Mat 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210831/#jira-as-of-monday","text":"# of tickets \u0394 State 162 +6 Open 34 -1 Selected for Dev 41 +3 In Progress 9 -1 Dev Complete 5 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210831/#osg-software-team","text":"Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Address osg-token-renewer review comments AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Add backfill container CI tests AI (Carl, Mat): Review OS Pool AP Topology PR","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210831/#discussion","text":"Mat and Marco should attend CE hackathon today; frontend admins should consider briefly joining. Marco investigating an incompatibility between a 3.6.5 factory (used at FNAL) and newer frontends.","title":"Discussion"},{"location":"meetings/2021/TechArea20210831/#support-update","text":"Marian: Singularity issues at Utah. Should assign ticket to Mats Rynge and add Mat as a watcher. HTCondor not properly handling CNAMEs in the IGWN central manager. Admins should create an A record for now, but BrianB will ask the HTCondor developers to address the issue. Carl: Waiting for response from LIGO about their accounting issue. No follow-up yet from HTCondor devs for DUNE/TIFR. Carl will examine the schedd log for any clues. Mat: Helping Andrew Melo with an overloaded schedd; HTCondor developers have joined the conversation. Greg Daues at U Illinois hasn't responded regarding minor XRootD security issue they found. Fix expected in XRootD 5.4.0; since it's security-related, it will also go into OSG 3.5-upcoming.","title":"Support Update"},{"location":"meetings/2021/TechArea20210831/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Elasticsearch is being from 7.10.2 to 7.14.1. Some downtime expected, but only momentarily. No gratia probes or clients should notice. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 70% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210831/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210831/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210831/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210907/","text":"OSG Technology Area Meeting, 7 September 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Mat, Tim Announcements \u00b6 Kubernetes Hackathon 1-5pm today Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 163 +1 Open 32 -2 Selected for Dev 37 -4 In Progress 14 +5 Dev Complete 4 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat): Kick off GlideinWMS 3.7.5 VMU tests GSI Transition AI (Carl): Address osg-token-renewer review comments Other AI (BrianL): Add backfill container CI tests AI (BrianL): add SSH certificate to the Hosted CE Discussion \u00b6 A longer term project for Carl is to enable mass token requests so Harvester folks can make a token per CE. Support Update \u00b6 Lancium (BrianL): backfill containers with bind-mounted CVMFS weren't getting jobs because they did not specify shared to the bind mount OSG DevOps \u00b6 New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing Discussion \u00b6 None this week","title":"September 7, 2021"},{"location":"meetings/2021/TechArea20210907/#osg-technology-area-meeting-7-september-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Mat, Tim","title":"OSG Technology Area Meeting, 7 September 2021"},{"location":"meetings/2021/TechArea20210907/#announcements","text":"Kubernetes Hackathon 1-5pm today","title":"Announcements"},{"location":"meetings/2021/TechArea20210907/#triage-duty","text":"This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210907/#jira-as-of-monday","text":"# of tickets \u0394 State 163 +1 Open 32 -2 Selected for Dev 37 -4 In Progress 14 +5 Dev Complete 4 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210907/#osg-software-team","text":"Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat): Kick off GlideinWMS 3.7.5 VMU tests GSI Transition AI (Carl): Address osg-token-renewer review comments Other AI (BrianL): Add backfill container CI tests AI (BrianL): add SSH certificate to the Hosted CE","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210907/#discussion","text":"A longer term project for Carl is to enable mass token requests so Harvester folks can make a token per CE.","title":"Discussion"},{"location":"meetings/2021/TechArea20210907/#support-update","text":"Lancium (BrianL): backfill containers with bind-mounted CVMFS weren't getting jobs because they did not specify shared to the bind mount","title":"Support Update"},{"location":"meetings/2021/TechArea20210907/#osg-devops","text":"New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210907/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210907/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210907/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210914/","text":"OSG Technology Area Meeting, 14 September 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat Announcements \u00b6 Canceling next week's meeting due to HTCondor Week Mat OOO Sep 17-22 Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 10 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 162 -1 Open 33 +1 Selected for Dev 32 -5 In Progress 13 -1 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Review osg-token-renewer doc and merge if satisfied Other AI (BrianL): Add SSH certificate to the Hosted CE AI (BrianL): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (BrianL): Investigate host cert on the CMS Hosted CE at Frontera to see if UW needs to renew it Discussion \u00b6 GlideinWMS 3.9.3rc1 available; will be built into 3.5-contrib; requesting a build for 3.6 as well. GSI not completely removed yet but that's acceptable because it will help with the transition FNAL and CERN expected to announce EL8 plans in October Support Update \u00b6 Florida (BrianL): uncovered a few bugs with job router transforms in HTCondor-CE 5.1.1. To be fixed in 5.1.2 in an expected upstream release this week. Marian: add Andrew Melo back as an OASIS manager; contact Mat if Topology assistance is needed Mat: Assist Vlad at IceCube with permissions problems at their new Stash Origin; contact Derek for assistance as needed Carl: LIGO fixed their ProbeConfig and some records started showing up. LIGO-WA-CalTech records are sparse; Carl will ask LIGO if this is expected OSG DevOps \u00b6 New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing GlideinWMS 3.7.5 cvmfs-x509-helper 2.2-2 and osg-oasis 17-4 Ready for Release Nothing Discussion \u00b6 None this week","title":"September 14, 2021"},{"location":"meetings/2021/TechArea20210914/#osg-technology-area-meeting-14-september-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat","title":"OSG Technology Area Meeting, 14 September 2021"},{"location":"meetings/2021/TechArea20210914/#announcements","text":"Canceling next week's meeting due to HTCondor Week Mat OOO Sep 17-22","title":"Announcements"},{"location":"meetings/2021/TechArea20210914/#triage-duty","text":"This week: TimT Next week: BrianL (?) 10 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210914/#jira-as-of-monday","text":"# of tickets \u0394 State 162 -1 Open 33 +1 Selected for Dev 32 -5 In Progress 13 -1 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210914/#osg-software-team","text":"Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Review osg-token-renewer doc and merge if satisfied Other AI (BrianL): Add SSH certificate to the Hosted CE AI (BrianL): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (BrianL): Investigate host cert on the CMS Hosted CE at Frontera to see if UW needs to renew it","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210914/#discussion","text":"GlideinWMS 3.9.3rc1 available; will be built into 3.5-contrib; requesting a build for 3.6 as well. GSI not completely removed yet but that's acceptable because it will help with the transition FNAL and CERN expected to announce EL8 plans in October","title":"Discussion"},{"location":"meetings/2021/TechArea20210914/#support-update","text":"Florida (BrianL): uncovered a few bugs with job router transforms in HTCondor-CE 5.1.1. To be fixed in 5.1.2 in an expected upstream release this week. Marian: add Andrew Melo back as an OASIS manager; contact Mat if Topology assistance is needed Mat: Assist Vlad at IceCube with permissions problems at their new Stash Origin; contact Derek for assistance as needed Carl: LIGO fixed their ProbeConfig and some records started showing up. LIGO-WA-CalTech records are sparse; Carl will ask LIGO if this is expected","title":"Support Update"},{"location":"meetings/2021/TechArea20210914/#osg-devops","text":"New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210914/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210914/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing GlideinWMS 3.7.5 cvmfs-x509-helper 2.2-2 and osg-oasis 17-4 Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210914/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210928/","text":"OSG Technology Area Meeting, 28 September 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Brian OOO Wed-Fri Carl OOO Wed Triage Duty \u00b6 This week: Mat Next week: Carl 12 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 164 +2 Open 33 +0 Selected for Dev 37 +5 In Progress 14 +1 Dev Complete 10 +6 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) GSI/GridFTP Transition AI (Carl): Address osg-token-renewer doc comments and merge Wei asked us to improve the XRootD standalone docs with info about Third-Party-Copy Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (Carl): Merge Topology and CILogon contact data Discussion \u00b6 None this week Support Update \u00b6 Lancium (BrianL): for Singularity-in-Singularity, GPUs aren't made available if the outer Singularity is < 3.8.0. On the plus side, GPUs work for unpriv Singularity in unpriv Singularity OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Stashcp changes to support authenticated reading from /ospool namespace is done and lightly tested. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5 and OSG 3.6: CVMFS 2.8.2 cvmfs-x509-helper 2.2-2, osg-oasis 17-4 vault 1.8.2, htvault-config 1.6, and htgettoken 1.6 OSG 3.5-upcoming: GlideinWMS 3.7.5 xrootd-multiuser-2.0.2 OSG 3.5-upcoming and OSG 3.6: HTCondor 9.0.6 blahp 2.1.2 OSG 3.6-upcoming HTCondor 9.2.0 Ready for Release OSG 3.5 and OSG 3.6 osg-wn-client Discussion \u00b6 None this week","title":"September 28, 2021"},{"location":"meetings/2021/TechArea20210928/#osg-technology-area-meeting-28-september-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 28 September 2021"},{"location":"meetings/2021/TechArea20210928/#announcements","text":"Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Brian OOO Wed-Fri Carl OOO Wed","title":"Announcements"},{"location":"meetings/2021/TechArea20210928/#triage-duty","text":"This week: Mat Next week: Carl 12 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210928/#jira-as-of-monday","text":"# of tickets \u0394 State 164 +2 Open 33 +0 Selected for Dev 37 +5 In Progress 14 +1 Dev Complete 10 +6 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210928/#osg-software-team","text":"Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) GSI/GridFTP Transition AI (Carl): Address osg-token-renewer doc comments and merge Wei asked us to improve the XRootD standalone docs with info about Third-Party-Copy Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (Carl): Merge Topology and CILogon contact data","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210928/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210928/#support-update","text":"Lancium (BrianL): for Singularity-in-Singularity, GPUs aren't made available if the outer Singularity is < 3.8.0. On the plus side, GPUs work for unpriv Singularity in unpriv Singularity","title":"Support Update"},{"location":"meetings/2021/TechArea20210928/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Stashcp changes to support authenticated reading from /ospool namespace is done and lightly tested. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210928/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210928/#osg-release-team","text":"Ready for Testing OSG 3.5 and OSG 3.6: CVMFS 2.8.2 cvmfs-x509-helper 2.2-2, osg-oasis 17-4 vault 1.8.2, htvault-config 1.6, and htgettoken 1.6 OSG 3.5-upcoming: GlideinWMS 3.7.5 xrootd-multiuser-2.0.2 OSG 3.5-upcoming and OSG 3.6: HTCondor 9.0.6 blahp 2.1.2 OSG 3.6-upcoming HTCondor 9.2.0 Ready for Release OSG 3.5 and OSG 3.6 osg-wn-client","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210928/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211005/","text":"OSG Technology Area Meeting, 5 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Triage Duty \u00b6 This week: Carl Next week: TimT 12 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 168 +4 Open 34 +1 Selected for Dev 37 +0 In Progress 12 -2 Dev Complete 5 -5 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon Doc focus this Friday October 8, 1-5pm Release AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Singularity backfill container CI tests (SOFTWARE-4726) AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL/HTCondor developers): Make internal documentation for how to add SciTokens to a CE in preparation for the token workshop AI (Mat): Review remaining issues for the Let's Encrypt CA expiration fire. Discussion \u00b6 Marco: Debugging glideinWMS compatibility issues with HTCondor 9.0.6; attempting to install 9.0.1 for testing but having dependency issues. Brian says that it's a frequent issue when trying to install old versions of HTCondor on EL7. Mat suggests trying the HTCondor Docker images if a 9.0.1 version is available. Support Update \u00b6 TimT: Justas (Caltech) is requesting additional GPU attributes in the job classad; Tim will link him up with one of the HTCondor developers directly. Carl: There is no easy upgrade path to the Python 3 version of gfal2-util due to RPM dependency issues; filed a ticket with EPEL, will try to contact developers directly if there's no response to the ticket. Marian: Continuing to support LIGO with using IDTOKEN authentication. OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming and OSG 3.6 blahp 2.1.2 Ready for Release OSG 3.5 and OSG 3.6 IGTF 1.113 Discussion \u00b6 None this week","title":"October 5, 2021"},{"location":"meetings/2021/TechArea20211005/#osg-technology-area-meeting-5-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 5 October 2021"},{"location":"meetings/2021/TechArea20211005/#announcements","text":"Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/","title":"Announcements"},{"location":"meetings/2021/TechArea20211005/#triage-duty","text":"This week: Carl Next week: TimT 12 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211005/#jira-as-of-monday","text":"# of tickets \u0394 State 168 +4 Open 34 +1 Selected for Dev 37 +0 In Progress 12 -2 Dev Complete 5 -5 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211005/#osg-software-team","text":"Kubernetes Hackathon this afternoon Doc focus this Friday October 8, 1-5pm Release AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Singularity backfill container CI tests (SOFTWARE-4726) AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL/HTCondor developers): Make internal documentation for how to add SciTokens to a CE in preparation for the token workshop AI (Mat): Review remaining issues for the Let's Encrypt CA expiration fire.","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211005/#discussion","text":"Marco: Debugging glideinWMS compatibility issues with HTCondor 9.0.6; attempting to install 9.0.1 for testing but having dependency issues. Brian says that it's a frequent issue when trying to install old versions of HTCondor on EL7. Mat suggests trying the HTCondor Docker images if a 9.0.1 version is available.","title":"Discussion"},{"location":"meetings/2021/TechArea20211005/#support-update","text":"TimT: Justas (Caltech) is requesting additional GPU attributes in the job classad; Tim will link him up with one of the HTCondor developers directly. Carl: There is no easy upgrade path to the Python 3 version of gfal2-util due to RPM dependency issues; filed a ticket with EPEL, will try to contact developers directly if there's no response to the ticket. Marian: Continuing to support LIGO with using IDTOKEN authentication.","title":"Support Update"},{"location":"meetings/2021/TechArea20211005/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211005/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211005/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming and OSG 3.6 blahp 2.1.2 Ready for Release OSG 3.5 and OSG 3.6 IGTF 1.113","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211005/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211012/","text":"OSG Technology Area Meeting, 12 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT Announcements \u00b6 Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 11 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 159 -9 Open 37 +3 Selected for Dev 40 +3 In Progress 12 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs Discussion \u00b6 None this week Support Update \u00b6 GP-ARGO (BrianL): Helped register them in Topology and get a backfill container started up. The container remains idle. (Derek) GRACC redirects broken. Fixed, but reminded Horst that redirects are not guarenteed forever! OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - stashcp feature request for better error messages. Added, waiting on some iterative feedback. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5 and OSG 3.6 osg-token-renewer 0.7.1 Ready for Release OSG 3.5-upcoming and OSG 3.6 blahp 2.1.3 Discussion \u00b6 None this week","title":"October 12, 2021"},{"location":"meetings/2021/TechArea20211012/#osg-technology-area-meeting-12-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 12 October 2021"},{"location":"meetings/2021/TechArea20211012/#announcements","text":"Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/","title":"Announcements"},{"location":"meetings/2021/TechArea20211012/#triage-duty","text":"This week: TimT Next week: BrianL (?) 11 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211012/#jira-as-of-monday","text":"# of tickets \u0394 State 159 -9 Open 37 +3 Selected for Dev 40 +3 In Progress 12 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211012/#osg-software-team","text":"Release AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211012/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211012/#support-update","text":"GP-ARGO (BrianL): Helped register them in Topology and get a backfill container started up. The container remains idle. (Derek) GRACC redirects broken. Fixed, but reminded Horst that redirects are not guarenteed forever!","title":"Support Update"},{"location":"meetings/2021/TechArea20211012/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - stashcp feature request for better error messages. Added, waiting on some iterative feedback. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211012/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211012/#osg-release-team","text":"Ready for Testing OSG 3.5 and OSG 3.6 osg-token-renewer 0.7.1 Ready for Release OSG 3.5-upcoming and OSG 3.6 blahp 2.1.3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211012/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211019/","text":"OSG Technology Area Meeting, 19 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL OOO Friday Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +1 Open 41 +4 Selected for Dev 38 -2 In Progress 11 -1 Dev Complete 0 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl, BrianL): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs Discussion \u00b6 HTCondor team planning to merge the BLAHP into the HTCondor source tree and build their packages together; this will eliminate the circular dependency between their packages. Support Update \u00b6 Token Transition Workshop (BrianL, Mat): many sites needed to adjust their AUTH_SSL_* CE config variables to continue to support IGTF CAs; also needed to update to scitokens-cpp-0.6.2 . HTCondor packaging will be updated upstream to require the latter. OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 None this week","title":"October 19, 2021"},{"location":"meetings/2021/TechArea20211019/#osg-technology-area-meeting-19-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 19 October 2021"},{"location":"meetings/2021/TechArea20211019/#announcements","text":"BrianL OOO Friday","title":"Announcements"},{"location":"meetings/2021/TechArea20211019/#triage-duty","text":"This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211019/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +1 Open 41 +4 Selected for Dev 38 -2 In Progress 11 -1 Dev Complete 0 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211019/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl, BrianL): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211019/#discussion","text":"HTCondor team planning to merge the BLAHP into the HTCondor source tree and build their packages together; this will eliminate the circular dependency between their packages.","title":"Discussion"},{"location":"meetings/2021/TechArea20211019/#support-update","text":"Token Transition Workshop (BrianL, Mat): many sites needed to adjust their AUTH_SSL_* CE config variables to continue to support IGTF CAs; also needed to update to scitokens-cpp-0.6.2 . HTCondor packaging will be updated upstream to require the latter.","title":"Support Update"},{"location":"meetings/2021/TechArea20211019/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211019/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211019/#osg-release-team","text":"Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211019/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211026/","text":"OSG Technology Area Meeting, 26 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, Marco Mambelli Announcements \u00b6 None this week Triage Duty \u00b6 This week: Mat Next week: Carl 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 164 +4 Open 42 +1 Selected for Dev 38 +0 In Progress 11 +0 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review gratia-probe PRs AI (BrianL): build gratia-probe and osg-flock for 3.6 Discussion \u00b6 There were some reports of user jobs failing in OSPool backfill containers due to insufficient storage space in /tmp . OSPool jobs almost always run inside Singularity containers and GlideinWMS has mechanisms that will decide what to mount from the host (in this case the backfill container), into /tmp inside the Singularity container: https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/glidein_startup.sh#L591 https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/singularity_lib.sh#L1639 It'd be worth checking to verify that the affected user jobs were running inside Singularity. Support Update \u00b6 None this week","title":"October 26, 2021"},{"location":"meetings/2021/TechArea20211026/#osg-technology-area-meeting-26-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, Marco Mambelli","title":"OSG Technology Area Meeting, 26 October 2021"},{"location":"meetings/2021/TechArea20211026/#announcements","text":"None this week","title":"Announcements"},{"location":"meetings/2021/TechArea20211026/#triage-duty","text":"This week: Mat Next week: Carl 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211026/#jira-as-of-monday","text":"# of tickets \u0394 State 164 +4 Open 42 +1 Selected for Dev 38 +0 In Progress 11 +0 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211026/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review gratia-probe PRs AI (BrianL): build gratia-probe and osg-flock for 3.6","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211026/#discussion","text":"There were some reports of user jobs failing in OSPool backfill containers due to insufficient storage space in /tmp . OSPool jobs almost always run inside Singularity containers and GlideinWMS has mechanisms that will decide what to mount from the host (in this case the backfill container), into /tmp inside the Singularity container: https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/glidein_startup.sh#L591 https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/singularity_lib.sh#L1639 It'd be worth checking to verify that the affected user jobs were running inside Singularity.","title":"Discussion"},{"location":"meetings/2021/TechArea20211026/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20211102/","text":"OSG Technology Area Meeting, 2 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +1 Open 40 -2 Selected for Dev 42 +4 In Progress 11 +0 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl, BrianL): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Discussion \u00b6 HTCondor 9.0.7 and 9.3.0 expected later today HTCondor credmon requires python-scitokens but it's currently shipped only in OSG repos, not EPEL, meaning it's not available for UW builds of HTCondor. TimT will decide if it's better to also ship python-scitokens in the HTCondor repos, or try and get it into EPEL. Support Update \u00b6 University of Colorado (BrianL): they were not receiving payload jobs, had them redeploy with updated containers and it appears that things are working ok now JLab (BrianL): help talk them through setting up a token issuer JLab (Marian): debugging why their new schedd does not show up in the VO Summary OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 None this week","title":"November 2, 2021"},{"location":"meetings/2021/TechArea20211102/#osg-technology-area-meeting-2-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 2 November 2021"},{"location":"meetings/2021/TechArea20211102/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20211102/#triage-duty","text":"This week: TimT Next week: BrianL (?) 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211102/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +1 Open 40 -2 Selected for Dev 42 +4 In Progress 11 +0 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211102/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl, BrianL): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211102/#discussion","text":"HTCondor 9.0.7 and 9.3.0 expected later today HTCondor credmon requires python-scitokens but it's currently shipped only in OSG repos, not EPEL, meaning it's not available for UW builds of HTCondor. TimT will decide if it's better to also ship python-scitokens in the HTCondor repos, or try and get it into EPEL.","title":"Discussion"},{"location":"meetings/2021/TechArea20211102/#support-update","text":"University of Colorado (BrianL): they were not receiving payload jobs, had them redeploy with updated containers and it appears that things are working ok now JLab (BrianL): help talk them through setting up a token issuer JLab (Marian): debugging why their new schedd does not show up in the VO Summary","title":"Support Update"},{"location":"meetings/2021/TechArea20211102/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211102/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211102/#osg-release-team","text":"Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211102/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211109/","text":"OSG Technology Area Meeting, 9 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT Announcements \u00b6 Doc focus this Friday (11/12) Marian leaving November 30 Triage Duty \u00b6 This week: BrianL Next week: Mat 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 161 +1 Open 39 -1 Selected for Dev 49 +7 In Progress 12 +1 Dev Complete 1 -6 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (BrianL): Release python-scitokens 1.6.0+ (SOFTWARE-4879) AI (Mat): Pegasus in OSG 3.6 (SOFTWARE-4877) AI (Mat): Release oidc-agent 4.2.2+ (SOFTWARE-4885) AI (Mat): kick off tests for vault/htvault/htgettoken (SOFTWARE-4884) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings Discussion \u00b6 GlideinWMS 3.9.3 is ready to go. Support Update \u00b6 Georgia State University (BrianL): followed up on their suggestion to use SSH ProxyCommand JLab (BrianL): had more discussions about setting up token issuers University of Southern California (BrianL): worked through issues requesting tokens for the backfill container and problems with startup University of Connecticut (Mat, Marian): modifying the namespaces that are exported in their Stash Origins. Mat provided XRootD configuration changes; Marian will take care of CVMFS syncing. JLab (Marian, BrianL): Updated certificate configuration in JLab frontend to avoid issues with the Let's Encrypt root certificate. NIKHEF (Marian): Helping update their HTCondor install; there is a large version jump so much config has to be adjusted. OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3 Discussion \u00b6 None this week","title":"November 9, 2021"},{"location":"meetings/2021/TechArea20211109/#osg-technology-area-meeting-9-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 9 November 2021"},{"location":"meetings/2021/TechArea20211109/#announcements","text":"Doc focus this Friday (11/12) Marian leaving November 30","title":"Announcements"},{"location":"meetings/2021/TechArea20211109/#triage-duty","text":"This week: BrianL Next week: Mat 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211109/#jira-as-of-monday","text":"# of tickets \u0394 State 161 +1 Open 39 -1 Selected for Dev 49 +7 In Progress 12 +1 Dev Complete 1 -6 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211109/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (BrianL): Release python-scitokens 1.6.0+ (SOFTWARE-4879) AI (Mat): Pegasus in OSG 3.6 (SOFTWARE-4877) AI (Mat): Release oidc-agent 4.2.2+ (SOFTWARE-4885) AI (Mat): kick off tests for vault/htvault/htgettoken (SOFTWARE-4884) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211109/#discussion","text":"GlideinWMS 3.9.3 is ready to go.","title":"Discussion"},{"location":"meetings/2021/TechArea20211109/#support-update","text":"Georgia State University (BrianL): followed up on their suggestion to use SSH ProxyCommand JLab (BrianL): had more discussions about setting up token issuers University of Southern California (BrianL): worked through issues requesting tokens for the backfill container and problems with startup University of Connecticut (Mat, Marian): modifying the namespaces that are exported in their Stash Origins. Mat provided XRootD configuration changes; Marian will take care of CVMFS syncing. JLab (Marian, BrianL): Updated certificate configuration in JLab frontend to avoid issues with the Let's Encrypt root certificate. NIKHEF (Marian): Helping update their HTCondor install; there is a large version jump so much config has to be adjusted.","title":"Support Update"},{"location":"meetings/2021/TechArea20211109/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211109/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211109/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211109/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211116/","text":"OSG Technology Area Meeting, 16 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 161 +0 Open 42 +3 Selected for Dev 39 -10 In Progress 9 -3 Dev Complete 11 +10 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Release AI (Mat): Release XRootD 5.3.3 in OSG 3.6 (SOFTWARE-4885) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): investigate HTCondor-CE failures in the nightlies (SOFTWARE-4901) Discussion \u00b6 None this week Support Update \u00b6 Georgia State University (BrianL): needed to add pre-populated known_hosts since ssh-keyscan doesn't work with jump hosts JLab (BrianL): had a meeting to discuss token issuers; they'll likely start with a local issuer for pilots and will consider CILogon as their issuer Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6 OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3 Discussion \u00b6 None this week","title":"November 16, 2021"},{"location":"meetings/2021/TechArea20211116/#osg-technology-area-meeting-16-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT","title":"OSG Technology Area Meeting, 16 November 2021"},{"location":"meetings/2021/TechArea20211116/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20211116/#triage-duty","text":"This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211116/#jira-as-of-monday","text":"# of tickets \u0394 State 161 +0 Open 42 +3 Selected for Dev 39 -10 In Progress 9 -3 Dev Complete 11 +10 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211116/#osg-software-team","text":"Release AI (Mat): Release XRootD 5.3.3 in OSG 3.6 (SOFTWARE-4885) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): investigate HTCondor-CE failures in the nightlies (SOFTWARE-4901)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211116/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211116/#support-update","text":"Georgia State University (BrianL): needed to add pre-populated known_hosts since ssh-keyscan doesn't work with jump hosts JLab (BrianL): had a meeting to discuss token issuers; they'll likely start with a local issuer for pilots and will consider CILogon as their issuer Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6","title":"Support Update"},{"location":"meetings/2021/TechArea20211116/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211116/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211123/","text":"OSG Technology Area Meeting, 23 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: BrianL 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 162 +1 Open 41 -1 Selected for Dev 31 +2 In Progress 10 +1 Dev Complete 14 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (BrianL): WLCG VO DN update in the vo-client (SOFTWARE-4912) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): Investigate OSPool registry pod stuck in Pending AI (BrianL): Give CMS a recipe to generate pilot configuration without using osg-configure Discussion \u00b6 HTCondor scitokens-credmon for EL8: aiming for Post-christmas release Marco: Fixing GlideinWMS 3.7.6 bugs; afterwards, further development will be Python 3 only. There are several patches used in OSG OS Pool frontend -- Marco will talk to Mats Rynge about getting them upstream. Proxy delegation in the OSG 3.6 build of HTCondor 9 is broken; does not affect the OSG 3.5-upcoming build, and will be fixed in 9.0.8. Fermilab is hiring for a developer position. Support Update \u00b6 Lancium (BrianL): GPUs not showing up in Lancium resources due to HTCondor 9.0.6 GPU discovery bug; OS Registry doesn't work with Google IDs since they don't provide an eduPersonPrincipalName ( eppn ) Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6 LBL (Mat): Gratia probes weren't reporting in; this was due to files on disk not having been properly restored from backup; yum reinstall fixed the issue. OSG Release Team \u00b6 Aiming for a release next week: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works) Discussion \u00b6 None this week","title":"November 23, 2021"},{"location":"meetings/2021/TechArea20211123/#osg-technology-area-meeting-23-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 23 November 2021"},{"location":"meetings/2021/TechArea20211123/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20211123/#triage-duty","text":"This week: TimT Next week: BrianL 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211123/#jira-as-of-monday","text":"# of tickets \u0394 State 162 +1 Open 41 -1 Selected for Dev 31 +2 In Progress 10 +1 Dev Complete 14 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211123/#osg-software-team","text":"Release AI (BrianL): WLCG VO DN update in the vo-client (SOFTWARE-4912) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): Investigate OSPool registry pod stuck in Pending AI (BrianL): Give CMS a recipe to generate pilot configuration without using osg-configure","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211123/#discussion","text":"HTCondor scitokens-credmon for EL8: aiming for Post-christmas release Marco: Fixing GlideinWMS 3.7.6 bugs; afterwards, further development will be Python 3 only. There are several patches used in OSG OS Pool frontend -- Marco will talk to Mats Rynge about getting them upstream. Proxy delegation in the OSG 3.6 build of HTCondor 9 is broken; does not affect the OSG 3.5-upcoming build, and will be fixed in 9.0.8. Fermilab is hiring for a developer position.","title":"Discussion"},{"location":"meetings/2021/TechArea20211123/#support-update","text":"Lancium (BrianL): GPUs not showing up in Lancium resources due to HTCondor 9.0.6 GPU discovery bug; OS Registry doesn't work with Google IDs since they don't provide an eduPersonPrincipalName ( eppn ) Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6 LBL (Mat): Gratia probes weren't reporting in; this was due to files on disk not having been properly restored from backup; yum reinstall fixed the issue.","title":"Support Update"},{"location":"meetings/2021/TechArea20211123/#osg-release-team","text":"Aiming for a release next week: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works)","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211123/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211130/","text":"OSG Technology Area Meeting, 30 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T Announcements \u00b6 BrianL out next Monday, Dec 6 Triage Duty \u00b6 This week: BrianL Next week: Mat 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 181 +19 Open 22 -19 Selected for Dev 39 -2 In Progress 8 -2 Dev Complete 16 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today AI (BrianL): Put certmanager config of individual VO frontends into the base vo-frontend resource AI (Mat): Work with John Thiltges to set up an additional instance of repo.opensciencegrid.org on the River cluster Release AI (BrianL): Release xrootd 5.3.3+ for OSG 3.5 upcoming and OSG 3.6 (SOFTWARE-4903, SOFTWARE-4904) AI (Mat): Create transitional dummy package for xrootd-lcmaps in 3.6 (SOFTWARE-4481) AI (BrianL): Release xrootd-rucioN2N-for-Xcache-1.2-3.3+ in OSG 3.6 (SOFTWARE-4894) AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) Token transition AI (Mat): add the ability to specify subjects to token issuer mappings (SOFTWARE-4915) AI (Mat): merge xrootd-for-3.6 osg-test branch into master AI (BrianL): Investigate XRootD 3.6 TPC failures in the nightlies Discussion \u00b6 XRootD 5.3.2 will be released for 3.6 this week, with the caveat that origins shouldn't use it. GlideinWMS 3.7.6 is in progress (likely the last feature release for 3.7), as is CentOS 8 support for the 3.9 series. Support Update \u00b6 Lancium (BrianL): OS Registry doesn't work with Google or ORCID accounts since they don't provide an eduPersonPrincipalName ( eppn ) BNL (BrianL): help with OSPool Token Registry issues with the BNL and BNL-SDCC IdPs BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV OSG DevOps \u00b6 Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler going to be tested at Florida tomorrow Discussion \u00b6 None this week OSG Release Team \u00b6 Release tomorrow: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works) Discussion \u00b6 None this week","title":"November 30, 2021"},{"location":"meetings/2021/TechArea20211130/#osg-technology-area-meeting-30-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 30 November 2021"},{"location":"meetings/2021/TechArea20211130/#announcements","text":"BrianL out next Monday, Dec 6","title":"Announcements"},{"location":"meetings/2021/TechArea20211130/#triage-duty","text":"This week: BrianL Next week: Mat 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211130/#jira-as-of-monday","text":"# of tickets \u0394 State 181 +19 Open 22 -19 Selected for Dev 39 -2 In Progress 8 -2 Dev Complete 16 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211130/#osg-software-team","text":"Kubernetes Hackathon today AI (BrianL): Put certmanager config of individual VO frontends into the base vo-frontend resource AI (Mat): Work with John Thiltges to set up an additional instance of repo.opensciencegrid.org on the River cluster Release AI (BrianL): Release xrootd 5.3.3+ for OSG 3.5 upcoming and OSG 3.6 (SOFTWARE-4903, SOFTWARE-4904) AI (Mat): Create transitional dummy package for xrootd-lcmaps in 3.6 (SOFTWARE-4481) AI (BrianL): Release xrootd-rucioN2N-for-Xcache-1.2-3.3+ in OSG 3.6 (SOFTWARE-4894) AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) Token transition AI (Mat): add the ability to specify subjects to token issuer mappings (SOFTWARE-4915) AI (Mat): merge xrootd-for-3.6 osg-test branch into master AI (BrianL): Investigate XRootD 3.6 TPC failures in the nightlies","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211130/#discussion","text":"XRootD 5.3.2 will be released for 3.6 this week, with the caveat that origins shouldn't use it. GlideinWMS 3.7.6 is in progress (likely the last feature release for 3.7), as is CentOS 8 support for the 3.9 series.","title":"Discussion"},{"location":"meetings/2021/TechArea20211130/#support-update","text":"Lancium (BrianL): OS Registry doesn't work with Google or ORCID accounts since they don't provide an eduPersonPrincipalName ( eppn ) BNL (BrianL): help with OSPool Token Registry issues with the BNL and BNL-SDCC IdPs BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV","title":"Support Update"},{"location":"meetings/2021/TechArea20211130/#osg-devops","text":"Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler going to be tested at Florida tomorrow","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211130/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211130/#osg-release-team","text":"Release tomorrow: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works)","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211130/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211207/","text":"OSG Technology Area Meeting, 7 December 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL out today Mat out this afternoon and tomorrow Triage Duty \u00b6 This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 183 +2 Open 22 +0 Selected for Dev 30 -9 In Progress 10 +2 Dev Complete 5 -11 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Create secondary instance of repo.openscience.org on the UChicago River cluster. AI (Mat): Test vault/htvault-config/htgettoken AI (Brian): Set osg-flock VOOverride to \"osg\" AI (TimT): Release HTCondors 9.0.8 and 9.4.0 Discussion \u00b6 Tim added \"devops-minefield\" repos to osg-release; this can be tested manually. Marco: GlideinWMS 3.7.6 is in progress; most GitHub issues have been merged, as well as a new check for expired tokens. A release candidate is expected later today. The GlideinWMS license is changing from Fermi-modified BSD to Apache2; using REUSE (reuse.software) and SPDX (spdx.org), which make managing licenses in source code very convenient; these might be also be useful for other OSG projects and HTCondor team. Support Update \u00b6 BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (Mat, BrianL): debug not finding Singularity in backfill container GATech (Derek): Gratia probe is reporting a lot of groups. OSG DevOps \u00b6 Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them) Discussion \u00b6 None this week OSG Release Team \u00b6 Release this week: Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.3.4 Ready for Testing OSG 3.6-upcoming Soon: HTCondor 9.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Soon: HTCondor 9.0.8 (should fix proxy delegation) OSG 3.5-upcoming Soon: HTCondor 9.0.8 OSG 3.5 oidc-agent 4.2.4 Discussion \u00b6 None this week","title":"December 7, 2021"},{"location":"meetings/2021/TechArea20211207/#osg-technology-area-meeting-7-december-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 7 December 2021"},{"location":"meetings/2021/TechArea20211207/#announcements","text":"BrianL out today Mat out this afternoon and tomorrow","title":"Announcements"},{"location":"meetings/2021/TechArea20211207/#triage-duty","text":"This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211207/#jira-as-of-monday","text":"# of tickets \u0394 State 183 +2 Open 22 +0 Selected for Dev 30 -9 In Progress 10 +2 Dev Complete 5 -11 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211207/#osg-software-team","text":"AI (Mat): Create secondary instance of repo.openscience.org on the UChicago River cluster. AI (Mat): Test vault/htvault-config/htgettoken AI (Brian): Set osg-flock VOOverride to \"osg\" AI (TimT): Release HTCondors 9.0.8 and 9.4.0","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211207/#discussion","text":"Tim added \"devops-minefield\" repos to osg-release; this can be tested manually. Marco: GlideinWMS 3.7.6 is in progress; most GitHub issues have been merged, as well as a new check for expired tokens. A release candidate is expected later today. The GlideinWMS license is changing from Fermi-modified BSD to Apache2; using REUSE (reuse.software) and SPDX (spdx.org), which make managing licenses in source code very convenient; these might be also be useful for other OSG projects and HTCondor team.","title":"Discussion"},{"location":"meetings/2021/TechArea20211207/#support-update","text":"BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (Mat, BrianL): debug not finding Singularity in backfill container GATech (Derek): Gratia probe is reporting a lot of groups.","title":"Support Update"},{"location":"meetings/2021/TechArea20211207/#osg-devops","text":"Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them)","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211207/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211207/#osg-release-team","text":"Release this week: Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.3.4 Ready for Testing OSG 3.6-upcoming Soon: HTCondor 9.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Soon: HTCondor 9.0.8 (should fix proxy delegation) OSG 3.5-upcoming Soon: HTCondor 9.0.8 OSG 3.5 oidc-agent 4.2.4","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211207/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211214/","text":"OSG Technology Area Meeting, 14 December 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT Announcements \u00b6 Mat out Thursday afternoon Doc focus Friday afternoon Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 4 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 179 -4 Open 23 +1 Selected for Dev 30 +0 In Progress 10 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (Mat): Convert osg-pki-tools to Python 3 AI (Brian): Build XRootD with Brian's patch AI (Brian): Set osg-flock VOOverride to \"osg\" Discussion \u00b6 The HTCondor OAuth Credmon's dependencies only have Python 2 versions on EL 7; we'll need a python-scitokens version for Python 2, even if it's security-fixes only. Support Update \u00b6 BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (BrianL): moved them over to Singularity-in-Singularity and had to adjust their bind mount settings GATech (Derek): Gratia probe is reporting a lot of groups. UConn (BrianL): job router config not correctly converted from old syntax to new syntax: extra quotes in the grid resource caused connection failure OSG DevOps \u00b6 Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them) Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release Nothing Ready for Testing OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Discussion \u00b6 None this week","title":"December 14, 2021"},{"location":"meetings/2021/TechArea20211214/#osg-technology-area-meeting-14-december-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT","title":"OSG Technology Area Meeting, 14 December 2021"},{"location":"meetings/2021/TechArea20211214/#announcements","text":"Mat out Thursday afternoon Doc focus Friday afternoon","title":"Announcements"},{"location":"meetings/2021/TechArea20211214/#triage-duty","text":"This week: TimT Next week: BrianL (?) 4 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211214/#jira-as-of-monday","text":"# of tickets \u0394 State 179 -4 Open 23 +1 Selected for Dev 30 +0 In Progress 10 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211214/#osg-software-team","text":"Kubernetes hackathon today AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (Mat): Convert osg-pki-tools to Python 3 AI (Brian): Build XRootD with Brian's patch AI (Brian): Set osg-flock VOOverride to \"osg\"","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211214/#discussion","text":"The HTCondor OAuth Credmon's dependencies only have Python 2 versions on EL 7; we'll need a python-scitokens version for Python 2, even if it's security-fixes only.","title":"Discussion"},{"location":"meetings/2021/TechArea20211214/#support-update","text":"BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (BrianL): moved them over to Singularity-in-Singularity and had to adjust their bind mount settings GATech (Derek): Gratia probe is reporting a lot of groups. UConn (BrianL): job router config not correctly converted from old syntax to new syntax: extra quotes in the grid resource caused connection failure","title":"Support Update"},{"location":"meetings/2021/TechArea20211214/#osg-devops","text":"Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them)","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211214/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211214/#osg-release-team","text":"Ready for Release Nothing Ready for Testing OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211214/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220104/","text":"OSG Technology Area Meeting, 4 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Mat, TimT Announcements \u00b6 Brian out today. Triage Duty \u00b6 This week: Mat Next week: BrianL (?) 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 178 -1 Open 21 -2 Selected for Dev 35 +5 In Progress 10 +0 Dev Complete 9 +7 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Mat: update stashcache-client RPM to contain stashcp 6.4.0 TimT: release HTCondor 9.0.9+, HTCondor 9.5.0+ Discussion \u00b6 HTCondor developers adding Rocky Linux 8 as one of their platforms for UW builds (replacing CentOS Linux 8, which was EOL as of the end of last year). OSG is testing on Rocky Linux 8 (among other compatible platforms) but still using CentOS Linux 8 for build repos; no decision on yet on which variant to use as a replacement but CentOS Stream 8 is likely since that is what Fermilab is using. Support Update \u00b6 Doug Benjamin (BNL) needed to be added as a Topology contact for several resources for submitting downtime; TimC is working on making sure Topology contacts are up to date. Gluex was unable to access some of their files hosted on stash origins via CVMFS; their directory had too many files and bloated the CVMFS catalog to the point where it kept getting evicted from clients' caches. Derek split the catalog into smaller catalogs, which should solve the problem. OSG DevOps \u00b6 Discussion \u00b6 None this week OSG Release Team \u00b6 Discussion \u00b6 None this week","title":"January 4, 2022"},{"location":"meetings/2022/TechArea20220104/#osg-technology-area-meeting-4-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Mat, TimT","title":"OSG Technology Area Meeting, 4 January 2022"},{"location":"meetings/2022/TechArea20220104/#announcements","text":"Brian out today.","title":"Announcements"},{"location":"meetings/2022/TechArea20220104/#triage-duty","text":"This week: Mat Next week: BrianL (?) 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220104/#jira-as-of-monday","text":"# of tickets \u0394 State 178 -1 Open 21 -2 Selected for Dev 35 +5 In Progress 10 +0 Dev Complete 9 +7 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220104/#osg-software-team","text":"Mat: update stashcache-client RPM to contain stashcp 6.4.0 TimT: release HTCondor 9.0.9+, HTCondor 9.5.0+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220104/#discussion","text":"HTCondor developers adding Rocky Linux 8 as one of their platforms for UW builds (replacing CentOS Linux 8, which was EOL as of the end of last year). OSG is testing on Rocky Linux 8 (among other compatible platforms) but still using CentOS Linux 8 for build repos; no decision on yet on which variant to use as a replacement but CentOS Stream 8 is likely since that is what Fermilab is using.","title":"Discussion"},{"location":"meetings/2022/TechArea20220104/#support-update","text":"Doug Benjamin (BNL) needed to be added as a Topology contact for several resources for submitting downtime; TimC is working on making sure Topology contacts are up to date. Gluex was unable to access some of their files hosted on stash origins via CVMFS; their directory had too many files and bloated the CVMFS catalog to the point where it kept getting evicted from clients' caches. Derek split the catalog into smaller catalogs, which should solve the problem.","title":"Support Update"},{"location":"meetings/2022/TechArea20220104/#osg-devops","text":"","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220104/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220104/#osg-release-team","text":"","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220104/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220111/","text":"OSG Technology Area Meeting, 11 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Mat 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 180 +2 Open 18 -3 Selected for Dev 36 +1 In Progress 10 +0 Dev Complete 13 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): release stashcp 6.5.3+ K8s Hackathon: test functionality of \"canary\" CEs; start moving Koji components to Kubernetes AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release new osg-flock Discussion \u00b6 xrootd-tcp-stats is ready for testing; planning to test on a small set of hosts before adding it to the defaults in osg-xrootd Support Update \u00b6 Lancium (BrianL): pilot container probe has had issues querying the HA OSPool collectors since Dec 21. UTC-Epyc (BrianL, Mat): lots of stash related transfer failures. Worked on disabling stash at the site. OSG DevOps \u00b6 K8s Hackathon: Work on xrootd monitoring collector. Mostly asking questions... Following up on issues noted by Mat on StashCP Working on improving GeoIP algorithms Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Ready for Testing OSG 3.5, OSG 3.6 vo-client 116 (data) osg-scitokens-mapfile 4 (data) osg-pki-tools 3.5.0-2 (Python 3 conversion) OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 xrootd-tcp-stats 1.0.0 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12 Discussion \u00b6 None this week","title":"January 11, 2022"},{"location":"meetings/2022/TechArea20220111/#osg-technology-area-meeting-11-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 11 January 2022"},{"location":"meetings/2022/TechArea20220111/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220111/#triage-duty","text":"This week: BrianL Next week: Mat 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220111/#jira-as-of-monday","text":"# of tickets \u0394 State 180 +2 Open 18 -3 Selected for Dev 36 +1 In Progress 10 +0 Dev Complete 13 +4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220111/#osg-software-team","text":"AI (Mat): release stashcp 6.5.3+ K8s Hackathon: test functionality of \"canary\" CEs; start moving Koji components to Kubernetes AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release new osg-flock","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220111/#discussion","text":"xrootd-tcp-stats is ready for testing; planning to test on a small set of hosts before adding it to the defaults in osg-xrootd","title":"Discussion"},{"location":"meetings/2022/TechArea20220111/#support-update","text":"Lancium (BrianL): pilot container probe has had issues querying the HA OSPool collectors since Dec 21. UTC-Epyc (BrianL, Mat): lots of stash related transfer failures. Worked on disabling stash at the site.","title":"Support Update"},{"location":"meetings/2022/TechArea20220111/#osg-devops","text":"K8s Hackathon: Work on xrootd monitoring collector. Mostly asking questions... Following up on issues noted by Mat on StashCP Working on improving GeoIP algorithms","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220111/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220111/#osg-release-team","text":"Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Ready for Testing OSG 3.5, OSG 3.6 vo-client 116 (data) osg-scitokens-mapfile 4 (data) osg-pki-tools 3.5.0-2 (Python 3 conversion) OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 xrootd-tcp-stats 1.0.0 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220111/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220118/","text":"OSG Technology Area Meeting, 11 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 6 (+2) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 179 -1 Open 21 -3 Selected for Dev 32 -4 In Progress 10 +0 Dev Complete 5 -8 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): release stashcp 6.5.3+ AI (Mat): add ATLAS IAM to vo-client: should only require a packaging change AI (Mat): Write osg-resource-catalog-generator. AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release osg-flock 1.7+ Discussion \u00b6 EPEL metadata broken in EL7 Koji builds; a regen-repo should fix that. AI (student): write a script to run the appropriate regen-repo commands next time. HEPCloud version 2 release candidate is expected today. GlideinWMS 3.7.6 release candidate is out and being tested by Marco Mascheroni at the CERN ITB. Support Update \u00b6 BNL (Mat): Debugging authentication issues with XRootD. OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12 Discussion \u00b6 Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"January 18, 2022"},{"location":"meetings/2022/TechArea20220118/#osg-technology-area-meeting-11-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 11 January 2022"},{"location":"meetings/2022/TechArea20220118/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220118/#triage-duty","text":"This week: Mat Next week: TimT 6 (+2) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220118/#jira-as-of-monday","text":"# of tickets \u0394 State 179 -1 Open 21 -3 Selected for Dev 32 -4 In Progress 10 +0 Dev Complete 5 -8 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220118/#osg-software-team","text":"AI (Mat): release stashcp 6.5.3+ AI (Mat): add ATLAS IAM to vo-client: should only require a packaging change AI (Mat): Write osg-resource-catalog-generator. AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release osg-flock 1.7+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220118/#discussion","text":"EPEL metadata broken in EL7 Koji builds; a regen-repo should fix that. AI (student): write a script to run the appropriate regen-repo commands next time. HEPCloud version 2 release candidate is expected today. GlideinWMS 3.7.6 release candidate is out and being tested by Marco Mascheroni at the CERN ITB.","title":"Discussion"},{"location":"meetings/2022/TechArea20220118/#support-update","text":"BNL (Mat): Debugging authentication issues with XRootD.","title":"Support Update"},{"location":"meetings/2022/TechArea20220118/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220118/#discussion_1","text":"Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"Discussion"},{"location":"meetings/2022/TechArea20220125/","text":"OSG Technology Area Meeting, 25 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco, Mat, TimT Announcements \u00b6 OSG site admin office hours today, 1-4pm Central Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 7 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 180 +1 Open 24 +3 Selected for Dev 31 -1 In Progress 10 +0 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-resource-catalog-generator, update osg-configure-bosco deps and script refs AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): Release osg-flock 1.7+ AI (BrianL): Create new release tags for XRootD images. AI (BrianL): Collaborate with Fermi to get default token mappings for their experiments. Discussion \u00b6 GlideinWMS 3.7.6 released, which is the last of the 3.7 series. Most frontends (GLOW, OSPool, IGWN, and others) are already using the 3.9 series, as is HEPCloud. A workaround is available for the credential name issue on GSI-less frontends, and will be documented in the ticket. Dennis is working on a fix. GlideinWMS team is working on a way to send a token to GCE and AWS pilots since HTCondor file transfer does not work. TJ of the HTCondor Team is also working on a solution. Discussed whether HTCondor patch releases should be moved out of the devops repos into the mainline repos. We've decided against it because patch releases are more intended for testing on the OS Pool than for general usage. The stashcp RPM in progress for OSG is binary-only because Go 1.16 is not available in EPEL 7. Dave Dykstra mentioned trying to get the EPEL version of Go updated; if he is successful, we can revisit the packaging. Support Update \u00b6 ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. Purdue (BrianL): CE jobs evicted OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12 Discussion \u00b6 Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"January 25, 2022"},{"location":"meetings/2022/TechArea20220125/#osg-technology-area-meeting-25-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 25 January 2022"},{"location":"meetings/2022/TechArea20220125/#announcements","text":"OSG site admin office hours today, 1-4pm Central","title":"Announcements"},{"location":"meetings/2022/TechArea20220125/#triage-duty","text":"This week: TimT Next week: BrianL (?) 7 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220125/#jira-as-of-monday","text":"# of tickets \u0394 State 180 +1 Open 24 +3 Selected for Dev 31 -1 In Progress 10 +0 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220125/#osg-software-team","text":"AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-resource-catalog-generator, update osg-configure-bosco deps and script refs AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): Release osg-flock 1.7+ AI (BrianL): Create new release tags for XRootD images. AI (BrianL): Collaborate with Fermi to get default token mappings for their experiments.","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220125/#discussion","text":"GlideinWMS 3.7.6 released, which is the last of the 3.7 series. Most frontends (GLOW, OSPool, IGWN, and others) are already using the 3.9 series, as is HEPCloud. A workaround is available for the credential name issue on GSI-less frontends, and will be documented in the ticket. Dennis is working on a fix. GlideinWMS team is working on a way to send a token to GCE and AWS pilots since HTCondor file transfer does not work. TJ of the HTCondor Team is also working on a solution. Discussed whether HTCondor patch releases should be moved out of the devops repos into the mainline repos. We've decided against it because patch releases are more intended for testing on the OS Pool than for general usage. The stashcp RPM in progress for OSG is binary-only because Go 1.16 is not available in EPEL 7. Dave Dykstra mentioned trying to get the EPEL version of Go updated; if he is successful, we can revisit the packaging.","title":"Discussion"},{"location":"meetings/2022/TechArea20220125/#support-update","text":"ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. Purdue (BrianL): CE jobs evicted","title":"Support Update"},{"location":"meetings/2022/TechArea20220125/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220125/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220125/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220125/#discussion_2","text":"Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"Discussion"},{"location":"meetings/2022/TechArea20220201/","text":"OSG Technology Area Meeting, 1 February 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Mat 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 185 +5 Open 28 +4 Selected for Dev 33 +2 In Progress 9 -1 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-ce-attributes-generator update osg-configure-bosco deps and script refs AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): add support for manual client registration to osg-token-renewer Discussion \u00b6 None this week Support Update \u00b6 ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. MWT2 (BrianL): troubleshoot issues with missing accounting records. Got everything restored. Purdue (BrianL): CE jobs evicted, appears to be removals from the factory side UCSD (Mat): Debugging cache server issues reporting to central collector OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release OSG 3.6 Gratia Probe 2.5.1 Ready for Testing OSG 3.6, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 osg-flock 1.7 OSG 3.6 upcoming HTCondor 9.5.0 Discussion \u00b6 None this week","title":"February 1, 2022"},{"location":"meetings/2022/TechArea20220201/#osg-technology-area-meeting-1-february-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Mat, Tim","title":"OSG Technology Area Meeting, 1 February 2022"},{"location":"meetings/2022/TechArea20220201/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220201/#triage-duty","text":"This week: BrianL Next week: Mat 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220201/#jira-as-of-monday","text":"# of tickets \u0394 State 185 +5 Open 28 +4 Selected for Dev 33 +2 In Progress 9 -1 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220201/#osg-software-team","text":"AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-ce-attributes-generator update osg-configure-bosco deps and script refs AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): add support for manual client registration to osg-token-renewer","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220201/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220201/#support-update","text":"ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. MWT2 (BrianL): troubleshoot issues with missing accounting records. Got everything restored. Purdue (BrianL): CE jobs evicted, appears to be removals from the factory side UCSD (Mat): Debugging cache server issues reporting to central collector","title":"Support Update"},{"location":"meetings/2022/TechArea20220201/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220201/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220201/#osg-release-team","text":"Ready for Release OSG 3.6 Gratia Probe 2.5.1 Ready for Testing OSG 3.6, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 osg-flock 1.7 OSG 3.6 upcoming HTCondor 9.5.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220201/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220208/","text":"OSG Technology Area Meeting, 8 February 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, Brian Lin, Marco Mambelli, Tim Theisen Announcements \u00b6 BrianL unavailable Wed-Thu, OOO Fri TimT OOO Feb 21-25 Triage Duty \u00b6 This week: Mat Next week: TimT 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 190 +5 Open 29 +1 Selected for Dev 37 +4 In Progress 9 +0 Dev Complete 6 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! AI (Mat): Release stashcp 6.5.3+ AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): add new OSG/GLOW VO DNs to the vo-client Discussion \u00b6 Brian C of the Security Team will be taking over some of Ryan Kiser's projects (e.g. grid scanner) Dennis is working on addressing the GlideinWMS bug where an X.509 credential was still required (but unused) for factory/frontend communication Marco is working on moving GlideinWMS issues from Redmine to GitHub; he will also coordinate GlideinWMS dev attendance at the Operations Frontend admin meeting later this week Support Update \u00b6 UIUC (BrianL) assist Ops with troubleshooting Hosted CE WN client installation OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Release expected this week Ready for Testing OSG 3.5, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 upcoming HTCondor 9.5.0 Discussion \u00b6 Expect a vo-client update this week AI (BrianC): follow-up with Josh Drake on the members of the OSG security mailing list and the process by which members are added/removed","title":"February 8, 2022"},{"location":"meetings/2022/TechArea20220208/#osg-technology-area-meeting-8-february-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, Brian Lin, Marco Mambelli, Tim Theisen","title":"OSG Technology Area Meeting, 8 February 2022"},{"location":"meetings/2022/TechArea20220208/#announcements","text":"BrianL unavailable Wed-Thu, OOO Fri TimT OOO Feb 21-25","title":"Announcements"},{"location":"meetings/2022/TechArea20220208/#triage-duty","text":"This week: Mat Next week: TimT 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220208/#jira-as-of-monday","text":"# of tickets \u0394 State 190 +5 Open 29 +1 Selected for Dev 37 +4 In Progress 9 +0 Dev Complete 6 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220208/#osg-software-team","text":"Kubernetes Hackathon today! AI (Mat): Release stashcp 6.5.3+ AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): add new OSG/GLOW VO DNs to the vo-client","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220208/#discussion","text":"Brian C of the Security Team will be taking over some of Ryan Kiser's projects (e.g. grid scanner) Dennis is working on addressing the GlideinWMS bug where an X.509 credential was still required (but unused) for factory/frontend communication Marco is working on moving GlideinWMS issues from Redmine to GitHub; he will also coordinate GlideinWMS dev attendance at the Operations Frontend admin meeting later this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220208/#support-update","text":"UIUC (BrianL) assist Ops with troubleshooting Hosted CE WN client installation","title":"Support Update"},{"location":"meetings/2022/TechArea20220208/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220208/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220208/#osg-release-team","text":"Release expected this week Ready for Testing OSG 3.5, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 upcoming HTCondor 9.5.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220208/#discussion_2","text":"Expect a vo-client update this week AI (BrianC): follow-up with Josh Drake on the members of the OSG security mailing list and the process by which members are added/removed","title":"Discussion"},{"location":"meetings/2022/TechArea20220222/","text":"OSG Technology Area Meeting, 22 February 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, BrianL, Mat Announcements \u00b6 TimT OOO Feb 21-25 Triage Duty \u00b6 This week: BrianL Next week: Mat 13 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 199 +5 Open 31 +1 Selected for Dev 37 +0 In Progress 14 +3 Dev Complete 4 +2 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): Update osg-configure-bosco dependency and build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): kick off tests for GlideinWMS 3.7.6 and 3.9.4 AI (BrianL): build new osg-scitokens-mapfile AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): address issues with gratia-probe-condor-ap Discussion \u00b6 Additional develoment work is needed to support multi-VO APs, especially with Gratia reporting (probes can only deal with one VO at a time) and figuring out how to map jobs to VOs in a way that the probe can recognize. rpm --verify test in VMU tests does not handle virtual dependencies; it does two things: verify that all listed packages were installed (can be done with a yum flag) verify that files on disk match files in package (has caught at least one error within living memory) Support Update \u00b6 GSU (BrianL): investigate SSH certificate issues JLab (BrianL): troubleshoot missing payload records from APs Lancium (BrianL): investigate HAS_SINGULARITY = False SDSC (Mat): troubleshoot cache/origin authentication OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming, OSG 3.6 osg-xrootd OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure) Discussion \u00b6 None this week","title":"February 22, 2022"},{"location":"meetings/2022/TechArea20220222/#osg-technology-area-meeting-22-february-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, BrianL, Mat","title":"OSG Technology Area Meeting, 22 February 2022"},{"location":"meetings/2022/TechArea20220222/#announcements","text":"TimT OOO Feb 21-25","title":"Announcements"},{"location":"meetings/2022/TechArea20220222/#triage-duty","text":"This week: BrianL Next week: Mat 13 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220222/#jira-as-of-monday","text":"# of tickets \u0394 State 199 +5 Open 31 +1 Selected for Dev 37 +0 In Progress 14 +3 Dev Complete 4 +2 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220222/#osg-software-team","text":"Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): Update osg-configure-bosco dependency and build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): kick off tests for GlideinWMS 3.7.6 and 3.9.4 AI (BrianL): build new osg-scitokens-mapfile AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): address issues with gratia-probe-condor-ap","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220222/#discussion","text":"Additional develoment work is needed to support multi-VO APs, especially with Gratia reporting (probes can only deal with one VO at a time) and figuring out how to map jobs to VOs in a way that the probe can recognize. rpm --verify test in VMU tests does not handle virtual dependencies; it does two things: verify that all listed packages were installed (can be done with a yum flag) verify that files on disk match files in package (has caught at least one error within living memory)","title":"Discussion"},{"location":"meetings/2022/TechArea20220222/#support-update","text":"GSU (BrianL): investigate SSH certificate issues JLab (BrianL): troubleshoot missing payload records from APs Lancium (BrianL): investigate HAS_SINGULARITY = False SDSC (Mat): troubleshoot cache/origin authentication","title":"Support Update"},{"location":"meetings/2022/TechArea20220222/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220222/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220222/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming, OSG 3.6 osg-xrootd OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220222/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220301/","text":"OSG Technology Area Meeting, 1 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 18 (+5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 186 -13 Open 41 +10 Selected for Dev 35 -2 In Progress 20 +6 Dev Complete 7 +3 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Doc focus Friday 1-5pm! Full court press on documentation Consolidating container images to https://github.com/opensciencegrid/images/ (SOFTWARE-4944) AI (Mat): build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): address issues with gratia-probe-condor-ap AI (TimT): prepare HTCondor 9.7.0 release candidate in time for Patch Tuesday Discussion \u00b6 osg-token-renewer release is waiting for Dave Dykstra and CILogon developers to diagnose issues between OIDC-Agent and CILogon interactions = We have updated our container retention policy: timestamped containers will be deleted after 6 months or if there are any security issues Support Update \u00b6 BNL (BrianL): issue was caused by missing/outdated CRLs; Brian will review the support ticket and create any necessary JIRA tickets for development work GSU (BrianL): investigate SSH certificate issues; turned out to be an expired cert and a bad target post-jump host Lancium (BrianL): discussed OSG ownership of container deployment; facilitated an introduction with Igor SDSC (Mat): the XrdVoms plugin (used in OSG 3.6) is mapping certificates to a different XRootD identity than LCMAPS was. Mat will investigate if XRootD config changes can solve the issue GlideinWMS (Marco): fixing bug related to cloud submission OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure) Discussion \u00b6 Announce container retention policy update with this week's release","title":"March 1, 2022"},{"location":"meetings/2022/TechArea20220301/#osg-technology-area-meeting-1-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Tim T","title":"OSG Technology Area Meeting, 1 March 2022"},{"location":"meetings/2022/TechArea20220301/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220301/#triage-duty","text":"This week: Mat Next week: TimT 18 (+5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220301/#jira-as-of-monday","text":"# of tickets \u0394 State 186 -13 Open 41 +10 Selected for Dev 35 -2 In Progress 20 +6 Dev Complete 7 +3 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220301/#osg-software-team","text":"Doc focus Friday 1-5pm! Full court press on documentation Consolidating container images to https://github.com/opensciencegrid/images/ (SOFTWARE-4944) AI (Mat): build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): address issues with gratia-probe-condor-ap AI (TimT): prepare HTCondor 9.7.0 release candidate in time for Patch Tuesday","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220301/#discussion","text":"osg-token-renewer release is waiting for Dave Dykstra and CILogon developers to diagnose issues between OIDC-Agent and CILogon interactions = We have updated our container retention policy: timestamped containers will be deleted after 6 months or if there are any security issues","title":"Discussion"},{"location":"meetings/2022/TechArea20220301/#support-update","text":"BNL (BrianL): issue was caused by missing/outdated CRLs; Brian will review the support ticket and create any necessary JIRA tickets for development work GSU (BrianL): investigate SSH certificate issues; turned out to be an expired cert and a bad target post-jump host Lancium (BrianL): discussed OSG ownership of container deployment; facilitated an introduction with Igor SDSC (Mat): the XrdVoms plugin (used in OSG 3.6) is mapping certificates to a different XRootD identity than LCMAPS was. Mat will investigate if XRootD config changes can solve the issue GlideinWMS (Marco): fixing bug related to cloud submission","title":"Support Update"},{"location":"meetings/2022/TechArea20220301/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220301/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220301/#osg-release-team","text":"Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220301/#discussion_2","text":"Announce container retention policy update with this week's release","title":"Discussion"},{"location":"meetings/2022/TechArea20220308/","text":"OSG Technology Area Meeting, 8 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian C, Brian L, Derek, Marco, Mat, Tim T Announcements \u00b6 OSG All Hands next week! OSG site admin office hours from 3:30-5:30pm Tue Mar 15! Triage Duty \u00b6 This week: TimT Next week: BrianL 13 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 185 -1 Open 40 -1 Selected for Dev 34 -1 In Progress 14 -6 Dev Complete 6 -1 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): xcache-reporter packaging issues AI (TimT): move and update oidc-agent technology doc to main docs area as a \"using tokens\" doc AI (Mat): add token overview for site admins AI (BrianL): add overview of 3.6 token transition AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken Discussion \u00b6 GlideinWMS (Marco): GlideinWMS development has moved to GitHub; there are workflows and the developers are in the process of migrating Redmine tickets. Working on fix for slowdown when launching processes for running RRD commands; Python RRD is the only method which gives acceptable performance but there is no RPM for the dependency. Marco will discuss with OSG Software team how to handle the dependency issue. Support Update \u00b6 BNL (BrianL): Qiulan/Doug say that WebDAV doesn't work for their standalone server Edinburgh (BrianL): help register a cache and sort out Dune data federation details OU (Derek): Issues with tier2-01.ochep.ou.edu gratia, Horst indicated it's an EL6 cluster and he would be in favor of turning it off. SDSC (Mat): Got their cache working by using OSG 3.5; asked Diego/Fabio to upgrade some of our test caches to OSG 3.6 so we can figure out auth issues without breaking his site. OSG DevOps \u00b6 StashCP multi-file download/upload. Secured an \"Open Source\" license for Gitpod which is the Professional level. It's a competitor to Github Codespaces. Remote development. My first thought is that it would be nice for topology development since it's difficult (in my experience) to iterate. Especially initial setup. License is open to all members of the opensciencegrid github organization. Packaging of the shoveler? Packaging of the python-scitokens? Working on OSDF metrics for OSG Meeting. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure) Discussion \u00b6 Announce container retention policy update with this week's release","title":"March 8, 2022"},{"location":"meetings/2022/TechArea20220308/#osg-technology-area-meeting-8-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian C, Brian L, Derek, Marco, Mat, Tim T","title":"OSG Technology Area Meeting, 8 March 2022"},{"location":"meetings/2022/TechArea20220308/#announcements","text":"OSG All Hands next week! OSG site admin office hours from 3:30-5:30pm Tue Mar 15!","title":"Announcements"},{"location":"meetings/2022/TechArea20220308/#triage-duty","text":"This week: TimT Next week: BrianL 13 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220308/#jira-as-of-monday","text":"# of tickets \u0394 State 185 -1 Open 40 -1 Selected for Dev 34 -1 In Progress 14 -6 Dev Complete 6 -1 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220308/#osg-software-team","text":"Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): xcache-reporter packaging issues AI (TimT): move and update oidc-agent technology doc to main docs area as a \"using tokens\" doc AI (Mat): add token overview for site admins AI (BrianL): add overview of 3.6 token transition AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220308/#discussion","text":"GlideinWMS (Marco): GlideinWMS development has moved to GitHub; there are workflows and the developers are in the process of migrating Redmine tickets. Working on fix for slowdown when launching processes for running RRD commands; Python RRD is the only method which gives acceptable performance but there is no RPM for the dependency. Marco will discuss with OSG Software team how to handle the dependency issue.","title":"Discussion"},{"location":"meetings/2022/TechArea20220308/#support-update","text":"BNL (BrianL): Qiulan/Doug say that WebDAV doesn't work for their standalone server Edinburgh (BrianL): help register a cache and sort out Dune data federation details OU (Derek): Issues with tier2-01.ochep.ou.edu gratia, Horst indicated it's an EL6 cluster and he would be in favor of turning it off. SDSC (Mat): Got their cache working by using OSG 3.5; asked Diego/Fabio to upgrade some of our test caches to OSG 3.6 so we can figure out auth issues without breaking his site.","title":"Support Update"},{"location":"meetings/2022/TechArea20220308/#osg-devops","text":"StashCP multi-file download/upload. Secured an \"Open Source\" license for Gitpod which is the Professional level. It's a competitor to Github Codespaces. Remote development. My first thought is that it would be nice for topology development since it's difficult (in my experience) to iterate. Especially initial setup. License is open to all members of the opensciencegrid github organization. Packaging of the shoveler? Packaging of the python-scitokens? Working on OSDF metrics for OSG Meeting.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220308/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220308/#osg-release-team","text":"Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220308/#discussion_2","text":"Announce container retention policy update with this week's release","title":"Discussion"},{"location":"meetings/2022/TechArea20220322/","text":"OSG Technology Area Meeting, 22 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T Announcements \u00b6 BrianB out this week Triage Duty \u00b6 This week: Mat Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 183 +1 Open 42 +1 Selected for Dev 29 -4 In Progress 14 -2 Dev Complete 14 +2 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River Set up Dex for Tiger Clean up PATh facility backfill containers AI (Mat): xcache-reporter packaging issues AI (Mat): Build wn-client tarballs from 3.5-upcoming AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): release osg-ce with OSG_SERIES schedd attr Discussion \u00b6 Marco: Implementing features started in last week's GlideinWMS Hackathon, including a plugin interface for SciTokens/WLCG Tokens. HTCondor Week registration is open, looking for speakers. Marco has several ideas for talks that Fermi or GlideinWMS folks can give; Brian will pass them on to the HTCSS dev team. Derek reports that HTCondor file transfer output plugins are hard to debug, primarily due to lack of output upon failures. HTCondor 9.7.0 has improvements in this department; Derek will verify and send suggestions for further improvements to the HTCSS devs. Support Update \u00b6 Edinburgh (BrianL): registered their cache OSG DevOps \u00b6 StashCP multi-file download/upload and improvement of HTCondor file transfer. Packaging of the shoveler is ongoing. Update the OSDF metrics gathering, working with Fabio Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.6-upcoming: HTCondor 9.7.0: New feature release OSG 3.6 XRootD 5.4.2-1.1: OSG patches added HTCondor 9.0.11: Bug fix release python-scitokens 1.7.0 osg-token-renewer 0.8.1 xrootd-monitoring-shoveler 1.0.0 stashcp 6.5.0 OSG 3.5-upcoming XRootD 5.4.2 HTCondor 9.0.11: Bug fix release GlideWMS 3.7.6 gfal2 2.20.3: Update to resolve installation issues on 3.5-upcoming OSG 3.5 HTCondor 8.8.17: Bug fix release scitokens-cpp 0.7.0 python-scitokens 1.7.0 osg-token-renewer 0.8.1 Ready for Release Nothing yet Discussion \u00b6 Announce container retention policy update with this week's release","title":"March 22, 2022"},{"location":"meetings/2022/TechArea20220322/#osg-technology-area-meeting-22-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 22 March 2022"},{"location":"meetings/2022/TechArea20220322/#announcements","text":"BrianB out this week","title":"Announcements"},{"location":"meetings/2022/TechArea20220322/#triage-duty","text":"This week: Mat Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220322/#jira-as-of-monday","text":"# of tickets \u0394 State 183 +1 Open 42 +1 Selected for Dev 29 -4 In Progress 14 -2 Dev Complete 14 +2 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220322/#osg-software-team","text":"Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River Set up Dex for Tiger Clean up PATh facility backfill containers AI (Mat): xcache-reporter packaging issues AI (Mat): Build wn-client tarballs from 3.5-upcoming AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): release osg-ce with OSG_SERIES schedd attr","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220322/#discussion","text":"Marco: Implementing features started in last week's GlideinWMS Hackathon, including a plugin interface for SciTokens/WLCG Tokens. HTCondor Week registration is open, looking for speakers. Marco has several ideas for talks that Fermi or GlideinWMS folks can give; Brian will pass them on to the HTCSS dev team. Derek reports that HTCondor file transfer output plugins are hard to debug, primarily due to lack of output upon failures. HTCondor 9.7.0 has improvements in this department; Derek will verify and send suggestions for further improvements to the HTCSS devs.","title":"Discussion"},{"location":"meetings/2022/TechArea20220322/#support-update","text":"Edinburgh (BrianL): registered their cache","title":"Support Update"},{"location":"meetings/2022/TechArea20220322/#osg-devops","text":"StashCP multi-file download/upload and improvement of HTCondor file transfer. Packaging of the shoveler is ongoing. Update the OSDF metrics gathering, working with Fabio","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220322/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220322/#osg-release-team","text":"Ready for Testing OSG 3.6-upcoming: HTCondor 9.7.0: New feature release OSG 3.6 XRootD 5.4.2-1.1: OSG patches added HTCondor 9.0.11: Bug fix release python-scitokens 1.7.0 osg-token-renewer 0.8.1 xrootd-monitoring-shoveler 1.0.0 stashcp 6.5.0 OSG 3.5-upcoming XRootD 5.4.2 HTCondor 9.0.11: Bug fix release GlideWMS 3.7.6 gfal2 2.20.3: Update to resolve installation issues on 3.5-upcoming OSG 3.5 HTCondor 8.8.17: Bug fix release scitokens-cpp 0.7.0 python-scitokens 1.7.0 osg-token-renewer 0.8.1 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220322/#discussion_2","text":"Announce container retention policy update with this week's release","title":"Discussion"},{"location":"meetings/2022/TechArea20220329/","text":"OSG Technology Area Meeting, 29 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Marco Mambelli, Mat Announcements \u00b6 TimT out next week Triage Duty \u00b6 This week: TimT Next week: BrianL 18 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 179 -4 Open 42 +0 Selected for Dev 29 +0 In Progress 14 +0 Dev Complete 5 -9 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus friday AI (Mat): Release osg-scitokens-mapfile-7 with HCC token mapping AI (Mat): kick off VMU tests for cigetcert AI (BrianL): release osg-ce with OSG_SERIES schedd attr AI (BrianL): python3-rrdtool for EL7 Discussion \u00b6 GlideinWMS 3.7.7 in progress; working on putting the token from the HTCondor-CE collector in the correct location. GlideinWMS 3.9.5 ETA ~3 weeks, including the scitoken credential plugin interface Support Update \u00b6 UNL (BrianL, Derek): helped troubleshoot WholeNodeJob and accounting issues Marco: Trying to use condor_config_val -dump as part of config generation, but condor_config_val does not show where multi-line values end; this has been reported upstream. OSG DevOps \u00b6 No updates this week Discussion \u00b6 None this week OSG Release Team \u00b6 No updates this week Discussion \u00b6 None this week","title":"March 29, 2022"},{"location":"meetings/2022/TechArea20220329/#osg-technology-area-meeting-29-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 29 March 2022"},{"location":"meetings/2022/TechArea20220329/#announcements","text":"TimT out next week","title":"Announcements"},{"location":"meetings/2022/TechArea20220329/#triage-duty","text":"This week: TimT Next week: BrianL 18 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220329/#jira-as-of-monday","text":"# of tickets \u0394 State 179 -4 Open 42 +0 Selected for Dev 29 +0 In Progress 14 +0 Dev Complete 5 -9 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220329/#osg-software-team","text":"Doc focus friday AI (Mat): Release osg-scitokens-mapfile-7 with HCC token mapping AI (Mat): kick off VMU tests for cigetcert AI (BrianL): release osg-ce with OSG_SERIES schedd attr AI (BrianL): python3-rrdtool for EL7","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220329/#discussion","text":"GlideinWMS 3.7.7 in progress; working on putting the token from the HTCondor-CE collector in the correct location. GlideinWMS 3.9.5 ETA ~3 weeks, including the scitoken credential plugin interface","title":"Discussion"},{"location":"meetings/2022/TechArea20220329/#support-update","text":"UNL (BrianL, Derek): helped troubleshoot WholeNodeJob and accounting issues Marco: Trying to use condor_config_val -dump as part of config generation, but condor_config_val does not show where multi-line values end; this has been reported upstream.","title":"Support Update"},{"location":"meetings/2022/TechArea20220329/#osg-devops","text":"No updates this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220329/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220329/#osg-release-team","text":"No updates this week","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220329/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220405/","text":"OSG Technology Area Meeting, 5 April 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat Announcements \u00b6 TimT OOO this week BrianL largely unavailable next week due to ITLP workshop Mat OOO Apr 15-29 Next week's meeting canceled Triage Duty \u00b6 This week: BrianL Next week: Mat 16 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 182 +3 Open 40 -2 Selected for Dev 30 +1 In Progress 13 -1 Dev Complete 9 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today: Dex for Tiger Update CHTC cache/origin Upgrade production GLOW frontend AI (Mat): increase default key size in renew proxy (SOFTWARE-5112) AI (Mat): document xcache (and xrootd?) upgrade to 3.6 (SOFTWARE-5109) AI (BrianL): python3-rrdtool for EL7 (SOFTWARE-5080) AI (BrianL): update VOMS clients default proxy key bit length to 2048 bits (SOFTWARE-4889) Discussion \u00b6 Marco: adding small requested changes to 3.7.7; 3.9.5 in progress, including the code to generate scitokens and wlcg tokens using an external script BrianB ran into an issue with an expired GLOW proxy causing a failure at the factory, even though token auth was enabled; he will send Marco the configuration that caused it CMS is still sending 1024-bit proxies which no longer work on EL 8. We need to find out where their proxies are generated and ask them to upgrade. EL 8 can be configured to accept 1024-bit proxies again, but this makes sites less secure so we do not want to recommend it New security release of Go upcoming; no details on the issue yet, but we may need to rebuild our software if it's affected CMS has requested that we build worker node images using Alma Linux, because they have not validated CentOS Stream 8. (WLCG sites in general have been avoiding Stream 8 because it goes EOL in the middle of Run 3.) OS SW does not currently test Alma but that would not be too difficult to add Support Update \u00b6 OSG Connect (BrianL): help with AP update to OSG 3.6 UNL (Derek): Correct whole node GRACC accounting UNL (Derek): help with GRACC records issues. Since UNL is running OSG 3.5 for now, they can use the condor batch system probe CRIC (Mat): with BrianB's help found a Topology issue that was causing SSL errors for CRIC, caused by CentOS Stream 8 dropping a needed package from their default container image OSG DevOps \u00b6 Go update is coming thursday, will be watching for possible impact on OSG things. Security team is notified. Working on shoveler docs https://github.com/opensciencegrid/docs/pull/959 Discussion \u00b6 None this week OSG Release Team \u00b6 No updates this week Discussion \u00b6 None this week","title":"April 5, 2022"},{"location":"meetings/2022/TechArea20220405/#osg-technology-area-meeting-5-april-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 5 April 2022"},{"location":"meetings/2022/TechArea20220405/#announcements","text":"TimT OOO this week BrianL largely unavailable next week due to ITLP workshop Mat OOO Apr 15-29 Next week's meeting canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220405/#triage-duty","text":"This week: BrianL Next week: Mat 16 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220405/#jira-as-of-monday","text":"# of tickets \u0394 State 182 +3 Open 40 -2 Selected for Dev 30 +1 In Progress 13 -1 Dev Complete 9 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220405/#osg-software-team","text":"Kubernetes hackathon today: Dex for Tiger Update CHTC cache/origin Upgrade production GLOW frontend AI (Mat): increase default key size in renew proxy (SOFTWARE-5112) AI (Mat): document xcache (and xrootd?) upgrade to 3.6 (SOFTWARE-5109) AI (BrianL): python3-rrdtool for EL7 (SOFTWARE-5080) AI (BrianL): update VOMS clients default proxy key bit length to 2048 bits (SOFTWARE-4889)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220405/#discussion","text":"Marco: adding small requested changes to 3.7.7; 3.9.5 in progress, including the code to generate scitokens and wlcg tokens using an external script BrianB ran into an issue with an expired GLOW proxy causing a failure at the factory, even though token auth was enabled; he will send Marco the configuration that caused it CMS is still sending 1024-bit proxies which no longer work on EL 8. We need to find out where their proxies are generated and ask them to upgrade. EL 8 can be configured to accept 1024-bit proxies again, but this makes sites less secure so we do not want to recommend it New security release of Go upcoming; no details on the issue yet, but we may need to rebuild our software if it's affected CMS has requested that we build worker node images using Alma Linux, because they have not validated CentOS Stream 8. (WLCG sites in general have been avoiding Stream 8 because it goes EOL in the middle of Run 3.) OS SW does not currently test Alma but that would not be too difficult to add","title":"Discussion"},{"location":"meetings/2022/TechArea20220405/#support-update","text":"OSG Connect (BrianL): help with AP update to OSG 3.6 UNL (Derek): Correct whole node GRACC accounting UNL (Derek): help with GRACC records issues. Since UNL is running OSG 3.5 for now, they can use the condor batch system probe CRIC (Mat): with BrianB's help found a Topology issue that was causing SSL errors for CRIC, caused by CentOS Stream 8 dropping a needed package from their default container image","title":"Support Update"},{"location":"meetings/2022/TechArea20220405/#osg-devops","text":"Go update is coming thursday, will be watching for possible impact on OSG things. Security team is notified. Working on shoveler docs https://github.com/opensciencegrid/docs/pull/959","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220405/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220405/#osg-release-team","text":"No updates this week","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220405/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220419/","text":"OSG Technology Area Meeting, 19 April 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, TimT Announcements \u00b6 Mat OOO Apr 15-29 Carl OOO Apr 21-25 BrianL OOO Apr 28-29 Triage Duty \u00b6 This week: TimT Next week: BrianL 13 (-3) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 185 +4 Open 3 -6 Selected for Dev 29 +0 In Progress 20 +6 Dev Complete 14 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today: investigate condor failing to start in backfill containers Primary MkDocs repositories being moved to the osg-htc GitHub organization FNAL reports an issue with osg-pki-tools that needs to be addressed in OSG 3.6. Should have a fix by early next week. AI (BrianL): add release series tags for backfill containers and merge new tagging policy Discussion \u00b6 GlideinWMS: Working on RCs, including a fix for communication issues between 3.9 frontends to a 3.7 factory Software team will apply a packaging patch to fix an issue with EL7 GlideinWMS installations in case the RC isn't ready for Operations in time Decision Engine 2.0 RC is coming soon; Marco will provide regular updates from the GIL investigation Support Update \u00b6 BNL (BrianL): investigating an issue with write auth failures using the xroot protocol OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.6 CVMFS 2.9.2 cigetcert 1.20 osg-ce 3.6-5 vault 1.10, htvault-config 1.12, htgettoken 1.11 osg-xrootd 3.6-16 (stash-cache crash with VOMS) VOMS default proxy key length OSG 3.6, OSG 3.5-upcoming HTCondor-CE 5.1.4 xcache 2.2.0, xcache 3.0.0 OSG 3.5-upcoming osg-xrootd Ready for Release Nothing yet Discussion \u00b6 3.5 to 3.6 minefield upgrade failures with HTCondor-CE due to our packaging of rrdtool","title":"April 19, 2022"},{"location":"meetings/2022/TechArea20220419/#osg-technology-area-meeting-19-april-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 19 April 2022"},{"location":"meetings/2022/TechArea20220419/#announcements","text":"Mat OOO Apr 15-29 Carl OOO Apr 21-25 BrianL OOO Apr 28-29","title":"Announcements"},{"location":"meetings/2022/TechArea20220419/#triage-duty","text":"This week: TimT Next week: BrianL 13 (-3) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220419/#jira-as-of-monday","text":"# of tickets \u0394 State 185 +4 Open 3 -6 Selected for Dev 29 +0 In Progress 20 +6 Dev Complete 14 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220419/#osg-software-team","text":"Kubernetes hackathon today: investigate condor failing to start in backfill containers Primary MkDocs repositories being moved to the osg-htc GitHub organization FNAL reports an issue with osg-pki-tools that needs to be addressed in OSG 3.6. Should have a fix by early next week. AI (BrianL): add release series tags for backfill containers and merge new tagging policy","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220419/#discussion","text":"GlideinWMS: Working on RCs, including a fix for communication issues between 3.9 frontends to a 3.7 factory Software team will apply a packaging patch to fix an issue with EL7 GlideinWMS installations in case the RC isn't ready for Operations in time Decision Engine 2.0 RC is coming soon; Marco will provide regular updates from the GIL investigation","title":"Discussion"},{"location":"meetings/2022/TechArea20220419/#support-update","text":"BNL (BrianL): investigating an issue with write auth failures using the xroot protocol","title":"Support Update"},{"location":"meetings/2022/TechArea20220419/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220419/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220419/#osg-release-team","text":"Ready for Testing OSG 3.6 CVMFS 2.9.2 cigetcert 1.20 osg-ce 3.6-5 vault 1.10, htvault-config 1.12, htgettoken 1.11 osg-xrootd 3.6-16 (stash-cache crash with VOMS) VOMS default proxy key length OSG 3.6, OSG 3.5-upcoming HTCondor-CE 5.1.4 xcache 2.2.0, xcache 3.0.0 OSG 3.5-upcoming osg-xrootd Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220419/#discussion_2","text":"3.5 to 3.6 minefield upgrade failures with HTCondor-CE due to our packaging of rrdtool","title":"Discussion"},{"location":"meetings/2022/TechArea20220426/","text":"OSG Technology Area Meeting, 26 April 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Announcements \u00b6 Mat OOO Apr 15-29 BrianL OOO Apr 28-29 Triage Duty \u00b6 This week: Carl Next week: BrianL 13 (+0) open FreshDesk tickets 2 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs Factory host cert expires on Apr 28; central collector host cert expires on May 6 OSG 3.5 EOL at the end of the week! Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5 Discussion \u00b6 None this week Support Update \u00b6 None this week OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release OSG 3.5 and OSG 3.6 CA Certificates based on IGTF 1.116 OSG 3.6 CVMFS 2.9.2: Bug fix release cigetgert 1.20: works better with CILogon's AWS infrastructure osg-ce 3.6-5 Add OSG_SERIES = 3.6 as a schedd attribute Remove default BATCH_GAHP configuration now provided by upstream osg-xrootd 3.6-16 Fix stash-cache: enabling VOMS causes unauth cache to crash vault 1.10, htvault 1.12 htgettoken 1.11 VOMS 2: Update default proxy certificate key length to 2048 bits Upcoming: HTCondor 9.8.1 Support for Heterogeneous GPUs, some configuration required Allow HTCondor to utilize grid sites requiring multi-factor authentication Technology preview: bring your own resources from HPC clusters Fix HTCondor startup failure with certain complex network configurations Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS Discussion \u00b6 None this week","title":"April 26, 2022"},{"location":"meetings/2022/TechArea20220426/#osg-technology-area-meeting-26-april-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending:","title":"OSG Technology Area Meeting, 26 April 2022"},{"location":"meetings/2022/TechArea20220426/#announcements","text":"Mat OOO Apr 15-29 BrianL OOO Apr 28-29","title":"Announcements"},{"location":"meetings/2022/TechArea20220426/#triage-duty","text":"This week: Carl Next week: BrianL 13 (+0) open FreshDesk tickets 2 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220426/#jira-as-of-monday","text":"# of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220426/#osg-software-team","text":"Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs Factory host cert expires on Apr 28; central collector host cert expires on May 6 OSG 3.5 EOL at the end of the week! Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220426/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220426/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20220426/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220426/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220426/#osg-release-team","text":"Ready for Release OSG 3.5 and OSG 3.6 CA Certificates based on IGTF 1.116 OSG 3.6 CVMFS 2.9.2: Bug fix release cigetgert 1.20: works better with CILogon's AWS infrastructure osg-ce 3.6-5 Add OSG_SERIES = 3.6 as a schedd attribute Remove default BATCH_GAHP configuration now provided by upstream osg-xrootd 3.6-16 Fix stash-cache: enabling VOMS causes unauth cache to crash vault 1.10, htvault 1.12 htgettoken 1.11 VOMS 2: Update default proxy certificate key length to 2048 bits Upcoming: HTCondor 9.8.1 Support for Heterogeneous GPUs, some configuration required Allow HTCondor to utilize grid sites requiring multi-factor authentication Technology preview: bring your own resources from HPC clusters Fix HTCondor startup failure with certain complex network configurations Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220426/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220503/","text":"OSG Technology Area Meeting, 3 May 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT Announcements \u00b6 OSG 3.5 EOL! Doc focus this Friday, primarily concentrated on removing old OSG 3.5 documentation. Triage Duty \u00b6 This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 1 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! AI (Carl): Make CronJob for fixing up user GIDs in COManage. AI (Mat): Investigate auto-update failures in the PATh facility Kubernetes pool. AI (BrianL): Move FE cert-manager patches to base AI (BrianL): Investigate upgrade path from Flux v1 to Flux v2 Doc focus this Friday Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs AI (BrianL): Work with JeffD to debug site failures starting after OSG 3.6 upgrades. AI (BrianL): Respond to Scott Koranda regarding missing EPPNs in COManage. AI (Carl): Remove certinfo usage from Gratia. AI (Mat): Renew central collector host cert (which expires on May 6); UNL SANs are no longer necessary. AI (Mat): Register PATh Facility Execute Points in Topology. AI (TimT): Test HTCondor 9.9.0 in CHTC; new remote management features might impact glideins so those will need extra testing. Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5 Allow for custom workflows in opensciencegrid/images Discussion \u00b6 Added a \"contrib\" directory to the opensciencegrid/images repo so people can contribute images; the first contributor was FNAL with some FTS images. There is a danger of the GitHub Actions for the repo taking too long; the Software Team will investigate fixes as necessary. Support Update \u00b6 BNL (Derek): Debugging various randomly occurring slow or failing transfers with XRootD-Standalone GRACC (Derek): Debugging CEs that have stopped reporting to GRACC after upgrading to OSG 3.6; will stay in touch with the Software Team regarding necessary software/packaging/documentation fixes resulting from these. GIL (Carl): Debug Igor's issue with viewing Topology resources using his COManage credentials. OSG DevOps \u00b6 A few feature requests / bug fixes for StashCP. Still helping shoveler support for token auto-updating. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS Discussion \u00b6 None this week","title":"May 3, 2022"},{"location":"meetings/2022/TechArea20220503/#osg-technology-area-meeting-3-may-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 3 May 2022"},{"location":"meetings/2022/TechArea20220503/#announcements","text":"OSG 3.5 EOL! Doc focus this Friday, primarily concentrated on removing old OSG 3.5 documentation.","title":"Announcements"},{"location":"meetings/2022/TechArea20220503/#triage-duty","text":"This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 1 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220503/#jira-as-of-monday","text":"# of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220503/#osg-software-team","text":"Kubernetes Hackathon today! AI (Carl): Make CronJob for fixing up user GIDs in COManage. AI (Mat): Investigate auto-update failures in the PATh facility Kubernetes pool. AI (BrianL): Move FE cert-manager patches to base AI (BrianL): Investigate upgrade path from Flux v1 to Flux v2 Doc focus this Friday Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs AI (BrianL): Work with JeffD to debug site failures starting after OSG 3.6 upgrades. AI (BrianL): Respond to Scott Koranda regarding missing EPPNs in COManage. AI (Carl): Remove certinfo usage from Gratia. AI (Mat): Renew central collector host cert (which expires on May 6); UNL SANs are no longer necessary. AI (Mat): Register PATh Facility Execute Points in Topology. AI (TimT): Test HTCondor 9.9.0 in CHTC; new remote management features might impact glideins so those will need extra testing. Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5 Allow for custom workflows in opensciencegrid/images","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220503/#discussion","text":"Added a \"contrib\" directory to the opensciencegrid/images repo so people can contribute images; the first contributor was FNAL with some FTS images. There is a danger of the GitHub Actions for the repo taking too long; the Software Team will investigate fixes as necessary.","title":"Discussion"},{"location":"meetings/2022/TechArea20220503/#support-update","text":"BNL (Derek): Debugging various randomly occurring slow or failing transfers with XRootD-Standalone GRACC (Derek): Debugging CEs that have stopped reporting to GRACC after upgrading to OSG 3.6; will stay in touch with the Software Team regarding necessary software/packaging/documentation fixes resulting from these. GIL (Carl): Debug Igor's issue with viewing Topology resources using his COManage credentials.","title":"Support Update"},{"location":"meetings/2022/TechArea20220503/#osg-devops","text":"A few feature requests / bug fixes for StashCP. Still helping shoveler support for token auto-updating.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220503/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220503/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220503/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220510/","text":"OSG Technology Area Meeting, 10 May 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL OOO next week HTCondor week May 23 - 26 Next two meetings canceled Triage Duty \u00b6 This week: Mat Next week: TimT 13 (-3) open FreshDesk tickets 2 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 192 +5 Open 27 -2 Selected for Dev 34 +6 In Progress 17 +1 Dev Complete 9 -7 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 AI (Carl) remove certinfo log messages AI (Mat) XRootD 5.4.3 RC1 Next week: AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing Discussion \u00b6 GlideinWMS stakeholders meeting tomorrow; 3.9.3 release planned. Support Update \u00b6 ComputeCanada (BrianL): troubleshoot missing OSG_WN_TMP due to HTCondor change from GLITE_LOCATION to BLAHPD_LOCATION in HTCondor 9.3.0 Carl: Continue to assist Igor with authentication issues. Mats can give him a manually generated token to keep things moving along. ODU (Mat): Investigate failure to launch Singularity from CVMFS. UTC-EPYC (Mat): Investigate random job failures; request assistance from HTCondor developers. JLab (Mat): Setting up a cache and an origin; they are planning on having both on one host (in containers) and using the same cert. This will cause accounting issues (the StashCache graphs are keyed by hostname) but the other central XRootD services should handle it properly. OSG DevOps \u00b6 A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.6 WN client: Fix missing packages in tarball HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2 Discussion \u00b6 None this week","title":"May 10, 2022"},{"location":"meetings/2022/TechArea20220510/#osg-technology-area-meeting-10-may-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 10 May 2022"},{"location":"meetings/2022/TechArea20220510/#announcements","text":"BrianL OOO next week HTCondor week May 23 - 26 Next two meetings canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220510/#triage-duty","text":"This week: Mat Next week: TimT 13 (-3) open FreshDesk tickets 2 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220510/#jira-as-of-monday","text":"# of tickets \u0394 State 192 +5 Open 27 -2 Selected for Dev 34 +6 In Progress 17 +1 Dev Complete 9 -7 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220510/#osg-software-team","text":"OSG 3.6 AI (Carl) remove certinfo log messages AI (Mat) XRootD 5.4.3 RC1 Next week: AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220510/#discussion","text":"GlideinWMS stakeholders meeting tomorrow; 3.9.3 release planned.","title":"Discussion"},{"location":"meetings/2022/TechArea20220510/#support-update","text":"ComputeCanada (BrianL): troubleshoot missing OSG_WN_TMP due to HTCondor change from GLITE_LOCATION to BLAHPD_LOCATION in HTCondor 9.3.0 Carl: Continue to assist Igor with authentication issues. Mats can give him a manually generated token to keep things moving along. ODU (Mat): Investigate failure to launch Singularity from CVMFS. UTC-EPYC (Mat): Investigate random job failures; request assistance from HTCondor developers. JLab (Mat): Setting up a cache and an origin; they are planning on having both on one host (in containers) and using the same cert. This will cause accounting issues (the StashCache graphs are keyed by hostname) but the other central XRootD services should handle it properly.","title":"Support Update"},{"location":"meetings/2022/TechArea20220510/#osg-devops","text":"A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220510/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220510/#osg-release-team","text":"Ready for Testing OSG 3.6 WN client: Fix missing packages in tarball HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220510/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220531/","text":"OSG Technology Area Meeting, 31 May 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Ziyang, our new IRIS-HEP fellow, has joined. He will be working on network monitoring for XCache container deployments Triage Duty \u00b6 This week: Carl Next week: Mat 15 (+2) open FreshDesk tickets 1 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 190 +0 Open 31 -1 Selected for Dev 24 +0 In Progress 17 +1 Dev Complete 25 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon Mat: Autoupdates for Flux v2 on PATh Facility; can be tested on the backfill pilots since they are old. Mat: Fix backfill pilots and other broken pods on Tiger. Mat: Assist Cannon in debugging Topology on Tiger. BrianL: Test HTCondor-CE 5.1.4 by upgrading the Canary CE(s). BrianL: Deploy Dex. Some UW CSL-hosted services have had their certs expire. vdt.cs.wisc.edu (used for Koji) was migrated today. AI (TimT): Release 9.9.0 release candidate of HTCondor in the Open Pool. Planning to deprecate old interfaces before the start of the next LTS series. BrianB diagnosed shared port issues with 9.8.0 on the APs that he worked around by disabling IPv6. 9.9.0 should fix it. Tim will let Brian know once the upgrade is done, so Brian can re-enable IPv6. AI (Mat) Create new Topology endpoints for improved OSDF support. AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing Discussion \u00b6 None this week Support Update \u00b6 JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utilization from the Slurm side Carl: Requests assistance on unregistered pilot container Gratia probes. UTC-Epyc (Mat): Requests assistance for diagnosing random pilot deaths. Because rsyslog is broken on the site, we do not have pilot logs for the failed pilots. OSG DevOps \u00b6 A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing gratia-probe 2.6.1 Replace AuthToken* references with routed job attributes Fix mismatched type concatenation in Gratia record send Gratia: Set SCHEDD_CRON_LOG_NON_ZERO_EXIT = True in the htcondor-ce configuration Remove certinfo file log messages HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2 htvault-config-1.13 htgettoken 1.12 XCache 3.1.0 stashcp 6.7.5 HTCondor 9.0.13 Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations Upcoming HTCondor 9.9.0 A new authentication method for remote HTCondor administration Several changes to improve the security of connections Fix issue where DAGMan direct submission failed when using Kerberos The submission method is now recorded in the job ClassAd Singularity jobs can now pull from Docker style repositories The OWNER authorization level has been folded into the ADMINISTRATOR level Discussion \u00b6 None this week","title":"May 31, 2022"},{"location":"meetings/2022/TechArea20220531/#osg-technology-area-meeting-31-may-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 31 May 2022"},{"location":"meetings/2022/TechArea20220531/#announcements","text":"Ziyang, our new IRIS-HEP fellow, has joined. He will be working on network monitoring for XCache container deployments","title":"Announcements"},{"location":"meetings/2022/TechArea20220531/#triage-duty","text":"This week: Carl Next week: Mat 15 (+2) open FreshDesk tickets 1 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220531/#jira-as-of-monday","text":"# of tickets \u0394 State 190 +0 Open 31 -1 Selected for Dev 24 +0 In Progress 17 +1 Dev Complete 25 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220531/#osg-software-team","text":"Kubernetes Hackathon Mat: Autoupdates for Flux v2 on PATh Facility; can be tested on the backfill pilots since they are old. Mat: Fix backfill pilots and other broken pods on Tiger. Mat: Assist Cannon in debugging Topology on Tiger. BrianL: Test HTCondor-CE 5.1.4 by upgrading the Canary CE(s). BrianL: Deploy Dex. Some UW CSL-hosted services have had their certs expire. vdt.cs.wisc.edu (used for Koji) was migrated today. AI (TimT): Release 9.9.0 release candidate of HTCondor in the Open Pool. Planning to deprecate old interfaces before the start of the next LTS series. BrianB diagnosed shared port issues with 9.8.0 on the APs that he worked around by disabling IPv6. 9.9.0 should fix it. Tim will let Brian know once the upgrade is done, so Brian can re-enable IPv6. AI (Mat) Create new Topology endpoints for improved OSDF support. AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220531/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220531/#support-update","text":"JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utilization from the Slurm side Carl: Requests assistance on unregistered pilot container Gratia probes. UTC-Epyc (Mat): Requests assistance for diagnosing random pilot deaths. Because rsyslog is broken on the site, we do not have pilot logs for the failed pilots.","title":"Support Update"},{"location":"meetings/2022/TechArea20220531/#osg-devops","text":"A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220531/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220531/#osg-release-team","text":"Ready for Testing gratia-probe 2.6.1 Replace AuthToken* references with routed job attributes Fix mismatched type concatenation in Gratia record send Gratia: Set SCHEDD_CRON_LOG_NON_ZERO_EXIT = True in the htcondor-ce configuration Remove certinfo file log messages HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2 htvault-config-1.13 htgettoken 1.12 XCache 3.1.0 stashcp 6.7.5 HTCondor 9.0.13 Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations Upcoming HTCondor 9.9.0 A new authentication method for remote HTCondor administration Several changes to improve the security of connections Fix issue where DAGMan direct submission failed when using Kerberos The submission method is now recorded in the job ClassAd Singularity jobs can now pull from Docker style repositories The OWNER authorization level has been folded into the ADMINISTRATOR level","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220531/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220607/","text":"OSG Technology Area Meeting, 7 June 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Ziyang Announcements \u00b6 Mat OOO Jun 13 BrianL traveling Jun 13-16, OOO Jun 17 Next week's meeting canceled Triage Duty \u00b6 This week: Mat Next week: TimT 11 (-4) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +1 Open 32 +1 Selected for Dev 27 +3 In Progress 14 -3 Dev Complete 28 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus Friday afternoon JLab FE and VO certs expire next Thursday, Ops may need a reminder to update the certs next week BNL will be submitting EIC jobs via Harvester and will pass along a subject DN that we need added to the vo-client Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): backfill container should shut down upon HTCondor exit (SOFTWARE-4608) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) AI (Carl): remove duplicate contact entries in the Topology contact pages (SOFTWARE-5214) Discussion \u00b6 There are several Docker images that are built from individual GitHub repositories instead of the central \"images\" repository. They should be moved to the images repo; keep an eye on how well GitHub Actions workflows scale, though. COManage registration denials seem to be sticky; if you want to admit someone you have previously denied, you will have to expunge the CO Person record Support Update \u00b6 JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. They will lift the blacklisting of ScotsGrid to try to gather more info Belle II (BrianL): will be having a meeting this week to discuss token-based pilot submission Texas Tech (BrianL): new backfill container site, working on fixing COManage registrations WeNMR (BrianL): helping DIRAC developers test token-based pilot submission BNL (Mat): Experiencing CA failures with XRootD TPC. Their CA certificates look fine; Mat has requested that they perform some manual tests to try and isolate the error. The XRootD developers are Cc'ed on the ticket and can provide debugging assistance. OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.5 gratia-probe 2.6.1 Log schedd cron errors with newer versions of HTCondor Replace AuthToken* references with routed job attributes Remove certinfo flie log messages Fix crash on send failure HTCondor 9.0.13 : Bug fix release Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations HTCondor-CE 5.1.5 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Rename AuthToken attributes in the routed job to better support accounting Prevent GSI environment from pointing the job to the wrong certificates Fix issue where HTCondor-CE would need port 9618 open to start up XCache 3.1.0 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged XRootD 5.4.3 RC4 htvault-config 1.13 removes support for old style secret storage, requires htgettoken >= 1.7 htgettoken 1.12 avoids crash when verbose output includes UTF-8 osg-pki-tools 3.5.2 bug fix for osg-incommon-cert-request when using host file osg-release 3.6-5: Add osg-next yum repository osg-token-renewer 0.8.2 use oidc-agent's built-in password file option ensure tokens are renewed more frequently than their lifespan rrdtool 1.8.0-1.2.el7: make Python RRDtools available to GlideinWMS stashcp 6.7.5 Adds multi-file transfer and improved error messages relax download timeouts for file transfer plugin multiple bug fixes xrootd-multiuser 2.0.4 fix crash on EL8 Discussion \u00b6 Sometimes packages get stuck in Ready for Testing state because they are considered \"critical\" but no external people have provided feedback. Mat suggests amending our release policy such that critical packages are released after a month without negative feedback, even if no positive feedback has been received. Tim says that would be better for software that has received VMU testing or has been well tested outside of OSG. We have an IRIS-HEP metric to increase the percentage of packages tested in VMU; Brian will create tickets. Also discussed improving coordination of testing between OSG Operations and Software","title":"June 7, 2022"},{"location":"meetings/2022/TechArea20220607/#osg-technology-area-meeting-7-june-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Ziyang","title":"OSG Technology Area Meeting, 7 June 2022"},{"location":"meetings/2022/TechArea20220607/#announcements","text":"Mat OOO Jun 13 BrianL traveling Jun 13-16, OOO Jun 17 Next week's meeting canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220607/#triage-duty","text":"This week: Mat Next week: TimT 11 (-4) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220607/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +1 Open 32 +1 Selected for Dev 27 +3 In Progress 14 -3 Dev Complete 28 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220607/#osg-software-team","text":"Doc focus Friday afternoon JLab FE and VO certs expire next Thursday, Ops may need a reminder to update the certs next week BNL will be submitting EIC jobs via Harvester and will pass along a subject DN that we need added to the vo-client Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): backfill container should shut down upon HTCondor exit (SOFTWARE-4608) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) AI (Carl): remove duplicate contact entries in the Topology contact pages (SOFTWARE-5214)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220607/#discussion","text":"There are several Docker images that are built from individual GitHub repositories instead of the central \"images\" repository. They should be moved to the images repo; keep an eye on how well GitHub Actions workflows scale, though. COManage registration denials seem to be sticky; if you want to admit someone you have previously denied, you will have to expunge the CO Person record","title":"Discussion"},{"location":"meetings/2022/TechArea20220607/#support-update","text":"JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. They will lift the blacklisting of ScotsGrid to try to gather more info Belle II (BrianL): will be having a meeting this week to discuss token-based pilot submission Texas Tech (BrianL): new backfill container site, working on fixing COManage registrations WeNMR (BrianL): helping DIRAC developers test token-based pilot submission BNL (Mat): Experiencing CA failures with XRootD TPC. Their CA certificates look fine; Mat has requested that they perform some manual tests to try and isolate the error. The XRootD developers are Cc'ed on the ticket and can provide debugging assistance.","title":"Support Update"},{"location":"meetings/2022/TechArea20220607/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.5 gratia-probe 2.6.1 Log schedd cron errors with newer versions of HTCondor Replace AuthToken* references with routed job attributes Remove certinfo flie log messages Fix crash on send failure HTCondor 9.0.13 : Bug fix release Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations HTCondor-CE 5.1.5 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Rename AuthToken attributes in the routed job to better support accounting Prevent GSI environment from pointing the job to the wrong certificates Fix issue where HTCondor-CE would need port 9618 open to start up XCache 3.1.0 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged XRootD 5.4.3 RC4 htvault-config 1.13 removes support for old style secret storage, requires htgettoken >= 1.7 htgettoken 1.12 avoids crash when verbose output includes UTF-8 osg-pki-tools 3.5.2 bug fix for osg-incommon-cert-request when using host file osg-release 3.6-5: Add osg-next yum repository osg-token-renewer 0.8.2 use oidc-agent's built-in password file option ensure tokens are renewed more frequently than their lifespan rrdtool 1.8.0-1.2.el7: make Python RRDtools available to GlideinWMS stashcp 6.7.5 Adds multi-file transfer and improved error messages relax download timeouts for file transfer plugin multiple bug fixes xrootd-multiuser 2.0.4 fix crash on EL8","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220607/#discussion_1","text":"Sometimes packages get stuck in Ready for Testing state because they are considered \"critical\" but no external people have provided feedback. Mat suggests amending our release policy such that critical packages are released after a month without negative feedback, even if no positive feedback has been received. Tim says that would be better for software that has received VMU testing or has been well tested outside of OSG. We have an IRIS-HEP metric to increase the percentage of packages tested in VMU; Brian will create tickets. Also discussed improving coordination of testing between OSG Operations and Software","title":"Discussion"},{"location":"meetings/2022/TechArea20220621/","text":"OSG Technology Area Meeting, 21 June 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, Ziyang Announcements \u00b6 TimT OOO this week BrianL OOO Thu, Fri Triage Duty \u00b6 This week: Carl Next week: BrianL 13 (+2) open FreshDesk tickets 0 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 187 +3 Open 34 -3 Selected for Dev 29 +0 In Progress 22 +3 Dev Complete 5 -7 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) Discussion \u00b6 Sketched out a plan to split the Topology git repo into two, one for code and one for data Support Update \u00b6 CHTC (Derek, Mat): issues with authenticated access to origin-auth2001 OSPool (BrianL, Mat): many shadow failures due to an issue with the user job wrapper. Currently suspecting a startd cron script locking issue. JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. Seems like we're requesting 8 core pilots but only advertising single core slots. Hosted CEs (Carl): identified an FD file leak in the scitokens-cpp library","title":"June 21, 2022"},{"location":"meetings/2022/TechArea20220621/#osg-technology-area-meeting-21-june-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, Ziyang","title":"OSG Technology Area Meeting, 21 June 2022"},{"location":"meetings/2022/TechArea20220621/#announcements","text":"TimT OOO this week BrianL OOO Thu, Fri","title":"Announcements"},{"location":"meetings/2022/TechArea20220621/#triage-duty","text":"This week: Carl Next week: BrianL 13 (+2) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220621/#jira-as-of-monday","text":"# of tickets \u0394 State 187 +3 Open 34 -3 Selected for Dev 29 +0 In Progress 22 +3 Dev Complete 5 -7 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220621/#osg-software-team","text":"Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220621/#discussion","text":"Sketched out a plan to split the Topology git repo into two, one for code and one for data","title":"Discussion"},{"location":"meetings/2022/TechArea20220621/#support-update","text":"CHTC (Derek, Mat): issues with authenticated access to origin-auth2001 OSPool (BrianL, Mat): many shadow failures due to an issue with the user job wrapper. Currently suspecting a startd cron script locking issue. JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. Seems like we're requesting 8 core pilots but only advertising single core slots. Hosted CEs (Carl): identified an FD file leak in the scitokens-cpp library","title":"Support Update"},{"location":"meetings/2022/TechArea20220628/","text":"OSG Technology Area Meeting, 28 June 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Ziyang Announcements \u00b6 BrianL OOO Fri, Tue Next week's meeting canceled Triage Duty \u00b6 This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 189 +2 Open 33 -1 Selected for Dev 27 -2 In Progress 17 -5 Dev Complete 8 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon this afternoon Doc focus afternoon of Jul 15 Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) Discussion \u00b6 We had a short discussion regarding the appropriate fix for the way that GlideinWMS writes to glidein_config ; BrianL will discuss thoughts with the HTCSS dev team and get back to Marco Support Update \u00b6 OSPool (BrianL, Mat): discovered GlideinWMS file locking issue causing user job wrapper shadow exceptions","title":"June 28, 2022"},{"location":"meetings/2022/TechArea20220628/#osg-technology-area-meeting-28-june-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Ziyang","title":"OSG Technology Area Meeting, 28 June 2022"},{"location":"meetings/2022/TechArea20220628/#announcements","text":"BrianL OOO Fri, Tue Next week's meeting canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220628/#triage-duty","text":"This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220628/#jira-as-of-monday","text":"# of tickets \u0394 State 189 +2 Open 33 -1 Selected for Dev 27 -2 In Progress 17 -5 Dev Complete 8 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220628/#osg-software-team","text":"Kubernetes hackathon this afternoon Doc focus afternoon of Jul 15 Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220628/#discussion","text":"We had a short discussion regarding the appropriate fix for the way that GlideinWMS writes to glidein_config ; BrianL will discuss thoughts with the HTCSS dev team and get back to Marco","title":"Discussion"},{"location":"meetings/2022/TechArea20220628/#support-update","text":"OSPool (BrianL, Mat): discovered GlideinWMS file locking issue causing user job wrapper shadow exceptions","title":"Support Update"},{"location":"meetings/2022/TechArea20220726/","text":"OSG Technology Area Meeting, 26 July 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Derek out this week Triage Duty \u00b6 This week: Mat Next week: TimT 8 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 189 +0 Open 30 +2 Selected for Dev 31 +0 In Progress 17 -5 Dev Complete 16 +6 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): high prio (must be completed this week), continue Derek's GRACC correction work for Purdue Kubernetes hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (Mat): Validate CHTC-canary2 CE; see if pilots are filling up /tmp on exec nodes and why AI (Carl): enumerate differences between Kubernetes caches (SOFTWARE-5259) AI (BrianL): use Dex and COManage to give external collaborators read-only access to the osgdev namespace Discussion \u00b6 CMS running into problems with their XRootD redirector where due to a misconfiguration, writes went to random hosts. They would like a config knob to prevent this kind of misconfiguration; BrianL suggested that they send mail to the XRootD development list. Support Update \u00b6 Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots IceCube (BrianL): investigate OS Registry failure to issue token due to split of OSPool CCB/CM FNAL (BrianL): diagnose FD leaks affecting Bridges2/Expanse Hosted CEs FNAL (Carl): waiting for response regarding testing of new version of gratia-probes BNL (Mat): GermanGrid CA signed with SHA1; asked Doug if his crypto policy allows that OSG Release Team \u00b6 Ready for Testing gratia-probe 2.7.0 xrootd-monitoring-shoveler 1.1.2 HTCondor 9.10.1 blahp 2.2.1 HTCondor 9.0.15 CVMFS 2.9.3 osg-xrootd 3.6-18 XRootD 5.4.3-1.2 htgettoken 1.15 osg-release 3.5-9 Discussion \u00b6 Release this week.","title":"July 26, 2022"},{"location":"meetings/2022/TechArea20220726/#osg-technology-area-meeting-26-july-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 26 July 2022"},{"location":"meetings/2022/TechArea20220726/#announcements","text":"Derek out this week","title":"Announcements"},{"location":"meetings/2022/TechArea20220726/#triage-duty","text":"This week: Mat Next week: TimT 8 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220726/#jira-as-of-monday","text":"# of tickets \u0394 State 189 +0 Open 30 +2 Selected for Dev 31 +0 In Progress 17 -5 Dev Complete 16 +6 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220726/#osg-software-team","text":"AI (Carl): high prio (must be completed this week), continue Derek's GRACC correction work for Purdue Kubernetes hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (Mat): Validate CHTC-canary2 CE; see if pilots are filling up /tmp on exec nodes and why AI (Carl): enumerate differences between Kubernetes caches (SOFTWARE-5259) AI (BrianL): use Dex and COManage to give external collaborators read-only access to the osgdev namespace","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220726/#discussion","text":"CMS running into problems with their XRootD redirector where due to a misconfiguration, writes went to random hosts. They would like a config knob to prevent this kind of misconfiguration; BrianL suggested that they send mail to the XRootD development list.","title":"Discussion"},{"location":"meetings/2022/TechArea20220726/#support-update","text":"Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots IceCube (BrianL): investigate OS Registry failure to issue token due to split of OSPool CCB/CM FNAL (BrianL): diagnose FD leaks affecting Bridges2/Expanse Hosted CEs FNAL (Carl): waiting for response regarding testing of new version of gratia-probes BNL (Mat): GermanGrid CA signed with SHA1; asked Doug if his crypto policy allows that","title":"Support Update"},{"location":"meetings/2022/TechArea20220726/#osg-release-team","text":"Ready for Testing gratia-probe 2.7.0 xrootd-monitoring-shoveler 1.1.2 HTCondor 9.10.1 blahp 2.2.1 HTCondor 9.0.15 CVMFS 2.9.3 osg-xrootd 3.6-18 XRootD 5.4.3-1.2 htgettoken 1.15 osg-release 3.5-9","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220726/#discussion_1","text":"Release this week.","title":"Discussion"},{"location":"meetings/2022/TechArea20220802/","text":"OSG Technology Area Meeting, 2 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 Mat OOO Wed - Fri TimT OOO Thu + Fri BrianL OOO Fri + Mon Triage Duty \u00b6 This week: Carl Next week: TimT 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket Discussion \u00b6 Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; he and Derek will debug. Support Update \u00b6 Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. CLAS12 (Derek): Helping fix gratia, /var/lock/condor failed to be created. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, not sure what's going on, debugging. (Ugh, the issuer is complicated) OSG Release Team \u00b6 Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes) Discussion \u00b6 No release this week","title":"August 2, 2022"},{"location":"meetings/2022/TechArea20220802/#osg-technology-area-meeting-2-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 2 August 2022"},{"location":"meetings/2022/TechArea20220802/#announcements","text":"Mat OOO Wed - Fri TimT OOO Thu + Fri BrianL OOO Fri + Mon","title":"Announcements"},{"location":"meetings/2022/TechArea20220802/#triage-duty","text":"This week: Carl Next week: TimT 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220802/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220802/#osg-software-team","text":"AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220802/#discussion","text":"Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; he and Derek will debug.","title":"Discussion"},{"location":"meetings/2022/TechArea20220802/#support-update","text":"Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. CLAS12 (Derek): Helping fix gratia, /var/lock/condor failed to be created. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, not sure what's going on, debugging. (Ugh, the issuer is complicated)","title":"Support Update"},{"location":"meetings/2022/TechArea20220802/#osg-release-team","text":"Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220802/#discussion_1","text":"No release this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220809/","text":"OSG Technology Area Meeting, 9 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Derek, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: ? 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket Discussion \u00b6 Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; Derek will send email to ToddM regarding this feature. Support Update \u00b6 Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, Fixed! The JSON of the user-config was not valid (my fault, typo) OSG Release Team \u00b6 Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes) Discussion \u00b6 No release this week","title":"August 9, 2022"},{"location":"meetings/2022/TechArea20220809/#osg-technology-area-meeting-9-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 9 August 2022"},{"location":"meetings/2022/TechArea20220809/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220809/#triage-duty","text":"This week: TimT Next week: ? 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220809/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220809/#osg-software-team","text":"Kubernetes Hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220809/#discussion","text":"Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; Derek will send email to ToddM regarding this feature.","title":"Discussion"},{"location":"meetings/2022/TechArea20220809/#support-update","text":"Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, Fixed! The JSON of the user-config was not valid (my fault, typo)","title":"Support Update"},{"location":"meetings/2022/TechArea20220809/#osg-release-team","text":"Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220809/#discussion_1","text":"No release this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220816/","text":"OSG Technology Area Meeting, 16 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Mat, TimT Announcements \u00b6 Mat, TimT out of office next Monday. Triage Duty \u00b6 This week: Brian Next week: Carl 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 187 -7 Open 38 +6 Selected for Dev 35 +5 In Progress 18 +1 Dev Complete 3 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Use COManage IDs in Topology wherever possible! AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): set up expiration notification template and workflow; contact COManage developers for assistance if needed AI (Carl): complete custom workflows ticket; meet with BrianL and Mat to discuss use cases for workflows Discussion \u00b6 The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday. Support Update \u00b6 FIU (Mat) working with FIU to resolve connection issues while attempting to mirror OSG Software repos. FNAL (Carl) worked with Yuijun and Kevin Retzke on Gratia probe changes. Software team work is done for now; at this point Yuijun and Kevin should discuss their requirements. OSG Release Team \u00b6 Ready for Testing xrootd-monitoring-shoveler 1.1.2 HTCondor 9.0.16 (important bug fixes) Upcoming: HTCondor 9.11.0 RC2 Discussion \u00b6 - Release xrootd-monitoring-shoveler and HTCondor 9.0.16 this week.","title":"August 16, 2022"},{"location":"meetings/2022/TechArea20220816/#osg-technology-area-meeting-16-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 16 August 2022"},{"location":"meetings/2022/TechArea20220816/#announcements","text":"Mat, TimT out of office next Monday.","title":"Announcements"},{"location":"meetings/2022/TechArea20220816/#triage-duty","text":"This week: Brian Next week: Carl 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220816/#jira-as-of-monday","text":"# of tickets \u0394 State 187 -7 Open 38 +6 Selected for Dev 35 +5 In Progress 18 +1 Dev Complete 3 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220816/#osg-software-team","text":"Use COManage IDs in Topology wherever possible! AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): set up expiration notification template and workflow; contact COManage developers for assistance if needed AI (Carl): complete custom workflows ticket; meet with BrianL and Mat to discuss use cases for workflows","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220816/#discussion","text":"The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday.","title":"Discussion"},{"location":"meetings/2022/TechArea20220816/#support-update","text":"FIU (Mat) working with FIU to resolve connection issues while attempting to mirror OSG Software repos. FNAL (Carl) worked with Yuijun and Kevin Retzke on Gratia probe changes. Software team work is done for now; at this point Yuijun and Kevin should discuss their requirements.","title":"Support Update"},{"location":"meetings/2022/TechArea20220816/#osg-release-team","text":"Ready for Testing xrootd-monitoring-shoveler 1.1.2 HTCondor 9.0.16 (important bug fixes) Upcoming: HTCondor 9.11.0 RC2","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220816/#discussion_1","text":"- Release xrootd-monitoring-shoveler and HTCondor 9.0.16 this week.","title":"Discussion"},{"location":"meetings/2022/TechArea20220823/","text":"OSG Technology Area Meeting, 23 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Carl, Marco Mambelli, Ziyang Announcements \u00b6 Carl out Wednesdays Triage Duty \u00b6 This week: Carl Next week: Carl 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 190 +3 Open 44 +6 Selected for Dev 24 -11 In Progress 144 -4 Dev Complete 5 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today, already discussed things on the docket Fields (like github username) are editible in comanage; would be good to test editing especially if we are non-admins Marco: has PR for GWMS item; troubleshooting Mats's issue AI (BrianL, Mat, Carl) discuss all the container building use cases AI (Mat): check in with Fabio to see where PR for hawaii origin stands Discussion \u00b6 Do we want to fork off existing SLATE chart, or do we just make the changes? Eventually want cache in tiger for our purposes. The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday. Support Update \u00b6 None this week OSG Release Team \u00b6 TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp Discussion \u00b6 TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"August 23, 2022"},{"location":"meetings/2022/TechArea20220823/#osg-technology-area-meeting-23-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Carl, Marco Mambelli, Ziyang","title":"OSG Technology Area Meeting, 23 August 2022"},{"location":"meetings/2022/TechArea20220823/#announcements","text":"Carl out Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20220823/#triage-duty","text":"This week: Carl Next week: Carl 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220823/#jira-as-of-monday","text":"# of tickets \u0394 State 190 +3 Open 44 +6 Selected for Dev 24 -11 In Progress 144 -4 Dev Complete 5 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220823/#osg-software-team","text":"Kubernetes hackathon today, already discussed things on the docket Fields (like github username) are editible in comanage; would be good to test editing especially if we are non-admins Marco: has PR for GWMS item; troubleshooting Mats's issue AI (BrianL, Mat, Carl) discuss all the container building use cases AI (Mat): check in with Fabio to see where PR for hawaii origin stands","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220823/#discussion","text":"Do we want to fork off existing SLATE chart, or do we just make the changes? Eventually want cache in tiger for our purposes. The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday.","title":"Discussion"},{"location":"meetings/2022/TechArea20220823/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20220823/#osg-release-team","text":"TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220823/#discussion_1","text":"TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220830/","text":"OSG Technology Area Meeting, 30 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT, Ziyang Announcements \u00b6 Carl out Wednesdays Ziyang's last day is today Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): OSDF origin chart AI (Mat): Assist Fabio with setting up the University of Hawaii origin; we are currently waiting on them for Resource Group information, after which Mat will help with Data Federation information -- the format of that information is new AI (Carl): XRootD 5.5.0 release; contact Mat for assistance as needed AI (Carl): Review various PRs for the Tiger Kubernetes cluster AI (BrianL): Review and reprioritize Software Team JIRA tickets AI (BrianL): Review PATh metrics for the monthly report before the end of the month Discussion \u00b6 Marco: GlideinWMS 3.9.6 expected by the end of the week; fixed setup issues noticed by Mat and others, and added a token generator Support Update \u00b6 USC (BrianL): helped solve issues with backfill containers; issues caused by tokens and using an outdated image. Admins were surprised that the pilots exited because they didn't get any jobs; this event should be communicated more clearly, perhaps in the container logs Virgo (BrianL): helped Jason resolve issues with Virgo proxy generation due to upstream VOMS server cert update LIGO (Carl): assisted Peter Couvares with getting the HTCondor version on a CE LIGO (Carl): received formal request from LIGO for first-class SIF file support on the OS Pool; redirected to Jason but Mats should also be added -- for now this is a question of OS Pool policy OS Pool (Derek): user wanted to have a very large file accessible on /cvmfs/stash.osgstorage.org . Derek increased the max file size from 26 GB to 500 GB. This change should not affect anything except large files, but staff should keep an eye out for issues MIT (Derek): Credential for lightweight issuer, hopefully can be resolved with a few more back and forths. WTAMU (Derek): observed a difference between pilot and payload hours -- looks to be due to the site having huge slots (64 cores) with Glideins pilots retiring (finishing old jobs but no longer accepting new jobs) but with a handful of long, small jobs keeping the pilot alive. Mats suggested increasing the pilot lifetime OS Pool (Derek): cvmfs-singularity-sync started deleting containers on CVMFS yesterday (8/29). The problem was fixed and the containers restored; the issue was due to code changes in order to support tag wildcards on hub.opensciencegrid.org. Derek is writing a full incident report. OSG Release Team \u00b6 TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp Discussion \u00b6 TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"August 30, 2022"},{"location":"meetings/2022/TechArea20220830/#osg-technology-area-meeting-30-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT, Ziyang","title":"OSG Technology Area Meeting, 30 August 2022"},{"location":"meetings/2022/TechArea20220830/#announcements","text":"Carl out Wednesdays Ziyang's last day is today","title":"Announcements"},{"location":"meetings/2022/TechArea20220830/#triage-duty","text":"This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220830/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220830/#osg-software-team","text":"AI (Mat): OSDF origin chart AI (Mat): Assist Fabio with setting up the University of Hawaii origin; we are currently waiting on them for Resource Group information, after which Mat will help with Data Federation information -- the format of that information is new AI (Carl): XRootD 5.5.0 release; contact Mat for assistance as needed AI (Carl): Review various PRs for the Tiger Kubernetes cluster AI (BrianL): Review and reprioritize Software Team JIRA tickets AI (BrianL): Review PATh metrics for the monthly report before the end of the month","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220830/#discussion","text":"Marco: GlideinWMS 3.9.6 expected by the end of the week; fixed setup issues noticed by Mat and others, and added a token generator","title":"Discussion"},{"location":"meetings/2022/TechArea20220830/#support-update","text":"USC (BrianL): helped solve issues with backfill containers; issues caused by tokens and using an outdated image. Admins were surprised that the pilots exited because they didn't get any jobs; this event should be communicated more clearly, perhaps in the container logs Virgo (BrianL): helped Jason resolve issues with Virgo proxy generation due to upstream VOMS server cert update LIGO (Carl): assisted Peter Couvares with getting the HTCondor version on a CE LIGO (Carl): received formal request from LIGO for first-class SIF file support on the OS Pool; redirected to Jason but Mats should also be added -- for now this is a question of OS Pool policy OS Pool (Derek): user wanted to have a very large file accessible on /cvmfs/stash.osgstorage.org . Derek increased the max file size from 26 GB to 500 GB. This change should not affect anything except large files, but staff should keep an eye out for issues MIT (Derek): Credential for lightweight issuer, hopefully can be resolved with a few more back and forths. WTAMU (Derek): observed a difference between pilot and payload hours -- looks to be due to the site having huge slots (64 cores) with Glideins pilots retiring (finishing old jobs but no longer accepting new jobs) but with a handful of long, small jobs keeping the pilot alive. Mats suggested increasing the pilot lifetime OS Pool (Derek): cvmfs-singularity-sync started deleting containers on CVMFS yesterday (8/29). The problem was fixed and the containers restored; the issue was due to code changes in order to support tag wildcards on hub.opensciencegrid.org. Derek is writing a full incident report.","title":"Support Update"},{"location":"meetings/2022/TechArea20220830/#osg-release-team","text":"TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220830/#discussion_1","text":"TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220906/","text":"OSG Technology Area Meeting, 6 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT Announcements \u00b6 Carl out Wednesdays Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon AI (BrianL): Debug Dex authentication system for the Tiger cluster AI (Mat): Assist IceCube with Kubernetes networking AI (Mat): Continue development of OSDF origin chart New CHTC Infrastructure Services student starting (Aiden) AI (Carl): hosted-ce-tools Python 3 compatibility Discussion \u00b6 None this week Support Update \u00b6 Mat (LIGO): James Clark is interested in what OSG does for job monitoring; this is something that both OSG and HTCSS devs are interested in, so suggest that they discuss this at their regular LIGO-HTCSS meeting OSG Release Team \u00b6 TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp Discussion \u00b6 TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"September 6, 2022"},{"location":"meetings/2022/TechArea20220906/#osg-technology-area-meeting-6-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT","title":"OSG Technology Area Meeting, 6 September 2022"},{"location":"meetings/2022/TechArea20220906/#announcements","text":"Carl out Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20220906/#triage-duty","text":"This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220906/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220906/#osg-software-team","text":"Kubernetes Hackathon this afternoon AI (BrianL): Debug Dex authentication system for the Tiger cluster AI (Mat): Assist IceCube with Kubernetes networking AI (Mat): Continue development of OSDF origin chart New CHTC Infrastructure Services student starting (Aiden) AI (Carl): hosted-ce-tools Python 3 compatibility","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220906/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220906/#support-update","text":"Mat (LIGO): James Clark is interested in what OSG does for job monitoring; this is something that both OSG and HTCSS devs are interested in, so suggest that they discuss this at their regular LIGO-HTCSS meeting","title":"Support Update"},{"location":"meetings/2022/TechArea20220906/#osg-release-team","text":"TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220906/#discussion_1","text":"TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220913/","text":"OSG Technology Area Meeting, 13 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT Announcements \u00b6 Carl out Wednesdays Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 206 -1 Open 36 +5 Selected for Dev 22 +2 In Progress 9 +0 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Next doc focus Oct 7 AI (Mat): OSDF origin Helm chart AI (Mat): fix rsyslog in glideins AI (Mat): add changes for XCache: review Carl's PR for authfile generator add extra issuer for PRP caches for Fabio AI (Carl): auto-generate OASIS StashCache configs AI (Carl): improve hosted-ce-tools Python 3 support AI (BrianL): cut new topology client AI (BrianL): meet with Igor et al. to discuss handoff of supporting Lancium provisioner from GIL to Operations or Software AI (Mat/Carl): discuss interface for supporting complex disk setups in OSDF Helm charts AI (TimT): fix regexps in condor-mapfile in HTCondor-CE 5 to be compatible with HTCondor 9.11+ Discussion \u00b6 LIGO has tested XRootD 5.5.0, which fixed scitokens issues they were having. LIGO uses CILogon and Vault for managing token auth. Support Update \u00b6 COManage (BrianL): manually fix a user's access, notes in FD#70228 LIGO (Derek): Debug HTTP(s) transfers with tokens. Failed with 5.4.3, works with 5.5.0 (osg-testing). So calling it a success. FNAL (Derek): Low cpu utilization at FNAL a few months back. Not sure there is much to debug as source of truth. LIGO (Derek): New CVMFS repo for igwn.osgstorage.org, copy of ligo.osgstorage.org (will be a symlink) LIGO (Carl): assisted CalTech in registering their Squid proxy in Topology OSG Release Team \u00b6 Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3 Discussion \u00b6 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"September 13, 2022"},{"location":"meetings/2022/TechArea20220913/#osg-technology-area-meeting-13-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 13 September 2022"},{"location":"meetings/2022/TechArea20220913/#announcements","text":"Carl out Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20220913/#triage-duty","text":"This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220913/#jira-as-of-monday","text":"# of tickets \u0394 State 206 -1 Open 36 +5 Selected for Dev 22 +2 In Progress 9 +0 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220913/#osg-software-team","text":"Next doc focus Oct 7 AI (Mat): OSDF origin Helm chart AI (Mat): fix rsyslog in glideins AI (Mat): add changes for XCache: review Carl's PR for authfile generator add extra issuer for PRP caches for Fabio AI (Carl): auto-generate OASIS StashCache configs AI (Carl): improve hosted-ce-tools Python 3 support AI (BrianL): cut new topology client AI (BrianL): meet with Igor et al. to discuss handoff of supporting Lancium provisioner from GIL to Operations or Software AI (Mat/Carl): discuss interface for supporting complex disk setups in OSDF Helm charts AI (TimT): fix regexps in condor-mapfile in HTCondor-CE 5 to be compatible with HTCondor 9.11+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220913/#discussion","text":"LIGO has tested XRootD 5.5.0, which fixed scitokens issues they were having. LIGO uses CILogon and Vault for managing token auth.","title":"Discussion"},{"location":"meetings/2022/TechArea20220913/#support-update","text":"COManage (BrianL): manually fix a user's access, notes in FD#70228 LIGO (Derek): Debug HTTP(s) transfers with tokens. Failed with 5.4.3, works with 5.5.0 (osg-testing). So calling it a success. FNAL (Derek): Low cpu utilization at FNAL a few months back. Not sure there is much to debug as source of truth. LIGO (Derek): New CVMFS repo for igwn.osgstorage.org, copy of ligo.osgstorage.org (will be a symlink) LIGO (Carl): assisted CalTech in registering their Squid proxy in Topology","title":"Support Update"},{"location":"meetings/2022/TechArea20220913/#osg-release-team","text":"Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220913/#discussion_1","text":"AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220920/","text":"OSG Technology Area Meeting, 20 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT Announcements \u00b6 None this week Triage Duty \u00b6 This week: Carl Next week: Mat 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 209 +3 Open 33 -3 Selected for Dev 18 -4 In Progress 14 +5 Dev Complete 0 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today: AI (Carl): deploy SLATE stashcache chart in Tiger AI (Mat): OSDF origin Helm chart Next doc focus Oct 7 AI (Mat): fix rsyslog in glideins AI (Mat): rebuild XCache to fix extra issuer bug AI (Carl): build XRootD 5.5.1 release candidate AI (Carl): auto-generate OASIS StashCache configs: There is a PR for scripts to compare the various configs against each other; request input from Dave Dykstra and Derek about what to do with the comparison results. AI (TimT): Release HTCondor-CE 5.1.6 for various bugfixes Discussion \u00b6 HTCondor-CE 5.1.6 scheduled for this week. Marco: GlideinWMS 3.9.6rc3 released last week; this is expected to be the last release candidate before the final release. LIGO is interested in Decision Engine; Marco is updating documentation and will send overview material. Support Update \u00b6 None this week OSG Release Team \u00b6 Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3 Discussion \u00b6 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"September 20, 2022"},{"location":"meetings/2022/TechArea20220920/#osg-technology-area-meeting-20-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 20 September 2022"},{"location":"meetings/2022/TechArea20220920/#announcements","text":"None this week","title":"Announcements"},{"location":"meetings/2022/TechArea20220920/#triage-duty","text":"This week: Carl Next week: Mat 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220920/#jira-as-of-monday","text":"# of tickets \u0394 State 209 +3 Open 33 -3 Selected for Dev 18 -4 In Progress 14 +5 Dev Complete 0 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220920/#osg-software-team","text":"Kubernetes Hackathon today: AI (Carl): deploy SLATE stashcache chart in Tiger AI (Mat): OSDF origin Helm chart Next doc focus Oct 7 AI (Mat): fix rsyslog in glideins AI (Mat): rebuild XCache to fix extra issuer bug AI (Carl): build XRootD 5.5.1 release candidate AI (Carl): auto-generate OASIS StashCache configs: There is a PR for scripts to compare the various configs against each other; request input from Dave Dykstra and Derek about what to do with the comparison results. AI (TimT): Release HTCondor-CE 5.1.6 for various bugfixes","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220920/#discussion","text":"HTCondor-CE 5.1.6 scheduled for this week. Marco: GlideinWMS 3.9.6rc3 released last week; this is expected to be the last release candidate before the final release. LIGO is interested in Decision Engine; Marco is updating documentation and will send overview material.","title":"Discussion"},{"location":"meetings/2022/TechArea20220920/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20220920/#osg-release-team","text":"Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220920/#discussion_1","text":"AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220927/","text":"OSG Technology Area Meeting, 27 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, Marco Mambelli, TimT Announcements \u00b6 BrianL OOO Friday Triage Duty \u00b6 This week: Mat Next week: TimT 9 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 212 +3 Open 32 -1 Selected for Dev 17 -1 In Progress 13 -1 Dev Complete 5 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 BrianL: Assisting Antonios with logging in -- his ACCESS CILogon credentials might be conflicting with his OSG CILogon credentials Talk to Aiden about tasks for the next two weeks. Carl: Have PR for validating stash/osdf cache data between OASIS and Topology. Mat: Test auth origin support in stash-origin containers. TimT: Putting 9.12.0 into OSPool. Thin pool improvements are being tested on CHTC. Planning on releasing 9.0.17 this week. Putting finishing touches on 10.0.0; mostly bringing UW spec file in sync with OSG. AIs (Carl): Putting Git identifiers into COManage. Upload missing hosted CE records to GRACC. AIs (Mat): Check if CHTC-canary2 has been sending rsyslog logs to central syslog server. Continue work on OSDF-Origin Helm chart. Fix rsyslog in pilots; assist Jason with setting up rsyslog for LIGO if needed. AIs (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. AI (TimT): Update HTCondor-CE in OSG repos to the latest release. AI (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. GlideinWMS: Two PRs remaining for GlideinWMS 3.9.6; release targeted for later this week. Investigating general credential support improvements. The factory would like to supply a list of credentials for a CE with fallback from one to the other (instead of using only one credential that has to be listed per-entry). Discussion \u00b6 Kernel issues in CHTC being investigated; most likely a kernel bug being triggered by having many condor_procds (one for each Glidein). Not worth holding up the release for. EL9 coming - transition tasks likely to be assigned to Carl. Support Update \u00b6 BrianL (PATh Facility): Helping users that have previously had XSEDE credentials log in to the Facility. Carl (unregistered Gratia probes): There are questions about how to match probe names with Topology identifiers. OSG Release Team \u00b6 Decision Engine: Versions 2.0.2 and 1.7.4 have been released. (1.7.4 is for internal use; 2.0.2 is the recommended version for external users.) Discussion \u00b6","title":"September 27, 2022"},{"location":"meetings/2022/TechArea20220927/#osg-technology-area-meeting-27-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 27 September 2022"},{"location":"meetings/2022/TechArea20220927/#announcements","text":"BrianL OOO Friday","title":"Announcements"},{"location":"meetings/2022/TechArea20220927/#triage-duty","text":"This week: Mat Next week: TimT 9 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220927/#jira-as-of-monday","text":"# of tickets \u0394 State 212 +3 Open 32 -1 Selected for Dev 17 -1 In Progress 13 -1 Dev Complete 5 +5 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220927/#osg-software-team","text":"BrianL: Assisting Antonios with logging in -- his ACCESS CILogon credentials might be conflicting with his OSG CILogon credentials Talk to Aiden about tasks for the next two weeks. Carl: Have PR for validating stash/osdf cache data between OASIS and Topology. Mat: Test auth origin support in stash-origin containers. TimT: Putting 9.12.0 into OSPool. Thin pool improvements are being tested on CHTC. Planning on releasing 9.0.17 this week. Putting finishing touches on 10.0.0; mostly bringing UW spec file in sync with OSG. AIs (Carl): Putting Git identifiers into COManage. Upload missing hosted CE records to GRACC. AIs (Mat): Check if CHTC-canary2 has been sending rsyslog logs to central syslog server. Continue work on OSDF-Origin Helm chart. Fix rsyslog in pilots; assist Jason with setting up rsyslog for LIGO if needed. AIs (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. AI (TimT): Update HTCondor-CE in OSG repos to the latest release. AI (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. GlideinWMS: Two PRs remaining for GlideinWMS 3.9.6; release targeted for later this week. Investigating general credential support improvements. The factory would like to supply a list of credentials for a CE with fallback from one to the other (instead of using only one credential that has to be listed per-entry).","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220927/#discussion","text":"Kernel issues in CHTC being investigated; most likely a kernel bug being triggered by having many condor_procds (one for each Glidein). Not worth holding up the release for. EL9 coming - transition tasks likely to be assigned to Carl.","title":"Discussion"},{"location":"meetings/2022/TechArea20220927/#support-update","text":"BrianL (PATh Facility): Helping users that have previously had XSEDE credentials log in to the Facility. Carl (unregistered Gratia probes): There are questions about how to match probe names with Topology identifiers.","title":"Support Update"},{"location":"meetings/2022/TechArea20220927/#osg-release-team","text":"Decision Engine: Versions 2.0.2 and 1.7.4 have been released. (1.7.4 is for internal use; 2.0.2 is the recommended version for external users.)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220927/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2022/TechArea20221004/","text":"OSG Technology Area Meeting, 4 October 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT Announcements \u00b6 BrianL OOO (travel + vacation) the next two weeks Mat gone next Tue-Fri + following Monday morning for travel Triage Duty \u00b6 This week: TimT Next week: ? 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 214 +2 Open 32 +0 Selected for Dev 20 +3 In Progress 13 +0 Dev Complete 1 -4 Ready for Testing 4 +4 Ready for Release OSG Software Team \u00b6 TimT on triage duty next week; will do double duty Next Doc Focus this week Fri, Oct 7 Starting EL 9 work this month; including items for Carl after GitHub comanage identifier work; TimT may rope in help for EL9 prep work AI (Mat): OSDF helm chart for Fabio targeted for this week AI (Mat): fix rsyslog in glideins AI (Carl): Update Topology to pull GitHub identifier from COManage Discussion \u00b6 rsyslog not working at a lot of sites, see if canary sites are reporting properly with rsyslog; Lincoln is interested as well (in rsyslog), and in first-class rook PVC. Support Update \u00b6 BrianL: user issue, ssh key with comanage account; or 2fa like with duo; issue with XSEDE and ACCESS; submit6 never logged them in. Mat: stash issue; everything transferred to stderr; empty files cause transfers to fail; jobs w/ no stdout cause transfer failures; ospool ticket. Upgrades for stashcp. New upstream location for source tarballs. Carl: made PRs for retiring TIGER-OSG-BACKFILL; can review together at hackathon; Mat suggests doing things differently. OSG Release Team \u00b6 Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing Discussion \u00b6 None last week","title":"October 4, 2022"},{"location":"meetings/2022/TechArea20221004/#osg-technology-area-meeting-4-october-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT","title":"OSG Technology Area Meeting, 4 October 2022"},{"location":"meetings/2022/TechArea20221004/#announcements","text":"BrianL OOO (travel + vacation) the next two weeks Mat gone next Tue-Fri + following Monday morning for travel","title":"Announcements"},{"location":"meetings/2022/TechArea20221004/#triage-duty","text":"This week: TimT Next week: ? 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221004/#jira-as-of-monday","text":"# of tickets \u0394 State 214 +2 Open 32 +0 Selected for Dev 20 +3 In Progress 13 +0 Dev Complete 1 -4 Ready for Testing 4 +4 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221004/#osg-software-team","text":"TimT on triage duty next week; will do double duty Next Doc Focus this week Fri, Oct 7 Starting EL 9 work this month; including items for Carl after GitHub comanage identifier work; TimT may rope in help for EL9 prep work AI (Mat): OSDF helm chart for Fabio targeted for this week AI (Mat): fix rsyslog in glideins AI (Carl): Update Topology to pull GitHub identifier from COManage","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221004/#discussion","text":"rsyslog not working at a lot of sites, see if canary sites are reporting properly with rsyslog; Lincoln is interested as well (in rsyslog), and in first-class rook PVC.","title":"Discussion"},{"location":"meetings/2022/TechArea20221004/#support-update","text":"BrianL: user issue, ssh key with comanage account; or 2fa like with duo; issue with XSEDE and ACCESS; submit6 never logged them in. Mat: stash issue; everything transferred to stderr; empty files cause transfers to fail; jobs w/ no stdout cause transfer failures; ospool ticket. Upgrades for stashcp. New upstream location for source tarballs. Carl: made PRs for retiring TIGER-OSG-BACKFILL; can review together at hackathon; Mat suggests doing things differently.","title":"Support Update"},{"location":"meetings/2022/TechArea20221004/#osg-release-team","text":"Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221004/#discussion_1","text":"None last week","title":"Discussion"},{"location":"meetings/2022/TechArea20221018/","text":"OSG Technology Area Meeting, 18 October 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, Tim Announcements \u00b6 BrianL OOO (travel + vacation) this week Kubernetes Hackathon today - Researchers from a local lab will be joining for the tutorial Triage Duty \u00b6 This week: Carl Next week: Mat 10 (+3 from 2 weeks ago) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday 10/17) \u00b6 # of tickets \u0394 State 214 +2 Open 25 -7 Selected for Dev 22 +2 In Progress 16 +3 Dev Complete 4 +3 Ready for Testing 1 -3 Ready for Release OSG Software Team \u00b6 Starting EL 9 work this month AI (Mat): OSDF Origin Helm chart; use it to serve files from the UW-Madison ResearchDrive service Discussion \u00b6 None this week Support Update \u00b6 None last week OSG Release Team \u00b6 Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing Discussion \u00b6 None last week","title":"OSG Technology Area Meeting, 18 October 2022"},{"location":"meetings/2022/TechArea20221018/#osg-technology-area-meeting-18-october-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, Tim","title":"OSG Technology Area Meeting, 18 October 2022"},{"location":"meetings/2022/TechArea20221018/#announcements","text":"BrianL OOO (travel + vacation) this week Kubernetes Hackathon today - Researchers from a local lab will be joining for the tutorial","title":"Announcements"},{"location":"meetings/2022/TechArea20221018/#triage-duty","text":"This week: Carl Next week: Mat 10 (+3 from 2 weeks ago) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221018/#jira-as-of-monday-1017","text":"# of tickets \u0394 State 214 +2 Open 25 -7 Selected for Dev 22 +2 In Progress 16 +3 Dev Complete 4 +3 Ready for Testing 1 -3 Ready for Release","title":"Jira (as of Monday 10/17)"},{"location":"meetings/2022/TechArea20221018/#osg-software-team","text":"Starting EL 9 work this month AI (Mat): OSDF Origin Helm chart; use it to serve files from the UW-Madison ResearchDrive service","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221018/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221018/#support-update","text":"None last week","title":"Support Update"},{"location":"meetings/2022/TechArea20221018/#osg-release-team","text":"Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221018/#discussion_1","text":"None last week","title":"Discussion"},{"location":"meetings/2022/TechArea20221101/","text":"OSG Technology Area Meeting, 1 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT Announcements \u00b6 BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays Triage Duty \u00b6 This week: BrianL Next week: ? 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 217 +2 Open 25 +0 Selected for Dev 22 +0 In Progress 14 -1 Dev Complete 6 +2 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records EL 9 work starts this this month Discussion \u00b6 None this week Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0 Discussion \u00b6 None this week","title":"November 1, 2022"},{"location":"meetings/2022/TechArea20221101/#osg-technology-area-meeting-1-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT","title":"OSG Technology Area Meeting, 1 November 2022"},{"location":"meetings/2022/TechArea20221101/#announcements","text":"BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221101/#triage-duty","text":"This week: BrianL Next week: ? 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221101/#jira-as-of-monday","text":"# of tickets \u0394 State 217 +2 Open 25 +0 Selected for Dev 22 +0 In Progress 14 -1 Dev Complete 6 +2 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221101/#osg-software-team","text":"AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records EL 9 work starts this this month","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221101/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221101/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20221101/#osg-release-team","text":"Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221101/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221108/","text":"OSG Technology Area Meeting, 8 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays Triage Duty \u00b6 This week: Mat Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) (TODO) \u00b6 # of tickets \u0394 State 217 +0 Open 27 +2 Selected for Dev 22 +0 In Progress 15 +1 Dev Complete 2 -4 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OS Pool AI (Mat): Update EL8 containers to Alma EL 9 work starts this this month Discussion \u00b6 GlideinWMS: Marco investigating what's causing Frontend to report 0 to factory monitoring in GlideinWMS 3.9.6. Support Update \u00b6 Carl (SIUE): Site is experiencing disk issues in their scratch space; Carl to follow up Mat (NERSC): Difficulty getting voms-mapfile to work for xrootd-standalone; will request assistance from XRootD developers OSG Release Team \u00b6 Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0 Discussion \u00b6 None this week","title":"November 8, 2022"},{"location":"meetings/2022/TechArea20221108/#osg-technology-area-meeting-8-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 8 November 2022"},{"location":"meetings/2022/TechArea20221108/#announcements","text":"BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221108/#triage-duty","text":"This week: Mat Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221108/#jira-as-of-monday-todo","text":"# of tickets \u0394 State 217 +0 Open 27 +2 Selected for Dev 22 +0 In Progress 15 +1 Dev Complete 2 -4 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday) (TODO)"},{"location":"meetings/2022/TechArea20221108/#osg-software-team","text":"AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OS Pool AI (Mat): Update EL8 containers to Alma EL 9 work starts this this month","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221108/#discussion","text":"GlideinWMS: Marco investigating what's causing Frontend to report 0 to factory monitoring in GlideinWMS 3.9.6.","title":"Discussion"},{"location":"meetings/2022/TechArea20221108/#support-update","text":"Carl (SIUE): Site is experiencing disk issues in their scratch space; Carl to follow up Mat (NERSC): Difficulty getting voms-mapfile to work for xrootd-standalone; will request assistance from XRootD developers","title":"Support Update"},{"location":"meetings/2022/TechArea20221108/#osg-release-team","text":"Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221108/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221115/","text":"OSG Technology Area Meeting, 15 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays Triage Duty \u00b6 This week: BrianL Next week: TimT 10 (+2) open FreshDesk tickets ? (+?) open GGUS ticket Jira (as of Monday) (TODO) \u00b6 # of tickets \u0394 State 229 +12 Open 23 -4 Selected for Dev 16 -6 In Progress 17 +2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat, Carl) EL 9 groundwork AI (Carl): Update valut to 1.12.1+ Discussion \u00b6 None this week Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 vault 1.12.1 Ready for Release Nothing Yet Discussion \u00b6 None this week","title":"November 15, 2022"},{"location":"meetings/2022/TechArea20221115/#osg-technology-area-meeting-15-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 15 November 2022"},{"location":"meetings/2022/TechArea20221115/#announcements","text":"BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221115/#triage-duty","text":"This week: BrianL Next week: TimT 10 (+2) open FreshDesk tickets ? (+?) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221115/#jira-as-of-monday-todo","text":"# of tickets \u0394 State 229 +12 Open 23 -4 Selected for Dev 16 -6 In Progress 17 +2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday) (TODO)"},{"location":"meetings/2022/TechArea20221115/#osg-software-team","text":"AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat, Carl) EL 9 groundwork AI (Carl): Update valut to 1.12.1+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221115/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221115/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20221115/#osg-release-team","text":"Ready for Testing CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 vault 1.12.1 Ready for Release Nothing Yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221115/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221122/","text":"OSG Technology Area Meeting, 22 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays Triage Duty \u00b6 This week: TimT Next week: Carl 10 (+0) open FreshDesk tickets ? (+?) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 233 -6 Open 23 +0 Selected for Dev 15 -1 In Progress 16 -1 Dev Complete 6 +3 Ready for Testing 0 +0 Ready for Release Brian will be tossing more things into backlog to make sense of prios; in need of cleaning OSG Software Team \u00b6 AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat): scitokens ticket for Steve Timm AI (Mat, Carl) EL 9 groundwork: Carl: for next week, add VMU images for EL9 (SOFTWARE-5337) After that: OSDF tickets selected for development: SOFTWARE-5296, SOFTWARE-5295 Discussion \u00b6 Marco: glideinwms: frontend is not reporting properly to monitoring Support Update \u00b6 BrianL: discusses Open Science Pool token registry; will manually create a token for comanage after discussion with Brians B,A University of Arkansas Little Rock (BrianL): working around an issue with ORCID and the self-service OS Registry NERSC (Mat, BrianB, BrianL): got a patched XRootD into testing for Lisa to install to test issues with missing Role/Capability in her VOMS certificate. That seems to be fixed but there are still ongoing issues. Mat: not getting logging we are supposed to for XRootD server at NERSC. CalTech startd cron not getting parsed correctly; BrianL will talk to Todd about it Carl: DESY: don't want other VOs they host Carl: unregistered gratia probes: we want to close for moral victory, might wanna check for more unreg probes at some point Derek: supporting TimC in osg-connect-ops Derek: Einstein telescope wants to use OSDF Derek: gratia probe payloads, identifying the pool? Next week, not this week. OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) One more xrootd patch for Mat to get in; Mat says go with 1.4, unresolved bug in 1.5 Vault 1.12.1 Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 22, 2022"},{"location":"meetings/2022/TechArea20221122/#osg-technology-area-meeting-22-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 22 November 2022"},{"location":"meetings/2022/TechArea20221122/#announcements","text":"BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221122/#triage-duty","text":"This week: TimT Next week: Carl 10 (+0) open FreshDesk tickets ? (+?) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221122/#jira-as-of-monday","text":"# of tickets \u0394 State 233 -6 Open 23 +0 Selected for Dev 15 -1 In Progress 16 -1 Dev Complete 6 +3 Ready for Testing 0 +0 Ready for Release Brian will be tossing more things into backlog to make sense of prios; in need of cleaning","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221122/#osg-software-team","text":"AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat): scitokens ticket for Steve Timm AI (Mat, Carl) EL 9 groundwork: Carl: for next week, add VMU images for EL9 (SOFTWARE-5337) After that: OSDF tickets selected for development: SOFTWARE-5296, SOFTWARE-5295","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221122/#discussion","text":"Marco: glideinwms: frontend is not reporting properly to monitoring","title":"Discussion"},{"location":"meetings/2022/TechArea20221122/#support-update","text":"BrianL: discusses Open Science Pool token registry; will manually create a token for comanage after discussion with Brians B,A University of Arkansas Little Rock (BrianL): working around an issue with ORCID and the self-service OS Registry NERSC (Mat, BrianB, BrianL): got a patched XRootD into testing for Lisa to install to test issues with missing Role/Capability in her VOMS certificate. That seems to be fixed but there are still ongoing issues. Mat: not getting logging we are supposed to for XRootD server at NERSC. CalTech startd cron not getting parsed correctly; BrianL will talk to Todd about it Carl: DESY: don't want other VOs they host Carl: unregistered gratia probes: we want to close for moral victory, might wanna check for more unreg probes at some point Derek: supporting TimC in osg-connect-ops Derek: Einstein telescope wants to use OSDF Derek: gratia probe payloads, identifying the pool? Next week, not this week.","title":"Support Update"},{"location":"meetings/2022/TechArea20221122/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) One more xrootd patch for Mat to get in; Mat says go with 1.4, unresolved bug in 1.5 Vault 1.12.1 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221122/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221129/","text":"OSG Technology Area Meeting, 29 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, TimT Announcements \u00b6 BrianL traveling Nov 28 - Dec 2 Triage Duty \u00b6 This week: Carl Next week: ? 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 240 +7 Open 22 -1 Selected for Dev 15 +0 In Progress 16 +0 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon: On Thursday, the default network for the Tiger Kubernetes cluster will change; people should review the services they are responsible for to make sure they will continue to function after the network change. AI (Mat): Create a variant of the pilot container that unpacks SIF files if they cannot be used directly. AI (Carl): Continue debugging COManage authentication failures on the Topology ITB instance. AI (Mat): Continue to assist Mats and HTCondor devs in getting container universe working on the OSPool, along with other pilot fixes. AI (Mat, Carl) Continue EL 9 groundwork. Discussion \u00b6 GlideinWMS: Fix available for factory monitoring issue. The ITB frontends and factory have been updated; waiting for green light from Mats and Marco Mascheroni before making a release. Support Update \u00b6 Mat (FNAL/CMS): Come up with a fix or workaround for gfal2 authentication failures when using the tarball client on EL8. Mat (CalTech): Discuss errors with parsing output of CalTech's periodic scripts with HTCondor dev team. OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) Vault 1.12.1 Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 29, 2022"},{"location":"meetings/2022/TechArea20221129/#osg-technology-area-meeting-29-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 29 November 2022"},{"location":"meetings/2022/TechArea20221129/#announcements","text":"BrianL traveling Nov 28 - Dec 2","title":"Announcements"},{"location":"meetings/2022/TechArea20221129/#triage-duty","text":"This week: Carl Next week: ? 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221129/#jira-as-of-monday","text":"# of tickets \u0394 State 240 +7 Open 22 -1 Selected for Dev 15 +0 In Progress 16 +0 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221129/#osg-software-team","text":"Kubernetes Hackathon: On Thursday, the default network for the Tiger Kubernetes cluster will change; people should review the services they are responsible for to make sure they will continue to function after the network change. AI (Mat): Create a variant of the pilot container that unpacks SIF files if they cannot be used directly. AI (Carl): Continue debugging COManage authentication failures on the Topology ITB instance. AI (Mat): Continue to assist Mats and HTCondor devs in getting container universe working on the OSPool, along with other pilot fixes. AI (Mat, Carl) Continue EL 9 groundwork.","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221129/#discussion","text":"GlideinWMS: Fix available for factory monitoring issue. The ITB frontends and factory have been updated; waiting for green light from Mats and Marco Mascheroni before making a release.","title":"Discussion"},{"location":"meetings/2022/TechArea20221129/#support-update","text":"Mat (FNAL/CMS): Come up with a fix or workaround for gfal2 authentication failures when using the tarball client on EL8. Mat (CalTech): Discuss errors with parsing output of CalTech's periodic scripts with HTCondor dev team.","title":"Support Update"},{"location":"meetings/2022/TechArea20221129/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) Vault 1.12.1 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221129/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221206/","text":"OSG Technology Area Meeting, 6 December 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 244 +4 Open 19 -3 Selected for Dev 17 +2 In Progress 18 +2 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): EL9 support next items Create 'buildsys-*' packages (SOFTWARE-5391, SOFTWARE-5392) Build 'fetch-sources' (SOFTWARE-5393) AI (BrianL): NVidia GPU software-base image (SOFTWARE-5368) Discussion \u00b6 Time limit on GHA jobs; may want to consider paid tier for github; cross that bridge when we get there. Marco: what's the story with condor el9 support? 10.2.0 will have el9 support 10.0 LTS will not get el9 support (for reasons relating to cgroups support) el7 EOL in May 2024 will trigger updates Support Update \u00b6 NERSC (Mat, BrianL, BrianB): spoke with XRootD devs about the missing VOMS thread and he suggested compiling with print statements. Atlas is very interested. Carl: new issues: fd-71210: OSG 3.6 and OSG connection to Wayne State compute resources fd-71208: HTCondor-CE Hold jobs randomly (1/day) - Spooling input data UConn (Derek, DaveD): Debug OSDF cache selection. Was always using KC cache rather than NYC. With Dave's help, debugged it to a bad entry in the geoip DB. Richard sent an update to the upstream DB, which was accepted. OSG Release Team \u00b6 Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"December 6, 2022"},{"location":"meetings/2022/TechArea20221206/#osg-technology-area-meeting-6-december-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 6 December 2022"},{"location":"meetings/2022/TechArea20221206/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20221206/#triage-duty","text":"This week: Brian Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221206/#jira-as-of-monday","text":"JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 244 +4 Open 19 -3 Selected for Dev 17 +2 In Progress 18 +2 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221206/#osg-software-team","text":"AI (Carl): EL9 support next items Create 'buildsys-*' packages (SOFTWARE-5391, SOFTWARE-5392) Build 'fetch-sources' (SOFTWARE-5393) AI (BrianL): NVidia GPU software-base image (SOFTWARE-5368)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221206/#discussion","text":"Time limit on GHA jobs; may want to consider paid tier for github; cross that bridge when we get there. Marco: what's the story with condor el9 support? 10.2.0 will have el9 support 10.0 LTS will not get el9 support (for reasons relating to cgroups support) el7 EOL in May 2024 will trigger updates","title":"Discussion"},{"location":"meetings/2022/TechArea20221206/#support-update","text":"NERSC (Mat, BrianL, BrianB): spoke with XRootD devs about the missing VOMS thread and he suggested compiling with print statements. Atlas is very interested. Carl: new issues: fd-71210: OSG 3.6 and OSG connection to Wayne State compute resources fd-71208: HTCondor-CE Hold jobs randomly (1/day) - Spooling input data UConn (Derek, DaveD): Debug OSDF cache selection. Was always using KC cache rather than NYC. With Dave's help, debugged it to a bad entry in the geoip DB. Richard sent an update to the upstream DB, which was accepted.","title":"Support Update"},{"location":"meetings/2022/TechArea20221206/#osg-release-team","text":"Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221206/#discussion_1","text":"condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"Discussion"},{"location":"meetings/2022/TechArea20221213/","text":"OSG Technology Area Meeting, 13 December 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 10 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 246 +2 Open 20 +1 Selected for Dev 20 +3 In Progress 18 +0 Dev Complete 2 -2 Ready for Testing 6 +6 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today AI (Carl): sort out COManage issues with Topology ITB; if they cannot be solved this afternoon, add a config knob to disable the feature so it does not block testing of other Topology changes AI (BrianL, Mat): investigate issues with Flux on osgdev AI (BrianL, Mat): deploy us-west-1 OSDF origin based on the Helm chart AI (Mat): Fix the OSG (not CMS) Frontera Hosted CE Doc focus Friday AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): Continue package rebuilds of OSG 3.6 packages signed with the pre-3.6 key EL9 support next items: Test yum installing software from our EL9 repos to verify that the new GPG key works Build a table of RPMs that need to be built for EL9 AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot Discussion \u00b6 Building NVidia GPU-based pilot images exposed some architectural issues with the way we use GitHub Actions for image building. Some redesign will be needed. Resource-based OSDF lookups for Topology may not be urgent since UC-Leuvain can have multiple services in a single resource. There is a problem with how duplicate \"issuer\" sections in xrootd-scitokens config are combined; Topology will need to be modified to not create issuer sections with the same name and instead combine namespaces using the same issuer in a sensible manner. Note that \"base path\" in the xrootd-scitokens config can be a comma-separated list. Code freeze for HTCondor 10.0.1 and 10.2.0 is today; this will include thinpool provisioning and the OSDF client. Partial EL9 builds (i.e. without cgroups) succeed but the UW EL9 repositories will need to be configured to not use SHA1 checksums because they are forbidden by EL9. Support Update \u00b6 Generally, Snowmass tickets should be assigned to Collaboration Support OSG Release Team \u00b6 Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"December 13, 2022"},{"location":"meetings/2022/TechArea20221213/#osg-technology-area-meeting-13-december-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 13 December 2022"},{"location":"meetings/2022/TechArea20221213/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20221213/#triage-duty","text":"This week: Carl Next week: Mat 10 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221213/#jira-as-of-monday","text":"JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 246 +2 Open 20 +1 Selected for Dev 20 +3 In Progress 18 +0 Dev Complete 2 -2 Ready for Testing 6 +6 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221213/#osg-software-team","text":"Kubernetes Hackathon today AI (Carl): sort out COManage issues with Topology ITB; if they cannot be solved this afternoon, add a config knob to disable the feature so it does not block testing of other Topology changes AI (BrianL, Mat): investigate issues with Flux on osgdev AI (BrianL, Mat): deploy us-west-1 OSDF origin based on the Helm chart AI (Mat): Fix the OSG (not CMS) Frontera Hosted CE Doc focus Friday AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): Continue package rebuilds of OSG 3.6 packages signed with the pre-3.6 key EL9 support next items: Test yum installing software from our EL9 repos to verify that the new GPG key works Build a table of RPMs that need to be built for EL9 AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221213/#discussion","text":"Building NVidia GPU-based pilot images exposed some architectural issues with the way we use GitHub Actions for image building. Some redesign will be needed. Resource-based OSDF lookups for Topology may not be urgent since UC-Leuvain can have multiple services in a single resource. There is a problem with how duplicate \"issuer\" sections in xrootd-scitokens config are combined; Topology will need to be modified to not create issuer sections with the same name and instead combine namespaces using the same issuer in a sensible manner. Note that \"base path\" in the xrootd-scitokens config can be a comma-separated list. Code freeze for HTCondor 10.0.1 and 10.2.0 is today; this will include thinpool provisioning and the OSDF client. Partial EL9 builds (i.e. without cgroups) succeed but the UW EL9 repositories will need to be configured to not use SHA1 checksums because they are forbidden by EL9.","title":"Discussion"},{"location":"meetings/2022/TechArea20221213/#support-update","text":"Generally, Snowmass tickets should be assigned to Collaboration Support","title":"Support Update"},{"location":"meetings/2022/TechArea20221213/#osg-release-team","text":"Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221213/#discussion_1","text":"condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"Discussion"},{"location":"meetings/2022/TechArea20221220/","text":"OSG Technology Area Meeting, 20 December 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL out Dec 22 - Jan 2 Mat out Dec 23 - Dec 27 Carl out Dec 29 Triage Duty \u00b6 This week: Mat Next week: TimT 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 242 -4 Open 20 +0 Selected for Dev 21 +1 In Progress 18 +0 Dev Complete 4 +2 Ready for Testing 0 -6 Ready for Release OSG Software Team \u00b6 AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): EL9 support next items: EL9 VMU images (debug VMs with vnc). EL9 spreadsheet link is in SOFTWARE-5416; divide and conquer with Mat over the next few weeks. Note no HTCondor 10.0 or dependent pkgs for el9 release; need to wait for 10.2.0 in upcoming. A few pkgs will have version differences. AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot Discussion \u00b6 Topology contact registrations are now self-service in comanage. Mat/Carl: next couple weeks: Take a look at plates; backlog of tasks that you'd like to do but haven't had time to do. Fine as long as we're making progress on el9 and ospool. If there's no ticket make one. BrianL may add some wishlist items. Support Update \u00b6 University of Arkansas Little Rock (BrianL): help them register an ORCID account for use with the OS Registry CMS SW (BrianB, BrianL, Mat, TimT): assist them with OSG 3.5 software dependency issue Carl UConn CC* gratia issue Richard T. Jones; resolved There's an XRootD 5.5 issue; see https://osg-htc.org/docs/release/osg-36/#xrootd (will put in known issues for OSG release notes) OSG Release Team \u00b6 6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 BrianL recommends WFH if blizzard WILL NOT MEET NEXT WEEK - SEE YOU NEXT YEAR","title":"December 20, 2022"},{"location":"meetings/2022/TechArea20221220/#osg-technology-area-meeting-20-december-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 20 December 2022"},{"location":"meetings/2022/TechArea20221220/#announcements","text":"BrianL out Dec 22 - Jan 2 Mat out Dec 23 - Dec 27 Carl out Dec 29","title":"Announcements"},{"location":"meetings/2022/TechArea20221220/#triage-duty","text":"This week: Mat Next week: TimT 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221220/#jira-as-of-monday","text":"# of tickets \u0394 State 242 -4 Open 20 +0 Selected for Dev 21 +1 In Progress 18 +0 Dev Complete 4 +2 Ready for Testing 0 -6 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221220/#osg-software-team","text":"AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): EL9 support next items: EL9 VMU images (debug VMs with vnc). EL9 spreadsheet link is in SOFTWARE-5416; divide and conquer with Mat over the next few weeks. Note no HTCondor 10.0 or dependent pkgs for el9 release; need to wait for 10.2.0 in upcoming. A few pkgs will have version differences. AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221220/#discussion","text":"Topology contact registrations are now self-service in comanage. Mat/Carl: next couple weeks: Take a look at plates; backlog of tasks that you'd like to do but haven't had time to do. Fine as long as we're making progress on el9 and ospool. If there's no ticket make one. BrianL may add some wishlist items.","title":"Discussion"},{"location":"meetings/2022/TechArea20221220/#support-update","text":"University of Arkansas Little Rock (BrianL): help them register an ORCID account for use with the OS Registry CMS SW (BrianB, BrianL, Mat, TimT): assist them with OSG 3.5 software dependency issue Carl UConn CC* gratia issue Richard T. Jones; resolved There's an XRootD 5.5 issue; see https://osg-htc.org/docs/release/osg-36/#xrootd (will put in known issues for OSG release notes)","title":"Support Update"},{"location":"meetings/2022/TechArea20221220/#osg-release-team","text":"6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221220/#discussion_1","text":"BrianL recommends WFH if blizzard WILL NOT MEET NEXT WEEK - SEE YOU NEXT YEAR","title":"Discussion"},{"location":"meetings/2023/TechArea20230103/","text":"OSG Technology Area Meeting, 3 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: BrianL (?) Next week: Carl (?) 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 208 -3 Open 33 +0 Selected for Dev 27 +2 In Progress 17 +1 Dev Complete 2 -2 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 EL9 GPG key had to be recreated again so packages have to be rebuilt. AI (Carl): Debug VMU image generation for EL9; CHTC infrastructure staff can answer questions about Kickstart AI (Carl): Rebuild EL9 packages to get signed with the new GPG key AI (Mat): Clean-up work on OSPool Container Universe project AI (TimT): Test HTCondor 10.x on EL9; this requires an EL9 VM or host in order to test cgroupv2 support, since that is based on the kernel version Discussion \u00b6 None this week Support Update \u00b6 NERSC (Mat): Provided XRootD builds with extra debug logging OSG Release Team \u00b6 6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 3, 2023"},{"location":"meetings/2023/TechArea20230103/#osg-technology-area-meeting-3-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 3 January 2023"},{"location":"meetings/2023/TechArea20230103/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230103/#triage-duty","text":"This week: BrianL (?) Next week: Carl (?) 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230103/#jira-as-of-monday","text":"# of tickets \u0394 State 208 -3 Open 33 +0 Selected for Dev 27 +2 In Progress 17 +1 Dev Complete 2 -2 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230103/#osg-software-team","text":"EL9 GPG key had to be recreated again so packages have to be rebuilt. AI (Carl): Debug VMU image generation for EL9; CHTC infrastructure staff can answer questions about Kickstart AI (Carl): Rebuild EL9 packages to get signed with the new GPG key AI (Mat): Clean-up work on OSPool Container Universe project AI (TimT): Test HTCondor 10.x on EL9; this requires an EL9 VM or host in order to test cgroupv2 support, since that is based on the kernel version","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230103/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230103/#support-update","text":"NERSC (Mat): Provided XRootD builds with extra debug logging","title":"Support Update"},{"location":"meetings/2023/TechArea20230103/#osg-release-team","text":"6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230103/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230117/","text":"OSG Technology Area Meeting, 17 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 215 +1 Open 38 +5 Selected for Dev 28 -1 In Progress 17 +0 Dev Complete 4 +2 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 AI (Carl): Release python-scitokens for IGWN AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes Discussion \u00b6 EL9 VMU images are available Rocky 8 image generation failed because the upstream ISO is gone Marco: GlideinWMS 3.10.1 is available; waiting for OSG Software Team to release it into their repos Support Update \u00b6 BNL (Brian): Provided XRootD builds with extra debug logging MWT2 (Brian): CE was backed up with high RecentDaemonCoreDutyCycle and was backed up handling reads. Forks were taking 0.1s so we turned down SCHEDD_QUERY_WORKERS down to 2 and it eventually caught back up. Purdue (Brian): helped Colby troubleshoot issues with cred transfer to the EP OSG Release Team \u00b6 Ready for Testing vo-client 128 Update HCC, GLOW, and OSG VOMS certificates Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 17, 2023"},{"location":"meetings/2023/TechArea20230117/#osg-technology-area-meeting-17-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Tim","title":"OSG Technology Area Meeting, 17 January 2023"},{"location":"meetings/2023/TechArea20230117/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230117/#triage-duty","text":"This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230117/#jira-as-of-monday","text":"# of tickets \u0394 State 215 +1 Open 38 +5 Selected for Dev 28 -1 In Progress 17 +0 Dev Complete 4 +2 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230117/#osg-software-team","text":"AI (Carl): Release python-scitokens for IGWN AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230117/#discussion","text":"EL9 VMU images are available Rocky 8 image generation failed because the upstream ISO is gone Marco: GlideinWMS 3.10.1 is available; waiting for OSG Software Team to release it into their repos","title":"Discussion"},{"location":"meetings/2023/TechArea20230117/#support-update","text":"BNL (Brian): Provided XRootD builds with extra debug logging MWT2 (Brian): CE was backed up with high RecentDaemonCoreDutyCycle and was backed up handling reads. Forks were taking 0.1s so we turned down SCHEDD_QUERY_WORKERS down to 2 and it eventually caught back up. Purdue (Brian): helped Colby troubleshoot issues with cred transfer to the EP","title":"Support Update"},{"location":"meetings/2023/TechArea20230117/#osg-release-team","text":"Ready for Testing vo-client 128 Update HCC, GLOW, and OSG VOMS certificates Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230117/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230124/","text":"OSG Technology Area Meeting, 24 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: Tim 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 217 +2 Open 42 +4 Selected for Dev 29 +1 In Progress 17 +0 Dev Complete 5 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): Release python-scitokens for IGWN AI (Carl): Work with dev team (?) to figure out EL9 VM kernel panics AI (Mat): Release glideinwms AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes Discussion \u00b6 None this week Support Update \u00b6 BNL (Brian): discussed weighted slots and GRACC/WLCG accounting OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 24, 2023"},{"location":"meetings/2023/TechArea20230124/#osg-technology-area-meeting-24-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 24 January 2023"},{"location":"meetings/2023/TechArea20230124/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230124/#triage-duty","text":"This week: Mat Next week: Tim 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230124/#jira-as-of-monday","text":"# of tickets \u0394 State 217 +2 Open 42 +4 Selected for Dev 29 +1 In Progress 17 +0 Dev Complete 5 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230124/#osg-software-team","text":"AI (Carl): Release python-scitokens for IGWN AI (Carl): Work with dev team (?) to figure out EL9 VM kernel panics AI (Mat): Release glideinwms AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230124/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230124/#support-update","text":"BNL (Brian): discussed weighted slots and GRACC/WLCG accounting","title":"Support Update"},{"location":"meetings/2023/TechArea20230124/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230124/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230131/","text":"OSG Technology Area Meeting, 31 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: Tim Next week: BrianL (?) 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 209 -8 Open 42 +0 Selected for Dev 33 +4 In Progress 18 +1 Dev Complete 7 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): add option to filter OSPool project user map by login group AI (Carl): Kick off appropriate package set tests for EL9 AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile work AI (Mat): Lancium provisioner backfill container changes Discussion \u00b6 GlideinWMS 3.10.1 is in use in the ITB at CERN; this should be sufficient testing to add it to the OSG release. Question about how an HTCondor client validates the server when using IDTOKENS; Mat says the client doesn't have a copy of the IDTOKEN signing key so it can't use that method and it must use something else like FS or SSL. Reminder: HTCondor will be built for EL9 only in 3.6-upcoming because the LTS series 10.0 does not support EL9. Support Update \u00b6 BNL (Brian): further discussion of weighted slots and GRACC/WLCG accounting OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 31, 2023"},{"location":"meetings/2023/TechArea20230131/#osg-technology-area-meeting-31-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Mat, Tim","title":"OSG Technology Area Meeting, 31 January 2023"},{"location":"meetings/2023/TechArea20230131/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230131/#triage-duty","text":"This week: Tim Next week: BrianL (?) 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230131/#jira-as-of-monday","text":"# of tickets \u0394 State 209 -8 Open 42 +0 Selected for Dev 33 +4 In Progress 18 +1 Dev Complete 7 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230131/#osg-software-team","text":"Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): add option to filter OSPool project user map by login group AI (Carl): Kick off appropriate package set tests for EL9 AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile work AI (Mat): Lancium provisioner backfill container changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230131/#discussion","text":"GlideinWMS 3.10.1 is in use in the ITB at CERN; this should be sufficient testing to add it to the OSG release. Question about how an HTCondor client validates the server when using IDTOKENS; Mat says the client doesn't have a copy of the IDTOKEN signing key so it can't use that method and it must use something else like FS or SSL. Reminder: HTCondor will be built for EL9 only in 3.6-upcoming because the LTS series 10.0 does not support EL9.","title":"Discussion"},{"location":"meetings/2023/TechArea20230131/#support-update","text":"BNL (Brian): further discussion of weighted slots and GRACC/WLCG accounting","title":"Support Update"},{"location":"meetings/2023/TechArea20230131/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230131/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230207/","text":"OSG Technology Area Meeting, 7 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Marco, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 210 +1 Open 38 -4 Selected for Dev 32 -1 In Progress 18 +0 Dev Complete 4 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): Kick off appropriate package set tests for EL9 AI (Carl): osg-build branch protection AI (Carl): document more Git opinions AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile + Topology work Florida requests a backported fix for https://github.com/xrootd/xrootd/issues/1874 . We've got a lot of patches, should we cut a new build with reduced patches? Relatedly, XRootD 5.5.2 has been released; the software team should patch that version instead of 5.5.1. - x509-scitokens-issuer, which is in osg-contrib, needs to be rebuilt to sign it with the current OSG 3.6 GPG key. Kubernetes Hackathon: - BrianL: PATh Facility Origin - Mat: ITB EP with a GPU for testing container universe changes Discussion \u00b6 XRootD developers have requested that the OSG SW team clearly indicate in XRootD packages that they are the OSG versions and not upstream; there is a text file in the XRootD packages that can be used for that purpose. Support Update \u00b6 BNL (Brian): will hold off on weighted slots work until this sorted out at the WLCG level OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"February 7, 2023"},{"location":"meetings/2023/TechArea20230207/#osg-technology-area-meeting-7-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Marco, Mat, Tim","title":"OSG Technology Area Meeting, 7 February 2023"},{"location":"meetings/2023/TechArea20230207/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230207/#triage-duty","text":"This week: BrianL Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230207/#jira-as-of-monday","text":"# of tickets \u0394 State 210 +1 Open 38 -4 Selected for Dev 32 -1 In Progress 18 +0 Dev Complete 4 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230207/#osg-software-team","text":"Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): Kick off appropriate package set tests for EL9 AI (Carl): osg-build branch protection AI (Carl): document more Git opinions AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile + Topology work Florida requests a backported fix for https://github.com/xrootd/xrootd/issues/1874 . We've got a lot of patches, should we cut a new build with reduced patches? Relatedly, XRootD 5.5.2 has been released; the software team should patch that version instead of 5.5.1. - x509-scitokens-issuer, which is in osg-contrib, needs to be rebuilt to sign it with the current OSG 3.6 GPG key. Kubernetes Hackathon: - BrianL: PATh Facility Origin - Mat: ITB EP with a GPU for testing container universe changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230207/#discussion","text":"XRootD developers have requested that the OSG SW team clearly indicate in XRootD packages that they are the OSG versions and not upstream; there is a text file in the XRootD packages that can be used for that purpose.","title":"Discussion"},{"location":"meetings/2023/TechArea20230207/#support-update","text":"BNL (Brian): will hold off on weighted slots work until this sorted out at the WLCG level","title":"Support Update"},{"location":"meetings/2023/TechArea20230207/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230207/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230214/","text":"OSG Technology Area Meeting, 14 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Derek, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 218 +8 Open 40 +2 Selected for Dev 26 -6 In Progress 17 -1 Dev Complete 8 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): Write tests for OSG-Build branch safety. AI (Carl): Continue work on EL9 builds AI (Mat): Build new VO-Client for second Fermilab cert change. AI (Brian): Investigate rrdtool for EL9. AI (Mat): Continue work on Topology endpoints for grid-mapfiles. Discussion \u00b6 Tim will release HTCondor-CE 6 which works with HTCondor 10 this week; HTCondor 10.3.0 expected next week Group write permissions for the PATh origin are broken due to xrootd-multiuser not having the right group permission to traverse the directory tree to enter into private directories. A potential workaround is to make the parent directories world-traverseable but not world-readable. We would have to remind users that they need to make their files not world-readable and also investigate what permissions xrootd gives newly written files. A long term solution is to modify xrootd-multiuser to set the process's supplementary groups before accessing files in group directories. Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"February 14, 2023"},{"location":"meetings/2023/TechArea20230214/#osg-technology-area-meeting-14-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Derek, Mat, Tim","title":"OSG Technology Area Meeting, 14 February 2023"},{"location":"meetings/2023/TechArea20230214/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230214/#triage-duty","text":"This week: Carl Next week: Mat 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230214/#jira-as-of-monday","text":"# of tickets \u0394 State 218 +8 Open 40 +2 Selected for Dev 26 -6 In Progress 17 -1 Dev Complete 8 +4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230214/#osg-software-team","text":"AI (Carl): Write tests for OSG-Build branch safety. AI (Carl): Continue work on EL9 builds AI (Mat): Build new VO-Client for second Fermilab cert change. AI (Brian): Investigate rrdtool for EL9. AI (Mat): Continue work on Topology endpoints for grid-mapfiles.","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230214/#discussion","text":"Tim will release HTCondor-CE 6 which works with HTCondor 10 this week; HTCondor 10.3.0 expected next week Group write permissions for the PATh origin are broken due to xrootd-multiuser not having the right group permission to traverse the directory tree to enter into private directories. A potential workaround is to make the parent directories world-traverseable but not world-readable. We would have to remind users that they need to make their files not world-readable and also investigate what permissions xrootd gives newly written files. A long term solution is to modify xrootd-multiuser to set the process's supplementary groups before accessing files in group directories.","title":"Discussion"},{"location":"meetings/2023/TechArea20230214/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230214/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230214/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230221/","text":"OSG Technology Area Meeting, 21 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon Plan osdf-origin chart pipeline Implement automatic deployment re-roll in the origin chart (https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments) Pick CHTC LDAP replica static IP EL 9 AI (BrianL): rebuild osg-ce without Squid dependency AI (BrianL): build voms for EL9 AI (Mat): XRootD mapfile + Topology status? AI (Mat): Upgrade Topology Webapp to EL8 and Python 3.9 Discussion \u00b6 Mat and BrianL will discuss cleaning up old OSG images on Harbor Harbor upgrade planned for the next few weeks OSG Build Tools do not work on Fedora 37; there is a Docker image available as an alternative to running the software natively GlideinWMS release candidate planned for next week Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN) Discussion \u00b6 None this week","title":"February 21, 2023"},{"location":"meetings/2023/TechArea20230221/#osg-technology-area-meeting-21-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 21 February 2023"},{"location":"meetings/2023/TechArea20230221/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230221/#triage-duty","text":"This week: Mat Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230221/#jira-as-of-monday","text":"# of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230221/#osg-software-team","text":"Kubernetes Hackathon Plan osdf-origin chart pipeline Implement automatic deployment re-roll in the origin chart (https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments) Pick CHTC LDAP replica static IP EL 9 AI (BrianL): rebuild osg-ce without Squid dependency AI (BrianL): build voms for EL9 AI (Mat): XRootD mapfile + Topology status? AI (Mat): Upgrade Topology Webapp to EL8 and Python 3.9","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230221/#discussion","text":"Mat and BrianL will discuss cleaning up old OSG images on Harbor Harbor upgrade planned for the next few weeks OSG Build Tools do not work on Fedora 37; there is a Docker image available as an alternative to running the software natively GlideinWMS release candidate planned for next week","title":"Discussion"},{"location":"meetings/2023/TechArea20230221/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230221/#osg-release-team","text":"Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN)","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230221/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230228/","text":"OSG Technology Area Meeting, 28 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: TimT Next week: BrianL 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Software team members should pull in others to help out as soon as possible. Jira (as of Monday) \u00b6 # of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Critical bug in gratia-probe-htcondor-ce-2.8.1 requires an expedited release (SOFTWARE-5504) EL 9 AI (BrianL): investigate Slurm failures AI (Mat): Verify EL9 tests for XRootD-related package sets Give up on voms-proxy-direct ? This will allow OSG to drop packaging voms-clients; users will still be able to take voms clients from EPEL Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) AI (BrianL, Mat, TimT): Meet to plan OSG 3.7 repository structure Discussion \u00b6 GlideinWMS 3.10.2 release candidate planned for next week Support Update \u00b6 IGWN interested in setting up their own central-syslog service; BrianL has pointed them at the OSPool instance OSG Release Team \u00b6 Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN) Discussion \u00b6 None this week","title":"OSG Technology Area Meeting, 28 February 2023"},{"location":"meetings/2023/TechArea20230228/#osg-technology-area-meeting-28-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 28 February 2023"},{"location":"meetings/2023/TechArea20230228/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230228/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: TimT Next week: BrianL 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Software team members should pull in others to help out as soon as possible.","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230228/#jira-as-of-monday","text":"# of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230228/#osg-software-team","text":"Critical bug in gratia-probe-htcondor-ce-2.8.1 requires an expedited release (SOFTWARE-5504) EL 9 AI (BrianL): investigate Slurm failures AI (Mat): Verify EL9 tests for XRootD-related package sets Give up on voms-proxy-direct ? This will allow OSG to drop packaging voms-clients; users will still be able to take voms clients from EPEL Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) AI (BrianL, Mat, TimT): Meet to plan OSG 3.7 repository structure","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230228/#discussion","text":"GlideinWMS 3.10.2 release candidate planned for next week","title":"Discussion"},{"location":"meetings/2023/TechArea20230228/#support-update","text":"IGWN interested in setting up their own central-syslog service; BrianL has pointed them at the OSPool instance","title":"Support Update"},{"location":"meetings/2023/TechArea20230228/#osg-release-team","text":"Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN)","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230228/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230314/","text":"OSG Technology Area Meeting, 14 March 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 BrianL out Thursday March 16 and Friday March 17 TimT out Monday, March 20 through Friday, March 31. (May work remotely on March 20 and 21.) Mat out Thursday, March 30 through Monday, April 17. Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: Mat Next week: BrianL 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 223 +3 Open 38 -1 Selected for Dev 27 +0 In Progress 19 +0 Dev Complete 9 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 EL 9 AI (BrianL): investigate Slurm failures AI (BrianL): rebuild upcoming packages into main AI (BrianL): build osg-ca-certs-experimental AI (Mat): build XRootD + kick off EL9 VMU tests Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) Other AI (Mat): Use the OSDF Client shipped with HTCondor in OSPool pilots Discussion \u00b6 Marco: Final GlideinWMS release candidate is expected this week. Notable changes: Fixes for OSG autoconf script The tarball to use for CVMFSEXEC will be configurable Fixes error in configuring token lifetime Horst at OU has successfully installed an EL9 CE; he has reported some documentation issues, which BrianL will review Support Update \u00b6 BrianL (Caltech): Gratia probe failures were due to incorrect directory permissions at the site. This is not the first time such an error has occurred; the Gratia probe should detect this issue and log and/or refuse to start (instead of just discarding records). BrianL will discuss it with Derek. BrianL: A site in India stopped receiving pilots from Fermilab; they reinstalled their CE and need assistance with registration and using token-based pilots OSG Release Team \u00b6 Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN) Discussion \u00b6 None this week","title":"March 14, 2023"},{"location":"meetings/2023/TechArea20230314/#osg-technology-area-meeting-14-march-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 14 March 2023"},{"location":"meetings/2023/TechArea20230314/#announcements","text":"BrianL out Thursday March 16 and Friday March 17 TimT out Monday, March 20 through Friday, March 31. (May work remotely on March 20 and 21.) Mat out Thursday, March 30 through Monday, April 17.","title":"Announcements"},{"location":"meetings/2023/TechArea20230314/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: Mat Next week: BrianL 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230314/#jira-as-of-monday","text":"# of tickets \u0394 State 223 +3 Open 38 -1 Selected for Dev 27 +0 In Progress 19 +0 Dev Complete 9 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230314/#osg-software-team","text":"EL 9 AI (BrianL): investigate Slurm failures AI (BrianL): rebuild upcoming packages into main AI (BrianL): build osg-ca-certs-experimental AI (Mat): build XRootD + kick off EL9 VMU tests Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) Other AI (Mat): Use the OSDF Client shipped with HTCondor in OSPool pilots","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230314/#discussion","text":"Marco: Final GlideinWMS release candidate is expected this week. Notable changes: Fixes for OSG autoconf script The tarball to use for CVMFSEXEC will be configurable Fixes error in configuring token lifetime Horst at OU has successfully installed an EL9 CE; he has reported some documentation issues, which BrianL will review","title":"Discussion"},{"location":"meetings/2023/TechArea20230314/#support-update","text":"BrianL (Caltech): Gratia probe failures were due to incorrect directory permissions at the site. This is not the first time such an error has occurred; the Gratia probe should detect this issue and log and/or refuse to start (instead of just discarding records). BrianL will discuss it with Derek. BrianL: A site in India stopped receiving pilots from Fermilab; they reinstalled their CE and need assistance with registration and using token-based pilots","title":"Support Update"},{"location":"meetings/2023/TechArea20230314/#osg-release-team","text":"Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN)","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230314/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230328/","text":"OSG Technology Area Meeting, 28 March 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Marco Announcements \u00b6 TimT out Monday, March 20 through Friday, March 31. Mat out Thursday, March 30 through Monday, April 17. Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: Mat and BrianL Next week: BrianL 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 225 +1 Open 39 -1 Selected for Dev 28 -2 In Progress 22 -1 Dev Complete 11 +2 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Marco: Testing release candidate; The last remaining PR before a release is to allow configuring location of CVMFSEXEC tarball It is no longer possible to use an EL 7 machine for development because because the git pre-commit hooks do not work on Python 3.6; however, GlideinWMS will continue to run on EL 7. EL 9 AI (BrianL): investigate Slurm failures The Slurm service may be failing to start but the tests are not catching it soon enough. AI (Mat): build osg-ca-certs-experimental AI (BrianL): enable EL9 tests in VMU Gratia probe release for AP bugs: docs should be fixed to indicate that all history files should be moved from quarantine Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (JeffT?): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) Discussion \u00b6 None this week Support Update \u00b6 Oklahoma (BrianL): got their CE up and running! MWT2 (BrianL): helped troubleshoot HTCondor-CE -> HTCondor submission issues. Their JOB_ROUTER_SCHEDD2_SPOOL CE config didn't match their custom local HTCondor SPOOL config UCLouvain (Mat): Virgo pilots failing to read protected LIGO data; need assistance from a pilot expert OSG Release Team \u00b6 Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0 Discussion \u00b6 None this week","title":"March 28, 2023"},{"location":"meetings/2023/TechArea20230328/#osg-technology-area-meeting-28-march-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Marco","title":"OSG Technology Area Meeting, 28 March 2023"},{"location":"meetings/2023/TechArea20230328/#announcements","text":"TimT out Monday, March 20 through Friday, March 31. Mat out Thursday, March 30 through Monday, April 17.","title":"Announcements"},{"location":"meetings/2023/TechArea20230328/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: Mat and BrianL Next week: BrianL 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230328/#jira-as-of-monday","text":"# of tickets \u0394 State 225 +1 Open 39 -1 Selected for Dev 28 -2 In Progress 22 -1 Dev Complete 11 +2 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230328/#osg-software-team","text":"Marco: Testing release candidate; The last remaining PR before a release is to allow configuring location of CVMFSEXEC tarball It is no longer possible to use an EL 7 machine for development because because the git pre-commit hooks do not work on Python 3.6; however, GlideinWMS will continue to run on EL 7. EL 9 AI (BrianL): investigate Slurm failures The Slurm service may be failing to start but the tests are not catching it soon enough. AI (Mat): build osg-ca-certs-experimental AI (BrianL): enable EL9 tests in VMU Gratia probe release for AP bugs: docs should be fixed to indicate that all history files should be moved from quarantine Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (JeffT?): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325)","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230328/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230328/#support-update","text":"Oklahoma (BrianL): got their CE up and running! MWT2 (BrianL): helped troubleshoot HTCondor-CE -> HTCondor submission issues. Their JOB_ROUTER_SCHEDD2_SPOOL CE config didn't match their custom local HTCondor SPOOL config UCLouvain (Mat): Virgo pilots failing to read protected LIGO data; need assistance from a pilot expert","title":"Support Update"},{"location":"meetings/2023/TechArea20230328/#osg-release-team","text":"Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230328/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230404/","text":"OSG Technology Area Meeting, 28 March 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, TimT Announcements \u00b6 Mat out Thursday, March 30 through Monday, April 17. Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: BrianL Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 224 -1 Open 41 +2 Selected for Dev 26 -2 In Progress 19 -3 Dev Complete 9 -2 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 AI (BrianL): build new XCache AI (BrianL): build patched XRootD AI (BrianL): investigate WN client tarball failures; eliminate remaining Python 2 dependencies Discussion \u00b6 None this week DevOps \u00b6 Moving python-scitokens to EPEL: https://bugzilla.redhat.com/show_bug.cgi?id=2181686 Support Update \u00b6 (Derek) OSG pilots checking for retired CVMFS repo, desdm.osgstorage.org, causing errors in site logs. Fixed the check. (Derek) CVMFS Singularity Sync patch to fix new OCI type being used by ubuntu and other newer images. (Derek) CVMFS indexing is failing for FNAL's nova, some issue with offsite access to data there. OSG Release Team \u00b6 Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0 Discussion \u00b6 None this week","title":"April 4, 2023"},{"location":"meetings/2023/TechArea20230404/#osg-technology-area-meeting-28-march-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, TimT","title":"OSG Technology Area Meeting, 28 March 2023"},{"location":"meetings/2023/TechArea20230404/#announcements","text":"Mat out Thursday, March 30 through Monday, April 17.","title":"Announcements"},{"location":"meetings/2023/TechArea20230404/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: BrianL Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230404/#jira-as-of-monday","text":"# of tickets \u0394 State 224 -1 Open 41 +2 Selected for Dev 26 -2 In Progress 19 -3 Dev Complete 9 -2 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230404/#osg-software-team","text":"AI (BrianL): build new XCache AI (BrianL): build patched XRootD AI (BrianL): investigate WN client tarball failures; eliminate remaining Python 2 dependencies","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230404/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230404/#devops","text":"Moving python-scitokens to EPEL: https://bugzilla.redhat.com/show_bug.cgi?id=2181686","title":"DevOps"},{"location":"meetings/2023/TechArea20230404/#support-update","text":"(Derek) OSG pilots checking for retired CVMFS repo, desdm.osgstorage.org, causing errors in site logs. Fixed the check. (Derek) CVMFS Singularity Sync patch to fix new OCI type being used by ubuntu and other newer images. (Derek) CVMFS indexing is failing for FNAL's nova, some issue with offsite access to data there.","title":"Support Update"},{"location":"meetings/2023/TechArea20230404/#osg-release-team","text":"Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230404/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230418/","text":"OSG Technology Area Meeting, 18 April 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 228 -1 Open 42 +0 Selected for Dev 29 +2 In Progress 19 +0 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Request new gfactory-2 IGTF certificate AI (Mat): investigate OSDF plugin failures (INF-913) AI (BrianL): add glidein IDTOKEN support to Hosted CE AI (Mat): request new IGTF gfactory-2 cert Kubernetes Hackathon today AI (Mat): Expanse upgrade, locking down firewalls AI (BrianL): make progress on TACC remote flux AI (Mat): Assist Fabio in debugging Helm / Flux v2 on Nautilus Discussion \u00b6 None this week Support Update \u00b6 AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"April 18, 2023"},{"location":"meetings/2023/TechArea20230418/#osg-technology-area-meeting-18-april-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 18 April 2023"},{"location":"meetings/2023/TechArea20230418/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230418/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230418/#jira-as-of-monday","text":"# of tickets \u0394 State 228 -1 Open 42 +0 Selected for Dev 29 +2 In Progress 19 +0 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230418/#osg-software-team","text":"AI (Mat): Request new gfactory-2 IGTF certificate AI (Mat): investigate OSDF plugin failures (INF-913) AI (BrianL): add glidein IDTOKEN support to Hosted CE AI (Mat): request new IGTF gfactory-2 cert Kubernetes Hackathon today AI (Mat): Expanse upgrade, locking down firewalls AI (BrianL): make progress on TACC remote flux AI (Mat): Assist Fabio in debugging Helm / Flux v2 on Nautilus","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230418/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230418/#support-update","text":"AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs","title":"Support Update"},{"location":"meetings/2023/TechArea20230418/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230418/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230418/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230509/","text":"OSG Technology Area Meeting, 9 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat (?) Next week: TimT (?) 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 228 +2 Open 38 -1 Selected for Dev 30 +0 In Progress 23 +0 Dev Complete 7 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Flux v1 -> v2 transition AI (BrianL): ticket review and planning work for Matthew Discussion \u00b6 None this week Support Update \u00b6 AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 9, 2023"},{"location":"meetings/2023/TechArea20230509/#osg-technology-area-meeting-9-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 9 May 2023"},{"location":"meetings/2023/TechArea20230509/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230509/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat (?) Next week: TimT (?) 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230509/#jira-as-of-monday","text":"# of tickets \u0394 State 228 +2 Open 38 -1 Selected for Dev 30 +0 In Progress 23 +0 Dev Complete 7 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230509/#osg-software-team","text":"AI (Mat): Flux v1 -> v2 transition AI (BrianL): ticket review and planning work for Matthew","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230509/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230509/#support-update","text":"AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs","title":"Support Update"},{"location":"meetings/2023/TechArea20230509/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230509/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230509/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230516/","text":"OSG Technology Area Meeting, 16 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 +9 Open 40 +2 Selected for Dev 26 -4 In Progress 25 +2 Dev Complete 8 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): XCache and osg-xrootd mapfile-related releases Kubernetes Hackathon AI (Mat): Flux v1 -> v2 transition AI (BrianL): review Helm chart CI, investigate path-facility-admin RBAC issues and Expanse user namespace issues Discussion \u00b6 The script that tests upgrades from HTCondor 9 to 10 needs improvements; there will be an updated release soon. The release of HTCondor 10.0.4 is waiting for scitokens-cpp 1.0.2 to be released. Derek and Fabio are debugging why the open and close times for transfers are the same; this leads to reporting an infinite amount of bandwidth since the reported transfer time is zero Support Update \u00b6 AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs Fermilab (BrianL): WLCG folks are worried about accounting for VO information with tokens. (OSG SW and GRACC look at the SciToken issuer.) Steve Timm ran into a problem where multiple VOs were using a single AP where DAGMan-created jobs don't have any of the auth token attributes. There is a workaround since Steve's jobs still have VOMS attributes but passing the token attributes requires HTCondor changes. SDSC (Mat): The OSDF authfile generator service was renamed and the documentation wasn't updated with the new paths; Mat made a PR to fix the documentation. DevOps \u00b6 APEL accounting updates for new HEPScore benchmark. Derek will try to schedule meetings with USCMS and USATLAS groups to present the (minor) changes to topology. OSDF client director, Derek needs to review. OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 16, 2023"},{"location":"meetings/2023/TechArea20230516/#osg-technology-area-meeting-16-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Tim","title":"OSG Technology Area Meeting, 16 May 2023"},{"location":"meetings/2023/TechArea20230516/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230516/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230516/#jira-as-of-monday","text":"# of tickets \u0394 State 237 +9 Open 40 +2 Selected for Dev 26 -4 In Progress 25 +2 Dev Complete 8 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230516/#osg-software-team","text":"Release AI (Mat): XCache and osg-xrootd mapfile-related releases Kubernetes Hackathon AI (Mat): Flux v1 -> v2 transition AI (BrianL): review Helm chart CI, investigate path-facility-admin RBAC issues and Expanse user namespace issues","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230516/#discussion","text":"The script that tests upgrades from HTCondor 9 to 10 needs improvements; there will be an updated release soon. The release of HTCondor 10.0.4 is waiting for scitokens-cpp 1.0.2 to be released. Derek and Fabio are debugging why the open and close times for transfers are the same; this leads to reporting an infinite amount of bandwidth since the reported transfer time is zero","title":"Discussion"},{"location":"meetings/2023/TechArea20230516/#support-update","text":"AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs Fermilab (BrianL): WLCG folks are worried about accounting for VO information with tokens. (OSG SW and GRACC look at the SciToken issuer.) Steve Timm ran into a problem where multiple VOs were using a single AP where DAGMan-created jobs don't have any of the auth token attributes. There is a workaround since Steve's jobs still have VOMS attributes but passing the token attributes requires HTCondor changes. SDSC (Mat): The OSDF authfile generator service was renamed and the documentation wasn't updated with the new paths; Mat made a PR to fix the documentation.","title":"Support Update"},{"location":"meetings/2023/TechArea20230516/#devops","text":"APEL accounting updates for new HEPScore benchmark. Derek will try to schedule meetings with USCMS and USATLAS groups to present the (minor) changes to topology. OSDF client director, Derek needs to review.","title":"DevOps"},{"location":"meetings/2023/TechArea20230516/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230516/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230523/","text":"OSG Technology Area Meeting, 16 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 New OSG Software Team member, Matthew Westphall, started yesterday! Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: ??? 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 +0 Open 39 -1 Selected for Dev 27 +1 In Progress 25 +0 Dev Complete 7 -1 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 AI (BrianL): create a Kanban board for Matthew AI (Mat): help Matthew set up Subversion access AI (Mat): XRootD patch for token username claims (SOFTWARE-5541) AI (Matthew): Remove python2 packaging deps from osg-update-vos (SOFTWARE-5545) Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 23, 2023"},{"location":"meetings/2023/TechArea20230523/#osg-technology-area-meeting-16-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 16 May 2023"},{"location":"meetings/2023/TechArea20230523/#announcements","text":"New OSG Software Team member, Matthew Westphall, started yesterday!","title":"Announcements"},{"location":"meetings/2023/TechArea20230523/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: ??? 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230523/#jira-as-of-monday","text":"# of tickets \u0394 State 237 +0 Open 39 -1 Selected for Dev 27 +1 In Progress 25 +0 Dev Complete 7 -1 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230523/#osg-software-team","text":"AI (BrianL): create a Kanban board for Matthew AI (Mat): help Matthew set up Subversion access AI (Mat): XRootD patch for token username claims (SOFTWARE-5541) AI (Matthew): Remove python2 packaging deps from osg-update-vos (SOFTWARE-5545)","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230523/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230523/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230523/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230523/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230523/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230530/","text":"OSG Technology Area Meeting, 30 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT Announcements \u00b6 PATh mid-point NSF review this Thursday and Friday Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: BrianL 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 planning meeting this morning Kubernetes hackathon this afternoon! AI (MatS): Create OSDF origin for NIH public data AI (MatS): Migrate \"osg\" namespace to Flux V2 AI (MattW): Work with TimT to build RPMs for the new IGTF CA cert bundle Discussion \u00b6 UFlorida Research Computing policy no longer allows them to install software out of osg-testing, so they won't be able to provide community testing for XRootD for us anymore; BrianL will ask OU if they would be available for this in the future Support Update \u00b6 IGWN (TimT): IGWN is setting up an HTCondor AP; TimT will contact Stefano for a status update DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 30, 2023"},{"location":"meetings/2023/TechArea20230530/#osg-technology-area-meeting-30-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 30 May 2023"},{"location":"meetings/2023/TechArea20230530/#announcements","text":"PATh mid-point NSF review this Thursday and Friday","title":"Announcements"},{"location":"meetings/2023/TechArea20230530/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: BrianL 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230530/#jira-as-of-monday","text":"# of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230530/#osg-software-team","text":"OSG 3.7 planning meeting this morning Kubernetes hackathon this afternoon! AI (MatS): Create OSDF origin for NIH public data AI (MatS): Migrate \"osg\" namespace to Flux V2 AI (MattW): Work with TimT to build RPMs for the new IGTF CA cert bundle","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230530/#discussion","text":"UFlorida Research Computing policy no longer allows them to install software out of osg-testing, so they won't be able to provide community testing for XRootD for us anymore; BrianL will ask OU if they would be available for this in the future","title":"Discussion"},{"location":"meetings/2023/TechArea20230530/#support-update","text":"IGWN (TimT): IGWN is setting up an HTCondor AP; TimT will contact Stefano for a status update","title":"Support Update"},{"location":"meetings/2023/TechArea20230530/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230530/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230530/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230606/","text":"OSG Technology Area Meeting, 6 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks (targeting initial release for early/mid August) HTCondor repo planning meeting this Friday AI (Mat): Prep koji tags + targets AI (Matt, Mat): Koji package signing AI (Mat): Koji policy Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 6, 2023"},{"location":"meetings/2023/TechArea20230606/#osg-technology-area-meeting-6-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 6 June 2023"},{"location":"meetings/2023/TechArea20230606/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230606/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230606/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230606/#osg-software-team","text":"OSG 3.7 tasks (targeting initial release for early/mid August) HTCondor repo planning meeting this Friday AI (Mat): Prep koji tags + targets AI (Matt, Mat): Koji package signing AI (Mat): Koji policy","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230606/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230606/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230606/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230606/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230606/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230613/","text":"OSG Technology Area Meeting, 13 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT Announcements \u00b6 CHTC planning retreat June 21/22 Collaboration day tentatively June 20 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: Matt 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks (targeting initial release for August) AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy Kubernetes Hackathon today AI (BrianL): prepare PRs for updating Dex templates to generate proxy-url config AI (Mat): Copy Expanse remote Flux config for TACC AI (Matt): osg-repo technical debt Discussion \u00b6 None this week Support Update \u00b6 Louvain (BrianL): issues with EL8 WNs pulling from Virgo caches (using default security policy) DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 13, 2023"},{"location":"meetings/2023/TechArea20230613/#osg-technology-area-meeting-13-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 13 June 2023"},{"location":"meetings/2023/TechArea20230613/#announcements","text":"CHTC planning retreat June 21/22 Collaboration day tentatively June 20","title":"Announcements"},{"location":"meetings/2023/TechArea20230613/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: Matt 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230613/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230613/#osg-software-team","text":"OSG 3.7 tasks (targeting initial release for August) AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy Kubernetes Hackathon today AI (BrianL): prepare PRs for updating Dex templates to generate proxy-url config AI (Mat): Copy Expanse remote Flux config for TACC AI (Matt): osg-repo technical debt","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230613/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230613/#support-update","text":"Louvain (BrianL): issues with EL8 WNs pulling from Virgo caches (using default security policy)","title":"Support Update"},{"location":"meetings/2023/TechArea20230613/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230613/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230613/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230620/","text":"OSG Technology Area Meeting, 20 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW Announcements \u00b6 CHTC planning retreat June 21/22 Collaboration day moved to Thursday, July 6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy Discussion \u00b6 GlideinWMS: - 3.10.3 release candidate in progress - CMS ran into a bug with 3.9.6 where the factory wasn't updating the number of glideins and kept sending new glideins. This had been fixed in 3.10; if you are using tokens, be sure to use GlideinWMS 3.10 or newer. Brief overview of OSG 3.7 plans so far: - OSG 3.7 layout will not differ much from previous layouts (i.e. will have \"main\" and \"upcoming\") - OSG release schedules starting with 3.7 will be aligned with HTCondor release schedules (starting with 11): 3.7-main will have HTCondor 11.0, and 3.7-upcoming will have HTCondor 11.x - OSG team is experimenting with new signing procedures; this should not impact developers Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 20, 2023"},{"location":"meetings/2023/TechArea20230620/#osg-technology-area-meeting-20-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW","title":"OSG Technology Area Meeting, 20 June 2023"},{"location":"meetings/2023/TechArea20230620/#announcements","text":"CHTC planning retreat June 21/22 Collaboration day moved to Thursday, July 6","title":"Announcements"},{"location":"meetings/2023/TechArea20230620/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230620/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230620/#osg-software-team","text":"OSG 3.7 tasks AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230620/#discussion","text":"GlideinWMS: - 3.10.3 release candidate in progress - CMS ran into a bug with 3.9.6 where the factory wasn't updating the number of glideins and kept sending new glideins. This had been fixed in 3.10; if you are using tokens, be sure to use GlideinWMS 3.10 or newer. Brief overview of OSG 3.7 plans so far: - OSG 3.7 layout will not differ much from previous layouts (i.e. will have \"main\" and \"upcoming\") - OSG release schedules starting with 3.7 will be aligned with HTCondor release schedules (starting with 11): 3.7-main will have HTCondor 11.0, and 3.7-upcoming will have HTCondor 11.x - OSG team is experimenting with new signing procedures; this should not impact developers","title":"Discussion"},{"location":"meetings/2023/TechArea20230620/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230620/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230620/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230620/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230627/","text":"OSG Technology Area Meeting, 27 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: ??? Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 233 +1 Open 37 +1 Selected for Dev 33 -2 In Progress 18 -1 Dev Complete 4 +2 Ready for Testing 0 -0 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks AI (Mat): Finish design doc; send it out for re-review AI (Mat): Review Koji policy config AI (Matt): Yubikey process documented? Kubernetes Hackathon AI (BrianL/Mat/Matt): TACC PATh Facility AI (BrianL): testing Flux minor version upgrades AI (Matt): repo k8s health probe (OPS-332) Other AI (BrianL/Mat): Test xrootd-multiuser supplementary groups patch in the PATh Facility origin Discussion \u00b6 None this week Support Update \u00b6 (Derek) Working on GRACC corrections. DevOps \u00b6 Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up) OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 27, 2023"},{"location":"meetings/2023/TechArea20230627/#osg-technology-area-meeting-27-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt","title":"OSG Technology Area Meeting, 27 June 2023"},{"location":"meetings/2023/TechArea20230627/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230627/#triage-duty","text":"Triage duty shifts Tue-Mon This week: ??? Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230627/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 233 +1 Open 37 +1 Selected for Dev 33 -2 In Progress 18 -1 Dev Complete 4 +2 Ready for Testing 0 -0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230627/#osg-software-team","text":"OSG 3.7 tasks AI (Mat): Finish design doc; send it out for re-review AI (Mat): Review Koji policy config AI (Matt): Yubikey process documented? Kubernetes Hackathon AI (BrianL/Mat/Matt): TACC PATh Facility AI (BrianL): testing Flux minor version upgrades AI (Matt): repo k8s health probe (OPS-332) Other AI (BrianL/Mat): Test xrootd-multiuser supplementary groups patch in the PATh Facility origin","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230627/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230627/#support-update","text":"(Derek) Working on GRACC corrections.","title":"Support Update"},{"location":"meetings/2023/TechArea20230627/#devops","text":"Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up)","title":"DevOps"},{"location":"meetings/2023/TechArea20230627/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230627/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230718/","text":"OSG Technology Area Meeting, 18 July 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 TimT OOO Thursday MattW OOO Thursday + Friday BrianL OOO next week MatS OOO next Monday afternoon Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: Mat 8 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 243 +16 Open 24 -7 Selected for Dev 27 -5 In Progress 17 -1 Dev Complete 4 +0 Ready for Testing 0 -0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): Release XRootD 5.6+ AI (BrianL): Release xrootd-multiuser-2.1.3+ AI (Matt): osg-ca-scripts missing dependency on perl-filetest. We need this done before we can build EL9 tarballs - no longer included with base perl packages in EL9. MatS to provide special Perl packaging tips. AI (Matt): Release oidc-agent-4.4.2+. SRPMs no longer provided by upstream, github is not properly organized to use as source. Either a spec file in the github, or return to releasing the srpm OSG 23 tasks What's the next step in the Yubikey setup for promoting packages? Per-developer key, packages get re-signed when promoted from development to testing Need to: Update script OSG Promote Generate promotion key Create Yubikey for each developer (4 or 5) Workflow update: Will need to sign packages locally, since you can't use a Yubikey on Moria AI (Matt): Build buildsys-macro packages AI (BrianL): build package list AI (Matt): update release scripts to accommodate OSG 23 New args: ... (as long as it sorts) Kubernetes Hackathon (Next Week) TBD Discussion \u00b6 None this week Support Update \u00b6 Topology/GGUS (BrianL, Mat): Topology does not accept certs from SHA1-signed CAs. We need to petition G\u00fcnter to get the German CA to update their signing key. Mat: Reach out to Gunter to update CA, update Topology to temporarily accept SHA1 Louvain (Mat): OSG-based CVMFS installation hitting Syracuse cache from Europe. We should probably just suggest that he install the EGI config while we sort out policy. Renewing Colorado host certificates (Matt): Awaiting approval by Douglas DevOps \u00b6 Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up) OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"July 18, 2023"},{"location":"meetings/2023/TechArea20230718/#osg-technology-area-meeting-18-july-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 18 July 2023"},{"location":"meetings/2023/TechArea20230718/#announcements","text":"TimT OOO Thursday MattW OOO Thursday + Friday BrianL OOO next week MatS OOO next Monday afternoon","title":"Announcements"},{"location":"meetings/2023/TechArea20230718/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: Mat 8 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230718/#jira-as-of-monday","text":"# of tickets \u0394 State 243 +16 Open 24 -7 Selected for Dev 27 -5 In Progress 17 -1 Dev Complete 4 +0 Ready for Testing 0 -0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230718/#osg-software-team","text":"Release AI (Mat): Release XRootD 5.6+ AI (BrianL): Release xrootd-multiuser-2.1.3+ AI (Matt): osg-ca-scripts missing dependency on perl-filetest. We need this done before we can build EL9 tarballs - no longer included with base perl packages in EL9. MatS to provide special Perl packaging tips. AI (Matt): Release oidc-agent-4.4.2+. SRPMs no longer provided by upstream, github is not properly organized to use as source. Either a spec file in the github, or return to releasing the srpm OSG 23 tasks What's the next step in the Yubikey setup for promoting packages? Per-developer key, packages get re-signed when promoted from development to testing Need to: Update script OSG Promote Generate promotion key Create Yubikey for each developer (4 or 5) Workflow update: Will need to sign packages locally, since you can't use a Yubikey on Moria AI (Matt): Build buildsys-macro packages AI (BrianL): build package list AI (Matt): update release scripts to accommodate OSG 23 New args: ... (as long as it sorts) Kubernetes Hackathon (Next Week) TBD","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230718/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230718/#support-update","text":"Topology/GGUS (BrianL, Mat): Topology does not accept certs from SHA1-signed CAs. We need to petition G\u00fcnter to get the German CA to update their signing key. Mat: Reach out to Gunter to update CA, update Topology to temporarily accept SHA1 Louvain (Mat): OSG-based CVMFS installation hitting Syracuse cache from Europe. We should probably just suggest that he install the EGI config while we sort out policy. Renewing Colorado host certificates (Matt): Awaiting approval by Douglas","title":"Support Update"},{"location":"meetings/2023/TechArea20230718/#devops","text":"Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up)","title":"DevOps"},{"location":"meetings/2023/TechArea20230718/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230718/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230725/","text":"OSG Technology Area Meeting, 25 July 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Mat, Matt, TimT Announcements \u00b6 BrianL out this week Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: BrianL ? (+?) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -6 Open 22 -2 Selected for Dev 30 +3 In Progress 16 -1 Dev Complete 2 -2 Ready for Testing 0 -0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon AI (Mat): Upgrade PATh Facility central manager AI (Mat): Investigate PATh Facility autoscaler issues AI (Matt): Perform various cleanup tasks on the OSG Repo server Kubernetes configuration OSG 23: AI (Matt): Update OSG Repo scripts to work with OSG 23 naming scheme AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23 Discussion \u00b6 Planning to have the copy of the OSDF plugin that is shipped with HTCondor come from the Pelican repo instead of osdf-client; this can be done independently of HTCondor 23 TimT: HTCondor 10.0.7 will be released today, and will have the newest version of scitokens-cpp in the tarballs. HTCondor 10.7.0 will be released later this week and will have apptainer in the tarballs. Support Update \u00b6 TimT: Bockjoo at UFlorida requests packaging \"xrootd-cmstfc\" for EL9; this is a \"contrib\" package meaning it's not officially supported by OSG Software. If building for EL9 is easy then we can do it ourselves, otherwise we will have to contact the developer. Matt: Created IGTF certs for UColorado and send them to the admin; Matt should ping them admin since they haven't responded Topology/GGUS (BrianL, Mat): G\u00fcnter is trying to get a new certificate working with Topology but running into SSL issues. SHA1 was a red herring: SHA1 support was disabled in EL9, not EL8, and Topology is still EL8. Mat will debug. DevOps \u00b6 (none this week) OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"July 25, 2023"},{"location":"meetings/2023/TechArea20230725/#osg-technology-area-meeting-25-july-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Mat, Matt, TimT","title":"OSG Technology Area Meeting, 25 July 2023"},{"location":"meetings/2023/TechArea20230725/#announcements","text":"BrianL out this week","title":"Announcements"},{"location":"meetings/2023/TechArea20230725/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: BrianL ? (+?) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230725/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -6 Open 22 -2 Selected for Dev 30 +3 In Progress 16 -1 Dev Complete 2 -2 Ready for Testing 0 -0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230725/#osg-software-team","text":"Kubernetes Hackathon AI (Mat): Upgrade PATh Facility central manager AI (Mat): Investigate PATh Facility autoscaler issues AI (Matt): Perform various cleanup tasks on the OSG Repo server Kubernetes configuration OSG 23: AI (Matt): Update OSG Repo scripts to work with OSG 23 naming scheme AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230725/#discussion","text":"Planning to have the copy of the OSDF plugin that is shipped with HTCondor come from the Pelican repo instead of osdf-client; this can be done independently of HTCondor 23 TimT: HTCondor 10.0.7 will be released today, and will have the newest version of scitokens-cpp in the tarballs. HTCondor 10.7.0 will be released later this week and will have apptainer in the tarballs.","title":"Discussion"},{"location":"meetings/2023/TechArea20230725/#support-update","text":"TimT: Bockjoo at UFlorida requests packaging \"xrootd-cmstfc\" for EL9; this is a \"contrib\" package meaning it's not officially supported by OSG Software. If building for EL9 is easy then we can do it ourselves, otherwise we will have to contact the developer. Matt: Created IGTF certs for UColorado and send them to the admin; Matt should ping them admin since they haven't responded Topology/GGUS (BrianL, Mat): G\u00fcnter is trying to get a new certificate working with Topology but running into SSL issues. SHA1 was a red herring: SHA1 support was disabled in EL9, not EL8, and Topology is still EL8. Mat will debug.","title":"Support Update"},{"location":"meetings/2023/TechArea20230725/#devops","text":"(none this week)","title":"DevOps"},{"location":"meetings/2023/TechArea20230725/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230725/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230801/","text":"OSG Technology Area Meeting, 1 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 TimT out Wed afternoon - Fri MattW attending the OSG User School next week MattW out this afternoon Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (+?) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 238 +1 Open 16 -6 Selected for Dev 30 +0 In Progress 23 +7 Dev Complete 2 +0 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23. Done? AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) We decided that merging the UW HTCondor and OSG repos would require hackery and also moving to Pungi is too large a lift so we will do the remaining work with mash AI (Mat): update osg-promote to allow Yubikey package signing. Is there a ticket? Mat to create a ticket AI (BrianL): build OSG 23 package list Discussion \u00b6 None this week Support Update \u00b6 CRIC (Mat): X.509 certificate Topology access turned out to be a user issue (missing client certificate bit) UFlorida (Mat): built xrootd-cmstfc for contrib DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"August 1, 2023"},{"location":"meetings/2023/TechArea20230801/#osg-technology-area-meeting-1-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 1 August 2023"},{"location":"meetings/2023/TechArea20230801/#announcements","text":"TimT out Wed afternoon - Fri MattW attending the OSG User School next week MattW out this afternoon","title":"Announcements"},{"location":"meetings/2023/TechArea20230801/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (+?) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230801/#jira-as-of-monday","text":"# of tickets \u0394 State 238 +1 Open 16 -6 Selected for Dev 30 +0 In Progress 23 +7 Dev Complete 2 +0 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230801/#osg-software-team","text":"OSG 23: AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23. Done? AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) We decided that merging the UW HTCondor and OSG repos would require hackery and also moving to Pungi is too large a lift so we will do the remaining work with mash AI (Mat): update osg-promote to allow Yubikey package signing. Is there a ticket? Mat to create a ticket AI (BrianL): build OSG 23 package list","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230801/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230801/#support-update","text":"CRIC (Mat): X.509 certificate Topology access turned out to be a user issue (missing client certificate bit) UFlorida (Mat): built xrootd-cmstfc for contrib","title":"Support Update"},{"location":"meetings/2023/TechArea20230801/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230801/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230801/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230808/","text":"OSG Technology Area Meeting, 8 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL OOO later this morning MattW attending the OSG User School this week MatS OOO Fri - Wed Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 7 (+1) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) AI (Mat): update osg-promote to allow Yubikey package signing AI (BrianL): build OSG 23 package list Kubernetes Hackathon AI (BrianL): test xrootd-multiuser on PATh origin Discussion \u00b6 None this week Support Update \u00b6 JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Georgia Tech (Mat): submit a downtime for them DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"August 8, 2023"},{"location":"meetings/2023/TechArea20230808/#osg-technology-area-meeting-8-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 8 August 2023"},{"location":"meetings/2023/TechArea20230808/#announcements","text":"BrianL OOO later this morning MattW attending the OSG User School this week MatS OOO Fri - Wed","title":"Announcements"},{"location":"meetings/2023/TechArea20230808/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 7 (+1) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230808/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230808/#osg-software-team","text":"OSG 23: AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) AI (Mat): update osg-promote to allow Yubikey package signing AI (BrianL): build OSG 23 package list Kubernetes Hackathon AI (BrianL): test xrootd-multiuser on PATh origin","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230808/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230808/#support-update","text":"JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Georgia Tech (Mat): submit a downtime for them","title":"Support Update"},{"location":"meetings/2023/TechArea20230808/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230808/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230808/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230815/","text":"OSG Technology Area Meeting, 15 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 MatS OOO Fri - Wed Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: MattW Next week: Mat 6 (-1) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) TimT to create empty HTC23 repos for testing Open item: Use same signing key(s) for OSG and HTC? Open item: Generate OSG 23 promotion key(s) AI (BrianL): assign OSG 23 package builds AI (BrianL, Matt): populate bootstrap tags AI (BrianL, Matt): start massive rebuild OSG 3.6 AI (Matt): release new version of xrootd-multiuser AI (BrianL): who knows how to add EPEL packages to the build repos? Miscellaneous AI (Matt): autogenerate Topology IDs AI (Matt): Topology webhook -> GitHub Actions Changes to 2FA will break the webhook in 44 days Currently lives in the topology repo, deployed in the same container Gordon Watts: IRIS HEP talk topic Something K8s related oidc-agent-4.4.2 - still blocked MattW: Create github ticket to restore spec file Discussion \u00b6 None this week Support Update \u00b6 JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Person to contact is John, currently unavailable OSG School Participants requesting accounts X.509 CVMFS Helper Core Dumping on EL9 (Derek) SciTokens support is wrapped up in this package Python SciTokens EPEL package Rebuild for EL9 (Derek) This is at least a month away from being released in EPEL DevOps \u00b6 Really pushing on the python-scitokens EPEL package. CVMFS helper is core dumping in EL9 build: Github Issue OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign pegasus 5.0.6 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"August 15, 2023"},{"location":"meetings/2023/TechArea20230815/#osg-technology-area-meeting-15-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 15 August 2023"},{"location":"meetings/2023/TechArea20230815/#announcements","text":"MatS OOO Fri - Wed","title":"Announcements"},{"location":"meetings/2023/TechArea20230815/#triage-duty","text":"Triage duty shifts Tue-Mon This week: MattW Next week: Mat 6 (-1) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230815/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230815/#osg-software-team","text":"OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) TimT to create empty HTC23 repos for testing Open item: Use same signing key(s) for OSG and HTC? Open item: Generate OSG 23 promotion key(s) AI (BrianL): assign OSG 23 package builds AI (BrianL, Matt): populate bootstrap tags AI (BrianL, Matt): start massive rebuild OSG 3.6 AI (Matt): release new version of xrootd-multiuser AI (BrianL): who knows how to add EPEL packages to the build repos? Miscellaneous AI (Matt): autogenerate Topology IDs AI (Matt): Topology webhook -> GitHub Actions Changes to 2FA will break the webhook in 44 days Currently lives in the topology repo, deployed in the same container Gordon Watts: IRIS HEP talk topic Something K8s related oidc-agent-4.4.2 - still blocked MattW: Create github ticket to restore spec file","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230815/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230815/#support-update","text":"JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Person to contact is John, currently unavailable OSG School Participants requesting accounts X.509 CVMFS Helper Core Dumping on EL9 (Derek) SciTokens support is wrapped up in this package Python SciTokens EPEL package Rebuild for EL9 (Derek) This is at least a month away from being released in EPEL","title":"Support Update"},{"location":"meetings/2023/TechArea20230815/#devops","text":"Really pushing on the python-scitokens EPEL package. CVMFS helper is core dumping in EL9 build: Github Issue","title":"DevOps"},{"location":"meetings/2023/TechArea20230815/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign pegasus 5.0.6 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230815/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230829/","text":"OSG Technology Area Meeting, 29 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: MattW 3 (-3) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Table in design doc for which htcss repos to merge with osg AI (Matt): Complete the two -contrib builds (reach out to Mat for what to do with SVN repo branch) AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) Most tests require the HTCSS-23 condor build, these two don't May require slight updates to test repo AI (BrianL): review OSG 23 package builds Rebuild osg-release with new signing keys AI (TimT): populate HTCSS 23 daily repo Outstanding: condor, condor-plugin. Should be complete today (08/29) Issue: Things are still signed with Condor 10.X keys. Will need to get the signing keys to Tim somehow Will need to create a separate yubikey for this Issue: Moria is EL7, where we've previously seen issues in signing Could also sign on an EL8 machine in the current workflow, maybe AI (Matt): Create new signing yubikey to address the above issue AI (Mat): osg-promote updates Next step is koji OSG 3.6 AI (Matt): follow-up with Josh Willis regarding XRootD build available in testing Miscellaneous AI (BrianL): sort out osg-bot 2FA Should largely work as-is for automated actions with access tokens 2FA changes will cause issues if we need to log into the account though AI (Mat): Figure out issues with PATh-Wisc deployment Discussion \u00b6 None this week Support Update \u00b6 COManage (BrianL): work with CILogon to identify group misconfiguration issues; helped Will Leight with linking org IDs (contact CILogon about strange error) Issue: Group IDs and user IDs are becoming misaligned, which breaks COManage provisioning assumptions Issue: Users with multiple identities cannot be successfully linked to a single COManage user entity DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"August 29, 2023"},{"location":"meetings/2023/TechArea20230829/#osg-technology-area-meeting-29-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 29 August 2023"},{"location":"meetings/2023/TechArea20230829/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230829/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: MattW 3 (-3) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230829/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230829/#osg-software-team","text":"OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Table in design doc for which htcss repos to merge with osg AI (Matt): Complete the two -contrib builds (reach out to Mat for what to do with SVN repo branch) AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) Most tests require the HTCSS-23 condor build, these two don't May require slight updates to test repo AI (BrianL): review OSG 23 package builds Rebuild osg-release with new signing keys AI (TimT): populate HTCSS 23 daily repo Outstanding: condor, condor-plugin. Should be complete today (08/29) Issue: Things are still signed with Condor 10.X keys. Will need to get the signing keys to Tim somehow Will need to create a separate yubikey for this Issue: Moria is EL7, where we've previously seen issues in signing Could also sign on an EL8 machine in the current workflow, maybe AI (Matt): Create new signing yubikey to address the above issue AI (Mat): osg-promote updates Next step is koji OSG 3.6 AI (Matt): follow-up with Josh Willis regarding XRootD build available in testing Miscellaneous AI (BrianL): sort out osg-bot 2FA Should largely work as-is for automated actions with access tokens 2FA changes will cause issues if we need to log into the account though AI (Mat): Figure out issues with PATh-Wisc deployment","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230829/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230829/#support-update","text":"COManage (BrianL): work with CILogon to identify group misconfiguration issues; helped Will Leight with linking org IDs (contact CILogon about strange error) Issue: Group IDs and user IDs are becoming misaligned, which breaks COManage provisioning assumptions Issue: Users with multiple identities cannot be successfully linked to a single COManage user entity","title":"Support Update"},{"location":"meetings/2023/TechArea20230829/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230829/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230829/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230905/","text":"OSG Technology Area Meeting, 5 September 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW, TimT Announcements \u00b6 IRIS-HEP retreat next Mon-Wed: https://indico.cern.ch/event/1288444/page/30534-meeting-participants Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: MattW Next week: TimT 6 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 Automated Jira ticket summary email seems to be flaky (maybe corresponds to Jira maintenace?) # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (BrianL): Switch osg-wn-client to Alma8 - AI (BrianL): Hosted CEs move update WN client scripts to the container image - AI (BrianL): Add support for HelmReleases on Nautilus - AI (Mat): Set up remote Kustomization to TACC - AI (Matt): Create postgres Topology institution database in Kubernetes OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Still an issue with empty repos? AI (Matt): Complete the two -contrib builds AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) May require slight updates to VMU repo regex ( https://github.com/opensciencegrid/vm-test-runs/blob/master/bin/vmu.py#L96-L119 ). Worth just trying it AI (Mat): Examine OSG-Test to see what needs to be updated for OSG 23 AI (TimT): populate HTCSS 23 repos Path of least resistance to compile newer versions of GnuPG on Moria (needed for daily and RC/release builds) AI (Mat): Kojihub update status Apache RPM turns on multiproc module, so does Hiera, apache doesn't like it. Talk to Joe to figure out how to turn off the packaging OSG 3.6 AI (Mat): review osg-pki-tools promotion request AI (Matt): build CA certs packages, merge in EL9 crypto policy hack Miscellaneous AI (BrianL): sort out osg-bot 2FA AI (TimT): debug various failures with HTCondor 10.8.0 release candidate Discussion \u00b6 GlideinWMS RC2 ready, final release should be ready today or tomorrow. - Added optionally enabled structured logging - Added workaround for rrdtool Python binding issues Support Update \u00b6 Caltech (Mat): review OSDF cache ticket for any remaining TODO items DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"September 5, 2023"},{"location":"meetings/2023/TechArea20230905/#osg-technology-area-meeting-5-september-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 5 September 2023"},{"location":"meetings/2023/TechArea20230905/#announcements","text":"IRIS-HEP retreat next Mon-Wed: https://indico.cern.ch/event/1288444/page/30534-meeting-participants","title":"Announcements"},{"location":"meetings/2023/TechArea20230905/#triage-duty","text":"Triage duty shifts Tue-Mon This week: MattW Next week: TimT 6 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230905/#jira-as-of-tuesday-morning","text":"Automated Jira ticket summary email seems to be flaky (maybe corresponds to Jira maintenace?) # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20230905/#osg-software-team","text":"Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (BrianL): Switch osg-wn-client to Alma8 - AI (BrianL): Hosted CEs move update WN client scripts to the container image - AI (BrianL): Add support for HelmReleases on Nautilus - AI (Mat): Set up remote Kustomization to TACC - AI (Matt): Create postgres Topology institution database in Kubernetes OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Still an issue with empty repos? AI (Matt): Complete the two -contrib builds AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) May require slight updates to VMU repo regex ( https://github.com/opensciencegrid/vm-test-runs/blob/master/bin/vmu.py#L96-L119 ). Worth just trying it AI (Mat): Examine OSG-Test to see what needs to be updated for OSG 23 AI (TimT): populate HTCSS 23 repos Path of least resistance to compile newer versions of GnuPG on Moria (needed for daily and RC/release builds) AI (Mat): Kojihub update status Apache RPM turns on multiproc module, so does Hiera, apache doesn't like it. Talk to Joe to figure out how to turn off the packaging OSG 3.6 AI (Mat): review osg-pki-tools promotion request AI (Matt): build CA certs packages, merge in EL9 crypto policy hack Miscellaneous AI (BrianL): sort out osg-bot 2FA AI (TimT): debug various failures with HTCondor 10.8.0 release candidate","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230905/#discussion","text":"GlideinWMS RC2 ready, final release should be ready today or tomorrow. - Added optionally enabled structured logging - Added workaround for rrdtool Python binding issues","title":"Discussion"},{"location":"meetings/2023/TechArea20230905/#support-update","text":"Caltech (Mat): review OSDF cache ticket for any remaining TODO items","title":"Support Update"},{"location":"meetings/2023/TechArea20230905/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230905/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230905/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230919/","text":"OSG Technology Area Meeting, 19 September 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 -3 Open 20 -1 Selected for Dev 30 -3 In Progress 23 +0 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (Matt): If no xDD tasks, set up shoveler in front of tiger cache (INF-1265) OSG 23: - AI (TimT): get HTCondor 23 daily repos in place. This is blocking OSG 23 really badly. - AI (Mat): Shepherd Kojihub upgrade to allow promotion via Yubikey (SOFTWARE-5637) - Needs to be updated for internal-development + internal-release - AI (Mat): Replace \"osg-internal\" tags and targets in 3.7 with \"osg-3.7-extra-deps\" (SOFTWARE-5611) - AI (Matt): Generate 5 Yubikeys with developer signing key OSG 3.6 - AI (Matt): XRootD 5.6.2 (sometime this week) Miscellaneous - AI (BrianL): sort out osg-bot 2FA (needs to be done this week!) Discussion \u00b6 GlideinWMS 3.10.4 is ready for testing - Mats Rynge reported a bug in token caching due to an EL7 pyjwt bug - Marco gave Mats a patch -- this is not fatal, just errors in the logs Support Update \u00b6 LIGO (Mat): unexpected behavior for XRootD gridmap, somewhat related Jira ticket CMS (Matt): jsoncpp version built for all EL versions, xrootd-cmstfc still needs to be built DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"September 19, 2023"},{"location":"meetings/2023/TechArea20230919/#osg-technology-area-meeting-19-september-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 19 September 2023"},{"location":"meetings/2023/TechArea20230919/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230919/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230919/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 -3 Open 20 -1 Selected for Dev 30 -3 In Progress 23 +0 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20230919/#osg-software-team","text":"Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (Matt): If no xDD tasks, set up shoveler in front of tiger cache (INF-1265) OSG 23: - AI (TimT): get HTCondor 23 daily repos in place. This is blocking OSG 23 really badly. - AI (Mat): Shepherd Kojihub upgrade to allow promotion via Yubikey (SOFTWARE-5637) - Needs to be updated for internal-development + internal-release - AI (Mat): Replace \"osg-internal\" tags and targets in 3.7 with \"osg-3.7-extra-deps\" (SOFTWARE-5611) - AI (Matt): Generate 5 Yubikeys with developer signing key OSG 3.6 - AI (Matt): XRootD 5.6.2 (sometime this week) Miscellaneous - AI (BrianL): sort out osg-bot 2FA (needs to be done this week!)","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230919/#discussion","text":"GlideinWMS 3.10.4 is ready for testing - Mats Rynge reported a bug in token caching due to an EL7 pyjwt bug - Marco gave Mats a patch -- this is not fatal, just errors in the logs","title":"Discussion"},{"location":"meetings/2023/TechArea20230919/#support-update","text":"LIGO (Mat): unexpected behavior for XRootD gridmap, somewhat related Jira ticket CMS (Matt): jsoncpp version built for all EL versions, xrootd-cmstfc still needs to be built","title":"Support Update"},{"location":"meetings/2023/TechArea20230919/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230919/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230919/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230926/","text":"OSG Technology Area Meeting, 26 September 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: Matt 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 233 -1 Open 17 -3 Selected for Dev 32 +2 In Progress 24 +1 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 OSG 23: - AI (TimT): get HTCSS 23 RCs in place - AI (Mat): Coordinate transition to kojihub2000. Absolutely has to be done by Thursday. - AI (Matt): Mass promote packages post upgrade - AI (BrianL): Add support for OSG 23 containers - AI (TimT): kick off test of WN client tarball creation ~ OSG 23 - AI (BrianL): Review docker-osg-build container PR - AI (Matt): add new GPG keys on repo - We may have to backversion GlideinWMS - For October: add cron job regen-repo for minefield + HTCSS repos Discussion \u00b6 None this week Support Update \u00b6 JLab (Matt): instruct them on how to install XRootD debug symbols, look for core files DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"September 26, 2023"},{"location":"meetings/2023/TechArea20230926/#osg-technology-area-meeting-26-september-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 26 September 2023"},{"location":"meetings/2023/TechArea20230926/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230926/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: Matt 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230926/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 233 -1 Open 17 -3 Selected for Dev 32 +2 In Progress 24 +1 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20230926/#osg-software-team","text":"OSG 23: - AI (TimT): get HTCSS 23 RCs in place - AI (Mat): Coordinate transition to kojihub2000. Absolutely has to be done by Thursday. - AI (Matt): Mass promote packages post upgrade - AI (BrianL): Add support for OSG 23 containers - AI (TimT): kick off test of WN client tarball creation ~ OSG 23 - AI (BrianL): Review docker-osg-build container PR - AI (Matt): add new GPG keys on repo - We may have to backversion GlideinWMS - For October: add cron job regen-repo for minefield + HTCSS repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230926/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230926/#support-update","text":"JLab (Matt): instruct them on how to install XRootD debug symbols, look for core files","title":"Support Update"},{"location":"meetings/2023/TechArea20230926/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230926/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230926/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231003/","text":"OSG Technology Area Meeting, 3 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: TimT 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 OSG 23: - Tasks for today - AI (Matt): Kick off WN tarball scripts - AI (TimT): Write OSG 23 upgrade instructions - AI (BrianL): Ensure container images are built - AI (BrianL): Update release notes - AI (TimT): Announce release! - Follow-on tasks - Test FNAL build access - Remove repo FIXME hacks - Improve Kerberos support in osg-promote - Additional mash cache for 23 dev repos (almost done?) - Figure out if we need VOMS for EL9/an update to EL8 - HTCondor-CE + Torque failures - Summarize problems encountered during release process Kuberentes Hackathon: - AI (Mat, BrianL): repo cleanup - AI (BrianL): troubleshoot TACC PATh Facility - AI (Matt): update central collector host cert - AI (Matt): stash-cache + shoveler work Discussion \u00b6 Marco: GlideinWMS released last week and has been stable so far; factory ops has not reported problems. Planning to work with JeffD to improve GlideinWMS containers. Support Update \u00b6 JLab (Matt, BrianL): XRootD core dump, issues with proxy config with gfal tools DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"October 3, 2023"},{"location":"meetings/2023/TechArea20231003/#osg-technology-area-meeting-3-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 3 October 2023"},{"location":"meetings/2023/TechArea20231003/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231003/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: TimT 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231003/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231003/#osg-software-team","text":"OSG 23: - Tasks for today - AI (Matt): Kick off WN tarball scripts - AI (TimT): Write OSG 23 upgrade instructions - AI (BrianL): Ensure container images are built - AI (BrianL): Update release notes - AI (TimT): Announce release! - Follow-on tasks - Test FNAL build access - Remove repo FIXME hacks - Improve Kerberos support in osg-promote - Additional mash cache for 23 dev repos (almost done?) - Figure out if we need VOMS for EL9/an update to EL8 - HTCondor-CE + Torque failures - Summarize problems encountered during release process Kuberentes Hackathon: - AI (Mat, BrianL): repo cleanup - AI (BrianL): troubleshoot TACC PATh Facility - AI (Matt): update central collector host cert - AI (Matt): stash-cache + shoveler work","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231003/#discussion","text":"Marco: GlideinWMS released last week and has been stable so far; factory ops has not reported problems. Planning to work with JeffD to improve GlideinWMS containers.","title":"Discussion"},{"location":"meetings/2023/TechArea20231003/#support-update","text":"JLab (Matt, BrianL): XRootD core dump, issues with proxy config with gfal tools","title":"Support Update"},{"location":"meetings/2023/TechArea20231003/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231003/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231003/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231010/","text":"OSG Technology Area Meeting, 10 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, Tim Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 4 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 A fair amount of OSG 23 work remains https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 , though some tickets look like they may be able to be closed. Top priorities include: - Fix build signing/development (fixed by Matt) - Test and provide instructions for FNAL build access - Figure out if we need VOMS for EL9/an update to EL8 - Update docs for OSG 23 tarballs and images Miscellaneous - AI (BrianL, Mat, Matt): offboard Carl and Brian Chase Discussion \u00b6 Code freeze for HTCondor 23.1.0 and 23.0.1 is this week Marco: new features in progress for the next GlideinWMS release and development release; GlideinWMS 3.10.5 is working well. Marco will be unavailable for the next two weeks due to vacation and Fermilab workshop. AI (Marco): Send Todd Tannenbaum instructions for how to configure GlideinWMS to use apptainer from the HTCondor tarball. Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"October 10, 2023"},{"location":"meetings/2023/TechArea20231010/#osg-technology-area-meeting-10-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, Tim","title":"OSG Technology Area Meeting, 10 October 2023"},{"location":"meetings/2023/TechArea20231010/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231010/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 4 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231010/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231010/#osg-software-team","text":"A fair amount of OSG 23 work remains https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 , though some tickets look like they may be able to be closed. Top priorities include: - Fix build signing/development (fixed by Matt) - Test and provide instructions for FNAL build access - Figure out if we need VOMS for EL9/an update to EL8 - Update docs for OSG 23 tarballs and images Miscellaneous - AI (BrianL, Mat, Matt): offboard Carl and Brian Chase","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231010/#discussion","text":"Code freeze for HTCondor 23.1.0 and 23.0.1 is this week Marco: new features in progress for the next GlideinWMS release and development release; GlideinWMS 3.10.5 is working well. Marco will be unavailable for the next two weeks due to vacation and Fermilab workshop. AI (Marco): Send Todd Tannenbaum instructions for how to configure GlideinWMS to use apptainer from the HTCondor tarball.","title":"Discussion"},{"location":"meetings/2023/TechArea20231010/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20231010/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231010/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231010/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231017/","text":"OSG Technology Area Meeting, 17 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - We want to upgrade various Tiger components (Kubernetes, Flux, Kustomize) and need to make sure our existing apps don't get broken, making changes as necessary. AI (BrianA): Investigate the upgrades. Things to note: - \"patchesStrategicMerge\" has been replaced with \"patches\" - \"vars\" are deprecated; \"replacements\" are the suggested replacement - AI (BrianL): TACC PATh Facility - AI (Mat): Finish deploying repo on Tempest - AI (Mat): osgvo-docker-pilot items We're getting close to Done Enough for OSG 23 https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . Remaining top items - Test and provide instructions for FNAL build access. Mat to write instructions. - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL) Update docs for OSG 23 tarballs and images - AI (Matt): Update mash scripts to pull HTCSS 23 RC packages into 23-{main,upcoming}-testing - AI (Matt): cpio in EL9 tarballs - AI (Mat): cronjob to regen repos to pull in HTCondor RPMs Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase Discussion \u00b6 HTCondor 23.1.0 and 23.0.1 are going onto the CHTC pool this week; we want to deploy in the OSPool as well, but BrianL and Mat will need to help UChicago staff upgrade their APs to OSG 23 first. Support Update \u00b6 JLab (BrianL, Matt): fts-rest-client created non-RFC proxies, which XRootD didn't like (reporting an unknown CA). Next issue is that macaroons configuration is apparently causing XRootD to dump core. UCSD (Mat): feature request for OSDF area with public read and authenticated write Kisti (Matt): got affirmation that new XRootD build contains the relevant changes DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Ready for Release Nothing Yet Discussion \u00b6 Release tomorrow","title":"October 17, 2023"},{"location":"meetings/2023/TechArea20231017/#osg-technology-area-meeting-17-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 17 October 2023"},{"location":"meetings/2023/TechArea20231017/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231017/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231017/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231017/#osg-software-team","text":"Kubernetes Hackathon - We want to upgrade various Tiger components (Kubernetes, Flux, Kustomize) and need to make sure our existing apps don't get broken, making changes as necessary. AI (BrianA): Investigate the upgrades. Things to note: - \"patchesStrategicMerge\" has been replaced with \"patches\" - \"vars\" are deprecated; \"replacements\" are the suggested replacement - AI (BrianL): TACC PATh Facility - AI (Mat): Finish deploying repo on Tempest - AI (Mat): osgvo-docker-pilot items We're getting close to Done Enough for OSG 23 https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . Remaining top items - Test and provide instructions for FNAL build access. Mat to write instructions. - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL) Update docs for OSG 23 tarballs and images - AI (Matt): Update mash scripts to pull HTCSS 23 RC packages into 23-{main,upcoming}-testing - AI (Matt): cpio in EL9 tarballs - AI (Mat): cronjob to regen repos to pull in HTCondor RPMs Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231017/#discussion","text":"HTCondor 23.1.0 and 23.0.1 are going onto the CHTC pool this week; we want to deploy in the OSPool as well, but BrianL and Mat will need to help UChicago staff upgrade their APs to OSG 23 first.","title":"Discussion"},{"location":"meetings/2023/TechArea20231017/#support-update","text":"JLab (BrianL, Matt): fts-rest-client created non-RFC proxies, which XRootD didn't like (reporting an unknown CA). Next issue is that macaroons configuration is apparently causing XRootD to dump core. UCSD (Mat): feature request for OSDF area with public read and authenticated write Kisti (Matt): got affirmation that new XRootD build contains the relevant changes","title":"Support Update"},{"location":"meetings/2023/TechArea20231017/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231017/#osg-release-team","text":"Ready for Testing HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Ready for Release Nothing Yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231017/#discussion_1","text":"Release tomorrow","title":"Discussion"},{"location":"meetings/2023/TechArea20231024/","text":"OSG Technology Area Meeting, 26 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: Matt 3 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 246 +2 Open 28 -2 Selected for Dev 26 +0 In Progress 21 +1 Dev Complete 3 +3 Ready for Testing 2 +2 Ready for Release OSG Software Team \u00b6 Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase - AI (Mat) XRootD tarball for Pelican - AI (Mat) XRDHOST env is not working with XRootD 5.6.2 Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat) Update docs for OSG 23 tarballs - AI (Tim) Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL) Finish transition of internal containers to OSG 23 - AI (Matt) HTCondor repo rsync failures should cause update_repos.sh to fail Discussion \u00b6 None this week Support Update \u00b6 JLab (Mat): submit a GitHub issue for the macaroons coredump DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Discussion \u00b6 Release Thursday","title":"October 24, 2023"},{"location":"meetings/2023/TechArea20231024/#osg-technology-area-meeting-26-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 26 October 2023"},{"location":"meetings/2023/TechArea20231024/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231024/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: Matt 3 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231024/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 246 +2 Open 28 -2 Selected for Dev 26 +0 In Progress 21 +1 Dev Complete 3 +3 Ready for Testing 2 +2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231024/#osg-software-team","text":"Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase - AI (Mat) XRootD tarball for Pelican - AI (Mat) XRDHOST env is not working with XRootD 5.6.2 Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat) Update docs for OSG 23 tarballs - AI (Tim) Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL) Finish transition of internal containers to OSG 23 - AI (Matt) HTCondor repo rsync failures should cause update_repos.sh to fail","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231024/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231024/#support-update","text":"JLab (Mat): submit a GitHub issue for the macaroons coredump","title":"Support Update"},{"location":"meetings/2023/TechArea20231024/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231024/#osg-release-team","text":"Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34]","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231024/#discussion_1","text":"Release Thursday","title":"Discussion"},{"location":"meetings/2023/TechArea20231031/","text":"OSG Technology Area Meeting, 31 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: TimT 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 24 -4 Selected for Dev 30 +4 In Progress 19 -2 Dev Complete 2 -1 Ready for Testing 0 -2 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - AI (Mat): Set up Tempest repo - AI (Matt): xDD MongoDB, XRootD shoveler in base - AI (BrianL, Mat): investigate ITB OSDF; set up image updates Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (Mat): XRDHOST env is not working with XRootD 5.6.2 - AI (Mat): IGTF CA certificate update - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (TimT): Release HTCondor 23.0.1 and 23.1.0; send release announcement to OSG lists as well Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat): Update docs for OSG 23 tarballs - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Matt): Write signed OSG 23 RPMs to disk and turn strict signature checking on for 23-development Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Discussion \u00b6 Release Thursday","title":"October 31, 2023"},{"location":"meetings/2023/TechArea20231031/#osg-technology-area-meeting-31-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 31 October 2023"},{"location":"meetings/2023/TechArea20231031/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231031/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: TimT 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231031/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 24 -4 Selected for Dev 30 +4 In Progress 19 -2 Dev Complete 2 -1 Ready for Testing 0 -2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231031/#osg-software-team","text":"Kubernetes Hackathon - AI (Mat): Set up Tempest repo - AI (Matt): xDD MongoDB, XRootD shoveler in base - AI (BrianL, Mat): investigate ITB OSDF; set up image updates Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (Mat): XRDHOST env is not working with XRootD 5.6.2 - AI (Mat): IGTF CA certificate update - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (TimT): Release HTCondor 23.0.1 and 23.1.0; send release announcement to OSG lists as well Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat): Update docs for OSG 23 tarballs - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Matt): Write signed OSG 23 RPMs to disk and turn strict signature checking on for 23-development","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231031/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231031/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20231031/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231031/#osg-release-team","text":"Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34]","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231031/#discussion_1","text":"Release Thursday","title":"Discussion"},{"location":"meetings/2023/TechArea20231107/","text":"OSG Technology Area Meeting, 7 November 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, JohnT, MattW, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 3 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (???): ship first batch of vo-client updates for IGTF CA 3 - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (BrianL): put together backfill container RPM package ticket for MattW Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 Discussion \u00b6 How should we manage containers produced by OSG Staff? We should separate needs/reqs for containers that are built off of the OSG Software pipeline (dev -> testing -> release Yum repos) vs everything else Ideally, for everything else, we'd have a GitHub workflow template or action and some convention for tagging as well as immutability/retention policies Repo sprawl is a concern for security and management. Harbor creds are per organization so it may be prudent to separate out mostly-internally facing containers to a separate project, e.g. osg-internal Consolidation into the images repo doesn't work well for many images right now, especially those with \"large\" code bases as it makes dev (think tracking issues/PRs) more difficult. We should think of the SVN packaging repo as an analog here. We could add some additional flexibility to the images repo that would allow per-image references to external, trusted repos and usage of build processes that aren't so tightly tied to the Software release process. For the time being for the xrootd-monitoring-collector , we should just use a custom GitHub Action Implementation discussion in SOFTWARE-5013 Release of scitokens-cpp is in bodhi and needs karma. Ready for TimT tobuild for Debian EPEL7: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f0f162d810 EPEL8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f9dc18f284 EPEL9: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2dfb911a54 Support Update \u00b6 CVMFS issue with the latest version that causes the client to hang. DaveD is on it. DevOps \u00b6 scitokens-cpp release this week. Already in fedora update system bodhi. OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.2 osg-system-profiler 1.7.0 Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 7, 2023"},{"location":"meetings/2023/TechArea20231107/#osg-technology-area-meeting-7-november-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, JohnT, MattW, TimT","title":"OSG Technology Area Meeting, 7 November 2023"},{"location":"meetings/2023/TechArea20231107/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231107/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 3 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231107/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231107/#osg-software-team","text":"Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (???): ship first batch of vo-client updates for IGTF CA 3 - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (BrianL): put together backfill container RPM package ticket for MattW Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231107/#discussion","text":"How should we manage containers produced by OSG Staff? We should separate needs/reqs for containers that are built off of the OSG Software pipeline (dev -> testing -> release Yum repos) vs everything else Ideally, for everything else, we'd have a GitHub workflow template or action and some convention for tagging as well as immutability/retention policies Repo sprawl is a concern for security and management. Harbor creds are per organization so it may be prudent to separate out mostly-internally facing containers to a separate project, e.g. osg-internal Consolidation into the images repo doesn't work well for many images right now, especially those with \"large\" code bases as it makes dev (think tracking issues/PRs) more difficult. We should think of the SVN packaging repo as an analog here. We could add some additional flexibility to the images repo that would allow per-image references to external, trusted repos and usage of build processes that aren't so tightly tied to the Software release process. For the time being for the xrootd-monitoring-collector , we should just use a custom GitHub Action Implementation discussion in SOFTWARE-5013 Release of scitokens-cpp is in bodhi and needs karma. Ready for TimT tobuild for Debian EPEL7: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f0f162d810 EPEL8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f9dc18f284 EPEL9: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2dfb911a54","title":"Discussion"},{"location":"meetings/2023/TechArea20231107/#support-update","text":"CVMFS issue with the latest version that causes the client to hang. DaveD is on it.","title":"Support Update"},{"location":"meetings/2023/TechArea20231107/#devops","text":"scitokens-cpp release this week. Already in fedora update system bodhi.","title":"DevOps"},{"location":"meetings/2023/TechArea20231107/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.2 osg-system-profiler 1.7.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231107/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231114/","text":"OSG Technology Area Meeting, 7 November 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - AI (Mat): Pelican ITB director! Work with the dev team to figure it out + William who will be working on the registry - Fengping got Mat unstuck on this - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): DSI oauth2-proxy Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows - Setup is working, not documented yet - AI (BrianL): Write release announcement for impending OSG CA certs packaging changes (aiming for week of Nov 27) - AI (MattW): osg-ca-certs sha1 workaround: Investigate failures with -java subpackage - Might be issue with tests rather than -java subpackage - AI (TimT): osg-ca-certs sha1 workaround: announce that this change is upcoming, will break java applications Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 AI (BrainL): vo-client, osg-pki-tools doesn't work on EL9 (via FermiLab) Only FermiLab directly interacts with the InCommon API via this tool, our capability to debug is limited AI (Mat): JLab ran into a segfault bug with XRootD, XRootD released a patch We need to backport/release this patch DevOps \u00b6 AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 14, 2023"},{"location":"meetings/2023/TechArea20231114/#osg-technology-area-meeting-7-november-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 7 November 2023"},{"location":"meetings/2023/TechArea20231114/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231114/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231114/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231114/#osg-software-team","text":"Kubernetes Hackathon - AI (Mat): Pelican ITB director! Work with the dev team to figure it out + William who will be working on the registry - Fengping got Mat unstuck on this - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): DSI oauth2-proxy Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows - Setup is working, not documented yet - AI (BrianL): Write release announcement for impending OSG CA certs packaging changes (aiming for week of Nov 27) - AI (MattW): osg-ca-certs sha1 workaround: Investigate failures with -java subpackage - Might be issue with tests rather than -java subpackage - AI (TimT): osg-ca-certs sha1 workaround: announce that this change is upcoming, will break java applications Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231114/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231114/#support-update","text":"AI (BrainL): vo-client, osg-pki-tools doesn't work on EL9 (via FermiLab) Only FermiLab directly interacts with the InCommon API via this tool, our capability to debug is limited AI (Mat): JLab ran into a segfault bug with XRootD, XRootD released a patch We need to backport/release this patch","title":"Support Update"},{"location":"meetings/2023/TechArea20231114/#devops","text":"AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart","title":"DevOps"},{"location":"meetings/2023/TechArea20231114/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231114/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231128/","text":"OSG Technology Area Meeting, 28 November 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: TimT 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 246 -3 Open 23 +0 Selected for Dev 29 +1 In Progress 20 -1 Dev Complete 2 +0 Ready for Testing 1 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - AI (Mat): Pelican origin - William shadowing - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): Cleanup OSG 23 containers, maybe Release - AI (Matt): OSG CA certs workaround. Are there still mysterious test failures with the -java subpackage - AI (Matt): vo-client update Miscellaneous: - NRAO hero run - AI (Mat): submit transform to flock out to the OSPool from AP1 - AI (Mat): analyze Felipe's logs and construct a GPU site go/no-go list - AI (BrianL): Fix CHTC CE GPU submission - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 JLab (Mat): Kurt running into another XRootD segfault Topology/COManage (Mat): interrupted enrollment flow Lebanon (BrianL): new site, consulting with management regarding policy DevOps \u00b6 AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet Discussion \u00b6 CA cert updates? Punting for ~week. RE: AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) Done in previous release. Dropping latest OASIS worker node client symlink. Sites should be making a concious choice to change version. Possibly in Febuary?","title":"November 28, 2023"},{"location":"meetings/2023/TechArea20231128/#osg-technology-area-meeting-28-november-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 28 November 2023"},{"location":"meetings/2023/TechArea20231128/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231128/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: TimT 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231128/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 246 -3 Open 23 +0 Selected for Dev 29 +1 In Progress 20 -1 Dev Complete 2 +0 Ready for Testing 1 -1 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231128/#osg-software-team","text":"Kubernetes Hackathon - AI (Mat): Pelican origin - William shadowing - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): Cleanup OSG 23 containers, maybe Release - AI (Matt): OSG CA certs workaround. Are there still mysterious test failures with the -java subpackage - AI (Matt): vo-client update Miscellaneous: - NRAO hero run - AI (Mat): submit transform to flock out to the OSPool from AP1 - AI (Mat): analyze Felipe's logs and construct a GPU site go/no-go list - AI (BrianL): Fix CHTC CE GPU submission - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231128/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231128/#support-update","text":"JLab (Mat): Kurt running into another XRootD segfault Topology/COManage (Mat): interrupted enrollment flow Lebanon (BrianL): new site, consulting with management regarding policy","title":"Support Update"},{"location":"meetings/2023/TechArea20231128/#devops","text":"AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart","title":"DevOps"},{"location":"meetings/2023/TechArea20231128/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231128/#discussion_1","text":"CA cert updates? Punting for ~week. RE: AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) Done in previous release. Dropping latest OASIS worker node client symlink. Sites should be making a concious choice to change version. Possibly in Febuary?","title":"Discussion"},{"location":"meetings/2023/TechArea20231205/","text":"OSG Technology Area Meeting, 5 December 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Matt, TimT Announcements \u00b6 Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 24 +1 Selected for Dev 25 -4 In Progress 20 +0 Dev Complete 3 +1 Ready for Testing 2 +2 Ready for Release OSG Software Team \u00b6 Miscellaneous: - AI (Matt): add shoveler to OSDF origin helm chart Release - AI (Matt): build new xrootd-multiuser RPM - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 OSPool (BrianL): AP40 job submission issues were due to changes in the authZ level for condor_reconfig The University of Tokyo (Matt): answering questions about origin outbound ports DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.4 Add SecEntity.addrInfo patch to xrootd 5.6 Backport certificate chain patch to XRootD 5.6 Ready for Release Nothing yet Discussion \u00b6 AI (TimT): Check in with Fabio regarding XRootD testing","title":"December 5, 2023"},{"location":"meetings/2023/TechArea20231205/#osg-technology-area-meeting-5-december-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Matt, TimT","title":"OSG Technology Area Meeting, 5 December 2023"},{"location":"meetings/2023/TechArea20231205/#announcements","text":"Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5","title":"Announcements"},{"location":"meetings/2023/TechArea20231205/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231205/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 24 +1 Selected for Dev 25 -4 In Progress 20 +0 Dev Complete 3 +1 Ready for Testing 2 +2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231205/#osg-software-team","text":"Miscellaneous: - AI (Matt): add shoveler to OSDF origin helm chart Release - AI (Matt): build new xrootd-multiuser RPM - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231205/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231205/#support-update","text":"OSPool (BrianL): AP40 job submission issues were due to changes in the authZ level for condor_reconfig The University of Tokyo (Matt): answering questions about origin outbound ports","title":"Support Update"},{"location":"meetings/2023/TechArea20231205/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231205/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.4 Add SecEntity.addrInfo patch to xrootd 5.6 Backport certificate chain patch to XRootD 5.6 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231205/#discussion_1","text":"AI (TimT): Check in with Fabio regarding XRootD testing","title":"Discussion"},{"location":"meetings/2023/TechArea20231212/","text":"OSG Technology Area Meeting, 12 December 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 245 -2 Open 24 +1 Selected for Dev 27 +2 In Progress 19 -1 Dev Complete 3 +0 Ready for Testing 0 -2 Ready for Release OSG Software Team \u00b6 Miscellaneous: - AI (Matt): build OSDF cache helm chart Release - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 OSPool OSDF (BrianL): troubleshoot Showmic's OSDF job failures. Turned out to be too-large tokens due to extensive project group membership in COManage The University of Tokyo (BrianL): help them with cache registration. COManage Topology contact update appears to still be broken University of Wisconsin (BrianL): CarlV lost access to Koji Vanderbilt/Colorado (BrianL): help with IGTF cert renewals DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing XRootD 5.6.4 XCache 3.6.0 xrootd-multiuser 2.2.0 Ready for Release Nothing yet Discussion \u00b6 AI (TimT): Check in with Fabio regarding XRootD testing","title":"December 12, 2023"},{"location":"meetings/2023/TechArea20231212/#osg-technology-area-meeting-12-december-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 12 December 2023"},{"location":"meetings/2023/TechArea20231212/#announcements","text":"Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5","title":"Announcements"},{"location":"meetings/2023/TechArea20231212/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231212/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 245 -2 Open 24 +1 Selected for Dev 27 +2 In Progress 19 -1 Dev Complete 3 +0 Ready for Testing 0 -2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231212/#osg-software-team","text":"Miscellaneous: - AI (Matt): build OSDF cache helm chart Release - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231212/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231212/#support-update","text":"OSPool OSDF (BrianL): troubleshoot Showmic's OSDF job failures. Turned out to be too-large tokens due to extensive project group membership in COManage The University of Tokyo (BrianL): help them with cache registration. COManage Topology contact update appears to still be broken University of Wisconsin (BrianL): CarlV lost access to Koji Vanderbilt/Colorado (BrianL): help with IGTF cert renewals","title":"Support Update"},{"location":"meetings/2023/TechArea20231212/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231212/#osg-release-team","text":"Ready for Testing XRootD 5.6.4 XCache 3.6.0 xrootd-multiuser 2.2.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231212/#discussion_1","text":"AI (TimT): Check in with Fabio regarding XRootD testing","title":"Discussion"},{"location":"meetings/2023/TechArea20231219/","text":"OSG Technology Area Meeting, 12 December 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt, TimT Announcements \u00b6 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Derek OOO Dec 22 - Jan 2 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 244 -1 Open 23 -1 Selected for Dev 24 -3 In Progress 18 -1 Dev Complete 2 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus today! Tickets incoming Release - AI (Mat): release xrdcl-pelican - AI (Matt): verify cadist is populated by osg-ca-certs-java Miscellaneous: - AI (BrianL, Mat): deploy ITB OSDF Pelican origin - AI (Matt): build OSDF cache helm chart Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - AI (Matt): Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 HTCondor 23.x release candidate is deployed on the CHTC pool; CentOS 7 is added back as a supported platform. The IGTF 1.126 CA distribution preemptively pulled the old IGTF CA (that is still valid and in use); OSG software will not be releasing that version until the next year. Support Update \u00b6 University of Tokyo/KAGRA (BrianL): University of Tokyo KAGRA cache admin's registration was not showing up in Topology; Brian applied a workaround and also fixed the issue with the Topology software JLab (Matt): Admins were informed about a new XRootD version that should fix their crash DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet Discussion \u00b6 Delay releasing CA bundle based on IGTF 1.126 until January ospool-ap should always use OSG 23 Docker images","title":"December 19, 2023"},{"location":"meetings/2023/TechArea20231219/#osg-technology-area-meeting-12-december-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 12 December 2023"},{"location":"meetings/2023/TechArea20231219/#announcements","text":"Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Derek OOO Dec 22 - Jan 2","title":"Announcements"},{"location":"meetings/2023/TechArea20231219/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231219/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 244 -1 Open 23 -1 Selected for Dev 24 -3 In Progress 18 -1 Dev Complete 2 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231219/#osg-software-team","text":"Doc focus today! Tickets incoming Release - AI (Mat): release xrdcl-pelican - AI (Matt): verify cadist is populated by osg-ca-certs-java Miscellaneous: - AI (BrianL, Mat): deploy ITB OSDF Pelican origin - AI (Matt): build OSDF cache helm chart Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - AI (Matt): Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231219/#discussion","text":"HTCondor 23.x release candidate is deployed on the CHTC pool; CentOS 7 is added back as a supported platform. The IGTF 1.126 CA distribution preemptively pulled the old IGTF CA (that is still valid and in use); OSG software will not be releasing that version until the next year.","title":"Discussion"},{"location":"meetings/2023/TechArea20231219/#support-update","text":"University of Tokyo/KAGRA (BrianL): University of Tokyo KAGRA cache admin's registration was not showing up in Topology; Brian applied a workaround and also fixed the issue with the Topology software JLab (Matt): Admins were informed about a new XRootD version that should fix their crash","title":"Support Update"},{"location":"meetings/2023/TechArea20231219/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231219/#osg-release-team","text":"Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231219/#discussion_1","text":"Delay releasing CA bundle based on IGTF 1.126 until January ospool-ap should always use OSG 23 Docker images","title":"Discussion"},{"location":"meetings/2024/TechArea20240102/","text":"OSG Technology Area Meeting, 2 January 2024 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, TimT Announcements \u00b6 BrianL OOO Dec 20 - Jan 5 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday morning) \u00b6 # of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Brian B was unable to reproduce the failures that the osg-ca-certs package change is meant to work around (and so unable to verify that the workaround worked). We will need to ask the original reporter to reproduce it AI (Mat): add Institution to OSG ID mapping Topology endpoint AI (Mat): release xrdcl-pelican AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files Discussion \u00b6 GlideinWMS 3.10.6 RC is planned for the end of this week, containing mostly bugfixes: Fix for the Python-based match policy function not being correctly imported Compatibility with new versions of the M2Crypto library New factory config options by Marco Mascheroni HTCondor 23.3.0/23.0.3 scheduled for Thursday Support Update \u00b6 Mat (KAGRA): Tokyo site reporting issues while testing origin authentication; Mat will continue to debug DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet Discussion \u00b6","title":"January 2, 2024"},{"location":"meetings/2024/TechArea20240102/#osg-technology-area-meeting-2-january-2024","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 2 January 2024"},{"location":"meetings/2024/TechArea20240102/#announcements","text":"BrianL OOO Dec 20 - Jan 5","title":"Announcements"},{"location":"meetings/2024/TechArea20240102/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2024/TechArea20240102/#jira-as-of-monday-morning","text":"# of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday morning)"},{"location":"meetings/2024/TechArea20240102/#osg-software-team","text":"Brian B was unable to reproduce the failures that the osg-ca-certs package change is meant to work around (and so unable to verify that the workaround worked). We will need to ask the original reporter to reproduce it AI (Mat): add Institution to OSG ID mapping Topology endpoint AI (Mat): release xrdcl-pelican AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files","title":"OSG Software Team"},{"location":"meetings/2024/TechArea20240102/#discussion","text":"GlideinWMS 3.10.6 RC is planned for the end of this week, containing mostly bugfixes: Fix for the Python-based match policy function not being correctly imported Compatibility with new versions of the M2Crypto library New factory config options by Marco Mascheroni HTCondor 23.3.0/23.0.3 scheduled for Thursday","title":"Discussion"},{"location":"meetings/2024/TechArea20240102/#support-update","text":"Mat (KAGRA): Tokyo site reporting issues while testing origin authentication; Mat will continue to debug","title":"Support Update"},{"location":"meetings/2024/TechArea20240102/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2024/TechArea20240102/#osg-release-team","text":"Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2024/TechArea20240102/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2024/TechArea20240109/","text":"OSG Technology Area Meeting, 9 January 2024 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday morning) \u00b6 # of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon: - AI (BrianL): clean up last Flux v1 Helm Charts, OSG 23 container image roundup - AI (Matt): xDD tasks? OSG institution frontend + OAuth2 - AI (Mat): new Yum repos on Tempest, auto-update EPs on the PATh Facility Release: - Frontier Squid + CarlV osg-build status? - AI (Matt): build VOMS for EL9 Miscellaneous: - AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing Nothing yet Ready for Release Nothing yet Discussion \u00b6","title":"January 9, 2024"},{"location":"meetings/2024/TechArea20240109/#osg-technology-area-meeting-9-january-2024","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 9 January 2024"},{"location":"meetings/2024/TechArea20240109/#announcements","text":"","title":"Announcements"},{"location":"meetings/2024/TechArea20240109/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2024/TechArea20240109/#jira-as-of-monday-morning","text":"# of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday morning)"},{"location":"meetings/2024/TechArea20240109/#osg-software-team","text":"Kubernetes hackathon: - AI (BrianL): clean up last Flux v1 Helm Charts, OSG 23 container image roundup - AI (Matt): xDD tasks? OSG institution frontend + OAuth2 - AI (Mat): new Yum repos on Tempest, auto-update EPs on the PATh Facility Release: - Frontier Squid + CarlV osg-build status? - AI (Matt): build VOMS for EL9 Miscellaneous: - AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files","title":"OSG Software Team"},{"location":"meetings/2024/TechArea20240109/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2024/TechArea20240109/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2024/TechArea20240109/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2024/TechArea20240109/#osg-release-team","text":"Ready for Testing Nothing yet Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2024/TechArea20240109/#discussion_1","text":"","title":"Discussion"},{"location":"operations/comanage/","text":"COManage Operations \u00b6 OSG is using a new identity management system called COManage. This system is used for managing contact information for OSPool and PATh Facility users, Topology site contacts, and OSG/PATh staff. Contact Registration \u00b6 Contact registrations must be manually approved by a COManage admin. Follow the instructions below to approve a contact registration. Note This page is for COManage Admins who want to approve contact registrations. If you are a user who wants to register with COManage, go to the Registering for the OSG COManage page instead. Check for contact registration requests: If you are a COManage sponsor for a given group of registrants, you will receive email notifications when there are new registration requests. Check for an email from registry@cilogon.org saying \"Petition for changed status from Confirmed to Pending Approval\" and visit the first link in the body. Alternatively, you can view all requests pending approval here . Click on the registrant's name to view their request. Note Many groups share our COManage instance so make sure that you're only approving registration requests for the appropriate group, e.g. site contacts. If prompted, log in with your institutional credentials. Review the request: Verify that the request is legitimate by doing at least one of the following: Find associated support tickets by searching for their email address in Freshdesk Ask someone affiliated with the site, collaboration, or the sponsor of a project to verify the registrant's affiliation. Ask if other staff have been in contact with them via the #staff Slack channel Verify that the registrant has submitted their request using the correct form, e.g. OSPool users should not have submitted a request to register as a Topology contact. In the top-right corner, click the \"Add comment\" link and add a note indicating how you verified the request 'Approver Comment' is public The registrant will see notes added to the \"Approver Comment\" field Click the \"Approve\" button. You should see \"Petition Approved\" and \"Petition Finalized\" on top. The Status should now be \"Finalized\". Click on their name next to CO Person to verify that the registrant is Active and that they are in the expected groups. The user will get an email saying \"Petition for changed status from Pending Approval to Approved\". Revoking AP login access \u00b6 Login access to AP1 (PATh Facility) and AP40 (OSPool) is controlled by membership to COManage groups. To revoke a user's login access to either of these APs, perform the following steps: Find the corresponding user in COManage and revoke access to all OSG services or just the relevant AP: If you are revoking access to all OSG services, set the user's CO Person status to Suspended If you only need to revoke access to AP1 or AP40, remove the user from the ap1-login or ap40-login group, respectively Note the OSG Username identifier of the user On the AP host(s) where you are revoking access, clear the SSSD cache as root: root@ap-host # sss_cache -u <OSG Username> Replacing <OSG Username> with the OSG Username identifier that you noted in step (2) Troubleshooting \u00b6 The COManage petition is stuck in the \"confirmed\" state \u00b6 This may happen if there are issues when confirming the user's email address. We have seen this occur if a user clicks the confirmation link then closes the tab too quickly. Under the People drop-down on the left, click on My Population Browse to the CO Person record. Scroll down to the Role Attributes , click the gear icon, select Edit , and set the status for the Role to Active . Verify that the overall status of the CO Person record is Active . If not, change it to Active as well. Click on Autogenerate Identifiers on the right, so that the necessary identifiers are created. Now that the necessary identifiers exist for the CO Person record, the LDAP DN can be computed and the record provisioned in LDAP. To make sure, click on Provisioned Services and then Provision .","title":"COManage"},{"location":"operations/comanage/#comanage-operations","text":"OSG is using a new identity management system called COManage. This system is used for managing contact information for OSPool and PATh Facility users, Topology site contacts, and OSG/PATh staff.","title":"COManage Operations"},{"location":"operations/comanage/#contact-registration","text":"Contact registrations must be manually approved by a COManage admin. Follow the instructions below to approve a contact registration. Note This page is for COManage Admins who want to approve contact registrations. If you are a user who wants to register with COManage, go to the Registering for the OSG COManage page instead. Check for contact registration requests: If you are a COManage sponsor for a given group of registrants, you will receive email notifications when there are new registration requests. Check for an email from registry@cilogon.org saying \"Petition for changed status from Confirmed to Pending Approval\" and visit the first link in the body. Alternatively, you can view all requests pending approval here . Click on the registrant's name to view their request. Note Many groups share our COManage instance so make sure that you're only approving registration requests for the appropriate group, e.g. site contacts. If prompted, log in with your institutional credentials. Review the request: Verify that the request is legitimate by doing at least one of the following: Find associated support tickets by searching for their email address in Freshdesk Ask someone affiliated with the site, collaboration, or the sponsor of a project to verify the registrant's affiliation. Ask if other staff have been in contact with them via the #staff Slack channel Verify that the registrant has submitted their request using the correct form, e.g. OSPool users should not have submitted a request to register as a Topology contact. In the top-right corner, click the \"Add comment\" link and add a note indicating how you verified the request 'Approver Comment' is public The registrant will see notes added to the \"Approver Comment\" field Click the \"Approve\" button. You should see \"Petition Approved\" and \"Petition Finalized\" on top. The Status should now be \"Finalized\". Click on their name next to CO Person to verify that the registrant is Active and that they are in the expected groups. The user will get an email saying \"Petition for changed status from Pending Approval to Approved\".","title":"Contact Registration"},{"location":"operations/comanage/#revoking-ap-login-access","text":"Login access to AP1 (PATh Facility) and AP40 (OSPool) is controlled by membership to COManage groups. To revoke a user's login access to either of these APs, perform the following steps: Find the corresponding user in COManage and revoke access to all OSG services or just the relevant AP: If you are revoking access to all OSG services, set the user's CO Person status to Suspended If you only need to revoke access to AP1 or AP40, remove the user from the ap1-login or ap40-login group, respectively Note the OSG Username identifier of the user On the AP host(s) where you are revoking access, clear the SSSD cache as root: root@ap-host # sss_cache -u <OSG Username> Replacing <OSG Username> with the OSG Username identifier that you noted in step (2)","title":"Revoking AP login access"},{"location":"operations/comanage/#troubleshooting","text":"","title":"Troubleshooting"},{"location":"operations/comanage/#the-comanage-petition-is-stuck-in-the-confirmed-state","text":"This may happen if there are issues when confirming the user's email address. We have seen this occur if a user clicks the confirmation link then closes the tab too quickly. Under the People drop-down on the left, click on My Population Browse to the CO Person record. Scroll down to the Role Attributes , click the gear icon, select Edit , and set the status for the Role to Active . Verify that the overall status of the CO Person record is Active . If not, change it to Active as well. Click on Autogenerate Identifiers on the right, so that the necessary identifiers are created. Now that the necessary identifiers exist for the CO Person record, the LDAP DN can be computed and the record provisioned in LDAP. To make sure, click on Provisioned Services and then Provision .","title":"The COManage petition is stuck in the \"confirmed\" state"},{"location":"policy/bestman2-retire/","text":"BeStMan2 Retirement \u00b6 This document provides an overview of the planned retirement of support for BeStMan in the OSG Software Stack. Introduction \u00b6 BeStMan2 is a standalone implementation of a subset of the Storage Resource Manager v2 (SRMv2) protocol. SRM was meant to be a high-level management protocol for site storage resources, allowing administrators to manage storage offerings using the abstraction of \"storage tokens.\" Additionally, SRM can be used to mediate transfer protocol selection. OSG currently supports BeStMan2 in \"gateway mode\" -- in this mode, SRM is only used for metadata operations (listing directory contents), listing total space used, and load-balancing GridFTP servers. This functionality is redundant to what can be accomplished with GridFTP alone. BeStMan2 has not received upstream support for approximately five years; the existing code base (about 150,000 lines of Java - similar in size to Globus GridFTP) and its extensive set of dependencies (such as JGlobus) are now quite outdated and would require significant investment to modernize. OSG has worked at length with our stakeholders to replace SRM-specific use cases with other equivalents. We believe none of our stakeholders require sites to have an SRM endpoint: this document describes the site transition plan. Site Transition Plans \u00b6 We have released documentation for a configuration of GridFTP that takes advantage of Linux Virtual Server (LVS) for load balancing between multiple GridFTP endpoints. Sites should work with their supported VOs (typically, CMS or ATLAS) to identify any VO-specific usage and replacement plans for BeStMan2. Timeline \u00b6 March 2017 (completed): Release load balanced GridFTP documentation June 2017 (completed): OSG 3.4.0 is released without BeStMan December 2018 (completed): Security-only support for OSG 3.3 series and BeStMan is provided May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for BeStMan is provided.","title":"BeStMan2 Retirement"},{"location":"policy/bestman2-retire/#bestman2-retirement","text":"This document provides an overview of the planned retirement of support for BeStMan in the OSG Software Stack.","title":"BeStMan2 Retirement"},{"location":"policy/bestman2-retire/#introduction","text":"BeStMan2 is a standalone implementation of a subset of the Storage Resource Manager v2 (SRMv2) protocol. SRM was meant to be a high-level management protocol for site storage resources, allowing administrators to manage storage offerings using the abstraction of \"storage tokens.\" Additionally, SRM can be used to mediate transfer protocol selection. OSG currently supports BeStMan2 in \"gateway mode\" -- in this mode, SRM is only used for metadata operations (listing directory contents), listing total space used, and load-balancing GridFTP servers. This functionality is redundant to what can be accomplished with GridFTP alone. BeStMan2 has not received upstream support for approximately five years; the existing code base (about 150,000 lines of Java - similar in size to Globus GridFTP) and its extensive set of dependencies (such as JGlobus) are now quite outdated and would require significant investment to modernize. OSG has worked at length with our stakeholders to replace SRM-specific use cases with other equivalents. We believe none of our stakeholders require sites to have an SRM endpoint: this document describes the site transition plan.","title":"Introduction"},{"location":"policy/bestman2-retire/#site-transition-plans","text":"We have released documentation for a configuration of GridFTP that takes advantage of Linux Virtual Server (LVS) for load balancing between multiple GridFTP endpoints. Sites should work with their supported VOs (typically, CMS or ATLAS) to identify any VO-specific usage and replacement plans for BeStMan2.","title":"Site Transition Plans"},{"location":"policy/bestman2-retire/#timeline","text":"March 2017 (completed): Release load balanced GridFTP documentation June 2017 (completed): OSG 3.4.0 is released without BeStMan December 2018 (completed): Security-only support for OSG 3.3 series and BeStMan is provided May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for BeStMan is provided.","title":"Timeline"},{"location":"policy/campus-cyberinfrastructure/","text":"The OSG and NSF Campus Cyberinfrastructure \u00b6 The NSF Campus Cyberinfrastructure (CC*) program invests in coordinated campus-level cyberinfrastructure improvements, innovation, integration, and engineering for science applications and distributed research projects, including enhancements to campus networking and computing resources. The Open Science Grid (as part of the Partnership to Advance Throughput Computing (PATh) ), is here to help you with your Campus Cyberinfrastructure (CC*) proposal! Please contact us at cc-star-proposals@osg-htc.org We have significant experience working with CC* applicants and awardees, offering letters of collaboration and consulting for: bringing the power of the OSG to YOUR researchers gathering science drivers and planning local computing resources CC*-required resource sharing for the Campus Compute category*, and other options for integrating local resources into OSG *In the most recent call for proposals ( NSF 21-528 ), joining the OSG is mentioned as a potential path to sharing resources with the wider research community: Proposals are required to commit to a minimum of 20% shared time on the cluster and describe their approach to making the cluster available as a shared resource external to the campus, [...] One possible approach to implementing such a federated distributed computing solution is joining a multi-campus or national federated system such as the Open Science Grid. Sharing Resources via the OSG \u00b6 The OSG consortium provides standard services and support for computational resource providers (i.e., \"sites\") using a distributed fabric of high throughput computating (HTC) technologies. These distributed-HTC (dHTC) services communicate with the site's local resource management (e.g. \"queueing\") systems to provision resources for OSG users. The OSG itself does not own resources, but provides software and services that enable the sharing of resources by many sites, and enable users to take advantage of these from submission points (whether via an OSG-operated submission point, like OSG Connect , or a locally-managed one). To contribute computational resources to the OSG, the following will be needed: An existing compute cluster running on a supported operating system with a supported resource management system: Grid Engine , HTCondor , LSF , PBS Pro / Torque , Slurm , and some local cloud provisioners. Outbound network connectivity from the cluster's worker nodes SSH access to your local cluster's submit node from a known IP address Temporary scratch space on each worker node and shared home directories on each cluster node Installation of some additional packages on the local cluster, IF the site would like to maximize its ability to support users, including those with large per-job data, containerized software, and/or GPU jobs. (There ARE some exceptions to the above. Contact us to discuss them!) Next steps If you are interested in OSG-offered services, please contact us for a consultation, even if your site does not meet all the conditions as outlined above! Additional Materials \u00b6 If you are interested in learning more about the dHTC, OSG, and what it means to share resources via OSG services, consider reviewing the following presentations from our October 2020 workshop on dHTC and OSG services for campuses ( YouTube Playlist ): Intro to dHTC and PATh Services for Campuses ( slides , YouTube ) How OSG Works ( slides , YouTube ) Intro to OSG Resource Sharing ( slides , YouTube ) Resource Sharing Technology, Security, System Requirements, Setup Process ( slides , YouTube )","title":"Campus Cyberinfrastructure"},{"location":"policy/campus-cyberinfrastructure/#the-osg-and-nsf-campus-cyberinfrastructure","text":"The NSF Campus Cyberinfrastructure (CC*) program invests in coordinated campus-level cyberinfrastructure improvements, innovation, integration, and engineering for science applications and distributed research projects, including enhancements to campus networking and computing resources. The Open Science Grid (as part of the Partnership to Advance Throughput Computing (PATh) ), is here to help you with your Campus Cyberinfrastructure (CC*) proposal! Please contact us at cc-star-proposals@osg-htc.org We have significant experience working with CC* applicants and awardees, offering letters of collaboration and consulting for: bringing the power of the OSG to YOUR researchers gathering science drivers and planning local computing resources CC*-required resource sharing for the Campus Compute category*, and other options for integrating local resources into OSG *In the most recent call for proposals ( NSF 21-528 ), joining the OSG is mentioned as a potential path to sharing resources with the wider research community: Proposals are required to commit to a minimum of 20% shared time on the cluster and describe their approach to making the cluster available as a shared resource external to the campus, [...] One possible approach to implementing such a federated distributed computing solution is joining a multi-campus or national federated system such as the Open Science Grid.","title":"The OSG and NSF Campus Cyberinfrastructure"},{"location":"policy/campus-cyberinfrastructure/#sharing-resources-via-the-osg","text":"The OSG consortium provides standard services and support for computational resource providers (i.e., \"sites\") using a distributed fabric of high throughput computating (HTC) technologies. These distributed-HTC (dHTC) services communicate with the site's local resource management (e.g. \"queueing\") systems to provision resources for OSG users. The OSG itself does not own resources, but provides software and services that enable the sharing of resources by many sites, and enable users to take advantage of these from submission points (whether via an OSG-operated submission point, like OSG Connect , or a locally-managed one). To contribute computational resources to the OSG, the following will be needed: An existing compute cluster running on a supported operating system with a supported resource management system: Grid Engine , HTCondor , LSF , PBS Pro / Torque , Slurm , and some local cloud provisioners. Outbound network connectivity from the cluster's worker nodes SSH access to your local cluster's submit node from a known IP address Temporary scratch space on each worker node and shared home directories on each cluster node Installation of some additional packages on the local cluster, IF the site would like to maximize its ability to support users, including those with large per-job data, containerized software, and/or GPU jobs. (There ARE some exceptions to the above. Contact us to discuss them!) Next steps If you are interested in OSG-offered services, please contact us for a consultation, even if your site does not meet all the conditions as outlined above!","title":"Sharing Resources via the OSG"},{"location":"policy/campus-cyberinfrastructure/#additional-materials","text":"If you are interested in learning more about the dHTC, OSG, and what it means to share resources via OSG services, consider reviewing the following presentations from our October 2020 workshop on dHTC and OSG services for campuses ( YouTube Playlist ): Intro to dHTC and PATh Services for Campuses ( slides , YouTube ) How OSG Works ( slides , YouTube ) Intro to OSG Resource Sharing ( slides , YouTube ) Resource Sharing Technology, Security, System Requirements, Setup Process ( slides , YouTube )","title":"Additional Materials"},{"location":"policy/collab-bearer-tokens/","text":"Collaborations and Bearer Tokens \u00b6 Sites in the OSG grant access to their grid services based on client's association with a specific collaboration (i.e. VO) instead of granting access on a per-user basis. In the past, this type of access was provided through X.509 proxies with VOMS attributes to demonstrate assocation with a collaboration: Users (both human and robots) would request that their collaboration sign their X.509 proxies (usually through a VOMS server), Or in the case of automated services (i.e. pilot job submission) a collaboration could directly create and sign proxies themselves Now, sites can authenticate and authorize clients presenting bearer tokens, such as SciTokens or WLCG tokens. This document describes how collaborations can issue bearer tokens for the aforementioned use cases in ways that are compatible with OSG sites. Issuers \u00b6 To generate bearer tokens, a collaboration must adminster at least one \"token issuer\" to issue tokens to their users. In addition to generating and signing tokens, token issuers provide a public endpoint that can be used to validate an issued token, e.g. an OSG Compute Entrypoint (CE) will contact the token issuer to authorize a bearer token used for pilot job submission. Token issuer uptime Due to the centralized nature of bearer token validation, token issuers should be treated as critical, highly available services. Otherwise, a token issuer outage will result in OSG sites being unable to authenticate a collaboration's tokens, meaning an interruption in pilot job submission and authenticated data transfers. Choose one of the token issuer types below, depending on the needs of your collaboration. Simple issuer \u00b6 If your collaboration centrally administers all services requiring bearer tokens and your users do not need to directly manage bearer tokens, consider running a simple token issuer. A simple token issuer consists of a public/private certificate keypair where the private key is used to issue tokens directly and the public certificate is made available through a web server. For example, the OSPool (n\u00e9e OSG VO) serves its public certificate through GitHub pages and uses the private key to sign tokens used for pilot job submission as well as automatically generating tokens to accompany user jobs so that they can access their private storage areas. OAuth2/OpenID Connect \u00b6 If your collaboration distributes administrative responsibility or your users need to request and manage their own tokens, you should administer an OAuth2/OpenID Connect (OIDC) service (e.g., INDIGO IAM ) or work with an existing OAuth2/OIDC provider (e.g., CILogon ). For example, Fermilab uses CILogon as their OIDC provider combined with an HTVault server used to streamline the OIDC process for users and integrate with their local Kerberos. Claims \u00b6 Bearer tokens are self-describing credentials that enumerate their capabilities as \"claims\" and different token \"profiles\" enumerate common sets of claims. OSG sites support the following bearer token profiles: SciTokens WLCG tokens Claims are further described below with recommendations to ensure the greatest compatibility with OSG sites. Scope \u00b6 The scope claim is a space-separated list of authorizations that should be granted to the bearer. Scopes utilized by OSG services include the following: Capability SciTokens scope WLCG scope HTCondor READ condor:/READ compute.read HTCondor WRITE condor:/WRITE compute.modify compute.cancel compute.create XRootD read read:<PATH> storage.read:<PATH> XRootD write write:<PATH> storage.modify:<PATH> Replacing <PATH> with a path to the storage location that the bearer should be authorized to access. Issuer \u00b6 The issuer URL, or the iss claim, indicates the endpoint to use for authenticating a given token. A collaboration may have more than one token issuer but a single token issuer should never serve more than one collaboration. In other words, given the token issuer, the site can determine the collaboration that issued the token. The following collaborations have registered token issuers with the OSG: Collaboration Issuers ATLAS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/ATLAS.yaml CLAS12 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CLAS12.yaml CMS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CMS.yaml DES https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DES.yaml DUNE https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DUNE.yaml EIC https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/EIC.yaml Fermilab https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Fermilab.yaml CHTC (n\u00e9e GLOW) https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/GLOW.yaml Gluex https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Gluex.yaml IceCube https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/IceCube.yaml LIGO https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/LIGO.yaml Mu2e https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Mu2e.yaml OSPool https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/OSG.yaml SBND https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/SBND.yaml gm2 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/gm2.yaml The OSG distributes the osg-scitokens-mapfile RPM package that includes issuer and subject to default user mappings for use by OSG CEs. Subject \u00b6 Subjects (i.e., the sub claim) should be unique, stable identifiers that correspond to a user or service (e.g. pilot job submission). In other words, subjects combined with a token issuer can be used for suspending access for a given collaboration user, user-level accounting, monitoring, auditing, or tracing. In tandem with a token issuer URL (i.e., the iss claim), subjects can be used by site HTCondor-CE or XRootD services to map to a local identity. Privacy considerations Depending on your collaboration's userbase and contributing sites, you may have to take privacy concerns, such as the GDPR into account when assigning subjects to users. Thus, it may be preferable to assign users a randomly-generated string as their sub . Audience \u00b6 To take advantage of the improved security posture of bearer tokens, we recommend that the aud claim be set to the intended host. For example, tokens used for submission to an HTCondor-CE should set the following: aud = <CE FQDN>:<CE PORT> WLCG groups \u00b6 WLCG tokens may have the wlcg.groups claim consisting of a comma and space separated list of collaboration groups. The format of these groups are similar to VOMS FQANs: /<collaboration>[/<group>][/Role=<role>] , replacing <collaboration> , <group> , and <role> with the collaboration, group, and role, respectively, where the group and role are optional. For example, the following groups and roles have been used by the ATLAS and CMS collaborations: /atlas/ /atlas/usatlas /cms/Role=pilot /cms/local/Role=pilot Traditionally, sites have made local accounting and scheduling decisions based on the first VOMS FQAN so collaborations should set the first group/role in wlcg.groups to the most specific group or role. For example: wlcg.groups = /cms/Role=pilot, /cms Instead of: wlcg.groups = /cms, /cms/Role=pilot Help \u00b6 To get assistance, please use the this page .","title":"Collaborations and Bearer Tokens"},{"location":"policy/collab-bearer-tokens/#collaborations-and-bearer-tokens","text":"Sites in the OSG grant access to their grid services based on client's association with a specific collaboration (i.e. VO) instead of granting access on a per-user basis. In the past, this type of access was provided through X.509 proxies with VOMS attributes to demonstrate assocation with a collaboration: Users (both human and robots) would request that their collaboration sign their X.509 proxies (usually through a VOMS server), Or in the case of automated services (i.e. pilot job submission) a collaboration could directly create and sign proxies themselves Now, sites can authenticate and authorize clients presenting bearer tokens, such as SciTokens or WLCG tokens. This document describes how collaborations can issue bearer tokens for the aforementioned use cases in ways that are compatible with OSG sites.","title":"Collaborations and Bearer Tokens"},{"location":"policy/collab-bearer-tokens/#issuers","text":"To generate bearer tokens, a collaboration must adminster at least one \"token issuer\" to issue tokens to their users. In addition to generating and signing tokens, token issuers provide a public endpoint that can be used to validate an issued token, e.g. an OSG Compute Entrypoint (CE) will contact the token issuer to authorize a bearer token used for pilot job submission. Token issuer uptime Due to the centralized nature of bearer token validation, token issuers should be treated as critical, highly available services. Otherwise, a token issuer outage will result in OSG sites being unable to authenticate a collaboration's tokens, meaning an interruption in pilot job submission and authenticated data transfers. Choose one of the token issuer types below, depending on the needs of your collaboration.","title":"Issuers"},{"location":"policy/collab-bearer-tokens/#simple-issuer","text":"If your collaboration centrally administers all services requiring bearer tokens and your users do not need to directly manage bearer tokens, consider running a simple token issuer. A simple token issuer consists of a public/private certificate keypair where the private key is used to issue tokens directly and the public certificate is made available through a web server. For example, the OSPool (n\u00e9e OSG VO) serves its public certificate through GitHub pages and uses the private key to sign tokens used for pilot job submission as well as automatically generating tokens to accompany user jobs so that they can access their private storage areas.","title":"Simple issuer"},{"location":"policy/collab-bearer-tokens/#oauth2openid-connect","text":"If your collaboration distributes administrative responsibility or your users need to request and manage their own tokens, you should administer an OAuth2/OpenID Connect (OIDC) service (e.g., INDIGO IAM ) or work with an existing OAuth2/OIDC provider (e.g., CILogon ). For example, Fermilab uses CILogon as their OIDC provider combined with an HTVault server used to streamline the OIDC process for users and integrate with their local Kerberos.","title":"OAuth2/OpenID Connect"},{"location":"policy/collab-bearer-tokens/#claims","text":"Bearer tokens are self-describing credentials that enumerate their capabilities as \"claims\" and different token \"profiles\" enumerate common sets of claims. OSG sites support the following bearer token profiles: SciTokens WLCG tokens Claims are further described below with recommendations to ensure the greatest compatibility with OSG sites.","title":"Claims"},{"location":"policy/collab-bearer-tokens/#scope","text":"The scope claim is a space-separated list of authorizations that should be granted to the bearer. Scopes utilized by OSG services include the following: Capability SciTokens scope WLCG scope HTCondor READ condor:/READ compute.read HTCondor WRITE condor:/WRITE compute.modify compute.cancel compute.create XRootD read read:<PATH> storage.read:<PATH> XRootD write write:<PATH> storage.modify:<PATH> Replacing <PATH> with a path to the storage location that the bearer should be authorized to access.","title":"Scope"},{"location":"policy/collab-bearer-tokens/#issuer","text":"The issuer URL, or the iss claim, indicates the endpoint to use for authenticating a given token. A collaboration may have more than one token issuer but a single token issuer should never serve more than one collaboration. In other words, given the token issuer, the site can determine the collaboration that issued the token. The following collaborations have registered token issuers with the OSG: Collaboration Issuers ATLAS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/ATLAS.yaml CLAS12 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CLAS12.yaml CMS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CMS.yaml DES https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DES.yaml DUNE https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DUNE.yaml EIC https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/EIC.yaml Fermilab https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Fermilab.yaml CHTC (n\u00e9e GLOW) https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/GLOW.yaml Gluex https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Gluex.yaml IceCube https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/IceCube.yaml LIGO https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/LIGO.yaml Mu2e https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Mu2e.yaml OSPool https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/OSG.yaml SBND https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/SBND.yaml gm2 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/gm2.yaml The OSG distributes the osg-scitokens-mapfile RPM package that includes issuer and subject to default user mappings for use by OSG CEs.","title":"Issuer"},{"location":"policy/collab-bearer-tokens/#subject","text":"Subjects (i.e., the sub claim) should be unique, stable identifiers that correspond to a user or service (e.g. pilot job submission). In other words, subjects combined with a token issuer can be used for suspending access for a given collaboration user, user-level accounting, monitoring, auditing, or tracing. In tandem with a token issuer URL (i.e., the iss claim), subjects can be used by site HTCondor-CE or XRootD services to map to a local identity. Privacy considerations Depending on your collaboration's userbase and contributing sites, you may have to take privacy concerns, such as the GDPR into account when assigning subjects to users. Thus, it may be preferable to assign users a randomly-generated string as their sub .","title":"Subject"},{"location":"policy/collab-bearer-tokens/#audience","text":"To take advantage of the improved security posture of bearer tokens, we recommend that the aud claim be set to the intended host. For example, tokens used for submission to an HTCondor-CE should set the following: aud = <CE FQDN>:<CE PORT>","title":"Audience"},{"location":"policy/collab-bearer-tokens/#wlcg-groups","text":"WLCG tokens may have the wlcg.groups claim consisting of a comma and space separated list of collaboration groups. The format of these groups are similar to VOMS FQANs: /<collaboration>[/<group>][/Role=<role>] , replacing <collaboration> , <group> , and <role> with the collaboration, group, and role, respectively, where the group and role are optional. For example, the following groups and roles have been used by the ATLAS and CMS collaborations: /atlas/ /atlas/usatlas /cms/Role=pilot /cms/local/Role=pilot Traditionally, sites have made local accounting and scheduling decisions based on the first VOMS FQAN so collaborations should set the first group/role in wlcg.groups to the most specific group or role. For example: wlcg.groups = /cms/Role=pilot, /cms Instead of: wlcg.groups = /cms, /cms/Role=pilot","title":"WLCG groups"},{"location":"policy/collab-bearer-tokens/#help","text":"To get assistance, please use the this page .","title":"Help"},{"location":"policy/community-testing/","text":"OSG Community Software Testing \u00b6 8 October 2019 The community of OSG resource providers has a vested interest in the quality and stability of the OSG software stack. We would like to notify our stakeholders of software updates as soon as they are designated as \"Ready for Testing\" by the Software Team. Direct engagement with the entire community would allow for feedback from a broader array of interested parties. Combined with our flexible release model , we hope to further improve the turnaround time of new features and bug fixes. Implementation \u00b6 After the OSG Software Team builds and tests a package successfully, it is marked \"Ready for Testing\" and is added to the appropriate Yum testing repository: osg-testing and osg-upcoming-testing for packages targeted for the release and the upcoming release, respectively. Upon addition to the relevant testing repository, we intend to notify OSG site administrators that the package, or a logically connected group of packages, is available for testing with a description of changes compared to previously released versions and provide a forum by which interested users can provide feedback. Additionally, any packages that are considered release candidates by their upstream authors will be noted as such. The Software and Release team will classify packages as either \"major\" or \"minor\"; where major packages are deemed critical to the functionality of the production grid and all other packages are minor. For major packages, we will notify site administrators as soon as they are eligible for testing; minor packages eligible for testing will be collected and announced in a weekly digest. After users have been notified of changes, minor packages will be marked eligible for release if they have not received negative feedback after 7 calendar days. In addition to the above requirements, major packages must also receive positive feedback and be approved by the Release Manager. If a major package has not received feedback after four weeks and it has been sufficiently tested by OSG integration tests, the Release Manager may approve the package for release. If a package receives negative feedback, the offending package will be removed from the relevant testing repository. Major Packages \u00b6 The following packages are considered critical to the production Open Science Grid: CVMFS Frontier Squid GlideinWMS Gratia Probes HTCondor HTCondor-CE stashcp XCache XRootD This list is maintained by the Release Manager with input from OSG stakeholders, the Software Manager, and the Operations Manager. Exceptions \u00b6 If an expedient release is required, the OSG Software Team may forego the community testing policy outlined above. Common exceptions to the policy include releases that contain one or more of the following: Security updates CA or VO data updates Updates that address installation or upgrade issues Version History \u00b6 2022-10-07 : All promoting of lanquishing critical packages when adequately covered by automated tests 2022-05-06 : Drop unsupported software from the critical package list 2019-10-08 : Add policy exceptions 2019-08-12 : Add notification frequency details 2019-02-20 : Initial policy","title":"Community Testing"},{"location":"policy/community-testing/#osg-community-software-testing","text":"8 October 2019 The community of OSG resource providers has a vested interest in the quality and stability of the OSG software stack. We would like to notify our stakeholders of software updates as soon as they are designated as \"Ready for Testing\" by the Software Team. Direct engagement with the entire community would allow for feedback from a broader array of interested parties. Combined with our flexible release model , we hope to further improve the turnaround time of new features and bug fixes.","title":"OSG Community Software Testing"},{"location":"policy/community-testing/#implementation","text":"After the OSG Software Team builds and tests a package successfully, it is marked \"Ready for Testing\" and is added to the appropriate Yum testing repository: osg-testing and osg-upcoming-testing for packages targeted for the release and the upcoming release, respectively. Upon addition to the relevant testing repository, we intend to notify OSG site administrators that the package, or a logically connected group of packages, is available for testing with a description of changes compared to previously released versions and provide a forum by which interested users can provide feedback. Additionally, any packages that are considered release candidates by their upstream authors will be noted as such. The Software and Release team will classify packages as either \"major\" or \"minor\"; where major packages are deemed critical to the functionality of the production grid and all other packages are minor. For major packages, we will notify site administrators as soon as they are eligible for testing; minor packages eligible for testing will be collected and announced in a weekly digest. After users have been notified of changes, minor packages will be marked eligible for release if they have not received negative feedback after 7 calendar days. In addition to the above requirements, major packages must also receive positive feedback and be approved by the Release Manager. If a major package has not received feedback after four weeks and it has been sufficiently tested by OSG integration tests, the Release Manager may approve the package for release. If a package receives negative feedback, the offending package will be removed from the relevant testing repository.","title":"Implementation"},{"location":"policy/community-testing/#major-packages","text":"The following packages are considered critical to the production Open Science Grid: CVMFS Frontier Squid GlideinWMS Gratia Probes HTCondor HTCondor-CE stashcp XCache XRootD This list is maintained by the Release Manager with input from OSG stakeholders, the Software Manager, and the Operations Manager.","title":"Major Packages"},{"location":"policy/community-testing/#exceptions","text":"If an expedient release is required, the OSG Software Team may forego the community testing policy outlined above. Common exceptions to the policy include releases that contain one or more of the following: Security updates CA or VO data updates Updates that address installation or upgrade issues","title":"Exceptions"},{"location":"policy/community-testing/#version-history","text":"2022-10-07 : All promoting of lanquishing critical packages when adequately covered by automated tests 2022-05-06 : Drop unsupported software from the critical package list 2019-10-08 : Add policy exceptions 2019-08-12 : Add notification frequency details 2019-02-20 : Initial policy","title":"Version History"},{"location":"policy/container-release/","text":"Container Release Policy \u00b6 16 February 2022 Container images are an increasingly popular tool for shortening the software development life cycle, allowing for speedy deployment of new software versions or additional instances of a service. Select services in the OSG Software Stack will be distributed as container images to support VOs and sites that are interested in this model. This document contains policy information for container images distributed by the OSG Software Team. Contents and Sources \u00b6 Similar to our existing RPM infrastructure, container image sources, build logs, and artifacts will be stored in publicly available repositories (e.g. GitHub, Docker Hub) for collaboration and traceability. Additionally, container images distributed by the OSG Software team will be based off of the latest version of a supported platform with software installed from OS, EPEL, and OSG Yum repositories. Tags \u00b6 OSG Software container images will be built at least weekly and tagged with the following format: <SERIES>-<REPO>[-<TIME>] Field Description <SERIES> The OSG release series used for software installation. Possible values: 3.6 and 3.5 . <REPO> OSG Yum repositories used for software installation, including the corresponding upcoming repository. Possible values: release and testing . <TIME> The time that the image was built, in the format YYYYMMDD-HHMM; see below for an example. OSG Software Release Series life cycle Container images based on unsupported OSG release series will stop receiving regular updates. Immutable vs mutable tags Image tags without a build time are treated as mutable, i.e. these tags are regularly updated with the latest available software in their respective Yum repositories. Image tags with a build time are treated as immutable and do not change. For example, to deploy an Open Science Data Federation cache with the latest production software versions from OSG 3.6, use the following image tag: opensciencegrid/stash-cache:3.6-release However, to deploy a cache with software that was available in the osg-testing and osg-upcoming-testing repositories at 3:17 PM on December 17, 2021, use the following image tag: opensciencegrid/stash-cache:3.6-testing-20211217-1517 Deprecated \u00b6 Images based off of OSG 3.5 originally did not have the release series prefix. The following tags will no longer be supported after the retirement of OSG 3.5 on May 1, 2022: release-<TIME> release testing-<TIME> testing Where <TIME> is the time that the tag was built. See this page for more details on release series support. Retention \u00b6 Image tags older than 6 months will be automatically removed. Additionally, the Software Team may remove images with detected security flaws. Validation \u00b6 OSG Software container images consist of RPMs for OSG services that are tested through existing release processes as well as scripts and configuration specific to the container implementation of the service. New container images limited to RPM updates undergo additional automated testing before being published. In order to test changes to container-specific scripts or configuration, OSG Software performs automated tests and coordinates testing of release candidate images before applying these changes to the production tags . Change Log \u00b6 21 April 2022: Deprecate tags without the OSG release series 16 February 2022: Remove Docker Hub dependency from the retention policy. 22 January 2021: Modify the tagging policy to more closely track OSG Yum repositories 14 August 2020: Updated cleanup policy to match Docker Hub image retention policy. 17 April 2019: Initial policy","title":"Container Release Policy"},{"location":"policy/container-release/#container-release-policy","text":"16 February 2022 Container images are an increasingly popular tool for shortening the software development life cycle, allowing for speedy deployment of new software versions or additional instances of a service. Select services in the OSG Software Stack will be distributed as container images to support VOs and sites that are interested in this model. This document contains policy information for container images distributed by the OSG Software Team.","title":"Container Release Policy"},{"location":"policy/container-release/#contents-and-sources","text":"Similar to our existing RPM infrastructure, container image sources, build logs, and artifacts will be stored in publicly available repositories (e.g. GitHub, Docker Hub) for collaboration and traceability. Additionally, container images distributed by the OSG Software team will be based off of the latest version of a supported platform with software installed from OS, EPEL, and OSG Yum repositories.","title":"Contents and Sources"},{"location":"policy/container-release/#tags","text":"OSG Software container images will be built at least weekly and tagged with the following format: <SERIES>-<REPO>[-<TIME>] Field Description <SERIES> The OSG release series used for software installation. Possible values: 3.6 and 3.5 . <REPO> OSG Yum repositories used for software installation, including the corresponding upcoming repository. Possible values: release and testing . <TIME> The time that the image was built, in the format YYYYMMDD-HHMM; see below for an example. OSG Software Release Series life cycle Container images based on unsupported OSG release series will stop receiving regular updates. Immutable vs mutable tags Image tags without a build time are treated as mutable, i.e. these tags are regularly updated with the latest available software in their respective Yum repositories. Image tags with a build time are treated as immutable and do not change. For example, to deploy an Open Science Data Federation cache with the latest production software versions from OSG 3.6, use the following image tag: opensciencegrid/stash-cache:3.6-release However, to deploy a cache with software that was available in the osg-testing and osg-upcoming-testing repositories at 3:17 PM on December 17, 2021, use the following image tag: opensciencegrid/stash-cache:3.6-testing-20211217-1517","title":"Tags"},{"location":"policy/container-release/#deprecated","text":"Images based off of OSG 3.5 originally did not have the release series prefix. The following tags will no longer be supported after the retirement of OSG 3.5 on May 1, 2022: release-<TIME> release testing-<TIME> testing Where <TIME> is the time that the tag was built. See this page for more details on release series support.","title":"Deprecated"},{"location":"policy/container-release/#retention","text":"Image tags older than 6 months will be automatically removed. Additionally, the Software Team may remove images with detected security flaws.","title":"Retention"},{"location":"policy/container-release/#validation","text":"OSG Software container images consist of RPMs for OSG services that are tested through existing release processes as well as scripts and configuration specific to the container implementation of the service. New container images limited to RPM updates undergo additional automated testing before being published. In order to test changes to container-specific scripts or configuration, OSG Software performs automated tests and coordinates testing of release candidate images before applying these changes to the production tags .","title":"Validation"},{"location":"policy/container-release/#change-log","text":"21 April 2022: Deprecate tags without the OSG release series 16 February 2022: Remove Docker Hub dependency from the retention policy. 22 January 2021: Modify the tagging policy to more closely track OSG Yum repositories 14 August 2020: Updated cleanup policy to match Docker Hub image retention policy. 17 April 2019: Initial policy","title":"Change Log"},{"location":"policy/cream-support/","text":"OSG/HTCondor CREAM-CE Support \u00b6 The CREAM working group has recently announced official support for the CREAM-CE will cease in December 2020. With this email, we are soliciting feedback on OSG and HTCondor\u2019s transition plan. OSG and HTCondor remain committed to supporting VOs who need to access to CREAM-CE based resources throughout the transition period; we will continue to support submission to CREAM-CE endpoints and offer assistance to VOs to manage the transition. OSG runs a glidein submission service that submits to grid infrastructures worldwide on behalf of dozens of science projects. This service currently submits to approximately 100 CREAM-CE endpoints; we will continue to maintain the capability to access these endpoints while we assist sites in testing and enabling ARC-CE and/or HTCondor-CE replacement services. The HTCondor team plans to support the CREAM-CE on EL6/7 in the 8.8.x stable release series and will maintain support for 8.8.x through December 2020. CREAM-CE support will remain enabled at the start of the 8.9.x developer series; in early 2020, the HTCondor team will re-evaluate, based on community need, whether CREAM-CE support will be available in the next stable series. We realize that software retirements can be very disruptive; the OSG and HTCondor teams are committed to assisting user communities through the process. If you believe our plan does not fit the needs of your user community, please contact help@osg-htc.org . Regards, Brian Bockelman, OSG Technology Area Coordinator Todd Tannenbaum, HTCondor Technical Lead Reference \u00b6 EGI broadcast about CREAM retirement ; the EGI link requires authentication; statement has been reproduced below: Dear Users The CREAM working group has announced that official support for the CREAM-CE component will cease at the end of the EOSC-hub project, i.e. in Dec 2020. To prepare for this, EGI Foundation and CERN are actively working to help to minimise disruption. This will include helping users migrate to alternative solutions, i.e. ARC-CE or HTCondor-CE. The CREAM working group will be providing full support until the end of 2019, including one minor release already scheduled. During 2020 only security updates will be released. If you have any concerns or queries, please open a support ticket at https://ggus.eu/ Best regards EGI Foundation and CERN Operations Teams","title":"CREAM-CE Support"},{"location":"policy/cream-support/#osghtcondor-cream-ce-support","text":"The CREAM working group has recently announced official support for the CREAM-CE will cease in December 2020. With this email, we are soliciting feedback on OSG and HTCondor\u2019s transition plan. OSG and HTCondor remain committed to supporting VOs who need to access to CREAM-CE based resources throughout the transition period; we will continue to support submission to CREAM-CE endpoints and offer assistance to VOs to manage the transition. OSG runs a glidein submission service that submits to grid infrastructures worldwide on behalf of dozens of science projects. This service currently submits to approximately 100 CREAM-CE endpoints; we will continue to maintain the capability to access these endpoints while we assist sites in testing and enabling ARC-CE and/or HTCondor-CE replacement services. The HTCondor team plans to support the CREAM-CE on EL6/7 in the 8.8.x stable release series and will maintain support for 8.8.x through December 2020. CREAM-CE support will remain enabled at the start of the 8.9.x developer series; in early 2020, the HTCondor team will re-evaluate, based on community need, whether CREAM-CE support will be available in the next stable series. We realize that software retirements can be very disruptive; the OSG and HTCondor teams are committed to assisting user communities through the process. If you believe our plan does not fit the needs of your user community, please contact help@osg-htc.org . Regards, Brian Bockelman, OSG Technology Area Coordinator Todd Tannenbaum, HTCondor Technical Lead","title":"OSG/HTCondor CREAM-CE Support"},{"location":"policy/cream-support/#reference","text":"EGI broadcast about CREAM retirement ; the EGI link requires authentication; statement has been reproduced below: Dear Users The CREAM working group has announced that official support for the CREAM-CE component will cease at the end of the EOSC-hub project, i.e. in Dec 2020. To prepare for this, EGI Foundation and CERN are actively working to help to minimise disruption. This will include helping users migrate to alternative solutions, i.e. ARC-CE or HTCondor-CE. The CREAM working group will be providing full support until the end of 2019, including one minor release already scheduled. During 2020 only security updates will be released. If you have any concerns or queries, please open a support ticket at https://ggus.eu/ Best regards EGI Foundation and CERN Operations Teams","title":"Reference"},{"location":"policy/external-oasis-repos/","text":"Policy for OSG Mirroring of External CVMFS repositories \u00b6 12 October 2017 This document provides an overview of the policies and security understanding with regards to OSG mirroring of CVMFS repositories of external organizations. It aims to help external repositories and OSG VOs understand what OSG is attempting to achieve with the mirroring service. This is not a service-level agreement but rather a statement of responsibilities. Note To actually understand the technical procedure for mirroring a repository, see the following page . This document solely covers the policy aspects. Introduction \u00b6 The OSG provides a network of CVMFS Stratum-1 servers for mirroring content of externally-managed repositories. These repositories are often hosted by large HEP or physics VOs for the purpose of distributing software for high-throughput computing jobs. Additionally, OSG provides a repository ( ) for smaller VOs; this is not covered here. OSG will include additional repositories into the content distribution network (CDN) at the request of an OSG-affiliated VO. These repositories are meant to help the OSG-affiliated VO accomplish their domain science. The goal of this mirroring provides an improved quality-of-service for the VO end-users running at OSG sites. OSG does not provide support for use of the software in external repositories, but will help end-users contact the VO for help as necessary. OSG Responsibilities \u00b6 OSG will provide the Stratum-1 server network according to the OASIS SLA OSG will provide a best-effort mirror of the full contents of the external repo. We will attempt to provide best-effort integrity of the object contents, but assume users of the Stratum-1 will do further integrity checking. No SLA is provided covering potential data corruptions. OSG will provide best-effort notification to the mirrored repository in case OSG detects a service outage of the external repo. In the event of a security incident, the operations group will replace the compromised repository with an empty directory, signed by the key managed by them. This will be done in consultation with the security team or, in the unlikely event they cannot be reached, at the discretion of the Operations Coordinator. Once the external repository is approved, OSG will distribute the corresponding repository signing keys in a valid whitelist. The whitelist will be signed by the OSG Stratum-0. This whitelist attests to the authenticity of the key, but not a statement about repository contents. VO Responsibilities \u00b6 The individual responsible on behalf of the VO will be registered with the OASIS Manager role in OIM. The requesting VO should only include targeted repositories they need to support their science. The VO should understand that in the event of a reported security incident, the contents of this repository may be replaced with an empty directory and signed by the OSG repository key. Depending on the OSG Security team's evaluation of the severity and urgency of the incident, the blanking may be done immediately without VO notification or after some notification period. In the case of a security incident, the VO and OSG Security team will need to mutually agree that the incident is resolved before the repository is unblanked. The VO is ultimately responsible for the contents of the repository. OSG provides a mirror. If the external repository is not operated by the VO, OSG may work directly with the external repository maintainers. This is done for ease of operations and may be limited to day-to-day, non-security-related support. Operational Policies \u00b6 To help us provide the best operational setup possible, we have a few additional replication policies: OSG Operations only hosts the shared oasis.opensciencegrid.org repository; VO-dedicated software respositories (such as nova.opensciencegrid.org for the NoVA VO) should be operated by the VO. VOs are asked to either run their own repository or utilize the shared repository, but not both. There is a finite amount of high-performance storage on the CDN. A minimum of 100 GB per repository is guaranteed. Larger limits may be requested. VOs may ask the OSG to replicate their repositories to the European Grid Infrastructure (EGI); however, this can only be done if the repository name ends in .opensciencegrid.org .","title":"OASIS Repository Mirroring"},{"location":"policy/external-oasis-repos/#policy-for-osg-mirroring-of-external-cvmfs-repositories","text":"12 October 2017 This document provides an overview of the policies and security understanding with regards to OSG mirroring of CVMFS repositories of external organizations. It aims to help external repositories and OSG VOs understand what OSG is attempting to achieve with the mirroring service. This is not a service-level agreement but rather a statement of responsibilities. Note To actually understand the technical procedure for mirroring a repository, see the following page . This document solely covers the policy aspects.","title":"Policy for OSG Mirroring of External CVMFS repositories"},{"location":"policy/external-oasis-repos/#introduction","text":"The OSG provides a network of CVMFS Stratum-1 servers for mirroring content of externally-managed repositories. These repositories are often hosted by large HEP or physics VOs for the purpose of distributing software for high-throughput computing jobs. Additionally, OSG provides a repository ( ) for smaller VOs; this is not covered here. OSG will include additional repositories into the content distribution network (CDN) at the request of an OSG-affiliated VO. These repositories are meant to help the OSG-affiliated VO accomplish their domain science. The goal of this mirroring provides an improved quality-of-service for the VO end-users running at OSG sites. OSG does not provide support for use of the software in external repositories, but will help end-users contact the VO for help as necessary.","title":"Introduction"},{"location":"policy/external-oasis-repos/#osg-responsibilities","text":"OSG will provide the Stratum-1 server network according to the OASIS SLA OSG will provide a best-effort mirror of the full contents of the external repo. We will attempt to provide best-effort integrity of the object contents, but assume users of the Stratum-1 will do further integrity checking. No SLA is provided covering potential data corruptions. OSG will provide best-effort notification to the mirrored repository in case OSG detects a service outage of the external repo. In the event of a security incident, the operations group will replace the compromised repository with an empty directory, signed by the key managed by them. This will be done in consultation with the security team or, in the unlikely event they cannot be reached, at the discretion of the Operations Coordinator. Once the external repository is approved, OSG will distribute the corresponding repository signing keys in a valid whitelist. The whitelist will be signed by the OSG Stratum-0. This whitelist attests to the authenticity of the key, but not a statement about repository contents.","title":"OSG Responsibilities"},{"location":"policy/external-oasis-repos/#vo-responsibilities","text":"The individual responsible on behalf of the VO will be registered with the OASIS Manager role in OIM. The requesting VO should only include targeted repositories they need to support their science. The VO should understand that in the event of a reported security incident, the contents of this repository may be replaced with an empty directory and signed by the OSG repository key. Depending on the OSG Security team's evaluation of the severity and urgency of the incident, the blanking may be done immediately without VO notification or after some notification period. In the case of a security incident, the VO and OSG Security team will need to mutually agree that the incident is resolved before the repository is unblanked. The VO is ultimately responsible for the contents of the repository. OSG provides a mirror. If the external repository is not operated by the VO, OSG may work directly with the external repository maintainers. This is done for ease of operations and may be limited to day-to-day, non-security-related support.","title":"VO Responsibilities"},{"location":"policy/external-oasis-repos/#operational-policies","text":"To help us provide the best operational setup possible, we have a few additional replication policies: OSG Operations only hosts the shared oasis.opensciencegrid.org repository; VO-dedicated software respositories (such as nova.opensciencegrid.org for the NoVA VO) should be operated by the VO. VOs are asked to either run their own repository or utilize the shared repository, but not both. There is a finite amount of high-performance storage on the CDN. A minimum of 100 GB per repository is guaranteed. Larger limits may be requested. VOs may ask the OSG to replicate their repositories to the European Grid Infrastructure (EGI); however, this can only be done if the repository name ends in .opensciencegrid.org .","title":"Operational Policies"},{"location":"policy/flexible-release-model/","text":"OSG Software Flexible Release Model \u00b6 Introduction \u00b6 Before November 2017, the OSG software stack was released on the second Tuesday of each month, except in the case of urgent releases, which were infrequent. This schedule had been in place since early 2013. Since then, conditions within and outside of the Software team have changed, and we have adjusted the release schedule and associated processes. The previous release model had the recurring problem of a \"release crunch,\" where it was difficult to find the effort required to test large changes before their deadline had passed. Sometimes the lack of timely effort led to software being pushed to the next release (a month later), because there was insufficient testing time. Based on software support tickets, we noticed that many sites follow a local update schedule that is independent of the OSG Release team schedule; some sites upgrade every few months, skipping interim releases, other sites upgrade individual packages as needed. In addition, upstream software developers do not follow our release schedule either, releasing software on their own development timelines. As a result, some site administrators would prefer to have OSG software updates more often, closer to when they become available, rather than tied to a monthly cycle. For these reasons, we created a new release model. Release Model \u00b6 The OSG Release team releases batches of integrated, tested software on an ad hoc basis, with the process outlined below (changes from the old process are highlighted): Software and Release Team members develop packages and mark them for testing Software and Release Team members test the packages, possibly with help from the community Once adequate testing is complete and successful, the Release Manager approves packages for release Weekly, the Release Manager evaluates packages that are ready for release; when a sufficient number of important packages are ready [1] , the Release Manager schedules a release date and announces it. For urgent changes, the Release Manager evaluates the packages as soon as they are tested The Software and Release Team performs pre-release testing, releases the packages, and announces the release Note: The release dates of parallel release series (e.g., 3.3 and 3.4) do not have to coincide, as they have in the past. [1] The threshold for \u201csufficient number of important packages\u201d is determined by the Release Manager, with input from the other Technology Area leaders.","title":"Flexible Release Model"},{"location":"policy/flexible-release-model/#osg-software-flexible-release-model","text":"","title":"OSG Software Flexible Release Model"},{"location":"policy/flexible-release-model/#introduction","text":"Before November 2017, the OSG software stack was released on the second Tuesday of each month, except in the case of urgent releases, which were infrequent. This schedule had been in place since early 2013. Since then, conditions within and outside of the Software team have changed, and we have adjusted the release schedule and associated processes. The previous release model had the recurring problem of a \"release crunch,\" where it was difficult to find the effort required to test large changes before their deadline had passed. Sometimes the lack of timely effort led to software being pushed to the next release (a month later), because there was insufficient testing time. Based on software support tickets, we noticed that many sites follow a local update schedule that is independent of the OSG Release team schedule; some sites upgrade every few months, skipping interim releases, other sites upgrade individual packages as needed. In addition, upstream software developers do not follow our release schedule either, releasing software on their own development timelines. As a result, some site administrators would prefer to have OSG software updates more often, closer to when they become available, rather than tied to a monthly cycle. For these reasons, we created a new release model.","title":"Introduction"},{"location":"policy/flexible-release-model/#release-model","text":"The OSG Release team releases batches of integrated, tested software on an ad hoc basis, with the process outlined below (changes from the old process are highlighted): Software and Release Team members develop packages and mark them for testing Software and Release Team members test the packages, possibly with help from the community Once adequate testing is complete and successful, the Release Manager approves packages for release Weekly, the Release Manager evaluates packages that are ready for release; when a sufficient number of important packages are ready [1] , the Release Manager schedules a release date and announces it. For urgent changes, the Release Manager evaluates the packages as soon as they are tested The Software and Release Team performs pre-release testing, releases the packages, and announces the release Note: The release dates of parallel release series (e.g., 3.3 and 3.4) do not have to coincide, as they have in the past. [1] The threshold for \u201csufficient number of important packages\u201d is determined by the Release Manager, with input from the other Technology Area leaders.","title":"Release Model"},{"location":"policy/globus-toolkit/","text":"OSG Support of the Globus Toolkit \u00b6 Gridftp and GSI Migration Plan In December 2019, the OSG developed a plan for migrating the OSG Software stack away from GridFTP and GSI that can be found here . 6 June 2017 Many in the OSG community have heard the news about the end of support for the open-source Globus Toolkit (formerly available from https://github.com/globus/globus-toolkit/blob/globus_6_branch/support-changes). What does this imply for the OSG Software stack? Not much: OSG support for the Globus Toolkit (e.g., GridFTP and GSI) will continue for as long as stakeholders need it. Period. Note the OSG Software team provides a support guarantee for all the software in its stack. When a software component reaches end-of-life, the OSG assists its stakeholders in managing the transition to new software to replace or extend those capabilities. This assistance comes in many forms, such as finding an equivalent replacement, adapting code to avoid the dependency, or helping research and develop a transition to new technology. During such transition periods, OSG takes on traditional maintenance duties (i.e., patching, bug fixes and support) of the end-of-life software. The OSG is committed to keep the software secure until its stakeholders have successfully transitioned to new software. This model has been successfully demonstrated throughout the lifetime of OSG, including for example the five year transition period for the BestMan storage resource manager. The Globus Toolkit will not be an exception. Indeed, OSG has accumulated more than a decade of experience with this software and has often provided patches back to Globus. Over the next weeks and months, we will be in contact with our stakeholder VOs, sites, and software providers to discuss their requirements and timelines with regard to GridFTP and GSI. Please reach out to goc@opensciencegrid.org with your questions, comments, and concerns. Change Log \u00b6 8 October 2020 Add note linking to the GridFTP and GSI migration plan","title":"Globus Toolkit Support"},{"location":"policy/globus-toolkit/#osg-support-of-the-globus-toolkit","text":"Gridftp and GSI Migration Plan In December 2019, the OSG developed a plan for migrating the OSG Software stack away from GridFTP and GSI that can be found here . 6 June 2017 Many in the OSG community have heard the news about the end of support for the open-source Globus Toolkit (formerly available from https://github.com/globus/globus-toolkit/blob/globus_6_branch/support-changes). What does this imply for the OSG Software stack? Not much: OSG support for the Globus Toolkit (e.g., GridFTP and GSI) will continue for as long as stakeholders need it. Period. Note the OSG Software team provides a support guarantee for all the software in its stack. When a software component reaches end-of-life, the OSG assists its stakeholders in managing the transition to new software to replace or extend those capabilities. This assistance comes in many forms, such as finding an equivalent replacement, adapting code to avoid the dependency, or helping research and develop a transition to new technology. During such transition periods, OSG takes on traditional maintenance duties (i.e., patching, bug fixes and support) of the end-of-life software. The OSG is committed to keep the software secure until its stakeholders have successfully transitioned to new software. This model has been successfully demonstrated throughout the lifetime of OSG, including for example the five year transition period for the BestMan storage resource manager. The Globus Toolkit will not be an exception. Indeed, OSG has accumulated more than a decade of experience with this software and has often provided patches back to Globus. Over the next weeks and months, we will be in contact with our stakeholder VOs, sites, and software providers to discuss their requirements and timelines with regard to GridFTP and GSI. Please reach out to goc@opensciencegrid.org with your questions, comments, and concerns.","title":"OSG Support of the Globus Toolkit"},{"location":"policy/globus-toolkit/#change-log","text":"8 October 2020 Add note linking to the GridFTP and GSI migration plan","title":"Change Log"},{"location":"policy/gridftp-gsi-migration/","text":"GridFTP and GSI Migration \u00b6 6 December 2019 Introduction \u00b6 The GridFTP protocol (for data transfer) and GSI (as an Authentication and Authorization Infrastructure, AAI) were selected for the OSG ecosystem nearly 15 years ago. In both cases, approaches are becoming increasingly niche; as they have not become widely adopted - indeed, as the communities dramatically shrink while the Internet ecosystem grows - the support costs are increasingly directly shouldered by the OSG. For example, we currently use the GridFTP and GSI implementations in the Grid Community Toolkit (GCT). While the OSG contributes to the GCT (a fork of the abandoned Globus Toolkit) to sustain operations, the long-term plan is to migrate our community off these approaches. The end of the Globus Toolkit is a stark reminder of how niche the current ecosystem is: even the original reference implementation was abandoned. Thus, OSG has the opportunity and motivation to evolve toward a data transfer protocol and security techniques that better fit our needs and allow us to connect to more vibrant software communities. For the data transfer, we are proposing HTTP; for the AAI, we are proposing the use of bearer tokens, HTTPS, and OAuth2. The production-oriented nature of the OSG \u2014 and the embedding of OSG-LHC in the WLCG community \u2014 means that careful coordination, communication, and planning are needed whenever we migrate away from production services. OSG has executed several such technology transitions before and managing the full software lifecycle is part of our value to stakeholders. This document proposes affected services, replacement technologies, and rough timelines for a transition. Timeline \u00b6 The following table contains the major milestones and deliverables for the entire transition. Detailed migration plans can be found in this document . Date Milestone or Deliverable Completed Aug 2019 Beginning of OSG 3.5 release series (last release series depending on GCT) \u2705 Aug 2019 Including HTCondor 8.9.2 in the \u2018upcoming\u2019 repository (first HTCondor version with SciTokens support). \u2705 Oct 2019 OSG no longer carries OSG-specific patches for the GCT. All patches are upstreamed or retired. \u2705 Mar 2020 \"GSI free\" site demo. Show, at proof-of-concept / prototype level, all components without use of GCT. \u2705 Sep 2020 All GCT-free components are in OSG-Upcoming. \u2705 Feb 2021 OSG series 3.6, without GCT dependencies, is released. \u2705 1 May 2022 End of support for OSG 3.5. \u2705 Frequently Asked Questions \u00b6 How does SciTokens interoperate with other token technologies in the WLCG? \u00b6 The scitokens-cpp library used by OSG can transparently use both WLCG JSON Web Tokens (JWTs) and SciTokens. Will a US-LHC migration from GridFTP to XRootD require the same migration for WLCG? \u00b6 No but we have been working to ensure that we coordinate our activities through the WLCG DOMA group. What role does LCMAPS play with SciTokens? \u00b6 LCMAPS only works with GSI. The model for SciTokens is sufficiently more simple for sites that the full complexity of LCMAPS is not needed. What does a SciTokens transition for GlideinWMS mean for European sites? \u00b6 The only piece that involves European sites is the factory to CE relationship: given HTCondor-CE 4.0 already supports SciTokens, we have begun to engage with the ARC-CE team. What are the T1s going to do? No SRM? How does tape work with XRootD and HTTPS? \u00b6 Note that CTA, which CERN is planning to transition to this year, only has XRootD support. We don't think there's a clear HTTPS picture here (or a clear dCache picture for SRM-free) so there will need to be coordination with other groups (e.g. the QoS working group). Can WLCG-FTS handle both SciTokens and x509 certificates at the same time? \u00b6 Yes. Can PhEDEx handle SciTokens? \u00b6 Yes. Version History \u00b6 2021-03-05 : Updated dates for the initial OSG 3.6 release and the targeted OSG 3.5 retirement 2020-03-30 : Completed GSI-free site demonstration 2020-03-17 : Highlighted delay in Jan 2020 milestone and new expected completion date of Mar 2020 2020-03-16 : Updated completed items on the overall timeline; added link for detailed document","title":"GridFTP and GSI Migration"},{"location":"policy/gridftp-gsi-migration/#gridftp-and-gsi-migration","text":"6 December 2019","title":"GridFTP and GSI Migration"},{"location":"policy/gridftp-gsi-migration/#introduction","text":"The GridFTP protocol (for data transfer) and GSI (as an Authentication and Authorization Infrastructure, AAI) were selected for the OSG ecosystem nearly 15 years ago. In both cases, approaches are becoming increasingly niche; as they have not become widely adopted - indeed, as the communities dramatically shrink while the Internet ecosystem grows - the support costs are increasingly directly shouldered by the OSG. For example, we currently use the GridFTP and GSI implementations in the Grid Community Toolkit (GCT). While the OSG contributes to the GCT (a fork of the abandoned Globus Toolkit) to sustain operations, the long-term plan is to migrate our community off these approaches. The end of the Globus Toolkit is a stark reminder of how niche the current ecosystem is: even the original reference implementation was abandoned. Thus, OSG has the opportunity and motivation to evolve toward a data transfer protocol and security techniques that better fit our needs and allow us to connect to more vibrant software communities. For the data transfer, we are proposing HTTP; for the AAI, we are proposing the use of bearer tokens, HTTPS, and OAuth2. The production-oriented nature of the OSG \u2014 and the embedding of OSG-LHC in the WLCG community \u2014 means that careful coordination, communication, and planning are needed whenever we migrate away from production services. OSG has executed several such technology transitions before and managing the full software lifecycle is part of our value to stakeholders. This document proposes affected services, replacement technologies, and rough timelines for a transition.","title":"Introduction"},{"location":"policy/gridftp-gsi-migration/#timeline","text":"The following table contains the major milestones and deliverables for the entire transition. Detailed migration plans can be found in this document . Date Milestone or Deliverable Completed Aug 2019 Beginning of OSG 3.5 release series (last release series depending on GCT) \u2705 Aug 2019 Including HTCondor 8.9.2 in the \u2018upcoming\u2019 repository (first HTCondor version with SciTokens support). \u2705 Oct 2019 OSG no longer carries OSG-specific patches for the GCT. All patches are upstreamed or retired. \u2705 Mar 2020 \"GSI free\" site demo. Show, at proof-of-concept / prototype level, all components without use of GCT. \u2705 Sep 2020 All GCT-free components are in OSG-Upcoming. \u2705 Feb 2021 OSG series 3.6, without GCT dependencies, is released. \u2705 1 May 2022 End of support for OSG 3.5. \u2705","title":"Timeline"},{"location":"policy/gridftp-gsi-migration/#frequently-asked-questions","text":"","title":"Frequently Asked Questions"},{"location":"policy/gridftp-gsi-migration/#how-does-scitokens-interoperate-with-other-token-technologies-in-the-wlcg","text":"The scitokens-cpp library used by OSG can transparently use both WLCG JSON Web Tokens (JWTs) and SciTokens.","title":"How does SciTokens interoperate with other token technologies in the WLCG?"},{"location":"policy/gridftp-gsi-migration/#will-a-us-lhc-migration-from-gridftp-to-xrootd-require-the-same-migration-for-wlcg","text":"No but we have been working to ensure that we coordinate our activities through the WLCG DOMA group.","title":"Will a US-LHC migration from GridFTP to XRootD require the same migration for WLCG?"},{"location":"policy/gridftp-gsi-migration/#what-role-does-lcmaps-play-with-scitokens","text":"LCMAPS only works with GSI. The model for SciTokens is sufficiently more simple for sites that the full complexity of LCMAPS is not needed.","title":"What role does LCMAPS play with SciTokens?"},{"location":"policy/gridftp-gsi-migration/#what-does-a-scitokens-transition-for-glideinwms-mean-for-european-sites","text":"The only piece that involves European sites is the factory to CE relationship: given HTCondor-CE 4.0 already supports SciTokens, we have begun to engage with the ARC-CE team.","title":"What does a SciTokens transition for GlideinWMS mean for European sites?"},{"location":"policy/gridftp-gsi-migration/#what-are-the-t1s-going-to-do-no-srm-how-does-tape-work-with-xrootd-and-https","text":"Note that CTA, which CERN is planning to transition to this year, only has XRootD support. We don't think there's a clear HTTPS picture here (or a clear dCache picture for SRM-free) so there will need to be coordination with other groups (e.g. the QoS working group).","title":"What are the T1s going to do? No SRM? How does tape work with XRootD and HTTPS?"},{"location":"policy/gridftp-gsi-migration/#can-wlcg-fts-handle-both-scitokens-and-x509-certificates-at-the-same-time","text":"Yes.","title":"Can WLCG-FTS handle both SciTokens and x509 certificates at the same time?"},{"location":"policy/gridftp-gsi-migration/#can-phedex-handle-scitokens","text":"Yes.","title":"Can PhEDEx handle SciTokens?"},{"location":"policy/gridftp-gsi-migration/#version-history","text":"2021-03-05 : Updated dates for the initial OSG 3.6 release and the targeted OSG 3.5 retirement 2020-03-30 : Completed GSI-free site demonstration 2020-03-17 : Highlighted delay in Jan 2020 milestone and new expected completion date of Mar 2020 2020-03-16 : Updated completed items on the overall timeline; added link for detailed document","title":"Version History"},{"location":"policy/gums-retire/","text":"GUMS Retirement \u00b6 This document provides an overview of the planned retirement of support for GUMS in the OSG Software Stack. Introduction \u00b6 GUMS (Grid User Management System) is an authentication system used by OSG resource providers to map grid credentials to local UNIX accounts. It provides OSG site adminstrators with a centrally managed service that can handle requests from multiple hosts that require authentication e.g., HTCondor-CE, GridFTP, and XRootD servers. In discussion with the OSG community, we have found that sites use the following GUMS features: Mapping based on VOMS attributes Host-based mappings Banning users/VOs Supporting pool accounts GUMS is a large Java web application that is more complex than necessary for the subset of features used in the OSG. Additionally, upstream support has tailed off and as a result, the maintenance burden has largely fallen on the OSG Software team. OSG's plans to retire GUMS has two major components: Find a suitable replacement for GUMS Provide documentation, tooling, and support to aid in the transition from GUMS to the intended solution Site Transition Plans \u00b6 We have released a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions. This configuration, referred to as the LCMAPS VOMS plugin, supports VOMS attribute based mappings as well as user and VO banning. Host-based mappings are not supported however, the simplicity of the plugin's installation and the distributed verification of VOMS extensions makes this feature unnecessary. Pool accounts are not supported by the plugin but this feature will be addressed in an upcoming transition-specific document. The intended solution will revolve around mapping local user accounts via user grid mapfile and we will work with any site for which this solution does not work. LCMAPS VOMS plugin installation and configuration documentation can be found here (formerly: lcmaps-voms-authentication). Timeline \u00b6 April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. July 2017 (completed): OSG 3.4 CEs can be configured with 3.3 GUMS hosts March 2018: Complete transition for sites not using pool accounts May 2018: Support is dropped for OSG 3.3 series; no further support for GUMS is provided.","title":"GUMS Retirement"},{"location":"policy/gums-retire/#gums-retirement","text":"This document provides an overview of the planned retirement of support for GUMS in the OSG Software Stack.","title":"GUMS Retirement"},{"location":"policy/gums-retire/#introduction","text":"GUMS (Grid User Management System) is an authentication system used by OSG resource providers to map grid credentials to local UNIX accounts. It provides OSG site adminstrators with a centrally managed service that can handle requests from multiple hosts that require authentication e.g., HTCondor-CE, GridFTP, and XRootD servers. In discussion with the OSG community, we have found that sites use the following GUMS features: Mapping based on VOMS attributes Host-based mappings Banning users/VOs Supporting pool accounts GUMS is a large Java web application that is more complex than necessary for the subset of features used in the OSG. Additionally, upstream support has tailed off and as a result, the maintenance burden has largely fallen on the OSG Software team. OSG's plans to retire GUMS has two major components: Find a suitable replacement for GUMS Provide documentation, tooling, and support to aid in the transition from GUMS to the intended solution","title":"Introduction"},{"location":"policy/gums-retire/#site-transition-plans","text":"We have released a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions. This configuration, referred to as the LCMAPS VOMS plugin, supports VOMS attribute based mappings as well as user and VO banning. Host-based mappings are not supported however, the simplicity of the plugin's installation and the distributed verification of VOMS extensions makes this feature unnecessary. Pool accounts are not supported by the plugin but this feature will be addressed in an upcoming transition-specific document. The intended solution will revolve around mapping local user accounts via user grid mapfile and we will work with any site for which this solution does not work. LCMAPS VOMS plugin installation and configuration documentation can be found here (formerly: lcmaps-voms-authentication).","title":"Site Transition Plans"},{"location":"policy/gums-retire/#timeline","text":"April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. July 2017 (completed): OSG 3.4 CEs can be configured with 3.3 GUMS hosts March 2018: Complete transition for sites not using pool accounts May 2018: Support is dropped for OSG 3.3 series; no further support for GUMS is provided.","title":"Timeline"},{"location":"policy/new-ospool-user/","text":"Registering for a new Open Science Pool Account \u00b6 The OSG access points at UW-Madison us the COManage identity management system to register new users. COManage uses the InCommon federation , allowing users to register with their institutional identities; there is no \"OSPool password\" that users must memorize Starting the registration process \u00b6 You can start the application for a new account by following the registration process below: Visit the new OSPool user enrollment page . You will be presented with a CILogon Single-Sign On page. Select your insitution and sign in with your insitutional credentials: Please use your institution's credentials as this simplifies the verification process; only select the Google or GitHub identity providers if your institution is not an option. After you have signed in, you will be presented with the self-signup form. Click the \"BEGIN\" button: Enter your name and email address. In most cases, your institution will provide defaults for your name and email address. If you prefer, you may override these values. If you have a GitHub account, please fill in your username. If you have already been working with an member to get the OSPool account, please select their name from the Sponsor drop-down; otherwise, leave it blank. Click the \"SUBMIT\" button: Verifying Your Email Address \u00b6 After submitting your registration application, you will receive an email from registry@cilogon.org to verify your email address. Follow the link in the email and click the \"Accept\" button to complete the verification: Adding an SSH Key \u00b6 A SSH public key (see this overview page for more information) allows for easier SSH-based login to the access point. After verifying your email address, you will be given an option to upload a public key for your account. If you are not ready to do that at this time, simply click \"skip\". ) Meeting with a Facilitator \u00b6 After verifying your email address (and optionally uploading the SSH key), a new support ticket will be generated and we will contact you to arrange a meeting with a Facilitator for an introduction to the access point and High Throughput Computing. After this initial meeting, your account will be finalized and you will be able to login to the system. Getting Help \u00b6 For assistance or questions, please email the support team at support@opensciencegrid.org","title":"New OSPool User Registration"},{"location":"policy/new-ospool-user/#registering-for-a-new-open-science-pool-account","text":"The OSG access points at UW-Madison us the COManage identity management system to register new users. COManage uses the InCommon federation , allowing users to register with their institutional identities; there is no \"OSPool password\" that users must memorize","title":"Registering for a new Open Science Pool Account"},{"location":"policy/new-ospool-user/#starting-the-registration-process","text":"You can start the application for a new account by following the registration process below: Visit the new OSPool user enrollment page . You will be presented with a CILogon Single-Sign On page. Select your insitution and sign in with your insitutional credentials: Please use your institution's credentials as this simplifies the verification process; only select the Google or GitHub identity providers if your institution is not an option. After you have signed in, you will be presented with the self-signup form. Click the \"BEGIN\" button: Enter your name and email address. In most cases, your institution will provide defaults for your name and email address. If you prefer, you may override these values. If you have a GitHub account, please fill in your username. If you have already been working with an member to get the OSPool account, please select their name from the Sponsor drop-down; otherwise, leave it blank. Click the \"SUBMIT\" button:","title":"Starting the registration process"},{"location":"policy/new-ospool-user/#verifying-your-email-address","text":"After submitting your registration application, you will receive an email from registry@cilogon.org to verify your email address. Follow the link in the email and click the \"Accept\" button to complete the verification:","title":"Verifying Your Email Address"},{"location":"policy/new-ospool-user/#adding-an-ssh-key","text":"A SSH public key (see this overview page for more information) allows for easier SSH-based login to the access point. After verifying your email address, you will be given an option to upload a public key for your account. If you are not ready to do that at this time, simply click \"skip\". )","title":"Adding an SSH Key"},{"location":"policy/new-ospool-user/#meeting-with-a-facilitator","text":"After verifying your email address (and optionally uploading the SSH key), a new support ticket will be generated and we will contact you to arrange a meeting with a Facilitator for an introduction to the access point and High Throughput Computing. After this initial meeting, your account will be finalized and you will be able to login to the system.","title":"Meeting with a Facilitator"},{"location":"policy/new-ospool-user/#getting-help","text":"For assistance or questions, please email the support team at support@opensciencegrid.org","title":"Getting Help"},{"location":"policy/service-migrations-spring-2018/","text":"Service Migrations - Spring 2018 \u00b6 The Open Science Grid (OSG) has transitioned effort from Indiana, requiring a redistribution of support and services. Some services were retired, most services were migrated to other locations (with minimal expected sites impact), and some services were migrated that resulted in significant impact on sites. This document was intended to guide OSG site administrators through these changes, highlighting where the site administrator action is required. If you have questions or concerns that are not addressed in this document, see the Getting Help section for details. Getting Help \u00b6 If you have questions or concerns that are not addressed in this document, please contact us at the usual locations: help@osg-htc.org software-discuss@opensciencegrid.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org Support Changes \u00b6 The Footprints ticketing system at https://ticket.opensciencegrid.org was used to track support and security issues as well as certificate and membership requests. This service was retired in favor of two different ticketing systems, depending on the VOs you support at your site: If your site primarily supports... Submit new tickets to... LHC VOs GGUS Anyone else Freshdesk If you experience any problems with ticketing, please contact us at help@osg-htc.org . Service-specific details \u00b6 OSG CA \u00b6 The OSG CA service offered certificate request, renewal, and revocation through the OIM web interface, the OIM REST API, and the osg-pki-tools command-line tool. This service was retired on May 31 but the OSG CA certificate remains in the IGTF distribution, so any certificates issued by the OSG CA remain valid until they expire. The OSG recommends using the following CA certificate services: For... We plan to use the following Certificate Authorities... Host Certificates InCommon and Let\u2019s Encrypt User Certificates CILogon Basic for non-LHC users LHC users should continue to request their user certificates from CERN. Web-Based services Let's Encrypt Note The semantics of Let's Encrypt certificates are different from those of previous CAs. Please see the security team's position on Let's Encrypt for the security and setup implications of switching to a Let's Encrypt host or service certificate. If you experience any problems acquiring host or service certificates, please contact us at help@osg-htc.org . Software Repository \u00b6 The OSG Software repository includes the YUM repositories, client tarballs, and CA tarballs. The physical hosting location changed during the migration but was otherwise unchanged. If you experience any problems with the OSG Software repository, please contact us at help@osg-htc.org . MyOSG and OIM \u00b6 The MyOSG service used to provide web and REST interfaces to access information about OSG resource topology, projects, and VOs. The MyOSG web interface was retired but we continue to offer the same REST interface at https://my.opensciencegrid.org . OIM served as the database for the information used by MyOSG with a web interface for data updates. The OIM web interface was retired but its data was migrated to the topology repository . Updates to the aforementioned data can be requested via email or pull request. Note Please see the OSG CA section for information regarding the OIM certificate service. If you experience any problems with MyOSG or the topology repository, please contact us at help@osg-htc.org . GRACC Accounting and WLCG Accounting \u00b6 No changes were made to the GRACC accounting service during the service migration. If you experience any problems with GRACC accounting, please contact us at help@osg-htc.org . OASIS and CVMFS \u00b6 The OASIS (OSG Application and Software Installation Service) is a service used to distribute common applications and software to OSG sites via CVMFS. The OSG hosts a CVMFS Stratum-0 for keysigning, a repository server, and a CVMFS Stratum-1. The physical hosting location of these services were moved to Nebraska without any other changes. If you experience any problems with OASIS or CVMFS, please contact us at help@osg-htc.org . VOMS Admin Server \u00b6 The OSG VOMS service was used to sign VOMS attributes for members of the OSG VO and responded to queries for a list of VO members. VOMS Admin Server is deprecated in the OSG and the OSG VOMS servers were retired as planned. RSV \u00b6 The central RSV service was a monitoring tool that displayed every service status information about OSG sites that elected to provide it. It was retired since there was no longer a need to monitor OSG site status as a whole. If you would like to monitor your OSG services, you can access the status page of your local RSV instance. Collector \u00b6 The central Collector is a central database service that provides details about pilot jobs currently running in the OSG. The physical hosting location of the central Collector was moved but there were no other changes. If you experience any problems with the central Collector, please contact us at help@osg-htc.org . Homepage \u00b6 The OSG homepage was a Wordpress instance that has been moved to a static site. If you experience any problems with the homepage, please contact us at help@osg-htc.org .","title":"Service Migrations - Spring 2018"},{"location":"policy/service-migrations-spring-2018/#service-migrations-spring-2018","text":"The Open Science Grid (OSG) has transitioned effort from Indiana, requiring a redistribution of support and services. Some services were retired, most services were migrated to other locations (with minimal expected sites impact), and some services were migrated that resulted in significant impact on sites. This document was intended to guide OSG site administrators through these changes, highlighting where the site administrator action is required. If you have questions or concerns that are not addressed in this document, see the Getting Help section for details.","title":"Service Migrations - Spring 2018"},{"location":"policy/service-migrations-spring-2018/#getting-help","text":"If you have questions or concerns that are not addressed in this document, please contact us at the usual locations: help@osg-htc.org software-discuss@opensciencegrid.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org","title":"Getting Help"},{"location":"policy/service-migrations-spring-2018/#support-changes","text":"The Footprints ticketing system at https://ticket.opensciencegrid.org was used to track support and security issues as well as certificate and membership requests. This service was retired in favor of two different ticketing systems, depending on the VOs you support at your site: If your site primarily supports... Submit new tickets to... LHC VOs GGUS Anyone else Freshdesk If you experience any problems with ticketing, please contact us at help@osg-htc.org .","title":"Support Changes"},{"location":"policy/service-migrations-spring-2018/#service-specific-details","text":"","title":"Service-specific details"},{"location":"policy/service-migrations-spring-2018/#osg-ca","text":"The OSG CA service offered certificate request, renewal, and revocation through the OIM web interface, the OIM REST API, and the osg-pki-tools command-line tool. This service was retired on May 31 but the OSG CA certificate remains in the IGTF distribution, so any certificates issued by the OSG CA remain valid until they expire. The OSG recommends using the following CA certificate services: For... We plan to use the following Certificate Authorities... Host Certificates InCommon and Let\u2019s Encrypt User Certificates CILogon Basic for non-LHC users LHC users should continue to request their user certificates from CERN. Web-Based services Let's Encrypt Note The semantics of Let's Encrypt certificates are different from those of previous CAs. Please see the security team's position on Let's Encrypt for the security and setup implications of switching to a Let's Encrypt host or service certificate. If you experience any problems acquiring host or service certificates, please contact us at help@osg-htc.org .","title":"OSG CA"},{"location":"policy/service-migrations-spring-2018/#software-repository","text":"The OSG Software repository includes the YUM repositories, client tarballs, and CA tarballs. The physical hosting location changed during the migration but was otherwise unchanged. If you experience any problems with the OSG Software repository, please contact us at help@osg-htc.org .","title":"Software Repository"},{"location":"policy/service-migrations-spring-2018/#myosg-and-oim","text":"The MyOSG service used to provide web and REST interfaces to access information about OSG resource topology, projects, and VOs. The MyOSG web interface was retired but we continue to offer the same REST interface at https://my.opensciencegrid.org . OIM served as the database for the information used by MyOSG with a web interface for data updates. The OIM web interface was retired but its data was migrated to the topology repository . Updates to the aforementioned data can be requested via email or pull request. Note Please see the OSG CA section for information regarding the OIM certificate service. If you experience any problems with MyOSG or the topology repository, please contact us at help@osg-htc.org .","title":"MyOSG and OIM"},{"location":"policy/service-migrations-spring-2018/#gracc-accounting-and-wlcg-accounting","text":"No changes were made to the GRACC accounting service during the service migration. If you experience any problems with GRACC accounting, please contact us at help@osg-htc.org .","title":"GRACC Accounting and WLCG Accounting"},{"location":"policy/service-migrations-spring-2018/#oasis-and-cvmfs","text":"The OASIS (OSG Application and Software Installation Service) is a service used to distribute common applications and software to OSG sites via CVMFS. The OSG hosts a CVMFS Stratum-0 for keysigning, a repository server, and a CVMFS Stratum-1. The physical hosting location of these services were moved to Nebraska without any other changes. If you experience any problems with OASIS or CVMFS, please contact us at help@osg-htc.org .","title":"OASIS and CVMFS"},{"location":"policy/service-migrations-spring-2018/#voms-admin-server","text":"The OSG VOMS service was used to sign VOMS attributes for members of the OSG VO and responded to queries for a list of VO members. VOMS Admin Server is deprecated in the OSG and the OSG VOMS servers were retired as planned.","title":"VOMS Admin Server"},{"location":"policy/service-migrations-spring-2018/#rsv","text":"The central RSV service was a monitoring tool that displayed every service status information about OSG sites that elected to provide it. It was retired since there was no longer a need to monitor OSG site status as a whole. If you would like to monitor your OSG services, you can access the status page of your local RSV instance.","title":"RSV"},{"location":"policy/service-migrations-spring-2018/#collector","text":"The central Collector is a central database service that provides details about pilot jobs currently running in the OSG. The physical hosting location of the central Collector was moved but there were no other changes. If you experience any problems with the central Collector, please contact us at help@osg-htc.org .","title":"Collector"},{"location":"policy/service-migrations-spring-2018/#homepage","text":"The OSG homepage was a Wordpress instance that has been moved to a static site. If you experience any problems with the homepage, please contact us at help@osg-htc.org .","title":"Homepage"},{"location":"policy/software-release/","text":"Software Release Policy \u00b6 This document contains information about the OSG Software Yum repositories and their policies. For details regarding the technical process for an OSG release, see this document . Yum Repositories \u00b6 The Software Team maintains the following Yum repositories: osg-development : This is the \"wild west\", the place where software goes while it is being worked on by the software team. osg-testing : This is where software goes when it is ready for wide-spread testing, including upstream release candidates osg-prerelease : This is where software goes just before being released, for final verification. osg-release : This is the official, production release of the software stack. This is the main repository for end-users. osg-contrib : This is where software goes that is not officially supported by the OSG Software Team, but we provide as a convenience for software our users might find useful. Occasionally there may be other repositories for specific short-term purposes. Note osg-rolling and osg-release-VERSION are only present in the OSG 3.5 series. osg-rolling : This is where software goes before being included in a point release. Intended for end-users. In OSG 3.5, software goes into osg-rolling when it is put into osg-prerelease . osg-release-VERSION : This repository is created per release and its name contains the version number (e.g. osg-release-3.5.4). This is intended mostly for testing purposes, though users may occasionally find it useful. Version Numbers \u00b6 OSG 3.6+ \u00b6 The version number matches the release series. OSG 3.5 \u00b6 There is a single version number that is used to summarize the contents of the osg-release repository. Having a single version number is very useful for a variety of reasons, including: Every time changes are made to the osg-release repository, we update the version number and write release notes. We have a shorthand for referring to the state of the repository; we can talk about specific releases. However, there are important caveats about the version number: Even if a user says they have installed Version X, it may not be an accurate reflection of what they have installed: they may have chosen to update some of their software from a previous version. To truly understand what they have installed, the entire set of RPMs installed on their computer must be considered. The version number is only meaningful in the osg-release repository, though for technical reasons it's present (as an RPM) in other repositories. The version number is communicated as follows: Every time a new release is made, the version number is updated. All release notes and communication to users about this release uses the new version number. The version number will be of the form X.Y.Z. As of this writing, version numbers are 3.5.Z, where Z indicates a minor revision. Progression of Repositories \u00b6 This figure shows the progression of repositories that packages will go through: osg-development -> osg-testing -> osg-prerelease / osg-rolling -> osg-release \\ -> osg-contrib Release Policies \u00b6 Adding packages to osg-development \u00b6 New packages will only be added to osg-development with the permission of the OSG Software Manager. Updates can be done at any time without permission, but developers should be careful if their updates might be significant, particularly if an update might cause series compatibility issues. In cases where there is uncertainty, discuss it with the Software Manager. Moving packages to osg-testing \u00b6 A package may be moved from osg-development to osg-testing when the individual maintainer of that package decides that it is ready for widespread testing and when approved by the OSG Software Manager. Approval is needed because this is when we first make packages available to people outside of the OSG Software Team. Moving packages to osg-prerelease; Readying the release \u00b6 When we are ready to make a production release, we first move the correct subset of packages from osg-testing into osg-prerelease . This should be done after checking with the OSG Release Manager to verify that it's okay to release the software. The intention of osg-prerelease is to do a final verification that we have the correct set of packages for release and that they really work together. This is important because the osg-testing repository might contain a mix of packages that are ready for release with packages that are not ready for release. When moving packages to osg-prerelease , the team member doing the release will: Find the correct set of packages to push from osg-testing into osg-prerelease . At a minimum, run the automated test suite on the contents of osg-prerelease . In cases were more extensive testing is needed, or the test suite doesn't sufficiently cover the testing needs, do specific ad-hoc testing. (If appropriate, consider proposing extensions to the automated test suite.) We expect that in most cases, this process of updating and testing the osg-prerelease repository will be less than one day. If there are urgent security updates to release, this process may be shortened. Moving packages to osg-release \u00b6 When the osg-prerelease repository has been updated and verified, all of the changed software can be moved into the osg-release repository. As part of this move, three important tasks must be done: The released packages are automatically recorded in such a manner that end users/administrators can be notified if desired. Major package updates will also be recorded on the OSG 3.6 \"News\" page with links to the respective release note page or change log. An announcement is sent out whenever a major package is updated. Moving packages to osg-contrib \u00b6 The osg-contrib repository is loosely regulated. In most cases, the team member in charge of the package can decide when a package is updated in osg-contrib . Contrib packages should be tested in osg-development first. Timing of releases \u00b6 Software is released between 9AM and 5PM Central Time on a work day that is followed by a work day. The idea is to have a working day to correct any problems with a release rather than having a problematic release persist over a weekend or holiday. We will make exceptions for urgent situations; consult with the release manager when needed. CA Certificates and VO Client packages \u00b6 Packages that contain only data are not part of the usual release cycle. Currently, these are the CA certificate packages and the VO Client packages. Updates to these packages come from the Security Team and Software Team, respectively. They still move through the usual process for release, and the Software and Release Managers decide when these packages should be promoted to the next repository level.","title":"Software Release Policy"},{"location":"policy/software-release/#software-release-policy","text":"This document contains information about the OSG Software Yum repositories and their policies. For details regarding the technical process for an OSG release, see this document .","title":"Software Release Policy"},{"location":"policy/software-release/#yum-repositories","text":"The Software Team maintains the following Yum repositories: osg-development : This is the \"wild west\", the place where software goes while it is being worked on by the software team. osg-testing : This is where software goes when it is ready for wide-spread testing, including upstream release candidates osg-prerelease : This is where software goes just before being released, for final verification. osg-release : This is the official, production release of the software stack. This is the main repository for end-users. osg-contrib : This is where software goes that is not officially supported by the OSG Software Team, but we provide as a convenience for software our users might find useful. Occasionally there may be other repositories for specific short-term purposes. Note osg-rolling and osg-release-VERSION are only present in the OSG 3.5 series. osg-rolling : This is where software goes before being included in a point release. Intended for end-users. In OSG 3.5, software goes into osg-rolling when it is put into osg-prerelease . osg-release-VERSION : This repository is created per release and its name contains the version number (e.g. osg-release-3.5.4). This is intended mostly for testing purposes, though users may occasionally find it useful.","title":"Yum Repositories"},{"location":"policy/software-release/#version-numbers","text":"","title":"Version Numbers"},{"location":"policy/software-release/#osg-36","text":"The version number matches the release series.","title":"OSG 3.6+"},{"location":"policy/software-release/#osg-35","text":"There is a single version number that is used to summarize the contents of the osg-release repository. Having a single version number is very useful for a variety of reasons, including: Every time changes are made to the osg-release repository, we update the version number and write release notes. We have a shorthand for referring to the state of the repository; we can talk about specific releases. However, there are important caveats about the version number: Even if a user says they have installed Version X, it may not be an accurate reflection of what they have installed: they may have chosen to update some of their software from a previous version. To truly understand what they have installed, the entire set of RPMs installed on their computer must be considered. The version number is only meaningful in the osg-release repository, though for technical reasons it's present (as an RPM) in other repositories. The version number is communicated as follows: Every time a new release is made, the version number is updated. All release notes and communication to users about this release uses the new version number. The version number will be of the form X.Y.Z. As of this writing, version numbers are 3.5.Z, where Z indicates a minor revision.","title":"OSG 3.5"},{"location":"policy/software-release/#progression-of-repositories","text":"This figure shows the progression of repositories that packages will go through: osg-development -> osg-testing -> osg-prerelease / osg-rolling -> osg-release \\ -> osg-contrib","title":"Progression of Repositories"},{"location":"policy/software-release/#release-policies","text":"","title":"Release Policies"},{"location":"policy/software-release/#adding-packages-to-osg-development","text":"New packages will only be added to osg-development with the permission of the OSG Software Manager. Updates can be done at any time without permission, but developers should be careful if their updates might be significant, particularly if an update might cause series compatibility issues. In cases where there is uncertainty, discuss it with the Software Manager.","title":"Adding packages to osg-development"},{"location":"policy/software-release/#moving-packages-to-osg-testing","text":"A package may be moved from osg-development to osg-testing when the individual maintainer of that package decides that it is ready for widespread testing and when approved by the OSG Software Manager. Approval is needed because this is when we first make packages available to people outside of the OSG Software Team.","title":"Moving packages to osg-testing"},{"location":"policy/software-release/#moving-packages-to-osg-prerelease-readying-the-release","text":"When we are ready to make a production release, we first move the correct subset of packages from osg-testing into osg-prerelease . This should be done after checking with the OSG Release Manager to verify that it's okay to release the software. The intention of osg-prerelease is to do a final verification that we have the correct set of packages for release and that they really work together. This is important because the osg-testing repository might contain a mix of packages that are ready for release with packages that are not ready for release. When moving packages to osg-prerelease , the team member doing the release will: Find the correct set of packages to push from osg-testing into osg-prerelease . At a minimum, run the automated test suite on the contents of osg-prerelease . In cases were more extensive testing is needed, or the test suite doesn't sufficiently cover the testing needs, do specific ad-hoc testing. (If appropriate, consider proposing extensions to the automated test suite.) We expect that in most cases, this process of updating and testing the osg-prerelease repository will be less than one day. If there are urgent security updates to release, this process may be shortened.","title":"Moving packages to osg-prerelease; Readying the release"},{"location":"policy/software-release/#moving-packages-to-osg-release","text":"When the osg-prerelease repository has been updated and verified, all of the changed software can be moved into the osg-release repository. As part of this move, three important tasks must be done: The released packages are automatically recorded in such a manner that end users/administrators can be notified if desired. Major package updates will also be recorded on the OSG 3.6 \"News\" page with links to the respective release note page or change log. An announcement is sent out whenever a major package is updated.","title":"Moving packages to osg-release"},{"location":"policy/software-release/#moving-packages-to-osg-contrib","text":"The osg-contrib repository is loosely regulated. In most cases, the team member in charge of the package can decide when a package is updated in osg-contrib . Contrib packages should be tested in osg-development first.","title":"Moving packages to osg-contrib"},{"location":"policy/software-release/#timing-of-releases","text":"Software is released between 9AM and 5PM Central Time on a work day that is followed by a work day. The idea is to have a working day to correct any problems with a release rather than having a problematic release persist over a weekend or holiday. We will make exceptions for urgent situations; consult with the release manager when needed.","title":"Timing of releases"},{"location":"policy/software-release/#ca-certificates-and-vo-client-packages","text":"Packages that contain only data are not part of the usual release cycle. Currently, these are the CA certificate packages and the VO Client packages. Updates to these packages come from the Security Team and Software Team, respectively. They still move through the usual process for release, and the Software and Release Managers decide when these packages should be promoted to the next repository level.","title":"CA Certificates and VO Client packages"},{"location":"policy/software-support/","text":"Software Support \u00b6 This document describes how OSG Technology Team members should support the OSG Software Stack, including triage duty responsibilities and when to transition from direct support inquiries to a ticketing system such as Freshdesk or Jira. Considerations \u00b6 When providing support for our users, remember the following: We are a small community and we need to take good care of our users. Please be friendly and patient even when the user is frustrated or lacking in knowledge. Always sign your ticket with your full name, so people know who is responding. If it's easy for you, include a signature at the bottom of your response. If you need to collect information about a problematic host, ask users to run osg-system-profiler . It can shorten the number of times you ask for information because it collects quite a bit for you. If you run across a problem that has a chance of being hit by other users: Is there a bug we should fix in the software? Open a Jira ticket. Is there something we could improve in the software? Notify the Software Area Coordinator. Is there a way to improve our documentation? Notify the Software Area Coordinator. Can you extend our troubleshooting documents to help people track this down more quickly? Consider the troubleshooting documents to be as much for us as for our users. Is this something that other Technology Team members should be aware of? Note it during the support discussion during the weekly OSG Technology meeting, or email the Technology Team if it seems more urgent. Triage Duty \u00b6 The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Area Coordinator for access). Logging in as an agent Don't enter your credentials directly into the login page ! Click the agent login link instead so that you don't have to enter your credentials twice. During normal work hours, the OSG Technology Team splits responsibilities for managing incoming OSG Software support requests based upon a weekly rotation . If you are on triage duty, your responsibilities are as follows: Watch for new software tickets: review the Unresolved Software Tickets and All Unassigned Tickets filters at least three times daily for new OSG Software-related tickets. For any such unassigned tickets, assign it as follows: If you can handle an incoming ticket, assign it to yourself. Inasmuch as possible, you should strive to handle the easier tickets and not pass them off to other people. If you cannot handle an incoming ticket, collect initial details such as relevant versions, logs, etc., and assign the ticket to the most appropriate Technology Team member. Where appropriate, CC third-parties or add relevant OSG staff with FD accounts as watchers (see this documentation ) New sites interested in joining the OSG For support requests inquiring about joining the OSG, assign the ticket to the Campus Facilitation group. Review assigned software tickets. For tickets that are not being handled in a timely fashion (pay special attention to OVERDUE and Customer Responded tickets): If the ticket is pending and the assignee has not responded in > 2 business days, notify the ticket assignee via private note that they need to revisit the ticket. If the ticket is waiting on the customer or a third party and they have not responded in > 1 week, reply to the ticket asking if they've had the time to review the Technology Team's latest response(s). If the ticket was opened by the customer, is waiting on the customer and they have not responded in > 2 weeks, close the ticket and let the customer know that they can re-open it by responding whenever they're ready to tackle the issue again. Review and approve/deny COManage site contact registrations: Follow the instructions to review site contact registrations here . Review Topology data pull requests: Review any Topology PRs that update anything in the collaborations , projects/ , topology/ , or virtual-organizations directories. New institutions Approval of new facilities or project institutions require PATh Project Office, i.e. Irene or Janet. Re-assign non-software tickets: Tickets that have been mistakenly assigned to the Software group should be re-assigned to the appropriate group. Merge duplicate tickets: Responses to a ticket sometimes results in creation of a new ticket; these new tickets should be merged into the original ticket. See this documentation . Split off new support requests in old tickets: If a user has reopened or followed-up in a ticket with a new support request unrelated to the existing ticket (this is a judgment call) and their comment is the last one in the ticket, split off the comment into a new ticket (see this documentation ). If you are unsure if a ticket should be split, consult the Software Area Coordinator. Do not split comments other than the last one FD treats splitting tickets as \"take this comment and make it the start of a new ticket\" and not \"take this comment and all subsequent comments into a new ticket\". Clean up spam: Mark the ticket as spam and block the user. See this documentation . Clean up automated replies: announcements are often sent with Reply-to: help@osg-htc.org so automated replies (e.g. Out of Office, mailing list moderation) will generate tickets. These tickets can be closed. Question If you have questions concerning a ticket, consult the OSG Software Team Manager and/or the #software channel in the OSG Slack. Updating the triage calendar \u00b6 The current triage duty schedule can be found in the OSG Software calendar, hosted on Tim Cartwright\u2019s Google account. If you need privileges to edit the calendar, ask the OSG Software Team Manager. To update the triage duty schedule: Clone the git repo Generate next rotation: ./triage.py --generateNextRotation > rotation.txt Check and update assignments according to team member outages Load triage assignments into Google Calendar: ./triage.py --load rotation.txt To subscribe to this calendar in your calendar program, use the iCal URL: https://www.google.com/calendar/ical/h5t4mns6omp49db1e4qtqrrf4g%40group.calendar.google.com/public/basic.ics Ticket Systems \u00b6 The OSG Technology Team uses the Freshdesk and Jira ticketing systems to track support and all other work, respectively. This section describes the differences between the two as well as some OSG Technology Freshdesk conventions. Direct Email \u00b6 Sometimes users may email you directly with support inquiries. If someone emails you directly for support, you have the choice of when to move it to a ticket. The recommended criteria are: If it's easy to handle and you can definitely do it yourself, leave it in email. If there's a chance that you can't do it in a timely fashion, turn it into a ticket. If there's a chance that you might lose track of the email, turn it into a ticket. If there's a chance that you might need help from others, turn it into a ticket. If it's an unusual topic and other people would benefit from seeing the ticket (now or in the future), turn it into a ticket. Freshdesk \u00b6 Freshdesk access The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Manager for access). Freshdesk tickets are for user support, i.e. this is where we help users debug, understand their problems, etc. When replying to or otherwise updating a Freshdesk ticket, there are a few things to note: Freshdesk auto-populates the contact's name when replying through the web interface, e.g. Hi Brian . Ensure that the name is correct, especially if there are multiple parties involved in a single ticket. If the auto-populated name looks incorrect, e.g. Hi blin.wisc , fix the contact's First and Last name fields. Make sure to set the state of the ticket, which is helpful for those on triage: State Description Open OSG staff is responsible for next actions, including when ticket has not yet been assigned (initial ticket state) Waiting on Customer Assignee needs the reporter to respond Waiting on Third Party Assignee needs a response from a CC Resolved Support is complete or the user is unresponsive. See above . Closed DO NOT SET MANUALLY . Terminal ticket state that is set by Freshdesk. If actionable Technology Team tasks arise from a Freshdesk ticket, Jira ticket(s) should be created to track that work. Resultant Jira tickets should include a link to the original Freshdesk ticket, a description of the problem or feature request, and a proposed solution or implementation. After the relevant Jira tickets have been created, ask the user if they would be ok with tracking the issue via Jira. If they say yes, close the Freshdesk ticket. Jira \u00b6 Jira is for tracking our work and it's meant for internal usage, not for user support. In general, users should not ask for support via Jira. A single user support ticket might result in zero, one, or multiple Jira tickets.","title":"Software Support"},{"location":"policy/software-support/#software-support","text":"This document describes how OSG Technology Team members should support the OSG Software Stack, including triage duty responsibilities and when to transition from direct support inquiries to a ticketing system such as Freshdesk or Jira.","title":"Software Support"},{"location":"policy/software-support/#considerations","text":"When providing support for our users, remember the following: We are a small community and we need to take good care of our users. Please be friendly and patient even when the user is frustrated or lacking in knowledge. Always sign your ticket with your full name, so people know who is responding. If it's easy for you, include a signature at the bottom of your response. If you need to collect information about a problematic host, ask users to run osg-system-profiler . It can shorten the number of times you ask for information because it collects quite a bit for you. If you run across a problem that has a chance of being hit by other users: Is there a bug we should fix in the software? Open a Jira ticket. Is there something we could improve in the software? Notify the Software Area Coordinator. Is there a way to improve our documentation? Notify the Software Area Coordinator. Can you extend our troubleshooting documents to help people track this down more quickly? Consider the troubleshooting documents to be as much for us as for our users. Is this something that other Technology Team members should be aware of? Note it during the support discussion during the weekly OSG Technology meeting, or email the Technology Team if it seems more urgent.","title":"Considerations"},{"location":"policy/software-support/#triage-duty","text":"The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Area Coordinator for access). Logging in as an agent Don't enter your credentials directly into the login page ! Click the agent login link instead so that you don't have to enter your credentials twice. During normal work hours, the OSG Technology Team splits responsibilities for managing incoming OSG Software support requests based upon a weekly rotation . If you are on triage duty, your responsibilities are as follows: Watch for new software tickets: review the Unresolved Software Tickets and All Unassigned Tickets filters at least three times daily for new OSG Software-related tickets. For any such unassigned tickets, assign it as follows: If you can handle an incoming ticket, assign it to yourself. Inasmuch as possible, you should strive to handle the easier tickets and not pass them off to other people. If you cannot handle an incoming ticket, collect initial details such as relevant versions, logs, etc., and assign the ticket to the most appropriate Technology Team member. Where appropriate, CC third-parties or add relevant OSG staff with FD accounts as watchers (see this documentation ) New sites interested in joining the OSG For support requests inquiring about joining the OSG, assign the ticket to the Campus Facilitation group. Review assigned software tickets. For tickets that are not being handled in a timely fashion (pay special attention to OVERDUE and Customer Responded tickets): If the ticket is pending and the assignee has not responded in > 2 business days, notify the ticket assignee via private note that they need to revisit the ticket. If the ticket is waiting on the customer or a third party and they have not responded in > 1 week, reply to the ticket asking if they've had the time to review the Technology Team's latest response(s). If the ticket was opened by the customer, is waiting on the customer and they have not responded in > 2 weeks, close the ticket and let the customer know that they can re-open it by responding whenever they're ready to tackle the issue again. Review and approve/deny COManage site contact registrations: Follow the instructions to review site contact registrations here . Review Topology data pull requests: Review any Topology PRs that update anything in the collaborations , projects/ , topology/ , or virtual-organizations directories. New institutions Approval of new facilities or project institutions require PATh Project Office, i.e. Irene or Janet. Re-assign non-software tickets: Tickets that have been mistakenly assigned to the Software group should be re-assigned to the appropriate group. Merge duplicate tickets: Responses to a ticket sometimes results in creation of a new ticket; these new tickets should be merged into the original ticket. See this documentation . Split off new support requests in old tickets: If a user has reopened or followed-up in a ticket with a new support request unrelated to the existing ticket (this is a judgment call) and their comment is the last one in the ticket, split off the comment into a new ticket (see this documentation ). If you are unsure if a ticket should be split, consult the Software Area Coordinator. Do not split comments other than the last one FD treats splitting tickets as \"take this comment and make it the start of a new ticket\" and not \"take this comment and all subsequent comments into a new ticket\". Clean up spam: Mark the ticket as spam and block the user. See this documentation . Clean up automated replies: announcements are often sent with Reply-to: help@osg-htc.org so automated replies (e.g. Out of Office, mailing list moderation) will generate tickets. These tickets can be closed. Question If you have questions concerning a ticket, consult the OSG Software Team Manager and/or the #software channel in the OSG Slack.","title":"Triage Duty"},{"location":"policy/software-support/#updating-the-triage-calendar","text":"The current triage duty schedule can be found in the OSG Software calendar, hosted on Tim Cartwright\u2019s Google account. If you need privileges to edit the calendar, ask the OSG Software Team Manager. To update the triage duty schedule: Clone the git repo Generate next rotation: ./triage.py --generateNextRotation > rotation.txt Check and update assignments according to team member outages Load triage assignments into Google Calendar: ./triage.py --load rotation.txt To subscribe to this calendar in your calendar program, use the iCal URL: https://www.google.com/calendar/ical/h5t4mns6omp49db1e4qtqrrf4g%40group.calendar.google.com/public/basic.ics","title":"Updating the triage calendar"},{"location":"policy/software-support/#ticket-systems","text":"The OSG Technology Team uses the Freshdesk and Jira ticketing systems to track support and all other work, respectively. This section describes the differences between the two as well as some OSG Technology Freshdesk conventions.","title":"Ticket Systems"},{"location":"policy/software-support/#direct-email","text":"Sometimes users may email you directly with support inquiries. If someone emails you directly for support, you have the choice of when to move it to a ticket. The recommended criteria are: If it's easy to handle and you can definitely do it yourself, leave it in email. If there's a chance that you can't do it in a timely fashion, turn it into a ticket. If there's a chance that you might lose track of the email, turn it into a ticket. If there's a chance that you might need help from others, turn it into a ticket. If it's an unusual topic and other people would benefit from seeing the ticket (now or in the future), turn it into a ticket.","title":"Direct Email"},{"location":"policy/software-support/#freshdesk","text":"Freshdesk access The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Manager for access). Freshdesk tickets are for user support, i.e. this is where we help users debug, understand their problems, etc. When replying to or otherwise updating a Freshdesk ticket, there are a few things to note: Freshdesk auto-populates the contact's name when replying through the web interface, e.g. Hi Brian . Ensure that the name is correct, especially if there are multiple parties involved in a single ticket. If the auto-populated name looks incorrect, e.g. Hi blin.wisc , fix the contact's First and Last name fields. Make sure to set the state of the ticket, which is helpful for those on triage: State Description Open OSG staff is responsible for next actions, including when ticket has not yet been assigned (initial ticket state) Waiting on Customer Assignee needs the reporter to respond Waiting on Third Party Assignee needs a response from a CC Resolved Support is complete or the user is unresponsive. See above . Closed DO NOT SET MANUALLY . Terminal ticket state that is set by Freshdesk. If actionable Technology Team tasks arise from a Freshdesk ticket, Jira ticket(s) should be created to track that work. Resultant Jira tickets should include a link to the original Freshdesk ticket, a description of the problem or feature request, and a proposed solution or implementation. After the relevant Jira tickets have been created, ask the user if they would be ok with tracking the issue via Jira. If they say yes, close the Freshdesk ticket.","title":"Freshdesk"},{"location":"policy/software-support/#jira","text":"Jira is for tracking our work and it's meant for internal usage, not for user support. In general, users should not ask for support via Jira. A single user support ticket might result in zero, one, or multiple Jira tickets.","title":"Jira"},{"location":"policy/topology-registration/","text":"Handling Topology and Contacts Registration \u00b6 This is an internal procedure handled by OSG Staff; the documentation is available in the operations site .","title":"Handling Topology/Contacts Registrations"},{"location":"policy/topology-registration/#handling-topology-and-contacts-registration","text":"This is an internal procedure handled by OSG Staff; the documentation is available in the operations site .","title":"Handling Topology and Contacts Registration"},{"location":"policy/voms-admin-retire/","text":"VOMS-Admin Retirement \u00b6 Introduction \u00b6 This document provides an overview of the planned retirement of support for VOMS-Admin in the OSG Software Stack. Support for the VOMS infrastructure has three major components: VOMS-Admin : A web interface for maintaining the list of authorized users in a VO and their various authorizations (group membership, roles, attributes, etc). VOMS-Server : A TCP service which signs a cryptographic extension on an X509 proxy certificate asserting the authorizations available to the authenticated user. VOMS Client : Software for extracting and validating the signed VOMS extension from an X509 proxy. The validation is meant to be distributed: the VOMS client does not need to contact the VOMS-Admin server. However, OSG has historically used software such as GUMS or edg-mkgridmap to cache a list of authorizations from the VOMS-Admin interface, creating a dependency between VOMS client and VOMS-Admin. VOMS-Admin is a large, complex Java web application. Over the last few years, upstream support has tailed off - particularly as OSG has been unable to update to VOMS-Admin version 3. As a result, the maintenance burden has largely fallen on the OSG Software team. Given that VOMS-Admin is deeply tied to X509 security infrastructure - and is maintenance-only from OSG Software - there is no path forward to eliminate the use of X509 certificates in the web browser, a high-priority goal In discussions with the OSG community, we have found very few VOs utilize VOMS-Admin to manage their VO users. Instead, the majority use VOMS-Admin to whitelist a pilot certificate: this can be done without a VOMS-Admin endpoint. OSG's plans to retire VOMS-Admin has three major components: (Sites) Enable distributed validation of VOMS extensions in the VOMS client. (VOs) Migrate VOs that use VOMS only for pilot certificates to direct signing of VOMS proxies. (VOs) Migrate remaining VOs to a central comanage instance for managing user authorizations; maintain a plugin to enable direct callouts from VOMS-Server to comanage for authorization lookups. Site Transition Plans \u00b6 We will release a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions; this verification eludes the need to contact the VOMS-Admin interface for a list of authorizations. In 2015/2016, LCMAPS and GUMS were upgraded so GUMS skips the VOMS-Admin lookup when LCMAPS asserts the validation was performed. Hence, when GUMS sites update clients to the latest (April 2017) LCMAPS and HTCondor-CE releases, the callout to VOMS-Admin is no longer needed. Note : In parallel to the VOMS-Admin transition, OSG Software plans to retire GUMS . There is no need to complete one transition before the other. Sites using edg-mkgridmap will need to use its replacement, lcmaps-plugins-voms (this process is documented here ). VO Transition Plans \u00b6 Based on one-to-one discussions, we believe the majority of VOs only use VOMS-Admin to maintain a list of authorized pilots. For these VOs, we will help convert invocations of voms-proxy-init : voms-proxy-init -voms hcc:/hcc/Role=pilot to an equivalent call to voms-proxy-fake : voms-proxy-fake -hostcert /etc/grid-security/voms/vomscert.pem \\ -hostkey /etc/grid-security/voms/vomskey.pem \\ -fqan /hcc/Role=pilot/Capability=NULL \\ -voms hcc -uri hcc-voms.unl.edu:15000 The latter command would typically be run on the VO's glideinWMS frontend host, requiring the service certificate currently on the VOMS-Admin server to be kept on the frontend host. The frontend's account may also need access to the certificate. Info See this documentation to update your GlideinWMS Frontend to use the new proxy generation command. We plan to transition more complex VOs - those using VOMS-Admin to track membership in a VO - to comanage . It is not clear there are any such VOs that need support from OSG. If there are, a hosted version of comanage is expected to be available in summer 2017 from the CILogon 2.0 project. If you feel your VO is affected, please contact the OSG and we will build a custom timeline. If there are no such VOs, we will not need to adopt comanage for this use case (other uses of comanage are expected to proceed regardless). Timeline \u00b6 April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. Sites begin transition to validating VOMS extensions. Summer 2017 (completed): As necessary, VOs are given access to a hosted comanage instance. March 2017 (completed): First VOs begin to retire VOMS-Admin. May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for VOMS-Admin or GUMS is provided.","title":"VOMS Admin Retirement"},{"location":"policy/voms-admin-retire/#voms-admin-retirement","text":"","title":"VOMS-Admin Retirement"},{"location":"policy/voms-admin-retire/#introduction","text":"This document provides an overview of the planned retirement of support for VOMS-Admin in the OSG Software Stack. Support for the VOMS infrastructure has three major components: VOMS-Admin : A web interface for maintaining the list of authorized users in a VO and their various authorizations (group membership, roles, attributes, etc). VOMS-Server : A TCP service which signs a cryptographic extension on an X509 proxy certificate asserting the authorizations available to the authenticated user. VOMS Client : Software for extracting and validating the signed VOMS extension from an X509 proxy. The validation is meant to be distributed: the VOMS client does not need to contact the VOMS-Admin server. However, OSG has historically used software such as GUMS or edg-mkgridmap to cache a list of authorizations from the VOMS-Admin interface, creating a dependency between VOMS client and VOMS-Admin. VOMS-Admin is a large, complex Java web application. Over the last few years, upstream support has tailed off - particularly as OSG has been unable to update to VOMS-Admin version 3. As a result, the maintenance burden has largely fallen on the OSG Software team. Given that VOMS-Admin is deeply tied to X509 security infrastructure - and is maintenance-only from OSG Software - there is no path forward to eliminate the use of X509 certificates in the web browser, a high-priority goal In discussions with the OSG community, we have found very few VOs utilize VOMS-Admin to manage their VO users. Instead, the majority use VOMS-Admin to whitelist a pilot certificate: this can be done without a VOMS-Admin endpoint. OSG's plans to retire VOMS-Admin has three major components: (Sites) Enable distributed validation of VOMS extensions in the VOMS client. (VOs) Migrate VOs that use VOMS only for pilot certificates to direct signing of VOMS proxies. (VOs) Migrate remaining VOs to a central comanage instance for managing user authorizations; maintain a plugin to enable direct callouts from VOMS-Server to comanage for authorization lookups.","title":"Introduction"},{"location":"policy/voms-admin-retire/#site-transition-plans","text":"We will release a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions; this verification eludes the need to contact the VOMS-Admin interface for a list of authorizations. In 2015/2016, LCMAPS and GUMS were upgraded so GUMS skips the VOMS-Admin lookup when LCMAPS asserts the validation was performed. Hence, when GUMS sites update clients to the latest (April 2017) LCMAPS and HTCondor-CE releases, the callout to VOMS-Admin is no longer needed. Note : In parallel to the VOMS-Admin transition, OSG Software plans to retire GUMS . There is no need to complete one transition before the other. Sites using edg-mkgridmap will need to use its replacement, lcmaps-plugins-voms (this process is documented here ).","title":"Site Transition Plans"},{"location":"policy/voms-admin-retire/#vo-transition-plans","text":"Based on one-to-one discussions, we believe the majority of VOs only use VOMS-Admin to maintain a list of authorized pilots. For these VOs, we will help convert invocations of voms-proxy-init : voms-proxy-init -voms hcc:/hcc/Role=pilot to an equivalent call to voms-proxy-fake : voms-proxy-fake -hostcert /etc/grid-security/voms/vomscert.pem \\ -hostkey /etc/grid-security/voms/vomskey.pem \\ -fqan /hcc/Role=pilot/Capability=NULL \\ -voms hcc -uri hcc-voms.unl.edu:15000 The latter command would typically be run on the VO's glideinWMS frontend host, requiring the service certificate currently on the VOMS-Admin server to be kept on the frontend host. The frontend's account may also need access to the certificate. Info See this documentation to update your GlideinWMS Frontend to use the new proxy generation command. We plan to transition more complex VOs - those using VOMS-Admin to track membership in a VO - to comanage . It is not clear there are any such VOs that need support from OSG. If there are, a hosted version of comanage is expected to be available in summer 2017 from the CILogon 2.0 project. If you feel your VO is affected, please contact the OSG and we will build a custom timeline. If there are no such VOs, we will not need to adopt comanage for this use case (other uses of comanage are expected to proceed regardless).","title":"VO Transition Plans"},{"location":"policy/voms-admin-retire/#timeline","text":"April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. Sites begin transition to validating VOMS extensions. Summer 2017 (completed): As necessary, VOs are given access to a hosted comanage instance. March 2017 (completed): First VOs begin to retire VOMS-Admin. May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for VOMS-Admin or GUMS is provided.","title":"Timeline"},{"location":"projects/sha2-support/","text":"SHA-2 Compliance \u00b6 When a certificate authority signs a certificate, it uses one of several possible hash algorithms. Historically, the most popular algorithms were MD5 (now retired due to security issues) and the SHA-1 family. SHA-1 certificates are being phased out due to perceived weaknesses \u2014 as of February 2017, a practical attack for generating collisions was demonstrated by Google researchers . These days, the preferred hash algorithm family is SHA-2. The certificate authorities (CAs), which issue host and user certificates used widely in the OSG, defaulted to SHA-2-based certificates on 1 October 2013; all sites will need to make sure that their software supports certificates using the SHA-2 algorithms. All supported OSG releases support SHA-2. The table below denotes indicates the minimum releases necessary to support SHA-2 certificates. Component Version In Release Notes BeStMan 2 bestman2-2.3.0-9.osg 3.1.13 SHA-2 support; also see jGlobus, below dCache SRM client dcache-srmclient-2.2.11.1-2.osg 3.1.22 Major update includes SHA-2 support Globus GRAM globus-gram-job-manager-13.45-1.2.osg, globus-gram-job-manager-condor-1.0-13.1.osg, globus-gram-job-manager-pbs-1.6-1.1.osg 3.1.9 Critical bug fixes (not SHA-2 specific) GUMS gums-1.3.18.009-15.2.osg 3.1.13 Switched to jGlobus 2 with SHA-2 support; also see jGlobus, below jGlobus (for BeStMan 2) jglobus-2.0.5-3.osg 3.1.18 Fixed CRL refresh bug (not SHA-2 specific) VOMS voms-2.0.8-1.5.osg 3.1.17 SHA-2 fix for voms-proxy-init If a component does not appear in the above table, it already has SHA-2 support.","title":"SHA-2 Support"},{"location":"projects/sha2-support/#sha-2-compliance","text":"When a certificate authority signs a certificate, it uses one of several possible hash algorithms. Historically, the most popular algorithms were MD5 (now retired due to security issues) and the SHA-1 family. SHA-1 certificates are being phased out due to perceived weaknesses \u2014 as of February 2017, a practical attack for generating collisions was demonstrated by Google researchers . These days, the preferred hash algorithm family is SHA-2. The certificate authorities (CAs), which issue host and user certificates used widely in the OSG, defaulted to SHA-2-based certificates on 1 October 2013; all sites will need to make sure that their software supports certificates using the SHA-2 algorithms. All supported OSG releases support SHA-2. The table below denotes indicates the minimum releases necessary to support SHA-2 certificates. Component Version In Release Notes BeStMan 2 bestman2-2.3.0-9.osg 3.1.13 SHA-2 support; also see jGlobus, below dCache SRM client dcache-srmclient-2.2.11.1-2.osg 3.1.22 Major update includes SHA-2 support Globus GRAM globus-gram-job-manager-13.45-1.2.osg, globus-gram-job-manager-condor-1.0-13.1.osg, globus-gram-job-manager-pbs-1.6-1.1.osg 3.1.9 Critical bug fixes (not SHA-2 specific) GUMS gums-1.3.18.009-15.2.osg 3.1.13 Switched to jGlobus 2 with SHA-2 support; also see jGlobus, below jGlobus (for BeStMan 2) jglobus-2.0.5-3.osg 3.1.18 Fixed CRL refresh bug (not SHA-2 specific) VOMS voms-2.0.8-1.5.osg 3.1.17 SHA-2 fix for voms-proxy-init If a component does not appear in the above table, it already has SHA-2 support.","title":"SHA-2 Compliance"},{"location":"release/acceptance-testing/","text":"Acceptance Testing \u00b6 The OSG Release Team collects and maintains testing procedures for major components in the OSG Sofware Stack. These test should verify that basic functionality of the component works in typically deployed configurations. CVMFS \u00b6 Note This acceptance testing recipe was created when access to a machine with sufficient disk space to make a complete replica of OASIS was not available. Creating a CVMFS Repository Server (Stratum 0) \u00b6 Disable SELinux by setting the following in /etc/selinux/config . SELINUX=disabled Check kernel version. uname -a CVMFS for EL7 requires OverlayFS (as of kernel version 4.2.x). If default kernel is <= 4.2.x, update kernel. root@host # rpm --import <https://www.elrepo.org/RPM-GPG-KEY-elrepo.org> root@host # rpm -Uvh <http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm> root@host # yum install yum-plugin-fastestmirror root@host # yum --enablerepo = elrepo-kernel install kernel-ml Select updated kernel by editing /etc/default/grub . GRUB_DEFAULT=0 and run: root@host # grub2-mkconfig -o /boot/grub2/grub.cfg Reboot system. Check kernel version again and make sure SELinux is disabled. root@host # uname -a root@host # sestatus If kernel >= 4.2 and SELinux is disabled, then update system and install CVMFS server and client packages. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs cvmfs-server Configure web server and start it up. Edit /etc/httpd/conf.d/cvmfs.conf : Listen 8000 KeepAlive On and run: root@host # chkconfig httpd on root@host # service httpd start Make new repository. root@host # cvmfs_server mkfs test.cvmfs-stratum-0.novalocal Run transaction on new repository to enable write access. root@host # cvmfs_server transaction test.cvmfs-stratum-0.novalocal Place some sample code in new repository directory and then publish it. root@host # cd /cvmfs/test.cvmfs-stratum-0.novalocal root@host # vi [ bash \\_ pi.sh ]( %ATTACHURL%/bash_pi.sh ) root@host # chmod +x bash \\_ pi.sh root@host # cvmfs \\_ server publish test.cvmfs-stratum-0.novalocal Check repository status after publication. root@host # cvmfs \\_ server check root@host # cvmfs \\_ server tag root@host # wget -qO- <http://localhost:8000/cvmfs/test.cvmfs-stratum-0.novalocal/.cvmfswhitelist%7Ccat> -v Download a copy of the CVMFS repository's public key e.g., /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub Creating a CVMFS Replica Server (Stratum 1) \u00b6 Repeat steps 1 though 8 in the previous section on \"Creating a CVMFS Repository Server \". However, now also install mod_wsgi . root@host # yum install cvmfs cvmfs-server mod \\_ wsgi Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Add replica of the repository. root@host # cvmfs_server add-replica -o root <http://10.128.3.96:8000/cvmfs/test.cvmfs-stratum-0.novalocal> /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub Make a snapshot of the repository. root@host # cvmfs \\_ server snapshot test.cvmfs-stratum-0.novalocal Creating a CVMFS client \u00b6 Update system and install CVMFS client package. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Edit fuse configuration /etc/fuse.conf . user_allow_other Edit autofs configuration and restart service /etc/auto.master . /cvmfs /etc/auto.cvmfs and run: root@host # service autofs restart Edit cvmfs configuration ( /etc/cvmfs/default.local ) to point to replica server. CVMFS_SERVER_URL=\"http://10.128.3.97:8000/cvmfs/@fqrn@\" CVMFS_REPOSITORIES=\"test.cvmfs-stratum-0.novalocal\" CVMFS_HTTP_PROXY=DIRECT Remove OSG CVMFS configuration file. rm /etc/cvmfs/default.d/60-osg.conf Run CVMFS config probe. cvmfs_config probe test.cvmfs-stratum-0.novalocal Check CVMFS config status. cvmfs_config stat -v test.cvmfs-stratum-0.novalocal Execute sample code published to repository from client. /cvmfs/test.cvmfs-stratum-0.novalocal/bash_pi.sh -b 8 -r 5 -s 10000 Creating an OASIS client \u00b6 Update system and install CVMFS client package. yum update yum install epel-release yum install yum-plugin-priorities rpm -Uvh https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm yum install osg-oasis Verify latest versions of cvmfs, cvmfs-config-osg, and cvmfs-x509-helper have been installed. Edit fuse configuration. vi /etc/fuse.conf user_allow_other Edit cvmfs configuration to point to replica server. vi /etc/cvmfs/default.local CVMFS_REPOSITORIES=\"`echo $((echo oasis.opensciencegrid.org;echo cms.cern.ch;ls /cvmfs)|sort -u)|tr ' ' ,`\" CVMFS_QUOTA_LIMIT=20000 CVMFS_HTTP_PROXY=DIRECT Edit autofs configuration and restart service. vi /etc/auto.master /cvmfs /etc/auto.cvmfs service autofs restart Run CVMFS config probe. cvmfs_config probe Check CVMFS config status. cvmfs_config stat -v oasis.opensciencegrid.org Additional Documentation \u00b6 CERN's CVMFS Documentation OSG's CVMFS Replica Server OSG's CVMFS Client Documentation OSG's OASIS Documentation bash_pi.sh : A bash script that uses a simple Monte Carlo method to estimate the value of Pi Gratia Probe \u00b6 This section documents the testing procedure to test the gratia probes sufficiently tested to be promoted to the osg-testing repository. The test procedure is the same on both SL6 and SL7. install or update the gratia-probe-condor rpm as appropriate On each VM download the gratia-probe-setup.sh script and run it In /etc/gratia/condor/ProbeConfig , verify the following have been changed: change SiteName to something aside from Generic Site change EnableProbe to 1 change CollectorHost , SSLHost , and SSLRegistrationHost to the an invalid host (E.g. test.com) or the localhost Create /var/lib/osg/ and download the attached user-vo-map file and place it in that directory Edit the user-vo-map file and change the account from sthapa to the account you'll be using to submit the condor jobs in the following step Download and submit the attached condor_submit file (note, on the default fermicloud VM, this takes about 3 hours, so you may want to set NUM_CPUS to 50 so that 50 jobs will run at a time) Run /usr/share/gratia/condor/condor_meter Check /var/lib/gratia/tmp/gratiafiles/ for a subdir.condor_... directory and verify that there are 200 xml jobs and the cpus/wall times are appropriate (either PT0S or PT1M). HTCondor-CE Collector (WIP) \u00b6 The CE Collector is a stripped-down version of HTCondor-CE that contains mostly just the collector daemon and configs. It was introduced in htcondor-ce-1.6. The production CE Collectors run at the GOC, but you may want to set up your own for testing. Make 2 VMs with the EPEL/OSG repos installed: one for the collector, and one for the CE Setting Up the Collector \u00b6 Install htcondor-ce-collector Create a file called /etc/condor-ce/config.d/99-local.conf that contains this line: COLLECTOR.ALLOW_ADVERTISE_SCHEDD = $(COLLECTOR.ALLOW_ADVERTISE_SCHEDD), your_htcondor_ce_host.example.net</pre> (with your_htcondor_ce_host replaced by the hostname the HTCondor-CE VM) Run service condor-ce-collector start Setting Up the CE \u00b6 Install osg-htcondor-ce-condor (replace condor with the batch system of your choice) Ensure osg-configure >= 1.0.60-2 is installed Configure your CE using osg-configure You should use the HTCondor-CE Install Docs as a reference, although you can skip several of the steps You can skip setting up Squid: set enabled to True and location to UNAVAILABLE in 01-squid.ini Set htcondor_gateway_enabled to True in 10-gateway.ini You probably don't need GUMS, but if you want it, use the Fermi GUMS server (set gums_host to gums.fnal.gov and authorization_method to xacml in 10-misc.ini) To keep osg-configure from complaining about storage, edit 10-storage.ini : Set se_available to False Set app_dir to /osg/app_dir Set data_dir to /osg/data_dir Do mkdir -p /osg/app_dir/etc; mkdir -p /osg/data_dir; chmod 1777 /osg/app_dir{,/etc} Enable your batch system by setting enabled to True in 20-<batch system>.ini Set up the site info in 40-siteinfo.ini ; in particular, you'll need to set the resource and resource_group settings \\ (you just need to pick a name; I concatenate my login name with the short host name and use that, e.g. matyasfermicloud001). \\ You can also use the following settings: group=OSG-ITB sponsor=local city=Batavia, IL country=US longitude=-88 latitude=41 Edit the file /etc/osg/config.d/30-infoservices.ini and set ce_collectors to the collector host Run osg-configure -dc Start up your batch system Run service condor-ce start The CE will report to the collector host every five minutes. If you want to force it to send now, run condor_ce_reconfig . You should see your CE if you run condor_ce_status -schedd on the collector host. RSV \u00b6 Testing a fresh installation: make sure the yum repositories required by OSG is installed on your host rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el8-release-latest.rpm OR rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm also make sure epel repo is set up. install the rpm yum --enablerepo=osg-testing install rsv edit /etc/osg/config.d/30-rsv.ini file in my case, I don't have a service cert for testing, so I use my own personal cert to create the proxy, but later on the owner of the proxy should be changed to \"rsv\" user that is created during the rpm install. in the config file, for the ce_hosts and gridftp_hosts, put in a test server, as the result from this test will be uploaded to OSG GOC, which may mess up your production service monitoring if you chose a production server for the test. osg-configure -v osg-configure -c /etc/init.d/condor-cron start /etc/init.d/rsv start rsv-control --list rsv-control --version rsv-control --run --all-enabled 11. make sure the results from the above commands look fine. Testing an upgrade installation: make sure to enable the osg-testing repo, and set its priority higher than the other repos yum --enablerepo=osg-testing upgrade rsv* you can use the old 30-rsv.ini file for configuration repeat steps 4)~11) as mentioned in the last section. Slurm \u00b6 This section goes through the steps needed to set up a slurm install on a VM. This is a necessary prerequisite for testing Slurm related components (CE integration, gratia, etc.). Note that the slurm setup used for this uses weak passwords for mysql. It should be sufficient for a quick setup, testing, and then tear down but should not be used without changes if it will be running for any appreciable length of time. Note need to have a VM with 2+ GB of memory Installation and setup \u00b6 Download scripts and config files: cd /tmp/ git clone <https://github.com/sthapa/utilities.git> cd utilities/slurm setup and install slurm components export username='USERNAME' \\# user that jobs will run as export version='14.11.7' \\# slurm version to install (e.g. 16.05.2 or 14.11.7) ./slurm-setup.sh After successful completion, slurm and slurm gratia probes should be setup and enabled. Running a job using slurm \u00b6 Generate test.sh with the following: #/bin/bash echo \"In the directory: `pwd`\" echo \"As the user: `whoami`\" echo \u201cHostname:\" /bin/hostname sleep 60 </pre> run sbatch test.sh the output from the jobs should appear in the current working directory as test.sh.[eo].nnnnn where nnnnn is a job id VO Client \u00b6 This document contains a basic recipe for testing a VO Package release Prerequisites \u00b6 Testing the VO package requires a few components: * X.509 certificate with membership to at least one VO * System with working GUMS installation * System with OSG installation (voms-proxy-init and edg-mkgridmap) Testing voms-proxy-init \u00b6 Login in the system that has voms-proxy-init installed. Make sure that you have the correct vo-client rpms installed and that your X.509 certificate is in your home directory. For each VO that you have membership in, run the following voms-proxy-init -voms [VO] where [VO] is the appropriate VO (e.g. osg, cms, etc.). You should be able to generate a voms-proxy for that VO without errors. XRootD VOMS Testing \u00b6 This section is intended for OSG Software/Release teams to gather information on testing vomsxrd/xrootd-voms-plugin package. Original plugin named vomsxrd , similar to lcmaps that extracts information for authorization within xrootd of a proxy's voms extension. You need an xrootd server installation In the xrootd server yum install the following packages: xrootd xrootd-voms-plugin vo-client In the xrootd client yum install the following packages: xrootd-client voms-clients vo-client In the xrootd server add this lines to file /etc/xrootd/xrootd-clustered.cfg xrootd.seclib /usr/lib64/libXrdSec.so sec.protparm gsi -vomsfun:/usr/lib64/libXrdSecgsiVOMS.so -vomsfunparms:certfmt=raw|vos=cms|dbg -vomsat:2 sec.protocol /usr/lib64 gsi -ca:1 -crl:3 This configuration will only authorize members of VO cms . You can change it to another VO. Make sure fetch-crl has been run otherwise the xrootd service may fail to start. In the xrootd client get a proxy without voms extension or with another VO extension different that the one used in the configuration: user@host $ voms-proxy-init -voms mis Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ........................... Done Contacting voms.opensciencegrid.org:15001 [/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=http/voms.opensciencegrid.org] \"mis\" Done Creating proxy ............................................... Done user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s] Run: [FATAL] Auth failed Now get a proxy with cms extension and run it again: user@host $ voms-proxy-init -voms cms Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ...................................... Done Contacting voms2.cern.ch:15002 [/DC=ch/DC=cern/OU=computers/CN=voms2.cern.ch] \"cms\" Done Creating proxy .......................................... Done Your proxy is valid until Thu Dec 4 22:53:29 2014 user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s] HDFS \u00b6 Hadoop name node installation \u00b6 Use the following script with option 1: #!/bin/bash set -e select NODETYPE in namenode datanode gridftp; do [[ $NODETYPE ]] && break done case $NODETYPE in namenode ) NAMENODE=$HOSTNAME ;; * ) read -p 'hostname for NAMENODE? ' NAMENODE ;; esac echo NODETYPE=$NODETYPE echo NAMENODE=$NAMENODE read -p 'ok? [y/N] ' ok case $ok in y*|Y*) ;; # ok *) exit ;; esac #yum install --enablerepo=osg-minefield osg-se-hadoop-$NODETYPE yum install osg-se-hadoop-$NODETYPE case $NODETYPE in namenode|datanode ) mkdir -p /data/{hadoop,scratch,checkpoint} chown -R hdfs:hdfs /data sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml cp /etc/hadoop/conf.osg/{core,hdfs}-site.xml /etc/hadoop/conf/ touch /etc/hosts_exclude ;; gridftp ) ln -snf conf.osg /etc/hadoop/conf sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml echo \"hadoop-fuse-dfs# /mnt/hadoop fuse server=$NAMENODE,port=9000,rdbuffer=131072,allow_other 0 0\" >> /etc/fstab mkdir /mnt/hadoop mount /mnt/hadoop cp -v /etc/redhat-release /mnt/hadoop/test-file sed -i '/globus_mapping/s/^# *//' /etc/grid-security/gsi-authz.conf sed -i s/yourgums.yourdomain/gums.fnal.gov/ /etc/lcmaps.db mkdir /mnt/hadoop/fnalgrid useradd fnalgrid -g fnalgrid chown fnalgrid:fnalgrid /mnt/hadoop/fnalgrid service globus-gridftp-server start if type -t globus-url-copy >/dev/null; then globus-url-copy file:////bin/bash gsiftp://$HOSTNAME/mnt/hadoop/fnalgrid/first_test else echo globus-url-copy not installed fi ;; esac case $NODETYPE in namenode ) su - hdfs -c \"hadoop namenode -format\" ;; esac service hadoop-hdfs-$NODETYPE start Edit Configuration \u00b6 Edit /etc/hadoop/conf/hdfs-site.xml set dfs.replication to 1 set dfs.replication.min to 1 Hadoop data node installation \u00b6 Run same script as before but with option number 2. GridFTP installation \u00b6 Run same as script but with option number 3. On the name node \u00b6 [root@fermicloud092 ~]# hdfs dfs -ls /test-file Found 1 items -rw-r--r-- 2 root root 0 2014-07-21 15:57 /test-file On the name node \u00b6 [root@]# hadoop fs -mkdir /matyas [root@]# hadoop fs -chown matyas /matyas [root@]# hdfs dfsadmin -setSpaceQuota 123k /matyas user@host $ dd if = /dev/zero of = /tmp/blob bs = 4096 count = 10000 user@host $ kx509 ; voms-proxy-init -noregen -voms fermilab user@host $ globus-url-copy -vb file:///tmp/blob gsiftp:// ` hostname -f ` /mnt/hadoop/matyas XRootD Plugins \u00b6 Install xrootd-server: yum install xrootd-server Install xrootd-plugins yum install xrootd-cmstfc xrootd-hdfs Modify the file /etc/xrootd/xrootd-clustered.cfg to look like this: xrd.port 1094 # The roles this server will play. all.role server all.role manager if xrootd.unl.edu # The known managers all.manager srm.unl.edu:1213 #all.manager xrootd.ultralight.org:1213 # Allow any path to be exported; this is further refined in the authfile. all.export / nostage # Hosts allowed to use this xrootd cluster cms.allow host * ### Standard directives # Simple sites probably don't need to touch these. # Logging verbosity xrootd.trace all -debug ofs.trace all -debug xrd.trace all -debug cms.trace all -debug # Integrate with CMS TFC, placed in /etc/storage.xml oss.namelib /usr/lib64/libXrdCmsTfc.so file:/etc/xrootd/storage.xml?protocol=hadoop xrootd.seclib /usr/lib64/libXrdSec.so xrootd.fslib /usr/lib64/libXrdOfs.so ofs.osslib /usr/lib64/libXrdHdfs.so all.adminpath /var/run/xrootd all.pidpath /var/run/xrootd cms.delay startup 10 cms.fxhold 60s cms.perf int 30s pgm /usr/bin/XrdOlbMonPerf 30 oss.space default_stage /opt/xrootd_cache Create file /etc/xrootd/storage.xml and place this: <storage-mapping> <lfn-to-pfn protocol=\"hadoop\" destination-match=\".*\" path-match=\".*/+tmp2/test-file\" result=\"/test-file\"/> </storage-mapping> For el7 the instrucctions are a little bit different. See: https://jira.opensciencegrid.org/browse/SOFTWARE-2198?focusedCommentId=334667&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-334667 Now from a node do: xrdcp --debug 3 root://yourdatanode.yourdomain:1094//tmp2/test-file . If it is sucessful it would have tested both cmstfc and hdfs plugins","title":"Acceptance Testing"},{"location":"release/acceptance-testing/#acceptance-testing","text":"The OSG Release Team collects and maintains testing procedures for major components in the OSG Sofware Stack. These test should verify that basic functionality of the component works in typically deployed configurations.","title":"Acceptance Testing"},{"location":"release/acceptance-testing/#cvmfs","text":"Note This acceptance testing recipe was created when access to a machine with sufficient disk space to make a complete replica of OASIS was not available.","title":"CVMFS"},{"location":"release/acceptance-testing/#creating-a-cvmfs-repository-server-stratum-0","text":"Disable SELinux by setting the following in /etc/selinux/config . SELINUX=disabled Check kernel version. uname -a CVMFS for EL7 requires OverlayFS (as of kernel version 4.2.x). If default kernel is <= 4.2.x, update kernel. root@host # rpm --import <https://www.elrepo.org/RPM-GPG-KEY-elrepo.org> root@host # rpm -Uvh <http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm> root@host # yum install yum-plugin-fastestmirror root@host # yum --enablerepo = elrepo-kernel install kernel-ml Select updated kernel by editing /etc/default/grub . GRUB_DEFAULT=0 and run: root@host # grub2-mkconfig -o /boot/grub2/grub.cfg Reboot system. Check kernel version again and make sure SELinux is disabled. root@host # uname -a root@host # sestatus If kernel >= 4.2 and SELinux is disabled, then update system and install CVMFS server and client packages. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs cvmfs-server Configure web server and start it up. Edit /etc/httpd/conf.d/cvmfs.conf : Listen 8000 KeepAlive On and run: root@host # chkconfig httpd on root@host # service httpd start Make new repository. root@host # cvmfs_server mkfs test.cvmfs-stratum-0.novalocal Run transaction on new repository to enable write access. root@host # cvmfs_server transaction test.cvmfs-stratum-0.novalocal Place some sample code in new repository directory and then publish it. root@host # cd /cvmfs/test.cvmfs-stratum-0.novalocal root@host # vi [ bash \\_ pi.sh ]( %ATTACHURL%/bash_pi.sh ) root@host # chmod +x bash \\_ pi.sh root@host # cvmfs \\_ server publish test.cvmfs-stratum-0.novalocal Check repository status after publication. root@host # cvmfs \\_ server check root@host # cvmfs \\_ server tag root@host # wget -qO- <http://localhost:8000/cvmfs/test.cvmfs-stratum-0.novalocal/.cvmfswhitelist%7Ccat> -v Download a copy of the CVMFS repository's public key e.g., /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub","title":"Creating a CVMFS Repository Server (Stratum 0)"},{"location":"release/acceptance-testing/#creating-a-cvmfs-replica-server-stratum-1","text":"Repeat steps 1 though 8 in the previous section on \"Creating a CVMFS Repository Server \". However, now also install mod_wsgi . root@host # yum install cvmfs cvmfs-server mod \\_ wsgi Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Add replica of the repository. root@host # cvmfs_server add-replica -o root <http://10.128.3.96:8000/cvmfs/test.cvmfs-stratum-0.novalocal> /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub Make a snapshot of the repository. root@host # cvmfs \\_ server snapshot test.cvmfs-stratum-0.novalocal","title":"Creating a CVMFS Replica Server (Stratum 1)"},{"location":"release/acceptance-testing/#creating-a-cvmfs-client","text":"Update system and install CVMFS client package. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Edit fuse configuration /etc/fuse.conf . user_allow_other Edit autofs configuration and restart service /etc/auto.master . /cvmfs /etc/auto.cvmfs and run: root@host # service autofs restart Edit cvmfs configuration ( /etc/cvmfs/default.local ) to point to replica server. CVMFS_SERVER_URL=\"http://10.128.3.97:8000/cvmfs/@fqrn@\" CVMFS_REPOSITORIES=\"test.cvmfs-stratum-0.novalocal\" CVMFS_HTTP_PROXY=DIRECT Remove OSG CVMFS configuration file. rm /etc/cvmfs/default.d/60-osg.conf Run CVMFS config probe. cvmfs_config probe test.cvmfs-stratum-0.novalocal Check CVMFS config status. cvmfs_config stat -v test.cvmfs-stratum-0.novalocal Execute sample code published to repository from client. /cvmfs/test.cvmfs-stratum-0.novalocal/bash_pi.sh -b 8 -r 5 -s 10000","title":"Creating a CVMFS client"},{"location":"release/acceptance-testing/#creating-an-oasis-client","text":"Update system and install CVMFS client package. yum update yum install epel-release yum install yum-plugin-priorities rpm -Uvh https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm yum install osg-oasis Verify latest versions of cvmfs, cvmfs-config-osg, and cvmfs-x509-helper have been installed. Edit fuse configuration. vi /etc/fuse.conf user_allow_other Edit cvmfs configuration to point to replica server. vi /etc/cvmfs/default.local CVMFS_REPOSITORIES=\"`echo $((echo oasis.opensciencegrid.org;echo cms.cern.ch;ls /cvmfs)|sort -u)|tr ' ' ,`\" CVMFS_QUOTA_LIMIT=20000 CVMFS_HTTP_PROXY=DIRECT Edit autofs configuration and restart service. vi /etc/auto.master /cvmfs /etc/auto.cvmfs service autofs restart Run CVMFS config probe. cvmfs_config probe Check CVMFS config status. cvmfs_config stat -v oasis.opensciencegrid.org","title":"Creating an OASIS client"},{"location":"release/acceptance-testing/#additional-documentation","text":"CERN's CVMFS Documentation OSG's CVMFS Replica Server OSG's CVMFS Client Documentation OSG's OASIS Documentation bash_pi.sh : A bash script that uses a simple Monte Carlo method to estimate the value of Pi","title":"Additional Documentation"},{"location":"release/acceptance-testing/#gratia-probe","text":"This section documents the testing procedure to test the gratia probes sufficiently tested to be promoted to the osg-testing repository. The test procedure is the same on both SL6 and SL7. install or update the gratia-probe-condor rpm as appropriate On each VM download the gratia-probe-setup.sh script and run it In /etc/gratia/condor/ProbeConfig , verify the following have been changed: change SiteName to something aside from Generic Site change EnableProbe to 1 change CollectorHost , SSLHost , and SSLRegistrationHost to the an invalid host (E.g. test.com) or the localhost Create /var/lib/osg/ and download the attached user-vo-map file and place it in that directory Edit the user-vo-map file and change the account from sthapa to the account you'll be using to submit the condor jobs in the following step Download and submit the attached condor_submit file (note, on the default fermicloud VM, this takes about 3 hours, so you may want to set NUM_CPUS to 50 so that 50 jobs will run at a time) Run /usr/share/gratia/condor/condor_meter Check /var/lib/gratia/tmp/gratiafiles/ for a subdir.condor_... directory and verify that there are 200 xml jobs and the cpus/wall times are appropriate (either PT0S or PT1M).","title":"Gratia Probe"},{"location":"release/acceptance-testing/#htcondor-ce-collector-wip","text":"The CE Collector is a stripped-down version of HTCondor-CE that contains mostly just the collector daemon and configs. It was introduced in htcondor-ce-1.6. The production CE Collectors run at the GOC, but you may want to set up your own for testing. Make 2 VMs with the EPEL/OSG repos installed: one for the collector, and one for the CE","title":"HTCondor-CE Collector (WIP)"},{"location":"release/acceptance-testing/#setting-up-the-collector","text":"Install htcondor-ce-collector Create a file called /etc/condor-ce/config.d/99-local.conf that contains this line: COLLECTOR.ALLOW_ADVERTISE_SCHEDD = $(COLLECTOR.ALLOW_ADVERTISE_SCHEDD), your_htcondor_ce_host.example.net</pre> (with your_htcondor_ce_host replaced by the hostname the HTCondor-CE VM) Run service condor-ce-collector start","title":"Setting Up the Collector"},{"location":"release/acceptance-testing/#setting-up-the-ce","text":"Install osg-htcondor-ce-condor (replace condor with the batch system of your choice) Ensure osg-configure >= 1.0.60-2 is installed Configure your CE using osg-configure You should use the HTCondor-CE Install Docs as a reference, although you can skip several of the steps You can skip setting up Squid: set enabled to True and location to UNAVAILABLE in 01-squid.ini Set htcondor_gateway_enabled to True in 10-gateway.ini You probably don't need GUMS, but if you want it, use the Fermi GUMS server (set gums_host to gums.fnal.gov and authorization_method to xacml in 10-misc.ini) To keep osg-configure from complaining about storage, edit 10-storage.ini : Set se_available to False Set app_dir to /osg/app_dir Set data_dir to /osg/data_dir Do mkdir -p /osg/app_dir/etc; mkdir -p /osg/data_dir; chmod 1777 /osg/app_dir{,/etc} Enable your batch system by setting enabled to True in 20-<batch system>.ini Set up the site info in 40-siteinfo.ini ; in particular, you'll need to set the resource and resource_group settings \\ (you just need to pick a name; I concatenate my login name with the short host name and use that, e.g. matyasfermicloud001). \\ You can also use the following settings: group=OSG-ITB sponsor=local city=Batavia, IL country=US longitude=-88 latitude=41 Edit the file /etc/osg/config.d/30-infoservices.ini and set ce_collectors to the collector host Run osg-configure -dc Start up your batch system Run service condor-ce start The CE will report to the collector host every five minutes. If you want to force it to send now, run condor_ce_reconfig . You should see your CE if you run condor_ce_status -schedd on the collector host.","title":"Setting Up the CE"},{"location":"release/acceptance-testing/#rsv","text":"Testing a fresh installation: make sure the yum repositories required by OSG is installed on your host rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el8-release-latest.rpm OR rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm also make sure epel repo is set up. install the rpm yum --enablerepo=osg-testing install rsv edit /etc/osg/config.d/30-rsv.ini file in my case, I don't have a service cert for testing, so I use my own personal cert to create the proxy, but later on the owner of the proxy should be changed to \"rsv\" user that is created during the rpm install. in the config file, for the ce_hosts and gridftp_hosts, put in a test server, as the result from this test will be uploaded to OSG GOC, which may mess up your production service monitoring if you chose a production server for the test. osg-configure -v osg-configure -c /etc/init.d/condor-cron start /etc/init.d/rsv start rsv-control --list rsv-control --version rsv-control --run --all-enabled 11. make sure the results from the above commands look fine. Testing an upgrade installation: make sure to enable the osg-testing repo, and set its priority higher than the other repos yum --enablerepo=osg-testing upgrade rsv* you can use the old 30-rsv.ini file for configuration repeat steps 4)~11) as mentioned in the last section.","title":"RSV"},{"location":"release/acceptance-testing/#slurm","text":"This section goes through the steps needed to set up a slurm install on a VM. This is a necessary prerequisite for testing Slurm related components (CE integration, gratia, etc.). Note that the slurm setup used for this uses weak passwords for mysql. It should be sufficient for a quick setup, testing, and then tear down but should not be used without changes if it will be running for any appreciable length of time. Note need to have a VM with 2+ GB of memory","title":"Slurm"},{"location":"release/acceptance-testing/#installation-and-setup","text":"Download scripts and config files: cd /tmp/ git clone <https://github.com/sthapa/utilities.git> cd utilities/slurm setup and install slurm components export username='USERNAME' \\# user that jobs will run as export version='14.11.7' \\# slurm version to install (e.g. 16.05.2 or 14.11.7) ./slurm-setup.sh After successful completion, slurm and slurm gratia probes should be setup and enabled.","title":"Installation and setup"},{"location":"release/acceptance-testing/#running-a-job-using-slurm","text":"Generate test.sh with the following: #/bin/bash echo \"In the directory: `pwd`\" echo \"As the user: `whoami`\" echo \u201cHostname:\" /bin/hostname sleep 60 </pre> run sbatch test.sh the output from the jobs should appear in the current working directory as test.sh.[eo].nnnnn where nnnnn is a job id","title":"Running a job using slurm"},{"location":"release/acceptance-testing/#vo-client","text":"This document contains a basic recipe for testing a VO Package release","title":"VO Client"},{"location":"release/acceptance-testing/#prerequisites","text":"Testing the VO package requires a few components: * X.509 certificate with membership to at least one VO * System with working GUMS installation * System with OSG installation (voms-proxy-init and edg-mkgridmap)","title":"Prerequisites"},{"location":"release/acceptance-testing/#testing-voms-proxy-init","text":"Login in the system that has voms-proxy-init installed. Make sure that you have the correct vo-client rpms installed and that your X.509 certificate is in your home directory. For each VO that you have membership in, run the following voms-proxy-init -voms [VO] where [VO] is the appropriate VO (e.g. osg, cms, etc.). You should be able to generate a voms-proxy for that VO without errors.","title":"Testing voms-proxy-init"},{"location":"release/acceptance-testing/#xrootd-voms-testing","text":"This section is intended for OSG Software/Release teams to gather information on testing vomsxrd/xrootd-voms-plugin package. Original plugin named vomsxrd , similar to lcmaps that extracts information for authorization within xrootd of a proxy's voms extension. You need an xrootd server installation In the xrootd server yum install the following packages: xrootd xrootd-voms-plugin vo-client In the xrootd client yum install the following packages: xrootd-client voms-clients vo-client In the xrootd server add this lines to file /etc/xrootd/xrootd-clustered.cfg xrootd.seclib /usr/lib64/libXrdSec.so sec.protparm gsi -vomsfun:/usr/lib64/libXrdSecgsiVOMS.so -vomsfunparms:certfmt=raw|vos=cms|dbg -vomsat:2 sec.protocol /usr/lib64 gsi -ca:1 -crl:3 This configuration will only authorize members of VO cms . You can change it to another VO. Make sure fetch-crl has been run otherwise the xrootd service may fail to start. In the xrootd client get a proxy without voms extension or with another VO extension different that the one used in the configuration: user@host $ voms-proxy-init -voms mis Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ........................... Done Contacting voms.opensciencegrid.org:15001 [/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=http/voms.opensciencegrid.org] \"mis\" Done Creating proxy ............................................... Done user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s] Run: [FATAL] Auth failed Now get a proxy with cms extension and run it again: user@host $ voms-proxy-init -voms cms Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ...................................... Done Contacting voms2.cern.ch:15002 [/DC=ch/DC=cern/OU=computers/CN=voms2.cern.ch] \"cms\" Done Creating proxy .......................................... Done Your proxy is valid until Thu Dec 4 22:53:29 2014 user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s]","title":"XRootD VOMS Testing"},{"location":"release/acceptance-testing/#hdfs","text":"","title":"HDFS"},{"location":"release/acceptance-testing/#hadoop-name-node-installation","text":"Use the following script with option 1: #!/bin/bash set -e select NODETYPE in namenode datanode gridftp; do [[ $NODETYPE ]] && break done case $NODETYPE in namenode ) NAMENODE=$HOSTNAME ;; * ) read -p 'hostname for NAMENODE? ' NAMENODE ;; esac echo NODETYPE=$NODETYPE echo NAMENODE=$NAMENODE read -p 'ok? [y/N] ' ok case $ok in y*|Y*) ;; # ok *) exit ;; esac #yum install --enablerepo=osg-minefield osg-se-hadoop-$NODETYPE yum install osg-se-hadoop-$NODETYPE case $NODETYPE in namenode|datanode ) mkdir -p /data/{hadoop,scratch,checkpoint} chown -R hdfs:hdfs /data sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml cp /etc/hadoop/conf.osg/{core,hdfs}-site.xml /etc/hadoop/conf/ touch /etc/hosts_exclude ;; gridftp ) ln -snf conf.osg /etc/hadoop/conf sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml echo \"hadoop-fuse-dfs# /mnt/hadoop fuse server=$NAMENODE,port=9000,rdbuffer=131072,allow_other 0 0\" >> /etc/fstab mkdir /mnt/hadoop mount /mnt/hadoop cp -v /etc/redhat-release /mnt/hadoop/test-file sed -i '/globus_mapping/s/^# *//' /etc/grid-security/gsi-authz.conf sed -i s/yourgums.yourdomain/gums.fnal.gov/ /etc/lcmaps.db mkdir /mnt/hadoop/fnalgrid useradd fnalgrid -g fnalgrid chown fnalgrid:fnalgrid /mnt/hadoop/fnalgrid service globus-gridftp-server start if type -t globus-url-copy >/dev/null; then globus-url-copy file:////bin/bash gsiftp://$HOSTNAME/mnt/hadoop/fnalgrid/first_test else echo globus-url-copy not installed fi ;; esac case $NODETYPE in namenode ) su - hdfs -c \"hadoop namenode -format\" ;; esac service hadoop-hdfs-$NODETYPE start","title":"Hadoop name node installation"},{"location":"release/acceptance-testing/#edit-configuration","text":"Edit /etc/hadoop/conf/hdfs-site.xml set dfs.replication to 1 set dfs.replication.min to 1","title":"Edit Configuration"},{"location":"release/acceptance-testing/#hadoop-data-node-installation","text":"Run same script as before but with option number 2.","title":"Hadoop data node installation"},{"location":"release/acceptance-testing/#gridftp-installation","text":"Run same as script but with option number 3.","title":"GridFTP installation"},{"location":"release/acceptance-testing/#on-the-name-node","text":"[root@fermicloud092 ~]# hdfs dfs -ls /test-file Found 1 items -rw-r--r-- 2 root root 0 2014-07-21 15:57 /test-file","title":"On the name node"},{"location":"release/acceptance-testing/#on-the-name-node_1","text":"[root@]# hadoop fs -mkdir /matyas [root@]# hadoop fs -chown matyas /matyas [root@]# hdfs dfsadmin -setSpaceQuota 123k /matyas user@host $ dd if = /dev/zero of = /tmp/blob bs = 4096 count = 10000 user@host $ kx509 ; voms-proxy-init -noregen -voms fermilab user@host $ globus-url-copy -vb file:///tmp/blob gsiftp:// ` hostname -f ` /mnt/hadoop/matyas","title":"On the name node"},{"location":"release/acceptance-testing/#xrootd-plugins","text":"Install xrootd-server: yum install xrootd-server Install xrootd-plugins yum install xrootd-cmstfc xrootd-hdfs Modify the file /etc/xrootd/xrootd-clustered.cfg to look like this: xrd.port 1094 # The roles this server will play. all.role server all.role manager if xrootd.unl.edu # The known managers all.manager srm.unl.edu:1213 #all.manager xrootd.ultralight.org:1213 # Allow any path to be exported; this is further refined in the authfile. all.export / nostage # Hosts allowed to use this xrootd cluster cms.allow host * ### Standard directives # Simple sites probably don't need to touch these. # Logging verbosity xrootd.trace all -debug ofs.trace all -debug xrd.trace all -debug cms.trace all -debug # Integrate with CMS TFC, placed in /etc/storage.xml oss.namelib /usr/lib64/libXrdCmsTfc.so file:/etc/xrootd/storage.xml?protocol=hadoop xrootd.seclib /usr/lib64/libXrdSec.so xrootd.fslib /usr/lib64/libXrdOfs.so ofs.osslib /usr/lib64/libXrdHdfs.so all.adminpath /var/run/xrootd all.pidpath /var/run/xrootd cms.delay startup 10 cms.fxhold 60s cms.perf int 30s pgm /usr/bin/XrdOlbMonPerf 30 oss.space default_stage /opt/xrootd_cache Create file /etc/xrootd/storage.xml and place this: <storage-mapping> <lfn-to-pfn protocol=\"hadoop\" destination-match=\".*\" path-match=\".*/+tmp2/test-file\" result=\"/test-file\"/> </storage-mapping> For el7 the instrucctions are a little bit different. See: https://jira.opensciencegrid.org/browse/SOFTWARE-2198?focusedCommentId=334667&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-334667 Now from a node do: xrdcp --debug 3 root://yourdatanode.yourdomain:1094//tmp2/test-file . If it is sucessful it would have tested both cmstfc and hdfs plugins","title":"XRootD Plugins"},{"location":"release/announce-rft-packages/","text":"Ready for Testing Announcements \u00b6 Per our community testing policy , we must send weekly digests of packages that are ready for testing. Create the Announcement \u00b6 Step 1: Identify the packages that are \"Ready for Testing\" \u00b6 Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = \"<VERSION(S)>\" git clone https://github.com/opensciencegrid/release-tools.git cd release-tools 0 -generate-pkg-list $VERSIONS Note In the future, will we have a command the produces the package list sorted according to release series and importance. Step 2: Populate the Announcement Template \u00b6 Find the software components that the packages in the list correspond to. For example, htcondor-ce-4.4.0-1.osg35.el7 should be listed as \"HTCondor-CE 4.4.0\". Place software components into the appropriate section depending on release series and importance of the software. The major software components are listed in the community testing policy . Omit any software that does not need to tested by the community such osg-version and internal tools. Step 3: Send the \"Ready for Testing\" Announcement \u00b6 The announcement goes to: osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov OIM administrative contacts Use the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject 'OSG Packages Available for Testing' \\ --recipients \"osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative Announcement Template \u00b6 The following email template is filled out to announce that packages are ready for testing. Text between <ANGLE BRACKETS> should be replaced and sections without packages to be tested should be omitted. Omit release numbers unless they are relevant (e.g. for a packaging-only change). Each major component should have a line about what's new. Several packages are available for testing for tentative release next week. OSG 3.5 Only: - Major Components* - <Major Component Name and Version (NV)> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> Both OSG 3.5 and 3.4: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> OSG 3.4 Only: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> To install any of these packages, run the following command: # yum install --enablerepo=osg-testing <PACKAGE NAME> Please test this software and send positive or negative feedback to software-discuss@osg-htc.org. Be sure to include details describing your testing platform, e.g. OSG 3.4 vs 3.5, EL6 vs EL7! If you any questions, you can always contact us at help@osg-htc.org. JIRA Ticket Summary: https://opensciencegrid.atlassian.net/issues/?filter=12355 Sincerely, The OSG Software & Release Team * As described by our Community Software Testing Policy, (https://osg-htc.org/technology/policy/community-testing/) major components of the OSG Software Stack need positive feedback and the approval of the release manager before they can be released.","title":"Ready for Testing Announcements"},{"location":"release/announce-rft-packages/#ready-for-testing-announcements","text":"Per our community testing policy , we must send weekly digests of packages that are ready for testing.","title":"Ready for Testing Announcements"},{"location":"release/announce-rft-packages/#create-the-announcement","text":"","title":"Create the Announcement"},{"location":"release/announce-rft-packages/#step-1-identify-the-packages-that-are-ready-for-testing","text":"Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = \"<VERSION(S)>\" git clone https://github.com/opensciencegrid/release-tools.git cd release-tools 0 -generate-pkg-list $VERSIONS Note In the future, will we have a command the produces the package list sorted according to release series and importance.","title":"Step 1: Identify the packages that are \"Ready for Testing\""},{"location":"release/announce-rft-packages/#step-2-populate-the-announcement-template","text":"Find the software components that the packages in the list correspond to. For example, htcondor-ce-4.4.0-1.osg35.el7 should be listed as \"HTCondor-CE 4.4.0\". Place software components into the appropriate section depending on release series and importance of the software. The major software components are listed in the community testing policy . Omit any software that does not need to tested by the community such osg-version and internal tools.","title":"Step 2: Populate the Announcement Template"},{"location":"release/announce-rft-packages/#step-3-send-the-ready-for-testing-announcement","text":"The announcement goes to: osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov OIM administrative contacts Use the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject 'OSG Packages Available for Testing' \\ --recipients \"osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative","title":"Step 3: Send the \"Ready for Testing\" Announcement"},{"location":"release/announce-rft-packages/#announcement-template","text":"The following email template is filled out to announce that packages are ready for testing. Text between <ANGLE BRACKETS> should be replaced and sections without packages to be tested should be omitted. Omit release numbers unless they are relevant (e.g. for a packaging-only change). Each major component should have a line about what's new. Several packages are available for testing for tentative release next week. OSG 3.5 Only: - Major Components* - <Major Component Name and Version (NV)> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> Both OSG 3.5 and 3.4: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> OSG 3.4 Only: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> To install any of these packages, run the following command: # yum install --enablerepo=osg-testing <PACKAGE NAME> Please test this software and send positive or negative feedback to software-discuss@osg-htc.org. Be sure to include details describing your testing platform, e.g. OSG 3.4 vs 3.5, EL6 vs EL7! If you any questions, you can always contact us at help@osg-htc.org. JIRA Ticket Summary: https://opensciencegrid.atlassian.net/issues/?filter=12355 Sincerely, The OSG Software & Release Team * As described by our Community Software Testing Policy, (https://osg-htc.org/technology/policy/community-testing/) major components of the OSG Software Stack need positive feedback and the approval of the release manager before they can be released.","title":"Announcement Template"},{"location":"release/cut-sw-release/","text":"How to Cut a Software Release \u00b6 This document details the process for releasing new OSG Release version(s). This document does NOT discuss the policy for deciding what goes into a release, which can be found here . Due to the length of time that this process takes, it is recommended to do the release over two or more days to allow for errors to be corrected and tests to be run. Requirements \u00b6 UW netID registered with OSG's koji with build and release team privileges On laptop: kinit netid@AD.WISC.EDU An account on dumbo and UW CS to access UW's AFS On dumbo: kinit user@CS.WISC.EDU; aklog release-tools scripts in your PATH ( GitHub ) osg-build scripts in your PATH (installed via OSG yum repos or source ) Pick the Version Number \u00b6 The rest of this document makes references to <VERSION(S)> and <NON-UPCOMING VERSIONS(S)> , which refer to a space-delimited list of a date string plus the OSG version(s) and that same list minus the upcoming versions (e.g. 231130 3.6 3.6-upcoming 23 23-upcoming and 231130 3.6 23 ). Generally, the first number is the release date encoded as yymmdd . Also this document make references to <FULL VERSION(S)> , which refer to a space-delimited list of version numbers (e.g. 3.6.231130 23.231130 ). If you are unsure about either the version or revision, please consult the release manager. Day 0: Generate Preliminary Release List \u00b6 The release manager often needs a tentative list of packages to be released. This is done by finding the package differences between osg-testing and the current release. Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = '<VERSION(S)>' # laptop git clone https://github.com/opensciencegrid/release-tools.git cd release-tools ./0-generate-pkg-list $VERSIONS Day 1: Verify Pre-Release and Generate Tarballs \u00b6 This section is to be performed 1-2 days before the release (as designated by the release manager) to perform last checks of the release and create the client tarballs. Step 1: Verify Pre-Release \u00b6 Compare the list of packages already in pre-release to the final list for the release put together by the OSG Release Coordinator (who should have updated release-list in git). To do this, run the 1-verify-prerelease script from git: VERSIONS = '<VERSION(S)>' # laptop ./1-verify-prerelease $VERSIONS If there are any discrepancies, consult the release manager. You may have to tag or untag packages with the osg-koji tool. Step 2: Test Pre-Release in VM Universe \u00b6 To test pre-release, you will be kicking off a manual VM universe test run from osg-sw-submit.chtc.wisc.edu . Ensure that you meet the pre-requisites for submitting VM universe test runs Prepare the test suite by running: osg-run-tests -P 'Testing OSG pre-release' cd into the directory specified in the output of the previous command Submit the DAG: ./master-run.sh Note Test upcoming even though nothing will be released into upcoming. It is possible that a blahp (or some other) update in 3.X could affect upcoming. Note If there are failures, consult the release-manager before proceeding. Step 3: Regenerate the build repositories \u00b6 To avoid 404 errors when retrieving packages, it's necessary to regenerate the build repositories. Run the following script from a machine with your koji-registered user certificate: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # laptop ./1-regen-repos $NON_UPCOMING_VERSIONS Step 4: Create the client tarballs \u00b6 Create the OSG client tarballs on dumbo using the relevant script from git: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./docker-make-client-tarball --version $ver --all done The tarballs are found in the tarball-client directory. Step 5: Briefly test the client tarballs \u00b6 Test the OSG client tarballs in Docker containers on dumbo using the relevant release-tools script: As an unprivileged user , run the script: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./1-verify-tarballs $NON_UPCOMING_VERSIONS If you have time, try some of the binaries, such as grid-proxy-init. Step 6: Wait \u00b6 Wait for clearance. The OSG Release Coordinator (in consultation with the Software Team and any testers) need to sign off on the update before it is released. If you are releasing things over two days, this is a good place to stop for the day. Day 2: Pushing the Release \u00b6 Step 1: Upload the tarballs to AFS \u00b6 On dumbo , upload the tarballs to AFS. (This step moved to release day, since repo.opensciencegrid.org tarballs are automatically updated hourly from the VDT web site served out of AFS.) NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./2-upload-tarballs-to-afs $NON_UPCOMING_VERSIONS Step 2: Push from pre-release to release \u00b6 This script moves the packages into release, clones releases into new version-specific release repos, locks the repos and regenerates them. VERSIONS = '<VERSION(S)>' # laptop 2 -push-release $VERSIONS Step 3: Update the Release Information \u00b6 This script updates the release information in AFS. VERSIONS = '<VERSION(S)>' # laptop 2 -update-info $VERSIONS *.txt files are created and it should be verified that they've been moved to /p/vdt/public/html/release-info/ on UW's AFS. Step 4: Rebuild the Docker software base \u00b6 Go to the build-docker-image workflow page of the opensciencegrid/docker-software-base : https://github.com/opensciencegrid/docker-software-base/actions/workflows/build-container.yml Click the Run Workflow button, select the master branch, and click Run workflow . Step 5: Install the tarballs into OASIS \u00b6 Note You must be an OASIS manager of the mis VO to do these steps. Known managers as of 2014-07-22: Mat, Tim C, Tim T, Brian L. Get the uploader script from Git and run it with osgrun from the UW AFS install of the tarball client you made earlier. On a UW CSL machine: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone --depth 1 https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./upload-tarballs-to-oasis $ver done The script will automatically ssh you to oasis-login.opensciencegrid.org and give you instructions to complete the process. Step 6: Update the Docker WN client \u00b6 The GitHub repository at opensciencegrid/docker-osg-wn controls the contents and tags pushed for the opensciencegrid/osg-wn container image. Navigate to the build/push workflow Click the Run workflow button and select the master branch Verify that all builds succeed Step 7: Verify the CA certificates update \u00b6 If this release contains either the osg-ca-certs package, verify that the CA web site has been updated. Wait for the CA certificates to be updated. It may take a while for the updates to reach the mirror used to update the web site. The repository is checked hourly for updated CA certificates. Once the web page is updated, run the following command to update the CA certificates in the tarball installation and verify that the version of the CA certificates match the version that was promoted to release. # moria.cs.wisc.edu /p/vdt/workspace/tarball-client/current/amd64_rhel7/osgrun osg-update-data Step 8: Merge any pending documentation \u00b6 For each documentation ticket in this release, merge the pull requests mentioned in the description or comments. Step 9: Update News \u00b6 Make a new entry in the News section of the release series page. For the list of changes, make an entry for each package that contains short descriptive text that would inform a system administrator whether or not this change is of concern to them. Also, link in any release announcement web page that is available for the software. Look a prior releases of the same software for hints on where to find such a page. Examine the known issues and remove any that were resolved with this release. Of course, add any new ones that have come up. Spell check the news. Locally serve up the web pages and ensure that the formatting looks good and the links work as expected. docker run --rm -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material:7.1.0 Make a pull request, get it approved, and merged. When the web page is available, you can announce the release. Step 10: Announce the release \u00b6 The following instructions are meant for the release manager (or interim release manager). If you are not the release manager, let the release manager know that they can announce the release. The release manager writes the a release announcement for each version and sends it out. The announcement should mention a handful of the most important updates. Due to downstream formatting issues, each major change should end at column 76 or earlier. Here is a sample, replace <BRACKETED TEXT> with the appropriate values: Subject: Announcing OSG Software version <VERSION> We are pleased to announce OSG Software version <VERSION>! Changes to OSG <VERSION> include: - Major Change 1 - Major Change 2 - Major Change 3 Release notes and pointers to more documentation can be found at: https://osg-htc.org/docs/release/osg-36/#latest-news The OSG Docker images on Docker Hub (https://hub.docker.com/u/opensciencegrid/) have been updated to contain the new software. Need help? Let us know: http://www.osg-htc.org/docs/common/help/ We welcome feedback on this release! The release manager uses the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject '<EMAIL SUBJECT>' \\ --recipients \"osg-general@opensciencegrid.org osg-operations@opensciencegrid.org osg-sites@opensciencegrid.org software-discuss@osg-htc.org site-announce@opensciencegrid.org\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative Replacing <EMAIL SUBJECT> with an appropriate subject for your announcement and <PATH TO MESSAGE FILE> with the path to the file containing your message in plain text. The release manager releases the tickets marked 'Ready for Release' in the release's JIRA filter using the 'bulk change' function.","title":"How to Cut a Release"},{"location":"release/cut-sw-release/#how-to-cut-a-software-release","text":"This document details the process for releasing new OSG Release version(s). This document does NOT discuss the policy for deciding what goes into a release, which can be found here . Due to the length of time that this process takes, it is recommended to do the release over two or more days to allow for errors to be corrected and tests to be run.","title":"How to Cut a Software Release"},{"location":"release/cut-sw-release/#requirements","text":"UW netID registered with OSG's koji with build and release team privileges On laptop: kinit netid@AD.WISC.EDU An account on dumbo and UW CS to access UW's AFS On dumbo: kinit user@CS.WISC.EDU; aklog release-tools scripts in your PATH ( GitHub ) osg-build scripts in your PATH (installed via OSG yum repos or source )","title":"Requirements"},{"location":"release/cut-sw-release/#pick-the-version-number","text":"The rest of this document makes references to <VERSION(S)> and <NON-UPCOMING VERSIONS(S)> , which refer to a space-delimited list of a date string plus the OSG version(s) and that same list minus the upcoming versions (e.g. 231130 3.6 3.6-upcoming 23 23-upcoming and 231130 3.6 23 ). Generally, the first number is the release date encoded as yymmdd . Also this document make references to <FULL VERSION(S)> , which refer to a space-delimited list of version numbers (e.g. 3.6.231130 23.231130 ). If you are unsure about either the version or revision, please consult the release manager.","title":"Pick the Version Number"},{"location":"release/cut-sw-release/#day-0-generate-preliminary-release-list","text":"The release manager often needs a tentative list of packages to be released. This is done by finding the package differences between osg-testing and the current release. Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = '<VERSION(S)>' # laptop git clone https://github.com/opensciencegrid/release-tools.git cd release-tools ./0-generate-pkg-list $VERSIONS","title":"Day 0: Generate Preliminary Release List"},{"location":"release/cut-sw-release/#day-1-verify-pre-release-and-generate-tarballs","text":"This section is to be performed 1-2 days before the release (as designated by the release manager) to perform last checks of the release and create the client tarballs.","title":"Day 1: Verify Pre-Release and Generate Tarballs"},{"location":"release/cut-sw-release/#step-1-verify-pre-release","text":"Compare the list of packages already in pre-release to the final list for the release put together by the OSG Release Coordinator (who should have updated release-list in git). To do this, run the 1-verify-prerelease script from git: VERSIONS = '<VERSION(S)>' # laptop ./1-verify-prerelease $VERSIONS If there are any discrepancies, consult the release manager. You may have to tag or untag packages with the osg-koji tool.","title":"Step 1: Verify Pre-Release"},{"location":"release/cut-sw-release/#step-2-test-pre-release-in-vm-universe","text":"To test pre-release, you will be kicking off a manual VM universe test run from osg-sw-submit.chtc.wisc.edu . Ensure that you meet the pre-requisites for submitting VM universe test runs Prepare the test suite by running: osg-run-tests -P 'Testing OSG pre-release' cd into the directory specified in the output of the previous command Submit the DAG: ./master-run.sh Note Test upcoming even though nothing will be released into upcoming. It is possible that a blahp (or some other) update in 3.X could affect upcoming. Note If there are failures, consult the release-manager before proceeding.","title":"Step 2: Test Pre-Release in VM Universe"},{"location":"release/cut-sw-release/#step-3-regenerate-the-build-repositories","text":"To avoid 404 errors when retrieving packages, it's necessary to regenerate the build repositories. Run the following script from a machine with your koji-registered user certificate: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # laptop ./1-regen-repos $NON_UPCOMING_VERSIONS","title":"Step 3: Regenerate the build repositories"},{"location":"release/cut-sw-release/#step-4-create-the-client-tarballs","text":"Create the OSG client tarballs on dumbo using the relevant script from git: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./docker-make-client-tarball --version $ver --all done The tarballs are found in the tarball-client directory.","title":"Step 4: Create the client tarballs"},{"location":"release/cut-sw-release/#step-5-briefly-test-the-client-tarballs","text":"Test the OSG client tarballs in Docker containers on dumbo using the relevant release-tools script: As an unprivileged user , run the script: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./1-verify-tarballs $NON_UPCOMING_VERSIONS If you have time, try some of the binaries, such as grid-proxy-init.","title":"Step 5: Briefly test the client tarballs"},{"location":"release/cut-sw-release/#step-6-wait","text":"Wait for clearance. The OSG Release Coordinator (in consultation with the Software Team and any testers) need to sign off on the update before it is released. If you are releasing things over two days, this is a good place to stop for the day.","title":"Step 6: Wait"},{"location":"release/cut-sw-release/#day-2-pushing-the-release","text":"","title":"Day 2: Pushing the Release"},{"location":"release/cut-sw-release/#step-1-upload-the-tarballs-to-afs","text":"On dumbo , upload the tarballs to AFS. (This step moved to release day, since repo.opensciencegrid.org tarballs are automatically updated hourly from the VDT web site served out of AFS.) NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./2-upload-tarballs-to-afs $NON_UPCOMING_VERSIONS","title":"Step 1: Upload the tarballs to AFS"},{"location":"release/cut-sw-release/#step-2-push-from-pre-release-to-release","text":"This script moves the packages into release, clones releases into new version-specific release repos, locks the repos and regenerates them. VERSIONS = '<VERSION(S)>' # laptop 2 -push-release $VERSIONS","title":"Step 2: Push from pre-release to release"},{"location":"release/cut-sw-release/#step-3-update-the-release-information","text":"This script updates the release information in AFS. VERSIONS = '<VERSION(S)>' # laptop 2 -update-info $VERSIONS *.txt files are created and it should be verified that they've been moved to /p/vdt/public/html/release-info/ on UW's AFS.","title":"Step 3: Update the Release Information"},{"location":"release/cut-sw-release/#step-4-rebuild-the-docker-software-base","text":"Go to the build-docker-image workflow page of the opensciencegrid/docker-software-base : https://github.com/opensciencegrid/docker-software-base/actions/workflows/build-container.yml Click the Run Workflow button, select the master branch, and click Run workflow .","title":"Step 4: Rebuild the Docker software base"},{"location":"release/cut-sw-release/#step-5-install-the-tarballs-into-oasis","text":"Note You must be an OASIS manager of the mis VO to do these steps. Known managers as of 2014-07-22: Mat, Tim C, Tim T, Brian L. Get the uploader script from Git and run it with osgrun from the UW AFS install of the tarball client you made earlier. On a UW CSL machine: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone --depth 1 https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./upload-tarballs-to-oasis $ver done The script will automatically ssh you to oasis-login.opensciencegrid.org and give you instructions to complete the process.","title":"Step 5: Install the tarballs into OASIS"},{"location":"release/cut-sw-release/#step-6-update-the-docker-wn-client","text":"The GitHub repository at opensciencegrid/docker-osg-wn controls the contents and tags pushed for the opensciencegrid/osg-wn container image. Navigate to the build/push workflow Click the Run workflow button and select the master branch Verify that all builds succeed","title":"Step 6: Update the Docker WN client"},{"location":"release/cut-sw-release/#step-7-verify-the-ca-certificates-update","text":"If this release contains either the osg-ca-certs package, verify that the CA web site has been updated. Wait for the CA certificates to be updated. It may take a while for the updates to reach the mirror used to update the web site. The repository is checked hourly for updated CA certificates. Once the web page is updated, run the following command to update the CA certificates in the tarball installation and verify that the version of the CA certificates match the version that was promoted to release. # moria.cs.wisc.edu /p/vdt/workspace/tarball-client/current/amd64_rhel7/osgrun osg-update-data","title":"Step 7: Verify the CA certificates update"},{"location":"release/cut-sw-release/#step-8-merge-any-pending-documentation","text":"For each documentation ticket in this release, merge the pull requests mentioned in the description or comments.","title":"Step 8: Merge any pending documentation"},{"location":"release/cut-sw-release/#step-9-update-news","text":"Make a new entry in the News section of the release series page. For the list of changes, make an entry for each package that contains short descriptive text that would inform a system administrator whether or not this change is of concern to them. Also, link in any release announcement web page that is available for the software. Look a prior releases of the same software for hints on where to find such a page. Examine the known issues and remove any that were resolved with this release. Of course, add any new ones that have come up. Spell check the news. Locally serve up the web pages and ensure that the formatting looks good and the links work as expected. docker run --rm -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material:7.1.0 Make a pull request, get it approved, and merged. When the web page is available, you can announce the release.","title":"Step 9: Update News"},{"location":"release/cut-sw-release/#step-10-announce-the-release","text":"The following instructions are meant for the release manager (or interim release manager). If you are not the release manager, let the release manager know that they can announce the release. The release manager writes the a release announcement for each version and sends it out. The announcement should mention a handful of the most important updates. Due to downstream formatting issues, each major change should end at column 76 or earlier. Here is a sample, replace <BRACKETED TEXT> with the appropriate values: Subject: Announcing OSG Software version <VERSION> We are pleased to announce OSG Software version <VERSION>! Changes to OSG <VERSION> include: - Major Change 1 - Major Change 2 - Major Change 3 Release notes and pointers to more documentation can be found at: https://osg-htc.org/docs/release/osg-36/#latest-news The OSG Docker images on Docker Hub (https://hub.docker.com/u/opensciencegrid/) have been updated to contain the new software. Need help? Let us know: http://www.osg-htc.org/docs/common/help/ We welcome feedback on this release! The release manager uses the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject '<EMAIL SUBJECT>' \\ --recipients \"osg-general@opensciencegrid.org osg-operations@opensciencegrid.org osg-sites@opensciencegrid.org software-discuss@osg-htc.org site-announce@opensciencegrid.org\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative Replacing <EMAIL SUBJECT> with an appropriate subject for your announcement and <PATH TO MESSAGE FILE> with the path to the file containing your message in plain text. The release manager releases the tickets marked 'Ready for Release' in the release's JIRA filter using the 'bulk change' function.","title":"Step 10: Announce the release"},{"location":"release/empty-pkgs/","text":"Procedure for updating empty-* packages \u00b6 Background \u00b6 The empty-* packages were introduced a workaround for sites that install certain software (for example HTCondor or CA certs) from tarballs or other means that do not involve Yum/RPM. The packages contain no files, and exist merely to satisfy RPM dependencies so that other packages can be installed. It is the admin's responsibility to make sure that whatever component they installed the empty package for is functional. The empty packages are kept in a separate repository to prevent them from being accidentally installed instead of the component they claim to provide. Because of this, they do not go through the normal release process of development to testing to prerelease to release, but are moved straight from osg-development into osg-empty after developer testing. Warning It is important to untag the packages from osg-development immediately after promotion to osg-empty Procedure \u00b6 Prepare the package update, but do not build yet. Coordinate with the Software and Release Managers to set aside a good time to update the package. An empty package should not remain in the development repos for longer than a few hours. Build into development. Test out of development. Be thorough , as there is no separate acceptance testing for empty packages. In the JIRA ticket, document your testing procedure and request permission from both the Software and the Release Managers. (Since there is no acceptance testing, both of them have to sign off on the new build). After receiving permission, tag the builds into the osg-empty tags, and untag them from the osg-development tags. Then regenerate the osg-empty repos. osg-koji move-pkg osg-3.3-el6-development osg-3.3-el6-empty <EL6_BUILD_NVR> osg-koji move-pkg osg-3.3-el7-development osg-3.3-el7-empty <EL7_BUILD_NVR> osg-koji regen-repo --nowait osg-3.3-el6-empty osg-koji regen-repo --nowait osg-3.3-el7-empty","title":"Empty Packages"},{"location":"release/empty-pkgs/#procedure-for-updating-empty-packages","text":"","title":"Procedure for updating empty-* packages"},{"location":"release/empty-pkgs/#background","text":"The empty-* packages were introduced a workaround for sites that install certain software (for example HTCondor or CA certs) from tarballs or other means that do not involve Yum/RPM. The packages contain no files, and exist merely to satisfy RPM dependencies so that other packages can be installed. It is the admin's responsibility to make sure that whatever component they installed the empty package for is functional. The empty packages are kept in a separate repository to prevent them from being accidentally installed instead of the component they claim to provide. Because of this, they do not go through the normal release process of development to testing to prerelease to release, but are moved straight from osg-development into osg-empty after developer testing. Warning It is important to untag the packages from osg-development immediately after promotion to osg-empty","title":"Background"},{"location":"release/empty-pkgs/#procedure","text":"Prepare the package update, but do not build yet. Coordinate with the Software and Release Managers to set aside a good time to update the package. An empty package should not remain in the development repos for longer than a few hours. Build into development. Test out of development. Be thorough , as there is no separate acceptance testing for empty packages. In the JIRA ticket, document your testing procedure and request permission from both the Software and the Release Managers. (Since there is no acceptance testing, both of them have to sign off on the new build). After receiving permission, tag the builds into the osg-empty tags, and untag them from the osg-development tags. Then regenerate the osg-empty repos. osg-koji move-pkg osg-3.3-el6-development osg-3.3-el6-empty <EL6_BUILD_NVR> osg-koji move-pkg osg-3.3-el7-development osg-3.3-el7-empty <EL7_BUILD_NVR> osg-koji regen-repo --nowait osg-3.3-el6-empty osg-koji regen-repo --nowait osg-3.3-el7-empty","title":"Procedure"},{"location":"release/itb-testing/","text":"Testing OSG Software Prereleases on the Madison ITB Site \u00b6 This document contains basic recipes for testing a OSG software prereleases on the Madison ITB site, which includes HTCondor prerelease builds and full OSG software stack prereleases from Yum. Prerequisites \u00b6 The following items are known prerequisites to using this recipe. If you are not running the Ansible commands from osghost, there are almost certainly other prerequisites that are not listed below. And even using osghost for Ansible and itb-submit for the submissions, there may be other prerequisites missing. Please improve this document by adding other prerequisites as they are identified! A checkout of the osgitb directory from our local git instance (not GitHub) Your X.509 DN in the osgitb/unmanaged/htcondor-ce/grid-mapfile file and (via Ansible) on itb-ce1 and itb-ce2 Gathering Information \u00b6 Technically skippable, this section is about checking on the state of the ITB machines before making changes. The plan is to keep the ITB machines generally up-to-date independently, so those steps are not listed here. And honestly, the steps below are just some ideas; do whatever makes sense for the given update. The commands can be run as-is from within the osgitb directory from git. Check OS versions for all current ITB hosts: ansible current -i inventory -f 20 -o -m command -a 'cat /etc/redhat-release' Check the date and time on all hosts (in case NTP stops working): ansible current -i inventory -f 20 -o -m command -a 'date' Check software versions for certain hosts (e.g., for the condor package on hosts in the workers group): ansible workers -i inventory -f 20 -o -m command -a 'rpm -q condor' Installing HTCondor Prerelease \u00b6 Use this section to install a new version of HTCondor, specifically a prerelease build from the development or upcoming-development repository, on the test hosts. Obtain the NVR of the HTCondor prerelease build from OSG to test. Do this by talking to Tim T. and checking Koji. Shut down HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=stopped' ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=stopped' Install new version of HTCondor on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes update condor' or, if you need to install an NVR that is \u201cearlier\u201d (in the RPM sense) than what is currently installed: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes downgrade condor condor-classads condor-python condor-procd blahp' Verify correct RPM versions across the site: ansible condor -i inventory -f 20 -o -m command -a 'rpm -q condor' Restart HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=started' ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=started' Installing a Prerelease of the OSG Software Stack \u00b6 Use this section to install new versions of all OSG software from a prerelease repository in Yum. Check with the Release Manager to make sure that the prerelease repository has been populated with the desired package versions. Make sure that software is generally up-to-date on the hosts \u2014 see the Madison ITB Site doc for more details It may be desirable to update only non-OSG software at this stage, in which case one could simply disable the OSG repositories by adding command-line options to the yum update commands. Install new software on prerelease hosts: ansible testing -i inventory -bK -f 20 -m command -a 'yum --enablerepo=osg-prerelease --assumeyes update' Read the Yum output carefully, and follow up on any warnings, etc. If the osg-configure package was updated on any host(s), run the osg-configure command on the host(s): ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -v' -l [HOST(S)] ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -c' -l [HOST(S)] Verify OSG software updates by inspecting the Yum output carefully or examining specific package versions: ansible current -i inventory -f 20 -o -m command -a 'rpm -q osg-wn-client' Use an inventory group and package names that best fit the situation. Running Tests \u00b6 For the first two test workflows, use your personal space on itb-submit . Copy or checkout the osgitb/htcondor-tests directory to get the test directories. Part \u2160: Submitting jobs directly \u00b6 Change into the 1-direct-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in a few minutes. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt You should see a reasonable distribution of jobs by hostname, keeping in mind the different number of cores per machine and the fact that HTCondor can and will reuse claims to process many jobs on a single host. Especially watch out for a case in which no jobs run on the newly updated hosts (at the time of writing: itb-data[456] ). (Optional) Clean up, using the make clean or make distclean commands. Use the clean target to remove intermediate result and log files generated by a workflow run but preserve the final output file; use the distclean target to remove all workflow-generated files (plus Emacs backup files). Part \u2161: Submitting jobs using HTCondor-C \u00b6 If direct submissions fail, there is probably no point to doing this step. Change into the 2-htcondor-c-jobs subdirectory If there are old result files in the directory, remove them: make distclean Get a proxy for your X.509 credentials voms-proxy-init Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in 10 minutes or less; generally, this test takes longer than the direct submission test, because of the layers of indirection. Also, status updates from the CEs back to the submit host are infrequent. For direct information about the CEs, log in to itb-ce1 and itb-ce2 to check status; don\u2019t forget to check both condor_ce_q and condor_q on the CEs, probably in that order. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt Again, look for a reasonable distribution of jobs by hostname. (Optional) Clean up, using the make clean or make distclean commands. Part \u2162: Submitting jobs from a GlideinWMS VO Frontend \u00b6 For this workflow, use your personal space on glidein3.chtc.wisc.edu . Copy or checkout the osgitb/htcondor-tests directory to get the test directories. Again, if previous steps fail, do not bother with this step. Change into the 3-frontend-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck This workflow could take much longer than the first two, maybe an hour or so. Also, unless there are active glideins, it will take 10 minutes or longer for the first glideins to appear and start matching jobs. Thus it is helpful to monitor condor_q -totals until all of the jobs are submitted (there should be 2001), then switch to monitoring condor_status until glideins start appearing. After the first jobs start running and finishing, it is probably safe to ignore the rest of the run. If the jobs do not appear in the local queue, if glideins do not appear, or if jobs do not start running on the glideins, it is time to start troubleshooting. Check the final output file: cat count-by-hostnames.txt The distribution of jobs per execute node may be more skewed than in the first two workflows, due to the way in which pilots ramp up over time and how HTCondor allocates jobs to slots. (Optional) Clean up, using the make clean or make distclean commands.","title":"ITB Prerelease Testing"},{"location":"release/itb-testing/#testing-osg-software-prereleases-on-the-madison-itb-site","text":"This document contains basic recipes for testing a OSG software prereleases on the Madison ITB site, which includes HTCondor prerelease builds and full OSG software stack prereleases from Yum.","title":"Testing OSG Software Prereleases on the Madison ITB Site"},{"location":"release/itb-testing/#prerequisites","text":"The following items are known prerequisites to using this recipe. If you are not running the Ansible commands from osghost, there are almost certainly other prerequisites that are not listed below. And even using osghost for Ansible and itb-submit for the submissions, there may be other prerequisites missing. Please improve this document by adding other prerequisites as they are identified! A checkout of the osgitb directory from our local git instance (not GitHub) Your X.509 DN in the osgitb/unmanaged/htcondor-ce/grid-mapfile file and (via Ansible) on itb-ce1 and itb-ce2","title":"Prerequisites"},{"location":"release/itb-testing/#gathering-information","text":"Technically skippable, this section is about checking on the state of the ITB machines before making changes. The plan is to keep the ITB machines generally up-to-date independently, so those steps are not listed here. And honestly, the steps below are just some ideas; do whatever makes sense for the given update. The commands can be run as-is from within the osgitb directory from git. Check OS versions for all current ITB hosts: ansible current -i inventory -f 20 -o -m command -a 'cat /etc/redhat-release' Check the date and time on all hosts (in case NTP stops working): ansible current -i inventory -f 20 -o -m command -a 'date' Check software versions for certain hosts (e.g., for the condor package on hosts in the workers group): ansible workers -i inventory -f 20 -o -m command -a 'rpm -q condor'","title":"Gathering Information"},{"location":"release/itb-testing/#installing-htcondor-prerelease","text":"Use this section to install a new version of HTCondor, specifically a prerelease build from the development or upcoming-development repository, on the test hosts. Obtain the NVR of the HTCondor prerelease build from OSG to test. Do this by talking to Tim T. and checking Koji. Shut down HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=stopped' ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=stopped' Install new version of HTCondor on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes update condor' or, if you need to install an NVR that is \u201cearlier\u201d (in the RPM sense) than what is currently installed: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes downgrade condor condor-classads condor-python condor-procd blahp' Verify correct RPM versions across the site: ansible condor -i inventory -f 20 -o -m command -a 'rpm -q condor' Restart HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=started' ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=started'","title":"Installing HTCondor Prerelease"},{"location":"release/itb-testing/#installing-a-prerelease-of-the-osg-software-stack","text":"Use this section to install new versions of all OSG software from a prerelease repository in Yum. Check with the Release Manager to make sure that the prerelease repository has been populated with the desired package versions. Make sure that software is generally up-to-date on the hosts \u2014 see the Madison ITB Site doc for more details It may be desirable to update only non-OSG software at this stage, in which case one could simply disable the OSG repositories by adding command-line options to the yum update commands. Install new software on prerelease hosts: ansible testing -i inventory -bK -f 20 -m command -a 'yum --enablerepo=osg-prerelease --assumeyes update' Read the Yum output carefully, and follow up on any warnings, etc. If the osg-configure package was updated on any host(s), run the osg-configure command on the host(s): ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -v' -l [HOST(S)] ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -c' -l [HOST(S)] Verify OSG software updates by inspecting the Yum output carefully or examining specific package versions: ansible current -i inventory -f 20 -o -m command -a 'rpm -q osg-wn-client' Use an inventory group and package names that best fit the situation.","title":"Installing a Prerelease of the OSG Software Stack"},{"location":"release/itb-testing/#running-tests","text":"For the first two test workflows, use your personal space on itb-submit . Copy or checkout the osgitb/htcondor-tests directory to get the test directories.","title":"Running Tests"},{"location":"release/itb-testing/#part-i-submitting-jobs-directly","text":"Change into the 1-direct-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in a few minutes. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt You should see a reasonable distribution of jobs by hostname, keeping in mind the different number of cores per machine and the fact that HTCondor can and will reuse claims to process many jobs on a single host. Especially watch out for a case in which no jobs run on the newly updated hosts (at the time of writing: itb-data[456] ). (Optional) Clean up, using the make clean or make distclean commands. Use the clean target to remove intermediate result and log files generated by a workflow run but preserve the final output file; use the distclean target to remove all workflow-generated files (plus Emacs backup files).","title":"Part \u2160: Submitting jobs directly"},{"location":"release/itb-testing/#part-ii-submitting-jobs-using-htcondor-c","text":"If direct submissions fail, there is probably no point to doing this step. Change into the 2-htcondor-c-jobs subdirectory If there are old result files in the directory, remove them: make distclean Get a proxy for your X.509 credentials voms-proxy-init Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in 10 minutes or less; generally, this test takes longer than the direct submission test, because of the layers of indirection. Also, status updates from the CEs back to the submit host are infrequent. For direct information about the CEs, log in to itb-ce1 and itb-ce2 to check status; don\u2019t forget to check both condor_ce_q and condor_q on the CEs, probably in that order. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt Again, look for a reasonable distribution of jobs by hostname. (Optional) Clean up, using the make clean or make distclean commands.","title":"Part \u2161: Submitting jobs using HTCondor-C"},{"location":"release/itb-testing/#part-iii-submitting-jobs-from-a-glideinwms-vo-frontend","text":"For this workflow, use your personal space on glidein3.chtc.wisc.edu . Copy or checkout the osgitb/htcondor-tests directory to get the test directories. Again, if previous steps fail, do not bother with this step. Change into the 3-frontend-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck This workflow could take much longer than the first two, maybe an hour or so. Also, unless there are active glideins, it will take 10 minutes or longer for the first glideins to appear and start matching jobs. Thus it is helpful to monitor condor_q -totals until all of the jobs are submitted (there should be 2001), then switch to monitoring condor_status until glideins start appearing. After the first jobs start running and finishing, it is probably safe to ignore the rest of the run. If the jobs do not appear in the local queue, if glideins do not appear, or if jobs do not start running on the glideins, it is time to start troubleshooting. Check the final output file: cat count-by-hostnames.txt The distribution of jobs per execute node may be more skewed than in the first two workflows, due to the way in which pilots ramp up over time and how HTCondor allocates jobs to slots. (Optional) Clean up, using the make clean or make distclean commands.","title":"Part \u2162: Submitting jobs from a GlideinWMS VO Frontend"},{"location":"release/new-os-series/","text":"How to Add a New Enterprise Linux Series \u00b6 Throughout this document, we will refer to the new Enterprise Linux series as ELX , and the previous EL series as ELX.OLD . For example, if we are adding el9, then ELX refers to el9 , and ELX.OLD refers to el8 . This document explains how to add support for a new ELX series to an existing OSG series. For adding a new OSG series, see the New Release Series documentation. See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure. Prepare Koji and OSG-Build \u00b6 Add ELX Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-elX-tags-etc In particular, update EL as appropriate (eg, el9 ), and update the ### external repos ### section with a new block of external repos to add to the dist-$EL-build tag. Then for the OSG-series specific tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, set SERIES to the current OSG series, and include ONLY the new ELX in the EL loop (eg, el9 ). (Do not include EL versions that already exist for this series.) Then for the devops tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-devops-tags-etc In particular, set SERIES to the current OSG series, and set EL to the new ELX in the EL loop (eg, el9 ). Add Koji package signing, as necessary With any luck, you can use the existing RPM signing key for the OSG series to which you are adding the new EL series. If it turns out that you need to create a new RPM signing key for ELX (because reusing the one for the current OSG series doesn't work in ELX for some unexpected reason), then you will need to generate a new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config. See Infrastructure Google Drive folder for details. Either way, you will need to make modifications to the osg-services repo, gitolite@git.chtc.wisc.edu:osg-services.git , so get a checkout of that ready. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services If you are adding a new RPM signing key, you need to edit koji/roles/signplugin/vars/main.yml to add the key name, password, and list of tags the key should be used for; and koji/roles/signplugin/templates/sign.conf.j2 to add template code for generating the sign.conf config blocks for those tags. If you are using the existing RPM signing key for the OSG series, you only need to edit koji/roles/signplugin/vars/main.yml . Find the tags section for your current signing key, eg, osg3_build_tags , and add all ELX build tags to this section. Eg, for el9 to OSG 3.6: osg3_build_tags: - dist-el9-build - osg-el9-internal-build - osg-3.6-el9-build - osg-3.6-upcoming-el9-build Apply the Koji Ansible config on the Koji Hub host. # ssh koji.chtc.wisc.edu # git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd ~/osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply If you are adding a new RPM signing key, export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-<N> (where <N> is the previous key's number incremented by one), and add it to the osg-release RPM. In the script generate-repo-files.sh ensure that the logic for selecting the GPGKEY includes the correct behavior for the new ELX to reference the latest key file. Update osg-build to add the new ELX to the various dvers in python scripts, and extra_dvers in promoter.ini ; and add the new ELX tags and targets to the test scripts. See the Git commits on opensciencegrid/osg-build for SOFTWARE-5342 for details on how to do this. Use this version of osg-build for subsequent steps. Subsequent Steps \u00b6 This section is incomplete. But for starters, begin with the Build prerequisite packages section of the New Release Series documentation. In general, you will not have to repeat steps for creating a new osg-3.Y series, but you will have to create a new buildsys-macros.elX package for the new EL9 series. Good luck.","title":"New OS Series"},{"location":"release/new-os-series/#how-to-add-a-new-enterprise-linux-series","text":"Throughout this document, we will refer to the new Enterprise Linux series as ELX , and the previous EL series as ELX.OLD . For example, if we are adding el9, then ELX refers to el9 , and ELX.OLD refers to el8 . This document explains how to add support for a new ELX series to an existing OSG series. For adding a new OSG series, see the New Release Series documentation. See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure.","title":"How to Add a New Enterprise Linux Series"},{"location":"release/new-os-series/#prepare-koji-and-osg-build","text":"Add ELX Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-elX-tags-etc In particular, update EL as appropriate (eg, el9 ), and update the ### external repos ### section with a new block of external repos to add to the dist-$EL-build tag. Then for the OSG-series specific tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, set SERIES to the current OSG series, and include ONLY the new ELX in the EL loop (eg, el9 ). (Do not include EL versions that already exist for this series.) Then for the devops tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-devops-tags-etc In particular, set SERIES to the current OSG series, and set EL to the new ELX in the EL loop (eg, el9 ). Add Koji package signing, as necessary With any luck, you can use the existing RPM signing key for the OSG series to which you are adding the new EL series. If it turns out that you need to create a new RPM signing key for ELX (because reusing the one for the current OSG series doesn't work in ELX for some unexpected reason), then you will need to generate a new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config. See Infrastructure Google Drive folder for details. Either way, you will need to make modifications to the osg-services repo, gitolite@git.chtc.wisc.edu:osg-services.git , so get a checkout of that ready. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services If you are adding a new RPM signing key, you need to edit koji/roles/signplugin/vars/main.yml to add the key name, password, and list of tags the key should be used for; and koji/roles/signplugin/templates/sign.conf.j2 to add template code for generating the sign.conf config blocks for those tags. If you are using the existing RPM signing key for the OSG series, you only need to edit koji/roles/signplugin/vars/main.yml . Find the tags section for your current signing key, eg, osg3_build_tags , and add all ELX build tags to this section. Eg, for el9 to OSG 3.6: osg3_build_tags: - dist-el9-build - osg-el9-internal-build - osg-3.6-el9-build - osg-3.6-upcoming-el9-build Apply the Koji Ansible config on the Koji Hub host. # ssh koji.chtc.wisc.edu # git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd ~/osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply If you are adding a new RPM signing key, export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-<N> (where <N> is the previous key's number incremented by one), and add it to the osg-release RPM. In the script generate-repo-files.sh ensure that the logic for selecting the GPGKEY includes the correct behavior for the new ELX to reference the latest key file. Update osg-build to add the new ELX to the various dvers in python scripts, and extra_dvers in promoter.ini ; and add the new ELX tags and targets to the test scripts. See the Git commits on opensciencegrid/osg-build for SOFTWARE-5342 for details on how to do this. Use this version of osg-build for subsequent steps.","title":"Prepare Koji and OSG-Build"},{"location":"release/new-os-series/#subsequent-steps","text":"This section is incomplete. But for starters, begin with the Build prerequisite packages section of the New Release Series documentation. In general, you will not have to repeat steps for creating a new osg-3.Y series, but you will have to create a new buildsys-macros.elX package for the new EL9 series. Good luck.","title":"Subsequent Steps"},{"location":"release/new-release-series/","text":"How to Prepare a New Release Series \u00b6 Throughout this document, we will refer to the new release series as 3.X , and the previous release series as 3.OLD . For example, if we are creating OSG 3.7, then 3.X refers to 3.7 , and 3.OLD refers to 3.6 . See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure. Prepare Koji and OSG-Build \u00b6 Add 3.X and 3.X-upcoming Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, update SERIES as appropriate, and include any applicable Enterprise Linux versions to the EL loop (eg, el7 el8 ) Add Koji package signing Starting with OSG 3.6, we've been using a different RPM signing key for each series. Generate the new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config (see Infrastructure Google Drive folder for details). Use a strong algorithm for the key; 4096-bit RSA is recommended. Note: generate RSA keys on EL9 (e.g. in a container) or they will not be importable in EL9. Edit koji/roles/signplugin/vars/main.yml and koji/roles/signplugin/templates/sign.conf.j2 in the Koji Ansible config to add the key name, password, list of tags the key should be used for, and template code for generating the sign.conf config blocks for those tags. Tags for EL9 and newer distros should have gpg_digest_algo = sha256 set. Apply the Koji Ansible config on the Koji Hub host. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply Export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-3.X , and add it to the osg-release RPM. Add the file and modify the template.repo.* files to reference the new key file. Update Koji policy as needed (for new distro versions); see SOFTWARE-5426 for details. Update osg-build to use the new koji tags and targets (not by default of course). See the Git commits on opensciencegrid/osg-build for SOFTWARE-2693 for details on how to do this. Use this version for subsequent steps. Build prerequisite packages \u00b6 Create a blank X-main SVN branch and add buildsys-macros.elY packages, one for each supported distro version. As an example, here's what you'd do for osg-23 and el8: svn copy the buildsys-macros.elX directories from the osg-3.OLD branch and hand-edit it to hardcode the new osg_version and dver values. $ cd native/redhat/branches $ svn mkdir 23 -main $ svn copy osg-3.6/buildsys-macros.el8 23 -main/buildsys-macros.el8 $ cd 23 -main/buildsys-macros.el8 $ $EDITOR osg/*.spec # ## change the osg_version and dver values as appropriate Build locally and import the resulting RPMs (need Koji admin permissions). Run the following commands (adjust the NVR and distro version as necessary): :::console $ osg-build rpmbuild --el8 $ osg-koji import _build_results/buildsys-macros-*.el8.src.rpm $ osg-koji import _build_results/buildsys-macros-*.el8.noarch.rpm $ pkg=$(basename _build_results/buildsys-macros-*.el8.src.rpm .src.rpm) $ osg-koji tag-pkg osg-23-main-el8-development \"$pkg\" Bump the revision in each buildsys-macros.elY spec file and edit the %changelog , svn commit , then do Koji builds of them. Again, with osg-3.7 and el8: $ osg-build koji --repo = 23 -main --el8 23 -main/buildsys-macros.el8 Repeat the previous steps for X-upcoming and X-internal Update tarball-client bundles.ini patches/ upload-tarballs-to-oasis (for X, foreach_dver_arch will need to be updated for the new set of X dver_arches ) Add relase-series specific repos/osg-23-main-el<DVER>.repo.in for each supported distro version (e.g., 8 , 9 ) Populate the bootstrap tags Need to have them inherit from the OLD development tags, but only packages, not builds (hence the --noconfig ; yes, the name is weird) # set OLD and NEW as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do osg-koji add-tag-inheritance --noconfig --priority=2 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-main-$el-development; osg-koji add-tag-inheritance --noconfig --priority=3 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-upcoming-$el-development; done Get the actual NVRs to tag I put Brian's spreadsheet into Excel and used its filtering feature to separate out: the packages going into 3.X.0 package differences between each dver (eg, el7 vs el8) save the NVRs for each dver to a separate file, eg, pkgtotag-el7.txt and pkgtotag-el8.txt Tagging: # set X as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do \\ xargs -a pkgtotag-$el osg-koji tag-pkg osg-X-main-$el-bootstrap; \\ done (btw, xargs -a doesn't work on a Mac) In order to make testing easier, build the new osg-release and osg-release-itb packages and promote them all the way to release, so that all the 3.X repos exist and have at least one rpm in them. Prepare repo and test infrastructure \u00b6 Update mash to pull from the new tags, using the new key On repo-itb On repo Put the new public key on repo and repo-itb Update documentation here Update osg-test / vmu-test-runs They're only going to test from minefield (and eventually testing) until the release Build software \u00b6 Populate SVN branches and tags (as in fill it with the packages we're going to release for 3.X and 3.X-upcoming) Mass rebuild Don't forget to update the empty and contrib tags with the appropriate packages; remove the empty* packages from the development tags after they've been tagged into the empty tags Drop the osg-X-main-elY-bootstrap koji tags (after the successful mass rebuild only) Update docker-software-base and any container images that are based on it Release! \u00b6 Update release tools scripts as necessary Cut a release Have a release party Update this document and the Infrastructure Google Drive folder with issues you ran into Post-release \u00b6 Update osg-test / vmu-test-runs again to add release and release -> testing tests Update the tarball that is used to keep the CA certificates and VO data current in CVMFS. Logon as ouser.mis@oasis-login.opensciencegrid.org and follow the directions in the README file. Update the koji osg-elY build targets to build from and to X instead of OLD ; notify the software-discuss list of this change Update the docker-osg-wn-client scripts to build from X (need direct push access) Update the constants in the genbranches script in the docker-osg-wn-scripts repo Update the branches in docker-osg-wn-client ; a script like this ought to work: git clone git@github.com:opensciencegrid/docker-osg-wn-scripts.git git clone git@github.com:opensciencegrid/docker-osg-wn.git cd docker-osg-wn-scripts ./genbranches cd ../docker-osg-wn for bpath in ../docker-osg-wn-scripts/branches/* ; do b = ${ bpath ##*/ } git checkout -b $b master && \\ mv $bpath Dockerfile.in && \\ git add Dockerfile.in && \\ git commit -m \"Add branch $b \" done and then run a similar script to update the existing branches Check the results before pushing, and then run git push --all Update the arrays in update-all and osg-wn-nightly-build in docker-osg-wn-scripts Update the default promotion route aliases in osg-promote Update documentation again to reflect that X is now the main branch and OLD is the maintenance branch","title":"New Release Series"},{"location":"release/new-release-series/#how-to-prepare-a-new-release-series","text":"Throughout this document, we will refer to the new release series as 3.X , and the previous release series as 3.OLD . For example, if we are creating OSG 3.7, then 3.X refers to 3.7 , and 3.OLD refers to 3.6 . See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure.","title":"How to Prepare a New Release Series"},{"location":"release/new-release-series/#prepare-koji-and-osg-build","text":"Add 3.X and 3.X-upcoming Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, update SERIES as appropriate, and include any applicable Enterprise Linux versions to the EL loop (eg, el7 el8 ) Add Koji package signing Starting with OSG 3.6, we've been using a different RPM signing key for each series. Generate the new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config (see Infrastructure Google Drive folder for details). Use a strong algorithm for the key; 4096-bit RSA is recommended. Note: generate RSA keys on EL9 (e.g. in a container) or they will not be importable in EL9. Edit koji/roles/signplugin/vars/main.yml and koji/roles/signplugin/templates/sign.conf.j2 in the Koji Ansible config to add the key name, password, list of tags the key should be used for, and template code for generating the sign.conf config blocks for those tags. Tags for EL9 and newer distros should have gpg_digest_algo = sha256 set. Apply the Koji Ansible config on the Koji Hub host. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply Export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-3.X , and add it to the osg-release RPM. Add the file and modify the template.repo.* files to reference the new key file. Update Koji policy as needed (for new distro versions); see SOFTWARE-5426 for details. Update osg-build to use the new koji tags and targets (not by default of course). See the Git commits on opensciencegrid/osg-build for SOFTWARE-2693 for details on how to do this. Use this version for subsequent steps.","title":"Prepare Koji and OSG-Build"},{"location":"release/new-release-series/#build-prerequisite-packages","text":"Create a blank X-main SVN branch and add buildsys-macros.elY packages, one for each supported distro version. As an example, here's what you'd do for osg-23 and el8: svn copy the buildsys-macros.elX directories from the osg-3.OLD branch and hand-edit it to hardcode the new osg_version and dver values. $ cd native/redhat/branches $ svn mkdir 23 -main $ svn copy osg-3.6/buildsys-macros.el8 23 -main/buildsys-macros.el8 $ cd 23 -main/buildsys-macros.el8 $ $EDITOR osg/*.spec # ## change the osg_version and dver values as appropriate Build locally and import the resulting RPMs (need Koji admin permissions). Run the following commands (adjust the NVR and distro version as necessary): :::console $ osg-build rpmbuild --el8 $ osg-koji import _build_results/buildsys-macros-*.el8.src.rpm $ osg-koji import _build_results/buildsys-macros-*.el8.noarch.rpm $ pkg=$(basename _build_results/buildsys-macros-*.el8.src.rpm .src.rpm) $ osg-koji tag-pkg osg-23-main-el8-development \"$pkg\" Bump the revision in each buildsys-macros.elY spec file and edit the %changelog , svn commit , then do Koji builds of them. Again, with osg-3.7 and el8: $ osg-build koji --repo = 23 -main --el8 23 -main/buildsys-macros.el8 Repeat the previous steps for X-upcoming and X-internal Update tarball-client bundles.ini patches/ upload-tarballs-to-oasis (for X, foreach_dver_arch will need to be updated for the new set of X dver_arches ) Add relase-series specific repos/osg-23-main-el<DVER>.repo.in for each supported distro version (e.g., 8 , 9 ) Populate the bootstrap tags Need to have them inherit from the OLD development tags, but only packages, not builds (hence the --noconfig ; yes, the name is weird) # set OLD and NEW as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do osg-koji add-tag-inheritance --noconfig --priority=2 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-main-$el-development; osg-koji add-tag-inheritance --noconfig --priority=3 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-upcoming-$el-development; done Get the actual NVRs to tag I put Brian's spreadsheet into Excel and used its filtering feature to separate out: the packages going into 3.X.0 package differences between each dver (eg, el7 vs el8) save the NVRs for each dver to a separate file, eg, pkgtotag-el7.txt and pkgtotag-el8.txt Tagging: # set X as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do \\ xargs -a pkgtotag-$el osg-koji tag-pkg osg-X-main-$el-bootstrap; \\ done (btw, xargs -a doesn't work on a Mac) In order to make testing easier, build the new osg-release and osg-release-itb packages and promote them all the way to release, so that all the 3.X repos exist and have at least one rpm in them.","title":"Build prerequisite packages"},{"location":"release/new-release-series/#prepare-repo-and-test-infrastructure","text":"Update mash to pull from the new tags, using the new key On repo-itb On repo Put the new public key on repo and repo-itb Update documentation here Update osg-test / vmu-test-runs They're only going to test from minefield (and eventually testing) until the release","title":"Prepare repo and test infrastructure"},{"location":"release/new-release-series/#build-software","text":"Populate SVN branches and tags (as in fill it with the packages we're going to release for 3.X and 3.X-upcoming) Mass rebuild Don't forget to update the empty and contrib tags with the appropriate packages; remove the empty* packages from the development tags after they've been tagged into the empty tags Drop the osg-X-main-elY-bootstrap koji tags (after the successful mass rebuild only) Update docker-software-base and any container images that are based on it","title":"Build software"},{"location":"release/new-release-series/#release","text":"Update release tools scripts as necessary Cut a release Have a release party Update this document and the Infrastructure Google Drive folder with issues you ran into","title":"Release!"},{"location":"release/new-release-series/#post-release","text":"Update osg-test / vmu-test-runs again to add release and release -> testing tests Update the tarball that is used to keep the CA certificates and VO data current in CVMFS. Logon as ouser.mis@oasis-login.opensciencegrid.org and follow the directions in the README file. Update the koji osg-elY build targets to build from and to X instead of OLD ; notify the software-discuss list of this change Update the docker-osg-wn-client scripts to build from X (need direct push access) Update the constants in the genbranches script in the docker-osg-wn-scripts repo Update the branches in docker-osg-wn-client ; a script like this ought to work: git clone git@github.com:opensciencegrid/docker-osg-wn-scripts.git git clone git@github.com:opensciencegrid/docker-osg-wn.git cd docker-osg-wn-scripts ./genbranches cd ../docker-osg-wn for bpath in ../docker-osg-wn-scripts/branches/* ; do b = ${ bpath ##*/ } git checkout -b $b master && \\ mv $bpath Dockerfile.in && \\ git add Dockerfile.in && \\ git commit -m \"Add branch $b \" done and then run a similar script to update the existing branches Check the results before pushing, and then run git push --all Update the arrays in update-all and osg-wn-nightly-build in docker-osg-wn-scripts Update the default promotion route aliases in osg-promote Update documentation again to reflect that X is now the main branch and OLD is the maintenance branch","title":"Post-release"},{"location":"release/release-eol/","text":"Release Series End-of-Life \u00b6 When a release reaches end-of-life, we need to discountinue a few items. Remove the retired series from the OSG VMU tests. However, retain the upgrade test from the retired series to the current series. Remove any github actions that build software-base or osg-wn-client Docker images for the retired series. Previous Release Series Removal Plan \u00b6 In order to reduce clutter and disk usage on our repositories and build system, we will remove older OSG Software release series. This will result in packages from those series becoming unavailable, so we will remove a release series when its packages are no longer needed. We will remove a release series no earlier than when the following series is completely out of support. For example, OSG 3.1 will be removed when OSG 3.2 is out of support, and OSG 3.2 will be removed when OSG 3.3 is out of support. Tasks \u00b6 Removing a release series requires work from both Operations and Software & Release. The first step is to create a JIRA ticket in the SOFTWARE project to track the work. Second, Software & Release will enumerate the directories for Operations to remove. Operations tasks should be completed before Software & Release tasks. Operations \u00b6 These tasks should be completed in order. Two weeks in advance, notify sites (including mirror sites) that the release series is going away. See the template email below. Remove the series from the mash configs on the repo.opensciencegrid.org machines: Add the koji tags for the old series to the /usr/local/osg-tags.excluded file: # cd /usr/local # fgrep osg-3.1 osg-tags osg-3.1-el5-contrib osg-3.1-el5-development osg-3.1-el5-release osg-3.1-el5-testing osg-3.1-el6-contrib osg-3.1-el6-development osg-3.1-el6-release osg-3.1-el6-testing # fgrep osg-3.1 osg-tags >> osg-tags.exclude Re-run update_mashfiles.sh to update the mash config files: # ./update_mashfiles.sh Remove the appropriate repo directories from /usr/local/repo/osg . # rm -rf repo*/osg/3.1/ Reclaim space from any cached rpms in the mash cache which are no longer linked elsewhere: # find mash/cache/ -name \\* .rpm -type f -links 1 -delete Wait for mash to run and verify that the repos are no longer getting updated: Look at the mash logs in /var/log/repo . Verify that mash did not recreate the repo directory under /usr/local/repo/osg corresponding to the old release series. Remove tarballs from repo and OASIS Software & Release \u00b6 These tasks can be completed in any order. Tag and remove the SVN branch corresponding to the release series. Edit vm-test-runs and remove any \"long tail\" tests that reference the series. Edit tarball-client : Remove bundles from bundles.ini . Remove patch and other files that were used only by those bundles. Test that the current bundles didn't get broken by your changes. Edit osg-build : Remove the promotion routes from promoter.ini . Remove references in constants.py . Test your changes; also run the unit tests. Remove things from Koji: All targets referencing the series. All tags referencing the series. Remove references to the series from opensciencegrid/docker-osg-wn on GitHub. Move files in /p/vdt/public/html/release-info to its attic subdirectory. Undoing \u00b6 If we really need RPMs from a removed release series, we can look at the text files in /p/vdt/public/html/release-info/attic to determine the exact NVRs we need, and download them from Koji. Template Email \u00b6 Subject: OSG 3.X packages will be removed from the repositories YYYY-MM-DD On <DAYNAME, MONTH DAY>, the OSG will be removing the OSG <3.X> release series from our repositories. This includes both RPMs and tarballs hosted on repo.opensciencegrid.org. As a reminder, support for OSG <3.X> ended after <MONTH YEAR>. If your site is running OSG <3.X>, you should upgrade to the current release series, OSG 3.Y. See our upgrade documentation [1] for instructions. If you need assistance upgrading, please contact us at help@osg-htc.org. [1] https://osg-htc.org/docs/release/release_series/#updating-from-osg-31-32-33-to-34 If we're dropping support for a distro (e.g. EL 5 when we drop OSG 3.2), add the following after the first paragraph: Note that OSG <3.X> was the last release that supported Enterprise Linux <Z> distributions. If you believe that you still need support for this operating system series, please contact us at help@osg-htc.org. Since we're dropping support for i386 (32-bit) when we drop OSG 3.3, add the following after the first paragraph: Note that OSG 3.3 was the last release that contained 32-bit packages. If you believe that you still need support for this architecture, please contacts us at help@osg-htc.org.","title":"Release Series End-of-Life"},{"location":"release/release-eol/#release-series-end-of-life","text":"When a release reaches end-of-life, we need to discountinue a few items. Remove the retired series from the OSG VMU tests. However, retain the upgrade test from the retired series to the current series. Remove any github actions that build software-base or osg-wn-client Docker images for the retired series.","title":"Release Series End-of-Life"},{"location":"release/release-eol/#previous-release-series-removal-plan","text":"In order to reduce clutter and disk usage on our repositories and build system, we will remove older OSG Software release series. This will result in packages from those series becoming unavailable, so we will remove a release series when its packages are no longer needed. We will remove a release series no earlier than when the following series is completely out of support. For example, OSG 3.1 will be removed when OSG 3.2 is out of support, and OSG 3.2 will be removed when OSG 3.3 is out of support.","title":"Previous Release Series Removal Plan"},{"location":"release/release-eol/#tasks","text":"Removing a release series requires work from both Operations and Software & Release. The first step is to create a JIRA ticket in the SOFTWARE project to track the work. Second, Software & Release will enumerate the directories for Operations to remove. Operations tasks should be completed before Software & Release tasks.","title":"Tasks"},{"location":"release/release-eol/#operations","text":"These tasks should be completed in order. Two weeks in advance, notify sites (including mirror sites) that the release series is going away. See the template email below. Remove the series from the mash configs on the repo.opensciencegrid.org machines: Add the koji tags for the old series to the /usr/local/osg-tags.excluded file: # cd /usr/local # fgrep osg-3.1 osg-tags osg-3.1-el5-contrib osg-3.1-el5-development osg-3.1-el5-release osg-3.1-el5-testing osg-3.1-el6-contrib osg-3.1-el6-development osg-3.1-el6-release osg-3.1-el6-testing # fgrep osg-3.1 osg-tags >> osg-tags.exclude Re-run update_mashfiles.sh to update the mash config files: # ./update_mashfiles.sh Remove the appropriate repo directories from /usr/local/repo/osg . # rm -rf repo*/osg/3.1/ Reclaim space from any cached rpms in the mash cache which are no longer linked elsewhere: # find mash/cache/ -name \\* .rpm -type f -links 1 -delete Wait for mash to run and verify that the repos are no longer getting updated: Look at the mash logs in /var/log/repo . Verify that mash did not recreate the repo directory under /usr/local/repo/osg corresponding to the old release series. Remove tarballs from repo and OASIS","title":"Operations"},{"location":"release/release-eol/#software-release","text":"These tasks can be completed in any order. Tag and remove the SVN branch corresponding to the release series. Edit vm-test-runs and remove any \"long tail\" tests that reference the series. Edit tarball-client : Remove bundles from bundles.ini . Remove patch and other files that were used only by those bundles. Test that the current bundles didn't get broken by your changes. Edit osg-build : Remove the promotion routes from promoter.ini . Remove references in constants.py . Test your changes; also run the unit tests. Remove things from Koji: All targets referencing the series. All tags referencing the series. Remove references to the series from opensciencegrid/docker-osg-wn on GitHub. Move files in /p/vdt/public/html/release-info to its attic subdirectory.","title":"Software & Release"},{"location":"release/release-eol/#undoing","text":"If we really need RPMs from a removed release series, we can look at the text files in /p/vdt/public/html/release-info/attic to determine the exact NVRs we need, and download them from Koji.","title":"Undoing"},{"location":"release/release-eol/#template-email","text":"Subject: OSG 3.X packages will be removed from the repositories YYYY-MM-DD On <DAYNAME, MONTH DAY>, the OSG will be removing the OSG <3.X> release series from our repositories. This includes both RPMs and tarballs hosted on repo.opensciencegrid.org. As a reminder, support for OSG <3.X> ended after <MONTH YEAR>. If your site is running OSG <3.X>, you should upgrade to the current release series, OSG 3.Y. See our upgrade documentation [1] for instructions. If you need assistance upgrading, please contact us at help@osg-htc.org. [1] https://osg-htc.org/docs/release/release_series/#updating-from-osg-31-32-33-to-34 If we're dropping support for a distro (e.g. EL 5 when we drop OSG 3.2), add the following after the first paragraph: Note that OSG <3.X> was the last release that supported Enterprise Linux <Z> distributions. If you believe that you still need support for this operating system series, please contact us at help@osg-htc.org. Since we're dropping support for i386 (32-bit) when we drop OSG 3.3, add the following after the first paragraph: Note that OSG 3.3 was the last release that contained 32-bit packages. If you believe that you still need support for this architecture, please contacts us at help@osg-htc.org.","title":"Template Email"},{"location":"software/ce-test-scaling/","text":"How to Run Scalability Tests on a CE \u00b6 Introduction \u00b6 This document is intended as a general overview of the process for scalability testing of an OSG CE (Compute Element). All examples are for testing an HTCondor-CE , but they should be applicable for other CE software. The focus of testing a CE is on the number of concurrent running jobs the CE can sustain as well as the ramp-up rate when many jobs are queued. Sleeper Pool \u00b6 With the focus on the CE, actual job payloads can be minimal \u2013 simple long sleep jobs are fine. Thus, then can run on nearly any resources, and it is even possible to allow far more of these jobs to run on a single resource than would be sensible for real jobs. When large-scale testing a CE, one of the objectives is to see if the CE can fully utilize all resources (cores) available to it or if there are bottlenecks preventing that outcome. However to do this would normally require using up production slots, and it is hard to find a site willing to give up so many production slots for so long. Thus, running resourceless jobs in parallel with production jobs allows the testing to proceed without interfering with real work. Setting Up a Sleeper Pool \u00b6 A sleeper pool is created by \u201ctricking\u201d a worker node into thinking it has more cores than physically available. Then, the host is configured so that jobs marked for the sleeper pool are routed to the extra slots. In HTCondor, this is done by changing the START expression on each startd. For example, on a 32-core machine: START = ( \\ (SlotID >= 1) && \\ (SlotID < 33) && \\ (RequiresWholeMachine =!= TRUE ) && \\ (SleepSlot =!= TRUE) && \\ (distro =?= \"RHEL6\" ) && \\ (CPU_Only == TRUE ) \\ ) || \\ ( (SlotID >= 33) && (distro =?= \"RHEL6\" ) && (SleepSlot == TRUE) ) Usual Topology of the Tests \u00b6 A brief introduction to the topology involved in the tests. Batch System and Sleeper Pool \u00b6 This is normally the batch system of the resources which will be behind the CE to be tested. It is normally set up by a site administrator. CE \u00b6 This is the physical hardware where the CE software runs, hopefully mimicking real production hardware specifications. Submitter \u00b6 An HTCondor submit host. It can be a virtual machine for most test submissions. Monitoring tools \u00b6 To monitor tests, two software components are needed (which can be installed on the same node): ganglia-gmond and ganglia-gmetad. Once they are installed, then some ad-hoc metrics can be created to monitor the CE; for example: condor_q -pool red.unl.edu:9619 -name sleeper@red.unl.edu -const 'JobStatus=?=2' | wc -l gmetric --name RunningJobsCE Generating Load \u00b6 Location \u00b6 The load_generators are found in the OSgscal github repo . The binary of interest here is loadtest_condor Use \u00b6 Just untar it or check it out from mas on the HTCondor submit node (see above): git checkout https://github.com/efajardo/osgscal cd load_generators/loadtest_condor/trunk/bin Keep in mind that you also need a valid proxy for grid submissions. For example, if the goal is to keep 1,000 jobs in the queue and run 6-hour sleep jobs (on average), you can run this command: ./loadtest_condor.sh -type grid condor sleeper@red.unl.edu red.unl.edu:9619 -jobs 40000 -cluster 10 -proxy /home/submituser/.globus/cmspilot01.proxy -end random 21600 -maxidle 1000 -in sandbox 50","title":"CE Scale Testing"},{"location":"software/ce-test-scaling/#how-to-run-scalability-tests-on-a-ce","text":"","title":"How to Run Scalability Tests on a CE"},{"location":"software/ce-test-scaling/#introduction","text":"This document is intended as a general overview of the process for scalability testing of an OSG CE (Compute Element). All examples are for testing an HTCondor-CE , but they should be applicable for other CE software. The focus of testing a CE is on the number of concurrent running jobs the CE can sustain as well as the ramp-up rate when many jobs are queued.","title":"Introduction"},{"location":"software/ce-test-scaling/#sleeper-pool","text":"With the focus on the CE, actual job payloads can be minimal \u2013 simple long sleep jobs are fine. Thus, then can run on nearly any resources, and it is even possible to allow far more of these jobs to run on a single resource than would be sensible for real jobs. When large-scale testing a CE, one of the objectives is to see if the CE can fully utilize all resources (cores) available to it or if there are bottlenecks preventing that outcome. However to do this would normally require using up production slots, and it is hard to find a site willing to give up so many production slots for so long. Thus, running resourceless jobs in parallel with production jobs allows the testing to proceed without interfering with real work.","title":"Sleeper Pool"},{"location":"software/ce-test-scaling/#setting-up-a-sleeper-pool","text":"A sleeper pool is created by \u201ctricking\u201d a worker node into thinking it has more cores than physically available. Then, the host is configured so that jobs marked for the sleeper pool are routed to the extra slots. In HTCondor, this is done by changing the START expression on each startd. For example, on a 32-core machine: START = ( \\ (SlotID >= 1) && \\ (SlotID < 33) && \\ (RequiresWholeMachine =!= TRUE ) && \\ (SleepSlot =!= TRUE) && \\ (distro =?= \"RHEL6\" ) && \\ (CPU_Only == TRUE ) \\ ) || \\ ( (SlotID >= 33) && (distro =?= \"RHEL6\" ) && (SleepSlot == TRUE) )","title":"Setting Up a Sleeper Pool"},{"location":"software/ce-test-scaling/#usual-topology-of-the-tests","text":"A brief introduction to the topology involved in the tests.","title":"Usual Topology of the Tests"},{"location":"software/ce-test-scaling/#batch-system-and-sleeper-pool","text":"This is normally the batch system of the resources which will be behind the CE to be tested. It is normally set up by a site administrator.","title":"Batch System and Sleeper Pool"},{"location":"software/ce-test-scaling/#ce","text":"This is the physical hardware where the CE software runs, hopefully mimicking real production hardware specifications.","title":"CE"},{"location":"software/ce-test-scaling/#submitter","text":"An HTCondor submit host. It can be a virtual machine for most test submissions.","title":"Submitter"},{"location":"software/ce-test-scaling/#monitoring-tools","text":"To monitor tests, two software components are needed (which can be installed on the same node): ganglia-gmond and ganglia-gmetad. Once they are installed, then some ad-hoc metrics can be created to monitor the CE; for example: condor_q -pool red.unl.edu:9619 -name sleeper@red.unl.edu -const 'JobStatus=?=2' | wc -l gmetric --name RunningJobsCE","title":"Monitoring tools"},{"location":"software/ce-test-scaling/#generating-load","text":"","title":"Generating Load"},{"location":"software/ce-test-scaling/#location","text":"The load_generators are found in the OSgscal github repo . The binary of interest here is loadtest_condor","title":"Location"},{"location":"software/ce-test-scaling/#use","text":"Just untar it or check it out from mas on the HTCondor submit node (see above): git checkout https://github.com/efajardo/osgscal cd load_generators/loadtest_condor/trunk/bin Keep in mind that you also need a valid proxy for grid submissions. For example, if the goal is to keep 1,000 jobs in the queue and run 6-hour sleep jobs (on average), you can run this command: ./loadtest_condor.sh -type grid condor sleeper@red.unl.edu red.unl.edu:9619 -jobs 40000 -cluster 10 -proxy /home/submituser/.globus/cmspilot01.proxy -end random 21600 -maxidle 1000 -in sandbox 50","title":"Use"},{"location":"software/container-development-guide/","text":"Container Development Guide \u00b6 This document contains instructions for OSG Technology Team members, including: How to to develop OSG Software container images that are automatically pushed to Docker Hub that adhere to our container release policy How to build a new version of an existing image How to manage tags for images in the OSG DockerHub organization Tips for container image development Creating New OSG Software Containers \u00b6 OSG Software service container images intended for OSG site admin use need to be automatically updated once per week to pick up any OS updates, as well as upon any changes to the images themselves. To do this, we use GitHub Actions to: Build new images on commits to master or main Update the docker-software-base on a schedule, which triggers builds for all image repos through repository dispatch Push container images to Docker Hub and the OSG Container Registry (Harbor) Code for new container images should now be stored in the GitHub repository opensciencegrid/images ; see below for instructions . The previous convention was to use individual GitHub repos for each image; these are described below . Add image code to the opensciencegrid/images repo \u00b6 The opensciencegrid/images repository is a central repository containing multiple container images based on the OSG Software Stack. The repository uses GitHub Actions CI to automatically build and push images, both on changes to individual images and upon updates to the upstream opensciencegrid/docker-software-base image. This repository is intended for images owned by OSG Staff with relatively simple CI needs: Images using OSG Yum repositories, especially those based on opensciencegrid/software-base Images that need tags based on the development , testing , and release tags for the supported OSG release series Images that push to Docker Hub and OSG Harbor Images that do not need CI tests See SOFTWARE-5013 for additional considerations. Creating new images from scratch \u00b6 Images are automatically built from the subdirectories of the opensciencegrid directory . A set of images will be built for each subdirectory, with each set containing multiple images based on OSG release series (e.g. 3.5 , 3.6 ) and release level (e.g. testing , release ). Fork and clone the https://github.com/opensciencegrid/images repo Create a subdirectory under opensciencegrid/ Create a README.md file describing the software provided by the image Create a LICENSE file containing the Apache 2.0 license text Create a Dockerfile building from the OSG Software Base image: ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release FROM opensciencegrid/software-base:$BASE_OSG_SERIES-<DISTRO VERSION>-$BASE_YUM_REPO # Previous instance has gone out of scope ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum install -y <PACKAGE(S)> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <DISTRO VERSION> with the Enterprise Linux version abbreviation (e.g., el7 , el8 ), and <PACKAGE(S)> with the RPM(s) you'd like to provide in this image. Hardcoding OSG series or release level If you do not want to build your image for all release series (for example, it's 3.6-only), or you do not want to build your image for all release levels (for example, always build from release), hardcode those instead of using the arguments, as in: ARG BASE_OSG_SERIES=3.6 FROM opensciencegrid/software-base:$BASE_OSG_SERIES-el8-release Adding an existing image from another repository \u00b6 If there is an existing source repository for an image that you would like to pull into the opensciencegrid/images central repository (e.g., images that make use of OSG Yum repositories), use the following instructions to retain history from the old repository. Install the git filter-repo plugin. For example, on an RPM-based operating system: yum install git-filter-repo Checkout opensciencegrid/images and your other source repository or make sure your local main branches are up-to-date cd to your other source repository and run the following: git filter-repo --to-subdirectory-filter opensciencegrid/<IMAGE NAME> cd to your local clone of the images repository and add your local repo as a remote using filesystem paths. For example: git remote add <IMAGE NAME> <PATH TO OTHER SOURCE REPO> In the images repo, create a branch based off of main for your work In the images repo, make sure your fork knows all the refs from the other source repo remote with the following: git fetch <IMAGE NAME> --tags While on your your new branch, do the merge. For example, if the main branch of your other source repository is main : git merge --allow-unrelated-histories <IMAGE NAME>/main Update the merged in Dockerfile to accept the BASE_OSG_SERIES and BASE_YUM_REPO arguments. Prepare the Docker Hub repository \u00b6 Ask the Software Manager to create a Docker Hub repo in the OSG organization. The name should generally match the subdirectory name under the images repo. Go to the permissions tab and give the robots and technology teams Read & Write access Old Image Repositories \u00b6 Some container images are stored in individual repositories under the opensciencegrid organization, with names prefixed with docker- and with the container repository topic. New images should not be created this way, but existing images may need to be updated or fixed; this section describes their layout and mechanics. Old image repos will have: A README.md file describing the software provided by the image A LICENSE file containing the Apache 2.0 license text A Dockerfile based off of the OSG Software Base image: FROM opensciencegrid/software-base:<OSG RELEASE SERIES>-<EL MAJOR VERSION>-release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum update -y && \\ yum clean all && \\ rm -rf /var/cache/yum/* RUN yum install -y <PACKAGE> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <PACKAGE> with the name of the RPM you'd like to provide in this container image, <OSG RELEASE SERIES> with the OSG release series version (e.g., 3.6 ), and <EL MAJOR VERSION> with the Enterprise Linux major version (e.g., 7 ). The BASE_OSG_SERIES and BASE_YUM_REPO arguments may or may not be used. The pre-defined Publish OSG Software container image workflow, found under the Actions tab. The user \"osg-bot\" needs to have the \"Write\" role for this repo in order to trigger automatic builds. Access to the following organizational secrets DOCKER_USERNAME DOCKER_PASSWORD OSG_HARBOR_ROBOT_USER OSG_HARBOR_ROBOT_PASSWORD The repo may also have access to the REPO_ACCESS_TOKEN organization secret, if it needs to send dispatches to another repository (e.g. docker-software-base ). A Docker Hub repository with a name matching the GitHub repo name, without the docker- prefix, with Read & Write access for the robots and technology teams. In addition, for repository dispatch from docker-software-base, they are listed in the GitHub Actions workflow for docker-software-base , in the dispatch-repo: list (under jobs: dispatch: strategy: matrix: ). Triggering Container Image Builds \u00b6 To build a new version of an existing container image , e.g. for a new RPM version of software in the container, you can kick off a new build in one of two ways: If there are no changes necessary to the container packaging: go to the GitHub repository's latest build under Actions, e.g. https://github.com/opensciencegrid/docker-frontier-squid/actions/ , and click \"Re-run jobs\" -> \"Re-run all jobs\". If changes need to be made to the container packaging: submit a pull request with your changes to the relevant GitHub repository and request that another team member review it. Once merged into master or main , a GitHub Actions build should start automatically. If the GitHub Actions build completes successfully, you should shortly see new fresh and timestamp tags appear in the DockerHub repository. Automatic weekly rebuilds If the repo's GitHub Actions are configured as above, container images will automatically rebuild, and therefore pick up new packages available in minefield once per week. Managing Tags in DockerHub \u00b6 Adding tags \u00b6 Images that have passed acceptance testing should be tagged as stable : Install the jq utility: yum install jq Get the sha256 repo digest of the image that the user has tested. All you need is the part that starts with sha256:... (aka the <DIGEST> ). A Kubernetes user can get the digest from the \"Image ID\" line obtained by running: kubectl describe pod <POD> A Docker user can get the digest by running: docker image inspect <IMAGE NAME>:<TAG> | jq '.[0].Id' (Optional) If you are tagging multiple images, you can enter your Docker Hub username and password into environment variables, to avoid having to re-type them. Otherwise the script will prompt for them. read user # enter dockerhub username read -s pass # enter dockerhub password export user pass Run the Docker container image tagging command from release-tools : ./dockerhub-tag-fresh-to-stable.sh <IMAGE NAME> <DIGEST> Removing tags \u00b6 Run the Docker container image pruning command from release-tools : ./dockerhub-prune-tags.py <IMAGE NAME> Making Slim Containers \u00b6 Here are some resources for creating slim, efficient containers: https://developers.redhat.com/blog/2016/03/09/more-about-docker-images-size/ https://github.com/opensciencegrid/topology/pull/399 https://docs.docker.com/develop/develop-images/multistage-build/","title":"Container Development Guide"},{"location":"software/container-development-guide/#container-development-guide","text":"This document contains instructions for OSG Technology Team members, including: How to to develop OSG Software container images that are automatically pushed to Docker Hub that adhere to our container release policy How to build a new version of an existing image How to manage tags for images in the OSG DockerHub organization Tips for container image development","title":"Container Development Guide"},{"location":"software/container-development-guide/#creating-new-osg-software-containers","text":"OSG Software service container images intended for OSG site admin use need to be automatically updated once per week to pick up any OS updates, as well as upon any changes to the images themselves. To do this, we use GitHub Actions to: Build new images on commits to master or main Update the docker-software-base on a schedule, which triggers builds for all image repos through repository dispatch Push container images to Docker Hub and the OSG Container Registry (Harbor) Code for new container images should now be stored in the GitHub repository opensciencegrid/images ; see below for instructions . The previous convention was to use individual GitHub repos for each image; these are described below .","title":"Creating New OSG Software Containers"},{"location":"software/container-development-guide/#add-image-code-to-the-opensciencegridimages-repo","text":"The opensciencegrid/images repository is a central repository containing multiple container images based on the OSG Software Stack. The repository uses GitHub Actions CI to automatically build and push images, both on changes to individual images and upon updates to the upstream opensciencegrid/docker-software-base image. This repository is intended for images owned by OSG Staff with relatively simple CI needs: Images using OSG Yum repositories, especially those based on opensciencegrid/software-base Images that need tags based on the development , testing , and release tags for the supported OSG release series Images that push to Docker Hub and OSG Harbor Images that do not need CI tests See SOFTWARE-5013 for additional considerations.","title":"Add image code to the opensciencegrid/images repo"},{"location":"software/container-development-guide/#creating-new-images-from-scratch","text":"Images are automatically built from the subdirectories of the opensciencegrid directory . A set of images will be built for each subdirectory, with each set containing multiple images based on OSG release series (e.g. 3.5 , 3.6 ) and release level (e.g. testing , release ). Fork and clone the https://github.com/opensciencegrid/images repo Create a subdirectory under opensciencegrid/ Create a README.md file describing the software provided by the image Create a LICENSE file containing the Apache 2.0 license text Create a Dockerfile building from the OSG Software Base image: ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release FROM opensciencegrid/software-base:$BASE_OSG_SERIES-<DISTRO VERSION>-$BASE_YUM_REPO # Previous instance has gone out of scope ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum install -y <PACKAGE(S)> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <DISTRO VERSION> with the Enterprise Linux version abbreviation (e.g., el7 , el8 ), and <PACKAGE(S)> with the RPM(s) you'd like to provide in this image. Hardcoding OSG series or release level If you do not want to build your image for all release series (for example, it's 3.6-only), or you do not want to build your image for all release levels (for example, always build from release), hardcode those instead of using the arguments, as in: ARG BASE_OSG_SERIES=3.6 FROM opensciencegrid/software-base:$BASE_OSG_SERIES-el8-release","title":"Creating new images from scratch"},{"location":"software/container-development-guide/#adding-an-existing-image-from-another-repository","text":"If there is an existing source repository for an image that you would like to pull into the opensciencegrid/images central repository (e.g., images that make use of OSG Yum repositories), use the following instructions to retain history from the old repository. Install the git filter-repo plugin. For example, on an RPM-based operating system: yum install git-filter-repo Checkout opensciencegrid/images and your other source repository or make sure your local main branches are up-to-date cd to your other source repository and run the following: git filter-repo --to-subdirectory-filter opensciencegrid/<IMAGE NAME> cd to your local clone of the images repository and add your local repo as a remote using filesystem paths. For example: git remote add <IMAGE NAME> <PATH TO OTHER SOURCE REPO> In the images repo, create a branch based off of main for your work In the images repo, make sure your fork knows all the refs from the other source repo remote with the following: git fetch <IMAGE NAME> --tags While on your your new branch, do the merge. For example, if the main branch of your other source repository is main : git merge --allow-unrelated-histories <IMAGE NAME>/main Update the merged in Dockerfile to accept the BASE_OSG_SERIES and BASE_YUM_REPO arguments.","title":"Adding an existing image from another repository"},{"location":"software/container-development-guide/#prepare-the-docker-hub-repository","text":"Ask the Software Manager to create a Docker Hub repo in the OSG organization. The name should generally match the subdirectory name under the images repo. Go to the permissions tab and give the robots and technology teams Read & Write access","title":"Prepare the Docker Hub repository"},{"location":"software/container-development-guide/#old-image-repositories","text":"Some container images are stored in individual repositories under the opensciencegrid organization, with names prefixed with docker- and with the container repository topic. New images should not be created this way, but existing images may need to be updated or fixed; this section describes their layout and mechanics. Old image repos will have: A README.md file describing the software provided by the image A LICENSE file containing the Apache 2.0 license text A Dockerfile based off of the OSG Software Base image: FROM opensciencegrid/software-base:<OSG RELEASE SERIES>-<EL MAJOR VERSION>-release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum update -y && \\ yum clean all && \\ rm -rf /var/cache/yum/* RUN yum install -y <PACKAGE> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <PACKAGE> with the name of the RPM you'd like to provide in this container image, <OSG RELEASE SERIES> with the OSG release series version (e.g., 3.6 ), and <EL MAJOR VERSION> with the Enterprise Linux major version (e.g., 7 ). The BASE_OSG_SERIES and BASE_YUM_REPO arguments may or may not be used. The pre-defined Publish OSG Software container image workflow, found under the Actions tab. The user \"osg-bot\" needs to have the \"Write\" role for this repo in order to trigger automatic builds. Access to the following organizational secrets DOCKER_USERNAME DOCKER_PASSWORD OSG_HARBOR_ROBOT_USER OSG_HARBOR_ROBOT_PASSWORD The repo may also have access to the REPO_ACCESS_TOKEN organization secret, if it needs to send dispatches to another repository (e.g. docker-software-base ). A Docker Hub repository with a name matching the GitHub repo name, without the docker- prefix, with Read & Write access for the robots and technology teams. In addition, for repository dispatch from docker-software-base, they are listed in the GitHub Actions workflow for docker-software-base , in the dispatch-repo: list (under jobs: dispatch: strategy: matrix: ).","title":"Old Image Repositories"},{"location":"software/container-development-guide/#triggering-container-image-builds","text":"To build a new version of an existing container image , e.g. for a new RPM version of software in the container, you can kick off a new build in one of two ways: If there are no changes necessary to the container packaging: go to the GitHub repository's latest build under Actions, e.g. https://github.com/opensciencegrid/docker-frontier-squid/actions/ , and click \"Re-run jobs\" -> \"Re-run all jobs\". If changes need to be made to the container packaging: submit a pull request with your changes to the relevant GitHub repository and request that another team member review it. Once merged into master or main , a GitHub Actions build should start automatically. If the GitHub Actions build completes successfully, you should shortly see new fresh and timestamp tags appear in the DockerHub repository. Automatic weekly rebuilds If the repo's GitHub Actions are configured as above, container images will automatically rebuild, and therefore pick up new packages available in minefield once per week.","title":"Triggering Container Image Builds"},{"location":"software/container-development-guide/#managing-tags-in-dockerhub","text":"","title":"Managing Tags in DockerHub"},{"location":"software/container-development-guide/#adding-tags","text":"Images that have passed acceptance testing should be tagged as stable : Install the jq utility: yum install jq Get the sha256 repo digest of the image that the user has tested. All you need is the part that starts with sha256:... (aka the <DIGEST> ). A Kubernetes user can get the digest from the \"Image ID\" line obtained by running: kubectl describe pod <POD> A Docker user can get the digest by running: docker image inspect <IMAGE NAME>:<TAG> | jq '.[0].Id' (Optional) If you are tagging multiple images, you can enter your Docker Hub username and password into environment variables, to avoid having to re-type them. Otherwise the script will prompt for them. read user # enter dockerhub username read -s pass # enter dockerhub password export user pass Run the Docker container image tagging command from release-tools : ./dockerhub-tag-fresh-to-stable.sh <IMAGE NAME> <DIGEST>","title":"Adding tags"},{"location":"software/container-development-guide/#removing-tags","text":"Run the Docker container image pruning command from release-tools : ./dockerhub-prune-tags.py <IMAGE NAME>","title":"Removing tags"},{"location":"software/container-development-guide/#making-slim-containers","text":"Here are some resources for creating slim, efficient containers: https://developers.redhat.com/blog/2016/03/09/more-about-docker-images-size/ https://github.com/opensciencegrid/topology/pull/399 https://docs.docker.com/develop/develop-images/multistage-build/","title":"Making Slim Containers"},{"location":"software/create-vo-client/","text":"Creating the VO Client Package \u00b6 Overview \u00b6 This document will explain the step-by-step procedures for creating and releasing the VO Client Package. The VO Client Package sources can be found here: https://github.com/opensciencegrid/osg-vo-config When upstream changes have been made and are ready for a new VO Client Package release, these sources will be used to prepare a release tarball, which will in turn be used for the RPMs. In order to build the RPM, one needs: The tarball containing the: edg-mkgridmap.conf file gums.config.template file grid-vorolemap file (generated) voms-mapfile-default file (generated) vomses file vomsdir directory tree, containing the .lsc files. The RPM spec file, maintained in the OSG packaging area. JIRA Ticket for the Release \u00b6 There should be an associated JIRA ticket with a summary line of the form \"Release VO Package 85\". (Throughout this document, this release number will be referred to as <NN> .) The JIRA ticket should contain the details of the changes expected in the new VO Client Package release, which you should verify before proceeding. You can verify this with your favorite git tool (eg, git diff or gitk ), or just view the changes directly on GitHub: https://github.com/opensciencegrid/osg-vo-config/compare/release-84...master Here, release-84 is the previous release tag, which you are comparing to the latest changes in master . To use GitHub to view the comparison, you need to specify whatever is the most recent previous release tag. Alternatively, you can proceed to make the tarball , and compare the result to the previous vo-client tarball (from the upstream source cache) before publishing the new release . However you choose to do it, the point is to verify that the changes going into the release match what is expected in the JIRA ticket before publishing a new release. Updates to the GUMS Template \u00b6 Most commonly, VO Client Package releases do not involve changes to the gums.config.template file, though on occasion it needs to be updated. Before proceeding, any changes to gums.config.template related to this release should be committed to git and pushed to the upstream repo on GitHub. The procedure for updating gums.config.template is outside the scope of this document, but the main important point is that any updates to this file should be done with the GUMS web interface rather than editing its xml contents by hand. Making the Tarball \u00b6 The process to make a new tarball has been mostly scripted. To make the tarball: Start with a clean checkout of the latest master branch of the osg-vo-config source repo . This checked out commit should be the one intended to be tagged for the new release. - Run the mk-vo-client-tarball script with the new release number <NN> : $ ./bin/mk-vo-client-tarball <NN> For example: $ ./bin/mk-vo-client-tarball 85 This will create a file vo-client-<NN>-osg.tar.gz in the current directory. Once the tarball is created: If you have not already verified the changes expected in the JIRA ticket, compare the contents of the new tarball with the previous version in the upstream source cache . Upload the tarball into the upstream source cache , under the vo-client/<NN>/ directory. RPM Spec File Maintenance \u00b6 The OSG RPM spec file is maintained in Subversion . The VO Client package is located in native/redhat/trunk/vo-client ; that is, here . There are two files that need to be maintained: osg/vo-client.spec The Version: field should be updated to match the <NN> number for the release A %changelog entry should be added for the new release, mentioning any changes and their associated tickets upstream/release_tarball.source Update the relative path for the new tarball within the upstream source cache . Typically this will be vo-client/<NN>/vo-client-<NN>-osg.tar.gz . RPM Building \u00b6 After installing the osg-build tools , check out a clean copy of the vo-client packaging directory from svn, then: osg-build prebuild . Once there are no errors, run osg-build koji . --scratch . (This can be done without making any permanent change.) Once that builds successfully, run osg-build koji . (This is permanent, unlike when you ran with --scratch .) You cannot rebuild this version of the RPM again; to rebuild with changes, you must bump the release number and edit the changelog. This will push the RPMs into the OSG development repository. Note Koji requires additional setup compared to rpmbuild; see the documentation here . Publishing the New Release \u00b6 The final version of the sources in the osg-vo-config , which was used to create the tarball that was used in the koji build, needs be tagged in git with a release-<NN> tag (eg, release-85 ) and published as a release on GitHub. You can create and push the release-<NN> from your git checkout of osg-vo-config , OR create the tag while publishing the release on GitHub (recommended). To publish the new release on GitHub: Go to https://github.com/opensciencegrid/osg-vo-config/releases/new In the \"Tag version\" field, enter release-<NN> (eg, release-85 ) If you are creating this tag on GitHub, click the \"Target\" dropdown button, and under the \"Recent Commits\" tab, make sure to select the commit you used when creating the tarball (It should be the first one) In the \"Release title\" field, enter <MONTH> <YEAR> VO Package Release <NN> (eg, December 2018 VO Package Release 85 ) In the release description, list the changes in this release and their associated ticket numbers, similar to the new %changelog entry added in the rpm spec file (You can view the releases page for examples) - Click the \"Publish release\" button Promotion to Testing and Release: \u00b6 Read Release Policy . Note that the vo-client package frequently is part of a separate -data release; it does not necessarily have to wait for the main release cycle.","title":"Creating the VO Client Package"},{"location":"software/create-vo-client/#creating-the-vo-client-package","text":"","title":"Creating the VO Client Package"},{"location":"software/create-vo-client/#overview","text":"This document will explain the step-by-step procedures for creating and releasing the VO Client Package. The VO Client Package sources can be found here: https://github.com/opensciencegrid/osg-vo-config When upstream changes have been made and are ready for a new VO Client Package release, these sources will be used to prepare a release tarball, which will in turn be used for the RPMs. In order to build the RPM, one needs: The tarball containing the: edg-mkgridmap.conf file gums.config.template file grid-vorolemap file (generated) voms-mapfile-default file (generated) vomses file vomsdir directory tree, containing the .lsc files. The RPM spec file, maintained in the OSG packaging area.","title":"Overview"},{"location":"software/create-vo-client/#jira-ticket-for-the-release","text":"There should be an associated JIRA ticket with a summary line of the form \"Release VO Package 85\". (Throughout this document, this release number will be referred to as <NN> .) The JIRA ticket should contain the details of the changes expected in the new VO Client Package release, which you should verify before proceeding. You can verify this with your favorite git tool (eg, git diff or gitk ), or just view the changes directly on GitHub: https://github.com/opensciencegrid/osg-vo-config/compare/release-84...master Here, release-84 is the previous release tag, which you are comparing to the latest changes in master . To use GitHub to view the comparison, you need to specify whatever is the most recent previous release tag. Alternatively, you can proceed to make the tarball , and compare the result to the previous vo-client tarball (from the upstream source cache) before publishing the new release . However you choose to do it, the point is to verify that the changes going into the release match what is expected in the JIRA ticket before publishing a new release.","title":"JIRA Ticket for the Release"},{"location":"software/create-vo-client/#updates-to-the-gums-template","text":"Most commonly, VO Client Package releases do not involve changes to the gums.config.template file, though on occasion it needs to be updated. Before proceeding, any changes to gums.config.template related to this release should be committed to git and pushed to the upstream repo on GitHub. The procedure for updating gums.config.template is outside the scope of this document, but the main important point is that any updates to this file should be done with the GUMS web interface rather than editing its xml contents by hand.","title":"Updates to the GUMS Template"},{"location":"software/create-vo-client/#making-the-tarball","text":"The process to make a new tarball has been mostly scripted. To make the tarball: Start with a clean checkout of the latest master branch of the osg-vo-config source repo . This checked out commit should be the one intended to be tagged for the new release. - Run the mk-vo-client-tarball script with the new release number <NN> : $ ./bin/mk-vo-client-tarball <NN> For example: $ ./bin/mk-vo-client-tarball 85 This will create a file vo-client-<NN>-osg.tar.gz in the current directory. Once the tarball is created: If you have not already verified the changes expected in the JIRA ticket, compare the contents of the new tarball with the previous version in the upstream source cache . Upload the tarball into the upstream source cache , under the vo-client/<NN>/ directory.","title":"Making the Tarball"},{"location":"software/create-vo-client/#rpm-spec-file-maintenance","text":"The OSG RPM spec file is maintained in Subversion . The VO Client package is located in native/redhat/trunk/vo-client ; that is, here . There are two files that need to be maintained: osg/vo-client.spec The Version: field should be updated to match the <NN> number for the release A %changelog entry should be added for the new release, mentioning any changes and their associated tickets upstream/release_tarball.source Update the relative path for the new tarball within the upstream source cache . Typically this will be vo-client/<NN>/vo-client-<NN>-osg.tar.gz .","title":"RPM Spec File Maintenance"},{"location":"software/create-vo-client/#rpm-building","text":"After installing the osg-build tools , check out a clean copy of the vo-client packaging directory from svn, then: osg-build prebuild . Once there are no errors, run osg-build koji . --scratch . (This can be done without making any permanent change.) Once that builds successfully, run osg-build koji . (This is permanent, unlike when you ran with --scratch .) You cannot rebuild this version of the RPM again; to rebuild with changes, you must bump the release number and edit the changelog. This will push the RPMs into the OSG development repository. Note Koji requires additional setup compared to rpmbuild; see the documentation here .","title":"RPM Building"},{"location":"software/create-vo-client/#publishing-the-new-release","text":"The final version of the sources in the osg-vo-config , which was used to create the tarball that was used in the koji build, needs be tagged in git with a release-<NN> tag (eg, release-85 ) and published as a release on GitHub. You can create and push the release-<NN> from your git checkout of osg-vo-config , OR create the tag while publishing the release on GitHub (recommended). To publish the new release on GitHub: Go to https://github.com/opensciencegrid/osg-vo-config/releases/new In the \"Tag version\" field, enter release-<NN> (eg, release-85 ) If you are creating this tag on GitHub, click the \"Target\" dropdown button, and under the \"Recent Commits\" tab, make sure to select the commit you used when creating the tarball (It should be the first one) In the \"Release title\" field, enter <MONTH> <YEAR> VO Package Release <NN> (eg, December 2018 VO Package Release 85 ) In the release description, list the changes in this release and their associated ticket numbers, similar to the new %changelog entry added in the rpm spec file (You can view the releases page for examples) - Click the \"Publish release\" button","title":"Publishing the New Release"},{"location":"software/create-vo-client/#promotion-to-testing-and-release","text":"Read Release Policy . Note that the vo-client package frequently is part of a separate -data release; it does not necessarily have to wait for the main release cycle.","title":"Promotion to Testing and Release:"},{"location":"software/development-process/","text":"Software Development Process \u00b6 This page is for the OSG Software team and other contributors to the OSG software stack. It is meant to be the central source for all development processes for the Software team. (But right now, it is just a starting point.) Overall Development Cycle \u00b6 For a typical update to an existing package, the overall development cycle is roughly as follows: Download the new upstream source (tarball, source RPM, checkout) into the UW AFS upstream area In a checkout of our packaging code , update the reference to the upstream file and, as needed, the RPM spec file Use osg-build to perform a scratch build of the updated package Verify that the build succeeded; if not, redo previous steps until success Optionally, lightly test the new RPM(s); if there are problems, redo previous steps until success Use osg-build to perform an official build of the updated package (which will go into the development repos) Perform standard developer testing of the new RPM(s) \u2014 see below for details Obtain permission from the Software Manager to promote the package Promote the package to testing \u2014 see below for details Versioning Guidelines \u00b6 OSG-owned software should contain three digits, X.Y.Z, where X represents the major version, Y the minor version, and Z the maintenance version. New releases of software should increment one of the major, minor, or maintenance according to the following guidelines: Major: Major new software, typically (but not limited to) full rewrites, new architectures, major new features; can certainly break backward compatibility (but should provide a smooth upgrade path). Worthy of introduction into Upcoming. Minor: Notable changes to the software, including significant feature changes, API changes, etc.; may break compatibility, but must provide an upgrade path from other versions within the same Major series. Maintenance: Bug fixes, minor feature tweaks, etc.; must not break compatibility with other versions within the same Major.Minor series. If you are unsure about which version number to increment in a software update, consult the Software Manager. Build Procedures \u00b6 Building packages for multiple OSG release series \u00b6 The OSG Software team supports multiple release series, independent but in parallel to a large degree. In many cases, a single package is the same across release series, and therefore we want to build the package once and share it among the series. The procedure below suggests a way to accomplish this task. Current definitions: maintenance: OSG 3.4 ( trunk ) current: OSG 3.5 ( branches/osg-3.5 ) Procedure: Make changes to trunk Optionally, make and test a scratch build from trunk Commit the changes Make an official build from trunk (e.g.: osg-build koji <PACKAGE> ) Perform the standard 4 tests for the current series (see below) Merge the relevant commits from trunk into the maintenance branch (see below for tips) Optionally, make and test a scratch build from the maintenance branch Commit the merge Make an official build from the maintenance branch (e.g.: osg-build koji --repo=3.4 <PACKAGE> ) Perform the standard 4 tests for the maintenance series (see below) As needed (or directed by the Software manager), perform the cross-series tests (see below) Note Do not change the RPM Release number in the maintenance branch before rebuilding; the %dist tag will differ automatically, and hence the maintenance and current NVRs will not conflict. Merging changes from one release series to another \u00b6 These instructions assume that you are merging from trunk to branches/osg-3.5 . They also assume that the current directory you are in is a checkout of branches/osg-3.5 . I will use $pkg to refer to the name of your package. First, you will need the commit numbers for your changes: svn log \\^/native/redhat/trunk/$pkg | less Write down the commits you want to merge. If you only have one commit, merge that commit with -c as follows: svn merge -c $commit_num \\^/native/redhat/trunk/$pkg $pkg Where $commit_num is the SVN revision number of that commit (e.g. 17000). Merging an individual change like this is referred to as \"cherry-picking\". If you have a range of commits and you wish to merge all commits within that range, then do the following: svn merge -r $start_num:$end_num \\^/native/redhat/trunk/$pkg $pkg Where $start_num is the SVN revision of the commit BEFORE your first commit, and $end_num is the SVN revision of your last commit in that range. Note: Be very careful when merging a range from trunk into the maintenance branch so that you do not introduce more changes to the maintenance branch than are necessary. If you have multiple commits but they are not contiguous (i.e. there are commits made by you or someone else in that range that you do not want to merge), you will need to cherry-pick each individual commit. svn merge -c $commit1 \\^/native/redhat/trunk/$pkg $pkg svn merge -c $commit2 \\^/native/redhat/trunk/$pkg $pkg ... Where $commit1 , $commit2 are the commit numbers of the individual changes. Note that merge tracking in recent versions of SVN (1.5 or newer) should prevent commits from accidentally being merged multiple times. You should still look out for conflicts and examine the changes via svn diff before committing the merge. Testing Procedures \u00b6 Before promoting a package to a testing repository, each build must be tested lightly from the development repos to make sure that it is not completely broken, thereby wasting time during acceptance testing. Normally, the person who builds a package performs the development testing. If you are not doing your own development testing for a package , contact the Software Manager and/or leave a comment in the associated ticket; otherwise, your package may never be promoted to testing and hence never released. The \"Standard 4\" tests, defined \u00b6 In most cases, the Software manager will ask a developer to perform the \u201cstandard 4\u201d tests on an updated package in a release series before promotion. This is a shorthand description for a standard set of 4 test runs: Fresh install on el6 Fresh install on el7 Update install on el6 Update install on el7 An \u201cupdate install\u201d is a fresh install of the relevant package (or better yet, metapackage that includes it) from the production repository , followed by an update to the new build from the development repository . For each test run, the amount of functional testing required will vary. For very simple changes, it may be sufficient to verify that each installation succeeds and that the expected files are in place For some changes, it may be sufficient to run osg-test on the resulting installation For some changes, it will be necessary to perform careful functional tests of the affected component(s) If you have questions, check with the Software Manager to determine the amount of testing that is required per test run. The \"Cross-Series\" test, defined \u00b6 The cross-series test may need to be run for packages that have been built for multiple release series of the OSG software stack (i.e. 3.4 and 3.5): On el7, install from the 3.4 repositories, then update from the 3.5 repositories Viewed another way, this test is similar to the update installs, above, except from 3.4-release to 3.5-development. The \"Long Tail\" tests, defined \u00b6 These tests may need to be run when updating a package that's also in the old, unsupported (3.3) branch. They will consist of: Install from 3.3-release and update to 3.5-development (on el7 only) The \"full set of tests\", defined \u00b6 All of the tests mentioned above. Running the tests in VM Universe \u00b6 In the case that the package you're testing is covered by osg-tested-internal, you can run the full set of tests in a manual VM universe test run. Make sure you meet the pre-requisites required to submit VM Universe jobs on osghost.chtc.wisc.edu . After that's done, prepare the test suite with a comment describing the test run. For example, if you were testing a new htcondor-ce package: osg-run-tests 'Testing htcondor-ce-3.2.1-1' After you cd into the directory specified in the output of the previous command, you will need to edit the *.yaml files in parameters.d to reflect the tests that you will want to run, i.e. clean installs, upgrade installs and upgrade installs between OSG versions. Once you're satisfied with your list of parameters, submit the dag: condor_submit_dag master-run.dag Promoting a Package to Testing \u00b6 Once development and development testing is complete, the final OSG Software step is to promote the package(s) to our testing repositories. After that, the Release team takes over with acceptance testing and ultimately release. Of course if they discover problems, the ticket(s) will be returned to OSG Software for further development, essentially restarting the development cycle. Preparing a Good Promotion Request \u00b6 Developers must obtain permission from the OSG Software manager to promote a package from development to testing. A promotion request goes into at least one affected JIRA ticket and will be answered there as well. Below are some tips for writing a good promotion request: Make sure that relevant information about goals, history, and resolution is in the associated ticket(s) Include globs for the NVRs to be promoted (or a detailed list, if it is that complicated, which it almost never is) If you ran automated tests: Link to the results page(s) Verify that relevant tests ran successfully (as opposed to being skipped or failing) \u2013 briefly summarize your findings Note whether the automated tests are just regression tests or actually test the current change(s) If there are any failures, explain why they are not important to the promotion request If you ran manual tests: Summarize your tests and findings If there were failures, explain why they are not important to the promotion request If there are critical build dependencies that we typically check, include reports from the built-against-pkgs tool Note: This step is really just for known, specific cases, like the {HTCondor, BLAHP} set Occasionally, the OSG Software manager will request the tool to be run for other cases If other packages depend on the to-be-promoted package, explain whether the dependent packages must be rebuilt or, if not, why not For example (hypothetical promotion request for HTCondor-CE): May I promote htcondor-ce-2.3.4-2.osg3*.el* ? I ran a complete set of automated tests <LINK THE PRECEDING TEXT OR SEPARATELY HERE>; the HTCondor-CE tests ran and passed in all cases. There were some spurious failures of RSV in the All condition for RHEL 6, but this is a known failure case that is independent of HTCondor-CE. I also did a few spot checks manually (one VM each for SL 6 and SL 7), and in each case setting use_frobnosticator = true in the configuration resulted in the expected behavior as defined in the description field above. The built-against-pkgs tool shows that I built against all the latest HTCondor and BLAHP builds, see below. <JIRA-formatted table comes after> Promoting \u00b6 Follow these steps to request promotion, promote a package, and note the promotion in JIRA: Make sure the package update has at least one associated JIRA ticket; if there is no ticket, at least create one for releasing the package(s) Obtain permission to promote the package(s) from the Software Manager (see above) Use osg-promote to promote the package(s) from development to testing Comment on the associated JIRA ticket(s) with osg-promote's JIRA-formatted output (or at least the build NVRs) and, if you know, suggestions for acceptance testing Update the JIRA ticket description with a bulleted list describing changes in the promoted version(s) compared to the currently released version(s) Mark each associated JIRA ticket as \u201cReady For Testing\u201d","title":"Development Process"},{"location":"software/development-process/#software-development-process","text":"This page is for the OSG Software team and other contributors to the OSG software stack. It is meant to be the central source for all development processes for the Software team. (But right now, it is just a starting point.)","title":"Software Development Process"},{"location":"software/development-process/#overall-development-cycle","text":"For a typical update to an existing package, the overall development cycle is roughly as follows: Download the new upstream source (tarball, source RPM, checkout) into the UW AFS upstream area In a checkout of our packaging code , update the reference to the upstream file and, as needed, the RPM spec file Use osg-build to perform a scratch build of the updated package Verify that the build succeeded; if not, redo previous steps until success Optionally, lightly test the new RPM(s); if there are problems, redo previous steps until success Use osg-build to perform an official build of the updated package (which will go into the development repos) Perform standard developer testing of the new RPM(s) \u2014 see below for details Obtain permission from the Software Manager to promote the package Promote the package to testing \u2014 see below for details","title":"Overall Development Cycle"},{"location":"software/development-process/#versioning-guidelines","text":"OSG-owned software should contain three digits, X.Y.Z, where X represents the major version, Y the minor version, and Z the maintenance version. New releases of software should increment one of the major, minor, or maintenance according to the following guidelines: Major: Major new software, typically (but not limited to) full rewrites, new architectures, major new features; can certainly break backward compatibility (but should provide a smooth upgrade path). Worthy of introduction into Upcoming. Minor: Notable changes to the software, including significant feature changes, API changes, etc.; may break compatibility, but must provide an upgrade path from other versions within the same Major series. Maintenance: Bug fixes, minor feature tweaks, etc.; must not break compatibility with other versions within the same Major.Minor series. If you are unsure about which version number to increment in a software update, consult the Software Manager.","title":"Versioning Guidelines"},{"location":"software/development-process/#build-procedures","text":"","title":"Build Procedures"},{"location":"software/development-process/#building-packages-for-multiple-osg-release-series","text":"The OSG Software team supports multiple release series, independent but in parallel to a large degree. In many cases, a single package is the same across release series, and therefore we want to build the package once and share it among the series. The procedure below suggests a way to accomplish this task. Current definitions: maintenance: OSG 3.4 ( trunk ) current: OSG 3.5 ( branches/osg-3.5 ) Procedure: Make changes to trunk Optionally, make and test a scratch build from trunk Commit the changes Make an official build from trunk (e.g.: osg-build koji <PACKAGE> ) Perform the standard 4 tests for the current series (see below) Merge the relevant commits from trunk into the maintenance branch (see below for tips) Optionally, make and test a scratch build from the maintenance branch Commit the merge Make an official build from the maintenance branch (e.g.: osg-build koji --repo=3.4 <PACKAGE> ) Perform the standard 4 tests for the maintenance series (see below) As needed (or directed by the Software manager), perform the cross-series tests (see below) Note Do not change the RPM Release number in the maintenance branch before rebuilding; the %dist tag will differ automatically, and hence the maintenance and current NVRs will not conflict.","title":"Building packages for multiple OSG release series"},{"location":"software/development-process/#merging-changes-from-one-release-series-to-another","text":"These instructions assume that you are merging from trunk to branches/osg-3.5 . They also assume that the current directory you are in is a checkout of branches/osg-3.5 . I will use $pkg to refer to the name of your package. First, you will need the commit numbers for your changes: svn log \\^/native/redhat/trunk/$pkg | less Write down the commits you want to merge. If you only have one commit, merge that commit with -c as follows: svn merge -c $commit_num \\^/native/redhat/trunk/$pkg $pkg Where $commit_num is the SVN revision number of that commit (e.g. 17000). Merging an individual change like this is referred to as \"cherry-picking\". If you have a range of commits and you wish to merge all commits within that range, then do the following: svn merge -r $start_num:$end_num \\^/native/redhat/trunk/$pkg $pkg Where $start_num is the SVN revision of the commit BEFORE your first commit, and $end_num is the SVN revision of your last commit in that range. Note: Be very careful when merging a range from trunk into the maintenance branch so that you do not introduce more changes to the maintenance branch than are necessary. If you have multiple commits but they are not contiguous (i.e. there are commits made by you or someone else in that range that you do not want to merge), you will need to cherry-pick each individual commit. svn merge -c $commit1 \\^/native/redhat/trunk/$pkg $pkg svn merge -c $commit2 \\^/native/redhat/trunk/$pkg $pkg ... Where $commit1 , $commit2 are the commit numbers of the individual changes. Note that merge tracking in recent versions of SVN (1.5 or newer) should prevent commits from accidentally being merged multiple times. You should still look out for conflicts and examine the changes via svn diff before committing the merge.","title":"Merging changes from one release series to another"},{"location":"software/development-process/#testing-procedures","text":"Before promoting a package to a testing repository, each build must be tested lightly from the development repos to make sure that it is not completely broken, thereby wasting time during acceptance testing. Normally, the person who builds a package performs the development testing. If you are not doing your own development testing for a package , contact the Software Manager and/or leave a comment in the associated ticket; otherwise, your package may never be promoted to testing and hence never released.","title":"Testing Procedures"},{"location":"software/development-process/#the-standard-4-tests-defined","text":"In most cases, the Software manager will ask a developer to perform the \u201cstandard 4\u201d tests on an updated package in a release series before promotion. This is a shorthand description for a standard set of 4 test runs: Fresh install on el6 Fresh install on el7 Update install on el6 Update install on el7 An \u201cupdate install\u201d is a fresh install of the relevant package (or better yet, metapackage that includes it) from the production repository , followed by an update to the new build from the development repository . For each test run, the amount of functional testing required will vary. For very simple changes, it may be sufficient to verify that each installation succeeds and that the expected files are in place For some changes, it may be sufficient to run osg-test on the resulting installation For some changes, it will be necessary to perform careful functional tests of the affected component(s) If you have questions, check with the Software Manager to determine the amount of testing that is required per test run.","title":"The \"Standard 4\" tests, defined"},{"location":"software/development-process/#the-cross-series-test-defined","text":"The cross-series test may need to be run for packages that have been built for multiple release series of the OSG software stack (i.e. 3.4 and 3.5): On el7, install from the 3.4 repositories, then update from the 3.5 repositories Viewed another way, this test is similar to the update installs, above, except from 3.4-release to 3.5-development.","title":"The \"Cross-Series\" test, defined"},{"location":"software/development-process/#the-long-tail-tests-defined","text":"These tests may need to be run when updating a package that's also in the old, unsupported (3.3) branch. They will consist of: Install from 3.3-release and update to 3.5-development (on el7 only)","title":"The \"Long Tail\" tests, defined"},{"location":"software/development-process/#the-full-set-of-tests-defined","text":"All of the tests mentioned above.","title":"The \"full set of tests\", defined"},{"location":"software/development-process/#running-the-tests-in-vm-universe","text":"In the case that the package you're testing is covered by osg-tested-internal, you can run the full set of tests in a manual VM universe test run. Make sure you meet the pre-requisites required to submit VM Universe jobs on osghost.chtc.wisc.edu . After that's done, prepare the test suite with a comment describing the test run. For example, if you were testing a new htcondor-ce package: osg-run-tests 'Testing htcondor-ce-3.2.1-1' After you cd into the directory specified in the output of the previous command, you will need to edit the *.yaml files in parameters.d to reflect the tests that you will want to run, i.e. clean installs, upgrade installs and upgrade installs between OSG versions. Once you're satisfied with your list of parameters, submit the dag: condor_submit_dag master-run.dag","title":"Running the tests in VM Universe"},{"location":"software/development-process/#promoting-a-package-to-testing","text":"Once development and development testing is complete, the final OSG Software step is to promote the package(s) to our testing repositories. After that, the Release team takes over with acceptance testing and ultimately release. Of course if they discover problems, the ticket(s) will be returned to OSG Software for further development, essentially restarting the development cycle.","title":"Promoting a Package to Testing"},{"location":"software/development-process/#preparing-a-good-promotion-request","text":"Developers must obtain permission from the OSG Software manager to promote a package from development to testing. A promotion request goes into at least one affected JIRA ticket and will be answered there as well. Below are some tips for writing a good promotion request: Make sure that relevant information about goals, history, and resolution is in the associated ticket(s) Include globs for the NVRs to be promoted (or a detailed list, if it is that complicated, which it almost never is) If you ran automated tests: Link to the results page(s) Verify that relevant tests ran successfully (as opposed to being skipped or failing) \u2013 briefly summarize your findings Note whether the automated tests are just regression tests or actually test the current change(s) If there are any failures, explain why they are not important to the promotion request If you ran manual tests: Summarize your tests and findings If there were failures, explain why they are not important to the promotion request If there are critical build dependencies that we typically check, include reports from the built-against-pkgs tool Note: This step is really just for known, specific cases, like the {HTCondor, BLAHP} set Occasionally, the OSG Software manager will request the tool to be run for other cases If other packages depend on the to-be-promoted package, explain whether the dependent packages must be rebuilt or, if not, why not For example (hypothetical promotion request for HTCondor-CE): May I promote htcondor-ce-2.3.4-2.osg3*.el* ? I ran a complete set of automated tests <LINK THE PRECEDING TEXT OR SEPARATELY HERE>; the HTCondor-CE tests ran and passed in all cases. There were some spurious failures of RSV in the All condition for RHEL 6, but this is a known failure case that is independent of HTCondor-CE. I also did a few spot checks manually (one VM each for SL 6 and SL 7), and in each case setting use_frobnosticator = true in the configuration resulted in the expected behavior as defined in the description field above. The built-against-pkgs tool shows that I built against all the latest HTCondor and BLAHP builds, see below. <JIRA-formatted table comes after>","title":"Preparing a Good Promotion Request"},{"location":"software/development-process/#promoting","text":"Follow these steps to request promotion, promote a package, and note the promotion in JIRA: Make sure the package update has at least one associated JIRA ticket; if there is no ticket, at least create one for releasing the package(s) Obtain permission to promote the package(s) from the Software Manager (see above) Use osg-promote to promote the package(s) from development to testing Comment on the associated JIRA ticket(s) with osg-promote's JIRA-formatted output (or at least the build NVRs) and, if you know, suggestions for acceptance testing Update the JIRA ticket description with a bulleted list describing changes in the promoted version(s) compared to the currently released version(s) Mark each associated JIRA ticket as \u201cReady For Testing\u201d","title":"Promoting"},{"location":"software/effort-tracking/","text":"Effort Tracking \u00b6 This page describes a simple plan for tracking effort in the OSG Technology teams. Basic Ideas \u00b6 At its simplest, we would like to understand how much effort is spent on various OSG Technology activities over time. The focus is on having reasonably accurate, unbiased data. We might use the data later, for example, to hone future OSG proposals. And of course, all federal funding is subject to effort tracking. There are just a few simple ideas to keep in mind: Each week, report your effort on OSG Technology activities Update your numbers in the effort tracking google spreadsheet (ask BrianL for access) and include a section in your weekly status report; here is an example: EFFORT External development: 63% Support: 12% Leave: 20% Outside: 5 Follow standard federal regulations for calculating effort (e.g., OMB Circular A-21) The main idea is that all of your job-related activity for a week equals 100%, whether that is exactly 40 hours of work, a little less (subject to your local institution\u2019s rules), or more. This implies that the same hours worked could result in different effort percentages reported from week to week; for example, 4 hours in a 40-hour week is 10%, but 4 hours in a 50-hour week (which I hope is exceedingly rare) is 8%. Report 100% of your effort each week, but note that all effort outside of the Technology area falls into a single category. Unless you work at UW\u2013Madison, we do not need to know any details about your effort outside of the Technology area. (BrianL will talk to UW\u2013Madison folks about local expectations.) If you are assigned to the Technology area for less than 100%, please report your actual Technology effort accurately. Workloads vary from week to week. For example, suppose you are 50% Technology in general, but you actually work 24 hours in a 40-hour week; you should report 60% effort for that week. The goal is to present reality, not what you think management wants to see. Effort is reported as integer percentages, no less accurate than 5% intervals So please do not report percentages like 43.21% and please do not round to the nearest 10%. Effort Categories \u00b6 Here are the categories in which to track effort: Investigations Work on the Investigations team External Software work that (generally) benefits our users; e.g., creating packages; updating existing ones; designing, coding, and testing new tools, existing tools, patches, or our software components Internal Software work on tools that we use to get work done; e.g., working on osg-test (for now), osg-build, Koji maintenance, the UW or UC ITB instances Documentation Work on our TWiki or Markdown documentation Release Release team activities, primarily acceptance testing and cutting releases Support User support, including working on GOC tickets, direct support emails, some JIRA tickets that are more support than development, etc. It might be tricky to decide when support work becomes development work; generally, once a support ticket turns into a JIRA ticket and goes through the normal development lifecycle, then the JIRA-based work is development. If there is still extensive communication with GOC ticket users, that is still support. Management This is mainly for team leads; e.g., managing team activities and tickets (generally); hiring; leading (not just attending) meetings Education Not for general learning or training activities The OSG Education area is essentially part of the Software area, because many technology-area members contribute to the OSG School. So this category is for OSG School effort (or other sanctioned OSG Education activities. Admin General administrative activities that benefit the OSG Technology area but that do not fit elsewhere \u2014 use sparingly!! Outside For all activities outside of the OSG Technology area (Madison team members should provide extra details, see BrianL) Leave This is for holidays, vacation, and sick leave; count a full day of leave as 8.0 hours, count a half day as 4.0 hours A few thoughts about tricky situations: Meetings. If a meeting is specific to one of the categories above, use that category. If the meeting is more general (e.g., the weekly Monday meeting, or the OSG AHM), amortize your time according to your usual breakdown by category. For example, someone who spends nearly all of their time working on development tasks should count the Monday meeting as development time. Administrative activities. This is probably the trickiest category. It certainly covers any administrative work that pertains to your activity in the OSG Technology area. But what about administrative activities that pertain to your employment in general, and not to any particular activity? In that case, and that case only, you should amortize the administrative activity between Admin and Outside according to either (a) your appointment percentages between OSG Technology and non-Technology activities, or (b) your actual percentages between OSG Technology and non-Technology activities. Outside (non-Technology) activities that benefit the OSG Technology area. The simplest approach is to amortize the time. The more correct approach is to figure out where credit will be given for the work; if the OSG Annual Report will describe the work in one of the Technology sections, then it should be a Technology category; otherwise not. Learning activities. Put short amounts of learning time in their relevant development category. For instance, if Igor is showing Edgar how to use GlideTester, that goes into Internal . But for longer training events, or for events that are less obviously related to day-to-day activities, mark the time as Admin , and maybe add a comment explaining the activity. Ultimately, if you are not sure how to deal with a situation, ask BrianL and he will make something up and document it here (generically) for future reference.","title":"Effort Tracking"},{"location":"software/effort-tracking/#effort-tracking","text":"This page describes a simple plan for tracking effort in the OSG Technology teams.","title":"Effort Tracking"},{"location":"software/effort-tracking/#basic-ideas","text":"At its simplest, we would like to understand how much effort is spent on various OSG Technology activities over time. The focus is on having reasonably accurate, unbiased data. We might use the data later, for example, to hone future OSG proposals. And of course, all federal funding is subject to effort tracking. There are just a few simple ideas to keep in mind: Each week, report your effort on OSG Technology activities Update your numbers in the effort tracking google spreadsheet (ask BrianL for access) and include a section in your weekly status report; here is an example: EFFORT External development: 63% Support: 12% Leave: 20% Outside: 5 Follow standard federal regulations for calculating effort (e.g., OMB Circular A-21) The main idea is that all of your job-related activity for a week equals 100%, whether that is exactly 40 hours of work, a little less (subject to your local institution\u2019s rules), or more. This implies that the same hours worked could result in different effort percentages reported from week to week; for example, 4 hours in a 40-hour week is 10%, but 4 hours in a 50-hour week (which I hope is exceedingly rare) is 8%. Report 100% of your effort each week, but note that all effort outside of the Technology area falls into a single category. Unless you work at UW\u2013Madison, we do not need to know any details about your effort outside of the Technology area. (BrianL will talk to UW\u2013Madison folks about local expectations.) If you are assigned to the Technology area for less than 100%, please report your actual Technology effort accurately. Workloads vary from week to week. For example, suppose you are 50% Technology in general, but you actually work 24 hours in a 40-hour week; you should report 60% effort for that week. The goal is to present reality, not what you think management wants to see. Effort is reported as integer percentages, no less accurate than 5% intervals So please do not report percentages like 43.21% and please do not round to the nearest 10%.","title":"Basic Ideas"},{"location":"software/effort-tracking/#effort-categories","text":"Here are the categories in which to track effort: Investigations Work on the Investigations team External Software work that (generally) benefits our users; e.g., creating packages; updating existing ones; designing, coding, and testing new tools, existing tools, patches, or our software components Internal Software work on tools that we use to get work done; e.g., working on osg-test (for now), osg-build, Koji maintenance, the UW or UC ITB instances Documentation Work on our TWiki or Markdown documentation Release Release team activities, primarily acceptance testing and cutting releases Support User support, including working on GOC tickets, direct support emails, some JIRA tickets that are more support than development, etc. It might be tricky to decide when support work becomes development work; generally, once a support ticket turns into a JIRA ticket and goes through the normal development lifecycle, then the JIRA-based work is development. If there is still extensive communication with GOC ticket users, that is still support. Management This is mainly for team leads; e.g., managing team activities and tickets (generally); hiring; leading (not just attending) meetings Education Not for general learning or training activities The OSG Education area is essentially part of the Software area, because many technology-area members contribute to the OSG School. So this category is for OSG School effort (or other sanctioned OSG Education activities. Admin General administrative activities that benefit the OSG Technology area but that do not fit elsewhere \u2014 use sparingly!! Outside For all activities outside of the OSG Technology area (Madison team members should provide extra details, see BrianL) Leave This is for holidays, vacation, and sick leave; count a full day of leave as 8.0 hours, count a half day as 4.0 hours A few thoughts about tricky situations: Meetings. If a meeting is specific to one of the categories above, use that category. If the meeting is more general (e.g., the weekly Monday meeting, or the OSG AHM), amortize your time according to your usual breakdown by category. For example, someone who spends nearly all of their time working on development tasks should count the Monday meeting as development time. Administrative activities. This is probably the trickiest category. It certainly covers any administrative work that pertains to your activity in the OSG Technology area. But what about administrative activities that pertain to your employment in general, and not to any particular activity? In that case, and that case only, you should amortize the administrative activity between Admin and Outside according to either (a) your appointment percentages between OSG Technology and non-Technology activities, or (b) your actual percentages between OSG Technology and non-Technology activities. Outside (non-Technology) activities that benefit the OSG Technology area. The simplest approach is to amortize the time. The more correct approach is to figure out where credit will be given for the work; if the OSG Annual Report will describe the work in one of the Technology sections, then it should be a Technology category; otherwise not. Learning activities. Put short amounts of learning time in their relevant development category. For instance, if Igor is showing Edgar how to use GlideTester, that goes into Internal . But for longer training events, or for events that are less obviously related to day-to-day activities, mark the time as Admin , and maybe add a comment explaining the activity. Ultimately, if you are not sure how to deal with a situation, ask BrianL and he will make something up and document it here (generically) for future reference.","title":"Effort Categories"},{"location":"software/git-software-development/","text":"Git software development workflow \u00b6 This document describes the development workflow for OSG software packages kept in GitHub. It is intended for people who wish to contribute to OSG software. Git and GitHub basics \u00b6 If you are unfamiliar with Git and GitHub, the GitHub website has a good series of tutorials at https://docs.github.com/en/get-started Getting shell access to GitHub \u00b6 There are multiple ways of authenticating to GitHub from the shell. This section will cover using SSH keys. This is no longer the method recommended by GitHub, but is easier to set up for someone with existing SSH experience. The instructions here are derived from GitHub's own instructions on using SSH keys . Creating a new SSH key (optional but recommended) \u00b6 If you already have an SSH keypair in your ~/.ssh directory that you want to use for GitHub, you may skip this step. It is more secure, however, to create a new keypair specifically for use with GitHub. The instructions below will create an SSH public/private key pair with the private key stored in ~/.ssh/id_github and public key stored in ~/.ssh/id_github.pub . Generating the key \u00b6 Use ssh-keygen to generate the SSH keypair. For <EMAIL_ADDRESS> , use the email address associated with your GitHub account. [user@client ~ ] $ ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_github -C <EMAIL_ADDRESS> Configuring SSH to use the key for GitHub \u00b6 Make sure SSH uses the new key by default to access GitHub. Create or edit ~/.ssh/config and append the following lines: Host github.com IdentityFile <YOUR_HOME_DIR>/.ssh/id_github Where is the output of the command: echo $HOME Adding the SSH public key to GitHub \u00b6 Using the GitHub web interface: On the upper right of the screen, click on your profile picture In the menu that pops up, click \"Settings\" On the left-hand sidebar, click \"SSH and GPG keys\" In the top right of the \"SSH keys\" box, click \"New SSH key\" In the \"Title\" field of the dialog that pops up, enter a descriptive name for the key Open the public key file (e.g. ~/.ssh/id_github.pub (don't forget the .pub )) in a text editor and copy its full contents to the clipboard In the \"Key\" field, paste the public key Below the \"Key\" field, click \"Add SSH key\" You should see your new key in the \"SSH keys\" list. Testing that shell access works \u00b6 To verify you can authenticate to GitHub using SSH, SSH to git@github.com . You should see a message that 'you've successfully authenticated, but GitHub does not provide shell access.' Contribution workflow \u00b6 We use the standard GitHub pull request workflow for making contributions to OSG software. If you've never contributed to this project on GitHub before, do the following steps first: Using the GitHub web interface, fork the repo you wish to contribute to. Make a clone of your forked repo on your local machine. [user@client ~ ] $ git clone git@github.com:<USERNAME/PROJECT> Where <USERNAME> is your github username and <PROJECT> is the name of the project you want to contribute to, e.g. in order to clone my local fork of the openscience/technology repository: [user@client ~ ] $ git clone https://github.com/ddavila0/technology.git Note If you get a \"Permission denied\" error, your public key may not be set up with GitHub -- please see the \"Getting shell access to GitHub\" section above. If you get some other error, the GitHub page on SSH may contain useful information on troubleshooting. Once you have your local repo, do the following: Create a branch to hold changes that are related to the issue you are working on. Give the <BRANCH> a name that will remind you of its purpose, including any relevant ticket numbers, such as SOFTWARE-2345.pathchange : [user@client ~ ] $ git checkout -b <BRANCH> Make your commits to this branch, then push the branch to your repo on GitHub. [user@client ~ ] $ git push origin <BRANCH> Select your branch in the GitHub web interface, then create a \"pull request\" against the original repo. Add a good description of your change into the message for the pull request. Enter a Jira ticket number in the message to automatically link the pull request to the Jira ticket. Request a review from the drop down menu on the right and wait for your pull request to be reviewed by a software team member. If the team member accepts your changes, they will merge your pull request, and your changes will be incorporated upstream. You may then delete the branch you created your pull request from. If your changes are rejected, then you may make additional changes to the branch that your pull request is for. Once you push the changes from your local repo to your GitHub repo, they will automatically be added to the pull request. Release workflow \u00b6 This section is intended for OSG Software team members or the primary developers of a software project (i.e. those that make releases). Some of the steps require direct write access the GitHub repo for the project owned by opensciencegrid . (If you can approve pull requests, you have write access). A release of a software is created from your local clone of a software project. Before you release, you need to make sure your local clone is in sync with the GitHub repo owned by opensciencegrid (the OSG repo): If you haven't already, add the OSG repo as a \"remote\" to your repo: [user@client ~ ] $ git remote add upstream git@github.com:opensciencegrid/<PROJECT> Where <PROJECT> is the name of the project you are going to release, e.g. for openscience/technology repository it would be technology.git Fetch changes from the OSG repo: [user@client ~ ] $ git fetch upstream Compare your branch you are releasing from (probably master ) to its copy in the OSG repo: [user@client ~ ] $ git checkout master ; git diff upstream/master There should be no differences. Once this is done, release the software as you usually do. This process varies from one project to another, but often it involves running make upstream or similar. Check your project's README file for instructions. Test your software. Tag the commit that you made the release from. Git release tags are conventionally called VERSION , where VERSION is the version of the software you are releasing. So if you're releasing version 1.3.0, you would create the <TAG> v1.3.0 . Note Once a tag has been pushed to the OSG repo, it should not be changed. Be sure the commit you want to tag is the final one you made the release from. Create the tag in your local repo: [user@client ~ ] $ git tag <TAG> Push the tag to your own GitHub repo: [user@client ~ ] $ git push origin <TAG> Push the tag to the OSG repo: [user@client ~ ] $ git push upstream <TAG> Best practices \u00b6 Making good pull requests (The Art of Good Commits) \u00b6 In addition to writing good code, it's important to organize your changes to make the task of reviewing them easier, both for the reviewer of the pull request, and even for yourself later. Here are some general guidelines and tips. Put logically separate changes into separate commits \u00b6 This becomes more relevant if there are a lot of changes in the pull request. Having a single commit with many different changes happening at the same time can make the changes harder to review. If possible, split up logically separate changes into separate commits. As a simple example, if you are renaming a variable in many places, and also refactoring the structure of some code, these changes can be split into two separate commits. This will make it easier when reviewing to see clearly what each commit is trying to accomplish. The process you went through to arrive at your final code may have been different, but you can clean up your commits after the fact. One method is to use git rebase -i to combine (squash) several commits into one, and then use git gui to amend the combined commit, staging the parts that represent each logical change into separate commits. Another example that occasionally comes up is when you want to copy or move a file AND make changes to that file. If you have a single commit that introduces a file to a new location with changes , it will not be obvious from the commit diff itself which parts are the same (moved or copied in) and which parts you are modifying. Instead, by putting the copy or move of the original file into its own commit, and then putting your changes in a separate commit, it will make it clear to the reviewer which parts are changing from the original. Avoid whitespace noise \u00b6 There are a few considerations to note when it comes to whitespace. Avoid adding spaces at the end of lines. These are generally considered \"noise\" that will get cleaned up later (sometimes automatically, depending on editor settings). It's not necessary to \"fix\" this kind of whitespace noise everywhere you happen to find it in existing files, but it's fine to remove trailing whitespace for lines that you are already modifying for your own changes. Do not strip the final newline at the end-of-file. Some text editors will automatically strip the final newline at the end of file, but this is a form of whitespace noise similar to trailing spaces. If that is the case for your editor, please configure it not to strip the newline at EOF. (GitHub will show the diff for files with a missing newline at EOF with a red circle-minus symbol with the mouseover text \"No newline at end of file\".) Avoid mixing tabs and spaces. With the exception of Makefiles and Go source code, indentation should be done with regular spaces, not tabs. Please configure your text editor accordingly. Mixing tabs and spaces in indentation is problematic because different editor settings can make tab stops appear at different widths. As with trailing whitespace, it's fine to convert stray tabs to spaces on lines you are modifying, but it is not necessary to fix them everywhere, if that is not the purpose of your pull request. Put large whitespace changes into a separate commit. If you do want to change a significant amount of whitespace (either converting tabs to spaces on many lines, or perhaps adjusting the amount of indentation, or wrapping text at a different width), make your whitespace-only changes as a separate commit. This will make it clear that, although many lines may be changing, there is no functional change for that particular commit. Then any functional changes to the text in a following commit will be easier to review. Don't commit large files \u00b6 Try to keep the repository small by not committing files that are too large. Avoid committing large binaries or data sets. Ask yourself if they need to be in the repository before committing. If, somehow, a large file has been committed and pushed, it's not enough to remove the file in another commit. The file must be removed from all of the history or else the repository will still contain the large file as Git keeps track of deleted files. This can be done using the git rebase -i and git filter-repo commands. If a large file must be added to the repository. Use (Git LFS)[https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage] Verify that only the files intended are modified in each commit \u00b6 Sometimes you may have several files modified at once, but you only intend to commit a subset of the changes. In such cases you should be aware that git commit -a will include all the modified files in your commit. Likewise, if you have some untracked files in your working copy, that you do not intend to commit, be aware that git add . will introduce these as new files in the commit. Note If you do use the -a option for git commit , you may want to consider using the -v option along with it (i.e. git commit -av ), which will show you the diff to be committed in your editor while you are typing your commit message. After making a commit locally, you can verify that only the files you intended to modify were included in the commit by running git show --stat . Or to review the actual changes to those files, git show (without --stat ). If you find unintended files included in the commit, you can amend the commit so that it does not include changes to file-not-to-commit like so: [user@client ~ ] $ git reset HEAD^ file-not-to-commit [user@client ~ ] $ git commit --amend If you have multiple commits ready for a pull request, you can review the high-level changes for each commit with git log --stat origin/master.. (or origin/main.. , whichever is the name of the main origin branch). Tools like git gui also provide a way to review commits. If you find unintended files included in earlier commits, you can do a git rebase -i origin/master and edit the commits in question, which will give you a chance to amend a particular commit as shown above. Squash noisy work-in-progress commits \u00b6 Naturally in the trial-and-error-prone process of development, there will be many changes along the way that didn't make the final cut. This is good and healthy, and it's perfectly reasonable to be making many small work-in-progress commits locally while you are developing. However, for the reviewer, the relevant thing is what final changes are being introduced into the codebase. Having to review several ideas that were put into and then taken out of the changeset is a distraction, and makes it harder to see what the end result is for the new changes. If you have such work-in-progress commits, first combine them (this is also called \"squashing\" or \"rebasing\"), and then break them up into logically distinct commits as necessary, representing the final changeset. As mentioned above, one way to do this is with a combination of git rebase -i and git gui , though there are other third-party tools (e.g., magit) available also. Write a succinct subject to explain what each commit does \u00b6 The first line of a commit message is the \"subject\" (or sometimes also called the \"title\"). It should be short and sweet (at most 72 characters) and briefly state what the commit is designed to do. As a convention, the subject of the commit message should be written in the imperative - that is, it should be written as if it were a command. For instance, a subject should start with \"fix a bug\" rather than \"fixing\" or \"fixes\". Explain why a change was made in the commit message \u00b6 It is generally important also to explain why a change was made. If this is not covered by the succinct subject line of your commit, you should explain the rationale behind your change in the commit message body. (The commit message starts with the subject line, then is optionally followed by a blank line plus the message body.) You can also explain in the commit message body how this commit accomplishes the stated purpose in the subject - and you may find yourself needing to do this if there are some tricky details in the changes. But even if it is perfectly clear from the code and your commit message what you are changing and how you are going about it, it is not always clear why the change is needed or desired - so it is important to explain your reasons, in order to make this clear to the reviewer. For an example of \"explaining your reasons\", see this commit message body . Summarize your commits in the pull request title \u00b6 The title of a pull request is analogous to the subject of a commit. If you have only one commit in your pull request, GitHub will by default set the pull request title and body to match that commit's subject and body; and that default is acceptable for single-commit pull requests. But if you have multiple commits in your pull request, you should try to capture the overall goal of these commits in your pull request title. In the pull request body, you can also mention or discuss the high-level changes from each commit, and if relevant discuss how these changes work together for the overall goal of the pull request. Choose a separate, descriptive branch name for each pull request \u00b6 GitHub allows creating pull requests entirely on their web interface, and will automatically suggest a generic branch name like patch-42 . But this is boring and not especially helpful to the reviewer or to the one submitting the pull request. Instead, choose a short name for the branch that describes the topic of the changes or the feature being introduced. For instance, fix-memory-leak or scitokens-support . (As will be discussed more later, it is best to prefix the branch name with a ticket reference as well.) Note that each pull request should get its own branch name, even if two pull requests are for the same ticket and the topic is similar. New commits pushed to a branch for a pull request will automatically show up as part of that pull request; so a second pull request needs a separate branch to track the separate set of changes. Reference any relevant tickets \u00b6 Code changes often are related to a Jira ticket, for instance SOFTWARE-1234. By referencing the name of a ticket in your pull request, it provides a convenient way to look into the background context for the change; and later on down the road, it makes it easy to find which changes were made for a particular task, referenced by the ticket name. Ideally, you can include a ticket reference each of these three places: Your branch name. For example, name the branch in your fork of the GitHub repo for the pull request SOFTWARE-1234.fix-memory-leak . Your commit messages. For example, the subject of your commit message might read, fix a memory leak (SOFTWARE-1234) . If you have trouble squeezing the ticket name into the subject line, or if you have a number of related tickets that you want to reference, it is also OK to mention them later in the commit message body. The pull request title. If your pull request is just a single commit, and you have the ticket reference in the subject line of the commit message, GitHub will include this in the pull request title automatically. But if you have multiple commits, or you have only included the ticket reference in the body of the commit message, or more generally if you want to tweak the title of the pull request, you should in any case make a point to include the ticket name in the title of the pull request. (By convention, we include this at the end of the title, in parentheses.) If there is no ticket associated with your changes, consider creating one (or asking an OSG software team member to create one) before submitting your pull request. Further reading \u00b6 There are a number of articles and guides for making good git commits and good pull requests - a simple search will turn up plenty of material for the interested reader. See online guides such as this one for more details. Brownie points \u00b6 You will get brownie points from Carl, personally, if you strive to make your code (and other text files) fit within an 80-column terminal window. Reviewing pull requests \u00b6 There are a couple items to note about the review process for GitHub pull requests. Batch comments in a formal review \u00b6 When reviewing a pull request, GitHub allows you to comment on lines and presents the option to \"Add single comment\" or \"Start a review\". A single comment added will not be tied to your review, and a separate email notification will be sent for every time you click \"Add single comment\". Especially for reviewing larger pull requests, we generally prefer to \"Start a review\", and then \"Add review comment\" for subsequent comments. This will tie all of your comments and suggestions together as part of your review. When you complete your review, you will have the opportunity to make summary comments about the changes, when you select Approve/Comment/Request changes. By \"batching\" all of your review comments this way, a single email notification will be sent for your review, which contains all of your review comments together. Batch commits when accepting suggestions from a review \u00b6 When someone reviews your pull request, they may make suggestions that tweak your changes. Similar to review comments, suggestions from a review can either be applied one at a time (Commit suggestion), or they can be batched and applied together. To batch suggestions, first you need to open the \"Files changed\" tab; then for each suggestion you want to accept, click \"Add suggestion to batch\". Finally, click \"Commit suggestions\" to apply all batched suggestions as a single commit. Generally we prefer to batch related changes or miscellaneous tweaks rather than applying each one individually. But if there are a number of suggestions of a different nature, it is OK to group them such that you apply one batch for each set of related suggestions (consistent with the guideline to put logically separate changes into separate commits).","title":"Git Software Development Process"},{"location":"software/git-software-development/#git-software-development-workflow","text":"This document describes the development workflow for OSG software packages kept in GitHub. It is intended for people who wish to contribute to OSG software.","title":"Git software development workflow"},{"location":"software/git-software-development/#git-and-github-basics","text":"If you are unfamiliar with Git and GitHub, the GitHub website has a good series of tutorials at https://docs.github.com/en/get-started","title":"Git and GitHub basics"},{"location":"software/git-software-development/#getting-shell-access-to-github","text":"There are multiple ways of authenticating to GitHub from the shell. This section will cover using SSH keys. This is no longer the method recommended by GitHub, but is easier to set up for someone with existing SSH experience. The instructions here are derived from GitHub's own instructions on using SSH keys .","title":"Getting shell access to GitHub"},{"location":"software/git-software-development/#creating-a-new-ssh-key-optional-but-recommended","text":"If you already have an SSH keypair in your ~/.ssh directory that you want to use for GitHub, you may skip this step. It is more secure, however, to create a new keypair specifically for use with GitHub. The instructions below will create an SSH public/private key pair with the private key stored in ~/.ssh/id_github and public key stored in ~/.ssh/id_github.pub .","title":"Creating a new SSH key (optional but recommended)"},{"location":"software/git-software-development/#generating-the-key","text":"Use ssh-keygen to generate the SSH keypair. For <EMAIL_ADDRESS> , use the email address associated with your GitHub account. [user@client ~ ] $ ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_github -C <EMAIL_ADDRESS>","title":"Generating the key"},{"location":"software/git-software-development/#configuring-ssh-to-use-the-key-for-github","text":"Make sure SSH uses the new key by default to access GitHub. Create or edit ~/.ssh/config and append the following lines: Host github.com IdentityFile <YOUR_HOME_DIR>/.ssh/id_github Where is the output of the command: echo $HOME","title":"Configuring SSH to use the key for GitHub"},{"location":"software/git-software-development/#adding-the-ssh-public-key-to-github","text":"Using the GitHub web interface: On the upper right of the screen, click on your profile picture In the menu that pops up, click \"Settings\" On the left-hand sidebar, click \"SSH and GPG keys\" In the top right of the \"SSH keys\" box, click \"New SSH key\" In the \"Title\" field of the dialog that pops up, enter a descriptive name for the key Open the public key file (e.g. ~/.ssh/id_github.pub (don't forget the .pub )) in a text editor and copy its full contents to the clipboard In the \"Key\" field, paste the public key Below the \"Key\" field, click \"Add SSH key\" You should see your new key in the \"SSH keys\" list.","title":"Adding the SSH public key to GitHub"},{"location":"software/git-software-development/#testing-that-shell-access-works","text":"To verify you can authenticate to GitHub using SSH, SSH to git@github.com . You should see a message that 'you've successfully authenticated, but GitHub does not provide shell access.'","title":"Testing that shell access works"},{"location":"software/git-software-development/#contribution-workflow","text":"We use the standard GitHub pull request workflow for making contributions to OSG software. If you've never contributed to this project on GitHub before, do the following steps first: Using the GitHub web interface, fork the repo you wish to contribute to. Make a clone of your forked repo on your local machine. [user@client ~ ] $ git clone git@github.com:<USERNAME/PROJECT> Where <USERNAME> is your github username and <PROJECT> is the name of the project you want to contribute to, e.g. in order to clone my local fork of the openscience/technology repository: [user@client ~ ] $ git clone https://github.com/ddavila0/technology.git Note If you get a \"Permission denied\" error, your public key may not be set up with GitHub -- please see the \"Getting shell access to GitHub\" section above. If you get some other error, the GitHub page on SSH may contain useful information on troubleshooting. Once you have your local repo, do the following: Create a branch to hold changes that are related to the issue you are working on. Give the <BRANCH> a name that will remind you of its purpose, including any relevant ticket numbers, such as SOFTWARE-2345.pathchange : [user@client ~ ] $ git checkout -b <BRANCH> Make your commits to this branch, then push the branch to your repo on GitHub. [user@client ~ ] $ git push origin <BRANCH> Select your branch in the GitHub web interface, then create a \"pull request\" against the original repo. Add a good description of your change into the message for the pull request. Enter a Jira ticket number in the message to automatically link the pull request to the Jira ticket. Request a review from the drop down menu on the right and wait for your pull request to be reviewed by a software team member. If the team member accepts your changes, they will merge your pull request, and your changes will be incorporated upstream. You may then delete the branch you created your pull request from. If your changes are rejected, then you may make additional changes to the branch that your pull request is for. Once you push the changes from your local repo to your GitHub repo, they will automatically be added to the pull request.","title":"Contribution workflow"},{"location":"software/git-software-development/#release-workflow","text":"This section is intended for OSG Software team members or the primary developers of a software project (i.e. those that make releases). Some of the steps require direct write access the GitHub repo for the project owned by opensciencegrid . (If you can approve pull requests, you have write access). A release of a software is created from your local clone of a software project. Before you release, you need to make sure your local clone is in sync with the GitHub repo owned by opensciencegrid (the OSG repo): If you haven't already, add the OSG repo as a \"remote\" to your repo: [user@client ~ ] $ git remote add upstream git@github.com:opensciencegrid/<PROJECT> Where <PROJECT> is the name of the project you are going to release, e.g. for openscience/technology repository it would be technology.git Fetch changes from the OSG repo: [user@client ~ ] $ git fetch upstream Compare your branch you are releasing from (probably master ) to its copy in the OSG repo: [user@client ~ ] $ git checkout master ; git diff upstream/master There should be no differences. Once this is done, release the software as you usually do. This process varies from one project to another, but often it involves running make upstream or similar. Check your project's README file for instructions. Test your software. Tag the commit that you made the release from. Git release tags are conventionally called VERSION , where VERSION is the version of the software you are releasing. So if you're releasing version 1.3.0, you would create the <TAG> v1.3.0 . Note Once a tag has been pushed to the OSG repo, it should not be changed. Be sure the commit you want to tag is the final one you made the release from. Create the tag in your local repo: [user@client ~ ] $ git tag <TAG> Push the tag to your own GitHub repo: [user@client ~ ] $ git push origin <TAG> Push the tag to the OSG repo: [user@client ~ ] $ git push upstream <TAG>","title":"Release workflow"},{"location":"software/git-software-development/#best-practices","text":"","title":"Best practices"},{"location":"software/git-software-development/#making-good-pull-requests-the-art-of-good-commits","text":"In addition to writing good code, it's important to organize your changes to make the task of reviewing them easier, both for the reviewer of the pull request, and even for yourself later. Here are some general guidelines and tips.","title":"Making good pull requests (The Art of Good Commits)"},{"location":"software/git-software-development/#put-logically-separate-changes-into-separate-commits","text":"This becomes more relevant if there are a lot of changes in the pull request. Having a single commit with many different changes happening at the same time can make the changes harder to review. If possible, split up logically separate changes into separate commits. As a simple example, if you are renaming a variable in many places, and also refactoring the structure of some code, these changes can be split into two separate commits. This will make it easier when reviewing to see clearly what each commit is trying to accomplish. The process you went through to arrive at your final code may have been different, but you can clean up your commits after the fact. One method is to use git rebase -i to combine (squash) several commits into one, and then use git gui to amend the combined commit, staging the parts that represent each logical change into separate commits. Another example that occasionally comes up is when you want to copy or move a file AND make changes to that file. If you have a single commit that introduces a file to a new location with changes , it will not be obvious from the commit diff itself which parts are the same (moved or copied in) and which parts you are modifying. Instead, by putting the copy or move of the original file into its own commit, and then putting your changes in a separate commit, it will make it clear to the reviewer which parts are changing from the original.","title":"Put logically separate changes into separate commits"},{"location":"software/git-software-development/#avoid-whitespace-noise","text":"There are a few considerations to note when it comes to whitespace. Avoid adding spaces at the end of lines. These are generally considered \"noise\" that will get cleaned up later (sometimes automatically, depending on editor settings). It's not necessary to \"fix\" this kind of whitespace noise everywhere you happen to find it in existing files, but it's fine to remove trailing whitespace for lines that you are already modifying for your own changes. Do not strip the final newline at the end-of-file. Some text editors will automatically strip the final newline at the end of file, but this is a form of whitespace noise similar to trailing spaces. If that is the case for your editor, please configure it not to strip the newline at EOF. (GitHub will show the diff for files with a missing newline at EOF with a red circle-minus symbol with the mouseover text \"No newline at end of file\".) Avoid mixing tabs and spaces. With the exception of Makefiles and Go source code, indentation should be done with regular spaces, not tabs. Please configure your text editor accordingly. Mixing tabs and spaces in indentation is problematic because different editor settings can make tab stops appear at different widths. As with trailing whitespace, it's fine to convert stray tabs to spaces on lines you are modifying, but it is not necessary to fix them everywhere, if that is not the purpose of your pull request. Put large whitespace changes into a separate commit. If you do want to change a significant amount of whitespace (either converting tabs to spaces on many lines, or perhaps adjusting the amount of indentation, or wrapping text at a different width), make your whitespace-only changes as a separate commit. This will make it clear that, although many lines may be changing, there is no functional change for that particular commit. Then any functional changes to the text in a following commit will be easier to review.","title":"Avoid whitespace noise"},{"location":"software/git-software-development/#dont-commit-large-files","text":"Try to keep the repository small by not committing files that are too large. Avoid committing large binaries or data sets. Ask yourself if they need to be in the repository before committing. If, somehow, a large file has been committed and pushed, it's not enough to remove the file in another commit. The file must be removed from all of the history or else the repository will still contain the large file as Git keeps track of deleted files. This can be done using the git rebase -i and git filter-repo commands. If a large file must be added to the repository. Use (Git LFS)[https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage]","title":"Don't commit large files"},{"location":"software/git-software-development/#verify-that-only-the-files-intended-are-modified-in-each-commit","text":"Sometimes you may have several files modified at once, but you only intend to commit a subset of the changes. In such cases you should be aware that git commit -a will include all the modified files in your commit. Likewise, if you have some untracked files in your working copy, that you do not intend to commit, be aware that git add . will introduce these as new files in the commit. Note If you do use the -a option for git commit , you may want to consider using the -v option along with it (i.e. git commit -av ), which will show you the diff to be committed in your editor while you are typing your commit message. After making a commit locally, you can verify that only the files you intended to modify were included in the commit by running git show --stat . Or to review the actual changes to those files, git show (without --stat ). If you find unintended files included in the commit, you can amend the commit so that it does not include changes to file-not-to-commit like so: [user@client ~ ] $ git reset HEAD^ file-not-to-commit [user@client ~ ] $ git commit --amend If you have multiple commits ready for a pull request, you can review the high-level changes for each commit with git log --stat origin/master.. (or origin/main.. , whichever is the name of the main origin branch). Tools like git gui also provide a way to review commits. If you find unintended files included in earlier commits, you can do a git rebase -i origin/master and edit the commits in question, which will give you a chance to amend a particular commit as shown above.","title":"Verify that only the files intended are modified in each commit"},{"location":"software/git-software-development/#squash-noisy-work-in-progress-commits","text":"Naturally in the trial-and-error-prone process of development, there will be many changes along the way that didn't make the final cut. This is good and healthy, and it's perfectly reasonable to be making many small work-in-progress commits locally while you are developing. However, for the reviewer, the relevant thing is what final changes are being introduced into the codebase. Having to review several ideas that were put into and then taken out of the changeset is a distraction, and makes it harder to see what the end result is for the new changes. If you have such work-in-progress commits, first combine them (this is also called \"squashing\" or \"rebasing\"), and then break them up into logically distinct commits as necessary, representing the final changeset. As mentioned above, one way to do this is with a combination of git rebase -i and git gui , though there are other third-party tools (e.g., magit) available also.","title":"Squash noisy work-in-progress commits"},{"location":"software/git-software-development/#write-a-succinct-subject-to-explain-what-each-commit-does","text":"The first line of a commit message is the \"subject\" (or sometimes also called the \"title\"). It should be short and sweet (at most 72 characters) and briefly state what the commit is designed to do. As a convention, the subject of the commit message should be written in the imperative - that is, it should be written as if it were a command. For instance, a subject should start with \"fix a bug\" rather than \"fixing\" or \"fixes\".","title":"Write a succinct subject to explain what each commit does"},{"location":"software/git-software-development/#explain-why-a-change-was-made-in-the-commit-message","text":"It is generally important also to explain why a change was made. If this is not covered by the succinct subject line of your commit, you should explain the rationale behind your change in the commit message body. (The commit message starts with the subject line, then is optionally followed by a blank line plus the message body.) You can also explain in the commit message body how this commit accomplishes the stated purpose in the subject - and you may find yourself needing to do this if there are some tricky details in the changes. But even if it is perfectly clear from the code and your commit message what you are changing and how you are going about it, it is not always clear why the change is needed or desired - so it is important to explain your reasons, in order to make this clear to the reviewer. For an example of \"explaining your reasons\", see this commit message body .","title":"Explain why a change was made in the commit message"},{"location":"software/git-software-development/#summarize-your-commits-in-the-pull-request-title","text":"The title of a pull request is analogous to the subject of a commit. If you have only one commit in your pull request, GitHub will by default set the pull request title and body to match that commit's subject and body; and that default is acceptable for single-commit pull requests. But if you have multiple commits in your pull request, you should try to capture the overall goal of these commits in your pull request title. In the pull request body, you can also mention or discuss the high-level changes from each commit, and if relevant discuss how these changes work together for the overall goal of the pull request.","title":"Summarize your commits in the pull request title"},{"location":"software/git-software-development/#choose-a-separate-descriptive-branch-name-for-each-pull-request","text":"GitHub allows creating pull requests entirely on their web interface, and will automatically suggest a generic branch name like patch-42 . But this is boring and not especially helpful to the reviewer or to the one submitting the pull request. Instead, choose a short name for the branch that describes the topic of the changes or the feature being introduced. For instance, fix-memory-leak or scitokens-support . (As will be discussed more later, it is best to prefix the branch name with a ticket reference as well.) Note that each pull request should get its own branch name, even if two pull requests are for the same ticket and the topic is similar. New commits pushed to a branch for a pull request will automatically show up as part of that pull request; so a second pull request needs a separate branch to track the separate set of changes.","title":"Choose a separate, descriptive branch name for each pull request"},{"location":"software/git-software-development/#reference-any-relevant-tickets","text":"Code changes often are related to a Jira ticket, for instance SOFTWARE-1234. By referencing the name of a ticket in your pull request, it provides a convenient way to look into the background context for the change; and later on down the road, it makes it easy to find which changes were made for a particular task, referenced by the ticket name. Ideally, you can include a ticket reference each of these three places: Your branch name. For example, name the branch in your fork of the GitHub repo for the pull request SOFTWARE-1234.fix-memory-leak . Your commit messages. For example, the subject of your commit message might read, fix a memory leak (SOFTWARE-1234) . If you have trouble squeezing the ticket name into the subject line, or if you have a number of related tickets that you want to reference, it is also OK to mention them later in the commit message body. The pull request title. If your pull request is just a single commit, and you have the ticket reference in the subject line of the commit message, GitHub will include this in the pull request title automatically. But if you have multiple commits, or you have only included the ticket reference in the body of the commit message, or more generally if you want to tweak the title of the pull request, you should in any case make a point to include the ticket name in the title of the pull request. (By convention, we include this at the end of the title, in parentheses.) If there is no ticket associated with your changes, consider creating one (or asking an OSG software team member to create one) before submitting your pull request.","title":"Reference any relevant tickets"},{"location":"software/git-software-development/#further-reading","text":"There are a number of articles and guides for making good git commits and good pull requests - a simple search will turn up plenty of material for the interested reader. See online guides such as this one for more details.","title":"Further reading"},{"location":"software/git-software-development/#brownie-points","text":"You will get brownie points from Carl, personally, if you strive to make your code (and other text files) fit within an 80-column terminal window.","title":"Brownie points"},{"location":"software/git-software-development/#reviewing-pull-requests","text":"There are a couple items to note about the review process for GitHub pull requests.","title":"Reviewing pull requests"},{"location":"software/git-software-development/#batch-comments-in-a-formal-review","text":"When reviewing a pull request, GitHub allows you to comment on lines and presents the option to \"Add single comment\" or \"Start a review\". A single comment added will not be tied to your review, and a separate email notification will be sent for every time you click \"Add single comment\". Especially for reviewing larger pull requests, we generally prefer to \"Start a review\", and then \"Add review comment\" for subsequent comments. This will tie all of your comments and suggestions together as part of your review. When you complete your review, you will have the opportunity to make summary comments about the changes, when you select Approve/Comment/Request changes. By \"batching\" all of your review comments this way, a single email notification will be sent for your review, which contains all of your review comments together.","title":"Batch comments in a formal review"},{"location":"software/git-software-development/#batch-commits-when-accepting-suggestions-from-a-review","text":"When someone reviews your pull request, they may make suggestions that tweak your changes. Similar to review comments, suggestions from a review can either be applied one at a time (Commit suggestion), or they can be batched and applied together. To batch suggestions, first you need to open the \"Files changed\" tab; then for each suggestion you want to accept, click \"Add suggestion to batch\". Finally, click \"Commit suggestions\" to apply all batched suggestions as a single commit. Generally we prefer to batch related changes or miscellaneous tweaks rather than applying each one individually. But if there are a number of suggestions of a different nature, it is OK to group them such that you apply one batch for each set of related suggestions (consistent with the guideline to put logically separate changes into separate commits).","title":"Batch commits when accepting suggestions from a review"},{"location":"software/ipv6-testing/","text":"Testing Software with IPv6 \u00b6 About this Document \u00b6 This document provides instructions on setting up a host with an IPv6 address for testing the OSG software stack. The plan is to be able to spin up special Fermicloud VM\u2019s that have corresponding public IPv6 addresses meaning that there will be a limit of ~15 VM\u2019s at one time. For more information on IPv6, consult Wikipedia . Requirements \u00b6 Be familiar with your institute's network policy and firewall configuration 1 Root access is required to configure iptables Enabling IPV6 \u00b6 Determine the public IPv6 address of your host. In the example below that would be 2001:400:2410:29::182 : user@host $ nslookup -type = aaaa <HOSTNAME> Server: 132.239.0.252 Address: 132.239.0.252#53 Non-authoritative answer: ipv6vm001.fnal.gov has AAAA address 2001:400:2410:29::182 Replacing <HOSTNAME> with your machine's hostname. Ask your network administrator for your IPv6 default gateway Modify /etc/sysconfig/network-scripts/ifcfg-eth0 and be sure these lines exist, and : IPV6INIT=yes IPV6_AUTOCONF=no IPV6ADDR=<IPV6 ADDRESS>\" IPV6_DEFAULTGW=\"The IPV6 Default Gateway\" Replace <IPV6 ADDRESS> with the address found in step 1. Restart the network devices: root@host # service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Testing IPv6 connectivity \u00b6 To verify that the VM is capable of IPv6 we will be using the ping6 command between the test VM and another IPv6 capable machine From another IPv6 capable machine, ping your VM: user@host $ ping6 ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov(ipv6vm001.fnal.gov) 56 data bytes 64 bytes from ipv6vm001.fnal.gov: icmp_seq=1 ttl=51 time=68.1 ms 64 bytes from ipv6vm001.fnal.gov: icmp_seq=2 ttl=51 time=57.6 ms From your test VM, ping another IPv6 capable machine: [efajardo@ipv6vm001 ~]# ping6 uaf-4.t2.ucsd.edu PING uaf-4.t2.ucsd.edu(uaf-4.t2.ucsd.edu) 56 data bytes 64 bytes from uaf-4.t2.ucsd.edu: icmp_seq=1 ttl=51 time=57.6 ms Verifying SSH over IPv6 \u00b6 Make sure you can login to your VM over IPv6. Currently, Fermilab's kerberos does not support SSH over IPv6. Add your ssh_key to your machine and make sure /etc/ssh/sshd_config has the following lines: RSAAuthentication yes PubkeyAuthentication yes Try connecting to you IPv6 enabled machine over SSH: efajardo@uaf-4 ~$ ssh -6 root@ipv6vm001.fnal.gov Last login: Wed Jun 11 14:51:47 2014 from 2607:f720:1700:1b30:21f:c6ff:feeb:2631 [root@ipv6vm001 ~]# Disabling IPv4 \u00b6 If you were able to log into your VM over IPv6, you can disable IPv4 and try to communicate exclusively over IPv6. Comment the IPADDR line in /etc/sysconfig/network-scripts/ifcfg-eth0 : #IPADDR=131.225.41.182 IPV6ADDR=\"2607:f720:1700:1b30::9b\" Note Ensure that your IPV6ADDR is uncommented otherwise you will not be able to connect to the host again Restart the network services: root@host # service network restart The ping command should no longer work: root@host # ping ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov (131.225.41.182): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Disabling IPv6 \u00b6 In your testing, you may find the need to disable IPv6. root@host # sysctl -w net.ipv6.conf.all.disable_ipv6 = 1 root@host # service network restart The ping6 command should no longer work: root@host # ping6 ipv6vm001.fnal.gov Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Testing in mixed mode \u00b6 To test IPv6 in mixed mode, you can use the ntop tool to monitor traffic over IPv6. ntop is installed on all the test machines and you can access the web interface at hostname:3000 . To see a table that displays network traffic between your VM and another host by going to All Protocols -> Traffic and looking at the IPv6 column. Enforcing communication over IPv6 \u00b6 If you want to enforce IPv6 over mixed mode you can try using the IPv6 address for whatever software that you are testing. For example with xrdcp: root@host # xrdcp -d 1 /tmp/first_test root:// [ 2607 :f720:1700:1b30::a4 ] :1094//tmp/first_test_8 [19B/19B][100%][==================================================][0B/s] Notice that the IPv6 address follows RFC2732 .","title":"IPv6 Testing"},{"location":"software/ipv6-testing/#testing-software-with-ipv6","text":"","title":"Testing Software with IPv6"},{"location":"software/ipv6-testing/#about-this-document","text":"This document provides instructions on setting up a host with an IPv6 address for testing the OSG software stack. The plan is to be able to spin up special Fermicloud VM\u2019s that have corresponding public IPv6 addresses meaning that there will be a limit of ~15 VM\u2019s at one time. For more information on IPv6, consult Wikipedia .","title":"About this Document"},{"location":"software/ipv6-testing/#requirements","text":"Be familiar with your institute's network policy and firewall configuration 1 Root access is required to configure iptables","title":"Requirements"},{"location":"software/ipv6-testing/#enabling-ipv6","text":"Determine the public IPv6 address of your host. In the example below that would be 2001:400:2410:29::182 : user@host $ nslookup -type = aaaa <HOSTNAME> Server: 132.239.0.252 Address: 132.239.0.252#53 Non-authoritative answer: ipv6vm001.fnal.gov has AAAA address 2001:400:2410:29::182 Replacing <HOSTNAME> with your machine's hostname. Ask your network administrator for your IPv6 default gateway Modify /etc/sysconfig/network-scripts/ifcfg-eth0 and be sure these lines exist, and : IPV6INIT=yes IPV6_AUTOCONF=no IPV6ADDR=<IPV6 ADDRESS>\" IPV6_DEFAULTGW=\"The IPV6 Default Gateway\" Replace <IPV6 ADDRESS> with the address found in step 1. Restart the network devices: root@host # service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ]","title":"Enabling IPV6"},{"location":"software/ipv6-testing/#testing-ipv6-connectivity","text":"To verify that the VM is capable of IPv6 we will be using the ping6 command between the test VM and another IPv6 capable machine From another IPv6 capable machine, ping your VM: user@host $ ping6 ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov(ipv6vm001.fnal.gov) 56 data bytes 64 bytes from ipv6vm001.fnal.gov: icmp_seq=1 ttl=51 time=68.1 ms 64 bytes from ipv6vm001.fnal.gov: icmp_seq=2 ttl=51 time=57.6 ms From your test VM, ping another IPv6 capable machine: [efajardo@ipv6vm001 ~]# ping6 uaf-4.t2.ucsd.edu PING uaf-4.t2.ucsd.edu(uaf-4.t2.ucsd.edu) 56 data bytes 64 bytes from uaf-4.t2.ucsd.edu: icmp_seq=1 ttl=51 time=57.6 ms","title":"Testing IPv6 connectivity"},{"location":"software/ipv6-testing/#verifying-ssh-over-ipv6","text":"Make sure you can login to your VM over IPv6. Currently, Fermilab's kerberos does not support SSH over IPv6. Add your ssh_key to your machine and make sure /etc/ssh/sshd_config has the following lines: RSAAuthentication yes PubkeyAuthentication yes Try connecting to you IPv6 enabled machine over SSH: efajardo@uaf-4 ~$ ssh -6 root@ipv6vm001.fnal.gov Last login: Wed Jun 11 14:51:47 2014 from 2607:f720:1700:1b30:21f:c6ff:feeb:2631 [root@ipv6vm001 ~]#","title":"Verifying SSH over IPv6"},{"location":"software/ipv6-testing/#disabling-ipv4","text":"If you were able to log into your VM over IPv6, you can disable IPv4 and try to communicate exclusively over IPv6. Comment the IPADDR line in /etc/sysconfig/network-scripts/ifcfg-eth0 : #IPADDR=131.225.41.182 IPV6ADDR=\"2607:f720:1700:1b30::9b\" Note Ensure that your IPV6ADDR is uncommented otherwise you will not be able to connect to the host again Restart the network services: root@host # service network restart The ping command should no longer work: root@host # ping ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov (131.225.41.182): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1","title":"Disabling IPv4"},{"location":"software/ipv6-testing/#disabling-ipv6","text":"In your testing, you may find the need to disable IPv6. root@host # sysctl -w net.ipv6.conf.all.disable_ipv6 = 1 root@host # service network restart The ping6 command should no longer work: root@host # ping6 ipv6vm001.fnal.gov Request timeout for icmp_seq 0 Request timeout for icmp_seq 1","title":"Disabling IPv6"},{"location":"software/ipv6-testing/#testing-in-mixed-mode","text":"To test IPv6 in mixed mode, you can use the ntop tool to monitor traffic over IPv6. ntop is installed on all the test machines and you can access the web interface at hostname:3000 . To see a table that displays network traffic between your VM and another host by going to All Protocols -> Traffic and looking at the IPv6 column.","title":"Testing in mixed mode"},{"location":"software/ipv6-testing/#enforcing-communication-over-ipv6","text":"If you want to enforce IPv6 over mixed mode you can try using the IPv6 address for whatever software that you are testing. For example with xrdcp: root@host # xrdcp -d 1 /tmp/first_test root:// [ 2607 :f720:1700:1b30::a4 ] :1094//tmp/first_test_8 [19B/19B][100%][==================================================][0B/s] Notice that the IPv6 address follows RFC2732 .","title":"Enforcing communication over IPv6"},{"location":"software/koji-mass-rebuilds/","text":"Mass RPM Rebuilds for a new Build Target in Koji \u00b6 Whenever we move to a new OSG series (OSG 3.3) and/or a new RHEL version (EL7), we want to make new builds for all of our packages in the new koji build target (osg-3.3-el7). Due to tricky build dependencies and unexpected build failures, this can be a messy task; and in the past we have gone about it in an ad-hoc manner. This document will discuss some of the aspects of the task and issues involved, some possible approaches, and ultimately a proposal for a general tool or procedure for doing our mass rebuilds. New RHEL version vs new OSG series \u00b6 New RHEL version \u00b6 For a new RHEL version, we start with no osg packages to build against, so we are forced to build things in dependency order. Figuring out the dependency order is possibly the most difficult (or interesting) part of doing mass rebuilds -- more on that later. New OSG series \u00b6 For a new OSG series within an existing RHEL version, we have more options. While it's possible to \"start from scratch\" the same way we would with a new RHEL version and build everything in dependency order, this is not really necessary if we take advantage of existing builds from the previous series. A prior step is to determine the package list for the new series -- this will be some combination of Upcoming and the current release series, minus any packages pruned for the new series. This should also be reflected in the new trunk packaging area. All the current builds for packages in that list (from upcoming + current series) can be tagged into the new *-development (or *-build) repos. This should make all of the build dependencies available for mass rebuilding the new series all at once (osg-build koji *). After some consideration, I wholeheartedly endorse this approach for new OSG series -- for all but academic exercises. Rebuilding in dependency order when all the dependencies are already built just seems like wasted effort. Doing scratch builds of everything first \u00b6 Before doing the mass rebuilds in a new build target, it seems to be a good idea to do scratch builds of all the packages in the current series first. (Or, at least the ones we intend to bring into the new build target.) This will give us a chance to see any build failures that have crept in (possibly due to upstream changes in the OS or EPEL), and fix them first if desired, but in any case avoid the confusion of seeing the failures for the first time in the new build target. Doing mass scratch rebuilds for an existing series is easy, as they can all be done at once. Relatedly, doing a round of scratch builds after successfully building all packages into a new build target can also be useful, because it can reveal dependency issues only present in the new set of builds. Doing developer test installs or a round of VMU tests may also uncover any runtime dependency issues. Options for calculating build dependencies \u00b6 We can get dependency information from a number of places: scraping .spec files for Requires/BuildRequires/Provides and %package names querying existing rpms directly on koji-hub and our OS/EPEL mirrors ( rpm -q ) querying srpms from osg-build prebuild directly for build requirements inspecting previous buildroots to determine resolved build dependencies use repoquery to determine whatrequires/whatprovides for packages use yum-builddep to find packages with all build requirements available using the repodata (primary+filelists) from rpm repositories, including: upcoming + 3.X development + external repos (Centos/EPEL/JPackage), OR osg-upcoming-elX-build, which includes them all One important aspect is that the runtime requirements are also relevant for determining build requirements, since a build will require installing all of the runtime requirements of the packages required for the build. That is, (A BuildRequires B) and (B Requires C) implies A BuildRequires C . Combined with the fact that runtime requirements are transitive, that is, (A Requires B) and (B Requires C) implies A Requires C , computing build requirements is a recursive operation, which can be many levels deep. Another question to keep in mind is whether to use versioned requires/provides (i.e., BuildRequires xyz >= 1.2-3) or to only pay attention to the package/capability names. Similarly, whether to pay any attention to conflicts/obsoletes. These would add complexity to anything except the standard tools (repoquery, yum-builddep) which already take these things into account. (And we may get pretty far even without paying attention to versions.) Note also that the dependencies/capabilities for a given package often varies between different rhel versions. Pre-computing (predictive) vs just-in-time \u00b6 Two different approaches to determining dependency order for building are: pre compute all dependencies based on an existing series/rhel version, OR compute which remaining packages have all build reqs satisfied now The first approach has the benefit of being able to determine the packages that need to be built in order to accomplish a smaller subset goal first -- for example, to be able to install osg-wn-client. (And, if there are problems with resolving certain dependencies (say with osg-wn-client again), it will become apparent earlier, as opposed to not until all possible-to-build packages have been built.) The limitation of this approach is that the predicted set of files/capabilities that a binary package will provide may differ between osg series/rhel versions, and as a result may be inaccurate for the new build target. The second approach provides somewhat more confidence about being able to correctly determine which packages should be buildable at any point in time, but (as mentioned above) it is a bit more in the dark about seeing the bigger picture of the dependency graph or being able to build subsets of targets. It may be useful to have both options available -- building from the list in the second approach, but using the first mechanism to have a better picture of where things are at, or perhaps to steer toward finishing a certain subset of packages first. Package list closure, pruning \u00b6 At some point (either in the planning stage or after building packages into the new build target), we need to ensure that the new osg series/rhel version contains all of its install requirements for all of its packages. It would probably suffice to do a VMU run that installs each package (perhaps individually, to avoid conflicts). But if we go about it more analytically, we may also get, as a result, a list of packages which we previously only maintained for the purpose of building our other packages (ie, that were never required at runtime for any use cases that we cared about), which now, in the new target, are no longer build requirements (directly or indirectly) for any packages that we care about installing. Packages in this category could be reviewed to also be dropped from the new build target. Proposal / Recommendations \u00b6 As mentioned earlier, my recommendation is that we treat a new OSG series differently than a new RHEL version. For a new OSG series: \u00b6 update native/redhat packaging area to reflect packages for new series, including upcoming + trunk - removed packages tag existing builds of packages in new list into the new development tag (eg, for osg-3.3-el6, tag the .osgup.el6 and .osg32.el6 builds into osg-3.3-el6-development) build all packages in new packaging area into new build target at once for all successful builds, remove corresponding old builds (eg, .osgup/.osg32) from the new tag (osg-3.3-el6-development) For a new RHEL version: \u00b6 pull the repodata from the relevant *-build repo from koji: for pre-computing, use a build repo from an existing rhel version: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el6-build/latest/x86_64/repodata/ for just-in-time, use the new build repo: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el8-build/latest/x86_64/repodata/ the primary and filelists (sqlite) files can be used to get runtime requires and provides. (Note that this includes packages from the relevant external repos, also.) generate srpms repodata for the current set of packages to build, with osg-build prebuild and createrepo. the primary (sqlite) file can be used to get build-requires. use sql to resolve direct dependencies at the package name level: src-pkg: bin-pkg (BuildRequires) bin-pkg: bin-pkg (Requires) bin-pkg: src-pkg (bin-pkg comes from which src-pkg? only needed for pre-computing dependencies) resolve this list into a full list of recursive build dependencies. Since this is recursive, there is no way to do it in a fixed number of sql queries. However the above input list is already directly consumable by Make, which is designed to handle recursive dependencies just like this. Or we can write a new tool to do it in python. build ready-to-be-built packages update our copy of the repodata from the regen'ed *-build repo, as often as new versions become available update our dependency lists repeat until all packages are built","title":"Koji Mass Rebuilds"},{"location":"software/koji-mass-rebuilds/#mass-rpm-rebuilds-for-a-new-build-target-in-koji","text":"Whenever we move to a new OSG series (OSG 3.3) and/or a new RHEL version (EL7), we want to make new builds for all of our packages in the new koji build target (osg-3.3-el7). Due to tricky build dependencies and unexpected build failures, this can be a messy task; and in the past we have gone about it in an ad-hoc manner. This document will discuss some of the aspects of the task and issues involved, some possible approaches, and ultimately a proposal for a general tool or procedure for doing our mass rebuilds.","title":"Mass RPM Rebuilds for a new Build Target in Koji"},{"location":"software/koji-mass-rebuilds/#new-rhel-version-vs-new-osg-series","text":"","title":"New RHEL version vs new OSG series"},{"location":"software/koji-mass-rebuilds/#new-rhel-version","text":"For a new RHEL version, we start with no osg packages to build against, so we are forced to build things in dependency order. Figuring out the dependency order is possibly the most difficult (or interesting) part of doing mass rebuilds -- more on that later.","title":"New RHEL version"},{"location":"software/koji-mass-rebuilds/#new-osg-series","text":"For a new OSG series within an existing RHEL version, we have more options. While it's possible to \"start from scratch\" the same way we would with a new RHEL version and build everything in dependency order, this is not really necessary if we take advantage of existing builds from the previous series. A prior step is to determine the package list for the new series -- this will be some combination of Upcoming and the current release series, minus any packages pruned for the new series. This should also be reflected in the new trunk packaging area. All the current builds for packages in that list (from upcoming + current series) can be tagged into the new *-development (or *-build) repos. This should make all of the build dependencies available for mass rebuilding the new series all at once (osg-build koji *). After some consideration, I wholeheartedly endorse this approach for new OSG series -- for all but academic exercises. Rebuilding in dependency order when all the dependencies are already built just seems like wasted effort.","title":"New OSG series"},{"location":"software/koji-mass-rebuilds/#doing-scratch-builds-of-everything-first","text":"Before doing the mass rebuilds in a new build target, it seems to be a good idea to do scratch builds of all the packages in the current series first. (Or, at least the ones we intend to bring into the new build target.) This will give us a chance to see any build failures that have crept in (possibly due to upstream changes in the OS or EPEL), and fix them first if desired, but in any case avoid the confusion of seeing the failures for the first time in the new build target. Doing mass scratch rebuilds for an existing series is easy, as they can all be done at once. Relatedly, doing a round of scratch builds after successfully building all packages into a new build target can also be useful, because it can reveal dependency issues only present in the new set of builds. Doing developer test installs or a round of VMU tests may also uncover any runtime dependency issues.","title":"Doing scratch builds of everything first"},{"location":"software/koji-mass-rebuilds/#options-for-calculating-build-dependencies","text":"We can get dependency information from a number of places: scraping .spec files for Requires/BuildRequires/Provides and %package names querying existing rpms directly on koji-hub and our OS/EPEL mirrors ( rpm -q ) querying srpms from osg-build prebuild directly for build requirements inspecting previous buildroots to determine resolved build dependencies use repoquery to determine whatrequires/whatprovides for packages use yum-builddep to find packages with all build requirements available using the repodata (primary+filelists) from rpm repositories, including: upcoming + 3.X development + external repos (Centos/EPEL/JPackage), OR osg-upcoming-elX-build, which includes them all One important aspect is that the runtime requirements are also relevant for determining build requirements, since a build will require installing all of the runtime requirements of the packages required for the build. That is, (A BuildRequires B) and (B Requires C) implies A BuildRequires C . Combined with the fact that runtime requirements are transitive, that is, (A Requires B) and (B Requires C) implies A Requires C , computing build requirements is a recursive operation, which can be many levels deep. Another question to keep in mind is whether to use versioned requires/provides (i.e., BuildRequires xyz >= 1.2-3) or to only pay attention to the package/capability names. Similarly, whether to pay any attention to conflicts/obsoletes. These would add complexity to anything except the standard tools (repoquery, yum-builddep) which already take these things into account. (And we may get pretty far even without paying attention to versions.) Note also that the dependencies/capabilities for a given package often varies between different rhel versions.","title":"Options for calculating build dependencies"},{"location":"software/koji-mass-rebuilds/#pre-computing-predictive-vs-just-in-time","text":"Two different approaches to determining dependency order for building are: pre compute all dependencies based on an existing series/rhel version, OR compute which remaining packages have all build reqs satisfied now The first approach has the benefit of being able to determine the packages that need to be built in order to accomplish a smaller subset goal first -- for example, to be able to install osg-wn-client. (And, if there are problems with resolving certain dependencies (say with osg-wn-client again), it will become apparent earlier, as opposed to not until all possible-to-build packages have been built.) The limitation of this approach is that the predicted set of files/capabilities that a binary package will provide may differ between osg series/rhel versions, and as a result may be inaccurate for the new build target. The second approach provides somewhat more confidence about being able to correctly determine which packages should be buildable at any point in time, but (as mentioned above) it is a bit more in the dark about seeing the bigger picture of the dependency graph or being able to build subsets of targets. It may be useful to have both options available -- building from the list in the second approach, but using the first mechanism to have a better picture of where things are at, or perhaps to steer toward finishing a certain subset of packages first.","title":"Pre-computing (predictive) vs just-in-time"},{"location":"software/koji-mass-rebuilds/#package-list-closure-pruning","text":"At some point (either in the planning stage or after building packages into the new build target), we need to ensure that the new osg series/rhel version contains all of its install requirements for all of its packages. It would probably suffice to do a VMU run that installs each package (perhaps individually, to avoid conflicts). But if we go about it more analytically, we may also get, as a result, a list of packages which we previously only maintained for the purpose of building our other packages (ie, that were never required at runtime for any use cases that we cared about), which now, in the new target, are no longer build requirements (directly or indirectly) for any packages that we care about installing. Packages in this category could be reviewed to also be dropped from the new build target.","title":"Package list closure, pruning"},{"location":"software/koji-mass-rebuilds/#proposal-recommendations","text":"As mentioned earlier, my recommendation is that we treat a new OSG series differently than a new RHEL version.","title":"Proposal / Recommendations"},{"location":"software/koji-mass-rebuilds/#for-a-new-osg-series","text":"update native/redhat packaging area to reflect packages for new series, including upcoming + trunk - removed packages tag existing builds of packages in new list into the new development tag (eg, for osg-3.3-el6, tag the .osgup.el6 and .osg32.el6 builds into osg-3.3-el6-development) build all packages in new packaging area into new build target at once for all successful builds, remove corresponding old builds (eg, .osgup/.osg32) from the new tag (osg-3.3-el6-development)","title":"For a new OSG series:"},{"location":"software/koji-mass-rebuilds/#for-a-new-rhel-version","text":"pull the repodata from the relevant *-build repo from koji: for pre-computing, use a build repo from an existing rhel version: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el6-build/latest/x86_64/repodata/ for just-in-time, use the new build repo: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el8-build/latest/x86_64/repodata/ the primary and filelists (sqlite) files can be used to get runtime requires and provides. (Note that this includes packages from the relevant external repos, also.) generate srpms repodata for the current set of packages to build, with osg-build prebuild and createrepo. the primary (sqlite) file can be used to get build-requires. use sql to resolve direct dependencies at the package name level: src-pkg: bin-pkg (BuildRequires) bin-pkg: bin-pkg (Requires) bin-pkg: src-pkg (bin-pkg comes from which src-pkg? only needed for pre-computing dependencies) resolve this list into a full list of recursive build dependencies. Since this is recursive, there is no way to do it in a fixed number of sql queries. However the above input list is already directly consumable by Make, which is designed to handle recursive dependencies just like this. Or we can write a new tool to do it in python. build ready-to-be-built packages update our copy of the repodata from the regen'ed *-build repo, as often as new versions become available update our dependency lists repeat until all packages are built","title":"For a new RHEL version:"},{"location":"software/koji-workflow/","text":"Koji Workflow \u00b6 This covers the basics of using and understanding the OSG Koji instance. It is meant primarily for OSG Software team members who need to interact with the service. Terminology \u00b6 Using and understanding the following terminology correctly will help in the reading of this document: Package This refers to a named piece of software in the Koji database. An example would be \"lcmaps\". Build A specific version and release of a package, and an associated state. A build state may be successful (and contain RPMs), failed, or in-progress. A given build may be in one or more tags. The build is associated with the output of the latest build task with the same version and release of the package. Tag A named set of packages and builds, parent tags, and reference to external repositories. An example would be the \"osg-3.3-el6-development\" tag, which contains (among others) the \"lcmaps\" package and the \"lcmaps-1.6.6-1.1.osg33.el6\" build. There is an inheritance structure to tags: by default, all packages/builds in a parent tag are added to the tag. A tag may contain a reference to (possibly inherited) external repositories; the RPMs in these repositories are added to repositories created from this tag. Examples of referenced external repositories include CentOS base, EPEL, or JPackage. Note A tag is NOT a yum repository. Target A target consists of a build tag and a destination tag. An example is \"osg-3.3-el6\", where the build tag is \"osg-3.3-el6-build\" and the destination tag is \"osg-3.3-el6\". A target is used by the build task to know what repository to build from and tag to build into. Task A unit of work for Koji. Several common tasks are: build This task takes a SRPM and a target, and attempts to create a complete Build in the target's destination tag from the target's build repository. This task will launch one buildArch task for each architecture in the destination tag; if each subtask is successful, then it will launch a tagBuild subtask. Note If the build task is marked as \"scratch\", then it won't result in a saved Build. buildArch This task takes a SRPM, architecture name, and a Koji repository as an input, and runs mock to create output RPMs for that arch. The build artifacts are added to the Build if all buildArch tasks are successful. tagBuild This adds a successful build to a given tag. newRepo This creates a new repository from a given tag. Build artifacts The results of a buildArch task. Their metadata are recorded in the Koji database, and files are saved to disk. Metadata may include checksums, timestamps, and who initiated the task. Artifacts may include RPMs, SRPMs, and build logs. Repository A yum repository created from the contents of a tag at a specific point in time. By default, the yum repository will contain all successful, non-blocked builds in the tag, plus all RPMs in the external repositories for the tag. Obtaining Access \u00b6 Building OSG packages in Koji requires these privileges: access to the OSG subversion repository at https://vdt.cs.wisc.edu/svn access to a login node at UW Comp Sci such as moria.cs.wisc.edu access to the Koji service via a grid user certificate See the old user certificates document for information about how to get a user certificate. Open a Freshdesk ticket with the subject \"Requesting access to Koji\" with the following information: - top 3 username choices for the login node and SVN (8 characters max, no punctuation) - the DN of your user certificate Assign the ticket to the Software team. Initial Setup \u00b6 You will be using the OSG Build Tools to interact with Koji. You can use them on either your own machine or on your UW Comp Sci login node such as moria . Setting up on moria \u00b6 Perform the following to set up the build tools on moria : Clone the osg-build git repo you@moria$ git clone https://github.com/opensciencegrid/osg-build $HOME /osg-build Set your $PATH : you@moria$ export PATH = $PATH : $HOME /osg-build you@moria$ export PATH = $PATH :/p/vdt/workspace/quilt/bin you@moria$ export PATH = $PATH :/p/vdt/workspace/tarball-client/stable/sys Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions. Setting up on your own host \u00b6 This requires an Enterprise Linux 6 or 7 host. Install the OSG YUM repositories If using OSG 3.5 or newer, enable the devops repository. Install osg-build and its dependencies: you@host$ sudo yum install osg-build Install a program for getting grid certificates you@host$ sudo yum install globus-proxy-utils Note If you already have voms-clients-cpp or voms-clients-java installed, you can use voms-proxy-init -rfc instead of grid-proxy-init , and don't need to install globus-proxy-utils . (Optional) If you want to do mock builds (these are local builds in a chroot), add yourself to the mock user group: you@host$ sudo usermod -a -G mock $USER Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. Note If you are using a certificate from SAML or Kerberos credentials, such as with cigetcert or kx509 , skip this step. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions. Authenticating to Koji \u00b6 To use the OSG Build tools and the Koji command-line client, you will need to make sure you can authenticate to Koji. This involves getting a grid proxy certificate. Do one of the following: On moria Run osgrun grid-proxy-init -bits 2048 and type your grid certificate password. If you cannot find osgrun , ensure you have /p/vdt/workspace/tarball-client/stable/sys in your $PATH . On your local machine Run grid-proxy-init -bits 2048 (if using globus-proxy-utils ) or voms-proxy-init -rfc -bits 2048 (if using voms-clients ) and type your grid certificate password. On your local machine using SAML or Kerberos-based credentials Run cigetcert or kx509 and perform whatever identification challenges you are asked. To verify your login access and permissions, run: you@host$ osg-koji list-permissions --mine You should see a list of your permissions if successful, or an error message if unsuccessful. Note If you see the error SSL: EE_KEY_TOO_SMALL , OpenSSL may be rejecting your proxy because it is too short. Be sure to request at least 2048 bits by passing -bits 2048 to grid-proxy-init or voms-proxy-init . You can check the key length by examining your proxy: you@host$ openssl x509 -in /tmp/x509up_u $( id -u ) -noout -text and looking at the \"Subject Public Key Info\" which might look like Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) Using Koji \u00b6 Creating a new build \u00b6 We create a new build in Koji from the package's directory in OSG Software subversion. If a successful build already exists in Koji (regardless of whether it is in the tag you use), you cannot replace the build. Two builds are the same if they have the same NVR (Name-Version-Release). You can do a \"scratch\" build, which recompiles, but the results are not added to the tag. This is useful for experimenting with koji. To do a build, execute the following command from within the OSG Software subversion checkout: [you@host]$ osg-build koji <PACKAGE NAME> To do a scratch build, simply add the --scratch command line flag. When you do a non-scratch build, it will build with the osg-el6 and osg-el7 targets. This will assign your build the osg-3.4-el6-development and osg-3.4-el7-development tags (and your package will be assigned the osg-el6 and osg-el7 tags). If successful, your build will end up in the Koji osg-minefield yum repos and will eventually show up in the osg-development yum repos. This is a high latency process. Build task Results \u00b6 How to find build results \u00b6 The most recent build results are always shown on the home page of Koji: https://koji.opensciencegrid.org/koji/index Clicking on a build result brings you to the build information page. A successful build will result in the build page having build logs, RPMs, and a SRPM. If your build isn't in the recent list, you can use the search box in the upper-right-hand corner. Type the exact package name (or use a wildcard), and it will bring up a list of all builds for that package. You can find your build from there. For example, the \"lcmaps\" package page is here: https://koji.opensciencegrid.org/koji/packageinfo?packageID=56 And the lcmaps-1.6.6-1.1.osg33.el6 build is here: https://koji.opensciencegrid.org/koji/buildinfo?buildID=7427 Trying our your build \u00b6 Because it takes a while for your build to get into one of the regular repositories, it's simplest to download your RPM directly (see the previous section on How to find build results), and install it with: [root@host]# yum localinstall <RPM> How to get the resulting RPM into a repository \u00b6 Once a package has been built, it is added to a tag. We then must turn the tag into a yum repository. This is normally done automatically and you do not need to deal with it yourself. Three notes: The kojira daemon creates a repository automatically post-build on the koji-hub host. Eventually, the development repository will be the one hosted by koji-hub. The koji-hub repository can be created manually by running [you@host]$ osg-koji regen-repo <TAG NAME> For example, the tag name for osg-development in 3.4 on el6 is \"osg-3.4-el6-development\". Likely, you won't need to do this when kojira is working. - Repositories are created on external hosts with the mash tool. These are usually triggered by cron jobs, but may be run by hand too. Documentation for running mash is on the TODO list. - You can create your own personal repository using mash . Debugging build issues \u00b6 Failed build tasks can be seen from the Koji homepage. The logs from the tasks are included. Relevant logs include: root.log This is the log of mock trying to create an appropriate build root for your RPM. This will invoke yum twice: once to create a generic build root, once for all the dependencies in your BuildRequires. All RPMs in your build root will be logged here. If mock is unable to create the build root, the reason will show up here. 404 Errors If you see Error downloading packages and HTTP Error 404 - Not Found errors in your root.log , this commonly indicates that an rpm repo mirror was updated and our build repo is out-of-date. This can be fixed by regenerating the relevant build repos for your builds. This is usually something like osg-3.4-el7-build or osg-upcoming-el7-build ; but you can find the exact build tag by clicking the Build Target link for the koji task, and whatever is listed for the Build Tag is the name of the repo to regen. Regenerate each repo that failed with 404 errors: $ osg-koji regen-repo <BUILD TAG> build.log The output of the rpmbuild executable. If your package fails to compile, the reason will show up here. One input to the buildArch task is a repository, which is based on a Koji tag. If the repository hasn't been recreated for a dependency you need (for example, when kojira isn't working), you may not have the right RPMs available in your build root. One common issue is building a chain of dependencies. For example, suppose build B depends on the results of build A. If you build A then build B immediately, B will likely fail. This is because A is not in the repository that B uses. The proper string of events building A, starting the regeneration of the destination and build repo (which should happen in a few minutes of the build A task completing), then submitting build task B. Note if you submit build task B while the build repository task is open, it will not start until the build task has finished. Other errors package <PACKAGE NAME> not in list for tag <TAG> This happens when the name of the directory your package is in does not match the name of the package. You must rename one or the other and commit your changes before trying again. Promoting Builds from Development -> Testing \u00b6 Software contributors can promote any package to testing. Members of the security team can promote ca-cert packages to testing. To promote from development to testing: Using osg-promote \u00b6 Before using osg-promote , authenticate to Koji as above . If you want to promote the latest version: [you@host]$ osg-promote -r <OSGVER>-testing <PACKAGE NAME> <PACKAGE NAME> is the bare package name without version, e.g. gratia-probe . If you want to promote a specific version: [you@host]$ osg-promote -r <OSGVER>-testing <BUILD NAME> <BUILD NAME> is a full name-version-revision.disttag such as gratia-probe-1.17.0-2.osg33.el6 . <OSGVER> is the OSG major version that you are promoting for (e.g. 3.4 ). osg-promote will promote both the el6 and el7 builds of a package. After promoting, copy and paste the JIRA code osg-promote produces into the JIRA ticket that you are working on. For osg-promote , you may omit the .osg34.el6 or .osg34.el7 ; the script will add the appropriate disttag on. See OSG Building Tools for full details on osg-promote . Creating custom koji areas \u00b6 Occasionally you may want to make builds of a package (or packages) which you do not yet want to go into the main development repos. In this case, you can create a set of custom koji tags and build targets for these builds. We have a script in our osg-next-tools repo called new-koji-area that facilitates this set up. Further reading \u00b6 Official Koji documentation: https://docs.pagure.org/koji/ Fedora's koji documentation: https://fedoraproject.org/wiki/Koji Fedora's \"Using Koji\" page: https://docs.fedoraproject.org/en-US/package-maintainers/Using_the_Koji_Build_System/ Note that some instructions there may not apply to OSG's Koji. For the most part though, they are useful.","title":"Koji Workflow"},{"location":"software/koji-workflow/#koji-workflow","text":"This covers the basics of using and understanding the OSG Koji instance. It is meant primarily for OSG Software team members who need to interact with the service.","title":"Koji Workflow"},{"location":"software/koji-workflow/#terminology","text":"Using and understanding the following terminology correctly will help in the reading of this document: Package This refers to a named piece of software in the Koji database. An example would be \"lcmaps\". Build A specific version and release of a package, and an associated state. A build state may be successful (and contain RPMs), failed, or in-progress. A given build may be in one or more tags. The build is associated with the output of the latest build task with the same version and release of the package. Tag A named set of packages and builds, parent tags, and reference to external repositories. An example would be the \"osg-3.3-el6-development\" tag, which contains (among others) the \"lcmaps\" package and the \"lcmaps-1.6.6-1.1.osg33.el6\" build. There is an inheritance structure to tags: by default, all packages/builds in a parent tag are added to the tag. A tag may contain a reference to (possibly inherited) external repositories; the RPMs in these repositories are added to repositories created from this tag. Examples of referenced external repositories include CentOS base, EPEL, or JPackage. Note A tag is NOT a yum repository. Target A target consists of a build tag and a destination tag. An example is \"osg-3.3-el6\", where the build tag is \"osg-3.3-el6-build\" and the destination tag is \"osg-3.3-el6\". A target is used by the build task to know what repository to build from and tag to build into. Task A unit of work for Koji. Several common tasks are: build This task takes a SRPM and a target, and attempts to create a complete Build in the target's destination tag from the target's build repository. This task will launch one buildArch task for each architecture in the destination tag; if each subtask is successful, then it will launch a tagBuild subtask. Note If the build task is marked as \"scratch\", then it won't result in a saved Build. buildArch This task takes a SRPM, architecture name, and a Koji repository as an input, and runs mock to create output RPMs for that arch. The build artifacts are added to the Build if all buildArch tasks are successful. tagBuild This adds a successful build to a given tag. newRepo This creates a new repository from a given tag. Build artifacts The results of a buildArch task. Their metadata are recorded in the Koji database, and files are saved to disk. Metadata may include checksums, timestamps, and who initiated the task. Artifacts may include RPMs, SRPMs, and build logs. Repository A yum repository created from the contents of a tag at a specific point in time. By default, the yum repository will contain all successful, non-blocked builds in the tag, plus all RPMs in the external repositories for the tag.","title":"Terminology"},{"location":"software/koji-workflow/#obtaining-access","text":"Building OSG packages in Koji requires these privileges: access to the OSG subversion repository at https://vdt.cs.wisc.edu/svn access to a login node at UW Comp Sci such as moria.cs.wisc.edu access to the Koji service via a grid user certificate See the old user certificates document for information about how to get a user certificate. Open a Freshdesk ticket with the subject \"Requesting access to Koji\" with the following information: - top 3 username choices for the login node and SVN (8 characters max, no punctuation) - the DN of your user certificate Assign the ticket to the Software team.","title":"Obtaining Access"},{"location":"software/koji-workflow/#initial-setup","text":"You will be using the OSG Build Tools to interact with Koji. You can use them on either your own machine or on your UW Comp Sci login node such as moria .","title":"Initial Setup"},{"location":"software/koji-workflow/#setting-up-on-moria","text":"Perform the following to set up the build tools on moria : Clone the osg-build git repo you@moria$ git clone https://github.com/opensciencegrid/osg-build $HOME /osg-build Set your $PATH : you@moria$ export PATH = $PATH : $HOME /osg-build you@moria$ export PATH = $PATH :/p/vdt/workspace/quilt/bin you@moria$ export PATH = $PATH :/p/vdt/workspace/tarball-client/stable/sys Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions.","title":"Setting up on moria"},{"location":"software/koji-workflow/#setting-up-on-your-own-host","text":"This requires an Enterprise Linux 6 or 7 host. Install the OSG YUM repositories If using OSG 3.5 or newer, enable the devops repository. Install osg-build and its dependencies: you@host$ sudo yum install osg-build Install a program for getting grid certificates you@host$ sudo yum install globus-proxy-utils Note If you already have voms-clients-cpp or voms-clients-java installed, you can use voms-proxy-init -rfc instead of grid-proxy-init , and don't need to install globus-proxy-utils . (Optional) If you want to do mock builds (these are local builds in a chroot), add yourself to the mock user group: you@host$ sudo usermod -a -G mock $USER Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. Note If you are using a certificate from SAML or Kerberos credentials, such as with cigetcert or kx509 , skip this step. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions.","title":"Setting up on your own host"},{"location":"software/koji-workflow/#authenticating-to-koji","text":"To use the OSG Build tools and the Koji command-line client, you will need to make sure you can authenticate to Koji. This involves getting a grid proxy certificate. Do one of the following: On moria Run osgrun grid-proxy-init -bits 2048 and type your grid certificate password. If you cannot find osgrun , ensure you have /p/vdt/workspace/tarball-client/stable/sys in your $PATH . On your local machine Run grid-proxy-init -bits 2048 (if using globus-proxy-utils ) or voms-proxy-init -rfc -bits 2048 (if using voms-clients ) and type your grid certificate password. On your local machine using SAML or Kerberos-based credentials Run cigetcert or kx509 and perform whatever identification challenges you are asked. To verify your login access and permissions, run: you@host$ osg-koji list-permissions --mine You should see a list of your permissions if successful, or an error message if unsuccessful. Note If you see the error SSL: EE_KEY_TOO_SMALL , OpenSSL may be rejecting your proxy because it is too short. Be sure to request at least 2048 bits by passing -bits 2048 to grid-proxy-init or voms-proxy-init . You can check the key length by examining your proxy: you@host$ openssl x509 -in /tmp/x509up_u $( id -u ) -noout -text and looking at the \"Subject Public Key Info\" which might look like Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit)","title":"Authenticating to Koji"},{"location":"software/koji-workflow/#using-koji","text":"","title":"Using Koji"},{"location":"software/koji-workflow/#creating-a-new-build","text":"We create a new build in Koji from the package's directory in OSG Software subversion. If a successful build already exists in Koji (regardless of whether it is in the tag you use), you cannot replace the build. Two builds are the same if they have the same NVR (Name-Version-Release). You can do a \"scratch\" build, which recompiles, but the results are not added to the tag. This is useful for experimenting with koji. To do a build, execute the following command from within the OSG Software subversion checkout: [you@host]$ osg-build koji <PACKAGE NAME> To do a scratch build, simply add the --scratch command line flag. When you do a non-scratch build, it will build with the osg-el6 and osg-el7 targets. This will assign your build the osg-3.4-el6-development and osg-3.4-el7-development tags (and your package will be assigned the osg-el6 and osg-el7 tags). If successful, your build will end up in the Koji osg-minefield yum repos and will eventually show up in the osg-development yum repos. This is a high latency process.","title":"Creating a new build"},{"location":"software/koji-workflow/#build-task-results","text":"","title":"Build task Results"},{"location":"software/koji-workflow/#how-to-find-build-results","text":"The most recent build results are always shown on the home page of Koji: https://koji.opensciencegrid.org/koji/index Clicking on a build result brings you to the build information page. A successful build will result in the build page having build logs, RPMs, and a SRPM. If your build isn't in the recent list, you can use the search box in the upper-right-hand corner. Type the exact package name (or use a wildcard), and it will bring up a list of all builds for that package. You can find your build from there. For example, the \"lcmaps\" package page is here: https://koji.opensciencegrid.org/koji/packageinfo?packageID=56 And the lcmaps-1.6.6-1.1.osg33.el6 build is here: https://koji.opensciencegrid.org/koji/buildinfo?buildID=7427","title":"How to find build results"},{"location":"software/koji-workflow/#trying-our-your-build","text":"Because it takes a while for your build to get into one of the regular repositories, it's simplest to download your RPM directly (see the previous section on How to find build results), and install it with: [root@host]# yum localinstall <RPM>","title":"Trying our your build"},{"location":"software/koji-workflow/#how-to-get-the-resulting-rpm-into-a-repository","text":"Once a package has been built, it is added to a tag. We then must turn the tag into a yum repository. This is normally done automatically and you do not need to deal with it yourself. Three notes: The kojira daemon creates a repository automatically post-build on the koji-hub host. Eventually, the development repository will be the one hosted by koji-hub. The koji-hub repository can be created manually by running [you@host]$ osg-koji regen-repo <TAG NAME> For example, the tag name for osg-development in 3.4 on el6 is \"osg-3.4-el6-development\". Likely, you won't need to do this when kojira is working. - Repositories are created on external hosts with the mash tool. These are usually triggered by cron jobs, but may be run by hand too. Documentation for running mash is on the TODO list. - You can create your own personal repository using mash .","title":"How to get the resulting RPM into a repository"},{"location":"software/koji-workflow/#debugging-build-issues","text":"Failed build tasks can be seen from the Koji homepage. The logs from the tasks are included. Relevant logs include: root.log This is the log of mock trying to create an appropriate build root for your RPM. This will invoke yum twice: once to create a generic build root, once for all the dependencies in your BuildRequires. All RPMs in your build root will be logged here. If mock is unable to create the build root, the reason will show up here. 404 Errors If you see Error downloading packages and HTTP Error 404 - Not Found errors in your root.log , this commonly indicates that an rpm repo mirror was updated and our build repo is out-of-date. This can be fixed by regenerating the relevant build repos for your builds. This is usually something like osg-3.4-el7-build or osg-upcoming-el7-build ; but you can find the exact build tag by clicking the Build Target link for the koji task, and whatever is listed for the Build Tag is the name of the repo to regen. Regenerate each repo that failed with 404 errors: $ osg-koji regen-repo <BUILD TAG> build.log The output of the rpmbuild executable. If your package fails to compile, the reason will show up here. One input to the buildArch task is a repository, which is based on a Koji tag. If the repository hasn't been recreated for a dependency you need (for example, when kojira isn't working), you may not have the right RPMs available in your build root. One common issue is building a chain of dependencies. For example, suppose build B depends on the results of build A. If you build A then build B immediately, B will likely fail. This is because A is not in the repository that B uses. The proper string of events building A, starting the regeneration of the destination and build repo (which should happen in a few minutes of the build A task completing), then submitting build task B. Note if you submit build task B while the build repository task is open, it will not start until the build task has finished. Other errors package <PACKAGE NAME> not in list for tag <TAG> This happens when the name of the directory your package is in does not match the name of the package. You must rename one or the other and commit your changes before trying again.","title":"Debugging build issues"},{"location":"software/koji-workflow/#promoting-builds-from-development-testing","text":"Software contributors can promote any package to testing. Members of the security team can promote ca-cert packages to testing. To promote from development to testing:","title":"Promoting Builds from Development -> Testing"},{"location":"software/koji-workflow/#using-osg-promote","text":"Before using osg-promote , authenticate to Koji as above . If you want to promote the latest version: [you@host]$ osg-promote -r <OSGVER>-testing <PACKAGE NAME> <PACKAGE NAME> is the bare package name without version, e.g. gratia-probe . If you want to promote a specific version: [you@host]$ osg-promote -r <OSGVER>-testing <BUILD NAME> <BUILD NAME> is a full name-version-revision.disttag such as gratia-probe-1.17.0-2.osg33.el6 . <OSGVER> is the OSG major version that you are promoting for (e.g. 3.4 ). osg-promote will promote both the el6 and el7 builds of a package. After promoting, copy and paste the JIRA code osg-promote produces into the JIRA ticket that you are working on. For osg-promote , you may omit the .osg34.el6 or .osg34.el7 ; the script will add the appropriate disttag on. See OSG Building Tools for full details on osg-promote .","title":"Using osg-promote"},{"location":"software/koji-workflow/#creating-custom-koji-areas","text":"Occasionally you may want to make builds of a package (or packages) which you do not yet want to go into the main development repos. In this case, you can create a set of custom koji tags and build targets for these builds. We have a script in our osg-next-tools repo called new-koji-area that facilitates this set up.","title":"Creating custom koji areas"},{"location":"software/koji-workflow/#further-reading","text":"Official Koji documentation: https://docs.pagure.org/koji/ Fedora's koji documentation: https://fedoraproject.org/wiki/Koji Fedora's \"Using Koji\" page: https://docs.fedoraproject.org/en-US/package-maintainers/Using_the_Koji_Build_System/ Note that some instructions there may not apply to OSG's Koji. For the most part though, they are useful.","title":"Further reading"},{"location":"software/new-team-member/","text":"Setup Instructions for New Team Members \u00b6 ssh access to a UW CompSci account, including AFS access Ask CHTC infrastructure Read/write access to the UW Subversion repository; Send email to Mat or Brian L after having obtained UW CompSci account User certificate Follow instructions here Import the certificate into your browser of choice Register for a GGUS account with the following information: Your certificate's subject DN Select none from the \"Virtual Organization\" drop-down Select yes for \"Do you want to have support access?\" and answer \"Why?\" with the following: Yes, I need to comment on tickets as a member of the OSG Software & Release Team (https://www.opensciencegrid.org/technology/#the-team) Access to Koji After obtaining certificate, follow the instructions on the Koji User Management doc Sign up for mailing lists software-discuss@osg-htc.org technology-team@osg-htc.org osg-commits@cs.wisc.edu GitHub team membership https://github.com/orgs/opensciencegrid/teams/software-and-release/members If > 50% S&R, add them to the triage schedule","title":"New Team Member"},{"location":"software/new-team-member/#setup-instructions-for-new-team-members","text":"ssh access to a UW CompSci account, including AFS access Ask CHTC infrastructure Read/write access to the UW Subversion repository; Send email to Mat or Brian L after having obtained UW CompSci account User certificate Follow instructions here Import the certificate into your browser of choice Register for a GGUS account with the following information: Your certificate's subject DN Select none from the \"Virtual Organization\" drop-down Select yes for \"Do you want to have support access?\" and answer \"Why?\" with the following: Yes, I need to comment on tickets as a member of the OSG Software & Release Team (https://www.opensciencegrid.org/technology/#the-team) Access to Koji After obtaining certificate, follow the instructions on the Koji User Management doc Sign up for mailing lists software-discuss@osg-htc.org technology-team@osg-htc.org osg-commits@cs.wisc.edu GitHub team membership https://github.com/orgs/opensciencegrid/teams/software-and-release/members If > 50% S&R, add them to the triage schedule","title":"Setup Instructions for New Team Members"},{"location":"software/osg-build-tools/","text":"OSG Build Tools \u00b6 This page documents the tools used for RPM development for the OSG Software Stack. See the RPM development guide for the principles on which these tools are based. The tools are distributed in the osg-build RPM in our repositories, but can also be used from a Git clone of opensciencegrid/osg-build on GitHub . This page is up-to-date as of osg-build version 1.14.1. The tools \u00b6 osg-build \u00b6 Overview \u00b6 This is the primary tool used in building source and binary RPMs. osg-build <TASK> [options] <PACKAGE DIRECTORY> [...] package_directory is a directory containing an osg/ and/or an upstream/ subdirectory. See the RPM development guide for how these directories are organized. Tasks \u00b6 koji \u00b6 Prebuilds the final source package, then builds it remotely using the Koji instance hosted at UW-Madison. https://koji.opensciencegrid.org By default, the resulting RPMs will end up in the osg-minefield repositories based on the most recent OSG major version (e.g. 3.4). You may specify a different set of repos with --repo , described later. RPMs from the osg-minefield repositories are regularly pulled to the osg-development repositories hosted by the GOC at http://repo.opensciencegrid.org Unless you specify otherwise (by passing --el6 , --el7 or specifying a different koji tag/target), the package will be built for both el6 and el7. This is the method used to build final versions of packages you expect to ship. lint \u00b6 Prebuilds the final source package, then runs rpmlint on it to check for various problems. You will need to have rpmlint installed. People on UW CSL machines should add /p/vdt/workspace/rpmlint to their $PATH. mock \u00b6 Prebuilds the final source package, then builds it locally using mock , and stores the resulting source and binary RPMs in the package-specific _build_results directory. prebuild \u00b6 Prebuilds the final source package from upstream sources (if any) and local files (if any). May create or overwrite the _upstream_srpm_contents and _final_srpm_contents directories. prepare \u00b6 Prebuilds the final source package, then calls rpmbuild -bp on the result, extracting and patching the source files (and performing any other steps defined in the %prep section of the spec file. The resulting sources will be under _final_srpm_contents . rpmbuild \u00b6 Prebuilds the final source package, then builds it locally using rpmbuild , and stores the resulting source and binary RPMs in the package-specific _build_results directory. quilt \u00b6 Collects the upstream local sources and spec file, then calls quilt setup on the spec file, extracting the source files and adding the patches to a quilt series file. See Quilt documentation (PDF link) for more information on quilt; also look at the example in the Usage Patterns section below. Similar to prepare (in fact, quilt calls rpmbuild -bp behind the scenes), but the source tree is in pre-patch state, and various quilt commands can be used to apply and modify patches. Unpacks into _quilt as of osg-build-1.2.2 or _final_srpm_contents in previous versions. Requires quilt . People on UW CSL machines should add /p/vdt/workspace/quilt/bin to their $PATH , and /p/vdt/workspace/quilt/share/man to their $MANPATH . Options \u00b6 This section lists the command-line options. --help \u00b6 Prints the built-in usage information and exits without doing anything else. --version \u00b6 Prints the version of osg-build and exits without doing anything else. Common Options \u00b6 -a, --autoclean, --no-autoclean \u00b6 Before each build, clean out the contents of the underscore directories (_build_results, _final_srpm_contents, _upstream_srpm_contents, _upstream_tarball_contents). If the directories are not cleaned up, earlier builds of a package may interfere with later ones. --no-autoclean will disable this. Default is true . Has no effect with the --vcs flag. -c, --cache-prefix prefix \u00b6 Sets the prefix for upstream source cache references. The prefix must be a valid URI starting with either http , https , or file , or one of the following special values: AFS (corresponds to file:///p/vdt/public/html/upstream , which is the location of the VDT cache using AFS from a UW CS machine). VDT (corresponds to http://vdt.cs.wisc.edu/upstream , which is the location of the VDT cache from off-site). AUTO (AFS if available, VDT if not) The upstream source cache must be organized as described above. All files referenced by .source files in the affected packages must exist in the cache, or a runtime error will occur. Default is AUTO . Has no effect with the --vcs flag. --el6, --el7, --redhat-release version (Config: redhat_release) \u00b6 Sets the distro version to build for. This affects the %dist tag, the mock config, and the default koji tag and target (unless otherwise specified). --el6 is equivalent to --redhat-release 6 --el7 is equivalent to --redhat-release 7 --loglevel loglevel \u00b6 Sets the verbosity of the script. Valid values are: debug , info , warning , error and critical . Default is info . -q, --quiet \u00b6 Do not display as much information. Equivalent to --loglevel warning -v, --verbose \u00b6 Display more information. Equivalent to --loglevel debug -w, --working-directory path \u00b6 Use path as the root directory of the files created by the script. For example, if path is $HOME/working , and the package being built is ndt , the following tree will be created: $HOME/working/ndt/_upstream_srpm_contents $HOME/working/ndt/_upstream_tarball_contents $HOME/working/ndt/_final_srpm_contents $HOME/working/ndt/_build_results If path is TEMP , a randomly named directory under /tmp is used as the working directory. The default setting is to use the package directory as the working directory. Has no effect with the --vcs flag. Options specific to prebuild task \u00b6 --full-extract \u00b6 If set, all upstream tarballs will be extracted into _upstream_tarball_contents/ during the prebuild step. This flag is now mostly redundant with the prepare and quilt tasks. Options specific to rpmbuild and mock tasks \u00b6 --distro-tag dist \u00b6 Sets the distribution tag added on to the end of the release in the RPM ( rpmbuild and mock tasks only ). Default is .osg.el6 or .osg.el7 -t, --target-arch arch \u00b6 Specify an architecture to build packages for ( rpmbuild and mock tasks only ). Default is unspecified, which builds for the current machine architecture. Options specific to mock task \u00b6 --mock-clean, --no-mock-clean \u00b6 Enable/disable deletion of the mock buildroot after a successful build. Default is true . -m, --mock-config path \u00b6 Specifies the mock configuration file to use. This file details how to set up the build environment used by mock for the build, including Yum repositories from which to install dependencies and certain predefined variables (e.g., the distribution tag %dist ). See also --mock-config-from-koji . --mock-config-from-koji build tag \u00b6 Creates a mock config from a Koji build tag. This is the most accurate way to replicate the build environment that Koji will provide (outside of Koji). The build tag is based on the distro version (el6, el7) and the OSG major version (3.3, 3.4). For 3.4 on el6, it is: osg-3.4-el6-build Also requires the Koji command-line tools (package koji ), obtainable from the osg repositories. Since this uses koji, some of the koji-specific options may apply, namely: --koji-backend , --koji-login , and --koji-wrapper . Options specific to koji task \u00b6 --dry-run \u00b6 Do not actually run koji, merely show the command(s) that will be run. For debugging purposes. --getfiles, --get-files \u00b6 For scratch builds without --vcs only. Download the resulting RPMs and logs from the build into the _build_results directory. -k, --kojilogin, --koji-login login \u00b6 Sets the login to use for the koji task. This should most likely be your CN. If not specified, will extract it from your client cert ( ~/.osg-koji/client.crt or ~/.koji/client.crt ). --koji-target target \u00b6 The koji target to use for building. Default is osg-el6 for el6 and osg-el7 for el7. --koji-tag tag \u00b6 The koji tag to add packages to. See the Koji Workflow guide for more information on the terminology. The special value TARGET uses the destination tag defined in the koji target. Default is osg-el6 or osg-el7 . --ktt, --koji-tag-and-target arg \u00b6 Shorthand for setting both --koji-tag and --koji-target to arg . --koji-wrapper, --no-koji-wrapper \u00b6 Enable/disable use of the osg-koji wrapper script around koji. See below for a description of osg-koji . Default is true . --koji-backend backend \u00b6 Specifies the method osg-build will use to interface with Koji. This can be shell or kojilib . --wait, --no-wait, --nowait \u00b6 Wait for koji tasks to finish. Bad for running multiple builds in a single command, since you will have to type in your passphrase for the first one, wait for it to complete, then type in your passphrase for the second one, wait for it to complete, etc. If you want to wait for multiple tasks to finish, use the koji watch-task command or look at the website https://koji.opensciencegrid.org . --wait used to be the default until osg-build-1.1.3 --regen-repos \u00b6 Start a regen-repo koji task on the build tag after each koji build, to update the build repository used for the next build. Not useful unless you are launching multiple builds. This enables you to launch builds that depend on each other. Doesn't work too well with --no-wait , since the next build may be started before the regen-repo task is complete. Waiting will keep the next build from being queued until the regen-repo is complete. --scratch, --no-scratch \u00b6 Perform scratch builds. A scratch build does not go into a repository, but the name-version-release (NVR) of the created RPMs are not considered used, so the build may be modified and repeated without needing a release bump. This has the same use case as the mock task: creating packages that you want to test before releasing. If you do not have a machine with mock set up, or want to test exactly the environment that Koji provides, scratch builds might be more convenient. --vcs, --no-vcs, --svn, --no-svn \u00b6 Have Koji check the package out from a version control system instead of creating an SRPM on the local machine and submitting that to Koji. Currently, SVN and Git are supported. If this flag is specified, you may use SVN URLs or URL@Revision pairs to specify the packages to build. You may continue specify package directories from an SVN checkout, in which case osg-build will use svn info to find the right URL@Revision pair to use and warn you about uncommitted changes. osg-build will also warn you about an outdated working directory. --vcs defaults to true for non-scratch builds, and false for scratch builds. --repo= destination repository , --upcoming \u00b6 Selects the repositories (osg-3.3, upcoming, etc.) to build packages for. Currently valid repositories are: Repository Description osg OSG Software development repos for trunk (this is the default) osg-3.3 (or just 3.3) OSG Software development repos for 3.3 branch upcoming OSG Software development repos for upcoming branch internal OSG Software internal branch hcc Holland Computing Center (Nebraska) testing repos --upcoming is an alias for --repo=upcoming Note that the repo selection affects which VCS paths you are allowed to build from. For example, you are not allowed to build from branches/osg-3.3 (from the OSG SVN) into the 'osg' repo, or from HCC's git repositories into the 'upcoming' repo. koji-tag-diff \u00b6 This script displays the differences between the latest packages in two koji tags. Example invocation: koji-tag-diff osg-3.4-el6-development osg-3.4-el7-testing This prints the packages that are in osg-3.4-el6-development but not in osg-3.4-el7-testing, or vice versa. osg-build-test \u00b6 This script runs automated tests for osg-build . Only a few tests have been implemented so far. osg-import-srpm \u00b6 This is a script to fetch an SRPM from a remote site, copy it into the upstream cache on AFS, and create an SVN package dir (if needed) with an upstream/*.source file. By default it will put downloaded files into the VDT upstream cache (/p/vdt/public/html/upstream), but you can pass --upstream-root=<UPSTREAM DIR> to put them somewhere else. If called with the --extract-spec or -e argument, it will extract the spec file from the SRPM and place it into the osg subdir in SVN. If called with the --diff-spec or -d argument, it will extract the spec file and compare it to the existing spec file in the osg subdir. The script hasn't been touched in a while and needs a good deal of cleanup. A planned feature is to allow doing a three-way diff between the existing RPM before OSG modifications, the new RPM before OSG modifications and the existing RPM after OSG modifications. osg-koji \u00b6 This is a wrapper script around the koji command line tool. It automatically specifies parameters to access the OSG's koji instance, and forces SSL authentication. It takes the same parameters as koji and passes them on. An additional command, osg-koji setup exists, which performs the following tasks: Create a koji configuration in ~/.osg-koji Create a CA bundle for verifying the server. Use either files in /etc/grid-security/certificates , or (if those are not found), from files downloaded from the DOEGrids and DigiCert sites. Create a client cert file. This can be a symlink to your grid proxy, or it can be a file created from your grid public and private key files. The location of those files can be specified by the --usercert and --userkey arguments. If unspecified, usercert defaults to ~/.globus/usercert.pem , and userkey defaults to ~/.globus/userkey.pem . osg-promote \u00b6 Overview \u00b6 Run this script to push packages from one set of repos to another (e.g. from development to testing), according to the OSG software promotion guidelines. Once the packages are promoted, the script will generate code to cut and paste into a JIRA comment. Synopsis \u00b6 osg-promote [-r|--route <ROUTE>]... [options] <PACKAGE OR BUILD> [...] Examples \u00b6 Promote the latest build of osg-version to testing for the current release series osg-promote -r testing osg-version Promote the latest builds of osg-ce to testing for the 3.3 and 3.4 release series osg-promote -r 3.3-testing -r 3.4-testing osg-ce Promote osg-build-1.5.0-1 to testing for the current release series osg-promote -r testing osg-build-1.5.0-1 Arguments \u00b6 -h \u00b6 Display help and a list of valid routes. package or build \u00b6 A package (e.g. osg-version ) or build (e.g. osg-version-3.3.0-1.osg33.el6 ) to promote. You may omit the dist tag (the .osg33.el6 part). If a package is specified, the most recent version of that package will be promoted. If a build is specified, that build and the build that has the same version - release for the other distro version(s) will be promoted. That is, if you specify the route 3.3-testing and the build foo-1-1 , then foo-1-1.osg33.el6 and foo-1-1.osg33.el7 will be promoted. This may be specified multiple times, to promote multiple packages. The NVRs of each set of builds for a package must match. -r ROUTE , --route ROUTE \u00b6 The promotion route to use. Use osg-promote -h to get a list of valid routes. This may be specified multiple times. For example, to promote for both 3.4 and 3.3, pass -r 3.4-testing -r 3.3-testing . If not specified, the testing route is used, which corresponds to the testing route for the latest release series. -n, --dry-run \u00b6 Do not promote, just show what would be done. --el6-only / --el7-only \u00b6 Only promote packages for el6 / el7. --no-el6 / --no-el7 \u00b6 Do not promote packages for el6 / el7. --ignore-rejects \u00b6 Ignore rejections due to version mismatch between dvers or missing package for one dver. --regen \u00b6 Regenerate the destination repos after promoting. -y, --assume-yes \u00b6 Do not prompt before promotion. Common Usage Patterns \u00b6 Verify that all files necessary to build the package are in the right place \u00b6 Run osg-build prebuild <PACKAGEDIR> . Fetch and extract all source files for examination \u00b6 Run osg-build prebuild --full-extract <PACKAGEDIR> . Look inside the _upstream_tarball_contents directory. Get a post-patch version of the upstream sources for examination \u00b6 Run osg-build prepare <PACKAGEDIR> . Look inside the _build_results directory. See which patches work with a new version of a package, update or remove them \u00b6 Place the new source tarball into the upstream cache, edit the version in the spec file and *.sources files as necessary Run osg-build quilt <PACKAGEDIR> . Enter the extracted sources inside the _final_srpm_contents directory. You should see a file called series and a symlink called patches . Type quilt series to get a list of patches in order of application. Type quilt push to apply the next patch. If the patch applies cleanly, continue. If the patch applies with some fuzz, type quilt refresh to update the offsets in the patch. If the patch does not apply and you wish to remove it, type quilt delete <PATCH NAME> (delete only removes it from the series file, not the disk) If the patch does not apply and you wish to fix it, either type quilt push -f to interactively apply the patch, or quilt delete <PATCH NAME> the patch and use quilt new / quilt edit / quilt refresh to edit files and make a new patch from your changes. Consult the quilt(1) manpage for more info. If you have a new patch, run quilt import <PATCHFILE> to add the patch to the series file, and run quilt push to apply it. If you have changes to make to the source code that you want to save as a patch, type quilt new <PATCHNAME> , edit the files, type quilt add <FILE> on each file you edited, then type quilt refresh to recreate the patch. Once you're all done, copy the patches in the patches/ directory to the osg/ dir in SVN, run quilt series to get the application order and update the spec file accordingly. See if a package builds successfully for OSG 3.4 \u00b6 If you have all the build dependencies of the package installed, run osg-build rpmbuild <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have all the build dependencies installed, or want to make sure you specified all of the necessary ones and the package builds from a clean environment, run osg-build mock --mock-config-from-koji osg-3.4-el6-build <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have mock installed, or want to exactly replicate the build environment in Koji, run osg-build koji --scratch <PACKAGEDIR> . You may download the resulting RPMs from kojiweb https://koji.opensciencegrid.org/koji or pass --getfiles to osg-build koji and they will get downloaded to the _build_results directory. Check for potential errors in a package \u00b6 Run osg-build lint <PACKAGEDIR> . Create and test a final build of a package for all platforms for upcoming \u00b6 svn commit your changes in branches/upcoming . Type osg-build koji --repo=upcoming <PACKAGEDIR> Wait for the osg-upcoming-minefield repos to be regenerated containing the new version of your package. You can run osg-koji wait-repo osg-upcoming-el<X>-development --build=<PACKAGENAME-VERSION-RELEASE> and wait for that process to finish (substitute 6 or 7 for X ). Or, you can just check kojiweb https://koji.opensciencegrid.org/koji/tasks . On your test machine, make sure the osg-upcoming-minefield repo is enabled (edit /etc/yum.repos.d/osg-upcoming-minefield.repo or /etc/yum.repos.d/osg-el6-upcoming-minefield.repo ). Clean your cache ( yum clean all; yum clean expire-cache ). Install your software, see if it works. Promote the latest build of a package to testing for the current OSG release series \u00b6 Run osg-promote -r testing <PACKAGE> Promote the latest build of a package to testing for the 3.3 and 3.4 release series \u00b6 Run osg-promote -r 3.3-testing -r 3.4-testing <PACKAGE>","title":"OSG Build Tools"},{"location":"software/osg-build-tools/#osg-build-tools","text":"This page documents the tools used for RPM development for the OSG Software Stack. See the RPM development guide for the principles on which these tools are based. The tools are distributed in the osg-build RPM in our repositories, but can also be used from a Git clone of opensciencegrid/osg-build on GitHub . This page is up-to-date as of osg-build version 1.14.1.","title":"OSG Build Tools"},{"location":"software/osg-build-tools/#the-tools","text":"","title":"The tools"},{"location":"software/osg-build-tools/#osg-build","text":"","title":"osg-build"},{"location":"software/osg-build-tools/#overview","text":"This is the primary tool used in building source and binary RPMs. osg-build <TASK> [options] <PACKAGE DIRECTORY> [...] package_directory is a directory containing an osg/ and/or an upstream/ subdirectory. See the RPM development guide for how these directories are organized.","title":"Overview"},{"location":"software/osg-build-tools/#tasks","text":"","title":"Tasks"},{"location":"software/osg-build-tools/#koji","text":"Prebuilds the final source package, then builds it remotely using the Koji instance hosted at UW-Madison. https://koji.opensciencegrid.org By default, the resulting RPMs will end up in the osg-minefield repositories based on the most recent OSG major version (e.g. 3.4). You may specify a different set of repos with --repo , described later. RPMs from the osg-minefield repositories are regularly pulled to the osg-development repositories hosted by the GOC at http://repo.opensciencegrid.org Unless you specify otherwise (by passing --el6 , --el7 or specifying a different koji tag/target), the package will be built for both el6 and el7. This is the method used to build final versions of packages you expect to ship.","title":"koji"},{"location":"software/osg-build-tools/#lint","text":"Prebuilds the final source package, then runs rpmlint on it to check for various problems. You will need to have rpmlint installed. People on UW CSL machines should add /p/vdt/workspace/rpmlint to their $PATH.","title":"lint"},{"location":"software/osg-build-tools/#mock","text":"Prebuilds the final source package, then builds it locally using mock , and stores the resulting source and binary RPMs in the package-specific _build_results directory.","title":"mock"},{"location":"software/osg-build-tools/#prebuild","text":"Prebuilds the final source package from upstream sources (if any) and local files (if any). May create or overwrite the _upstream_srpm_contents and _final_srpm_contents directories.","title":"prebuild"},{"location":"software/osg-build-tools/#prepare","text":"Prebuilds the final source package, then calls rpmbuild -bp on the result, extracting and patching the source files (and performing any other steps defined in the %prep section of the spec file. The resulting sources will be under _final_srpm_contents .","title":"prepare"},{"location":"software/osg-build-tools/#rpmbuild","text":"Prebuilds the final source package, then builds it locally using rpmbuild , and stores the resulting source and binary RPMs in the package-specific _build_results directory.","title":"rpmbuild"},{"location":"software/osg-build-tools/#quilt","text":"Collects the upstream local sources and spec file, then calls quilt setup on the spec file, extracting the source files and adding the patches to a quilt series file. See Quilt documentation (PDF link) for more information on quilt; also look at the example in the Usage Patterns section below. Similar to prepare (in fact, quilt calls rpmbuild -bp behind the scenes), but the source tree is in pre-patch state, and various quilt commands can be used to apply and modify patches. Unpacks into _quilt as of osg-build-1.2.2 or _final_srpm_contents in previous versions. Requires quilt . People on UW CSL machines should add /p/vdt/workspace/quilt/bin to their $PATH , and /p/vdt/workspace/quilt/share/man to their $MANPATH .","title":"quilt"},{"location":"software/osg-build-tools/#options","text":"This section lists the command-line options.","title":"Options"},{"location":"software/osg-build-tools/#-help","text":"Prints the built-in usage information and exits without doing anything else.","title":"--help"},{"location":"software/osg-build-tools/#-version","text":"Prints the version of osg-build and exits without doing anything else.","title":"--version"},{"location":"software/osg-build-tools/#common-options","text":"","title":"Common Options"},{"location":"software/osg-build-tools/#-a-autoclean-no-autoclean","text":"Before each build, clean out the contents of the underscore directories (_build_results, _final_srpm_contents, _upstream_srpm_contents, _upstream_tarball_contents). If the directories are not cleaned up, earlier builds of a package may interfere with later ones. --no-autoclean will disable this. Default is true . Has no effect with the --vcs flag.","title":"-a, --autoclean, --no-autoclean"},{"location":"software/osg-build-tools/#-c-cache-prefix-prefix","text":"Sets the prefix for upstream source cache references. The prefix must be a valid URI starting with either http , https , or file , or one of the following special values: AFS (corresponds to file:///p/vdt/public/html/upstream , which is the location of the VDT cache using AFS from a UW CS machine). VDT (corresponds to http://vdt.cs.wisc.edu/upstream , which is the location of the VDT cache from off-site). AUTO (AFS if available, VDT if not) The upstream source cache must be organized as described above. All files referenced by .source files in the affected packages must exist in the cache, or a runtime error will occur. Default is AUTO . Has no effect with the --vcs flag.","title":"-c, --cache-prefix prefix"},{"location":"software/osg-build-tools/#-el6-el7-redhat-release-version-config-redhat_release","text":"Sets the distro version to build for. This affects the %dist tag, the mock config, and the default koji tag and target (unless otherwise specified). --el6 is equivalent to --redhat-release 6 --el7 is equivalent to --redhat-release 7","title":"--el6, --el7, --redhat-release version (Config: redhat_release)"},{"location":"software/osg-build-tools/#-loglevel-loglevel","text":"Sets the verbosity of the script. Valid values are: debug , info , warning , error and critical . Default is info .","title":"--loglevel loglevel"},{"location":"software/osg-build-tools/#-q-quiet","text":"Do not display as much information. Equivalent to --loglevel warning","title":"-q, --quiet"},{"location":"software/osg-build-tools/#-v-verbose","text":"Display more information. Equivalent to --loglevel debug","title":"-v, --verbose"},{"location":"software/osg-build-tools/#-w-working-directory-path","text":"Use path as the root directory of the files created by the script. For example, if path is $HOME/working , and the package being built is ndt , the following tree will be created: $HOME/working/ndt/_upstream_srpm_contents $HOME/working/ndt/_upstream_tarball_contents $HOME/working/ndt/_final_srpm_contents $HOME/working/ndt/_build_results If path is TEMP , a randomly named directory under /tmp is used as the working directory. The default setting is to use the package directory as the working directory. Has no effect with the --vcs flag.","title":"-w, --working-directory path"},{"location":"software/osg-build-tools/#options-specific-to-prebuild-task","text":"","title":"Options specific to prebuild task"},{"location":"software/osg-build-tools/#-full-extract","text":"If set, all upstream tarballs will be extracted into _upstream_tarball_contents/ during the prebuild step. This flag is now mostly redundant with the prepare and quilt tasks.","title":"--full-extract"},{"location":"software/osg-build-tools/#options-specific-to-rpmbuild-and-mock-tasks","text":"","title":"Options specific to rpmbuild and mock tasks"},{"location":"software/osg-build-tools/#-distro-tag-dist","text":"Sets the distribution tag added on to the end of the release in the RPM ( rpmbuild and mock tasks only ). Default is .osg.el6 or .osg.el7","title":"--distro-tag dist"},{"location":"software/osg-build-tools/#-t-target-arch-arch","text":"Specify an architecture to build packages for ( rpmbuild and mock tasks only ). Default is unspecified, which builds for the current machine architecture.","title":"-t, --target-arch arch"},{"location":"software/osg-build-tools/#options-specific-to-mock-task","text":"","title":"Options specific to mock task"},{"location":"software/osg-build-tools/#-mock-clean-no-mock-clean","text":"Enable/disable deletion of the mock buildroot after a successful build. Default is true .","title":"--mock-clean, --no-mock-clean"},{"location":"software/osg-build-tools/#-m-mock-config-path","text":"Specifies the mock configuration file to use. This file details how to set up the build environment used by mock for the build, including Yum repositories from which to install dependencies and certain predefined variables (e.g., the distribution tag %dist ). See also --mock-config-from-koji .","title":"-m, --mock-config path"},{"location":"software/osg-build-tools/#-mock-config-from-koji-build-tag","text":"Creates a mock config from a Koji build tag. This is the most accurate way to replicate the build environment that Koji will provide (outside of Koji). The build tag is based on the distro version (el6, el7) and the OSG major version (3.3, 3.4). For 3.4 on el6, it is: osg-3.4-el6-build Also requires the Koji command-line tools (package koji ), obtainable from the osg repositories. Since this uses koji, some of the koji-specific options may apply, namely: --koji-backend , --koji-login , and --koji-wrapper .","title":"--mock-config-from-koji build tag"},{"location":"software/osg-build-tools/#options-specific-to-koji-task","text":"","title":"Options specific to koji task"},{"location":"software/osg-build-tools/#-dry-run","text":"Do not actually run koji, merely show the command(s) that will be run. For debugging purposes.","title":"--dry-run"},{"location":"software/osg-build-tools/#-getfiles-get-files","text":"For scratch builds without --vcs only. Download the resulting RPMs and logs from the build into the _build_results directory.","title":"--getfiles, --get-files"},{"location":"software/osg-build-tools/#-k-kojilogin-koji-login-login","text":"Sets the login to use for the koji task. This should most likely be your CN. If not specified, will extract it from your client cert ( ~/.osg-koji/client.crt or ~/.koji/client.crt ).","title":"-k, --kojilogin, --koji-login login"},{"location":"software/osg-build-tools/#-koji-target-target","text":"The koji target to use for building. Default is osg-el6 for el6 and osg-el7 for el7.","title":"--koji-target target"},{"location":"software/osg-build-tools/#-koji-tag-tag","text":"The koji tag to add packages to. See the Koji Workflow guide for more information on the terminology. The special value TARGET uses the destination tag defined in the koji target. Default is osg-el6 or osg-el7 .","title":"--koji-tag tag"},{"location":"software/osg-build-tools/#-ktt-koji-tag-and-target-arg","text":"Shorthand for setting both --koji-tag and --koji-target to arg .","title":"--ktt, --koji-tag-and-target arg"},{"location":"software/osg-build-tools/#-koji-wrapper-no-koji-wrapper","text":"Enable/disable use of the osg-koji wrapper script around koji. See below for a description of osg-koji . Default is true .","title":"--koji-wrapper, --no-koji-wrapper"},{"location":"software/osg-build-tools/#-koji-backend-backend","text":"Specifies the method osg-build will use to interface with Koji. This can be shell or kojilib .","title":"--koji-backend backend"},{"location":"software/osg-build-tools/#-wait-no-wait-nowait","text":"Wait for koji tasks to finish. Bad for running multiple builds in a single command, since you will have to type in your passphrase for the first one, wait for it to complete, then type in your passphrase for the second one, wait for it to complete, etc. If you want to wait for multiple tasks to finish, use the koji watch-task command or look at the website https://koji.opensciencegrid.org . --wait used to be the default until osg-build-1.1.3","title":"--wait, --no-wait, --nowait"},{"location":"software/osg-build-tools/#-regen-repos","text":"Start a regen-repo koji task on the build tag after each koji build, to update the build repository used for the next build. Not useful unless you are launching multiple builds. This enables you to launch builds that depend on each other. Doesn't work too well with --no-wait , since the next build may be started before the regen-repo task is complete. Waiting will keep the next build from being queued until the regen-repo is complete.","title":"--regen-repos"},{"location":"software/osg-build-tools/#-scratch-no-scratch","text":"Perform scratch builds. A scratch build does not go into a repository, but the name-version-release (NVR) of the created RPMs are not considered used, so the build may be modified and repeated without needing a release bump. This has the same use case as the mock task: creating packages that you want to test before releasing. If you do not have a machine with mock set up, or want to test exactly the environment that Koji provides, scratch builds might be more convenient.","title":"--scratch, --no-scratch"},{"location":"software/osg-build-tools/#-vcs-no-vcs-svn-no-svn","text":"Have Koji check the package out from a version control system instead of creating an SRPM on the local machine and submitting that to Koji. Currently, SVN and Git are supported. If this flag is specified, you may use SVN URLs or URL@Revision pairs to specify the packages to build. You may continue specify package directories from an SVN checkout, in which case osg-build will use svn info to find the right URL@Revision pair to use and warn you about uncommitted changes. osg-build will also warn you about an outdated working directory. --vcs defaults to true for non-scratch builds, and false for scratch builds.","title":"--vcs, --no-vcs, --svn, --no-svn"},{"location":"software/osg-build-tools/#-repodestination-repository-upcoming","text":"Selects the repositories (osg-3.3, upcoming, etc.) to build packages for. Currently valid repositories are: Repository Description osg OSG Software development repos for trunk (this is the default) osg-3.3 (or just 3.3) OSG Software development repos for 3.3 branch upcoming OSG Software development repos for upcoming branch internal OSG Software internal branch hcc Holland Computing Center (Nebraska) testing repos --upcoming is an alias for --repo=upcoming Note that the repo selection affects which VCS paths you are allowed to build from. For example, you are not allowed to build from branches/osg-3.3 (from the OSG SVN) into the 'osg' repo, or from HCC's git repositories into the 'upcoming' repo.","title":"--repo=destination repository, --upcoming"},{"location":"software/osg-build-tools/#koji-tag-diff","text":"This script displays the differences between the latest packages in two koji tags. Example invocation: koji-tag-diff osg-3.4-el6-development osg-3.4-el7-testing This prints the packages that are in osg-3.4-el6-development but not in osg-3.4-el7-testing, or vice versa.","title":"koji-tag-diff"},{"location":"software/osg-build-tools/#osg-build-test","text":"This script runs automated tests for osg-build . Only a few tests have been implemented so far.","title":"osg-build-test"},{"location":"software/osg-build-tools/#osg-import-srpm","text":"This is a script to fetch an SRPM from a remote site, copy it into the upstream cache on AFS, and create an SVN package dir (if needed) with an upstream/*.source file. By default it will put downloaded files into the VDT upstream cache (/p/vdt/public/html/upstream), but you can pass --upstream-root=<UPSTREAM DIR> to put them somewhere else. If called with the --extract-spec or -e argument, it will extract the spec file from the SRPM and place it into the osg subdir in SVN. If called with the --diff-spec or -d argument, it will extract the spec file and compare it to the existing spec file in the osg subdir. The script hasn't been touched in a while and needs a good deal of cleanup. A planned feature is to allow doing a three-way diff between the existing RPM before OSG modifications, the new RPM before OSG modifications and the existing RPM after OSG modifications.","title":"osg-import-srpm"},{"location":"software/osg-build-tools/#osg-koji","text":"This is a wrapper script around the koji command line tool. It automatically specifies parameters to access the OSG's koji instance, and forces SSL authentication. It takes the same parameters as koji and passes them on. An additional command, osg-koji setup exists, which performs the following tasks: Create a koji configuration in ~/.osg-koji Create a CA bundle for verifying the server. Use either files in /etc/grid-security/certificates , or (if those are not found), from files downloaded from the DOEGrids and DigiCert sites. Create a client cert file. This can be a symlink to your grid proxy, or it can be a file created from your grid public and private key files. The location of those files can be specified by the --usercert and --userkey arguments. If unspecified, usercert defaults to ~/.globus/usercert.pem , and userkey defaults to ~/.globus/userkey.pem .","title":"osg-koji"},{"location":"software/osg-build-tools/#osg-promote","text":"","title":"osg-promote"},{"location":"software/osg-build-tools/#overview_1","text":"Run this script to push packages from one set of repos to another (e.g. from development to testing), according to the OSG software promotion guidelines. Once the packages are promoted, the script will generate code to cut and paste into a JIRA comment.","title":"Overview"},{"location":"software/osg-build-tools/#synopsis","text":"osg-promote [-r|--route <ROUTE>]... [options] <PACKAGE OR BUILD> [...]","title":"Synopsis"},{"location":"software/osg-build-tools/#examples","text":"Promote the latest build of osg-version to testing for the current release series osg-promote -r testing osg-version Promote the latest builds of osg-ce to testing for the 3.3 and 3.4 release series osg-promote -r 3.3-testing -r 3.4-testing osg-ce Promote osg-build-1.5.0-1 to testing for the current release series osg-promote -r testing osg-build-1.5.0-1","title":"Examples"},{"location":"software/osg-build-tools/#arguments","text":"","title":"Arguments"},{"location":"software/osg-build-tools/#-h","text":"Display help and a list of valid routes.","title":"-h"},{"location":"software/osg-build-tools/#package-or-build","text":"A package (e.g. osg-version ) or build (e.g. osg-version-3.3.0-1.osg33.el6 ) to promote. You may omit the dist tag (the .osg33.el6 part). If a package is specified, the most recent version of that package will be promoted. If a build is specified, that build and the build that has the same version - release for the other distro version(s) will be promoted. That is, if you specify the route 3.3-testing and the build foo-1-1 , then foo-1-1.osg33.el6 and foo-1-1.osg33.el7 will be promoted. This may be specified multiple times, to promote multiple packages. The NVRs of each set of builds for a package must match.","title":"package or build"},{"location":"software/osg-build-tools/#-r-route-route-route","text":"The promotion route to use. Use osg-promote -h to get a list of valid routes. This may be specified multiple times. For example, to promote for both 3.4 and 3.3, pass -r 3.4-testing -r 3.3-testing . If not specified, the testing route is used, which corresponds to the testing route for the latest release series.","title":"-r ROUTE, --route ROUTE"},{"location":"software/osg-build-tools/#-n-dry-run","text":"Do not promote, just show what would be done.","title":"-n, --dry-run"},{"location":"software/osg-build-tools/#-el6-only-el7-only","text":"Only promote packages for el6 / el7.","title":"--el6-only / --el7-only"},{"location":"software/osg-build-tools/#-no-el6-no-el7","text":"Do not promote packages for el6 / el7.","title":"--no-el6 / --no-el7"},{"location":"software/osg-build-tools/#-ignore-rejects","text":"Ignore rejections due to version mismatch between dvers or missing package for one dver.","title":"--ignore-rejects"},{"location":"software/osg-build-tools/#-regen","text":"Regenerate the destination repos after promoting.","title":"--regen"},{"location":"software/osg-build-tools/#-y-assume-yes","text":"Do not prompt before promotion.","title":"-y, --assume-yes"},{"location":"software/osg-build-tools/#common-usage-patterns","text":"","title":"Common Usage Patterns"},{"location":"software/osg-build-tools/#verify-that-all-files-necessary-to-build-the-package-are-in-the-right-place","text":"Run osg-build prebuild <PACKAGEDIR> .","title":"Verify that all files necessary to build the package are in the right place"},{"location":"software/osg-build-tools/#fetch-and-extract-all-source-files-for-examination","text":"Run osg-build prebuild --full-extract <PACKAGEDIR> . Look inside the _upstream_tarball_contents directory.","title":"Fetch and extract all source files for examination"},{"location":"software/osg-build-tools/#get-a-post-patch-version-of-the-upstream-sources-for-examination","text":"Run osg-build prepare <PACKAGEDIR> . Look inside the _build_results directory.","title":"Get a post-patch version of the upstream sources for examination"},{"location":"software/osg-build-tools/#see-which-patches-work-with-a-new-version-of-a-package-update-or-remove-them","text":"Place the new source tarball into the upstream cache, edit the version in the spec file and *.sources files as necessary Run osg-build quilt <PACKAGEDIR> . Enter the extracted sources inside the _final_srpm_contents directory. You should see a file called series and a symlink called patches . Type quilt series to get a list of patches in order of application. Type quilt push to apply the next patch. If the patch applies cleanly, continue. If the patch applies with some fuzz, type quilt refresh to update the offsets in the patch. If the patch does not apply and you wish to remove it, type quilt delete <PATCH NAME> (delete only removes it from the series file, not the disk) If the patch does not apply and you wish to fix it, either type quilt push -f to interactively apply the patch, or quilt delete <PATCH NAME> the patch and use quilt new / quilt edit / quilt refresh to edit files and make a new patch from your changes. Consult the quilt(1) manpage for more info. If you have a new patch, run quilt import <PATCHFILE> to add the patch to the series file, and run quilt push to apply it. If you have changes to make to the source code that you want to save as a patch, type quilt new <PATCHNAME> , edit the files, type quilt add <FILE> on each file you edited, then type quilt refresh to recreate the patch. Once you're all done, copy the patches in the patches/ directory to the osg/ dir in SVN, run quilt series to get the application order and update the spec file accordingly.","title":"See which patches work with a new version of a package, update or remove them"},{"location":"software/osg-build-tools/#see-if-a-package-builds-successfully-for-osg-34","text":"If you have all the build dependencies of the package installed, run osg-build rpmbuild <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have all the build dependencies installed, or want to make sure you specified all of the necessary ones and the package builds from a clean environment, run osg-build mock --mock-config-from-koji osg-3.4-el6-build <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have mock installed, or want to exactly replicate the build environment in Koji, run osg-build koji --scratch <PACKAGEDIR> . You may download the resulting RPMs from kojiweb https://koji.opensciencegrid.org/koji or pass --getfiles to osg-build koji and they will get downloaded to the _build_results directory.","title":"See if a package builds successfully for OSG 3.4"},{"location":"software/osg-build-tools/#check-for-potential-errors-in-a-package","text":"Run osg-build lint <PACKAGEDIR> .","title":"Check for potential errors in a package"},{"location":"software/osg-build-tools/#create-and-test-a-final-build-of-a-package-for-all-platforms-for-upcoming","text":"svn commit your changes in branches/upcoming . Type osg-build koji --repo=upcoming <PACKAGEDIR> Wait for the osg-upcoming-minefield repos to be regenerated containing the new version of your package. You can run osg-koji wait-repo osg-upcoming-el<X>-development --build=<PACKAGENAME-VERSION-RELEASE> and wait for that process to finish (substitute 6 or 7 for X ). Or, you can just check kojiweb https://koji.opensciencegrid.org/koji/tasks . On your test machine, make sure the osg-upcoming-minefield repo is enabled (edit /etc/yum.repos.d/osg-upcoming-minefield.repo or /etc/yum.repos.d/osg-el6-upcoming-minefield.repo ). Clean your cache ( yum clean all; yum clean expire-cache ). Install your software, see if it works.","title":"Create and test a final build of a package for all platforms for upcoming"},{"location":"software/osg-build-tools/#promote-the-latest-build-of-a-package-to-testing-for-the-current-osg-release-series","text":"Run osg-promote -r testing <PACKAGE>","title":"Promote the latest build of a package to testing for the current OSG release series"},{"location":"software/osg-build-tools/#promote-the-latest-build-of-a-package-to-testing-for-the-33-and-34-release-series","text":"Run osg-promote -r 3.3-testing -r 3.4-testing <PACKAGE>","title":"Promote the latest build of a package to testing for the 3.3 and 3.4 release series"},{"location":"software/ospool-containers/","text":"Containers in the OSPool \u00b6 Tim C. started this document in February 2023 to remember things from hallway discussions. If the scope of this page broadens, be sure to update the title and/or this description. Slot Ad Attributes for Containers \u00b6 There are two seemingly similar Slot Ad attributes in the OSPool related to Singularity: HasSingularity is an HTCondor attribute that indicates whether jobs can run within Singularity containers. It is set to true based on a test that HTCondor performs at start-up, although subsequent container invocations could revoke the value upon certain failure conditions. HAS_SINGULARITY is an OSG pool attribute that indicates whether user payload jobs can and will run within Singularity containers. Only Singularity container runtimes are supported. It is set to true based on a test that is run in the pilot scripts. Note that the test is also baked into the OSPool Backfill Containers. The pilot-script test checks more conditions than the HTCondor HasSingularity one. Periodic scripts in the pilot (i.e., STARTD_CRON ) retest some of these conditions; thus, HAS_SINGULARITY may start out true but become false later in the pilot\u2019s lifetime. When an OSPool job asks to run inside a container, requirements are set to check that both HasSingularity and HAS_SINGULARITY are true for any matching Slot Ad. Containers and Pilots \u00b6 Obviously, Backfill Container \u201cpilots\u201d run inside a container runtime, although the specific choice of container runtime technology is up to the site. Within a GlideinWMS pilot, the pilot scripts determine whether a functioning Singularity container is available, which could come from a local install on each Execution Point or from CVMFS. If detected, then HAS_SINGULARITY is set to true and all user payloads will be run in containers. (It is possible to override this behavior through site-specific pilot hackery.) For Backfill Containers, the container itself includes an installation of Apptainer (n\u00e9e Singularity) and it will always be used (in unprivileged mode) instead of any system or other installation. The user job is a vanilla job. Today, though, a pilot runs the \u201cuser job wrapper\u201d script, which is a replacement for the user\u2019s executable that does some stuff and then runs the user\u2019s executable. If the HAS_SINGULARITY attribute is true in the environment of the wrapper, then it runs the actual user payload job in Singularity (or Apptainer). PID Namespaces \u00b6 PID namespaces are a key technology that enables containers to isolate from each other. See, for example, this Ubuntu copy of the man page for pid_namespaces . The root user always has the ability to create PID namespaces, so a privileged container runtime (i.e., not unprivileged Singularity) can always do this. There is a special feature for user PID namespaces , which can be created by unprivileged processes. To work, there is a certain kernel setting that must be set, and then user PID namespaces are available to all. Today, when the GlideinWMS user job wrapper is about to start a user payload job in a Singularity container, the default is to pass a flag to Singularity to use user PID namespaces. However, if user PID namespaces are not available (say, due to the kernel setting), the pilot start-up scripts do not detect this condition automatically. So, there is a special envirnoment variable that can be set on the outer container (e.g., the Backfill Container) to disable this flag: SINGULARITY_DISABLE_PID_NAMESPACES=1 While set on the outer container, it affects only the user job wrapper and how it invokes the inner Singularity container. Mat says that HTCondor 10.2.2 has a feature to detect the lack of user PID namespaces and, in such a case, to avoid using them, but it is not clear that that feature will help anything as long as the GlideinWMS user job wrapper is being used. Containers and GPUs \u00b6 Most, but certainly not all, OSPool payload jobs that request GPUs also request to run within a container. This is probably due to GPU-using software stacks often being complex, and so users often turn to containers for their runtime environment, including ones that we and others pre-build. Note that the Backfill Container images themselves do not include the NVIDIA CUDA drivers (although, we are experimenting with that). Instead, the CUDA drivers that are installed on the host system are mounted inside the running Backfill Container. This scheme, which works at most OSPool sites, allows GPU payload jobs to work without specifically requesting a container, although see above for why many do so anyway.","title":"OSPool Containers"},{"location":"software/ospool-containers/#containers-in-the-ospool","text":"Tim C. started this document in February 2023 to remember things from hallway discussions. If the scope of this page broadens, be sure to update the title and/or this description.","title":"Containers in the OSPool"},{"location":"software/ospool-containers/#slot-ad-attributes-for-containers","text":"There are two seemingly similar Slot Ad attributes in the OSPool related to Singularity: HasSingularity is an HTCondor attribute that indicates whether jobs can run within Singularity containers. It is set to true based on a test that HTCondor performs at start-up, although subsequent container invocations could revoke the value upon certain failure conditions. HAS_SINGULARITY is an OSG pool attribute that indicates whether user payload jobs can and will run within Singularity containers. Only Singularity container runtimes are supported. It is set to true based on a test that is run in the pilot scripts. Note that the test is also baked into the OSPool Backfill Containers. The pilot-script test checks more conditions than the HTCondor HasSingularity one. Periodic scripts in the pilot (i.e., STARTD_CRON ) retest some of these conditions; thus, HAS_SINGULARITY may start out true but become false later in the pilot\u2019s lifetime. When an OSPool job asks to run inside a container, requirements are set to check that both HasSingularity and HAS_SINGULARITY are true for any matching Slot Ad.","title":"Slot Ad Attributes for Containers"},{"location":"software/ospool-containers/#containers-and-pilots","text":"Obviously, Backfill Container \u201cpilots\u201d run inside a container runtime, although the specific choice of container runtime technology is up to the site. Within a GlideinWMS pilot, the pilot scripts determine whether a functioning Singularity container is available, which could come from a local install on each Execution Point or from CVMFS. If detected, then HAS_SINGULARITY is set to true and all user payloads will be run in containers. (It is possible to override this behavior through site-specific pilot hackery.) For Backfill Containers, the container itself includes an installation of Apptainer (n\u00e9e Singularity) and it will always be used (in unprivileged mode) instead of any system or other installation. The user job is a vanilla job. Today, though, a pilot runs the \u201cuser job wrapper\u201d script, which is a replacement for the user\u2019s executable that does some stuff and then runs the user\u2019s executable. If the HAS_SINGULARITY attribute is true in the environment of the wrapper, then it runs the actual user payload job in Singularity (or Apptainer).","title":"Containers and Pilots"},{"location":"software/ospool-containers/#pid-namespaces","text":"PID namespaces are a key technology that enables containers to isolate from each other. See, for example, this Ubuntu copy of the man page for pid_namespaces . The root user always has the ability to create PID namespaces, so a privileged container runtime (i.e., not unprivileged Singularity) can always do this. There is a special feature for user PID namespaces , which can be created by unprivileged processes. To work, there is a certain kernel setting that must be set, and then user PID namespaces are available to all. Today, when the GlideinWMS user job wrapper is about to start a user payload job in a Singularity container, the default is to pass a flag to Singularity to use user PID namespaces. However, if user PID namespaces are not available (say, due to the kernel setting), the pilot start-up scripts do not detect this condition automatically. So, there is a special envirnoment variable that can be set on the outer container (e.g., the Backfill Container) to disable this flag: SINGULARITY_DISABLE_PID_NAMESPACES=1 While set on the outer container, it affects only the user job wrapper and how it invokes the inner Singularity container. Mat says that HTCondor 10.2.2 has a feature to detect the lack of user PID namespaces and, in such a case, to avoid using them, but it is not clear that that feature will help anything as long as the GlideinWMS user job wrapper is being used.","title":"PID Namespaces"},{"location":"software/ospool-containers/#containers-and-gpus","text":"Most, but certainly not all, OSPool payload jobs that request GPUs also request to run within a container. This is probably due to GPU-using software stacks often being complex, and so users often turn to containers for their runtime environment, including ones that we and others pre-build. Note that the Backfill Container images themselves do not include the NVIDIA CUDA drivers (although, we are experimenting with that). Instead, the CUDA drivers that are installed on the host system are mounted inside the running Backfill Container. This scheme, which works at most OSPool sites, allows GPU payload jobs to work without specifically requesting a container, although see above for why many do so anyway.","title":"Containers and GPUs"},{"location":"software/quilt/","text":"How to Write a Patch \u00b6 You create one or more .patch files with diff and stick them in the osg directory. Then you declare the patch files in the header of the spec file with a line like Patch0: py24compat.patch and in the %prep section, just after %setup , you add a %patch line to actually apply the patch, like this: %patch0 -p1 (where the -p1 indicates that it should strip off the first leading component of the path in each file mentioned in the .patch file) Look at the mash package for an example. The easiest way to actually create the patch in the first place is to use a utility called quilt. First you run osg-build quilt on the package directory and it will create a _quilt subdirectory that has the expanded sources and patches. cd into _quilt/pegasus-source-2.3.0 , then run quilt push -a to apply any patches that already exist (there are none for pegasus but there might be for other packages). run quilt new py24compat.patch to name your new patch file. run quilt add <filename> for each file you want to make changes to (you must run this before making any changes). actually make the changes. run quilt refresh -p1 to have quilt add those changes into the .patch file. (The -p1 option to quilt refresh must be the same as the -p1 option to %patch0 in your spec file). copy patches/py24compat.patch into the pegasus/osg directory and edit the spec file as above. Don't forget to git add your new patch file before committing. Once you've tested your patch successfully, you should make that bug report and send them the patch. A bug report is looked on more favorably if it includes a patch to fix the problem.","title":"Using Quilt"},{"location":"software/quilt/#how-to-write-a-patch","text":"You create one or more .patch files with diff and stick them in the osg directory. Then you declare the patch files in the header of the spec file with a line like Patch0: py24compat.patch and in the %prep section, just after %setup , you add a %patch line to actually apply the patch, like this: %patch0 -p1 (where the -p1 indicates that it should strip off the first leading component of the path in each file mentioned in the .patch file) Look at the mash package for an example. The easiest way to actually create the patch in the first place is to use a utility called quilt. First you run osg-build quilt on the package directory and it will create a _quilt subdirectory that has the expanded sources and patches. cd into _quilt/pegasus-source-2.3.0 , then run quilt push -a to apply any patches that already exist (there are none for pegasus but there might be for other packages). run quilt new py24compat.patch to name your new patch file. run quilt add <filename> for each file you want to make changes to (you must run this before making any changes). actually make the changes. run quilt refresh -p1 to have quilt add those changes into the .patch file. (The -p1 option to quilt refresh must be the same as the -p1 option to %patch0 in your spec file). copy patches/py24compat.patch into the pegasus/osg directory and edit the spec file as above. Don't forget to git add your new patch file before committing. Once you've tested your patch successfully, you should make that bug report and send them the patch. A bug report is looked on more favorably if it includes a patch to fix the problem.","title":"How to Write a Patch"},{"location":"software/release-planning/","text":"Plans for Future Releases \u00b6 This informal page is the mapping of \"technology goals\" (e.g., \"release software Foo version X\") to release numbers. It is meant to be updated as the releases evolve (and items are moved back in schedule). For package support policy between release series, see this page . Unless explicitly noted, bullet points refer to software in the release repo. This page is not meant to track minor bugfixes or updates -- rather, its focus should be new features. OSG 3.4 (May 2017) \u00b6 Package(s) Change in osg-release Notes BeStMan2 Drop Retirement policy edg-mkgridmap Drop SOFTWARE-2600 frontier-squid Modify Version 3 glexec Drop SOFTWARE-2620 GRAM Drop SOFTWARE-2530 GUMS Drop Retirement policy , SOFTWARE-2600 jglobus Drop SOFTWARE-2606 netlogger Drop osg-ce Modify Drop GridFTP , gums-client osg-info-services Drop osg-version Drop singularity Add voms-admin-server Drop Retirement policy Track OSG 3.4 updates through its JIRA epic . Support Policy for OSG 3.3 \u00b6 According to our release support policy and the release date of May 2017 for OSG 3.4, OSG 3.3 will receive routine software updates until November 2017 and critical updates until May 2018. Previous Releases \u00b6 12 November 2013 \u00b6 OSG 3.1 HTCondor-CE with PBS osg-configure emits an ERROR if squid defaults are not changed (\"UNAVAILABLE\" is a valid change) OSG 3.2 Initial release HDFS 2.0.0 (already done in Upcoming) HTCondor 8.0.4 glideinWMS 3.2.0 osg-info-services (Note: ReSS will likely be retired around year-end) OSG 3.1 updates Upcoming HTCondor 8.1 with unified RPM BOSCO 10 December 2013 \u00b6 OSG 3.2 RSV-for-VOs Squid must be present on OSG-CE (??? what does this mean?)","title":"Release Planning"},{"location":"software/release-planning/#plans-for-future-releases","text":"This informal page is the mapping of \"technology goals\" (e.g., \"release software Foo version X\") to release numbers. It is meant to be updated as the releases evolve (and items are moved back in schedule). For package support policy between release series, see this page . Unless explicitly noted, bullet points refer to software in the release repo. This page is not meant to track minor bugfixes or updates -- rather, its focus should be new features.","title":"Plans for Future Releases"},{"location":"software/release-planning/#osg-34-may-2017","text":"Package(s) Change in osg-release Notes BeStMan2 Drop Retirement policy edg-mkgridmap Drop SOFTWARE-2600 frontier-squid Modify Version 3 glexec Drop SOFTWARE-2620 GRAM Drop SOFTWARE-2530 GUMS Drop Retirement policy , SOFTWARE-2600 jglobus Drop SOFTWARE-2606 netlogger Drop osg-ce Modify Drop GridFTP , gums-client osg-info-services Drop osg-version Drop singularity Add voms-admin-server Drop Retirement policy Track OSG 3.4 updates through its JIRA epic .","title":"OSG 3.4 (May 2017)"},{"location":"software/release-planning/#support-policy-for-osg-33","text":"According to our release support policy and the release date of May 2017 for OSG 3.4, OSG 3.3 will receive routine software updates until November 2017 and critical updates until May 2018.","title":"Support Policy for OSG 3.3"},{"location":"software/release-planning/#previous-releases","text":"","title":"Previous Releases"},{"location":"software/release-planning/#12-november-2013","text":"OSG 3.1 HTCondor-CE with PBS osg-configure emits an ERROR if squid defaults are not changed (\"UNAVAILABLE\" is a valid change) OSG 3.2 Initial release HDFS 2.0.0 (already done in Upcoming) HTCondor 8.0.4 glideinWMS 3.2.0 osg-info-services (Note: ReSS will likely be retired around year-end) OSG 3.1 updates Upcoming HTCondor 8.1 with unified RPM BOSCO","title":"12 November 2013"},{"location":"software/release-planning/#10-december-2013","text":"OSG 3.2 RSV-for-VOs Squid must be present on OSG-CE (??? what does this mean?)","title":"10 December 2013"},{"location":"software/repository-management/","text":"Repository Management \u00b6 This document attempts to record everything there is to know about repository management for the OSG. Public repositories \u00b6 We host four public-facing repositories at repo.opensciencegrid.org : development : This repository is the bleeding edge. Installing from this repository may cause the host to stop functioning, and we will not assist in undoing any damage. testing : This repository contains software ready for testing. If you install packages from here, they may be buggy, but we will provide limited assistance in providing a migration path to a fixed verison. release : This repository contains software that we are willing to support and can be used by the general community. contrib : RPMs contributed from outside the OSG. These repos are updated by the mash script running on repo.opensciencegrid.org . Internal repositories \u00b6 In addition to the public repositories above, we host two repositories on koji.opensciencegrid.org . These are updated shortly after jobs are built into them or tagged into them. They are technically publicly accessible, but we discourage the public from using them. minefield : This repository is a copy of development above. prerelease : This repository is a staging area for software that is slated to be in the next release. These repos are updated by the kojira daemon running on koji.opensciencegrid.org . Build repositories \u00b6 Warning this section is out of date; the tags it references no longer exist. The koji task in osg-build uses the osg-3.4-el6-build/osg-3.4-el7-build repo, which is the union of the following repositories: Minefield a.k.a. osg-3.4-el6-development / osg-3.4-el7-development The osg-el6-internal / osg-el7-internal tag (containing build dependencies we do not want to make public) The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist) CentOS and EPEL Koji will work from its internal cache of the above repositories (downloading the packages from the source), and will not update until the build repository is regenerated. By default, Koji does a groupinstall of the build group, then resolves the BuildRequires dependencies. The tarball creation scripts use the osg-3.4-el6-release-build / osg-3.4-el7-release-build repo, which is the union of the following repositories: Release a.k.a. osg-3.4-el6-release / osg-3.4-el7-release The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist ) CentOS and EPEL","title":"Repository Management"},{"location":"software/repository-management/#repository-management","text":"This document attempts to record everything there is to know about repository management for the OSG.","title":"Repository Management"},{"location":"software/repository-management/#public-repositories","text":"We host four public-facing repositories at repo.opensciencegrid.org : development : This repository is the bleeding edge. Installing from this repository may cause the host to stop functioning, and we will not assist in undoing any damage. testing : This repository contains software ready for testing. If you install packages from here, they may be buggy, but we will provide limited assistance in providing a migration path to a fixed verison. release : This repository contains software that we are willing to support and can be used by the general community. contrib : RPMs contributed from outside the OSG. These repos are updated by the mash script running on repo.opensciencegrid.org .","title":"Public repositories"},{"location":"software/repository-management/#internal-repositories","text":"In addition to the public repositories above, we host two repositories on koji.opensciencegrid.org . These are updated shortly after jobs are built into them or tagged into them. They are technically publicly accessible, but we discourage the public from using them. minefield : This repository is a copy of development above. prerelease : This repository is a staging area for software that is slated to be in the next release. These repos are updated by the kojira daemon running on koji.opensciencegrid.org .","title":"Internal repositories"},{"location":"software/repository-management/#build-repositories","text":"Warning this section is out of date; the tags it references no longer exist. The koji task in osg-build uses the osg-3.4-el6-build/osg-3.4-el7-build repo, which is the union of the following repositories: Minefield a.k.a. osg-3.4-el6-development / osg-3.4-el7-development The osg-el6-internal / osg-el7-internal tag (containing build dependencies we do not want to make public) The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist) CentOS and EPEL Koji will work from its internal cache of the above repositories (downloading the packages from the source), and will not update until the build repository is regenerated. By default, Koji does a groupinstall of the build group, then resolves the BuildRequires dependencies. The tarball creation scripts use the osg-3.4-el6-release-build / osg-3.4-el7-release-build repo, which is the union of the following repositories: Release a.k.a. osg-3.4-el6-release / osg-3.4-el7-release The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist ) CentOS and EPEL","title":"Build repositories"},{"location":"software/requesting-tokens/","text":"How to Request Tokens \u00b6 As part of the GridFTP and GSI migration , the OSG will be transitioning authentication away from X.509 certificates to the use of bearer tokens such as SciTokens or WLCG JWT . This document is intended as a guide for OSG developers for requesting tokens necessary for software development. Before Starting \u00b6 Before you can request the appropriate tokens, you must have the following: A WLCG INDIGO IAM account belonging to the wlcg , wlcg/pilots , and wlcg/xfers groups. One of the following: The ability to run containers through tools like docker or podman An installation of oidc-agent available as an RPM from the OSG repositories Requesting Tokens Using a Container \u00b6 oidc-agent is a process that runs in the background that can request access and refresh tokens from OpenID Connect token providers. Registering an OIDC profile \u00b6 Start an agent container in the background and name it my-agent to easily run subsequent commands against it: docker run -d --name my-agent opensciencegrid/oidc-agent:3.6-release Generate a local client profile and follow the prompts: docker exec -it my-agent oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read storage.read:/ XRootD write storage.modify:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions. Requesting access tokens \u00b6 Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : docker exec -it my-agent oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client. Reloading an OIDC profile \u00b6 Note Required after restarting the running container. You must have an existing registered profile . If your existing container is not already running, start it: docker start my-agent Reload profile: docker exec -it my-agent oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration. Requesting Tokens with an RPM installation \u00b6 Registering an OIDC profile \u00b6 Start the agent and add the appropriate variables to your environment: eval `oidc-agent` Generate a local client profile and follow the prompts: oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read read:/ XRootD write write:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions. Requesting access tokens \u00b6 Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client. Reloading an OIDC profile \u00b6 Note Required if you log out of the running machine. You must have an existing registered profile . If you do not already have a running 'oidc-agent', start one: eval 'oidc-agent' Reload profile: oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration. Troubleshooting Tokens \u00b6 You can inspect the payload by copy-pasting the token into the \"Encoded\" text box here: http://jwt.io/ . Mouse over the fields and values for details.","title":"How to Request Tokens"},{"location":"software/requesting-tokens/#how-to-request-tokens","text":"As part of the GridFTP and GSI migration , the OSG will be transitioning authentication away from X.509 certificates to the use of bearer tokens such as SciTokens or WLCG JWT . This document is intended as a guide for OSG developers for requesting tokens necessary for software development.","title":"How to Request Tokens"},{"location":"software/requesting-tokens/#before-starting","text":"Before you can request the appropriate tokens, you must have the following: A WLCG INDIGO IAM account belonging to the wlcg , wlcg/pilots , and wlcg/xfers groups. One of the following: The ability to run containers through tools like docker or podman An installation of oidc-agent available as an RPM from the OSG repositories","title":"Before Starting"},{"location":"software/requesting-tokens/#requesting-tokens-using-a-container","text":"oidc-agent is a process that runs in the background that can request access and refresh tokens from OpenID Connect token providers.","title":"Requesting Tokens Using a Container"},{"location":"software/requesting-tokens/#registering-an-oidc-profile","text":"Start an agent container in the background and name it my-agent to easily run subsequent commands against it: docker run -d --name my-agent opensciencegrid/oidc-agent:3.6-release Generate a local client profile and follow the prompts: docker exec -it my-agent oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read storage.read:/ XRootD write storage.modify:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions.","title":"Registering an OIDC profile"},{"location":"software/requesting-tokens/#requesting-access-tokens","text":"Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : docker exec -it my-agent oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client.","title":"Requesting access tokens"},{"location":"software/requesting-tokens/#reloading-an-oidc-profile","text":"Note Required after restarting the running container. You must have an existing registered profile . If your existing container is not already running, start it: docker start my-agent Reload profile: docker exec -it my-agent oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration.","title":"Reloading an OIDC profile"},{"location":"software/requesting-tokens/#requesting-tokens-with-an-rpm-installation","text":"","title":"Requesting Tokens with an RPM installation"},{"location":"software/requesting-tokens/#registering-an-oidc-profile_1","text":"Start the agent and add the appropriate variables to your environment: eval `oidc-agent` Generate a local client profile and follow the prompts: oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read read:/ XRootD write write:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions.","title":"Registering an OIDC profile"},{"location":"software/requesting-tokens/#requesting-access-tokens_1","text":"Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client.","title":"Requesting access tokens"},{"location":"software/requesting-tokens/#reloading-an-oidc-profile_1","text":"Note Required if you log out of the running machine. You must have an existing registered profile . If you do not already have a running 'oidc-agent', start one: eval 'oidc-agent' Reload profile: oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration.","title":"Reloading an OIDC profile"},{"location":"software/requesting-tokens/#troubleshooting-tokens","text":"You can inspect the payload by copy-pasting the token into the \"Encoded\" text box here: http://jwt.io/ . Mouse over the fields and values for details.","title":"Troubleshooting Tokens"},{"location":"software/resurrecting-epel-packages/","text":"Resurrecting EPEL RPMs \u00b6 You will need to be a Koji admin to do these steps. [user@client ~] $ osg-koji --list-permissions --mine Will tell you if you're an admin or not. Current Koji admins are the Madison team and Brian Bockelman. EPEL version EPEL Koji tag Our Koji tag 5 dist-5E-epel epelrescue-el5 6 dist-6E-epel epelrescue-el6 7 epel7 epelrescue-el7 Determine the NVR of the build containing the RPM of the package you want. Use the Fedora/EPEL Koji web interface ( https://koji.fedoraproject.org ) to search for it. You can use the search box in the upper right to look for packages, builds, or RPMs; it accepts shell wildcards. EPEL builds have .el5, .el6, or .el7 in the dist tag. Download all RPMs for all architectures we care about (i386, i486, i586, i686, x86_64, noarch), including the .src.rpm and the debuginfo rpms. You have three options for the downloads: Use the links in the web interface Use the koji command-line interface against the Fedora koji: Download fedora-koji.conf , attached to this page Run koji --noauth -c fedora-koji.conf download-build --debuginfo <PACKAGE_NVR> Delete RPMs for architectures we do not care about (see list above) <PACKAGE_NVR> is the Name-Version-Release information about the build, which was determined in the step 1 above Dig around in https://kojipkgs.fedoraproject.org/packages/ On your development machine: Important: Verify that all of the RPMs are signed: [root@client ~] # rpm -K *.rpm | grep -iv gpg should be empty If not, STOP and sign them using the OSG RPM key -- talk to Mat Import the RPMs themselves into the Koji system [user@client ~] $ osg-koji import <RPM_DIRECTORY>/*.rpm Where <RPM_DIRECTORY> is the directory where you have downloaded the rpms. They will not be in any tags at this point Add the package to the whitelist for our koji tag: [user@client ~] $ osg-koji add-pkg <OUR_KOJI_TAG> <PACKAGE> --owner = \"<YOUR_KOJI_USERNAME>\" Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page, an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 and <YOUR_KOJI_USERNAME> is the username you use to interact with the Koji system Actually tag the builds: [user@client ~] $ osg-koji tag-pkg <OUR_KOJI_TAG> <PACKAGE> Check the Tasks tab in Koji to see if kojira has started regening the repos -- it might take a few minutes to kick in. If it doesn't, do it manually (if you're doing multiple packages, save this step until you're done with all of them): for repo in osg-{3.1,3.2,3.3,upcoming}-el5-{build,development,testing,release,prerelease,release-build}; do osg-koji regen-repo --nowait $repo done Make a test VM and install the package from minefield to test that it is actually present. Update the epelrescue RPMs table below Removing resurrected RPMs \u00b6 In case the RPM appeared back in EPEL, or we no longer need it, here's how to remove it from the epelrescue tags so we're not overriding the EPEL version: Find out the NVR of the build: [user@client ~] $ osg-koji list-tagged <OUR_KOJI_TAG> <PACKAGE> Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page and an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 Untag the packages: [user@client ~] $ osg-koji untag-pkg <OUR_KOJI_TAG> <PACKAGE> Why you should not use block-pkg \u00b6 EPEL removes their packages by using 'koji block-pkg', which leaves the package and the builds in the tag, but prevents it from appearing in the repos. We cannot do that, because blocks are inherited and this will mess up our build repos. This is what happened in one case: EPEL removed rpmdevtools, which is a necessary package for all builds. I resurrected it into epelrescue-el5. Later, EPEL put rpmdevtools back into their repos, so it no longer needed to be in epelrescue-el5. I used block-pkg on rpmdevtools in epelrescue-el5, thinking that the package could remain tagged, but will stay out of our repos, and the EPEL package would be used instead. The block not only hid our rpmdevtools, it hid EPEL's rpmdevtools as well, preventing us from being able to build. I unblocked the rpmdevtools, and just untagged the build instead, regenerated our build repos, and we could build again. Policy for epelrescue tags \u00b6 https://jira.opensciencegrid.org/browse/SOFTWARE-2046 Table of epelrescue RPMs \u00b6 Package Distro version Date added Reason added Date removed python-six-1.7.3-1.el6 6 2015-08-12 Dep of osg-build (via mock) 2015-10-14 python-argparse-1.2.1-2.el6 6 2015-09-23 Dep of osg-wn-client (via gfal2) 2015-10-14 python-backports-ssl_match_hostname-3.4.0.2-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-requests-1.1.0-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-urllib3-1.5-7.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 Finding out if a package is still needed in epelrescue \u00b6 Set $pkg to the name of a package to test (e.g. python-six ), and $rhel set to the RHEL version you're testing for (e.g. 5 , 6 , or 7 ). Using Carl's centos-srpms , scientific-srpms , slf-srpms scripts: for script in centos-srpms scientific-srpms slf-srpms; do echo -n $script \": \" $script -$rhel $pkg | grep . || echo none done A dry run of removing the package: osg-koji untag-pkg -n --all epelrescue-el$rhel $pkg Remove the -n when the output of that looks fine.","title":"Resurrecting Epel Packages"},{"location":"software/resurrecting-epel-packages/#resurrecting-epel-rpms","text":"You will need to be a Koji admin to do these steps. [user@client ~] $ osg-koji --list-permissions --mine Will tell you if you're an admin or not. Current Koji admins are the Madison team and Brian Bockelman. EPEL version EPEL Koji tag Our Koji tag 5 dist-5E-epel epelrescue-el5 6 dist-6E-epel epelrescue-el6 7 epel7 epelrescue-el7 Determine the NVR of the build containing the RPM of the package you want. Use the Fedora/EPEL Koji web interface ( https://koji.fedoraproject.org ) to search for it. You can use the search box in the upper right to look for packages, builds, or RPMs; it accepts shell wildcards. EPEL builds have .el5, .el6, or .el7 in the dist tag. Download all RPMs for all architectures we care about (i386, i486, i586, i686, x86_64, noarch), including the .src.rpm and the debuginfo rpms. You have three options for the downloads: Use the links in the web interface Use the koji command-line interface against the Fedora koji: Download fedora-koji.conf , attached to this page Run koji --noauth -c fedora-koji.conf download-build --debuginfo <PACKAGE_NVR> Delete RPMs for architectures we do not care about (see list above) <PACKAGE_NVR> is the Name-Version-Release information about the build, which was determined in the step 1 above Dig around in https://kojipkgs.fedoraproject.org/packages/ On your development machine: Important: Verify that all of the RPMs are signed: [root@client ~] # rpm -K *.rpm | grep -iv gpg should be empty If not, STOP and sign them using the OSG RPM key -- talk to Mat Import the RPMs themselves into the Koji system [user@client ~] $ osg-koji import <RPM_DIRECTORY>/*.rpm Where <RPM_DIRECTORY> is the directory where you have downloaded the rpms. They will not be in any tags at this point Add the package to the whitelist for our koji tag: [user@client ~] $ osg-koji add-pkg <OUR_KOJI_TAG> <PACKAGE> --owner = \"<YOUR_KOJI_USERNAME>\" Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page, an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 and <YOUR_KOJI_USERNAME> is the username you use to interact with the Koji system Actually tag the builds: [user@client ~] $ osg-koji tag-pkg <OUR_KOJI_TAG> <PACKAGE> Check the Tasks tab in Koji to see if kojira has started regening the repos -- it might take a few minutes to kick in. If it doesn't, do it manually (if you're doing multiple packages, save this step until you're done with all of them): for repo in osg-{3.1,3.2,3.3,upcoming}-el5-{build,development,testing,release,prerelease,release-build}; do osg-koji regen-repo --nowait $repo done Make a test VM and install the package from minefield to test that it is actually present. Update the epelrescue RPMs table below","title":"Resurrecting EPEL RPMs"},{"location":"software/resurrecting-epel-packages/#removing-resurrected-rpms","text":"In case the RPM appeared back in EPEL, or we no longer need it, here's how to remove it from the epelrescue tags so we're not overriding the EPEL version: Find out the NVR of the build: [user@client ~] $ osg-koji list-tagged <OUR_KOJI_TAG> <PACKAGE> Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page and an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 Untag the packages: [user@client ~] $ osg-koji untag-pkg <OUR_KOJI_TAG> <PACKAGE>","title":"Removing resurrected RPMs"},{"location":"software/resurrecting-epel-packages/#why-you-should-not-use-block-pkg","text":"EPEL removes their packages by using 'koji block-pkg', which leaves the package and the builds in the tag, but prevents it from appearing in the repos. We cannot do that, because blocks are inherited and this will mess up our build repos. This is what happened in one case: EPEL removed rpmdevtools, which is a necessary package for all builds. I resurrected it into epelrescue-el5. Later, EPEL put rpmdevtools back into their repos, so it no longer needed to be in epelrescue-el5. I used block-pkg on rpmdevtools in epelrescue-el5, thinking that the package could remain tagged, but will stay out of our repos, and the EPEL package would be used instead. The block not only hid our rpmdevtools, it hid EPEL's rpmdevtools as well, preventing us from being able to build. I unblocked the rpmdevtools, and just untagged the build instead, regenerated our build repos, and we could build again.","title":"Why you should not use block-pkg"},{"location":"software/resurrecting-epel-packages/#policy-for-epelrescue-tags","text":"https://jira.opensciencegrid.org/browse/SOFTWARE-2046","title":"Policy for epelrescue tags"},{"location":"software/resurrecting-epel-packages/#table-of-epelrescue-rpms","text":"Package Distro version Date added Reason added Date removed python-six-1.7.3-1.el6 6 2015-08-12 Dep of osg-build (via mock) 2015-10-14 python-argparse-1.2.1-2.el6 6 2015-09-23 Dep of osg-wn-client (via gfal2) 2015-10-14 python-backports-ssl_match_hostname-3.4.0.2-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-requests-1.1.0-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-urllib3-1.5-7.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14","title":"Table of epelrescue RPMs"},{"location":"software/resurrecting-epel-packages/#finding-out-if-a-package-is-still-needed-in-epelrescue","text":"Set $pkg to the name of a package to test (e.g. python-six ), and $rhel set to the RHEL version you're testing for (e.g. 5 , 6 , or 7 ). Using Carl's centos-srpms , scientific-srpms , slf-srpms scripts: for script in centos-srpms scientific-srpms slf-srpms; do echo -n $script \": \" $script -$rhel $pkg | grep . || echo none done A dry run of removing the package: osg-koji untag-pkg -n --all epelrescue-el$rhel $pkg Remove the -n when the output of that looks fine.","title":"Finding out if a package is still needed in epelrescue"},{"location":"software/rpm-development-guide/","text":"RPM Development Guide \u00b6 This page documents technical guidelines and details about RPM development for the OSG Software Stack. The procedures, conventions, and policies defined within are used by the OSG Software Team, and are recommended to all external developers who wish to contribute to the OSG Software Stack. Principles \u00b6 The principles below guide the design and implementation of the technical details that follow. Packages should adhere to community standards (e.g., Fedora Packaging Guidelines when possible, and significant deviations must be documented Every released package must be reproducible from data stored in our system Source code for software should be clearly separable from the packaging of that software Upstream source files (which should not be modified) should be clearly separated from files owned by the OSG Software Team Building source and binary packages from our system should be easy and efficient External developers should have a clear and effective system for developing and contributing packages We should use standard tools from relevant packaging and development communities when appropriate Contributing Packages \u00b6 We encourage all interested parties to contribute to OSG Software, and all the infrastructure described on this page should be friendly to external contributors. To participate in the packaging community: You must subscribe to the software-discuss@osg-htc.org email list. To create and edit packages: Obtain access to VDT SVN . To upload new source tarballs: You must have a cs.wisc.edu account with write access to the VDT source tarball directory. Email the osg-software list and request permission. To build using the OSG's Koji build system: You must have a valid personal certificate and a Koji account. To obtain the Koji account, email the osg-software list with your cert's DN and request permission. Development Infrastructure \u00b6 This section documents most of what a developer needs to know about our RPM infrastructure: Upstream Source Cache \u2014 a filesystem scheme for caching upstream source files Revision Control System \u2014 where to get and store development files, and how they are organized Build System \u2014 how to build packages from the revision control system Yum Repository \u2014 the location and organization of our Yum repository, and how to promote packages through it Upstream Source Cache \u00b6 One of our principles (every released package must be reproducible from data stored in our system) creates a potential issue: If we keep all historical source data, especially upstream files like source tarballs and source RPMs, in our revision control system, we may face large checkouts and consequently long checkout and update times. Our solution is to cache all upstream source files in a separate filesystem area, retaining historical files indefinitely. To avoid tainting upstream files, our policy is to leave them unmodified after download. Locating Files in the Cache \u00b6 Upstream source files are stored in the filesystem as follows: /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> where: Symbol Definition Example <PACKAGE> Upstream name of the source package, or some widely accepted form thereof ndt <VERSION> Upstream version string used to identify the release 3.6.4 <FILE> Upstream filename itself ndt-3.6.4.tar.gz The authoritative cache is the VDT webserver, which is fully backed up. The Koji build system uses this cache. Upstream source files are referenced from within the revision control system; see below for details. You will need to know the SHA1 checksum of any files you use from the cache. Do get it, do: $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> Contributing Upstream Files \u00b6 You must make sure that any new upstream source files are cached on the VDT webserver before building the package via Koji. You have two options: If you have access to a UW\u2013Madison CSL machine, you can scp the source files directly into the AFS locations using that machine If you do not have such access, write to the osg-software list to find someone who will post the files for you Git/GitHub Hosted Upstream Files \u00b6 It is also possible to pull sources and spec files from remote Git or GitHub repos instead of our source cache. See the upstream dir info for more information. Revision Control System \u00b6 All packages that the OSG Software Team releases are checked into our Subversion repository. Subversion Access \u00b6 Our Subversion repository is located at: https://vdt.cs.wisc.edu/svn Procedure for offsite users obtaining access to Subversion Or, from a UW\u2013Madison Computer Sciences machine: file:///p/condor/workspaces/vdt/svn The current SVN directory housing our native package work is $SVN/native/redhat (where $SVN is one of the ways of accessing our SVN repository above). For example, to check out the current package repository via HTTPS, do: [you@host]$ svn co https://vdt.cs.wisc.edu/svn/native/redhat OSG-Owned Software \u00b6 OSG-owned software goes into GitHub under the opensciencegrid organization. Files are organized as the developer sees fit. It is strongly recommended that each software package include a top-level Makefile with at least the following targets: Symbol Purpose install Install the software into final FHS locations rooted at DESTDIR dist Create a distribution source tarball (in the current section directory) for a release upstream Install the distribution source tarball into the upstream source cache Packaging Top-Level Directory Organization \u00b6 The top levels of our Subversion directory hierarchy for packaging are as follows: native/redhat/<SECTION>/<PACKAGE> where: Symbol Definition Example <SECTION> Development section Standard Subversion sections like trunk and branches/* <PACKAGE> Our standardized name for a source package ndt Package Directory Organization \u00b6 Within a source package directory, the following files (detailed in separate sections below) may exist: README text file package notes, by and for developers upstream/ directory references to the upstream source cache and other kinds of upstream files osg/ directory overrides and patches of upstream files, plus new files, which contribute to the final OSG source package README \u00b6 This is a free-form text file for developers to leave notes about the package. Please document anything interesting about how you procured the upstream source, the reasons for the modifications you made, or anything else people might need to know in order to maintain the package in the future. Please document the why , not just the what . upstream \u00b6 Within the per-package directories of the revision control system, there must be a way to refer to cached files. This is done with small text files that (a) are named consistently, and (b) contain the location of the referenced file as its contents. A reference file is named: <DESCRIPTION>.<TYPE>.source where: Symbol Definition Example <DESCRIPTION> Descriptive label of the source of the referenced file developer , epel , emi <TYPE> Type of referenced file tarball , srpm and contain references to cached files, Git repos, and comments. which start with # and continue until the end of the line. It is useful to add the source of the upstream file into a comment. Cached files \u00b6 To reference files in the upstream source cache, use the upstream source cache path defined above, without the prefix component, followed by the sha1sum of the file: <PACKAGE>/<VERSION>/<FILE> sha1sum=<SHA1SUM> Obtain the sha1sum by running the sha1sum command with the source file as an argument, i.e. $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> Note This feature requires OSG-Build 1.14.0 or later. Example The reference file for globus-common 's source tarball is named epel.srpm.source and contains: globus-common/16.4/globus-common-16.4-1.el6.src.rpm sha1sum=134478c56c2437c335c20636831f794b66290bec # Downloaded from 'http://dl.fedoraproject.org/pub/epel/6/SRPMS/globus-common-16.4-1.el6.src.rpm' GitHub repos \u00b6 Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note See also advanced features for Git and GitHub repos . To reference tags in GitHub repos, use the following syntax (all on one line): type=github repo=<OWNER>/<PROJECT> tag=<TAG> hash=<HASH> where: Symbol Definition Example <OWNER> Owner of the GitHub repo opensciencegrid <PROJECT> Name of the project osg-build <TAG> Git tag to use v1.12.2 <HASH> Full 40-char Git hash of the tag cff50ffe812282552cedae81f3809d3cf7087a3e Note The tarball will be called <PROJECT>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example You can refer to the 1.12.2 release of osg-build with this line: type=github repo=opensciencegrid/osg-build tag=v1.12.2 hash=cff50ffe812282552cedae81f3809d3cf7087a3e This results in a tarball named osg-build-1.12.2.tar.gz . In addition, if the repository contains a file called rpm/<PROJECT>.spec , it will be used as the spec file for the build (unless overridden in the osg directory). Git repos \u00b6 Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note You can use a shorter syntax for GitHub repos -- see above. See also advanced features for Git and GitHub repos . To reference tags in Git repos, use the following syntax (all on one line): type=git url=<URL> name=<NAME> tag=<TAG> hash=<HASH> where: Symbol Definition Example <URL> Location of the Git repo https://github.com/opensciencegrid/osg-build.git <NAME> Name of the software (optional) osg-build <TAG> Git tag to use v1.11.2 <HASH> Full 40-char Git hash of the tag 5bcf48c442d21b1e8c93a468d884f84122f7cc9e Note <NAME> is optional; if not present, OSG-Build will use the last component of the URL, without the .git suffix. The tarball will be called <NAME>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example The reference file for osg-build 's repo is named osg.github.source and contains: type=git url=https://github.com/opensciencegrid/osg-build.git name=osg-build tag=v1.11.2 hash=5bcf48c442d21b1e8c93a468d884f84122f7cc9e This results in a tarball named osg-build-1.11.2.tar.gz . In addition, if the repository contains a file called rpm/<NAME>.spec , it will be used as the spec file for the build (unless overridden in the osg directory). Typical workflow when building out of GitHub repos \u00b6 Fork the repository of the package that you would like to build Create a new branch in your fork Make, commit, and push changes to your new branch In your fork, tag the commit that you would like to build In the upstream/osg.github.source , change the repo to point at your fork and tag Attempt a scratch build If the build fails, remove the tag and repeat steps 3-6 Submit a PR to merge changes upstream Tag the final version on the upstream fork Build the version that will go through the normal software cycle Note Packaging-only changes should be tagged with a release number of the format v<version>-<release> , e.g. v3.4.23-2 Advanced features for Git and GitHub repos \u00b6 The following features make software development in Git and GitHub more convenient: Support for RPM release numbers in Git tags: If the tag for the software contains a dash, as in v1.12.2-1 , it is assumed that the text after the dash is the RPM release instead of the software version. The RPM release is not included in the tarball. That is, the project osg-build with the tag v1.12.2-1 will result in a tarball named osg-build-1.12.1.tar.gz , not osg-build-1.12.1-1.tar.gz . Can specify tarball name in the .source file: The new tarball attribute allows you to specify the name of the tarball and directory that the repo contents will be put into. The syntax is tarball=<NAME>.tar.gz . The extension must be .tar.gz , no other archive formats are supported. The directory inside the tarball will then be <NAME>/ . Can ignore hash mismatch (scratch and local builds only): For local builds (rpmbuild and mock tasks) and Koji scratch builds, a hash mismatch will result in a warning. Non-scratch Koji builds will still consider it an error. Can use a branch as the tag: The tag attribute can refer to a branch instead of a tag, e.g. tag=master . Combining the last two features can really speed up package development. For example, you can use this to make scratch builds of the current master: type=github repo=<OWNER>/<PROJECT> tarball=<PROJECT>-<VERSION>.tar.gz tag=master hash=0 This might also be useful as part of a continuous integration scheme (e.g. Travis-CI). osg \u00b6 The osg directory contains files that are owned by the OSG Software Team and that are used to create the final, released source package. It may contain a variety of development files: An RPM .spec file, which overrides any spec file from a referenced source Patch ( .patch ) or replacement files, which override any same-named file from the top-level directory of a referenced source Other files, which must be explicitly placed into the package by the spec file Generated directories \u00b6 The following directories may be generated by our build tool, OSG-Build . They are not under revision control. _upstream_srpm_contents/ expanded contents of a cached upstream source package _upstream_tarball_contents/ expanded contents of all cached upstream source tarballs _final_srpm_contents/ the final contents of the OSG source package _build_results/ OSG source and binary packages resulting from a build _quilt/ expanded, patched contents of the upstream sources, as generated by the quilt tool _upstream_srpm_contents \u00b6 The _upstream_srpm_contents directory contains the files that are part of the upstream source package. It is a volatile record of the upstream source for developer use. _upstream_tarball_contents \u00b6 The _upstream_tarball_contents directory contains the files that are part of the upstream source tarballs. It is generated by the package build tool if the --full-extract option is passed. It is not used for anything by the build tool, but meant as a convenience to allow the developer to look inside the upstream sources (for making patches, etc.). _final_srpm_contents \u00b6 The _final_srpm_contents directory contains the final files that are part of the released source package. It is a volatile record of a build for developer use. _build_results \u00b6 The _build_results directory contains the source and binary RPMs that are produced by a local build. It is a volatile record of a build for developer use. _quilt \u00b6 The _quilt directory contains the unpacked sources after they have been patched using the quilt utility. This allows easier patch development. Packaging Organization Examples \u00b6 Use Case 1: Packaging an Upstream Source Tarball \u00b6 When the OSG Software Team packages an upstream source tarball, for which there is no existing package, the source tarball is referenced with a .source file and we provide a spec file and, if necessary, patches. For example, RSV is provided as a source tarball only. Its package directory contains: rsv/ osg/ rsv.spec upstream/ developer.tarball.source Use Case 2: Passing Through a Source RPM \u00b6 When the OSG Software Team simply provides a copy of an existing source RPM, it is referenced with a .source file and that is it. For example, we do not modify the globus-common source RPM from EPEL. Its package directory contains: globus-common/ upstream/ epel.srpm.source Use Case 3: Modifying a Source RPM \u00b6 When the OSG Software Team modifies an existing source RPM, it is referenced with a .source file and then all changes to the upstream source are contained in the osg directory. For example, we use this mechanism for the globus-ftp-client package, originally obtained from EPEL. Its package directory contains: globus-ftp-client/ osg/ globus-ftp-client.spec 1853-ssh-bin.patch upstream/ epel.srpm.source Build Process \u00b6 All necessary information to create the package will be committed to the VDT source code repository (see below) The OSG build tools will take those files, create a source RPM, and submit it to our Koji build system Developers may use rpmbuild and mock for faster iterative development before submitting the package to Koji. osg-build may be used as a wrapper script around rpmbuild and mock . OSG Software Repository \u00b6 OSG Operations maintains the Yum repositories that contain our source and binary RPMs at https://repo.opensciencegrid.org/osg/ and are mirrored at other institutions as well. Release Levels \u00b6 Every package is classified into a release level based on the amount of testing it has undergone and our confidence in its stability. When a package is first built, it goes into the lowest level ( osg-development ). The members of the OSG Software and Release teams may promote packages through the release levels, as per our Release Policy page . Packaging Conventions \u00b6 In addition to adhering to the Fedora Packaging Guidelines (FPG), we have a few rules and guidelines of our own: When we pass-through an RPM and make any changes to it (so it has an updated package number), we construct the version-release as follows: The version of the original RPM remains unchanged The release is composed of three parts: ORIGINALRELEASE.OSGRELEASE We add a distro tag based on the OSG major version and OS major version, e.g. \"osg33.el6\". (Use %{?dist} in the Release field) Example: We copy package foobar-3.0.5-1 from somewhere. We need to patch it, so the full name-version-release (NVR) for OSG 3.3 on EL 6 becomes foobar-3.0.5-1.1.osg33.el6 Note that we added \".1.osg33.el6\" to the release number. If we update our packaging (but still base on foobar-3.0.5-1), we change to \".2.osg33.el6\". In the spec file, this would look like: Release : 1.2 %{?dist} Packaging for Multiple Distro Versions \u00b6 Conditionalizing spec files \u00b6 Some packages may need different build behavior between major versions of the OS; RPM conditional statements will be used to handle this. The following macros are defined: Name Value (EL6) Value (EL7) %rhel 6 7 %el6 1 undefined or 0 %el7 undefined or 0 1 Here's how to use them: %if 0%{?el6} # this code will be executed on EL 6 only %endif %if 0%{?el7} # this code will be executed on EL 7 only %endif %if 0%{?rhel} >= 7 # this code will be executed on EL 7 and newer %endif (There does not seem to be an %elseif ). The syntax %{?el6} expands to the value of the %el6 macro if it is defined, and to the empty string if not; the 0 is there to keep the condition from being empty in the %if statement if the macro is not defined. Renaming or Removing Packages \u00b6 Occasionally we want to cause a package to be removed on update, or replaced by a package with a different name. For the most part, the Fedora Packaging Guidelines page on renames shows how to do that. The exception is that we do not have the equivalent of a fedora-obsolete-packages package, so in order to force the removal of an entire package (not a subpackage), we have to dummy out the package instead -- see below. (This should be a rare situation.) Note After doing a rename or a removal, you must update all the packages and subpackages that require the package being removed or renamed, and change or remove the requirements as appropriate. To find packages that require the old package at run time, set up a host with the OSG repos and install the yum-utils RPM. Then, run: $ repoquery --plugins --whatrequires $OLDPACKAGE To find packages that require the old package at build time, install osg-build , and do this from a checkout of the OSG repos: $ osg-build prebuild * $ for srpm in */_final_srpm_contents/*.src.rpm ; do \\ echo \"***** $srpm *****\"; \\ rpm -q --requires -p $srpm | grep -w $OLDPACKAGE; \\ done (examine the output to avoid false matches) Note Carefully test these changes, including places where the old package may be brought in indirectly. Dummying out a package \u00b6 In order to forcibly remove an entire package with no replacement, you have to replace the package with one that does nothing. This is because there is no package that will \"obsolete\" the old package. Do the following for the main package and any subpackages it may have: Change the Summary to \"Dummy package\" Change the %description to: This is an empty package created for $REASONS It may safely be removed. Where $REASONS is a description of why you need this dummy package Remove all Requires and Obsoletes lines Do not remove Provides lines Remove %pre and %post scriptlets Unless there is a good reason not to, remove %preun and %postun scriptlets Empty the %files section","title":"RPM Development Guide"},{"location":"software/rpm-development-guide/#rpm-development-guide","text":"This page documents technical guidelines and details about RPM development for the OSG Software Stack. The procedures, conventions, and policies defined within are used by the OSG Software Team, and are recommended to all external developers who wish to contribute to the OSG Software Stack.","title":"RPM Development Guide"},{"location":"software/rpm-development-guide/#principles","text":"The principles below guide the design and implementation of the technical details that follow. Packages should adhere to community standards (e.g., Fedora Packaging Guidelines when possible, and significant deviations must be documented Every released package must be reproducible from data stored in our system Source code for software should be clearly separable from the packaging of that software Upstream source files (which should not be modified) should be clearly separated from files owned by the OSG Software Team Building source and binary packages from our system should be easy and efficient External developers should have a clear and effective system for developing and contributing packages We should use standard tools from relevant packaging and development communities when appropriate","title":"Principles"},{"location":"software/rpm-development-guide/#contributing-packages","text":"We encourage all interested parties to contribute to OSG Software, and all the infrastructure described on this page should be friendly to external contributors. To participate in the packaging community: You must subscribe to the software-discuss@osg-htc.org email list. To create and edit packages: Obtain access to VDT SVN . To upload new source tarballs: You must have a cs.wisc.edu account with write access to the VDT source tarball directory. Email the osg-software list and request permission. To build using the OSG's Koji build system: You must have a valid personal certificate and a Koji account. To obtain the Koji account, email the osg-software list with your cert's DN and request permission.","title":"Contributing Packages"},{"location":"software/rpm-development-guide/#development-infrastructure","text":"This section documents most of what a developer needs to know about our RPM infrastructure: Upstream Source Cache \u2014 a filesystem scheme for caching upstream source files Revision Control System \u2014 where to get and store development files, and how they are organized Build System \u2014 how to build packages from the revision control system Yum Repository \u2014 the location and organization of our Yum repository, and how to promote packages through it","title":"Development Infrastructure"},{"location":"software/rpm-development-guide/#upstream-source-cache","text":"One of our principles (every released package must be reproducible from data stored in our system) creates a potential issue: If we keep all historical source data, especially upstream files like source tarballs and source RPMs, in our revision control system, we may face large checkouts and consequently long checkout and update times. Our solution is to cache all upstream source files in a separate filesystem area, retaining historical files indefinitely. To avoid tainting upstream files, our policy is to leave them unmodified after download.","title":"Upstream Source Cache"},{"location":"software/rpm-development-guide/#locating-files-in-the-cache","text":"Upstream source files are stored in the filesystem as follows: /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> where: Symbol Definition Example <PACKAGE> Upstream name of the source package, or some widely accepted form thereof ndt <VERSION> Upstream version string used to identify the release 3.6.4 <FILE> Upstream filename itself ndt-3.6.4.tar.gz The authoritative cache is the VDT webserver, which is fully backed up. The Koji build system uses this cache. Upstream source files are referenced from within the revision control system; see below for details. You will need to know the SHA1 checksum of any files you use from the cache. Do get it, do: $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE>","title":"Locating Files in the Cache"},{"location":"software/rpm-development-guide/#contributing-upstream-files","text":"You must make sure that any new upstream source files are cached on the VDT webserver before building the package via Koji. You have two options: If you have access to a UW\u2013Madison CSL machine, you can scp the source files directly into the AFS locations using that machine If you do not have such access, write to the osg-software list to find someone who will post the files for you","title":"Contributing Upstream Files"},{"location":"software/rpm-development-guide/#gitgithub-hosted-upstream-files","text":"It is also possible to pull sources and spec files from remote Git or GitHub repos instead of our source cache. See the upstream dir info for more information.","title":"Git/GitHub Hosted Upstream Files"},{"location":"software/rpm-development-guide/#revision-control-system","text":"All packages that the OSG Software Team releases are checked into our Subversion repository.","title":"Revision Control System"},{"location":"software/rpm-development-guide/#subversion-access","text":"Our Subversion repository is located at: https://vdt.cs.wisc.edu/svn Procedure for offsite users obtaining access to Subversion Or, from a UW\u2013Madison Computer Sciences machine: file:///p/condor/workspaces/vdt/svn The current SVN directory housing our native package work is $SVN/native/redhat (where $SVN is one of the ways of accessing our SVN repository above). For example, to check out the current package repository via HTTPS, do: [you@host]$ svn co https://vdt.cs.wisc.edu/svn/native/redhat","title":"Subversion Access"},{"location":"software/rpm-development-guide/#osg-owned-software","text":"OSG-owned software goes into GitHub under the opensciencegrid organization. Files are organized as the developer sees fit. It is strongly recommended that each software package include a top-level Makefile with at least the following targets: Symbol Purpose install Install the software into final FHS locations rooted at DESTDIR dist Create a distribution source tarball (in the current section directory) for a release upstream Install the distribution source tarball into the upstream source cache","title":"OSG-Owned Software"},{"location":"software/rpm-development-guide/#packaging-top-level-directory-organization","text":"The top levels of our Subversion directory hierarchy for packaging are as follows: native/redhat/<SECTION>/<PACKAGE> where: Symbol Definition Example <SECTION> Development section Standard Subversion sections like trunk and branches/* <PACKAGE> Our standardized name for a source package ndt","title":"Packaging Top-Level Directory Organization"},{"location":"software/rpm-development-guide/#package-directory-organization","text":"Within a source package directory, the following files (detailed in separate sections below) may exist: README text file package notes, by and for developers upstream/ directory references to the upstream source cache and other kinds of upstream files osg/ directory overrides and patches of upstream files, plus new files, which contribute to the final OSG source package","title":"Package Directory Organization"},{"location":"software/rpm-development-guide/#readme","text":"This is a free-form text file for developers to leave notes about the package. Please document anything interesting about how you procured the upstream source, the reasons for the modifications you made, or anything else people might need to know in order to maintain the package in the future. Please document the why , not just the what .","title":"README"},{"location":"software/rpm-development-guide/#upstream","text":"Within the per-package directories of the revision control system, there must be a way to refer to cached files. This is done with small text files that (a) are named consistently, and (b) contain the location of the referenced file as its contents. A reference file is named: <DESCRIPTION>.<TYPE>.source where: Symbol Definition Example <DESCRIPTION> Descriptive label of the source of the referenced file developer , epel , emi <TYPE> Type of referenced file tarball , srpm and contain references to cached files, Git repos, and comments. which start with # and continue until the end of the line. It is useful to add the source of the upstream file into a comment.","title":"upstream"},{"location":"software/rpm-development-guide/#cached-files","text":"To reference files in the upstream source cache, use the upstream source cache path defined above, without the prefix component, followed by the sha1sum of the file: <PACKAGE>/<VERSION>/<FILE> sha1sum=<SHA1SUM> Obtain the sha1sum by running the sha1sum command with the source file as an argument, i.e. $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> Note This feature requires OSG-Build 1.14.0 or later. Example The reference file for globus-common 's source tarball is named epel.srpm.source and contains: globus-common/16.4/globus-common-16.4-1.el6.src.rpm sha1sum=134478c56c2437c335c20636831f794b66290bec # Downloaded from 'http://dl.fedoraproject.org/pub/epel/6/SRPMS/globus-common-16.4-1.el6.src.rpm'","title":"Cached files"},{"location":"software/rpm-development-guide/#github-repos","text":"Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note See also advanced features for Git and GitHub repos . To reference tags in GitHub repos, use the following syntax (all on one line): type=github repo=<OWNER>/<PROJECT> tag=<TAG> hash=<HASH> where: Symbol Definition Example <OWNER> Owner of the GitHub repo opensciencegrid <PROJECT> Name of the project osg-build <TAG> Git tag to use v1.12.2 <HASH> Full 40-char Git hash of the tag cff50ffe812282552cedae81f3809d3cf7087a3e Note The tarball will be called <PROJECT>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example You can refer to the 1.12.2 release of osg-build with this line: type=github repo=opensciencegrid/osg-build tag=v1.12.2 hash=cff50ffe812282552cedae81f3809d3cf7087a3e This results in a tarball named osg-build-1.12.2.tar.gz . In addition, if the repository contains a file called rpm/<PROJECT>.spec , it will be used as the spec file for the build (unless overridden in the osg directory).","title":"GitHub repos"},{"location":"software/rpm-development-guide/#git-repos","text":"Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note You can use a shorter syntax for GitHub repos -- see above. See also advanced features for Git and GitHub repos . To reference tags in Git repos, use the following syntax (all on one line): type=git url=<URL> name=<NAME> tag=<TAG> hash=<HASH> where: Symbol Definition Example <URL> Location of the Git repo https://github.com/opensciencegrid/osg-build.git <NAME> Name of the software (optional) osg-build <TAG> Git tag to use v1.11.2 <HASH> Full 40-char Git hash of the tag 5bcf48c442d21b1e8c93a468d884f84122f7cc9e Note <NAME> is optional; if not present, OSG-Build will use the last component of the URL, without the .git suffix. The tarball will be called <NAME>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example The reference file for osg-build 's repo is named osg.github.source and contains: type=git url=https://github.com/opensciencegrid/osg-build.git name=osg-build tag=v1.11.2 hash=5bcf48c442d21b1e8c93a468d884f84122f7cc9e This results in a tarball named osg-build-1.11.2.tar.gz . In addition, if the repository contains a file called rpm/<NAME>.spec , it will be used as the spec file for the build (unless overridden in the osg directory).","title":"Git repos"},{"location":"software/rpm-development-guide/#typical-workflow-when-building-out-of-github-repos","text":"Fork the repository of the package that you would like to build Create a new branch in your fork Make, commit, and push changes to your new branch In your fork, tag the commit that you would like to build In the upstream/osg.github.source , change the repo to point at your fork and tag Attempt a scratch build If the build fails, remove the tag and repeat steps 3-6 Submit a PR to merge changes upstream Tag the final version on the upstream fork Build the version that will go through the normal software cycle Note Packaging-only changes should be tagged with a release number of the format v<version>-<release> , e.g. v3.4.23-2","title":"Typical workflow when building out of GitHub repos"},{"location":"software/rpm-development-guide/#advanced-features-for-git-and-github-repos","text":"The following features make software development in Git and GitHub more convenient: Support for RPM release numbers in Git tags: If the tag for the software contains a dash, as in v1.12.2-1 , it is assumed that the text after the dash is the RPM release instead of the software version. The RPM release is not included in the tarball. That is, the project osg-build with the tag v1.12.2-1 will result in a tarball named osg-build-1.12.1.tar.gz , not osg-build-1.12.1-1.tar.gz . Can specify tarball name in the .source file: The new tarball attribute allows you to specify the name of the tarball and directory that the repo contents will be put into. The syntax is tarball=<NAME>.tar.gz . The extension must be .tar.gz , no other archive formats are supported. The directory inside the tarball will then be <NAME>/ . Can ignore hash mismatch (scratch and local builds only): For local builds (rpmbuild and mock tasks) and Koji scratch builds, a hash mismatch will result in a warning. Non-scratch Koji builds will still consider it an error. Can use a branch as the tag: The tag attribute can refer to a branch instead of a tag, e.g. tag=master . Combining the last two features can really speed up package development. For example, you can use this to make scratch builds of the current master: type=github repo=<OWNER>/<PROJECT> tarball=<PROJECT>-<VERSION>.tar.gz tag=master hash=0 This might also be useful as part of a continuous integration scheme (e.g. Travis-CI).","title":"Advanced features for Git and GitHub repos"},{"location":"software/rpm-development-guide/#osg","text":"The osg directory contains files that are owned by the OSG Software Team and that are used to create the final, released source package. It may contain a variety of development files: An RPM .spec file, which overrides any spec file from a referenced source Patch ( .patch ) or replacement files, which override any same-named file from the top-level directory of a referenced source Other files, which must be explicitly placed into the package by the spec file","title":"osg"},{"location":"software/rpm-development-guide/#generated-directories","text":"The following directories may be generated by our build tool, OSG-Build . They are not under revision control. _upstream_srpm_contents/ expanded contents of a cached upstream source package _upstream_tarball_contents/ expanded contents of all cached upstream source tarballs _final_srpm_contents/ the final contents of the OSG source package _build_results/ OSG source and binary packages resulting from a build _quilt/ expanded, patched contents of the upstream sources, as generated by the quilt tool","title":"Generated directories"},{"location":"software/rpm-development-guide/#_upstream_srpm_contents","text":"The _upstream_srpm_contents directory contains the files that are part of the upstream source package. It is a volatile record of the upstream source for developer use.","title":"_upstream_srpm_contents"},{"location":"software/rpm-development-guide/#_upstream_tarball_contents","text":"The _upstream_tarball_contents directory contains the files that are part of the upstream source tarballs. It is generated by the package build tool if the --full-extract option is passed. It is not used for anything by the build tool, but meant as a convenience to allow the developer to look inside the upstream sources (for making patches, etc.).","title":"_upstream_tarball_contents"},{"location":"software/rpm-development-guide/#_final_srpm_contents","text":"The _final_srpm_contents directory contains the final files that are part of the released source package. It is a volatile record of a build for developer use.","title":"_final_srpm_contents"},{"location":"software/rpm-development-guide/#_build_results","text":"The _build_results directory contains the source and binary RPMs that are produced by a local build. It is a volatile record of a build for developer use.","title":"_build_results"},{"location":"software/rpm-development-guide/#_quilt","text":"The _quilt directory contains the unpacked sources after they have been patched using the quilt utility. This allows easier patch development.","title":"_quilt"},{"location":"software/rpm-development-guide/#packaging-organization-examples","text":"","title":"Packaging Organization Examples"},{"location":"software/rpm-development-guide/#use-case-1-packaging-an-upstream-source-tarball","text":"When the OSG Software Team packages an upstream source tarball, for which there is no existing package, the source tarball is referenced with a .source file and we provide a spec file and, if necessary, patches. For example, RSV is provided as a source tarball only. Its package directory contains: rsv/ osg/ rsv.spec upstream/ developer.tarball.source","title":"Use Case 1: Packaging an Upstream Source Tarball"},{"location":"software/rpm-development-guide/#use-case-2-passing-through-a-source-rpm","text":"When the OSG Software Team simply provides a copy of an existing source RPM, it is referenced with a .source file and that is it. For example, we do not modify the globus-common source RPM from EPEL. Its package directory contains: globus-common/ upstream/ epel.srpm.source","title":"Use Case 2: Passing Through a Source RPM"},{"location":"software/rpm-development-guide/#use-case-3-modifying-a-source-rpm","text":"When the OSG Software Team modifies an existing source RPM, it is referenced with a .source file and then all changes to the upstream source are contained in the osg directory. For example, we use this mechanism for the globus-ftp-client package, originally obtained from EPEL. Its package directory contains: globus-ftp-client/ osg/ globus-ftp-client.spec 1853-ssh-bin.patch upstream/ epel.srpm.source","title":"Use Case 3: Modifying a Source RPM"},{"location":"software/rpm-development-guide/#build-process","text":"All necessary information to create the package will be committed to the VDT source code repository (see below) The OSG build tools will take those files, create a source RPM, and submit it to our Koji build system Developers may use rpmbuild and mock for faster iterative development before submitting the package to Koji. osg-build may be used as a wrapper script around rpmbuild and mock .","title":"Build Process"},{"location":"software/rpm-development-guide/#osg-software-repository","text":"OSG Operations maintains the Yum repositories that contain our source and binary RPMs at https://repo.opensciencegrid.org/osg/ and are mirrored at other institutions as well.","title":"OSG Software Repository"},{"location":"software/rpm-development-guide/#release-levels","text":"Every package is classified into a release level based on the amount of testing it has undergone and our confidence in its stability. When a package is first built, it goes into the lowest level ( osg-development ). The members of the OSG Software and Release teams may promote packages through the release levels, as per our Release Policy page .","title":"Release Levels"},{"location":"software/rpm-development-guide/#packaging-conventions","text":"In addition to adhering to the Fedora Packaging Guidelines (FPG), we have a few rules and guidelines of our own: When we pass-through an RPM and make any changes to it (so it has an updated package number), we construct the version-release as follows: The version of the original RPM remains unchanged The release is composed of three parts: ORIGINALRELEASE.OSGRELEASE We add a distro tag based on the OSG major version and OS major version, e.g. \"osg33.el6\". (Use %{?dist} in the Release field) Example: We copy package foobar-3.0.5-1 from somewhere. We need to patch it, so the full name-version-release (NVR) for OSG 3.3 on EL 6 becomes foobar-3.0.5-1.1.osg33.el6 Note that we added \".1.osg33.el6\" to the release number. If we update our packaging (but still base on foobar-3.0.5-1), we change to \".2.osg33.el6\". In the spec file, this would look like: Release : 1.2 %{?dist}","title":"Packaging Conventions"},{"location":"software/rpm-development-guide/#packaging-for-multiple-distro-versions","text":"","title":"Packaging for Multiple Distro Versions"},{"location":"software/rpm-development-guide/#conditionalizing-spec-files","text":"Some packages may need different build behavior between major versions of the OS; RPM conditional statements will be used to handle this. The following macros are defined: Name Value (EL6) Value (EL7) %rhel 6 7 %el6 1 undefined or 0 %el7 undefined or 0 1 Here's how to use them: %if 0%{?el6} # this code will be executed on EL 6 only %endif %if 0%{?el7} # this code will be executed on EL 7 only %endif %if 0%{?rhel} >= 7 # this code will be executed on EL 7 and newer %endif (There does not seem to be an %elseif ). The syntax %{?el6} expands to the value of the %el6 macro if it is defined, and to the empty string if not; the 0 is there to keep the condition from being empty in the %if statement if the macro is not defined.","title":"Conditionalizing spec files"},{"location":"software/rpm-development-guide/#renaming-or-removing-packages","text":"Occasionally we want to cause a package to be removed on update, or replaced by a package with a different name. For the most part, the Fedora Packaging Guidelines page on renames shows how to do that. The exception is that we do not have the equivalent of a fedora-obsolete-packages package, so in order to force the removal of an entire package (not a subpackage), we have to dummy out the package instead -- see below. (This should be a rare situation.) Note After doing a rename or a removal, you must update all the packages and subpackages that require the package being removed or renamed, and change or remove the requirements as appropriate. To find packages that require the old package at run time, set up a host with the OSG repos and install the yum-utils RPM. Then, run: $ repoquery --plugins --whatrequires $OLDPACKAGE To find packages that require the old package at build time, install osg-build , and do this from a checkout of the OSG repos: $ osg-build prebuild * $ for srpm in */_final_srpm_contents/*.src.rpm ; do \\ echo \"***** $srpm *****\"; \\ rpm -q --requires -p $srpm | grep -w $OLDPACKAGE; \\ done (examine the output to avoid false matches) Note Carefully test these changes, including places where the old package may be brought in indirectly.","title":"Renaming or Removing Packages"},{"location":"software/rpm-development-guide/#dummying-out-a-package","text":"In order to forcibly remove an entire package with no replacement, you have to replace the package with one that does nothing. This is because there is no package that will \"obsolete\" the old package. Do the following for the main package and any subpackages it may have: Change the Summary to \"Dummy package\" Change the %description to: This is an empty package created for $REASONS It may safely be removed. Where $REASONS is a description of why you need this dummy package Remove all Requires and Obsoletes lines Do not remove Provides lines Remove %pre and %post scriptlets Unless there is a good reason not to, remove %preun and %postun scriptlets Empty the %files section","title":"Dummying out a package"},{"location":"software/upcoming-to-main/","text":"Promoting Packages from Upcoming to Main \u00b6 Sometimes we move packages from Upcoming to the Main repositories in the middle of a release series. Once the Release Manager has given tentative approval for such a move: If needed, move the software from upcoming to trunk and release using the usual process: Merge changes to the package in SVN from branches/upcoming to trunk. Build the package from trunk. Follow the normal process to prepare a build for release (including development testing, promotion, etc.). On release day, when the package has been released in the Main production repository, clean up the package from the upcoming repos: Untag from all upcoming repos the version of the package corresponding to the version that was released in main. (Do NOT untag from the osg-upcoming-elN-release-X.Y.Z tags) Also, untag all equal or lesser NVRs (minus the dist tag) from all upcoming repos. If you do not have the privileges to untag from upcoming-release, someone on the Release Team can help. (These steps are necessary to make sure Koji builds can't mistakenly use an older build from the upcoming repos). Unless there's a newer build in branches/upcoming than what was released, remove the package directory from branches/upcoming.","title":"Upcoming to Main"},{"location":"software/upcoming-to-main/#promoting-packages-from-upcoming-to-main","text":"Sometimes we move packages from Upcoming to the Main repositories in the middle of a release series. Once the Release Manager has given tentative approval for such a move: If needed, move the software from upcoming to trunk and release using the usual process: Merge changes to the package in SVN from branches/upcoming to trunk. Build the package from trunk. Follow the normal process to prepare a build for release (including development testing, promotion, etc.). On release day, when the package has been released in the Main production repository, clean up the package from the upcoming repos: Untag from all upcoming repos the version of the package corresponding to the version that was released in main. (Do NOT untag from the osg-upcoming-elN-release-X.Y.Z tags) Also, untag all equal or lesser NVRs (minus the dist tag) from all upcoming repos. If you do not have the privileges to untag from upcoming-release, someone on the Release Team can help. (These steps are necessary to make sure Koji builds can't mistakenly use an older build from the upcoming repos). Unless there's a newer build in branches/upcoming than what was released, remove the package directory from branches/upcoming.","title":"Promoting Packages from Upcoming to Main"},{"location":"software/user-certs/","text":"User Certificates \u00b6 Note This document describes how to get and set up a personal certificate (also called a grid user certificate). For instructions on how to get host certificates, see the Host Certificates document . Getting a User Certificate \u00b6 This section describes how to get and set up a personal (user) certificate. A user certificate is a type of SSL certificate -- the same technology used for identifying websites when using HTTPS -- but identifying a human instead of a host. This is used to access some grid resources, such as: OSG Topology (for viewing private contact information) The osg-notify tool for sending mass emails The GGUS ticketing system The Koji build system for the OSG Software Stack User certs may also be useful for debugging storage access (such as XRootD). Currently, you can get a user certificate from CILogon. Know your responsibilities \u00b6 If your account or user certificate is compromised, you must notify the issuer of your certificate. In addition, you should update your certificate and revoke the old certificate if any of the information in the certificate (such as name or email address) change. For the CILogon RA send email to ca@cilogon.org . Additional responsibilities required by the CILogon CA are given on their page . Getting a certificate from CILogon \u00b6 You will have to obtain your user certificate using the CILogon web UI . Follow the steps below to get an user certificate: Open the CILogon page, https://cilogon.org , in your browser of choice First, either search for your institution and select it or scroll through list and do the same. . Warning Do not use Google, GitHub, or ORCID as providers since they are not widely supported in the OSG. If your institution is not on the list, please contact your institution's IT support to see if they can support CILogon. Click the Log On button and enter your institutional credentials if prompted. After successfully entering your credentials, click on the \"Create Password-Protected Certificate\" link Enter a password that is at least 12 characters long and then click on the Get New Certificate button. Click the Download Your Certificate button to download your certificate in .p12 format. The certificate will be protected using the password you entered in the previous step. Certificate formats \u00b6 Your user certificate can be stored in a few different formats: CILogon will give you a certificate in the PKCS12 format (file extension .p12 ). The PKCS12 format stores the certificate and private key in a single file along with an optional certificate chain. This is the file format that can be loaded into your browser for accessing Topology, GGUS, or the Koji web interace with. Most command line tools use the PEM format (file extension .pem ). The PEM format stores the public certificate in one file, and the private key in another file. To convert a PKCS12 file to PEM files, do the following: First, extract your user certificate from your PKCS12 file by running the following command. You'll be prompted for the password you used to create the certificate. The invocation assumes that the PKCS12 file is called usercred.p12 . After running, the PEM certificate will be written to usercert.pem . user@host $ openssl pkcs12 -in usercred.p12 -out usercert.pem -nodes -clcerts -nokeys Enter Import Password: MAC verified OK Second, extract the private key by running the following command. You'll be prompted for two different passwords. The first prompt will be for the password that you used to create the certificate. The second prompt will be for the password that will encrypt the PEM certificate that will be created. As before, the invocation assumes that your PKCS12 certificate is located in usercred.p12 . After running, the PEM certificate with your private key will be written to userkey.pem . user@host $ openssl pkcs12 -in usercred.p12 -out userkey.pem -nocerts Enter Import Password: MAC verified OK Enter PEM pass phrase: Verifying - Enter PEM pass phrase: Using Your User Certificate \u00b6 The standard location to place user certificates is in the .globus subdirectory of your home directory: user@host $ mkdir -p ~/.globus user@host $ cp userkey.pem ~/.globus/ user@host $ cp usercert.pem ~/.globus/ user@host $ cp usercred.p12 ~/.globus/ user@host $ chmod go-rwx ~/.globus/userkey.pem ~/.globus/usercred.p12 In order to find the Distinguished Name (DN), issuer and lifetime of a certificate: user@host $ openssl x509 -in ~/.globus/usercert.pem -noout -subject -issuer -enddate To generate a proxy use the command voms-proxy-init . user@host $ voms-proxy-init Revoking Your User Certificate \u00b6 If the security of your certificate or private key has been compromised, you have a responsibility to revoke the certificate. In addition, if your name or email address changes, you must revoke your certificate and get a new one with the correct information. If you have a CILogon issued certificate, contact ca@cilogon.org in order revoke your certificate. If you received a certificate from another CA, please contact the CA to initiate a certificate revocation.","title":"User Certificates"},{"location":"software/user-certs/#user-certificates","text":"Note This document describes how to get and set up a personal certificate (also called a grid user certificate). For instructions on how to get host certificates, see the Host Certificates document .","title":"User Certificates"},{"location":"software/user-certs/#getting-a-user-certificate","text":"This section describes how to get and set up a personal (user) certificate. A user certificate is a type of SSL certificate -- the same technology used for identifying websites when using HTTPS -- but identifying a human instead of a host. This is used to access some grid resources, such as: OSG Topology (for viewing private contact information) The osg-notify tool for sending mass emails The GGUS ticketing system The Koji build system for the OSG Software Stack User certs may also be useful for debugging storage access (such as XRootD). Currently, you can get a user certificate from CILogon.","title":"Getting a User Certificate"},{"location":"software/user-certs/#know-your-responsibilities","text":"If your account or user certificate is compromised, you must notify the issuer of your certificate. In addition, you should update your certificate and revoke the old certificate if any of the information in the certificate (such as name or email address) change. For the CILogon RA send email to ca@cilogon.org . Additional responsibilities required by the CILogon CA are given on their page .","title":"Know your responsibilities"},{"location":"software/user-certs/#getting-a-certificate-from-cilogon","text":"You will have to obtain your user certificate using the CILogon web UI . Follow the steps below to get an user certificate: Open the CILogon page, https://cilogon.org , in your browser of choice First, either search for your institution and select it or scroll through list and do the same. . Warning Do not use Google, GitHub, or ORCID as providers since they are not widely supported in the OSG. If your institution is not on the list, please contact your institution's IT support to see if they can support CILogon. Click the Log On button and enter your institutional credentials if prompted. After successfully entering your credentials, click on the \"Create Password-Protected Certificate\" link Enter a password that is at least 12 characters long and then click on the Get New Certificate button. Click the Download Your Certificate button to download your certificate in .p12 format. The certificate will be protected using the password you entered in the previous step.","title":"Getting a certificate from CILogon"},{"location":"software/user-certs/#certificate-formats","text":"Your user certificate can be stored in a few different formats: CILogon will give you a certificate in the PKCS12 format (file extension .p12 ). The PKCS12 format stores the certificate and private key in a single file along with an optional certificate chain. This is the file format that can be loaded into your browser for accessing Topology, GGUS, or the Koji web interace with. Most command line tools use the PEM format (file extension .pem ). The PEM format stores the public certificate in one file, and the private key in another file. To convert a PKCS12 file to PEM files, do the following: First, extract your user certificate from your PKCS12 file by running the following command. You'll be prompted for the password you used to create the certificate. The invocation assumes that the PKCS12 file is called usercred.p12 . After running, the PEM certificate will be written to usercert.pem . user@host $ openssl pkcs12 -in usercred.p12 -out usercert.pem -nodes -clcerts -nokeys Enter Import Password: MAC verified OK Second, extract the private key by running the following command. You'll be prompted for two different passwords. The first prompt will be for the password that you used to create the certificate. The second prompt will be for the password that will encrypt the PEM certificate that will be created. As before, the invocation assumes that your PKCS12 certificate is located in usercred.p12 . After running, the PEM certificate with your private key will be written to userkey.pem . user@host $ openssl pkcs12 -in usercred.p12 -out userkey.pem -nocerts Enter Import Password: MAC verified OK Enter PEM pass phrase: Verifying - Enter PEM pass phrase:","title":"Certificate formats"},{"location":"software/user-certs/#using-your-user-certificate","text":"The standard location to place user certificates is in the .globus subdirectory of your home directory: user@host $ mkdir -p ~/.globus user@host $ cp userkey.pem ~/.globus/ user@host $ cp usercert.pem ~/.globus/ user@host $ cp usercred.p12 ~/.globus/ user@host $ chmod go-rwx ~/.globus/userkey.pem ~/.globus/usercred.p12 In order to find the Distinguished Name (DN), issuer and lifetime of a certificate: user@host $ openssl x509 -in ~/.globus/usercert.pem -noout -subject -issuer -enddate To generate a proxy use the command voms-proxy-init . user@host $ voms-proxy-init","title":"Using Your User Certificate"},{"location":"software/user-certs/#revoking-your-user-certificate","text":"If the security of your certificate or private key has been compromised, you have a responsibility to revoke the certificate. In addition, if your name or email address changes, you must revoke your certificate and get a new one with the correct information. If you have a CILogon issued certificate, contact ca@cilogon.org in order revoke your certificate. If you received a certificate from another CA, please contact the CA to initiate a certificate revocation.","title":"Revoking Your User Certificate"}]} \ No newline at end of file +{"config":{"lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"OSG Technology Area \u00b6 Welcome to the home page of the OSG Technology Team documentation area! If you are looking for site administrator documentation, please visit the OSG Documentation page . The Team \u00b6 Software and Release Technology Brian Lin (software manager) Brian Bockelman (manager) (15%) Mat Selmeci Derek Weitzel (50%) Matt Westphall (50%) Diego Davila (50%) Tim Theisen (release manager) (50%) Contact Us \u00b6 software-discuss@osg-htc.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org Meetings \u00b6 When: Every Tuesday, 9:30 a.m. (U.S. Central) Where: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Meeting note archives can be found directly in the GitHub repository .","title":"Home"},{"location":"#osg-technology-area","text":"Welcome to the home page of the OSG Technology Team documentation area! If you are looking for site administrator documentation, please visit the OSG Documentation page .","title":"OSG Technology Area"},{"location":"#the-team","text":"Software and Release Technology Brian Lin (software manager) Brian Bockelman (manager) (15%) Mat Selmeci Derek Weitzel (50%) Matt Westphall (50%) Diego Davila (50%) Tim Theisen (release manager) (50%)","title":"The Team"},{"location":"#contact-us","text":"software-discuss@osg-htc.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org","title":"Contact Us"},{"location":"#meetings","text":"When: Every Tuesday, 9:30 a.m. (U.S. Central) Where: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Meeting note archives can be found directly in the GitHub repository .","title":"Meetings"},{"location":"documentation/markdown-migration/","text":"Migrating to Markdown \u00b6 As part of the TWiki retirement (the read-only target date of Oct 1, 2017, with a shutdown date in 2018), we will need to convert the OSG Software and Release3 docs from TWiki syntax to Markdown . The following document outlines the conversion process and conventions. Choosing the git repository \u00b6 First you will need to choose which git repoository you will be working with: If you are converting a document from... Use this github repository... SoftwareTeam technology Release3 docs Once you've chosen the target repository for your document, move onto the next section and pick your conversion method. Automatic TWiki conversion \u00b6 Note If you are only archiving the documents, skip to this section . Choose one of the following methods for converting TWiki documents: Using our own docker conversion image (recommended) Directly using pandoc and mkdocs on your own machine Using docker \u00b6 The twiki-converter docker image can be used to preview the document tree via a mkdocs development server, archive TWiki documents, and convert documents to Markdown via pandoc . The image is available on osghost , otherwise, it is availble on dockerhub . user@host $ docker pull opensciencegrid/docker-twiki-converter Requirements \u00b6 To perform a document migration using docker, you will need the following tools and accounts: Fork and clone the repository that you chose in the above section A host with a running docker service sudo or membership in the docker group If you cannot install the above tools locally, they are available on osghost . Speak with Brian L for access. Preparing the git repository \u00b6 cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch <BRANCH NAME> master Replace <BRANCH NAME> with a name of your choice Change to the branch you just created user@host $ git checkout <BRANCH NAME> Replace <BRANCH NAME> with the name you chose in the step above Previewing the document tree \u00b6 When starting a twiki-converter docker container, it expects your local github repository to be mounted in /source so that any changes made to the repository are reflected in the mkdocs development server. To start a docker container based off of the twiki-converter docker image: Create a container from the image with the following command: user@host $ docker run -d -v <PATH TO LOCAL GITHUB REPO>:/source -p 8000 opensciencegrid/docker-twiki-converter Change <PATH TO LOCAL GITHUB REPO> for the directory where you have cloned the repo. The above command should return the container ID, which will be used in subsequent commands. Note If the docker container exits immediately, remove the -d option for details. If you see permission denied errors, you may need to disable SELinux or put it in permissive mode. To find the port that your development server is listening on, use the container ID (you should only need the first few chars of the ID) returned from the previous command: user@host $ docker port <CONTAINER ID> Change <CONTAINER ID> for the value returned by the execution of the previous command Access the development server in your browser via http://osghost.chtc.wisc.edu:<PORT> or localhost:<PORT> for containers run on osghost or locally, respectively. osghost has a restrictive firewall so if you have issues accessing your container from outside of the UW-Madison campus, use an SSH tunnel to map the osghost port to a local port. Converting documents \u00b6 The docker image contains a convenience script, convert-twiki for saving archives and converting them to Markdown. To run the script in a running container, run the following command: user@host $ docker exec <CONTAINER ID> convert-twiki <TWIKI URL> Where <CONTAINER ID> is the docker container ID and <TWIKI URL> is the link to the TWiki document that you want to convert, e.g. https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess . This will result in an archive of the twiki doc, archive/SoftwareDevelopmentProcess , in your local repo and a converted copy, SoftwareDevelopmentProcess.md , placed into the root of your local github repository. If the twiki url is for a specific revision of the document, a .rNN will be included in the output filenames. Warning If the above command does not complete quickly, it means that Pandoc is having an issue with a specific section of the document. See Troubleshooting conversion for next steps. To see the converted document in your browser: Rename, move the converted document into a folder in docs/ . Document file names should be lowercase, - delimited, and descriptive but concise, e.g. markdown-migration.md or cutting-release.md It's not important to get the name/location correct on the first try as this can be discussed in the pull request sudo chown the archived and converted documents to be owned by you Add the document to the pages: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Refresh the document tree in your browser Once you can view the converted document in your browser, move onto the next section Troubleshooting conversion \u00b6 Pandoc sometimes has issues converting documents and requires manual intervention by removing whichever section is causing issues in the conversion. Copy the archive of the document into the root of your git repository Kill the process in the docker container: user@host $ docker exec <CONTAINER ID> pkill -9 pandoc Where <CONTAINER ID> is the docker container ID Remove a section from the copy of the archive to find the problematic section (recommendation: use a binary search strategy) Run pandoc manually: user@host $ docker exec <CONTAINER ID> pandoc -f twiki -t markdown_github <ARCHIVE COPY> > <MARKDOWN FILE> Where <CONTAINER ID> is the docker container ID, <ARCHIVE COPY> is the the file you copied in the first step and <MARKDOWN FILE> is the resulting .md file Repeat steps 2-4 until you've narrowed down the problematic section Manually convert the offending section Conversion without Docker \u00b6 If you've already used the docker method , skip to the section about completing the conversion . Requirements \u00b6 This method requires the following: Fork and clone the repository that you chose in the above section pandoc (> 1.16) mkdocs MarkdownHighlight pygments Preparing the git repository \u00b6 cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch <BRANCH NAME> master Replace <BRANCH NAME> with a name of your choice 5. Change to the branch you just created user@host $ git checkout <BRANCH NAME> Replace <BRANCH NAME> with the name you chose in the step above Archiving the TWiki document \u00b6 Follow the instructions for archival then continue to the next section to convert the document with pandoc. Initial conversion with Pandoc \u00b6 Pandoc is a tool that's useful for automated conversion of markdown languages. Once installed (alternatively, run pandoc via docker ), run the following command to convert TWiki to Markdown: $ pandoc -f twiki -t markdown_github <TWIKI FILE> > <MARKDOWN FILE> Where <TWIKI FILE> is the path to initial document in raw TWiki and <MARKDOWN FILE> is the path to the resulting document in GitHub Markdown. Note If you don't see output from the above command quickly, it means that Pandoc is having an issue with a specific section of the document. Stop the command (or docker container), find and temporarily remove the offending section, convert the remainder of the document with Pandoc, and manually convert the offending section. Previewing your document(s) with Mkdocs \u00b6 Mkdocs has a development mode that can be used to preview documents as you work on them and is available via package manager or pip . Once installed , add your document(s) to the pages section of mkdocs.yml and launch the mkdocs server with the following command from the dir containing mkdocs.yml : $ PYTHONPATH = src/ mkdocs serve Access the server at http://127.0.0.1:8000 and navigate to the document you're working on. It's useful to open the original TWiki doc in an adjacent tab or window to quickly compare the two. Completing the conversion \u00b6 Manual review of the automatically converted documents are required since the automatic conversion process isn't perfect. This section contains a list of problems commonly encountered in automatically converted documents. Visit the style guide to ensure that the document meets all style guidelines. Archiving Documents \u00b6 If the document is slated for archival (check if it says \"yes\" in the \"archived\" column of the spreadsheet), just download the document to the archive folder of your local git repository: user@host $ cd technology/ user@host $ curl '<TWIKI URL>?raw=text' | iconv -f windows-1252 > archive/<TWIKI TITLE> Where <TWIKI URL> is the link to the TWiki document that you want to download and <TWIKI TITLE> is the name that will receive the archived file For example: user@host $ cd technology user@host $ curl 'https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/SHA2Compliance?raw=text' | iconv -f windows-1252 > archive/SHA2Compliance After downloading the document, continue onto the next section to walk through pull request submission. Submitting the pull request \u00b6 Stage the archived raw TWiki (as well as the converted Markdown document(s) and mkdocs.yml if you are converting the document): user@host $ git add mkdocs.yml archive/<TWIKI ARCHIVE> <PATH TO CONVERTED DOC> Where <TWIKI ARCHIVE> is the name of the archived document and <PATH TO CONVERTED DOC> is the path to the .md file Commit and push your changes to your GitHub repo: user@host $ git commit -m \"<COMMIT MSG>\" user@host $ git push origin <BRANCH NAME> Change <COMMIT MSG> for a meaningful text that describes the conversion done and <BRANCH NAME> with the name chosen in the 3rd step of the Preparing the git repository section Open your browser and navigate to your GitHub fork Submit a pull request containing with the following body: <LINK TO TWIKI DOCUMENT> - [ ] Enter date into \"Migrated\" column of google sheet An example of <LINK TO TWIKI DOCUMENT> is: https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess If you are migrating a document, also add this task: - [ ] Add migration header to TWiki document If you are archiving a document, add this task: - [ ] Move TWiki document to the trash See an example pull request here . After the pull request \u00b6 After the pull request is merged, replace the contents of TWiki document with the div if you're migrating the document, linking to the location of the migrated document: <div style=\"border: 1px solid black; margin: 1em 0; padding: 1em; background-color: #FFDDDD; font-weight: 600;\"> This document has been migrated to !GitHub (<LINK TO GITHUB DOCUMENT>). If you wish to see the old TWiki document, use the TWiki history below. Background: At the end of year (2017), the TWiki will be retired in favor of !GitHub. You can find the various TWiki webs and their new !GitHub locations listed below: * Release3: https://www.opensciencegrid.org/docs ([[https://github.com/opensciencegrid/docs/tree/master/archive][archive]]) * !SoftwareTeam: https://www.opensciencegrid.org/technology ([[https://github.com/opensciencegrid/technology/tree/master/archive][archive]]) </div> If you are archiving a document, move it to the trash instead. Once the document has been updated or trashed, add the date to the spreadsheet and go back to your pull request and mark your tasks as complete. For example, if you completed the migration of a document: - [X] Enter date into \"Migrated\" column of google sheet - [X] Add migration div to TWiki document Currently, we do not recommend changing backlinks (links on other twiki pages that refer to the Twiki page you are migrating) to point at the new GitHub URL. This is to provide a simple reminder to users that the migration will occur, and also is likely low priority regardless as all pages will eventually migrate to GitHub. This advice may change in the future as we gain experience with this transition. Reviewing pull requests \u00b6 To review pull requests, cd into the dir containing your git repository and check out the requester's branch, which the twiki-converter container should automatically notice. Here's an example checking out Brian's cut-sw-release branch of the technology repository: # Add the requester 's repo as a remote if you haven' t already user@host $ git remote add blin https://www.github.com/brianhlin/technology.git user@host $ git fetch --all user@host $ git checkout blin/cut-sw-release Refresh your browser and navigate to the document in the request.","title":"Migrating Documents to Markdown"},{"location":"documentation/markdown-migration/#migrating-to-markdown","text":"As part of the TWiki retirement (the read-only target date of Oct 1, 2017, with a shutdown date in 2018), we will need to convert the OSG Software and Release3 docs from TWiki syntax to Markdown . The following document outlines the conversion process and conventions.","title":"Migrating to Markdown"},{"location":"documentation/markdown-migration/#choosing-the-git-repository","text":"First you will need to choose which git repoository you will be working with: If you are converting a document from... Use this github repository... SoftwareTeam technology Release3 docs Once you've chosen the target repository for your document, move onto the next section and pick your conversion method.","title":"Choosing the git repository"},{"location":"documentation/markdown-migration/#automatic-twiki-conversion","text":"Note If you are only archiving the documents, skip to this section . Choose one of the following methods for converting TWiki documents: Using our own docker conversion image (recommended) Directly using pandoc and mkdocs on your own machine","title":"Automatic TWiki conversion"},{"location":"documentation/markdown-migration/#using-docker","text":"The twiki-converter docker image can be used to preview the document tree via a mkdocs development server, archive TWiki documents, and convert documents to Markdown via pandoc . The image is available on osghost , otherwise, it is availble on dockerhub . user@host $ docker pull opensciencegrid/docker-twiki-converter","title":"Using docker"},{"location":"documentation/markdown-migration/#requirements","text":"To perform a document migration using docker, you will need the following tools and accounts: Fork and clone the repository that you chose in the above section A host with a running docker service sudo or membership in the docker group If you cannot install the above tools locally, they are available on osghost . Speak with Brian L for access.","title":"Requirements"},{"location":"documentation/markdown-migration/#preparing-the-git-repository","text":"cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch <BRANCH NAME> master Replace <BRANCH NAME> with a name of your choice Change to the branch you just created user@host $ git checkout <BRANCH NAME> Replace <BRANCH NAME> with the name you chose in the step above","title":"Preparing the git repository"},{"location":"documentation/markdown-migration/#previewing-the-document-tree","text":"When starting a twiki-converter docker container, it expects your local github repository to be mounted in /source so that any changes made to the repository are reflected in the mkdocs development server. To start a docker container based off of the twiki-converter docker image: Create a container from the image with the following command: user@host $ docker run -d -v <PATH TO LOCAL GITHUB REPO>:/source -p 8000 opensciencegrid/docker-twiki-converter Change <PATH TO LOCAL GITHUB REPO> for the directory where you have cloned the repo. The above command should return the container ID, which will be used in subsequent commands. Note If the docker container exits immediately, remove the -d option for details. If you see permission denied errors, you may need to disable SELinux or put it in permissive mode. To find the port that your development server is listening on, use the container ID (you should only need the first few chars of the ID) returned from the previous command: user@host $ docker port <CONTAINER ID> Change <CONTAINER ID> for the value returned by the execution of the previous command Access the development server in your browser via http://osghost.chtc.wisc.edu:<PORT> or localhost:<PORT> for containers run on osghost or locally, respectively. osghost has a restrictive firewall so if you have issues accessing your container from outside of the UW-Madison campus, use an SSH tunnel to map the osghost port to a local port.","title":"Previewing the document tree"},{"location":"documentation/markdown-migration/#converting-documents","text":"The docker image contains a convenience script, convert-twiki for saving archives and converting them to Markdown. To run the script in a running container, run the following command: user@host $ docker exec <CONTAINER ID> convert-twiki <TWIKI URL> Where <CONTAINER ID> is the docker container ID and <TWIKI URL> is the link to the TWiki document that you want to convert, e.g. https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess . This will result in an archive of the twiki doc, archive/SoftwareDevelopmentProcess , in your local repo and a converted copy, SoftwareDevelopmentProcess.md , placed into the root of your local github repository. If the twiki url is for a specific revision of the document, a .rNN will be included in the output filenames. Warning If the above command does not complete quickly, it means that Pandoc is having an issue with a specific section of the document. See Troubleshooting conversion for next steps. To see the converted document in your browser: Rename, move the converted document into a folder in docs/ . Document file names should be lowercase, - delimited, and descriptive but concise, e.g. markdown-migration.md or cutting-release.md It's not important to get the name/location correct on the first try as this can be discussed in the pull request sudo chown the archived and converted documents to be owned by you Add the document to the pages: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Refresh the document tree in your browser Once you can view the converted document in your browser, move onto the next section","title":"Converting documents"},{"location":"documentation/markdown-migration/#troubleshooting-conversion","text":"Pandoc sometimes has issues converting documents and requires manual intervention by removing whichever section is causing issues in the conversion. Copy the archive of the document into the root of your git repository Kill the process in the docker container: user@host $ docker exec <CONTAINER ID> pkill -9 pandoc Where <CONTAINER ID> is the docker container ID Remove a section from the copy of the archive to find the problematic section (recommendation: use a binary search strategy) Run pandoc manually: user@host $ docker exec <CONTAINER ID> pandoc -f twiki -t markdown_github <ARCHIVE COPY> > <MARKDOWN FILE> Where <CONTAINER ID> is the docker container ID, <ARCHIVE COPY> is the the file you copied in the first step and <MARKDOWN FILE> is the resulting .md file Repeat steps 2-4 until you've narrowed down the problematic section Manually convert the offending section","title":"Troubleshooting conversion"},{"location":"documentation/markdown-migration/#conversion-without-docker","text":"If you've already used the docker method , skip to the section about completing the conversion .","title":"Conversion without Docker"},{"location":"documentation/markdown-migration/#requirements_1","text":"This method requires the following: Fork and clone the repository that you chose in the above section pandoc (> 1.16) mkdocs MarkdownHighlight pygments","title":"Requirements"},{"location":"documentation/markdown-migration/#preparing-the-git-repository_1","text":"cd into your local git repository Add opensciencegrid/technology as the upstream remote repository for merging upstream changes: user@host $ git remote add upstream https://www.github.com/opensciencegrid/technology.git Create a branch for the document you plan to convert: user@host $ git branch <BRANCH NAME> master Replace <BRANCH NAME> with a name of your choice 5. Change to the branch you just created user@host $ git checkout <BRANCH NAME> Replace <BRANCH NAME> with the name you chose in the step above","title":"Preparing the git repository"},{"location":"documentation/markdown-migration/#archiving-the-twiki-document","text":"Follow the instructions for archival then continue to the next section to convert the document with pandoc.","title":"Archiving the TWiki document"},{"location":"documentation/markdown-migration/#initial-conversion-with-pandoc","text":"Pandoc is a tool that's useful for automated conversion of markdown languages. Once installed (alternatively, run pandoc via docker ), run the following command to convert TWiki to Markdown: $ pandoc -f twiki -t markdown_github <TWIKI FILE> > <MARKDOWN FILE> Where <TWIKI FILE> is the path to initial document in raw TWiki and <MARKDOWN FILE> is the path to the resulting document in GitHub Markdown. Note If you don't see output from the above command quickly, it means that Pandoc is having an issue with a specific section of the document. Stop the command (or docker container), find and temporarily remove the offending section, convert the remainder of the document with Pandoc, and manually convert the offending section.","title":"Initial conversion with Pandoc"},{"location":"documentation/markdown-migration/#previewing-your-documents-with-mkdocs","text":"Mkdocs has a development mode that can be used to preview documents as you work on them and is available via package manager or pip . Once installed , add your document(s) to the pages section of mkdocs.yml and launch the mkdocs server with the following command from the dir containing mkdocs.yml : $ PYTHONPATH = src/ mkdocs serve Access the server at http://127.0.0.1:8000 and navigate to the document you're working on. It's useful to open the original TWiki doc in an adjacent tab or window to quickly compare the two.","title":"Previewing your document(s) with Mkdocs"},{"location":"documentation/markdown-migration/#completing-the-conversion","text":"Manual review of the automatically converted documents are required since the automatic conversion process isn't perfect. This section contains a list of problems commonly encountered in automatically converted documents. Visit the style guide to ensure that the document meets all style guidelines.","title":"Completing the conversion"},{"location":"documentation/markdown-migration/#archiving-documents","text":"If the document is slated for archival (check if it says \"yes\" in the \"archived\" column of the spreadsheet), just download the document to the archive folder of your local git repository: user@host $ cd technology/ user@host $ curl '<TWIKI URL>?raw=text' | iconv -f windows-1252 > archive/<TWIKI TITLE> Where <TWIKI URL> is the link to the TWiki document that you want to download and <TWIKI TITLE> is the name that will receive the archived file For example: user@host $ cd technology user@host $ curl 'https://twiki.opensciencegrid.org/bin/view/Documentation/Release3/SHA2Compliance?raw=text' | iconv -f windows-1252 > archive/SHA2Compliance After downloading the document, continue onto the next section to walk through pull request submission.","title":"Archiving Documents"},{"location":"documentation/markdown-migration/#submitting-the-pull-request","text":"Stage the archived raw TWiki (as well as the converted Markdown document(s) and mkdocs.yml if you are converting the document): user@host $ git add mkdocs.yml archive/<TWIKI ARCHIVE> <PATH TO CONVERTED DOC> Where <TWIKI ARCHIVE> is the name of the archived document and <PATH TO CONVERTED DOC> is the path to the .md file Commit and push your changes to your GitHub repo: user@host $ git commit -m \"<COMMIT MSG>\" user@host $ git push origin <BRANCH NAME> Change <COMMIT MSG> for a meaningful text that describes the conversion done and <BRANCH NAME> with the name chosen in the 3rd step of the Preparing the git repository section Open your browser and navigate to your GitHub fork Submit a pull request containing with the following body: <LINK TO TWIKI DOCUMENT> - [ ] Enter date into \"Migrated\" column of google sheet An example of <LINK TO TWIKI DOCUMENT> is: https://twiki.opensciencegrid.org/bin/view/SoftwareTeam/SoftwareDevelopmentProcess If you are migrating a document, also add this task: - [ ] Add migration header to TWiki document If you are archiving a document, add this task: - [ ] Move TWiki document to the trash See an example pull request here .","title":"Submitting the pull request"},{"location":"documentation/markdown-migration/#after-the-pull-request","text":"After the pull request is merged, replace the contents of TWiki document with the div if you're migrating the document, linking to the location of the migrated document: <div style=\"border: 1px solid black; margin: 1em 0; padding: 1em; background-color: #FFDDDD; font-weight: 600;\"> This document has been migrated to !GitHub (<LINK TO GITHUB DOCUMENT>). If you wish to see the old TWiki document, use the TWiki history below. Background: At the end of year (2017), the TWiki will be retired in favor of !GitHub. You can find the various TWiki webs and their new !GitHub locations listed below: * Release3: https://www.opensciencegrid.org/docs ([[https://github.com/opensciencegrid/docs/tree/master/archive][archive]]) * !SoftwareTeam: https://www.opensciencegrid.org/technology ([[https://github.com/opensciencegrid/technology/tree/master/archive][archive]]) </div> If you are archiving a document, move it to the trash instead. Once the document has been updated or trashed, add the date to the spreadsheet and go back to your pull request and mark your tasks as complete. For example, if you completed the migration of a document: - [X] Enter date into \"Migrated\" column of google sheet - [X] Add migration div to TWiki document Currently, we do not recommend changing backlinks (links on other twiki pages that refer to the Twiki page you are migrating) to point at the new GitHub URL. This is to provide a simple reminder to users that the migration will occur, and also is likely low priority regardless as all pages will eventually migrate to GitHub. This advice may change in the future as we gain experience with this transition.","title":"After the pull request"},{"location":"documentation/markdown-migration/#reviewing-pull-requests","text":"To review pull requests, cd into the dir containing your git repository and check out the requester's branch, which the twiki-converter container should automatically notice. Here's an example checking out Brian's cut-sw-release branch of the technology repository: # Add the requester 's repo as a remote if you haven' t already user@host $ git remote add blin https://www.github.com/brianhlin/technology.git user@host $ git fetch --all user@host $ git checkout blin/cut-sw-release Refresh your browser and navigate to the document in the request.","title":"Reviewing pull requests"},{"location":"documentation/publish-osg-pages/","text":"Publishing OSG Pages with MkDocs \u00b6 The OSG uses MkDocs for site documentation and team-specific web pages (e.g. https://osg-htc.org/technology/ ). This document contains instructions for creating a new OSG area through GitHub and transitioning an existing MkDocs GitHub repository from Travis CI to GitHub Actions . Creating New Pages \u00b6 Need assistance? If you need any assistance with setting up your GitHub repository, please reach out to help@osg-htc.org . This document assumes that you are an administrator of the opensciencegrid GitHub organization. Before starting, make sure that you have the git and gem tools installed. Create a new public repository in the opensciencegrid organization (referred to as <REPO NAME> in the rest of this document) Check the box marked Initialize this repository with a README Identify the repository as using mkdocs: On the repository home page (i.e., https://github.com/opensciencegrid/<REPO NAME> ), click the gear button in the top right (next to \"About\") In the topics field, add mkdocs Click the \u201cSave Changes\u201d button Clone the repository and cd into the directory: git clone https://github.com/opensciencegrid/<REPO NAME>.git cd <REPO NAME> Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md and populate the LICENSE file with a Creative Commons Attribution 4.0 license : wget https://creativecommons.org/licenses/by/4.0/legalcode.txt > LICENSE Create and encrypt the repository deploy key Generate the repository deploy key: ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-key -N '' Install the travis gem: gem install travis Login using your GitHub credentials: travis login --com Enable the repository in Travis: travis enable --com -r opensciencegrid/<REPO NAME> Encrypt the deploy key and temporarily save the output (you will need the hashes later for .travis.env ): travis encrypt-file --com deploy-key Stage and commit your files: git add LICENSE README.md deploy-key.enc git commit -m \"Prepare the repository for Travis-CI deployment\" Danger Do NOT commit the unencrypted deploy-key ! Add the contents of deploy-key.pub to your repository's list of deploy keys . Make sure to check Allow write access . Follow these instructions to add the doc-ci-scripts sub-module Use the mkdocs-v1 branch of the doc-ci-scripts submodule. Create mkdocs.yml containing the following: site_name: <TITLE OF YOUR SITE> site_url: https://osg-htc.org/<REPO NAME> repo_name: https://github.com/osg-htc/<REPO NAME> theme: name: material nav: - Home: 'index.md' markdown_extensions: - admonition - codehilite: guess_lang: False - meta - toc: permalink: True Create a docs directory containing an index.md that will be your home page. Stage and commit these changes: git add mkdocs.yml docs/index.md git commit -m \"Staging initial web page contents\" Push local changes to the GitHub repository: git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME> Contact help@osg-htc.org to request repository backups to UW-Madison. Creating an ITB Area \u00b6 This section describes creating an ITB repository for a documentation area created in the previous section Create a new repository in the opensciencegrid organization and name it <REPO NAME>-itb . For example, an ITB area for the docs repository has a repository name of docs-itb . The ITB repository will be referred to as <ITB REPO NAME> in the rest of this document. Check the box marked Initialize this repository with a README Once created, add the mkdocs topic by clicking on the \"Add topics\" button Clone the repository and cd into the directory: git clone git@github.com:opensciencegrid/<ITB REPO NAME> cd <ITB REPO NAME> Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md In the non-ITB repository, create and encrypt the ITB repository deploy key cd into the non-ITB repository and generate the ITB deploy key cd <REPO NAME> ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-itb Install the travis gem: gem install travis Encrypt the deploy key: travis encrypt-file deploy-itb Update .travis.env with the appropriate ITB values Add and commit your files: git add .travis.env deploy-itb.enc git commit -m \"Add ITB deployment\" Danger Do NOT commit the unencrypted deploy-itb ! Add deploy-itb.pub to the ITB repository's list of deploy keys . Make sure to check Allow write access . Still in the non-ITB repository, push your local changes to the GitHub repository git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME> Transitioning to GitHub Actions \u00b6 Need assistance? If you need any assistance with transitioning your repository to GitHub actions, please reach out to help@osg-htc.org . When originally developed, OSG MkDocs repositories were set up to automatically publish web page changes through Travis CI . But in November 2020, Travis CI changed their pricing model so we are moving the automatic publishing infrastructure to GitHub Actions and using this opportunity to also upgrade the version of MkDocs. To ensure that your pages continue to be autmoatically published you will need to prepare your repository for the new version of MkDocs, disable Travis CI, and enable GitHub Actions. Preparing the repository \u00b6 Before upgrading, you must fix the following incompatibilities: Rename the pages: section of mkdocs.yml to nav: . The section contents are identical; only the name is changing. Update all of the links in the documents as follows: Ensure links end in .md Ensure links are document-relative, not site-relative For example, links should be of the form ../software/development-process.md instead of /software/development-process . Push your changes to your fork and create a pull request Previewing your pages with Docker If you would like to ensure the correctness of your fixes, run the following command: docker run -it -v ${PWD}/docs -p 8000:8000 squidfunk/mkdocs-material:6.1.4 After running this command, enter localhost:8000 in your browser to preview your pages. Saved changes made to .md files are automatically updated in your browser! Disabling Travis CI \u00b6 After you've prepared your repository for the transition, disable Travis CI by removing related files from it. Perform the following actions from the command-line: Create a fresh clone of the repository that is still using Travis CI: git clone https://github.com/opensciencegrid/<GIT REPOSITORY> Important For the rest of the steps in this documentation to work, you should create a new clone of the repository using the above command, even if you already have an existing copy! cd into the directory containing the repository (should be the same as <GIT REPOSITORY> by default) Remove all of the Travs CI related files: git rm ci git rm .travis.env deploy-key.enc .travis.yml Commit your changes: git commit -am \"Disable Travis CI\" Push your changes (you will be prompted for your GitHub credentials): git push origin master Enabling GitHub Actions \u00b6 The new method for validating and publishing OSG pages for a MkDocs repository can be enabled entirely through the GitHub web interface : Navigate to the opensciencegrid fork of the GitHub repository in your web browser, e.g. https://github.com/opensciencegrid/docs/ Click on the Actions tab: Find the Publish MkDocs static HTML workflow by the Open Science Grid and click the Set up this workflow button: Click on the Start commit drop-down button then click Commit new file : Navigate to the Actions tab to verify your transition. If you see green check marks, your pages are now being published with GitHub Actions! (Optional) Enable the Validate MkDocs Static HTML workflow to check for broken links and markdown correctness of pull requests to the repository. Navigate to the Actions tab as before Click on the New Workflow button: Find the Validate MkDocs static HTML workflow by the Open Science Grid and click Set up this workflow As before, click on the Start commit drop-down button then click Commit new file","title":"Publishing OSG pages"},{"location":"documentation/publish-osg-pages/#publishing-osg-pages-with-mkdocs","text":"The OSG uses MkDocs for site documentation and team-specific web pages (e.g. https://osg-htc.org/technology/ ). This document contains instructions for creating a new OSG area through GitHub and transitioning an existing MkDocs GitHub repository from Travis CI to GitHub Actions .","title":"Publishing OSG Pages with MkDocs"},{"location":"documentation/publish-osg-pages/#creating-new-pages","text":"Need assistance? If you need any assistance with setting up your GitHub repository, please reach out to help@osg-htc.org . This document assumes that you are an administrator of the opensciencegrid GitHub organization. Before starting, make sure that you have the git and gem tools installed. Create a new public repository in the opensciencegrid organization (referred to as <REPO NAME> in the rest of this document) Check the box marked Initialize this repository with a README Identify the repository as using mkdocs: On the repository home page (i.e., https://github.com/opensciencegrid/<REPO NAME> ), click the gear button in the top right (next to \"About\") In the topics field, add mkdocs Click the \u201cSave Changes\u201d button Clone the repository and cd into the directory: git clone https://github.com/opensciencegrid/<REPO NAME>.git cd <REPO NAME> Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md and populate the LICENSE file with a Creative Commons Attribution 4.0 license : wget https://creativecommons.org/licenses/by/4.0/legalcode.txt > LICENSE Create and encrypt the repository deploy key Generate the repository deploy key: ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-key -N '' Install the travis gem: gem install travis Login using your GitHub credentials: travis login --com Enable the repository in Travis: travis enable --com -r opensciencegrid/<REPO NAME> Encrypt the deploy key and temporarily save the output (you will need the hashes later for .travis.env ): travis encrypt-file --com deploy-key Stage and commit your files: git add LICENSE README.md deploy-key.enc git commit -m \"Prepare the repository for Travis-CI deployment\" Danger Do NOT commit the unencrypted deploy-key ! Add the contents of deploy-key.pub to your repository's list of deploy keys . Make sure to check Allow write access . Follow these instructions to add the doc-ci-scripts sub-module Use the mkdocs-v1 branch of the doc-ci-scripts submodule. Create mkdocs.yml containing the following: site_name: <TITLE OF YOUR SITE> site_url: https://osg-htc.org/<REPO NAME> repo_name: https://github.com/osg-htc/<REPO NAME> theme: name: material nav: - Home: 'index.md' markdown_extensions: - admonition - codehilite: guess_lang: False - meta - toc: permalink: True Create a docs directory containing an index.md that will be your home page. Stage and commit these changes: git add mkdocs.yml docs/index.md git commit -m \"Staging initial web page contents\" Push local changes to the GitHub repository: git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME> Contact help@osg-htc.org to request repository backups to UW-Madison.","title":"Creating New Pages"},{"location":"documentation/publish-osg-pages/#creating-an-itb-area","text":"This section describes creating an ITB repository for a documentation area created in the previous section Create a new repository in the opensciencegrid organization and name it <REPO NAME>-itb . For example, an ITB area for the docs repository has a repository name of docs-itb . The ITB repository will be referred to as <ITB REPO NAME> in the rest of this document. Check the box marked Initialize this repository with a README Once created, add the mkdocs topic by clicking on the \"Add topics\" button Clone the repository and cd into the directory: git clone git@github.com:opensciencegrid/<ITB REPO NAME> cd <ITB REPO NAME> Create a gh-pages branch in the GitHub repository: git push origin main:gh-pages Update the contents of README.md In the non-ITB repository, create and encrypt the ITB repository deploy key cd into the non-ITB repository and generate the ITB deploy key cd <REPO NAME> ssh-keygen -t rsa -b 4096 -C \"help@osg-htc.org\" -f deploy-itb Install the travis gem: gem install travis Encrypt the deploy key: travis encrypt-file deploy-itb Update .travis.env with the appropriate ITB values Add and commit your files: git add .travis.env deploy-itb.enc git commit -m \"Add ITB deployment\" Danger Do NOT commit the unencrypted deploy-itb ! Add deploy-itb.pub to the ITB repository's list of deploy keys . Make sure to check Allow write access . Still in the non-ITB repository, push your local changes to the GitHub repository git push origin main Your documents should be shortly available at https://www.opensciencegrid.org/<REPO NAME>","title":"Creating an ITB Area"},{"location":"documentation/publish-osg-pages/#transitioning-to-github-actions","text":"Need assistance? If you need any assistance with transitioning your repository to GitHub actions, please reach out to help@osg-htc.org . When originally developed, OSG MkDocs repositories were set up to automatically publish web page changes through Travis CI . But in November 2020, Travis CI changed their pricing model so we are moving the automatic publishing infrastructure to GitHub Actions and using this opportunity to also upgrade the version of MkDocs. To ensure that your pages continue to be autmoatically published you will need to prepare your repository for the new version of MkDocs, disable Travis CI, and enable GitHub Actions.","title":"Transitioning to GitHub Actions"},{"location":"documentation/publish-osg-pages/#preparing-the-repository","text":"Before upgrading, you must fix the following incompatibilities: Rename the pages: section of mkdocs.yml to nav: . The section contents are identical; only the name is changing. Update all of the links in the documents as follows: Ensure links end in .md Ensure links are document-relative, not site-relative For example, links should be of the form ../software/development-process.md instead of /software/development-process . Push your changes to your fork and create a pull request Previewing your pages with Docker If you would like to ensure the correctness of your fixes, run the following command: docker run -it -v ${PWD}/docs -p 8000:8000 squidfunk/mkdocs-material:6.1.4 After running this command, enter localhost:8000 in your browser to preview your pages. Saved changes made to .md files are automatically updated in your browser!","title":"Preparing the repository"},{"location":"documentation/publish-osg-pages/#disabling-travis-ci","text":"After you've prepared your repository for the transition, disable Travis CI by removing related files from it. Perform the following actions from the command-line: Create a fresh clone of the repository that is still using Travis CI: git clone https://github.com/opensciencegrid/<GIT REPOSITORY> Important For the rest of the steps in this documentation to work, you should create a new clone of the repository using the above command, even if you already have an existing copy! cd into the directory containing the repository (should be the same as <GIT REPOSITORY> by default) Remove all of the Travs CI related files: git rm ci git rm .travis.env deploy-key.enc .travis.yml Commit your changes: git commit -am \"Disable Travis CI\" Push your changes (you will be prompted for your GitHub credentials): git push origin master","title":"Disabling Travis CI"},{"location":"documentation/publish-osg-pages/#enabling-github-actions","text":"The new method for validating and publishing OSG pages for a MkDocs repository can be enabled entirely through the GitHub web interface : Navigate to the opensciencegrid fork of the GitHub repository in your web browser, e.g. https://github.com/opensciencegrid/docs/ Click on the Actions tab: Find the Publish MkDocs static HTML workflow by the Open Science Grid and click the Set up this workflow button: Click on the Start commit drop-down button then click Commit new file : Navigate to the Actions tab to verify your transition. If you see green check marks, your pages are now being published with GitHub Actions! (Optional) Enable the Validate MkDocs Static HTML workflow to check for broken links and markdown correctness of pull requests to the repository. Navigate to the Actions tab as before Click on the New Workflow button: Find the Validate MkDocs static HTML workflow by the Open Science Grid and click Set up this workflow As before, click on the Start commit drop-down button then click Commit new file","title":"Enabling GitHub Actions"},{"location":"documentation/reviewing-documentation/","text":"Reviewing Software Documentation \u00b6 To maintain quality documentation, we regularly review our documentation for clarity and correctness. Performing a Review \u00b6 When reviewing a document, follow the instructions of the document to a tee as if you were completely new to the OSG. Some common things to note and/or fix: After completing the instructions in the document: Does the document inform you how to use the product? Does the document tell you how to verify that the product is functioning? Does the product work? Incorrect or out of date instructions Steps that may be particularly conducive to software or default configuration as a solution Lack of clarity or any other confusion you may have Additionally, ensure that the document meets our style and layout guidelines, as well as correct spelling and grammar. Completing a Review \u00b6 Upon completion of the review: Update (or add) the review date in the metadata at the top of the document above the h1 : DateReviewed: YYYY-MM-DD Submit a pull request with the above change and any other improvements from the review","title":"Reviewing Documentation"},{"location":"documentation/reviewing-documentation/#reviewing-software-documentation","text":"To maintain quality documentation, we regularly review our documentation for clarity and correctness.","title":"Reviewing Software Documentation"},{"location":"documentation/reviewing-documentation/#performing-a-review","text":"When reviewing a document, follow the instructions of the document to a tee as if you were completely new to the OSG. Some common things to note and/or fix: After completing the instructions in the document: Does the document inform you how to use the product? Does the document tell you how to verify that the product is functioning? Does the product work? Incorrect or out of date instructions Steps that may be particularly conducive to software or default configuration as a solution Lack of clarity or any other confusion you may have Additionally, ensure that the document meets our style and layout guidelines, as well as correct spelling and grammar.","title":"Performing a Review"},{"location":"documentation/reviewing-documentation/#completing-a-review","text":"Upon completion of the review: Update (or add) the review date in the metadata at the top of the document above the h1 : DateReviewed: YYYY-MM-DD Submit a pull request with the above change and any other improvements from the review","title":"Completing a Review"},{"location":"documentation/style-guide/","text":"Markdown Style Guide \u00b6 This document contains markdown conventions that are used in OSG Software documentation. Meta \u00b6 Run a spellchecker to catch any obvious spelling mistakes. Use official capitalizations when referring to titles (i.e., HTTPS, HTCondor) Start each new sentence on a new line. Lines should not exceed 120 characters, except in the case of link text , but may be split at earlier points (e.g. punctuation). Headings \u00b6 Use the following conventions for headings: The title should be the only level 1 heading Level 1 headings should use the ==== format Level 2 headings should use the ---- format Use APA-style title case for level 1 and level 2 headings. Only capitalize the first word for all other headings. Other heading levels should use the appropriate number of # Go no deeper than of level 5 headings Spin-off a new document or re-organize the existing document if you find that you regularly need level 5 headings. Links \u00b6 Only use document relative links in MkDocs 1.0.0 and newer MkDocs 1.0.0 does not support site-relative links (e.g. /software/development-process.md ). You must use document-relative links (e.g. ../software/development-process.md ) instead. Earlier versions of this guide recommended site-relative links; these only worked in earlier versions of MkDocs. Document-relative links work in all versions of MkDocs. Please convert any site-relative links to document-relative links before updating the doc-ci-scripts submodule to use MkDocs 1.0.0+. Links to internal pages must have the .md extension. (Earlier versions of this guide said links should not have the .md extension, but adding the .md extension is required for MkDocs 1.0.0+. Links with the .md extension work in all versions of MkDocs.) Links to the area's homepage (e.g. https://osg-htc.org/technology/) need to be of the form [link text](/) Links to other areas (like from https://osg-htc.org/technology/ to https://osg-htc.org/operations/) need to be absolute links (i.e. include the domain name) Section links \u00b6 To link sections within a page, lowercase the entire section name and replace spaces with dashes. If there are multiple sections with the same name you can link the subsequent sections by appending _N where N is the section's ordinal number minus one, e.g. append _1 for the second section. For example, if you have three sections named \"Optional Configuration\", link them like so: [1st section](#optional-configuration) [2nd section](#optional-configuration_1) [3rd section](#optional-configuration_2) Command blocks and file snippets \u00b6 Command blocks and file snippets outside of lists should be wrapped in three back-ticks (```) followed by an optional code highlighting format: ```console # stuff ``` Command blocks and file snippets inside of a list should use the appropriate number of spaces before three colons followed by an optional code highlighting format: # stuff See the lists section for details on properly formatting command blocks within a list. We use the Pygments highlighting library for syntax; it knows about 100 different languages. The Pygments website contains a live renderer if you want to see how your text will come out. Please use the console language for shell sessions. Root and user prompts \u00b6 When specifying instructions for the command-line, indicate to users whether the commands can be run as root ( root@host # ) or as an unprivileged user ( user@host $ ). For example: root@host # useradd -m osguser root@host # su - osguser user@host $ whoami osguser It can provide helpful context to use a more specific hostname in the prompt than host . For example, if you're writing a doc for setting up a Storage Element and a command is run as root on the SE, use root@se # . Or if you're testing the SE from the client side and the command is run as a normal user on a client, use user@client $ . Highlighting user input \u00b6 Use descriptive, all-caps text wrapped in angle brackets to to highlight areas that users would have to insert text specific to their site, e.g. <REMOTE SSH HOSTNAME> . The same text should be cited verbatim in surrounding prose with further explanation with examples of appropriate values. For additional visual highlighting, use hl_lines=\"N\" , where N can indicate multiple line numbers: ```console hl_lines=\"1 3\" root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME> ```` Similarly, you may also specify :::console hl_lines=\"N\" for indented command blocks, replacing console with any language supported by Pygments . The above block is rendered below: root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME> Lists \u00b6 When constructing lists, use the following guidelines: Use 1. for each item in a numbered list To make sure the contents of code blocks, file snippets, and subsequent paragraphs are indented properly, use the following formatting: For code blocks or file snippets, add an empty line after any regular text, then insert (N+1)*4 spaces at the beginning of each line, where N is the level of the item in the list. To apply code highlighting, start the code block with :::<FORMAT> ; see this page for details, including possible highlighting formats. For an example of formatting a code section inside a list, see the release series document . For additional text (i.e. after a code block), insert N*4 spaces at the beginning of each line, where N is the level of the item in the list. For example: 1. Foo - Bar :::console COMMAND BLOCK text associated with Bar text associated with Foo 1. Baz FILE SNIPPET There are 12 spaces and 8 spaces in front of the command block and text associated with Bar , respectively; 4 spaces in front of the text associated with Foo ; and 8 spaces in front of the file snippet associated with Baz . The above block is rendered below: Foo Bar COMMAND BLOCK text associated with Bar text associated with Foo Baz FILE SNIPPET Notes \u00b6 To catch the user's attention for important items or pitfalls, we used %NOTE% TWiki macros, these can be replaced with admonition-style notes and warnings: !!! note things to note or !!! warning if a user doesn't do this thing, bad stuff will happen The above blocks are rendered below as an example. Note things to note and Warning if a user doesn't do this thing, bad stuff will happen For a full list of admonition styles, see the documentation here .","title":"Markdown Style Guide"},{"location":"documentation/style-guide/#markdown-style-guide","text":"This document contains markdown conventions that are used in OSG Software documentation.","title":"Markdown Style Guide"},{"location":"documentation/style-guide/#meta","text":"Run a spellchecker to catch any obvious spelling mistakes. Use official capitalizations when referring to titles (i.e., HTTPS, HTCondor) Start each new sentence on a new line. Lines should not exceed 120 characters, except in the case of link text , but may be split at earlier points (e.g. punctuation).","title":"Meta"},{"location":"documentation/style-guide/#headings","text":"Use the following conventions for headings: The title should be the only level 1 heading Level 1 headings should use the ==== format Level 2 headings should use the ---- format Use APA-style title case for level 1 and level 2 headings. Only capitalize the first word for all other headings. Other heading levels should use the appropriate number of # Go no deeper than of level 5 headings Spin-off a new document or re-organize the existing document if you find that you regularly need level 5 headings.","title":"Headings"},{"location":"documentation/style-guide/#links","text":"Only use document relative links in MkDocs 1.0.0 and newer MkDocs 1.0.0 does not support site-relative links (e.g. /software/development-process.md ). You must use document-relative links (e.g. ../software/development-process.md ) instead. Earlier versions of this guide recommended site-relative links; these only worked in earlier versions of MkDocs. Document-relative links work in all versions of MkDocs. Please convert any site-relative links to document-relative links before updating the doc-ci-scripts submodule to use MkDocs 1.0.0+. Links to internal pages must have the .md extension. (Earlier versions of this guide said links should not have the .md extension, but adding the .md extension is required for MkDocs 1.0.0+. Links with the .md extension work in all versions of MkDocs.) Links to the area's homepage (e.g. https://osg-htc.org/technology/) need to be of the form [link text](/) Links to other areas (like from https://osg-htc.org/technology/ to https://osg-htc.org/operations/) need to be absolute links (i.e. include the domain name)","title":"Links"},{"location":"documentation/style-guide/#section-links","text":"To link sections within a page, lowercase the entire section name and replace spaces with dashes. If there are multiple sections with the same name you can link the subsequent sections by appending _N where N is the section's ordinal number minus one, e.g. append _1 for the second section. For example, if you have three sections named \"Optional Configuration\", link them like so: [1st section](#optional-configuration) [2nd section](#optional-configuration_1) [3rd section](#optional-configuration_2)","title":"Section links"},{"location":"documentation/style-guide/#command-blocks-and-file-snippets","text":"Command blocks and file snippets outside of lists should be wrapped in three back-ticks (```) followed by an optional code highlighting format: ```console # stuff ``` Command blocks and file snippets inside of a list should use the appropriate number of spaces before three colons followed by an optional code highlighting format: # stuff See the lists section for details on properly formatting command blocks within a list. We use the Pygments highlighting library for syntax; it knows about 100 different languages. The Pygments website contains a live renderer if you want to see how your text will come out. Please use the console language for shell sessions.","title":"Command blocks and file snippets"},{"location":"documentation/style-guide/#root-and-user-prompts","text":"When specifying instructions for the command-line, indicate to users whether the commands can be run as root ( root@host # ) or as an unprivileged user ( user@host $ ). For example: root@host # useradd -m osguser root@host # su - osguser user@host $ whoami osguser It can provide helpful context to use a more specific hostname in the prompt than host . For example, if you're writing a doc for setting up a Storage Element and a command is run as root on the SE, use root@se # . Or if you're testing the SE from the client side and the command is run as a normal user on a client, use user@client $ .","title":"Root and user prompts"},{"location":"documentation/style-guide/#highlighting-user-input","text":"Use descriptive, all-caps text wrapped in angle brackets to to highlight areas that users would have to insert text specific to their site, e.g. <REMOTE SSH HOSTNAME> . The same text should be cited verbatim in surrounding prose with further explanation with examples of appropriate values. For additional visual highlighting, use hl_lines=\"N\" , where N can indicate multiple line numbers: ```console hl_lines=\"1 3\" root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME> ```` Similarly, you may also specify :::console hl_lines=\"N\" for indented command blocks, replacing console with any language supported by Pygments . The above block is rendered below: root@condor-ce # yum install htcondor-ce # this is a comment root@condor-ce # condor_ce_trace -d <CE HOSTNAME>","title":"Highlighting user input"},{"location":"documentation/style-guide/#lists","text":"When constructing lists, use the following guidelines: Use 1. for each item in a numbered list To make sure the contents of code blocks, file snippets, and subsequent paragraphs are indented properly, use the following formatting: For code blocks or file snippets, add an empty line after any regular text, then insert (N+1)*4 spaces at the beginning of each line, where N is the level of the item in the list. To apply code highlighting, start the code block with :::<FORMAT> ; see this page for details, including possible highlighting formats. For an example of formatting a code section inside a list, see the release series document . For additional text (i.e. after a code block), insert N*4 spaces at the beginning of each line, where N is the level of the item in the list. For example: 1. Foo - Bar :::console COMMAND BLOCK text associated with Bar text associated with Foo 1. Baz FILE SNIPPET There are 12 spaces and 8 spaces in front of the command block and text associated with Bar , respectively; 4 spaces in front of the text associated with Foo ; and 8 spaces in front of the file snippet associated with Baz . The above block is rendered below: Foo Bar COMMAND BLOCK text associated with Bar text associated with Foo Baz FILE SNIPPET","title":"Lists"},{"location":"documentation/style-guide/#notes","text":"To catch the user's attention for important items or pitfalls, we used %NOTE% TWiki macros, these can be replaced with admonition-style notes and warnings: !!! note things to note or !!! warning if a user doesn't do this thing, bad stuff will happen The above blocks are rendered below as an example. Note things to note and Warning if a user doesn't do this thing, bad stuff will happen For a full list of admonition styles, see the documentation here .","title":"Notes"},{"location":"documentation/writing-documentation/","text":"Writing OSG Documentation \u00b6 Many OSG pages are written in markdown , built using MkDocs , and served via GitHub Pages . To contribute content , submit a pull request to the relevant GitHub repository, which are tagged with \"mkdocs\". List of documentation repos This document contains instructions, recommendations, and guidelines for writing OSG content. Contributing Content \u00b6 To contribute minor content changes (e.g., fixing typos, changing a couple of sentences), we recommend using the GitHub web interface to submit a pull request. To contribute major content changes to one of the above OSG areas, make sure you and the machine you'll be working on meet the following requirements: Have a Github account Installations of the following tools: Docker git Preparing the git repository \u00b6 Before making any content changes, you will need to prepare a local git clone: Fork and clone the GitHub repository that you'd like to contribute to Add the upstream Github repository as a remote . For example, if you are working on the User School 2018 pages: $ git remote add upstream https://github.com/opensciencegrid/user-school-2018 Previewing the pages \u00b6 To preview the pages, start a MkDocs development server. The development server will automatically detect any content changes and make them viewable in your browser. cd into the directory containing the local clone of your GitHub fork Start a MkDocs development server to preview your changes: $ docker run --rm -p 8000 :8000 -v ${ PWD } :/docs squidfunk/mkdocs-material:7.1.0 To preview your changes visit localhost:8000 in the browser of your choice. The server can be stopped with Ctrl-C . Making content changes \u00b6 To contribute content to the OSG, follow these steps to submit a pull request with your desired changes: cd into the directory containing the local clone of your Github fork Create a branch based on a branch from the upstream repository: $ git fetch --all $ git checkout -b <BRANCH NAME> upstream/<UPSTREAM BRANCH NAME> Replace <BRANCH NAME> with a name of your choice and <UPSTREAM BRANCH NAME> with a branch name from the upstream repository. For example, instructors for the 2018 User School should use the materials branch: $ git checkout -b example_branch_name upstream/materials If you do not know which upstream branch to use, pick master . Make your changes in the docs/ directory of your local clone, following the style guide : If you are making changes to an existing page: Open mkdocs.yml and find the location of the file relative to the docs/ directory Make your changes to that file and move onto the next step If you are contributing a new page: Name the page. Page file names should be lowercase, - delimited, and concise but descriptive, e.g. markdown-migration.md or cutting-release.md Place the page in the relevant sub-folder of the docs/ directory. If you are unsure of the appropriate location, note that in the description of the pull request. Add the document to the nav: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Note If mkdocs.yml contains does not contain a nav: section, add the above to the pages: section instead. This means that the repository is using an older version of MkDocs and will need to be transitioned to GitHub Actions . If you are writing site administrator documentation, following the suggested document layout If you haven't already, start a Mkdocs development server to preview your changes . Continue making changes until you are satisfied with the preview, then stage your changes in git: $ git add <YOUR FILE> <YOUR 2nd FILE>...<YOUR Nth FILE> Where <YOUR * FILE> is any file that contains changes that you'd wish to make. If you are adding a new page, one of the files should be mkdocs.yml . Commit your changes and push them to your Github fork: $ git commit -m \"<DESCRIPTIVE COMMIT MESSAGE>\" $ git push origin Where <DESCRIPTIVE COMMIT MESSAGE> is a meaningful short text that identifies the changes applied, it is a good practice, to concatenate the ticket number associated e.g. \"Removing color macros (SOFTWARE-3739)\" From your Github fork, submit a pull request Document Layout \u00b6 This section contains suggested layouts of externally-facing, site administrator documentation . The introduction is the only layout requirement for documents except for installation guides. Introductions \u00b6 All documents should start with an introduction that explains what the document contains, what the product does, and why someone may want to use it. In the past, document introductions were included in About this... sections due to the layout of the table of contents. Since the table of contents is included in the sidebar this is unnecessary and introduction content should go directly below the title heading without any second-level headings. The HTCondor-CE installation guide is an example that meet all of the above criteria. Installation guides \u00b6 In addition to the introduction above, installation documents should have the following sections: Before Starting: This section should contain information for any prepatory work that the site administrator should do or consider before proceeding with the installation ( example ). Installation: Procedural instructions that tell the user how to install the software ( example ) Validation: How does the user make sure their installation is functional? Optionally, the following sections should be included as necessary. Overview: if the introduction becomes large and unwieldy, extract the details of what the product does into an overview section Configuration: required configuration steps ( example ) as well as a sub-section for optional configurations. For long optional configuration sections, consider creating alist of contents at the top of the sub-section ( example ). Troubleshooting: common issues that users encounter and their fixes Reference: Details about configuration and log files, unix users, certificates, networking, links to relevant upstream documentation, etc. ( example ) If any of the sections become too large, consider separating them out and linking to the new documents ( example ). Tips for Writing Procedural Instructions \u00b6 Title the procedure with the user goal, usually starting with a gerund; e.g.: Installing the Frobnosticator Number all steps (as opposed to using bullets) List steps in order in which they are performed Each step should begin with a single-line instruction in plain English, in command form; e.g.: Make sure that the Frobnosticator configuration file is world-writable If the means of carrying out the instruction is unclear or complex, include clarification, ideally in the form of a working example; e.g.: chmod a+x /usr/share/frobnosticator/frob.conf Put clarifying information in separate paragraphs within the step Put critical information about the whole procedure in one or more paragraphs before the numbered steps Put supplemental information about the whole procedure in one or more paragraphs after the numbered steps Avoid pronouns when writing technical articles or documentation e.g., install foo rather than install it . Avoid superfluous statements like you will want , you want , you should e.g., install foo rather than you will want to install foo . Use the imperative form in step-by-step instructions, e.g. install package foo rather than the package foo should be installed","title":"Writing Documentation"},{"location":"documentation/writing-documentation/#writing-osg-documentation","text":"Many OSG pages are written in markdown , built using MkDocs , and served via GitHub Pages . To contribute content , submit a pull request to the relevant GitHub repository, which are tagged with \"mkdocs\". List of documentation repos This document contains instructions, recommendations, and guidelines for writing OSG content.","title":"Writing OSG Documentation"},{"location":"documentation/writing-documentation/#contributing-content","text":"To contribute minor content changes (e.g., fixing typos, changing a couple of sentences), we recommend using the GitHub web interface to submit a pull request. To contribute major content changes to one of the above OSG areas, make sure you and the machine you'll be working on meet the following requirements: Have a Github account Installations of the following tools: Docker git","title":"Contributing Content"},{"location":"documentation/writing-documentation/#preparing-the-git-repository","text":"Before making any content changes, you will need to prepare a local git clone: Fork and clone the GitHub repository that you'd like to contribute to Add the upstream Github repository as a remote . For example, if you are working on the User School 2018 pages: $ git remote add upstream https://github.com/opensciencegrid/user-school-2018","title":"Preparing the git repository"},{"location":"documentation/writing-documentation/#previewing-the-pages","text":"To preview the pages, start a MkDocs development server. The development server will automatically detect any content changes and make them viewable in your browser. cd into the directory containing the local clone of your GitHub fork Start a MkDocs development server to preview your changes: $ docker run --rm -p 8000 :8000 -v ${ PWD } :/docs squidfunk/mkdocs-material:7.1.0 To preview your changes visit localhost:8000 in the browser of your choice. The server can be stopped with Ctrl-C .","title":"Previewing the pages"},{"location":"documentation/writing-documentation/#making-content-changes","text":"To contribute content to the OSG, follow these steps to submit a pull request with your desired changes: cd into the directory containing the local clone of your Github fork Create a branch based on a branch from the upstream repository: $ git fetch --all $ git checkout -b <BRANCH NAME> upstream/<UPSTREAM BRANCH NAME> Replace <BRANCH NAME> with a name of your choice and <UPSTREAM BRANCH NAME> with a branch name from the upstream repository. For example, instructors for the 2018 User School should use the materials branch: $ git checkout -b example_branch_name upstream/materials If you do not know which upstream branch to use, pick master . Make your changes in the docs/ directory of your local clone, following the style guide : If you are making changes to an existing page: Open mkdocs.yml and find the location of the file relative to the docs/ directory Make your changes to that file and move onto the next step If you are contributing a new page: Name the page. Page file names should be lowercase, - delimited, and concise but descriptive, e.g. markdown-migration.md or cutting-release.md Place the page in the relevant sub-folder of the docs/ directory. If you are unsure of the appropriate location, note that in the description of the pull request. Add the document to the nav: section of mkdocs.yml in APA-style title case , e.g. - Migrating Documents to Markdown: 'software/markdown-migration.md' Note If mkdocs.yml contains does not contain a nav: section, add the above to the pages: section instead. This means that the repository is using an older version of MkDocs and will need to be transitioned to GitHub Actions . If you are writing site administrator documentation, following the suggested document layout If you haven't already, start a Mkdocs development server to preview your changes . Continue making changes until you are satisfied with the preview, then stage your changes in git: $ git add <YOUR FILE> <YOUR 2nd FILE>...<YOUR Nth FILE> Where <YOUR * FILE> is any file that contains changes that you'd wish to make. If you are adding a new page, one of the files should be mkdocs.yml . Commit your changes and push them to your Github fork: $ git commit -m \"<DESCRIPTIVE COMMIT MESSAGE>\" $ git push origin Where <DESCRIPTIVE COMMIT MESSAGE> is a meaningful short text that identifies the changes applied, it is a good practice, to concatenate the ticket number associated e.g. \"Removing color macros (SOFTWARE-3739)\" From your Github fork, submit a pull request","title":"Making content changes"},{"location":"documentation/writing-documentation/#document-layout","text":"This section contains suggested layouts of externally-facing, site administrator documentation . The introduction is the only layout requirement for documents except for installation guides.","title":"Document Layout"},{"location":"documentation/writing-documentation/#introductions","text":"All documents should start with an introduction that explains what the document contains, what the product does, and why someone may want to use it. In the past, document introductions were included in About this... sections due to the layout of the table of contents. Since the table of contents is included in the sidebar this is unnecessary and introduction content should go directly below the title heading without any second-level headings. The HTCondor-CE installation guide is an example that meet all of the above criteria.","title":"Introductions"},{"location":"documentation/writing-documentation/#installation-guides","text":"In addition to the introduction above, installation documents should have the following sections: Before Starting: This section should contain information for any prepatory work that the site administrator should do or consider before proceeding with the installation ( example ). Installation: Procedural instructions that tell the user how to install the software ( example ) Validation: How does the user make sure their installation is functional? Optionally, the following sections should be included as necessary. Overview: if the introduction becomes large and unwieldy, extract the details of what the product does into an overview section Configuration: required configuration steps ( example ) as well as a sub-section for optional configurations. For long optional configuration sections, consider creating alist of contents at the top of the sub-section ( example ). Troubleshooting: common issues that users encounter and their fixes Reference: Details about configuration and log files, unix users, certificates, networking, links to relevant upstream documentation, etc. ( example ) If any of the sections become too large, consider separating them out and linking to the new documents ( example ).","title":"Installation guides"},{"location":"documentation/writing-documentation/#tips-for-writing-procedural-instructions","text":"Title the procedure with the user goal, usually starting with a gerund; e.g.: Installing the Frobnosticator Number all steps (as opposed to using bullets) List steps in order in which they are performed Each step should begin with a single-line instruction in plain English, in command form; e.g.: Make sure that the Frobnosticator configuration file is world-writable If the means of carrying out the instruction is unclear or complex, include clarification, ideally in the form of a working example; e.g.: chmod a+x /usr/share/frobnosticator/frob.conf Put clarifying information in separate paragraphs within the step Put critical information about the whole procedure in one or more paragraphs before the numbered steps Put supplemental information about the whole procedure in one or more paragraphs after the numbered steps Avoid pronouns when writing technical articles or documentation e.g., install foo rather than install it . Avoid superfluous statements like you will want , you want , you should e.g., install foo rather than you will want to install foo . Use the imperative form in step-by-step instructions, e.g. install package foo rather than the package foo should be installed","title":"Tips for Writing Procedural Instructions"},{"location":"meetings/TechAreaTemplate/","text":"OSG Technology Area Meeting, 17 July 2017 \u00b6 Coordinates: Conference: 719-284-5267, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianB, BrianL, Carl, Derek, Edgar, Jeff, Marian, Marty, Mat, Suchandra, TimC, TimT, Xin Announcements \u00b6 Triage Duty \u00b6 This week: Next week: ( ) open tickets JIRA \u00b6 # of tickets \u0394 State 141 -17 Open 33 +9 In Progress 4 +2 Ready for Testing 0 -12 Ready for Release Release Schedule \u00b6 Name Version Development Freeze Package Freeze Release Notes August 3.4.2, 3.3.27 2017-07-24 2017-07-31 2017-08-08 September 3.4.3, 3.3.28 2017-08-28 2017-09-05 2017-09-12 5 week cycle October 3.4.4, 3.3.29 2017-09-25 2017-10-02 2017-10-10 Notes: Additional \u201curgent\u201d releases may be scheduled for the 4th Tuesday of each month. The Testing date is when acceptance testing will be scheduled for releasable packages; if a package is added after this date, it may not be possible to schedule adequate testing time, thereby forcing it into the next release. OSG Software Team \u00b6 Discussions \u00b6 Support Update \u00b6 OSG Release Team \u00b6 3.3.27 \u0394 Both \u0394 3.4.2 \u0394 Total \u0394 Status 1 +0 4 +0 2 +0 7 +0 Open 0 +0 10 +0 4 +0 14 +0 In Progress 2 +0 1 +0 1 +0 4 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +0 15 +0 7 +0 25 +0 Total Discussions \u00b6 OSG Investigations Team \u00b6 Last Week \u00b6 This Week \u00b6 Ongoing \u00b6","title":"OSG Technology Area Meeting, 17 July 2017"},{"location":"meetings/TechAreaTemplate/#osg-technology-area-meeting-17-july-2017","text":"Coordinates: Conference: 719-284-5267, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianB, BrianL, Carl, Derek, Edgar, Jeff, Marian, Marty, Mat, Suchandra, TimC, TimT, Xin","title":"OSG Technology Area Meeting, 17 July 2017"},{"location":"meetings/TechAreaTemplate/#announcements","text":"","title":"Announcements"},{"location":"meetings/TechAreaTemplate/#triage-duty","text":"This week: Next week: ( ) open tickets","title":"Triage Duty"},{"location":"meetings/TechAreaTemplate/#jira","text":"# of tickets \u0394 State 141 -17 Open 33 +9 In Progress 4 +2 Ready for Testing 0 -12 Ready for Release","title":"JIRA"},{"location":"meetings/TechAreaTemplate/#release-schedule","text":"Name Version Development Freeze Package Freeze Release Notes August 3.4.2, 3.3.27 2017-07-24 2017-07-31 2017-08-08 September 3.4.3, 3.3.28 2017-08-28 2017-09-05 2017-09-12 5 week cycle October 3.4.4, 3.3.29 2017-09-25 2017-10-02 2017-10-10 Notes: Additional \u201curgent\u201d releases may be scheduled for the 4th Tuesday of each month. The Testing date is when acceptance testing will be scheduled for releasable packages; if a package is added after this date, it may not be possible to schedule adequate testing time, thereby forcing it into the next release.","title":"Release Schedule"},{"location":"meetings/TechAreaTemplate/#osg-software-team","text":"","title":"OSG Software Team"},{"location":"meetings/TechAreaTemplate/#discussions","text":"","title":"Discussions"},{"location":"meetings/TechAreaTemplate/#support-update","text":"","title":"Support Update"},{"location":"meetings/TechAreaTemplate/#osg-release-team","text":"3.3.27 \u0394 Both \u0394 3.4.2 \u0394 Total \u0394 Status 1 +0 4 +0 2 +0 7 +0 Open 0 +0 10 +0 4 +0 14 +0 In Progress 2 +0 1 +0 1 +0 4 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +0 15 +0 7 +0 25 +0 Total","title":"OSG Release Team"},{"location":"meetings/TechAreaTemplate/#discussions_1","text":"","title":"Discussions"},{"location":"meetings/TechAreaTemplate/#osg-investigations-team","text":"","title":"OSG Investigations Team"},{"location":"meetings/TechAreaTemplate/#last-week","text":"","title":"Last Week"},{"location":"meetings/TechAreaTemplate/#this-week","text":"","title":"This Week"},{"location":"meetings/TechAreaTemplate/#ongoing","text":"","title":"Ongoing"},{"location":"meetings/2020/TechArea20200106/","text":"OSG Technology Area Meeting, 6 January 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Edgar, Diego, Marian, Marco Mambelli, Mat Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: Carl 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 162 +2 Open 35 +0 In Progress 12 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.8/3.4.42 AI (Mat): Package default XRootD standalone auth file (SOFTWARE-3951) AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Carl): HTCondor 8.9.5 and 8.8.7 releases (SOFTWARE-3929, SOFTWARE-3957) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment AI (Brian): Working on serving HTML results from osg-sw-submit web server Discussion \u00b6 None this week Support Update \u00b6 None last week OSG Release Team \u00b6 3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 1 +1 11 +11 1 +1 13 +13 Open 0 +0 4 +4 2 +2 6 +6 In Progress 1 +1 9 +9 2 +2 12 +12 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 2 +2 24 +24 5 +5 31 +31 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 3.4.42 Hosted CE Tools 0.5-2 osg-tested-internal 3.4-8 OSG XRootD 3.4-10 Ready for Release Nothing Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing Discussion \u00b6 UCSD is running the latest osg-xrootd-standalone package in production and will update the relevant tickets with testing notes AI (Diego): Test the xrootd-standalone fresh container AI (Diego, Edgar): Test XRootD 4.11.1 OSG Investigations Team \u00b6 No updates this week Discussion \u00b6 None this week","title":"January, 6 2020"},{"location":"meetings/2020/TechArea20200106/#osg-technology-area-meeting-6-january-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Edgar, Diego, Marian, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 6 January 2020"},{"location":"meetings/2020/TechArea20200106/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200106/#triage-duty","text":"This week: Mat Next week: Carl 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200106/#jira","text":"# of tickets \u0394 State 162 +2 Open 35 +0 In Progress 12 +0 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200106/#osg-software-team","text":"OSG 3.5.8/3.4.42 AI (Mat): Package default XRootD standalone auth file (SOFTWARE-3951) AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Carl): HTCondor 8.9.5 and 8.8.7 releases (SOFTWARE-3929, SOFTWARE-3957) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment AI (Brian): Working on serving HTML results from osg-sw-submit web server","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200106/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200106/#support-update","text":"None last week","title":"Support Update"},{"location":"meetings/2020/TechArea20200106/#osg-release-team","text":"3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 1 +1 11 +11 1 +1 13 +13 Open 0 +0 4 +4 2 +2 6 +6 In Progress 1 +1 9 +9 2 +2 12 +12 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 2 +2 24 +24 5 +5 31 +31 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 3.4.42 Hosted CE Tools 0.5-2 osg-tested-internal 3.4-8 OSG XRootD 3.4-10 Ready for Release Nothing Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200106/#discussion_1","text":"UCSD is running the latest osg-xrootd-standalone package in production and will update the relevant tickets with testing notes AI (Diego): Test the xrootd-standalone fresh container AI (Diego, Edgar): Test XRootD 4.11.1","title":"Discussion"},{"location":"meetings/2020/TechArea20200106/#osg-investigations-team","text":"No updates this week","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200106/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200113/","text":"OSG Technology Area Meeting, 13 January 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Marian, Tim Announcements \u00b6 Meeting canceled next week (UW on holiday for MLK Jr Day) Triage Duty \u00b6 This week: Carl Next week: Brian 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 155 -7 Open 33 -2 In Progress 21 +9 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.8/3.4.42 AI (Carl): Drop instructions for commenting out all.export /tmp (SOFTWARE-3858) OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) AI (Diego): Add osg-xrootd-standalone to osg-tested-internal (SOFTWARE-3964) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment GridFTP/GSI transition AI (Edgar): OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Generate list of registered, supported GridFTP servers (SOFTWARE-3942) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) AI (Brian): Working on serving HTML results from osg-sw-submit web server Fill out doc focus doodle poll: https://doodle.com/poll/puy4rtfnrmuvhmzx Discussion \u00b6 Carl was wondering if GRACC records had GPU information. Derek: Yes, they do. glidein-monitor is in osg-development but Marco needs to do some more testing but when it's ready, he'll send an email to interesting parties Support Update \u00b6 Purdue (Derek): Adding new sites to Topology requires mapping on the WLCG side. In the future, we need to coordinate with the WLCG if an existing site would like to change its name. GRACC (Derek): user wanted a custom GRACC dashboard but needs to coordinate with user support and FKW (Freshdesk #63926) OSG Release Team \u00b6 3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 0 -1 1 -10 0 -1 1 -12 Open 0 +0 1 -3 0 -2 1 -5 In Progress 0 -1 15 +6 5 +3 20 +8 Ready for Testing 1 +1 0 +0 0 +0 1 +1 Ready for Release 1 -1 17 -7 5 +0 23 -8 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Upcoming HTCondor 8.9.5 Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 HTCondor 8.8.7 osg-ce osg-xrootd 3.4.42 Hosted CE Tools 0.5-2 OSG XRootD 3.4-10 Ready for Release 3.4.42 osg-tested-internal 3.4-8 Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing Discussion \u00b6 AI (Diego, Edgar): Test XRootD 4.11.1 AI (TimT): Test HTCondor 8.9.5 on the ITB AI (TimT): Reach out to admins for testing of HTCondor 8.8.7 OSG Investigations Team \u00b6 Assisted user support in stashcache transition, writable and origin Moving scitokens-cpp to epel. EPEL-7 EPEL-8 GRACC transition to gracc2 Discussion \u00b6 None this week","title":"January, 13 2020"},{"location":"meetings/2020/TechArea20200113/#osg-technology-area-meeting-13-january-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Marian, Tim","title":"OSG Technology Area Meeting, 13 January 2020"},{"location":"meetings/2020/TechArea20200113/#announcements","text":"Meeting canceled next week (UW on holiday for MLK Jr Day)","title":"Announcements"},{"location":"meetings/2020/TechArea20200113/#triage-duty","text":"This week: Carl Next week: Brian 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200113/#jira","text":"# of tickets \u0394 State 155 -7 Open 33 -2 In Progress 21 +9 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200113/#osg-software-team","text":"OSG 3.5.8/3.4.42 AI (Carl): Drop instructions for commenting out all.export /tmp (SOFTWARE-3858) OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Carl): Add fetch-crl schedd cron (SOFTWARE-3912) AI (Diego): Add osg-xrootd-standalone to osg-tested-internal (SOFTWARE-3964) Hosted CE AI (Mat): Avoid duplicate WN tarball generation for multiple users (SOFTWARE-3848) AI (Carl): Issues related to cache management in condor status.sh (SOFTWARE-3930) AI (Brian): Work with the SLATE team to troubleshoot their Hosted CE deployment GridFTP/GSI transition AI (Edgar): OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Generate list of registered, supported GridFTP servers (SOFTWARE-3942) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) AI (Brian): Working on serving HTML results from osg-sw-submit web server Fill out doc focus doodle poll: https://doodle.com/poll/puy4rtfnrmuvhmzx","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200113/#discussion","text":"Carl was wondering if GRACC records had GPU information. Derek: Yes, they do. glidein-monitor is in osg-development but Marco needs to do some more testing but when it's ready, he'll send an email to interesting parties","title":"Discussion"},{"location":"meetings/2020/TechArea20200113/#support-update","text":"Purdue (Derek): Adding new sites to Topology requires mapping on the WLCG side. In the future, we need to coordinate with the WLCG if an existing site would like to change its name. GRACC (Derek): user wanted a custom GRACC dashboard but needs to coordinate with user support and FKW (Freshdesk #63926)","title":"Support Update"},{"location":"meetings/2020/TechArea20200113/#osg-release-team","text":"3.4.42 \u0394 Both \u0394 3.5.8 \u0394 Total \u0394 Status 0 -1 1 -10 0 -1 1 -12 Open 0 +0 1 -3 0 -2 1 -5 In Progress 0 -1 15 +6 5 +3 20 +8 Ready for Testing 1 +1 0 +0 0 +0 1 +1 Ready for Release 1 -1 17 -7 5 +0 23 -8 Total Software Ready for Testing 3.5.8 GridFTP 13.20-1 GSI OpenSSH 7.4p1-4.5 OSG GridFTP 3.5-4 OSG GSI OpenSSH Addons 1.0.0-3 OSG XRootD 3.5-9 (including xrootd-standalone container) Upcoming HTCondor 8.9.5 Both Gratia Probe 1.20.12 scitokens-cpp 0.4.0 VOMS 2.0.14-1.5 XRootD 4.11.1 HTCondor 8.8.7 osg-ce osg-xrootd 3.4.42 Hosted CE Tools 0.5-2 OSG XRootD 3.4-10 Ready for Release 3.4.42 osg-tested-internal 3.4-8 Data Nothing Operations osg-tested-internal 3.5-2 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200113/#discussion_1","text":"AI (Diego, Edgar): Test XRootD 4.11.1 AI (TimT): Test HTCondor 8.9.5 on the ITB AI (TimT): Reach out to admins for testing of HTCondor 8.8.7","title":"Discussion"},{"location":"meetings/2020/TechArea20200113/#osg-investigations-team","text":"Assisted user support in stashcache transition, writable and origin Moving scitokens-cpp to epel. EPEL-7 EPEL-8 GRACC transition to gracc2","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200113/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200127/","text":"OSG Technology Area Meeting, 27 January 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Derek, Diego, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Edgar 5 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 147 -3 Open 40 -1 In Progress 1 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Release osg-system-profiler 1.5.0+ (SOFTWARE-3970) Hosted CE Hosted CE containers accepting jobs and reporting to the GRACC ! Next steps: Reorganize Utah topology AI (Brian): Simplify remote user configuration (SOFTWARE-3960) Documentation for OSG Ops Push HTCondor-CE logs to ElasticSearch GridFTP/GSI transition AI (Brian, Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd Discussion \u00b6 GlidenWMS 3.6.2 release candidate expected this week Support Update \u00b6 Brown (Marian): Marian had a long meeting with them to work through some site.xml issues and they're looking to fix them XRootD < 4.9 clients have issues with a Polish CA that has an expiration time after 2038 ( https://github.com/xrootd/xrootd/issues/1110 ). OSG Release Team \u00b6 3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +1 10 +10 1 +1 12 +12 Open 2 +2 5 +5 4 +4 11 +11 In Progress 0 +0 1 +1 0 +0 1 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +3 16 +16 5 +5 24 +24 Total Software Ready for Testing 3.5.9 Nothing yet Both XCache 1.2.1 3.4.43 Nothing yet Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data IGTF 1.103 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 Scitokens-cpp is in epel. EPEL-7 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6756584348) EPEL-8 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a4bf7c5d9c) GRACC transition to gracc2 Discussion \u00b6 None this week","title":"January, 27 2020"},{"location":"meetings/2020/TechArea20200127/#osg-technology-area-meeting-27-january-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Derek, Diego, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 27 January 2020"},{"location":"meetings/2020/TechArea20200127/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200127/#triage-duty","text":"This week: Brian Next week: Edgar 5 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200127/#jira","text":"# of tickets \u0394 State 147 -3 Open 40 -1 In Progress 1 -1 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200127/#osg-software-team","text":"OSG 3.5.9/3.4.43 AI (Mat): Various osg-configure fixes/features (SOFTWARE-3382, SOFTWARE-3471, SOFTWARE-3949, SOFTWARE-3953) AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Release osg-system-profiler 1.5.0+ (SOFTWARE-3970) Hosted CE Hosted CE containers accepting jobs and reporting to the GRACC ! Next steps: Reorganize Utah topology AI (Brian): Simplify remote user configuration (SOFTWARE-3960) Documentation for OSG Ops Push HTCondor-CE logs to ElasticSearch GridFTP/GSI transition AI (Brian, Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200127/#discussion","text":"GlidenWMS 3.6.2 release candidate expected this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200127/#support-update","text":"Brown (Marian): Marian had a long meeting with them to work through some site.xml issues and they're looking to fix them XRootD < 4.9 clients have issues with a Polish CA that has an expiration time after 2038 ( https://github.com/xrootd/xrootd/issues/1110 ).","title":"Support Update"},{"location":"meetings/2020/TechArea20200127/#osg-release-team","text":"3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +1 10 +10 1 +1 12 +12 Open 2 +2 5 +5 4 +4 11 +11 In Progress 0 +0 1 +1 0 +0 1 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 3 +3 16 +16 5 +5 24 +24 Total Software Ready for Testing 3.5.9 Nothing yet Both XCache 1.2.1 3.4.43 Nothing yet Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data IGTF 1.103 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200127/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200127/#osg-investigations-team","text":"Scitokens-cpp is in epel. EPEL-7 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6756584348) EPEL-8 (formerly available from https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a4bf7c5d9c) GRACC transition to gracc2","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200127/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200203/","text":"OSG Technology Area Meeting, 3 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! Moria access is flaky, we're in touch with UW CS Lab Triage Duty \u00b6 This week: Carl Next week: Edgar 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 149 +2 Open 44 +4 In Progress 3 +2 Ready for Testing 1 +1 Ready for Release JIRA ticket reporter didn't fire this week. Numbers updated manually. OSG Software Team \u00b6 OSG 3.5.9/3.4.43 AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd Discussion \u00b6 XCache validator has a lot of non-packaged RPM dependencies as Python libs. Diego will install the dependencies into a Python virtualenv and determine which libs are needed. AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena. Support Update \u00b6 Czech Site (Marian): They had some questions about Gratia vs APEL accounting. They may follow-up with other tickets via Freshdesk. EIC (Mat): Registered new contacts, waiting on some answers from Jerome Geant4 (Marian, Carl): Need to register contacts for their OASIS repo Purdue (Derek): Completed site rename and coordination with WLCG: https://ggus.eu/index.php?mode=ticket_info&ticket_id=144769 UCSD (Carl): Provided OSG-specific patches for our version of Hadoop UFL (Brian, Derek): Issues with Slurm job statuses not updating for short-running (~10min) jobs OSG Release Team \u00b6 3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +0 11 +1 1 +0 13 +1 Open 2 +0 6 +1 3 -1 11 +0 In Progress 1 +1 4 +3 2 +2 7 +6 Ready for Testing 0 +0 1 +1 0 +0 1 +1 Ready for Release 4 +1 22 +6 6 +1 32 +8 Total Software Ready for Testing 3.5.9 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.43 osg-configure 2.5.1 Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (BrianL): coordinate Frontier Squid testing with Igor and Edgar OSG Investigations Team \u00b6 New scitokens-cpp and xrootd-scitokens. GRACC transition to gracc2 Working on SciTokens + StashCache Discussion \u00b6 None this week","title":"February 3, 2020"},{"location":"meetings/2020/TechArea20200203/#osg-technology-area-meeting-3-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Brian, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 3 February 2020"},{"location":"meetings/2020/TechArea20200203/#announcements","text":"OSG All Hands meeting registration open! Moria access is flaky, we're in touch with UW CS Lab","title":"Announcements"},{"location":"meetings/2020/TechArea20200203/#triage-duty","text":"This week: Carl Next week: Edgar 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200203/#jira","text":"# of tickets \u0394 State 149 +2 Open 44 +4 In Progress 3 +2 Ready for Testing 1 +1 Ready for Release JIRA ticket reporter didn't fire this week. Numbers updated manually.","title":"JIRA"},{"location":"meetings/2020/TechArea20200203/#osg-software-team","text":"OSG 3.5.9/3.4.43 AI (Mat): Replace custom accounting group code with HTCondor user maps (SOFTWARE-3885) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Brian): Demonstrate a HTCondor-CE/XRootD reporting to the central collector via SSL (SOFTWARE-3939, SOFTWARE-3940) Fill out doc focus doodle poll: https://doodle.com/poll/buvg5qp5aewh8vxd","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200203/#discussion","text":"XCache validator has a lot of non-packaged RPM dependencies as Python libs. Diego will install the dependencies into a Python virtualenv and determine which libs are needed. AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena.","title":"Discussion"},{"location":"meetings/2020/TechArea20200203/#support-update","text":"Czech Site (Marian): They had some questions about Gratia vs APEL accounting. They may follow-up with other tickets via Freshdesk. EIC (Mat): Registered new contacts, waiting on some answers from Jerome Geant4 (Marian, Carl): Need to register contacts for their OASIS repo Purdue (Derek): Completed site rename and coordination with WLCG: https://ggus.eu/index.php?mode=ticket_info&ticket_id=144769 UCSD (Carl): Provided OSG-specific patches for our version of Hadoop UFL (Brian, Derek): Issues with Slurm job statuses not updating for short-running (~10min) jobs","title":"Support Update"},{"location":"meetings/2020/TechArea20200203/#osg-release-team","text":"3.4.43 \u0394 Both \u0394 3.5.9 \u0394 Total \u0394 Status 1 +0 11 +1 1 +0 13 +1 Open 2 +0 6 +1 3 -1 11 +0 In Progress 1 +1 4 +3 2 +2 7 +6 Ready for Testing 0 +0 1 +1 0 +0 1 +1 Ready for Release 4 +1 22 +6 6 +1 32 +8 Total Software Ready for Testing 3.5.9 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.43 osg-configure 2.5.1 Ready for Release 3.5.9 Nothing yet Both Nothing yet 3.4.43 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200203/#discussion_1","text":"AI (BrianL): coordinate Frontier Squid testing with Igor and Edgar","title":"Discussion"},{"location":"meetings/2020/TechArea20200203/#osg-investigations-team","text":"New scitokens-cpp and xrootd-scitokens. GRACC transition to gracc2 Working on SciTokens + StashCache","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200203/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200210/","text":"OSG Technology Area Meeting, 10 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! BrianL OOO Thu-Fri Triage Duty \u00b6 This week: Edgar Next week: TimT 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 147 -2 Open 42 -2 In Progress 7 +4 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.10/3.4.44 AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Derek): Review CE -> Central Collector SSL advertising PR ( https://github.com/htcondor/htcondor-ce/pull/300 ) Discussion \u00b6 Marco expects a new GlideinWMS 3.6 and 3.7 RC expected soon AI (BrianL): Get DockerHub accounts from team AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena. Support Update \u00b6 EIC (Mat): Jerome is getting info from their admin for further registration Topology (Carl): Various contact database additions and a deletion OSG Release Team \u00b6 3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 -2 1 +0 11 -2 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 4 +0 2 +0 7 +0 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 20 -2 6 +0 30 -2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related) Discussion \u00b6 None this week","title":"February 10, 2020"},{"location":"meetings/2020/TechArea20200210/#osg-technology-area-meeting-10-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 10 February 2020"},{"location":"meetings/2020/TechArea20200210/#announcements","text":"OSG All Hands meeting registration open! BrianL OOO Thu-Fri","title":"Announcements"},{"location":"meetings/2020/TechArea20200210/#triage-duty","text":"This week: Edgar Next week: TimT 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200210/#jira","text":"# of tickets \u0394 State 147 -2 Open 42 -2 In Progress 7 +4 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200210/#osg-software-team","text":"OSG 3.5.10/3.4.44 AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build XRootD 4.11.2 (SOFTWARE-3894) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Brian): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Derek): Review CE -> Central Collector SSL advertising PR ( https://github.com/htcondor/htcondor-ce/pull/300 )","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200210/#discussion","text":"Marco expects a new GlideinWMS 3.6 and 3.7 RC expected soon AI (BrianL): Get DockerHub accounts from team AI (Carl): register two new GlideinWMS developers in Koji and SVN. Remove Lorena.","title":"Discussion"},{"location":"meetings/2020/TechArea20200210/#support-update","text":"EIC (Mat): Jerome is getting info from their admin for further registration Topology (Carl): Various contact database additions and a deletion","title":"Support Update"},{"location":"meetings/2020/TechArea20200210/#osg-release-team","text":"3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 -2 1 +0 11 -2 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 4 +0 2 +0 7 +0 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 20 -2 6 +0 30 -2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200210/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200210/#osg-investigations-team","text":"TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200210/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200217/","text":"OSG Technology Area Meeting, 17 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! UCSD out for President's day Triage Duty \u00b6 This week: TimT Next week: Mat 11 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG JIRA \u00b6 # of tickets \u0394 State 146 -1 Open 39 -3 In Progress 10 +3 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.10/3.4.44 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) Discussion \u00b6 None this week Support Update \u00b6 Florida (BrianL, Derek): Working to speed up startup of SAM test jobs in their CE; waiting on feedback Purdue (Mat): Helped debug authentication issues with their local HTCondor pool and the new OSG default authentication UIUC (Carl): Debugging quoting issues with condor blahp submission (Derek) Update WLCG report. Stalled uploader which was corrected, and fixed from happening again. OSG Release Team \u00b6 3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 +0 1 +0 11 +0 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 6 +2 2 +0 9 +2 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 22 +2 6 +0 32 +2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XRootD 4.11.2 uberftp 2.8-3 XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data HCC VOMS cert Operations Nothing Contrib Nothing Discussion \u00b6 AI (Tim): Create a JIRA ticket to automate packages ready for testing list OSG Investigations Team \u00b6 (lots of people outages) TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related) IRIS-HEP Posters! Discussion \u00b6 None this week","title":"February 17, 2020"},{"location":"meetings/2020/TechArea20200217/#osg-technology-area-meeting-17-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Mat, TimT","title":"OSG Technology Area Meeting, 17 February 2020"},{"location":"meetings/2020/TechArea20200217/#announcements","text":"OSG All Hands meeting registration open! UCSD out for President's day","title":"Announcements"},{"location":"meetings/2020/TechArea20200217/#triage-duty","text":"This week: TimT Next week: Mat 11 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Add Lauren and BrianL as watchers on any new sites interested in the OSG","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200217/#jira","text":"# of tickets \u0394 State 146 -1 Open 39 -3 In Progress 10 +3 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200217/#osg-software-team","text":"OSG 3.5.10/3.4.44 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Distribute XCache validation tool (SOFTWARE-3976) AI (Diego): Build xrootd-rucio-N2N-for-Xcache (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Diego): Review OSG XRootD standalone container (SOFTWARE-3937) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200217/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200217/#support-update","text":"Florida (BrianL, Derek): Working to speed up startup of SAM test jobs in their CE; waiting on feedback Purdue (Mat): Helped debug authentication issues with their local HTCondor pool and the new OSG default authentication UIUC (Carl): Debugging quoting issues with condor blahp submission (Derek) Update WLCG report. Stalled uploader which was corrected, and fixed from happening again.","title":"Support Update"},{"location":"meetings/2020/TechArea20200217/#osg-release-team","text":"3.4.44 \u0394 Both \u0394 3.5.10 \u0394 Total \u0394 Status 1 +0 9 +0 1 +0 11 +0 Open 2 +0 6 +0 3 +0 11 +0 In Progress 1 +0 6 +2 2 +0 9 +2 Ready for Testing 0 +0 1 +0 0 +0 1 +0 Ready for Release 4 +0 22 +2 6 +0 32 +2 Total Software Ready for Testing 3.5.10 osg-configure 3.1.1 Both XRootD 4.11.2 uberftp 2.8-3 XCache 1.2.1 osg-system-profiler 1.5.0 3.4.44 osg-configure 2.5.1 Ready for Release 3.5.10 Nothing yet Both Nothing yet 3.4.44 Nothing yet Data HCC VOMS cert Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200217/#discussion_1","text":"AI (Tim): Create a JIRA ticket to automate packages ready for testing list","title":"Discussion"},{"location":"meetings/2020/TechArea20200217/#osg-investigations-team","text":"(lots of people outages) TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 Mid-point: Working on SciTokens + StashCache (Globus transition related) IRIS-HEP Posters!","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200217/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200224/","text":"OSG Technology Area Meeting, 24 February 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 OSG All Hands meeting registration open! Carl OOO Mon-Tue BrianL and Diego at the IRIS-HEP review Wed-Fri TimT out Friday and next week, returning March 9 Triage Duty \u00b6 This week: Mat Next week: Diego 12 (+1) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 153 +7 Open 41 +2 In Progress 2 -8 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 2020 Technology Area WBS: https://docs.google.com/spreadsheets/d/1pwJXu1tWnfFrSUPXkuV-fYXJg1RLY3n50XxF85AhUT4/edit?usp=sharing InCommon subject DN format change (state abbreviation -> full state name) will result in a number of vo-client updates in the next few months so we can transition VOs Critical bug/security fix only support for OSG 3.4 starts at the beginning of next month. Double-check ticket labels for release series to build for. OSG 3.5.11 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) Discussion \u00b6 Next GlideinWMS version expected at the end of this week There were questions about how to separate the XRootD TPC transfers for production from XRootD client transfers. We think that we can get the production transfer data from FTS and subtract that from the data uploaded to get the XRootD client numbers. Support Update \u00b6 Florida (BrianL, Derek): Investigating delays in SAM test job startup Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD OSG Release Team \u00b6 3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 2 +0 12 +0 2 +0 16 +0 Open 2 +0 5 +0 5 +0 12 +0 In Progress 0 +0 1 +0 0 +0 1 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 4 +0 18 +0 7 +0 29 +0 Total Software Ready for Testing 3.5.11 Nothing yet Both XCache validation tool 3.4.45 Nothing yet Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data Nothing Operations osg-notify smart quotes Contrib Nothing Discussion \u00b6 AI (Tim): Draft OSG 3.4 Limited Support Announcement. OSG Investigations Team \u00b6 TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 - March 4th Mid-point: Working on SciTokens + StashCache (Globus transition related) Discussion \u00b6 xrootd-scitokens with XCache work will require a lot of testing and is initially targeted for Stash Caches and Origins","title":"February 24, 2020"},{"location":"meetings/2020/TechArea20200224/#osg-technology-area-meeting-24-february-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 24 February 2020"},{"location":"meetings/2020/TechArea20200224/#announcements","text":"OSG All Hands meeting registration open! Carl OOO Mon-Tue BrianL and Diego at the IRIS-HEP review Wed-Fri TimT out Friday and next week, returning March 9","title":"Announcements"},{"location":"meetings/2020/TechArea20200224/#triage-duty","text":"This week: Mat Next week: Diego 12 (+1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200224/#jira","text":"# of tickets \u0394 State 153 +7 Open 41 +2 In Progress 2 -8 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200224/#osg-software-team","text":"2020 Technology Area WBS: https://docs.google.com/spreadsheets/d/1pwJXu1tWnfFrSUPXkuV-fYXJg1RLY3n50XxF85AhUT4/edit?usp=sharing InCommon subject DN format change (state abbreviation -> full state name) will result in a number of vo-client updates in the next few months so we can transition VOs Critical bug/security fix only support for OSG 3.4 starts at the beginning of next month. Double-check ticket labels for release series to build for. OSG 3.5.11 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Edgar): Release oidc-agent and CCTools (SOFTWARE-3987, SOFTWARE-3988) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Hosted CE AI (Brian): Simplify remote user configuration (SOFTWARE-3960) AI (Brian): Documentation for OSG Ops GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200224/#discussion","text":"Next GlideinWMS version expected at the end of this week There were questions about how to separate the XRootD TPC transfers for production from XRootD client transfers. We think that we can get the production transfer data from FTS and subtract that from the data uploaded to get the XRootD client numbers.","title":"Discussion"},{"location":"meetings/2020/TechArea20200224/#support-update","text":"Florida (BrianL, Derek): Investigating delays in SAM test job startup Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD","title":"Support Update"},{"location":"meetings/2020/TechArea20200224/#osg-release-team","text":"3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 2 +0 12 +0 2 +0 16 +0 Open 2 +0 5 +0 5 +0 12 +0 In Progress 0 +0 1 +0 0 +0 1 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 4 +0 18 +0 7 +0 29 +0 Total Software Ready for Testing 3.5.11 Nothing yet Both XCache validation tool 3.4.45 Nothing yet Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data Nothing Operations osg-notify smart quotes Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200224/#discussion_1","text":"AI (Tim): Draft OSG 3.4 Limited Support Announcement.","title":"Discussion"},{"location":"meetings/2020/TechArea20200224/#osg-investigations-team","text":"TODO: New scitokens-cpp and xrootd-scitokens. Paused: GRACC transition to gracc2 - March 4th Mid-point: Working on SciTokens + StashCache (Globus transition related)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200224/#discussion_2","text":"xrootd-scitokens with XCache work will require a lot of testing and is initially targeted for Stash Caches and Origins","title":"Discussion"},{"location":"meetings/2020/TechArea20200302/","text":"OSG Technology Area Meeting, 2 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marco, Marian, Mat Announcements \u00b6 TimT OOO this week BrianL OOO Friday and next Monday Triage Duty \u00b6 This week: Diego Next week: ??? 10 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 159 +6 Open 43 +2 In Progress 2 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Did everyone get an email from Freshworks about account migration? OSG 3.5.11/3.4.45 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE Fixed some WN client and host cert/key mounting issues last week AI (Brian): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) Discussion \u00b6 AI (BrianL): Write tickets for TPC config.d and self-registration improvements UCSD and UNL aren't interested in a standalone XRootD container for the time being XCache SciTokens waiting on XRootD RC2, which is expected this week GlideinWMS 3.6.2 RC expected this week Support Update \u00b6 Florida (BrianL, Derek): Investigating delays in SAM test job startup FNAL (Marian): hitting issues with IPv6 due to reverse DNS lookups similar to what we saw at UCSD some time ago (possibly fixed in XRootD 5). For now FNL has turned off IPv6 support on the redirectors. Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD Purdue (Edgar): reinstalled the CMS XCache with all the new redirectors; had documentation requests and notes UConn (Derek): troubleshooting potential issues with yearly summaries OSG Release Team \u00b6 3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 -2 3 -9 11 +9 14 -2 Open 0 -2 2 -3 7 +2 9 -3 In Progress 1 +1 0 -1 4 +4 5 +5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 -3 5 -13 22 +15 28 -1 Total Software Ready for Testing 3.5.11 CCTools 7.0.22 CVMFS 2.7.1 oidc-agent 3.3.1 osg-oasis 16-2 XCache validation tool Both Nothing yet 3.4.45 Singularity 3.5.3 Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data vo-client 100 Operations osg-notify smart quotes Contrib Nothing Discussion \u00b6 AI (BrianL): Contact ET about OSG 3.4 end of regular support dates AI (BrianL): Write weekly ready for testing email AI (BrianL): Prepare for vo-client release Wednesday OSG Investigations Team \u00b6 scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition to gracc2 - March 4th SciTokens+XrootD requires xrootd 5.0. RC2 was suppose to be out last week, maybe this week? (from xcache meeting) Discussion \u00b6 None this week","title":"March 2, 2020"},{"location":"meetings/2020/TechArea20200302/#osg-technology-area-meeting-2-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marco, Marian, Mat","title":"OSG Technology Area Meeting, 2 March 2020"},{"location":"meetings/2020/TechArea20200302/#announcements","text":"TimT OOO this week BrianL OOO Friday and next Monday","title":"Announcements"},{"location":"meetings/2020/TechArea20200302/#triage-duty","text":"This week: Diego Next week: ??? 10 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200302/#jira","text":"# of tickets \u0394 State 159 +6 Open 43 +2 In Progress 2 +4 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200302/#osg-software-team","text":"Did everyone get an email from Freshworks about account migration? OSG 3.5.11/3.4.45 AI (Mat): Update Globus packages (SOFTWARE-3991) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE Fixed some WN client and host cert/key mounting issues last week AI (Brian): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Mat): Review contents of audit log for places where we may want to audit tokens AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200302/#discussion","text":"AI (BrianL): Write tickets for TPC config.d and self-registration improvements UCSD and UNL aren't interested in a standalone XRootD container for the time being XCache SciTokens waiting on XRootD RC2, which is expected this week GlideinWMS 3.6.2 RC expected this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200302/#support-update","text":"Florida (BrianL, Derek): Investigating delays in SAM test job startup FNAL (Marian): hitting issues with IPv6 due to reverse DNS lookups similar to what we saw at UCSD some time ago (possibly fixed in XRootD 5). For now FNL has turned off IPv6 support on the redirectors. Nebraska (Diego): Working with admins to transition Nebraska to using XRootD TPC with UCSD Purdue (Edgar): reinstalled the CMS XCache with all the new redirectors; had documentation requests and notes UConn (Derek): troubleshooting potential issues with yearly summaries","title":"Support Update"},{"location":"meetings/2020/TechArea20200302/#osg-release-team","text":"3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 -2 3 -9 11 +9 14 -2 Open 0 -2 2 -3 7 +2 9 -3 In Progress 1 +1 0 -1 4 +4 5 +5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 -3 5 -13 22 +15 28 -1 Total Software Ready for Testing 3.5.11 CCTools 7.0.22 CVMFS 2.7.1 oidc-agent 3.3.1 osg-oasis 16-2 XCache validation tool Both Nothing yet 3.4.45 Singularity 3.5.3 Ready for Release 3.5.11 Nothing yet Both Nothing yet 3.4.45 Nothing yet Data vo-client 100 Operations osg-notify smart quotes Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200302/#discussion_1","text":"AI (BrianL): Contact ET about OSG 3.4 end of regular support dates AI (BrianL): Write weekly ready for testing email AI (BrianL): Prepare for vo-client release Wednesday","title":"Discussion"},{"location":"meetings/2020/TechArea20200302/#osg-investigations-team","text":"scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition to gracc2 - March 4th SciTokens+XrootD requires xrootd 5.0. RC2 was suppose to be out last week, maybe this week? (from xcache meeting)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200302/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200309/","text":"OSG Technology Area Meeting, 9 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Mat, Carl, Edgar, Derek, Diego Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Brian 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 163 +4 Open 41 -2 In Progress 5 +3 Ready for Testing 4 +4 Ready for Release OSG Software Team \u00b6 AI (Carl): Release new VO client OSG 3.5.11/3.4.45 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) need to figure out how to get Hadoop working with the container before any Hadoop site can test it Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE AI (Brian (not here)): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Brian (not here)): Demonstrate an HTCondor-CE reporting to the central collector via SSL (SOFTWARE-3939) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) (which is blocked on XRootD RC2) Discussion \u00b6 None this week Support Update \u00b6 None this week OSG Release Team \u00b6 3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 +0 3 +0 9 -2 12 -2 Open 0 +0 2 +0 8 +1 10 +1 In Progress 0 -1 0 +0 4 +0 4 -1 Ready for Testing 1 +1 0 +0 3 +3 4 +4 Ready for Release 1 +0 5 +0 24 +2 30 +2 Total Software Ready for Testing 3.5.11 Pegasus 4.9.3 scitokens-cpp 0.5.0 CCTools 7.0.22 XCache validation tool Both Nothing yet Ready for Release 3.5.11 CVMFS 2.7.1 osg-oasis 16-2 oidc-agent 3.3.1 gsi-openssh 7.4p1-5 Both Nothing yet 3.4.45 Singularity 3.5.3 Data vo-client 101 Operations osg-notify smart quotes Contrib Nothing Sent OSG 3.4 end of regular support date email. Discussion \u00b6 None this week OSG Investigations Team \u00b6 scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released... Discussion \u00b6 None this week","title":"March 9, 2020"},{"location":"meetings/2020/TechArea20200309/#osg-technology-area-meeting-9-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: Mat, Carl, Edgar, Derek, Diego","title":"OSG Technology Area Meeting, 9 March 2020"},{"location":"meetings/2020/TechArea20200309/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200309/#triage-duty","text":"This week: Carl Next week: Brian 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200309/#jira","text":"# of tickets \u0394 State 163 +4 Open 41 -2 In Progress 5 +3 Ready for Testing 4 +4 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200309/#osg-software-team","text":"AI (Carl): Release new VO client OSG 3.5.11/3.4.45 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Diego): Build XRootD plugins for XRootD 5; RC2 expected in the next ~2 weeks (SOFTWARE-3923) Containers Need a volunteer to test the XRootD standalone container (SOFTWARE-3934) need to figure out how to get Hadoop working with the container before any Hadoop site can test it Need to enable the XCache data integrity script for CMS and ATLAS XCache Hosted CE AI (Brian (not here)): Simplify remote user configuration (SOFTWARE-3960) GridFTP/GSI transition AI (Brian (not here)): Demonstrate an HTCondor-CE reporting to the central collector via SSL (SOFTWARE-3939) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process AI (Derek): Demonstrate access to LIGO frame data with SciTokens (waiting on XCache SciTokens integration) (which is blocked on XRootD RC2)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200309/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200309/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2020/TechArea20200309/#osg-release-team","text":"3.4.45 \u0394 Both \u0394 3.5.11 \u0394 Total \u0394 Status 0 +0 3 +0 9 -2 12 -2 Open 0 +0 2 +0 8 +1 10 +1 In Progress 0 -1 0 +0 4 +0 4 -1 Ready for Testing 1 +1 0 +0 3 +3 4 +4 Ready for Release 1 +0 5 +0 24 +2 30 +2 Total Software Ready for Testing 3.5.11 Pegasus 4.9.3 scitokens-cpp 0.5.0 CCTools 7.0.22 XCache validation tool Both Nothing yet Ready for Release 3.5.11 CVMFS 2.7.1 osg-oasis 16-2 oidc-agent 3.3.1 gsi-openssh 7.4p1-5 Both Nothing yet 3.4.45 Singularity 3.5.3 Data vo-client 101 Operations osg-notify smart quotes Contrib Nothing Sent OSG 3.4 end of regular support date email.","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200309/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200309/#osg-investigations-team","text":"scitokens-cpp update in EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d247b5382c Paused: GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released...","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200309/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200316/","text":"OSG Technology Area Meeting, 16 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Edgar 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 161 -2 Open 40 -1 In Progress 2 -3 Ready for Testing 0 -4 Ready for Release OSG Software Team \u00b6 OSG 3.5.12/3.4.46 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Carl): Various blahp tickets AI (Diego): Release XRootD 4.11.3 (SOFTWARE-4017) AI (BrianL): Release HTCondor-CE (SOFTWARE-4009) AI (Derek): Update XRootD SciTokens 1.2.0 GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts Discussion \u00b6 None this week Support Update \u00b6 Nebraska (Diego): Found a bug with the Phedex download script in the production agent that fixed transfer issues Purdue (Diego): Opened a ticket because there are issues with FTS transfers OSG Release Team \u00b6 3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 5 +2 7 -2 12 +0 Open 0 +0 2 +0 9 +1 11 +1 In Progress 0 +0 0 +0 2 -2 2 -2 Ready for Testing 0 -1 0 +0 0 -3 0 -4 Ready for Release 0 -1 7 +2 18 -6 25 -5 Total Software Ready for Testing 3.5.12 scitokens-cpp 0.5.0 XCache validation tool Both Nothing yet Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 scitokens-cpp update now in EPEL stable EPEL-7 EPEL-8 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA 4030 Discussion \u00b6 None this week","title":"March 16, 2020"},{"location":"meetings/2020/TechArea20200316/#osg-technology-area-meeting-16-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Diego, Derek, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 16 March 2020"},{"location":"meetings/2020/TechArea20200316/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200316/#triage-duty","text":"This week: Brian Next week: Edgar 10 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200316/#jira","text":"# of tickets \u0394 State 161 -2 Open 40 -1 In Progress 2 -3 Ready for Testing 0 -4 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200316/#osg-software-team","text":"OSG 3.5.12/3.4.46 AI (Mat): Update default lcmaps.db to use VOMS mappings (SOFTWARE-3927) AI (Carl): Various blahp tickets AI (Diego): Release XRootD 4.11.3 (SOFTWARE-4017) AI (BrianL): Release HTCondor-CE (SOFTWARE-4009) AI (Derek): Update XRootD SciTokens 1.2.0 GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (Mat): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200316/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200316/#support-update","text":"Nebraska (Diego): Found a bug with the Phedex download script in the production agent that fixed transfer issues Purdue (Diego): Opened a ticket because there are issues with FTS transfers","title":"Support Update"},{"location":"meetings/2020/TechArea20200316/#osg-release-team","text":"3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 5 +2 7 -2 12 +0 Open 0 +0 2 +0 9 +1 11 +1 In Progress 0 +0 0 +0 2 -2 2 -2 Ready for Testing 0 -1 0 +0 0 -3 0 -4 Ready for Release 0 -1 7 +2 18 -6 25 -5 Total Software Ready for Testing 3.5.12 scitokens-cpp 0.5.0 XCache validation tool Both Nothing yet Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200316/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200316/#osg-investigations-team","text":"scitokens-cpp update now in EPEL stable EPEL-7 EPEL-8 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA 4030","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200316/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200323/","text":"OSG Technology Area Meeting, 23 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Edgar Next week: Mat 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 158 -3 Open 38 -2 In Progress 11 +9 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus this Thursday, 26 Mar at 1:30pm Central! OSG 3.5.12/3.4.46 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts Discussion \u00b6 None this week Support Update \u00b6 ALICE (Carl, Derek): they want two different facilities to report under the same name to the WLCG; investigating possibilities LIGO (Edgar, Derek): discussing OASIS manager contact registrations with LIGO management Purdue (Diego): wrote some manual tests for direct transfers and uncovered some issues that he's forwarded onto the GGUS ticket OSG Release Team \u00b6 3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 3 -2 7 +0 10 -2 Open 0 +0 3 +1 4 -5 7 -4 In Progress 0 +0 2 +2 8 +6 10 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 8 +1 19 +1 27 +2 Total Software Ready for Testing 3.5.12 HTCondor CE 4.2.1 Pegasus 4.9.3 lcmaps 1.6.6 scitokens-cpp 0.5.0 XRootD 4.11.3 (Release Candidate 2) XCache validation tool Both XRootD SciTokens 1.2.0 Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA-4030 300+ corrections latter, we are in a good place! Need to evaluate HTCondor-CE tests for availability Discussion \u00b6 None this week","title":"March 23, 2020"},{"location":"meetings/2020/TechArea20200323/#osg-technology-area-meeting-23-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Mat, TimT","title":"OSG Technology Area Meeting, 23 March 2020"},{"location":"meetings/2020/TechArea20200323/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200323/#triage-duty","text":"This week: Edgar Next week: Mat 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200323/#jira","text":"# of tickets \u0394 State 158 -3 Open 38 -2 In Progress 11 +9 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200323/#osg-software-team","text":"Doc focus this Thursday, 26 Mar at 1:30pm Central! OSG 3.5.12/3.4.46 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Edgar): Update TPC tests to use config.d configuration; add HTTP/S tests for XRootD standalone (SOFTWARE-3936) (done) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200323/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200323/#support-update","text":"ALICE (Carl, Derek): they want two different facilities to report under the same name to the WLCG; investigating possibilities LIGO (Edgar, Derek): discussing OASIS manager contact registrations with LIGO management Purdue (Diego): wrote some manual tests for direct transfers and uncovered some issues that he's forwarded onto the GGUS ticket","title":"Support Update"},{"location":"meetings/2020/TechArea20200323/#osg-release-team","text":"3.4.46 \u0394 Both \u0394 3.5.12 \u0394 Total \u0394 Status 0 +0 3 -2 7 +0 10 -2 Open 0 +0 3 +1 4 -5 7 -4 In Progress 0 +0 2 +2 8 +6 10 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 8 +1 19 +1 27 +2 Total Software Ready for Testing 3.5.12 HTCondor CE 4.2.1 Pegasus 4.9.3 lcmaps 1.6.6 scitokens-cpp 0.5.0 XRootD 4.11.3 (Release Candidate 2) XCache validation tool Both XRootD SciTokens 1.2.0 Ready for Release 3.5.12 Nothing yet Both Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200323/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200323/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/ SciTokens+XrootD requires xrootd 5.0. RC2 still not released GRACC Development for new corrections: JIRA-4030 300+ corrections latter, we are in a good place! Need to evaluate HTCondor-CE tests for availability","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200323/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200330/","text":"OSG Technology Area Meeting, 30 March 2020 \u00b6 Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, TimT Announcements \u00b6 Mat OOO today Switching meeting to Zoom next week OSG support for COVID-19 research: assign any tickets for users or sites to me and set the prio to \"Urgent\" Triage Duty \u00b6 This week: Mat Next week: TimT 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 157 -1 Open 42 +4 In Progress 11 +0 Ready for Testing 2 +2 Ready for Release OSG Software Team \u00b6 OSG 3.5.13/3.4.47 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) AI (Diego): Build XRootD-4.11.3-1.2 (SOFTWARE-4017) with redirector fix GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process AI (Edgar): Try out the self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts New OSG Software testing host (osg-sw-submit.chtc.wisc.edu) is up and ready! Next doc focus 9 Apr 2020 @ 1:30pm Discussion \u00b6 AI (Marian): Add BrianL and Andy to discussion about CMS monitoring configuration AI (Diego): Send BrianL local UCSD XRootD standalone and redirector configurations AI (BrianL): Verify non-UW Software Team access to the new OSG Software testing host Support Update \u00b6 Caltech, Nebraska (Mat): issue with missing GridFTP logs; we have a package that addresses this issue Notre Dame (Edgar): pilots landing on GPU nodes but not able to use the GPUs; we suspect that it's a wrapper script issue Purdue (Diego): saw 5-6 different issues and saw that the first two accounted for 70% of the errors. The next build of XRootD should solve the first issue and they are increasing the # of TCP connections to address the second. OSG Release Team \u00b6 3.4.47 \u0394 Both \u0394 3.5.13 \u0394 Total \u0394 Status 0 +0 0 -3 13 +6 13 +3 Open 0 +0 2 -1 5 +1 7 +0 In Progress 0 +0 1 -1 8 +0 9 -1 Ready for Testing 0 +0 0 +0 2 +2 2 +2 Ready for Release 0 +0 3 -5 28 +9 31 +4 Total Software Ready for Testing 3.5.13 XRootD 4.11.3 HTCondor CE 4.2.1 lcmaps 1.6.6 scitokens-cpp 0.5.0 XCache validation tool osg-xrootd 3.5-12 - osg standalone config Both Nothing yet Ready for Release 3.5.13 Pegasus 4.9.3 globus-gridftp-server-13.20-1.1 Both Nothing yet Data IGTF 1.105 Operations gsi-openssh-7.4p1-5 vm-test-runs-1.1-1 Contrib Nothing Discussion \u00b6 One release this week including software and CA certificates OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 78% SciTokens+XrootD requires xrootd 5.0. RC2 still not released Need to evaluate HTCondor-CE tests for availability Discussion \u00b6 None this week","title":"March 30, 2020"},{"location":"meetings/2020/TechArea20200330/#osg-technology-area-meeting-30-march-2020","text":"Coordinates: Conference: 971-292-4623, PIN: 57363; https://www.uberconference.com/osgblin Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, TimT","title":"OSG Technology Area Meeting, 30 March 2020"},{"location":"meetings/2020/TechArea20200330/#announcements","text":"Mat OOO today Switching meeting to Zoom next week OSG support for COVID-19 research: assign any tickets for users or sites to me and set the prio to \"Urgent\"","title":"Announcements"},{"location":"meetings/2020/TechArea20200330/#triage-duty","text":"This week: Mat Next week: TimT 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200330/#jira","text":"# of tickets \u0394 State 157 -1 Open 42 +4 In Progress 11 +0 Ready for Testing 2 +2 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200330/#osg-software-team","text":"OSG 3.5.13/3.4.47 AI (Carl): Various blahp tickets, including LSF status update from Jaime (?) AI (Diego): Build XRootD-4.11.3-1.2 (SOFTWARE-4017) with redirector fix GridFTP/GSI transition AI (Diego): Add option to enable the XCache data integrity script for CMS and ATLAS XCache (SOFTWARE-4026) AI (Carl): Move OASIS manager login credential information to CILogon (SOFTWARE-3947) AI (BrianL): Fix-up email templates and confusing web page for the COManage self-registration process AI (Edgar): Try out the self-registration process EL8 support AI (Mat): Test EL8 builds with new Koji hosts New OSG Software testing host (osg-sw-submit.chtc.wisc.edu) is up and ready! Next doc focus 9 Apr 2020 @ 1:30pm","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200330/#discussion","text":"AI (Marian): Add BrianL and Andy to discussion about CMS monitoring configuration AI (Diego): Send BrianL local UCSD XRootD standalone and redirector configurations AI (BrianL): Verify non-UW Software Team access to the new OSG Software testing host","title":"Discussion"},{"location":"meetings/2020/TechArea20200330/#support-update","text":"Caltech, Nebraska (Mat): issue with missing GridFTP logs; we have a package that addresses this issue Notre Dame (Edgar): pilots landing on GPU nodes but not able to use the GPUs; we suspect that it's a wrapper script issue Purdue (Diego): saw 5-6 different issues and saw that the first two accounted for 70% of the errors. The next build of XRootD should solve the first issue and they are increasing the # of TCP connections to address the second.","title":"Support Update"},{"location":"meetings/2020/TechArea20200330/#osg-release-team","text":"3.4.47 \u0394 Both \u0394 3.5.13 \u0394 Total \u0394 Status 0 +0 0 -3 13 +6 13 +3 Open 0 +0 2 -1 5 +1 7 +0 In Progress 0 +0 1 -1 8 +0 9 -1 Ready for Testing 0 +0 0 +0 2 +2 2 +2 Ready for Release 0 +0 3 -5 28 +9 31 +4 Total Software Ready for Testing 3.5.13 XRootD 4.11.3 HTCondor CE 4.2.1 lcmaps 1.6.6 scitokens-cpp 0.5.0 XCache validation tool osg-xrootd 3.5-12 - osg standalone config Both Nothing yet Ready for Release 3.5.13 Pegasus 4.9.3 globus-gridftp-server-13.20-1.1 Both Nothing yet Data IGTF 1.105 Operations gsi-openssh-7.4p1-5 vm-test-runs-1.1-1 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200330/#discussion_1","text":"One release this week including software and CA certificates","title":"Discussion"},{"location":"meetings/2020/TechArea20200330/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 78% SciTokens+XrootD requires xrootd 5.0. RC2 still not released Need to evaluate HTCondor-CE tests for availability","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200330/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200406/","text":"OSG Technology Area Meeting, 6 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 New COVID-19 site documentation available: https://osg-htc.org/docs/compute-element/covid-19/ Triage Duty \u00b6 This week: TimT Next week: Diego 9 (-2) open FreshDesk tickets 0 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 157 +0 Open 40 -2 In Progress 8 -3 Ready for Testing 0 -2 Ready for Release OSG Software Team \u00b6 COVID-19 Open Science CE AI (Mat): add POOL secret volume mount and generate a new token for Mats AI (Mat): Create a gittrac ticket for the HTCondor security session string comparison bug AI (BrianL): Advertise consistent schedd name between instances OSG 3.5.15/3.4.49 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Next doc focus 9 Apr 2020 @ 1:30pm Discussion \u00b6 AI (Edgar): Build ENMR singularity image AI (BrianL): Follow-up with Diego about running tests manually to troubleshoot XRootD 5 issues AI (BrianL): Create GlideinWMS 3.7 ticket and assign it to Edgar Diego spoke with XRootD devs about xrootd-lcmaps linked libraries. It built without the libraries so we will test to see it if it stil works. Support Update \u00b6 GlueX (Edgar): Had issues with signing VOMS attributes \u2013 will investigate with BrianL and Carl Purdue, UCSD (Diego): Having issues reproducing the XRootD failures \u2013 we decided that if there aren't regressions, we should just move forward with the release OSG Release Team \u00b6 3.4.48 \u0394 Both \u0394 3.5.14 \u0394 Total \u0394 Status 0 +0 0 +0 10 -3 10 -3 Open 0 +0 0 -2 6 +1 6 -1 In Progress 0 +0 2 +1 4 -4 6 -3 Ready for Testing 0 +0 0 +0 0 -2 0 -2 Ready for Release 0 +0 2 -1 20 -8 22 -9 Total Software Ready for Testing 3.5.14 osg-ce 3.5-5 XRootD 4.11.3 osg-xrootd 3.5-12 - osg standalone config Both Frontier Squid 4.10-3.1 Data VO Packge v103 - Wednesday Operations Nothing Contrib Nothing Discussion \u00b6 AI (Edgar): Get Igor to update to a container with the latest frontier-squid, verify it works, and tag it as stable AI (Edgar): Comment in SOFTWARE-4017 with the results of the UCSD XRootD update OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 91% SciTokens+XrootD requires xrootd 5.0. RC2 is out, in development. Need to evaluate HTCondor-CE tests for availability. Folding@Home is running on the OSG within Singularity. Discussion \u00b6 None this week","title":"April 6, 2020"},{"location":"meetings/2020/TechArea20200406/#osg-technology-area-meeting-6-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 6 April 2020"},{"location":"meetings/2020/TechArea20200406/#announcements","text":"New COVID-19 site documentation available: https://osg-htc.org/docs/compute-element/covid-19/","title":"Announcements"},{"location":"meetings/2020/TechArea20200406/#triage-duty","text":"This week: TimT Next week: Diego 9 (-2) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200406/#jira","text":"# of tickets \u0394 State 157 +0 Open 40 -2 In Progress 8 -3 Ready for Testing 0 -2 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200406/#osg-software-team","text":"COVID-19 Open Science CE AI (Mat): add POOL secret volume mount and generate a new token for Mats AI (Mat): Create a gittrac ticket for the HTCondor security session string comparison bug AI (BrianL): Advertise consistent schedd name between instances OSG 3.5.15/3.4.49 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Next doc focus 9 Apr 2020 @ 1:30pm","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200406/#discussion","text":"AI (Edgar): Build ENMR singularity image AI (BrianL): Follow-up with Diego about running tests manually to troubleshoot XRootD 5 issues AI (BrianL): Create GlideinWMS 3.7 ticket and assign it to Edgar Diego spoke with XRootD devs about xrootd-lcmaps linked libraries. It built without the libraries so we will test to see it if it stil works.","title":"Discussion"},{"location":"meetings/2020/TechArea20200406/#support-update","text":"GlueX (Edgar): Had issues with signing VOMS attributes \u2013 will investigate with BrianL and Carl Purdue, UCSD (Diego): Having issues reproducing the XRootD failures \u2013 we decided that if there aren't regressions, we should just move forward with the release","title":"Support Update"},{"location":"meetings/2020/TechArea20200406/#osg-release-team","text":"3.4.48 \u0394 Both \u0394 3.5.14 \u0394 Total \u0394 Status 0 +0 0 +0 10 -3 10 -3 Open 0 +0 0 -2 6 +1 6 -1 In Progress 0 +0 2 +1 4 -4 6 -3 Ready for Testing 0 +0 0 +0 0 -2 0 -2 Ready for Release 0 +0 2 -1 20 -8 22 -9 Total Software Ready for Testing 3.5.14 osg-ce 3.5-5 XRootD 4.11.3 osg-xrootd 3.5-12 - osg standalone config Both Frontier Squid 4.10-3.1 Data VO Packge v103 - Wednesday Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200406/#discussion_1","text":"AI (Edgar): Get Igor to update to a container with the latest frontier-squid, verify it works, and tag it as stable AI (Edgar): Comment in SOFTWARE-4017 with the results of the UCSD XRootD update","title":"Discussion"},{"location":"meetings/2020/TechArea20200406/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 91% SciTokens+XrootD requires xrootd 5.0. RC2 is out, in development. Need to evaluate HTCondor-CE tests for availability. Folding@Home is running on the OSG within Singularity.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200406/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200413/","text":"OSG Technology Area Meeting, 13 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Edgar OOO today Carl OOO Friday and next Monday Triage Duty \u00b6 This week: Diego Next week: BrianL (?) 11 (+2) open FreshDesk tickets 2 (+2) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 147 +0 Open 46 +6 In Progress 3 -5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 COVID-19 Open Science CE AI (Mat): send BrianL list of technical debt AI (BrianL): Begin work on persisting jobs across instances OSG 3.5.16/3.4.50 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Carl): Various gratia-probe tickets (SOFTWARE-3980) AI (Diego): Kick off OSG 3.4 tests for XRootD 4.11.3 for 3.4 (SOFTWARE-3056) AI (BrianL): Release GlideinWMS 3.7 (SOFTWARE-4051) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Doc focus postponed to 7 May 2020 @ 1:30pm Discussion \u00b6 None this week Support Update \u00b6 Harvester (BrianL): Worked with Harvester developers to troubleshoot an issue where clients failed to connect to the SciTokens test CE. Turned out to be an authentication failure that resulted in an unhelpful client error message. SWT2 (Carl): Continued troubleshooting missing March accounting data. UCSD (Diego): CMS load test transfers were failing due to mismatched checksums. Turned out to be a problem with the source files and HDFS checksums needing to be updated rather than an issue in the transfer itself. OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 1 +1 0 +0 10 +4 11 +5 In Progress 0 +0 0 -2 1 -3 1 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +1 0 -2 23 +3 24 +2 Total Software Ready for Testing 3.5.16 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 97% GRACC reports pruning this week. SciTokens + XCache - no progress last week. LIGO is waiting on me. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effor from Diego and Derek. Discussion \u00b6 None this week","title":"April 13, 2020"},{"location":"meetings/2020/TechArea20200413/#osg-technology-area-meeting-13-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 13 April 2020"},{"location":"meetings/2020/TechArea20200413/#announcements","text":"Edgar OOO today Carl OOO Friday and next Monday","title":"Announcements"},{"location":"meetings/2020/TechArea20200413/#triage-duty","text":"This week: Diego Next week: BrianL (?) 11 (+2) open FreshDesk tickets 2 (+2) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200413/#jira","text":"# of tickets \u0394 State 147 +0 Open 46 +6 In Progress 3 -5 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200413/#osg-software-team","text":"COVID-19 Open Science CE AI (Mat): send BrianL list of technical debt AI (BrianL): Begin work on persisting jobs across instances OSG 3.5.16/3.4.50 AI (Carl): Various blahp tickets (SOFTWARE-3995) AI (Carl): Various gratia-probe tickets (SOFTWARE-3980) AI (Diego): Kick off OSG 3.4 tests for XRootD 4.11.3 for 3.4 (SOFTWARE-3056) AI (BrianL): Release GlideinWMS 3.7 (SOFTWARE-4051) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) Doc focus postponed to 7 May 2020 @ 1:30pm","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200413/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200413/#support-update","text":"Harvester (BrianL): Worked with Harvester developers to troubleshoot an issue where clients failed to connect to the SciTokens test CE. Turned out to be an authentication failure that resulted in an unhelpful client error message. SWT2 (Carl): Continued troubleshooting missing March accounting data. UCSD (Diego): CMS load test transfers were failing due to mismatched checksums. Turned out to be a problem with the source files and HDFS checksums needing to be updated rather than an issue in the transfer itself.","title":"Support Update"},{"location":"meetings/2020/TechArea20200413/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 1 +1 0 +0 10 +4 11 +5 In Progress 0 +0 0 -2 1 -3 1 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +1 0 -2 23 +3 24 +2 Total Software Ready for Testing 3.5.16 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200413/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200413/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 97% GRACC reports pruning this week. SciTokens + XCache - no progress last week. LIGO is waiting on me. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effor from Diego and Derek.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200413/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200420/","text":"OSG Technology Area Meeting, 20 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Carl OOO today Triage Duty \u00b6 This week: BrianL Next week: Edgar 6 (-5) open FreshDesk tickets 1 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 152 -5 Open 50 +4 In Progress 3 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG Release tickets AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Mat): troubleshoot issue with EL8 builds due to dependencies being satisfied by modules instead of by repositories AI (BrianL): Begin work on persisting jobs across Open Science CE instances Discussion \u00b6 None this week Support Update \u00b6 AGLT2, BNL, MWT2 (BrianL): negotiator bug in the latest HTCondor 8.8 versions that prevent some jobs from matching when using hierarchical accounting group quotas. HTCondor team working on verifying a fix. AMNH (Derek, Edgar): now running their squid at Manhattan Internet2 node. New CE being added as well. Brown (Marian): had Webex troubleshooting session last week and will have a follow-up this week. Has some XRootD + NFS configuration that we may want to add to our own documentation. Cybera (Diego): having some issues setting up COVID-19 routes and will discuss with BrianL offline GlideinWMS (Marco, Edgar): a few proxy different proxy issues (missing pathlen, cannot generate VO proxies for a sub-vo, and proxy lifetime not getting passed along properly) that are expected to make it into the next 3.6 and 3.7 releases Purdue (Diego): was able to produce an issue similar to transfers getting stuck by setting and removing network bandwidth restrictions. Will discuss short timeouts with gfal2 client developers. Rutgers (Derek, BrianL): Issues with Accounting groups, prioritization of COVID research. OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 9 -3 9 -3 Open 1 +0 0 +0 14 +4 15 +4 In Progress 0 +0 0 +0 2 +1 2 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +0 0 +0 25 +2 26 +2 Total Software Ready for Testing 3.5.16 GlideinWMS 3.7 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) Significant GRACC reports refactor. SciTokens + XCache - no progress last week. Goal for this week. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Validation presentation this week to CMS / FNAL. Discussion \u00b6 None this week","title":"April 20, 2020"},{"location":"meetings/2020/TechArea20200420/#osg-technology-area-meeting-20-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 20 April 2020"},{"location":"meetings/2020/TechArea20200420/#announcements","text":"Carl OOO today","title":"Announcements"},{"location":"meetings/2020/TechArea20200420/#triage-duty","text":"This week: BrianL Next week: Edgar 6 (-5) open FreshDesk tickets 1 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200420/#jira","text":"# of tickets \u0394 State 152 -5 Open 50 +4 In Progress 3 +0 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200420/#osg-software-team","text":"OSG Release tickets AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Mat): troubleshoot issue with EL8 builds due to dependencies being satisfied by modules instead of by repositories AI (BrianL): Begin work on persisting jobs across Open Science CE instances","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200420/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200420/#support-update","text":"AGLT2, BNL, MWT2 (BrianL): negotiator bug in the latest HTCondor 8.8 versions that prevent some jobs from matching when using hierarchical accounting group quotas. HTCondor team working on verifying a fix. AMNH (Derek, Edgar): now running their squid at Manhattan Internet2 node. New CE being added as well. Brown (Marian): had Webex troubleshooting session last week and will have a follow-up this week. Has some XRootD + NFS configuration that we may want to add to our own documentation. Cybera (Diego): having some issues setting up COVID-19 routes and will discuss with BrianL offline GlideinWMS (Marco, Edgar): a few proxy different proxy issues (missing pathlen, cannot generate VO proxies for a sub-vo, and proxy lifetime not getting passed along properly) that are expected to make it into the next 3.6 and 3.7 releases Purdue (Diego): was able to produce an issue similar to transfers getting stuck by setting and removing network bandwidth restrictions. Will discuss short timeouts with gfal2 client developers. Rutgers (Derek, BrianL): Issues with Accounting groups, prioritization of COVID research.","title":"Support Update"},{"location":"meetings/2020/TechArea20200420/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 9 -3 9 -3 Open 1 +0 0 +0 14 +4 15 +4 In Progress 0 +0 0 +0 2 +1 2 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 1 +0 0 +0 25 +2 26 +2 Total Software Ready for Testing 3.5.16 GlideinWMS 3.7 osg-ce 3.5-5 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200420/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200420/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) Significant GRACC reports refactor. SciTokens + XCache - no progress last week. Goal for this week. Folding@Home ran at scale on the OSG. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Validation presentation this week to CMS / FNAL.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200420/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200427/","text":"OSG Technology Area Meeting, 27 April 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT Announcements \u00b6 BrianL OOO Wednesday Triage Duty \u00b6 This week: Edgar Next week: Carl 8 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 -6 Open 45 -5 In Progress 10 +7 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.16 AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): need to find testers for the EL8 WN RPM and container (we suggested LIGO and Mat, respectively). Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins Discussion \u00b6 None this week Support Update \u00b6 Alice T2 (Derek): Naming consistency with WLCG. Brown (Marian): working on Topology registration and finishing touches on remaining CMS issues Networking (Derek): Pipeline malfunctioned last week, may take surgery to recover data. SWT2 CPB (Derek): Accounting malfunction may require gratia-probe slurm surgery OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 8 -1 8 -1 Open 0 -1 0 +0 9 -5 9 -6 In Progress 0 +0 0 +0 6 +4 6 +4 Ready for Testing 1 +1 0 +0 1 +1 2 +2 Ready for Release 1 +0 0 +0 24 -1 25 -1 Total Software Ready for Testing 3.5.16 CVMFS 2.7.2 Frontier Squid 4.11-2.1 blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) SciTokens + XCache - no progress last week. Goal for this week. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure. Discussion \u00b6 None this week","title":"April 27, 2020"},{"location":"meetings/2020/TechArea20200427/#osg-technology-area-meeting-27-april-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 27 April 2020"},{"location":"meetings/2020/TechArea20200427/#announcements","text":"BrianL OOO Wednesday","title":"Announcements"},{"location":"meetings/2020/TechArea20200427/#triage-duty","text":"This week: Edgar Next week: Carl 8 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200427/#jira","text":"# of tickets \u0394 State 146 -6 Open 45 -5 In Progress 10 +7 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200427/#osg-software-team","text":"OSG 3.5.16 AI (Edgar): Release XRootD 4.12.0 (SOFTWARE-4063) AI (Diego): Troubleshoot VMU test failures with XRootD 5 (SOFTWARE-3923) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): need to find testers for the EL8 WN RPM and container (we suggested LIGO and Mat, respectively). Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200427/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200427/#support-update","text":"Alice T2 (Derek): Naming consistency with WLCG. Brown (Marian): working on Topology registration and finishing touches on remaining CMS issues Networking (Derek): Pipeline malfunctioned last week, may take surgery to recover data. SWT2 CPB (Derek): Accounting malfunction may require gratia-probe slurm surgery","title":"Support Update"},{"location":"meetings/2020/TechArea20200427/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 8 -1 8 -1 Open 0 -1 0 +0 9 -5 9 -6 In Progress 0 +0 0 +0 6 +4 6 +4 Ready for Testing 1 +1 0 +0 1 +1 2 +2 Ready for Release 1 +0 0 +0 24 -1 25 -1 Total Software Ready for Testing 3.5.16 CVMFS 2.7.2 Frontier Squid 4.11-2.1 blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200427/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200427/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 100% (within rounding error) SciTokens + XCache - no progress last week. Goal for this week. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200427/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200504/","text":"OSG Technology Area Meeting, 4 May 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 8 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 +0 Open 45 -1 In Progress 12 +2 Ready for Testing 2 +1 Ready for Release OSG Software Team \u00b6 AI (BrianL, Carl, Mat): Release IGTF CA update, making sure to test InCommon certs between EL6 and EL7 hosts OSG 3.5.17 AI (Edgar): XRootD 4.12.0 RC2 ready upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor_ce_info_status (SOFTWARE-3963) Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins Old Fermicloud VMs have old DNs, need to be rebooted for new DNs Doc focus this Thursday @ 1:30pm CDT Discussion \u00b6 AI (TimT): transition OSG Travis repos from .org to .com Support Update \u00b6 Clarkson, Old Dominion, Portland State (BrianL, Derek): engagements with new Slurm sites. Clarkson and Portland asked for examples of Slurm config \"for the OSG\", which brought up the question of whether or not we should document these recommendations. We don't want to take on the batch system support burden but this is something that sites are asking for. SWT2 (Derek): Old records are now in the GRACC, waiting for EGI numbers to be updated OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 1 -7 1 -7 Open 0 +0 0 +0 0 -9 0 -9 In Progress 0 +0 0 +0 11 +5 11 +5 Ready for Testing 1 +0 0 +0 1 +0 2 +0 Ready for Release 1 +0 0 +0 13 -11 14 -11 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 CMVFS 2.7.2 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data IGTF 1.106 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Paused while Marian is in transition to Europe. SciTokens + XCache - Lots of progress. Back and forth with XRootD devs. TLS is not well documented. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure. Discussion \u00b6 None this week","title":"May 4, 2020"},{"location":"meetings/2020/TechArea20200504/#osg-technology-area-meeting-4-may-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 4 May 2020"},{"location":"meetings/2020/TechArea20200504/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200504/#triage-duty","text":"This week: Carl Next week: Mat 8 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200504/#jira","text":"# of tickets \u0394 State 146 +0 Open 45 -1 In Progress 12 +2 Ready for Testing 2 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200504/#osg-software-team","text":"AI (BrianL, Carl, Mat): Release IGTF CA update, making sure to test InCommon certs between EL6 and EL7 hosts OSG 3.5.17 AI (Edgar): XRootD 4.12.0 RC2 ready upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Edgar): Release CCTools 7.1.0+ (SOFTWARE-4031) AI (BrianL): Release HTCondor-CE 4.2.2 AI (Carl): Release Gratia Probe 1.20.13 (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor_ce_info_status (SOFTWARE-3963) Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins Old Fermicloud VMs have old DNs, need to be rebooted for new DNs Doc focus this Thursday @ 1:30pm CDT","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200504/#discussion","text":"AI (TimT): transition OSG Travis repos from .org to .com","title":"Discussion"},{"location":"meetings/2020/TechArea20200504/#support-update","text":"Clarkson, Old Dominion, Portland State (BrianL, Derek): engagements with new Slurm sites. Clarkson and Portland asked for examples of Slurm config \"for the OSG\", which brought up the question of whether or not we should document these recommendations. We don't want to take on the batch system support burden but this is something that sites are asking for. SWT2 (Derek): Old records are now in the GRACC, waiting for EGI numbers to be updated","title":"Support Update"},{"location":"meetings/2020/TechArea20200504/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 1 -7 1 -7 Open 0 +0 0 +0 0 -9 0 -9 In Progress 0 +0 0 +0 11 +5 11 +5 Ready for Testing 1 +0 0 +0 1 +0 2 +0 Ready for Release 1 +0 0 +0 13 -11 14 -11 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 CMVFS 2.7.2 GlideinWMS 3.7 Ready for Release 3.5.16 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data IGTF 1.106 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200504/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200504/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Paused while Marian is in transition to Europe. SciTokens + XCache - Lots of progress. Back and forth with XRootD devs. TLS is not well documented. Need to figure out the singularity container pruning. XRootD monitoring collector validation is starting. Effort from Diego and Derek. Starting to create the parallel infrastructure.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200504/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200511/","text":"OSG Technology Area Meeting, 11 May 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 13 (+5) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 147 +1 Open 45 +1 In Progress 13 +1 Ready for Testing 3 +1 Ready for Release OSG Software Team \u00b6 Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins OSG 3.5.16 AI (Mat): Release HTCondor 8.8.9 and 8.9.7 (SOFTWARE-4079, SOFTWARE-4080) AI (Edgar): Release vo-client with EIC VOMS (SOFTWARE-4097) OSG 3.5.17 AI (Edgar): XRootD 4.12.0 officially released upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Carl): Release gratia-probe 1.20.13+ (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor ce info status (SOFTWARE-3963) Discussion \u00b6 Marco has some Singularity and condor_chirp fixes and updates in GlideinWMS 3.6.3 (expected in 2-3 weeks) Support Update \u00b6 Brown (Marian): waiting on a response from Brown about registering their XRootD in Topology JLab (Edgar): actively troubleshooting issues with submit hosts authenticating with different hosts with Let's Encrypt certs LIGO (Carl, Derek): followed up on some extra VO attribtues showing up in the accounting dashboards Notre Dame (Carl): answered questions about passing along AccountingGroup via the BLAH SWT2 (Derek): had to do Slurm Gratia probe surgery for Oklahoma and UTA. We're getting tired of doing this so UNL is going to pilot using the HTCondor-CE Gratia probe at their Slurm site. OSG Release Team \u00b6 3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 2 +1 2 +1 Open 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 8 -3 8 -3 Ready for Testing 1 +0 0 +0 2 +1 3 +1 Ready for Release 1 +0 0 +0 12 -1 13 -1 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 GlideinWMS 3.7 Ready for Release 3.5.16 CMVFS 2.7.2 CCTools 7.1.5 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (Carl): Create a follow-on ticket to fix the INDEX in the CA certificate packaging AI (Edgar): Test the latest Frontier Squid package via the fresh container OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - As always, very complicated... Need to figure out the singularity container pruning. Turned on garbage collection on the CVMFS repo. Cleaned up a TON of space, no longer need to worry so much about pruning. XRootD monitoring collector validation is starting. Parallel infrastructure is 90% up and running. Slurm gratia probe considerations Discussion \u00b6 None this week","title":"May 11, 2020"},{"location":"meetings/2020/TechArea20200511/#osg-technology-area-meeting-11-may-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 11 May 2020"},{"location":"meetings/2020/TechArea20200511/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200511/#triage-duty","text":"This week: Mat Next week: TimT 13 (+5) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200511/#jira","text":"# of tickets \u0394 State 147 +1 Open 45 +1 In Progress 13 +1 Ready for Testing 3 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200511/#osg-software-team","text":"Reminder: Promotion requests should include a summary of changes in the requested packages that are relevant to OSG site admins OSG 3.5.16 AI (Mat): Release HTCondor 8.8.9 and 8.9.7 (SOFTWARE-4079, SOFTWARE-4080) AI (Edgar): Release vo-client with EIC VOMS (SOFTWARE-4097) OSG 3.5.17 AI (Edgar): XRootD 4.12.0 officially released upstream (SOFTWARE-4063) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Carl): Release gratia-probe 1.20.13+ (SOFTWARE-3980) AI (Mat): Remove OSG references in HTCondor-CE view and condor ce info status (SOFTWARE-3963)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200511/#discussion","text":"Marco has some Singularity and condor_chirp fixes and updates in GlideinWMS 3.6.3 (expected in 2-3 weeks)","title":"Discussion"},{"location":"meetings/2020/TechArea20200511/#support-update","text":"Brown (Marian): waiting on a response from Brown about registering their XRootD in Topology JLab (Edgar): actively troubleshooting issues with submit hosts authenticating with different hosts with Let's Encrypt certs LIGO (Carl, Derek): followed up on some extra VO attribtues showing up in the accounting dashboards Notre Dame (Carl): answered questions about passing along AccountingGroup via the BLAH SWT2 (Derek): had to do Slurm Gratia probe surgery for Oklahoma and UTA. We're getting tired of doing this so UNL is going to pilot using the HTCondor-CE Gratia probe at their Slurm site.","title":"Support Update"},{"location":"meetings/2020/TechArea20200511/#osg-release-team","text":"3.4.50 \u0394 Both \u0394 3.5.16 \u0394 Total \u0394 Status 0 +0 0 +0 2 +1 2 +1 Open 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 8 -3 8 -3 Ready for Testing 1 +0 0 +0 2 +1 3 +1 Ready for Release 1 +0 0 +0 12 -1 13 -1 Total Software Ready for Testing 3.5.16 EL8 wn client blahp 1.18.46 hosted-ce-tools 0.6 Frontier Squid 4.11-2.1 GlideinWMS 3.7 Ready for Release 3.5.16 CMVFS 2.7.2 CCTools 7.1.5 osg-ce 3.5-5 3.4.50 XRootD 4.11.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200511/#discussion_1","text":"AI (Carl): Create a follow-on ticket to fix the INDEX in the CA certificate packaging AI (Edgar): Test the latest Frontier Squid package via the fresh container","title":"Discussion"},{"location":"meetings/2020/TechArea20200511/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - As always, very complicated... Need to figure out the singularity container pruning. Turned on garbage collection on the CVMFS repo. Cleaned up a TON of space, no longer need to worry so much about pruning. XRootD monitoring collector validation is starting. Parallel infrastructure is 90% up and running. Slurm gratia probe considerations","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200511/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200518/","text":"OSG Technology Area Meeting, 18 May 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 Next week's meeting canceled (Memorial Day) HTCondor Week Tuesday and Wednesday: https://agenda.hep.wisc.edu/event/1440/overview IRIS-HEP planning retreat next Tuesday - Thursday BrianL out Friday Triage Duty \u00b6 This week: TimT Next week: Diego 8 (-5) open FreshDesk tickets 0 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 143 -4 Open 43 -2 In Progress 16 +3 Ready for Testing 1 -2 Ready for Release OSG Software Team \u00b6 Nightly VMU tests are delayed due to image creation failures due to lack of resources. Adding retries and limits to the number of local universe jobs Please fill out the next doc focus doodle poll OSG 3.5.17 AI (Mat): Release HTCondor 8.9.7 (SOFTWARE-4080) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Mat): Update de-osgify HTCondor-CE ticket with investigation notes. We can punt on condor ce info status but not on HTCondor-CE View (SOFTWARE-3963) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Edgar): Build OASIS packages for EL8 (JIRA ticket incoming) AI (Carl): Finish up new CE emailer (SOFTWARE-4057) Discussion \u00b6 None this week Support Update \u00b6 EIC (Edgar): working on getting pilots into JLab with EIC and JLab admins; separately, planning on how to do two origins serving the same data (one at BNL and one at JLab) FNAL (Carl): abandoned tracking down UCLA Frontier Squid (not an OSG site, no longer a problem for CVMFS ops groups) Nebraska, SurfSARA (Edgar): troubleshooting various issues with authenticated CVMFS cache issues OSG Release Team \u00b6 3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +1 0 +0 7 +5 8 +6 Open 0 +0 0 +0 10 +10 10 +10 In Progress 0 +0 3 +3 10 +2 13 +5 Ready for Testing 0 -1 0 +0 1 -1 1 -2 Ready for Release 1 +0 3 +3 28 +16 32 +19 Total Software Ready for Testing 3.5.17 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 gratia-probe 1.20.13 Upcoming XRootD 5.0.0 EL8 wn client blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.17 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - Document incoming. Talking with Andy about schedules. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations Guinea Pig Nebraska Discussion \u00b6 None this week","title":"May 18, 2020"},{"location":"meetings/2020/TechArea20200518/#osg-technology-area-meeting-18-may-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 18 May 2020"},{"location":"meetings/2020/TechArea20200518/#announcements","text":"Next week's meeting canceled (Memorial Day) HTCondor Week Tuesday and Wednesday: https://agenda.hep.wisc.edu/event/1440/overview IRIS-HEP planning retreat next Tuesday - Thursday BrianL out Friday","title":"Announcements"},{"location":"meetings/2020/TechArea20200518/#triage-duty","text":"This week: TimT Next week: Diego 8 (-5) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200518/#jira","text":"# of tickets \u0394 State 143 -4 Open 43 -2 In Progress 16 +3 Ready for Testing 1 -2 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200518/#osg-software-team","text":"Nightly VMU tests are delayed due to image creation failures due to lack of resources. Adding retries and limits to the number of local universe jobs Please fill out the next doc focus doodle poll OSG 3.5.17 AI (Mat): Release HTCondor 8.9.7 (SOFTWARE-4080) AI (Diego): Release XCache 1.3+ (SOFTWARE-4047) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) AI (Mat): Update de-osgify HTCondor-CE ticket with investigation notes. We can punt on condor ce info status but not on HTCondor-CE View (SOFTWARE-3963) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Edgar): Build OASIS packages for EL8 (JIRA ticket incoming) AI (Carl): Finish up new CE emailer (SOFTWARE-4057)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200518/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200518/#support-update","text":"EIC (Edgar): working on getting pilots into JLab with EIC and JLab admins; separately, planning on how to do two origins serving the same data (one at BNL and one at JLab) FNAL (Carl): abandoned tracking down UCLA Frontier Squid (not an OSG site, no longer a problem for CVMFS ops groups) Nebraska, SurfSARA (Edgar): troubleshooting various issues with authenticated CVMFS cache issues","title":"Support Update"},{"location":"meetings/2020/TechArea20200518/#osg-release-team","text":"3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +1 0 +0 7 +5 8 +6 Open 0 +0 0 +0 10 +10 10 +10 In Progress 0 +0 3 +3 10 +2 13 +5 Ready for Testing 0 -1 0 +0 1 -1 1 -2 Ready for Release 1 +0 3 +3 28 +16 32 +19 Total Software Ready for Testing 3.5.17 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 gratia-probe 1.20.13 Upcoming XRootD 5.0.0 EL8 wn client blahp 1.18.46 GlideinWMS 3.7 Ready for Release 3.5.17 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200518/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200518/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. SciTokens + XCache - Document incoming. Talking with Andy about schedules. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations Guinea Pig Nebraska","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200518/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200601/","text":"OSG Technology Area Meeting, 1 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Mat, Marian, Marco Mambelli, TimT Announcements \u00b6 Carl OOO Mon/Tue Triage Duty \u00b6 This week: BrianL Next week: Carl 12 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 147 -1 Open 44 +1 In Progress 9 +1 Ready for Testing 11 +0 Ready for Release OSG Software Team \u00b6 BrianL working on IRIS-HEP quarterly report this week Due to the CA expiration, Koji builds from moria hang. Workaround is to hit t followed by Enter to accept the moria certificate. OSG 3.5.17 AI (Diego): Move XCache 1.4-related tickets to RFT AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Carl): Finish up new CE emailer (SOFTWARE-4057) Discussion \u00b6 None this week Support Update \u00b6 BNL (Edgar): Working on LIGO data frame data working, which is difficult because they get CVMFS config from EGI but cvmfs-x509-helper from OSG. CMS (Marco): helped troubleshoot an issue due to CA expiration over the weekend because of stale CAs in a CMS docker container FNAL (Derek): Worked to get accounting up and running on new cluster using HTCondor-CE probe with SLURM. OSGConnect (Derek): SciTokens CredMon fixes. Causing user submission issues, to top priority. OU (Derek): Helped Horst get a CE up and running on an old cluster. Though, Horst did most of the work. Syracuse (Edgar, Derek): submit host reporting records as pilots UFL (Marco): Troubleshooting issues finding local Singularity with SAM tests Utah (BrianL): Pilots fail to report back to the gWMS collector due to a bad X509_USER_CERT set by Bosco. This is due to a bad Bosco tarball from the CHTC at least 2 weeks ago so any Hosted CEs instantiated during this time may experience these same failures. OSG Release Team \u00b6 3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +0 0 +0 5 -2 6 -2 Open 0 +0 0 +0 10 +0 10 +0 In Progress 0 +0 1 -2 6 -4 7 -6 Ready for Testing 0 +0 3 +3 7 +6 10 +9 Ready for Release 1 +0 4 +1 28 +0 33 +1 Total Software Ready for Testing 3.5.17 Upcoming: HTCondor 8.9.7 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release 3.5.17 GlideinWMS 3.7 gratia-probe 1.20.13 blahp 1.18.46 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations FNAL is up and running successfully. Nebraska is next, then the world! New GRACC report for Tim sent out this morning! Investigations team is helping with IRIS-HEP Analysis cluster demo at Nebraska. BrianB and Derek are helping. Derek mostly for xcache + tokens components. Discussion \u00b6 None this week","title":"June 1, 2020"},{"location":"meetings/2020/TechArea20200601/#osg-technology-area-meeting-1-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Derek, Diego, Edgar, Mat, Marian, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 1 June 2020"},{"location":"meetings/2020/TechArea20200601/#announcements","text":"Carl OOO Mon/Tue","title":"Announcements"},{"location":"meetings/2020/TechArea20200601/#triage-duty","text":"This week: BrianL Next week: Carl 12 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200601/#jira","text":"# of tickets \u0394 State 147 -1 Open 44 +1 In Progress 9 +1 Ready for Testing 11 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200601/#osg-software-team","text":"BrianL working on IRIS-HEP quarterly report this week Due to the CA expiration, Koji builds from moria hang. Workaround is to hit t followed by Enter to accept the moria certificate. OSG 3.5.17 AI (Diego): Move XCache 1.4-related tickets to RFT AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Finish OASIS DN + SSH key endpoint (SOFTWARE-3947) AI (Carl): Finish up new CE emailer (SOFTWARE-4057)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200601/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200601/#support-update","text":"BNL (Edgar): Working on LIGO data frame data working, which is difficult because they get CVMFS config from EGI but cvmfs-x509-helper from OSG. CMS (Marco): helped troubleshoot an issue due to CA expiration over the weekend because of stale CAs in a CMS docker container FNAL (Derek): Worked to get accounting up and running on new cluster using HTCondor-CE probe with SLURM. OSGConnect (Derek): SciTokens CredMon fixes. Causing user submission issues, to top priority. OU (Derek): Helped Horst get a CE up and running on an old cluster. Though, Horst did most of the work. Syracuse (Edgar, Derek): submit host reporting records as pilots UFL (Marco): Troubleshooting issues finding local Singularity with SAM tests Utah (BrianL): Pilots fail to report back to the gWMS collector due to a bad X509_USER_CERT set by Bosco. This is due to a bad Bosco tarball from the CHTC at least 2 weeks ago so any Hosted CEs instantiated during this time may experience these same failures.","title":"Support Update"},{"location":"meetings/2020/TechArea20200601/#osg-release-team","text":"3.4.51 \u0394 Both \u0394 3.5.17 \u0394 Total \u0394 Status 1 +0 0 +0 5 -2 6 -2 Open 0 +0 0 +0 10 +0 10 +0 In Progress 0 +0 1 -2 6 -4 7 -6 Ready for Testing 0 +0 3 +3 7 +6 10 +9 Ready for Release 1 +0 4 +1 28 +0 33 +1 Total Software Ready for Testing 3.5.17 Upcoming: HTCondor 8.9.7 HTCondor 8.8.9 XRootD 4.12.1 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release 3.5.17 GlideinWMS 3.7 gratia-probe 1.20.13 blahp 1.18.46 Frontier Squid container Hosted CE container Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200601/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200601/#osg-investigations-team","text":"GRACC transition now monitored with gracc-transition website: https://gracc-transition.herokuapp.com/: 99% Marian can give status. XRootD monitoring collector validation is starting. Parallel infrastructure is 100% up and running. Slurm gratia probe considerations FNAL is up and running successfully. Nebraska is next, then the world! New GRACC report for Tim sent out this morning! Investigations team is helping with IRIS-HEP Analysis cluster demo at Nebraska. BrianB and Derek are helping. Derek mostly for xcache + tokens components.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200601/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200608/","text":"OSG Technology Area Meeting, 8 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Mat, Marian, TimT Announcements \u00b6 If you are taking Wednesday Jun 10 off for #ShutDownSTEM, please let me know and try to keep an eye on critical infrastructure or urgent items during the day Triage Duty \u00b6 This week: Carl Next week: Edgar 7 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 148 +1 Open 43 -1 In Progress 14 +5 Ready for Testing 0 -11 Ready for Release OSG Software Team \u00b6 OSG 3.5.18 AI (BrianL): Automatically remove completed jobs after 30 days (SOFTWARE-4108) AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) Discussion \u00b6 xrootd-hdfs and xrootd-lcmaps currently don't create versioned shared libs. Now that XRootD advertises its major version, it should be reflected in the plugin shared libs. AI (BrianL): create ticket for testing GFAL client for Edgar AI (BrianL): discuss Cybera CE management with Jeff and Igor AI (Diego): noticed that development label of the atlas-xcache container is old. This is expected so he should delete that label from Docker Hub and update the documentation to use fresh instead. EL8 Bosco tarballs fail to build with the new BLAHP source. We don't have a pressing need for this yet but would like this to be resolved in the HTCondor 9.0.0 release Support Update \u00b6 Bellarmine (Mat): CE wasn't accepting pilots, turned out to be an old osg-ca-certs version GLOW (Mat): GLOW cache also experienced problems due to the out-of-date osg-ca-certs. Mat will follow-up with Operations to see why check_mk tests didn't catch this JLab (Edgar): working on security questionnaires so that he can continue setting up services (also has to fill out questionnaires for BNL and FNAL) OSG Release Team \u00b6 3.4.52 \u0394 Both \u0394 3.5.18 \u0394 Total \u0394 Status 0 -1 1 +1 5 +0 6 +0 Open 0 +0 0 +0 8 -2 8 -2 In Progress 0 +0 2 +1 8 +2 10 +3 Ready for Testing 0 +0 0 -3 0 -7 0 -10 Ready for Release 0 -1 3 -1 21 -7 24 -9 Total Software Ready for Testing 3.5.18 VOMS 2.0.14-1.6 Frontier Squid 4.11-3.1 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): assign Frontier Squid, XCache, and xrootd-lcmaps tickets to Edgar so he can let us know if he's testing the latest versions in his container deployments HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required Horst has tested and verified the VOMS update OSG Investigations Team \u00b6 Derek out today Want to do gracc 2 switchover soon; will wait until Derek's back and also need (another) reindex. Discussion \u00b6 None this week","title":"June 8, 2020"},{"location":"meetings/2020/TechArea20200608/#osg-technology-area-meeting-8-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Mat, Marian, TimT","title":"OSG Technology Area Meeting, 8 June 2020"},{"location":"meetings/2020/TechArea20200608/#announcements","text":"If you are taking Wednesday Jun 10 off for #ShutDownSTEM, please let me know and try to keep an eye on critical infrastructure or urgent items during the day","title":"Announcements"},{"location":"meetings/2020/TechArea20200608/#triage-duty","text":"This week: Carl Next week: Edgar 7 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200608/#jira","text":"# of tickets \u0394 State 148 +1 Open 43 -1 In Progress 14 +5 Ready for Testing 0 -11 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200608/#osg-software-team","text":"OSG 3.5.18 AI (BrianL): Automatically remove completed jobs after 30 days (SOFTWARE-4108) AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200608/#discussion","text":"xrootd-hdfs and xrootd-lcmaps currently don't create versioned shared libs. Now that XRootD advertises its major version, it should be reflected in the plugin shared libs. AI (BrianL): create ticket for testing GFAL client for Edgar AI (BrianL): discuss Cybera CE management with Jeff and Igor AI (Diego): noticed that development label of the atlas-xcache container is old. This is expected so he should delete that label from Docker Hub and update the documentation to use fresh instead. EL8 Bosco tarballs fail to build with the new BLAHP source. We don't have a pressing need for this yet but would like this to be resolved in the HTCondor 9.0.0 release","title":"Discussion"},{"location":"meetings/2020/TechArea20200608/#support-update","text":"Bellarmine (Mat): CE wasn't accepting pilots, turned out to be an old osg-ca-certs version GLOW (Mat): GLOW cache also experienced problems due to the out-of-date osg-ca-certs. Mat will follow-up with Operations to see why check_mk tests didn't catch this JLab (Edgar): working on security questionnaires so that he can continue setting up services (also has to fill out questionnaires for BNL and FNAL)","title":"Support Update"},{"location":"meetings/2020/TechArea20200608/#osg-release-team","text":"3.4.52 \u0394 Both \u0394 3.5.18 \u0394 Total \u0394 Status 0 -1 1 +1 5 +0 6 +0 Open 0 +0 0 +0 8 -2 8 -2 In Progress 0 +0 2 +1 8 +2 10 +3 Ready for Testing 0 +0 0 -3 0 -7 0 -10 Ready for Release 0 -1 3 -1 21 -7 24 -9 Total Software Ready for Testing 3.5.18 VOMS 2.0.14-1.6 Frontier Squid 4.11-3.1 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 XCache 1.4.0 stashcache-client 5.6.1 Upcoming: XRootD 5.0.0 EL8 wn client Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200608/#discussion_1","text":"AI (TimT): assign Frontier Squid, XCache, and xrootd-lcmaps tickets to Edgar so he can let us know if he's testing the latest versions in his container deployments HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required Horst has tested and verified the VOMS update","title":"Discussion"},{"location":"meetings/2020/TechArea20200608/#osg-investigations-team","text":"Derek out today Want to do gracc 2 switchover soon; will wait until Derek's back and also need (another) reindex.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200608/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200615/","text":"OSG Technology Area Meeting, 15 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Mat, BrianL, Diego, TimT, Carl, Edgar, Marian, Marco Mambelli Announcements \u00b6 Brian giving HTCondor-CE webinar at EGI; reached out to team members for help during Q&A. Doc focus this Thursday Triage Duty \u00b6 This week: Edgar Next week: Mat 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 150 +2 Open 42 -1 In Progress 10 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.18 AI (BrianL): Release HTCondor-CE 4.3.0+ AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Waiting on review from Derek on HDFS plugin. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 There does not seem to be a new GFAL client in EPEL testing for EL 7 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages for EL8 (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) Discussion \u00b6 CentOS repos were broken Friday/weekend, causing false errors in VMU tests. BrianL sent team members filtered spreadsheets for the SW WBS; please prioritize tasks marked OVERDUE. GlideinWMS Marco found problem that when a grid universe job lands against an invalid grid resource, it remains idle forever, instead of going on hold. Try reproducing on 8.8 and send email to condor-users. Denis still working on token auth between frontend and collector; might be a good idea to do some pair programming with an OSG developer so we can help with HTCondor config etc. Support Update \u00b6 BrianL: helped AGLT2 with problem where home dir was on a shared file system and condor was incorrectly assuming the shared file system was mounted on the execute host as well as the submit host, and not doing file transfer. Edgar: helped LIGO with interpreting graphs. We have some bad names in there like how \"batch records\" are actually \"pilot records\". Also the meaning of \"dedicated\" vs \"opportunistic\" isn't obvious. Also Syracuse is listed as owned by LIGO which is wrong. Edgar should talk to Derek about making some of these easier to understand. Marco: GlideinWMS 3.7: using TOKEN auth results in tarballs that have some libraries from the OS. This should be fixed in 3.7.1. OSG Release Team \u00b6 3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 -1 5 +0 5 -1 Open 0 +0 0 +0 10 +2 10 +2 In Progress 0 +0 0 -2 4 -4 4 -6 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -3 19 -2 19 -5 Total Software Ready for Testing 3.5.19 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required OSG Investigations Team \u00b6 Derek was on slate training. GRACC 2 switch was performed today. Lots of investigation effort to figure out bottlenecks. Lots of communication with XRootD team on TLS + Tokens support. Discussion \u00b6 Edgar's student starts in July to do scale testing for HTTP third party copy. Considering testing authenticated CVMFS but might not be worth doing it until the SciTokens switch (since we'd just have to do it again).","title":"June 15, 2020"},{"location":"meetings/2020/TechArea20200615/#osg-technology-area-meeting-15-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Mat, BrianL, Diego, TimT, Carl, Edgar, Marian, Marco Mambelli","title":"OSG Technology Area Meeting, 15 June 2020"},{"location":"meetings/2020/TechArea20200615/#announcements","text":"Brian giving HTCondor-CE webinar at EGI; reached out to team members for help during Q&A. Doc focus this Thursday","title":"Announcements"},{"location":"meetings/2020/TechArea20200615/#triage-duty","text":"This week: Edgar Next week: Mat 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200615/#jira","text":"# of tickets \u0394 State 150 +2 Open 42 -1 In Progress 10 -4 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200615/#osg-software-team","text":"OSG 3.5.18 AI (BrianL): Release HTCondor-CE 4.3.0+ AI (Diego): Build XRootD 4.12.2 (SOFTWARE-4063) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Waiting on review from Derek on HDFS plugin. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 There does not seem to be a new GFAL client in EPEL testing for EL 7 AI (Edgar): Update a VO frontend to GlideinWMS 3.7 AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Enterprise Linux 8 AI (Edgar): Test built XRootD packages for EL8 (lower prio) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200615/#discussion","text":"CentOS repos were broken Friday/weekend, causing false errors in VMU tests. BrianL sent team members filtered spreadsheets for the SW WBS; please prioritize tasks marked OVERDUE. GlideinWMS Marco found problem that when a grid universe job lands against an invalid grid resource, it remains idle forever, instead of going on hold. Try reproducing on 8.8 and send email to condor-users. Denis still working on token auth between frontend and collector; might be a good idea to do some pair programming with an OSG developer so we can help with HTCondor config etc.","title":"Discussion"},{"location":"meetings/2020/TechArea20200615/#support-update","text":"BrianL: helped AGLT2 with problem where home dir was on a shared file system and condor was incorrectly assuming the shared file system was mounted on the execute host as well as the submit host, and not doing file transfer. Edgar: helped LIGO with interpreting graphs. We have some bad names in there like how \"batch records\" are actually \"pilot records\". Also the meaning of \"dedicated\" vs \"opportunistic\" isn't obvious. Also Syracuse is listed as owned by LIGO which is wrong. Edgar should talk to Derek about making some of these easier to understand. Marco: GlideinWMS 3.7: using TOKEN auth results in tarballs that have some libraries from the OS. This should be fixed in 3.7.1.","title":"Support Update"},{"location":"meetings/2020/TechArea20200615/#osg-release-team","text":"3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 -1 5 +0 5 -1 Open 0 +0 0 +0 10 +2 10 +2 In Progress 0 +0 0 -2 4 -4 4 -6 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -3 19 -2 19 -5 Total Software Ready for Testing 3.5.19 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200615/#discussion_1","text":"HTCondor 8.9.7 will be re-released this week but we need to review Jason's update instructions to publish them ourselves and/or modify the packaging so that manual interventions aren't required","title":"Discussion"},{"location":"meetings/2020/TechArea20200615/#osg-investigations-team","text":"Derek was on slate training. GRACC 2 switch was performed today. Lots of investigation effort to figure out bottlenecks. Lots of communication with XRootD team on TLS + Tokens support.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200615/#discussion_2","text":"Edgar's student starts in July to do scale testing for HTTP third party copy. Considering testing authenticated CVMFS but might not be worth doing it until the SciTokens switch (since we'd just have to do it again).","title":"Discussion"},{"location":"meetings/2020/TechArea20200622/","text":"OSG Technology Area Meeting, 22 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 151 +1 Open 36 -6 In Progress 18 +8 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Carl): Release CCTools 7.1.6+ (SOFTWARE-4132) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Also remove the XRootD version requirement that was causing upgrade issues. The changes can be tested together. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 The new client works with XRootD 4; still cannot test on XRootD 5rc4. Edgar is in communication with Andy to debug and fix. Two problems with XRootD: HTTPS is not recognized as a plugin and the proxy is being rejected. AI (Edgar): Update a VO frontend to GlideinWMS 3.7 Edgar updated the JLab frontend to GlideinWMS 3.7-1. Seems stable but there are other, unrelated issues at JLab. AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Some back and forth with Dave Dykstra, who is experiencing authorization issues. Since the data is public, it's possible that the authorization check can be dropped. Should check that it causes no privacy issues (for example). AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) The tagging will be done on the Resource level, not Resource Group; Derek will have to adjust GRACC import script appropriately, though it's low priority. Discussion \u00b6 None this week. Support Update \u00b6 None this week. OSG Release Team \u00b6 3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 -5 0 -5 Open 0 +0 0 +0 0 -10 0 -10 In Progress 0 +0 1 +1 11 +7 12 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +1 11 -8 12 -7 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 GRACC2 transition tasks are still ongoing. XRootD Monitoring Validation is ongoing, and take significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested properties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Lots of communication with XRootD team on TLS + Tokens support. Discussion \u00b6 None this week","title":"June 22, 2020"},{"location":"meetings/2020/TechArea20200622/#osg-technology-area-meeting-22-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 22 June 2020"},{"location":"meetings/2020/TechArea20200622/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20200622/#triage-duty","text":"This week: Mat Next week: TimT 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200622/#jira","text":"# of tickets \u0394 State 151 +1 Open 36 -6 In Progress 18 +8 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200622/#osg-software-team","text":"OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Carl): Release CCTools 7.1.6+ (SOFTWARE-4132) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) Also remove the XRootD version requirement that was causing upgrade issues. The changes can be tested together. GSI/GridFTP migration AI (Edgar): test new GFAL client available in EPEL testing with XRootD 4 and 5 The new client works with XRootD 4; still cannot test on XRootD 5rc4. Edgar is in communication with Andy to debug and fix. Two problems with XRootD: HTTPS is not recognized as a plugin and the proxy is being rejected. AI (Edgar): Update a VO frontend to GlideinWMS 3.7 Edgar updated the JLab frontend to GlideinWMS 3.7-1. Seems stable but there are other, unrelated issues at JLab. AI (Carl): OASIS manager + COManage endpoint (SOFTWARE-3947) Some back and forth with Dave Dykstra, who is experiencing authorization issues. Since the data is public, it's possible that the authorization check can be dropped. Should check that it causes no privacy issues (for example). AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Test built XRootD packages AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Mat): Get CentOS 8 images ready for VMU tests (SOFTWARE-4072) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) The tagging will be done on the Resource level, not Resource Group; Derek will have to adjust GRACC import script appropriately, though it's low priority.","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200622/#discussion","text":"None this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200622/#support-update","text":"None this week.","title":"Support Update"},{"location":"meetings/2020/TechArea20200622/#osg-release-team","text":"3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 -5 0 -5 Open 0 +0 0 +0 0 -10 0 -10 In Progress 0 +0 1 +1 11 +7 12 +8 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +1 11 -8 12 -7 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200622/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200622/#osg-investigations-team","text":"GRACC2 transition tasks are still ongoing. XRootD Monitoring Validation is ongoing, and take significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested properties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Lots of communication with XRootD team on TLS + Tokens support.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200622/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200629/","text":"OSG Technology Area Meeting, 29 June 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian, Derek, Diego, Marian, Mat, Edgar, TimT, Marco Mambelli Announcements \u00b6 Carl OOO today Edgar OOO Tue + Wed afternoons; Thu UCSD, UNL out Friday Mat out Friday Brian out next Mon and Tue Tim out for two weeks starting next Mon Triage Duty \u00b6 This week: TimT Next week: Diego 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 152 +1 Open 40 +4 In Progress 20 +2 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): verify the version of GFAL client you tested so we can give it karma (SOFTWARE-4120) Edgar will also test GFAL client + xrootd 5 on the same machine AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Finish doc for VM base images, separating out the effort required to building EL8 vs the rest (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) Discussion \u00b6 Support Update \u00b6 Edgar: - Georgia Tech StashCache using very old version of the packages; the error is about not being able to get an Authfile from topology. - Clas12 is registered as a project but not a VO, which was causing issues because they are sending batch records tagged with a \"Clas12\" VO. Since they are part of JLab, they should be under the JLab umbrella but they are using their own top-level VOMS attribute. Clas12 will be registered as a VO under the JLab VO in topology (similar to how DUNE is registered). Diego: - Helped Riccardo di Maria set up an XRootD dev environment. Riccardo was compiling XRootD himself, which resulted in a different version number for XRootD and this led to dependency resolution issues when installing the plugins. - Worked with JINR sysadmin to test HTTP transfers between UCSD and JINR. OSG Release Team \u00b6 3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 +0 0 +0 Open 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 1 +0 11 +0 12 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +0 12 +1 13 +1 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 OSG Investigations Team \u00b6 GRACC2 Transitioned! Still some services have not completely transitioned. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is this week. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Wroking with interested parties. No XRootD 5 RC5 yet for TLS testing Discussion \u00b6 None this week","title":"June 29, 2020"},{"location":"meetings/2020/TechArea20200629/#osg-technology-area-meeting-29-june-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian, Derek, Diego, Marian, Mat, Edgar, TimT, Marco Mambelli","title":"OSG Technology Area Meeting, 29 June 2020"},{"location":"meetings/2020/TechArea20200629/#announcements","text":"Carl OOO today Edgar OOO Tue + Wed afternoons; Thu UCSD, UNL out Friday Mat out Friday Brian out next Mon and Tue Tim out for two weeks starting next Mon","title":"Announcements"},{"location":"meetings/2020/TechArea20200629/#triage-duty","text":"This week: TimT Next week: Diego 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200629/#jira","text":"# of tickets \u0394 State 152 +1 Open 40 +4 In Progress 20 +2 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200629/#osg-software-team","text":"OSG 3.5.20 AI (Carl): Broken links on cadist web page (SOFTWARE-3874) AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Edgar): verify the version of GFAL client you tested so we can give it karma (SOFTWARE-4120) Edgar will also test GFAL client + xrootd 5 on the same machine AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Finish doc for VM base images, separating out the effort required to building EL8 vs the rest (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200629/#discussion","text":"","title":"Discussion"},{"location":"meetings/2020/TechArea20200629/#support-update","text":"Edgar: - Georgia Tech StashCache using very old version of the packages; the error is about not being able to get an Authfile from topology. - Clas12 is registered as a project but not a VO, which was causing issues because they are sending batch records tagged with a \"Clas12\" VO. Since they are part of JLab, they should be under the JLab umbrella but they are using their own top-level VOMS attribute. Clas12 will be registered as a VO under the JLab VO in topology (similar to how DUNE is registered). Diego: - Helped Riccardo di Maria set up an XRootD dev environment. Riccardo was compiling XRootD himself, which resulted in a different version number for XRootD and this led to dependency resolution issues when installing the plugins. - Worked with JINR sysadmin to test HTTP transfers between UCSD and JINR.","title":"Support Update"},{"location":"meetings/2020/TechArea20200629/#osg-release-team","text":"3.4.53 \u0394 Both \u0394 3.5.19 \u0394 Total \u0394 Status 0 +0 0 +0 0 +0 0 +0 Open 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 1 +0 11 +0 12 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 1 +0 12 +1 13 +1 Total Software Ready for Testing 3.5.19 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens 0.7 Upcoming: HTCondor 8.9.7 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200629/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2020/TechArea20200629/#osg-investigations-team","text":"GRACC2 Transitioned! Still some services have not completely transitioned. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is this week. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Wroking with interested parties. No XRootD 5 RC5 yet for TLS testing","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200629/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200706/","text":"OSG Technology Area Meeting, 6 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Marco Mambelli, Marian, Mat Announcements \u00b6 Tim out for two weeks starting today Brian out today and tomorrow Triage Duty \u00b6 This week: Diego Next week: Brian 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 155 +3 Open 45 +5 In Progress 17 -3 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Create VMU test images EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) AI (Diego): Build gfal2-plugin-xrootd for upcoming (SOFTWARE-4160) Discussion \u00b6 None. Support Update \u00b6 None. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 5 +5 5 +0 Open 0 +0 0 +0 6 +5 6 +5 In Progress 0 +0 0 -1 11 +0 11 -1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -1 22 +11 22 +9 Total Software Ready for Testing 3.5.20 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens-cpp 0.5.1 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 OSG Investigations Team \u00b6 GRACC2 Transition is complete. Two students are working with Derek: IRIS-HEP fellowship for \"Proactive site monitoring\": Using outlier analysis and ML to find problem sites from accounting data Other student is attempting to re-write stashcp in Go: statically compiled and allow for inclusion of libraries. With XRootD 5 rc5 candidate, update testbed with TLS support and upstream changes. XRootD validation: Beginning report writing. Discussion \u00b6 None this week","title":"July 6, 2020"},{"location":"meetings/2020/TechArea20200706/#osg-technology-area-meeting-6-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Marco Mambelli, Marian, Mat","title":"OSG Technology Area Meeting, 6 July 2020"},{"location":"meetings/2020/TechArea20200706/#announcements","text":"Tim out for two weeks starting today Brian out today and tomorrow","title":"Announcements"},{"location":"meetings/2020/TechArea20200706/#triage-duty","text":"This week: Diego Next week: Brian 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200706/#jira","text":"# of tickets \u0394 State 155 +3 Open 45 +5 In Progress 17 -3 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200706/#osg-software-team","text":"OSG 3.5.20 AI (Diego): Build XRootD plugin .so's based on XRootD version (SOFTWARE-4093) GSI/GridFTP migration AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Edgar to update ticket with areas of code that need to be updated AI (Mat): Create VMU test images EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (Carl): Add ability to tag CC* resources in Topology (SOFTWARE-4000) AI (Diego): Build gfal2-plugin-xrootd for upcoming (SOFTWARE-4160)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200706/#discussion","text":"None.","title":"Discussion"},{"location":"meetings/2020/TechArea20200706/#support-update","text":"None.","title":"Support Update"},{"location":"meetings/2020/TechArea20200706/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 5 +5 5 +0 Open 0 +0 0 +0 6 +5 6 +5 In Progress 0 +0 0 -1 11 +0 11 -1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 -1 22 +11 22 +9 Total Software Ready for Testing 3.5.20 HTCondor-CE 4.4.0 XRootD 4.12.3 scitokens-cpp 0.5.1 xrootd-lcmaps 1.7.7 Upcoming: XRootD 5.0.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200706/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2020/TechArea20200706/#osg-investigations-team","text":"GRACC2 Transition is complete. Two students are working with Derek: IRIS-HEP fellowship for \"Proactive site monitoring\": Using outlier analysis and ML to find problem sites from accounting data Other student is attempting to re-write stashcp in Go: statically compiled and allow for inclusion of libraries. With XRootD 5 rc5 candidate, update testbed with TLS support and upstream changes. XRootD validation: Beginning report writing.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200706/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200713/","text":"OSG Technology Area Meeting, 13 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Marco Mambelli, Mat Announcements \u00b6 Mat OOO tomorrow TimT OOO until next Monday Derek OOO next week OSG User School this week and next week Triage Duty \u00b6 This week: Edgar Next week: Carl 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 164 +9 Open 45 +5 In Progress 11 -6 Ready for Testing 10 +9 Ready for Release OSG Software Team \u00b6 OSG 3.5.20 AI (Diego): Investigate XRootD 5 VMU failures (SOFTWARE-3923) AI (Edgar): Work with XRootD developers to obtain a patch for XRootD 5 and build it in OSG Containers AI (Edgar): Review XCache default directories PR (SOFTWARE-4159) AI (Edgar): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (Edgar): Promote frontier-squid container to stable (SOFTWARE-4156) AI (Carl): Transition software base and Frontier Squid to GitHub Actions (SOFTWARE-4171, SOFTWARE-4172) Enterprise Linux 8 AI (Edgar): Test OpenSSL 1.1.1 support for xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (BrianL): Design a plan with Derek/BrianB to generate pilot records in the OSG pilot container (SOFTWARE-4169) Discussion \u00b6 The task of tagging CC resources will be performed by Hosted CE operators (for Hosted CEs) or by BrianL or delegate for other resources. Actual tagging will wait until the site's CC status is public. GlideinWMS \u00b6 Developers continuing to work on Python 3 migration Marco will build test versions of GlideinWMS into the osg-contrib repos Support Update \u00b6 Edgar working with Georgia Tech for fixing their cache; will set up a screen sharing session in order to speed up communication with admins. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 6 +1 6 +1 Open 0 +0 0 +0 8 +2 8 +2 In Progress 0 +0 0 +0 4 -7 4 -7 Ready for Testing 0 +0 0 +0 9 +9 9 +9 Ready for Release 0 +0 0 +0 27 +5 27 +5 Total Software Ready for Testing 3.5.20 osg-xrootd 3.5-13 scitokens-cpp 0.5.1 Upcoming: XRootD 5.0.0 Ready for Release HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 Edgar will check if the logging changes in osg-xrootd 3.5-13 are included in his current containers. No release this week. OSG Investigations Team \u00b6 OSG Summer School is this week, Derek is participating. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is continuing. Several patches accepted upstream. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Working with interested parties, some are slow to respond. But, Mats is happy. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list). Discussion \u00b6 None this week","title":"July 13, 2020"},{"location":"meetings/2020/TechArea20200713/#osg-technology-area-meeting-13-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 13 July 2020"},{"location":"meetings/2020/TechArea20200713/#announcements","text":"Mat OOO tomorrow TimT OOO until next Monday Derek OOO next week OSG User School this week and next week","title":"Announcements"},{"location":"meetings/2020/TechArea20200713/#triage-duty","text":"This week: Edgar Next week: Carl 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200713/#jira","text":"# of tickets \u0394 State 164 +9 Open 45 +5 In Progress 11 -6 Ready for Testing 10 +9 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200713/#osg-software-team","text":"OSG 3.5.20 AI (Diego): Investigate XRootD 5 VMU failures (SOFTWARE-3923) AI (Edgar): Work with XRootD developers to obtain a patch for XRootD 5 and build it in OSG Containers AI (Edgar): Review XCache default directories PR (SOFTWARE-4159) AI (Edgar): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (Edgar): Promote frontier-squid container to stable (SOFTWARE-4156) AI (Carl): Transition software base and Frontier Squid to GitHub Actions (SOFTWARE-4171, SOFTWARE-4172) Enterprise Linux 8 AI (Edgar): Test OpenSSL 1.1.1 support for xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (BrianL): Design a plan with Derek/BrianB to generate pilot records in the OSG pilot container (SOFTWARE-4169)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200713/#discussion","text":"The task of tagging CC resources will be performed by Hosted CE operators (for Hosted CEs) or by BrianL or delegate for other resources. Actual tagging will wait until the site's CC status is public.","title":"Discussion"},{"location":"meetings/2020/TechArea20200713/#glideinwms","text":"Developers continuing to work on Python 3 migration Marco will build test versions of GlideinWMS into the osg-contrib repos","title":"GlideinWMS"},{"location":"meetings/2020/TechArea20200713/#support-update","text":"Edgar working with Georgia Tech for fixing their cache; will set up a screen sharing session in order to speed up communication with admins.","title":"Support Update"},{"location":"meetings/2020/TechArea20200713/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 6 +1 6 +1 Open 0 +0 0 +0 8 +2 8 +2 In Progress 0 +0 0 +0 4 -7 4 -7 Ready for Testing 0 +0 0 +0 9 +9 9 +9 Ready for Release 0 +0 0 +0 27 +5 27 +5 Total Software Ready for Testing 3.5.20 osg-xrootd 3.5-13 scitokens-cpp 0.5.1 Upcoming: XRootD 5.0.0 Ready for Release HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200713/#discussion_1","text":"Edgar will check if the logging changes in osg-xrootd 3.5-13 are included in his current containers. No release this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200713/#osg-investigations-team","text":"OSG Summer School is this week, Derek is participating. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) Report writing is continuing. Several patches accepted upstream. CVMFS Singularity Sync is going to start using singularity to create the containers. Working with interested parties on testing. https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 Found some testing issues. Working with interested parties, some are slow to respond. But, Mats is happy. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list).","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200713/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200720/","text":"OSG Technology Area Meeting, 20 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT Announcements \u00b6 Derek OOO this week OSG User School ongoing this week Triage Duty \u00b6 This week: Carl Next week: BrianL 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 166 +2 Open 44 -1 In Progress 15 +4 Ready for Testing 11 +1 Ready for Release OSG Software Team \u00b6 OSG 3.5.21 AI (Diego): Add package NVR table to XRootD plugin tickets and mark RFT (SOFTWARE-4093, SOFTWARE-4137) Diego is ready to promote plugins but is waiting on a PR review for xrootd-cmstfc. AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (Diego): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (BrianL): Add XRootD 5 based XCache image builds (SOFTWARE-4181) AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) Close to working; needs cleanup and PR review. AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169) Discussion \u00b6 Ongoing storage ticket with Brown; currently it's not OSG-related troubleshooting, so it would be better served if it's tracked by CMS coordinators. Carl working on moving building container to GitHub actions; this enables us to make updates to the software-base image and have them trigger builds for all descendent images. Edgar will be working on DOMA tasks so will not have time for software work. BrianL and Marian are interested in seeing XCache-related documentation that Edgar writes. Edgar has been running an XRootD 5 cache in Sunnyvale. No problems so far but there have been auth issues reported against XRootD 5; BrianL will find the GitHub issue so Edgar can test. Support Update \u00b6 Edgar: - #65322 -- CMU is having difficulties with GridFTP and XRootD. - Multi-core pilots at Syracuse not matching; Edgar requests help from HTCondor developers, who request additional logs from Syracuse. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 1 -5 1 -5 Open 0 +0 0 +0 5 -3 5 -3 In Progress 0 +0 0 +0 4 +0 4 +0 Ready for Testing 0 +0 0 +0 10 +1 10 +1 Ready for Release 0 +0 0 +0 20 -7 20 -7 Total Software Ready for Testing 3.5.20 ATLAS and CMS XCache containers osg-xrootd 3.5-13 Upcoming: XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations osg-build 1.16.2 Frontier-Squid 4.12-2 Contrib Nothing Discussion \u00b6 Release this week. OSG Investigations Team \u00b6 Outage of personel last week, Marian was available only on Monday last week OSG Summer School is ongoing this week. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list). organizing presentation on http://gitbhub.com/xrootd/xrootd-k8s-operator on next xcache meeting, IN2P3 folks involved GRACC tape backup broke last week, investigated root cause, turned out to be FNAL issue and fixed by the end of business day on last Friday (operations effort) Discussion \u00b6 None this week","title":"July 20, 2020"},{"location":"meetings/2020/TechArea20200720/#osg-technology-area-meeting-20-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Diego, Edgar, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 20 July 2020"},{"location":"meetings/2020/TechArea20200720/#announcements","text":"Derek OOO this week OSG User School ongoing this week","title":"Announcements"},{"location":"meetings/2020/TechArea20200720/#triage-duty","text":"This week: Carl Next week: BrianL 7 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200720/#jira","text":"# of tickets \u0394 State 166 +2 Open 44 -1 In Progress 15 +4 Ready for Testing 11 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200720/#osg-software-team","text":"OSG 3.5.21 AI (Diego): Add package NVR table to XRootD plugin tickets and mark RFT (SOFTWARE-4093, SOFTWARE-4137) Diego is ready to promote plugins but is waiting on a PR review for xrootd-cmstfc. AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (Diego): Add tcmalloc to XCache containers (SOFTWARE-4166) AI (BrianL): Add XRootD 5 based XCache image builds (SOFTWARE-4181) AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) Testing via XCache not possible because Python bindings for HTCondor (for OSG) are not available yet. Edgar will test using xrootd-standalone AI (Mat): Add functioning VMU tests for EL8 (SOFTWARE-4072) Close to working; needs cleanup and PR review. AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200720/#discussion","text":"Ongoing storage ticket with Brown; currently it's not OSG-related troubleshooting, so it would be better served if it's tracked by CMS coordinators. Carl working on moving building container to GitHub actions; this enables us to make updates to the software-base image and have them trigger builds for all descendent images. Edgar will be working on DOMA tasks so will not have time for software work. BrianL and Marian are interested in seeing XCache-related documentation that Edgar writes. Edgar has been running an XRootD 5 cache in Sunnyvale. No problems so far but there have been auth issues reported against XRootD 5; BrianL will find the GitHub issue so Edgar can test.","title":"Discussion"},{"location":"meetings/2020/TechArea20200720/#support-update","text":"Edgar: - #65322 -- CMU is having difficulties with GridFTP and XRootD. - Multi-core pilots at Syracuse not matching; Edgar requests help from HTCondor developers, who request additional logs from Syracuse.","title":"Support Update"},{"location":"meetings/2020/TechArea20200720/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.20 \u0394 Total \u0394 Status 0 +0 0 +0 1 -5 1 -5 Open 0 +0 0 +0 5 -3 5 -3 In Progress 0 +0 0 +0 4 +0 4 +0 Ready for Testing 0 +0 0 +0 10 +1 10 +1 Ready for Release 0 +0 0 +0 20 -7 20 -7 Total Software Ready for Testing 3.5.20 ATLAS and CMS XCache containers osg-xrootd 3.5-13 Upcoming: XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.0 Frontier-Squid 4.12-2 CVMFS 2.7.3 / cvmfs-config-2.7.3 / osg-oasis 16-5 Data Nothing Operations osg-build 1.16.2 Frontier-Squid 4.12-2 Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200720/#discussion_1","text":"Release this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200720/#osg-investigations-team","text":"Outage of personel last week, Marian was available only on Monday last week OSG Summer School is ongoing this week. XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming, though bugs in xrootd5 are the current issue (watching xcache mailing list). organizing presentation on http://gitbhub.com/xrootd/xrootd-k8s-operator on next xcache meeting, IN2P3 folks involved GRACC tape backup broke last week, investigated root cause, turned out to be FNAL issue and fixed by the end of business day on last Friday (operations effort)","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200720/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200727/","text":"OSG Technology Area Meeting, 27 July 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL OOO next week Mat OOO Monday and Friday Doc focus doodle poll sent Triage Duty \u00b6 This week: BrianL Next week: Mat 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 167 +1 Open 41 -3 In Progress 18 +3 Ready for Testing 4 -7 Ready for Release OSG Software Team \u00b6 OSG 3.5.21 AI (Carl): Release gratia-probe 1.20.14+, create ticket for 4af0a53 (SOFTWARE-4193) AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) HTCondor in osg-development for EL8; Edgar can now build the XRootD metapackages and use them for testing AI (Diego): Release scitokens for EL8 (SOFTWARE-4126) AI (Diego): Kick off Frontier Squid EL8 VMU (SOFTWARE-4105) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (Mat, Edgar): Change osg-test tests that are marked \"el7 only\" to \"el7 and el8\" AI (Mat, TimT): Build condor 8.9 for el8 AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169) Discussion \u00b6 Marco: No Fermicloud EL8 template available yet, nor is there an ETA; admins planning to upgrade OpenNebula before starting work GlideinWMS release coming soon Support Update \u00b6 None this week OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.21 \u0394 Total \u0394 Status 0 +0 0 +0 5 +4 5 +4 Open 0 +0 0 +0 3 -2 3 -2 In Progress 0 +0 0 +0 17 +13 17 +13 Ready for Testing 0 +0 0 +0 4 -6 4 -6 Ready for Release 0 +0 0 +0 29 +9 29 +9 Total Software Ready for Testing 3.5.21 osg-wn-client 3.5-4 on EL8 stashcache-client 6.0.0 (EL8) osg-flock 1.1 osg-update-vos 1.4.0 (EL8) oidc-agent 3.3.3 xrootd-lcmaps (EL8) XRootD plugins - version matching VOMS 2.1.0 (EL8) osg-xrootd 3.5-13 - reduce logging CVMFS 2.7.3 / cvmfs-config-2.4-4 / osg-oasis 16-5 (EL8) Upcoming XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.1 osg-pki-tools 3.4.0 osg-system-profiler 1.6.0 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 Release this week. OSG Investigations Team \u00b6 Outage of personel last week, Marian was available only on Monday last week Top priority for Deigo and Derek: XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming. Discussion \u00b6 None this week","title":"July 27, 2020"},{"location":"meetings/2020/TechArea20200727/#osg-technology-area-meeting-27-july-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 27 July 2020"},{"location":"meetings/2020/TechArea20200727/#announcements","text":"BrianL OOO next week Mat OOO Monday and Friday Doc focus doodle poll sent","title":"Announcements"},{"location":"meetings/2020/TechArea20200727/#triage-duty","text":"This week: BrianL Next week: Mat 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200727/#jira","text":"# of tickets \u0394 State 167 +1 Open 41 -3 In Progress 18 +3 Ready for Testing 4 -7 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200727/#osg-software-team","text":"OSG 3.5.21 AI (Carl): Release gratia-probe 1.20.14+, create ticket for 4af0a53 (SOFTWARE-4193) AI (Carl): Fix broken cadist links in the initial HTML generation (SOFTWARE-3874) Containers AI (BrianL): Add the ability to build XCache images based on XRootD hotfixes (SOFTWARE-4151) Enterprise Linux 8 AI (Edgar): Add OpenSSL 1.1.1 support to xrootd-lcmaps (SOFTWARE-4150) HTCondor in osg-development for EL8; Edgar can now build the XRootD metapackages and use them for testing AI (Diego): Release scitokens for EL8 (SOFTWARE-4126) AI (Diego): Kick off Frontier Squid EL8 VMU (SOFTWARE-4105) AI (Mat): Build osg-wn-client tarball (SOFTWARE-4050) AI (TimT): Release condor for el8 (SOFTWARE-4157) AI (Mat, Edgar): Change osg-test tests that are marked \"el7 only\" to \"el7 and el8\" AI (Mat, TimT): Build condor 8.9 for el8 AI (BrianL, Carl): Write design doc for generating pilot records for OSG pilot containers (SOFTWARE-4169)","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200727/#discussion","text":"Marco: No Fermicloud EL8 template available yet, nor is there an ETA; admins planning to upgrade OpenNebula before starting work GlideinWMS release coming soon","title":"Discussion"},{"location":"meetings/2020/TechArea20200727/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2020/TechArea20200727/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.21 \u0394 Total \u0394 Status 0 +0 0 +0 5 +4 5 +4 Open 0 +0 0 +0 3 -2 3 -2 In Progress 0 +0 0 +0 17 +13 17 +13 Ready for Testing 0 +0 0 +0 4 -6 4 -6 Ready for Release 0 +0 0 +0 29 +9 29 +9 Total Software Ready for Testing 3.5.21 osg-wn-client 3.5-4 on EL8 stashcache-client 6.0.0 (EL8) osg-flock 1.1 osg-update-vos 1.4.0 (EL8) oidc-agent 3.3.3 xrootd-lcmaps (EL8) XRootD plugins - version matching VOMS 2.1.0 (EL8) osg-xrootd 3.5-13 - reduce logging CVMFS 2.7.3 / cvmfs-config-2.4-4 / osg-oasis 16-5 (EL8) Upcoming XRootD 5.0.0 Ready for Release scitokens-cpp 0.5.1 HTCondor-CE 4.4.1 osg-pki-tools 3.4.0 osg-system-profiler 1.6.0 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200727/#discussion_1","text":"Release this week.","title":"Discussion"},{"location":"meetings/2020/TechArea20200727/#osg-investigations-team","text":"Outage of personel last week, Marian was available only on Monday last week Top priority for Deigo and Derek: XRootD Monitoring Validation is ongoing, and taking significant amount of time (and development / bugfixes) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. XRootD 5 release and built in OSG. Preparing TLS configurations for upstreaming.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200727/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200803/","text":"OSG Technology Area Meeting, 3 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Edgar, Marian, Tim Announcements \u00b6 BrianL OOO this week Mat OOO Monday Carl OOO Thursday Triage Duty \u00b6 This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 166 -1 Open 41 +0 In Progress 20 +2 Ready for Testing 0 -4 Ready for Release OSG Software Team \u00b6 AI (Derek): XCache 1.5.0 breaks osg-test tests and docker-xcache CI (preventing image tag updates!), probably due to hardcoded Authfiles in the tests of both: https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache_origin.sh#L10 https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache.sh#L9 https://github.com/opensciencegrid/osg-test/blob/master/osgtest/tests/test_155_stashcache.py#L81-L100 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Doc Focus scheduled for August 13 1:30pm CDT Discussion \u00b6 Derek: scitokens-cpp is already in EPEL 7 and 8. Do we need it in OSG 3.5? Support Update \u00b6 Edgar: Helping SDSC with some CC* grant work OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 7 +2 7 +2 Open 0 +0 0 +0 6 +3 6 +3 In Progress 0 +0 0 +0 12 -5 12 -5 Ready for Testing 0 +0 0 +0 0 -4 0 -4 Ready for Release 0 +0 0 +0 25 -4 25 -4 Total Software Ready for Testing 3.5.21 oidc-agent 3.3.3 XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 XRootD 5.0.0 is ready for release OSG Investigations Team \u00b6 Validation document is in \"Draft\" CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. Derek needs help with XCache test failures. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. Discussion \u00b6 None this week","title":"August 3, 2020"},{"location":"meetings/2020/TechArea20200803/#osg-technology-area-meeting-3-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Derek, Diego, Edgar, Marian, Tim","title":"OSG Technology Area Meeting, 3 August 2020"},{"location":"meetings/2020/TechArea20200803/#announcements","text":"BrianL OOO this week Mat OOO Monday Carl OOO Thursday","title":"Announcements"},{"location":"meetings/2020/TechArea20200803/#triage-duty","text":"This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200803/#jira","text":"# of tickets \u0394 State 166 -1 Open 41 +0 In Progress 20 +2 Ready for Testing 0 -4 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200803/#osg-software-team","text":"AI (Derek): XCache 1.5.0 breaks osg-test tests and docker-xcache CI (preventing image tag updates!), probably due to hardcoded Authfiles in the tests of both: https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache_origin.sh#L10 https://github.com/opensciencegrid/docker-xcache/blob/master/tests/test_stashcache.sh#L9 https://github.com/opensciencegrid/osg-test/blob/master/osgtest/tests/test_155_stashcache.py#L81-L100 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Doc Focus scheduled for August 13 1:30pm CDT","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200803/#discussion","text":"Derek: scitokens-cpp is already in EPEL 7 and 8. Do we need it in OSG 3.5?","title":"Discussion"},{"location":"meetings/2020/TechArea20200803/#support-update","text":"Edgar: Helping SDSC with some CC* grant work","title":"Support Update"},{"location":"meetings/2020/TechArea20200803/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 7 +2 7 +2 Open 0 +0 0 +0 6 +3 6 +3 In Progress 0 +0 0 +0 12 -5 12 -5 Ready for Testing 0 +0 0 +0 0 -4 0 -4 Ready for Release 0 +0 0 +0 25 -4 25 -4 Total Software Ready for Testing 3.5.21 oidc-agent 3.3.3 XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200803/#discussion_1","text":"XRootD 5.0.0 is ready for release","title":"Discussion"},{"location":"meetings/2020/TechArea20200803/#osg-investigations-team","text":"Validation document is in \"Draft\" CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. Derek needs help with XCache test failures. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200803/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200810/","text":"OSG Technology Area Meeting, 10 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Doc focus this Thursday starting at 13:30 CDT OSG All Hands Aug 31 - Sep 3 Release of vo-client as soon as possible today because of SLAC VOMS server cert expiration Triage Duty \u00b6 This week: TimT Next week: Diego 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 165 -1 Open 41 +0 In Progress 19 -1 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 AI: Carl - Release IGTF certs today. This includes EL8 builds. AI: Carl - Tracking CC* GPU jobs (in progress). AI: Mat - Update osg-test to handle StashCache and SciTokens integration. AI: Diego - Build scitokens packages for EL8. This includes scitokens-credmon for EL8, which requires Python 3 support. AI: Diego - Run VMU tests for frontier squid. Edgar tested XCache for XRootD 4 in EL8; it needed condor and blahp built for EL8 but it is successfully running. AI: Edgar - Send BrianL an rpm -qa dump to help get a list of all the packages that were touched. Edgar tested XCache 1.5.0 but found some issues; will make a PR. TimT - built HTCondor 8.9 in upcoming for EL8; will make a patch to fix permission issues that cause RPM verification to fail. BLAHP needs to built for upcoming; BrianL will investigate if there are any related tickets. Discussion \u00b6 None this week Support Update \u00b6 TimT: Received a ticket for XRootD Ceph support; will route it to BrianL. Edgar: Wesley Smith at JLab is installing the origin and has some questions about the documentation, specifically about Topology registration. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 8 +1 8 +1 Open 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 11 -1 11 -1 Ready for Testing 0 +0 0 +0 1 +1 1 +1 Ready for Release 0 +0 0 +0 26 +1 26 +1 Total Software Ready for Testing 3.5.22 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data VO Package v107 IGTF 1.107 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 XRootD Validation document is in \"Draft\" (Will go out this week) (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. We have a prototype, who would like to play with it? Proactive site monitoring is progressing nicely. May present at operations meeting this week. Discussion \u00b6 None this week","title":"August 10, 2020"},{"location":"meetings/2020/TechArea20200810/#osg-technology-area-meeting-10-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 10 August 2020"},{"location":"meetings/2020/TechArea20200810/#announcements","text":"Doc focus this Thursday starting at 13:30 CDT OSG All Hands Aug 31 - Sep 3 Release of vo-client as soon as possible today because of SLAC VOMS server cert expiration","title":"Announcements"},{"location":"meetings/2020/TechArea20200810/#triage-duty","text":"This week: TimT Next week: Diego 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200810/#jira","text":"# of tickets \u0394 State 165 -1 Open 41 +0 In Progress 19 -1 Ready for Testing 1 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200810/#osg-software-team","text":"Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 AI: Carl - Release IGTF certs today. This includes EL8 builds. AI: Carl - Tracking CC* GPU jobs (in progress). AI: Mat - Update osg-test to handle StashCache and SciTokens integration. AI: Diego - Build scitokens packages for EL8. This includes scitokens-credmon for EL8, which requires Python 3 support. AI: Diego - Run VMU tests for frontier squid. Edgar tested XCache for XRootD 4 in EL8; it needed condor and blahp built for EL8 but it is successfully running. AI: Edgar - Send BrianL an rpm -qa dump to help get a list of all the packages that were touched. Edgar tested XCache 1.5.0 but found some issues; will make a PR. TimT - built HTCondor 8.9 in upcoming for EL8; will make a patch to fix permission issues that cause RPM verification to fail. BLAHP needs to built for upcoming; BrianL will investigate if there are any related tickets.","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200810/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200810/#support-update","text":"TimT: Received a ticket for XRootD Ceph support; will route it to BrianL. Edgar: Wesley Smith at JLab is installing the origin and has some questions about the documentation, specifically about Topology registration.","title":"Support Update"},{"location":"meetings/2020/TechArea20200810/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 8 +1 8 +1 Open 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 11 -1 11 -1 Ready for Testing 0 +0 0 +0 1 +1 1 +1 Ready for Release 0 +0 0 +0 26 +1 26 +1 Total Software Ready for Testing 3.5.22 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data VO Package v107 IGTF 1.107 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200810/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200810/#osg-investigations-team","text":"XRootD Validation document is in \"Draft\" (Will go out this week) (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. We have a prototype, who would like to play with it? Proactive site monitoring is progressing nicely. May present at operations meeting this week.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200810/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200817/","text":"OSG Technology Area Meeting, 17 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, TimT Announcements \u00b6 OSG All Hands Aug 31 - Sep 3 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Mat OOO today Triage Duty \u00b6 This week: Diego Next week: BrianL (???) 8 (+0) open FreshDesk tickets 1 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 169 +4 Open 1 +1 Selected for Dev 27 -14 In Progress 6 +6 Dev Complete 20 +1 Ready for Testing 2 +1 Ready for Release OSG Software Team \u00b6 Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 AI (BrianL): Revisit Carl's plate AI (Edgar): Finish up bookkeeping for EL8 tickets; kick off tests for GlideinWMS 3.6.3 AI (Diego): Kick off builds for the XRootD 4.12.4 RC1 AI (TimT): Build HTCondor 8.8.10 for 3.4; also release GlideinWMS for 3.4 Support Update \u00b6 Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Still investigating. Marco suggested checking with the factory + frontend to see if they've set an aggressive pilot expiration time University of Florida (BrianL): Dynamic WN env functionality broke with a blahp update to 1.18.46. Bockjoo needed to update his configuration from blah.config.rpmnew OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +2 10 +2 Open 0 +0 0 +0 0 +0 0 +0 Selected for Development 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 2 +2 2 +2 Development Complete 0 +0 0 +0 14 +3 14 +3 Ready for Testing 0 +0 0 +0 1 +0 1 +0 Ready for Release 0 +0 0 +0 33 +7 33 +7 Total Software Ready for Testing 3.5.22 HTCondor 8.8.10 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 XRootD Validation document is released: (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. Added cvmfs and check for xrootd functionality. Proactive site monitoring is progressing nicely. Goal: Present this week GPUs for Folding@Home took some debugging with Mats, but as of this morning, seem to be working great. Discussion \u00b6 None this week","title":"August 17, 2020"},{"location":"meetings/2020/TechArea20200817/#osg-technology-area-meeting-17-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, TimT","title":"OSG Technology Area Meeting, 17 August 2020"},{"location":"meetings/2020/TechArea20200817/#announcements","text":"OSG All Hands Aug 31 - Sep 3 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Mat OOO today","title":"Announcements"},{"location":"meetings/2020/TechArea20200817/#triage-duty","text":"This week: Diego Next week: BrianL (???) 8 (+0) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200817/#jira","text":"# of tickets \u0394 State 169 +4 Open 1 +1 Selected for Dev 27 -14 In Progress 6 +6 Dev Complete 20 +1 Ready for Testing 2 +1 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200817/#osg-software-team","text":"Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200817/#discussion","text":"AI (BrianL): Revisit Carl's plate AI (Edgar): Finish up bookkeeping for EL8 tickets; kick off tests for GlideinWMS 3.6.3 AI (Diego): Kick off builds for the XRootD 4.12.4 RC1 AI (TimT): Build HTCondor 8.8.10 for 3.4; also release GlideinWMS for 3.4","title":"Discussion"},{"location":"meetings/2020/TechArea20200817/#support-update","text":"Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Still investigating. Marco suggested checking with the factory + frontend to see if they've set an aggressive pilot expiration time University of Florida (BrianL): Dynamic WN env functionality broke with a blahp update to 1.18.46. Bockjoo needed to update his configuration from blah.config.rpmnew","title":"Support Update"},{"location":"meetings/2020/TechArea20200817/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +2 10 +2 Open 0 +0 0 +0 0 +0 0 +0 Selected for Development 0 +0 0 +0 6 +0 6 +0 In Progress 0 +0 0 +0 2 +2 2 +2 Development Complete 0 +0 0 +0 14 +3 14 +3 Ready for Testing 0 +0 0 +0 1 +0 1 +0 Ready for Release 0 +0 0 +0 33 +7 33 +7 Total Software Ready for Testing 3.5.22 HTCondor 8.8.10 gratia-probe-1.20.14 tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.0 Ready for Release oidc-agent 3.3.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200817/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200817/#osg-investigations-team","text":"XRootD Validation document is released: (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation, may want some help with \"evaluating\" it as a replacement for stashcp. Added cvmfs and check for xrootd functionality. Proactive site monitoring is progressing nicely. Goal: Present this week GPUs for Folding@Home took some debugging with Mats, but as of this morning, seem to be working great.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200817/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200824/","text":"OSG Technology Area Meeting, 24 August 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T Announcements \u00b6 OSG All Hands Aug 31 - Sep 4 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Register ASAP! https://osg-htc.org/all-hands/2020/registration/ Triage Duty \u00b6 This week: BrianL Next week: Carl 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 173 +4 Open 7 +6 Selected for Dev 14 -13 In Progress 7 +1 Dev Complete 32 +12 Ready for Testing 2 +0 Ready for Release OSG Software Team \u00b6 Next doc focus Sep 17 13:30 - 17:30 CDT Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 AI (Diego): Continue to build and scitokens packages for EL8. Contact Jason Patton for software help. AI (Edgar): Build scitokens-issuer for EL8; Derek to merge pull request and make a new release. AI (Edgar): Build osg-gridftp for EL8 since osg-xrootd-standalone is blocked by osg-configure. Support Update \u00b6 JLab (BrianL): Walked the admin through setting up an Origin container. Topology registration is done; Derek will work on CVMFS. JLab will have their own CVMFS endpoint at jlab.opensciencegrid.org, with per-experiment directories. Takeaway: we really need to improve the container so that it's easier to test before Topology registration. Our current policy is to require registration before installing the software; we will revisit the policy. Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Investigating with the HTCondor team. Edgar: Working on giving UC-Irvine a hosted CE on SLATE. Also planning to set up a hosted CE for EXPANSE, but needs to do it without SLATE. Martin Kandes has complained about the install instructions for the worker node client. Brian L would like additional information; for a hosted CE, the site admin shouldn't have to install worker node client. Marco Mambelli: Planning to release glideinWMS 3.6.3; there is a known issue with a missing dependency in the spec file, which will be fixed in the next release. glideinWMS 3.7.1-rc1 has been released. Tim T: Built Bosco tarballs for EL8 per Ops request for Clemson. OSG Release Team \u00b6 3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +0 10 +0 Open 0 +0 0 +0 2 +2 2 +2 Selected for Development 0 +0 0 +0 1 -5 1 -5 In Progress 0 +0 0 +0 1 -1 1 -1 Development Complete 0 +0 0 +0 16 +2 16 +2 Ready for Testing 0 +0 1 +1 5 +4 5 +4 Ready for Release 0 +0 1 +1 35 +2 36 +3 Total Software Ready for Testing 3.5.22 XCache 1.5.2 xrootd-scitokens 1.2.2 Bunch of EL8 stuff tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.1 Ready for Release oidc-agent 3.3.3 HTCondor 8.8.10 gratia-probe-1.20.14 blahp 1.18.47 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 (No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation is ongoing. Proactive site monitoring is progressing nicely. Presented last week at Ops, good feedback! UNL's production cache is 5.0.1, with SciTokens enabled. Discussion \u00b6 Tim T discovered that the HTCondor Campus Factory subpackage is broken; was wondering what it was, and if it was still in use, or required for BOSCO. Derek (original author) said it was a way for campuses to set up a mini-Glidein Factory. bosco_cluster has callouts to it but they can be removed with minimal effort.","title":"August 24, 2020"},{"location":"meetings/2020/TechArea20200824/#osg-technology-area-meeting-24-august-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Carl, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 24 August 2020"},{"location":"meetings/2020/TechArea20200824/#announcements","text":"OSG All Hands Aug 31 - Sep 4 Technology section: 1:30-3pm CDT Wed session 2, Sep 2 Edgar giving StashCache talk, BrianB giving overview talk Register ASAP! https://osg-htc.org/all-hands/2020/registration/","title":"Announcements"},{"location":"meetings/2020/TechArea20200824/#triage-duty","text":"This week: BrianL Next week: Carl 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200824/#jira","text":"# of tickets \u0394 State 173 +4 Open 7 +6 Selected for Dev 14 -13 In Progress 7 +1 Dev Complete 32 +12 Ready for Testing 2 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200824/#osg-software-team","text":"Next doc focus Sep 17 13:30 - 17:30 CDT Register with the OSG COManage: https://osg-htc.org/register Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200824/#discussion","text":"AI (Diego): Continue to build and scitokens packages for EL8. Contact Jason Patton for software help. AI (Edgar): Build scitokens-issuer for EL8; Derek to merge pull request and make a new release. AI (Edgar): Build osg-gridftp for EL8 since osg-xrootd-standalone is blocked by osg-configure.","title":"Discussion"},{"location":"meetings/2020/TechArea20200824/#support-update","text":"JLab (BrianL): Walked the admin through setting up an Origin container. Topology registration is done; Derek will work on CVMFS. JLab will have their own CVMFS endpoint at jlab.opensciencegrid.org, with per-experiment directories. Takeaway: we really need to improve the container so that it's easier to test before Topology registration. Our current policy is to require registration before installing the software; we will revisit the policy. Vanderbilt (BrianL): Pilots being killed by the CE after 8 hours (shortly after a proxy renewal). Investigating with the HTCondor team. Edgar: Working on giving UC-Irvine a hosted CE on SLATE. Also planning to set up a hosted CE for EXPANSE, but needs to do it without SLATE. Martin Kandes has complained about the install instructions for the worker node client. Brian L would like additional information; for a hosted CE, the site admin shouldn't have to install worker node client. Marco Mambelli: Planning to release glideinWMS 3.6.3; there is a known issue with a missing dependency in the spec file, which will be fixed in the next release. glideinWMS 3.7.1-rc1 has been released. Tim T: Built Bosco tarballs for EL8 per Ops request for Clemson.","title":"Support Update"},{"location":"meetings/2020/TechArea20200824/#osg-release-team","text":"3.4.54 \u0394 Both \u0394 3.5.22 \u0394 Total \u0394 Status 0 +0 0 +0 10 +0 10 +0 Open 0 +0 0 +0 2 +2 2 +2 Selected for Development 0 +0 0 +0 1 -5 1 -5 In Progress 0 +0 0 +0 1 -1 1 -1 Development Complete 0 +0 0 +0 16 +2 16 +2 Ready for Testing 0 +0 1 +1 5 +4 5 +4 Ready for Release 0 +0 1 +1 35 +2 36 +3 Total Software Ready for Testing 3.5.22 XCache 1.5.2 xrootd-scitokens 1.2.2 Bunch of EL8 stuff tcmalloc in OSG XCaches xrootd-lcmaps 1.7.8: OpenSSL 1.1.1 support XRootD plugins - version matching Upcoming: HTCondor 8.9.8 Upcoming: XRootD 5.0.1 Ready for Release oidc-agent 3.3.3 HTCondor 8.8.10 gratia-probe-1.20.14 blahp 1.18.47 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200824/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200824/#osg-investigations-team","text":"(No-progress) CVMFS Singularity Sync is going to start using singularity to create the containers. Working on testing, see github discussion: https://github.com/opensciencegrid/cvmfs-singularity-sync/issues/245 More feedback from interested parties and they seem to be happy. Will provide feedback when Derek is back from vacation. StashCP Go implementation is ongoing. Proactive site monitoring is progressing nicely. Presented last week at Ops, good feedback! UNL's production cache is 5.0.1, with SciTokens enabled.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200824/#discussion_2","text":"Tim T discovered that the HTCondor Campus Factory subpackage is broken; was wondering what it was, and if it was still in use, or required for BOSCO. Derek (original author) said it was a way for campuses to set up a mini-Glidein Factory. bosco_cluster has callouts to it but they can be removed with minimal effort.","title":"Discussion"},{"location":"meetings/2020/TechArea20200914/","text":"OSG Technology Area Meeting, 14 September 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T Announcements \u00b6 Next week's meeting canceled (HTCondor Week Europe) PATh grant has been awarded! Triage Duty \u00b6 This week: Mat Next week: Diego 8 (+1) open FreshDesk tickets 3 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 166 +2 Open 12 -4 Selected for Dev 14 -1 In Progress 5 +1 Dev Complete 23 +4 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Doc focus Sep 17 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 UCSD team members (Edgar, Diego) will be moving to the GIL project, which is primarily involved in network and software performance testing; they will continue to provide OSG Software effort until the end of October. AI (Diego): Build XRootD 5.0.2 rc1 for upcoming. Build python-scitokens. AI (Edgar): Release vo-client in time for this week's release. Review and merge documentation PR about prescribed xcache locations. Present Data Lake talk at WLCG meeting tomorrow. AI (Mat): Build osg-configure once Python 3 conversion PR is merged. Continue to work on OIDC auth for Topology. Write talks for HTCondor Week Europe. Marco Mambelli: - Working on GWMS 3.7 release candidate and GWMS 3.6.4. - Troubleshooting condor_chirp issue with Marco Mascheroni. Support Update \u00b6 Georgia State (BrianL): investigated Hosted CE SSH issues (in progress) Georgia Tech (BrianL): assisted with their self-deployed SLATE Hosted CE with Lincoln + Judith Swinburne University (BrianL): setting up a new Hosted CE for them via the CHTC Tiger k8s cluster LHCb @ MIT (Derek): Usage is still not showing up. May be related first to EGI portal problems, which caused them to restart it, which caused it to not get the topology information because wrong URL. belle2 @ BNL (Derek): Not showing up as well, may be related to EGI portal and now topology problems. CalTech (Edgar): Working with Justas to help him set up xrootd-multiuser with checksums, but running into a bug in xrootd/xrootd-multiuser that gives the wrong checksums. Running into GWMS problems after upgrading the HTCondor central manager to 8.9; will debug with Marco. CMU (Mat): gfal-ls ticket given to Wei, but waiting on debug information; Mat will ping user. Cesga (Mat): script trying to contact Topology via the old iu.edu address. Mat will help them switch over to the current address. OSG Release Team \u00b6 3.4.55 \u0394 Both \u0394 3.5.24 \u0394 Total \u0394 Status 0 +0 0 +0 11 +1 11 +1 Open 0 +0 0 +0 1 -1 1 -1 Selected for Development 0 +0 0 +0 3 +2 3 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 7 -9 7 -9 Ready for Testing 0 +0 0 -1 1 -4 1 -5 Ready for Release 0 +0 0 -1 24 -11 24 -12 Total Software Ready for Testing 3.5.24 hosted-ce-tools 0.8-2 stashcache-client 6.1.0 XRootD 4.12.4 CCTools 7.1.1 EL8: Frontier Squid 4.12-2.1 EL8: lcmaps 1.6.6 Upcoming XRootD 5.0.1-1.4 (xrootd4 compat packages) Ready for Release 3.5.24 CVMFS 2.7.4 Data VO Package v108 Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 CVMFS singularity building is now in production! StashCP Go implementation is ongoing. Discussion \u00b6 Planning to upgrade XCache redirectors to XRootD 5 and change the config to require cache<->redirector commuication to use TLS. This will break XRootD 4 caches; almost all caches have been moved to XRootD 5, except for ItalianGrid. Edgar will get in touch with them.","title":"September 14, 2020"},{"location":"meetings/2020/TechArea20200914/#osg-technology-area-meeting-14-september-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Brian L, Derek, Diego, Edgar, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 14 September 2020"},{"location":"meetings/2020/TechArea20200914/#announcements","text":"Next week's meeting canceled (HTCondor Week Europe) PATh grant has been awarded!","title":"Announcements"},{"location":"meetings/2020/TechArea20200914/#triage-duty","text":"This week: Mat Next week: Diego 8 (+1) open FreshDesk tickets 3 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200914/#jira","text":"# of tickets \u0394 State 166 +2 Open 12 -4 Selected for Dev 14 -1 In Progress 5 +1 Dev Complete 23 +4 Ready for Testing 1 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200914/#osg-software-team","text":"Doc focus Sep 17 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200914/#discussion","text":"UCSD team members (Edgar, Diego) will be moving to the GIL project, which is primarily involved in network and software performance testing; they will continue to provide OSG Software effort until the end of October. AI (Diego): Build XRootD 5.0.2 rc1 for upcoming. Build python-scitokens. AI (Edgar): Release vo-client in time for this week's release. Review and merge documentation PR about prescribed xcache locations. Present Data Lake talk at WLCG meeting tomorrow. AI (Mat): Build osg-configure once Python 3 conversion PR is merged. Continue to work on OIDC auth for Topology. Write talks for HTCondor Week Europe. Marco Mambelli: - Working on GWMS 3.7 release candidate and GWMS 3.6.4. - Troubleshooting condor_chirp issue with Marco Mascheroni.","title":"Discussion"},{"location":"meetings/2020/TechArea20200914/#support-update","text":"Georgia State (BrianL): investigated Hosted CE SSH issues (in progress) Georgia Tech (BrianL): assisted with their self-deployed SLATE Hosted CE with Lincoln + Judith Swinburne University (BrianL): setting up a new Hosted CE for them via the CHTC Tiger k8s cluster LHCb @ MIT (Derek): Usage is still not showing up. May be related first to EGI portal problems, which caused them to restart it, which caused it to not get the topology information because wrong URL. belle2 @ BNL (Derek): Not showing up as well, may be related to EGI portal and now topology problems. CalTech (Edgar): Working with Justas to help him set up xrootd-multiuser with checksums, but running into a bug in xrootd/xrootd-multiuser that gives the wrong checksums. Running into GWMS problems after upgrading the HTCondor central manager to 8.9; will debug with Marco. CMU (Mat): gfal-ls ticket given to Wei, but waiting on debug information; Mat will ping user. Cesga (Mat): script trying to contact Topology via the old iu.edu address. Mat will help them switch over to the current address.","title":"Support Update"},{"location":"meetings/2020/TechArea20200914/#osg-release-team","text":"3.4.55 \u0394 Both \u0394 3.5.24 \u0394 Total \u0394 Status 0 +0 0 +0 11 +1 11 +1 Open 0 +0 0 +0 1 -1 1 -1 Selected for Development 0 +0 0 +0 3 +2 3 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 7 -9 7 -9 Ready for Testing 0 +0 0 -1 1 -4 1 -5 Ready for Release 0 +0 0 -1 24 -11 24 -12 Total Software Ready for Testing 3.5.24 hosted-ce-tools 0.8-2 stashcache-client 6.1.0 XRootD 4.12.4 CCTools 7.1.1 EL8: Frontier Squid 4.12-2.1 EL8: lcmaps 1.6.6 Upcoming XRootD 5.0.1-1.4 (xrootd4 compat packages) Ready for Release 3.5.24 CVMFS 2.7.4 Data VO Package v108 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200914/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200914/#osg-investigations-team","text":"CVMFS singularity building is now in production! StashCP Go implementation is ongoing.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20200914/#discussion_2","text":"Planning to upgrade XCache redirectors to XRootD 5 and change the config to require cache<->redirector commuication to use TLS. This will break XRootD 4 caches; almost all caches have been moved to XRootD 5, except for ItalianGrid. Edgar will get in touch with them.","title":"Discussion"},{"location":"meetings/2020/TechArea20200928/","text":"OSG Technology Area Meeting, 28 September 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Diego, Edgar, Marco Mambelli, Mat, Tim T Announcements \u00b6 None this week. Triage Duty \u00b6 This week: Tim T Carl to send out email for the next rotation. 7 (-1) open FreshDesk tickets 3 (+0) open GGUS tickets JIRA \u00b6 # of tickets \u0394 State 166 +0 Open 15 +3 Selected for Dev 15 +1 In Progress 4 -1 Dev Complete 17 -6 Ready for Testing 6 +5 Ready for Release OSG Software Team \u00b6 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 None. Support Update \u00b6 Edgar: StashCache at PIC upgraded to the upcoming-fresh version but it's broken for them. Edgar is troubleshooting; will reach out to XRootD developers for assistance. The symptom is an SSL permission denied, but the error only shows up in XRootD 5 and goes away when they downgrade. GlideinWMS News \u00b6 Marco Mascheroni testing 3.6.4 in the ITB. (This will be in OSG 3.4 and OSG 3.5.) 3.9 now in osg-contrib (this includes Python 3 support). Continuing work on 3.7; integrating some work from the recent tokens hackathon. OSG Release Team \u00b6 3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 0 +0 10 -1 10 -1 Open 0 +0 0 +0 3 +2 3 +2 Selected for Development 0 +0 0 +0 1 -2 1 -2 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 1 +1 4 -3 5 -2 Ready for Testing 1 +1 0 +0 0 -1 1 +0 Ready for Release 1 +1 1 +1 18 -6 20 -4 Total Software Ready for Testing Both GlideinWMS 3.6.4 3.5.25 blahp 1.18.48 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 Next week we have the stashcp-go presentation. Tackling some GRACC technical debt (RabbitMQ library changed a lot between versions) IRIS-HEP Fellows presentation today Converted perfsonar ingesters over to K8s Much work on perfsonar collector. Now using multi-processing, and a thread pool (DNS lookup are slow!) Consulting on the gratia probe for containers","title":"September 28, 2020"},{"location":"meetings/2020/TechArea20200928/#osg-technology-area-meeting-28-september-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: Carl, Diego, Edgar, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 28 September 2020"},{"location":"meetings/2020/TechArea20200928/#announcements","text":"None this week.","title":"Announcements"},{"location":"meetings/2020/TechArea20200928/#triage-duty","text":"This week: Tim T Carl to send out email for the next rotation. 7 (-1) open FreshDesk tickets 3 (+0) open GGUS tickets","title":"Triage Duty"},{"location":"meetings/2020/TechArea20200928/#jira","text":"# of tickets \u0394 State 166 +0 Open 15 +3 Selected for Dev 15 +1 In Progress 4 -1 Dev Complete 17 -6 Ready for Testing 6 +5 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20200928/#osg-software-team","text":"Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20200928/#discussion","text":"None.","title":"Discussion"},{"location":"meetings/2020/TechArea20200928/#support-update","text":"Edgar: StashCache at PIC upgraded to the upcoming-fresh version but it's broken for them. Edgar is troubleshooting; will reach out to XRootD developers for assistance. The symptom is an SSL permission denied, but the error only shows up in XRootD 5 and goes away when they downgrade.","title":"Support Update"},{"location":"meetings/2020/TechArea20200928/#glideinwms-news","text":"Marco Mascheroni testing 3.6.4 in the ITB. (This will be in OSG 3.4 and OSG 3.5.) 3.9 now in osg-contrib (this includes Python 3 support). Continuing work on 3.7; integrating some work from the recent tokens hackathon.","title":"GlideinWMS News"},{"location":"meetings/2020/TechArea20200928/#osg-release-team","text":"3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 0 +0 10 -1 10 -1 Open 0 +0 0 +0 3 +2 3 +2 Selected for Development 0 +0 0 +0 1 -2 1 -2 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 1 +1 4 -3 5 -2 Ready for Testing 1 +1 0 +0 0 -1 1 +0 Ready for Release 1 +1 1 +1 18 -6 20 -4 Total Software Ready for Testing Both GlideinWMS 3.6.4 3.5.25 blahp 1.18.48 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20200928/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20200928/#osg-investigations-team","text":"Next week we have the stashcp-go presentation. Tackling some GRACC technical debt (RabbitMQ library changed a lot between versions) IRIS-HEP Fellows presentation today Converted perfsonar ingesters over to K8s Much work on perfsonar collector. Now using multi-processing, and a thread pool (DNS lookup are slow!) Consulting on the gratia probe for containers","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201005/","text":"OSG Technology Area Meeting, 5 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 CC spin-up meeting for the 2020 CC recipients later this month -- requests for materials will be high-priority. Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (-3) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 173 +7 Open 15 +0 Selected for Dev 14 -1 In Progress 6 +2 Dev Complete 17 +0 Ready for Testing 6 +0 Ready for Release OSG Software Team \u00b6 Doc focus Oct 22 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 AI (Edgar): merge https://opensciencegrid.atlassian.net/browse/SOFTWARE-4203 Does XRootD 4.12.5 fix issues found with XRootD 4.12.4? No; the error seems to affect TPC in the entire 4.12.X series. For some reason, nightly VMU tests (which test TPC) have not detected the issue. AI (Edgar/Diego): Investigate why VMU tests do not catch this issue. AI (Edgar/Diego): Report problem to XRootD developers as a GitHub issue. Discussion \u00b6 Diego: PR for Python 3 support for SciTokens was merged. AI (Diego): Rebuild XRootD plugins for XRootD 5 (except XRootD-HDFS). AI (Edgar): Build osg-xrootd and x509-scitokens-issuer for EL8, since they are no longer blocked by osg-configure. (This is lower priority than XRootD issues mentioned above.) AI (BrianL): Coordinate improvement of cache federation registration process. AI (Mat): Investigate stale URLs in technology docs. TimT: Encountering build failures for HTCondor on EL8 -- these appear to be random (i.e. rebuilds succeed). HTCondor-CE tests with HTCondor 8.9.9 are brittle and randomly fail to run. BrianL will investigate. GlideinWMS \u00b6 Will release 3.6.5, which includes a fix for a bind-mount issue encountered by Marco Mascheroni. Support Update \u00b6 Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. Edgar: Continuing to debug issues with XRootD 5 in the CNAF StashCache -- maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB. OSG Release Team \u00b6 3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 1 +1 10 +0 11 +1 Open 0 +0 0 +0 4 +1 4 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 -1 4 +0 4 -1 Ready for Testing 1 +0 0 +0 1 +1 2 +1 Ready for Release 1 +0 1 +0 20 +2 22 +2 Total Software Ready for Testing 3.5.25 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.25 blahp 1.18.48 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 StashCP Go presentation planned for next week. Redirectors with TLS turned on test is planned for today. Lets see what breaks! Discussion \u00b6 None this week","title":"October 5, 2020"},{"location":"meetings/2020/TechArea20201005/#osg-technology-area-meeting-5-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 5 October 2020"},{"location":"meetings/2020/TechArea20201005/#announcements","text":"CC spin-up meeting for the 2020 CC recipients later this month -- requests for materials will be high-priority.","title":"Announcements"},{"location":"meetings/2020/TechArea20201005/#triage-duty","text":"This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (-3) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201005/#jira","text":"# of tickets \u0394 State 173 +7 Open 15 +0 Selected for Dev 14 -1 In Progress 6 +2 Dev Complete 17 +0 Ready for Testing 6 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201005/#osg-software-team","text":"Doc focus Oct 22 13:30 - 17:30 CDT Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 AI (Edgar): merge https://opensciencegrid.atlassian.net/browse/SOFTWARE-4203 Does XRootD 4.12.5 fix issues found with XRootD 4.12.4? No; the error seems to affect TPC in the entire 4.12.X series. For some reason, nightly VMU tests (which test TPC) have not detected the issue. AI (Edgar/Diego): Investigate why VMU tests do not catch this issue. AI (Edgar/Diego): Report problem to XRootD developers as a GitHub issue.","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201005/#discussion","text":"Diego: PR for Python 3 support for SciTokens was merged. AI (Diego): Rebuild XRootD plugins for XRootD 5 (except XRootD-HDFS). AI (Edgar): Build osg-xrootd and x509-scitokens-issuer for EL8, since they are no longer blocked by osg-configure. (This is lower priority than XRootD issues mentioned above.) AI (BrianL): Coordinate improvement of cache federation registration process. AI (Mat): Investigate stale URLs in technology docs. TimT: Encountering build failures for HTCondor on EL8 -- these appear to be random (i.e. rebuilds succeed). HTCondor-CE tests with HTCondor 8.9.9 are brittle and randomly fail to run. BrianL will investigate.","title":"Discussion"},{"location":"meetings/2020/TechArea20201005/#glideinwms","text":"Will release 3.6.5, which includes a fix for a bind-mount issue encountered by Marco Mascheroni.","title":"GlideinWMS"},{"location":"meetings/2020/TechArea20201005/#support-update","text":"Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. Edgar: Continuing to debug issues with XRootD 5 in the CNAF StashCache -- maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB.","title":"Support Update"},{"location":"meetings/2020/TechArea20201005/#osg-release-team","text":"3.4.55 \u0394 Both \u0394 3.5.25 \u0394 Total \u0394 Status 0 +0 1 +1 10 +0 11 +1 Open 0 +0 0 +0 4 +1 4 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 -1 4 +0 4 -1 Ready for Testing 1 +0 0 +0 1 +1 2 +1 Ready for Release 1 +0 1 +0 20 +2 22 +2 Total Software Ready for Testing 3.5.25 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.25 blahp 1.18.48 3.4.55 Singularity 3.6.3 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201005/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201005/#osg-investigations-team","text":"StashCP Go presentation planned for next week. Redirectors with TLS turned on test is planned for today. Lets see what breaks!","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201005/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201012/","text":"OSG Technology Area Meeting, 12 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, Mat, Salman Djingueinabaye, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Edgar 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 157 -16 Open 16 +1 Selected for Dev 18 +4 In Progress 12 +12 Dev Complete 17 +0 Ready for Testing 0 +0 Ready for Release StashCP in Go Presentation \u00b6 WIP source ; slides Due to a number of benefits of Golang as opposed to Python, stashcp is being reimplemented in Golang. This is primarily performance (since it's built for concurrency) and ease of installation (since it's a statically linked binary.) Some features that have yet to be implemented are: finding the \"best\" cache stashcp_single Timeline of release is \"weeks, not months.\" Good documentation and well-commented code is a high priority. OSG Software Team \u00b6 Doc focus Oct 22 canceled due to OSG CC* Workshop Oct 22-23 Oct 29 is a good cadidate date for a reschedule. CVMFS + EL6 nightly failures currently under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 OSG-Display (the software) is deployed by a Git checkout that is picked up by an Apache server. John Thiltges is working on moving it to Kubernetes. AI (Carl): Deploy repo generation changes to repo-itb. AI (Diego): Build python-scitokens for EL7 and xrootd 5 and plugins for EL8. AI (Edgar): Debug why XRootD fails to start in EL8 VMU tests. In time crunch to get EXPANSE going. They require hosted CEs and use EL8 head nodes. All the software should be ready. AI (Mat): Implement token auth for topology. AI (Mat): Update the state of WLCG VO proxy support ticket (SOFTWARE-4113). Support Update \u00b6 Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. CNAF (Edgar): Continuing to debug issues with XRootD 5 in the CNAF StashCache \u2013 maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB. OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 -1 9 -1 9 -2 Open 0 +0 0 +0 5 +1 5 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 5 +1 5 +1 Ready for Testing 0 -1 0 +0 0 -1 0 -2 Ready for Release 0 -1 0 -1 20 +0 20 -2 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week OSG Investigations Team \u00b6 StashCP Go presentation! TLS on redirectors is done. No reports of breakage. Elasticsearch on Kubernetes! Discussion \u00b6 None this week","title":"October 12, 2020"},{"location":"meetings/2020/TechArea20201012/#osg-technology-area-meeting-12-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marian, Mat, Salman Djingueinabaye, TimT","title":"OSG Technology Area Meeting, 12 October 2020"},{"location":"meetings/2020/TechArea20201012/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20201012/#triage-duty","text":"This week: Carl Next week: Edgar 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201012/#jira","text":"# of tickets \u0394 State 157 -16 Open 16 +1 Selected for Dev 18 +4 In Progress 12 +12 Dev Complete 17 +0 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201012/#stashcp-in-go-presentation","text":"WIP source ; slides Due to a number of benefits of Golang as opposed to Python, stashcp is being reimplemented in Golang. This is primarily performance (since it's built for concurrency) and ease of installation (since it's a statically linked binary.) Some features that have yet to be implemented are: finding the \"best\" cache stashcp_single Timeline of release is \"weeks, not months.\" Good documentation and well-commented code is a high priority.","title":"StashCP in Go Presentation"},{"location":"meetings/2020/TechArea20201012/#osg-software-team","text":"Doc focus Oct 22 canceled due to OSG CC* Workshop Oct 22-23 Oct 29 is a good cadidate date for a reschedule. CVMFS + EL6 nightly failures currently under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201012/#discussion","text":"OSG-Display (the software) is deployed by a Git checkout that is picked up by an Apache server. John Thiltges is working on moving it to Kubernetes. AI (Carl): Deploy repo generation changes to repo-itb. AI (Diego): Build python-scitokens for EL7 and xrootd 5 and plugins for EL8. AI (Edgar): Debug why XRootD fails to start in EL8 VMU tests. In time crunch to get EXPANSE going. They require hosted CEs and use EL8 head nodes. All the software should be ready. AI (Mat): Implement token auth for topology. AI (Mat): Update the state of WLCG VO proxy support ticket (SOFTWARE-4113).","title":"Discussion"},{"location":"meetings/2020/TechArea20201012/#support-update","text":"Univeristy of Connecticut (BrianL): investigating Blahp segfault with Flightworthy JLab (Derek): Origin host is crashing. Not necessarily the OSG provided container. CNAF (Edgar): Continuing to debug issues with XRootD 5 in the CNAF StashCache \u2013 maybe caused by authfile generation. Also testing HTCondor 8.9.9 tarballs in the LIGO ITB.","title":"Support Update"},{"location":"meetings/2020/TechArea20201012/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 -1 9 -1 9 -2 Open 0 +0 0 +0 5 +1 5 +1 Selected for Development 0 +0 0 +0 1 +0 1 +0 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 5 +1 5 +1 Ready for Testing 0 -1 0 +0 0 -1 0 -2 Ready for Release 0 -1 0 -1 20 +0 20 -2 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201012/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201012/#osg-investigations-team","text":"StashCP Go presentation! TLS on redirectors is done. No reports of breakage. Elasticsearch on Kubernetes!","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201012/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201019/","text":"OSG Technology Area Meeting, 19 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Oct 22-23 Workshop: Supporting Campus Researchers with dHTC and the OSG Triage Duty \u00b6 This week: Edgar Next week: Diego 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 169 +12 Open 15 -1 Selected for Dev 20 +2 In Progress 11 -1 Dev Complete 21 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus Oct 29 1:30pm CVMFS + EL6 nightly failures still under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 There will be upcoming changes to Freshdesk SLAs and policies; exact details to come later. XRootD 4.12.5 release is out. Derek: LIGO dataframe access with SciTokens is at a roadblock because LIGO shares an origin with CMS; LIGO wants TLS enabled but CMS is not ready for it. LIGO will move to their own origin server. AI (Diego): Continue building XRootD 5 plugins for EL8, and updating xrootd-multiuser. AI (Edgar): Push xrootd-standalone and x509-scitokens-issuer over the finish line AI (Mat): Document building xrootd-compat packages; build Ubuntu containers. GlideinWMS: 3.7.1 work continuing. 3.6.5 released recently and has been stable in production. Jeff having trouble restricting disk usage on a site; Marco will debug and seek help from HTCondor developers. Support Update \u00b6 Expanse (Edgar, BrianL): Tracked down some EL8 Bosco incompatibilities. These fixes need to be included in Bosco override files until they're fixed upstream. JLab (Derek): JLab Origin much more stable this week. Continuing to aggressively monitor, but so far so good. OSG Connect (Derek): StashCP issue when the writeback address is a directory and not a file. Curl doesn't give an error message, it just gives a non-zero exit code. So the error from stashcp is cryptic. Will investigate solution. OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! Elasticsearch upgrade upcoming on OSG GRACC coming the end of this month. Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +2 11 +2 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 6 +1 6 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 23 +0 23 +3 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"October 19, 2020"},{"location":"meetings/2020/TechArea20201019/#osg-technology-area-meeting-19-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Diego, Edgar, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 19 October 2020"},{"location":"meetings/2020/TechArea20201019/#announcements","text":"Oct 22-23 Workshop: Supporting Campus Researchers with dHTC and the OSG","title":"Announcements"},{"location":"meetings/2020/TechArea20201019/#triage-duty","text":"This week: Edgar Next week: Diego 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201019/#jira","text":"# of tickets \u0394 State 169 +12 Open 15 -1 Selected for Dev 20 +2 In Progress 11 -1 Dev Complete 21 +4 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201019/#osg-software-team","text":"Doc focus Oct 29 1:30pm CVMFS + EL6 nightly failures still under investigation with upstream Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201019/#discussion","text":"There will be upcoming changes to Freshdesk SLAs and policies; exact details to come later. XRootD 4.12.5 release is out. Derek: LIGO dataframe access with SciTokens is at a roadblock because LIGO shares an origin with CMS; LIGO wants TLS enabled but CMS is not ready for it. LIGO will move to their own origin server. AI (Diego): Continue building XRootD 5 plugins for EL8, and updating xrootd-multiuser. AI (Edgar): Push xrootd-standalone and x509-scitokens-issuer over the finish line AI (Mat): Document building xrootd-compat packages; build Ubuntu containers. GlideinWMS: 3.7.1 work continuing. 3.6.5 released recently and has been stable in production. Jeff having trouble restricting disk usage on a site; Marco will debug and seek help from HTCondor developers.","title":"Discussion"},{"location":"meetings/2020/TechArea20201019/#support-update","text":"Expanse (Edgar, BrianL): Tracked down some EL8 Bosco incompatibilities. These fixes need to be included in Bosco override files until they're fixed upstream. JLab (Derek): JLab Origin much more stable this week. Continuing to aggressively monitor, but so far so good. OSG Connect (Derek): StashCP issue when the writeback address is a directory and not a file. Curl doesn't give an error message, it just gives a non-zero exit code. So the error from stashcp is cryptic. Will investigate solution.","title":"Support Update"},{"location":"meetings/2020/TechArea20201019/#osg-investigations-team","text":"Elasticsearch on Kubernetes! Elasticsearch upgrade upcoming on OSG GRACC coming the end of this month.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201019/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201019/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +2 11 +2 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 6 +1 6 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 23 +0 23 +3 Total Software Ready for Testing 3.5.26 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201019/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201026/","text":"OSG Technology Area Meeting, 26 October 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Diego, Edgar, Marco Mambell, Marian, Mat, TimT Announcements \u00b6 This is Diego and Edgar's last week on the Software and Release team! Triage Duty \u00b6 This week: Diego Next week: TimT 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 154 -15 Open 16 +1 Selected for Dev 18 -2 In Progress 12 +1 Dev Complete 23 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus this Thursday Oct 29 1:30pm Kubernetes hackathon tomorrow Oct 27 1:00pm CVMFS + EL6 nightly failures due to SELinux issue and newly changed OSG CVMFS config; workaround in place Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 Our VIRGO contact is the VIRGO Computing Coordinator Stefano Bagnasco (bagnasco@to.infn.it). IRIS-HEP Analysis Systems workshop today and tomorrow. AI (Diego): diagnose XRootD 5 on EL8 issues. AI (Edgar): debug why xrootd-multiuser plugin keeps XRootD server from starting. debug why binary used to generate macaroons is core dumping; contact Zach Miller for assistance. AI (Mat): help Mark Coatsworth with EL8/Python3 support for HTCondor-CE. Multiple issues with BOSCO/Hosted-CEs: Job persistence hasn't been implemented for Hosted-CE containers yet, which means restarts kill jobs. This makes testing and config updates somewhat harmful. A potential solution is using a PersistendVolumeClaim but that's not easy on SLATE. Bosco keeps persistent state in /tmp ; Expanse had their submit node set up with DNS round-robin which means state was sometimes there, sometimes not. Edgar added a manual workaround. Support Update \u00b6 Expanse (Edgar, BrianL): CMS user not being set up properly and PATH being overriden: PRs in to fix both JLab (Edgar): Figured out origin port re-use issue: problem with the site config OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! OASIS upgrade last week (supports SSH logins via authorized keys registered in COmanage!). OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2. Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 0 +0 8 +2 8 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +2 25 +2 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"October 26, 2020"},{"location":"meetings/2020/TechArea20201026/#osg-technology-area-meeting-26-october-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Diego, Edgar, Marco Mambell, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 26 October 2020"},{"location":"meetings/2020/TechArea20201026/#announcements","text":"This is Diego and Edgar's last week on the Software and Release team!","title":"Announcements"},{"location":"meetings/2020/TechArea20201026/#triage-duty","text":"This week: Diego Next week: TimT 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201026/#jira","text":"# of tickets \u0394 State 154 -15 Open 16 +1 Selected for Dev 18 -2 In Progress 12 +1 Dev Complete 23 +2 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201026/#osg-software-team","text":"Doc focus this Thursday Oct 29 1:30pm Kubernetes hackathon tomorrow Oct 27 1:00pm CVMFS + EL6 nightly failures due to SELinux issue and newly changed OSG CVMFS config; workaround in place Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201026/#discussion","text":"Our VIRGO contact is the VIRGO Computing Coordinator Stefano Bagnasco (bagnasco@to.infn.it). IRIS-HEP Analysis Systems workshop today and tomorrow. AI (Diego): diagnose XRootD 5 on EL8 issues. AI (Edgar): debug why xrootd-multiuser plugin keeps XRootD server from starting. debug why binary used to generate macaroons is core dumping; contact Zach Miller for assistance. AI (Mat): help Mark Coatsworth with EL8/Python3 support for HTCondor-CE. Multiple issues with BOSCO/Hosted-CEs: Job persistence hasn't been implemented for Hosted-CE containers yet, which means restarts kill jobs. This makes testing and config updates somewhat harmful. A potential solution is using a PersistendVolumeClaim but that's not easy on SLATE. Bosco keeps persistent state in /tmp ; Expanse had their submit node set up with DNS round-robin which means state was sometimes there, sometimes not. Edgar added a manual workaround.","title":"Discussion"},{"location":"meetings/2020/TechArea20201026/#support-update","text":"Expanse (Edgar, BrianL): CMS user not being set up properly and PATH being overriden: PRs in to fix both JLab (Edgar): Figured out origin port re-use issue: problem with the site config","title":"Support Update"},{"location":"meetings/2020/TechArea20201026/#osg-investigations-team","text":"Elasticsearch on Kubernetes! OASIS upgrade last week (supports SSH logins via authorized keys registered in COmanage!). OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201026/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201026/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 5 +0 5 +0 Selected for Development 0 +0 0 +0 1 +1 1 +1 In Progress 0 +0 0 +0 0 -1 0 -1 Development Complete 0 +0 0 +0 8 +2 8 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +2 25 +2 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) XRootD 4.12.5-rc1 EL8: lcmaps 1.6.6 EL8: osg-configure 3.10 EL8: xrootd-multiuser 0.4.4 Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201026/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201102/","text":"OSG Technology Area Meeting, 2 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marian, Marco Mambelli, TimT Announcements \u00b6 Travis CI has a new pricing model ( https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing ) that affects us: The OSG org has 1000 minutes off the bat and we can apply for OSS minutes All new container builds should be set up using GitHub actions We are discussing consolidating this meeting with 9am Monday morning stand-ups Triage Duty \u00b6 This week: TimT Next week: Mat 7 (-4) open FreshDesk tickets 1 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 137 -14 Open 17 +1 Selected for Dev 21 +3 In Progress 12 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 WN client installs and StashCache tests fail in the release due to EPEL gfal requiring XRootD 5 Workaround: yum install osg-wn-client --enablerepo=osg-upcoming We'll need to build gfal2-plugin-xrootd for OSG 3.5 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 AI (TimT): give BrianL HTCondor yum repo URLs to include in the OSG nightly tests Support Update \u00b6 CMS (Marian, Derek): Running into issues with XRootD 5 and GSI/VOMS authN; perhaps related to an xrootd-lcmaps config issue that John Thiltges ran into FNAL (Derek): CVMFS sync stopped working and they switched to another one and has been resolved JLab (Carl): still waiting on JLab to sort out DNS and firewall issues before we can verify their CE OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! Need to add logstash XRootD 5 on the LIGO origin (Thanks John) xrootd-scitokens requires some work requested from Andy about renaming things to be consistent with XRootD. OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2. Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 -2 3 -2 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 11 +3 11 +3 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +0 25 +0 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 XRootD 4.12.5 osg-flock 1.2-2 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) Upcoming: HTCondor 8.9.9 Upcoming: XRootD 5.0.2 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"November 2, 2020"},{"location":"meetings/2020/TechArea20201102/#osg-technology-area-meeting-2-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marian, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 2 November 2020"},{"location":"meetings/2020/TechArea20201102/#announcements","text":"Travis CI has a new pricing model ( https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing ) that affects us: The OSG org has 1000 minutes off the bat and we can apply for OSS minutes All new container builds should be set up using GitHub actions We are discussing consolidating this meeting with 9am Monday morning stand-ups","title":"Announcements"},{"location":"meetings/2020/TechArea20201102/#triage-duty","text":"This week: TimT Next week: Mat 7 (-4) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201102/#jira","text":"# of tickets \u0394 State 137 -14 Open 17 +1 Selected for Dev 21 +3 In Progress 12 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201102/#osg-software-team","text":"WN client installs and StashCache tests fail in the release due to EPEL gfal requiring XRootD 5 Workaround: yum install osg-wn-client --enablerepo=osg-upcoming We'll need to build gfal2-plugin-xrootd for OSG 3.5 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201102/#discussion","text":"AI (TimT): give BrianL HTCondor yum repo URLs to include in the OSG nightly tests","title":"Discussion"},{"location":"meetings/2020/TechArea20201102/#support-update","text":"CMS (Marian, Derek): Running into issues with XRootD 5 and GSI/VOMS authN; perhaps related to an xrootd-lcmaps config issue that John Thiltges ran into FNAL (Derek): CVMFS sync stopped working and they switched to another one and has been resolved JLab (Carl): still waiting on JLab to sort out DNS and firewall issues before we can verify their CE","title":"Support Update"},{"location":"meetings/2020/TechArea20201102/#osg-investigations-team","text":"Elasticsearch on Kubernetes! Need to add logstash XRootD 5 on the LIGO origin (Thanks John) xrootd-scitokens requires some work requested from Andy about renaming things to be consistent with XRootD. OSG GRACC upgrade coming this week, v7.8.2 -> v7.9.2.","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201102/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201102/#osg-release-team","text":"3.4.56 \u0394 Both \u0394 3.5.26 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 -2 3 -2 Selected for Development 0 +0 0 +0 0 -1 0 -1 In Progress 0 +0 0 +0 0 +0 0 +0 Development Complete 0 +0 0 +0 11 +3 11 +3 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 25 +0 25 +0 Total Software Ready for Testing 3.5.26 HTCondor 8.8.11 CVMFS 2.7.5 XRootD 4.12.5 osg-flock 1.2-2 scitokens-credmon 0.8.1 python-scitokens 1.2.4-3 (Python 3 implementation) Upcoming: HTCondor 8.9.9 Upcoming: XRootD 5.0.2 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.26 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201102/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201109/","text":"OSG Technology Area Meeting, 9 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 We are discussing consolidating this meeting with 9am Monday morning stand-ups Triage Duty \u00b6 This week: Mat Next week: BrianL 11 (+4) open FreshDesk tickets 1 (+1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 +14 Open 16 +1 Selected for Dev 20 +3 In Progress 14 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66 Discussion \u00b6 Considering releasing XRootD for EL8 AI (Mat): Finish releasing osg-build into devops-production. AI (Mat): Add additional features to OSG-Configure (see tickets) AI (TimT): Write release policy for OSG 3.6 (high priority -- we want to send it out for review soon) AI (Derek): Assist LIGO. Potential Kubernetes Hackathon tomorrow. Shreyas Bharat may join the hackathon to work on factory items. GlideinWMS 3.7.1 has been released and is in osg-upcoming-development. Support Update \u00b6 Derek: continued assisting AMNH with their hosted CE. Mat: assisting Vlad at IceCube for setting up their StashCache Origin. OSG Investigations Team \u00b6 Elasticsearch on Kubernetes! May not use logstash, more to follow XRootD 5 on the LIGO origin, now on Derek to configure for TLS and do all the ligo things . xrootd-scitokens - round 2. OSG GRACC upgraded: v7.8.2 -> v7.9.2. Investigated possible status sites, best option may be Cachet Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.57 \u0394 Both \u0394 3.5.27 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 7 -4 7 -4 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 -3 22 -3 Total Software Ready for Testing 3.5.27 XRootD 4.12.5 Upcoming: HTCondor 8.9.9 EL8: bunch of stuff (still waiting for HTCondor-CE) xrootd-cmstfc 1.5.2-6 (contrib in upcoming) Ready for Release 3.5.27 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"November 9, 2020"},{"location":"meetings/2020/TechArea20201109/#osg-technology-area-meeting-9-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 9 November 2020"},{"location":"meetings/2020/TechArea20201109/#announcements","text":"We are discussing consolidating this meeting with 9am Monday morning stand-ups","title":"Announcements"},{"location":"meetings/2020/TechArea20201109/#triage-duty","text":"This week: Mat Next week: BrianL 11 (+4) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201109/#jira","text":"# of tickets \u0394 State 146 +14 Open 16 +1 Selected for Dev 20 +3 In Progress 14 +0 Dev Complete 28 +5 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201109/#osg-software-team","text":"Tech team priorities this week: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19&quickFilter=66","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201109/#discussion","text":"Considering releasing XRootD for EL8 AI (Mat): Finish releasing osg-build into devops-production. AI (Mat): Add additional features to OSG-Configure (see tickets) AI (TimT): Write release policy for OSG 3.6 (high priority -- we want to send it out for review soon) AI (Derek): Assist LIGO. Potential Kubernetes Hackathon tomorrow. Shreyas Bharat may join the hackathon to work on factory items. GlideinWMS 3.7.1 has been released and is in osg-upcoming-development.","title":"Discussion"},{"location":"meetings/2020/TechArea20201109/#support-update","text":"Derek: continued assisting AMNH with their hosted CE. Mat: assisting Vlad at IceCube for setting up their StashCache Origin.","title":"Support Update"},{"location":"meetings/2020/TechArea20201109/#osg-investigations-team","text":"Elasticsearch on Kubernetes! May not use logstash, more to follow XRootD 5 on the LIGO origin, now on Derek to configure for TLS and do all the ligo things . xrootd-scitokens - round 2. OSG GRACC upgraded: v7.8.2 -> v7.9.2. Investigated possible status sites, best option may be Cachet","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201109/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201109/#osg-release-team","text":"3.4.57 \u0394 Both \u0394 3.5.27 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 0 +0 0 +0 In Progress 0 +0 0 +0 1 +1 1 +1 Development Complete 0 +0 0 +0 7 -4 7 -4 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 -3 22 -3 Total Software Ready for Testing 3.5.27 XRootD 4.12.5 Upcoming: HTCondor 8.9.9 EL8: bunch of stuff (still waiting for HTCondor-CE) xrootd-cmstfc 1.5.2-6 (contrib in upcoming) Ready for Release 3.5.27 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201109/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201116/","text":"OSG Technology Area Meeting, 16 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 Tech Area meeting merged into Monday morning 9am CST stand-ups! Please provide any feedback to BrianL BrianL OOO next week, Mat and BrianB to act as back-up Triage Duty \u00b6 This week: BrianL Next week: Carl 4 (-7) open FreshDesk tickets 0 (-1) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA Discussion \u00b6 AI (Junheng): work on osg-notify bug-fix AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. GlideinWMS Mat found a GlideinWMS bug when working on Ubuntu support; Marco to review and merge, which should get us further along since the affected script is pulled from the master branch 3.7.1 got promoted to production. Working on merging the changes to the Python 3 version. UCSD factories are both running the 3.7 series. CERN factory still running 3.6 series. 3.7.2 expected to handle missing GSI infrastructure. Support Update \u00b6 IceCube (Mat) - playing whack-a-mole with Stash Origin issues (docs have already been improved as a result). Currently investigating permission issues that are likely in the XRootD configuration layer. OSG Investigations Team \u00b6 BrianB has made quite a bit of progress on the OS pool registry: Almost has an end-to-end proof of concept working in the osgdev namespace on Tiger Put together a development container so that work can be handed off Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 2 +2 2 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 5 -2 5 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 +0 22 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): Build HTCondor 8.8 and 8.9 in OSG & run VMU tests Talk to Horst about testing XRootD 4 Difficult to find to find willing testers for XRootD 4 since XCache servers are all using XRootD 5 on the other hand, non-XCache servers are reluctant to upgrade; talk to Dave Mason for help. Look at EL 6 retirement spreadsheet Move cronjobs from ingwe to moria","title":"November 16, 2020"},{"location":"meetings/2020/TechArea20201116/#osg-technology-area-meeting-16-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 16 November 2020"},{"location":"meetings/2020/TechArea20201116/#announcements","text":"Tech Area meeting merged into Monday morning 9am CST stand-ups! Please provide any feedback to BrianL BrianL OOO next week, Mat and BrianB to act as back-up","title":"Announcements"},{"location":"meetings/2020/TechArea20201116/#triage-duty","text":"This week: BrianL Next week: Carl 4 (-7) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201116/#jira","text":"# of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201116/#osg-software-team","text":"Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201116/#discussion","text":"AI (Junheng): work on osg-notify bug-fix AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. GlideinWMS Mat found a GlideinWMS bug when working on Ubuntu support; Marco to review and merge, which should get us further along since the affected script is pulled from the master branch 3.7.1 got promoted to production. Working on merging the changes to the Python 3 version. UCSD factories are both running the 3.7 series. CERN factory still running 3.6 series. 3.7.2 expected to handle missing GSI infrastructure.","title":"Discussion"},{"location":"meetings/2020/TechArea20201116/#support-update","text":"IceCube (Mat) - playing whack-a-mole with Stash Origin issues (docs have already been improved as a result). Currently investigating permission issues that are likely in the XRootD configuration layer.","title":"Support Update"},{"location":"meetings/2020/TechArea20201116/#osg-investigations-team","text":"BrianB has made quite a bit of progress on the OS pool registry: Almost has an end-to-end proof of concept working in the osgdev namespace on Tiger Put together a development container so that work can be handed off","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201116/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201116/#osg-release-team","text":"3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 11 +0 11 +0 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 2 +2 2 +2 In Progress 0 +0 0 +0 1 +0 1 +0 Development Complete 0 +0 0 +0 5 -2 5 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 22 +0 22 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201116/#discussion_2","text":"AI (TimT): Build HTCondor 8.8 and 8.9 in OSG & run VMU tests Talk to Horst about testing XRootD 4 Difficult to find to find willing testers for XRootD 4 since XCache servers are all using XRootD 5 on the other hand, non-XCache servers are reluctant to upgrade; talk to Dave Mason for help. Look at EL 6 retirement spreadsheet Move cronjobs from ingwe to moria","title":"Discussion"},{"location":"meetings/2020/TechArea20201123/","text":"OSG Technology Area Meeting, 23 November 2020 \u00b6 Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, Carl, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL out all week; Mat out Wednesday and Friday. (TODO numbers) Triage Duty \u00b6 This week: Carl Next week: Mat 8 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 146 +5 Open 13 -2 Selected for Dev 23 +1 In Progress 17 +1 Dev Complete 16 -6 Ready for Testing 7 +7 Ready for Release OSG Software Team \u00b6 Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA Discussion \u00b6 AI (Carl): Continue working on Gratia probes. Move cron jobs from ingwe to moria. AI (Junheng): OSG-Notify and packages emailer cronjob close to being merged. AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. Test, finish Ubuntu Submit host and inform Old Dominion University of status. Work on Open Pool Negotiator. Kubernetes documentation for the OSG Worker Node. GlideinWMS: Integrate IDTOKEN fixes for 3.7.2. Update Glidein-in-Vacuum and add it to the main release (instead of having it be a separate project). Currently, frontend user needs to be added to sudoers for token generation; working on a way to remove that requirement. GLOW frontend upgraded to 3.7.1; no major problems found. Fermicloud will shut off all EL6 VMs and remove images; Marco will continue to maintain some Docker/Singularity images (since they are still used by experiments). Support Update \u00b6 GlideinWMS: the factory was using 3.7.0rc9 let to some errors due to compatibility issues with the 3.6 series. OSG Investigations Team \u00b6 Discussion \u00b6 None this week OSG Release Team \u00b6 3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 1 -1 1 -1 In Progress 0 +0 0 +0 2 +1 2 +1 Development Complete 0 +0 0 +0 5 +0 5 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 24 +2 24 +2 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"November 23, 2020"},{"location":"meetings/2020/TechArea20201123/#osg-technology-area-meeting-23-november-2020","text":"Coordinates: Conference: +1 312-626-6799, PIN: 718 161 330, https://cern.zoom.us/j/718161330 (password sent separately) Attending: BrianB, Carl, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 23 November 2020"},{"location":"meetings/2020/TechArea20201123/#announcements","text":"BrianL out all week; Mat out Wednesday and Friday. (TODO numbers)","title":"Announcements"},{"location":"meetings/2020/TechArea20201123/#triage-duty","text":"This week: Carl Next week: Mat 8 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201123/#jira","text":"# of tickets \u0394 State 146 +5 Open 13 -2 Selected for Dev 23 +1 In Progress 17 +1 Dev Complete 16 -6 Ready for Testing 7 +7 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201123/#osg-software-team","text":"Container dev guide updated for GHA New docs for upgrading MkDocs repos to GHA","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201123/#discussion","text":"AI (Carl): Continue working on Gratia probes. Move cron jobs from ingwe to moria. AI (Junheng): OSG-Notify and packages emailer cronjob close to being merged. AI (Mat): OSG-Configure tasks promised to the GlideinWMS team for the end of November. Test, finish Ubuntu Submit host and inform Old Dominion University of status. Work on Open Pool Negotiator. Kubernetes documentation for the OSG Worker Node. GlideinWMS: Integrate IDTOKEN fixes for 3.7.2. Update Glidein-in-Vacuum and add it to the main release (instead of having it be a separate project). Currently, frontend user needs to be added to sudoers for token generation; working on a way to remove that requirement. GLOW frontend upgraded to 3.7.1; no major problems found. Fermicloud will shut off all EL6 VMs and remove images; Marco will continue to maintain some Docker/Singularity images (since they are still used by experiments).","title":"Discussion"},{"location":"meetings/2020/TechArea20201123/#support-update","text":"GlideinWMS: the factory was using 3.7.0rc9 let to some errors due to compatibility issues with the 3.6 series.","title":"Support Update"},{"location":"meetings/2020/TechArea20201123/#osg-investigations-team","text":"","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201123/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201123/#osg-release-team","text":"3.4.58 \u0394 Both \u0394 3.5.28 \u0394 Total \u0394 Status 0 +0 0 +0 12 +2 12 +2 Open 0 +0 0 +0 3 +0 3 +0 Selected for Development 0 +0 0 +0 1 -1 1 -1 In Progress 0 +0 0 +0 2 +1 2 +1 Development Complete 0 +0 0 +0 5 +0 5 +0 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 0 +0 0 +0 24 +2 24 +2 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201123/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201130/","text":"OSG Technology Area Meeting, 30 November 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 Second Kubernetes-HEP meetup Dec 1 and 2: https://indico.cern.ch/event/968726/ Triage Duty \u00b6 This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 HTCondor-CE + PBS EPEL testing nightlies job submissions are failing Software base image builds are failing due to \"invalid tag\" (maybe leading space?): https://github.com/opensciencegrid/docker-software-base/runs/1437033352?check_suite_focus=true#step:7:16 Discussion \u00b6 AI (TimT): will investigate HTCondor-CE + PBS EPEL testing failures; may require BLAHP fixes AI (Marco): Contact Mats Rynge for TOKEN support for the ITB FE. AI (Carl): Multi site support for pilot probe GHA for per-commit builds for gratia-probe Support Update \u00b6 None this week OSG Investigations Team \u00b6 No updates Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.28 \u0394 Status 8 -4 Open 3 +0 Selected for Development 2 +1 In Progress 5 +3 Development Complete 5 +0 Ready for Testing 0 +0 Ready for Release 23 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 No release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"November 30, 2020"},{"location":"meetings/2020/TechArea20201130/#osg-technology-area-meeting-30-november-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 30 November 2020"},{"location":"meetings/2020/TechArea20201130/#announcements","text":"Second Kubernetes-HEP meetup Dec 1 and 2: https://indico.cern.ch/event/968726/","title":"Announcements"},{"location":"meetings/2020/TechArea20201130/#triage-duty","text":"This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201130/#jira","text":"# of tickets \u0394 State 141 -5 Open 15 -1 Selected for Dev 22 +2 In Progress 16 +2 Dev Complete 22 -2 Ready for Testing 0 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201130/#osg-software-team","text":"HTCondor-CE + PBS EPEL testing nightlies job submissions are failing Software base image builds are failing due to \"invalid tag\" (maybe leading space?): https://github.com/opensciencegrid/docker-software-base/runs/1437033352?check_suite_focus=true#step:7:16","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201130/#discussion","text":"AI (TimT): will investigate HTCondor-CE + PBS EPEL testing failures; may require BLAHP fixes AI (Marco): Contact Mats Rynge for TOKEN support for the ITB FE. AI (Carl): Multi site support for pilot probe GHA for per-commit builds for gratia-probe","title":"Discussion"},{"location":"meetings/2020/TechArea20201130/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2020/TechArea20201130/#osg-investigations-team","text":"No updates","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201130/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201130/#osg-release-team","text":"3.5.28 \u0394 Status 8 -4 Open 3 +0 Selected for Development 2 +1 In Progress 5 +3 Development Complete 5 +0 Ready for Testing 0 +0 Ready for Release 23 +0 Total Software Ready for Testing 3.5.28 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201130/#discussion_2","text":"No release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"Discussion"},{"location":"meetings/2020/TechArea20201207/","text":"OSG Technology Area Meeting, 7 December 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Junheng, Marco Mambelli, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Tim Next week: BrianL (?) 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 144 +0 Open 12 -1 Selected for Dev 26 +2 In Progress 18 -1 Dev Complete 22 +6 Ready for Testing 7 +7 Ready for Release OSG Software Team \u00b6 EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 Marco: GWMS 3.7.2 released, includes bugfixes for IDTOKEN support; in upcoming-testing.AI (Mat): Submit bug report for XRootD 5.1.0rc1 problem detected in VMU tests. AI (Mat): Mail GridCF list about Travis CI's policy changes. AI (Mat): Ask Marco Mascheroni if he's happy with the new Pilot sections for OSG Configure. AI (Mat): Continue work on OSG flocking negotiator. AI (BrianL): Investigate webapp frameworks and EL 8 compatibility for HTCondor CE View. AI (Junheng): Investigate registry logout error. AI (TimT): Add PowerPC support to EPEL HTCondor packages. VPN access now required to log in to Fermicloud head node (fcluigpvm01.fnal.gov). 2FA required to access Fermi VPN. Steve Timm's suggested solution is to create a (persistent) VM for creating other VMs if that's not possible. Marco will send instructions on how to get access to Fermi VPN. Support Update \u00b6 IceCube (Mat, Derek): Stash Origin now appears to work after creating dummy SciTokens information in Topology. UCL stash origin needed the same fix but needs additional debugging; Derek is providing assistance. JLab (BrianL): blahp status queries time out trying to populate the Slurm job status cache. Opened a ticket with the the HTCondor team: https://opensciencegrid.atlassian.net/browse/HTCONDOR-104 OSG Investigations Team \u00b6 No updates Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.28 \u0394 Status 7 -1 Open 2 -1 Selected for Development 4 +2 In Progress 5 +0 Development Complete 9 +4 Ready for Testing 0 +0 Ready for Release 27 +4 Total Software Ready for Testing 3.5.28 HTCondor 8.8.12 Upcoming: HTCondor 8.9.10 hosted-ce-tools 0.9 htgettoken 1.0 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Containers opensciencegrid/atlas-xcache:fresh opensciencegrid/cms-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI(TimT): promote osg-build to devops Release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"December 7, 2020"},{"location":"meetings/2020/TechArea20201207/#osg-technology-area-meeting-7-december-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Junheng, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 7 December 2020"},{"location":"meetings/2020/TechArea20201207/#announcements","text":"","title":"Announcements"},{"location":"meetings/2020/TechArea20201207/#triage-duty","text":"This week: Tim Next week: BrianL (?) 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201207/#jira","text":"# of tickets \u0394 State 144 +0 Open 12 -1 Selected for Dev 26 +2 In Progress 18 -1 Dev Complete 22 +6 Ready for Testing 7 +7 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201207/#osg-software-team","text":"EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201207/#discussion","text":"Marco: GWMS 3.7.2 released, includes bugfixes for IDTOKEN support; in upcoming-testing.AI (Mat): Submit bug report for XRootD 5.1.0rc1 problem detected in VMU tests. AI (Mat): Mail GridCF list about Travis CI's policy changes. AI (Mat): Ask Marco Mascheroni if he's happy with the new Pilot sections for OSG Configure. AI (Mat): Continue work on OSG flocking negotiator. AI (BrianL): Investigate webapp frameworks and EL 8 compatibility for HTCondor CE View. AI (Junheng): Investigate registry logout error. AI (TimT): Add PowerPC support to EPEL HTCondor packages. VPN access now required to log in to Fermicloud head node (fcluigpvm01.fnal.gov). 2FA required to access Fermi VPN. Steve Timm's suggested solution is to create a (persistent) VM for creating other VMs if that's not possible. Marco will send instructions on how to get access to Fermi VPN.","title":"Discussion"},{"location":"meetings/2020/TechArea20201207/#support-update","text":"IceCube (Mat, Derek): Stash Origin now appears to work after creating dummy SciTokens information in Topology. UCL stash origin needed the same fix but needs additional debugging; Derek is providing assistance. JLab (BrianL): blahp status queries time out trying to populate the Slurm job status cache. Opened a ticket with the the HTCondor team: https://opensciencegrid.atlassian.net/browse/HTCONDOR-104","title":"Support Update"},{"location":"meetings/2020/TechArea20201207/#osg-investigations-team","text":"No updates","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201207/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201207/#osg-release-team","text":"3.5.28 \u0394 Status 7 -1 Open 2 -1 Selected for Development 4 +2 In Progress 5 +0 Development Complete 9 +4 Ready for Testing 0 +0 Ready for Release 27 +4 Total Software Ready for Testing 3.5.28 HTCondor 8.8.12 Upcoming: HTCondor 8.9.10 hosted-ce-tools 0.9 htgettoken 1.0 XRootD 4.12.5 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.28 Nothing yet Containers opensciencegrid/atlas-xcache:fresh opensciencegrid/cms-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201207/#discussion_2","text":"AI(TimT): promote osg-build to devops Release expected this week Waiting for Dave Mason to get people to test XRootD 4.","title":"Discussion"},{"location":"meetings/2020/TechArea20201214/","text":"OSG Technology Area Meeting, 14 December 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Junheng, Marco Mambelli, Marian, Mat, Tim C, Tim T Announcements \u00b6 Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts Triage Duty \u00b6 This week: Carl Next week: BrianL 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 145 +1 Open 12 +0 Selected for Dev 25 -1 In Progress 16 -2 Dev Complete 17 -5 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 AI (Carl): New IGTF CA release; update XRootD to 4.12.6. AI (Carl): Investigate bug in generating the CA certs website (lower priority since we can fix it manually) AI (Junheng): Fix location for registry PR; apply changes from review of 'outdated packages' Marco: Working on adding GitHub Actions and plans to use artifacts instead of caches since the former is longer lived AI (Mat): Ensure GridCF can make a GCT release AI (TimT): Prepare for new CA release. AI (TimT): Automate BOSCO and tarball updates; create tarballs for PPC architecture.Announcements: Support Update \u00b6 CMS (Marian): European CMS still mostly on XRootD 4 due to AAA dependency; still discussing migration plans. Miron (Carl): Continue investigating issues with Compute Canada sites erroneously showing up in the CC* dashboard UCL (Mat): Help UCL test authenticated stash origin. Discuss with Derek and Brian B about what kind of authentication is desired. OSG Investigations Team \u00b6 Focus on migrating more GRACC services to Tiger Establish documentation for the GRACC rolling update and fresh install Added and deployed SciToken helper support to OASIS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 10 +3 Open 2 +0 Selected for Development 5 +1 In Progress 5 +0 Development Complete 4 -5 Ready for Testing 0 +0 Ready for Release 26 -1 Total Software Ready for Testing 3.5.29 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data IGTF 1.108 Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"December 14, 2020"},{"location":"meetings/2020/TechArea20201214/#osg-technology-area-meeting-14-december-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Junheng, Marco Mambelli, Marian, Mat, Tim C, Tim T","title":"OSG Technology Area Meeting, 14 December 2020"},{"location":"meetings/2020/TechArea20201214/#announcements","text":"Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts","title":"Announcements"},{"location":"meetings/2020/TechArea20201214/#triage-duty","text":"This week: Carl Next week: BrianL 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201214/#jira","text":"# of tickets \u0394 State 145 +1 Open 12 +0 Selected for Dev 25 -1 In Progress 16 -2 Dev Complete 17 -5 Ready for Testing 7 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201214/#osg-software-team","text":"EL8 builds appear to automatically add package requirements for shebang lines. Beware /usr/bin/env python3 ! Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201214/#discussion","text":"AI (Carl): New IGTF CA release; update XRootD to 4.12.6. AI (Carl): Investigate bug in generating the CA certs website (lower priority since we can fix it manually) AI (Junheng): Fix location for registry PR; apply changes from review of 'outdated packages' Marco: Working on adding GitHub Actions and plans to use artifacts instead of caches since the former is longer lived AI (Mat): Ensure GridCF can make a GCT release AI (TimT): Prepare for new CA release. AI (TimT): Automate BOSCO and tarball updates; create tarballs for PPC architecture.Announcements:","title":"Discussion"},{"location":"meetings/2020/TechArea20201214/#support-update","text":"CMS (Marian): European CMS still mostly on XRootD 4 due to AAA dependency; still discussing migration plans. Miron (Carl): Continue investigating issues with Compute Canada sites erroneously showing up in the CC* dashboard UCL (Mat): Help UCL test authenticated stash origin. Discuss with Derek and Brian B about what kind of authentication is desired.","title":"Support Update"},{"location":"meetings/2020/TechArea20201214/#osg-investigations-team","text":"Focus on migrating more GRACC services to Tiger Establish documentation for the GRACC rolling update and fresh install Added and deployed SciToken helper support to OASIS","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201214/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201214/#osg-release-team","text":"3.5.29 \u0394 Status 10 +3 Open 2 +0 Selected for Development 5 +1 In Progress 5 +0 Development Complete 4 -5 Ready for Testing 0 +0 Ready for Release 26 -1 Total Software Ready for Testing 3.5.29 EL8: bunch of stuff (still waiting for HTCondor-CE) Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data IGTF 1.108 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201214/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201221/","text":"OSG Technology Area Meeting, 21 December 2020 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Carl, Irene, Junheng, Marco, Marian, TimT Announcements \u00b6 Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts Cancelling next week's meeting, to resume on Jan 4 Triage Duty \u00b6 This week: BrianL Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket JIRA \u00b6 # of tickets \u0394 State 133 -12 Open 12 +0 Selected for Dev 31 +6 In Progress 17 +1 Dev Complete 18 +1 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 AI (BrianL): Move new site onboarding engagement Freshdesk tickets to the Operations group Support Update \u00b6 IceCube (BrianL): completing request to require Singularity for IceCube pilots; continuing a discussion with David to see how we should manage the shared IceCube/GLOW pilots MIT (BrianL): troubleshooting GPU jobs not matching, turned out to be due to an old version of HTCondor OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January XCache(s): deployed new Wisconsin cache to osg-config repo XRootD data transfer monitor close to complete (testing and validation) GRACC (continued progress): migrating more GRACC services to Tiger documentation for the GRACC rolling update and fresh install Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 4 +6 Open 1 -1 Selected for Development 6 +1 In Progress 5 +0 Development Complete 4 +0 Ready for Testing 0 +0 Ready for Release 20 -6 Total Software Ready for Testing 3.5.29 EL8: various things, needs review Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"December 21, 2020"},{"location":"meetings/2020/TechArea20201221/#osg-technology-area-meeting-21-december-2020","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianB, BrianL, Carl, Irene, Junheng, Marco, Marian, TimT","title":"OSG Technology Area Meeting, 21 December 2020"},{"location":"meetings/2020/TechArea20201221/#announcements","text":"Outages through the end of the year: Mat starting Dec 21 Carl starting Dec 23 BrianL starting Dec 24 Potentially moving this meeting to handle ATLAS Tech Coordination Board conflicts Cancelling next week's meeting, to resume on Jan 4","title":"Announcements"},{"location":"meetings/2020/TechArea20201221/#triage-duty","text":"This week: BrianL Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2020/TechArea20201221/#jira","text":"# of tickets \u0394 State 133 -12 Open 12 +0 Selected for Dev 31 +6 In Progress 17 +1 Dev Complete 18 +1 Ready for Testing 7 +0 Ready for Release","title":"JIRA"},{"location":"meetings/2020/TechArea20201221/#osg-software-team","text":"Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2020/TechArea20201221/#discussion","text":"AI (BrianL): Move new site onboarding engagement Freshdesk tickets to the Operations group","title":"Discussion"},{"location":"meetings/2020/TechArea20201221/#support-update","text":"IceCube (BrianL): completing request to require Singularity for IceCube pilots; continuing a discussion with David to see how we should manage the shared IceCube/GLOW pilots MIT (BrianL): troubleshooting GPU jobs not matching, turned out to be due to an old version of HTCondor","title":"Support Update"},{"location":"meetings/2020/TechArea20201221/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January XCache(s): deployed new Wisconsin cache to osg-config repo XRootD data transfer monitor close to complete (testing and validation) GRACC (continued progress): migrating more GRACC services to Tiger documentation for the GRACC rolling update and fresh install","title":"OSG Investigations Team"},{"location":"meetings/2020/TechArea20201221/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2020/TechArea20201221/#osg-release-team","text":"3.5.29 \u0394 Status 4 +6 Open 1 -1 Selected for Development 6 +1 In Progress 5 +0 Development Complete 4 +0 Ready for Testing 0 +0 Ready for Release 20 -6 Total Software Ready for Testing 3.5.29 EL8: various things, needs review Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2020/TechArea20201221/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210104/","text":"OSG Technology Area Meeting, 4 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Derek, Marian, Mat, Tim T Announcements \u00b6 Moving this meeting to Tuesdays after standup starting next week (Jan 12) Triage Duty \u00b6 This week: BrianL Next week: Mat 12 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Switching to a rolling releases within a release series Separate upcoming repositories for 3.5 and 3.6 Docker tags switching to release/testing, tracking the RPM repos Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19 Discussion \u00b6 AI (Carl): test partial records for Condor Gratia probe AI (Carl): GHA for per-commit builds for Gratia probes Support Update \u00b6 None this week OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. Will catch up on status at later standup. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Next rolling update date? APEL Reporting - Should we update to the new AMS. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 6 +2 Open 0 -1 Selected for Development 6 +0 In Progress 5 +0 Development Complete 5 +1 Ready for Testing 0 +0 Ready for Release 22 +2 Total Software Ready for Testing 3.5.29 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 4, 2021"},{"location":"meetings/2021/TechArea20210104/#osg-technology-area-meeting-4-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Derek, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 4 January 2021"},{"location":"meetings/2021/TechArea20210104/#announcements","text":"Moving this meeting to Tuesdays after standup starting next week (Jan 12)","title":"Announcements"},{"location":"meetings/2021/TechArea20210104/#triage-duty","text":"This week: BrianL Next week: Mat 12 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210104/#jira","text":"# of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210104/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Switching to a rolling releases within a release series Separate upcoming repositories for 3.5 and 3.6 Docker tags switching to release/testing, tracking the RPM repos Tech area plates: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=19","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210104/#discussion","text":"AI (Carl): test partial records for Condor Gratia probe AI (Carl): GHA for per-commit builds for Gratia probes","title":"Discussion"},{"location":"meetings/2021/TechArea20210104/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210104/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. Will catch up on status at later standup. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Next rolling update date? APEL Reporting - Should we update to the new AMS.","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210104/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210104/#osg-release-team","text":"3.5.29 \u0394 Status 6 +2 Open 0 -1 Selected for Development 6 +0 In Progress 5 +0 Development Complete 5 +1 Ready for Testing 0 +0 Ready for Release 22 +2 Total Software Ready for Testing 3.5.29 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210104/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210112/","text":"OSG Technology Area Meeting, 12 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 Kubernetes hackathon today UCSD, UNL, UW-Madison all OOO for MLK day next Monday Triage Duty \u00b6 Freshdesk priority increased for Software team This week: Mat Next week: Carl 12 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI TimT/BrianL: Release/container policy docs Koji infrastructure setup tasks TimT noticed XRootD TPC test failures in the nightlies: Edgar added a test for multi-stream TPC that is known to be an issue and we're waiting on an upstream fix Discussion \u00b6 Marco: Testing Python 3 version of GWMS 3.9.1 (rc3); also making the periodic setup script working under Singularity. Had some difficulty splitting out HTTPD parts into a separate RPM, but fixed now. Dennis working on contacting schedds with SciTokens. Support Update \u00b6 IceCube (BrianL): having authentication/certs issues with the CHTC GWMS pool; suspecting old versions of EL6/OSG/Condor. NDSU (BrianL): will be contributing their resources via a private cloud (Lancium) and a custom scheduler; BrianL helping with registration details, and we Carl verified that we're seeing accounting records from them in Kibana. UCSD (Carl): Assist HPC cluster admins with Gratia probe issues OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 5 -1 Open 0 +0 Selected for Development 5 -1 In Progress 3 -2 Development Complete 11 +6 Ready for Testing 0 +0 Ready for Release 24 +2 Total Software Ready for Testing 3.5.29 htgettoken 1.1 osg-configure 3.11.0 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 12, 2021"},{"location":"meetings/2021/TechArea20210112/#osg-technology-area-meeting-12-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian B, Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 12 January 2021"},{"location":"meetings/2021/TechArea20210112/#announcements","text":"Kubernetes hackathon today UCSD, UNL, UW-Madison all OOO for MLK day next Monday","title":"Announcements"},{"location":"meetings/2021/TechArea20210112/#triage-duty","text":"Freshdesk priority increased for Software team This week: Mat Next week: Carl 12 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210112/#jira","text":"# of tickets \u0394 State 135 +2 Open 12 +0 Selected for Dev 29 +0 In Progress 15 +0 Dev Complete 23 +0 Ready for Testing 7 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210112/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI TimT/BrianL: Release/container policy docs Koji infrastructure setup tasks TimT noticed XRootD TPC test failures in the nightlies: Edgar added a test for multi-stream TPC that is known to be an issue and we're waiting on an upstream fix","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210112/#discussion","text":"Marco: Testing Python 3 version of GWMS 3.9.1 (rc3); also making the periodic setup script working under Singularity. Had some difficulty splitting out HTTPD parts into a separate RPM, but fixed now. Dennis working on contacting schedds with SciTokens.","title":"Discussion"},{"location":"meetings/2021/TechArea20210112/#support-update","text":"IceCube (BrianL): having authentication/certs issues with the CHTC GWMS pool; suspecting old versions of EL6/OSG/Condor. NDSU (BrianL): will be contributing their resources via a private cloud (Lancium) and a custom scheduler; BrianL helping with registration details, and we Carl verified that we're seeing accounting records from them in Kibana. UCSD (Carl): Assist HPC cluster admins with Gratia probe issues","title":"Support Update"},{"location":"meetings/2021/TechArea20210112/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210112/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210112/#osg-release-team","text":"3.5.29 \u0394 Status 5 -1 Open 0 +0 Selected for Development 5 -1 In Progress 3 -2 Development Complete 11 +6 Ready for Testing 0 +0 Ready for Release 24 +2 Total Software Ready for Testing 3.5.29 htgettoken 1.1 osg-configure 3.11.0 GlideinWMS 3.7.2 Ready for Release 3.5.29 Nothing yet Containers To Be Tested opensciencegrid/atlas-xcache:fresh opensciencegrid/frontier-squid:fresh opensciencegrid/hosted-ce:fresh opensciencegrid/stash-cache:fresh opensciencegrid/stash-origin:fresh Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210112/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210119/","text":"OSG Technology Area Meeting, 19 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Marian, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 10 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 133 -2 Open 17 +2 Selected for Dev 30 +1 In Progress 16 -3 Dev Complete 29 +4 Ready for Testing 8 +1 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT/BrianL): Release/container policy docs AI (Mat): Add support to osg-build for 3.5-upcoming AI (Carl): Set up 3.6 and 3.6-upcoming SVN branches; begin putting together 3.6 Koji tags and repos AI (Mat): Review Derek's multiuser PR AI (Carl): XRootD 5.1.0 RC5 is ready to be built and tested OSG and GLOW VO certificates expire on Feb 23 Discussion \u00b6 AI (Brian): IGTF has a new release Marco was wondering about the status of GlideinWMS 3.7.2: external testing has passed and it is ready to be released Support Update \u00b6 None this week OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.29 \u0394 Status 5 +0 Open 1 +1 Selected for Development 7 +2 In Progress 1 -1 Development Complete 11 +6 Ready for Testing 1 +1 Ready for Release 32 +8 Total Software Ready for Testing 3.5.29 Upcoming: HTCondor 8.9.11 htgettoken 1.1 osg-configure 3.11.0 Ready for Release 3.5.29 GlideinWMS 3.7.2 (EL7 Only) Data IGTF 1.109 Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 19, 2021"},{"location":"meetings/2021/TechArea20210119/#osg-technology-area-meeting-19-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Marian, TimT","title":"OSG Technology Area Meeting, 19 January 2021"},{"location":"meetings/2021/TechArea20210119/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210119/#triage-duty","text":"This week: Carl Next week: Mat 10 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210119/#jira","text":"# of tickets \u0394 State 133 -2 Open 17 +2 Selected for Dev 30 +1 In Progress 16 -3 Dev Complete 29 +4 Ready for Testing 8 +1 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210119/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT/BrianL): Release/container policy docs AI (Mat): Add support to osg-build for 3.5-upcoming AI (Carl): Set up 3.6 and 3.6-upcoming SVN branches; begin putting together 3.6 Koji tags and repos AI (Mat): Review Derek's multiuser PR AI (Carl): XRootD 5.1.0 RC5 is ready to be built and tested OSG and GLOW VO certificates expire on Feb 23","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210119/#discussion","text":"AI (Brian): IGTF has a new release Marco was wondering about the status of GlideinWMS 3.7.2: external testing has passed and it is ready to be released","title":"Discussion"},{"location":"meetings/2021/TechArea20210119/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210119/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210119/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210119/#osg-release-team","text":"3.5.29 \u0394 Status 5 +0 Open 1 +1 Selected for Development 7 +2 In Progress 1 -1 Development Complete 11 +6 Ready for Testing 1 +1 Ready for Release 32 +8 Total Software Ready for Testing 3.5.29 Upcoming: HTCondor 8.9.11 htgettoken 1.1 osg-configure 3.11.0 Ready for Release 3.5.29 GlideinWMS 3.7.2 (EL7 Only) Data IGTF 1.109 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210119/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210126/","text":"OSG Technology Area Meeting, 26 January 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 4 (-6) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 134 +1 Open 15 -2 Selected for Dev 30 +0 In Progress 21 +5 Dev Complete 21 -8 Ready for Testing 8 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Rolling release policy doc AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming OSG 3.5.30 AI (Carl): Add missing LE root cert (SOFTWARE-4436) AI (Mat): Review Derek's multiuser PR ( https://github.com/opensciencegrid/xrootd-multiuser/pull/17 ) AI (Carl): Release gratia-probe (SOFTWARE-4348) AI (Carl): Uppdate SciTokens library to 1.3.1 (SOFTWARE-4439) OSG and GLOW VO certificates expire on Feb 23 Discussion \u00b6 AI (Brian): Debug crashes in new Python 3 version of HTCondor-CE AI (Brian): Update XCache configuration to work with XRootD 5.1 Marco is testing a full GWMS system without X.509 Support Update \u00b6 Carl: Gratia Probe issues noticed by Marty Kandes (fixed) Marco: GlideinWMS issues brought up by user support OSG Investigations Team \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.30 \u0394 Status 8 +3 Open 2 +1 Selected for Development 10 +3 In Progress 4 +3 Development Complete 6 -5 Ready for Testing 1 +0 Ready for Release 31 +5 Total Software Ready for Testing 3.5.30 Upcoming: HTCondor 8.9.11 Ready for Release 3.5.30 XRootD 4.12.6 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"January 26, 2021"},{"location":"meetings/2021/TechArea20210126/#osg-technology-area-meeting-26-january-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 26 January 2021"},{"location":"meetings/2021/TechArea20210126/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210126/#triage-duty","text":"This week: Mat Next week: TimT 4 (-6) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210126/#jira","text":"# of tickets \u0394 State 134 +1 Open 15 -2 Selected for Dev 30 +0 In Progress 21 +5 Dev Complete 21 -8 Ready for Testing 8 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210126/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Rolling release policy doc AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming OSG 3.5.30 AI (Carl): Add missing LE root cert (SOFTWARE-4436) AI (Mat): Review Derek's multiuser PR ( https://github.com/opensciencegrid/xrootd-multiuser/pull/17 ) AI (Carl): Release gratia-probe (SOFTWARE-4348) AI (Carl): Uppdate SciTokens library to 1.3.1 (SOFTWARE-4439) OSG and GLOW VO certificates expire on Feb 23","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210126/#discussion","text":"AI (Brian): Debug crashes in new Python 3 version of HTCondor-CE AI (Brian): Update XCache configuration to work with XRootD 5.1 Marco is testing a full GWMS system without X.509","title":"Discussion"},{"location":"meetings/2021/TechArea20210126/#support-update","text":"Carl: Gratia Probe issues noticed by Marty Kandes (fixed) Marco: GlideinWMS issues brought up by user support","title":"Support Update"},{"location":"meetings/2021/TechArea20210126/#osg-investigations-team","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: testing close to complete, deploy in January. GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install next rolling update scheduled for the end of the month APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG Investigations Team"},{"location":"meetings/2021/TechArea20210126/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210126/#osg-release-team","text":"3.5.30 \u0394 Status 8 +3 Open 2 +1 Selected for Development 10 +3 In Progress 4 +3 Development Complete 6 -5 Ready for Testing 1 +0 Ready for Release 31 +5 Total Software Ready for Testing 3.5.30 Upcoming: HTCondor 8.9.11 Ready for Release 3.5.30 XRootD 4.12.6 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210126/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210202/","text":"OSG Technology Area Meeting, 2 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Tim T Announcements \u00b6 dHTC campus workshop Feb 8-9 OSG All Hands March 1-5 Triage Duty \u00b6 This week: TimT Next week: ??? 5 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 130 -1 Open 15 +0 Selected for Dev 32 +2 In Progress 13 -8 Dev Complete 37 +16 Ready for Testing 8 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming/3.6 AI (Mat): Token issuer packaging Release-specific devops tags voted unnecessary Time to start building! Spreadsheet incoming Still need to add token tests Dev work still needed for gratia-probe, osg-configure, and HTCondor-CE OSG 3.5.31 AI (Carl): Convert SGE Gratia probe to be Python 2/3 compatible AI (Carl): Fix repo-update-cadist link generation bug. OSG and GLOW VO certificates expire on Feb 23 AI (Mat): Help UW infrastructure team with the renewal process. Discussion \u00b6 Marco attending the CVMFS workshop; gave a presentation on cvmfs-exec yesterday. Carl will shadow Marian during the GRACC upgrade. Support Update \u00b6 Brian L: Call with Villanova about setting up a submit node dedicated to OSG. Marco: Adding a fix to the Singularity wrapper that was requested by Mats Rynge. Mat: Debugging LCMAPS for UFlorida. OSG DevOps \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: In production on tiger. Let us know if you see problems! GRACC (continued progress): GRACC Request is on tiger now. migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.31 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 -6 In Progress 2 -2 Development Complete 18 +12 Ready for Testing 5 +4 Ready for Release 39 +8 Total Software Ready for Testing 3.5.31 gratia-probe 1.22.3 osg-flock 1.3 scitokens Python library 1.3.1 Ready for Release 3.5.31 CVMFS 2.8.0 osg-release 3.5-5 XRootD 4.12.6 lcmaps for EL8 Data osg-ca-certs 1.94 Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale container tickets","title":"February 2, 2021"},{"location":"meetings/2021/TechArea20210202/#osg-technology-area-meeting-2-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Tim T","title":"OSG Technology Area Meeting, 2 February 2021"},{"location":"meetings/2021/TechArea20210202/#announcements","text":"dHTC campus workshop Feb 8-9 OSG All Hands March 1-5","title":"Announcements"},{"location":"meetings/2021/TechArea20210202/#triage-duty","text":"This week: TimT Next week: ??? 5 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210202/#jira","text":"# of tickets \u0394 State 130 -1 Open 15 +0 Selected for Dev 32 +2 In Progress 13 -8 Dev Complete 37 +16 Ready for Testing 8 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210202/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) AI (TimT): Send reminder announcement for OSG 3.6 AI (Mat): Add support to osg-build for 3.5-upcoming/3.6 AI (Mat): Token issuer packaging Release-specific devops tags voted unnecessary Time to start building! Spreadsheet incoming Still need to add token tests Dev work still needed for gratia-probe, osg-configure, and HTCondor-CE OSG 3.5.31 AI (Carl): Convert SGE Gratia probe to be Python 2/3 compatible AI (Carl): Fix repo-update-cadist link generation bug. OSG and GLOW VO certificates expire on Feb 23 AI (Mat): Help UW infrastructure team with the renewal process.","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210202/#discussion","text":"Marco attending the CVMFS workshop; gave a presentation on cvmfs-exec yesterday. Carl will shadow Marian during the GRACC upgrade.","title":"Discussion"},{"location":"meetings/2021/TechArea20210202/#support-update","text":"Brian L: Call with Villanova about setting up a submit node dedicated to OSG. Marco: Adding a fix to the Singularity wrapper that was requested by Mats Rynge. Mat: Debugging LCMAPS for UFlorida.","title":"Support Update"},{"location":"meetings/2021/TechArea20210202/#osg-devops","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page Topology: In production on tiger. Let us know if you see problems! GRACC (continued progress): GRACC Request is on tiger now. migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210202/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210202/#osg-release-team","text":"3.5.31 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 -6 In Progress 2 -2 Development Complete 18 +12 Ready for Testing 5 +4 Ready for Release 39 +8 Total Software Ready for Testing 3.5.31 gratia-probe 1.22.3 osg-flock 1.3 scitokens Python library 1.3.1 Ready for Release 3.5.31 CVMFS 2.8.0 osg-release 3.5-5 XRootD 4.12.6 lcmaps for EL8 Data osg-ca-certs 1.94 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210202/#discussion_2","text":"AI (TimT): clean up stale container tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210209/","text":"OSG Technology Area Meeting, 9 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 dHTC campus workshop today! OSG All Hands March 1-5 Mat, BrianL out this Friday Triage Duty \u00b6 This week: Carl Next week: BrianL 3 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 138 +8 Open 12 -3 Selected for Dev 34 +2 In Progress 15 +2 Dev Complete 34 -3 Ready for Testing 1 -7 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Carl, Mat): Make upcoming \u2190\u2192 3.5-upcoming switch (tomorrow 2/10) OSG 3.5.32 AI (Mat): Token issuer packaging AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25 Discussion \u00b6 Doc focus will concentrate on 3.6 documentation; those who can make it should use the whole day GlideinWMS 3.9.1 will be released later today Support Update \u00b6 Carl: Support ticket for batch vs payload core hour discrepancy (needs further investigation and will be tracked in JIRA instead) Helping Daniel Caunt at Harvard with Topology registration Working with Lincoln B to help UIUC work around CE problems caused by deletion of state at boot time Derek: Working with Purdue to try and resolve missing Gratia data caused by their SLURM database going down and the CE not creating history entries on job removal; BrianL says the latter may be by design These kinds of issues should stop happening once we move to the HTCondor-CE probe instead of the batch system probes OSG DevOps \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. XRootD Monitoring collector changes from validation. So far, just monitoring updates, no functionality changes. Will deploy as necessary. Discussion with John about persistent state Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 +0 In Progress 2 +0 Development Complete 17 -1 Ready for Testing 0 -5 Ready for Release 33 -6 Total Software Ready for Testing gratia-probe 1.22.3 (partially) osg-ce 3.5-6 xcache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale RFT tickets","title":"February 9, 2021"},{"location":"meetings/2021/TechArea20210209/#osg-technology-area-meeting-9-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 9 February 2021"},{"location":"meetings/2021/TechArea20210209/#announcements","text":"dHTC campus workshop today! OSG All Hands March 1-5 Mat, BrianL out this Friday","title":"Announcements"},{"location":"meetings/2021/TechArea20210209/#triage-duty","text":"This week: Carl Next week: BrianL 3 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210209/#jira","text":"# of tickets \u0394 State 138 +8 Open 12 -3 Selected for Dev 34 +2 In Progress 15 +2 Dev Complete 34 -3 Ready for Testing 1 -7 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210209/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Carl, Mat): Make upcoming \u2190\u2192 3.5-upcoming switch (tomorrow 2/10) OSG 3.5.32 AI (Mat): Token issuer packaging AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210209/#discussion","text":"Doc focus will concentrate on 3.6 documentation; those who can make it should use the whole day GlideinWMS 3.9.1 will be released later today","title":"Discussion"},{"location":"meetings/2021/TechArea20210209/#support-update","text":"Carl: Support ticket for batch vs payload core hour discrepancy (needs further investigation and will be tracked in JIRA instead) Helping Daniel Caunt at Harvard with Topology registration Working with Lincoln B to help UIUC work around CE problems caused by deletion of state at boot time Derek: Working with Purdue to try and resolve missing Gratia data caused by their SLURM database going down and the CE not creating history entries on job removal; BrianL says the latter may be by design These kinds of issues should stop happening once we move to the HTCondor-CE probe instead of the batch system probes","title":"Support Update"},{"location":"meetings/2021/TechArea20210209/#osg-devops","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): migrating more GRACC services to Tiger (Prometheus) documentation for the GRACC rolling update and fresh install Rolling update is starting this week. APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. XRootD Monitoring collector changes from validation. So far, just monitoring updates, no functionality changes. Will deploy as necessary. Discussion with John about persistent state","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210209/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210209/#osg-release-team","text":"3.5.32 \u0394 Status 8 +0 Open 2 +0 Selected for Development 4 +0 In Progress 2 +0 Development Complete 17 -1 Ready for Testing 0 -5 Ready for Release 33 -6 Total Software Ready for Testing gratia-probe 1.22.3 (partially) osg-ce 3.5-6 xcache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210209/#discussion_2","text":"AI (TimT): clean up stale RFT tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210216/","text":"OSG Technology Area Meeting, 16 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 OSG All Hands March 1-5 Triage Duty \u00b6 This week: BrianL Next week: Mat 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 134 -4 Open 16 +4 Selected for Dev 31 -3 In Progress 14 -1 Dev Complete 39 +5 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) New column added for EL8 success/failure AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming OSG 3.5.32 AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25 (all day if possible) Discussion \u00b6 Container backfill: GRACC can handle the new 'Execution Endpoint' service. GlideinWMS 3.9.1 is out; HTTP service has been split out of the default RPM to make containerization easier. Q (Marian): How does the factory know how much disk space is available for a slot? A (Marco): Uses what HTCondor reports (which is dynamically measured). Open HTCondor ticket (HTCONDOR-174) for adding a way to set a disk quota for a slot. HTCondor 8.9.12 will not be ready for 3.6 so we will ship 8.9.11. Support Update \u00b6 SIUE (Southern Illinois University Edwardsville) (BrianL): discussing CE support for Ubuntu CU Boulder (BrianL, Carl, Derek): some 0 CPU usage records with non-zero walltimes OSG DevOps \u00b6 OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): documentation for the GRACC rolling update and fresh install APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. Discussion of the Zoom attendees script Derek wrote. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 7 -1 Open 3 +1 Selected for Development 3 -1 In Progress 1 -1 Development Complete 22 +5 Ready for Testing 0 +0 Ready for Release 36 +3 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale RFT tickets","title":"February 16, 2021"},{"location":"meetings/2021/TechArea20210216/#osg-technology-area-meeting-16-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 16 February 2021"},{"location":"meetings/2021/TechArea20210216/#announcements","text":"OSG All Hands March 1-5","title":"Announcements"},{"location":"meetings/2021/TechArea20210216/#triage-duty","text":"This week: BrianL Next week: Mat 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210216/#jira","text":"# of tickets \u0394 State 134 -4 Open 16 +4 Selected for Dev 31 -3 In Progress 14 -1 Dev Complete 39 +5 Ready for Testing 1 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210216/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) New column added for EL8 success/failure AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming OSG 3.5.32 AI (Carl): Release Python 3 compatible gratia probe Doc Focus Feb 25 (all day if possible)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210216/#discussion","text":"Container backfill: GRACC can handle the new 'Execution Endpoint' service. GlideinWMS 3.9.1 is out; HTTP service has been split out of the default RPM to make containerization easier. Q (Marian): How does the factory know how much disk space is available for a slot? A (Marco): Uses what HTCondor reports (which is dynamically measured). Open HTCondor ticket (HTCONDOR-174) for adding a way to set a disk quota for a slot. HTCondor 8.9.12 will not be ready for 3.6 so we will ship 8.9.11.","title":"Discussion"},{"location":"meetings/2021/TechArea20210216/#support-update","text":"SIUE (Southern Illinois University Edwardsville) (BrianL): discussing CE support for Ubuntu CU Boulder (BrianL, Carl, Derek): some 0 CPU usage records with non-zero walltimes","title":"Support Update"},{"location":"meetings/2021/TechArea20210216/#osg-devops","text":"OSG Status page: Developing script to synchronize OSG contact list to subscribe the status page GRACC (continued progress): documentation for the GRACC rolling update and fresh install APEL Reporting - still investigating whether should we update to the new AMS Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches. Discussing implementation details with Tim. Discussion of the Zoom attendees script Derek wrote.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210216/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210216/#osg-release-team","text":"3.5.32 \u0394 Status 7 -1 Open 3 +1 Selected for Development 3 -1 In Progress 1 -1 Development Complete 22 +5 Ready for Testing 0 +0 Ready for Release 36 +3 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210216/#discussion_2","text":"AI (TimT): clean up stale RFT tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210223/","text":"OSG Technology Area Meeting, 23 February 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 OSG All Hands March 1-5 Triage Duty \u00b6 This week: Mat Next week: TimT 2 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira \u00b6 # of tickets \u0394 State 132 -2 Open 18 +2 Selected for Dev 34 +3 In Progress 12 -2 Dev Complete 45 +6 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (BrianL): Update osg-test to use scitokens AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Carl): Freshen the GPG key ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-3275 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Mat): osg-ca-certs-updater build for EL7 AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming Punt on osg-obsoletes and osg-next for the initial release Doc Focus Feb 25 (all day if possible) Carl: Document changes in Gratia Probe 2 and provide upgrade instructions Carl: Add material admonitions to the deprecated 3.5 documents All: Fill in upgrade instructions for OSG 3.6 components Discussion \u00b6 In the HTCondor-CE Gratia Probe ProbeConfig, the data folder should match the per-job history dir. Support Update \u00b6 SIUE (Southern Illinois University Edwardsville) (BrianL): got successful Ubuntu 20 pilots with patches to HTCondor Purdue (Carl, Derek): Custom Gratia probe to fill in gap in usage without the DN information. OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches, deployed on topology-itb. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 7 +0 Open 2 -1 Selected for Development 2 -1 In Progress 1 +0 Development Complete 24 +2 Ready for Testing 0 +0 Ready for Release 36 +0 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 AI (TimT): clean up stale RFT tickets","title":"February 23, 2021"},{"location":"meetings/2021/TechArea20210223/#osg-technology-area-meeting-23-february-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 23 February 2021"},{"location":"meetings/2021/TechArea20210223/#announcements","text":"OSG All Hands March 1-5","title":"Announcements"},{"location":"meetings/2021/TechArea20210223/#triage-duty","text":"This week: Mat Next week: TimT 2 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210223/#jira","text":"# of tickets \u0394 State 132 -2 Open 18 +2 Selected for Dev 34 +3 In Progress 12 -2 Dev Complete 45 +6 Ready for Testing 1 +0 Ready for Release","title":"Jira"},{"location":"meetings/2021/TechArea20210223/#osg-software-team","text":"OSG 3.6 deadline at the end of February ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4282 ) Package build tasks ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4475 ) AI (BrianL): Update osg-test to use scitokens AI (Carl): Consolidate Gratia probes ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4467 ) AI (Carl): Freshen the GPG key ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-3275 ) AI (Mat): Release osg-configure 4.0.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4468 ) AI (Mat): osg-ca-certs-updater build for EL7 AI (GlideinWMS devs): Build GlideinWMS for 3.6 and 3.6-upcoming Punt on osg-obsoletes and osg-next for the initial release Doc Focus Feb 25 (all day if possible) Carl: Document changes in Gratia Probe 2 and provide upgrade instructions Carl: Add material admonitions to the deprecated 3.5 documents All: Fill in upgrade instructions for OSG 3.6 components","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210223/#discussion","text":"In the HTCondor-CE Gratia Probe ProbeConfig, the data folder should match the per-job history dir.","title":"Discussion"},{"location":"meetings/2021/TechArea20210223/#support-update","text":"SIUE (Southern Illinois University Edwardsville) (BrianL): got successful Ubuntu 20 pilots with patches to HTCondor Purdue (Carl, Derek): Custom Gratia probe to fill in gap in usage without the DN information.","title":"Support Update"},{"location":"meetings/2021/TechArea20210223/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger Gratia probe update for queue time metric XRootD accounting information (from Frank): Table of working set, read, and re-read for monthly, quarterly, and year. Map of StashCache origins and caches, deployed on topology-itb.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210223/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210223/#osg-release-team","text":"3.5.32 \u0394 Status 7 +0 Open 2 -1 Selected for Development 2 -1 In Progress 1 +0 Development Complete 24 +2 Ready for Testing 0 +0 Ready for Release 36 +0 Total Software Ready for Testing gratia-probe 1.22.3 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210223/#discussion_2","text":"AI (TimT): clean up stale RFT tickets","title":"Discussion"},{"location":"meetings/2021/TechArea20210302/","text":"OSG Technology Area Meeting, 2 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Mat OOO next week BrianL OOO next Monday Triage Duty \u00b6 This week: TimT Next week: Carl (?) 4 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 131 -1 Open 14 -4 Selected for Dev 28 -6 In Progress 5 -7 Dev Complete 51 +6 Ready for Testing 10 +9 Ready for Release OSG Software Team \u00b6 OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 ) Discussion \u00b6 GlideinWMS 3.7.3 expected next week; will not include cvmfsexec integration but HTCondor version comparison bugs should be fixed. New Docker version 20.10.4 caused hung jobs all over CHTC. TimT dealing with the fallout -- others should avoid upgrading. Debian build files have been merged into scitokens-cpp; Derek should tag a new release. HTCondor 8.9.12 in progress; developers working on updating the default security configuration. Many EL8 tickets in Ready for Testing will be moved back to Open to update package versions. Support Update \u00b6 Mat: Misconfigured CVMFS/Squid at Wisconsin; Mat will register CHTC Squid in Topology; CHTC infrastructure will take care of more involved config changes. Derek: Debugging Folding@Home issues at Syracuse; likely requires Folding@Home configuration change to deal with consumer GPUs at Syracuse. Derek/Carl: Continuing to debug Purdue accounting discrepancy -- urgent because the WLCG is finalizing monthly accounting info soon. Marian: Assisting IGWN users at Georgia Tech with getting jobs running from their submit host. (https://support.opensciencegrid.org/a/tickets/66744) Marian: Debugging OASIS issues with jobs running at CRUSH. (https://support.opensciencegrid.org/a/tickets/66839) OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger (on-going) DONE: Gratia probe update for queue time metric XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. DONE: Map of StashCache origins and caches, deployed and done! Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 9 +2 Open 12 +10 Selected for Development 4 +2 In Progress 1 +0 Development Complete 14 -10 Ready for Testing 0 +0 Ready for Release 40 +4 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"March 2, 2021"},{"location":"meetings/2021/TechArea20210302/#osg-technology-area-meeting-2-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 2 March 2021"},{"location":"meetings/2021/TechArea20210302/#announcements","text":"Mat OOO next week BrianL OOO next Monday","title":"Announcements"},{"location":"meetings/2021/TechArea20210302/#triage-duty","text":"This week: TimT Next week: Carl (?) 4 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210302/#jira-as-of-monday","text":"# of tickets \u0394 State 131 -1 Open 14 -4 Selected for Dev 28 -6 In Progress 5 -7 Dev Complete 51 +6 Ready for Testing 10 +9 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210302/#osg-software-team","text":"OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210302/#discussion","text":"GlideinWMS 3.7.3 expected next week; will not include cvmfsexec integration but HTCondor version comparison bugs should be fixed. New Docker version 20.10.4 caused hung jobs all over CHTC. TimT dealing with the fallout -- others should avoid upgrading. Debian build files have been merged into scitokens-cpp; Derek should tag a new release. HTCondor 8.9.12 in progress; developers working on updating the default security configuration. Many EL8 tickets in Ready for Testing will be moved back to Open to update package versions.","title":"Discussion"},{"location":"meetings/2021/TechArea20210302/#support-update","text":"Mat: Misconfigured CVMFS/Squid at Wisconsin; Mat will register CHTC Squid in Topology; CHTC infrastructure will take care of more involved config changes. Derek: Debugging Folding@Home issues at Syracuse; likely requires Folding@Home configuration change to deal with consumer GPUs at Syracuse. Derek/Carl: Continuing to debug Purdue accounting discrepancy -- urgent because the WLCG is finalizing monthly accounting info soon. Marian: Assisting IGWN users at Georgia Tech with getting jobs running from their submit host. (https://support.opensciencegrid.org/a/tickets/66744) Marian: Debugging OASIS issues with jobs running at CRUSH. (https://support.opensciencegrid.org/a/tickets/66839)","title":"Support Update"},{"location":"meetings/2021/TechArea20210302/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger (on-going) DONE: Gratia probe update for queue time metric XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. DONE: Map of StashCache origins and caches, deployed and done!","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210302/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210302/#osg-release-team","text":"3.5.32 \u0394 Status 9 +2 Open 12 +10 Selected for Development 4 +2 In Progress 1 +0 Development Complete 14 -10 Ready for Testing 0 +0 Ready for Release 40 +4 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.1 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210302/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210309/","text":"OSG Technology Area Meeting, 9 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, TimT Announcements \u00b6 Mat OOO this week Triage Duty \u00b6 This week: Carl Next week: BrianL 7 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 133 +2 Open 23 +9 Selected for Dev 28 +0 In Progress 5 +0 Dev Complete 20 -31 Ready for Testing 1 -9 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today 2-6pm Central OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Gratia probe 1.23.2 with fixe to QueueTime collection AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 ) Discussion \u00b6 We only need to build xrootd-hdfs build for 3.5 EL7 upcoming, can be ignored for 3.6 and 3.5 EL8 upcoming Support Update \u00b6 AGLT2 (BrianL): helped them downgrade to OSG 3.5 after an upgrade to 3.6. In addition to downgrading RPMs, they had to uncomment the line in /etc/grid-security/gsi-authz.conf to re-enable LCMAPS Purdue (BrianL): ran into issues with the new supervisord backfill container not having rootly permissions Purdue (Carl, Derek): made custom Gratia probe to generate missed February records OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger (pull request submitted) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics writing is ongoing for user \"wait time\" Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"March 9, 2021"},{"location":"meetings/2021/TechArea20210309/#osg-technology-area-meeting-9-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, TimT","title":"OSG Technology Area Meeting, 9 March 2021"},{"location":"meetings/2021/TechArea20210309/#announcements","text":"Mat OOO this week","title":"Announcements"},{"location":"meetings/2021/TechArea20210309/#triage-duty","text":"This week: Carl Next week: BrianL 7 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210309/#jira-as-of-monday","text":"# of tickets \u0394 State 133 +2 Open 23 +9 Selected for Dev 28 +0 In Progress 5 +0 Dev Complete 20 -31 Ready for Testing 1 -9 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210309/#osg-software-team","text":"Kubernetes Hackathon today 2-6pm Central OSG 3.6 next AI (Carl): Release XRootD in OSG 3.6 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4494 ) AI (BrianL): Issues with the blahp AI (Mat): Investigate GlideinWMS Globus dependencies (GlideinWMS 3.9 built into 3.6 upcoming development) OSG 3.5.32 AI (Carl): Gratia probe 1.23.2 with fixe to QueueTime collection AI (Carl): Release XRootD 5.1.0 ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4356 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210309/#discussion","text":"We only need to build xrootd-hdfs build for 3.5 EL7 upcoming, can be ignored for 3.6 and 3.5 EL8 upcoming","title":"Discussion"},{"location":"meetings/2021/TechArea20210309/#support-update","text":"AGLT2 (BrianL): helped them downgrade to OSG 3.5 after an upgrade to 3.6. In addition to downgrading RPMs, they had to uncomment the line in /etc/grid-security/gsi-authz.conf to re-enable LCMAPS Purdue (BrianL): ran into issues with the new supervisord backfill container not having rootly permissions Purdue (Carl, Derek): made custom Gratia probe to generate missed February records","title":"Support Update"},{"location":"meetings/2021/TechArea20210309/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger (pull request submitted) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics writing is ongoing for user \"wait time\"","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210309/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210309/#osg-release-team","text":"3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210309/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210323/","text":"OSG Technology Area Meeting, 23 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco, Marian, Mat, TimT Announcements \u00b6 Kubernetes Hackathon today 1-5pm TimT OOO starting Mar 26, returning Apr 6 Triage Duty \u00b6 This week: TimT Next week: Mat 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 136 +4 Open 12 -2 Selected for Dev 27 -7 In Progress 9 +4 Dev Complete 39 +9 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 AI (Carl, with help from Mat): Enable networking in Koji builds Kubernetes Hackathon AI (Mat): put together Hosted CE submitting to the CHTC Slurm cluster AI (Carl): create koji builder pod in production namespace AI (BrianL): deploy ITB central collector Discussion \u00b6 The new version of HTCondor-CE 5 should be pulled from testing due to bugs found. AI (Marco): Add check to frontend to make sure the VOMS signing certificate is valid. Support Update \u00b6 SDSC Expanse (BrianL): Released production tarballs are broken for the OSG case but there is a workaround for Hosted CEs Marian: Public links to Freshdesk tickets don't work for some people; the workaround for them is to use incognito mode. Freshdesk refuses to fix the issue so for now we have to remind people to use incognito mode. Purdue records (Derek, Carl): Gratia probe seemed to be sending records for local usage, not just OSG. Carl will investigate and provide a software fix. LBL (Carl): Continuing to help with Squid registration; some of their Squids are internal and should not be registered. OSG DevOps \u00b6 OSG Status page: Moving synchronization to Tiger, merged. XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics: Waittime has gone through a few iterations. Pull request ready for review: https://github.com/path-cc/metric-tools/pull/22 Discussion \u00b6 gracc-status RPM can be dropped from OSG devops repo, but gracc-archive RPM should be kept. OSG Release Team \u00b6 3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"March 23, 2021"},{"location":"meetings/2021/TechArea20210323/#osg-technology-area-meeting-23-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 23 March 2021"},{"location":"meetings/2021/TechArea20210323/#announcements","text":"Kubernetes Hackathon today 1-5pm TimT OOO starting Mar 26, returning Apr 6","title":"Announcements"},{"location":"meetings/2021/TechArea20210323/#triage-duty","text":"This week: TimT Next week: Mat 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210323/#jira-as-of-monday","text":"# of tickets \u0394 State 136 +4 Open 12 -2 Selected for Dev 27 -7 In Progress 9 +4 Dev Complete 39 +9 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210323/#osg-software-team","text":"AI (Carl, with help from Mat): Enable networking in Koji builds Kubernetes Hackathon AI (Mat): put together Hosted CE submitting to the CHTC Slurm cluster AI (Carl): create koji builder pod in production namespace AI (BrianL): deploy ITB central collector","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210323/#discussion","text":"The new version of HTCondor-CE 5 should be pulled from testing due to bugs found. AI (Marco): Add check to frontend to make sure the VOMS signing certificate is valid.","title":"Discussion"},{"location":"meetings/2021/TechArea20210323/#support-update","text":"SDSC Expanse (BrianL): Released production tarballs are broken for the OSG case but there is a workaround for Hosted CEs Marian: Public links to Freshdesk tickets don't work for some people; the workaround for them is to use incognito mode. Freshdesk refuses to fix the issue so for now we have to remind people to use incognito mode. Purdue records (Derek, Carl): Gratia probe seemed to be sending records for local usage, not just OSG. Carl will investigate and provide a software fix. LBL (Carl): Continuing to help with Squid registration; some of their Squids are internal and should not be registered.","title":"Support Update"},{"location":"meetings/2021/TechArea20210323/#osg-devops","text":"OSG Status page: Moving synchronization to Tiger, merged. XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. PATh metrics: Waittime has gone through a few iterations. Pull request ready for review: https://github.com/path-cc/metric-tools/pull/22","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210323/#discussion_1","text":"gracc-status RPM can be dropped from OSG devops repo, but gracc-archive RPM should be kept.","title":"Discussion"},{"location":"meetings/2021/TechArea20210323/#osg-release-team","text":"3.5.32 \u0394 Status 10 +1 Open 12 +0 Selected for Development 4 +0 In Progress 1 +0 Development Complete 14 +0 Ready for Testing 0 +0 Ready for Release 41 +1 Total Software Ready for Testing gratia-probe 1.23.2 osg-ce 3.5-6 osg-scitokens-mapfile 1 cmvfs-gateway 1.2.0 HTCondor-CE 4.5.0 vault 1.6.2 htvault-config 0.5 Upcoming: HTCondor-CE 5.0.0 Upcoming: XCache 2.0.0 Ready for Release Nothing Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210323/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210330/","text":"OSG Technology Area Meeting, 30 March 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Jason Patton, Marco, Marian, Mat Announcements \u00b6 IRIS-HEP full team retreat Apr 27-30 canceled TimT OOO, returning Apr 6 Triage Duty \u00b6 This week: Mat Next week: BrianL (?) 7 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 139 +3 Open 15 +3 Selected for Dev 27 +0 In Progress 8 -1 Dev Complete 29 -10 Ready for Testing 9 +8 Ready for Release OSG Software Team \u00b6 OSG 3.5.33/3.6 xrootd-multiuser is broken for XRootD 5. Should we delay the release? osg-xrootd needs to be updated to fix its use of ofs.authlib Anything else we should document in the update notes? AI (Carl): Rebuild condor RPM AI (Mat): Add multiple config directories to HTCondor packaging AI (Carl, with help from Mat): Enable networking in Koji builds AI (Mat): Finish adding CVMFS to the OSG backfill container Discussion \u00b6 kojibuilder2 (new K8s builder in the production namespace) not reporting to the koji hub. GlideinWMS: 3.7.3 release candidate is in testing. New 3.9 release needed to fix the following bugs: https://cdcvs.fnal.gov/redmine/issues/25620, https://cdcvs.fnal.gov/redmine/issues/25619 String encoding issue at glideFactoryLib.py, Update LDAP module for Python 3, both affect only AWS submission, not regular grid submission. Support Update \u00b6 Chameleon Cloud (BrianL): investigating an issue where the OSG validation script is failing so the container isn't running jobs Purdue (Carl, Derek): Derek successfully removed the errant local records for Purdue; Carl will ask Purdue to re-run the custom Gratia probe he provided to them. AMNH (Derek): Assisting them with SLURM configuration. Might be worthwhile to write a 'recommended SLURM configuration' document, even if it's not widely publicized. OzSTAR (Marian): Assisting them with stash cache setup. OSG DevOps \u00b6 XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming Discussion \u00b6 None this week","title":"March 30, 2021"},{"location":"meetings/2021/TechArea20210330/#osg-technology-area-meeting-30-march-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Jason Patton, Marco, Marian, Mat","title":"OSG Technology Area Meeting, 30 March 2021"},{"location":"meetings/2021/TechArea20210330/#announcements","text":"IRIS-HEP full team retreat Apr 27-30 canceled TimT OOO, returning Apr 6","title":"Announcements"},{"location":"meetings/2021/TechArea20210330/#triage-duty","text":"This week: Mat Next week: BrianL (?) 7 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210330/#jira-as-of-monday","text":"# of tickets \u0394 State 139 +3 Open 15 +3 Selected for Dev 27 +0 In Progress 8 -1 Dev Complete 29 -10 Ready for Testing 9 +8 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210330/#osg-software-team","text":"OSG 3.5.33/3.6 xrootd-multiuser is broken for XRootD 5. Should we delay the release? osg-xrootd needs to be updated to fix its use of ofs.authlib Anything else we should document in the update notes? AI (Carl): Rebuild condor RPM AI (Mat): Add multiple config directories to HTCondor packaging AI (Carl, with help from Mat): Enable networking in Koji builds AI (Mat): Finish adding CVMFS to the OSG backfill container","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210330/#discussion","text":"kojibuilder2 (new K8s builder in the production namespace) not reporting to the koji hub. GlideinWMS: 3.7.3 release candidate is in testing. New 3.9 release needed to fix the following bugs: https://cdcvs.fnal.gov/redmine/issues/25620, https://cdcvs.fnal.gov/redmine/issues/25619 String encoding issue at glideFactoryLib.py, Update LDAP module for Python 3, both affect only AWS submission, not regular grid submission.","title":"Discussion"},{"location":"meetings/2021/TechArea20210330/#support-update","text":"Chameleon Cloud (BrianL): investigating an issue where the OSG validation script is failing so the container isn't running jobs Purdue (Carl, Derek): Derek successfully removed the errant local records for Purdue; Carl will ask Purdue to re-run the custom Gratia probe he provided to them. AMNH (Derek): Assisting them with SLURM configuration. Might be worthwhile to write a 'recommended SLURM configuration' document, even if it's not widely publicized. OzSTAR (Marian): Assisting them with stash cache setup.","title":"Support Update"},{"location":"meetings/2021/TechArea20210330/#osg-devops","text":"XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210330/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210330/#osg-release-team","text":"Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210330/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210406/","text":"OSG Technology Area Meeting, 6 April 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 138 -1 Open 15 +0 Selected for Dev 26 -1 In Progress 12 +3 Dev Complete 26 -3 Ready for Testing 0 -9 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today at 1pm, same coordinates AI (Carl): Fix kojibuilder2, test prescribed token location container AI (Mat): CHTC \"Canary\" SLURM CE OSG 3.5.33/3.6 AI (BrianL): Build blahp 2.0.0 Discussion \u00b6 AI (BrianL): Review XRootD software support policy. HTCondor 8.9.13 has been tested but we are likely to skip it since 9.0.0 is imminent and we're waiting on upgrade instructions from the developers. Support Update \u00b6 Carl: Continuing to work with Purdue on accounting; waiting for logs. Mat: Helping ICTS-TIFR (LIGO site in India) with Topology registartion. OSG DevOps \u00b6 XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming Discussion \u00b6 None this week","title":"April 6, 2021"},{"location":"meetings/2021/TechArea20210406/#osg-technology-area-meeting-6-april-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 6 April 2021"},{"location":"meetings/2021/TechArea20210406/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210406/#triage-duty","text":"This week: BrianL Next week: Carl 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210406/#jira-as-of-monday","text":"# of tickets \u0394 State 138 -1 Open 15 +0 Selected for Dev 26 -1 In Progress 12 +3 Dev Complete 26 -3 Ready for Testing 0 -9 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210406/#osg-software-team","text":"Kubernetes hackathon today at 1pm, same coordinates AI (Carl): Fix kojibuilder2, test prescribed token location container AI (Mat): CHTC \"Canary\" SLURM CE OSG 3.5.33/3.6 AI (BrianL): Build blahp 2.0.0","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210406/#discussion","text":"AI (BrianL): Review XRootD software support policy. HTCondor 8.9.13 has been tested but we are likely to skip it since 9.0.0 is imminent and we're waiting on upgrade instructions from the developers.","title":"Discussion"},{"location":"meetings/2021/TechArea20210406/#support-update","text":"Carl: Continuing to work with Purdue on accounting; waiting for logs. Mat: Helping ICTS-TIFR (LIGO site in India) with Topology registartion.","title":"Support Update"},{"location":"meetings/2021/TechArea20210406/#osg-devops","text":"XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210406/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210406/#osg-release-team","text":"Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210406/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210413/","text":"OSG Technology Area Meeting, 13 April 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T Announcements \u00b6 BrianL out this Thu/Fri Marian on extended leave Triage Duty \u00b6 This week: Carl Next week: Mat 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 143 +5 Open 14 -1 Selected for Dev 27 +1 In Progress 12 +0 Dev Complete 28 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.5.33/3.6 AI (Carl): Promote Frontier Squid to testing AI (Carl): Rebuild Blahp 2.0.1 in OSG 3.6 AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Mat): Build HTCondor-CE 5.1.0 once released upstream AI (Carl): Kick off VMU tests for htvault-config and htgettoken AI (Mat): Debug Tiger Slurm Hosted CE failure to start Discussion \u00b6 None this week Support Update \u00b6 SIUE (BrianL): they're trying out a self-hosted CE in front of their Ubuntu 20 cluster University of Tennessee Chattanooga (BrianL): multi-VO Hosted CEs don't work because HTCondor-CE sets HOME from the CE by default. Fixed in to-be-released versions of HTCondor-CE Lancium (Mat): debug low contributions after updating to the latest backfill container image OSG DevOps \u00b6 XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming Discussion \u00b6 None this week","title":"April 13, 2021"},{"location":"meetings/2021/TechArea20210413/#osg-technology-area-meeting-13-april-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 13 April 2021"},{"location":"meetings/2021/TechArea20210413/#announcements","text":"BrianL out this Thu/Fri Marian on extended leave","title":"Announcements"},{"location":"meetings/2021/TechArea20210413/#triage-duty","text":"This week: Carl Next week: Mat 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210413/#jira-as-of-monday","text":"# of tickets \u0394 State 143 +5 Open 14 -1 Selected for Dev 27 +1 In Progress 12 +0 Dev Complete 28 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210413/#osg-software-team","text":"OSG 3.5.33/3.6 AI (Carl): Promote Frontier Squid to testing AI (Carl): Rebuild Blahp 2.0.1 in OSG 3.6 AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Mat): Build HTCondor-CE 5.1.0 once released upstream AI (Carl): Kick off VMU tests for htvault-config and htgettoken AI (Mat): Debug Tiger Slurm Hosted CE failure to start","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210413/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210413/#support-update","text":"SIUE (BrianL): they're trying out a self-hosted CE in front of their Ubuntu 20 cluster University of Tennessee Chattanooga (BrianL): multi-VO Hosted CEs don't work because HTCondor-CE sets HOME from the CE by default. Fixed in to-be-released versions of HTCondor-CE Lancium (Mat): debug low contributions after updating to the latest backfill container image","title":"Support Update"},{"location":"meetings/2021/TechArea20210413/#osg-devops","text":"XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210413/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210413/#osg-release-team","text":"Need to send ready for testing email today Aiming to release XRootD 5 this week, at least in 3.5 upcoming","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210413/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210420/","text":"OSG Technology Area Meeting, 20 April 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T Announcements \u00b6 Mat out Friday and next Monday Triage Duty \u00b6 This week: Mat Next week: Tim 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 143 +0 Open 18 +4 Selected for Dev 28 +1 In Progress 10 -2 Dev Complete 17 -11 Ready for Testing 14 +14 Ready for Release OSG Software Team \u00b6 Need highlights of accomplishments since Jan 13 for AC meeting Kubernetes hackathon this afternoon AI (Brian): Test latest Bosco tarballs AI (Mat): Debug Tiger Slurm Hosted CE failure to start AI (Carl): Test Hosted CE SciTokens changes Doc focus this Thursday starting at 1:30pm OSG 3.5.33/3.6 AI (Brian): Kick off HTCondor-CE/HTCondor VMU tests AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Carl): Kick off VMU tests for htvault-config Discussion \u00b6 None this week Support Update \u00b6 Purdue (Carl): discuss with Derek if it's acceptable to interpolate missing data; note that the switch from batch system probes to the HTCondor-CE probe in OSG 3.6 should prevent issues like this in the future. Lancium (Mat): debug low contributions after updating to the latest backfill container image OSG Release Team \u00b6 3.5.34 \u0394 Status 10 +0 Open 5 +0 Selected for Development 3 +0 In Progress 5 +0 Development Complete 8 +0 Ready for Testing 14 +0 Ready for Release 45 +0 Total Software Ready for Testing frontier-squid-4.13-5.1 HTCondor 8.8.13 vault 1.7.0 osg-xrootd for EL8 osg-gridftp for EL8 Upcoming: xrootd-hdfs 2.2.0 Ready for Release CVMFS 2.8.1 gratia-probe 1.23.2 Data vo-client 111 Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"April 20, 2021"},{"location":"meetings/2021/TechArea20210420/#osg-technology-area-meeting-20-april-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Marco Mambelli, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 20 April 2021"},{"location":"meetings/2021/TechArea20210420/#announcements","text":"Mat out Friday and next Monday","title":"Announcements"},{"location":"meetings/2021/TechArea20210420/#triage-duty","text":"This week: Mat Next week: Tim 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210420/#jira-as-of-monday","text":"# of tickets \u0394 State 143 +0 Open 18 +4 Selected for Dev 28 +1 In Progress 10 -2 Dev Complete 17 -11 Ready for Testing 14 +14 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210420/#osg-software-team","text":"Need highlights of accomplishments since Jan 13 for AC meeting Kubernetes hackathon this afternoon AI (Brian): Test latest Bosco tarballs AI (Mat): Debug Tiger Slurm Hosted CE failure to start AI (Carl): Test Hosted CE SciTokens changes Doc focus this Thursday starting at 1:30pm OSG 3.5.33/3.6 AI (Brian): Kick off HTCondor-CE/HTCondor VMU tests AI (Mat): Push GlideinWMS 3.7.3 to testing when it's ready, coordinate with Mats and Jeff Dost AI (Carl): Kick off VMU tests for htvault-config","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210420/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210420/#support-update","text":"Purdue (Carl): discuss with Derek if it's acceptable to interpolate missing data; note that the switch from batch system probes to the HTCondor-CE probe in OSG 3.6 should prevent issues like this in the future. Lancium (Mat): debug low contributions after updating to the latest backfill container image","title":"Support Update"},{"location":"meetings/2021/TechArea20210420/#osg-release-team","text":"3.5.34 \u0394 Status 10 +0 Open 5 +0 Selected for Development 3 +0 In Progress 5 +0 Development Complete 8 +0 Ready for Testing 14 +0 Ready for Release 45 +0 Total Software Ready for Testing frontier-squid-4.13-5.1 HTCondor 8.8.13 vault 1.7.0 osg-xrootd for EL8 osg-gridftp for EL8 Upcoming: xrootd-hdfs 2.2.0 Ready for Release CVMFS 2.8.1 gratia-probe 1.23.2 Data vo-client 111 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210420/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210504/","text":"OSG Technology Area Meeting, 4 May 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Mat, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Carl 5 (-6) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 147 +6 Open 11 -1 Selected for Dev 23 -4 In Progress 16 +4 Dev Complete 24 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon this afternoon AI (Brian): Test Hosted CE PVCs AI (Mat): Update Ubuntu WN containers and automate pushes to the OSG Harbor instance AI (Carl): Fixup production Koji builder OSG 3.5.35/3.5.36/3.6 AI (Carl): Build new XCache for upcoming/3.6 (SOFTWARE-4476) Time to get to work on verifying EL8 packages (SOFTWARE-3308) Discussion \u00b6 hosted-ce35 not reporting in - Carl to investigate since it's running the Python 3 version of the Gratia probe. Support Update \u00b6 BrianL, Mat - Lancium was seeing multiple issues for backfill containers; one of the issues was having newlines in the token, which caused HTCondor to report failure to parse. Will ask developers how HTCondor parses tokens. Carl - Purdue's gap records will be filled in from the previous day. OSG Release Team \u00b6 3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 -1 0 +0 3 +3 12 +2 Open 2 +0 2 -1 1 +1 5 +0 Selected for Development 0 +0 2 +1 3 +1 5 +2 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 7 +6 12 +6 1 +0 20 +12 Ready for Testing 0 -13 0 -1 0 +0 0 -14 Ready for Release 20 -8 19 +5 8 +5 47 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.13-5.2 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing Discussion \u00b6 HTCondor 9.0.0 bug: AES encryption + x509 proxy refresh crashes the starter. Brian L will discuss it with developers to see if it affects the OSG infrastructure. This may be fixed in 9.0.1 (expected next week); if not, we will mention it as a known issue in the release notes.","title":"May 4, 2021"},{"location":"meetings/2021/TechArea20210504/#osg-technology-area-meeting-4-may-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Mat, Tim T","title":"OSG Technology Area Meeting, 4 May 2021"},{"location":"meetings/2021/TechArea20210504/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210504/#triage-duty","text":"This week: Brian Next week: Carl 5 (-6) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210504/#jira-as-of-monday","text":"# of tickets \u0394 State 147 +6 Open 11 -1 Selected for Dev 23 -4 In Progress 16 +4 Dev Complete 24 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210504/#osg-software-team","text":"Kubernetes hackathon this afternoon AI (Brian): Test Hosted CE PVCs AI (Mat): Update Ubuntu WN containers and automate pushes to the OSG Harbor instance AI (Carl): Fixup production Koji builder OSG 3.5.35/3.5.36/3.6 AI (Carl): Build new XCache for upcoming/3.6 (SOFTWARE-4476) Time to get to work on verifying EL8 packages (SOFTWARE-3308)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210504/#discussion","text":"hosted-ce35 not reporting in - Carl to investigate since it's running the Python 3 version of the Gratia probe.","title":"Discussion"},{"location":"meetings/2021/TechArea20210504/#support-update","text":"BrianL, Mat - Lancium was seeing multiple issues for backfill containers; one of the issues was having newlines in the token, which caused HTCondor to report failure to parse. Will ask developers how HTCondor parses tokens. Carl - Purdue's gap records will be filled in from the previous day.","title":"Support Update"},{"location":"meetings/2021/TechArea20210504/#osg-release-team","text":"3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 -1 0 +0 3 +3 12 +2 Open 2 +0 2 -1 1 +1 5 +0 Selected for Development 0 +0 2 +1 3 +1 5 +2 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 7 +6 12 +6 1 +0 20 +12 Ready for Testing 0 -13 0 -1 0 +0 0 -14 Ready for Release 20 -8 19 +5 8 +5 47 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.13-5.2 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210504/#discussion_1","text":"HTCondor 9.0.0 bug: AES encryption + x509 proxy refresh crashes the starter. Brian L will discuss it with developers to see if it affects the OSG infrastructure. This may be fixed in 9.0.1 (expected next week); if not, we will mention it as a known issue in the release notes.","title":"Discussion"},{"location":"meetings/2021/TechArea20210511/","text":"OSG Technology Area Meeting, 11 May 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Mat, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 11 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 149 +2 Open 15 +4 Selected for Dev 32 +9 In Progress 12 -4 Dev Complete 25 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 GSI Transition AI (Carl): will Gratia ignore SciTokens-based pilots? AI (Carl): HTCondor-CE Gratia probe should avoid use of condor_ce_q XRootD in 3.6 Need to document native VOMS and SciTokens auth. Upstream docs? SciTokens osg-xrootd needs to be updated (at least removing LCMAPS + config) Topology changes probably need to be made to also support the new format Any new sites/CEs should be directed to the \"Campus Facilitation\" FD group Discussion \u00b6 HTCondor service startup tests in osg-test for 9.0.1 need updates to work with new upstream configuration. XRootD-TPC tests should be split into single-stream and multi-stream. GlideinWMS: GlideinWMS 3.7.4rc1 now available; fixes a regression with 3.6 frontend compatibility. OSG Scitokens patches, X509-less submission, and CVMFSEXEC will go into 3.7.5. 3.7.5 expected in a month and a half. Redmine currently locked down to people with service accounts. Some issues can be tracked in GitHub. Future authentication policy has not been decided yet. Support Update \u00b6 (Mat) Justas at CalTech is having STARTD_CRON issues; investigating with help from the HTCondor developers. (Derek) ORNL is running a patched slurm gratia probe. We should engage with them to run a production probe, if we can. But their use case complicates things. OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu... Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 3 +0 13 +1 Open 2 +0 1 -1 1 +0 4 -1 Selected for Development 0 +0 3 +1 3 +0 6 +1 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 8 +1 12 +0 1 +0 21 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 20 +1 20 +1 8 +0 49 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.15-1.1 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"May 11, 2021"},{"location":"meetings/2021/TechArea20210511/#osg-technology-area-meeting-11-may-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Mat, Tim T","title":"OSG Technology Area Meeting, 11 May 2021"},{"location":"meetings/2021/TechArea20210511/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210511/#triage-duty","text":"This week: Carl Next week: Mat 11 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210511/#jira-as-of-monday","text":"# of tickets \u0394 State 149 +2 Open 15 +4 Selected for Dev 32 +9 In Progress 12 -4 Dev Complete 25 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210511/#osg-software-team","text":"GSI Transition AI (Carl): will Gratia ignore SciTokens-based pilots? AI (Carl): HTCondor-CE Gratia probe should avoid use of condor_ce_q XRootD in 3.6 Need to document native VOMS and SciTokens auth. Upstream docs? SciTokens osg-xrootd needs to be updated (at least removing LCMAPS + config) Topology changes probably need to be made to also support the new format Any new sites/CEs should be directed to the \"Campus Facilitation\" FD group","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210511/#discussion","text":"HTCondor service startup tests in osg-test for 9.0.1 need updates to work with new upstream configuration. XRootD-TPC tests should be split into single-stream and multi-stream. GlideinWMS: GlideinWMS 3.7.4rc1 now available; fixes a regression with 3.6 frontend compatibility. OSG Scitokens patches, X509-less submission, and CVMFSEXEC will go into 3.7.5. 3.7.5 expected in a month and a half. Redmine currently locked down to people with service accounts. Some issues can be tracked in GitHub. Future authentication policy has not been decided yet.","title":"Discussion"},{"location":"meetings/2021/TechArea20210511/#support-update","text":"(Mat) Justas at CalTech is having STARTD_CRON issues; investigating with help from the HTCondor developers. (Derek) ORNL is running a patched slurm gratia probe. We should engage with them to run a production probe, if we can. But their use case complicates things.","title":"Support Update"},{"location":"meetings/2021/TechArea20210511/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu... Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210511/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210511/#osg-release-team","text":"3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 3 +0 13 +1 Open 2 +0 1 -1 1 +0 4 -1 Selected for Development 0 +0 3 +1 3 +0 6 +1 In Progress 2 +0 3 +0 0 +0 5 +0 Development Complete 8 +1 12 +0 1 +0 21 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 20 +1 20 +1 8 +0 49 +2 Total Software Ready for Testing voms 2.0.16 (EL7), voms 2.1.0-rc1 (EL8) frontier-squid 4.15-1.1 HTCondor 8.8.13 HTCondor-CE 4.5.2 Vault-1.7.1 Htgettoken 1.2 and htvault-config 0.7 Osg-scitokens-mapfile 3 EL8 osg-xrootd Osg-gridftp XRootD 5 XCache SciTokens Cilogon-openid-ca-cert Upcoming GlideinWMS 3.7.3 Upcoming + 3.6 HTCondor 9.0.0-1.5 HTCondor-CE 5.1.0 blahp 2.0.2 Ready for Release Nothing yet Data IGTF 1.110 vo-client 112 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210511/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210518/","text":"OSG Technology Area Meeting, 18 May 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim Announcements \u00b6 Next week's meeting canceled for HTCondor week, to resume June 1 BrianL OOO May 28 and June 1 Triage Duty \u00b6 This week: Mat Next week: TimT 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 155 +6 Open 16 +1 Selected for Dev 31 -1 In Progress 12 +0 Dev Complete 9 -16 Ready for Testing 11 +11 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34&sprint=32 AI (Carl): Production Koji builder Release AI (Mat): osg-xrootd and documentation need to be updated to use the voms-xrootd-plugin for 3.6 AI (Mat): XRootD for EL8 AI (Carl): Gratia probe Hosted CE quarantine issues AI (Carl): Gratia probe collection of VO data for token-based pilots Do we need to update the Gratia dirs for OSG 3.6? https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 Discussion \u00b6 Nightly XRootD multistream TPC tests are still failing; Derek will investigate since it might be related to xrootd-multiuser. However, this may have only been used for performance tests; Derek will ask Brian B. about real-world use cases and adjust priority accordingly. xrootd-multiuser 1.0.1 expected soon. SciTokens VO mapping: right now, pilots contain both X.509 and SciTokens credentials; Gratia prefers the former, so it may be difficult to do an integration test; adding unit tests will provide sufficient coverage for now. AI (Carl): Run VMU tests for GlideinWMS 3.7.4. Support Update \u00b6 Hosted CEs (BrianL): cert-manager changes (?) resulted in a slightly different LE chain being advertised from the CEs, requiring an update to osg-ca-certs-1.96 on the client side XRootD (Derek): Justas opened tickets with XRootD, watching to see if OSG can contribute to debugging / development for fixes. OzStar (Marian): Debugging Singularity; this may be due to attempting to run unprivileged Singularity without user namespaces. The ticket should be reassigned to the Software group; Dave Dykstra may be able to help. CalTech (Mat): Problem with long lines in STARTD_CRON output causing startd ads not to get updated; created HTCondor ticket to fix and gave Justas a workaround. LBL (Carl): Continuing to support LBL with setting up Squid. Dave Dykstra may be able to help. OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira GRACC S3 (CEPH) backup coming up, will coordinate a disaster recovery drill. XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 2 +1 5 +2 16 +3 Open 5 +3 1 +0 1 +0 7 +3 Selected for Development 0 +0 2 -1 2 -1 4 -2 In Progress 3 +1 1 -2 0 +0 4 -1 Development Complete 5 -3 2 -10 0 -1 7 -14 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 22 +1 8 -12 8 +0 38 -11 Total Software Ready for Testing OSG 3.5 HTCondor-CE 4.5.2 osg-gridftp on EL8 OSG 3.5-upcoming HTCondor 9.0.1 GlideinWMS 3.7.4 XRootD 5.2.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.1 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"May 18, 2021"},{"location":"meetings/2021/TechArea20210518/#osg-technology-area-meeting-18-may-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim","title":"OSG Technology Area Meeting, 18 May 2021"},{"location":"meetings/2021/TechArea20210518/#announcements","text":"Next week's meeting canceled for HTCondor week, to resume June 1 BrianL OOO May 28 and June 1","title":"Announcements"},{"location":"meetings/2021/TechArea20210518/#triage-duty","text":"This week: Mat Next week: TimT 12 (+2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210518/#jira-as-of-monday","text":"# of tickets \u0394 State 155 +6 Open 16 +1 Selected for Dev 31 -1 In Progress 12 +0 Dev Complete 9 -16 Ready for Testing 11 +11 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210518/#osg-software-team","text":"Kubernetes Hackathon this afternoon: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34&sprint=32 AI (Carl): Production Koji builder Release AI (Mat): osg-xrootd and documentation need to be updated to use the voms-xrootd-plugin for 3.6 AI (Mat): XRootD for EL8 AI (Carl): Gratia probe Hosted CE quarantine issues AI (Carl): Gratia probe collection of VO data for token-based pilots Do we need to update the Gratia dirs for OSG 3.6? https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210518/#discussion","text":"Nightly XRootD multistream TPC tests are still failing; Derek will investigate since it might be related to xrootd-multiuser. However, this may have only been used for performance tests; Derek will ask Brian B. about real-world use cases and adjust priority accordingly. xrootd-multiuser 1.0.1 expected soon. SciTokens VO mapping: right now, pilots contain both X.509 and SciTokens credentials; Gratia prefers the former, so it may be difficult to do an integration test; adding unit tests will provide sufficient coverage for now. AI (Carl): Run VMU tests for GlideinWMS 3.7.4.","title":"Discussion"},{"location":"meetings/2021/TechArea20210518/#support-update","text":"Hosted CEs (BrianL): cert-manager changes (?) resulted in a slightly different LE chain being advertised from the CEs, requiring an update to osg-ca-certs-1.96 on the client side XRootD (Derek): Justas opened tickets with XRootD, watching to see if OSG can contribute to debugging / development for fixes. OzStar (Marian): Debugging Singularity; this may be due to attempting to run unprivileged Singularity without user namespaces. The ticket should be reassigned to the Software group; Dave Dykstra may be able to help. CalTech (Mat): Problem with long lines in STARTD_CRON output causing startd ads not to get updated; created HTCondor ticket to fix and gave Justas a workaround. LBL (Carl): Continuing to support LBL with setting up Squid. Dave Dykstra may be able to help.","title":"Support Update"},{"location":"meetings/2021/TechArea20210518/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira GRACC S3 (CEPH) backup coming up, will coordinate a disaster recovery drill. XRootD Multiuser: One more comment from Andy, so there will be a 1.0.1 (sorry) Known not to work with xrootd async io. But that might be ok. StashCP go client is working, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210518/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210518/#osg-release-team","text":"3.5.35 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 2 +1 5 +2 16 +3 Open 5 +3 1 +0 1 +0 7 +3 Selected for Development 0 +0 2 -1 2 -1 4 -2 In Progress 3 +1 1 -2 0 +0 4 -1 Development Complete 5 -3 2 -10 0 -1 7 -14 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 22 +1 8 -12 8 +0 38 -11 Total Software Ready for Testing OSG 3.5 HTCondor-CE 4.5.2 osg-gridftp on EL8 OSG 3.5-upcoming HTCondor 9.0.1 GlideinWMS 3.7.4 XRootD 5.2.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.1 Ready for Release Nothing yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210518/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210608/","text":"OSG Technology Area Meeting, 8 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Marco, Marian, Mat, TimT Announcements \u00b6 TimT OOO June 14-18 Triage Duty \u00b6 This week: TimT Next week: Carl 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 156 -5 Open 21 +5 Selected for Dev 31 +1 In Progress 10 -2 Dev Complete 8 -5 Ready for Testing 2 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): Review scitokens-cpp promotion request (should we release it for EL8?) AI (Mat): XRootD for EL8 for OSG 3.5 Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): walk Lehigh/SIUE through recovering their old accounting records Discussion \u00b6 We should release scitokens-cpp for EL8 in order to maintain symmetry with EL7 GlideinWMS 3.9.2 is in osg-development and has passed internal testing; TimT will promote it to contrib Support Update \u00b6 SIUE/Lehigh (Carl, BrianL): identified pilot accounting upload bugs (fixed in gratia-probe-1.23.3 and the HTCondor versions in testing) PSU (BrianL): $HOME expansion doesn't work for Hosted CEs submitting to local HTCondor batch systems CIT/IGWN (Marian): Marian is providing assistance with upgrading to HTCondor 9 GlideinWMS (Marco): Found a bug where temporary errors contacting the frontend collectors would get cached, causing further queries to fail until the cache expired or the frontend was restarted. This will be fixed in 3.7.5 OZStar (Derek): StashCache is not connecting to the ligo origin correctly. Difficult to iterate since in Australia. Diego and I setup a time to meet that works for all. KSU / JLab (Derek/Marian): Failures at KSU. Difficult to tell what exactly the failures are, but the faliure has something to do with xrootd, the posix preload, and downloading a file from jalb. OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira . Pull request: https://github.com/opensciencegrid/tiger-osg-config/pull/173 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! Bluepring meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.38 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 -2 4 -1 13 -3 Open 6 +1 3 +2 2 +1 11 +4 Selected for Development 0 +0 1 -1 2 +0 3 -1 In Progress 3 +0 1 +0 0 +0 4 +0 Development Complete 2 -3 3 +1 1 +1 6 -1 Ready for Testing 2 +2 0 +0 0 +0 2 +2 Ready for Release 22 +0 8 +0 9 +1 39 +1 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) xrootd-hdfs 2.2.0-1.1 (get correct username from token) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release OSG 3.5 HTCondor 8.8.13-1.1 OSG 3.5-upcoming XRootD 5.2.0 Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"June 8, 2021"},{"location":"meetings/2021/TechArea20210608/#osg-technology-area-meeting-8-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 8 June 2021"},{"location":"meetings/2021/TechArea20210608/#announcements","text":"TimT OOO June 14-18","title":"Announcements"},{"location":"meetings/2021/TechArea20210608/#triage-duty","text":"This week: TimT Next week: Carl 11 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210608/#jira-as-of-monday","text":"# of tickets \u0394 State 156 -5 Open 21 +5 Selected for Dev 31 +1 In Progress 10 -2 Dev Complete 8 -5 Ready for Testing 2 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210608/#osg-software-team","text":"Release AI (Mat): Review scitokens-cpp promotion request (should we release it for EL8?) AI (Mat): XRootD for EL8 for OSG 3.5 Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): walk Lehigh/SIUE through recovering their old accounting records","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210608/#discussion","text":"We should release scitokens-cpp for EL8 in order to maintain symmetry with EL7 GlideinWMS 3.9.2 is in osg-development and has passed internal testing; TimT will promote it to contrib","title":"Discussion"},{"location":"meetings/2021/TechArea20210608/#support-update","text":"SIUE/Lehigh (Carl, BrianL): identified pilot accounting upload bugs (fixed in gratia-probe-1.23.3 and the HTCondor versions in testing) PSU (BrianL): $HOME expansion doesn't work for Hosted CEs submitting to local HTCondor batch systems CIT/IGWN (Marian): Marian is providing assistance with upgrading to HTCondor 9 GlideinWMS (Marco): Found a bug where temporary errors contacting the frontend collectors would get cached, causing further queries to fail until the cache expired or the frontend was restarted. This will be fixed in 3.7.5 OZStar (Derek): StashCache is not connecting to the ligo origin correctly. Difficult to iterate since in Australia. Diego and I setup a time to meet that works for all. KSU / JLab (Derek/Marian): Failures at KSU. Difficult to tell what exactly the failures are, but the faliure has something to do with xrootd, the posix preload, and downloading a file from jalb.","title":"Support Update"},{"location":"meetings/2021/TechArea20210608/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira . Pull request: https://github.com/opensciencegrid/tiger-osg-config/pull/173 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, just waiting on effort from Derek on how to package / deliver it. As a reminder, compiling on EL7 makes it work on EL7, 8, ubuntu\u2026 Go is great! Bluepring meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210608/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210608/#osg-release-team","text":"3.5.38 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 -2 4 -1 13 -3 Open 6 +1 3 +2 2 +1 11 +4 Selected for Development 0 +0 1 -1 2 +0 3 -1 In Progress 3 +0 1 +0 0 +0 4 +0 Development Complete 2 -3 3 +1 1 +1 6 -1 Ready for Testing 2 +2 0 +0 0 +0 2 +2 Ready for Release 22 +0 8 +0 9 +1 39 +1 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) xrootd-hdfs 2.2.0-1.1 (get correct username from token) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release OSG 3.5 HTCondor 8.8.13-1.1 OSG 3.5-upcoming XRootD 5.2.0 Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210608/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210615/","text":"OSG Technology Area Meeting, 15 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Marian, Mat Announcements \u00b6 TimT OOO June 14-18 CHTC team OOO Thu Jun 17 BrianL OOO Fri and Mon Mat OOO Fri afternoon Triage Duty \u00b6 This week: Carl Next week: BrianL 9 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 154 -2 Open 21 +0 Selected for Dev 34 +3 In Progress 6 -4 Dev Complete 9 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Release AI (BrianL): Add new EIC VO DN ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4666 ) AI (Mat): Build empty-condor package AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Ensure that Gratia accounts for SciTokens-based pilots ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4615 ) Discussion \u00b6 GlideinWMS 3.7 release expected later this month. Dennis is reviewing a PR for the frontend to increase admin control over SciToken generation ( https://github.com/glideinWMS/glideinwms/pull/52 ) Support Update \u00b6 SIUE/Lehigh (Carl): provided instructions for restoring missing pilot data OzStar (Derek, Marian): Cert was communicated incorrectly, and osg-xrootd-standalone was conflicting with the stash cache auth. ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4668 ) OSG DevOps \u00b6 GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Blueprint meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. Added new wait time metrics: https://github.com/path-cc/metric-tools/pull/26 (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week","title":"June 15, 2021"},{"location":"meetings/2021/TechArea20210615/#osg-technology-area-meeting-15-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Carl, Derek, Marco, Marian, Mat","title":"OSG Technology Area Meeting, 15 June 2021"},{"location":"meetings/2021/TechArea20210615/#announcements","text":"TimT OOO June 14-18 CHTC team OOO Thu Jun 17 BrianL OOO Fri and Mon Mat OOO Fri afternoon","title":"Announcements"},{"location":"meetings/2021/TechArea20210615/#triage-duty","text":"This week: Carl Next week: BrianL 9 (-2) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210615/#jira-as-of-monday","text":"# of tickets \u0394 State 154 -2 Open 21 +0 Selected for Dev 34 +3 In Progress 6 -4 Dev Complete 9 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210615/#osg-software-team","text":"Kubernetes Hackathon today: https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Release AI (BrianL): Add new EIC VO DN ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4666 ) AI (Mat): Build empty-condor package AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Ensure that Gratia accounts for SciTokens-based pilots ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4615 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210615/#discussion","text":"GlideinWMS 3.7 release expected later this month. Dennis is reviewing a PR for the frontend to increase admin control over SciToken generation ( https://github.com/glideinWMS/glideinwms/pull/52 )","title":"Discussion"},{"location":"meetings/2021/TechArea20210615/#support-update","text":"SIUE/Lehigh (Carl): provided instructions for restoring missing pilot data OzStar (Derek, Marian): Cert was communicated incorrectly, and osg-xrootd-standalone was conflicting with the stash cache auth. ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4668 )","title":"Support Update"},{"location":"meetings/2021/TechArea20210615/#osg-devops","text":"GRACC ITB Collector k8s on Tiger Jira XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Blueprint meeting for xrootd-monitoring identified a new service to be written. The xrootd-shoveler is currently being written up in a design document. Added new wait time metrics: https://github.com/path-cc/metric-tools/pull/26 (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210615/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210622/","text":"OSG Technology Area Meeting, 22 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Jack Yuan, Marian, Tim Announcements \u00b6 Carl OOO Wed-Fri Triage Duty \u00b6 This week: BrianL Next week: ??? 9 (-0) open FreshDesk tickets 0 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +6 Open 21 +0 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Doc focus this Friday afternoon Release AI (BrianL): kick off Vault VMU tests (SOFTWARE-4677) AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (TimT): Rebuild new HTCondor daily into the devops repo so it can be tested in the OSG Open Pool Discussion \u00b6 None this week Support Update \u00b6 BrianL (NDSU Lancium): Backfill container not detecting their GPUs; Brian will consult Mats for assistance. Carl (Lehigh): Successfully resent old records. Carl will double-check that current records are working correctly.f Carl, Derek (SIUE): No longer receiving records, planning a live debugging session this afternoon OSG DevOps \u00b6 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Design document is done and is being distributed. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 +0 4 +0 13 +0 Open 2 -4 4 +1 1 -1 7 -4 Selected for Development 2 +2 1 +0 3 +1 6 +3 In Progress 0 -3 1 +0 0 +0 1 -3 Development Complete 5 +3 4 +1 2 +1 11 +5 Ready for Testing 0 -2 0 +0 0 +0 0 -2 Ready for Release 18 -4 10 +2 10 +1 38 -1 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 scitokens-cpp 0.6.2 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"June 22, 2021"},{"location":"meetings/2021/TechArea20210622/#osg-technology-area-meeting-22-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Jack Yuan, Marian, Tim","title":"OSG Technology Area Meeting, 22 June 2021"},{"location":"meetings/2021/TechArea20210622/#announcements","text":"Carl OOO Wed-Fri","title":"Announcements"},{"location":"meetings/2021/TechArea20210622/#triage-duty","text":"This week: BrianL Next week: ??? 9 (-0) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210622/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +6 Open 21 +0 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210622/#osg-software-team","text":"Doc focus this Friday afternoon Release AI (BrianL): kick off Vault VMU tests (SOFTWARE-4677) AI (Mat): XRootD for EL8 for OSG 3.5 AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (TimT): Rebuild new HTCondor daily into the devops repo so it can be tested in the OSG Open Pool","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210622/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210622/#support-update","text":"BrianL (NDSU Lancium): Backfill container not detecting their GPUs; Brian will consult Mats for assistance. Carl (Lehigh): Successfully resent old records. Carl will double-check that current records are working correctly.f Carl, Derek (SIUE): No longer receiving records, planning a live debugging session this afternoon","title":"Support Update"},{"location":"meetings/2021/TechArea20210622/#osg-devops","text":"XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. Design document is done and is being distributed. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210622/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210622/#osg-release-team","text":"3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 0 +0 4 +0 13 +0 Open 2 -4 4 +1 1 -1 7 -4 Selected for Development 2 +2 1 +0 3 +1 6 +3 In Progress 0 -3 1 +0 0 +0 1 -3 Development Complete 5 +3 4 +1 2 +1 11 +5 Ready for Testing 0 -2 0 +0 0 +0 0 -2 Ready for Release 18 -4 10 +2 10 +1 38 -1 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 scitokens-cpp 0.6.2 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 HTCondor 9.0.1-1.1 HTCondor-CE 5.1.1 XCache 2.0.1 (Python 3 conversion) OSG 3.6 HTCondor 9.0.1-1.2 HTCondor-CE 5.1.1-1.1 OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210622/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210629/","text":"OSG Technology Area Meeting, 29 June 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Marian, Mat, Tim T Announcements \u00b6 Carl OOO July 2-7 Triage Duty \u00b6 This week: Carl Next week: BrianL 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +0 Open 19 -2 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon. Prioritize working on fallout from the recent outage, otherwise see tasks on https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Tim makeup doc focus Release AI (Mat): XRootD for EL8 for OSG 3.5. What's left? AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) Discussion \u00b6 ATLAS and CMS have tested IAM vo-client updates; Brian L will mail CERN folks to ask if they're ready for the transition XRootD 5.2 for OSG 3.5 has already been released xrootd-multiuser 1.1.0 in the 3.5 upcoming-testing repos; we're asking Justas from Caltech to test XRootD 5.3.0rc1 release candidate in the 3.5 upcoming-testing repos; Horst at OU was the most affected by bugs in previous versions so he is a good testing candidate AI (Mat): Create automated Koji user for doing CI builds Support Update \u00b6 MWT2 (BrianL): merged in .rpmsave containing a config fix for held job pile-up due to `SYSTEM PERIODIC ` expressions fighting Lehigh (Derek): (DONE) Removed extranous records GLOW (Derek): Submitted GRACC records with start date in 2008. Caused by node coming up after power outage with date set to 2008, so jobs will have \"started\" in 2008, and run until now, resulting in huge walltimes. Will remove. KSU (Derek): Likely IDS blocking access to data for JLAB jobs running at KSU. Not sure how to solve other than have JLAB blacklist KSU. OSG DevOps \u00b6 XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Debugging of gracc nodes after tiger update resulted in restarting a few pods, and 1 typo discovered. Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +1 Open 2 +0 4 +0 1 +0 7 +0 Selected for Development 1 -1 0 -1 3 +0 4 -2 In Progress 0 +0 2 +1 0 +0 2 +1 Development Complete 5 +0 2 -2 2 +0 9 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 17 -1 9 -1 10 +0 36 -2 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 gfal2 in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 Release this week Push out HTCondor 9.1.0 into EL6 with minimal testing","title":"June 29, 2021"},{"location":"meetings/2021/TechArea20210629/#osg-technology-area-meeting-29-june-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Marian, Mat, Tim T","title":"OSG Technology Area Meeting, 29 June 2021"},{"location":"meetings/2021/TechArea20210629/#announcements","text":"Carl OOO July 2-7","title":"Announcements"},{"location":"meetings/2021/TechArea20210629/#triage-duty","text":"This week: Carl Next week: BrianL 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210629/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +0 Open 19 -2 Selected for Dev 35 +1 In Progress 8 +2 Dev Complete 12 +3 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210629/#osg-software-team","text":"Kubernetes Hackathon this afternoon. Prioritize working on fallout from the recent outage, otherwise see tasks on https://opensciencegrid.atlassian.net/secure/RapidBoard.jspa?rapidView=34 Tim makeup doc focus Release AI (Mat): XRootD for EL8 for OSG 3.5. What's left? AI (Mat): xrootd-multiuser 1.1.0 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 )","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210629/#discussion","text":"ATLAS and CMS have tested IAM vo-client updates; Brian L will mail CERN folks to ask if they're ready for the transition XRootD 5.2 for OSG 3.5 has already been released xrootd-multiuser 1.1.0 in the 3.5 upcoming-testing repos; we're asking Justas from Caltech to test XRootD 5.3.0rc1 release candidate in the 3.5 upcoming-testing repos; Horst at OU was the most affected by bugs in previous versions so he is a good testing candidate AI (Mat): Create automated Koji user for doing CI builds","title":"Discussion"},{"location":"meetings/2021/TechArea20210629/#support-update","text":"MWT2 (BrianL): merged in .rpmsave containing a config fix for held job pile-up due to `SYSTEM PERIODIC ` expressions fighting Lehigh (Derek): (DONE) Removed extranous records GLOW (Derek): Submitted GRACC records with start date in 2008. Caused by node coming up after power outage with date set to 2008, so jobs will have \"started\" in 2008, and run until now, resulting in huge walltimes. Will remove. KSU (Derek): Likely IDS blocking access to data for JLAB jobs running at KSU. Not sure how to solve other than have JLAB blacklist KSU.","title":"Support Update"},{"location":"meetings/2021/TechArea20210629/#osg-devops","text":"XRootD Multiuser: 1.1.0 is tagged: https://opensciencegrid.atlassian.net/browse/SOFTWARE-4658 (in testing below) StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Debugging of gracc nodes after tiger update resulted in restarting a few pods, and 1 typo discovered. Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210629/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210629/#osg-release-team","text":"3.5.39 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +1 Open 2 +0 4 +0 1 +0 7 +0 Selected for Development 1 -1 0 -1 3 +0 4 -2 In Progress 0 +0 2 +1 0 +0 2 +1 Development Complete 5 +0 2 -2 2 +0 9 -2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 17 -1 9 -1 10 +0 36 -2 Total Software Ready for Testing Both vault 1.7.3, htvault-config 1.2 frontier-squid 4.15-2.1 (no log rotation if log compression disabled) OSG 3.5 XRootD 4.12.6-1.1 in EL8 osg-flock in EL8 gfal2 in EL8 OSG 3.5-upcoming xrootd-multiuser 1.1.0 XCache 2.0.1 (Python 3 conversion) OSG 3.6-upcoming HTCondor 9.1.0-1.2 Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210629/#discussion_2","text":"Release this week Push out HTCondor 9.1.0 into EL6 with minimal testing","title":"Discussion"},{"location":"meetings/2021/TechArea20210706/","text":"OSG Technology Area Meeting, 6 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco, Marian, Mat, TimT Announcements \u00b6 Carl OOO until Thursday Mat OOO Jul 9-14 TimT OOO Jul 9 Triage Duty \u00b6 This week: BrianL Next week: TimT 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 152 -8 Open 24 +5 Selected for Dev 36 +1 In Progress 9 +1 Dev Complete 8 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus Release AI (Mat): XRootD 5.3.0 RC4 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Remove deps needed for Globus from HTCondor in 3.6 Discussion \u00b6 Madison would like GlideinWMS container images with immutable tags for their production frontends. Currently the images are contributed by Diego, but BrianL will make a ticket for tracking the issue. GlideinWMS 3.7 series release not expected until a few weeks from now. Upstream HTCondor 9.0.2 and BLAHP 2.1.0 release planned for tomorrow (7/7); TimT will provide BrianL with a BLAHP tarball for testing. Support Update \u00b6 SUT (BrianL): remote host missing libltdl IGWN frontend (Marian): proxy was not getting renewed, but a pod redeploy fixed the issue. Investigate the original cause; BrianL thinks it might have been a Fetch-CRL error. GLOW (Derek): Removed abnormal CMS records (900,000+ hours for 1 job), and re-uploaded WLCG records for June. OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +0 Open 1 -1 3 -1 2 +1 6 -1 Selected for Development 0 -1 0 -1 3 +0 3 -1 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 -3 1 -1 1 -1 4 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 -5 7 -2 10 +0 29 -7 Total Software Ready for Testing OSG 3.5-upcoming XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing Discussion \u00b6 None this week","title":"July 6, 2021"},{"location":"meetings/2021/TechArea20210706/#osg-technology-area-meeting-6-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 6 July 2021"},{"location":"meetings/2021/TechArea20210706/#announcements","text":"Carl OOO until Thursday Mat OOO Jul 9-14 TimT OOO Jul 9","title":"Announcements"},{"location":"meetings/2021/TechArea20210706/#triage-duty","text":"This week: BrianL Next week: TimT 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210706/#jira-as-of-monday","text":"# of tickets \u0394 State 152 -8 Open 24 +5 Selected for Dev 36 +1 In Progress 9 +1 Dev Complete 8 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210706/#osg-software-team","text":"Tim makeup doc focus Release AI (Mat): XRootD 5.3.0 RC4 AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Remove deps needed for Globus from HTCondor in 3.6","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210706/#discussion","text":"Madison would like GlideinWMS container images with immutable tags for their production frontends. Currently the images are contributed by Diego, but BrianL will make a ticket for tracking the issue. GlideinWMS 3.7 series release not expected until a few weeks from now. Upstream HTCondor 9.0.2 and BLAHP 2.1.0 release planned for tomorrow (7/7); TimT will provide BrianL with a BLAHP tarball for testing.","title":"Discussion"},{"location":"meetings/2021/TechArea20210706/#support-update","text":"SUT (BrianL): remote host missing libltdl IGWN frontend (Marian): proxy was not getting renewed, but a pod redeploy fixed the issue. Investigate the original cause; BrianL thinks it might have been a Fetch-CRL error. GLOW (Derek): Removed abnormal CMS records (900,000+ hours for 1 job), and re-uploaded WLCG records for June.","title":"Support Update"},{"location":"meetings/2021/TechArea20210706/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210706/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210706/#osg-release-team","text":"3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +1 4 +0 14 +0 Open 1 -1 3 -1 2 +1 6 -1 Selected for Development 0 -1 0 -1 3 +0 3 -1 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 -3 1 -1 1 -1 4 -5 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 -5 7 -2 10 +0 29 -7 Total Software Ready for Testing OSG 3.5-upcoming XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data Nothing Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210706/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210713/","text":"OSG Technology Area Meeting, 13 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, TimT Announcements \u00b6 Mat OOO Jul 9-14 BrianL OOO Friday Triage Duty \u00b6 This week: TimT Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 151 -1 Open 24 +0 Selected for Dev 40 +4 In Progress 11 +2 Dev Complete 7 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Kubernetes Hackathon Release AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Tag and build VO client Discussion \u00b6 None this week Support Update \u00b6 None this week OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 4 +0 14 +0 Open 1 +0 3 +0 1 -1 5 -1 Selected for Development 0 +0 1 +1 4 +1 5 +2 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 +0 3 +2 0 -1 5 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 +0 10 +3 9 -1 31 +2 Total Software Ready for Testing OSG 3.5-upcoming XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing Discussion \u00b6 VO Package v114 should go out this week","title":"July 13, 2021"},{"location":"meetings/2021/TechArea20210713/#osg-technology-area-meeting-13-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, TimT","title":"OSG Technology Area Meeting, 13 July 2021"},{"location":"meetings/2021/TechArea20210713/#announcements","text":"Mat OOO Jul 9-14 BrianL OOO Friday","title":"Announcements"},{"location":"meetings/2021/TechArea20210713/#triage-duty","text":"This week: TimT Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210713/#jira-as-of-monday","text":"# of tickets \u0394 State 151 -1 Open 24 +0 Selected for Dev 40 +4 In Progress 11 +2 Dev Complete 7 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210713/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Kubernetes Hackathon Release AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs (SOFTWARE-4621) ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Missing zero walltime records AI (BrianL): Tag and build VO client","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210713/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210713/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210713/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up) Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler development has begun! XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. Derek needs to discuss with XRootD team, but it will be on Derek's plate. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210713/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210713/#osg-release-team","text":"3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 4 +0 14 +0 Open 1 +0 3 +0 1 -1 5 -1 Selected for Development 0 +0 1 +1 4 +1 5 +2 In Progress 0 +0 2 +0 0 +0 2 +0 Development Complete 2 +0 3 +2 0 -1 5 +1 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 12 +0 10 +3 9 -1 31 +2 Total Software Ready for Testing OSG 3.5-upcoming XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210713/#discussion_2","text":"VO Package v114 should go out this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210720/","text":"OSG Technology Area Meeting, 20 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Carl OOO Jul 26-30 Triage Duty \u00b6 This week: Mat Next week: BrianL (?) 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 147 -4 Open 27 +3 Selected for Dev 37 -3 In Progress 10 -1 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Fill out doc focus poll: https://terminplaner.dfn.de/RxlXW8dscNfMXaMx Release AI (Carl): Follow-up on Lincoln's gratia-probe stacktrace reported in #software AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Release gratia-probe 1.23.4+, 2.0.1+ AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Missing zero walltime records AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Give GlideinWMS team JIRA access. Discussion \u00b6 GlideinWMS 3.7 release candidate planned for tomorrow (7/21). Support Update \u00b6 (Derek) SIUE - Discovered bug in gratia probe, fixed locally and submitted upstream: https://github.com/opensciencegrid/gratia-probe/pull/107 BrianL: We are currently only sending LIGO jobs to Georgia Tech to avoid having OSG (and other VO) jobs run on LIGO pilots. Marian: Continuing to debug JLab submissions at Georgia Tech. Lamar (CLAS12) does not have any pilots or show any HTCondor activity. Finish setting up ICTS; it is registered in Topology so only the factory config needs to be updated. Mat: Lancium not seeing enough jobs again; Brian will investigate further. OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the typ rather than ver . (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 3 -1 13 -1 Open 2 +1 2 -1 1 +0 5 +0 Selected for Development 0 +0 2 +1 5 +1 7 +2 In Progress 0 +0 3 +1 0 +0 3 +1 Development Complete 3 +1 4 +1 0 +0 7 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 14 +2 12 +2 9 +0 35 +4 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.2 + blahp 2.1.0 XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing Discussion \u00b6 VO Package v114 should go out this week","title":"July 20, 2021"},{"location":"meetings/2021/TechArea20210720/#osg-technology-area-meeting-20-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 20 July 2021"},{"location":"meetings/2021/TechArea20210720/#announcements","text":"Carl OOO Jul 26-30","title":"Announcements"},{"location":"meetings/2021/TechArea20210720/#triage-duty","text":"This week: Mat Next week: BrianL (?) 10 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210720/#jira-as-of-monday","text":"# of tickets \u0394 State 147 -4 Open 27 +3 Selected for Dev 37 -3 In Progress 10 -1 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210720/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Fill out doc focus poll: https://terminplaner.dfn.de/RxlXW8dscNfMXaMx Release AI (Carl): Follow-up on Lincoln's gratia-probe stacktrace reported in #software AI (Carl): Move 99 gratia -ce.conf to /usr/share location AI (Carl): Release gratia-probe 1.23.4+, 2.0.1+ AI (Carl): Fix default HTCondor-CE ProbeConfig default dirs ( https://opensciencegrid.atlassian.net/browse/SOFTWARE-4621 ) AI (Carl): Missing zero walltime records AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Give GlideinWMS team JIRA access.","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210720/#discussion","text":"GlideinWMS 3.7 release candidate planned for tomorrow (7/21).","title":"Discussion"},{"location":"meetings/2021/TechArea20210720/#support-update","text":"(Derek) SIUE - Discovered bug in gratia probe, fixed locally and submitted upstream: https://github.com/opensciencegrid/gratia-probe/pull/107 BrianL: We are currently only sending LIGO jobs to Georgia Tech to avoid having OSG (and other VO) jobs run on LIGO pilots. Marian: Continuing to debug JLab submissions at Georgia Tech. Lamar (CLAS12) does not have any pilots or show any HTCondor activity. Finish setting up ICTS; it is registered in Topology so only the factory config needs to be updated. Mat: Lancium not seeing enough jobs again; Brian will investigate further.","title":"Support Update"},{"location":"meetings/2021/TechArea20210720/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the typ rather than ver . (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210720/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210720/#osg-release-team","text":"3.5.41 \u0394 Both \u0394 3.6 \u0394 Total \u0394 Status 9 +0 1 +0 3 -1 13 -1 Open 2 +1 2 -1 1 +0 5 +0 Selected for Development 0 +0 2 +1 5 +1 7 +2 In Progress 0 +0 3 +1 0 +0 3 +1 Development Complete 3 +1 4 +1 0 +0 7 +2 Ready for Testing 0 +0 0 +0 0 +0 0 +0 Ready for Release 14 +2 12 +2 9 +0 35 +4 Total Software Ready for Testing OSG 3.5-upcoming HTCondor 9.0.2 + blahp 2.1.0 XRootD 5.3.0 XCache 2.0.1 (Python 3 conversion) Ready for Release Nothing Yet Data VO Package v114 Operations Nothing Contrib Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210720/#discussion_2","text":"VO Package v114 should go out this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210727/","text":"OSG Technology Area Meeting, 27 July 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT Announcements \u00b6 Carl OOO Jul 26-30 Party at Tim's house with three racks of ribs Triage Duty \u00b6 This week: BrianL Next week: Carl 6 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 148 +1 Open 25 -2 Selected for Dev 36 -1 In Progress 12 +2 Dev Complete 3 -4 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Verify that HTCondor got updated on the OS registry AT (BrianL): Create ticket for pushing to OSG Hub as well as Docker Hub in automated builds Discussion \u00b6 GlideinWMS release candidate expected later this week SSH to tiger cluster head node only available from select CHTC hosts; kubectl access has not been changed Support Update \u00b6 None this week OSG DevOps \u00b6 StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.42 and OSG 3.6 (today) HTCondor Security Release 8.8.14, 9.0.3, 9.1.1 OSG 3.5.43 and OSG 3.6 (Thursday) Ready for Testing OSG 3.5 and 3.6 gratia-probe 1.24.0 Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 Discussion \u00b6 None this week","title":"July 27, 2021"},{"location":"meetings/2021/TechArea20210727/#osg-technology-area-meeting-27-july-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 27 July 2021"},{"location":"meetings/2021/TechArea20210727/#announcements","text":"Carl OOO Jul 26-30 Party at Tim's house with three racks of ribs","title":"Announcements"},{"location":"meetings/2021/TechArea20210727/#triage-duty","text":"This week: BrianL Next week: Carl 6 (-4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210727/#jira-as-of-monday","text":"# of tickets \u0394 State 148 +1 Open 25 -2 Selected for Dev 36 -1 In Progress 12 +2 Dev Complete 3 -4 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210727/#osg-software-team","text":"Kubernetes Hackathon this afternoon Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (BrianL): Use vomsxrd config in osg-xrootd on 3.6 AI (TimT): SciTokens credmon? AI (BrianL): Verify that HTCondor got updated on the OS registry AT (BrianL): Create ticket for pushing to OSG Hub as well as Docker Hub in automated builds","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210727/#discussion","text":"GlideinWMS release candidate expected later this week SSH to tiger cluster head node only available from select CHTC hosts; kubectl access has not been changed","title":"Discussion"},{"location":"meetings/2021/TechArea20210727/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20210727/#osg-devops","text":"StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Now on to the collector. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210727/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210727/#osg-release-team","text":"OSG 3.5.42 and OSG 3.6 (today) HTCondor Security Release 8.8.14, 9.0.3, 9.1.1 OSG 3.5.43 and OSG 3.6 (Thursday) Ready for Testing OSG 3.5 and 3.6 gratia-probe 1.24.0 Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210727/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210803/","text":"OSG Technology Area Meeting, 3 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 7 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 153 +5 Open 26 +1 Selected for Dev 39 +3 In Progress 11 -1 Dev Complete 3 +0 Ready for Testing 5 +2 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens credmon? AI (Carl): Move Gratia sub-tickets into RFT AI (Carl): Improve default ProbeConfig directory configuration GSI Transition AI (Carl): Directly query OSG COManage's LDAP for OSGID (SOFTWARE-4528) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) OSG VO Backfill Containers AI (Mat): Add support for limiting resources available to the osgvo-docker-pilot (SOFTWARE-4634) AI (BrianL): Add CI tests Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies Discussion \u00b6 GlideinWMS 3.7.5 still in progress; release candidate expected today/tomorrow; rc will contain cvmfsexec support Support Update \u00b6 Georgia Tech (BrianL): Gave them some AP HTCondor config that should prevent pilots from flocking out to pilots Lancium (BrianL, Mats): live backfill container debugging session that uncovered issues in the periodic health check not properly detecting unpriv Singularity. Multiple (Derek): Several sites had failed gratia probes over the last week. All isolated events, but I think there were 4 at the same time. OSG DevOps \u00b6 Elasticsearch will need to be updated. Working on a schedule. StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 50% done. Design document is still not reviewed, but moving foward anyways. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming) Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 Discussion \u00b6 None this week","title":"August 3, 2021"},{"location":"meetings/2021/TechArea20210803/#osg-technology-area-meeting-3-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 3 August 2021"},{"location":"meetings/2021/TechArea20210803/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210803/#triage-duty","text":"This week: Carl Next week: Mat 7 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210803/#jira-as-of-monday","text":"# of tickets \u0394 State 153 +5 Open 26 +1 Selected for Dev 39 +3 In Progress 11 -1 Dev Complete 3 +0 Ready for Testing 5 +2 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210803/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens credmon? AI (Carl): Move Gratia sub-tickets into RFT AI (Carl): Improve default ProbeConfig directory configuration GSI Transition AI (Carl): Directly query OSG COManage's LDAP for OSGID (SOFTWARE-4528) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) OSG VO Backfill Containers AI (Mat): Add support for limiting resources available to the osgvo-docker-pilot (SOFTWARE-4634) AI (BrianL): Add CI tests Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210803/#discussion","text":"GlideinWMS 3.7.5 still in progress; release candidate expected today/tomorrow; rc will contain cvmfsexec support","title":"Discussion"},{"location":"meetings/2021/TechArea20210803/#support-update","text":"Georgia Tech (BrianL): Gave them some AP HTCondor config that should prevent pilots from flocking out to pilots Lancium (BrianL, Mats): live backfill container debugging session that uncovered issues in the periodic health check not properly detecting unpriv Singularity. Multiple (Derek): Several sites had failed gratia probes over the last week. All isolated events, but I think there were 4 at the same time.","title":"Support Update"},{"location":"meetings/2021/TechArea20210803/#osg-devops","text":"Elasticsearch will need to be updated. Working on a schedule. StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 50% done. Design document is still not reviewed, but moving foward anyways. XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. More partners are asking about scitokens-cpp, and compatibility. Expect some updates. Maybe we have been doing tokens wrong? Use the `typ` rather than `ver`. (Stalled, but need to get back to it) XRootD accounting information (from Frank): May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. Table of working set, read, and re-read for monthly, quarterly, and year.","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210803/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210803/#osg-release-team","text":"Ready for Testing gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming) Ready for Release OSG 3.5 Upcoming: XCache 2.0.1 (Python 3 conversion) VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3 OSG 3.6 VOMS 2.0.16 (2.1.0rc? on EL8) htvault-config 1.4 and htgettoken 1.3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210803/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210810/","text":"OSG Technology Area Meeting, 10 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT Announcements \u00b6 OSG User School in session until the end of the week Triage Duty \u00b6 This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 155 +2 Open 26 +0 Selected for Dev 39 +0 In Progress 6 -5 Dev Complete 8 +3 Ready for Testing 6 +1 Ready for Release OSG Software Team \u00b6 Kuberentes Hackathon today 1-5pm Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens update for EL8 (SOFTWARE-4126) AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add CI tests Discussion \u00b6 GRACC upgrade is planned for the end of August Support Update \u00b6 Georgia Tech (BrianL, Mats): Need to verify that the config worked to prevent pilots from running in pilots Lancium (BrianL, Mats): their GPUs are still going unused, it seems that RecentJobStarts is frequently at its limit of 400 starts/20 min JLab (Marian): Fixed HTCondor configuration; JLab admins should be informed to expect some downtime and manual changes between OSG release series upgrades Lamar (Marian): Jobs are running but requesting Software Team help to examine job classads for anything unexpected BNL (Marian): Troubleshooting with John de Stefano and other BNL admins; getting unexpected behavior from Freshdesk with notes or replies not getting to everyone on the ticket. Marian will notify Freshdesk support about the strange behavior. Hosted CEs (Carl): Investigate hosted-ce35 not reporting to GRACC. University of Illinois (Mat): Undesired XRootD HTTP plugin behavior; Mat is following discussion between XRootD developers OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 80% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.45 and OSG 3.6 (Thursday) Ready for Release gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming) Discussion \u00b6 None this week","title":"August 10, 2021"},{"location":"meetings/2021/TechArea20210810/#osg-technology-area-meeting-10-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 10 August 2021"},{"location":"meetings/2021/TechArea20210810/#announcements","text":"OSG User School in session until the end of the week","title":"Announcements"},{"location":"meetings/2021/TechArea20210810/#triage-duty","text":"This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210810/#jira-as-of-monday","text":"# of tickets \u0394 State 155 +2 Open 26 +0 Selected for Dev 39 +0 In Progress 6 -5 Dev Complete 8 +3 Ready for Testing 6 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210810/#osg-software-team","text":"Kuberentes Hackathon today 1-5pm Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Release AI (TimT): SciTokens update for EL8 (SOFTWARE-4126) AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Investigate persistent condor_ce_run failures in 3.6 nightlies AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add CI tests","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210810/#discussion","text":"GRACC upgrade is planned for the end of August","title":"Discussion"},{"location":"meetings/2021/TechArea20210810/#support-update","text":"Georgia Tech (BrianL, Mats): Need to verify that the config worked to prevent pilots from running in pilots Lancium (BrianL, Mats): their GPUs are still going unused, it seems that RecentJobStarts is frequently at its limit of 400 starts/20 min JLab (Marian): Fixed HTCondor configuration; JLab admins should be informed to expect some downtime and manual changes between OSG release series upgrades Lamar (Marian): Jobs are running but requesting Software Team help to examine job classads for anything unexpected BNL (Marian): Troubleshooting with John de Stefano and other BNL admins; getting unexpected behavior from Freshdesk with notes or replies not getting to everyone on the ticket. Marian will notify Freshdesk support about the strange behavior. Hosted CEs (Carl): Investigate hosted-ce35 not reporting to GRACC. University of Illinois (Mat): Undesired XRootD HTTP plugin behavior; Mat is following discussion between XRootD developers","title":"Support Update"},{"location":"meetings/2021/TechArea20210810/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 80% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210810/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210810/#osg-release-team","text":"OSG 3.5.45 and OSG 3.6 (Thursday) Ready for Release gratia-probe 1.24.0 (OSG 3.5 and 3.6) XRootD 5.3.1 (OSG 3.5-upcoming)","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210810/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210817/","text":"OSG Technology Area Meeting, 17 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: BrianL? 13 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 156 +1 Open 26 +0 Selected for Dev 39 +0 In Progress 9 +3 Dev Complete 0 -8 Ready for Testing 0 -6 Ready for Release OSG Software Team \u00b6 Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Planning to add a \"doc pending\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL, Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add backfill container CI tests Discussion \u00b6 GRACC upgrade is planned for the end of August Diego noticed some condor_mapfile entries weren't matching if the incoming cert had both commas and VOMS attributes. There's a regex recipe that fixes it, which needs to be documented (HTCONDOR-651) Support Update \u00b6 Brown (BrianL): authN failures with their GridFTP + XRootD setup Caltech (BrianL): investigated 8.8.15 stacktrace LIGO-WA & LIGO-LA (Carl): invstigating missing probes in the payload summary page GlideinWMS (Marco): removed the code section in the user job wrapper that tried to add condor_chirp; will be replaced with a Python version 3.7 release candidate still in progress OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.45-2 and OSG 3.6 (2021-08-16) CA Certificates based on IGTF 1.112 OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 None this week","title":"August 17, 2021"},{"location":"meetings/2021/TechArea20210817/#osg-technology-area-meeting-17-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 17 August 2021"},{"location":"meetings/2021/TechArea20210817/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20210817/#triage-duty","text":"This week: TimT Next week: BrianL? 13 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210817/#jira-as-of-monday","text":"# of tickets \u0394 State 156 +1 Open 26 +0 Selected for Dev 39 +0 In Progress 9 +3 Dev Complete 0 -8 Ready for Testing 0 -6 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210817/#osg-software-team","text":"Tim makeup doc focus: EL8 interest is increasing Doc focus Aug 20 Planning to add a \"doc pending\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (BrianL, Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): osg-token-renewer package AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) AI (BrianL): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (Mat): Review comments on cvmfsexec doc changes AI (BrianL): Add backfill container CI tests","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210817/#discussion","text":"GRACC upgrade is planned for the end of August Diego noticed some condor_mapfile entries weren't matching if the incoming cert had both commas and VOMS attributes. There's a regex recipe that fixes it, which needs to be documented (HTCONDOR-651)","title":"Discussion"},{"location":"meetings/2021/TechArea20210817/#support-update","text":"Brown (BrianL): authN failures with their GridFTP + XRootD setup Caltech (BrianL): investigated 8.8.15 stacktrace LIGO-WA & LIGO-LA (Carl): invstigating missing probes in the payload summary page GlideinWMS (Marco): removed the code section in the user job wrapper that tried to add condor_chirp; will be replaced with a Python version 3.7 release candidate still in progress","title":"Support Update"},{"location":"meetings/2021/TechArea20210817/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - StashCP go client is working and tested, and being tested by Christina now. Need to talk to Mats on packaging and releasing. (will follow up). No news from Christina, - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210817/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210817/#osg-release-team","text":"OSG 3.5.45-2 and OSG 3.6 (2021-08-16) CA Certificates based on IGTF 1.112 OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210817/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210824/","text":"OSG Technology Area Meeting, 24 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim Announcements \u00b6 Carl OOO Wed-Thu TimT OOO Fri afternoon Triage Duty \u00b6 This week: BrianL Next week: Carl 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 156 +0 Open 35 +9 Selected for Dev 38 -1 In Progress 10 +1 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (BrianL): Review the osg-token-renewer package AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Other AI (BrianL): Add backfill container CI tests AI (TimT): Release HTCondor 9.1.4; add a fix/patch for proxy delegation Discussion \u00b6 None this week Support Update \u00b6 Colorado (BrianL): OSG-issued IGTF certs won't work because their IT won't issue a PTR pointing to the OSG domain Brown (Derek): Supporting XRootD configuration. Using standalone config, but also copied from other server that was working before. Old LCMaps configuration. Caltech (Derek)/LIGO (Carl): Debugging accounting information not showing up in the GRACC or in Gratia logs. (These are two separate tickets for the same issue; BrianL will merge them) UERJ (Carl): Provided support for tuning GridFTP configuration Hosted CEs (Carl): Hosted CEs failed to quarantine history files because the Gratia probes run as the 'condor' user and do not have write permission to the quarantine directory. This results in zero-length jobs not being reported to GRACC OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - StashCP Go client is now being used and distributed with every OSPool Glidein! Being used in the stash:/// transfer plugin and starting to be used by Mats on his singularity image distribution. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 HTCondor 9.0.5, HTCondor 9.1.3, and blahp 2.1.1 should be ready for testing today Proxy delegation problem with mixed versions in HTCondor 9.1.3","title":"August 24, 2021"},{"location":"meetings/2021/TechArea20210824/#osg-technology-area-meeting-24-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim","title":"OSG Technology Area Meeting, 24 August 2021"},{"location":"meetings/2021/TechArea20210824/#announcements","text":"Carl OOO Wed-Thu TimT OOO Fri afternoon","title":"Announcements"},{"location":"meetings/2021/TechArea20210824/#triage-duty","text":"This week: BrianL Next week: Carl 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210824/#jira-as-of-monday","text":"# of tickets \u0394 State 156 +0 Open 35 +9 Selected for Dev 38 -1 In Progress 10 +1 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210824/#osg-software-team","text":"Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (BrianL): Review the osg-token-renewer package AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) AI (Mat): Add API token authentication to Topology (SOFTWARE-4134) Other AI (BrianL): Add backfill container CI tests AI (TimT): Release HTCondor 9.1.4; add a fix/patch for proxy delegation","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210824/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210824/#support-update","text":"Colorado (BrianL): OSG-issued IGTF certs won't work because their IT won't issue a PTR pointing to the OSG domain Brown (Derek): Supporting XRootD configuration. Using standalone config, but also copied from other server that was working before. Old LCMaps configuration. Caltech (Derek)/LIGO (Carl): Debugging accounting information not showing up in the GRACC or in Gratia logs. (These are two separate tickets for the same issue; BrianL will merge them) UERJ (Carl): Provided support for tuning GridFTP configuration Hosted CEs (Carl): Hosted CEs failed to quarantine history files because the Gratia probes run as the 'condor' user and do not have write permission to the quarantine directory. This results in zero-length jobs not being reported to GRACC","title":"Support Update"},{"location":"meetings/2021/TechArea20210824/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - StashCP Go client is now being used and distributed with every OSPool Glidein! Being used in the stash:/// transfer plugin and starting to be used by Mats on his singularity image distribution. Ongoing: - Elasticsearch will need to be updated, scheduled for last week in August. Planning ongoing. - Design document is done and is being distributed for xrootd monitoring collector NG (next gen). Shoveler is working and lightly tested. Collector is 90% done. Design document is still not reviewed, but moving foward anyways. - Discussions of xrootd-multiuser support for checksumming on-the-fly. After a discussion, the checksum-on-the-fly funcationality will be ported to xrootd-multiuser. Copied largely from xrootd-hdfs. This does mean that out-of-order writes will not be supported. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210824/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210824/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210824/#discussion_2","text":"HTCondor 9.0.5, HTCondor 9.1.3, and blahp 2.1.1 should be ready for testing today Proxy delegation problem with mixed versions in HTCondor 9.1.3","title":"Discussion"},{"location":"meetings/2021/TechArea20210831/","text":"OSG Technology Area Meeting, 31 August 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim Announcements \u00b6 CE Token Hackathon 1-5pm today Triage Duty \u00b6 This week: Carl Next week: Mat 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 162 +6 Open 34 -1 Selected for Dev 41 +3 In Progress 9 -1 Dev Complete 5 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Address osg-token-renewer review comments AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Add backfill container CI tests AI (Carl, Mat): Review OS Pool AP Topology PR Discussion \u00b6 Mat and Marco should attend CE hackathon today; frontend admins should consider briefly joining. Marco investigating an incompatibility between a 3.6.5 factory (used at FNAL) and newer frontends. Support Update \u00b6 Marian: Singularity issues at Utah. Should assign ticket to Mats Rynge and add Mat as a watcher. HTCondor not properly handling CNAMEs in the IGWN central manager. Admins should create an A record for now, but BrianB will ask the HTCondor developers to address the issue. Carl: Waiting for response from LIGO about their accounting issue. No follow-up yet from HTCondor devs for DUNE/TIFR. Carl will examine the schedd log for any clues. Mat: Helping Andrew Melo with an overloaded schedd; HTCondor developers have joined the conversation. Greg Daues at U Illinois hasn't responded regarding minor XRootD security issue they found. Fix expected in XRootD 5.4.0; since it's security-related, it will also go into OSG 3.5-upcoming. OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Elasticsearch is being from 7.10.2 to 7.14.1. Some downtime expected, but only momentarily. No gratia probes or clients should notice. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 70% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing Discussion \u00b6 None this week","title":"August 31, 2021"},{"location":"meetings/2021/TechArea20210831/#osg-technology-area-meeting-31-august-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Derek, Marco, Marian, Mat, Tim","title":"OSG Technology Area Meeting, 31 August 2021"},{"location":"meetings/2021/TechArea20210831/#announcements","text":"CE Token Hackathon 1-5pm today","title":"Announcements"},{"location":"meetings/2021/TechArea20210831/#triage-duty","text":"This week: Carl Next week: Mat 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210831/#jira-as-of-monday","text":"# of tickets \u0394 State 162 +6 Open 34 -1 Selected for Dev 41 +3 In Progress 9 -1 Dev Complete 5 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210831/#osg-software-team","text":"Planning to add a \"doc pending\" or \"promotion requested\" status before RFT Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Address osg-token-renewer review comments AI (Mat): Get XRootD tests running with proxies again (SOFTWARE-4604) Other AI (BrianL): Add backfill container CI tests AI (Carl, Mat): Review OS Pool AP Topology PR","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210831/#discussion","text":"Mat and Marco should attend CE hackathon today; frontend admins should consider briefly joining. Marco investigating an incompatibility between a 3.6.5 factory (used at FNAL) and newer frontends.","title":"Discussion"},{"location":"meetings/2021/TechArea20210831/#support-update","text":"Marian: Singularity issues at Utah. Should assign ticket to Mats Rynge and add Mat as a watcher. HTCondor not properly handling CNAMEs in the IGWN central manager. Admins should create an A record for now, but BrianB will ask the HTCondor developers to address the issue. Carl: Waiting for response from LIGO about their accounting issue. No follow-up yet from HTCondor devs for DUNE/TIFR. Carl will examine the schedd log for any clues. Mat: Helping Andrew Melo with an overloaded schedd; HTCondor developers have joined the conversation. Greg Daues at U Illinois hasn't responded regarding minor XRootD security issue they found. Fix expected in XRootD 5.4.0; since it's security-related, it will also go into OSG 3.5-upcoming.","title":"Support Update"},{"location":"meetings/2021/TechArea20210831/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Elasticsearch is being from 7.10.2 to 7.14.1. Some downtime expected, but only momentarily. No gratia probes or clients should notice. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 70% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210831/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210831/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210831/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210907/","text":"OSG Technology Area Meeting, 7 September 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Mat, Tim Announcements \u00b6 Kubernetes Hackathon 1-5pm today Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 163 +1 Open 32 -2 Selected for Dev 37 -4 In Progress 14 +5 Dev Complete 4 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat): Kick off GlideinWMS 3.7.5 VMU tests GSI Transition AI (Carl): Address osg-token-renewer review comments Other AI (BrianL): Add backfill container CI tests AI (BrianL): add SSH certificate to the Hosted CE Discussion \u00b6 A longer term project for Carl is to enable mass token requests so Harvester folks can make a token per CE. Support Update \u00b6 Lancium (BrianL): backfill containers with bind-mounted CVMFS weren't getting jobs because they did not specify shared to the bind mount OSG DevOps \u00b6 New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing Discussion \u00b6 None this week","title":"September 7, 2021"},{"location":"meetings/2021/TechArea20210907/#osg-technology-area-meeting-7-september-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Carl, Mat, Tim","title":"OSG Technology Area Meeting, 7 September 2021"},{"location":"meetings/2021/TechArea20210907/#announcements","text":"Kubernetes Hackathon 1-5pm today","title":"Announcements"},{"location":"meetings/2021/TechArea20210907/#triage-duty","text":"This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210907/#jira-as-of-monday","text":"# of tickets \u0394 State 163 +1 Open 32 -2 Selected for Dev 37 -4 In Progress 14 +5 Dev Complete 4 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210907/#osg-software-team","text":"Release AI (Carl): Improve default ProbeConfig directory configuration (SOFTWARE-4621) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat): Kick off GlideinWMS 3.7.5 VMU tests GSI Transition AI (Carl): Address osg-token-renewer review comments Other AI (BrianL): Add backfill container CI tests AI (BrianL): add SSH certificate to the Hosted CE","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210907/#discussion","text":"A longer term project for Carl is to enable mass token requests so Harvester folks can make a token per CE.","title":"Discussion"},{"location":"meetings/2021/TechArea20210907/#support-update","text":"Lancium (BrianL): backfill containers with bind-mounted CVMFS weren't getting jobs because they did not specify shared to the bind mount","title":"Support Update"},{"location":"meetings/2021/TechArea20210907/#osg-devops","text":"New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210907/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210907/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing 3.5.46-upcoming and 3.6: HTCondor 9.0.5 and blahp 2.1.1 Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210907/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210914/","text":"OSG Technology Area Meeting, 14 September 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat Announcements \u00b6 Canceling next week's meeting due to HTCondor Week Mat OOO Sep 17-22 Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 10 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 162 -1 Open 33 +1 Selected for Dev 32 -5 In Progress 13 -1 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Review osg-token-renewer doc and merge if satisfied Other AI (BrianL): Add SSH certificate to the Hosted CE AI (BrianL): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (BrianL): Investigate host cert on the CMS Hosted CE at Frontera to see if UW needs to renew it Discussion \u00b6 GlideinWMS 3.9.3rc1 available; will be built into 3.5-contrib; requesting a build for 3.6 as well. GSI not completely removed yet but that's acceptable because it will help with the transition FNAL and CERN expected to announce EL8 plans in October Support Update \u00b6 Florida (BrianL): uncovered a few bugs with job router transforms in HTCondor-CE 5.1.1. To be fixed in 5.1.2 in an expected upstream release this week. Marian: add Andrew Melo back as an OASIS manager; contact Mat if Topology assistance is needed Mat: Assist Vlad at IceCube with permissions problems at their new Stash Origin; contact Derek for assistance as needed Carl: LIGO fixed their ProbeConfig and some records started showing up. LIGO-WA-CalTech records are sparse; Carl will ask LIGO if this is expected OSG DevOps \u00b6 New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 OSG 3.5.46 and OSG 3.6 Ready for Testing GlideinWMS 3.7.5 cvmfs-x509-helper 2.2-2 and osg-oasis 17-4 Ready for Release Nothing Discussion \u00b6 None this week","title":"September 14, 2021"},{"location":"meetings/2021/TechArea20210914/#osg-technology-area-meeting-14-september-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat","title":"OSG Technology Area Meeting, 14 September 2021"},{"location":"meetings/2021/TechArea20210914/#announcements","text":"Canceling next week's meeting due to HTCondor Week Mat OOO Sep 17-22","title":"Announcements"},{"location":"meetings/2021/TechArea20210914/#triage-duty","text":"This week: TimT Next week: BrianL (?) 10 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210914/#jira-as-of-monday","text":"# of tickets \u0394 State 162 -1 Open 33 +1 Selected for Dev 32 -5 In Progress 13 -1 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210914/#osg-software-team","text":"Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) GSI Transition AI (Carl): Review osg-token-renewer doc and merge if satisfied Other AI (BrianL): Add SSH certificate to the Hosted CE AI (BrianL): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (BrianL): Investigate host cert on the CMS Hosted CE at Frontera to see if UW needs to renew it","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210914/#discussion","text":"GlideinWMS 3.9.3rc1 available; will be built into 3.5-contrib; requesting a build for 3.6 as well. GSI not completely removed yet but that's acceptable because it will help with the transition FNAL and CERN expected to announce EL8 plans in October","title":"Discussion"},{"location":"meetings/2021/TechArea20210914/#support-update","text":"Florida (BrianL): uncovered a few bugs with job router transforms in HTCondor-CE 5.1.1. To be fixed in 5.1.2 in an expected upstream release this week. Marian: add Andrew Melo back as an OASIS manager; contact Mat if Topology assistance is needed Mat: Assist Vlad at IceCube with permissions problems at their new Stash Origin; contact Derek for assistance as needed Carl: LIGO fixed their ProbeConfig and some records started showing up. LIGO-WA-CalTech records are sparse; Carl will ask LIGO if this is expected","title":"Support Update"},{"location":"meetings/2021/TechArea20210914/#osg-devops","text":"New: - GRACC update completed; backup service verification to come this week. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. - Stashcp changes to support authenticated reading from /ospool namespace. Ongoing: - Shoveler is working and lightly tested. Collector is 90% done. - Checksums in xrootd-multiuser is 80% done. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210914/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210914/#osg-release-team","text":"OSG 3.5.46 and OSG 3.6 Ready for Testing GlideinWMS 3.7.5 cvmfs-x509-helper 2.2-2 and osg-oasis 17-4 Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210914/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210928/","text":"OSG Technology Area Meeting, 28 September 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Brian OOO Wed-Fri Carl OOO Wed Triage Duty \u00b6 This week: Mat Next week: Carl 12 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 164 +2 Open 33 +0 Selected for Dev 37 +5 In Progress 14 +1 Dev Complete 10 +6 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) GSI/GridFTP Transition AI (Carl): Address osg-token-renewer doc comments and merge Wei asked us to improve the XRootD standalone docs with info about Third-Party-Copy Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (Carl): Merge Topology and CILogon contact data Discussion \u00b6 None this week Support Update \u00b6 Lancium (BrianL): for Singularity-in-Singularity, GPUs aren't made available if the outer Singularity is < 3.8.0. On the plus side, GPUs work for unpriv Singularity in unpriv Singularity OSG DevOps \u00b6 New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Stashcp changes to support authenticated reading from /ospool namespace is done and lightly tested. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5 and OSG 3.6: CVMFS 2.8.2 cvmfs-x509-helper 2.2-2, osg-oasis 17-4 vault 1.8.2, htvault-config 1.6, and htgettoken 1.6 OSG 3.5-upcoming: GlideinWMS 3.7.5 xrootd-multiuser-2.0.2 OSG 3.5-upcoming and OSG 3.6: HTCondor 9.0.6 blahp 2.1.2 OSG 3.6-upcoming HTCondor 9.2.0 Ready for Release OSG 3.5 and OSG 3.6 osg-wn-client Discussion \u00b6 None this week","title":"September 28, 2021"},{"location":"meetings/2021/TechArea20210928/#osg-technology-area-meeting-28-september-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 28 September 2021"},{"location":"meetings/2021/TechArea20210928/#announcements","text":"Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Brian OOO Wed-Fri Carl OOO Wed","title":"Announcements"},{"location":"meetings/2021/TechArea20210928/#triage-duty","text":"This week: Mat Next week: Carl 12 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20210928/#jira-as-of-monday","text":"# of tickets \u0394 State 164 +2 Open 33 +0 Selected for Dev 37 +5 In Progress 14 +1 Dev Complete 10 +6 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20210928/#osg-software-team","text":"Release AI (Carl): Cut new Gratia Probe 2.x RPM AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) GSI/GridFTP Transition AI (Carl): Address osg-token-renewer doc comments and merge Wei asked us to improve the XRootD standalone docs with info about Third-Party-Copy Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL): Add Singularity backfill container CI tests AI (Carl): Merge Topology and CILogon contact data","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20210928/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210928/#support-update","text":"Lancium (BrianL): for Singularity-in-Singularity, GPUs aren't made available if the outer Singularity is < 3.8.0. On the plus side, GPUs work for unpriv Singularity in unpriv Singularity","title":"Support Update"},{"location":"meetings/2021/TechArea20210928/#osg-devops","text":"New: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Stashcp changes to support authenticated reading from /ospool namespace is done and lightly tested. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20210928/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20210928/#osg-release-team","text":"Ready for Testing OSG 3.5 and OSG 3.6: CVMFS 2.8.2 cvmfs-x509-helper 2.2-2, osg-oasis 17-4 vault 1.8.2, htvault-config 1.6, and htgettoken 1.6 OSG 3.5-upcoming: GlideinWMS 3.7.5 xrootd-multiuser-2.0.2 OSG 3.5-upcoming and OSG 3.6: HTCondor 9.0.6 blahp 2.1.2 OSG 3.6-upcoming HTCondor 9.2.0 Ready for Release OSG 3.5 and OSG 3.6 osg-wn-client","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20210928/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211005/","text":"OSG Technology Area Meeting, 5 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat, TimT Announcements \u00b6 Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Triage Duty \u00b6 This week: Carl Next week: TimT 12 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 168 +4 Open 34 +1 Selected for Dev 37 +0 In Progress 12 -2 Dev Complete 5 -5 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon Doc focus this Friday October 8, 1-5pm Release AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Singularity backfill container CI tests (SOFTWARE-4726) AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL/HTCondor developers): Make internal documentation for how to add SciTokens to a CE in preparation for the token workshop AI (Mat): Review remaining issues for the Let's Encrypt CA expiration fire. Discussion \u00b6 Marco: Debugging glideinWMS compatibility issues with HTCondor 9.0.6; attempting to install 9.0.1 for testing but having dependency issues. Brian says that it's a frequent issue when trying to install old versions of HTCondor on EL7. Mat suggests trying the HTCondor Docker images if a 9.0.1 version is available. Support Update \u00b6 TimT: Justas (Caltech) is requesting additional GPU attributes in the job classad; Tim will link him up with one of the HTCondor developers directly. Carl: There is no easy upgrade path to the Python 3 version of gfal2-util due to RPM dependency issues; filed a ticket with EPEL, will try to contact developers directly if there's no response to the ticket. Marian: Continuing to support LIGO with using IDTOKEN authentication. OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming and OSG 3.6 blahp 2.1.2 Ready for Release OSG 3.5 and OSG 3.6 IGTF 1.113 Discussion \u00b6 None this week","title":"October 5, 2021"},{"location":"meetings/2021/TechArea20211005/#osg-technology-area-meeting-5-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 5 October 2021"},{"location":"meetings/2021/TechArea20211005/#announcements","text":"Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/","title":"Announcements"},{"location":"meetings/2021/TechArea20211005/#triage-duty","text":"This week: Carl Next week: TimT 12 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211005/#jira-as-of-monday","text":"# of tickets \u0394 State 168 +4 Open 34 +1 Selected for Dev 37 +0 In Progress 12 -2 Dev Complete 5 -5 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211005/#osg-software-team","text":"Kubernetes Hackathon this afternoon Doc focus this Friday October 8, 1-5pm Release AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (BrianL): Add SSH certificate to the Hosted CE AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Singularity backfill container CI tests (SOFTWARE-4726) AI (Carl): Add Topology endpoint for querying resources tied to VOs AI (BrianL/HTCondor developers): Make internal documentation for how to add SciTokens to a CE in preparation for the token workshop AI (Mat): Review remaining issues for the Let's Encrypt CA expiration fire.","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211005/#discussion","text":"Marco: Debugging glideinWMS compatibility issues with HTCondor 9.0.6; attempting to install 9.0.1 for testing but having dependency issues. Brian says that it's a frequent issue when trying to install old versions of HTCondor on EL7. Mat suggests trying the HTCondor Docker images if a 9.0.1 version is available.","title":"Discussion"},{"location":"meetings/2021/TechArea20211005/#support-update","text":"TimT: Justas (Caltech) is requesting additional GPU attributes in the job classad; Tim will link him up with one of the HTCondor developers directly. Carl: There is no easy upgrade path to the Python 3 version of gfal2-util due to RPM dependency issues; filed a ticket with EPEL, will try to contact developers directly if there's no response to the ticket. Marian: Continuing to support LIGO with using IDTOKEN authentication.","title":"Support Update"},{"location":"meetings/2021/TechArea20211005/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211005/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211005/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming and OSG 3.6 blahp 2.1.2 Ready for Release OSG 3.5 and OSG 3.6 IGTF 1.113","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211005/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211012/","text":"OSG Technology Area Meeting, 12 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT Announcements \u00b6 Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/ Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 11 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 159 -9 Open 37 +3 Selected for Dev 40 +3 In Progress 12 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs Discussion \u00b6 None this week Support Update \u00b6 GP-ARGO (BrianL): Helped register them in Topology and get a backfill container started up. The container remains idle. (Derek) GRACC redirects broken. Fixed, but reminded Horst that redirects are not guarenteed forever! OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - stashcp feature request for better error messages. Added, waiting on some iterative feedback. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5 and OSG 3.6 osg-token-renewer 0.7.1 Ready for Release OSG 3.5-upcoming and OSG 3.6 blahp 2.1.3 Discussion \u00b6 None this week","title":"October 12, 2021"},{"location":"meetings/2021/TechArea20211012/#osg-technology-area-meeting-12-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 12 October 2021"},{"location":"meetings/2021/TechArea20211012/#announcements","text":"Token transition workshop Oct 14-15: https://indico.fnal.gov/event/50597/","title":"Announcements"},{"location":"meetings/2021/TechArea20211012/#triage-duty","text":"This week: TimT Next week: BrianL (?) 11 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211012/#jira-as-of-monday","text":"# of tickets \u0394 State 159 -9 Open 37 +3 Selected for Dev 40 +3 In Progress 12 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211012/#osg-software-team","text":"Release AI (Mat): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211012/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211012/#support-update","text":"GP-ARGO (BrianL): Helped register them in Topology and get a backfill container started up. The container remains idle. (Derek) GRACC redirects broken. Fixed, but reminded Horst that redirects are not guarenteed forever!","title":"Support Update"},{"location":"meetings/2021/TechArea20211012/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - stashcp feature request for better error messages. Added, waiting on some iterative feedback. Ongoing: - Shoveler and Collector is tested, now converting UNL to using the shoveler. - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211012/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211012/#osg-release-team","text":"Ready for Testing OSG 3.5 and OSG 3.6 osg-token-renewer 0.7.1 Ready for Release OSG 3.5-upcoming and OSG 3.6 blahp 2.1.3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211012/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211019/","text":"OSG Technology Area Meeting, 19 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL OOO Friday Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +1 Open 41 +4 Selected for Dev 38 -2 In Progress 11 -1 Dev Complete 0 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl, BrianL): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs Discussion \u00b6 HTCondor team planning to merge the BLAHP into the HTCondor source tree and build their packages together; this will eliminate the circular dependency between their packages. Support Update \u00b6 Token Transition Workshop (BrianL, Mat): many sites needed to adjust their AUTH_SSL_* CE config variables to continue to support IGTF CAs; also needed to update to scitokens-cpp-0.6.2 . HTCondor packaging will be updated upstream to require the latter. OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 None this week","title":"October 19, 2021"},{"location":"meetings/2021/TechArea20211019/#osg-technology-area-meeting-19-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 19 October 2021"},{"location":"meetings/2021/TechArea20211019/#announcements","text":"BrianL OOO Friday","title":"Announcements"},{"location":"meetings/2021/TechArea20211019/#triage-duty","text":"This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211019/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +1 Open 41 +4 Selected for Dev 38 -2 In Progress 11 -1 Dev Complete 0 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211019/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Other AI (Carl, BrianL): Merge Topology and CILogon contact data (SOFTWARE-4734) AI (BrianL): Add Topology endpoint for querying resources tied to VOs","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211019/#discussion","text":"HTCondor team planning to merge the BLAHP into the HTCondor source tree and build their packages together; this will eliminate the circular dependency between their packages.","title":"Discussion"},{"location":"meetings/2021/TechArea20211019/#support-update","text":"Token Transition Workshop (BrianL, Mat): many sites needed to adjust their AUTH_SSL_* CE config variables to continue to support IGTF CAs; also needed to update to scitokens-cpp-0.6.2 . HTCondor packaging will be updated upstream to require the latter.","title":"Support Update"},{"location":"meetings/2021/TechArea20211019/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211019/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211019/#osg-release-team","text":"Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211019/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211026/","text":"OSG Technology Area Meeting, 26 October 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, Marco Mambelli Announcements \u00b6 None this week Triage Duty \u00b6 This week: Mat Next week: Carl 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 164 +4 Open 42 +1 Selected for Dev 38 +0 In Progress 11 +0 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review gratia-probe PRs AI (BrianL): build gratia-probe and osg-flock for 3.6 Discussion \u00b6 There were some reports of user jobs failing in OSPool backfill containers due to insufficient storage space in /tmp . OSPool jobs almost always run inside Singularity containers and GlideinWMS has mechanisms that will decide what to mount from the host (in this case the backfill container), into /tmp inside the Singularity container: https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/glidein_startup.sh#L591 https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/singularity_lib.sh#L1639 It'd be worth checking to verify that the affected user jobs were running inside Singularity. Support Update \u00b6 None this week","title":"October 26, 2021"},{"location":"meetings/2021/TechArea20211026/#osg-technology-area-meeting-26-october-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, Marco Mambelli","title":"OSG Technology Area Meeting, 26 October 2021"},{"location":"meetings/2021/TechArea20211026/#announcements","text":"None this week","title":"Announcements"},{"location":"meetings/2021/TechArea20211026/#triage-duty","text":"This week: Mat Next week: Carl 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211026/#jira-as-of-monday","text":"# of tickets \u0394 State 164 +4 Open 42 +1 Selected for Dev 38 +0 In Progress 11 +0 Dev Complete 2 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211026/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review gratia-probe PRs AI (BrianL): build gratia-probe and osg-flock for 3.6","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211026/#discussion","text":"There were some reports of user jobs failing in OSPool backfill containers due to insufficient storage space in /tmp . OSPool jobs almost always run inside Singularity containers and GlideinWMS has mechanisms that will decide what to mount from the host (in this case the backfill container), into /tmp inside the Singularity container: https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/glidein_startup.sh#L591 https://github.com/glideinWMS/glideinwms/blob/fa3babd2452c7deeb2b8de543595aa2412ddef7b/creation/web_base/singularity_lib.sh#L1639 It'd be worth checking to verify that the affected user jobs were running inside Singularity.","title":"Discussion"},{"location":"meetings/2021/TechArea20211026/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2021/TechArea20211102/","text":"OSG Technology Area Meeting, 2 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 160 +1 Open 40 -2 Selected for Dev 42 +4 In Progress 11 +0 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl, BrianL): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) Discussion \u00b6 HTCondor 9.0.7 and 9.3.0 expected later today HTCondor credmon requires python-scitokens but it's currently shipped only in OSG repos, not EPEL, meaning it's not available for UW builds of HTCondor. TimT will decide if it's better to also ship python-scitokens in the HTCondor repos, or try and get it into EPEL. Support Update \u00b6 University of Colorado (BrianL): they were not receiving payload jobs, had them redeploy with updated containers and it appears that things are working ok now JLab (BrianL): help talk them through setting up a token issuer JLab (Marian): debugging why their new schedd does not show up in the VO Summary OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing Nothing Ready for Release Nothing Discussion \u00b6 None this week","title":"November 2, 2021"},{"location":"meetings/2021/TechArea20211102/#osg-technology-area-meeting-2-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 2 November 2021"},{"location":"meetings/2021/TechArea20211102/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20211102/#triage-duty","text":"This week: TimT Next week: BrianL (?) 11 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211102/#jira-as-of-monday","text":"# of tickets \u0394 State 160 +1 Open 40 -2 Selected for Dev 42 +4 In Progress 11 +0 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211102/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Mat) review xrootd-multiuser and osg-ca-certs-updater promotion requests AI (Carl, BrianL): Create new gratia-probe-condor-ap package (SOFTWARE-4846) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211102/#discussion","text":"HTCondor 9.0.7 and 9.3.0 expected later today HTCondor credmon requires python-scitokens but it's currently shipped only in OSG repos, not EPEL, meaning it's not available for UW builds of HTCondor. TimT will decide if it's better to also ship python-scitokens in the HTCondor repos, or try and get it into EPEL.","title":"Discussion"},{"location":"meetings/2021/TechArea20211102/#support-update","text":"University of Colorado (BrianL): they were not receiving payload jobs, had them redeploy with updated containers and it appears that things are working ok now JLab (BrianL): help talk them through setting up a token issuer JLab (Marian): debugging why their new schedd does not show up in the VO Summary","title":"Support Update"},{"location":"meetings/2021/TechArea20211102/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211102/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211102/#osg-release-team","text":"Ready for Testing Nothing Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211102/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211109/","text":"OSG Technology Area Meeting, 9 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT Announcements \u00b6 Doc focus this Friday (11/12) Marian leaving November 30 Triage Duty \u00b6 This week: BrianL Next week: Mat 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 161 +1 Open 39 -1 Selected for Dev 49 +7 In Progress 12 +1 Dev Complete 1 -6 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (BrianL): Release python-scitokens 1.6.0+ (SOFTWARE-4879) AI (Mat): Pegasus in OSG 3.6 (SOFTWARE-4877) AI (Mat): Release oidc-agent 4.2.2+ (SOFTWARE-4885) AI (Mat): kick off tests for vault/htvault/htgettoken (SOFTWARE-4884) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings Discussion \u00b6 GlideinWMS 3.9.3 is ready to go. Support Update \u00b6 Georgia State University (BrianL): followed up on their suggestion to use SSH ProxyCommand JLab (BrianL): had more discussions about setting up token issuers University of Southern California (BrianL): worked through issues requesting tokens for the backfill container and problems with startup University of Connecticut (Mat, Marian): modifying the namespaces that are exported in their Stash Origins. Mat provided XRootD configuration changes; Marian will take care of CVMFS syncing. JLab (Marian, BrianL): Updated certificate configuration in JLab frontend to avoid issues with the Let's Encrypt root certificate. NIKHEF (Marian): Helping update their HTCondor install; there is a large version jump so much config has to be adjusted. OSG DevOps \u00b6 New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744 Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3 Discussion \u00b6 None this week","title":"November 9, 2021"},{"location":"meetings/2021/TechArea20211109/#osg-technology-area-meeting-9-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marian, Mat, TimT","title":"OSG Technology Area Meeting, 9 November 2021"},{"location":"meetings/2021/TechArea20211109/#announcements","text":"Doc focus this Friday (11/12) Marian leaving November 30","title":"Announcements"},{"location":"meetings/2021/TechArea20211109/#triage-duty","text":"This week: BrianL Next week: Mat 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211109/#jira-as-of-monday","text":"# of tickets \u0394 State 161 +1 Open 39 -1 Selected for Dev 49 +7 In Progress 12 +1 Dev Complete 1 -6 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211109/#osg-software-team","text":"Release AI (Mat, BrianL): XRootD in OSG 3.6 (SOFTWARE-4494) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (BrianL): Release python-scitokens 1.6.0+ (SOFTWARE-4879) AI (Mat): Pegasus in OSG 3.6 (SOFTWARE-4877) AI (Mat): Release oidc-agent 4.2.2+ (SOFTWARE-4885) AI (Mat): kick off tests for vault/htvault/htgettoken (SOFTWARE-4884) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211109/#discussion","text":"GlideinWMS 3.9.3 is ready to go.","title":"Discussion"},{"location":"meetings/2021/TechArea20211109/#support-update","text":"Georgia State University (BrianL): followed up on their suggestion to use SSH ProxyCommand JLab (BrianL): had more discussions about setting up token issuers University of Southern California (BrianL): worked through issues requesting tokens for the backfill container and problems with startup University of Connecticut (Mat, Marian): modifying the namespaces that are exported in their Stash Origins. Mat provided XRootD configuration changes; Marian will take care of CVMFS syncing. JLab (Marian, BrianL): Updated certificate configuration in JLab frontend to avoid issues with the Let's Encrypt root certificate. NIKHEF (Marian): Helping update their HTCondor install; there is a large version jump so much config has to be adjusted.","title":"Support Update"},{"location":"meetings/2021/TechArea20211109/#osg-devops","text":"New: - Transition to IDTOKENs for IGWN, JLab, GLUEX - Shoveler and Collector is tested, and UNL is using it in production now. - Now writing docs on how to run the shoveler. Ongoing: - Request to inject entire HTCondor job classad into GRACC records. Will require gratia-probe-condor changes. Back burner: - (Stalled, but need to get back to it) XRootD accounting information (from Frank): - May need help with automating the process of generating these reports. A month only takes a few minutes. Longer periods take much longer. - Table of working set, read, and re-read for monthly, quarterly, and year. - XRootD TCP plugin is ready for packaging. Derek will follow up with software team on who to hand that off to. - https://opensciencegrid.atlassian.net/browse/SOFTWARE-4744","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211109/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211109/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211109/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211116/","text":"OSG Technology Area Meeting, 16 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 161 +0 Open 42 +3 Selected for Dev 39 -10 In Progress 9 -3 Dev Complete 11 +10 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Release AI (Mat): Release XRootD 5.3.3 in OSG 3.6 (SOFTWARE-4885) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): investigate HTCondor-CE failures in the nightlies (SOFTWARE-4901) Discussion \u00b6 None this week Support Update \u00b6 Georgia State University (BrianL): needed to add pre-populated known_hosts since ssh-keyscan doesn't work with jump hosts JLab (BrianL): had a meeting to discuss token issuers; they'll likely start with a local issuer for pilots and will consider CILogon as their issuer Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6 OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3 Discussion \u00b6 None this week","title":"November 16, 2021"},{"location":"meetings/2021/TechArea20211116/#osg-technology-area-meeting-16-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT","title":"OSG Technology Area Meeting, 16 November 2021"},{"location":"meetings/2021/TechArea20211116/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20211116/#triage-duty","text":"This week: Mat Next week: TimT 11 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211116/#jira-as-of-monday","text":"# of tickets \u0394 State 161 +0 Open 42 +3 Selected for Dev 39 -10 In Progress 9 -3 Dev Complete 11 +10 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211116/#osg-software-team","text":"Release AI (Mat): Release XRootD 5.3.3 in OSG 3.6 (SOFTWARE-4885) AI (Carl, BrianL): osg-pki-tools in OSG 3.6 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): investigate HTCondor-CE failures in the nightlies (SOFTWARE-4901)","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211116/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211116/#support-update","text":"Georgia State University (BrianL): needed to add pre-populated known_hosts since ssh-keyscan doesn't work with jump hosts JLab (BrianL): had a meeting to discuss token issuers; they'll likely start with a local issuer for pilots and will consider CILogon as their issuer Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6","title":"Support Update"},{"location":"meetings/2021/TechArea20211116/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming XRootD 5.3.2 Ready for Release OSG 3.5 osg-ca-certs-updater 2.0 OSG 3.5-upcoming xrootd-multiuser 2.0.3 OSG 3.6 gratia-probe 2.3.2 osg-flock 1.6-3","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211116/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211123/","text":"OSG Technology Area Meeting, 23 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: BrianL 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 162 +1 Open 41 -1 Selected for Dev 31 +2 In Progress 10 +1 Dev Complete 14 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (BrianL): WLCG VO DN update in the vo-client (SOFTWARE-4912) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): Investigate OSPool registry pod stuck in Pending AI (BrianL): Give CMS a recipe to generate pilot configuration without using osg-configure Discussion \u00b6 HTCondor scitokens-credmon for EL8: aiming for Post-christmas release Marco: Fixing GlideinWMS 3.7.6 bugs; afterwards, further development will be Python 3 only. There are several patches used in OSG OS Pool frontend -- Marco will talk to Mats Rynge about getting them upstream. Proxy delegation in the OSG 3.6 build of HTCondor 9 is broken; does not affect the OSG 3.5-upcoming build, and will be fixed in 9.0.8. Fermilab is hiring for a developer position. Support Update \u00b6 Lancium (BrianL): GPUs not showing up in Lancium resources due to HTCondor 9.0.6 GPU discovery bug; OS Registry doesn't work with Google IDs since they don't provide an eduPersonPrincipalName ( eppn ) Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6 LBL (Mat): Gratia probes weren't reporting in; this was due to files on disk not having been properly restored from backup; yum reinstall fixed the issue. OSG Release Team \u00b6 Aiming for a release next week: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works) Discussion \u00b6 None this week","title":"November 23, 2021"},{"location":"meetings/2021/TechArea20211123/#osg-technology-area-meeting-23-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 23 November 2021"},{"location":"meetings/2021/TechArea20211123/#announcements","text":"","title":"Announcements"},{"location":"meetings/2021/TechArea20211123/#triage-duty","text":"This week: TimT Next week: BrianL 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211123/#jira-as-of-monday","text":"# of tickets \u0394 State 162 +1 Open 41 -1 Selected for Dev 31 +2 In Progress 10 +1 Dev Complete 14 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211123/#osg-software-team","text":"Release AI (BrianL): WLCG VO DN update in the vo-client (SOFTWARE-4912) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) AI (Mat): oidc-agent 4.2.2+ (SOFTWARE-4885) Token transition AI (Mat): add the ability to specify subjects + description to token issuer mappings AI (BrianL): Investigate OSPool registry pod stuck in Pending AI (BrianL): Give CMS a recipe to generate pilot configuration without using osg-configure","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211123/#discussion","text":"HTCondor scitokens-credmon for EL8: aiming for Post-christmas release Marco: Fixing GlideinWMS 3.7.6 bugs; afterwards, further development will be Python 3 only. There are several patches used in OSG OS Pool frontend -- Marco will talk to Mats Rynge about getting them upstream. Proxy delegation in the OSG 3.6 build of HTCondor 9 is broken; does not affect the OSG 3.5-upcoming build, and will be fixed in 9.0.8. Fermilab is hiring for a developer position.","title":"Discussion"},{"location":"meetings/2021/TechArea20211123/#support-update","text":"Lancium (BrianL): GPUs not showing up in Lancium resources due to HTCondor 9.0.6 GPU discovery bug; OS Registry doesn't work with Google IDs since they don't provide an eduPersonPrincipalName ( eppn ) Nikhef (BrianL, Marian, Diego): helped troubleshoot IDTOKEN exchange since they updated to OSG 3.6 LBL (Mat): Gratia probes weren't reporting in; this was due to files on disk not having been properly restored from backup; yum reinstall fixed the issue.","title":"Support Update"},{"location":"meetings/2021/TechArea20211123/#osg-release-team","text":"Aiming for a release next week: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works)","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211123/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211130/","text":"OSG Technology Area Meeting, 30 November 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T Announcements \u00b6 BrianL out next Monday, Dec 6 Triage Duty \u00b6 This week: BrianL Next week: Mat 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 181 +19 Open 22 -19 Selected for Dev 39 -2 In Progress 8 -2 Dev Complete 16 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today AI (BrianL): Put certmanager config of individual VO frontends into the base vo-frontend resource AI (Mat): Work with John Thiltges to set up an additional instance of repo.opensciencegrid.org on the River cluster Release AI (BrianL): Release xrootd 5.3.3+ for OSG 3.5 upcoming and OSG 3.6 (SOFTWARE-4903, SOFTWARE-4904) AI (Mat): Create transitional dummy package for xrootd-lcmaps in 3.6 (SOFTWARE-4481) AI (BrianL): Release xrootd-rucioN2N-for-Xcache-1.2-3.3+ in OSG 3.6 (SOFTWARE-4894) AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) Token transition AI (Mat): add the ability to specify subjects to token issuer mappings (SOFTWARE-4915) AI (Mat): merge xrootd-for-3.6 osg-test branch into master AI (BrianL): Investigate XRootD 3.6 TPC failures in the nightlies Discussion \u00b6 XRootD 5.3.2 will be released for 3.6 this week, with the caveat that origins shouldn't use it. GlideinWMS 3.7.6 is in progress (likely the last feature release for 3.7), as is CentOS 8 support for the 3.9 series. Support Update \u00b6 Lancium (BrianL): OS Registry doesn't work with Google or ORCID accounts since they don't provide an eduPersonPrincipalName ( eppn ) BNL (BrianL): help with OSPool Token Registry issues with the BNL and BNL-SDCC IdPs BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV OSG DevOps \u00b6 Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler going to be tested at Florida tomorrow Discussion \u00b6 None this week OSG Release Team \u00b6 Release tomorrow: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works) Discussion \u00b6 None this week","title":"November 30, 2021"},{"location":"meetings/2021/TechArea20211130/#osg-technology-area-meeting-30-november-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 30 November 2021"},{"location":"meetings/2021/TechArea20211130/#announcements","text":"BrianL out next Monday, Dec 6","title":"Announcements"},{"location":"meetings/2021/TechArea20211130/#triage-duty","text":"This week: BrianL Next week: Mat 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211130/#jira-as-of-monday","text":"# of tickets \u0394 State 181 +19 Open 22 -19 Selected for Dev 39 -2 In Progress 8 -2 Dev Complete 16 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211130/#osg-software-team","text":"Kubernetes Hackathon today AI (BrianL): Put certmanager config of individual VO frontends into the base vo-frontend resource AI (Mat): Work with John Thiltges to set up an additional instance of repo.opensciencegrid.org on the River cluster Release AI (BrianL): Release xrootd 5.3.3+ for OSG 3.5 upcoming and OSG 3.6 (SOFTWARE-4903, SOFTWARE-4904) AI (Mat): Create transitional dummy package for xrootd-lcmaps in 3.6 (SOFTWARE-4481) AI (BrianL): Release xrootd-rucioN2N-for-Xcache-1.2-3.3+ in OSG 3.6 (SOFTWARE-4894) AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (BrianL): osg-pki-tools in EL8 (SOFTWARE-4786) Token transition AI (Mat): add the ability to specify subjects to token issuer mappings (SOFTWARE-4915) AI (Mat): merge xrootd-for-3.6 osg-test branch into master AI (BrianL): Investigate XRootD 3.6 TPC failures in the nightlies","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211130/#discussion","text":"XRootD 5.3.2 will be released for 3.6 this week, with the caveat that origins shouldn't use it. GlideinWMS 3.7.6 is in progress (likely the last feature release for 3.7), as is CentOS 8 support for the 3.9 series.","title":"Discussion"},{"location":"meetings/2021/TechArea20211130/#support-update","text":"Lancium (BrianL): OS Registry doesn't work with Google or ORCID accounts since they don't provide an eduPersonPrincipalName ( eppn ) BNL (BrianL): help with OSPool Token Registry issues with the BNL and BNL-SDCC IdPs BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV","title":"Support Update"},{"location":"meetings/2021/TechArea20211130/#osg-devops","text":"Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler going to be tested at Florida tomorrow","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211130/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211130/#osg-release-team","text":"Release tomorrow: Ready for Release OSG 3.5 vo-client 115 python-scitokens 1.6.2 OSG 3.5-upcoming HTCondor 9.0.7 (has GSI, proxy delegation works) OSG 3.6 vo-client 115 XRootD 5.3.2 xrootd-multiuser 2.0.3 XCache 3.0.0 osg-xrootd 3.6-10 HTCondor 9.0.7 (no GSI, proxy delegation broken) blahp 2.2.0 (no GSI) GlideinWMS 3.9.3 Pegasus 5.0.1 python-scitokens 1.6.2 OSG 3.6-upcoming HTCondor 9.3.0 (no GSI, proxy delegation works)","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211130/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211207/","text":"OSG Technology Area Meeting, 7 December 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL out today Mat out this afternoon and tomorrow Triage Duty \u00b6 This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 183 +2 Open 22 +0 Selected for Dev 30 -9 In Progress 10 +2 Dev Complete 5 -11 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Create secondary instance of repo.openscience.org on the UChicago River cluster. AI (Mat): Test vault/htvault-config/htgettoken AI (Brian): Set osg-flock VOOverride to \"osg\" AI (TimT): Release HTCondors 9.0.8 and 9.4.0 Discussion \u00b6 Tim added \"devops-minefield\" repos to osg-release; this can be tested manually. Marco: GlideinWMS 3.7.6 is in progress; most GitHub issues have been merged, as well as a new check for expired tokens. A release candidate is expected later today. The GlideinWMS license is changing from Fermi-modified BSD to Apache2; using REUSE (reuse.software) and SPDX (spdx.org), which make managing licenses in source code very convenient; these might be also be useful for other OSG projects and HTCondor team. Support Update \u00b6 BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (Mat, BrianL): debug not finding Singularity in backfill container GATech (Derek): Gratia probe is reporting a lot of groups. OSG DevOps \u00b6 Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them) Discussion \u00b6 None this week OSG Release Team \u00b6 Release this week: Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.3.4 Ready for Testing OSG 3.6-upcoming Soon: HTCondor 9.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Soon: HTCondor 9.0.8 (should fix proxy delegation) OSG 3.5-upcoming Soon: HTCondor 9.0.8 OSG 3.5 oidc-agent 4.2.4 Discussion \u00b6 None this week","title":"December 7, 2021"},{"location":"meetings/2021/TechArea20211207/#osg-technology-area-meeting-7-december-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 7 December 2021"},{"location":"meetings/2021/TechArea20211207/#announcements","text":"BrianL out today Mat out this afternoon and tomorrow","title":"Announcements"},{"location":"meetings/2021/TechArea20211207/#triage-duty","text":"This week: Mat Next week: TimT 9 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211207/#jira-as-of-monday","text":"# of tickets \u0394 State 183 +2 Open 22 +0 Selected for Dev 30 -9 In Progress 10 +2 Dev Complete 5 -11 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211207/#osg-software-team","text":"AI (Mat): Create secondary instance of repo.openscience.org on the UChicago River cluster. AI (Mat): Test vault/htvault-config/htgettoken AI (Brian): Set osg-flock VOOverride to \"osg\" AI (TimT): Release HTCondors 9.0.8 and 9.4.0","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211207/#discussion","text":"Tim added \"devops-minefield\" repos to osg-release; this can be tested manually. Marco: GlideinWMS 3.7.6 is in progress; most GitHub issues have been merged, as well as a new check for expired tokens. A release candidate is expected later today. The GlideinWMS license is changing from Fermi-modified BSD to Apache2; using REUSE (reuse.software) and SPDX (spdx.org), which make managing licenses in source code very convenient; these might be also be useful for other OSG projects and HTCondor team.","title":"Discussion"},{"location":"meetings/2021/TechArea20211207/#support-update","text":"BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (Mat, BrianL): debug not finding Singularity in backfill container GATech (Derek): Gratia probe is reporting a lot of groups.","title":"Support Update"},{"location":"meetings/2021/TechArea20211207/#osg-devops","text":"Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them)","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211207/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211207/#osg-release-team","text":"Release this week: Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.3.4 Ready for Testing OSG 3.6-upcoming Soon: HTCondor 9.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Soon: HTCondor 9.0.8 (should fix proxy delegation) OSG 3.5-upcoming Soon: HTCondor 9.0.8 OSG 3.5 oidc-agent 4.2.4","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211207/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211214/","text":"OSG Technology Area Meeting, 14 December 2021 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT Announcements \u00b6 Mat out Thursday afternoon Doc focus Friday afternoon Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 4 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 179 -4 Open 23 +1 Selected for Dev 30 +0 In Progress 10 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (Mat): Convert osg-pki-tools to Python 3 AI (Brian): Build XRootD with Brian's patch AI (Brian): Set osg-flock VOOverride to \"osg\" Discussion \u00b6 The HTCondor OAuth Credmon's dependencies only have Python 2 versions on EL 7; we'll need a python-scitokens version for Python 2, even if it's security-fixes only. Support Update \u00b6 BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (BrianL): moved them over to Singularity-in-Singularity and had to adjust their bind mount settings GATech (Derek): Gratia probe is reporting a lot of groups. UConn (BrianL): job router config not correctly converted from old syntax to new syntax: extra quotes in the grid resource caused connection failure OSG DevOps \u00b6 Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them) Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release Nothing Ready for Testing OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Discussion \u00b6 None this week","title":"December 14, 2021"},{"location":"meetings/2021/TechArea20211214/#osg-technology-area-meeting-14-december-2021","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Mat, TimT","title":"OSG Technology Area Meeting, 14 December 2021"},{"location":"meetings/2021/TechArea20211214/#announcements","text":"Mat out Thursday afternoon Doc focus Friday afternoon","title":"Announcements"},{"location":"meetings/2021/TechArea20211214/#triage-duty","text":"This week: TimT Next week: BrianL (?) 4 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2021/TechArea20211214/#jira-as-of-monday","text":"# of tickets \u0394 State 179 -4 Open 23 +1 Selected for Dev 30 +0 In Progress 10 +0 Dev Complete 3 -2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2021/TechArea20211214/#osg-software-team","text":"Kubernetes hackathon today AI (Mat): Package xrootd-tcp-stats plugin (SOFTWARE-4744) AI (Mat): Convert osg-pki-tools to Python 3 AI (Brian): Build XRootD with Brian's patch AI (Brian): Set osg-flock VOOverride to \"osg\"","title":"OSG Software Team"},{"location":"meetings/2021/TechArea20211214/#discussion","text":"The HTCondor OAuth Credmon's dependencies only have Python 2 versions on EL 7; we'll need a python-scitokens version for Python 2, even if it's security-fixes only.","title":"Discussion"},{"location":"meetings/2021/TechArea20211214/#support-update","text":"BNL (Mat): debug authentication issues when accessing an xrootd server using WebDAV Lancium (BrianL): moved them over to Singularity-in-Singularity and had to adjust their bind mount settings GATech (Derek): Gratia probe is reporting a lot of groups. UConn (BrianL): job router config not correctly converted from old syntax to new syntax: extra quotes in the grid resource caused connection failure","title":"Support Update"},{"location":"meetings/2021/TechArea20211214/#osg-devops","text":"Stashcp now supports recursive downloads. Release upcoming. How should we handle packaging of stashcache-client in OSG repos? Some stashcp debugging is in order for proxy support. xrootd-monitoring-shoveler running at UCSD and Florida (RPM) and UNL (K8s) Go packaging: No network for builds, so deps come from EPEL or from a dependency bundle. Derek will investigate what dependencies are already in EPEL (likely all of them)","title":"OSG DevOps"},{"location":"meetings/2021/TechArea20211214/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2021/TechArea20211214/#osg-release-team","text":"Ready for Release Nothing Ready for Testing OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 CVMFS 2.9.0 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4","title":"OSG Release Team"},{"location":"meetings/2021/TechArea20211214/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220104/","text":"OSG Technology Area Meeting, 4 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Mat, TimT Announcements \u00b6 Brian out today. Triage Duty \u00b6 This week: Mat Next week: BrianL (?) 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 178 -1 Open 21 -2 Selected for Dev 35 +5 In Progress 10 +0 Dev Complete 9 +7 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Mat: update stashcache-client RPM to contain stashcp 6.4.0 TimT: release HTCondor 9.0.9+, HTCondor 9.5.0+ Discussion \u00b6 HTCondor developers adding Rocky Linux 8 as one of their platforms for UW builds (replacing CentOS Linux 8, which was EOL as of the end of last year). OSG is testing on Rocky Linux 8 (among other compatible platforms) but still using CentOS Linux 8 for build repos; no decision on yet on which variant to use as a replacement but CentOS Stream 8 is likely since that is what Fermilab is using. Support Update \u00b6 Doug Benjamin (BNL) needed to be added as a Topology contact for several resources for submitting downtime; TimC is working on making sure Topology contacts are up to date. Gluex was unable to access some of their files hosted on stash origins via CVMFS; their directory had too many files and bloated the CVMFS catalog to the point where it kept getting evicted from clients' caches. Derek split the catalog into smaller catalogs, which should solve the problem. OSG DevOps \u00b6 Discussion \u00b6 None this week OSG Release Team \u00b6 Discussion \u00b6 None this week","title":"January 4, 2022"},{"location":"meetings/2022/TechArea20220104/#osg-technology-area-meeting-4-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Mat, TimT","title":"OSG Technology Area Meeting, 4 January 2022"},{"location":"meetings/2022/TechArea20220104/#announcements","text":"Brian out today.","title":"Announcements"},{"location":"meetings/2022/TechArea20220104/#triage-duty","text":"This week: Mat Next week: BrianL (?) 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220104/#jira-as-of-monday","text":"# of tickets \u0394 State 178 -1 Open 21 -2 Selected for Dev 35 +5 In Progress 10 +0 Dev Complete 9 +7 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220104/#osg-software-team","text":"Mat: update stashcache-client RPM to contain stashcp 6.4.0 TimT: release HTCondor 9.0.9+, HTCondor 9.5.0+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220104/#discussion","text":"HTCondor developers adding Rocky Linux 8 as one of their platforms for UW builds (replacing CentOS Linux 8, which was EOL as of the end of last year). OSG is testing on Rocky Linux 8 (among other compatible platforms) but still using CentOS Linux 8 for build repos; no decision on yet on which variant to use as a replacement but CentOS Stream 8 is likely since that is what Fermilab is using.","title":"Discussion"},{"location":"meetings/2022/TechArea20220104/#support-update","text":"Doug Benjamin (BNL) needed to be added as a Topology contact for several resources for submitting downtime; TimC is working on making sure Topology contacts are up to date. Gluex was unable to access some of their files hosted on stash origins via CVMFS; their directory had too many files and bloated the CVMFS catalog to the point where it kept getting evicted from clients' caches. Derek split the catalog into smaller catalogs, which should solve the problem.","title":"Support Update"},{"location":"meetings/2022/TechArea20220104/#osg-devops","text":"","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220104/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220104/#osg-release-team","text":"","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220104/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220111/","text":"OSG Technology Area Meeting, 11 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Mat 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 180 +2 Open 18 -3 Selected for Dev 36 +1 In Progress 10 +0 Dev Complete 13 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): release stashcp 6.5.3+ K8s Hackathon: test functionality of \"canary\" CEs; start moving Koji components to Kubernetes AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release new osg-flock Discussion \u00b6 xrootd-tcp-stats is ready for testing; planning to test on a small set of hosts before adding it to the defaults in osg-xrootd Support Update \u00b6 Lancium (BrianL): pilot container probe has had issues querying the HA OSPool collectors since Dec 21. UTC-Epyc (BrianL, Mat): lots of stash related transfer failures. Worked on disabling stash at the site. OSG DevOps \u00b6 K8s Hackathon: Work on xrootd monitoring collector. Mostly asking questions... Following up on issues noted by Mat on StashCP Working on improving GeoIP algorithms Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Ready for Testing OSG 3.5, OSG 3.6 vo-client 116 (data) osg-scitokens-mapfile 4 (data) osg-pki-tools 3.5.0-2 (Python 3 conversion) OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 xrootd-tcp-stats 1.0.0 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12 Discussion \u00b6 None this week","title":"January 11, 2022"},{"location":"meetings/2022/TechArea20220111/#osg-technology-area-meeting-11-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 11 January 2022"},{"location":"meetings/2022/TechArea20220111/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220111/#triage-duty","text":"This week: BrianL Next week: Mat 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220111/#jira-as-of-monday","text":"# of tickets \u0394 State 180 +2 Open 18 -3 Selected for Dev 36 +1 In Progress 10 +0 Dev Complete 13 +4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220111/#osg-software-team","text":"AI (Mat): release stashcp 6.5.3+ K8s Hackathon: test functionality of \"canary\" CEs; start moving Koji components to Kubernetes AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release new osg-flock","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220111/#discussion","text":"xrootd-tcp-stats is ready for testing; planning to test on a small set of hosts before adding it to the defaults in osg-xrootd","title":"Discussion"},{"location":"meetings/2022/TechArea20220111/#support-update","text":"Lancium (BrianL): pilot container probe has had issues querying the HA OSPool collectors since Dec 21. UTC-Epyc (BrianL, Mat): lots of stash related transfer failures. Worked on disabling stash at the site.","title":"Support Update"},{"location":"meetings/2022/TechArea20220111/#osg-devops","text":"K8s Hackathon: Work on xrootd monitoring collector. Mostly asking questions... Following up on issues noted by Mat on StashCP Working on improving GeoIP algorithms","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220111/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220111/#osg-release-team","text":"Ready for Release OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.0 OSG 3.6 vault 1.9, htvault-config 1.11, htgettoken 1.9 oidc-agent 4.2.4 Ready for Testing OSG 3.5, OSG 3.6 vo-client 116 (data) osg-scitokens-mapfile 4 (data) osg-pki-tools 3.5.0-2 (Python 3 conversion) OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 xrootd-tcp-stats 1.0.0 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220111/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220118/","text":"OSG Technology Area Meeting, 11 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 6 (+2) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 179 -1 Open 21 -3 Selected for Dev 32 -4 In Progress 10 +0 Dev Complete 5 -8 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): release stashcp 6.5.3+ AI (Mat): add ATLAS IAM to vo-client: should only require a packaging change AI (Mat): Write osg-resource-catalog-generator. AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release osg-flock 1.7+ Discussion \u00b6 EPEL metadata broken in EL7 Koji builds; a regen-repo should fix that. AI (student): write a script to run the appropriate regen-repo commands next time. HEPCloud version 2 release candidate is expected today. GlideinWMS 3.7.6 release candidate is out and being tested by Marco Mascheroni at the CERN ITB. Support Update \u00b6 BNL (Mat): Debugging authentication issues with XRootD. OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12 Discussion \u00b6 Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"January 18, 2022"},{"location":"meetings/2022/TechArea20220118/#osg-technology-area-meeting-11-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 11 January 2022"},{"location":"meetings/2022/TechArea20220118/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220118/#triage-duty","text":"This week: Mat Next week: TimT 6 (+2) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220118/#jira-as-of-monday","text":"# of tickets \u0394 State 179 -1 Open 21 -3 Selected for Dev 32 -4 In Progress 10 +0 Dev Complete 5 -8 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220118/#osg-software-team","text":"AI (Mat): release stashcp 6.5.3+ AI (Mat): add ATLAS IAM to vo-client: should only require a packaging change AI (Mat): Write osg-resource-catalog-generator. AI (TimT): release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): release osg-flock 1.7+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220118/#discussion","text":"EPEL metadata broken in EL7 Koji builds; a regen-repo should fix that. AI (student): write a script to run the appropriate regen-repo commands next time. HEPCloud version 2 release candidate is expected today. GlideinWMS 3.7.6 release candidate is out and being tested by Marco Mascheroni at the CERN ITB.","title":"Discussion"},{"location":"meetings/2022/TechArea20220118/#support-update","text":"BNL (Mat): Debugging authentication issues with XRootD.","title":"Support Update"},{"location":"meetings/2022/TechArea20220118/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220118/#discussion_1","text":"Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"Discussion"},{"location":"meetings/2022/TechArea20220125/","text":"OSG Technology Area Meeting, 25 January 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco, Mat, TimT Announcements \u00b6 OSG site admin office hours today, 1-4pm Central Triage Duty \u00b6 This week: TimT Next week: BrianL (?) 7 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 180 +1 Open 24 +3 Selected for Dev 31 -1 In Progress 10 +0 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-resource-catalog-generator, update osg-configure-bosco deps and script refs AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): Release osg-flock 1.7+ AI (BrianL): Create new release tags for XRootD images. AI (BrianL): Collaborate with Fermi to get default token mappings for their experiments. Discussion \u00b6 GlideinWMS 3.7.6 released, which is the last of the 3.7 series. Most frontends (GLOW, OSPool, IGWN, and others) are already using the 3.9 series, as is HEPCloud. A workaround is available for the credential name issue on GSI-less frontends, and will be documented in the ticket. Dennis is working on a fix. GlideinWMS team is working on a way to send a token to GCE and AWS pilots since HTCondor file transfer does not work. TJ of the HTCondor Team is also working on a solution. Discussed whether HTCondor patch releases should be moved out of the devops repos into the mainline repos. We've decided against it because patch releases are more intended for testing on the OS Pool than for general usage. The stashcp RPM in progress for OSG is binary-only because Go 1.16 is not available in EPEL 7. Dave Dykstra mentioned trying to get the EPEL version of Go updated; if he is successful, we can revisit the packaging. Support Update \u00b6 ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. Purdue (BrianL): CE jobs evicted OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12 Discussion \u00b6 Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"January 25, 2022"},{"location":"meetings/2022/TechArea20220125/#osg-technology-area-meeting-25-january-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 25 January 2022"},{"location":"meetings/2022/TechArea20220125/#announcements","text":"OSG site admin office hours today, 1-4pm Central","title":"Announcements"},{"location":"meetings/2022/TechArea20220125/#triage-duty","text":"This week: TimT Next week: BrianL (?) 7 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220125/#jira-as-of-monday","text":"# of tickets \u0394 State 180 +1 Open 24 +3 Selected for Dev 31 -1 In Progress 10 +0 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220125/#osg-software-team","text":"AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-resource-catalog-generator, update osg-configure-bosco deps and script refs AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): Release osg-flock 1.7+ AI (BrianL): Create new release tags for XRootD images. AI (BrianL): Collaborate with Fermi to get default token mappings for their experiments.","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220125/#discussion","text":"GlideinWMS 3.7.6 released, which is the last of the 3.7 series. Most frontends (GLOW, OSPool, IGWN, and others) are already using the 3.9 series, as is HEPCloud. A workaround is available for the credential name issue on GSI-less frontends, and will be documented in the ticket. Dennis is working on a fix. GlideinWMS team is working on a way to send a token to GCE and AWS pilots since HTCondor file transfer does not work. TJ of the HTCondor Team is also working on a solution. Discussed whether HTCondor patch releases should be moved out of the devops repos into the mainline repos. We've decided against it because patch releases are more intended for testing on the OS Pool than for general usage. The stashcp RPM in progress for OSG is binary-only because Go 1.16 is not available in EPEL 7. Dave Dykstra mentioned trying to get the EPEL version of Go updated; if he is successful, we can revisit the packaging.","title":"Discussion"},{"location":"meetings/2022/TechArea20220125/#support-update","text":"ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. Purdue (BrianL): CE jobs evicted","title":"Support Update"},{"location":"meetings/2022/TechArea20220125/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220125/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220125/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming, OSG 3.6 HTCondor-CE 5.1.3 OSG 3.6 CVMFS 2.9.0 osg-xrootd 3.6-12","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220125/#discussion_2","text":"Check Central Collector for CEs running 5.1.3 Mention CVMFS needs testing at the afternoon Production Meeting","title":"Discussion"},{"location":"meetings/2022/TechArea20220201/","text":"OSG Technology Area Meeting, 1 February 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Mat 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 185 +5 Open 28 +4 Selected for Dev 33 +2 In Progress 9 -1 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-ce-attributes-generator update osg-configure-bosco deps and script refs AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): add support for manual client registration to osg-token-renewer Discussion \u00b6 None this week Support Update \u00b6 ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. MWT2 (BrianL): troubleshoot issues with missing accounting records. Got everything restored. Purdue (BrianL): CE jobs evicted, appears to be removals from the factory side UCSD (Mat): Debugging cache server issues reporting to central collector OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release OSG 3.6 Gratia Probe 2.5.1 Ready for Testing OSG 3.6, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 osg-flock 1.7 OSG 3.6 upcoming HTCondor 9.5.0 Discussion \u00b6 None this week","title":"February 1, 2022"},{"location":"meetings/2022/TechArea20220201/#osg-technology-area-meeting-1-february-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian, Mat, Tim","title":"OSG Technology Area Meeting, 1 February 2022"},{"location":"meetings/2022/TechArea20220201/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220201/#triage-duty","text":"This week: BrianL Next week: Mat 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220201/#jira-as-of-monday","text":"# of tickets \u0394 State 185 +5 Open 28 +4 Selected for Dev 33 +2 In Progress 9 -1 Dev Complete 7 +5 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220201/#osg-software-team","text":"AI (Mat): Release stashcp 6.5.3+ AI (Mat): Write osg-ce-attributes-generator update osg-configure-bosco deps and script refs AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (TimT): Release HTCondor 9.0.9+, HTCondor 9.5.0+ AI (BrianL): add support for manual client registration to osg-token-renewer","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220201/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220201/#support-update","text":"ASU (BrianL): Investigate no pilot hours due to too many open FDs while running Gratia BNL (Mat): Debugging authentication issues with XRootD. MWT2 (BrianL): troubleshoot issues with missing accounting records. Got everything restored. Purdue (BrianL): CE jobs evicted, appears to be removals from the factory side UCSD (Mat): Debugging cache server issues reporting to central collector","title":"Support Update"},{"location":"meetings/2022/TechArea20220201/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220201/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220201/#osg-release-team","text":"Ready for Release OSG 3.6 Gratia Probe 2.5.1 Ready for Testing OSG 3.6, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 osg-flock 1.7 OSG 3.6 upcoming HTCondor 9.5.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220201/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220208/","text":"OSG Technology Area Meeting, 8 February 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, Brian Lin, Marco Mambelli, Tim Theisen Announcements \u00b6 BrianL unavailable Wed-Thu, OOO Fri TimT OOO Feb 21-25 Triage Duty \u00b6 This week: Mat Next week: TimT 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 190 +5 Open 29 +1 Selected for Dev 37 +4 In Progress 9 +0 Dev Complete 6 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! AI (Mat): Release stashcp 6.5.3+ AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): add new OSG/GLOW VO DNs to the vo-client Discussion \u00b6 Brian C of the Security Team will be taking over some of Ryan Kiser's projects (e.g. grid scanner) Dennis is working on addressing the GlideinWMS bug where an X.509 credential was still required (but unused) for factory/frontend communication Marco is working on moving GlideinWMS issues from Redmine to GitHub; he will also coordinate GlideinWMS dev attendance at the Operations Frontend admin meeting later this week Support Update \u00b6 UIUC (BrianL) assist Ops with troubleshooting Hosted CE WN client installation OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Release expected this week Ready for Testing OSG 3.5, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 upcoming HTCondor 9.5.0 Discussion \u00b6 Expect a vo-client update this week AI (BrianC): follow-up with Josh Drake on the members of the OSG security mailing list and the process by which members are added/removed","title":"February 8, 2022"},{"location":"meetings/2022/TechArea20220208/#osg-technology-area-meeting-8-february-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, Brian Lin, Marco Mambelli, Tim Theisen","title":"OSG Technology Area Meeting, 8 February 2022"},{"location":"meetings/2022/TechArea20220208/#announcements","text":"BrianL unavailable Wed-Thu, OOO Fri TimT OOO Feb 21-25","title":"Announcements"},{"location":"meetings/2022/TechArea20220208/#triage-duty","text":"This week: Mat Next week: TimT 7 (+0) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220208/#jira-as-of-monday","text":"# of tickets \u0394 State 190 +5 Open 29 +1 Selected for Dev 37 +4 In Progress 9 +0 Dev Complete 6 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220208/#osg-software-team","text":"Kubernetes Hackathon today! AI (Mat): Release stashcp 6.5.3+ AI (Mat): Test cvmfsexec script changes for use at Compute Canada AI (Mat): Move OSPool HPC frontend groups to the new OSPool frontend. AI (TimT): Create a ticket for a student to write a script to run the appropriate regen-repo commands next time. AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): add new OSG/GLOW VO DNs to the vo-client","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220208/#discussion","text":"Brian C of the Security Team will be taking over some of Ryan Kiser's projects (e.g. grid scanner) Dennis is working on addressing the GlideinWMS bug where an X.509 credential was still required (but unused) for factory/frontend communication Marco is working on moving GlideinWMS issues from Redmine to GitHub; he will also coordinate GlideinWMS dev attendance at the Operations Frontend admin meeting later this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220208/#support-update","text":"UIUC (BrianL) assist Ops with troubleshooting Hosted CE WN client installation","title":"Support Update"},{"location":"meetings/2022/TechArea20220208/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220208/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220208/#osg-release-team","text":"Release expected this week Ready for Testing OSG 3.5, 3.6 hosted-ce-tools 0.9 for EL8 OSG 3.5-upcoming, OSG 3.6 HTCondor 9.0.9 scitokens-credmon 0.8.1 for EL8 OSG 3.6 upcoming HTCondor 9.5.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220208/#discussion_2","text":"Expect a vo-client update this week AI (BrianC): follow-up with Josh Drake on the members of the OSG security mailing list and the process by which members are added/removed","title":"Discussion"},{"location":"meetings/2022/TechArea20220222/","text":"OSG Technology Area Meeting, 22 February 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, BrianL, Mat Announcements \u00b6 TimT OOO Feb 21-25 Triage Duty \u00b6 This week: BrianL Next week: Mat 13 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 199 +5 Open 31 +1 Selected for Dev 37 +0 In Progress 14 +3 Dev Complete 4 +2 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): Update osg-configure-bosco dependency and build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): kick off tests for GlideinWMS 3.7.6 and 3.9.4 AI (BrianL): build new osg-scitokens-mapfile AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): address issues with gratia-probe-condor-ap Discussion \u00b6 Additional develoment work is needed to support multi-VO APs, especially with Gratia reporting (probes can only deal with one VO at a time) and figuring out how to map jobs to VOs in a way that the probe can recognize. rpm --verify test in VMU tests does not handle virtual dependencies; it does two things: verify that all listed packages were installed (can be done with a yum flag) verify that files on disk match files in package (has caught at least one error within living memory) Support Update \u00b6 GSU (BrianL): investigate SSH certificate issues JLab (BrianL): troubleshoot missing payload records from APs Lancium (BrianL): investigate HAS_SINGULARITY = False SDSC (Mat): troubleshoot cache/origin authentication OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5-upcoming, OSG 3.6 osg-xrootd OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure) Discussion \u00b6 None this week","title":"February 22, 2022"},{"location":"meetings/2022/TechArea20220222/#osg-technology-area-meeting-22-february-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian Chase, BrianL, Mat","title":"OSG Technology Area Meeting, 22 February 2022"},{"location":"meetings/2022/TechArea20220222/#announcements","text":"TimT OOO Feb 21-25","title":"Announcements"},{"location":"meetings/2022/TechArea20220222/#triage-duty","text":"This week: BrianL Next week: Mat 13 (+6) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220222/#jira-as-of-monday","text":"# of tickets \u0394 State 199 +5 Open 31 +1 Selected for Dev 37 +0 In Progress 14 +3 Dev Complete 4 +2 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220222/#osg-software-team","text":"Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): Update osg-configure-bosco dependency and build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): kick off tests for GlideinWMS 3.7.6 and 3.9.4 AI (BrianL): build new osg-scitokens-mapfile AI (BrianL): add support for manual client registration to osg-token-renewer AI (BrianL): address issues with gratia-probe-condor-ap","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220222/#discussion","text":"Additional develoment work is needed to support multi-VO APs, especially with Gratia reporting (probes can only deal with one VO at a time) and figuring out how to map jobs to VOs in a way that the probe can recognize. rpm --verify test in VMU tests does not handle virtual dependencies; it does two things: verify that all listed packages were installed (can be done with a yum flag) verify that files on disk match files in package (has caught at least one error within living memory)","title":"Discussion"},{"location":"meetings/2022/TechArea20220222/#support-update","text":"GSU (BrianL): investigate SSH certificate issues JLab (BrianL): troubleshoot missing payload records from APs Lancium (BrianL): investigate HAS_SINGULARITY = False SDSC (Mat): troubleshoot cache/origin authentication","title":"Support Update"},{"location":"meetings/2022/TechArea20220222/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220222/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220222/#osg-release-team","text":"Ready for Testing OSG 3.5-upcoming, OSG 3.6 osg-xrootd OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220222/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220301/","text":"OSG Technology Area Meeting, 1 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Tim T Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 18 (+5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 186 -13 Open 41 +10 Selected for Dev 35 -2 In Progress 20 +6 Dev Complete 7 +3 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Doc focus Friday 1-5pm! Full court press on documentation Consolidating container images to https://github.com/opensciencegrid/images/ (SOFTWARE-4944) AI (Mat): build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): address issues with gratia-probe-condor-ap AI (TimT): prepare HTCondor 9.7.0 release candidate in time for Patch Tuesday Discussion \u00b6 osg-token-renewer release is waiting for Dave Dykstra and CILogon developers to diagnose issues between OIDC-Agent and CILogon interactions = We have updated our container retention policy: timestamped containers will be deleted after 6 months or if there are any security issues Support Update \u00b6 BNL (BrianL): issue was caused by missing/outdated CRLs; Brian will review the support ticket and create any necessary JIRA tickets for development work GSU (BrianL): investigate SSH certificate issues; turned out to be an expired cert and a bad target post-jump host Lancium (BrianL): discussed OSG ownership of container deployment; facilitated an introduction with Igor SDSC (Mat): the XrdVoms plugin (used in OSG 3.6) is mapping certificates to a different XRootD identity than LCMAPS was. Mat will investigate if XRootD config changes can solve the issue GlideinWMS (Marco): fixing bug related to cloud submission OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure) Discussion \u00b6 Announce container retention policy update with this week's release","title":"March 1, 2022"},{"location":"meetings/2022/TechArea20220301/#osg-technology-area-meeting-1-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Tim T","title":"OSG Technology Area Meeting, 1 March 2022"},{"location":"meetings/2022/TechArea20220301/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220301/#triage-duty","text":"This week: Mat Next week: TimT 18 (+5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220301/#jira-as-of-monday","text":"# of tickets \u0394 State 186 -13 Open 41 +10 Selected for Dev 35 -2 In Progress 20 +6 Dev Complete 7 +3 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220301/#osg-software-team","text":"Doc focus Friday 1-5pm! Full court press on documentation Consolidating container images to https://github.com/opensciencegrid/images/ (SOFTWARE-4944) AI (Mat): build osg-configure AI (Mat): xcache-reporter packaging issues AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): address issues with gratia-probe-condor-ap AI (TimT): prepare HTCondor 9.7.0 release candidate in time for Patch Tuesday","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220301/#discussion","text":"osg-token-renewer release is waiting for Dave Dykstra and CILogon developers to diagnose issues between OIDC-Agent and CILogon interactions = We have updated our container retention policy: timestamped containers will be deleted after 6 months or if there are any security issues","title":"Discussion"},{"location":"meetings/2022/TechArea20220301/#support-update","text":"BNL (BrianL): issue was caused by missing/outdated CRLs; Brian will review the support ticket and create any necessary JIRA tickets for development work GSU (BrianL): investigate SSH certificate issues; turned out to be an expired cert and a bad target post-jump host Lancium (BrianL): discussed OSG ownership of container deployment; facilitated an introduction with Igor SDSC (Mat): the XrdVoms plugin (used in OSG 3.6) is mapping certificates to a different XRootD identity than LCMAPS was. Mat will investigate if XRootD config changes can solve the issue GlideinWMS (Marco): fixing bug related to cloud submission","title":"Support Update"},{"location":"meetings/2022/TechArea20220301/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220301/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220301/#osg-release-team","text":"Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220301/#discussion_2","text":"Announce container retention policy update with this week's release","title":"Discussion"},{"location":"meetings/2022/TechArea20220308/","text":"OSG Technology Area Meeting, 8 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian C, Brian L, Derek, Marco, Mat, Tim T Announcements \u00b6 OSG All Hands next week! OSG site admin office hours from 3:30-5:30pm Tue Mar 15! Triage Duty \u00b6 This week: TimT Next week: BrianL 13 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 185 -1 Open 40 -1 Selected for Dev 34 -1 In Progress 14 -6 Dev Complete 6 -1 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): xcache-reporter packaging issues AI (TimT): move and update oidc-agent technology doc to main docs area as a \"using tokens\" doc AI (Mat): add token overview for site admins AI (BrianL): add overview of 3.6 token transition AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken Discussion \u00b6 GlideinWMS (Marco): GlideinWMS development has moved to GitHub; there are workflows and the developers are in the process of migrating Redmine tickets. Working on fix for slowdown when launching processes for running RRD commands; Python RRD is the only method which gives acceptable performance but there is no RPM for the dependency. Marco will discuss with OSG Software team how to handle the dependency issue. Support Update \u00b6 BNL (BrianL): Qiulan/Doug say that WebDAV doesn't work for their standalone server Edinburgh (BrianL): help register a cache and sort out Dune data federation details OU (Derek): Issues with tier2-01.ochep.ou.edu gratia, Horst indicated it's an EL6 cluster and he would be in favor of turning it off. SDSC (Mat): Got their cache working by using OSG 3.5; asked Diego/Fabio to upgrade some of our test caches to OSG 3.6 so we can figure out auth issues without breaking his site. OSG DevOps \u00b6 StashCP multi-file download/upload. Secured an \"Open Source\" license for Gitpod which is the Professional level. It's a competitor to Github Codespaces. Remote development. My first thought is that it would be nice for topology development since it's difficult (in my experience) to iterate. Especially initial setup. License is open to all members of the opensciencegrid github organization. Packaging of the shoveler? Packaging of the python-scitokens? Working on OSDF metrics for OSG Meeting. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure) Discussion \u00b6 Announce container retention policy update with this week's release","title":"March 8, 2022"},{"location":"meetings/2022/TechArea20220308/#osg-technology-area-meeting-8-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian C, Brian L, Derek, Marco, Mat, Tim T","title":"OSG Technology Area Meeting, 8 March 2022"},{"location":"meetings/2022/TechArea20220308/#announcements","text":"OSG All Hands next week! OSG site admin office hours from 3:30-5:30pm Tue Mar 15!","title":"Announcements"},{"location":"meetings/2022/TechArea20220308/#triage-duty","text":"This week: TimT Next week: BrianL 13 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220308/#jira-as-of-monday","text":"# of tickets \u0394 State 185 -1 Open 40 -1 Selected for Dev 34 -1 In Progress 14 -6 Dev Complete 6 -1 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220308/#osg-software-team","text":"Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River AI (Mat): xcache-reporter packaging issues AI (TimT): move and update oidc-agent technology doc to main docs area as a \"using tokens\" doc AI (Mat): add token overview for site admins AI (BrianL): add overview of 3.6 token transition AI (Mat): apply voms mapfile patch to OSG's build of XRootD; Justas at Caltech can test AI (BrianL): kick off tests for Vault, htgetttoken","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220308/#discussion","text":"GlideinWMS (Marco): GlideinWMS development has moved to GitHub; there are workflows and the developers are in the process of migrating Redmine tickets. Working on fix for slowdown when launching processes for running RRD commands; Python RRD is the only method which gives acceptable performance but there is no RPM for the dependency. Marco will discuss with OSG Software team how to handle the dependency issue.","title":"Discussion"},{"location":"meetings/2022/TechArea20220308/#support-update","text":"BNL (BrianL): Qiulan/Doug say that WebDAV doesn't work for their standalone server Edinburgh (BrianL): help register a cache and sort out Dune data federation details OU (Derek): Issues with tier2-01.ochep.ou.edu gratia, Horst indicated it's an EL6 cluster and he would be in favor of turning it off. SDSC (Mat): Got their cache working by using OSG 3.5; asked Diego/Fabio to upgrade some of our test caches to OSG 3.6 so we can figure out auth issues without breaking his site.","title":"Support Update"},{"location":"meetings/2022/TechArea20220308/#osg-devops","text":"StashCP multi-file download/upload. Secured an \"Open Source\" license for Gitpod which is the Professional level. It's a competitor to Github Codespaces. Remote development. My first thought is that it would be nice for topology development since it's difficult (in my experience) to iterate. Especially initial setup. License is open to all members of the opensciencegrid github organization. Packaging of the shoveler? Packaging of the python-scitokens? Working on OSDF metrics for OSG Meeting.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220308/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220308/#osg-release-team","text":"Ready for Testing OSG 3.5, OSG 3.6 osg-scitokens-mapfile 6 OSG 3.5-upcoming, OSG 3.6 XRootD 5.4.1 osg-xrootd OSG 3.6 GlideinWMS 3.9.4 Ready for Release OSG 3.6 upcoming HTCondor 9.5.0 (blocked by osg-configure)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220308/#discussion_2","text":"Announce container retention policy update with this week's release","title":"Discussion"},{"location":"meetings/2022/TechArea20220322/","text":"OSG Technology Area Meeting, 22 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T Announcements \u00b6 BrianB out this week Triage Duty \u00b6 This week: Mat Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 183 +1 Open 42 +1 Selected for Dev 29 -4 In Progress 14 -2 Dev Complete 14 +2 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River Set up Dex for Tiger Clean up PATh facility backfill containers AI (Mat): xcache-reporter packaging issues AI (Mat): Build wn-client tarballs from 3.5-upcoming AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): release osg-ce with OSG_SERIES schedd attr Discussion \u00b6 Marco: Implementing features started in last week's GlideinWMS Hackathon, including a plugin interface for SciTokens/WLCG Tokens. HTCondor Week registration is open, looking for speakers. Marco has several ideas for talks that Fermi or GlideinWMS folks can give; Brian will pass them on to the HTCSS dev team. Derek reports that HTCondor file transfer output plugins are hard to debug, primarily due to lack of output upon failures. HTCondor 9.7.0 has improvements in this department; Derek will verify and send suggestions for further improvements to the HTCSS devs. Support Update \u00b6 Edinburgh (BrianL): registered their cache OSG DevOps \u00b6 StashCP multi-file download/upload and improvement of HTCondor file transfer. Packaging of the shoveler is ongoing. Update the OSDF metrics gathering, working with Fabio Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.6-upcoming: HTCondor 9.7.0: New feature release OSG 3.6 XRootD 5.4.2-1.1: OSG patches added HTCondor 9.0.11: Bug fix release python-scitokens 1.7.0 osg-token-renewer 0.8.1 xrootd-monitoring-shoveler 1.0.0 stashcp 6.5.0 OSG 3.5-upcoming XRootD 5.4.2 HTCondor 9.0.11: Bug fix release GlideWMS 3.7.6 gfal2 2.20.3: Update to resolve installation issues on 3.5-upcoming OSG 3.5 HTCondor 8.8.17: Bug fix release scitokens-cpp 0.7.0 python-scitokens 1.7.0 osg-token-renewer 0.8.1 Ready for Release Nothing yet Discussion \u00b6 Announce container retention policy update with this week's release","title":"March 22, 2022"},{"location":"meetings/2022/TechArea20220322/#osg-technology-area-meeting-22-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Derek, Marco Mambelli, Mat, Tim T","title":"OSG Technology Area Meeting, 22 March 2022"},{"location":"meetings/2022/TechArea20220322/#announcements","text":"BrianB out this week","title":"Announcements"},{"location":"meetings/2022/TechArea20220322/#triage-duty","text":"This week: Mat Next week: TimT 15 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220322/#jira-as-of-monday","text":"# of tickets \u0394 State 183 +1 Open 42 +1 Selected for Dev 29 -4 In Progress 14 -2 Dev Complete 14 +2 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220322/#osg-software-team","text":"Kubernetes Hackathon today! Potential projects: Add Prometheus monitoring for the Postgresql node Set up a secondary CHTC (GLOW) frontend on River Set up Dex for Tiger Clean up PATh facility backfill containers AI (Mat): xcache-reporter packaging issues AI (Mat): Build wn-client tarballs from 3.5-upcoming AI (BrianL): kick off tests for Vault, htgetttoken AI (BrianL): release osg-ce with OSG_SERIES schedd attr","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220322/#discussion","text":"Marco: Implementing features started in last week's GlideinWMS Hackathon, including a plugin interface for SciTokens/WLCG Tokens. HTCondor Week registration is open, looking for speakers. Marco has several ideas for talks that Fermi or GlideinWMS folks can give; Brian will pass them on to the HTCSS dev team. Derek reports that HTCondor file transfer output plugins are hard to debug, primarily due to lack of output upon failures. HTCondor 9.7.0 has improvements in this department; Derek will verify and send suggestions for further improvements to the HTCSS devs.","title":"Discussion"},{"location":"meetings/2022/TechArea20220322/#support-update","text":"Edinburgh (BrianL): registered their cache","title":"Support Update"},{"location":"meetings/2022/TechArea20220322/#osg-devops","text":"StashCP multi-file download/upload and improvement of HTCondor file transfer. Packaging of the shoveler is ongoing. Update the OSDF metrics gathering, working with Fabio","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220322/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220322/#osg-release-team","text":"Ready for Testing OSG 3.6-upcoming: HTCondor 9.7.0: New feature release OSG 3.6 XRootD 5.4.2-1.1: OSG patches added HTCondor 9.0.11: Bug fix release python-scitokens 1.7.0 osg-token-renewer 0.8.1 xrootd-monitoring-shoveler 1.0.0 stashcp 6.5.0 OSG 3.5-upcoming XRootD 5.4.2 HTCondor 9.0.11: Bug fix release GlideWMS 3.7.6 gfal2 2.20.3: Update to resolve installation issues on 3.5-upcoming OSG 3.5 HTCondor 8.8.17: Bug fix release scitokens-cpp 0.7.0 python-scitokens 1.7.0 osg-token-renewer 0.8.1 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220322/#discussion_2","text":"Announce container retention policy update with this week's release","title":"Discussion"},{"location":"meetings/2022/TechArea20220329/","text":"OSG Technology Area Meeting, 29 March 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Marco Mambelli, Mat Announcements \u00b6 TimT out next week Triage Duty \u00b6 This week: TimT Next week: BrianL 18 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 179 -4 Open 42 +0 Selected for Dev 29 +0 In Progress 14 +0 Dev Complete 5 -9 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus friday AI (Mat): Release osg-scitokens-mapfile-7 with HCC token mapping AI (Mat): kick off VMU tests for cigetcert AI (BrianL): release osg-ce with OSG_SERIES schedd attr AI (BrianL): python3-rrdtool for EL7 Discussion \u00b6 GlideinWMS 3.7.7 in progress; working on putting the token from the HTCondor-CE collector in the correct location. GlideinWMS 3.9.5 ETA ~3 weeks, including the scitoken credential plugin interface Support Update \u00b6 UNL (BrianL, Derek): helped troubleshoot WholeNodeJob and accounting issues Marco: Trying to use condor_config_val -dump as part of config generation, but condor_config_val does not show where multi-line values end; this has been reported upstream. OSG DevOps \u00b6 No updates this week Discussion \u00b6 None this week OSG Release Team \u00b6 No updates this week Discussion \u00b6 None this week","title":"March 29, 2022"},{"location":"meetings/2022/TechArea20220329/#osg-technology-area-meeting-29-march-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Brian L, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 29 March 2022"},{"location":"meetings/2022/TechArea20220329/#announcements","text":"TimT out next week","title":"Announcements"},{"location":"meetings/2022/TechArea20220329/#triage-duty","text":"This week: TimT Next week: BrianL 18 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220329/#jira-as-of-monday","text":"# of tickets \u0394 State 179 -4 Open 42 +0 Selected for Dev 29 +0 In Progress 14 +0 Dev Complete 5 -9 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220329/#osg-software-team","text":"Doc focus friday AI (Mat): Release osg-scitokens-mapfile-7 with HCC token mapping AI (Mat): kick off VMU tests for cigetcert AI (BrianL): release osg-ce with OSG_SERIES schedd attr AI (BrianL): python3-rrdtool for EL7","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220329/#discussion","text":"GlideinWMS 3.7.7 in progress; working on putting the token from the HTCondor-CE collector in the correct location. GlideinWMS 3.9.5 ETA ~3 weeks, including the scitoken credential plugin interface","title":"Discussion"},{"location":"meetings/2022/TechArea20220329/#support-update","text":"UNL (BrianL, Derek): helped troubleshoot WholeNodeJob and accounting issues Marco: Trying to use condor_config_val -dump as part of config generation, but condor_config_val does not show where multi-line values end; this has been reported upstream.","title":"Support Update"},{"location":"meetings/2022/TechArea20220329/#osg-devops","text":"No updates this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220329/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220329/#osg-release-team","text":"No updates this week","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220329/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220405/","text":"OSG Technology Area Meeting, 5 April 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat Announcements \u00b6 TimT OOO this week BrianL largely unavailable next week due to ITLP workshop Mat OOO Apr 15-29 Next week's meeting canceled Triage Duty \u00b6 This week: BrianL Next week: Mat 16 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 182 +3 Open 40 -2 Selected for Dev 30 +1 In Progress 13 -1 Dev Complete 9 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today: Dex for Tiger Update CHTC cache/origin Upgrade production GLOW frontend AI (Mat): increase default key size in renew proxy (SOFTWARE-5112) AI (Mat): document xcache (and xrootd?) upgrade to 3.6 (SOFTWARE-5109) AI (BrianL): python3-rrdtool for EL7 (SOFTWARE-5080) AI (BrianL): update VOMS clients default proxy key bit length to 2048 bits (SOFTWARE-4889) Discussion \u00b6 Marco: adding small requested changes to 3.7.7; 3.9.5 in progress, including the code to generate scitokens and wlcg tokens using an external script BrianB ran into an issue with an expired GLOW proxy causing a failure at the factory, even though token auth was enabled; he will send Marco the configuration that caused it CMS is still sending 1024-bit proxies which no longer work on EL 8. We need to find out where their proxies are generated and ask them to upgrade. EL 8 can be configured to accept 1024-bit proxies again, but this makes sites less secure so we do not want to recommend it New security release of Go upcoming; no details on the issue yet, but we may need to rebuild our software if it's affected CMS has requested that we build worker node images using Alma Linux, because they have not validated CentOS Stream 8. (WLCG sites in general have been avoiding Stream 8 because it goes EOL in the middle of Run 3.) OS SW does not currently test Alma but that would not be too difficult to add Support Update \u00b6 OSG Connect (BrianL): help with AP update to OSG 3.6 UNL (Derek): Correct whole node GRACC accounting UNL (Derek): help with GRACC records issues. Since UNL is running OSG 3.5 for now, they can use the condor batch system probe CRIC (Mat): with BrianB's help found a Topology issue that was causing SSL errors for CRIC, caused by CentOS Stream 8 dropping a needed package from their default container image OSG DevOps \u00b6 Go update is coming thursday, will be watching for possible impact on OSG things. Security team is notified. Working on shoveler docs https://github.com/opensciencegrid/docs/pull/959 Discussion \u00b6 None this week OSG Release Team \u00b6 No updates this week Discussion \u00b6 None this week","title":"April 5, 2022"},{"location":"meetings/2022/TechArea20220405/#osg-technology-area-meeting-5-april-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Derek, Marco Mambelli, Mat","title":"OSG Technology Area Meeting, 5 April 2022"},{"location":"meetings/2022/TechArea20220405/#announcements","text":"TimT OOO this week BrianL largely unavailable next week due to ITLP workshop Mat OOO Apr 15-29 Next week's meeting canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220405/#triage-duty","text":"This week: BrianL Next week: Mat 16 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220405/#jira-as-of-monday","text":"# of tickets \u0394 State 182 +3 Open 40 -2 Selected for Dev 30 +1 In Progress 13 -1 Dev Complete 9 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220405/#osg-software-team","text":"Kubernetes hackathon today: Dex for Tiger Update CHTC cache/origin Upgrade production GLOW frontend AI (Mat): increase default key size in renew proxy (SOFTWARE-5112) AI (Mat): document xcache (and xrootd?) upgrade to 3.6 (SOFTWARE-5109) AI (BrianL): python3-rrdtool for EL7 (SOFTWARE-5080) AI (BrianL): update VOMS clients default proxy key bit length to 2048 bits (SOFTWARE-4889)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220405/#discussion","text":"Marco: adding small requested changes to 3.7.7; 3.9.5 in progress, including the code to generate scitokens and wlcg tokens using an external script BrianB ran into an issue with an expired GLOW proxy causing a failure at the factory, even though token auth was enabled; he will send Marco the configuration that caused it CMS is still sending 1024-bit proxies which no longer work on EL 8. We need to find out where their proxies are generated and ask them to upgrade. EL 8 can be configured to accept 1024-bit proxies again, but this makes sites less secure so we do not want to recommend it New security release of Go upcoming; no details on the issue yet, but we may need to rebuild our software if it's affected CMS has requested that we build worker node images using Alma Linux, because they have not validated CentOS Stream 8. (WLCG sites in general have been avoiding Stream 8 because it goes EOL in the middle of Run 3.) OS SW does not currently test Alma but that would not be too difficult to add","title":"Discussion"},{"location":"meetings/2022/TechArea20220405/#support-update","text":"OSG Connect (BrianL): help with AP update to OSG 3.6 UNL (Derek): Correct whole node GRACC accounting UNL (Derek): help with GRACC records issues. Since UNL is running OSG 3.5 for now, they can use the condor batch system probe CRIC (Mat): with BrianB's help found a Topology issue that was causing SSL errors for CRIC, caused by CentOS Stream 8 dropping a needed package from their default container image","title":"Support Update"},{"location":"meetings/2022/TechArea20220405/#osg-devops","text":"Go update is coming thursday, will be watching for possible impact on OSG things. Security team is notified. Working on shoveler docs https://github.com/opensciencegrid/docs/pull/959","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220405/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220405/#osg-release-team","text":"No updates this week","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220405/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220419/","text":"OSG Technology Area Meeting, 19 April 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, TimT Announcements \u00b6 Mat OOO Apr 15-29 Carl OOO Apr 21-25 BrianL OOO Apr 28-29 Triage Duty \u00b6 This week: TimT Next week: BrianL 13 (-3) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 185 +4 Open 3 -6 Selected for Dev 29 +0 In Progress 20 +6 Dev Complete 14 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today: investigate condor failing to start in backfill containers Primary MkDocs repositories being moved to the osg-htc GitHub organization FNAL reports an issue with osg-pki-tools that needs to be addressed in OSG 3.6. Should have a fix by early next week. AI (BrianL): add release series tags for backfill containers and merge new tagging policy Discussion \u00b6 GlideinWMS: Working on RCs, including a fix for communication issues between 3.9 frontends to a 3.7 factory Software team will apply a packaging patch to fix an issue with EL7 GlideinWMS installations in case the RC isn't ready for Operations in time Decision Engine 2.0 RC is coming soon; Marco will provide regular updates from the GIL investigation Support Update \u00b6 BNL (BrianL): investigating an issue with write auth failures using the xroot protocol OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.6 CVMFS 2.9.2 cigetcert 1.20 osg-ce 3.6-5 vault 1.10, htvault-config 1.12, htgettoken 1.11 osg-xrootd 3.6-16 (stash-cache crash with VOMS) VOMS default proxy key length OSG 3.6, OSG 3.5-upcoming HTCondor-CE 5.1.4 xcache 2.2.0, xcache 3.0.0 OSG 3.5-upcoming osg-xrootd Ready for Release Nothing yet Discussion \u00b6 3.5 to 3.6 minefield upgrade failures with HTCondor-CE due to our packaging of rrdtool","title":"April 19, 2022"},{"location":"meetings/2022/TechArea20220419/#osg-technology-area-meeting-19-april-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 19 April 2022"},{"location":"meetings/2022/TechArea20220419/#announcements","text":"Mat OOO Apr 15-29 Carl OOO Apr 21-25 BrianL OOO Apr 28-29","title":"Announcements"},{"location":"meetings/2022/TechArea20220419/#triage-duty","text":"This week: TimT Next week: BrianL 13 (-3) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220419/#jira-as-of-monday","text":"# of tickets \u0394 State 185 +4 Open 3 -6 Selected for Dev 29 +0 In Progress 20 +6 Dev Complete 14 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220419/#osg-software-team","text":"Kubernetes hackathon today: investigate condor failing to start in backfill containers Primary MkDocs repositories being moved to the osg-htc GitHub organization FNAL reports an issue with osg-pki-tools that needs to be addressed in OSG 3.6. Should have a fix by early next week. AI (BrianL): add release series tags for backfill containers and merge new tagging policy","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220419/#discussion","text":"GlideinWMS: Working on RCs, including a fix for communication issues between 3.9 frontends to a 3.7 factory Software team will apply a packaging patch to fix an issue with EL7 GlideinWMS installations in case the RC isn't ready for Operations in time Decision Engine 2.0 RC is coming soon; Marco will provide regular updates from the GIL investigation","title":"Discussion"},{"location":"meetings/2022/TechArea20220419/#support-update","text":"BNL (BrianL): investigating an issue with write auth failures using the xroot protocol","title":"Support Update"},{"location":"meetings/2022/TechArea20220419/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220419/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220419/#osg-release-team","text":"Ready for Testing OSG 3.6 CVMFS 2.9.2 cigetcert 1.20 osg-ce 3.6-5 vault 1.10, htvault-config 1.12, htgettoken 1.11 osg-xrootd 3.6-16 (stash-cache crash with VOMS) VOMS default proxy key length OSG 3.6, OSG 3.5-upcoming HTCondor-CE 5.1.4 xcache 2.2.0, xcache 3.0.0 OSG 3.5-upcoming osg-xrootd Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220419/#discussion_2","text":"3.5 to 3.6 minefield upgrade failures with HTCondor-CE due to our packaging of rrdtool","title":"Discussion"},{"location":"meetings/2022/TechArea20220426/","text":"OSG Technology Area Meeting, 26 April 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: Announcements \u00b6 Mat OOO Apr 15-29 BrianL OOO Apr 28-29 Triage Duty \u00b6 This week: Carl Next week: BrianL 13 (+0) open FreshDesk tickets 2 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs Factory host cert expires on Apr 28; central collector host cert expires on May 6 OSG 3.5 EOL at the end of the week! Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5 Discussion \u00b6 None this week Support Update \u00b6 None this week OSG DevOps \u00b6 None this week Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Release OSG 3.5 and OSG 3.6 CA Certificates based on IGTF 1.116 OSG 3.6 CVMFS 2.9.2: Bug fix release cigetgert 1.20: works better with CILogon's AWS infrastructure osg-ce 3.6-5 Add OSG_SERIES = 3.6 as a schedd attribute Remove default BATCH_GAHP configuration now provided by upstream osg-xrootd 3.6-16 Fix stash-cache: enabling VOMS causes unauth cache to crash vault 1.10, htvault 1.12 htgettoken 1.11 VOMS 2: Update default proxy certificate key length to 2048 bits Upcoming: HTCondor 9.8.1 Support for Heterogeneous GPUs, some configuration required Allow HTCondor to utilize grid sites requiring multi-factor authentication Technology preview: bring your own resources from HPC clusters Fix HTCondor startup failure with certain complex network configurations Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS Discussion \u00b6 None this week","title":"April 26, 2022"},{"location":"meetings/2022/TechArea20220426/#osg-technology-area-meeting-26-april-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending:","title":"OSG Technology Area Meeting, 26 April 2022"},{"location":"meetings/2022/TechArea20220426/#announcements","text":"Mat OOO Apr 15-29 BrianL OOO Apr 28-29","title":"Announcements"},{"location":"meetings/2022/TechArea20220426/#triage-duty","text":"This week: Carl Next week: BrianL 13 (+0) open FreshDesk tickets 2 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220426/#jira-as-of-monday","text":"# of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220426/#osg-software-team","text":"Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs Factory host cert expires on Apr 28; central collector host cert expires on May 6 OSG 3.5 EOL at the end of the week! Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220426/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220426/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20220426/#osg-devops","text":"None this week","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220426/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220426/#osg-release-team","text":"Ready for Release OSG 3.5 and OSG 3.6 CA Certificates based on IGTF 1.116 OSG 3.6 CVMFS 2.9.2: Bug fix release cigetgert 1.20: works better with CILogon's AWS infrastructure osg-ce 3.6-5 Add OSG_SERIES = 3.6 as a schedd attribute Remove default BATCH_GAHP configuration now provided by upstream osg-xrootd 3.6-16 Fix stash-cache: enabling VOMS causes unauth cache to crash vault 1.10, htvault 1.12 htgettoken 1.11 VOMS 2: Update default proxy certificate key length to 2048 bits Upcoming: HTCondor 9.8.1 Support for Heterogeneous GPUs, some configuration required Allow HTCondor to utilize grid sites requiring multi-factor authentication Technology preview: bring your own resources from HPC clusters Fix HTCondor startup failure with certain complex network configurations Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220426/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220503/","text":"OSG Technology Area Meeting, 3 May 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT Announcements \u00b6 OSG 3.5 EOL! Doc focus this Friday, primarily concentrated on removing old OSG 3.5 documentation. Triage Duty \u00b6 This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 1 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today! AI (Carl): Make CronJob for fixing up user GIDs in COManage. AI (Mat): Investigate auto-update failures in the PATh facility Kubernetes pool. AI (BrianL): Move FE cert-manager patches to base AI (BrianL): Investigate upgrade path from Flux v1 to Flux v2 Doc focus this Friday Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs AI (BrianL): Work with JeffD to debug site failures starting after OSG 3.6 upgrades. AI (BrianL): Respond to Scott Koranda regarding missing EPPNs in COManage. AI (Carl): Remove certinfo usage from Gratia. AI (Mat): Renew central collector host cert (which expires on May 6); UNL SANs are no longer necessary. AI (Mat): Register PATh Facility Execute Points in Topology. AI (TimT): Test HTCondor 9.9.0 in CHTC; new remote management features might impact glideins so those will need extra testing. Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5 Allow for custom workflows in opensciencegrid/images Discussion \u00b6 Added a \"contrib\" directory to the opensciencegrid/images repo so people can contribute images; the first contributor was FNAL with some FTS images. There is a danger of the GitHub Actions for the repo taking too long; the Software Team will investigate fixes as necessary. Support Update \u00b6 BNL (Derek): Debugging various randomly occurring slow or failing transfers with XRootD-Standalone GRACC (Derek): Debugging CEs that have stopped reporting to GRACC after upgrading to OSG 3.6; will stay in touch with the Software Team regarding necessary software/packaging/documentation fixes resulting from these. GIL (Carl): Debug Igor's issue with viewing Topology resources using his COManage credentials. OSG DevOps \u00b6 A few feature requests / bug fixes for StashCP. Still helping shoveler support for token auto-updating. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS Discussion \u00b6 None this week","title":"May 3, 2022"},{"location":"meetings/2022/TechArea20220503/#osg-technology-area-meeting-3-may-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge.webex.com/webappng/sites/morgridge/meeting/info/791d9dddc5464eb6a73fc7746331d06c (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 3 May 2022"},{"location":"meetings/2022/TechArea20220503/#announcements","text":"OSG 3.5 EOL! Doc focus this Friday, primarily concentrated on removing old OSG 3.5 documentation.","title":"Announcements"},{"location":"meetings/2022/TechArea20220503/#triage-duty","text":"This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 1 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220503/#jira-as-of-monday","text":"# of tickets \u0394 State 184 -1 Open 30 -3 Selected for Dev 29 +0 In Progress 15 -5 Dev Complete 24 +10 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220503/#osg-software-team","text":"Kubernetes Hackathon today! AI (Carl): Make CronJob for fixing up user GIDs in COManage. AI (Mat): Investigate auto-update failures in the PATh facility Kubernetes pool. AI (BrianL): Move FE cert-manager patches to base AI (BrianL): Investigate upgrade path from Flux v1 to Flux v2 Doc focus this Friday Primary MkDocs repositories being moved to the osg-htc GitHub organization. Technology first, then docs AI (BrianL): Work with JeffD to debug site failures starting after OSG 3.6 upgrades. AI (BrianL): Respond to Scott Koranda regarding missing EPPNs in COManage. AI (Carl): Remove certinfo usage from Gratia. AI (Mat): Renew central collector host cert (which expires on May 6); UNL SANs are no longer necessary. AI (Mat): Register PATh Facility Execute Points in Topology. AI (TimT): Test HTCondor 9.9.0 in CHTC; new remote management features might impact glideins so those will need extra testing. Next projects: Transition contacts to COManage Finish sending OSPool StartD logs to the GRACC Streamline deployments of OSDF caches and origins Retire OSG 3.5 Allow for custom workflows in opensciencegrid/images","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220503/#discussion","text":"Added a \"contrib\" directory to the opensciencegrid/images repo so people can contribute images; the first contributor was FNAL with some FTS images. There is a danger of the GitHub Actions for the repo taking too long; the Software Team will investigate fixes as necessary.","title":"Discussion"},{"location":"meetings/2022/TechArea20220503/#support-update","text":"BNL (Derek): Debugging various randomly occurring slow or failing transfers with XRootD-Standalone GRACC (Derek): Debugging CEs that have stopped reporting to GRACC after upgrading to OSG 3.6; will stay in touch with the Software Team regarding necessary software/packaging/documentation fixes resulting from these. GIL (Carl): Debug Igor's issue with viewing Topology resources using his COManage credentials.","title":"Support Update"},{"location":"meetings/2022/TechArea20220503/#osg-devops","text":"A few feature requests / bug fixes for StashCP. Still helping shoveler support for token auto-updating.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220503/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220503/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.4-3: Fix rrdtool dependencies gratia-probe 2.5.2 Remove pre-routed jobs instead of quarantining them always set MapUnknownToGroup HTCondor 9.0.12: Bug fix release HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade XCache 3.0.1 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged osg-flock 1.8 Remove MapUnknownToGroup and MapGroupToRole from osg-flock Advertise osg-flock version in the osg-flock RPM rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220503/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220510/","text":"OSG Technology Area Meeting, 10 May 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL OOO next week HTCondor week May 23 - 26 Next two meetings canceled Triage Duty \u00b6 This week: Mat Next week: TimT 13 (-3) open FreshDesk tickets 2 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 192 +5 Open 27 -2 Selected for Dev 34 +6 In Progress 17 +1 Dev Complete 9 -7 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 3.6 AI (Carl) remove certinfo log messages AI (Mat) XRootD 5.4.3 RC1 Next week: AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing Discussion \u00b6 GlideinWMS stakeholders meeting tomorrow; 3.9.3 release planned. Support Update \u00b6 ComputeCanada (BrianL): troubleshoot missing OSG_WN_TMP due to HTCondor change from GLITE_LOCATION to BLAHPD_LOCATION in HTCondor 9.3.0 Carl: Continue to assist Igor with authentication issues. Mats can give him a manually generated token to keep things moving along. ODU (Mat): Investigate failure to launch Singularity from CVMFS. UTC-EPYC (Mat): Investigate random job failures; request assistance from HTCondor developers. JLab (Mat): Setting up a cache and an origin; they are planning on having both on one host (in containers) and using the same cert. This will cause accounting issues (the StashCache graphs are keyed by hostname) but the other central XRootD services should handle it properly. OSG DevOps \u00b6 A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing OSG 3.6 WN client: Fix missing packages in tarball HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2 Discussion \u00b6 None this week","title":"May 10, 2022"},{"location":"meetings/2022/TechArea20220510/#osg-technology-area-meeting-10-may-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 10 May 2022"},{"location":"meetings/2022/TechArea20220510/#announcements","text":"BrianL OOO next week HTCondor week May 23 - 26 Next two meetings canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220510/#triage-duty","text":"This week: Mat Next week: TimT 13 (-3) open FreshDesk tickets 2 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220510/#jira-as-of-monday","text":"# of tickets \u0394 State 192 +5 Open 27 -2 Selected for Dev 34 +6 In Progress 17 +1 Dev Complete 9 -7 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220510/#osg-software-team","text":"OSG 3.6 AI (Carl) remove certinfo log messages AI (Mat) XRootD 5.4.3 RC1 Next week: AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220510/#discussion","text":"GlideinWMS stakeholders meeting tomorrow; 3.9.3 release planned.","title":"Discussion"},{"location":"meetings/2022/TechArea20220510/#support-update","text":"ComputeCanada (BrianL): troubleshoot missing OSG_WN_TMP due to HTCondor change from GLITE_LOCATION to BLAHPD_LOCATION in HTCondor 9.3.0 Carl: Continue to assist Igor with authentication issues. Mats can give him a manually generated token to keep things moving along. ODU (Mat): Investigate failure to launch Singularity from CVMFS. UTC-EPYC (Mat): Investigate random job failures; request assistance from HTCondor developers. JLab (Mat): Setting up a cache and an origin; they are planning on having both on one host (in containers) and using the same cert. This will cause accounting issues (the StashCache graphs are keyed by hostname) but the other central XRootD services should handle it properly.","title":"Support Update"},{"location":"meetings/2022/TechArea20220510/#osg-devops","text":"A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220510/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220510/#osg-release-team","text":"Ready for Testing OSG 3.6 WN client: Fix missing packages in tarball HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220510/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220531/","text":"OSG Technology Area Meeting, 31 May 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Ziyang, our new IRIS-HEP fellow, has joined. He will be working on network monitoring for XCache container deployments Triage Duty \u00b6 This week: Carl Next week: Mat 15 (+2) open FreshDesk tickets 1 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 190 +0 Open 31 -1 Selected for Dev 24 +0 In Progress 17 +1 Dev Complete 25 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon Mat: Autoupdates for Flux v2 on PATh Facility; can be tested on the backfill pilots since they are old. Mat: Fix backfill pilots and other broken pods on Tiger. Mat: Assist Cannon in debugging Topology on Tiger. BrianL: Test HTCondor-CE 5.1.4 by upgrading the Canary CE(s). BrianL: Deploy Dex. Some UW CSL-hosted services have had their certs expire. vdt.cs.wisc.edu (used for Koji) was migrated today. AI (TimT): Release 9.9.0 release candidate of HTCondor in the Open Pool. Planning to deprecate old interfaces before the start of the next LTS series. BrianB diagnosed shared port issues with 9.8.0 on the APs that he worked around by disabling IPv6. 9.9.0 should fix it. Tim will let Brian know once the upgrade is done, so Brian can re-enable IPv6. AI (Mat) Create new Topology endpoints for improved OSDF support. AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing Discussion \u00b6 None this week Support Update \u00b6 JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utilization from the Slurm side Carl: Requests assistance on unregistered pilot container Gratia probes. UTC-Epyc (Mat): Requests assistance for diagnosing random pilot deaths. Because rsyslog is broken on the site, we do not have pilot logs for the failed pilots. OSG DevOps \u00b6 A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map. Discussion \u00b6 None this week OSG Release Team \u00b6 Ready for Testing gratia-probe 2.6.1 Replace AuthToken* references with routed job attributes Fix mismatched type concatenation in Gratia record send Gratia: Set SCHEDD_CRON_LOG_NON_ZERO_EXIT = True in the htcondor-ce configuration Remove certinfo file log messages HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2 htvault-config-1.13 htgettoken 1.12 XCache 3.1.0 stashcp 6.7.5 HTCondor 9.0.13 Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations Upcoming HTCondor 9.9.0 A new authentication method for remote HTCondor administration Several changes to improve the security of connections Fix issue where DAGMan direct submission failed when using Kerberos The submission method is now recorded in the job ClassAd Singularity jobs can now pull from Docker style repositories The OWNER authorization level has been folded into the ADMINISTRATOR level Discussion \u00b6 None this week","title":"May 31, 2022"},{"location":"meetings/2022/TechArea20220531/#osg-technology-area-meeting-31-may-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 31 May 2022"},{"location":"meetings/2022/TechArea20220531/#announcements","text":"Ziyang, our new IRIS-HEP fellow, has joined. He will be working on network monitoring for XCache container deployments","title":"Announcements"},{"location":"meetings/2022/TechArea20220531/#triage-duty","text":"This week: Carl Next week: Mat 15 (+2) open FreshDesk tickets 1 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220531/#jira-as-of-monday","text":"# of tickets \u0394 State 190 +0 Open 31 -1 Selected for Dev 24 +0 In Progress 17 +1 Dev Complete 25 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220531/#osg-software-team","text":"Kubernetes Hackathon Mat: Autoupdates for Flux v2 on PATh Facility; can be tested on the backfill pilots since they are old. Mat: Fix backfill pilots and other broken pods on Tiger. Mat: Assist Cannon in debugging Topology on Tiger. BrianL: Test HTCondor-CE 5.1.4 by upgrading the Canary CE(s). BrianL: Deploy Dex. Some UW CSL-hosted services have had their certs expire. vdt.cs.wisc.edu (used for Koji) was migrated today. AI (TimT): Release 9.9.0 release candidate of HTCondor in the Open Pool. Planning to deprecate old interfaces before the start of the next LTS series. BrianB diagnosed shared port issues with 9.8.0 on the APs that he worked around by disabling IPv6. 9.9.0 should fix it. Tim will let Brian know once the upgrade is done, so Brian can re-enable IPv6. AI (Mat) Create new Topology endpoints for improved OSDF support. AI (Mat) Streamlining OSDF service deployment: add Topology endpoint returning a list of OSDF caches for a given path AI (Carl) Topology COManage transition: pull contact db into COManage contact results where missing","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220531/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220531/#support-update","text":"JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utilization from the Slurm side Carl: Requests assistance on unregistered pilot container Gratia probes. UTC-Epyc (Mat): Requests assistance for diagnosing random pilot deaths. Because rsyslog is broken on the site, we do not have pilot logs for the failed pilots.","title":"Support Update"},{"location":"meetings/2022/TechArea20220531/#osg-devops","text":"A few feature requests / bug fixes for StashCP. One of them ready for pull request: https://github.com/opensciencegrid/stashcp/pull/41 Shoveler auto-update is working great! Increased token lifetime on lightweight issuer to 1 hour. Did a large pull request for GP-ARGO. Wondering if we should include the Site Name in the OSG map? Currently, we show Facility Name, Resource Group, and Resource names. But we don't show the site level in the map.","title":"OSG DevOps"},{"location":"meetings/2022/TechArea20220531/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220531/#osg-release-team","text":"Ready for Testing gratia-probe 2.6.1 Replace AuthToken* references with routed job attributes Fix mismatched type concatenation in Gratia record send Gratia: Set SCHEDD_CRON_LOG_NON_ZERO_EXIT = True in the htcondor-ce configuration Remove certinfo file log messages HTCondor-CE 5.1.4 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Fix rrdtool dependencies to ease OSG 3.5 to 3.6 upgrade GlideinWMS 3.9.4-3: Fix rrdtool dependencies rrdtool 1.8.0-1.2-el7: make Python RRDtools available to GlideinWMS xrootd-multiuser 2.0.4 osg-token-renewer 0.8.2 htvault-config-1.13 htgettoken 1.12 XCache 3.1.0 stashcp 6.7.5 HTCondor 9.0.13 Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations Upcoming HTCondor 9.9.0 A new authentication method for remote HTCondor administration Several changes to improve the security of connections Fix issue where DAGMan direct submission failed when using Kerberos The submission method is now recorded in the job ClassAd Singularity jobs can now pull from Docker style repositories The OWNER authorization level has been folded into the ADMINISTRATOR level","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220531/#discussion_2","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220607/","text":"OSG Technology Area Meeting, 7 June 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Ziyang Announcements \u00b6 Mat OOO Jun 13 BrianL traveling Jun 13-16, OOO Jun 17 Next week's meeting canceled Triage Duty \u00b6 This week: Mat Next week: TimT 11 (-4) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +1 Open 32 +1 Selected for Dev 27 +3 In Progress 14 -3 Dev Complete 28 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus Friday afternoon JLab FE and VO certs expire next Thursday, Ops may need a reminder to update the certs next week BNL will be submitting EIC jobs via Harvester and will pass along a subject DN that we need added to the vo-client Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): backfill container should shut down upon HTCondor exit (SOFTWARE-4608) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) AI (Carl): remove duplicate contact entries in the Topology contact pages (SOFTWARE-5214) Discussion \u00b6 There are several Docker images that are built from individual GitHub repositories instead of the central \"images\" repository. They should be moved to the images repo; keep an eye on how well GitHub Actions workflows scale, though. COManage registration denials seem to be sticky; if you want to admit someone you have previously denied, you will have to expunge the CO Person record Support Update \u00b6 JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. They will lift the blacklisting of ScotsGrid to try to gather more info Belle II (BrianL): will be having a meeting this week to discuss token-based pilot submission Texas Tech (BrianL): new backfill container site, working on fixing COManage registrations WeNMR (BrianL): helping DIRAC developers test token-based pilot submission BNL (Mat): Experiencing CA failures with XRootD TPC. Their CA certificates look fine; Mat has requested that they perform some manual tests to try and isolate the error. The XRootD developers are Cc'ed on the ticket and can provide debugging assistance. OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.5 gratia-probe 2.6.1 Log schedd cron errors with newer versions of HTCondor Replace AuthToken* references with routed job attributes Remove certinfo flie log messages Fix crash on send failure HTCondor 9.0.13 : Bug fix release Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations HTCondor-CE 5.1.5 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Rename AuthToken attributes in the routed job to better support accounting Prevent GSI environment from pointing the job to the wrong certificates Fix issue where HTCondor-CE would need port 9618 open to start up XCache 3.1.0 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged XRootD 5.4.3 RC4 htvault-config 1.13 removes support for old style secret storage, requires htgettoken >= 1.7 htgettoken 1.12 avoids crash when verbose output includes UTF-8 osg-pki-tools 3.5.2 bug fix for osg-incommon-cert-request when using host file osg-release 3.6-5: Add osg-next yum repository osg-token-renewer 0.8.2 use oidc-agent's built-in password file option ensure tokens are renewed more frequently than their lifespan rrdtool 1.8.0-1.2.el7: make Python RRDtools available to GlideinWMS stashcp 6.7.5 Adds multi-file transfer and improved error messages relax download timeouts for file transfer plugin multiple bug fixes xrootd-multiuser 2.0.4 fix crash on EL8 Discussion \u00b6 Sometimes packages get stuck in Ready for Testing state because they are considered \"critical\" but no external people have provided feedback. Mat suggests amending our release policy such that critical packages are released after a month without negative feedback, even if no positive feedback has been received. Tim says that would be better for software that has received VMU testing or has been well tested outside of OSG. We have an IRIS-HEP metric to increase the percentage of packages tested in VMU; Brian will create tickets. Also discussed improving coordination of testing between OSG Operations and Software","title":"June 7, 2022"},{"location":"meetings/2022/TechArea20220607/#osg-technology-area-meeting-7-june-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Ziyang","title":"OSG Technology Area Meeting, 7 June 2022"},{"location":"meetings/2022/TechArea20220607/#announcements","text":"Mat OOO Jun 13 BrianL traveling Jun 13-16, OOO Jun 17 Next week's meeting canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220607/#triage-duty","text":"This week: Mat Next week: TimT 11 (-4) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220607/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +1 Open 32 +1 Selected for Dev 27 +3 In Progress 14 -3 Dev Complete 28 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220607/#osg-software-team","text":"Doc focus Friday afternoon JLab FE and VO certs expire next Thursday, Ops may need a reminder to update the certs next week BNL will be submitting EIC jobs via Harvester and will pass along a subject DN that we need added to the vo-client Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): backfill container should shut down upon HTCondor exit (SOFTWARE-4608) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) AI (Carl): remove duplicate contact entries in the Topology contact pages (SOFTWARE-5214)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220607/#discussion","text":"There are several Docker images that are built from individual GitHub repositories instead of the central \"images\" repository. They should be moved to the images repo; keep an eye on how well GitHub Actions workflows scale, though. COManage registration denials seem to be sticky; if you want to admit someone you have previously denied, you will have to expunge the CO Person record","title":"Discussion"},{"location":"meetings/2022/TechArea20220607/#support-update","text":"JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. They will lift the blacklisting of ScotsGrid to try to gather more info Belle II (BrianL): will be having a meeting this week to discuss token-based pilot submission Texas Tech (BrianL): new backfill container site, working on fixing COManage registrations WeNMR (BrianL): helping DIRAC developers test token-based pilot submission BNL (Mat): Experiencing CA failures with XRootD TPC. Their CA certificates look fine; Mat has requested that they perform some manual tests to try and isolate the error. The XRootD developers are Cc'ed on the ticket and can provide debugging assistance.","title":"Support Update"},{"location":"meetings/2022/TechArea20220607/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.5 gratia-probe 2.6.1 Log schedd cron errors with newer versions of HTCondor Replace AuthToken* references with routed job attributes Remove certinfo flie log messages Fix crash on send failure HTCondor 9.0.13 : Bug fix release Schedd and startd cron jobs can now log output upon non-zero exit condor_config_val now produces correct syntax for multi-line values The condor_run tool now reports submit errors and warnings to the terminal Fix issue where Kerberos authentication would fail within DAGMan Fix HTCondor startup failure with certain complex network configurations HTCondor-CE 5.1.5 Fix whole node job glidein CPUs and GPUs exprs that caused held jobs Fix bug where default CERequirements were being ignored Pass whole node request from GlideinWMS to the batch system Rename AuthToken attributes in the routed job to better support accounting Prevent GSI environment from pointing the job to the wrong certificates Fix issue where HTCondor-CE would need port 9618 open to start up XCache 3.1.0 Fixed library dependency issues for xcache-reporter Add systemd overrides for xrootd-privileged XRootD 5.4.3 RC4 htvault-config 1.13 removes support for old style secret storage, requires htgettoken >= 1.7 htgettoken 1.12 avoids crash when verbose output includes UTF-8 osg-pki-tools 3.5.2 bug fix for osg-incommon-cert-request when using host file osg-release 3.6-5: Add osg-next yum repository osg-token-renewer 0.8.2 use oidc-agent's built-in password file option ensure tokens are renewed more frequently than their lifespan rrdtool 1.8.0-1.2.el7: make Python RRDtools available to GlideinWMS stashcp 6.7.5 Adds multi-file transfer and improved error messages relax download timeouts for file transfer plugin multiple bug fixes xrootd-multiuser 2.0.4 fix crash on EL8","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220607/#discussion_1","text":"Sometimes packages get stuck in Ready for Testing state because they are considered \"critical\" but no external people have provided feedback. Mat suggests amending our release policy such that critical packages are released after a month without negative feedback, even if no positive feedback has been received. Tim says that would be better for software that has received VMU testing or has been well tested outside of OSG. We have an IRIS-HEP metric to increase the percentage of packages tested in VMU; Brian will create tickets. Also discussed improving coordination of testing between OSG Operations and Software","title":"Discussion"},{"location":"meetings/2022/TechArea20220621/","text":"OSG Technology Area Meeting, 21 June 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, Ziyang Announcements \u00b6 TimT OOO this week BrianL OOO Thu, Fri Triage Duty \u00b6 This week: Carl Next week: BrianL 13 (+2) open FreshDesk tickets 0 (-1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 187 +3 Open 34 -3 Selected for Dev 29 +0 In Progress 22 +3 Dev Complete 5 -7 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) Discussion \u00b6 Sketched out a plan to split the Topology git repo into two, one for code and one for data Support Update \u00b6 CHTC (Derek, Mat): issues with authenticated access to origin-auth2001 OSPool (BrianL, Mat): many shadow failures due to an issue with the user job wrapper. Currently suspecting a startd cron script locking issue. JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. Seems like we're requesting 8 core pilots but only advertising single core slots. Hosted CEs (Carl): identified an FD file leak in the scitokens-cpp library","title":"June 21, 2022"},{"location":"meetings/2022/TechArea20220621/#osg-technology-area-meeting-21-june-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, Ziyang","title":"OSG Technology Area Meeting, 21 June 2022"},{"location":"meetings/2022/TechArea20220621/#announcements","text":"TimT OOO this week BrianL OOO Thu, Fri","title":"Announcements"},{"location":"meetings/2022/TechArea20220621/#triage-duty","text":"This week: Carl Next week: BrianL 13 (+2) open FreshDesk tickets 0 (-1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220621/#jira-as-of-monday","text":"# of tickets \u0394 State 187 +3 Open 34 -3 Selected for Dev 29 +0 In Progress 22 +3 Dev Complete 5 -7 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220621/#osg-software-team","text":"Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220621/#discussion","text":"Sketched out a plan to split the Topology git repo into two, one for code and one for data","title":"Discussion"},{"location":"meetings/2022/TechArea20220621/#support-update","text":"CHTC (Derek, Mat): issues with authenticated access to origin-auth2001 OSPool (BrianL, Mat): many shadow failures due to an issue with the user job wrapper. Currently suspecting a startd cron script locking issue. JLab (BrianL): JLab and their ScotsGrid site are seeing low CPU utiliziation from Slurm for CLAS12 pilots. Seems like we're requesting 8 core pilots but only advertising single core slots. Hosted CEs (Carl): identified an FD file leak in the scitokens-cpp library","title":"Support Update"},{"location":"meetings/2022/TechArea20220628/","text":"OSG Technology Area Meeting, 28 June 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Ziyang Announcements \u00b6 BrianL OOO Fri, Tue Next week's meeting canceled Triage Duty \u00b6 This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 189 +2 Open 33 -1 Selected for Dev 27 -2 In Progress 17 -5 Dev Complete 8 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon this afternoon Doc focus afternoon of Jul 15 Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013) Discussion \u00b6 We had a short discussion regarding the appropriate fix for the way that GlideinWMS writes to glidein_config ; BrianL will discuss thoughts with the HTCSS dev team and get back to Marco Support Update \u00b6 OSPool (BrianL, Mat): discovered GlideinWMS file locking issue causing user job wrapper shadow exceptions","title":"June 28, 2022"},{"location":"meetings/2022/TechArea20220628/#osg-technology-area-meeting-28-june-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Ziyang","title":"OSG Technology Area Meeting, 28 June 2022"},{"location":"meetings/2022/TechArea20220628/#announcements","text":"BrianL OOO Fri, Tue Next week's meeting canceled","title":"Announcements"},{"location":"meetings/2022/TechArea20220628/#triage-duty","text":"This week: BrianL Next week: Mat 16 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220628/#jira-as-of-monday","text":"# of tickets \u0394 State 189 +2 Open 33 -1 Selected for Dev 27 -2 In Progress 17 -5 Dev Complete 8 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220628/#osg-software-team","text":"Kubernetes hackathon this afternoon Doc focus afternoon of Jul 15 Streamline deployments of OSDF caches and origins AI (Mat): Add topology endpoint serving cache/namespace mappings (SOFTWARE-5179) AI (Mat): Evaluate state of SLATE stashcache chart (SOFTWARE-5211) AI (Carl): Add stashcache lookup by resource name (SOFTWARE-4347) AI (Carl): stash-cache/origin: allow toggling VOMS by environment variable (SOFTWARE-5106) AI (Carl): authfile generation fails if origin serves no public data (SOFTWARE-5028) AI (Carl): Authfiles for auth stash origins should include the origin's DN (SOFTWARE-4399) AI (Carl): Validate OSDF data in Topology (SOFTWARE-4167) AI (Carl): add ability to specify custom workflows in opensciencegrid/images (SOFTWARE-5013)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220628/#discussion","text":"We had a short discussion regarding the appropriate fix for the way that GlideinWMS writes to glidein_config ; BrianL will discuss thoughts with the HTCSS dev team and get back to Marco","title":"Discussion"},{"location":"meetings/2022/TechArea20220628/#support-update","text":"OSPool (BrianL, Mat): discovered GlideinWMS file locking issue causing user job wrapper shadow exceptions","title":"Support Update"},{"location":"meetings/2022/TechArea20220726/","text":"OSG Technology Area Meeting, 26 July 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Derek out this week Triage Duty \u00b6 This week: Mat Next week: TimT 8 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 189 +0 Open 30 +2 Selected for Dev 31 +0 In Progress 17 -5 Dev Complete 16 +6 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): high prio (must be completed this week), continue Derek's GRACC correction work for Purdue Kubernetes hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (Mat): Validate CHTC-canary2 CE; see if pilots are filling up /tmp on exec nodes and why AI (Carl): enumerate differences between Kubernetes caches (SOFTWARE-5259) AI (BrianL): use Dex and COManage to give external collaborators read-only access to the osgdev namespace Discussion \u00b6 CMS running into problems with their XRootD redirector where due to a misconfiguration, writes went to random hosts. They would like a config knob to prevent this kind of misconfiguration; BrianL suggested that they send mail to the XRootD development list. Support Update \u00b6 Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots IceCube (BrianL): investigate OS Registry failure to issue token due to split of OSPool CCB/CM FNAL (BrianL): diagnose FD leaks affecting Bridges2/Expanse Hosted CEs FNAL (Carl): waiting for response regarding testing of new version of gratia-probes BNL (Mat): GermanGrid CA signed with SHA1; asked Doug if his crypto policy allows that OSG Release Team \u00b6 Ready for Testing gratia-probe 2.7.0 xrootd-monitoring-shoveler 1.1.2 HTCondor 9.10.1 blahp 2.2.1 HTCondor 9.0.15 CVMFS 2.9.3 osg-xrootd 3.6-18 XRootD 5.4.3-1.2 htgettoken 1.15 osg-release 3.5-9 Discussion \u00b6 Release this week.","title":"July 26, 2022"},{"location":"meetings/2022/TechArea20220726/#osg-technology-area-meeting-26-july-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 26 July 2022"},{"location":"meetings/2022/TechArea20220726/#announcements","text":"Derek out this week","title":"Announcements"},{"location":"meetings/2022/TechArea20220726/#triage-duty","text":"This week: Mat Next week: TimT 8 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220726/#jira-as-of-monday","text":"# of tickets \u0394 State 189 +0 Open 30 +2 Selected for Dev 31 +0 In Progress 17 -5 Dev Complete 16 +6 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220726/#osg-software-team","text":"AI (Carl): high prio (must be completed this week), continue Derek's GRACC correction work for Purdue Kubernetes hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (Mat): Validate CHTC-canary2 CE; see if pilots are filling up /tmp on exec nodes and why AI (Carl): enumerate differences between Kubernetes caches (SOFTWARE-5259) AI (BrianL): use Dex and COManage to give external collaborators read-only access to the osgdev namespace","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220726/#discussion","text":"CMS running into problems with their XRootD redirector where due to a misconfiguration, writes went to random hosts. They would like a config knob to prevent this kind of misconfiguration; BrianL suggested that they send mail to the XRootD development list.","title":"Discussion"},{"location":"meetings/2022/TechArea20220726/#support-update","text":"Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots IceCube (BrianL): investigate OS Registry failure to issue token due to split of OSPool CCB/CM FNAL (BrianL): diagnose FD leaks affecting Bridges2/Expanse Hosted CEs FNAL (Carl): waiting for response regarding testing of new version of gratia-probes BNL (Mat): GermanGrid CA signed with SHA1; asked Doug if his crypto policy allows that","title":"Support Update"},{"location":"meetings/2022/TechArea20220726/#osg-release-team","text":"Ready for Testing gratia-probe 2.7.0 xrootd-monitoring-shoveler 1.1.2 HTCondor 9.10.1 blahp 2.2.1 HTCondor 9.0.15 CVMFS 2.9.3 osg-xrootd 3.6-18 XRootD 5.4.3-1.2 htgettoken 1.15 osg-release 3.5-9","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220726/#discussion_1","text":"Release this week.","title":"Discussion"},{"location":"meetings/2022/TechArea20220802/","text":"OSG Technology Area Meeting, 2 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT Announcements \u00b6 Mat OOO Wed - Fri TimT OOO Thu + Fri BrianL OOO Fri + Mon Triage Duty \u00b6 This week: Carl Next week: TimT 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket Discussion \u00b6 Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; he and Derek will debug. Support Update \u00b6 Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. CLAS12 (Derek): Helping fix gratia, /var/lock/condor failed to be created. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, not sure what's going on, debugging. (Ugh, the issuer is complicated) OSG Release Team \u00b6 Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes) Discussion \u00b6 No release this week","title":"August 2, 2022"},{"location":"meetings/2022/TechArea20220802/#osg-technology-area-meeting-2-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 2 August 2022"},{"location":"meetings/2022/TechArea20220802/#announcements","text":"Mat OOO Wed - Fri TimT OOO Thu + Fri BrianL OOO Fri + Mon","title":"Announcements"},{"location":"meetings/2022/TechArea20220802/#triage-duty","text":"This week: Carl Next week: TimT 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220802/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220802/#osg-software-team","text":"AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220802/#discussion","text":"Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; he and Derek will debug.","title":"Discussion"},{"location":"meetings/2022/TechArea20220802/#support-update","text":"Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. CLAS12 (Derek): Helping fix gratia, /var/lock/condor failed to be created. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, not sure what's going on, debugging. (Ugh, the issuer is complicated)","title":"Support Update"},{"location":"meetings/2022/TechArea20220802/#osg-release-team","text":"Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220802/#discussion_1","text":"No release this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220809/","text":"OSG Technology Area Meeting, 9 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Derek, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: TimT Next week: ? 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket Discussion \u00b6 Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; Derek will send email to ToddM regarding this feature. Support Update \u00b6 Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, Fixed! The JSON of the user-config was not valid (my fault, typo) OSG Release Team \u00b6 Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes) Discussion \u00b6 No release this week","title":"August 9, 2022"},{"location":"meetings/2022/TechArea20220809/#osg-technology-area-meeting-9-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 9 August 2022"},{"location":"meetings/2022/TechArea20220809/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20220809/#triage-duty","text":"This week: TimT Next week: ? 6 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220809/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +2 Open 33 +3 Selected for Dev 30 -1 In Progress 17 +0 Dev Complete 3 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220809/#osg-software-team","text":"Kubernetes Hackathon today AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): Check on /tmp in HPC exec nodes; update Canary2 to testing AI (Carl): complete custom workflows ticket","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220809/#discussion","text":"Mat: Topology DataFederation namespaces PR ready for review and also deployed on ITB. Marco: Working on GlideinWMS 3.9.6; adding Python 3.9 support. Derek: systemd-tmpfiles-setup did not create /var/lock/condor on one site because the \"condor\" user doesn't exist at the time systemd-tmpfiles-setup runs. TimT says that condor_master since 8.9.12 should create the necessary directories on startup if they are missing; Derek will send email to ToddM regarding this feature.","title":"Discussion"},{"location":"meetings/2022/TechArea20220809/#support-update","text":"Purdue (Derek, Carl, BrianL): help sort out fixes for incorrect accounting of whole node pilots FNAL (BrianL): redeployed FNAL CEs; still on OSG 3.5 so they're at risk of running into the same FD limit again FNAL (Carl): packaging fixes verified by Yujun. Submitted PR with some of Yujun's requested changes. BNL (Mat): Still debugging CA certs. BrianB had a back-and-forth with the admin; Mat will follow along. Florida (Derek): OSG shoveler issuer is issuing token with wrong audience, Fixed! The JSON of the user-config was not valid (my fault, typo)","title":"Support Update"},{"location":"meetings/2022/TechArea20220809/#osg-release-team","text":"Ready for Testing xrootd-monitoring-shoveler 1.1.2 Upcoming: HTCondor 9.11.0 RC2 (for patch Tuesday) HTCondor 9.0.16 RC1 (important bug fixes)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220809/#discussion_1","text":"No release this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220816/","text":"OSG Technology Area Meeting, 16 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Mat, TimT Announcements \u00b6 Mat, TimT out of office next Monday. Triage Duty \u00b6 This week: Brian Next week: Carl 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 187 -7 Open 38 +6 Selected for Dev 35 +5 In Progress 18 +1 Dev Complete 3 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Use COManage IDs in Topology wherever possible! AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): set up expiration notification template and workflow; contact COManage developers for assistance if needed AI (Carl): complete custom workflows ticket; meet with BrianL and Mat to discuss use cases for workflows Discussion \u00b6 The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday. Support Update \u00b6 FIU (Mat) working with FIU to resolve connection issues while attempting to mirror OSG Software repos. FNAL (Carl) worked with Yuijun and Kevin Retzke on Gratia probe changes. Software team work is done for now; at this point Yuijun and Kevin should discuss their requirements. OSG Release Team \u00b6 Ready for Testing xrootd-monitoring-shoveler 1.1.2 HTCondor 9.0.16 (important bug fixes) Upcoming: HTCondor 9.11.0 RC2 Discussion \u00b6 - Release xrootd-monitoring-shoveler and HTCondor 9.0.16 this week.","title":"August 16, 2022"},{"location":"meetings/2022/TechArea20220816/#osg-technology-area-meeting-16-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 16 August 2022"},{"location":"meetings/2022/TechArea20220816/#announcements","text":"Mat, TimT out of office next Monday.","title":"Announcements"},{"location":"meetings/2022/TechArea20220816/#triage-duty","text":"This week: Brian Next week: Carl 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220816/#jira-as-of-monday","text":"# of tickets \u0394 State 187 -7 Open 38 +6 Selected for Dev 35 +5 In Progress 18 +1 Dev Complete 3 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220816/#osg-software-team","text":"Use COManage IDs in Topology wherever possible! AI (Mat): build stash-origin chart (SOFTWARE-5258) AI (BrianL): set up expiration notification template and workflow; contact COManage developers for assistance if needed AI (Carl): complete custom workflows ticket; meet with BrianL and Mat to discuss use cases for workflows","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220816/#discussion","text":"The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday.","title":"Discussion"},{"location":"meetings/2022/TechArea20220816/#support-update","text":"FIU (Mat) working with FIU to resolve connection issues while attempting to mirror OSG Software repos. FNAL (Carl) worked with Yuijun and Kevin Retzke on Gratia probe changes. Software team work is done for now; at this point Yuijun and Kevin should discuss their requirements.","title":"Support Update"},{"location":"meetings/2022/TechArea20220816/#osg-release-team","text":"Ready for Testing xrootd-monitoring-shoveler 1.1.2 HTCondor 9.0.16 (important bug fixes) Upcoming: HTCondor 9.11.0 RC2","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220816/#discussion_1","text":"- Release xrootd-monitoring-shoveler and HTCondor 9.0.16 this week.","title":"Discussion"},{"location":"meetings/2022/TechArea20220823/","text":"OSG Technology Area Meeting, 23 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Carl, Marco Mambelli, Ziyang Announcements \u00b6 Carl out Wednesdays Triage Duty \u00b6 This week: Carl Next week: Carl 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 190 +3 Open 44 +6 Selected for Dev 24 -11 In Progress 144 -4 Dev Complete 5 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon today, already discussed things on the docket Fields (like github username) are editible in comanage; would be good to test editing especially if we are non-admins Marco: has PR for GWMS item; troubleshooting Mats's issue AI (BrianL, Mat, Carl) discuss all the container building use cases AI (Mat): check in with Fabio to see where PR for hawaii origin stands Discussion \u00b6 Do we want to fork off existing SLATE chart, or do we just make the changes? Eventually want cache in tiger for our purposes. The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday. Support Update \u00b6 None this week OSG Release Team \u00b6 TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp Discussion \u00b6 TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"August 23, 2022"},{"location":"meetings/2022/TechArea20220823/#osg-technology-area-meeting-23-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT, Carl, Marco Mambelli, Ziyang","title":"OSG Technology Area Meeting, 23 August 2022"},{"location":"meetings/2022/TechArea20220823/#announcements","text":"Carl out Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20220823/#triage-duty","text":"This week: Carl Next week: Carl 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220823/#jira-as-of-monday","text":"# of tickets \u0394 State 190 +3 Open 44 +6 Selected for Dev 24 -11 In Progress 144 -4 Dev Complete 5 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220823/#osg-software-team","text":"Kubernetes hackathon today, already discussed things on the docket Fields (like github username) are editible in comanage; would be good to test editing especially if we are non-admins Marco: has PR for GWMS item; troubleshooting Mats's issue AI (BrianL, Mat, Carl) discuss all the container building use cases AI (Mat): check in with Fabio to see where PR for hawaii origin stands","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220823/#discussion","text":"Do we want to fork off existing SLATE chart, or do we just make the changes? Eventually want cache in tiger for our purposes. The new EPEL release of Apptainer (the replacement for Singularity) requires user namespaces. This will need to be documented for admins. The GlideinWMS developers planning a release candidate for this week. They recently worked with the HTCondor Team to debug an HTCondor-CE issue with dual stack IPv4/IPv6. BrianL will investigate the CE default configuration to see what might have caused that. Expecting a new HTCondor 9.0.16 release today, and a 9.11.0 release on Thursday.","title":"Discussion"},{"location":"meetings/2022/TechArea20220823/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20220823/#osg-release-team","text":"TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220823/#discussion_1","text":"TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220830/","text":"OSG Technology Area Meeting, 30 August 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT, Ziyang Announcements \u00b6 Carl out Wednesdays Ziyang's last day is today Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): OSDF origin chart AI (Mat): Assist Fabio with setting up the University of Hawaii origin; we are currently waiting on them for Resource Group information, after which Mat will help with Data Federation information -- the format of that information is new AI (Carl): XRootD 5.5.0 release; contact Mat for assistance as needed AI (Carl): Review various PRs for the Tiger Kubernetes cluster AI (BrianL): Review and reprioritize Software Team JIRA tickets AI (BrianL): Review PATh metrics for the monthly report before the end of the month Discussion \u00b6 Marco: GlideinWMS 3.9.6 expected by the end of the week; fixed setup issues noticed by Mat and others, and added a token generator Support Update \u00b6 USC (BrianL): helped solve issues with backfill containers; issues caused by tokens and using an outdated image. Admins were surprised that the pilots exited because they didn't get any jobs; this event should be communicated more clearly, perhaps in the container logs Virgo (BrianL): helped Jason resolve issues with Virgo proxy generation due to upstream VOMS server cert update LIGO (Carl): assisted Peter Couvares with getting the HTCondor version on a CE LIGO (Carl): received formal request from LIGO for first-class SIF file support on the OS Pool; redirected to Jason but Mats should also be added -- for now this is a question of OS Pool policy OS Pool (Derek): user wanted to have a very large file accessible on /cvmfs/stash.osgstorage.org . Derek increased the max file size from 26 GB to 500 GB. This change should not affect anything except large files, but staff should keep an eye out for issues MIT (Derek): Credential for lightweight issuer, hopefully can be resolved with a few more back and forths. WTAMU (Derek): observed a difference between pilot and payload hours -- looks to be due to the site having huge slots (64 cores) with Glideins pilots retiring (finishing old jobs but no longer accepting new jobs) but with a handful of long, small jobs keeping the pilot alive. Mats suggested increasing the pilot lifetime OS Pool (Derek): cvmfs-singularity-sync started deleting containers on CVMFS yesterday (8/29). The problem was fixed and the containers restored; the issue was due to code changes in order to support tag wildcards on hub.opensciencegrid.org. Derek is writing a full incident report. OSG Release Team \u00b6 TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp Discussion \u00b6 TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"August 30, 2022"},{"location":"meetings/2022/TechArea20220830/#osg-technology-area-meeting-30-august-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Marco Mambelli, Mat, TimT, Ziyang","title":"OSG Technology Area Meeting, 30 August 2022"},{"location":"meetings/2022/TechArea20220830/#announcements","text":"Carl out Wednesdays Ziyang's last day is today","title":"Announcements"},{"location":"meetings/2022/TechArea20220830/#triage-duty","text":"This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220830/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220830/#osg-software-team","text":"AI (Mat): OSDF origin chart AI (Mat): Assist Fabio with setting up the University of Hawaii origin; we are currently waiting on them for Resource Group information, after which Mat will help with Data Federation information -- the format of that information is new AI (Carl): XRootD 5.5.0 release; contact Mat for assistance as needed AI (Carl): Review various PRs for the Tiger Kubernetes cluster AI (BrianL): Review and reprioritize Software Team JIRA tickets AI (BrianL): Review PATh metrics for the monthly report before the end of the month","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220830/#discussion","text":"Marco: GlideinWMS 3.9.6 expected by the end of the week; fixed setup issues noticed by Mat and others, and added a token generator","title":"Discussion"},{"location":"meetings/2022/TechArea20220830/#support-update","text":"USC (BrianL): helped solve issues with backfill containers; issues caused by tokens and using an outdated image. Admins were surprised that the pilots exited because they didn't get any jobs; this event should be communicated more clearly, perhaps in the container logs Virgo (BrianL): helped Jason resolve issues with Virgo proxy generation due to upstream VOMS server cert update LIGO (Carl): assisted Peter Couvares with getting the HTCondor version on a CE LIGO (Carl): received formal request from LIGO for first-class SIF file support on the OS Pool; redirected to Jason but Mats should also be added -- for now this is a question of OS Pool policy OS Pool (Derek): user wanted to have a very large file accessible on /cvmfs/stash.osgstorage.org . Derek increased the max file size from 26 GB to 500 GB. This change should not affect anything except large files, but staff should keep an eye out for issues MIT (Derek): Credential for lightweight issuer, hopefully can be resolved with a few more back and forths. WTAMU (Derek): observed a difference between pilot and payload hours -- looks to be due to the site having huge slots (64 cores) with Glideins pilots retiring (finishing old jobs but no longer accepting new jobs) but with a handful of long, small jobs keeping the pilot alive. Mats suggested increasing the pilot lifetime OS Pool (Derek): cvmfs-singularity-sync started deleting containers on CVMFS yesterday (8/29). The problem was fixed and the containers restored; the issue was due to code changes in order to support tag wildcards on hub.opensciencegrid.org. Derek is writing a full incident report.","title":"Support Update"},{"location":"meetings/2022/TechArea20220830/#osg-release-team","text":"TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220830/#discussion_1","text":"TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220906/","text":"OSG Technology Area Meeting, 6 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT Announcements \u00b6 Carl out Wednesdays Triage Duty \u00b6 This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon this afternoon AI (BrianL): Debug Dex authentication system for the Tiger cluster AI (Mat): Assist IceCube with Kubernetes networking AI (Mat): Continue development of OSDF origin chart New CHTC Infrastructure Services student starting (Aiden) AI (Carl): hosted-ce-tools Python 3 compatibility Discussion \u00b6 None this week Support Update \u00b6 Mat (LIGO): James Clark is interested in what OSG does for job monitoring; this is something that both OSG and HTCSS devs are interested in, so suggest that they discuss this at their regular LIGO-HTCSS meeting OSG Release Team \u00b6 TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp Discussion \u00b6 TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"September 6, 2022"},{"location":"meetings/2022/TechArea20220906/#osg-technology-area-meeting-6-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, TimT","title":"OSG Technology Area Meeting, 6 September 2022"},{"location":"meetings/2022/TechArea20220906/#announcements","text":"Carl out Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20220906/#triage-duty","text":"This week: Mat Next week: TimT 11 (+4) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220906/#jira-as-of-monday","text":"# of tickets \u0394 State 191 +1 Open 44 +0 Selected for Dev 26 +2 In Progress 12 -2 Dev Complete 2 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220906/#osg-software-team","text":"Kubernetes Hackathon this afternoon AI (BrianL): Debug Dex authentication system for the Tiger cluster AI (Mat): Assist IceCube with Kubernetes networking AI (Mat): Continue development of OSDF origin chart New CHTC Infrastructure Services student starting (Aiden) AI (Carl): hosted-ce-tools Python 3 compatibility","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220906/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20220906/#support-update","text":"Mat (LIGO): James Clark is interested in what OSG does for job monitoring; this is something that both OSG and HTCSS devs are interested in, so suggest that they discuss this at their regular LIGO-HTCSS meeting","title":"Support Update"},{"location":"meetings/2022/TechArea20220906/#osg-release-team","text":"TimT: new condor releases (9.11.1) Ready for Testing gratia-probe stashcp","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220906/#discussion_1","text":"TimT: note prce2 more strict about character classes in regex (hyphen must go at the end [abc-] ) BrianL: need to find victims to update from stable series to 9.12 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220913/","text":"OSG Technology Area Meeting, 13 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT Announcements \u00b6 Carl out Wednesdays Triage Duty \u00b6 This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 206 -1 Open 36 +5 Selected for Dev 22 +2 In Progress 9 +0 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Next doc focus Oct 7 AI (Mat): OSDF origin Helm chart AI (Mat): fix rsyslog in glideins AI (Mat): add changes for XCache: review Carl's PR for authfile generator add extra issuer for PRP caches for Fabio AI (Carl): auto-generate OASIS StashCache configs AI (Carl): improve hosted-ce-tools Python 3 support AI (BrianL): cut new topology client AI (BrianL): meet with Igor et al. to discuss handoff of supporting Lancium provisioner from GIL to Operations or Software AI (Mat/Carl): discuss interface for supporting complex disk setups in OSDF Helm charts AI (TimT): fix regexps in condor-mapfile in HTCondor-CE 5 to be compatible with HTCondor 9.11+ Discussion \u00b6 LIGO has tested XRootD 5.5.0, which fixed scitokens issues they were having. LIGO uses CILogon and Vault for managing token auth. Support Update \u00b6 COManage (BrianL): manually fix a user's access, notes in FD#70228 LIGO (Derek): Debug HTTP(s) transfers with tokens. Failed with 5.4.3, works with 5.5.0 (osg-testing). So calling it a success. FNAL (Derek): Low cpu utilization at FNAL a few months back. Not sure there is much to debug as source of truth. LIGO (Derek): New CVMFS repo for igwn.osgstorage.org, copy of ligo.osgstorage.org (will be a symlink) LIGO (Carl): assisted CalTech in registering their Squid proxy in Topology OSG Release Team \u00b6 Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3 Discussion \u00b6 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"September 13, 2022"},{"location":"meetings/2022/TechArea20220913/#osg-technology-area-meeting-13-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 13 September 2022"},{"location":"meetings/2022/TechArea20220913/#announcements","text":"Carl out Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20220913/#triage-duty","text":"This week: BrianL Next week: Carl 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220913/#jira-as-of-monday","text":"# of tickets \u0394 State 206 -1 Open 36 +5 Selected for Dev 22 +2 In Progress 9 +0 Dev Complete 4 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220913/#osg-software-team","text":"Next doc focus Oct 7 AI (Mat): OSDF origin Helm chart AI (Mat): fix rsyslog in glideins AI (Mat): add changes for XCache: review Carl's PR for authfile generator add extra issuer for PRP caches for Fabio AI (Carl): auto-generate OASIS StashCache configs AI (Carl): improve hosted-ce-tools Python 3 support AI (BrianL): cut new topology client AI (BrianL): meet with Igor et al. to discuss handoff of supporting Lancium provisioner from GIL to Operations or Software AI (Mat/Carl): discuss interface for supporting complex disk setups in OSDF Helm charts AI (TimT): fix regexps in condor-mapfile in HTCondor-CE 5 to be compatible with HTCondor 9.11+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220913/#discussion","text":"LIGO has tested XRootD 5.5.0, which fixed scitokens issues they were having. LIGO uses CILogon and Vault for managing token auth.","title":"Discussion"},{"location":"meetings/2022/TechArea20220913/#support-update","text":"COManage (BrianL): manually fix a user's access, notes in FD#70228 LIGO (Derek): Debug HTTP(s) transfers with tokens. Failed with 5.4.3, works with 5.5.0 (osg-testing). So calling it a success. FNAL (Derek): Low cpu utilization at FNAL a few months back. Not sure there is much to debug as source of truth. LIGO (Derek): New CVMFS repo for igwn.osgstorage.org, copy of ligo.osgstorage.org (will be a symlink) LIGO (Carl): assisted CalTech in registering their Squid proxy in Topology","title":"Support Update"},{"location":"meetings/2022/TechArea20220913/#osg-release-team","text":"Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220913/#discussion_1","text":"AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220920/","text":"OSG Technology Area Meeting, 20 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT Announcements \u00b6 None this week Triage Duty \u00b6 This week: Carl Next week: Mat 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 209 +3 Open 33 -3 Selected for Dev 18 -4 In Progress 14 +5 Dev Complete 0 -4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today: AI (Carl): deploy SLATE stashcache chart in Tiger AI (Mat): OSDF origin Helm chart Next doc focus Oct 7 AI (Mat): fix rsyslog in glideins AI (Mat): rebuild XCache to fix extra issuer bug AI (Carl): build XRootD 5.5.1 release candidate AI (Carl): auto-generate OASIS StashCache configs: There is a PR for scripts to compare the various configs against each other; request input from Dave Dykstra and Derek about what to do with the comparison results. AI (TimT): Release HTCondor-CE 5.1.6 for various bugfixes Discussion \u00b6 HTCondor-CE 5.1.6 scheduled for this week. Marco: GlideinWMS 3.9.6rc3 released last week; this is expected to be the last release candidate before the final release. LIGO is interested in Decision Engine; Marco is updating documentation and will send overview material. Support Update \u00b6 None this week OSG Release Team \u00b6 Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3 Discussion \u00b6 AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"September 20, 2022"},{"location":"meetings/2022/TechArea20220920/#osg-technology-area-meeting-20-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 20 September 2022"},{"location":"meetings/2022/TechArea20220920/#announcements","text":"None this week","title":"Announcements"},{"location":"meetings/2022/TechArea20220920/#triage-duty","text":"This week: Carl Next week: Mat 6 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220920/#jira-as-of-monday","text":"# of tickets \u0394 State 209 +3 Open 33 -3 Selected for Dev 18 -4 In Progress 14 +5 Dev Complete 0 -4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220920/#osg-software-team","text":"Kubernetes Hackathon today: AI (Carl): deploy SLATE stashcache chart in Tiger AI (Mat): OSDF origin Helm chart Next doc focus Oct 7 AI (Mat): fix rsyslog in glideins AI (Mat): rebuild XCache to fix extra issuer bug AI (Carl): build XRootD 5.5.1 release candidate AI (Carl): auto-generate OASIS StashCache configs: There is a PR for scripts to compare the various configs against each other; request input from Dave Dykstra and Derek about what to do with the comparison results. AI (TimT): Release HTCondor-CE 5.1.6 for various bugfixes","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220920/#discussion","text":"HTCondor-CE 5.1.6 scheduled for this week. Marco: GlideinWMS 3.9.6rc3 released last week; this is expected to be the last release candidate before the final release. LIGO is interested in Decision Engine; Marco is updating documentation and will send overview material.","title":"Discussion"},{"location":"meetings/2022/TechArea20220920/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20220920/#osg-release-team","text":"Patch Tuesday Release today to Execution Points Ready for Testing XRootD 5.5.0 Ready for Release stashcp 6.8.1 osg-token-renewer 0.8.3","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220920/#discussion_1","text":"AI (TimT): reach out to John Thiltges about feasibility of updating to 10.0? (TimT: 9.12.0 in a couple weeks)","title":"Discussion"},{"location":"meetings/2022/TechArea20220927/","text":"OSG Technology Area Meeting, 27 September 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, Marco Mambelli, TimT Announcements \u00b6 BrianL OOO Friday Triage Duty \u00b6 This week: Mat Next week: TimT 9 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 212 +3 Open 32 -1 Selected for Dev 17 -1 In Progress 13 -1 Dev Complete 5 +5 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 BrianL: Assisting Antonios with logging in -- his ACCESS CILogon credentials might be conflicting with his OSG CILogon credentials Talk to Aiden about tasks for the next two weeks. Carl: Have PR for validating stash/osdf cache data between OASIS and Topology. Mat: Test auth origin support in stash-origin containers. TimT: Putting 9.12.0 into OSPool. Thin pool improvements are being tested on CHTC. Planning on releasing 9.0.17 this week. Putting finishing touches on 10.0.0; mostly bringing UW spec file in sync with OSG. AIs (Carl): Putting Git identifiers into COManage. Upload missing hosted CE records to GRACC. AIs (Mat): Check if CHTC-canary2 has been sending rsyslog logs to central syslog server. Continue work on OSDF-Origin Helm chart. Fix rsyslog in pilots; assist Jason with setting up rsyslog for LIGO if needed. AIs (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. AI (TimT): Update HTCondor-CE in OSG repos to the latest release. AI (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. GlideinWMS: Two PRs remaining for GlideinWMS 3.9.6; release targeted for later this week. Investigating general credential support improvements. The factory would like to supply a list of credentials for a CE with fallback from one to the other (instead of using only one credential that has to be listed per-entry). Discussion \u00b6 Kernel issues in CHTC being investigated; most likely a kernel bug being triggered by having many condor_procds (one for each Glidein). Not worth holding up the release for. EL9 coming - transition tasks likely to be assigned to Carl. Support Update \u00b6 BrianL (PATh Facility): Helping users that have previously had XSEDE credentials log in to the Facility. Carl (unregistered Gratia probes): There are questions about how to match probe names with Topology identifiers. OSG Release Team \u00b6 Decision Engine: Versions 2.0.2 and 1.7.4 have been released. (1.7.4 is for internal use; 2.0.2 is the recommended version for external users.) Discussion \u00b6","title":"September 27, 2022"},{"location":"meetings/2022/TechArea20220927/#osg-technology-area-meeting-27-september-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, Marco Mambelli, TimT","title":"OSG Technology Area Meeting, 27 September 2022"},{"location":"meetings/2022/TechArea20220927/#announcements","text":"BrianL OOO Friday","title":"Announcements"},{"location":"meetings/2022/TechArea20220927/#triage-duty","text":"This week: Mat Next week: TimT 9 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20220927/#jira-as-of-monday","text":"# of tickets \u0394 State 212 +3 Open 32 -1 Selected for Dev 17 -1 In Progress 13 -1 Dev Complete 5 +5 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20220927/#osg-software-team","text":"BrianL: Assisting Antonios with logging in -- his ACCESS CILogon credentials might be conflicting with his OSG CILogon credentials Talk to Aiden about tasks for the next two weeks. Carl: Have PR for validating stash/osdf cache data between OASIS and Topology. Mat: Test auth origin support in stash-origin containers. TimT: Putting 9.12.0 into OSPool. Thin pool improvements are being tested on CHTC. Planning on releasing 9.0.17 this week. Putting finishing touches on 10.0.0; mostly bringing UW spec file in sync with OSG. AIs (Carl): Putting Git identifiers into COManage. Upload missing hosted CE records to GRACC. AIs (Mat): Check if CHTC-canary2 has been sending rsyslog logs to central syslog server. Continue work on OSDF-Origin Helm chart. Fix rsyslog in pilots; assist Jason with setting up rsyslog for LIGO if needed. AIs (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. AI (TimT): Update HTCondor-CE in OSG repos to the latest release. AI (BrianL): Brief our student Aiden on the big picture and upcoming tasks for GitHub container actions. GlideinWMS: Two PRs remaining for GlideinWMS 3.9.6; release targeted for later this week. Investigating general credential support improvements. The factory would like to supply a list of credentials for a CE with fallback from one to the other (instead of using only one credential that has to be listed per-entry).","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20220927/#discussion","text":"Kernel issues in CHTC being investigated; most likely a kernel bug being triggered by having many condor_procds (one for each Glidein). Not worth holding up the release for. EL9 coming - transition tasks likely to be assigned to Carl.","title":"Discussion"},{"location":"meetings/2022/TechArea20220927/#support-update","text":"BrianL (PATh Facility): Helping users that have previously had XSEDE credentials log in to the Facility. Carl (unregistered Gratia probes): There are questions about how to match probe names with Topology identifiers.","title":"Support Update"},{"location":"meetings/2022/TechArea20220927/#osg-release-team","text":"Decision Engine: Versions 2.0.2 and 1.7.4 have been released. (1.7.4 is for internal use; 2.0.2 is the recommended version for external users.)","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20220927/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2022/TechArea20221004/","text":"OSG Technology Area Meeting, 4 October 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT Announcements \u00b6 BrianL OOO (travel + vacation) the next two weeks Mat gone next Tue-Fri + following Monday morning for travel Triage Duty \u00b6 This week: TimT Next week: ? 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 214 +2 Open 32 +0 Selected for Dev 20 +3 In Progress 13 +0 Dev Complete 1 -4 Ready for Testing 4 +4 Ready for Release OSG Software Team \u00b6 TimT on triage duty next week; will do double duty Next Doc Focus this week Fri, Oct 7 Starting EL 9 work this month; including items for Carl after GitHub comanage identifier work; TimT may rope in help for EL9 prep work AI (Mat): OSDF helm chart for Fabio targeted for this week AI (Mat): fix rsyslog in glideins AI (Carl): Update Topology to pull GitHub identifier from COManage Discussion \u00b6 rsyslog not working at a lot of sites, see if canary sites are reporting properly with rsyslog; Lincoln is interested as well (in rsyslog), and in first-class rook PVC. Support Update \u00b6 BrianL: user issue, ssh key with comanage account; or 2fa like with duo; issue with XSEDE and ACCESS; submit6 never logged them in. Mat: stash issue; everything transferred to stderr; empty files cause transfers to fail; jobs w/ no stdout cause transfer failures; ospool ticket. Upgrades for stashcp. New upstream location for source tarballs. Carl: made PRs for retiring TIGER-OSG-BACKFILL; can review together at hackathon; Mat suggests doing things differently. OSG Release Team \u00b6 Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing Discussion \u00b6 None last week","title":"October 4, 2022"},{"location":"meetings/2022/TechArea20221004/#osg-technology-area-meeting-4-october-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT","title":"OSG Technology Area Meeting, 4 October 2022"},{"location":"meetings/2022/TechArea20221004/#announcements","text":"BrianL OOO (travel + vacation) the next two weeks Mat gone next Tue-Fri + following Monday morning for travel","title":"Announcements"},{"location":"meetings/2022/TechArea20221004/#triage-duty","text":"This week: TimT Next week: ? 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221004/#jira-as-of-monday","text":"# of tickets \u0394 State 214 +2 Open 32 +0 Selected for Dev 20 +3 In Progress 13 +0 Dev Complete 1 -4 Ready for Testing 4 +4 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221004/#osg-software-team","text":"TimT on triage duty next week; will do double duty Next Doc Focus this week Fri, Oct 7 Starting EL 9 work this month; including items for Carl after GitHub comanage identifier work; TimT may rope in help for EL9 prep work AI (Mat): OSDF helm chart for Fabio targeted for this week AI (Mat): fix rsyslog in glideins AI (Carl): Update Topology to pull GitHub identifier from COManage","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221004/#discussion","text":"rsyslog not working at a lot of sites, see if canary sites are reporting properly with rsyslog; Lincoln is interested as well (in rsyslog), and in first-class rook PVC.","title":"Discussion"},{"location":"meetings/2022/TechArea20221004/#support-update","text":"BrianL: user issue, ssh key with comanage account; or 2fa like with duo; issue with XSEDE and ACCESS; submit6 never logged them in. Mat: stash issue; everything transferred to stderr; empty files cause transfers to fail; jobs w/ no stdout cause transfer failures; ospool ticket. Upgrades for stashcp. New upstream location for source tarballs. Carl: made PRs for retiring TIGER-OSG-BACKFILL; can review together at hackathon; Mat suggests doing things differently.","title":"Support Update"},{"location":"meetings/2022/TechArea20221004/#osg-release-team","text":"Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221004/#discussion_1","text":"None last week","title":"Discussion"},{"location":"meetings/2022/TechArea20221018/","text":"OSG Technology Area Meeting, 18 October 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, Tim Announcements \u00b6 BrianL OOO (travel + vacation) this week Kubernetes Hackathon today - Researchers from a local lab will be joining for the tutorial Triage Duty \u00b6 This week: Carl Next week: Mat 10 (+3 from 2 weeks ago) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday 10/17) \u00b6 # of tickets \u0394 State 214 +2 Open 25 -7 Selected for Dev 22 +2 In Progress 16 +3 Dev Complete 4 +3 Ready for Testing 1 -3 Ready for Release OSG Software Team \u00b6 Starting EL 9 work this month AI (Mat): OSDF Origin Helm chart; use it to serve files from the UW-Madison ResearchDrive service Discussion \u00b6 None this week Support Update \u00b6 None last week OSG Release Team \u00b6 Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing Discussion \u00b6 None last week","title":"OSG Technology Area Meeting, 18 October 2022"},{"location":"meetings/2022/TechArea20221018/#osg-technology-area-meeting-18-october-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, Tim","title":"OSG Technology Area Meeting, 18 October 2022"},{"location":"meetings/2022/TechArea20221018/#announcements","text":"BrianL OOO (travel + vacation) this week Kubernetes Hackathon today - Researchers from a local lab will be joining for the tutorial","title":"Announcements"},{"location":"meetings/2022/TechArea20221018/#triage-duty","text":"This week: Carl Next week: Mat 10 (+3 from 2 weeks ago) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221018/#jira-as-of-monday-1017","text":"# of tickets \u0394 State 214 +2 Open 25 -7 Selected for Dev 22 +2 In Progress 16 +3 Dev Complete 4 +3 Ready for Testing 1 -3 Ready for Release","title":"Jira (as of Monday 10/17)"},{"location":"meetings/2022/TechArea20221018/#osg-software-team","text":"Starting EL 9 work this month AI (Mat): OSDF Origin Helm chart; use it to serve files from the UW-Madison ResearchDrive service","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221018/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221018/#support-update","text":"None last week","title":"Support Update"},{"location":"meetings/2022/TechArea20221018/#osg-release-team","text":"Ready for Testing XRootD 5.5.1 RC1 - Fix issue with FUSE mounts Ready for Release Nothing","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221018/#discussion_1","text":"None last week","title":"Discussion"},{"location":"meetings/2022/TechArea20221101/","text":"OSG Technology Area Meeting, 1 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT Announcements \u00b6 BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays Triage Duty \u00b6 This week: BrianL Next week: ? 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 217 +2 Open 25 +0 Selected for Dev 22 +0 In Progress 14 -1 Dev Complete 6 +2 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records EL 9 work starts this this month Discussion \u00b6 None this week Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0 Discussion \u00b6 None this week","title":"November 1, 2022"},{"location":"meetings/2022/TechArea20221101/#osg-technology-area-meeting-1-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Carl, TimT","title":"OSG Technology Area Meeting, 1 November 2022"},{"location":"meetings/2022/TechArea20221101/#announcements","text":"BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221101/#triage-duty","text":"This week: BrianL Next week: ? 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221101/#jira-as-of-monday","text":"# of tickets \u0394 State 217 +2 Open 25 +0 Selected for Dev 22 +0 In Progress 14 -1 Dev Complete 6 +2 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221101/#osg-software-team","text":"AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records EL 9 work starts this this month","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221101/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221101/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20221101/#osg-release-team","text":"Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221101/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221108/","text":"OSG Technology Area Meeting, 8 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT Announcements \u00b6 BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays Triage Duty \u00b6 This week: Mat Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) (TODO) \u00b6 # of tickets \u0394 State 217 +0 Open 27 +2 Selected for Dev 22 +0 In Progress 15 +1 Dev Complete 2 -4 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OS Pool AI (Mat): Update EL8 containers to Alma EL 9 work starts this this month Discussion \u00b6 GlideinWMS: Marco investigating what's causing Frontend to report 0 to factory monitoring in GlideinWMS 3.9.6. Support Update \u00b6 Carl (SIUE): Site is experiencing disk issues in their scratch space; Carl to follow up Mat (NERSC): Difficulty getting voms-mapfile to work for xrootd-standalone; will request assistance from XRootD developers OSG Release Team \u00b6 Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0 Discussion \u00b6 None this week","title":"November 8, 2022"},{"location":"meetings/2022/TechArea20221108/#osg-technology-area-meeting-8-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco Mambelli, Mat, TimT","title":"OSG Technology Area Meeting, 8 November 2022"},{"location":"meetings/2022/TechArea20221108/#announcements","text":"BrianL traveling to ATLAS meeting at the end of the month Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221108/#triage-duty","text":"This week: Mat Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221108/#jira-as-of-monday-todo","text":"# of tickets \u0394 State 217 +0 Open 27 +2 Selected for Dev 22 +0 In Progress 15 +1 Dev Complete 2 -4 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday) (TODO)"},{"location":"meetings/2022/TechArea20221108/#osg-software-team","text":"AI (Carl): PID namespace fix for backfill containers AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OS Pool AI (Mat): Update EL8 containers to Alma EL 9 work starts this this month","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221108/#discussion","text":"GlideinWMS: Marco investigating what's causing Frontend to report 0 to factory monitoring in GlideinWMS 3.9.6.","title":"Discussion"},{"location":"meetings/2022/TechArea20221108/#support-update","text":"Carl (SIUE): Site is experiencing disk issues in their scratch space; Carl to follow up Mat (NERSC): Difficulty getting voms-mapfile to work for xrootd-standalone; will request assistance from XRootD developers","title":"Support Update"},{"location":"meetings/2022/TechArea20221108/#osg-release-team","text":"Ready for Testing xrootd-mulituser 2.1.2 XCache 3.2.3 Ready for Release osdf-client 6.9.2 HTCondor-CE 5.1.6 Upcoming: HTCondor 9.12.0","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221108/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221115/","text":"OSG Technology Area Meeting, 15 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays Triage Duty \u00b6 This week: BrianL Next week: TimT 10 (+2) open FreshDesk tickets ? (+?) open GGUS ticket Jira (as of Monday) (TODO) \u00b6 # of tickets \u0394 State 229 +12 Open 23 -4 Selected for Dev 16 -6 In Progress 17 +2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat, Carl) EL 9 groundwork AI (Carl): Update valut to 1.12.1+ Discussion \u00b6 None this week Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 vault 1.12.1 Ready for Release Nothing Yet Discussion \u00b6 None this week","title":"November 15, 2022"},{"location":"meetings/2022/TechArea20221115/#osg-technology-area-meeting-15-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 15 November 2022"},{"location":"meetings/2022/TechArea20221115/#announcements","text":"BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221115/#triage-duty","text":"This week: BrianL Next week: TimT 10 (+2) open FreshDesk tickets ? (+?) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221115/#jira-as-of-monday-todo","text":"# of tickets \u0394 State 229 +12 Open 23 -4 Selected for Dev 16 -6 In Progress 17 +2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday) (TODO)"},{"location":"meetings/2022/TechArea20221115/#osg-software-team","text":"AI (Carl): fixup missing historical CE records; work is done, requesting sign-off from TimC and BrianL AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat, Carl) EL 9 groundwork AI (Carl): Update valut to 1.12.1+","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221115/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221115/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2022/TechArea20221115/#osg-release-team","text":"Ready for Testing CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 vault 1.12.1 Ready for Release Nothing Yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221115/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221122/","text":"OSG Technology Area Meeting, 22 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays Triage Duty \u00b6 This week: TimT Next week: Carl 10 (+0) open FreshDesk tickets ? (+?) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 233 -6 Open 23 +0 Selected for Dev 15 -1 In Progress 16 -1 Dev Complete 6 +3 Ready for Testing 0 +0 Ready for Release Brian will be tossing more things into backlog to make sense of prios; in need of cleaning OSG Software Team \u00b6 AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat): scitokens ticket for Steve Timm AI (Mat, Carl) EL 9 groundwork: Carl: for next week, add VMU images for EL9 (SOFTWARE-5337) After that: OSDF tickets selected for development: SOFTWARE-5296, SOFTWARE-5295 Discussion \u00b6 Marco: glideinwms: frontend is not reporting properly to monitoring Support Update \u00b6 BrianL: discusses Open Science Pool token registry; will manually create a token for comanage after discussion with Brians B,A University of Arkansas Little Rock (BrianL): working around an issue with ORCID and the self-service OS Registry NERSC (Mat, BrianB, BrianL): got a patched XRootD into testing for Lisa to install to test issues with missing Role/Capability in her VOMS certificate. That seems to be fixed but there are still ongoing issues. Mat: not getting logging we are supposed to for XRootD server at NERSC. CalTech startd cron not getting parsed correctly; BrianL will talk to Todd about it Carl: DESY: don't want other VOs they host Carl: unregistered gratia probes: we want to close for moral victory, might wanna check for more unreg probes at some point Derek: supporting TimC in osg-connect-ops Derek: Einstein telescope wants to use OSDF Derek: gratia probe payloads, identifying the pool? Next week, not this week. OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) One more xrootd patch for Mat to get in; Mat says go with 1.4, unresolved bug in 1.5 Vault 1.12.1 Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 22, 2022"},{"location":"meetings/2022/TechArea20221122/#osg-technology-area-meeting-22-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 22 November 2022"},{"location":"meetings/2022/TechArea20221122/#announcements","text":"BrianL traveling Nov 28 - Dec 2 Carl OOO Wednesdays","title":"Announcements"},{"location":"meetings/2022/TechArea20221122/#triage-duty","text":"This week: TimT Next week: Carl 10 (+0) open FreshDesk tickets ? (+?) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221122/#jira-as-of-monday","text":"# of tickets \u0394 State 233 -6 Open 23 +0 Selected for Dev 15 -1 In Progress 16 -1 Dev Complete 6 +3 Ready for Testing 0 +0 Ready for Release Brian will be tossing more things into backlog to make sense of prios; in need of cleaning","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221122/#osg-software-team","text":"AI (Mat): Assist Mats and HTCondor devs in getting container universe working on the OSPool AI (Mat): scitokens ticket for Steve Timm AI (Mat, Carl) EL 9 groundwork: Carl: for next week, add VMU images for EL9 (SOFTWARE-5337) After that: OSDF tickets selected for development: SOFTWARE-5296, SOFTWARE-5295","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221122/#discussion","text":"Marco: glideinwms: frontend is not reporting properly to monitoring","title":"Discussion"},{"location":"meetings/2022/TechArea20221122/#support-update","text":"BrianL: discusses Open Science Pool token registry; will manually create a token for comanage after discussion with Brians B,A University of Arkansas Little Rock (BrianL): working around an issue with ORCID and the self-service OS Registry NERSC (Mat, BrianB, BrianL): got a patched XRootD into testing for Lisa to install to test issues with missing Role/Capability in her VOMS certificate. That seems to be fixed but there are still ongoing issues. Mat: not getting logging we are supposed to for XRootD server at NERSC. CalTech startd cron not getting parsed correctly; BrianL will talk to Todd about it Carl: DESY: don't want other VOs they host Carl: unregistered gratia probes: we want to close for moral victory, might wanna check for more unreg probes at some point Derek: supporting TimC in osg-connect-ops Derek: Einstein telescope wants to use OSDF Derek: gratia probe payloads, identifying the pool? Next week, not this week.","title":"Support Update"},{"location":"meetings/2022/TechArea20221122/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) One more xrootd patch for Mat to get in; Mat says go with 1.4, unresolved bug in 1.5 Vault 1.12.1 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221122/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221129/","text":"OSG Technology Area Meeting, 29 November 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, TimT Announcements \u00b6 BrianL traveling Nov 28 - Dec 2 Triage Duty \u00b6 This week: Carl Next week: ? 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 240 +7 Open 22 -1 Selected for Dev 15 +0 In Progress 16 +0 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon: On Thursday, the default network for the Tiger Kubernetes cluster will change; people should review the services they are responsible for to make sure they will continue to function after the network change. AI (Mat): Create a variant of the pilot container that unpacks SIF files if they cannot be used directly. AI (Carl): Continue debugging COManage authentication failures on the Topology ITB instance. AI (Mat): Continue to assist Mats and HTCondor devs in getting container universe working on the OSPool, along with other pilot fixes. AI (Mat, Carl) Continue EL 9 groundwork. Discussion \u00b6 GlideinWMS: Fix available for factory monitoring issue. The ITB frontends and factory have been updated; waiting for green light from Mats and Marco Mascheroni before making a release. Support Update \u00b6 Mat (FNAL/CMS): Come up with a fix or workaround for gfal2 authentication failures when using the tarball client on EL8. Mat (CalTech): Discuss errors with parsing output of CalTech's periodic scripts with HTCondor dev team. OSG Release Team \u00b6 Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) Vault 1.12.1 Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 29, 2022"},{"location":"meetings/2022/TechArea20221129/#osg-technology-area-meeting-29-november-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Carl, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 29 November 2022"},{"location":"meetings/2022/TechArea20221129/#announcements","text":"BrianL traveling Nov 28 - Dec 2","title":"Announcements"},{"location":"meetings/2022/TechArea20221129/#triage-duty","text":"This week: Carl Next week: ? 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221129/#jira-as-of-monday","text":"# of tickets \u0394 State 240 +7 Open 22 -1 Selected for Dev 15 +0 In Progress 16 +0 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221129/#osg-software-team","text":"Kubernetes Hackathon: On Thursday, the default network for the Tiger Kubernetes cluster will change; people should review the services they are responsible for to make sure they will continue to function after the network change. AI (Mat): Create a variant of the pilot container that unpacks SIF files if they cannot be used directly. AI (Carl): Continue debugging COManage authentication failures on the Topology ITB instance. AI (Mat): Continue to assist Mats and HTCondor devs in getting container universe working on the OSPool, along with other pilot fixes. AI (Mat, Carl) Continue EL 9 groundwork.","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221129/#discussion","text":"GlideinWMS: Fix available for factory monitoring issue. The ITB frontends and factory have been updated; waiting for green light from Mats and Marco Mascheroni before making a release.","title":"Discussion"},{"location":"meetings/2022/TechArea20221129/#support-update","text":"Mat (FNAL/CMS): Come up with a fix or workaround for gfal2 authentication failures when using the tarball client on EL8. Mat (CalTech): Discuss errors with parsing output of CalTech's periodic scripts with HTCondor dev team.","title":"Support Update"},{"location":"meetings/2022/TechArea20221129/#osg-release-team","text":"Ready for Testing GlideinWMS 3.9.6 CVMFS 2.10.0-1.1 (and osg-oasis 19) XRootD 5.5.1-1.4 (fixes FUSE mounts via xrdfs) Vault 1.12.1 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221129/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2022/TechArea20221206/","text":"OSG Technology Area Meeting, 6 December 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 This week: Brian Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 244 +4 Open 19 -3 Selected for Dev 17 +2 In Progress 18 +2 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): EL9 support next items Create 'buildsys-*' packages (SOFTWARE-5391, SOFTWARE-5392) Build 'fetch-sources' (SOFTWARE-5393) AI (BrianL): NVidia GPU software-base image (SOFTWARE-5368) Discussion \u00b6 Time limit on GHA jobs; may want to consider paid tier for github; cross that bridge when we get there. Marco: what's the story with condor el9 support? 10.2.0 will have el9 support 10.0 LTS will not get el9 support (for reasons relating to cgroups support) el7 EOL in May 2024 will trigger updates Support Update \u00b6 NERSC (Mat, BrianL, BrianB): spoke with XRootD devs about the missing VOMS thread and he suggested compiling with print statements. Atlas is very interested. Carl: new issues: fd-71210: OSG 3.6 and OSG connection to Wayne State compute resources fd-71208: HTCondor-CE Hold jobs randomly (1/day) - Spooling input data UConn (Derek, DaveD): Debug OSDF cache selection. Was always using KC cache rather than NYC. With Dave's help, debugged it to a bad entry in the geoip DB. Richard sent an update to the upstream DB, which was accepted. OSG Release Team \u00b6 Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"December 6, 2022"},{"location":"meetings/2022/TechArea20221206/#osg-technology-area-meeting-6-december-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 6 December 2022"},{"location":"meetings/2022/TechArea20221206/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20221206/#triage-duty","text":"This week: Brian Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221206/#jira-as-of-monday","text":"JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 244 +4 Open 19 -3 Selected for Dev 17 +2 In Progress 18 +2 Dev Complete 6 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221206/#osg-software-team","text":"AI (Carl): EL9 support next items Create 'buildsys-*' packages (SOFTWARE-5391, SOFTWARE-5392) Build 'fetch-sources' (SOFTWARE-5393) AI (BrianL): NVidia GPU software-base image (SOFTWARE-5368)","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221206/#discussion","text":"Time limit on GHA jobs; may want to consider paid tier for github; cross that bridge when we get there. Marco: what's the story with condor el9 support? 10.2.0 will have el9 support 10.0 LTS will not get el9 support (for reasons relating to cgroups support) el7 EOL in May 2024 will trigger updates","title":"Discussion"},{"location":"meetings/2022/TechArea20221206/#support-update","text":"NERSC (Mat, BrianL, BrianB): spoke with XRootD devs about the missing VOMS thread and he suggested compiling with print statements. Atlas is very interested. Carl: new issues: fd-71210: OSG 3.6 and OSG connection to Wayne State compute resources fd-71208: HTCondor-CE Hold jobs randomly (1/day) - Spooling input data UConn (Derek, DaveD): Debug OSDF cache selection. Was always using KC cache rather than NYC. With Dave's help, debugged it to a bad entry in the geoip DB. Richard sent an update to the upstream DB, which was accepted.","title":"Support Update"},{"location":"meetings/2022/TechArea20221206/#osg-release-team","text":"Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221206/#discussion_1","text":"condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"Discussion"},{"location":"meetings/2022/TechArea20221213/","text":"OSG Technology Area Meeting, 13 December 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 10 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 246 +2 Open 20 +1 Selected for Dev 20 +3 In Progress 18 +0 Dev Complete 2 -2 Ready for Testing 6 +6 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon today AI (Carl): sort out COManage issues with Topology ITB; if they cannot be solved this afternoon, add a config knob to disable the feature so it does not block testing of other Topology changes AI (BrianL, Mat): investigate issues with Flux on osgdev AI (BrianL, Mat): deploy us-west-1 OSDF origin based on the Helm chart AI (Mat): Fix the OSG (not CMS) Frontera Hosted CE Doc focus Friday AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): Continue package rebuilds of OSG 3.6 packages signed with the pre-3.6 key EL9 support next items: Test yum installing software from our EL9 repos to verify that the new GPG key works Build a table of RPMs that need to be built for EL9 AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot Discussion \u00b6 Building NVidia GPU-based pilot images exposed some architectural issues with the way we use GitHub Actions for image building. Some redesign will be needed. Resource-based OSDF lookups for Topology may not be urgent since UC-Leuvain can have multiple services in a single resource. There is a problem with how duplicate \"issuer\" sections in xrootd-scitokens config are combined; Topology will need to be modified to not create issuer sections with the same name and instead combine namespaces using the same issuer in a sensible manner. Note that \"base path\" in the xrootd-scitokens config can be a comma-separated list. Code freeze for HTCondor 10.0.1 and 10.2.0 is today; this will include thinpool provisioning and the OSDF client. Partial EL9 builds (i.e. without cgroups) succeed but the UW EL9 repositories will need to be configured to not use SHA1 checksums because they are forbidden by EL9. Support Update \u00b6 Generally, Snowmass tickets should be assigned to Collaboration Support OSG Release Team \u00b6 Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"December 13, 2022"},{"location":"meetings/2022/TechArea20221213/#osg-technology-area-meeting-13-december-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Derek, Mat, TimT","title":"OSG Technology Area Meeting, 13 December 2022"},{"location":"meetings/2022/TechArea20221213/#announcements","text":"","title":"Announcements"},{"location":"meetings/2022/TechArea20221213/#triage-duty","text":"This week: Carl Next week: Mat 10 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221213/#jira-as-of-monday","text":"JIRA tickets exploding; moved a lot from IN PROG to OPEN. # of tickets \u0394 State 246 +2 Open 20 +1 Selected for Dev 20 +3 In Progress 18 +0 Dev Complete 2 -2 Ready for Testing 6 +6 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221213/#osg-software-team","text":"Kubernetes Hackathon today AI (Carl): sort out COManage issues with Topology ITB; if they cannot be solved this afternoon, add a config knob to disable the feature so it does not block testing of other Topology changes AI (BrianL, Mat): investigate issues with Flux on osgdev AI (BrianL, Mat): deploy us-west-1 OSDF origin based on the Helm chart AI (Mat): Fix the OSG (not CMS) Frontera Hosted CE Doc focus Friday AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): Continue package rebuilds of OSG 3.6 packages signed with the pre-3.6 key EL9 support next items: Test yum installing software from our EL9 repos to verify that the new GPG key works Build a table of RPMs that need to be built for EL9 AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221213/#discussion","text":"Building NVidia GPU-based pilot images exposed some architectural issues with the way we use GitHub Actions for image building. Some redesign will be needed. Resource-based OSDF lookups for Topology may not be urgent since UC-Leuvain can have multiple services in a single resource. There is a problem with how duplicate \"issuer\" sections in xrootd-scitokens config are combined; Topology will need to be modified to not create issuer sections with the same name and instead combine namespaces using the same issuer in a sensible manner. Note that \"base path\" in the xrootd-scitokens config can be a comma-separated list. Code freeze for HTCondor 10.0.1 and 10.2.0 is today; this will include thinpool provisioning and the OSDF client. Partial EL9 builds (i.e. without cgroups) succeed but the UW EL9 repositories will need to be configured to not use SHA1 checksums because they are forbidden by EL9.","title":"Discussion"},{"location":"meetings/2022/TechArea20221213/#support-update","text":"Generally, Snowmass tickets should be assigned to Collaboration Support","title":"Support Update"},{"location":"meetings/2022/TechArea20221213/#osg-release-team","text":"Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221213/#discussion_1","text":"condor 10.0.0 / with upgrading from 9->10; with gotchas: mapfile pcre2 character classes trust domain used to be derived from condor host; if trust domain changes need to re-issue tokens. THIS MAY BREAK SITES. Sites may not want to re-issue tokens; may want to go back to trust domain based on condor host. Used to specify gpus with requirements section; now there's a request-gpu keyword: end users will have to change how they're doing this.","title":"Discussion"},{"location":"meetings/2022/TechArea20221220/","text":"OSG Technology Area Meeting, 20 December 2022 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL out Dec 22 - Jan 2 Mat out Dec 23 - Dec 27 Carl out Dec 29 Triage Duty \u00b6 This week: Mat Next week: TimT 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 242 -4 Open 20 +0 Selected for Dev 21 +1 In Progress 18 +0 Dev Complete 4 +2 Ready for Testing 0 -6 Ready for Release OSG Software Team \u00b6 AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): EL9 support next items: EL9 VMU images (debug VMs with vnc). EL9 spreadsheet link is in SOFTWARE-5416; divide and conquer with Mat over the next few weeks. Note no HTCondor 10.0 or dependent pkgs for el9 release; need to wait for 10.2.0 in upcoming. A few pkgs will have version differences. AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot Discussion \u00b6 Topology contact registrations are now self-service in comanage. Mat/Carl: next couple weeks: Take a look at plates; backlog of tasks that you'd like to do but haven't had time to do. Fine as long as we're making progress on el9 and ospool. If there's no ticket make one. BrianL may add some wishlist items. Support Update \u00b6 University of Arkansas Little Rock (BrianL): help them register an ORCID account for use with the OS Registry CMS SW (BrianB, BrianL, Mat, TimT): assist them with OSG 3.5 software dependency issue Carl UConn CC* gratia issue Richard T. Jones; resolved There's an XRootD 5.5 issue; see https://osg-htc.org/docs/release/osg-36/#xrootd (will put in known issues for OSG release notes) OSG Release Team \u00b6 6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 BrianL recommends WFH if blizzard WILL NOT MEET NEXT WEEK - SEE YOU NEXT YEAR","title":"December 20, 2022"},{"location":"meetings/2022/TechArea20221220/#osg-technology-area-meeting-20-december-2022","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 20 December 2022"},{"location":"meetings/2022/TechArea20221220/#announcements","text":"BrianL out Dec 22 - Jan 2 Mat out Dec 23 - Dec 27 Carl out Dec 29","title":"Announcements"},{"location":"meetings/2022/TechArea20221220/#triage-duty","text":"This week: Mat Next week: TimT 13 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2022/TechArea20221220/#jira-as-of-monday","text":"# of tickets \u0394 State 242 -4 Open 20 +0 Selected for Dev 21 +1 In Progress 18 +0 Dev Complete 4 +2 Ready for Testing 0 -6 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2022/TechArea20221220/#osg-software-team","text":"AI (Mat): Deploy OSPool environment changes from \"main-canary\" to \"main\" and \"main-gpu\" Deploy OSPool prepare-job-hook into \"main-canary\" Add extra debugging to XRootD AI (Carl): EL9 support next items: EL9 VMU images (debug VMs with vnc). EL9 spreadsheet link is in SOFTWARE-5416; divide and conquer with Mat over the next few weeks. Note no HTCondor 10.0 or dependent pkgs for el9 release; need to wait for 10.2.0 in upcoming. A few pkgs will have version differences. AI: add resource-based OSDF lookups to Topology and the xcache container AI (BrianL): NVidia GPU osgvo-docker-pilot","title":"OSG Software Team"},{"location":"meetings/2022/TechArea20221220/#discussion","text":"Topology contact registrations are now self-service in comanage. Mat/Carl: next couple weeks: Take a look at plates; backlog of tasks that you'd like to do but haven't had time to do. Fine as long as we're making progress on el9 and ospool. If there's no ticket make one. BrianL may add some wishlist items.","title":"Discussion"},{"location":"meetings/2022/TechArea20221220/#support-update","text":"University of Arkansas Little Rock (BrianL): help them register an ORCID account for use with the OS Registry CMS SW (BrianB, BrianL, Mat, TimT): assist them with OSG 3.5 software dependency issue Carl UConn CC* gratia issue Richard T. Jones; resolved There's an XRootD 5.5 issue; see https://osg-htc.org/docs/release/osg-36/#xrootd (will put in known issues for OSG release notes)","title":"Support Update"},{"location":"meetings/2022/TechArea20221220/#osg-release-team","text":"6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2022/TechArea20221220/#discussion_1","text":"BrianL recommends WFH if blizzard WILL NOT MEET NEXT WEEK - SEE YOU NEXT YEAR","title":"Discussion"},{"location":"meetings/2023/TechArea20230103/","text":"OSG Technology Area Meeting, 3 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: BrianL (?) Next week: Carl (?) 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 208 -3 Open 33 +0 Selected for Dev 27 +2 In Progress 17 +1 Dev Complete 2 -2 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 EL9 GPG key had to be recreated again so packages have to be rebuilt. AI (Carl): Debug VMU image generation for EL9; CHTC infrastructure staff can answer questions about Kickstart AI (Carl): Rebuild EL9 packages to get signed with the new GPG key AI (Mat): Clean-up work on OSPool Container Universe project AI (TimT): Test HTCondor 10.x on EL9; this requires an EL9 VM or host in order to test cgroupv2 support, since that is based on the kernel version Discussion \u00b6 None this week Support Update \u00b6 NERSC (Mat): Provided XRootD builds with extra debug logging OSG Release Team \u00b6 6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 3, 2023"},{"location":"meetings/2023/TechArea20230103/#osg-technology-area-meeting-3-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Carl, Mat, TimT","title":"OSG Technology Area Meeting, 3 January 2023"},{"location":"meetings/2023/TechArea20230103/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230103/#triage-duty","text":"This week: BrianL (?) Next week: Carl (?) 8 (-5) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230103/#jira-as-of-monday","text":"# of tickets \u0394 State 208 -3 Open 33 +0 Selected for Dev 27 +2 In Progress 17 +1 Dev Complete 2 -2 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230103/#osg-software-team","text":"EL9 GPG key had to be recreated again so packages have to be rebuilt. AI (Carl): Debug VMU image generation for EL9; CHTC infrastructure staff can answer questions about Kickstart AI (Carl): Rebuild EL9 packages to get signed with the new GPG key AI (Mat): Clean-up work on OSPool Container Universe project AI (TimT): Test HTCondor 10.x on EL9; this requires an EL9 VM or host in order to test cgroupv2 support, since that is based on the kernel version","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230103/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230103/#support-update","text":"NERSC (Mat): Provided XRootD builds with extra debug logging","title":"Support Update"},{"location":"meetings/2023/TechArea20230103/#osg-release-team","text":"6 RFT; and of those 2 are condor, which we'll ignore; the rest are el9. Will do a release this Thursday, mainly for re-signed rebuilds for old gpgkey. Untagged XRootD. Ready for Testing osg-scitokens-mapfile 11 Support HEPCloud factory XRootD 5.5.1 Fixes critical issue with XRootD FUSE mounts via xrdfs CVMFS 2.10.0 Release Notes for CernVM-FS 2.10.0 GlideinWMS 3.9.6 adds token (and hybrid) support for Clouds (AWS/GCE) XCache 3.3.0 Removed X.509 proxy requirement for an unauthenticated stash-cache instance Vault 1.12.1 includes a fix to prevent a potential denial of service attack for HA installations HTCondor 10.0.0 Please consult the upgrade guide for major differences Upgrading from an 9.0 LTS version to an 10.0 LTS version of HTCondor In particular, consult the second section of things to be aware of when upgrading Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230103/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230117/","text":"OSG Technology Area Meeting, 17 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 215 +1 Open 38 +5 Selected for Dev 28 -1 In Progress 17 +0 Dev Complete 4 +2 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 AI (Carl): Release python-scitokens for IGWN AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes Discussion \u00b6 EL9 VMU images are available Rocky 8 image generation failed because the upstream ISO is gone Marco: GlideinWMS 3.10.1 is available; waiting for OSG Software Team to release it into their repos Support Update \u00b6 BNL (Brian): Provided XRootD builds with extra debug logging MWT2 (Brian): CE was backed up with high RecentDaemonCoreDutyCycle and was backed up handling reads. Forks were taking 0.1s so we turned down SCHEDD_QUERY_WORKERS down to 2 and it eventually caught back up. Purdue (Brian): helped Colby troubleshoot issues with cred transfer to the EP OSG Release Team \u00b6 Ready for Testing vo-client 128 Update HCC, GLOW, and OSG VOMS certificates Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 17, 2023"},{"location":"meetings/2023/TechArea20230117/#osg-technology-area-meeting-17-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Tim","title":"OSG Technology Area Meeting, 17 January 2023"},{"location":"meetings/2023/TechArea20230117/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230117/#triage-duty","text":"This week: Mat Next week: Tim 7 (-1) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230117/#jira-as-of-monday","text":"# of tickets \u0394 State 215 +1 Open 38 +5 Selected for Dev 28 -1 In Progress 17 +0 Dev Complete 4 +2 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230117/#osg-software-team","text":"AI (Carl): Release python-scitokens for IGWN AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230117/#discussion","text":"EL9 VMU images are available Rocky 8 image generation failed because the upstream ISO is gone Marco: GlideinWMS 3.10.1 is available; waiting for OSG Software Team to release it into their repos","title":"Discussion"},{"location":"meetings/2023/TechArea20230117/#support-update","text":"BNL (Brian): Provided XRootD builds with extra debug logging MWT2 (Brian): CE was backed up with high RecentDaemonCoreDutyCycle and was backed up handling reads. Forks were taking 0.1s so we turned down SCHEDD_QUERY_WORKERS down to 2 and it eventually caught back up. Purdue (Brian): helped Colby troubleshoot issues with cred transfer to the EP","title":"Support Update"},{"location":"meetings/2023/TechArea20230117/#osg-release-team","text":"Ready for Testing vo-client 128 Update HCC, GLOW, and OSG VOMS certificates Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230117/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230124/","text":"OSG Technology Area Meeting, 24 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: Tim 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 217 +2 Open 42 +4 Selected for Dev 29 +1 In Progress 17 +0 Dev Complete 5 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): Release python-scitokens for IGWN AI (Carl): Work with dev team (?) to figure out EL9 VM kernel panics AI (Mat): Release glideinwms AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes Discussion \u00b6 None this week Support Update \u00b6 BNL (Brian): discussed weighted slots and GRACC/WLCG accounting OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 24, 2023"},{"location":"meetings/2023/TechArea20230124/#osg-technology-area-meeting-24-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 24 January 2023"},{"location":"meetings/2023/TechArea20230124/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230124/#triage-duty","text":"This week: Mat Next week: Tim 10 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230124/#jira-as-of-monday","text":"# of tickets \u0394 State 217 +2 Open 42 +4 Selected for Dev 29 +1 In Progress 17 +0 Dev Complete 5 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230124/#osg-software-team","text":"AI (Carl): Release python-scitokens for IGWN AI (Carl): Work with dev team (?) to figure out EL9 VM kernel panics AI (Mat): Release glideinwms AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): Rename condor_stash_plugin to condor_osdf_plugin AI (Mat): Lancium provisioner backfill container changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230124/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230124/#support-update","text":"BNL (Brian): discussed weighted slots and GRACC/WLCG accounting","title":"Support Update"},{"location":"meetings/2023/TechArea20230124/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230124/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230131/","text":"OSG Technology Area Meeting, 31 January 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: Tim Next week: BrianL (?) 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 209 -8 Open 42 +0 Selected for Dev 33 +4 In Progress 18 +1 Dev Complete 7 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): add option to filter OSPool project user map by login group AI (Carl): Kick off appropriate package set tests for EL9 AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile work AI (Mat): Lancium provisioner backfill container changes Discussion \u00b6 GlideinWMS 3.10.1 is in use in the ITB at CERN; this should be sufficient testing to add it to the OSG release. Question about how an HTCondor client validates the server when using IDTOKENS; Mat says the client doesn't have a copy of the IDTOKEN signing key so it can't use that method and it must use something else like FS or SSL. Reminder: HTCondor will be built for EL9 only in 3.6-upcoming because the LTS series 10.0 does not support EL9. Support Update \u00b6 BNL (Brian): further discussion of weighted slots and GRACC/WLCG accounting OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"January 31, 2023"},{"location":"meetings/2023/TechArea20230131/#osg-technology-area-meeting-31-january-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Mat, Tim","title":"OSG Technology Area Meeting, 31 January 2023"},{"location":"meetings/2023/TechArea20230131/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230131/#triage-duty","text":"This week: Tim Next week: BrianL (?) 9 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230131/#jira-as-of-monday","text":"# of tickets \u0394 State 209 -8 Open 42 +0 Selected for Dev 33 +4 In Progress 18 +1 Dev Complete 7 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230131/#osg-software-team","text":"Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): add option to filter OSPool project user map by login group AI (Carl): Kick off appropriate package set tests for EL9 AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile work AI (Mat): Lancium provisioner backfill container changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230131/#discussion","text":"GlideinWMS 3.10.1 is in use in the ITB at CERN; this should be sufficient testing to add it to the OSG release. Question about how an HTCondor client validates the server when using IDTOKENS; Mat says the client doesn't have a copy of the IDTOKEN signing key so it can't use that method and it must use something else like FS or SSL. Reminder: HTCondor will be built for EL9 only in 3.6-upcoming because the LTS series 10.0 does not support EL9.","title":"Discussion"},{"location":"meetings/2023/TechArea20230131/#support-update","text":"BNL (Brian): further discussion of weighted slots and GRACC/WLCG accounting","title":"Support Update"},{"location":"meetings/2023/TechArea20230131/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230131/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230207/","text":"OSG Technology Area Meeting, 7 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Marco, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: BrianL Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 210 +1 Open 38 -4 Selected for Dev 32 -1 In Progress 18 +0 Dev Complete 4 -3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): Kick off appropriate package set tests for EL9 AI (Carl): osg-build branch protection AI (Carl): document more Git opinions AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile + Topology work Florida requests a backported fix for https://github.com/xrootd/xrootd/issues/1874 . We've got a lot of patches, should we cut a new build with reduced patches? Relatedly, XRootD 5.5.2 has been released; the software team should patch that version instead of 5.5.1. - x509-scitokens-issuer, which is in osg-contrib, needs to be rebuilt to sign it with the current OSG 3.6 GPG key. Kubernetes Hackathon: - BrianL: PATh Facility Origin - Mat: ITB EP with a GPU for testing container universe changes Discussion \u00b6 XRootD developers have requested that the OSG SW team clearly indicate in XRootD packages that they are the OSG versions and not upstream; there is a text file in the XRootD packages that can be used for that purpose. Support Update \u00b6 BNL (Brian): will hold off on weighted slots work until this sorted out at the WLCG level OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"February 7, 2023"},{"location":"meetings/2023/TechArea20230207/#osg-technology-area-meeting-7-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Marco, Mat, Tim","title":"OSG Technology Area Meeting, 7 February 2023"},{"location":"meetings/2023/TechArea20230207/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230207/#triage-duty","text":"This week: BrianL Next week: Carl 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230207/#jira-as-of-monday","text":"# of tickets \u0394 State 210 +1 Open 38 -4 Selected for Dev 32 -1 In Progress 18 +0 Dev Complete 4 -3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230207/#osg-software-team","text":"Reminder: triage duty responsibilities . New duties include Topology data and COManage site contact reviews. AI (Carl): Kick off appropriate package set tests for EL9 AI (Carl): osg-build branch protection AI (Carl): document more Git opinions AI (Mat): Continue work on container universe changes for the OSPool AI (Mat): XRootD mapfile + Topology work Florida requests a backported fix for https://github.com/xrootd/xrootd/issues/1874 . We've got a lot of patches, should we cut a new build with reduced patches? Relatedly, XRootD 5.5.2 has been released; the software team should patch that version instead of 5.5.1. - x509-scitokens-issuer, which is in osg-contrib, needs to be rebuilt to sign it with the current OSG 3.6 GPG key. Kubernetes Hackathon: - BrianL: PATh Facility Origin - Mat: ITB EP with a GPU for testing container universe changes","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230207/#discussion","text":"XRootD developers have requested that the OSG SW team clearly indicate in XRootD packages that they are the OSG versions and not upstream; there is a text file in the XRootD packages that can be used for that purpose.","title":"Discussion"},{"location":"meetings/2023/TechArea20230207/#support-update","text":"BNL (Brian): will hold off on weighted slots work until this sorted out at the WLCG level","title":"Support Update"},{"location":"meetings/2023/TechArea20230207/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230207/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230214/","text":"OSG Technology Area Meeting, 14 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Derek, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 This week: Carl Next week: Mat 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 218 +8 Open 40 +2 Selected for Dev 26 -6 In Progress 17 -1 Dev Complete 8 +4 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Carl): Write tests for OSG-Build branch safety. AI (Carl): Continue work on EL9 builds AI (Mat): Build new VO-Client for second Fermilab cert change. AI (Brian): Investigate rrdtool for EL9. AI (Mat): Continue work on Topology endpoints for grid-mapfiles. Discussion \u00b6 Tim will release HTCondor-CE 6 which works with HTCondor 10 this week; HTCondor 10.3.0 expected next week Group write permissions for the PATh origin are broken due to xrootd-multiuser not having the right group permission to traverse the directory tree to enter into private directories. A potential workaround is to make the parent directories world-traverseable but not world-readable. We would have to remind users that they need to make their files not world-readable and also investigate what permissions xrootd gives newly written files. A long term solution is to modify xrootd-multiuser to set the process's supplementary groups before accessing files in group directories. Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet Discussion \u00b6 None this week","title":"February 14, 2023"},{"location":"meetings/2023/TechArea20230214/#osg-technology-area-meeting-14-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Brian, Carl, Derek, Mat, Tim","title":"OSG Technology Area Meeting, 14 February 2023"},{"location":"meetings/2023/TechArea20230214/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230214/#triage-duty","text":"This week: Carl Next week: Mat 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230214/#jira-as-of-monday","text":"# of tickets \u0394 State 218 +8 Open 40 +2 Selected for Dev 26 -6 In Progress 17 -1 Dev Complete 8 +4 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230214/#osg-software-team","text":"AI (Carl): Write tests for OSG-Build branch safety. AI (Carl): Continue work on EL9 builds AI (Mat): Build new VO-Client for second Fermilab cert change. AI (Brian): Investigate rrdtool for EL9. AI (Mat): Continue work on Topology endpoints for grid-mapfiles.","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230214/#discussion","text":"Tim will release HTCondor-CE 6 which works with HTCondor 10 this week; HTCondor 10.3.0 expected next week Group write permissions for the PATh origin are broken due to xrootd-multiuser not having the right group permission to traverse the directory tree to enter into private directories. A potential workaround is to make the parent directories world-traverseable but not world-readable. We would have to remind users that they need to make their files not world-readable and also investigate what permissions xrootd gives newly written files. A long term solution is to modify xrootd-multiuser to set the process's supplementary groups before accessing files in group directories.","title":"Discussion"},{"location":"meetings/2023/TechArea20230214/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230214/#osg-release-team","text":"Ready for Testing htvault-config 1.14 Add auditlog option to move the audit log to a different location Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230214/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230221/","text":"OSG Technology Area Meeting, 21 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 This week: Mat Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon Plan osdf-origin chart pipeline Implement automatic deployment re-roll in the origin chart (https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments) Pick CHTC LDAP replica static IP EL 9 AI (BrianL): rebuild osg-ce without Squid dependency AI (BrianL): build voms for EL9 AI (Mat): XRootD mapfile + Topology status? AI (Mat): Upgrade Topology Webapp to EL8 and Python 3.9 Discussion \u00b6 Mat and BrianL will discuss cleaning up old OSG images on Harbor Harbor upgrade planned for the next few weeks OSG Build Tools do not work on Fedora 37; there is a Docker image available as an alternative to running the software natively GlideinWMS release candidate planned for next week Support Update \u00b6 None this week OSG Release Team \u00b6 Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN) Discussion \u00b6 None this week","title":"February 21, 2023"},{"location":"meetings/2023/TechArea20230221/#osg-technology-area-meeting-21-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 21 February 2023"},{"location":"meetings/2023/TechArea20230221/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230221/#triage-duty","text":"This week: Mat Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230221/#jira-as-of-monday","text":"# of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230221/#osg-software-team","text":"Kubernetes Hackathon Plan osdf-origin chart pipeline Implement automatic deployment re-roll in the origin chart (https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments) Pick CHTC LDAP replica static IP EL 9 AI (BrianL): rebuild osg-ce without Squid dependency AI (BrianL): build voms for EL9 AI (Mat): XRootD mapfile + Topology status? AI (Mat): Upgrade Topology Webapp to EL8 and Python 3.9","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230221/#discussion","text":"Mat and BrianL will discuss cleaning up old OSG images on Harbor Harbor upgrade planned for the next few weeks OSG Build Tools do not work on Fedora 37; there is a Docker image available as an alternative to running the software natively GlideinWMS release candidate planned for next week","title":"Discussion"},{"location":"meetings/2023/TechArea20230221/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230221/#osg-release-team","text":"Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN)","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230221/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230228/","text":"OSG Technology Area Meeting, 28 February 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: TimT Next week: BrianL 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Software team members should pull in others to help out as soon as possible. Jira (as of Monday) \u00b6 # of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Critical bug in gratia-probe-htcondor-ce-2.8.1 requires an expedited release (SOFTWARE-5504) EL 9 AI (BrianL): investigate Slurm failures AI (Mat): Verify EL9 tests for XRootD-related package sets Give up on voms-proxy-direct ? This will allow OSG to drop packaging voms-clients; users will still be able to take voms clients from EPEL Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) AI (BrianL, Mat, TimT): Meet to plan OSG 3.7 repository structure Discussion \u00b6 GlideinWMS 3.10.2 release candidate planned for next week Support Update \u00b6 IGWN interested in setting up their own central-syslog service; BrianL has pointed them at the OSPool instance OSG Release Team \u00b6 Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN) Discussion \u00b6 None this week","title":"OSG Technology Area Meeting, 28 February 2023"},{"location":"meetings/2023/TechArea20230228/#osg-technology-area-meeting-28-february-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 28 February 2023"},{"location":"meetings/2023/TechArea20230228/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230228/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: TimT Next week: BrianL 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Software team members should pull in others to help out as soon as possible.","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230228/#jira-as-of-monday","text":"# of tickets \u0394 State 220 +2 Open 37 -3 Selected for Dev 27 +1 In Progress 10 -7 Dev Complete 10 +2 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230228/#osg-software-team","text":"Critical bug in gratia-probe-htcondor-ce-2.8.1 requires an expedited release (SOFTWARE-5504) EL 9 AI (BrianL): investigate Slurm failures AI (Mat): Verify EL9 tests for XRootD-related package sets Give up on voms-proxy-direct ? This will allow OSG to drop packaging voms-clients; users will still be able to take voms clients from EPEL Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) AI (BrianL, Mat, TimT): Meet to plan OSG 3.7 repository structure","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230228/#discussion","text":"GlideinWMS 3.10.2 release candidate planned for next week","title":"Discussion"},{"location":"meetings/2023/TechArea20230228/#support-update","text":"IGWN interested in setting up their own central-syslog service; BrianL has pointed them at the OSPool instance","title":"Support Update"},{"location":"meetings/2023/TechArea20230228/#osg-release-team","text":"Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN)","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230228/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230314/","text":"OSG Technology Area Meeting, 14 March 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 BrianL out Thursday March 16 and Friday March 17 TimT out Monday, March 20 through Friday, March 31. (May work remotely on March 20 and 21.) Mat out Thursday, March 30 through Monday, April 17. Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: Mat Next week: BrianL 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 223 +3 Open 38 -1 Selected for Dev 27 +0 In Progress 19 +0 Dev Complete 9 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 EL 9 AI (BrianL): investigate Slurm failures AI (BrianL): rebuild upcoming packages into main AI (BrianL): build osg-ca-certs-experimental AI (Mat): build XRootD + kick off EL9 VMU tests Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) Other AI (Mat): Use the OSDF Client shipped with HTCondor in OSPool pilots Discussion \u00b6 Marco: Final GlideinWMS release candidate is expected this week. Notable changes: Fixes for OSG autoconf script The tarball to use for CVMFSEXEC will be configurable Fixes error in configuring token lifetime Horst at OU has successfully installed an EL9 CE; he has reported some documentation issues, which BrianL will review Support Update \u00b6 BrianL (Caltech): Gratia probe failures were due to incorrect directory permissions at the site. This is not the first time such an error has occurred; the Gratia probe should detect this issue and log and/or refuse to start (instead of just discarding records). BrianL will discuss it with Derek. BrianL: A site in India stopped receiving pilots from Fermilab; they reinstalled their CE and need assistance with registration and using token-based pilots OSG Release Team \u00b6 Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN) Discussion \u00b6 None this week","title":"March 14, 2023"},{"location":"meetings/2023/TechArea20230314/#osg-technology-area-meeting-14-march-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 14 March 2023"},{"location":"meetings/2023/TechArea20230314/#announcements","text":"BrianL out Thursday March 16 and Friday March 17 TimT out Monday, March 20 through Friday, March 31. (May work remotely on March 20 and 21.) Mat out Thursday, March 30 through Monday, April 17.","title":"Announcements"},{"location":"meetings/2023/TechArea20230314/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: Mat Next week: BrianL 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230314/#jira-as-of-monday","text":"# of tickets \u0394 State 223 +3 Open 38 -1 Selected for Dev 27 +0 In Progress 19 +0 Dev Complete 9 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230314/#osg-software-team","text":"EL 9 AI (BrianL): investigate Slurm failures AI (BrianL): rebuild upcoming packages into main AI (BrianL): build osg-ca-certs-experimental AI (Mat): build XRootD + kick off EL9 VMU tests Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (BrianL): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) Other AI (Mat): Use the OSDF Client shipped with HTCondor in OSPool pilots","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230314/#discussion","text":"Marco: Final GlideinWMS release candidate is expected this week. Notable changes: Fixes for OSG autoconf script The tarball to use for CVMFSEXEC will be configurable Fixes error in configuring token lifetime Horst at OU has successfully installed an EL9 CE; he has reported some documentation issues, which BrianL will review","title":"Discussion"},{"location":"meetings/2023/TechArea20230314/#support-update","text":"BrianL (Caltech): Gratia probe failures were due to incorrect directory permissions at the site. This is not the first time such an error has occurred; the Gratia probe should detect this issue and log and/or refuse to start (instead of just discarding records). BrianL will discuss it with Derek. BrianL: A site in India stopped receiving pilots from Fermilab; they reinstalled their CE and need assistance with registration and using token-based pilots","title":"Support Update"},{"location":"meetings/2023/TechArea20230314/#osg-release-team","text":"Ready for Testing hosted-ce-tools 1.0 HTCondor-CE 6.0.0 HTCondor 10.0.1 Upcoming: HTCondor 10.2.0 Ready for Release vo-client v130 (Fermilab voms2 DN)","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230314/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230328/","text":"OSG Technology Area Meeting, 28 March 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Marco Announcements \u00b6 TimT out Monday, March 20 through Friday, March 31. Mat out Thursday, March 30 through Monday, April 17. Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: Mat and BrianL Next week: BrianL 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 225 +1 Open 39 -1 Selected for Dev 28 -2 In Progress 22 -1 Dev Complete 11 +2 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 Marco: Testing release candidate; The last remaining PR before a release is to allow configuring location of CVMFSEXEC tarball It is no longer possible to use an EL 7 machine for development because because the git pre-commit hooks do not work on Python 3.6; however, GlideinWMS will continue to run on EL 7. EL 9 AI (BrianL): investigate Slurm failures The Slurm service may be failing to start but the tests are not catching it soon enough. AI (Mat): build osg-ca-certs-experimental AI (BrianL): enable EL9 tests in VMU Gratia probe release for AP bugs: docs should be fixed to indicate that all history files should be moved from quarantine Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (JeffT?): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325) Discussion \u00b6 None this week Support Update \u00b6 Oklahoma (BrianL): got their CE up and running! MWT2 (BrianL): helped troubleshoot HTCondor-CE -> HTCondor submission issues. Their JOB_ROUTER_SCHEDD2_SPOOL CE config didn't match their custom local HTCondor SPOOL config UCLouvain (Mat): Virgo pilots failing to read protected LIGO data; need assistance from a pilot expert OSG Release Team \u00b6 Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0 Discussion \u00b6 None this week","title":"March 28, 2023"},{"location":"meetings/2023/TechArea20230328/#osg-technology-area-meeting-28-march-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Marco","title":"OSG Technology Area Meeting, 28 March 2023"},{"location":"meetings/2023/TechArea20230328/#announcements","text":"TimT out Monday, March 20 through Friday, March 31. Mat out Thursday, March 30 through Monday, April 17.","title":"Announcements"},{"location":"meetings/2023/TechArea20230328/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: Mat and BrianL Next week: BrianL 7 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230328/#jira-as-of-monday","text":"# of tickets \u0394 State 225 +1 Open 39 -1 Selected for Dev 28 -2 In Progress 22 -1 Dev Complete 11 +2 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230328/#osg-software-team","text":"Marco: Testing release candidate; The last remaining PR before a release is to allow configuring location of CVMFSEXEC tarball It is no longer possible to use an EL 7 machine for development because because the git pre-commit hooks do not work on Python 3.6; however, GlideinWMS will continue to run on EL 7. EL 9 AI (BrianL): investigate Slurm failures The Slurm service may be failing to start but the tests are not catching it soon enough. AI (Mat): build osg-ca-certs-experimental AI (BrianL): enable EL9 tests in VMU Gratia probe release for AP bugs: docs should be fixed to indicate that all history files should be moved from quarantine Lancium provisioner AI (Mat): Allow advertising arbitrary startd attrs (SOFTWARE-5324) AI (JeffT?): Add job to osgvo-docker-pilot GHA to kick off Lancium rebuilds (SOFTWARE-5325)","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230328/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230328/#support-update","text":"Oklahoma (BrianL): got their CE up and running! MWT2 (BrianL): helped troubleshoot HTCondor-CE -> HTCondor submission issues. Their JOB_ROUTER_SCHEDD2_SPOOL CE config didn't match their custom local HTCondor SPOOL config UCLouvain (Mat): Virgo pilots failing to read protected LIGO data; need assistance from a pilot expert","title":"Support Update"},{"location":"meetings/2023/TechArea20230328/#osg-release-team","text":"Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230328/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230404/","text":"OSG Technology Area Meeting, 28 March 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, TimT Announcements \u00b6 Mat out Thursday, March 30 through Monday, April 17. Triage Duty \u00b6 Triage duty shifts changing to Tue-Mon This week: BrianL Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 224 -1 Open 41 +2 Selected for Dev 26 -2 In Progress 19 -3 Dev Complete 9 -2 Ready for Testing 1 +0 Ready for Release OSG Software Team \u00b6 AI (BrianL): build new XCache AI (BrianL): build patched XRootD AI (BrianL): investigate WN client tarball failures; eliminate remaining Python 2 dependencies Discussion \u00b6 None this week DevOps \u00b6 Moving python-scitokens to EPEL: https://bugzilla.redhat.com/show_bug.cgi?id=2181686 Support Update \u00b6 (Derek) OSG pilots checking for retired CVMFS repo, desdm.osgstorage.org, causing errors in site logs. Fixed the check. (Derek) CVMFS Singularity Sync patch to fix new OCI type being used by ubuntu and other newer images. (Derek) CVMFS indexing is failing for FNAL's nova, some issue with offsite access to data there. OSG Release Team \u00b6 Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0 Discussion \u00b6 None this week","title":"April 4, 2023"},{"location":"meetings/2023/TechArea20230404/#osg-technology-area-meeting-28-march-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, TimT","title":"OSG Technology Area Meeting, 28 March 2023"},{"location":"meetings/2023/TechArea20230404/#announcements","text":"Mat out Thursday, March 30 through Monday, April 17.","title":"Announcements"},{"location":"meetings/2023/TechArea20230404/#triage-duty","text":"Triage duty shifts changing to Tue-Mon This week: BrianL Next week: TimT 8 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230404/#jira-as-of-monday","text":"# of tickets \u0394 State 224 -1 Open 41 +2 Selected for Dev 26 -2 In Progress 19 -3 Dev Complete 9 -2 Ready for Testing 1 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230404/#osg-software-team","text":"AI (BrianL): build new XCache AI (BrianL): build patched XRootD AI (BrianL): investigate WN client tarball failures; eliminate remaining Python 2 dependencies","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230404/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230404/#devops","text":"Moving python-scitokens to EPEL: https://bugzilla.redhat.com/show_bug.cgi?id=2181686","title":"DevOps"},{"location":"meetings/2023/TechArea20230404/#support-update","text":"(Derek) OSG pilots checking for retired CVMFS repo, desdm.osgstorage.org, causing errors in site logs. Fixed the check. (Derek) CVMFS Singularity Sync patch to fix new OCI type being used by ubuntu and other newer images. (Derek) CVMFS indexing is failing for FNAL's nova, some issue with offsite access to data there.","title":"Support Update"},{"location":"meetings/2023/TechArea20230404/#osg-release-team","text":"Ready for Testing EL9 packages! AI (BrianL): review packages vs spreadsheet AI (BrianL): write release notes Ready for Release osdf-client 6.10.0","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230404/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230418/","text":"OSG Technology Area Meeting, 18 April 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 228 -1 Open 42 +0 Selected for Dev 29 +2 In Progress 19 +0 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Request new gfactory-2 IGTF certificate AI (Mat): investigate OSDF plugin failures (INF-913) AI (BrianL): add glidein IDTOKEN support to Hosted CE AI (Mat): request new IGTF gfactory-2 cert Kubernetes Hackathon today AI (Mat): Expanse upgrade, locking down firewalls AI (BrianL): make progress on TACC remote flux AI (Mat): Assist Fabio in debugging Helm / Flux v2 on Nautilus Discussion \u00b6 None this week Support Update \u00b6 AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"April 18, 2023"},{"location":"meetings/2023/TechArea20230418/#osg-technology-area-meeting-18-april-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, TimT","title":"OSG Technology Area Meeting, 18 April 2023"},{"location":"meetings/2023/TechArea20230418/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230418/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230418/#jira-as-of-monday","text":"# of tickets \u0394 State 228 -1 Open 42 +0 Selected for Dev 29 +2 In Progress 19 +0 Dev Complete 7 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230418/#osg-software-team","text":"AI (Mat): Request new gfactory-2 IGTF certificate AI (Mat): investigate OSDF plugin failures (INF-913) AI (BrianL): add glidein IDTOKEN support to Hosted CE AI (Mat): request new IGTF gfactory-2 cert Kubernetes Hackathon today AI (Mat): Expanse upgrade, locking down firewalls AI (BrianL): make progress on TACC remote flux AI (Mat): Assist Fabio in debugging Helm / Flux v2 on Nautilus","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230418/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230418/#support-update","text":"AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs","title":"Support Update"},{"location":"meetings/2023/TechArea20230418/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230418/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230418/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230509/","text":"OSG Technology Area Meeting, 9 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat (?) Next week: TimT (?) 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 228 +2 Open 38 -1 Selected for Dev 30 +0 In Progress 23 +0 Dev Complete 7 +3 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 AI (Mat): Flux v1 -> v2 transition AI (BrianL): ticket review and planning work for Matthew Discussion \u00b6 None this week Support Update \u00b6 AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 9, 2023"},{"location":"meetings/2023/TechArea20230509/#osg-technology-area-meeting-9-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 9 May 2023"},{"location":"meetings/2023/TechArea20230509/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230509/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat (?) Next week: TimT (?) 11 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230509/#jira-as-of-monday","text":"# of tickets \u0394 State 228 +2 Open 38 -1 Selected for Dev 30 +0 In Progress 23 +0 Dev Complete 7 +3 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230509/#osg-software-team","text":"AI (Mat): Flux v1 -> v2 transition AI (BrianL): ticket review and planning work for Matthew","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230509/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230509/#support-update","text":"AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs","title":"Support Update"},{"location":"meetings/2023/TechArea20230509/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230509/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230509/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230516/","text":"OSG Technology Area Meeting, 16 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Tim Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 +9 Open 40 +2 Selected for Dev 26 -4 In Progress 25 +2 Dev Complete 8 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): XCache and osg-xrootd mapfile-related releases Kubernetes Hackathon AI (Mat): Flux v1 -> v2 transition AI (BrianL): review Helm chart CI, investigate path-facility-admin RBAC issues and Expanse user namespace issues Discussion \u00b6 The script that tests upgrades from HTCondor 9 to 10 needs improvements; there will be an updated release soon. The release of HTCondor 10.0.4 is waiting for scitokens-cpp 1.0.2 to be released. Derek and Fabio are debugging why the open and close times for transfers are the same; this leads to reporting an infinite amount of bandwidth since the reported transfer time is zero Support Update \u00b6 AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs Fermilab (BrianL): WLCG folks are worried about accounting for VO information with tokens. (OSG SW and GRACC look at the SciToken issuer.) Steve Timm ran into a problem where multiple VOs were using a single AP where DAGMan-created jobs don't have any of the auth token attributes. There is a workaround since Steve's jobs still have VOMS attributes but passing the token attributes requires HTCondor changes. SDSC (Mat): The OSDF authfile generator service was renamed and the documentation wasn't updated with the new paths; Mat made a PR to fix the documentation. DevOps \u00b6 APEL accounting updates for new HEPScore benchmark. Derek will try to schedule meetings with USCMS and USATLAS groups to present the (minor) changes to topology. OSDF client director, Derek needs to review. OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 16, 2023"},{"location":"meetings/2023/TechArea20230516/#osg-technology-area-meeting-16-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Tim","title":"OSG Technology Area Meeting, 16 May 2023"},{"location":"meetings/2023/TechArea20230516/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230516/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 9 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230516/#jira-as-of-monday","text":"# of tickets \u0394 State 237 +9 Open 40 +2 Selected for Dev 26 -4 In Progress 25 +2 Dev Complete 8 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230516/#osg-software-team","text":"Release AI (Mat): XCache and osg-xrootd mapfile-related releases Kubernetes Hackathon AI (Mat): Flux v1 -> v2 transition AI (BrianL): review Helm chart CI, investigate path-facility-admin RBAC issues and Expanse user namespace issues","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230516/#discussion","text":"The script that tests upgrades from HTCondor 9 to 10 needs improvements; there will be an updated release soon. The release of HTCondor 10.0.4 is waiting for scitokens-cpp 1.0.2 to be released. Derek and Fabio are debugging why the open and close times for transfers are the same; this leads to reporting an infinite amount of bandwidth since the reported transfer time is zero","title":"Discussion"},{"location":"meetings/2023/TechArea20230516/#support-update","text":"AMNH (BrianL): issues mounting CVMFS, no luck getting debug logs Fermilab (BrianL): WLCG folks are worried about accounting for VO information with tokens. (OSG SW and GRACC look at the SciToken issuer.) Steve Timm ran into a problem where multiple VOs were using a single AP where DAGMan-created jobs don't have any of the auth token attributes. There is a workaround since Steve's jobs still have VOMS attributes but passing the token attributes requires HTCondor changes. SDSC (Mat): The OSDF authfile generator service was renamed and the documentation wasn't updated with the new paths; Mat made a PR to fix the documentation.","title":"Support Update"},{"location":"meetings/2023/TechArea20230516/#devops","text":"APEL accounting updates for new HEPScore benchmark. Derek will try to schedule meetings with USCMS and USATLAS groups to present the (minor) changes to topology. OSDF client director, Derek needs to review.","title":"DevOps"},{"location":"meetings/2023/TechArea20230516/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230516/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230523/","text":"OSG Technology Area Meeting, 16 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 New OSG Software Team member, Matthew Westphall, started yesterday! Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: ??? 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 +0 Open 39 -1 Selected for Dev 27 +1 In Progress 25 +0 Dev Complete 7 -1 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 AI (BrianL): create a Kanban board for Matthew AI (Mat): help Matthew set up Subversion access AI (Mat): XRootD patch for token username claims (SOFTWARE-5541) AI (Matthew): Remove python2 packaging deps from osg-update-vos (SOFTWARE-5545) Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 23, 2023"},{"location":"meetings/2023/TechArea20230523/#osg-technology-area-meeting-16-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 16 May 2023"},{"location":"meetings/2023/TechArea20230523/#announcements","text":"New OSG Software Team member, Matthew Westphall, started yesterday!","title":"Announcements"},{"location":"meetings/2023/TechArea20230523/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: ??? 9 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230523/#jira-as-of-monday","text":"# of tickets \u0394 State 237 +0 Open 39 -1 Selected for Dev 27 +1 In Progress 25 +0 Dev Complete 7 -1 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230523/#osg-software-team","text":"AI (BrianL): create a Kanban board for Matthew AI (Mat): help Matthew set up Subversion access AI (Mat): XRootD patch for token username claims (SOFTWARE-5541) AI (Matthew): Remove python2 packaging deps from osg-update-vos (SOFTWARE-5545)","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230523/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230523/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230523/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230523/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230523/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230530/","text":"OSG Technology Area Meeting, 30 May 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT Announcements \u00b6 PATh mid-point NSF review this Thursday and Friday Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: BrianL 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 planning meeting this morning Kubernetes hackathon this afternoon! AI (MatS): Create OSDF origin for NIH public data AI (MatS): Migrate \"osg\" namespace to Flux V2 AI (MattW): Work with TimT to build RPMs for the new IGTF CA cert bundle Discussion \u00b6 UFlorida Research Computing policy no longer allows them to install software out of osg-testing, so they won't be able to provide community testing for XRootD for us anymore; BrianL will ask OU if they would be available for this in the future Support Update \u00b6 IGWN (TimT): IGWN is setting up an HTCondor AP; TimT will contact Stefano for a status update DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"May 30, 2023"},{"location":"meetings/2023/TechArea20230530/#osg-technology-area-meeting-30-may-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 30 May 2023"},{"location":"meetings/2023/TechArea20230530/#announcements","text":"PATh mid-point NSF review this Thursday and Friday","title":"Announcements"},{"location":"meetings/2023/TechArea20230530/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: BrianL 7 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230530/#jira-as-of-monday","text":"# of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230530/#osg-software-team","text":"OSG 3.7 planning meeting this morning Kubernetes hackathon this afternoon! AI (MatS): Create OSDF origin for NIH public data AI (MatS): Migrate \"osg\" namespace to Flux V2 AI (MattW): Work with TimT to build RPMs for the new IGTF CA cert bundle","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230530/#discussion","text":"UFlorida Research Computing policy no longer allows them to install software out of osg-testing, so they won't be able to provide community testing for XRootD for us anymore; BrianL will ask OU if they would be available for this in the future","title":"Discussion"},{"location":"meetings/2023/TechArea20230530/#support-update","text":"IGWN (TimT): IGWN is setting up an HTCondor AP; TimT will contact Stefano for a status update","title":"Support Update"},{"location":"meetings/2023/TechArea20230530/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230530/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230530/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230606/","text":"OSG Technology Area Meeting, 6 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks (targeting initial release for early/mid August) HTCondor repo planning meeting this Friday AI (Mat): Prep koji tags + targets AI (Matt, Mat): Koji package signing AI (Mat): Koji policy Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 6, 2023"},{"location":"meetings/2023/TechArea20230606/#osg-technology-area-meeting-6-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 6 June 2023"},{"location":"meetings/2023/TechArea20230606/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230606/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230606/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230606/#osg-software-team","text":"OSG 3.7 tasks (targeting initial release for early/mid August) HTCondor repo planning meeting this Friday AI (Mat): Prep koji tags + targets AI (Matt, Mat): Koji package signing AI (Mat): Koji policy","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230606/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230606/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230606/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230606/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230606/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230613/","text":"OSG Technology Area Meeting, 13 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT Announcements \u00b6 CHTC planning retreat June 21/22 Collaboration day tentatively June 20 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: Matt 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks (targeting initial release for August) AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy Kubernetes Hackathon today AI (BrianL): prepare PRs for updating Dex templates to generate proxy-url config AI (Mat): Copy Expanse remote Flux config for TACC AI (Matt): osg-repo technical debt Discussion \u00b6 None this week Support Update \u00b6 Louvain (BrianL): issues with EL8 WNs pulling from Virgo caches (using default security policy) DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 13, 2023"},{"location":"meetings/2023/TechArea20230613/#osg-technology-area-meeting-13-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 13 June 2023"},{"location":"meetings/2023/TechArea20230613/#announcements","text":"CHTC planning retreat June 21/22 Collaboration day tentatively June 20","title":"Announcements"},{"location":"meetings/2023/TechArea20230613/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: Matt 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230613/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230613/#osg-software-team","text":"OSG 3.7 tasks (targeting initial release for August) AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy Kubernetes Hackathon today AI (BrianL): prepare PRs for updating Dex templates to generate proxy-url config AI (Mat): Copy Expanse remote Flux config for TACC AI (Matt): osg-repo technical debt","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230613/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230613/#support-update","text":"Louvain (BrianL): issues with EL8 WNs pulling from Virgo caches (using default security policy)","title":"Support Update"},{"location":"meetings/2023/TechArea20230613/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230613/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230613/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230620/","text":"OSG Technology Area Meeting, 20 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW Announcements \u00b6 CHTC planning retreat June 21/22 Collaboration day moved to Thursday, July 6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy Discussion \u00b6 GlideinWMS: - 3.10.3 release candidate in progress - CMS ran into a bug with 3.9.6 where the factory wasn't updating the number of glideins and kept sending new glideins. This had been fixed in 3.10; if you are using tokens, be sure to use GlideinWMS 3.10 or newer. Brief overview of OSG 3.7 plans so far: - OSG 3.7 layout will not differ much from previous layouts (i.e. will have \"main\" and \"upcoming\") - OSG release schedules starting with 3.7 will be aligned with HTCondor release schedules (starting with 11): 3.7-main will have HTCondor 11.0, and 3.7-upcoming will have HTCondor 11.x - OSG team is experimenting with new signing procedures; this should not impact developers Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 20, 2023"},{"location":"meetings/2023/TechArea20230620/#osg-technology-area-meeting-20-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW","title":"OSG Technology Area Meeting, 20 June 2023"},{"location":"meetings/2023/TechArea20230620/#announcements","text":"CHTC planning retreat June 21/22 Collaboration day moved to Thursday, July 6","title":"Announcements"},{"location":"meetings/2023/TechArea20230620/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230620/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 232 -5 Open 38 -1 Selected for Dev 31 +4 In Progress 23 -2 Dev Complete 7 +0 Ready for Testing 0 -3 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230620/#osg-software-team","text":"OSG 3.7 tasks AI (Mat): Update design doc AI (Mat): Update koji tags/targets based on the design doc AI (Matt): learn about Yubikeys, intended for package signing AI (Mat): Koji policy","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230620/#discussion","text":"GlideinWMS: - 3.10.3 release candidate in progress - CMS ran into a bug with 3.9.6 where the factory wasn't updating the number of glideins and kept sending new glideins. This had been fixed in 3.10; if you are using tokens, be sure to use GlideinWMS 3.10 or newer. Brief overview of OSG 3.7 plans so far: - OSG 3.7 layout will not differ much from previous layouts (i.e. will have \"main\" and \"upcoming\") - OSG release schedules starting with 3.7 will be aligned with HTCondor release schedules (starting with 11): 3.7-main will have HTCondor 11.0, and 3.7-upcoming will have HTCondor 11.x - OSG team is experimenting with new signing procedures; this should not impact developers","title":"Discussion"},{"location":"meetings/2023/TechArea20230620/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20230620/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230620/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230620/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230627/","text":"OSG Technology Area Meeting, 27 June 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: ??? Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday) \u00b6 Stale due to Jira outage # of tickets \u0394 State 233 +1 Open 37 +1 Selected for Dev 33 -2 In Progress 18 -1 Dev Complete 4 +2 Ready for Testing 0 -0 Ready for Release OSG Software Team \u00b6 OSG 3.7 tasks AI (Mat): Finish design doc; send it out for re-review AI (Mat): Review Koji policy config AI (Matt): Yubikey process documented? Kubernetes Hackathon AI (BrianL/Mat/Matt): TACC PATh Facility AI (BrianL): testing Flux minor version upgrades AI (Matt): repo k8s health probe (OPS-332) Other AI (BrianL/Mat): Test xrootd-multiuser supplementary groups patch in the PATh Facility origin Discussion \u00b6 None this week Support Update \u00b6 (Derek) Working on GRACC corrections. DevOps \u00b6 Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up) OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 Discussion \u00b6 None this week","title":"June 27, 2023"},{"location":"meetings/2023/TechArea20230627/#osg-technology-area-meeting-27-june-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt","title":"OSG Technology Area Meeting, 27 June 2023"},{"location":"meetings/2023/TechArea20230627/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230627/#triage-duty","text":"Triage duty shifts Tue-Mon This week: ??? Next week: ??? 6 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230627/#jira-as-of-monday","text":"Stale due to Jira outage # of tickets \u0394 State 233 +1 Open 37 +1 Selected for Dev 33 -2 In Progress 18 -1 Dev Complete 4 +2 Ready for Testing 0 -0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230627/#osg-software-team","text":"OSG 3.7 tasks AI (Mat): Finish design doc; send it out for re-review AI (Mat): Review Koji policy config AI (Matt): Yubikey process documented? Kubernetes Hackathon AI (BrianL/Mat/Matt): TACC PATh Facility AI (BrianL): testing Flux minor version upgrades AI (Matt): repo k8s health probe (OPS-332) Other AI (BrianL/Mat): Test xrootd-multiuser supplementary groups patch in the PATh Facility origin","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230627/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230627/#support-update","text":"(Derek) Working on GRACC corrections.","title":"Support Update"},{"location":"meetings/2023/TechArea20230627/#devops","text":"Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up)","title":"DevOps"},{"location":"meetings/2023/TechArea20230627/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230627/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230718/","text":"OSG Technology Area Meeting, 18 July 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 TimT OOO Thursday MattW OOO Thursday + Friday BrianL OOO next week MatS OOO next Monday afternoon Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: Mat 8 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 243 +16 Open 24 -7 Selected for Dev 27 -5 In Progress 17 -1 Dev Complete 4 +0 Ready for Testing 0 -0 Ready for Release OSG Software Team \u00b6 Release AI (Mat): Release XRootD 5.6+ AI (BrianL): Release xrootd-multiuser-2.1.3+ AI (Matt): osg-ca-scripts missing dependency on perl-filetest. We need this done before we can build EL9 tarballs - no longer included with base perl packages in EL9. MatS to provide special Perl packaging tips. AI (Matt): Release oidc-agent-4.4.2+. SRPMs no longer provided by upstream, github is not properly organized to use as source. Either a spec file in the github, or return to releasing the srpm OSG 23 tasks What's the next step in the Yubikey setup for promoting packages? Per-developer key, packages get re-signed when promoted from development to testing Need to: Update script OSG Promote Generate promotion key Create Yubikey for each developer (4 or 5) Workflow update: Will need to sign packages locally, since you can't use a Yubikey on Moria AI (Matt): Build buildsys-macro packages AI (BrianL): build package list AI (Matt): update release scripts to accommodate OSG 23 New args: ... (as long as it sorts) Kubernetes Hackathon (Next Week) TBD Discussion \u00b6 None this week Support Update \u00b6 Topology/GGUS (BrianL, Mat): Topology does not accept certs from SHA1-signed CAs. We need to petition G\u00fcnter to get the German CA to update their signing key. Mat: Reach out to Gunter to update CA, update Topology to temporarily accept SHA1 Louvain (Mat): OSG-based CVMFS installation hitting Syracuse cache from Europe. We should probably just suggest that he install the EGI config while we sort out policy. Renewing Colorado host certificates (Matt): Awaiting approval by Douglas DevOps \u00b6 Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up) OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"July 18, 2023"},{"location":"meetings/2023/TechArea20230718/#osg-technology-area-meeting-18-july-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 18 July 2023"},{"location":"meetings/2023/TechArea20230718/#announcements","text":"TimT OOO Thursday MattW OOO Thursday + Friday BrianL OOO next week MatS OOO next Monday afternoon","title":"Announcements"},{"location":"meetings/2023/TechArea20230718/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: Mat 8 (+1) open FreshDesk tickets 1 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230718/#jira-as-of-monday","text":"# of tickets \u0394 State 243 +16 Open 24 -7 Selected for Dev 27 -5 In Progress 17 -1 Dev Complete 4 +0 Ready for Testing 0 -0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230718/#osg-software-team","text":"Release AI (Mat): Release XRootD 5.6+ AI (BrianL): Release xrootd-multiuser-2.1.3+ AI (Matt): osg-ca-scripts missing dependency on perl-filetest. We need this done before we can build EL9 tarballs - no longer included with base perl packages in EL9. MatS to provide special Perl packaging tips. AI (Matt): Release oidc-agent-4.4.2+. SRPMs no longer provided by upstream, github is not properly organized to use as source. Either a spec file in the github, or return to releasing the srpm OSG 23 tasks What's the next step in the Yubikey setup for promoting packages? Per-developer key, packages get re-signed when promoted from development to testing Need to: Update script OSG Promote Generate promotion key Create Yubikey for each developer (4 or 5) Workflow update: Will need to sign packages locally, since you can't use a Yubikey on Moria AI (Matt): Build buildsys-macro packages AI (BrianL): build package list AI (Matt): update release scripts to accommodate OSG 23 New args: ... (as long as it sorts) Kubernetes Hackathon (Next Week) TBD","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230718/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230718/#support-update","text":"Topology/GGUS (BrianL, Mat): Topology does not accept certs from SHA1-signed CAs. We need to petition G\u00fcnter to get the German CA to update their signing key. Mat: Reach out to Gunter to update CA, update Topology to temporarily accept SHA1 Louvain (Mat): OSG-based CVMFS installation hitting Syracuse cache from Europe. We should probably just suggest that he install the EGI config while we sort out policy. Renewing Colorado host certificates (Matt): Awaiting approval by Douglas","title":"Support Update"},{"location":"meetings/2023/TechArea20230718/#devops","text":"Hosted-CE availability email, will need Brian Lin to create service account (Ashton will follow up)","title":"DevOps"},{"location":"meetings/2023/TechArea20230718/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230718/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230725/","text":"OSG Technology Area Meeting, 25 July 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Mat, Matt, TimT Announcements \u00b6 BrianL out this week Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: BrianL ? (+?) open FreshDesk tickets 1 (+0) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -6 Open 22 -2 Selected for Dev 30 +3 In Progress 16 -1 Dev Complete 2 -2 Ready for Testing 0 -0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon AI (Mat): Upgrade PATh Facility central manager AI (Mat): Investigate PATh Facility autoscaler issues AI (Matt): Perform various cleanup tasks on the OSG Repo server Kubernetes configuration OSG 23: AI (Matt): Update OSG Repo scripts to work with OSG 23 naming scheme AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23 Discussion \u00b6 Planning to have the copy of the OSDF plugin that is shipped with HTCondor come from the Pelican repo instead of osdf-client; this can be done independently of HTCondor 23 TimT: HTCondor 10.0.7 will be released today, and will have the newest version of scitokens-cpp in the tarballs. HTCondor 10.7.0 will be released later this week and will have apptainer in the tarballs. Support Update \u00b6 TimT: Bockjoo at UFlorida requests packaging \"xrootd-cmstfc\" for EL9; this is a \"contrib\" package meaning it's not officially supported by OSG Software. If building for EL9 is easy then we can do it ourselves, otherwise we will have to contact the developer. Matt: Created IGTF certs for UColorado and send them to the admin; Matt should ping them admin since they haven't responded Topology/GGUS (BrianL, Mat): G\u00fcnter is trying to get a new certificate working with Topology but running into SSL issues. SHA1 was a red herring: SHA1 support was disabled in EL9, not EL8, and Topology is still EL8. Mat will debug. DevOps \u00b6 (none this week) OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"July 25, 2023"},{"location":"meetings/2023/TechArea20230725/#osg-technology-area-meeting-25-july-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Mat, Matt, TimT","title":"OSG Technology Area Meeting, 25 July 2023"},{"location":"meetings/2023/TechArea20230725/#announcements","text":"BrianL out this week","title":"Announcements"},{"location":"meetings/2023/TechArea20230725/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: BrianL ? (+?) open FreshDesk tickets 1 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230725/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -6 Open 22 -2 Selected for Dev 30 +3 In Progress 16 -1 Dev Complete 2 -2 Ready for Testing 0 -0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230725/#osg-software-team","text":"Kubernetes Hackathon AI (Mat): Upgrade PATh Facility central manager AI (Mat): Investigate PATh Facility autoscaler issues AI (Matt): Perform various cleanup tasks on the OSG Repo server Kubernetes configuration OSG 23: AI (Matt): Update OSG Repo scripts to work with OSG 23 naming scheme AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230725/#discussion","text":"Planning to have the copy of the OSDF plugin that is shipped with HTCondor come from the Pelican repo instead of osdf-client; this can be done independently of HTCondor 23 TimT: HTCondor 10.0.7 will be released today, and will have the newest version of scitokens-cpp in the tarballs. HTCondor 10.7.0 will be released later this week and will have apptainer in the tarballs.","title":"Discussion"},{"location":"meetings/2023/TechArea20230725/#support-update","text":"TimT: Bockjoo at UFlorida requests packaging \"xrootd-cmstfc\" for EL9; this is a \"contrib\" package meaning it's not officially supported by OSG Software. If building for EL9 is easy then we can do it ourselves, otherwise we will have to contact the developer. Matt: Created IGTF certs for UColorado and send them to the admin; Matt should ping them admin since they haven't responded Topology/GGUS (BrianL, Mat): G\u00fcnter is trying to get a new certificate working with Topology but running into SSL issues. SHA1 was a red herring: SHA1 support was disabled in EL9, not EL8, and Topology is still EL8. Mat will debug.","title":"Support Update"},{"location":"meetings/2023/TechArea20230725/#devops","text":"(none this week)","title":"DevOps"},{"location":"meetings/2023/TechArea20230725/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230725/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230801/","text":"OSG Technology Area Meeting, 1 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 TimT out Wed afternoon - Fri MattW attending the OSG User School next week MattW out this afternoon Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (+?) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 238 +1 Open 16 -6 Selected for Dev 30 +0 In Progress 23 +7 Dev Complete 2 +0 Ready for Testing 1 +1 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23. Done? AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) We decided that merging the UW HTCondor and OSG repos would require hackery and also moving to Pungi is too large a lift so we will do the remaining work with mash AI (Mat): update osg-promote to allow Yubikey package signing. Is there a ticket? Mat to create a ticket AI (BrianL): build OSG 23 package list Discussion \u00b6 None this week Support Update \u00b6 CRIC (Mat): X.509 certificate Topology access turned out to be a user issue (missing client certificate bit) UFlorida (Mat): built xrootd-cmstfc for contrib DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"August 1, 2023"},{"location":"meetings/2023/TechArea20230801/#osg-technology-area-meeting-1-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 1 August 2023"},{"location":"meetings/2023/TechArea20230801/#announcements","text":"TimT out Wed afternoon - Fri MattW attending the OSG User School next week MattW out this afternoon","title":"Announcements"},{"location":"meetings/2023/TechArea20230801/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: TimT 6 (+?) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230801/#jira-as-of-monday","text":"# of tickets \u0394 State 238 +1 Open 16 -6 Selected for Dev 30 +0 In Progress 23 +7 Dev Complete 2 +0 Ready for Testing 1 +1 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230801/#osg-software-team","text":"OSG 23: AI (Matt, with Mat): Build \"buildsys-macros\" packages for OSG 23. Done? AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) We decided that merging the UW HTCondor and OSG repos would require hackery and also moving to Pungi is too large a lift so we will do the remaining work with mash AI (Mat): update osg-promote to allow Yubikey package signing. Is there a ticket? Mat to create a ticket AI (BrianL): build OSG 23 package list","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230801/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230801/#support-update","text":"CRIC (Mat): X.509 certificate Topology access turned out to be a user issue (missing client certificate bit) UFlorida (Mat): built xrootd-cmstfc for contrib","title":"Support Update"},{"location":"meetings/2023/TechArea20230801/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230801/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230801/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230808/","text":"OSG Technology Area Meeting, 8 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 BrianL OOO later this morning MattW attending the OSG User School this week MatS OOO Fri - Wed Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 7 (+1) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) AI (Mat): update osg-promote to allow Yubikey package signing AI (BrianL): build OSG 23 package list Kubernetes Hackathon AI (BrianL): test xrootd-multiuser on PATh origin Discussion \u00b6 None this week Support Update \u00b6 JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Georgia Tech (Mat): submit a downtime for them DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"August 8, 2023"},{"location":"meetings/2023/TechArea20230808/#osg-technology-area-meeting-8-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 8 August 2023"},{"location":"meetings/2023/TechArea20230808/#announcements","text":"BrianL OOO later this morning MattW attending the OSG User School this week MatS OOO Fri - Wed","title":"Announcements"},{"location":"meetings/2023/TechArea20230808/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 7 (+1) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230808/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230808/#osg-software-team","text":"OSG 23: AI (Matt): Convert mash scripts to Pungi (SOFTWARE-5621) AI (Mat): update osg-promote to allow Yubikey package signing AI (BrianL): build OSG 23 package list Kubernetes Hackathon AI (BrianL): test xrootd-multiuser on PATh origin","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230808/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230808/#support-update","text":"JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Georgia Tech (Mat): submit a downtime for them","title":"Support Update"},{"location":"meetings/2023/TechArea20230808/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230808/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230808/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230815/","text":"OSG Technology Area Meeting, 15 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 MatS OOO Fri - Wed Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: MattW Next week: Mat 6 (-1) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) TimT to create empty HTC23 repos for testing Open item: Use same signing key(s) for OSG and HTC? Open item: Generate OSG 23 promotion key(s) AI (BrianL): assign OSG 23 package builds AI (BrianL, Matt): populate bootstrap tags AI (BrianL, Matt): start massive rebuild OSG 3.6 AI (Matt): release new version of xrootd-multiuser AI (BrianL): who knows how to add EPEL packages to the build repos? Miscellaneous AI (Matt): autogenerate Topology IDs AI (Matt): Topology webhook -> GitHub Actions Changes to 2FA will break the webhook in 44 days Currently lives in the topology repo, deployed in the same container Gordon Watts: IRIS HEP talk topic Something K8s related oidc-agent-4.4.2 - still blocked MattW: Create github ticket to restore spec file Discussion \u00b6 None this week Support Update \u00b6 JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Person to contact is John, currently unavailable OSG School Participants requesting accounts X.509 CVMFS Helper Core Dumping on EL9 (Derek) SciTokens support is wrapped up in this package Python SciTokens EPEL package Rebuild for EL9 (Derek) This is at least a month away from being released in EPEL DevOps \u00b6 Really pushing on the python-scitokens EPEL package. CVMFS helper is core dumping in EL9 build: Github Issue OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign pegasus 5.0.6 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 Discussion \u00b6 None this week","title":"August 15, 2023"},{"location":"meetings/2023/TechArea20230815/#osg-technology-area-meeting-15-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 15 August 2023"},{"location":"meetings/2023/TechArea20230815/#announcements","text":"MatS OOO Fri - Wed","title":"Announcements"},{"location":"meetings/2023/TechArea20230815/#triage-duty","text":"Triage duty shifts Tue-Mon This week: MattW Next week: Mat 6 (-1) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230815/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230815/#osg-software-team","text":"OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) TimT to create empty HTC23 repos for testing Open item: Use same signing key(s) for OSG and HTC? Open item: Generate OSG 23 promotion key(s) AI (BrianL): assign OSG 23 package builds AI (BrianL, Matt): populate bootstrap tags AI (BrianL, Matt): start massive rebuild OSG 3.6 AI (Matt): release new version of xrootd-multiuser AI (BrianL): who knows how to add EPEL packages to the build repos? Miscellaneous AI (Matt): autogenerate Topology IDs AI (Matt): Topology webhook -> GitHub Actions Changes to 2FA will break the webhook in 44 days Currently lives in the topology repo, deployed in the same container Gordon Watts: IRIS HEP talk topic Something K8s related oidc-agent-4.4.2 - still blocked MattW: Create github ticket to restore spec file","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230815/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230815/#support-update","text":"JLab (BrianL): running into TLS issues upon macaroon request with fts-rest-transfer-client Person to contact is John, currently unavailable OSG School Participants requesting accounts X.509 CVMFS Helper Core Dumping on EL9 (Derek) SciTokens support is wrapped up in this package Python SciTokens EPEL package Rebuild for EL9 (Derek) This is at least a month away from being released in EPEL","title":"Support Update"},{"location":"meetings/2023/TechArea20230815/#devops","text":"Really pushing on the python-scitokens EPEL package. CVMFS helper is core dumping in EL9 build: Github Issue","title":"DevOps"},{"location":"meetings/2023/TechArea20230815/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.4 frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign pegasus 5.0.6 Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230815/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230829/","text":"OSG Technology Area Meeting, 29 August 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: MattW 3 (-3) open FreshDesk tickets 0 (+1) open GGUS ticket Jira (as of Monday) \u00b6 # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Table in design doc for which htcss repos to merge with osg AI (Matt): Complete the two -contrib builds (reach out to Mat for what to do with SVN repo branch) AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) Most tests require the HTCSS-23 condor build, these two don't May require slight updates to test repo AI (BrianL): review OSG 23 package builds Rebuild osg-release with new signing keys AI (TimT): populate HTCSS 23 daily repo Outstanding: condor, condor-plugin. Should be complete today (08/29) Issue: Things are still signed with Condor 10.X keys. Will need to get the signing keys to Tim somehow Will need to create a separate yubikey for this Issue: Moria is EL7, where we've previously seen issues in signing Could also sign on an EL8 machine in the current workflow, maybe AI (Matt): Create new signing yubikey to address the above issue AI (Mat): osg-promote updates Next step is koji OSG 3.6 AI (Matt): follow-up with Josh Willis regarding XRootD build available in testing Miscellaneous AI (BrianL): sort out osg-bot 2FA Should largely work as-is for automated actions with access tokens 2FA changes will cause issues if we need to log into the account though AI (Mat): Figure out issues with PATh-Wisc deployment Discussion \u00b6 None this week Support Update \u00b6 COManage (BrianL): work with CILogon to identify group misconfiguration issues; helped Will Leight with linking org IDs (contact CILogon about strange error) Issue: Group IDs and user IDs are becoming misaligned, which breaks COManage provisioning assumptions Issue: Users with multiple identities cannot be successfully linked to a single COManage user entity DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"August 29, 2023"},{"location":"meetings/2023/TechArea20230829/#osg-technology-area-meeting-29-august-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 29 August 2023"},{"location":"meetings/2023/TechArea20230829/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230829/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: MattW 3 (-3) open FreshDesk tickets 0 (+1) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230829/#jira-as-of-monday","text":"# of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday)"},{"location":"meetings/2023/TechArea20230829/#osg-software-team","text":"OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Table in design doc for which htcss repos to merge with osg AI (Matt): Complete the two -contrib builds (reach out to Mat for what to do with SVN repo branch) AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) Most tests require the HTCSS-23 condor build, these two don't May require slight updates to test repo AI (BrianL): review OSG 23 package builds Rebuild osg-release with new signing keys AI (TimT): populate HTCSS 23 daily repo Outstanding: condor, condor-plugin. Should be complete today (08/29) Issue: Things are still signed with Condor 10.X keys. Will need to get the signing keys to Tim somehow Will need to create a separate yubikey for this Issue: Moria is EL7, where we've previously seen issues in signing Could also sign on an EL8 machine in the current workflow, maybe AI (Matt): Create new signing yubikey to address the above issue AI (Mat): osg-promote updates Next step is koji OSG 3.6 AI (Matt): follow-up with Josh Willis regarding XRootD build available in testing Miscellaneous AI (BrianL): sort out osg-bot 2FA Should largely work as-is for automated actions with access tokens 2FA changes will cause issues if we need to log into the account though AI (Mat): Figure out issues with PATh-Wisc deployment","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230829/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230829/#support-update","text":"COManage (BrianL): work with CILogon to identify group misconfiguration issues; helped Will Leight with linking org IDs (contact CILogon about strange error) Issue: Group IDs and user IDs are becoming misaligned, which breaks COManage provisioning assumptions Issue: Users with multiple identities cannot be successfully linked to a single COManage user entity","title":"Support Update"},{"location":"meetings/2023/TechArea20230829/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230829/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230829/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230905/","text":"OSG Technology Area Meeting, 5 September 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW, TimT Announcements \u00b6 IRIS-HEP retreat next Mon-Wed: https://indico.cern.ch/event/1288444/page/30534-meeting-participants Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: MattW Next week: TimT 6 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 Automated Jira ticket summary email seems to be flaky (maybe corresponds to Jira maintenace?) # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (BrianL): Switch osg-wn-client to Alma8 - AI (BrianL): Hosted CEs move update WN client scripts to the container image - AI (BrianL): Add support for HelmReleases on Nautilus - AI (Mat): Set up remote Kustomization to TACC - AI (Matt): Create postgres Topology institution database in Kubernetes OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Still an issue with empty repos? AI (Matt): Complete the two -contrib builds AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) May require slight updates to VMU repo regex ( https://github.com/opensciencegrid/vm-test-runs/blob/master/bin/vmu.py#L96-L119 ). Worth just trying it AI (Mat): Examine OSG-Test to see what needs to be updated for OSG 23 AI (TimT): populate HTCSS 23 repos Path of least resistance to compile newer versions of GnuPG on Moria (needed for daily and RC/release builds) AI (Mat): Kojihub update status Apache RPM turns on multiproc module, so does Hiera, apache doesn't like it. Talk to Joe to figure out how to turn off the packaging OSG 3.6 AI (Mat): review osg-pki-tools promotion request AI (Matt): build CA certs packages, merge in EL9 crypto policy hack Miscellaneous AI (BrianL): sort out osg-bot 2FA AI (TimT): debug various failures with HTCondor 10.8.0 release candidate Discussion \u00b6 GlideinWMS RC2 ready, final release should be ready today or tomorrow. - Added optionally enabled structured logging - Added workaround for rrdtool Python binding issues Support Update \u00b6 Caltech (Mat): review OSDF cache ticket for any remaining TODO items DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"September 5, 2023"},{"location":"meetings/2023/TechArea20230905/#osg-technology-area-meeting-5-september-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, MatS, MattW, TimT","title":"OSG Technology Area Meeting, 5 September 2023"},{"location":"meetings/2023/TechArea20230905/#announcements","text":"IRIS-HEP retreat next Mon-Wed: https://indico.cern.ch/event/1288444/page/30534-meeting-participants","title":"Announcements"},{"location":"meetings/2023/TechArea20230905/#triage-duty","text":"Triage duty shifts Tue-Mon This week: MattW Next week: TimT 6 (+3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230905/#jira-as-of-tuesday-morning","text":"Automated Jira ticket summary email seems to be flaky (maybe corresponds to Jira maintenace?) # of tickets \u0394 State 237 -1 Open 21 +5 Selected for Dev 29 -1 In Progress 21 -2 Dev Complete 3 +1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20230905/#osg-software-team","text":"Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (BrianL): Switch osg-wn-client to Alma8 - AI (BrianL): Hosted CEs move update WN client scripts to the container image - AI (BrianL): Add support for HelmReleases on Nautilus - AI (Mat): Set up remote Kustomization to TACC - AI (Matt): Create postgres Topology institution database in Kubernetes OSG 23: AI (Matt): Update mash scripts to merge OSG and UW HTCondor repos (SOFTWARE-5653) Still an issue with empty repos? AI (Matt): Complete the two -contrib builds AI (Matt): Kick off OSG 23 XRootD tests (worker node and XRootD) May require slight updates to VMU repo regex ( https://github.com/opensciencegrid/vm-test-runs/blob/master/bin/vmu.py#L96-L119 ). Worth just trying it AI (Mat): Examine OSG-Test to see what needs to be updated for OSG 23 AI (TimT): populate HTCSS 23 repos Path of least resistance to compile newer versions of GnuPG on Moria (needed for daily and RC/release builds) AI (Mat): Kojihub update status Apache RPM turns on multiproc module, so does Hiera, apache doesn't like it. Talk to Joe to figure out how to turn off the packaging OSG 3.6 AI (Mat): review osg-pki-tools promotion request AI (Matt): build CA certs packages, merge in EL9 crypto policy hack Miscellaneous AI (BrianL): sort out osg-bot 2FA AI (TimT): debug various failures with HTCondor 10.8.0 release candidate","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230905/#discussion","text":"GlideinWMS RC2 ready, final release should be ready today or tomorrow. - Added optionally enabled structured logging - Added workaround for rrdtool Python binding issues","title":"Discussion"},{"location":"meetings/2023/TechArea20230905/#support-update","text":"Caltech (Mat): review OSDF cache ticket for any remaining TODO items","title":"Support Update"},{"location":"meetings/2023/TechArea20230905/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230905/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230905/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230919/","text":"OSG Technology Area Meeting, 19 September 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 -3 Open 20 -1 Selected for Dev 30 -3 In Progress 23 +0 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (Matt): If no xDD tasks, set up shoveler in front of tiger cache (INF-1265) OSG 23: - AI (TimT): get HTCondor 23 daily repos in place. This is blocking OSG 23 really badly. - AI (Mat): Shepherd Kojihub upgrade to allow promotion via Yubikey (SOFTWARE-5637) - Needs to be updated for internal-development + internal-release - AI (Mat): Replace \"osg-internal\" tags and targets in 3.7 with \"osg-3.7-extra-deps\" (SOFTWARE-5611) - AI (Matt): Generate 5 Yubikeys with developer signing key OSG 3.6 - AI (Matt): XRootD 5.6.2 (sometime this week) Miscellaneous - AI (BrianL): sort out osg-bot 2FA (needs to be done this week!) Discussion \u00b6 GlideinWMS 3.10.4 is ready for testing - Mats Rynge reported a bug in token caching due to an EL7 pyjwt bug - Marco gave Mats a patch -- this is not fatal, just errors in the logs Support Update \u00b6 LIGO (Mat): unexpected behavior for XRootD gridmap, somewhat related Jira ticket CMS (Matt): jsoncpp version built for all EL versions, xrootd-cmstfc still needs to be built DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"September 19, 2023"},{"location":"meetings/2023/TechArea20230919/#osg-technology-area-meeting-19-september-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 19 September 2023"},{"location":"meetings/2023/TechArea20230919/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230919/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 4 (-2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230919/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 -3 Open 20 -1 Selected for Dev 30 -3 In Progress 23 +0 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20230919/#osg-software-team","text":"Kubernetes Hackathon: - AI (BrianL): Build OSG 23 container images - AI (BrianL): Tie WN client series to OSG series used for Hosted CE image build - AI (Matt): If no xDD tasks, set up shoveler in front of tiger cache (INF-1265) OSG 23: - AI (TimT): get HTCondor 23 daily repos in place. This is blocking OSG 23 really badly. - AI (Mat): Shepherd Kojihub upgrade to allow promotion via Yubikey (SOFTWARE-5637) - Needs to be updated for internal-development + internal-release - AI (Mat): Replace \"osg-internal\" tags and targets in 3.7 with \"osg-3.7-extra-deps\" (SOFTWARE-5611) - AI (Matt): Generate 5 Yubikeys with developer signing key OSG 3.6 - AI (Matt): XRootD 5.6.2 (sometime this week) Miscellaneous - AI (BrianL): sort out osg-bot 2FA (needs to be done this week!)","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230919/#discussion","text":"GlideinWMS 3.10.4 is ready for testing - Mats Rynge reported a bug in token caching due to an EL7 pyjwt bug - Marco gave Mats a patch -- this is not fatal, just errors in the logs","title":"Discussion"},{"location":"meetings/2023/TechArea20230919/#support-update","text":"LIGO (Mat): unexpected behavior for XRootD gridmap, somewhat related Jira ticket CMS (Matt): jsoncpp version built for all EL versions, xrootd-cmstfc still needs to be built","title":"Support Update"},{"location":"meetings/2023/TechArea20230919/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230919/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230919/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230926/","text":"OSG Technology Area Meeting, 26 September 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: Matt 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 233 -1 Open 17 -3 Selected for Dev 32 +2 In Progress 24 +1 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release OSG Software Team \u00b6 OSG 23: - AI (TimT): get HTCSS 23 RCs in place - AI (Mat): Coordinate transition to kojihub2000. Absolutely has to be done by Thursday. - AI (Matt): Mass promote packages post upgrade - AI (BrianL): Add support for OSG 23 containers - AI (TimT): kick off test of WN client tarball creation ~ OSG 23 - AI (BrianL): Review docker-osg-build container PR - AI (Matt): add new GPG keys on repo - We may have to backversion GlideinWMS - For October: add cron job regen-repo for minefield + HTCSS repos Discussion \u00b6 None this week Support Update \u00b6 JLab (Matt): instruct them on how to install XRootD debug symbols, look for core files DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"September 26, 2023"},{"location":"meetings/2023/TechArea20230926/#osg-technology-area-meeting-26-september-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 26 September 2023"},{"location":"meetings/2023/TechArea20230926/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20230926/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: Matt 4 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20230926/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 233 -1 Open 17 -3 Selected for Dev 32 +2 In Progress 24 +1 Dev Complete 10 +6 Ready for Testing 0 -1 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20230926/#osg-software-team","text":"OSG 23: - AI (TimT): get HTCSS 23 RCs in place - AI (Mat): Coordinate transition to kojihub2000. Absolutely has to be done by Thursday. - AI (Matt): Mass promote packages post upgrade - AI (BrianL): Add support for OSG 23 containers - AI (TimT): kick off test of WN client tarball creation ~ OSG 23 - AI (BrianL): Review docker-osg-build container PR - AI (Matt): add new GPG keys on repo - We may have to backversion GlideinWMS - For October: add cron job regen-repo for minefield + HTCSS repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20230926/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20230926/#support-update","text":"JLab (Matt): instruct them on how to install XRootD debug symbols, look for core files","title":"Support Update"},{"location":"meetings/2023/TechArea20230926/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20230926/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20230926/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231003/","text":"OSG Technology Area Meeting, 3 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: TimT 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 OSG 23: - Tasks for today - AI (Matt): Kick off WN tarball scripts - AI (TimT): Write OSG 23 upgrade instructions - AI (BrianL): Ensure container images are built - AI (BrianL): Update release notes - AI (TimT): Announce release! - Follow-on tasks - Test FNAL build access - Remove repo FIXME hacks - Improve Kerberos support in osg-promote - Additional mash cache for 23 dev repos (almost done?) - Figure out if we need VOMS for EL9/an update to EL8 - HTCondor-CE + Torque failures - Summarize problems encountered during release process Kuberentes Hackathon: - AI (Mat, BrianL): repo cleanup - AI (BrianL): troubleshoot TACC PATh Facility - AI (Matt): update central collector host cert - AI (Matt): stash-cache + shoveler work Discussion \u00b6 Marco: GlideinWMS released last week and has been stable so far; factory ops has not reported problems. Planning to work with JeffD to improve GlideinWMS containers. Support Update \u00b6 JLab (Matt, BrianL): XRootD core dump, issues with proxy config with gfal tools DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"October 3, 2023"},{"location":"meetings/2023/TechArea20231003/#osg-technology-area-meeting-3-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Marco, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 3 October 2023"},{"location":"meetings/2023/TechArea20231003/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231003/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: TimT 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231003/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231003/#osg-software-team","text":"OSG 23: - Tasks for today - AI (Matt): Kick off WN tarball scripts - AI (TimT): Write OSG 23 upgrade instructions - AI (BrianL): Ensure container images are built - AI (BrianL): Update release notes - AI (TimT): Announce release! - Follow-on tasks - Test FNAL build access - Remove repo FIXME hacks - Improve Kerberos support in osg-promote - Additional mash cache for 23 dev repos (almost done?) - Figure out if we need VOMS for EL9/an update to EL8 - HTCondor-CE + Torque failures - Summarize problems encountered during release process Kuberentes Hackathon: - AI (Mat, BrianL): repo cleanup - AI (BrianL): troubleshoot TACC PATh Facility - AI (Matt): update central collector host cert - AI (Matt): stash-cache + shoveler work","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231003/#discussion","text":"Marco: GlideinWMS released last week and has been stable so far; factory ops has not reported problems. Planning to work with JeffD to improve GlideinWMS containers.","title":"Discussion"},{"location":"meetings/2023/TechArea20231003/#support-update","text":"JLab (Matt, BrianL): XRootD core dump, issues with proxy config with gfal tools","title":"Support Update"},{"location":"meetings/2023/TechArea20231003/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231003/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231003/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231010/","text":"OSG Technology Area Meeting, 10 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, Tim Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 4 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 A fair amount of OSG 23 work remains https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 , though some tickets look like they may be able to be closed. Top priorities include: - Fix build signing/development (fixed by Matt) - Test and provide instructions for FNAL build access - Figure out if we need VOMS for EL9/an update to EL8 - Update docs for OSG 23 tarballs and images Miscellaneous - AI (BrianL, Mat, Matt): offboard Carl and Brian Chase Discussion \u00b6 Code freeze for HTCondor 23.1.0 and 23.0.1 is this week Marco: new features in progress for the next GlideinWMS release and development release; GlideinWMS 3.10.5 is working well. Marco will be unavailable for the next two weeks due to vacation and Fermilab workshop. AI (Marco): Send Todd Tannenbaum instructions for how to configure GlideinWMS to use apptainer from the HTCondor tarball. Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR Discussion \u00b6 None this week","title":"October 10, 2023"},{"location":"meetings/2023/TechArea20231010/#osg-technology-area-meeting-10-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, Tim","title":"OSG Technology Area Meeting, 10 October 2023"},{"location":"meetings/2023/TechArea20231010/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231010/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 4 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231010/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231010/#osg-software-team","text":"A fair amount of OSG 23 work remains https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 , though some tickets look like they may be able to be closed. Top priorities include: - Fix build signing/development (fixed by Matt) - Test and provide instructions for FNAL build access - Figure out if we need VOMS for EL9/an update to EL8 - Update docs for OSG 23 tarballs and images Miscellaneous - AI (BrianL, Mat, Matt): offboard Carl and Brian Chase","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231010/#discussion","text":"Code freeze for HTCondor 23.1.0 and 23.0.1 is this week Marco: new features in progress for the next GlideinWMS release and development release; GlideinWMS 3.10.5 is working well. Marco will be unavailable for the next two weeks due to vacation and Fermilab workshop. AI (Marco): Send Todd Tannenbaum instructions for how to configure GlideinWMS to use apptainer from the HTCondor tarball.","title":"Discussion"},{"location":"meetings/2023/TechArea20231010/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20231010/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231010/#osg-release-team","text":"Ready for Testing HTCondor 10.0.3 XRootD 5.5.5-1.2 Requires testing from Josh Willis prior frontier-squid 5.8-2.1 AI (TimT): create an INF ticket for testing at the CHTC, BrianL to assign Ready for Release HTCondor 10.4.0 HTCondor-CE 6.0.0 htgettoken 1.17 xcache 3.5.0-2 AI (MattW): Review release-tools PR","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231010/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231017/","text":"OSG Technology Area Meeting, 17 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - We want to upgrade various Tiger components (Kubernetes, Flux, Kustomize) and need to make sure our existing apps don't get broken, making changes as necessary. AI (BrianA): Investigate the upgrades. Things to note: - \"patchesStrategicMerge\" has been replaced with \"patches\" - \"vars\" are deprecated; \"replacements\" are the suggested replacement - AI (BrianL): TACC PATh Facility - AI (Mat): Finish deploying repo on Tempest - AI (Mat): osgvo-docker-pilot items We're getting close to Done Enough for OSG 23 https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . Remaining top items - Test and provide instructions for FNAL build access. Mat to write instructions. - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL) Update docs for OSG 23 tarballs and images - AI (Matt): Update mash scripts to pull HTCSS 23 RC packages into 23-{main,upcoming}-testing - AI (Matt): cpio in EL9 tarballs - AI (Mat): cronjob to regen repos to pull in HTCondor RPMs Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase Discussion \u00b6 HTCondor 23.1.0 and 23.0.1 are going onto the CHTC pool this week; we want to deploy in the OSPool as well, but BrianL and Mat will need to help UChicago staff upgrade their APs to OSG 23 first. Support Update \u00b6 JLab (BrianL, Matt): fts-rest-client created non-RFC proxies, which XRootD didn't like (reporting an unknown CA). Next issue is that macaroons configuration is apparently causing XRootD to dump core. UCSD (Mat): feature request for OSDF area with public read and authenticated write Kisti (Matt): got affirmation that new XRootD build contains the relevant changes DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Ready for Release Nothing Yet Discussion \u00b6 Release tomorrow","title":"October 17, 2023"},{"location":"meetings/2023/TechArea20231017/#osg-technology-area-meeting-17-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 17 October 2023"},{"location":"meetings/2023/TechArea20231017/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231017/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 6 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231017/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 234 +1 Open 17 +0 Selected for Dev 30 -2 In Progress 22 -2 Dev Complete 10 +6 Ready for Testing 3 +3 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231017/#osg-software-team","text":"Kubernetes Hackathon - We want to upgrade various Tiger components (Kubernetes, Flux, Kustomize) and need to make sure our existing apps don't get broken, making changes as necessary. AI (BrianA): Investigate the upgrades. Things to note: - \"patchesStrategicMerge\" has been replaced with \"patches\" - \"vars\" are deprecated; \"replacements\" are the suggested replacement - AI (BrianL): TACC PATh Facility - AI (Mat): Finish deploying repo on Tempest - AI (Mat): osgvo-docker-pilot items We're getting close to Done Enough for OSG 23 https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . Remaining top items - Test and provide instructions for FNAL build access. Mat to write instructions. - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL) Update docs for OSG 23 tarballs and images - AI (Matt): Update mash scripts to pull HTCSS 23 RC packages into 23-{main,upcoming}-testing - AI (Matt): cpio in EL9 tarballs - AI (Mat): cronjob to regen repos to pull in HTCondor RPMs Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231017/#discussion","text":"HTCondor 23.1.0 and 23.0.1 are going onto the CHTC pool this week; we want to deploy in the OSPool as well, but BrianL and Mat will need to help UChicago staff upgrade their APs to OSG 23 first.","title":"Discussion"},{"location":"meetings/2023/TechArea20231017/#support-update","text":"JLab (BrianL, Matt): fts-rest-client created non-RFC proxies, which XRootD didn't like (reporting an unknown CA). Next issue is that macaroons configuration is apparently causing XRootD to dump core. UCSD (Mat): feature request for OSDF area with public read and authenticated write Kisti (Matt): got affirmation that new XRootD build contains the relevant changes","title":"Support Update"},{"location":"meetings/2023/TechArea20231017/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231017/#osg-release-team","text":"Ready for Testing HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Ready for Release Nothing Yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231017/#discussion_1","text":"Release tomorrow","title":"Discussion"},{"location":"meetings/2023/TechArea20231024/","text":"OSG Technology Area Meeting, 26 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: Matt 3 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 246 +2 Open 28 -2 Selected for Dev 26 +0 In Progress 21 +1 Dev Complete 3 +3 Ready for Testing 2 +2 Ready for Release OSG Software Team \u00b6 Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase - AI (Mat) XRootD tarball for Pelican - AI (Mat) XRDHOST env is not working with XRootD 5.6.2 Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat) Update docs for OSG 23 tarballs - AI (Tim) Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL) Finish transition of internal containers to OSG 23 - AI (Matt) HTCondor repo rsync failures should cause update_repos.sh to fail Discussion \u00b6 None this week Support Update \u00b6 JLab (Mat): submit a GitHub issue for the macaroons coredump DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Discussion \u00b6 Release Thursday","title":"October 24, 2023"},{"location":"meetings/2023/TechArea20231024/#osg-technology-area-meeting-26-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 26 October 2023"},{"location":"meetings/2023/TechArea20231024/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231024/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: Matt 3 (-3) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231024/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 246 +2 Open 28 -2 Selected for Dev 26 +0 In Progress 21 +1 Dev Complete 3 +3 Ready for Testing 2 +2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231024/#osg-software-team","text":"Miscellaneous - AI (BrianL, Mat, Matt): offboard Brian Chase - AI (Mat) XRootD tarball for Pelican - AI (Mat) XRDHOST env is not working with XRootD 5.6.2 Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat) Update docs for OSG 23 tarballs - AI (Tim) Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL) Finish transition of internal containers to OSG 23 - AI (Matt) HTCondor repo rsync failures should cause update_repos.sh to fail","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231024/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231024/#support-update","text":"JLab (Mat): submit a GitHub issue for the macaroons coredump","title":"Support Update"},{"location":"meetings/2023/TechArea20231024/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231024/#osg-release-team","text":"Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34]","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231024/#discussion_1","text":"Release Thursday","title":"Discussion"},{"location":"meetings/2023/TechArea20231031/","text":"OSG Technology Area Meeting, 31 October 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: TimT 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 24 -4 Selected for Dev 30 +4 In Progress 19 -2 Dev Complete 2 -1 Ready for Testing 0 -2 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - AI (Mat): Set up Tempest repo - AI (Matt): xDD MongoDB, XRootD shoveler in base - AI (BrianL, Mat): investigate ITB OSDF; set up image updates Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (Mat): XRDHOST env is not working with XRootD 5.6.2 - AI (Mat): IGTF CA certificate update - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (TimT): Release HTCondor 23.0.1 and 23.1.0; send release announcement to OSG lists as well Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat): Update docs for OSG 23 tarballs - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Matt): Write signed OSG 23 RPMs to disk and turn strict signature checking on for 23-development Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34] Discussion \u00b6 Release Thursday","title":"October 31, 2023"},{"location":"meetings/2023/TechArea20231031/#osg-technology-area-meeting-31-october-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 31 October 2023"},{"location":"meetings/2023/TechArea20231031/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231031/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: TimT 2 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231031/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 24 -4 Selected for Dev 30 +4 In Progress 19 -2 Dev Complete 2 -1 Ready for Testing 0 -2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231031/#osg-software-team","text":"Kubernetes Hackathon - AI (Mat): Set up Tempest repo - AI (Matt): xDD MongoDB, XRootD shoveler in base - AI (BrianL, Mat): investigate ITB OSDF; set up image updates Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (Mat): XRDHOST env is not working with XRootD 5.6.2 - AI (Mat): IGTF CA certificate update - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (TimT): Release HTCondor 23.0.1 and 23.1.0; send release announcement to OSG lists as well Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Mat): Update docs for OSG 23 tarballs - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Matt): Write signed OSG 23 RPMs to disk and turn strict signature checking on for 23-development","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231031/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231031/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2023/TechArea20231031/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231031/#osg-release-team","text":"Ready for Testing CVMFS 2.11.1-1.3 osg-update-vos 1.4.2-2 Ready for Release HTCondor-CE 6.0.1-[13] XRootD 5.6.2-2.[34]","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231031/#discussion_1","text":"Release Thursday","title":"Discussion"},{"location":"meetings/2023/TechArea20231107/","text":"OSG Technology Area Meeting, 7 November 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, JohnT, MattW, TimT Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 3 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (???): ship first batch of vo-client updates for IGTF CA 3 - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (BrianL): put together backfill container RPM package ticket for MattW Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 Discussion \u00b6 How should we manage containers produced by OSG Staff? We should separate needs/reqs for containers that are built off of the OSG Software pipeline (dev -> testing -> release Yum repos) vs everything else Ideally, for everything else, we'd have a GitHub workflow template or action and some convention for tagging as well as immutability/retention policies Repo sprawl is a concern for security and management. Harbor creds are per organization so it may be prudent to separate out mostly-internally facing containers to a separate project, e.g. osg-internal Consolidation into the images repo doesn't work well for many images right now, especially those with \"large\" code bases as it makes dev (think tracking issues/PRs) more difficult. We should think of the SVN packaging repo as an analog here. We could add some additional flexibility to the images repo that would allow per-image references to external, trusted repos and usage of build processes that aren't so tightly tied to the Software release process. For the time being for the xrootd-monitoring-collector , we should just use a custom GitHub Action Implementation discussion in SOFTWARE-5013 Release of scitokens-cpp is in bodhi and needs karma. Ready for TimT tobuild for Debian EPEL7: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f0f162d810 EPEL8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f9dc18f284 EPEL9: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2dfb911a54 Support Update \u00b6 CVMFS issue with the latest version that causes the client to hang. DaveD is on it. DevOps \u00b6 scitokens-cpp release this week. Already in fedora update system bodhi. OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.2 osg-system-profiler 1.7.0 Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 7, 2023"},{"location":"meetings/2023/TechArea20231107/#osg-technology-area-meeting-7-november-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, JohnT, MattW, TimT","title":"OSG Technology Area Meeting, 7 November 2023"},{"location":"meetings/2023/TechArea20231107/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231107/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL 3 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231107/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231107/#osg-software-team","text":"Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (???): ship first batch of vo-client updates for IGTF CA 3 - AI (Mat): Write instructions for package signing using YubiKeys on Windows - AI (Matt): ship osg-ca-certs with workaround, osg-ca-certs-java without workaround - AI (BrianL): put together backfill container RPM package ticket for MattW Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231107/#discussion","text":"How should we manage containers produced by OSG Staff? We should separate needs/reqs for containers that are built off of the OSG Software pipeline (dev -> testing -> release Yum repos) vs everything else Ideally, for everything else, we'd have a GitHub workflow template or action and some convention for tagging as well as immutability/retention policies Repo sprawl is a concern for security and management. Harbor creds are per organization so it may be prudent to separate out mostly-internally facing containers to a separate project, e.g. osg-internal Consolidation into the images repo doesn't work well for many images right now, especially those with \"large\" code bases as it makes dev (think tracking issues/PRs) more difficult. We should think of the SVN packaging repo as an analog here. We could add some additional flexibility to the images repo that would allow per-image references to external, trusted repos and usage of build processes that aren't so tightly tied to the Software release process. For the time being for the xrootd-monitoring-collector , we should just use a custom GitHub Action Implementation discussion in SOFTWARE-5013 Release of scitokens-cpp is in bodhi and needs karma. Ready for TimT tobuild for Debian EPEL7: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f0f162d810 EPEL8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f9dc18f284 EPEL9: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2dfb911a54","title":"Discussion"},{"location":"meetings/2023/TechArea20231107/#support-update","text":"CVMFS issue with the latest version that causes the client to hang. DaveD is on it.","title":"Support Update"},{"location":"meetings/2023/TechArea20231107/#devops","text":"scitokens-cpp release this week. Already in fedora update system bodhi.","title":"DevOps"},{"location":"meetings/2023/TechArea20231107/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.2 osg-system-profiler 1.7.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231107/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231114/","text":"OSG Technology Area Meeting, 7 November 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - AI (Mat): Pelican ITB director! Work with the dev team to figure it out + William who will be working on the registry - Fengping got Mat unstuck on this - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): DSI oauth2-proxy Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows - Setup is working, not documented yet - AI (BrianL): Write release announcement for impending OSG CA certs packaging changes (aiming for week of Nov 27) - AI (MattW): osg-ca-certs sha1 workaround: Investigate failures with -java subpackage - Might be issue with tests rather than -java subpackage - AI (TimT): osg-ca-certs sha1 workaround: announce that this change is upcoming, will break java applications Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 AI (BrainL): vo-client, osg-pki-tools doesn't work on EL9 (via FermiLab) Only FermiLab directly interacts with the InCommon API via this tool, our capability to debug is limited AI (Mat): JLab ran into a segfault bug with XRootD, XRootD released a patch We need to backport/release this patch DevOps \u00b6 AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet Discussion \u00b6 None this week","title":"November 14, 2023"},{"location":"meetings/2023/TechArea20231114/#osg-technology-area-meeting-7-november-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 7 November 2023"},{"location":"meetings/2023/TechArea20231114/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231114/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 5 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231114/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 22 -2 Selected for Dev 28 -2 In Progress 22 +3 Dev Complete 1 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231114/#osg-software-team","text":"Kubernetes Hackathon - AI (Mat): Pelican ITB director! Work with the dev team to figure it out + William who will be working on the registry - Fengping got Mat unstuck on this - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): DSI oauth2-proxy Miscellaneous: - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows - Setup is working, not documented yet - AI (BrianL): Write release announcement for impending OSG CA certs packaging changes (aiming for week of Nov 27) - AI (MattW): osg-ca-certs sha1 workaround: Investigate failures with -java subpackage - Might be issue with tests rather than -java subpackage - AI (TimT): osg-ca-certs sha1 workaround: announce that this change is upcoming, will break java applications Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231114/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231114/#support-update","text":"AI (BrainL): vo-client, osg-pki-tools doesn't work on EL9 (via FermiLab) Only FermiLab directly interacts with the InCommon API via this tool, our capability to debug is limited AI (Mat): JLab ran into a segfault bug with XRootD, XRootD released a patch We need to backport/release this patch","title":"Support Update"},{"location":"meetings/2023/TechArea20231114/#devops","text":"AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart","title":"DevOps"},{"location":"meetings/2023/TechArea20231114/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231114/#discussion_1","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231128/","text":"OSG Technology Area Meeting, 28 November 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: TimT 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 246 -3 Open 23 +0 Selected for Dev 29 +1 In Progress 20 -1 Dev Complete 2 +0 Ready for Testing 1 -1 Ready for Release OSG Software Team \u00b6 Kubernetes Hackathon - AI (Mat): Pelican origin - William shadowing - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): Cleanup OSG 23 containers, maybe Release - AI (Matt): OSG CA certs workaround. Are there still mysterious test failures with the -java subpackage - AI (Matt): vo-client update Miscellaneous: - NRAO hero run - AI (Mat): submit transform to flock out to the OSPool from AP1 - AI (Mat): analyze Felipe's logs and construct a GPU site go/no-go list - AI (BrianL): Fix CHTC CE GPU submission - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 JLab (Mat): Kurt running into another XRootD segfault Topology/COManage (Mat): interrupted enrollment flow Lebanon (BrianL): new site, consulting with management regarding policy DevOps \u00b6 AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet Discussion \u00b6 CA cert updates? Punting for ~week. RE: AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) Done in previous release. Dropping latest OASIS worker node client symlink. Sites should be making a concious choice to change version. Possibly in Febuary?","title":"November 28, 2023"},{"location":"meetings/2023/TechArea20231128/#osg-technology-area-meeting-28-november-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 28 November 2023"},{"location":"meetings/2023/TechArea20231128/#announcements","text":"","title":"Announcements"},{"location":"meetings/2023/TechArea20231128/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: TimT 6 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231128/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 246 -3 Open 23 +0 Selected for Dev 29 +1 In Progress 20 -1 Dev Complete 2 +0 Ready for Testing 1 -1 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231128/#osg-software-team","text":"Kubernetes Hackathon - AI (Mat): Pelican origin - William shadowing - AI (Matt): xDD MongoDB Stuff, add shoveler sidecar to osdf-origin helm chart - AI (BrianL): Cleanup OSG 23 containers, maybe Release - AI (Matt): OSG CA certs workaround. Are there still mysterious test failures with the -java subpackage - AI (Matt): vo-client update Miscellaneous: - NRAO hero run - AI (Mat): submit transform to flock out to the OSPool from AP1 - AI (Mat): analyze Felipe's logs and construct a GPU site go/no-go list - AI (BrianL): Fix CHTC CE GPU submission - AI (Mat): XRootD tarball for Pelican - AI (BrianL): ship first batch of vo-client updates for IGTF CA 3 this week - AI (Mat): Write instructions for package signing using YubiKeys on Windows Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231128/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231128/#support-update","text":"JLab (Mat): Kurt running into another XRootD segfault Topology/COManage (Mat): interrupted enrollment flow Lebanon (BrianL): new site, consulting with management regarding policy","title":"Support Update"},{"location":"meetings/2023/TechArea20231128/#devops","text":"AI (Derek): K8s hackathon, address large number of permissions requested OpenSearch helm chart","title":"DevOps"},{"location":"meetings/2023/TechArea20231128/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.2 Another bugfix incoming for XRootD osg-system-profiler 1.7.0 htcondor-ce 23.0.1 osg-vo-client (Ready by Thursday) Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231128/#discussion_1","text":"CA cert updates? Punting for ~week. RE: AI (Tim): Update tarball scripts to use 23-main (SOFTWARE-5713) Done in previous release. Dropping latest OASIS worker node client symlink. Sites should be making a concious choice to change version. Possibly in Febuary?","title":"Discussion"},{"location":"meetings/2023/TechArea20231205/","text":"OSG Technology Area Meeting, 5 December 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Matt, TimT Announcements \u00b6 Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 247 +1 Open 24 +1 Selected for Dev 25 -4 In Progress 20 +0 Dev Complete 3 +1 Ready for Testing 2 +2 Ready for Release OSG Software Team \u00b6 Miscellaneous: - AI (Matt): add shoveler to OSDF origin helm chart Release - AI (Matt): build new xrootd-multiuser RPM - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 OSPool (BrianL): AP40 job submission issues were due to changes in the authZ level for condor_reconfig The University of Tokyo (Matt): answering questions about origin outbound ports DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing XRootD 5.6.3-1.4 Add SecEntity.addrInfo patch to xrootd 5.6 Backport certificate chain patch to XRootD 5.6 Ready for Release Nothing yet Discussion \u00b6 AI (TimT): Check in with Fabio regarding XRootD testing","title":"December 5, 2023"},{"location":"meetings/2023/TechArea20231205/#osg-technology-area-meeting-5-december-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Matt, TimT","title":"OSG Technology Area Meeting, 5 December 2023"},{"location":"meetings/2023/TechArea20231205/#announcements","text":"Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5","title":"Announcements"},{"location":"meetings/2023/TechArea20231205/#triage-duty","text":"Triage duty shifts Tue-Mon This week: TimT Next week: BrianL (?) 8 (+2) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231205/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 247 +1 Open 24 +1 Selected for Dev 25 -4 In Progress 20 +0 Dev Complete 3 +1 Ready for Testing 2 +2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231205/#osg-software-team","text":"Miscellaneous: - AI (Matt): add shoveler to OSDF origin helm chart Release - AI (Matt): build new xrootd-multiuser RPM - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231205/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231205/#support-update","text":"OSPool (BrianL): AP40 job submission issues were due to changes in the authZ level for condor_reconfig The University of Tokyo (Matt): answering questions about origin outbound ports","title":"Support Update"},{"location":"meetings/2023/TechArea20231205/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231205/#osg-release-team","text":"Ready for Testing XRootD 5.6.3-1.4 Add SecEntity.addrInfo patch to xrootd 5.6 Backport certificate chain patch to XRootD 5.6 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231205/#discussion_1","text":"AI (TimT): Check in with Fabio regarding XRootD testing","title":"Discussion"},{"location":"meetings/2023/TechArea20231212/","text":"OSG Technology Area Meeting, 12 December 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 245 -2 Open 24 +1 Selected for Dev 27 +2 In Progress 19 -1 Dev Complete 3 +0 Ready for Testing 0 -2 Ready for Release OSG Software Team \u00b6 Miscellaneous: - AI (Matt): build OSDF cache helm chart Release - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 None this week Support Update \u00b6 OSPool OSDF (BrianL): troubleshoot Showmic's OSDF job failures. Turned out to be too-large tokens due to extensive project group membership in COManage The University of Tokyo (BrianL): help them with cache registration. COManage Topology contact update appears to still be broken University of Wisconsin (BrianL): CarlV lost access to Koji Vanderbilt/Colorado (BrianL): help with IGTF cert renewals DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing XRootD 5.6.4 XCache 3.6.0 xrootd-multiuser 2.2.0 Ready for Release Nothing yet Discussion \u00b6 AI (TimT): Check in with Fabio regarding XRootD testing","title":"December 12, 2023"},{"location":"meetings/2023/TechArea20231212/#osg-technology-area-meeting-12-december-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 12 December 2023"},{"location":"meetings/2023/TechArea20231212/#announcements","text":"Mat OOO Dec 5 - 12 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5","title":"Announcements"},{"location":"meetings/2023/TechArea20231212/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231212/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 245 -2 Open 24 +1 Selected for Dev 27 +2 In Progress 19 -1 Dev Complete 3 +0 Ready for Testing 0 -2 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231212/#osg-software-team","text":"Miscellaneous: - AI (Matt): build OSDF cache helm chart Release - AI (Matt): build new xcache RPM Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231212/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2023/TechArea20231212/#support-update","text":"OSPool OSDF (BrianL): troubleshoot Showmic's OSDF job failures. Turned out to be too-large tokens due to extensive project group membership in COManage The University of Tokyo (BrianL): help them with cache registration. COManage Topology contact update appears to still be broken University of Wisconsin (BrianL): CarlV lost access to Koji Vanderbilt/Colorado (BrianL): help with IGTF cert renewals","title":"Support Update"},{"location":"meetings/2023/TechArea20231212/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231212/#osg-release-team","text":"Ready for Testing XRootD 5.6.4 XCache 3.6.0 xrootd-multiuser 2.2.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231212/#discussion_1","text":"AI (TimT): Check in with Fabio regarding XRootD testing","title":"Discussion"},{"location":"meetings/2023/TechArea20231219/","text":"OSG Technology Area Meeting, 12 December 2023 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt, TimT Announcements \u00b6 Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Derek OOO Dec 22 - Jan 2 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Tuesday morning) \u00b6 # of tickets \u0394 State 244 -1 Open 23 -1 Selected for Dev 24 -3 In Progress 18 -1 Dev Complete 2 -1 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Doc focus today! Tickets incoming Release - AI (Mat): release xrdcl-pelican - AI (Matt): verify cadist is populated by osg-ca-certs-java Miscellaneous: - AI (BrianL, Mat): deploy ITB OSDF Pelican origin - AI (Matt): build OSDF cache helm chart Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - AI (Matt): Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos Discussion \u00b6 HTCondor 23.x release candidate is deployed on the CHTC pool; CentOS 7 is added back as a supported platform. The IGTF 1.126 CA distribution preemptively pulled the old IGTF CA (that is still valid and in use); OSG software will not be releasing that version until the next year. Support Update \u00b6 University of Tokyo/KAGRA (BrianL): University of Tokyo KAGRA cache admin's registration was not showing up in Topology; Brian applied a workaround and also fixed the issue with the Topology software JLab (Matt): Admins were informed about a new XRootD version that should fix their crash DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet Discussion \u00b6 Delay releasing CA bundle based on IGTF 1.126 until January ospool-ap should always use OSG 23 Docker images","title":"December 19, 2023"},{"location":"meetings/2023/TechArea20231219/#osg-technology-area-meeting-12-december-2023","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: BrianL, Derek, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 12 December 2023"},{"location":"meetings/2023/TechArea20231219/#announcements","text":"Matt OOO Dec 26 - 29 BrianL OOO Dec 20 - Jan 5 Derek OOO Dec 22 - Jan 2","title":"Announcements"},{"location":"meetings/2023/TechArea20231219/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Mat Next week: TimT 8 (-1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2023/TechArea20231219/#jira-as-of-tuesday-morning","text":"# of tickets \u0394 State 244 -1 Open 23 -1 Selected for Dev 24 -3 In Progress 18 -1 Dev Complete 2 -1 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Tuesday morning)"},{"location":"meetings/2023/TechArea20231219/#osg-software-team","text":"Doc focus today! Tickets incoming Release - AI (Mat): release xrdcl-pelican - AI (Matt): verify cadist is populated by osg-ca-certs-java Miscellaneous: - AI (BrianL, Mat): deploy ITB OSDF Pelican origin - AI (Matt): build OSDF cache helm chart Remaining OSG 23 items https://opensciencegrid.atlassian.net/browse/SOFTWARE-5503 . - AI (Matt): Figure out if we need VOMS for EL9/an update to EL8 - AI (BrianL): Finish transition of internal containers to OSG 23 - AI (Mat): Investigate automatically regenerating development/minefield repos","title":"OSG Software Team"},{"location":"meetings/2023/TechArea20231219/#discussion","text":"HTCondor 23.x release candidate is deployed on the CHTC pool; CentOS 7 is added back as a supported platform. The IGTF 1.126 CA distribution preemptively pulled the old IGTF CA (that is still valid and in use); OSG software will not be releasing that version until the next year.","title":"Discussion"},{"location":"meetings/2023/TechArea20231219/#support-update","text":"University of Tokyo/KAGRA (BrianL): University of Tokyo KAGRA cache admin's registration was not showing up in Topology; Brian applied a workaround and also fixed the issue with the Topology software JLab (Matt): Admins were informed about a new XRootD version that should fix their crash","title":"Support Update"},{"location":"meetings/2023/TechArea20231219/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2023/TechArea20231219/#osg-release-team","text":"Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2023/TechArea20231219/#discussion_1","text":"Delay releasing CA bundle based on IGTF 1.126 until January ospool-ap should always use OSG 23 Docker images","title":"Discussion"},{"location":"meetings/2024/TechArea20240102/","text":"OSG Technology Area Meeting, 2 January 2024 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, TimT Announcements \u00b6 BrianL OOO Dec 20 - Jan 5 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: Matt Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday morning) \u00b6 # of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Brian B was unable to reproduce the failures that the osg-ca-certs package change is meant to work around (and so unable to verify that the workaround worked). We will need to ask the original reporter to reproduce it AI (Mat): add Institution to OSG ID mapping Topology endpoint AI (Mat): release xrdcl-pelican AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files Discussion \u00b6 GlideinWMS 3.10.6 RC is planned for the end of this week, containing mostly bugfixes: Fix for the Python-based match policy function not being correctly imported Compatibility with new versions of the M2Crypto library New factory config options by Marco Mascheroni HTCondor 23.3.0/23.0.3 scheduled for Thursday Support Update \u00b6 Mat (KAGRA): Tokyo site reporting issues while testing origin authentication; Mat will continue to debug DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet Discussion \u00b6","title":"January 2, 2024"},{"location":"meetings/2024/TechArea20240102/#osg-technology-area-meeting-2-january-2024","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Marco, Mat, Matt, TimT","title":"OSG Technology Area Meeting, 2 January 2024"},{"location":"meetings/2024/TechArea20240102/#announcements","text":"BrianL OOO Dec 20 - Jan 5","title":"Announcements"},{"location":"meetings/2024/TechArea20240102/#triage-duty","text":"Triage duty shifts Tue-Mon This week: Matt Next week: BrianL 8 (+0) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2024/TechArea20240102/#jira-as-of-monday-morning","text":"# of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday morning)"},{"location":"meetings/2024/TechArea20240102/#osg-software-team","text":"Brian B was unable to reproduce the failures that the osg-ca-certs package change is meant to work around (and so unable to verify that the workaround worked). We will need to ask the original reporter to reproduce it AI (Mat): add Institution to OSG ID mapping Topology endpoint AI (Mat): release xrdcl-pelican AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files","title":"OSG Software Team"},{"location":"meetings/2024/TechArea20240102/#discussion","text":"GlideinWMS 3.10.6 RC is planned for the end of this week, containing mostly bugfixes: Fix for the Python-based match policy function not being correctly imported Compatibility with new versions of the M2Crypto library New factory config options by Marco Mascheroni HTCondor 23.3.0/23.0.3 scheduled for Thursday","title":"Discussion"},{"location":"meetings/2024/TechArea20240102/#support-update","text":"Mat (KAGRA): Tokyo site reporting issues while testing origin authentication; Mat will continue to debug","title":"Support Update"},{"location":"meetings/2024/TechArea20240102/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2024/TechArea20240102/#osg-release-team","text":"Ready for Testing ospool-ep 1.0 Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2024/TechArea20240102/#discussion_1","text":"","title":"Discussion"},{"location":"meetings/2024/TechArea20240109/","text":"OSG Technology Area Meeting, 9 January 2024 \u00b6 Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending: Announcements \u00b6 Triage Duty \u00b6 Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket Jira (as of Monday morning) \u00b6 # of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release OSG Software Team \u00b6 Kubernetes hackathon: - AI (BrianL): clean up last Flux v1 Helm Charts, OSG 23 container image roundup - AI (Matt): xDD tasks? OSG institution frontend + OAuth2 - AI (Mat): new Yum repos on Tempest, auto-update EPs on the PATh Facility Release: - Frontier Squid + CarlV osg-build status? - AI (Matt): build VOMS for EL9 Miscellaneous: - AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files Discussion \u00b6 None this week Support Update \u00b6 None this week DevOps \u00b6 None this week OSG Release Team \u00b6 Ready for Testing Nothing yet Ready for Release Nothing yet Discussion \u00b6","title":"January 9, 2024"},{"location":"meetings/2024/TechArea20240109/#osg-technology-area-meeting-9-january-2024","text":"Coordinates: Conference: +1-415-655-0002, PIN: 146 266 9392, https://morgridge-org.zoom.us/j/91987518094 (password sent separately) Attending:","title":"OSG Technology Area Meeting, 9 January 2024"},{"location":"meetings/2024/TechArea20240109/#announcements","text":"","title":"Announcements"},{"location":"meetings/2024/TechArea20240109/#triage-duty","text":"Triage duty shifts Tue-Mon This week: BrianL Next week: Mat 9 (+1) open FreshDesk tickets 0 (+0) open GGUS ticket","title":"Triage Duty"},{"location":"meetings/2024/TechArea20240109/#jira-as-of-monday-morning","text":"# of tickets \u0394 State 245 +1 Open 28 +5 Selected for Dev 24 +0 In Progress 18 +0 Dev Complete 2 +0 Ready for Testing 0 +0 Ready for Release","title":"Jira (as of Monday morning)"},{"location":"meetings/2024/TechArea20240109/#osg-software-team","text":"Kubernetes hackathon: - AI (BrianL): clean up last Flux v1 Helm Charts, OSG 23 container image roundup - AI (Matt): xDD tasks? OSG institution frontend + OAuth2 - AI (Mat): new Yum repos on Tempest, auto-update EPs on the PATh Facility Release: - Frontier Squid + CarlV osg-build status? - AI (Matt): build VOMS for EL9 Miscellaneous: - AI (Matt): replace the deprecated save-state and set-output commands in GitHub Actions with Environment files","title":"OSG Software Team"},{"location":"meetings/2024/TechArea20240109/#discussion","text":"None this week","title":"Discussion"},{"location":"meetings/2024/TechArea20240109/#support-update","text":"None this week","title":"Support Update"},{"location":"meetings/2024/TechArea20240109/#devops","text":"None this week","title":"DevOps"},{"location":"meetings/2024/TechArea20240109/#osg-release-team","text":"Ready for Testing Nothing yet Ready for Release Nothing yet","title":"OSG Release Team"},{"location":"meetings/2024/TechArea20240109/#discussion_1","text":"","title":"Discussion"},{"location":"operations/comanage/","text":"COManage Operations \u00b6 OSG is using a new identity management system called COManage. This system is used for managing contact information for OSPool and PATh Facility users, Topology site contacts, and OSG/PATh staff. Contact Registration \u00b6 Contact registrations must be manually approved by a COManage admin. Follow the instructions below to approve a contact registration. Note This page is for COManage Admins who want to approve contact registrations. If you are a user who wants to register with COManage, go to the Registering for the OSG COManage page instead. Check for contact registration requests: If you are a COManage sponsor for a given group of registrants, you will receive email notifications when there are new registration requests. Check for an email from registry@cilogon.org saying \"Petition for changed status from Confirmed to Pending Approval\" and visit the first link in the body. Alternatively, you can view all requests pending approval here . Click on the registrant's name to view their request. Note Many groups share our COManage instance so make sure that you're only approving registration requests for the appropriate group, e.g. site contacts. If prompted, log in with your institutional credentials. Review the request: Verify that the request is legitimate by doing at least one of the following: Find associated support tickets by searching for their email address in Freshdesk Ask someone affiliated with the site, collaboration, or the sponsor of a project to verify the registrant's affiliation. Ask if other staff have been in contact with them via the #staff Slack channel Verify that the registrant has submitted their request using the correct form, e.g. OSPool users should not have submitted a request to register as a Topology contact. In the top-right corner, click the \"Add comment\" link and add a note indicating how you verified the request 'Approver Comment' is public The registrant will see notes added to the \"Approver Comment\" field Click the \"Approve\" button. You should see \"Petition Approved\" and \"Petition Finalized\" on top. The Status should now be \"Finalized\". Click on their name next to CO Person to verify that the registrant is Active and that they are in the expected groups. The user will get an email saying \"Petition for changed status from Pending Approval to Approved\". Revoking AP login access \u00b6 Login access to AP1 (PATh Facility) and AP40 (OSPool) is controlled by membership to COManage groups. To revoke a user's login access to either of these APs, perform the following steps: Find the corresponding user in COManage and revoke access to all OSG services or just the relevant AP: If you are revoking access to all OSG services, set the user's CO Person status to Suspended If you only need to revoke access to AP1 or AP40, remove the user from the ap1-login or ap40-login group, respectively Note the OSG Username identifier of the user On the AP host(s) where you are revoking access, clear the SSSD cache as root: root@ap-host # sss_cache -u <OSG Username> Replacing <OSG Username> with the OSG Username identifier that you noted in step (2) Troubleshooting \u00b6 The COManage petition is stuck in the \"confirmed\" state \u00b6 This may happen if there are issues when confirming the user's email address. We have seen this occur if a user clicks the confirmation link then closes the tab too quickly. Under the People drop-down on the left, click on My Population Browse to the CO Person record. Scroll down to the Role Attributes , click the gear icon, select Edit , and set the status for the Role to Active . Verify that the overall status of the CO Person record is Active . If not, change it to Active as well. Click on Autogenerate Identifiers on the right, so that the necessary identifiers are created. Now that the necessary identifiers exist for the CO Person record, the LDAP DN can be computed and the record provisioned in LDAP. To make sure, click on Provisioned Services and then Provision .","title":"COManage"},{"location":"operations/comanage/#comanage-operations","text":"OSG is using a new identity management system called COManage. This system is used for managing contact information for OSPool and PATh Facility users, Topology site contacts, and OSG/PATh staff.","title":"COManage Operations"},{"location":"operations/comanage/#contact-registration","text":"Contact registrations must be manually approved by a COManage admin. Follow the instructions below to approve a contact registration. Note This page is for COManage Admins who want to approve contact registrations. If you are a user who wants to register with COManage, go to the Registering for the OSG COManage page instead. Check for contact registration requests: If you are a COManage sponsor for a given group of registrants, you will receive email notifications when there are new registration requests. Check for an email from registry@cilogon.org saying \"Petition for changed status from Confirmed to Pending Approval\" and visit the first link in the body. Alternatively, you can view all requests pending approval here . Click on the registrant's name to view their request. Note Many groups share our COManage instance so make sure that you're only approving registration requests for the appropriate group, e.g. site contacts. If prompted, log in with your institutional credentials. Review the request: Verify that the request is legitimate by doing at least one of the following: Find associated support tickets by searching for their email address in Freshdesk Ask someone affiliated with the site, collaboration, or the sponsor of a project to verify the registrant's affiliation. Ask if other staff have been in contact with them via the #staff Slack channel Verify that the registrant has submitted their request using the correct form, e.g. OSPool users should not have submitted a request to register as a Topology contact. In the top-right corner, click the \"Add comment\" link and add a note indicating how you verified the request 'Approver Comment' is public The registrant will see notes added to the \"Approver Comment\" field Click the \"Approve\" button. You should see \"Petition Approved\" and \"Petition Finalized\" on top. The Status should now be \"Finalized\". Click on their name next to CO Person to verify that the registrant is Active and that they are in the expected groups. The user will get an email saying \"Petition for changed status from Pending Approval to Approved\".","title":"Contact Registration"},{"location":"operations/comanage/#revoking-ap-login-access","text":"Login access to AP1 (PATh Facility) and AP40 (OSPool) is controlled by membership to COManage groups. To revoke a user's login access to either of these APs, perform the following steps: Find the corresponding user in COManage and revoke access to all OSG services or just the relevant AP: If you are revoking access to all OSG services, set the user's CO Person status to Suspended If you only need to revoke access to AP1 or AP40, remove the user from the ap1-login or ap40-login group, respectively Note the OSG Username identifier of the user On the AP host(s) where you are revoking access, clear the SSSD cache as root: root@ap-host # sss_cache -u <OSG Username> Replacing <OSG Username> with the OSG Username identifier that you noted in step (2)","title":"Revoking AP login access"},{"location":"operations/comanage/#troubleshooting","text":"","title":"Troubleshooting"},{"location":"operations/comanage/#the-comanage-petition-is-stuck-in-the-confirmed-state","text":"This may happen if there are issues when confirming the user's email address. We have seen this occur if a user clicks the confirmation link then closes the tab too quickly. Under the People drop-down on the left, click on My Population Browse to the CO Person record. Scroll down to the Role Attributes , click the gear icon, select Edit , and set the status for the Role to Active . Verify that the overall status of the CO Person record is Active . If not, change it to Active as well. Click on Autogenerate Identifiers on the right, so that the necessary identifiers are created. Now that the necessary identifiers exist for the CO Person record, the LDAP DN can be computed and the record provisioned in LDAP. To make sure, click on Provisioned Services and then Provision .","title":"The COManage petition is stuck in the \"confirmed\" state"},{"location":"policy/bestman2-retire/","text":"BeStMan2 Retirement \u00b6 This document provides an overview of the planned retirement of support for BeStMan in the OSG Software Stack. Introduction \u00b6 BeStMan2 is a standalone implementation of a subset of the Storage Resource Manager v2 (SRMv2) protocol. SRM was meant to be a high-level management protocol for site storage resources, allowing administrators to manage storage offerings using the abstraction of \"storage tokens.\" Additionally, SRM can be used to mediate transfer protocol selection. OSG currently supports BeStMan2 in \"gateway mode\" -- in this mode, SRM is only used for metadata operations (listing directory contents), listing total space used, and load-balancing GridFTP servers. This functionality is redundant to what can be accomplished with GridFTP alone. BeStMan2 has not received upstream support for approximately five years; the existing code base (about 150,000 lines of Java - similar in size to Globus GridFTP) and its extensive set of dependencies (such as JGlobus) are now quite outdated and would require significant investment to modernize. OSG has worked at length with our stakeholders to replace SRM-specific use cases with other equivalents. We believe none of our stakeholders require sites to have an SRM endpoint: this document describes the site transition plan. Site Transition Plans \u00b6 We have released documentation for a configuration of GridFTP that takes advantage of Linux Virtual Server (LVS) for load balancing between multiple GridFTP endpoints. Sites should work with their supported VOs (typically, CMS or ATLAS) to identify any VO-specific usage and replacement plans for BeStMan2. Timeline \u00b6 March 2017 (completed): Release load balanced GridFTP documentation June 2017 (completed): OSG 3.4.0 is released without BeStMan December 2018 (completed): Security-only support for OSG 3.3 series and BeStMan is provided May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for BeStMan is provided.","title":"BeStMan2 Retirement"},{"location":"policy/bestman2-retire/#bestman2-retirement","text":"This document provides an overview of the planned retirement of support for BeStMan in the OSG Software Stack.","title":"BeStMan2 Retirement"},{"location":"policy/bestman2-retire/#introduction","text":"BeStMan2 is a standalone implementation of a subset of the Storage Resource Manager v2 (SRMv2) protocol. SRM was meant to be a high-level management protocol for site storage resources, allowing administrators to manage storage offerings using the abstraction of \"storage tokens.\" Additionally, SRM can be used to mediate transfer protocol selection. OSG currently supports BeStMan2 in \"gateway mode\" -- in this mode, SRM is only used for metadata operations (listing directory contents), listing total space used, and load-balancing GridFTP servers. This functionality is redundant to what can be accomplished with GridFTP alone. BeStMan2 has not received upstream support for approximately five years; the existing code base (about 150,000 lines of Java - similar in size to Globus GridFTP) and its extensive set of dependencies (such as JGlobus) are now quite outdated and would require significant investment to modernize. OSG has worked at length with our stakeholders to replace SRM-specific use cases with other equivalents. We believe none of our stakeholders require sites to have an SRM endpoint: this document describes the site transition plan.","title":"Introduction"},{"location":"policy/bestman2-retire/#site-transition-plans","text":"We have released documentation for a configuration of GridFTP that takes advantage of Linux Virtual Server (LVS) for load balancing between multiple GridFTP endpoints. Sites should work with their supported VOs (typically, CMS or ATLAS) to identify any VO-specific usage and replacement plans for BeStMan2.","title":"Site Transition Plans"},{"location":"policy/bestman2-retire/#timeline","text":"March 2017 (completed): Release load balanced GridFTP documentation June 2017 (completed): OSG 3.4.0 is released without BeStMan December 2018 (completed): Security-only support for OSG 3.3 series and BeStMan is provided May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for BeStMan is provided.","title":"Timeline"},{"location":"policy/campus-cyberinfrastructure/","text":"The OSG and NSF Campus Cyberinfrastructure \u00b6 The NSF Campus Cyberinfrastructure (CC*) program invests in coordinated campus-level cyberinfrastructure improvements, innovation, integration, and engineering for science applications and distributed research projects, including enhancements to campus networking and computing resources. The Open Science Grid (as part of the Partnership to Advance Throughput Computing (PATh) ), is here to help you with your Campus Cyberinfrastructure (CC*) proposal! Please contact us at cc-star-proposals@osg-htc.org We have significant experience working with CC* applicants and awardees, offering letters of collaboration and consulting for: bringing the power of the OSG to YOUR researchers gathering science drivers and planning local computing resources CC*-required resource sharing for the Campus Compute category*, and other options for integrating local resources into OSG *In the most recent call for proposals ( NSF 21-528 ), joining the OSG is mentioned as a potential path to sharing resources with the wider research community: Proposals are required to commit to a minimum of 20% shared time on the cluster and describe their approach to making the cluster available as a shared resource external to the campus, [...] One possible approach to implementing such a federated distributed computing solution is joining a multi-campus or national federated system such as the Open Science Grid. Sharing Resources via the OSG \u00b6 The OSG consortium provides standard services and support for computational resource providers (i.e., \"sites\") using a distributed fabric of high throughput computating (HTC) technologies. These distributed-HTC (dHTC) services communicate with the site's local resource management (e.g. \"queueing\") systems to provision resources for OSG users. The OSG itself does not own resources, but provides software and services that enable the sharing of resources by many sites, and enable users to take advantage of these from submission points (whether via an OSG-operated submission point, like OSG Connect , or a locally-managed one). To contribute computational resources to the OSG, the following will be needed: An existing compute cluster running on a supported operating system with a supported resource management system: Grid Engine , HTCondor , LSF , PBS Pro / Torque , Slurm , and some local cloud provisioners. Outbound network connectivity from the cluster's worker nodes SSH access to your local cluster's submit node from a known IP address Temporary scratch space on each worker node and shared home directories on each cluster node Installation of some additional packages on the local cluster, IF the site would like to maximize its ability to support users, including those with large per-job data, containerized software, and/or GPU jobs. (There ARE some exceptions to the above. Contact us to discuss them!) Next steps If you are interested in OSG-offered services, please contact us for a consultation, even if your site does not meet all the conditions as outlined above! Additional Materials \u00b6 If you are interested in learning more about the dHTC, OSG, and what it means to share resources via OSG services, consider reviewing the following presentations from our October 2020 workshop on dHTC and OSG services for campuses ( YouTube Playlist ): Intro to dHTC and PATh Services for Campuses ( slides , YouTube ) How OSG Works ( slides , YouTube ) Intro to OSG Resource Sharing ( slides , YouTube ) Resource Sharing Technology, Security, System Requirements, Setup Process ( slides , YouTube )","title":"Campus Cyberinfrastructure"},{"location":"policy/campus-cyberinfrastructure/#the-osg-and-nsf-campus-cyberinfrastructure","text":"The NSF Campus Cyberinfrastructure (CC*) program invests in coordinated campus-level cyberinfrastructure improvements, innovation, integration, and engineering for science applications and distributed research projects, including enhancements to campus networking and computing resources. The Open Science Grid (as part of the Partnership to Advance Throughput Computing (PATh) ), is here to help you with your Campus Cyberinfrastructure (CC*) proposal! Please contact us at cc-star-proposals@osg-htc.org We have significant experience working with CC* applicants and awardees, offering letters of collaboration and consulting for: bringing the power of the OSG to YOUR researchers gathering science drivers and planning local computing resources CC*-required resource sharing for the Campus Compute category*, and other options for integrating local resources into OSG *In the most recent call for proposals ( NSF 21-528 ), joining the OSG is mentioned as a potential path to sharing resources with the wider research community: Proposals are required to commit to a minimum of 20% shared time on the cluster and describe their approach to making the cluster available as a shared resource external to the campus, [...] One possible approach to implementing such a federated distributed computing solution is joining a multi-campus or national federated system such as the Open Science Grid.","title":"The OSG and NSF Campus Cyberinfrastructure"},{"location":"policy/campus-cyberinfrastructure/#sharing-resources-via-the-osg","text":"The OSG consortium provides standard services and support for computational resource providers (i.e., \"sites\") using a distributed fabric of high throughput computating (HTC) technologies. These distributed-HTC (dHTC) services communicate with the site's local resource management (e.g. \"queueing\") systems to provision resources for OSG users. The OSG itself does not own resources, but provides software and services that enable the sharing of resources by many sites, and enable users to take advantage of these from submission points (whether via an OSG-operated submission point, like OSG Connect , or a locally-managed one). To contribute computational resources to the OSG, the following will be needed: An existing compute cluster running on a supported operating system with a supported resource management system: Grid Engine , HTCondor , LSF , PBS Pro / Torque , Slurm , and some local cloud provisioners. Outbound network connectivity from the cluster's worker nodes SSH access to your local cluster's submit node from a known IP address Temporary scratch space on each worker node and shared home directories on each cluster node Installation of some additional packages on the local cluster, IF the site would like to maximize its ability to support users, including those with large per-job data, containerized software, and/or GPU jobs. (There ARE some exceptions to the above. Contact us to discuss them!) Next steps If you are interested in OSG-offered services, please contact us for a consultation, even if your site does not meet all the conditions as outlined above!","title":"Sharing Resources via the OSG"},{"location":"policy/campus-cyberinfrastructure/#additional-materials","text":"If you are interested in learning more about the dHTC, OSG, and what it means to share resources via OSG services, consider reviewing the following presentations from our October 2020 workshop on dHTC and OSG services for campuses ( YouTube Playlist ): Intro to dHTC and PATh Services for Campuses ( slides , YouTube ) How OSG Works ( slides , YouTube ) Intro to OSG Resource Sharing ( slides , YouTube ) Resource Sharing Technology, Security, System Requirements, Setup Process ( slides , YouTube )","title":"Additional Materials"},{"location":"policy/collab-bearer-tokens/","text":"Collaborations and Bearer Tokens \u00b6 Sites in the OSG grant access to their grid services based on client's association with a specific collaboration (i.e. VO) instead of granting access on a per-user basis. In the past, this type of access was provided through X.509 proxies with VOMS attributes to demonstrate assocation with a collaboration: Users (both human and robots) would request that their collaboration sign their X.509 proxies (usually through a VOMS server), Or in the case of automated services (i.e. pilot job submission) a collaboration could directly create and sign proxies themselves Now, sites can authenticate and authorize clients presenting bearer tokens, such as SciTokens or WLCG tokens. This document describes how collaborations can issue bearer tokens for the aforementioned use cases in ways that are compatible with OSG sites. Issuers \u00b6 To generate bearer tokens, a collaboration must adminster at least one \"token issuer\" to issue tokens to their users. In addition to generating and signing tokens, token issuers provide a public endpoint that can be used to validate an issued token, e.g. an OSG Compute Entrypoint (CE) will contact the token issuer to authorize a bearer token used for pilot job submission. Token issuer uptime Due to the centralized nature of bearer token validation, token issuers should be treated as critical, highly available services. Otherwise, a token issuer outage will result in OSG sites being unable to authenticate a collaboration's tokens, meaning an interruption in pilot job submission and authenticated data transfers. Choose one of the token issuer types below, depending on the needs of your collaboration. Simple issuer \u00b6 If your collaboration centrally administers all services requiring bearer tokens and your users do not need to directly manage bearer tokens, consider running a simple token issuer. A simple token issuer consists of a public/private certificate keypair where the private key is used to issue tokens directly and the public certificate is made available through a web server. For example, the OSPool (n\u00e9e OSG VO) serves its public certificate through GitHub pages and uses the private key to sign tokens used for pilot job submission as well as automatically generating tokens to accompany user jobs so that they can access their private storage areas. OAuth2/OpenID Connect \u00b6 If your collaboration distributes administrative responsibility or your users need to request and manage their own tokens, you should administer an OAuth2/OpenID Connect (OIDC) service (e.g., INDIGO IAM ) or work with an existing OAuth2/OIDC provider (e.g., CILogon ). For example, Fermilab uses CILogon as their OIDC provider combined with an HTVault server used to streamline the OIDC process for users and integrate with their local Kerberos. Claims \u00b6 Bearer tokens are self-describing credentials that enumerate their capabilities as \"claims\" and different token \"profiles\" enumerate common sets of claims. OSG sites support the following bearer token profiles: SciTokens WLCG tokens Claims are further described below with recommendations to ensure the greatest compatibility with OSG sites. Scope \u00b6 The scope claim is a space-separated list of authorizations that should be granted to the bearer. Scopes utilized by OSG services include the following: Capability SciTokens scope WLCG scope HTCondor READ condor:/READ compute.read HTCondor WRITE condor:/WRITE compute.modify compute.cancel compute.create XRootD read read:<PATH> storage.read:<PATH> XRootD write write:<PATH> storage.modify:<PATH> Replacing <PATH> with a path to the storage location that the bearer should be authorized to access. Issuer \u00b6 The issuer URL, or the iss claim, indicates the endpoint to use for authenticating a given token. A collaboration may have more than one token issuer but a single token issuer should never serve more than one collaboration. In other words, given the token issuer, the site can determine the collaboration that issued the token. The following collaborations have registered token issuers with the OSG: Collaboration Issuers ATLAS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/ATLAS.yaml CLAS12 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CLAS12.yaml CMS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CMS.yaml DES https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DES.yaml DUNE https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DUNE.yaml EIC https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/EIC.yaml Fermilab https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Fermilab.yaml CHTC (n\u00e9e GLOW) https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/GLOW.yaml Gluex https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Gluex.yaml IceCube https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/IceCube.yaml LIGO https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/LIGO.yaml Mu2e https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Mu2e.yaml OSPool https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/OSG.yaml SBND https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/SBND.yaml gm2 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/gm2.yaml The OSG distributes the osg-scitokens-mapfile RPM package that includes issuer and subject to default user mappings for use by OSG CEs. Subject \u00b6 Subjects (i.e., the sub claim) should be unique, stable identifiers that correspond to a user or service (e.g. pilot job submission). In other words, subjects combined with a token issuer can be used for suspending access for a given collaboration user, user-level accounting, monitoring, auditing, or tracing. In tandem with a token issuer URL (i.e., the iss claim), subjects can be used by site HTCondor-CE or XRootD services to map to a local identity. Privacy considerations Depending on your collaboration's userbase and contributing sites, you may have to take privacy concerns, such as the GDPR into account when assigning subjects to users. Thus, it may be preferable to assign users a randomly-generated string as their sub . Audience \u00b6 To take advantage of the improved security posture of bearer tokens, we recommend that the aud claim be set to the intended host. For example, tokens used for submission to an HTCondor-CE should set the following: aud = <CE FQDN>:<CE PORT> WLCG groups \u00b6 WLCG tokens may have the wlcg.groups claim consisting of a comma and space separated list of collaboration groups. The format of these groups are similar to VOMS FQANs: /<collaboration>[/<group>][/Role=<role>] , replacing <collaboration> , <group> , and <role> with the collaboration, group, and role, respectively, where the group and role are optional. For example, the following groups and roles have been used by the ATLAS and CMS collaborations: /atlas/ /atlas/usatlas /cms/Role=pilot /cms/local/Role=pilot Traditionally, sites have made local accounting and scheduling decisions based on the first VOMS FQAN so collaborations should set the first group/role in wlcg.groups to the most specific group or role. For example: wlcg.groups = /cms/Role=pilot, /cms Instead of: wlcg.groups = /cms, /cms/Role=pilot Help \u00b6 To get assistance, please use the this page .","title":"Collaborations and Bearer Tokens"},{"location":"policy/collab-bearer-tokens/#collaborations-and-bearer-tokens","text":"Sites in the OSG grant access to their grid services based on client's association with a specific collaboration (i.e. VO) instead of granting access on a per-user basis. In the past, this type of access was provided through X.509 proxies with VOMS attributes to demonstrate assocation with a collaboration: Users (both human and robots) would request that their collaboration sign their X.509 proxies (usually through a VOMS server), Or in the case of automated services (i.e. pilot job submission) a collaboration could directly create and sign proxies themselves Now, sites can authenticate and authorize clients presenting bearer tokens, such as SciTokens or WLCG tokens. This document describes how collaborations can issue bearer tokens for the aforementioned use cases in ways that are compatible with OSG sites.","title":"Collaborations and Bearer Tokens"},{"location":"policy/collab-bearer-tokens/#issuers","text":"To generate bearer tokens, a collaboration must adminster at least one \"token issuer\" to issue tokens to their users. In addition to generating and signing tokens, token issuers provide a public endpoint that can be used to validate an issued token, e.g. an OSG Compute Entrypoint (CE) will contact the token issuer to authorize a bearer token used for pilot job submission. Token issuer uptime Due to the centralized nature of bearer token validation, token issuers should be treated as critical, highly available services. Otherwise, a token issuer outage will result in OSG sites being unable to authenticate a collaboration's tokens, meaning an interruption in pilot job submission and authenticated data transfers. Choose one of the token issuer types below, depending on the needs of your collaboration.","title":"Issuers"},{"location":"policy/collab-bearer-tokens/#simple-issuer","text":"If your collaboration centrally administers all services requiring bearer tokens and your users do not need to directly manage bearer tokens, consider running a simple token issuer. A simple token issuer consists of a public/private certificate keypair where the private key is used to issue tokens directly and the public certificate is made available through a web server. For example, the OSPool (n\u00e9e OSG VO) serves its public certificate through GitHub pages and uses the private key to sign tokens used for pilot job submission as well as automatically generating tokens to accompany user jobs so that they can access their private storage areas.","title":"Simple issuer"},{"location":"policy/collab-bearer-tokens/#oauth2openid-connect","text":"If your collaboration distributes administrative responsibility or your users need to request and manage their own tokens, you should administer an OAuth2/OpenID Connect (OIDC) service (e.g., INDIGO IAM ) or work with an existing OAuth2/OIDC provider (e.g., CILogon ). For example, Fermilab uses CILogon as their OIDC provider combined with an HTVault server used to streamline the OIDC process for users and integrate with their local Kerberos.","title":"OAuth2/OpenID Connect"},{"location":"policy/collab-bearer-tokens/#claims","text":"Bearer tokens are self-describing credentials that enumerate their capabilities as \"claims\" and different token \"profiles\" enumerate common sets of claims. OSG sites support the following bearer token profiles: SciTokens WLCG tokens Claims are further described below with recommendations to ensure the greatest compatibility with OSG sites.","title":"Claims"},{"location":"policy/collab-bearer-tokens/#scope","text":"The scope claim is a space-separated list of authorizations that should be granted to the bearer. Scopes utilized by OSG services include the following: Capability SciTokens scope WLCG scope HTCondor READ condor:/READ compute.read HTCondor WRITE condor:/WRITE compute.modify compute.cancel compute.create XRootD read read:<PATH> storage.read:<PATH> XRootD write write:<PATH> storage.modify:<PATH> Replacing <PATH> with a path to the storage location that the bearer should be authorized to access.","title":"Scope"},{"location":"policy/collab-bearer-tokens/#issuer","text":"The issuer URL, or the iss claim, indicates the endpoint to use for authenticating a given token. A collaboration may have more than one token issuer but a single token issuer should never serve more than one collaboration. In other words, given the token issuer, the site can determine the collaboration that issued the token. The following collaborations have registered token issuers with the OSG: Collaboration Issuers ATLAS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/ATLAS.yaml CLAS12 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CLAS12.yaml CMS https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/CMS.yaml DES https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DES.yaml DUNE https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/DUNE.yaml EIC https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/EIC.yaml Fermilab https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Fermilab.yaml CHTC (n\u00e9e GLOW) https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/GLOW.yaml Gluex https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Gluex.yaml IceCube https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/IceCube.yaml LIGO https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/LIGO.yaml Mu2e https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/Mu2e.yaml OSPool https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/OSG.yaml SBND https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/SBND.yaml gm2 https://github.com/opensciencegrid/topology/blob/master/virtual-organizations/gm2.yaml The OSG distributes the osg-scitokens-mapfile RPM package that includes issuer and subject to default user mappings for use by OSG CEs.","title":"Issuer"},{"location":"policy/collab-bearer-tokens/#subject","text":"Subjects (i.e., the sub claim) should be unique, stable identifiers that correspond to a user or service (e.g. pilot job submission). In other words, subjects combined with a token issuer can be used for suspending access for a given collaboration user, user-level accounting, monitoring, auditing, or tracing. In tandem with a token issuer URL (i.e., the iss claim), subjects can be used by site HTCondor-CE or XRootD services to map to a local identity. Privacy considerations Depending on your collaboration's userbase and contributing sites, you may have to take privacy concerns, such as the GDPR into account when assigning subjects to users. Thus, it may be preferable to assign users a randomly-generated string as their sub .","title":"Subject"},{"location":"policy/collab-bearer-tokens/#audience","text":"To take advantage of the improved security posture of bearer tokens, we recommend that the aud claim be set to the intended host. For example, tokens used for submission to an HTCondor-CE should set the following: aud = <CE FQDN>:<CE PORT>","title":"Audience"},{"location":"policy/collab-bearer-tokens/#wlcg-groups","text":"WLCG tokens may have the wlcg.groups claim consisting of a comma and space separated list of collaboration groups. The format of these groups are similar to VOMS FQANs: /<collaboration>[/<group>][/Role=<role>] , replacing <collaboration> , <group> , and <role> with the collaboration, group, and role, respectively, where the group and role are optional. For example, the following groups and roles have been used by the ATLAS and CMS collaborations: /atlas/ /atlas/usatlas /cms/Role=pilot /cms/local/Role=pilot Traditionally, sites have made local accounting and scheduling decisions based on the first VOMS FQAN so collaborations should set the first group/role in wlcg.groups to the most specific group or role. For example: wlcg.groups = /cms/Role=pilot, /cms Instead of: wlcg.groups = /cms, /cms/Role=pilot","title":"WLCG groups"},{"location":"policy/collab-bearer-tokens/#help","text":"To get assistance, please use the this page .","title":"Help"},{"location":"policy/community-testing/","text":"OSG Community Software Testing \u00b6 8 October 2019 The community of OSG resource providers has a vested interest in the quality and stability of the OSG software stack. We would like to notify our stakeholders of software updates as soon as they are designated as \"Ready for Testing\" by the Software Team. Direct engagement with the entire community would allow for feedback from a broader array of interested parties. Combined with our flexible release model , we hope to further improve the turnaround time of new features and bug fixes. Implementation \u00b6 After the OSG Software Team builds and tests a package successfully, it is marked \"Ready for Testing\" and is added to the appropriate Yum testing repository: osg-testing and osg-upcoming-testing for packages targeted for the release and the upcoming release, respectively. Upon addition to the relevant testing repository, we intend to notify OSG site administrators that the package, or a logically connected group of packages, is available for testing with a description of changes compared to previously released versions and provide a forum by which interested users can provide feedback. Additionally, any packages that are considered release candidates by their upstream authors will be noted as such. The Software and Release team will classify packages as either \"major\" or \"minor\"; where major packages are deemed critical to the functionality of the production grid and all other packages are minor. For major packages, we will notify site administrators as soon as they are eligible for testing; minor packages eligible for testing will be collected and announced in a weekly digest. After users have been notified of changes, minor packages will be marked eligible for release if they have not received negative feedback after 7 calendar days. In addition to the above requirements, major packages must also receive positive feedback and be approved by the Release Manager. If a major package has not received feedback after four weeks and it has been sufficiently tested by OSG integration tests, the Release Manager may approve the package for release. If a package receives negative feedback, the offending package will be removed from the relevant testing repository. Major Packages \u00b6 The following packages are considered critical to the production Open Science Grid: CVMFS Frontier Squid GlideinWMS Gratia Probes HTCondor HTCondor-CE stashcp XCache XRootD This list is maintained by the Release Manager with input from OSG stakeholders, the Software Manager, and the Operations Manager. Exceptions \u00b6 If an expedient release is required, the OSG Software Team may forego the community testing policy outlined above. Common exceptions to the policy include releases that contain one or more of the following: Security updates CA or VO data updates Updates that address installation or upgrade issues Version History \u00b6 2022-10-07 : All promoting of lanquishing critical packages when adequately covered by automated tests 2022-05-06 : Drop unsupported software from the critical package list 2019-10-08 : Add policy exceptions 2019-08-12 : Add notification frequency details 2019-02-20 : Initial policy","title":"Community Testing"},{"location":"policy/community-testing/#osg-community-software-testing","text":"8 October 2019 The community of OSG resource providers has a vested interest in the quality and stability of the OSG software stack. We would like to notify our stakeholders of software updates as soon as they are designated as \"Ready for Testing\" by the Software Team. Direct engagement with the entire community would allow for feedback from a broader array of interested parties. Combined with our flexible release model , we hope to further improve the turnaround time of new features and bug fixes.","title":"OSG Community Software Testing"},{"location":"policy/community-testing/#implementation","text":"After the OSG Software Team builds and tests a package successfully, it is marked \"Ready for Testing\" and is added to the appropriate Yum testing repository: osg-testing and osg-upcoming-testing for packages targeted for the release and the upcoming release, respectively. Upon addition to the relevant testing repository, we intend to notify OSG site administrators that the package, or a logically connected group of packages, is available for testing with a description of changes compared to previously released versions and provide a forum by which interested users can provide feedback. Additionally, any packages that are considered release candidates by their upstream authors will be noted as such. The Software and Release team will classify packages as either \"major\" or \"minor\"; where major packages are deemed critical to the functionality of the production grid and all other packages are minor. For major packages, we will notify site administrators as soon as they are eligible for testing; minor packages eligible for testing will be collected and announced in a weekly digest. After users have been notified of changes, minor packages will be marked eligible for release if they have not received negative feedback after 7 calendar days. In addition to the above requirements, major packages must also receive positive feedback and be approved by the Release Manager. If a major package has not received feedback after four weeks and it has been sufficiently tested by OSG integration tests, the Release Manager may approve the package for release. If a package receives negative feedback, the offending package will be removed from the relevant testing repository.","title":"Implementation"},{"location":"policy/community-testing/#major-packages","text":"The following packages are considered critical to the production Open Science Grid: CVMFS Frontier Squid GlideinWMS Gratia Probes HTCondor HTCondor-CE stashcp XCache XRootD This list is maintained by the Release Manager with input from OSG stakeholders, the Software Manager, and the Operations Manager.","title":"Major Packages"},{"location":"policy/community-testing/#exceptions","text":"If an expedient release is required, the OSG Software Team may forego the community testing policy outlined above. Common exceptions to the policy include releases that contain one or more of the following: Security updates CA or VO data updates Updates that address installation or upgrade issues","title":"Exceptions"},{"location":"policy/community-testing/#version-history","text":"2022-10-07 : All promoting of lanquishing critical packages when adequately covered by automated tests 2022-05-06 : Drop unsupported software from the critical package list 2019-10-08 : Add policy exceptions 2019-08-12 : Add notification frequency details 2019-02-20 : Initial policy","title":"Version History"},{"location":"policy/container-release/","text":"Container Release Policy \u00b6 16 February 2022 Container images are an increasingly popular tool for shortening the software development life cycle, allowing for speedy deployment of new software versions or additional instances of a service. Select services in the OSG Software Stack will be distributed as container images to support VOs and sites that are interested in this model. This document contains policy information for container images distributed by the OSG Software Team. Contents and Sources \u00b6 Similar to our existing RPM infrastructure, container image sources, build logs, and artifacts will be stored in publicly available repositories (e.g. GitHub, Docker Hub) for collaboration and traceability. Additionally, container images distributed by the OSG Software team will be based off of the latest version of a supported platform with software installed from OS, EPEL, and OSG Yum repositories. Tags \u00b6 OSG Software container images will be built at least weekly and tagged with the following format: <SERIES>-<REPO>[-<TIME>] Field Description <SERIES> The OSG release series used for software installation. Possible values: 3.6 and 3.5 . <REPO> OSG Yum repositories used for software installation, including the corresponding upcoming repository. Possible values: release and testing . <TIME> The time that the image was built, in the format YYYYMMDD-HHMM; see below for an example. OSG Software Release Series life cycle Container images based on unsupported OSG release series will stop receiving regular updates. Immutable vs mutable tags Image tags without a build time are treated as mutable, i.e. these tags are regularly updated with the latest available software in their respective Yum repositories. Image tags with a build time are treated as immutable and do not change. For example, to deploy an Open Science Data Federation cache with the latest production software versions from OSG 3.6, use the following image tag: opensciencegrid/stash-cache:3.6-release However, to deploy a cache with software that was available in the osg-testing and osg-upcoming-testing repositories at 3:17 PM on December 17, 2021, use the following image tag: opensciencegrid/stash-cache:3.6-testing-20211217-1517 Deprecated \u00b6 Images based off of OSG 3.5 originally did not have the release series prefix. The following tags will no longer be supported after the retirement of OSG 3.5 on May 1, 2022: release-<TIME> release testing-<TIME> testing Where <TIME> is the time that the tag was built. See this page for more details on release series support. Retention \u00b6 Image tags older than 6 months will be automatically removed. Additionally, the Software Team may remove images with detected security flaws. Validation \u00b6 OSG Software container images consist of RPMs for OSG services that are tested through existing release processes as well as scripts and configuration specific to the container implementation of the service. New container images limited to RPM updates undergo additional automated testing before being published. In order to test changes to container-specific scripts or configuration, OSG Software performs automated tests and coordinates testing of release candidate images before applying these changes to the production tags . Change Log \u00b6 21 April 2022: Deprecate tags without the OSG release series 16 February 2022: Remove Docker Hub dependency from the retention policy. 22 January 2021: Modify the tagging policy to more closely track OSG Yum repositories 14 August 2020: Updated cleanup policy to match Docker Hub image retention policy. 17 April 2019: Initial policy","title":"Container Release Policy"},{"location":"policy/container-release/#container-release-policy","text":"16 February 2022 Container images are an increasingly popular tool for shortening the software development life cycle, allowing for speedy deployment of new software versions or additional instances of a service. Select services in the OSG Software Stack will be distributed as container images to support VOs and sites that are interested in this model. This document contains policy information for container images distributed by the OSG Software Team.","title":"Container Release Policy"},{"location":"policy/container-release/#contents-and-sources","text":"Similar to our existing RPM infrastructure, container image sources, build logs, and artifacts will be stored in publicly available repositories (e.g. GitHub, Docker Hub) for collaboration and traceability. Additionally, container images distributed by the OSG Software team will be based off of the latest version of a supported platform with software installed from OS, EPEL, and OSG Yum repositories.","title":"Contents and Sources"},{"location":"policy/container-release/#tags","text":"OSG Software container images will be built at least weekly and tagged with the following format: <SERIES>-<REPO>[-<TIME>] Field Description <SERIES> The OSG release series used for software installation. Possible values: 3.6 and 3.5 . <REPO> OSG Yum repositories used for software installation, including the corresponding upcoming repository. Possible values: release and testing . <TIME> The time that the image was built, in the format YYYYMMDD-HHMM; see below for an example. OSG Software Release Series life cycle Container images based on unsupported OSG release series will stop receiving regular updates. Immutable vs mutable tags Image tags without a build time are treated as mutable, i.e. these tags are regularly updated with the latest available software in their respective Yum repositories. Image tags with a build time are treated as immutable and do not change. For example, to deploy an Open Science Data Federation cache with the latest production software versions from OSG 3.6, use the following image tag: opensciencegrid/stash-cache:3.6-release However, to deploy a cache with software that was available in the osg-testing and osg-upcoming-testing repositories at 3:17 PM on December 17, 2021, use the following image tag: opensciencegrid/stash-cache:3.6-testing-20211217-1517","title":"Tags"},{"location":"policy/container-release/#deprecated","text":"Images based off of OSG 3.5 originally did not have the release series prefix. The following tags will no longer be supported after the retirement of OSG 3.5 on May 1, 2022: release-<TIME> release testing-<TIME> testing Where <TIME> is the time that the tag was built. See this page for more details on release series support.","title":"Deprecated"},{"location":"policy/container-release/#retention","text":"Image tags older than 6 months will be automatically removed. Additionally, the Software Team may remove images with detected security flaws.","title":"Retention"},{"location":"policy/container-release/#validation","text":"OSG Software container images consist of RPMs for OSG services that are tested through existing release processes as well as scripts and configuration specific to the container implementation of the service. New container images limited to RPM updates undergo additional automated testing before being published. In order to test changes to container-specific scripts or configuration, OSG Software performs automated tests and coordinates testing of release candidate images before applying these changes to the production tags .","title":"Validation"},{"location":"policy/container-release/#change-log","text":"21 April 2022: Deprecate tags without the OSG release series 16 February 2022: Remove Docker Hub dependency from the retention policy. 22 January 2021: Modify the tagging policy to more closely track OSG Yum repositories 14 August 2020: Updated cleanup policy to match Docker Hub image retention policy. 17 April 2019: Initial policy","title":"Change Log"},{"location":"policy/cream-support/","text":"OSG/HTCondor CREAM-CE Support \u00b6 The CREAM working group has recently announced official support for the CREAM-CE will cease in December 2020. With this email, we are soliciting feedback on OSG and HTCondor\u2019s transition plan. OSG and HTCondor remain committed to supporting VOs who need to access to CREAM-CE based resources throughout the transition period; we will continue to support submission to CREAM-CE endpoints and offer assistance to VOs to manage the transition. OSG runs a glidein submission service that submits to grid infrastructures worldwide on behalf of dozens of science projects. This service currently submits to approximately 100 CREAM-CE endpoints; we will continue to maintain the capability to access these endpoints while we assist sites in testing and enabling ARC-CE and/or HTCondor-CE replacement services. The HTCondor team plans to support the CREAM-CE on EL6/7 in the 8.8.x stable release series and will maintain support for 8.8.x through December 2020. CREAM-CE support will remain enabled at the start of the 8.9.x developer series; in early 2020, the HTCondor team will re-evaluate, based on community need, whether CREAM-CE support will be available in the next stable series. We realize that software retirements can be very disruptive; the OSG and HTCondor teams are committed to assisting user communities through the process. If you believe our plan does not fit the needs of your user community, please contact help@osg-htc.org . Regards, Brian Bockelman, OSG Technology Area Coordinator Todd Tannenbaum, HTCondor Technical Lead Reference \u00b6 EGI broadcast about CREAM retirement ; the EGI link requires authentication; statement has been reproduced below: Dear Users The CREAM working group has announced that official support for the CREAM-CE component will cease at the end of the EOSC-hub project, i.e. in Dec 2020. To prepare for this, EGI Foundation and CERN are actively working to help to minimise disruption. This will include helping users migrate to alternative solutions, i.e. ARC-CE or HTCondor-CE. The CREAM working group will be providing full support until the end of 2019, including one minor release already scheduled. During 2020 only security updates will be released. If you have any concerns or queries, please open a support ticket at https://ggus.eu/ Best regards EGI Foundation and CERN Operations Teams","title":"CREAM-CE Support"},{"location":"policy/cream-support/#osghtcondor-cream-ce-support","text":"The CREAM working group has recently announced official support for the CREAM-CE will cease in December 2020. With this email, we are soliciting feedback on OSG and HTCondor\u2019s transition plan. OSG and HTCondor remain committed to supporting VOs who need to access to CREAM-CE based resources throughout the transition period; we will continue to support submission to CREAM-CE endpoints and offer assistance to VOs to manage the transition. OSG runs a glidein submission service that submits to grid infrastructures worldwide on behalf of dozens of science projects. This service currently submits to approximately 100 CREAM-CE endpoints; we will continue to maintain the capability to access these endpoints while we assist sites in testing and enabling ARC-CE and/or HTCondor-CE replacement services. The HTCondor team plans to support the CREAM-CE on EL6/7 in the 8.8.x stable release series and will maintain support for 8.8.x through December 2020. CREAM-CE support will remain enabled at the start of the 8.9.x developer series; in early 2020, the HTCondor team will re-evaluate, based on community need, whether CREAM-CE support will be available in the next stable series. We realize that software retirements can be very disruptive; the OSG and HTCondor teams are committed to assisting user communities through the process. If you believe our plan does not fit the needs of your user community, please contact help@osg-htc.org . Regards, Brian Bockelman, OSG Technology Area Coordinator Todd Tannenbaum, HTCondor Technical Lead","title":"OSG/HTCondor CREAM-CE Support"},{"location":"policy/cream-support/#reference","text":"EGI broadcast about CREAM retirement ; the EGI link requires authentication; statement has been reproduced below: Dear Users The CREAM working group has announced that official support for the CREAM-CE component will cease at the end of the EOSC-hub project, i.e. in Dec 2020. To prepare for this, EGI Foundation and CERN are actively working to help to minimise disruption. This will include helping users migrate to alternative solutions, i.e. ARC-CE or HTCondor-CE. The CREAM working group will be providing full support until the end of 2019, including one minor release already scheduled. During 2020 only security updates will be released. If you have any concerns or queries, please open a support ticket at https://ggus.eu/ Best regards EGI Foundation and CERN Operations Teams","title":"Reference"},{"location":"policy/external-oasis-repos/","text":"Policy for OSG Mirroring of External CVMFS repositories \u00b6 12 October 2017 This document provides an overview of the policies and security understanding with regards to OSG mirroring of CVMFS repositories of external organizations. It aims to help external repositories and OSG VOs understand what OSG is attempting to achieve with the mirroring service. This is not a service-level agreement but rather a statement of responsibilities. Note To actually understand the technical procedure for mirroring a repository, see the following page . This document solely covers the policy aspects. Introduction \u00b6 The OSG provides a network of CVMFS Stratum-1 servers for mirroring content of externally-managed repositories. These repositories are often hosted by large HEP or physics VOs for the purpose of distributing software for high-throughput computing jobs. Additionally, OSG provides a repository ( ) for smaller VOs; this is not covered here. OSG will include additional repositories into the content distribution network (CDN) at the request of an OSG-affiliated VO. These repositories are meant to help the OSG-affiliated VO accomplish their domain science. The goal of this mirroring provides an improved quality-of-service for the VO end-users running at OSG sites. OSG does not provide support for use of the software in external repositories, but will help end-users contact the VO for help as necessary. OSG Responsibilities \u00b6 OSG will provide the Stratum-1 server network according to the OASIS SLA OSG will provide a best-effort mirror of the full contents of the external repo. We will attempt to provide best-effort integrity of the object contents, but assume users of the Stratum-1 will do further integrity checking. No SLA is provided covering potential data corruptions. OSG will provide best-effort notification to the mirrored repository in case OSG detects a service outage of the external repo. In the event of a security incident, the operations group will replace the compromised repository with an empty directory, signed by the key managed by them. This will be done in consultation with the security team or, in the unlikely event they cannot be reached, at the discretion of the Operations Coordinator. Once the external repository is approved, OSG will distribute the corresponding repository signing keys in a valid whitelist. The whitelist will be signed by the OSG Stratum-0. This whitelist attests to the authenticity of the key, but not a statement about repository contents. VO Responsibilities \u00b6 The individual responsible on behalf of the VO will be registered with the OASIS Manager role in OIM. The requesting VO should only include targeted repositories they need to support their science. The VO should understand that in the event of a reported security incident, the contents of this repository may be replaced with an empty directory and signed by the OSG repository key. Depending on the OSG Security team's evaluation of the severity and urgency of the incident, the blanking may be done immediately without VO notification or after some notification period. In the case of a security incident, the VO and OSG Security team will need to mutually agree that the incident is resolved before the repository is unblanked. The VO is ultimately responsible for the contents of the repository. OSG provides a mirror. If the external repository is not operated by the VO, OSG may work directly with the external repository maintainers. This is done for ease of operations and may be limited to day-to-day, non-security-related support. Operational Policies \u00b6 To help us provide the best operational setup possible, we have a few additional replication policies: OSG Operations only hosts the shared oasis.opensciencegrid.org repository; VO-dedicated software respositories (such as nova.opensciencegrid.org for the NoVA VO) should be operated by the VO. VOs are asked to either run their own repository or utilize the shared repository, but not both. There is a finite amount of high-performance storage on the CDN. A minimum of 100 GB per repository is guaranteed. Larger limits may be requested. VOs may ask the OSG to replicate their repositories to the European Grid Infrastructure (EGI); however, this can only be done if the repository name ends in .opensciencegrid.org .","title":"OASIS Repository Mirroring"},{"location":"policy/external-oasis-repos/#policy-for-osg-mirroring-of-external-cvmfs-repositories","text":"12 October 2017 This document provides an overview of the policies and security understanding with regards to OSG mirroring of CVMFS repositories of external organizations. It aims to help external repositories and OSG VOs understand what OSG is attempting to achieve with the mirroring service. This is not a service-level agreement but rather a statement of responsibilities. Note To actually understand the technical procedure for mirroring a repository, see the following page . This document solely covers the policy aspects.","title":"Policy for OSG Mirroring of External CVMFS repositories"},{"location":"policy/external-oasis-repos/#introduction","text":"The OSG provides a network of CVMFS Stratum-1 servers for mirroring content of externally-managed repositories. These repositories are often hosted by large HEP or physics VOs for the purpose of distributing software for high-throughput computing jobs. Additionally, OSG provides a repository ( ) for smaller VOs; this is not covered here. OSG will include additional repositories into the content distribution network (CDN) at the request of an OSG-affiliated VO. These repositories are meant to help the OSG-affiliated VO accomplish their domain science. The goal of this mirroring provides an improved quality-of-service for the VO end-users running at OSG sites. OSG does not provide support for use of the software in external repositories, but will help end-users contact the VO for help as necessary.","title":"Introduction"},{"location":"policy/external-oasis-repos/#osg-responsibilities","text":"OSG will provide the Stratum-1 server network according to the OASIS SLA OSG will provide a best-effort mirror of the full contents of the external repo. We will attempt to provide best-effort integrity of the object contents, but assume users of the Stratum-1 will do further integrity checking. No SLA is provided covering potential data corruptions. OSG will provide best-effort notification to the mirrored repository in case OSG detects a service outage of the external repo. In the event of a security incident, the operations group will replace the compromised repository with an empty directory, signed by the key managed by them. This will be done in consultation with the security team or, in the unlikely event they cannot be reached, at the discretion of the Operations Coordinator. Once the external repository is approved, OSG will distribute the corresponding repository signing keys in a valid whitelist. The whitelist will be signed by the OSG Stratum-0. This whitelist attests to the authenticity of the key, but not a statement about repository contents.","title":"OSG Responsibilities"},{"location":"policy/external-oasis-repos/#vo-responsibilities","text":"The individual responsible on behalf of the VO will be registered with the OASIS Manager role in OIM. The requesting VO should only include targeted repositories they need to support their science. The VO should understand that in the event of a reported security incident, the contents of this repository may be replaced with an empty directory and signed by the OSG repository key. Depending on the OSG Security team's evaluation of the severity and urgency of the incident, the blanking may be done immediately without VO notification or after some notification period. In the case of a security incident, the VO and OSG Security team will need to mutually agree that the incident is resolved before the repository is unblanked. The VO is ultimately responsible for the contents of the repository. OSG provides a mirror. If the external repository is not operated by the VO, OSG may work directly with the external repository maintainers. This is done for ease of operations and may be limited to day-to-day, non-security-related support.","title":"VO Responsibilities"},{"location":"policy/external-oasis-repos/#operational-policies","text":"To help us provide the best operational setup possible, we have a few additional replication policies: OSG Operations only hosts the shared oasis.opensciencegrid.org repository; VO-dedicated software respositories (such as nova.opensciencegrid.org for the NoVA VO) should be operated by the VO. VOs are asked to either run their own repository or utilize the shared repository, but not both. There is a finite amount of high-performance storage on the CDN. A minimum of 100 GB per repository is guaranteed. Larger limits may be requested. VOs may ask the OSG to replicate their repositories to the European Grid Infrastructure (EGI); however, this can only be done if the repository name ends in .opensciencegrid.org .","title":"Operational Policies"},{"location":"policy/flexible-release-model/","text":"OSG Software Flexible Release Model \u00b6 Introduction \u00b6 Before November 2017, the OSG software stack was released on the second Tuesday of each month, except in the case of urgent releases, which were infrequent. This schedule had been in place since early 2013. Since then, conditions within and outside of the Software team have changed, and we have adjusted the release schedule and associated processes. The previous release model had the recurring problem of a \"release crunch,\" where it was difficult to find the effort required to test large changes before their deadline had passed. Sometimes the lack of timely effort led to software being pushed to the next release (a month later), because there was insufficient testing time. Based on software support tickets, we noticed that many sites follow a local update schedule that is independent of the OSG Release team schedule; some sites upgrade every few months, skipping interim releases, other sites upgrade individual packages as needed. In addition, upstream software developers do not follow our release schedule either, releasing software on their own development timelines. As a result, some site administrators would prefer to have OSG software updates more often, closer to when they become available, rather than tied to a monthly cycle. For these reasons, we created a new release model. Release Model \u00b6 The OSG Release team releases batches of integrated, tested software on an ad hoc basis, with the process outlined below (changes from the old process are highlighted): Software and Release Team members develop packages and mark them for testing Software and Release Team members test the packages, possibly with help from the community Once adequate testing is complete and successful, the Release Manager approves packages for release Weekly, the Release Manager evaluates packages that are ready for release; when a sufficient number of important packages are ready [1] , the Release Manager schedules a release date and announces it. For urgent changes, the Release Manager evaluates the packages as soon as they are tested The Software and Release Team performs pre-release testing, releases the packages, and announces the release Note: The release dates of parallel release series (e.g., 3.3 and 3.4) do not have to coincide, as they have in the past. [1] The threshold for \u201csufficient number of important packages\u201d is determined by the Release Manager, with input from the other Technology Area leaders.","title":"Flexible Release Model"},{"location":"policy/flexible-release-model/#osg-software-flexible-release-model","text":"","title":"OSG Software Flexible Release Model"},{"location":"policy/flexible-release-model/#introduction","text":"Before November 2017, the OSG software stack was released on the second Tuesday of each month, except in the case of urgent releases, which were infrequent. This schedule had been in place since early 2013. Since then, conditions within and outside of the Software team have changed, and we have adjusted the release schedule and associated processes. The previous release model had the recurring problem of a \"release crunch,\" where it was difficult to find the effort required to test large changes before their deadline had passed. Sometimes the lack of timely effort led to software being pushed to the next release (a month later), because there was insufficient testing time. Based on software support tickets, we noticed that many sites follow a local update schedule that is independent of the OSG Release team schedule; some sites upgrade every few months, skipping interim releases, other sites upgrade individual packages as needed. In addition, upstream software developers do not follow our release schedule either, releasing software on their own development timelines. As a result, some site administrators would prefer to have OSG software updates more often, closer to when they become available, rather than tied to a monthly cycle. For these reasons, we created a new release model.","title":"Introduction"},{"location":"policy/flexible-release-model/#release-model","text":"The OSG Release team releases batches of integrated, tested software on an ad hoc basis, with the process outlined below (changes from the old process are highlighted): Software and Release Team members develop packages and mark them for testing Software and Release Team members test the packages, possibly with help from the community Once adequate testing is complete and successful, the Release Manager approves packages for release Weekly, the Release Manager evaluates packages that are ready for release; when a sufficient number of important packages are ready [1] , the Release Manager schedules a release date and announces it. For urgent changes, the Release Manager evaluates the packages as soon as they are tested The Software and Release Team performs pre-release testing, releases the packages, and announces the release Note: The release dates of parallel release series (e.g., 3.3 and 3.4) do not have to coincide, as they have in the past. [1] The threshold for \u201csufficient number of important packages\u201d is determined by the Release Manager, with input from the other Technology Area leaders.","title":"Release Model"},{"location":"policy/globus-toolkit/","text":"OSG Support of the Globus Toolkit \u00b6 Gridftp and GSI Migration Plan In December 2019, the OSG developed a plan for migrating the OSG Software stack away from GridFTP and GSI that can be found here . 6 June 2017 Many in the OSG community have heard the news about the end of support for the open-source Globus Toolkit (formerly available from https://github.com/globus/globus-toolkit/blob/globus_6_branch/support-changes). What does this imply for the OSG Software stack? Not much: OSG support for the Globus Toolkit (e.g., GridFTP and GSI) will continue for as long as stakeholders need it. Period. Note the OSG Software team provides a support guarantee for all the software in its stack. When a software component reaches end-of-life, the OSG assists its stakeholders in managing the transition to new software to replace or extend those capabilities. This assistance comes in many forms, such as finding an equivalent replacement, adapting code to avoid the dependency, or helping research and develop a transition to new technology. During such transition periods, OSG takes on traditional maintenance duties (i.e., patching, bug fixes and support) of the end-of-life software. The OSG is committed to keep the software secure until its stakeholders have successfully transitioned to new software. This model has been successfully demonstrated throughout the lifetime of OSG, including for example the five year transition period for the BestMan storage resource manager. The Globus Toolkit will not be an exception. Indeed, OSG has accumulated more than a decade of experience with this software and has often provided patches back to Globus. Over the next weeks and months, we will be in contact with our stakeholder VOs, sites, and software providers to discuss their requirements and timelines with regard to GridFTP and GSI. Please reach out to goc@opensciencegrid.org with your questions, comments, and concerns. Change Log \u00b6 8 October 2020 Add note linking to the GridFTP and GSI migration plan","title":"Globus Toolkit Support"},{"location":"policy/globus-toolkit/#osg-support-of-the-globus-toolkit","text":"Gridftp and GSI Migration Plan In December 2019, the OSG developed a plan for migrating the OSG Software stack away from GridFTP and GSI that can be found here . 6 June 2017 Many in the OSG community have heard the news about the end of support for the open-source Globus Toolkit (formerly available from https://github.com/globus/globus-toolkit/blob/globus_6_branch/support-changes). What does this imply for the OSG Software stack? Not much: OSG support for the Globus Toolkit (e.g., GridFTP and GSI) will continue for as long as stakeholders need it. Period. Note the OSG Software team provides a support guarantee for all the software in its stack. When a software component reaches end-of-life, the OSG assists its stakeholders in managing the transition to new software to replace or extend those capabilities. This assistance comes in many forms, such as finding an equivalent replacement, adapting code to avoid the dependency, or helping research and develop a transition to new technology. During such transition periods, OSG takes on traditional maintenance duties (i.e., patching, bug fixes and support) of the end-of-life software. The OSG is committed to keep the software secure until its stakeholders have successfully transitioned to new software. This model has been successfully demonstrated throughout the lifetime of OSG, including for example the five year transition period for the BestMan storage resource manager. The Globus Toolkit will not be an exception. Indeed, OSG has accumulated more than a decade of experience with this software and has often provided patches back to Globus. Over the next weeks and months, we will be in contact with our stakeholder VOs, sites, and software providers to discuss their requirements and timelines with regard to GridFTP and GSI. Please reach out to goc@opensciencegrid.org with your questions, comments, and concerns.","title":"OSG Support of the Globus Toolkit"},{"location":"policy/globus-toolkit/#change-log","text":"8 October 2020 Add note linking to the GridFTP and GSI migration plan","title":"Change Log"},{"location":"policy/gridftp-gsi-migration/","text":"GridFTP and GSI Migration \u00b6 6 December 2019 Introduction \u00b6 The GridFTP protocol (for data transfer) and GSI (as an Authentication and Authorization Infrastructure, AAI) were selected for the OSG ecosystem nearly 15 years ago. In both cases, approaches are becoming increasingly niche; as they have not become widely adopted - indeed, as the communities dramatically shrink while the Internet ecosystem grows - the support costs are increasingly directly shouldered by the OSG. For example, we currently use the GridFTP and GSI implementations in the Grid Community Toolkit (GCT). While the OSG contributes to the GCT (a fork of the abandoned Globus Toolkit) to sustain operations, the long-term plan is to migrate our community off these approaches. The end of the Globus Toolkit is a stark reminder of how niche the current ecosystem is: even the original reference implementation was abandoned. Thus, OSG has the opportunity and motivation to evolve toward a data transfer protocol and security techniques that better fit our needs and allow us to connect to more vibrant software communities. For the data transfer, we are proposing HTTP; for the AAI, we are proposing the use of bearer tokens, HTTPS, and OAuth2. The production-oriented nature of the OSG \u2014 and the embedding of OSG-LHC in the WLCG community \u2014 means that careful coordination, communication, and planning are needed whenever we migrate away from production services. OSG has executed several such technology transitions before and managing the full software lifecycle is part of our value to stakeholders. This document proposes affected services, replacement technologies, and rough timelines for a transition. Timeline \u00b6 The following table contains the major milestones and deliverables for the entire transition. Detailed migration plans can be found in this document . Date Milestone or Deliverable Completed Aug 2019 Beginning of OSG 3.5 release series (last release series depending on GCT) \u2705 Aug 2019 Including HTCondor 8.9.2 in the \u2018upcoming\u2019 repository (first HTCondor version with SciTokens support). \u2705 Oct 2019 OSG no longer carries OSG-specific patches for the GCT. All patches are upstreamed or retired. \u2705 Mar 2020 \"GSI free\" site demo. Show, at proof-of-concept / prototype level, all components without use of GCT. \u2705 Sep 2020 All GCT-free components are in OSG-Upcoming. \u2705 Feb 2021 OSG series 3.6, without GCT dependencies, is released. \u2705 1 May 2022 End of support for OSG 3.5. \u2705 Frequently Asked Questions \u00b6 How does SciTokens interoperate with other token technologies in the WLCG? \u00b6 The scitokens-cpp library used by OSG can transparently use both WLCG JSON Web Tokens (JWTs) and SciTokens. Will a US-LHC migration from GridFTP to XRootD require the same migration for WLCG? \u00b6 No but we have been working to ensure that we coordinate our activities through the WLCG DOMA group. What role does LCMAPS play with SciTokens? \u00b6 LCMAPS only works with GSI. The model for SciTokens is sufficiently more simple for sites that the full complexity of LCMAPS is not needed. What does a SciTokens transition for GlideinWMS mean for European sites? \u00b6 The only piece that involves European sites is the factory to CE relationship: given HTCondor-CE 4.0 already supports SciTokens, we have begun to engage with the ARC-CE team. What are the T1s going to do? No SRM? How does tape work with XRootD and HTTPS? \u00b6 Note that CTA, which CERN is planning to transition to this year, only has XRootD support. We don't think there's a clear HTTPS picture here (or a clear dCache picture for SRM-free) so there will need to be coordination with other groups (e.g. the QoS working group). Can WLCG-FTS handle both SciTokens and x509 certificates at the same time? \u00b6 Yes. Can PhEDEx handle SciTokens? \u00b6 Yes. Version History \u00b6 2021-03-05 : Updated dates for the initial OSG 3.6 release and the targeted OSG 3.5 retirement 2020-03-30 : Completed GSI-free site demonstration 2020-03-17 : Highlighted delay in Jan 2020 milestone and new expected completion date of Mar 2020 2020-03-16 : Updated completed items on the overall timeline; added link for detailed document","title":"GridFTP and GSI Migration"},{"location":"policy/gridftp-gsi-migration/#gridftp-and-gsi-migration","text":"6 December 2019","title":"GridFTP and GSI Migration"},{"location":"policy/gridftp-gsi-migration/#introduction","text":"The GridFTP protocol (for data transfer) and GSI (as an Authentication and Authorization Infrastructure, AAI) were selected for the OSG ecosystem nearly 15 years ago. In both cases, approaches are becoming increasingly niche; as they have not become widely adopted - indeed, as the communities dramatically shrink while the Internet ecosystem grows - the support costs are increasingly directly shouldered by the OSG. For example, we currently use the GridFTP and GSI implementations in the Grid Community Toolkit (GCT). While the OSG contributes to the GCT (a fork of the abandoned Globus Toolkit) to sustain operations, the long-term plan is to migrate our community off these approaches. The end of the Globus Toolkit is a stark reminder of how niche the current ecosystem is: even the original reference implementation was abandoned. Thus, OSG has the opportunity and motivation to evolve toward a data transfer protocol and security techniques that better fit our needs and allow us to connect to more vibrant software communities. For the data transfer, we are proposing HTTP; for the AAI, we are proposing the use of bearer tokens, HTTPS, and OAuth2. The production-oriented nature of the OSG \u2014 and the embedding of OSG-LHC in the WLCG community \u2014 means that careful coordination, communication, and planning are needed whenever we migrate away from production services. OSG has executed several such technology transitions before and managing the full software lifecycle is part of our value to stakeholders. This document proposes affected services, replacement technologies, and rough timelines for a transition.","title":"Introduction"},{"location":"policy/gridftp-gsi-migration/#timeline","text":"The following table contains the major milestones and deliverables for the entire transition. Detailed migration plans can be found in this document . Date Milestone or Deliverable Completed Aug 2019 Beginning of OSG 3.5 release series (last release series depending on GCT) \u2705 Aug 2019 Including HTCondor 8.9.2 in the \u2018upcoming\u2019 repository (first HTCondor version with SciTokens support). \u2705 Oct 2019 OSG no longer carries OSG-specific patches for the GCT. All patches are upstreamed or retired. \u2705 Mar 2020 \"GSI free\" site demo. Show, at proof-of-concept / prototype level, all components without use of GCT. \u2705 Sep 2020 All GCT-free components are in OSG-Upcoming. \u2705 Feb 2021 OSG series 3.6, without GCT dependencies, is released. \u2705 1 May 2022 End of support for OSG 3.5. \u2705","title":"Timeline"},{"location":"policy/gridftp-gsi-migration/#frequently-asked-questions","text":"","title":"Frequently Asked Questions"},{"location":"policy/gridftp-gsi-migration/#how-does-scitokens-interoperate-with-other-token-technologies-in-the-wlcg","text":"The scitokens-cpp library used by OSG can transparently use both WLCG JSON Web Tokens (JWTs) and SciTokens.","title":"How does SciTokens interoperate with other token technologies in the WLCG?"},{"location":"policy/gridftp-gsi-migration/#will-a-us-lhc-migration-from-gridftp-to-xrootd-require-the-same-migration-for-wlcg","text":"No but we have been working to ensure that we coordinate our activities through the WLCG DOMA group.","title":"Will a US-LHC migration from GridFTP to XRootD require the same migration for WLCG?"},{"location":"policy/gridftp-gsi-migration/#what-role-does-lcmaps-play-with-scitokens","text":"LCMAPS only works with GSI. The model for SciTokens is sufficiently more simple for sites that the full complexity of LCMAPS is not needed.","title":"What role does LCMAPS play with SciTokens?"},{"location":"policy/gridftp-gsi-migration/#what-does-a-scitokens-transition-for-glideinwms-mean-for-european-sites","text":"The only piece that involves European sites is the factory to CE relationship: given HTCondor-CE 4.0 already supports SciTokens, we have begun to engage with the ARC-CE team.","title":"What does a SciTokens transition for GlideinWMS mean for European sites?"},{"location":"policy/gridftp-gsi-migration/#what-are-the-t1s-going-to-do-no-srm-how-does-tape-work-with-xrootd-and-https","text":"Note that CTA, which CERN is planning to transition to this year, only has XRootD support. We don't think there's a clear HTTPS picture here (or a clear dCache picture for SRM-free) so there will need to be coordination with other groups (e.g. the QoS working group).","title":"What are the T1s going to do? No SRM? How does tape work with XRootD and HTTPS?"},{"location":"policy/gridftp-gsi-migration/#can-wlcg-fts-handle-both-scitokens-and-x509-certificates-at-the-same-time","text":"Yes.","title":"Can WLCG-FTS handle both SciTokens and x509 certificates at the same time?"},{"location":"policy/gridftp-gsi-migration/#can-phedex-handle-scitokens","text":"Yes.","title":"Can PhEDEx handle SciTokens?"},{"location":"policy/gridftp-gsi-migration/#version-history","text":"2021-03-05 : Updated dates for the initial OSG 3.6 release and the targeted OSG 3.5 retirement 2020-03-30 : Completed GSI-free site demonstration 2020-03-17 : Highlighted delay in Jan 2020 milestone and new expected completion date of Mar 2020 2020-03-16 : Updated completed items on the overall timeline; added link for detailed document","title":"Version History"},{"location":"policy/gums-retire/","text":"GUMS Retirement \u00b6 This document provides an overview of the planned retirement of support for GUMS in the OSG Software Stack. Introduction \u00b6 GUMS (Grid User Management System) is an authentication system used by OSG resource providers to map grid credentials to local UNIX accounts. It provides OSG site adminstrators with a centrally managed service that can handle requests from multiple hosts that require authentication e.g., HTCondor-CE, GridFTP, and XRootD servers. In discussion with the OSG community, we have found that sites use the following GUMS features: Mapping based on VOMS attributes Host-based mappings Banning users/VOs Supporting pool accounts GUMS is a large Java web application that is more complex than necessary for the subset of features used in the OSG. Additionally, upstream support has tailed off and as a result, the maintenance burden has largely fallen on the OSG Software team. OSG's plans to retire GUMS has two major components: Find a suitable replacement for GUMS Provide documentation, tooling, and support to aid in the transition from GUMS to the intended solution Site Transition Plans \u00b6 We have released a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions. This configuration, referred to as the LCMAPS VOMS plugin, supports VOMS attribute based mappings as well as user and VO banning. Host-based mappings are not supported however, the simplicity of the plugin's installation and the distributed verification of VOMS extensions makes this feature unnecessary. Pool accounts are not supported by the plugin but this feature will be addressed in an upcoming transition-specific document. The intended solution will revolve around mapping local user accounts via user grid mapfile and we will work with any site for which this solution does not work. LCMAPS VOMS plugin installation and configuration documentation can be found here (formerly: lcmaps-voms-authentication). Timeline \u00b6 April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. July 2017 (completed): OSG 3.4 CEs can be configured with 3.3 GUMS hosts March 2018: Complete transition for sites not using pool accounts May 2018: Support is dropped for OSG 3.3 series; no further support for GUMS is provided.","title":"GUMS Retirement"},{"location":"policy/gums-retire/#gums-retirement","text":"This document provides an overview of the planned retirement of support for GUMS in the OSG Software Stack.","title":"GUMS Retirement"},{"location":"policy/gums-retire/#introduction","text":"GUMS (Grid User Management System) is an authentication system used by OSG resource providers to map grid credentials to local UNIX accounts. It provides OSG site adminstrators with a centrally managed service that can handle requests from multiple hosts that require authentication e.g., HTCondor-CE, GridFTP, and XRootD servers. In discussion with the OSG community, we have found that sites use the following GUMS features: Mapping based on VOMS attributes Host-based mappings Banning users/VOs Supporting pool accounts GUMS is a large Java web application that is more complex than necessary for the subset of features used in the OSG. Additionally, upstream support has tailed off and as a result, the maintenance burden has largely fallen on the OSG Software team. OSG's plans to retire GUMS has two major components: Find a suitable replacement for GUMS Provide documentation, tooling, and support to aid in the transition from GUMS to the intended solution","title":"Introduction"},{"location":"policy/gums-retire/#site-transition-plans","text":"We have released a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions. This configuration, referred to as the LCMAPS VOMS plugin, supports VOMS attribute based mappings as well as user and VO banning. Host-based mappings are not supported however, the simplicity of the plugin's installation and the distributed verification of VOMS extensions makes this feature unnecessary. Pool accounts are not supported by the plugin but this feature will be addressed in an upcoming transition-specific document. The intended solution will revolve around mapping local user accounts via user grid mapfile and we will work with any site for which this solution does not work. LCMAPS VOMS plugin installation and configuration documentation can be found here (formerly: lcmaps-voms-authentication).","title":"Site Transition Plans"},{"location":"policy/gums-retire/#timeline","text":"April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. July 2017 (completed): OSG 3.4 CEs can be configured with 3.3 GUMS hosts March 2018: Complete transition for sites not using pool accounts May 2018: Support is dropped for OSG 3.3 series; no further support for GUMS is provided.","title":"Timeline"},{"location":"policy/new-ospool-user/","text":"Registering for a new Open Science Pool Account \u00b6 The OSG access points at UW-Madison us the COManage identity management system to register new users. COManage uses the InCommon federation , allowing users to register with their institutional identities; there is no \"OSPool password\" that users must memorize Starting the registration process \u00b6 You can start the application for a new account by following the registration process below: Visit the new OSPool user enrollment page . You will be presented with a CILogon Single-Sign On page. Select your insitution and sign in with your insitutional credentials: Please use your institution's credentials as this simplifies the verification process; only select the Google or GitHub identity providers if your institution is not an option. After you have signed in, you will be presented with the self-signup form. Click the \"BEGIN\" button: Enter your name and email address. In most cases, your institution will provide defaults for your name and email address. If you prefer, you may override these values. If you have a GitHub account, please fill in your username. If you have already been working with an member to get the OSPool account, please select their name from the Sponsor drop-down; otherwise, leave it blank. Click the \"SUBMIT\" button: Verifying Your Email Address \u00b6 After submitting your registration application, you will receive an email from registry@cilogon.org to verify your email address. Follow the link in the email and click the \"Accept\" button to complete the verification: Adding an SSH Key \u00b6 A SSH public key (see this overview page for more information) allows for easier SSH-based login to the access point. After verifying your email address, you will be given an option to upload a public key for your account. If you are not ready to do that at this time, simply click \"skip\". ) Meeting with a Facilitator \u00b6 After verifying your email address (and optionally uploading the SSH key), a new support ticket will be generated and we will contact you to arrange a meeting with a Facilitator for an introduction to the access point and High Throughput Computing. After this initial meeting, your account will be finalized and you will be able to login to the system. Getting Help \u00b6 For assistance or questions, please email the support team at support@opensciencegrid.org","title":"New OSPool User Registration"},{"location":"policy/new-ospool-user/#registering-for-a-new-open-science-pool-account","text":"The OSG access points at UW-Madison us the COManage identity management system to register new users. COManage uses the InCommon federation , allowing users to register with their institutional identities; there is no \"OSPool password\" that users must memorize","title":"Registering for a new Open Science Pool Account"},{"location":"policy/new-ospool-user/#starting-the-registration-process","text":"You can start the application for a new account by following the registration process below: Visit the new OSPool user enrollment page . You will be presented with a CILogon Single-Sign On page. Select your insitution and sign in with your insitutional credentials: Please use your institution's credentials as this simplifies the verification process; only select the Google or GitHub identity providers if your institution is not an option. After you have signed in, you will be presented with the self-signup form. Click the \"BEGIN\" button: Enter your name and email address. In most cases, your institution will provide defaults for your name and email address. If you prefer, you may override these values. If you have a GitHub account, please fill in your username. If you have already been working with an member to get the OSPool account, please select their name from the Sponsor drop-down; otherwise, leave it blank. Click the \"SUBMIT\" button:","title":"Starting the registration process"},{"location":"policy/new-ospool-user/#verifying-your-email-address","text":"After submitting your registration application, you will receive an email from registry@cilogon.org to verify your email address. Follow the link in the email and click the \"Accept\" button to complete the verification:","title":"Verifying Your Email Address"},{"location":"policy/new-ospool-user/#adding-an-ssh-key","text":"A SSH public key (see this overview page for more information) allows for easier SSH-based login to the access point. After verifying your email address, you will be given an option to upload a public key for your account. If you are not ready to do that at this time, simply click \"skip\". )","title":"Adding an SSH Key"},{"location":"policy/new-ospool-user/#meeting-with-a-facilitator","text":"After verifying your email address (and optionally uploading the SSH key), a new support ticket will be generated and we will contact you to arrange a meeting with a Facilitator for an introduction to the access point and High Throughput Computing. After this initial meeting, your account will be finalized and you will be able to login to the system.","title":"Meeting with a Facilitator"},{"location":"policy/new-ospool-user/#getting-help","text":"For assistance or questions, please email the support team at support@opensciencegrid.org","title":"Getting Help"},{"location":"policy/service-migrations-spring-2018/","text":"Service Migrations - Spring 2018 \u00b6 The Open Science Grid (OSG) has transitioned effort from Indiana, requiring a redistribution of support and services. Some services were retired, most services were migrated to other locations (with minimal expected sites impact), and some services were migrated that resulted in significant impact on sites. This document was intended to guide OSG site administrators through these changes, highlighting where the site administrator action is required. If you have questions or concerns that are not addressed in this document, see the Getting Help section for details. Getting Help \u00b6 If you have questions or concerns that are not addressed in this document, please contact us at the usual locations: help@osg-htc.org software-discuss@opensciencegrid.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org Support Changes \u00b6 The Footprints ticketing system at https://ticket.opensciencegrid.org was used to track support and security issues as well as certificate and membership requests. This service was retired in favor of two different ticketing systems, depending on the VOs you support at your site: If your site primarily supports... Submit new tickets to... LHC VOs GGUS Anyone else Freshdesk If you experience any problems with ticketing, please contact us at help@osg-htc.org . Service-specific details \u00b6 OSG CA \u00b6 The OSG CA service offered certificate request, renewal, and revocation through the OIM web interface, the OIM REST API, and the osg-pki-tools command-line tool. This service was retired on May 31 but the OSG CA certificate remains in the IGTF distribution, so any certificates issued by the OSG CA remain valid until they expire. The OSG recommends using the following CA certificate services: For... We plan to use the following Certificate Authorities... Host Certificates InCommon and Let\u2019s Encrypt User Certificates CILogon Basic for non-LHC users LHC users should continue to request their user certificates from CERN. Web-Based services Let's Encrypt Note The semantics of Let's Encrypt certificates are different from those of previous CAs. Please see the security team's position on Let's Encrypt for the security and setup implications of switching to a Let's Encrypt host or service certificate. If you experience any problems acquiring host or service certificates, please contact us at help@osg-htc.org . Software Repository \u00b6 The OSG Software repository includes the YUM repositories, client tarballs, and CA tarballs. The physical hosting location changed during the migration but was otherwise unchanged. If you experience any problems with the OSG Software repository, please contact us at help@osg-htc.org . MyOSG and OIM \u00b6 The MyOSG service used to provide web and REST interfaces to access information about OSG resource topology, projects, and VOs. The MyOSG web interface was retired but we continue to offer the same REST interface at https://my.opensciencegrid.org . OIM served as the database for the information used by MyOSG with a web interface for data updates. The OIM web interface was retired but its data was migrated to the topology repository . Updates to the aforementioned data can be requested via email or pull request. Note Please see the OSG CA section for information regarding the OIM certificate service. If you experience any problems with MyOSG or the topology repository, please contact us at help@osg-htc.org . GRACC Accounting and WLCG Accounting \u00b6 No changes were made to the GRACC accounting service during the service migration. If you experience any problems with GRACC accounting, please contact us at help@osg-htc.org . OASIS and CVMFS \u00b6 The OASIS (OSG Application and Software Installation Service) is a service used to distribute common applications and software to OSG sites via CVMFS. The OSG hosts a CVMFS Stratum-0 for keysigning, a repository server, and a CVMFS Stratum-1. The physical hosting location of these services were moved to Nebraska without any other changes. If you experience any problems with OASIS or CVMFS, please contact us at help@osg-htc.org . VOMS Admin Server \u00b6 The OSG VOMS service was used to sign VOMS attributes for members of the OSG VO and responded to queries for a list of VO members. VOMS Admin Server is deprecated in the OSG and the OSG VOMS servers were retired as planned. RSV \u00b6 The central RSV service was a monitoring tool that displayed every service status information about OSG sites that elected to provide it. It was retired since there was no longer a need to monitor OSG site status as a whole. If you would like to monitor your OSG services, you can access the status page of your local RSV instance. Collector \u00b6 The central Collector is a central database service that provides details about pilot jobs currently running in the OSG. The physical hosting location of the central Collector was moved but there were no other changes. If you experience any problems with the central Collector, please contact us at help@osg-htc.org . Homepage \u00b6 The OSG homepage was a Wordpress instance that has been moved to a static site. If you experience any problems with the homepage, please contact us at help@osg-htc.org .","title":"Service Migrations - Spring 2018"},{"location":"policy/service-migrations-spring-2018/#service-migrations-spring-2018","text":"The Open Science Grid (OSG) has transitioned effort from Indiana, requiring a redistribution of support and services. Some services were retired, most services were migrated to other locations (with minimal expected sites impact), and some services were migrated that resulted in significant impact on sites. This document was intended to guide OSG site administrators through these changes, highlighting where the site administrator action is required. If you have questions or concerns that are not addressed in this document, see the Getting Help section for details.","title":"Service Migrations - Spring 2018"},{"location":"policy/service-migrations-spring-2018/#getting-help","text":"If you have questions or concerns that are not addressed in this document, please contact us at the usual locations: help@osg-htc.org software-discuss@opensciencegrid.org - General discussion of the OSG Software stack ( subscribe ) Slack channel - if you can't create an account, send an e-mail to help@osg-htc.org","title":"Getting Help"},{"location":"policy/service-migrations-spring-2018/#support-changes","text":"The Footprints ticketing system at https://ticket.opensciencegrid.org was used to track support and security issues as well as certificate and membership requests. This service was retired in favor of two different ticketing systems, depending on the VOs you support at your site: If your site primarily supports... Submit new tickets to... LHC VOs GGUS Anyone else Freshdesk If you experience any problems with ticketing, please contact us at help@osg-htc.org .","title":"Support Changes"},{"location":"policy/service-migrations-spring-2018/#service-specific-details","text":"","title":"Service-specific details"},{"location":"policy/service-migrations-spring-2018/#osg-ca","text":"The OSG CA service offered certificate request, renewal, and revocation through the OIM web interface, the OIM REST API, and the osg-pki-tools command-line tool. This service was retired on May 31 but the OSG CA certificate remains in the IGTF distribution, so any certificates issued by the OSG CA remain valid until they expire. The OSG recommends using the following CA certificate services: For... We plan to use the following Certificate Authorities... Host Certificates InCommon and Let\u2019s Encrypt User Certificates CILogon Basic for non-LHC users LHC users should continue to request their user certificates from CERN. Web-Based services Let's Encrypt Note The semantics of Let's Encrypt certificates are different from those of previous CAs. Please see the security team's position on Let's Encrypt for the security and setup implications of switching to a Let's Encrypt host or service certificate. If you experience any problems acquiring host or service certificates, please contact us at help@osg-htc.org .","title":"OSG CA"},{"location":"policy/service-migrations-spring-2018/#software-repository","text":"The OSG Software repository includes the YUM repositories, client tarballs, and CA tarballs. The physical hosting location changed during the migration but was otherwise unchanged. If you experience any problems with the OSG Software repository, please contact us at help@osg-htc.org .","title":"Software Repository"},{"location":"policy/service-migrations-spring-2018/#myosg-and-oim","text":"The MyOSG service used to provide web and REST interfaces to access information about OSG resource topology, projects, and VOs. The MyOSG web interface was retired but we continue to offer the same REST interface at https://my.opensciencegrid.org . OIM served as the database for the information used by MyOSG with a web interface for data updates. The OIM web interface was retired but its data was migrated to the topology repository . Updates to the aforementioned data can be requested via email or pull request. Note Please see the OSG CA section for information regarding the OIM certificate service. If you experience any problems with MyOSG or the topology repository, please contact us at help@osg-htc.org .","title":"MyOSG and OIM"},{"location":"policy/service-migrations-spring-2018/#gracc-accounting-and-wlcg-accounting","text":"No changes were made to the GRACC accounting service during the service migration. If you experience any problems with GRACC accounting, please contact us at help@osg-htc.org .","title":"GRACC Accounting and WLCG Accounting"},{"location":"policy/service-migrations-spring-2018/#oasis-and-cvmfs","text":"The OASIS (OSG Application and Software Installation Service) is a service used to distribute common applications and software to OSG sites via CVMFS. The OSG hosts a CVMFS Stratum-0 for keysigning, a repository server, and a CVMFS Stratum-1. The physical hosting location of these services were moved to Nebraska without any other changes. If you experience any problems with OASIS or CVMFS, please contact us at help@osg-htc.org .","title":"OASIS and CVMFS"},{"location":"policy/service-migrations-spring-2018/#voms-admin-server","text":"The OSG VOMS service was used to sign VOMS attributes for members of the OSG VO and responded to queries for a list of VO members. VOMS Admin Server is deprecated in the OSG and the OSG VOMS servers were retired as planned.","title":"VOMS Admin Server"},{"location":"policy/service-migrations-spring-2018/#rsv","text":"The central RSV service was a monitoring tool that displayed every service status information about OSG sites that elected to provide it. It was retired since there was no longer a need to monitor OSG site status as a whole. If you would like to monitor your OSG services, you can access the status page of your local RSV instance.","title":"RSV"},{"location":"policy/service-migrations-spring-2018/#collector","text":"The central Collector is a central database service that provides details about pilot jobs currently running in the OSG. The physical hosting location of the central Collector was moved but there were no other changes. If you experience any problems with the central Collector, please contact us at help@osg-htc.org .","title":"Collector"},{"location":"policy/service-migrations-spring-2018/#homepage","text":"The OSG homepage was a Wordpress instance that has been moved to a static site. If you experience any problems with the homepage, please contact us at help@osg-htc.org .","title":"Homepage"},{"location":"policy/software-release/","text":"Software Release Policy \u00b6 This document contains information about the OSG Software Yum repositories and their policies. For details regarding the technical process for an OSG release, see this document . Yum Repositories \u00b6 The Software Team maintains the following Yum repositories: osg-development : This is the \"wild west\", the place where software goes while it is being worked on by the software team. osg-testing : This is where software goes when it is ready for wide-spread testing, including upstream release candidates osg-prerelease : This is where software goes just before being released, for final verification. osg-release : This is the official, production release of the software stack. This is the main repository for end-users. osg-contrib : This is where software goes that is not officially supported by the OSG Software Team, but we provide as a convenience for software our users might find useful. Occasionally there may be other repositories for specific short-term purposes. Note osg-rolling and osg-release-VERSION are only present in the OSG 3.5 series. osg-rolling : This is where software goes before being included in a point release. Intended for end-users. In OSG 3.5, software goes into osg-rolling when it is put into osg-prerelease . osg-release-VERSION : This repository is created per release and its name contains the version number (e.g. osg-release-3.5.4). This is intended mostly for testing purposes, though users may occasionally find it useful. Version Numbers \u00b6 OSG 3.6+ \u00b6 The version number matches the release series. OSG 3.5 \u00b6 There is a single version number that is used to summarize the contents of the osg-release repository. Having a single version number is very useful for a variety of reasons, including: Every time changes are made to the osg-release repository, we update the version number and write release notes. We have a shorthand for referring to the state of the repository; we can talk about specific releases. However, there are important caveats about the version number: Even if a user says they have installed Version X, it may not be an accurate reflection of what they have installed: they may have chosen to update some of their software from a previous version. To truly understand what they have installed, the entire set of RPMs installed on their computer must be considered. The version number is only meaningful in the osg-release repository, though for technical reasons it's present (as an RPM) in other repositories. The version number is communicated as follows: Every time a new release is made, the version number is updated. All release notes and communication to users about this release uses the new version number. The version number will be of the form X.Y.Z. As of this writing, version numbers are 3.5.Z, where Z indicates a minor revision. Progression of Repositories \u00b6 This figure shows the progression of repositories that packages will go through: osg-development -> osg-testing -> osg-prerelease / osg-rolling -> osg-release \\ -> osg-contrib Release Policies \u00b6 Adding packages to osg-development \u00b6 New packages will only be added to osg-development with the permission of the OSG Software Manager. Updates can be done at any time without permission, but developers should be careful if their updates might be significant, particularly if an update might cause series compatibility issues. In cases where there is uncertainty, discuss it with the Software Manager. Moving packages to osg-testing \u00b6 A package may be moved from osg-development to osg-testing when the individual maintainer of that package decides that it is ready for widespread testing and when approved by the OSG Software Manager. Approval is needed because this is when we first make packages available to people outside of the OSG Software Team. Moving packages to osg-prerelease; Readying the release \u00b6 When we are ready to make a production release, we first move the correct subset of packages from osg-testing into osg-prerelease . This should be done after checking with the OSG Release Manager to verify that it's okay to release the software. The intention of osg-prerelease is to do a final verification that we have the correct set of packages for release and that they really work together. This is important because the osg-testing repository might contain a mix of packages that are ready for release with packages that are not ready for release. When moving packages to osg-prerelease , the team member doing the release will: Find the correct set of packages to push from osg-testing into osg-prerelease . At a minimum, run the automated test suite on the contents of osg-prerelease . In cases were more extensive testing is needed, or the test suite doesn't sufficiently cover the testing needs, do specific ad-hoc testing. (If appropriate, consider proposing extensions to the automated test suite.) We expect that in most cases, this process of updating and testing the osg-prerelease repository will be less than one day. If there are urgent security updates to release, this process may be shortened. Moving packages to osg-release \u00b6 When the osg-prerelease repository has been updated and verified, all of the changed software can be moved into the osg-release repository. As part of this move, three important tasks must be done: The released packages are automatically recorded in such a manner that end users/administrators can be notified if desired. Major package updates will also be recorded on the OSG 3.6 \"News\" page with links to the respective release note page or change log. An announcement is sent out whenever a major package is updated. Moving packages to osg-contrib \u00b6 The osg-contrib repository is loosely regulated. In most cases, the team member in charge of the package can decide when a package is updated in osg-contrib . Contrib packages should be tested in osg-development first. Timing of releases \u00b6 Software is released between 9AM and 5PM Central Time on a work day that is followed by a work day. The idea is to have a working day to correct any problems with a release rather than having a problematic release persist over a weekend or holiday. We will make exceptions for urgent situations; consult with the release manager when needed. CA Certificates and VO Client packages \u00b6 Packages that contain only data are not part of the usual release cycle. Currently, these are the CA certificate packages and the VO Client packages. Updates to these packages come from the Security Team and Software Team, respectively. They still move through the usual process for release, and the Software and Release Managers decide when these packages should be promoted to the next repository level.","title":"Software Release Policy"},{"location":"policy/software-release/#software-release-policy","text":"This document contains information about the OSG Software Yum repositories and their policies. For details regarding the technical process for an OSG release, see this document .","title":"Software Release Policy"},{"location":"policy/software-release/#yum-repositories","text":"The Software Team maintains the following Yum repositories: osg-development : This is the \"wild west\", the place where software goes while it is being worked on by the software team. osg-testing : This is where software goes when it is ready for wide-spread testing, including upstream release candidates osg-prerelease : This is where software goes just before being released, for final verification. osg-release : This is the official, production release of the software stack. This is the main repository for end-users. osg-contrib : This is where software goes that is not officially supported by the OSG Software Team, but we provide as a convenience for software our users might find useful. Occasionally there may be other repositories for specific short-term purposes. Note osg-rolling and osg-release-VERSION are only present in the OSG 3.5 series. osg-rolling : This is where software goes before being included in a point release. Intended for end-users. In OSG 3.5, software goes into osg-rolling when it is put into osg-prerelease . osg-release-VERSION : This repository is created per release and its name contains the version number (e.g. osg-release-3.5.4). This is intended mostly for testing purposes, though users may occasionally find it useful.","title":"Yum Repositories"},{"location":"policy/software-release/#version-numbers","text":"","title":"Version Numbers"},{"location":"policy/software-release/#osg-36","text":"The version number matches the release series.","title":"OSG 3.6+"},{"location":"policy/software-release/#osg-35","text":"There is a single version number that is used to summarize the contents of the osg-release repository. Having a single version number is very useful for a variety of reasons, including: Every time changes are made to the osg-release repository, we update the version number and write release notes. We have a shorthand for referring to the state of the repository; we can talk about specific releases. However, there are important caveats about the version number: Even if a user says they have installed Version X, it may not be an accurate reflection of what they have installed: they may have chosen to update some of their software from a previous version. To truly understand what they have installed, the entire set of RPMs installed on their computer must be considered. The version number is only meaningful in the osg-release repository, though for technical reasons it's present (as an RPM) in other repositories. The version number is communicated as follows: Every time a new release is made, the version number is updated. All release notes and communication to users about this release uses the new version number. The version number will be of the form X.Y.Z. As of this writing, version numbers are 3.5.Z, where Z indicates a minor revision.","title":"OSG 3.5"},{"location":"policy/software-release/#progression-of-repositories","text":"This figure shows the progression of repositories that packages will go through: osg-development -> osg-testing -> osg-prerelease / osg-rolling -> osg-release \\ -> osg-contrib","title":"Progression of Repositories"},{"location":"policy/software-release/#release-policies","text":"","title":"Release Policies"},{"location":"policy/software-release/#adding-packages-to-osg-development","text":"New packages will only be added to osg-development with the permission of the OSG Software Manager. Updates can be done at any time without permission, but developers should be careful if their updates might be significant, particularly if an update might cause series compatibility issues. In cases where there is uncertainty, discuss it with the Software Manager.","title":"Adding packages to osg-development"},{"location":"policy/software-release/#moving-packages-to-osg-testing","text":"A package may be moved from osg-development to osg-testing when the individual maintainer of that package decides that it is ready for widespread testing and when approved by the OSG Software Manager. Approval is needed because this is when we first make packages available to people outside of the OSG Software Team.","title":"Moving packages to osg-testing"},{"location":"policy/software-release/#moving-packages-to-osg-prerelease-readying-the-release","text":"When we are ready to make a production release, we first move the correct subset of packages from osg-testing into osg-prerelease . This should be done after checking with the OSG Release Manager to verify that it's okay to release the software. The intention of osg-prerelease is to do a final verification that we have the correct set of packages for release and that they really work together. This is important because the osg-testing repository might contain a mix of packages that are ready for release with packages that are not ready for release. When moving packages to osg-prerelease , the team member doing the release will: Find the correct set of packages to push from osg-testing into osg-prerelease . At a minimum, run the automated test suite on the contents of osg-prerelease . In cases were more extensive testing is needed, or the test suite doesn't sufficiently cover the testing needs, do specific ad-hoc testing. (If appropriate, consider proposing extensions to the automated test suite.) We expect that in most cases, this process of updating and testing the osg-prerelease repository will be less than one day. If there are urgent security updates to release, this process may be shortened.","title":"Moving packages to osg-prerelease; Readying the release"},{"location":"policy/software-release/#moving-packages-to-osg-release","text":"When the osg-prerelease repository has been updated and verified, all of the changed software can be moved into the osg-release repository. As part of this move, three important tasks must be done: The released packages are automatically recorded in such a manner that end users/administrators can be notified if desired. Major package updates will also be recorded on the OSG 3.6 \"News\" page with links to the respective release note page or change log. An announcement is sent out whenever a major package is updated.","title":"Moving packages to osg-release"},{"location":"policy/software-release/#moving-packages-to-osg-contrib","text":"The osg-contrib repository is loosely regulated. In most cases, the team member in charge of the package can decide when a package is updated in osg-contrib . Contrib packages should be tested in osg-development first.","title":"Moving packages to osg-contrib"},{"location":"policy/software-release/#timing-of-releases","text":"Software is released between 9AM and 5PM Central Time on a work day that is followed by a work day. The idea is to have a working day to correct any problems with a release rather than having a problematic release persist over a weekend or holiday. We will make exceptions for urgent situations; consult with the release manager when needed.","title":"Timing of releases"},{"location":"policy/software-release/#ca-certificates-and-vo-client-packages","text":"Packages that contain only data are not part of the usual release cycle. Currently, these are the CA certificate packages and the VO Client packages. Updates to these packages come from the Security Team and Software Team, respectively. They still move through the usual process for release, and the Software and Release Managers decide when these packages should be promoted to the next repository level.","title":"CA Certificates and VO Client packages"},{"location":"policy/software-support/","text":"Software Support \u00b6 This document describes how OSG Technology Team members should support the OSG Software Stack, including triage duty responsibilities and when to transition from direct support inquiries to a ticketing system such as Freshdesk or Jira. Considerations \u00b6 When providing support for our users, remember the following: We are a small community and we need to take good care of our users. Please be friendly and patient even when the user is frustrated or lacking in knowledge. Always sign your ticket with your full name, so people know who is responding. If it's easy for you, include a signature at the bottom of your response. If you need to collect information about a problematic host, ask users to run osg-system-profiler . It can shorten the number of times you ask for information because it collects quite a bit for you. If you run across a problem that has a chance of being hit by other users: Is there a bug we should fix in the software? Open a Jira ticket. Is there something we could improve in the software? Notify the Software Area Coordinator. Is there a way to improve our documentation? Notify the Software Area Coordinator. Can you extend our troubleshooting documents to help people track this down more quickly? Consider the troubleshooting documents to be as much for us as for our users. Is this something that other Technology Team members should be aware of? Note it during the support discussion during the weekly OSG Technology meeting, or email the Technology Team if it seems more urgent. Triage Duty \u00b6 The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Area Coordinator for access). Logging in as an agent Don't enter your credentials directly into the login page ! Click the agent login link instead so that you don't have to enter your credentials twice. During normal work hours, the OSG Technology Team splits responsibilities for managing incoming OSG Software support requests based upon a weekly rotation . If you are on triage duty, your responsibilities are as follows: Watch for new software tickets: review the Unresolved Software Tickets and All Unassigned Tickets filters at least three times daily for new OSG Software-related tickets. For any such unassigned tickets, assign it as follows: If you can handle an incoming ticket, assign it to yourself. Inasmuch as possible, you should strive to handle the easier tickets and not pass them off to other people. If you cannot handle an incoming ticket, collect initial details such as relevant versions, logs, etc., and assign the ticket to the most appropriate Technology Team member. Where appropriate, CC third-parties or add relevant OSG staff with FD accounts as watchers (see this documentation ) New sites interested in joining the OSG For support requests inquiring about joining the OSG, assign the ticket to the Campus Facilitation group. Review assigned software tickets. For tickets that are not being handled in a timely fashion (pay special attention to OVERDUE and Customer Responded tickets): If the ticket is pending and the assignee has not responded in > 2 business days, notify the ticket assignee via private note that they need to revisit the ticket. If the ticket is waiting on the customer or a third party and they have not responded in > 1 week, reply to the ticket asking if they've had the time to review the Technology Team's latest response(s). If the ticket was opened by the customer, is waiting on the customer and they have not responded in > 2 weeks, close the ticket and let the customer know that they can re-open it by responding whenever they're ready to tackle the issue again. Review and approve/deny COManage site contact registrations: Follow the instructions to review site contact registrations here . Review Topology data pull requests: Review any Topology PRs that update anything in the collaborations , projects/ , topology/ , or virtual-organizations directories. New institutions Approval of new facilities or project institutions require PATh Project Office, i.e. Irene or Janet. Re-assign non-software tickets: Tickets that have been mistakenly assigned to the Software group should be re-assigned to the appropriate group. Merge duplicate tickets: Responses to a ticket sometimes results in creation of a new ticket; these new tickets should be merged into the original ticket. See this documentation . Split off new support requests in old tickets: If a user has reopened or followed-up in a ticket with a new support request unrelated to the existing ticket (this is a judgment call) and their comment is the last one in the ticket, split off the comment into a new ticket (see this documentation ). If you are unsure if a ticket should be split, consult the Software Area Coordinator. Do not split comments other than the last one FD treats splitting tickets as \"take this comment and make it the start of a new ticket\" and not \"take this comment and all subsequent comments into a new ticket\". Clean up spam: Mark the ticket as spam and block the user. See this documentation . Clean up automated replies: announcements are often sent with Reply-to: help@osg-htc.org so automated replies (e.g. Out of Office, mailing list moderation) will generate tickets. These tickets can be closed. Question If you have questions concerning a ticket, consult the OSG Software Team Manager and/or the #software channel in the OSG Slack. Updating the triage calendar \u00b6 The current triage duty schedule can be found in the OSG Software calendar, hosted on Tim Cartwright\u2019s Google account. If you need privileges to edit the calendar, ask the OSG Software Team Manager. To update the triage duty schedule: Clone the git repo Generate next rotation: ./triage.py --generateNextRotation > rotation.txt Check and update assignments according to team member outages Load triage assignments into Google Calendar: ./triage.py --load rotation.txt To subscribe to this calendar in your calendar program, use the iCal URL: https://www.google.com/calendar/ical/h5t4mns6omp49db1e4qtqrrf4g%40group.calendar.google.com/public/basic.ics Ticket Systems \u00b6 The OSG Technology Team uses the Freshdesk and Jira ticketing systems to track support and all other work, respectively. This section describes the differences between the two as well as some OSG Technology Freshdesk conventions. Direct Email \u00b6 Sometimes users may email you directly with support inquiries. If someone emails you directly for support, you have the choice of when to move it to a ticket. The recommended criteria are: If it's easy to handle and you can definitely do it yourself, leave it in email. If there's a chance that you can't do it in a timely fashion, turn it into a ticket. If there's a chance that you might lose track of the email, turn it into a ticket. If there's a chance that you might need help from others, turn it into a ticket. If it's an unusual topic and other people would benefit from seeing the ticket (now or in the future), turn it into a ticket. Freshdesk \u00b6 Freshdesk access The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Manager for access). Freshdesk tickets are for user support, i.e. this is where we help users debug, understand their problems, etc. When replying to or otherwise updating a Freshdesk ticket, there are a few things to note: Freshdesk auto-populates the contact's name when replying through the web interface, e.g. Hi Brian . Ensure that the name is correct, especially if there are multiple parties involved in a single ticket. If the auto-populated name looks incorrect, e.g. Hi blin.wisc , fix the contact's First and Last name fields. Make sure to set the state of the ticket, which is helpful for those on triage: State Description Open OSG staff is responsible for next actions, including when ticket has not yet been assigned (initial ticket state) Waiting on Customer Assignee needs the reporter to respond Waiting on Third Party Assignee needs a response from a CC Resolved Support is complete or the user is unresponsive. See above . Closed DO NOT SET MANUALLY . Terminal ticket state that is set by Freshdesk. If actionable Technology Team tasks arise from a Freshdesk ticket, Jira ticket(s) should be created to track that work. Resultant Jira tickets should include a link to the original Freshdesk ticket, a description of the problem or feature request, and a proposed solution or implementation. After the relevant Jira tickets have been created, ask the user if they would be ok with tracking the issue via Jira. If they say yes, close the Freshdesk ticket. Jira \u00b6 Jira is for tracking our work and it's meant for internal usage, not for user support. In general, users should not ask for support via Jira. A single user support ticket might result in zero, one, or multiple Jira tickets.","title":"Software Support"},{"location":"policy/software-support/#software-support","text":"This document describes how OSG Technology Team members should support the OSG Software Stack, including triage duty responsibilities and when to transition from direct support inquiries to a ticketing system such as Freshdesk or Jira.","title":"Software Support"},{"location":"policy/software-support/#considerations","text":"When providing support for our users, remember the following: We are a small community and we need to take good care of our users. Please be friendly and patient even when the user is frustrated or lacking in knowledge. Always sign your ticket with your full name, so people know who is responding. If it's easy for you, include a signature at the bottom of your response. If you need to collect information about a problematic host, ask users to run osg-system-profiler . It can shorten the number of times you ask for information because it collects quite a bit for you. If you run across a problem that has a chance of being hit by other users: Is there a bug we should fix in the software? Open a Jira ticket. Is there something we could improve in the software? Notify the Software Area Coordinator. Is there a way to improve our documentation? Notify the Software Area Coordinator. Can you extend our troubleshooting documents to help people track this down more quickly? Consider the troubleshooting documents to be as much for us as for our users. Is this something that other Technology Team members should be aware of? Note it during the support discussion during the weekly OSG Technology meeting, or email the Technology Team if it seems more urgent.","title":"Considerations"},{"location":"policy/software-support/#triage-duty","text":"The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Area Coordinator for access). Logging in as an agent Don't enter your credentials directly into the login page ! Click the agent login link instead so that you don't have to enter your credentials twice. During normal work hours, the OSG Technology Team splits responsibilities for managing incoming OSG Software support requests based upon a weekly rotation . If you are on triage duty, your responsibilities are as follows: Watch for new software tickets: review the Unresolved Software Tickets and All Unassigned Tickets filters at least three times daily for new OSG Software-related tickets. For any such unassigned tickets, assign it as follows: If you can handle an incoming ticket, assign it to yourself. Inasmuch as possible, you should strive to handle the easier tickets and not pass them off to other people. If you cannot handle an incoming ticket, collect initial details such as relevant versions, logs, etc., and assign the ticket to the most appropriate Technology Team member. Where appropriate, CC third-parties or add relevant OSG staff with FD accounts as watchers (see this documentation ) New sites interested in joining the OSG For support requests inquiring about joining the OSG, assign the ticket to the Campus Facilitation group. Review assigned software tickets. For tickets that are not being handled in a timely fashion (pay special attention to OVERDUE and Customer Responded tickets): If the ticket is pending and the assignee has not responded in > 2 business days, notify the ticket assignee via private note that they need to revisit the ticket. If the ticket is waiting on the customer or a third party and they have not responded in > 1 week, reply to the ticket asking if they've had the time to review the Technology Team's latest response(s). If the ticket was opened by the customer, is waiting on the customer and they have not responded in > 2 weeks, close the ticket and let the customer know that they can re-open it by responding whenever they're ready to tackle the issue again. Review and approve/deny COManage site contact registrations: Follow the instructions to review site contact registrations here . Review Topology data pull requests: Review any Topology PRs that update anything in the collaborations , projects/ , topology/ , or virtual-organizations directories. New institutions Approval of new facilities or project institutions require PATh Project Office, i.e. Irene or Janet. Re-assign non-software tickets: Tickets that have been mistakenly assigned to the Software group should be re-assigned to the appropriate group. Merge duplicate tickets: Responses to a ticket sometimes results in creation of a new ticket; these new tickets should be merged into the original ticket. See this documentation . Split off new support requests in old tickets: If a user has reopened or followed-up in a ticket with a new support request unrelated to the existing ticket (this is a judgment call) and their comment is the last one in the ticket, split off the comment into a new ticket (see this documentation ). If you are unsure if a ticket should be split, consult the Software Area Coordinator. Do not split comments other than the last one FD treats splitting tickets as \"take this comment and make it the start of a new ticket\" and not \"take this comment and all subsequent comments into a new ticket\". Clean up spam: Mark the ticket as spam and block the user. See this documentation . Clean up automated replies: announcements are often sent with Reply-to: help@osg-htc.org so automated replies (e.g. Out of Office, mailing list moderation) will generate tickets. These tickets can be closed. Question If you have questions concerning a ticket, consult the OSG Software Team Manager and/or the #software channel in the OSG Slack.","title":"Triage Duty"},{"location":"policy/software-support/#updating-the-triage-calendar","text":"The current triage duty schedule can be found in the OSG Software calendar, hosted on Tim Cartwright\u2019s Google account. If you need privileges to edit the calendar, ask the OSG Software Team Manager. To update the triage duty schedule: Clone the git repo Generate next rotation: ./triage.py --generateNextRotation > rotation.txt Check and update assignments according to team member outages Load triage assignments into Google Calendar: ./triage.py --load rotation.txt To subscribe to this calendar in your calendar program, use the iCal URL: https://www.google.com/calendar/ical/h5t4mns6omp49db1e4qtqrrf4g%40group.calendar.google.com/public/basic.ics","title":"Updating the triage calendar"},{"location":"policy/software-support/#ticket-systems","text":"The OSG Technology Team uses the Freshdesk and Jira ticketing systems to track support and all other work, respectively. This section describes the differences between the two as well as some OSG Technology Freshdesk conventions.","title":"Ticket Systems"},{"location":"policy/software-support/#direct-email","text":"Sometimes users may email you directly with support inquiries. If someone emails you directly for support, you have the choice of when to move it to a ticket. The recommended criteria are: If it's easy to handle and you can definitely do it yourself, leave it in email. If there's a chance that you can't do it in a timely fashion, turn it into a ticket. If there's a chance that you might lose track of the email, turn it into a ticket. If there's a chance that you might need help from others, turn it into a ticket. If it's an unusual topic and other people would benefit from seeing the ticket (now or in the future), turn it into a ticket.","title":"Direct Email"},{"location":"policy/software-support/#freshdesk","text":"Freshdesk access The OSG uses Freshdesk to track support issues so you will need a Freshworks account with agent privileges (contact the OSG Software Team Manager for access). Freshdesk tickets are for user support, i.e. this is where we help users debug, understand their problems, etc. When replying to or otherwise updating a Freshdesk ticket, there are a few things to note: Freshdesk auto-populates the contact's name when replying through the web interface, e.g. Hi Brian . Ensure that the name is correct, especially if there are multiple parties involved in a single ticket. If the auto-populated name looks incorrect, e.g. Hi blin.wisc , fix the contact's First and Last name fields. Make sure to set the state of the ticket, which is helpful for those on triage: State Description Open OSG staff is responsible for next actions, including when ticket has not yet been assigned (initial ticket state) Waiting on Customer Assignee needs the reporter to respond Waiting on Third Party Assignee needs a response from a CC Resolved Support is complete or the user is unresponsive. See above . Closed DO NOT SET MANUALLY . Terminal ticket state that is set by Freshdesk. If actionable Technology Team tasks arise from a Freshdesk ticket, Jira ticket(s) should be created to track that work. Resultant Jira tickets should include a link to the original Freshdesk ticket, a description of the problem or feature request, and a proposed solution or implementation. After the relevant Jira tickets have been created, ask the user if they would be ok with tracking the issue via Jira. If they say yes, close the Freshdesk ticket.","title":"Freshdesk"},{"location":"policy/software-support/#jira","text":"Jira is for tracking our work and it's meant for internal usage, not for user support. In general, users should not ask for support via Jira. A single user support ticket might result in zero, one, or multiple Jira tickets.","title":"Jira"},{"location":"policy/topology-registration/","text":"Handling Topology and Contacts Registration \u00b6 This is an internal procedure handled by OSG Staff; the documentation is available in the operations site .","title":"Handling Topology/Contacts Registrations"},{"location":"policy/topology-registration/#handling-topology-and-contacts-registration","text":"This is an internal procedure handled by OSG Staff; the documentation is available in the operations site .","title":"Handling Topology and Contacts Registration"},{"location":"policy/voms-admin-retire/","text":"VOMS-Admin Retirement \u00b6 Introduction \u00b6 This document provides an overview of the planned retirement of support for VOMS-Admin in the OSG Software Stack. Support for the VOMS infrastructure has three major components: VOMS-Admin : A web interface for maintaining the list of authorized users in a VO and their various authorizations (group membership, roles, attributes, etc). VOMS-Server : A TCP service which signs a cryptographic extension on an X509 proxy certificate asserting the authorizations available to the authenticated user. VOMS Client : Software for extracting and validating the signed VOMS extension from an X509 proxy. The validation is meant to be distributed: the VOMS client does not need to contact the VOMS-Admin server. However, OSG has historically used software such as GUMS or edg-mkgridmap to cache a list of authorizations from the VOMS-Admin interface, creating a dependency between VOMS client and VOMS-Admin. VOMS-Admin is a large, complex Java web application. Over the last few years, upstream support has tailed off - particularly as OSG has been unable to update to VOMS-Admin version 3. As a result, the maintenance burden has largely fallen on the OSG Software team. Given that VOMS-Admin is deeply tied to X509 security infrastructure - and is maintenance-only from OSG Software - there is no path forward to eliminate the use of X509 certificates in the web browser, a high-priority goal In discussions with the OSG community, we have found very few VOs utilize VOMS-Admin to manage their VO users. Instead, the majority use VOMS-Admin to whitelist a pilot certificate: this can be done without a VOMS-Admin endpoint. OSG's plans to retire VOMS-Admin has three major components: (Sites) Enable distributed validation of VOMS extensions in the VOMS client. (VOs) Migrate VOs that use VOMS only for pilot certificates to direct signing of VOMS proxies. (VOs) Migrate remaining VOs to a central comanage instance for managing user authorizations; maintain a plugin to enable direct callouts from VOMS-Server to comanage for authorization lookups. Site Transition Plans \u00b6 We will release a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions; this verification eludes the need to contact the VOMS-Admin interface for a list of authorizations. In 2015/2016, LCMAPS and GUMS were upgraded so GUMS skips the VOMS-Admin lookup when LCMAPS asserts the validation was performed. Hence, when GUMS sites update clients to the latest (April 2017) LCMAPS and HTCondor-CE releases, the callout to VOMS-Admin is no longer needed. Note : In parallel to the VOMS-Admin transition, OSG Software plans to retire GUMS . There is no need to complete one transition before the other. Sites using edg-mkgridmap will need to use its replacement, lcmaps-plugins-voms (this process is documented here ). VO Transition Plans \u00b6 Based on one-to-one discussions, we believe the majority of VOs only use VOMS-Admin to maintain a list of authorized pilots. For these VOs, we will help convert invocations of voms-proxy-init : voms-proxy-init -voms hcc:/hcc/Role=pilot to an equivalent call to voms-proxy-fake : voms-proxy-fake -hostcert /etc/grid-security/voms/vomscert.pem \\ -hostkey /etc/grid-security/voms/vomskey.pem \\ -fqan /hcc/Role=pilot/Capability=NULL \\ -voms hcc -uri hcc-voms.unl.edu:15000 The latter command would typically be run on the VO's glideinWMS frontend host, requiring the service certificate currently on the VOMS-Admin server to be kept on the frontend host. The frontend's account may also need access to the certificate. Info See this documentation to update your GlideinWMS Frontend to use the new proxy generation command. We plan to transition more complex VOs - those using VOMS-Admin to track membership in a VO - to comanage . It is not clear there are any such VOs that need support from OSG. If there are, a hosted version of comanage is expected to be available in summer 2017 from the CILogon 2.0 project. If you feel your VO is affected, please contact the OSG and we will build a custom timeline. If there are no such VOs, we will not need to adopt comanage for this use case (other uses of comanage are expected to proceed regardless). Timeline \u00b6 April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. Sites begin transition to validating VOMS extensions. Summer 2017 (completed): As necessary, VOs are given access to a hosted comanage instance. March 2017 (completed): First VOs begin to retire VOMS-Admin. May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for VOMS-Admin or GUMS is provided.","title":"VOMS Admin Retirement"},{"location":"policy/voms-admin-retire/#voms-admin-retirement","text":"","title":"VOMS-Admin Retirement"},{"location":"policy/voms-admin-retire/#introduction","text":"This document provides an overview of the planned retirement of support for VOMS-Admin in the OSG Software Stack. Support for the VOMS infrastructure has three major components: VOMS-Admin : A web interface for maintaining the list of authorized users in a VO and their various authorizations (group membership, roles, attributes, etc). VOMS-Server : A TCP service which signs a cryptographic extension on an X509 proxy certificate asserting the authorizations available to the authenticated user. VOMS Client : Software for extracting and validating the signed VOMS extension from an X509 proxy. The validation is meant to be distributed: the VOMS client does not need to contact the VOMS-Admin server. However, OSG has historically used software such as GUMS or edg-mkgridmap to cache a list of authorizations from the VOMS-Admin interface, creating a dependency between VOMS client and VOMS-Admin. VOMS-Admin is a large, complex Java web application. Over the last few years, upstream support has tailed off - particularly as OSG has been unable to update to VOMS-Admin version 3. As a result, the maintenance burden has largely fallen on the OSG Software team. Given that VOMS-Admin is deeply tied to X509 security infrastructure - and is maintenance-only from OSG Software - there is no path forward to eliminate the use of X509 certificates in the web browser, a high-priority goal In discussions with the OSG community, we have found very few VOs utilize VOMS-Admin to manage their VO users. Instead, the majority use VOMS-Admin to whitelist a pilot certificate: this can be done without a VOMS-Admin endpoint. OSG's plans to retire VOMS-Admin has three major components: (Sites) Enable distributed validation of VOMS extensions in the VOMS client. (VOs) Migrate VOs that use VOMS only for pilot certificates to direct signing of VOMS proxies. (VOs) Migrate remaining VOs to a central comanage instance for managing user authorizations; maintain a plugin to enable direct callouts from VOMS-Server to comanage for authorization lookups.","title":"Introduction"},{"location":"policy/voms-admin-retire/#site-transition-plans","text":"We will release a configuration of the LCMAPS authorization framework that performs distributed verification of VOMS extensions; this verification eludes the need to contact the VOMS-Admin interface for a list of authorizations. In 2015/2016, LCMAPS and GUMS were upgraded so GUMS skips the VOMS-Admin lookup when LCMAPS asserts the validation was performed. Hence, when GUMS sites update clients to the latest (April 2017) LCMAPS and HTCondor-CE releases, the callout to VOMS-Admin is no longer needed. Note : In parallel to the VOMS-Admin transition, OSG Software plans to retire GUMS . There is no need to complete one transition before the other. Sites using edg-mkgridmap will need to use its replacement, lcmaps-plugins-voms (this process is documented here ).","title":"Site Transition Plans"},{"location":"policy/voms-admin-retire/#vo-transition-plans","text":"Based on one-to-one discussions, we believe the majority of VOs only use VOMS-Admin to maintain a list of authorized pilots. For these VOs, we will help convert invocations of voms-proxy-init : voms-proxy-init -voms hcc:/hcc/Role=pilot to an equivalent call to voms-proxy-fake : voms-proxy-fake -hostcert /etc/grid-security/voms/vomscert.pem \\ -hostkey /etc/grid-security/voms/vomskey.pem \\ -fqan /hcc/Role=pilot/Capability=NULL \\ -voms hcc -uri hcc-voms.unl.edu:15000 The latter command would typically be run on the VO's glideinWMS frontend host, requiring the service certificate currently on the VOMS-Admin server to be kept on the frontend host. The frontend's account may also need access to the certificate. Info See this documentation to update your GlideinWMS Frontend to use the new proxy generation command. We plan to transition more complex VOs - those using VOMS-Admin to track membership in a VO - to comanage . It is not clear there are any such VOs that need support from OSG. If there are, a hosted version of comanage is expected to be available in summer 2017 from the CILogon 2.0 project. If you feel your VO is affected, please contact the OSG and we will build a custom timeline. If there are no such VOs, we will not need to adopt comanage for this use case (other uses of comanage are expected to proceed regardless).","title":"VO Transition Plans"},{"location":"policy/voms-admin-retire/#timeline","text":"April 2017 (completed): lcmaps-plugins-voms shipped and supported by OSG. May 2017 (completed): osg-configure and documentation necessary for using lcmaps-plugins-voms is shipped. June 2017 (completed): OSG 3.4.0 is released without VOMS-Admin, edg-mkgridmap , or GUMS. Sites begin transition to validating VOMS extensions. Summer 2017 (completed): As necessary, VOs are given access to a hosted comanage instance. March 2017 (completed): First VOs begin to retire VOMS-Admin. May 2018 (completed): Support is dropped for OSG 3.3 series; no further support for VOMS-Admin or GUMS is provided.","title":"Timeline"},{"location":"projects/sha2-support/","text":"SHA-2 Compliance \u00b6 When a certificate authority signs a certificate, it uses one of several possible hash algorithms. Historically, the most popular algorithms were MD5 (now retired due to security issues) and the SHA-1 family. SHA-1 certificates are being phased out due to perceived weaknesses \u2014 as of February 2017, a practical attack for generating collisions was demonstrated by Google researchers . These days, the preferred hash algorithm family is SHA-2. The certificate authorities (CAs), which issue host and user certificates used widely in the OSG, defaulted to SHA-2-based certificates on 1 October 2013; all sites will need to make sure that their software supports certificates using the SHA-2 algorithms. All supported OSG releases support SHA-2. The table below denotes indicates the minimum releases necessary to support SHA-2 certificates. Component Version In Release Notes BeStMan 2 bestman2-2.3.0-9.osg 3.1.13 SHA-2 support; also see jGlobus, below dCache SRM client dcache-srmclient-2.2.11.1-2.osg 3.1.22 Major update includes SHA-2 support Globus GRAM globus-gram-job-manager-13.45-1.2.osg, globus-gram-job-manager-condor-1.0-13.1.osg, globus-gram-job-manager-pbs-1.6-1.1.osg 3.1.9 Critical bug fixes (not SHA-2 specific) GUMS gums-1.3.18.009-15.2.osg 3.1.13 Switched to jGlobus 2 with SHA-2 support; also see jGlobus, below jGlobus (for BeStMan 2) jglobus-2.0.5-3.osg 3.1.18 Fixed CRL refresh bug (not SHA-2 specific) VOMS voms-2.0.8-1.5.osg 3.1.17 SHA-2 fix for voms-proxy-init If a component does not appear in the above table, it already has SHA-2 support.","title":"SHA-2 Support"},{"location":"projects/sha2-support/#sha-2-compliance","text":"When a certificate authority signs a certificate, it uses one of several possible hash algorithms. Historically, the most popular algorithms were MD5 (now retired due to security issues) and the SHA-1 family. SHA-1 certificates are being phased out due to perceived weaknesses \u2014 as of February 2017, a practical attack for generating collisions was demonstrated by Google researchers . These days, the preferred hash algorithm family is SHA-2. The certificate authorities (CAs), which issue host and user certificates used widely in the OSG, defaulted to SHA-2-based certificates on 1 October 2013; all sites will need to make sure that their software supports certificates using the SHA-2 algorithms. All supported OSG releases support SHA-2. The table below denotes indicates the minimum releases necessary to support SHA-2 certificates. Component Version In Release Notes BeStMan 2 bestman2-2.3.0-9.osg 3.1.13 SHA-2 support; also see jGlobus, below dCache SRM client dcache-srmclient-2.2.11.1-2.osg 3.1.22 Major update includes SHA-2 support Globus GRAM globus-gram-job-manager-13.45-1.2.osg, globus-gram-job-manager-condor-1.0-13.1.osg, globus-gram-job-manager-pbs-1.6-1.1.osg 3.1.9 Critical bug fixes (not SHA-2 specific) GUMS gums-1.3.18.009-15.2.osg 3.1.13 Switched to jGlobus 2 with SHA-2 support; also see jGlobus, below jGlobus (for BeStMan 2) jglobus-2.0.5-3.osg 3.1.18 Fixed CRL refresh bug (not SHA-2 specific) VOMS voms-2.0.8-1.5.osg 3.1.17 SHA-2 fix for voms-proxy-init If a component does not appear in the above table, it already has SHA-2 support.","title":"SHA-2 Compliance"},{"location":"release/acceptance-testing/","text":"Acceptance Testing \u00b6 The OSG Release Team collects and maintains testing procedures for major components in the OSG Sofware Stack. These test should verify that basic functionality of the component works in typically deployed configurations. CVMFS \u00b6 Note This acceptance testing recipe was created when access to a machine with sufficient disk space to make a complete replica of OASIS was not available. Creating a CVMFS Repository Server (Stratum 0) \u00b6 Disable SELinux by setting the following in /etc/selinux/config . SELINUX=disabled Check kernel version. uname -a CVMFS for EL7 requires OverlayFS (as of kernel version 4.2.x). If default kernel is <= 4.2.x, update kernel. root@host # rpm --import <https://www.elrepo.org/RPM-GPG-KEY-elrepo.org> root@host # rpm -Uvh <http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm> root@host # yum install yum-plugin-fastestmirror root@host # yum --enablerepo = elrepo-kernel install kernel-ml Select updated kernel by editing /etc/default/grub . GRUB_DEFAULT=0 and run: root@host # grub2-mkconfig -o /boot/grub2/grub.cfg Reboot system. Check kernel version again and make sure SELinux is disabled. root@host # uname -a root@host # sestatus If kernel >= 4.2 and SELinux is disabled, then update system and install CVMFS server and client packages. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs cvmfs-server Configure web server and start it up. Edit /etc/httpd/conf.d/cvmfs.conf : Listen 8000 KeepAlive On and run: root@host # chkconfig httpd on root@host # service httpd start Make new repository. root@host # cvmfs_server mkfs test.cvmfs-stratum-0.novalocal Run transaction on new repository to enable write access. root@host # cvmfs_server transaction test.cvmfs-stratum-0.novalocal Place some sample code in new repository directory and then publish it. root@host # cd /cvmfs/test.cvmfs-stratum-0.novalocal root@host # vi [ bash \\_ pi.sh ]( %ATTACHURL%/bash_pi.sh ) root@host # chmod +x bash \\_ pi.sh root@host # cvmfs \\_ server publish test.cvmfs-stratum-0.novalocal Check repository status after publication. root@host # cvmfs \\_ server check root@host # cvmfs \\_ server tag root@host # wget -qO- <http://localhost:8000/cvmfs/test.cvmfs-stratum-0.novalocal/.cvmfswhitelist%7Ccat> -v Download a copy of the CVMFS repository's public key e.g., /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub Creating a CVMFS Replica Server (Stratum 1) \u00b6 Repeat steps 1 though 8 in the previous section on \"Creating a CVMFS Repository Server \". However, now also install mod_wsgi . root@host # yum install cvmfs cvmfs-server mod \\_ wsgi Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Add replica of the repository. root@host # cvmfs_server add-replica -o root <http://10.128.3.96:8000/cvmfs/test.cvmfs-stratum-0.novalocal> /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub Make a snapshot of the repository. root@host # cvmfs \\_ server snapshot test.cvmfs-stratum-0.novalocal Creating a CVMFS client \u00b6 Update system and install CVMFS client package. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Edit fuse configuration /etc/fuse.conf . user_allow_other Edit autofs configuration and restart service /etc/auto.master . /cvmfs /etc/auto.cvmfs and run: root@host # service autofs restart Edit cvmfs configuration ( /etc/cvmfs/default.local ) to point to replica server. CVMFS_SERVER_URL=\"http://10.128.3.97:8000/cvmfs/@fqrn@\" CVMFS_REPOSITORIES=\"test.cvmfs-stratum-0.novalocal\" CVMFS_HTTP_PROXY=DIRECT Remove OSG CVMFS configuration file. rm /etc/cvmfs/default.d/60-osg.conf Run CVMFS config probe. cvmfs_config probe test.cvmfs-stratum-0.novalocal Check CVMFS config status. cvmfs_config stat -v test.cvmfs-stratum-0.novalocal Execute sample code published to repository from client. /cvmfs/test.cvmfs-stratum-0.novalocal/bash_pi.sh -b 8 -r 5 -s 10000 Creating an OASIS client \u00b6 Update system and install CVMFS client package. yum update yum install epel-release yum install yum-plugin-priorities rpm -Uvh https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm yum install osg-oasis Verify latest versions of cvmfs, cvmfs-config-osg, and cvmfs-x509-helper have been installed. Edit fuse configuration. vi /etc/fuse.conf user_allow_other Edit cvmfs configuration to point to replica server. vi /etc/cvmfs/default.local CVMFS_REPOSITORIES=\"`echo $((echo oasis.opensciencegrid.org;echo cms.cern.ch;ls /cvmfs)|sort -u)|tr ' ' ,`\" CVMFS_QUOTA_LIMIT=20000 CVMFS_HTTP_PROXY=DIRECT Edit autofs configuration and restart service. vi /etc/auto.master /cvmfs /etc/auto.cvmfs service autofs restart Run CVMFS config probe. cvmfs_config probe Check CVMFS config status. cvmfs_config stat -v oasis.opensciencegrid.org Additional Documentation \u00b6 CERN's CVMFS Documentation OSG's CVMFS Replica Server OSG's CVMFS Client Documentation OSG's OASIS Documentation bash_pi.sh : A bash script that uses a simple Monte Carlo method to estimate the value of Pi Gratia Probe \u00b6 This section documents the testing procedure to test the gratia probes sufficiently tested to be promoted to the osg-testing repository. The test procedure is the same on both SL6 and SL7. install or update the gratia-probe-condor rpm as appropriate On each VM download the gratia-probe-setup.sh script and run it In /etc/gratia/condor/ProbeConfig , verify the following have been changed: change SiteName to something aside from Generic Site change EnableProbe to 1 change CollectorHost , SSLHost , and SSLRegistrationHost to the an invalid host (E.g. test.com) or the localhost Create /var/lib/osg/ and download the attached user-vo-map file and place it in that directory Edit the user-vo-map file and change the account from sthapa to the account you'll be using to submit the condor jobs in the following step Download and submit the attached condor_submit file (note, on the default fermicloud VM, this takes about 3 hours, so you may want to set NUM_CPUS to 50 so that 50 jobs will run at a time) Run /usr/share/gratia/condor/condor_meter Check /var/lib/gratia/tmp/gratiafiles/ for a subdir.condor_... directory and verify that there are 200 xml jobs and the cpus/wall times are appropriate (either PT0S or PT1M). HTCondor-CE Collector (WIP) \u00b6 The CE Collector is a stripped-down version of HTCondor-CE that contains mostly just the collector daemon and configs. It was introduced in htcondor-ce-1.6. The production CE Collectors run at the GOC, but you may want to set up your own for testing. Make 2 VMs with the EPEL/OSG repos installed: one for the collector, and one for the CE Setting Up the Collector \u00b6 Install htcondor-ce-collector Create a file called /etc/condor-ce/config.d/99-local.conf that contains this line: COLLECTOR.ALLOW_ADVERTISE_SCHEDD = $(COLLECTOR.ALLOW_ADVERTISE_SCHEDD), your_htcondor_ce_host.example.net</pre> (with your_htcondor_ce_host replaced by the hostname the HTCondor-CE VM) Run service condor-ce-collector start Setting Up the CE \u00b6 Install osg-htcondor-ce-condor (replace condor with the batch system of your choice) Ensure osg-configure >= 1.0.60-2 is installed Configure your CE using osg-configure You should use the HTCondor-CE Install Docs as a reference, although you can skip several of the steps You can skip setting up Squid: set enabled to True and location to UNAVAILABLE in 01-squid.ini Set htcondor_gateway_enabled to True in 10-gateway.ini You probably don't need GUMS, but if you want it, use the Fermi GUMS server (set gums_host to gums.fnal.gov and authorization_method to xacml in 10-misc.ini) To keep osg-configure from complaining about storage, edit 10-storage.ini : Set se_available to False Set app_dir to /osg/app_dir Set data_dir to /osg/data_dir Do mkdir -p /osg/app_dir/etc; mkdir -p /osg/data_dir; chmod 1777 /osg/app_dir{,/etc} Enable your batch system by setting enabled to True in 20-<batch system>.ini Set up the site info in 40-siteinfo.ini ; in particular, you'll need to set the resource and resource_group settings \\ (you just need to pick a name; I concatenate my login name with the short host name and use that, e.g. matyasfermicloud001). \\ You can also use the following settings: group=OSG-ITB sponsor=local city=Batavia, IL country=US longitude=-88 latitude=41 Edit the file /etc/osg/config.d/30-infoservices.ini and set ce_collectors to the collector host Run osg-configure -dc Start up your batch system Run service condor-ce start The CE will report to the collector host every five minutes. If you want to force it to send now, run condor_ce_reconfig . You should see your CE if you run condor_ce_status -schedd on the collector host. RSV \u00b6 Testing a fresh installation: make sure the yum repositories required by OSG is installed on your host rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el8-release-latest.rpm OR rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm also make sure epel repo is set up. install the rpm yum --enablerepo=osg-testing install rsv edit /etc/osg/config.d/30-rsv.ini file in my case, I don't have a service cert for testing, so I use my own personal cert to create the proxy, but later on the owner of the proxy should be changed to \"rsv\" user that is created during the rpm install. in the config file, for the ce_hosts and gridftp_hosts, put in a test server, as the result from this test will be uploaded to OSG GOC, which may mess up your production service monitoring if you chose a production server for the test. osg-configure -v osg-configure -c /etc/init.d/condor-cron start /etc/init.d/rsv start rsv-control --list rsv-control --version rsv-control --run --all-enabled 11. make sure the results from the above commands look fine. Testing an upgrade installation: make sure to enable the osg-testing repo, and set its priority higher than the other repos yum --enablerepo=osg-testing upgrade rsv* you can use the old 30-rsv.ini file for configuration repeat steps 4)~11) as mentioned in the last section. Slurm \u00b6 This section goes through the steps needed to set up a slurm install on a VM. This is a necessary prerequisite for testing Slurm related components (CE integration, gratia, etc.). Note that the slurm setup used for this uses weak passwords for mysql. It should be sufficient for a quick setup, testing, and then tear down but should not be used without changes if it will be running for any appreciable length of time. Note need to have a VM with 2+ GB of memory Installation and setup \u00b6 Download scripts and config files: cd /tmp/ git clone <https://github.com/sthapa/utilities.git> cd utilities/slurm setup and install slurm components export username='USERNAME' \\# user that jobs will run as export version='14.11.7' \\# slurm version to install (e.g. 16.05.2 or 14.11.7) ./slurm-setup.sh After successful completion, slurm and slurm gratia probes should be setup and enabled. Running a job using slurm \u00b6 Generate test.sh with the following: #/bin/bash echo \"In the directory: `pwd`\" echo \"As the user: `whoami`\" echo \u201cHostname:\" /bin/hostname sleep 60 </pre> run sbatch test.sh the output from the jobs should appear in the current working directory as test.sh.[eo].nnnnn where nnnnn is a job id VO Client \u00b6 This document contains a basic recipe for testing a VO Package release Prerequisites \u00b6 Testing the VO package requires a few components: * X.509 certificate with membership to at least one VO * System with working GUMS installation * System with OSG installation (voms-proxy-init and edg-mkgridmap) Testing voms-proxy-init \u00b6 Login in the system that has voms-proxy-init installed. Make sure that you have the correct vo-client rpms installed and that your X.509 certificate is in your home directory. For each VO that you have membership in, run the following voms-proxy-init -voms [VO] where [VO] is the appropriate VO (e.g. osg, cms, etc.). You should be able to generate a voms-proxy for that VO without errors. XRootD VOMS Testing \u00b6 This section is intended for OSG Software/Release teams to gather information on testing vomsxrd/xrootd-voms-plugin package. Original plugin named vomsxrd , similar to lcmaps that extracts information for authorization within xrootd of a proxy's voms extension. You need an xrootd server installation In the xrootd server yum install the following packages: xrootd xrootd-voms-plugin vo-client In the xrootd client yum install the following packages: xrootd-client voms-clients vo-client In the xrootd server add this lines to file /etc/xrootd/xrootd-clustered.cfg xrootd.seclib /usr/lib64/libXrdSec.so sec.protparm gsi -vomsfun:/usr/lib64/libXrdSecgsiVOMS.so -vomsfunparms:certfmt=raw|vos=cms|dbg -vomsat:2 sec.protocol /usr/lib64 gsi -ca:1 -crl:3 This configuration will only authorize members of VO cms . You can change it to another VO. Make sure fetch-crl has been run otherwise the xrootd service may fail to start. In the xrootd client get a proxy without voms extension or with another VO extension different that the one used in the configuration: user@host $ voms-proxy-init -voms mis Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ........................... Done Contacting voms.opensciencegrid.org:15001 [/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=http/voms.opensciencegrid.org] \"mis\" Done Creating proxy ............................................... Done user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s] Run: [FATAL] Auth failed Now get a proxy with cms extension and run it again: user@host $ voms-proxy-init -voms cms Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ...................................... Done Contacting voms2.cern.ch:15002 [/DC=ch/DC=cern/OU=computers/CN=voms2.cern.ch] \"cms\" Done Creating proxy .......................................... Done Your proxy is valid until Thu Dec 4 22:53:29 2014 user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s] HDFS \u00b6 Hadoop name node installation \u00b6 Use the following script with option 1: #!/bin/bash set -e select NODETYPE in namenode datanode gridftp; do [[ $NODETYPE ]] && break done case $NODETYPE in namenode ) NAMENODE=$HOSTNAME ;; * ) read -p 'hostname for NAMENODE? ' NAMENODE ;; esac echo NODETYPE=$NODETYPE echo NAMENODE=$NAMENODE read -p 'ok? [y/N] ' ok case $ok in y*|Y*) ;; # ok *) exit ;; esac #yum install --enablerepo=osg-minefield osg-se-hadoop-$NODETYPE yum install osg-se-hadoop-$NODETYPE case $NODETYPE in namenode|datanode ) mkdir -p /data/{hadoop,scratch,checkpoint} chown -R hdfs:hdfs /data sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml cp /etc/hadoop/conf.osg/{core,hdfs}-site.xml /etc/hadoop/conf/ touch /etc/hosts_exclude ;; gridftp ) ln -snf conf.osg /etc/hadoop/conf sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml echo \"hadoop-fuse-dfs# /mnt/hadoop fuse server=$NAMENODE,port=9000,rdbuffer=131072,allow_other 0 0\" >> /etc/fstab mkdir /mnt/hadoop mount /mnt/hadoop cp -v /etc/redhat-release /mnt/hadoop/test-file sed -i '/globus_mapping/s/^# *//' /etc/grid-security/gsi-authz.conf sed -i s/yourgums.yourdomain/gums.fnal.gov/ /etc/lcmaps.db mkdir /mnt/hadoop/fnalgrid useradd fnalgrid -g fnalgrid chown fnalgrid:fnalgrid /mnt/hadoop/fnalgrid service globus-gridftp-server start if type -t globus-url-copy >/dev/null; then globus-url-copy file:////bin/bash gsiftp://$HOSTNAME/mnt/hadoop/fnalgrid/first_test else echo globus-url-copy not installed fi ;; esac case $NODETYPE in namenode ) su - hdfs -c \"hadoop namenode -format\" ;; esac service hadoop-hdfs-$NODETYPE start Edit Configuration \u00b6 Edit /etc/hadoop/conf/hdfs-site.xml set dfs.replication to 1 set dfs.replication.min to 1 Hadoop data node installation \u00b6 Run same script as before but with option number 2. GridFTP installation \u00b6 Run same as script but with option number 3. On the name node \u00b6 [root@fermicloud092 ~]# hdfs dfs -ls /test-file Found 1 items -rw-r--r-- 2 root root 0 2014-07-21 15:57 /test-file On the name node \u00b6 [root@]# hadoop fs -mkdir /matyas [root@]# hadoop fs -chown matyas /matyas [root@]# hdfs dfsadmin -setSpaceQuota 123k /matyas user@host $ dd if = /dev/zero of = /tmp/blob bs = 4096 count = 10000 user@host $ kx509 ; voms-proxy-init -noregen -voms fermilab user@host $ globus-url-copy -vb file:///tmp/blob gsiftp:// ` hostname -f ` /mnt/hadoop/matyas XRootD Plugins \u00b6 Install xrootd-server: yum install xrootd-server Install xrootd-plugins yum install xrootd-cmstfc xrootd-hdfs Modify the file /etc/xrootd/xrootd-clustered.cfg to look like this: xrd.port 1094 # The roles this server will play. all.role server all.role manager if xrootd.unl.edu # The known managers all.manager srm.unl.edu:1213 #all.manager xrootd.ultralight.org:1213 # Allow any path to be exported; this is further refined in the authfile. all.export / nostage # Hosts allowed to use this xrootd cluster cms.allow host * ### Standard directives # Simple sites probably don't need to touch these. # Logging verbosity xrootd.trace all -debug ofs.trace all -debug xrd.trace all -debug cms.trace all -debug # Integrate with CMS TFC, placed in /etc/storage.xml oss.namelib /usr/lib64/libXrdCmsTfc.so file:/etc/xrootd/storage.xml?protocol=hadoop xrootd.seclib /usr/lib64/libXrdSec.so xrootd.fslib /usr/lib64/libXrdOfs.so ofs.osslib /usr/lib64/libXrdHdfs.so all.adminpath /var/run/xrootd all.pidpath /var/run/xrootd cms.delay startup 10 cms.fxhold 60s cms.perf int 30s pgm /usr/bin/XrdOlbMonPerf 30 oss.space default_stage /opt/xrootd_cache Create file /etc/xrootd/storage.xml and place this: <storage-mapping> <lfn-to-pfn protocol=\"hadoop\" destination-match=\".*\" path-match=\".*/+tmp2/test-file\" result=\"/test-file\"/> </storage-mapping> For el7 the instrucctions are a little bit different. See: https://jira.opensciencegrid.org/browse/SOFTWARE-2198?focusedCommentId=334667&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-334667 Now from a node do: xrdcp --debug 3 root://yourdatanode.yourdomain:1094//tmp2/test-file . If it is sucessful it would have tested both cmstfc and hdfs plugins","title":"Acceptance Testing"},{"location":"release/acceptance-testing/#acceptance-testing","text":"The OSG Release Team collects and maintains testing procedures for major components in the OSG Sofware Stack. These test should verify that basic functionality of the component works in typically deployed configurations.","title":"Acceptance Testing"},{"location":"release/acceptance-testing/#cvmfs","text":"Note This acceptance testing recipe was created when access to a machine with sufficient disk space to make a complete replica of OASIS was not available.","title":"CVMFS"},{"location":"release/acceptance-testing/#creating-a-cvmfs-repository-server-stratum-0","text":"Disable SELinux by setting the following in /etc/selinux/config . SELINUX=disabled Check kernel version. uname -a CVMFS for EL7 requires OverlayFS (as of kernel version 4.2.x). If default kernel is <= 4.2.x, update kernel. root@host # rpm --import <https://www.elrepo.org/RPM-GPG-KEY-elrepo.org> root@host # rpm -Uvh <http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm> root@host # yum install yum-plugin-fastestmirror root@host # yum --enablerepo = elrepo-kernel install kernel-ml Select updated kernel by editing /etc/default/grub . GRUB_DEFAULT=0 and run: root@host # grub2-mkconfig -o /boot/grub2/grub.cfg Reboot system. Check kernel version again and make sure SELinux is disabled. root@host # uname -a root@host # sestatus If kernel >= 4.2 and SELinux is disabled, then update system and install CVMFS server and client packages. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs cvmfs-server Configure web server and start it up. Edit /etc/httpd/conf.d/cvmfs.conf : Listen 8000 KeepAlive On and run: root@host # chkconfig httpd on root@host # service httpd start Make new repository. root@host # cvmfs_server mkfs test.cvmfs-stratum-0.novalocal Run transaction on new repository to enable write access. root@host # cvmfs_server transaction test.cvmfs-stratum-0.novalocal Place some sample code in new repository directory and then publish it. root@host # cd /cvmfs/test.cvmfs-stratum-0.novalocal root@host # vi [ bash \\_ pi.sh ]( %ATTACHURL%/bash_pi.sh ) root@host # chmod +x bash \\_ pi.sh root@host # cvmfs \\_ server publish test.cvmfs-stratum-0.novalocal Check repository status after publication. root@host # cvmfs \\_ server check root@host # cvmfs \\_ server tag root@host # wget -qO- <http://localhost:8000/cvmfs/test.cvmfs-stratum-0.novalocal/.cvmfswhitelist%7Ccat> -v Download a copy of the CVMFS repository's public key e.g., /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub","title":"Creating a CVMFS Repository Server (Stratum 0)"},{"location":"release/acceptance-testing/#creating-a-cvmfs-replica-server-stratum-1","text":"Repeat steps 1 though 8 in the previous section on \"Creating a CVMFS Repository Server \". However, now also install mod_wsgi . root@host # yum install cvmfs cvmfs-server mod \\_ wsgi Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Add replica of the repository. root@host # cvmfs_server add-replica -o root <http://10.128.3.96:8000/cvmfs/test.cvmfs-stratum-0.novalocal> /etc/cvmfs/keys/test.cvmfs-stratum-0.novalocal.pub Make a snapshot of the repository. root@host # cvmfs \\_ server snapshot test.cvmfs-stratum-0.novalocal","title":"Creating a CVMFS Replica Server (Stratum 1)"},{"location":"release/acceptance-testing/#creating-a-cvmfs-client","text":"Update system and install CVMFS client package. root@host # yum update root@host # yum install epel-release root@host # yum install yum-plugin-priorities root@host # rpm -Uvh <https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm> root@host # yum install cvmfs Upload a copy of the CVMFS repository's public key and place in /etc/cvmfs/keys directory. Edit fuse configuration /etc/fuse.conf . user_allow_other Edit autofs configuration and restart service /etc/auto.master . /cvmfs /etc/auto.cvmfs and run: root@host # service autofs restart Edit cvmfs configuration ( /etc/cvmfs/default.local ) to point to replica server. CVMFS_SERVER_URL=\"http://10.128.3.97:8000/cvmfs/@fqrn@\" CVMFS_REPOSITORIES=\"test.cvmfs-stratum-0.novalocal\" CVMFS_HTTP_PROXY=DIRECT Remove OSG CVMFS configuration file. rm /etc/cvmfs/default.d/60-osg.conf Run CVMFS config probe. cvmfs_config probe test.cvmfs-stratum-0.novalocal Check CVMFS config status. cvmfs_config stat -v test.cvmfs-stratum-0.novalocal Execute sample code published to repository from client. /cvmfs/test.cvmfs-stratum-0.novalocal/bash_pi.sh -b 8 -r 5 -s 10000","title":"Creating a CVMFS client"},{"location":"release/acceptance-testing/#creating-an-oasis-client","text":"Update system and install CVMFS client package. yum update yum install epel-release yum install yum-plugin-priorities rpm -Uvh https://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm yum install osg-oasis Verify latest versions of cvmfs, cvmfs-config-osg, and cvmfs-x509-helper have been installed. Edit fuse configuration. vi /etc/fuse.conf user_allow_other Edit cvmfs configuration to point to replica server. vi /etc/cvmfs/default.local CVMFS_REPOSITORIES=\"`echo $((echo oasis.opensciencegrid.org;echo cms.cern.ch;ls /cvmfs)|sort -u)|tr ' ' ,`\" CVMFS_QUOTA_LIMIT=20000 CVMFS_HTTP_PROXY=DIRECT Edit autofs configuration and restart service. vi /etc/auto.master /cvmfs /etc/auto.cvmfs service autofs restart Run CVMFS config probe. cvmfs_config probe Check CVMFS config status. cvmfs_config stat -v oasis.opensciencegrid.org","title":"Creating an OASIS client"},{"location":"release/acceptance-testing/#additional-documentation","text":"CERN's CVMFS Documentation OSG's CVMFS Replica Server OSG's CVMFS Client Documentation OSG's OASIS Documentation bash_pi.sh : A bash script that uses a simple Monte Carlo method to estimate the value of Pi","title":"Additional Documentation"},{"location":"release/acceptance-testing/#gratia-probe","text":"This section documents the testing procedure to test the gratia probes sufficiently tested to be promoted to the osg-testing repository. The test procedure is the same on both SL6 and SL7. install or update the gratia-probe-condor rpm as appropriate On each VM download the gratia-probe-setup.sh script and run it In /etc/gratia/condor/ProbeConfig , verify the following have been changed: change SiteName to something aside from Generic Site change EnableProbe to 1 change CollectorHost , SSLHost , and SSLRegistrationHost to the an invalid host (E.g. test.com) or the localhost Create /var/lib/osg/ and download the attached user-vo-map file and place it in that directory Edit the user-vo-map file and change the account from sthapa to the account you'll be using to submit the condor jobs in the following step Download and submit the attached condor_submit file (note, on the default fermicloud VM, this takes about 3 hours, so you may want to set NUM_CPUS to 50 so that 50 jobs will run at a time) Run /usr/share/gratia/condor/condor_meter Check /var/lib/gratia/tmp/gratiafiles/ for a subdir.condor_... directory and verify that there are 200 xml jobs and the cpus/wall times are appropriate (either PT0S or PT1M).","title":"Gratia Probe"},{"location":"release/acceptance-testing/#htcondor-ce-collector-wip","text":"The CE Collector is a stripped-down version of HTCondor-CE that contains mostly just the collector daemon and configs. It was introduced in htcondor-ce-1.6. The production CE Collectors run at the GOC, but you may want to set up your own for testing. Make 2 VMs with the EPEL/OSG repos installed: one for the collector, and one for the CE","title":"HTCondor-CE Collector (WIP)"},{"location":"release/acceptance-testing/#setting-up-the-collector","text":"Install htcondor-ce-collector Create a file called /etc/condor-ce/config.d/99-local.conf that contains this line: COLLECTOR.ALLOW_ADVERTISE_SCHEDD = $(COLLECTOR.ALLOW_ADVERTISE_SCHEDD), your_htcondor_ce_host.example.net</pre> (with your_htcondor_ce_host replaced by the hostname the HTCondor-CE VM) Run service condor-ce-collector start","title":"Setting Up the Collector"},{"location":"release/acceptance-testing/#setting-up-the-ce","text":"Install osg-htcondor-ce-condor (replace condor with the batch system of your choice) Ensure osg-configure >= 1.0.60-2 is installed Configure your CE using osg-configure You should use the HTCondor-CE Install Docs as a reference, although you can skip several of the steps You can skip setting up Squid: set enabled to True and location to UNAVAILABLE in 01-squid.ini Set htcondor_gateway_enabled to True in 10-gateway.ini You probably don't need GUMS, but if you want it, use the Fermi GUMS server (set gums_host to gums.fnal.gov and authorization_method to xacml in 10-misc.ini) To keep osg-configure from complaining about storage, edit 10-storage.ini : Set se_available to False Set app_dir to /osg/app_dir Set data_dir to /osg/data_dir Do mkdir -p /osg/app_dir/etc; mkdir -p /osg/data_dir; chmod 1777 /osg/app_dir{,/etc} Enable your batch system by setting enabled to True in 20-<batch system>.ini Set up the site info in 40-siteinfo.ini ; in particular, you'll need to set the resource and resource_group settings \\ (you just need to pick a name; I concatenate my login name with the short host name and use that, e.g. matyasfermicloud001). \\ You can also use the following settings: group=OSG-ITB sponsor=local city=Batavia, IL country=US longitude=-88 latitude=41 Edit the file /etc/osg/config.d/30-infoservices.ini and set ce_collectors to the collector host Run osg-configure -dc Start up your batch system Run service condor-ce start The CE will report to the collector host every five minutes. If you want to force it to send now, run condor_ce_reconfig . You should see your CE if you run condor_ce_status -schedd on the collector host.","title":"Setting Up the CE"},{"location":"release/acceptance-testing/#rsv","text":"Testing a fresh installation: make sure the yum repositories required by OSG is installed on your host rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el8-release-latest.rpm OR rpm -Uvh http://repo.opensciencegrid.org/osg/3.6/osg-3.6-el7-release-latest.rpm also make sure epel repo is set up. install the rpm yum --enablerepo=osg-testing install rsv edit /etc/osg/config.d/30-rsv.ini file in my case, I don't have a service cert for testing, so I use my own personal cert to create the proxy, but later on the owner of the proxy should be changed to \"rsv\" user that is created during the rpm install. in the config file, for the ce_hosts and gridftp_hosts, put in a test server, as the result from this test will be uploaded to OSG GOC, which may mess up your production service monitoring if you chose a production server for the test. osg-configure -v osg-configure -c /etc/init.d/condor-cron start /etc/init.d/rsv start rsv-control --list rsv-control --version rsv-control --run --all-enabled 11. make sure the results from the above commands look fine. Testing an upgrade installation: make sure to enable the osg-testing repo, and set its priority higher than the other repos yum --enablerepo=osg-testing upgrade rsv* you can use the old 30-rsv.ini file for configuration repeat steps 4)~11) as mentioned in the last section.","title":"RSV"},{"location":"release/acceptance-testing/#slurm","text":"This section goes through the steps needed to set up a slurm install on a VM. This is a necessary prerequisite for testing Slurm related components (CE integration, gratia, etc.). Note that the slurm setup used for this uses weak passwords for mysql. It should be sufficient for a quick setup, testing, and then tear down but should not be used without changes if it will be running for any appreciable length of time. Note need to have a VM with 2+ GB of memory","title":"Slurm"},{"location":"release/acceptance-testing/#installation-and-setup","text":"Download scripts and config files: cd /tmp/ git clone <https://github.com/sthapa/utilities.git> cd utilities/slurm setup and install slurm components export username='USERNAME' \\# user that jobs will run as export version='14.11.7' \\# slurm version to install (e.g. 16.05.2 or 14.11.7) ./slurm-setup.sh After successful completion, slurm and slurm gratia probes should be setup and enabled.","title":"Installation and setup"},{"location":"release/acceptance-testing/#running-a-job-using-slurm","text":"Generate test.sh with the following: #/bin/bash echo \"In the directory: `pwd`\" echo \"As the user: `whoami`\" echo \u201cHostname:\" /bin/hostname sleep 60 </pre> run sbatch test.sh the output from the jobs should appear in the current working directory as test.sh.[eo].nnnnn where nnnnn is a job id","title":"Running a job using slurm"},{"location":"release/acceptance-testing/#vo-client","text":"This document contains a basic recipe for testing a VO Package release","title":"VO Client"},{"location":"release/acceptance-testing/#prerequisites","text":"Testing the VO package requires a few components: * X.509 certificate with membership to at least one VO * System with working GUMS installation * System with OSG installation (voms-proxy-init and edg-mkgridmap)","title":"Prerequisites"},{"location":"release/acceptance-testing/#testing-voms-proxy-init","text":"Login in the system that has voms-proxy-init installed. Make sure that you have the correct vo-client rpms installed and that your X.509 certificate is in your home directory. For each VO that you have membership in, run the following voms-proxy-init -voms [VO] where [VO] is the appropriate VO (e.g. osg, cms, etc.). You should be able to generate a voms-proxy for that VO without errors.","title":"Testing voms-proxy-init"},{"location":"release/acceptance-testing/#xrootd-voms-testing","text":"This section is intended for OSG Software/Release teams to gather information on testing vomsxrd/xrootd-voms-plugin package. Original plugin named vomsxrd , similar to lcmaps that extracts information for authorization within xrootd of a proxy's voms extension. You need an xrootd server installation In the xrootd server yum install the following packages: xrootd xrootd-voms-plugin vo-client In the xrootd client yum install the following packages: xrootd-client voms-clients vo-client In the xrootd server add this lines to file /etc/xrootd/xrootd-clustered.cfg xrootd.seclib /usr/lib64/libXrdSec.so sec.protparm gsi -vomsfun:/usr/lib64/libXrdSecgsiVOMS.so -vomsfunparms:certfmt=raw|vos=cms|dbg -vomsat:2 sec.protocol /usr/lib64 gsi -ca:1 -crl:3 This configuration will only authorize members of VO cms . You can change it to another VO. Make sure fetch-crl has been run otherwise the xrootd service may fail to start. In the xrootd client get a proxy without voms extension or with another VO extension different that the one used in the configuration: user@host $ voms-proxy-init -voms mis Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ........................... Done Contacting voms.opensciencegrid.org:15001 [/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=http/voms.opensciencegrid.org] \"mis\" Done Creating proxy ............................................... Done user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s] Run: [FATAL] Auth failed Now get a proxy with cms extension and run it again: user@host $ voms-proxy-init -voms cms Enter GRID pass phrase: Your identity: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Edgar Mauricio Fajardo Hernandez 2020 Creating temporary proxy ...................................... Done Contacting voms2.cern.ch:15002 [/DC=ch/DC=cern/OU=computers/CN=voms2.cern.ch] \"cms\" Done Creating proxy .......................................... Done Your proxy is valid until Thu Dec 4 22:53:29 2014 user@host $ xrdcp vomsxrdtest root://fermicloud024.fnal.gov:1094//tmp/ [0B/0B][100%][==================================================][0B/s]","title":"XRootD VOMS Testing"},{"location":"release/acceptance-testing/#hdfs","text":"","title":"HDFS"},{"location":"release/acceptance-testing/#hadoop-name-node-installation","text":"Use the following script with option 1: #!/bin/bash set -e select NODETYPE in namenode datanode gridftp; do [[ $NODETYPE ]] && break done case $NODETYPE in namenode ) NAMENODE=$HOSTNAME ;; * ) read -p 'hostname for NAMENODE? ' NAMENODE ;; esac echo NODETYPE=$NODETYPE echo NAMENODE=$NAMENODE read -p 'ok? [y/N] ' ok case $ok in y*|Y*) ;; # ok *) exit ;; esac #yum install --enablerepo=osg-minefield osg-se-hadoop-$NODETYPE yum install osg-se-hadoop-$NODETYPE case $NODETYPE in namenode|datanode ) mkdir -p /data/{hadoop,scratch,checkpoint} chown -R hdfs:hdfs /data sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml cp /etc/hadoop/conf.osg/{core,hdfs}-site.xml /etc/hadoop/conf/ touch /etc/hosts_exclude ;; gridftp ) ln -snf conf.osg /etc/hadoop/conf sed -i s/NAMENODE/$NAMENODE/ /etc/hadoop/conf.osg/{core,hdfs}-site.xml echo \"hadoop-fuse-dfs# /mnt/hadoop fuse server=$NAMENODE,port=9000,rdbuffer=131072,allow_other 0 0\" >> /etc/fstab mkdir /mnt/hadoop mount /mnt/hadoop cp -v /etc/redhat-release /mnt/hadoop/test-file sed -i '/globus_mapping/s/^# *//' /etc/grid-security/gsi-authz.conf sed -i s/yourgums.yourdomain/gums.fnal.gov/ /etc/lcmaps.db mkdir /mnt/hadoop/fnalgrid useradd fnalgrid -g fnalgrid chown fnalgrid:fnalgrid /mnt/hadoop/fnalgrid service globus-gridftp-server start if type -t globus-url-copy >/dev/null; then globus-url-copy file:////bin/bash gsiftp://$HOSTNAME/mnt/hadoop/fnalgrid/first_test else echo globus-url-copy not installed fi ;; esac case $NODETYPE in namenode ) su - hdfs -c \"hadoop namenode -format\" ;; esac service hadoop-hdfs-$NODETYPE start","title":"Hadoop name node installation"},{"location":"release/acceptance-testing/#edit-configuration","text":"Edit /etc/hadoop/conf/hdfs-site.xml set dfs.replication to 1 set dfs.replication.min to 1","title":"Edit Configuration"},{"location":"release/acceptance-testing/#hadoop-data-node-installation","text":"Run same script as before but with option number 2.","title":"Hadoop data node installation"},{"location":"release/acceptance-testing/#gridftp-installation","text":"Run same as script but with option number 3.","title":"GridFTP installation"},{"location":"release/acceptance-testing/#on-the-name-node","text":"[root@fermicloud092 ~]# hdfs dfs -ls /test-file Found 1 items -rw-r--r-- 2 root root 0 2014-07-21 15:57 /test-file","title":"On the name node"},{"location":"release/acceptance-testing/#on-the-name-node_1","text":"[root@]# hadoop fs -mkdir /matyas [root@]# hadoop fs -chown matyas /matyas [root@]# hdfs dfsadmin -setSpaceQuota 123k /matyas user@host $ dd if = /dev/zero of = /tmp/blob bs = 4096 count = 10000 user@host $ kx509 ; voms-proxy-init -noregen -voms fermilab user@host $ globus-url-copy -vb file:///tmp/blob gsiftp:// ` hostname -f ` /mnt/hadoop/matyas","title":"On the name node"},{"location":"release/acceptance-testing/#xrootd-plugins","text":"Install xrootd-server: yum install xrootd-server Install xrootd-plugins yum install xrootd-cmstfc xrootd-hdfs Modify the file /etc/xrootd/xrootd-clustered.cfg to look like this: xrd.port 1094 # The roles this server will play. all.role server all.role manager if xrootd.unl.edu # The known managers all.manager srm.unl.edu:1213 #all.manager xrootd.ultralight.org:1213 # Allow any path to be exported; this is further refined in the authfile. all.export / nostage # Hosts allowed to use this xrootd cluster cms.allow host * ### Standard directives # Simple sites probably don't need to touch these. # Logging verbosity xrootd.trace all -debug ofs.trace all -debug xrd.trace all -debug cms.trace all -debug # Integrate with CMS TFC, placed in /etc/storage.xml oss.namelib /usr/lib64/libXrdCmsTfc.so file:/etc/xrootd/storage.xml?protocol=hadoop xrootd.seclib /usr/lib64/libXrdSec.so xrootd.fslib /usr/lib64/libXrdOfs.so ofs.osslib /usr/lib64/libXrdHdfs.so all.adminpath /var/run/xrootd all.pidpath /var/run/xrootd cms.delay startup 10 cms.fxhold 60s cms.perf int 30s pgm /usr/bin/XrdOlbMonPerf 30 oss.space default_stage /opt/xrootd_cache Create file /etc/xrootd/storage.xml and place this: <storage-mapping> <lfn-to-pfn protocol=\"hadoop\" destination-match=\".*\" path-match=\".*/+tmp2/test-file\" result=\"/test-file\"/> </storage-mapping> For el7 the instrucctions are a little bit different. See: https://jira.opensciencegrid.org/browse/SOFTWARE-2198?focusedCommentId=334667&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-334667 Now from a node do: xrdcp --debug 3 root://yourdatanode.yourdomain:1094//tmp2/test-file . If it is sucessful it would have tested both cmstfc and hdfs plugins","title":"XRootD Plugins"},{"location":"release/announce-rft-packages/","text":"Ready for Testing Announcements \u00b6 Per our community testing policy , we must send weekly digests of packages that are ready for testing. Create the Announcement \u00b6 Step 1: Identify the packages that are \"Ready for Testing\" \u00b6 Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = \"<VERSION(S)>\" git clone https://github.com/opensciencegrid/release-tools.git cd release-tools 0 -generate-pkg-list $VERSIONS Note In the future, will we have a command the produces the package list sorted according to release series and importance. Step 2: Populate the Announcement Template \u00b6 Find the software components that the packages in the list correspond to. For example, htcondor-ce-4.4.0-1.osg35.el7 should be listed as \"HTCondor-CE 4.4.0\". Place software components into the appropriate section depending on release series and importance of the software. The major software components are listed in the community testing policy . Omit any software that does not need to tested by the community such osg-version and internal tools. Step 3: Send the \"Ready for Testing\" Announcement \u00b6 The announcement goes to: osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov OIM administrative contacts Use the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject 'OSG Packages Available for Testing' \\ --recipients \"osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative Announcement Template \u00b6 The following email template is filled out to announce that packages are ready for testing. Text between <ANGLE BRACKETS> should be replaced and sections without packages to be tested should be omitted. Omit release numbers unless they are relevant (e.g. for a packaging-only change). Each major component should have a line about what's new. Several packages are available for testing for tentative release next week. OSG 3.5 Only: - Major Components* - <Major Component Name and Version (NV)> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> Both OSG 3.5 and 3.4: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> OSG 3.4 Only: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> To install any of these packages, run the following command: # yum install --enablerepo=osg-testing <PACKAGE NAME> Please test this software and send positive or negative feedback to software-discuss@osg-htc.org. Be sure to include details describing your testing platform, e.g. OSG 3.4 vs 3.5, EL6 vs EL7! If you any questions, you can always contact us at help@osg-htc.org. JIRA Ticket Summary: https://opensciencegrid.atlassian.net/issues/?filter=12355 Sincerely, The OSG Software & Release Team * As described by our Community Software Testing Policy, (https://osg-htc.org/technology/policy/community-testing/) major components of the OSG Software Stack need positive feedback and the approval of the release manager before they can be released.","title":"Ready for Testing Announcements"},{"location":"release/announce-rft-packages/#ready-for-testing-announcements","text":"Per our community testing policy , we must send weekly digests of packages that are ready for testing.","title":"Ready for Testing Announcements"},{"location":"release/announce-rft-packages/#create-the-announcement","text":"","title":"Create the Announcement"},{"location":"release/announce-rft-packages/#step-1-identify-the-packages-that-are-ready-for-testing","text":"Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = \"<VERSION(S)>\" git clone https://github.com/opensciencegrid/release-tools.git cd release-tools 0 -generate-pkg-list $VERSIONS Note In the future, will we have a command the produces the package list sorted according to release series and importance.","title":"Step 1: Identify the packages that are \"Ready for Testing\""},{"location":"release/announce-rft-packages/#step-2-populate-the-announcement-template","text":"Find the software components that the packages in the list correspond to. For example, htcondor-ce-4.4.0-1.osg35.el7 should be listed as \"HTCondor-CE 4.4.0\". Place software components into the appropriate section depending on release series and importance of the software. The major software components are listed in the community testing policy . Omit any software that does not need to tested by the community such osg-version and internal tools.","title":"Step 2: Populate the Announcement Template"},{"location":"release/announce-rft-packages/#step-3-send-the-ready-for-testing-announcement","text":"The announcement goes to: osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov OIM administrative contacts Use the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject 'OSG Packages Available for Testing' \\ --recipients \"osg-sites@opensciencegrid.org cms-t2@fnal.gov usatlas-t2-l@lists.bnl.gov\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative","title":"Step 3: Send the \"Ready for Testing\" Announcement"},{"location":"release/announce-rft-packages/#announcement-template","text":"The following email template is filled out to announce that packages are ready for testing. Text between <ANGLE BRACKETS> should be replaced and sections without packages to be tested should be omitted. Omit release numbers unless they are relevant (e.g. for a packaging-only change). Each major component should have a line about what's new. Several packages are available for testing for tentative release next week. OSG 3.5 Only: - Major Components* - <Major Component Name and Version (NV)> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> Both OSG 3.5 and 3.4: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> OSG 3.4 Only: - Major Components* - <Major Component NV> - <DESCRIPTION> - <Major Component NV> - <DESCRIPTION> - Minor Components - <Minor Component NV> - <Minor Component NV> To install any of these packages, run the following command: # yum install --enablerepo=osg-testing <PACKAGE NAME> Please test this software and send positive or negative feedback to software-discuss@osg-htc.org. Be sure to include details describing your testing platform, e.g. OSG 3.4 vs 3.5, EL6 vs EL7! If you any questions, you can always contact us at help@osg-htc.org. JIRA Ticket Summary: https://opensciencegrid.atlassian.net/issues/?filter=12355 Sincerely, The OSG Software & Release Team * As described by our Community Software Testing Policy, (https://osg-htc.org/technology/policy/community-testing/) major components of the OSG Software Stack need positive feedback and the approval of the release manager before they can be released.","title":"Announcement Template"},{"location":"release/cut-sw-release/","text":"How to Cut a Software Release \u00b6 This document details the process for releasing new OSG Release version(s). This document does NOT discuss the policy for deciding what goes into a release, which can be found here . Due to the length of time that this process takes, it is recommended to do the release over two or more days to allow for errors to be corrected and tests to be run. Requirements \u00b6 UW netID registered with OSG's koji with build and release team privileges On laptop: kinit netid@AD.WISC.EDU An account on dumbo and UW CS to access UW's AFS On dumbo: kinit user@CS.WISC.EDU; aklog release-tools scripts in your PATH ( GitHub ) osg-build scripts in your PATH (installed via OSG yum repos or source ) Pick the Version Number \u00b6 The rest of this document makes references to <VERSION(S)> and <NON-UPCOMING VERSIONS(S)> , which refer to a space-delimited list of a date string plus the OSG version(s) and that same list minus the upcoming versions (e.g. 231130 3.6 3.6-upcoming 23 23-upcoming and 231130 3.6 23 ). Generally, the first number is the release date encoded as yymmdd . Also this document make references to <FULL VERSION(S)> , which refer to a space-delimited list of version numbers (e.g. 3.6.231130 23.231130 ). If you are unsure about either the version or revision, please consult the release manager. Day 0: Generate Preliminary Release List \u00b6 The release manager often needs a tentative list of packages to be released. This is done by finding the package differences between osg-testing and the current release. Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = '<VERSION(S)>' # laptop git clone https://github.com/opensciencegrid/release-tools.git cd release-tools ./0-generate-pkg-list $VERSIONS Day 1: Verify Pre-Release and Generate Tarballs \u00b6 This section is to be performed 1-2 days before the release (as designated by the release manager) to perform last checks of the release and create the client tarballs. Step 1: Verify Pre-Release \u00b6 Compare the list of packages already in pre-release to the final list for the release put together by the OSG Release Coordinator (who should have updated release-list in git). To do this, run the 1-verify-prerelease script from git: VERSIONS = '<VERSION(S)>' # laptop ./1-verify-prerelease $VERSIONS If there are any discrepancies, consult the release manager. You may have to tag or untag packages with the osg-koji tool. Step 2: Test Pre-Release in VM Universe \u00b6 To test pre-release, you will be kicking off a manual VM universe test run from osg-sw-submit.chtc.wisc.edu . Ensure that you meet the pre-requisites for submitting VM universe test runs Prepare the test suite by running: osg-run-tests -P 'Testing OSG pre-release' cd into the directory specified in the output of the previous command Submit the DAG: ./master-run.sh Note Test upcoming even though nothing will be released into upcoming. It is possible that a blahp (or some other) update in 3.X could affect upcoming. Note If there are failures, consult the release-manager before proceeding. Step 3: Regenerate the build repositories \u00b6 To avoid 404 errors when retrieving packages, it's necessary to regenerate the build repositories. Run the following script from a machine with your koji-registered user certificate: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # laptop ./1-regen-repos $NON_UPCOMING_VERSIONS Step 4: Create the client tarballs \u00b6 Create the OSG client tarballs on dumbo using the relevant script from git: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./docker-make-client-tarball --version $ver --all done The tarballs are found in the tarball-client directory. Step 5: Briefly test the client tarballs \u00b6 Test the OSG client tarballs in Docker containers on dumbo using the relevant release-tools script: As an unprivileged user , run the script: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./1-verify-tarballs $NON_UPCOMING_VERSIONS If you have time, try some of the binaries, such as grid-proxy-init. Step 6: Wait \u00b6 Wait for clearance. The OSG Release Coordinator (in consultation with the Software Team and any testers) need to sign off on the update before it is released. If you are releasing things over two days, this is a good place to stop for the day. Day 2: Pushing the Release \u00b6 Step 1: Upload the tarballs to AFS \u00b6 On dumbo , upload the tarballs to AFS. (This step moved to release day, since repo.opensciencegrid.org tarballs are automatically updated hourly from the VDT web site served out of AFS.) NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./2-upload-tarballs-to-afs $NON_UPCOMING_VERSIONS Step 2: Push from pre-release to release \u00b6 This script moves the packages into release, clones releases into new version-specific release repos, locks the repos and regenerates them. VERSIONS = '<VERSION(S)>' # laptop 2 -push-release $VERSIONS Step 3: Update the Release Information \u00b6 This script updates the release information in AFS. VERSIONS = '<VERSION(S)>' # laptop 2 -update-info $VERSIONS *.txt files are created and it should be verified that they've been moved to /p/vdt/public/html/release-info/ on UW's AFS. Step 4: Rebuild the Docker software base \u00b6 Go to the build-docker-image workflow page of the opensciencegrid/docker-software-base : https://github.com/opensciencegrid/docker-software-base/actions/workflows/build-container.yml Click the Run Workflow button, select the master branch, and click Run workflow . Step 5: Install the tarballs into OASIS \u00b6 Note You must be an OASIS manager of the mis VO to do these steps. Known managers as of 2014-07-22: Mat, Tim C, Tim T, Brian L. Get the uploader script from Git and run it with osgrun from the UW AFS install of the tarball client you made earlier. On a UW CSL machine: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone --depth 1 https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./upload-tarballs-to-oasis $ver done The script will automatically ssh you to oasis-login.opensciencegrid.org and give you instructions to complete the process. Step 6: Update the Docker WN client \u00b6 The GitHub repository at opensciencegrid/docker-osg-wn controls the contents and tags pushed for the opensciencegrid/osg-wn container image. Navigate to the build/push workflow Click the Run workflow button and select the master branch Verify that all builds succeed Step 7: Verify the CA certificates update \u00b6 If this release contains either the osg-ca-certs package, verify that the CA web site has been updated. Wait for the CA certificates to be updated. It may take a while for the updates to reach the mirror used to update the web site. The repository is checked hourly for updated CA certificates. Once the web page is updated, run the following command to update the CA certificates in the tarball installation and verify that the version of the CA certificates match the version that was promoted to release. # moria.cs.wisc.edu /p/vdt/workspace/tarball-client/current/amd64_rhel7/osgrun osg-update-data Step 8: Merge any pending documentation \u00b6 For each documentation ticket in this release, merge the pull requests mentioned in the description or comments. Step 9: Update News \u00b6 Make a new entry in the News section of the release series page. For the list of changes, make an entry for each package that contains short descriptive text that would inform a system administrator whether or not this change is of concern to them. Also, link in any release announcement web page that is available for the software. Look a prior releases of the same software for hints on where to find such a page. Examine the known issues and remove any that were resolved with this release. Of course, add any new ones that have come up. Spell check the news. Locally serve up the web pages and ensure that the formatting looks good and the links work as expected. docker run --rm -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material:7.1.0 Make a pull request, get it approved, and merged. When the web page is available, you can announce the release. Step 10: Announce the release \u00b6 The following instructions are meant for the release manager (or interim release manager). If you are not the release manager, let the release manager know that they can announce the release. The release manager writes the a release announcement for each version and sends it out. The announcement should mention a handful of the most important updates. Due to downstream formatting issues, each major change should end at column 76 or earlier. Here is a sample, replace <BRACKETED TEXT> with the appropriate values: Subject: Announcing OSG Software version <VERSION> We are pleased to announce OSG Software version <VERSION>! Changes to OSG <VERSION> include: - Major Change 1 - Major Change 2 - Major Change 3 Release notes and pointers to more documentation can be found at: https://osg-htc.org/docs/release/osg-36/#latest-news The OSG Docker images on Docker Hub (https://hub.docker.com/u/opensciencegrid/) have been updated to contain the new software. Need help? Let us know: http://www.osg-htc.org/docs/common/help/ We welcome feedback on this release! The release manager uses the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject '<EMAIL SUBJECT>' \\ --recipients \"osg-general@opensciencegrid.org osg-operations@opensciencegrid.org osg-sites@opensciencegrid.org software-discuss@osg-htc.org site-announce@opensciencegrid.org\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative Replacing <EMAIL SUBJECT> with an appropriate subject for your announcement and <PATH TO MESSAGE FILE> with the path to the file containing your message in plain text. The release manager releases the tickets marked 'Ready for Release' in the release's JIRA filter using the 'bulk change' function.","title":"How to Cut a Release"},{"location":"release/cut-sw-release/#how-to-cut-a-software-release","text":"This document details the process for releasing new OSG Release version(s). This document does NOT discuss the policy for deciding what goes into a release, which can be found here . Due to the length of time that this process takes, it is recommended to do the release over two or more days to allow for errors to be corrected and tests to be run.","title":"How to Cut a Software Release"},{"location":"release/cut-sw-release/#requirements","text":"UW netID registered with OSG's koji with build and release team privileges On laptop: kinit netid@AD.WISC.EDU An account on dumbo and UW CS to access UW's AFS On dumbo: kinit user@CS.WISC.EDU; aklog release-tools scripts in your PATH ( GitHub ) osg-build scripts in your PATH (installed via OSG yum repos or source )","title":"Requirements"},{"location":"release/cut-sw-release/#pick-the-version-number","text":"The rest of this document makes references to <VERSION(S)> and <NON-UPCOMING VERSIONS(S)> , which refer to a space-delimited list of a date string plus the OSG version(s) and that same list minus the upcoming versions (e.g. 231130 3.6 3.6-upcoming 23 23-upcoming and 231130 3.6 23 ). Generally, the first number is the release date encoded as yymmdd . Also this document make references to <FULL VERSION(S)> , which refer to a space-delimited list of version numbers (e.g. 3.6.231130 23.231130 ). If you are unsure about either the version or revision, please consult the release manager.","title":"Pick the Version Number"},{"location":"release/cut-sw-release/#day-0-generate-preliminary-release-list","text":"The release manager often needs a tentative list of packages to be released. This is done by finding the package differences between osg-testing and the current release. Run 0-generate-pkg-list from a machine that has your koji-registered user certificate: VERSIONS = '<VERSION(S)>' # laptop git clone https://github.com/opensciencegrid/release-tools.git cd release-tools ./0-generate-pkg-list $VERSIONS","title":"Day 0: Generate Preliminary Release List"},{"location":"release/cut-sw-release/#day-1-verify-pre-release-and-generate-tarballs","text":"This section is to be performed 1-2 days before the release (as designated by the release manager) to perform last checks of the release and create the client tarballs.","title":"Day 1: Verify Pre-Release and Generate Tarballs"},{"location":"release/cut-sw-release/#step-1-verify-pre-release","text":"Compare the list of packages already in pre-release to the final list for the release put together by the OSG Release Coordinator (who should have updated release-list in git). To do this, run the 1-verify-prerelease script from git: VERSIONS = '<VERSION(S)>' # laptop ./1-verify-prerelease $VERSIONS If there are any discrepancies, consult the release manager. You may have to tag or untag packages with the osg-koji tool.","title":"Step 1: Verify Pre-Release"},{"location":"release/cut-sw-release/#step-2-test-pre-release-in-vm-universe","text":"To test pre-release, you will be kicking off a manual VM universe test run from osg-sw-submit.chtc.wisc.edu . Ensure that you meet the pre-requisites for submitting VM universe test runs Prepare the test suite by running: osg-run-tests -P 'Testing OSG pre-release' cd into the directory specified in the output of the previous command Submit the DAG: ./master-run.sh Note Test upcoming even though nothing will be released into upcoming. It is possible that a blahp (or some other) update in 3.X could affect upcoming. Note If there are failures, consult the release-manager before proceeding.","title":"Step 2: Test Pre-Release in VM Universe"},{"location":"release/cut-sw-release/#step-3-regenerate-the-build-repositories","text":"To avoid 404 errors when retrieving packages, it's necessary to regenerate the build repositories. Run the following script from a machine with your koji-registered user certificate: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # laptop ./1-regen-repos $NON_UPCOMING_VERSIONS","title":"Step 3: Regenerate the build repositories"},{"location":"release/cut-sw-release/#step-4-create-the-client-tarballs","text":"Create the OSG client tarballs on dumbo using the relevant script from git: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./docker-make-client-tarball --version $ver --all done The tarballs are found in the tarball-client directory.","title":"Step 4: Create the client tarballs"},{"location":"release/cut-sw-release/#step-5-briefly-test-the-client-tarballs","text":"Test the OSG client tarballs in Docker containers on dumbo using the relevant release-tools script: As an unprivileged user , run the script: NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./1-verify-tarballs $NON_UPCOMING_VERSIONS If you have time, try some of the binaries, such as grid-proxy-init.","title":"Step 5: Briefly test the client tarballs"},{"location":"release/cut-sw-release/#step-6-wait","text":"Wait for clearance. The OSG Release Coordinator (in consultation with the Software Team and any testers) need to sign off on the update before it is released. If you are releasing things over two days, this is a good place to stop for the day.","title":"Step 6: Wait"},{"location":"release/cut-sw-release/#day-2-pushing-the-release","text":"","title":"Day 2: Pushing the Release"},{"location":"release/cut-sw-release/#step-1-upload-the-tarballs-to-afs","text":"On dumbo , upload the tarballs to AFS. (This step moved to release day, since repo.opensciencegrid.org tarballs are automatically updated hourly from the VDT web site served out of AFS.) NON_UPCOMING_VERSIONS = \"<NON-UPCOMING VERSION(S)>\" # dumbo.chtc.wisc.edu ./2-upload-tarballs-to-afs $NON_UPCOMING_VERSIONS","title":"Step 1: Upload the tarballs to AFS"},{"location":"release/cut-sw-release/#step-2-push-from-pre-release-to-release","text":"This script moves the packages into release, clones releases into new version-specific release repos, locks the repos and regenerates them. VERSIONS = '<VERSION(S)>' # laptop 2 -push-release $VERSIONS","title":"Step 2: Push from pre-release to release"},{"location":"release/cut-sw-release/#step-3-update-the-release-information","text":"This script updates the release information in AFS. VERSIONS = '<VERSION(S)>' # laptop 2 -update-info $VERSIONS *.txt files are created and it should be verified that they've been moved to /p/vdt/public/html/release-info/ on UW's AFS.","title":"Step 3: Update the Release Information"},{"location":"release/cut-sw-release/#step-4-rebuild-the-docker-software-base","text":"Go to the build-docker-image workflow page of the opensciencegrid/docker-software-base : https://github.com/opensciencegrid/docker-software-base/actions/workflows/build-container.yml Click the Run Workflow button, select the master branch, and click Run workflow .","title":"Step 4: Rebuild the Docker software base"},{"location":"release/cut-sw-release/#step-5-install-the-tarballs-into-oasis","text":"Note You must be an OASIS manager of the mis VO to do these steps. Known managers as of 2014-07-22: Mat, Tim C, Tim T, Brian L. Get the uploader script from Git and run it with osgrun from the UW AFS install of the tarball client you made earlier. On a UW CSL machine: FULL_VERSIONS = \"<FULL VERSION(S)>\" # dumbo.chtc.wisc.edu git clone --depth 1 https://github.com/opensciencegrid/tarball-client.git cd tarball-client for ver in $FULL_VERSIONS ; do ./upload-tarballs-to-oasis $ver done The script will automatically ssh you to oasis-login.opensciencegrid.org and give you instructions to complete the process.","title":"Step 5: Install the tarballs into OASIS"},{"location":"release/cut-sw-release/#step-6-update-the-docker-wn-client","text":"The GitHub repository at opensciencegrid/docker-osg-wn controls the contents and tags pushed for the opensciencegrid/osg-wn container image. Navigate to the build/push workflow Click the Run workflow button and select the master branch Verify that all builds succeed","title":"Step 6: Update the Docker WN client"},{"location":"release/cut-sw-release/#step-7-verify-the-ca-certificates-update","text":"If this release contains either the osg-ca-certs package, verify that the CA web site has been updated. Wait for the CA certificates to be updated. It may take a while for the updates to reach the mirror used to update the web site. The repository is checked hourly for updated CA certificates. Once the web page is updated, run the following command to update the CA certificates in the tarball installation and verify that the version of the CA certificates match the version that was promoted to release. # moria.cs.wisc.edu /p/vdt/workspace/tarball-client/current/amd64_rhel7/osgrun osg-update-data","title":"Step 7: Verify the CA certificates update"},{"location":"release/cut-sw-release/#step-8-merge-any-pending-documentation","text":"For each documentation ticket in this release, merge the pull requests mentioned in the description or comments.","title":"Step 8: Merge any pending documentation"},{"location":"release/cut-sw-release/#step-9-update-news","text":"Make a new entry in the News section of the release series page. For the list of changes, make an entry for each package that contains short descriptive text that would inform a system administrator whether or not this change is of concern to them. Also, link in any release announcement web page that is available for the software. Look a prior releases of the same software for hints on where to find such a page. Examine the known issues and remove any that were resolved with this release. Of course, add any new ones that have come up. Spell check the news. Locally serve up the web pages and ensure that the formatting looks good and the links work as expected. docker run --rm -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material:7.1.0 Make a pull request, get it approved, and merged. When the web page is available, you can announce the release.","title":"Step 9: Update News"},{"location":"release/cut-sw-release/#step-10-announce-the-release","text":"The following instructions are meant for the release manager (or interim release manager). If you are not the release manager, let the release manager know that they can announce the release. The release manager writes the a release announcement for each version and sends it out. The announcement should mention a handful of the most important updates. Due to downstream formatting issues, each major change should end at column 76 or earlier. Here is a sample, replace <BRACKETED TEXT> with the appropriate values: Subject: Announcing OSG Software version <VERSION> We are pleased to announce OSG Software version <VERSION>! Changes to OSG <VERSION> include: - Major Change 1 - Major Change 2 - Major Change 3 Release notes and pointers to more documentation can be found at: https://osg-htc.org/docs/release/osg-36/#latest-news The OSG Docker images on Docker Hub (https://hub.docker.com/u/opensciencegrid/) have been updated to contain the new software. Need help? Let us know: http://www.osg-htc.org/docs/common/help/ We welcome feedback on this release! The release manager uses the osg-notify tool on osg-sw-submit.chtc.wisc.edu to send the release announcement using the following command: $ osg-notify --cert your-cert.pem --key your-key.pem \\ --no-sign --type production --message <PATH TO MESSAGE FILE> \\ --subject '<EMAIL SUBJECT>' \\ --recipients \"osg-general@opensciencegrid.org osg-operations@opensciencegrid.org osg-sites@opensciencegrid.org software-discuss@osg-htc.org site-announce@opensciencegrid.org\" \\ --oim-recipients resources --oim-recipients vos --oim-contact-type administrative Replacing <EMAIL SUBJECT> with an appropriate subject for your announcement and <PATH TO MESSAGE FILE> with the path to the file containing your message in plain text. The release manager releases the tickets marked 'Ready for Release' in the release's JIRA filter using the 'bulk change' function.","title":"Step 10: Announce the release"},{"location":"release/empty-pkgs/","text":"Procedure for updating empty-* packages \u00b6 Background \u00b6 The empty-* packages were introduced a workaround for sites that install certain software (for example HTCondor or CA certs) from tarballs or other means that do not involve Yum/RPM. The packages contain no files, and exist merely to satisfy RPM dependencies so that other packages can be installed. It is the admin's responsibility to make sure that whatever component they installed the empty package for is functional. The empty packages are kept in a separate repository to prevent them from being accidentally installed instead of the component they claim to provide. Because of this, they do not go through the normal release process of development to testing to prerelease to release, but are moved straight from osg-development into osg-empty after developer testing. Warning It is important to untag the packages from osg-development immediately after promotion to osg-empty Procedure \u00b6 Prepare the package update, but do not build yet. Coordinate with the Software and Release Managers to set aside a good time to update the package. An empty package should not remain in the development repos for longer than a few hours. Build into development. Test out of development. Be thorough , as there is no separate acceptance testing for empty packages. In the JIRA ticket, document your testing procedure and request permission from both the Software and the Release Managers. (Since there is no acceptance testing, both of them have to sign off on the new build). After receiving permission, tag the builds into the osg-empty tags, and untag them from the osg-development tags. Then regenerate the osg-empty repos. osg-koji move-pkg osg-3.3-el6-development osg-3.3-el6-empty <EL6_BUILD_NVR> osg-koji move-pkg osg-3.3-el7-development osg-3.3-el7-empty <EL7_BUILD_NVR> osg-koji regen-repo --nowait osg-3.3-el6-empty osg-koji regen-repo --nowait osg-3.3-el7-empty","title":"Empty Packages"},{"location":"release/empty-pkgs/#procedure-for-updating-empty-packages","text":"","title":"Procedure for updating empty-* packages"},{"location":"release/empty-pkgs/#background","text":"The empty-* packages were introduced a workaround for sites that install certain software (for example HTCondor or CA certs) from tarballs or other means that do not involve Yum/RPM. The packages contain no files, and exist merely to satisfy RPM dependencies so that other packages can be installed. It is the admin's responsibility to make sure that whatever component they installed the empty package for is functional. The empty packages are kept in a separate repository to prevent them from being accidentally installed instead of the component they claim to provide. Because of this, they do not go through the normal release process of development to testing to prerelease to release, but are moved straight from osg-development into osg-empty after developer testing. Warning It is important to untag the packages from osg-development immediately after promotion to osg-empty","title":"Background"},{"location":"release/empty-pkgs/#procedure","text":"Prepare the package update, but do not build yet. Coordinate with the Software and Release Managers to set aside a good time to update the package. An empty package should not remain in the development repos for longer than a few hours. Build into development. Test out of development. Be thorough , as there is no separate acceptance testing for empty packages. In the JIRA ticket, document your testing procedure and request permission from both the Software and the Release Managers. (Since there is no acceptance testing, both of them have to sign off on the new build). After receiving permission, tag the builds into the osg-empty tags, and untag them from the osg-development tags. Then regenerate the osg-empty repos. osg-koji move-pkg osg-3.3-el6-development osg-3.3-el6-empty <EL6_BUILD_NVR> osg-koji move-pkg osg-3.3-el7-development osg-3.3-el7-empty <EL7_BUILD_NVR> osg-koji regen-repo --nowait osg-3.3-el6-empty osg-koji regen-repo --nowait osg-3.3-el7-empty","title":"Procedure"},{"location":"release/itb-testing/","text":"Testing OSG Software Prereleases on the Madison ITB Site \u00b6 This document contains basic recipes for testing a OSG software prereleases on the Madison ITB site, which includes HTCondor prerelease builds and full OSG software stack prereleases from Yum. Prerequisites \u00b6 The following items are known prerequisites to using this recipe. If you are not running the Ansible commands from osghost, there are almost certainly other prerequisites that are not listed below. And even using osghost for Ansible and itb-submit for the submissions, there may be other prerequisites missing. Please improve this document by adding other prerequisites as they are identified! A checkout of the osgitb directory from our local git instance (not GitHub) Your X.509 DN in the osgitb/unmanaged/htcondor-ce/grid-mapfile file and (via Ansible) on itb-ce1 and itb-ce2 Gathering Information \u00b6 Technically skippable, this section is about checking on the state of the ITB machines before making changes. The plan is to keep the ITB machines generally up-to-date independently, so those steps are not listed here. And honestly, the steps below are just some ideas; do whatever makes sense for the given update. The commands can be run as-is from within the osgitb directory from git. Check OS versions for all current ITB hosts: ansible current -i inventory -f 20 -o -m command -a 'cat /etc/redhat-release' Check the date and time on all hosts (in case NTP stops working): ansible current -i inventory -f 20 -o -m command -a 'date' Check software versions for certain hosts (e.g., for the condor package on hosts in the workers group): ansible workers -i inventory -f 20 -o -m command -a 'rpm -q condor' Installing HTCondor Prerelease \u00b6 Use this section to install a new version of HTCondor, specifically a prerelease build from the development or upcoming-development repository, on the test hosts. Obtain the NVR of the HTCondor prerelease build from OSG to test. Do this by talking to Tim T. and checking Koji. Shut down HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=stopped' ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=stopped' Install new version of HTCondor on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes update condor' or, if you need to install an NVR that is \u201cearlier\u201d (in the RPM sense) than what is currently installed: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes downgrade condor condor-classads condor-python condor-procd blahp' Verify correct RPM versions across the site: ansible condor -i inventory -f 20 -o -m command -a 'rpm -q condor' Restart HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=started' ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=started' Installing a Prerelease of the OSG Software Stack \u00b6 Use this section to install new versions of all OSG software from a prerelease repository in Yum. Check with the Release Manager to make sure that the prerelease repository has been populated with the desired package versions. Make sure that software is generally up-to-date on the hosts \u2014 see the Madison ITB Site doc for more details It may be desirable to update only non-OSG software at this stage, in which case one could simply disable the OSG repositories by adding command-line options to the yum update commands. Install new software on prerelease hosts: ansible testing -i inventory -bK -f 20 -m command -a 'yum --enablerepo=osg-prerelease --assumeyes update' Read the Yum output carefully, and follow up on any warnings, etc. If the osg-configure package was updated on any host(s), run the osg-configure command on the host(s): ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -v' -l [HOST(S)] ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -c' -l [HOST(S)] Verify OSG software updates by inspecting the Yum output carefully or examining specific package versions: ansible current -i inventory -f 20 -o -m command -a 'rpm -q osg-wn-client' Use an inventory group and package names that best fit the situation. Running Tests \u00b6 For the first two test workflows, use your personal space on itb-submit . Copy or checkout the osgitb/htcondor-tests directory to get the test directories. Part \u2160: Submitting jobs directly \u00b6 Change into the 1-direct-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in a few minutes. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt You should see a reasonable distribution of jobs by hostname, keeping in mind the different number of cores per machine and the fact that HTCondor can and will reuse claims to process many jobs on a single host. Especially watch out for a case in which no jobs run on the newly updated hosts (at the time of writing: itb-data[456] ). (Optional) Clean up, using the make clean or make distclean commands. Use the clean target to remove intermediate result and log files generated by a workflow run but preserve the final output file; use the distclean target to remove all workflow-generated files (plus Emacs backup files). Part \u2161: Submitting jobs using HTCondor-C \u00b6 If direct submissions fail, there is probably no point to doing this step. Change into the 2-htcondor-c-jobs subdirectory If there are old result files in the directory, remove them: make distclean Get a proxy for your X.509 credentials voms-proxy-init Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in 10 minutes or less; generally, this test takes longer than the direct submission test, because of the layers of indirection. Also, status updates from the CEs back to the submit host are infrequent. For direct information about the CEs, log in to itb-ce1 and itb-ce2 to check status; don\u2019t forget to check both condor_ce_q and condor_q on the CEs, probably in that order. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt Again, look for a reasonable distribution of jobs by hostname. (Optional) Clean up, using the make clean or make distclean commands. Part \u2162: Submitting jobs from a GlideinWMS VO Frontend \u00b6 For this workflow, use your personal space on glidein3.chtc.wisc.edu . Copy or checkout the osgitb/htcondor-tests directory to get the test directories. Again, if previous steps fail, do not bother with this step. Change into the 3-frontend-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck This workflow could take much longer than the first two, maybe an hour or so. Also, unless there are active glideins, it will take 10 minutes or longer for the first glideins to appear and start matching jobs. Thus it is helpful to monitor condor_q -totals until all of the jobs are submitted (there should be 2001), then switch to monitoring condor_status until glideins start appearing. After the first jobs start running and finishing, it is probably safe to ignore the rest of the run. If the jobs do not appear in the local queue, if glideins do not appear, or if jobs do not start running on the glideins, it is time to start troubleshooting. Check the final output file: cat count-by-hostnames.txt The distribution of jobs per execute node may be more skewed than in the first two workflows, due to the way in which pilots ramp up over time and how HTCondor allocates jobs to slots. (Optional) Clean up, using the make clean or make distclean commands.","title":"ITB Prerelease Testing"},{"location":"release/itb-testing/#testing-osg-software-prereleases-on-the-madison-itb-site","text":"This document contains basic recipes for testing a OSG software prereleases on the Madison ITB site, which includes HTCondor prerelease builds and full OSG software stack prereleases from Yum.","title":"Testing OSG Software Prereleases on the Madison ITB Site"},{"location":"release/itb-testing/#prerequisites","text":"The following items are known prerequisites to using this recipe. If you are not running the Ansible commands from osghost, there are almost certainly other prerequisites that are not listed below. And even using osghost for Ansible and itb-submit for the submissions, there may be other prerequisites missing. Please improve this document by adding other prerequisites as they are identified! A checkout of the osgitb directory from our local git instance (not GitHub) Your X.509 DN in the osgitb/unmanaged/htcondor-ce/grid-mapfile file and (via Ansible) on itb-ce1 and itb-ce2","title":"Prerequisites"},{"location":"release/itb-testing/#gathering-information","text":"Technically skippable, this section is about checking on the state of the ITB machines before making changes. The plan is to keep the ITB machines generally up-to-date independently, so those steps are not listed here. And honestly, the steps below are just some ideas; do whatever makes sense for the given update. The commands can be run as-is from within the osgitb directory from git. Check OS versions for all current ITB hosts: ansible current -i inventory -f 20 -o -m command -a 'cat /etc/redhat-release' Check the date and time on all hosts (in case NTP stops working): ansible current -i inventory -f 20 -o -m command -a 'date' Check software versions for certain hosts (e.g., for the condor package on hosts in the workers group): ansible workers -i inventory -f 20 -o -m command -a 'rpm -q condor'","title":"Gathering Information"},{"location":"release/itb-testing/#installing-htcondor-prerelease","text":"Use this section to install a new version of HTCondor, specifically a prerelease build from the development or upcoming-development repository, on the test hosts. Obtain the NVR of the HTCondor prerelease build from OSG to test. Do this by talking to Tim T. and checking Koji. Shut down HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=stopped' ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=stopped' Install new version of HTCondor on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes update condor' or, if you need to install an NVR that is \u201cearlier\u201d (in the RPM sense) than what is currently installed: ansible 'testing:&condor' -i inventory -bK -f 10 -m command -a 'yum --enablerepo=osg-development --assumeyes downgrade condor condor-classads condor-python condor-procd blahp' Verify correct RPM versions across the site: ansible condor -i inventory -f 20 -o -m command -a 'rpm -q condor' Restart HTCondor and HTCondor-CE on prerelease machines: ansible 'testing:&condor' -i inventory -bK -f 20 -m service -a 'name=condor state=started' ansible 'testing:&ces' -i inventory -bK -f 20 -m service -a 'name=condor-ce state=started'","title":"Installing HTCondor Prerelease"},{"location":"release/itb-testing/#installing-a-prerelease-of-the-osg-software-stack","text":"Use this section to install new versions of all OSG software from a prerelease repository in Yum. Check with the Release Manager to make sure that the prerelease repository has been populated with the desired package versions. Make sure that software is generally up-to-date on the hosts \u2014 see the Madison ITB Site doc for more details It may be desirable to update only non-OSG software at this stage, in which case one could simply disable the OSG repositories by adding command-line options to the yum update commands. Install new software on prerelease hosts: ansible testing -i inventory -bK -f 20 -m command -a 'yum --enablerepo=osg-prerelease --assumeyes update' Read the Yum output carefully, and follow up on any warnings, etc. If the osg-configure package was updated on any host(s), run the osg-configure command on the host(s): ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -v' -l [HOST(S)] ansible testing -i inventory -bK -f 20 -m command -a 'osg-configure -c' -l [HOST(S)] Verify OSG software updates by inspecting the Yum output carefully or examining specific package versions: ansible current -i inventory -f 20 -o -m command -a 'rpm -q osg-wn-client' Use an inventory group and package names that best fit the situation.","title":"Installing a Prerelease of the OSG Software Stack"},{"location":"release/itb-testing/#running-tests","text":"For the first two test workflows, use your personal space on itb-submit . Copy or checkout the osgitb/htcondor-tests directory to get the test directories.","title":"Running Tests"},{"location":"release/itb-testing/#part-i-submitting-jobs-directly","text":"Change into the 1-direct-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in a few minutes. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt You should see a reasonable distribution of jobs by hostname, keeping in mind the different number of cores per machine and the fact that HTCondor can and will reuse claims to process many jobs on a single host. Especially watch out for a case in which no jobs run on the newly updated hosts (at the time of writing: itb-data[456] ). (Optional) Clean up, using the make clean or make distclean commands. Use the clean target to remove intermediate result and log files generated by a workflow run but preserve the final output file; use the distclean target to remove all workflow-generated files (plus Emacs backup files).","title":"Part \u2160: Submitting jobs directly"},{"location":"release/itb-testing/#part-ii-submitting-jobs-using-htcondor-c","text":"If direct submissions fail, there is probably no point to doing this step. Change into the 2-htcondor-c-jobs subdirectory If there are old result files in the directory, remove them: make distclean Get a proxy for your X.509 credentials voms-proxy-init Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck In the initial test runs, the entire workflow ran in 10 minutes or less; generally, this test takes longer than the direct submission test, because of the layers of indirection. Also, status updates from the CEs back to the submit host are infrequent. For direct information about the CEs, log in to itb-ce1 and itb-ce2 to check status; don\u2019t forget to check both condor_ce_q and condor_q on the CEs, probably in that order. If the DAG or jobs exit immediately, go on hold, or otherwise fail, then you have some troubleshooting to do! Keep trying steps 2 and 3 until you get a clean run (or one or more HTCondor bug tickets). Check the final output file: cat count-by-hostnames.txt Again, look for a reasonable distribution of jobs by hostname. (Optional) Clean up, using the make clean or make distclean commands.","title":"Part \u2161: Submitting jobs using HTCondor-C"},{"location":"release/itb-testing/#part-iii-submitting-jobs-from-a-glideinwms-vo-frontend","text":"For this workflow, use your personal space on glidein3.chtc.wisc.edu . Copy or checkout the osgitb/htcondor-tests directory to get the test directories. Again, if previous steps fail, do not bother with this step. Change into the 3-frontend-jobs subdirectory If there are old result files in the directory, remove them: make distclean Submit the test workflow condor_submit_dag test.dag Monitor the jobs until they are complete or stuck This workflow could take much longer than the first two, maybe an hour or so. Also, unless there are active glideins, it will take 10 minutes or longer for the first glideins to appear and start matching jobs. Thus it is helpful to monitor condor_q -totals until all of the jobs are submitted (there should be 2001), then switch to monitoring condor_status until glideins start appearing. After the first jobs start running and finishing, it is probably safe to ignore the rest of the run. If the jobs do not appear in the local queue, if glideins do not appear, or if jobs do not start running on the glideins, it is time to start troubleshooting. Check the final output file: cat count-by-hostnames.txt The distribution of jobs per execute node may be more skewed than in the first two workflows, due to the way in which pilots ramp up over time and how HTCondor allocates jobs to slots. (Optional) Clean up, using the make clean or make distclean commands.","title":"Part \u2162: Submitting jobs from a GlideinWMS VO Frontend"},{"location":"release/new-os-series/","text":"How to Add a New Enterprise Linux Series \u00b6 Throughout this document, we will refer to the new Enterprise Linux series as ELX , and the previous EL series as ELX.OLD . For example, if we are adding el9, then ELX refers to el9 , and ELX.OLD refers to el8 . This document explains how to add support for a new ELX series to an existing OSG series. For adding a new OSG series, see the New Release Series documentation. See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure. Prepare Koji and OSG-Build \u00b6 Add ELX Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-elX-tags-etc In particular, update EL as appropriate (eg, el9 ), and update the ### external repos ### section with a new block of external repos to add to the dist-$EL-build tag. Then for the OSG-series specific tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, set SERIES to the current OSG series, and include ONLY the new ELX in the EL loop (eg, el9 ). (Do not include EL versions that already exist for this series.) Then for the devops tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-devops-tags-etc In particular, set SERIES to the current OSG series, and set EL to the new ELX in the EL loop (eg, el9 ). Add Koji package signing, as necessary With any luck, you can use the existing RPM signing key for the OSG series to which you are adding the new EL series. If it turns out that you need to create a new RPM signing key for ELX (because reusing the one for the current OSG series doesn't work in ELX for some unexpected reason), then you will need to generate a new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config. See Infrastructure Google Drive folder for details. Either way, you will need to make modifications to the osg-services repo, gitolite@git.chtc.wisc.edu:osg-services.git , so get a checkout of that ready. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services If you are adding a new RPM signing key, you need to edit koji/roles/signplugin/vars/main.yml to add the key name, password, and list of tags the key should be used for; and koji/roles/signplugin/templates/sign.conf.j2 to add template code for generating the sign.conf config blocks for those tags. If you are using the existing RPM signing key for the OSG series, you only need to edit koji/roles/signplugin/vars/main.yml . Find the tags section for your current signing key, eg, osg3_build_tags , and add all ELX build tags to this section. Eg, for el9 to OSG 3.6: osg3_build_tags: - dist-el9-build - osg-el9-internal-build - osg-3.6-el9-build - osg-3.6-upcoming-el9-build Apply the Koji Ansible config on the Koji Hub host. # ssh koji.chtc.wisc.edu # git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd ~/osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply If you are adding a new RPM signing key, export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-<N> (where <N> is the previous key's number incremented by one), and add it to the osg-release RPM. In the script generate-repo-files.sh ensure that the logic for selecting the GPGKEY includes the correct behavior for the new ELX to reference the latest key file. Update osg-build to add the new ELX to the various dvers in python scripts, and extra_dvers in promoter.ini ; and add the new ELX tags and targets to the test scripts. See the Git commits on opensciencegrid/osg-build for SOFTWARE-5342 for details on how to do this. Use this version of osg-build for subsequent steps. Subsequent Steps \u00b6 This section is incomplete. But for starters, begin with the Build prerequisite packages section of the New Release Series documentation. In general, you will not have to repeat steps for creating a new osg-3.Y series, but you will have to create a new buildsys-macros.elX package for the new EL9 series. Good luck.","title":"New OS Series"},{"location":"release/new-os-series/#how-to-add-a-new-enterprise-linux-series","text":"Throughout this document, we will refer to the new Enterprise Linux series as ELX , and the previous EL series as ELX.OLD . For example, if we are adding el9, then ELX refers to el9 , and ELX.OLD refers to el8 . This document explains how to add support for a new ELX series to an existing OSG series. For adding a new OSG series, see the New Release Series documentation. See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure.","title":"How to Add a New Enterprise Linux Series"},{"location":"release/new-os-series/#prepare-koji-and-osg-build","text":"Add ELX Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-elX-tags-etc In particular, update EL as appropriate (eg, el9 ), and update the ### external repos ### section with a new block of external repos to add to the dist-$EL-build tag. Then for the OSG-series specific tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, set SERIES to the current OSG series, and include ONLY the new ELX in the EL loop (eg, el9 ). (Do not include EL versions that already exist for this series.) Then for the devops tags, modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-devops-tags-etc In particular, set SERIES to the current OSG series, and set EL to the new ELX in the EL loop (eg, el9 ). Add Koji package signing, as necessary With any luck, you can use the existing RPM signing key for the OSG series to which you are adding the new EL series. If it turns out that you need to create a new RPM signing key for ELX (because reusing the one for the current OSG series doesn't work in ELX for some unexpected reason), then you will need to generate a new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config. See Infrastructure Google Drive folder for details. Either way, you will need to make modifications to the osg-services repo, gitolite@git.chtc.wisc.edu:osg-services.git , so get a checkout of that ready. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services If you are adding a new RPM signing key, you need to edit koji/roles/signplugin/vars/main.yml to add the key name, password, and list of tags the key should be used for; and koji/roles/signplugin/templates/sign.conf.j2 to add template code for generating the sign.conf config blocks for those tags. If you are using the existing RPM signing key for the OSG series, you only need to edit koji/roles/signplugin/vars/main.yml . Find the tags section for your current signing key, eg, osg3_build_tags , and add all ELX build tags to this section. Eg, for el9 to OSG 3.6: osg3_build_tags: - dist-el9-build - osg-el9-internal-build - osg-3.6-el9-build - osg-3.6-upcoming-el9-build Apply the Koji Ansible config on the Koji Hub host. # ssh koji.chtc.wisc.edu # git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd ~/osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply If you are adding a new RPM signing key, export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-<N> (where <N> is the previous key's number incremented by one), and add it to the osg-release RPM. In the script generate-repo-files.sh ensure that the logic for selecting the GPGKEY includes the correct behavior for the new ELX to reference the latest key file. Update osg-build to add the new ELX to the various dvers in python scripts, and extra_dvers in promoter.ini ; and add the new ELX tags and targets to the test scripts. See the Git commits on opensciencegrid/osg-build for SOFTWARE-5342 for details on how to do this. Use this version of osg-build for subsequent steps.","title":"Prepare Koji and OSG-Build"},{"location":"release/new-os-series/#subsequent-steps","text":"This section is incomplete. But for starters, begin with the Build prerequisite packages section of the New Release Series documentation. In general, you will not have to repeat steps for creating a new osg-3.Y series, but you will have to create a new buildsys-macros.elX package for the new EL9 series. Good luck.","title":"Subsequent Steps"},{"location":"release/new-release-series/","text":"How to Prepare a New Release Series \u00b6 Throughout this document, we will refer to the new release series as 3.X , and the previous release series as 3.OLD . For example, if we are creating OSG 3.7, then 3.X refers to 3.7 , and 3.OLD refers to 3.6 . See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure. Prepare Koji and OSG-Build \u00b6 Add 3.X and 3.X-upcoming Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, update SERIES as appropriate, and include any applicable Enterprise Linux versions to the EL loop (eg, el7 el8 ) Add Koji package signing Starting with OSG 3.6, we've been using a different RPM signing key for each series. Generate the new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config (see Infrastructure Google Drive folder for details). Use a strong algorithm for the key; 4096-bit RSA is recommended. Note: generate RSA keys on EL9 (e.g. in a container) or they will not be importable in EL9. Edit koji/roles/signplugin/vars/main.yml and koji/roles/signplugin/templates/sign.conf.j2 in the Koji Ansible config to add the key name, password, list of tags the key should be used for, and template code for generating the sign.conf config blocks for those tags. Tags for EL9 and newer distros should have gpg_digest_algo = sha256 set. Apply the Koji Ansible config on the Koji Hub host. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply Export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-3.X , and add it to the osg-release RPM. Add the file and modify the template.repo.* files to reference the new key file. Update Koji policy as needed (for new distro versions); see SOFTWARE-5426 for details. Update osg-build to use the new koji tags and targets (not by default of course). See the Git commits on opensciencegrid/osg-build for SOFTWARE-2693 for details on how to do this. Use this version for subsequent steps. Build prerequisite packages \u00b6 Create a blank X-main SVN branch and add buildsys-macros.elY packages, one for each supported distro version. As an example, here's what you'd do for osg-23 and el8: svn copy the buildsys-macros.elX directories from the osg-3.OLD branch and hand-edit it to hardcode the new osg_version and dver values. $ cd native/redhat/branches $ svn mkdir 23 -main $ svn copy osg-3.6/buildsys-macros.el8 23 -main/buildsys-macros.el8 $ cd 23 -main/buildsys-macros.el8 $ $EDITOR osg/*.spec # ## change the osg_version and dver values as appropriate Build locally and import the resulting RPMs (need Koji admin permissions). Run the following commands (adjust the NVR and distro version as necessary): :::console $ osg-build rpmbuild --el8 $ osg-koji import _build_results/buildsys-macros-*.el8.src.rpm $ osg-koji import _build_results/buildsys-macros-*.el8.noarch.rpm $ pkg=$(basename _build_results/buildsys-macros-*.el8.src.rpm .src.rpm) $ osg-koji tag-pkg osg-23-main-el8-development \"$pkg\" Bump the revision in each buildsys-macros.elY spec file and edit the %changelog , svn commit , then do Koji builds of them. Again, with osg-3.7 and el8: $ osg-build koji --repo = 23 -main --el8 23 -main/buildsys-macros.el8 Repeat the previous steps for X-upcoming and X-internal Update tarball-client bundles.ini patches/ upload-tarballs-to-oasis (for X, foreach_dver_arch will need to be updated for the new set of X dver_arches ) Add relase-series specific repos/osg-23-main-el<DVER>.repo.in for each supported distro version (e.g., 8 , 9 ) Populate the bootstrap tags Need to have them inherit from the OLD development tags, but only packages, not builds (hence the --noconfig ; yes, the name is weird) # set OLD and NEW as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do osg-koji add-tag-inheritance --noconfig --priority=2 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-main-$el-development; osg-koji add-tag-inheritance --noconfig --priority=3 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-upcoming-$el-development; done Get the actual NVRs to tag I put Brian's spreadsheet into Excel and used its filtering feature to separate out: the packages going into 3.X.0 package differences between each dver (eg, el7 vs el8) save the NVRs for each dver to a separate file, eg, pkgtotag-el7.txt and pkgtotag-el8.txt Tagging: # set X as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do \\ xargs -a pkgtotag-$el osg-koji tag-pkg osg-X-main-$el-bootstrap; \\ done (btw, xargs -a doesn't work on a Mac) In order to make testing easier, build the new osg-release and osg-release-itb packages and promote them all the way to release, so that all the 3.X repos exist and have at least one rpm in them. Prepare repo and test infrastructure \u00b6 Update mash to pull from the new tags, using the new key On repo-itb On repo Put the new public key on repo and repo-itb Update documentation here Update osg-test / vmu-test-runs They're only going to test from minefield (and eventually testing) until the release Build software \u00b6 Populate SVN branches and tags (as in fill it with the packages we're going to release for 3.X and 3.X-upcoming) Mass rebuild Don't forget to update the empty and contrib tags with the appropriate packages; remove the empty* packages from the development tags after they've been tagged into the empty tags Drop the osg-X-main-elY-bootstrap koji tags (after the successful mass rebuild only) Update docker-software-base and any container images that are based on it Release! \u00b6 Update release tools scripts as necessary Cut a release Have a release party Update this document and the Infrastructure Google Drive folder with issues you ran into Post-release \u00b6 Update osg-test / vmu-test-runs again to add release and release -> testing tests Update the tarball that is used to keep the CA certificates and VO data current in CVMFS. Logon as ouser.mis@oasis-login.opensciencegrid.org and follow the directions in the README file. Update the koji osg-elY build targets to build from and to X instead of OLD ; notify the software-discuss list of this change Update the docker-osg-wn-client scripts to build from X (need direct push access) Update the constants in the genbranches script in the docker-osg-wn-scripts repo Update the branches in docker-osg-wn-client ; a script like this ought to work: git clone git@github.com:opensciencegrid/docker-osg-wn-scripts.git git clone git@github.com:opensciencegrid/docker-osg-wn.git cd docker-osg-wn-scripts ./genbranches cd ../docker-osg-wn for bpath in ../docker-osg-wn-scripts/branches/* ; do b = ${ bpath ##*/ } git checkout -b $b master && \\ mv $bpath Dockerfile.in && \\ git add Dockerfile.in && \\ git commit -m \"Add branch $b \" done and then run a similar script to update the existing branches Check the results before pushing, and then run git push --all Update the arrays in update-all and osg-wn-nightly-build in docker-osg-wn-scripts Update the default promotion route aliases in osg-promote Update documentation again to reflect that X is now the main branch and OLD is the maintenance branch","title":"New Release Series"},{"location":"release/new-release-series/#how-to-prepare-a-new-release-series","text":"Throughout this document, we will refer to the new release series as 3.X , and the previous release series as 3.OLD . For example, if we are creating OSG 3.7, then 3.X refers to 3.7 , and 3.OLD refers to 3.6 . See the documentation in the OSG Technology/Software and Release/Infrastructure Google Drive folder for details on the infrastructure.","title":"How to Prepare a New Release Series"},{"location":"release/new-release-series/#prepare-koji-and-osg-build","text":"Add 3.X and 3.X-upcoming Koji tags and targets Modify this script as appropriate and run: https://github.com/opensciencegrid/osg-next-tools/blob/master/koji/create-new-koji-osg3X-tags-etc In particular, update SERIES as appropriate, and include any applicable Enterprise Linux versions to the EL loop (eg, el7 el8 ) Add Koji package signing Starting with OSG 3.6, we've been using a different RPM signing key for each series. Generate the new key in the keyring for the Koji sign plugin, and save it (encrypted) in the Koji Ansible config (see Infrastructure Google Drive folder for details). Use a strong algorithm for the key; 4096-bit RSA is recommended. Note: generate RSA keys on EL9 (e.g. in a container) or they will not be importable in EL9. Edit koji/roles/signplugin/vars/main.yml and koji/roles/signplugin/templates/sign.conf.j2 in the Koji Ansible config to add the key name, password, list of tags the key should be used for, and template code for generating the sign.conf config blocks for those tags. Tags for EL9 and newer distros should have gpg_digest_algo = sha256 set. Apply the Koji Ansible config on the Koji Hub host. $ ssh koji.chtc.wisc.edu $ git clone gitolite@git.chtc.wisc.edu:osg-services.git $ cd osg-services/koji $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --check --diff secure.yml # If the above looks good, run again without --check to apply for real $ ansible-playbook -K -c local -l $( hostname -f ) --ask-vault-pass --diff secure.yml # -K = prompt you for sudo password ( BECOME password ) # -c local = use the \"local\" connection method # -l $( hostname -f ) = apply the changes to the current machine only # --ask-vault-pass = prompt you for the ansible-vault pw # --check = dry-run mode # --diff = show the diffs of any file changes it ( would ) make # secure.yml = the \"playbook\" of changes to apply Export the ASCII-armored public key as RPM-GPG-OSG-KEY-OSG-3.X , and add it to the osg-release RPM. Add the file and modify the template.repo.* files to reference the new key file. Update Koji policy as needed (for new distro versions); see SOFTWARE-5426 for details. Update osg-build to use the new koji tags and targets (not by default of course). See the Git commits on opensciencegrid/osg-build for SOFTWARE-2693 for details on how to do this. Use this version for subsequent steps.","title":"Prepare Koji and OSG-Build"},{"location":"release/new-release-series/#build-prerequisite-packages","text":"Create a blank X-main SVN branch and add buildsys-macros.elY packages, one for each supported distro version. As an example, here's what you'd do for osg-23 and el8: svn copy the buildsys-macros.elX directories from the osg-3.OLD branch and hand-edit it to hardcode the new osg_version and dver values. $ cd native/redhat/branches $ svn mkdir 23 -main $ svn copy osg-3.6/buildsys-macros.el8 23 -main/buildsys-macros.el8 $ cd 23 -main/buildsys-macros.el8 $ $EDITOR osg/*.spec # ## change the osg_version and dver values as appropriate Build locally and import the resulting RPMs (need Koji admin permissions). Run the following commands (adjust the NVR and distro version as necessary): :::console $ osg-build rpmbuild --el8 $ osg-koji import _build_results/buildsys-macros-*.el8.src.rpm $ osg-koji import _build_results/buildsys-macros-*.el8.noarch.rpm $ pkg=$(basename _build_results/buildsys-macros-*.el8.src.rpm .src.rpm) $ osg-koji tag-pkg osg-23-main-el8-development \"$pkg\" Bump the revision in each buildsys-macros.elY spec file and edit the %changelog , svn commit , then do Koji builds of them. Again, with osg-3.7 and el8: $ osg-build koji --repo = 23 -main --el8 23 -main/buildsys-macros.el8 Repeat the previous steps for X-upcoming and X-internal Update tarball-client bundles.ini patches/ upload-tarballs-to-oasis (for X, foreach_dver_arch will need to be updated for the new set of X dver_arches ) Add relase-series specific repos/osg-23-main-el<DVER>.repo.in for each supported distro version (e.g., 8 , 9 ) Populate the bootstrap tags Need to have them inherit from the OLD development tags, but only packages, not builds (hence the --noconfig ; yes, the name is weird) # set OLD and NEW as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do osg-koji add-tag-inheritance --noconfig --priority=2 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-main-$el-development; osg-koji add-tag-inheritance --noconfig --priority=3 \\ osg-$NEW-main-$el-bootstrap osg-$OLD-upcoming-$el-development; done Get the actual NVRs to tag I put Brian's spreadsheet into Excel and used its filtering feature to separate out: the packages going into 3.X.0 package differences between each dver (eg, el7 vs el8) save the NVRs for each dver to a separate file, eg, pkgtotag-el7.txt and pkgtotag-el8.txt Tagging: # set X as appropriate, specify any relevant dvers for el $ for el in el8 el9 ; do \\ xargs -a pkgtotag-$el osg-koji tag-pkg osg-X-main-$el-bootstrap; \\ done (btw, xargs -a doesn't work on a Mac) In order to make testing easier, build the new osg-release and osg-release-itb packages and promote them all the way to release, so that all the 3.X repos exist and have at least one rpm in them.","title":"Build prerequisite packages"},{"location":"release/new-release-series/#prepare-repo-and-test-infrastructure","text":"Update mash to pull from the new tags, using the new key On repo-itb On repo Put the new public key on repo and repo-itb Update documentation here Update osg-test / vmu-test-runs They're only going to test from minefield (and eventually testing) until the release","title":"Prepare repo and test infrastructure"},{"location":"release/new-release-series/#build-software","text":"Populate SVN branches and tags (as in fill it with the packages we're going to release for 3.X and 3.X-upcoming) Mass rebuild Don't forget to update the empty and contrib tags with the appropriate packages; remove the empty* packages from the development tags after they've been tagged into the empty tags Drop the osg-X-main-elY-bootstrap koji tags (after the successful mass rebuild only) Update docker-software-base and any container images that are based on it","title":"Build software"},{"location":"release/new-release-series/#release","text":"Update release tools scripts as necessary Cut a release Have a release party Update this document and the Infrastructure Google Drive folder with issues you ran into","title":"Release!"},{"location":"release/new-release-series/#post-release","text":"Update osg-test / vmu-test-runs again to add release and release -> testing tests Update the tarball that is used to keep the CA certificates and VO data current in CVMFS. Logon as ouser.mis@oasis-login.opensciencegrid.org and follow the directions in the README file. Update the koji osg-elY build targets to build from and to X instead of OLD ; notify the software-discuss list of this change Update the docker-osg-wn-client scripts to build from X (need direct push access) Update the constants in the genbranches script in the docker-osg-wn-scripts repo Update the branches in docker-osg-wn-client ; a script like this ought to work: git clone git@github.com:opensciencegrid/docker-osg-wn-scripts.git git clone git@github.com:opensciencegrid/docker-osg-wn.git cd docker-osg-wn-scripts ./genbranches cd ../docker-osg-wn for bpath in ../docker-osg-wn-scripts/branches/* ; do b = ${ bpath ##*/ } git checkout -b $b master && \\ mv $bpath Dockerfile.in && \\ git add Dockerfile.in && \\ git commit -m \"Add branch $b \" done and then run a similar script to update the existing branches Check the results before pushing, and then run git push --all Update the arrays in update-all and osg-wn-nightly-build in docker-osg-wn-scripts Update the default promotion route aliases in osg-promote Update documentation again to reflect that X is now the main branch and OLD is the maintenance branch","title":"Post-release"},{"location":"release/release-eol/","text":"Release Series End-of-Life \u00b6 When a release reaches end-of-life, we need to discountinue a few items. Remove the retired series from the OSG VMU tests. However, retain the upgrade test from the retired series to the current series. Remove any github actions that build software-base or osg-wn-client Docker images for the retired series. Previous Release Series Removal Plan \u00b6 In order to reduce clutter and disk usage on our repositories and build system, we will remove older OSG Software release series. This will result in packages from those series becoming unavailable, so we will remove a release series when its packages are no longer needed. We will remove a release series no earlier than when the following series is completely out of support. For example, OSG 3.1 will be removed when OSG 3.2 is out of support, and OSG 3.2 will be removed when OSG 3.3 is out of support. Tasks \u00b6 Removing a release series requires work from both Operations and Software & Release. The first step is to create a JIRA ticket in the SOFTWARE project to track the work. Second, Software & Release will enumerate the directories for Operations to remove. Operations tasks should be completed before Software & Release tasks. Operations \u00b6 These tasks should be completed in order. Two weeks in advance, notify sites (including mirror sites) that the release series is going away. See the template email below. Remove the series from the mash configs on the repo.opensciencegrid.org machines: Add the koji tags for the old series to the /usr/local/osg-tags.excluded file: # cd /usr/local # fgrep osg-3.1 osg-tags osg-3.1-el5-contrib osg-3.1-el5-development osg-3.1-el5-release osg-3.1-el5-testing osg-3.1-el6-contrib osg-3.1-el6-development osg-3.1-el6-release osg-3.1-el6-testing # fgrep osg-3.1 osg-tags >> osg-tags.exclude Re-run update_mashfiles.sh to update the mash config files: # ./update_mashfiles.sh Remove the appropriate repo directories from /usr/local/repo/osg . # rm -rf repo*/osg/3.1/ Reclaim space from any cached rpms in the mash cache which are no longer linked elsewhere: # find mash/cache/ -name \\* .rpm -type f -links 1 -delete Wait for mash to run and verify that the repos are no longer getting updated: Look at the mash logs in /var/log/repo . Verify that mash did not recreate the repo directory under /usr/local/repo/osg corresponding to the old release series. Remove tarballs from repo and OASIS Software & Release \u00b6 These tasks can be completed in any order. Tag and remove the SVN branch corresponding to the release series. Edit vm-test-runs and remove any \"long tail\" tests that reference the series. Edit tarball-client : Remove bundles from bundles.ini . Remove patch and other files that were used only by those bundles. Test that the current bundles didn't get broken by your changes. Edit osg-build : Remove the promotion routes from promoter.ini . Remove references in constants.py . Test your changes; also run the unit tests. Remove things from Koji: All targets referencing the series. All tags referencing the series. Remove references to the series from opensciencegrid/docker-osg-wn on GitHub. Move files in /p/vdt/public/html/release-info to its attic subdirectory. Undoing \u00b6 If we really need RPMs from a removed release series, we can look at the text files in /p/vdt/public/html/release-info/attic to determine the exact NVRs we need, and download them from Koji. Template Email \u00b6 Subject: OSG 3.X packages will be removed from the repositories YYYY-MM-DD On <DAYNAME, MONTH DAY>, the OSG will be removing the OSG <3.X> release series from our repositories. This includes both RPMs and tarballs hosted on repo.opensciencegrid.org. As a reminder, support for OSG <3.X> ended after <MONTH YEAR>. If your site is running OSG <3.X>, you should upgrade to the current release series, OSG 3.Y. See our upgrade documentation [1] for instructions. If you need assistance upgrading, please contact us at help@osg-htc.org. [1] https://osg-htc.org/docs/release/release_series/#updating-from-osg-31-32-33-to-34 If we're dropping support for a distro (e.g. EL 5 when we drop OSG 3.2), add the following after the first paragraph: Note that OSG <3.X> was the last release that supported Enterprise Linux <Z> distributions. If you believe that you still need support for this operating system series, please contact us at help@osg-htc.org. Since we're dropping support for i386 (32-bit) when we drop OSG 3.3, add the following after the first paragraph: Note that OSG 3.3 was the last release that contained 32-bit packages. If you believe that you still need support for this architecture, please contacts us at help@osg-htc.org.","title":"Release Series End-of-Life"},{"location":"release/release-eol/#release-series-end-of-life","text":"When a release reaches end-of-life, we need to discountinue a few items. Remove the retired series from the OSG VMU tests. However, retain the upgrade test from the retired series to the current series. Remove any github actions that build software-base or osg-wn-client Docker images for the retired series.","title":"Release Series End-of-Life"},{"location":"release/release-eol/#previous-release-series-removal-plan","text":"In order to reduce clutter and disk usage on our repositories and build system, we will remove older OSG Software release series. This will result in packages from those series becoming unavailable, so we will remove a release series when its packages are no longer needed. We will remove a release series no earlier than when the following series is completely out of support. For example, OSG 3.1 will be removed when OSG 3.2 is out of support, and OSG 3.2 will be removed when OSG 3.3 is out of support.","title":"Previous Release Series Removal Plan"},{"location":"release/release-eol/#tasks","text":"Removing a release series requires work from both Operations and Software & Release. The first step is to create a JIRA ticket in the SOFTWARE project to track the work. Second, Software & Release will enumerate the directories for Operations to remove. Operations tasks should be completed before Software & Release tasks.","title":"Tasks"},{"location":"release/release-eol/#operations","text":"These tasks should be completed in order. Two weeks in advance, notify sites (including mirror sites) that the release series is going away. See the template email below. Remove the series from the mash configs on the repo.opensciencegrid.org machines: Add the koji tags for the old series to the /usr/local/osg-tags.excluded file: # cd /usr/local # fgrep osg-3.1 osg-tags osg-3.1-el5-contrib osg-3.1-el5-development osg-3.1-el5-release osg-3.1-el5-testing osg-3.1-el6-contrib osg-3.1-el6-development osg-3.1-el6-release osg-3.1-el6-testing # fgrep osg-3.1 osg-tags >> osg-tags.exclude Re-run update_mashfiles.sh to update the mash config files: # ./update_mashfiles.sh Remove the appropriate repo directories from /usr/local/repo/osg . # rm -rf repo*/osg/3.1/ Reclaim space from any cached rpms in the mash cache which are no longer linked elsewhere: # find mash/cache/ -name \\* .rpm -type f -links 1 -delete Wait for mash to run and verify that the repos are no longer getting updated: Look at the mash logs in /var/log/repo . Verify that mash did not recreate the repo directory under /usr/local/repo/osg corresponding to the old release series. Remove tarballs from repo and OASIS","title":"Operations"},{"location":"release/release-eol/#software-release","text":"These tasks can be completed in any order. Tag and remove the SVN branch corresponding to the release series. Edit vm-test-runs and remove any \"long tail\" tests that reference the series. Edit tarball-client : Remove bundles from bundles.ini . Remove patch and other files that were used only by those bundles. Test that the current bundles didn't get broken by your changes. Edit osg-build : Remove the promotion routes from promoter.ini . Remove references in constants.py . Test your changes; also run the unit tests. Remove things from Koji: All targets referencing the series. All tags referencing the series. Remove references to the series from opensciencegrid/docker-osg-wn on GitHub. Move files in /p/vdt/public/html/release-info to its attic subdirectory.","title":"Software & Release"},{"location":"release/release-eol/#undoing","text":"If we really need RPMs from a removed release series, we can look at the text files in /p/vdt/public/html/release-info/attic to determine the exact NVRs we need, and download them from Koji.","title":"Undoing"},{"location":"release/release-eol/#template-email","text":"Subject: OSG 3.X packages will be removed from the repositories YYYY-MM-DD On <DAYNAME, MONTH DAY>, the OSG will be removing the OSG <3.X> release series from our repositories. This includes both RPMs and tarballs hosted on repo.opensciencegrid.org. As a reminder, support for OSG <3.X> ended after <MONTH YEAR>. If your site is running OSG <3.X>, you should upgrade to the current release series, OSG 3.Y. See our upgrade documentation [1] for instructions. If you need assistance upgrading, please contact us at help@osg-htc.org. [1] https://osg-htc.org/docs/release/release_series/#updating-from-osg-31-32-33-to-34 If we're dropping support for a distro (e.g. EL 5 when we drop OSG 3.2), add the following after the first paragraph: Note that OSG <3.X> was the last release that supported Enterprise Linux <Z> distributions. If you believe that you still need support for this operating system series, please contact us at help@osg-htc.org. Since we're dropping support for i386 (32-bit) when we drop OSG 3.3, add the following after the first paragraph: Note that OSG 3.3 was the last release that contained 32-bit packages. If you believe that you still need support for this architecture, please contacts us at help@osg-htc.org.","title":"Template Email"},{"location":"software/ce-test-scaling/","text":"How to Run Scalability Tests on a CE \u00b6 Introduction \u00b6 This document is intended as a general overview of the process for scalability testing of an OSG CE (Compute Element). All examples are for testing an HTCondor-CE , but they should be applicable for other CE software. The focus of testing a CE is on the number of concurrent running jobs the CE can sustain as well as the ramp-up rate when many jobs are queued. Sleeper Pool \u00b6 With the focus on the CE, actual job payloads can be minimal \u2013 simple long sleep jobs are fine. Thus, then can run on nearly any resources, and it is even possible to allow far more of these jobs to run on a single resource than would be sensible for real jobs. When large-scale testing a CE, one of the objectives is to see if the CE can fully utilize all resources (cores) available to it or if there are bottlenecks preventing that outcome. However to do this would normally require using up production slots, and it is hard to find a site willing to give up so many production slots for so long. Thus, running resourceless jobs in parallel with production jobs allows the testing to proceed without interfering with real work. Setting Up a Sleeper Pool \u00b6 A sleeper pool is created by \u201ctricking\u201d a worker node into thinking it has more cores than physically available. Then, the host is configured so that jobs marked for the sleeper pool are routed to the extra slots. In HTCondor, this is done by changing the START expression on each startd. For example, on a 32-core machine: START = ( \\ (SlotID >= 1) && \\ (SlotID < 33) && \\ (RequiresWholeMachine =!= TRUE ) && \\ (SleepSlot =!= TRUE) && \\ (distro =?= \"RHEL6\" ) && \\ (CPU_Only == TRUE ) \\ ) || \\ ( (SlotID >= 33) && (distro =?= \"RHEL6\" ) && (SleepSlot == TRUE) ) Usual Topology of the Tests \u00b6 A brief introduction to the topology involved in the tests. Batch System and Sleeper Pool \u00b6 This is normally the batch system of the resources which will be behind the CE to be tested. It is normally set up by a site administrator. CE \u00b6 This is the physical hardware where the CE software runs, hopefully mimicking real production hardware specifications. Submitter \u00b6 An HTCondor submit host. It can be a virtual machine for most test submissions. Monitoring tools \u00b6 To monitor tests, two software components are needed (which can be installed on the same node): ganglia-gmond and ganglia-gmetad. Once they are installed, then some ad-hoc metrics can be created to monitor the CE; for example: condor_q -pool red.unl.edu:9619 -name sleeper@red.unl.edu -const 'JobStatus=?=2' | wc -l gmetric --name RunningJobsCE Generating Load \u00b6 Location \u00b6 The load_generators are found in the OSgscal github repo . The binary of interest here is loadtest_condor Use \u00b6 Just untar it or check it out from mas on the HTCondor submit node (see above): git checkout https://github.com/efajardo/osgscal cd load_generators/loadtest_condor/trunk/bin Keep in mind that you also need a valid proxy for grid submissions. For example, if the goal is to keep 1,000 jobs in the queue and run 6-hour sleep jobs (on average), you can run this command: ./loadtest_condor.sh -type grid condor sleeper@red.unl.edu red.unl.edu:9619 -jobs 40000 -cluster 10 -proxy /home/submituser/.globus/cmspilot01.proxy -end random 21600 -maxidle 1000 -in sandbox 50","title":"CE Scale Testing"},{"location":"software/ce-test-scaling/#how-to-run-scalability-tests-on-a-ce","text":"","title":"How to Run Scalability Tests on a CE"},{"location":"software/ce-test-scaling/#introduction","text":"This document is intended as a general overview of the process for scalability testing of an OSG CE (Compute Element). All examples are for testing an HTCondor-CE , but they should be applicable for other CE software. The focus of testing a CE is on the number of concurrent running jobs the CE can sustain as well as the ramp-up rate when many jobs are queued.","title":"Introduction"},{"location":"software/ce-test-scaling/#sleeper-pool","text":"With the focus on the CE, actual job payloads can be minimal \u2013 simple long sleep jobs are fine. Thus, then can run on nearly any resources, and it is even possible to allow far more of these jobs to run on a single resource than would be sensible for real jobs. When large-scale testing a CE, one of the objectives is to see if the CE can fully utilize all resources (cores) available to it or if there are bottlenecks preventing that outcome. However to do this would normally require using up production slots, and it is hard to find a site willing to give up so many production slots for so long. Thus, running resourceless jobs in parallel with production jobs allows the testing to proceed without interfering with real work.","title":"Sleeper Pool"},{"location":"software/ce-test-scaling/#setting-up-a-sleeper-pool","text":"A sleeper pool is created by \u201ctricking\u201d a worker node into thinking it has more cores than physically available. Then, the host is configured so that jobs marked for the sleeper pool are routed to the extra slots. In HTCondor, this is done by changing the START expression on each startd. For example, on a 32-core machine: START = ( \\ (SlotID >= 1) && \\ (SlotID < 33) && \\ (RequiresWholeMachine =!= TRUE ) && \\ (SleepSlot =!= TRUE) && \\ (distro =?= \"RHEL6\" ) && \\ (CPU_Only == TRUE ) \\ ) || \\ ( (SlotID >= 33) && (distro =?= \"RHEL6\" ) && (SleepSlot == TRUE) )","title":"Setting Up a Sleeper Pool"},{"location":"software/ce-test-scaling/#usual-topology-of-the-tests","text":"A brief introduction to the topology involved in the tests.","title":"Usual Topology of the Tests"},{"location":"software/ce-test-scaling/#batch-system-and-sleeper-pool","text":"This is normally the batch system of the resources which will be behind the CE to be tested. It is normally set up by a site administrator.","title":"Batch System and Sleeper Pool"},{"location":"software/ce-test-scaling/#ce","text":"This is the physical hardware where the CE software runs, hopefully mimicking real production hardware specifications.","title":"CE"},{"location":"software/ce-test-scaling/#submitter","text":"An HTCondor submit host. It can be a virtual machine for most test submissions.","title":"Submitter"},{"location":"software/ce-test-scaling/#monitoring-tools","text":"To monitor tests, two software components are needed (which can be installed on the same node): ganglia-gmond and ganglia-gmetad. Once they are installed, then some ad-hoc metrics can be created to monitor the CE; for example: condor_q -pool red.unl.edu:9619 -name sleeper@red.unl.edu -const 'JobStatus=?=2' | wc -l gmetric --name RunningJobsCE","title":"Monitoring tools"},{"location":"software/ce-test-scaling/#generating-load","text":"","title":"Generating Load"},{"location":"software/ce-test-scaling/#location","text":"The load_generators are found in the OSgscal github repo . The binary of interest here is loadtest_condor","title":"Location"},{"location":"software/ce-test-scaling/#use","text":"Just untar it or check it out from mas on the HTCondor submit node (see above): git checkout https://github.com/efajardo/osgscal cd load_generators/loadtest_condor/trunk/bin Keep in mind that you also need a valid proxy for grid submissions. For example, if the goal is to keep 1,000 jobs in the queue and run 6-hour sleep jobs (on average), you can run this command: ./loadtest_condor.sh -type grid condor sleeper@red.unl.edu red.unl.edu:9619 -jobs 40000 -cluster 10 -proxy /home/submituser/.globus/cmspilot01.proxy -end random 21600 -maxidle 1000 -in sandbox 50","title":"Use"},{"location":"software/comanage-troubleshooting-guide/","text":"COManage Troubleshooting Guide \u00b6 A resource for COManage administrators to find solutions to commonly encountered problems. COManage Troubleshooting Items \u00b6 This section contains some of the issues you may encounter when interacting with the OSG COManage. Valid Tiger User is unauthorized with Dex credentials \u00b6 Under certain circumstances Dex may not be able to match a user to their COManage identity, possibly due to incorrect and/or missing organization identities/identifiers. Symptoms \u00b6 Tiger-Dex credentials missing some or all of a users group permissions. User unable to connect to the Tiger cluster. Error message from Tiger involving an unauthorized user. Example error message: kubectl get pods -n osg-dev Error from server (Forbidden): pods is forbidden: User \"user@email.edu\" cannot list resource \"pods\" in API group \"\" in the namespace \"osg-dev\"\" Empty groups in the Dex response after logging in with SSO Next actions \u00b6 Ensure that the user's LDAP record contains the attribute uid , which shares the same value as the COManage identifier used as a source for the LDAP provisioner target. LDAP attributes and their COManage sources can be found here Have the user log in Have the user fetch a new Dex token Explanation of SAML -> CILogon OIDC sub claim -> LDAP matching used in Dex. \u00b6 How the OAuth2 server does the following: Receives appropriate SAML attributes from the campus Identity provider. Uses those attributes to find the user in the CILogon user database, from which the CILogon OIDC sub claim is obtained. Performs an LDAP search using a filter of (uid=<CILogon OIDC sub claim value>) . Retrieves configured LDAP attributes from the record it has found, and sends those values out as claims with names as configured.","title":"COmanage Troubleshooting Guide"},{"location":"software/comanage-troubleshooting-guide/#comanage-troubleshooting-guide","text":"A resource for COManage administrators to find solutions to commonly encountered problems.","title":"COManage Troubleshooting Guide"},{"location":"software/comanage-troubleshooting-guide/#comanage-troubleshooting-items","text":"This section contains some of the issues you may encounter when interacting with the OSG COManage.","title":"COManage Troubleshooting Items"},{"location":"software/comanage-troubleshooting-guide/#valid-tiger-user-is-unauthorized-with-dex-credentials","text":"Under certain circumstances Dex may not be able to match a user to their COManage identity, possibly due to incorrect and/or missing organization identities/identifiers.","title":"Valid Tiger User is unauthorized with Dex credentials"},{"location":"software/comanage-troubleshooting-guide/#symptoms","text":"Tiger-Dex credentials missing some or all of a users group permissions. User unable to connect to the Tiger cluster. Error message from Tiger involving an unauthorized user. Example error message: kubectl get pods -n osg-dev Error from server (Forbidden): pods is forbidden: User \"user@email.edu\" cannot list resource \"pods\" in API group \"\" in the namespace \"osg-dev\"\" Empty groups in the Dex response after logging in with SSO","title":"Symptoms"},{"location":"software/comanage-troubleshooting-guide/#next-actions","text":"Ensure that the user's LDAP record contains the attribute uid , which shares the same value as the COManage identifier used as a source for the LDAP provisioner target. LDAP attributes and their COManage sources can be found here Have the user log in Have the user fetch a new Dex token","title":"Next actions"},{"location":"software/comanage-troubleshooting-guide/#explanation-of-saml-cilogon-oidc-sub-claim-ldap-matching-used-in-dex","text":"How the OAuth2 server does the following: Receives appropriate SAML attributes from the campus Identity provider. Uses those attributes to find the user in the CILogon user database, from which the CILogon OIDC sub claim is obtained. Performs an LDAP search using a filter of (uid=<CILogon OIDC sub claim value>) . Retrieves configured LDAP attributes from the record it has found, and sends those values out as claims with names as configured.","title":"Explanation of SAML -> CILogon OIDC sub claim -> LDAP matching used in Dex."},{"location":"software/container-development-guide/","text":"Container Development Guide \u00b6 This document contains instructions for OSG Technology Team members, including: How to to develop OSG Software container images that are automatically pushed to Docker Hub that adhere to our container release policy How to build a new version of an existing image How to manage tags for images in the OSG DockerHub organization Tips for container image development Creating New OSG Software Containers \u00b6 OSG Software service container images intended for OSG site admin use need to be automatically updated once per week to pick up any OS updates, as well as upon any changes to the images themselves. To do this, we use GitHub Actions to: Build new images on commits to master or main Update the docker-software-base on a schedule, which triggers builds for all image repos through repository dispatch Push container images to Docker Hub and the OSG Container Registry (Harbor) Code for new container images should now be stored in the GitHub repository opensciencegrid/images ; see below for instructions . The previous convention was to use individual GitHub repos for each image; these are described below . Add image code to the opensciencegrid/images repo \u00b6 The opensciencegrid/images repository is a central repository containing multiple container images based on the OSG Software Stack. The repository uses GitHub Actions CI to automatically build and push images, both on changes to individual images and upon updates to the upstream opensciencegrid/docker-software-base image. This repository is intended for images owned by OSG Staff with relatively simple CI needs: Images using OSG Yum repositories, especially those based on opensciencegrid/software-base Images that need tags based on the development , testing , and release tags for the supported OSG release series Images that push to Docker Hub and OSG Harbor Images that do not need CI tests See SOFTWARE-5013 for additional considerations. Creating new images from scratch \u00b6 Images are automatically built from the subdirectories of the opensciencegrid directory . A set of images will be built for each subdirectory, with each set containing multiple images based on OSG release series (e.g. 3.5 , 3.6 ) and release level (e.g. testing , release ). Fork and clone the https://github.com/opensciencegrid/images repo Create a subdirectory under opensciencegrid/ Create a README.md file describing the software provided by the image Create a LICENSE file containing the Apache 2.0 license text Create a Dockerfile building from the OSG Software Base image: ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release FROM opensciencegrid/software-base:$BASE_OSG_SERIES-<DISTRO VERSION>-$BASE_YUM_REPO # Previous instance has gone out of scope ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum install -y <PACKAGE(S)> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <DISTRO VERSION> with the Enterprise Linux version abbreviation (e.g., el7 , el8 ), and <PACKAGE(S)> with the RPM(s) you'd like to provide in this image. Hardcoding OSG series or release level If you do not want to build your image for all release series (for example, it's 3.6-only), or you do not want to build your image for all release levels (for example, always build from release), hardcode those instead of using the arguments, as in: ARG BASE_OSG_SERIES=3.6 FROM opensciencegrid/software-base:$BASE_OSG_SERIES-el8-release Adding an existing image from another repository \u00b6 If there is an existing source repository for an image that you would like to pull into the opensciencegrid/images central repository (e.g., images that make use of OSG Yum repositories), use the following instructions to retain history from the old repository. Install the git filter-repo plugin. For example, on an RPM-based operating system: yum install git-filter-repo Checkout opensciencegrid/images and your other source repository or make sure your local main branches are up-to-date cd to your other source repository and run the following: git filter-repo --to-subdirectory-filter opensciencegrid/<IMAGE NAME> cd to your local clone of the images repository and add your local repo as a remote using filesystem paths. For example: git remote add <IMAGE NAME> <PATH TO OTHER SOURCE REPO> In the images repo, create a branch based off of main for your work In the images repo, make sure your fork knows all the refs from the other source repo remote with the following: git fetch <IMAGE NAME> --tags While on your your new branch, do the merge. For example, if the main branch of your other source repository is main : git merge --allow-unrelated-histories <IMAGE NAME>/main Update the merged in Dockerfile to accept the BASE_OSG_SERIES and BASE_YUM_REPO arguments. Prepare the Docker Hub repository \u00b6 Ask the Software Manager to create a Docker Hub repo in the OSG organization. The name should generally match the subdirectory name under the images repo. Go to the permissions tab and give the robots and technology teams Read & Write access Old Image Repositories \u00b6 Some container images are stored in individual repositories under the opensciencegrid organization, with names prefixed with docker- and with the container repository topic. New images should not be created this way, but existing images may need to be updated or fixed; this section describes their layout and mechanics. Old image repos will have: A README.md file describing the software provided by the image A LICENSE file containing the Apache 2.0 license text A Dockerfile based off of the OSG Software Base image: FROM opensciencegrid/software-base:<OSG RELEASE SERIES>-<EL MAJOR VERSION>-release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum update -y && \\ yum clean all && \\ rm -rf /var/cache/yum/* RUN yum install -y <PACKAGE> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <PACKAGE> with the name of the RPM you'd like to provide in this container image, <OSG RELEASE SERIES> with the OSG release series version (e.g., 3.6 ), and <EL MAJOR VERSION> with the Enterprise Linux major version (e.g., 7 ). The BASE_OSG_SERIES and BASE_YUM_REPO arguments may or may not be used. The pre-defined Publish OSG Software container image workflow, found under the Actions tab. The user \"osg-bot\" needs to have the \"Write\" role for this repo in order to trigger automatic builds. Access to the following organizational secrets DOCKER_USERNAME DOCKER_PASSWORD OSG_HARBOR_ROBOT_USER OSG_HARBOR_ROBOT_PASSWORD The repo may also have access to the REPO_ACCESS_TOKEN organization secret, if it needs to send dispatches to another repository (e.g. docker-software-base ). A Docker Hub repository with a name matching the GitHub repo name, without the docker- prefix, with Read & Write access for the robots and technology teams. In addition, for repository dispatch from docker-software-base, they are listed in the GitHub Actions workflow for docker-software-base , in the dispatch-repo: list (under jobs: dispatch: strategy: matrix: ). Triggering Container Image Builds \u00b6 To build a new version of an existing container image , e.g. for a new RPM version of software in the container, you can kick off a new build in one of two ways: If there are no changes necessary to the container packaging: go to the GitHub repository's latest build under Actions, e.g. https://github.com/opensciencegrid/docker-frontier-squid/actions/ , and click \"Re-run jobs\" -> \"Re-run all jobs\". If changes need to be made to the container packaging: submit a pull request with your changes to the relevant GitHub repository and request that another team member review it. Once merged into master or main , a GitHub Actions build should start automatically. If the GitHub Actions build completes successfully, you should shortly see new fresh and timestamp tags appear in the DockerHub repository. Automatic weekly rebuilds If the repo's GitHub Actions are configured as above, container images will automatically rebuild, and therefore pick up new packages available in minefield once per week. Managing Tags in DockerHub \u00b6 Adding tags \u00b6 Images that have passed acceptance testing should be tagged as stable : Install the jq utility: yum install jq Get the sha256 repo digest of the image that the user has tested. All you need is the part that starts with sha256:... (aka the <DIGEST> ). A Kubernetes user can get the digest from the \"Image ID\" line obtained by running: kubectl describe pod <POD> A Docker user can get the digest by running: docker image inspect <IMAGE NAME>:<TAG> | jq '.[0].Id' (Optional) If you are tagging multiple images, you can enter your Docker Hub username and password into environment variables, to avoid having to re-type them. Otherwise the script will prompt for them. read user # enter dockerhub username read -s pass # enter dockerhub password export user pass Run the Docker container image tagging command from release-tools : ./dockerhub-tag-fresh-to-stable.sh <IMAGE NAME> <DIGEST> Removing tags \u00b6 Run the Docker container image pruning command from release-tools : ./dockerhub-prune-tags.py <IMAGE NAME> Making Slim Containers \u00b6 Here are some resources for creating slim, efficient containers: https://developers.redhat.com/blog/2016/03/09/more-about-docker-images-size/ https://github.com/opensciencegrid/topology/pull/399 https://docs.docker.com/develop/develop-images/multistage-build/","title":"Container Development Guide"},{"location":"software/container-development-guide/#container-development-guide","text":"This document contains instructions for OSG Technology Team members, including: How to to develop OSG Software container images that are automatically pushed to Docker Hub that adhere to our container release policy How to build a new version of an existing image How to manage tags for images in the OSG DockerHub organization Tips for container image development","title":"Container Development Guide"},{"location":"software/container-development-guide/#creating-new-osg-software-containers","text":"OSG Software service container images intended for OSG site admin use need to be automatically updated once per week to pick up any OS updates, as well as upon any changes to the images themselves. To do this, we use GitHub Actions to: Build new images on commits to master or main Update the docker-software-base on a schedule, which triggers builds for all image repos through repository dispatch Push container images to Docker Hub and the OSG Container Registry (Harbor) Code for new container images should now be stored in the GitHub repository opensciencegrid/images ; see below for instructions . The previous convention was to use individual GitHub repos for each image; these are described below .","title":"Creating New OSG Software Containers"},{"location":"software/container-development-guide/#add-image-code-to-the-opensciencegridimages-repo","text":"The opensciencegrid/images repository is a central repository containing multiple container images based on the OSG Software Stack. The repository uses GitHub Actions CI to automatically build and push images, both on changes to individual images and upon updates to the upstream opensciencegrid/docker-software-base image. This repository is intended for images owned by OSG Staff with relatively simple CI needs: Images using OSG Yum repositories, especially those based on opensciencegrid/software-base Images that need tags based on the development , testing , and release tags for the supported OSG release series Images that push to Docker Hub and OSG Harbor Images that do not need CI tests See SOFTWARE-5013 for additional considerations.","title":"Add image code to the opensciencegrid/images repo"},{"location":"software/container-development-guide/#creating-new-images-from-scratch","text":"Images are automatically built from the subdirectories of the opensciencegrid directory . A set of images will be built for each subdirectory, with each set containing multiple images based on OSG release series (e.g. 3.5 , 3.6 ) and release level (e.g. testing , release ). Fork and clone the https://github.com/opensciencegrid/images repo Create a subdirectory under opensciencegrid/ Create a README.md file describing the software provided by the image Create a LICENSE file containing the Apache 2.0 license text Create a Dockerfile building from the OSG Software Base image: ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release FROM opensciencegrid/software-base:$BASE_OSG_SERIES-<DISTRO VERSION>-$BASE_YUM_REPO # Previous instance has gone out of scope ARG BASE_OSG_SERIES=3.6 ARG BASE_YUM_REPO=release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum install -y <PACKAGE(S)> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <DISTRO VERSION> with the Enterprise Linux version abbreviation (e.g., el7 , el8 ), and <PACKAGE(S)> with the RPM(s) you'd like to provide in this image. Hardcoding OSG series or release level If you do not want to build your image for all release series (for example, it's 3.6-only), or you do not want to build your image for all release levels (for example, always build from release), hardcode those instead of using the arguments, as in: ARG BASE_OSG_SERIES=3.6 FROM opensciencegrid/software-base:$BASE_OSG_SERIES-el8-release","title":"Creating new images from scratch"},{"location":"software/container-development-guide/#adding-an-existing-image-from-another-repository","text":"If there is an existing source repository for an image that you would like to pull into the opensciencegrid/images central repository (e.g., images that make use of OSG Yum repositories), use the following instructions to retain history from the old repository. Install the git filter-repo plugin. For example, on an RPM-based operating system: yum install git-filter-repo Checkout opensciencegrid/images and your other source repository or make sure your local main branches are up-to-date cd to your other source repository and run the following: git filter-repo --to-subdirectory-filter opensciencegrid/<IMAGE NAME> cd to your local clone of the images repository and add your local repo as a remote using filesystem paths. For example: git remote add <IMAGE NAME> <PATH TO OTHER SOURCE REPO> In the images repo, create a branch based off of main for your work In the images repo, make sure your fork knows all the refs from the other source repo remote with the following: git fetch <IMAGE NAME> --tags While on your your new branch, do the merge. For example, if the main branch of your other source repository is main : git merge --allow-unrelated-histories <IMAGE NAME>/main Update the merged in Dockerfile to accept the BASE_OSG_SERIES and BASE_YUM_REPO arguments.","title":"Adding an existing image from another repository"},{"location":"software/container-development-guide/#prepare-the-docker-hub-repository","text":"Ask the Software Manager to create a Docker Hub repo in the OSG organization. The name should generally match the subdirectory name under the images repo. Go to the permissions tab and give the robots and technology teams Read & Write access","title":"Prepare the Docker Hub repository"},{"location":"software/container-development-guide/#old-image-repositories","text":"Some container images are stored in individual repositories under the opensciencegrid organization, with names prefixed with docker- and with the container repository topic. New images should not be created this way, but existing images may need to be updated or fixed; this section describes their layout and mechanics. Old image repos will have: A README.md file describing the software provided by the image A LICENSE file containing the Apache 2.0 license text A Dockerfile based off of the OSG Software Base image: FROM opensciencegrid/software-base:<OSG RELEASE SERIES>-<EL MAJOR VERSION>-release LABEL maintainer OSG Software <help@osg-htc.org> RUN yum update -y && \\ yum clean all && \\ rm -rf /var/cache/yum/* RUN yum install -y <PACKAGE> && \\ yum clean all && \\ rm -rf /var/cache/yum/* Replacing <PACKAGE> with the name of the RPM you'd like to provide in this container image, <OSG RELEASE SERIES> with the OSG release series version (e.g., 3.6 ), and <EL MAJOR VERSION> with the Enterprise Linux major version (e.g., 7 ). The BASE_OSG_SERIES and BASE_YUM_REPO arguments may or may not be used. The pre-defined Publish OSG Software container image workflow, found under the Actions tab. The user \"osg-bot\" needs to have the \"Write\" role for this repo in order to trigger automatic builds. Access to the following organizational secrets DOCKER_USERNAME DOCKER_PASSWORD OSG_HARBOR_ROBOT_USER OSG_HARBOR_ROBOT_PASSWORD The repo may also have access to the REPO_ACCESS_TOKEN organization secret, if it needs to send dispatches to another repository (e.g. docker-software-base ). A Docker Hub repository with a name matching the GitHub repo name, without the docker- prefix, with Read & Write access for the robots and technology teams. In addition, for repository dispatch from docker-software-base, they are listed in the GitHub Actions workflow for docker-software-base , in the dispatch-repo: list (under jobs: dispatch: strategy: matrix: ).","title":"Old Image Repositories"},{"location":"software/container-development-guide/#triggering-container-image-builds","text":"To build a new version of an existing container image , e.g. for a new RPM version of software in the container, you can kick off a new build in one of two ways: If there are no changes necessary to the container packaging: go to the GitHub repository's latest build under Actions, e.g. https://github.com/opensciencegrid/docker-frontier-squid/actions/ , and click \"Re-run jobs\" -> \"Re-run all jobs\". If changes need to be made to the container packaging: submit a pull request with your changes to the relevant GitHub repository and request that another team member review it. Once merged into master or main , a GitHub Actions build should start automatically. If the GitHub Actions build completes successfully, you should shortly see new fresh and timestamp tags appear in the DockerHub repository. Automatic weekly rebuilds If the repo's GitHub Actions are configured as above, container images will automatically rebuild, and therefore pick up new packages available in minefield once per week.","title":"Triggering Container Image Builds"},{"location":"software/container-development-guide/#managing-tags-in-dockerhub","text":"","title":"Managing Tags in DockerHub"},{"location":"software/container-development-guide/#adding-tags","text":"Images that have passed acceptance testing should be tagged as stable : Install the jq utility: yum install jq Get the sha256 repo digest of the image that the user has tested. All you need is the part that starts with sha256:... (aka the <DIGEST> ). A Kubernetes user can get the digest from the \"Image ID\" line obtained by running: kubectl describe pod <POD> A Docker user can get the digest by running: docker image inspect <IMAGE NAME>:<TAG> | jq '.[0].Id' (Optional) If you are tagging multiple images, you can enter your Docker Hub username and password into environment variables, to avoid having to re-type them. Otherwise the script will prompt for them. read user # enter dockerhub username read -s pass # enter dockerhub password export user pass Run the Docker container image tagging command from release-tools : ./dockerhub-tag-fresh-to-stable.sh <IMAGE NAME> <DIGEST>","title":"Adding tags"},{"location":"software/container-development-guide/#removing-tags","text":"Run the Docker container image pruning command from release-tools : ./dockerhub-prune-tags.py <IMAGE NAME>","title":"Removing tags"},{"location":"software/container-development-guide/#making-slim-containers","text":"Here are some resources for creating slim, efficient containers: https://developers.redhat.com/blog/2016/03/09/more-about-docker-images-size/ https://github.com/opensciencegrid/topology/pull/399 https://docs.docker.com/develop/develop-images/multistage-build/","title":"Making Slim Containers"},{"location":"software/create-vo-client/","text":"Creating the VO Client Package \u00b6 Overview \u00b6 This document will explain the step-by-step procedures for creating and releasing the VO Client Package. The VO Client Package sources can be found here: https://github.com/opensciencegrid/osg-vo-config When upstream changes have been made and are ready for a new VO Client Package release, these sources will be used to prepare a release tarball, which will in turn be used for the RPMs. In order to build the RPM, one needs: The tarball containing the: edg-mkgridmap.conf file gums.config.template file grid-vorolemap file (generated) voms-mapfile-default file (generated) vomses file vomsdir directory tree, containing the .lsc files. The RPM spec file, maintained in the OSG packaging area. JIRA Ticket for the Release \u00b6 There should be an associated JIRA ticket with a summary line of the form \"Release VO Package 85\". (Throughout this document, this release number will be referred to as <NN> .) The JIRA ticket should contain the details of the changes expected in the new VO Client Package release, which you should verify before proceeding. You can verify this with your favorite git tool (eg, git diff or gitk ), or just view the changes directly on GitHub: https://github.com/opensciencegrid/osg-vo-config/compare/release-84...master Here, release-84 is the previous release tag, which you are comparing to the latest changes in master . To use GitHub to view the comparison, you need to specify whatever is the most recent previous release tag. Alternatively, you can proceed to make the tarball , and compare the result to the previous vo-client tarball (from the upstream source cache) before publishing the new release . However you choose to do it, the point is to verify that the changes going into the release match what is expected in the JIRA ticket before publishing a new release. Updates to the GUMS Template \u00b6 Most commonly, VO Client Package releases do not involve changes to the gums.config.template file, though on occasion it needs to be updated. Before proceeding, any changes to gums.config.template related to this release should be committed to git and pushed to the upstream repo on GitHub. The procedure for updating gums.config.template is outside the scope of this document, but the main important point is that any updates to this file should be done with the GUMS web interface rather than editing its xml contents by hand. Making the Tarball \u00b6 The process to make a new tarball has been mostly scripted. To make the tarball: Start with a clean checkout of the latest master branch of the osg-vo-config source repo . This checked out commit should be the one intended to be tagged for the new release. - Run the mk-vo-client-tarball script with the new release number <NN> : $ ./bin/mk-vo-client-tarball <NN> For example: $ ./bin/mk-vo-client-tarball 85 This will create a file vo-client-<NN>-osg.tar.gz in the current directory. Once the tarball is created: If you have not already verified the changes expected in the JIRA ticket, compare the contents of the new tarball with the previous version in the upstream source cache . Upload the tarball into the upstream source cache , under the vo-client/<NN>/ directory. RPM Spec File Maintenance \u00b6 The OSG RPM spec file is maintained in Subversion . The VO Client package is located in native/redhat/trunk/vo-client ; that is, here . There are two files that need to be maintained: osg/vo-client.spec The Version: field should be updated to match the <NN> number for the release A %changelog entry should be added for the new release, mentioning any changes and their associated tickets upstream/release_tarball.source Update the relative path for the new tarball within the upstream source cache . Typically this will be vo-client/<NN>/vo-client-<NN>-osg.tar.gz . RPM Building \u00b6 After installing the osg-build tools , check out a clean copy of the vo-client packaging directory from svn, then: osg-build prebuild . Once there are no errors, run osg-build koji . --scratch . (This can be done without making any permanent change.) Once that builds successfully, run osg-build koji . (This is permanent, unlike when you ran with --scratch .) You cannot rebuild this version of the RPM again; to rebuild with changes, you must bump the release number and edit the changelog. This will push the RPMs into the OSG development repository. Note Koji requires additional setup compared to rpmbuild; see the documentation here . Publishing the New Release \u00b6 The final version of the sources in the osg-vo-config , which was used to create the tarball that was used in the koji build, needs be tagged in git with a release-<NN> tag (eg, release-85 ) and published as a release on GitHub. You can create and push the release-<NN> from your git checkout of osg-vo-config , OR create the tag while publishing the release on GitHub (recommended). To publish the new release on GitHub: Go to https://github.com/opensciencegrid/osg-vo-config/releases/new In the \"Tag version\" field, enter release-<NN> (eg, release-85 ) If you are creating this tag on GitHub, click the \"Target\" dropdown button, and under the \"Recent Commits\" tab, make sure to select the commit you used when creating the tarball (It should be the first one) In the \"Release title\" field, enter <MONTH> <YEAR> VO Package Release <NN> (eg, December 2018 VO Package Release 85 ) In the release description, list the changes in this release and their associated ticket numbers, similar to the new %changelog entry added in the rpm spec file (You can view the releases page for examples) - Click the \"Publish release\" button Promotion to Testing and Release: \u00b6 Read Release Policy . Note that the vo-client package frequently is part of a separate -data release; it does not necessarily have to wait for the main release cycle.","title":"Creating the VO Client Package"},{"location":"software/create-vo-client/#creating-the-vo-client-package","text":"","title":"Creating the VO Client Package"},{"location":"software/create-vo-client/#overview","text":"This document will explain the step-by-step procedures for creating and releasing the VO Client Package. The VO Client Package sources can be found here: https://github.com/opensciencegrid/osg-vo-config When upstream changes have been made and are ready for a new VO Client Package release, these sources will be used to prepare a release tarball, which will in turn be used for the RPMs. In order to build the RPM, one needs: The tarball containing the: edg-mkgridmap.conf file gums.config.template file grid-vorolemap file (generated) voms-mapfile-default file (generated) vomses file vomsdir directory tree, containing the .lsc files. The RPM spec file, maintained in the OSG packaging area.","title":"Overview"},{"location":"software/create-vo-client/#jira-ticket-for-the-release","text":"There should be an associated JIRA ticket with a summary line of the form \"Release VO Package 85\". (Throughout this document, this release number will be referred to as <NN> .) The JIRA ticket should contain the details of the changes expected in the new VO Client Package release, which you should verify before proceeding. You can verify this with your favorite git tool (eg, git diff or gitk ), or just view the changes directly on GitHub: https://github.com/opensciencegrid/osg-vo-config/compare/release-84...master Here, release-84 is the previous release tag, which you are comparing to the latest changes in master . To use GitHub to view the comparison, you need to specify whatever is the most recent previous release tag. Alternatively, you can proceed to make the tarball , and compare the result to the previous vo-client tarball (from the upstream source cache) before publishing the new release . However you choose to do it, the point is to verify that the changes going into the release match what is expected in the JIRA ticket before publishing a new release.","title":"JIRA Ticket for the Release"},{"location":"software/create-vo-client/#updates-to-the-gums-template","text":"Most commonly, VO Client Package releases do not involve changes to the gums.config.template file, though on occasion it needs to be updated. Before proceeding, any changes to gums.config.template related to this release should be committed to git and pushed to the upstream repo on GitHub. The procedure for updating gums.config.template is outside the scope of this document, but the main important point is that any updates to this file should be done with the GUMS web interface rather than editing its xml contents by hand.","title":"Updates to the GUMS Template"},{"location":"software/create-vo-client/#making-the-tarball","text":"The process to make a new tarball has been mostly scripted. To make the tarball: Start with a clean checkout of the latest master branch of the osg-vo-config source repo . This checked out commit should be the one intended to be tagged for the new release. - Run the mk-vo-client-tarball script with the new release number <NN> : $ ./bin/mk-vo-client-tarball <NN> For example: $ ./bin/mk-vo-client-tarball 85 This will create a file vo-client-<NN>-osg.tar.gz in the current directory. Once the tarball is created: If you have not already verified the changes expected in the JIRA ticket, compare the contents of the new tarball with the previous version in the upstream source cache . Upload the tarball into the upstream source cache , under the vo-client/<NN>/ directory.","title":"Making the Tarball"},{"location":"software/create-vo-client/#rpm-spec-file-maintenance","text":"The OSG RPM spec file is maintained in Subversion . The VO Client package is located in native/redhat/trunk/vo-client ; that is, here . There are two files that need to be maintained: osg/vo-client.spec The Version: field should be updated to match the <NN> number for the release A %changelog entry should be added for the new release, mentioning any changes and their associated tickets upstream/release_tarball.source Update the relative path for the new tarball within the upstream source cache . Typically this will be vo-client/<NN>/vo-client-<NN>-osg.tar.gz .","title":"RPM Spec File Maintenance"},{"location":"software/create-vo-client/#rpm-building","text":"After installing the osg-build tools , check out a clean copy of the vo-client packaging directory from svn, then: osg-build prebuild . Once there are no errors, run osg-build koji . --scratch . (This can be done without making any permanent change.) Once that builds successfully, run osg-build koji . (This is permanent, unlike when you ran with --scratch .) You cannot rebuild this version of the RPM again; to rebuild with changes, you must bump the release number and edit the changelog. This will push the RPMs into the OSG development repository. Note Koji requires additional setup compared to rpmbuild; see the documentation here .","title":"RPM Building"},{"location":"software/create-vo-client/#publishing-the-new-release","text":"The final version of the sources in the osg-vo-config , which was used to create the tarball that was used in the koji build, needs be tagged in git with a release-<NN> tag (eg, release-85 ) and published as a release on GitHub. You can create and push the release-<NN> from your git checkout of osg-vo-config , OR create the tag while publishing the release on GitHub (recommended). To publish the new release on GitHub: Go to https://github.com/opensciencegrid/osg-vo-config/releases/new In the \"Tag version\" field, enter release-<NN> (eg, release-85 ) If you are creating this tag on GitHub, click the \"Target\" dropdown button, and under the \"Recent Commits\" tab, make sure to select the commit you used when creating the tarball (It should be the first one) In the \"Release title\" field, enter <MONTH> <YEAR> VO Package Release <NN> (eg, December 2018 VO Package Release 85 ) In the release description, list the changes in this release and their associated ticket numbers, similar to the new %changelog entry added in the rpm spec file (You can view the releases page for examples) - Click the \"Publish release\" button","title":"Publishing the New Release"},{"location":"software/create-vo-client/#promotion-to-testing-and-release","text":"Read Release Policy . Note that the vo-client package frequently is part of a separate -data release; it does not necessarily have to wait for the main release cycle.","title":"Promotion to Testing and Release:"},{"location":"software/development-process/","text":"Software Development Process \u00b6 This page is for the OSG Software team and other contributors to the OSG software stack. It is meant to be the central source for all development processes for the Software team. (But right now, it is just a starting point.) Overall Development Cycle \u00b6 For a typical update to an existing package, the overall development cycle is roughly as follows: Download the new upstream source (tarball, source RPM, checkout) into the UW AFS upstream area In a checkout of our packaging code , update the reference to the upstream file and, as needed, the RPM spec file Use osg-build to perform a scratch build of the updated package Verify that the build succeeded; if not, redo previous steps until success Optionally, lightly test the new RPM(s); if there are problems, redo previous steps until success Use osg-build to perform an official build of the updated package (which will go into the development repos) Perform standard developer testing of the new RPM(s) \u2014 see below for details Obtain permission from the Software Manager to promote the package Promote the package to testing \u2014 see below for details Versioning Guidelines \u00b6 OSG-owned software should contain three digits, X.Y.Z, where X represents the major version, Y the minor version, and Z the maintenance version. New releases of software should increment one of the major, minor, or maintenance according to the following guidelines: Major: Major new software, typically (but not limited to) full rewrites, new architectures, major new features; can certainly break backward compatibility (but should provide a smooth upgrade path). Worthy of introduction into Upcoming. Minor: Notable changes to the software, including significant feature changes, API changes, etc.; may break compatibility, but must provide an upgrade path from other versions within the same Major series. Maintenance: Bug fixes, minor feature tweaks, etc.; must not break compatibility with other versions within the same Major.Minor series. If you are unsure about which version number to increment in a software update, consult the Software Manager. Build Procedures \u00b6 Building packages for multiple OSG release series \u00b6 The OSG Software team supports multiple release series, independent but in parallel to a large degree. In many cases, a single package is the same across release series, and therefore we want to build the package once and share it among the series. The procedure below suggests a way to accomplish this task. Current definitions: maintenance: OSG 3.4 ( trunk ) current: OSG 3.5 ( branches/osg-3.5 ) Procedure: Make changes to trunk Optionally, make and test a scratch build from trunk Commit the changes Make an official build from trunk (e.g.: osg-build koji <PACKAGE> ) Perform the standard 4 tests for the current series (see below) Merge the relevant commits from trunk into the maintenance branch (see below for tips) Optionally, make and test a scratch build from the maintenance branch Commit the merge Make an official build from the maintenance branch (e.g.: osg-build koji --repo=3.4 <PACKAGE> ) Perform the standard 4 tests for the maintenance series (see below) As needed (or directed by the Software manager), perform the cross-series tests (see below) Note Do not change the RPM Release number in the maintenance branch before rebuilding; the %dist tag will differ automatically, and hence the maintenance and current NVRs will not conflict. Merging changes from one release series to another \u00b6 These instructions assume that you are merging from trunk to branches/osg-3.5 . They also assume that the current directory you are in is a checkout of branches/osg-3.5 . I will use $pkg to refer to the name of your package. First, you will need the commit numbers for your changes: svn log \\^/native/redhat/trunk/$pkg | less Write down the commits you want to merge. If you only have one commit, merge that commit with -c as follows: svn merge -c $commit_num \\^/native/redhat/trunk/$pkg $pkg Where $commit_num is the SVN revision number of that commit (e.g. 17000). Merging an individual change like this is referred to as \"cherry-picking\". If you have a range of commits and you wish to merge all commits within that range, then do the following: svn merge -r $start_num:$end_num \\^/native/redhat/trunk/$pkg $pkg Where $start_num is the SVN revision of the commit BEFORE your first commit, and $end_num is the SVN revision of your last commit in that range. Note: Be very careful when merging a range from trunk into the maintenance branch so that you do not introduce more changes to the maintenance branch than are necessary. If you have multiple commits but they are not contiguous (i.e. there are commits made by you or someone else in that range that you do not want to merge), you will need to cherry-pick each individual commit. svn merge -c $commit1 \\^/native/redhat/trunk/$pkg $pkg svn merge -c $commit2 \\^/native/redhat/trunk/$pkg $pkg ... Where $commit1 , $commit2 are the commit numbers of the individual changes. Note that merge tracking in recent versions of SVN (1.5 or newer) should prevent commits from accidentally being merged multiple times. You should still look out for conflicts and examine the changes via svn diff before committing the merge. Testing Procedures \u00b6 Before promoting a package to a testing repository, each build must be tested lightly from the development repos to make sure that it is not completely broken, thereby wasting time during acceptance testing. Normally, the person who builds a package performs the development testing. If you are not doing your own development testing for a package , contact the Software Manager and/or leave a comment in the associated ticket; otherwise, your package may never be promoted to testing and hence never released. The \"Standard 4\" tests, defined \u00b6 In most cases, the Software manager will ask a developer to perform the \u201cstandard 4\u201d tests on an updated package in a release series before promotion. This is a shorthand description for a standard set of 4 test runs: Fresh install on el6 Fresh install on el7 Update install on el6 Update install on el7 An \u201cupdate install\u201d is a fresh install of the relevant package (or better yet, metapackage that includes it) from the production repository , followed by an update to the new build from the development repository . For each test run, the amount of functional testing required will vary. For very simple changes, it may be sufficient to verify that each installation succeeds and that the expected files are in place For some changes, it may be sufficient to run osg-test on the resulting installation For some changes, it will be necessary to perform careful functional tests of the affected component(s) If you have questions, check with the Software Manager to determine the amount of testing that is required per test run. The \"Cross-Series\" test, defined \u00b6 The cross-series test may need to be run for packages that have been built for multiple release series of the OSG software stack (i.e. 3.4 and 3.5): On el7, install from the 3.4 repositories, then update from the 3.5 repositories Viewed another way, this test is similar to the update installs, above, except from 3.4-release to 3.5-development. The \"Long Tail\" tests, defined \u00b6 These tests may need to be run when updating a package that's also in the old, unsupported (3.3) branch. They will consist of: Install from 3.3-release and update to 3.5-development (on el7 only) The \"full set of tests\", defined \u00b6 All of the tests mentioned above. Running the tests in VM Universe \u00b6 In the case that the package you're testing is covered by osg-tested-internal, you can run the full set of tests in a manual VM universe test run. Make sure you meet the pre-requisites required to submit VM Universe jobs on osghost.chtc.wisc.edu . After that's done, prepare the test suite with a comment describing the test run. For example, if you were testing a new htcondor-ce package: osg-run-tests 'Testing htcondor-ce-3.2.1-1' After you cd into the directory specified in the output of the previous command, you will need to edit the *.yaml files in parameters.d to reflect the tests that you will want to run, i.e. clean installs, upgrade installs and upgrade installs between OSG versions. Once you're satisfied with your list of parameters, submit the dag: condor_submit_dag master-run.dag Promoting a Package to Testing \u00b6 Once development and development testing is complete, the final OSG Software step is to promote the package(s) to our testing repositories. After that, the Release team takes over with acceptance testing and ultimately release. Of course if they discover problems, the ticket(s) will be returned to OSG Software for further development, essentially restarting the development cycle. Preparing a Good Promotion Request \u00b6 Developers must obtain permission from the OSG Software manager to promote a package from development to testing. A promotion request goes into at least one affected JIRA ticket and will be answered there as well. Below are some tips for writing a good promotion request: Make sure that relevant information about goals, history, and resolution is in the associated ticket(s) Include globs for the NVRs to be promoted (or a detailed list, if it is that complicated, which it almost never is) If you ran automated tests: Link to the results page(s) Verify that relevant tests ran successfully (as opposed to being skipped or failing) \u2013 briefly summarize your findings Note whether the automated tests are just regression tests or actually test the current change(s) If there are any failures, explain why they are not important to the promotion request If you ran manual tests: Summarize your tests and findings If there were failures, explain why they are not important to the promotion request If there are critical build dependencies that we typically check, include reports from the built-against-pkgs tool Note: This step is really just for known, specific cases, like the {HTCondor, BLAHP} set Occasionally, the OSG Software manager will request the tool to be run for other cases If other packages depend on the to-be-promoted package, explain whether the dependent packages must be rebuilt or, if not, why not For example (hypothetical promotion request for HTCondor-CE): May I promote htcondor-ce-2.3.4-2.osg3*.el* ? I ran a complete set of automated tests <LINK THE PRECEDING TEXT OR SEPARATELY HERE>; the HTCondor-CE tests ran and passed in all cases. There were some spurious failures of RSV in the All condition for RHEL 6, but this is a known failure case that is independent of HTCondor-CE. I also did a few spot checks manually (one VM each for SL 6 and SL 7), and in each case setting use_frobnosticator = true in the configuration resulted in the expected behavior as defined in the description field above. The built-against-pkgs tool shows that I built against all the latest HTCondor and BLAHP builds, see below. <JIRA-formatted table comes after> Promoting \u00b6 Follow these steps to request promotion, promote a package, and note the promotion in JIRA: Make sure the package update has at least one associated JIRA ticket; if there is no ticket, at least create one for releasing the package(s) Obtain permission to promote the package(s) from the Software Manager (see above) Use osg-promote to promote the package(s) from development to testing Comment on the associated JIRA ticket(s) with osg-promote's JIRA-formatted output (or at least the build NVRs) and, if you know, suggestions for acceptance testing Update the JIRA ticket description with a bulleted list describing changes in the promoted version(s) compared to the currently released version(s) Mark each associated JIRA ticket as \u201cReady For Testing\u201d","title":"Development Process"},{"location":"software/development-process/#software-development-process","text":"This page is for the OSG Software team and other contributors to the OSG software stack. It is meant to be the central source for all development processes for the Software team. (But right now, it is just a starting point.)","title":"Software Development Process"},{"location":"software/development-process/#overall-development-cycle","text":"For a typical update to an existing package, the overall development cycle is roughly as follows: Download the new upstream source (tarball, source RPM, checkout) into the UW AFS upstream area In a checkout of our packaging code , update the reference to the upstream file and, as needed, the RPM spec file Use osg-build to perform a scratch build of the updated package Verify that the build succeeded; if not, redo previous steps until success Optionally, lightly test the new RPM(s); if there are problems, redo previous steps until success Use osg-build to perform an official build of the updated package (which will go into the development repos) Perform standard developer testing of the new RPM(s) \u2014 see below for details Obtain permission from the Software Manager to promote the package Promote the package to testing \u2014 see below for details","title":"Overall Development Cycle"},{"location":"software/development-process/#versioning-guidelines","text":"OSG-owned software should contain three digits, X.Y.Z, where X represents the major version, Y the minor version, and Z the maintenance version. New releases of software should increment one of the major, minor, or maintenance according to the following guidelines: Major: Major new software, typically (but not limited to) full rewrites, new architectures, major new features; can certainly break backward compatibility (but should provide a smooth upgrade path). Worthy of introduction into Upcoming. Minor: Notable changes to the software, including significant feature changes, API changes, etc.; may break compatibility, but must provide an upgrade path from other versions within the same Major series. Maintenance: Bug fixes, minor feature tweaks, etc.; must not break compatibility with other versions within the same Major.Minor series. If you are unsure about which version number to increment in a software update, consult the Software Manager.","title":"Versioning Guidelines"},{"location":"software/development-process/#build-procedures","text":"","title":"Build Procedures"},{"location":"software/development-process/#building-packages-for-multiple-osg-release-series","text":"The OSG Software team supports multiple release series, independent but in parallel to a large degree. In many cases, a single package is the same across release series, and therefore we want to build the package once and share it among the series. The procedure below suggests a way to accomplish this task. Current definitions: maintenance: OSG 3.4 ( trunk ) current: OSG 3.5 ( branches/osg-3.5 ) Procedure: Make changes to trunk Optionally, make and test a scratch build from trunk Commit the changes Make an official build from trunk (e.g.: osg-build koji <PACKAGE> ) Perform the standard 4 tests for the current series (see below) Merge the relevant commits from trunk into the maintenance branch (see below for tips) Optionally, make and test a scratch build from the maintenance branch Commit the merge Make an official build from the maintenance branch (e.g.: osg-build koji --repo=3.4 <PACKAGE> ) Perform the standard 4 tests for the maintenance series (see below) As needed (or directed by the Software manager), perform the cross-series tests (see below) Note Do not change the RPM Release number in the maintenance branch before rebuilding; the %dist tag will differ automatically, and hence the maintenance and current NVRs will not conflict.","title":"Building packages for multiple OSG release series"},{"location":"software/development-process/#merging-changes-from-one-release-series-to-another","text":"These instructions assume that you are merging from trunk to branches/osg-3.5 . They also assume that the current directory you are in is a checkout of branches/osg-3.5 . I will use $pkg to refer to the name of your package. First, you will need the commit numbers for your changes: svn log \\^/native/redhat/trunk/$pkg | less Write down the commits you want to merge. If you only have one commit, merge that commit with -c as follows: svn merge -c $commit_num \\^/native/redhat/trunk/$pkg $pkg Where $commit_num is the SVN revision number of that commit (e.g. 17000). Merging an individual change like this is referred to as \"cherry-picking\". If you have a range of commits and you wish to merge all commits within that range, then do the following: svn merge -r $start_num:$end_num \\^/native/redhat/trunk/$pkg $pkg Where $start_num is the SVN revision of the commit BEFORE your first commit, and $end_num is the SVN revision of your last commit in that range. Note: Be very careful when merging a range from trunk into the maintenance branch so that you do not introduce more changes to the maintenance branch than are necessary. If you have multiple commits but they are not contiguous (i.e. there are commits made by you or someone else in that range that you do not want to merge), you will need to cherry-pick each individual commit. svn merge -c $commit1 \\^/native/redhat/trunk/$pkg $pkg svn merge -c $commit2 \\^/native/redhat/trunk/$pkg $pkg ... Where $commit1 , $commit2 are the commit numbers of the individual changes. Note that merge tracking in recent versions of SVN (1.5 or newer) should prevent commits from accidentally being merged multiple times. You should still look out for conflicts and examine the changes via svn diff before committing the merge.","title":"Merging changes from one release series to another"},{"location":"software/development-process/#testing-procedures","text":"Before promoting a package to a testing repository, each build must be tested lightly from the development repos to make sure that it is not completely broken, thereby wasting time during acceptance testing. Normally, the person who builds a package performs the development testing. If you are not doing your own development testing for a package , contact the Software Manager and/or leave a comment in the associated ticket; otherwise, your package may never be promoted to testing and hence never released.","title":"Testing Procedures"},{"location":"software/development-process/#the-standard-4-tests-defined","text":"In most cases, the Software manager will ask a developer to perform the \u201cstandard 4\u201d tests on an updated package in a release series before promotion. This is a shorthand description for a standard set of 4 test runs: Fresh install on el6 Fresh install on el7 Update install on el6 Update install on el7 An \u201cupdate install\u201d is a fresh install of the relevant package (or better yet, metapackage that includes it) from the production repository , followed by an update to the new build from the development repository . For each test run, the amount of functional testing required will vary. For very simple changes, it may be sufficient to verify that each installation succeeds and that the expected files are in place For some changes, it may be sufficient to run osg-test on the resulting installation For some changes, it will be necessary to perform careful functional tests of the affected component(s) If you have questions, check with the Software Manager to determine the amount of testing that is required per test run.","title":"The \"Standard 4\" tests, defined"},{"location":"software/development-process/#the-cross-series-test-defined","text":"The cross-series test may need to be run for packages that have been built for multiple release series of the OSG software stack (i.e. 3.4 and 3.5): On el7, install from the 3.4 repositories, then update from the 3.5 repositories Viewed another way, this test is similar to the update installs, above, except from 3.4-release to 3.5-development.","title":"The \"Cross-Series\" test, defined"},{"location":"software/development-process/#the-long-tail-tests-defined","text":"These tests may need to be run when updating a package that's also in the old, unsupported (3.3) branch. They will consist of: Install from 3.3-release and update to 3.5-development (on el7 only)","title":"The \"Long Tail\" tests, defined"},{"location":"software/development-process/#the-full-set-of-tests-defined","text":"All of the tests mentioned above.","title":"The \"full set of tests\", defined"},{"location":"software/development-process/#running-the-tests-in-vm-universe","text":"In the case that the package you're testing is covered by osg-tested-internal, you can run the full set of tests in a manual VM universe test run. Make sure you meet the pre-requisites required to submit VM Universe jobs on osghost.chtc.wisc.edu . After that's done, prepare the test suite with a comment describing the test run. For example, if you were testing a new htcondor-ce package: osg-run-tests 'Testing htcondor-ce-3.2.1-1' After you cd into the directory specified in the output of the previous command, you will need to edit the *.yaml files in parameters.d to reflect the tests that you will want to run, i.e. clean installs, upgrade installs and upgrade installs between OSG versions. Once you're satisfied with your list of parameters, submit the dag: condor_submit_dag master-run.dag","title":"Running the tests in VM Universe"},{"location":"software/development-process/#promoting-a-package-to-testing","text":"Once development and development testing is complete, the final OSG Software step is to promote the package(s) to our testing repositories. After that, the Release team takes over with acceptance testing and ultimately release. Of course if they discover problems, the ticket(s) will be returned to OSG Software for further development, essentially restarting the development cycle.","title":"Promoting a Package to Testing"},{"location":"software/development-process/#preparing-a-good-promotion-request","text":"Developers must obtain permission from the OSG Software manager to promote a package from development to testing. A promotion request goes into at least one affected JIRA ticket and will be answered there as well. Below are some tips for writing a good promotion request: Make sure that relevant information about goals, history, and resolution is in the associated ticket(s) Include globs for the NVRs to be promoted (or a detailed list, if it is that complicated, which it almost never is) If you ran automated tests: Link to the results page(s) Verify that relevant tests ran successfully (as opposed to being skipped or failing) \u2013 briefly summarize your findings Note whether the automated tests are just regression tests or actually test the current change(s) If there are any failures, explain why they are not important to the promotion request If you ran manual tests: Summarize your tests and findings If there were failures, explain why they are not important to the promotion request If there are critical build dependencies that we typically check, include reports from the built-against-pkgs tool Note: This step is really just for known, specific cases, like the {HTCondor, BLAHP} set Occasionally, the OSG Software manager will request the tool to be run for other cases If other packages depend on the to-be-promoted package, explain whether the dependent packages must be rebuilt or, if not, why not For example (hypothetical promotion request for HTCondor-CE): May I promote htcondor-ce-2.3.4-2.osg3*.el* ? I ran a complete set of automated tests <LINK THE PRECEDING TEXT OR SEPARATELY HERE>; the HTCondor-CE tests ran and passed in all cases. There were some spurious failures of RSV in the All condition for RHEL 6, but this is a known failure case that is independent of HTCondor-CE. I also did a few spot checks manually (one VM each for SL 6 and SL 7), and in each case setting use_frobnosticator = true in the configuration resulted in the expected behavior as defined in the description field above. The built-against-pkgs tool shows that I built against all the latest HTCondor and BLAHP builds, see below. <JIRA-formatted table comes after>","title":"Preparing a Good Promotion Request"},{"location":"software/development-process/#promoting","text":"Follow these steps to request promotion, promote a package, and note the promotion in JIRA: Make sure the package update has at least one associated JIRA ticket; if there is no ticket, at least create one for releasing the package(s) Obtain permission to promote the package(s) from the Software Manager (see above) Use osg-promote to promote the package(s) from development to testing Comment on the associated JIRA ticket(s) with osg-promote's JIRA-formatted output (or at least the build NVRs) and, if you know, suggestions for acceptance testing Update the JIRA ticket description with a bulleted list describing changes in the promoted version(s) compared to the currently released version(s) Mark each associated JIRA ticket as \u201cReady For Testing\u201d","title":"Promoting"},{"location":"software/effort-tracking/","text":"Effort Tracking \u00b6 This page describes a simple plan for tracking effort in the OSG Technology teams. Basic Ideas \u00b6 At its simplest, we would like to understand how much effort is spent on various OSG Technology activities over time. The focus is on having reasonably accurate, unbiased data. We might use the data later, for example, to hone future OSG proposals. And of course, all federal funding is subject to effort tracking. There are just a few simple ideas to keep in mind: Each week, report your effort on OSG Technology activities Update your numbers in the effort tracking google spreadsheet (ask BrianL for access) and include a section in your weekly status report; here is an example: EFFORT External development: 63% Support: 12% Leave: 20% Outside: 5 Follow standard federal regulations for calculating effort (e.g., OMB Circular A-21) The main idea is that all of your job-related activity for a week equals 100%, whether that is exactly 40 hours of work, a little less (subject to your local institution\u2019s rules), or more. This implies that the same hours worked could result in different effort percentages reported from week to week; for example, 4 hours in a 40-hour week is 10%, but 4 hours in a 50-hour week (which I hope is exceedingly rare) is 8%. Report 100% of your effort each week, but note that all effort outside of the Technology area falls into a single category. Unless you work at UW\u2013Madison, we do not need to know any details about your effort outside of the Technology area. (BrianL will talk to UW\u2013Madison folks about local expectations.) If you are assigned to the Technology area for less than 100%, please report your actual Technology effort accurately. Workloads vary from week to week. For example, suppose you are 50% Technology in general, but you actually work 24 hours in a 40-hour week; you should report 60% effort for that week. The goal is to present reality, not what you think management wants to see. Effort is reported as integer percentages, no less accurate than 5% intervals So please do not report percentages like 43.21% and please do not round to the nearest 10%. Effort Categories \u00b6 Here are the categories in which to track effort: Investigations Work on the Investigations team External Software work that (generally) benefits our users; e.g., creating packages; updating existing ones; designing, coding, and testing new tools, existing tools, patches, or our software components Internal Software work on tools that we use to get work done; e.g., working on osg-test (for now), osg-build, Koji maintenance, the UW or UC ITB instances Documentation Work on our TWiki or Markdown documentation Release Release team activities, primarily acceptance testing and cutting releases Support User support, including working on GOC tickets, direct support emails, some JIRA tickets that are more support than development, etc. It might be tricky to decide when support work becomes development work; generally, once a support ticket turns into a JIRA ticket and goes through the normal development lifecycle, then the JIRA-based work is development. If there is still extensive communication with GOC ticket users, that is still support. Management This is mainly for team leads; e.g., managing team activities and tickets (generally); hiring; leading (not just attending) meetings Education Not for general learning or training activities The OSG Education area is essentially part of the Software area, because many technology-area members contribute to the OSG School. So this category is for OSG School effort (or other sanctioned OSG Education activities. Admin General administrative activities that benefit the OSG Technology area but that do not fit elsewhere \u2014 use sparingly!! Outside For all activities outside of the OSG Technology area (Madison team members should provide extra details, see BrianL) Leave This is for holidays, vacation, and sick leave; count a full day of leave as 8.0 hours, count a half day as 4.0 hours A few thoughts about tricky situations: Meetings. If a meeting is specific to one of the categories above, use that category. If the meeting is more general (e.g., the weekly Monday meeting, or the OSG AHM), amortize your time according to your usual breakdown by category. For example, someone who spends nearly all of their time working on development tasks should count the Monday meeting as development time. Administrative activities. This is probably the trickiest category. It certainly covers any administrative work that pertains to your activity in the OSG Technology area. But what about administrative activities that pertain to your employment in general, and not to any particular activity? In that case, and that case only, you should amortize the administrative activity between Admin and Outside according to either (a) your appointment percentages between OSG Technology and non-Technology activities, or (b) your actual percentages between OSG Technology and non-Technology activities. Outside (non-Technology) activities that benefit the OSG Technology area. The simplest approach is to amortize the time. The more correct approach is to figure out where credit will be given for the work; if the OSG Annual Report will describe the work in one of the Technology sections, then it should be a Technology category; otherwise not. Learning activities. Put short amounts of learning time in their relevant development category. For instance, if Igor is showing Edgar how to use GlideTester, that goes into Internal . But for longer training events, or for events that are less obviously related to day-to-day activities, mark the time as Admin , and maybe add a comment explaining the activity. Ultimately, if you are not sure how to deal with a situation, ask BrianL and he will make something up and document it here (generically) for future reference.","title":"Effort Tracking"},{"location":"software/effort-tracking/#effort-tracking","text":"This page describes a simple plan for tracking effort in the OSG Technology teams.","title":"Effort Tracking"},{"location":"software/effort-tracking/#basic-ideas","text":"At its simplest, we would like to understand how much effort is spent on various OSG Technology activities over time. The focus is on having reasonably accurate, unbiased data. We might use the data later, for example, to hone future OSG proposals. And of course, all federal funding is subject to effort tracking. There are just a few simple ideas to keep in mind: Each week, report your effort on OSG Technology activities Update your numbers in the effort tracking google spreadsheet (ask BrianL for access) and include a section in your weekly status report; here is an example: EFFORT External development: 63% Support: 12% Leave: 20% Outside: 5 Follow standard federal regulations for calculating effort (e.g., OMB Circular A-21) The main idea is that all of your job-related activity for a week equals 100%, whether that is exactly 40 hours of work, a little less (subject to your local institution\u2019s rules), or more. This implies that the same hours worked could result in different effort percentages reported from week to week; for example, 4 hours in a 40-hour week is 10%, but 4 hours in a 50-hour week (which I hope is exceedingly rare) is 8%. Report 100% of your effort each week, but note that all effort outside of the Technology area falls into a single category. Unless you work at UW\u2013Madison, we do not need to know any details about your effort outside of the Technology area. (BrianL will talk to UW\u2013Madison folks about local expectations.) If you are assigned to the Technology area for less than 100%, please report your actual Technology effort accurately. Workloads vary from week to week. For example, suppose you are 50% Technology in general, but you actually work 24 hours in a 40-hour week; you should report 60% effort for that week. The goal is to present reality, not what you think management wants to see. Effort is reported as integer percentages, no less accurate than 5% intervals So please do not report percentages like 43.21% and please do not round to the nearest 10%.","title":"Basic Ideas"},{"location":"software/effort-tracking/#effort-categories","text":"Here are the categories in which to track effort: Investigations Work on the Investigations team External Software work that (generally) benefits our users; e.g., creating packages; updating existing ones; designing, coding, and testing new tools, existing tools, patches, or our software components Internal Software work on tools that we use to get work done; e.g., working on osg-test (for now), osg-build, Koji maintenance, the UW or UC ITB instances Documentation Work on our TWiki or Markdown documentation Release Release team activities, primarily acceptance testing and cutting releases Support User support, including working on GOC tickets, direct support emails, some JIRA tickets that are more support than development, etc. It might be tricky to decide when support work becomes development work; generally, once a support ticket turns into a JIRA ticket and goes through the normal development lifecycle, then the JIRA-based work is development. If there is still extensive communication with GOC ticket users, that is still support. Management This is mainly for team leads; e.g., managing team activities and tickets (generally); hiring; leading (not just attending) meetings Education Not for general learning or training activities The OSG Education area is essentially part of the Software area, because many technology-area members contribute to the OSG School. So this category is for OSG School effort (or other sanctioned OSG Education activities. Admin General administrative activities that benefit the OSG Technology area but that do not fit elsewhere \u2014 use sparingly!! Outside For all activities outside of the OSG Technology area (Madison team members should provide extra details, see BrianL) Leave This is for holidays, vacation, and sick leave; count a full day of leave as 8.0 hours, count a half day as 4.0 hours A few thoughts about tricky situations: Meetings. If a meeting is specific to one of the categories above, use that category. If the meeting is more general (e.g., the weekly Monday meeting, or the OSG AHM), amortize your time according to your usual breakdown by category. For example, someone who spends nearly all of their time working on development tasks should count the Monday meeting as development time. Administrative activities. This is probably the trickiest category. It certainly covers any administrative work that pertains to your activity in the OSG Technology area. But what about administrative activities that pertain to your employment in general, and not to any particular activity? In that case, and that case only, you should amortize the administrative activity between Admin and Outside according to either (a) your appointment percentages between OSG Technology and non-Technology activities, or (b) your actual percentages between OSG Technology and non-Technology activities. Outside (non-Technology) activities that benefit the OSG Technology area. The simplest approach is to amortize the time. The more correct approach is to figure out where credit will be given for the work; if the OSG Annual Report will describe the work in one of the Technology sections, then it should be a Technology category; otherwise not. Learning activities. Put short amounts of learning time in their relevant development category. For instance, if Igor is showing Edgar how to use GlideTester, that goes into Internal . But for longer training events, or for events that are less obviously related to day-to-day activities, mark the time as Admin , and maybe add a comment explaining the activity. Ultimately, if you are not sure how to deal with a situation, ask BrianL and he will make something up and document it here (generically) for future reference.","title":"Effort Categories"},{"location":"software/git-software-development/","text":"Git software development workflow \u00b6 This document describes the development workflow for OSG software packages kept in GitHub. It is intended for people who wish to contribute to OSG software. Git and GitHub basics \u00b6 If you are unfamiliar with Git and GitHub, the GitHub website has a good series of tutorials at https://docs.github.com/en/get-started Getting shell access to GitHub \u00b6 There are multiple ways of authenticating to GitHub from the shell. This section will cover using SSH keys. This is no longer the method recommended by GitHub, but is easier to set up for someone with existing SSH experience. The instructions here are derived from GitHub's own instructions on using SSH keys . Creating a new SSH key (optional but recommended) \u00b6 If you already have an SSH keypair in your ~/.ssh directory that you want to use for GitHub, you may skip this step. It is more secure, however, to create a new keypair specifically for use with GitHub. The instructions below will create an SSH public/private key pair with the private key stored in ~/.ssh/id_github and public key stored in ~/.ssh/id_github.pub . Generating the key \u00b6 Use ssh-keygen to generate the SSH keypair. For <EMAIL_ADDRESS> , use the email address associated with your GitHub account. [user@client ~ ] $ ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_github -C <EMAIL_ADDRESS> Configuring SSH to use the key for GitHub \u00b6 Make sure SSH uses the new key by default to access GitHub. Create or edit ~/.ssh/config and append the following lines: Host github.com IdentityFile <YOUR_HOME_DIR>/.ssh/id_github Where is the output of the command: echo $HOME Adding the SSH public key to GitHub \u00b6 Using the GitHub web interface: On the upper right of the screen, click on your profile picture In the menu that pops up, click \"Settings\" On the left-hand sidebar, click \"SSH and GPG keys\" In the top right of the \"SSH keys\" box, click \"New SSH key\" In the \"Title\" field of the dialog that pops up, enter a descriptive name for the key Open the public key file (e.g. ~/.ssh/id_github.pub (don't forget the .pub )) in a text editor and copy its full contents to the clipboard In the \"Key\" field, paste the public key Below the \"Key\" field, click \"Add SSH key\" You should see your new key in the \"SSH keys\" list. Testing that shell access works \u00b6 To verify you can authenticate to GitHub using SSH, SSH to git@github.com . You should see a message that 'you've successfully authenticated, but GitHub does not provide shell access.' Contribution workflow \u00b6 We use the standard GitHub pull request workflow for making contributions to OSG software. If you've never contributed to this project on GitHub before, do the following steps first: Using the GitHub web interface, fork the repo you wish to contribute to. Make a clone of your forked repo on your local machine. [user@client ~ ] $ git clone git@github.com:<USERNAME/PROJECT> Where <USERNAME> is your github username and <PROJECT> is the name of the project you want to contribute to, e.g. in order to clone my local fork of the openscience/technology repository: [user@client ~ ] $ git clone https://github.com/ddavila0/technology.git Note If you get a \"Permission denied\" error, your public key may not be set up with GitHub -- please see the \"Getting shell access to GitHub\" section above. If you get some other error, the GitHub page on SSH may contain useful information on troubleshooting. Once you have your local repo, do the following: Create a branch to hold changes that are related to the issue you are working on. Give the <BRANCH> a name that will remind you of its purpose, including any relevant ticket numbers, such as SOFTWARE-2345.pathchange : [user@client ~ ] $ git checkout -b <BRANCH> Make your commits to this branch, then push the branch to your repo on GitHub. [user@client ~ ] $ git push origin <BRANCH> Select your branch in the GitHub web interface, then create a \"pull request\" against the original repo. Add a good description of your change into the message for the pull request. Enter a Jira ticket number in the message to automatically link the pull request to the Jira ticket. Request a review from the drop down menu on the right and wait for your pull request to be reviewed by a software team member. If the team member accepts your changes, they will merge your pull request, and your changes will be incorporated upstream. You may then delete the branch you created your pull request from. If your changes are rejected, then you may make additional changes to the branch that your pull request is for. Once you push the changes from your local repo to your GitHub repo, they will automatically be added to the pull request. Release workflow \u00b6 This section is intended for OSG Software team members or the primary developers of a software project (i.e. those that make releases). Some of the steps require direct write access the GitHub repo for the project owned by opensciencegrid . (If you can approve pull requests, you have write access). A release of a software is created from your local clone of a software project. Before you release, you need to make sure your local clone is in sync with the GitHub repo owned by opensciencegrid (the OSG repo): If you haven't already, add the OSG repo as a \"remote\" to your repo: [user@client ~ ] $ git remote add upstream git@github.com:opensciencegrid/<PROJECT> Where <PROJECT> is the name of the project you are going to release, e.g. for openscience/technology repository it would be technology.git Fetch changes from the OSG repo: [user@client ~ ] $ git fetch upstream Compare your branch you are releasing from (probably master ) to its copy in the OSG repo: [user@client ~ ] $ git checkout master ; git diff upstream/master There should be no differences. Once this is done, release the software as you usually do. This process varies from one project to another, but often it involves running make upstream or similar. Check your project's README file for instructions. Test your software. Tag the commit that you made the release from. Git release tags are conventionally called VERSION , where VERSION is the version of the software you are releasing. So if you're releasing version 1.3.0, you would create the <TAG> v1.3.0 . Note Once a tag has been pushed to the OSG repo, it should not be changed. Be sure the commit you want to tag is the final one you made the release from. Create the tag in your local repo: [user@client ~ ] $ git tag <TAG> Push the tag to your own GitHub repo: [user@client ~ ] $ git push origin <TAG> Push the tag to the OSG repo: [user@client ~ ] $ git push upstream <TAG> Best practices \u00b6 Making good pull requests (The Art of Good Commits) \u00b6 In addition to writing good code, it's important to organize your changes to make the task of reviewing them easier, both for the reviewer of the pull request, and even for yourself later. Here are some general guidelines and tips. Put logically separate changes into separate commits \u00b6 This becomes more relevant if there are a lot of changes in the pull request. Having a single commit with many different changes happening at the same time can make the changes harder to review. If possible, split up logically separate changes into separate commits. As a simple example, if you are renaming a variable in many places, and also refactoring the structure of some code, these changes can be split into two separate commits. This will make it easier when reviewing to see clearly what each commit is trying to accomplish. The process you went through to arrive at your final code may have been different, but you can clean up your commits after the fact. One method is to use git rebase -i to combine (squash) several commits into one, and then use git gui to amend the combined commit, staging the parts that represent each logical change into separate commits. Another example that occasionally comes up is when you want to copy or move a file AND make changes to that file. If you have a single commit that introduces a file to a new location with changes , it will not be obvious from the commit diff itself which parts are the same (moved or copied in) and which parts you are modifying. Instead, by putting the copy or move of the original file into its own commit, and then putting your changes in a separate commit, it will make it clear to the reviewer which parts are changing from the original. Avoid whitespace noise \u00b6 There are a few considerations to note when it comes to whitespace. Avoid adding spaces at the end of lines. These are generally considered \"noise\" that will get cleaned up later (sometimes automatically, depending on editor settings). It's not necessary to \"fix\" this kind of whitespace noise everywhere you happen to find it in existing files, but it's fine to remove trailing whitespace for lines that you are already modifying for your own changes. Do not strip the final newline at the end-of-file. Some text editors will automatically strip the final newline at the end of file, but this is a form of whitespace noise similar to trailing spaces. If that is the case for your editor, please configure it not to strip the newline at EOF. (GitHub will show the diff for files with a missing newline at EOF with a red circle-minus symbol with the mouseover text \"No newline at end of file\".) Avoid mixing tabs and spaces. With the exception of Makefiles and Go source code, indentation should be done with regular spaces, not tabs. Please configure your text editor accordingly. Mixing tabs and spaces in indentation is problematic because different editor settings can make tab stops appear at different widths. As with trailing whitespace, it's fine to convert stray tabs to spaces on lines you are modifying, but it is not necessary to fix them everywhere, if that is not the purpose of your pull request. Put large whitespace changes into a separate commit. If you do want to change a significant amount of whitespace (either converting tabs to spaces on many lines, or perhaps adjusting the amount of indentation, or wrapping text at a different width), make your whitespace-only changes as a separate commit. This will make it clear that, although many lines may be changing, there is no functional change for that particular commit. Then any functional changes to the text in a following commit will be easier to review. Don't commit large files \u00b6 Try to keep the repository small by not committing files that are too large. Avoid committing large binaries or data sets. Ask yourself if they need to be in the repository before committing. If, somehow, a large file has been committed and pushed, it's not enough to remove the file in another commit. The file must be removed from all of the history or else the repository will still contain the large file as Git keeps track of deleted files. This can be done using the git rebase -i and git filter-repo commands. If a large file must be added to the repository. Use (Git LFS)[https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage] Verify that only the files intended are modified in each commit \u00b6 Sometimes you may have several files modified at once, but you only intend to commit a subset of the changes. In such cases you should be aware that git commit -a will include all the modified files in your commit. Likewise, if you have some untracked files in your working copy, that you do not intend to commit, be aware that git add . will introduce these as new files in the commit. Note If you do use the -a option for git commit , you may want to consider using the -v option along with it (i.e. git commit -av ), which will show you the diff to be committed in your editor while you are typing your commit message. After making a commit locally, you can verify that only the files you intended to modify were included in the commit by running git show --stat . Or to review the actual changes to those files, git show (without --stat ). If you find unintended files included in the commit, you can amend the commit so that it does not include changes to file-not-to-commit like so: [user@client ~ ] $ git reset HEAD^ file-not-to-commit [user@client ~ ] $ git commit --amend If you have multiple commits ready for a pull request, you can review the high-level changes for each commit with git log --stat origin/master.. (or origin/main.. , whichever is the name of the main origin branch). Tools like git gui also provide a way to review commits. If you find unintended files included in earlier commits, you can do a git rebase -i origin/master and edit the commits in question, which will give you a chance to amend a particular commit as shown above. Squash noisy work-in-progress commits \u00b6 Naturally in the trial-and-error-prone process of development, there will be many changes along the way that didn't make the final cut. This is good and healthy, and it's perfectly reasonable to be making many small work-in-progress commits locally while you are developing. However, for the reviewer, the relevant thing is what final changes are being introduced into the codebase. Having to review several ideas that were put into and then taken out of the changeset is a distraction, and makes it harder to see what the end result is for the new changes. If you have such work-in-progress commits, first combine them (this is also called \"squashing\" or \"rebasing\"), and then break them up into logically distinct commits as necessary, representing the final changeset. As mentioned above, one way to do this is with a combination of git rebase -i and git gui , though there are other third-party tools (e.g., magit) available also. Write a succinct subject to explain what each commit does \u00b6 The first line of a commit message is the \"subject\" (or sometimes also called the \"title\"). It should be short and sweet (at most 72 characters) and briefly state what the commit is designed to do. As a convention, the subject of the commit message should be written in the imperative - that is, it should be written as if it were a command. For instance, a subject should start with \"fix a bug\" rather than \"fixing\" or \"fixes\". Explain why a change was made in the commit message \u00b6 It is generally important also to explain why a change was made. If this is not covered by the succinct subject line of your commit, you should explain the rationale behind your change in the commit message body. (The commit message starts with the subject line, then is optionally followed by a blank line plus the message body.) You can also explain in the commit message body how this commit accomplishes the stated purpose in the subject - and you may find yourself needing to do this if there are some tricky details in the changes. But even if it is perfectly clear from the code and your commit message what you are changing and how you are going about it, it is not always clear why the change is needed or desired - so it is important to explain your reasons, in order to make this clear to the reviewer. For an example of \"explaining your reasons\", see this commit message body . Summarize your commits in the pull request title \u00b6 The title of a pull request is analogous to the subject of a commit. If you have only one commit in your pull request, GitHub will by default set the pull request title and body to match that commit's subject and body; and that default is acceptable for single-commit pull requests. But if you have multiple commits in your pull request, you should try to capture the overall goal of these commits in your pull request title. In the pull request body, you can also mention or discuss the high-level changes from each commit, and if relevant discuss how these changes work together for the overall goal of the pull request. Choose a separate, descriptive branch name for each pull request \u00b6 GitHub allows creating pull requests entirely on their web interface, and will automatically suggest a generic branch name like patch-42 . But this is boring and not especially helpful to the reviewer or to the one submitting the pull request. Instead, choose a short name for the branch that describes the topic of the changes or the feature being introduced. For instance, fix-memory-leak or scitokens-support . (As will be discussed more later, it is best to prefix the branch name with a ticket reference as well.) Note that each pull request should get its own branch name, even if two pull requests are for the same ticket and the topic is similar. New commits pushed to a branch for a pull request will automatically show up as part of that pull request; so a second pull request needs a separate branch to track the separate set of changes. Reference any relevant tickets \u00b6 Code changes often are related to a Jira ticket, for instance SOFTWARE-1234. By referencing the name of a ticket in your pull request, it provides a convenient way to look into the background context for the change; and later on down the road, it makes it easy to find which changes were made for a particular task, referenced by the ticket name. Ideally, you can include a ticket reference each of these three places: Your branch name. For example, name the branch in your fork of the GitHub repo for the pull request SOFTWARE-1234.fix-memory-leak . Your commit messages. For example, the subject of your commit message might read, fix a memory leak (SOFTWARE-1234) . If you have trouble squeezing the ticket name into the subject line, or if you have a number of related tickets that you want to reference, it is also OK to mention them later in the commit message body. The pull request title. If your pull request is just a single commit, and you have the ticket reference in the subject line of the commit message, GitHub will include this in the pull request title automatically. But if you have multiple commits, or you have only included the ticket reference in the body of the commit message, or more generally if you want to tweak the title of the pull request, you should in any case make a point to include the ticket name in the title of the pull request. (By convention, we include this at the end of the title, in parentheses.) If there is no ticket associated with your changes, consider creating one (or asking an OSG software team member to create one) before submitting your pull request. Further reading \u00b6 There are a number of articles and guides for making good git commits and good pull requests - a simple search will turn up plenty of material for the interested reader. See online guides such as this one for more details. Brownie points \u00b6 You will get brownie points from Carl, personally, if you strive to make your code (and other text files) fit within an 80-column terminal window. Reviewing pull requests \u00b6 There are a couple items to note about the review process for GitHub pull requests. Batch comments in a formal review \u00b6 When reviewing a pull request, GitHub allows you to comment on lines and presents the option to \"Add single comment\" or \"Start a review\". A single comment added will not be tied to your review, and a separate email notification will be sent for every time you click \"Add single comment\". Especially for reviewing larger pull requests, we generally prefer to \"Start a review\", and then \"Add review comment\" for subsequent comments. This will tie all of your comments and suggestions together as part of your review. When you complete your review, you will have the opportunity to make summary comments about the changes, when you select Approve/Comment/Request changes. By \"batching\" all of your review comments this way, a single email notification will be sent for your review, which contains all of your review comments together. Batch commits when accepting suggestions from a review \u00b6 When someone reviews your pull request, they may make suggestions that tweak your changes. Similar to review comments, suggestions from a review can either be applied one at a time (Commit suggestion), or they can be batched and applied together. To batch suggestions, first you need to open the \"Files changed\" tab; then for each suggestion you want to accept, click \"Add suggestion to batch\". Finally, click \"Commit suggestions\" to apply all batched suggestions as a single commit. Generally we prefer to batch related changes or miscellaneous tweaks rather than applying each one individually. But if there are a number of suggestions of a different nature, it is OK to group them such that you apply one batch for each set of related suggestions (consistent with the guideline to put logically separate changes into separate commits).","title":"Git Software Development Process"},{"location":"software/git-software-development/#git-software-development-workflow","text":"This document describes the development workflow for OSG software packages kept in GitHub. It is intended for people who wish to contribute to OSG software.","title":"Git software development workflow"},{"location":"software/git-software-development/#git-and-github-basics","text":"If you are unfamiliar with Git and GitHub, the GitHub website has a good series of tutorials at https://docs.github.com/en/get-started","title":"Git and GitHub basics"},{"location":"software/git-software-development/#getting-shell-access-to-github","text":"There are multiple ways of authenticating to GitHub from the shell. This section will cover using SSH keys. This is no longer the method recommended by GitHub, but is easier to set up for someone with existing SSH experience. The instructions here are derived from GitHub's own instructions on using SSH keys .","title":"Getting shell access to GitHub"},{"location":"software/git-software-development/#creating-a-new-ssh-key-optional-but-recommended","text":"If you already have an SSH keypair in your ~/.ssh directory that you want to use for GitHub, you may skip this step. It is more secure, however, to create a new keypair specifically for use with GitHub. The instructions below will create an SSH public/private key pair with the private key stored in ~/.ssh/id_github and public key stored in ~/.ssh/id_github.pub .","title":"Creating a new SSH key (optional but recommended)"},{"location":"software/git-software-development/#generating-the-key","text":"Use ssh-keygen to generate the SSH keypair. For <EMAIL_ADDRESS> , use the email address associated with your GitHub account. [user@client ~ ] $ ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_github -C <EMAIL_ADDRESS>","title":"Generating the key"},{"location":"software/git-software-development/#configuring-ssh-to-use-the-key-for-github","text":"Make sure SSH uses the new key by default to access GitHub. Create or edit ~/.ssh/config and append the following lines: Host github.com IdentityFile <YOUR_HOME_DIR>/.ssh/id_github Where is the output of the command: echo $HOME","title":"Configuring SSH to use the key for GitHub"},{"location":"software/git-software-development/#adding-the-ssh-public-key-to-github","text":"Using the GitHub web interface: On the upper right of the screen, click on your profile picture In the menu that pops up, click \"Settings\" On the left-hand sidebar, click \"SSH and GPG keys\" In the top right of the \"SSH keys\" box, click \"New SSH key\" In the \"Title\" field of the dialog that pops up, enter a descriptive name for the key Open the public key file (e.g. ~/.ssh/id_github.pub (don't forget the .pub )) in a text editor and copy its full contents to the clipboard In the \"Key\" field, paste the public key Below the \"Key\" field, click \"Add SSH key\" You should see your new key in the \"SSH keys\" list.","title":"Adding the SSH public key to GitHub"},{"location":"software/git-software-development/#testing-that-shell-access-works","text":"To verify you can authenticate to GitHub using SSH, SSH to git@github.com . You should see a message that 'you've successfully authenticated, but GitHub does not provide shell access.'","title":"Testing that shell access works"},{"location":"software/git-software-development/#contribution-workflow","text":"We use the standard GitHub pull request workflow for making contributions to OSG software. If you've never contributed to this project on GitHub before, do the following steps first: Using the GitHub web interface, fork the repo you wish to contribute to. Make a clone of your forked repo on your local machine. [user@client ~ ] $ git clone git@github.com:<USERNAME/PROJECT> Where <USERNAME> is your github username and <PROJECT> is the name of the project you want to contribute to, e.g. in order to clone my local fork of the openscience/technology repository: [user@client ~ ] $ git clone https://github.com/ddavila0/technology.git Note If you get a \"Permission denied\" error, your public key may not be set up with GitHub -- please see the \"Getting shell access to GitHub\" section above. If you get some other error, the GitHub page on SSH may contain useful information on troubleshooting. Once you have your local repo, do the following: Create a branch to hold changes that are related to the issue you are working on. Give the <BRANCH> a name that will remind you of its purpose, including any relevant ticket numbers, such as SOFTWARE-2345.pathchange : [user@client ~ ] $ git checkout -b <BRANCH> Make your commits to this branch, then push the branch to your repo on GitHub. [user@client ~ ] $ git push origin <BRANCH> Select your branch in the GitHub web interface, then create a \"pull request\" against the original repo. Add a good description of your change into the message for the pull request. Enter a Jira ticket number in the message to automatically link the pull request to the Jira ticket. Request a review from the drop down menu on the right and wait for your pull request to be reviewed by a software team member. If the team member accepts your changes, they will merge your pull request, and your changes will be incorporated upstream. You may then delete the branch you created your pull request from. If your changes are rejected, then you may make additional changes to the branch that your pull request is for. Once you push the changes from your local repo to your GitHub repo, they will automatically be added to the pull request.","title":"Contribution workflow"},{"location":"software/git-software-development/#release-workflow","text":"This section is intended for OSG Software team members or the primary developers of a software project (i.e. those that make releases). Some of the steps require direct write access the GitHub repo for the project owned by opensciencegrid . (If you can approve pull requests, you have write access). A release of a software is created from your local clone of a software project. Before you release, you need to make sure your local clone is in sync with the GitHub repo owned by opensciencegrid (the OSG repo): If you haven't already, add the OSG repo as a \"remote\" to your repo: [user@client ~ ] $ git remote add upstream git@github.com:opensciencegrid/<PROJECT> Where <PROJECT> is the name of the project you are going to release, e.g. for openscience/technology repository it would be technology.git Fetch changes from the OSG repo: [user@client ~ ] $ git fetch upstream Compare your branch you are releasing from (probably master ) to its copy in the OSG repo: [user@client ~ ] $ git checkout master ; git diff upstream/master There should be no differences. Once this is done, release the software as you usually do. This process varies from one project to another, but often it involves running make upstream or similar. Check your project's README file for instructions. Test your software. Tag the commit that you made the release from. Git release tags are conventionally called VERSION , where VERSION is the version of the software you are releasing. So if you're releasing version 1.3.0, you would create the <TAG> v1.3.0 . Note Once a tag has been pushed to the OSG repo, it should not be changed. Be sure the commit you want to tag is the final one you made the release from. Create the tag in your local repo: [user@client ~ ] $ git tag <TAG> Push the tag to your own GitHub repo: [user@client ~ ] $ git push origin <TAG> Push the tag to the OSG repo: [user@client ~ ] $ git push upstream <TAG>","title":"Release workflow"},{"location":"software/git-software-development/#best-practices","text":"","title":"Best practices"},{"location":"software/git-software-development/#making-good-pull-requests-the-art-of-good-commits","text":"In addition to writing good code, it's important to organize your changes to make the task of reviewing them easier, both for the reviewer of the pull request, and even for yourself later. Here are some general guidelines and tips.","title":"Making good pull requests (The Art of Good Commits)"},{"location":"software/git-software-development/#put-logically-separate-changes-into-separate-commits","text":"This becomes more relevant if there are a lot of changes in the pull request. Having a single commit with many different changes happening at the same time can make the changes harder to review. If possible, split up logically separate changes into separate commits. As a simple example, if you are renaming a variable in many places, and also refactoring the structure of some code, these changes can be split into two separate commits. This will make it easier when reviewing to see clearly what each commit is trying to accomplish. The process you went through to arrive at your final code may have been different, but you can clean up your commits after the fact. One method is to use git rebase -i to combine (squash) several commits into one, and then use git gui to amend the combined commit, staging the parts that represent each logical change into separate commits. Another example that occasionally comes up is when you want to copy or move a file AND make changes to that file. If you have a single commit that introduces a file to a new location with changes , it will not be obvious from the commit diff itself which parts are the same (moved or copied in) and which parts you are modifying. Instead, by putting the copy or move of the original file into its own commit, and then putting your changes in a separate commit, it will make it clear to the reviewer which parts are changing from the original.","title":"Put logically separate changes into separate commits"},{"location":"software/git-software-development/#avoid-whitespace-noise","text":"There are a few considerations to note when it comes to whitespace. Avoid adding spaces at the end of lines. These are generally considered \"noise\" that will get cleaned up later (sometimes automatically, depending on editor settings). It's not necessary to \"fix\" this kind of whitespace noise everywhere you happen to find it in existing files, but it's fine to remove trailing whitespace for lines that you are already modifying for your own changes. Do not strip the final newline at the end-of-file. Some text editors will automatically strip the final newline at the end of file, but this is a form of whitespace noise similar to trailing spaces. If that is the case for your editor, please configure it not to strip the newline at EOF. (GitHub will show the diff for files with a missing newline at EOF with a red circle-minus symbol with the mouseover text \"No newline at end of file\".) Avoid mixing tabs and spaces. With the exception of Makefiles and Go source code, indentation should be done with regular spaces, not tabs. Please configure your text editor accordingly. Mixing tabs and spaces in indentation is problematic because different editor settings can make tab stops appear at different widths. As with trailing whitespace, it's fine to convert stray tabs to spaces on lines you are modifying, but it is not necessary to fix them everywhere, if that is not the purpose of your pull request. Put large whitespace changes into a separate commit. If you do want to change a significant amount of whitespace (either converting tabs to spaces on many lines, or perhaps adjusting the amount of indentation, or wrapping text at a different width), make your whitespace-only changes as a separate commit. This will make it clear that, although many lines may be changing, there is no functional change for that particular commit. Then any functional changes to the text in a following commit will be easier to review.","title":"Avoid whitespace noise"},{"location":"software/git-software-development/#dont-commit-large-files","text":"Try to keep the repository small by not committing files that are too large. Avoid committing large binaries or data sets. Ask yourself if they need to be in the repository before committing. If, somehow, a large file has been committed and pushed, it's not enough to remove the file in another commit. The file must be removed from all of the history or else the repository will still contain the large file as Git keeps track of deleted files. This can be done using the git rebase -i and git filter-repo commands. If a large file must be added to the repository. Use (Git LFS)[https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage]","title":"Don't commit large files"},{"location":"software/git-software-development/#verify-that-only-the-files-intended-are-modified-in-each-commit","text":"Sometimes you may have several files modified at once, but you only intend to commit a subset of the changes. In such cases you should be aware that git commit -a will include all the modified files in your commit. Likewise, if you have some untracked files in your working copy, that you do not intend to commit, be aware that git add . will introduce these as new files in the commit. Note If you do use the -a option for git commit , you may want to consider using the -v option along with it (i.e. git commit -av ), which will show you the diff to be committed in your editor while you are typing your commit message. After making a commit locally, you can verify that only the files you intended to modify were included in the commit by running git show --stat . Or to review the actual changes to those files, git show (without --stat ). If you find unintended files included in the commit, you can amend the commit so that it does not include changes to file-not-to-commit like so: [user@client ~ ] $ git reset HEAD^ file-not-to-commit [user@client ~ ] $ git commit --amend If you have multiple commits ready for a pull request, you can review the high-level changes for each commit with git log --stat origin/master.. (or origin/main.. , whichever is the name of the main origin branch). Tools like git gui also provide a way to review commits. If you find unintended files included in earlier commits, you can do a git rebase -i origin/master and edit the commits in question, which will give you a chance to amend a particular commit as shown above.","title":"Verify that only the files intended are modified in each commit"},{"location":"software/git-software-development/#squash-noisy-work-in-progress-commits","text":"Naturally in the trial-and-error-prone process of development, there will be many changes along the way that didn't make the final cut. This is good and healthy, and it's perfectly reasonable to be making many small work-in-progress commits locally while you are developing. However, for the reviewer, the relevant thing is what final changes are being introduced into the codebase. Having to review several ideas that were put into and then taken out of the changeset is a distraction, and makes it harder to see what the end result is for the new changes. If you have such work-in-progress commits, first combine them (this is also called \"squashing\" or \"rebasing\"), and then break them up into logically distinct commits as necessary, representing the final changeset. As mentioned above, one way to do this is with a combination of git rebase -i and git gui , though there are other third-party tools (e.g., magit) available also.","title":"Squash noisy work-in-progress commits"},{"location":"software/git-software-development/#write-a-succinct-subject-to-explain-what-each-commit-does","text":"The first line of a commit message is the \"subject\" (or sometimes also called the \"title\"). It should be short and sweet (at most 72 characters) and briefly state what the commit is designed to do. As a convention, the subject of the commit message should be written in the imperative - that is, it should be written as if it were a command. For instance, a subject should start with \"fix a bug\" rather than \"fixing\" or \"fixes\".","title":"Write a succinct subject to explain what each commit does"},{"location":"software/git-software-development/#explain-why-a-change-was-made-in-the-commit-message","text":"It is generally important also to explain why a change was made. If this is not covered by the succinct subject line of your commit, you should explain the rationale behind your change in the commit message body. (The commit message starts with the subject line, then is optionally followed by a blank line plus the message body.) You can also explain in the commit message body how this commit accomplishes the stated purpose in the subject - and you may find yourself needing to do this if there are some tricky details in the changes. But even if it is perfectly clear from the code and your commit message what you are changing and how you are going about it, it is not always clear why the change is needed or desired - so it is important to explain your reasons, in order to make this clear to the reviewer. For an example of \"explaining your reasons\", see this commit message body .","title":"Explain why a change was made in the commit message"},{"location":"software/git-software-development/#summarize-your-commits-in-the-pull-request-title","text":"The title of a pull request is analogous to the subject of a commit. If you have only one commit in your pull request, GitHub will by default set the pull request title and body to match that commit's subject and body; and that default is acceptable for single-commit pull requests. But if you have multiple commits in your pull request, you should try to capture the overall goal of these commits in your pull request title. In the pull request body, you can also mention or discuss the high-level changes from each commit, and if relevant discuss how these changes work together for the overall goal of the pull request.","title":"Summarize your commits in the pull request title"},{"location":"software/git-software-development/#choose-a-separate-descriptive-branch-name-for-each-pull-request","text":"GitHub allows creating pull requests entirely on their web interface, and will automatically suggest a generic branch name like patch-42 . But this is boring and not especially helpful to the reviewer or to the one submitting the pull request. Instead, choose a short name for the branch that describes the topic of the changes or the feature being introduced. For instance, fix-memory-leak or scitokens-support . (As will be discussed more later, it is best to prefix the branch name with a ticket reference as well.) Note that each pull request should get its own branch name, even if two pull requests are for the same ticket and the topic is similar. New commits pushed to a branch for a pull request will automatically show up as part of that pull request; so a second pull request needs a separate branch to track the separate set of changes.","title":"Choose a separate, descriptive branch name for each pull request"},{"location":"software/git-software-development/#reference-any-relevant-tickets","text":"Code changes often are related to a Jira ticket, for instance SOFTWARE-1234. By referencing the name of a ticket in your pull request, it provides a convenient way to look into the background context for the change; and later on down the road, it makes it easy to find which changes were made for a particular task, referenced by the ticket name. Ideally, you can include a ticket reference each of these three places: Your branch name. For example, name the branch in your fork of the GitHub repo for the pull request SOFTWARE-1234.fix-memory-leak . Your commit messages. For example, the subject of your commit message might read, fix a memory leak (SOFTWARE-1234) . If you have trouble squeezing the ticket name into the subject line, or if you have a number of related tickets that you want to reference, it is also OK to mention them later in the commit message body. The pull request title. If your pull request is just a single commit, and you have the ticket reference in the subject line of the commit message, GitHub will include this in the pull request title automatically. But if you have multiple commits, or you have only included the ticket reference in the body of the commit message, or more generally if you want to tweak the title of the pull request, you should in any case make a point to include the ticket name in the title of the pull request. (By convention, we include this at the end of the title, in parentheses.) If there is no ticket associated with your changes, consider creating one (or asking an OSG software team member to create one) before submitting your pull request.","title":"Reference any relevant tickets"},{"location":"software/git-software-development/#further-reading","text":"There are a number of articles and guides for making good git commits and good pull requests - a simple search will turn up plenty of material for the interested reader. See online guides such as this one for more details.","title":"Further reading"},{"location":"software/git-software-development/#brownie-points","text":"You will get brownie points from Carl, personally, if you strive to make your code (and other text files) fit within an 80-column terminal window.","title":"Brownie points"},{"location":"software/git-software-development/#reviewing-pull-requests","text":"There are a couple items to note about the review process for GitHub pull requests.","title":"Reviewing pull requests"},{"location":"software/git-software-development/#batch-comments-in-a-formal-review","text":"When reviewing a pull request, GitHub allows you to comment on lines and presents the option to \"Add single comment\" or \"Start a review\". A single comment added will not be tied to your review, and a separate email notification will be sent for every time you click \"Add single comment\". Especially for reviewing larger pull requests, we generally prefer to \"Start a review\", and then \"Add review comment\" for subsequent comments. This will tie all of your comments and suggestions together as part of your review. When you complete your review, you will have the opportunity to make summary comments about the changes, when you select Approve/Comment/Request changes. By \"batching\" all of your review comments this way, a single email notification will be sent for your review, which contains all of your review comments together.","title":"Batch comments in a formal review"},{"location":"software/git-software-development/#batch-commits-when-accepting-suggestions-from-a-review","text":"When someone reviews your pull request, they may make suggestions that tweak your changes. Similar to review comments, suggestions from a review can either be applied one at a time (Commit suggestion), or they can be batched and applied together. To batch suggestions, first you need to open the \"Files changed\" tab; then for each suggestion you want to accept, click \"Add suggestion to batch\". Finally, click \"Commit suggestions\" to apply all batched suggestions as a single commit. Generally we prefer to batch related changes or miscellaneous tweaks rather than applying each one individually. But if there are a number of suggestions of a different nature, it is OK to group them such that you apply one batch for each set of related suggestions (consistent with the guideline to put logically separate changes into separate commits).","title":"Batch commits when accepting suggestions from a review"},{"location":"software/ipv6-testing/","text":"Testing Software with IPv6 \u00b6 About this Document \u00b6 This document provides instructions on setting up a host with an IPv6 address for testing the OSG software stack. The plan is to be able to spin up special Fermicloud VM\u2019s that have corresponding public IPv6 addresses meaning that there will be a limit of ~15 VM\u2019s at one time. For more information on IPv6, consult Wikipedia . Requirements \u00b6 Be familiar with your institute's network policy and firewall configuration 1 Root access is required to configure iptables Enabling IPV6 \u00b6 Determine the public IPv6 address of your host. In the example below that would be 2001:400:2410:29::182 : user@host $ nslookup -type = aaaa <HOSTNAME> Server: 132.239.0.252 Address: 132.239.0.252#53 Non-authoritative answer: ipv6vm001.fnal.gov has AAAA address 2001:400:2410:29::182 Replacing <HOSTNAME> with your machine's hostname. Ask your network administrator for your IPv6 default gateway Modify /etc/sysconfig/network-scripts/ifcfg-eth0 and be sure these lines exist, and : IPV6INIT=yes IPV6_AUTOCONF=no IPV6ADDR=<IPV6 ADDRESS>\" IPV6_DEFAULTGW=\"The IPV6 Default Gateway\" Replace <IPV6 ADDRESS> with the address found in step 1. Restart the network devices: root@host # service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Testing IPv6 connectivity \u00b6 To verify that the VM is capable of IPv6 we will be using the ping6 command between the test VM and another IPv6 capable machine From another IPv6 capable machine, ping your VM: user@host $ ping6 ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov(ipv6vm001.fnal.gov) 56 data bytes 64 bytes from ipv6vm001.fnal.gov: icmp_seq=1 ttl=51 time=68.1 ms 64 bytes from ipv6vm001.fnal.gov: icmp_seq=2 ttl=51 time=57.6 ms From your test VM, ping another IPv6 capable machine: [efajardo@ipv6vm001 ~]# ping6 uaf-4.t2.ucsd.edu PING uaf-4.t2.ucsd.edu(uaf-4.t2.ucsd.edu) 56 data bytes 64 bytes from uaf-4.t2.ucsd.edu: icmp_seq=1 ttl=51 time=57.6 ms Verifying SSH over IPv6 \u00b6 Make sure you can login to your VM over IPv6. Currently, Fermilab's kerberos does not support SSH over IPv6. Add your ssh_key to your machine and make sure /etc/ssh/sshd_config has the following lines: RSAAuthentication yes PubkeyAuthentication yes Try connecting to you IPv6 enabled machine over SSH: efajardo@uaf-4 ~$ ssh -6 root@ipv6vm001.fnal.gov Last login: Wed Jun 11 14:51:47 2014 from 2607:f720:1700:1b30:21f:c6ff:feeb:2631 [root@ipv6vm001 ~]# Disabling IPv4 \u00b6 If you were able to log into your VM over IPv6, you can disable IPv4 and try to communicate exclusively over IPv6. Comment the IPADDR line in /etc/sysconfig/network-scripts/ifcfg-eth0 : #IPADDR=131.225.41.182 IPV6ADDR=\"2607:f720:1700:1b30::9b\" Note Ensure that your IPV6ADDR is uncommented otherwise you will not be able to connect to the host again Restart the network services: root@host # service network restart The ping command should no longer work: root@host # ping ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov (131.225.41.182): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Disabling IPv6 \u00b6 In your testing, you may find the need to disable IPv6. root@host # sysctl -w net.ipv6.conf.all.disable_ipv6 = 1 root@host # service network restart The ping6 command should no longer work: root@host # ping6 ipv6vm001.fnal.gov Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Testing in mixed mode \u00b6 To test IPv6 in mixed mode, you can use the ntop tool to monitor traffic over IPv6. ntop is installed on all the test machines and you can access the web interface at hostname:3000 . To see a table that displays network traffic between your VM and another host by going to All Protocols -> Traffic and looking at the IPv6 column. Enforcing communication over IPv6 \u00b6 If you want to enforce IPv6 over mixed mode you can try using the IPv6 address for whatever software that you are testing. For example with xrdcp: root@host # xrdcp -d 1 /tmp/first_test root:// [ 2607 :f720:1700:1b30::a4 ] :1094//tmp/first_test_8 [19B/19B][100%][==================================================][0B/s] Notice that the IPv6 address follows RFC2732 .","title":"IPv6 Testing"},{"location":"software/ipv6-testing/#testing-software-with-ipv6","text":"","title":"Testing Software with IPv6"},{"location":"software/ipv6-testing/#about-this-document","text":"This document provides instructions on setting up a host with an IPv6 address for testing the OSG software stack. The plan is to be able to spin up special Fermicloud VM\u2019s that have corresponding public IPv6 addresses meaning that there will be a limit of ~15 VM\u2019s at one time. For more information on IPv6, consult Wikipedia .","title":"About this Document"},{"location":"software/ipv6-testing/#requirements","text":"Be familiar with your institute's network policy and firewall configuration 1 Root access is required to configure iptables","title":"Requirements"},{"location":"software/ipv6-testing/#enabling-ipv6","text":"Determine the public IPv6 address of your host. In the example below that would be 2001:400:2410:29::182 : user@host $ nslookup -type = aaaa <HOSTNAME> Server: 132.239.0.252 Address: 132.239.0.252#53 Non-authoritative answer: ipv6vm001.fnal.gov has AAAA address 2001:400:2410:29::182 Replacing <HOSTNAME> with your machine's hostname. Ask your network administrator for your IPv6 default gateway Modify /etc/sysconfig/network-scripts/ifcfg-eth0 and be sure these lines exist, and : IPV6INIT=yes IPV6_AUTOCONF=no IPV6ADDR=<IPV6 ADDRESS>\" IPV6_DEFAULTGW=\"The IPV6 Default Gateway\" Replace <IPV6 ADDRESS> with the address found in step 1. Restart the network devices: root@host # service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ]","title":"Enabling IPV6"},{"location":"software/ipv6-testing/#testing-ipv6-connectivity","text":"To verify that the VM is capable of IPv6 we will be using the ping6 command between the test VM and another IPv6 capable machine From another IPv6 capable machine, ping your VM: user@host $ ping6 ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov(ipv6vm001.fnal.gov) 56 data bytes 64 bytes from ipv6vm001.fnal.gov: icmp_seq=1 ttl=51 time=68.1 ms 64 bytes from ipv6vm001.fnal.gov: icmp_seq=2 ttl=51 time=57.6 ms From your test VM, ping another IPv6 capable machine: [efajardo@ipv6vm001 ~]# ping6 uaf-4.t2.ucsd.edu PING uaf-4.t2.ucsd.edu(uaf-4.t2.ucsd.edu) 56 data bytes 64 bytes from uaf-4.t2.ucsd.edu: icmp_seq=1 ttl=51 time=57.6 ms","title":"Testing IPv6 connectivity"},{"location":"software/ipv6-testing/#verifying-ssh-over-ipv6","text":"Make sure you can login to your VM over IPv6. Currently, Fermilab's kerberos does not support SSH over IPv6. Add your ssh_key to your machine and make sure /etc/ssh/sshd_config has the following lines: RSAAuthentication yes PubkeyAuthentication yes Try connecting to you IPv6 enabled machine over SSH: efajardo@uaf-4 ~$ ssh -6 root@ipv6vm001.fnal.gov Last login: Wed Jun 11 14:51:47 2014 from 2607:f720:1700:1b30:21f:c6ff:feeb:2631 [root@ipv6vm001 ~]#","title":"Verifying SSH over IPv6"},{"location":"software/ipv6-testing/#disabling-ipv4","text":"If you were able to log into your VM over IPv6, you can disable IPv4 and try to communicate exclusively over IPv6. Comment the IPADDR line in /etc/sysconfig/network-scripts/ifcfg-eth0 : #IPADDR=131.225.41.182 IPV6ADDR=\"2607:f720:1700:1b30::9b\" Note Ensure that your IPV6ADDR is uncommented otherwise you will not be able to connect to the host again Restart the network services: root@host # service network restart The ping command should no longer work: root@host # ping ipv6vm001.fnal.gov PING ipv6vm001.fnal.gov (131.225.41.182): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1","title":"Disabling IPv4"},{"location":"software/ipv6-testing/#disabling-ipv6","text":"In your testing, you may find the need to disable IPv6. root@host # sysctl -w net.ipv6.conf.all.disable_ipv6 = 1 root@host # service network restart The ping6 command should no longer work: root@host # ping6 ipv6vm001.fnal.gov Request timeout for icmp_seq 0 Request timeout for icmp_seq 1","title":"Disabling IPv6"},{"location":"software/ipv6-testing/#testing-in-mixed-mode","text":"To test IPv6 in mixed mode, you can use the ntop tool to monitor traffic over IPv6. ntop is installed on all the test machines and you can access the web interface at hostname:3000 . To see a table that displays network traffic between your VM and another host by going to All Protocols -> Traffic and looking at the IPv6 column.","title":"Testing in mixed mode"},{"location":"software/ipv6-testing/#enforcing-communication-over-ipv6","text":"If you want to enforce IPv6 over mixed mode you can try using the IPv6 address for whatever software that you are testing. For example with xrdcp: root@host # xrdcp -d 1 /tmp/first_test root:// [ 2607 :f720:1700:1b30::a4 ] :1094//tmp/first_test_8 [19B/19B][100%][==================================================][0B/s] Notice that the IPv6 address follows RFC2732 .","title":"Enforcing communication over IPv6"},{"location":"software/koji-mass-rebuilds/","text":"Mass RPM Rebuilds for a new Build Target in Koji \u00b6 Whenever we move to a new OSG series (OSG 3.3) and/or a new RHEL version (EL7), we want to make new builds for all of our packages in the new koji build target (osg-3.3-el7). Due to tricky build dependencies and unexpected build failures, this can be a messy task; and in the past we have gone about it in an ad-hoc manner. This document will discuss some of the aspects of the task and issues involved, some possible approaches, and ultimately a proposal for a general tool or procedure for doing our mass rebuilds. New RHEL version vs new OSG series \u00b6 New RHEL version \u00b6 For a new RHEL version, we start with no osg packages to build against, so we are forced to build things in dependency order. Figuring out the dependency order is possibly the most difficult (or interesting) part of doing mass rebuilds -- more on that later. New OSG series \u00b6 For a new OSG series within an existing RHEL version, we have more options. While it's possible to \"start from scratch\" the same way we would with a new RHEL version and build everything in dependency order, this is not really necessary if we take advantage of existing builds from the previous series. A prior step is to determine the package list for the new series -- this will be some combination of Upcoming and the current release series, minus any packages pruned for the new series. This should also be reflected in the new trunk packaging area. All the current builds for packages in that list (from upcoming + current series) can be tagged into the new *-development (or *-build) repos. This should make all of the build dependencies available for mass rebuilding the new series all at once (osg-build koji *). After some consideration, I wholeheartedly endorse this approach for new OSG series -- for all but academic exercises. Rebuilding in dependency order when all the dependencies are already built just seems like wasted effort. Doing scratch builds of everything first \u00b6 Before doing the mass rebuilds in a new build target, it seems to be a good idea to do scratch builds of all the packages in the current series first. (Or, at least the ones we intend to bring into the new build target.) This will give us a chance to see any build failures that have crept in (possibly due to upstream changes in the OS or EPEL), and fix them first if desired, but in any case avoid the confusion of seeing the failures for the first time in the new build target. Doing mass scratch rebuilds for an existing series is easy, as they can all be done at once. Relatedly, doing a round of scratch builds after successfully building all packages into a new build target can also be useful, because it can reveal dependency issues only present in the new set of builds. Doing developer test installs or a round of VMU tests may also uncover any runtime dependency issues. Options for calculating build dependencies \u00b6 We can get dependency information from a number of places: scraping .spec files for Requires/BuildRequires/Provides and %package names querying existing rpms directly on koji-hub and our OS/EPEL mirrors ( rpm -q ) querying srpms from osg-build prebuild directly for build requirements inspecting previous buildroots to determine resolved build dependencies use repoquery to determine whatrequires/whatprovides for packages use yum-builddep to find packages with all build requirements available using the repodata (primary+filelists) from rpm repositories, including: upcoming + 3.X development + external repos (Centos/EPEL/JPackage), OR osg-upcoming-elX-build, which includes them all One important aspect is that the runtime requirements are also relevant for determining build requirements, since a build will require installing all of the runtime requirements of the packages required for the build. That is, (A BuildRequires B) and (B Requires C) implies A BuildRequires C . Combined with the fact that runtime requirements are transitive, that is, (A Requires B) and (B Requires C) implies A Requires C , computing build requirements is a recursive operation, which can be many levels deep. Another question to keep in mind is whether to use versioned requires/provides (i.e., BuildRequires xyz >= 1.2-3) or to only pay attention to the package/capability names. Similarly, whether to pay any attention to conflicts/obsoletes. These would add complexity to anything except the standard tools (repoquery, yum-builddep) which already take these things into account. (And we may get pretty far even without paying attention to versions.) Note also that the dependencies/capabilities for a given package often varies between different rhel versions. Pre-computing (predictive) vs just-in-time \u00b6 Two different approaches to determining dependency order for building are: pre compute all dependencies based on an existing series/rhel version, OR compute which remaining packages have all build reqs satisfied now The first approach has the benefit of being able to determine the packages that need to be built in order to accomplish a smaller subset goal first -- for example, to be able to install osg-wn-client. (And, if there are problems with resolving certain dependencies (say with osg-wn-client again), it will become apparent earlier, as opposed to not until all possible-to-build packages have been built.) The limitation of this approach is that the predicted set of files/capabilities that a binary package will provide may differ between osg series/rhel versions, and as a result may be inaccurate for the new build target. The second approach provides somewhat more confidence about being able to correctly determine which packages should be buildable at any point in time, but (as mentioned above) it is a bit more in the dark about seeing the bigger picture of the dependency graph or being able to build subsets of targets. It may be useful to have both options available -- building from the list in the second approach, but using the first mechanism to have a better picture of where things are at, or perhaps to steer toward finishing a certain subset of packages first. Package list closure, pruning \u00b6 At some point (either in the planning stage or after building packages into the new build target), we need to ensure that the new osg series/rhel version contains all of its install requirements for all of its packages. It would probably suffice to do a VMU run that installs each package (perhaps individually, to avoid conflicts). But if we go about it more analytically, we may also get, as a result, a list of packages which we previously only maintained for the purpose of building our other packages (ie, that were never required at runtime for any use cases that we cared about), which now, in the new target, are no longer build requirements (directly or indirectly) for any packages that we care about installing. Packages in this category could be reviewed to also be dropped from the new build target. Proposal / Recommendations \u00b6 As mentioned earlier, my recommendation is that we treat a new OSG series differently than a new RHEL version. For a new OSG series: \u00b6 update native/redhat packaging area to reflect packages for new series, including upcoming + trunk - removed packages tag existing builds of packages in new list into the new development tag (eg, for osg-3.3-el6, tag the .osgup.el6 and .osg32.el6 builds into osg-3.3-el6-development) build all packages in new packaging area into new build target at once for all successful builds, remove corresponding old builds (eg, .osgup/.osg32) from the new tag (osg-3.3-el6-development) For a new RHEL version: \u00b6 pull the repodata from the relevant *-build repo from koji: for pre-computing, use a build repo from an existing rhel version: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el6-build/latest/x86_64/repodata/ for just-in-time, use the new build repo: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el8-build/latest/x86_64/repodata/ the primary and filelists (sqlite) files can be used to get runtime requires and provides. (Note that this includes packages from the relevant external repos, also.) generate srpms repodata for the current set of packages to build, with osg-build prebuild and createrepo. the primary (sqlite) file can be used to get build-requires. use sql to resolve direct dependencies at the package name level: src-pkg: bin-pkg (BuildRequires) bin-pkg: bin-pkg (Requires) bin-pkg: src-pkg (bin-pkg comes from which src-pkg? only needed for pre-computing dependencies) resolve this list into a full list of recursive build dependencies. Since this is recursive, there is no way to do it in a fixed number of sql queries. However the above input list is already directly consumable by Make, which is designed to handle recursive dependencies just like this. Or we can write a new tool to do it in python. build ready-to-be-built packages update our copy of the repodata from the regen'ed *-build repo, as often as new versions become available update our dependency lists repeat until all packages are built","title":"Koji Mass Rebuilds"},{"location":"software/koji-mass-rebuilds/#mass-rpm-rebuilds-for-a-new-build-target-in-koji","text":"Whenever we move to a new OSG series (OSG 3.3) and/or a new RHEL version (EL7), we want to make new builds for all of our packages in the new koji build target (osg-3.3-el7). Due to tricky build dependencies and unexpected build failures, this can be a messy task; and in the past we have gone about it in an ad-hoc manner. This document will discuss some of the aspects of the task and issues involved, some possible approaches, and ultimately a proposal for a general tool or procedure for doing our mass rebuilds.","title":"Mass RPM Rebuilds for a new Build Target in Koji"},{"location":"software/koji-mass-rebuilds/#new-rhel-version-vs-new-osg-series","text":"","title":"New RHEL version vs new OSG series"},{"location":"software/koji-mass-rebuilds/#new-rhel-version","text":"For a new RHEL version, we start with no osg packages to build against, so we are forced to build things in dependency order. Figuring out the dependency order is possibly the most difficult (or interesting) part of doing mass rebuilds -- more on that later.","title":"New RHEL version"},{"location":"software/koji-mass-rebuilds/#new-osg-series","text":"For a new OSG series within an existing RHEL version, we have more options. While it's possible to \"start from scratch\" the same way we would with a new RHEL version and build everything in dependency order, this is not really necessary if we take advantage of existing builds from the previous series. A prior step is to determine the package list for the new series -- this will be some combination of Upcoming and the current release series, minus any packages pruned for the new series. This should also be reflected in the new trunk packaging area. All the current builds for packages in that list (from upcoming + current series) can be tagged into the new *-development (or *-build) repos. This should make all of the build dependencies available for mass rebuilding the new series all at once (osg-build koji *). After some consideration, I wholeheartedly endorse this approach for new OSG series -- for all but academic exercises. Rebuilding in dependency order when all the dependencies are already built just seems like wasted effort.","title":"New OSG series"},{"location":"software/koji-mass-rebuilds/#doing-scratch-builds-of-everything-first","text":"Before doing the mass rebuilds in a new build target, it seems to be a good idea to do scratch builds of all the packages in the current series first. (Or, at least the ones we intend to bring into the new build target.) This will give us a chance to see any build failures that have crept in (possibly due to upstream changes in the OS or EPEL), and fix them first if desired, but in any case avoid the confusion of seeing the failures for the first time in the new build target. Doing mass scratch rebuilds for an existing series is easy, as they can all be done at once. Relatedly, doing a round of scratch builds after successfully building all packages into a new build target can also be useful, because it can reveal dependency issues only present in the new set of builds. Doing developer test installs or a round of VMU tests may also uncover any runtime dependency issues.","title":"Doing scratch builds of everything first"},{"location":"software/koji-mass-rebuilds/#options-for-calculating-build-dependencies","text":"We can get dependency information from a number of places: scraping .spec files for Requires/BuildRequires/Provides and %package names querying existing rpms directly on koji-hub and our OS/EPEL mirrors ( rpm -q ) querying srpms from osg-build prebuild directly for build requirements inspecting previous buildroots to determine resolved build dependencies use repoquery to determine whatrequires/whatprovides for packages use yum-builddep to find packages with all build requirements available using the repodata (primary+filelists) from rpm repositories, including: upcoming + 3.X development + external repos (Centos/EPEL/JPackage), OR osg-upcoming-elX-build, which includes them all One important aspect is that the runtime requirements are also relevant for determining build requirements, since a build will require installing all of the runtime requirements of the packages required for the build. That is, (A BuildRequires B) and (B Requires C) implies A BuildRequires C . Combined with the fact that runtime requirements are transitive, that is, (A Requires B) and (B Requires C) implies A Requires C , computing build requirements is a recursive operation, which can be many levels deep. Another question to keep in mind is whether to use versioned requires/provides (i.e., BuildRequires xyz >= 1.2-3) or to only pay attention to the package/capability names. Similarly, whether to pay any attention to conflicts/obsoletes. These would add complexity to anything except the standard tools (repoquery, yum-builddep) which already take these things into account. (And we may get pretty far even without paying attention to versions.) Note also that the dependencies/capabilities for a given package often varies between different rhel versions.","title":"Options for calculating build dependencies"},{"location":"software/koji-mass-rebuilds/#pre-computing-predictive-vs-just-in-time","text":"Two different approaches to determining dependency order for building are: pre compute all dependencies based on an existing series/rhel version, OR compute which remaining packages have all build reqs satisfied now The first approach has the benefit of being able to determine the packages that need to be built in order to accomplish a smaller subset goal first -- for example, to be able to install osg-wn-client. (And, if there are problems with resolving certain dependencies (say with osg-wn-client again), it will become apparent earlier, as opposed to not until all possible-to-build packages have been built.) The limitation of this approach is that the predicted set of files/capabilities that a binary package will provide may differ between osg series/rhel versions, and as a result may be inaccurate for the new build target. The second approach provides somewhat more confidence about being able to correctly determine which packages should be buildable at any point in time, but (as mentioned above) it is a bit more in the dark about seeing the bigger picture of the dependency graph or being able to build subsets of targets. It may be useful to have both options available -- building from the list in the second approach, but using the first mechanism to have a better picture of where things are at, or perhaps to steer toward finishing a certain subset of packages first.","title":"Pre-computing (predictive) vs just-in-time"},{"location":"software/koji-mass-rebuilds/#package-list-closure-pruning","text":"At some point (either in the planning stage or after building packages into the new build target), we need to ensure that the new osg series/rhel version contains all of its install requirements for all of its packages. It would probably suffice to do a VMU run that installs each package (perhaps individually, to avoid conflicts). But if we go about it more analytically, we may also get, as a result, a list of packages which we previously only maintained for the purpose of building our other packages (ie, that were never required at runtime for any use cases that we cared about), which now, in the new target, are no longer build requirements (directly or indirectly) for any packages that we care about installing. Packages in this category could be reviewed to also be dropped from the new build target.","title":"Package list closure, pruning"},{"location":"software/koji-mass-rebuilds/#proposal-recommendations","text":"As mentioned earlier, my recommendation is that we treat a new OSG series differently than a new RHEL version.","title":"Proposal / Recommendations"},{"location":"software/koji-mass-rebuilds/#for-a-new-osg-series","text":"update native/redhat packaging area to reflect packages for new series, including upcoming + trunk - removed packages tag existing builds of packages in new list into the new development tag (eg, for osg-3.3-el6, tag the .osgup.el6 and .osg32.el6 builds into osg-3.3-el6-development) build all packages in new packaging area into new build target at once for all successful builds, remove corresponding old builds (eg, .osgup/.osg32) from the new tag (osg-3.3-el6-development)","title":"For a new OSG series:"},{"location":"software/koji-mass-rebuilds/#for-a-new-rhel-version","text":"pull the repodata from the relevant *-build repo from koji: for pre-computing, use a build repo from an existing rhel version: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el6-build/latest/x86_64/repodata/ for just-in-time, use the new build repo: https://koji.chtc.wisc.edu/mnt/koji/repos/osg-3.2-el8-build/latest/x86_64/repodata/ the primary and filelists (sqlite) files can be used to get runtime requires and provides. (Note that this includes packages from the relevant external repos, also.) generate srpms repodata for the current set of packages to build, with osg-build prebuild and createrepo. the primary (sqlite) file can be used to get build-requires. use sql to resolve direct dependencies at the package name level: src-pkg: bin-pkg (BuildRequires) bin-pkg: bin-pkg (Requires) bin-pkg: src-pkg (bin-pkg comes from which src-pkg? only needed for pre-computing dependencies) resolve this list into a full list of recursive build dependencies. Since this is recursive, there is no way to do it in a fixed number of sql queries. However the above input list is already directly consumable by Make, which is designed to handle recursive dependencies just like this. Or we can write a new tool to do it in python. build ready-to-be-built packages update our copy of the repodata from the regen'ed *-build repo, as often as new versions become available update our dependency lists repeat until all packages are built","title":"For a new RHEL version:"},{"location":"software/koji-workflow/","text":"Koji Workflow \u00b6 This covers the basics of using and understanding the OSG Koji instance. It is meant primarily for OSG Software team members who need to interact with the service. Terminology \u00b6 Using and understanding the following terminology correctly will help in the reading of this document: Package This refers to a named piece of software in the Koji database. An example would be \"lcmaps\". Build A specific version and release of a package, and an associated state. A build state may be successful (and contain RPMs), failed, or in-progress. A given build may be in one or more tags. The build is associated with the output of the latest build task with the same version and release of the package. Tag A named set of packages and builds, parent tags, and reference to external repositories. An example would be the \"osg-3.3-el6-development\" tag, which contains (among others) the \"lcmaps\" package and the \"lcmaps-1.6.6-1.1.osg33.el6\" build. There is an inheritance structure to tags: by default, all packages/builds in a parent tag are added to the tag. A tag may contain a reference to (possibly inherited) external repositories; the RPMs in these repositories are added to repositories created from this tag. Examples of referenced external repositories include CentOS base, EPEL, or JPackage. Note A tag is NOT a yum repository. Target A target consists of a build tag and a destination tag. An example is \"osg-3.3-el6\", where the build tag is \"osg-3.3-el6-build\" and the destination tag is \"osg-3.3-el6\". A target is used by the build task to know what repository to build from and tag to build into. Task A unit of work for Koji. Several common tasks are: build This task takes a SRPM and a target, and attempts to create a complete Build in the target's destination tag from the target's build repository. This task will launch one buildArch task for each architecture in the destination tag; if each subtask is successful, then it will launch a tagBuild subtask. Note If the build task is marked as \"scratch\", then it won't result in a saved Build. buildArch This task takes a SRPM, architecture name, and a Koji repository as an input, and runs mock to create output RPMs for that arch. The build artifacts are added to the Build if all buildArch tasks are successful. tagBuild This adds a successful build to a given tag. newRepo This creates a new repository from a given tag. Build artifacts The results of a buildArch task. Their metadata are recorded in the Koji database, and files are saved to disk. Metadata may include checksums, timestamps, and who initiated the task. Artifacts may include RPMs, SRPMs, and build logs. Repository A yum repository created from the contents of a tag at a specific point in time. By default, the yum repository will contain all successful, non-blocked builds in the tag, plus all RPMs in the external repositories for the tag. Obtaining Access \u00b6 Building OSG packages in Koji requires these privileges: access to the OSG subversion repository at https://vdt.cs.wisc.edu/svn access to a login node at UW Comp Sci such as moria.cs.wisc.edu access to the Koji service via a grid user certificate See the old user certificates document for information about how to get a user certificate. Open a Freshdesk ticket with the subject \"Requesting access to Koji\" with the following information: - top 3 username choices for the login node and SVN (8 characters max, no punctuation) - the DN of your user certificate Assign the ticket to the Software team. Initial Setup \u00b6 You will be using the OSG Build Tools to interact with Koji. You can use them on either your own machine or on your UW Comp Sci login node such as moria . Setting up on moria \u00b6 Perform the following to set up the build tools on moria : Clone the osg-build git repo you@moria$ git clone https://github.com/opensciencegrid/osg-build $HOME /osg-build Set your $PATH : you@moria$ export PATH = $PATH : $HOME /osg-build you@moria$ export PATH = $PATH :/p/vdt/workspace/quilt/bin you@moria$ export PATH = $PATH :/p/vdt/workspace/tarball-client/stable/sys Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions. Setting up on your own host \u00b6 This requires an Enterprise Linux 6 or 7 host. Install the OSG YUM repositories If using OSG 3.5 or newer, enable the devops repository. Install osg-build and its dependencies: you@host$ sudo yum install osg-build Install a program for getting grid certificates you@host$ sudo yum install globus-proxy-utils Note If you already have voms-clients-cpp or voms-clients-java installed, you can use voms-proxy-init -rfc instead of grid-proxy-init , and don't need to install globus-proxy-utils . (Optional) If you want to do mock builds (these are local builds in a chroot), add yourself to the mock user group: you@host$ sudo usermod -a -G mock $USER Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. Note If you are using a certificate from SAML or Kerberos credentials, such as with cigetcert or kx509 , skip this step. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions. Authenticating to Koji \u00b6 To use the OSG Build tools and the Koji command-line client, you will need to make sure you can authenticate to Koji. This involves getting a grid proxy certificate. Do one of the following: On moria Run osgrun grid-proxy-init -bits 2048 and type your grid certificate password. If you cannot find osgrun , ensure you have /p/vdt/workspace/tarball-client/stable/sys in your $PATH . On your local machine Run grid-proxy-init -bits 2048 (if using globus-proxy-utils ) or voms-proxy-init -rfc -bits 2048 (if using voms-clients ) and type your grid certificate password. On your local machine using SAML or Kerberos-based credentials Run cigetcert or kx509 and perform whatever identification challenges you are asked. To verify your login access and permissions, run: you@host$ osg-koji list-permissions --mine You should see a list of your permissions if successful, or an error message if unsuccessful. Note If you see the error SSL: EE_KEY_TOO_SMALL , OpenSSL may be rejecting your proxy because it is too short. Be sure to request at least 2048 bits by passing -bits 2048 to grid-proxy-init or voms-proxy-init . You can check the key length by examining your proxy: you@host$ openssl x509 -in /tmp/x509up_u $( id -u ) -noout -text and looking at the \"Subject Public Key Info\" which might look like Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) Using Koji \u00b6 Creating a new build \u00b6 We create a new build in Koji from the package's directory in OSG Software subversion. If a successful build already exists in Koji (regardless of whether it is in the tag you use), you cannot replace the build. Two builds are the same if they have the same NVR (Name-Version-Release). You can do a \"scratch\" build, which recompiles, but the results are not added to the tag. This is useful for experimenting with koji. To do a build, execute the following command from within the OSG Software subversion checkout: [you@host]$ osg-build koji <PACKAGE NAME> To do a scratch build, simply add the --scratch command line flag. When you do a non-scratch build, it will build with the osg-el6 and osg-el7 targets. This will assign your build the osg-3.4-el6-development and osg-3.4-el7-development tags (and your package will be assigned the osg-el6 and osg-el7 tags). If successful, your build will end up in the Koji osg-minefield yum repos and will eventually show up in the osg-development yum repos. This is a high latency process. Build task Results \u00b6 How to find build results \u00b6 The most recent build results are always shown on the home page of Koji: https://koji.opensciencegrid.org/koji/index Clicking on a build result brings you to the build information page. A successful build will result in the build page having build logs, RPMs, and a SRPM. If your build isn't in the recent list, you can use the search box in the upper-right-hand corner. Type the exact package name (or use a wildcard), and it will bring up a list of all builds for that package. You can find your build from there. For example, the \"lcmaps\" package page is here: https://koji.opensciencegrid.org/koji/packageinfo?packageID=56 And the lcmaps-1.6.6-1.1.osg33.el6 build is here: https://koji.opensciencegrid.org/koji/buildinfo?buildID=7427 Trying our your build \u00b6 Because it takes a while for your build to get into one of the regular repositories, it's simplest to download your RPM directly (see the previous section on How to find build results), and install it with: [root@host]# yum localinstall <RPM> How to get the resulting RPM into a repository \u00b6 Once a package has been built, it is added to a tag. We then must turn the tag into a yum repository. This is normally done automatically and you do not need to deal with it yourself. Three notes: The kojira daemon creates a repository automatically post-build on the koji-hub host. Eventually, the development repository will be the one hosted by koji-hub. The koji-hub repository can be created manually by running [you@host]$ osg-koji regen-repo <TAG NAME> For example, the tag name for osg-development in 3.4 on el6 is \"osg-3.4-el6-development\". Likely, you won't need to do this when kojira is working. - Repositories are created on external hosts with the mash tool. These are usually triggered by cron jobs, but may be run by hand too. Documentation for running mash is on the TODO list. - You can create your own personal repository using mash . Debugging build issues \u00b6 Failed build tasks can be seen from the Koji homepage. The logs from the tasks are included. Relevant logs include: root.log This is the log of mock trying to create an appropriate build root for your RPM. This will invoke yum twice: once to create a generic build root, once for all the dependencies in your BuildRequires. All RPMs in your build root will be logged here. If mock is unable to create the build root, the reason will show up here. 404 Errors If you see Error downloading packages and HTTP Error 404 - Not Found errors in your root.log , this commonly indicates that an rpm repo mirror was updated and our build repo is out-of-date. This can be fixed by regenerating the relevant build repos for your builds. This is usually something like osg-3.4-el7-build or osg-upcoming-el7-build ; but you can find the exact build tag by clicking the Build Target link for the koji task, and whatever is listed for the Build Tag is the name of the repo to regen. Regenerate each repo that failed with 404 errors: $ osg-koji regen-repo <BUILD TAG> build.log The output of the rpmbuild executable. If your package fails to compile, the reason will show up here. One input to the buildArch task is a repository, which is based on a Koji tag. If the repository hasn't been recreated for a dependency you need (for example, when kojira isn't working), you may not have the right RPMs available in your build root. One common issue is building a chain of dependencies. For example, suppose build B depends on the results of build A. If you build A then build B immediately, B will likely fail. This is because A is not in the repository that B uses. The proper string of events building A, starting the regeneration of the destination and build repo (which should happen in a few minutes of the build A task completing), then submitting build task B. Note if you submit build task B while the build repository task is open, it will not start until the build task has finished. Other errors package <PACKAGE NAME> not in list for tag <TAG> This happens when the name of the directory your package is in does not match the name of the package. You must rename one or the other and commit your changes before trying again. Promoting Builds from Development -> Testing \u00b6 Software contributors can promote any package to testing. Members of the security team can promote ca-cert packages to testing. To promote from development to testing: Using osg-promote \u00b6 Before using osg-promote , authenticate to Koji as above . If you want to promote the latest version: [you@host]$ osg-promote -r <OSGVER>-testing <PACKAGE NAME> <PACKAGE NAME> is the bare package name without version, e.g. gratia-probe . If you want to promote a specific version: [you@host]$ osg-promote -r <OSGVER>-testing <BUILD NAME> <BUILD NAME> is a full name-version-revision.disttag such as gratia-probe-1.17.0-2.osg33.el6 . <OSGVER> is the OSG major version that you are promoting for (e.g. 3.4 ). osg-promote will promote both the el6 and el7 builds of a package. After promoting, copy and paste the JIRA code osg-promote produces into the JIRA ticket that you are working on. For osg-promote , you may omit the .osg34.el6 or .osg34.el7 ; the script will add the appropriate disttag on. See OSG Building Tools for full details on osg-promote . Creating custom koji areas \u00b6 Occasionally you may want to make builds of a package (or packages) which you do not yet want to go into the main development repos. In this case, you can create a set of custom koji tags and build targets for these builds. We have a script in our osg-next-tools repo called new-koji-area that facilitates this set up. Further reading \u00b6 Official Koji documentation: https://docs.pagure.org/koji/ Fedora's koji documentation: https://fedoraproject.org/wiki/Koji Fedora's \"Using Koji\" page: https://docs.fedoraproject.org/en-US/package-maintainers/Using_the_Koji_Build_System/ Note that some instructions there may not apply to OSG's Koji. For the most part though, they are useful.","title":"Koji Workflow"},{"location":"software/koji-workflow/#koji-workflow","text":"This covers the basics of using and understanding the OSG Koji instance. It is meant primarily for OSG Software team members who need to interact with the service.","title":"Koji Workflow"},{"location":"software/koji-workflow/#terminology","text":"Using and understanding the following terminology correctly will help in the reading of this document: Package This refers to a named piece of software in the Koji database. An example would be \"lcmaps\". Build A specific version and release of a package, and an associated state. A build state may be successful (and contain RPMs), failed, or in-progress. A given build may be in one or more tags. The build is associated with the output of the latest build task with the same version and release of the package. Tag A named set of packages and builds, parent tags, and reference to external repositories. An example would be the \"osg-3.3-el6-development\" tag, which contains (among others) the \"lcmaps\" package and the \"lcmaps-1.6.6-1.1.osg33.el6\" build. There is an inheritance structure to tags: by default, all packages/builds in a parent tag are added to the tag. A tag may contain a reference to (possibly inherited) external repositories; the RPMs in these repositories are added to repositories created from this tag. Examples of referenced external repositories include CentOS base, EPEL, or JPackage. Note A tag is NOT a yum repository. Target A target consists of a build tag and a destination tag. An example is \"osg-3.3-el6\", where the build tag is \"osg-3.3-el6-build\" and the destination tag is \"osg-3.3-el6\". A target is used by the build task to know what repository to build from and tag to build into. Task A unit of work for Koji. Several common tasks are: build This task takes a SRPM and a target, and attempts to create a complete Build in the target's destination tag from the target's build repository. This task will launch one buildArch task for each architecture in the destination tag; if each subtask is successful, then it will launch a tagBuild subtask. Note If the build task is marked as \"scratch\", then it won't result in a saved Build. buildArch This task takes a SRPM, architecture name, and a Koji repository as an input, and runs mock to create output RPMs for that arch. The build artifacts are added to the Build if all buildArch tasks are successful. tagBuild This adds a successful build to a given tag. newRepo This creates a new repository from a given tag. Build artifacts The results of a buildArch task. Their metadata are recorded in the Koji database, and files are saved to disk. Metadata may include checksums, timestamps, and who initiated the task. Artifacts may include RPMs, SRPMs, and build logs. Repository A yum repository created from the contents of a tag at a specific point in time. By default, the yum repository will contain all successful, non-blocked builds in the tag, plus all RPMs in the external repositories for the tag.","title":"Terminology"},{"location":"software/koji-workflow/#obtaining-access","text":"Building OSG packages in Koji requires these privileges: access to the OSG subversion repository at https://vdt.cs.wisc.edu/svn access to a login node at UW Comp Sci such as moria.cs.wisc.edu access to the Koji service via a grid user certificate See the old user certificates document for information about how to get a user certificate. Open a Freshdesk ticket with the subject \"Requesting access to Koji\" with the following information: - top 3 username choices for the login node and SVN (8 characters max, no punctuation) - the DN of your user certificate Assign the ticket to the Software team.","title":"Obtaining Access"},{"location":"software/koji-workflow/#initial-setup","text":"You will be using the OSG Build Tools to interact with Koji. You can use them on either your own machine or on your UW Comp Sci login node such as moria .","title":"Initial Setup"},{"location":"software/koji-workflow/#setting-up-on-moria","text":"Perform the following to set up the build tools on moria : Clone the osg-build git repo you@moria$ git clone https://github.com/opensciencegrid/osg-build $HOME /osg-build Set your $PATH : you@moria$ export PATH = $PATH : $HOME /osg-build you@moria$ export PATH = $PATH :/p/vdt/workspace/quilt/bin you@moria$ export PATH = $PATH :/p/vdt/workspace/tarball-client/stable/sys Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions.","title":"Setting up on moria"},{"location":"software/koji-workflow/#setting-up-on-your-own-host","text":"This requires an Enterprise Linux 6 or 7 host. Install the OSG YUM repositories If using OSG 3.5 or newer, enable the devops repository. Install osg-build and its dependencies: you@host$ sudo yum install osg-build Install a program for getting grid certificates you@host$ sudo yum install globus-proxy-utils Note If you already have voms-clients-cpp or voms-clients-java installed, you can use voms-proxy-init -rfc instead of grid-proxy-init , and don't need to install globus-proxy-utils . (Optional) If you want to do mock builds (these are local builds in a chroot), add yourself to the mock user group: you@host$ sudo usermod -a -G mock $USER Copy your user certificate and key into $HOME/.globus/usercert.pem and $HOME/.globus/userkey.pem . Make sure userkey.pem is only readable by yourself. Note If you are using a certificate from SAML or Kerberos credentials, such as with cigetcert or kx509 , skip this step. (Optional) Load your certificate into your browser. This will allow you to make some changes using the Koji web interface . Set up the OSG Koji config you@moria$ osg-koji setup Answer \"yes\" to all questions.","title":"Setting up on your own host"},{"location":"software/koji-workflow/#authenticating-to-koji","text":"To use the OSG Build tools and the Koji command-line client, you will need to make sure you can authenticate to Koji. This involves getting a grid proxy certificate. Do one of the following: On moria Run osgrun grid-proxy-init -bits 2048 and type your grid certificate password. If you cannot find osgrun , ensure you have /p/vdt/workspace/tarball-client/stable/sys in your $PATH . On your local machine Run grid-proxy-init -bits 2048 (if using globus-proxy-utils ) or voms-proxy-init -rfc -bits 2048 (if using voms-clients ) and type your grid certificate password. On your local machine using SAML or Kerberos-based credentials Run cigetcert or kx509 and perform whatever identification challenges you are asked. To verify your login access and permissions, run: you@host$ osg-koji list-permissions --mine You should see a list of your permissions if successful, or an error message if unsuccessful. Note If you see the error SSL: EE_KEY_TOO_SMALL , OpenSSL may be rejecting your proxy because it is too short. Be sure to request at least 2048 bits by passing -bits 2048 to grid-proxy-init or voms-proxy-init . You can check the key length by examining your proxy: you@host$ openssl x509 -in /tmp/x509up_u $( id -u ) -noout -text and looking at the \"Subject Public Key Info\" which might look like Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit)","title":"Authenticating to Koji"},{"location":"software/koji-workflow/#using-koji","text":"","title":"Using Koji"},{"location":"software/koji-workflow/#creating-a-new-build","text":"We create a new build in Koji from the package's directory in OSG Software subversion. If a successful build already exists in Koji (regardless of whether it is in the tag you use), you cannot replace the build. Two builds are the same if they have the same NVR (Name-Version-Release). You can do a \"scratch\" build, which recompiles, but the results are not added to the tag. This is useful for experimenting with koji. To do a build, execute the following command from within the OSG Software subversion checkout: [you@host]$ osg-build koji <PACKAGE NAME> To do a scratch build, simply add the --scratch command line flag. When you do a non-scratch build, it will build with the osg-el6 and osg-el7 targets. This will assign your build the osg-3.4-el6-development and osg-3.4-el7-development tags (and your package will be assigned the osg-el6 and osg-el7 tags). If successful, your build will end up in the Koji osg-minefield yum repos and will eventually show up in the osg-development yum repos. This is a high latency process.","title":"Creating a new build"},{"location":"software/koji-workflow/#build-task-results","text":"","title":"Build task Results"},{"location":"software/koji-workflow/#how-to-find-build-results","text":"The most recent build results are always shown on the home page of Koji: https://koji.opensciencegrid.org/koji/index Clicking on a build result brings you to the build information page. A successful build will result in the build page having build logs, RPMs, and a SRPM. If your build isn't in the recent list, you can use the search box in the upper-right-hand corner. Type the exact package name (or use a wildcard), and it will bring up a list of all builds for that package. You can find your build from there. For example, the \"lcmaps\" package page is here: https://koji.opensciencegrid.org/koji/packageinfo?packageID=56 And the lcmaps-1.6.6-1.1.osg33.el6 build is here: https://koji.opensciencegrid.org/koji/buildinfo?buildID=7427","title":"How to find build results"},{"location":"software/koji-workflow/#trying-our-your-build","text":"Because it takes a while for your build to get into one of the regular repositories, it's simplest to download your RPM directly (see the previous section on How to find build results), and install it with: [root@host]# yum localinstall <RPM>","title":"Trying our your build"},{"location":"software/koji-workflow/#how-to-get-the-resulting-rpm-into-a-repository","text":"Once a package has been built, it is added to a tag. We then must turn the tag into a yum repository. This is normally done automatically and you do not need to deal with it yourself. Three notes: The kojira daemon creates a repository automatically post-build on the koji-hub host. Eventually, the development repository will be the one hosted by koji-hub. The koji-hub repository can be created manually by running [you@host]$ osg-koji regen-repo <TAG NAME> For example, the tag name for osg-development in 3.4 on el6 is \"osg-3.4-el6-development\". Likely, you won't need to do this when kojira is working. - Repositories are created on external hosts with the mash tool. These are usually triggered by cron jobs, but may be run by hand too. Documentation for running mash is on the TODO list. - You can create your own personal repository using mash .","title":"How to get the resulting RPM into a repository"},{"location":"software/koji-workflow/#debugging-build-issues","text":"Failed build tasks can be seen from the Koji homepage. The logs from the tasks are included. Relevant logs include: root.log This is the log of mock trying to create an appropriate build root for your RPM. This will invoke yum twice: once to create a generic build root, once for all the dependencies in your BuildRequires. All RPMs in your build root will be logged here. If mock is unable to create the build root, the reason will show up here. 404 Errors If you see Error downloading packages and HTTP Error 404 - Not Found errors in your root.log , this commonly indicates that an rpm repo mirror was updated and our build repo is out-of-date. This can be fixed by regenerating the relevant build repos for your builds. This is usually something like osg-3.4-el7-build or osg-upcoming-el7-build ; but you can find the exact build tag by clicking the Build Target link for the koji task, and whatever is listed for the Build Tag is the name of the repo to regen. Regenerate each repo that failed with 404 errors: $ osg-koji regen-repo <BUILD TAG> build.log The output of the rpmbuild executable. If your package fails to compile, the reason will show up here. One input to the buildArch task is a repository, which is based on a Koji tag. If the repository hasn't been recreated for a dependency you need (for example, when kojira isn't working), you may not have the right RPMs available in your build root. One common issue is building a chain of dependencies. For example, suppose build B depends on the results of build A. If you build A then build B immediately, B will likely fail. This is because A is not in the repository that B uses. The proper string of events building A, starting the regeneration of the destination and build repo (which should happen in a few minutes of the build A task completing), then submitting build task B. Note if you submit build task B while the build repository task is open, it will not start until the build task has finished. Other errors package <PACKAGE NAME> not in list for tag <TAG> This happens when the name of the directory your package is in does not match the name of the package. You must rename one or the other and commit your changes before trying again.","title":"Debugging build issues"},{"location":"software/koji-workflow/#promoting-builds-from-development-testing","text":"Software contributors can promote any package to testing. Members of the security team can promote ca-cert packages to testing. To promote from development to testing:","title":"Promoting Builds from Development -> Testing"},{"location":"software/koji-workflow/#using-osg-promote","text":"Before using osg-promote , authenticate to Koji as above . If you want to promote the latest version: [you@host]$ osg-promote -r <OSGVER>-testing <PACKAGE NAME> <PACKAGE NAME> is the bare package name without version, e.g. gratia-probe . If you want to promote a specific version: [you@host]$ osg-promote -r <OSGVER>-testing <BUILD NAME> <BUILD NAME> is a full name-version-revision.disttag such as gratia-probe-1.17.0-2.osg33.el6 . <OSGVER> is the OSG major version that you are promoting for (e.g. 3.4 ). osg-promote will promote both the el6 and el7 builds of a package. After promoting, copy and paste the JIRA code osg-promote produces into the JIRA ticket that you are working on. For osg-promote , you may omit the .osg34.el6 or .osg34.el7 ; the script will add the appropriate disttag on. See OSG Building Tools for full details on osg-promote .","title":"Using osg-promote"},{"location":"software/koji-workflow/#creating-custom-koji-areas","text":"Occasionally you may want to make builds of a package (or packages) which you do not yet want to go into the main development repos. In this case, you can create a set of custom koji tags and build targets for these builds. We have a script in our osg-next-tools repo called new-koji-area that facilitates this set up.","title":"Creating custom koji areas"},{"location":"software/koji-workflow/#further-reading","text":"Official Koji documentation: https://docs.pagure.org/koji/ Fedora's koji documentation: https://fedoraproject.org/wiki/Koji Fedora's \"Using Koji\" page: https://docs.fedoraproject.org/en-US/package-maintainers/Using_the_Koji_Build_System/ Note that some instructions there may not apply to OSG's Koji. For the most part though, they are useful.","title":"Further reading"},{"location":"software/new-team-member/","text":"Setup Instructions for New Team Members \u00b6 ssh access to a UW CompSci account, including AFS access Ask CHTC infrastructure Read/write access to the UW Subversion repository; Send email to Mat or Brian L after having obtained UW CompSci account User certificate Follow instructions here Import the certificate into your browser of choice Register for a GGUS account with the following information: Your certificate's subject DN Select none from the \"Virtual Organization\" drop-down Select yes for \"Do you want to have support access?\" and answer \"Why?\" with the following: Yes, I need to comment on tickets as a member of the OSG Software & Release Team (https://www.opensciencegrid.org/technology/#the-team) Access to Koji After obtaining certificate, follow the instructions on the Koji User Management doc Sign up for mailing lists software-discuss@osg-htc.org technology-team@osg-htc.org osg-commits@cs.wisc.edu GitHub team membership https://github.com/orgs/opensciencegrid/teams/software-and-release/members If > 50% S&R, add them to the triage schedule","title":"New Team Member"},{"location":"software/new-team-member/#setup-instructions-for-new-team-members","text":"ssh access to a UW CompSci account, including AFS access Ask CHTC infrastructure Read/write access to the UW Subversion repository; Send email to Mat or Brian L after having obtained UW CompSci account User certificate Follow instructions here Import the certificate into your browser of choice Register for a GGUS account with the following information: Your certificate's subject DN Select none from the \"Virtual Organization\" drop-down Select yes for \"Do you want to have support access?\" and answer \"Why?\" with the following: Yes, I need to comment on tickets as a member of the OSG Software & Release Team (https://www.opensciencegrid.org/technology/#the-team) Access to Koji After obtaining certificate, follow the instructions on the Koji User Management doc Sign up for mailing lists software-discuss@osg-htc.org technology-team@osg-htc.org osg-commits@cs.wisc.edu GitHub team membership https://github.com/orgs/opensciencegrid/teams/software-and-release/members If > 50% S&R, add them to the triage schedule","title":"Setup Instructions for New Team Members"},{"location":"software/osg-build-tools/","text":"OSG Build Tools \u00b6 This page documents the tools used for RPM development for the OSG Software Stack. See the RPM development guide for the principles on which these tools are based. The tools are distributed in the osg-build RPM in our repositories, but can also be used from a Git clone of opensciencegrid/osg-build on GitHub . This page is up-to-date as of osg-build version 1.14.1. The tools \u00b6 osg-build \u00b6 Overview \u00b6 This is the primary tool used in building source and binary RPMs. osg-build <TASK> [options] <PACKAGE DIRECTORY> [...] package_directory is a directory containing an osg/ and/or an upstream/ subdirectory. See the RPM development guide for how these directories are organized. Tasks \u00b6 koji \u00b6 Prebuilds the final source package, then builds it remotely using the Koji instance hosted at UW-Madison. https://koji.opensciencegrid.org By default, the resulting RPMs will end up in the osg-minefield repositories based on the most recent OSG major version (e.g. 3.4). You may specify a different set of repos with --repo , described later. RPMs from the osg-minefield repositories are regularly pulled to the osg-development repositories hosted by the GOC at http://repo.opensciencegrid.org Unless you specify otherwise (by passing --el6 , --el7 or specifying a different koji tag/target), the package will be built for both el6 and el7. This is the method used to build final versions of packages you expect to ship. lint \u00b6 Prebuilds the final source package, then runs rpmlint on it to check for various problems. You will need to have rpmlint installed. People on UW CSL machines should add /p/vdt/workspace/rpmlint to their $PATH. mock \u00b6 Prebuilds the final source package, then builds it locally using mock , and stores the resulting source and binary RPMs in the package-specific _build_results directory. prebuild \u00b6 Prebuilds the final source package from upstream sources (if any) and local files (if any). May create or overwrite the _upstream_srpm_contents and _final_srpm_contents directories. prepare \u00b6 Prebuilds the final source package, then calls rpmbuild -bp on the result, extracting and patching the source files (and performing any other steps defined in the %prep section of the spec file. The resulting sources will be under _final_srpm_contents . rpmbuild \u00b6 Prebuilds the final source package, then builds it locally using rpmbuild , and stores the resulting source and binary RPMs in the package-specific _build_results directory. quilt \u00b6 Collects the upstream local sources and spec file, then calls quilt setup on the spec file, extracting the source files and adding the patches to a quilt series file. See Quilt documentation (PDF link) for more information on quilt; also look at the example in the Usage Patterns section below. Similar to prepare (in fact, quilt calls rpmbuild -bp behind the scenes), but the source tree is in pre-patch state, and various quilt commands can be used to apply and modify patches. Unpacks into _quilt as of osg-build-1.2.2 or _final_srpm_contents in previous versions. Requires quilt . People on UW CSL machines should add /p/vdt/workspace/quilt/bin to their $PATH , and /p/vdt/workspace/quilt/share/man to their $MANPATH . Options \u00b6 This section lists the command-line options. --help \u00b6 Prints the built-in usage information and exits without doing anything else. --version \u00b6 Prints the version of osg-build and exits without doing anything else. Common Options \u00b6 -a, --autoclean, --no-autoclean \u00b6 Before each build, clean out the contents of the underscore directories (_build_results, _final_srpm_contents, _upstream_srpm_contents, _upstream_tarball_contents). If the directories are not cleaned up, earlier builds of a package may interfere with later ones. --no-autoclean will disable this. Default is true . Has no effect with the --vcs flag. -c, --cache-prefix prefix \u00b6 Sets the prefix for upstream source cache references. The prefix must be a valid URI starting with either http , https , or file , or one of the following special values: AFS (corresponds to file:///p/vdt/public/html/upstream , which is the location of the VDT cache using AFS from a UW CS machine). VDT (corresponds to http://vdt.cs.wisc.edu/upstream , which is the location of the VDT cache from off-site). AUTO (AFS if available, VDT if not) The upstream source cache must be organized as described above. All files referenced by .source files in the affected packages must exist in the cache, or a runtime error will occur. Default is AUTO . Has no effect with the --vcs flag. --el6, --el7, --redhat-release version (Config: redhat_release) \u00b6 Sets the distro version to build for. This affects the %dist tag, the mock config, and the default koji tag and target (unless otherwise specified). --el6 is equivalent to --redhat-release 6 --el7 is equivalent to --redhat-release 7 --loglevel loglevel \u00b6 Sets the verbosity of the script. Valid values are: debug , info , warning , error and critical . Default is info . -q, --quiet \u00b6 Do not display as much information. Equivalent to --loglevel warning -v, --verbose \u00b6 Display more information. Equivalent to --loglevel debug -w, --working-directory path \u00b6 Use path as the root directory of the files created by the script. For example, if path is $HOME/working , and the package being built is ndt , the following tree will be created: $HOME/working/ndt/_upstream_srpm_contents $HOME/working/ndt/_upstream_tarball_contents $HOME/working/ndt/_final_srpm_contents $HOME/working/ndt/_build_results If path is TEMP , a randomly named directory under /tmp is used as the working directory. The default setting is to use the package directory as the working directory. Has no effect with the --vcs flag. Options specific to prebuild task \u00b6 --full-extract \u00b6 If set, all upstream tarballs will be extracted into _upstream_tarball_contents/ during the prebuild step. This flag is now mostly redundant with the prepare and quilt tasks. Options specific to rpmbuild and mock tasks \u00b6 --distro-tag dist \u00b6 Sets the distribution tag added on to the end of the release in the RPM ( rpmbuild and mock tasks only ). Default is .osg.el6 or .osg.el7 -t, --target-arch arch \u00b6 Specify an architecture to build packages for ( rpmbuild and mock tasks only ). Default is unspecified, which builds for the current machine architecture. Options specific to mock task \u00b6 --mock-clean, --no-mock-clean \u00b6 Enable/disable deletion of the mock buildroot after a successful build. Default is true . -m, --mock-config path \u00b6 Specifies the mock configuration file to use. This file details how to set up the build environment used by mock for the build, including Yum repositories from which to install dependencies and certain predefined variables (e.g., the distribution tag %dist ). See also --mock-config-from-koji . --mock-config-from-koji build tag \u00b6 Creates a mock config from a Koji build tag. This is the most accurate way to replicate the build environment that Koji will provide (outside of Koji). The build tag is based on the distro version (el6, el7) and the OSG major version (3.3, 3.4). For 3.4 on el6, it is: osg-3.4-el6-build Also requires the Koji command-line tools (package koji ), obtainable from the osg repositories. Since this uses koji, some of the koji-specific options may apply, namely: --koji-backend , --koji-login , and --koji-wrapper . Options specific to koji task \u00b6 --dry-run \u00b6 Do not actually run koji, merely show the command(s) that will be run. For debugging purposes. --getfiles, --get-files \u00b6 For scratch builds without --vcs only. Download the resulting RPMs and logs from the build into the _build_results directory. -k, --kojilogin, --koji-login login \u00b6 Sets the login to use for the koji task. This should most likely be your CN. If not specified, will extract it from your client cert ( ~/.osg-koji/client.crt or ~/.koji/client.crt ). --koji-target target \u00b6 The koji target to use for building. Default is osg-el6 for el6 and osg-el7 for el7. --koji-tag tag \u00b6 The koji tag to add packages to. See the Koji Workflow guide for more information on the terminology. The special value TARGET uses the destination tag defined in the koji target. Default is osg-el6 or osg-el7 . --ktt, --koji-tag-and-target arg \u00b6 Shorthand for setting both --koji-tag and --koji-target to arg . --koji-wrapper, --no-koji-wrapper \u00b6 Enable/disable use of the osg-koji wrapper script around koji. See below for a description of osg-koji . Default is true . --koji-backend backend \u00b6 Specifies the method osg-build will use to interface with Koji. This can be shell or kojilib . --wait, --no-wait, --nowait \u00b6 Wait for koji tasks to finish. Bad for running multiple builds in a single command, since you will have to type in your passphrase for the first one, wait for it to complete, then type in your passphrase for the second one, wait for it to complete, etc. If you want to wait for multiple tasks to finish, use the koji watch-task command or look at the website https://koji.opensciencegrid.org . --wait used to be the default until osg-build-1.1.3 --regen-repos \u00b6 Start a regen-repo koji task on the build tag after each koji build, to update the build repository used for the next build. Not useful unless you are launching multiple builds. This enables you to launch builds that depend on each other. Doesn't work too well with --no-wait , since the next build may be started before the regen-repo task is complete. Waiting will keep the next build from being queued until the regen-repo is complete. --scratch, --no-scratch \u00b6 Perform scratch builds. A scratch build does not go into a repository, but the name-version-release (NVR) of the created RPMs are not considered used, so the build may be modified and repeated without needing a release bump. This has the same use case as the mock task: creating packages that you want to test before releasing. If you do not have a machine with mock set up, or want to test exactly the environment that Koji provides, scratch builds might be more convenient. --vcs, --no-vcs, --svn, --no-svn \u00b6 Have Koji check the package out from a version control system instead of creating an SRPM on the local machine and submitting that to Koji. Currently, SVN and Git are supported. If this flag is specified, you may use SVN URLs or URL@Revision pairs to specify the packages to build. You may continue specify package directories from an SVN checkout, in which case osg-build will use svn info to find the right URL@Revision pair to use and warn you about uncommitted changes. osg-build will also warn you about an outdated working directory. --vcs defaults to true for non-scratch builds, and false for scratch builds. --repo= destination repository , --upcoming \u00b6 Selects the repositories (osg-3.3, upcoming, etc.) to build packages for. Currently valid repositories are: Repository Description osg OSG Software development repos for trunk (this is the default) osg-3.3 (or just 3.3) OSG Software development repos for 3.3 branch upcoming OSG Software development repos for upcoming branch internal OSG Software internal branch hcc Holland Computing Center (Nebraska) testing repos --upcoming is an alias for --repo=upcoming Note that the repo selection affects which VCS paths you are allowed to build from. For example, you are not allowed to build from branches/osg-3.3 (from the OSG SVN) into the 'osg' repo, or from HCC's git repositories into the 'upcoming' repo. koji-tag-diff \u00b6 This script displays the differences between the latest packages in two koji tags. Example invocation: koji-tag-diff osg-3.4-el6-development osg-3.4-el7-testing This prints the packages that are in osg-3.4-el6-development but not in osg-3.4-el7-testing, or vice versa. osg-build-test \u00b6 This script runs automated tests for osg-build . Only a few tests have been implemented so far. osg-import-srpm \u00b6 This is a script to fetch an SRPM from a remote site, copy it into the upstream cache on AFS, and create an SVN package dir (if needed) with an upstream/*.source file. By default it will put downloaded files into the VDT upstream cache (/p/vdt/public/html/upstream), but you can pass --upstream-root=<UPSTREAM DIR> to put them somewhere else. If called with the --extract-spec or -e argument, it will extract the spec file from the SRPM and place it into the osg subdir in SVN. If called with the --diff-spec or -d argument, it will extract the spec file and compare it to the existing spec file in the osg subdir. The script hasn't been touched in a while and needs a good deal of cleanup. A planned feature is to allow doing a three-way diff between the existing RPM before OSG modifications, the new RPM before OSG modifications and the existing RPM after OSG modifications. osg-koji \u00b6 This is a wrapper script around the koji command line tool. It automatically specifies parameters to access the OSG's koji instance, and forces SSL authentication. It takes the same parameters as koji and passes them on. An additional command, osg-koji setup exists, which performs the following tasks: Create a koji configuration in ~/.osg-koji Create a CA bundle for verifying the server. Use either files in /etc/grid-security/certificates , or (if those are not found), from files downloaded from the DOEGrids and DigiCert sites. Create a client cert file. This can be a symlink to your grid proxy, or it can be a file created from your grid public and private key files. The location of those files can be specified by the --usercert and --userkey arguments. If unspecified, usercert defaults to ~/.globus/usercert.pem , and userkey defaults to ~/.globus/userkey.pem . osg-promote \u00b6 Overview \u00b6 Run this script to push packages from one set of repos to another (e.g. from development to testing), according to the OSG software promotion guidelines. Once the packages are promoted, the script will generate code to cut and paste into a JIRA comment. Synopsis \u00b6 osg-promote [-r|--route <ROUTE>]... [options] <PACKAGE OR BUILD> [...] Examples \u00b6 Promote the latest build of osg-version to testing for the current release series osg-promote -r testing osg-version Promote the latest builds of osg-ce to testing for the 3.3 and 3.4 release series osg-promote -r 3.3-testing -r 3.4-testing osg-ce Promote osg-build-1.5.0-1 to testing for the current release series osg-promote -r testing osg-build-1.5.0-1 Arguments \u00b6 -h \u00b6 Display help and a list of valid routes. package or build \u00b6 A package (e.g. osg-version ) or build (e.g. osg-version-3.3.0-1.osg33.el6 ) to promote. You may omit the dist tag (the .osg33.el6 part). If a package is specified, the most recent version of that package will be promoted. If a build is specified, that build and the build that has the same version - release for the other distro version(s) will be promoted. That is, if you specify the route 3.3-testing and the build foo-1-1 , then foo-1-1.osg33.el6 and foo-1-1.osg33.el7 will be promoted. This may be specified multiple times, to promote multiple packages. The NVRs of each set of builds for a package must match. -r ROUTE , --route ROUTE \u00b6 The promotion route to use. Use osg-promote -h to get a list of valid routes. This may be specified multiple times. For example, to promote for both 3.4 and 3.3, pass -r 3.4-testing -r 3.3-testing . If not specified, the testing route is used, which corresponds to the testing route for the latest release series. -n, --dry-run \u00b6 Do not promote, just show what would be done. --el6-only / --el7-only \u00b6 Only promote packages for el6 / el7. --no-el6 / --no-el7 \u00b6 Do not promote packages for el6 / el7. --ignore-rejects \u00b6 Ignore rejections due to version mismatch between dvers or missing package for one dver. --regen \u00b6 Regenerate the destination repos after promoting. -y, --assume-yes \u00b6 Do not prompt before promotion. Common Usage Patterns \u00b6 Verify that all files necessary to build the package are in the right place \u00b6 Run osg-build prebuild <PACKAGEDIR> . Fetch and extract all source files for examination \u00b6 Run osg-build prebuild --full-extract <PACKAGEDIR> . Look inside the _upstream_tarball_contents directory. Get a post-patch version of the upstream sources for examination \u00b6 Run osg-build prepare <PACKAGEDIR> . Look inside the _build_results directory. See which patches work with a new version of a package, update or remove them \u00b6 Place the new source tarball into the upstream cache, edit the version in the spec file and *.sources files as necessary Run osg-build quilt <PACKAGEDIR> . Enter the extracted sources inside the _final_srpm_contents directory. You should see a file called series and a symlink called patches . Type quilt series to get a list of patches in order of application. Type quilt push to apply the next patch. If the patch applies cleanly, continue. If the patch applies with some fuzz, type quilt refresh to update the offsets in the patch. If the patch does not apply and you wish to remove it, type quilt delete <PATCH NAME> (delete only removes it from the series file, not the disk) If the patch does not apply and you wish to fix it, either type quilt push -f to interactively apply the patch, or quilt delete <PATCH NAME> the patch and use quilt new / quilt edit / quilt refresh to edit files and make a new patch from your changes. Consult the quilt(1) manpage for more info. If you have a new patch, run quilt import <PATCHFILE> to add the patch to the series file, and run quilt push to apply it. If you have changes to make to the source code that you want to save as a patch, type quilt new <PATCHNAME> , edit the files, type quilt add <FILE> on each file you edited, then type quilt refresh to recreate the patch. Once you're all done, copy the patches in the patches/ directory to the osg/ dir in SVN, run quilt series to get the application order and update the spec file accordingly. See if a package builds successfully for OSG 3.4 \u00b6 If you have all the build dependencies of the package installed, run osg-build rpmbuild <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have all the build dependencies installed, or want to make sure you specified all of the necessary ones and the package builds from a clean environment, run osg-build mock --mock-config-from-koji osg-3.4-el6-build <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have mock installed, or want to exactly replicate the build environment in Koji, run osg-build koji --scratch <PACKAGEDIR> . You may download the resulting RPMs from kojiweb https://koji.opensciencegrid.org/koji or pass --getfiles to osg-build koji and they will get downloaded to the _build_results directory. Check for potential errors in a package \u00b6 Run osg-build lint <PACKAGEDIR> . Create and test a final build of a package for all platforms for upcoming \u00b6 svn commit your changes in branches/upcoming . Type osg-build koji --repo=upcoming <PACKAGEDIR> Wait for the osg-upcoming-minefield repos to be regenerated containing the new version of your package. You can run osg-koji wait-repo osg-upcoming-el<X>-development --build=<PACKAGENAME-VERSION-RELEASE> and wait for that process to finish (substitute 6 or 7 for X ). Or, you can just check kojiweb https://koji.opensciencegrid.org/koji/tasks . On your test machine, make sure the osg-upcoming-minefield repo is enabled (edit /etc/yum.repos.d/osg-upcoming-minefield.repo or /etc/yum.repos.d/osg-el6-upcoming-minefield.repo ). Clean your cache ( yum clean all; yum clean expire-cache ). Install your software, see if it works. Promote the latest build of a package to testing for the current OSG release series \u00b6 Run osg-promote -r testing <PACKAGE> Promote the latest build of a package to testing for the 3.3 and 3.4 release series \u00b6 Run osg-promote -r 3.3-testing -r 3.4-testing <PACKAGE>","title":"OSG Build Tools"},{"location":"software/osg-build-tools/#osg-build-tools","text":"This page documents the tools used for RPM development for the OSG Software Stack. See the RPM development guide for the principles on which these tools are based. The tools are distributed in the osg-build RPM in our repositories, but can also be used from a Git clone of opensciencegrid/osg-build on GitHub . This page is up-to-date as of osg-build version 1.14.1.","title":"OSG Build Tools"},{"location":"software/osg-build-tools/#the-tools","text":"","title":"The tools"},{"location":"software/osg-build-tools/#osg-build","text":"","title":"osg-build"},{"location":"software/osg-build-tools/#overview","text":"This is the primary tool used in building source and binary RPMs. osg-build <TASK> [options] <PACKAGE DIRECTORY> [...] package_directory is a directory containing an osg/ and/or an upstream/ subdirectory. See the RPM development guide for how these directories are organized.","title":"Overview"},{"location":"software/osg-build-tools/#tasks","text":"","title":"Tasks"},{"location":"software/osg-build-tools/#koji","text":"Prebuilds the final source package, then builds it remotely using the Koji instance hosted at UW-Madison. https://koji.opensciencegrid.org By default, the resulting RPMs will end up in the osg-minefield repositories based on the most recent OSG major version (e.g. 3.4). You may specify a different set of repos with --repo , described later. RPMs from the osg-minefield repositories are regularly pulled to the osg-development repositories hosted by the GOC at http://repo.opensciencegrid.org Unless you specify otherwise (by passing --el6 , --el7 or specifying a different koji tag/target), the package will be built for both el6 and el7. This is the method used to build final versions of packages you expect to ship.","title":"koji"},{"location":"software/osg-build-tools/#lint","text":"Prebuilds the final source package, then runs rpmlint on it to check for various problems. You will need to have rpmlint installed. People on UW CSL machines should add /p/vdt/workspace/rpmlint to their $PATH.","title":"lint"},{"location":"software/osg-build-tools/#mock","text":"Prebuilds the final source package, then builds it locally using mock , and stores the resulting source and binary RPMs in the package-specific _build_results directory.","title":"mock"},{"location":"software/osg-build-tools/#prebuild","text":"Prebuilds the final source package from upstream sources (if any) and local files (if any). May create or overwrite the _upstream_srpm_contents and _final_srpm_contents directories.","title":"prebuild"},{"location":"software/osg-build-tools/#prepare","text":"Prebuilds the final source package, then calls rpmbuild -bp on the result, extracting and patching the source files (and performing any other steps defined in the %prep section of the spec file. The resulting sources will be under _final_srpm_contents .","title":"prepare"},{"location":"software/osg-build-tools/#rpmbuild","text":"Prebuilds the final source package, then builds it locally using rpmbuild , and stores the resulting source and binary RPMs in the package-specific _build_results directory.","title":"rpmbuild"},{"location":"software/osg-build-tools/#quilt","text":"Collects the upstream local sources and spec file, then calls quilt setup on the spec file, extracting the source files and adding the patches to a quilt series file. See Quilt documentation (PDF link) for more information on quilt; also look at the example in the Usage Patterns section below. Similar to prepare (in fact, quilt calls rpmbuild -bp behind the scenes), but the source tree is in pre-patch state, and various quilt commands can be used to apply and modify patches. Unpacks into _quilt as of osg-build-1.2.2 or _final_srpm_contents in previous versions. Requires quilt . People on UW CSL machines should add /p/vdt/workspace/quilt/bin to their $PATH , and /p/vdt/workspace/quilt/share/man to their $MANPATH .","title":"quilt"},{"location":"software/osg-build-tools/#options","text":"This section lists the command-line options.","title":"Options"},{"location":"software/osg-build-tools/#-help","text":"Prints the built-in usage information and exits without doing anything else.","title":"--help"},{"location":"software/osg-build-tools/#-version","text":"Prints the version of osg-build and exits without doing anything else.","title":"--version"},{"location":"software/osg-build-tools/#common-options","text":"","title":"Common Options"},{"location":"software/osg-build-tools/#-a-autoclean-no-autoclean","text":"Before each build, clean out the contents of the underscore directories (_build_results, _final_srpm_contents, _upstream_srpm_contents, _upstream_tarball_contents). If the directories are not cleaned up, earlier builds of a package may interfere with later ones. --no-autoclean will disable this. Default is true . Has no effect with the --vcs flag.","title":"-a, --autoclean, --no-autoclean"},{"location":"software/osg-build-tools/#-c-cache-prefix-prefix","text":"Sets the prefix for upstream source cache references. The prefix must be a valid URI starting with either http , https , or file , or one of the following special values: AFS (corresponds to file:///p/vdt/public/html/upstream , which is the location of the VDT cache using AFS from a UW CS machine). VDT (corresponds to http://vdt.cs.wisc.edu/upstream , which is the location of the VDT cache from off-site). AUTO (AFS if available, VDT if not) The upstream source cache must be organized as described above. All files referenced by .source files in the affected packages must exist in the cache, or a runtime error will occur. Default is AUTO . Has no effect with the --vcs flag.","title":"-c, --cache-prefix prefix"},{"location":"software/osg-build-tools/#-el6-el7-redhat-release-version-config-redhat_release","text":"Sets the distro version to build for. This affects the %dist tag, the mock config, and the default koji tag and target (unless otherwise specified). --el6 is equivalent to --redhat-release 6 --el7 is equivalent to --redhat-release 7","title":"--el6, --el7, --redhat-release version (Config: redhat_release)"},{"location":"software/osg-build-tools/#-loglevel-loglevel","text":"Sets the verbosity of the script. Valid values are: debug , info , warning , error and critical . Default is info .","title":"--loglevel loglevel"},{"location":"software/osg-build-tools/#-q-quiet","text":"Do not display as much information. Equivalent to --loglevel warning","title":"-q, --quiet"},{"location":"software/osg-build-tools/#-v-verbose","text":"Display more information. Equivalent to --loglevel debug","title":"-v, --verbose"},{"location":"software/osg-build-tools/#-w-working-directory-path","text":"Use path as the root directory of the files created by the script. For example, if path is $HOME/working , and the package being built is ndt , the following tree will be created: $HOME/working/ndt/_upstream_srpm_contents $HOME/working/ndt/_upstream_tarball_contents $HOME/working/ndt/_final_srpm_contents $HOME/working/ndt/_build_results If path is TEMP , a randomly named directory under /tmp is used as the working directory. The default setting is to use the package directory as the working directory. Has no effect with the --vcs flag.","title":"-w, --working-directory path"},{"location":"software/osg-build-tools/#options-specific-to-prebuild-task","text":"","title":"Options specific to prebuild task"},{"location":"software/osg-build-tools/#-full-extract","text":"If set, all upstream tarballs will be extracted into _upstream_tarball_contents/ during the prebuild step. This flag is now mostly redundant with the prepare and quilt tasks.","title":"--full-extract"},{"location":"software/osg-build-tools/#options-specific-to-rpmbuild-and-mock-tasks","text":"","title":"Options specific to rpmbuild and mock tasks"},{"location":"software/osg-build-tools/#-distro-tag-dist","text":"Sets the distribution tag added on to the end of the release in the RPM ( rpmbuild and mock tasks only ). Default is .osg.el6 or .osg.el7","title":"--distro-tag dist"},{"location":"software/osg-build-tools/#-t-target-arch-arch","text":"Specify an architecture to build packages for ( rpmbuild and mock tasks only ). Default is unspecified, which builds for the current machine architecture.","title":"-t, --target-arch arch"},{"location":"software/osg-build-tools/#options-specific-to-mock-task","text":"","title":"Options specific to mock task"},{"location":"software/osg-build-tools/#-mock-clean-no-mock-clean","text":"Enable/disable deletion of the mock buildroot after a successful build. Default is true .","title":"--mock-clean, --no-mock-clean"},{"location":"software/osg-build-tools/#-m-mock-config-path","text":"Specifies the mock configuration file to use. This file details how to set up the build environment used by mock for the build, including Yum repositories from which to install dependencies and certain predefined variables (e.g., the distribution tag %dist ). See also --mock-config-from-koji .","title":"-m, --mock-config path"},{"location":"software/osg-build-tools/#-mock-config-from-koji-build-tag","text":"Creates a mock config from a Koji build tag. This is the most accurate way to replicate the build environment that Koji will provide (outside of Koji). The build tag is based on the distro version (el6, el7) and the OSG major version (3.3, 3.4). For 3.4 on el6, it is: osg-3.4-el6-build Also requires the Koji command-line tools (package koji ), obtainable from the osg repositories. Since this uses koji, some of the koji-specific options may apply, namely: --koji-backend , --koji-login , and --koji-wrapper .","title":"--mock-config-from-koji build tag"},{"location":"software/osg-build-tools/#options-specific-to-koji-task","text":"","title":"Options specific to koji task"},{"location":"software/osg-build-tools/#-dry-run","text":"Do not actually run koji, merely show the command(s) that will be run. For debugging purposes.","title":"--dry-run"},{"location":"software/osg-build-tools/#-getfiles-get-files","text":"For scratch builds without --vcs only. Download the resulting RPMs and logs from the build into the _build_results directory.","title":"--getfiles, --get-files"},{"location":"software/osg-build-tools/#-k-kojilogin-koji-login-login","text":"Sets the login to use for the koji task. This should most likely be your CN. If not specified, will extract it from your client cert ( ~/.osg-koji/client.crt or ~/.koji/client.crt ).","title":"-k, --kojilogin, --koji-login login"},{"location":"software/osg-build-tools/#-koji-target-target","text":"The koji target to use for building. Default is osg-el6 for el6 and osg-el7 for el7.","title":"--koji-target target"},{"location":"software/osg-build-tools/#-koji-tag-tag","text":"The koji tag to add packages to. See the Koji Workflow guide for more information on the terminology. The special value TARGET uses the destination tag defined in the koji target. Default is osg-el6 or osg-el7 .","title":"--koji-tag tag"},{"location":"software/osg-build-tools/#-ktt-koji-tag-and-target-arg","text":"Shorthand for setting both --koji-tag and --koji-target to arg .","title":"--ktt, --koji-tag-and-target arg"},{"location":"software/osg-build-tools/#-koji-wrapper-no-koji-wrapper","text":"Enable/disable use of the osg-koji wrapper script around koji. See below for a description of osg-koji . Default is true .","title":"--koji-wrapper, --no-koji-wrapper"},{"location":"software/osg-build-tools/#-koji-backend-backend","text":"Specifies the method osg-build will use to interface with Koji. This can be shell or kojilib .","title":"--koji-backend backend"},{"location":"software/osg-build-tools/#-wait-no-wait-nowait","text":"Wait for koji tasks to finish. Bad for running multiple builds in a single command, since you will have to type in your passphrase for the first one, wait for it to complete, then type in your passphrase for the second one, wait for it to complete, etc. If you want to wait for multiple tasks to finish, use the koji watch-task command or look at the website https://koji.opensciencegrid.org . --wait used to be the default until osg-build-1.1.3","title":"--wait, --no-wait, --nowait"},{"location":"software/osg-build-tools/#-regen-repos","text":"Start a regen-repo koji task on the build tag after each koji build, to update the build repository used for the next build. Not useful unless you are launching multiple builds. This enables you to launch builds that depend on each other. Doesn't work too well with --no-wait , since the next build may be started before the regen-repo task is complete. Waiting will keep the next build from being queued until the regen-repo is complete.","title":"--regen-repos"},{"location":"software/osg-build-tools/#-scratch-no-scratch","text":"Perform scratch builds. A scratch build does not go into a repository, but the name-version-release (NVR) of the created RPMs are not considered used, so the build may be modified and repeated without needing a release bump. This has the same use case as the mock task: creating packages that you want to test before releasing. If you do not have a machine with mock set up, or want to test exactly the environment that Koji provides, scratch builds might be more convenient.","title":"--scratch, --no-scratch"},{"location":"software/osg-build-tools/#-vcs-no-vcs-svn-no-svn","text":"Have Koji check the package out from a version control system instead of creating an SRPM on the local machine and submitting that to Koji. Currently, SVN and Git are supported. If this flag is specified, you may use SVN URLs or URL@Revision pairs to specify the packages to build. You may continue specify package directories from an SVN checkout, in which case osg-build will use svn info to find the right URL@Revision pair to use and warn you about uncommitted changes. osg-build will also warn you about an outdated working directory. --vcs defaults to true for non-scratch builds, and false for scratch builds.","title":"--vcs, --no-vcs, --svn, --no-svn"},{"location":"software/osg-build-tools/#-repodestination-repository-upcoming","text":"Selects the repositories (osg-3.3, upcoming, etc.) to build packages for. Currently valid repositories are: Repository Description osg OSG Software development repos for trunk (this is the default) osg-3.3 (or just 3.3) OSG Software development repos for 3.3 branch upcoming OSG Software development repos for upcoming branch internal OSG Software internal branch hcc Holland Computing Center (Nebraska) testing repos --upcoming is an alias for --repo=upcoming Note that the repo selection affects which VCS paths you are allowed to build from. For example, you are not allowed to build from branches/osg-3.3 (from the OSG SVN) into the 'osg' repo, or from HCC's git repositories into the 'upcoming' repo.","title":"--repo=destination repository, --upcoming"},{"location":"software/osg-build-tools/#koji-tag-diff","text":"This script displays the differences between the latest packages in two koji tags. Example invocation: koji-tag-diff osg-3.4-el6-development osg-3.4-el7-testing This prints the packages that are in osg-3.4-el6-development but not in osg-3.4-el7-testing, or vice versa.","title":"koji-tag-diff"},{"location":"software/osg-build-tools/#osg-build-test","text":"This script runs automated tests for osg-build . Only a few tests have been implemented so far.","title":"osg-build-test"},{"location":"software/osg-build-tools/#osg-import-srpm","text":"This is a script to fetch an SRPM from a remote site, copy it into the upstream cache on AFS, and create an SVN package dir (if needed) with an upstream/*.source file. By default it will put downloaded files into the VDT upstream cache (/p/vdt/public/html/upstream), but you can pass --upstream-root=<UPSTREAM DIR> to put them somewhere else. If called with the --extract-spec or -e argument, it will extract the spec file from the SRPM and place it into the osg subdir in SVN. If called with the --diff-spec or -d argument, it will extract the spec file and compare it to the existing spec file in the osg subdir. The script hasn't been touched in a while and needs a good deal of cleanup. A planned feature is to allow doing a three-way diff between the existing RPM before OSG modifications, the new RPM before OSG modifications and the existing RPM after OSG modifications.","title":"osg-import-srpm"},{"location":"software/osg-build-tools/#osg-koji","text":"This is a wrapper script around the koji command line tool. It automatically specifies parameters to access the OSG's koji instance, and forces SSL authentication. It takes the same parameters as koji and passes them on. An additional command, osg-koji setup exists, which performs the following tasks: Create a koji configuration in ~/.osg-koji Create a CA bundle for verifying the server. Use either files in /etc/grid-security/certificates , or (if those are not found), from files downloaded from the DOEGrids and DigiCert sites. Create a client cert file. This can be a symlink to your grid proxy, or it can be a file created from your grid public and private key files. The location of those files can be specified by the --usercert and --userkey arguments. If unspecified, usercert defaults to ~/.globus/usercert.pem , and userkey defaults to ~/.globus/userkey.pem .","title":"osg-koji"},{"location":"software/osg-build-tools/#osg-promote","text":"","title":"osg-promote"},{"location":"software/osg-build-tools/#overview_1","text":"Run this script to push packages from one set of repos to another (e.g. from development to testing), according to the OSG software promotion guidelines. Once the packages are promoted, the script will generate code to cut and paste into a JIRA comment.","title":"Overview"},{"location":"software/osg-build-tools/#synopsis","text":"osg-promote [-r|--route <ROUTE>]... [options] <PACKAGE OR BUILD> [...]","title":"Synopsis"},{"location":"software/osg-build-tools/#examples","text":"Promote the latest build of osg-version to testing for the current release series osg-promote -r testing osg-version Promote the latest builds of osg-ce to testing for the 3.3 and 3.4 release series osg-promote -r 3.3-testing -r 3.4-testing osg-ce Promote osg-build-1.5.0-1 to testing for the current release series osg-promote -r testing osg-build-1.5.0-1","title":"Examples"},{"location":"software/osg-build-tools/#arguments","text":"","title":"Arguments"},{"location":"software/osg-build-tools/#-h","text":"Display help and a list of valid routes.","title":"-h"},{"location":"software/osg-build-tools/#package-or-build","text":"A package (e.g. osg-version ) or build (e.g. osg-version-3.3.0-1.osg33.el6 ) to promote. You may omit the dist tag (the .osg33.el6 part). If a package is specified, the most recent version of that package will be promoted. If a build is specified, that build and the build that has the same version - release for the other distro version(s) will be promoted. That is, if you specify the route 3.3-testing and the build foo-1-1 , then foo-1-1.osg33.el6 and foo-1-1.osg33.el7 will be promoted. This may be specified multiple times, to promote multiple packages. The NVRs of each set of builds for a package must match.","title":"package or build"},{"location":"software/osg-build-tools/#-r-route-route-route","text":"The promotion route to use. Use osg-promote -h to get a list of valid routes. This may be specified multiple times. For example, to promote for both 3.4 and 3.3, pass -r 3.4-testing -r 3.3-testing . If not specified, the testing route is used, which corresponds to the testing route for the latest release series.","title":"-r ROUTE, --route ROUTE"},{"location":"software/osg-build-tools/#-n-dry-run","text":"Do not promote, just show what would be done.","title":"-n, --dry-run"},{"location":"software/osg-build-tools/#-el6-only-el7-only","text":"Only promote packages for el6 / el7.","title":"--el6-only / --el7-only"},{"location":"software/osg-build-tools/#-no-el6-no-el7","text":"Do not promote packages for el6 / el7.","title":"--no-el6 / --no-el7"},{"location":"software/osg-build-tools/#-ignore-rejects","text":"Ignore rejections due to version mismatch between dvers or missing package for one dver.","title":"--ignore-rejects"},{"location":"software/osg-build-tools/#-regen","text":"Regenerate the destination repos after promoting.","title":"--regen"},{"location":"software/osg-build-tools/#-y-assume-yes","text":"Do not prompt before promotion.","title":"-y, --assume-yes"},{"location":"software/osg-build-tools/#common-usage-patterns","text":"","title":"Common Usage Patterns"},{"location":"software/osg-build-tools/#verify-that-all-files-necessary-to-build-the-package-are-in-the-right-place","text":"Run osg-build prebuild <PACKAGEDIR> .","title":"Verify that all files necessary to build the package are in the right place"},{"location":"software/osg-build-tools/#fetch-and-extract-all-source-files-for-examination","text":"Run osg-build prebuild --full-extract <PACKAGEDIR> . Look inside the _upstream_tarball_contents directory.","title":"Fetch and extract all source files for examination"},{"location":"software/osg-build-tools/#get-a-post-patch-version-of-the-upstream-sources-for-examination","text":"Run osg-build prepare <PACKAGEDIR> . Look inside the _build_results directory.","title":"Get a post-patch version of the upstream sources for examination"},{"location":"software/osg-build-tools/#see-which-patches-work-with-a-new-version-of-a-package-update-or-remove-them","text":"Place the new source tarball into the upstream cache, edit the version in the spec file and *.sources files as necessary Run osg-build quilt <PACKAGEDIR> . Enter the extracted sources inside the _final_srpm_contents directory. You should see a file called series and a symlink called patches . Type quilt series to get a list of patches in order of application. Type quilt push to apply the next patch. If the patch applies cleanly, continue. If the patch applies with some fuzz, type quilt refresh to update the offsets in the patch. If the patch does not apply and you wish to remove it, type quilt delete <PATCH NAME> (delete only removes it from the series file, not the disk) If the patch does not apply and you wish to fix it, either type quilt push -f to interactively apply the patch, or quilt delete <PATCH NAME> the patch and use quilt new / quilt edit / quilt refresh to edit files and make a new patch from your changes. Consult the quilt(1) manpage for more info. If you have a new patch, run quilt import <PATCHFILE> to add the patch to the series file, and run quilt push to apply it. If you have changes to make to the source code that you want to save as a patch, type quilt new <PATCHNAME> , edit the files, type quilt add <FILE> on each file you edited, then type quilt refresh to recreate the patch. Once you're all done, copy the patches in the patches/ directory to the osg/ dir in SVN, run quilt series to get the application order and update the spec file accordingly.","title":"See which patches work with a new version of a package, update or remove them"},{"location":"software/osg-build-tools/#see-if-a-package-builds-successfully-for-osg-34","text":"If you have all the build dependencies of the package installed, run osg-build rpmbuild <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have all the build dependencies installed, or want to make sure you specified all of the necessary ones and the package builds from a clean environment, run osg-build mock --mock-config-from-koji osg-3.4-el6-build <PACKAGEDIR> . The resulting RPMs will be in the _build_results directory. If you do not have mock installed, or want to exactly replicate the build environment in Koji, run osg-build koji --scratch <PACKAGEDIR> . You may download the resulting RPMs from kojiweb https://koji.opensciencegrid.org/koji or pass --getfiles to osg-build koji and they will get downloaded to the _build_results directory.","title":"See if a package builds successfully for OSG 3.4"},{"location":"software/osg-build-tools/#check-for-potential-errors-in-a-package","text":"Run osg-build lint <PACKAGEDIR> .","title":"Check for potential errors in a package"},{"location":"software/osg-build-tools/#create-and-test-a-final-build-of-a-package-for-all-platforms-for-upcoming","text":"svn commit your changes in branches/upcoming . Type osg-build koji --repo=upcoming <PACKAGEDIR> Wait for the osg-upcoming-minefield repos to be regenerated containing the new version of your package. You can run osg-koji wait-repo osg-upcoming-el<X>-development --build=<PACKAGENAME-VERSION-RELEASE> and wait for that process to finish (substitute 6 or 7 for X ). Or, you can just check kojiweb https://koji.opensciencegrid.org/koji/tasks . On your test machine, make sure the osg-upcoming-minefield repo is enabled (edit /etc/yum.repos.d/osg-upcoming-minefield.repo or /etc/yum.repos.d/osg-el6-upcoming-minefield.repo ). Clean your cache ( yum clean all; yum clean expire-cache ). Install your software, see if it works.","title":"Create and test a final build of a package for all platforms for upcoming"},{"location":"software/osg-build-tools/#promote-the-latest-build-of-a-package-to-testing-for-the-current-osg-release-series","text":"Run osg-promote -r testing <PACKAGE>","title":"Promote the latest build of a package to testing for the current OSG release series"},{"location":"software/osg-build-tools/#promote-the-latest-build-of-a-package-to-testing-for-the-33-and-34-release-series","text":"Run osg-promote -r 3.3-testing -r 3.4-testing <PACKAGE>","title":"Promote the latest build of a package to testing for the 3.3 and 3.4 release series"},{"location":"software/ospool-containers/","text":"Containers in the OSPool \u00b6 Tim C. started this document in February 2023 to remember things from hallway discussions. If the scope of this page broadens, be sure to update the title and/or this description. Slot Ad Attributes for Containers \u00b6 There are two seemingly similar Slot Ad attributes in the OSPool related to Singularity: HasSingularity is an HTCondor attribute that indicates whether jobs can run within Singularity containers. It is set to true based on a test that HTCondor performs at start-up, although subsequent container invocations could revoke the value upon certain failure conditions. HAS_SINGULARITY is an OSG pool attribute that indicates whether user payload jobs can and will run within Singularity containers. Only Singularity container runtimes are supported. It is set to true based on a test that is run in the pilot scripts. Note that the test is also baked into the OSPool Backfill Containers. The pilot-script test checks more conditions than the HTCondor HasSingularity one. Periodic scripts in the pilot (i.e., STARTD_CRON ) retest some of these conditions; thus, HAS_SINGULARITY may start out true but become false later in the pilot\u2019s lifetime. When an OSPool job asks to run inside a container, requirements are set to check that both HasSingularity and HAS_SINGULARITY are true for any matching Slot Ad. Containers and Pilots \u00b6 Obviously, Backfill Container \u201cpilots\u201d run inside a container runtime, although the specific choice of container runtime technology is up to the site. Within a GlideinWMS pilot, the pilot scripts determine whether a functioning Singularity container is available, which could come from a local install on each Execution Point or from CVMFS. If detected, then HAS_SINGULARITY is set to true and all user payloads will be run in containers. (It is possible to override this behavior through site-specific pilot hackery.) For Backfill Containers, the container itself includes an installation of Apptainer (n\u00e9e Singularity) and it will always be used (in unprivileged mode) instead of any system or other installation. The user job is a vanilla job. Today, though, a pilot runs the \u201cuser job wrapper\u201d script, which is a replacement for the user\u2019s executable that does some stuff and then runs the user\u2019s executable. If the HAS_SINGULARITY attribute is true in the environment of the wrapper, then it runs the actual user payload job in Singularity (or Apptainer). PID Namespaces \u00b6 PID namespaces are a key technology that enables containers to isolate from each other. See, for example, this Ubuntu copy of the man page for pid_namespaces . The root user always has the ability to create PID namespaces, so a privileged container runtime (i.e., not unprivileged Singularity) can always do this. There is a special feature for user PID namespaces , which can be created by unprivileged processes. To work, there is a certain kernel setting that must be set, and then user PID namespaces are available to all. Today, when the GlideinWMS user job wrapper is about to start a user payload job in a Singularity container, the default is to pass a flag to Singularity to use user PID namespaces. However, if user PID namespaces are not available (say, due to the kernel setting), the pilot start-up scripts do not detect this condition automatically. So, there is a special envirnoment variable that can be set on the outer container (e.g., the Backfill Container) to disable this flag: SINGULARITY_DISABLE_PID_NAMESPACES=1 While set on the outer container, it affects only the user job wrapper and how it invokes the inner Singularity container. Mat says that HTCondor 10.2.2 has a feature to detect the lack of user PID namespaces and, in such a case, to avoid using them, but it is not clear that that feature will help anything as long as the GlideinWMS user job wrapper is being used. Containers and GPUs \u00b6 Most, but certainly not all, OSPool payload jobs that request GPUs also request to run within a container. This is probably due to GPU-using software stacks often being complex, and so users often turn to containers for their runtime environment, including ones that we and others pre-build. Note that the Backfill Container images themselves do not include the NVIDIA CUDA drivers (although, we are experimenting with that). Instead, the CUDA drivers that are installed on the host system are mounted inside the running Backfill Container. This scheme, which works at most OSPool sites, allows GPU payload jobs to work without specifically requesting a container, although see above for why many do so anyway.","title":"OSPool Containers"},{"location":"software/ospool-containers/#containers-in-the-ospool","text":"Tim C. started this document in February 2023 to remember things from hallway discussions. If the scope of this page broadens, be sure to update the title and/or this description.","title":"Containers in the OSPool"},{"location":"software/ospool-containers/#slot-ad-attributes-for-containers","text":"There are two seemingly similar Slot Ad attributes in the OSPool related to Singularity: HasSingularity is an HTCondor attribute that indicates whether jobs can run within Singularity containers. It is set to true based on a test that HTCondor performs at start-up, although subsequent container invocations could revoke the value upon certain failure conditions. HAS_SINGULARITY is an OSG pool attribute that indicates whether user payload jobs can and will run within Singularity containers. Only Singularity container runtimes are supported. It is set to true based on a test that is run in the pilot scripts. Note that the test is also baked into the OSPool Backfill Containers. The pilot-script test checks more conditions than the HTCondor HasSingularity one. Periodic scripts in the pilot (i.e., STARTD_CRON ) retest some of these conditions; thus, HAS_SINGULARITY may start out true but become false later in the pilot\u2019s lifetime. When an OSPool job asks to run inside a container, requirements are set to check that both HasSingularity and HAS_SINGULARITY are true for any matching Slot Ad.","title":"Slot Ad Attributes for Containers"},{"location":"software/ospool-containers/#containers-and-pilots","text":"Obviously, Backfill Container \u201cpilots\u201d run inside a container runtime, although the specific choice of container runtime technology is up to the site. Within a GlideinWMS pilot, the pilot scripts determine whether a functioning Singularity container is available, which could come from a local install on each Execution Point or from CVMFS. If detected, then HAS_SINGULARITY is set to true and all user payloads will be run in containers. (It is possible to override this behavior through site-specific pilot hackery.) For Backfill Containers, the container itself includes an installation of Apptainer (n\u00e9e Singularity) and it will always be used (in unprivileged mode) instead of any system or other installation. The user job is a vanilla job. Today, though, a pilot runs the \u201cuser job wrapper\u201d script, which is a replacement for the user\u2019s executable that does some stuff and then runs the user\u2019s executable. If the HAS_SINGULARITY attribute is true in the environment of the wrapper, then it runs the actual user payload job in Singularity (or Apptainer).","title":"Containers and Pilots"},{"location":"software/ospool-containers/#pid-namespaces","text":"PID namespaces are a key technology that enables containers to isolate from each other. See, for example, this Ubuntu copy of the man page for pid_namespaces . The root user always has the ability to create PID namespaces, so a privileged container runtime (i.e., not unprivileged Singularity) can always do this. There is a special feature for user PID namespaces , which can be created by unprivileged processes. To work, there is a certain kernel setting that must be set, and then user PID namespaces are available to all. Today, when the GlideinWMS user job wrapper is about to start a user payload job in a Singularity container, the default is to pass a flag to Singularity to use user PID namespaces. However, if user PID namespaces are not available (say, due to the kernel setting), the pilot start-up scripts do not detect this condition automatically. So, there is a special envirnoment variable that can be set on the outer container (e.g., the Backfill Container) to disable this flag: SINGULARITY_DISABLE_PID_NAMESPACES=1 While set on the outer container, it affects only the user job wrapper and how it invokes the inner Singularity container. Mat says that HTCondor 10.2.2 has a feature to detect the lack of user PID namespaces and, in such a case, to avoid using them, but it is not clear that that feature will help anything as long as the GlideinWMS user job wrapper is being used.","title":"PID Namespaces"},{"location":"software/ospool-containers/#containers-and-gpus","text":"Most, but certainly not all, OSPool payload jobs that request GPUs also request to run within a container. This is probably due to GPU-using software stacks often being complex, and so users often turn to containers for their runtime environment, including ones that we and others pre-build. Note that the Backfill Container images themselves do not include the NVIDIA CUDA drivers (although, we are experimenting with that). Instead, the CUDA drivers that are installed on the host system are mounted inside the running Backfill Container. This scheme, which works at most OSPool sites, allows GPU payload jobs to work without specifically requesting a container, although see above for why many do so anyway.","title":"Containers and GPUs"},{"location":"software/quilt/","text":"How to Write a Patch \u00b6 You create one or more .patch files with diff and stick them in the osg directory. Then you declare the patch files in the header of the spec file with a line like Patch0: py24compat.patch and in the %prep section, just after %setup , you add a %patch line to actually apply the patch, like this: %patch0 -p1 (where the -p1 indicates that it should strip off the first leading component of the path in each file mentioned in the .patch file) Look at the mash package for an example. The easiest way to actually create the patch in the first place is to use a utility called quilt. First you run osg-build quilt on the package directory and it will create a _quilt subdirectory that has the expanded sources and patches. cd into _quilt/pegasus-source-2.3.0 , then run quilt push -a to apply any patches that already exist (there are none for pegasus but there might be for other packages). run quilt new py24compat.patch to name your new patch file. run quilt add <filename> for each file you want to make changes to (you must run this before making any changes). actually make the changes. run quilt refresh -p1 to have quilt add those changes into the .patch file. (The -p1 option to quilt refresh must be the same as the -p1 option to %patch0 in your spec file). copy patches/py24compat.patch into the pegasus/osg directory and edit the spec file as above. Don't forget to git add your new patch file before committing. Once you've tested your patch successfully, you should make that bug report and send them the patch. A bug report is looked on more favorably if it includes a patch to fix the problem.","title":"Using Quilt"},{"location":"software/quilt/#how-to-write-a-patch","text":"You create one or more .patch files with diff and stick them in the osg directory. Then you declare the patch files in the header of the spec file with a line like Patch0: py24compat.patch and in the %prep section, just after %setup , you add a %patch line to actually apply the patch, like this: %patch0 -p1 (where the -p1 indicates that it should strip off the first leading component of the path in each file mentioned in the .patch file) Look at the mash package for an example. The easiest way to actually create the patch in the first place is to use a utility called quilt. First you run osg-build quilt on the package directory and it will create a _quilt subdirectory that has the expanded sources and patches. cd into _quilt/pegasus-source-2.3.0 , then run quilt push -a to apply any patches that already exist (there are none for pegasus but there might be for other packages). run quilt new py24compat.patch to name your new patch file. run quilt add <filename> for each file you want to make changes to (you must run this before making any changes). actually make the changes. run quilt refresh -p1 to have quilt add those changes into the .patch file. (The -p1 option to quilt refresh must be the same as the -p1 option to %patch0 in your spec file). copy patches/py24compat.patch into the pegasus/osg directory and edit the spec file as above. Don't forget to git add your new patch file before committing. Once you've tested your patch successfully, you should make that bug report and send them the patch. A bug report is looked on more favorably if it includes a patch to fix the problem.","title":"How to Write a Patch"},{"location":"software/release-planning/","text":"Plans for Future Releases \u00b6 This informal page is the mapping of \"technology goals\" (e.g., \"release software Foo version X\") to release numbers. It is meant to be updated as the releases evolve (and items are moved back in schedule). For package support policy between release series, see this page . Unless explicitly noted, bullet points refer to software in the release repo. This page is not meant to track minor bugfixes or updates -- rather, its focus should be new features. OSG 3.4 (May 2017) \u00b6 Package(s) Change in osg-release Notes BeStMan2 Drop Retirement policy edg-mkgridmap Drop SOFTWARE-2600 frontier-squid Modify Version 3 glexec Drop SOFTWARE-2620 GRAM Drop SOFTWARE-2530 GUMS Drop Retirement policy , SOFTWARE-2600 jglobus Drop SOFTWARE-2606 netlogger Drop osg-ce Modify Drop GridFTP , gums-client osg-info-services Drop osg-version Drop singularity Add voms-admin-server Drop Retirement policy Track OSG 3.4 updates through its JIRA epic . Support Policy for OSG 3.3 \u00b6 According to our release support policy and the release date of May 2017 for OSG 3.4, OSG 3.3 will receive routine software updates until November 2017 and critical updates until May 2018. Previous Releases \u00b6 12 November 2013 \u00b6 OSG 3.1 HTCondor-CE with PBS osg-configure emits an ERROR if squid defaults are not changed (\"UNAVAILABLE\" is a valid change) OSG 3.2 Initial release HDFS 2.0.0 (already done in Upcoming) HTCondor 8.0.4 glideinWMS 3.2.0 osg-info-services (Note: ReSS will likely be retired around year-end) OSG 3.1 updates Upcoming HTCondor 8.1 with unified RPM BOSCO 10 December 2013 \u00b6 OSG 3.2 RSV-for-VOs Squid must be present on OSG-CE (??? what does this mean?)","title":"Release Planning"},{"location":"software/release-planning/#plans-for-future-releases","text":"This informal page is the mapping of \"technology goals\" (e.g., \"release software Foo version X\") to release numbers. It is meant to be updated as the releases evolve (and items are moved back in schedule). For package support policy between release series, see this page . Unless explicitly noted, bullet points refer to software in the release repo. This page is not meant to track minor bugfixes or updates -- rather, its focus should be new features.","title":"Plans for Future Releases"},{"location":"software/release-planning/#osg-34-may-2017","text":"Package(s) Change in osg-release Notes BeStMan2 Drop Retirement policy edg-mkgridmap Drop SOFTWARE-2600 frontier-squid Modify Version 3 glexec Drop SOFTWARE-2620 GRAM Drop SOFTWARE-2530 GUMS Drop Retirement policy , SOFTWARE-2600 jglobus Drop SOFTWARE-2606 netlogger Drop osg-ce Modify Drop GridFTP , gums-client osg-info-services Drop osg-version Drop singularity Add voms-admin-server Drop Retirement policy Track OSG 3.4 updates through its JIRA epic .","title":"OSG 3.4 (May 2017)"},{"location":"software/release-planning/#support-policy-for-osg-33","text":"According to our release support policy and the release date of May 2017 for OSG 3.4, OSG 3.3 will receive routine software updates until November 2017 and critical updates until May 2018.","title":"Support Policy for OSG 3.3"},{"location":"software/release-planning/#previous-releases","text":"","title":"Previous Releases"},{"location":"software/release-planning/#12-november-2013","text":"OSG 3.1 HTCondor-CE with PBS osg-configure emits an ERROR if squid defaults are not changed (\"UNAVAILABLE\" is a valid change) OSG 3.2 Initial release HDFS 2.0.0 (already done in Upcoming) HTCondor 8.0.4 glideinWMS 3.2.0 osg-info-services (Note: ReSS will likely be retired around year-end) OSG 3.1 updates Upcoming HTCondor 8.1 with unified RPM BOSCO","title":"12 November 2013"},{"location":"software/release-planning/#10-december-2013","text":"OSG 3.2 RSV-for-VOs Squid must be present on OSG-CE (??? what does this mean?)","title":"10 December 2013"},{"location":"software/repository-management/","text":"Repository Management \u00b6 This document attempts to record everything there is to know about repository management for the OSG. Public repositories \u00b6 We host four public-facing repositories at repo.opensciencegrid.org : development : This repository is the bleeding edge. Installing from this repository may cause the host to stop functioning, and we will not assist in undoing any damage. testing : This repository contains software ready for testing. If you install packages from here, they may be buggy, but we will provide limited assistance in providing a migration path to a fixed verison. release : This repository contains software that we are willing to support and can be used by the general community. contrib : RPMs contributed from outside the OSG. These repos are updated by the mash script running on repo.opensciencegrid.org . Internal repositories \u00b6 In addition to the public repositories above, we host two repositories on koji.opensciencegrid.org . These are updated shortly after jobs are built into them or tagged into them. They are technically publicly accessible, but we discourage the public from using them. minefield : This repository is a copy of development above. prerelease : This repository is a staging area for software that is slated to be in the next release. These repos are updated by the kojira daemon running on koji.opensciencegrid.org . Build repositories \u00b6 Warning this section is out of date; the tags it references no longer exist. The koji task in osg-build uses the osg-3.4-el6-build/osg-3.4-el7-build repo, which is the union of the following repositories: Minefield a.k.a. osg-3.4-el6-development / osg-3.4-el7-development The osg-el6-internal / osg-el7-internal tag (containing build dependencies we do not want to make public) The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist) CentOS and EPEL Koji will work from its internal cache of the above repositories (downloading the packages from the source), and will not update until the build repository is regenerated. By default, Koji does a groupinstall of the build group, then resolves the BuildRequires dependencies. The tarball creation scripts use the osg-3.4-el6-release-build / osg-3.4-el7-release-build repo, which is the union of the following repositories: Release a.k.a. osg-3.4-el6-release / osg-3.4-el7-release The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist ) CentOS and EPEL","title":"Repository Management"},{"location":"software/repository-management/#repository-management","text":"This document attempts to record everything there is to know about repository management for the OSG.","title":"Repository Management"},{"location":"software/repository-management/#public-repositories","text":"We host four public-facing repositories at repo.opensciencegrid.org : development : This repository is the bleeding edge. Installing from this repository may cause the host to stop functioning, and we will not assist in undoing any damage. testing : This repository contains software ready for testing. If you install packages from here, they may be buggy, but we will provide limited assistance in providing a migration path to a fixed verison. release : This repository contains software that we are willing to support and can be used by the general community. contrib : RPMs contributed from outside the OSG. These repos are updated by the mash script running on repo.opensciencegrid.org .","title":"Public repositories"},{"location":"software/repository-management/#internal-repositories","text":"In addition to the public repositories above, we host two repositories on koji.opensciencegrid.org . These are updated shortly after jobs are built into them or tagged into them. They are technically publicly accessible, but we discourage the public from using them. minefield : This repository is a copy of development above. prerelease : This repository is a staging area for software that is slated to be in the next release. These repos are updated by the kojira daemon running on koji.opensciencegrid.org .","title":"Internal repositories"},{"location":"software/repository-management/#build-repositories","text":"Warning this section is out of date; the tags it references no longer exist. The koji task in osg-build uses the osg-3.4-el6-build/osg-3.4-el7-build repo, which is the union of the following repositories: Minefield a.k.a. osg-3.4-el6-development / osg-3.4-el7-development The osg-el6-internal / osg-el7-internal tag (containing build dependencies we do not want to make public) The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist) CentOS and EPEL Koji will work from its internal cache of the above repositories (downloading the packages from the source), and will not update until the build repository is regenerated. By default, Koji does a groupinstall of the build group, then resolves the BuildRequires dependencies. The tarball creation scripts use the osg-3.4-el6-release-build / osg-3.4-el7-release-build repo, which is the union of the following repositories: Release a.k.a. osg-3.4-el6-release / osg-3.4-el7-release The dist-el6-build / dist-el7-build tag (consisting of the appropriate macros for %dist ) CentOS and EPEL","title":"Build repositories"},{"location":"software/requesting-tokens/","text":"How to Request Tokens \u00b6 As part of the GridFTP and GSI migration , the OSG will be transitioning authentication away from X.509 certificates to the use of bearer tokens such as SciTokens or WLCG JWT . This document is intended as a guide for OSG developers for requesting tokens necessary for software development. Before Starting \u00b6 Before you can request the appropriate tokens, you must have the following: A WLCG INDIGO IAM account belonging to the wlcg , wlcg/pilots , and wlcg/xfers groups. One of the following: The ability to run containers through tools like docker or podman An installation of oidc-agent available as an RPM from the OSG repositories Requesting Tokens Using a Container \u00b6 oidc-agent is a process that runs in the background that can request access and refresh tokens from OpenID Connect token providers. Registering an OIDC profile \u00b6 Start an agent container in the background and name it my-agent to easily run subsequent commands against it: docker run -d --name my-agent opensciencegrid/oidc-agent:3.6-release Generate a local client profile and follow the prompts: docker exec -it my-agent oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read storage.read:/ XRootD write storage.modify:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions. Requesting access tokens \u00b6 Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : docker exec -it my-agent oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client. Reloading an OIDC profile \u00b6 Note Required after restarting the running container. You must have an existing registered profile . If your existing container is not already running, start it: docker start my-agent Reload profile: docker exec -it my-agent oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration. Requesting Tokens with an RPM installation \u00b6 Registering an OIDC profile \u00b6 Start the agent and add the appropriate variables to your environment: eval `oidc-agent` Generate a local client profile and follow the prompts: oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read read:/ XRootD write write:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions. Requesting access tokens \u00b6 Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client. Reloading an OIDC profile \u00b6 Note Required if you log out of the running machine. You must have an existing registered profile . If you do not already have a running 'oidc-agent', start one: eval 'oidc-agent' Reload profile: oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration. Troubleshooting Tokens \u00b6 You can inspect the payload by copy-pasting the token into the \"Encoded\" text box here: http://jwt.io/ . Mouse over the fields and values for details.","title":"How to Request Tokens"},{"location":"software/requesting-tokens/#how-to-request-tokens","text":"As part of the GridFTP and GSI migration , the OSG will be transitioning authentication away from X.509 certificates to the use of bearer tokens such as SciTokens or WLCG JWT . This document is intended as a guide for OSG developers for requesting tokens necessary for software development.","title":"How to Request Tokens"},{"location":"software/requesting-tokens/#before-starting","text":"Before you can request the appropriate tokens, you must have the following: A WLCG INDIGO IAM account belonging to the wlcg , wlcg/pilots , and wlcg/xfers groups. One of the following: The ability to run containers through tools like docker or podman An installation of oidc-agent available as an RPM from the OSG repositories","title":"Before Starting"},{"location":"software/requesting-tokens/#requesting-tokens-using-a-container","text":"oidc-agent is a process that runs in the background that can request access and refresh tokens from OpenID Connect token providers.","title":"Requesting Tokens Using a Container"},{"location":"software/requesting-tokens/#registering-an-oidc-profile","text":"Start an agent container in the background and name it my-agent to easily run subsequent commands against it: docker run -d --name my-agent opensciencegrid/oidc-agent:3.6-release Generate a local client profile and follow the prompts: docker exec -it my-agent oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read storage.read:/ XRootD write storage.modify:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions.","title":"Registering an OIDC profile"},{"location":"software/requesting-tokens/#requesting-access-tokens","text":"Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : docker exec -it my-agent oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client.","title":"Requesting access tokens"},{"location":"software/requesting-tokens/#reloading-an-oidc-profile","text":"Note Required after restarting the running container. You must have an existing registered profile . If your existing container is not already running, start it: docker start my-agent Reload profile: docker exec -it my-agent oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration.","title":"Reloading an OIDC profile"},{"location":"software/requesting-tokens/#requesting-tokens-with-an-rpm-installation","text":"","title":"Requesting Tokens with an RPM installation"},{"location":"software/requesting-tokens/#registering-an-oidc-profile_1","text":"Start the agent and add the appropriate variables to your environment: eval `oidc-agent` Generate a local client profile and follow the prompts: oidc-gen -w device <CLIENT PROFILE> Specify the WLCG INDIGO IAM instance as the client issuer: Issuer [https://iam-test.indigo-datacloud.eu/]: https://wlcg.cloud.cnaf.infn.it/ Request wlcg , offline_access , and other scopes for the capabilities that you need: Capability Scope HTCondor READ compute.read HTCondor WRITE compute.modify compute.cancel compute.create XRootD read read:/ XRootD write write:/ For example, to request HTCondor READ and WRITE access, specify the following scopes: This issuer supports the following scopes: openid profile email address phone offline_access wlcg iam wlcg.groups Space delimited list of scopes or 'max' [openid profile offline_access]: wlcg offline_access compute.read compute.modify compute.cancel compute.create Note that, prior to HTCondor 8.9.7, the server also needed condor:/ALLOW in all cases. When prompted, open https://wlcg.cloud.cnaf.infn.it/device in a browser, enter the code provided by oidc-gen , and click \"Submit\". On the next page, verify the scopes and client profile name, and click \"Authorize\". Enter a password to encrypt your local client profile. You'll need to remember this if you want to re-use this profile in subsequent sessions.","title":"Registering an OIDC profile"},{"location":"software/requesting-tokens/#requesting-access-tokens_1","text":"Note You must first register a new profile . Request a token using the client profile that you used with oidc-gen : oidc-token --aud=\"<SERVER AUDIENCE>\" <CLIENT PROFILE> For tokens used against an HTCondor-CE, set <SERVER AUDIENCE> to <CE FQDN>:<CE PORT> . Copy the output of oidc-token into a file on the host where you need SciToken authentication, e.g. an HTCondor or XRootD client.","title":"Requesting access tokens"},{"location":"software/requesting-tokens/#reloading-an-oidc-profile_1","text":"Note Required if you log out of the running machine. You must have an existing registered profile . If you do not already have a running 'oidc-agent', start one: eval 'oidc-agent' Reload profile: oidc-add <CLIENT PROFILE> Enter password used to encrypt your <CLIENT PROFILE> created during profile registration.","title":"Reloading an OIDC profile"},{"location":"software/requesting-tokens/#troubleshooting-tokens","text":"You can inspect the payload by copy-pasting the token into the \"Encoded\" text box here: http://jwt.io/ . Mouse over the fields and values for details.","title":"Troubleshooting Tokens"},{"location":"software/resurrecting-epel-packages/","text":"Resurrecting EPEL RPMs \u00b6 You will need to be a Koji admin to do these steps. [user@client ~] $ osg-koji --list-permissions --mine Will tell you if you're an admin or not. Current Koji admins are the Madison team and Brian Bockelman. EPEL version EPEL Koji tag Our Koji tag 5 dist-5E-epel epelrescue-el5 6 dist-6E-epel epelrescue-el6 7 epel7 epelrescue-el7 Determine the NVR of the build containing the RPM of the package you want. Use the Fedora/EPEL Koji web interface ( https://koji.fedoraproject.org ) to search for it. You can use the search box in the upper right to look for packages, builds, or RPMs; it accepts shell wildcards. EPEL builds have .el5, .el6, or .el7 in the dist tag. Download all RPMs for all architectures we care about (i386, i486, i586, i686, x86_64, noarch), including the .src.rpm and the debuginfo rpms. You have three options for the downloads: Use the links in the web interface Use the koji command-line interface against the Fedora koji: Download fedora-koji.conf , attached to this page Run koji --noauth -c fedora-koji.conf download-build --debuginfo <PACKAGE_NVR> Delete RPMs for architectures we do not care about (see list above) <PACKAGE_NVR> is the Name-Version-Release information about the build, which was determined in the step 1 above Dig around in https://kojipkgs.fedoraproject.org/packages/ On your development machine: Important: Verify that all of the RPMs are signed: [root@client ~] # rpm -K *.rpm | grep -iv gpg should be empty If not, STOP and sign them using the OSG RPM key -- talk to Mat Import the RPMs themselves into the Koji system [user@client ~] $ osg-koji import <RPM_DIRECTORY>/*.rpm Where <RPM_DIRECTORY> is the directory where you have downloaded the rpms. They will not be in any tags at this point Add the package to the whitelist for our koji tag: [user@client ~] $ osg-koji add-pkg <OUR_KOJI_TAG> <PACKAGE> --owner = \"<YOUR_KOJI_USERNAME>\" Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page, an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 and <YOUR_KOJI_USERNAME> is the username you use to interact with the Koji system Actually tag the builds: [user@client ~] $ osg-koji tag-pkg <OUR_KOJI_TAG> <PACKAGE> Check the Tasks tab in Koji to see if kojira has started regening the repos -- it might take a few minutes to kick in. If it doesn't, do it manually (if you're doing multiple packages, save this step until you're done with all of them): for repo in osg-{3.1,3.2,3.3,upcoming}-el5-{build,development,testing,release,prerelease,release-build}; do osg-koji regen-repo --nowait $repo done Make a test VM and install the package from minefield to test that it is actually present. Update the epelrescue RPMs table below Removing resurrected RPMs \u00b6 In case the RPM appeared back in EPEL, or we no longer need it, here's how to remove it from the epelrescue tags so we're not overriding the EPEL version: Find out the NVR of the build: [user@client ~] $ osg-koji list-tagged <OUR_KOJI_TAG> <PACKAGE> Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page and an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 Untag the packages: [user@client ~] $ osg-koji untag-pkg <OUR_KOJI_TAG> <PACKAGE> Why you should not use block-pkg \u00b6 EPEL removes their packages by using 'koji block-pkg', which leaves the package and the builds in the tag, but prevents it from appearing in the repos. We cannot do that, because blocks are inherited and this will mess up our build repos. This is what happened in one case: EPEL removed rpmdevtools, which is a necessary package for all builds. I resurrected it into epelrescue-el5. Later, EPEL put rpmdevtools back into their repos, so it no longer needed to be in epelrescue-el5. I used block-pkg on rpmdevtools in epelrescue-el5, thinking that the package could remain tagged, but will stay out of our repos, and the EPEL package would be used instead. The block not only hid our rpmdevtools, it hid EPEL's rpmdevtools as well, preventing us from being able to build. I unblocked the rpmdevtools, and just untagged the build instead, regenerated our build repos, and we could build again. Policy for epelrescue tags \u00b6 https://jira.opensciencegrid.org/browse/SOFTWARE-2046 Table of epelrescue RPMs \u00b6 Package Distro version Date added Reason added Date removed python-six-1.7.3-1.el6 6 2015-08-12 Dep of osg-build (via mock) 2015-10-14 python-argparse-1.2.1-2.el6 6 2015-09-23 Dep of osg-wn-client (via gfal2) 2015-10-14 python-backports-ssl_match_hostname-3.4.0.2-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-requests-1.1.0-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-urllib3-1.5-7.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 Finding out if a package is still needed in epelrescue \u00b6 Set $pkg to the name of a package to test (e.g. python-six ), and $rhel set to the RHEL version you're testing for (e.g. 5 , 6 , or 7 ). Using Carl's centos-srpms , scientific-srpms , slf-srpms scripts: for script in centos-srpms scientific-srpms slf-srpms; do echo -n $script \": \" $script -$rhel $pkg | grep . || echo none done A dry run of removing the package: osg-koji untag-pkg -n --all epelrescue-el$rhel $pkg Remove the -n when the output of that looks fine.","title":"Resurrecting Epel Packages"},{"location":"software/resurrecting-epel-packages/#resurrecting-epel-rpms","text":"You will need to be a Koji admin to do these steps. [user@client ~] $ osg-koji --list-permissions --mine Will tell you if you're an admin or not. Current Koji admins are the Madison team and Brian Bockelman. EPEL version EPEL Koji tag Our Koji tag 5 dist-5E-epel epelrescue-el5 6 dist-6E-epel epelrescue-el6 7 epel7 epelrescue-el7 Determine the NVR of the build containing the RPM of the package you want. Use the Fedora/EPEL Koji web interface ( https://koji.fedoraproject.org ) to search for it. You can use the search box in the upper right to look for packages, builds, or RPMs; it accepts shell wildcards. EPEL builds have .el5, .el6, or .el7 in the dist tag. Download all RPMs for all architectures we care about (i386, i486, i586, i686, x86_64, noarch), including the .src.rpm and the debuginfo rpms. You have three options for the downloads: Use the links in the web interface Use the koji command-line interface against the Fedora koji: Download fedora-koji.conf , attached to this page Run koji --noauth -c fedora-koji.conf download-build --debuginfo <PACKAGE_NVR> Delete RPMs for architectures we do not care about (see list above) <PACKAGE_NVR> is the Name-Version-Release information about the build, which was determined in the step 1 above Dig around in https://kojipkgs.fedoraproject.org/packages/ On your development machine: Important: Verify that all of the RPMs are signed: [root@client ~] # rpm -K *.rpm | grep -iv gpg should be empty If not, STOP and sign them using the OSG RPM key -- talk to Mat Import the RPMs themselves into the Koji system [user@client ~] $ osg-koji import <RPM_DIRECTORY>/*.rpm Where <RPM_DIRECTORY> is the directory where you have downloaded the rpms. They will not be in any tags at this point Add the package to the whitelist for our koji tag: [user@client ~] $ osg-koji add-pkg <OUR_KOJI_TAG> <PACKAGE> --owner = \"<YOUR_KOJI_USERNAME>\" Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page, an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 and <YOUR_KOJI_USERNAME> is the username you use to interact with the Koji system Actually tag the builds: [user@client ~] $ osg-koji tag-pkg <OUR_KOJI_TAG> <PACKAGE> Check the Tasks tab in Koji to see if kojira has started regening the repos -- it might take a few minutes to kick in. If it doesn't, do it manually (if you're doing multiple packages, save this step until you're done with all of them): for repo in osg-{3.1,3.2,3.3,upcoming}-el5-{build,development,testing,release,prerelease,release-build}; do osg-koji regen-repo --nowait $repo done Make a test VM and install the package from minefield to test that it is actually present. Update the epelrescue RPMs table below","title":"Resurrecting EPEL RPMs"},{"location":"software/resurrecting-epel-packages/#removing-resurrected-rpms","text":"In case the RPM appeared back in EPEL, or we no longer need it, here's how to remove it from the epelrescue tags so we're not overriding the EPEL version: Find out the NVR of the build: [user@client ~] $ osg-koji list-tagged <OUR_KOJI_TAG> <PACKAGE> Where <OUR_KOJI_TAG> is one of those listed in the table at the top of this page and an example of <PACKAGE> is: cvmfs-config-osg-2.4-1.osg34.el6 Untag the packages: [user@client ~] $ osg-koji untag-pkg <OUR_KOJI_TAG> <PACKAGE>","title":"Removing resurrected RPMs"},{"location":"software/resurrecting-epel-packages/#why-you-should-not-use-block-pkg","text":"EPEL removes their packages by using 'koji block-pkg', which leaves the package and the builds in the tag, but prevents it from appearing in the repos. We cannot do that, because blocks are inherited and this will mess up our build repos. This is what happened in one case: EPEL removed rpmdevtools, which is a necessary package for all builds. I resurrected it into epelrescue-el5. Later, EPEL put rpmdevtools back into their repos, so it no longer needed to be in epelrescue-el5. I used block-pkg on rpmdevtools in epelrescue-el5, thinking that the package could remain tagged, but will stay out of our repos, and the EPEL package would be used instead. The block not only hid our rpmdevtools, it hid EPEL's rpmdevtools as well, preventing us from being able to build. I unblocked the rpmdevtools, and just untagged the build instead, regenerated our build repos, and we could build again.","title":"Why you should not use block-pkg"},{"location":"software/resurrecting-epel-packages/#policy-for-epelrescue-tags","text":"https://jira.opensciencegrid.org/browse/SOFTWARE-2046","title":"Policy for epelrescue tags"},{"location":"software/resurrecting-epel-packages/#table-of-epelrescue-rpms","text":"Package Distro version Date added Reason added Date removed python-six-1.7.3-1.el6 6 2015-08-12 Dep of osg-build (via mock) 2015-10-14 python-argparse-1.2.1-2.el6 6 2015-09-23 Dep of osg-wn-client (via gfal2) 2015-10-14 python-backports-ssl_match_hostname-3.4.0.2-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-requests-1.1.0-4.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14 python-urllib3-1.5-7.el6 6 2015-09-23 Dep of osg-build (via mock) 2015-10-14","title":"Table of epelrescue RPMs"},{"location":"software/resurrecting-epel-packages/#finding-out-if-a-package-is-still-needed-in-epelrescue","text":"Set $pkg to the name of a package to test (e.g. python-six ), and $rhel set to the RHEL version you're testing for (e.g. 5 , 6 , or 7 ). Using Carl's centos-srpms , scientific-srpms , slf-srpms scripts: for script in centos-srpms scientific-srpms slf-srpms; do echo -n $script \": \" $script -$rhel $pkg | grep . || echo none done A dry run of removing the package: osg-koji untag-pkg -n --all epelrescue-el$rhel $pkg Remove the -n when the output of that looks fine.","title":"Finding out if a package is still needed in epelrescue"},{"location":"software/rpm-development-guide/","text":"RPM Development Guide \u00b6 This page documents technical guidelines and details about RPM development for the OSG Software Stack. The procedures, conventions, and policies defined within are used by the OSG Software Team, and are recommended to all external developers who wish to contribute to the OSG Software Stack. Principles \u00b6 The principles below guide the design and implementation of the technical details that follow. Packages should adhere to community standards (e.g., Fedora Packaging Guidelines when possible, and significant deviations must be documented Every released package must be reproducible from data stored in our system Source code for software should be clearly separable from the packaging of that software Upstream source files (which should not be modified) should be clearly separated from files owned by the OSG Software Team Building source and binary packages from our system should be easy and efficient External developers should have a clear and effective system for developing and contributing packages We should use standard tools from relevant packaging and development communities when appropriate Contributing Packages \u00b6 We encourage all interested parties to contribute to OSG Software, and all the infrastructure described on this page should be friendly to external contributors. To participate in the packaging community: You must subscribe to the software-discuss@osg-htc.org email list. To create and edit packages: Obtain access to VDT SVN . To upload new source tarballs: You must have a cs.wisc.edu account with write access to the VDT source tarball directory. Email the osg-software list and request permission. To build using the OSG's Koji build system: You must have a valid personal certificate and a Koji account. To obtain the Koji account, email the osg-software list with your cert's DN and request permission. Development Infrastructure \u00b6 This section documents most of what a developer needs to know about our RPM infrastructure: Upstream Source Cache \u2014 a filesystem scheme for caching upstream source files Revision Control System \u2014 where to get and store development files, and how they are organized Build System \u2014 how to build packages from the revision control system Yum Repository \u2014 the location and organization of our Yum repository, and how to promote packages through it Upstream Source Cache \u00b6 One of our principles (every released package must be reproducible from data stored in our system) creates a potential issue: If we keep all historical source data, especially upstream files like source tarballs and source RPMs, in our revision control system, we may face large checkouts and consequently long checkout and update times. Our solution is to cache all upstream source files in a separate filesystem area, retaining historical files indefinitely. To avoid tainting upstream files, our policy is to leave them unmodified after download. Locating Files in the Cache \u00b6 Upstream source files are stored in the filesystem as follows: /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> where: Symbol Definition Example <PACKAGE> Upstream name of the source package, or some widely accepted form thereof ndt <VERSION> Upstream version string used to identify the release 3.6.4 <FILE> Upstream filename itself ndt-3.6.4.tar.gz The authoritative cache is the VDT webserver, which is fully backed up. The Koji build system uses this cache. Upstream source files are referenced from within the revision control system; see below for details. You will need to know the SHA1 checksum of any files you use from the cache. Do get it, do: $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> Contributing Upstream Files \u00b6 You must make sure that any new upstream source files are cached on the VDT webserver before building the package via Koji. You have two options: If you have access to a UW\u2013Madison CSL machine, you can scp the source files directly into the AFS locations using that machine If you do not have such access, write to the osg-software list to find someone who will post the files for you Git/GitHub Hosted Upstream Files \u00b6 It is also possible to pull sources and spec files from remote Git or GitHub repos instead of our source cache. See the upstream dir info for more information. Revision Control System \u00b6 All packages that the OSG Software Team releases are checked into our Subversion repository. Subversion Access \u00b6 Our Subversion repository is located at: https://vdt.cs.wisc.edu/svn Procedure for offsite users obtaining access to Subversion Or, from a UW\u2013Madison Computer Sciences machine: file:///p/condor/workspaces/vdt/svn The current SVN directory housing our native package work is $SVN/native/redhat (where $SVN is one of the ways of accessing our SVN repository above). For example, to check out the current package repository via HTTPS, do: [you@host]$ svn co https://vdt.cs.wisc.edu/svn/native/redhat OSG-Owned Software \u00b6 OSG-owned software goes into GitHub under the opensciencegrid organization. Files are organized as the developer sees fit. It is strongly recommended that each software package include a top-level Makefile with at least the following targets: Symbol Purpose install Install the software into final FHS locations rooted at DESTDIR dist Create a distribution source tarball (in the current section directory) for a release upstream Install the distribution source tarball into the upstream source cache Packaging Top-Level Directory Organization \u00b6 The top levels of our Subversion directory hierarchy for packaging are as follows: native/redhat/<SECTION>/<PACKAGE> where: Symbol Definition Example <SECTION> Development section Standard Subversion sections like trunk and branches/* <PACKAGE> Our standardized name for a source package ndt Package Directory Organization \u00b6 Within a source package directory, the following files (detailed in separate sections below) may exist: README text file package notes, by and for developers upstream/ directory references to the upstream source cache and other kinds of upstream files osg/ directory overrides and patches of upstream files, plus new files, which contribute to the final OSG source package README \u00b6 This is a free-form text file for developers to leave notes about the package. Please document anything interesting about how you procured the upstream source, the reasons for the modifications you made, or anything else people might need to know in order to maintain the package in the future. Please document the why , not just the what . upstream \u00b6 Within the per-package directories of the revision control system, there must be a way to refer to cached files. This is done with small text files that (a) are named consistently, and (b) contain the location of the referenced file as its contents. A reference file is named: <DESCRIPTION>.<TYPE>.source where: Symbol Definition Example <DESCRIPTION> Descriptive label of the source of the referenced file developer , epel , emi <TYPE> Type of referenced file tarball , srpm and contain references to cached files, Git repos, and comments. which start with # and continue until the end of the line. It is useful to add the source of the upstream file into a comment. Cached files \u00b6 To reference files in the upstream source cache, use the upstream source cache path defined above, without the prefix component, followed by the sha1sum of the file: <PACKAGE>/<VERSION>/<FILE> sha1sum=<SHA1SUM> Obtain the sha1sum by running the sha1sum command with the source file as an argument, i.e. $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> Note This feature requires OSG-Build 1.14.0 or later. Example The reference file for globus-common 's source tarball is named epel.srpm.source and contains: globus-common/16.4/globus-common-16.4-1.el6.src.rpm sha1sum=134478c56c2437c335c20636831f794b66290bec # Downloaded from 'http://dl.fedoraproject.org/pub/epel/6/SRPMS/globus-common-16.4-1.el6.src.rpm' GitHub repos \u00b6 Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note See also advanced features for Git and GitHub repos . To reference tags in GitHub repos, use the following syntax (all on one line): type=github repo=<OWNER>/<PROJECT> tag=<TAG> hash=<HASH> where: Symbol Definition Example <OWNER> Owner of the GitHub repo opensciencegrid <PROJECT> Name of the project osg-build <TAG> Git tag to use v1.12.2 <HASH> Full 40-char Git hash of the tag cff50ffe812282552cedae81f3809d3cf7087a3e Note The tarball will be called <PROJECT>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example You can refer to the 1.12.2 release of osg-build with this line: type=github repo=opensciencegrid/osg-build tag=v1.12.2 hash=cff50ffe812282552cedae81f3809d3cf7087a3e This results in a tarball named osg-build-1.12.2.tar.gz . In addition, if the repository contains a file called rpm/<PROJECT>.spec , it will be used as the spec file for the build (unless overridden in the osg directory). Git repos \u00b6 Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note You can use a shorter syntax for GitHub repos -- see above. See also advanced features for Git and GitHub repos . To reference tags in Git repos, use the following syntax (all on one line): type=git url=<URL> name=<NAME> tag=<TAG> hash=<HASH> where: Symbol Definition Example <URL> Location of the Git repo https://github.com/opensciencegrid/osg-build.git <NAME> Name of the software (optional) osg-build <TAG> Git tag to use v1.11.2 <HASH> Full 40-char Git hash of the tag 5bcf48c442d21b1e8c93a468d884f84122f7cc9e Note <NAME> is optional; if not present, OSG-Build will use the last component of the URL, without the .git suffix. The tarball will be called <NAME>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example The reference file for osg-build 's repo is named osg.github.source and contains: type=git url=https://github.com/opensciencegrid/osg-build.git name=osg-build tag=v1.11.2 hash=5bcf48c442d21b1e8c93a468d884f84122f7cc9e This results in a tarball named osg-build-1.11.2.tar.gz . In addition, if the repository contains a file called rpm/<NAME>.spec , it will be used as the spec file for the build (unless overridden in the osg directory). Typical workflow when building out of GitHub repos \u00b6 Fork the repository of the package that you would like to build Create a new branch in your fork Make, commit, and push changes to your new branch In your fork, tag the commit that you would like to build In the upstream/osg.github.source , change the repo to point at your fork and tag Attempt a scratch build If the build fails, remove the tag and repeat steps 3-6 Submit a PR to merge changes upstream Tag the final version on the upstream fork Build the version that will go through the normal software cycle Note Packaging-only changes should be tagged with a release number of the format v<version>-<release> , e.g. v3.4.23-2 Advanced features for Git and GitHub repos \u00b6 The following features make software development in Git and GitHub more convenient: Support for RPM release numbers in Git tags: If the tag for the software contains a dash, as in v1.12.2-1 , it is assumed that the text after the dash is the RPM release instead of the software version. The RPM release is not included in the tarball. That is, the project osg-build with the tag v1.12.2-1 will result in a tarball named osg-build-1.12.1.tar.gz , not osg-build-1.12.1-1.tar.gz . Can specify tarball name in the .source file: The new tarball attribute allows you to specify the name of the tarball and directory that the repo contents will be put into. The syntax is tarball=<NAME>.tar.gz . The extension must be .tar.gz , no other archive formats are supported. The directory inside the tarball will then be <NAME>/ . Can ignore hash mismatch (scratch and local builds only): For local builds (rpmbuild and mock tasks) and Koji scratch builds, a hash mismatch will result in a warning. Non-scratch Koji builds will still consider it an error. Can use a branch as the tag: The tag attribute can refer to a branch instead of a tag, e.g. tag=master . Combining the last two features can really speed up package development. For example, you can use this to make scratch builds of the current master: type=github repo=<OWNER>/<PROJECT> tarball=<PROJECT>-<VERSION>.tar.gz tag=master hash=0 This might also be useful as part of a continuous integration scheme (e.g. Travis-CI). osg \u00b6 The osg directory contains files that are owned by the OSG Software Team and that are used to create the final, released source package. It may contain a variety of development files: An RPM .spec file, which overrides any spec file from a referenced source Patch ( .patch ) or replacement files, which override any same-named file from the top-level directory of a referenced source Other files, which must be explicitly placed into the package by the spec file Generated directories \u00b6 The following directories may be generated by our build tool, OSG-Build . They are not under revision control. _upstream_srpm_contents/ expanded contents of a cached upstream source package _upstream_tarball_contents/ expanded contents of all cached upstream source tarballs _final_srpm_contents/ the final contents of the OSG source package _build_results/ OSG source and binary packages resulting from a build _quilt/ expanded, patched contents of the upstream sources, as generated by the quilt tool _upstream_srpm_contents \u00b6 The _upstream_srpm_contents directory contains the files that are part of the upstream source package. It is a volatile record of the upstream source for developer use. _upstream_tarball_contents \u00b6 The _upstream_tarball_contents directory contains the files that are part of the upstream source tarballs. It is generated by the package build tool if the --full-extract option is passed. It is not used for anything by the build tool, but meant as a convenience to allow the developer to look inside the upstream sources (for making patches, etc.). _final_srpm_contents \u00b6 The _final_srpm_contents directory contains the final files that are part of the released source package. It is a volatile record of a build for developer use. _build_results \u00b6 The _build_results directory contains the source and binary RPMs that are produced by a local build. It is a volatile record of a build for developer use. _quilt \u00b6 The _quilt directory contains the unpacked sources after they have been patched using the quilt utility. This allows easier patch development. Packaging Organization Examples \u00b6 Use Case 1: Packaging an Upstream Source Tarball \u00b6 When the OSG Software Team packages an upstream source tarball, for which there is no existing package, the source tarball is referenced with a .source file and we provide a spec file and, if necessary, patches. For example, RSV is provided as a source tarball only. Its package directory contains: rsv/ osg/ rsv.spec upstream/ developer.tarball.source Use Case 2: Passing Through a Source RPM \u00b6 When the OSG Software Team simply provides a copy of an existing source RPM, it is referenced with a .source file and that is it. For example, we do not modify the globus-common source RPM from EPEL. Its package directory contains: globus-common/ upstream/ epel.srpm.source Use Case 3: Modifying a Source RPM \u00b6 When the OSG Software Team modifies an existing source RPM, it is referenced with a .source file and then all changes to the upstream source are contained in the osg directory. For example, we use this mechanism for the globus-ftp-client package, originally obtained from EPEL. Its package directory contains: globus-ftp-client/ osg/ globus-ftp-client.spec 1853-ssh-bin.patch upstream/ epel.srpm.source Build Process \u00b6 All necessary information to create the package will be committed to the VDT source code repository (see below) The OSG build tools will take those files, create a source RPM, and submit it to our Koji build system Developers may use rpmbuild and mock for faster iterative development before submitting the package to Koji. osg-build may be used as a wrapper script around rpmbuild and mock . OSG Software Repository \u00b6 OSG Operations maintains the Yum repositories that contain our source and binary RPMs at https://repo.opensciencegrid.org/osg/ and are mirrored at other institutions as well. Release Levels \u00b6 Every package is classified into a release level based on the amount of testing it has undergone and our confidence in its stability. When a package is first built, it goes into the lowest level ( osg-development ). The members of the OSG Software and Release teams may promote packages through the release levels, as per our Release Policy page . Packaging Conventions \u00b6 In addition to adhering to the Fedora Packaging Guidelines (FPG), we have a few rules and guidelines of our own: When we pass-through an RPM and make any changes to it (so it has an updated package number), we construct the version-release as follows: The version of the original RPM remains unchanged The release is composed of three parts: ORIGINALRELEASE.OSGRELEASE We add a distro tag based on the OSG major version and OS major version, e.g. \"osg33.el6\". (Use %{?dist} in the Release field) Example: We copy package foobar-3.0.5-1 from somewhere. We need to patch it, so the full name-version-release (NVR) for OSG 3.3 on EL 6 becomes foobar-3.0.5-1.1.osg33.el6 Note that we added \".1.osg33.el6\" to the release number. If we update our packaging (but still base on foobar-3.0.5-1), we change to \".2.osg33.el6\". In the spec file, this would look like: Release : 1.2 %{?dist} Packaging for Multiple Distro Versions \u00b6 Conditionalizing spec files \u00b6 Some packages may need different build behavior between major versions of the OS; RPM conditional statements will be used to handle this. The following macros are defined: Name Value (EL6) Value (EL7) %rhel 6 7 %el6 1 undefined or 0 %el7 undefined or 0 1 Here's how to use them: %if 0%{?el6} # this code will be executed on EL 6 only %endif %if 0%{?el7} # this code will be executed on EL 7 only %endif %if 0%{?rhel} >= 7 # this code will be executed on EL 7 and newer %endif (There does not seem to be an %elseif ). The syntax %{?el6} expands to the value of the %el6 macro if it is defined, and to the empty string if not; the 0 is there to keep the condition from being empty in the %if statement if the macro is not defined. Renaming or Removing Packages \u00b6 Occasionally we want to cause a package to be removed on update, or replaced by a package with a different name. For the most part, the Fedora Packaging Guidelines page on renames shows how to do that. The exception is that we do not have the equivalent of a fedora-obsolete-packages package, so in order to force the removal of an entire package (not a subpackage), we have to dummy out the package instead -- see below. (This should be a rare situation.) Note After doing a rename or a removal, you must update all the packages and subpackages that require the package being removed or renamed, and change or remove the requirements as appropriate. To find packages that require the old package at run time, set up a host with the OSG repos and install the yum-utils RPM. Then, run: $ repoquery --plugins --whatrequires $OLDPACKAGE To find packages that require the old package at build time, install osg-build , and do this from a checkout of the OSG repos: $ osg-build prebuild * $ for srpm in */_final_srpm_contents/*.src.rpm ; do \\ echo \"***** $srpm *****\"; \\ rpm -q --requires -p $srpm | grep -w $OLDPACKAGE; \\ done (examine the output to avoid false matches) Note Carefully test these changes, including places where the old package may be brought in indirectly. Dummying out a package \u00b6 In order to forcibly remove an entire package with no replacement, you have to replace the package with one that does nothing. This is because there is no package that will \"obsolete\" the old package. Do the following for the main package and any subpackages it may have: Change the Summary to \"Dummy package\" Change the %description to: This is an empty package created for $REASONS It may safely be removed. Where $REASONS is a description of why you need this dummy package Remove all Requires and Obsoletes lines Do not remove Provides lines Remove %pre and %post scriptlets Unless there is a good reason not to, remove %preun and %postun scriptlets Empty the %files section","title":"RPM Development Guide"},{"location":"software/rpm-development-guide/#rpm-development-guide","text":"This page documents technical guidelines and details about RPM development for the OSG Software Stack. The procedures, conventions, and policies defined within are used by the OSG Software Team, and are recommended to all external developers who wish to contribute to the OSG Software Stack.","title":"RPM Development Guide"},{"location":"software/rpm-development-guide/#principles","text":"The principles below guide the design and implementation of the technical details that follow. Packages should adhere to community standards (e.g., Fedora Packaging Guidelines when possible, and significant deviations must be documented Every released package must be reproducible from data stored in our system Source code for software should be clearly separable from the packaging of that software Upstream source files (which should not be modified) should be clearly separated from files owned by the OSG Software Team Building source and binary packages from our system should be easy and efficient External developers should have a clear and effective system for developing and contributing packages We should use standard tools from relevant packaging and development communities when appropriate","title":"Principles"},{"location":"software/rpm-development-guide/#contributing-packages","text":"We encourage all interested parties to contribute to OSG Software, and all the infrastructure described on this page should be friendly to external contributors. To participate in the packaging community: You must subscribe to the software-discuss@osg-htc.org email list. To create and edit packages: Obtain access to VDT SVN . To upload new source tarballs: You must have a cs.wisc.edu account with write access to the VDT source tarball directory. Email the osg-software list and request permission. To build using the OSG's Koji build system: You must have a valid personal certificate and a Koji account. To obtain the Koji account, email the osg-software list with your cert's DN and request permission.","title":"Contributing Packages"},{"location":"software/rpm-development-guide/#development-infrastructure","text":"This section documents most of what a developer needs to know about our RPM infrastructure: Upstream Source Cache \u2014 a filesystem scheme for caching upstream source files Revision Control System \u2014 where to get and store development files, and how they are organized Build System \u2014 how to build packages from the revision control system Yum Repository \u2014 the location and organization of our Yum repository, and how to promote packages through it","title":"Development Infrastructure"},{"location":"software/rpm-development-guide/#upstream-source-cache","text":"One of our principles (every released package must be reproducible from data stored in our system) creates a potential issue: If we keep all historical source data, especially upstream files like source tarballs and source RPMs, in our revision control system, we may face large checkouts and consequently long checkout and update times. Our solution is to cache all upstream source files in a separate filesystem area, retaining historical files indefinitely. To avoid tainting upstream files, our policy is to leave them unmodified after download.","title":"Upstream Source Cache"},{"location":"software/rpm-development-guide/#locating-files-in-the-cache","text":"Upstream source files are stored in the filesystem as follows: /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> where: Symbol Definition Example <PACKAGE> Upstream name of the source package, or some widely accepted form thereof ndt <VERSION> Upstream version string used to identify the release 3.6.4 <FILE> Upstream filename itself ndt-3.6.4.tar.gz The authoritative cache is the VDT webserver, which is fully backed up. The Koji build system uses this cache. Upstream source files are referenced from within the revision control system; see below for details. You will need to know the SHA1 checksum of any files you use from the cache. Do get it, do: $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE>","title":"Locating Files in the Cache"},{"location":"software/rpm-development-guide/#contributing-upstream-files","text":"You must make sure that any new upstream source files are cached on the VDT webserver before building the package via Koji. You have two options: If you have access to a UW\u2013Madison CSL machine, you can scp the source files directly into the AFS locations using that machine If you do not have such access, write to the osg-software list to find someone who will post the files for you","title":"Contributing Upstream Files"},{"location":"software/rpm-development-guide/#gitgithub-hosted-upstream-files","text":"It is also possible to pull sources and spec files from remote Git or GitHub repos instead of our source cache. See the upstream dir info for more information.","title":"Git/GitHub Hosted Upstream Files"},{"location":"software/rpm-development-guide/#revision-control-system","text":"All packages that the OSG Software Team releases are checked into our Subversion repository.","title":"Revision Control System"},{"location":"software/rpm-development-guide/#subversion-access","text":"Our Subversion repository is located at: https://vdt.cs.wisc.edu/svn Procedure for offsite users obtaining access to Subversion Or, from a UW\u2013Madison Computer Sciences machine: file:///p/condor/workspaces/vdt/svn The current SVN directory housing our native package work is $SVN/native/redhat (where $SVN is one of the ways of accessing our SVN repository above). For example, to check out the current package repository via HTTPS, do: [you@host]$ svn co https://vdt.cs.wisc.edu/svn/native/redhat","title":"Subversion Access"},{"location":"software/rpm-development-guide/#osg-owned-software","text":"OSG-owned software goes into GitHub under the opensciencegrid organization. Files are organized as the developer sees fit. It is strongly recommended that each software package include a top-level Makefile with at least the following targets: Symbol Purpose install Install the software into final FHS locations rooted at DESTDIR dist Create a distribution source tarball (in the current section directory) for a release upstream Install the distribution source tarball into the upstream source cache","title":"OSG-Owned Software"},{"location":"software/rpm-development-guide/#packaging-top-level-directory-organization","text":"The top levels of our Subversion directory hierarchy for packaging are as follows: native/redhat/<SECTION>/<PACKAGE> where: Symbol Definition Example <SECTION> Development section Standard Subversion sections like trunk and branches/* <PACKAGE> Our standardized name for a source package ndt","title":"Packaging Top-Level Directory Organization"},{"location":"software/rpm-development-guide/#package-directory-organization","text":"Within a source package directory, the following files (detailed in separate sections below) may exist: README text file package notes, by and for developers upstream/ directory references to the upstream source cache and other kinds of upstream files osg/ directory overrides and patches of upstream files, plus new files, which contribute to the final OSG source package","title":"Package Directory Organization"},{"location":"software/rpm-development-guide/#readme","text":"This is a free-form text file for developers to leave notes about the package. Please document anything interesting about how you procured the upstream source, the reasons for the modifications you made, or anything else people might need to know in order to maintain the package in the future. Please document the why , not just the what .","title":"README"},{"location":"software/rpm-development-guide/#upstream","text":"Within the per-package directories of the revision control system, there must be a way to refer to cached files. This is done with small text files that (a) are named consistently, and (b) contain the location of the referenced file as its contents. A reference file is named: <DESCRIPTION>.<TYPE>.source where: Symbol Definition Example <DESCRIPTION> Descriptive label of the source of the referenced file developer , epel , emi <TYPE> Type of referenced file tarball , srpm and contain references to cached files, Git repos, and comments. which start with # and continue until the end of the line. It is useful to add the source of the upstream file into a comment.","title":"upstream"},{"location":"software/rpm-development-guide/#cached-files","text":"To reference files in the upstream source cache, use the upstream source cache path defined above, without the prefix component, followed by the sha1sum of the file: <PACKAGE>/<VERSION>/<FILE> sha1sum=<SHA1SUM> Obtain the sha1sum by running the sha1sum command with the source file as an argument, i.e. $ sha1sum /p/vdt/public/html/upstream/<PACKAGE>/<VERSION>/<FILE> Note This feature requires OSG-Build 1.14.0 or later. Example The reference file for globus-common 's source tarball is named epel.srpm.source and contains: globus-common/16.4/globus-common-16.4-1.el6.src.rpm sha1sum=134478c56c2437c335c20636831f794b66290bec # Downloaded from 'http://dl.fedoraproject.org/pub/epel/6/SRPMS/globus-common-16.4-1.el6.src.rpm'","title":"Cached files"},{"location":"software/rpm-development-guide/#github-repos","text":"Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note See also advanced features for Git and GitHub repos . To reference tags in GitHub repos, use the following syntax (all on one line): type=github repo=<OWNER>/<PROJECT> tag=<TAG> hash=<HASH> where: Symbol Definition Example <OWNER> Owner of the GitHub repo opensciencegrid <PROJECT> Name of the project osg-build <TAG> Git tag to use v1.12.2 <HASH> Full 40-char Git hash of the tag cff50ffe812282552cedae81f3809d3cf7087a3e Note The tarball will be called <PROJECT>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example You can refer to the 1.12.2 release of osg-build with this line: type=github repo=opensciencegrid/osg-build tag=v1.12.2 hash=cff50ffe812282552cedae81f3809d3cf7087a3e This results in a tarball named osg-build-1.12.2.tar.gz . In addition, if the repository contains a file called rpm/<PROJECT>.spec , it will be used as the spec file for the build (unless overridden in the osg directory).","title":"GitHub repos"},{"location":"software/rpm-development-guide/#git-repos","text":"Warning OSG software policy requires that all Git and GitHub repos used for building software have mirrors at the UW. Many software repos under the opensciencegrid GitHub organization are already mirrored. If you are uncertain, or have a new project that you want mirrored, send email to technology-team@osg-htc.org . Note You can use a shorter syntax for GitHub repos -- see above. See also advanced features for Git and GitHub repos . To reference tags in Git repos, use the following syntax (all on one line): type=git url=<URL> name=<NAME> tag=<TAG> hash=<HASH> where: Symbol Definition Example <URL> Location of the Git repo https://github.com/opensciencegrid/osg-build.git <NAME> Name of the software (optional) osg-build <TAG> Git tag to use v1.11.2 <HASH> Full 40-char Git hash of the tag 5bcf48c442d21b1e8c93a468d884f84122f7cc9e Note <NAME> is optional; if not present, OSG-Build will use the last component of the URL, without the .git suffix. The tarball will be called <NAME>-<VERSION>.tar.gz where <VERSION> is <TAG> without the v prefix (if there is one). Example The reference file for osg-build 's repo is named osg.github.source and contains: type=git url=https://github.com/opensciencegrid/osg-build.git name=osg-build tag=v1.11.2 hash=5bcf48c442d21b1e8c93a468d884f84122f7cc9e This results in a tarball named osg-build-1.11.2.tar.gz . In addition, if the repository contains a file called rpm/<NAME>.spec , it will be used as the spec file for the build (unless overridden in the osg directory).","title":"Git repos"},{"location":"software/rpm-development-guide/#typical-workflow-when-building-out-of-github-repos","text":"Fork the repository of the package that you would like to build Create a new branch in your fork Make, commit, and push changes to your new branch In your fork, tag the commit that you would like to build In the upstream/osg.github.source , change the repo to point at your fork and tag Attempt a scratch build If the build fails, remove the tag and repeat steps 3-6 Submit a PR to merge changes upstream Tag the final version on the upstream fork Build the version that will go through the normal software cycle Note Packaging-only changes should be tagged with a release number of the format v<version>-<release> , e.g. v3.4.23-2","title":"Typical workflow when building out of GitHub repos"},{"location":"software/rpm-development-guide/#advanced-features-for-git-and-github-repos","text":"The following features make software development in Git and GitHub more convenient: Support for RPM release numbers in Git tags: If the tag for the software contains a dash, as in v1.12.2-1 , it is assumed that the text after the dash is the RPM release instead of the software version. The RPM release is not included in the tarball. That is, the project osg-build with the tag v1.12.2-1 will result in a tarball named osg-build-1.12.1.tar.gz , not osg-build-1.12.1-1.tar.gz . Can specify tarball name in the .source file: The new tarball attribute allows you to specify the name of the tarball and directory that the repo contents will be put into. The syntax is tarball=<NAME>.tar.gz . The extension must be .tar.gz , no other archive formats are supported. The directory inside the tarball will then be <NAME>/ . Can ignore hash mismatch (scratch and local builds only): For local builds (rpmbuild and mock tasks) and Koji scratch builds, a hash mismatch will result in a warning. Non-scratch Koji builds will still consider it an error. Can use a branch as the tag: The tag attribute can refer to a branch instead of a tag, e.g. tag=master . Combining the last two features can really speed up package development. For example, you can use this to make scratch builds of the current master: type=github repo=<OWNER>/<PROJECT> tarball=<PROJECT>-<VERSION>.tar.gz tag=master hash=0 This might also be useful as part of a continuous integration scheme (e.g. Travis-CI).","title":"Advanced features for Git and GitHub repos"},{"location":"software/rpm-development-guide/#osg","text":"The osg directory contains files that are owned by the OSG Software Team and that are used to create the final, released source package. It may contain a variety of development files: An RPM .spec file, which overrides any spec file from a referenced source Patch ( .patch ) or replacement files, which override any same-named file from the top-level directory of a referenced source Other files, which must be explicitly placed into the package by the spec file","title":"osg"},{"location":"software/rpm-development-guide/#generated-directories","text":"The following directories may be generated by our build tool, OSG-Build . They are not under revision control. _upstream_srpm_contents/ expanded contents of a cached upstream source package _upstream_tarball_contents/ expanded contents of all cached upstream source tarballs _final_srpm_contents/ the final contents of the OSG source package _build_results/ OSG source and binary packages resulting from a build _quilt/ expanded, patched contents of the upstream sources, as generated by the quilt tool","title":"Generated directories"},{"location":"software/rpm-development-guide/#_upstream_srpm_contents","text":"The _upstream_srpm_contents directory contains the files that are part of the upstream source package. It is a volatile record of the upstream source for developer use.","title":"_upstream_srpm_contents"},{"location":"software/rpm-development-guide/#_upstream_tarball_contents","text":"The _upstream_tarball_contents directory contains the files that are part of the upstream source tarballs. It is generated by the package build tool if the --full-extract option is passed. It is not used for anything by the build tool, but meant as a convenience to allow the developer to look inside the upstream sources (for making patches, etc.).","title":"_upstream_tarball_contents"},{"location":"software/rpm-development-guide/#_final_srpm_contents","text":"The _final_srpm_contents directory contains the final files that are part of the released source package. It is a volatile record of a build for developer use.","title":"_final_srpm_contents"},{"location":"software/rpm-development-guide/#_build_results","text":"The _build_results directory contains the source and binary RPMs that are produced by a local build. It is a volatile record of a build for developer use.","title":"_build_results"},{"location":"software/rpm-development-guide/#_quilt","text":"The _quilt directory contains the unpacked sources after they have been patched using the quilt utility. This allows easier patch development.","title":"_quilt"},{"location":"software/rpm-development-guide/#packaging-organization-examples","text":"","title":"Packaging Organization Examples"},{"location":"software/rpm-development-guide/#use-case-1-packaging-an-upstream-source-tarball","text":"When the OSG Software Team packages an upstream source tarball, for which there is no existing package, the source tarball is referenced with a .source file and we provide a spec file and, if necessary, patches. For example, RSV is provided as a source tarball only. Its package directory contains: rsv/ osg/ rsv.spec upstream/ developer.tarball.source","title":"Use Case 1: Packaging an Upstream Source Tarball"},{"location":"software/rpm-development-guide/#use-case-2-passing-through-a-source-rpm","text":"When the OSG Software Team simply provides a copy of an existing source RPM, it is referenced with a .source file and that is it. For example, we do not modify the globus-common source RPM from EPEL. Its package directory contains: globus-common/ upstream/ epel.srpm.source","title":"Use Case 2: Passing Through a Source RPM"},{"location":"software/rpm-development-guide/#use-case-3-modifying-a-source-rpm","text":"When the OSG Software Team modifies an existing source RPM, it is referenced with a .source file and then all changes to the upstream source are contained in the osg directory. For example, we use this mechanism for the globus-ftp-client package, originally obtained from EPEL. Its package directory contains: globus-ftp-client/ osg/ globus-ftp-client.spec 1853-ssh-bin.patch upstream/ epel.srpm.source","title":"Use Case 3: Modifying a Source RPM"},{"location":"software/rpm-development-guide/#build-process","text":"All necessary information to create the package will be committed to the VDT source code repository (see below) The OSG build tools will take those files, create a source RPM, and submit it to our Koji build system Developers may use rpmbuild and mock for faster iterative development before submitting the package to Koji. osg-build may be used as a wrapper script around rpmbuild and mock .","title":"Build Process"},{"location":"software/rpm-development-guide/#osg-software-repository","text":"OSG Operations maintains the Yum repositories that contain our source and binary RPMs at https://repo.opensciencegrid.org/osg/ and are mirrored at other institutions as well.","title":"OSG Software Repository"},{"location":"software/rpm-development-guide/#release-levels","text":"Every package is classified into a release level based on the amount of testing it has undergone and our confidence in its stability. When a package is first built, it goes into the lowest level ( osg-development ). The members of the OSG Software and Release teams may promote packages through the release levels, as per our Release Policy page .","title":"Release Levels"},{"location":"software/rpm-development-guide/#packaging-conventions","text":"In addition to adhering to the Fedora Packaging Guidelines (FPG), we have a few rules and guidelines of our own: When we pass-through an RPM and make any changes to it (so it has an updated package number), we construct the version-release as follows: The version of the original RPM remains unchanged The release is composed of three parts: ORIGINALRELEASE.OSGRELEASE We add a distro tag based on the OSG major version and OS major version, e.g. \"osg33.el6\". (Use %{?dist} in the Release field) Example: We copy package foobar-3.0.5-1 from somewhere. We need to patch it, so the full name-version-release (NVR) for OSG 3.3 on EL 6 becomes foobar-3.0.5-1.1.osg33.el6 Note that we added \".1.osg33.el6\" to the release number. If we update our packaging (but still base on foobar-3.0.5-1), we change to \".2.osg33.el6\". In the spec file, this would look like: Release : 1.2 %{?dist}","title":"Packaging Conventions"},{"location":"software/rpm-development-guide/#packaging-for-multiple-distro-versions","text":"","title":"Packaging for Multiple Distro Versions"},{"location":"software/rpm-development-guide/#conditionalizing-spec-files","text":"Some packages may need different build behavior between major versions of the OS; RPM conditional statements will be used to handle this. The following macros are defined: Name Value (EL6) Value (EL7) %rhel 6 7 %el6 1 undefined or 0 %el7 undefined or 0 1 Here's how to use them: %if 0%{?el6} # this code will be executed on EL 6 only %endif %if 0%{?el7} # this code will be executed on EL 7 only %endif %if 0%{?rhel} >= 7 # this code will be executed on EL 7 and newer %endif (There does not seem to be an %elseif ). The syntax %{?el6} expands to the value of the %el6 macro if it is defined, and to the empty string if not; the 0 is there to keep the condition from being empty in the %if statement if the macro is not defined.","title":"Conditionalizing spec files"},{"location":"software/rpm-development-guide/#renaming-or-removing-packages","text":"Occasionally we want to cause a package to be removed on update, or replaced by a package with a different name. For the most part, the Fedora Packaging Guidelines page on renames shows how to do that. The exception is that we do not have the equivalent of a fedora-obsolete-packages package, so in order to force the removal of an entire package (not a subpackage), we have to dummy out the package instead -- see below. (This should be a rare situation.) Note After doing a rename or a removal, you must update all the packages and subpackages that require the package being removed or renamed, and change or remove the requirements as appropriate. To find packages that require the old package at run time, set up a host with the OSG repos and install the yum-utils RPM. Then, run: $ repoquery --plugins --whatrequires $OLDPACKAGE To find packages that require the old package at build time, install osg-build , and do this from a checkout of the OSG repos: $ osg-build prebuild * $ for srpm in */_final_srpm_contents/*.src.rpm ; do \\ echo \"***** $srpm *****\"; \\ rpm -q --requires -p $srpm | grep -w $OLDPACKAGE; \\ done (examine the output to avoid false matches) Note Carefully test these changes, including places where the old package may be brought in indirectly.","title":"Renaming or Removing Packages"},{"location":"software/rpm-development-guide/#dummying-out-a-package","text":"In order to forcibly remove an entire package with no replacement, you have to replace the package with one that does nothing. This is because there is no package that will \"obsolete\" the old package. Do the following for the main package and any subpackages it may have: Change the Summary to \"Dummy package\" Change the %description to: This is an empty package created for $REASONS It may safely be removed. Where $REASONS is a description of why you need this dummy package Remove all Requires and Obsoletes lines Do not remove Provides lines Remove %pre and %post scriptlets Unless there is a good reason not to, remove %preun and %postun scriptlets Empty the %files section","title":"Dummying out a package"},{"location":"software/upcoming-to-main/","text":"Promoting Packages from Upcoming to Main \u00b6 Sometimes we move packages from Upcoming to the Main repositories in the middle of a release series. Once the Release Manager has given tentative approval for such a move: If needed, move the software from upcoming to trunk and release using the usual process: Merge changes to the package in SVN from branches/upcoming to trunk. Build the package from trunk. Follow the normal process to prepare a build for release (including development testing, promotion, etc.). On release day, when the package has been released in the Main production repository, clean up the package from the upcoming repos: Untag from all upcoming repos the version of the package corresponding to the version that was released in main. (Do NOT untag from the osg-upcoming-elN-release-X.Y.Z tags) Also, untag all equal or lesser NVRs (minus the dist tag) from all upcoming repos. If you do not have the privileges to untag from upcoming-release, someone on the Release Team can help. (These steps are necessary to make sure Koji builds can't mistakenly use an older build from the upcoming repos). Unless there's a newer build in branches/upcoming than what was released, remove the package directory from branches/upcoming.","title":"Upcoming to Main"},{"location":"software/upcoming-to-main/#promoting-packages-from-upcoming-to-main","text":"Sometimes we move packages from Upcoming to the Main repositories in the middle of a release series. Once the Release Manager has given tentative approval for such a move: If needed, move the software from upcoming to trunk and release using the usual process: Merge changes to the package in SVN from branches/upcoming to trunk. Build the package from trunk. Follow the normal process to prepare a build for release (including development testing, promotion, etc.). On release day, when the package has been released in the Main production repository, clean up the package from the upcoming repos: Untag from all upcoming repos the version of the package corresponding to the version that was released in main. (Do NOT untag from the osg-upcoming-elN-release-X.Y.Z tags) Also, untag all equal or lesser NVRs (minus the dist tag) from all upcoming repos. If you do not have the privileges to untag from upcoming-release, someone on the Release Team can help. (These steps are necessary to make sure Koji builds can't mistakenly use an older build from the upcoming repos). Unless there's a newer build in branches/upcoming than what was released, remove the package directory from branches/upcoming.","title":"Promoting Packages from Upcoming to Main"},{"location":"software/user-certs/","text":"User Certificates \u00b6 Note This document describes how to get and set up a personal certificate (also called a grid user certificate). For instructions on how to get host certificates, see the Host Certificates document . Getting a User Certificate \u00b6 This section describes how to get and set up a personal (user) certificate. A user certificate is a type of SSL certificate -- the same technology used for identifying websites when using HTTPS -- but identifying a human instead of a host. This is used to access some grid resources, such as: OSG Topology (for viewing private contact information) The osg-notify tool for sending mass emails The GGUS ticketing system The Koji build system for the OSG Software Stack User certs may also be useful for debugging storage access (such as XRootD). Currently, you can get a user certificate from CILogon. Know your responsibilities \u00b6 If your account or user certificate is compromised, you must notify the issuer of your certificate. In addition, you should update your certificate and revoke the old certificate if any of the information in the certificate (such as name or email address) change. For the CILogon RA send email to ca@cilogon.org . Additional responsibilities required by the CILogon CA are given on their page . Getting a certificate from CILogon \u00b6 You will have to obtain your user certificate using the CILogon web UI . Follow the steps below to get an user certificate: Open the CILogon page, https://cilogon.org , in your browser of choice First, either search for your institution and select it or scroll through list and do the same. . Warning Do not use Google, GitHub, or ORCID as providers since they are not widely supported in the OSG. If your institution is not on the list, please contact your institution's IT support to see if they can support CILogon. Click the Log On button and enter your institutional credentials if prompted. After successfully entering your credentials, click on the \"Create Password-Protected Certificate\" link Enter a password that is at least 12 characters long and then click on the Get New Certificate button. Click the Download Your Certificate button to download your certificate in .p12 format. The certificate will be protected using the password you entered in the previous step. Certificate formats \u00b6 Your user certificate can be stored in a few different formats: CILogon will give you a certificate in the PKCS12 format (file extension .p12 ). The PKCS12 format stores the certificate and private key in a single file along with an optional certificate chain. This is the file format that can be loaded into your browser for accessing Topology, GGUS, or the Koji web interace with. Most command line tools use the PEM format (file extension .pem ). The PEM format stores the public certificate in one file, and the private key in another file. To convert a PKCS12 file to PEM files, do the following: First, extract your user certificate from your PKCS12 file by running the following command. You'll be prompted for the password you used to create the certificate. The invocation assumes that the PKCS12 file is called usercred.p12 . After running, the PEM certificate will be written to usercert.pem . user@host $ openssl pkcs12 -in usercred.p12 -out usercert.pem -nodes -clcerts -nokeys Enter Import Password: MAC verified OK Second, extract the private key by running the following command. You'll be prompted for two different passwords. The first prompt will be for the password that you used to create the certificate. The second prompt will be for the password that will encrypt the PEM certificate that will be created. As before, the invocation assumes that your PKCS12 certificate is located in usercred.p12 . After running, the PEM certificate with your private key will be written to userkey.pem . user@host $ openssl pkcs12 -in usercred.p12 -out userkey.pem -nocerts Enter Import Password: MAC verified OK Enter PEM pass phrase: Verifying - Enter PEM pass phrase: Using Your User Certificate \u00b6 The standard location to place user certificates is in the .globus subdirectory of your home directory: user@host $ mkdir -p ~/.globus user@host $ cp userkey.pem ~/.globus/ user@host $ cp usercert.pem ~/.globus/ user@host $ cp usercred.p12 ~/.globus/ user@host $ chmod go-rwx ~/.globus/userkey.pem ~/.globus/usercred.p12 In order to find the Distinguished Name (DN), issuer and lifetime of a certificate: user@host $ openssl x509 -in ~/.globus/usercert.pem -noout -subject -issuer -enddate To generate a proxy use the command voms-proxy-init . user@host $ voms-proxy-init Revoking Your User Certificate \u00b6 If the security of your certificate or private key has been compromised, you have a responsibility to revoke the certificate. In addition, if your name or email address changes, you must revoke your certificate and get a new one with the correct information. If you have a CILogon issued certificate, contact ca@cilogon.org in order revoke your certificate. If you received a certificate from another CA, please contact the CA to initiate a certificate revocation.","title":"User Certificates"},{"location":"software/user-certs/#user-certificates","text":"Note This document describes how to get and set up a personal certificate (also called a grid user certificate). For instructions on how to get host certificates, see the Host Certificates document .","title":"User Certificates"},{"location":"software/user-certs/#getting-a-user-certificate","text":"This section describes how to get and set up a personal (user) certificate. A user certificate is a type of SSL certificate -- the same technology used for identifying websites when using HTTPS -- but identifying a human instead of a host. This is used to access some grid resources, such as: OSG Topology (for viewing private contact information) The osg-notify tool for sending mass emails The GGUS ticketing system The Koji build system for the OSG Software Stack User certs may also be useful for debugging storage access (such as XRootD). Currently, you can get a user certificate from CILogon.","title":"Getting a User Certificate"},{"location":"software/user-certs/#know-your-responsibilities","text":"If your account or user certificate is compromised, you must notify the issuer of your certificate. In addition, you should update your certificate and revoke the old certificate if any of the information in the certificate (such as name or email address) change. For the CILogon RA send email to ca@cilogon.org . Additional responsibilities required by the CILogon CA are given on their page .","title":"Know your responsibilities"},{"location":"software/user-certs/#getting-a-certificate-from-cilogon","text":"You will have to obtain your user certificate using the CILogon web UI . Follow the steps below to get an user certificate: Open the CILogon page, https://cilogon.org , in your browser of choice First, either search for your institution and select it or scroll through list and do the same. . Warning Do not use Google, GitHub, or ORCID as providers since they are not widely supported in the OSG. If your institution is not on the list, please contact your institution's IT support to see if they can support CILogon. Click the Log On button and enter your institutional credentials if prompted. After successfully entering your credentials, click on the \"Create Password-Protected Certificate\" link Enter a password that is at least 12 characters long and then click on the Get New Certificate button. Click the Download Your Certificate button to download your certificate in .p12 format. The certificate will be protected using the password you entered in the previous step.","title":"Getting a certificate from CILogon"},{"location":"software/user-certs/#certificate-formats","text":"Your user certificate can be stored in a few different formats: CILogon will give you a certificate in the PKCS12 format (file extension .p12 ). The PKCS12 format stores the certificate and private key in a single file along with an optional certificate chain. This is the file format that can be loaded into your browser for accessing Topology, GGUS, or the Koji web interace with. Most command line tools use the PEM format (file extension .pem ). The PEM format stores the public certificate in one file, and the private key in another file. To convert a PKCS12 file to PEM files, do the following: First, extract your user certificate from your PKCS12 file by running the following command. You'll be prompted for the password you used to create the certificate. The invocation assumes that the PKCS12 file is called usercred.p12 . After running, the PEM certificate will be written to usercert.pem . user@host $ openssl pkcs12 -in usercred.p12 -out usercert.pem -nodes -clcerts -nokeys Enter Import Password: MAC verified OK Second, extract the private key by running the following command. You'll be prompted for two different passwords. The first prompt will be for the password that you used to create the certificate. The second prompt will be for the password that will encrypt the PEM certificate that will be created. As before, the invocation assumes that your PKCS12 certificate is located in usercred.p12 . After running, the PEM certificate with your private key will be written to userkey.pem . user@host $ openssl pkcs12 -in usercred.p12 -out userkey.pem -nocerts Enter Import Password: MAC verified OK Enter PEM pass phrase: Verifying - Enter PEM pass phrase:","title":"Certificate formats"},{"location":"software/user-certs/#using-your-user-certificate","text":"The standard location to place user certificates is in the .globus subdirectory of your home directory: user@host $ mkdir -p ~/.globus user@host $ cp userkey.pem ~/.globus/ user@host $ cp usercert.pem ~/.globus/ user@host $ cp usercred.p12 ~/.globus/ user@host $ chmod go-rwx ~/.globus/userkey.pem ~/.globus/usercred.p12 In order to find the Distinguished Name (DN), issuer and lifetime of a certificate: user@host $ openssl x509 -in ~/.globus/usercert.pem -noout -subject -issuer -enddate To generate a proxy use the command voms-proxy-init . user@host $ voms-proxy-init","title":"Using Your User Certificate"},{"location":"software/user-certs/#revoking-your-user-certificate","text":"If the security of your certificate or private key has been compromised, you have a responsibility to revoke the certificate. In addition, if your name or email address changes, you must revoke your certificate and get a new one with the correct information. If you have a CILogon issued certificate, contact ca@cilogon.org in order revoke your certificate. If you received a certificate from another CA, please contact the CA to initiate a certificate revocation.","title":"Revoking Your User Certificate"}]} \ No newline at end of file diff --git a/sitemap.xml b/sitemap.xml index f47435d37..7501baac6 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1,903 +1,907 @@ <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url> <loc>https://osg-htc.org/technology/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/rpm-development-guide/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/osg-build-tools/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/quilt/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/upcoming-to-main/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/koji-workflow/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/create-vo-client/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/container-development-guide/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/repository-management/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/resurrecting-epel-packages/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/koji-mass-rebuilds/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/development-process/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/git-software-development/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/ce-test-scaling/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/ipv6-testing/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/requesting-tokens/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/ospool-containers/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/operations/comanage/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> + <changefreq>daily</changefreq> + </url><url> + <loc>https://osg-htc.org/technology/software/comanage-troubleshooting-guide/</loc> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/software-support/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/effort-tracking/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/release-planning/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/new-team-member/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/software/user-certs/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/cut-sw-release/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/announce-rft-packages/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/new-release-series/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/new-os-series/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/release-eol/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/itb-testing/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/empty-pkgs/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/release/acceptance-testing/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/gridftp-gsi-migration/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/campus-cyberinfrastructure/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/collab-bearer-tokens/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/cream-support/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/globus-toolkit/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/external-oasis-repos/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/flexible-release-model/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/software-release/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/container-release/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/community-testing/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/new-ospool-user/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/topology-registration/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/documentation/writing-documentation/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/documentation/reviewing-documentation/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/documentation/style-guide/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/documentation/publish-osg-pages/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/service-migrations-spring-2018/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/gums-retire/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/bestman2-retire/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/policy/voms-admin-retire/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/projects/sha2-support/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/documentation/markdown-migration/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2024/TechArea20240109/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2024/TechArea20240102/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231219/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231212/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231205/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231128/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231114/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231107/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231031/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231024/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231017/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231010/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20231003/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230926/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230919/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230905/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230829/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230815/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230808/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230801/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230725/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230718/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230627/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230620/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230613/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230606/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230530/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230523/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230516/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230509/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230418/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230404/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230328/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230314/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230221/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230221/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230214/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230207/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230131/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230124/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230117/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2023/TechArea20230103/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221220/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221213/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221206/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221129/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221122/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221115/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221108/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221101/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20221004/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220927/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220920/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220913/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220906/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220830/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220823/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220816/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220809/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220802/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220726/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220628/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220621/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220607/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220531/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220510/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220503/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220426/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220419/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220405/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220329/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220322/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220308/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220301/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220222/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220208/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220201/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220125/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220118/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220111/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2022/TechArea20220104/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211214/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211207/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211130/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211123/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211116/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211109/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211102/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211026/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211019/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211012/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20211005/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210928/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210914/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210907/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210831/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210824/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210817/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210810/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210803/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210727/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210720/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210713/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210706/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210629/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210622/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210615/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210608/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210518/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210511/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210504/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210420/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210413/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210406/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210330/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210323/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210309/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210302/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210223/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210216/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210209/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210202/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210126/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210119/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210112/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2021/TechArea20210104/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201221/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201214/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201207/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201130/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201123/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201116/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201109/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201102/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201026/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201019/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201012/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20201005/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200928/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200914/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200824/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200817/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200810/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200803/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200727/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200720/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200713/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200706/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200629/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200622/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200615/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200608/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200601/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200518/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200511/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200504/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200427/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200420/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200413/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200406/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200330/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200323/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200316/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200309/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200302/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200224/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200217/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200210/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200203/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200127/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200113/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url><url> <loc>https://osg-htc.org/technology/meetings/2020/TechArea20200106/</loc> - <lastmod>2024-01-09</lastmod> + <lastmod>2024-01-12</lastmod> <changefreq>daily</changefreq> </url> </urlset> \ No newline at end of file diff --git a/sitemap.xml.gz b/sitemap.xml.gz index 6f8465c17..7c1ab3624 100644 Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ diff --git a/software/ce-test-scaling/index.html b/software/ce-test-scaling/index.html index ad4e515a6..7ee57ab16 100644 --- a/software/ce-test-scaling/index.html +++ b/software/ce-test-scaling/index.html @@ -667,6 +667,18 @@ + + + + + <li class="md-nav__item"> + <a href="../comanage-troubleshooting-guide/" class="md-nav__link"> + COmanage Troubleshooting Guide + </a> + </li> + + + </ul> </nav> </li> diff --git a/software/comanage-troubleshooting-guide/index.html b/software/comanage-troubleshooting-guide/index.html new file mode 100644 index 000000000..c6ca9ac7c --- /dev/null +++ b/software/comanage-troubleshooting-guide/index.html @@ -0,0 +1,3488 @@ + +<!doctype html> +<html lang="en" class="no-js"> + <head> + + + <meta charset="utf-8"> + <meta name="viewport" content="width=device-width,initial-scale=1"> + + + + + <link rel="canonical" href="https://osg-htc.org/technology/software/comanage-troubleshooting-guide/"> + + <link rel="icon" href="../../img/favicon.ico"> + <meta name="generator" content="mkdocs-1.1.2, mkdocs-material-7.1.0"> + + + + <title>COmanage Troubleshooting Guide - OSG Technology Area + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + +
    + +
    + +
    + +
    + + + + +
    +
    + + + +
    +
    +
    + + + + +
    +
    +
    + + + +
    +
    +
    + + +
    +
    +
    + + +
    +
    + + + + + + + +

    COManage Troubleshooting Guide

    +

    A resource for COManage administrators to find solutions to commonly encountered problems.

    +

    COManage Troubleshooting Items

    +

    This section contains some of the issues you may encounter when interacting with the OSG COManage.

    +

    Valid Tiger User is unauthorized with Dex credentials

    +

    Under certain circumstances Dex may not be able to match a user to their COManage identity, + possibly due to incorrect and/or missing organization identities/identifiers.

    +

    Symptoms

    +
      +
    • Tiger-Dex credentials missing some or all of a users group permissions.
      • +
    • User unable to connect to the Tiger cluster.
      • +
    • +

      Error message from Tiger involving an unauthorized user.

      +
        +
      • Example error message:
        • +
      +
      +

      kubectl get pods -n osg-dev

      +

      Error from server (Forbidden): pods is forbidden: User "user@email.edu" cannot list resource "pods" in API group "" in the namespace "osg-dev""

      +
      +
      • +
    • +

      Empty groups in the Dex response after logging in with SSO

      +
      • +
    +

    Next actions

    +
      +
    1. Ensure that the user's LDAP record contains the attribute uid, + which shares the same value as the COManage identifier used as a source for the LDAP provisioner target.
        +
      • LDAP attributes and their COManage sources can be found here
        • +
      +
      2. +
    2. Have the user log in
      3. +
    3. Have the user fetch a new Dex token
      4. +
    +

    Explanation of SAML -> CILogon OIDC sub claim -> LDAP matching used in Dex.

    +

    How the OAuth2 server does the following:

    +
      +
    1. Receives appropriate SAML attributes from the campus Identity provider.
      2. +
    2. Uses those attributes to find the user in the CILogon user database, + from which the CILogon OIDC sub claim is obtained.
      3. +
    3. Performs an LDAP search using a filter of (uid=<CILogon OIDC sub claim value>).
      4. +
    4. Retrieves configured LDAP attributes from the record it has found, + and sends those values out as claims with names as configured.
      5. +
    + + + + + + + +
    +
    +
    + +
    + + + + +
    +
    +
    +
    + + + + + + + + \ No newline at end of file diff --git a/software/container-development-guide/index.html b/software/container-development-guide/index.html index 6e8c89813..cea7b0d79 100644 --- a/software/container-development-guide/index.html +++ b/software/container-development-guide/index.html @@ -667,6 +667,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/create-vo-client/index.html b/software/create-vo-client/index.html index 8dbef3365..0551b444e 100644 --- a/software/create-vo-client/index.html +++ b/software/create-vo-client/index.html @@ -628,6 +628,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/development-process/index.html b/software/development-process/index.html index fceeea082..cc993b802 100644 --- a/software/development-process/index.html +++ b/software/development-process/index.html @@ -688,6 +688,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/effort-tracking/index.html b/software/effort-tracking/index.html index 31b14bff1..304772840 100644 --- a/software/effort-tracking/index.html +++ b/software/effort-tracking/index.html @@ -539,6 +539,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/git-software-development/index.html b/software/git-software-development/index.html index f551d0c66..c125e68a1 100644 --- a/software/git-software-development/index.html +++ b/software/git-software-development/index.html @@ -784,6 +784,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/ipv6-testing/index.html b/software/ipv6-testing/index.html index f2ba3661c..8a7f34d85 100644 --- a/software/ipv6-testing/index.html +++ b/software/ipv6-testing/index.html @@ -653,6 +653,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/koji-mass-rebuilds/index.html b/software/koji-mass-rebuilds/index.html index e43ed374d..489b55cbe 100644 --- a/software/koji-mass-rebuilds/index.html +++ b/software/koji-mass-rebuilds/index.html @@ -654,6 +654,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/koji-workflow/index.html b/software/koji-workflow/index.html index eb2e322ae..197b3d4c3 100644 --- a/software/koji-workflow/index.html +++ b/software/koji-workflow/index.html @@ -715,6 +715,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/new-team-member/index.html b/software/new-team-member/index.html index 53833c65f..c7cbe2c41 100644 --- a/software/new-team-member/index.html +++ b/software/new-team-member/index.html @@ -539,6 +539,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/osg-build-tools/index.html b/software/osg-build-tools/index.html index 7e80c8e3e..8f41a7a70 100644 --- a/software/osg-build-tools/index.html +++ b/software/osg-build-tools/index.html @@ -1155,6 +1155,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/ospool-containers/index.html b/software/ospool-containers/index.html index e8ae48469..b2a08e814 100644 --- a/software/ospool-containers/index.html +++ b/software/ospool-containers/index.html @@ -600,6 +600,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/quilt/index.html b/software/quilt/index.html index c67a40802..5ec426b01 100644 --- a/software/quilt/index.html +++ b/software/quilt/index.html @@ -550,6 +550,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/release-planning/index.html b/software/release-planning/index.html index 7e134e8a4..bc4acf5b9 100644 --- a/software/release-planning/index.html +++ b/software/release-planning/index.html @@ -539,6 +539,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/repository-management/index.html b/software/repository-management/index.html index b42175a80..7548a2221 100644 --- a/software/repository-management/index.html +++ b/software/repository-management/index.html @@ -593,6 +593,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/requesting-tokens/index.html b/software/requesting-tokens/index.html index 69dc444de..d2cee15a8 100644 --- a/software/requesting-tokens/index.html +++ b/software/requesting-tokens/index.html @@ -654,6 +654,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/resurrecting-epel-packages/index.html b/software/resurrecting-epel-packages/index.html index fbbc39102..5d1701ff2 100644 --- a/software/resurrecting-epel-packages/index.html +++ b/software/resurrecting-epel-packages/index.html @@ -619,6 +619,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/rpm-development-guide/index.html b/software/rpm-development-guide/index.html index 02ebfcd68..ffc3a7d9c 100644 --- a/software/rpm-development-guide/index.html +++ b/software/rpm-development-guide/index.html @@ -898,6 +898,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/upcoming-to-main/index.html b/software/upcoming-to-main/index.html index f7c2bdd58..bbe60b840 100644 --- a/software/upcoming-to-main/index.html +++ b/software/upcoming-to-main/index.html @@ -550,6 +550,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + + diff --git a/software/user-certs/index.html b/software/user-certs/index.html index 60acd95a1..dd6b22487 100644 --- a/software/user-certs/index.html +++ b/software/user-certs/index.html @@ -539,6 +539,18 @@ + + + + +
  • + + COmanage Troubleshooting Guide + +
    • + + +