emote lxd cloud. I showed this in
> last week's Juju show.
>
> https://youtu.be/CidoBy3iqUw
>
> On Wed, Jun 6, 2018, 6:58 PM Marco Ceppi
> wrote:
>
>> On Wed, Jun 6, 2018, 21:33 Kelvin Liu wrote:
>>
>>>
>>>
>>>
>>>
>>
That page ends at #98 - but still great to see! Proud to have my 6 commits
in there
On Wed, Mar 14, 2018 at 5:45 PM Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> We're in triple digits! I'm not sure when this happened, but it's
> exciting nonetheless.
>
>
Fan Networking is a game changer
I've got something else for the .1 release - m5 instance types dropped last
week in AWS, preparing a pull request now
On Fri, Dec 8, 2017 at 6:30 AM Rick Harding
wrote:
> Hey, how did you know I was working on a plugin for
On Thu, Nov 2, 2017 at 12:57 AM Chris Lee wrote:
> A new development release of Juju is here, 2.3-beta2.
>
Woop woop!
> * Autoconfiguration of FAN networking for EC2 and GCE providers
>
> When creating a model in a VPC environment on EC2 or on GCE FAN settings
>
to collect information from hook tools of all units in a
deploy, network-get for example, or other commands.
Marco
On Mon, Oct 23, 2017 at 11:20 AM Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> On Mon, Oct 23, 2017 at 5:12 PM Marco Ceppi <marco.ce...@canonical.com>
>
On Mon, Oct 23, 2017, 03:59 Andrew Wilkins
wrote:
> On Mon, Oct 23, 2017 at 4:20 AM Akshat Jiwan Sharma
> wrote:
>
>> HI,
>>
>> I'm trying to manually expose a port on a juju machine. According to this
>> answer
>>
This seems to have landed in candidate already, for those wanting to test
on something other than edge.
sudo snap refresh charm --channel candidate
On Fri, Sep 8, 2017 at 2:59 PM Tim Van Steenburgh <
tim.van.steenbu...@canonical.com> wrote:
> Fantastic, this is a great change - well done!
>
>
The "problem" with Google, is you can actually customize the CPU/Memory
arbitrarily per instance. So they have recommended instance types, but you
can change those properties. I'm not sure why you're getting an
n1-highcpu-4. Default bootstrap for me has been a n1-standard-1
Marco
On Tue, Jan 10,
the cloud bringing up the instance.
I plan on doing this across all the clouds I have access to, and track in a
spreadsheet. I'll share that sheet out in a bit.
Thanks,
Marco Ceppi
On Thu, Dec 1, 2016 at 5:00 AM Adam Collard <adam.coll...@canonical.com>
wrote:
> On Thu, 1 Dec 2016 at 04:02 N
I think the actual path is to streamline reactive framework, so that Ubuntu
is the simplest example of reactive. Anyone can, as Nate demonstrated,
create a minimal charm. The feedback here is great so far and we're going
to be iterating on the framework.
Marco
On Fri, Dec 9, 2016, 9:32 AM John
A one machine manual provider? Might as well just `ssh ; juju
bootstrap lxd`.
On Mon, Dec 5, 2016 at 10:09 AM Nate Finch wrote:
> The should be no reason you can't deploy to the controller machine using
> manual just like any other cloud.
>
> juju bootstrap
n it's a bit of a
stretch weighing the pros and cons for the amount of work needed to support
unicode throughout Juju as an application name.
Marco
> On Fri, Dec 2, 2016 at 10:46 AM Marco Ceppi <marco.ce...@canonical.com>
> wrote:
>
> On Fri, Dec 2, 2016 at 10:31 AM Nate Finch
On Fri, Dec 2, 2016 at 10:31 AM Nate Finch wrote:
> One thing we *could* do to support non-english names that would not
> entirely open the door to emoji etc is to simply constrain the names to
> unicode letters and numbers. Thus you could name something 數據庫 but
> not
://svg.juju.solutions/?bundle=cs:~bigdata-dev/bundle/apache-analytics-sql-15=png
Thanks,
Marco Ceppi
On Thu, Dec 1, 2016 at 9:48 AM James Donner <james.don...@canonical.com>
wrote:
> This is a godsend.
>
> It used to be incredibly difficult to gather images of Juju bundles, but
> this to
On Thu, Dec 1, 2016 at 8:28 AM Free Ekanayaka <free.ekanay...@canonical.com>
wrote:
> On 1 December 2016 at 13:53, Marco Ceppi <marco.ce...@canonical.com>
> wrote:
>
> On Thu, Dec 1, 2016 at 5:00 AM Adam Collard <adam.coll...@canonical.com>
> wrote:
>
>
On Thu, Dec 1, 2016 at 5:00 AM Adam Collard
wrote:
> On Thu, 1 Dec 2016 at 04:02 Nate Finch wrote:
>
> On IRC, someone was lamenting the fact that the Ubuntu charm takes longer
> to deploy now, because it has been updated to exercise more of
msvg
* https://jujucharms.com/u/marcoceppi/charm-svg
The site is, of course, deployed and managed by Juju.
Thanks,
Marco Ceppi
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
Hey James!
We were looking at adding Keystone as a user management backend for
Kubernetes. This is a great step forward in making that possible, I noticed
the barbican charm in the AWS deploy was "local", are there any major
changes to the charm from ~openstack-charmers needed for it to run in
Hey James,
I think this is the best way about it for the time being, discussing what
people are working on ahead of it being perfect gives everyone a chance to
see what's going on and can help focus people on getting help from others
interested!
On Wed, Nov 2, 2016 at 10:48 AM James Beedy
This is really one of the goals. python-jujuclient, amulet, and even to an
extent deployer all poorly implement an abstraction to Juju. These will all
eventually fall away in favor of a consolidated, focused, well built Object
Oriented Python library.
Marco
On Tue, Nov 1, 2016, 4:25 PM Ryan
Thanks have some ideas about this, I'll file a bug (blueprint?) about it. I
really care about plugins and would like to make them more robust in Juju.
Marco
On Thu, Sep 29, 2016, 6:07 PM Tim Penhey wrote:
> If we do that, then we can make the plug-in also install a
lay names may also include unicode characters in the future,
for example
Übersoftware
Which would need name to still be defined from a store/unique id
perspective.
As for case insensitive juju deploy command, I'd consider that out of scope
of this proposal.
On Sat, Sep 24, 2016 at 2:50 PM, Mar
juju add-relation cinder san2
Now, you can configure each of the new applications, which are teh same
copy of the charm deployed multiple times. This will add a unique backend
per charm copy which seems to be your intended use case.
Thanks,
Marco Ceppi
On Wed, Sep 7, 2016 at 12:03 PM
On Thu, Sep 1, 2016 at 3:10 PM Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> A new development release of Juju, 2.0-beta17, is here!
>
> ## What's new?
>
> * add-model now takes region name as an optional positional argument,
>to be consistent with bootstrap. The --region flag has
someone without thinking.
>
What happens if I destroy-controller without that flag? Do I have to go
into my cloud portal to kill those instances? Is there any way to recover
from that to get juju reconnected? If not, it's just a slower death.
> On Thu, Sep 1, 2016 at 3:40 PM, Marco Ceppi <m
Hey everyone,
I know we've had discussions about this over the past few months, but it
seems we have three commands that overlap pretty aggressively.
Using Juju beta16, and trying to 'destroy' a controller it looks like this
now:
```
root@ubuntu:~# juju help destroy-controller
Usage: juju
What happened to the charms that were in development channel? Are they now
in edge?
Marco
On Wed, Aug 31, 2016, 9:06 AM Brad Crittenden wrote:
> The new version of the charmstore provides support for four channels
> (edge, beta, candidate, stable). The development channel
On Thu, Aug 4, 2016 at 6:16 AM John Meinel wrote:
> On Aug 2, 2016 6:08 PM, "Nate Finch" wrote:
> >
> >
> >
> > To make a PR from the CLI using hub, make sure the repo you want to PR
> against is the git remote called origin, then you can make a
Because of the ambiguous nature of actions and application. Some would
expect, as you do, to run on all units. Others would expect the leader to
coordinate that action. Furthermore, it becomes more complex as to how
results are curated. Do you get back X UUIDs one for each unit or a single
action
What does `juju status --format yaml` produce? it should provide more
fruitful machine errors.
Marco
On Mon, Aug 1, 2016 at 5:46 PM James Beedy wrote:
> I'm having some issues with deploying instances to network spaces on aws.
>
> Problem: Instance errors on deploy
>
> I
Hi Patrik,
This would be a great and welcomed addition. I'm adding the juju-dev
mailing list to this thread as that is where most the Juju Core development
happens.
Marco
On Mon, Aug 1, 2016, 6:23 AM Patrik Karisch
wrote:
> Hi there,
>
> I want to add DigitalOcean as
On Wed, Jul 27, 2016 at 8:25 PM Rick Harding
wrote:
> That being said, any API client that requires three API calls to login
>> should be beat over the head with a fail stick, but there are many cases
>> where performing some workflow might require multiple api calls.
Thanks!
On Wed, Jul 6, 2016 at 4:43 PM Cheryl Jennings <
cheryl.jenni...@canonical.com> wrote:
> There are no API changes planned for beta12, but if any do come up, they
> will be announced on the mailing lists.
>
> On Wed, Jul 6, 2016 at 8:59 PM, Marco Ceppi <marco.ce...@c
On Wed, Jul 6, 2016 at 3:51 PM Cheryl Jennings <
cheryl.jenni...@canonical.com> wrote:
> Hi Everyone,
>
> Due to the US holidays and with much of the team at core and networking
> sprints, we will be releasing 2.0-beta12 next week. There are currently 6
> assigned critical bugs [0] that need to
On Fri, Jun 24, 2016 at 3:18 PM Curtis Hovey-Canonical
wrote:
> A new development release of Juju, 2.0-beta10 is here!
>
> ## What's new?
>
> * Improved handling of LACP bonds
> * Continued usability enhancements
> * Users can now use `juju relate` to add a relation
This is purely anecdotal, but on the ecosystem side for a lot of our
projects I've tried to psuedo-enforce the "one commit", or really, a
change/fix/feature per commit. Thereby allowing me to cherrypick for patch
releases to stable (or revert a commit) with confidence and without a lot
of hunting
Hi Gayan,
I've added the general Juju list which covers more of these general topics.
So, because of the nature of LXC machines and Docker style application
containers it's hard to model that style application container in Juju in
the same way LXC machines work. However, it's quite easy to wrap
Thanks for the update, appreciate the consideration!
On Sat, Apr 23, 2016, 2:29 PM Alexis Bruemmer
wrote:
> Thank you all for the great feedback on 2.0! Based on this thread and
> similar feedback the juju-core dev team has made some updates to the plan
> for lxd
On Mon, Apr 18, 2016 at 11:31 PM Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> On Mon, Apr 18, 2016 at 7:57 PM, Marco Ceppi <marco.ce...@canonical.com>
> wrote:
>
>> Thanks so much for spending time on this polish! It'll really help our
>> user experi
On Mon, Apr 18, 2016, 6:12 PM Tycho Andersen
wrote:
> Hi Martin,
>
> Thanks for looking into this.
>
> On Mon, Apr 18, 2016 at 07:17:29PM +0100, Martin Packman wrote:
> > With the LXD 2.0 release at the start of last week and the prospect of
> > some stability, I
Thanks so much for spending time on this polish! It'll really help our user
experience shine for cost effective dev.
On Mon, Apr 18, 2016, 2:17 PM Martin Packman
wrote:
> When it comes to using lxd in clouds, as I understand it we've settled
> on retaining the
t, j...@lists.ubuntu.com - report issues against either
https://github.com/juju/charm-tools or
https://github.com/juju/charmstore-client ask questions in #juju on
freenode.net or on https://askubuntu.com
Thanks,
Marco Ceppi
on behalf of the Juju Charm Community Team and UI Engineering Team
--
Juju
On Wed, Apr 6, 2016 at 10:07 AM Stuart Bishop
wrote:
> On 5 April 2016 at 23:35, Martin Packman
> wrote:
>
> > The challenge here is we want Juju 2.0 and all the new functionality
> > to be the default on release, but not break our
On Tue, Apr 5, 2016 at 1:37 PM Martin Packman
wrote:
> On 05/04/2016, Adam Collard wrote:
> > Will there be a transitional release of 1.25.x that also gives us a juju1
> > binary to facilitate this?
>
> Yes, the plan entails both an
On Mon, Mar 28, 2016 at 10:12 PM Andrew Wilkins <
> andrew.wilk...@canonical.com> wrote:
>
>> On Tue, Mar 29, 2016 at 10:03 AM Marco Ceppi <marco.ce...@canonical.com>
>> wrote:
>>
>>> On Mon, Mar 28, 2016 at 9:49 PM Andrew Wilkins <
>>> andrew.wi
On Mon, Mar 28, 2016 at 9:49 PM Andrew Wilkins
wrote:
> Hi,
>
> There's a code review in progress (http://reviews.vapour.ws/r/4286/) that
> will introduce a predefined action, "juju-run", which is part of the
> replacement for the current SSH-based juju-run.
>
This
Well, an outstanding turnout, thank you everyone for your feedback. With
more than two +1 from existing charmers welcome thedac!
Thanks,
Marco Ceppi
On Mon, Mar 21, 2016 at 11:41 AM James Page <james.p...@canonical.com>
wrote:
> +1
>
> On Mon, 21 Mar 2016 at 15:37 Chris Glass
On Thu, Mar 10, 2016 at 10:28 PM Ian Booth wrote:
> So we have a feature of upgrade-charm which allows you to crossgrade to a
> different charm than the one originally deployed.
>
> From the upgrade-charm help docs:
>
> The new charm's URL and revision are inferred as
block until storage is added? We really want to be
able to support the /option/ or adding storage by the operator but we're
not sure how this functions. If we use that directory before the operator
attaches storage will it be mounted over or migrated?
Thanks,
Marco Ceppi
--
Juju-dev mailing list
Juju
This sounds very promising! Will play around with it a bit more.
On Fri, Feb 5, 2016, 7:16 PM Mark Shuttleworth <m...@ubuntu.com> wrote:
> On 05/02/16 17:47, Marco Ceppi wrote:
> > Does this require the operator to add storage at deploy time? Does this
> > mean our cha
Very exciting to see these bits landing now! I'm looking forward to the
alpha and trying out all the commands
On Wed, Feb 3, 2016 at 12:05 AM Ian Booth wrote:
> Yeah, there's a couple of places that need a bit of cleanup. With that
> one, I
> needed to double check
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
How do current customers, like dtag, who are very keen on having everything
goto syslog/rsyslog, going to keep that functionality going forward? Is
there an easy mechanism to get the logs out of mongodb?
All too often when I'm rummaging around in debug-hooks, I'll tail
/var/log/juju/unit-*.log to
ccze also works really well for colouring log output and is one less tool
we have to build/maintain. Getting some fixes to it so it better colors
juju logs would be a win I think. FWIW, I and others in eco have been using
it for a while on a variety of application outputs including juju
Marco
On
Whew, because I was about to raise some serious concern over conflating
namespaces :D
On Thu, Apr 2, 2015 at 6:47 AM, Ian Booth ian.bo...@canonical.com wrote:
Ah, yes, of course. Typo, sorry.
On 02/04/15 20:19, John Meinel wrote:
...
Hook tools
--
juju-set, used to
juju mailing list to help correct and clarify these statements and
shed some light once and for all.
Finally, once it's been known, I'll be updating the author docs to detail
the execution pattern in detail.
Thanks,
Marco Ceppi
On Sat, Aug 30, 2014 at 6:31 AM, Humphrey, Timothy L (RIS-DAY
This might be a true problem when you don't map what event should fire what
code in the hook. The majority, if not all, of charms that currently
implement this pattern do so by either using charm-helpers or by having a
giant if/else case statement at the bottom of the hook which maps which
code
I actually don't see a problem with removing apt-get upgrade, but what
apt-get update? It's only 20s user time according to the original post. For
stale cloud images, local provider and manual, it's just a no brained.
Marco
On Jul 1, 2014 4:04 PM, David Britton david.brit...@canonical.com wrote:
sure it deploys consistently and everytime on all
cloud providers. I'm in the process of writing tests for the MySQL charm so
we'll have better exposure of this issue sooner.
Thanks,
Marco Ceppi
On Thu, Feb 6, 2014 at 9:23 AM, Daniele Stroppa
daniele.stro...@joyent.comwrote:
David,
I missed
you all do. I look forward to a solution,
whatever it may be, in the future!
Marco Ceppi
On Wed, Nov 6, 2013 at 9:22 PM, Tim Penhey tim.pen...@canonical.com wrote:
On 07/11/13 15:00, Andrew Wilkins wrote:
On Thu, Nov 7, 2013 at 9:23 AM, Ian Booth ian.bo...@canonical.com
mailto:ian.bo
61 matches
Mail list logo