Re: Elasticsearch Charm Promulgation

2017-08-31 Thread Tim Van Steenburgh
It's been promulgated, thanks!

On Wed, Aug 30, 2017 at 7:08 PM, Haw Loeung 
wrote:

> On Wed, Aug 30, 2017 at 02:38:42PM -0400, Tim Van Steenburgh wrote:
> > I checked with James Beedy and he's +1 on promulgating this one too.
> >
> > Looks like there's no bugs-url or homepage set on the charm though.
> Please
> > add those (see `charm set -h`) and then I'll be happy to promulgate it.
>
> I've updated the two:
>
> | $ charm show cs:~elasticsearch-charmers/elasticsearch bugs-url homepage
> | bugs-url: https://bugs.launchpad.net/elasticsearch-charm
> | homepage: https://launchpad.net/elasticsearch-charm
>
>
> Regards,
>
> Haw
>
> --
> 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


Newbie Question: How do I replace a machine in a deployed Model?

2017-08-31 Thread Raghurama Bhat
Hi,

I have a newbie question. I deployed a two node Kubernetes Core Cluster using 
Juju  into a MaaS Setup.   Now if I one of the Machine has a hardware failure, 
What is the process for replacing it with another machine? Does Juju controller 
monitor the cluster and request MaaS for a new machine if it detects one of the 
machines is gone? Even if this has to be done manually, I did not see a 
replace-machine option to Juju. Only add and remove units and machines. How 
does this work?

Thanks,

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


Re: Juju-gui only show localhost as the deployment option

2017-08-31 Thread John Meinel
Supporting multiple 'projects' in Openstack should already be supported by
passing different credentials during "juju add-model".

John
=:->

On Thu, Aug 31, 2017 at 1:55 AM, Giuseppe Attardi 
wrote:

> I have a slightly different requirement.
> Currently in our OpenStack cloud, if a user wants to use Juju, it must
> install a Juju controller in his project.
> It would be useful to use a single controller for the whole cloud and to
> just switch the project which the controller uses.
> Juju already can deal with multiple models, so it would just need to
> distinguish which models exist in a given project.
> It also should be possible to authenticate with OpenStack credentials in
> the Juju GUI.
>
> — Beppe
>
> > Date: Tue, 29 Aug 2017 19:29:14 +0530
> > From: Akshat Jiwan Sharma 
> > To: juju@lists.ubuntu.com
> > Subject: Juju-gui only show localhost as the deployment option
> > Message-ID:
> >gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Is there a way I can configure multiple providers using the Juju-GUI?
> Also
> > is there a way I can configure cloud providers based on user access
> roles?
> > For example a user with access to a particular model can deploy only to a
> > specific cloud provider.
> >
> > If one controller can manage multiple clouds and one controller can have
> > many users then what is the mapping of the relationship between the users
> > and the clouds?
> >
> > Thanks,
> > Akshat
> >
>
>
>
> --
> 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: Juju-gui only show localhost as the deployment option

2017-08-31 Thread Giuseppe Attardi

> On 31 ago 2017, at 17:24, John Meinel  wrote:
> 
> Supporting multiple 'projects' in Openstack should already be supported by 
> passing different credentials during "juju add-model”.

Good point, thank you.

--

> 
> John
> =:->
> 
> On Thu, Aug 31, 2017 at 1:55 AM, Giuseppe Attardi  > wrote:
> I have a slightly different requirement.
> Currently in our OpenStack cloud, if a user wants to use Juju, it must 
> install a Juju controller in his project.
> It would be useful to use a single controller for the whole cloud and to just 
> switch the project which the controller uses.
> Juju already can deal with multiple models, so it would just need to 
> distinguish which models exist in a given project.
> It also should be possible to authenticate with OpenStack credentials in the 
> Juju GUI.
> 
> — Beppe
> 
> > Date: Tue, 29 Aug 2017 19:29:14 +0530
> > From: Akshat Jiwan Sharma  > >
> > To: juju@lists.ubuntu.com 
> > Subject: Juju-gui only show localhost as the deployment option
> > Message-ID:
> >> >
> > Content-Type: text/plain; charset="utf-8"
> >
> > Is there a way I can configure multiple providers using the Juju-GUI? Also
> > is there a way I can configure cloud providers based on user access roles?
> > For example a user with access to a particular model can deploy only to a
> > specific cloud provider.
> >
> > If one controller can manage multiple clouds and one controller can have
> > many users then what is the mapping of the relationship between the users
> > and the clouds?
> >
> > Thanks,
> > Akshat
> >
> 
> 
> 
> --
> 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


How to use LXC local image for new machine

2017-08-31 Thread fengxia

Hi Juju,

I'm using `localhost` provider for dev test. I have create a LXD 
controller, and each time `juju deploy` will create a new container 
(series/trusty).


I'm experimenting to use a local image so `juju deploy` can use. So far:

1. Created an image, "gold-copy"

2. `lxc image alias create trusty [hash]`, also created alias 
`ubuntu-trusty`


But no avail. Juju will continue to download a `ubuntu-trusty` image to 
use.


Any advice here?

btw, the ultimate goal is to shorten the cycle of getting a new machine. 
The thought is to provide a customized image that has packages 
pre-loaded, eg python, python-dev, and a few charm libs.


I also read somewhere about juju using `clone-image`? Any detail on this 
function?


--
Feng xia
Engineer
Lenovo USA

Phone: 5088011794
fx...@lenovo.com

Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums


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


How to use LXC local image for new machine

2017-08-31 Thread fengxia

Hi Juju,

I'm using `localhost` provider for dev test. I have create a LXD 
controller, and each time `juju deploy` will create a new container 
(series/trusty).


I'm experimenting to use a local image so `juju deploy` can use. So far:

1. Created an image, "gold-copy"

2. `lxc image alias create trusty [hash]`, also created alias 
`ubuntu-trusty`


But no avail. Juju will continue to download a `ubuntu-trusty` image to 
use.


Any advice here?

btw, the ultimate goal is to shorten the cycle of getting a new machine. 
The thought is to provide a customized image that has packages 
pre-loaded, eg python, python-dev, and a few charm libs.


I also read somewhere about juju using `clone-image`? Any detail on this 
function?


--
Feng xia
Engineer
Lenovo USA

Phone: 5088011794
fx...@lenovo.com

Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums


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


kubectl run

2017-08-31 Thread Micheal B
Trying to convert a Docker run to kubectl

 

Working thru

 

https://hub.docker.com/r/ibmcom/db2express-c/

 

docker run -it -p 5:5 -e DB2INST1_PASSWORD=db2inst1-pwd -e 
LICENSE=accept ibmcom/db2express-c:latest bash

 

 

in Docker I have it running great just need to figure out the Kubectl run 
translation 

 

I thought that

kubectl run db2express-c --image=db2express-c --port=5 --command -e 
DB2INST1_PASSWORD=db2inst1 -e LICENSE=accept ibmcom/db2express-c:latest bash 
--generator=run-pod/v1 

 

but that fails…

 

 

thanks

 

Micheal

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


Re: How to use LXC local image for new machine

2017-08-31 Thread fengxia
According to https://bugs.launchpad.net/juju/+bug/1650651, juju 2.1 
supports using local image if its alias is `juju/series/arch` format.


So following this, I created a local image and gave it an alias of this 
format, but juju deploy will still download ubuntu-trusty before 
creating the container.


Below is dump from `lxc image [image-name] info`:

fengxia@local-charmdev:~/workspace/wss$ lxc image info trusty
Fingerprint: 
203a6ae7d45cbe5c1411ad3f17b9b2429cb5ddfec69019fa96ce5710c4871504

Size: 365.92MB
Architecture: x86_64
Public: no
Timestamps:
Uploaded: 2017/08/31 14:32 UTC
Expires: never
Last used: never
Properties:
label: release
os: ubuntu
release: trusty
serial: 20170811
version: 14.04
architecture: amd64
description: ubuntu 14.04 LTS amd64 (release) (20170811)
Aliases:
- gold-image (gold-image)
- trusty (trusty)
- juju/trusty/amd64 (juju/trusty/amd64)
Auto update: disabled



