On 6/28/12 2:41 AM, "Hugo Trippaers" <htrippa...@schubergphilis.com> wrote:
>Heya, > >While setting up a new system for some testing I noticed that the system >default networks are created from the createZone call in >ConfigurationManagerImpl. However at this point the physical network is >not yet created for these networks. It seems not to be a problem as >physical network id are is to null in the database, but I wonder if it is >ok to have the default networks not bound to a physical network? > >Also I did not see this behavior when running an earlier version (from >github) > > >Cheers, > >Hugo > This kind of behavior was there since 2.2.x when networks came in place - all default networks are being added as a part of createZone command. It's ok for system networks to not being bound explicitly in the DB. We do the bounding based on the following (once physical network is created): * Only one physical network in the zone can support traffic types of system networks - Public/Storage/Management * when we need to locate corresponding physical network for the system network, we locate physical network by zoneId + trafficType (this combination is unique for traffic types Public/Storage/Management) * if traffic type is not supported by any of the physical networks in the zone, the network can't be used (for example, the Basic zone w/o EIP/ELB - there is no support for Public traffic type) -Alena.
