[RELEASE] IXP Manager v6.0.0

[barryo]

We are pleased to announce the immediate availability of IXP Manager v6.0.0. Thanks to many of you for your patience to date - we know this release was some time in the making.

One of the biggest changes in v6 relates to a significant framework change - Doctrine ORM has been completely removed and replaced with Laravel's Eloquent. This work is thanks to @yannrobin who has done all the heavy-lifting on rewriting all database-related code within the project over the past few months. Using Eloquent, which is a key component of Laravel and integrates fully with the framework, should allow us to develop new features with greater ease and speed.

This release also introduces two new major features: core bundle management (inter-switch links) and database change logging.

Prerequisite: PHP v8 is required for IXP Manager v6.0.0. To help with this - and upgrading in general - we have also released a video tutorial of the IXP Manager v5.8.0 to v6.0.0 upgrade process which includes upgrading to PHP 8 on an existing system (e.g. Ubuntu 18.04 in the video) and a second option of upgrading to Ubuntu 20.04 and then to PHP 8.0.

All relevant collateral on the IXP Manager website and documentation has been updated for v6. This includes installation and upgrade video tutorials.

[pimvanpelt]

Excellent work, with much respect for your efforts from a tiny IXP operator in Geneva/Zurich/Lugano - Hi from Free-IX.

I upgraded the IXPManger from 5.8.0 to 6.0.0 and mostly things are fine thanks to the great pointers on the releases page.

A few things worth noting perhaps for others, too:

1. the scripting language has changed, in my case this required a few rewrites in welcome-email.blade.php, mostly easy to do thanks to the INEX default having been updated already in resources/skins/inex/customer/emails/welcome-email.blade.php
2. updating the SQL views errored out on me.
3. A bit more confusing to me, routeserver updated API may have a regression:

I'm using the Bird2 router updater tools/runtime/route-servers/api-reconfigure-example-birdv2.sh that ships with 5.8.0, and it has not changed in 6.0.0. Calling the updated endpoint succeeds but consistently returns the last value from before the upgrade.

$ curl -s -X POST -H "X-IXP-Manager-API-Key: ${KEY}" ${URL_DONE}/rs1-ipv4 | jq
{
  "last_updated": "2021-07-16T18:47:01+00:00",
  "last_updated_unix": 1626461221
}
$ curl -s -X GET -H "X-IXP-Manager-API-Key: ${KEY}" ${URL_DONE}/rs1-ipv4 | jq
{
  "last_updated": "2021-07-16T18:47:01+00:00",
  "last_updated_unix": 1626461221
}

Looking at http://ixpmanager.free-ix.net/router/list I see 'stale' entries, however looking at the live status on http://ixpmanager.free-ix.net/router/status the entries are fine.

[barryo]

Thanks for the detailed feedback @pimvanpelt - very helpful.

@yannrobin - could you put in a fixed for the welcome email template?

@pimvanpelt - The SQL views probably errored out because your SQL user needs SUPER privileges. This is covered on the release notes. If not, please provide the error message. In any case, the views are fairly much deprecated and I include them just in case someone is still relying on them.

@yannrobin - can you check the last issue too? The issue is here where I fixed a misunderstanding via 77ddfff but missed this. Basically, this change shouldn't have been made. Can you also then check that timestamps() actually works on the routers table?

[nickhilliard]

The views are still used for some of the sflow stuff. I don't think they're used anywhere else.

[pimvanpelt]

hey @nickhilliard and @barryo, my bad, (2) is a non-issue. Compare the first and second mysql client invocations, it's a bit hellish:

root@free-ix:/srv/ixpmanager# source /some/hidden/place/.ixp-manager-installer-settingsrc

## Broken -- mysql `-p` parameter does not like a space:
root@free-ix:/srv/ixpmanager# mysql -h $DB_HOST -u root -p $MYSQL_ROOT_PW $DB_DATABASE < tools/sql/views.sql 

## Happy times, this one does the job:
root@free-ix:/srv/ixpmanager# mysql -h $DB_HOST -u root -p$MYSQL_ROOT_PW $DB_DATABASE < tools/sql/views.sql 

Thanks for the intel on (3), it seems that should be easily addressed. I'm not too fussed about (1), but in case other users trip over it, at least understanding the pattern of dropping getters() from v6 could be a useful post-upgrade note.