devel

devel@lists.centos.org

4679 discussions

Cent OS 5.5 Clustering and Support
by Kumar, Ranjan 06 Apr '11

06 Apr '11

Hi, We are a Channel product team within LSI and we are trying to add Cent OS 5.5 to our compatibility Matrix. We found out that LSI currently has a relationship with CentOS for another project on the Internal Storage division but not with the OS Certification team. We require some information on CentOS which will help us plan the deliverables. And considering the timelines we need to deliver at it will be great if someone from CentOS can help us out in this regard. If anybody else also can answer these in the mailing list, we would be grateful. The questions that we have are as follows:- 1) Cluster Support : * Does CentOS 5.5 provides native cluster support ? * Is there any cluster suite available for CentOS 5.5 ? * Can we use the cluster suite in CentOS 4 for 5.5. 2) Does CentOS have any self Certification tool which allows OEMs/Vendors to qualify the OS and post it in their compatibility matrix? One we start our qualification, we might need some help in resolving issues/defects on CentOS. Can we open a channel or Point of contact who will be able to help us out with such issues. I would also request to forward this email to the right forum if the mailing list we are sending to is not the appropriate one. Thanks and Regards. Kumar Ranjan LSI Technologies.

10 12

I want to help
by Marian Marinov 05 Apr '11

05 Apr '11

Hello, Just today I read in LWN( https://lwn.net/Articles/435744/ ) about the problems with CentOS. I want to offer hardware (build servers) and I also want to volunteer time for cleaning up packages. Is there a page giving some guidelines? How can I start helping ? I'm packaging my own software with RPM for more then an year now so I think I have the required knowledge. -- Best regards, Marian Marinov

16 25

Status 5.6
by Leon Fauster 05 Apr '11

05 Apr '11

For the archives: http://www.karan.org/status_5.6.html Leon

1 0

Re: [CentOS-devel] QA effort
by Karanbir Singh 04 Apr '11

04 Apr '11

On 04/04/2011 06:46 PM, Dennis Gerasimov wrote: > Thank you, I think I know just the part I want to tackle: the cluster > suite: cman, clvm and rgmanager (excluding gfs* for now). > Where do we keep the tests? Are there examples of tests for other > packages that I can look at? http://www.karan.org/blog/index.php/2010/03/30/autmated-install-testing-for… has something to start with, its very basic, but its something. There have been a few posts about that here on the list as well. But I'll give you enough to get started with : The tests themselves can be of two types : a) installer based ( where one would write a kickstart, that sets up the machine does its tests or sets up the tests in %post ). Kickstarts are well, kickstarts. Look here for some examples if you need to : https://nazar.karan.org/cgit/bluecain/tree/ b) post-install scripts. These are the ones where one would do functional tests. Each of these tests is a single script which must - at this time - be self contained. And the only real concern for the testing system is what the exit code was ( 0 = pass, 1 = fail ). They can be written in any language you like. Here is a very simple example: ------------------------------------ #!/bin/sh echo -n 'Test that all updates can be applied to this machine cleanly' yum -d0 -y upgrade > /dev/null 2>&1 if [ $? -eq 0 ]; then echo ': PASS' else echo ': Fail' exit 1 fi ------------------------------------ here is another which does something similar : ------------------------------------ #!/bin/sh echo -n 'Test that all 32 rpms can be removed' # only run this test on x86_64 machines! is64=$(uname -m|grep x86_64) if [ "$?" -ne '0' ]; then echo ' Skip' exit 1 fi yum -d0 -y erase *.i?86 > /dev/null 2>&1 if [ $? -eq 0 ]; then echo ' PASS' else echo ' Fail' exit 1 fi # note, this does not imply the machine is still usable after # the remove! need to test that independently ------------------------------------ Things that you *do* need to be concerned about : - kickstarts should make no assumptions about storage ( since we run them on xen and kvm hosts ). If you need specific names and labels, use lvm. - Getting the tests into the machine post install is not something you need to worry about, thats done by the test harness. - ideally, tests will be in filenames that reflect the package or the nature of the test they are hoping to work against. eg: yum_CanBlindUpgrade.sh and yum_CanRemove32bit.sh - if you are not writing a kickstart to cover the scope of tests, then you need to assume packages being tested are not installed. eg. php tests should start with a 'yum -d0 install php' - test real functionality first, then work your way down if you want to. Eg: ------------------------------------ #!/bin/sh echo -n 'Test to see if dns works' echo 'nameserver 8.8.8.8' > /etc/resolv.conf # its important we dont hit a dns record with a wildcard like centos.org ping -c 1 www.google.com > /dev/null 2>&1 if [ $? -eq 0 ]; then echo ' PASS' else echo ' Fail' exit 1 fi # implied results: # - network works # - default route is really honoured # - atleast one network link on the machine is working # - ipv4 is functional ------------------------------------ So in this case, its testing if DNS is functional ( something a user would care about ) and you get some free test wins ( network works, route etc ). Questions ? ask away. Maybe a few people can get together and even start working on a set of wiki pages for this stuff! The tests are all inside a git repo, but for the first few that you write - how about posting them here to the list and we can take it from there. - KB

1 0

Brief status update, please?
by Matthew Miller 04 Apr '11

04 Apr '11

I checked the web forum in case there was something new there, and there doesn't appear to be. It's been a couple of weeks without news. Thanks. -- Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>

7 15

QA effort
by Jonas Larson 04 Apr '11

04 Apr '11

Hi all, How can I help (if I can) to contribute to the fine distribution of Centos? //jonas larson

4 4

Website v2 Meeting
by Andrea Veri 04 Apr '11

04 Apr '11

howdy guys, looks like we are stuck again with the renew/rebuild of the CentOS website and therefore I pinged Ralph the other day proposing a solution. We definitely *need* to move on :) I think the best way to start sorting things out would be to setup an IRC meeting anytime soon to organize our work, decide which content should stay and which one should go away, what are our next steps, who will take care of them and how etc. I live in a GMT+2 country and it would be great if we could handle this meeting in the evening, let's say 9.30-10pm in any day which is *not* friday/saturday/sunday. Next week, tuesday or wednesday at around 9.30-10pm would be fine for everyone? (for everyone I mean anyone interested in helping out and volunteering for the website v2 rebuild) The channel where the meeting will be held is still to be decided, but that's definitely not an issue at the moment. I am open to any change to the time/date, but please let's don't get everything stuck again. (1 month is gone with no activity on this side) cheers, Andrea

