Hi Brian, thanks for the info.  It would be a really cool feature to have
MooseFS along with NFS on XCP.  For now, I can mount the moosefs shares on
the master and metalogger servers and share them with unfs3, and through
XenCenter I can import with NFS.  For now, I'll play around with it more.
 Thanks again!

Edward


On Tue, Dec 18, 2012 at 11:17 AM, Brian Menges <[email protected]> wrote:

>  Edward,****
>
> ** **
>
> You can create SRs out of physical media, or remote block IO devs exposed
> under things like iscsi, etc.****
>
> ** **
>
> Depending on how your device shows up, you should be able to. However, if
> it is just a remote file system mount no. It would have to be a block of
> some type to my knowledge.****
>
> ** **
>
> Related commands can be found at the following:****
>
> http://support.citrix.com/article/CTX121896/****
>
> http://support.citrix.com/article/CTX121313****
>
> ** **
>
> These articles may be old, but they’re still very relevant.****
>
> ** **
>
> - Brian Menges****
>
> Principal Engineer, DevOps****
>
> GoGrid | ServePath | ColoServe | UpStream Networks****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Edward Ronquillo
> *Sent:* Tuesday, December 18, 2012 05:56
> *To:* [email protected]
> *Subject:* [Xen-API] Creating an SR from an already mounted moosefs share*
> ***
>
> ** **
>
> Hi, I'm currently running XCP 1.6, and it has been running quite nicely.**
> **
>
> Recently,  I had created a moosefs mount on the XCP host****
>
> e.g. /media/mfs.****
>
> ** **
>
> Is it possible to create a SR that makes use of that directory I whose
> moosefs share I had mounted?****
>
> ------------------------------
> The information contained in this message, and any attachments, may
> contain confidential and legally privileged material. It is solely for the
> use of the person or entity to which it is addressed. Any review,
> retransmission, dissemination, or action taken in reliance upon this
> information by persons or entities other than the intended recipient is
> prohibited. If you receive this in error, please contact the sender and
> delete the material from any computer.
>
> _______________________________________________
> Xen-api mailing list
> [email protected]
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
>
>
_______________________________________________
Xen-api mailing list
[email protected]
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Reply via email to