In my opinion:
1) package naming (e.g.: linux-{headers,image}-generic-lts-CODENAME in DEFAULT_TRUSTY_PACKAGES)
2) _probably_, DEFAULT_TRUSTY_PACKAGES should be renamed to DEFAULT_UBUNTU_PACKAGES
3) also, codename/suite in tests
4) fuel_bootstrap/files/xenial can be copied from uel_bootstrap/files/trusty (don't forget about mcollective daemonize)
During investigation I've been found that mcollective shall be deamonized (or service type, in systemd notation, shall be simple instead of forking). Also, cloud-init-templates require some changes related to rc.local (missing shebang will cause 'unknown exec format' systemd error), and mcollective settings (daemonize parameter).
According to https:/ /blueprints. launchpad. net/fuel/ +spec/support- ubuntu- xenial- xerus we need to make a small changes in fuel-agent project.
In my opinion: headers, image}- generic- lts-CODENAME in DEFAULT_ TRUSTY_ PACKAGES) TRUSTY_ PACKAGES should be renamed to DEFAULT_ UBUNTU_ PACKAGES files/xenial can be copied from uel_bootstrap/ files/trusty (don't forget about mcollective daemonize)
1) package naming (e.g.: linux-{
2) _probably_, DEFAULT_
3) also, codename/suite in tests
4) fuel_bootstrap/
During investigation I've been found that mcollective shall be deamonized (or service type, in systemd notation, shall be simple instead of forking). Also, cloud-init- templates require some changes related to rc.local (missing shebang will cause 'unknown exec format' systemd error), and mcollective settings (daemonize parameter).