Created on June 6, 2017 @author: louts
1th Session Work 10minutes
Display page, only login to display, not logged in will pop up a login box, is a masking layer
2nd Course Automation Road and CMBD status 22minutes
cmdb:
automatic installation
configuration management system
cmdb Operations Asset Management System (all systems need to call the information here)--the core is located
highchats
echats
cmdb:
acquisition hardware data
API report----open to all external, gather information, write to database via API
page management
approximate flow: Client Agent reports to API via URL ====>api received and stored in the database ====> background management by invoking the database, the data is added and modified to check the
3rd Course CMDB Puppet collection data mode 21minutes
Collect puppet to operate
Puppet
Factor ==> results are present in Key/value mode (saltstack ===> grains)
Report ==> executes the report process function as long as the master/slive is connected once
Master (Save configuration information, and slive half-hour connection, can be changed)
Slive (Get configuration from master, use this configuration to get local hardware information)
Hardware information can be acquired through puppet, which relies heavily on puppet
4th lesson the CMDB custom Python plugin collects data 11minutes
Call the shell to collect hardware information through a Python program
A new DAY15_PJ program, the code is not complete, you need to add
The 5th session of the CMDB's Django implementation API 35minutes
Every Agang gets a dictionary containing hardware information about the device.
The copy of the script in the video is partially not seen.
You can send data to a function in a httplib way.
6th session of the CMDB data Flow execution Process review 18minutes
Python Learning day15 CMDB