<div dir="ltr">A follow-up question: should closing a port that was not opened previous to that result in an error?<div><br></div><div>Domas</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 27, 2014 at 2:13 PM, Matthew Williams <span dir="ltr"><<a href="mailto:matthew.williams@canonical.com" target="_blank">matthew.williams@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 on an opened-ports hook tool, I've added it to the task list</div><div class="HOEnZb"><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 27, 2014 at 9:41 AM, William Reade <span dir="ltr"><<a href="mailto:william.reade@canonical.com" target="_blank">william.reade@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Agreed. Note, though, that we'll want to give charms a way to know what ports they have already opened: I think this is a case where look-before-you-leap maybe beats easier-ask-forgiveness-than-permission (and the consequent requirement that error messages be parsed...). An opened-ports hook tool should do the trick.</div>
<div><div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 26, 2014 at 9:18 PM, Gustavo Niemeyer <span dir="ltr"><<a href="mailto:gustavo@niemeyer.net" target="_blank">gustavo@niemeyer.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1 to Mark's point. Handling exact matches is much easier, and does<br>
not prevent a fancier feature later, if there's ever the need.<br>
<div><div><br>
On Thu, Jun 26, 2014 at 3:38 PM, Mark Ramm-Christensen (Canonical.com)<br>
<<a href="mailto:mark.ramm-christensen@canonical.com" target="_blank">mark.ramm-christensen@canonical.com</a>> wrote:<br>
> My belief is that as long as the error messages are clear, and it is easy to<br>
> close 8000-9000 and then open 8000-8499 and 8600-9000, we are fine. Of<br>
> course it is "nicer" if we can do that automatically for you, but I don't<br>
> see why we can't add that later, and I think there is a value in keeping a<br>
> port-range as an atomic data-object either way.<br>
><br>
> --Mark Ramm<br>
><br>
><br>
> On Thu, Jun 26, 2014 at 2:11 PM, Domas Monkus <<a href="mailto:domas.monkus@canonical.com" target="_blank">domas.monkus@canonical.com</a>><br>
> wrote:<br>
>><br>
>> Hi,<br>
>> me and Matthew Williams are working on support for port ranges in juju.<br>
>> There is one question that the networking model document does not answer<br>
>> explicitly and the simplicity (or complexity) of the implementation depends<br>
>> greatly on that.<br>
>><br>
>> Should we only allow units to close exactly the same port ranges that they<br>
>> have opened? That is, if a unit opens the port range [8000-9000], can it<br>
>> later close ports [8500-8600], effectively splitting the previously opened<br>
>> port range in half?<br>
>><br>
>> Domas<br>
>><br>
>> --<br>
>> Juju-dev mailing list<br>
>> <a href="mailto:Juju-dev@lists.ubuntu.com" target="_blank">Juju-dev@lists.ubuntu.com</a><br>
>> Modify settings or unsubscribe at:<br>
>> <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
>><br>
><br>
><br>
> --<br>
> Juju-dev mailing list<br>
> <a href="mailto:Juju-dev@lists.ubuntu.com" target="_blank">Juju-dev@lists.ubuntu.com</a><br>
> Modify settings or unsubscribe at:<br>
> <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
><br>
<br>
<br>
<br>
</div></div><span><font color="#888888">--<br>
<br>
gustavo @ <a href="http://niemeyer.net" target="_blank">http://niemeyer.net</a><br>
</font></span><div><div><br>
--<br>
Juju-dev mailing list<br>
<a href="mailto:Juju-dev@lists.ubuntu.com" target="_blank">Juju-dev@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>--<br>
Juju-dev mailing list<br>
<a href="mailto:Juju-dev@lists.ubuntu.com" target="_blank">Juju-dev@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>--<br>
Juju-dev mailing list<br>
<a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
<br></blockquote></div><br></div>