The document discusses the evolution of AMS-IX's provisioning system. Originally, the provisioning process involved manual copy-pasting of information between different systems and teams. This led to errors and inefficiencies. To address these issues, AMS-IX standardized procedures, developed scripts to automate tasks, and integrated email templates. These improvements reduced errors, sped up provisioning time, and allowed AMS-IX to scale to support new sites and exchanges. Current plans include further automating customer configurations and partner modifications to continue improving scalability and the customer experience.
2. Agenda
1. Definition of the provision system
2. Evolution of the provision system
3. Achievements and plans
3. Definition of provision system
Maksym Tulyuk, maksym.tulyuk@ams-ix.net
More-IP event, Amsterdam, 22nd May 2014
4. Provision system as Black Box
Customer
requests a link
AMS-IX provides
access to a VLAN
AMS-IX
provisio
n
system
link is a physical port(s) or rate-limit on a partners port
in 95% cases VLAN is Internet Peering VLAN
5. Inside The Black Box
reservatio
n
assignmen
t
testing
enabling
customers
request
signed documents
link is up
router is ready
7. Evolution of provision system
Maksym Tulyuk, maksym.tulyuk@ams-ix.net
More-IP event, Amsterdam, 22nd May 2014
8. Provision 4 years ago
customer: sends email to MR team
MR: copy&paste information into my.ams-ix and RT, and
sends email to NOC
NOC: copy&paste to browser to find free port
NOC: copy&paste to XML (internal database)
NOC: copy&paste to console to configure port
NOC: copy&paste to email to send reserved port to MR team
MR: copy&paste into ...
9. Issues with old systems
each engineer did it in his/her own way
a NOC engineer made a lot of errors
it took a lot of time and energy
it required a lot of the engineers
11. Procedures
Procedure = best practice
Write down existing processes
Constantly check and improve them
12. Scripts
One step" scripts: change configuration,
find free resources (port, IP address), etc
Do-it-all scripts: replacement of procedures
Require careful thinking
Have a lot of checks
13. Email templates
Replacement of copy&paste operations
Integration with my.ams-ix and our database
Flexibility via simple programming language
14. Historical perspective
Write down best practices as procedures
Replace the procedures with scripts
Generate emails via templates
16. Fixing the issues
his/her own way
a lot of errors
a lot of time and
energy
a lot of the engineers
standardisation
no errors
minimum and
predictive time
no engineers involved
17. Scalability
Four new sites in Amsterdam: Equinix 3,
EvoSwitch, Telecity 5, Terremark
Four new exchanges: CW, EA, HK, NY
19. Achievements
Free up engineers
Speed up provision
Scale up for new sites and exchanges
20. Plans
customer can add, remove and change
mac addresses
customer can configure BGP sessions
with route-servers and our router
partners can modify virtual links
21. Even more ideas
automatic testing and enabling
automatic addition of mac addresses, BGP
sessions, IPv6 addresses, etc
automatic operations (show logs, port status,
etc)
22. Summary
Simple concept of provision: request from
customer -> link from AMS-IX
From procedures to scripts
Automatic emails and processes
Scalability and growth
23. Big thanks!
m6_provision: Martin Pels
my.ams-ix: Martin Lyden, Petros and Peter
provision scripts: Gloria
XML: Steven
NOC and MR teams: feedback