- CSI Documentation
- Working with CSI
Linux Build Services
- Overview of Linux Environment
- Getting Started
- Building Hosts
- Using Puppet
- Software Repositories
- Satellite deployment
- NTP time
- AFS/Auristor Filestore
- MySQL / MariaDB
- Load Balancing
CSI Internal docs
- Operational docs
- Updating Documentation
- Tag summaries for CSI docs
- Pager Admin Commands
- Nagios Config for Windows
- SSL Certificate Management
- Build Environment
- Firewall Information
- On-Call Playbook
Getting started with PCI Foreman
Get your group the WolfTech RENV( Regulatory ENVironment )
Contact [Security and Compliance][https://oit.ncsu.edu/it-security/]
Get access to the PCI Foreman
If you’ve never had access to the PCI Foreman, CSI will create a Foreman “organization” for your group so that you can create and manage hosts.
Once the Foreman organization is created, any regulatory user in the identitied AD group will be able to manage group resources in Foreman. All account work (password resets etc) are not done by CSI, but handled using the RENV processes.
Make sure your subnet/vlan has the proper firewall entries
CSI can assist you with this. If your connected system is in a network that has never been configured, it will need to have the proper firewall ports opened.
The PCI foreman is
pcibuild.oit.ncsu.edu and the Firewall should be
configured in a similar manner as firewalls for the campus Foreman.
Configure your PXE boots
The PCI environment uses almost identical technologies as our regular campus build system The main differences are in the policies and processes by which it is maintained.
The Foreman host that you use to manage PCI systems is
PXE-Dev-PCI filter in Infoblox to select the proper environment.