summaryrefslogtreecommitdiff
path: root/meta-ibm/recipes-phosphor/bmcweb/bmcweb_%.bbappend
AgeCommit message (Collapse)AuthorFilesLines
2020-09-03Move bmcweb bbappend files to interfacesManojkiran Eda1-8/+0
- meta-phosphor has bmcweb bitbake file under interfaces,so moving the append files accordingly. (From meta-ibm rev: b7952717a7c74b0ebda2d7971f75b1b060f8911c) Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I86ba09396f109f0987220bcdd070a0fff8e1e972 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-27meta-ibm: move all meta-witherspoon metadataBrad Bishop1-0/+5
The metadata common to all IBM systems is confusingly split between meta-ibm and meta-witherspoon. Move everything to meta-ibm. The meta-ibm README is re-written to more accurately reflect the scope of the layer. Allow the configuration samples (bblayers.conf.sample, local.conf.sample) to be sourced from either meta-ibm or meta-witherspoon until such a time that any workflows and tooling have had the opportunity to move to meta-ibm. (From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442) Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-07-09Enable TFTP updates via RedfishAndrew Geissler1-0/+3
TFTP is already enabled by default using the existing REST api's. Code was put in recently to also support TFTP via the Redfish UpdateServices.SimpleUpdate object. By default this is disabled within bmcweb. Enable it by default on all IBM systems to keep parity with the existing REST api's Tested: curl -k -H "X-Auth-Token: $TOKEN" -X GET https://${BMC_IP}/redfish/v1/UpdateService { "@odata.context": "/redfish/v1/$metadata#UpdateService.UpdateService", "@odata.id": "/redfish/v1/UpdateService", "@odata.type": "#UpdateService.v1_2_0.UpdateService", "Actions": { "#UpdateService.SimpleUpdate": { "TransferProtocol@Redfish.AllowableValues": [ "TFTP" ], "target": "/redfish/v1/UpdateService/Actions/UpdateService.SimpleUpdate" } (From meta-ibm rev: f93d1c8da15a0d73be54b80eb0f042733d1f314f) Change-Id: I2a9980b4bbb3bfd50550881e206154d1f69c0a24 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-02-01meta-ibm: Remove bmcweb overridesMatt Spinler1-10/+0
As bmcweb will be enabled from meta-phoshor, that's where the socket and service files will be, and where the repo will be pulled in from. No need to it from meta-ibm. (From meta-ibm rev: e9f1abf282032579fb400d5511760de080cbeac2) Change-Id: Ifa94158a2401eaad6eb44dbed1ca9bf81bce0e35 Signed-off-by: Matt Spinler <spinler@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-22Revert "Disable bmcweb static hosting in IBM layer"Gunnar Mills1-1/+1
This reverts commit 8891e02efa759bb3173a0985f194c1e9a0bc255b. openbmc/bmcweb#5 has been fixed. This static hosting is needed for the RedfishServiceValidator.py to pass. This adds ~50KB to the obmc-phosphor-image-witherspoon.squashfs-xz With change: 20570112 Jan 17 16:03 obmc-phosphor-image-witherspoon-20190117213346.rootfs.squashfs-xz Without change: 20525056 Jan 17 16:12 obmc-phosphor-image-witherspoon-20190117220913.rootfs.squashfs-xz Tested: Verified bmcweb starts fine and responds to redfish requests. Verified the GUI works. No longer see the RedfishServiceValidator error associated with not hosting the metadata. (From meta-ibm rev: 65f3e6f2e936ba2a66dfaa128567189edca1ad20) Change-Id: I9cd68469cde5fac3fc827c6d6201547d98004a8d Signed-off-by: Gunnar Mills <gmills@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-10-18meta-ibm: bmcweb: set version wildcardPatrick Venture1-0/+10
Set version wildcard for bmcweb. (From meta-ibm rev: cc403fd638819840744cd288b95fb9f34ad1f7a2) Change-Id: I1da6441654b64038ff58bccce5d478e46d492cb7 Signed-off-by: Patrick Venture <venture@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>