February 2017 - devel - lists.centos.org

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

NFV SIG - update
by Dave Neary 30 May '17

30 May '17

Hi, There has been a recent resurgence of interest in the NFV SIG, and in the interest of keeping the momentum going, I would like to step aside as SIG char, and recommend that Tom Herbert take over. Tom has taken on the packaging and building of VPP and DPDK-accelerated OVS for OPNFV, and has been active in the SIG in recent weeks, and I think he will help add the structure that has been sorely lacking from me in recent months. I'm not sure what the process is for replacing a SIG chair - can someone let us know, please? Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338

4 4

[Infra] - Pre-announced major outage for several services (please read)
by Fabian Arrotin 08 Mar '17

08 Mar '17

Due to some reorganization at the DC/Cage level, we'll have to shutdown/move/reconfigure a big part of our hosted infra for the following services : - cbs.centos.org (Koji) - accounts.centos.org (auth backend) - ci.centos.org (jenkins-driven CI environment) We're working on a plan to minimize the downtime/reconfiguration part, but at first sight, due to the hardware move of the racks/recabling parts/etc, the announced downtime will be probably ~48h. What does that mean ? That during this window, nobody will be able to build/tests packages, nor be able to triggers automatically CI jobs (important). We don't have the final dates confirmed (yet) but it seems that the migration will be scheduled for March 14th. We'll keep you informed when we'll have confirmation about those dates. Feel free to answer in this thread, or find us in #centos-devel on freenode. -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 2

Questions about NFV Sig and Repos
by Thomas F Herbert 23 Feb '17

23 Feb '17

I am beginning to look at NFV Sig again and I have a question about the following. Can Centos NFV SIG create a Repo to be visible in mirrors.centos.org that contains DPDK and other packages as well as VPP once that is built in CBS. If so, what is the process for instancing a repo in mirrors.centos.org like the cloud SIG has? Also, do the following packages appear in any of the Repos. Did I miss something? <http://cbs.centos.org/koji/packageinfo?packageID=737>http://cbs.centos.org/koji/packageinfo?packageID=737 <http://cbs.centos.org/koji/packageinfo?packageID=288>http://cbs.centos.org/koji/packageinfo?packageID=288 --TFH -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat*

4 7

Fwd: [rdo-list] [release] RDO Ocata packages released
by Alan Pevec 22 Feb '17

22 Feb '17

---------- Forwarded message ---------- From: "Javier Pena" <javier.pena(a)redhat.com> Date: Feb 22, 2017 18:27 Subject: [rdo-list] [release] RDO Ocata packages released The RDO community is pleased to announce the general availability of the RDO build for OpenStack Ocata for RPM-based distributions, CentOS Linux 7 and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Ocata is the 15th release from the OpenStack project (http://openstack.org) which is the work of more than 2500 contributors from around the world (source http://stackalytics.com/) The RDO community project (https://www.rdoproject.org/) curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG ( https://wiki.centos.org/SpecialInterestGroup/Cloud) The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO, and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. Interesting things in the Ocata release include: - Significant Improvements (https://www.rdoproject.org/ blog/2017/02/testing-rdo-with-tempest-new-features-in-ocata/) to Tempest and Tempest plugin packaging in RDO - The OpenStack-Ansible (https://docs.openstack.org/ releasenotes/openstack-ansible/ocata.html#new-features) project now supports deployment on top of CentOS with the help of RDO-packaged dependencies For cloud operators, RDO now provides packages for some new OpenStack Services: - Tacker (https://docs.openstack.org/developer/tacker/) an ETSI MANO NFV Orchestrator and VNF Manager - Congress (https://docs.openstack.org/developer/congress/ architecture.html): an open policy framework for the cloud - Vitrage (https://docs.openstack.org/developer/vitrage/) the OpenStack RCA (Root Cause Analysis) Service - Kolla (https://github.com/openstack/kolla) The Kolla project provides tooling to build production-ready container images for deploying OpenStack clouds Some other notable additions: - novajoin (https://github.com/openstack/novajoin) a dynamic vendordata plugin for the OpenStack nova metadata service to manage automatic host instantiation in an IPA server - ironic-ui (https://docs.openstack.org/developer/ironic-ui/) a new Horizon plugin to view and manage baremetal servers - python-virtualbmc (https://github.com/openstack/virtualbmc) VirtualBMC is a proxy that translates IPMI commands to libvirt calls. This allows projects such as OpenStack Ironic to test IPMI drivers using VMs. - python-muranoclient (https://github.com/openstack/python-muranoclient) a client for the Application Catalog service. - python-monascaclient (https://github.com/openstack/ python-monascaclient): a client for the Monasca monitoring-as-a-service solution. - Shaker (http://pyshaker.readthedocs.io/en/latest/) the distributed data-plane testing tool built for OpenStack - Multi-architecture support: aarch64 builds are now provided through an experimental repository - enable the RDO 'testing' repositories to get started >From a networking perspective, we have added some new Neutron plugins that can help Cloud users and operators to address new use cases and scenarios: - networking-bagpipe (https://docs.openstack.org/ developer/networking-bagpipe/): a mechanism driver for Neutron ML2 plugin using BGP E-VPNs/IP VPNs as a backend - networking-bgpvpn (https://docs.openstack.org/ developer/networking-bgpvpn/): an API and framework to interconnect BGP/MPLS VPNs to Openstack Neutron networks - networking-fujitsu (https://github.com/openstack/networking-fujitsu) FUJITSU ML2 plugins/drivers for OpenStack Neutron - networking-l2gw (https://github.com/openstack/networking-l2gw) APIs and implementations to support L2 Gateways in Neutron - networking-sfc (https://github.com/openstack/networking-sfc) APIs and implementations to support Service Function Chaining in Neutron >From the Packstack (https://github.com/openstack/packstack) side, we have several improvements: - We have added support to install Panko and Magnum - Puppet 4 is now supported, and we have updated our manifests to cover the latest changes in the supported projects **Getting Started** There are three ways to get started with RDO. - To spin up a proof of concept cloud, quickly, and on limited hardware, try the All-In-One Quickstart (http://rdoproject.org/Quickstart) You can run RDO on a single node to get a feel for how it works. - For a production deployment of RDO, use the TripleO Quickstart ( https://www.rdoproject.org/tripleo/) and you'll be running a production cloud in short order. - Finally, if you want to try out OpenStack, but don't have the time or hardware to run it yourself, visit TryStack (http://trystack.org/) where you can use a free public OpenStack instance, running RDO packages, to experiment with the OpenStack management interface and API, launch instances, configure networks, and generally familiarize yourself with OpenStack. (TryStack is not, at this time, running Ocata, although it is running RDO.) **Getting Help** The RDO Project participates in a Q&A service at ask.openstack.org ( http://ask.openstack.org) for more developer-oriented content we recommend joining the rdo-list mailing list (https://www.redhat.com/ mailman/listinfo/rdo-list). Remember to post a brief introduction about yourself and your RDO story. You can also find extensive documentation on the RDO docs site (https://www.rdoproject.org/documentation) The #rdo channel on Freenode IRC is also an excellent place to find help and give help. We also welcome comments and requests on the CentOS mailing lists ( https://lists.centos.org/) and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net) however we have a more focused audience in the RDO venues. **Getting Involved** To get involved in the OpenStack RPM packaging effort, see the RDO community pages (https://www.rdoproject.org/community/) and the CentOS Cloud SIG page (https://wiki.centos.org/SpecialInterestGroup/Cloud) See also the RDO packaging documentation (https://www.rdoproject.org/packaging/ ). Join us in #rdo on the Freenode IRC network, and follow us at @RDOCommunity (http://twitter.com/rdocommunity) on Twitter. If you prefer Facebook, we're there too (http://facebook.com/rdocommunity) and also Google+ ( http://tm3.org/rdogplus) Cheers, Javier _______________________________________________ rdo-list mailing list rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe(a)redhat.com

1 0

No Paas SIG meeting today
by Troy Dawson 22 Feb '17

22 Feb '17

Due to several key SIG members being gone, thre will be no Paas SIG meeting today. Troy

1 0

Joining OpsTools SIG
by Sandro Bonazzola 22 Feb '17

22 Feb '17

Hi, I'm working close with OpsTool for oVirt project within VIrt SIG and I can help with some of the packaging effort there. According to https://wiki.centos.org/SpecialInterestGroup/OpsTools#line-69 I'm publishing my interest to join the group and applied through FAS2 system to join the group. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 2

CentOS PaaS SIG meeting (2017-02-08)
by Troy Dawson 21 Feb '17

21 Feb '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 08 February 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current StatusI -- rpms --- Pass / No Pass for origin 1.4.1 and openshift-ansible -- Documentation -- Automated testing and Automated rpm building -- images / image building -- Multi-arch - Discussion on having seperate repo for each release -- paas7-openshift-origin-1.4, paas7-openshift-origin-1.5 - Open Floor

2 3

ABI Navigator
by Andrey Ponomarenko 21 Feb '17

21 Feb '17

1 0

CentOS PaaS SIG meeting (2017-02-15)
by Troy Dawson 15 Feb '17

15 Feb '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 15 February 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current StatusI -- rpms -- Documentation -- Automated testing and Automated rpm building -- images / image building -- Multi-arch - Discussion on having seperate repo for each release -- paas7-openshift-origin-1.4, paas7-openshift-origin-1.5 - Open Floor

1 1

[scl.org] [SCLo SIG] new sclo-php* packages available for testing
by Remi Collet 15 Feb '17

15 Feb '17

Additional packages available in centos-sclo-sclo-testing "PHP extension for interfacing with memcached" https://pecl.php.net/package/memcached "PHP extension for interfacing with MessagePack" https://pecl.php.net/package/msgpack For rh-php70 * sclo-php70-php-pecl-msgpack-2.0.2-1 * sclo-php70-php-pecl-memcached-3.0.2-1 (EL-7 only) Notice, from memcached upstream documentation: "Note that support for libmemcached 0.x series has been discontinued and the oldest actively tested version is 1.0.2. It is highly recommended to use version 1.0.18 of libmemcached." So not available for EL-6 (libmemcached 0.31) EL-7 have libmemcached 1.0.16 which is not really perfect. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

New CentOS Atomic Host with Updated Docker, Kubernetes and Etcd
by Jason Brooks 15 Feb '17

15 Feb '17

An updated version of CentOS Atomic Host (tree version 7.20170209), is now available [1], including significant updates to docker (version 1.12.5), kubernetes (version 1.4) and etcd (version 3.0.15). [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download 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. 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: - atomic-1.14.1-5.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - docker-1.12.5-14.el7.centos.x86_64 - etcd-3.0.15-1.el7.x86_64 - flannel-0.5.5-2.el7.x86_64 - kernel-3.10.0-514.6.1.el7.x86_64 - kubernetes-node-1.4.0-0.1.git87d9d8d.el7.x86_64 - ostree-2016.15-1.atomic.el7.x86_64 - rpm-ostree-client-2016.13-1.atomic.el7.x86_64 Containerized kubernetes-master The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. Instead, you can run the master kubernetes components (apiserver, scheduler, and controller-manager) in containers, managed via systemd, using the service files and instructions on the CentOS wiki. [2] The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline, based on Dockerfiles from the CentOS-Dockerfiles repository. [2] https://wiki.centos.org/SpecialInterestGroup/Atomic/ContainerizedMaster These containers have been tested with the kubernetes ansible scripts provided in the upstream contrib repository, and they work as expected, provided you first copy the service files onto your master. 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 and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box 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 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 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-10f53a06 us-west-2 ami-4d9b1c2d us-west-1 ami-4ae1bd2a eu-west-1 ami-1daa8c7b eu-central-1 ami-e8c20987 ap-southeast-1 ami-a8388fcb ap-northeast-1 ami-ba2b67dd ap-southeast-2 ami-1f84857c ap-northeast-2 ami-adbd6dc3 sa-east-1 ami-1f492e73 SHA Sums 6f8b91373c763cf96ffead6ca044ddf6eea5c0b102a239933c112a7f1089396e CentOS-Atomic-Host-7.1701-GenericCloud.qcow2 380dcbdd4514f87f8915fee418cc965985c89a91b9182af622e36ffad26c9e04 CentOS-Atomic-Host-7.1701-GenericCloud.qcow2.gz 0bf3d5ec95d40cee94bc80e7c19206b3a260d2835fa43f1e99965bb8f99a777d CentOS-Atomic-Host-7.1701-GenericCloud.qcow2.xz bc55326e54832e3e08530e41cb738c4b293a7645c960a4c9be7f66024770a68c CentOS-Atomic-Host-7.1701-Installer.iso aaba6ca5e3b0a64abff843bff28eb82092e39fe82f120c76614822334ff22462 CentOS-Atomic-Host-7.1701-Vagrant-Libvirt.box 8d3c64895a40638cb8659186a0caabef9fc10ba944a130eda53f7d2109cfba35 CentOS-Atomic-Host-7.1701-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

python-etcd
by Sebastiaan Glazenborg 14 Feb '17

14 Feb '17

I have a question regarding this package: https://cbs.centos.org/koji/buildinfo?buildID=15088 I do not know much about CentOS package building; does this mean that package python-etcd will be available soon?

3 3

[scl.org] [SCLo SIG] new sclo-php* packages available for testing
by Remi Collet 14 Feb '17

14 Feb '17

Yet another package available in centos-sclo-sclo-testing "PHP extension for interfacing with Redis" A stable version was recently released with PHP 5 and 7 compatibility. For rh-php56 * sclo-php56-php-pecl-redis-3.1.1-1 For rh-php70 * sclo-php70-php-pecl-redis-3.1.1-1 This extension is recommended by ownCloud for distributed cache. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo _______________________________________________ SCLorg mailing list SCLorg(a)redhat.com https://www.redhat.com/mailman/listinfo/sclorg

1 0

[ceph] Hammer 0.94.9 tagged for testing
by David Moreau Simard 13 Feb '17

13 Feb '17

Hi, Please note that Ceph Hammer 0.94.9 has been tagged for testing. The previous release provided in the stable channel of the centos-release-ceph-hammer package provided 0.94.5. To test this new release: yum -y install centos-release-ceph-hammer yum-config-manager --enable centos-ceph-hammer-test This is a straight rebuild from upstream source RPM. For release notes, please refer to upstream [1]. We would like to expedite the release of this new version due to the age of the previous release, 0.94.5 dating back to December 14th 2015. There are also problems running 0.94.5 against a CentOS 7.3 installation under certain circumstances. As such, if there are no objections, we will tag 0.94.9 for release no later than February 13th. [1]: http://docs.ceph.com/docs/master/release-notes/#v0-94-9-hammer David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter]

2 2

ManualInstall fail in first steps
by Andreas Benzler 13 Feb '17

13 Feb '17

Hello while I wanne try out very special partition, i walk through https://wiki.centos.org/HowTos/ManualInstall But fail allready at "INSTALL setup basesystem filesystem" This is very clear to me, because rpm don't know the full path (real version) or is there some thing wrong ?? Very wired. Doesn't looks like up to date. Sincerely Andy

2 1

Missing CentOS 7.3.1611 SRPMS on vault.centos.org
by HAYASHI Kentaro 13 Feb '17

13 Feb '17

Hi, folks. Recently, I've noticed that there is no CentOS 7.3.1611 SRPMS on vault.centos.org. http://vault.centos.org/7.3.1611/ (Empty!) In the contrast, mirror site [1] still keeps them. For example, there are SRPMS on kernel.org which is one of mirrors ( Mirror list information: http://vault.centos.org/readme.txt ) [1] http://archive.kernel.org/centos-vault/7.3.1611/ What happened on vault.centos.org? -- Kentaro Hayashi <kenhys(a)gmail.com>

2 2

DeviceMapper Storage Drive on CentOS7 Atomic Host
by David J. Brewer 08 Feb '17

08 Feb '17

The Atomic Host (CentOS Linux release 7.3.1611 (Core)), the Docker Engine still writes its images to /var/lib/docker even with DeviceMapper as the storage driver. Perplexing. We performed a "rm -rf /var/lib/docker/*" and rebuilt the docker thinpool (lvcreate.... etc.) after the Docker Engine complained. # lvremove cah/docker-pool # lvcreate --wipesignatures y -n docker-pool cah -l 50%VG # lvcreate --wipesignatures y -n docker-poolmeta cah -l 1%VG # lvconvert -y --zero n -c 512K --thinpool cah/docker-pool --poolmetadata cah/docker-poolmeta # lvchange --metadataprofile docker-pool-extend cah/docker-pool # lvchange --metadataprofile cah--docker-pool-extend cah/docker-pool b132d0cfa1a: Waiting 64afa62fe941: Waiting c45ccadbbd13: Waiting 025d185dba2b: Waiting f4a0ea1a1da2: Waiting write /var/lib/docker/tmp/GetImageBlob531020381: no space left on device [root@atomic1 docker]# docker info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 1.10.3 Storage Driver: devicemapper Pool Name: cah-docker--pool Pool Blocksize: 524.3 kB Base Device Size: 10.74 GB Backing Filesystem: xfs Data file: Metadata file: Data Space Used: 19.92 MB Data Space Total: 499.4 GB Data Space Available: 499.4 GB Metadata Space Used: 888.8 kB Metadata Space Total: 9.987 GB Metadata Space Available: 9.986 GB Udev Sync Supported: true Deferred Removal Enabled: false Deferred Deletion Enabled: false Deferred Deleted Device Count: 0 Library Version: 1.02.135-RHEL7 (2016-09-28) Execution Driver: native-0.2 Logging Driver: json-file Plugins: Volume: local Network: bridge null host Kernel Version: 3.10.0-514.2.2.el7.x86_64 Operating System: CentOS Linux 7 (Core) OSType: linux Architecture: x86_64 Number of Docker Hooks: 2 CPUs: 8 Total Memory: 31.26 GiB Name: atomic1.eupraxialabs.com ID: CLGC:SBXV:HWBO:ZA6X:BYIS:RU4D:LIII:2GEJ:ZR4K: As an added measure, we even did an override: [root@atomic1 docker]# cat /etc/systemd/system/docker.service.d/override.conf [Service] ExecStart= ExecStart=/usr/bin/docker daemon --storage-opt dm.thinpooldev=cah-docker--pool Same result. The graphDriver is clearly DeviceMapper. This looks like a bug. [root@atomic1 docker]# systemctl status -l docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/docker.service.d └─flannel.conf /etc/systemd/system/docker.service.d └─override.conf Active: active (running) since Wed 2017-02-08 08:36:32 CST; 1h 22min ago Docs: http://docs.docker.com Main PID: 4626 (docker-current) Memory: 21.2M CGroup: /system.slice/docker.service └─4626 /usr/bin/docker-current daemon --storage-opt dm.thinpooldev=cah-docker--pool Feb 08 08:36:32 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:32.271317883-06:00" level=info msg="Firewalld running: false" Feb 08 08:36:32 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:32.337846499-06:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" Feb 08 08:36:32 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:32.408356956-06:00" level=info msg="Loading containers: start." Feb 08 08:36:32 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:32.408635390-06:00" level=info msg="Loading containers: done." Feb 08 08:36:32 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:32.408684424-06:00" level=info msg="Daemon has completed initialization" Feb 08 08:36:32 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:32.408740148-06:00" level=info msg="Docker daemon" commit=3999ccb-unsupported execdriver=native-0.2 graphdriver=devicemapper version=1.10.3 Feb 08 08:36:32 atomic1.eupraxialabs.com systemd[1]: Started Docker Application Container Engine. Feb 08 08:36:32 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:32.421796182-06:00" level=info msg="API listen on /var/run/docker.sock" Feb 08 08:36:52 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:36:52.352294281-06:00" level=info msg="{Action=create, Username=centos, LoginUID=1001, PID=4701}" Feb 08 08:37:52 atomic1.eupraxialabs.com docker[4626]: time="2017-02-08T08:37:52.430393646-06:00" level=error msg="Download failed: write /var/lib/docker/tmp/GetImageBlob531020381: no space left on device" This looks like a bug in the Docker Storage Driver. Is anyone else experiencing a similar issue? Dave --

1 0

CentOS 7.3 docker image for ppc64le available at Unicamp - Call for testers
by Murilo Opsfelder Araújo 07 Feb '17

07 Feb '17

Hi, CentOS community. We would like to welcome and invite all of you to test and provide us feedback as to the CentOS 7.3 docker image for ppc64le available at ftp://ftp.unicamp.br/pub/ppc64el/centos/7/images/ This tarball can be easily imported into docker with the information shown in the README file. The tarball was created with the following script https://github.com/fabianorosas/centos-docker-ppc64le/blob/master/centos-do… Consider this an early evaluation. We intend to get the required fixes integrated into CentOS so this image can be fully integrated with CentOS Registry. We would be glad to hear from you! Thanks! -- Murilo

3 4

test builds on private server (drivers, kernel, media, mesa, winehq, java)
by Andreas Benzler 07 Feb '17

07 Feb '17

Hello Guys, this is a duplicate from the standard centos(a)centos.org mailing list. MIght be interest for a developer. Thanks ... from christmas till now I updated follow packages in my privated builds: http://centos.cms4all.org/repo/7/ Drivers: libdrm 2.4.75 (update) vulkan 1.0.3 Kernel: 4.9.1 & firmware (update) Media: Kodi 17.0 + pvr addons & vlc 2.2.4 (update) Mesa: 13.0.4 with d3dadapter and vulkan (update) WineHQ: wine 2.0.1 & wine-stage 2.0.1 (update), winetricks http://centos.cms4all.org/repo/java/ Oracle Java 1.8.0 121 Netbeans 8.2.1 Sincerely Andy PS: This are no signed packages, but the source

3 3

Re: [CentOS-devel] CentOS-devel Digest, Vol 144, Issue 5
by Andreas Benzler 06 Feb '17

06 Feb '17

Good evening, A few words to my repository. First I have gstreamer in as far as multimedia enabled so totem most, or all mine, Fromat plays off. Driver section was necessary because I installed Centos on flexible media and wanted to access the latest drivers. And yes it works to 99%. At Home, on my laptops and business pc. I have created the Repostorie to have a backup. Why should I not make my work available? Why should not others benefit from it and when they need it? Why not fedora? Have no desire to reinvent my desktop every 18 months. In the past, I had the opportunity to get evolution in the version 3.4 under Centos 6 with gnome 2.34 to run, because I am professionally connected to an exchange. And also this has worked with the keyring of gnome 2.3. Funny, isn't it? Who likes to sit alone at home and strive for a "his" stablies, usable system. I do not like the copyright of Ubuntu. Sometimes I get on better with RPMS. What would I like to do better with it? A matrix over the repository is built on. You can only use Drivers and the rest not. Wine, however, needs almost everyone. And who adds the repository "Other" just like "gnome mutter" with patched shadows. Therefore, a matrix would be cool. Good night. Andy Am Montag, den 06.02.2017, 12:00 +0000 schrieb centos-devel-request(a)centos.org: > Send CentOS-devel mailing list submissions to > centos-devel(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos-devel > or, via email, send a message with subject or body 'help' to > centos-devel-request(a)centos.orgYou can reach the person managing the list at > centos-devel-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS-devel digest..." > > > Today's Topics: > > 1. Re: test builds on private server (drivers, kernel, media, > mesa, winehq, java) (Akemi Yagi) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 5 Feb 2017 11:20:21 -0800 > From: Akemi Yagi <amyagi(a)gmail.com> > To: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Subject: Re: [CentOS-devel] test builds on private server (drivers, > kernel, media, mesa, winehq, java) > Message-ID: > <CABA31DqUi9qXywUU+j=FKg8wr2FgN5msmGxX10AAz-1_T5vxvQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Sat, Feb 4, 2017 at 1:33 PM, Andreas Benzler <andreas(a)benzlerweb.de> wrote: > > Hello Guys, > > > > this is a duplicate from the standard centos(a)centos.org mailing list. > > > > MIght be interest for a developer. Thanks ... > > > > from christmas till now I updated follow packages in my privated builds: > > > > http://centos.cms4all.org/repo/7/ > > > > Drivers: libdrm 2.4.75 (update) > > vulkan 1.0.3 > > > > Kernel: 4.9.1 & firmware (update) > > > > Media: Kodi 17.0 + pvr addons & vlc 2.2.4 (update) > > > > Mesa: 13.0.4 with d3dadapter and vulkan (update) > > > > WineHQ: wine 2.0.1 & wine-stage 2.0.1 (update), winetricks > > > > http://centos.cms4all.org/repo/java/ > > > > Oracle Java 1.8.0 121 > > Netbeans 8.2.1 > > > > Sincerely > > > > Andy > > > > PS: This are no signed packages, but the source > > I assume you are offering those packages for public consumption, not > building just for personal use. If this is the case, I'd like to > suggest that you use a unique tag for your packages rather than the > .centos tag. In the past i was think about to take another tag for the packages and to sign that. But unfortunately my leisure time is limited and therefore I have not implemented it so far. Pick my rpm up. change it and let him run through mock. Everyone by hand. > Regarding the kernel, I see that it was rebuilt from ELRepo's > kernel-lt with modification(s). You may want to provide details on how > your kernel is different from kernel-lt [1] or kernel-ml [2] and how > you plan to maintain it. Everybody can use elrepo. I built it most time vanille, but got it handy in the "box". > [1] http:elrepo.org/tiki/kernel-lt > [2] http:elrepo.org/tiki/kernel-ml > > Akemi > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > > > ------------------------------ > > End of CentOS-devel Digest, Vol 144, Issue 5 > ********************************************

1 0

[Virt SIG] escalating 0012768: [ppc64le] build libvirt-daemon-kvm for 2.0.0-10.el7_3.4 for ppc64le to satisfy oVirt deps
by Sandro Bonazzola 05 Feb '17

05 Feb '17

hi, I'd like to escalate https://bugs.centos.org/view.php?id=12768 for oVirt / Virt SIG. Right now x86_64 and ppc64le are shipping different versions of libvirt causing failures in ppc64le deployments / upgrades. Any chance I can help getting the new libvirt pushed to ppc64le repos? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 2

[SCLo SIG] new sclo-php* packages available for testing
by Remi Collet 03 Feb '17

03 Feb '17

Yet another package available in centos-sclo-sclo-testing "Provides a wrapper to the ImageMagick library." A stable version was just released with PHP 5 and 7 compatibility. For rh-php56 (updated from 3.3.0): * sclo-php56-php-pecl-imagick-3.4.3-1 For rh-php70 (new package): * sclo-php70-php-pecl-imagick-3.4.3-1 Notice: this extension uses system ImageMagick 6.7.8.9 (EL-7) or 6.7.2.7 (EL-6), so only feature available in these library versions will be available in the PHP extension. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

New ansible in Paas testing repo
by Troy Dawson 02 Feb '17

02 Feb '17

Hi, As many of you might have found out, ansible 2.2.1.0, which fixes a security update, broke openshift-ansible. We have built a new ansible that has been patched to not break openshift-ansible. It is in the Paas testing repo. Please give it a try, see if it fixed your openshift-ansible troubles that happened with the ansible update. ansible-2.2.1.0-2.el7 Thanks Troy

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2017