/openbmc/phosphor-objmgr/src/ |
H A D | associations.hpp | 15 * org.openbmc.Associations 16 * @param[in] owner - The Dbus service having its associations 36 * org.openbmc.Associations 48 /** @brief Check and remove any changed associations 50 * Based on the latest values of the org.openbmc.Associations.associations 59 * org.openbmc.Associations 62 * @param[in] newAssociations - New associations to look at for change 75 * Called when either a new org.openbmc.Associations interface was 76 * created, or the associations property on that interface changed 80 * @param[in] associations - New associations to look at for change [all …]
|
H A D | processing.hpp | 3 #include "associations.hpp" 11 /** @brief The associations definitions interface */ 15 /** @brief The associations definitions property name */ 16 constexpr const char* assocDefsProperty = "Associations"; 22 * pair2: D-bus Method,vector[Associations]
|
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/sensors/phosphor-virtual-sensor/ |
H A D | virtual_sensor_config.json | 7 "Associations": [ array 39 "Associations": [ array 71 "Associations": [ array 103 "Associations": [ array 135 "Associations": [ array 167 "Associations": [ array 199 "Associations": [ array 231 "Associations": [ array 263 "Associations": [ array 295 "Associations": [ array [all …]
|
/openbmc/phosphor-dbus-interfaces/ |
H A D | requirements.md | 51 ## Associations section in Requirements and Expectations for dbus interfaces 53 There are typically two types of associations we use: 55 - Peer associations. 56 - Directed associations. 58 Peer associations are rare, but are used to link a single entity that is 62 Directed associations are more common and are used to show a relationship 64 associations should be considered to have a "primary" and "secondary" end, which 69 ### Peer associations should be named with hierarchy names 82 ### Directed associations should not codify type 90 ### Directed associations should be named with participle verbs [all …]
|
/openbmc/phosphor-inventory-manager/ |
H A D | association_manager.hpp | 19 namespace associations namespace 42 * @brief This class provides the ability to add org.openbmc.Associations 77 * @param[in] jsonPath - path to the JSON File that contains associations 92 * the JSON associations definition for the object path passed 97 * @param[in] objectPath - the D-Bus object path to check for associations 126 * before an associations file is valid. 140 * If it is valid, it will load the associations pointed to 161 * If it is valid, it will load the associations pointed to 174 * @param[in] json - The associations JSON 179 * @brief Creates an instance of an org.openbmc.Associations [all …]
|
H A D | README.md | 133 ## Creating Associations 135 PIM can create [associations][1] between inventory items and other D-Bus 139 `--enable-associations` configure option. It defaults to disabled. 141 To use this, the associations to create should be defined in a JSON file which 143 to `/usr/share/phosphor-inventory-manager/associations.json`. This file is 206 In the case where different systems that require different associations reside 208 in the same directory as the default associations file would go, but it does not 212 list of values, then the condition is met and those associations are activated. 214 If a file with a conditions section is found, then the default associations file 215 is ignored. The end result is that associations are only ever loaded from one [all …]
|
H A D | association_manager.cpp | 14 namespace associations namespace 21 // If there aren't any conditional associations files, look for in Manager() 69 "Invalid JSON in associations condition entry in {PATH}. Skipping file.", in loadConditions() 177 load(json["associations"]); in conditionMatch() 206 load(json["associations"]); in conditionMatch() 298 a->associations(std::move(prop)); in createAssociation() 308 auto prop = object->second->associations(); in createAssociation() 310 object->second->associations(std::move(prop), deferSignal); in createAssociation() 313 } // namespace associations
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/sensors/phosphor-virtual-sensor/sbp1/ |
H A D | virtual_sensor_config.json | 7 "Associations": [ array 37 "Associations": [ array 73 "Associations": [ array 109 "Associations": [ array 145 "Associations": [ array 181 "Associations": [ array 211 "Associations": [ array 248 "Associations": [ array 278 "Associations": [ array 315 "Associations": [ array [all …]
|
/openbmc/entity-manager/docs/ |
H A D | associations.md | 1 # Associations chapter 3 Entity Manager will create [associations][1] between entities in certain cases. 10 contained_by upstream' associations for the connected entities. 44 'Subchassis contained_by Superchassis` associations, putting the associations 49 In addition to the `containing` associations, entity-manager will add 50 `powering`/`powered_by` associations between a power supply and its parent when 89 https://github.com/openbmc/docs/blob/master/architecture/object-mapper.md#associations
|
/openbmc/phosphor-logging/ |
H A D | elog_serialize.cpp | 35 e.associations(), e.resolved(), e.version(), e.updateTimestamp(), in save() 57 AssociationList associations{}; in load() local 66 a(id, severity, timestamp, message, additionalData_old, associations, in load() 74 a(id, severity, timestamp, message, additionalData_old, associations, in load() 82 a(id, severity, timestamp, message, additionalData_old, associations, in load() 89 a(id, severity, timestamp, message, additionalData_old, associations, in load() 97 a(id, severity, timestamp, message, additionalData_old, associations, in load() 103 a(id, severity, timestamp, message, additionalData, associations, in load() 115 e.associations(associations, true); in load() 163 // possibly associations ??. But handling it here for in deserialize()
|
/openbmc/openbmc/meta-bytedance/meta-g220a/recipes-phosphor/sensors/phosphor-virtual-sensor/ |
H A D | virtual_sensor_config.json | 8 "Associations": array 46 "Associations": array 84 "Associations": array 122 "Associations": array 168 "Associations": array 219 "Associations": array 262 "Associations": array 305 "Associations": array 356 "Associations": array
|
/openbmc/phosphor-psu-code-mgmt/src/ |
H A D | item_updater.cpp | 120 AssociationList associations; in onVersionInterfacesAdded() local 123 associations.emplace_back(std::make_tuple( in onVersionInterfacesAdded() 134 activationState, associations, filePath); in onVersionInterfacesAdded() 176 associations(assocs); in createActiveAssociation() 183 associations(assocs); in addFunctionalAssociation() 190 associations(assocs); in addUpdateableAssociation() 200 associations(assocs); in removeAssociation() 216 utils::isAssociated(psuInventoryPath, it->second->associations())) in onUpdateDone() 255 auto associations = it->second->associations(); in createPsuObject() local 256 associations.emplace_back( in createPsuObject() [all …]
|
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/inventory/ |
H A D | phosphor-inventory-manager_%.bbappend | 2 PACKAGECONFIG:append:gbs = " associations" 3 SRC_URI:append:gbs = " file://associations.json" 8 install -m 0755 ${UNPACKDIR}/associations.json ${D}${base_datadir}/associations.json
|
/openbmc/docs/designs/ |
H A D | physical-topology.md | 21 specifies using Associations for all relationships (Proposal II) rather than 27 Changes to phosphor-dbus-interfaces documenting new Associations have been 73 Associations, so no changes are needed here. 83 New code in entity-manager matches these properties and exposes associations on 126 choose to include the same Associations that phosphor-inventory-manager and 165 associations to communicate topology, but this significantly increases the 169 Associations are the only approach that fits all use cases, so we should start 174 dedicated tool to query for Associations of a specific type and present a 187 associations, then their output such as Redfish will not change either.
|
/openbmc/openbmc/meta-quanta/meta-olympus-nuvoton/recipes-phosphor/inventory/ |
H A D | phosphor-inventory-manager_%.bbappend | 2 PACKAGECONFIG:append:olympus-nuvoton = " associations" 3 SRC_URI:append:olympus-nuvoton = " file://associations.json" 9 install -m 0755 ${UNPACKDIR}/associations.json ${D}${base_datadir}/associations.json
|
/openbmc/phosphor-psu-code-mgmt/test/ |
H A D | test_activation.cpp | 84 AssociationList associations; member in TestActivation 90 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 98 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 111 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 121 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 142 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 171 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 223 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 255 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() 271 mockedBus, dBusPath, versionId, extVersion, status, associations, in TEST_F() [all …]
|
/openbmc/phosphor-objmgr/src/test/ |
H A D | associations.cpp | 1 #include "src/associations.hpp" 106 // Verify no associations or endpoints removed when the change is identical 173 std::vector<Association> associations = { in TEST_F() local 182 associationChanged(io, *server, associations, defaultSourcePath, in TEST_F() 198 std::vector<Association> associations = { in TEST_F() local 210 associationChanged(io, *server, associations, "/new/source/path", in TEST_F() 233 std::vector<Association> associations = { in TEST_F() local 244 associationChanged(io, *server, associations, defaultSourcePath, in TEST_F() 247 // New associations so ensure it now contains a single entry in TEST_F() 269 std::vector<Association> associations = { in TEST_F() local [all …]
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/inventory/ |
H A D | phosphor-inventory-manager_%.bbappend | 2 PACKAGECONFIG:append:ibm-ac-server = " associations" 3 SRC_URI:append:ibm-ac-server = " file://associations.json" 6 PACKAGECONFIG:append:p10bmc = " associations" 19 install -m 0755 ${UNPACKDIR}/associations.json ${D}${base_datadir}/associations.json
|
/openbmc/phosphor-power/phosphor-power-supply/ |
H A D | util.hpp | 140 AssociationsProperty associations; in handleChassisHealthRollup() local 143 associations); in handleChassisHealthRollup() 148 auto assocIt = std::find(associations.begin(), associations.end(), in handleChassisHealthRollup() 152 if (assocIt != associations.end()) in handleChassisHealthRollup() 158 associations.push_back(critAssociation); in handleChassisHealthRollup() 162 if (assocIt == associations.end()) in handleChassisHealthRollup() 180 associations.erase(assocIt); in handleChassisHealthRollup() 185 associations); in handleChassisHealthRollup() 191 "associations for {}: {}", in handleChassisHealthRollup()
|
/openbmc/openbmc-test-automation/redfish/systems/eventlog/ |
H A D | test_event_association.robot | 55 Create Test Error Callout And Verify Associations 56 [Documentation] Create test error callout and verify Associations. 60 # "Associations": [ 71 List Should Contain Value ${resp.json()["data"]["Associations"][0]} callout 72 List Should Contain Value ${resp.json()["data"]["Associations"][0]} fault 74 ... ${resp.json()["data"]["Associations"][0]} 94 # "Associations": [ 131 # "Associations": [ 155 # "Associations": [ 203 Should Contain ${resp.json()["data"]["Associations"][0]} callout [all …]
|
/openbmc/phosphor-logging/test/ |
H A D | elog_quiesce_test.cpp | 46 phosphor::logging::AssociationList associations{}; in TEST_F() local 55 std::move(associations), in TEST_F() 74 phosphor::logging::AssociationList associations{}; in TEST_F() local 83 std::move(associations), in TEST_F() 102 phosphor::logging::AssociationList associations{}; in TEST_F() local 122 std::move(associations), in TEST_F() 159 phosphor::logging::AssociationList associations{}; in TEST_F() local 179 std::move(associations), in TEST_F() 218 phosphor::logging::AssociationList associations{}; in TEST_F() local 238 std::move(associations), in TEST_F()
|
/openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/sensors/phosphor-virtual-sensor/ |
H A D | virtual_sensor_config.json | 17 "Associations": array 63 "Associations": array 105 "Associations": array 143 "Associations": array 181 "Associations": array
|
/openbmc/openpower-pnor-code-mgmt/ |
H A D | item_updater.cpp | 94 AssociationList associations = {}; in createActivation() local 99 associations.emplace_back(std::make_tuple( in createActivation() 114 path, versionId, extendedVersion, activationState, associations); in createActivation() 128 associations(assocs); in createActiveAssociation() 135 associations(assocs); in createUpdateableAssociation() 141 // remove all functional associations in updateFunctionalAssociation() 155 associations(assocs); in updateFunctionalAssociation() 165 associations(assocs); in removeAssociation()
|
/openbmc/openbmc/meta-fii/meta-kudo/recipes-phosphor/sensors/phosphor-virtual-sensor/ |
H A D | virtual_sensor_config.json | 14 "Associations":[ array 58 "Associations":[ array 143 "Associations":[ array 186 "Associations":[ array 229 "Associations":[ array 274 "Associations":[ array
|
/openbmc/openbmc/meta-ampere/meta-mitchell/recipes-phosphor/inventory/ |
H A D | phosphor-inventory-manager_%.bbappend | 2 PACKAGECONFIG:append = " associations" 3 SRC_URI:append = " file://associations.json" 7 install -m 0755 ${UNPACKDIR}/associations.json ${D}${base_datadir}
|