search for: network_services

redux patchset permitting a vm to be associated with multiple networks and vice-versa. updated patchset so as to be applicable against current oVirt server HEAD these patches may be applied in any order, they all need to be pushed together

This patchset contains changes to the ovirt server frontend, backend, and tests components, permitting vms to be associated with multiple networks and vice versa. Also included are two patches which are required for the frontend bits; a patch adding collapsable sections to the vm form, which in itself depends on the second patch that provides default values for the cpu and memory vm table fields

...m aware it's not ideal in terms of security, but it's been running in our local school since 2010, and it just works. The current setup is based on Slackware Linux on both server and desktop clients. Here's the relevant documentation (which I wrote): http://docs.slackware.com/howtos:network_services:roaming_profiles BTW, the first two years this solution worked perfectly with CentOS 5.x on the server and on the desktop clients. I'm currently migrating from Slackware to CentOS, and I'm looking for a "business-grade" replacement of this more or less obsolete configuration....

There's still room for additional refactoring as we may want to eventually split out nic, bonding, and ip address manipulation into their own controller/svc module, but that would be a much more extensive redesign than we want to deal with for the overall service layer creation refactoring. Signed-off-by: Scott Seago <sseago at redhat.com> --- src/app/controllers/network_controller.rb

- db, model, service, controller, and view changes - many tests additions - various fixes / cleanup to get things working depends on my last two (still unacked) patches: - add collapsable sections to vm form - provide default vm allocated cpu and memory values ovirt-agent might need to be updated to work with the changes --- src/app/controllers/pool_controller.rb | 2 +-