XenServer 7.0: monitor hard drive failure
-
It's fine, more XS knowledge is a good thing!
-
@BRRABill said in XenServer 7.0: monitor hard drive failure:
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
@BRRABill said in XenServer 7.0: monitor hard drive failure:
http://discussions.citrix.com/topic/378701-dell-openmanage-in-xenserver-7/
Yup, looks like the right procedure. That's exactly how XenServer is supposed to be used.
So they said about everything.
I mean, you always say about how XS works as long as your don't do anything advanced. You wouldn't qualify that procedure as advanced?
Installing basic tools? No, it's pretty rudimentary.
ML should whip up some how tos that are clearer than that one. There are better ways to handle the setup instructions. But the basic installation is:
- Add repo
- Install tool
- Configure where to send alerts
Then it is self maintaining along with the rest of the system. The other option is... just let it fail. This is the same super basic "how you monitor any hardware". No different than basic setup with VMware, Hyper-V, Linux on bare metal, Windows on bare metal, etc.
-
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
@BRRABill said in XenServer 7.0: monitor hard drive failure:
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
@BRRABill said in XenServer 7.0: monitor hard drive failure:
http://discussions.citrix.com/topic/378701-dell-openmanage-in-xenserver-7/
Yup, looks like the right procedure. That's exactly how XenServer is supposed to be used.
So they said about everything.
I mean, you always say about how XS works as long as your don't do anything advanced. You wouldn't qualify that procedure as advanced?
Installing basic tools? No, it's pretty rudimentary.
ML should whip up some how tos that are clearer than that one. There are better ways to handle the setup instructions. But the basic installation is:
- Add repo
- Install tool
- Configure where to send alerts
Then it is self maintaining along with the rest of the system. The other option is... just let it fail. This is the same super basic "how you monitor any hardware". No different than basic setup with VMware, Hyper-V, Linux on bare metal, Windows on bare metal, etc.
When I read through that post, there were comments about how you had to be careful because you didn't want to update CentOS stuff that would break XS. That's the kind of thing that confuses me.
Like, should you revert all the changes you make to the repos to get it to work?
-
@BRRABill said in XenServer 7.0: monitor hard drive failure:
Like, should you revert all the changes you make to the repos to get it to work?
No, that guy was confused
-
@BRRABill said in XenServer 7.0: monitor hard drive failure:
When I read through that post, there were comments about how you had to be careful because you didn't want to update CentOS stuff that would break XS. That's the kind of thing that confuses me.
Dell's repos do not update the CentOS OS. He's right, don't update that stuff. He's wrong to associate it with this task.
-
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
@BRRABill said in XenServer 7.0: monitor hard drive failure:
When I read through that post, there were comments about how you had to be careful because you didn't want to update CentOS stuff that would break XS. That's the kind of thing that confuses me.
Dell's repos do not update the CentOS OS. He's right, don't update that stuff. He's wrong to associate it with this task.
It was the two comments in the middle.
This one:
"I believe that if you modify, or "hack", the underlying operating system in any way you are technically voiding any warranty. So, is it safe? Probably not. That being said. What I did above was tell yum where to find the files for that repo that was already there. I also did not enable the repo permanently but used the --enablerepo parameter so it would only be used for this one command. Openmanage just needed a few packages from the Centos base repo to install so I made them available.I have not added any other repositories to XenServer so I don't know what affect it will have on the server. If you did install the repo I am not sure it would even work without doing some similar modification to the epel baseurl or mirrorlist. I also don't know if, during the install of some other software, the repo would pull in packages that replace important files used by XenServer. In short, if you are not very careful about the packages you allow to install you may end up with a broken system.
Others may have more experience with other repos on XenServer."
and this one
"These main problems may come about :
-
doing a gratuitous "yum upgrade -y" and getting too many packages out of synch with the xenserver sepecific ones.
-
XS65 specific because centos5 is rather old - trying to find "bridging" packages that are compiled for centos5 but new enough to provide the support required. salt-minion and python under xenserver 6.5 are first to mind.
-
kludge software raid underneath xenserver. The installer won't see this and will merrily wipe out your entire install."
-
-
@scottalanmiller maybe worth a fork?
-
@BRRABill said in XenServer 7.0: monitor hard drive failure:
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
@BRRABill said in XenServer 7.0: monitor hard drive failure:
When I read through that post, there were comments about how you had to be careful because you didn't want to update CentOS stuff that would break XS. That's the kind of thing that confuses me.
Dell's repos do not update the CentOS OS. He's right, don't update that stuff. He's wrong to associate it with this task.
It was the two comments in the middle.
This one:
"I believe that if you modify, or "hack", the underlying operating system in any way you are technically voiding any warranty. So, is it safe? Probably not. That being said. What I did above was tell yum where to find the files for that repo that was already there. I also did not enable the repo permanently but used the --enablerepo parameter so it would only be used for this one command. Openmanage just needed a few packages from the Centos base repo to install so I made them available.I have not added any other repositories to XenServer so I don't know what affect it will have on the server. If you did install the repo I am not sure it would even work without doing some similar modification to the epel baseurl or mirrorlist. I also don't know if, during the install of some other software, the repo would pull in packages that replace important files used by XenServer. In short, if you are not very careful about the packages you allow to install you may end up with a broken system.
Others may have more experience with other repos on XenServer."
and this one
"These main problems may come about :
-
doing a gratuitous "yum upgrade -y" and getting too many packages out of synch with the xenserver sepecific ones.
-
XS65 specific because centos5 is rather old - trying to find "bridging" packages that are compiled for centos5 but new enough to provide the support required. salt-minion and python under xenserver 6.5 are first to mind.
-
kludge software raid underneath xenserver. The installer won't see this and will merrily wipe out your entire install."
Yup, that's the one I mean by confused. It's not modifying or hacking the system, at ALL. It's not a kludge. It's installing proper software exactly as designed. It's the Linux equivalent of "double clicking the install icon". Do you call it "modifying the OS or hacking" anytime you install Notepad++ on Windows?
-
-
This is a guy who managed to get a basic install but doesn't understand what he's doing so is making really ridiculous statements. If you read what he writes, he's very clearly lost.
Not sure why he mentions software RAID because the entire point of this is to properly use the hardware RAID.
-
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
This is a guy who managed to get a basic install but doesn't understand what he's doing so is making really ridiculous statements. If you read what he writes, he's very clearly lost.
It's statements like this that totally kill me - doesn't understand what he's doing. it's Clear to you, a 20+ year veteran of Linux, but to someone like Bill and I, we have no idea, because we are even more clueless about Linux than the poster.
-
@Dashrender said in XenServer 7.0: monitor hard drive failure:
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
This is a guy who managed to get a basic install but doesn't understand what he's doing so is making really ridiculous statements. If you read what he writes, he's very clearly lost.
It's statements like this that totally kill me - doesn't understand what he's doing. it's Clear to you, a 20+ year veteran of Linux, but to someone like Bill and I, we have no idea, because we are even more clueless about Linux than the poster.
I want to keep posting on this.
This confuses me like the Hyper-V issue. But even more so since I do not understand Linux.
Like for example, should I be updating XS (or CentOS) from the CLI?
A primer type writeup from an expert would be awesome here.
-
The question that comes to mind is, if we make this change/install this software into XS itself on DOM0, what happens when it's time to upgrade? Will it work? or will it break?
I guess that someone will come back at me - well, don't you ask the same question when you upgrade anything else?
Why would XS be any different than ESXi? if you install an add-on to ESXi, there's no telling if it will work when ESXi is upgraded, so you're in the same boat.
-
@BRRABill said in XenServer 7.0: monitor hard drive failure:
@scottalanmiller said in XenServer 7.0: monitor hard drive failure:
@BRRABill said in XenServer 7.0: monitor hard drive failure:
@scottalanmiller they have dropped support for that, I think. ALso, would you really be comfortable installing that on XS? You know the first rule of XS!
Installing the hardware montitoring on the Dom0? Yes, that is what it's purposeis.
Shivers....
I know, but the one server at both sites here is doing just that. Dom0 has the RAID card driver installed. Easy command line checks of the RAID status.... my 360k upload connection can at least forward text quick.
-
@travisdh1 said in XenServer 7.0: monitor hard drive failure:
I know, but the one server at both sites here is doing just that. Dom0 has the RAID card driver installed. Easy command line checks of the RAID status.... my 360k upload connection can at least forward text quick.
Dell or non Dell hardware?
Is the message forwarding automated so that when you are on the beach like @BRRABill everything is all good? -
@Dashrender said in XenServer 7.0: monitor hard drive failure:
The question that comes to mind is, if we make this change/install this software into XS itself on DOM0, what happens when it's time to upgrade? Will it work? or will it break?
I guess that someone will come back at me - well, don't you ask the same question when you upgrade anything else?
Why would XS be any different than ESXi? if you install an add-on to ESXi, there's no telling if it will work when ESXi is upgraded, so you're in the same boat.
Exactly. This is just a normal package like anything else. And CentOS is built to not break packages like no other system ever (outside of things like AIX and mainframes.)
-
Since the Dell fanboi's hijacked this thread (jk
) I'm going to start another thread.
Actually have some good info for those of us non-Dell users.
I use SuperMIcro. -
@FATeknollogee said in XenServer 7.0: monitor hard drive failure:
Since the Dell fanboi's hijacked this thread (jk
) I'm going to start another thread.
Actually have some good info for those of us non-Dell users.
I use SuperMIcro.Is there anything about Dell on here? Dell was mentioned, but nothing Dell specific was said. All of the info applies to SuperMicro as well. IPMI is used instead of iDRAC. And the PERC software and the LSI MegaRAID software is the same. Only difference is branding.
