Difference between revisions of "Hostnames and Roles"
Jump to navigation
Jump to search
m |
|||
| Line 7: | Line 7: | ||
See also: ''[[Proxy and SSL Decryption]]'' for other notes about JLAB-specific networking. | See also: ''[[Proxy and SSL Decryption]]'' for other notes about JLAB-specific networking. | ||
| + | |||
| + | ==== SSH Keys ==== | ||
| + | |||
| + | Authorized keys for ''laci'' and ''softegr'' are managed through puppet. Note only the ''laci'' account can be used for the production server. | ||
== Servers == | == Servers == | ||
Revision as of 16:36, 26 April 2018
Configuration
All Linux hosts are managed with Puppet. If packages need to be installed or any other host configuration is needed, contact Wesley Moore (wmoore@jlab.org).
Installation of EPICS and other things that are shared via NFS, do not need Puppet updates.
See also: Proxy and SSL Decryption for other notes about JLAB-specific networking.
SSH Keys
Authorized keys for laci and softegr are managed through puppet. Note only the laci account can be used for the production server.
Servers
lclsfs.acc.jlab.org
- File server
- Core services
lclsapp1.acc.jlab.org
- Build server
- Development server
lclsapp2.acc.jlab.org
- Production server
- softIOCs
- Restricted to 'laci' only
VDI / Workstations
lclsvdi##.jlab.org
- Remote access
- Future plans - Run client tools for channel access, view archive data, etc.
lclsl##.acc.jlab.org
- Control Room Workstations used for operations
- Run client tools for channel access, view archive data, etc.
Windows
lclsw01/02.acc.jlab.org
- PCs strictly for PLC administration
- Available via RDP from VDI hosts and workstations