devel

devel@lists.centos.org

4 participants
4640 discussions

[RFC] Bootstrapping a new arch
by Haïkel 21 Oct '16

21 Oct '16

Hi, There was various discussions about enabling aarch64 architecture for Cloud SIG OpenStack repositories. And likely others are coming, so I'd like to confirm with a wider audience about the proper course of action. So we can document it and share that experience with other SIGs. Arrfab suggested the following: * scratch builds with archoverride of existing arch-dependent builds * ask CBS admin to merge the task with existing builds using mergeScratch. I find this process simple and efficient, but I'm worried about how it scales. In my case, I have about 250 binary packages (including the Erlang stack etc.) with many interdependencies, so it can rapidly get bothersome for CBS admins. If we can find a way to automate the mergeScratch operations or temporarily grant that permission to SIGs during bootstrapping phase, I have pretty much no objections for that course. --- As for daily operations, if you can't block on alternate arch build failures, I was recommended to just use %excludearch and move forward. Which gives us the flexibility to move forward and give more time to fix things at our pace. So what do you think? Any other suggestions? Regards, H.

6 5

Introducing Linch-Pin, Hybrid cloud provisioning using ansible
by Clint Savage 19 Oct '16

19 Oct '16

Hi all, Recently, as part of the CentOS PaaS SIG, I've been working on some basic tooling for CI. One of the tools that came out of this work, is Linch-Pin. It's a fairly simple tool for multi-cloud provisioning that's starting to get some traction. Currently, it's being used to provision Duffy instances inside for one Jenkins job in CentOS CI[1], but can do so much more. If you're interested in learning more about it, or trying it out, I'd love to hear your take. It's all open source and ready for you to try it out. I've written a blog post about Linch-Pin, and plan to do a series over the coming months. Check out the first installment in the series. http://sexysexypenguins.com/posts/introducing-linch-pin/ A link to the project is in the blog post, but also included below[2]. Additionally, there is some documentation[3], which is in the process of being improved. I'd love feedback on the blog post. And we're obviously interested in feedback on the project as well. Cheers, herlo 1- https://ci.centos.org/job/origin-from-source-0-test-matrix/ 2- https://github.com/CentOS-PaaS-SIG/linch-pin 3- http://linch-pin.readthedocs.io

1 0

CentOS PaaS SIG meeting (2016-10-19)
by Troy Dawson 19 Oct '16

19 Oct '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 19 October 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms --- new origin rpms --- new openshift-ansible rpms --- new openshift-excludes rpms -- Documentation -- Automated testing -- images / image building - Open Floor

2 1

[Cloud SIG] Virtualization & IaaS DevRoom at FOSDEM
by Rich Bowen 19 Oct '16

19 Oct '16

A Virtualization & IaaS DevRoom is planned for FOSDEM, and the CFP is available at http://www.ovirt.org/blog/2016/10/call-for-proposal-fosdem-2017/ I hope to see many of you there again this time. -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

1 0

[opstools] Will miss this weeks meeting (+next one)
by Matthias Runge 19 Oct '16

19 Oct '16

Hello, sorry for the short notice: due to a conflict I'll probably miss today's meeting. Next week I'll be in Barcelona for the OpenStack Summit and won't make it to the meeting as well. See you either in Barcelona or in 3 weeks on #centos-devel. Best, Matthias

1 0

CentOS PaaS SIG meeting (2016-10-12)
by Troy Dawson 12 Oct '16

12 Oct '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 12 October 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - Open Floor

1 0

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

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