Discuss with UWA IT on production database

[frinzekt]

As part of being in the UWA IT infrastructure, a conversation with IT has to be done before putting any software in the cloud in production state.

However, be ready to note that the options for the production database will either be the VPS (less likely due to storage and recoverability) or Mongo Atlas (as stated in the requirements document)

[frinzekt]

I have started the conversation with Uni IT

[frinzekt]

Atlas mongo it is

[frinzekt]

@mhodki I have not yet provisioned a cloud database, currently the indeaa.systemhealthlab.com/ deployment is linked to my own personal account at Atlas Mongo. I would like to transfer this to another account closer to SHL.

[mhodki]

Let me know what you need to do this and if we need to set something up in SHL, whatever you think is best for now and to support this in the future

[frinzekt]

@mhodki I need to create a new account here at Atlas Cloud Mongo, the pricing can be seen https://www.mongodb.com/pricing . I recommend the "shared" plan. I doubt we will even get 512 MB of storage because we store the files in google drive. However, in the scenario that we do expand... it can expand up to 5 gb ( $25/mo ) or 2 gb ( $9/mo ).

The only thing stored in the Mongo DB are the information such as the reviews and things... but those usually are very insignifcant in size. From Marcus's original proposal, he planned to store the files in MongoDB... Hence the cost estimate, but I changed it such that we upload in google drive for simplicity (atleast for MVP). This can be later decided, but even then for scalability, file are usually not stored in Databases, but rather File servers... (in terms of the OurLabTraining, it uses two storages - the Amazon S3 Bucket and Atlas Mongo Database).

Furthermore, I reviewed the Atlas Mongo Database for the ourlabtraining... I think that database is still in Fraser's account, but we have the Amazon S3 bucket is on a separate account. At the moment, I don't mind having the database on my account, but I just think its best practice to change that.

I have two main choices... either I create a new gmail account to link with the atlas cloud account for use specifically for IndEAA (i recommend this) or I register it on the systemhealthlab@gmail.com email. The only downside with my recommendation is that... its another gmail acount. Furthermore, I also have to migrate a couple of google oauth keys.

[mhodki]

Ho Frinze I think we can manage another account as long as it goes into our LastPass. I’d like to chat to ben. Also I’d like to move away in any reliance on individual accounts such as both yours and Fraser’s.

Let’s chat after Ben has had a chance to comment M

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Frinze Erin Lapuz notifications@github.com Sent: Wednesday, February 3, 2021 18:03 To: uwasystemhealth/IndEAA Cc: Melinda Hodkiewicz; Mention Subject: Re: [uwasystemhealth/IndEAA] Discuss with UWA IT on production database (#5)

@mhodkihttps://github.com/mhodki I need to create a new account here at Atlas Cloud Mongo, the pricing can be seen https://www.mongodb.com/pricing . I recommend the "shared" plan. I doubt we will even get 512 MB of storage because we store the files in google drive. However, in the scenario that we do expand... it can expand up to 5 gb ( $25/mo ) or 2 gb ( $9/mo ).

The only thing stored in the Mongo DB are the information such as the reviews and things... but those usually are very insignifcant in size. From Marcus's original proposal, he planned to store the files in MongoDB... Hence the cost estimate, but I changed it such that we upload in google drive for simplicity (atleast for MVP). This can be later decided, but even then for scalability, file are usually not stored in Databases, but rather File servers... (in terms of the OurLabTraining, it uses two storages - the Amazon S3 Bucket and Atlas Mongo Database).

Furthermore, I reviewed the Atlas Mongo Database... I think that database is still in Fraser's account, but we have the Amazon S3 bucket is on a separate account.

I have two main choices... either I create a new gmail account to link with the atlas cloud account for use specifically for IndEAA (i recommend this) or I register it on the systemhealthlab@gmail.commailto:systemhealthlab@gmail.com email. The only downside with my recommendation is that... its another gmail acount. Furthermore, I also have to migrate a couple of google oauth keys.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/uwasystemhealth/IndEAA/issues/5#issuecomment-772387553, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADDQ35YQZMGB2Q5IXC5BJC3S5ENPNANCNFSM4UTMTQ4Q.

[frinzekt]

I think this will also be a great chance to migrate the mongo database in the VPS. To raise an awareness, last week the UWA dental school system crashed and frustrated many students at around January 27-28.

This system has been identified to be reliant on one of our services Pheme API, furthermore, the reason why Pheme API crashed is due to the system using the mongo database in the VPS which crashed when University IT updated our system. This can be seen https://uptime.systemhealthlab.com/ . So I do highly recommend that we migrate all our database in the cloud.

To reiterate from many weeks ago when I was starting deployment on IndEAA, I have accidentally crashed Pheme API and Binchook which seems to be because those are the only 2 services that relies on that mongo database in the VPS.

[frinzekt]

As written in this thread, UWA IT cannot provide a production database. Hence SHL needs to get an account that can be used for production deployment database.

I will be closing this and reopening a new issue. See #135