On 6/7/17 14:59 , Ján Poctavek wrote: > Okay, seems I've figured it out. But it was not an easy one. The > documentation about this is nonexistent.
Hi Ján, 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. > When using overlays with VMs, the overlays are created automatically and > they don't need to be created by dladm command. This was the design center for triton where we're not using direct tunnels, but we effectively have an overlay per customer, so they're much more dynamic. > - note that overlays as nic_tag need to be referenced by name and a > (random) number after slash The number in this case was designed to be a vxlan (or other encapsulation protocol) identifier. > - and also note that "-s direct" overlay can be created only between two > (and no more) SmartOS servers Right, it's really designed for point to point connections. There's an open RFE about making sure you can use multicast groups, but beyond that, folks will need to look at other search plugins with overlays to plug into other directory services. Hopefully that helps clarify a bit, sorry this was rather painful. 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
