devel June 2015

devel@lists.centos.org

49 participants
40 discussions

CentOS Linux 6 Vagrant
by Timothy Rees 10 Jun '15

10 Jun '15

Great to see a project CentOS 7 box made available for Vagrant. Are there any plans to provide an official CentOS 6 variant with the same update cycle? Cheers, Tim

2 2

devtoolset-3 rebuild in SCLo
by Honza Horak 09 Jun '15

09 Jun '15

On the last meeting [1] we talked about whether we need maven and rh-java-common for rebuilding devtoolset-3. Unfortunately it is a requirement right now, so we need to have maven and rh-java-common collections first. However, the maven and rh-java-common SCL dependencies are needed just for the devtoolset-3-ide part, so for devtoolset-3-toolchain and devtoolset-3-perftools we may remove the requirements temporarily. Anyway, there have been requests for devtoolset and gcc-5 especially, often from other projects based on CentOS, so copr builds are not enough. We're still not ready with the centpkg/lookaside-cache things, but what about to create necessary tags from devtoolset-3 collection and build packages from srpms for now? Thomas, is it ^ possible? What information do you need from me? Let's limit on sclo part and RHEL-7 only. Based on the tags we consulted before, that should mean to create: * sig-sclo7-devtoolset-3-sclo tag * sclo7-devtoolset-3-sclo-el7 target and associated buildroot Correct? Will it be possible to tag built packages (I speak still about scratch builds) to sig-sclo7-sclo, which other SIGs could depend on? [1] http://www.centos.org/minutes/2015/may/centos-devel.2015-05-20-14.31.html [2] https://copr.fedoraproject.org/coprs/rhscl/devtoolset-3-el7/builds/ Honza

5 5

Setting up fedmsg for centos
by Jan Chaloupka 08 Jun '15

08 Jun '15

Hi, CentOS does not have any equivalent to fedmsg bus [1] at the moment. What is it used for? Services (koji, pkgdb, ...) can send messages about their state and result of tasks they run into the bus to notify other service which can react accordingly. Thus creating a modular infrastructure. E.g. koji send a message about finished build. Agent read the message, trigger a jenkins job and run additional tests on the build. Daily statistics about number of finished /failed builds can be collected. Other application can have their own use cases. Example of bus topology [4]. [5] is another source of some info about fedora infrastructure. What needs to be done to set up the bus? Basic demo and setup of fedmsg, fedmsg-relay is at [3]. First would be great to setup the bus for koji. Koji runs on CentOS 6. fedpkg package is in epel6 repository [2]. We will be needing fedmsg-hub, fedmsg-relay, koji-hub and koji-plugin parts in the topology at the moment [4]. CentOS koji and Fedora koji are not exacly the same but both APIs are compatible. So maybe take an inspiration from Fedora's koji plugin. In order to set up bus and clients, endpoints has to be set. Setting of endpoints is discussed at [6]. Context of endpoints is described at [3]. Configuration files are shared and must be the same on all machines using the bus. Bus messages can be saved into database [7]. What we can start with? 1) create an instance of centos/fedora for fedmsg to run 2) create/reuse koji plugin (where it can be found?) 3) set/implement koji plugin to send messages for fedmsg What other application do you have in centos that could use fedmsg? Once there is a running msg bus, instances set, etc., it will be easier to debug and test. Ralph, Pierre, what would be the optimal distribution of instances for fedmsg? Is one instance of centos enough? What would be the best first step to set up fedmsg? Where can I found koji-plugin, resp. its implementation? This is only a discussion at the moment. Any other ideas are appreciated. Other issues and problems will arise while configuring the bus and koji. [1] https://github.com/fedora-infra/fedmsg/ [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=630367 [3] http://fedmsg.readthedocs.org/en/latest/deployment/ [4] http://fedmsg.readthedocs.org/en/latest/topology/ [5] https://fedoraproject.org/wiki/Messaging_SIG [6] http://fedmsg.readthedocs.org/en/latest/config/#term-endpoints [7] http://fedmsg.readthedocs.org/en/latest/deployment/#store-all-messages Kind Regards Jan

5 6

CentOS 7 (1503) i686 Beta Architecture
by Johnny Hughes 08 Jun '15

08 Jun '15

