quantum configuration is overly hardcoded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Clint Byrum |
Bug Description
From the POC notes:
nova.conf - quantum_url is 127.0.0.1:9696 rather than 10.10.16.136:9696
Ditto quantum_
[[above:
177e540c (Robert Collins 2013-06-18 13:13:10 +1200 48)service_
]]
quantum/
may need to set nova-metadata_ip and nova_metadata_port too - to nova.host and 8775
in /etc/quantum/
local_ip is wrong - should be the machines local details - undercloud assigned ip. [[Done - see os-collect-config]]
the ctlplane networking configuration isn’t suitable for virtual: we don’t want any tenant traffic getting onto 10.10.16.x at all.
what we want for networking is the public range on the network nodes, and unbridged traffic on the other nodes.
so - bridge_mappings -> blank
vlan25 with .16 as it’s address [for all-in-one the API endpoint is the thing]
-> bridge mappings should be policy
[[ The above is all true now ]]
we still want br-int
We don’t need br-ctlplane [[ Wha? This needs more context I think ]]
network_
init-quantum is creating a provider network [[ All moved to incubator "from the outside" setup scripts ]]
init-quantum isn’t using the network range we want [[ Bug fails to say what we want, but I believe this is all handled now ]]
Changed in tripleo: | |
assignee: | nobody → Clint Byrum (clint-fewbar) |
Changed in tripleo: | |
status: | Triaged → In Progress |
This mega bug is mainly useful to crib things from - filing smaller targeted bugs as things are done.