[01:04] <jose-phillips> hi someone have idea
[01:04] <jose-phillips> how to setup a extra interface to a lxd container while is deployed with juju
[01:05] <jose-phillips> i need add extra network to a lxd container mapped to a extra interface
[01:05] <jose-phillips> is possible do that?
[01:09] <hml> jose-phillips: you can create lxc profiles named juju-<model-name>; then deploy from a model with that name.
[01:10] <jose-phillips> how i select the container profile with juju
[01:10] <hml> jose-phillips: i do this with the localhost cloud - not sure where to setup with containers nested in other clouds
[01:10] <jose-phillips> juju deploy --to lxd:1 openstack-dashboard
[01:11] <hml> jose-phillips: juju will auto-magically look for it - it’s found by creating it.
[01:11] <hml> jose-phillips: what cloud did you bootstrap?
[01:11] <jose-phillips> maas
[01:11] <jose-phillips> and openstack
[01:12] <jose-phillips> deployed by juju
[01:12] <hml> jose-phillips: i’m not sure where the modified profile needs to exist in that case
[01:20] <hml> jose-phillips: perhaps if you check machine 1 for an lxc profile of juju-default?   juju does create an lxc profile for the models itself with a few necessary items
[01:20] <jose-phillips> yeah but the main goal is do this setting from juju controller
[01:21] <jose-phillips> so when the container is created is already setted up
[01:21] <jose-phillips> with the second interface
[15:26] <vds> is there a preferred way to install oracle java 8 in charms? I've only found thism so far: https://github.com/jamesbeedy/juju-layer-java
[15:33] <bdx> vds: that was an experiment based on layer-openjdk
[15:34] <bdx> vds: that made sense for me because I was already using layer-openjdk, but needed oracle java
[15:39] <vds> bdx, how did the experiment go? :)
[15:39] <bdx> vds: I stole the super awesome layer-openjdk code and changed the bits to make it install oracle java such that I could use it as a drop in replacement to get my charms that were already using layer-openjdk to run oracle java
[15:40] <bdx> it went well, I mean, it works
[15:40] <bdx> the side note here is that
[15:40] <bdx> I probably spent a total of 30 mins getting that to do what I needed
[15:41] <bdx> once it worked I never looked back or touched the repo again
[15:41] <bdx> its not using the practices in some places
[15:42] <bdx> best*
[15:42] <bdx> like, automatically accepting the terms and conditions for the user
[15:43] <bdx> like, you have no option to decline or accept the terms, and the charm just automatically masks and makes that decision for you
[15:43] <bdx> but, if you don't care about things like that
[15:43] <bdx> its fair game
[15:43] <bdx> vds: if you are interested in using it, I'll move it to a legit repo and give it a few touch ups
[15:43] <bdx> let me know
[15:45] <vds> bdx, the only concern I have about it is the use of the PPA
[15:47] <bdx> vds: yeah, so that is configurable through the charm config I think
[15:49] <bdx> vds: depending on what you are doing (packaging a java app) ... there is a way cooler/more better way of doing packaging/delivery for java apps now, "snaps"
[15:49] <bdx> vds: have you looked into this much?
[15:51] <vds> bdx, good suggestion, thanks
[15:52] <bdx> vds: https://docs.snapcraft.io/reference/plugins/
[15:53] <bdx> np