devel

devel@lists.centos.org

5 participants
4641 discussions

[infra] : Hardware migration status
by Fabian Arrotin 11 Oct '16

11 Oct '16

As announced some time ago ( https://lists.centos.org/pipermail/centos-announce/2016-September/022065.ht… ) , there was a big hardware migration/DC relocation happening yesterday that impacted several of our public services. Here is a small report of that migration, that finally took less time that previously announced. * 2016-10-10 - 3pm UTC : we started to preconfigure all changes, and powered down all the services in correct order * 2016-10-10 - 3pm UTC * 2016-10-10 - 3pm UTC * 2016-10-10 - 3pm UTC * 2016-10-10 - 3pm UTC -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

password ssh-ing in Centos/7 Vagrant box
by Rafal Skolasinski 10 Oct '16

10 Oct '16

Hi, Vagrant Image version 1607.01 introduced a nice fix for a security issue with default password for a Vagrant user. I understand that this is important, however I wanted to ask if it is possible to switch it off? I couldn't figure out a way it was introduced. I was using first ansible login via password to configure my vms and then switching that option off by myself anyway. Cheers, Rafal

4 10

A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages
by Ponomarenko Andrey 08 Oct '16

08 Oct '16

Hello, I'd like to present a new free tool for maintainers of software libraries — Package ABI Diff Tool (pkg-abidiff). It's a tool for backward compatibility analysis of API/ABI interfaces in RPM packages. The tool is based on ABI Compliance Checker and ABI Dumper tools. The tool does the following: 1. Extracts input packages 2. Searches for *.debug, *.so and header files 3. Creates ABI dumps of all found shared objects 4. Filters out private part of the ABI using info from header files 5. Matches shared objects in old and new packages 6. Compares ABI dumps of corresponding objects 7. Creates backward binary compatibility (BC) report 8. Creates backward source compatibility (SC) report The tool is intended for Linux maintainers who are interested in ensuring backward compatibility, i.e. allow old applications to run (BC) or to be recompiled (SC) with newer versions of RPM packages. Home page: https://github.com/lvc/pkg-abidiff Usage: pkg-abidiff -old P1 P1-DEBUG P1-DEV -new P2 P2-DEBUG P2-DEV P1 — RPM package to analyze (with *.so object files) P1-DEBUG — corresponding debug-info package (*.debug files with DWARF info) P1-DEV — corresponding development package (with header files) Report example for libssh 0.6.4 vs 0.7.1: https://abi-laboratory.pro/examples/compat_report/x86_64/libssh/0.6.4-4.el7… Enjoy!

2 1

[Infra] - CentOS Bug tracker migration / maintenance window
by Fabian Arrotin 08 Oct '16

08 Oct '16

We have to upgrade our current MantisBT instance for the CentOS bug tracker service (aka https://bugs.centos.org) Migration is scheduled for """"Friday october 7th, 12:15 pm UTC time"""". You can convert to local time with $(date -d '2016-10-7 12:15 UTC'') The expected "downtime" is estimated to ~15 minutes , time needed to update MantisBT code, run the mysql schema update, and then put the node back in production mode. Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

Openshift Origin Containers for v1.2.1 and v1.3 on container pipeline.
by Mohammed Ahmed 07 Oct '16

07 Oct '16

Hi, We currently have openshift origin containers being delivered through the Container Pipeline. However, with the release of openshift origin 1.3, we have to consider how we are going to deliver containers for v1.2.1 and v1.3. Currently, the dockerfiles basically do a yum install origin[1] and other origin packages. This could possibly result in the latest origin rpms being used even in 1.2.1 containers. We need to consider how we are going to differentiate the versions. Even if there aren't any updates to 1.2 containers on toe repos, its still possible the containers might get rebuilt from other triggers, such as base image rebuilds and so on. KB, Troy Dawson, thoughts? Others are welcome to chime in as well. [1] https://github.com/openshift/origin/blob/release-1.2/images/origin/Dockerfi… -- *Mohammed Zeeshan Ahmed* Associate Software Engineer, Redhat Developers Team (Devtools) http://mohammedzee1000.wordpress.com RED HAT | DIFFERENT FOR THE SAKE OF BETTER TECHNOLOGY Find out why every airline, telecom, commercial bank, healthcare, and financial data services company in the Fortune 500 relies on Red Hat. Trusted | Red Hat <https://www.redhat.com/en/about/trusted>

4 6

Backporting Hyper-V support to Koji 1.10.1
by Laurentiu Pancescu 06 Oct '16

06 Oct '16

We already upgraded Image Factory some time ago, to be able to generate images for Hyper-V. Unfortunately, we were hold back by the lack of a newer stable release of Koji, which passes the right parameters to Image Factory. I tried to backport Ian's changes to Koji 1.10.1 (which I assume we're using). I had to manually fix a few merge conflicts - could someone take a look at the attached patches? I have no possibility of testing them here. Thanks, Laurențiu

1 0

Ideas for customizing the embedded Vagrantfile?
by Laurentiu Pancescu 06 Oct '16

06 Oct '16

Hello all, Vagrant boxes include a Vagrantfile, where we can preset some configuration values, as required by our images. Right now, the Vagrantfile for each provider is hard-coded inside the Image Factory code, but, during a conversation in #centos-devel, Ian was inclined to accept patches, and eventually discuss possible approaches with whoever is interested. Do you have any specific ideas or wishes for customizing the Vagrantfiles? At a minimum, the MAC address needs to be set in the embedded Vagrantfile. Perhaps each image builder could provide its own template as a parameter, just we like pass the kickstart files to Koji. I think it's already possible to interpret variables inside kickstart files (we used that for setting the root password in the past, before hardcoding it to 'vagrant'); if not, I think Zope includes a template system. We'll need to implement this both in Image Factory and Koji (for CBS). I would be especially interested in getting this done; with just one hardcoded Vagrantfile for everyone using Image Factory, there's always the danger that a change in Image Factory to accommodate one project might adversely impact other projects. [1] Best regards, Laurențiu [1] https://github.com/redhat-imaging/imagefactory/issues/366

1 0

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

05 Oct '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 05 October 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - Origin LTS ?? - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2016/september/centos-devel.2016-09-28-17.00…

1 0

[Cloud SIG]: RDO Newton GA Test Day - October 13, 14
by Rich Bowen 05 Oct '16

05 Oct '16

FYI, we'll be testing the OpenStack Newton GA packages next week. Please join us. -------- Forwarded Message -------- Subject: RDO Newton GA Test Day - October 13, 14 Date: Wed, 5 Oct 2016 10:05:12 -0400 From: Rich Bowen <rbowen(a)redhat.com> To: rdo-list(a)redhat.com <rdo-list(a)redhat.com> Please join us for the final test day of the Newton cycle. Full details of the test day are at https://www.rdoproject.org/testday/newton/final/ We will be testing on October 13th and 14th. Come to #rdo on the Freenode IRC network for help and discussion. Based on discussion on the list, I've moved the test scenarios document entirely to an etherpad, to make it easier to add test scenarios, as well as easier for people to add their test day notes. Please have a look at the test scenario etherpad prior to test day, and ensure that desired scenarios are listed, and that instructions are there for testers to follow - https://etherpad.openstack.org/p/rdo-newton-ga-testday-testplan -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

1 0

[opstools] proposal to skip this weeks meeting
by Matthias Runge 03 Oct '16

03 Oct '16

Hello, I'm traveling this week and won't be near any internet during meeting time. Let's skip it this week. If you have anything opstools related, please send it to the list. Thanks, Matthias

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