devel

devel@lists.centos.org

2 participants
4653 discussions

Packaging the VirtualBox Guest Additions?
by Laurentiu Pancescu 16 Aug '16

16 Aug '16

We occasionaly get complaints from users that our official Vagrant images do not include the VirtualBox Guest Additions. We do not include them because the CentOS repositories do not have any package for VirtualBox. Packaging it would probably require a significant amount of work - the Debian source package shows quite a number of first-level dependencies, probably not all already available in CentOS. [1] I'm also not sure if packaging the full VirtualBox is even desirable. [2] The alternative would be to package just the Guest Additions (which have considerably fewer build dependencies), to be able to include them in the Vagrant images. Two VirtualBox developers told me in #vbox-devel that the source code already supports building just the Guest Additions, and it's actually used for generating the official download images: one should simply invoke "kmk VBOX_ONLY_ADDITIONS=1", or, I quote: 'kmk VBOX_ONLY_ADDITIONS=1 packing to produce the ISO, which will only be for one platform and bit count.' They also believe we should be able to get away with simply providing the binary modules, since our kernels have a stable ABI (the upstream Guest Additions ISO, as well as the Debian packages, require DKMS and the development tools and kernel headers, which would considerably increase the size of our Vagrant images). We would probably need to incorporate some functionality from their installer at RPM build time, to get just the binary modules. Regards, Laurențiu [1] https://packages.debian.org/sid/virtualbox [2] https://lkml.org/lkml/2011/10/6/317

3 3

cbs.centos.org upgrade on 2016-08-22
by Thomas Oulevey 16 Aug '16

16 Aug '16

Hello Folks, Please note that next week on Monday cbs.centos.org will be upgraded to support newer features. What does that mean for you ? Next Monday, we will upgrade imagefactory to latest version. The change is scheduled to be implemented on Monday August 22nd 7:00 am UTC time You can convert to local time with $(date -d '2016-08-22 7:00 UTC') What will be the impact ? During the update it will not be possible to build 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 Thursday August 18th if it could impact dramatically your work/releases schedule. -- Thomas Oulevey on behalf of the infrastructure team

1 0

PaaS Question: How to stay on origin 1.2
by Troy Dawson 15 Aug '16

15 Aug '16

A question came up on the OpenShift-Ansible issue[1], that I would like to discuss with a broader, CentOS based community. "With OpenShift Origin, running yum update or yum upgrade will include any updated OpenShift packages, potentially causing issues." With Origin 1.3 getting ready for release candidate, this is a very valid concern. I've already put this on the next PaaS SIG meeting agenda, but I wouldn't mind hearing opinions before the meeting. Feel free to state problems, worries, solutions, or overall comments by replying to this email and/or adding to the issue. Thank You Troy [1] - https://github.com/openshift/openshift-ansible/issues/2293

1 0

Atomic Developer Bundle 2.3.0 released
by Praveen Kumar 15 Aug '16

15 Aug '16

We are pleased to release the Atomic Developer Bundle 2.3.0 through CentOS Atomic SIG. Atomic Developer Bundle consists of a Vagrant-box and couple of Vagrant plugins. Please refer project documentation for more information [4]. This Atomic Developer Bundle release also includes release of following ecosystem projects: * vagrant-service-manager 1.3.0 : A set of utility scripts and configuration files for ADB * vagrant-sshfs 1.2.0 : SSHFS synced folder implementation for Vagrant. * adb-utils 2.0: A set of utilities for managing services used provided in the Atomic Developer Bundle. This release includes many changes and bug fixes, which are detailed in the release change log of vagrant-service-manager [1] and ADB [2]. Introduction: Atomic Developer Environment (ADB) helps to setup Kubernetes, Docker, OpenShift, Mesos Marathon on your workstation easily. Application developers can quickly create the setup to containerize applications and run them using mentioned platforms . ADB is designed to run on Microsoft Windows, OS X and on GNU/Linux and give homogeneous setup across different operating systems. ADB and OpenShift can also be used directly from Eclipse using docker tooling and OpenShift adapter [5] [6]. Please update the ADB Vagrant box [3] and the vagrant-service-manager ($ vagrant plugin update vagrant-service-manager) and give the new ADB version a spin. [1] https://github.com/projectatomic/vagrant-service-manager/releases/tag/v1.3.0 [2] https://github.com/projectatomic/adb-atomic-developer-bundle/releases/tag/v… [3] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do… [4] https://github.com/projectatomic/adb-atomic-developer-bundle [5] https://developers.openshift.com/getting-started/eclipse.html [6] https://www.eclipse.org/community/eclipse_newsletter/2015/june/article3.php -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com

1 0

sclo-ror42: Ruby on Rails 4.2 security updates in testing
by Dominic Cleal 12 Aug '16

12 Aug '16

