This looks like your console proxy VM isn't working. It could be firewall
on the KVM host not allowing access to 5900+ anymore, or the consoleproxy
VM may need to be restarted (system VM starting with "v"). Has it worked in
the past? You could try connecting to the instances with a vnc client to
s
For some reason, I am unsure of the issue; attempting to review the KVM of any
instance times out:
cloudstack realhostip.com took too long to respond
Has anyone encountered this error and how can it be corrected?
Thanks,
Maurice
Alex,
I think we need concern ourselves with both to maximize the clarity of
the history that will eventually be merged into master. Therefore, we
need to make sure that the master to feature branch syncs are done
properly as well.
Thanks,
-John
On Mar 30, 2013, at 5:07 PM, Alex Huang wrote:
+1. I think we're specifically talking about merging into master, not syncing
from master.
--Alex
> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Saturday, March 30, 2013 2:04 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] git rebase vs git mer
Alex,
It seems appropriate to me to use both rebase and squashed commits.
To my way of thinking, we should rebase when syncing features branches
with master (or the eventual target branch) to keep the revision
history of the eventual patch as concise as possible. We should merge
from feature bran
On Thu, Mar 28, 2013 at 03:55:26PM -0700, Sheng Yang wrote:
> commit e3f67d126d66c31e027c96b5524667884084053b
> Author: Sheng Yang
> Date: Thu Mar 28 15:02:45 2013 -0700
>
> CLOUDSTACK-1827: Fix redundant router update mechanism
>
> There is a bug that if the smaller number ID RvR stop
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10200/#review18560
---
Ship it!
applied to 4.1:
commit 80c588e6b6d04fa97d4934d12ae191aafd
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10200/
---
(Updated March 30, 2013, 8:19 p.m.)
Review request for cloudstack and Chip Chil
Justin
Read over your email, really liked the proposal - I think all of them are very
good and useful.
Please post the code if you need someone to test it.
Thanks
ilya
-Original Message-
From: Justin Grudzien [mailto:grudz...@gmail.com]
Sent: Friday, March 29, 2013 11:51 PM
To: dev@
On 03/30/2013 04:02 PM, Marcus Sorensen wrote:
One of the things that helped me quite a bit With the CentOS stuff was
that I created a VM with agent/management server running in it. I set
up a 4.0 system with an advanced zone, pulled down the source code
into it, and then took a copy of the VM.
Dave and I have talked on IRC at one point about this. We both thought feature
branch merges should come in as a squashed commit because it's easier to see
exactly what the changes that merge branch brought in were and easier to
revert. Something to consider when talking about this.
--Alex
>
One of the things that helped me quite a bit With the CentOS stuff was
that I created a VM with agent/management server running in it. I set
up a 4.0 system with an advanced zone, pulled down the source code
into it, and then took a copy of the VM. Then I ran through the
upgrade process 10 or 15 ti
2013/03/29 19:28、Sebastien Goasguen のメッセージ:
>>
>> -snip-
>>> I ended fixing it in remove-vpx.xml , the tags need to be on a new
>>> line…
>> -snip-
>>
>> That's strange. I could successfully run publican. As it is an xml,
>> new line should not matter...
>>
>> What I did:
>> cd docs
>> tx p
Hi,
I've started a Wiki[0] to describe the upgrade process going from 4.0 to
4.1 with Ubuntu packages.
Since the packages got renamed from cloud-* to cloudstack-* a lot has
changed and some manual intervention is required.
The Wiki is work-in-progress while I'm upgrading one of my 4.0 clust
Hi,
On 03/30/2013 12:36 AM, Edison Su wrote:
Hi all,
I am trying to review some feature branches, when I see merge requests coming from mailing list, one
thing that makes code review almost unrealistic is that, developers tend to use "git merge" to
master branch whenever rebase is needed
15 matches
Mail list logo