3 5

Re: [CentOS-devel] QA effort
by Jonas Larson 30 Mar '11

30 Mar '11

Hi Phil, On 03/28/2011 08:02 AM, Phil Schaffner wrote: > A good start would be a brief introduction with a description of your > background and capabilities, and a statement of how you would like to > contribute to CentOS. For QA testing - what platforms, applications, etc. I'm a system administrator/consultant working with linux and unix (well mostly linux these days :-) ). I have been working with linux since '99 and has worked with red hat ever since. I first installed redhat 5.2 and was hooked! Those days I only worked with HP-UX and linux was a step forward, to say the least. Over the years I have worked with red hat a lot, building custom CD's, auto-installing with PXE, kickstart, performance tuning applications and so on. I have done some programming (C and python) but don't consider myself a programmer. I have access to our lab with the x86_64 plattform. On the application side I'm not sure what is needed, I am open to suggestions! My main interest is in contributing and trying to keep centos as current as possible. Let me know if you need something more specific! Cheers, Jonas

1 0

Re: [CentOS-devel] Upstream SRPMs
by Coy Hile 25 Mar '11

25 Mar '11

> Date: Thu, 24 Mar 2011 17:59:16 +0100 (CET) > From: Dag Wieers <dag(a)wieers.com> > > You can find these at: > > ftp://ftp.redhat.com/redhat/linux/enterprise/ > Thanks, Dag. Are the SRPMS for the updates published likewise? I'm mostly just curious. Having some idea of how this all works would be beneficial if I were to decide to contribute in the future. -Coy

2 1

Re: [CentOS-devel] Polite Request
by Butch Whitby 25 Mar '11

25 Mar '11

hi Guys, > > This list is the centos-devel list, there are other lists like this > list. But*this* list is the list dedicated to development of CentOS. > Which means its not a list to talk about generic technical stuff that > does not directly have a relation to centos development, its also not a > list to discuss development issues with code and process that isnt > centos itself. Its not a place to announce stuff, its also not a place > to have social and 'in the old days...' or 'when i was young..' or > politics ( around open source, generic software, technology or otherwise ). > > Recently lots of fluff being posted here is just noise and really not > appropriate for this list. The end result is that most of the people > doing development work on CentOS are not reading this list anymore since > its all irrelevant and offtopic noise. > > Its not a good situation to be in, so a polite request from my side - > take it elsewhere. Lets try and maintain topic sanity here on this list > so we don't need to all go back to using private, focused and productive > lists; > > Thanks > > - KB I agree. I've been watching this list for updates on whats happening with the status of 5.6 and 6.0. About all I do at this point is scan over the digest to see if there is anything that ISN"T completely irrelevant to the intent of the list. Please take all non CentOS dev conversations elsewhere, and let those that are dev's concentrate on getting the work done rather than addressing unrelated fluff as KB has done here. Their dev's not gossip columnists. FWIW, yes I do consider my message unrelated, even though it's in support of the original intention of this list. -- Butch

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