devel

devel@lists.centos.org

10 participants
4617 discussions

Start a nNew thread

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel