2018-04-26 - System Operations and Management SIG Agenda and Notes

Craig McNally has worked with AWS as deployment platform, will see what else he can share.

We have some existing documentation that we can build on:

List of technologies for deployment available on wiki: Deployment Environments (general overview). Wayne Schneider and Mike Gorrell will look at reorganizing page.

Wiki page for SIG member environments: Deployment Environments in SIG members' institutes

Session at WOLFcon will focus on common orchestration patterns and tooling, with goal of settling on standards for the community.

1. Install issues

1. Dale A and Chris C. are both having an issue getting Okapi/Folio to connect to postgres in single node deployment

2. Okapi and service discovery tool

1. Stephen P: asked if we should ask developers to use a service discovery tool, rather than the current Okapi setup

2. Individual microservices not typically aware of system, except self

1. Okapi is currently arbiter of microservices

2. Application shouldn’t manage its own state

3. Okapi has no sense of HA backend services

1. Can’t tell it to spin up multiple copies of service

4. Need backend module register itself with discovery service, at URL

1. Okapi would talk to discovery service like etcd or console

2. Would help with load balance abilities

3. Most orchestration tools assume service discovery tool, which Okapi doesn't currently have

1. Proxied okapi request for circ data, what happens?

2. How does Okapi know where that service URL is located?

3. Okapi was designed to be agnostic to service discovery

4. Wayne recommends current smoother path to use DNS based launch/deployment descriptors, rather than service discovery tool

1. How much orchestration do we want Okapi to do?

2. Difficult previously to have use-cases to give developers.

3. What will it use other than URL for mod-circ?

4. Brandon:  We don’t want Okapi as orchestration tool, only a proxy; too dynamic

1. Rather make Okapi work better w/ orchestration tools

2. Wayne: Module registration is unavoidable in Okapi

3. Give Okapi discovery service information ability

4. Stephen: modules should be able to self-register to discovery service rather than posting to Okapi

5. How do I know what I am supposed to run?

1. Build front-end first, then back-end

2. This is backwards

3. However, in multi-tennant Front-end first may be more appropriate, according to Wayne

3. Other external tools Okapi needs in production environment?

1. Smaller libraries have smaller needs

2. General monitoring/ Dashboard

3. log files

4. SSO

2. Next meeting:

1. Touch base on Wolf-Con final agenda

2. Desired Wolfcon outcomes? Will help us have more conference discussions

3. Wolf-con logistics; have we confirmed locations for sessions?

1. Hotel 21?

2. Install fest should also be at hotel21, but confirmation needed