• Created by Unknown User (pdomagala), last modified on Jul 07, 2017

Infrastructure meetings take place every other Thurs. at 9:00 Pacific on the BlueJeans infrastructure-meeting channel: https://bluejeans.com/383721668

Date

Goals

  • Alignment of NCSA-provided services with program needs
  • Ensure effective use of the current NCSA infrastructure
  • Refinement and continuous improvement of services, resources and processes
  • Plan for near- and medium-term activities

Discussion items

ItemWhoNotes
Review of last meeting notes and outstanding taks

Unknown User (pdomagala)

Ticket Review

  • SSL cert for http://lsst-sui-proxy01.ncsa.illinois.edu is on its way.

    • also added lsst-sui-proxy.ncsa.illinois.edu and lsst-sui.ncsa.illinois.edu CNAMEs to the cert for your convenience

    • Questions:

      • Is the Apache config relatively stable on this machine yet?

        • stable, but will have a need to modify proxy file

      • Will Apache be locally installed on the machine down the line (i.e., as opposed to being put into a Docker container)?

        • i.e. should we puppetize Apache?

        • Likely to be a Docker container somewhere in the not too distant future

  • qserv-master upgrade status

    • quotes are flying

    • the price tag is pretty steep. ~$20k

Monitoring
IN2P3 has some fairly robust monitoring, should connect Harathi w/ Fabian

DAQ Status

All


lsst-dev resource management

Unknown User (pdomagala)

Discussion: Do we need a policy and implementation mechanisms?



PDAC StatusGregory Dubois-Felsmann
Topics for next meeting



Action items

Please enter action items in the form

Responsible Person, Due Date, Description

  • IN2P3 has some fairly robust monitoring, should connect Harathi w/ Fabian  (Paul)

2 Comments

  1. Gregory Dubois-Felsmann

    For the record, a few open items that I understand were discussed during the meeting:

     

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Refresh

  2. Unknown User (pdomagala)

    Realize that qserv-master was left out of the original spec so the sysadmins plugged that gap the best they could by repurposing a SUI node.  Definitely sub-optimal.  A new, purpose-built machine will provide the necessary performance and have a usable life of 3-5 years assuming the requirements don't change drastically.  Working on our side to see if we have sufficient equipment budget to cover this.