ESciDoc-core Migration v1.1 to v1.2 coreservice splitting

MPDL,GWDG

Preparation

 * Note: Actions described as preparation have to be triggered up-front (asap)
 * Responsible: SysAdmin

Ist der GWDG gemeldet, angeblich arbeiten sie dran, aber keine Änderungen works with 1 Gbps Fedora Files 4 h DB create Dump 7 Min. DB copy dump 30 Min. DB import dump ~ 90 Min. Coreservice copy 3 Min
 * 1) Fix srv01 net to 1Gbps
 * 1) Fix srv03 net to work on peth0 1Gbps
 * 1) Fix PostgreSQL mount for new Harddisk (done)
 * 2) Performance tests to copy data

I haven't any new feedback from GWDG, but i wrote a e-mail die support of GWDG too.
 * 1) Check all network connections to work on 1Gbps
 * 1) Prepare vm31+vm33 to act as new servers instead of (srv01, srv02)
 * 2) Install PostgreSQL on vm33 --installed--
 * 3) Prepare Settings on vm31+vm33 --should be prepared but double check of somebody please--
 * 4) Apply for new Alias: r-coreservice.mpdl.mpg.de (request sent)
 * 5) start incremental copy of Fedora data and fulltexts from srv01 to vm31 --done--

Read-only coreservice and read-only solutions

 * Prerequisite state:
 * "Sorry no login possible" page is prepared(sorry, no login possible currently: Readonly)
 * data are copied only increments from Monday, Tuesday (13-14.09) are expected
 * 1) Shutdown
 * 2) Shutdown JBoss of all solutions {pubman, faces, virr}.mpdl.mpg.de,
 * 3) Shutdown JBoss on coreservice.mpdl.mpg.de (srv02),
 * 4) Backup a.user_account table from escidoc-core database
 * 5) Shutdown Fedora and PostgreSQL on srv01
 * 6) Finalize copying of data
 * 7) incremental: Fedora data (srv01)+FullTexts(SAN)-> vm31,
 * 8) full: PostgreSQL (srv01-> vm33)
 * 9) full: Lucene data (srv02->vm31)
 * 10) Swap ID addresses (to keep coreservice.mpdl.mpg.de in place for MPI PL)
 * 11) Give IP address from srv02 (134.76.28.241) to vm31
 * 12) Give Ip address from vm31 (134.76.28.207) to srv02
 * 13) Start-up read-only coreservice
 * 14) start-up PostgreSQL on vm33
 * 15) make all users inactive except root user (set attribute active=FALSE in aa.user_account table in escidoc-core database)
 * 16) delete all user sessions to prevent editing (aa.user_login_data table in escidoc-core database)
 * 17) start-up Fedora on vm33
 * 18) deploy "Sorry no login possible" page on coreservice on vm33
 * 19) start-up read-only coreservice on vm31
 * 20) PubMan,VIRR,Faces for new coreservice on vm31
 * 21) change properties for coreservice
 * 22) start-up JBoss on {pubman, faces, virr}.mpdl.mpg.de respectively

PubMan 6.1 Deployment

 * Prerequisite state:
 * Read-only solutions are running
 * Fedora, PostgreSQL are stopped on srv01
 * JBoss on coreservice.mpdl.mpg.de (srv02) is stopped


 * 1) Purge VIRR, FACES data from coreservice
 * 2) Delete VIRR, FACES FOXMLs from Fedora data directory (DONE)
 * 3) Continue with Escidoc-core_Migration_v1.1_to_v1.2 as described, under following limitations:
 * 4) do not apply foxml changes for virr, faces (as no foxmls shall exist)
 * 5) Quick test if PubMan is running with new core service from local instance
 * 6) Stop PubMan on srv03
 * 7) Update PubMan to 6.1 on srv03 as described in PubMan_6_1
 * 8) Swap back IP addresses between srv02 and vm31
 * 9) Start PubMan 6.1(Jboss on pubman.mpdl.mpg.de)

Faces, VIRR Deployment

 * purge publication data from r-coreservice (publication items+files, importtask items+files)
 * use following

./X/fedora/client/bin/remove-publications-from-research.sh