<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><div dir="ltr" style="font-family:arial,sans-serif;font-size:12.8px"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">It it very useful for deploying on a target in the future. Not very helpful to developing/testing/debugging on system without the gadget snap today.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Perhaps, if a snap is installed in --devmode, then all interfaces are auto-connected. I would think that if a snap can be installed in --devmode on a system, then you are already opening up the system to all sorts of "dangers".</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Mike</div></div><div class="" style="font-family:arial,sans-serif;font-size:12.8px"><div id=":1h9" class="" tabindex="0"><img class="" src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif" style=""></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 13, 2016 at 2:25 PM, Mark Shuttleworth <span dir="ltr"><<a href="mailto:mark@ubuntu.com" target="_blank">mark@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div><br>
In the context of a snap running on Ubuntu Core, the all-snap
version of Ubuntu, the gadget snap (which defines behaviors
specific to that particular device) would describe additional
auto-connection rules.<br>
<br>
So in your case, a switch that had certified your OpenSwitch NOS
would specify that, when installed, OpenSwitch plugs and slots be
connected appropriately.<br>
<br>
Think if it as that "the user OR the device manufacturer can take
this decision" and the gadget snap is how the device manufacturer
would do so.<br>
<br>
Would that be useful?<span class="HOEnZb"><font color="#888888"><br>
<br>
Mark</font></span><div><div class="h5"><br>
<br>
On 13/07/16 10:54, MikeB wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div style="font-family:tahoma,sans-serif;font-size:small">Yes, I
see your point.</div>
<div style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div style="font-family:tahoma,sans-serif;font-size:small">Perhaps
a concept of optional vs required is needed. </div>
<div style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div style="font-family:tahoma,sans-serif;font-size:small">Mike</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 13, 2016 at 12:37 PM, Kyle
Fazzari <span dir="ltr"><<a href="mailto:kyle.fazzari@canonical.com" target="_blank">kyle.fazzari@canonical.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Hey Mike,</p>
<span>
<p dir="ltr">On Jul 13, 2016 3:46 AM, "MikeB" <<a href="mailto:mabnhdev@gmail.com" target="_blank"></a><a href="mailto:mabnhdev@gmail.com" target="_blank">mabnhdev@gmail.com</a>>
wrote:<br>
> I understand why you want manual connections for
some "critcal" interfaces. However, if you're going to
require manual intervention, the snapd should be smart
enough to wait for the required connections before
starting up any daemons that have plugs for those
"critical" interfaces. Perhaps even nagging about
unconnected plugs in the snap.</p>
</span>
<p dir="ltr">I understand where you're coming from here.
However, I can imagine use-cases where such a daemon can
actually run successfully without one of its plugs
(particularly when seccomp starts using ERRNO), and have
extra functionality if it's connected. If snapd didn't
start services until all their plugs were connected, such
a scenario would be impossible. Also, keep in mind that
the user can disconnect interfaces at any time, so ideally
daemons would be able to handle such things (though I
realize that's not always the case).</p>
<p dir="ltr">Just my two cents.</p>
<span><font color="#888888">
<p dir="ltr">Kyle</p>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div>