bmcweb: Remove associations between cpu and core

Remove associations as it is causing issues with the
way external storer handles the error metrics.
Detailed explanation can be found in go/gbmccl/127347.

This change updates all the affected patches

Tested:

Verified that the core and thread URIs.
Verified that efficient expand works
Verified that Processor Metrics URIs work

```

wget -qO- 'http://localhost:80/redfish/v1/Systems/system/Processors/cpu0/SubProcessors'
{
  "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors",
  "@odata.type": "#ProcessorCollection.ProcessorCollection",
  "Members": [
    {
    "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core0"
    },
    {
      "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core1"
    },
    ....,
    ....,
    {
      "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/coreX"
    }
  ],
  "Members@odata.count": ..,
  "Name": "SubProcessor Collection"
}

wget -qO- 'http://localhost:80/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3'
{
  "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3",
  "@odata.type": "#Processor.v1_11_0.Processor",
  "Id": "core3",
  "Name": "SubProcessor",
  "ProcessorId": {
    "MicrocodeInfo": "...."
  },
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  },
  "SubProcessors": {
    "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3/SubProcessors"
  }
}

wget -qO- 'http://localhost:80/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3/SubProcessors'
{
  "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3/SubProcessors",
  "@odata.type": "#ProcessorCollection.ProcessorCollection",
  "Members": [
    {
      "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3/SubProcessors/thread0"
    },
    {
      "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3/SubProcessors/thread1"
    },
    ......,
    .......
  ],
  "Members@odata.count": ..,
  "Name": "SubProcessor Collection"
}

wget -qO- 'http://localhost:80/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3/SubProcssors/thread1'
{
  "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0/SubProcessors/core3/SubProcessors/thread1",
  "@odata.type": "#Processor.v1_11_0.Processor",
  "Id": "thread1",
  "Name": "SubProcessor",
  "ProcessorId": {
    "MicrocodeInfo": "......"
  },
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}

```

Google-Bug-Id: 268565156
Change-Id: I36c9d20683edc5003396844975ea6201ed17baee
Signed-off-by: Nikhil Namjoshi <nikhilnamjoshi@google.com>
4 files changed
tree: 75513dd052c74796329168e0344b55b4241da4ac
  1. conf/
  2. dynamic-layers/
  3. meta-nuvoton-npcm8xx/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-google/
  7. recipes-kernel/
  8. recipes-phosphor/
  9. LICENSE
  10. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.