Closed PaulClark2 closed 6 years ago
Primary goal is to have two missing applications from the new fec.gov website (fecviewer and data catalog pages) functionality available at the alternate site. But most of the classic.gov functionality should be available at the new location.
[PCC] I consolidated the checklist below with the checklist in the original issue post.
- [ ] Move one WEB, one APP, and one DB server from BO1 to DC3.
- [ ] Once the servers arrived at DC3 host them behind a firewall
- [ ] Create a small database similar to pubdb3z2 and push data to it from FECP
- [ ] Create a read only standby database against the new database.
- [ ] Connect APP server to above standby database.
As of 11/28/17 WEB, APP, and Databases are mounted on a rack in DC3. @gmengistu will power up assign new IP address and configure them on Monday 11/28/17
Next steps are:
The web and app servers are up. The app server is connected to a read-only internal DB for testing while the new DB machines are being built. The network configuration is being worked on, but going a bit slow as Mark has been sick last week. We are not able to build the DBs before the network configuration is complete - but shouldn't be a show stopper as we have a connection to another database now - atleast for testing.
@rjayasekera should this be closed?
So users can access classic.fec.gov after we shutdown our Waltham data center, we should host classic.fec.gov in an in alternative hosting center.