-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Eric,
Today I tried proposing a PR and the RB issue (#202) was created, but
it didn't have Reviewers field set (as described below), it wasn't
published (due to the former), but MOST importantly didn't have a diff
uploaded. After fiddling around
That should be fine, the dictates here are from mongodb default semantics,
we've tweaked them minorly but for the most part there per upstream
recommends. The amount of data juju uses is miniscule (1-2mb).. till juju
1.21 where we store charms in mongodb.
cheers,
Kapil
On Sun, Oct 19, 2014 at
Yeah, this is the same issue that Ian brought up. I'm looking into
it. Sorry for the pain.
-eric
On Mon, Oct 20, 2014 at 5:31 PM, Dimiter Naydenov
dimiter.nayde...@canonical.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Eric,
Today I tried proposing a PR and the RB issue
2014-10-20 21:16 GMT+04:00 Kapil Thangavelu kapil.thangav...@canonical.com:
That should be fine, the dictates here are from mongodb default semantics,
we've tweaked them minorly but for the most part there per upstream
recommends. The amount of data juju uses is miniscule (1-2mb).. till juju
we're trying to make providers easier to right, currently we use provider
object-storage, but a number of low cost providers don't have it and it
complicates writing a provider (ie. no all openstack installs have object
storage either), obviating the need by making juju handle its own very
limited
2014-10-21 0:55 GMT+04:00 Kapil Thangavelu kapil.thangav...@canonical.com:
we're trying to make providers easier to right, currently we use provider
object-storage, but a number of low cost providers don't have it and it
complicates writing a provider (ie. no all openstack installs have object
This is a pretty major problem it *seems* like it must be Azure's
fault, but it would be good to get more information about it. If anyone
cares to investigate, here's the bug:
https://launchpad.net/bugs/1383310
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or
possibly related to http://azure.microsoft.com/en-us/status/
Starting at approximately 19:00 on the 18th Oct, 2014 UTC a limited subset
of customers may experience intermittent errors when attempting to access
Azure Virtual Networks. Engineers are continuing with their manual recovery
and have
This should be resolved now. I've verified it works for me. If it
still impacts anyone, just let me know.
-eric
On Mon, Oct 20, 2014 at 7:34 PM, Eric Snow eric.s...@canonical.com wrote:
Yeah, this is the same issue that Ian brought up. I'm looking into
it. Sorry for the pain.
-eric
On
I just changed the Azure provider (locally) to allocate a virtual network
using a Location instead of Affinity Group, and it got most of the way
through bootstrap. It ends up failing with
2014-10-21 01:43:39 ERROR juju.cmd supercommand.go:323 Get
Hi Eric
I just created a pull request for a 1.20 branch and got the same symptoms as
seen previously. ie an incomplete review board review without a diff and with a
reviewer.
On 21/10/14 07:38, Eric Snow wrote:
This should be resolved now. I've verified it works for me. If it
still impacts
11 matches
Mail list logo