devel December 2013

devel@lists.centos.org

24 participants
14 discussions

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

/opt/rh is a directory and not a symbolic link when installing devtoolset
by Dave Johansen 11 Feb '14

11 Feb '14

I just installed devtoolset-1.1-gcc-c++ and devtoolset-1.1-gcc-plugin-devel on a clean install and after doing so /opt/rh was a directory and not a symbolic link to /opt/centos. It was an easy fix, but is there something I can do to help diagnose the cause of the issue so it won't bite other people? Thanks, Dave

2 2

FreeIPA functional testing
by James Hogarth 01 Feb '14

01 Feb '14

Hi all, The initial commit I made (not carried out pull request just yet) does the following: * Installs IPA packages * Does automated basic configuration of server * Verifies kerberos tickets being issued for host/admin user * Tests adding a user (and checks that the initial password is expired plus the change) In the next few days I'm intending to add: * Test adding a service and getting a keytab and certificate for that service * Test adding a host * Test adding DNS zone and records * Test reloading bind (regression test for RHBA-2013-0739) * Test sudo rules configured via IPA * Test deleting all the stuff added above After that I'll issue the pull request... Next stage subsequent to the server tests working would be client side to tests registration against the IPA server itself... Is there anything else that anyone can think of that would be useful to have in the IPA test suite? Cheers, James

1 1

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

Qt Creator for CentOS
by Dave Johansen 14 Jan '14

14 Jan '14

Is Qt Creator for Qt 4 available for CentOS (either 5 or 6)? I've installed the qt and qt-devel packages on CentOS 6 and I can launch Qt Designer, but is there a version of Qt Creator available? Thanks, Dave

1 1

CentOS-6.4 OpenStack testing cloud images
by Karanbir Singh 08 Jan '14

08 Jan '14

Hi, CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well. Images are published as raw, qcow2 qcow2compressed and vpc ( vhd ) for both i386 and x86_64 CentOS-6.4 The images represent media versions, and have not had an update run against them. Its highly recommended that in testing, please check this version *then* do a yum update and repeat tests to ensure that there is no test result change in the 6.4+updates tree's. Keeping in line with the general CentOS Cloud strategy, ie to help people migrate or investigate cloud instances, we expect the images to represent as close as possible to a real machine CentOS install ( ie. no cloud specific user, people use root to login, selinux is enabled ). With some exceptions like isdn support is removed, as is cups and bluetooth since those things make little sense on a cloud instance ( nothing stopping the users from installing them later if they need to ). Also, cloud-init is included. This is based on the 0.7.x stream and based off sources published by Red Hat in their RHEL-Common/ tree. md5sums: ac6c1f683f18ec2742fc620930b6b77a CentOS-6.4-i386-Minimal-OpenStack.image.bz2 ac6c1f683f18ec2742fc620930b6b77a CentOS-6.4-i386-Minimal-OpenStack.image.qcow2.bz2 d0ef1077886714d9808eb21b0d35b64e CentOS-6.4-i386-Minimal-OpenStack.image.qcow2c.bz2 853487ac600963da6c00f69be10f11d5 CentOS-6.4-i386-Minimal-OpenStack.image.raw.bz2 dc16f7339c97856514ce35f65196a928 CentOS-6.4-i386-Minimal-OpenStack.image.vpc.bz2 9169abb16ad2b0a0195574fc8c7c6e7a CentOS-6.4-i386-Minimal-VMware.image.vmdk.bz2 1c1ff6ffca8ca7845f49a017f5386961 CentOS-6.4-x86_64-Minimal-OpenStack.image.bz2 1c1ff6ffca8ca7845f49a017f5386961 CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2.bz2 2d9a25fa573b3c512e97c9d6cea64657 CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2c.bz2 f701914d4eafb563b086853cd8e7e79d CentOS-6.4-x86_64-Minimal-OpenStack.image.raw.bz2 8476063151f9163ba37e260e144270e1 CentOS-6.4-x86_64-Minimal-OpenStack.image.vpc.bz2 a68f0bd1328bd67056e07be8501607a0 CentOS-6.4-x86_64-Minimal-VMware.image.vmdk.bz2 sha256sums: 2418f233fabc02074e54f705667ba16e2845883863e5c2e860ffc5b615f1a096 CentOS-6.4-i386-Minimal-OpenStack.image.bz2 2418f233fabc02074e54f705667ba16e2845883863e5c2e860ffc5b615f1a096 CentOS-6.4-i386-Minimal-OpenStack.image.qcow2.bz2 1156a84f18c62e5bb04d82976e6c7aa412c8486de0780e35b42f97697fe06aed CentOS-6.4-i386-Minimal-OpenStack.image.qcow2c.bz2 70c9c4f1a44b8ef349ca13da1993c1b9211a1ec72f68b4ddfc85ad21e70e6e97 CentOS-6.4-i386-Minimal-OpenStack.image.raw.bz2 ec1e5ab7508d9139df110e4a5c957c56a4dc6011fc8030cb6e48d3f6a27866ab CentOS-6.4-i386-Minimal-OpenStack.image.vpc.bz2 675c9717b82b71833cb074e76357aa2325d03730d989507110caa0e6d2e4cb5c CentOS-6.4-i386-Minimal-VMware.image.vmdk.bz2 a68e76596568b9e3117f021ba4d1db983b763ef31097b9aa47139927dcbf14bc CentOS-6.4-x86_64-Minimal-OpenStack.image.bz2 a68e76596568b9e3117f021ba4d1db983b763ef31097b9aa47139927dcbf14bc CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2.bz2 888da1ac03dd78027421db0629d899187456058a72a6e555d459bcb1d4f20296 CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2c.bz2 4626a83e8d0c706d9303874d0e26d2b127983207adb7a64e079e359e6b33a156 CentOS-6.4-x86_64-Minimal-OpenStack.image.raw.bz2 3bd4c91b276e9b4a049fd5ecd32e6e538593331a1298162ffe07e9033eefd903 CentOS-6.4-x86_64-Minimal-OpenStack.image.vpc.bz2 8c70a927d761e99e1529585b43d8dc2e080977b00436ec7038288d542fba6d4c CentOS-6.4-x86_64-Minimal-VMware.image.vmdk.bz2 Note: these images have not been through a regular CentOS QA cycle, and I am requesting people to actually test these in either dev or test environments that run the hypervisor being tested, the cloud controller being tested and provide feedback here to the mailing list. Please clearly indicate what hypervisor was used, what cloud controller and versions of the relevant software. As a baseline the CentOS CI tests ( https://gitorious.org/testautomation/t_functional ) is a good place to start, if you just need tests to run ( although these tests mostly target machine instances, its still a good baseline for these images ). And while you are at it, please feel free to submit cloud, virtualised, instance and image specific tests. The overall aim is to be ready for inclusion of Cloud image release in sync with iso and distro release for next-version ( 6.5 most likely ). Apart from baseline testing, I am also looking for feedback on package manifests included in the images ( should we add something ? should we remove something ? ) and if there is any need / scope for publishing specific role images as well ? ( eg. should we do a LAMP image ? ) Finally, I want to thank Alessandro and Octavian from Cloudbase Solutions for helping get this effort off the ground, and then their patience as I went through the mechanics of automating the build process and getting the images ready. Enjoy! -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

