Hello everyone,
Here's the latest office hours, we've got some great summaries of
what's going across the teams as well as more information on what's
coming up in Juju 2.0:
https://www.youtube.com/watch?v=zPLW7cGrrjE
Our next office hours will be March 25th, you can find all that
information
Yeah I think that's about right. Currently saiku is subordinate of tomcat
so we're basically locked in, which in reality is fine as we've not tested
elsewhere but I like flexibility which is what juju relations offer.
So it would be good to create a charm that maybe as Rick suggests provides
a
The Juju team is working on a feature called "juju resources" that can be
used to provide a blob to a charm to be used in the deployment. It sounds
like it might be interesting as a way to deliver the WAR file to the Tomcat
charm. The current beta1 implemented the local version where you can
Hi Tom,
That's an interesting idea. Let me check if I understood what you said. The
subordinate WAR-charm will essentially be a place-holder for the .war file.
The interface connecting the WAR-charm and the java container would enable
the WAR-charm to say "I got this war file stored on this
>
> Does this mean it won't be possible to deploy old single-series
> charms with Juju without modifying metadata.yaml to add the supported
> series?
>
You can use the --series argument
$ juju deploy ./trusty/mysql --series trusty
We could look at pulling the series out of the path if it's an
Hey Marco
>
> I'm a +1
>
> How will bundles work which reference local charms? Will this work as
> expected where nova-compute is a directory at the same level as a bundle
> file?
>
> ```
> series: trusty
> services:
> nova-compute:
> charm: ./nova-compute
> num_units: 2
> ```
>
Okay so here's one I wanted to know if it made sense to people or not now
there are layers, interfaces etc.
Take Saiku or any other WAR based webapp. Currently our app is a Tomcat
subordinate, which installs the WAR and a few other directories and just
sed-s a few files to set some variables.
In