devel

devel@lists.centos.org

8 participants
4607 discussions

moving to a regular account admin schedule
by Karanbir Singh 19 Oct '15

19 Oct '15

hi folks, we've now gotten to a point where we regularly have account requests for various CentOS resources, to a point where its harder to track things down constantly. I'd like to move towards a schedule based admin cycle for the following resources: - cbs.centos.org - ci.centos.org - devcloud Ideally, this would run through in a way to have the backlog cleared on every alternate Monday, for the buildsystem meeting every alternate Monday to confirm new-users onboarded and followup with any new-user training we need to run through. Note that every resource needs some level of support or sponsorship, so folks requesting accounts should make sure that is in place, before the next cycle. ofcourse we would look into emergency and downtime situations as soon as we are able to. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

CentOS-7 / powerpc LE bring up
by James O'Connor 15 Oct '15

15 Oct '15

Starting a new status thread for CentOS 7 POWER Little Endian. On Monday, Arrfab turned over the keys to a pairf of shiny new Fedora 21 ppc64le VMs running atop PowerKVM. I created a f21-ppc64le mock config and built a Linux from Scratch [1] toolchain with CentOS 7.1.1503 sources. This is necessary to jump back in time from Fedora 21 glibc-2.20 to CentOS 7 glibc-2.17. I then proceeded to build enough ppc64le.el7 rpms with the LFS toolchain to construct a minimal c7.01.01-ppc64le mock buildroot. As of last night, the minimal c7.01.01-ppc64le buildroot is complete and I’m untangling circular dependencies in the CentOS 7.1.1503 source rpms. I’ve built 700 of 2523 source packages so 27% complete with this first pass. Next, I’ll bootstrap java-1.7.0-openjdk and continue to loop through ppc64le rpm builds with mock. In the next 1-2 weeks, I should have 95+% of the source packages building for ppc64le. At which point we can create the first CentOS 7 ppc64le VMs and rebuild c7.01.02-ppc64le atop CentOS 7 instead of Fedora 21. CentOS 7.1.1503 ppc64le Alpha images for the early adopters sometime after that. [1] http://www.linuxfromscratch.org/lfs/view/stable-systemd/

5 9

[Atomic] 20151001 Atomic seems to be broken
by Dusty Mabe 14 Oct '15

14 Oct '15

For some reason I can't seem to get it [1] to boot. I get a "No bootable device" massage from the BIOS for both libvirt/kvm and a local openstack setup. Can someone confirm or refute this? Dusty [1] - http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7.2015100…

2 3

Re: [CentOS-devel] [scl.org] validating scls being built
by Karanbir Singh 12 Oct '15

12 Oct '15

On 11/10/15 03:21, Subhendu Ghosh wrote: > It would also be useful if the repo definitions did not use > ReleaseVersion to allow use by CentOS and other distroa. let me see if we can parametrise those from the jenkins side of things - should be possible, and we can default to something that works here for the scl/cbs process. regards, > > Sent from Nine <http://www.9folders.com/> > > *From:* Karanbir Singh <mail-lists(a)karan.org> > *Sent:* Oct 10, 2015 6:29 PM > *To:* centos-devel(a)centos.org; sclorg(a)redhat.com > *Subject:* [scl.org] validating scls being built > > firstly, apologies for the cross post. > > I've setup an example to illustrate some very simple things we can do to > validate a collection. In this case the vagrant collection. > > https://github.com/kbsingh/validate-vagrant-scl has the test script. > > It does 2 things: > 1) makes sure all the rpms we expect to have in the repo are there. > 2) it will install the collection, run a centos/7 vagrant box, and run > the centos functional test suite inside the box. if this passes, we can > assert that vagrant installed ok, was able to run a libvirt backed box > properly, and was able to provide typical expected functionality. > > There maybe 100s more features of the collection we are not testing > here, but that might not be needed if a simple baseline is established. > And this test can be run, from triggers in ci.centos.org, watching the 3 > repos we care about for the vagrant collection ( ruby22 / ror41 and > vagrant itself ). > > thoughts ? > > > -- > Karanbir Singh > +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh > GnuPG Key : http://www.karan.org/publickey.asc > > _______________________________________________ > SCLorg mailing list > SCLorg(a)redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

