| /openbmc/docs/designs/ |
| H A D | redfish-resource-supplement-for-pfr.md | 21 represent the PFR provisioning status such as platform firmware is provisioned
22 or not as well as provisioning is locked or not. This also covers the Redfish
44 provisioning status over Redfish.
68 provisioning status.
70 - ProvisiongStatus: The value of this property indicates the provisioning status
77 provisioned but not locked. So re-provisioning is allowed in this state.
80 and locked. So re-provisioning is not allowed in this state.
96 Below type of events should be logged as part of PFR or provisioning. These
200 provisioning status.
|
| H A D | expired-password.md | 185 requires the tech to have access, and requires re-provisioning the account
211 design where the BMC is initially in a provisioning mode which does not allow
213 the BMC (which includes changing its password) before you can leave provisioning
|
| /openbmc/bmcweb/redfish-core/schema/oem/openbmc/json-schema/ |
| H A D | OpenBMCComputerSystem.v1_0_0.json | 8 "description": "Configuration data for platform firmware provisioning.",
33 "description": "This indicates platform firmware provisioning state.",
34 …"longDescription": "The value of this property indicating provisioning status of platform firmware…
53 …sionedAndLocked": "Platform firmware is provisioned and locked. So re-provisioning is not allowed …
54 …utNotLocked": "Platform firmware is provisioned but not locked. So re-provisioning is allowed in t…
|
| /openbmc/bmcweb/redfish-core/schema/oem/openbmc/csdl/ |
| H A D | OpenBMCComputerSystem_v1.xml | 50 …notation Term="OData.Description" String="Configuration data for platform firmware provisioning."/>
53 …Annotation Term="OData.Description" String="This indicates platform firmware provisioning state."/>
54 …"OData.LongDescription" String="The value of this property indicating provisioning status of platf…
64 …ption" String="Platform firmware is provisioned but not locked. So re-provisioning is allowed in t…
68 …scription" String="Platform firmware is provisioned and locked. So re-provisioning is not allowed …
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PFR/ |
| H A D | Attributes.interface.yaml | 17 Indicates the platform firmware provisioning locked state. Once the
18 provisioning is locked, it can't be re-provisioned.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/lvm2/ |
| H A D | lvm2.inc | 44 # NOTE: Add thin-provisioning-tools only if your distro policy allows GPL-3.0 license
45 PACKAGECONFIG[thin-provisioning-tools] = "--with-thin=internal,--with-thin=none,,thin-provisioning-…
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | persistent-data.rst | 13 - Heinz Mauelshagen's thin provisioning target
22 targets. It's currently used by the thin-provisioning target and an
83 thin-provisioning target uses a btree with two levels of nesting.
|
| H A D | thin-provisioning.rst | 2 Thin provisioning
9 between them implement thin-provisioning and snapshots.
51 This section describes some quick recipes for using thin provisioning.
112 thin-pool is created. People primarily interested in thin provisioning
137 means the thin-provisioning target behaves like a physical disk that has
157 Thin provisioning
|
| H A D | era.rst | 114 thin-provisioning-tools project:
116 https://github.com/jthornber/thin-provisioning-tools
|
| H A D | index.rst | 35 thin-provisioning
|
| H A D | dm-clone.rst | 29 The dm-clone target reuses the metadata library used by the thin-provisioning
327 thinly-provisioned volumes. Thin-provisioning has an inherent metadata
331 Moreover, cloning a device shouldn't force the use of thin-provisioning. On
332 the other hand, if we wish to use thin provisioning, we can just use a thin
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-linecard.rst | 32 concept of provisioning is introduced. It allows the user to:
65 * ``provisioning``: Line card slot is currently in a process of being provisioned
67 * ``provisioning_failed``: Provisioning was not successful.
83 | | provisioning |
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Security/ |
| H A D | RestrictionMode.interface.yaml | 24 - name: Provisioning
26 Indicate that system is in provisioning mode and all commands
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/thin-provisioning-tools/ |
| H A D | thin-provisioning-tools_1.0.13.bb | 3 HOMEPAGE = "https://github.com/jthornber/thin-provisioning-tools"
11 git://github.com/jthornber/thin-provisioning-tools;branch=main;protocol=https \
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | cpu-topology.rst | 176 Polarization defines two models of CPU provisioning: horizontal
181 have about equal resource provisioning.
195 different real CPU provisioning:
198 vCPU gets 100% of the real CPU provisioning.
204 vCPU only gets real CPU provisioning when no other vCPUs needs it.
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/marvell/ |
| H A D | octeontx2.rst | 24 again has multiple local functions (LFs) for provisioning to PCI devices.
43 Resource provisioning examples
66 supports resource provisioning and configuration of functional blocks.
71 receiving requests AF does resource provisioning and other HW configuration.
74 DPDK etc. So AF has to handle provisioning/configuration requests sent
|
| /openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | devlink_linecard.sh | 128 log_info "Provisioning linecard $lc"
131 check_err $? "Failed trigger linecard $lc provisioning"
133 state=$(lc_wait_until_state_changes $lc "provisioning" \
|
| /openbmc/linux/drivers/md/persistent-data/ |
| H A D | Kconfig | 9 device-mapper targets such as the thin provisioning target.
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | software-architecture.rst | 110 the provisioning on the first boot, hardware initialization and verification
113 The BL1_2 code, hashes and keys are written into the OTP during the provisioning.
140 - The provisioning bundle that contains the BL1_2 code is located in the ROM.
141 This means the BL1_2 cannot be updated during provisioning time.
|
| /openbmc/qemu/tests/keys/ |
| H A D | README | 3 Some guests require the key to exist prior to provisioning the guest; also,
|
| /openbmc/linux/tools/arch/x86/intel_sdsi/ |
| H A D | Makefile | 2 # Makefile for Intel Software Defined Silicon provisioning tool
|
| /openbmc/linux/net/devlink/ |
| H A D | linecard.c | 302 /* Provisioning failed. Assume the linecard is unprovisioned in devlink_linecard_type_set()
493 * devlink_linecard_provision_set - Set provisioning on linecard
514 * devlink_linecard_provision_clear - Clear provisioning on linecard
533 * devlink_linecard_provision_fail - Fail provisioning on linecard
|
| /openbmc/bmcweb/redfish-core/schema/oem/openbmc/ |
| H A D | meson.build | 5 'redfish-provisioning-feature': 'OpenBMCComputerSystem',
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Schedule.v1_2_5.json | 161 … "description": "The time after provisioning when the schedule as a whole expires.",
162 …operty shall contain a Redfish Duration that describes the time after provisioning when the schedu…
|
| /openbmc/openbmc/meta-openembedded/meta-oe/conf/include/ |
| H A D | non-repro-meta-oe.inc | 96 thin-provisioning-tools-dev \
|