yahoo-eng-team team mailing list archive

[Andrew Kutz <1992512@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Per the netplan reference documentation (https://netplan.io/reference),
the scalar fields "gateway4" and "gateway6" have been deprecated:

> Deprecated, see Default routes. Set default gateway for IPv4/6, for
manual address configuration. This requires setting addresses too.
Gateway IPs must be in a form recognized by inet_pton(3). There should
only be a single gateway per IP address family set in your global
config, to make it unambiguous. If you need multiple default routes,
please define them via routing-policy.

However, I checked, and nothing in the Cloud-Init bug tracker or GitHub
repository indicates there are plans for Cloud-Init to address this
change:

* https://bugs.launchpad.net/cloud-init?field.searchtext=gateway4
* https://github.com/canonical/cloud-init/search?q=gateway4&type=issues

Additionally:

* the Cloud-Init network_state module still uses both fields -- https://github.com/canonical/cloud-init/blob/cd2cca35a1bf36b584422f431c3ddf55b820434c/cloudinit/net/network_state.py#L40-L41
* the Cloud-Init netplan module still references both fields -- https://github.com/canonical/cloud-init/blob/cd2cca35a1bf36b584422f431c3ddf55b820434c/cloudinit/net/netplan.py#L117-L120
* both fields are still part of the network unit tests -- https://github.com/canonical/cloud-init/blob/cd2cca35a1bf36b584422f431c3ddf55b820434c/tests/unittests/test_net.py#L478-L494

I am curious to find out:

* What is Cloud-Init's plan to handle the gateway4 and gateway6 fields?
* Will Cloud-Init deprecate them from their network v2 config to be aligned with netplan?
* Will Cloud-Init continue to support them and seamless produce the recommended default routes per netplan's documentation?
* What is the timeline for any such change or changes?

Thanks!

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
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/1992512

Title:
  gateway4 and gateway6 have been deprecated in netplan

Status in cloud-init:
  New

Bug description:
  Per the netplan reference documentation
  (https://netplan.io/reference), the scalar fields "gateway4" and
  "gateway6" have been deprecated:

  > Deprecated, see Default routes. Set default gateway for IPv4/6, for
  manual address configuration. This requires setting addresses too.
  Gateway IPs must be in a form recognized by inet_pton(3). There should
  only be a single gateway per IP address family set in your global
  config, to make it unambiguous. If you need multiple default routes,
  please define them via routing-policy.

  However, I checked, and nothing in the Cloud-Init bug tracker or
  GitHub repository indicates there are plans for Cloud-Init to address
  this change:

  * https://bugs.launchpad.net/cloud-init?field.searchtext=gateway4
  * https://github.com/canonical/cloud-init/search?q=gateway4&type=issues

  Additionally:

  * the Cloud-Init network_state module still uses both fields -- https://github.com/canonical/cloud-init/blob/cd2cca35a1bf36b584422f431c3ddf55b820434c/cloudinit/net/network_state.py#L40-L41
  * the Cloud-Init netplan module still references both fields -- https://github.com/canonical/cloud-init/blob/cd2cca35a1bf36b584422f431c3ddf55b820434c/cloudinit/net/netplan.py#L117-L120
  * both fields are still part of the network unit tests -- https://github.com/canonical/cloud-init/blob/cd2cca35a1bf36b584422f431c3ddf55b820434c/tests/unittests/test_net.py#L478-L494

  I am curious to find out:

  * What is Cloud-Init's plan to handle the gateway4 and gateway6 fields?
  * Will Cloud-Init deprecate them from their network v2 config to be aligned with netplan?
  * Will Cloud-Init continue to support them and seamless produce the recommended default routes per netplan's documentation?
  * What is the timeline for any such change or changes?

  Thanks!

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