On 6/8/17 13:29 , Ján Poctavek wrote: > Hi Robert, > > thank you for the clarification. Now, with all bits together, it seems > quite logical. Some additional comments in-line: > > > On 8. 6. 2017 2:40, Robert Mustacchi wrote: >> We never really figured out what a good interface for this would be for >> normal SmartOS, so you've mostly found all the bits in Triton that >> automate it there and make more sense there. I'll try and explain some >> of the things you saw, but if you have ideas on what might make sense, >> that'd be useful. > > The hardcoded location of overlay_rules.json that has to reside on the > non-permament storage is a bit weird. One has to create a service early > in the boot list (definitely before starting zones) just to put the file > in place. Maybe if there was some alternative (permanent) location that > can be looked up if not found in the first location. It also could be > loaded into /run at boot e.g. from /opt/custom/overlays. > > Or, alternatively, dladm create-overlay could have some "persist" flag > that can add new overlay into the overlay_rules.json
Yeah, if we could do some things over, we might have instead have done a better job of dealing with /etc/path_to_inst and added the persistence that nictags represent as permanent dladm devices. I think realistically we'd want to look at ways of doing that permanence. That file was really only intended to bootstrap the nictagadm rules at boot time. We should probably be looking at better ways to handle this for the general SmartOS case and allow them being present in the config file potentially. 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
