62b3d548d6
bug 8753: never release public Ip address without ensuring that all corresponding resources (PF/StaticNat/Lb rules) are cleaned up.
...
Fixed couple of other problems along:
* when expunge PF/Static nat rules as a part of vmExpunge/IpRelease process, first mark all rules as Revoke, and then send commands to the backend. Group commands by Ip address.
Before we used to do Revoke/Send per rule basis.
* When release source nat rule, make sure that corresponding vpn (if exists) is being expunged.
2011-02-28 09:21:05 -08:00
d80caf24fd
bug 8564: Changed implementation for static nat rules. Now we use separate interfaces instead of PortForwardingRules interfaces.
...
status 8564: resolved fixed
2011-02-15 10:45:28 -08:00
6544820e74
Moved networkRestart to the NetworkManager as it's up to the manager (not network elements) to decide what to do on restart (IpAssoc/ruleApply/etc..)
2011-02-01 12:16:19 -08:00
f6f8a35c75
bug 8251: introduced "id" field for public IP address. In the DB id is a primary key in user_ip_address table; ip_address and source_network_id is a composite key
...
status 8251: resolved fixed
2011-02-01 12:16:18 -08:00
dfaf7c4c5d
Remove vm from Load Balancers when vm is Expunged. Added more logging to vm expunge process
2010-12-23 16:23:51 -08:00
0049c74a5e
1) Different format for LoadBalancerCommand.
...
2) When apply lb rule for domR, resend all lb rules belonging to the lb network
2010-12-17 09:37:13 -08:00
223688d0bf
Port forwarding rules and load balancing rules rewrite
2010-12-03 08:48:02 -08:00
alena
Alex Huang