Re: reviewboard-github integration
-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 with rbt I managed to do: $ rbt diff ~/patch (while on the proposed feature branch) And then went to the RB issue page and manually uploaded the generated diff and published it. So most definitely the hook generating RB issues have to upload the diff as well :) It's coming together, keep up the good work! Cheers, Dimiter On 20.10.2014 16:53, Eric Snow wrote: On Mon, Oct 20, 2014 at 6:06 AM, Ian Booth ian.bo...@canonical.com wrote: Hey Eric This is awesome, thank you. I did run into a gotcha - I created a PR and then looked at the Incoming review queue and there was nothing new there. I then clicked on All in the Outgoing review queue and saw that the review was unpublished. I then went to publish it and it complained at least one reviewer was needed. So I had to fill in juju-team and all was good. 1. Can we make it so that the review is published automatically? 2. Can we pre-fill juju-team as the reviewer? Good catch. The two are actually related. The review is published, but that fails because no reviewer got set. I'll get that fixed. -eric - -- Dimiter Naydenov dimiter.nayde...@canonical.com juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJURSrnAAoJENzxV2TbLzHw0BQH/16P4qPDI28kkGs398qRKY5s eUtcHBpYs+JuLV2ZA0LjCpTds89RBDW6cKsxcfXxaAmawIb0KHh920VzKb1Wl2OT z/iMOF2q91LnV58dqPf7mZjHaT1LPRdSRxg6aAZW/mjexwVRtRDT4Asd5w6JpKrH 9Tkqfy86OilJ70X8qNbegvjJrBAttwoLLI4jwJq4dNWUbWCBbuumryh0k6+GlmNH NiKbpi45pPy/RIFVA7ewbLIOpUXleHm5NIGlA/liZOMHpz0w5QHK3FYGLuGMNzQC fq4qW6rfb1ITdr7XWsA3gooV6FUndw3mbNsod3QgSv82RDA6GGECHeYimGG94/g= =POJ4 -END PGP SIGNATURE- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: mongodb log file size
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 2:35 PM, Vasiliy Tolstov v.tols...@selfip.ru wrote: Hi again =). I find discussion about mongodb repl log size, that it minimal 512Mb and maximum 1024Mb (max may be wrong...). Does it possible to minimize it to 128Mb? I'm understand about negative sides of this, but now i deploy via juju single machine and don't want to keep this logs big. Does it possible to minimize it, but if i need big cluster - set new size? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: reviewboard-github integration
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 (#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 with rbt I managed to do: $ rbt diff ~/patch (while on the proposed feature branch) And then went to the RB issue page and manually uploaded the generated diff and published it. So most definitely the hook generating RB issues have to upload the diff as well :) It's coming together, keep up the good work! Cheers, Dimiter On 20.10.2014 16:53, Eric Snow wrote: On Mon, Oct 20, 2014 at 6:06 AM, Ian Booth ian.bo...@canonical.com wrote: Hey Eric This is awesome, thank you. I did run into a gotcha - I created a PR and then looked at the Incoming review queue and there was nothing new there. I then clicked on All in the Outgoing review queue and saw that the review was unpublished. I then went to publish it and it complained at least one reviewer was needed. So I had to fill in juju-team and all was good. 1. Can we make it so that the review is published automatically? 2. Can we pre-fill juju-team as the reviewer? Good catch. The two are actually related. The review is published, but that fails because no reviewer got set. I'll get that fixed. -eric - -- Dimiter Naydenov dimiter.nayde...@canonical.com juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJURSrnAAoJENzxV2TbLzHw0BQH/16P4qPDI28kkGs398qRKY5s eUtcHBpYs+JuLV2ZA0LjCpTds89RBDW6cKsxcfXxaAmawIb0KHh920VzKb1Wl2OT z/iMOF2q91LnV58dqPf7mZjHaT1LPRdSRxg6aAZW/mjexwVRtRDT4Asd5w6JpKrH 9Tkqfy86OilJ70X8qNbegvjJrBAttwoLLI4jwJq4dNWUbWCBbuumryh0k6+GlmNH NiKbpi45pPy/RIFVA7ewbLIOpUXleHm5NIGlA/liZOMHpz0w5QHK3FYGLuGMNzQC fq4qW6rfb1ITdr7XWsA3gooV6FUndw3mbNsod3QgSv82RDA6GGECHeYimGG94/g= =POJ4 -END PGP SIGNATURE- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: mongodb log file size
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 1.21 where we store charms in mongodb. Hmm, why you need to store charms in mongodb =( ? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: mongodb log file size
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 need object storage needs makes things a bit simpler. most charms are fairly small minus those that bundle binaries. -k On Mon, Oct 20, 2014 at 4:53 PM, Vasiliy Tolstov v.tols...@selfip.ru wrote: 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 1.21 where we store charms in mongodb. Hmm, why you need to store charms in mongodb =( ? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: mongodb log file size
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 storage either), obviating the need by making juju handle its own very limited need object storage needs makes things a bit simpler. most charms are fairly small minus those that bundle binaries. Hm, as i see some charms have deb packages inside it =(... Does it possible to have option not preallocate data, but specify minimum and maximum storage use and grow on demand? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Azure US West having problems
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 unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Azure US West having problems
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 validated significant improvement as a result of their action plan. Customers may begin to see improvements to availability of their Virtual Networks. The next update will be provided in 2 hours or as events warrant. -k On Mon, Oct 20, 2014 at 5:05 PM, Nate Finch nate.fi...@canonical.com wrote: 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 unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: reviewboard-github integration
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 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 (#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 with rbt I managed to do: $ rbt diff ~/patch (while on the proposed feature branch) And then went to the RB issue page and manually uploaded the generated diff and published it. So most definitely the hook generating RB issues have to upload the diff as well :) It's coming together, keep up the good work! Cheers, Dimiter On 20.10.2014 16:53, Eric Snow wrote: On Mon, Oct 20, 2014 at 6:06 AM, Ian Booth ian.bo...@canonical.com wrote: Hey Eric This is awesome, thank you. I did run into a gotcha - I created a PR and then looked at the Incoming review queue and there was nothing new there. I then clicked on All in the Outgoing review queue and saw that the review was unpublished. I then went to publish it and it complained at least one reviewer was needed. So I had to fill in juju-team and all was good. 1. Can we make it so that the review is published automatically? 2. Can we pre-fill juju-team as the reviewer? Good catch. The two are actually related. The review is published, but that fails because no reviewer got set. I'll get that fixed. -eric - -- Dimiter Naydenov dimiter.nayde...@canonical.com juju-core team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJURSrnAAoJENzxV2TbLzHw0BQH/16P4qPDI28kkGs398qRKY5s eUtcHBpYs+JuLV2ZA0LjCpTds89RBDW6cKsxcfXxaAmawIb0KHh920VzKb1Wl2OT z/iMOF2q91LnV58dqPf7mZjHaT1LPRdSRxg6aAZW/mjexwVRtRDT4Asd5w6JpKrH 9Tkqfy86OilJ70X8qNbegvjJrBAttwoLLI4jwJq4dNWUbWCBbuumryh0k6+GlmNH NiKbpi45pPy/RIFVA7ewbLIOpUXleHm5NIGlA/liZOMHpz0w5QHK3FYGLuGMNzQC fq4qW6rfb1ITdr7XWsA3gooV6FUndw3mbNsod3QgSv82RDA6GGECHeYimGG94/g= =POJ4 -END PGP SIGNATURE- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Azure US West having problems
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
https://management.core.windows.net/6f0e3b87-f601-40fd-9727-76d05563fedd/services/hostedservices:
dial tcp: lookup management.core.windows.net: No address associated with
hostname
I'm not sure if we can or should change the code, as in the past I've
observed problems when using Location and not Affinity Group.
Cheers,
Andrew
diff --git a/provider/azure/environ.go b/provider/azure/environ.go
index 9d5d5bf..b435b95 100644
--- a/provider/azure/environ.go
+++ b/provider/azure/environ.go
@@ -201,8 +201,8 @@ func (env *azureEnviron) createVirtualNetwork() error {
}
defer env.releaseManagementAPI(azure)
virtualNetwork := gwacl.VirtualNetworkSite{
- Name: vnetName,
- AffinityGroup: env.getAffinityGroupName(),
+ Name: vnetName,
+ Location: env.getSnapshot().ecfg.location(),
AddressSpacePrefixes: []string{
networkDefinition,
},
On Tue, Oct 21, 2014 at 5:13 AM, Kapil Thangavelu
kapil.thangav...@canonical.com wrote:
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 validated significant improvement as a result of their
action plan. Customers may begin to see improvements to availability of
their Virtual Networks. The next update will be provided in 2 hours or as
events warrant.
-k
On Mon, Oct 20, 2014 at 5:05 PM, Nate Finch nate.fi...@canonical.com
wrote:
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 unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: reviewboard-github integration
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 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 Mon, Oct 20, 2014 at 5:31 PM, Dimiter Naydenov dimiter.nayde...@canonical.com wrote: 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 with rbt I managed to do: $ rbt diff ~/patch (while on the proposed feature branch) And then went to the RB issue page and manually uploaded the generated diff and published it. So most definitely the hook generating RB issues have to upload the diff as well :) It's coming together, keep up the good work! Cheers, Dimiter On 20.10.2014 16:53, Eric Snow wrote: On Mon, Oct 20, 2014 at 6:06 AM, Ian Booth ian.bo...@canonical.com wrote: Hey Eric This is awesome, thank you. I did run into a gotcha - I created a PR and then looked at the Incoming review queue and there was nothing new there. I then clicked on All in the Outgoing review queue and saw that the review was unpublished. I then went to publish it and it complained at least one reviewer was needed. So I had to fill in juju-team and all was good. 1. Can we make it so that the review is published automatically? 2. Can we pre-fill juju-team as the reviewer? Good catch. The two are actually related. The review is published, but that fails because no reviewer got set. I'll get that fixed. -eric -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
