Hi all,
seems we are making good progress. Thank you everyone!
* First Xen release via the SIG is imminent (see Xen section)
* We are also close to a Docker release (see Docker section)
* We also need to look at cross-SIG dependencies to be able to make use of Gluster support in the Storage SIG (see oVirt section)
Regards
Lars
= Attendees =
* Lars Kurth
* George Dunlap
* Sandro Bonazzola
* Lokesh Mandevar
= Agenda =
== Replace audio meetings in favor of IRC meetings, which seem to work better ==
<All agree with IRC meetings>
ACTION :Send mail to list: If anyone objects, let us know.
ACTION: Lars to changeg invite and wiki to reflect IRC meetings always.
== Xen Update (George) ==
4.4.1 Virt-Sif testing for several weeks now. Everything appears to be working
Have a wiki now: covering xend to libxl migration - see http://wiki.centos.org/HowTos/Xen/Xen4QuickStart
Jonny has pushed the signed packages
Thus, this is the 1st Xen release from the VIRT SIG
ACTION: George to send quick mail to the list and write up a blog post. CC publicity@xenproject and KB such that he can cross post to the CentOS blog if he wants to
Note: 4.4.1 is still using the new old 3.10 kernel.
DISCUSSION:
George: do we have a conflict on kernel versions for CentOS 7. For xen we would need to override the CentOS 7 kernel to make Xen work with CentOS 7
Lokesh: there is no kernel requirement for Docker except that the kernel needs to be >= 3.10 – this should be a match
George: potential issue is that Docker is officially supported in RHEL/ CentOS 7
Lokesh: 3.14 should work for Docker, but needs to be verified.
George: before we push to public repo we need to test it.
Lokesh: CentOS and Docker are tested with 3.10. For Fedora we test with 3.18. Docker has its own test suite. So covering 3.14 should be straightforward
George: would you mind if I uploaded 3.10 and see whether it works? But there may be an issue that we would be missing RedHat backports in CentOS 7
Lokesh: Since yesterday have been doing a daily test for rawhide in addition to the stable branch. I don't think there should be an issue
George: Checking understanding that a new kernel is totally OK.
Lokesh: As long as we are not disabling standard kernel functionality we are fine
ACTION: George upload the latest kernel and coordinate with Lokesh re testing to ensure that nothing breaks
= Docker update (Lokesh) =
Still on 1.4.1
Yesterday I was talking to Jim and KB re a daily rebuild for CentOS and that should be fine
Maybe we will have an additional package Docker-upstream or Docker-unsupported (TBD)
I have also been talking to people from Kubernetes and Cockpit re new versions.
ACTION: Lokesh to make an announcements on the list(s) and then we can try and make a public release.
ACTION: Lokesh to create a getting started wiki page
ACTION: Lars to link to any announcements in FOSDEM VIRT SIG presentation
= oVirt update (Sandro) =
3.5.1 is upstreamed and released
Now we have a bit more time to investigate CBS, etc.
We also have credentials for wiki and CBS
Sandro: I had asked for some HowTo for CBS / Coogee by mail, which is still unresolved
George: has some runes for basic stuff which he can share
ACTION: George to create brief howto and share on list/wiki.
One of the other issues Sandro brought up is that the Storage SIG now has Gluster support and that he would like to build oVirt with support from Gluster packages in the storage SIG. There may a requirement for QEMU and KVM packages (details needed) from that SIG.
George: this will require some cross-SIG coordination that we need to resolve. At the moment we don’t have a way to cover inter-SIG dependencies
ACTION: Sandro email storage SIG (via centos-devel) and virt SIG and lay out problem to kick off a discussion. Lars can try and follow up with KB and others at FOSDEM.
= Any other business =
None
The new xen-4-41-5 and libvirt-1.2.10-3 RPMs produced by the
Virtualization SIG are now live in the Xen4CentOS repo for CentOS-6.6.
Thanks to the Virt SIG and the CBS team for all the hard work.
Looks like this SIG thing is finally taking off. Stuff from Atomic,
Storage, and Virt .. good job guys :)
Thanks,
Johnny Hughes
Hi: I want to make a linux OS based on Centos recently. I searched on Google several days, but still can't find the whole source code of Centos. Is there any way to get the whole source code of Centos, like android, just do a few command and then get the image files
--------------------------------
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