Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will provide network utility APIs.
What changes:
APIs
I have analyzed the existing API classifications and then assigned separate API tags. It's because these APIs can be used to design and validate a network for both the MCIR and the MCIS. (I think it could be used more generally :-) )
It would be great for me to get some feedback on this, and I will quickly modify the
route
andtag in annotation
according to the feedback :-DAPI usage example
POST /util/net/design
This API can support network design more easily than calculating and designing all CIDR blocks.
"minSubnets"
and"minHosts"
are supported astype
for the subnetting rule.POST /util/net/validate
The following example shows validating a multi-cloud network consisting of 2 VPC networks, each with 4 subnets.