cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edison Su <Edison...@citrix.com>
Subject RE: [VOTE] Adapting git workflow for release branches
Date Thu, 21 Aug 2014 17:18:30 GMT


> -----Original Message-----
> From: Erik Weber [mailto:terbolous@gmail.com]
> Sent: Wednesday, August 20, 2014 3:15 PM
> To: dev
> Subject: Re: [VOTE] Adapting git workflow for release branches
> 
> >
> >
> > > > There are several proposals from Citrix:
> > > > http://markmail.org/thread/c4pded5i3r22keqw
> > > > http://markmail.org/thread/xoyjw2sduenlytwm
> > >
> > > Edison, Citrix can't make proposals. Individuals do..
> > Sorry, what I am trying to say is "from people, who happen to be
> > employee from Citrix".
> >
> > > I know Citrix has an internal BVT/CI whatever you want to call it
> > system, but
> > > until it is live for the whole community I don't think there is any
> > point of
> > > discussing it.
> > >
> > > There is hardware being donated (which people on this list may not
> > > be
> > aware
> > > off), but it is not available yet, nor do we know how this hardware
> > > will
> > be
> > > managed.
> > > So right now the only apache infra we have to do CI is the current
> > jenkins
> > > setup and things like TravisCI which I have mentioned before.
> > >
> > > In any case, the threads you mention did not reach consensus or led
> > > to a vote thread. The way forward is to keep working on those
> > > threads or
> > start a
> > > VOTE thread.
> > >
> > > I am just wondering what we will VOTE on in terms of CI, since there
> > > is
> > no
> > > infra to do it yet and nobody seems to be owning this (or maybe I
> > > missed some threads).
> >
> > Ok, I got it. So right now, we don't have problem about need to have
> > CI or not, It's about how will gonna do it, right?
> > The options we have today:
> > 1.TravisCi,
> > 2. the CI donated from Citrix(I heard of that the donated hardware is
> > delayed, I mistakenly thought the hardware is already donated), 3. any
> > other hardware( I am working on a machine created on DigitalOcean,
> > $80/month, 8G memory, 4 core cpus, SSD, I want to donate it as CI
> > machine personally, if there is no other good solution) Any other
> > options?
> >
> 
> Regarding nr. 3) if hardware really is/was the issue, I'm sure there's several
> cloudstack users that would happily donate a VM or two.
> Atleast I know that I've seen several offerings, and I can say that my
> employer most likely would be able to donate additional hardware if
> necessary.
Yes, I think hardware and how to manage hardware is really an issue. If there are donation
on the 
Hardware, that will be great. 
 
> 
> The problem is that there's not really any system/routine available to take it
> into use, ie. the "CI/BVT" we're discussing is currently an internal Citrix thing,
> not a community thing.
CI/BVT has three parts:
1. The test framework. Currently, it's Marvin, it's open sourced since beginning.
2. The test cases, some of them are open sourced, some are not. The open sourced test cases
can cover basic functionality.
3. The test infrastructure: e.g. how to install hypervisors, how to manage IP address assigned
to hypervisors etc. This part, Citrix has
Some python/shell scripts to manage these, not sure the status of these code, maybe open sourced
somewhere. I think it's not the only way to manage hardware, 
Don't need to depend on Citrix's code.

So we need hardware and a layer to manage these hardware.


> 
> --
> Erik
Mime
View raw message