canonical-ubuntu-qa team mailing list archive

[Skia <2058558@xxxxxxxxxxxxxxxxxx>]

** Merge proposal linked:
   https://code.launchpad.net/~hyask/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462858

** Changed in: auto-package-testing
       Status: New => In Progress

** Changed in: auto-package-testing
     Assignee: (unassigned) => Skia (hyask)

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058558

Title:
  dump-lxd-remotes does not produce a usable yaml file

Status in Auto Package Testing:
  In Progress

Bug description:
  I wanted to set the `n-workers` value for the autopkgtest-cloud-
  workers using juju config so I looked at dump-lxd-remotes to figure
  out how to produce a yaml file to set the value. However, the yaml
  file produced by "juju config autopkgtest-lxd-worker lxd-remotes" is
  actually usable. I needed to construct a yaml file that looked like
  this:

  autopkgtest-cloud-worker:
    n-workers: 
      "  lcy02:\n    amd64: 65\n  bos01:\n    arm64: 20\n    ppc64el: 20\n    s390x: 20\n  bos02:\n    arm64: 20\n    ppc64el: 20\n    s390x: 22\n  bos03:\n    arm64: 25"

  Manipulating the output of the juju config to produce something like
  this seems rather hard, so maybe there is another format that would
  work? I actually looked at canonical-mojo-specs for ideas on the
  proper formatting so maybe somebody else can figure out the right
  format.

  dump-lxd-remotes needs fixing to produce something usable be it ugly
  or beautiful. Additionally, it would be lovely if we use the same
  script to dump the n-workers ... something like yaml-dump autopkgtest-
  cloud-worker n-workers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058558/+subscriptions