devel

devel@lists.centos.org

7 participants
4671 discussions

CentOS PaaS SIG meeting (2016-04-06)
by Troy Dawson 07 Apr '16

07 Apr '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1500 UTC - Wedensdays Date: Today Wedensday, 06 April 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms - origin 1.1.6, docker 1.9.1-origin -- repo(s) --- https://tdawson.fedorapeople.org/centos/CentOS-OpenShift.repo --- testing (buildlogs) --- candidate -- images - not started -- Quickstart - not started - What is our criteria for a release? - Building image demo ?? - Open Floor

3 4

Reminder: CentOS Cloud SIG meeting tomorrow, 15:00 UTC
by Rich Bowen 06 Apr '16

06 Apr '16

Reminder: CentOS Cloud SIG Meeting, tomorrow, 15:00 UTC, on the #centos-devel channel on Freenode IRC. Agenda: https://etherpad.openstack.org/p/centos-cloud-sig -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

Custom docker in PaaS common target
by Karanbir Singh 05 Apr '16

05 Apr '16

hi, While working on the push to buildlogs, I noticed there is a custom docker ( 1.9 ) in the PaaS Common target, i presume the distro docker ( 1.9.1 ) isnt suitable ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 3

rehashing all the buildlogs repos from cbs.centos.org
by Karanbir Singh 05 Apr '16

05 Apr '16

hi, I've just done a complete rehash of all the buildlogs repos from their corresponding cbs.centos.org tag's, please let me know if there are any issues. It does mean a lot of the older stale content will be gone ( saving us 50+ GB ) Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Update on CentOS Container Pipeline
by Karanbir Singh 04 Apr '16

04 Apr '16

hi Guys, We've made some progress on the Pipeline bringup. Highlights from the last few days: - Welcome Dharmit to the team, he's going to be contributing on the testing side of things. - We've got some baseline user stories written up, in the coming days the aim is to try and get some acceptance criteria written up, following which we will try and do some estimates and task allocations around them. We'll then get these in front of a larger audience to see how things map to expectations and what folks feel is the best priority order to work on. - Within our devel infra, we've established an idea of Project V/s Job. Users will now have their built containers delivered as <hostname>/<project name>/<job id>:<tag> - We've got a test instance up for pulp 2.8, that seems to meet all the requirements of delivering both a v1 and v2 container format; although we are likely only going to be looking at v2 from now onwards. - We've started working on a deploy script that would allow us to run managed deploy's and also help us move into a CD like setup, where we can test / deploy often. - Hardware to locate the first user facing version of the stack is now in place, and we have the required firewall policy etc setup. In the coming days, we will start doing some load testing and also start working through the implementation plans for the user service. Most of our effort is now focused on getting the content together to have a user facing deployment up. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

vagrant image nits for future update
by Vince Skahan 04 Apr '16

04 Apr '16

