| Summary: | Add a mechanism for creating build appliance as a container image | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Runtime | Reporter: | Randy Witt <randy.e.witt> |
| Component: | build-appliance | Assignee: | brian avery <brian.avery> |
| Status: | RESOLVED OBSOLETE | QA Contact: | David Lopez Barriba <davidx.lopez.barriba> |
| Severity: | enhancement | ||
| Priority: | High | CC: | bluelightning, brian.avery, jose.perez.carranza, konrad.scherer, randy.macleod, richard.purdie, sgw |
| Version: | 2.2 | ||
| Target Milestone: | 2.3 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
| Bug Depends on: | 10528, 10713, 10768 | ||
| Bug Blocks: | 10769 | ||
|
Description
Randy Witt
2016-05-04 23:21:05 UTC
Reassigning to Brian since he wants to leverage the existing crops containers. AFAIK, the remaining functionality missing from the CROPS/container et al family is the ability to run qemu with a graphical display. RFC sent out . Awaiting feedback. Mail sent to open embedded architecture list. Several questions came up and were answered/pointed to bugs that are being worked on. ML reference: http://lists.openembedded.org/pipermail/openembedded-architecture/2016-December/000348.html We have agreed that the containers serve a different purpose from the Build Appliance. The containers provide a lightweight way to use the YP. The Build Appliance is a complete image dogfooding test which verifies we can rebuild an image from an image we created. Because of this, we are keeping both the Build Appliance and the containers so I am marking this as resolved/obsolete as we chose not to go down the path of deprecating the Build Appliance. |