5 13

a public build tool for seven
by Karanbir Singh 03 Jan '14

03 Jan '14

hi, I've started the builds for centos7beta, so far its ging good ( in that 3 packages of 3 attempted have built, so its going to be a while before we have a true picture on the state of srpms ). What I'd like to also do is get a public instance of the buildsystem online that allows everyone else the ability to submit their own packages for builds against the existing rhel7b1 code and parse / process the output ( purely for testing ). Think of it as a getting-ready-for-seven sort of an effort. One challenge in the mix is going to be that EPEL isnt building for EL7 as yet, and lots of people rely on EPEL for their own deps. We could help things by pushing all of EPEL6 through, and provide feedback on the EPEL lists.... thoughts ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

12 25

Forums missing a seven
by Karanbir Singh 24 Dec '13

24 Dec '13

hi I noticed today the forums dont have a section/group for CentOS-7 should we fix that ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 3

Input for CentOS7
by Joshua Thijssen 19 Dec '13

19 Dec '13

Hi all, As a newcomer on the list with not much time, but enough to hopefully be a bit useful to the upcoming CentOS7 release, i'm wondering what the best action is I could take? I'm seeing lots of things happening here and in other places like CentOS but not sure if is there is something i could focus on or help out? I'm seeing some info at http://seven.centos.org/ about t_functional, but i'm not sure if that is the place where help would be welcome, and if so, how to proceed to be honest. gr, josh

2 3

The Guster issue
by Karanbir Singh 18 Dec '13

18 Dec '13

hi, soliciting comments on http://bugs.centos.org/view.php?id=6820 ( which deals with the partial component inclusion of glusterfs into the base distro ). There are a couple of workarounds mentioned there, but none seem perfect. In an ideal world, it would be nice if Red Hat had their RHS gluster rpms in line with the gluster rpms shipped in the base distro and we could use those into CentOS-Extras. the closest other practical option seems to be building gluster --with server enabled, and shipping the extra rpms into CentOS-Extras; provided the '--with server' is retained going forward, this would atleast mean we have version sync between the client code in the distro and the server code in CentOS Extras. The option of just adding all the gluster code into the distro we ship, server and client content included, seems very intrusive and might have an impact on third party expectations. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel December 2013