Update on RHEV-M going open source
Following the post yesterday on RHEV-M going open source, I contacted Red Hat directly to confirm and find out more information about RHEV-M’s roadmap for release under an open source license. Red Hat has confirmed that RHEV-M will be released under an open source license in the future.
Here’s what I was able to confirm. Currently, work Is under way to port RHEV-M from C# to java and to remove all windows specific dependencies and libraries. Red Hat will be leveraging JBoss as part of the move to java ( which is almost expected seeing that it will be java ). The intention is to support multiple database backends eventually via hibernate, whether open source or proprietary, so you will be able to use Microsoft SQL server or postgresql for example. The current requirement for using Active Directory will be opened up so that you will be able to use either Active Directory or LDAP. It will be sometime before the port is completed and it is still in the very early stages. The next release of RHEV-M, which is currently in beta, will still run under windows.
There’s currently an open source project hosted by Red Hat for developing a REST-based API integration layer for RHEV-M that you can find out more about at the following link.
https://fedorahosted.org/rhevm-api/
Do you think releasing RHEV-M under an open source license will help expand KVM adoption? Looking forward to your comments.
- Haydn Solomon's blog
- 13970 reads
- Email this page
Comments
Very impressive! So what does
Friday, May 14, 2010 - 20:08 LouiseVery impressive!
So what does JBoss bring to the table? Is JBoss a library so you don't have to program every thing yourself?
Re: very impressive
Friday, May 14, 2010 - 21:17 Haydn SolomonLouise
Jboss is open source middleware software written in java. As you probably know, java makes it cross platform. It has reusable components as well which will help with development speed through code reuse. It is also scalable and extensible. Apart from all of this, the original company that developed jboss was acquired by Red Hat. You can find out more about jboss at www.jboss.org.
@Haydn I see. Looks like
Sunday, May 16, 2010 - 20:59 Louise@Haydn
I see. Looks like JBoss is exceeding useful for rapid Java development!
Danger, Will Robinson!
Wednesday, March 2, 2011 - 21:10 Anonymous (not verified)After weeks of work, including several hours working with Red Hat, I can only say "Run, Forrest, Run!"
We are reverting to kvm and RHEL. RHEV might be ready for prime time eventually, but it's currently the Windows ME of the Linux community. I strongly recommend AGAINST this solution.
Based on my experience with VMware ESX, Citrix XEN, KVM, Ubuntu Enterprise Cloud and Virtual Iron, I can say that the current RHEV experience (especially the single point-of-failure for its manager) is the worst possible experience in virtualization I have encountered in nearly 20 years of IT.
Red Hat needs to consider the following:
(1) LOSE WINDOWS! RHEV-M should be a RHEL-based system if not its own stand-alone system.
(2) Build some redundancy into RHEV-M! There should be some level of redundancy in RHEV-M that allows high-availability of this critical piece of infrastructure during a disaster.
(3) Add support for bonding in the RHEV-H setup utility. I am still not sure how someone is supposed to create bonds efficiently in this mess. Using RHEV-M for this was hit-and-miss. I understand that others on IRC had the same issue.
(4) Add GFS support to the storage options. NFS, iSCSI and FC is not adequate.
(5) Revise documentation to provide for a checklist to be used during deployment.
(6) Improve support training. Currently the support experience involved too many people looking at the issue and responding with different and sometimes conflicting courses of action. This wealth of "work arounds" suggests that the feedback loop from field engineers back to the developer teams is broken. Underlying problems are not being addressed and/or communicated effectively.
Post new comment