On Tue, Nov 18, 2008 at 09:09:07AM -0800, Andre Lue wrote:
> Is the web interface on the appliance available for download or will it make
> it to opensolaris sometime in the near future?
It's not, and it's unlikely to make it to OpenSolaris.
Adam
--
Adam Leventhal, Fishworks
Refering to the web gui or bui seen here
http://blogs.sun.com/brendan/entry/status_dashboard
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Is the web interface on the appliance available for download or will it make it
to opensolaris sometime in the near future?
thanks
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensola
when, but
they're not that far off.
Here's a list of what existing products we're currently targeting in the
near term:
http://www.sun.com/storage/flash/products.jsp
Original Message ----
Subject: Re: [zfs-discuss] Storage 7000
From: Adam Leventhal <[EMAIL PROTECT
> Would be interesting to hear more about how Fishworks differs from
> Opensolaris, what build it is based on, what package mechanism you are
> using (IPS already?), and other differences...
I'm sure these details will be examined in the coming weeks on the blogs
of members of the Fishworks team
Adam Leventhal wrote:
> Yes. The Sun Storage 7000 Series uses the same ZFS that's in OpenSolaris
> today. A pool created on the appliance could potentially be imported on an
> OpenSolaris system; that is, of course, not explicitly supported in the
> service contract.
>
Would be interesting to he
On Mon, Nov 17, 2008 at 2:36 PM, Eric Schrock <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 17, 2008 at 01:38:29PM -0600, Tim wrote:
> >
> > And this passage:
> > "If there is a broken or missing disk, we don't let you proceed without
> > explicit confirmation. The reason we do this is that once the st
On Mon, Nov 17, 2008 at 01:38:29PM -0600, Tim wrote:
>
> And this passage:
> "If there is a broken or missing disk, we don't let you proceed without
> explicit confirmation. The reason we do this is that once the storage pool
> is configured, there is no way to add those disks to the pool without
>
On Mon, Nov 17, 2008 at 1:14 PM, Eric Schrock <[EMAIL PROTECTED]> wrote:
>
>
> Yes, we support adding whole or half JBODs. We do not support adding
> individual disks or arbitrarily populated JBODs. If you want the
> ability to survive JBOD failure ("NSPF" in our storage config terms),
> you mus
On Mon, Nov 17, 2008 at 01:07:12PM -0600, Tim wrote:
>
> So that leads me to my second question then: If I buy a 7410 with a single
> JBOD attached, can I easily attach a second JBOD and grow the pool? It
> would seem the logical answer is "yes", since growing the pool would just
> require addin
>I'm not sure if this is the right place for the question or not, but I'll
>throw it out there anyways. Does anyone know, if you create your pool(s)
>with a system running fishworks, can that pool later be imported by a
>standard solaris system? IE: If for some reason the head running fishworks
On Mon, Nov 17, 2008 at 12:48 PM, Eric Schrock <[EMAIL PROTECTED]> wrote:
> Yes, the on-disk format is compatible. You cannot, however, do the
> reverse. Importing arbitrary Solaris pools (or former Fishworks pools)
> into the Fishworks environment is not supported. While the on-disk
> format i
On Mon, Nov 17, 2008 at 12:35:38PM -0600, Tim wrote:
> I'm not sure if this is the right place for the question or not, but I'll
> throw it out there anyways. Does anyone know, if you create your pool(s)
> with a system running fishworks, can that pool later be imported by a
> standard solaris sys
On Mon, Nov 17, 2008 at 12:35:38PM -0600, Tim wrote:
> I'm not sure if this is the right place for the question or not, but I'll
> throw it out there anyways. Does anyone know, if you create your pool(s)
> with a system running fishworks, can that pool later be imported by a
> standard solaris sys
14 matches
Mail list logo
