devel

devel@lists.centos.org

8 participants
4623 discussions

[PAAS SIG] origin 1.2.1 is available in testing
by Troy Dawson 18 Jul '16

18 Jul '16

Hello, Origin v1.2.1 has been released, containing a security hot fix to the server components to prevent some users from escalating privileges via the API. I have created a 1.2.1 rpm for Centos. It is currently in centos-openshift-origin-testing. It has passed all of my tests but I'd feel more comfortable if others tested it as well. If you already have centos-release-openshift-origin installed, you can update and test this rpm via yum --enablerepo=centos-openshift-origin-testing update origin\* For those that want to download the source rpm, it is here. http://cbs.centos.org/kojifiles/packages/origin/1.2.1/1.el7/src/origin-1.2.… I plan to push this to release on Monday or Tuesday (July 18 or 19) so test as soon as possible. Thanks Troy Dawson

1 1

unsubscribe
by Regis Perdreau 16 Jul '16

16 Jul '16

2016-07-12 16:36 GMT+02:00 Haïkel <hguemar(a)fedoraproject.org>: > 2016-07-12 9:10 GMT+02:00 Fabian Arrotin <arrfab(a)centos.org>: >> I just had a look at CBS and was wondering how one SIG (so not >> ConfigMgmt SIG specific, but let's use that as an example) can interact >> with other SIGs. >> >> One example is Ansible : it seems some other SIGs are relying on it and >> so actually the ConfigMgmgt SIG isn't able to build it as it's already >> built with the same ENVR but in a different target/tag : >> https://cbs.centos.org/koji/packageinfo?packageID=1947 >> >> What would be the option for this ? >> Actually the direct option is for the ConfigMgmt SIG to just tag that >> build (for example for ansible-2.1.0.0-1.el7) so that it will appear in >> the correct repositories, but I'm wondering if such SIG wouldn't have to >> be considered "authoritative" and so having to discuss/bump/build new >> releases, and then other SIGs can just consume/tag a specific build/ENVR >> they want in their own repositories. >> >> -- >> Fabian Arrotin >> The CentOS Project | http://www.centos.org >> gpg key: 56BEC54E | twitter: @arrfab >> > > Concerning Cloud SIG, we're relying on two packages that are Cfg Mgmt > SIG-related: > * Puppet: puppet is quite critical for us, as it's the heart of our > installers (packstack, TripleO), > critical component for our CI and also upstream CI. > We also had to patch Puppet3 default for buggy Puppet behaviours (like > not supporting provides), I co-maintain the Fedora package with the > help of Red Hat puppet experts. > Our puppet package is mere rebuild of Fedora Rawhide (with a decent > amount of CI/testing before being shipped) > * Ansible: It's more and more used in our infrastructure, WeiRDO our > CI swiss-knife relies on it. We're currently not shipping it but we'll > likely have too. > > I don't mind handing puppet packaging to Cfg Mgmt as authoritative > source, nor Ansible, I think we can manage to work together. > What worries me is that CfgMgmt SIG used to think about relying on > Software Collections, that we're not ready to use in the Cloud SIG. > > Regards, > H. > >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel >> > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel

1 0

Question about authoritative SIG for specific pkg[s] (wrt ConfigMgmt SIG)
by Fabian Arrotin 15 Jul '16

15 Jul '16

I just had a look at CBS and was wondering how one SIG (so not ConfigMgmt SIG specific, but let's use that as an example) can interact with other SIGs. One example is Ansible : it seems some other SIGs are relying on it and so actually the ConfigMgmgt SIG isn't able to build it as it's already built with the same ENVR but in a different target/tag : https://cbs.centos.org/koji/packageinfo?packageID=1947 What would be the option for this ? Actually the direct option is for the ConfigMgmt SIG to just tag that build (for example for ansible-2.1.0.0-1.el7) so that it will appear in the correct repositories, but I'm wondering if such SIG wouldn't have to be considered "authoritative" and so having to discuss/bump/build new releases, and then other SIGs can just consume/tag a specific build/ENVR they want in their own repositories. -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

4 5

Re: [CentOS-devel] ConfigMgmt SIG Status
by Ben Hosmer 15 Jul '16

15 Jul '16

I'm having a hard time getting my bearings. Where can I help out?

4 3

Update on the CentOS Community Container Pipeline
by Karanbir Singh 14 Jul '16

14 Jul '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The last week and a half, the dev team split up and took on specific focus areas. The aim being to spend a few days and quantify the technical debt and also validate the features we had already delivered ( or had hoped to have delivered ). This allowed us to run a sort of retrospective sprint. The result of which was checklists that allow us to measure a state of completeness in the following areas : - - Post-build and regular image scanning + reporting - - Ability for a contributor to onramp rapidly - - Production band-aid's / flaky code that needed immediate attention - - Ensuring we've completed the initial set of user stories we'd set out to deliver on. Over the next 2 weeks, our aim is going to be to try and close down as much of this debt as we can, before moving back to focusing on Feature development. We've also started handing off SRE roles and developing a deployment pipeline to move towards a CD model in the coming weeks. As we move towards production with the SRE / Dev splits, there will be some code work that we need to work on, and we will try to track that via a priority task list, labelled as 'bugs/issues'. In order to better organise the tasks, we've created 5 labels as follows : - - Contributor Process / Developer enablement - - Service Feature - - User - - Scanner + Testing - - Production Critical We've also agreed, and reminded ourselves, to not work on things that are not on cards and in the current sprint. And we've agreed to run daily standups at 10:00 UTC daily. - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXh7EvAAoJEI3Oi2Mx7xbtXIwH/2Mb2P3GFJXaTkI1BEgoqLe1 LIFqp0G1kJYx+7FNlxjLgo1YXoWVw0gMtEgSz9dDyx4ON/MDhSHKWLILzGMwqqoK kCmkSiL5eSpVedQrh3CFf6/OqfDi4NXTIz0a2VB8SvFxlBpNEl4UZr5eX9+U8HI2 jxCZtNjB0TOaL0m4k9rxtrs75QCr1t5aiFbcDbhyV7WDfAU3xlmGfaOBojofrLHD J43a4VZ9/TyK0gmuH7/bZ9qZq4j7dDHC3AZwBaUtY0pRzrtRwpm3gDmpuKxaas8M sbVbwYLPauWtbVOsqHvE3hCDbPd6tUR+pTELW+f28V2gR5Sbe/bOQ9gTfh8/0l8= =alEJ -----END PGP SIGNATURE-----

1 0

Incorrect default governor on CentOS ppc64el builds
by Adi Gangidi 14 Jul '16

14 Jul '16

Hello nice people on CentOS list, ?Default governor on CentOS 7 ppc64le OS bootup is "conservative" . This has about 20% effect on benchmark numbers, if you don't change the governor to ondemand manually (for specific benchmarks). I tested this on our barreleye power 8 server. This even though kernel config is set for "ondemand" as default governor: [root@Barreleye-1 ~]# cat /boot/config-3.10.0-327.el7.ppc64le | grep -i ondemand CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y I filed a bug on this with details and am posting here for info and also to accelerate some response on the bug: https://bugs.centos.org/view.php?id=11094 Best Adi Gangidi Rackspace

1 0

CentOS PaaS SIG meeting (2016-07-13)
by Troy Dawson 13 Jul '16

13 Jul '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 13 July 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated testing --- linch-pin -- Documentation -- images / image building - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2016/july/centos-devel.2016-07-06-16.59.log.…

3 2

network issues to cbs / ci and related services
by Karanbir Singh 13 Jul '16

13 Jul '16

hi guys, As of 3:00 am UTC today 13th July 2016, we've been having networking issues into the facility that hosts : - cbs.centos.org - ci.centos.org and their related services. We've been told that the facilities folks are working on it, but have no ETA. The main symptom is high packet loss. Till this gets rectified, we are going to see timeout's on some of the services and resources hosted from there. If you have any specific concerns, you can find us on #centos-devel on irc.freenode.net Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Re: [CentOS-devel] ConfigMGMT SIG Status
by Ben Hosmer 12 Jul '16

12 Jul '16

Thanks for the bump on this. I'll be happy to represent SALT and submit the bug, however I'm slightly confused on the tagging convention. Would something like configmanagement7-salt-2016.3 be an acceptable tag? I've confirmed my access to CBS: [bhosmer@xur ~]$ cbs moshimoshi zdravstvuite, bhosmer! You are using the hub at https://cbs.centos.org/kojihub/ Authenticated via client certificate /home/bhosmer/.centos.cert

1 0

Interest in a SIG for logging and monitoring?
by Steve Huston 12 Jul '16

12 Jul '16

Apologies for not being able to use a proper reply, since I only just joined the list today; came here to say that I too would be interested in such a SIG. -- Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci Princeton University | ICBM Address: 40.346344 -74.652242 345 Lewis Library |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (267) 793-0852 | headlong into mystery." -Rush, 'Cygnus X-1'

6 6

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