I've seen a thread where OV is discussed as a feature test platform in the same vein as FC. That raises the question, for me at least, as to whether or not I should deploy OV in a production environment where it will host continuous build VMs in support of Agile Teams of developers. It looks really good but not if a new version comes out every six months or so and I have to do a reinstall. If it is a new feature platform, will easy (spelled "single-click" or something close to it) upgrading be supported?

Thanx, Garth

Thanx for the response. One more follow-up question: I'm currently only running three ESXi 4.1 boxes (one large 710, two small 2950s) so VDSM is a bit overkill. Is there a plan for a simpler "VDSM Lite" on the horizon that would make more sense for an installation with only a few nodes? That would be attractive for me. Again, Thanx for the response... Garth

On 03/28/2012 09:59 AM, Ofer Schreiber wrote: > > ----- Original Message ----- >> I've seen a thread where OV is discussed as a feature test >> platform >> in >> the same vein as FC. That raises the question, for me at least, as >> to >> whether or not I should deploy OV in a production environment >> where >> it >> will host continuous build VMs in support of Agile Teams of >> developers. >> It looks really good but not if a new version comes out every six >> months >> or so and I have to do a reinstall. If it is a new feature >> platform, >> will easy (spelled "single-click" or something close to it) >> upgrading >> be >> supported? > I assume that upgrade won't be perfect at the first couple of > versions, as we're trying to stabilize the project. > A "single-click" upgrade is already implemented upstream > (engine-upgrade utility), but it relays very much on the platform. > if the platform will be changed (moving to official JBoss rpms for > an example), the upgrade process might involve couple of manual > steps. > > Ofer Schreiber > oVirt Release Manager > > >> Thanx, >> Garth

No problems, really, but then I've only set up one node and not yet built a VM on the node. Let's just say that connecting to the VDSM site offers a lot of options that I don't think I'll ever need/use. It's more that I've not played with VDSM nearly as much as I have Virtual Machine Manager or ProxMox so I'm just not familiar with it. So, no problems or complaints. I just need to spend more time with it. Neat stuff, tho, and fun to play with. :-)

Thanx, Garth On 03/29/2012 04:27 AM, Ofer Schreiber wrote: > > ----- Original Message ----- >> Thanx for the response. One more follow-up question: I'm currently >> only >> running three ESXi 4.1 boxes (one large 710, two small 2950s) so >> VDSM >> is >> a bit overkill. Is there a plan for a simpler "VDSM Lite" on the >> horizon >> that would make more sense for an installation with only a few >> nodes? >> That would be attractive for me. >> >> Again, Thanx for the response... >> Garth > Well, VDSM does support hundreds of hosts, but it work well in a > small environments. (my testing environment contains normally up > to 5 hosts, so you have nothing to worry about.) > > There are no plans for a "VDSM Lite", but I'd like to hear why the > current VDSM is such a problem for you. > > Ofer. > > >> On 03/28/2012 09:59 AM, Ofer Schreiber wrote: >>> ----- Original Message ----- >>>> I've seen a thread where OV is discussed as a feature test >>>> platform >>>> in >>>> the same vein as FC. That raises the question, for me at least, >>>> as >>>> to >>>> whether or not I should deploy OV in a production environment >>>> where >>>> it >>>> will host continuous build VMs in support of Agile Teams of >>>> developers. >>>> It looks really good but not if a new version comes out every >>>> six >>>> months >>>> or so and I have to do a reinstall. If it is a new feature >>>> platform, >>>> will easy (spelled "single-click" or something close to it) >>>> upgrading >>>> be >>>> supported? >>> I assume that upgrade won't be perfect at the first couple of >>> versions, as we're trying to stabilize the project. >>> A "single-click" upgrade is already implemented upstream >>> (engine-upgrade utility), but it relays very much on the >>> platform. >>> if the platform will be changed (moving to official JBoss rpms >>> for >>> an example), the upgrade process might involve couple of manual >>> steps. >>> >>> Ofer Schreiber >>> oVirt Release Manager >>> >>> >>>> Thanx, >>>> Garth