1. I just did a rough grep, so 158 logs out of 6674 are these. Roughly 2.3%.
This is just creating datacenter and playing few initial things. As well,
message format is of these logs is little incomplete i believe, it ends at
typ.. with out giving further information.
2. Its giving good
Iam not sure, its stretching a limit, but i have seen many patches missing in
master or only applied to one branch.
One RCA for many failures or issues reported during initial days of every new
branch is that it has these fixes are missing. I believe if we can enforce a
patch submitter to
On May 28, 2014, at 5:32 AM, sebgoa run...@gmail.com wrote:
On May 28, 2014, at 11:05 AM, Wido den Hollander w...@widodh.nl wrote:
On 05/28/2014 10:43 AM, sebgoa wrote:
On May 16, 2014, at 2:10 AM, Andrei Mikhailovsky and...@arhont.com wrote:
Hi guys,
Sorry if this email will
On May 31, 2014, at 11:14 AM, Milamber milam...@apache.org wrote:
A related ticket has been open in Jira
https://issues.apache.org/jira/browse/CLOUDSTACK-6673
Let me copy Alex and Chiradeep, they might have some background about this.
Le 31/05/2014 08:27, ilya musayev a ecrit :
I
Punith, Mike,
Allow me to ask questions regarding guaranteed IOPS feature.
(Since it may be off-topic to Hieu's original question, I changed the subject.)
Q1) Does your plugins(Solidfire, CloudBytes) support KVM? From which version?
In my understanding,
Current CloudStack's implementation
Thanks Mike and Punith for quick reply.
Both solutions you gave here are absolutely correct. But as I mentioned in
the first email, I want another better solution for current infrastructure
at my company.
Creating a high IOPS primary storage using storage tags is good but it will
be very waste
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22093/#review44479
---
The issue I see with this fix is that it also applies to other
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22093/#review44480
---
Another issue might be that new entries (we see this on ACS 4.3
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22093/#review44481
---
engine/schema/src/com/cloud/upgrade/dao/Upgrade421to430.java
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22093/#review44482
---
If someone is already on 4.3, is this fix not applicable? Shouldn't
Any other suggestions/objections/comments??
Can we discuss this in detail and agree to a process??
~Rajani
On 02-Jun-2014, at 9:32 am, Rajani Karuturi rajani.karut...@citrix.com wrote:
Yes as mike said, if its a one-off case we can do a empty merge(merge -s
ours) for it and git will
I don't think this should be solved this way afterall. 'untagged'
actually means no vlan, so it should not be prepended with 'vlan://'.
I think the kvm code should be fixed for this not the generic code.
On Fri, May 30, 2014 at 10:59 PM, Daan Hoogland daan.hoogl...@gmail.com wrote:
On Fri, May
H,
Please, have a look at the example picture in
https://cwiki.apache.org/confluence/display/CLOUDSTACK/inter+vpc+network
It depicts a mix of the use cases I described earlier and gives an
overview of the possibilities required.
regards,
Daan
On Tue, May 27, 2014 at 10:15 PM, Daan Hoogland
Hi Hugo,
awsapi-generated-code is excluded for the project but I still see issues
reported in them.
For example for file src/com/amazon/ec2/DeleteTagsResponseType.java
Can you check the file exclude pattern? I think .* is missing
(awsapi/src/com/amazon/.*)
Fixing this might give us a
On June 2, 2014, 8:37 a.m., Erik Weber wrote:
engine/schema/src/com/cloud/upgrade/dao/Upgrade421to430.java, line 368
https://reviews.apache.org/r/22093/diff/2/?file=600082#file600082line368
There's a typo in the where clause. vland_id should be vlan_id
thanks, will fix
- daan
On June 2, 2014, 8:52 a.m., Koushik Das wrote:
If someone is already on 4.3, is this fix not applicable? Shouldn't this go
to 4.3-4.4 upgrade?
yes, will do, I was wondering on this. It is a repeatable conversion so it can
go in 4.3.0 to 4.3.1 and in 4.3 to 4.4 as well
- daan
On June 2, 2014, 8:32 a.m., Joris van Lieshout wrote:
Another issue might be that new entries (we see this on ACS 4.3 with
XenServer) are created without vlan://
The name of the field is vlan_id and not BroadcastURI so keeping it an
integer only would make more sense to me. And then
It is an interesting idea. If the constraints you face at your company can
be corrected somewhat by implementing this, then you should go for it.
It sounds like writes will be placed on the slower storage pool. This means
as you update OS components, those updates will be placed on the slower
Also, give some thought in your design as to how VM migration will work.
Thanks!
On Monday, June 2, 2014, Mike Tutkowski mike.tutkow...@solidfire.com
wrote:
It is an interesting idea. If the constraints you face at your company can
be corrected somewhat by implementing this, then you should
On Fri, May 30, 2014 at 01:57:13PM -0700, Ritu Sabharwal wrote:
Hi Sebastian,
This gives a real good picture of the IP clearance process.
I sent a Proposal email to mailing list last week, still waiting for
acceptance. Can you please have a look at it and provide feedback?
Don't assume
On May 30, 2014, at 10:57 PM, Ritu Sabharwal rsabh...@brocade.com wrote:
Hi Sebastian,
This gives a real good picture of the IP clearance process.
I sent a Proposal email to mailing list last week, still waiting for
acceptance. Can you please have a look at it and provide feedback?
I
This is great Ian, i will keep an eye out for your work.
It will be useful for the meetups we run todo demo and how to installs.
On 6/1/14, 6:06 AM, Ian Duffy wrote:
Hi all,
I am making slow but steady progress on my GSoC project. If anybody is
interested in seeing the work completed and work
I'm not sure the KVM code needs to be changed, you're asking it to deal
with an inconsistency from the mgmt server. Don't you find it odd that one
Command from the mgmt server provides broadcastUri=vlan://untagged and
another provides broadcastUri=untagged? I'm not sure I understand why
changing
Just to recap... I was trying to review the issue in my head and thought it
might be useful to write it down.
in 4.3 we got the BroadcastDomainType enum introduced, and many parts of
the code were changed to use that when dealing with the vlan id. This code,
among other things, returns a vlan id
I've forced cloudstack...@nuagenetworks.net to be unsubscribed from
the list, given that it keeps sending that message to all posters.
On Fri, May 30, 2014 at 5:12 PM, Daan Hoogland daan.hoogl...@gmail.com wrote:
I've been getting them all day about my polemic wiht Marcus. All mail
went through
Hi Alena,
Did you get back from the vacation?
If so, let me know when it is the good time to discuss this.
Thanks
Alex Ough
On Thu, May 15, 2014 at 9:02 AM, Alex Ough alex.o...@sungardas.com wrote:
I know. That's why I asked before Alex Huang to let me know when he's
available after he's
Thanks!
On Monday, June 2, 2014, Chip Childers chipchild...@apache.org wrote:
I've forced cloudstack...@nuagenetworks.net javascript:; to be
unsubscribed from
the list, given that it keeps sending that message to all posters.
On Fri, May 30, 2014 at 5:12 PM, Daan Hoogland
Yes, I’m back. Please check with Alex Huang what time he can be on the call
with you. I can join any time today/tomorrow.
-Alena.
From: Alex Ough alex.o...@sungardas.commailto:alex.o...@sungardas.com
Date: Monday, June 2, 2014 at 9:49 AM
To: Alena Prokharchyk
Hi,
I've found a way to sponsor myself to work full-time on the project again
in upcoming months, and will slowly and gradually start contributing to the
project. Please do help me in catching up about the changes and
developments since last year.
Cheers.
On Tue, Aug 27, 2013 at 2:19 PM,
No idea, but +1 on removing it.
From: Sebastien Goasguen run...@gmail.commailto:run...@gmail.com
Date: Monday, June 2, 2014 at 12:16 AM
To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org, Alex Huang
+1 I just found it was removed yesterday from master:
https://github.com/apache/cloudstack/commit/ab89eb106f9836632668366d407a2d8c5892bec9
Regards.
On Mon, Jun 2, 2014 at 10:32 PM, Chiradeep Vittal
chiradeep.vit...@citrix.com wrote:
No idea, but +1 on removing it.
From: Sebastien Goasguen
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22143/
---
Review request for cloudstack, Brian Federle and Jessica Wang.
Bugs:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22147/
---
Review request for cloudstack, Brian Federle and Jessica Wang.
Bugs:
Hi Alex Huang,
Can you tell me when you're available?
Thanks
Alex Ough
On Mon, Jun 2, 2014 at 12:52 PM, Alena Prokharchyk
alena.prokharc...@citrix.com wrote:
Yes, I’m back. Please check with Alex Huang what time he can be on the
call with you. I can join any time today/tomorrow.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22147/
---
(Updated June 2, 2014, 6:10 p.m.)
Review request for cloudstack, Brian Federle
Thanks Sebastien, and Chiradeep,
I've already push a commit to remove the code.
If someone explain the reason why we need it, I'll revert my code or
make additional patch.
2014-06-02 11:02 GMT-06:00 Chiradeep Vittal chiradeep.vit...@citrix.com:
No idea, but +1 on removing it.
From: Sebastien
Hi Chip,
Thanks for the information.
I created a JIRA bug for the plugin development CLOUDSTACK-6823.
I don't have the Edit permissions to edit the wiki to add the design spec.
User ID: rsabharw
Can I get the edit permissions to edit the wiki please?
Thanks Regards,
Ritu S.
Hi Sebastian,
Right now I am the only author for the plugin. Will add more to the wiki and
Review Board as an when people join me.
Thanks Regards,
Ritu S.
-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: Monday, June 02, 2014 7:59 AM
To: Ritu Sabharwal
Cc:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18677/#review44511
---
Commit eb8e630f24f5359b6c2e9a74bf12ea338df66a41 in cloudstack's
I think many of the bullet points are what we are currently doing
(guidelines for commit comments, feature branches need to stay in sync with
master, no back-merging). I also think that much of what we do now is done
the way it is simply because there *are* vast changes between versions.
Classes
On Mon, Jun 2, 2014 at 1:21 PM, Marcus shadow...@gmail.com wrote:
I think many of the bullet points are what we are currently doing
(guidelines for commit comments, feature branches need to stay in sync with
master, no back-merging). I also think that much of what we do now is done
the way it
Welcome back, Rohit.
-min
On 6/2/14 9:56 AM, Rohit Yadav rohityada...@gmail.com wrote:
Hi,
I've found a way to sponsor myself to work full-time on the project again
in upcoming months, and will slowly and gradually start contributing to
the
project. Please do help me in catching up about the
Good to hear and welcome back Rohit.
-sadhu
-Original Message-
From: Min Chen [mailto:min.c...@citrix.com]
Sent: 02 June 2014 23:03
To: dev@cloudstack.apache.org
Cc: Rohit Yadav
Subject: Re: [OFFLINE] Going away for some time
Welcome back, Rohit.
-min
On 6/2/14 9:56 AM, Rohit Yadav
I will merge 4.3-forward into 4.3 later today.
Animesh
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Saturday, May 31, 2014 1:38 PM
To: dev
Subject: [DISCUSS] old forward branches
The older forward branches are still heavily used, while the release
Daan - Thanks for your comment. The java upgrade code has never been data
migration code only.
I have always seen complex DDL logic being handled by java upgrade code
because we can write complex logic and catch exceptions gracefully. As you
see from the links below - add column if it doesn't
I don't think there's any real reason it was there. Probably it was easiest at
that time to do. +1 and thanks on removing it.
--Alex
-Original Message-
From: ynoj...@ynojima.net [mailto:ynoj...@ynojima.net] On Behalf Of
Yoshikazu Nojima
Sent: Monday, June 2, 2014 10:14 AM
To:
Hi,
I am trying to upload an SSL certificate to cloudstack using uploadSslCert
API since 4.3 version does not have UI support for the same. But on debugging,
it was found that some characters were missing from certificate after it was
decoded from the URL, due to which the following exception
On Jun 2, 2014, at 7:13 PM, Ritu Sabharwal rsabh...@brocade.com wrote:
Hi Chip,
Thanks for the information.
I created a JIRA bug for the plugin development CLOUDSTACK-6823.
I don't have the Edit permissions to edit the wiki to add the design spec.
User ID: rsabharw
you should be
The Project Management Committee (PMC) for Apache CloudStack has
asked Amogh Vasekar to become a committer and we are pleased to announce
that he has accepted.
Being a committer allows many contributors to contribute more autonomously. For
developers, it makes it easier to submit changes and
The UI does support uploading the server certificate. Were you uploading
chain certs (because UI doesn't support that) ? There is a bug in 4.3
where there is double decoding for this api. Check CLOUDSTACK-6499 for
reference and port it in 4.3 if possible.
Thanks,
-Nitin
On 02/06/14 10:59 AM,
Congratulations, Amogh! Well done.
-Alena.
On 6/2/14, 11:14 AM, John Kinsella j...@stratosec.co wrote:
The Project Management Committee (PMC) for Apache CloudStack has
asked Amogh Vasekar to become a committer and we are pleased to announce
that he has accepted.
Being a committer allows many
Great news. Congrats Amogh !!!
On 02/06/14 11:14 AM, John Kinsella j...@stratosec.co wrote:
The Project Management Committee (PMC) for Apache CloudStack has
asked Amogh Vasekar to become a committer and we are pleased to announce
that he has accepted.
Being a committer allows many contributors
Hi,
1 and 2) CloudStack now supports managed storage for the following
hypervisor types:
* Disk Offerings for XenServer and ESX as of CS 4.2
* Disk Offerings for KVM as of CS 4.3
* Compute Offerings for XenServer and ESX as of CS 4.4
The SolidFire plug-in is capable of supporting whatever
Congrats Amogh.
Regards,
Rayees
-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Monday, June 02, 2014 11:17 AM
To: dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] Amogh Vasekar as committer
Great news. Congrats Amogh !!!
On 02/06/14 11:14 AM, John
I think the current implementation, outside of custom vendors is to simply
act as a tune-able rate-limiter for the admin to leverage how they see fit.
I'm not sure it was intended to be a guarantee of service, just a cap,
therefore the thought of oversubscribing wasn't an issue. It is an exercise
oh dang! good stuff Amogh!
On Mon, Jun 2, 2014 at 11:29 AM, Rayees Namathponnan
rayees.namathpon...@citrix.com wrote:
Congrats Amogh.
Regards,
Rayees
-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Monday, June 02, 2014 11:17 AM
To:
Is that not happening?
On Mon, Jun 2, 2014 at 11:26 AM, David Nalley da...@gnsa.us wrote:
On Mon, Jun 2, 2014 at 1:21 PM, Marcus shadow...@gmail.com wrote:
I think many of the bullet points are what we are currently doing
(guidelines for commit comments, feature branches need to stay in
Congratulations, Amogh.
-min
On 6/2/14 11:53 AM, Ahmad Emneina aemne...@gmail.com wrote:
oh dang! good stuff Amogh!
On Mon, Jun 2, 2014 at 11:29 AM, Rayees Namathponnan
rayees.namathpon...@citrix.com wrote:
Congrats Amogh.
Regards,
Rayees
-Original Message-
From: Nitin Mehta
I started playing with the 'javasphinx' project to see if it would work for
generating the API docs.
So here is the basic idea of what it produces.
I created docs for the following cloudstack directory:
'api/src/org/apache/cloudstack/api/'
I then took the RST files and generated the html docs
Hi,
Could you please give edit/contribute permission to Cloudstack Jira and
Wiki.
My account IDs are as below:
Cloudstack Jira : suresh.ramamurthy
Cloudstack wiki : suresh.ramamurthy
Do I need the same permission for Cloudstack Review Board ? If yes, please
add the
below account ID too
Thanks everyone :-)
Regards,
Amogh
On 6/2/14 11:57 AM, Min Chen min.c...@citrix.com wrote:
Congratulations, Amogh.
-min
On 6/2/14 11:53 AM, Ahmad Emneina aemne...@gmail.com wrote:
oh dang! good stuff Amogh!
On Mon, Jun 2, 2014 at 11:29 AM, Rayees Namathponnan
Congratulations Amogh!
-Original Message-
From: John Kinsella [mailto:j...@stratosec.co]
Sent: Monday, June 02, 2014 11:14 AM
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] Amogh Vasekar as committer
The Project Management Committee (PMC) for Apache CloudStack has asked Amogh
Hi Daan,
Thanks for the visual. It helps, but the use case outlined seems possible with
a single VPC?
Assuming that for some reason (please educate us) it is not possible to use a
single VPC, it appears to me that we are inventing a new network type
(“InterVPC”).
Who “owns” this network? Who
There are 11 Blockers ( 1more than 5/28) and 76 Critical ( 2 less than 5/28) -
Not much improvement in fixing issues.
There is 1 unassigned defect in today's blocker defects
KeySummary Assignee
CLOUDSTACK-6602 [UI] createNetworkACL API action param value passed
There is also the problem of cherry-picking.
As a contributor, I always endup creating multiple patches for each branch as
they don’t cleanly apply on the upward branches. which means distinct commits
for each branch and I don’t easily know which all branches my commit exists
unless I do grep.
Congrats Amogh!
-Original Message-
From: John Kinsella [mailto:j...@stratosec.co]
Sent: Monday, 2 June 2014 11:44 PM
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] Amogh Vasekar as committer
The Project Management Committee (PMC) for Apache CloudStack has asked Amogh
Vasekar to
Congrats Amogh.
-Original Message-
From: John Kinsella [mailto:j...@stratosec.co]
Sent: Monday, June 2, 2014 11:44 PM
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] Amogh Vasekar as committer
The Project Management Committee (PMC) for Apache CloudStack has
asked Amogh Vasekar
Hearty Congratulations Amogh!
-Original Message-
From: John Kinsella [mailto:j...@stratosec.co]
Sent: Monday, June 2, 2014 11:44 PM
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] Amogh Vasekar as committer
The Project Management Committee (PMC) for Apache CloudStack has asked Amogh
Hearty Congratulations Saksham!
-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: Thursday, May 29, 2014 12:18 PM
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] Saksham Srivastava as committer
The Project Management Committee (PMC) for Apache CloudStack has asked
Great work Saksham! Congratulations.
On Mon, Jun 2, 2014 at 10:29 PM, Rajesh Battala rajesh.batt...@citrix.com
wrote:
Hearty Congratulations Saksham!
-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: Thursday, May 29, 2014 12:18 PM
To: dev@cloudstack.apache.org
Congrats Amogh!
On 02-Jun-2014, at 11:44 PM, John Kinsella j...@stratosec.co wrote:
The Project Management Committee (PMC) for Apache CloudStack has
asked Amogh Vasekar to become a committer and we are pleased to announce
that he has accepted.
Being a committer allows many contributors to
71 matches
Mail list logo
