devel

devel@lists.centos.org

2 participants
4591 discussions

CentOS PaaS SIG meeting (2017-06-21)
by Troy Dawson 21 Jun '17

21 Jun '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 21 June 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- Multi-arch -- minishift (marcindulak and lalatenduM) - Open Floor

1 0

CentOS Linux images for Vagrant updated to address "stack clash"
by Laurentiu Pancescu 21 Jun '17

21 Jun '17

Hi there, we have just released version 1705.02 of the official CentOS Linux images for Vagrant (centos/6 and centos/7) on Atlas. This update contains the security fixes for the "stack clash" vulnerability. https://access.redhat.com/security/vulnerabilities/stackguard https://blog.qualys.com/securitylabs/2017/06/19/the-stack-clash Existing images can be upgraded in-place via "sudo yum update". Best regards, Laurențiu

2 1

CentOS Atomic Host upgrade for CESA-2017:1484 kernel Security Update
by Jason Brooks 21 Jun '17

21 Jun '17

We've upgraded the ostree repo for CentOS Atomic Host (v7.1705.1) to include the packages affected by this advisory. You can upgrade your CentOS Atomic Host to this version with the command: atomic host upgrade --reboot Upgraded: ca-certificates 2017.2.11-70.1.el7_3 -> 2017.2.14-70.1.el7_3 glibc 2.17-157.el7_3.2 -> 2.17-157.el7_3.4 glibc-common 2.17-157.el7_3.2 -> 2.17-157.el7_3.4 kernel 3.10.0-514.21.1.el7 -> 3.10.0-514.21.2.el7 python-perf 3.10.0-514.21.1.el7 -> 3.10.0-514.21.2.el7 rpcbind 0.2.0-38.el7_3 -> 0.2.0-38.el7_3.1 ---------- Forwarded message ---------- From: Johnny Hughes <johnny(a)centos.org> Date: Tue, Jun 20, 2017 at 8:31 AM Subject: [CentOS-announce] CESA-2017:1484 Important CentOS 7 kernel Security Update To: centos-announce(a)centos.org CentOS Errata and Security Advisory 2017:1484 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1484.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 5bf01ddf86b01221e0958422ec627961d035551e0474ac10245dc4958800705f kernel-3.10.0-514.21.2.el7.x86_64.rpm 232a0f622143e55d9011f3808471aad219396cccd156f24687b156b6d432a608 kernel-abi-whitelists-3.10.0-514.21.2.el7.noarch.rpm 967dc375e96b08d16737aad6d9630e6b47903dd02ce6d7a916c741eee78afc51 kernel-debug-3.10.0-514.21.2.el7.x86_64.rpm e68aa2a3377cdf058843658dbf4447d0091538891b0fa1bcd79c1a0dd2c9ce34 kernel-debug-devel-3.10.0-514.21.2.el7.x86_64.rpm 5000ca51295103b942c4941a5d2e53a6a78aadc08708d32c2ace22c227a58c4d kernel-devel-3.10.0-514.21.2.el7.x86_64.rpm ad28e256a053af55c9167e6d4ef737bf334b128df16cddc023e845c9f6a94480 kernel-doc-3.10.0-514.21.2.el7.noarch.rpm 62b49e8818f09e2833753e8bd1d861aa36a05b1f8982adcb80bf7f5cc9c8af24 kernel-headers-3.10.0-514.21.2.el7.x86_64.rpm 4a5b113ba6761d64045250d364470007c8961d8f374d4321bd3db24c629c4a9b kernel-tools-3.10.0-514.21.2.el7.x86_64.rpm 2c4d3a43385253a681618b4d0135753d893bd312fb82f19eb4d958c713d28bb9 kernel-tools-libs-3.10.0-514.21.2.el7.x86_64.rpm 7bc126ec06ffde55cf2217eb43cc44fdf96628131a5806f6303faad8e6b63252 kernel-tools-libs-devel-3.10.0-514.21.2.el7.x86_64.rpm 9d55662dadce103200676da60fce559da8d9bacea7fc38930e461c2a52665a7b perf-3.10.0-514.21.2.el7.x86_64.rpm d9ef263dba6b41ad7d4e1282a63ae04a1614788a1988485455448c0cf0034eb8 python-perf-3.10.0-514.21.2.el7.x86_64.rpm Source: 3235af92f1e1681e86df0c33bf822a56c7f9f54bdb88746dffb8764cf8bc7db5 kernel-3.10.0-514.21.2.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce

1 0

Using atomic-openshift-installer to upgrade from origin 1.4 to 1.5
by Jean-Francois Chevrette 20 Jun '17

20 Jun '17

Hi, 3 months ago I have used atomic-openshift-utils/installer to setup two OpenShift origin 1.4 clusters. Today I discovered that I am unable to upgrade from 1.4 to 1.5 because atomic-openshift-installer states that "No upgrades available for origin 1.4" atomic-openshift-utils-3.5.71-1.git.1.640cb7d.el7.noarch centos-release-openshift-origin15-1-1.el7.centos.noarch openshift-ansible-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-callback-plugins-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-docs-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-filter-plugins-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-lookup-plugins-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-playbooks-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-roles-3.5.71-1.git.1.640cb7d.el7.noarch 1.5 is in the list of supported install variants here: /usr/lib/python2.7/site-packages/ooinstall/variants.py However the UPGRADE_MAPPINGS list in /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py only has upgrade paths for 3.4 and 3.5 Is upgrading between origin releases simply not supported/possible? Thanks, Jean-Francois C.

2 1

Please allow me to introduce myself...
by Al Stone 20 Jun '17

20 Jun '17

Howdy. I've recently had the desire to get more involved in the CentOS community -- both from professional and personal interests. So, please allow me to introduce myself to both CentOS folks, and to storage folks in particular. I have two goals, really: (1) make sure that Ceph upstream builds from scratch on aarch64 and ppc64le; that also means making sure that initial tests (i.e., make check) pass and that ultimately the full test suite passes; (2) make sure that the CentOS packages are as close to upstream as possible. For the first goal, the idea would be to work with upstream or anyone else to fully support more than just x86, even for development work. That's going to take a while since I'm new to the Ceph community but eager to join in; I've spent several years working with file systems and look forward to growing that knowledge. For the second goal, I would hope to be able to assist the current maintainer for Ceph packages and broaden the availability of Ceph. Since I'm really just getting started on the upstream work, I haven't jumped into this part yet. By the same token, though, I do have some experience as a Debian Developer and as a Fedora Packager that could be of use. I've also got the same goals for Fedora (eventually), and I am approaching it the same way -- make sure upstream is solid and stable on all architectures, and then make sure the packages are as up-to-date as they can be. As far as my personal background goes, I was literally a rocket scientist for a while, working on guidance algorithms for the flight systems. I've also been involved with Linux on some level for about two decades. The last few years have seen a lot of kernel work on ARMv8 (I drove the implementation of the ACPI subsystem for servers), and before that a port of the BSD file system to a proprietary OS that had to support asynchronous operations but had no real concept of processes or even tasks. Before that was a smattering of all sorts of things -- compiler work, tech support, technical consulting, the Andrew file system, the NCS (Network Computing System -- that probably dates me some :), and even some management (I swear I have fully recovered from that). Thanks for your time and patience in getting this far; I look forward to working with the community and helping to build a better CentOS. -- ciao, al ----------------------------------- Al Stone Software Engineer Red Hat, Inc. ahs3(a)redhat.com -----------------------------------

3 2

HPC SIG: IT4Innovations Ostrava - Supercomputer visit notes
by Jan Chaloupka 20 Jun '17

20 Jun '17

Sharing notes from a visit in IT4Innovations center in Ostrava. Supercomputer parameters info are available at [1] - mixture of Xeon, Xeon Phi and graphic card cores. Two clusters - Anselm runs RHEL 6, Salomon runs CentOS 6. Each node runs on a specific piece of a hardware. If a project is built on a builder of a different hardware, it is built with different flags and configuration and the resulting binaries are not properly optimized. Some projects need special features of compilers in order to run efficiently. Some of the features are available only in the latest versions of compilers. By the time the latest versions get into builders, it is usually to late. Or a project needs to be built with a proprietary compiler that is not publicly available. Or given each project needs different version of system libraries in general, the HPC infrastructure needs to offer various versions of the same library. The software needs to be available in many flavors. It means the same software to be built with multiple compilers and multiple versions. Different versions have different properties/features. Different compilers accent/provide different optimizations. Thus, a matrix of software to provide the users with. At the end a software needs to be built for the end-system architecture so it can use all the available instructions not to slow down the computation. For that reason (and many others) all the projects need to be built locally inside the cluster. That makes most of the binary packages in CentOS distribution unusable for the HPC use cases.Only usecase for rpm as proof of concepting on devel laptops is useful, not for final deployments.Currently, the EasyBuild project [2] is used as a replacement for rpm based spec files.Operators use Fedora upstream monitoring tool to monitor latest&greatest software (atm. ~400+ projects). Infiniband is usedfor connection of the nodes, sometimes issues with 3rd party SW drivers (Bull/Atos and/or HPE). Other notes: - Lot of service providers are still running on CentOS 6, which blocks upgrade to CentOS 7- shutdown of cluster not possible, infra for clusters changed between RHEL 6 and RHEL 7. - Puppet and Ansible used to deploy clusters (Ansible for disk-free nodes, Puppetfor nodes with disks). Still, each deployment is unique (e.g. unexpected situations) and thus not fully automated.For Ansiblepart,there is no roleusedfromthe AnsibleGalaxy - just Core modules and custom roles and playbooks - Experiments with containers as well via Singularity [3] (Docker is not fully supported on CentOS 6, needs privileged user account) - Demand on packaging and providing tooling for HPC rather than libraries themselves. If possible, provide full HPC stack that is upstream and distribution supported/maintained (including full stack upgrades). CI/CD supported as well. - HPC community is unfortunately security free, security fix deployment can take several months, dependencies on specific minor releases or kernel versions. Kernel KABI whitelist should be advised to 3rd party vendors of drivers to prevent hard version deps - Each assigned set of nodes is expected to be vanilla new. Given it takes some time before a node is rebooted (order of minutes), all the tooling running inside a node must clean everything a user task left. Thus, minimize a number of times a node is really rebooted. [1] https://docs.it4i.cz/salomon/hardware-overview/ [2] https://github.com/hpcugent/easybuild [3] http://singularity.lbl.gov/

4 3

New CentOS Atomic Available for Download
by Jason Brooks 19 Jun '17

19 Jun '17

An updated version of CentOS Atomic Host (tree version 7.1705), is now available[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: - atomic-1.17.2-4.git2760e30.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - docker-1.12.6-28.git1398f24.el7.centos.x86_64 - etcd-3.1.7-1.el7.x86_64 - flannel-0.7.0-1.el7.x86_64 - kernel-3.10.0-514.21.1.el7.x86_64 - kubernetes-node-1.5.2-0.6.gitd33fd89.el7.x86_64 - ostree-2017.5-1.el7.x86_64 - rpm-ostree-client-2017.5-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. 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. 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. Alternatively, you can install the kubernetes-master components using rpm-ostree package layering using the command: atomic host install kubernetes-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-90e7c686 ap-south-1 ami-2ba1de44 eu-west-2 ami-2b44524f eu-west-1 ami-a6c5dbc0 ap-northeast-2 ami-87ba65e9 ap-northeast-1 ami-64868e03 sa-east-1 ami-f9197295 ca-central-1 ami-66e55a02 ap-southeast-1 ami-850a88e6 ap-southeast-2 ami-caf7e6a9 eu-central-1 ami-42e84f2d us-east-2 ami-89bb9dec us-west-1 ami-245b7644 us-west-2 ami-68818a11 SHA Sums 46082267562f9eefbc4b29058696108f07cb0ceb2dafe601ec5d66bb1037120a CentOS-Atomic-Host-7.1705-GenericCloud.qcow2 1bd6dfbe360be599a45734f03b34e08cc903630327e1c54534eb4218bf18d0da CentOS-Atomic-Host-7.1705-GenericCloud.qcow2.gz aa4a3ac057d3ea898bea07052aa9fd20c7ca7ea3c8a5474bca9227622915e5e2 CentOS-Atomic-Host-7.1705-GenericCloud.qcow2.xz d99c2e9d1d31907ace3c1e54fc3087ebb9d627ca46168f7e65b469789cd39739 CentOS-Atomic-Host-7.1705-Installer.iso cfd6a29e26e202476b6a2dc54b1b31321688270a6cc6a9ef4206ac0ebd0e309c CentOS-Atomic-Host-7.1705-Vagrant-Libvirt.box d9b5f965f637a909efa15cd43063729db002c012c81a8cde0de588ea0932f970 CentOS-Atomic-Host-7.1705-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

[SCLo SIG] new sclo-php*-php-pecl-amqp packages available for testing
by Remi Collet 16 Jun '17

16 Jun '17

Yet another package available in centos-sclo-sclo-testing (requested by some users) This extension can communicate with any AMQP spec 0-9-1 compatible server, such as RabbitMQ, OpenAMQP and Qpid, giving you the ability to create and delete exchanges and queues, as well as publish to any exchange and consume from any queue. https://pecl.php.net/package/amqp For rh-php56 * sclo-php56-php-amqp-1.9.1-1 For rh-php70 * sclo-php70-php-amqp-1.9.1-1 Notice: this package doesn't requires "librabbitmq" which is not available in base repository (only in EPEL), but use a static library instead. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

Setting up CentOS Container-Pipeline to build AArch64 images
by Bamacharan Kundu 15 Jun '17

15 Jun '17

Hi, We are planning to build AArch64 images in centos community container pipeline[1]. We were trying to setup one POC on this today. We got stuck in few points. 1. We could not find openshift-orgin RPM or container to use for pipeline. 2. Docker complains with go panic to build ARM64 images in X86_64 box or X86 image in Aarch64 box. how could we get openshift-origin (either on package or as container) running in Aarch64? Any thoughts please. Regards Bamacharan [1] https://github.com/CentOS/container-pipeline-service

3 4

Boot aarch64 VM on x86_64 host
by Dharmit Shah 15 Jun '17

15 Jun '17

I'm trying to $subject using CentOS 7.3 system. I took a cue from the blog [0] on https://seven.centos.org and tried doing it with virt-install. However, the installation process doesn't really begin and I don't see any error either. Here's [1] the stdout when I run virt-install. And the list of packages [2] related to libvirt, qemu, kvm, arm. Can someone help me understand what I'm doing wrong? [0] https://seven.centos.org/2016/07/running-virtual-machines-on-aarch64/ [1] http://pastebin.centos.org/108011/ [2] http://pastebin.centos.org/108021/ Regards, Dharmit.

2 1

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