devel May 2017

devel@lists.centos.org

29 participants
28 discussions

Request for feedback: CentOS-Atomic container
by Karanbir Singh 25 Sep '17

25 Sep '17

hi Alpha2: registry.centos.org/kbsingh/centos-atomic:7-alpha2 The CentOS Atomic Container is a minimal ( 30MB on disk ) image that can be used to host static content, and small footprint content that does not need the entire CentOS Linux Base image. This is also not meant to replace CentOS Linux Base image as the default, we want to make it available as an additional container base for apps that find it useful. The main highlight is that it does not contain yum, but has microdnf. I am looking for feedback, and some wider testing as well as recommendations on howto further reduce size, before we move to release. You can consume this as : docker run -t -i \ registry.centos.org/kbsingh/centos-atomic:7-alpha2 \ /bin/bash regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 4

Re: [CentOS-devel] Azure Cloud Images
by Patrick Laimbock 14 Jun '17

14 Jun '17

On 18-05-17 20:02, lkd-centos(a)sky-haven.net wrote: > On 2017-05-18 12:58, Patrick Laimbock wrote: >> On 17-05-17 13:38, Akshay Kumar wrote: >>> 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 >> >> Can you please do the conversion with qemu-img-ev from the Virt SIG >> and try again? The qemu-img-ev repo rpm can be found here: >> >> https://cbs.centos.org/koji/packageinfo?packageID=1950 > > Hi, > > There's nothing wrong with the image proper; the VM actually starts and > one can log in (if the starting image is unwrapped and deliberately > bugged with a hardcoded username/password first), it responds to SSH, etc. > > What doesn't happen is: waagent doesn't start because it hasn't been > `systemctl enable`'ed. Thanks for clarifying that the image boots properly. A new image with a fix will be generated. When it's ready (I don't know when as I'm not involved in that process) it should show up at: http://cloud.centos.org/centos/7/images/ HTH, Patrick

3 3

[opstools] regular meeting June-14 2017
by Matthias Runge 01 Jun '17

01 Jun '17

Hello, we'll have the next opstools SIG meeting on Wed, June 14 2017, 18:00 UTC. The meeting will be held in #centos-devel on freenode. If you're interested in tools for operators, have questions, suggestions,... you're kindly invited to participate. See you then, Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

2 1

CentOS PaaS SIG meeting (2017-05-31)
by Troy Dawson 31 May '17

31 May '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 31 May 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- separate repo work -- minishift - Find new chairperson for Paas SIG - Open Floor

1 0

CentOS SIG NFV Membership Request
by Billy McFall 31 May '17

31 May '17

I would like to join the CentOS SIG-NFV. I am copying Thomas Herbert, acting chair of the CentOS SIG-NFV, who is wiling to sponsor me. SIG NFV Request bug: https://bugs.centos.org/view.php?id=13338 Thank you, Billy McFall -- *Billy McFall* SDN Group Office of Technology *Red Hat*

2 1

NFV SIG - update
by Dave Neary 30 May '17

30 May '17

Hi, There has been a recent resurgence of interest in the NFV SIG, and in the interest of keeping the momentum going, I would like to step aside as SIG char, and recommend that Tom Herbert take over. Tom has taken on the packaging and building of VPP and DPDK-accelerated OVS for OPNFV, and has been active in the SIG in recent weeks, and I think he will help add the structure that has been sorely lacking from me in recent months. I'm not sure what the process is for replacing a SIG chair - can someone let us know, please? Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338

4 4

Configuration Management SIG status and new pkg proposal : ARA (Ansible Run Analysis)
by Fabian Arrotin 29 May '17

29 May '17

Hi, While technically speaking a ConfigManagement SIG was approved a long time ago (https://wiki.centos.org/SpecialInterestGroup/ConfigManagementSIG) it seems that nothing was built at all, and that initial people probably lost interest in that idea (?) The interesting part is that other SIGs that were relying on such config management tools (like puppet or ansible) built it themselves in their own tags : - puppet : https://cbs.centos.org/koji/packageinfo?packageID=390 - ansible : https://cbs.centos.org/koji/packageinfo?packageID=1947 I was myself just the "sponsor" for other community people to join and take care of the pkgs they were interested into, but suddenly I was myself busy rebuilding such tools, and I'd even have a new one as a proposal : ARA ARA (Ansible Run Analysis) is a tool written under the openstack umbrella, and written/maintained by dmsimard (Cloud SIG member) For people not aware of it, it's a callback plugin for ansible that let you store (and so browse) your ansible logs through webui (and it stores those reports into a DB) I initially thought about building that in the infrastructure7-el7 target, but maybe some other people would be interested into using those as pkgs directly in a repo on mirror.centos.org Initially the author wanted to have it in Epel7, but due to two pkgs version that are in [base] (and so that will not be overwritten by Epel), that doesn't seem possible. So my proposal would be to rebuild what's needed through configmgmt SIG , including the two packages (pytest and python-jinja2) For people interested in the ARA in Epel7 story, here is the pkg review : https://bugzilla.redhat.com/show_bug.cgi?id=1426193 Ideas, opinions ? -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

Re: [CentOS-devel] [OpsTools] fluentd packages tagging
by Sandro Bonazzola 29 May '17

29 May '17

On Mon, May 29, 2017 at 12:20 PM, Matthias Runge <mrunge(a)redhat.com> wrote: > On Mon, May 29, 2017 at 10:52:01AM +0200, Sandro Bonazzola wrote: > > On Mon, May 29, 2017 at 10:15 AM, Matthias Runge <mrunge(a)redhat.com> > wrote: > > > > > On Fri, May 26, 2017 at 07:55:32AM -0600, Rich Megginson wrote: > > > > On 05/26/2017 02:59 AM, Sandro Bonazzola wrote: > > > > > Hi, > > > > > I just discovered we have an issue with the package tagging about > > > fluentd. > > > > > fluentd-0.12.26-2.el7 > > > > > > > > $ cbs list-tags |grep opstool|grep release > > > > > opstools7-common-release > > > > > opstools7-elastic-2-release > > > > > opstools7-elastic-common-release > > > > > > > > We should get rid of these elastic tags, or at least ignore them, > and if > > > > there are any packages that we need in those tags, we should add > them to > > > > fluentd-012. > > > > > > > > > opstools7-fluentd-012-release > > > > > opstools7-perfmon-common-release > > > > > opstools7-sensu-023-release > > > > > opstools7-sensu-027-release > > > > > opstools7-sensu-common-release > > > > > > > > > > can we review the mappings in order to get fluentd packages > correctly > > > > > published? > > > > > Personally I would be happy if fluentd and collectd can be in > their own > > > > > repo so they won't require openstack as dependency repo. > > > > > > Packages tagged and not landing somewhere is unfortunate and should be > > > sorted out. > > > Unfortunately, that is nothing we can do, that is something for > > > CentOS infra folks. > > > > > > > Well, we need to tell CentOS infra folks which tags should be published > and > > where :-) > > So, I can open a ticket for adding the mappings for fluentd-012 tags, > where > > the packages should land? > > > > https://buildlogs.centos.org/centos/7/opstools/$basearch/fluentd/ ? > > guessed above because on mirrors we have: > > http://mirror.centos.org/centos/7/opstools/x86_64/fluentd/ > > on buildlogs, the path is https://buildlogs.centos.org/ > centos/7/opstools/x86_64/logging/ > > There is https://bugs.centos.org/view.php?id=12718 > which also requests to publish packages from > opstools7-fluentd-012-release > to https://mirror.centos.org/centos/$releasever/opstools/$basearch/ > > Maybe I've missed something? > Brian, can you please look again at https://bugs.centos.org/view. php?id=12718 ? As Matthias noted, there was already a request for this publishing. > > Matthias > -- > Matthias Runge <mrunge(a)redhat.com> > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Re: [CentOS-devel] [OpsTools] fluentd packages tagging
by Sandro Bonazzola 29 May '17

29 May '17

On Mon, May 29, 2017 at 10:15 AM, Matthias Runge <mrunge(a)redhat.com> wrote: > On Fri, May 26, 2017 at 07:55:32AM -0600, Rich Megginson wrote: > > On 05/26/2017 02:59 AM, Sandro Bonazzola wrote: > > > Hi, > > > I just discovered we have an issue with the package tagging about > fluentd. > > > fluentd-0.12.26-2.el7 > > > > $ cbs list-tags |grep opstool|grep release > > > opstools7-common-release > > > opstools7-elastic-2-release > > > opstools7-elastic-common-release > > > > We should get rid of these elastic tags, or at least ignore them, and if > > there are any packages that we need in those tags, we should add them to > > fluentd-012. > > > > > opstools7-fluentd-012-release > > > opstools7-perfmon-common-release > > > opstools7-sensu-023-release > > > opstools7-sensu-027-release > > > opstools7-sensu-common-release > > > > > > can we review the mappings in order to get fluentd packages correctly > > > published? > > > Personally I would be happy if fluentd and collectd can be in their own > > > repo so they won't require openstack as dependency repo. > > Packages tagged and not landing somewhere is unfortunate and should be > sorted out. > Unfortunately, that is nothing we can do, that is something for > CentOS infra folks. > Well, we need to tell CentOS infra folks which tags should be published and where :-) So, I can open a ticket for adding the mappings for fluentd-012 tags, where the packages should land? https://buildlogs.centos.org/centos/7/opstools/$basearch/fluentd/ ? guessed above because on mirrors we have: http://mirror.centos.org/centos/7/opstools/x86_64/fluentd/ > > I'm fine with getting rid of opstools7-elastic-* tags, we don't use them > anymore and afaik, we won't do in the future. > Ok, so if nobody objecting, I'll open a ticket tomorrow morning for removing those tags from cbs. > > A while ago, we moved the packages relying on openstack packages to the > cloud sig, and cremoved the dependency of openstack from opstools. > Unfortunately, the resulting centos-release-opstools build[1] > was not tagged and pushed correctly. > > [1] http://cbs.centos.org/koji/buildinfo?buildID=16800 now tagged correctly, not yet in http://mirror.centos.org/centos/7/extras/x86_64/Packages/ but should be just a matter of sign and publish which should hopefully happen soon. > > -- > Matthias Runge <mrunge(a)matthias-runge.de> > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[OpsTools] fluentd packages tagging
by Sandro Bonazzola 26 May '17

26 May '17

Hi, I just discovered we have an issue with the package tagging about fluentd. fluentd-0.12.26-2.el7 <http://cbs.centos.org/koji/buildinfo?buildID=16789> has been tagged opstools7-fluentd-012-testing and opstools7-fluentd-012-release but never got published. The published package is fluentd-0.12.26-1.el7 <http://cbs.centos.org/koji/buildinfo?buildID=11354> because of opstools7-elastic-common-testing and Now, I don't have a clue on how tagging has been mapped to testing and release repo but I think we need to fix it. Initial request was: https://bugs.centos.org/view.php?id=12718 with following mappings: for opstools SIG, could you please collect packages from opstools7-perfmon-common-release opstools7-common-release opstools7-elastic2-release opstools7-sensu-common-release opstools7-sensu-027-release and sync them to https://mirror.centos.org/centos/$releasever/opstools/$basearch/ Right now we have following tags: $ cbs list-tags |grep opstool|grep release opstools7-common-release opstools7-elastic-2-release opstools7-elastic-common-release opstools7-fluentd-012-release opstools7-perfmon-common-release opstools7-sensu-023-release opstools7-sensu-027-release opstools7-sensu-common-release can we review the mappings in order to get fluentd packages correctly published? Personally I would be happy if fluentd and collectd can be in their own repo so they won't require openstack as dependency repo. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel May 2017