devel

devel@lists.centos.org

3 participants
4591 discussions

Config Management Sig at Interlock
by Julien Pivotto 27 Oct '16

27 Oct '16

Hi everyone I will join the CentOS Interlock. At that moment we can discuss about the SIG. It looks like we have enough traction in the community to get started with Ansible. I will start working on that in the coming days, with people who have showed interest. Let's also meet & talk during the Interlock! Thanks. -- (o- Julien Pivotto //\ Config Management SIG V_/_ https://frama.link/cfgmgmt

6 7

Tagging origin and openshift-ansible into released
by Troy Dawson 27 Oct '16

27 Oct '16

Hi, I've ran origin and openshift-origin through all the tests I have. They are both passing everything without any problems. I have given them the -release tag, which means they should be going onto the mirrors tomorrow some time. Packages tagged into release: (Sub-Packages are automatically tagged in) origin-1.3.1-1.el7 openshift-ansible-3.3.39-1.git.1.ebc2639.el7 ansible-2.2.0-0.50.prerelease.el7 Troy

2 1

Using pungi for CentOS (AH specifically)
by Colin Walters 27 Oct '16

27 Oct '16

Hey, so upstream Fedora has been working on this: https://pagure.io/pungi And I'd like to discuss trying to use it for Atomic Host work. The concept of a "compose" that ties together the ISO and cloud images is nice for example. It's going to need to gain some more sophistication around OSTree, and there'd likely be some details that need changing such as how signing happens. But having a common codebase here would be nice, and I think we could also stop doing this in Jenkins for https://wiki.centos.org/SpecialInterestGroup/Atomic/Devel too. (We'd retain the auto-generated RPMs at least though)

2 2

[Cloud SIG] Aarch64 bootstrap status
by Haïkel 27 Oct '16

27 Oct '16

Hi, Many thanks to Thomas who spent his evening merging aarch64 builds (and Fabian for enabling the arch in our CBS tags!) Here's a summary of the bootstrap: https://review.rdoproject.org/etherpad/p/aarch64-bootstrap-current-status Erlang and texlive are still building, but the biggest remaining chunk will be building v8 on aarch64 (and node.js) but overall we're good. Next steps will be fixing broken builds and proper testing on real hardware. Regards, H.

4 5

No CentOS SCLo SIG sync-up meeting next week
by Honza Horak 27 Oct '16

27 Oct '16

I'm not able to make it for the next week's SCLo SIG meeting (was supposed to be 1st Nov). If anybody is willing to hold the meeting, feel free to do it, otherwise let's just cancel it. Honza

1 0

CentOS PaaS SIG meeting (2016-10-26)
by Troy Dawson 26 Oct '16

26 Oct '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 26 October 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms --- origin and openshift-ansible released -- Documentation -- Automated testing -- images / image building - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2016/october/centos-devel.2016-10-19-16.59.l…

1 0

[FOSDEM] [CFP] FOSDEM 2017 - Distributions Devroom
by Brian Stinson 25 Oct '16

25 Oct '16

FOSDEM 2017 - Distributions Devroom Call for Participation The Distributions devroom will take place 4 February, 2017 at FOSDEM, in room K.4.601 at Université Libre de Bruxelles, in Brussels, Belgium. Distributions are more than just hosted collections of software from various upstreams. Each distribution is responsible for problem-solving in building, testing, and releasing software as well as managing the lifecycle of each application in the collection. Additionally, distributions do very important work in ensuring that various versions of upstream software work well together and can co-exist. Distribution are also, often responsible, for "de-vendoring" upstream software so that security fixes can be applied more quickly. We welcome submissions targeted at contributors interested in issues unique to distributions, especially in the following topics: - Managing Build/Test/Release processes around shared ideas and resources - Lifecycle management, especially in the areas of sandboxing, containerization, vendoring, and bundling - Distribution construction tools and infrastructure development and implementation (building, signing, testing, distribution, etc.) - Cross-distribution collaboration on common issues, eg: content distribution, infrastructure, and documentation - Working with vendors and including them in the community - Building trust and code relationships with the upstream components of a distribution and between distributions - The future of distributions, emerging trends and evolving user demands from the idea of a platform - The place of distributions in today's world (including concepts of containerization, IoT, etc.) - Onboarding new users and mentorship, facilitating technical growth within the contributor base - Solving traditional problems like package management, and content management (eg. rpm/dpkg/ostree/coreos ) - Integration technologies like installers, deployment facilitation ( eg. cloud contextualisation ) - Principals of Rolling Releases, Long Term Supported Releases (LTS), Feature gated releases, and calendar releases Ideal submissions are actionable and opinionated. Submissions may be in the form of 25 or 50 minute talks, panel sessions, round-table discussions, or Birds of a Feather (BoF) sessions. Dates ------ Submission Deadline: 25-Nov-2016 Acceptance Notification: 5-Dec-2016 Final Schedule Posted: 11-Dec-2016 How to submit -------------- Visit https://penta.fosdem.org/submission/FOSDEM17 1.) If you do not have an account, create one here 2.) Click 'Create Event' 3.) Enter your presentation details 4.) Be sure to select the Distributions Devroom track! 5.) Submit What to include --------------- - The title of your submission - A 1-paragraph Abstract - A longer description including the benefit of your talk to your target audience, including a definition of your target audience. - Approximate length / type of submission (talk, BoF, ...) - Links to related websites/blogs/talk material (if any) Administrative Notes ---------------- We will be live-streaming and recording the Distributions Devroom. Presenting at FOSDEM implies permission to record your session and distribute the recording afterwards. All videos will be made available under the standard FOSDEM content license (CC-BY). If you have any questions, feel free to contact the devroom organizers: distributions-devroom(a)lists.fosdem.org (https://lists.fosdem.org/listinfo/distributions-devroom) Cheers! Brian Exelbierd (twitter: @bexelbie) and Brian Stinson (twitter: @bstinsonmhk) for and on behalf of The Distributions Devroom Program Committee

