October 21, 2014
The CentOS team has released the Continuous Release (CR) Repository RPMs for CentOS-6.6 into their 6.5/cr tree. See the Release Announcement.
Now a little more about the release process.
- Red Hat releases a version of Red Hat Enterprise Linux. In this case the version is Red Hat Enterprise Linux 6.6 (RHEL-6.6), which was released on October 14th, 2014. With that release by Red Hat comes the source code which RHEL 6.6 is based on.
- The CentOS team takes that released source code and starts building it for their CentOS release (in this case CentOS-6.6). This process can not start until the Source Code from Red Hat is available, which in this case was October 14th.
- At some point, all the Source Code has been built and there are RPMs available, this is normally 1-5 days depending on how many Source RPMs there are to build and how many times the order needs to be changed to get the builds done correctly.
- After the CentOS team thinks they have a good set of binary RPMs built, they submit them to the QA team (a team of volunteers who do QA for the releases). This QA process includes the t_functional suite and several knowledgeable system administrators downloading and running tests on the RPMs to validate updating with them works as planned.
- At this point there are tested RPMs ready, and the CentOS team needs to build an installer tree. This means, take the new RPMs and move them into place in the main tree, remove the older ones RPMs they are replacing, run the build installer to create an installable tree, test that installable tree. This process can take up to 7 days.
- Once there is an installable tree, all the ISOs have to be created and tested. We have to create the ISOs, upload them to the QA process, test them for installs via ISOs (correct sizes, how to split the ISOs, what is on the Live CDs and LiveDVDs to keep them below the max size to fit on media, etc.). We then also test the installs for UEFI installs, Secure Boot installs (CentOS-7 only), coping to USB Keys and checking the installs that way, etc. This process can also take up to 7 days.
The CR Repository
The process of building and testing an install tree, then creating and testing several types of ISO sets from that install tree (DVD Installer, Minimum Install ISO, LiveCD, LiveDVD, etc) can take 1-2 weeks after all the RPMs are built and have gone through initial QA testing.
The purpose of the CR repository is to provide quicker access to RPMs for an upcoming CentOS point release while further QA testing is ongoing and the ISO installers are being built and tested.
Updates in the CR for CentOS-6.6
More Information about CR.
CentOS-6.6 Release Notes (Still in progress until the actual CentOS-6.6 release).
Upstream RHEL-6.6 Release Notes and Technical Notes.
October 15, 2014
The CentOS Project is pleased to announce four new Docker images in the CentOS Container Set, providing popular, ready to use containerized applications and services. Today you can grab containers with MariaDB, Nginx, FreeIPA, and the Apache HTTP Server straight from the Docker Hub.
The new containers are based on CentOS 7, and are tailored to provide just the right set of packages to provide MariaDB, Nginx, FreeIPA, or The Apache HTTP Server right out of the box.
The first set of applications and services provide two of the world’s most popular Web servers, MariaDB for your database needs, and FreeIPA to provide an integrated security information management solution.
The CentOS Container Set is an effort to leverage the CentOS Project to give developers and admins the building blocks to easily set up containerized services in their environment. Keep an eye on the CentOS blog for further releases, or help us as we continue to develop more!
To get started with one of the images, use: `docker pull centos/<app>` where <app> is the name of the container (*e.g.* `docker pull centos/mariadb`). You can find some quick “getting started” info on the Docker Hub page for each application.
Jason Brooks has written up a longer howto for FreeIPA that details how to build the container (which is already done here, but you can rebuild the images if you like using the Dockerfiles on GitHub), and how to set it up to use FreeIPA with an application.
We have a larger set of Dockerfiles (derived initially from the Fedora Dockerfiles) set that we’re working on to develop pre-made CentOS Docker containers for easy use. Join the centos-devel mailing list to ask questions about the containers, or to provide feedback on their use. We also accept pull requests if you have any fixes or new Dockerfiles to contribute!
As most of you already know, there is an important SSLv3 vulnerability (CVE-2014-3566 - see https://access.redhat.com/articles/1232123) , known as Poodle.
While it's easy to disable SSLv3 in the allowed Protocols at the server level (for example SSLProtocol All -SSLv2 -SSLv3 for apache), some clients are still defaulting to SSLv3, and Koji does that.
We currently have disabled SSLv3 on our cbs.centos.org koji instance, so if you're a cbs/koji user, please adapt your local koji package (local fix !)
At the moment, there is no available upstream package, but the following patch has been tested by Fedora people too (and credits go to
- --- SSLCommon.py.orig 2014-10-15 11:42:54.747082029 +0200
+++ SSLCommon.py 2014-10-15 11:44:08.215257590 +0200
@@ -37,7 +37,8 @@
if f and not os.access(f, os.R_OK):
raise StandardError, "%s does not exist or is not
readable" % f
- - ctx = SSL.Context(SSL.SSLv3_METHOD) # SSLv3 only
+ #ctx = SSL.Context(SSL.SSLv3_METHOD) # SSLv3 only
+ ctx = SSL.Context(SSL.TLSv1_METHOD) # TLSv1 only
@@ -45,7 +46,8 @@
verify = SSL.VERIFY_PEER | SSL.VERIFY_FAIL_IF_NO_PEER_CERT
- - ctx.set_options(SSL.OP_NO_SSLv2 | SSL.OP_NO_TLSv1)
+ #ctx.set_options(SSL.OP_NO_SSLv2 | SSL.OP_NO_TLSv1)
+ ctx.set_options(SSL.OP_NO_SSLv2 | SSL.OP_NO_TLSv1 | SSL.OP_NO_SSLv3)
We'll keep you informed about possible upstream koji packages that would default to at least TLSv1
If you encounter a problem, feel free to drop into #centos-devel channel on irc.freenode.net and have a chat with us
October 01, 2014
There has been a fair amount of press in the last couple of days concerning Xen update XSA-108, and the fact that Amazon EC2 and Rackspace must reboot after this update:
Rackspace forced to reboot cloud over Xen bug
Amazon Reboots Cloud Servers, Xen Bug Blamed
There are other stories, but those articles cover the main issue.
As KB tweeted, the CentOS-6 Xen4CentOS release is also impacted by this issue and the CentOS team has released CESA-2014:X013 to deal with XSA-108. There are also 3 other Xen4CentOS updates released: CESA-2014:X010, CESA-2014:X011, CESA-2014:X012
If you are using Xen4CentOS on CentOS-6, please use yum update to get these security updates ... and like Rackspace and Amazon EC2, you need to reboot your dom0 machine after the updates are applied.
September 30, 2014
The CentOS team will have a booth in the Exhibit Hall for the 2014 cPanel Conference at the Westin Galleria hotel in Houston, Texas from September 30th to October 1st 2014.
CentOS Board members Johnny Hughes (that's me :D) and Jim Perrin will be at the booth whenever the hall is open.
We are looking forward to lots of discussions and we will have some swag to give out (Tee Shirts .. including the new 10 Year Anniversary tee, Stickers, etc.). We will also be happy to install CentOS on your laptop (or let you do it) ... or if you have a USB key available, we will put a CentOS iso on it for you to use for install later.
If you are going to be at cPanel 2014, come on down and see us!
The CentOS Linux 5.11 distribution for both the x86_64 and i386 architectures is now released.
If you are running any previous version of CentOS-5 Linux, then you can upgrade simply by using the command:
ISOs are also available here:
Please see the Release Announcement and Release Notes for more details.
September 25, 2014
Over the last few weeks, we’ve been asked about using systemd inside the CentOS-7 Docker containers for more complex operation. Because systemd offers a number of rather nice features, I can completely understand why people want to use it rather than pulling in outside tools like supervisord to recreate what already exists in centos by default. Unfortunately it’s just not that easy.
There are a couple major reasons why we don’t include systemd by default in the base Docker image. Dan Walsh covered these pretty completely in a blog post, but to recap where we are currently lets hit the highlights
- systemd requires the
CAP_SYS_ADMINcapability. This means running docker with
--privileged. Not good for a base image.
- systemd requires access to the cgroups filesystem.
- systemd has a number of unit files that don’t matter in a container, and they cause errors if they’re not removed
It’s for these reasons that we ship with fakesystemd in the default image. The fakesystemd package provides dependency resolution and the proper directory structure so that packages install normally, and individual apps can be run inside the container by default. The fakesystemd package isn’t really an elegant fix, but it’s currently the best we can do in the base images. As soon as we’re able to rip it out and ship a proper systemd package, we will.
If you’re okay with running your container with
--privileged, then you can
follow the steps below to create your systemd enabled docker image from the
CentOS-7 base image.
Dockerfile for systemd base image
FROM centos:centos7 MAINTAINER "you" <firstname.lastname@example.org> ENV container docker RUN yum -y swap -- remove fakesystemd -- install systemd systemd-libs RUN yum -y update; yum clean all; \ (cd /lib/systemd/system/sysinit.target.wants/; for i in *; do [ $i == systemd-tmpfiles-setup.service ] || rm -f $i; done); \ rm -f /lib/systemd/system/multi-user.target.wants/*;\ rm -f /etc/systemd/system/*.wants/*;\ rm -f /lib/systemd/system/local-fs.target.wants/*; \ rm -f /lib/systemd/system/sockets.target.wants/*udev*; \ rm -f /lib/systemd/system/sockets.target.wants/*initctl*; \ rm -f /lib/systemd/system/basic.target.wants/*;\ rm -f /lib/systemd/system/anaconda.target.wants/*; VOLUME [ "/sys/fs/cgroup" ] CMD ["/usr/sbin/init"]
This Dockerfile swaps out fakesystemd for the real deal, but deletes a bunch of the unit files we don’t need. Building this image gives us a usable base to start from.
docker build --rm -t centos7-systemd .
systemd enabled app container
Once this new base image is built, we can move on to building stuff that actually needs systemd. In this instance we’ll use httpd as an example.
FROM centos7-systemd RUN yum -y install httpd; yum clean all; systemctl enable httpd.service EXPOSE 80 CMD ["/usr/sbin/init"]
We build once again:
docker build --rm -t centos7-systemd/httpd
To put this all together and run httpd with systemd in Docker, we do this:
docker run –privileged -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 80:80 centos7-systemd/httpd
This container is running with systemd in a limited context, but it must always be run as a privileged container with the cgroups filesystem mounted.
There are plenty of rumors circulating that this will be addressed in the future, either in system or in a systemd-like subpackage. As soon as we’re able to ship systemd in the base image, we will do so.
September 24, 2014
There is a critical CVE issue in all versions CentOS that has been fixed today. Please update your CentOS with this command:
Information about this issue can be found here:
The CentOS release announcements are here:
CentOS-5, CentOS-6, CentOS-7
If you have any other questions about this issue, you can ask on the CentOS mailing list here.
September 05, 2014
“CentOS Dojos are a one day event that bring together people from the CentOS communities to talk about systems administration, best practises, and emerging technologies.”
At this particular Dojo we have this great lineup of information, discussion, and getting things done:
- Jim Perrin (@BitIntegrity) will start the day with a few minutes about the CentOS Project and do some introductions around the room.
- Garrett Honeycutt (@learnpuppet) goes next with a session, “Why Automation is Important” that covers topics such as configuration management with Puppet, Ansible, et al.
- Dmitri Pal from the FreeIPA project will discuss “Active Directory Integration”, a popular topic for many sysadmins and ops people stuck with a mixed-in-with-Windows environment.
- Greg Sheremeta (@gregsheremeta) of the oVirt project finishes with a tutorial on using the oVirt all-in-one installer. oVirt is virtualization management around KVM (cf. VMWare vSphere) with a growing userbase.
- Then a sponsored lunch and time to network with your fellow Dojo attendees.
- After lunch until the evening is a hackfest focusing on building and using Docker, building Xen components for CentOS 6, and whatever else gets cooked up. The CentOS team will be bringing a local mirror and WiFi for connecting on a private LAN for the hackfest. You can bring your laptop, ideas, and skills.
If you are interested in attending, please sign up on our event page.
September 03, 2014
We will have speakers in the morning, starting at 10:00 am local time and a hackfest beginning at 1:00pm.
September 02, 2014
July 22, 2014
EDIT (Monday July 28, 2014 – 2010 UTC):
We now have what we think is going to be the final version of this upgrade tool. Please see the following link to test:
We now have some Beta Testing RPMs available to test upgrades from CentOS-6 to CentOS-7. These tests were announced on the CentOS-Devel mailing list here:
Since the release of the test RPMs, we have had several patches created by Manuel Mausz. Manuel’s patches have done a lot to make the Preupgrade Assistant work for upgrades. We now need to get some tests of the patched RPMs.
The new RPMs are available from the Testing Repo here:
The upstream documentation for performing upgrades, as it currently exists, is here:
The CentOS team would like to very much thank Manuel for his testing work and patches for Preupgrade Assistant. This is an example of how we are now doing things in the “New” CentOS Project … where the community is now involved in all aspects of what we do except the actual building of the upstream sources for the actual distro.
Other things we need from the community for this process:
- Test the RPMs as they exist right now in the Testing Repo.
- If the process needs more changes to work properly, submit patches to the CentOS-Devel mailing list to get them rolled into the packages.
- Document the process of using the current RPMs from the Testing Repo to actually perform CentOS-6.5 to CentOS-7 upgrades.
- Update wiki.centos.org to contain the newly documented processes to perform the upgrades.
The SRPMs for these packages are here:
The sources are also available from git.centos.org:
And the specific packages are:
- preupgrade-assistant : Git Branch c6
- preupgrade-assistant-contents : Git Branch c6
- redhat-upgrade-tool: Git Branch c6
Please test and document these packages and the process, and submit any required code changes to the CentOS-Devel mailing list. If you need wiki.centos.org edit capability to create/update docs for the process, ask on the CentOS-Docs mailing list.
Note: The state of this software is to be considered Beta at best … do NOT try to use it on ANYTHING even slightly important.
EDIT: New packages are now pushed based on the changes from this mail:
Please run preupg with "-s CentOS6_7".
July 19, 2014
The Linux kernel before 3.15.4 on Intel processors does not properly restrict use of a non-canonical value for the saved RIP address in the case of a system call that does not use IRET, which allows local users to leverage a race condition and gain privileges, or cause a denial of service (double fault), via a crafted application that makes ptrace and fork system calls.
This issue affects CentOS-6 and -7 kernels. An updtream fix has now been applied to the CenOSPlus kernels.
July 15, 2014
We would like to announce the general availability of CentOS Linux 7 for 64 bit x86 compatible machines.
This is the first release for CentOS-7 and is version marked as 7.0-1406
First, please read through the release notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 – these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users.
Updates, Sources and DebugInfos
Since the upstream EL7 release, there have been some updates released – these have been built and are being pushed to the CentOS mirror network at the moment. They will be available within the next 24 hrs. From this point on we will aim to deliver all updates within 24 to 48 hrs of upstream releases.
For the first time, this release was built from sources hosted at git.centos.org, however srpms being a byproduct of the build and also considered critical in the code and buildsys process are being published to match every rpm we release. Sources will be available from vault.centos.org in their own dedicated directories to match the
corrosponding binary rpms. Since there is far lesser traffic to the source rpms compared with the binary rpms, we are not putting this content on the main mirror network, however if users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All source rpms are signed with the same key used to sign their binary counterparts.
Debuginfo packages are also being signed and pushed. They should be online by the end of this week, July 11th.
Yum configs for both sources and debuginfo packages are included in the default centos-release package on every install.
For the CentOS-7 build and release process we adopted a very open process. The output of the entire buildsystem is made available, as its built, at http://buildlogs.centos.org/ – we hope to continue with that process for the life of CentOS-7, and attempt bringing CentOS-5 and CentOS-6 builds into the same system.
CentOS 7.0-1406 introduces a new numbering scheme that we want to further develop into the life of CentOS-7. The 0 component maps to the upstream realease, whose code this release is built from. The 1406 component indicates the monthstamp of the code included in the release ( in this case, June 2014 ). By using a monthstamp we are able to respin and reissue updated media for things like container and cloud images, that are regularly refreshed, while still retaining a connection to the base distro version.
In order to facilitate Special Interest Groups to further extend the CentOS Linux platform, we are also using component codes. The main distro is, therefore, titled ‘Core’. SIGs would be able to adopt any name they need and deliver that by overriding the base centos-release rpm.
In order to conserve donor bandwidth, and to make it possible to get the mirror content sync’d out as soon as possible, we recommend using torrents to get your initial installer images:
Details on the images is available on the mirrors at http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt – that file clearly highlights the difference in the images, and when one might be more suiteable than the others.
The size, sha256 sums and torrents for the ISO files,:
The iso files are also available for direct download from
We are currently working to extend the portfolio of content we deliver for a major release. In the past its only been iso media and install tree’s, but with CentOS-7 we are also going to deliver:
= Docker Images
= Cloud Images in vendor ecosystems ( HPCloud, RackSpace, AWS, Google Compute etc )
= Cloud Images for direct download and consumption in on-premise infra ( RDO/OpenStack, CloudStack, OpenNebula and Eucalyptus )
= Given the popularity of the minimal install ISO in CentOS-6, we are going to try and deliver a minimal install ISO for CentOS-7 as well. One key challenge here is that the installer image has grown to nearly 360MB, and getting enough content into a CD size image is proving hard.
= A community build system is in the works, we hope to have that functional by the end of this month ( July 2014 ), allowing us to set up a contributor base in the Special Interest Groups to extend and further develop layers and variants on CentOS Linux
= Special Interest Groups including Xen on CentOS, CentOS Storage and CentOS Atomic Host are starting to gain traction, expect to see content delivered from those groups in the near future.
= As a part of the expanded Core efforts, we are also going to attempt to deliver a CentOS-7 release for 32bit x86, ARM and PowerPC in the coming months.
If you are interested in joining any of these efforts, signup for the CentOS-devel list at http://lists.centos.org/ and send in a self intro email and what areas you are interested in helping out with.
We try and organise Dojo’s in various parts of the world as a one day event, to bring together people who use CentOS and others who are keen to learn about CentOS. The day’s focus is on sharing technical knowledge and success stories. Its also a great place to meet and talk about upcoming technologies and learn how others are using them on CentOS Linux.
04th Aug ’14 Cologne, Germany : http://wiki.centos.org/Events/Dojo/Cologne2014
25th Aug ’14 Paris, France : http://wiki.centos.org/Events/Dojo/Paris2014
29th Oct ’14 Barcelona, Spain: http://wiki.centos.org/Events/Dojo/Barcelona2014
This autumn and winter we also hope to host Dojos in New York City USA, Timisoara Romania and Bangalore, Pune and New Delhi in India. Please keep an eye on the page at http://wiki.centos.org/Events for details on these venues.
The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp
This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution, without them CentOS Linux would look very different.
The following people made exceptional contributions in this build,
test release process for CentOS-7 :
Alain Reguera Delgado
Johnny Hughes Jr
Stephen John Smoogen
I would also like to thank our donors and sponsors for their continued support for the project. Its down to their help that we were able to deploy enough resources to run the Public QA process for CentOS-7; as a data point we ran nearly 300 – 350mbps of sustained bandwidth for the last 3 weeks that we?ve had the Public QA running.
And thanks to everyone who contributed with ideas, code, test feedback and promoting CentOS into the ecosystem.
Project Lead, The CentOS Project
+44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS
GnuPG Key : http://www.karan.org/publickey.asc
July 07, 2014
After three weeks in testing, we are very happy to announce the release for CentOS-7/x86_64 Please read the announcement here : http://lists.centos.org/pipermail/centos-announce/2014-July/020393.html And the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 But this isnt the end of the seven process, it’s where the fun begins – KB
A small picture say sometimes more than a long sentence …
June 12, 2014
The powerpc platform has always been interesting, but hard to get and while we’ve had some levels of interest in the past, either I struggled to find the hardware to bootstrap the builds, or we were unable to get enough communication going to bring the community of contributors together to kick things off. Now as we work through the mechnics of building and delivering CentOS-7 on x86, we again have the opportunity to try and see if there is a willing, contributor community that can come form up a PPC SIG in CentOS.
We do have some resources ( compute + network + mirror ) to make the backend side of things happen, and the folks at OSUOSL.org have offered us some capacity on their community powerpc builder resources to help as well.
Interested to come help ? Join the conversion on the centos-devel mailing list : http://lists.centos.org/pipermail/centos-devel/2014-June/010625.html
June 10, 2014
We would like to welcome onboard the CERN Linux Distro team ( http://cern.ch/linux ) to the CentOS Core SIG. Thomas Oulevey and Jaroslaw ‘Jarek’ Polok are going to be bootstrapping the CentOS Community Buildsystem around Koji and helping run it going forward. The community buildsystem is going to be the central place for all source to binary builds used by all efforts other than CentOS Core ( for now ).
The initial target is to get a test instance running in the coming weeks, and then work on the git.centos.org integration, with the aim of having the ‘production’ buildsys online soon. This is the build service that all SIG’s and Core SIG builds will consume going forward ( with the exception of CentOS Linux, we have quite a bit of work to do before we can migrate that ).
Communications on this effort will be on the centos-devel mailing list ( http://lists.centos.org/mailman/listinfo/centos-devel ) and on the #centos-devel irc channel on irc.freenode.net. Hardware resources for the effort have been identified, setup and access is being setup so things can start rolling fairly quickly. Mike McLean and Fabian Arrotin are going to be working with them.
You can keep up with Jarek on his google+ page at https://plus.google.com/+JaroslawPolok/ and Thomas tweets at https://twitter.com/thomasnomas ; They both also contribute to the http://linux.web.cern.ch/linux/ blog.
Please join me in welcoming Thomas and Jarek to the CentOS Project.
June 09, 2014
I was curious how the discussion rate on centos-devel compared to previous time periods. I want to know if our work on growing the project participation at the contributor level is working, and while examples such as the increase in the SIG activity are a good indication, one simple one is to see if there is more discussion in the contributor communication channels. Based on what I see, the trend looks very good.
My analysis is pretty simple.
- There have been other periods of time where the discussion level was this high (above 50 KB in archive size), but they appear more to be spikes than sustained discussion, with the exception of November 2010 through July 2011. If you were around the Project during that time, you know that is a reflection of work and associated noise around the CentOS 6 release. Although the sustained discussion levels are similar, I think the tone of the discussions is quite different, so I weigh the current trend as “good” by comparison because it reflects growing participation rather than concern about the timing of the CentOS 6 release.
- 50 KB seems like a good level to judge against in that it seems most months reach at least 25 KB, but going above 50 KB is less common. In the nine years the archives track, the size has gone above 50 KB about 20 times out of 112 archived months, or about 18% of the time. (By comparison, the size has gone above 25 KB 64 times, or 57% of the time.)
- The one largest-spike-of-all-time is January 2014, which is easily attributable to the announcement about joining forces with Red Hat and the subsequent discussions. Again, the tone of those emails was quite good, as compared to the previously largest spike of February 2011. That spike was to be expected since the news caught many people by surprise, so I’m generally ignoring it as an outlying data point in terms of having any more meaning than that.
June 04, 2014
As we get ready for CentOS-7 ( hope everyone is keeping their eyes on http://seven.centos.org/ ) I’ve been wondering what we can do from the CentOS Project side of things to help the larger ecosystem adapt, facilitate and grow into CentOS-7 once its released. And what we might be able to do in the interim to help with testing and porting efforts that people might be undertaking right now, as they too get ready for CentOS-7. There are some really cool things coming in CentOS-7, and it would be great if we can, as a community ensure that people are able to use these features in the best possible manner. And also educate people about these new features, so they are able to make the right choices.
So with that in mind, are you someone who is a part of or contributes to an open source community or effort, who rely on CentOS-5 and/or CentOS-6 ? How can we help you get on the CentOS-7 targets ?
May 07, 2014
The CentOS team is happy to announce that we will be having a CentOS Dojo on Wednesday, June 4th, 2014 at the University of Cincinnati's Dyer Hall (Map | Register | Info)
CentOS Dojos are a one day event that bring together people from the CentOS communities to talk about systems administration, best practises, and emerging technologies. The emphasis is to find local speakers and tutors to come together and talk about things that they care about most, and to share stories from their experiences working with CentOS in various scenarios.
Both Jim Perrin and I will be there representing the CentOS Board, and there will be several great speakers (details still being worked out on the exact speaker list).
If you are in the Cincinnati area and use CentOS, please register and come to the event.
See you there !
May 01, 2014
I will be representing the CentOS Project at OpenStack Summit Atlanta 2014 on May 12th to 16th, 2014.
April 30, 2014
The CentOS Project will be having a Dojo in São Paulo, Brazil on Monday, May 5th, 2014 at Avenida Brigadeiro Faria Lima 3900 - Cj 81 Itaim Bibi Sao Paul (map, register, info).
CentOS Dojos are one day events, organized around the world, that bring together people from the CentOS Communities to talk about systems administration, best practices in Linux-centric activities and emerging technologies of note. The emphasis is to find local speakers to come together and talk about things that they care about most, and to share stories from their experiences working with CentOS in various scenarios.
This event is sponsored By Red Hat and happens two days before FISL 15 in Porto Alegre, Brazil.
The CentOS team will also be at FISL 15 and these are our first ever events in South America, so we are pretty excited.
If you are near São Paulo or Porto Alegre at the beginning of May, please stop by and visit the team.
April 21, 2014
Many of us use consensus-style decision making in our free/open source projects such as Apache’s lazy consensus model, but often we have a practice or even a governance of having things end up in a majority-wins voting process.
In a majority-wins voting model, the dynamic is one where the dissenters are marginalized — the majority has to put the dissenting minority in the position of being a “loser” in a vote.
In a consensus-decision model with blocking, you have a situation where it becomes the duty of the entire group to take care of the dissenters’ concerns.
In general, consensus decisions force the group to focus on a compromise around the best-possible solution. When people are in the position of being a winner or a loser, the effect is to make people solidify around one of two extremes that may not represent the best possible solution.
Often achieving consensus only requires clarification of a misunderstanding or minor adjustments to the original proposal. This occurs even where no one has blocked, but the appearance of -0 (or a stand aside) will also make it clear that the original proposal might need more thought — getting a -0 from a leading thinker in a group spurs others to wonder if maybe there is more that can be done to make the proposal fully supported.
There are a lot more details to how things work in practice in a consensus-decision model, which I covered fairly well in the Appendix to the CentOS Project Board governance, quoted here:
In the CentOS Project a discussion toward a decision follows this process:
- A proposal is put forth and a check for consensus is made.
- Consensus is signified through a +1 vote.
- A check is made for any dissent on the proposal.
- Reservations? State reservation, sometimes with a ‘-1’ signifier
- Reservations about the proposal are worked through, seeking consensus to resolve the reservations.
- A reservation is not a vote against the proposal, but may turn into a vote against if unresolved. It is often expressed with an initial -1 vote to indicate reservations and concerns. This indicates there is still discussion to be had.
- Stand aside? No comment, or state concerns without a -1 reservation; sometimes the ‘-0’ signifier is used.
- This option allows a member to have issues with the proposal without choosing to block the proposal, by instead standing aside with a +/-0 vote.
- The stated concerns may influence other people to have or release reservations.
- Block? Vote ‘-1’ with reasons for the block.
- This is a complete block on a proposal, refusing to let it pass. A block is a -1 vote and must be accompanied with substantive arguments that are rooted in the merit criteria of the Project – protecting the community, the upstream, technical reasons, and so forth.
Block (-1) votes used as a veto are typically used only when consensus cannot otherwise be met, and are effectively a veto that any sitting Board member can utilize with sufficient substantiation.
In writing the original section of The Open Source Way, I didn’t go so far as to recommend the abandonment of the majority-wins voting method, instead I said, “Seek consensus — use voting as a last resort.” That section (unfinished) is now going to get a rewrite where I’ll definitely come down against majority-wins, and write out more of the why.
Partially I owe my improved understanding from using the consensus model in a business collective where I’m a partner, Santa Cruz Pedicab. Working with the model in the physical world made me intensely aware of the human impact of majority-wins by comparison, and convinced me it was really the backbone to a welcoming community.
March 20, 2014
Just to let you know that I have verified some mirrors last week and sent several mails to the contact info we had for those mirrors (unreachable/far behind).
I've received feedback from some people still willing to be listed as third-party mirror and so they fixed the issue they had (thank you !)
Some other people replied with a "sorry, we can't host a mirror anymore" answer . (Thanks for having replied my email and thank you for having been part of the successful "centos mirror party" !).
For the "unanswered" ones, I've decided that it was time to launch a "Spring clean-up operation" in the mirrors DB/Network.
I've removed them from the DB, meaning that the crawler process we use to detect bad/unreachable mirrors will not even try anymore to verify them.
We actually have more than 500 external (third-party) mirrors serving CentOS to the whole world, without counting the 50+ (managed by CentOS) servers used to feed those external mirrors, and sometimes serving content too for countries less covered.
Thanks a lot for your collaboration and support ! We *love* you
March 19, 2014
On the eve of the Percona Live: MySQL Conference and Expo (Monday 31 March 2014) I get to help run my first CentOS Dojo at the Santa Clara Convention Center. For this event, I’ll MC and give a talk about the newness in the CentOS Project. The lineup so far is pretty set and quite stellar:
- Jeremy Carroll — Systems Automation and Metrics at Pinterest: “At Pinterest metrics instrumentation and presentation has been an increasingly vital as our systems scale …”
- Monty Widenius — Notes on MariaDB 10: “MariaDB is coming along in great strides, and is now included by default in the EL7 Beta cycle …”
- Peter Zaitsev — Running MySQL on CentOS Linux: “Linux is by far the most common platform to run MySQL, and there is a lot of accumulated knowledge about which way is best to run MySQL …”
- Jordan Sissel — Happy Tools: “Happy tools! This talk will introduce three different operations-friendly tools to help make you happier …”
- Joe Miller — Two Years in Your Future: “Systemd is the new kid on the block, everyone is talking about it, everyone is thinking about it, everyone is planning for it …”
- Joe Brockmeier — Software Collections on CentOS: “The power to build, install and use multiple versions of software on the same system, without affecting system-wide installed packages. Welcome to software collections …”
- Karsten Wade — The New CentOS Project: “A new Board member’s perspective on where the CentOS project is today and the road ahead …”
Massive thanks to Joe Brockmeier and Karanbir Singh (of the OSAS and OSAS/CentOS Engineering teams) and Kortney Runyan and the event crew at Percona. If you want to attend, hop on it — space is limited. It’s a no-cost event and comes with the bonus of a no-cost expo and keynote pass for Percona Live. Oh, did I mention we’ll serve you some lunch and generally treat you right?
If you are attending the main conference, visit us as the CentOS Project booth in the DotOrg Pavilion — or contact me if you are interested in staffing the booth.
March 15, 2014
Comme vous le savez peut-être (ou pas !), nous tiendrons un Dojo CentOS à Lyon le vendredi 11 avril. Si donc vous avez envie de partager votre expérience autour de CentOS, en donnant une présentation par exemple, ou bien si vous désirez seulement venir passer un bon moment avec nous en écoutant les présentations prévues (appel - subliminal - aux candidats volontaires !), sentez-vous libre de vous inscrire.
L'inscription est gratuite ! Plus d'informations sur la page Wiki : http://wiki.centos.org/Events/Dojo/Lyon2014 .
Hi people, are you in the Lyon (France) area around April 11th ? Willing to come to a CentOS Dojo ? (either to attend it or even better, present something around CentOS ?) . Feel free to register for this free event ! : http://wiki.centos.org/Events/Dojo/Lyon2014
March 14, 2014
Anyone who is using Delta RPMs (AKA - the yum-presto plugin) on CentOS-6 or Fedora knows how much of a PITA it is to generate the drpms. It takes forever to generate.
Ian Mcleod has posted some new functionality on the Yum Developers mailing list that addresses this issue.
Here is the git repo that contains the new code.
I have created an RPM and SRPM for EL6 that use the tarball from the git repo and add the following functionality:
--delta-workers - The number of worker processes to use for delta
--max-concurrent-delta-rpm-size - The maximum total size of uncompressed
rpm payloads that are actively being processed by makedeltarpm at any
March 13, 2014
CentOS has 3 events happening in the next month or so. Please come out and join us at as many of them as you can.
CentOS Dojo in Santa Clara, California on 31 March 2014.
CentOS Dojo in Denver, Colorado on 10 April 2014.
The CentOS Project at the Red Hat Summit in San Francisco, CA on 14-17 April 2014.
We will have CentOS board members at each of these events. If you want to find out what is happening the the CentOS world then these are the places to be :)
February 19, 2014
On Friday, I’m going to hang out near the stage and nod cleverly as Jim Perrin tells us about “Growing CentOS as a Platform for Infrastructure Development“. You can register for Infrastructure.Next (it’s no-cost!) here. It’s a full day devoted to learning about how real people are solving real problems with open source. I’ll have to visit my friends at the Fedora Activity Day. Then I’ll do the brisk-for-LA dinner so I can get back for Lawrence Lessig’s keynote, “Only You Can Get This, So Where Are You?” at 9 pm.
Saturday is dedicated to all the fun the expo has to offer, plus the evening activities. I’ll be hanging out at the Fedora, CentOS, and Red Hat booths. I’ll definitely carve time for m’man Jason Hibbets’ “Open Source ALL The Cities” – a topic near to my heart, one I’ve acted on, but barely to the extent Jason has, so I’m looking forward to learning more from him (and seeing a friend speak, natch.) Closing Saturday, two other friends-also-faves are Ruth Suehle (“Raspberry Pi Hacks“) and Rikki Endsley (“You know, for kids! 7 tips for improving tech education in our schools“), at 6 pm opposite each other (curse the schedule overlords!!!), I may have to favor Rikki as I had the fortune to catch Ruth in Scotland talking on the same topic a few months ago … which is another story. And look! I have another colleague, Rich Bowen (“Demystifying mod_rewrite“) at the same time (a skill I sorely need to demystify), and I note Dawn Foster is talking as well … So much goodness!
Sunday kicks off for me with Leslie Hawthorn at 10 am with “Why Checking Your Privilege is Good For *You*“. Leslie is another friend-and-great-speaker, but I’ll note that she’s particularly interesting to listen to and I think more so on this topic. I’m very much looking forward to this, especially as the newbie feminist that I am. Then Thomas Cameron is speaking on “Next Generation High Availability Linux Clustering” at 11:30, which I hope to be able to catch some of (and heckle.). I’ll be preparing for the “CentOS Project Q&A Forum” that I’m leading with Jim Perrin and Johnny Hughes at 1:30, where I’m looking forward to some reverse-heckling from Thomas. Perusing the schedule, I found the quite intriguing, “Hacking the Kernel, Hacking Myself” talk by Kelley Nielsen at 4:30. I’ve quite interested to hear her story around the domains of kernel development, personal development, the Outreach Program for Women, and her story overall.
Powered by Planet!
Last updated: October 23, 2014 09:00 PM