BRRABill's Field Report With XenServer
-
-
Thin provisioning?
-
-
you have to refresh. Refresh doesn't happen automatically.
-
@Dashrender said:
you have to refresh. Refresh doesn't happen automatically.
Ah.
What is this? 1973?
-
@BRRABill said:
@Dashrender said:
you have to refresh. Refresh doesn't happen automatically.
Ah.
What is this? 1973?
I kinda asked/thought the same thing. Having to manually fresh, or relaunch the application just seems odd.
-
@Dashrender said:
I kinda asked/thought the same thing. Having to manually fresh, or relaunch the application just seems
oddOLD.FTFY
-
Did refreshing it solve the problem?
-
Yep.
Rescan is actually the word they use.
What does that do exactly, I wonder?
-
@Dashrender said:
Did refreshing it solve the problem?
Did you ever do this through XC?
I could not find the option there.
-
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
-
@scottalanmiller said:
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
No you have to click the "rescan" button or it never does it. At least that is what I am seeing.
-
-
@BRRABill said:
@scottalanmiller said:
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
No you have to click the "rescan" button or it never does it. At least that is what I am seeing.
Ah okay, my guess is because they don't want to incur a storage penalty without everyone being clear that they are about to query the storage. In a small lab with local storage this seems silly, but if this was a massive environment with tons of heavily used remote storage, might be something that you want to carefully control. What if you had a hundred admins with XO open all of the time and a thousand nodes on it with gobs of shared storage all updating automatically... suddenly what seems like a trivial hit becomes crippling.
-
@scottalanmiller said:
@BRRABill said:
@scottalanmiller said:
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
No you have to click the "rescan" button or it never does it. At least that is what I am seeing.
Ah okay, my guess is because they don't want to incur a storage penalty without everyone being clear that they are about to query the storage. In a small lab with local storage this seems silly, but if this was a massive environment with tons of heavily used remote storage, might be something that you want to carefully control. What if you had a hundred admins with XO open all of the time and a thousand nodes on it with gobs of shared storage all updating automatically... suddenly what seems like a trivial hit becomes crippling.
And, again, in a larger environment, seeing storage space in the GUI here is not really the proper way to manage it, correct?
-
@BRRABill said:
And, again, in a larger environment, seeing storage space in the GUI here is not really the proper way to manage it, correct?
Oh I don't know about that, no matter how big the environment is, the virtualization platform administrators are going to need a view into what is going on, at least from their perspective. In a really, REALLY large environment you would be on fully independent shared storage in 99% of cases (think EMC VMAX) with a totally independent storage management team and they would deal with performance, capacity, growth, monitoring, etc. But even then the platform team would need some visibility into what they were using of that storage. So I would expect that XO having that view would remain important, but for slightly curtailed reasons.
-
How does vSphere manage this without the need to do continuous refreshes?
Aren't both XO and vSphere are both centralized server systems that they themselves could maintain an updated status, and the users who are accessing the web server would be stressing the web centralized system, not the storage itself.
-
@Dashrender said:
Aren't both XO and vSphere are both centralized server systems that they themselves could maintain an updated status, and the users who are accessing the web server would be stressing the web centralized system, not the storage itself.
vSphere varies.
XO might be triggering it via the interface which doesn't make that undoable, just less obvious.
-
@scottalanmiller said:
@Dashrender said:
Aren't both XO and vSphere are both centralized server systems that they themselves could maintain an updated status, and the users who are accessing the web server would be stressing the web centralized system, not the storage itself.
vSphere varies.
XO might be triggering it via the interface which doesn't make that undoable, just less obvious.
varies how?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
Aren't both XO and vSphere are both centralized server systems that they themselves could maintain an updated status, and the users who are accessing the web server would be stressing the web centralized system, not the storage itself.
vSphere varies.
XO might be triggering it via the interface which doesn't make that undoable, just less obvious.
varies how?
The web client does one thing but the local client has to do another.
