Hello Casey,
We have something like that internally. It works something like this:
./sdndbg trace --from --to
{protocol:-tcp,udp,icmp4,ip4,arp,dhcp4} {protocol specific options}
would generate the output that one could directly use in `ovn-trace` command.
It is currently python based, and I
On 6/8/20 1:52 PM, Dumitru Ceara wrote:
> Hi everyone,
>
> CC-ing ovn-kubernetes mailing list as I know there's interest about this
> there too.
>
> OVN currently has a couple of tools that help
> tracing/tracking/simulating what would happen to packets within OVN,
> some examples:
>
> 1. ovn-tr
Skydive would be awesome, but that's a lot of work to integrate. I'd love
to see it more widely deployed, but that hasn't happened.
For starters, ovn-kubernetes should probably come with some kind of
ovn-trace wrapper that has a bit more logic around it. I could imagine it
looking something like
On Wed, Jun 10, 2020 at 3:36 AM Dumitru Ceara wrote:
> On 6/9/20 3:47 PM, Tim Rozet wrote:
> > Hi Dumitru,
>
> Hi Tim,
>
> > Thanks for the detailed explanation. It makes sense and would like to
> > comment on a few things you touched on:
> > 1. I do think we need to somehow functionally trigger
On 6/9/20 3:47 PM, Tim Rozet wrote:
> Hi Dumitru,
Hi Tim,
> Thanks for the detailed explanation. It makes sense and would like to
> comment on a few things you touched on:
> 1. I do think we need to somehow functionally trigger conntrack when we
> do ofproto-trace. It's the only way to know what
Hi Dumitru,
Thanks for the detailed explanation. It makes sense and would like to
comment on a few things you touched on:
1. I do think we need to somehow functionally trigger conntrack when we do
ofproto-trace. It's the only way to know what the real session state ends
up being, and we need to be