devel

devel@lists.centos.org

10 participants
4617 discussions

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

CentOS PaaS SIG meeting (2017-01-18)
by Troy Dawson 18 Jan '17

18 Jan '17

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

1 0

Update on status of CentOS Community Container Pipeline
by Bamacharan Kundu 18 Jan '17

18 Jan '17

Hi All, Here is update for the work done recently in CentOS Community Container Pipeline. * Get all the logs fetched from scanner and linter to NFS. * Configuring nginx to view the public logs for given url hash * Get jenkins containers onto container Pipeline * Rebuilt all the images due to base image centos:latest update * rpm verify scanner is updated to filter expected logs * Provisioning now takes care of the date-utils package required for atomic scan * Mattermost images are now pushed to registry.c.o under mattermost namespace. Our current focus is on: * Sharing the logs for all the stages in single mail with link to the storage * Cleanup the pods data once the build is complete * Update of required images before running linter/scanner process * Get openshift ready keycloak images upstreamed * Auto generating the the pipeline wiki for the validated images in registry.c.o. Regards Bamacharan Kundu

1 0

Building Debian packages on ci.centos.org?
by Ken Dreyer 17 Jan '17

17 Jan '17

Hi folks, I'm thinking about how we can migrate some of the jobs on jenkins.ceph.com to ci.centos.org. One of the barriers to entry for Ceph is that our jenkins.ceph.com jobs output both RPMs and DEBs for every branch, and keeping parity between the two formats is important. If we "brought our own" Jenkins slaves for building .deb packages, could we use the ci.centos.org infrastructure? - Ken

2 2

"7" still points to 7.2.1511 on vault.centos.org
by Laurentiu Pancescu 17 Jan '17

17 Jan '17

Hi, I received an email about the inability to download the current kernel sources from our Vagrant images: % yumdownloader --source kernel ... No source RPM found for kernel-3.10.0-514.2.2.el7.x86_64 No source RPM found for kernel-3.10.0-514.el7.x86_64 I think this is caused by vault.centos.org, not by our Vagrant images: I can see centos-release-7-2.1511.el7.centos.2.10.x86_64.rpm under http://vault.centos.org/centos/7/os/x86_64/Packages/ - perhaps the "7" symlink hasn't been switched to 7.3.1611 yet? "6" points to 6.8 packages, the current release in the 6.x series. Regards, Laurențiu

2 2

ceph-jewel: Can we get a release ?
by David Moreau Simard 17 Jan '17

17 Jan '17

Hi, http://buildlogs.centos.org/centos/7/storage/x86_64/ceph-jewel/ has Ceph 10.2.3 since *at least* 2016-09-28 but it's still not hit public mirrors, can we get a release ? ipv6 support is broken in 10.2.2, we need 10.2.3 to land in public mirrors. Thanks, David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter]

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