styhead: update WORKDIR usage

The latest yocto release(styhead,5.1) has made a significant change[1]
to the use of the WORKDIR parameter.

This is not the complete change required but gets us going

styhead: update WORKDIR usage

The latest yocto release(styhead,5.1) has made a significant change[1]
to the use of the WORKDIR parameter.

This is not the complete change required but gets us going in the right
direction.

[1]: https://docs.yoctoproject.org/next/migration-guides/migration-5.1.html#workdir-changes

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4f184b361be69e7704a0657a4a00cdad981aff8a

show more ...

meta-phosphor: settingsd: add BMC template variable

phosphor-settingsd has a variable for creating "host" templates,
which are a handy way of organizing (and generating per host) the
settingsd varia

meta-phosphor: settingsd: add BMC template variable

phosphor-settingsd has a variable for creating "host" templates,
which are a handy way of organizing (and generating per host) the
settingsd variables. Add a similar mechanism for "BMC" templates,
which could also be used for "whole system" settings. This allows
better organization of the override files.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I435c6d62414874b8e920af8ca346f519e4819a45

show more ...

Run oe-stylize on our files

In all of our recipes, we should be following yoctos lead on formatting,
order, and other things, for consistency in our meta layers.

This commit runs oe-stylize.py on a

Run oe-stylize on our files

In all of our recipes, we should be following yoctos lead on formatting,
order, and other things, for consistency in our meta layers.

This commit runs oe-stylize.py on all of our files. The types of
changes being made can be seen in the commit, but amount to:

1. Setting an explicit key ordering
2. Sectioning the files appropriately
3. Applying rules checking to our files

At some point in the near future, we would turn this on as part of
repotest, but some minor changes need to be upstreamed to meta-oe (WIP)
to make that happen.

Looking for input on whether this is something we'd like to do, and
whether the diffs below look reasonable to folks.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I489dd21d38a9fe4f3ece89cc7a5e1d0463224abf

show more ...

phosphor-settings-defaults: fix silent failures in install

