Add LLDP reporting and validation to tripleo introspection/deployment

Registered by Dan Sneddon on 2016-06-13

Currently TripleO leverages Ironic-Inspector to do introspection on hardware nodes. Work is underway to add LLDP collection to ironic-python-agent. This data should be parsed and reported on in a human-readable form so that the operator can use this data for validation. The data may also be useful for automation in the future.

Blueprint information

Status:
Complete
Approver:
Steven Hardy
Priority:
Medium
Drafter:
Dan Sneddon
Direction:
Approved
Assignee:
Bob Fournier
Definition:
Approved
Series goal:
Accepted for queens
Implementation:
Implemented
Milestone target:
milestone icon queens-2
Started by
Dan Sneddon on 2017-01-27
Completed by
Alex Schultz on 2017-12-08

Related branches

Sprints

Whiteboard

The specification describes the work that will be done in ironic-inspector to parse the LLDP TLVs and store the data in swift. It also describes the changes to display the data in openstack commands via python-ironic-inspector-client. Additional work will be needed to use the LLDP data in tripleo validations to verify that the templates match the switch configurations. Some potential validations possible with LLDP data are:

- Verify VLAN IDs set on switch match VLANs in configuration in nic-config files
- Verify link aggregation is set on switch when bonds are configured
- Verify maximum frame set set is not less than mtu configured
- Verify that expected ports are configured for bonds
- Check that links are set to auto-negotiate

(?)

Work Items

Work items:
Parse LLDP data and store in swift (https://review.openstack.org/#/c/406496/): DONE
Add reporting CLI (https://review.openstack.org/#/c/419141/): DONE
Add validation to use LLDP data (https://review.openstack.org/#/c/512375/): DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.