devel

devel@lists.centos.org

10 participants
4617 discussions

[rescheduled] cbs.centos.org upgrade on 2016-08-24
by Thomas Oulevey 24 Aug '16

24 Aug '16

Hello Folks, Please note that intervention scheduled on Monday August the 22nd has been postponed to Wednesday August 24th. cbs.centos.org will be upgraded to support newer features. What does that mean for you ? We will upgrade Imagefactory to latest version. The change is scheduled to be implemented on Wednesday August 24th 7:00 am UTC time You can convert to local time with $(date -d '2016-08-24 7:00 UTC') What will be the impact ? During the update it will not be possible to build packages or images. Please note that temporary repositories served on cbs.centos.org will be available (Mostly used for CI). Please let us know before Tuesday August 23rd if it could impact dramatically your work/releases schedule. -- Thomas Oulevey on behalf of the infrastructure team

1 1

New CentOS Atomic Host release available for download
by Jason Brooks 23 Aug '16

23 Aug '16

An updated version of CentOS Atomic Host (tree version 7.20160818), featuring support for rpm-ostree package layering. Using the command rpm-ostree pkg-add, it's now possible to layer new packages into an installed image that persist across reboots and upgrades. 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: - docker-1.10.3-46.el7.centos.10.x86_64 - kubernetes-1.2.0-0.13.gitec7364b.el7.x86_64 - kernel-3.10.0-327.28.2.el7.x86_64 - atomic-1.10.5-7.el7.x86_64 - flannel-0.5.3-9.el7.x86_64 - ostree-2016.7-2.atomic.el7.x86_64 - etcd-2.3.7-2.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 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 (530 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box (541 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 (757 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.1 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 us-east-1 ami-d43d5dc3 us-west-2 ami-0227f362 us-west-1 ami-52df9d32 eu-west-1 ami-ed4b3d9e eu-central-1 ami-014abb6e ap-southeast-1 ami-27a27a44 ap-northeast-1 ami-4d35fa2c ap-southeast-2 ami-65b18606 ap-northeast-2 ami-12ae7b7c sa-east-1 ami-6ed34202 SHA Sums 5e2d2bc26d4017f556d3f1e65b6cf1a8ca111534515bbb7a6fea3d446af1b674 CentOS-Atomic-Host-7.1607-GenericCloud.qcow2 c8e908072b63581a7c8a3ffc2658eaf64cb30e1f85db7ed97d1e7fa3605dc26f CentOS-Atomic-Host-7.1607-GenericCloud.qcow2.gz 99776addb6ab2ff25d64831a21eb0c7bfe337be68d402095fd740c05f5d40a3e CentOS-Atomic-Host-7.1607-GenericCloud.qcow2.xz 05ccc8c1db8047028fabb92c89c3fda9f07286f5e7f2832c9ee92a05bf1bc8dc CentOS-Atomic-Host-7.1607-Installer.iso 443af2e145370dee939eaab38df9a61a15a0aa1636e477acb7864a175f78b584 CentOS-Atomic-Host-7.1607-Vagrant-Libvirt.box 7fef5a9c02c4c351f051f73e00f24d3a7ce8c0a081ae0f0956eb820b1211dd06 CentOS-Atomic-Host-7.1607-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 1

pcs-0.9.143-15 is not rebranded
by aleksander.baranowski 22 Aug '16

22 Aug '16

