Ask Your Question

d4c07's profile - activity

2019-10-26 01:37:22 -0500 received badge  Famous Question (source)
2019-05-04 05:10:40 -0500 received badge  Notable Question (source)
2019-02-27 15:47:13 -0500 received badge  Popular Question (source)
2019-02-27 12:40:12 -0500 commented question Queens network isolation deployment failed. Overcloud nodes get only the provisioning IP address

I had a similar problem recently. Which I have now resolved. Can you post your network environment file? Have you tried taking out the overrides file and redeploying?

2019-02-27 10:42:05 -0500 answered a question tripleo - cannot access external network

So the issue here was that the configuration files within the network-environment.yaml and controller.yaml where not being picked up correctly during the overcloud deploy. Within the relevant files i put the full paths and this then picked up the correct configuration files. Also I added the full path to the run-os-net-config.sh. To correctly setup the controller node to have the right details the interfaces were modified as the below. The external IP was set on the bridge as it is the native VLAN

params:
        $network_config:
          network_config:
          # NIC 2- Provisioning
          - type: interface
            name: nic2
            use_dhcp: false
            defroute: false
            addresses:
            - ip_netmask:
                list_join:
                - /
                - - get_param: ControlPlaneIp
                  - get_param: ControlPlaneSubnetCidr
            routes:
            - ip_netmask: 169.254.169.254/32
              next_hop:
                get_param: EC2MetadataIp


          - type: ovs_bridge
            name: bridge_name
            use_dhcp: false
            addresses:
            - ip_netmask:
                {get_param: ExternalIpSubnet}
            routes:
            - default: true
              ip_netmask: 0.0.0.0/0
              next_hop:
                get_param: ExternalInterfaceDefaultRoute
            dns_servers:
              get_param: DnsServers
            members:
            - type: interface
              name: nic1
              # force the MAC address of the bridge to this interface
              primary: true
            - type: vlan
              vlan_id:
                get_param: StorageNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: StorageIpSubnet
            - type: vlan
              vlan_id:
                get_param: StorageMgmtNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: StorageMgmtIpSubnet
            - type: vlan
              vlan_id:
                get_param: InternalApiNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: InternalApiIpSubnet
            - type: vlan
              vlan_id:
                get_param: TenantNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: TenantIpSubnet

This now works correctly and the horizon dashboard and VMs are accessible on the external network.

2019-02-20 02:54:48 -0500 received badge  Enthusiast
2019-02-19 02:54:29 -0500 asked a question tripleo - cannot access external network

I am deploying Openstack via tripleo to one controller and one compute node from the undercloud. The installation completes successfully and the horizon dashboard is given an external IP but I am not able to access this. Nor am i able to ping the IP from the undercloud node. I believe everything from the network side is setup correctly and I appear to have followed the steps correctly. However, the default route is showing as the undercloud which i believe is incorrect as the undercloud should not be required for networking for the overcloud?

[heat-admin@overcloud-controller-0 ~]$ ip route show default via 192.168.24.1 dev enp2s0f1

Deploy command (one of many different variations tried)

openstack overcloud deploy --templates /home/stack/generated-openstack-tripleo-heat-templates \ -e /home/stack/templates/node-info.yaml \ -n /home/stack/templates/network_data.yaml \ -e /home/stack/generated-openstack-tripleo-heat-templates/environments/network-isolation.yaml \ -e /home/stack/generated-openstack-tripleo-heat-templates/environments/network-environment.yaml \ -e /home/stack/generated-openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \ --ntp-server http://pool.ntp.org

Can anyone point me in the right direction? Openstack version is Queens on CentOS.

2018-10-25 13:39:00 -0500 received badge  Famous Question (source)
2018-08-28 10:21:16 -0500 received badge  Notable Question (source)
2018-08-28 10:21:16 -0500 received badge  Popular Question (source)
2018-06-24 19:13:27 -0500 answered a question Unable to access external network

The issue was due to my error when creating the external network in the Horizon dashboard. I was mistakenly setting the wrong Physical Network - which should have been extnet which matches the bridge. The following command helped also helped by creating the external network from the command line.

neutron net-create external_network --provider:network_type flat --provider:physical_network extnet --router:external

2018-06-24 19:13:26 -0500 asked a question Unable to access external network

I have performed a packstack install (latest version) and run an all-in-one deployment which completed successfully. Upon completion I have created an internal and external within the horizon dashboard. I can assign IPs on both networks but I can only access them from the packstack server using ip netns, for example ip netns exec qrouter-2a65e98f-9bd3-4573-9330-3aee921b98bf ssh -i ~/.ssh/id_rsa centos@10.0.10.9. However, I am not able to simply ssh in using the external IP address. I set the gateway on the router to use the external network but I have since noticed that the status of this is down and it states VIF type binding failed. Unfortunately everything i seem to try results in the same down status.

The installation was a standard allinone install attempting to use my network packstack --allinone --provision-demo=n --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:enp2s0f0 --os-neutron-ml2-type-drivers=vxlan,flat.

I have looked online at a number of resources but I have not been able to identify the cause. I am fairly new to Openstack so any help would be much appreciated? Please let me know if any additional information is needed.