[Bug 1612365] [NEW] Migrate LVFS to Amazon S3

[Mario Limonciello]

Public bug reported:

[Impact]

 * The current fwupd implementation bangs on an instance of LVFS (which runs on OpenShift).  As more distros have been picking up fwupd, it's become apparent that openshift can't scale and carry the load.
 * This has meant that FW updates can't be distributed in a timely manner and a lot of clients time out

 * Upstream is moving all data to Amazon S3 instead and keeping the LVFS openshift instance only as the frontend for OEM use.
This change happened upstream in this commit:
https://github.com/hughsie/fwupd/commit/96e1ea6b265728aad5bf43f18009abb3befc34a0

[Test Case]

1) Update to new fwupd package
2) run fwupdmgr refresh

Make sure that no errors are reported

[Regression Potential]

 * Regression potential is low.  The data is still signed with the same
keys, it's just been moved to a different backend.

** Affects: fwupd (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: fwupd (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Affects: fwupd (Ubuntu Yakkety)
     Importance: Undecided
         Status: New

** Also affects: fwupd (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: fwupd (Ubuntu Xenial)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fwupd in Ubuntu.
https://bugs.launchpad.net/bugs/1612365

Title:
  Migrate LVFS to Amazon S3

Status in fwupd package in Ubuntu:
  New
Status in fwupd source package in Xenial:
  New
Status in fwupd source package in Yakkety:
  New

Bug description:
  [Impact]

   * The current fwupd implementation bangs on an instance of LVFS (which runs on OpenShift).  As more distros have been picking up fwupd, it's become apparent that openshift can't scale and carry the load.
   * This has meant that FW updates can't be distributed in a timely manner and a lot of clients time out

   * Upstream is moving all data to Amazon S3 instead and keeping the LVFS openshift instance only as the frontend for OEM use.
  This change happened upstream in this commit:
  https://github.com/hughsie/fwupd/commit/96e1ea6b265728aad5bf43f18009abb3befc34a0

  [Test Case]

  1) Update to new fwupd package
  2) run fwupdmgr refresh

  Make sure that no errors are reported

  [Regression Potential]

   * Regression potential is low.  The data is still signed with the
  same keys, it's just been moved to a different backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1612365/+subscriptions