[ixpmanager] Change peering address

[Barry O'Donovan]

> Rolling out the portal and other activities has caused a slew or
> requests and it has caused the members to look at their information
> and want to change any incorrect or out of date information.

Ah, thanks for this information. That's a route I hadn't considered and
bumps that request up the list :)

> Also the mailing list stuff went a bit wrong and I had to fix that. I
> think it didn't delete the old contacts from the mailing list.

Quoting from the documentation: "NB: This facility does not perform a
100% synchronisation. Any mailing list members that are added separately
without a matching user in IXP Manager are not interfered with."

It can be made to optionally do 100% syncronisation I'm sure.

I also need to review how it works if a contact is deleted.

> We have lots of noc@ and peering@ addresses on the mailing lists, but
> the only way for members to manage their subscriptions via the portal
> is to make a fake contact for their peering@ address.

What we normally do here is set the CUSTADMIN account email address to
noc at example.com and then in the CUSTADMIN account Profile, one manages
those subscriptions.

Mailing list (mailman) functionality can be improved. It works for us
but there are even things we'd like such as:

  - subscription is linked to the 'user' rather than the 'contact' - this
should probably be changed in theory but in practice that creates the
issue of password syncronisation as well (for access to ML archives);

  - ability to subscribe users in the admin interface directly without
having to switch to the user;



> We have a script which tries to check that there is at least one
> subscription per member, which needs to be translated into the portal
> somehow.

Sounds like a useful item on my planned 'member health checkup' feature.

> We really, really, really need some "generic form" capability

Let's discuss this in Helsinki. Creating something like this should not 
be too difficult at all (i.e. form -> email within IXP Manager).

I have bigger plans for this kind of stuff (adding new members, adding / 
upgrading ports, enabling IPv6, etc).

I want to build a dynamic provisioning system which individual IXPs can 
change / add to quite easily to suit their own needs.

Each provisioning process (e.g. adding a new port) would have a number 
of steps and actions. E.g.

  - Customer requests new port (location, UTP/SMF/etc, speed)
  - Open admin task on IXP Manager
  - Admin assigns switch port, IP address, etc
  - Admin configures port on quarantine LAN
  - Admin sends preformatted email with x-connect details, quarantine IP 
details and route collector BGP sessions information;
  - Customer updates when they have the port up and can ping the 
quarantine ping beacon / route collector
  - Admin performs quarantine - updates customer with any issues
  - Port moved to production LAN
  - Route server / as112 sessions enabled (if appropriate)
  - Customer updated with instructions
  - Customer peers with above services
  - Tech mailing list notified
  - Billing tasks
  - Task closed.

These bits missing, but you get the point. Each step can have a state 
and task associated as well as IXP actions:

  - state - waiting on customer (remind option), waiting on admin
  - task - configure switch, check quarantine
  - IXP action - update port state (e.g. Quarantine -> Normal)


> We have now installed our shiny new servers, and we are almost ready
>  to try the peering manager, flow tools/route server stuff, should be
>  exciting!

Cool!


  - Barry