Configuration Management How To
HOW TO AUTOMATE CONFIGURATION MANAGEMENT ON AIX SYSTEMS ? CONFIGURATION MANAGEMENT FOR AIX AIX is and has always been very strong in virtualization and partitionning (LPAR, and then WPAR), offering a robust and stable plateform for critical services. Now that DevOps is gaining momentum, many tools are available to automate Linux and Windows systems, manage their configuration, orchestrate containers, etc. However, there are not that many tools to manage the AIX systems, even though there are often a lot of them to manage, given the ease of partitionning in AIX. Once a Logical or Workload Partition has been Among the few available tools to manage AIX, there is created, user accounts and permission have to be Chef, who release an AIX agent at the end of 2014, configured, network parameters are to be set and CFEngine, who always supported AIX, and (like DNS), system need to be configured Rudder, which suports AIX since mid-2014 (timezone, mountpoint, log centralization, monitoring, etc), and finally services need to be These tools deal with every aspect of the deploy. configuration management on AIX; with some These configurations not only need to be differences. Only Chef and Rudder offer a performed at initialisation, but maintained during comprehensive inventory of the system, Chef and all the life of the systems (users may come and CFEngine both need to code the configuration of the go, parameters may change, new version of the system, and only Rudder come with a Web interface services may be released, etc..) for configuration. To fully benefit from automation and manage all your systems alike, the choice of the right solution for your needs is important.
[Show full text]