devel

devel@lists.centos.org

5 participants
4641 discussions

centos7.2 for ppc64le
by liu_xbing 30 Oct '15

30 Oct '15

Hi All: When is the moment to release centos7.2, especially centos7.2 for ppc64le? if the features of kvm for ppc64le are same as kvm for x86 in centos7.2? Thanks! 2015-10-30 liu_xbing

2 1

atomic-sig: Meeting minutes from 2015-10-29
by Jason Brooks 29 Oct '15

29 Oct '15

Here are the minutes[1] from our atomic-sig meeting today. We hold our meetings each Thursday at 16:00 UTC. For your calendaring convenience, you can subscribe to a calendar of centos sig meetings w/ this calendar[2]. For more info on the calendar, see here[3]. Meeting summary --------------- * LINK: Last meeting's Minutes https://www.centos.org/minutes/2015/october/centos-devel.2015-10-15-16.02.h… (jbrooks, 16:08:29) * TOPIC: action item review (jbrooks, 16:09:05) * LINK: Download page w/ added quickstart info https://wiki.centos.org/SpecialInterestGroup/Atomic/Download/ (jbrooks, 16:10:08) * ACTION: kbsingh to write up how to qcow2ami (jbrooks, 16:15:10) * ACTION: jbrooks to post byo docs to centos wiki (jbrooks, 16:16:16) * LINK: Message to list w/ 4week release summary https://lists.centos.org/pipermail/centos-devel/2015-October/013957.html (jbrooks, 16:17:11) * ACTION: dustymabe and kbsingh to get together and talk tunir testing (jbrooks, 16:18:59) * open floor (jbrooks, 16:22:54) Meeting ended at 16:23:56 UTC. [1] https://www.centos.org/minutes/2015/october/centos-devel.2015-10-29-16.05.t… [2] https://git.centos.org/raw/sig-core!calendar.git/master/output!irc-meetings… [3] http://seven.centos.org/2015/06/centos-irc-meeting-calendar-now-available/ --- Jason Brooks Red Hat Open Source and Standards @jasonbrooks | @redhatopen http://community.redhat.com

1 0

Where can I get the source code of the qemu-kvm package in centos7
by 管强 28 Oct '15

28 Oct '15

Hi experts, >From http://mirror.centos.org/centos/7/os/x86_64/Packages/ site, I can find qemu-kvm rpm package. And I want to see the source code of qemu-kvm for this package, where can I find it? >From the package name 'qemu-kvm-1.5.3-86.el7.x86_64.rpm <http://mirror.centos.org/centos/7/os/x86_64/Packages/qemu-kvm-1.5.3-86.el7.…>', the qemu version is 1.5.3. Are the source code just the same as code from site http://git.qemu.org/ with 1.5.3 tag? Regards, Jackie

2 2

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

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