Thanks Brian Mathis and Karanbir.
Hope people learn email etiquette from you guys !!
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Karanbir Singh
Sent: Monday, April 04, 2011 6:53 PM
To: The CentOS developers mailing list.
Subject: Re: [CentOS-devel] Cent OS 5.5 Clustering and Support
On 04/01/2011 03:50 PM, Kumar, Ranjan wrote:
> 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:-
I am fairly sure that the CentOS Project does not have any relationship
with LSI on any front ( internal storage or otherwise ). We have always
encouraged vendors to speak with upstream ( Red Hat ) for things of this
nature. However, being a non vendor driven project, there are still some
options that you might be able to follow. The most promising one of
which is self endorsement.
> 1)Cluster Support :
> *Does CentOS 5.5 provides native cluster support ?
That would depend on what you imply by 'support'. Code components and
resources needed to build something of this nature are included into the
> 2)Does CentOS have any self Certification tool which allows OEMs/Vendors
> to qualify the OS and post it in their compatibility matrix?
No. On the other hand, we prefer that vendors do both:
1) Approach upstream for such certifications / testing etc
2) Self endorse CentOS from their perspective with their own toolchains
( which, in your case would be LSI endorsing CentOS as a supported
platform ). If there is a reasonable need to do so, we could potentially
host a resource that allows third party vendors to document their
certification / endorsement; but at the moment there is nothing of that
nature on .centos.org
> 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.
http://bugs.centos.org/ is the best place to track something of this nature.
Its possible that these things might change in the future, but at the
moment this represents the state of play.
On Fri, Apr 01, 2011 at 08:20:29PM +0530, Kumar, Ranjan spake thusly:
> We are a Channel product team within LSI and we are trying to add Cent OS 5.5
MegaCLI is completely unacceptable and the reason why I refuse to buy LSI.
As far as I can tell, the MegaCli package is the way to manage the Dell PERC
from the command line in Linux. To work with it you have to hunt down the
MegaCli-1.01.39-0.i386.rpm tools since the tools are proprietary to LSI and
don't ship with RHEL.
Then you RPM install it and go looking for the software it installed. MegaCli
is rarely used. Only when setting up disks. They didn't call it megacli or
something I might remember. They called it MegaCli64 (case sensitive) which is
installed in /opt/MegaRAID/MegaCli/MegaCli64.
# /opt/MegaRAID/MegaCli/MegaCli64 --help
Invalid input at or near token -
# /opt/MegaRAID/MegaCli/MegaCli64 -h
whoah! This gets you a massive amount of cryptic command line options with no
explanation as to their purpose.
This is LSI's idea of "help". I'm a command line commando of 20+ years and this
scares even me! It would have been nice if they at least tried to make it work
somewhat like the Linux mdadm command or at least provided some examples of
common use cases etc. Because of the oddity of this command various people out
on the net have compiled "cheat sheets" to help poor souls like me figure out
how to use this thing:
Usually I avoid using this command and just reboot the server into the BIOS and
configure the RAID card from there but often it is not a convenient time for a
server reboot. I also avoid it because it is so complicated and one wrong
command can lose all of the data in the server. Yes there are backups, which I
would really rather not have to restore.
I needed to add a couple of disks on the fly and did not want to reboot. The
command line I seemed to need and response it gave me was:
Not a very reassuring response. Configured it how with what? It would be nice
if it said "Added virtual disk number 4 as a RAID 0" since that is what that
command told it to do.
Using the command:
/opt/MegaRAID/MegaCli/MegaCli -LDInfo -Lall -aALL
I was able to verify that it had in fact created virtual disk number 4 as a
RAID 0. However, I didn't have a file to work with in /dev representing the
disk. The operating system simply refused to see the disk so that I could
actually do something with it. I spent some time trying to figure out why but
couldn't come up with a solution. Eventually I just had to reboot and my whole
investment in hot-swap chassis and RAID card went out the window.
CentOS-devel mailing list
04-06-2011, 10:47 AM
Cent OS 5.5 Clustering and Support
On 04/06/2011 11:43 AM, Tracy Reed wrote:
> On Fri, Apr 01, 2011 at 08:20:29PM +0530, Kumar, Ranjan spake thusly:
>> We are a Channel product team within LSI and we are trying to add Cent OS 5.5
> MegaCLI is completely unacceptable and the reason why I refuse to buy LSI.
That is irrelevant to this list, take it elsewhere please.
CentOS-devel mailing list