Please download and review the CA Release Automation Architecture and Implementation Guide 5.5 - 6.x at the following link:
CA Release Automation 5.x / 6.x Architecture and Implementation Best Practice Guide
You can setup super nodes for a ring configuration, if you are going thru this step, why not setup a STAR configuration? That will give you more flexibility for future expansion if needed.
Now to setup the super node, please follow the instructions in the guide listed at the beginning of this response and review page 24, which explains what you have to do.
So each of the super nodes will contain just two RA agents each? If you create super nodes across data centers, you need to keep in mind the network latency. The description of the make up of the super nodes is very good and again based on the architecture that you decide to use, it will work on both.
Based on the information provided in the above guide, you can find additional information about how the artifacts are distributed to the NES. Release Automation KB: Artifact Distribution and Cleanup
Artifact NES Distribution
- Artifacts are retrieved by retrieval agent and downloaded to <Retrieval_Agent_Root>/files/ART<Release_ID>
- They are moved to <Retrieval_Agent_Root>\files_registry\<File_MD5>
- This sub-stage is sometimes referred to as the "Retrieval Stage". While the files are being moved, there could be a point where the file exists on the agent at both locations at the same time (thus peaking at two times its size). After the move finishes, they exist only in 'files_registry'.
- They are copied to the NES at <NES_Root>\artifact_store\releaseId_<Release_ID >
- Each NES will request and get only the artifacts that are needed by the agents that are connected to it.
- They are deleted from <Retrieval_Agent_Root>\files_registry\<File_MD5>.
Based on the information above, if you setup a super NES, the artifacts will be distributed to the NES servers that make up that super node.
Let me know, if you need any additional information about this.
Thanks
-Walter