Open Stack

 The command that we use to create subnets looks like this:

openstack subnet create --no-dhcp --network trust --network-segment trust-az1-seg --ip-version 4 --allocation-pool start=10.52.160.14,end=10.52.160.235 --subnet-range 10.52.160.0/24 --dns-nameserver 10.10.10.10 --gateway 10.52.160.1 trust-az1

 My co-workers tell me that we also specified "--gateway" when we created our Queens subnets, but this did not cause static routes to be created. Did the handling of "--gateway" change from Queens to Train?
     On Wednesday, March 30, 2022, 01:45:52 PM EDT, Brian Haley <haleyb.dev at gmail.com> wrote:  
 
 Hi Albert,

On 3/29/22 17:04, Albert Braden wrote:
> After upgrading our kolla-ansible clusters from Queens to Train, we are seeing static routes when we create subnets. We didn’t see this in Queens. For example, in our de6 region we have a network called “trust” with 3 subnets:
> 
> Subnet                CIDR                                  Gateway
> trust-az1:            10.52.160.0/22  10.52.160.1
> trust-az2:            10.52.164.0/22  10.52.164.1
> trust-az3:            10.52.168.0/22  10.52.168.1
> 
> Each of these subnets has 2 entries under “host_routes:” that point to the other two subnets. For example, subnet trust-az1 has these two routes:
> 
> host_routes          | destination='10.52.164.0/22', gateway='10.52.160.1' |
> |                      | destination='10.52.168.0/22', gateway='10.52.160.1' |
> 
> How can we prevent these host routes from being created in Train? Do we need to change something in our config?

 From the neutron side of things, host_routes of a subnet is not 
automatically calculated and filled-in, they have to be manually added. 
So perhaps this is something kolla is doing? At least on my Yoga setup 
it is completely blank using 'openstack subnet create ...' even with 
multiple subnets on a network.

How exactly are the subnets getting created?

-Brian
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220330/0a1f32ea/attachment.htm>