devel August 2017

devel@lists.centos.org

41 participants
33 discussions

Request for feedback: CentOS-Atomic container
by Karanbir Singh 25 Sep '17

25 Sep '17

hi Alpha2: registry.centos.org/kbsingh/centos-atomic:7-alpha2 The CentOS Atomic Container is a minimal ( 30MB on disk ) image that can be used to host static content, and small footprint content that does not need the entire CentOS Linux Base image. This is also not meant to replace CentOS Linux Base image as the default, we want to make it available as an additional container base for apps that find it useful. The main highlight is that it does not contain yum, but has microdnf. I am looking for feedback, and some wider testing as well as recommendations on howto further reduce size, before we move to release. You can consume this as : docker run -t -i \ registry.centos.org/kbsingh/centos-atomic:7-alpha2 \ /bin/bash regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 4

Disk size on Vagrant image
by Jeff Sheltren 12 Sep '17

12 Sep '17

I have some development projects that require a large amount of disk on the VM, and are running into issues with the current centos/7 Vagrant box. Is it possible to increase the disk size of the Vagrant image to 100, or even 200 GB? Since this is a sparse image, I don't believe the change will have any affect on people using less disk space, it will only use up as much space on the host system as is in use on the VM. Laurențiu, what do you think? Thanks, Jeff

8 18

kick starting duffy2 dev on github
by Karanbir Singh 02 Sep '17

02 Sep '17

hi everyone, I've started working on duffy2 here : https://github.com/kbsingh/duffy2 - there is a base framework in place there that should give you an idea on how this all comes together, I will keep pushing bits - but this will likely get major momentum once we are done with 7.1708 Everyone is welcome to come join the effort, but I would highly recommend joining the ci-users list to track what is going on. We will have no private meetings about this, all conversation to be kept to the ci-users list, bugs.centos.org and the github repo itself. regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 3

Plan for releasing CentOS CR into CBS and CI
by Brian Stinson 31 Aug '17

31 Aug '17

Hi Folks, We've had a few discussions around how to handle releasing CR (https://wiki.centos.org/AdditionalResources/Repositories/CR) over the past few days. When we last checked in, there was still a bit of work going on building and testing pre-release CR (the QA team has been hard at work), and the altarch builds were still in progress. There are 2 ways the release might play out: - If the altarch (aarch64, and ppc64{,le}) builds are finished, and we are otherwise ready: CBS and CI will be seeded from the mirrors just like usual, and CR will be available at roughly the same time as the rest of the mirror network - If the altarch builds are not yet ready, the CentOS QA team may decide to release x86_64 ahead of the other arches. In that case, we will wait for ppc and aarch64 but still seed CI and CBS together as soon as the altarch builds are ready. If there are any questions, feel free to comment here. As always we will post updates as we move forward. Cheers! -- Brian Stinson

7 8

[NFV SIG]First meeting dates and times
by Thomas F Herbert 29 Aug '17

29 Aug '17

I want to propose a meeting time for NFV SIG: * Time: 1600 UTC - Wednesdays (date -d "1600 UTC") * Dates: Wednesday August 16, August 30, September 13, September 27 etc. * Where: IRC- Freenode - #centos-devel Please see NFV SIG page for more details. I updated the NFV SIG page, https://wiki.centos.org/SpecialInterestGroup/NFV All feedback is welcome, --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat*

5 11

missing rpms in CR
by Jacco Ligthart 28 Aug '17

28 Aug '17

Hi, when looking through the recently released CR rpm set, I think I miss these RPMs: scap-security-guide scap-workbench virt-who as far as I can see, these used to be part of 7.1611, were updated on git.centos.org for 7.1708, but were not build (no directory on buildlogs) and are not in the CR set. Jacco

1 0

CentOS PaaS SIG meeting (2017-08-23)
by Troy Dawson 25 Aug '17

25 Aug '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 23 August 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building -- minishift -- kompose - Open Floor -- Will anyone be available next week for the meeting? Troy

