Closed jordanpadams closed 2 years ago
@viviant100 @acyu-jpl @jordanpadams OK, today's release is out with help from @c-suh. Next scheduled release is 12/15
@viviant100, I compared the data release files from the latest svn updates with the files in the new repo and pushed the difference. Do you have anything more for Action 2? If not, that is complete.
Consider action 2 done! Thanks @c-suh.
Thanks for wrapping up 12/6 data release @rchenatjpl. Starting next data release, we'll be using Github in lieu of svn for the updates. Feel free to reach out for any questions.
@jordanpadams and @viviant100, the one-time sync for the /data
directory (this is NOT static web content nor covered by the hourly sync in Action 1b) has been done thanks to Andrew, but I think there's active development happening (e.g. directory added this morning not caught by the sync: https://pds.nasa.gov/data/pds4/test-data/registry/lab.hydrocarbon_spectraV1/). So, I think a freeze on the /data
directory would be in order with a final one-time sync right before the cutover. Would this be a new Action item right before the second Action 5 on 12/16 ?
@c-suh since we are pushing the cutover for a few weeks, I would recommend we setup a sync for an hourly sync for the data, similar to the website, and then we can work on a freeze and shutdown of the sync once we are ready for the cutover.
@jordanpadams and @viviant100, just verifying that Action 4 is for prod2 as well?
Note: Action 3 has been completed. Please give prem gamma a try and let me know if you find anything missing or broken.
@c-suh Action 4 applies to prod2 as well.
@acyu-jpl has reviewed the deployment procedure and is ready to run it for prod1 and prod2 tomorrow.
@c-suh Action 4 has been applied to pds-prod1. pds-prod1 is loading correctly, with tophat & feedback widget showing as well.
Action 4 has been applied to (pds-prod2)[https://pds-prod2.jpl.nasa.gov). pds-prod2 is loading correctly, with tophat & feedback widget showing as well.
Quick test reveal that the Java app is not working correctly on pds-prod1 or pds-prod2 or pds-gamma the keyword search app https://pds-gamma.jpl.nasa.gov/datasearch/keyword-search/ and the dataset status app https://pds.nasa.gov/datasearch/ds-status/
@acyu-jpl let's first replace htdocs on prod2 with the backup htdocs, then test on prod1. Additionally, is this the same for you - Data Search at https://pds.nasa.gov/datasearch/data-search/ works on gamma but not on prod1/2?
@c-suh I restored the pre-git htdocs on pds-prod2. However, Keyword Search and Data Set Status are still broken. The data search is working on all environment.
@acyu-jpl OK; thank you. I will take a look now.
Created a ticket with the SAs. Just discovered that pages from Data Set Status are also 404 across all prem machines, e.g. https://pds.nasa.gov/ds-view/pds/viewBundle.jsp?identifier=urn%3Anasa%3Apds%3Aapollo_seismic_event_catalog&version=1.0, with the same error as for the other two applications.
@acyu-jpl Data Search was not working because I had mixed up part of the process. I've tested it on pds-prod1 and updated the documentation. Please apply this section to the git-htdocs directory on pds-prod2 and make that directory operational.
@acyu-jpl after switching prod2 back to git, also do a git pull
. Thank you
@c-suh pds-prod2 has switch back to the git working copy. ran git pull origin main
, no conflict detected
Action 5: I've started updating documentation, but there are many procedures. @rchenatjpl and @acyu-jpl, please update those processes for which you are responsible and let me know if you come across any which I might have missed.
Action 7a: https://github.com/NASA-PDS/operations/issues/197#issuecomment-990537849
Action 7b: talked with @acyu-jpl and this seems straightforward enough that I've asked him to look into misc application problems while I work this agu page.
@acyu-jpl , I see that prod2 is using git (thank you), but step 4 of the updated documentation has not been applied. Please do only that one step (not any of the other steps) then leave the changes (how those are to be handled are TBD and are fine to stay as untracked changes until then).
@c-suh I updated the password manually on pds-prod2 for the following 4 files based on the step 4 of the documentation datasearch/data-search/getInvestigation.php datasearch/data-search/getInvestigations.php datasearch/data-search/getTarget.php datasearch/data-search/getTargets.php
However, I do suggest that we ask SA to setup environment variables for the connection information so we can commit these 4 files to git, and not expose connection credential
@acyu-jpl @c-suh maybe let's create a separate ticket to track that since it is isn't required right now?
but i 100% agree. this will avoid an unintentional commit that will expose the info
Belatedly added Action 8 to test all applications/functionality of the AWS sites. Direct message me for the document tracking the tests.
List of tickets requested to this action item (some from initial testing before the holidays):
Update: tickets post-Jan 25
A follow up ticket has been created for the documentation https://github.com/NASA-PDS/portal-tasks/issues/23, this current ticket is now closed
Timeline for cutover.
[x] 12/6 - Action 1a: Complete today's data release (@rchenatjpl)
[x] 12/6 - Action 1b: Setup hourly sync of pds-prod1, pds-gamma, pds-engineering to AWS (SA Team)
[x] 12/6 - Action 2: Add Richard's Updates to Github (@c-suh / @viviant100 )
[x] 12/7 - Action 3: Test out using github instead of subversion for website (@c-suh / @acyu-jpl )
[x] 12/7-12/8 - Action 4: Perform same website deployment procedure on pds-prod1 (@c-suh / @acyu-jpl )
[x] 12/8 - Action 5: Update Ops/Data Engineering procedures to use git commands (Catherine/Allan/Richard)
[x] 12/8 - Action 6: Website Content Update Freeze Complete (All): obsolete, the on-prem and AWS site are mirrored hourly on 2 directories. Beware of application updates (e.g. doi-ui, doi-service).
[x] 12/8-12/10 - Action 7a: Complete B12.0 website updates / LDD deployment (@c-suh / @acyu-jpl ) (https://github.com/NASA-PDS/operations/issues/197)
[x] 12/8-12/10 - Action 7b: AGU web page development (@c-suh / @acyu-jpl ) (https://github.com/NASA-PDS/portal-tasks/issues/4)
[x] 1/31 - Action 8: Test all applications and functionality of AWS sites (list of tickets here)
[x] 12/16 - Action 9: Final OK to switchover pds.nasa.gov/pds-gamma to AWS (@viviant100 / @jordanpadams )
[x] 12/20 - Action 10: Initiate DNS switchover pds.nasa.gov, pds-gamma.jpl.nasa.gov, pds-engineering.jpl.nasa.gov to AWS (SA Team)
[x] Once DNS cutover completes -
[ ] clarify where the documentation of deployment of application is or should be (e.g. doi-service...), see https://wiki.jpl.nasa.gov/display/PDSEN/Software+Installation+and+Deployment+Guides