mclconsortium / mcl-site Goto Github PK

🐛 Describe the Bug

Previously, we could access var paths using mcl.nci.nih.gov/var and get to the database journal file (filestorage), the blob hierarchy (blobstorage) and the log files (log).

Now that AWS hosts the MCL site, these are in three separate URL endpoints:

• https://mcl.nci.nih.gov/logs/
• https://mcl.nci.nih.gov/blobstorage/
• https://mcl.nci.nih.gov/filestorage/

The sync operation will need to be refitted to use these.

🤔 Tell Us About the Feature

This isn't a "feature" so much as paperwork. We need to fill out and submit everything at: https://wiki.nci.nih.gov/display/NSCI/FISMA+Security+Templates+and+Forms

🗺 Context

🤮

🤔 Tell Us About the Feature

Move to Amazon Web Services.

🎇 What Solution You'd Like

Same as EDRN.

〽️ Alternative Ideas

Google Cloud?

🗺 Context

The old host in Shady Grove can no longer be maintained.

5 second page load doing simple navigation after logging in.

🤔 Tell Us About the Feature

The EC2 external IP that runs the portals changes from time to time and the edrn-ds.jpl.nasa.gov directory blocks them when they change. This prevents logins.

🎇 What Solution You'd Like

We need a way to make sure logins work on the portals. Alleviam is an idea.

As part of the IDEA Act, public websites must include the Digital Analytics Program (DAP). MCL is no exception.
DAP.zip

🐛 Describe the Bug

When Chelsey adds a new user, the page doesn't load. The issue seems to be a JavaScript stack trace when loading a modal.

📜 How To Reproduce

1. Visit https://mcl.nci.nih.gov/login and log in with a Manager account.
2. Click Site Setup in the personal tools.
3. Click Users and Groups.
4. Click "Add New User".
5. Nothing seems to happen.

🔎 Expected Behavior

The new user form should appear.

🖼 Screenshots

🕵️‍♀️ Extra Details

Workaround: visit https://mcl.nci.nih.gov/@@new-user directly.

🤔 Tell Us About the Feature

The CentOS 6 hosting platform used at NCI for the website of the Consortium for Molecular and Cellular Characterization of Screen-Detected Lesions is going to be retired at the end of October 2020. In order to be ready for this, we need to migrate the Consortium for Molecular and Cellular Characterization of Screen-Detected Lesions website to the Amazon Web Services "GovCloud" platform used at NCI, known as "CloudOne".

🎇 What Solution You'd Like

Essentially we should use the same approach as for EDRN's P5 site.

〽️ Alternative Ideas

None.

🗺 Context

This email from Cuong Nguyen gives the context:

The timeline for the CentOS6 EOL/migration is the end of October 2020. We can start requesting the Cloud EC2s for the same tiers as we did EDRN. And then replicate the EDRN jobs in Jenkins and just update the repos and server parameters for MCL. That way it’ll be ready for whenever you’d like to test on NCI Dev infrastructure.

I’m hoping the ATO team can leverage a lot of the same responses we had for EDRN and shortened the months long process to month long? 😊

This is the same as EDRN/P5#124 but for MCL.

🐛 Describe the Bug

If you try to edit a page or upload a file larger than 8k, it fails.

🐛 Describe the Bug

The memcached on the MCL site works fine everywhere but for some reason when it's running on an EC2, it goes into an infinite restart loop.

Changing from memcached to memcached-alpine seems to help.