Am I the first person to do AIO in the wrong way ?   No response from the  list/ community members !!!


How can newbies get inlined in the complex OpenStack suite ?    If there is a roadblock how can newbies get help if  the learning curve is so steep ?

 Or is there any other platform / channels to ask openstack deployment questions?  Pls let me know. 

Krish

On Thu, Mar 14, 2024 at 2:44 PM KK CHN <kkchn.in@gmail.com> wrote:
Hi,

Neutron external network connection to  and from instances.. 


Problem statement. 

I have deployed AIO on a Virtual Machine. (Created the  demo networks, flavors and images by    init-runonce script.)
I created a cirros instance with a demo-net instance, and the instance is spawning with 10.0.0.0/24 ips.

inside the cirros Vm I am able to ping its own ip(10.0.0.73) and  10.0.0.1 and  the "public1"  network  gateway  10.176.17.63 ..  But unable to ping  the Base VM IP 10.176.17.61

Any hints how I can reach the Base VM IP 10.176.17.61 ?    from 10.0.0.73 and vice versa .. 

 What steps I missed or  I am unaware of?  To get the external connection/ping/access..?

I have referred many documents and  I am at the end of the rope, but couldn't find a solution or what the exact issue is , any guidance much appreciated...

Krish.


If  more information  is required : 

There are two networks by default created

1. public1.  with gateway as 10.176.17.63

public1-subnet
10.176.16.0/23IPv410.176.17.63
2. demo-net 
demo-subnet10.0.0.0/24IPv410.0.0.1

These are the values given in the    " kolla_ansible_venv3/share/kolla-ansible/init-runonce"  script..

#################################################################################
DEMO_NET_CIDR=${DEMO_NET_CIDR:-'10.0.0.0/24'}
DEMO_NET_GATEWAY=${DEMO_NET_GATEWAY:-'10.0.0.1'}
DEMO_NET_DNS=${DEMO_NET_DNS:-'8.8.8.8'}

ENABLE_EXT_NET=${ENABLE_EXT_NET:-1}
EXT_NET_CIDR=${EXT_NET_CIDR:-'10.176.17.0/23'}
EXT_NET_RANGE=${EXT_NET_RANGE:-'start=10.176.17.62,end=10.176.17.80'}
EXT_NET_GATEWAY=${EXT_NET_GATEWAY:-'10.176.16.1'}
################################################################################


Demo Router: 


(ee6500a8-039c)
  • 10.176.17.63
ActiveExternal GatewayUP

(bb4c9437-82fa)
  • 10.0.0.1
ActiveInternal InterfaceUP


(kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml
---
workaround_ansible_issue_8743: yes
config_strategy: "COPY_ALWAYS"
kolla_base_distro: "ubuntu"
openstack_release: "2023.1"
kolla_internal_vip_address: "10.220.0.24"  // a free unused IP address in 10.220.0.0/24 segment. 
kolla_external_vip_address: "{{ kolla_internal_vip_address }}"
kolla_container_engine: docker
network_interface: "ens224"       /// this vNIC is with ip 10.220.0.51 and without internet - a vlan segment for internal experiments.
neutron_external_interface: "ens160"      // this is the vNIC with my organization dhcp leased ip 10.176.17.61  assigned and up and running
neutron_plugin_agent: "openvswitch"
nova_compute_virt_type: "qemu"
(kolla_ansible_venv3) ubuntu@ub

Strange Behaviour: 
When I create another instance ( Cirros) with the network selected as  " public1" network, the instance is spawning   the horizon dashboard showing IP as 10.176.17.70


extTestVMcirros
    10.176.17.70
But inside  this VM     $ ip a      /// lists the   IP  address of this VM as  169.254.198.1/16   ?? why 169.254 .198.1/16  ? It should be 10.176.17.70 right ?? 

What's happening ?? Confused ..