Re: CDK + Deis

[Samuel Cozannet]

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 GCE and azure.

Any hints from your previous efforts? Regarding AWS integration (I believe
it is your primary target, I did publish a post on medium about it, would
love feedback)

++
Sam

On Apr 21, 2017 11:16 PM, "James Beedy"  wrote:

> 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, so I will be putting a bit more effort into finding a path
> forward for here in hopes we can get CDK running underneath.
>
> If anyone is interested in, or has done work with Deis + CDK give me a
> shout and lets match notes.
>
> I'm going to be giving it another go with the latest CDK and the latest
> Deis here this weekend/next week, hopefully I can come up with some solid
> docs at least.
>
> I'll report back with my findings~
>
> --
> 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

Inherited Constraints Causing LXD to Fail

[James Beedy]

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' constraints.

The following will succeed:

$ juju deploy ubuntu # gets machine id 0
$ juju deploy ubuntu ubuntu-lxd --to lxd:0


The following will cause the lxd deploy to fail:

$ juju deploy ubuntu --constraints "spaces=myspace" # gets machine id 0
$ juju deploy ubuntu ubuntu-lxd --to lxd:0


The odd thing about this is, that it didn't start happening until this
week. I've been harping on this use case for a while now with no such
problems, then Monday morning rolls around, I go to spin up some new lxd
envs, and nothing  I've been blocked all week from sending any deploys.

This is a critical issue for me, any help would be greatly appreciated.

https://bugs.launchpad.net/juju/+bug/1684143
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Inherited Constraints Causing LXD to Fail

[James Beedy]

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' constraints.

The following will succeed:

$ juju deploy ubuntu # gets machine id 0
$ juju deploy ubuntu ubuntu-lxd --to lxd:0


The following will cause the lxd deploy to fail:

$ juju deploy ubuntu --constraints "spaces=myspace" # gets machine id 0
$ juju deploy ubuntu ubuntu-lxd --to lxd:0


The odd thing about this is, that it didn't start happening until this
week. I've been harping on this use case for a while now with no such
problems, then Monday morning rolls around, I go to spin up some new lxd
envs, and nothing  I've been blocked all week from sending any deploys.

This is a critical issue for me, any help would be greatly appreciated.

https://bugs.launchpad.net/juju/+bug/1684143
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

CDK + Deis

[James Beedy]

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, so I will be putting a bit more effort into finding a path
forward for here in hopes we can get CDK running underneath.

If anyone is interested in, or has done work with Deis + CDK give me a
shout and lets match notes.

I'm going to be giving it another go with the latest CDK and the latest
Deis here this weekend/next week, hopefully I can come up with some solid
docs at least.

I'll report back with my findings~
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

[Patrizio Bassi]

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,
>
> 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): Dmitrii-Sh
>
> On Fri, Apr 21, 2017 at 5:12 PM, Patrizio Bassi 
> wrote:
>
>> Dear All
>>
>> this conversation led me to an interesting (for me at least!) speculation
>> about nova-compute charm.
>>
>> At the moment the nova-compute charm has "virt-type" param supporting
>> kvm, xen, uml, lxc, qemu, lxd.
>> At the same time we have nova-compute-vmware charm which is an
>> indipendent app.
>>
>> So, in case i may want to have an openstack with kvm and vmware mixed,
>> juju allows it (just talking about juju, not considering openstack
>> opportunity to have them really working).
>>
>> What if i want to have two nova-compute installations, one unit with kvm
>> and one with lxd? As far i know we cannot.
>> So it would be nice to add a feature such as:
>>
>> juju deploy  which defaults the deployed app to charm name
>> juju deploy  -name 
>>
>> so all units will be in mycustomname/00XXX format, we kee the original
>> charm reference (for upgrades for instance) and we can use multiple
>> configurations under a different "umbrella"
>>
>> ie.
>> nova-compute/0 (with default kvm)
>> nova-compute/1 (with default kvm)
>> nova-compute/2 (with default kvm)
>> mynova-compute/0 (with lxd)
>> mynova-compute/1 (with lxd)
>> mynova-compute/2 (with lxd)
>>
>> regards,
>> Patrizio
>>
>>
>> 2017-04-21 9:55 GMT+02:00 Mark Shuttleworth :
>>
>>> 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
>>>
>>
>>
>>
>> --
>>
>> Patrizio Bassi
>> www.patriziobassi.it
>> http://piazzadelpopolo.patriziobassi.it
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
> --

Patrizio Bassi
www.patriziobassi.it
http://piazzadelpopolo.patriziobassi.it
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

[Dmitrii Shcherbakov]

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): Dmitrii-Sh

On Fri, Apr 21, 2017 at 5:12 PM, Patrizio Bassi 
wrote:

> Dear All
>
> this conversation led me to an interesting (for me at least!) speculation
> about nova-compute charm.
>
> At the moment the nova-compute charm has "virt-type" param supporting kvm,
> xen, uml, lxc, qemu, lxd.
> At the same time we have nova-compute-vmware charm which is an indipendent
> app.
>
> So, in case i may want to have an openstack with kvm and vmware mixed,
> juju allows it (just talking about juju, not considering openstack
> opportunity to have them really working).
>
> What if i want to have two nova-compute installations, one unit with kvm
> and one with lxd? As far i know we cannot.
> So it would be nice to add a feature such as:
>
> juju deploy  which defaults the deployed app to charm name
> juju deploy  -name 
>
> so all units will be in mycustomname/00XXX format, we kee the original
> charm reference (for upgrades for instance) and we can use multiple
> configurations under a different "umbrella"
>
> ie.
> nova-compute/0 (with default kvm)
> nova-compute/1 (with default kvm)
> nova-compute/2 (with default kvm)
> mynova-compute/0 (with lxd)
> mynova-compute/1 (with lxd)
> mynova-compute/2 (with lxd)
>
> regards,
> Patrizio
>
>
> 2017-04-21 9:55 GMT+02:00 Mark Shuttleworth :
>
>> 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/mailm
>> an/listinfo/juju
>>
>
>
>
> --
>
> Patrizio Bassi
> www.patriziobassi.it
> http://piazzadelpopolo.patriziobassi.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: Juju deploy same application twice, failed "application already exist"

[John Meinel]

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 interesting (for me at least!) speculation
> about nova-compute charm.
>
> At the moment the nova-compute charm has "virt-type" param supporting kvm,
> xen, uml, lxc, qemu, lxd.
> At the same time we have nova-compute-vmware charm which is an indipendent
> app.
>
> So, in case i may want to have an openstack with kvm and vmware mixed,
> juju allows it (just talking about juju, not considering openstack
> opportunity to have them really working).
>
> What if i want to have two nova-compute installations, one unit with kvm
> and one with lxd? As far i know we cannot.
> So it would be nice to add a feature such as:
>
> juju deploy  which defaults the deployed app to charm name
> juju deploy  -name 
>
> so all units will be in mycustomname/00XXX format, we kee the original
> charm reference (for upgrades for instance) and we can use multiple
> configurations under a different "umbrella"
>
> ie.
> nova-compute/0 (with default kvm)
> nova-compute/1 (with default kvm)
> nova-compute/2 (with default kvm)
> mynova-compute/0 (with lxd)
> mynova-compute/1 (with lxd)
> mynova-compute/2 (with lxd)
>
> regards,
> Patrizio
>
>
> 2017-04-21 9:55 GMT+02:00 Mark Shuttleworth :
>
>> 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/mailm
>> an/listinfo/juju
>>
>
>
>
> --
>
> Patrizio Bassi
> www.patriziobassi.it
> http://piazzadelpopolo.patriziobassi.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: Juju deploy same application twice, failed "application already exist"

[Mark Shuttleworth]

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

[Paul Gear]

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 proxy that encrypts traffic using a Let's Encrypt
> certificate with optional Basic Authentication. Deploy the charm, set
> fqdn, connect to your webservice, and go! The deployed proxy gets an
> A+ ssl rating on the Qualis SSL Server Test.
>
> It's not ready yet to be promulgated but it should work fine for demo
> deployment so give it a test drive if you're interested.
>
> If anyone wants to work together on this charm to expand its scope,
> let me know! I'm thinking about stuff like pluggable authentication
> backends, pluggable DNS backends, support for more protocols such as
> websockets, ...

Hi Merlijn,

I really liked your idea, so I thought I'd give your charm a spin.  I
found a couple minor niggles, which I'll write you some bug reports
about shortly.

Overall, it worked pretty well for me, and got the promised A+ rating on
Qualys SSL Labs right out of the box.  Thanks for making the charm!

-- 
Regards,
Paul Gear
Site Reliability Engineer
Canonical - Information Systems



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