+1 from me. I like having the list used as an application method to help
expose whose applying and feedback from there.
On Wed, Jul 31, 2013 at 6:32 PM, Antonio Rosales
antonio.rosa...@canonical.com wrote:
I added a clarification point at
https://juju.ubuntu.com/community/charmers/ on how
It's been several weeks since I first announced amulet[0] and I'm happy to
release the 1.0 milestone of amulet. A lot has been added since the
simple `jitsu watch` port. However, before I go into the details of this
release I want to take this moment to describe really the aim of this
project.
On Wed, Oct 30, 2013 at 10:47 AM, Gustavo Niemeyer gust...@niemeyer.netwrote:
On Wed, Oct 30, 2013 at 7:35 AM, Kapil Thangavelu
kapil.thangav...@canonical.com wrote:
Just thinking outloud, but In the active-active db scenario, there's an
available db for the charm to store this info. ie.
We still have and display oneiric charms in the charm store. I'm going to
keep this brief, but:
Can you still deploy to oneiric?
Do we want this to be displayed in the GUI at all?
Do we even want these in the store?
What's the plan for charms whos series has EOL'd?
Thanks,
Marco Ceppi
--
Juju
that nagios_check_url remains and
nagios_check_http_params is added with the change and note of the
distinction of the two in the README.
I'm actually not sure how to handle this though, so I'm reaching out to the
list for feedback.
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
be correct to keep squid
reverseproxy with the standard.
--
David Ames
On Sun, Nov 3, 2013 at 9:50 PM, Marco Ceppi marco.ce...@canonical.com
wrote:
Hi all, I need some consensus on how to handle merge proposals for
charms
in the charm charm store when these proposals change configuration
Hello everyone!
I'm happy to announce charm-tools 1.1.2 has been released! This release
succeeds 1.1.1, which was released a few hours. This announcements contains
the fixes for both 1.1.1 and 1.1.2. This release implements two patches to
improve proofing functionality for bundles and charms.
#
provides a Bundles class and only a proof
endpoint is exposed. More features will be published in the upcoming
releases of charmworldlib.
# Support
Support for charmworldlib is available via bug reporting at
https://bugs.launchpad.net/charmworldlib
Thanks,
Marco Ceppi
--
Juju mailing list
Juju
or feedback on this policy change, hoping to get it
released in the next version of charm-tools.
Thanks,
Marco Ceppi
[0]: http://yaml.org/type/null.html
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
,
etc. For now just collecting them all in one place is a good start.
Thanks,
Marco Ceppi
On Thu, Feb 13, 2014 at 5:50 PM, Joshua Strobl truthfroml...@gmail.comwrote:
Would it be feasible and/or benefitial to have some sort of rating
system for the plugins, with those that get the most support
to too many lists. I also want to re-iterate
that unless you're using very specific (and, arguably the proper way) to
reference charms this change will be transparent to you.
Thanks,
Marco Ceppi
On behalf of ~charmers
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe
Which cloud were you running this against?
On Feb 3, 2014 5:23 PM, Daniele Stroppa daniele.stro...@joyent.com
wrote:
Hi All,
while running test for the Node.js charm I ran into an issue with the
MySQL charm, see attached log. It looks like it's a permissions issue.
I'm running on Ubuntu
I don't see any objections, and a minimum of two charmers with a plus one
is satisfied. I'll leave this open for any further discussion, but
otherwise starting next week Matt will be elevated to charmers status.
Welcome!
Thanks,
Marco Ceppi
On Tue, Apr 1, 2014 at 9:23 AM, Peter Petrakis
are functions that
perform some rudimentary validation.
I eagerly await feedback and have had an immense amount of fun working on
this so far! I'll likely follow up with a more official announcement when
more of the commands have been implemented.
Thanks,
Marco Ceppi
--
Juju mailing list
Juju
which may arise. At this
time no 0.5 series is planned as the charmworld API has no future versions
planned.
Support for charmworldlib is available via bug reporting at
https://bugs.launchpad.net/charmworldlib
Thanks,
Marco Ceppi, on behalf of the Juju Solutions team
--
Juju mailing list
Juju
Hi Jose!
Thank you so much for your submission to be a charmer. Not only have you
been a huge asset helping community members but have done quite a lot of
work in the audit and in patching charms. That said, I've noticed a large
delta in your reviews of things which were missed and covered later
My question is why do you need to run add-relation in a synchronous fashion?
On Fri, Aug 22, 2014 at 9:02 AM, Chris Glass chris.gl...@canonical.com
wrote:
Charm-helpers uses a trick for this, which is to check if the
private-address key was set on the relation.
You can have a better look
term roadmap for the queue. There are still quite a
few things which need to be implemented, mainly the top navigation does
nothing and a few queues are empty but quite a few new items have showed up
in the queue!
Feedback, suggestions, comments, and pull requests welcome!
Thanks,
Marco Ceppi
Is there a way to see what commits made it in to this release? I'm curious
to know if a few patches (that weren't tied to bugs until recently) made it
in.
On Fri, Sep 19, 2014 at 5:32 AM, Samuel Cozannet
samuel.cozan...@canonical.com wrote:
Thanks for all of this, all good and very helpful
Hi Chris!
Awesome work on the charm, I'm not sure I'll ever need to mirror the entire
Ubuntu repository, but if I ever did I'm happy there's a charm for it! I do
like that it leverages the storage charm and is scaleout safe (safe for
bandwidth + wallet too).
Marco
On Sat, Sep 20, 2014 at 10:55
Jose and Charles,
Could you summarize the issue? Is it something that we need to document or
bugs we should file in core?
Marco
On Wed, Sep 24, 2014 at 12:42 AM, José Antonio Rey j...@ubuntu.com wrote:
On 09/23/2014 11:25 PM, Tim Penhey wrote:
On 24/09/14 16:20, Michael Schwartz wrote:
You have a big plus one from me Jorge, thanks for all your contributions
and continuing growth of charms and tool ecosystem!
On Wed, Sep 24, 2014 at 10:54 PM, Jorge Niedbalski
jorge.niedbal...@canonical.com wrote:
Hello Charmers,
I would like to have your consideration to become a member of
There shouldn't be much in the WordPress charm that's Ubuntu specific and
should work fine on Debian. Some charms already have logic to support
multiple Ubuntu releases by either coding switches in the hooks or by
leveraging a configuration management tool like chef or puppet which
abstracts that.
So there's no current way to determine when an environment is idle in Juju,
there's work being done to allow services to illuminate more than just the
current states of PENDING, INSTALLED, STARTED, ERROR in Juju which will
help illuminate where a service is in it's lifecycle. However, all of that
In addition, there's also a `juju retry-provisioning machine-number`
which can be used after you upgrade in the event you encounter provisioning
issues in the future. Typical provisioning issues for machines include
resource limitations on account and errors downloading required
dependencies.
.
This should be a good starting place for how much effort would be required
to accommodate this new feature.
Any idea what version of juju we can expect to start seeing this land?
Thanks!
Marco Ceppi
On Mon Nov 17 2014 at 9:13:45 PM Andrew Wilkins
andrew.wilk...@canonical.com wrote:
Hi all,
I
I have to disagree slightly, currently (and thankfully?) the current way
most charm-helpers aim to be included in charms is by embedding a working
snapshot of that version of charm-helpers. So merging this wouldn't affect
a huge number of charms, instead maybe the 5 or 6 at most that download
from
oneiric, precise, quantal, raring, saucy, trusty, utopic, and vivid are all
valid series for charms. We don't' freeze releases so once a release of
Ubuntu exists a charm series will also exist.
On Fri Nov 21 2014 at 11:21:28 PM José Antonio Rey j...@ubuntu.com wrote:
Please correct me if I'm
We typically discourage querying cloud specific utils in charms as it makes
them far less portable. It would be much more preferred to have this
patched in Juju.
On Wed Nov 26 2014 at 10:10:35 PM Andrew Wilkins
andrew.wilk...@canonical.com wrote:
Hi Mike,
Sounds like you're hitting
Can you link us to your request?
On Thu, Dec 4, 2014, 8:43 AM saurabh saurabh.ku...@techblue.co.uk wrote:
Hi,
I wanted to know that how do I raise a request to review my charm? I
have already subscribed a charmer to my branch but my charm doe not show
up in the review queue at
provide you the links to my charm's name-space?
Thanks,
On Thursday 04 December 2014 07:14 PM, Marco Ceppi wrote:
Can you link us to your request?
On Thu, Dec 4, 2014, 8:43 AM saurabh saurabh.ku...@techblue.co.uk
wrote:
Hi,
I wanted to know that how do I raise a request to review my charm
against the github repository
https://github.com/marcoceppi/amulet
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
On Wed Dec 10 2014 at 10:28:41 AM Marco Ceppi ma...@ondina.co wrote:
On Wed Dec 10 2014 at 10:26:48 AM Eric Snow eric.s...@canonical.com
wrote:
I had tried the explanation route to no avail. I'll probably work up
a demo for the specific folks I have in mind. I think juju is one of
those
to use Juju and let us know anywhere else we can help improve!
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
outlined, where --force will ignore hook
errors during the destruction of a service.
Thanks,
Marco Ceppi
IIRC, the reason we support juju destroy-machine --force but not juju
destroy-unit --force is because in the former case, because the machine is
no-more Juju has ensured that cleanup
This is the last planned release in the 1.5 series and 1.6 series and
branch are now open for development. You can always contact us for
additional help via #juju on irc.freenode.net, http://askubuntu.com with
questions tagged #juju, or via this very mailing list juju@lists.ubuntu.com
Thanks,
Marco Ceppi
You could, the only requirement is that it's served over HTTPS. We're
simply recommending imgur as an example of a free image hosting service
which has https enabled.
On Mon Feb 02 2015 at 2:05:57 PM Charles Butler
charles.but...@canonical.com wrote:
Nick,
Why add a complex requirement such
chose).
On Tue Jan 20 2015 at 1:18:05 PM David Britton david.brit...@canonical.com
wrote:
On Tue, Jan 20, 2015 at 05:58:24PM +, Marco Ceppi wrote:
I don't see how a Makefile in a charm doesn't resolve this issue.
+1 on some standard published Makefile targets. We already have some
I don't see how a Makefile in a charm doesn't resolve this issue. As long
as we define what targets a user should create in the Makefile, the
Makefile can then do everything required: create a virtualenv and install
deps, install ruby and execute bundler, npm for node, etc. Since charms are
so
, concerns, or questions.
[0]: http://packages.ubuntu.com/search?keywords=juju
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
We are striving to test charms against all substrates and architectures
juju supports; and are nearing completion for that goal. Manual provider is
not currently tested AFAIK but will likely be in the future.
On Tue Jan 20 2015 at 7:41:27 PM Andrew Wilkins
andrew.wilk...@canonical.com wrote:
We can also add Makefile checking to charm proof, for an even greater
redundancy.
To avoid multiple invocations of charm proof (not terrible, IMO) lint could
be broken down further:
lint: proof code_lint
proof:
charm proof
code_lint:
# Your code here
Then have bundle tester sniff out
Hey Andrew,
I agree with you on the feedback, since it's an HTML page at the moment
it's hard to incorporate those items, but I've forked the repo and started
building a lightweight Python app to provide that feedback to the user.
Marco
On Tue Feb 10 2015 at 9:37:48 PM Andrew Wilkins
WOW! What an action packed release! Great job to all the people who
reported bugs, hacked on code, and helped release this!
On Thu Jan 29 2015 at 12:03:07 PM Curtis Hovey-Canonical
cur...@canonical.com wrote:
# juju-core 1.21.1
A new stable release of Juju, juju-core 1.21.1, is now
. The agent-state: pending is a clear indication it hasn't
registered itself with the bootstrap node yet.
Thanks,
Marco Ceppi
On Wed Jan 28 2015 at 4:50:51 PM Daniel Bidwell drbidw...@gmail.com wrote:
I have ubuntu 14.04.1 with maas 1.7.1 rc4 and juju 1.20.14. My client
machine is commissioned
Hi VM,
The 409 CONFLICT error is the right error, and the error that MAAS provides
through the API when no machines matching the criteria supplied are
available. Juju doesn't directly query MAAS for how many machines are
available it simply takes the criteria you supplied (or the default
/docs/pull/222
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Thanks Nicolás for brining this to our attention and Stuart for shedding
light on how deep this bug runs. While it's true we're kind of tied to
doing what Juju does, that doesn't mean we can't look at ways to alleviate
this in Amulet to avoid tests to prevent them from failing.
On Fri, Feb 13,
The queue is quite backed up. A few people have reached out asking about
when items will be addressed so I spent a few hours cleaning up as much as
I could.
- Pure-Python Django: Merged;
https://code.launchpad.net/~patrick-hetu/charms/precise/python-django/pure-python/+merge/226742
- Liferay to
or bugs can be reported against the launchpad project:
https://launchpad.net/amulet
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
, not policy.
On Wed, Mar 4, 2015 at 11:44 AM Simon Davy bloodearn...@gmail.com wrote:
On 2 March 2015 at 17:46, Marco Ceppi ma...@ondina.co wrote:
# Charm Authors
- Avoid symlinks in charm
/me blinks
I assume you don't mean symlinks in hooks/ dir?
Anything documenting why this is a bad
It seems Jorge omitted why this is useful. When doing charm reviews or
performing charm testing (while developing) you can use the docker
container to quickly spin up an isolated environment so the charm can
execute it's testing dependencies without dirtying the testers system.
We're also now
The MAAS oauth keys contain a ':' which is an illegal character in YAML.
You'll need to wrap it in quotation marks to resolve that.
On Tue, Mar 24, 2015 at 1:43 PM José Antonio Rey j...@ubuntu.com wrote:
This should be because of a formatting error on your environments.yaml
file. Can you check
This is nothing but pure awesome in plugin form! Thanks for working on this
On Fri, Apr 24, 2015 at 8:34 AM Cory Johns cory.jo...@canonical.com wrote:
Last week, while in Nuremberg, Ben and I were able to create a new
plugin to enable a much better charm development workflow.
Once the Juju
, or you're not using local provider, let us know.
Also, the version of juju you're using may also help us identify issues
you're having.
Thanks,
Marco Ceppi
On Thu, Apr 30, 2015 at 3:52 AM dinesh.senap...@wipro.com wrote:
Hi,
I have been working on Juju for last 2 weeks. There are some blockages
feedback, feature, or bug requests.
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
to help anyone who wants to get started, you can
find me, (marcoceppi), Adam (aisrael), or Tim (tvansteenburgh) on #juju on
Freenode and on this list.
Thanks,
Marco Ceppi
on behalf the Juju Ecosystems Team
[0]:
http://www.adamisrael.com/blog/2015/06/23/announcing-benchmarking-with-juju/
[1]: http
Hello!
Yes we plan to update the charm tools versions and several other packages
in the archive this cycle. I've kicked off an upload of charm-tools 1.5.1
to the PPA in the mean time.
Thanks,
Marco Ceppi
On Tue, Jun 2, 2015 at 2:40 AM Nobuto Murata nob...@nobuto-murata.org
wrote:
Hi,
I've
While I'm not 100% confident, I believe that the image-metadata and
agent-metadata URLs need to be a URL that is addressible from within the
OpenStack cloud as they're used by cloud-init when bootstrapping which may
explain why you're not completing the process.
Marco
On Thu, Jul 2, 2015 at 7:21
at the moment.
TL;DR: I want to make charm-helpers very slim, versioned, packaged,
documented, and easily portable to other languages.
Thanks,
Marco Ceppi
Juju Developer Experience group
[0] http://pythonwheels.com/
[1] https://github.com/cloudbase/juju-powershell-modules
[2] https://crates.io/crates
...@canonical.com
On Tue, Aug 11, 2015 at 8:42 AM, Marco Ceppi marco.ce...@canonical.com
wrote:
Hello everyone,
There have been a lot of conversations had over the past few months about
charm-helpers and how to proceed forward with the project. As a result of
these conversations I'd like
On Wed, Aug 12, 2015 at 7:17 AM Adam Collard adam.coll...@canonical.com
wrote:
On Wed, 12 Aug 2015 at 12:12 Marco Ceppi marco.ce...@canonical.com
wrote:
Working with the Juju QA team to add a Jenkins job for test landing is a
great idea, one we should certainly do now while we figure
On Wed, Aug 12, 2015 at 6:11 AM Stuart Bishop stuart.bis...@canonical.com
wrote:
On 11 August 2015 at 20:42, Marco Ceppi marco.ce...@canonical.com wrote:
# Trimming down charm-helpers
The first item, and arguably the largest is a complete reorganization of
the
current charm-helpers
ke
delete_path safer
6fbb036 [Benjamin Saller] finish rename
a30876a [Benjamin Saller] rename composer to build
566b1e9 [Cory Johns] Move LPGitFetcher upstream and add missing rename
(fixes #14)
2a99239 [Cory Johns] Handle empty metadata.yaml (fixes #15)
bf563b9 [Marco Ceppi] Remove py3 testing
Regardless of the outcome of the bug, the proper syntax for accessing units
is as follows:
self.d.sentry["ibm-mobilefirst-server"][0]
This is because, our new testing environment and soon to be normal testing
procedure for all charms while we wait for multi-model environments
recycles the
Sorry to hear you're having troubles. It sounds like cloud-init didn't
finish. Are you able to get a console onto the VM? If so could you get the
contents of /var/log/cloud-init*?
On Thu, Nov 5, 2015, 6:36 AM Cseh Dávid wrote:
> Hi
>
>
>
> I tried to bootstrap juju on a
node run:
sudo apt-get install pastebinit
pastebinit /var/log/juju/machine-0.log
This will provide a URL with the pastebin of the machine-0 log which would
be helpful in diagnosing this issue further and potentially ways to resolve
this.
Thanks,
Marco Ceppi
On Fri, Oct 16, 2015 at 3:56 AM 曾建銘
For the time being you can add these entries to the lxc container defaults,
which should be in `/etc/lxc/default.conf` and new containers launched will
have those updated values. Going forward, we're working on a LXD provider
for Juju - part of that work will enable nesting of containers by
/~mattyw/charms/trusty/mongodb/mongodb-deployu/+merge/262666
*
https://code.launchpad.net/~stub/charms/trusty/postgresql/standby-service/+merge/262811
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
the
liberty to move the bug under the charms distribution and it should be in
the review queue momentarily.
In the weeks to come we'll be proposing a new, more streamlined review
process to this list, so your feedback (and everyone elses) will be much
appreciated then.
Thanks,
Marco Ceppi
On Thu, Jul 9
more
days to figure out this snafu.
I'm on the case now and hope to have those three packages sorted in a few
hours.
Thanks,
Marco Ceppi
On Fri, Sep 4, 2015 at 5:38 AM Adam Collard <adam.coll...@canonical.com>
wrote:
> Hi Marco,
>
> On Wed, 2 Sep 2015 at 22:01 Marco
ju, or via this very mailing list juju@lists.ubuntu.com
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
project:
https://launchpad.net/amulet
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
/pymongo-3.x/+merge/270525
- apache2: Adds support for nagios_servicegroups, merged
https://code.launchpad.net/~verterok/charms/trusty/apache2/nagios_servicegroups/+merge/269259
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com
## PIP
pip install -U charm-tools
# Summary
This is the last planned 1.7 series release barring any bug fixes. Going
forward we're looking to move charm-tools source hosting to
github.com/juju/charm-tools to better be aligned where the rest of the
ecosystems tools are.
Thanks,
Marco Ceppi
oblem when going
through the charm review process to have it listed as a recommended charm
in the charm store.
Thanks,
Marco Ceppi
On Fri, Oct 2, 2015 at 12:23 PM Frederico Araujo <arau...@gmail.com> wrote:
> Hi,
>
> I'm trying to create my first charm without success. I used 'juju
oblem when going
through the charm review process to have it listed as a recommended charm
in the charm store.
Thanks,
Marco Ceppi
On Fri, Oct 2, 2015 at 12:22 PM Frederico Araujo <arau...@gmail.com> wrote:
> Hi,
>
> I'm trying to create my first charm without success. I used 'juju
This is an interesting one, I hacked together a one-liner from both Nate
and your replies
juju ssh 0 "ps -ae -o command= | grep [j]ujud | grep JUJU_DEV_FEATURE_FLAGS
| awk -f'\"' '{ print $2 }'"
and added[0] it to the juju plugins repo as `juju flags`:
https://github.com/juju/plugins
$ juju
/edit
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Hash: SHA256
>
> On 2015-11-27 11:00 AM, Marco Ceppi wrote:
> > - Running Wily (LXD is installed by default)
> >
> >
> > For the LXD provider, I have the latest LXD installed on trusty,
> > will that work or is it hard-coded to wily+ ?
>
> It will not work. Only platf
On Fri, Nov 27, 2015 at 9:37 AM Aaron Bentley
wrote:
> # juju-core 1.26-alpha2
>
This is probably the most anticipated release of the year. Looking forward
to trying out all the new features!
> ### LXD Provider
>
> The new LXD provider is the best way to use Juju
On Thu, Nov 26, 2015 at 3:05 AM Simon Davy <bloodearn...@gmail.com> wrote:
> On Thursday, 26 November 2015, Marco Ceppi <marco.ce...@canonical.com>
> wrote:
> > On Wed, Nov 25, 2015 at 4:08 PM Simon Davy <bloodearn...@gmail.com>
> wrote:
> >>
>
On Thu, Dec 3, 2015 at 6:21 PM Cory Johns wrote:
> Greetings!
>
> The big data team, including myself, Kevin, Andrew, and Konstantinos, hit
> the Review Queue today:
>
>
>-
>
>zulu8
>-
>
> https://bugs.launchpad.net/charms/+bug/1519858
> -
>
>
`
# Changes
3b05f0c [Marco Ceppi] version bump
efb50fd [Cory Johns] Fixed tests
48ba928 [Cory Johns] Use Python 3 for layered charms
f2d5c5c [Cory Johns] Fixed hook name for storage and added test coverage
44e6c8c [Cory Johns] Resolve #66: Add reactive hooks for storage
238826d [Cory Johns] Add
`
# Changes
a5d3cf6 [Marco Ceppi] version bump
e192b56 [Marco Ceppi] add /home/marco to whitelist fixes #47
742f669 [Cory Johns] Fix #69: newline before shebang in generated hooks
# Highlights
This addresses two bugs, one which is critical to charm creation.
# Install
Charm Tools is available
You can actually
juju action fetch --wait=0
which will wait indefinitely for the result (ie, blocking) which would
simplify the code you provided. I agree there could be some improvements to
the action cli and will be making these bugs on the project as features
requests!
On Fri, Dec 11, 2015
to upgrade. As
always you can verify the version you are running by executing: `charm
version`
# Changes
8b23dcd [Marco Ceppi] version bump
2dba307 [Marco Ceppi] Match source dependency as found in Xenial
e6890e0 [Cory Johns] Resolve #65: Add support for layer options in
layer.yaml
0b06f42 [Cory
Not sure if it will work completely offline, but you'll probably want to
pull all the layers/interfaces you want into INTERFACE_PATH and LAYER_PATH.
If I recall correctly, those are searched first for matches before the
index. The pip stuff is a bit harder, but it seems reasonable that we could
I believe that the Juju GUI team is preparing a release in the coming weeks
to address this. It's not so much a bug, but rather a planned feature for
Juju GUI
On Fri, Dec 11, 2015 at 3:30 AM Sameer Zeidat wrote:
> Hello,
>
> I'm setting charm status to blocked (sometimes to
report.
Thanks,
Marco Ceppi
On Mon, Jan 4, 2016 at 9:04 AM Bruno Ranieri <br...@quobyte.com> wrote:
> Hello,
>
> I run into some problems when trying to bring some new charms through the
> charm store process
>
> https://bugs.launchpad.net/~3-bruno
>
> I s
tive pattern, because
> I don't know Python :)
>
> Thanks,
> Patrik
>
> Marco Ceppi <marco.ce...@canonical.com> schrieb am Mo., 4. Jan. 2016 um
> 15:13 Uhr:
>
>> Hi Patrik,
>>
>> It's best to think of the charm as an entire solution for the
>>
On Mon, Jan 4, 2016 at 9:51 AM Bruno Ranieri <br...@quobyte.com> wrote:
> Hi Marco,
>
> thanks for the quick response.
>
> 2016-01-04 15:21 GMT+01:00 Marco Ceppi <marco.ce...@canonical.com>:
>
>
>> When I search the charm store, https://jujuch
juju hotness!
Thanks,
Marco Ceppi
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
are running
by executing: `charm version`
# Changes
5cadfda [Marco Ceppi] version bump
8c09431 [Marco Ceppi] Make sure wheel is available in build venv fixes #51
11557b3 [Marco Ceppi] version bump
2a70207 [Marco Ceppi] install_requires needed because Homebrew can't handle
a pip install
f820bfd
On Wed, Nov 25, 2015 at 4:08 PM Simon Davy <bloodearn...@gmail.com> wrote:
> On 25 November 2015 at 16:02, Marco Ceppi <marco.ce...@canonical.com>
> wrote:
> > ## Wheel House for layer dependencies
> >
> > Going forward we recommend all dependencies f
On Wed, Nov 25, 2015 at 7:44 PM Rick Harding
wrote:
> On Wed, Nov 25, 2015 at 4:08 PM Simon Davy
>
>> I don't know where we are at with the resources work, but maybe that
>> could have a part to play here?
>>
>
> This is exactly what I wanted to bring up for
Hi Merlijn,
Sorry for the outage. Apparently the cloud is an ephemeral world. We deploy
svg.juju.solutions from the charm store
https://jujucharms.com/u/marcoceppi/charm-svg/3 but the cloud it was on
decided to turn off all the instances. I've redeployed it and it's back up
now.
I'll work on
; https://github.com/IBCNServices/tengu-charms/blob/master/bundles/hauchiwa-testbundle/bundle.yaml
>
>
>
> Kind regards
> Merlijn Sebrechts
>
> 2016-06-14 21:33 GMT+02:00 Marco Ceppi <marco.ce...@canonical.com>:
>
>> Hi Merlijn,
>>
>> Sorry for the o
I don't think this needs to be scoped to just proprietary charms. It can be
better scoped to:
Any software which requires acceptance of a license or EULA has to have
that as a term on the charm
Any software which installs components from outside of a distributions
archive needs to represent that
+1 to using % logic to make it scale across any sized instance. Awesome
stuff!
On Wed, Jun 1, 2016 at 6:28 AM Tom Barber wrote:
> Okay latest "stable" build has RAM config options.
>
> Drill ships with defaults of 8GB and 3GB but I didn't want it to die on
> EC2 Large
1 - 100 of 280 matches
Mail list logo