I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO.
Currently a big push to manage all our *nix infrastructure with a compliance as code type of tool. Make sure there's odm alerts, ntp is set, whole list of other things. And force a box back into compliance if its out of spec. In past this was managed by each lpar holding a directory with scripts and items added to the appropriate places.
Has anyone tried to run the Chef client on the VIO? I see that the AIX cookbook has a nimviosupdate to help build resources. However, I am not finding a lot of information about actual customers running the client on the VIO in a production setting. So, has anyone ran the Chef client on the VIO? Did you have any issues with IBM support if they noticed the client running? Looking at the
supported software solutions I see that the puppet client is supported, but no mention of Chef. In a document by Paul Finley from 2016, there is mention of VIOS Patch management with Chef but unable to find anything beyond that.
So part two of my question:
If you are not running any sort of configuration management on the VIOs, then how are you controlling the configs for your VIOs?
In the past, each VIO was built as needed but DNS servers retire and new ones get put into place. Search domains same thing. We've even had to change our NTP server. Doing this all by hand is tedious.
Thanks everyone!