If a file is missing from SETTINGS_HOST_TEMPLATES, the
previous `do_install` would silently fail because bash
by default does not use the `

phosphor-settings-defaults: fix silent failures in install

If a file is missing from SETTINGS_HOST_TEMPLATES, the
previous `do_install` would silently fail because bash
by default does not use the `pipefail` option. Avoid the pipe
operation so failures are more obvious:

```
| sed: can't read restrictionmode-host-settings.override.yml: No such file or directory
| WARNING: .../lf-build-bletchley/tmp/work/x86_64-linux/phosphor-settings-defaults-native/1.0-r1/temp/run.do_install.800503:152 exit 2 from 'sed "s/{}/${i}/g" ${f} >> ${DEST}/defaults.yaml'
```

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: If35ca6cbf1c1793229432cb680e6fc0148f721a2

show more ...

phosphor-settings-defaults: allow additonal host templates

Previously we supported a single default per-host template, which
enables default settings for multi-host designs. Add a variable,
SETTING

phosphor-settings-defaults: allow additonal host templates

Previously we supported a single default per-host template, which
enables default settings for multi-host designs. Add a variable,
SETTINGS_HOST_TEMPLATES, which allows machines to add their own template
snippets.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1e416e2af8b336017c800676efd0183f294168a9

show more ...

phosphor-settings-defaults: refactor defaults settings for multihost support

separate host items from defaults.yaml to host-template.yaml
add host items to defaults.yaml based on OBMC_HOST_INSTANCES

phosphor-settings-defaults: refactor defaults settings for multihost support

separate host items from defaults.yaml to host-template.yaml
add host items to defaults.yaml based on OBMC_HOST_INSTANCES to support multi-host.

TESTED:
a. build with default OBMC_HOST_INSTANCES="0"

`busctl tree xyz.openbmc_project.Settings`
└─/xyz
└─/xyz/openbmc_project
├─/xyz/openbmc_project/control
│ ├─/xyz/openbmc_project/control/host0
│ │ ├─/xyz/openbmc_project/control/host0/TPMEnable
│ │ ├─/xyz/openbmc_project/control/host0/auto_reboot
│ │ │ └─/xyz/openbmc_project/control/host0/auto_reboot/one_time
│ │ ├─/xyz/openbmc_project/control/host0/boot
│ │ │ └─/xyz/openbmc_project/control/host0/boot/one_time
│ │ ├─/xyz/openbmc_project/control/host0/power_cap
│ │ ├─/xyz/openbmc_project/control/host0/power_restore_policy
│ │ │ └─/xyz/openbmc_project/control/host0/power_restore_policy/one_time
│ │ ├─/xyz/openbmc_project/control/host0/restriction_mode
│ │ └─/xyz/openbmc_project/control/host0/turbo_allowed
│ ├─/xyz/openbmc_project/control/minimum_ship_level_required
│ ├─/xyz/openbmc_project/control/power_supply_attributes
│ └─/xyz/openbmc_project/control/power_supply_redundancy
├─/xyz/openbmc_project/logging
│ ├─/xyz/openbmc_project/logging/rest_api_logs
│ └─/xyz/openbmc_project/logging/settings
├─/xyz/openbmc_project/network
│ └─/xyz/openbmc_project/network/host0
│ └─/xyz/openbmc_project/network/host0/intf
│ └─/xyz/openbmc_project/network/host0/intf/addr
├─/xyz/openbmc_project/software
│ └─/xyz/openbmc_project/software/apply_time
└─/xyz/openbmc_project/time
└─/xyz/openbmc_project/time/sync_method

b. build with Bletchley platform: OBMC_HOST_INSTANCES = "1 2 3 4 5 6"
`busctl tree xyz.openbmc_project.Settings`
└─/xyz
└─/xyz/openbmc_project
├─/xyz/openbmc_project/control
│ ├─/xyz/openbmc_project/control/host1
│ │ ├─/xyz/openbmc_project/control/host1/TPMEnable
│ │ ├─/xyz/openbmc_project/control/host1/auto_reboot
│ │ │ └─/xyz/openbmc_project/control/host1/auto_reboot/one_time
│ │ ├─/xyz/openbmc_project/control/host1/boot
│ │ │ └─/xyz/openbmc_project/control/host1/boot/one_time
│ │ ├─/xyz/openbmc_project/control/host1/power_cap
│ │ ├─/xyz/openbmc_project/control/host1/power_restore_policy
│ │ │ └─/xyz/openbmc_project/control/host1/power_restore_policy/one_time
│ │ ├─/xyz/openbmc_project/control/host1/restriction_mode
│ │ └─/xyz/openbmc_project/control/host1/turbo_allowed
│ ├─/xyz/openbmc_project/control/host2
│ │ ├─/xyz/openbmc_project/control/host2/TPMEnable
│ │ ├─/xyz/openbmc_project/control/host2/auto_reboot
│ │ │ └─/xyz/openbmc_project/control/host2/auto_reboot/one_time
│ │ ├─/xyz/openbmc_project/control/host2/boot
│ │ │ └─/xyz/openbmc_project/control/host2/boot/one_time
│ │ ├─/xyz/openbmc_project/control/host2/power_cap
│ │ ├─/xyz/openbmc_project/control/host2/power_restore_policy
│ │ │ └─/xyz/openbmc_project/control/host2/power_restore_policy/one_time
│ │ ├─/xyz/openbmc_project/control/host2/restriction_mode
│ │ └─/xyz/openbmc_project/control/host2/turbo_allowed
│ ├─/xyz/openbmc_project/control/host3
(.......repeat util host6)
│ ├─/xyz/openbmc_project/control/minimum_ship_level_required
│ ├─/xyz/openbmc_project/control/power_supply_attributes
│ └─/xyz/openbmc_project/control/power_supply_redundancy
├─/xyz/openbmc_project/logging
│ ├─/xyz/openbmc_project/logging/rest_api_logs
│ └─/xyz/openbmc_project/logging/settings
├─/xyz/openbmc_project/network
│ ├─/xyz/openbmc_project/network/host1
│ │ └─/xyz/openbmc_project/network/host1/intf
│ │ └─/xyz/openbmc_project/network/host1/intf/addr
│ ├─/xyz/openbmc_project/network/host2
│ │ └─/xyz/openbmc_project/network/host2/intf
│ │ └─/xyz/openbmc_project/network/host2/intf/addr
│ ├─/xyz/openbmc_project/network/host3
│ │ └─/xyz/openbmc_project/network/host3/intf
│ │ └─/xyz/openbmc_project/network/host3/intf/addr
│ ├─/xyz/openbmc_project/network/host4
│ │ └─/xyz/openbmc_project/network/host4/intf
│ │ └─/xyz/openbmc_project/network/host4/intf/addr
│ ├─/xyz/openbmc_project/network/host5
│ │ └─/xyz/openbmc_project/network/host5/intf
│ │ └─/xyz/openbmc_project/network/host5/intf/addr
│ └─/xyz/openbmc_project/network/host6
│ └─/xyz/openbmc_project/network/host6/intf
│ └─/xyz/openbmc_project/network/host6/intf/addr
├─/xyz/openbmc_project/software
│ └─/xyz/openbmc_project/software/apply_time
└─/xyz/openbmc_project/time
└─/xyz/openbmc_project/time/sync_method

Change-Id: I4b70fb7e19647ea2ba5c985cb7c6bf851cb971b2
Signed-off-by: Allen.Wang <Allen_Wang@quantatw.com>

show more ...

native class is not inherited last

Moved "inherit native" statements to the last position to remove QA Issues.
The message is: WARNING: QA Issue: {RECIPENAME}: native/nativesdk class is not
inherite

native class is not inherited last

Moved "inherit native" statements to the last position to remove QA Issues.
The message is: WARNING: QA Issue: {RECIPENAME}: native/nativesdk class is not
inherited last, this can result in unexpected behaviour. Classes inherited
after native/nativesdk: {CLASSFILES} [native-last]

Tested: The witherspoon image builds without the warnings.

Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
Change-Id: Ic3c71234abfcac8b26478bc32808e3bec8bba810

show more ...

meta-phosphor: Remove references to PHOSPHORBASE

PHOSPHORBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto con

meta-phosphor: Remove references to PHOSPHORBASE

PHOSPHORBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.

(From meta-phosphor rev: a1cee09419cb1467c3d2b7bf996b40089f0d06f4)

Change-Id: If136d24638a8022671988cf0a01620e7fffc545f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

show more ...

meta-phosphor: master refresh 3026b0fa5a..d76a657a63

Update meta-phosphor to master HEAD.

Patrick Venture (52):
meta-phosphor: obmc-console: set LICENSE field
meta-phosphor: dbus-interf

meta-phosphor: master refresh 3026b0fa5a..d76a657a63

Update meta-phosphor to master HEAD.

Patrick Venture (52):
meta-phosphor: obmc-console: set LICENSE field
meta-phosphor: dbus-interfaces: set LICENSE field
meta-phosphor: rest-dbus: set LICENSE field
meta-phosphor: slpd-lite: set LICENSE field
meta-phosphor: ipmi-host: set LICENSE field
meta-phosphor: ipmi-net: set LICENSE field
meta-phosphor: network: inarp: set LICENSE field
meta-phosphor: network: set LICENSE field
meta-phosphor: logging: set LICENSE field
meta-phosphor: ipmi-tool: fixup LICENSE
meta-phosphor: clear-once: set LICENSE field
meta-phosphor: preinit-mounts: set LICENSE field
meta-phosphor: systemd: obmc-targets: set LICENSE field
meta-phosphor: dbus: perms: set LICENSE field
meta-phosphor: dbus-interfaces-mapper-config-native: set LICENSE field
meta-phosphor: dbus-monitor-config-native: set LICENSE field
meta-phosphor: legacy-namespace-mapper-config-native: set LICENSE field
meta-phosphor: mapper-config-native: set LICENSE field
meta-phosphor: obmc-host-failure-reboots: set LICENSE field
meta-phosphor: fan-control-events-config-native: set LICENSE field
meta-phosphor: fan-control-fan-config-native: set LICENSE field
meta-phosphor: fan-control-zone-conditions-config-native: set LICENSE field
meta-phosphor: fan-control-zone-config-native: set LICENSE field
meta-phosphor: fan-monitor-config-native: set LICENSE field
meta-phosphor: fan-presence-config-native: set LICENSE field
meta-phosphor: image-signing: set LICENSE field
meta-phosphor: insecure-signing-key-native: set LICENSE field
meta-phosphor: inventory-manager-assettag-native: set LICENSE field
meta-phosphor: inventory-manager-config-native: set LICENSE field
meta-phosphor: ipmi-channel-inventory-native: set LICENSE field
meta-phosphor: ipmi-config: set LICENSE field
meta-phosphor: ipmi-fru-merge-config-native: set LICENSE field
meta-phosphor: ipmi-fru-properties-native: set LICENSE field
meta-phosphor: ipmi-fru-read-bmc-inventory-native: set LICENSE field
meta-phosphor: ipmi-fru-read-not-sent-by-host-inventory-native: set LICENSE field
meta-phosphor: ipmi-fru-whitelist-native: set LICENSE field
meta-phosphor: ipmi-inventory-sel-native: set LICENSE field
meta-phosphor: ipmi-sensor-config-native: set LICENSE field
meta-phosphor: ipmi-sensor-inventory-native: set LICENSE field
meta-phosphor: logging-callouts-example-native: set LICENSE field
meta-phosphor: logging-error-logs-native: set LICENSE field
meta-phosphor: settings-defaults-native: set LICENSE field
meta-phosphor: fan-presence-mrw-native: set LICENSE field
meta-phosphor: fan-control-fan-config-mrw-native: set LICENSE field
meta-phosphor: ipmi-fru-properties-mrw-native: set LICENSE field
meta-phosphor: ipmi-inventory-sel-mrw-native: set LICENSE field
meta-phosphor: ipmi-sensor-inventory-mrw-config-native: set LICENSE field
meta-phosphor: ipmi-sensor-inventory-mrw-native: set LICENSE field
meta-phosphor: led-manager-config-mrw-native: set LICENSE field
meta-phosphor: logging-callouts-mrw-native: set LICENSE field
meta-phosphor: hwmon-config-mrw: set LICENSE field
meta-phosphor: settings-read-settings-mrw-native: set LICENSE field

Change-Id: Ibe919c3f1a748fae67b45ff6908a236b08902450
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

show more ...

meta-phosphor: Move layer content from common/

Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this

meta-phosphor: Move layer content from common/

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>

show more ...