Skip to content
This repository was archived by the owner on Jul 18, 2025. It is now read-only.

doc: description packet's road in butterfly#387

Open
outscale-toa wants to merge 1 commit into
outscale:developfrom
outscale-toa:description
Open

doc: description packet's road in butterfly#387
outscale-toa wants to merge 1 commit into
outscale:developfrom
outscale-toa:description

Conversation

@outscale-toa

Copy link
Copy Markdown
Contributor

Signed-off-by: Thiery Ouattara thiery.ouattara@outscale.com

@jerome-jutteau

Copy link
Copy Markdown
Contributor

Hi, few general comments about documentation:

  • English please
  • Standard formating please (md ?)

And particularly to this PR: what about this title: doc: add packet's journey in Butterfly case ?

@outscale-toa outscale-toa force-pushed the description branch 3 times, most recently from 78e7c85 to fccf269 Compare June 27, 2019 12:24
@outscale-mgo

Copy link
Copy Markdown

s/packet's/packets/
s/road/flow/

Comment thread doc/DESCRIPTION.md Outdated

### Poll

- We collect packets and its numbers in ethernet device queue, store them in array.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Traduction:
on collecte les paquets et son nombre dans la queue du périphérique ethernet, les stock dans tableau.

Comment thread doc/DESCRIPTION.md Outdated
### Poll

- We collect packets and its numbers in ethernet device queue, store them in array.
- We rebuild all metadata for each packet and burst all packets in opposite direction

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We rebuild packets metadata.
Burst them.

Comment thread doc/DESCRIPTION.md Outdated
### Burst

- We collect packets, its numbers, put them in ethernet device queue.
- We burst packets in the queue on ethernet port and free memory.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

put them in ethernet device queue.
We burst packets in the queue so it's not the same operation ?
free memory Which one ?

Signed-off-by: Thiery Ouattara <thiery.ouattara@outscale.com>
@outscale-mgo

Copy link
Copy Markdown

Also, s/Packet road/packet flow/

Comment thread doc/DESCRIPTION.md
@@ -0,0 +1,88 @@
DESCRIPTION

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DESCRIPTION of what ?

Comment thread doc/DESCRIPTION.md

### Poll:

- We collect VM packets in the queue. If not packet in the queue it return.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/not/no/
s/in/are in/

Comment thread doc/DESCRIPTION.md
## Packets go to VM (VHOST)

### Burst:
- Vhost bricks got all packet

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure of that ^
I mean each brick "got all packets"

Comment thread doc/DESCRIPTION.md
@@ -0,0 +1,88 @@
DESCRIPTION

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might add some schema here:
scenario 1: VM to VM in the same VNI on the same host

          /----[Firewall ?]--[Antispoof]--[ sniffer ?]--[vhost, tap or bench brick]
[switch]<
          \----[Firewall ?]--[Antispoof]--[ sniffer ?]--[vhost, tap or bench brick]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll do other schema latter

@outscale-mgo outscale-mgo Sep 9, 2019

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

scenario 2: VM to VM in the same VNI on diferent host with one VN of the same VNI par host

           /- [nic] -- [sniffer ?] -- [vtep] -- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
{The WEB} <
           \- [nic] -- [sniffer ?] -- [vtep] -- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

scenario 3: VM to VM in the same VNI on diferent host with more than 1 VN of the same VNI on 1rst host

                                                          /- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
           /- [nic] -- [sniffer ?] -- [vtep] -- [switch] {- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
{The WEB} <
           \- [nic] -- [sniffer ?] -- [vtep] -- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants