Re: Showing Juju GUI in controller model

[Merlijn Sebrechts]

Op maandag 16 januari 2017 heeft Mark Shuttleworth  het
volgende geschreven:
> On 16/01/17 11:57, Merlijn Sebrechts wrote:
>> Hi Jeff
>>
>>
>> I'd like to use lets encrypt certs with the GUI. I'm not sure how to
>> do that in a way that I don't break anything. I remember the Charm had
>> config options for ssl certs.
>>
>
> Yes, we should do the same for the controller (amongst other things you
> may want to have custom certs on the REST API and websockets too).
>
>> Another advantage of the charm is that it provided the HTTP
>> relationship so you can connect it to a reverseproxy etc..
>>
>
> We are working to have the controller and its database show up in the
> empty model that the controller uses to track its own machines. Then you
> could do exactly this :)

That's cool! Is that the first step towards the stacks functionality? You
create a charm that relates to the controller?

>
> Mark
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Showing Juju GUI in controller model

[Merlijn Sebrechts]

Exactly what I need, thanks!

Op maandag 16 januari 2017 heeft Rick Harding 
het volgende geschreven:
>
>
> On Mon, Jan 16, 2017 at 11:57 AM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
>>
>> Hi Jeff
>>
>> I'd like to use lets encrypt certs with the GUI. I'm not sure how to do
that in a way that I don't break anything. I remember the Charm had config
options for ssl certs.
>> Another advantage of the charm is that it provided the HTTP relationship
so you can connect it to a reverseproxy etc..
>
> I'm copying this from another thread. There's a form of lets encyrpt in
Juju currently that was added to Juju 2.0. I've not tried this out yet, but
will pass this info along and tomorrow I'll work on getting some notes/docs
together and give it a go.
>
https://github.com/juju/juju/blob/6cf1bc9d917a4c56d0034fd6e0d6f394d6eddb6e/controller/config.go#L46
>  copied info below
> When bootstrapping, you can set the controller config attribute
"autocert-dns-name" to a DNS name that points to your controller. If you
then use that DNS name instead of the controller's IP, or some other DNS
name, the controller will use autocert-generated certificates. By default
we use Let's Encrypt, but you can override the provider with additional
controller config.
> Once you've bootstrapped like that, clients can use the autocert-dns-name
value as the controller address, and they do not need to specify a CA
certificate for verification.
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Showing Juju GUI in controller model

[Rick Harding]

On Mon, Jan 16, 2017 at 11:57 AM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Hi Jeff
>
>
> I'd like to use lets encrypt certs with the GUI. I'm not sure how to do
> that in a way that I don't break anything. I remember the Charm had config
> options for ssl certs.
>
> Another advantage of the charm is that it provided the HTTP relationship
> so you can connect it to a reverseproxy etc..
>
>
I'm copying this from another thread. There's a form of lets encyrpt in
Juju currently that was added to Juju 2.0. I've not tried this out yet, but
will pass this info along and tomorrow I'll work on getting some notes/docs
together and give it a go.

https://github.com/juju/juju/blob/6cf1bc9d917a4c56d0034fd6e0d6f394d6eddb6e/controller/config.go#L46

 copied info below

When bootstrapping, you can set the controller config attribute
"autocert-dns-name" to a DNS name that points to your controller. If you
then use that DNS name instead of the controller's IP, or some other DNS
name, the controller will use autocert-generated certificates. By default
we use Let's Encrypt, but you can override the provider with additional
controller config.

Once you've bootstrapped like that, clients can use the autocert-dns-name
value as the controller address, and they do not need to specify a CA
certificate for verification.
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Showing Juju GUI in controller model

[Mark Shuttleworth]

On 16/01/17 11:57, Merlijn Sebrechts wrote:
> Hi Jeff
>
>
> I'd like to use lets encrypt certs with the GUI. I'm not sure how to
> do that in a way that I don't break anything. I remember the Charm had
> config options for ssl certs.
>

Yes, we should do the same for the controller (amongst other things you
may want to have custom certs on the REST API and websockets too).

> Another advantage of the charm is that it provided the HTTP
> relationship so you can connect it to a reverseproxy etc..
>

We are working to have the controller and its database show up in the
empty model that the controller uses to track its own machines. Then you
could do exactly this :)

Mark

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Orchestration charms

[Mark Shuttleworth]

On 11/01/17 07:03, Casey Marshall wrote:
>
> On Mon, Jan 9, 2017 at 11:53 AM, Simon Kollberg
> mailto:simon.kollb...@elastisys.com>>
> wrote:
>
> Right now, the user needs to manually provide credentials (via the
> charm
> config) to the CharmScaler enabling it to connect and execute
> operations on
> the Juju controller. What I would love to see is a way to make
> certain charms
> have special access - some kind of "orchestrator charm privilege"
> where the
> necessary credentials needed by the python lib would be passed to
> the charm
> automagically.
>

Yes, this fits in-roadmap with work we have outlined (called "stacks")
where a charm can take responsibility for other charms, acting more or
less as the operator does today.

Mark
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: A new development release of Juju, 2.1-beta4, is here!

[Mark Shuttleworth]

As we push to Juju 2.1 there are a couple of items that would be really
good to get testing feedback on!

On 06/01/17 15:06, Nicholas Skaggs wrote:
> Model Migration is no longer behind a feature flag

'Model migration' is key to ongoing easy and automatic upgrades on the
server. By migrating the model from a 2.n to 2.n+1 controller you will
have a very safe upgrade with rollback if safety tests don't pass. We'd
really like to help the Juju operator community move forward with Juju
releases more quickly, since there are loads of performance and
operations improvements landing at the moment, so please test model
migration. For fun, you should be able to move the same model from one
controller to another and back very reliably.

> vSphere provider improvements

Many folks have easier access to vSphere than public or private cloud
infrastructure, so we'd like to hear how you find the add-cloud and
bootstrap experiences, and how big bundles like kubernetes and hadoop
perform for you there.

Try 'juju add-cloud' and see how it goes!

> [conjure-up] New ‘Architecture’ button allows editing machine
> placement, including specifying a machine in a MAAS

Conjure-up is proving to be a superb front-end to Juju for initial
deployments of complex stuff like OpenStack. Please do try it, possibly
with Kubernetes or OpenStack. A 'spell' is a bundle with a few bells on
it, so if you have bundles that would benefit from conjuring up then
please shout if you need a hand crafting them.

Mark


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Amulet doesn't find deployed units

[Merlijn Sebrechts]

I'm sure the bundle is being deployed, I checked with `juju status`. When
that error message happens, both limeds and docker are already deployed,
even though the error happens at the first "add" line.

I'll post the debug output tomorrow.

Op maandag 16 januari 2017 heeft Tim Van Steenburgh <
tim.van.steenbu...@canonical.com> het volgende geschreven:
> You're right, deployment.add() isn't needed - the sentries get parsed out
of the real-time
> Juju status.
> Are you sure the bundle is actually being deployed before your test is
run? You can pass
> -vl DEBUG for more verbose output.
> I wonder if you need to set "bundle_deploy: true" instead of
"bundle_deploy: True"
> in your tests.yaml.
> On Mon, Jan 16, 2017 at 1:14 PM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
>>
>> Hi Tim
>> The tests for the kubernetes-core bundle don't do `deployment.add..`. I
thought that bundle was a good start for my tests since the bundle is
promulgated.. Does this mean that the tests for that bundle also won't work?
>> I added those two lines, and now I'm having the following error. The url
itself seems wrong the Charm I'm testing isn't promulgated. The bundle
itself should be correct since bundletester deployed the bundle
correctly..  You can see the bundle here:
https://github.com/IBCNServices/bundle-limeds-core
>> bundles/limeds-core$ bundletester
>> bundle
>> charm-proof
   PASS
>> 20-basic-check.py
   ERROR
>>
--
>> ERROR: bundle::20-basic-check.py
>> [/tmp/bundletester-gIybTn/limeds-core/tests/20-basic-check.py exit 1]
>> E
>> ==
>> ERROR: setUpClass (__main__.TestBundle)
>> --
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
line 58, in _get
>> response.raise_for_status()
>>   File "/usr/local/lib/python3.5/dist-packages/requests/models.py", line
893, in raise_for_status
>> raise HTTPError(http_error_msg, response=self)
>> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
https://api.jujucharms.com/v4/xenial/docker/meta/any?include=bundle-machine-count&include=bundle-metadata&include=bundle-unit-count&include=bundles-containing&include=charm-actions&include=charm-config&include=charm-metadata&include=common-info&include=extra-info&include=revision-info&include=stats&include=supported-series&include=manifest&include=tags&include=promulgated&include=perm&include=id
>> During handling of the above exception, another exception occurred:
>> Traceback (most recent call last):
>>   File "/tmp/bundletester-gIybTn/limeds-core/tests/20-basic-check.py",
line 18, in setUpClass
>> cls.deployment.add('docker')
>>   File "/usr/local/lib/python3.5/dist-packages/amulet/deployer.py", line
208, in add
>> service_name, charm, branch=branch, series=service['series'])
>>   File "/usr/local/lib/python3.5/dist-packages/amulet/charm.py", line
57, in fetch
>> series=series)
>>   File "/usr/local/lib/python3.5/dist-packages/amulet/charm.py", line
42, in get_charm
>> return Charm(with_series(charm_path, series))
>>   File "/usr/local/lib/python3.5/dist-packages/charmstore/lib.py", line
165, in __init__
>> super(Charm, self).__init__(id, api=api, timeout=timeout)
>>   File "/usr/local/lib/python3.5/dist-packages/charmstore/lib.py", line
115, in __init__
>> AVAILABLE_INCLUDES).get('Meta')
>>   File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
line 107, in _meta
>> data = self._get(url)
>>   File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
line 62, in _get
>> raise EntityNotFound(url)
>> theblues.errors.EntityNotFound:
https://api.jujucharms.com/v4/xenial/docker/meta/any?include=bundle-machine-count&include=bundle-metadata&include=bundle-unit-count&include=bundles-containing&include=charm-actions&include=charm-config&include=charm-metadata&include=common-info&include=extra-info&include=revision-info&include=stats&include=supported-series&include=manifest&include=tags&include=promulgated&include=perm&include=id
>> --
>> Ran 0 tests in 0.096s
>> FAILED (errors=1)
>> PASS: 1 ERROR: 1 Total: 2 (1.032546 sec)
>>
>>
>> 2017-01-16 18:52 GMT+01:00 Tim Van Steenburgh <
tim.van.steenbu...@canonical.com>:
>>>
>>> You need to define the services in the deployment, even if they are
already deployed
>>> by bundletester. So for example:
>>> cls.deployment.add('docker')
>>> cls.deployment.add('limeds')
>>>
>>> On Mon, Jan 16, 2017 at 10:15 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

 Hi all


 Code:
https://github.com/IBCNServices/bundle-limeds-core/blob/master/tests/20-basic-check.py

 I'm basing these tests off of the kubernetes core bundle. I want to
rely on bundle

Re: Amulet doesn't find deployed units

[Tim Van Steenburgh]

You're right, deployment.add() isn't needed - the sentries get parsed out
of the real-time
Juju status.

Are you sure the bundle is actually being deployed before your test is run?
You can pass
-vl DEBUG for more verbose output.

I wonder if you need to set "bundle_deploy: true" instead of
"bundle_deploy: True"
in your tests.yaml.

