February 2016 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

CentOS 7.2 cloud images for ppc64le
by Xiandong Meng 14 Jun '16

14 Jun '16

Hi all, I noticed that there are centos 7 cloud images for x86. But i did not find the cloud images for ppc64le. Are there any work on it within this community? Or is there any plan to work on it? Regards, Xiandong Meng <mengxiandong(a)gmail.com> mengxiandong(a)gmail.com

2 6

Curating containers
by Karanbir Singh 04 Apr '16

04 Apr '16

hi, Yesterday a few of us met for a face to face walk through of the CentOS Container Pipeline we've been talking about. The aim was to rescope the upstream projects we can lean on, share code with, and help - and then find the glue pieces that could bring this code base together. The larger picture effectively boils down to : - Find the components needed to track code git repos ( either in git.centos.org or elsewhere ) - Find the components needed to now build that code, containerise the code, push it through a test process, and then deliver the containers either locally into a centos transitional container registry, or to a CDN like wider centos registry or if the user so desires, to a third part registry ( provided a good process can be find to handle the credentials needed ). - We'd want to use this pipeline both internally, for the CentOS Linux components ( eg. a LAMP container from CentOS Linux 7 ), for SIG components via cbs output ( eg. SCLo SIG folks shipping containers for their content ), as well as open this up via a trivial UI, for anyone in the community who'd like to come and consume this pipeline. the key piece that we didnt have clarity on was the orchestration and glue that could bind the various software components. Vaclav Pavlin, brought up that we might be able to use openshift templates in order to get the job runs done - if the input for the templates could be derived from the cccp-index, either via the jjb work already done, or writing a new filter into JJB, we might be able to execute a fairly scaleable solution without needing to own any piece of the over all code. Additionally, there is a fair interest from the Fedora team ( ie Adam! ) working on the same problem in their space, mostly consuming the identical code stack, within and for their infra, their constraints and aims. Over the coming days we are going to try and work though PoC's, get some infra setup and trial running through some of the user stories we want to execute on. Finally, a quick shout out to everyone for coming together at pretty much the last minute adhoc meeting - Fabian Arrotin, Brian Stinson, Christoph Goern, Vaclav Pavlin, Aaron Weitekamp, Tomas Tomecek, Adam Miller, Dusty Mabe, Honza Horak, Radek Vokal as well as Tim Waugh, Bama Charan and Mohammed Zeeshan for dialing into the meeting. And to everyone else, want to build containers with us ? come talk to us - we'd love to make sure we include as many user stories to get great scope before we start implementing bits. regards -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

8 24

Audio production SIG
by Tim 23 Mar '16

23 Mar '16

Hi all, I would like to propose a new SIG for audio production. This would primarily cover to setup a digital audio workstation. I started to build some packages for this like plugins, configurations and a realtime kernel (built from git.centos.org) for a public repository. During doing all this stuff I thought of founding a SIG. I think, CentOS will be the right distribution for this, because it is really stable, reliable and long term supported. Regards Tim

7 30

sclo-ror42: Ruby on Rails 4.2 packages available for testing
by Dominic Cleal 16 Mar '16

16 Mar '16

I'm happy to announce test packages of a new Ruby on Rails 4.2 collection are available from the CentOS Software Collections SIG. These are modelled on previous collections (e.g. rh-ror41) and provide all of Rails with full asset compilation support, plus extras such as jQuery (1.11.2 & 2.1.3). It depends on the rh-ruby22 and v8314 collections. To install it, run: yum install centos-release-scl yum install --enablerepo=centos-sclo-sclo-testing --nogpgcheck sclo-ror42 Activate and use the collection with "scl enable sclo-ror42". https://wiki.centos.org/SpecialInterestGroup/SCLo/RubyOnRails contains tips on using the RoR collection(s) with Passenger. Please test the collection out and report bugs to https://github.com/domcleal/sclo-ror42/issues or on this thread. -- Dominic Cleal dominic(a)cleal.org

2 3

Skylake install errors for CentOS-7
by Johnny Hughes 06 Mar '16

06 Mar '16

