-
Notifications
You must be signed in to change notification settings - Fork 0
03.15.2021 TT Agenda
Nic edited this page Mar 15, 2021
·
2 revisions
@nniicc @adam3smith @stahs @qqmyers
Admin
- Intelligetnt tiering for S3 storage
- From JM on slack https://teamqdr.slack.com/archives/C3R3U99L5/p1615299472015900 -- In short, whats the downside?
Seba & Jim Coordination
- SSH vulnerability (We should be covered behind vpn)
Jim
- Report
-
- Datacite Metadata
-
- Anno-rep updates
- SSH vulnerability on Debian - we have no attack surface (ssh is not available) because of VPN configuration of QDR
- Java 11 was on stage - JM did some Payara tweaks
Seba
- Fleshed out how to backup from ICT instance in Infra documentation
- Provisioning back up needs to have some downtime to combine volumes ...
-
- Seba will do on Prod first and then stage ...
-
- Last time we did this - we did early evening ET (8pm EST) ... 6pm central ... Tuesdays or Friday ...
Jim
- Restoring data... We have files with funny names out on Dev, we have zip with actual names on Dev...
- Everything is restored in Prod
- Anno-rep - JM will have API finished later this week so To can see... We're waiting for Versal to get back to us on free OSS
SK
- Contact box ... People are contacting depositors about things that should be directed to QDR
-
- How hard will it be in contact form to toggle between depositor + repository ... ?
-
- (In short - default is that the request goes to both)
-
- JM thinks this is a default DV form, so we just need to mess with a parameter there - should not be hard.
Decisions
- Enable Intell S3 storage - we'll configure and start using
- There is even a colder (more remote) storage - we could configure in future
To do:
- JM will put banner up for maintenance on stage and SK
- JM will clean up restored files from last week living on Dev (no longer needed)
- SK will open a ticket / issue with IQSS to discuss default contact notification (see discussion above)
- Seba to prep and execute re-provisioning pre-work on Friday