Meeting recording
- Open Networking User Group updated content in the WebEx meeting space
Change Management/Automated Initial Configuration Working Group–ONUG Fall 15.
Attendees:
- Ted Turner
- Brian Hedstrom
- Maxime Bugat
- ??Matthew Caesar
- ??Nick Lippis – CoFounder /Co-Chair Open Network User Group
Vendor Attendees:
- Stefan Dietrich – Glue Networks
- ??Michael Githens – Ixia – testing sponsor, helping us validate solutions
Agenda:
- Introductions – quick recaps
- Automation tools
- Leave this to the vendors to help us understand what tool sets look like
- Future capabilities – RESTFul interfaces
- Brownfield – is this possible, desirable, cost effective
- Look to service providers to share capabilities for automated provisioning
- Leads towards deep capability in administrative domains
- ALSO leads to coordination of capabilities across administrative domains
- Potential “shared use cases” and “pain points” with sister working groups
- WG-Orchestration
- single administrative domains (switching, routing, etc)
- across multiple administrative domains (security, network, application, service providers, user self service)
- WG-Network State Collection, Correlation and Analytics
- WG-Federation
- WG-Orchestration
- Automated Initial Configuration?
- Need to better define administrative domains – ability to define deep dive technologies
- See definitions from WG – Network State Collection, Correlation and Analytics
- Need to better define, inter operation across domains
- Need to better define administrative domains – ability to define deep dive technologies
- Pain Point review
- completed – helped identify why our use cases exist
- Use Cases
- These topics are meaty and complex.
- How many of these items should we cover for presentation in the Fall ONUG meeting?
- Call outs for multiple domains, as identified in the use cases
- Action Items
- Seek more interaction with ONUG membership / working group members
- Reach out to sister working groups to minimize the amount of re-work
- Move to bi-weekly meeting format
- Start formatting build / flow for presentation for ONUG Fall
- Ideas / concepts of ONUG membership
- Integration of previous definitions by working groups
- Review opportunities for vendors to showcase solutions for ONUG membership
- There are probably three tracks
— legacy (brownfield)
— current technologies not widely adopted (think NetConf, Yang)
— new (Restful API, with scaling triggers – think AWS cloud bursting)
- There are probably three tracks
Pain Points identified contributing to use cases
- Ted’s new example, based on hallway conversation today – new firewall implementations with a global footprint
- VMWare is too expensive – businesses are moving to Open Stack
- If a configuration can be identified as predictable and safe….
- Can the change be automated
- How can changes be validated
- If desired outcomes are not achieved, execute automatic roll back
- Change design and validation
- During provisioning or change implementation
- Brown field
- Include provisioning of older network gear when building new network zones
- Real need for “current build” network modelling
- Leads to deficiency / fault remediation
- Leads to fault remediation – automation
Review previous use cases – looking for top 10 (high level items from previous meeting listed here)
- Enterprise AP provisioning for thousands of APs, with hundreds of nodes attached each
- Enterprise network LAN provisioning, with unique templates / cases for specific types of connected devices
- Add entire environments
- Add servers
- Network component automation
- Automate network services
- Data center automation
- Cloud orchestration
- Hybrid cloud integration
- WAN management / path selection /path optimization
- Users / subscribers