devel September 2012

devel@lists.centos.org

31 participants
11 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

Interested in IA64 build.
by James A. Peltier 22 Jan '13

22 Jan '13

I noticed on the SIG that people interested in other ports of interest. I'd like to express interest in the IA64 port. What is the best way to get started? I have two SGI Itanium 2 based machines. One 64 processor x 64GB SGI Altix and a 32 processor x 32GB RAM SGI Prism. They are currently running CentOS 4.8 and I would love to be able to run CentOS 5.5 on them to get them into compliance with the rest of the cluster. -- James A. Peltier Systems Analyst (FASNet), VIVARIUM Technical Director Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpeltier(a)sfu.ca Website : http://www.fas.sfu.ca | http://vivarium.cs.sfu.ca MSN : subatomic_spam(a)hotmail.com Does your OS has a man 8 lart? http://www.xinu.nl/unix/humour/asr-manpages/lart.html

9 53

Forums
by Karanbir Singh 20 Dec '12

20 Dec '12

Hi Guys, Realistically, what are the best-of forum software out there at the moment ? And what are the top 10 items on the forums moderators wish list at this time ? We can either move the forums to forums.centos.org or export them behind a proxy at www.centos.org/forums ( I prefer the second option ). Finally, lots of people seem to think that moving towards a serverfault.org type of interface is more 'these days' than a conventional forum setup. Thoughts ? -- 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

14 77

CentOS Theme for Wordpress
by Karanbir Singh 03 Nov '12

03 Nov '12

hi Guys, Would someone be willing to take a stab at getting the CentOS theme going for a wordpress blog ? The present wiki.centos.org theme would be a good place to start. I'd like to get a status / infra update blog going, and wordpress seems to be the easiest way to go about that. Regards, -- 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

2 2

Shipping an EPEL release
by Karanbir Singh 09 Oct '12

09 Oct '12

hi guys, One bit of feedback at LinuxCon this year from people was that we should ship epel with a lower barrier to entry. And I have mixed feelings about that. But I wanted to know what everyone else thinks about : 1) Shipping epel-release in CentOS-Extras, so its installable, usable out of the box. 2) Shipping epel-release in the distro itself, with the epel repos's enabled=false. This is the option that most people seem to want, but I am least keen on. 3) do nothing, leave things as they are. Ofcourse, if we do either (1) or (2) we would need to set some sort of a baseline standard that allows other repo's to be included as well ( as + if they meet the baseline standard ) regards, -- 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

27 67

yum-security and CentOS-5 / 6
by Karanbir Singh 04 Oct '12

04 Oct '12

hi Guys, with a bit of time opening up, I've gone back to looking at the yum-security issue and how we can address it ( i.e: atleast get the basics working ). I plan on doing the work in multiple stages as : step1: get a basic set of metadata online so that people can detect if an update is tag'd security, bugfix or enhancement step2: get some more metadata added in, with bug id's and cve's into that metadata step3: get everything rolled out by default on all centos installs and look at how external projects like spacewalk/pulp etc consume this metadata At the moment, I'm only thinking about things and trying to scope out the work. However, there is one issue that might be a spanner in the works based on how we have mirror.centos.org setup. What we have right now only provides for the <version>.<release> rpmset and updates but only in relation to that specific tree (eg. /6.3/ is what /6/ maps to at the moment ). Yum-security metadata in this repo would then only be relevant to the rpms contained in /6.3/, whatever repo they might be in - however, someone running 6.0 or 6.1. when checking for updates is likely to miss interim updates that were security tag'd at some release level or the other. One way to work around this would be to have yum consider all interim package metadata between installed.rpm and latest-in-repo.rpm ( which would then mean that we would need the yum-security metadata to contain all info for everything ever released ; isnt a problem as such ). Or we setup a repo that has everything ever released. This in turn has some serious caveats. Storage on every mirror being a good problem to start with - however, in limited tests it looks like yum will work with redirect, so while we would need the metadata to contain all packages, the physical packages can still be handed out from vault.centos.org, but that redirect foo needs some level of smartness on the mirror end; trivial to implement when we control the mirror.centos.org network, however a very large part of the mirror services are offloaded to external mirrors - hundreds of them. Its super tricky getting smartness onto each and every one of their machines. Thoughts, concerns, ideas ? There is no 'work' thats been done at this point on the problem, so we can take pretty much any course of action that seems sane. I feel its important that if we are going to provide a mechanism that people will then in turn rely on to get patch requirements for their machines, we need to make sure we have 100% coverage. -- 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

