devel August 2015

devel@lists.centos.org

28 participants
22 discussions

EL6 SCL packages
by Leon Fauster 18 Aug '15

18 Aug '15

This place may be more appropriate then centos-list. My subscription is new therefore sorry, if already asked: How is the centos policy for EL6 SCL packages? I see some activities about a sclo7 branch but how is the status for rhscl especially el6's ones? Thanks, LF

3 4

Central Auth: Group naming and Process Proposal
by Brian Stinson 18 Aug '15

18 Aug '15

Hi All, We're working on testing instances of FAS for storing our user/group membership information used by the CBS. I'd like to talk about group naming and the permissions model to get some input. The goal is to get these discussions going so we can set up our test environment to mirror what we'll roll out in production. Consider this a proposal, and please send comments my way (on-list please!). Groups will use the convention 'sig-<shortname>', for example: people in the Cloud SIG will be members of the FAS group 'sig-cloud'. This convention will allow push access in dist-git to any branch that starts with sig-cloud (sig-cloud7, sig-cloud7-openstack, sig-cloud7-openstack-juno) and grant build permissions under the SIG tags in Koji[0]. FAS has 3 types of membership in a group: Admin, Sponsor, and User. All 3 levels will be granted commit/build permissions, while only Admins and Sponsors can modify members of the group. To match our permissions model[1], I propose: - We populate the 'Accounts' (Global Admin) group with the members of the CentOS Board. - The Board member responsible for each SIG will create the appropriate SIG group in FAS - The Board member will add him/herself as an admin of the group - The Board member will sponsor the SIG Chair as a sponsor for the group - From then on, the SIG Chair and Board member can sponsor others into the group as users (and optionally add more sponsors to the group) Anyone have thoughts? Once we reach consensus, I'll get this written up for the SIG wiki page. Cheers! Brian [0]: http://wiki.centos.org/BrianStinson/GitBranchesandKojiTags [1]: http://wiki.centos.org/SpecialInterestGroup

5 4

CBS/Infra Meeting 17-Aug-2015 14:00 UTC
by Brian Stinson 17 Aug '15

17 Aug '15

Hi All, We'll be having another meeting to talk about the Commmunity Build System. Join us in #centos-devel on Freenode. Proposed Agenda: - Status Updates - General - Central Auth - Adding remote builders Cheers! Brian

1 0

integrating cbs.centos.org repos with ci jobs at ci.centos.org
by Karanbir Singh 14 Aug '15

14 Aug '15

hi guys, Can we get some notes on the wiki ( maybe in the GettingStarted guide for the CI users ), on how they can track the cbs repos for new content and trigger builds from there. I know we do this already for the cloud-sig, openstack packstack validation run, but its a feature that we can use in quite a few places. Regards, -- 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

2 1

[Introduction] Social Media Policies for CentOS
by Brian Proffitt 13 Aug '15

13 Aug '15

Hello to all: My name is Brian Proffitt, a social media and community analyst with Red Hat. The main focus of my work is to assist free and open source software projects with which Red Hat is involved to improve their social media planning and execution. CentOS has a broad and diverse social media implementation, which I believe could be improved using a coordinated set of guidelines regarding content discovery and delivery, as well as engagement with the different audiences found in various social media channels. To that end, I would like to begin a conversation here with interested members of the CentOS community and its Moderators Group to see what resources are needed, what improvements could be made, and how CentOS' social media could become an even more powerful tool within and without the CentOS community. The information attached is a first-step proposal to get such a conversation started. I look forward to the discussion! Peace, Brian Proffitt -- Principal Community Analyst Open Source and Standards bkp(a)redhat.com +1.574.383.9BKP

5 6

Adding geo distributed builder hardware for cbs.centos.org
by Karanbir Singh 11 Aug '15

11 Aug '15

hi, What are the main concerns for hosting some builder hardware geo-distributed from the main koji hub ? Apart from the latency thing, but given that most builders spend all their time in mock root builds and then the rpmbuild, if we can get gbit links to the remote machines, we should be ok right ? regards, -- 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

7 11

CentOS SCLo SIG sync-up meeting on #centos-devel (2015-08-05)
by Honza Horak 05 Aug '15

05 Aug '15

SCLo SIG meeting will be at 15:00 UTC (11:00 EST, 17:00 Brno, 11:00 Boston, 0:00+1d Tokyo, 1:00+1d Brisbane) in #centos-devel on Freenode. = Topics = * dist-git repos -- do we want to create all at once? * vagrant SCL as example of sclo upstream collection (sorry for late announcement) Honza

1 1

Build scripts for CentOS 7 AMIs
by Brian Lalor 04 Aug '15

04 Aug '15

I’ve been unable to find the build scripts used to create the CentOS 7 AMIs. I have found them for docker, vagrant, and I believe openstack. Can those please be published? — Brian Lalor blalor(a)bravo5.org

3 6

Working Documentation Toolchain [GSoC]
by kunaal jain 04 Aug '15

04 Aug '15

Hi, The basic toolchain is up and running. I encourage community to test this workflow once. It is an addition to the existing contributing mediums. Site: http://clown-olga-13325.bitballoon.com/ Contributing Docs repo : https://github.com/kunaaljain/test-centos-docs ==AIM== Initial Idea : http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain The CentOS Project needs more short-form contributions of content that focuses on how-to do things on top of a CentOS Linux installation, with a method to push changes in to appropriate and related upstream open source projects. There is a lot of content scattered across the Internet on how to do things with CentOS Linux. The goal of this toolchain is to make it easy for people to contribute new, short-form content articles to the Project with an ability to push them outward to relevant upstream projects. ==Workflow== 1. The user authors content in markdown format and creates a pull request on Github. 2. The backend service mirrors the pull request to pagure and creates a issue. 3. The doc is built and a link is provided to preview the doc. 5. Staff reviews the docs, gives comments either on pagure or github (two way synced) 4. Once the staff approves the doc is built and doc site updated. ==Infra== 1. A backend server listing to Github and Pagure webhooks and mirroring content. 2. A http site displaying the temporary docs. 3. A pagure instance ==Testing == 1. Fork the https://github.com/kunaaljain/test-centos-docs 2. Add new content to docs folder in mardown language. 3. Update the mkdocs.yml file and add the new file you just created with appropriate heading. 4. Create a pull request. 5. Within 15-20 seconds, a comment will be made on pull request, with the pagure link, which displaying various metadata. 6. Once the staff approves, PR is merged and site updated at http://clown-olga-13325.bitballoon.com/ -- Regards, Kunaal Jain

1 0

Testing CentOS as a hypervisor in different scenarios
by Karanbir Singh 04 Aug '15

04 Aug '15

Hi, this has come up in a few conversations, and its worth looking into. Various efforts including the CentOS Cloud Instance SIG, would like to test their VM instances under a CentOS 6/7 hypervisor setup. I am sure the Virt SIG guys would like to also have these VM instances tested on hypervisors and environments they curate. Whats the best way to move forward on this ? I am going to propose asking the various efforts ( eg. cloud sig, virt sig ) to help setup the environments like openstack, centos-kvm, centos-xen, ovirt etc; and provide a single mechanism that can be used via jenkins at ci.centos.org to grab, test, report on machine instance states. The cycle would need to run via triggers at ci.centos.org, and it would ideally be run for the entire set of environments we can bring up. thoughts ? -- 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

4 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2015