Skip to content

Telcon: 2022 07 13

Jump to bottom Edit New page
Peter Scheibel edited this page Jul 13, 2022 · 8 revisions

Attendees

  • Peter Scheibel (host)
  • Massimiliano Culpo
  • Davide DelVento
  • Phil Regier
  • Brian Van Essen
  • Tammy Dahlgren
  • Todd Gamblin

Agenda items

  • Davide: how to make a test environment
    • Make a change
    • Want to make sure it works before updating the production environment
    • For now maintaining two copies (they are in lockstep; to update the production instance - first try changing the test instance and then if it works you can change the production instance)
      • In other words, having a "rollback" option would be useful
      • This can be achieved with spack env:
        • If you version control the associated spack.lock file (in addition to the spack.yaml file) then if you make a change in the production instance and it fails, then you can copy spack.lock over
        • Caveat: you may have to module refresh
  • Peter: see https://github.com/spack/spack/discussions/31525, which is intended to be useful for people working with the develop branch of Spack
  • Phil: 30385 (os option in containerize)
    • Todd: could we turn the container section into a normal config section?
      • If that were supported then the user could control OS with -C
    • spack ci might also be helpful for the use case this is directed at
      • See share/spack/gitlab/ in the Spack repository
    • Massimiliano: will check into it
  • Davide:
    • If you have several versions of Python and each has py-numpy, can we update the Lmod MODULEPATH hierarchy to treat Python as a component of the hierarchy?
    • Right now no: compilers and virtual packages can be hierarchy components, but not necessarily extend-able packages

Possible Agenda items

Add a custom footer
Clone this wiki locally