Hi, A git repository is required to publish a new meta layer called meta-intel-edge-consolidation. This layer leverages recipes from meta-intel, meta-openembedded, meta-virtualization, meta-acrn and others for AI workload consolidation at the edge. It provides different system configurations for virtualization depending on the workload isolation level and required orchestration capabilities. Thank you, Francois
Copying recipes around perhaps is not a good idea, but bbappends are good to add customizations needed. So I think for this to be effective for layers it will be good to see if it can work well with layers it depends on.
The only recipes that would be "copied around" are those in dynamic-layers because of backporting needs--where those recipes would not be accepted by the upstream stable layers. Every attempt is being made to upstream our new recipes to the layers where they belong (e.g. the addition of hashicorp-serf to meta-virtualization). This umbrella layer adds packagegroups and images that leverage other layers, but in a more coherent fashion, e.g. an image with KVM and a guest OS ready to run Docker container workloads. It also utilizes the kas tool to make both "manifest" (the layers and their specific branches or commits) and "configuration" (what normally goes in bblayers.conf, local.conf, etc.) easier out of the box.
(In reply to comment #2) > The only recipes that would be "copied around" are those in dynamic-layers > because of backporting needs--where those recipes would not be accepted by > the upstream stable layers. Every attempt is being made to upstream our new > recipes to the layers where they belong (e.g. the addition of hashicorp-serf > to meta-virtualization). This umbrella layer adds packagegroups and images > that leverage other layers, but in a more coherent fashion, e.g. an image > with KVM and a guest OS ready to run Docker container workloads. It also > utilizes the kas tool to make both "manifest" (the layers and their specific > branches or commits) and "configuration" (what normally goes in > bblayers.conf, local.conf, etc.) easier out of the box. I am just commenting based on what information you guys are putting out, it perhaps would be better to post skeleton tree of layer perhaps can give better idea.
Given its namespaced as a meta-intel component I think this is fine.
The original project has been abandoned, so this request is no longer needed.