On 08/31/2017 02:20 PM, fengxia wrote:

Hi Juju,

I'm using `localhost` provider for dev test. I have create a LXD 
controller, and each time `juju deploy` will create a new container 
(series/trusty).


I'm experimenting to use a local image so `juju deploy` can use. So far:

1. Created an image, "gold-copy"

2. `lxc image alias create trusty [hash]`, also created alias 
`ubuntu-trusty`


But no avail. Juju will continue to download a `ubuntu-trusty` image 
to use.


Any advice here?

btw, the ultimate goal is to shorten the cycle of getting a new 
machine. The thought is to provide a customized image that has 
packages pre-loaded, eg python, python-dev, and a few charm libs.


I also read somewhere about juju using `clone-image`? Any detail on 
this function?




--
Feng xia
Engineer
Lenovo USA

Phone: 5088011794
fx...@lenovo.com

Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums

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


Re: kubectl run

2017-08-31 Thread Tim Van Steenburgh
This works for me:

kubectl run -it db2express-c --port=5 --env DB2INST1_PASSWORD=db2inst1
--env LICENSE=accept --image ibmcom/db2express-c:latest -- bash

On Thu, Aug 31, 2017 at 3:17 PM, Micheal B  wrote:

> Trying to convert a Docker run to kubectl
>
>
>
> Working thru
>
>
>
> https://hub.docker.com/r/ibmcom/db2express-c/
>
>
>
> docker run -it -p 5:5 -e DB2INST1_PASSWORD=db2inst1-pwd -e
> LICENSE=accept ibmcom/db2express-c:latest bash
>
>
>
>
>
> in Docker I have it running great just need to figure out the Kubectl run
> translation
>
>
>
> I thought that
>
> kubectl run db2express-c --image=db2express-c --port=5 --command -e
> DB2INST1_PASSWORD=db2inst1 -e LICENSE=accept ibmcom/db2express-c:latest
> bash --generator=run-pod/v1
>
>
>
> but that fails…
>
>
>
>
>
> thanks
>
>
>
> Micheal
>
> --
> 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


remove-application openstack-dashboard

2017-08-31 Thread Giuseppe Attardi
I am not able to remove an openstack-dashboard application from a model, 
because apparently there is no registered hook for stop in the charm and the 
log shows:

INFO juju-log Unknown hook stop - skipping.

and juju status shows:

App  Version  Status  Scale  Charm
Store   Rev  OS   Notes
openstack-dashboard  11.0.2   terminated  1  openstack-dashboard  
jujucharms  247  ubuntu

UnitWorkloadAgent  Machine   Public address 
 Ports   Message
openstack-dashboard/2*  terminated  executing  1/lxd/12  90.147.161.39   
80/tcp,443/tcp  (stop)

How can I get rid of it?

—




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


Re: kubectl run

2017-08-31 Thread Micheal B
Thank you! 

 

From: Tim Van Steenburgh 
Date: Thursday, August 31, 2017 at 3:33 PM
To: Micheal B 
Cc: juju 
Subject: Re: kubectl run

 

This works for me:

 

kubectl run -it db2express-c --port=5 --env DB2INST1_PASSWORD=db2inst1 
--env LICENSE=accept --image ibmcom/db2express-c:latest -- bash

 

On Thu, Aug 31, 2017 at 3:17 PM, Micheal B  wrote:

Trying to convert a Docker run to kubectl

 

Working thru

 

https://hub.docker.com/r/ibmcom/db2express-c/

 

docker run -it -p 5:5 -e DB2INST1_PASSWORD=db2inst1-pwd -e 
LICENSE=accept ibmcom/db2express-c:latest bash

 

 

in Docker I have it running great just need to figure out the Kubectl run 
translation 

 

I thought that

