I guess this could be due to differences in ReservationStrategy 'Create'
and 'Start'. Both the strategies would need a prepare, but require release
only for 'Start' reservation strategy.
Please refer to [1] for explanation of reservation strategies.
Hi Murali,
Thanks for the link. I see in that mail:
Create - IP address assigned to the NIC stays across start/stop sessions
In the case where I am not seeing a corresponding release to a prepare
call, the reservation strategy is 'Create'. However the trigger here
is destroying the VM. Should
I was hoping someone could clarify something I am seeing in
NetworkManagerImpl.java
I see that whenever we prepare a nic, we call element.prepare, regardless
of the ReservationStrategy of the nic:
