Bug 1467698 - [RFE] Validation and Management of Top-of-Rack Switch Configuration
[RFE] Validation and Management of Top-of-Rack Switch Configuration
Status: ASSIGNED
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 14.0 (Rocky)
Assigned To: Florian Fuchs
nlevinki
NeedsAllocation
: FutureFeature, Triaged
Depends On:
Blocks: 1476900
  Show dependency treegraph
 
Reported: 2017-07-04 12:20 EDT by Frank Zdarsky
Modified: 2017-10-16 14:31 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Frank Zdarsky 2017-07-04 12:20:00 EDT
Scope / Description:
OSP deployments for NFV have very complex network environments, with different overcloud nodes roles (say, compute-ovs, compute-sriov-2nics, compute-sriov-4nics, compute-ovs-dpdk) having vastly different NIC, VLAN segregation and bonding configurations. As a result, a recurring source of errors when deploying and scaling OSP are mismatching configurations on the Top-of-Rack switches.

This RFE is to add a pre-{deployment, scaling, upgrade} validation of ToR switch configurations to ensure these match the host networking configuration and - optionally - to manage those configurations.

A requirement is to support deployments with multiple roles on the overcloud node side and multiple switch vendors on the ToR side, e.g. using ansible-networking.
Comment 3 Mark McLoughlin 2017-07-04 16:34:35 EDT
Related, a design for gathering the LLDP data via Ironic introspection is here:

https://specs.openstack.org/openstack/tripleo-specs/specs/newton/tripleo-lldp-validation.html

and this is available since OSP-11:

https://bugzilla.redhat.com/1427608

Note You need to log in before you can comment on or make changes to this bug.