<div dir="ltr">I have landed the change. If this causes problems, we can add a flag private-cloud datasources to prevent fallback.<div><br></div><div>We'll need to document this in the release notes. I have created a new bug so this gets a mention in 1.17.0:</div>
<div><a href="https://bugs.launchpad.net/juju-core/+bug/1247730" target="_blank">https://bugs.launchpad.net/juju-core/+bug/1247730</a><br>
</div><div><br></div><div>Cheers,</div><div>Andrew</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 10, 2013 at 4:34 PM, John Meinel <span dir="ltr"><<a href="mailto:john@arbash-meinel.com" target="_blank">john@arbash-meinel.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">So there is a difference between there not being a simplestream source at a location and there not being a matching entry in an existing file. If someone sets up a private stream falling back might not be expected.<br>
</p>
<p dir="ltr">John<br>
=:-></p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Oct 10, 2013 11:16 AM, "Andrew Wilkins" <<a href="mailto:andrew.wilkins@canonical.com" target="_blank">andrew.wilkins@canonical.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">On Fri, Oct 4, 2013 at 9:24 PM, Curtis Hovey-Canonical <span dir="ltr"><<a href="mailto:curtis@canonical.com" target="_blank">curtis@canonical.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Do we place a specific warning in the log. If I bootstrap with<br>
--show-log, do I see a message that clearly states the image cannot be<br>
found and and that Juju is falling back? I want to know if I have<br>
misconfigured something.<br></blockquote><div><br></div><div>Not a warning, because it's not necessarily unexpected. The code currently logs a DEBUG level message if it can't find product (image, tools) information from a source.</div>
<div><br></div><div>Cheers,</div><div>Andrew</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br>
On Fri, Oct 4, 2013 at 6:24 AM, William Reade<br>
<<a href="mailto:william.reade@canonical.com" target="_blank">william.reade@canonical.com</a>> wrote:<br>
> Yeah, let's go with always-fall-back. Much more likely to be useful in<br>
> general, and we can worry about masking off the rest of the world if there's<br>
> a clear need for it that can't be easily addressed outside juju (if the<br>
> environment can't see a stream, it won't be able to fall back to it ;)).<br>
><br>
><br>
> On Fri, Oct 4, 2013 at 11:26 AM, Jeroen Vermeulen<br>
> <<a href="mailto:jeroen.vermeulen@canonical.com" target="_blank">jeroen.vermeulen@canonical.com</a>> wrote:<br>
>><br>
>> On 04/10/13 12:26, John Arbash Meinel wrote:<br>
>><br>
>>> We came to this because the Azure provider was adding the "daily"<br>
>>> stream to the search path. Which meant that we would find the daily<br>
>>> stream, parse it, not find anything and then stop. Without falling<br>
>>> back to the releases stream which has the actual entries we are<br>
>>> looking for. (We "solved" this by just removing the daily stream,<br>
>>> which was also for other reasons.)<br>
>><br>
>><br>
>> I did that, IIRC at a time when only the daily images worked yet but<br>
>> releases were the obvious long-term way to go.<br>
>><br>
>> The implied contract for the imagemetadata package seemed to be that it<br>
>> would consider only the selected stream, and ignore any other streams it<br>
>> found in the search path. From what you say, that's what Andrew<br>
>> implemented. Otherwise, what's the point of supporting a search path<br>
>> consisting of multiple URLs?<br>
>><br>
>> With the fallback, having both the daily and the release stream in the<br>
>> path allows users to select one or the other by setting just a stream name —<br>
>> no messing with simplestreams URLs in the most common case.<br>
>><br>
>><br>
>><br>
>> Jeroen<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>
> 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>
Curtis Hovey<br>
Canonical Cloud Development and Operations<br>
<a href="http://launchpad.net/~sinzui" target="_blank">http://launchpad.net/~sinzui</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>
<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>
</div></div></blockquote></div><br></div>