1 / 16

Infastructure documentations Flowchart,schemas and usefull informations

Infastructure documentations Flowchart,schemas and usefull informations. Pierre-Luc Dion pdion@cloudops.com. Overview. Various type of schema Usefull Information to provide ( Ops perspective) Flowchart ( my favorite) Share your opinions and ideas.

keely
Download Presentation

Infastructure documentations Flowchart,schemas and usefull informations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Infastructure documentationsFlowchart,schemas and usefull informations Pierre-Luc Dion pdion@cloudops.com

  2. Overview • Various type of schema • Usefull Information to provide (Ops perspective) • Flowchart (my favorite) • Shareyour opinions and ideas

  3. Usefulltools for your docs • Text • Anything that is collaborative and can be shared and remain protected. • Google apps (doc, spreadsheet, sites) • wiki • docuwiki • confluence • mediawiki • sharepoint • Graphs • Tool you will be confortable to work with • Visio • Lucidchart • Confluence (plugin) • Lot of Visio shapes available: • http://www.visiocafe.com/

  4. Schemas • Separate OSI layer in different schemas • Layer 2 (link layer) • physical connectivity • Ethernet • Layer 3 (network layer) • IP, routing layer • Layer 4 (transport layer) • Flowchart, applications communications

  5. Layer 2 example

  6. Layer 3 example

  7. Layer 4 example

  8. Valuable information in the flowChart Each box is an application (ex: process, webserver, database, JVM,…) • OS type, IP, hostname • Application name/type • Listen port(s) • init script • path to log files • Arrow express connection initiation (not the direction of data)

  9. event more… • Hypervisor (it’s a VM/instance/Bare) • NFS share if it’s required by Apps • Backup: software connectivity and origin • Which system USER is use to execute the app • Automation system connectivity

  10. Flowchart does not contain • SNMP • System admin (RDP, SSH, Telnet,…) • Unreleated to the application stack (system cron, system daemons) • NTP • Hypervisor tool (vmware tools, xentools,…)

  11. Tricks of the trade • Build your own Visio Stencils (shapes) • Top to bottom mean from Insecure to Secure • Have a color coding for app boxes

  12. When to Start the documentation? • Before the project begin • As you learn the application stack

  13. Before the project start Based on: • assumptions • Known applications that will be use • What it should look like Will allow you to • Understand dependencies;firewalland connectivity • What need to be build as infrastructure

  14. As you learn the system • Allow you to validate what you understand on the application stack. • Sometime it help existing team to better understand what they build and/or support

  15. Enough • Time to see more examples…

  16. C’estfini Thank you Questions/Comments?

More Related