In earlier versions of the Juju-gui it was easy and simple to deploy a charm,
by just dragging and dropping it into the canvas and hit commit.
With the latest versions the same process it is no more intuitive how to deploy
anymore. I hit “confirm” and “commit” and nothing happens. I have
Funny you should ask, but putting constraints directly in the charm's
metadata.yaml is a feature we are planning to work on this cycle. Charm
authors will be able to set default constraints for their charm, so that if
you know your charm needs 2GB of RAM to work properly, for example, you can
set
Hey,
We are currently in the Ubuntu Online Summit, and there will be a session
about the Juju GUI and how it's developing on Friday, don't have the exact
time handy since I'm on mobile. Probably that would be a great time to ask!
--
José Antonio Rey
On Nov 12, 2014 11:16 AM, Nate Finch
On 12/11/14 15:57, Stein Myrseth wrote:
With the latest versions the same process it is no more intuitive how to
deploy anymore. I hit “confirm” and “commit” and nothing happens. I have
create a machine first, or auto place, or add the constraints or as part of
the unit configuration, or as
On Wed, 12 Nov 2014, Stein Myrseth wrote:
In earlier versions of the Juju-gui it was easy and simple to deploy a
charm, by just dragging and dropping it into the canvas and hit commit.
With the latest versions the same process it is no more intuitive how to
deploy anymore. I hit “confirm”
Hi Stein,
The friday session that Jose mentioned is this one:
http://summit.ubuntu.com/uos-1411/meeting/22387/whats-new-and-upcoming-in-the-work-of-juju-ui-engineering/
Thanks
Matty
On Wed, Nov 12, 2014 at 4:58 PM, Richard Harding rick.hard...@canonical.com
wrote:
On Wed, 12 Nov 2014,
