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
- 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.
Is this implemented in some search plugin? I only see the vnetid
hardcoded in the overlay definition.
Jan
-------------------------------------------
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
