On 12/27/14 3:31 , Alex Wilson via smartos-discuss wrote: > I've heard mention that delegated datasets and "reprovisioning" (by this I > mean re-creating the zone with a new template, but the same delegated > dataset) are the "way of the future" -- or at least a good way to handle > upgrades in the long term. It makes good sense to me, and I've already been > taking steps to use it, developing internal templates that keep all their > individualised data on the delegated zfs, and when a new zone starts up, > checking for its presence and using it if already available. > > However, there's no way to use delegated datasets from the SDC CloudAPI at > the moment, and when I asked on IRC, the only answer I got was that there are > no plans to change this. If I want to use delegated datasets and SDC in the > near future then, it seems my only option is to write services that talk > directly to VMAPI, which as I understand it is considered unstable. > > So I have two questions: how unstable is "unstable" with regards to VMAPI in > SDC7? I note the ops portal seems to have support for it already.. does that > mean it's less likely to change? And secondly, are there any dissenting > opinions about the utility of delegated datasets that might be interesting to > hear? Are there concerns / problems with it that are the reason why this > feature has not progressed, or is it just a case of manpower being directed > elsewhere?
Hi Alex, So, let's break this into a few different pieces. The notion of delegated datasets isn't going away or changing. We use them quite heavily as part of SDC itself, and their presence in vmadm is stable. For example, the manatee services use delegated datasets to contain the postgres databases and transmit them around. With that in mind, we also use 'reprovisioning' as you describe to do the upgrades of a lot of our services. So, it's presence in adminui isn't likely to change. The ability to create and manipulate them via VMAPI is unlikely to change, though I can't say at this time if the current interface to that is stable (eg. that the way you manage it won't change, though I'd be surprised if it did). As for why it isn't in CloudAPI at the moment, it's primarily been a focus of our engineering effort towards other deliverables, particularly with the current work ongoing with the lx brand, docker, and overlay networking. There's also a bit of ZFS work that wants to be done with respect to receiving an untrusted ZFS receive stream from a user that may not be generated with ZFS send. Does that clarify things? Do you have additional questions? Robert ------------------------------------------- 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
