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
b23df4c7e3
Fixed zoneIsConfiguredForExternalNetworking method
2011-01-28 10:56:25 -08:00
c7bccd0b0f
Added method to check if a zone is configured for external networking.
2011-01-28 10:42:04 -08:00
52dd679d95
bug 8185: fixed java part of password reset feature. There are still changes needed in backend scripts (bugs 8253 and 8254 are filed separately)
...
status 8185: resolved fixed
2011-01-27 17:24:09 -08:00
77e89b72ca
bug 8187: retreive DNS information from DataCenter instead of resetting it for the network. After the DNS is reset, all networks in the zone have to be restarted. Console proxy and secondary vm should be restarted too.
...
status 8187: resolved fixed
2011-01-26 19:08:56 -08:00
0e4196448a
bug 7811: Start domR/Dhcp if it's not running when do userVmReboot
...
status 7811: resolved fixed
Other fixes:
* vmExpunge: cleanup LB/PF rules after vm was marked as Expunging in the DB to avoid the situation when user recovers a vm in the middle of expunge job.
2011-01-24 17:04:23 -08:00
fc33ef2be2
Removed several unused fields after the refactoring
2011-01-24 16:18:40 -08:00
6304a92c23
bug 7881: fixed publicIpAllocation to an account.
...
status 7881: resolved fixed
Also fixed the issue with account delete when nonSourceNat ip addresses were not being released
2011-01-24 10:03:18 -08:00
632d3c67f1
bug 6689: release source nat ip address as a part of domR/dhcp destroy
...
status 6689: resolved fixed
Changes to destroyNetwork process. Here are the steps:
* shutdown network - shutdowns all network elements (domRs/Dhcps)
* delete network - destroy all network elements, cleanup network's resources (vlans, ip ranges), mark network with Destroyed state and set Removed field
2011-01-18 19:31:04 -08:00
f20c725827
bug 8062: fixed releasing vnet when corresponding network is shutdown. Used to happen because reservation_id for the network didn't match reservation_id for the vnet, and cleanup thread couldn't find vnet to cleanup
...
status 8062: resolved fixed
Also set broadcastUri to null when shutdown the corresponding network.
2011-01-18 13:25:04 -08:00
42950f2e8b
migration complete
2011-01-14 15:12:13 -08:00
5dfe399c1a
bug 7803: introduces new parameter "is_default" for the network. DeployVm requires 1 default network to be specified, other networks (if any) have to be secondary
...
status 7803: resolved fixed
Fix overview:
1) Parameter "isDefault" should be defined as a part of createNetwork
* Virtual network is always default
* Parameter can be specified only for DirectNetwork
* Once parameter is set, there is no way to change it as we don't provide updateNetwork command.
2) Added isDefault parameter to listNetworks command so you can sort by that.
3) DeployVmCmd:
* at least one default network should be set
* if more than 1 default network is set - throw an error
4) Return isDefault information as a part of Nic object for the vm response in deploy/stop/start/listVm
2011-01-11 14:22:26 -08:00
d0687f663f
bug 7863: fixed router cleanup thread
...
status 7863: resolved fixed
Router cleanp thread is fixed, here is functionality description:
* Runs every "router.cleanup.interval" period of time (1 day by default)
* Stops only domRs running in Advance zone
* Thread Flow:
- gets all Running domRs/dhcps, get their networks, select network that
has to be checked (see criteria below):
- checks that there is only one nic in the op_networks table for the
network, and this nic belongs to domR/dhcp
- Stops domR/dhcp
* Criteria to choose the network:
- Network has to be non-system.
- Network should be one of the following: Guest Virtual (TrafficType=Guest; GuestType=Virtual); Direct Tagged (TrafficType=Public; GuestType=Direct)
Couple of other fixes:
* Added isShared parameter to listNetworks command
* Moved guestType from NetworkOffering to Network
2011-01-07 16:57:47 -08:00
386d4a540d
merge changes
2011-01-07 13:46:20 -08:00
2e29f21e5a
changes for injectors
2011-01-07 13:42:43 -08:00
4ec3bc5865
bug 7244: delete corresponding untagged pod vlan ranges when pod is deleted
...
status 7244: resolved fixed
2011-01-06 16:16:09 -08:00
916b516d13
bug 7878: Fixed Basic zone functionality - uservm/systemvm/domR start
...
status 7878: resolved fixed
2011-01-06 15:44:13 -08:00
c74fd529be
bug 7611: get directPodBased default network when deploy vm with no networkId specified
...
status 7611: resolved fixed
2011-01-04 18:43:03 -08:00
4eba6d10d7
Moved State into VirtualMachine like other States of objects
2011-01-04 15:01:34 -08:00
da4ed648ac
consolidated all of the vm destroy, cleanup and account cleanup.
2010-12-30 05:46:54 -08:00
544fa7ff1b
remote access vpn, user ip address changes
2010-12-29 09:32:54 -08:00
88afdb3313
Made NetworkId parameter required for Vlan, modified DB schema and corresponding Managers' methods. For Virtual and Direct untagged vlan networkId is got from default system Public/Public-DirectPodBased networks accordingly
2010-12-28 15:15:24 -08:00
ec9260ce62
bug 7619: Added list of Capabilities parameter for Network
...
status 7619: resolved fixed
2010-12-22 11:05:31 -08:00
356526db83
Changed exception code to give the scope of the problem
2010-12-21 03:54:30 -08:00
ca92c28e0e
Fixed setupNetwork command to use vlan tag instead of vlan dbId.
...
Changed LoadBalancerConfigCommand to use Array data structrue instead of List as list is not handled well by gson.
2010-12-17 12:07:06 -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
c1db5b6fc0
1) Fixed associate/disassociateIP address commands. The procedure is changed from 2.1, right now on single ipAssoc command we get a new ip and reapply all exising ip associations.
...
2) Added restartNetwork API command. Currently the command reapplies ip addresses for the network. TODO - reapply PF/LB rules and restart the domR.
2010-12-15 11:39:30 -08:00
68932929fb
Changes to how public ip addresses are allocated
2010-12-10 08:38:20 -08:00
04f3a4baa9
bug 7441: fix ipassoc when starting router
...
status 7441: resolved fixed
2010-12-09 20:25:27 -08:00
157156dd35
1)Introduced new Network Guru - used for direct tagged network.
...
2)Made vm start with multiple networks
2010-12-09 11:12:29 -08:00
2c42ebbf71
ip assoc working
2010-12-08 09:03:34 -08:00
f794abfdef
ip addresses are now separated from domR
2010-12-08 09:03:34 -08:00
f147bf5f94
start vm not working again
2010-12-06 14:17:53 -08:00
fcdd20ca06
more checkin
2010-12-06 14:17:53 -08:00
daa9add158
removed router stuff from network manager
2010-12-04 17:32:31 -08:00
150d684e05
1) isShared attribute belongs to Network now, not NetworkOffering
...
2) Added list by networkId support to listVirtualMachines command.
3) Implemented search by zoneId in listNetworks command
2010-12-03 19:07:08 -08:00
223688d0bf
Port forwarding rules and load balancing rules rewrite
2010-12-03 08:48:02 -08:00
f8a687ab23
1) Implemented create/list/deleteNetworkOffering create/delete/listNetwork APIs.
...
2) Added networkIds parameter to deployVMCmd - accepts list of networks ids separated by coma.
3) Changed domainRouter/systemVm/userVm response to return list of Nics associated with the vm.
2010-12-02 19:30:17 -08:00
1e44925564
api refactoring
2010-11-21 12:00:21 -08:00
5b4a6f27db
Changed networkconfigurations to network as per Sheng's suggestion
2010-11-19 15:44:42 -08:00
394554770e
Enforce user limit on number of vpn users
2010-11-18 18:38:29 -08:00
a73e3dc9ac
new networking can be set by use.new.networking
2010-11-17 17:51:17 -08:00
31e17b907d
bug 6971: ensure no conflicts with portforwarding rules for vpn udp ports
...
also, do not open up port 1701 -- only used on ppp interface not public interface
also clean up password generator, make it easier to use and more secure
moved some constants to NetUtils
heuristic to determine if an ip is one-to-one nat'ted
2010-11-17 15:32:50 -08:00
d5ab597fcf
bug 6474,6475: porting over the expunge fixes for port forwarding rules to 2.2
...
status 6474,6475: resolved fixed
2010-11-15 17:33:05 -08:00
05bbd35860
resolving the network manager merge conflict
2010-11-11 13:13:04 -08:00
1faaba8fb0
fixed a corner case; also changed the commands to be async and changed the method signatures to conform with the master refactor
2010-11-11 13:07:26 -08:00
26b75fc05d
this is a good point to check the code in; have completed a part of the enhancement's code; with create and delete ip forwarding rule commands and the skeleton for port to rule map with associated table
2010-11-11 13:07:26 -08:00
e5ca5dddf9
renaming the ip forwarding commands to port forwarding commands, and beginning to work on Keshav's request to modify the current 1-1 NAT to be compatible with the Amazon apis
2010-11-11 13:07:26 -08:00
94250c1330
committing to update
2010-11-11 12:53:19 -08:00
86e83bc4bd
Created new response objects for userVm/domainRouter/systemVm that going to be used by API after network refactorig is in place.
2010-11-11 10:43:18 -08:00
alena
keshav
Alex Huang
edison
Chiradeep Vittal
abhishek