Hey Mike,
In git you accomplish these kinds of things with merge strategies. There’s a
lot to choose from. What you’re describing sounds a bit like a variant on the
“theirs” strategy. You can also do a recursive merge with a “theirs” conflict
resolution choice, and there’s many other options.
Lucian, did you make a ticket for this? It seems a blocker bug to me!
On Fri, Oct 24, 2014 at 1:28 AM, Nux! n...@li.nux.ro wrote:
Ok, so how I solved it:
Followed the upgrade procedure to the letter, but before running
cloudstack-sysvmadm to upgrade my sytemvms I have replaced the QCOW2 file
On Fri, Oct 24, 2014 at 1:30 AM, Animesh Chaturvedi
animesh.chaturv...@citrix.com wrote:
I sttrongly disagree with Animesh here and think Rohit is overlooking a
simple fact. At the moment the branches are for 'stabalizing'.
Fixing on master first is in direct contradiction with that.
We have
Mike, Why have everybody work on the same branch. people can work on
their own branch and when they are done they can rebase on the tip see
ci success and then merge. The problem with forward branches is
abandoned work or work that for some reason shouldn't go in 'this'
release. it will remain
On Fri, Oct 24, 2014 at 8:36 AM, Leo Simons lsim...@schubergphilis.com wrote:
Hey Mike,
In git you accomplish these kinds of things with merge strategies. There’s a
lot to choose from. What you’re describing sounds a bit like a variant on the
“theirs” strategy.
...
doh, will give it another
Yep, https://issues.apache.org/jira/browse/CLOUDSTACK-7781
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Daan Hoogland daan.hoogl...@gmail.com
To: dev dev@cloudstack.apache.org
Sent: Friday, 24 October, 2014 08:03:59
Subject: Re:
thanks for walking the bleeding edge on this, Nux!
On Fri, Oct 24, 2014 at 10:32 AM, Nux! n...@li.nux.ro wrote:
Yep, https://issues.apache.org/jira/browse/CLOUDSTACK-7781
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Daan
Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7782 for this.
Anyone knows who we can bug for a fix?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Nux! n...@li.nux.ro
To: dev@cloudstack.apache.org
Sent: Friday, 24 October,
H,
I the present code a vr is updates as follows:
// 1) Shutdown all the elements and cleanup all the rules.
Don't allow to shutdown network in intermediate
// states - Shutdown and Implementing
// 2) Only after all the elements and rules are shutdown
properly, update
Hi,
On jenkins.buildacloud.org, the last successful builds for systemvm template
build jobs was 20-22 days ago. Can anyone give me either access to the infra so
I can help debug and fix it, or people who have access help fix it? Thanks.
The common issue is that it takes a lot of time to copy
At first glance it seems that we need is to
- shutdown one side
- update the vo
- restart the one side
- shutdown the other side
- restart the other side
Somehow this seems to be too simple. the shutdown elements works in a
generic way while my use case only applies to the virtual router and
not
Hello,
I tried yo upgrade Cloudstack from 4.4.0 to 4.4.1, following the
instructions of the release note.
When I restarted the MS the update of the database worked as expected
but after the server is stuck.
Regards,
Partial log output:
2014-10-24 14:01:54,283 INFO [c.c.u.d.T.Transaction]
Hi Lucian,
The View secondary IP button should be displayed next to the IP Address in
the gridview. Clicking on that this page should display the Acquire new
secondary IP button. I have tested this in master and we seem to have the same
code in 4.4.
Could you double check this? It could be
您好：
OS: CentOS6.3 x64
cloudstack: apache-cloudstack-4.4.0-src.tar.bz2
As building RPM，excute cloudstack-4.4.0/packaging/centos63/package.sh
,the error as followed, please help me to resolve it, Thanks!
Failed tests:
Hello,
This might sound stupid, but what is this gridview you are talking of?
This is what I am seeing http://imgur.com/9fl6ERD
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Gabor Apati-Nagy gabor.apati-n...@citrix.com
To:
GitHub user santhoshdaivajna opened a pull request:
https://github.com/apache/cloudstack/pull/25
listDirectory method updated to use ObjectListing.isTruncated().
Because buckets can contain a virtually unlimited number of keys, the
complete results of a list query can be
Hello,
Any reason you are not building 4.4.1? Perhaps it's fixed there.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: zengfh2...@aliyun.com
To: dev dev@cloudstack.apache.org
Sent: Friday, 24 October, 2014 15:13:19
Subject: [HELP]
Yeah, Daan, the approach you describe sounds like a reasonable substitute
for what I have in that diagram.
My main concern was CI running before the code was checked into the real
branch from the staging branch.
On Fri, Oct 24, 2014 at 1:12 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
Thanks, Leo
Yeah, being able to essentially mark a commit as NOT needing to be merged
(in fact, merging is wrong in this case) to a newer branch is key, I think,
to helping solve our branching issues.
On Fri, Oct 24, 2014 at 12:36 AM, Leo Simons lsim...@schubergphilis.com
wrote:
Hey Mike,
In
I'm still puzzled why it would have worked on my Firefox too. There must be
some difference in configuration.
--
Stephen Turner
-Original Message-
From: Amogh Vasekar [mailto:amogh.vase...@citrix.com]
Sent: 23 October 2014 16:18
To: dev@cloudstack.apache.org
Subject: Re: Urgent.
This looks like the certificate issue that has been mentioned in another
thread on the list.
On 24 October 2014 16:48, Nux! n...@li.nux.ro wrote:
Hello,
Any reason you are not building 4.4.1? Perhaps it's fixed there.
--
Sent from the Delta quadrant using Borg technology!
Nux!
Hello,
This might sound stupid, but what is this gridview you are talking of?
This is what I am seeing http://imgur.com/9fl6ERD
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Gabor Apati-Nagy gabor.apati-n...@citrix.com
To:
As you are building from source tarball, the simplest way to fix is to delete
CertServiceTest.java
-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Friday, October 24, 2014 9:54 AM
To: CloudStack Dev
Subject: Re: [HELP] cloudstack 4.4.0 src build failed
This
Right, we just need to make sure CI comes into play before the merge.
Hence my earlier reply to what Daan mention:
My main concern was CI running before the code was checked into the real
branch from the staging branch.
On Fri, Oct 24, 2014 at 12:28 PM, David Nalley da...@gnsa.us wrote:
On
On Fri, Oct 24, 2014 at 3:12 AM, Daan Hoogland daan.hoogl...@gmail.com wrote:
Mike, Why have everybody work on the same branch. people can work on
their own branch and when they are done they can rebase on the tip see
ci success and then merge. The problem with forward branches is
abandoned
See http://jenkins.buildacloud.org/job/build-4.5/43/changes
We have a cluster that is dedicated to a specific domain, and that domain
has resource limits set.
What would be the best way to display the currently utilized resources to
the user of that domain?
It's fairly easy with an API call to get the Max for each resource, but
so far I've been unable to
mobile dev with bilingual spelling checker used (read at your own risk)
Op 24 okt. 2014 20:30 schreef David Nalley da...@gnsa.us:
On Fri, Oct 24, 2014 at 3:12 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
Mike, Why have everybody work on the same branch. people can work on
their own
We do run ci on branches!
mobile dev with bilingual spelling checker used (read at your own risk)
Op 24 okt. 2014 20:38 schreef Mike Tutkowski mike.tutkow...@solidfire.com
:
Right, we just need to make sure CI comes into play before the merge.
Hence my earlier reply to what Daan mention:
My
Cool...so, it sounds like any branch we create in the repo will
automatically have CI run against it post each commit.
How do you know when CI has completed and what the results are?
At that point, you could treat your own branch (as Daan says) as the
forward branch. Once CI has been successful,
I think listAccounts api also gives that info ? If this is not easy to
find please find an enhancement on JIRA. Thanks.
-Nitin
On 24/10/14 11:51 AM, Logan Barfield lbarfi...@tqhosting.com wrote:
We have a cluster that is dedicated to a specific domain, and that domain
has resource limits set.
Hi Laszlo,
Any comments on the below? I agree adding 3 characters is a bug and
willing to fix it.
In addition, Ian, I believe we should set a minimum allowed value for the
config value vm.password.length. Any objections to setting the minimum to
8, the previous default?
Thanks
Amogh
On
Imho, considering the password is not very secure (it's missing symbols), we
should increase the length.
For my personal stuff I default to 15 chars.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Amogh Vasekar
Do note that the password generated here is considered temporary, as
previously pointed out by Chiradeep in another thread.
Thanks
Amogh
On 10/24/14 5:31 PM, Nux! n...@li.nux.ro wrote:
Imho, considering the password is not very secure (it's missing symbols),
we should increase the length.
For
I agree adding 3 characters is a bug and willing to fix it.
Me too.. I find it very worrying that the code base has tests that
cater for bugs to be valid input.
Really makes me wonder about the quality of the product.
Anyways... I did a grep of the codebase for usage of the method. Its not
At the moment it must be called 'hotfix/*' or 'bugfix/*'. we should
add 'feature/*' to that.
On Fri, Oct 24, 2014 at 11:11 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
Cool...so, it sounds like any branch we create in the repo will
automatically have CI run against it post each
All,
The following pertains to cloudstack + vmware. Currently when using a multi
CPU compute service offering, cloudstack creates the CPUs on the vm using all
sockets. This can be an issue for operating systems that have physical CPU
sockets limits. It can also be a license issue for certain
37 matches
Mail list logo
