<div dir="ltr"><div><div><div>Any help?<br><br></div>It will be very useful for me if somebody can comment on this.<br><br></div>Thanks<br></div>Nobin<br><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 23, 2015 at 9:22 AM, Cloud Fundoo <span dir="ltr"><<a href="mailto:cloudfundoo@gmail.com" target="_blank">cloudfundoo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi All,<br><br></div>I am evaluating GlusterFS for one of our requirement. <br><br></div>My system is a chassis based system with multiple blade cards, where each blade card has one, two or more storage disks. <br><br></div><div>These blades are also compute blades (application runs on the same card).<br><br></div><div>Users can unconfigure those storage disk, can take out and place in other chassis (say admin).<br><br></div><div>Because of this action from admin, we will end up in varying configuration of gluster configuration, there no fixed gluster configuration for long.<br><br></div><div>Basically when admin unconfigure/configure disk to system, it will result in brick addition/removal of bricks from volume.<br><br></div><div>So my question is can we enable striping on the volume?, from my initial understanding this is not possible.<br><br></div><div>Is there any alternate to striping which can be enabled for this configuration?<br><br></div><div>Or GlusterFS is suitable for this use case?<br><br><br></div><div>Thanks,<br></div><div>Cloudy.<br></div><div><br></div><div><br></div><div><br></div><div><br></div><br><div><div><br><br></div></div></div>
</blockquote></div><br></div></div></div></div></div></div>