BRRABill's Field Report With XenServer
-
Something else I found today, that could use some explaining when someone has time...
I added a server to a pool. But it turns out that if you remove a server from a pool, it deletes all the local storage. What is the reasoning behind that?
-
So you have 2 servers in a Xen Pool, and if you remove one, it wipes the pool?
Without looking into it to much it sounds just like shared storage, and for a single host to know what it has it has to clear the storage and rescan it.
-
@BRRABill said:
I added a server to a pool. But it turns out that if you remove a server from a pool, it deletes all the local storage. What is the reasoning behind that?
It's a decom process, they automate that step as the assumption is that the device is being scrapped. I'm not sure that I agree with the automation, but there is logic behind it.
Why are you removing systems from the pool if you want them to maintain their local storage?
-
@DustinB3403 said:
So you have 2 servers in a Xen Pool, and if you remove one, it wipes the pool?
No, it only wipes local.
-
The idea is that anything that got put onto a machine in a pool belongs to the pool, not the machine. If a machine is removed from a pool it should not get to take pool data with it when it goes. It's a security mechanism.
-
I moved it into a pool last night when I was playing around with my TWO XS boxes. (TWO now! Though one is just my test box.)
I had this idea, that I could move my XO install from the test machine to the production machine. But in XC, there is no move option, just migrate, and the new XS server I set up is not an option.
So I thought, maybe the VM needs to be off, which does give a MOVE option, but it still does not list the new XS.
So I thought (without reading or asking ... always dumb) that perhaps they needed to be in a pool. And that's how I got where I got.
Can you move a VM from one standalone XS to another?
-
-
@scottalanmiller said:
@BRRABill said:
Can you move a VM from one standalone XS to another?
Export and import.
But you can do it in XO, right?
-
@BRRABill said:
But you can do it in XO, right?
Or does "COPY THE VM" mean something other than what I am thinking?
I see there is also a "MIGRATE" option in XO that has my new server as an option.
Silly question ... could I use XO to migrate the VM that XO is running on? Or would that implode the universe?
-
@BRRABill said:
@BRRABill said:
But you can do it in XO, right?
Or does "COPY THE VM" mean something other than what I am thinking?
I see there is also a "MIGRATE" option in XO that has my new server as an option.
Silly question ... could I use XO to migrate the VM that XO is running on? Or would that implode the universe?
puts on full body armor
I don't know... try it and let us know the results...
-
@dafyre said:
puts on full body armor
I don't know... try it and let us know the results...
Haha...first I want to know if "COPY" and "MIGRATE" the VM do what I think they do.
I know it seems like a silly question, but I don't think it is.
-
@BRRABill said:
@BRRABill said:
But you can do it in XO, right?
Or does "COPY THE VM" mean something other than what I am thinking?
I see there is also a "MIGRATE" option in XO that has my new server as an option.
Silly question ... could I use XO to migrate the VM that XO is running on? Or would that implode the universe?
I don't see why it would cause any huge issue, maybe some switch/routing tables get confused for a bit. I agree with @dafyre, try it out.
You thinking of testing HA?
-
@travisdh1 said:
You thinking of testing HA?
No, just pushing all the bells and whistles before this server goes into production.
I'm the guy who presses the button below the "DON'T PRESS THIS BUTTON" sign.
-
@BRRABill said:
@travisdh1 said:
You thinking of testing HA?
No, just pushing all the bells and whistles before this server goes into production.
I'm the guy who presses the button below the "DON'T PRESS THIS BUTTON" sign.
I thought that was the point of a "DON'T PRESS THIS BUTTON" sign, to make it even more tempting to press the button.
-
Result:
"Migrate failed for unknown reason"
Next test is to see if I can migrate the non-XO VMs. Perhaps it is just me.
-
@BRRABill said:
Result:
"Migrate failed for unknown reason"
Next test is to see if I can migrate the non-XO VMs. Perhaps it is just me.
I had a similar error when trying to build a new VM in XO yesterday - I found I picked the wrong network... but XO just failed for unknown reason. XC actually told me bad NIC choice.
-
@Dashrender Here's a related XO issue on GH.
-
@Danp said:
@Dashrender Here's a related XO issue on GH.
I'm not sure if that is my issue.
I wonder if you can migrate from one standalone XS to another standalone. I am checking with @scottalanmiller on that one and will report back.
-
@BRRABill said:
I wonder if you can migrate from one standalone XS to another standalone. I am checking with @scottalanmiller on that one and will report back.
I can answer that for you. Yes, you can migrate between hosts in separate pools (technically, a lone XS is in it's own pool).
-
@Danp said:
@Dashrender Here's a related XO issue on GH.
Oh my issue had nothing to do with XenMotion - I was simply building a new VM - there were (are) a ton of network options.
Time to learn what they all mean.
