Bug #5371
improve consistency of networks created when importing templates and wilds
| Status: | Closed | Start date: | 09/15/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jaime Melis | % Done: | 0% | |
| Category: | vCenter | |||
| Target version: | Release 5.4.1 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 5.4 |
Description
If two templates are connected to the same network, there is no need to create more than one network, per vcenter instance.
For wild vms, with just one lease is enough.
This also affectst the pre-migrator.
Associated revisions
B #5371: Don't create a new network per template
B #5371: typo
B #5371: Don't use OPENNEBULA_MANAGED=NO for the networks
B #5371: If it's wild the AR will only be 1 lease big
B #5371: More consistent network creation behaviour
- Import Wild => create network always with 1 lease and mac
- Import Template => create network if not exists, 255 and ether
- Import Network => create network if not exists, 255 and ether
B #5371: More consistent network creation behaviour
- Import Wild => create network always with 1 lease and mac
- Import Template => create network if not exists, 255 and ether
- Import Network => create network if not exists, 255 and ether
B #5371: Don't create a new network per template
B #5371: typo
B #5371: Don't use OPENNEBULA_MANAGED=NO for the networks
B #5371: If it's wild the AR will only be 1 lease big
B #5371: More consistent network creation behaviour
- Import Wild => create network always with 1 lease and mac
- Import Template => create network if not exists, 255 and ether
- Import Network => create network if not exists, 255 and ether
B #5371: vcenter premigrator has same wild disks/nics logic
B #5371: vcenter premigrator has same wild disks/nics logic
(cherry picked from commit 09d0b9a72b9d842a53458cc06e7148023317e7a4)
History
#1
Updated by Ruben S. Montero almost 4 years ago
- Status changed from Pending to Closed
- Resolution set to fixed