Bug 1467698 - [RFE] Validation and Management of Top-of-Rack Switch Configuration
Summary: [RFE] Validation and Management of Top-of-Rack Switch Configuration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Florian Fuchs
QA Contact: nlevinki
URL:
Whiteboard: NeedsAllocation
Depends On:
Blocks: 1476900
TreeView+ depends on / blocked
 
Reported: 2017-07-04 16:20 UTC by Frank Zdarsky
Modified: 2019-12-05 10:21 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-05 10:21:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Frank Zdarsky 2017-07-04 16:20:00 UTC
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 20:34:35 UTC
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

Comment 10 Jose Luis Franco 2019-11-20 09:20:59 UTC
Now that the validation framework is in place, it makes sense to move this RFE into a validation. The idea of this validations are to be developed by each responsible DFG, not the validations Squad (they only take ownership of the framework), so moving the BZ into DFG:NFV to plan the creation of such a validation.
Also, adding some documentation in relation to how the validations can be executed and the repository where they are located:

openstack/tripleo-validations: https://github.com/openstack/tripleo-validations
Guide: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/post_deployment/validations/cli.html


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