Google may decide a GGC node is nearing its maximum serving capacity, and that the existing servers are new enough to warrant adding additional compatible machines. This process is called a "node augment".
A node augment process is initiated by Google, usually by the Interconnect Coordinator. The Interconnect Coordinator opens a ticket in the ISP Portal, which will drive the process.
Google will notify you via email when an augment step requires your action. Each email from Google contains a link to the ticket tracking the augment in the ISP Portal. The ticket will display the current state of the node augment. Emails are sent to the addresses shown in your ISP Portal Contacts page.
Node augment process
-
Google will inform you via email that a node augment is required.
-
Verify that the address shown on the "Shipping" tab of the "Assets" page for the node being augmented is correct.
-
-
New machines will be ordered and shipped to you.
-
When Google is notified that you’ve received the new machines, you’ll receive an email asking you to install them.
-
The email will state which IP address should be used for each new machine, with links to the current installation instructions and software image.
-
-
Install the new machines with the current GGC installation image.
-
When all of the new machines are installed and have called home to Google's servers, Google will email you, asking you to choose your preferred date and time to start the reconfiguration of the GGC node.
-
If a new machines fails to install, use the ticket tracking the augment to send a message to Google with details about the problem.
-
The augment process automatically adjusts if hardware problems prevent a new machine from being installed.
-
-
Google will email you when the node augment is complete and the new machines are serving as intended.
Problems that can affect a node augment
The automated reconfiguration of a GGC node requires that the GGC Application software and node configuration be pushed from Google core servers to all the working servers in the node. The process can’t complete until all working servers are fully updated. The node reconfiguration process automatically adjusts if a new GGC server isn’t working due to hardware problems.
Network connectivity problems could result in time-outs which could prevent the GGC machines from being fully updated at the first attempt. Resulting retries could greatly increase the time needed for the node reconfiguration to complete.
We can’t give a precise time to complete a node reconfiguration, but this type of reconfiguration normally completes within 24 hours. Once the node reconfiguration has begun, don’t try to stop or reverse it. Even if the node reconfiguration runs longer than desired, it’s safest to allow it to complete normally.
Prepare for a node augment
- Read the current GGC installation instructions.
- Download the current GGC installation image and prepare the installation media.
- Ensure that staff who will be involved in the node augment are included on the ISP Portal Contacts page, and have at minimum the "Rack Updates" and "Work Items" roles assigned.