Setting up a New Net
From VCGR Wiki
Contents |
I set off with the task to start up a new net on the Generals. The process I took and my experiences along the way are detailed below.
Net Machines
As the Windows machines are not up at this point, I have going to start up a net on the Linus machines: Titus, Cicero, Sulla, and Camillus. I have chosen Cicero for the root of the net (though I am unsure how this will affect the setup as of yet). The machine file under ~/GeniiNet was modified to contain the names of the new machines that will make up the new net.
Directory Structure
The contents of the directory GeniiNet was moved to oldGeniiNet. This folder contains all the settings for setting up the net that use to run on the Centurions.
Installing the Build
The installation .jar from the website was acquired to get the desired build version. Since the installer requires a graphical user interface, VNC was used to make the install. This process can be avoided by passing an xml file with the the appropriate installation settings (as has been done in the past for redeployments). The old file, installation-description.xml can still be used as it specifies the desired path for the install: /home/gbg/GeniiNet/Genesis II
Script Modifications
Each script was examined for any contents that might be affected due to the machine change. Nothing in the scripts was needed to be changed. However, several locations used in the scripts were initially missing:
- The /localtemp/gbg dir was created on each machine with the help of Systems
- The /certs/ dir was created along with its subdirs groups and users was created under GeniiNet; new certs are to be acquired from the group to fill the user folder
- The /log/ dir was created to be populated at script runtime with log files from each container.
- The conf-files dir was created and populated with its three appropriate scripts (client-config.xml,server-config.xml, and bootstrap.xml). I saw nothing in these scripts that needed to be modified.
The examined scripts that were copied verbatim to their new corresponding locations:
- initialize-security.sh
- clean-deployment.sh
- net-clean-deployment.sh
- net-start-containers.sh
- net-stop-containers.sh
- start-container.sh
- bootstrap.sh
Remaining Questions
What else needs to be done to handle the newest build?
Should the contents of the /deployment/default/security dir be emptied when initializing security or are some of the contents needed other than what is put in?
Where should the the pervious Genesis II/certs dir be located? Any changes here? (It is used in bootstrap.xml)
Is context.xml created after bootstrap.xml completes?
In runContainer.sh', should the argument /home/gbg/GeniiNet/Genesis II/security be changed to home/gbg/GeniiNet/Genesis II/deployments/default/security?
Why are there two security dirs: Genesis II/security and GenesisII/deployments/defualt/security?
