devel

devel@lists.centos.org

10 participants
4617 discussions

Security and other updates - too slow
by Phil Wyett 18 Dec '16

18 Dec '16

Hi, How is the core SIG looking at improving and speeding up (more than one person) builds of updates? As I see it the longer the time between vendor release and CentOS release people know that we are hittable if they have a viable exploit? I ask this as I see that the core SIG is not concentrating on the job at hand and concentrating on the work of their new masters - Red Hats CentOS? Their heads are in the cloud. ;-) Regards Phil -- Google+: https://plus.google.com/+PhilWyett Blog: https://philwyett-hemi.blogspot.co.uk/ GitLab: https://gitlab.com/philwyett_hemi/

7 13

missing rpms in extras
by Jacco Ligthart 16 Dec '16

16 Dec '16

Hi All, I think there are some rpms missing in the 7.3 extras repository. This is not a complete list, but just the items I missed. from the items needed for building 7.3: [DIR] nss_wrapper/ 2016-11-16 12:38 - [DIR] cmocka/ 2016-11-16 12:22 - [DIR] python-hypothesis/ 2016-11-15 13:24 - [DIR] python-cryptography-vectors/ 2016-11-15 13:23 - And some older items: [DIR] python-pretend/ 2015-11-20 01:07 - [DIR] python-iso8601/ 2015-11-20 00:57 - (items are cut-n-paste from buildlogs.centos.org) As far as I can see they are missing both in the normal mirrors as in the vault. Jacco

2 2

Centos on P8 824L OPAL
by Charlie Berry 16 Dec '16

16 Dec '16

Hi team: Want to run 7.2 on an IBM 824L bare metal on OPAL firmware. Seems like this should be OK. Any gotchas? Also, will want to run Nvidia CUDA 8 for packages for RHEL. I have a vote that this should be OK. Any other gotchas? Thanks for the sanity check. Charlie Berry Systems Architect - POWER Systems Technical Sales IBM Systems Hardware, North America, Public Sector Los Angeles, CA US 310-686-8173 cell crberry(a)us.ibm.com

4 3

Core SIG documentation - The community project
by Phil Wyett 16 Dec '16

16 Dec '16

Hi, I look around and see very little documentation of what the core SIG and other SIGs for that matter as to what they are doing and how they wish to help and bring people into the dev process. Note: I emailed the list about the paris meeting days and Karanbir said info would come out. None has come out, so when? The CentOS wiki is outdated and only allowed to be edited if you get access to do so if you carry good grace. It is time we start changing and as the project/community speeds up and diversifies with what they use CentOS for, is the leadership to move with that and maybe add more people, document those people as in what they do so we know points of contact and how people can contribute. At the moment if you look at list traffic, we seem to cover the same issues and if you use IRC, the Core SIG is all about Cloud. Can we have a public discussion about CentOS structure, Core, Other SIGs - What are the goals of CentOS? Regards Phil -- Google+: https://plus.google.com/+PhilWyett Blog: https://philwyett-hemi.blogspot.co.uk/ GitLab: https://gitlab.com/philwyett_hemi/

2 3

Update on status of CentOS Community Container Pipeline
by Bamacharan Kundu 15 Dec '16

15 Dec '16

Hi, Here is an update on the recent works done in CentOS Community Container Pipeline * We got weekly scan in place for images in registry.cenots.org * Vert.X stack for eclipse che is now setup. * registry.centos.org is now running in NFS to handle large number of images. * Rabbitmq is now available from registry.centos.org * keycloak-postgres is setup to run in openshift * Bayesian dependencies are now available from registry.centos.org * Jenkins is now polling the proper branch of git repo to track the changes and rebuild images. Our current focus of work are: * Setting up openshift node cluster for scaling up build speed * Putting checks in pipeline to avoid cyclic dependency * We are also focusing to solve the issues with build worker to continuously building the images. Regards Bamacharan Kundu

1 0

[opstools] skipping meetings on Dec 21 and Dec 28
by Matthias Runge 14 Dec '16

14 Dec '16

Hello, the subject says it all: we're going to skip those meetings. See you in 2017, Best, Matthias

1 0

Fwd: Vagrant boxes (7.2.1511)
by Carlos Rodrigues 14 Dec '16

14 Dec '16

Hi, Now that CentOS 7.3 has been released, vagrant boxes have become broken when the vagrant-vbguest plugin is used to build guest additions at creation time due to the "kernel-devel" package matching the running kernel not being available in the default repos anymore (since the base repo is not cumulative with older point releases). Of course, once there's an official CentOS 7.3 base box available, the problem should fix itself, but a somewhat important usecase remains broken and it's why I'm posting this: Using vagrant is especially useful when you want reproducible environments, and this includes pinning the base box to a particular version. As it stands, new CentOS point releases permanently break this usecase and I believe it would be important to have a solution for this. Best regards, -- Carlos Rodrigues

5 7

Cloud SIG: lessons learn in transition to 7.3
by Alfredo Moralejo Alonso 14 Dec '16

14 Dec '16

Hi, During the transition to CentOS 7.3, we have been hitting some issues in Cloud SIG and have collected them in https://review.rdoproject.org/etherpad/p/release-centos-7.3 so that we can learn for next releases. As some of the issues are generic and related to the CentOS release process, please feel free to comment on the etherpad or #centos-devel any feedback or questions that you may have about it. Best regards, Alfredop

1 0

keeping Extras in sync with Core
by Colin Walters 14 Dec '16

14 Dec '16

So right now following the instructions on: https://wiki.centos.org/Cloud/Docker results in a non-working Docker because the version in Extras hasn't been rebuilt yet, and there's a strong dependency on selinux policy. I'm still trying to wade through the pile of virt7* repos to find something working, right now hitting a requirement on `skopeo-containers`. In the future, can we ensure that there's a "CR" version of Extras[1] that is built at the same time, and they're all released at once? We also need to figure out how CR interacts with the CBS content better. [1] And ideally other things like the atomic host content, but let's start with Extras

1 0

Atomic SIG: discussion about kubernetes-node in downstream image
by Jason Brooks 13 Dec '16

13 Dec '16

With the goal of slimming down the size of our atomic host image and of allowing users the flexibility to choose different component versions, we removed kubernetes and few other packages from the continuous/alpha version of centos atomic host back in august[1]. [1] https://github.com/CentOS/sig-atomic-buildscripts/commit/3ce19d58a5f1d9b5d5… Fedora made a similar change[2] in Fedora Atomic 25. [2] https://pagure.io/fedora-atomic/c/219c9bb26426811a5f32188c59682ad70c3283e5 RHEL Atomic host, in the 7.3 version, went halfway and removed the master half of kubernetes, but left the node half of the package in place. When we update the downstream version of CentOS Atomic Host, if we follow the lead of RHEL AH, we'll be pinned to kubernetes 1.3 for the kubelet and kube-proxy, and we'll have to run the master components in containers. I want to discuss diverging from RHEL AH by not including the kubernetes-node pkg in our downstream image. This would allow users to install a newer version of the kubernetes-node, such as this 1.4.5 version from my copr[3] that I hope to see move into the virt-sig soon. [3] https://copr.fedorainfracloud.org/coprs/jasonbrooks/kubernetes/ The 1.3 kube would still be available in the extras repo (once it's built), and users will have the option of installing that one, if they choose, using package layering. [4] [4] http://www.projectatomic.io/blog/2016/07/hacking-and-extending-atomic-host/ Either way, we'll need to document this, and I'm working on those docs now. Jason

3 4

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