Hello,
What types of tests does the CentOS Development Team do for software in its repositories?
Where does it get its test catalog from?
I want to create a testing process which is equal to if not more rigorous that the CentOS process for any third party software we use.
For example, if I install the php-mysqlnd package from the Remi repository, I want to test it just as carefully as the php-mysql package has been tested before I get it from the CentOS repository.
If somebody can point me in the right direction I'd appreciate it.
Thanks!
David
P.S. I've moved this question from the centos thread to the centos-devel thread as Sven suggested.
Original post: http://lists.centos.org/pipermail/centos/2015-January/149091.html
Hi all,
Many of the folks involved in Project Atomic are going to be traveling
to FOSDEM or involved in other activities related to FOSDEM next week.
It makes sense to skip next week's meeting, because I doubt many of us
would be able to actually attend.
However, we do have a few action items from this week's meeting [1]:
imcleod
imcleod to request git.centos.org credentials, work on acting as
"mirror" for github/atomic -> git.centos.org
jzb work with walters and imcleod to set up github repo for
collaboration
jzb
jzb work with walters and imcleod to set up github repo for
collaboration
walters
jzb work with walters and imcleod to set up github repo for
collaboration
It'd be great if folks who have active AIs could send an update to the
lists with the status there. I'll be sure to do so.
Thanks!
jzb
[1]
http://centos.org/minutes/2015/january/centos-devel.2015-01-22-16.02.html
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
Greetings All!
Time for another Storage SIG meeting [1] . We will be meeting in
#centos-devel on Freenode.
Agenda:
#info Topic: Action items from previous meeting
#info Topic: Status Updates
#info Subtopic: GlusterFS
#info Subtopic: OpenAFS
#info Subtopic: Ceph
#info Subtopic: SCST
#info Open Floor
Action items from previous meetings:
* ACTION: billings to build OpenAFS using koji (lalatenduM, 15:35:29)
* ACTION: billings to try out reimzul's way of kmod building and yum
priorities stuff for openafs repo (lalatenduM, 15:49:54)
* ACTION: alphacc to validate the storage7 koji targets and setup new
tags as needed for openafs (kbsingh, 15:53:42)
* ACTION: kbsingh to see if openafs is GPL compatible or not
(lalatenduM, 15:53:54)
* ACTION: lalatenduM will help deason to get standard policy or
guidance on packaging selinux rules (lalatenduM, 15:54:48)
* ACTION: lalatenduM will help scuttlemonkey on 101 for building Ceph
on cbs (lalatenduM, 15:55:47)
* ACTION: hchiramm needs to finalize wiki articles for GlusterFS
(lalatenduM, 16:01:23)
[1] http://wiki.centos.org/SpecialInterestGroup/Storage
Thanks,
Lala
#lalatenduM on Freenode
WG meeting will be at 16:00 UTC (11:00 EST, 17:00 Brno, 11:00 Boston,
1:00+1d Tokyo, 2:00+1d Brisbane) in #centos-devel on Freenode.
= Topics =
* current status
* summarize the current work-flow to build collections
* Fosdem plans
===============================
#centos-devel: CentOS Cloud SIG
===============================
Meeting started by kushal at 15:02:37 UTC. The full logs are available
at centos-devel/2015/centos-devel.2015-01-22-15.02.log.html .
Meeting summary
---------------
* Roll call (kushal, 15:02:42)
* Action items from last meeting (kushal, 15:11:48)
* ACTION: rbowen will followup the RDO community for the help on Juno
on EL6 (kushal, 15:14:08)
* David Hill volunteered to maintain Centos/RHEL/EL6 packages for Juno
on rdo-list (rbowen, 15:14:19)
* LINK:
https://www.redhat.com/archives/rdo-list/2015-January/msg00066.html
(rbowen, 15:14:44)
* ACTION: number80 will open a ticket to get access to the box to
install RDO from CBS (kushal, 15:17:03)
* kbsingh got the machines for number80 to install RDO (kushal,
15:18:32)
* ACTION: send to centos-devel list of packages and builds to sign for
CBS RDO repo and open a ticket (number80, 15:21:24)
* ACTION: kushal to send emails to the SIG members before meetings,
and for once to the -devel and -user lists for those projects.
(kushal, 15:37:38)
* LINK: http://markmail.org/message/onebulgjkquotgkc (rbowen,
15:50:50)
Meeting ended at 15:51:14 UTC.
Action Items
------------
* rbowen will followup the RDO community for the help on Juno on EL6
* number80 will open a ticket to get access to the box to install RDO
from CBS
* send to centos-devel list of packages and builds to sign for CBS RDO
repo and open a ticket
* kushal to send emails to the SIG members before meetings, and for once
to the -devel and -user lists for those projects.
Action Items, by person
-----------------------
* kushal
* kushal to send emails to the SIG members before meetings, and for
once to the -devel and -user lists for those projects.
* number80
* number80 will open a ticket to get access to the box to install RDO
from CBS
* rbowen
* rbowen will followup the RDO community for the help on Juno on EL6
* **UNASSIGNED**
* send to centos-devel list of packages and builds to sign for CBS RDO
repo and open a ticket
People Present (lines said)
---------------------------
* kushal (67)
* kbsingh (40)
* rbowen (24)
* number80 (15)
* centbot (4)
* jzb (1)
* bstinson (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
Director Python Software Foundation
http://kushaldas.in
Hello,
I originally asked on the centos mailing list when CentOS will publish errata like Red Hat does for RHEL.
It has since turned into a discussion which seems more fit for the centos-devel list, so I'm moving it here now.
Here is the last post on the centos list: http://lists.centos.org/pipermail/centos/2015-January/149122.html
The current problem which needs to be tackled is where to get the data from.
It has been suggested that getting the data from Red Hat's emails would not be a breach of Red Hat's ToU.
Can anybody confirm this?
If this is the case, then we can just subscribe a bot to the emails and generate the data from that and put it in updateinfo.xml.
Thanks,
David
hi,
We've been working on this on and off for a while, and are pretty close
to taking up user accounts now. I've started documenting the User part
of things here : http://wiki.centos.org/DevCloud
There is a GUI as well, but meh. Everyone can CLI it.
This is running off OpenNebula on 4 machines, with gluster doing the
storage under it. There are another 4 machines waiting to do in, as soon
as we get extra power capacity at the DC it will expand ( from 64 cores
now, to 128 cores ); there are a few TiB of fairly performant storage
backing this entire setup.
There are no real limits for the users at this point, and unless we get
lots of people being abusive of resources, we will try and keep it that way.
regards
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
hi,
I've disabled the nightly run for the atomic-anaconda builds, there
seems to be some issue in lorax running from cron; will investigate this
and also, this might be a good time to start looking at running tests
against the atomic ostree repo and atomic-anaconda images.
- KB
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
hi,
In order to resolve a problem we have with the new c4.8xlarge instance
type, we need to carry a patch that isnt in the main distro kernel.
Therefore, we are going to roll the patch into a kernel with disttag
.e6.aws and use that for the x86_64/CentOS-6 AMI images refresh for Jan
'15. And setup a repo for folks using that AMI to get, and continue to
get their kernel updates.
This patch should make it into the upstream kernel, and when it does, we
will discontinue the .el6.aws kernel - resulting in users just rebasing
over to the regular distro kernel.
there is no impact on the c7 ami's, this is an issue limited to the
centos6 kernels.
ref: http://bugs.centos.org/view.php?id=8016
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc