yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

Public bug reported:

the vmware code that configures networking currently only supports
writing etc/network/interfaces (eni or ifupdown) format.  Additionally
it has its own code to write that data
(cloudinit/sources/helpers/vmware/imc/config_nic.py).

It would be better for it to use the renderers for ENI and sysconfig,
and then it will gain new backends as cloud-init does.

** Affects: cloud-init
     Importance: Medium
     Assignee: Sankar Tanguturi (sankaraditya)
         Status: Confirmed

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

** Changed in: cloud-init
   Importance: Undecided => Medium

** Merge proposal linked:
   https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/319866

** Changed in: cloud-init
     Assignee: (unassigned) => Sankar Tanguturi (sankaraditya)

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

Title:
  vmware customization only writes ENI network config

Status in cloud-init:
  Confirmed

Bug description:
  the vmware code that configures networking currently only supports
  writing etc/network/interfaces (eni or ifupdown) format.  Additionally
  it has its own code to write that data
  (cloudinit/sources/helpers/vmware/imc/config_nic.py).

  It would be better for it to use the renderers for ENI and sysconfig,
  and then it will gain new backends as cloud-init does.

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