| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Package app phosphor-ldap-conf. This app implements an API to update
the LDAP config file i.e /etc/nslcd.conf.
This commit also creates a file:/etc/nslcd.conf.default, which is to
be restored as /etc/nslcd.conf when we disable LDAP configuration.
(From meta-phosphor rev: 6d7f640d702b5853268bec58e8529516e7884493)
Change-Id: I7183652732c2200b5cc0a644ddb179c8784eb0fb
Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update meta-phosphor to master HEAD.
Adriana Kobylak (2):
rsyslog-policy: Add rsyslog-override.conf
Move remote logging features to their own category
Brad Bishop (2):
phosphor: rsyslog: remove obmc-phosphor-license
phosphor: mrw-api: fetch all of serverwiz
Change-Id: Ic342bda5d19272b2806f65c7082189d4a79c69d8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Dbus-broker is an alternative implementation of the dbus-daemon that is
oriented around reducing abnormal conditions, and increasing the
performance of the dbus daemon process.
In practice, this seems to make a world of difference in performance. A
testing of a smattering of user facing interfaces shows improvements
across the board:
1. 7 second improvement in boot time to BMC Ready change.
2. Dbus based ipmi sensor reading implementation gains a 120% speedup
(20 seconds down to 8)
3. Redfish thermal schema goes from 550ms time to first byte, to 400ms
time to first byte.
Negatives as they apply to OpenBMC
1. Debug: dbus-broker loses the ability to directly implement DBus over
TCP. To my knowlege very few people use this for anything other than
debug, and even for debug, its usefulness is limited. It's very likely
that an implementation of socat could bridge this gap.
2. Support. Very few other linux implementations have moved to dbus
broker, so there is the possibility that we will find a critical flaw or
bug that others haven't hit get. This seems relatively unlikely, given
the widespread usage of this project already.
Tested By: Booting system, and testing a variety of user facing
interfaces. No issues found.
Requires Williams patch cherry picked ontop of oe-core:
http://cgit.openembedded.org/meta-openembedded/commit/meta-oe/recipes-core/dbus/dbus-broker_git.bb?id=e4baf298cd658b37fd90134dc54a92c75fd117d9
(From meta-phosphor rev: 72615f5614abba33a14d68afdb9010c93f3a1ea3)
Change-Id: Iabac84c93253aa96c7735db4f1e0755d37e6c3db
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bringing the LDAP authentication module support in openbmc stack
requires to pull the nss-pam-ldapd which allows the LDAP
server to provide the user, passwd, group info that we normally get
from the /etc flat files.
nss-pam-ldapd provides libnss-ldap and pam_ldap module which
delegate the work to the nslcd(daemon) that queries the LDAP server.
pam_ldap uses the openldap client API to interact with the LDAP server.
nss-pam-ldapd files are pulled from
http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/
tree/recipes-support/nss-pam-ldapd
meta-cloud-services sha: 38cc19fb3a813673051de314aafabda0545d8466
Tested: Adding the "ldap" distro feature brings the nss-pam-ldapd
and its dependencies into the image and removing the "ldap" from the
distro feature doesn't bring the nss-pam-ldapd and its dependencies.
(From meta-phosphor rev: 4835bb3901a4bff777a97d4f363e3a731b87f21c)
Change-Id: Ifa5da20e7ac47b0c9d9af305ae621252e6d765f3
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
| |
This class is on its way to being deprecated, and oe-core packagegroups
don't have a LICENSE specified in the recipe. Adopt the same semantics
for meta-phosphor.
(From meta-phosphor rev: 72c0635ff972e51d502c43ae7de6e775a6bb5aa0)
Change-Id: I601ae5c5618cd098459baebbd5109972b52385e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was used a long while back for a console but it's
now only used for occasional debug.
Tested: Verified QEMU booted to ready state and screen
tool not in image. Verfied it is now in debug tarball.
(From meta-phosphor rev: 773ad6892bcfc42fa9902af5e6f97e02a4993310)
Change-Id: Ib1b9bae89fe0253fdc2ea173f6b0c0842d40d005
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Package app phosphor-rsyslog-conf. This app implements an API to update
the rsyslog config.
(From meta-phosphor rev: f99f3c8b4e3b364b0d1afacc144a31cccb8772da)
Change-Id: I06b68329d258782bba52a93f4f6431ba94783e53
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The intent is to use rsyslog for streaming journal logs off of the BMC.
Since this is the only intent (i.e at the moment there's no requirement
to employ rsyslog for local logging), modify rsyslog.conf accordingly.
(From meta-phosphor rev: a549e7540ede46686c5011ac2f7209704643a2d6)
Change-Id: I01d7dbd648da82536085f7586efcd7f1c7dd8ae0
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.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>
|