Can Splunk deployment server detect a container ID in a virtual environment, which was created... say by openvz, and apply the inputs.conf file to that container? This is necessary since the containers keep changing.
I would say no.
serverclass.conf has whitelist,machineType(deprecated) and machineTypesFilter properties to detect deployment clients.
Perhaps you could set your virtual container's IP addresses to encode the container ID, as described here , and then you can use the whitelist property to setup your serverclass stanzas based on the IP addresses.
Currently were using a script within puppet to identify those containers, does the deployment server support such a script. I guess what I can do is pupptize the host, install the forwarder,
and then if its a container Ill add the serverclass and deployment configuration files, from there
the Splunk server can populate the inputs.conf file. Does that sound like something that would work?