XOA Pricing Model - What might it look like from a US perspective
-
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
There's also HA-Lizard.
That's true, totally forgot about that one. (and I even deployed it)
-
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
There's also HA-Lizard.
That's true, totally forgot about that one. (and I even deployed it)
Didn't it blow up on you? That's also limited to two nodes. And fairly susceptible to split brain.
-
What you don't get with HA-Lizard is the SPoG
It's only the HA functionality, which you could get the SPoG from XO (not XOA) for free.
-
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
There's also HA-Lizard.
That's true, totally forgot about that one. (and I even deployed it)
Didn't it blow up on you? That's also limited to two nodes. And fairly susceptible to split brain.
It did, because my boss was far to cheap to pay for a proper setup and I flat out let him know before deploying it that I hadn't used it/tested it ever and if he wanted to go that route that he had better be getting support for it. Which he refused to do, but when it blew up he paid for emergency support and the support was awesome.
Fortunately I had good backups of everything and was able to recover.
-
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
That's also limited to two nodes. And fairly susceptible to split brain.
Is it? I know it supports 2-node deployments, but didn't realize it was limited to 2 nodes.
-
If I recall correctly XOSAN uses the same mechanism to connect the systems and there were some major concerns about split-brain issues.
-
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
That's also limited to two nodes. And fairly susceptible to split brain.
Is it? I know it supports 2-node deployments, but didn't realize it was limited to 2 nodes.
Found the answer here:
When running HA-Lizard there are no restrictions on how many hosts are part of the pool. So, in your example a 3-node pool is fully supported.
-
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@BRRABill said in 5Nine Free Hyper-V Manager No Long Available:
@scottalanmiller said in 5Nine Free Hyper-V Manager No Long Available:
@DustinB3403 said in 5Nine Free Hyper-V Manager No Long Available:
Flat out saying it "cost to much to take your money" is literally turning customers away.
It is, but it is also turning away small customers that might not be profitable and what they have to consider is the risk that this poses to bigger customers. I don't agree with the approach, but they have sound logic for why they do what they do. All customers are not good customers.
If I remember the conversation correctly (we went through all of this with @olivier on a ML thread) that was the crux of it, that it cost too much to support the smaller clients, since they don't have that many people.
The issue that I have with this is that if you have the staff to support XS, why would you need olivier to support it? Olivier's job would stop at XOA (unless it was an XOSAN) installation.
Which if the goal is to support XS and XOSAN than the pricing model still doesn't make sense as there are other products that do what XOSAN does and are further along in development.
Uh what other VSAs are there for XenServer?
DRBD and Starwind, for example. DRBD is not VSA, it's just RLS. You don't actually want VSA if you can help it. Starwind is VSA as a fallback. On Hyper-V, it's not a VSA, it's native.
-
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
That's also limited to two nodes. And fairly susceptible to split brain.
Is it? I know it supports 2-node deployments, but didn't realize it was limited to 2 nodes.
Sorry. With local it's two nodes. With iscsi you can do more.
-
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
What you don't get with HA-Lizard is the SPoG
Took me a few minutes to figure that one out. Kept thinking "single point of" something.
-
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates If by VSA you mean Virtual SAN Appliance there is Starwind. (having a brain fart)
That requires separate windows servers. There isn't really anything that competes with XOSAN for XenServer at all.
By definition, a VSA always requires a VM of some sort. Starwind's Xen VSA that doesn't use Windows is coming. It's publicly announced.
-
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
There's also HA-Lizard.
That's just DRBD. It's not RLS itself and not VSA at all.
-
@scottalanmiller said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates If by VSA you mean Virtual SAN Appliance there is Starwind. (having a brain fart)
That requires separate windows servers. There isn't really anything that competes with XOSAN for XenServer at all.
By definition, a VSA always requires a VM of some sort. Starwind's Xen VSA that doesn't use Windows is coming. It's publicly announced.
Ya. I meant right now physically separate Windows systems.
-
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
That's also limited to two nodes. And fairly susceptible to split brain.
Is it? I know it supports 2-node deployments, but didn't realize it was limited to 2 nodes.
DRBD is inherently a two node system. It's RAID 1 only. You CAN do more nodes with it, but they would be RAID 1 so the scaling would be terrible unless you manually segmented the storage, which you could do.
-
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
What you don't get with HA-Lizard is the SPoG
Took me a few minutes to figure that one out. Kept thinking "single point of" something.
I still don't know what it is.
-
@scottalanmiller said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@BRRABill said in 5Nine Free Hyper-V Manager No Long Available:
@scottalanmiller said in 5Nine Free Hyper-V Manager No Long Available:
@DustinB3403 said in 5Nine Free Hyper-V Manager No Long Available:
Flat out saying it "cost to much to take your money" is literally turning customers away.
It is, but it is also turning away small customers that might not be profitable and what they have to consider is the risk that this poses to bigger customers. I don't agree with the approach, but they have sound logic for why they do what they do. All customers are not good customers.
If I remember the conversation correctly (we went through all of this with @olivier on a ML thread) that was the crux of it, that it cost too much to support the smaller clients, since they don't have that many people.
The issue that I have with this is that if you have the staff to support XS, why would you need olivier to support it? Olivier's job would stop at XOA (unless it was an XOSAN) installation.
Which if the goal is to support XS and XOSAN than the pricing model still doesn't make sense as there are other products that do what XOSAN does and are further along in development.
Uh what other VSAs are there for XenServer?
DRBD and Starwind, for example. DRBD is not VSA, it's just RLS. You don't actually want VSA if you can help it. Starwind is VSA as a fallback. On Hyper-V, it's not a VSA, it's native.
That's kind of what I was getting at. There isn't a solution that's as easy to deploy as XO for this. Small shops most likely won't have the time spent to manage a DRBD setup, esp if something goes wrong.
-
@scottalanmiller Single Pane of Glass
-
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@scottalanmiller said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@BRRABill said in 5Nine Free Hyper-V Manager No Long Available:
@scottalanmiller said in 5Nine Free Hyper-V Manager No Long Available:
@DustinB3403 said in 5Nine Free Hyper-V Manager No Long Available:
Flat out saying it "cost to much to take your money" is literally turning customers away.
It is, but it is also turning away small customers that might not be profitable and what they have to consider is the risk that this poses to bigger customers. I don't agree with the approach, but they have sound logic for why they do what they do. All customers are not good customers.
If I remember the conversation correctly (we went through all of this with @olivier on a ML thread) that was the crux of it, that it cost too much to support the smaller clients, since they don't have that many people.
The issue that I have with this is that if you have the staff to support XS, why would you need olivier to support it? Olivier's job would stop at XOA (unless it was an XOSAN) installation.
Which if the goal is to support XS and XOSAN than the pricing model still doesn't make sense as there are other products that do what XOSAN does and are further along in development.
Uh what other VSAs are there for XenServer?
DRBD and Starwind, for example. DRBD is not VSA, it's just RLS. You don't actually want VSA if you can help it. Starwind is VSA as a fallback. On Hyper-V, it's not a VSA, it's native.
That's kind of what I was getting at. There isn't a solution that's as easy to deploy as XO for this. Small shops most likely won't have the time spent to manage a DRBD setup, esp if something goes wrong.
Small shops are probably topping at two nodes and using StarWinds for free on Hyper-V.
-
@Danp said in XOA Pricing Model - What might it look like from a US perspective:
@scottalanmiller Single Pane of Glass
OH!
-
@Dashrender said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@scottalanmiller said in XOA Pricing Model - What might it look like from a US perspective:
@stacksofplates said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@BRRABill said in 5Nine Free Hyper-V Manager No Long Available:
@scottalanmiller said in 5Nine Free Hyper-V Manager No Long Available:
@DustinB3403 said in 5Nine Free Hyper-V Manager No Long Available:
Flat out saying it "cost to much to take your money" is literally turning customers away.
It is, but it is also turning away small customers that might not be profitable and what they have to consider is the risk that this poses to bigger customers. I don't agree with the approach, but they have sound logic for why they do what they do. All customers are not good customers.
If I remember the conversation correctly (we went through all of this with @olivier on a ML thread) that was the crux of it, that it cost too much to support the smaller clients, since they don't have that many people.
The issue that I have with this is that if you have the staff to support XS, why would you need olivier to support it? Olivier's job would stop at XOA (unless it was an XOSAN) installation.
Which if the goal is to support XS and XOSAN than the pricing model still doesn't make sense as there are other products that do what XOSAN does and are further along in development.
Uh what other VSAs are there for XenServer?
DRBD and Starwind, for example. DRBD is not VSA, it's just RLS. You don't actually want VSA if you can help it. Starwind is VSA as a fallback. On Hyper-V, it's not a VSA, it's native.
That's kind of what I was getting at. There isn't a solution that's as easy to deploy as XO for this. Small shops most likely won't have the time spent to manage a DRBD setup, esp if something goes wrong.
Small shops are probably topping at two nodes and using StarWinds for free on Hyper-V.
Starwinds is always free, no node limit. Just in case anyone thought that that was implied.
