InCommon Operations Notifications

[Thomas Scavo <>]

You are receiving this message because you are an InCommon Site Administrator 
or are otherwise subscribed to this mailing list. Please read this message 
carefully. Your timely action may be REQUIRED.

InCommon Operations has deployed a new metadata distribution server node in 
Los Angeles, CA. Once the new node is fully deployed, the server node located 
in Bloomington, IN will be decommissioned. Consequently, you may have to 
reconfigure your metadata refresh process (but please read on).

If you do NOT automatically refresh metadata as recommended by InCommon, this 
message is FYI only. However, in that case we strongly recommend that you 
read this important document about Metadata Consumption: 
https://spaces.internet2.edu/x/JwQjAQ

If you automatically refresh metadata as recommended by InCommon AND your 
metadata refresh process is configured by name (not IP address) AND your 
metadata refresh process is NOT restricted by an outbound firewall, this 
message is FYI only. Otherwise READ THE REST OF THIS MESSAGE CAREFULLY.

As you know, InCommon metadata is served from vhost md.incommon.org. 
Currently that name resolves to one of two identical servers, a node in Ann 
Arbor, Michigan (207.75.165.125) or a node in Bloomington, Indiana 
(140.182.44.53). For more info about the InCommon Metadata Distribution 
Server, please visit our wiki: https://spaces.internet2.edu/x/wIfFAg

Since one of the IP addresses of the metadata distribution server nodes is 
changing, deployments that are restricted by an outbound firewall will need 
to re-configure that firewall no later than Monday, August 7 @ 3:00 pm EDT. 
At that time, the server node in Bloomington, Indiana (140.182.44.53) will be 
permanently decommissioned and the server node in Los Angeles, CA 
(163.253.32.9) will take its place.

IMPORTANT. InCommon Operations will conduct a “flash test” of the new server 
node on Tuesday, August 8 starting at 3:00 pm EDT. The test will run for 24 
hours. During this time, the metadata distribution server will intentionally 
be failed over to the server node in Los Angeles, CA. To avoid client-side 
errors, the IP address of the CA server node (163.253.32.9) should be added 
to your outbound firewall rules by August 8 @ 3:00 pm EDT. Again, if your 
metadata refresh process is configured by name (not IP address) AND your 
metadata refresh process is NOT restricted by an outbound firewall, there is 
nothing you need to do.

A complete timeline follows:

Tue, Jul 11: Send initial announcement to inc-ops-notifications
Thu, Aug 3: Send courtesy reminder
Mon, Aug 7 @ 3:00 pm EDT: Decommission IN server node (140.182.44.53)
Tue, Aug 8 @ 3:00 pm EDT: Failover to CA server node (163.253.32.9)
Wed, Aug 9 @ 3:00 pm EDT: Failover to MI server node (207.75.165.125)
Thu, Aug 10:  Send final announcement

If you experience a metadata issue on August 7 or thereafter, please send a 
message to 
.
 This will create a service ticket that can be tracked. 

In summary, the server node in IN will be decommissioned on Monday, August 7 
@ 3:00 pm EDT. To avoid client-side errors on or after August 7, any 
necessary re-configuration to your outbound firewall (if any) should be 
completed by that time.

As always, if you have any questions or concerns, please contact us at 


-----
Tom Scavo
For InCommon Operations