System environment:
CentOS 7.4 + ovs2.8.1 + ovn2.8.1
Seliunx closed, firwalld open all ports
OVS and von services all open and normal
Because OVS and OVN are on CentOS, OVS can not be OVN controlled by default
The following problems appear in the /var/log/openvswitch/ovn-controller.log:
2018-01-18
On Wed, Jan 17, 2018 at 09:17:07PM -0200, Flavio Leitner wrote:
> On Wed, Jan 17, 2018 at 04:35:01PM +, Vishal Deep Ajmera wrote:
> > > What happens if you have two or more bonds or if we fix dpdk port too,
> > > what happens when you have more than one?
> > > I think you will see errors/fai
On Wed, Jan 17, 2018 at 04:35:01PM +, Vishal Deep Ajmera wrote:
> > What happens if you have two or more bonds or if we fix dpdk port too,
> > what happens when you have more than one?
> > I think you will see errors/failures.
>
> I tried with two dpdk ports and I do see following print on
We've had a bit of a think about this, variable length probably isn't too
important (static 64b is probably fine), but yes, being able to set those
64 bytes will be quite useful with say with an extra "payload=0xC0FEFE"
argument on ofproto/trace.
Brad
On 18 January 2018 at 07:17, Ben Pfaff wrote
Hi,
Assuming that all ports use the same MTU, in OVS2.8 and earlier, a single
mempool of 256K buffers (MAX_NB_MBUF = 4096 * 64) will be created and shared by
all the ports
With the OVS2.9 mempool patches, we have port specific allocation and the
number of mbufs created for each port is based
Hi,
At eBay, we use OVN for multiple projects that are built with Go. We built a
Go Client to interact with OVN north-bound database directly.
We think it will be useful outside of eBay, and have now open sourced it at
https://github.com/eBay/go-ovn
Please try it, send feedback and PRs to make
On Sun, Jan 14, 2018 at 01:41:36PM -0800, Anil Jangam wrote:
> Hi,
>
> The "transact" method of OVSDB protocol mandates the sequential processing
> of the transaction. It is specificed in section 4.1.3 as follows.
>
>The database server executes each of the specified operations in
> the speci
OK, sounds good.
Do you think you need the ability to inject payloads of a specific
length or content? It's easy to, for example, always generate 64 bytes
of payload, but it would be a little more challenging to plumb through
extra data or metadata.
On Mon, Jan 15, 2018 at 01:48:10PM +1300, Brad
On Mon, Jan 15, 2018 at 08:46:50AM -0500, Russell Bryant wrote:
> On Mon, Jan 15, 2018 at 2:30 AM, Numan Siddique wrote:
> >
> >
> > On Fri, Jan 12, 2018 at 1:28 AM, Ben Pfaff wrote:
> >>
> >> I posted the patches to add clustering support to OVSDB at the end of
> >> last year so that it was tech
> What happens if you have two or more bonds or if we fix dpdk port too,
> what happens when you have more than one?
> I think you will see errors/failures.
I tried with two dpdk ports and I do see following print on console though
it seem harmless and does not impact route table. Also, this h
Hi David,
Please show us the output of:
ifconfig -a
ip address show
sudo ovs-vsctl show
On Wed, Jan 17, 2018 at 11:18 AM, David Gabriel
wrote:
> Here are the instances addresses:
> VM1: 10.0.1.10
> OVS: 10.0.1.11 et 10.0.2.10
> VM2: 10.0.2.11
> Before configuring the ovs bridge the ping betwe
> On Jan 16, 2018, at 9:28 AM, David Gabriel wrote:
>
> Dears,
>
> I am writing you this email to look for your help in order to fix a problem,
> I am facing since a while, related to creating two ubuntu instances in
> Openstack (Fuel 9.2 for Mitaka) and setting an ovs bridge in each VM.
> He
Here are the instances addresses:
VM1: 10.0.1.10
OVS: 10.0.1.11 et 10.0.2.10
VM2: 10.0.2.11
Before configuring the ovs bridge the ping between VM1 and 10.0.1.11 is
working (same for the ping between VM2 and 10.0.2.10)
Please advise me how to fix this issue.
Thanks in advance.
Regards.
2018-01-17
On Wed, Jan 17, 2018 at 10:25:36AM +, Vishal Deep Ajmera wrote:
> Hi Flavio,
>
> I tried to look closer into ifup-ovs script particularly for OVSDPDKPort &
> OVSDPDKBOND cases.
> With the change given below (git diff) at the end OVSDPDKBOND case, I see
> that the routes
> are getting insta
That something simple was my port connection. Traffic was never passing
through the switch.
2018-01-17 12:06 GMT+01:00 Alan Kayahan :
> Hello,
>
> In my custom action, setting the ethertype as following works
>
> struct eth_header *eh = dp_packet_eth(b);
> eh->eth_type = htons(ETH_TYPE_IPV6)
>
>
Hi David,
What are the IPs of those VMs and the ovs VM?
On Jan 17, 2018 5:59 AM, "David Gabriel" wrote:
Thanks Felipe Arturo for your reply.
Without setting the ovs bridge, the ping between VM1 and the interface of
OVS instance connected to LAN1 is working fine (same for VM2 and OVS).
I am won
Hello,
In my custom action, setting the ethertype as following works
struct eth_header *eh = dp_packet_eth(b);
eh->eth_type = htons(ETH_TYPE_IPV6)
However setting the next header field in IPv6 header as following doesn't.
struct ip6_hdr *nh = dp_packet_l3(b)
nh->ip6_nxt = htons(IPPROTO_AH);
I
Hi Flavio,
I tried to look closer into ifup-ovs script particularly for OVSDPDKPort &
OVSDPDKBOND cases.
With the change given below (git diff) at the end OVSDPDKBOND case, I see that
the routes
are getting installed again after adding dpdkbond port to the bridge. Perhaps
the same fix
needs
Thanks Felipe Arturo for your reply.
Without setting the ovs bridge, the ping between VM1 and the interface of
OVS instance connected to LAN1 is working fine (same for VM2 and OVS).
I am wondering if there is any setting I have to add in my instances in
order to enable the ping between the 3 insta
19 matches
Mail list logo