On Mon, Jan 16, 2017 at 1:14 PM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Hi Tim
>
> The tests for the kubernetes-core bundle
> 
> don't do `deployment.add..`. I thought that bundle was a good start for my
> tests since the bundle is promulgated.. Does this mean that the tests for
> that bundle also won't work?
>
> I added those two lines, and now I'm having the following error. The url
> itself seems wrong the Charm I'm testing isn't promulgated. The bundle
> itself should be correct since bundletester deployed the bundle
> correctly..  You can see the bundle here: https://github.com/
> IBCNServices/bundle-limeds-core
>
> bundles/limeds-core$ bundletester
> bundle
> charm-proof
>  PASS
> 20-basic-check.py
>  ERROR
>
> 
> --
> ERROR: bundle::20-basic-check.py
> [/tmp/bundletester-gIybTn/limeds-core/tests/20-basic-check.py exit 1]
> E
> ==
> ERROR: setUpClass (__main__.TestBundle)
> --
> Traceback (most recent call last):
>   File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
> line 58, in _get
> response.raise_for_status()
>   File "/usr/local/lib/python3.5/dist-packages/requests/models.py", line
> 893, in raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
> https://api.jujucharms.com/v4/xenial/docker/meta/any?
> include=bundle-machine-count&include=bundle-metadata&
> include=bundle-unit-count&include=bundles-containing&
> include=charm-actions&include=charm-config&include=charm-
> metadata&include=common-info&include=extra-info&include=
> revision-info&include=stats&include=supported-series&
> include=manifest&include=tags&include=promulgated&include=perm&include=id
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/tmp/bundletester-gIybTn/limeds-core/tests/20-basic-check.py",
> line 18, in setUpClass
> cls.deployment.add('docker')
>   File "/usr/local/lib/python3.5/dist-packages/amulet/deployer.py", line
> 208, in add
> service_name, charm, branch=branch, series=service['series'])
>   File "/usr/local/lib/python3.5/dist-packages/amulet/charm.py", line 57,
> in fetch
> series=series)
>   File "/usr/local/lib/python3.5/dist-packages/amulet/charm.py", line 42,
> in get_charm
> return Charm(with_series(charm_path, series))
>   File "/usr/local/lib/python3.5/dist-packages/charmstore/lib.py", line
> 165, in __init__
> super(Charm, self).__init__(id, api=api, timeout=timeout)
>   File "/usr/local/lib/python3.5/dist-packages/charmstore/lib.py", line
> 115, in __init__
> AVAILABLE_INCLUDES).get('Meta')
>   File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
> line 107, in _meta
> data = self._get(url)
>   File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
> line 62, in _get
> raise EntityNotFound(url)
> theblues.errors.EntityNotFound: https://api.jujucharms.com/v4/
> xenial/docker/meta/any?include=bundle-machine-count&
> include=bundle-metadata&include=bundle-unit-count&
> include=bundles-containing&include=charm-actions&include=
> charm-config&include=charm-metadata&include=common-info&
> include=extra-info&include=revision-info&include=stats&
> include=supported-series&include=manifest&include=tags&
> include=promulgated&include=perm&include=id
>
> --
> Ran 0 tests in 0.096s
>
> FAILED (errors=1)
>
> PASS: 1 ERROR: 1 Total: 2 (1.032546 sec)
>
>
>
> 2017-01-16 18:52 GMT+01:00 Tim Van Steenburgh <
> tim.van.steenbu...@canonical.com>:
>
>> You need to define the services in the deployment, even if they are
>> already deployed
>> by bundletester. So for example:
>>
>> cls.deployment.add('docker')
>> cls.deployment.add('limeds')
>>
>> On Mon, Jan 16, 2017 at 10:15 AM, Merlijn Sebrechts <
>> merlijn.sebrec...@gmail.com> wrote:
>>
>>> Hi all
>>>
>>>
>>> Code: https://github.com/IBCNServices/bundle-limeds-core/blob/mast
>>> er/tests/20-basic-check.py
>>>
>>> I'm basing these tests off of the kubernetes core bundle. I want to rely
>>> on bundletester to deploy the bundle and then use the deployed applications
>>> to run tests.
>>>
>>> When I run these tests, Amulet doesn't seem to find the deployed units.
>>>
>>> code:
>>>
>>> cls.docker =

Re: Amulet doesn't find deployed units

[Merlijn Sebrechts]

Hi Tim

The tests for the kubernetes-core bundle

don't do `deployment.add..`. I thought that bundle was a good start for my
tests since the bundle is promulgated.. Does this mean that the tests for
that bundle also won't work?

I added those two lines, and now I'm having the following error. The url
itself seems wrong the Charm I'm testing isn't promulgated. The bundle
itself should be correct since bundletester deployed the bundle
correctly..  You can see the bundle here:
https://github.com/IBCNServices/bundle-limeds-core

bundles/limeds-core$ bundletester
bundle
charm-proof
 PASS
20-basic-check.py
 ERROR

--
ERROR: bundle::20-basic-check.py
[/tmp/bundletester-gIybTn/limeds-core/tests/20-basic-check.py exit 1]
E
==
ERROR: setUpClass (__main__.TestBundle)
--
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
line 58, in _get
response.raise_for_status()
  File "/usr/local/lib/python3.5/dist-packages/requests/models.py", line
893, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
https://api.jujucharms.com/v4/xenial/docker/meta/any?include=bundle-machine-count&include=bundle-metadata&include=bundle-unit-count&include=bundles-containing&include=charm-actions&include=charm-config&include=charm-metadata&include=common-info&include=extra-info&include=revision-info&include=stats&include=supported-series&include=manifest&include=tags&include=promulgated&include=perm&include=id

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/bundletester-gIybTn/limeds-core/tests/20-basic-check.py", line
18, in setUpClass
cls.deployment.add('docker')
  File "/usr/local/lib/python3.5/dist-packages/amulet/deployer.py", line
208, in add
service_name, charm, branch=branch, series=service['series'])
  File "/usr/local/lib/python3.5/dist-packages/amulet/charm.py", line 57,
in fetch
series=series)
  File "/usr/local/lib/python3.5/dist-packages/amulet/charm.py", line 42,
in get_charm
return Charm(with_series(charm_path, series))
  File "/usr/local/lib/python3.5/dist-packages/charmstore/lib.py", line
165, in __init__
super(Charm, self).__init__(id, api=api, timeout=timeout)
  File "/usr/local/lib/python3.5/dist-packages/charmstore/lib.py", line
115, in __init__
AVAILABLE_INCLUDES).get('Meta')
  File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
line 107, in _meta
data = self._get(url)
  File "/usr/local/lib/python3.5/dist-packages/theblues/charmstore.py",
line 62, in _get
raise EntityNotFound(url)
theblues.errors.EntityNotFound:
https://api.jujucharms.com/v4/xenial/docker/meta/any?include=bundle-machine-count&include=bundle-metadata&include=bundle-unit-count&include=bundles-containing&include=charm-actions&include=charm-config&include=charm-metadata&include=common-info&include=extra-info&include=revision-info&include=stats&include=supported-series&include=manifest&include=tags&include=promulgated&include=perm&include=id

--
Ran 0 tests in 0.096s

FAILED (errors=1)

PASS: 1 ERROR: 1 Total: 2 (1.032546 sec)



2017-01-16 18:52 GMT+01:00 Tim Van Steenburgh <
tim.van.steenbu...@canonical.com>:

> You need to define the services in the deployment, even if they are
> already deployed
> by bundletester. So for example:
>
> cls.deployment.add('docker')
> cls.deployment.add('limeds')
>
> On Mon, Jan 16, 2017 at 10:15 AM, Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Hi all
>>
>>
>> Code: https://github.com/IBCNServices/bundle-limeds-core/blob/
>> master/tests/20-basic-check.py
>>
>> I'm basing these tests off of the kubernetes core bundle. I want to rely
>> on bundletester to deploy the bundle and then use the deployed applications
>> to run tests.
>>
>> When I run these tests, Amulet doesn't seem to find the deployed units.
>>
>> code:
>>
>> cls.docker = cls.deployment.sentry['docker']
>> cls.limeds = cls.deployment.sentry['limeds']
>> print("docker: {}".format(cls.docker))
>> for unit in cls.docker:
>> print(unit.info['public-address'])
>> print("limeds: {}".format(cls.limeds))
>> for unit in cls.limeds:
>> print(unit.info['public-address'])
>> output:
>>
>> docker: []
>> limeds: []
>>
>>
>> I expected both docker and limeds to contain one unit, since they are
>> indeed deployed.
>>
>> docker/0* active   idle   154.85.195.24
>>  30001/tcp,30002/tcp  Ready
>> limeds/0* active 

Re: Amulet doesn't find deployed units

[Tim Van Steenburgh]

You need to define the services in the deployment, even if they are already
deployed
by bundletester. So for example:

cls.deployment.add('docker')
cls.deployment.add('limeds')

