BRRABill's Field Report With XenServer
-
@DustinB3403 said
I'm glad that it worked for you, but I would refrain from doing it. Use XO to apply the patches (I know you said you would). It's elegant enough to not break things.
If the server needs a reboot after a patch, is XO elegant enough to handle that as well?
It never seems to need a reboot, and yet when you install through XC it almost always does.
-
It should handle the restarting.
Should...
-
@DustinB3403 said
It should handle the restarting.
Should...
Has yours ever restarted?
For example, I ran the last two updates just now for 6.5.
Through XC, each update required a reboot. I do not think XO rebooted the server.
Perhaps this is a @olivier question.
Because the updating in XO is so good. -
The last 2 updates for XS dont require reboots, just a restart of the xapi iirc from a couple weeks ago.
If they were the updates for ssl fixes and the one for gpus, that is. Teh other updates that are rollups of 2 or more updates do require restarts usually. -
@momurda said
The last 2 updates for XS dont require reboots, just a restart of the xapi iirc from a couple weeks ago.
If they were the updates for ssl fixes and the one for gpus, that is. Teh other updates that are rollups of 2 or more updates do require restarts usually.Both of them required restarts through XC Neither did through XO. That is what I am trying to get to the bottom of.
-
Hi there!
Let me recap the thing and put it in perspective.
The couple XenServer/XenCenter is targeting mainly Windows admins (thus the Windows client, the SP1 and so forth patching etc). You know, things that seems a bit strange inside the Linux world. It was really something wanted from Citrix to not "scare" their Windows public (have you ever seen the word "Linux" somewhere on XenServer/XenCenter?).
In this fabulous Windows world, you have to reboot very often for a lot of reasons.
Now, let's get to the point: XenServer updates are a kind of ugly tarball containing RPM packages (+ scripts) which are extracted on the host. In the patch metadata, there is a "recommendation" field, which gives you what to do after applying a patch. Roughly:
- if it's a lib or updated scripts: no reboot needed at all
- if it's kernel or hypervisor related: it will be used only after a reboot
But in all cases, there is no problem to install all patches at once, and do a reboot at the end. The missing info in XO is to display the recommandation field, which is now the case in the 5.0 interface.
So why on earth XenCenter will reboot your host 15 times? Even sometimes without asking you? I think that's really a bad behavior. It's up to you to decide.
-
@olivier said in BRRABill's Field Report With XenServer:
So why on earth XenCenter will reboot your host 15 times? Even sometimes without asking you? I think that's really a bad behavior. It's up to you to decide.
Simplified: Why would you run XenCenter?
-
@scottalanmiller said
Simplified: Why would you run XenCenter?
I started out on XC, but now do everything on XO.
I was just wondering why there were always reboots on one, and never on the other.
So it sounds like when 5 comes out, it'll tell you you need a reboot.
It's definitely different than the Windows world. It's interesting to know you can install update on top of update, and THEN just reboot.
-
@scottalanmiller said
Simplified: Why would you run XenCenter?
And aren't you a XC evangelist for the Windows folk? LOL.
-
@BRRABill said in BRRABill's Field Report With XenServer:
it'll tell you you need a reboot.
It won't tell you anything, it will display the recommendation for each patch.
-
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said
Simplified: Why would you run XenCenter?
And aren't you a XC evangelist for the Windows folk? LOL.
Scott has always recommended using XenServer or Hyper-V over ESXi due to the business model. I think his gripe with XenCenter was the limited functionality prior to it being wide open.
But with XO there is very little need for XC any more.
I find XC is easier to manage a VM at times, just because of how I use my system.
-
@olivier said i
It won't tell you anything, it will display the recommendation for each patch.
Hey when XO displays, I listen.
-
@BRRABill ahahah
-
I guess Windows works the same way, but I've always been fearful not rebooting pretty quickly would lead to serious system problems.
Though I am guessing that rebooting pretty quickly after applying patches that require rebooting on XS is probably prudent. Still, I could install during the day and just reboot it at night.
-
@BRRABill said in BRRABill's Field Report With XenServer:
I guess Windows works the same way, but I've always been fearful not rebooting pretty quickly would lead to serious system problems.
Though I am guessing that rebooting pretty quickly after applying patches that require rebooting on XS is probably prudent. Still, I could install during the day and just reboot it at night.
It's not really stability issues, it's that the updates don't take effect until you reboot.
-
I happened to notice in XO the following...
(xo-web 4.16.1 - xo-server 4.17.0)
Should those be the same? I was pretty sure they were both the same the other day when I upgraded them.
-
@BRRABill No, they can vary depending on the release schedule. My production server is currently
(xo-web 4.16.0 - xo-server 4.17.0) -
@Danp said in BRRABill's Field Report With XenServer:
@BRRABill No, they can vary depending on the release schedule. My production server is currently
(xo-web 4.16.0 - xo-server 4.17.0)OK, I am set, then!
Also upgraded one server (of two) to XS7 tonight.
-
@BRRABill said in BRRABill's Field Report With XenServer:
Also upgraded one server (of two) to XS7 tonight.
Just remember that migration from XS6 to XS7 is a one way operation.
-
@Danp said
Just remember that migration from XS6 to XS7 is a one way operation.
Why would one ever want to go back?
