Skip to content

Conversation

@souvik1914581
Copy link
Contributor

@souvik1914581 souvik1914581 commented Apr 11, 2025

The commit publishes Location code under PCIeDevice schema.

Validator was executed and no new error was found.

Test:
curl -k -H "X-Auth-Token: $bmc_token" -X GET "https://${BMC_IP}/redfish/v1/Systems/system/PCIeDevices/chassis_motherboard_pcieslot0_pcie_card0" {
"@odata.id": "/redfish/v1/Systems/system/PCIeDevices/chassis_motherboard_pcieslot0_pcie_card0",
"@odata.type": "#PCIeDevice.v1_9_0.PCIeDevice",
"Id": "chassis_motherboard_pcieslot0_pcie_card0",
"Oem": {
"IBM": {
"@odata.type": "#IBMPCIeDevice.v1_0_0.IBM",
"LinkReset": false
}
},
"PCIeFunctions": {
"@odata.id": "/redfish/v1/Systems/system/PCIeDevices/chassis_motherboard_pcieslot0_pcie_card0/PCIeFunctions"
},
"PCIeInterface": {
"LanesInUse": null
},
"Slot": {
"Location": {
"PartLocation": {
"ServiceLabel": "U78DA.ND0.WZS003T-P0-C0"
}
},
"SlotType": "FullLength"
},
"Status": {
"Health": "OK",
"State": "Enabled"
}
}

Change-Id: Iba1b98734fdfee43c2995f6c9f1f2660e196814a

@souvik1914581 souvik1914581 marked this pull request as draft April 11, 2025 04:41
@souvik1914581 souvik1914581 force-pushed the sr_publichLocationPcieDeviceSchema branch 2 times, most recently from 75a5c5b to 428a4df Compare April 11, 2025 08:36
@souvik1914581
Copy link
Contributor Author

Original commit : 8e7bf1f

@souvik1914581 souvik1914581 force-pushed the sr_publichLocationPcieDeviceSchema branch from 428a4df to 4aa3ba9 Compare April 11, 2025 09:25
@souvik1914581 souvik1914581 marked this pull request as ready for review April 11, 2025 16:29
@baemyung
Copy link
Contributor

PrettyName and Location are different.

So, please make separate PRs;

@baemyung baemyung requested a review from deepakala-k April 11, 2025 18:04
@souvik1914581 souvik1914581 force-pushed the sr_publichLocationPcieDeviceSchema branch from 4aa3ba9 to a3ef5ee Compare April 14, 2025 04:22
@souvik1914581 souvik1914581 marked this pull request as draft April 14, 2025 04:22
@souvik1914581 souvik1914581 changed the title Publish Location & Name under PCIeDevice schema (#1083) Publish Location under PCIeDevice schema (#1083) Apr 14, 2025
@souvik1914581 souvik1914581 changed the title Publish Location under PCIeDevice schema (#1083) Publish Location code under PCIeDevice schema (#1083) Apr 14, 2025
@souvik1914581
Copy link
Contributor Author

PrettyName and Location are different.
So, please make separate PRs;

one PR would be to do PrettyName for pcie.hpp (in addition to #1201). - fyi: @deepakala-k
Another PR for Location code.

@baemyung Can you please tell me why we need to put PrettyName and Location code into separate PRs? If we split the original commit up into two PRs (two commits), we would have to track two commits for any future rebase.

@baemyung
Copy link
Contributor

PrettyName and Location are different.
So, please make separate PRs;
one PR would be to do PrettyName for pcie.hpp (in addition to #1201). - fyi: @deepakala-k
Another PR for Location code.

@baemyung Can you please tell me why we need to put PrettyName and Location code into separate PRs? If we split the original commit up into two PRs (two commits), we would have to track two commits for any future rebase.

They are not related.
It is better to make the different one in separate commits.

In fact, PrettyName part is a bugfix (e.g. missing piece) of PR #1201. So, this part is better to be separate.
(Consider the future rebase situation.
Those commits/PRs [#1201 & bugfix] would be combined into one commit , not with LocationCode part)

@souvik1914581 souvik1914581 force-pushed the sr_publichLocationPcieDeviceSchema branch from a3ef5ee to cdd6cc4 Compare April 16, 2025 06:02
Copy link
Contributor

@baemyung baemyung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@souvik1914581 souvik1914581 marked this pull request as ready for review April 17, 2025 07:37
@souvik1914581 souvik1914581 force-pushed the sr_publichLocationPcieDeviceSchema branch 2 times, most recently from c8744f4 to dde2c22 Compare April 21, 2025 18:24
The commit publishes Location code under PCIeDevice schema.

Validator was executed and no new error was found.

Test:
curl -k -H "X-Auth-Token: $bmc_token" -X GET "https://${BMC_IP}/redfish/
v1/Systems/system/PCIeDevices/chassis_motherboard_pcieslot0_pcie_card0"
{
  "@odata.id": "/redfish/v1/Systems/system/PCIeDevices/
   chassis_motherboard_pcieslot0_pcie_card0",
  "@odata.type": "#PCIeDevice.v1_9_0.PCIeDevice",
  "Id": "chassis_motherboard_pcieslot0_pcie_card0",
  "Oem": {
    "IBM": {
      "@odata.type": "#IBMPCIeDevice.v1_0_0.IBM",
      "LinkReset": false
    }
  },
  "PCIeFunctions": {
    "@odata.id": "/redfish/v1/Systems/system/PCIeDevices/
    chassis_motherboard_pcieslot0_pcie_card0/PCIeFunctions"
  },
  "PCIeInterface": {
    "LanesInUse": null
  },
  "Slot": {
    "Location": {
      "PartLocation": {
        "ServiceLabel": "U78DA.ND0.WZS003T-P0-C0"
      }
    },
    "SlotType": "FullLength"
  },
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}

Change-Id: Iba1b98734fdfee43c2995f6c9f1f2660e196814a

Signed-off-by: Sunny Srivastava <[email protected]>
Co-authored-by: Sunny Srivastava <[email protected]>
Signed-off-by: Souvik Roy <[email protected]>
@souvik1914581 souvik1914581 force-pushed the sr_publichLocationPcieDeviceSchema branch from dde2c22 to eeec232 Compare April 21, 2025 18:26
@souvik1914581 souvik1914581 requested a review from gtmills April 22, 2025 04:26
@souvik1914581
Copy link
Contributor Author

Hi, requesting more reviews on this PR.

Copy link
Contributor

@jeaaustx jeaaustx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.
nit: If you add three backticks on a line before and on a line after the curl commands and their output in the commit message and in the PR message it will format nicer.

@rfrandse rfrandse merged commit fb3e088 into ibm-openbmc:1120 Apr 29, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants