devel January 2017

devel@lists.centos.org

38 participants
44 discussions

[Cloud SIG][RDO] RDO meeting minutes - 2017-01-25
by Chandan kumar 25 Jan '17

25 Jan '17

============================ #rdo: RDO meeting-2017-01-25 ============================ Meeting started by chandankumar at 15:01:18 UTC. The full logs are available at https://meetbot.fedoraproject.org/rdo/2017-01-25/rdo_meeting-2017-01-25.201… . Meeting summary --------------- * rollcall (chandankumar, 15:01:54) * Vote on move from fast-forwards only on review.rdoproject.org (chandankumar, 15:04:33) * LINK: https://gerrit-review.googlesource.com/Documentation/project-configuration.… (jruzicka, 15:08:38) * ACTION: jpena to script change existing distgit projects to "rebase if necessary" (jpena, 15:19:31) * Announcements & calls for participation (chandankumar, 15:20:12) * centos-ocata worker is alive and working (chandankumar, 15:27:32) * LINK: https://trunk.rdoproject.org/centos7 will start to diverge as soon as projects shift their focus to pike (jpena, 15:29:18) * ACTION: jpena to add a centos7-pike symlink pointing to centos7-master (jpena, 15:39:26) * Updates on Tempest Packaging (chandankumar, 15:41:03) * LINK: https://review.rdoproject.org/r/#/q/topic:switch-upstream-tempest (chandankumar, 15:41:52) * LINK: https://review.rdoproject.org/r/#/q/topic:add-tempestconf (chandankumar, 15:44:03) * chair for next meeting (chandankumar, 15:46:09) * ACTION: jruzicka to chair for next meeting (chandankumar, 15:48:02) * open floor (chandankumar, 15:48:17) Meeting ended at 15:59:09 UTC. Action Items ------------ * jpena to script change existing distgit projects to "rebase if necessary" * jpena to add a centos7-pike symlink pointing to centos7-master * jruzicka to chair for next meeting Action Items, by person ----------------------- * jpena * jpena to script change existing distgit projects to "rebase if necessary" * jpena to add a centos7-pike symlink pointing to centos7-master * jruzicka * jruzicka to chair for next meeting * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * chandankumar (62) * rbowen (28) * jruzicka (28) * apevec (17) * jpena (16) * dmsimard (12) * jschlueter (11) * EmilienM (10) * zodbot (8) * scsnow (5) * rdogerrit (4) * openstack (4) * matbu (3) * number80 (3) * trown (2) * radez (1) * dougbtv__ (1) * leifmadsen (1) * dougbtv (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[opstool] please add ppc64le arch
by Sandro Bonazzola 25 Jan '17

25 Jan '17

Hi, looks like opstool target is building aarch64 and x86_64 but not ppc64le. Can you please add ppc64le as well? It has been proven building so on CBS side there shouldn't be build issues. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[opstools] Getting opstools content to mirror.c.o
by Matthias Runge 25 Jan '17

25 Jan '17

Hello, what's the process to get the opstools content released for testing purpose on buildlogs.c.o over to a more "official" location on the mirrors? What do we need to do to get rpms signed there? Best, Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

3 3

2017-01-31 cbs.centos.org infrastructure upgrade.
by Thomas Oulevey 24 Jan '17

24 Jan '17

Dear All, Please note that next week on Tuesday cbs.centos.org will be upgraded to support newer features and allow us to improve our vagrant images type coverage. What does that mean for you ? Next Tuesday, we'll upgrade koji and imagefactory to latest version. The change is scheduled to be implemented on Tuesday January 31st, 8:00 am UTC time You can convert to local time with $(date -d '2017-01-31 8:00 UTC') What will be the impact ? Koji build service will be down for an hour. It will not be possible to build new packages or images. Please note that temporary repositories served on cbs.centos.org will be also affected as nodes will be rebooted to run latest kernel (Mostly used for CI). Please let us know before Friday January 27th if it could impact dramatically your work/releases schedule. -- Thomas on behalf of the infrastructure team.

1 0

Enable ppc64le architecture in ci.centos.org
by Murilo Opsfelder Araújo 24 Jan '17

24 Jan '17

Hi, Karanbir and CentOS community. I am starting this thread to understand what is needed to enable ppc64le architecture in ci.centos.org, be it hardware, software, or any roadblock. As soon as we understand all the requirements, I will be pleased to work with you to sort them out. Ideally speaking, we would like to have all relevant checks and validations performed against amd64 to be executed on ppc64le as well, for all the relevant SIGs. We also would like to see docker and cloud images, in general, being created and validated for ppc64le as part of CentOS pipelines. As of 7.3, CentOS on ppc64le became a lot easier, meaning, for example, that nested qemu/KVM virtualization works out of the box; and creating and running docker images in CentOS guest works just fine. To get the ball rolling, below is a short list of needed changes to create, run, and test docker images on CentOS 7.3: - https://github.com/rhinstaller/lorax/pull/149 - https://github.com/virt-manager/virt-manager/commit/cd35470e3c55aa64976cd0a… - https://github.com/CentOS/sig-cloud-instance-build/pull/65 - https://github.com/CentOS/sig-core-t_docker/pull/2 I am looking forward to work with you and define our next steps together. Thank you! -- Murilo

2 2

TLS/https for {buildlogs,cloud}.centos.org
by Fabian Arrotin 23 Jan '17

23 Jan '17

Hi, Last week we enabled https for buildlogs.centos.org and cloud.centos.org, but we haven't (yet) enforced the redirection. So both are available over http:// and https:// For buildlogs, as we already have redirection in place (RewriteRules) for content to the backend (see https://lists.centos.org/pipermail/centos-devel/2016-March/014552.html) , we can enforce the redirection without any issue (and good news is that the CDN backend also support https so it will be https end-to-end), so I'll implement the additional http=>https redirect soon My only concern is about doing the same for cloud.centos.org as we have no ideas about how people are "consuming" those images (and the wrapper script they use around it). As mentioned in the previous mail wrt buildlogs, people using wget will not suffer from the redirection, but people using curl can be impacted (if used without --location) Searching so for comments/opinions and if no real impact, we can start the automatic redirection in the next two weeks. (after having sent a mail to the -announce first) -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

GlusterFS 3.9
by Zdenek Sedlak 23 Jan '17

23 Jan '17

Hello everyone, I work a lot with GlusterFS and like the new features in the version 3.9. I saw the latest available version in CentOS is 3.8, but the buildlogs server already contains the version 3.9 built in back November last year. Could you tell me what is the plan to publish the 3.9 officially? Thanks //Zdenek

2 4

Any plans to update sclo-vagrant1?
by Laurentiu Pancescu 20 Jan '17

20 Jan '17

Hello, Oracle actively supports two VirtualBox release lines: 5.0 and 5.1. In my experience, 5.1.x releases are a little faster in some operations, but have some annoying bugs that 5.0.x don't. Oracle prominently features 5.1 as the default download, and it is also the version in the repos of most Linux distros (Debian Jessie backports[1], Testing and Unstable, Arch, OpenSUSE, OpenMandriva, Ubuntu 16.10 - only Ubuntu 16.04 LTS has 5.0). The CI test for our Vagrant images already tested with libvirt-kvm and VirtualBox 5.0; I extended it for testing with VirtualBox 5.1 as well, in a branch, but the test fails because sclo-vagrant1, based on upstream Vagrant 1.8.1, only supports VirtualBox up to version 5.0 (support for 5.1 first came in Vagrant 1.8.5). Are there any plans to upgrade sclo-vagrant1 to a more recent upstream version, or perhaps backport the support for 5.1 to the current sclo-vagrant1? [2] If you'd rather update to a newer version, Vagrant 1.9.1 broke at least private networking (eth0 is preconfigured by our image, but the additional network interfaces that Vagrant 1.9.1 configures don't get an IP address - I assume public networking is broken as well, but I only tried private networking). I also saw some entries concerning NFS in the upstream issue tracker, not sure if it's caused by the same bug. Versions 1.9.0 and 1.8.6 work for me. Best regards, Laurențiu [1] https://www.debian.org/security/2016/dsa-3699 [2] https://github.com/mitchellh/vagrant/commit/b57b0e0d48fe8b4196ca6b7e01bb6c1…

3 4

CentOS Atomic Updates
by Jason Brooks 19 Jan '17

19 Jan '17

A new CentOS Atomic Host release (7.20170117), based on CentOS 7.1611, is now available. Beyond the rebase to the new CentOS version, the biggest change in this release is the removal of the kubernetes-master package from the image, a change that we’ve inherited from RHEL Atomic. 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. [1] The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline [2], based on Dockerfiles from the CentOS-Dockerfiles repository. [3] [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/ContainerizedMaster [2] https://wiki.centos.org/ContainerPipeline [3] https://github.com/CentOS/CentOS-Dockerfiles/tree/master/kubernetes I’ve tested these containers with the kubernetes ansible scripts provided in the upstream contrib repository [4], and they work as expected, provided you first copy the service files onto your master. I’ve also tested the containers with a cluster already running kubernetes as configured by the ansible scripts, and that case works as well. [4] https://github.com/kubernetes/contrib/tree/master/ansible There is, however, an SELinux issue [5], the workaround for which is running your kubernetes nodes in permissive mode. The fix for this issue requires updating to the docker 1.12 version released this week as part of this week’s RHEL AH 7.3.2. As soon as docker and the rest of the “atomic” packages are built for CentOS, we’ll test and release an updated CentOS Atomic Host, along with refreshed media. [5] https://bugzilla.redhat.com/show_bug.cgi?id=1412803 For now, if you wish to upgrade to 7.20170117, do so by running: # atomic host upgrade If you aren't already running CentOS Atomic, you can download an image from our download page on the CentOS wiki and upgrade that to the latest tree. [6] [6] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download ### CentOS Atomic Host 7.20170117 includes these core component versions: * atomic-1.13.8-1.el7.x86_64 * cloud-init-0.7.5-10.el7.centos.1.x86_64 * docker-1.10.3-59.el7.centos.x86_64 * etcd-2.3.7-4.el7.x86_64 * flannel-0.5.5-1.el7.x86_64 * kernel-3.10.0-514.2.2.el7.x86_64 * kubernetes-node-1.3.0-0.3.git86dc49a.el7.x86_64 * ostree-2016.11-2.atomic.el7.x86_64

1 0

[opstools] weekly meeting
by Matthias Runge 18 Jan '17

18 Jan '17

Hello, we're having a weekly meeting on Wednesdays at 18:00 UTC. Currently, there is not that much going on in opstools. Thus I'd propose to skip weekly meetings until there is something which needs to be discussed in a chat meeting. Thoughts, objections? Best, Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2017