There were some install issues with some Intel Skylake chipsets/processors for CentOS-7. We have created a newer installer to fix this issue and the ISOs (CentOS-7-x86_64-DVD-1602-99.iso or CentOS-7-x86_64-Minimal-1602-99.iso) are available here: http://buildlogs.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1602-9… http://buildlogs.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-16… sha256sums: CentOS-7-x86_64-DVD-1602-99.iso: c226525cc5b47ffd32d8d082d8b316cb8f51592939f1b12d0dc846ff86d02e32 CentOS-7-x86_64-Minimal-1602-99.iso: 355eea6cc097e5f16805d075f27d2949aa17e8806127e4b361dcb2aef1eafe68 This is based on the latest released kernel (kernel-3.10.0-327.10.1.el7). This ISO set also has all current CentOS-7 updates rolled in including the new glibc. ========================== NOTE: Users who are not having issues what who want the latest ISOs should continue to use our normal ISO sets available here: http://buildlogs.centos.org/rolling/7/isos/x86_64/ Thanks, Johnny Hughes

4 3

How to build CentOS 7 AMI
by Alan Ivey 04 Mar '16

04 Mar '16

Hi everyone, I'd like to revisit the thread about how the CentOS 7 AMIs are created ( https://lists.centos.org/pipermail/centos-devel/2015-July/013652.html) and see if the process can be published in the https://github.com/CentOS/sig-cloud-instance-build repository or another relevant location. With CentOS 7 AMIs only being available in the Marketplace, all resulting EC2 instances have the Marketplace codes attached to the EBS volumes. A significant restriction of this is that a resulting image cannot be the non-primary volume of an instance unless it is powered down. This presents itself to be a problem in at least the following scenarios: - Unable to attach a CentOS 7 boot volume to another instance for repair without either creating a temporary instance or shutting down an existing one. For example, if you messed up the /etc/sudoers file and logged out, and wanted to repair, you would not be able to repair by mounting to another instance and editing the file without incurring additional (albeit small) cost, or having an existing instance be temporarily unavailable. - The "amazon-chroot" Packer Builder ( https://www.packer.io/docs/builders/amazon-chroot.html) does not work because it starts by mounting a copy of the snapshot tied to the AMI as part of a scripted operation and therefore cannot power off to do so Custom AMIs, snapshots, copied EBS volumes, etc, all have the marketplace codes copied to them and inherit the restrictions. If an org was to use these features for automating environments and was disconnected from the original Marketplace agreement, they may be unaware of this limitation. I would also appreciate being able to have the additional transparency of seeing how an AWS AMI is created as the docker/openstack/etc images from the repository referenced above. This would be useful in environments with regulatory compliance concerns, such as AWS GovCloud, HIPAA, FedRAMP, etc. I understand the benefit that Marketplace registrations allow for the ability to notify users of any changes, and I am not necessarily advocating for switching away from the Marketplace as the primary AMI location. I would like to be provided the opportunity to build a private AMI in the exact same procedure as the official image so as to avert the restrictions provided by the Marketplace. *[Note: I previously posted this question to centos-virt <https://lists.centos.org/pipermail/centos-virt/2016-February/004907.html>, but I did not receive any feedback and I have since noticed that **https://wiki.centos.org/SpecialInterestGroup/Cloud <https://wiki.centos.org/SpecialInterestGroup/Cloud> refers to the CentOS-Devel list for discussion. My apologies to subscribers of both lists.**]* Thank you, Alan

3 5

Experimental systemd repo
by Lukáš Nykrýn 29 Feb '16

29 Feb '16

Hi, I am one of the maintainers of systemd in RHEL/CentOS. We have put together a repository for systemd patches we would like to see in next release of CentOS 7: https://copr.fedorainfracloud.org/coprs/lnykryn/systemd-rhel-staging/ Unpacked source code can be found at github: https://github.com/lnykryn/systemd-rhel/commits/staging To be clear, this repository is not supported by CentOS or Red Hat in any way and it should not be used on production machines. It is really just a test build and it will not correspond to any later official update. But if somebody is interested in testing, I would really appreciate any feedback. For now, there are just some minor fixes, but more will come. Please report any problems via GitHub issues or email us to lnykryn(a)redhat.com or msekleta(a)redhat.com Regards, Lukas

3 3

A short introduction
by Laurentiu Pancescu 29 Feb '16

29 Feb '16