On Mon, Jan 16, 2017 at 10:15 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Hi all
>
>
> Code: https://github.com/IBCNServices/bundle-limeds-
> core/blob/master/tests/20-basic-check.py
>
> I'm basing these tests off of the kubernetes core bundle. I want to rely
> on bundletester to deploy the bundle and then use the deployed applications
> to run tests.
>
> When I run these tests, Amulet doesn't seem to find the deployed units.
>
> code:
>
> cls.docker = cls.deployment.sentry['docker']
> cls.limeds = cls.deployment.sentry['limeds']
> print("docker: {}".format(cls.docker))
> for unit in cls.docker:
> print(unit.info['public-address'])
> print("limeds: {}".format(cls.limeds))
> for unit in cls.limeds:
> print(unit.info['public-address'])
> output:
>
> docker: []
> limeds: []
>
>
> I expected both docker and limeds to contain one unit, since they are
> indeed deployed.
>
> docker/0* active   idle   154.85.195.24
>  30001/tcp,30002/tcp  Ready
> limeds/0* active   idle   154.85.195.24
>   Ready. (ibcndevs/limeds)
>
>
> What am I doing wrong?
>
>
>
> Kind regards
> Merlijn
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Showing Juju GUI in controller model

[Merlijn Sebrechts]

Hi Jeff


I'd like to use lets encrypt certs with the GUI. I'm not sure how to do
that in a way that I don't break anything. I remember the Charm had config
options for ssl certs.

Another advantage of the charm is that it provided the HTTP relationship so
you can connect it to a reverseproxy etc..



Kind regards
Merlijn

2017-01-16 17:50 GMT+01:00 Jeff Pihach :

> Hi Merlijn,
>
> In Juju 2 the GUI is actually being served directly from the controller,
> the charm isn't being deployed. The GUI charm is now only necessary in Juju
> 1.
>
> Were there features of the GUI charm you would like to see when the GUI is
> served directly from the controller?
>
> Thanks,
> Jeff
>
> On Mon, Jan 16, 2017 at 12:54 PM, Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Hi all
>>
>>
>> When I create a controller, the Juju GUI is automatically installed on
>> machine 0 of the controller model. However, the Juju GUI charm is not
>> visible in the model. Is there any way to view/change this Charm? Is there
>> a reason why the Charm isn't shown by default?
>>
>>
>>
>> Kind regards
>> Merlijn
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Showing Juju GUI in controller model

[Jeff Pihach]

Hi Merlijn,

In Juju 2 the GUI is actually being served directly from the controller,
the charm isn't being deployed. The GUI charm is now only necessary in Juju
1.

Were there features of the GUI charm you would like to see when the GUI is
served directly from the controller?

Thanks,
Jeff

On Mon, Jan 16, 2017 at 12:54 PM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Hi all
>
>
> When I create a controller, the Juju GUI is automatically installed on
> machine 0 of the controller model. However, the Juju GUI charm is not
> visible in the model. Is there any way to view/change this Charm? Is there
> a reason why the Charm isn't shown by default?
>
>
>
> Kind regards
> Merlijn
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Amulet doesn't find deployed units

[Merlijn Sebrechts]

Hi all


Code:
https://github.com/IBCNServices/bundle-limeds-core/blob/master/tests/20-basic-check.py

I'm basing these tests off of the kubernetes core bundle. I want to rely on
bundletester to deploy the bundle and then use the deployed applications to
run tests.

When I run these tests, Amulet doesn't seem to find the deployed units.

code:

cls.docker = cls.deployment.sentry['docker']
cls.limeds = cls.deployment.sentry['limeds']
print("docker: {}".format(cls.docker))
for unit in cls.docker:
print(unit.info['public-address'])
print("limeds: {}".format(cls.limeds))
for unit in cls.limeds:
print(unit.info['public-address'])
output:

docker: []
limeds: []


I expected both docker and limeds to contain one unit, since they are
indeed deployed.

docker/0* active   idle   154.85.195.24
 30001/tcp,30002/tcp  Ready
limeds/0* active   idle   154.85.195.24
Ready. (ibcndevs/limeds)


What am I doing wrong?



Kind regards
Merlijn
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Kubernetes icon

[Anthony Dillon]

Funny you should mention that Tom. The branch that landed a few days ago
updated the kubernetes link to /canonical-kubernetes and the spark link
to /spark.

The list was generated before we had a promulgated spark charm.

On Mon, 16 Jan 2017 at 11:27 John Meinel  wrote:

> Searching for "spark" the first response is:
>  https://jujucharms.com/apache-spark/10
>
> But you're right that the little icon that you see in the quick list is
> asanjar/spark. I wonder if it happened to be used more often than the
> official one. I don't know how that list is generated.
>
> John
> =:->
>
> On Mon, Jan 16, 2017 at 3:22 PM, Tom Barber  wrote:
>
> whilst we're on it
>
> Why when you click spark do you end up at:
> https://jujucharms.com/u/asanjar/spark/ and not cs:apache-spark or
> whatever the mainline one is?
>
> :)
>
> Tom
>
> On Mon, Jan 16, 2017 at 11:20 AM, John Meinel 
> wrote:
>
> Also, if you click the link, it tells you 404, maybe you want something
> else. It looks like it switched from being called "kubernetes" to being
> called "kubernetes-core", and the quick link didn't get updated.
>
> John
> =:->
>
>
> On Mon, Jan 16, 2017 at 3:17 PM, Anthony Dillon <
> anthony.dil...@canonical.com> wrote:
>
> Thanks Tom,
>
> A fix for the broken link has landed a few days ago. Therefore will be
> fixed with the next release.
>
> All the best,
> Ant.
>
> On Mon, 16 Jan 2017 at 10:40 Tom Barber  wrote:
>
> Canonical-ers,
>
> Has anyone clocked the k8s icon in the search box on jujucharms.com has
> been broken for about 2 months?
>
> Tom
>
> --
> Tom Barber
> CTO Spicule LTD
> t...@spicule.co.uk
>
> http://spicule.co.uk
>
> @spiculeim 
>
> Schedule a meeting with me 
>
> GB: +44(0)5603641316 <+44%2056%200364%201316>
> US: +18448141689 <(844)%20814-1689>
>
> 
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
>
>
>
> --
> Tom Barber
> CTO Spicule LTD
> t...@spicule.co.uk
>
> http://spicule.co.uk
>
> @spiculeim 
>
> Schedule a meeting with me 
>
> GB: +44(0)5603641316 <+44%2056%200364%201316>
> US: +18448141689 <(844)%20814-1689>
>
> 
>
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Kubernetes icon

[John Meinel]

Searching for "spark" the first response is:
 https://jujucharms.com/apache-spark/10

But you're right that the little icon that you see in the quick list is
asanjar/spark. I wonder if it happened to be used more often than the
official one. I don't know how that list is generated.

John
=:->

On Mon, Jan 16, 2017 at 3:22 PM, Tom Barber  wrote:

> whilst we're on it
>
> Why when you click spark do you end up at: https://jujucharms.com/u/
> asanjar/spark/ and not cs:apache-spark or whatever the mainline one is?
>
> :)
>
> Tom
>
> On Mon, Jan 16, 2017 at 11:20 AM, John Meinel 
> wrote:
>
>> Also, if you click the link, it tells you 404, maybe you want something
>> else. It looks like it switched from being called "kubernetes" to being
>> called "kubernetes-core", and the quick link didn't get updated.
>>
>> John
>> =:->
>>
>>
>> On Mon, Jan 16, 2017 at 3:17 PM, Anthony Dillon <
>> anthony.dil...@canonical.com> wrote:
>>
>>> Thanks Tom,
>>>
>>> A fix for the broken link has landed a few days ago. Therefore will be
>>> fixed with the next release.
>>>
>>> All the best,
>>> Ant.
>>>
>>> On Mon, 16 Jan 2017 at 10:40 Tom Barber  wrote:
>>>
 Canonical-ers,

 Has anyone clocked the k8s icon in the search box on jujucharms.com
 has been broken for about 2 months?

 Tom

 --
 Tom Barber
 CTO Spicule LTD
 t...@spicule.co.uk

 http://spicule.co.uk

 @spiculeim 

 Schedule a meeting with me 

 GB: +44(0)5603641316 <+44%2056%200364%201316>
 US: +18448141689 <(844)%20814-1689>

 
 --
 Juju mailing list
 Juju@lists.ubuntu.com
 Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
 an/listinfo/juju

>>>
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/juju
>>>
>>>
>>
>
>
> --
> Tom Barber
> CTO Spicule LTD
> t...@spicule.co.uk
>
> http://spicule.co.uk
>
> @spiculeim 
>
> Schedule a meeting with me 
>
> GB: +44(0)5603641316
> US: +18448141689
>
> 
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Kubernetes icon

