devel

devel@lists.centos.org

8 participants
4623 discussions

6.8 and AWS AMIs
by BC 25 May '16

25 May '16

Is there a planned timeline for 6.8 AMIs? Will an official AMI kickstart be provided in a repo somewhere (or perhaps there already is and I can't find it)? Thanks for all the hard work, guys!

2 1

CentOS PaaS SIG meeting (2016-05-25)
by Troy Dawson 25 May '16

25 May '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 25 May 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- origin 1.2.0 -- centos-openshift-future --- golang 1.6.2 -- Automated testing -- images / image building -- Documentation - Next 2 SIG Meetings -- tdawson will be gone for next two meetings -- Will someone want to chair the meetings? -- Do we want to skip the meetings for two weeks? - Open Floor Last Weeks minutes: https://www.centos.org/minutes/2016/may/centos-devel.2016-05-18-17.01.log.h…

1 0

The SCL wiki page contents and confusing SCL situation
by James Hogarth 24 May '16

24 May '16

Hi, I thought I'd start an article on my personal blog on the various options for newer PHP (in particular), python, ruby etc options in CentOS - particularly given some of the base packages in EL6 have now passed EOL upstream and consequently some applications (eg OwnCloud) now have minimal dependencies greater than in base. What I found on initial looks to SCL was at best confusing and in areas outright misleading, with help needed from Dominic in #centos-devel to work through the present SCL situation. Doing a general Google search (or the @scl keyword in #centos) will take someone to here: https://wiki.centos.org/AdditionalResources/Repositories/SCL This refers to an old centos-release-SCL package which is still in the repos and would direct the user to unmaintained old versions. The correct package is actually centos-release-scl ... yes just the case needs to change. The documentation for centos-release-scl stuff (ie the CentOS SCL SIG stuff) is pretty much nonexistent for a user needing a newer version of a package. These pages are very CentOS developer focused and not really useful for the end user: https://wiki.centos.org/SpecialInterestGroup/SCLo https://wiki.centos.org/SpecialInterestGroup/SCLo/CollectionsList Then once the right package is installed the user can see there is php54, php55 and rh-php56 packages but it's not clear why the difference in the naming and there's nothing that highlights to someone that if they want to use php55 or rh-php56 they'll need to handle a migration to rh-httpd24 as well. I'd suggest the first step is to have centos-release-scl obsolete centos-release-SCL so that users are not left on an unmaintained repository. Then as I gather data for my article I'd really like to flesh out and improve the 'user facing' SCL wiki page. Thoughts on this? James

4 7

Important infra outage notification - dates to be discussed
by Fabian Arrotin 20 May '16

20 May '16

Due to some reorganization at the DC/Cage level, we'll have to shutdown/move/reconfigure a big part of our hosted infra for the following services : - cbs.centos.org (Koji) - accounts.centos.org (auth backend) - ci.centos.org (jenkins-driven CI environment) We're working on a plan to minimize the downtime/reconfiguration part, but at first sight, due to the hardware move of the racks/recabling parts/etc, the announced downtime will be probably ~48h. What does that mean ? That during this window, nobody will be able to build/tests packages, nor be able to triggers automatically CI jobs (important). As said, we're working on an agenda with the team operating the DC, but we'd like you (cbs and ci users) to give us feedback on the best (or worst ?) time line for such migration. For example if you know that your $project will have a release soon, and already have an agenda for such release (and so build/ci) and that you rely on that infra, we'd like you to communicate those informations to us, so that we can try to find the best possible time slot for the migration, minimizing the impact on the whole CentOS ecosystem (and so for all our users) Feel free to answer in this thread, or find us in #centos-devel on freenode. -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

CentOS Atomic Host test images
by Jason Brooks 19 May '16

19 May '16

There are test images available for what will be the next CentOS Atomic Host release: https://ci.centos.org/artifacts/sig-atomic/downstream/images/ After we've done some testing, we'll update the official CentOS Atomic Host ostree repo, probably early next week, and announce the release. We're going to hold off on producing new release images for a week or so, in order to sync up with the regular monthly centos media refresh cycle. These test images include two versions of docker: docker-1.9.1-40 and docker-latest-1.10.3-22.1. To read more about docker vs. docker-latest, see: https://lists.centos.org/pipermail/centos-devel/2016-May/014731.html. For your non-atomic needs, these docker pkgs, along with the other content included in these images, are now available in the standard centos repositories -- docker, kubernetes and most of the other "atomic" pkgs live in the extras repo. Happy testing, Jason

1 0

[Fwd: [CentOS] ati fglrx vs amdgpu absolutely mad on R5 m255 vs IRIS P520]
by Andreas Benzler 19 May '16

19 May '16

1 0

Released ADB 2.1.0
by Lalatendu Mohanty 19 May '16

19 May '16

We have released the Atomic Developer Bundle 2.1.0 through CentOS Atomic SIG. The ADB 2.1.0 release also includes release of following ecosystem projects: * adb-utils 1.6: A set of utility scripts and configuration files for ADB. * vagrant-service manager 1.0.2 : Enables easier access to the features and services provided by ADB ADB 2.1.0 release adds new featuresand several bug fixes, including: - Addingcockpitin ADB box.Refer the project documentation for start using it with ADB [5]. - Removed some unwanted RPMs to reduce the size of the Vagrantbox. adb-utils 1.6release includes several enhancements , including - Added bash script auto completion for oc, oadm and OpenShift - SCCLI is re-written in Python with some enhancements. vagrant-service-manager 1.0.2 release adds new features and bug fixes. For its release announcement , please refer https://www.redhat.com/archives/container-tools/2016-May/msg00019.html Known issues: * Running AtomicApp in ADB fails. Refer: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/329 * Following workaround can be used till the above issue is fixed. $ sudo -E atomic run projectatomic/helloapache This release also includes many smaller changes and bugfixes, which are detailed in the release changelog of adb-utils [1]andADB [2]. Please update the ADB Vagrant box [4] and the vagrant-service-manager ($ vagrant plugin update vagrant-service-manager) and give the new ADB version a spin. [1] https://github.com/projectatomic/adb-utils/releases/tag/v1.6 <https://github.com/projectatomic/adb-utils/releases/tag/v1.6> [3] https://github.com/projectatomic/adb-atomic-developer-bundle/tree/v2.1.0 <https://github.com/projectatomic/adb-atomic-developer-bundle/tree/v2.1.0> [4] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do… [5] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do…

1 0

Re: [CentOS-devel] [RFC][opstools] Operational tools SIG (was logging and monitoring...)
by Martin Magr 19 May '16

19 May '16

On Mon, May 16, 2016 at 3:30 PM, Rich Megginson <rmeggins(a)redhat.com> wrote: > On 05/13/2016 01:12 AM, Matthias Runge wrote: > >> Hello, >> >> I would like to re-iterate my interest in having a SIG in CentOS >> to provide all kinds of tools for operators providing >> infrastructure by using CentOS. >> > > +1 > > >> The scope should be more than just simply packaging applications. >> Another part should be to provide puppet manifests or ansible playbooks >> to get things quicker up and running. >> > > +1 - should ideally provide a standalone installer, and puppet > manifests/ansible playbooks that can be included in other projects (puppet > manifests for RDO TripleO, ansible playbooks for openshift-ansible, etc.) > > >> Ideally, I would start with providing something like >> * elsasticsearch/fluentd/kibana for centralised logging >> > > +1 > > * collectd/graphite/grafana for performance monitoring >> * sensu/uchiwa for availability monitoring >> > +1 > >> We have already seen around 10 persons interested in helping, testing, >> trying out and providing feedback. >> >> For communcations etc. I would propose to start small, and to share >> already existent CentOS channels (email-lists, irc-channel). >> > > Emails should use the [opstools] prefix? > > This >> decision should be revisited, once amount of SIG related communication >> becomes annoying in general channels. >> >> Questions? Thoughts? Additions? >> >> Best, >> Matthias >> > > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > I'm in! Regards, Martin -- Martin Mágr Senior Software Engineer Red Hat Czech

2 1

Steps for adding a new centos-release-* package to CentOS Extras
by Niels de Vos 19 May '16

19 May '16

Hi, Gluster 3.8 is planned to be released in a few weeks, and we're preparing for provinding the packages through the Storage SIG. For Gluster 3.6 amd 3.7 we already have centos-release-gluster36 and *-gluster37 packages in CentOS Extras. These packages only provide the .repo files so that users can easily install the packages from the SIG. The SIGGuide in the wiki [1] mentions the steps to do when adding a new package to the tags/buildroot of the SIG managed build environment. Could you add the process to request centos-release-* packages to get included in CentOS Extras? Thanks, Niels 1. https://wiki.centos.org/SIGGuide/Content/Build#Newpkgs

3 3

'vagrant up' not working after yum update
by Dharmit Shah 19 May '16

19 May '16

Hello all, I'm seeing this behaviour since I did `yum update` today on one of my CentOS 7 boxes in that, `vagrant up` for libvirt provider throws the error: "The provider 'libvirt' could not be found, but was requested to back the machine 'default'. Please use a provider that exists." Details of the issue can be found on [1]. I observed the issue when I was doing testing for Atomic Developer Bundle (ADB) [2]. Besides that, earlier, one needed to install only two packages - centos-release-scl and sclo-vagrant1 - to use Vagrant. But now it seems to have changed and we need to install sclo-vagrant1-vagrant-libvirt as well as few other packages/dependencies to make it work. I modified my Ansible playbook [3] which reflects the set of packages I had to add. What I'm here to understand is that, am I doing something obviously wrong here to make things work or, did I miss some notification on this list that had details about the changes? Or is this some kind of unexpected behaviour? Thanks! [1] https://github.com/projectatomic/adb-atomic-developer-bundle/issues/383#iss… [2] https://github.com/projectatomic/adb-atomic-developer-bundle [3] https://github.com/dharmit/adb-ci-ansible/commit/1da0cbc6961c8161981a15b9d2… Regards, Dharmit.

2 2

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