11:04 a.m.
Hi Gianluca,
The provider in version 4.1 was installed automatically, but it did not
save the fact of being installed.
Hence if you try to install it in 4.2, it will try to install itself again
(and this time it will save the info of being installed).
I'm planning to add a feature that will allow reusing an already existing
provider during engine-setup. For now you can skip the provider
installation, the existing one will be kept as it is.
Thanks,
Marcin
On Mon, May 21, 2018 at 4:55 PM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
>
>
Another information regarding my current environment:
From engine database it results that my OVN provider name is "OVN"
engine=# select id,name from providers;
id | name
--------------------------------------+------------------------
ceab03af-7220-4d42-8f5c-9b557f5d29af | ovirt-image-repository
84546a85-2958-4c1d-bbfe-afeb486ebda9 | OVN
(2 rows)
engine=#
why it seems that in its default config it would name it
"ovirt-provider-ovn"?
Does this mean that it will be no conflict in name? But what about the
current nortbridge and southbridge configs?
Currently my central server is the engine (that is external to the infra)
and it shows this:
[root@ovmgr1 ~]# ovn-sbctl show
Chassis "1dce5b7c-a9fc-4ddb-99b4-e2c9e0fa54c5"
hostname: "ov200.mydomain"
Encap geneve
ip: "10.4.192.32"
options: {csum="true"}
Chassis "b8872ab5-4606-4a79-b77d-9d956a18d349"
hostname: "ov301.mydomain"
Encap geneve
ip: "10.4.192.34"
options: {csum="true"}
Chassis "ddecf0da-4708-4f93-958b-6af365a5eeca"
hostname: "ov300.mydomain"
Encap geneve
ip: "10.4.192.33"
options: {csum="true"}
[root@ovmgr1 ~]#
and
[root@ovmgr1 ~]# ovn-nbctl show
switch 32367d8a-460f-4447-b35a-abe9ea5187e0 (ovn192)
port affc5570-3e5a-439c-9fdf-d75d6810e3a3
addresses: ["00:1a:4a:17:01:73 dynamic"]
port f639d541-2118-4c24-b478-b7a586eb170c
addresses: ["00:1a:4a:17:01:75 dynamic"]
switch 6110649a-db2b-4de7-8fbc-601095cfe510 (ovn192)
switch 64c4c17f-cd67-4e29-939e-2b952495159f (ovn172)
port 32c348d9-12e9-4bcf-a43f-69338c887cfc
addresses: ["00:1a:4a:17:01:72 dynamic"]
port 3c77c2ea-de00-43f9-a5c5-9b3ffea5ec69
addresses: ["00:1a:4a:17:01:74 dynamic"]
switch 04501f6b-3977-4ba1-9ead-7096768d796d (ovn172)
port 0a2a47bc-ea0d-4f1d-8f49-ec903e519983
addresses: ["00:1a:4a:17:01:65 dynamic"]
port 8fc7bed4-7663-4903-922b-05e490c6a5a1
addresses: ["00:1a:4a:17:01:64 dynamic"]
port f2b64f89-b719-484c-ac02-2a1ac8eaacdb
addresses: ["00:1a:4a:17:01:59 dynamic"]
port f7389c88-1ea1-47c2-92fd-6beffb2e2190
addresses: ["00:1a:4a:17:01:58 dynamic"]
[root@ovmgr1 ~]#
and on my hosts currently I have something like this (eg on ov200):
[root@ov200 ~]# ovs-vsctl show
ae0a1256-7250-46a2-a1b6-8f0ae6105c20
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "ovn-ddecf0-0"
Interface "ovn-ddecf0-0"
type: geneve
options: {csum="true", key=flow,
remote_ip="10.4.192.33"}
Port "ovn-b8872a-0"
Interface "ovn-b8872a-0"
type: geneve
options: {csum="true", key=flow,
remote_ip="10.4.192.34"}
ovs_version: "2.7.3"
[root@ov200 ~]#
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org