You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New services get new subnets, which means the IPs change, which breaks the interconnection between containers -> every instance should get the same subnets separated by VLANs -> pop only once per service not per service_instance
VLAN isolation seems to work properly for E-LANs
collisions of VLANs possible? No -> each link/land gets a new one. Up to 4096.
Issue: Right now we can only deploy one instance per service, because the container names (and other things) will collide.
Solution: Have a
short_service_instance_id
orSSIID
and post-fix container names, e.g.,vnf_id.vdu_id.SSIID
with it.Problem (s):
0
if only one service is running.How to test:
Corner cases to think of:
Tests before merge:
Attention: Commit already exists; amend.
The text was updated successfully, but these errors were encountered: