Having tested some combinations of iSCSI targets and clients I know
that it can sometimes be a nightmare to get iSCSI to work. I never
took the time to read the over 200 pages iSCSI spec in order to find
out what's the cause of this mess.
What's the state of ATAoE? I read the spec and well - it is simple.
But does it sufficiently describe all that's needed to get different
ATAoE targets / clients to work seamlessly together?
Are there any known compatibility issues on the AoE landscape: will a
Coraid appliance behave/respond exactly the same to clients than a
What is Coraid's commitment on making changes/enhancements to the
ATAoE spec public?
Thanks again for any information.
From: Sam Hopkins <sah@co...> - 2008-06-12 15:03:42
Questions about coraid are best suited to support@... as this is
simply a community forum where some of us coraiders hang out. I'll
respond here, but let's be sure to keep the aoetools list from becoming
a place to discuss coraid.
> What's the state of ATAoE? I read the spec and well - it is simple.
> But does it sufficiently describe all that's needed to get different
> ATAoE targets / clients to work seamlessly together?
As far as we know, it does, from a developer's point of view. As a user
you'd likely be best served reading documentation on how to use the
tools built to utilize the protocol than you would be analyzing the protocol
itself. That being said, maybe you'll want to look at packet traces to, eg,
track i/o patterns. In that case knowing what goes into the packets
can be helpful.
> Are there any known compatibility issues on the AoE landscape: will a
> Coraid appliance behave/respond exactly the same to clients than a
> vblade target?
There are performance differences, obviously, but as far as the aoe
protocol goes there should be no difference. Vblade was written to
serve as an example aoe target implementation for developers wanting
to make targets and as a freely available aoe target for users to
become comfortable with aoe. Many of our customers started with
vblade installations, outgrew them, and came to us for faster/bigger
> What is Coraid's commitment on making changes/enhancements to the
> ATAoE spec public?
We haven't made any fundamental changes to the protocol in quite a
while. The last minor change was updating the config-query response
so the target could report its max sector request count for using
jumbo frames. When we do find it necessary to make a change, though,
we immediately update the protocol document. We respect the openness
needed to participate in the open source community.
We've occasionally come up with aoe vendor extensions that aren't in
the aoe protocol document because they don't belong there. One is the
mac mask command (documented in aoemask from the SR support page).
Anyone can define vendor extensions, though; that's why we reserved
the command space for them.
I hope that helps!