| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Yocto implements ptest classes for recipes. In general OpenBMC doesn't
implement ptest for any of its recipes. This is the first in an attempt
to change that, specifically, this enables ptest for the bmcweb recipe.
Examples for ptest + meson recipes are pulled from here:
http://layers.openembedded.org/layerindex/branch/master/recipes/?q=inherits%3Aptest+inherits%3Ameson
This commit implements the base ptest functionalityrequired to be able
to install and run the unit tests already present in bmcweb. The
specific changes are:
1. bmcweb recipe now inherits from ptest
2. When ptest is enabled, bmcweb now requires gtest and gmock
dependencies. This is done by updating DEPENDS. We also now require
bash at runtime, so that dependency is added, as that seems to be what
the upstream recipes do.
3. The meta-layer now includes a "run-ptest" script. This seems to be
the common convention in the upstream yocto recipes to include in the
meta layer so we should do the same thing here for consistency, even if
it is a little unconventional or odd.
To enable this and try it out, insert the following into your local.conf
DISTRO_FEATURES_append = " ptest"
CORE_IMAGE_EXTRA_INSTALL += "bmcweb-ptest"
This will add bmcweb ptests to your build. Keep in mind, this takes a
lot of flash space, so qemu is likely the best target, unless you're on
a system with eMMC, or a lot of SPI flash free. Once your system has
booted, you can run the tests by executing ptest_runner.
https://wiki.yoctoproject.org/wiki/Ptest
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I8c45c98afb941953c1855de2f3db10deea465b2a
|
|
Use the systemd service and socket unit files provided by bmcweb.
(From meta-phosphor rev: 8a5dc119cb1136a5a475c4b8a6b63ae1a6a13529)
Change-Id: Idec60b62def5df7238124f87d105765d6065bc63
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This patchset replaces the python based phorphor-rest implementation
with bmcweb, a c++ implementation.
bmcweb has several advantages to phosphor rest, and should be the
default implementation for new BMCs. Some of the advantages include:
1. Authentication and authorization is based on PAM
2. Its written in a compiled language, which gives it more applicability
for low resource systems with lower memory.
3. It replicates all the existing phosphor-rest interfaces.
4. Smaller binary size. The bmcweb binary compresses to 800KB at last
measure.
5. bmcweb implements a compliant redfish interface, which phosphor-rest
does not.
6. bmcweb has a selectable build, so features can be enabled/disabled
per platform as needed.
(From meta-phosphor rev: 7bfe2964d1c263d7104fcaabc42806ad0bcff331)
Change-Id: I4a9b5169c2151de633b5227612f15a9e7a771683
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
