devel June 2017

devel@lists.centos.org

42 participants
34 discussions

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

19 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

Re: [CentOS-devel] Azure Cloud Images
by Patrick Laimbock 14 Jun '17

14 Jun '17

On 18-05-17 20:02, lkd-centos(a)sky-haven.net wrote: > On 2017-05-18 12:58, Patrick Laimbock wrote: >> On 17-05-17 13:38, Akshay Kumar wrote: >>> Hi, >>> >>> We use the Cloud Generic Images >>> from https://cloud.centos.org/centos/7/images/ as a basis for making >>> custom images for AWS, GCP and Azure. >>> >>> It was great to see an Azure image that includes WALinuxAgent but 1703 >>> and 1704 don't work at all. Here's the bug report: >>> >>> https://bugs.centos.org/view.php?id=13264 >> >> Can you please do the conversion with qemu-img-ev from the Virt SIG >> and try again? The qemu-img-ev repo rpm can be found here: >> >> https://cbs.centos.org/koji/packageinfo?packageID=1950 > > Hi, > > There's nothing wrong with the image proper; the VM actually starts and > one can log in (if the starting image is unwrapped and deliberately > bugged with a hardcoded username/password first), it responds to SSH, etc. > > What doesn't happen is: waagent doesn't start because it hasn't been > `systemctl enable`'ed. Thanks for clarifying that the image boots properly. A new image with a fix will be generated. When it's ready (I don't know when as I'm not involved in that process) it should show up at: http://cloud.centos.org/centos/7/images/ HTH, Patrick

3 3

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

14 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, 14 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 -- Finding new head chairman for PAAS SIG Minutes from last meeting: https://www.centos.org/minutes/2017/june/centos-devel.2017-06-07-17.00.log.… Meeting:

1 0

Running openshift on arm64
by Mohammed Ahmed 14 Jun '17

14 Jun '17

Hi, I was wondering if it was possible to deploy openshift on arm64. We need this for building containers on the CentOS Container Pipeline. I am aware that there was some talk around rpms for the same, and it would be helpful if someone could point us to any resources. -- *Mohammed Zeeshan Ahmed* Associate Software Engineer, Redhat Developers Team (Devtools) http://mohammedzee1000.wordpress.com https://mojo.redhat.com/people/moahmed RED HAT | DIFFERENT FOR THE SAKE OF BETTER TECHNOLOGY Find out why every airline, telecom, commercial bank, healthcare, and financial data services company in the Fortune 500 relies on Red Hat. Trusted | Red Hat <https://www.redhat.com/en/about/trusted>

2 1

LinchPin v1.0.1 (bugfix) has been released
by Clint Savage 12 Jun '17

12 Jun '17

Hi all, We are happy to announce that LinchPin v1.0.1 has been released. This is a bugfix release, which fixed the following issues: #263 - linchpin destroy duffy error after 1.0 upgrade #264 - 1.0 error with linchpin init/linchpin up #267 - linchpin rise/up error since upgrade to 1.0.0 #269 - libvirt provisioning does not work on centos/rhel machines #271 - Unable to get topology file to pass schema validation #274 - Authorization failing with linchpin 1.0.0 #275 - Inventory generation fails as resource outputs are not generated One enhancement was included: #280 - Make a default path for credentials The official release notes are available at https://github.com/CentOS- PaaS-SIG/linchpin/blob/develop/docs/source/release/RELEASE_1_0_1.rst This update is available via PyPi and packages will be available as soon as possible. If you discover any errors or regressions, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues). Cheers and enjoy! Clint Savage LinchPin Maintainer/Senior Software Engineer Red Hat twitter: @herlo, github: herlo, IRC: herlo

1 0

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

07 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, 07 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 -- separate repo work -- minishift - Open Floor -- Finding new chairman for PAAS SIG

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2017