[ixpmanager] Multi IXP - Graphing

[Edrich de Lange]

Hi there

So Ive learnt quite a bit since the last mail.

I discovered you guys used the multi infrastructure to do the Cork network.
(which I was told wouldn't be good, but I think we have overcome most of
those issues :-)

The multi infrastructure seems to have fixed most of my issues :-), so
currently populating our three IXs each as a separate infrastructure.


Kind regards

[image: Inline image 1]

On Sun, Oct 1, 2017 at 12:09 PM, Barry O'Donovan <barry.odonovan at inex.ie>
wrote:

> Hi Edrich,
>
> > So fairly new user,
>
> Welcome!
>
> > We have a need to have the MultiInx graphing working. Is there any way
> > we can get this working, even if its semi manually for now? Is there any
> > hope to have that multi IXP functionality working.
>
> The history of multi-IXP functionality is that it was added under a
> commercial support arrangement with an organisation that never ended up
> using IXP Manager.
>
> Multi-IXP functionality is not functionality that INEX / the main
> developers want or need and nor is it something that the core target
> market for IXP Manager needs. The core/target market being small to
> medium IXPs.
>
> The unfortunate reality is that we have a feature list as long as our
> arms of things we want and need and so there is no possibility of that
> specific functionality being re-implemented in v4.
>
> It's not all dark and gloomy though:
>
> > Firstly, is there any other functionality that wasnt ported across from
> > the 3. codebase that affects Multi ixp.
>
> We have conscientiously dropped support for the explicit "multi-IXP"
> functionality. There is too much overhead and too little time to
> maintain code that is not core to the project.
>
> But:
>
> > Secondly, Ive heard of hacks to get the graphing working. Is there
> > anyone who can nudge me in the right direction?
>
> In the main, multi-IXP functionality provided ways of generating
> configuration for ancillary services on a per-IXP basis. As we move
> stuff from the older code base to the newer code base, we've generally
> stopped doing stuff on a per-IXP basis and now generate scripts as
> appropriate on a per-infrastructure or per-VLAN basis (VLANs being
> children of infrastructure).
>
> In other words, the multi-IXP functionality is mostly implemented by
> using infrastructures.
>
> One of the few things that I can think of that this doesn't include is
> graphing which, right now, is an 'all or nothing' system.
>
> We have however written a new graphing backend:
>
> http://docs.ixpmanager.org/features/grapher/
>
> It should be relatively easy for an experienced PHP programmer to copy
> the MRTG backend to create a new one that works on a per infrastructure
> basis.
>
> If you want to do this and the code is fit for purpose, we'd be happy to
> accept a pull request that includes:
>
>  - the code
>  - updates to the documentation
>
> See:
>
> https://github.com/inex/IXP-Manager/blob/master/CONTRIBUTING.md
>
> To ensure a PR is successful, it would be advisable to link in with us
> on the planned methodology.
>
> Cheers,
>  - Barry
>
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/listinfo/ixpmanager
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20171001/c6a667e2/attachment.html>