4.9 Create PAT Projects

Warning

Projects installed in PAT will have an administrator password assigned on installation. It is recommended to use the ‘passwd’ command to change the password to a long string and to use that same password for all VMs in the PAT projects. No user, other than ‘administrator’, should be added to sudoers and this long password should be kept secret as far as possible. All actions taken by users must not require sudo privilieges but must instead be enabled by Linux permissions.

You can choose whichever provisioning and telemetry tools you wish to install. The contents of this section can be viewed as one possible configuration. Typically PAT communicates with Pods over two networks, thus dividing all PAT projects into two groups based on network type used:

1. The Public Network is used to communicate with Pods via their PodNet public Interface.

2. The OOB networks in all Pods is used to communicate with Pods via VPN tunnels from within a PAT project called OOB.

This resilient connectivity strategy allows for recovery from network failures that would otherwise prevent the PAT team from diagnosing and repairing connectivity issues to Pods.

The following Projects must be created in PAT.

For the entire Galaxy the following Projects exist:

1. Provisioning

2. Rocky

3. VDIs

For each COP System in the Galaxy, there is a Project with multiple VMs:

1. Telemetry

   1. Sentry

   2. ELK Stack & Jaeger