kubectl run db2express-c --image=db2express-c --port=5 --command -e 
DB2INST1_PASSWORD=db2inst1 -e LICENSE=accept ibmcom/db2express-c:latest bash 
--generator=run-pod/v1 

 

but that fails…

 

 

thanks

 

Micheal


--
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: remove-application openstack-dashboard

2017-08-31 Thread Rick Harding
Is it alone on that container on machine 1 - container 12? If so you can

juju remove-machine --force 1/lxd/12

On Thu, Aug 31, 2017 at 8:08 PM Giuseppe Attardi 
wrote:

> I am not able to remove an openstack-dashboard application from a model,
> because apparently there is no registered hook for stop in the charm and
> the log shows:
>
> INFO juju-log Unknown hook stop - skipping.
>
> and juju status shows:
>
> App  Version  Status  Scale  Charm
> Store   Rev  OS   Notes
> openstack-dashboard  11.0.2   terminated  1  openstack-dashboard
> jujucharms  247  ubuntu
>
> UnitWorkloadAgent  Machine   Public
> address  Ports   Message
> openstack-dashboard/2*  terminated  executing  1/lxd/12  90.147.161.39
>  80/tcp,443/tcp  (stop)
>
> How can I get rid of it?
>
> —
>
>
>
>
> --
> 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: remove-application openstack-dashboard

2017-08-31 Thread James Hebden
Also, when in this situation, sometimes a unit agent restart can force a
failure, at which point you can force the unit to resolve and typically
it will be cleaned up.

But the remove-machine --force is a definitely a better option if it's
along on the machine.

Use the --force, Luke.

On Fri, Sep 01, 2017 at 12:52:03AM +, Rick Harding wrote:
> Is it alone on that container on machine 1 - container 12? If so you can
> 
> juju remove-machine --force 1/lxd/12
> 
> On Thu, Aug 31, 2017 at 8:08 PM Giuseppe Attardi 
> wrote:
> 
> > I am not able to remove an openstack-dashboard application from a model,
> > because apparently there is no registered hook for stop in the charm and
> > the log shows:
> >
> > INFO juju-log Unknown hook stop - skipping.
> >
> > and juju status shows:
> >
> > App  Version  Status  Scale  Charm
> > Store   Rev  OS   Notes
> > openstack-dashboard  11.0.2   terminated  1  openstack-dashboard
> > jujucharms  247  ubuntu
> >
> > UnitWorkloadAgent  Machine   Public
> > address  Ports   Message
> > openstack-dashboard/2*  terminated  executing  1/lxd/12  90.147.161.39
> >  80/tcp,443/tcp  (stop)
> >
> > How can I get rid of it?
> >
> > —
> >
> >
> >
> >
> > --
> > 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


-- 
James Hebden
Cloud Reliability Engineer
BootStack Squad @ Canonical Ltd.

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


Re: remove-application openstack-dashboard

2017-08-31 Thread Giuseppe Attardi
Unfortunately it is not alone.

—

> On 01 set 2017, at 02:52, Rick Harding  wrote:
> 
> Is it alone on that container on machine 1 - container 12? If so you can 
> 
> juju remove-machine --force 1/lxd/12 
> 
> On Thu, Aug 31, 2017 at 8:08 PM Giuseppe Attardi  > wrote:
> I am not able to remove an openstack-dashboard application from a model, 
> because apparently there is no registered hook for stop in the charm and the 
> log shows:
> 
> INFO juju-log Unknown hook stop - skipping.
> 
> and juju status shows:
> 
> App  Version  Status  Scale  Charm
> Store   Rev  OS   Notes
> openstack-dashboard  11.0.2   terminated  1  openstack-dashboard  
> jujucharms  247  ubuntu
> 
> UnitWorkloadAgent  Machine   Public 
> address  Ports   Message
> openstack-dashboard/2*  terminated  executing  1/lxd/12  90.147.161.39   
> 80/tcp,443/tcp  (stop)
> 
> How can I get rid of it?
> 
> —
> 
> 
> 
> 
> --
> 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