[190004] in North American Network Operators' Group
Thinking Methodically about building a PoC
daemon@ATHENA.MIT.EDU (Kasper Adel)
Mon Jun 13 00:18:00 2016
X-Original-To: nanog@nanog.org
From: Kasper Adel <karim.adel@gmail.com>
Date: Sun, 12 Jun 2016 18:52:20 -0700
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
hi,
I am asked to build a large lab/test it. I'm provided crazy scale numbers
for lots of technologies (L*VPN, IPv*, IGP*, All Tunnels flavors...etc).
It took me a lot of time to build this lab, because when I got the
request/test plan handed over to me, I did not verify that these scaled
numbers are even possible, not to mention the combination. I assumed some
thought/research were done before.
I'm trying to put together a list of the lessons learned, and the right way
to do this for future reference, specially that this project was time
critical and I got beaten hard because I did not deliver on time.
So my question is, in your extensive experience, what is the right
method/approach to this kind of task:
1) Get started immediately (MVP), things will break, tune it along the way.
2) Do some planning and research first.
I'd appreciate any references to 'software engineering' or other industries/
Thanks