5 10

Test OpenStack Essex builds for CentOS
by Karanbir Singh 03 Oct '12

03 Oct '12

hi, http://people.centos.org/z00dax/openstack/essex/ repo file: http://people.centos.org/z00dax/openstack/essex/CentOS-OpenStack-Essex-test… These should be considered as testing packages and are based on the upstream Open Stack preview 1 rpms set. These rpms are also signed with the CentOS-6-Testing key and not the regular distro key. The .el6.alt distag indicates they were built on the Alt.BuildSys and not the primary system.[1] https://access.redhat.com/knowledge/docs/Red_Hat_OpenStack_Preview/ is perhaps the best place to go for a quick start process. The only major difference is section 1.1 of the docs, that explain howto get the rhn repo setup should be replaced by just downloading the above mentioned .repo file into /etc/yum.repos.d/ It takes about 15 minutes to walk through and the end result is a functional open stack install. If anyone wants to offer up some basic template images to use, please do so. I have not tested to see how these rpms are going to work with/conflict with the EPEL hosted openstack. Some feedback on that would be appreciated as well. - KB [1]: Lots more details on that over the next few weeks. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 9

Centos Test times
by Madhurranjan Mohaan 21 Sep '12

21 Sep '12

Hi, We were discussing build and test times on the IRC and one suggestion was to get information around tests and how much time its taking . Attached is a script used to run the tests and the final csv in descending order that gives you the tests and the time taken . Most of the time is taken by the installs . I've also included the csv which has errors when I ran these tests. These were run on a Centos 6 VM. This experiment didn't seem to use the nearest mirror. So for the next run, added the local mirror and the results are in the csv - "sorted_test_times_3_descending.csv" Suggestions to make this better would be great as well . thanks, Mamu

2 1

Re: [CentOS-devel] Shipping an EPEL release
by Christoph Galuschka 14 Sep '12

14 Sep '12

> > hi guys, > > One bit of feedback at LinuxCon this year from people was that we should > ship epel with a lower barrier to entry. And I have mixed feelings about > that. But I wanted to know what everyone else thinks about : > > 1) Shipping epel-release in CentOS-Extras, so its installable, usable > out of the box. > > 2) Shipping epel-release in the distro itself, with the epel repos's > enabled=false. This is the option that most people seem to want, but I > am least keen on. > > 3) do nothing, leave things as they are. > > Ofcourse, if we do either (1) or (2) we would need to set some sort of a > baseline standard that allows other repo's to be included as well ( as + > if they meet the baseline standard ) > I add EPEL to all C6 installations because there is a certain set of packages which I need from that repo. But this is done by a script which sord of customizes the C6 installation to my needs. So basically I'm fine doing this by hand. Long story short: options 3 and 1 (in this order) get my vote. To be honest I never thought about other repos being part of CentOS by default. Christoph

1 0

Re: [CentOS-devel] Shipping an EPEL release
by κiζs飛ゞ揚 13 Sep '12

13 Sep '12

You have been unsubscribed from the CentOS-devel mailing list !!! Why should that be? How do I send mail to everyone? ------------------ Original ------------------ From: "David Hrbáč"<david-lists(a)hrbac.cz>; Date: Fri, Sep 14, 2012 00:20 AM To: "centos-devel"<centos-devel(a)centos.org>; Subject: Re: [CentOS-devel] Shipping an EPEL release Dne 13.9.2012 17:32, Karanbir Singh napsal(a): > 3) do nothing, leave things as they are. > My vote. DH _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2012