Last year, use case 4 was discussed, some network related requirements were
* global view for tenant level IP address / mac address space management
* If a tenant has networks in multiple region, and these networks are
routable (for example, connected with VPN), then, IP address may be duplicated.
Need a global view for IP address space management
* If IP v4 used, this issue needs to be considered. For IPv6, it should not
be a problem. IR - disagree with this statement. This requirement is important
not just for prevention of duplicate address.
* For security and other reasons it's important to know which IP Addresses
(IPv4 and IPv6) are used in which region.
* Can we also extend such requirement to MAC address tracking?
* Can we also extend such requirement to mapping for floating and public IP
* A service to clone security groups across regions
* No appropriate service to security groups across multiple region if the
tenant has resources distributed, has to set the security groups in different
And during the discussion thread with netready, one more issue identified
* VxLAN pool cross site management for VxLAN segmentation allocation
All these issues needs to be addressed, we can discuss them together.
Tricircle( now Tricircle team is working on the cleaning to make Tricircle
dedicated for networking automation across Neutron, mentioned below) could be
the reference, the design blueprint has just been updated for your reference:
local network and shared VLAN network and L3 has been implemented in Newton
release. Of course, in NFV area, L2 networking should be enough in most
And the spec for Tricircle Local Neutron Plugin is in review:
Chaoyi Huang (joehuang)
Sent: 09 September 2016 16:59
To: Ashish singh; opnfv-tech-discuss; caizhiyuan (A); Meimei; Sama, Malla
Reddy; Zhipeng Huang; Dimitri Mazmanov; Ashish Singh7
Subject: RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach
I think sync itself (if excluding the remote sec-group) is not complex, the
complexity is to ensure the rules set in different region of Neutron will not
conflict with each other. Otherwise, it'll become mess.
So I agree with you "We must use neutron to perform all our operations as with
neutron we have total control over it." (Is my understanding correct?)
That's the way of Tricircle(please forgive me to explain a little: Tricircle
now is only a project about networking automation across Neutron. And the
Nova/Cinder API-Gateway part will be moved to Trio2o, a new created project:
the SEG sync has been implemented in the Tricircle, and we are now doing the
tricircle splitting and cleaning.
If we implement seg sync in Kingbird, we have to write lots of duplicated code
which has already done in Neutron, for example, SEG CRUD, rule CRUD,
validation, rule checking, default rule management, etc.
From: Ashish singh [ashishsingh...@gmail.com]
Sent: 08 September 2016 23:57
To: opnfv-tech-discuss; caizhiyuan (A); Meimei; Sama, Malla Reddy; Zhipeng
Huang; Ashish singh; Dimitri Mazmanov; joehuang; Ashish Singh7
Subject: [opnfv-tech-discuss][multisite] Secgroup syncing Approach
I have drafted a basic approach for security group synching in release D and it
is as follows.
- Get list of secgroups with rules for a tenant from all the regions which do
not have remote group references(currently, we ignore remote secgroup
references as there can be lot nested dependencies).
- Traverse each region and do the following
- Get the list of secgroup which are present in all the regions except
the current region, These are the secgroups which we need to sync in current
region: say it GRP_TO_BE_SYNCED
- There can be case where the secgroup from GRP_TO_BE_SYNCED may have
the same rules as the secgroup in current region(If not initially but which
will obviously happen after a sync job).
- Traverse through the GRP_TO_BE_SYNCED and check if there are such
secgroups(rules overlapping groups), if there, ignore it. After this filtering,
the remaining secgroup will be the final list of secgroup which should be
created for the current region.
- Create the secgroup with the final list of secgroups in the region.
- Repeat the process for all the tenant in batches.
The default security group is not syned, as I feel region specific default
secgroup has to there in each region.
We must use neutron to perform all our operations as with neutron we have total
control over it.
For creating a security group we need the following information
The owner tenant ID.
Description of security group rule.
Direction of traffic: ingress/egress.
--protocol PROTOCOL Protocol of packet. Allowed values are [icmp, icmpv6,
tcp, udp] and integer representations [0-255]
Starting port range. For ICMP it is type.
--port-range-max PORT_RANGE_MAX Ending port range. For ICMP it is code.
CIDR to match on.
We have all these details with us available.
Let us take this forward, Please review/comment.
opnfv-tech-discuss mailing list