devel

devel@lists.centos.org

10 participants
4617 discussions

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

[NFV SIG][CBS]Understanding a bit more the NFV SIG builds and repos
by Joseph Gasparakis 03 Aug '15

03 Aug '15

Hi all, I finally put some time aside to move forward with building RPMs for DPDK 2.0 for the CentOS NFV SIG. In particular, I used pretty much the same spec file from Red Hat (made sure the RPM release matches what CBS expects for release) and I created package dpdk-2.0.0-1.el7.centos with buildID 1476. I am guessing I really should have built dpdk-2.0.0-8.el7.centos as I have kept all the changelog intact which goes up to number 8, and also keep it in sync with the Red Hat version? Any comments on that? Then my next question is that I noticed that following my successful build, kojira created task 16722 in order to create a new repo, which makes sense. According to that, since my RPM has tag nfv7-common-el7-build the dpdk rpm should apear on centos7-updates external repo, right? Following to this (and if I am right so far) shouldn't there be a specific repo for NFV SIG instead of centos7-updates which is a standard external repo? I have some more questions, but I will pause here if someone could shed some lights, that would be great. Thanks Joseph

2 3

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

03 Aug '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: - Status Updates: - General - Central Auth - Upcoming FAS and Tools Testing Cheers! Brian [0]: http://wiki.centos.org/HowTos/CommunityBuildSystem

1 0

Adding midonet-release to CentOS Extras (as a CATPR?)
by Sandro Mathys 30 Jul '15

30 Jul '15

Dear all, We, the MidoNet community [0], would like to include a midonet-release (or similarly named) package with the required yum repo files into CentOS Extras - similar to epel-release or centos-openstack-release packages in the same repo. For reference, our repos live at [1]. MidoNet is a network virtualization software and while our main focus is currently OpenStack, other use cases exist and will get more attention in future (mostly containers I guess) - which is why we would like to be included in CentOS Extras and not just in centos-openstack/rdo repos (if these accept release packages at all). I asked in #centos about this and was pointed here, so I hope someone can tell me what the process for this would look like and how to get started with it. I was told that IUS is undergoing the same process but couldn't find any information about this. I was also pointed to the "CATPR" guidelines [2] which I found to likely still being in draft status [3] but it should be no problem to fulfill the given requirements. We're only providing add-on packages and we have a bug tracker to report issues [4]. Cheers, Sandro Mathys MidoNet Community Manager [0] https://www.midonet.org/ [1] http://repo.midonet.org/ [2] https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 [3] http://wiki.centos.org/CarlGeorge/CATPR [4] https://midonet.atlassian.net/secure/Dashboard.jspa

5 8

Old issue with Minimal ISO
by leam hall 30 Jul '15

30 Jul '15

Sorry if I'm on the wrong list. I got bit by Bug 5589 ( https://bugs.centos.org/view.php?id=5589) It's a couple years old and looks to be a simple fix. Anything I can do to help? Leam -- Mind on a Mission <http://leamhall.blogspot.com/>

2 4

Re: [CentOS-devel] c7-ppc64 (big endian) progress
by youbest＠sina.com 29 Jul '15

29 Jul '15

http://mirror.lemote.com/CPOS/ This system is a CentOS 7 for Power 8 。 ----- Original Message ----- From: "Nuno Fernandes" <npf-mlists(a)eurotux.com> To: "The CentOS developers mailing list." <centos-devel(a)centos.org> Subject: Re: [CentOS-devel] c7-ppc64 (big endian) progress Date: 2015-07-22 04:48 Hello, I have a good knowledge of mock, building rpms and a Power8 box: [root@rhelbe ~]# lscpu Architecture: ppc64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Big Endian CPU(s): 16 On-line CPU(s) list: 0-15 Thread(s) per core: 4 Core(s) per socket: 1 Socket(s): 4 NUMA node(s): 2 Model: IBM,8284-22A L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): NUMA node3 CPU(s): 0-15 [root@rhelbe ~]# uname -a Linux rhelbe 3.10.0-229.el7.ppc64 #1 SMP Thu Jan 29 18:40:45 EST 2015 ppc64 ppc64 ppc64 GNU/Linux Is there any way i can help building CentOS 7 PPC64? Best regards, Nuno Fernandes -- Nuno Fernandes <npf(a)eurotux.com> Director de Investigação e Desenvolvimento Eurotux Informática, S.A. | www.eurotux.com (t) +351 253 680 300 (m) +351 919 475 933 _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

4 4

Update where we are with SCLo SIG
by Honza Horak 29 Jul '15

29 Jul '15

A small update for anybody who didn't follow the discussions last weeks around Software Collections in CentOS. Since we got quite a lot requests for devtoolset-3, we started with this collection. That one also requires the most problematic collections maven30 and rh-java-common, that are quite challenging to be rebuilt. Some packages that do not require java packages are already built in cbs.centos.org and available in this repo: http://cbs.centos.org/repos/sclo7-devtoolset-3-sclo-release/x86_64/os/ In order to accomplish the successful rebuilding of all packages we decided to import binary packages into cbs.centos.org as an external repo and rebuild the collections using those packages. Great news from today is it seems the imported packages work -- I was able to build the package devtoolset-3-apache-commons-el that during build needed a package not build in CBS yet (devtoolset-3-hamcrest, successfully used from the imported set). Completing my action items from last meeting: Task bug for creating tags for maven30 and rh-java-common collections: https://bugs.centos.org/view.php?id=9150 Task bug for creating components in dist-git for collections maven30, rh-java-common and devtoolset-3: https://bugs.centos.org/view.php?id=9151 The next step now is to rebuild those three collections using the external repo, while storing the sources into git.centos.org already. Branches for those packages will follow patterns described at http://wiki.centos.org/BrianStinson/GitBranchesandKojiTags, which means e.g. packages for devtoolset-3 will use branch sig-sclo7-devtoolset-3-sclo. Look-aside cache is still not ready, but Fedora's look-aside cache should be fine enough in most cases. Honza

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