Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[minigraph.py]: Parse peer switch info from minigraph #5869

Merged
merged 7 commits into from
Nov 13, 2020

Conversation

theasianpianist
Copy link
Contributor

- Why I did it

- How I did it
Add PEER_SWITCH table to config_DB:

PEER_SWITCH: {
	switch_name: {
		address_ipv4: {
			'ipv4 address'
		}
	}
}

Add dual ToR subtype to config_DB:

DEVICE_METADATA: {
	localhost: {
		...
		subtype: 'DualToR'
		...
	}
}

- How to verify it

- Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

@theasianpianist
Copy link
Contributor Author

retest this please

@theasianpianist
Copy link
Contributor Author

retest vs please

@theasianpianist
Copy link
Contributor Author

retest vs please

@theasianpianist theasianpianist merged commit bf50562 into sonic-net:master Nov 13, 2020
@theasianpianist theasianpianist deleted the mg-peer-switch branch November 13, 2020 23:31
santhosh-kt pushed a commit to santhosh-kt/sonic-buildimage that referenced this pull request Feb 25, 2021
* Create new `PEER_SWITCH` table in config DB with info from minigraph
* Add `subtype` field to `DEVICE_METADATA` table and set value to `DualToR` if device is in a dual ToR setup
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.

2 participants