Hey Merlijn,
I'm a bit late to this thread, but wanted to thank you for calling out the
FOSDEM talk this year :) That was me on stage giving the overview.
Really glad you took the time to reach out and get some answers. If there's
anything else we can do for you feel free to drop by #juju on
irc.
No problem, ask away!
Op zaterdag 28 maart 2015 heeft Nick Veitch het
volgende geschreven:
> Hi,
> Thanks for the useful feedback on docs! I agree that good examples for
> Python and the charm helpers are things that are sorely missing, and
> we will address that soon.
> I don't want to burden yo
Hi,
Thanks for the useful feedback on docs! I agree that good examples for
Python and the charm helpers are things that are sorely missing, and
we will address that soon.
I don't want to burden you further, but would you mind if I emailed
you some questions about your experience with the documentat
Thanks to everyone for taking the time to answer this so thoroughly! The
project is clearly going in a direction that will be very beneficial to us.
The monitoring, multi-user and cross-platform features will come in very
handy!
I do agree with Mark that "writing charms has been poorly documented"
On Fri, Mar 27, 2015 at 8:58 AM, Mark Shuttleworth wrote:
> In my travels now I am glad to say I see a shift in the way people
> engage with us about Juju. It used to be "why would you want to compete
> with Puppet?" but now folks understand that we do not want to compete
> with Puppet, we want to
On 25/03/15 20:01, Merlijn Sebrechts wrote:
> I'm interested in what the future of Juju is. From the small experience
> I've had with it, it seems like a product with a lot of potential. It fills
> a gap in our project that no other technology can fill. Its biggest
> strength is how relations betwe
I second Nate's statement!
On Thu, Mar 26, 2015 at 9:04 AM, Nate Finch
wrote:
> I wanted to specifically thank you for pointing out the bugs that affect
> you. It's a huge help in prioritizing what we work on.
>
>
>
> On Wed, Mar 25, 2015 at 5:24 PM, Merlijn Sebrechts <
> merlijn.sebrec...@gmail
I wanted to specifically thank you for pointing out the bugs that affect
you. It's a huge help in prioritizing what we work on.
On Wed, Mar 25, 2015 at 5:24 PM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> Thanks for your answer! I didn't know Windows and Centos support was
> comin
On Thu, Mar 26, 2015 at 14:35:23, Mark Ramm-Christensen (Canonical.com) wrote:
> As promised partners making use of juju as part of the OpenStack
> Interoperability Lab (OIL) include:
>
> * IBM
> * Microsoft
> * Intel
> * AMD
> * HP
> * Juniper
> * Lenovo
> * Melan
As promised partners making use of juju as part of the OpenStack
Interoperability Lab (OIL) include:
- IBM
- Microsoft
- Intel
- AMD
- HP
- Juniper
- Lenovo
- Melanox
- Metaswitch
- OCP (Open Compute Project)
- SanDisk
- VMWare
There are actually quite a few m
On Thu, Mar 26, 2015 at 8:24 AM, Merlijn Sebrechts
wrote:
> Thanks for your answer! I didn't know Windows and Centos support was coming
> so soon, great to know!
>
> The lacking documentation is the biggest issue to me. The charm-helpers
> documentation is outdated in a lot of places and that make
Thanks for your answer! I didn't know Windows and Centos support was coming
so soon, great to know!
The lacking documentation is the biggest issue to me. The charm-helpers
documentation is outdated in a lot of places and that makes it seem as it
isn't being actively maintained anymore. Ofcourse, t
Well, I can provide a few things off the top of my head that should help.
- Canonical is fully committed to Juju as the way we deploy software
internally, the way we deploy Open Stack clouds for our largest clients
- Windows workloads are supported in the current beta version of Juju,
I'm a core dev on Juju, I can answer some, but not all of these questions.
First off, as far as long term commitment for Juju - Juju is a huge part of
Canonical's long term strategy... right up there with the Ubuntu Phone and
Ubuntu itself. The Juju team has been expanding hugely in the last coup
14 matches
Mail list logo