1 0

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

12 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 Proposed Agenda: - Cloud SIG was curious about mirroring some tags to buildlogs.centos.org - 3rd party Repositories Proposal - Last half of the meeting devoted to an introduction to ci.centos.org https://plus.google.com/events/ckne86ufafpbfm00ducc9rl711g See you there! --Brian

1 0

validating scls being built
by Karanbir Singh 11 Oct '15

11 Oct '15

firstly, apologies for the cross post. I've setup an example to illustrate some very simple things we can do to validate a collection. In this case the vagrant collection. https://github.com/kbsingh/validate-vagrant-scl has the test script. It does 2 things: 1) makes sure all the rpms we expect to have in the repo are there. 2) it will install the collection, run a centos/7 vagrant box, and run the centos functional test suite inside the box. if this passes, we can assert that vagrant installed ok, was able to run a libvirt backed box properly, and was able to provide typical expected functionality. There maybe 100s more features of the collection we are not testing here, but that might not be needed if a simple baseline is established. And this test can be run, from triggers in ci.centos.org, watching the 3 repos we care about for the vagrant collection ( ruby22 / ror41 and vagrant itself ). thoughts ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Atomic-developer-bundle for inclusion in Atomic SIG
by Lalatendu Mohanty 08 Oct '15

08 Oct '15

Hi, Asapart of Project Atomic [1], we are working ona toolchain (as of now it is a Vagrant box),atomic-developer-bundle [2],for helping application developers package their microservice architecture applications for delivery vialinux containers.ADB (atomic developer bundle) is supported on GNU/Linux distributions, OSX and WIndows. It has (or isgoing to have) all the goodies that are part of Project Atomic to better enableLinux containers. Currently, the Vagrant box is based on CentOS. Therefore I think itmakes more sense toinclude it in the CentOS Atomic SIG. I believe this willopen channels with thecommunity and lead togreater participation. Let me know your thoughtson including the ADB as part of the Atomic SIG. For details please go through the README in ADB github repo [2] [1] https://github.com/projectatomic [2] https://github.com/projectatomic/adb-atomic-developer-bundle Thanks, Lala On behalf of ADB developers

4 10

New CentOS Atomic Host Release Available Now
by Jason Brooks 05 Oct '15

05 Oct '15

