devel

devel@lists.centos.org

2 participants
4651 discussions

Problem logging into cbs.centos.org
by Thomas F Herbert 24 May '17

24 May '17

All: I no longer can log in to https://cbs.centos.org/koji/login I get SSL_ERROR_HANDSHAKE_FAILURE_ALERT Did I forget a procedure along the way after generating new keys as instructed by email? accounts.centos.org works fine. --Tom -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat*

2 2

[storage] ceph-ansible tagged for -testing
by Giulio Fidente 23 May '17

23 May '17

Hi, we have tagged for testing ceph-ansible 2.2 in the jewel repo! Its dependencies, including ansible, are cross-tagged. These can be explored at http://cbs.centos.org/koji/builds?order=nvr&tagID=654 If you wanted to deploy Ceph using ceph-ansible, this is the right time to start testing it! :D -- Giulio Fidente GPG KEY: 08D733BA

1 1

CBS Outage : ppc64/ppc64le builders in offline mode
by Fabian Arrotin 23 May '17

23 May '17

Hi As discussed in CBS meeting today (https://www.centos.org/minutes/2017/may/centos-devel.2017-05-22-14.00.html) and also reflected on https://status.centos.org , we currently suffer from a hardware issue that impacts our connectivity to some nodes, including the ppc64/ppc64le builders. That means that SIG people willing to build against/for those arches will not be able to see their build jobs/tasks running as long as connectivity isn't restored (and no ETA yet) Worth noting that those builders are disabled at the koji level (https://cbs.centos.org/koji/hosts?state=all&order=name) We'll keep you informed when those nodes will be reachable again and so enabled for cbs builds Kind Regards, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 1

Bazel test cases timing out on CentOS 7.
by Atul Sowani 19 May '17

19 May '17

Hi, I have observed that certain Bazel test cases from the test suite are timing out on CentOS 7 (kernel version 3.10.0-123.el7.x86_64). For example, I tried bazel_coverage_test (using command bazel test //src/test/shell/bazel:bazel_coverage_test) and observed that it just hangs. I tried tracing it using strace (log attached). This seems to be CentOS specific behavior as I did not observe this on Ubuntu 16.04. Has anybody observed this? Is this a regression as far as CentOS is concerned? Thanks, Atul.

5 7

Azure Cloud Images
by Akshay Kumar 18 May '17

18 May '17

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 Thanks, A

2 2

CentOS 7 extras for alternative arches and Koji workflow.
by Thomas Oulevey 18 May '17

18 May '17

Dear All, I'd like to retake a pending issue with -extras on c7 and ask for feedback. I wear two hats : 1/ User, who would like to use altarch-extras packages soon after they are available in c7-extras. 2/ CBS maintainer, who would like to provide his users consistent buildroot across all architecture. Let's start with 1/. The important point here is to be able to rely on altarch-extras and expect it to be in sync with c7-extras in a reasonable time. (days not weeks) As it was always stated c7 (all repositories) cannot and should not be blocked by any alt-arch rebuild and should be independent. However we should at least try to provide these alt-arches packages in a timely manner. A lot of coordination (and motivated contributors) is needed if this effort is not centralized. For 2/ it is very important that we build package with similar buildroots on all arches. As c7-extras is now enabled for everybody, we should be able to have the altarch equivalent in a timely manner. Also all SIGs who are building for all alt-arches will be blocked in case an extras package is needed in the buildroot (we dealt with these issues during 7.2 -> 7.3 cycle and it will come back at next minor release. Additional challenge is the -cr repository which is enabled in CBS by default) However I understand, we need a way not to block official c7 arches for other arches that need fixes. After reviewing the possibilities with different people last year, one way to tackle this issue, would be to have 2 targets in Koji ; 1 including official arches and the other including official arches + alt-arches and allow SIG to bypass alt-arches by changing one target in their config. In this config we could move easily an altarch to an official one and vice versa. Finally, in my opinion, an easy way to have consistent altarch-extras would be to monitor official repository on the mirror.c.o (or buildlogs.c.o) and rebuild automatically extras packages in Koji, which would be picked by a script and so all altarch-extras would be generated directly by Koji itself and the process pretty much automated. The signing process will still be the key to control what is pushed to buildlogs/mirrors. (and close to what we already do) I don't see many disadvantages for this solution but I would like to know if it is possible to move forward and what the community and core contributors think about it. Is altarch-extras important to you ? thank you for your feedback, -- Thomas Oulevey

7 11

Anyone using the serial console from our Vagrant boxes?
by Laurentiu Pancescu 18 May '17

18 May '17

Hi, The default boot parameters of our Vagrant images activate a serial console. The problem is that VirtualBox doesn't enable a serial port by default, and our boxes hang if they really need to use the console, e.g. during relabeling[1] or during the initial configuration required for sealed VM templates (what I'm currently trying for Hyper-V support). Is anyone using the serial console we provide? If not, I can just remove the console=ttyS0 parameter from the kernel command line. Otherwise, a patch for Image Factory is trivial - I can just the set the port to enabled in the XML file, without the cable connected, and probably move console=tty0 on the last position, so it becomes the active console. Libvirt and VMware don't cause this problem, because they either have a serial port by default, or pretend it's there if the guest tries to use it. No idea if Hyper-V or Xen default to having a serial port. I would like to fix this for version 1704, which should be released in the following days. Regards, Laurențiu [1] https://bugs.centos.org/view.php?id=13213

4 6

office hours May 18th
by Karanbir Singh 18 May '17

18 May '17

hi apologies for the short notice, but I am unable to make the office hrs tomorrow. However, if anyone has pending points for the session - please email me and I will aim to reply within a few hrs. regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

[question] audio and realtime SIG
by Markus Seeber 17 May '17

17 May '17

Hello, I remember there has been some interest in creating an audio related SIG a few years ago and I'd like to know if anything has come out of that. Related to that, I wonder if there is a realtime related SIG. From a first quick search over the wiki pages there does not seem to be such a thing. On the other hand I know that CERN has put some effort in maintaining rt-kernels for their rt messaging grid. Is there anything going on the CentOS side in regard to these use cases? best regards Markus

1 0

New CentOS Atomic Host with Optional Docker 1.13
by Jason Brooks 16 May '17

16 May '17

An updated version of CentOS Atomic Host (tree version 7.20170428), is now available, featuring the option of substituting the host’s default docker 1.12 container engine with a more recent, docker 1.13-based version, provided via the docker-latest package. https://wiki.centos.org/SpecialInterestGroup/Atomic/Download 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. CentOS Atomic Host includes these core component versions: - atomic-1.15.4-2.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - docker-1.12.6-16.el7.centos.x86_64 - etcd-3.1.3-1.el7.x86_64 - flannel-0.7.0-1.el7.x86_64 - kernel-3.10.0-514.16.1.el7.x86_64 - kubernetes-node-1.5.2-0.5.gita552679.el7.x86_64 - ostree-2017.3-2.el7.x86_64 - rpm-ostree-client-2017.3-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. https://wiki.centos.org/SpecialInterestGroup/Atomic/ContainerizedMaster 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. 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 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 ---------------- -------------- ap-south-1 ami-9c7b06f3 eu-west-2 ami-14425570 eu-west-1 ami-a1b9b7c7 ap-northeast-2 ami-e01cc18e ap-northeast-1 ami-2a0d304d sa-east-1 ami-ce7619a2 ca-central-1 ami-8b813def ap-southeast-1 ami-61e36702 ap-southeast-2 ami-84c7cde7 eu-central-1 ami-f970ae96 us-east-1 ami-4a70015c us-east-2 ami-d2cfe8b7 us-west-1 ami-57ba9c37 us-west-2 ami-fbd8bd9b SHA Sums 977c9b6e70dd0170fc092520f01be26c4d256ffe5340928d79c762850e5cedd9 CentOS-Atomic-Host-7.1704-GenericCloud.qcow2 781074c43aa6a6f3cad61a77108541976776eb3cb6fe30f54ca746a8314b5f87 CentOS-Atomic-Host-7.1704-GenericCloud.qcow2.gz aef7fedf01b920ee75449467eb93724405cb22d861311fbc42406a7bd4dbfee2 CentOS-Atomic-Host-7.1704-GenericCloud.qcow2.xz 669c5fd1b97bc2849a7e3dbec325207d98e834ce71e17e0921b583820d91f4f5 CentOS-Atomic-Host-7.1704-Installer.iso b5ef69bff65ab595992649f62c8fc67c61faa59ba7f4ff0cb455a9196e450ae2 CentOS-Atomic-Host-7.1704-Vagrant-Libvirt.box 73757f50ef9cdac2e3ba6d88a216cca23000a32fa96891902feaa86d49147e3f CentOS-Atomic-Host-7.1704-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

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