On 2 December 2016 at 06:27, Stuart Bishop
wrote:
> We might be able to lower deployment times from minutes to seconds, since
> often this step is the main time sink.
>
Right. These are the time scales I meant too as well. If you want to have
quality software you need to be able to test it. If
Hi all,
Ionut Balutoiu (in cc) would like to use the resources mechanism but he
cannot upload the actual resources to accompany the charm. Instead he will
prompt the users to attach their own binaries during deployment. To serve
this use case Ionut can upload a dummy zero-sized binary to the store
Why can he not upload the resources? We have several mechanisms in place to
allow for gating charms based on things like "accepting terms", and a
general policy that "juju deploy SOFTWARE" should actually get you SOFTWARE
running in a functional manner. Telling people "do this deploy, but then go
g
Hello John,
I’m aware that there is a way to prompt users to accept EULA on deploy time,
but I’m worried about the fact the resources are downloadable from the charm
home page.
I’m not sure this is fine as I think we redistribute the software this way and
there are EULA’s that might not allow t
On Fri, Dec 2, 2016 at 5:49 AM Konstantinos Tsakalozos <
kos.tsakalo...@canonical.com> wrote:
> This works but has a side effect, the dummy binaries are available for
> downloading from the charm's page. Is there a way to hide the resources
> from the charm's readme page?
>
I'm confused why the u
Say you have a charm that deploys a proprietary piece of software. That
software has an EULA that prohibits anyone from redistributing it. The user is
essentially forced to go to the software vendor website, login using their
account, buy the software, and accept the EULA before being able to us
A new development release of Juju, 2.1-beta2, is here!
## What's new?
*Openstack Provider has been updated to support Neutron networking apis
* New APIs for querying instance types and characteristics available on
clouds
* Model Migration is no longer behind a feature flag
* Instrumentati
I'm with Rick... the expected usage is to publish a dummy resource with the
charm. Then, when you deploy, you deploy the real resource from your local
machine at deploy time. If you forget, you can always add the resource
after deploy, as well. The charm needs to take into consideration that
som
I was not aware that the expected usage was to publish with dummy resources. At
least, its not reflected in the documentation:
https://jujucharms.com/docs/2.0/developer-resources
Good to know :).
Uploading 0 byte resources sounds like a workaround rather then a feature
though. Would it not be
+1 its a workaround rather than a feature.
Can we allow publishing charms without resources? This simplifies things
for the charm author for the cases that the charm resource cannot be
uploaded to charmstore.
On Fri, Dec 2, 2016 at 11:59 AM, Gabriel Samfira <
gsamf...@cloudbasesolutions.com> wrot
10 matches
Mail list logo
