Preliminary knowledge of CMDB

Vision of operation and maintenance

1. Automatic machine
2. Configuration Management
3. Monitoring
4. Fortress machine
5. Asset Management "Essentials"

Current situation

• At present many companies still: manual maintenance Excel table
• Urgently needed: Assets are automatically collected and reported to the warehouse
• Workaround: CMDB-Configuration Management database (Asset management)

What if automatic acquisition is achieved?

1. Agent mode Api:django receive data and Warehousing program: placed in each server scenario: 2 for more servers. SSH mode Api:django receive data and warehousing program: Put in the central control machine application scenario: There are three kinds of tools, Paramiko, Fabric, Ansible, which are less for the server, and the fabric, Ansible internal principle is also through the Paramiko to achieve. Paramiko Installation: PIP3 install PARAMIKO3. Saltstack "Python language" Http://www.cnblogs.com/wupeiqi/articles/6415436.htmlAPI:Django receive data and inbound scenarios: Companies that are more servers "recommended" Master:v = subprocess.getoutput (' Salt ' * "Cmd.run" ls ") saltstack internal principle is implemented via RPC with Message Queuing 4.puppet" Ruby language " Internal principle: Puppet client automatically reports data to puppet server every 30 seconds. Application scenario: Primarily for companies that already use puppet.

CMDB to achieve the goal: the implementation of compatible agents, SSH, saltstack more than three ways.

Preliminary knowledge of CMDB