1 0

Storage SIG introduction: Ken Dreyer
by Ken Dreyer 25 Oct '16

25 Oct '16

Hi folks, My name is Ken Dreyer, and I work on the Ceph Engineering team @ RH. We're working on a new GUI for Ceph and Gluster management, https://github.com/Tendrl There are a couple of groups across the Ceph and Gluster communities that are working on Tendrl and its dependencies, so the CentOS Storage SIG community would be an ideal place to make all the pieces fit together. I'd like to help with packaging the Ceph-related dependencies in the CentOS Storage SIG, and getting them built in CBS, etc. I've set up my account at https://accounts.centos.org/user/view/ktdreyer and requested the storage sig group there. See you on IRC in #centos-devel ! - Ken

2 2

centos-packager 0.5.4 Released
by Brian Stinson 24 Oct '16

24 Oct '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Packagers! We have pushed an update to centos-packager containing 3 bugfixes and added COPR builds for Fedora 25. See https://wiki.centos.org/HowTos/CentosPackager for instructions about how to install it on your workstation. Highlights: - - Updated the path to the serverca bundle in the koji config (https://bugs.centos.org/view.php?id=12110) - - Use more restrictive permissions when downloading to ~/.centos.cert for multi-user workstations. (https://bugs.centos.org/view.php?id=12011) - - Update some references to accounts.centos.org in the help text of the centos-cert tool Please update and give it a try! Cheers, - -- Brian Stinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJYCSGbAAoJEIMGvNKzCweMB8wQAJj5R4dlEqqsemgAziYN2PHg abBiyoAlF85vPOseMNEYeF6m+TztVezSku9XnkIDk0AH6aSKfPE4ri68l7LEU3Lz 9ywOXt3MtFXmZ5KRCvBjeZ+Zonu6pYzEuXRGkZY+bpjhM42bJOu13zLM9oGzHyGb xrG6jaRKRKvO4l85OrHBfL/G/dDqOi/E8iP7h5rmP1hlpqwYUAjPGUCetMKVr77z gGec36wt61YKbV+DuQ2tY3lDX2yHaGMqBRrskh0/SwI0EWqcrZH30jZxfn3XCoX3 X1OTqCtVAH+mx6BKrdkETlSr57i8+aRrscB3jFRwGq1ywnoGJFv99qaL3bDDbxSb CLVFrOn8xVnqVfbrVpKiPLfArn1iuasr/ZDHLTUmY6qXoEbbxU7Y0e1TL0iT8DD+ 7f6G7vhTz7XUag06yq0zcfi6fKTloJk96+IbTQXFWoD8HwXATv6a8qnI/PJ3wtHs sNc2fn5MbhKp6U8/h2MWU/yrC5KIq2lBBQw88mdppiY56mMiAsm4psurQ7BJqYwo U8TabreLYkJeZiM2t1vCZEhQ05mT8xpVfQWj/42QjmeI0CtQmg7LDVXHeHLNq+Ca wSS9Qul/uyQBrZC0IumGcdvpRqJ1XEogQPRyURijKfV3mwS7cDOe3TfmPzSrGwet vxFq9RDDbAYBA9Vx+0PK =tN+6 -----END PGP SIGNATURE-----

2 1

[RFC] Bootstrapping a new arch
by Haïkel 21 Oct '16

21 Oct '16

Hi, There was various discussions about enabling aarch64 architecture for Cloud SIG OpenStack repositories. And likely others are coming, so I'd like to confirm with a wider audience about the proper course of action. So we can document it and share that experience with other SIGs. Arrfab suggested the following: * scratch builds with archoverride of existing arch-dependent builds * ask CBS admin to merge the task with existing builds using mergeScratch. I find this process simple and efficient, but I'm worried about how it scales. In my case, I have about 250 binary packages (including the Erlang stack etc.) with many interdependencies, so it can rapidly get bothersome for CBS admins. If we can find a way to automate the mergeScratch operations or temporarily grant that permission to SIGs during bootstrapping phase, I have pretty much no objections for that course. --- As for daily operations, if you can't block on alternate arch build failures, I was recommended to just use %excludearch and move forward. Which gives us the flexibility to move forward and give more time to fix things at our pace. So what do you think? Any other suggestions? Regards, H.

6 5

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