yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1855430@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => 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/1855430

Title:
  Unclear documentation how a complete minimal working configuration
  could look like for Ubuntu and Apache CloudStack

Status in cloud-init:
  Expired

Bug description:
  It's certainly clear that there are lots of possible configuration
  combinations (OSxProvider).

  Initially, I have thought that picking up the relevant configuration
  by pieces would work, but then reading the manual leaves some
  uncertainties.

  - information that you can place the configuration either in
  /etc/cloud/cloud.cfg or in /etc/cloud/cloud.cfg.d/* should be placed
  more prominently in an opening section, maybe also with an explained
  possible layout in the least. Are both ways idempotent, say, you could
  place everything in the single config file?

  - for example for network configuration, the documentation
  https://cloudinit.readthedocs.io/en/latest/topics/network-config-
  format-v2.html says "ethernets: []" is a valid default piece of
  configuration. Is it equivalent to using the "match" keyword with an
  asterisk?

  - for CloudStack, is the data source configuration also a valid
  complete minimal configuration so that the machine is able to
  configure a default DHCP network and get metadata?

  - debug: "verbose: true/false (defaulting to true)" does this mean,
  "verbose" is not needed but the "debug" statement has to be there to
  produce output?

  - logging: "The default config is given as "output: { all: "| tee -a
  /var/log/cloud-init-output.log" }" - does it mean, for default logging
  I do not need to provide the "output" statement or exactly that is
  required to enabled it?

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