Today we're announcing an update to CentOS Atomic Host (version 7.20151001), 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(http://cloud.centos.org/centos/7/atomic/images/). The backing ostree repo is published to mirror.centos.org(http://mirror.centos.org/centos/7/atomic/x86_64/repo). CentOS Atomic Host includes these core component versions: * kernel-3.10.0-229.14.1.el7.x86_64 * cloud-init-0.7.5-10.el7.centos.1.x86_64 * atomic-1.0-115.el7.x86_64 * kubernetes-1.0.3-0.1.gitb9a88a7.el7.x86_64 * flannel-0.2.0-10.el7.x86_64 * docker-1.7.1-115.el7.x86_64 * etcd-2.1.1-2.el7.x86_64 * ostree-2015.6-4.atomic.el7.x86_64 If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: ## Upgrading $ sudo atomic host upgrade ## Images ### Vagrant CentOS-Atomic-Host-7-Vagrant-Libvirt.box(http://cloud.centos.org/centos/7/at omic/images/CentOS-Atomic-Host-7-Vagrant-Libvirt.box) (389 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box(http://cloud.centos.org/centos/7 /atomic/images/CentOS-Atomic-Host-7-Vagrant-Virtualbox.box) (400 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(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(http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Inst aller.iso) (672 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 allows flexibility to control the install using kickstarts and define custom storage, networking and user accounts. This is the recommended process for getting CentOS Atomic Host onto bare metal machines, or to generate your own image sets for custom environments. ### QCOW2 The CentOS-Atomic-Host-7-GenericCloud.qcow2(http://cloud.centos.org/centos/7/ato mic/images/CentOS-Atomic-Host-7-GenericCloud.qcow2) (393 MB) 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(http://www.projectatomic.io/blog/2014/10/getting-started-with-cloud-init /) NoCloud iso image. The Generic Cloud image is also available compressed in gz format(http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-G enericCloud.qcow2.gz) (391 MB) and xz compressed(http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host -7-GenericCloud.qcow2.xz) (390 MB). ### Amazon Machine Images Region Image ID ------ -------- sa-east-1 ami-1b52c506 ap-northeast-1 ami-3428b634 ap-southeast-2 ami-43f2bb79 us-west-2 ami-73eaf043 ap-southeast-1 ami-346f7966 eu-central-1 ami-7ed1d363 eu-west-1 ami-3936034e us-west-1 ami-6d9c5a29 us-east-1 ami-951452f0 ### SHA Sums 96586e03a1a172195eae505be35729c1779e137cd1f8c11a74c7cf94b0663cb2 CentOS-Atomic-Host-7.20151001-GenericCloud.qcow2 33d338bb42ef916a40ac89adde9c121c98fbd4220b79985f91b47133310aa537 CentOS-Atomic-Host-7.20151001-GenericCloud.qcow2.gz 73184e6f77714472f63a7c944d3252aadc818ac42ae70dd8c2e72e7622e4de95 CentOS-Atomic-Host-7.20151001-GenericCloud.qcow2.xz 4e09f6dfae5024191fec9eab799861d87356a6075956d289dcb31c6b3ec37970 CentOS-Atomic-Host-7.20151001-Installer.iso 92932e9565b8118d7ca7cfbe8e18b6efd53783853cc75dae9ad5566c6e0d9c88 CentOS-Atomic-Host-7.20151001-Vagrant-Libvirt.box 8f626bdafaecb954ae3fab6a8a481da1b3ebb8f7acf6e84cf0b66771a3ac3a65 CentOS-Atomic-Host-7.20151001-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(http://wiki.centos.org/SpecialInterestGroup/Atomic), based on upstream work from Project Atomic(http://www.projectatomic.io/). 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(https://lists.projectatomic.io/mailman/listinfo/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(http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic(https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode.

1 0

EL6 to EL7 Update Tool and Maintenance
by Johnny Hughes 05 Oct '15

05 Oct '15

All, There exists an update tool for moving from CentOS-6 to CentOS-7 .. the tool worked for awhile, but has gone into disrepair. It currently does not work (so don't use it !), but we would like to get it working and maintain it. The following git trees are involved in the tool: https://git.centos.org/summary/rpms!redhat-upgrade-tool https://git.centos.org/summary/rpms!preupgrade-assistant https://git.centos.org/summary/rpms!preupgrade-assistant-contents https://git.centos.org/summary/openscap The effort to keep this operational is a 'community effort' and it requires users from the community to volunteer to keep it functional. People often ask how they can help with the CentOS Project .. if you have the ability, this is one way. What we need is to get all the modifications that were written for the original test RPMs to be modified to work with the newer versions of the Source code. The old tree is here: http://dev.centos.org/centos/6/upg/Source/SPackages/ (Those changes are also in the git trees above) What we need is for patches to be re-factored and rolled into the new versions of all the packages. Patches can be submitted to this list as attachments .. a git am format would be best, as applied to the latest version of each package that is imported into git. We also need maintainers who will track updates to those branches and re-factor and submit patches, also to this list as attachments, when updated source is released. If we can not find volunteers, we are likely going to have to take down even the testing files, as they do not currently work. Thanks, Johnny Hughes

3 4

armv7hl CentOS status discussion
by Fabian Arrotin 05 Oct '15

05 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Don't want to start a thread in parallel, as there is already a dedicated mailing list for that. Just as a reminder that some discussions are happening regarding CentOS 7 on armv7hl (raspberry 2, bananapi, odroid, etc) on the arm-dev list ( https://lists.centos.org/mailman/listinfo/arm-dev ) If you want to join the fun, and see CentOS for armv7hl being finalized and released, feel free to discuss that on the list. Kind Regards, (and hope to see you there) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYScacACgkQnVkHo1a+xU6juACeM4792fEqcjlodzrp7wIYu++D uvoAn0jwts/imqkuz1/kw2vyiET20WxS =v2f+ -----END PGP SIGNATURE-----

1 0

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