Security updates for the sclo-ror42 software collection, which provides Ruby on Rails 4.2, are now available in the CentOS SCLo SIG testing repository. To apply the updates: yum upgrade --enablerepo=centos-sclo-sclo-testing --nogpgcheck sclo-ror42\* These fix: a) CVE-2016-6316: Possible XSS Vulnerability in Action View https://groups.google.com/forum/#!topic/ruby-security-ann/8B2iV2tPRSE b) CVE-2016-6317: Unsafe Query Generation Risk in Active Record https://groups.google.com/forum/#!topic/ruby-security-ann/WccgKSKiPZA The packages updated are (both el6/7): sclo-ror42-rubygem-actionpack-4.2.5.1-2.el7 sclo-ror42-rubygem-activerecord-4.2.5.1-3.el7 sclo-ror42-rubygem-actionview-4.2.5.1-3.el7 I'll push them to stable in a week or so's time, but would appreciate any feedback. -- Dominic Cleal dominic(a)cleal.org

1 0

Ceph Jewel is now available for testing on AArch64
by Jim Perrin 11 Aug '16

11 Aug '16

Thanks to the work of François Cami, we now have a build of Ceph's Jewel release available for testing on the AArch64 platform. You can find the packages on buildlogs at http://buildlogs.centos.org/centos/7/storage/aarch64/ceph-jewel/ To install them via yum, simply add a repository definition like the one below: cat /etc/yum.repos.d/ceph-jewel-testing.repo [ceph-jewel-testing] name=Ceph Jewel Testing baseurl=http://buildlogs.centos.org/centos/7/storage/aarch64/ceph-jewel/ metadata_expire=6h gpgcheck=0 Please test them out and let us know if anything isn't behaving as you'd expect. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

Proposing ansible roles for the cfg mgmt SIG
by Michael Scherer 11 Aug '16

11 Aug '16

Hi, so for people who do not know me, my name is Michael Scherer, I work as a sysadmin on the open source and standard (OSAS) team at Red Hat, focusing on infrastructure issues for community my employer want to support (in the limit of 26h per day). In practice, that mean doing system administration for projects like manageiq, ovirt, gluster and others. My team want to push for community owned infrastructure (kinda like what Fedora and Mageia do, leveraging the config as code pattern and solution like puppet and ansible), so we are publishing as much as possible our configuration under free software license and so we have started to develop a set of ansible roles that can be reused accross community, trying to provides best practices[1]. They are partially on gitlab.com and partially on github.com. We standardized on ansible for various reasons, mostly due to a perceived higher ease of use by beginners and a slightly less painful deployment model (no need to keep agent and server in sync, which was a pain point for me for puppet, despites loving puppet itself). And we reached the conclusion that we could make this work useful to others, and a logical conclusion was to join the config management sig. So what we had in mind is the following: - we could use the roles to test them on various centos platforms with Centos CI and thus providing easy to use roles for centos users. We are mostly using Centos for infastructure. - the roles could also be used to test against the git head version of ansible to make sure that regression in role and/or ansible are detected early - this could show as best practices for roles developpers, with testing, etc So, what does members of the SIG think of the idea ? [1] who are highly opinionated and subjective, as I said, I am sysadmin, which is a polite way to say I am professionally stubborn. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS

2 1

CentOS PaaS SIG meeting (2016-08-10)
by Troy Dawson 10 Aug '16

10 Aug '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 10 August 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2016/august/centos-devel.2016-08-03-17.00.lo…

1 0

testing vagrant and the vagrant box's
by Karanbir Singh 10 Aug '16

10 Aug '16

hi guys Lala brought up a good point - we should validate all the various vagrant box's we build from cbs, and we should ideally validate them against the vagrant shipped from the sclo-vagratn1 stack. Ideally get to a point where we can block release either way. Ie. dont release vagrant box's that dont work with our vagrant, and dont release vagrant if it breaks any of the vagrant box's that we build and ship. I'll send a PR through shortly that should fix the problem here : https://ci.centos.org/view/SCLo/job/SCLo-sclo-vagrant1-sclo-C7-x86_64/ from there on, whats the best to get this 2way testing setup ? Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Problem with vagrant box (ssh-ing during ``vagrant up`` doesn't work)
by Rafal Skolasinski 10 Aug '16

10 Aug '16

Hi, I wanted to try vagrant box of Centos7 for my vm but I encounter problems during setting up a vm. I did very basic setup, in empty folder I did ``` vagrant init centos/7 vagrant up ``` In a result it repetitively promts ``` default: Warning: Authentication failure. Retrying... ``` Full output here: http://pastebin.com/JrQHER6L I am using Linux Mint 17.3 with VirtualBox 5 and Vagrant 1.8.5. Any clues what's going on wrong here? Best, Rafal P.S. I am sorry if I doubled the email, I don't know if it get through on the first time before I registered to the mailing list.

5 9

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