[ixpmanager] Packaging IXP Manager

[Barry O'Donovan]

Mike Hammett wrote on 31/05/2019 21:33:
> Right, but getting the IXP Manager application up is probably only 
> 1/10th of the work of getting everything running.

Just to add to this (and I think we've discussed it before on this 
mailing list and possibly with you Mike) - one thing we specifically and 
openly state that we do want IXP Manager to become is an "IXP in a box".

Runing an IX is a complicated and difficult task that requires a good 
understanding of networking and system administration. It's also a 
serious responsibility.

We feel strongly that anyone that starts an IX should be able to build 
and thus understand the different services well. And, when things go 
wrong (as they invariably do) they should be able to use that knowledge 
and experience to discover and fix issues.

IXP Manager is fairly prescriptive on some things (and purposely so) but 
not on others (such as operating systems for route servers, switch make 
and models, etc). These are left to each IX to decide based on their own 
unique set of skills and abilities and resources.

In your own case - "a functional IXP Manager install for our own use for 
multiple IX locations" - I would submit that this is best achieved 
internally yourselves using Salt / Ansible / Puppet / Chef. If you can 
make it work, open sourcing and documenting and presenting the story of 
"here's how we did it and these are the choices we made because of 
x/y/z" could add value.


  - Barry




> 
> I didn't necessarily mean for you you guys to maintain it. I'm talking 
> to someone else about managing some of our IXP Manager stuff, so I might 
> work with them to just package it up.
> 
> 
> 
> -----
> Mike Hammett
> Intelligent Computing Solutions <http://www.ics-il.com/>
> <https://www.facebook.com/ICSIL><https://plus.google.com/+IntelligentComputingSolutionsDeKalb><https://www.linkedin.com/company/intelligent-computing-solutions><https://twitter.com/ICSIL>
> Midwest Internet Exchange <http://www.midwest-ix.com/>
> <https://www.facebook.com/mdwestix><https://www.linkedin.com/company/midwest-internet-exchange><https://twitter.com/mdwestix>
> The Brothers WISP <http://www.thebrotherswisp.com/>
> <https://www.facebook.com/thebrotherswisp><https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg>
> ------------------------------------------------------------------------
> *From: *"Nick Hilliard (INEX)" <nick at inex.ie>
> *To: *"INEX IXP Manager Users Mailing List" <ixpmanager at inex.ie>, "Mike 
> Hammett" <ixp-manager at ics-il.net>
> *Sent: *Friday, May 31, 2019 3:19:43 PM
> *Subject: *Re: [ixpmanager] Packaging IXP Manager
> 
> Mike Hammett wrote on 31/05/2019 16:32:
>  > The reason I ask is that there's a lot of work beyond just answering the
>  > questions in the provided setup script in getting a fully featured IXP
>  > Manager setup working.
> 
> there's a lot of work in getting a fully featured IXP setup working.
> 
> Packaging the application has been done - it's packaged using git and
> composer.  There's also a docker image.
> 
> Creating VM images also creates a responsibility to maintain those
> images.  All these things take time, and we'd prefer to spend that time
> making the install easier and the documentation better.
> 
> Nick
> 
> 
> 
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager
> 


-- 

Kind regards,
Barry O'Donovan
INEX Operations

https://www.inex.ie/support/
+353 1 531 3339