Hello everyone, Could you perhaps use some help? My name is Laurentiu, I'm based in southwestern Germany, and I would like to help with the Vagrant images from the CentOS Cloud Instance SIG. A bit of background information: I started using Linux in 1997, with Red Hat Linux 4.2, switched to Slackware 7.0 a few years later (due to issues with gcc-2.96), then Debian from 2001 until about two years ago, when I switched to Fedora. Unfortunately, my experience with system administration is limited to workstations and running standalone (Debian) servers. I'm more of a software developer: I was a graduate teaching assistant at a University for a couple of years, followed by around 9 years in R&D for an international corporation (where I worked pretty much everywhere in code bases containing tens of millions of lines of code - I spent more than half of the time writing C++ for a couple of real-time operating systems, debugging hardware and turning on boards and ASICs, the rest being Windows development and a bit of Perl for the code generators and the release system), learning just enough system administration to get stuff done. Besides C++, I know Python, as well as some Perl and Bourne shell scripting. Best regards, Laurentiu Pancescu

1 0

Meeting minutes from last week's Cloud SIG meeting
by Kushal Das 29 Feb '16

29 Feb '16

Hi, ======================== #centos-devel: Cloud SIG ======================== Meeting started by rbowen at 15:11:07 UTC. The full logs are available at centos-devel/2016/centos-devel.2016-02-25-15.11.log.html . Meeting summary --------------- * LINK: https://etherpad.openstack.org/p/centos-cloud-sig (chandankumar, 15:13:37) * OpenStack (rbowen, 15:14:08) * Test day planned in RDO land on March 10th, 11th - https://www.rdoproject.org/blog/2016/02/rdo-mitaka-3-test-day-march-10th-11… (rbowen, 15:14:44) * LINK: https://www.youtube.com/watch?v=4O8KvC66eeU (rbowen, 15:15:46) * OpenNebula (rbowen, 15:18:04) * NFV (rbowen, 15:27:32) * Open Floor (rbowen, 15:29:18) * ACTION: Kushal will head up getting blog posts out about Cloud SIG, and getting meeting logs sent to the various mailing lists. (rbowen, 15:31:01) Meeting ended at 15:32:42 UTC. Action Items ------------ * Kushal will head up getting blog posts out about Cloud SIG, and getting meeting logs sent to the various mailing lists. Action Items, by person ----------------------- * **UNASSIGNED** * Kushal will head up getting blog posts out about Cloud SIG, and getting meeting logs sent to the various mailing lists. People Present (lines said) --------------------------- * rbowen (42) * kushal (25) * centbot (4) * chandankumar (3) * trown (1) * Arrfab (1) * dneary (0) * dmsimard (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

1 0

signing a vagrant box
by Karanbir Singh 29 Feb '16

29 Feb '16

hi folks, does anyone have insight into signing a vagrant box, so the origin can be confirmed ? A brief look around seems to indicate there is no such support in vagrant itself ? Surely, I must be missing something. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

New CentOS Atomic Host Images Available for Download
by Jason Brooks 26 Feb '16

26 Feb '16

