devel January 2014

devel@lists.centos.org

96 participants
61 discussions

Cloud-init for CentOS?
by Nux! 28 Jan '14

28 Jan '14

Hello, Can someone more involved with the Cloud SIG advise on how to use cloud-init in such a way that it does not violate the SIG rules? I.e. please add it to one of the CentOS repos so we can use it "legally". :-) The purpose is including it in "official" Cloudstack CentOS images. Regards, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

11 34

Cloud Instance SIG Hackathon @ CentOS Dojo 31st Jan 2014
by Karanbir Singh 28 Jan '14

28 Jan '14

hi, We are organising a hack session to try and build, test and deliver a set of CentOS-5/6 32bit/64bit images usable by various onpremise cloud setups. This email aims to give everyone an overview of what to expect on the day, so we can jump right in on the day and get productive. This is a bit of a wordy email, so feel free to skip details - I will have most of the important stuff on paper to hand out on the day as well. The Hack session is expected to start just after lunch, and will run through to the end of the day ( ~ 17:30 ); On the day, I will have a local Wifi network with SSID DojoHackathon running at the time, everyone wanting to participate will need to get onto that. dhcp on the network will hand out 172.30.30.100 - 250 IP's. There is a gateway on .1 that will NAT requests to the upstream internet ( but I'm told its slow, so dont rely on it being there ). If anyone needs content to pull, please let either me or Johnny know, we will mirror it down before the event and make sure its on the mirror host on the network at the time. We are going to have : - CentOS 5/6 on both 32/64 bit x86 - EPEL 5/6 - EPEL-Testing 5/6 Various people representing projects have offered to bring pre-setup cloud infra on their laptops, thanks for that. Lets try and target everyone of those on the day. So far the list is : - OpenNebula - CloudStack - OpenStack ( the HPCloud edition ) - OpenStack ( the RDO edition ) A rather basic idea of what to expect in terms of infra/network on the day : http://bit.ly/1ffXr4G ; Workflow anticipated: - git.centos.org ( hosted locally ) will have the git repos that host kickstarts and metadata files that have some info around the kickstarts. - anyone can clone the git repos ( I will make sure its pretty clear as to what repo to get for what task, ideally there will only be one git repo with all the kickstarts ). - make changes / edits / push back to git.centos.org ( please ensure git user.name and user.email is sane ) - git post-recv triggers kick off the actual image builds on the image-builder node, which will then push the resulting file to cloud.centos.org ( both image-builder and cloud.centos.org mirrors will be hosted locally ). - cloud images from cloud.centos.org can then be downloaded and instantiated on the cloud infra people are running; - once satisfied that the image does everything that is 'required', git clone the t_functional repo, and run the test suite. PASS on that would indicate them that the image is good to ship. For the day, we will trim the test suite down to just the basic stuff that runs in 10 min or less. - Indicate pass with a comment in the metadata file and git commit which starts with 'RELEASEABLE ', git push. rinse & repeat for 32bit and 64bit. Worth noting here that the reason i have all the various components setup to work with real world urls ( faked by dnsmasq on the .1 machine ) is that post hackathon the exact same infra will go live on the same urls. With one major change : we will have little or no ACL's fon the git repos at the hackathon to make live easier and encourage participation. Post Hackathon, we'll need to establish a mechanism for people to request commit access. If we still have time at the end of the day, we can shoot to deliver something that works for vmware, ovirt and docker. I am still waiting to hear back from the Eucalyptus guys if someone from their side is going to be at the hack session. please note: all kickstarst and images will need to only consume content hosted in mirror.centos.org and epel ( or if you need something else, let us know before Wed 29th ). See you there, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 6

Adding community PostgreSQL RPMs to CentOS repositories.
by Devrim GÜNDÜZ 26 Jan '14

26 Jan '14

Hi, Greetings first: I am maintaining the PostgreSQL community RPMs : http//yum.postgresql.org About 2 years before, Karanbir and I spoke a bit about adding these RPMs to CentOS repositories. Right now, only 8.4 is officially supported in RHEL/CentOS, which will be EOL'ed in a few months by upstream. However, community has RPMs for all versions from 8.4 to 9.3, which are in active development and released at the same time with the tarballs. Community RPMs has the ability for parallel installation also, so that people can run multiple version as the same time. So, how would you like to proceed? The SVN repo is open to public, and all you will need to do is pulling them and building the packages on CentOS servers. Regards, -- Devrim GÜNDÜZ Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz

