Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document rules for upgrading CSC servers #8

Open
nharraud opened this issue Nov 2, 2017 · 0 comments
Open

Document rules for upgrading CSC servers #8

nharraud opened this issue Nov 2, 2017 · 0 comments
Assignees

Comments

@nharraud
Copy link
Contributor

nharraud commented Nov 2, 2017

Problem:
We need to have a workflow and a set of rules explaining which conditions are required to update training and production servers.
The goal is to improve our worklows and crash recovery time.

Example of information:

  • The first step of any B2SHARE release is to deploy it on a test server. This test server should have a backup of b2share.eudat.eu loaded in order to test the migration.
  • The training server is used by EUDAT users and communities. The data should not be wiped and it should only be updated when a new release of B2SHARE has been tested on a test server.
  • Send an email to ... which is in charge of backups at CSC in order to have them ready before upgrading the server. (getting a backup of the files can take some time).

I suggest to create a wiki page on this repository.

@emanueldima @Tlacahuepan @thijscobben @SarahBA @dinosk

@nharraud nharraud self-assigned this Nov 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant