Vpools and v3.0-UPSTREAM LIO
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 23 lines · Ross S. W. Walker
Quoted 11 lines · Jerome Martin
On Thu, Jun 5, 2008 at 5:39 PM, Ross S. W. Walker <[email protected]> wrote:
How about something like "ipool"?
Maybe if I had a better picture of what it is your trying to achieve I can throw some better suggestions out too?
Quoted 9 lines
Well, basically the idea is to have a cluster of machines driven by heartbeatv2 (pacemaker) implementing "storage" and "vhost" roles for arbitrary nodes. The storage part is based on lvm + drbd + lio-target + open/iSCSI + ext3 (ocfs2 planned for v2). The vhost part is based on linux-vservers, with plans to add vmware server in v2 and then maybe xen/openVZ depending on contribs. The term "pool" relates to the fact that the vservers are "pooled" by storage chunks, and the "v" stands for vservers. The effect is "Vserver POOLS".
Quoted 6 lines
How about a "stateless" storage pool where each node knows nothing about any other node in the storage pool.
You have central servers that then organize each node in the pool by available storage, performance of that storage, etc.
Having central servers (and having to worry about the redundancy of said servers) would increase the complexity a great deal I would think.
Quoted 5 lines
The storage is then mapped out based on these
characteristics, redundancy and striping is handled in the mapping, also based on performance characteristics and served up to servers that need it.
Hmmm, so what are the advantages what we have working so far..?
Quoted 18 lines
Quoted 13 lines
An other property of that cluster scheme is that it is designed to work at N+M redundancy (N active, M spares per resource). That could be used for devising a name too.
I'm currently trying to find some acronym based on the software stack used :
- DRBD
- iSCSI (LIO-target, no other target being able to fullfill the project requirements, and either open/iSCSI or core iscsi)
- virtual servers (to stay implementation-agnostic)
- linux-ha / pacemaker (the actual heartbeat part is non-essential, will be replaced by openAIS in v2 I think)Quoted 4 lines
So maybe something like funny combinations like "DIVHA, software that sings" or "PAID, free software" or anything along those lines would work :-) To be honest, I liked "vpools", and don't really have a good idea yet.
Quoted 7 lines
How about DIVA?
This product can be added on to already existing iSCSI infrastructures and provides integrated high-level storage management services that would otherwise require separate products.
Hmm, not bad. I usually have to go for a walk or two to come up with good project names.. :-)
--nab
Quoted 13 lines
-Ross
______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.