I've corresponded with KS in the past regarding the vagrant images (thanks!) but wanted to this to the list to request the vagrant images be tweaked a little in future updates: * the /boot partition is too small - starting with a current vagrant image, just one kernel update resulted in complaints about /boot being too full. Can we consider adding 100MB to the /boot size and changing the installonly_limit in yum.conf down to perhaps 2 to try to live in a tiny /boot without users needing to work that hard after a simple yum update The manual steps in https://unix.stackexchange.com/questions/105026 work ok, as one way to work around it manually. * there is no DVD device defined, making it painful to install VirtualBox guest additions. At a minimum the box should have the device defined there so users don't have to work so hard if they update their kernel. Possible workarounds including adding a vagrant plugin (https://github.com/dotless-de/vagrant-vbguest) to automate reinstalling the guest additions pretty nicely. Other workaround is to manually add the device in your Vagrantfile using vb.customize ala: Vagrant.configure(2) do |config| config.vm.box = "centos/7" config.vm.provider "virtualbox" do |vb| vb.gui = true vb.memory = "1024" vb.customize "pre-boot", [ "storageattach", :id, "--storagectl", "IDE Controller", "--port", "1", "--device", "0", "--type", "dvddrive", "--medium", "emptydrive", ] vb.customize ["modifyvm", :id, "--clipboard", "bidirectional"] vb.customize ["modifyvm", :id, "--draganddrop", "bidirectional"] end config.vm.provision "shell", path: "provision.sh" end I'm bringing it up only because these images are 'so' good already, it would be fabulous if no workarounds were needed out of the box. Thanks again for the rolling vagrant/docker/AMI images - much appreciated. They really help. -- Vince Skahan Infrastructure Engineering and Support Office of Research Information Services (ORIS)

2 1

Curating containers
by Karanbir Singh 04 Apr '16

04 Apr '16

hi, Yesterday a few of us met for a face to face walk through of the CentOS Container Pipeline we've been talking about. The aim was to rescope the upstream projects we can lean on, share code with, and help - and then find the glue pieces that could bring this code base together. The larger picture effectively boils down to : - Find the components needed to track code git repos ( either in git.centos.org or elsewhere ) - Find the components needed to now build that code, containerise the code, push it through a test process, and then deliver the containers either locally into a centos transitional container registry, or to a CDN like wider centos registry or if the user so desires, to a third part registry ( provided a good process can be find to handle the credentials needed ). - We'd want to use this pipeline both internally, for the CentOS Linux components ( eg. a LAMP container from CentOS Linux 7 ), for SIG components via cbs output ( eg. SCLo SIG folks shipping containers for their content ), as well as open this up via a trivial UI, for anyone in the community who'd like to come and consume this pipeline. the key piece that we didnt have clarity on was the orchestration and glue that could bind the various software components. Vaclav Pavlin, brought up that we might be able to use openshift templates in order to get the job runs done - if the input for the templates could be derived from the cccp-index, either via the jjb work already done, or writing a new filter into JJB, we might be able to execute a fairly scaleable solution without needing to own any piece of the over all code. Additionally, there is a fair interest from the Fedora team ( ie Adam! ) working on the same problem in their space, mostly consuming the identical code stack, within and for their infra, their constraints and aims. Over the coming days we are going to try and work though PoC's, get some infra setup and trial running through some of the user stories we want to execute on. Finally, a quick shout out to everyone for coming together at pretty much the last minute adhoc meeting - Fabian Arrotin, Brian Stinson, Christoph Goern, Vaclav Pavlin, Aaron Weitekamp, Tomas Tomecek, Adam Miller, Dusty Mabe, Honza Horak, Radek Vokal as well as Tim Waugh, Bama Charan and Mohammed Zeeshan for dialing into the meeting. And to everyone else, want to build containers with us ? come talk to us - we'd love to make sure we include as many user stories to get great scope before we start implementing bits. regards -- 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

8 24

CentOS distribution media ks/config files
by Phil Wyett 04 Apr '16

04 Apr '16

Hi, Could someone please point me to the official config and/or ks files used in the creation of the CentOS release media? Currently I looking at how these and the Fedora media are created. I am also looking into what appears to be bugs with the CentOS install when compared with RHEL. Regards Phil

2 3

Mitaka is now available in the Testing repos
by Karanbir Singh 04 Apr '16

04 Apr '16

http://buildlogs.centos.org/centos/7/cloud/x86_64/openstack-mitaka/ With openstack-mitaka release now passing tests, Alan requested the Mitaka content to be pushed for wider testing and are now available at the above url. ref: https://ci.centos.org/view/rdo/job/weirdo-generic-packstack-scenario001/9/ https://ci.centos.org/view/rdo/job/weirdo-generic-packstack-scenario002/13/ https://ci.centos.org/view/rdo/job/weirdo-generic-packstack-scenario003/9/ Please note that this is unreleased testing content, and should be treated as such. All feedback is appreciated, including success stories. regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

cbs.centos.org infrastructure upgrade.
by Thomas Oulevey 04 Apr '16

04 Apr '16

Dear All, Please note that next week on Monday cbs.centos.org will be upgraded to support newer features and allow us to put in place aarch64 and future alt arch builders. What does that mean for you ? Next Monday, we'll upgrade koji and mock to latest version. The change is scheduled to be implemented on Monday April 11th, 7:00 am UTC time You can convert to local time with $(date -d '2016-04-11 7:00 UTC') What will be the impact ? Koji build service will be down for an hour. It will not be possible to build new packages or images. Please note that temporary repositories served on cbs.centos.org will be available (Mostly used for CI). Please let us know before Friday April 8th if it could impact dramatically your work/releases schedule. Thomas

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel