Building a devops CMDB
Download as PPTX, PDF13 likes7,846 views
This document discusses how a company implemented a CMDB (configuration management database) to automate their IT infrastructure using DevOps principles. The CMDB stores information on all their IT assets including servers, VMs, network devices, users and projects. It is fully automated with no manual maintenance needed. The CMDB integration has provided benefits like standardizing quality controls, finding underused resources to save costs, and delivering knowledge to users. It allows them to provision infrastructure through scripts like Ansible. An example is provided of how the CMDB was used to migrate 120 servers between data centers. The conclusions emphasize that a DevOps CMDB should integrate within the organization, information is only useful if you can do something with it, and political support
Building a devops CMDB
- 1. CMDB & Devops. Automatizing IT Infraestructure
- 2. About me & Index Speaker Jaime Valero de Bernabe Sysadmin at Expert Productiviy Group. Telefonica Global Resources Index Initial situation CMDB Features Benefits Case of use Conclussions
- 3. Initial Situation A typical IT Corporation
- 4. Problem: duplicated efforts An IT company has a complex ecosystem. Different environments, Technologies Metodologies Work groups Locations
- 5. Competitors: Organizations Smaller Agile Fully cloudified = Fast to introduce changes. Lower operating costs = Competitive products.
- 6. The main idea: Bring the best of both worlds ITIL Good practices to manage IT items Devops Integrate operations and development. Creation Interelation Decommision
- 7. Our response: a devops CMDB
- 9. 1.500 Physical Servers 60 Racks 3.500 Virtual Machines. 2.500 People •500 Projects •40 Locations 600 Network Devices. •10.000 IPs Objects . Storage
- 10. And now the technical part…
- 11. CMDB Applications : Tier • Frontend : • Open Source solution ITOP, by Combodo company. • Backend: • Database Inventory Internally • Linux • Apache • Mysql • PHP • Mysql: 1,5 M of rows • Modules ( Shell, sql, php, perl, ruby, power shell). Key feature • Datamodel easy to modify. • Interconnected by API with the rest of platforms.
- 12. CMDB Key features : • Fully automatized, no maintenance effort needed. •Backend destroys and re-creates data daily Automatization
- 13. CMDB Key features : • Objects have to meet certain policies. • If an object does not meet its policies, a flow could be triggered. Auditable
- 14. CMDB Key features : • The objects have : • lifecycle • audit rules • cost associated. Cost
- 15. CMDB Key features : • Customized dashboards, • Every team focus on their part of the universe. Customization
- 16. CMDB Key features : • All data is searchable. • Break down silos of knowledge! Searchable
- 17. Infraestructure Provisioning Scripts •Mysql daily tables Synch to CMDB •Itop objects Workflow Ansible Audit rules •Itop invalid objects
- 18. Before & After
- 19. Benefits: We have found underused resources that can be freed to save money. We can set standard quality controls for any given inventory item. Also, we deliver adquired knowledge to the users, the current state of their resources and its cost for the company.
- 20. Benefits We, the sysadmins, are no longer a grandmother cooking recipes. We are turning into cloud service providers for the organization. Thanks to the ansible integration we can automatize the management of our infraestructure.
- 21. Case of use: Migrating DataCenter To save costs, It was decided to migrate Data center location 120 Servers had to be migrated. from our Alcantara facility in Madrid to Boecillo, Valladolid.
- 22. Case of use: Migrating DataCenter We used the CMDB for: Verify connectivity and credentials for the servers. Backup server configuration. Verify the migrated servers were covered by third parties support. Arrange shutdown of the servers Keep in touch with the owners of the servers. Verify special network config for the servers. NAT, publishing domains, etc. Those scripts could be reused for future migrations!
- 23. Future
- 24. Future Further integration with automatization tools New objects, according to user feedback.
- 25. Conclussions
- 26. New paradigm Infrastructure as code Scripting is the new black!
- 27. A Devops CMDB: should integrate within your organization. It’s not a silver bullet
- 28. Information is not important by itself, but what you can do with it. User feedback is the key.
- 29. As you refine your model, you will find chances of speed up your bussiness processes. Devops is an iterating process.
- 30. Rather than technical difficulties, the hardest part is to overtake political considerations. You need direction support.
- 31. Conclussions Scripting Integrate User Feed back Iterate direction support
- 32. Thanks!
Editor's Notes
- #2: Buenas tardes a todos y bienvenidos a la charla de CMDB y DevoPS
- #3: Me llamo Jaime Valero, trabajo en el EPG.
- #4: Hubo un tiempo en el que las corporaciónes de IT “clásicas.” dominaban la tierra.
- #5: Resulta muy poco eficiente, sobre todo si lo comparamos con algunos de nuestros competidores.
- #6: Estos lemures representan a nuestros competidores. TTM
- #7: No podemos cloudificarnos – no podemos ser otros -, pero podemos ser una mejor versión de lo que somos.
- #8: Basicamente queremos que todo el universo de mi empresa, esté modelizado
- #9: Cada objeto está relacionado con todos los demas. Physical Infraestrture : Todo lo que hay en un datacenter físico. Servidores físicos, RACS, UCS, Cabinas de discos, LUNs. Network Infraestructure: DNSs, Interfaces físicas y lógicas, IP,s Switchs, Catalyst, VLANs. Service Management: Gestión del servicio. Grupos, (Departamentios) Iniciatiivas Tickets, incidencias, arquitectura de las soluciones, permisos accesos.
- #12: En cierto sentido me gusta decir que la cmdb es de solo lectura, porque todos los días voy a recrear el backend, y sincronizarlo contra frontend
- #18: Esta es tu infraestructura a administrar. Cada día aprovisionamos el backend, recreandolo por completo. Atacamos el webservice para sincronizarlo con la CMDB.
- #20: Licencias github enterprise, Servidores sin uso, Proyectos obsoletos.