An updated version of CentOS Atomic Host (version 7.20160224) is now available for download[1]. CentOS Atomic Host is a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. These images are available for download at cloud.centos.org. The backing ostree repo is published to mirror.centos.org. CentOS Atomic Host includes these core component versions: - kernel-3.10.0-327.10.1.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - atomic-1.6-6.gitca1e384.el7.x86_64 - kubernetes-1.2.0-0.6.alpha1.git8632732.el7.x86_64 - etcd-2.2.2-5.el7.x86_64 - ostree-2016.1-2.atomic.el7.x86_64 - docker-1.8.2-10.el7.centos.x86_64 - flannel-0.5.3-9.el7.x86_64 Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade Images Vagrant CentOS-Atomic-Host-7-Vagrant-Libvirt.box (421 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box (435 MB) are Vagrant boxes for Libvirt and Virtualbox providers. The easiest way to consume these images is via the Atlas / Vagrant Cloud setup (see https://atlas.hashicorp.com/centos/boxes/atomic-host) For example, getting the VirtualBox instance up would involve running the following two commands on a machine with vagrant installed: $ vagrant init centos/atomic-host && vagrant up --provider virtualbox ISO The installer ISO (742 MB) can be used via regular install methods (PXE, CD, USB image, etc.) and uses the Anaconda installer to deliver the CentOS Atomic Host. This image allows users to control the install using kickstarts and to define custom storage, networking and user accounts. This is the recommended option for getting CentOS Atomic Host onto bare metal machines, or for generating your own image sets for custom environments. QCOW2 The CentOS-Atomic-Host-7-GenericCloud.qcow2 (1 GB) image is suitable for use in on-premise and local virtualized environments. We test this on OpenStack, AWS and local Libvirt installs. If your virtualization platform does not provide its own cloud-init metadata source, you can create your own NoCloud iso image. Amazon Machine Images Region Image ID ------ -------- us-east-1 ami-e6d5e88c us-west-2 ami-3fb05d5f us-west-1 ami-fd62129d eu-west-1 ami-451ea236 eu-central-1 ami-ce8663a1 ap-southeast-1 ami-6c4c850f ap-northeast-1 ami-c74644a9 ap-southeast-2 ami-bae8ced9 ap-northeast-2 ami-5732fc39 sa-east-1 ami-059d1f69 SHA Sums d4e43826fc9f641272e589dfb8d979cd592809b34cdbdaee8b7abc9a09ff30d2 CentOS-Atomic-Host-7.1602-GenericCloud.qcow2 33bd4f732c2857c698bd00bc6db29ae2a4d7d0b768f0353d4e28a5c5ab1c999e CentOS-Atomic-Host-7.1602-GenericCloud.qcow2.gz ee9d9b4d78906ea9c33b0b87c8ad3387e997b479626e64ffedfd3f415a84cded CentOS-Atomic-Host-7.1602-GenericCloud.qcow2.xz 39a548f95022a9ab100d64dbf3579d40c66add1bc56ca938b7dba38b73c2ea87 CentOS-Atomic-Host-7.1602-Installer.iso 2f965b2a502c3839b6be84dee5ee4e60328d9f074e1494ded58b418a309df060 CentOS-Atomic-Host-7.1602-Vagrant-Libvirt.box bc976d197cac629fd68a6d8faf6bcfaeca8afd0020bf573ef343622a7ae1581b CentOS-Atomic-Host-7.1602-Vagrant-Virtualbox.box Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG, based on upstream work from Project Atomic. If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and you'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel mailing list. Have questions about using Atomic? See the atomic mailing list or find us in the #atomic channel on Freenode.

1 0

[StorageSIG] ceph on centos6
by daniel.vanderster＠cern.ch 26 Feb '16

26 Feb '16

Hi all, I've been directed here by ktdreyer in the ceph-devel irc. Today we learned that ceph hammer is no longer being built for centos6, so we won't be getting 0.94.6 or newer. AFAICT, it was dropped due to complications in their build system: https://github.com/ceph/ceph-build/commit/42c7cb3f412e9fc1f525a037f07697fc8… Would it make sense for the Storage-SIG to build hammer on centos6? Technically it should be doable -- but would you guys need some help getting this going? Eventually (client only) builds of jewel on el6 would be really nice to have, but I don't yet know if that's even possible. Cheers, Dan van der Ster CERN IT Storage Group Ceph Community "Academic Liaison"

3 2

Cloud images: what's current / release notes / hashes?
by Beni Paskin-Cherniavsky 26 Feb '16

26 Feb '16

Hi. [Follow up from https://github.com/openshift/openshift-ansible/issues/1384] I did not RTFM, this is a fresh-eyes-I-just-want-to-download-an-image perspective... Looking at http://cloud.centos.org/centos/7/images/, I see -1602 is latest version. - If for some reason I want to use the unversioned CentOS-7-x86_64-GenericCloud.* files, it's hard to be sure what I'll get (other than by downloading => I am getting 1602). - sha256sum.txt{,.asc} contain no hashes for the unversioned files. File size does suggest it's 1602. Ideally the file listing would actually show them as "name -> target" symlink, and/or downloading would return an HTTP redirect to the current version. Currently it returns the content directly, only identifying headers are `Last-Modified: Tue, 23 Feb 2016 17:53:08 GMT` and `ETag: "fcc0480-52c739f3d2900"` (for the .xz). [Be careful with redirect: some scripts/libraries by default don't follow them, e.g. any script using `curl` without `-L` would break :-(] - http://cloud.centos.org/centos/7/images/sha256sum.txt{,.asc} are not available over HTTPS. I can verify the hash but I can't trust the hash itself. That's what .asc is signed for, but lazy folks like me don't necessery know which key to trust... (`gpg --search-keys F4A80EB5` worked but then `gpg --verify` says "WARNING: This key is not certified with a trusted signature!". No idea what that means - I'm clueless with GPG; trusting https://cloud.centos.org would be trivial for me.) Looking at https://wiki.centos.org/Download: - It only links to the unversioned cloud images, doesn't say it's 1602 (other places on that page give the impression everything 7 is 1511), and doesn't list hashes. - I don't see a link to release notes for cloud images; https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 is for 1511 and only talks of the regular ISOs. https://wiki.centos.org/Cloud doesn't mention any specific versions, release notes or hashes either. Googling "centos cloud 1602" didn't lead me to any "official" announcement. Nothing on centos-announce this February. Is -1602 "officially" released? (I personally don't really care, but "what changed" is the first natural question people ask beyond "I just want the latest"...) Hope this is useful feedback.

3 4

Automated build failures on dockerhub
by Jim Perrin 25 Feb '16

25 Feb '16

Those of you using the automated build functionality of docker's hub may have been experiencing some build failures lately. It appears that docker has migrated to something using a different graph driver on the back-end or have otherwise limited the capabilities available during the build process. The result is that builds with packages like httpd will fail, because they require the cap_set_file privilege as part of the install process. There have been a few bugs filed with the Docker folks for this, but I don't know what the end result of this will be. For now, if you use the automated build framework on dockerhub, be aware that your builds may fail, and it's outside our control. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

[unscheduled outage] : DevCloud
by Fabian Arrotin 25 Feb '16

25 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Today in the evening we suffered from a big power outage that affected some of our infra services. Some small public services like : - - planet.centos.org - - seven.centos.org were down, but connection was restored and services back online. We had to spend more time on the DevCloud setup (https://wiki.centos.org/DevCloud) : we first had to verify the underlying block devices and status for that gluster setup (in Distributed/Replicated mode), and then slowly restart the hypervisor controller and then Virtual Machines. From a kvm hypervisor level, all VMs are powered back on, but we haven't verified each VM (and so the status) If you recently deployed some VMs in that DevCloud enviroment, verify that you can still reach your testing VMs. Sorry for the inconvenience. On behalf of the infra team, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlbOSioACgkQnVkHo1a+xU6KSACgmrfAEbzynNR3ef8It7du0e65 /xsAn3OmZZljXugAU31E129Iv58flyfY =xT0k -----END PGP SIGNATURE-----

2 1

[Storage SIG] Ceph Hammer 0.94.5 is out
by François Cami 24 Feb '16

24 Feb '16

Hi, The first release of Ceph Hammer by the Storage SIG is available on CentOS 7 x86_64 for testing purposes. It is mainly intended as a preview release as we are still working on the release process and associated documentation. A quickstart guide is available in the wiki: https://wiki.centos.org/SpecialInterestGroup/Storage/ceph-Quickstart We are of course looking for feedback from potential Ceph users on CentOS, especially from the Virtualization (oVirt), Cloud/RDO and Atomic Host SIGs. Our next steps are updating to 0.94.6, working on CI, and completing the quickstart guide. Co-maintainers are welcome of course! Cheers François

1 0

[Cloud SIG] OpenStack test day, March 10, 11
by Rich Bowen 24 Feb '16

24 Feb '16

TL;DR: * Mitaka 3 test day, March 10, 11: https://www.rdoproject.org/testday/mitaka/milestone3/ * On-site test day in Brno: https://www.rdoproject.org/testday/mitaka/brno-on-site/ * Demo of deploying with TripleO: https://www.youtube.com/watch?v=4O8KvC66eeU Mitaka milestone 3 is scheduled for the week of February 29 - March 4 [1] and, as per usual, we're planning a test day about a week out from that - March 10th and 11th. We've got the usual page of instructions [2] for testing. This time, however, we have two bonus events. First, we're delighted that Eliska Malikova is putting together an on-site test day at the Red Hat office in Brno, for anyone in that general area. If you wish to attend, please register [3] so that we know how much pizza to order. (Attendance is limited to 50, so please register sooner rather than later.) Second, as we attempt to get more people testing TripleO (formerly known as RDO Manager), John Trownbridge (that's Trown on IRC) will be doing a demo of the TripleO Quickstart. This will be conducted as a YouTube live stream [4] and will also be recorded, and available at that same location after the fact. So, please, come help us ensure that Mitaka is the best RDO yet. As usual, we'll be on #rdo (on Freenode IRC), and here on rdo-list, to field any questions. Full details are on the test day website [5] and, a usual, we can use lots of help making the test case instructions better, so that more people can participate. Thanks! --Rich [1] http://releases.openstack.org/mitaka/schedule.html [2] https://www.rdoproject.org/testday/mitaka/milestone3/ [3] https://www.eventbrite.com/e/rdo-on-site-test-day-brno-tickets-5934822213 [4] https://www.youtube.com/watch?v=4O8KvC66eeU [5] https://www.rdoproject.org/testday/mitaka/milestone3/ -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

Koji and aarch64 update
by Thomas Oulevey 24 Feb '16

24 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear All, Following FOSDEM discussion, I owe an update on the koji development for aarch64. Thanks to Fabian, at this we have a builder configured and we are able to build on specific targets for aarch64. I tested few glusterfs builds to ensure all operations are working well and no issue was found. At this time we will support only new builds, it won't be possible to rebuild an old NVR. A future koji update may help us with this requirement. ("merge scratch build" feature seems absent from latest release, I discussed it with Mike at Fosdem, I'll send an update when I have more news). In practice it means you will have to bump your release for getting aarch64 The last missing bit for enabling aarch64 for SIGs is to have a common URL for all arches. In koji an external repository can be defined with a $arch paramter in the url. http://mirror.centos.org/altarch/7/os/$arch/ Unfortunately at this time we have not a single URL that presents all $arch (previous link misses x86_64). After discussing with the team, the easier way would be to add a x86_64 link (e.g : http://mirror.centos.org/altarch/7/os/x86_64 pointing to http://mirror.centos.org/centos-7/7/os/x86_64/ ) for the internal koji mirror as it would solve all our issues. The pro is this solution will allow us to reconfigure koji once and be compatible for all future arches. The con is that mock configs generated by koji won't work for external users. Let me know if you have a better idea or some concerns. As soon as we agree on a solution I'll be able to enable it for the Storage SIG glusterfs targets as Niels De Vos "agreed" to be our first user :) - -- Thomas 'alphacc' Oulevey -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iF4EAREIAAYFAlbERAQACgkQXU8JKmZfxovZCwD/S6B6A4ICpDAKg+IeIlMhS06y 6/vPh8FyhRMTahzdU2oA/0j/SwEBr6zYOm7RP42petsNvU+fL+FKoJFEnQFqQuLn =EGqh -----END PGP SIGNATURE-----

3 3

rebuilding packages for ppc
by Bryson Lee 23 Feb '16

23 Feb '16

In order to get an in-house 32-bit ppc application running on CentOS 7, I've been rebuilding a number of SRPM's from 7.2.1511 on vault.centos.org. I'm down to three packages (glibc, gcc, and mesa) needing rebuilds to resolve "Protected multilib" errors when installing the Yum group that defines my application's "platform". Each of these three is failing to rebuild in different ways, so I'm looking for some pointers as to what I'm doing wrong. For glibc, the failure is that rpmbuild finds a number of installed but unpackaged files in the buildroot under /usr/lib/debug. I've tried setting a debuginfo-related macro in the mock.cfg, but I don't see that setting in the glibc mock.cfg on buildlogs.centos.org, so I think that might be a red herring. For gcc, mock fails to set up the chroot because it can't find a package to provide /usr/lib64/libc.so (which is called out explicitly in a BuildRequires), even though the mock.cfg includes a repo containing glibc-devel.ppc64 and glibc.ppc64. For mesa, the configure test for DRI3PROTO fails with dri3proto >= 1.0 not found. The F19 ppc backing repo I'm using has packages for Mesa 9.x, whereas 7.2.1511 is at Mesa 10.x. I'm guessing that some sort of manual intervention is needed to bootstrap across the major-version bump, but I haven't been able to work out the sequence. I realize that ppc RPM's are in the cards, but I'm trying to do as much risk-reduction as I can due to an internal deadline. Any hints as to what I'm missing on these three packages would be greatly appreciated. Thanks, -Bryson ________________________________ This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any attachments.

2 5

Reminder: Virt SIG meeting today at 1500 UTC (note changed time)
by George Dunlap 23 Feb '16

23 Feb '16

Just a reminder, we'll be having the regular Virt SIG meeting today at the new time -- 1500 UTC. -George

1 0

Where does Koji get the %{dist} macro for a build?
by Shatil Rafiullah 22 Feb '16

22 Feb '16

For packages built with Koji, where does the the %{?dist} macro come from?

3 3

Request for devcloud account
by Mohammed Zeeshan 22 Feb '16

22 Feb '16

Hi, I need a devcloud account to deploy a pulp/crane setup on the cloud. Thanks -- *Mohammed Zeeshan Ahmed, * B.E Computer Science Engineering Certified IT & Cloud Architect & RHCSA +919986458839 Bengaluru, India

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2016