Hi, following up to CentOS Virt SIG meeting here is a quick review of the gaps we have for porting ovirt within CentOS Koji. On the manager side, in order to properly build ovirt-engine (the main package in oVirt project) we're missing several pre-requisites. We're relying on a binary packaging of jboss-as 7.1 we ship as ovirt-engine-jboss-as. So first step should be to rebuild Fedora 19 JBoss rpms within CentOS 7. We're also using maven for building ovirt-engine. A proper packaging for using koji as build system requires to re-package ovirt-engine following fedora guidelines [1]. Issue here is that we're missing lot of maven dependencies like google GWT not yet packaged in Fedora and also other dependencies available in Fedora but not in CentOS 7 like: apache-sshd >= 0.11.0 checkstyle >= 5.4 dbunit >= 2.4.8 infinispan >= 5.2.5 javapackages-local jboss-modules >= 1.1.1 maven-checkstyle-plugin >= 2.9.1 maven-jaxb2-plugin >= 0.8.1 maven-processor-plugin >= 1.3.7 openstack-java-client >= 3.0.6 openstack-java-glance-client >= 3.0.6 openstack-java-keystone-client >= 3.0.6 openstack-java-quantum-client >= 3.0.6 openstack-java-resteasy-connector >= 3.0.6 powermock-junit4 >= 1.5 quartz >= 2.1.2 snmp4j >= 2.2.2 spring-ldap >= 1.3.1 springframework-test >= 3.1.1 On the host side we've been able to build everything in koji. Some dependencies have been rebuilt from EPEL but other than that we should be fine[2]. Only blocker we have on this is qemu-kvm-rhev, we discussed about the rhev suffix during the meeting and we haven't reached an agreement yet within oVirt on how to handle it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1168605 [2] http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com