Awesome! Congratulations everyone!!
-Prachi
-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Wednesday, March 20, 2013 11:42 AM
To: cloudstack-dev@incubator.apache.org
Subject: Graduation
Hi all,
A quick update... the board has *passed* our graduation re
Already committed to master.
Commit hash:d9b85e397d10f2291058ff972094decd8fc4ad7d
--
CLOUDSTACK-1706 Failed to deploy VM with error "cannot find
DeployPlannerSelector"
Changes:
- Regular plugin/adapter components should usually be loaded at run level
RUNLEVEL_COMPONEN
This API is provided to bridge the gap beetwen CS functionality and support the
EC2 API's. With this API admin can set the default zone from the available
zones for the accounts that use EC2.
All EC2 API calls that this account makes, will operate in relation to this
default zone.
E.g- Allocat
Thanks for the observation Joe. I will make the change to AdapterBase - seems
like we need to run all adapters at level 5.
Thanks,
Prachi
-Original Message-
From: Kelven Yang
Sent: Monday, March 18, 2013 10:52 AM
To: cloudstack-dev@incubator.apache.org; Prachi Damle
Subject: Re
nner by referring to the global config
vm.allocation.algorithm value
Contained in branches: master
Contained in no tag
- Prachi Damle
On March 14, 2013, 1:17 a.m., Prachi Damle wrote:
>
> ---
> This is an automatically gene
+1!
On 3/11/13 9:42 AM, "Chip Childers" wrote:
>Hi,
>
>I would like to invite the CloudStack community to vote on whether
>Apache CloudStack is ready to graduate to top-level project status. The
>result of this vote will demonstrate whether the community is willing
>to govern itself (which is
not sure why git am
fails.
Is it possible for you to try git apply?
- Prachi
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9917/#review17845
Patch: https://reviews.apache.org/r/9917/
Fix for CLOUDSTACK-1604: deploy VM failed when global setting
"vm.allocation.algorithm" is set to "userdispersing"
34a9aa
Diff: https://reviews.apache.org/r/9917/diff/
Testing
---
Successfully deployed VM using the UserDispersingPlanner or
UserConcentratedPodPlanner after changing the global setting.
Thanks,
Prachi Damle
ago (Wed Mar 13 14:09:27 2013 -0700)
Committer: Prachi Damle (pra...@cloud.com)
Commit date:15 seconds ago (Wed Mar 13 14:20:41 2013 -0700)
Commit hash:7bb8ed4d05ac9ea1242201e0e4fafc36916d5c51
BUG-ID: CLOUDSTACK-1557
Summary: EC2 REST API : cloudbridge database is missing on
> On March 8, 2013, 11:09 p.m., Prachi Damle wrote:
> > Changes are good. Are theer any changes for correcting the path to
> > ec2-service.properties, as you have mentioned in
> > https://issues.apache.org/jira/browse/CLOUDSTACK-1557
Pradeep,
I suspect that the path to e
ec2-service.properties, as you have mentioned in
https://issues.apache.org/jira/browse/CLOUDSTACK-1557
- Prachi Damle
On March 8, 2013, 1:05 p.m., Pradeep Soundararajan wrote:
>
> ---
> This is an automatically generated e-mail.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle reassigned CLOUDSTACK-1376:
Assignee: edison su (was: Prachi Damle)
> Unable to migrate VM due
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590881#comment-13590881
]
Prachi Damle commented on CLOUDSTACK-1376:
--
Root cause is some KVM i
:00 PM
To: cloudstack-dev@incubator.apache.org
Cc: Manan Shah; Alex Huang
Subject: Re: [DISCUSS] Affinity / Anti-affinity Rules
On Fri, Feb 22, 2013 at 01:36:20PM -0800, Prachi Damle wrote:
> Hey all,
>
> It seems that host affinity usecase has little value in reality and very less
>
[
https://issues.apache.org/jira/browse/CLOUDSTACK-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589926#comment-13589926
]
Prachi Damle commented on CLOUDSTACK-197:
-
All patches listed above have
Chandan,
AFAIK the main JIRA issue https://issues.apache.org/jira/browse/CLOUDSTACK-197
and its subtasks have been submitted to master and 4.1.
Let's wait for Likitha to confirm if all the API support is being covered by
these or otherwise.
Thanks,
Prachi
-Original Message-
From: Chan
I think using transient fields is fine, maybe you could add this to UserVMVO if
this is applicable only to guest VMs.
Prachi
-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Wednesday, February 27, 2013 7:51 PM
To: cloudstack-dev@incubator.apache.org
Subject: v
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1418.
--
Resolution: Fixed
> As regular user , we are not allowed to deploy VM o
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1443.
--
Resolution: Not A Problem
Invalid, this is working correctly in master
Prachi Damle created CLOUDSTACK-1443:
Summary: As domain admin we are allowed to create shared network.
Key: CLOUDSTACK-1443
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1443
Project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587807#comment-13587807
]
Prachi Damle commented on CLOUDSTACK-1418:
--
Sangeetha, please can you
being
reprogrammed in the router.
-Thanks
Sangeetha
-Original Message-
From: Prachi Damle [mailto:prachi.da...@citrix.com]
Sent: Monday, February 25, 2013 5:29 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: restartNetwork with cleanup=false in Shared Networks
I see that restartNetwork
I see that restartNetwork with cleanup = true, attempts a network shutdown
first (where all rules are revoked and all network elements are shutdown) and
then everything is reprogrammed using the information in the db.
This design is irrespective of the type of the network.
-Prachi
-Origi
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1338.
--
Resolution: Fixed
> Deploy VM failed using
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586372#comment-13586372
]
Prachi Damle commented on CLOUDSTACK-1338:
--
This should be fixed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle reassigned CLOUDSTACK-1338:
Assignee: Prachi Damle
> Deploy VM failed using
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle reassigned CLOUDSTACK-1382:
Assignee: frank zhang (was: Prachi Damle)
Frank - "DeployPlannerSel
de:
- framework for supporting affinity groups in general
- Default implementation for host anti-affinity
- DeploymentPlanningManager changes
Any thoughts/comments? I will update the FS if this sounds correct.
Thanks,
Prachi
-Original Message-----
From: Prachi Damle [mailto:prachi.da...@ci
You might also want to set this under preferences-> Java -> Editor -> Save
Actions and apply it to all projects.
Prachi
-Original Message-
From: Fang Wang [mailto:fang.w...@citrix.com]
Sent: Friday, February 22, 2013 11:51 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Commits
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1367.
--
Resolution: Fixed
> NPE noticed in logs while AgentMonitor is monitoring
Prachi Damle created CLOUDSTACK-1367:
Summary: NPE noticed in logs while AgentMonitor is monitoring the
host ping interval
Key: CLOUDSTACK-1367
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1367
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1362.
--
Resolution: Fixed
> EC2 dns-name filter support for EC2 describeInstances
Prachi Damle created CLOUDSTACK-1362:
Summary: EC2 dns-name filter support for EC2 describeInstances API
is broken
Key: CLOUDSTACK-1362
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1362
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583446#comment-13583446
]
Prachi Damle commented on CLOUDSTACK-1339:
--
Parth,
Can you reproduce
3
4.1.0<https://issues.apache.org/jira/browse/CLOUDSTACK/fixforversion/12323253>
4.1.0
Actions<https://issues.apache.org/jira/rest/api/1.0/issues/12632536/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED|fc876586a99a5a103fc77d403735ef2f67bba6c9|lin>
[cid:image001.gif@01CE0FB6.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582679#comment-13582679
]
Prachi Damle commented on CLOUDSTACK-1339:
--
Along with the manage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-322.
-
Resolution: Invalid
Issue with CloudPlatform.
> During upgr
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1346.
--
Resolution: Fixed
> Check to see if external devices are used in the netw
Prachi Damle created CLOUDSTACK-1346:
Summary: Check to see if external devices are used in the network,
is hardcoded for specific devices
Key: CLOUDSTACK-1346
URL: https://issues.apache.org/jira/browse
Hugo,
I just changed all the *NetworkGuru :: implement() to first try to retrieve
the physicalNetworkId from the NetworkVO. If it is null, then they can call the
regular code to derive it using _networkModel.findPhysicalNetworkId.
May be you need to change the unit test mocking due to this?
-
Prachi Damle created CLOUDSTACK-1344:
Summary: Typo in use.external.dns setting description
Key: CLOUDSTACK-1344
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1344
Project: CloudStack
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1344.
--
Resolution: Fixed
> Typo in use.external.dns setting descript
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1331.
--
Resolution: Fixed
> Upgrade fails for a 2.2.14 Zone having multiple gu
Prachi Damle created CLOUDSTACK-1331:
Summary: Upgrade fails for a 2.2.14 Zone having multiple guest
networks using network_tags and Public Vlan
Key: CLOUDSTACK-1331
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1330.
--
Resolution: Fixed
> ec2-run-instances - When -n option is used to dep
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581736#comment-13581736
]
Prachi Damle commented on CLOUDSTACK-1330:
--
Fixed.
Changes:
- Instea
Prachi Damle created CLOUDSTACK-1330:
Summary: ec2-run-instances - When -n option is used to deploy
multiple Vms API returns error even though few of the Vms have been deployed
successfully.
Key: CLOUDSTACK-1330
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1307.
--
Resolution: Fixed
> Noticed NPE when we put host in maintenance mode
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579707#comment-13579707
]
Prachi Damle commented on CLOUDSTACK-1307:
--
Fixed.
Changes:
- Us
Prachi Damle created CLOUDSTACK-1307:
Summary: Noticed NPE when we put host in maintenance mode in
clustered management setup
Key: CLOUDSTACK-1307
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1307
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Friday, February 15, 2013 9:26 AM
To: cloudstack-dev@incubator.apache.org
Subject: Question about deployVirtualMachine API Call
Hi,
I would like to use the userdata parameter of the deployVirtualMachine A
the plugin implementations to the deployment.
-Prachi
-Original Message-
From: Manan Shah
Sent: Thursday, February 14, 2013 11:41 AM
To: Prachi Damle; Alex Huang; cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] Affinity / Anti-affinity Rules
Hi Prachi,
My understanding is
.
- Prachi Damle
On Feb. 13, 2013, 6:18 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
Congratulations Likitha! Well-deserved indeed :)
Happy committing! ;)
-Prachi
-Original Message-
From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of Rohit
Yadav
Sent: Wednesday, February 13, 2013 10:27 AM
To: cloudstack-dev@incubator.apache.org
Cc: Likitha Shetty
> On Feb. 8, 2013, 1:03 a.m., Prachi Damle wrote:
> > Few comments:
> > 1) In Allocators, it would be good to put the logic to check if host is
> > suitable in separate methods that adding logic in-place. This will help
> > readability. e.g. methods
check and submit
again?
Also, instead of iterating through the volumeIdSet Map, you could have just
checked if the volumeId is present using containsKey method of the HashMap.
- Prachi Damle
On Feb. 1, 2013, 11:22 a.m., Likitha Shetty wrote
:c3be0f995d1b3f5ee1355971143234871ad517d9
- Prachi Damle
On Feb. 1, 2013, 11:39 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
:33964cf6dab69c486d6801f97ce6354ff2e6a2a2
- Prachi Damle
On Feb. 1, 2013, 10:36 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
:04a571e7ef350082c157f96d6ce7574c5b00d306
- Prachi Damle
On Feb. 1, 2013, 9:51 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
-
>
> (Updated Feb. 12, 2013, 12:18 p.m.)
>
>
> Review request for cloudstack and Prachi Damle.
>
>
> Description
> ---
>
> Convert space characters in the parameters to %20 while forming a query
> string after url-encode because java.net.URLEncoder
:c26b02a0a7fd52b4daa1c063d8e04a8866d8e0e0
- Prachi Damle
On Feb. 1, 2013, 9:33 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
:a9de95679e61d938540458f05a178858d25809fb
- Prachi Damle
On Feb. 1, 2013, 6:37 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
: 52b81f8bffb09fa9a4134a5f55ad2d676d24ef3f
- Prachi Damle
On Feb. 1, 2013, 6:29 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
:06fd21bd4498479c52bcf12921bf867190ace3a1
- Prachi Damle
On Feb. 1, 2013, 6:19 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
: 0b43efbcbf34ccd0a5a362b18fab3670384a239d
- Prachi Damle
On Feb. 1, 2013, 11:52 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
seem to be doing the
other way instead.
The changes done seem to encode following 3 characters in the input URL: space,
* and ~:
Please can you update if you tested all 3 inputs?
- Prachi Damle
On Feb. 1, 2013, 6:10 a.m., Likitha Shetty wrote
.
Commit hash:1e8648c92de9df281aaabc5067d6d1d61be3a4a3
- Prachi Damle
On Feb. 1, 2013, 6:03 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
: 5d09b9fd3a025491c59d76af1af7412fa8d3cb28
- Prachi Damle
On Feb. 1, 2013, 5:55 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
hash:
f839ad7b53ff805712852da0dd564b9857236c33
- Prachi Damle
On Feb. 1, 2013, 5:48 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
:05280976e5caa4cc9105223fea96163abb0b6935
- Prachi Damle
On Feb. 1, 2013, 5:31 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
I have updated the FS with the addition of the DeploymentPlanningManager
entity.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS+-+Affinity-Anti-affinity+groups
-Prachi
-Original Message-
From: Prachi Damle
Sent: Thursday, February 07, 2013 1:38 PM
To: Alex Huang
; cloudstack-dev@incubator.apache.org;
Prachi Damle
Cc: Rayees Namathponnan
Subject: Re: [ACS41][QA]Blockers to run automation
I am looking at the bug, could not reproduce this by running locally from
source code. Have updated the bug to ask for setup details. Rayees, please
update the bug at your
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle reassigned CLOUDSTACK-1200:
Assignee: Rohit Yadav (was: Prachi Damle)
> Unknown col
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574860#comment-13574860
]
Prachi Damle commented on CLOUDSTACK-1200:
--
The need of sto
Prachi Damle created CLOUDSTACK-1217:
Summary: Need to refactor cloud-engine createVM flow to handle
Storage and Network allocation separately.
Key: CLOUDSTACK-1217
URL: https://issues.apache.org/jira/browse
: 2364ada4df2543c75d5a569de73a83f4a235afa8
- Prachi Damle
On Feb. 1, 2013, 5:19 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
:b5e28038cbc85e4e39bfc2b71927e2935b1f1673
- Prachi Damle
On Feb. 1, 2013, 5:04 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
:12ad296b6c323f017f2fdbeb1e9be79c81c8dca2
- Prachi Damle
On Feb. 1, 2013, 4:52 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
: 4e4edc9e42f69b10314d0b09629546acc4db333a
- Prachi Damle
On Feb. 1, 2013, 4:41 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
of storage allocation when host
is not suitable.
3) Should db changes be in schema 40to402 instead of 401?
4) Need to add unit-tests. Tests can mock the DAO responses and just run the
allocator changes to check if they output the correct list of hosts.
- Prachi Damle
On Feb. 7, 2013, 3:05 p.m
Alex,
Thanks for the detailed review. I will couple the affinity design with the
deployment planner refactoring I had next in line then. Will update the FS with
these details.
-Prachi
-Original Message-
From: Alex Huang
Sent: Wednesday, February 06, 2013 12:00 PM
To: Prachi Damle
Hi Alex,
Thanks for the review, I have answered inline. Please comment.
I guess the FS needs more description reasoning the 2-component design to avoid
confusion.
-Prachi
-Original Message-
From: Alex Huang
Sent: Tuesday, February 05, 2013 4:49 PM
To: Prachi Damle; cloudstack-dev
ed on different hosts.
> For the first implementation, the guarantee would only apply to initial
> provisioning.
It could actually apply any time a planner is used to select a host (which I
think also includes CloudStack "HA").
> @Manan, would that be sufficient?
>
>
Hi Bharat / Abhi,
Even currently we always store actuals in the DB in op_host_capacity table.
During allocation, the overprovisioning ratios are applied dynamically to find
the overprovisioned "total" capacity.
So it's good that even the new way will follow that.
>Major differences are
>1.) In
, important to have! Looks
good.
- Prachi Damle
On Dec. 21, 2012, 1:04 p.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
.
- Prachi Damle
On Dec. 12, 2012, 10:31 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8483/#review15969
---
Ship it!
Ship It!
- Prachi Damle
On Dec. 12, 2012, 10:33 a.m
.
- Prachi Damle
On Dec. 12, 2012, 10:35 a.m., Likitha Shetty wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8513/#review15966
---
Ship it!
- Prachi Damle
On Dec. 12, 2012, 10:36 a.m., Likitha
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8468/#review15963
---
Ship it!
Fix is correct.
- Prachi Damle
On Dec. 12, 2012, 10:38
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8465/#review15959
---
Ship it!
Ship It!
- Prachi Damle
On Dec. 12, 2012, 10:29 a.m
testing framework to
mock servlet container/mock servlet setup due to its design, that Likitha will
look into separately. This should be possible with Spring introduction.
- Prachi Damle
On Dec. 12, 2012, 10:25 a.m., Likitha Shetty wrote
d time to code.
>>
>>
>>
>> With the above in consideration, is it possible to commit these
>>patches to master for 4.1 while we continue to work on writing a
>>unit-test framework for AWSAPI?
>>
>>
>>
>> [1] http://mail-archives.apache.o
Hi All,
I have reviewed the patches for the [EC2 Query API] support in awsapi and they
look good. However there are no unit tests added [like many other feature
branches].
So the merge of these patches is pending.
Should I merge them to master, since 4.1 release may miss out EC2 Query API
s
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8465/#review15599
---
Code fix looks fine. Unit-tests should cover this.
- Prachi Damle
>>>But for mysql in rhel5.x, the default mysql only allows 1000 bytes for each
>>>foreign key
This seems to be the limitation of MyISAM engine. Using InnoDB does not cause
this issue.
-Original Message-
From: Frank Zhang [mailto:frank.zh...@citrix.com]
Sent: Friday, January 18, 2013 4:
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-1017.
--
Resolution: Fixed
> Cloud-setup-databases operation failed in RH
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557867#comment-13557867
]
Prachi Damle commented on CLOUDSTACK-1017:
--
root@vl-sjc-cloud-
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557866#comment-13557866
]
Prachi Damle commented on CLOUDSTACK-1017:
--
The key-length limit is pu
1 - 100 of 195 matches
Mail list logo