Infrastructure Automation
From KynetxDocs
Infrastructure automation using Puppet and other tools gives Kynetx the ability scale up services on demand. The also provide the ability to react to system and service failures in an automated manner, reducing the length and impact of service outages. Automated configuration management ensure that all servers are consistently configured and administered.
In addition to these tools, Kynetx makes use of SVN and other code repository systems so that changes can be quickly rolled back in the event of a poor or failed release.
The following describes the state of infrastructure automation as of the date this page was last edited:
- All production servers use Puppet for server configuration.
- Major OS services (e.g. cron, sudo, sshd, DNS, etc.) are configured using puppet.
- User accounts, ssh keys, and sudo privileges are automatically maintained and configured.
- Logging is automatically maintained and configured.
- Apache, libraries required to run KNS, and data sources are automatically maintained and configured.
- KNS code is deployed via a tool based on server persona
- KNS code can be rolled back to last known good build via a tool based on server persona
The following describes automation tasks yet to be done:
- Automation of auxiliary services (e.g. memcached, network-level logging)
- Automation of corporate Web server assets (not involved in delivering KNS)
- AWS install
- Monitoring system deployment, configuration, and management
- Load balancers
Until these are automated, they are performed using manual processes that are documented on Kynetx Engineering Wiki.
