[EHPweb] Fwd: Moving EHP3

[Eric M Martinez]

- All -

In keeping with the timeline below, today please re-add EHP3 to your  
target hosts for public web content.

If you currently push only to EHPMaster and EHPBackup relying on our  
internal systems to keep things in sync, there is nothing for you to do.

If you currently push content to EHPMaster and EHPBackup and have a  
custom process set up to keep your content in sync, then you must  
modify this custom process to again include EHP3. You may want to  
manually sync your custom data before re-adding EHP3 to your custom  
process since it may be quite out of date.

If you currently push content directly to our public servers, you  
should add EHP3 to your list of destination hosts. You may want to  
manually sync your current data set to EHP3 before re-adding it as a  
destination host since your data may be quite out of date.

The new addresses for EHP3 are as follows:

	ehp3.wr.usgs.gov (137.227.233.17) -- Physical address. Use for SSH,  
RSYNC, etc...
	ehp3-earthquake.wr.usgs.gov (137.227.233.18) -- Web address. Use for  
HTTP.

The old *.gps.caltech.edu and corresponding IP addresses are no longer  
valid. Please let me know if you have any questions.

Regards,

Eric M Martinez
Application Developer
U.S. Geological Survey
emartinez at usgs.gov




Begin forwarded message:

> From: Eric M Martinez <emartinez at usgs.gov>
> Date: June 8, 2010 3:04:35 PM MDT
> To: EHP Web <ehpweb at geohazards.usgs.gov>
> Subject: Moving EHP3
>
> - All -
>
> We plan to turn of ehp3.gps.caltech.edu in order to move it from  
> Pasadena to Menlo Park.  I will take care of making sure the  
> internal rsync and build processes are configured to skip EHP3. If  
> any of you are manually pushing your content directly to the public  
> web servers you should also update your configuration to skip EHP3.  
> Below is a timeline outlining the steps required to perform this  
> migration.
>
> Timeline
>
> Wednesday 6/9/2010 - Friday 6/11/2010 : Everyone will update scripts  
> and configuration to remove EHP3 from their destination hosts. (i.e.  
> stop pushing content to EHP3).*
> Monday 6/14/2010 : Stan  Schwarz will turn off EHP3 and overnight  
> ship it to Stan Silverman in Menlo Park.
> Wednesday 6/16/2010: Stan Silverman will receive EHP3 in Menlo Park  
> and begin the process of restarting machine.
> Friday 6/18/2010: Eric will manually sync content from EHPMaster to  
> EHP3.
> Monday 6/21/2010: Everyone will update scripts and configuration to  
> add EHP3 back to their destination hosts. (i.e. start pushing  
> content to EHP3).*
> Wednesday 6/23/2010: Jeremy will manually sync content from  
> EHPMaster to EHP3.
> Thursday 6/26/2010 - Monday 6/28/2010: Everyone checks their content  
> ensuring pages are up-to-date, and being updated as appropriate for  
> their content.
> Monday 6/28/2010: Chris will add EHP3 back into DNS load balancing  
> effectively making EHP3 part of the production web site again.
>
> Obviously unforeseen events can happen and this timeline may change.  
> If changes occur, notifications will be sent out to this  
> distribution list. Please forward this message on to anybody else  
> who may be affected by this upcoming change.
>
> Thanks,
> 	~Eric.
>
> * Only applies if you are currently pushing content to public  
> production web servers manually.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/ehpweb/attachments/20100621/6793d7cb/attachment.html>