Question

我正在尝试将OpenDayLight（ODL）用作OpenStack的第二个控制器。如下使用OpenStack作为一体（控制器+计算）和一些输出来了解我的拓扑和基础知识：

[root@gg ~(keystone_admin)]# nova list
+--------------------------------------+---------+--------+------------+-------------+-----------------+
| ID                                   | Name    | Status | Task State | Power State | Networks        |
+--------------------------------------+---------+--------+------------+-------------+-----------------+
| 1ceb6ccc-b0c1-407d-92ab-5753f58e7f21 | testVM  | ACTIVE | -          | Running     | MCMGmt=10.1.0.8 |
| f52d9096-c814-4fb4-b802-a6a0013bf22b | testVM2 | ACTIVE | -          | Running     | MCMGmt=10.1.0.6 |
+--------------------------------------+---------+--------+------------+-------------+-----------------+
[root@gg ~(keystone_admin)]#
[root@gg ~(keystone_admin)]# ovs-vsctl show
ee5c6b92-4ecb-4b72-b6e0-ebebf3933a7b
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port "qr-322e0523-f2"
            tag: 1
            Interface "qr-322e0523-f2"
                type: internal
        Port "qg-e9916049-c4"
            tag: 2
            Interface "qg-e9916049-c4"
                type: internal
        Port "tapdc50bbac-39"
            tag: 2
            Interface "tapdc50bbac-39"
                type: internal
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port "qvob5fdc6c0-05"
            tag: 1
            Interface "qvob5fdc6c0-05"
        Port "qvo3bb030ec-94"
            tag: 1
            Interface "qvo3bb030ec-94"
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap02b28510-ed"
            tag: 1
            Interface "tap02b28510-ed"
                type: internal
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth0"
            Interface "eth0"
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    ovs_version: "2.9.0"
[root@gg ~(keystone_admin)]#

如果我想使用ODL作为中子的控制器，我将获得如下链接：

https://wiki.opendaylight.org/view/OpenStack_and_OpenDaylight

但是我试图通过运行以下命令将ODL添加为第二个控制器（安装在其他主机上）：

ovs-vsctl set-controller br-int tcp:127.0.0.1:6633 tcp:<ODL IP>:6633

首先，我想问“ 通过set-controller命令添加第二个控制器ODL是否正确用例”。如果为是，则继续进行下一步操作。

添加第二个ODL IP作为控制器，我可以看到ODL被视为主控制器，并且其角色更改为MASTER。

Pcap snippet of MASTER role reques t from ODL

如果我们将ODL设为主节点，是否意味着我们将openstack上的控制器节点设为从节点，并且它仅具有读访问权限，而没有写访问权限。

同样，如果为 YES ，如何将其更改为 EQUAL_PRIORITY ，因为我看到ODL custom.properties文件中只有一个字段

Connection manager configuration
connection.scheme = ANY_CONTROLLER_ONE_MASTER

我们没有在方案中提及其他值。

OpenDayLight作为OpenStack的第二个控制器

0 个答案: