----- Original Message ----- Sounds like an important project, that will bring up the quality of the sdk. I'm missing some info about those tests: 1. How much resources will it consume? (running all the tests) 2. Any special requirement for the sdk tests? (engine up & running?) 3. What sort of Jenkins integration we're looking for? How the output looks like? Ofer.

On Thu, 2012-04-19 at 14:35 +0300, Itamar Heim wrote: I'm ok with the new repo, but couldn't it be included as a directory of the ovirt-engine-sdk project? If that doesn't make sense in this case, then it's fine. Agree that no incubation would be needed. Mike

On 19/04/12 15:41, Itamar Heim wrote: +1 on Sub-project in a separate repo, as this has complete dependency in ovirt-engine-sdk, yet the other way around isn't so. -- /d "The answer, my friend, is blowing in the wind" --Bob Dylan, Blowin' in the Wind (1963)

On Thu, 2012-04-19 at 15:41 +0300, Itamar Heim wrote: Ok, just needed to ask the question. ACK from me. Mike

On Thu, 2012-04-19 at 08:26 -0400, Eyal Edri wrote: I'm adding hardware for jenkins to the agenda for the weekly meeting next week. Mike

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/19/2012 12:12 PM, Mike Burns wrote: So we're a bit stuck in a circle, because our current hosting for Jenkins is sub-par due to AIUI EC2 not being the best environment for continuous integration testing. I'd like to bring more on-par resources from Red Hat, but so far the ones we have gotten access to live inside of the private network. I don't yet see anything becoming available from Red Hat for external usage until after June 2012. I wouldn't be surprised if that situation were similar with other people and their supporting organizations or other private hosting situation. External hosting is sometimes more precious than internal labs. I was wondering if it is worth it for the short-term to do CI runs on internal networks and publish just the results externally? Functionally this is the same for some people, but for anyone who wants to help with Infrastructure, it's a closed door. (There may be other considerations to having Jenkins internally that I'm not aware of.) But it might be worth doing for a short period - six months? - to get us what we need on the development side. Itamar reports to me that performance with the EC2 hosts is 3x slower than what they get in their lab. That's a lot of wasted CI time. Of course, Infrastructure supporting that idea means that if anyone has private machines they want to use as Jenkins hosts, we'd want to hook them up with the same situation (somehow.) Ideally, we'll get more hosts provided by community members and supporters, but currently we don't have that. I would want to set a target end-date to return Jenkins et al to external-only hosting so the Infrastructure team can be a full participant. My original goal in setting up Infrastructure as fully open was based on my experience in other projects, but those are already established projects with donated hosting by many providers and none of them started out with that much external hosting. Realistically, this may be something we need to work toward. What do all of you think? BTW, if anyone knows KVM using hosting providers who want to support oVirt development, getting us physical hosts and virtual machines would be a *great* way to help. We can talk with the Board about adding them to the sponsors page. - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/23/2012 11:33 PM, Itamar Heim wrote: Itamar and I have been having some progress internally on getting hosts that may be able to be exposed externally so we can have shared community infrastructure. Based on that and the immediate need, I'd like us to start allowing Itamar's team to use whatever they have internally to support development, with these understandings: * Publish all results ASAP publicly, as per usual. * Move the workloads externally ASAP when we can. * Look for the future of how we want to handle enabling Jenkins servers to be used on internal networks so oVirt members can use more readily available internal hosts for infrastructure that doesn't require or benefit from an open collaboration. Basically, it makes sense to me that if we have a standard set of workloads that can be run on any instance, there is no reason anyone can't commit to doing that on infrastructure they run themselves. That is different from the actual participation components that should be run entirely externally. The project needs to have 100% r/w access to all of the online components that make up the project, but that doesn't have to include CI servers running a standard workload on an open source stack. - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/07/2012 08:28 PM, Itamar Heim wrote: OK, so far this discussion has been you and I agreeing on how to do things, with no other objections. Unless there is an objection now :) I'm going to say our +1s resolve the question in this thread. Go ahead and run Jenkins slaves internally, etc., and just report back out to this list (and write up on the wiki) as things are figured out and enacted. Does that work for you? - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41