2020-11-03 Meeting
Attendees:
@Stephanie Ayers
@Esmé Cowles
@Kate Lynch
Notes:
Initial meeting to discuss feasibility of a Library IT Sunsetting Group
Devices to hopefully sunset:
LibDBServer -> a little planning now might make sunsetting in the future a little easier
LibServer64
Meridian (this might be the most at-risk)
Supplemental Catalog
Kevin has a catalog somewhere of miscellaneous services that we could retire or port to other systems.
We are doing our best to work with stakeholders on an ad hoc basis and are generally doing a good job, but we could always have a group that helps coordinate this.
Having an owner for every service so you at least have someone you could go to, in order to learn more about an application, would be great.
Working group:
Define processes, work on the service catalog
Are there pieces of infrastructure that we’re looking to retire sooner than later?
Solr 7 boxes should be updated to 8.
Some servers still using the old database clusters.
Making sure we know who the owners are, and that they’re notified when something is migrated or turned off.
What applications are going away with Alma? Would be good to get a confirmation that this is going away.
Looking forward to shutting down PULFA and PUDL
Good for this group to be a potential consultant for content migration projects.
Checking with stakeholders for what is acceptable strategy, how to migrate.
Next steps:
Goals:
Unified service catalog
Identify an owner for each thing without getting bogged down in application, service, server-level ownership.
Develop a sunset or migration evaluation procedure agnostic of applications
Figure out what applications/services are being replaced with Alma.
Stephanie
Esmé
Kevin
Kate
Others on an as-needed basis (there will be a lot of this collaboration)
Draft a summary of work, make sure JS is aware but we don’t need to be a Steering Group.
Sunsetting Group
Plan for kickoff in early December ASAP.
Initial team:
Service Catalog