All, The Beta release of the 32-bit (i686) Architecture of CentOS-7 (1503) is currently on build logs. Right now, only the boot.iso is available, but after some testing from the users here with feedback, we can spin another tree with fixes and actual installer isos. http://buildlogs.centos.org/centos/7/os/i386/ updates are also here: http://buildlogs.centos.org/centos/7/updates/i386/ Current known issues are: 1. If installing on a QEMU (kvm) i386 VM, you must modify the VM cpu to use "copy host cpu" http://bugs.centos.org/view.php?id=8748 2. The gnome desktop will not exit or log out from the menu. http://bugs.centos.org/view.php?id=8834 If someone can figure out how to fix this issue, it would be much appreciated :) ====================== Please report bugs on bugs.centos.org or to this Centos-Devel mailing list will we do the beta testing and lets see if we can find/fix all the issues before the full release of this arch. Thanks, Johnny Hughes

12 21

CBS/Infra Meeting 08-Jun-2015 14:00 UTC
by Brian Stinson 08 Jun '15

08 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey All, It's time for another meeting to talk about the Community Build System[0]. We will meet in #centos-devel on irc.freenode.net Proposed Agenda: - - Status Updates: - General - Central Auth - - Fedmsg[1] in the CBS - - Merging the ci.dev.c.o and ci.c.o Jenkins instances Cheers! Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVdK1jAAoJEIMGvNKzCweM7WUP/RULhbw6LCSzB/Hu5sMwVldp /ZGB/PQLXFGInUIv7McT5pfjlD5VBgsG+B8XXepxs/YbMQM/cGufRy0qhRubvs/U PNGxNAjZlu8RNTt9r/wVyZm2QoMmKzq67k4EZKCTr1cXT2KpIG5OoNgW3PuQESNH ygKNtrLJAK4EiPOoStIFVkEGfCL8YbRXvWVXpGglrLRWC1rzXbgjLfBOFF7CA3sI SVBGhVW368VJTRC1zrEUr1GVX69afPP4OKtdojxnMYPf2so0l9X0fpAxlg7qKAac Wx56uqF7cq7P4E5Fozk2J2yVfy24p61z9E4U+FPRzBcUSAUHr2kjS8iH1+BfjaZh Zk0B9VgT3WaKb5SMf0WWJQ/nn8ION42DV4ca15DHARqJS3MgUPnKOIYQRm3uUNfU hQD0SKs+eJR0wK84fC/QTyCRNUwZE9RLUrO4PJ53tI5vy9LdWcU0qBEwIZvMPgE2 7L1JZRWeJky8WbNRQrCBy1tTvRXGOcikx8S98GbZoPnw47Oa6qZ8rjq6Qb+z3Z26 g+VfIuQQ//Esh36wv4ir+fa8+IXkm59EDOyfjSVfkuCzat4MFX3Z4w+H0R9Bvs3c mc42197T+rgjKaCOOVWCBWSMEdjYTbfSSYE9jC+6gyRqT4T+mkLSTjlLMkyWssUJ 5D/L4NCwQlHnQBH6Q4zQ =pqC0 -----END PGP SIGNATURE-----

1 1

python build script for ci.centos.org
by Karanbir Singh 08 Jun '15

08 Jun '15

hi, I've just pushed a basic script that uses the Duffy[1] interface to request machines, run jobs, discard machines. The source for this is at https://github.com/kbsingh/centos-ci-scripts . Its pretty simple, but should work. Help to expand this into a more functional script is welcome. Specially getting some exception handling around failed builds and failed requests to Duffy. Hopefully this script should be helpful enough that projects using ci.centos.org can just use it as is. Someone mentioned the thought of writing a Duffy plugin for Jenkins directly, and I am not sure if that is very useful over a simple script like this. regards [1]: http://wiki.centos.org/QaWiki/CI/Duffy - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Automated tracking of RPMs from EPEL
by Lalatendu Mohanty 08 Jun '15

08 Jun '15

