1 / 12

CANARIE Network Tools Development

User Portal ( ie . CMDB) Development Plan (v 0.1). CANARIE Network Tools Development. Ryan Davies | May 6, 2014. About CANARIE. CANARIE designs, delivers, and drives the adoption of digital infrastructure for Canada’s research and education communities. Proposed Structure. User Layer.

dutch
Download Presentation

CANARIE Network Tools Development

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. User Portal (ie. CMDB) Development Plan (v 0.1) CANARIE Network Tools Development Ryan Davies | May 6, 2014

  2. About CANARIE CANARIE designs, delivers, and drives the adoption of digital infrastructure for Canada’s research and education communities.

  3. Proposed Structure

  4. User Layer Web App • Likely be based on a framework (ie. Ruby, Django, etc.) • To include modules for display (ex. plotting) and submission (ex. configuration settings) to/from the Collimation/Distribution Layer • CAF-enabled • Mobile view • Dashboard view Push Generator • Passive e-mailer, prompted into action by C/D Layer (ex. Notification Module)

  5. Collimation/Distribution Layer Configuration • Stores, retrieves, alters Service configuration Status & Reports Compilation • Retrieves, processes, and formats data from Services • Example: “retrieve IP-layer uptime data for link A-B, aggregated hourly, for Q1 2014”… to be plotted by Web App

  6. Collimation/Distribution Layer (cont’d.) Notification & Alarms • Regularly monitors* Services, and determines whether an alarm or notification is warranted • Collimates alarms where feasible, to reduce quantity • Determines affected services/users • Triggers Push Generator and updates Web App automatically * Monitoring cycles triggered regularly by Polling Tickerand on-demand based on receipt of traps by Trap Listener

  7. Collimation/Distribution Layer (cont’d.) User Management • For User Layer • CAF-integrated History Management • Logs and stores all configuration changes, notifications, reports for historical purposes and reversion

  8. Service Layer • Modules! • Examples: router config, LightPath management, asset management, FlowData collection, perfSONAR monitoring, etc. • Integration with other tools (examples sought)

  9. Network Layer (Interface to underlying network devices. Not yet clearly defined.)

  10. Infrastructure Database • ie. CMDB! • Network Information Base • Storage repository for Service modules • Storage repository for Collimation/Distribution modules Polling Ticker • Effectively, a cron that regularly triggers hooked modules, ie. perfSONAR polling, Notification & Alarms, etc. Trap Listener • Daemon that will trigger hooked modules upon receipt of traps

  11. Use Cases (To be gathered)

More Related