multi-arch arm64/amd64 support

[Alan Baghumian]

It would be nice to be able to set a juju configuration option so the charm can generate a separate image per requested architecture. For instance arm64 and amd64.

Thank you,
Alan

--

ed: just to clarify (see comment #5), this is more about being able to do multiple image retrofits in one command and ensure that https://bugs.launchpad.net/charm-octavia-diskimage-retrofit/+bug/2016344 correspondingly sets the image property for architecture.

[Alex Kavanagh (ajkavanagh)]

This ought to be possible from the charm action itself. The architecture of the image is taken from the 'source-image' that is 'retrofitted'. From the actions.yaml for the charm:

retrofit-image:
  description: |
    Trigger image retrofitting process
  params:
    source-image:
      type: string
      default: ''
      description: |
        Optionally specify ID of image in Glance to use as source for the
        retrofitting. The default is to automatically select the most
        recent Ubuntu Server or Minimal daily Cloud image.
    force:
      type: boolean
      default: False
      description: |
        Force re-retrofitting image despite presence of apparently up to
        date target image.

i.e. if an arm64 image is used as a source-image, the resultant retrofitted image should be the same architecture.

If I've misunderstood, please do comment! thanks.

[Alex Kavanagh (ajkavanagh)]

Triage: setting to incomplete as I may not have understood the issue and have requested additional info.

[Alex Kavanagh (ajkavanagh)]

Hi Alan

> The issues is not with the retrofitting per se, but what information is ultimately saved in the database.

> Essentially the architecture (eg. architecture='x86_64') property is missing by default causing scheduling issues on the OpenStack side.

Isn't this effectively what https://bugs.launchpad.net/charm-octavia-diskimage-retrofit/+bug/2016344 is also asking? i.e. this bug may be a duplicate of that one? Just checking I'm understanding and there isn't something I'm missing.

Thanks
Alex.

[Alan Baghumian (alanbach)]

Scratch my previous comment, It was related to LP# 2016344.

It would be nice to be able to retrofit images from both arm64 and amd64 architectures at the same time.

Using the source-image enables us to use one or another but not both.

Perhaps if we could expand on this to map to multiple image sources and read the respective architecture from the respective image.

Just a thought.

[Alex Kavanagh (ajkavanagh)]

> It would be nice to be able to retrofit images from both arm64 and amd64 architectures at the same time.

> Using the source-image enables us to use one or another but not both.

> Perhaps if we could expand on this to map to multiple image sources and read the respective architecture from the respective image.

Yup, this is a current limitation of the current charm. In order to do two different architectures, the retrofit action would need to be run twice with different source-image parameters. I'm going to edit the description to fit. Thanks for the feature request!