4 13

EPEL and i686
by Karanbir Singh 24 Jan '14

24 Jan '14

Hi Whats the plan for EPEL i686 / EL7 ? Does anyone know if there is even going to be a multilib attempt or is everything going to stay x86_64 clean ? - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

6 12

Packaging Office hours at 16:00 UTC today
by Jim Perrin 24 Jan '14

24 Jan '14

At 10am CST / 16:00 UTC we'll be starting the packaging office hours discussion for SIGs and Variants. if you've got some questions you'd like us to address, please email them to us, or ask your questions via irc in #centos-devel on freenode. If you want to just follow along, we'll be broadcasting the session via http://www.centos.org/media/ -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

5 27

Cloud Instance SIG
by Karanbir Singh 23 Jan '14

23 Jan '14

hi guys, pushing this a bit forward since there is quite a bit of activity in this area already : http://wiki.centos.org/SpecialInterestGroup/CloudInstance while there are quite a few people keen on this subject, I've not added names to the wiki page, please come along and either edit it in ( if you are editgroup members ) or request addition and setup a homepage for yourself on the wiki. going out on a limb here but I am going to propose we get cloud-init out of EPEL into a local repo here so we can mange the entire stack locally for the time being while the larger repo dependancy conversations are ongoing. Also, this Wednesday's OfficeHours on Wed 22nd at 10:00 UTC ( http://wiki.centos.org/OfficeHours ) is dedicated to the Openstack images conversation. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 3

CloudStack instance ks files
by Nux! 23 Jan '14

23 Jan '14

Hi, Waiting further instructions regarding this whole thing. For now there are fully working ks files here: https://github.com/NuxRo/kickstarts Currently waiting for the promised cloud-init 0.7.4 or 0.7.5 and to see how that works with Apache CloudStack. Cheerio, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

1 0

Cloud Instance SIG and Vendor ecosystems
by Karanbir Singh 22 Jan '14

22 Jan '14

hi, I'd like to ask everyone for comments on and around working with vendor Ecosystems. We already have relationships in place ( some as old as 4 - 5 years ) where we have worked with vendors to get CentOS images into their service plans; but going forward we should consider what the overall goal here is going to be. Some vendors are easier than others to work with, but is this something we should persue as a part of the CentOS Instance SIG ? I am quite keen to build on the existing relationships with people like AWS, GCE, HPCloud, BrightBox etc and even expand the scope of the vendor involvement in the SIG, but where is everyone else's thought process on this ? - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 3

github foo
by Karanbir Singh 20 Jan '14

20 Jan '14

hi, It would be great if Merge Requests from github.com could be announced on irc #centos-devel in realtime, and a summary of all requests from the day posted to this centos-devel list at midnight UTC. Is something like that possible ? And if so, how does one go about setting that up. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

Building c6.99.00
by Karanbir Singh 17 Jan '14

17 Jan '14

hi, First community contributed build request for the el7b1 distro! : https://github.com/CentOS/sig-core-bld-seven/pull/1 We're going to build the entire rhel7b1 srpm stock against f19-i686 + rolling build repos into target c6.99.00-i686. Once we have that done, we remove the f19 requirement and rebuild against c6.99.00-i686 into c6.99.01-i686 rolling builds. That should give us a good idea of where things are w.r.t i686. We can then check back into what is needed into the x86_64 tree for multilib, and list the rest of the distro. Once we have that, I'd like to start a conversation around what is needed and how people feel about 'owning' the i686 that isnt needed for multilib x86_64. For now, the churn will start, build logs are going to the centos-build-reports list ( http://lists.centos.org/pipermail/centos-build-reports ) This is what a success report looks like http://lists.centos.org/pipermail/centos-build-reports/2014-January/000005.… the build-id is timestamp to a second's resolution. For centos6 one of the key things we've had to do ( increasingly lesser of ) is to rewind the buildroot states ( aka. git blame, but for the entire distro as a whole ) and patch blame ( aka git blame, for the spec file, rewinding patch layers ). The Build-ID is key to that process. Based on initial builds, we are not going to need any of this anymore ( we've not used it in el6 since the 6.3+updates days ). Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2014