Just so that there is no confusion, let's use beadm'ing instead of LU'ing.


On 02/ 5/10 02:18 AM, Michael Ramchand wrote:
> Based on my experience of LUing, I totally agree that this is a 
> necessary thing to do.
>
> I'm not completely sure that I would mount things under /var/shared 
> and then symlink them.
>
> I like the idea of each /var dir being a dataset.
>
> I also like the idea of LU being able to decide which to "share" and 
> which to "clone".
We are not going to provide the ability for the users to decide which to 
share or not.  This is going to be fixed.
>
> You suggested method of having a /var/shared dataset and having all 
> "shared" datasets underneath that is great, the only change I'd 
> suggest is to NOT symlink, but simply set mountpoint=/var/<blah> . zfs 
> list will make it clear what is "shared" or not.
Yup..that's reasonable.
>
> I'm slightly concerned that using the zfs heirarchy as a mechanism for 
> LU to know what to or not to propagate might be too restrictive, or 
> possibly require too much up front planning. Are there any good reason 
> why we shouldn't have an LU specific file in the /etc/lu dir where we 
> can define/modify per /var dataset what we want to do with it?
>
> I'm happy either way, it's just that the 2nd one seems a little more 
> flexible, though possibly more prone to user error.

Thanks for the feedback.

-Sanjay

>
> Mike
>
> On 05/02/2010 08:05, sanjay nadkarni (Laptop) wrote:
>>
>> Salutations!!
>>
>> As part of  Solaris Next I am proposing the following changes to /var 
>> hierarchy to avoid system amnesia across multiple Boot Environments.  
>> I would appreciate your feedback on caiman-discuss at opensolaris.org.
>>
>> -Sanjay
>>
>>
>> _______________________________________________
>> caiman-discuss mailing list
>> caiman-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>    
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20100205/8df9a21e/attachment.html>

Reply via email to