FDU descriptor with more than one architecture

[gabrik]

It is odd that if I have an application that can run on multiple architectures (eg. a python script) I need to define different FDUs.

Ideally, it would be nice to have the possibility to list the supported architectures.

An example descriptor with multiple architectures can look like this:

---
  id: test-ping-fdu
  name: ping fdu
  version: 0.3.0
  fdu_version: 0.0.1
  hypervisor: bare
  computation_requirements:
      cpu_archs: [x86_64, aarch64, armv7l] 
      ram_size_mb: 10
      storage_size_mb: 1
  migration_kind : COLD
  hypervisor_specific : "{\"cmd\":\"ping\",\"args\":[\"1.1.1.1\"],\"env\":{}}"
  interfaces : []
  storage: []
  connection_points: []
  depends_on: []

Or the CPU architecture can be part of the image when the image is present:

---
  id: test-ros2-fdu
  name: ros2 test fdu
  version: 0.3.0
  fdu_version: 0.0.1
  hypervisor: ros2
  computation_requirements:
      ram_size_mb: 10
      storage_size_mb: 1
  migration_kind : COLD
  image:
      uris: [aarch64:https://www.myimagerepository/aarch64/demo_ws.tar.gz, x86_64:https://www.myimagerepository/x86_64/demo_ws.tar.gz]
      checksums: [aarch64:6d37f74bb8752e56a3b624cb40f8c053846f80d87ac4880a77fe3dca01636ad9,x86_64:dde6962f502d0ee4ec921fc452866ac792c9324f2ddd050023079a07b13619d1]
      format: tar.gz
  hypervisor_specific : "{\"kind\":\"RUN\",\"app_name\":\"examples_rclcpp_minimal_publisher\",\"entry_point\":\"publisher_member_function\",\"args\":[],\"env\":{}}"
  interfaces : []
  storage: []
  connection_points: []
  depends_on: []

Other ideas?