devel October 2015

devel@lists.centos.org

41 participants
39 discussions

CBS/Infra Meeting 26-Oct-2015 1400UTC
by Brian Stinson 26 Oct '15

26 Oct '15

Hi 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 Agenda: - Status Updates - Work on the final task list for deploying Central Auth - Open Floor - Last half of the meeting devoted to a intro presentation to ci.centos.org See you there! --Brian

1 0

Why release notes lacks CentOS-6.7 LiveCD Checksum
by SZ Quadri 24 Oct '15

24 Oct '15

Can someone kindly enlighten why CentOS-6.7-i386-LiveCD has been excluded from the checksum provided on https://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.7 If you are providing it from all the download sources/mirrors; then please include the checksum in the release page also so that one can verify after downloading. I want to use 6.7 livecd on some old hardware and have no way to make sure the image is safe to use. If possible kindly do consider adding sha256 checksum to the page. Regards -- SZ Quadri http://twitter.com/szquadri

2 2

centos iso
by liu_xbing＠sina.com 23 Oct '15

23 Oct '15

What time does the centos iso to be release

2 1

[release] RDO Liberty released in CentOS Cloud SIG
by Alan Pevec 22 Oct '15

22 Oct '15

I am pleased to announce the general availability of the RDO build for OpenStack Liberty for CentOS Linux 7 x86_64, suitable for building private, public and hybrid clouds. OpenStack Liberty is the 12th release of the open source software collaboratively built by a large number of contributors around the OpenStack.org project space. The RDO community project ( https://www.rdoproject.org/ ) curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a founding member of the CentOS Cloud Infrastructure SIG ( https://wiki.centos.org/SpecialInterestGroup/Cloud ). The Cloud Infrastructure SIG focus on delivering a great user experience for CentOS Linux users looking to build and maintain their own onpremise, public or hybrid clouds. In addition to the comprehensive OpenStack services, libraries and clients, this release also provides Packstack, a simple installer for proof-of-concept installations, as small as a single all-in-one box and RDO Manager ( https://www.rdoproject.org/RDO-Manager ) , an OpenStack deployment and management tool for production environments based on the OpenStack TripleO project. ------- QuickStart: Ensure you have a fully updated CentOS Linux 7/x86_64 machine, and run : sudo yum install centos-release-openstack-liberty sudo yum install openstack-packstack packstack --allinone For a more detailed quickstart please refer to the RDO Project hosted guide at https://www.rdoproject.org/QuickStart For RDO Manager consult https://www.rdoproject.org/RDO-Manager page. RDO project is closely tracking upstream OpenStack projects using the Delorean tool[1] which is producing RPM packages from upstream development branches. Since the previous OpenStack Kilo release, RDO is participating in the Cloud SIG and using CentOS provided infrastructure. Towards the end of developement cycle packages are imported into CentOS Cloud SIG buildsystem[2] and get eventually published in Cloud SIG repositories[3]. [1] http://trunk.rdoproject.org/ [2] http://wiki.centos.org/HowTos/CommunityBuildSystem [3] http://mirror.centos.org/centos/7/cloud/x86_64/ -------- Getting Help: The RDO Project provides a Q&A service at ask.openstack.org, for more developer oriented content we recommend joining the mailing list at https://www.redhat.com/mailman/listinfo/rdo-list. Remember to post a brief introduction about yourself and your RDO story. You can also find extensive documentation at https://www.rdoproject.org/Docs. We also welcome comments and requests on the CentOS Mailing lists ( https://lists.centos.org/ ) and the CentOS IRC Channels ( #centos on irc.freenode.net ), however we have a more focused audience in the RDO venues. To get involved in the OpenStack RPM packaging effort, see https://www.rdoproject.org/Get_involved and https://wiki.centos.org/SpecialInterestGroup/Cloud Join us in #rdo on the Freenode IRC network, and follow us at @RDOCommunity on Twitter. And, if you're going to be in Tokyo for the OpenStack Summit next week, join us on Wednesday at lunch for the RDO community meetup ( http://sched.co/4MYy ). I'd like to thank all RDO developers and CentOS Project for their effort and support resulting in this release, especially dmsimard - for continuously improving RDO CI jpena - for keeping Delorean service up and running jruzicka - for the rdopkg auto-magic number80 - for countless reviews and packaging wisdom social - for puppet module mastery trown - for leading RDO Manager side of the show! Special thanks to all the folks who helped with last minute testing in IRC #rdo channel ! Thanks, Alan Pevec Cloud SIG and RDO project member

4 3

atomic-sig: proposing a process for centos atomic four-week release
by Jason Brooks 22 Oct '15

22 Oct '15

The four-week release of CentOS Atomic Host is set to consist of CentOS core plus a set newer "atomic" packages[1], built for CentOS in the CBS, with versions tracking what's in Fedora Latest Stable (currently F22, soon to be F23). In the downstream rebuild version of CentOS Atomic Host, these "atomic" packages come from the CentOS Extras repository, built from upstream RHEL AH code. ## Atomic pkgs in the CBS, today and tomorrow There are versions of all/most of the "atomic" pkgs in the CBS (in the atomic7-testing and virt7-common-candidate tags), but which versions, and when they're updated, and where they live, isn't governed by any set process. It may make sense to add a new tag specifically for the 4wk release. ### Here's a rough process proposal: 1. We pay attention to upstream releases of "atomic" packages, and pay attention to the available versions of those packages in Fedora latest testing. If the packages in Fedora latest testing are older than the currently released upstream versions, we ping the Fedora package maintainer about updating to the latest released version. 2. We help move Fedora packages from testing to stable by testing them and giving them karma. 3. We take the stable "atomic" packages from Fedora latest and rebuild them for CentOS 7 in the CBS, using a tag for this purpose. We automate this if, possible. 4. We feed the repo backing this CAH-4wk tag into our 4wk/devel buildscript (see https://github.com/CentOS/sig-atomic-buildscripts/tree/devel), build repo/images, test those images, images/trees that pass tests become our four-week releases, released, presumably, every four weeks or so. Again, automating as many steps as possible. [1] The "atomic" packages are: docker kubernetes etcd flannel cloud-init ostree atomic cockpit Finding the latest stable or testing version of a pkg in Fedora. For docker (replace pkg name as needed): https://bodhi.fedoraproject.org/updates/?packages=docker&status=stable https://bodhi.fedoraproject.org/updates/?packages=docker&status=testing Let's discuss this here on the list and at next week's atomic sig meeting. --- Jason Brooks Red Hat Open Source and Standards @jasonbrooks | @redhatopen http://community.redhat.com

1 0

Canceled Atomic SIG meeting today
by Dusty Mabe 22 Oct '15

22 Oct '15

A number of us will be unavailable for the meeting today so we have elected to cancel. See you next week! Dusty

1 0

cbs credentials on ci infra
by Karanbir Singh 22 Oct '15

22 Oct '15

hi, it would be great to implement jobs in the CI infra that can tag or reject content in cbs tags based on test output. But in order to do this, we need to be able to run a koji client in the same place, and that in turn means koji credentials. since the ci infra is all public and we dont want to publish the creds there, thoughts around how we might be able to do this ? One option might be to host the creds and koji itself on the jenkins-slave nodes, so its not pushed to the ci test infra itself, and use the feedback from the test run to make a decision on the slave. This does ofcourse complicate the jenkins job setup dramatically ( from the existing simple, grab machine, deploy tests, run tests, report success/fail ). Thoughts on other mechanics ? if at all possible ? Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 4

Re: [CentOS-devel] Howto Install gluster (server)?
by centos-devel 22 Oct '15

22 Oct '15

hi Karanbir and thanks for your reply. I just subscribed to centos-del (after intermittent longtime lurking) so some introduction may help. I have been experimenting with glusterfs on Fedora and Debian for a good while now and decided it was time to try and roll out a 'prod like' setup. After a fair bit of searching through obsolete webpages and reading through mailing lists I found the centos CBS and koji builds: Whilst I do not _require_ to be running absolute latest build I do need something recent. I was hoping to find relatively recent builds to enable a workflow whereby I produce easily maintainable 3.7+ gluster containers without me having to follow development, apply patches, compile from source etc. ATM I only actually require a build later than 3.7.2 to fix bug: https://bugzilla.redhat.com/show_bug.cgi?id=1222065 > use the user-facing content published to the buildlogs, thats what it > exists for : http://buildlogs.centos.org/centos/7/storage/ While the old-but-stable 3.6.2 build on buildlogs would be fine for 'prod', I am still at the 'dev' or 'pre-prod' stage and feature development and bugfix is underway in 3.7 series- as you know. I would be very happy to be able to test 'candidate' or 'testing' builds. Initially my testing is in VMs but subsequently I will be testing installing, updating and maintaining (docker) containers. So any suggestions for how I can access Centos builds of Gluster 3.7+ ? Once again, Thanks In Advance. :-)

3 2

Re: [CentOS-devel] Howto Install gluster (server)?
by centos-devel 22 Oct '15

22 Oct '15

> this image highlights content movement from cbs into various places : > http://www.karan.org/CBS_ContentPromotion.png Thanks Karanbir for posting that link to the explanatory diagram That certainly helped my understanding. :-) So now I am looking at the published builds, rather than koji links I find http://cbs.centos.org/repos/storage7-testing/x86_64/os/repoview/ Which seems to me to contain older stuff built from storage7-testing http://cbs.centos.org/koji/taginfo?tagID=9 and http://cbs.centos.org/repos/storage7-gluster-37-candidate/x86_64/os/repovie… which I try. # mkdir storage7-gluster-37-candidate # cd ~/admin/storage7-gluster-37-candidate/ wget --no-verbose --no-parent --recursive --level=1 --no-directories http://cbs.centos.org/repos/storage7-gluster-37-candidate/x86_64/os/Package… [root@vm407 storage7-gluster-37-candidate]# ls -alrt total 4136 -rw-r--r--. 1 root root 46024 Aug 31 16:39 glusterfs-coreutils-0.0.1-0.1.git0c86f7f.el7.x86_64.rpm -rw-r--r--. 1 root root 46404 Sep 1 10:14 userspace-rcu-devel-0.7.7-1.el7.x86_64.rpm -rw-r--r--. 1 root root 68672 Sep 1 10:14 userspace-rcu-0.7.7-1.el7.x86_64.rpm -rw-r--r--. 1 root root 1353308 Oct 14 22:31 glusterfs-server-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 90732 Oct 14 22:31 glusterfs-extra-xlators-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 772464 Oct 14 22:31 glusterfs-client-xlators-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 177420 Oct 14 22:31 glusterfs-cli-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 79104 Oct 14 22:31 glusterfs-api-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 59008 Oct 14 22:31 glusterfs-rdma-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 128812 Oct 14 22:31 glusterfs-fuse-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 26976 Oct 14 22:31 python-gluster-3.7.5-1.el7.noarch.rpm -rw-r--r--. 1 root root 470360 Oct 14 22:31 glusterfs-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 37996 Oct 14 22:31 glusterfs-ganesha-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 182764 Oct 14 22:31 glusterfs-geo-replication-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 168972 Oct 14 22:31 glusterfs-devel-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 346892 Oct 14 22:31 glusterfs-libs-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 29444 Oct 14 22:31 glusterfs-resource-agents-3.7.5-1.el7.noarch.rpm -rw-r--r--. 1 root root 36412 Oct 14 22:31 glusterfs-api-devel-3.7.5-1.el7.x86_64.rpm -rw-r--r--. 1 root root 5595 Oct 21 13:42 index.html -rw-r--r--. 1 root root 5595 Oct 21 13:42 index.html?C=N;O=D -rw-r--r--. 1 root root 5595 Oct 21 13:42 index.html?C=M;O=A -rw-r--r--. 1 root root 5595 Oct 21 13:42 index.html?C=S;O=A -rw-r--r--. 1 root root 5595 Oct 21 13:42 index.html?C=D;O=A drwxr-xr-x. 2 root root 4096 Oct 21 13:43 . drwxr-xr-x. 6 root root 4096 Oct 21 13:59 .. [root@vm407 storage7-gluster-37-candidate]# [root@vm407 admin]# cd .. [root@vm407 admin]# yum localinstall ./storage7-gluster-37-candidate/*.rpm | tee yum_localinstall_storage7-gluster-37-candidate <snip> Error: Package: glusterfs-ganesha-3.7.5-1.el7.x86_64 (/glusterfs-ganesha-3.7.5-1.el7.x86_64) Requires: nfs-ganesha-gluster You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@vm407 admin]# A search for nfs-ganesha-gluster only brought me to obsolete builds: nfs-ganesha http://cbs.centos.org/koji/packageinfo?packageID=98 nfs-ganesha-2.1.0-7.el7 2014-10-01 10:45:45 http://cbs.centos.org/koji/buildinfo?buildID=126 which contains: nfs-ganesha-2.1.0-7.el7.x86_64.rpm nfs-ganesha-fsal-gluster-2.1.0-7.el7.x86_64.rpm nfs-ganesha-debuginfo-2.1.0-7.el7.x86_64.rpm So it appears that I am stuck at that unresolved dependancy. Any suggestions will be much appreciated. Thanks In Advance. :-)

3 2

content movement from CBS into various places.
by Karanbir Singh 21 Oct '15

21 Oct '15

hi this image highlights content movement from cbs into various places : http://www.karan.org/CBS_ContentPromotion.png note that the sync to buildlogs is automatic, but you need to opt into that, also move from -release tag to mirror.centos.org is manual, since it involves a sign process ( again, sig's must opt into that, its not doing automatically, yet ) regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel October 2015