Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

fix SwitchPeers validation #959

Open
karenetheridge opened this issue Nov 29, 2019 · 3 comments
Open

fix SwitchPeers validation #959

karenetheridge opened this issue Nov 29, 2019 · 3 comments
Assignees
Labels
bug needs spec Additional information is required, preferably as a formal specification v2 This targets conch-api version 2 (legacy) v3.next features, big changes for api v3.<next> v3.0 features, big changes for api v3.0 validation

Comments

@karenetheridge
Copy link
Contributor

  • presently, the SwitchPeers validation fails when there is a gap in the rack layout -- necessitating a 'blank' hardware product to be inserted
  • also, (per Jeff) "it will need some new logic because it won't work with the new 4u servers cabling; -- well I think we need a way to have some sort of custom logic based on rack type; manta cabling should always be the same; that validation actually needs to be smarter too; becuase it only just gets the ports and validates the peer ports and thats it"
@karenetheridge karenetheridge added bug validation v3.0 features, big changes for api v3.0 labels Nov 29, 2019
@karenetheridge karenetheridge added the v2 This targets conch-api version 2 (legacy) label Jan 17, 2020
@karenetheridge
Copy link
Contributor Author

@perigrin We need a spec for this before Jeff leaves.

@karenetheridge karenetheridge added the needs spec Additional information is required, preferably as a formal specification label Apr 17, 2020
@perigrin
Copy link
Contributor

@jemershaw if you get a chance to brain dump here

@karenetheridge
Copy link
Contributor Author

A better understanding of the problems with this validation is necessary for rewriting it as part of #943.

@karenetheridge karenetheridge added the v3.next features, big changes for api v3.<next> label Aug 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug needs spec Additional information is required, preferably as a formal specification v2 This targets conch-api version 2 (legacy) v3.next features, big changes for api v3.<next> v3.0 features, big changes for api v3.0 validation
Projects
None yet
Development

No branches or pull requests

2 participants