projects / osm / RO.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f6fbe42) | patch
Fix bug 2302: IP ranges management in Azure not working properly 12/14012/1
authoraguilard <e.dah.tid@telefonica.com>
Thu, 2 Nov 2023 16:52:56 +0000 (16:52 +0000)
committeraguilard <e.dah.tid@telefonica.com>
Mon, 13 Nov 2023 10:19:32 +0000 (12:19 +0200)
commiteef6ef54490c2fe997b872d3324bfb03f23e178a
tree7dc13e7306b2aa67a9d763e0b51fc97f31a2609ctree | snapshot
parentf6fbe42594c64f6cacfaf1798568e3ff40712240commit | 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>
(cherry picked from commit 5d27a33f4c8f6a9bc5f6ca20f844a124a5d8b223)
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