Ask Your Question
0

tripleo queens ovn compute / fixed external ip not assigned [closed]

asked 2019-10-26 01:24:47 -0600

jkrah gravatar image

updated 2019-10-26 07:40:08 -0600

Trying to deploy Tripleo (qeeens) with ovn enabled.. Following (my interpretation of) the Redhat OS13 docs I have.. (Note: Im just using the RHOS13 docs as reference. Im deploying upstream/opensource queens)

  1. modified my compute NIC config to include the External network / vlan.
  2. modified environments/network-isolation.yaml to add the OS::TripleO::Compute::Ports::ExternalPort:
  3. modified environments/ips-from-pool-all.yaml to add the OS::TripleO::Compute::Ports::ExternalPort:
  4. modified (my env file) templates/fixed-ips.yaml to add relevant IPs (for ComputeIPs: / external:)

But the deploy is failing (step: overcloud.Compute.1.NetworkDeployment:) .. On my compute nodes if I examine /etc/os-net-config/config.json it looks like the (fixed) external IP is not being assigned.. (vlan10 is my external vlan)

[heat-admin@compute0 ~]$  cat /etc/os-net-config/config.json | jq ".network_config[3]"
{
  "members": [
    {
      "name": "nic4",
      "primary": true,
      "type": "interface"
    },
    {
      "addresses": [
        {
          "ip_netmask": ""
        }
      ],
      "routes": [
        {
          "default": true,
          "next_hop": "172.16.210.1"
        }
      ],
      "type": "vlan",
      "vlan_id": 10
    }
  ],
  "name": "br-ex",
  "type": "ovs_bridge",
  "use_dhcp": false
}
[heat-admin@compute0 ~]$

The vlan and next_hop look good..

I seem to be missing something to get the IP address assigned..

Any clues ??

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by jkrah
close date 2019-10-29 05:11:05.244820

Comments

I'm not sure if I'm heading in the right direction. Ive included a roles_data.yaml file that has the Compute role including the External network. Compute seems to get further as compute nodes now have (fixed) External IP's. (Compute) Now bombs out during docker-puppet tasks (generate config)

jkrah gravatar imagejkrah ( 2019-10-27 05:13:28 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-10-29 05:09:56 -0600

jkrah gravatar image

Closing this question as adding the External Network to the compute role resolved the fixed ip allocation issue.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-10-26 01:24:47 -0600

Seen: 43 times

Last updated: Oct 29