/
2018-03-22 - System Operations and Management SIG Notes

2018-03-22 - System Operations and Management SIG Notes

Mar 22, 2018

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
5 minDetermine note taker


5 minReview outstanding action items  

  1. Wayne with a WOLFcon update (week of May 7th)

    1. Conflict on Monday (dev ops meeting conflict against Folio fall upon)

      1. John M. and Wayne won’t be available for first half, but we have a slot

    2. Tuesday: two hour slot for data migration process flow 10-1230p

      1. 4-5 data cleanup slot

    3. Wednesday: two hour slot combined w/ dev ops meeting

      1. Deployment and orchestration topics

    4. Hotel blocks should be communicated soon

    5. Monday morning will be travel time (start time 130p on Monday)

      1. Reception Monday evening

    6. Thursday will be left open, intentionally

    7. Data migration discussion will need carefully crafted meeting (potential agenda item)

      1. Data mapping should be avoided, with preference for tools

  2. Okapi dependencies for deployment

    1. Speeding up okapi pull (disabled dependency checking when loading module descriptors)

    2. Includes launch descriptors: don’t need to post deployment descriptor anymore

      1. Okapi will launch using module descriptors it has access to

    3. TAMU request easier okapi to tell you what modules you need to support front end

      1. DNS based service discovery (based on URL) to point to load balance service

    4. Comments: Stephen P.: needs more time for testing (future item)

      1. Wayne: mod permissions bug yesterday will require him to update documentation

      2. C Creswell: Deployment w/o Okapi: multiple nodes deployment database location finding?

        1. Env variables set in container, should be able to locate DB

        2. Command line launch config or using config file for DB

        3. Roml module builder is lengthy but useful

          1. Notes encrypt credentials

          2. Look for Github roml/module/builder/read.m

45 minContinue discussion of local install experiences

  1. Local install concerns

    1. C. Creswell: https single node install broken (second from TAMU)

      1. Stripes hard coded http assumptions may exist

      2. Wayne will attempt to reproduce based on use case, and create Jira bug

        1. Email use case to Wayne

        2. Okapi not served on port 80 may hang

      3. Certificate config?

        1. Development team didn’t intend for anything but reverse proxied, but even this broke behind nginx as http backend (Cresewell)

          1. There is no stripes application on the backend, this should cause a mixed http https error

        2. Stephen tried 301 redirect

      4. Wayne will build broken vagrant box as a recreation env, give to devs

5 minTopics for next meeting

Action items