-1 on this. New features really should be across the board for the Hypervisors. Part of the thing that distinguishes ACS is it's support across Xen / VMware / KVM. Do we really want to start getting in the habit of pushing forward new features that are not across the fully functional hypervisors?
I agree with Outback this also will start to affect the Xen/XCP community by basically setting them apart and out on what a lot of people see as a major feature. I think it sets a really bad precedent. If it was Hyper-V which is not fully functional and not a major feature-set right now, I would be +1 on this. MHO Matt On 5/20/13 4:15 PM, "Chip Childers" <chip.child...@sungard.com> wrote: >All, > >As discussed on another thread [1], we identified a bug >(CLOUDSTACK-2492) in the current 3.x system VMs, where the System VMs >are not configured to sync their time with either the host HV or an NTP >service. That bug affects the system VMs for all three primary HVs (KVM, >Xen and vSphere). Patches have been committed addressing vSphere and >KVM. It appears that a correction for Xen would require the re-build of >a system VM image and a full round of regression testing that image. > >Given that the discussion thread has not resulted in a consensus on this >issue, I unfortunately believe that the only path forward is to call for >a formal VOTE. > >Please respond with one of the following: > >+1: proceed with 4.1 without the Xen portion of CLOUDSTACK-2492 being >resolved >+0: don't care one way or the other >-1: do *not* proceed with any further 4.1 release candidates until >CLOUDSTACK-2492 has been fully resolved > >-chip > >[1] http://markmail.org/message/rw7vciq3r33biasb
