Skip to content

Conversation

@iceiilin
Copy link
Member

@iceiilin iceiilin commented Oct 9, 2015

Add a generate enclosure job, which can be executed when discovery compute node.
In this job, a node with type "enclosure" will be created; the information about enclosure's SN and compute nodes which are inserted in this enclosure will be added into this node.
The corresponding compute node will also have an array about its enclosure node ID.

https://hwjiraprd01.corp.emc.com/browse/MAG-176

PRs in other repos for this feature:
RackHD/on-taskgraph#11
RackHD/on-core#14
RackHD/on-http#18

@benbp @jfrey @VulpesArtificem

Copy link
Contributor

Choose a reason for hiding this comment

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

Whether the IPMI spec says the "Builtin FRU device (ID 0)" always maps to the enclosure?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch.

"Builtin FRU device (ID 0)" is hard coded in ipmitool for FRU 0, so it will also be there as long as we use methods based on ipmitool. and in IPMI spec, FRU device ID 0 is "FRU Device for the FRU that the management controller is located on".

I checked FRU spec in IPMI standard, "Product Serial" is in "product area info" of FRU format. Although our supported platforms support this area and entry, it is optional in the spec, and there is possibility that some vendors won't expose this info.

There are other sources in node's catalog that contains product serial number. I will use ipmi-fru as first source to cover mgmt. server which only have ipmi related info. Add will add dmi sources to cover some nodes which doesn't have this info in ipmi channel.

@benbp
Copy link
Contributor

benbp commented Oct 13, 2015

👍 great work!

Copy link
Contributor

Choose a reason for hiding this comment

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

Ahh, nice.

@iceiilin
Copy link
Member Author

Smoke test is needed to be modified due to changes in monorail API /nodes (without catalogs). Will get code changes in tests repo reviewed and merged product and test code at the same time.

@benbp
Copy link
Contributor

benbp commented Oct 19, 2015

Note to self: Some comments still pending on https://github.com/RackHD/tests/pull/39, merge this and its dependents when they are resolved.

benbp added a commit that referenced this pull request Oct 27, 2015
@benbp benbp merged commit d711790 into RackHD:master Oct 27, 2015
@benbp benbp deleted the feature/MAG-176-generate-enclosure branch October 27, 2015 17:51
AlliumApotheosis pushed a commit to AlliumApotheosis/on-tasks that referenced this pull request Dec 16, 2015
…onorail

This is a commit depending on on-http pull Request RackHD#26 which adds SAS/SATA
controller infomation into the SMART raw output. The change in this commit
further decodes the newly added SMART catalog fields and appends them to
the SMART catalog.

Unit test code is also included
@JenkinsRHD JenkinsRHD mentioned this pull request Mar 23, 2017
geoff-reid pushed a commit to geoff-reid/on-tasks that referenced this pull request May 5, 2017
Removing code for hardwired credentials and reading IP from DB
kellylu2sym pushed a commit to kellylu2sym/on-tasks that referenced this pull request Aug 8, 2017
Fix async function usage in task-graph-subscriptions
kellylu2sym pushed a commit to kellylu2sym/on-tasks that referenced this pull request Aug 8, 2017
…master

* commit '786c9180ec5ec41394d216100d1f6fde76f6fcaf':
  Remove unnecessary toJSON that breaks tests on some machines
kellylu2sym pushed a commit to kellylu2sym/on-tasks that referenced this pull request Aug 8, 2017
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.

3 participants