Hello, Sorry for bothering you, I just joined your list. But when I was using different RHEL clone (SL), I found out that package pcs is not rebranded. So whey you log into High Availability console (one operating on 2224 and https) you have Red Hat logo. Source1: HAM-logo.png in rpm is responsible for that. There is also favicon in source pcs-0.9.143/pcsd/public/favicon.ico which is Red Hat :). Moreover there is pcs-0.9.143/pcsd/public/css/overpass_bold-web.svg which is font owned (???) by Red Hat :(. I don't know if it's important. The source of every generated page has also commented Red Hat footer. It's probably also not a big deal. Bests, Alex Baranowski

2 1

Re: [CentOS-devel] [rdo-list] [centos-ci] Artifacts server does not support ranges / resume of downloads?
by Haïkel 18 Aug '16

18 Aug '16

2016-06-28 4:25 GMT+02:00 Gerard Braad <me(a)gbraad.nl>: > Hi all, > > > Usually I download the undercloud images using: > > https://gist.github.com/gbraad/45cbe30415b0dc631f5e8d20beaffebf > > which targets: 'artifacts.ci.centos.org' but now get > > "HTTP server doesn't seem to support byte ranges. Cannot resume." > > I need to resume a download about 10 times on the office connection > (China), so what happened? I have a workaround by storing the files at > another server first in Japan or the west-coast which supports > resuming. > > Although, being able to resume the download of these files is preferable. > > regards, > > > Gerard > Since this part of infrastructure is managed by CentOS Core Team, CC'ing centos-devel list. > > -- > > Gerard Braad | http://gbraad.nl > [ Doing Open Source Matters ] > > _______________________________________________ > rdo-list mailing list > rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com

6 9

git.centos.org downtime
by Karanbir Singh 18 Aug '16

18 Aug '16

hi, Just a heads up that there is going to be a potential git.centos.org downtime for 4 hrs starting at 10:00 AM UTC Monday 22nd Aug 2016; I am hoping to get some maint work done that should not impact services, but it might degrade things for a few hours. During this time, you can find us in #centos-devel on irc.freenode.net if there are any issues. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

[Virt] Backport of a qemu fix for /dev/kvm permissions ?
by David Moreau Simard 18 Aug '16

18 Aug '16

Hi, To make a long story short, in certain circumstances, the /dev/kvm file can sometimes have permissions that do not allow it to be used properly [1]. This claims to have been fixed in qemu-2.3.0-1.fc22. I was wondering if we should expect that fix to land in the qemu-kvm-ev-2.3.0* packages provided by the virt SIG repo ? I know for a fact the patch is not there (yet) right now: (on Fedora): $ rpm -q --scripts qemu-system-x86 postinstall scriptlet (using /bin/sh): # Default /dev/kvm permissions are 660, we install a udev rule changing that # to 666. However trying to trigger the re-permissioning via udev has been # a neverending source of trouble, so we just force it with chmod. For # more info see: https://bugzilla.redhat.com/show_bug.cgi?id=950436 chmod --quiet 666 /dev/kvm || : (with latest qemu-kvm-ev from CentOS SIG repo): $ rpm -qp --scripts qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm postinstall scriptlet (using /bin/sh): # load kvm modules now, so we can make sure no reboot is needed. # If there's already a kvm module installed, we don't mess with it sh /etc/sysconfig/modules/kvm.modules &> /dev/null || : udevadm trigger --subsystem-match=misc --sysname-match=kvm --action=add || : ... Thanks, [1]: https://bugzilla.redhat.com/show_bug.cgi?id=950436 David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter]

2 1

[opstools] weekly meeting
by Matthias Runge 18 Aug '16

18 Aug '16

Hello, I would like to invite you all to the weekly opstools meeting on Wednesdays at 18:00 UTC (that's directly after the PaaS meeting) It happens on freenode, #centos-devel The first meeting will be on Aug 17th. Agenda for Aug 17th - introductions (persons, expectations) - rpm/git repositories - ci - ... See you all there, Matthias

1 2

CentOS PaaS SIG meeting (2016-08-17)
by Troy Dawson 17 Aug '16

17 Aug '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 17 August 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - origin update policy -- What should happen when a new openshift origin comes out. -- https://github.com/openshift/openshift-ansible/issues/2293 - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2016/august/centos-devel.2016-08-10-17.00.lo…

1 0

[OpsTools] oVirt Metrics Store
by Yedidyah Bar David 17 Aug '16

17 Aug '16

Hi all, The oVirt project is looking at using some of the tools worked on by the OpsTools SIG. More details can be found at [1]. We are currently looking at ElasticSearch and Logstash, and at Kibana and Grafana. This effort is lead by Shirly Radco, our BI engineer. I am a member of the integration-development team, and can try helping with packaging etc. I'll have a look at the current status of packaging of these tools and might send more emails with specific questions/issues as needed. [1] http://www.ovirt.org/develop/release-management/features/engine/metrics-sto… Best regards, -- Didi

1 0

[opstools] fluentd packaging
by Lars Kellogg-Stedman 17 Aug '16

17 Aug '16

In working with the fluentd packaging from the opstools sig, I think we need to make at least two changes: - For type=tail sources, fluentd really wants a pos_file parameter to track the file position. It would be helpful if we created /run/fluentd via /etc/tmpfiles.d as a common location for storing these files. - I think that the *_secure_forward plugins (which permit using ssl for communication between a fluentd client and a collector) are going to be a necessity for just about everybody, so these should probably be packaged in manner similar to the elasticsearch plugin. -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/

4 6

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