Open MITLabo opened 4 years ago
コマンド検討用
packstack \
--os-swift-install=y \
--os-heat-install=y \
--os-magnum-install=y \
--os-sahara-install=y \
--os-neutron-lbaas-install=y \
--ntp-servers=pool.ntp.org \
--keystone-admin-passwd=password \
--os-neutron-ovs-bridge-mappings=physnet1:br-ens224 \
--os-neutron-ovs-bridge-interfaces=br-ens224:ens224 \
--os-neutron-ovs-tunnel-if=ens224 \
--os-heat-cfn-install=y \
--os-neutron-ml2-tenant-network-types=vxlan \
--os-neutron-ml2-type-drivers=vxlan \
--os-neutron-metering-agent-install=n \
--provision-demo=n \
--os-compute-hosts=192.168.100.71,192.168.100.72 \
--os-neutron-l2-agent=openvswitch \
--os-neutron-ml2-mechanism-drivers=openvswitch \
--gen-answer-file ~/answers.txt
packstack \
--os-swift-install=y \
--os-heat-install=y \
--os-magnum-install=y \
--os-sahara-install=y \
--ntp-servers=ntp.nict.jp \
--keystone-admin-passwd=password \
--os-neutron-ovn-bridge-mappings=extnet:br-ex,prinet:br-pri \
--os-neutron-ovn-bridge-interfaces=br-ex:ens192,br-pri:ens224 \
--os-neutron-ovn-tunnel-if=ens224 \
--os-heat-cfn-install=y \
--provision-demo=n \
--os-compute-hosts=192.168.100.72,192.168.100.73 \
--gen-answer-file ~/answers.txt
なぜか無い。。。
--os-config-neutron-ovn-tunnel-subnets=172.16.107.0/24 \
直接変更する。設定しておかないとNICがIPアドレスを保持していてもエラーになる。CIDR表記でアドレス振らないが正解なのか?
CONFIG_NEUTRON_OVN_TUNNEL_SUBNETS=172.16.107.0/24
下記で3ノードクラスタ一旦完成だが、内部ブリッジは未確認なので、継続検証する。
[root@OSnode01 ~]# sdiff default_answers.txt answers.txt | grep "|" | grep -v "_PW"
CONFIG_SAHARA_INSTALL=n | CONFIG_SAHARA_INSTALL=y
CONFIG_HEAT_INSTALL=n | CONFIG_HEAT_INSTALL=y
CONFIG_MAGNUM_INSTALL=n | CONFIG_MAGNUM_INSTALL=y
CONFIG_NTP_SERVERS= | CONFIG_NTP_SERVERS=ntp.nict.jp
CONFIG_COMPUTE_HOSTS=192.168.100.71 | CONFIG_COMPUTE_HOSTS=192.168.100.72,192.168.100.73
CONFIG_KEYSTONE_ADMIN_TOKEN=174903f3d9a04e16b3562e8b1d146f21 | CONFIG_KEYSTONE_ADMIN_TOKEN=e2e5323e8349412f9e3db90f17b731e7
CONFIG_NEUTRON_OVN_BRIDGE_MAPPINGS=extnet:br-ex | CONFIG_NEUTRON_OVN_BRIDGE_MAPPINGS=extnet:br-ex,prinet:br-pri
CONFIG_NEUTRON_OVN_BRIDGE_IFACES= | CONFIG_NEUTRON_OVN_BRIDGE_IFACES=br-ex:ens192,br-pri:ens224
CONFIG_NEUTRON_OVN_TUNNEL_IF= | CONFIG_NEUTRON_OVN_TUNNEL_IF=ens224
CONFIG_NEUTRON_OVN_TUNNEL_SUBNETS= | CONFIG_NEUTRON_OVN_TUNNEL_SUBNETS=172.16.107.0/24
CONFIG_HORIZON_SECRET_KEY=fc57d5a3334c4a6ba355167c8af14af8 | CONFIG_HORIZON_SECRET_KEY=4f5eb7e87e32408c926818edaaeca568
CONFIG_SWIFT_HASH=b4dd3ad4378d4fd1 | CONFIG_SWIFT_HASH=6b2aa2a342e84195
CONFIG_HEAT_AUTH_ENC_KEY=181fb1f8125643d8 | CONFIG_HEAT_AUTH_ENC_KEY=04080a7b05b94b63
CONFIG_HEAT_DOMAIN_PASSWORD=PW_PLACEHOLDER | CONFIG_HEAT_DOMAIN_PASSWORD=059f54b818ce483f
CONFIG_PROVISION_DEMO=y | CONFIG_PROVISION_DEMO=n
CONFIG_CEILOMETER_SECRET=63344611811e40ec | CONFIG_CEILOMETER_SECRET=5cd683fb0e1a4a65~~~
internalとnovaゾーンでNIC分離できている。Timezone忘れてた。。。
== Nova managed services ==
+--------------------------------------+------------------+--------------------+----------+---------+-------+----------------------------+-----------------+-------------+
| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | Forced down |
+--------------------------------------+------------------+--------------------+----------+---------+-------+----------------------------+-----------------+-------------+
| 12a19823-e0eb-46d8-a8fe-9d019586fc76 | nova-conductor | OSnode01.shift.com | internal | enabled | up | 2020-02-04T12:33:04.000000 | - | False |
| 036a316f-e099-48ee-bb5f-6ede6d968bb1 | nova-scheduler | OSnode01.shift.com | internal | enabled | up | 2020-02-04T12:33:09.000000 | - | False |
| 521949de-fb4a-4bf8-a028-7ea2c6c0ba72 | nova-consoleauth | OSnode01.shift.com | internal | enabled | up | 2020-02-04T12:33:04.000000 | - | False |
| c468c3b1-9d1d-49b0-aa2c-d85dcf7519f4 | nova-compute | osnode03.shift.com | nova | enabled | up | 2020-02-04T12:33:10.000000 | - | False |
| 6e042d21-b5c6-4f77-b19c-38f228296885 | nova-compute | osnode02.shift.com | nova | enabled | up | 2020-02-04T12:33:02.000000 | - | False |
+--------------------------------------+------------------+--------------------+----------+---------+-------+----------------------------+-----------------+-------------+
OVNのブリッジトンネルgeneveでcontrolノードと2台のcomputeノードが繋がってる。かっこいいな。最近な感じ。
[root@OSnode01 ~(keystone_admin)]# ovs-vsctl show
047a70c3-d793-4415-887c-fcb773fed4dc
Bridge br-int
fail_mode: secure
Port "ovn-7cfac6-0"
Interface "ovn-7cfac6-0"
type: geneve
options: {csum="true", key=flow, remote_ip="172.16.107.13"}
Port br-int
Interface br-int
type: internal
Port "ovn-d9155b-0"
Interface "ovn-d9155b-0"
type: geneve
options: {csum="true", key=flow, remote_ip="172.16.107.12"}
Bridge br-pri
fail_mode: standalone
Port "ens224"
Interface "ens224"
Port br-pri
Interface br-pri
type: internal
Bridge br-ex
fail_mode: standalone
Port br-ex
Interface br-ex
type: internal
Port "ens192"
Interface "ens192"
ovs_version: "2.11.0"
Is your feature request related to a problem? Please describe. Steinのリリース特にOVSからOVNへのデフォ変更対応
Describe the solution you'd like ブリッジドライバをOVN指定で再作成する。そのほかAnsibleの洗練化を目指す。
Describe alternatives you've considered OVN理解だが、ものはOVSをベースとしているため、まずは最小限のパラメータ変更で対応する。
Additional context https://metonymical.hatenablog.com/entry/2019/07/21/190302