Agent-less Device Management
My current company creates and sells computer systems, mostly Linux-Based. I interact(usually troubleshooting, but also change requests) with a few of them before they are shipped and some that are already in use on remote sites. Most of them are in isolated networks and cannot access our servers (or anything in the internet) directly. If one of our technicians has to connect to one, this is usually done over a VPN.
Most of what I do is not automated in any way.
I am looking for software that helps me to automate as much as possible.
Areas I want to improve:
Task automation: Install Software, change Files/Configuration, do Backups. Basically Ansible.
Log/System analysis: Analyse the system and find known problems
Device History: I want to know what the last known state of the system was and (ideally) the steps that lead to this state.
While there seem to be many tools that are capable of doing those tasks, my problem is, that the hostname/IP-Address is no unique identifier for us. We usually use the MAC of the primary network interface for identification, but a file containing some unique identifier is also possible. I thought about using something like puppet but installing an agent on my target system is not allowed.
My goal is something along:
- Enter connection data to remote system somewhere
- System is scanned for known problems/irregularities
- Device history is accessible
- System state is recorded
- I can use a tool like Ansible to change things
For me this sounds like a DIY project to connect Ansible to some Log-Analysis tool and build/find a tool that records the device history. However, I'd prefer to use existing software over my own, so here's my question:
Do you know of any software that helps me with Log/System analysis and/or Device History that can use custom Identifiers for systems, is not agent-based and ideally integrates/supports Task automation (eg. Ansible)?
Posted Jul 3, 2018, 5:28 PM UTC
What you’re describing is a dream system
I was under the impression that ansible tower at least covers the device history and automation part. If I could use IP/DNS that would cover most of it. Might be wrong though
Yeah but what about device identification? That’s a hard one.