projects / osm / RO.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6c7318f) | patch
Fix bug 2302: IP ranges management in Azure not working properly 85/13985/4
authoraguilard <e.dah.tid@telefonica.com>
Thu, 2 Nov 2023 16:52:56 +0000 (16:52 +0000)
committeraguilard <e.dah.tid@telefonica.com>
Mon, 6 Nov 2023 07:29:55 +0000 (07:29 +0000)
commit5d27a33f4c8f6a9bc5f6ca20f844a124a5d8b223
treecff46f9f4d20e27582d444bddf3d1d253b3bc68btree | snapshot
parent6c7318f4ee720e17a8a6e95dc4ac0c551ee5da32commit | diff
Fix bug 2302: IP ranges management in Azure not working properly

OSM uses a specific vnet to create NS or VNF subnets when instantiating on
Azure. The vnets allow more than one address prefix, but RO only try to
allocate new subnets in the range defined in first place, ignoring the rest.

Change-Id: I9792caf2a468e60b6762567a9b4a90d0f1646b39
Signed-off-by: aguilard <e.dah.tid@telefonica.com>
RO-VIM-azure/osm_rovim_azure/vimconn_azure.py diff | blob | history
releasenotes/notes/fix_bug_2302-3432828f06200186.yaml [new file with mode: 0644] blob