On Mon, Mar 14, 2016 at 1:05 PM, John Meinel <j...@arbash-meinel.com> wrote: > ... > >> >> >> > 3) Downloading from the internet. This issue has been common in >> > charmstore charms, and is discouraged, AIUI. But the same issue >> > applies for layers, and possibly with more effect, due to a layer's >> > composibility. We simply can not utilise any layer that downloads >> > things from github or similar, and I'm sure others are in a similar >> > situation. We're aware of resources, but not convinced this is a >> > scalable solution for layers, as it makes using a charm that has >> > layers that require resources much more complex. So, some clarity in >> > this area would be helpful. >> >> Yes, layers that do not work in network restricted environments are >> not useful to many people. I think you will find layers will improve >> things here. Layers only need to be written correctly once. And if >> they are broken, only fixed once. A big improvement over cargo culted >> code, where you could end up fixing essentially the same bug or adding >> the same feature several times. >> > > Layers themselves are a compile time thing, not a runtime thing, right? So > while the code in the layer might say "download some resource from github", > you the layer itself is only downloaded from github before it is published > into the charm store. Am I understanding this wrong? > > John > =:->
Right, downloading at build time is a different problem. The issue is that the layer might do something on the install hook, for example, which downloads from the internet at run time, on the units. Such things work fine in dev or for demos, but will fail in many production environments. -- Simon -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
