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

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

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

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

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

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 > >

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

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

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

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,

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

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

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