[Tom Barber]

whilst we're on it

Why when you click spark do you end up at:
https://jujucharms.com/u/asanjar/spark/ and not cs:apache-spark or whatever
the mainline one is?

:)

Tom

On Mon, Jan 16, 2017 at 11:20 AM, John Meinel 
wrote:

> Also, if you click the link, it tells you 404, maybe you want something
> else. It looks like it switched from being called "kubernetes" to being
> called "kubernetes-core", and the quick link didn't get updated.
>
> John
> =:->
>
>
> On Mon, Jan 16, 2017 at 3:17 PM, Anthony Dillon <
> anthony.dil...@canonical.com> wrote:
>
>> Thanks Tom,
>>
>> A fix for the broken link has landed a few days ago. Therefore will be
>> fixed with the next release.
>>
>> All the best,
>> Ant.
>>
>> On Mon, 16 Jan 2017 at 10:40 Tom Barber  wrote:
>>
>>> Canonical-ers,
>>>
>>> Has anyone clocked the k8s icon in the search box on jujucharms.com has
>>> been broken for about 2 months?
>>>
>>> Tom
>>>
>>> --
>>> Tom Barber
>>> CTO Spicule LTD
>>> t...@spicule.co.uk
>>>
>>> http://spicule.co.uk
>>>
>>> @spiculeim 
>>>
>>> Schedule a meeting with me 
>>>
>>> GB: +44(0)5603641316 <+44%2056%200364%201316>
>>> US: +18448141689 <(844)%20814-1689>
>>>
>>> 
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/juju
>>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>


-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim 

Schedule a meeting with me 

GB: +44(0)5603641316
US: +18448141689


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Kubernetes icon

[John Meinel]

Also, if you click the link, it tells you 404, maybe you want something
else. It looks like it switched from being called "kubernetes" to being
called "kubernetes-core", and the quick link didn't get updated.

John
=:->


On Mon, Jan 16, 2017 at 3:17 PM, Anthony Dillon <
anthony.dil...@canonical.com> wrote:

> Thanks Tom,
>
> A fix for the broken link has landed a few days ago. Therefore will be
> fixed with the next release.
>
> All the best,
> Ant.
>
> On Mon, 16 Jan 2017 at 10:40 Tom Barber  wrote:
>
>> Canonical-ers,
>>
>> Has anyone clocked the k8s icon in the search box on jujucharms.com has
>> been broken for about 2 months?
>>
>> Tom
>>
>> --
>> Tom Barber
>> CTO Spicule LTD
>> t...@spicule.co.uk
>>
>> http://spicule.co.uk
>>
>> @spiculeim 
>>
>> Schedule a meeting with me 
>>
>> GB: +44(0)5603641316 <+44%2056%200364%201316>
>> US: +18448141689 <(844)%20814-1689>
>>
>> 
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Kubernetes icon

[Anthony Dillon]

Thanks Tom,

A fix for the broken link has landed a few days ago. Therefore will be
fixed with the next release.

All the best,
Ant.

On Mon, 16 Jan 2017 at 10:40 Tom Barber  wrote:

> Canonical-ers,
>
> Has anyone clocked the k8s icon in the search box on jujucharms.com has
> been broken for about 2 months?
>
> Tom
>
> --
> Tom Barber
> CTO Spicule LTD
> t...@spicule.co.uk
>
> http://spicule.co.uk
>
> @spiculeim 
>
> Schedule a meeting with me 
>
> GB: +44(0)5603641316 <+44%2056%200364%201316>
> US: +18448141689 <(844)%20814-1689>
>
> 
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Showing Juju GUI in controller model

[Merlijn Sebrechts]

Hi all


When I create a controller, the Juju GUI is automatically installed on
machine 0 of the controller model. However, the Juju GUI charm is not
visible in the model. Is there any way to view/change this Charm? Is there
a reason why the Charm isn't shown by default?



Kind regards
Merlijn
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Kubernetes icon

[Tom Barber]

Canonical-ers,

Has anyone clocked the k8s icon in the search box on jujucharms.com has
been broken for about 2 months?

Tom

-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim 

Schedule a meeting with me 

GB: +44(0)5603641316
US: +18448141689


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju