similar to: re-sending outstanding controller refactoring patches after rebase

Signed-off-by: Scott Seago <sseago at redhat.com> --- src/app/controllers/storage_volume_controller.rb | 6 ++- src/app/services/storage_volume_service.rb | 60 ++++++++++++--------- 2 files changed, 39 insertions(+), 27 deletions(-) diff --git a/src/app/controllers/storage_volume_controller.rb b/src/app/controllers/storage_volume_controller.rb index b89513a..fb6bc9c 100644 ---

This patch teaches taskomatic to use the volume 'key' instead of the path from libvirt to key the volume off of in the database. This fixes the duplicate iscsi volume bug we were seeing. The issue was that libvirt changed the way they name storage volumes and included a local ID that changed each time it was attached. Note that the first run with this new patch will cause duplicate

Signed-off-by: Loiseleur Michel <mloiseleur at linagora.com> --- app/models/vm.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/app/models/vm.rb b/app/models/vm.rb index 88e0aef..0be3f89 100644 --- a/app/models/vm.rb +++ b/app/models/vm.rb @@ -27,7 +27,7 @@ class Vm < ActiveRecord::Base find(:all, :conditions=>{:state=>Task::STATE_QUEUED})

Signed-off-by: Simon COURTOIS <scourtois at linagora.com> --- src/app/controllers/vm_controller.rb | 5 ++ src/app/models/vm_task.rb | 4 +- src/app/views/vm/start.rhtml | 77 ++++++++++++++++++++++++++++++++++ src/task-omatic/taskomatic.rb | 7 +++- 4 files changed, 91 insertions(+), 2 deletions(-) create mode 100644 src/app/views/vm/start.rhtml diff

Since Ruby::Qmf moves, the .key() method does not work anymore. It forces to use a .get_attr('key') in order to get the good value. Signed-off-by: Loiseleur Michel <mloiseleur at linagora.com> --- src/task-omatic/taskomatic.rb | 15 +++++++-------- 1 files changed, 7 insertions(+), 8 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index

This resend includes the rebase, but fixes a problem I just noticed with nil/empty checks.

This is a resend of the 2-patch series from a week or so ago, needed to be rebased due to some commits on next

The following two patches should be applied in the order: * [PATCH server] Add svc_vm_actions method to VmService. * [PATCH server] Cloud UI layer to initiate actions on vms. The service layer patch should work fine on its own (and not break anything), but cloud patch relies on service being there.

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

--- src/app/views/storage/_form.rhtml | 2 ++ src/app/views/storage/_list.rhtml | 4 ++++ src/app/views/storage/_list_volumes.rhtml | 4 ++++ src/app/views/storage/show.rhtml | 4 ++++ .../views/storage_volume/_new_volume_form.rhtml | 1 + src/app/views/storage_volume/show.rhtml | 8 ++++++++ 6 files

--- src/app/views/storage/_form.rhtml | 2 ++ src/app/views/storage/_list.rhtml | 4 ++++ src/app/views/storage/_list_volumes.rhtml | 4 ++++ src/app/views/storage/show.rhtml | 4 ++++ .../views/storage_volume/_new_volume_form.rhtml | 1 + src/app/views/storage_volume/show.rhtml | 8 ++++++++ 6 files

Hello, I have a Promise EX 12-port RAID controller in my box, connected to 8 750GB disks. I have set up 2 RAID-5 devices and joined these using LVM. This is working fine. However, there is something that seems wrong.. (4-1) * 750 = 2250, but df reports the LVM volume as a mere 4.0T; /dev/mapper/storage_volume-stor 4.0T 3.6T 507G 88% /storage Shouldn't this be 4.5TB? Relevant bit of

the vm form is getting cluttered, this patch simply add collapsable sections to the form, making the 'storage' and 'network' sections collapsed by default credit goes to jayg for contributing alot to this patch in terms of simplification and cleanup --- src/app/helpers/application_helper.rb | 4 +- src/app/views/vm/_form.rhtml | 35 ++++++++++++++++++++++----------

Hi all, I am trying to figure out if you can store the definition of a directory storage pool in a custom location. This is how I create the storage pool: xmlDesc = """ <pool type='dir'> <name>guest_images_storage_pool</name> <uuid>8c79f996-cb2a-d24d-9822-ac7547ab2d01</uuid> <capacity unit='bytes'>4306780815</capacity>

Also includes a couple minor model changes to support better error reporting. This method was added so that a client could submit multiple vms to the service layer in one call and get back appropriate messages showing any failures without those failures also causing the entire call to fail, or forcing the client to implement handling (begin/rescue blocks) of these errors to continue through the

hi there, I'm following these documentations to add a file-based disk volume to a KVM guest under Centos 6.0 : http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/chap-Virtualization-Storage_Volumes.html as instructed, I created a "pool" then a "volume", file-based, e.g : mkdir /mnt/raid/kvm_pool1 virsh # pool-define-as pool1 dir - - - -

This patch creates the shell for much of what the cloud ui will become. It is focused on layout (lightly fedora themed), accessibility, and 'bookmarkability'. This layout uses no javascript (that will be used to enhance interactivity in a future patch). It also introduces the idea of using a simple table rather than the more conplex js/json we use in the admin side. Plan here is to

Previously, a pxe-booted vm would always boot to HD at next startup. Signed-off-by: Nicolas Ochem <nicolas.ochem at alcatel-lucent.com> --- src/app/controllers/vm_controller.rb | 1 + src/app/models/vm.rb | 15 +++++++++++---- src/app/views/vm/_form.rhtml | 2 +- src/task-omatic/taskomatic.rb | 13 +++++++++++-- 4 files changed, 24 insertions(+), 7

Hello group, I have an OSX 10.3.9 Server that I'm trying to back up with rsync 3.0.2. Since I didn't have any luck with the 10.3.9 patch and I do have 10.4 clients, I decided to try running the backup over AFP (Apple's file sharing protocol). I found a way to mount the AFP volume with root permissions and rsync 3.0.2 works very nicely using this on the 10.4 clients, preserving