3 2

clearing out SIG content / trimming obsoleted content
by Karanbir Singh 24 Aug '17

24 Aug '17

hi with 7.1708 almost here, now would be a good time for the SIG's to think through if they want to lose existing obsoleted code from mirror.centos.org and have it moved to vault. When we do a new release, the tree for this version is built up manually and then pushed, so its a good convenient time to think about what the users are looking at, and perhaps trim the repos ( we typically will do this for centosplus/extras etc as well ) please get in touch with Brian or Thomas or myself for details, ideally open a request on bugs.centos.org/ regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 2

dep problems in centos-release-openshift-origin36
by Karanbir Singh 23 Aug '17

23 Aug '17

hi Cant install the ansible stack ( and therefore the utils, installer etc ) from the origin36 repos. Failing as : --> Finished Dependency Resolution Error: Package: ansible-2.2.2.0-3.el7.noarch (centos-openshift-origin36) Requires: python-keyczar Error: Package: ansible-2.2.2.0-3.el7.noarch (centos-openshift-origin36) Requires: sshpass Error: Package: ansible-2.2.2.0-3.el7.noarch (centos-openshift-origin36) Requires: python-httplib2 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 3

New CentOS Atomic Release and Kubernetes System Containers Now Available
by Jason Brooks 21 Aug '17

21 Aug '17

Last week, the CentOS Atomic SIG released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1707), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. The release, which came as part of the monthly CentOS release stream, was a modest one, including only a single glibc bugfix update (https://lists.centos.org/pipermail/centos-announce/2017-July/022505.html). The next Atomic Host release will be based on the RHEL 7.4 source code (https://seven.centos.org/2017/08/centos-linux-7-1708-based-on-rhel-7-4-sour…) and will include support for overlayfs container storage, among other enhancements. Outside of the Atomic Host itself, the SIG has updated its Kubernetes container images to be usable as system containers (http://www.projectatomic.io/blog/2016/09/intro-to-system-containers/). What's more, in addition to the Kubernetes 1.5.x-based containers that derive from RHEL, the Atomic SIG is now producing packages and containers that provide the current 1.7.x version of Kubernetes. ## Containerized Master The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. You can install the master kubernetes components (apiserver, scheduler, and controller-manager) as system containers, using the following commands: # atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-apiserver:latest # atomic install --system --system-package=no --name kube-scheduler registry.centos.org/centos/kubernetes-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-controller-manager:latest ## Kubernetes 1.7.x The CentOS Virt SIG is now producing Kubernetes 1.7.x rpms, available through this yum repo (https://github.com/CentOS/CentOS-Dockerfiles/blob/master/kubernetes-sig/mas…). The Atomic SIG is maintaining system containers based on these rpms that can be installed as as follows: ### on your master # atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-sig-apiserver:latest # atomic install --system --system-package=no --name kube-scheduler registry.centos.org/centos/kubernetes-sig-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-sig-controller-manager:latest ### on your node(s) # atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-sig-kubelet:latest # atomic install --system --system-package=no --name kube-proxy registry.centos.org/centos/kubernetes-sig-proxy:latest Both the 1.5.x and 1.7.x sets of containers have been tested with the kubernetes ansible scripts (https://github.com/kubernetes/contrib/tree/master/ansible) provided in the upstream contrib repository, and function as drop-in replacements for the installed rpms. If you prefer to run Kubernetes from installed rpms, you can layer the master components onto your Atomic Host image using rpm-ostree package layering with the command: `atomic host install kubernetes-master`. The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline (https://wiki.centos.org/ContainerPipeline), based on Dockerfiles from the CentOS-Dockerfiles repository (https://github.com/CentOS/CentOS-Dockerfiles/tree/master/kubernetes). ## Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download). ## Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade ## Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. ## Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic), based on upstream work from Project Atomic (http://www.projectatomic.io/). If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and you'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel (https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. ## Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic (https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode.

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2017