On Fri, May 19, 2017, at 02:03 PM, Kevin Benton wrote: > I split this conversation off of the "Is the pendulum swinging on PaaS > layers?" thread [1] to discuss some improvements we can make to Neutron > to > make orchestration easier. > > There are some pain points that heat has when working with the Neutron > API. > I would like to get them converted into requests for enhancements in > Neutron so the wider community is aware of them. > > Starting with the port/subnet/network relationship - it's important to > understand that IP addresses are not required on a port. > > >So knowing now that a Network is a layer-2 network segment and a Subnet > is... effectively a glorified DHCP address pool > > Yes, a Subnet controls IP address allocation as well as setting up > routing > for routers, which is why routers reference subnets instead of networks > (different routers can route for different subnets on the same network). > It > essentially dictates things related to L3 addressing and provides > information for L3 reachability.
One thing that is odd about this is when creating a router you specify the gateway information using a network which is l2 not l3. Seems like it would be more correct to use a subnet rather than a network there? Clark __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev