devel

devel@lists.centos.org

10 participants
4625 discussions

New CentOS Atomic Host Available for Download
by Jason Brooks 11 Oct '16

11 Oct '16

An updated version of CentOS Atomic Host (tree version 7.20161006), is now available, featuring the option of substituting the host's default docker 1.10 container engine with a more recent, docker 1.12-based version, provided via the docker-latest package. 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. For download links and more information, see the CentOS Atomic Download page on the CentOS wiki: https://wiki.centos.org/SpecialInterestGroup/Atomic/Download CentOS Atomic Host includes these core component versions: - atomic-1.10.5-7.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - docker-1.10.3-46.el7.centos.14.x86_64 - etcd-2.3.7-4.el7.x86_64 - flannel-0.5.3-9.el7.x86_64 - kernel-3.10.0-327.36.1.el7.x86_64 - kubernetes-1.2.0-0.13.gitec7364b.el7.x86_64 - ostree-2016.7-2.atomic.el7.x86_64 docker-latest You can switch to the alternate docker version by running: # systemctl disable docker --now # systemctl enable docker-latest --now # sed -i '/DOCKERBINARY/s/^#//g' /etc/sysconfig/docker Because both docker services share the /run/docker directory, you cannot run both docker and docker-latest at the same time on the same system. 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 (546 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box (558 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 (776 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.2 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 ap-northeast-1 ami-494e9628 ap-northeast-2 ami-07bb6f69 ap-southeast-1 ami-60b51203 ap-southeast-2 ami-598cbf3a eu-central-1 ami-6350af0c eu-west-1 ami-8c2c6fff sa-east-1 ami-5a51c336 us-east-1 ami-cfeca0d8 us-west-1 ami-71bef711 us-west-2 ami-f020f890 SHA Sums 3af63166dd86c0b719efb57b5b4cc0997b959caa6680d3f86ff710bc382a2bd6 CentOS-Atomic-Host-7.1609-GenericCloud.qcow2 4ab6c62710cf81ae1e632c428a915648e3573adddab9f9c5d6fed517dcf27553 CentOS-Atomic-Host-7.1609-GenericCloud.qcow2.gz 06549195aa626b82f9b7473a366a7f1b32932dff60e8d53be924b3b0c2635e00 CentOS-Atomic-Host-7.1609-GenericCloud.qcow2.xz e26651dd1c3dde5b6dfee088876189fb29fb79f729e86fcd516fe87ccd992381 CentOS-Atomic-Host-7.1609-Installer.iso 037dad130293cf7476e9d711fec0d40d88f370f36dae66b80c8cce4ab5082fc2 CentOS-Atomic-Host-7.1609-Vagrant-Libvirt.box 1353920c87b0516c44072a184bbb8845c89ba1e538185a4dfc03076f65401dca CentOS-Atomic-Host-7.1609-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

oc login from 1.3.0 will ignore --insecure-skip-tls-verify=true
by Karanbir Singh 11 Oct '16

11 Oct '16

hi, oc client from 1.3 will no longer work with --insecure-skip-tls-verify=true : I've had to fall back to 1.2.1 in order to get past local test cluster issues. https://github.com/openshift/origin/pull/11145 looks to be the upstream issue, is there any chance we can get this backported into our builds Troy ? regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

[infra] : Hardware migration status (full/correct version)
by Fabian Arrotin 11 Oct '16

11 Oct '16

As announced some time ago ( https://lists.centos.org/pipermail/centos-announce/2016-September/022065.ht… ) , there was a big hardware migration/DC relocation happening yesterday that impacted several of our public services. Here is a small report of that migration, that finally took less time that previously announced. * 2016-10-10 - 1pm UTC : we started to preconfigure all changes, and powered down all the services in correct order * 2016-10-10 - 2pm => 6pm UTC : hardware was moved/migrated * 2016-10-10 - 6pm => 8pm UTC : hardware was (in serial order) plugged back in and ipmi/oob interfaces reconfigured, and network started to be validated * 2016-10-10 - 8:30pm UTC : https://accounts.centos.org was back online and operational * 2016-10-10 - 9pm UTC : https://cbs.centos.org was back online but builders were still disabled for validation * 2016-10-10 - 9:45pm UTC : https://cbs.centos.org : builders were enabled and working again * 2016-10-11 - 3:30am UTC : https://ci.centos.org now fully operational (after some network reconfiguration needed post-migration, and validations Thanks a lot to Brian Stinson (on-site) and DC people who helped for that migration (Matt, Jon, Nathan, Nina, Phil) Should you encounter an issue , feel free to discuss with us in #centos-devel on irc.freenode.net PS : sorry for the previous and incomplete mail : sent by accident before finished and probably due to lack of coffee and short night ... -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

3 2

[infra] : Hardware migration status
by Fabian Arrotin 11 Oct '16

11 Oct '16

1 0

password ssh-ing in Centos/7 Vagrant box
by Rafal Skolasinski 10 Oct '16

10 Oct '16

Hi, Vagrant Image version 1607.01 introduced a nice fix for a security issue with default password for a Vagrant user. I understand that this is important, however I wanted to ask if it is possible to switch it off? I couldn't figure out a way it was introduced. I was using first ansible login via password to configure my vms and then switching that option off by myself anyway. Cheers, Rafal

4 10

A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages
by Ponomarenko Andrey 08 Oct '16

08 Oct '16

Hello, I'd like to present a new free tool for maintainers of software libraries — Package ABI Diff Tool (pkg-abidiff). It's a tool for backward compatibility analysis of API/ABI interfaces in RPM packages. The tool is based on ABI Compliance Checker and ABI Dumper tools. The tool does the following: 1. Extracts input packages 2. Searches for *.debug, *.so and header files 3. Creates ABI dumps of all found shared objects 4. Filters out private part of the ABI using info from header files 5. Matches shared objects in old and new packages 6. Compares ABI dumps of corresponding objects 7. Creates backward binary compatibility (BC) report 8. Creates backward source compatibility (SC) report The tool is intended for Linux maintainers who are interested in ensuring backward compatibility, i.e. allow old applications to run (BC) or to be recompiled (SC) with newer versions of RPM packages. Home page: https://github.com/lvc/pkg-abidiff Usage: pkg-abidiff -old P1 P1-DEBUG P1-DEV -new P2 P2-DEBUG P2-DEV P1 — RPM package to analyze (with *.so object files) P1-DEBUG — corresponding debug-info package (*.debug files with DWARF info) P1-DEV — corresponding development package (with header files) Report example for libssh 0.6.4 vs 0.7.1: https://abi-laboratory.pro/examples/compat_report/x86_64/libssh/0.6.4-4.el7… Enjoy!

2 1

[Infra] - CentOS Bug tracker migration / maintenance window
by Fabian Arrotin 08 Oct '16

08 Oct '16

We have to upgrade our current MantisBT instance for the CentOS bug tracker service (aka https://bugs.centos.org) Migration is scheduled for """"Friday october 7th, 12:15 pm UTC time"""". You can convert to local time with $(date -d '2016-10-7 12:15 UTC'') The expected "downtime" is estimated to ~15 minutes , time needed to update MantisBT code, run the mysql schema update, and then put the node back in production mode. Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

Openshift Origin Containers for v1.2.1 and v1.3 on container pipeline.
by Mohammed Ahmed 07 Oct '16

07 Oct '16

Hi, We currently have openshift origin containers being delivered through the Container Pipeline. However, with the release of openshift origin 1.3, we have to consider how we are going to deliver containers for v1.2.1 and v1.3. Currently, the dockerfiles basically do a yum install origin[1] and other origin packages. This could possibly result in the latest origin rpms being used even in 1.2.1 containers. We need to consider how we are going to differentiate the versions. Even if there aren't any updates to 1.2 containers on toe repos, its still possible the containers might get rebuilt from other triggers, such as base image rebuilds and so on. KB, Troy Dawson, thoughts? Others are welcome to chime in as well. [1] https://github.com/openshift/origin/blob/release-1.2/images/origin/Dockerfi… -- *Mohammed Zeeshan Ahmed* Associate Software Engineer, Redhat Developers Team (Devtools) http://mohammedzee1000.wordpress.com 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>

4 6

Backporting Hyper-V support to Koji 1.10.1
by Laurentiu Pancescu 06 Oct '16

06 Oct '16

We already upgraded Image Factory some time ago, to be able to generate images for Hyper-V. Unfortunately, we were hold back by the lack of a newer stable release of Koji, which passes the right parameters to Image Factory. I tried to backport Ian's changes to Koji 1.10.1 (which I assume we're using). I had to manually fix a few merge conflicts - could someone take a look at the attached patches? I have no possibility of testing them here. Thanks, Laurențiu

1 0

Ideas for customizing the embedded Vagrantfile?
by Laurentiu Pancescu 06 Oct '16

06 Oct '16

Hello all, Vagrant boxes include a Vagrantfile, where we can preset some configuration values, as required by our images. Right now, the Vagrantfile for each provider is hard-coded inside the Image Factory code, but, during a conversation in #centos-devel, Ian was inclined to accept patches, and eventually discuss possible approaches with whoever is interested. Do you have any specific ideas or wishes for customizing the Vagrantfiles? At a minimum, the MAC address needs to be set in the embedded Vagrantfile. Perhaps each image builder could provide its own template as a parameter, just we like pass the kickstart files to Koji. I think it's already possible to interpret variables inside kickstart files (we used that for setting the root password in the past, before hardcoding it to 'vagrant'); if not, I think Zope includes a template system. We'll need to implement this both in Image Factory and Koji (for CBS). I would be especially interested in getting this done; with just one hardcoded Vagrantfile for everyone using Image Factory, there's always the danger that a change in Image Factory to accommodate one project might adversely impact other projects. [1] Best regards, Laurențiu [1] https://github.com/redhat-imaging/imagefactory/issues/366

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