<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 February 2016 at 20:01, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org" target="_blank">mail-lists@karan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Some of us met at Devconf for a conversation around how best the<br>
CentOS infra might be used within the Gluster projects. Here is a<br>
quick catchup from that meeting, and to further encourate conversation<br>
around the topic.<br>
<br>
Meeting attended by:<br>
- Michael Schearer<br>
- Amye Scavarda<br>
- Humble Chirammal<br>
- Kaleb Keithley<br>
- Niels de Vos<br>
- Jim Perrim ( CentOS )<br>
- Karanbir Singh ( CentOS )<br>
<br>
The existing gluster devel workflow was established as :<br>
- Upstream dev work happens in git<br>
- Gerrit queues are used to manage the content / contributor flow<br>
- Jenkins is used as the orchestration tool to validate contributions<br>
+ Jenkins slaves are deployed against a central Jenkins Server<br>
+ each Jenkins slave represents a role or distro or test req<br>
+ Jenkins slaves are run both locally, as well as in<br>
RackSpace sponsored Cloud Instances<br>
+ Packaging is something that may or maynot be tested ( some<br>
projects do, others dont )<br>
- Release Managers own the cutoff / feature specs<br>
+ Content of each release<br>
+ Documentation<br>
+ Releases are not executed in packaged paylogs<br>
- Packaging team ( or folks from dev/release teams )<br>
+ Local set of rpms done from <a href="http://gluster.org" rel="noreferrer" target="_blank">gluster.org</a><br>
+ Liase with delivery upstreams / distros for packaging in their space<br>
<br>
We established that there are 2 major points of concern at this time.<br>
1) Jenkins and Gerrit self hosted are flaky and need unreasonable amount<br>
of real time effort to keep running<br>
2) Being able to test in real world deployment scenarios is hard.<br>
<br>
The CentOS Project curates a build and test infrastructure that is open<br>
to projects like Gluster,<br>
who have a SIG presence and have a user story in the CentOS Ecosystem.<br>
We feel being able to help<br>
the Gluster project is key for us. Added to that, we can also use the<br>
Gluster artifacts and expose<br>
them to related layered projects who have a dependancy on Gluster's<br>
projects directly ( eg. ovirt,<br>
openstack etc ), in the same infrastructure.<br>
<br>
Therefore I would like to welcome the Gluster project to come and use<br>
our Jenkins instance at <a href="https://ci.centos.org/" rel="noreferrer" target="_blank">https://ci.centos.org/</a> and use the downstream<br>
testing + release mechanics we have in the project. I also feel we are<br>
able to get this done with little impact to the larger developer<br>
expectations in the Gluster projects. Some of the points highlighed:<br>
- Self hosted Gerrit should move to Gerrithub.io!<br>
- Are all the needed plugins available on Gerrithub ?<br>
+ if not, can an easy compromise be found ?<br>
- Will the existing history migrate to Gerrithub ?<br>
- Developer discipline will need to be established to negate the impact<br>
of duplicate / redundant identities ( same person multi email add etc )<br>
<br>
In a followup meeting, Brian Stinson ( CentOS Team ) spent<br>
time with MS ( Gluster QE ) to explain the flow of how<br>
<a href="http://ci.centos.org" rel="noreferrer" target="_blank">ci.centos.org</a> is setup, how tests can be depoyed, and results<br>
collected, notifications run and what the expectations would be.<br></blockquote><div><br></div><div>I am in the process of setting up a jenkins job and currently trying for a dry run without the jenkins trigger. I will keep the list updated with the results of the same.</div><div><br></div><div>Best Regards,</div><div>Vishwanath</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
There are some highlights from the centos infra : we have an automated,<br>
baremetal driven test infra. That allows multinode deployments, scale<br>
out testing. We are also going to have a cloud native test infra in the<br>
near term, allowing for cloud workload testing - again from a user and<br>
developer perspective. The resource limits, while they do exist, are<br>
liberal and in many cases, negotiable. All of this runs as a service to<br>
you guys, in the gluster project, so you can focus on writing awesome<br>
storage code, let us run the Jenkins.<br>
<br>
We also established that there are some machines waiting bring up in the<br>
Community Cage - depending on how the Gluster project can use them or<br>
not, we would welcome including them in the larger CentOS community side<br>
pool, ensuring they get used well.<br>
<br>
Brian, Jim and I will be in the Bangalore office on the 3rd<br>
and 4th of March. Brian has offered to run a demo and face<br>
to face onboarding process for the Gluster team in the office<br>
on the 3rd in the afternoon, should this be seen as valuable.<br>
<br>
CentOS infra is deployed, in production now. We can start bringing jobs<br>
over right away, to suite your requirements / release timelines.<br>
<br>
Regards<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Karanbir Singh<br>
+44-207-0999389 | <a href="http://www.karan.org/" rel="noreferrer" target="_blank">http://www.karan.org/</a> | <a href="http://twitter.com/kbsingh" rel="noreferrer" target="_blank">twitter.com/kbsingh</a><br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc" rel="noreferrer" target="_blank">http://www.karan.org/publickey.asc</a><br>
_______________________________________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org">Gluster-infra@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-infra" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-infra</a><br>
</font></span></blockquote></div><br></div></div>