Рет қаралды 21
Inbound Routing issue 518: Community discussed the use of VNI, Vnet and prefix in the inbound routing rule table for PA validation and peered Vnet scenarios. They clarified that the prefix is optional and not used for this table, and that the VNI is required to match the peered Vnet. They also suggested to rename the table to PA validation table or create a separate stage for it.
PR 462:Kristina asked Marian about the status of this PR, which adds a new table for explicit PA validation. Marian said he will work on it next week after closing the PR and T with Riff and Andrei.
PR 509:Prince explained that this PR fixes some formatting and naming issues in the DASH model and API, and does not change the behavior.
PR 515:Prince introduced a new PR that adds a route group table and a binding operation to enable atomic updates of routes for an ENI. Sushant and Agrawal asked some questions about the motivation and the implementation of this change, and Prince explained how it aligns with the customer expectations and the cloud provider APIs.