yahoo-eng-team team mailing list archive

[James Falcon <1972819@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3973

** Bug watch added: github.com/canonical/cloud-init/issues #3973
   https://github.com/canonical/cloud-init/issues/3973

** Changed in: cloud-init
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1972819

Title:
  Firecracker Metadata Service + NoCloud source - API TOKEN required
  with MMDS v2 (v1 deprecated)

Status in cloud-init:
  Expired

Bug description:
  Hello,

  I noticed the Firecracker 1.1.0 hypervisor announced MMDS v1
  deprecation in favor of MMDS v2 (https://github.com/firecracker-
  microvm/firecracker/releases/tag/v1.1.0).

  The MMDS v2 is a a session-oriented and request to get and use
  API_TOKEN like EC2 Metadata service IMDSv2.

  Cloud-init can be used with firecracker medatada service using NoCloud
  data source as is described in https://ongres.com/blog/automation-to-
  run-vms-based-on-vanilla-cloud-images-on-firecracker/. However this is
  going to stop to work with MMDS v2 where the guest cannot get any
  user-data/meta-data by cloud-init any more due to missing API_TOKEN in
  request.

  Can you please implement API_TOKEN feature into NoCloud data source?

  Many thanks,

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1972819/+subscriptions