Josh, Unfortunately, no, LOFS is not what I need. I wanted to give full control of an existing dataset to a zone. We need this when we're testing databases, for example. We keep the database files in a separate ZFS dataset and then snapshot/clone the DB dataset into the development machine. Right now, the process is very much manual. We wanted to automate it via the JSON used by vmadm create script.
On 2 March 2015 at 11:36, Josh Wilsdon <[email protected]> wrote: > > I'd like to mount a dataset that has existing data. And the data is to be >> managed under different policies from the Zone data, for snapshotting as >> well as access. >> >> I am even considering whether to have it on a separate pool rather than >> the zones pool. >> > > > If you're wanting to do most of the work on this from the GZ and limit > access inside the zone, what about mounting the dataset in the GZ and using > a lofs mount and a filesystems section in your payload when mounting this > in? > > If you mount it at /zones/delegated/fileserver in your GZ (to use your > example) and you then use a filesystems entry like: > > "filesystems": [ > { > "source": "/zones/delegated/fileserver", > "target": "/fileserver", > "type": "lofs", > "options": [ > "nodevices" > ] > } > > does that do what you want? > > Thanks, > Josh > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
