From smcmanus at peeringdb.com Thu Aug 6 13:27:58 2020 From: smcmanus at peeringdb.com (Stephen McManus) Date: Thu, 6 Aug 2020 16:27:58 -0400 Subject: [PDB Announce] PeeringDB 2.22.0 release - rescheduled to 2020-08-26 04:00 UTC In-Reply-To: <4DD86E96-5FCB-4927-B179-01A108A9014C@peeringdb.com> References: <8755FB38-6F4C-4F53-A2C2-790BC1A7C89E@peeringdb.com> <4DD86E96-5FCB-4927-B179-01A108A9014C@peeringdb.com> Message-ID: <6ED58ACD-E857-491D-9040-B4D55F1B1FC3@peeringdb.com> Apologies for the multiple reschedules, but we continue to find room for improvement in the major feature changes happening in this release. The production deployment is now scheduled for 2020-08-26 04:00 UTC. We appreciate the continued feedback from the community to keep PeeringDB running well! -Steve > On Jul 23, 2020, at 1:52 PM, Stephen McManus wrote: > > Due to issues found after the beta release, we have rescheduled this release to give us more time to address those issues. A new beta will be deployed by 2020-07-27. > > The production deployment is now scheduled for 2020-08-12 04:00 UTC. > > Thanks to everyone who gave feedback on the beta release, it really helps ensure high quality features in PeeringDB. > > -Steve > > > > >> On Jul 15, 2020, at 10:42 AM, Stephen McManus wrote: >> >> On Wednesday, July 29th at 04:00 UTC, the current beta site will be deployed unless any critical issues are found. This release contains several major changes to PeeringDB, so we are adding an extra week for beta testing. >> >> Your help in verifying that the upgrade went well by thoroughly testing https://beta.peeringdb.com would be greatly appreciated. Please review the changes and test against the beta site as necessary to prepare for a production roll out. In addition, we will also release the language packs that have reached maturity since our last release. >> >> Preview of the release is at: >> https://beta.peeringdb.com >> >> Release notes for v2.22.0 are here: >> https://docs.peeringdb.com/release_notes/#release-2220 >> >> Highlights for this release include: >> * Implementations of recommendations from the Data Ownership Task Force. This significantly changes how PeeringDB handles data from IX-F imports. >> * Data integrity and safety checks at multiple levels (application and database) >> >> We will be holding a webinar on July 21st to explain some of these changes to the community in more detail. Look forward to an announcement about that shortly. >> >> As always, let us know at support at peeringdb.com with any comments/questions/concerns. >> >> Steve McManus on behalf of PeeringDB ProductCom >> >> >> >> > From smcmanus at peeringdb.com Tue Aug 11 18:09:17 2020 From: smcmanus at peeringdb.com (Stephen McManus) Date: Tue, 11 Aug 2020 21:09:17 -0400 Subject: [PDB Announce] Peering DB Data Ownership Policy Implementation Webinar now @ 2020-08-17 14:00 UTC In-Reply-To: <0D82594C-2DE7-47ED-B55D-5ED388C8174D@peeringdb.com> References: <0D82594C-2DE7-47ED-B55D-5ED388C8174D@peeringdb.com> Message-ID: <0395B005-0F58-4DD3-BEEF-DFAD4E161DB1@peeringdb.com> All, We've resolved some outstanding issues with the release and have rescheduled this webinar for this Monday, August 17th to review the major changes with the community. The meeting information can be found below. During this Webinar we will cover how PeeringDB will soon begin to handle IX-F import data, creating, changing or deleting netixlan objects and other upcoming changes relating to the implementation of PeeringDB Data Ownership Policy. Please join us if you can but if you cannot, please note we also plan to record the Webinar and place it on the PeeringDB website for future reference. Data Ownership Webinar Mon, Aug 17, 2020 14:00 - 15:00 (GMT+00:00) Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/671628085 You can also dial in using your phone. United States: +1 (646) 749-3129 Access Code: 671-628-085 More phone numbers: Australia: +61 2 9087 3604 Austria: +43 7 2081 5427 Belgium: +32 28 93 7018 Brazil: +55 21 3500-3941 Bulgaria: +359 2 906 0605 Canada: +1 (647) 497-9391 Chile: +56 2 3214 9680 Colombia: +57 1 600 9953 Czech Republic: +420 2 55 71 95 02 Denmark: +45 32 72 03 82 Finland: +358 923 17 0568 France: +33 170 950 594 Germany: +49 721 9881 4161 Greece: +30 21 0 300 2583 Hungary: +36 1 933 3699 Ireland: +353 16 572 651 Israel: +972 3 376 3070 Italy: +39 0 247 92 13 01 Luxembourg: +352 34 2080 9219 Malaysia: +60 3 7724 4059 Mexico: +52 55 3687 7278 Netherlands: +31 207 941 377 New Zealand: +64 9 280 6302 Norway: +47 21 93 37 51 Panama: +507 308 4334 Peru: +51 1 642 9424 Romania: +40 31 780 1158 South Africa: +27 11 259 4924 Spain: +34 932 75 2004 Sweden: +46 853 527 827 Switzerland: +41 225 4599 78 Turkey: +90 212 900 4807 United Kingdom: +44 330 221 0088 New to GoToMeeting? Get the app now and be ready when your first meeting starts: https://global.gotomeeting.com/install/671628085 -Steve > On Jul 20, 2020, at 3:48 AM, Filiz Yilmaz wrote: > > > Dear PeeringDB Community, > > We have seen a number of issues reported since the beta announcement for v2.22.0 last week. > > Product Committee and Admin Committee Chairs have decided that previously announced webinar will be cancelled and rescheduled to a new date in about two weeks time, after majority of these issues are resolved. > > We will make an announcement once the new date for the webinar is set. > > Kind regards > Filiz Yilmaz > > > >> On 15 Jul 2020, at 17:41, Filiz Yilmaz wrote: >> >> [Apologies for multiple posts] >> >> >> Dear PeeringDB Community, >> >> >> You may remember Peering DB Data Ownership Policy was adopted in April 2020 and was handed over to Product Committee for implementation. >> >> >> As noted by Steve McManus, beta for 2.22.0 is now out and this release is packed with issues relating to the Peering DB Data Ownership Policy implementation. >> https://lists.peeringdb.com/pipermail/pdb-announce/2020-July/000155.html >> >> >> In order to raise awareness about this important release and to explain the upcoming changes to the community in more detail we are organising a Webinar. >> It will take place on 21 July 16:00 CEST. You can find the details below. >> >> >> During this Webinar we will cover how PeeringDB will soon begin to handle IX-F import data, creating, changing or deleting netixlan objects and other upcoming changes relating to the implementation of PeeringDB Data Ownership Policy. >> >> >> Please join us if you can but if you cannot, please note we also plan to record the Webinar and place it on the PeeringDB website for future reference. >> >> >> Kind regards >> Filiz Yilmaz >> PeeringDB >> Product Manager From smcmanus at peeringdb.com Tue Aug 18 07:34:00 2020 From: smcmanus at peeringdb.com (Stephen McManus) Date: Tue, 18 Aug 2020 10:34:00 -0400 Subject: [PDB Announce] Peering DB Data Ownership Policy Implementation Webinar now @ 2020-08-17 14:00 UTC In-Reply-To: <0395B005-0F58-4DD3-BEEF-DFAD4E161DB1@peeringdb.com> References: <0D82594C-2DE7-47ED-B55D-5ED388C8174D@peeringdb.com> <0395B005-0F58-4DD3-BEEF-DFAD4E161DB1@peeringdb.com> Message-ID: <5D324710-CEBD-4579-B5BF-E78A5936AECE@peeringdb.com> Thanks everyone who attended the webinar yesterday! The video of the webinar is now up on our new YouTube channel: https://youtu.be/mtT_HojbIPs and the slides are on the peeringdb docs page: https://docs.peeringdb.com/presentation/20200817-dtf-implementation.pdf -Steve > On Aug 11, 2020, at 9:09 PM, Stephen McManus wrote: > > All, > > We've resolved some outstanding issues with the release and have rescheduled this webinar for this Monday, August 17th to review the major changes with the community. The meeting information can be found below. > > During this Webinar we will cover how PeeringDB will soon begin to handle IX-F import data, creating, changing or deleting netixlan objects and other upcoming changes relating to the implementation of PeeringDB Data Ownership Policy. > > Please join us if you can but if you cannot, please note we also plan to record the Webinar and place it on the PeeringDB website for future reference. > > Data Ownership Webinar > Mon, Aug 17, 2020 14:00 - 15:00 (GMT+00:00) > > Please join my meeting from your computer, tablet or smartphone. > https://global.gotomeeting.com/join/671628085 > > You can also dial in using your phone. > United States: +1 (646) 749-3129 > > Access Code: 671-628-085 > > More phone numbers: > Australia: +61 2 9087 3604 > Austria: +43 7 2081 5427 > Belgium: +32 28 93 7018 > Brazil: +55 21 3500-3941 > Bulgaria: +359 2 906 0605 > Canada: +1 (647) 497-9391 > Chile: +56 2 3214 9680 > Colombia: +57 1 600 9953 > Czech Republic: +420 2 55 71 95 02 > Denmark: +45 32 72 03 82 > Finland: +358 923 17 0568 > France: +33 170 950 594 > Germany: +49 721 9881 4161 > Greece: +30 21 0 300 2583 > Hungary: +36 1 933 3699 > Ireland: +353 16 572 651 > Israel: +972 3 376 3070 > Italy: +39 0 247 92 13 01 > Luxembourg: +352 34 2080 9219 > Malaysia: +60 3 7724 4059 > Mexico: +52 55 3687 7278 > Netherlands: +31 207 941 377 > New Zealand: +64 9 280 6302 > Norway: +47 21 93 37 51 > Panama: +507 308 4334 > Peru: +51 1 642 9424 > Romania: +40 31 780 1158 > South Africa: +27 11 259 4924 > Spain: +34 932 75 2004 > Sweden: +46 853 527 827 > Switzerland: +41 225 4599 78 > Turkey: +90 212 900 4807 > United Kingdom: +44 330 221 0088 > > New to GoToMeeting? Get the app now and be ready when your first meeting starts: > https://global.gotomeeting.com/install/671628085 > > -Steve > >> On Jul 20, 2020, at 3:48 AM, Filiz Yilmaz wrote: >> >> >> Dear PeeringDB Community, >> >> We have seen a number of issues reported since the beta announcement for v2.22.0 last week. >> >> Product Committee and Admin Committee Chairs have decided that previously announced webinar will be cancelled and rescheduled to a new date in about two weeks time, after majority of these issues are resolved. >> >> We will make an announcement once the new date for the webinar is set. >> >> Kind regards >> Filiz Yilmaz >> >> >> >>> On 15 Jul 2020, at 17:41, Filiz Yilmaz wrote: >>> >>> [Apologies for multiple posts] >>> >>> >>> Dear PeeringDB Community, >>> >>> >>> You may remember Peering DB Data Ownership Policy was adopted in April 2020 and was handed over to Product Committee for implementation. >>> >>> >>> As noted by Steve McManus, beta for 2.22.0 is now out and this release is packed with issues relating to the Peering DB Data Ownership Policy implementation. >>> https://lists.peeringdb.com/pipermail/pdb-announce/2020-July/000155.html >>> >>> >>> In order to raise awareness about this important release and to explain the upcoming changes to the community in more detail we are organising a Webinar. >>> It will take place on 21 July 16:00 CEST. You can find the details below. >>> >>> >>> During this Webinar we will cover how PeeringDB will soon begin to handle IX-F import data, creating, changing or deleting netixlan objects and other upcoming changes relating to the implementation of PeeringDB Data Ownership Policy. >>> >>> >>> Please join us if you can but if you cannot, please note we also plan to record the Webinar and place it on the PeeringDB website for future reference. >>> >>> >>> Kind regards >>> Filiz Yilmaz >>> PeeringDB >>> Product Manager From smcmanus at peeringdb.com Fri Aug 21 07:42:52 2020 From: smcmanus at peeringdb.com (Stephen McManus) Date: Fri, 21 Aug 2020 10:42:52 -0400 Subject: [PDB Announce] Call for testing your network record in advance of upcoming v2.22.0 release at 2020-08-26 04:00 UTC In-Reply-To: <6ED58ACD-E857-491D-9040-B4D55F1B1FC3@peeringdb.com> References: <8755FB38-6F4C-4F53-A2C2-790BC1A7C89E@peeringdb.com> <4DD86E96-5FCB-4927-B179-01A108A9014C@peeringdb.com> <6ED58ACD-E857-491D-9040-B4D55F1B1FC3@peeringdb.com> Message-ID: <9CC7EC11-74BF-4AF4-9440-DB94A0C29FA5@peeringdb.com> All, The next release of PeeringDB will involve the re-enabling of the IX-F JSON Importer - a tool which syncs data from IXes into PeeringDB programatically. There's quite a few new features, and we haven't seen the volume of testing from the community we'd hope for such a major feature change. We would like the help of all network operators to perform the below steps to help test the IX-F JSON Importer. 1) Login at https://beta.peeringdb.com/ 2) Search for the network you manage and go to the page. 3) If your page contains "Review suggestions", please review the suggestions and test accepting them or dismissing them as appropriate. 4) Please report any bugs or other problems with this new feature to support at peeringdb.com. IX Operators - if you have an IX-F JSON export, please configure your URL, and to share this call for testing with your members. There may be instances where members are able to provide feedback regarding problems with your IX-F JSON export. The more these are discovered and corrected in advance of the production release, the better. We are making this explicit call for testing because we need your help to ensure wide testing coverage *before* the release hits production and potentially causes problems. Please take a few minutes today to perform the steps above. Note: The beta site's data is not written to production - feel free to alter it and edit it as much as you'd like, without fear of it reaching production. Similarly, do not expect the data to match the current production data set 100%. There will be differences. Details on these changes are up at: https://youtu.be/mtT_HojbIPs https://docs.peeringdb.com/presentation/20200817-dtf-implementation.pdf Steve McManus on behalf of PeeringDB ProductCom > On Aug 6, 2020, at 4:27 PM, Stephen McManus wrote: > > Apologies for the multiple reschedules, but we continue to find room for improvement in the major feature changes happening in this release. > > The production deployment is now scheduled for 2020-08-26 04:00 UTC. > > We appreciate the continued feedback from the community to keep PeeringDB running well! > > -Steve > > > > >> On Jul 23, 2020, at 1:52 PM, Stephen McManus wrote: >> >> Due to issues found after the beta release, we have rescheduled this release to give us more time to address those issues. A new beta will be deployed by 2020-07-27. >> >> The production deployment is now scheduled for 2020-08-12 04:00 UTC. >> >> Thanks to everyone who gave feedback on the beta release, it really helps ensure high quality features in PeeringDB. >> >> -Steve >> >> >> >> >>> On Jul 15, 2020, at 10:42 AM, Stephen McManus wrote: >>> >>> On Wednesday, July 29th at 04:00 UTC, the current beta site will be deployed unless any critical issues are found. This release contains several major changes to PeeringDB, so we are adding an extra week for beta testing. >>> >>> Your help in verifying that the upgrade went well by thoroughly testing https://beta.peeringdb.com would be greatly appreciated. Please review the changes and test against the beta site as necessary to prepare for a production roll out. In addition, we will also release the language packs that have reached maturity since our last release. >>> >>> Preview of the release is at: >>> https://beta.peeringdb.com >>> >>> Release notes for v2.22.0 are here: >>> https://docs.peeringdb.com/release_notes/#release-2220 >>> >>> Highlights for this release include: >>> * Implementations of recommendations from the Data Ownership Task Force. This significantly changes how PeeringDB handles data from IX-F imports. >>> * Data integrity and safety checks at multiple levels (application and database) >>> >>> We will be holding a webinar on July 21st to explain some of these changes to the community in more detail. Look forward to an announcement about that shortly. >>> >>> As always, let us know at support at peeringdb.com with any comments/questions/concerns. >>> >>> Steve McManus on behalf of PeeringDB ProductCom >>> >>> >>> >>> >> > From grizz at 20c.com Wed Aug 26 00:50:34 2020 From: grizz at 20c.com (Matt Griswold) Date: Wed, 26 Aug 2020 07:50:34 +0000 Subject: [PDB Announce] PeeringDB 2.22.0 release - rescheduled to 2020-08-26 04:00 UTC In-Reply-To: <6ED58ACD-E857-491D-9040-B4D55F1B1FC3@peeringdb.com> References: <8755FB38-6F4C-4F53-A2C2-790BC1A7C89E@peeringdb.com> <4DD86E96-5FCB-4927-B179-01A108A9014C@peeringdb.com> <6ED58ACD-E857-491D-9040-B4D55F1B1FC3@peeringdb.com> Message-ID: <20200826075034.4a4fc89b@segv> We are very pleased to announce that 2.22 was finally released! This was one of the bigger releases for PeeringDB and included an immense amount of changes resulting from the work done by the Data Ownership Task Force, thanks to all of you! This release includes a revamped IX-F JSON Importer. The Importer will initially be limited to a small number of IXes and will see wider use if testing goes well. In addition, new versions of django-peeringdb and peeringdb-py were released, and they're now first class citizens in our workflow, we promise not to neglect them anymore. Please let us know via support at peeringdb.com with any feedback. * Stephen McManus [200806 16:27 -0400]: > Apologies for the multiple reschedules, but we continue to find room > for improvement in the major feature changes happening in this > release. > > The production deployment is now scheduled for 2020-08-26 04:00 UTC. > > We appreciate the continued feedback from the community to keep > PeeringDB running well! > > -Steve > > > > > > On Jul 23, 2020, at 1:52 PM, Stephen McManus > > wrote: > > > > Due to issues found after the beta release, we have rescheduled > > this release to give us more time to address those issues. A new > > beta will be deployed by 2020-07-27. > > > > The production deployment is now scheduled for 2020-08-12 04:00 > > UTC. > > > > Thanks to everyone who gave feedback on the beta release, it really > > helps ensure high quality features in PeeringDB. > > > > -Steve > > > > > > > > > >> On Jul 15, 2020, at 10:42 AM, Stephen McManus > >> wrote: > >> > >> On Wednesday, July 29th at 04:00 UTC, the current beta site will > >> be deployed unless any critical issues are found. This release > >> contains several major changes to PeeringDB, so we are adding an > >> extra week for beta testing. > >> > >> Your help in verifying that the upgrade went well by thoroughly > >> testing https://beta.peeringdb.com would be greatly appreciated. > >> Please review the changes and test against the beta site as > >> necessary to prepare for a production roll out. In addition, we > >> will also release the language packs that have reached maturity > >> since our last release. > >> > >> Preview of the release is at: > >> https://beta.peeringdb.com > >> > >> Release notes for v2.22.0 are here: > >> https://docs.peeringdb.com/release_notes/#release-2220 > >> > >> Highlights for this release include: > >> * Implementations of recommendations from the Data Ownership Task > >> Force. This significantly changes how PeeringDB handles data > >> from IX-F imports. > >> * Data integrity and safety checks at multiple levels (application > >> and database) > >> > >> We will be holding a webinar on July 21st to explain some of these > >> changes to the community in more detail. Look forward to an > >> announcement about that shortly. > >> > >> As always, let us know at support at peeringdb.com with any > >> comments/questions/concerns. > >> > >> Steve McManus on behalf of PeeringDB ProductCom > >> > >> > >> > >> > > > > _______________________________________________ > Pdb-announce mailing list > Pdb-announce at lists.peeringdb.com > https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce