Hello, Charles.
Thanks for your response.
I will wait for your blog post.
I'm going to play with chef and juju, and maybe it will give some interesting
results.
Good luck to you!
--
Best Regards,
Egor
On Wednesday 17 December 2014 at 00:41, Charles Butler wrote:
Egor,
With regards to
By the way, here is my first algorithm:
1. Install juju on server
2. Provide LXC-support
3. Generate manual configuration
4. Create at least one container for juju services
5. Then create n+1 machines, described in data bag
6. Add all of them to environment and make juju-deploy
--
Best Regards,
Greetings,
I composed a short 7 minute demo video illustrating some great work by
hazmat at bringing Flannel and ETCD to Juju for container networking
cross-host.
The short of this is it sets up a peer to peer network through a UDP
tun/tap device attached to the LXC bridge. The Flannel charm
Hi.
Can anyone think of a way for a peer relationship-broken hook to
detect that the entire service is being destroyed, rather than just a
unit or two being removed?
I have just added a peer relationship-broken hook to my Cassandra
charm, so when a unit is removed the node is decommissioned
A few questions:
For clarity - when you say generate manual configuration - is this going to
be a manual provider environment?
Where does the bootstrap server live? is this going to be a separate
service defined in your infrastructure, controlled by chef?
When it comes to deploying the
Folks, I just wanted to share my experience with Juju during the last few
months using it for real at work. I know it's pretty long but stay with me
as I wanted to see if some of these points are bugs, design decisions or if
we could simply to talk about them :-)
General:
1. Seems that if you
On Wed, 17 Dec 2014, Caio Begotti wrote:
Folks, I just wanted to share my experience with Juju during the last few
months using it for real at work. I know it's pretty long but stay with me
as I wanted to see if some of these points are bugs, design decisions or if
we could simply to talk
On 18/12/14 11:24, Caio Begotti wrote:
Folks, I just wanted to share my experience with Juju during the last
few months using it for real at work. I know it's pretty long but stay
with me as I wanted to see if some of these points are bugs, design
decisions or if we could simply to talk about
On Wed, Dec 17, 2014 at 8:47 PM, Tim Penhey tim.pen...@canonical.com
wrote:
1. Seems that if you happen to have more than... say, 30 machines, Juju
starts behaving weirdly until you remove unused machines. One of the
weird things is that new deploys all stay stuck with a pending status.
I spent most of my Review Queue time triaging charms that FAIL the
automated testing tools. The CI team has built us a report that shows
which charms PASS or FAIL on multiple cloud environments.
If you are interested in which charms are failing or if you are interested
in helping fix a charm you
Wow, what a great email and fantastic feedback. I'm going to attempt to
reply and address each item inline below.
I'm curious, what version of Juju are you currently using?
On Wed Dec 17 2014 at 5:25:08 PM Caio Begotti caio1...@gmail.com wrote:
Folks, I just wanted to share my experience with
On Wed, Dec 17, 2014 at 8:44 PM, Richard Harding rick.hard...@canonical.com
wrote:
11. Juju's GUI's bells and whistles are nice, but I think there's a bug
with it because its statuses are inaccurate. If you set a relation, Juju
says the relation is green and active immediately, which is
...
9. If you want to cancel a deployment that just started you need to keep
running remove-service forever. Juju will simply ignore you if it's still
running some special bits of the charm or if you have previously asked it
to cancel the deployment during its setting up. No errors, no other
On 18 December 2014 at 12:15, John Meinel j...@arbash-meinel.com wrote:
Stub- AFAIK there isn't something today, though William might know better.
William, does your Active/Goal proposal address this? Having a Goal of 0
units would be a pretty clear indication that the service is shutting
Can someone remind me of the process for proposing branches that depend on
another branch that is still in review?
I know it's been discussed here and on irc before, but I don't recall the
specifics.
I think that the steps are:
1. Just propose the branch in github, which will trigger the
On 18/12/14 03:01, John Weldon wrote:
Can someone remind me of the process for proposing branches that
depend on another branch that is still in review?
I know it's been discussed here and on irc before, but I don't recall
the specifics.
I think that the steps are:
1. Just propose the
On Wed, Dec 17, 2014 at 4:26 PM, Menno Smits menno.sm...@canonical.com
wrote:
There seems to be some confusion as to how merges gets blocked and
unblocked. Specifically:
1. How do merges get blocked?
Juju-core bugs with the following criteria will block merges:
a. status: 'Triaged', 'In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18.12.2014 04:20, John George wrote:
On Wed, Dec 17, 2014 at 4:26 PM, Menno Smits
menno.sm...@canonical.com mailto:menno.sm...@canonical.com
wrote:
There seems to be some confusion as to how merges gets blocked and
unblocked. Specifically:
...
3. How do merges get unblocked?
Merges are unblocked when no bugs are returned with the above
criteria. The bugs should be updated only after the committed fix
has successfully passed the CI tests which discovered the
regression. This will most often mean setting the status to
19 matches
Mail list logo
