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

Restore Nimbus Back To Life With Better Docs && Backups #190

Open
4 of 5 tasks
mfekadu opened this issue Aug 2, 2020 · 8 comments
Open
4 of 5 tasks

Restore Nimbus Back To Life With Better Docs && Backups #190

mfekadu opened this issue Aug 2, 2020 · 8 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@mfekadu
Copy link
Member

mfekadu commented Aug 2, 2020

Objective

Use our current opportunity to improve documentation && reliability of Nimbus

Key Result

  • Run through the MySQL setup documentation to deploy the MySQL server.
    • see if anyone has manual backups on their local machines
  • Discuss && consider updating the MySQL setup docs
  • Recreate the API VM instance on GCP
  • Set up snapshots on GCP to promote #reliability

Details

  • ??
@mfekadu mfekadu added documentation Improvements or additions to documentation enhancement New feature or request labels Aug 2, 2020
@mfekadu
Copy link
Member Author

mfekadu commented Aug 2, 2020

Discuss && consider updating the MySQL setup docs

notes from MySQL setup docs in Wiki
  1. MySQL is taught to Cal Poly Computer Science students in CSC 365
  2. MySQL is reportedly used by large software companies, which suggests it is reliable, scalable, and maintainable
  3. MySQL's relational model of storing data allows it to represent the relations between relevant objects. See the database schema
    (e.g., Dr. Khosmood's entry in the Professors table might have a relation to many entries in the Courses table and vice-versa. This is known as a many-to-many relation.)

@mfekadu
Copy link
Member Author

mfekadu commented Aug 2, 2020

Set up snapshots on GCP to promote #reliability

https://cloud.google.com/compute/docs/disks/create-snapshots

@snekiam
Copy link
Member

snekiam commented Aug 2, 2020

Recap of what got us here:

Our instances on GCP had 'test' in their names, and we didn't setup snapshots. While cleaning up some instances in our GCloud account, our 'test' instances were removed, since there was confusion about which instances were actually being used. Since we had no snapshots, our database was gone.

We should setup our infrastructure so if an instance does get deleted, it does not cause data loss, and only causes us to need to recreate the instance and restore a backup.

@mfekadu
Copy link
Member Author

mfekadu commented Aug 2, 2020

Run through the MySQL setup documentation to deploy the MySQL server.

We are now considering CloudSQL instead of the Compute Engine way of managing MySQL as seen in the MySQL wiki doc

@snekiam
Copy link
Member

snekiam commented Aug 2, 2020

Info on cloud sql: https://stackoverflow.com/a/34030484/13291759

@mfekadu
Copy link
Member Author

mfekadu commented Aug 2, 2020

good reasons for CloudSQL

image

image

@snekiam
Copy link
Member

snekiam commented Aug 8, 2020

How far did we get last week?

@snekiam
Copy link
Member

snekiam commented Aug 9, 2020

The database is restored! We're working on geting the API back up now. GCP seems to be running backups now automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants