[PDB Announce] PeeringDB 2.6.x release at 2018-01-17T0400Z on new infrastructure

[Job Snijders]

Dear all,

The next release has been deployed as beta to https://beta.peeringdb.com/

This deploy was done on the new cloud infrastructure, so aside from the
usual bugfixes & new features, we also are swapping the hosting itself.
The PDB Operations team is very interested in feedback on anomalies in
performance or transport characteristics.

Notable features in this release are the ability to use PeeringDB as
OAuth provider, CVS/JSON export of searches (easy if you want to work in
a spreadsheet), a bunch of usability improvements and added sanity
checks on user submitted data.

For a full overview of the software changes, please take a look here:

    https://beta.peeringdb.com/changes

Thanks for testing!

Kind regards,

Job

On Sat, Dec 30, 2017 at 11:27:02AM +0100, Eric Loos wrote:
> This is a pre-release announcement for the next PeeringDB beta
> release, which will be deployment on or around the 8th of January and
> the push to product of the beta on 17th of January at 0400Z, however
> next to the expected improvements to PeeringDB functionality, there
> also will be significant changes on the underlying infrastructure.

> As per Job Snijders for the PeeringDB Operations Committee:
>
> "During the January 17th 2018 maintenance we intend to move the
> PeeringDB service from its current hosting location (NTT) to a cloud
> provider.  This is one of multiple steps to improve PeeringDB
> resilience and availability.
> 
> A full cloudification of PeeringDB (with 'full' we mean a multi region
> deployment, leveraging web services where possible) proved to be too
> challenging for a single migration. The Ops team uncovered
> complexities related to (lack of) feature parity between IPv4 and IPv6
> in various cloud services, and PDB's offering of non-HTTP based
> services such as finger & whois on the same DNS endpoints as the
> HTTP-related services.  We'll tackle those one by one in 2018.
> 
> During the January 17th maintenance, DNS records in the
> PeeringDB.{com,org,net} zones will be updated to point to a new set of
> IP addresses. The Ops team will ensure that at any given time there is
> only a single active instance (e.g. we'll shutdown the current
> instance, then migrate, and then enable the new instance). DNS TTLs
> are set to low values to ensure a smooth transition.
> 
> Also, the next beta release (scheduled for January 8th) will be
> deployed on infrastructure at the new hosting provider in order to
> test the new infrastructure prior to the production cut-over."
> 
> Your help in verifying that the framework upgrade went well by
> thoroughly testing https://beta.peeringdb.com would be greatly
> appreciated. Please review the changes and test against beta as
> necessary to prepare for the production roll out.
> 
> Preview is at: https://beta.peeringdb.com The changes that were
> incorporated in this release can be found here:
> https://beta.peeringdb.com/changes
> 
> As always, let us know at support at peeringdb.com with any
> comments/questions/concerns.
> 
> Eric Loos on behalf of PeeringDB ProductCom