Hi, For Storage SIG (Gluster) we have dependency on a pkg i.e. userspace-rcu from EPEL . Looks like we can not have EPEL repo linked to the SIG target. So we have to rebuild the pkg in SIG and maintain it. I am not interested to maintain the pkg myself in SIG as I dont have skills to maintain it. However I am fine to rebuild the pkg if I get notified if a newer version of it is available in EPEL or we have some automation do the rebuild. I am looking for suggestion or alternative of how this is being done in other SIGs or can be done in CBS. Thanks, Lala

1 0

Resources Needed for Doc Toolchain Project [GSoC]
by kunaal jain 05 Jun '15

05 Jun '15

Hi, As discussed earlier about the workflow, I and Lei will need a server space to host Bugzilla, a test repository at Github + a git repository at git.centos.org. This is temporary, required for development and testing. Please let us know how do we obtain the same? We need it to get started on our project. Thanks! Regards, Kunaal

6 12

Re: [CentOS-devel] Regarding GSoC project : Documentation Toolchain
by Lei Yang 05 Jun '15

05 Jun '15

> On Sat, May 30, 2015 at 1:04 AM, kunaal jain <kunaalus at gmail.com <http://lists.centos.org/mailman/listinfo/centos-devel>> wrote: > > The typical workflow might look like this: > > > > 1. Author writes content in markdown language. > > 2. Makes a pull request on github. > > Is this github.com or, a git instance off CentOS infrastructure? Authors are supposed to make a pull request on github. > > > 3. Corresponding to the pull request a issue is created on bugzilla. > > 4. CentOS staff can either review the article on github pull request, or on > > bugzilla. > > I would recommend using one tool for handle inbound and review. Having > 2 tools that need to be kept synchronized would add overhead that you > don't want to deal with. Also, it has the effect of puzzling > contributors. Thanks for your suggestion! Staff will do the review only on bugzilla, but we think some contributors are only familiar with github, so we sync the comments between two platforms, so contributors don’t need to leave github to finish the whole process. > > > 5. Comments are two way synced. > > 6. At each point the article can be viewed on bugzilla, using an extension > > we propose to make. > > 7. After many iterations of commenting, and improving, article is finally > > accepted. > > Have you considered review workflow tools like Gerrit? We considered Gerrit and other code review platforms. However we are handling markdown or some similar markup languages, so we plan to build the doc on a CI and let the staff review the built docs. > > > 8. Staff tags it, and pushes to git.centos.org. > > 9. Using git.centos.org, new website is generated and pushed. > > 'Website' or, is the content rendered from the version control (g.c.o) > and pushed live? The content is rendered from g.c.o. built into HTML files using static site generator tool like jekyll. Regards, Lei

2 4

Meeting log from this week's cloud sig meeting
by Kushal Das 05 Jun '15

05 Jun '15

=============================== #centos-devel: CentOS Cloud SIG =============================== Meeting started by kushal at 15:00:32 UTC. The full logs are available at http://centos.org/minutes/2015/may/centos-devel.2015-05-28-15.00.log.html . Meeting summary --------------- * Roll Call (kushal, 15:00:39) * tmrts is developing a cloud instance contextualization tool as a GSoC project (kushal, 15:04:45) * ACTION: tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. (kushal, 15:06:57) * tmrts's project will focus on CentOS Atomic Host. (kushal, 15:08:01) * Update from OpenNebula (kushal, 15:09:52) * jmelis is studying about CBS. (kushal, 15:11:39) * jmelis is developing a set of tests to test the CBS based installs. (kushal, 15:12:43) * LINK: http://meetbot.debian.net/Manual.html (kushal, 15:14:27) * Openstack updates (kushal, 15:15:21) * Open Floor (kushal, 15:22:41) * LINK: http://community.redhat.com/blog/2015/05/highlights-from-rdo-meeting-at-ope… (kushal, 15:24:29) * LINK: https://review.openstack.org/#/c/185187/ (number80, 15:26:06) * planning a RDO track at FOSDEM CentOS dojo (number80, 15:29:18) Meeting ended at 15:35:26 UTC. Action Items ------------ * tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. Action Items, by person ----------------------- * tmrts * tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (62) * rbowen (30) * number80 (26) * jmelis (11) * tmrts (10) * Arrfab (5) * alphacc (3) * centbot (3) * Evolution (3) * hughesjr (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal Das -- Fedora Cloud Engineer CPython Core Developer Director @ Python Software Foundation http://kushaldas.in

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2015