Re: Juju deploy same application twice, failed "application already exist"

On 20/04/17 13:36, fengxia wrote: > > I c. So I should have used add-unit command instead of "deploy". Is > that right? > Yup :) -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju

Re: A+ HTTPS with the SSL termination proxy

On 21/04/17 01:28, Merlijn Sebrechts wrote: > Hi all > > > Want to have A+ HTTPS for your juju-managed webservice? Want to secure > a webservice with a password? The SSL termination proxy charm > to your > rescue! > > It's a reverse

Re: Juju deploy same application twice, failed "application already exist"

You can already do that without the extra flag: juju deploy app [name] You can name any app any name, we just default to the app name if it is not supplied. John =:-> On Apr 21, 2017 18:12, "Patrizio Bassi" wrote: > Dear All > > this conversation led me to an

Re: Juju deploy same application twice, failed "application already exist"

Patrizio, In a bundle: nova-compute-kvm: charm: cs:xenial/nova-compute ... options: ... virt-type: kvm nova-compute-lxd: charm: cs:xenial/nova-compute ... options: ... virt-type: lxd Best Regards, Dmitrii Shcherbakov Field Software Engineer IRC (freenode):

Re: Juju deploy same application twice, failed "application already exist"

Fantastic! I checked the docs but i didn't find that using different name could allow multiple instances I will test asap to check if i can deal with it. Thank you! Patrizio Il giorno ven 21 apr 2017 alle 16:24 Dmitrii Shcherbakov < dmitrii.shcherba...@canonical.com> ha scritto: > Patrizio,

CDK + Deis

Wondering if there is any interest out in running Deis on top of CDK? I was able to get Deis working atop CDK with some elbow grease and some inside info from @lazyPower a while back, but it was a bit rough. One of the departments in my company insists on running/deploying their apps using Deis,

Inherited Constraints Causing LXD to Fail

It looks like any LXD I deploy to an instance on AWS is now inheriting the constraints from the host, this is causing my LXD to fail across the board. This is slightly difficult to reproduce, as you must have spaces and subnets defined on AWS. This bug does not show do not add any 'spaces'

Re: CDK + Deis

Hi James, Deis is definitely on my map, I am happy to participate in the effort. Afaik, the 2 main issues are * getting Postgresql and Minio to have persistent storage. * Managing the expectation of ELB vs Ingress. This is pretty easy on AWS, I guess a little less on the metal bc LB. Not sure on

Inherited Constraints Causing LXD to Fail

It looks like any LXD I deploy to an instance on AWS is now inheriting the constraints from the host, this is causing my LXD to fail across the board. This is slightly difficult to reproduce, as you must have spaces and subnets defined on AWS. This bug does not show do not add any 'spaces'