- 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
- SSL Certificate Management
- Build Environment
- Firewall Information
- On-Call Playbook
Overview of the Environment
Campus needs a nimble deployment system for Linux systems where subject matter experts have complete control of the underlying technologies.
This completely distributed model does have a disadvantage, in that it excludes those groups that cannot afford to develop (and maintain) the required expertise in these underlying technologies.
High barriers to entry for folks who just want to build a system. One must know and follow Linux and Puppet best practices, in addition to learning git and other unfamiliar stuff.
We want to lower barriers to encourage more usage, without losing the distributed administration that the campus currently enjoys.
Provide a “soup to nuts” environment
We have some specifics about the Services for Everyone we expect to offer.
Be compatible with Campus Efforts
- Opt out at ANY time without assistance
- Merge back if desired
- Open source model means lurkers can benefit from our processes
We have some specifics about the Services for experts we expect to offer.
- Foreman as host management means flexible config management