Re: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql

[Rohit Yadav]

On Sat, Feb 16, 2013 at 10:49 AM, Abhinandan Prateek
 wrote:
> Any schema changes that are made after 4.1 targeted for 4.2 should be in
> /db/db/schema-410to420.sql

Good point Abhi, while I'm not sure about the recent checking on create-schema.
Developers please put new changes in 410to420, I'll create a stub and
post another email so it gets attention.

Regards.

>
> -abhi
>
> On 16/02/13 10:39 AM, "Koushik Das"  wrote:
>
>>For schema changes for features that are not part of 4.1 what is the
>>place to put the changes.
>>
>>> -Original Message-
>>> From: Min Chen [mailto:min.c...@citrix.com]
>>> Sent: Friday, February 15, 2013 11:43 PM
>>> To: Rohit Yadav; Edison Su; cloudstack-dev@incubator.apache.org
>>> Cc: Sheng Yang; Alex Huang; Kishan Kavala
>>> Subject: Re: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql
>>>
>>> Rohit, scripts run in create-schema-view.sql have been included  in
>>>schema-
>>> 40to410.sql. I will take care of removing create-schema-view.sql today.
>>>
>>> Thanks
>>> -min
>>>
>>> On 2/15/13 2:58 AM, "Rohit Yadav"  wrote:
>>>
>>> >Edison, you'd created a 4.1-new-db-schema sql, may I merge
>>> >4.1-new-db-schema.sql  to db/db/schema-40to410.sql? We'll also need a
>>> >db/db/schema-40to410-cleanup.sql and upgrading class.
>>> >
>>> >There is some difference between the 4.0 create-schema.sql and that in
>>> >4.1: http://people.apache.org/~bhaisaab/diff-create-schema-40-41.sql
>>> >
>>> >Alex suggested in last discussion that we should not change the schema
>>> >file and have upgrade paths and cleanup paths. This would help us do
>>> >rolling upgrades. But Alex, there are a lot of difference between the
>>> >4.0 schema and 4.1 schema sqls (about 4k lines of diff):
>>> >http://people.apache.org/~bhaisaab/diff4041sqls.sql If we don't want
>>> >developers to change anything in the schema files, how do you propose
>>> >we fix it now for 4.1? Move all these changes to 40to41 sql?
>>> >
>>> >Sheng (ipv6), Kishan (regions), Vijay (autoscale) I see some create
>>> >schema changes, should we move them to db/db/schema-40to410.sql?
>>> >
>>> >Min, the create-schema-view did not exist for 4.0, should we keep it as
>>> >it as, our move it as upgrade path?
>>> >
>>> >For 4.1, we should do following changes so DatabaseCreator could be
>>> >refactored and used starting 4.2/master:
>>> >- Change version to 4.0 in create-schema
>>> >- Make sure there is difference between 4.0 and 4.1 create-schema sqls
>>> >- Move new additions to db/db/schema-40to410.sql, define a cleanup
>>> >path/sql and upgrading class from 40-41
>>> >- Fix cloudstack-setup-databases, for 4.1 we won't use databasecreator,
>>> >stick with the present script (won't risk regressions and whatnot)
>>> >
>>> >Regards.
>>
>

Re: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql

[Rohit Yadav]

On Fri, Feb 15, 2013 at 11:43 PM, Min Chen  wrote:
> Rohit, scripts run in create-schema-view.sql have been included  in
> schema-40to410.sql. I will take care of removing create-schema-view.sql
> today.

Thanks Min, can you just recheck if they in sync, i.e. all rules in
create-schema-view are in schema-40to410?
Let's do one thing we can still keep it for 5.0 and till then have all
new updates synced to schema upgrade sqls, the only extra work would
be to sync the create-schema-view with the upgrade sql files.

Regards.

>
> Thanks
> -min
>
> On 2/15/13 2:58 AM, "Rohit Yadav"  wrote:
>
>>Edison, you'd created a 4.1-new-db-schema sql, may I merge
>>4.1-new-db-schema.sql  to db/db/schema-40to410.sql? We'll also need a
>>db/db/schema-40to410-cleanup.sql and upgrading class.
>>
>>There is some difference between the 4.0 create-schema.sql and that in
>>4.1: http://people.apache.org/~bhaisaab/diff-create-schema-40-41.sql
>>
>>Alex suggested in last discussion that we should not change the schema
>>file and have upgrade paths and cleanup paths. This would help us do
>>rolling upgrades. But Alex, there are a lot of difference between the
>>4.0 schema and 4.1 schema sqls (about 4k lines of diff):
>>http://people.apache.org/~bhaisaab/diff4041sqls.sql If we don't want
>>developers to change anything in the schema files, how do you propose
>>we fix it now for 4.1? Move all these changes to 40to41 sql?
>>
>>Sheng (ipv6), Kishan (regions), Vijay (autoscale) I see some create
>>schema changes, should we move them to db/db/schema-40to410.sql?
>>
>>Min, the create-schema-view did not exist for 4.0, should we keep it
>>as it as, our move it as upgrade path?
>>
>>For 4.1, we should do following changes so DatabaseCreator could be
>>refactored and used starting 4.2/master:
>>- Change version to 4.0 in create-schema
>>- Make sure there is difference between 4.0 and 4.1 create-schema sqls
>>- Move new additions to db/db/schema-40to410.sql, define a cleanup
>>path/sql and upgrading class from 40-41
>>- Fix cloudstack-setup-databases, for 4.1 we won't use
>>databasecreator, stick with the present script (won't risk regressions
>>and whatnot)
>>
>>Regards.
>

Re: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql

[Rohit Yadav]

On Fri, Feb 15, 2013 at 11:26 PM, Edison Su  wrote:
>
>
>> -Original Message-
>> From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf
>> Of Rohit Yadav
>> Sent: Friday, February 15, 2013 2:58 AM
>> To: Edison Su; cloudstack-dev@incubator.apache.org
>> Cc: Sheng Yang; Alex Huang; Kishan Kavala; Min Chen
>> Subject: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql
>>
>> Edison, you'd created a 4.1-new-db-schema sql, may I merge 4.1-new-db-
>> schema.sql  to db/db/schema-40to410.sql? We'll also need a db/db/schema-
>> 40to410-cleanup.sql and upgrading class.
>
> Yes, it should be merged into schema-40to410.sql

Thanks merged, and removed 4.1-new-db-schema sql

Pl. check the following commit on master:
commit f2ae6dcda9b93f77f1d9ac262e86e742ce19b0f1
Author: Rohit Yadav 
Date:   Sat Feb 16 12:44:45 2013 +0530

db: Remove and merge 4.1-new-db-schema.sql to schema-40to410.sql

Signed-off-by: Rohit Yadav 


Hugo, are you still going to get rid of the "use cloud" dialect and
couple database names with columns?

Regards.

>
>>
>> There is some difference between the 4.0 create-schema.sql and that in
>> 4.1: http://people.apache.org/~bhaisaab/diff-create-schema-40-41.sql
>>
>> Alex suggested in last discussion that we should not change the schema file
>> and have upgrade paths and cleanup paths. This would help us do rolling
>> upgrades. But Alex, there are a lot of difference between the
>> 4.0 schema and 4.1 schema sqls (about 4k lines of diff):
>> http://people.apache.org/~bhaisaab/diff4041sqls.sql If we don't want
>> developers to change anything in the schema files, how do you propose we
>> fix it now for 4.1? Move all these changes to 40to41 sql?
>>
>> Sheng (ipv6), Kishan (regions), Vijay (autoscale) I see some create schema
>> changes, should we move them to db/db/schema-40to410.sql?
>>
>> Min, the create-schema-view did not exist for 4.0, should we keep it as it 
>> as,
>> our move it as upgrade path?
>>
>> For 4.1, we should do following changes so DatabaseCreator could be
>> refactored and used starting 4.2/master:
>> - Change version to 4.0 in create-schema
>> - Make sure there is difference between 4.0 and 4.1 create-schema sqls
>> - Move new additions to db/db/schema-40to410.sql, define a cleanup
>> path/sql and upgrading class from 40-41
>> - Fix cloudstack-setup-databases, for 4.1 we won't use databasecreator, stick
>> with the present script (won't risk regressions and whatnot)
>>
>> Regards.

Re: git commit: refs/heads/master - added db.properties to usage test resources

[Rohit Yadav]

On Fri, Feb 15, 2013 at 10:41 PM, Hugo Trippaers
 wrote:
> Hey Kishan,
>
> This is probably not going to work. This only works if you have an actual 
> database, we need the test to run without a database by mocking all DAOs

Kishan, I can help you with that, monday or today?

Regards.

>
> Nice work on the tests by the way!
>
> Hugo
>
>> -Original Message-
>> From: kis...@apache.org [mailto:kis...@apache.org]
>> Sent: Friday, February 15, 2013 6:09 PM
>> To: cloudstack-comm...@incubator.apache.org
>> Subject: git commit: refs/heads/master - added db.properties to usage test
>> resources
>>
>> Updated Branches:
>>   refs/heads/master 2beb66fd3 -> b54db07d2
>>
>>
>> added db.properties to usage test resources
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/incubator-
>> cloudstack/commit/b54db07d
>> Tree: http://git-wip-us.apache.org/repos/asf/incubator-
>> cloudstack/tree/b54db07d
>> Diff: http://git-wip-us.apache.org/repos/asf/incubator-
>> cloudstack/diff/b54db07d
>>
>> Branch: refs/heads/master
>> Commit: b54db07d20893a437bb327f08d891553aa98aef8
>> Parents: 2beb66f
>> Author: Kishan Kavala 
>> Authored: Fri Feb 15 22:35:45 2013 +0530
>> Committer: Kishan Kavala 
>> Committed: Fri Feb 15 22:39:04 2013 +0530
>>
>> --
>>  usage/test/resources/db.properties |   70
>> +++
>>  1 files changed, 70 insertions(+), 0 deletions(-)
>> --
>>
>>
>> http://git-wip-us.apache.org/repos/asf/incubator-
>> cloudstack/blob/b54db07d/usage/test/resources/db.properties
>> --
>> diff --git a/usage/test/resources/db.properties
>> b/usage/test/resources/db.properties
>> new file mode 100644
>> index 000..18bf54c
>> --- /dev/null
>> +++ b/usage/test/resources/db.properties
>> @@ -0,0 +1,70 @@
>> +# Licensed to the Apache Software Foundation (ASF) under one # or more
>> +contributor license agreements.  See the NOTICE file # distributed with
>> +this work for additional information # regarding copyright ownership.
>> +The ASF licenses this file # to you under the Apache License, Version
>> +2.0 (the # "License"); you may not use this file except in compliance #
>> +with the License.  You may obtain a copy of the License at #
>> +#   http://www.apache.org/licenses/LICENSE-2.0
>> +#
>> +# Unless required by applicable law or agreed to in writing, # software
>> +distributed under the License is distributed on an # "AS IS" BASIS,
>> +WITHOUT WARRANTIES OR CONDITIONS OF ANY # KIND, either express or
>> +implied.  See the License for the # specific language governing
>> +permissions and limitations # under the License.
>> +
>> +
>> +# management server clustering parameters, change cluster.node.IP to
>> +the machine IP address # in which the management server(Tomcat) is
>> +running
>> +cluster.node.IP=127.0.0.1
>> +cluster.servlet.port=9090
>> +
>> +# CloudStack database settings
>> +db.cloud.username=cloud
>> +db.cloud.password=cloud
>> +db.root.password=
>> +db.cloud.host=localhost
>> +db.cloud.port=3306
>> +db.cloud.name=cloud
>> +
>> +# CloudStack database tuning parameters
>> +db.cloud.maxActive=250
>> +db.cloud.maxIdle=30
>> +db.cloud.maxWait=1
>> +db.cloud.autoReconnect=true
>> +db.cloud.validationQuery=SELECT 1
>> +db.cloud.testOnBorrow=true
>> +db.cloud.testWhileIdle=true
>> +db.cloud.timeBetweenEvictionRunsMillis=4
>> +db.cloud.minEvictableIdleTimeMillis=24
>> +db.cloud.poolPreparedStatements=false
>> +db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&prep
>> StmtC
>> +acheSqlLimit=4096
>> +
>> +# usage database settings
>> +db.usage.username=cloud
>> +db.usage.password=cloud
>> +db.usage.host=localhost
>> +db.usage.port=3306
>> +db.usage.name=cloud_usage
>> +
>> +# usage database tuning parameters
>> +db.usage.maxActive=100
>> +db.usage.maxIdle=30
>> +db.usage.maxWait=1
>> +db.usage.autoReconnect=true
>> +
>> +# awsapi database settings
>> +db.awsapi.name=cloudbridge
>> +
>> +# Simulator database settings
>> +db.simulator.username=cloud
>> +db.simulator.password=cloud
>> +db.simulator.host=localhost
>> +db.simulator.port=3306
>> +db.simulator.name=simulator
>> +db.simulator.maxActive=250
>> +db.simulator.maxIdle=30
>> +db.simulator.maxWait=1
>> +db.simulator.autoReconnect=true
>

RE: android cloudstack client

[Pranav Saxena]

Hi abhi ,

Even me and Brian had started to design the front end for an Android/ iOS app 
for cloudstack and we were using the phoneGap API to handle few of the touch 
functionalities for this . We thought that when we have a basic prototype up 
and working , we'll share it with the community . 

Our plan is to have a basic set of features like starting an instance , 
stopping an instance , may be take a snapshot and list the capacity charts on 
the dashboard . 

Could you also elaborate on what exactly is your plan and how do you plan to 
have the UI design for your work ? May be we should collaborate on this and 
avoid any redundant work . 

Regards,
Pranav

-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] 
Sent: Saturday, February 16, 2013 9:04 AM
To: cloudstack dev
Subject: android cloudstack client

Guys,
  I was wondering how useful will be a android (and iOS) cloudstack client will 
be ? I have started to put together a android client initially to show dash 
board and later probably will add more functionality.
Before putting in more effort, wanted to probe the community if this is 
something they will want to use ?

-abhi

RE: [ACS4.2] LDAP UI

[Pranav Saxena]

I'll have to check if it includes LDAP configuration in the response parameters 
. If yes , then we can do so . Could you give me a link to where I could find 
the details about the getConfiguration API ?

Regards,
Pranav

-Original Message-
From: Abhinandan Prateek 
Sent: Saturday, February 16, 2013 8:59 AM
To: Pranav Saxena; cloudstack-dev@incubator.apache.org
Subject: Re: [ACS4.2] LDAP UI

Pranav,
  I was wondering we have API to get configuration, can't we reuse the same to 
get ldap config ?

-abhi




On 15/02/13 7:36 PM, "Pranav Saxena"  wrote:

>Abhi ,
>
>Just wanted to check with you if we have a list LDAP configuration API 
>call in CS ? Because I would need this to list the current LDAP 
>configuration on the UI  , if it exists .
>
>Regards,
>Pranav
>
>-Original Message-
>From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>Sent: Thursday, February 14, 2013 12:27 PM
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [ACS4.2] LDAP UI
>
>
>On 14/02/13 11:30 AM, "David Nalley"  wrote:
>
>>On Thu, Feb 14, 2013 at 12:51 AM, Pranav Saxena 
>> wrote:
>>> To configure LDAP  , we need to pass in few multiple mandatory 
>>>parameters -
>>>
>>> hostnameHostname or ip address of the ldap server eg:
>>>my.ldap.com
>>> queryfilter You specify a query filter here, which narrows down the
>>>users, who can be part of this domain.
>>> searchbase  The search base defines the starting point for the
>>>search in the directory tree
>>>
>>> If you are referring to Global settings , that can be done but then 
>>>we'll have to have three Ldap config parameters there . if that is a 
>>>good design to handle this , then yes we can do that. Perhaps , the 
>>>idea is to have a single dialog box where a user could supply three 
>>>values and configure and debug them if something goes wrong.
>>
>>
>>Those are the mandatory API inputs for CloudStack.
>>But almost all environments will require username/password for binding 
>>at a minimum, and you should probably, and prolly offer the SSL option 
>>as well. Port should probably be an option too.
>>
>>Without at least bind creds, the API configuration is practically 
>>useless on any modern LDAP server.
>>
>>--David
>
>The admin guide documents the LDAP API. SSL is supported.
>http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0
>.0-
>i
>ncubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Admin_Guid
>e-e
>n
>-US.pdf
>
>Look for LDAP configuration. In short you have following config params:
>
>hostname
>searchbase
>queryfilter
>binddn
>bindpass
>port
>ssl
>truststore
>truststorepass
>response
>
>
>
>-abhi
>
>
>
>>
>

[jira] [Resolved] (CLOUDSTACK-863) Non-printable characters (ASCII control character) such as %00 or %0025 are getting stored in raw/non encoded form in the database.

[Rohit Yadav (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav resolved CLOUDSTACK-863.


Resolution: Fixed

Shipped on master and 4.1. Thanks Likitha for your patch.

> Non-printable characters (ASCII control character) such as %00 or %0025 are 
> getting stored in raw/non encoded form in the database.
> ---
>
> Key: CLOUDSTACK-863
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-863
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.0.0
>Reporter: Likitha Shetty
>Assignee: Likitha Shetty
> Fix For: 4.1.0
>
> Attachments: get.png, UI.jpg.jpeg
>
>
> Non-printable characters such as %00 or %0025 are getting stored in raw/non 
> encoded form in the database.
> It results in empty pages for all users loading the corrupted object in the 
> web interface (a corrupted Instance in this case - see attached UI.jpg.jpeg) 
> It also results in the API call results getting truncated with an error when 
> it encounters the non-printable characters

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-863) Non-printable characters (ASCII control character) such as %00 or %0025 are getting stored in raw/non encoded form in the database.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579729#comment-13579729
 ] 

ASF subversion and git services commented on CLOUDSTACK-863:


Commit ed06c16944ec28b254a5f1c7acb9152c44918467 in branch refs/heads/4.1 from 
[~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=ed06c16 ]

CLOUDSTACK-863: Fix Non-printable characters in api call

Non-printable characters results in empty pages for all users loading the
corrupted object in the web interface. It also results in the API call results
getting truncated with an error when it encounters the non-printable characters.
Every decoded parameter value is checked for control character using OWASP's
ESAPI library.

Signed-off-by: Rohit Yadav 
(cherry picked from commit 87b668b71b34c93e9ba85d4708a1c04f4020f6bf)

Signed-off-by: Rohit Yadav 


> Non-printable characters (ASCII control character) such as %00 or %0025 are 
> getting stored in raw/non encoded form in the database.
> ---
>
> Key: CLOUDSTACK-863
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-863
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.0.0
>Reporter: Likitha Shetty
>Assignee: Likitha Shetty
> Fix For: 4.1.0
>
> Attachments: get.png, UI.jpg.jpeg
>
>
> Non-printable characters such as %00 or %0025 are getting stored in raw/non 
> encoded form in the database.
> It results in empty pages for all users loading the corrupted object in the 
> web interface (a corrupted Instance in this case - see attached UI.jpg.jpeg) 
> It also results in the API call results getting truncated with an error when 
> it encounters the non-printable characters

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-863) Non-printable characters (ASCII control character) such as %00 or %0025 are getting stored in raw/non encoded form in the database.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579728#comment-13579728
 ] 

ASF subversion and git services commented on CLOUDSTACK-863:


Commit 87b668b71b34c93e9ba85d4708a1c04f4020f6bf in branch refs/heads/master 
from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=87b668b ]

CLOUDSTACK-863: Fix Non-printable characters in api call

Non-printable characters results in empty pages for all users loading the
corrupted object in the web interface. It also results in the API call results
getting truncated with an error when it encounters the non-printable characters.
Every decoded parameter value is checked for control character using OWASP's
ESAPI library.

Signed-off-by: Rohit Yadav 


> Non-printable characters (ASCII control character) such as %00 or %0025 are 
> getting stored in raw/non encoded form in the database.
> ---
>
> Key: CLOUDSTACK-863
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-863
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.0.0
>Reporter: Likitha Shetty
>Assignee: Likitha Shetty
> Fix For: 4.1.0
>
> Attachments: get.png, UI.jpg.jpeg
>
>
> Non-printable characters such as %00 or %0025 are getting stored in raw/non 
> encoded form in the database.
> It results in empty pages for all users loading the corrupted object in the 
> web interface (a corrupted Instance in this case - see attached UI.jpg.jpeg) 
> It also results in the API call results getting truncated with an error when 
> it encounters the non-printable characters

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-176) Tooltip widget

[Jessica Tomechak (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579716#comment-13579716
 ] 

Jessica Tomechak commented on CLOUDSTACK-176:
-

Parth has opened additional bugs for some of the comments raised: 
CLOUDSTACK-1282, CLOUDSTACK-1283, CLOUDSTACK-1284, CLOUDSTACK-1285, 
CLOUDSTACK-1286.

> Tooltip widget
> --
>
> Key: CLOUDSTACK-176
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-176
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Reporter: Sonny Chhen
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: screen 1.jpg, screen 2.jpg, screen 3.jpg, screen 4.jpg, 
> tooltip1.png, tooltip.png
>
>
> Create tooltip widget to be populated dynamically from content provided by 
> documentation.
> Release Planning:
> Functional Spec: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+-+Dynamic+Tooltip
> Dev list discussion: 
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3c7914b38a4445b34aa16eb9f1352942f1012f1078f...@sjcpmailbox01.citrite.net%3E
> Feature branch: N/A
> Documentation task: N/A

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1285) UI -Tooltip - Lengthy and inconsistent description among toolips

[Jessica Tomechak (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579714#comment-13579714
 ] 

Jessica Tomechak commented on CLOUDSTACK-1285:
--

The guideline we used for the first round of tooltips was 100 characters 
maximum. "A name for the zone" is too short. It tells you nothing useful - just 
restates the name of the field. Knowing what the name will be used for is 
helpful. Knowing whether this is a new name you're supposed to come up with 
yourself, vs. a name that has to match some already-existing value, is also 
helpful. The advice about best practices for choosing a good name might 
admittedly be overkill. I'd suggest something in between, like "Give the new 
template a name. This name will be visible to users."

> UI -Tooltip - Lengthy and inconsistent description among toolips
> 
>
> Key: CLOUDSTACK-1285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, UI
>Affects Versions: 4.1.0
> Environment: RHEL 6.3 Build#15
>Reporter: Parth Jagirdar
>Priority: Minor
> Attachments: 3.jpg, 4.jpg
>
>
>  "A unique name for the template. This will be visible to users, so choose 
> something descriptive" ; I think 94 Characters are too much for a ToolTip 
> representing name. (Screen 4)
> And is also inconsistent with other tooltips for names which are more concise 
> and simple such as "A name for the Zone". (Refer to Screen 4 and compare it 
> to Screen 3)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql

[Abhinandan Prateek]

Any schema changes that are made after 4.1 targeted for 4.2 should be in
/db/db/schema-410to420.sql

-abhi

On 16/02/13 10:39 AM, "Koushik Das"  wrote:

>For schema changes for features that are not part of 4.1 what is the
>place to put the changes.
>
>> -Original Message-
>> From: Min Chen [mailto:min.c...@citrix.com]
>> Sent: Friday, February 15, 2013 11:43 PM
>> To: Rohit Yadav; Edison Su; cloudstack-dev@incubator.apache.org
>> Cc: Sheng Yang; Alex Huang; Kishan Kavala
>> Subject: Re: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql
>> 
>> Rohit, scripts run in create-schema-view.sql have been included  in
>>schema-
>> 40to410.sql. I will take care of removing create-schema-view.sql today.
>> 
>> Thanks
>> -min
>> 
>> On 2/15/13 2:58 AM, "Rohit Yadav"  wrote:
>> 
>> >Edison, you'd created a 4.1-new-db-schema sql, may I merge
>> >4.1-new-db-schema.sql  to db/db/schema-40to410.sql? We'll also need a
>> >db/db/schema-40to410-cleanup.sql and upgrading class.
>> >
>> >There is some difference between the 4.0 create-schema.sql and that in
>> >4.1: http://people.apache.org/~bhaisaab/diff-create-schema-40-41.sql
>> >
>> >Alex suggested in last discussion that we should not change the schema
>> >file and have upgrade paths and cleanup paths. This would help us do
>> >rolling upgrades. But Alex, there are a lot of difference between the
>> >4.0 schema and 4.1 schema sqls (about 4k lines of diff):
>> >http://people.apache.org/~bhaisaab/diff4041sqls.sql If we don't want
>> >developers to change anything in the schema files, how do you propose
>> >we fix it now for 4.1? Move all these changes to 40to41 sql?
>> >
>> >Sheng (ipv6), Kishan (regions), Vijay (autoscale) I see some create
>> >schema changes, should we move them to db/db/schema-40to410.sql?
>> >
>> >Min, the create-schema-view did not exist for 4.0, should we keep it as
>> >it as, our move it as upgrade path?
>> >
>> >For 4.1, we should do following changes so DatabaseCreator could be
>> >refactored and used starting 4.2/master:
>> >- Change version to 4.0 in create-schema
>> >- Make sure there is difference between 4.0 and 4.1 create-schema sqls
>> >- Move new additions to db/db/schema-40to410.sql, define a cleanup
>> >path/sql and upgrading class from 40-41
>> >- Fix cloudstack-setup-databases, for 4.1 we won't use databasecreator,
>> >stick with the present script (won't risk regressions and whatnot)
>> >
>> >Regards.
>

[jira] [Commented] (CLOUDSTACK-1286) UI - Tooltip - Missing Tooltips for some key features

[Jessica Tomechak (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579711#comment-13579711
 ] 

Jessica Tomechak commented on CLOUDSTACK-1286:
--

I think we did not support checkboxes in the first round of tooltips, for some 
technical reason. Fixing this might require some coding to overcome whatever 
that limitation was. Adding bfederle to the bug in case he can comment.

> UI - Tooltip - Missing Tooltips for some key features
> -
>
> Key: CLOUDSTACK-1286
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1286
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, UI
>Affects Versions: 4.1.0
> Environment: RHEL 6.3 Build #15
>Reporter: Parth Jagirdar
>
> A few drop down menus(Select’s) have tooltips and almost no checkbox has any. 
> (Again this was brief sanity test). 
> I think ToolTips for "Public" and "Featured" on template registration wizard 
> would be worth reading for a new user.
> Marking this Major as if Tooltips are at all required then these features are 
> the few places they should go in first.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1299) Errors in 4.5.5 section of installation guide

[Jessica Tomechak (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579710#comment-13579710
 ] 

Jessica Tomechak commented on CLOUDSTACK-1299:
--

The title of the section is "Prepare NFS Shares."

> Errors in 4.5.5 section of installation guide
> -
>
> Key: CLOUDSTACK-1299
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1299
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.0.1
>Reporter: sebastien goasguen
> Fix For: 4.0.2
>
>
> In 
> http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/management-server-install-flow.html
> Section 4.5.5, the first note mentions RDB instead of RBD. 
> More critical is 4.5.5.2 which installs nfs server but looks for 
> /etc/sysconfig/nfs which is a rhel like configurationneed to fix

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql

[Koushik Das]

For schema changes for features that are not part of 4.1 what is the place to 
put the changes. 

> -Original Message-
> From: Min Chen [mailto:min.c...@citrix.com]
> Sent: Friday, February 15, 2013 11:43 PM
> To: Rohit Yadav; Edison Su; cloudstack-dev@incubator.apache.org
> Cc: Sheng Yang; Alex Huang; Kishan Kavala
> Subject: Re: Merge 4.1-new-db-schema.sql to db/db/schema-40to410.sql
> 
> Rohit, scripts run in create-schema-view.sql have been included  in schema-
> 40to410.sql. I will take care of removing create-schema-view.sql today.
> 
> Thanks
> -min
> 
> On 2/15/13 2:58 AM, "Rohit Yadav"  wrote:
> 
> >Edison, you'd created a 4.1-new-db-schema sql, may I merge
> >4.1-new-db-schema.sql  to db/db/schema-40to410.sql? We'll also need a
> >db/db/schema-40to410-cleanup.sql and upgrading class.
> >
> >There is some difference between the 4.0 create-schema.sql and that in
> >4.1: http://people.apache.org/~bhaisaab/diff-create-schema-40-41.sql
> >
> >Alex suggested in last discussion that we should not change the schema
> >file and have upgrade paths and cleanup paths. This would help us do
> >rolling upgrades. But Alex, there are a lot of difference between the
> >4.0 schema and 4.1 schema sqls (about 4k lines of diff):
> >http://people.apache.org/~bhaisaab/diff4041sqls.sql If we don't want
> >developers to change anything in the schema files, how do you propose
> >we fix it now for 4.1? Move all these changes to 40to41 sql?
> >
> >Sheng (ipv6), Kishan (regions), Vijay (autoscale) I see some create
> >schema changes, should we move them to db/db/schema-40to410.sql?
> >
> >Min, the create-schema-view did not exist for 4.0, should we keep it as
> >it as, our move it as upgrade path?
> >
> >For 4.1, we should do following changes so DatabaseCreator could be
> >refactored and used starting 4.2/master:
> >- Change version to 4.0 in create-schema
> >- Make sure there is difference between 4.0 and 4.1 create-schema sqls
> >- Move new additions to db/db/schema-40to410.sql, define a cleanup
> >path/sql and upgrading class from 40-41
> >- Fix cloudstack-setup-databases, for 4.1 we won't use databasecreator,
> >stick with the present script (won't risk regressions and whatnot)
> >
> >Regards.

Re: createStoragePool API Question

[Jessica Tomechak]

If so, please file a bug with Component set to Doc. Thanks!

Jessica T

On Thu, Feb 14, 2013 at 9:15 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> OK, thanks, Alex
>
> Then the docs here must be incorrect:
>
> *name**the name for the storage pool**true**url**the URL of the storage
> pool
> **true**zoneid**the Zone ID for the storage pool**true**clusterid**the
> cluster ID for the storage pool**false**details**the details for the
> storage pool**false**podid**the Pod ID for the storage
> pool**false**tags**the
> tags for the storage pool**false*
>
>
> On Thu, Feb 14, 2013 at 8:42 PM, Alex Huang  wrote:
>
> > According to the command itself it is required.  Look in
> > createstoragepoolcmd.java.
> >
> > --Alex
> >
> > > -Original Message-
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > Sent: Thursday, February 14, 2013 6:58 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: createStoragePool API Question
> > >
> > > Hi,
> > >
> > > I'm looking at the following API description:
> > >
> > > http://incubator.apache.org/cloudstack/docs/api/apidocs-
> > > 4.0.0/root_admin/createStoragePool.html
> > >
> > > I was wondering why clusterid was not a required parameter.  I was
> under
> > > the impression that Primary Storage (a storage pool) is always within a
> > > cluster.
> > >
> > > Can someone clarify this for me?
> > >
> > > Thanks!
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud
> > > *(tm)*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
>

Re: android cloudstack client

[Kelceydamage@bbits]

As a dual iOS/Android user I think this is a great idea. Heck, even to just 
have a nice monitoring tool/performance app would be great.

Sent from my iPhone

On Feb 15, 2013, at 7:48 PM, Abhinandan Prateek  
wrote:

> On 16/02/13 9:08 AM, "David Nalley"  wrote:
> 
>> On Fri, Feb 15, 2013 at 10:33 PM, Abhinandan Prateek
>>  wrote:
>>> Guys,
>>>  I was wondering how useful will be a android (and iOS) cloudstack
>>> client will be ? I have started to put together a android client
>>> initially to show dash board and later probably will add more
>>> functionality.
>>> Before putting in more effort, wanted to probe the community if this is
>>> something they will want to use ?
>>> 
>>> -abhi
>> 
>> I find Cumulus [1] to be pretty useful as an end-user, but less so as an
>> admin
>> 
>> [1] https://github.com/creationline/cumulus
> 
> Is there something similar for iOS platform ?
> 
> 

[jira] [Resolved] (CLOUDSTACK-1307) Noticed NPE when we put host in maintenance mode in clustered management setup

[Prachi Damle (JIRA)]

 [ 
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 in clustered management setup
> --
>
> Key: CLOUDSTACK-1307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1307
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Prachi Damle
>Assignee: Prachi Damle
> Fix For: 4.1.0
>
>
> Noticed the Nullpointer exception when we put one of the host in maintenance 
> mode
> Steps:
> 1.Configured cluster management setup with 4 management server and 4 
> hosts(make sure each host was managed by unique Ms )
> 2.create few domain and user accounts
> 3 login with that account and deploy vms based on isolated and sharednetworks
> 4.once the all the vms are up and running
> 5.select one host and put in maintenance mode
> actual result;
> Putting the one of host into maintenance mode causes the 
> java.lang.NullPointerException.
> 012-06-06 12:24:44,111 INFO [vmware.resource.VmwareResource] 
> (DirectAgent-287:10.147.29.53) Executing resource MaintainCommand: {"wait":0}
> 2012-06-06 12:24:44,277 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-287:null) Seq 8-1880293401: Response Received:
> 2012-06-06 12:24:44,277 DEBUG [agent.transport.Request] 
> (DirectAgent-287:null) Seq 8-1880293401: Processing: { Ans: , MgmtId: 
> 7551760465939, via: 8, Ver: v1, Flags: 110, 
> [{"MaintainAnswer":{"willMigrate":true,"result":true,"details":"Put host in 
> maintaince","wait":0}}] }
> 2012-06-06 12:24:44,282 DEBUG [agent.transport.Request] 
> (Job-Executor-2:job-40) Seq 8-1880293401: Received: { Ans: , MgmtId: 
> 7551760465939, via: 8, Ver: v1, Flags: 110, { MaintainAnswer } }
> 2012-06-06 12:24:44,282 DEBUG [agent.manager.AgentManagerImpl] 
> (Job-Executor-2:job-40) Details from executing class 
> com.cloud.agent.api.MaintainCommand: Put host in maintaince
> 2012-06-06 12:24:44,283 DEBUG [agent.manager.AgentAttache] 
> (DirectAgent-287:null) Seq 8-1880293401: No more commands found
> 2012-06-06 12:24:44,616 DEBUG [cloud.resource.ResourceState] 
> (Job-Executor-2:job-40) Resource state update: [id = 8; name = 10.147.29.53; 
> old state = Enabled; event = AdminAskMaintenace; new state = 
> PrepareForMaintenance]
> 2012-06-06 12:24:44,703 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-104:null) Ping from 8
> 2012-06-06 12:24:44,751 DEBUG [agent.manager.AgentAttache] 
> (Job-Executor-2:job-40) Seq 8-1880293377: Sending disconnect to class 
> com.cloud.network.security.SecurityGroupListener
> 2012-06-06 12:24:45,576 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-481:null) Ping from 9
> 2012-06-06 12:24:45,844 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-32:null) Seq 3-412680218: Response Received:
> 2012-06-06 12:24:45,844 DEBUG [agent.transport.Request] 
> (StatsCollector-2:null) Seq 3-412680218: Received: { Ans: , MgmtId: 
> 7551760465939, via: 3, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
> 2012-06-06 12:24:45,848 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-15:null) Seq 3-1803485203: Response Received:
> 2012-06-06 12:24:45,848 DEBUG [agent.manager.ClusteredAgentManagerImpl] 
> (DirectAgent-15:null) Seq 3-1803485203: MgmtId 6835037798417: Resp: Routing 
> to peer
> 2012-06-06 12:24:46,009 DEBUG [agent.manager.ClusteredAgentAttache] 
> (StatsCollector-2:null) Seq 7-1926104508: Forwarding null to 7487134629906
> 2012-06-06 12:24:46,275 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-0:work-4) Processing HAWork[4-Migration-4-Running-Scheduled]
> 2012-06-06 12:24:46,279 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-4:work-5) Processing HAWork[5-Migration-6-Running-Scheduled]
> 2012-06-06 12:24:46,330 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-2:work-6) Processing HAWork[6-Migration-10-Running-Scheduled]
> 2012-06-06 12:24:46,356 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-1:work-7) Processing HAWork[7-Migration-13-Running-Scheduled]
> 2012-06-06 12:24:46,616 DEBUG [cloud.resource.ResourceManagerImpl] 
> (Job-Executor-2:job-40) Sent resource event EVENT_PREPARE_MAINTENANCE_AFTER 
> to listener CapacityManagerImpl$$EnhancerByCGLIB$$e9d6b2bf
> 2012-06-06 12:24:47,155 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-2:job-40) Complete async job-40, jobStatus: 1, resultCode: 0, 
> result: com.cloud.api.response.HostResponse@3133134e
> 2012-06-06 12:24:51,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-2:job-40) Done executing 
> com.cloud.api.commands.PrepareForMaintenanceCmd for job-40
> 2012-06-0

[jira] [Commented] (CLOUDSTACK-1307) Noticed NPE when we put host in maintenance mode in clustered management setup

[Prachi Damle (JIRA)]

[ 
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:
   - Use of class variable of type GenericSearchBuilder causes issues when 
multiple threads invoke this method to findCapacity
   - Changing the scope of the variable to be local to these methods.

Master:
Commit hash:a621048869fcfaf73e8a0cab75e83e86b7e5e589

Also merged to 4.1



> 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
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Prachi Damle
>Assignee: Prachi Damle
> Fix For: 4.1.0
>
>
> Noticed the Nullpointer exception when we put one of the host in maintenance 
> mode
> Steps:
> 1.Configured cluster management setup with 4 management server and 4 
> hosts(make sure each host was managed by unique Ms )
> 2.create few domain and user accounts
> 3 login with that account and deploy vms based on isolated and sharednetworks
> 4.once the all the vms are up and running
> 5.select one host and put in maintenance mode
> actual result;
> Putting the one of host into maintenance mode causes the 
> java.lang.NullPointerException.
> 012-06-06 12:24:44,111 INFO [vmware.resource.VmwareResource] 
> (DirectAgent-287:10.147.29.53) Executing resource MaintainCommand: {"wait":0}
> 2012-06-06 12:24:44,277 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-287:null) Seq 8-1880293401: Response Received:
> 2012-06-06 12:24:44,277 DEBUG [agent.transport.Request] 
> (DirectAgent-287:null) Seq 8-1880293401: Processing: { Ans: , MgmtId: 
> 7551760465939, via: 8, Ver: v1, Flags: 110, 
> [{"MaintainAnswer":{"willMigrate":true,"result":true,"details":"Put host in 
> maintaince","wait":0}}] }
> 2012-06-06 12:24:44,282 DEBUG [agent.transport.Request] 
> (Job-Executor-2:job-40) Seq 8-1880293401: Received: { Ans: , MgmtId: 
> 7551760465939, via: 8, Ver: v1, Flags: 110, { MaintainAnswer } }
> 2012-06-06 12:24:44,282 DEBUG [agent.manager.AgentManagerImpl] 
> (Job-Executor-2:job-40) Details from executing class 
> com.cloud.agent.api.MaintainCommand: Put host in maintaince
> 2012-06-06 12:24:44,283 DEBUG [agent.manager.AgentAttache] 
> (DirectAgent-287:null) Seq 8-1880293401: No more commands found
> 2012-06-06 12:24:44,616 DEBUG [cloud.resource.ResourceState] 
> (Job-Executor-2:job-40) Resource state update: [id = 8; name = 10.147.29.53; 
> old state = Enabled; event = AdminAskMaintenace; new state = 
> PrepareForMaintenance]
> 2012-06-06 12:24:44,703 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-104:null) Ping from 8
> 2012-06-06 12:24:44,751 DEBUG [agent.manager.AgentAttache] 
> (Job-Executor-2:job-40) Seq 8-1880293377: Sending disconnect to class 
> com.cloud.network.security.SecurityGroupListener
> 2012-06-06 12:24:45,576 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-481:null) Ping from 9
> 2012-06-06 12:24:45,844 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-32:null) Seq 3-412680218: Response Received:
> 2012-06-06 12:24:45,844 DEBUG [agent.transport.Request] 
> (StatsCollector-2:null) Seq 3-412680218: Received: { Ans: , MgmtId: 
> 7551760465939, via: 3, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
> 2012-06-06 12:24:45,848 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-15:null) Seq 3-1803485203: Response Received:
> 2012-06-06 12:24:45,848 DEBUG [agent.manager.ClusteredAgentManagerImpl] 
> (DirectAgent-15:null) Seq 3-1803485203: MgmtId 6835037798417: Resp: Routing 
> to peer
> 2012-06-06 12:24:46,009 DEBUG [agent.manager.ClusteredAgentAttache] 
> (StatsCollector-2:null) Seq 7-1926104508: Forwarding null to 7487134629906
> 2012-06-06 12:24:46,275 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-0:work-4) Processing HAWork[4-Migration-4-Running-Scheduled]
> 2012-06-06 12:24:46,279 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-4:work-5) Processing HAWork[5-Migration-6-Running-Scheduled]
> 2012-06-06 12:24:46,330 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-2:work-6) Processing HAWork[6-Migration-10-Running-Scheduled]
> 2012-06-06 12:24:46,356 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-1:work-7) Processing HAWork[7-Migration-13-Running-Scheduled]
> 2012-06-06 12:24:46,616 DEBUG [cloud.resource.ResourceManagerImpl] 
> (Job-Executor-2:job-40) Sent resource event EVENT_PREPARE_MAINTENANCE_AFTER 
> to listener CapacityManagerImpl$$EnhancerByCGLIB$$e9d6b2bf
> 2012-06-06 12:24:47,155 DEBUG [

[jira] [Commented] (CLOUDSTACK-1307) Noticed NPE when we put host in maintenance mode in clustered management setup

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579706#comment-13579706
 ] 

ASF subversion and git services commented on CLOUDSTACK-1307:
-

Commit a621048869fcfaf73e8a0cab75e83e86b7e5e589 in branch refs/heads/master 
from Prachi Damle 
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=a621048 ]

CLOUDSTACK-1307 Noticed NPE when we put host in maintenance mode in clustered 
management setup

Changes:
   - Use of class variable of type GenericSearchBuilder causes issues when 
multiple threads invoke this method to findCapacity
   - Changing the scope of the variable to be local to these methods.


> 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
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Prachi Damle
>Assignee: Prachi Damle
> Fix For: 4.1.0
>
>
> Noticed the Nullpointer exception when we put one of the host in maintenance 
> mode
> Steps:
> 1.Configured cluster management setup with 4 management server and 4 
> hosts(make sure each host was managed by unique Ms )
> 2.create few domain and user accounts
> 3 login with that account and deploy vms based on isolated and sharednetworks
> 4.once the all the vms are up and running
> 5.select one host and put in maintenance mode
> actual result;
> Putting the one of host into maintenance mode causes the 
> java.lang.NullPointerException.
> 012-06-06 12:24:44,111 INFO [vmware.resource.VmwareResource] 
> (DirectAgent-287:10.147.29.53) Executing resource MaintainCommand: {"wait":0}
> 2012-06-06 12:24:44,277 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-287:null) Seq 8-1880293401: Response Received:
> 2012-06-06 12:24:44,277 DEBUG [agent.transport.Request] 
> (DirectAgent-287:null) Seq 8-1880293401: Processing: { Ans: , MgmtId: 
> 7551760465939, via: 8, Ver: v1, Flags: 110, 
> [{"MaintainAnswer":{"willMigrate":true,"result":true,"details":"Put host in 
> maintaince","wait":0}}] }
> 2012-06-06 12:24:44,282 DEBUG [agent.transport.Request] 
> (Job-Executor-2:job-40) Seq 8-1880293401: Received: { Ans: , MgmtId: 
> 7551760465939, via: 8, Ver: v1, Flags: 110, { MaintainAnswer } }
> 2012-06-06 12:24:44,282 DEBUG [agent.manager.AgentManagerImpl] 
> (Job-Executor-2:job-40) Details from executing class 
> com.cloud.agent.api.MaintainCommand: Put host in maintaince
> 2012-06-06 12:24:44,283 DEBUG [agent.manager.AgentAttache] 
> (DirectAgent-287:null) Seq 8-1880293401: No more commands found
> 2012-06-06 12:24:44,616 DEBUG [cloud.resource.ResourceState] 
> (Job-Executor-2:job-40) Resource state update: [id = 8; name = 10.147.29.53; 
> old state = Enabled; event = AdminAskMaintenace; new state = 
> PrepareForMaintenance]
> 2012-06-06 12:24:44,703 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-104:null) Ping from 8
> 2012-06-06 12:24:44,751 DEBUG [agent.manager.AgentAttache] 
> (Job-Executor-2:job-40) Seq 8-1880293377: Sending disconnect to class 
> com.cloud.network.security.SecurityGroupListener
> 2012-06-06 12:24:45,576 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-481:null) Ping from 9
> 2012-06-06 12:24:45,844 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-32:null) Seq 3-412680218: Response Received:
> 2012-06-06 12:24:45,844 DEBUG [agent.transport.Request] 
> (StatsCollector-2:null) Seq 3-412680218: Received: { Ans: , MgmtId: 
> 7551760465939, via: 3, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
> 2012-06-06 12:24:45,848 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-15:null) Seq 3-1803485203: Response Received:
> 2012-06-06 12:24:45,848 DEBUG [agent.manager.ClusteredAgentManagerImpl] 
> (DirectAgent-15:null) Seq 3-1803485203: MgmtId 6835037798417: Resp: Routing 
> to peer
> 2012-06-06 12:24:46,009 DEBUG [agent.manager.ClusteredAgentAttache] 
> (StatsCollector-2:null) Seq 7-1926104508: Forwarding null to 7487134629906
> 2012-06-06 12:24:46,275 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-0:work-4) Processing HAWork[4-Migration-4-Running-Scheduled]
> 2012-06-06 12:24:46,279 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-4:work-5) Processing HAWork[5-Migration-6-Running-Scheduled]
> 2012-06-06 12:24:46,330 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-2:work-6) Processing HAWork[6-Migration-10-Running-Scheduled]
> 2012-06-06 12:24:46,356 INFO [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-1:work-7) Processing HAWork[7-Migration-13-Running-Scheduled]
> 2012-06-06 12:24:46,616 

Re: android cloudstack client

[Abhinandan Prateek]

On 16/02/13 9:08 AM, "David Nalley"  wrote:

>On Fri, Feb 15, 2013 at 10:33 PM, Abhinandan Prateek
> wrote:
>> Guys,
>>   I was wondering how useful will be a android (and iOS) cloudstack
>>client will be ? I have started to put together a android client
>>initially to show dash board and later probably will add more
>>functionality.
>> Before putting in more effort, wanted to probe the community if this is
>>something they will want to use ?
>>
>> -abhi
>
>I find Cumulus [1] to be pretty useful as an end-user, but less so as an
>admin
>
>[1] https://github.com/creationline/cumulus

Is there something similar for iOS platform ?

Re: android cloudstack client

[David Nalley]

On Fri, Feb 15, 2013 at 10:33 PM, Abhinandan Prateek
 wrote:
> Guys,
>   I was wondering how useful will be a android (and iOS) cloudstack client 
> will be ? I have started to put together a android client initially to show 
> dash board and later probably will add more functionality.
> Before putting in more effort, wanted to probe the community if this is 
> something they will want to use ?
>
> -abhi

I find Cumulus [1] to be pretty useful as an end-user, but less so as an admin

[1] https://github.com/creationline/cumulus

[jira] [Created] (CLOUDSTACK-1308) Document guest configuration to utilize IPv6

[David Nalley (JIRA)]

David Nalley created CLOUDSTACK-1308:


 Summary: Document guest configuration to utilize IPv6
 Key: CLOUDSTACK-1308
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1308
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Reporter: David Nalley


See CLOUDSTACK-1095 for details on configuration. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

android cloudstack client

[Abhinandan Prateek]

Guys,
  I was wondering how useful will be a android (and iOS) cloudstack client will 
be ? I have started to put together a android client initially to show dash 
board and later probably will add more functionality.
Before putting in more effort, wanted to probe the community if this is 
something they will want to use ?

-abhi

Re: [ACS4.2] LDAP UI

[Abhinandan Prateek]

Pranav,
  I was wondering we have API to get configuration, can't we reuse the
same to get ldap config ?

-abhi




On 15/02/13 7:36 PM, "Pranav Saxena"  wrote:

>Abhi ,
>
>Just wanted to check with you if we have a list LDAP configuration API
>call in CS ? Because I would need this to list the current LDAP
>configuration on the UI  , if it exists .
>
>Regards,
>Pranav
>
>-Original Message-
>From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>Sent: Thursday, February 14, 2013 12:27 PM
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [ACS4.2] LDAP UI
>
>
>On 14/02/13 11:30 AM, "David Nalley"  wrote:
>
>>On Thu, Feb 14, 2013 at 12:51 AM, Pranav Saxena
>> wrote:
>>> To configure LDAP  , we need to pass in few multiple mandatory
>>>parameters -
>>>
>>> hostnameHostname or ip address of the ldap server eg:
>>>my.ldap.com
>>> queryfilter You specify a query filter here, which narrows down the
>>>users, who can be part of this domain.
>>> searchbase  The search base defines the starting point for the
>>>search in the directory tree
>>>
>>> If you are referring to Global settings , that can be done but then
>>>we'll have to have three Ldap config parameters there . if that is a
>>>good design to handle this , then yes we can do that. Perhaps , the
>>>idea is to have a single dialog box where a user could supply three
>>>values and configure and debug them if something goes wrong.
>>
>>
>>Those are the mandatory API inputs for CloudStack.
>>But almost all environments will require username/password for binding
>>at a minimum, and you should probably, and prolly offer the SSL option
>>as well. Port should probably be an option too.
>>
>>Without at least bind creds, the API configuration is practically
>>useless on any modern LDAP server.
>>
>>--David
>
>The admin guide documents the LDAP API. SSL is supported.
>http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0-
>i
>ncubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Admin_Guide-e
>n
>-US.pdf
>
>Look for LDAP configuration. In short you have following config params:
>
>hostname
>searchbase
>queryfilter
>binddn
>bindpass
>port
>ssl
>truststore
>truststorepass
>response
>
>
>
>-abhi
>
>
>
>>
>

Re: Review Request: Scripts for Selenium UI automation.

[David Nalley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9336/#review16677
---


Parth: 

So diff version 2 looks like a diff that's assuming v1 is already applied. 

Can you update this so that it's a single patch that can be applied? 

--David

- David Nalley


On Feb. 15, 2013, 11:43 p.m., Parth Jagirdar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/9336/
> ---
> 
> (Updated Feb. 15, 2013, 11:43 p.m.)
> 
> 
> Review request for cloudstack, John Kinsella, Prasanna Santhanam, and Kelcey 
> Jamison-Damage.
> 
> 
> Description
> ---
> 
> These scripts will execute following test cases on UI through Firefox. (Test 
> Cases taken from :: http://wiki.cloudstack.org/display/QA/Manual+BVT)
> 
> 
> Login Admin user to UI.
> Create an Account name Test.
> Logout Admin user.
> Login Test user.
> 
> Add a new Disk Offering.
> Edit this Disk offering.
> Delete this Disk offering.
> 
> Add a new Compute Offering.
> Edit this Compute offering.
> Delete this Compute offering.
> 
> Logout Test user.
> Login Admin user.
> Delete Test user Account. And tear down the Browser instance.
> 
> # End of Tests
> 
> Thanks,
> ...Parth
> 
> 
> This addresses bug CLOUDSTACK-1180.
> 
> 
> Diffs
> -
> 
>   test/selenium/lib/Global_Locators.py PRE-CREATION 
>   test/selenium/lib/initialize.py PRE-CREATION 
>   test/selenium/smoke/Login_and_Accounts.py PRE-CREATION 
>   test/selenium/smoke/Service_Offering.py PRE-CREATION 
>   test/selenium/smoke/TemplatesAndISO.py PRE-CREATION 
>   test/selenium/smoke/VM_lifeCycle.py PRE-CREATION 
>   test/selenium/smoke/main.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/9336/diff/
> 
> 
> Testing
> ---
> 
> Tested with network refactor branch.
> 
> 
> Thanks,
> 
> Parth Jagirdar
> 
>

[jira] [Commented] (CLOUDSTACK-1302) Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM hypervisor

[edison su (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579679#comment-13579679
 ] 

edison su commented on CLOUDSTACK-1302:
---

Seems vmware has API to configure cache policy, not sure about xenserver.

> Add per storage setting for cache="none/writeback/writethrough" options for 
> VMs on KVM hypervisor
> -
>
> Key: CLOUDSTACK-1302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.0.0
> Environment: Ubuntu 12.04.2 Host, KVM hypervisor
>Reporter: Jason Villalta
>Priority: Minor
>
> Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual 
> machines deployed.  This causes conflict with filesystems mounted with fuse 
> such as ZFS, GlusterFs and CEPH as fuse does not support directio with these 
> file systems.  When starting VMs libvirt throws an error "could not open disk 
> image  Invalid argument"
> Changing the cache= setting to writethough or writeback solves this problem 
> but there currently is no way to set this.  Ideally this would get set on a 
> per datastore basis.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1307) Noticed NPE when we put host in maintenance mode in clustered management setup

[Prachi Damle (JIRA)]

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
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Reporter: Prachi Damle
Assignee: Prachi Damle
 Fix For: 4.1.0


Noticed the Nullpointer exception when we put one of the host in maintenance 
mode

Steps:
1.Configured cluster management setup with 4 management server and 4 hosts(make 
sure each host was managed by unique Ms )
2.create few domain and user accounts
3 login with that account and deploy vms based on isolated and sharednetworks
4.once the all the vms are up and running
5.select one host and put in maintenance mode

actual result;
Putting the one of host into maintenance mode causes the 
java.lang.NullPointerException.


012-06-06 12:24:44,111 INFO [vmware.resource.VmwareResource] 
(DirectAgent-287:10.147.29.53) Executing resource MaintainCommand: {"wait":0}
2012-06-06 12:24:44,277 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-287:null) Seq 8-1880293401: Response Received:
2012-06-06 12:24:44,277 DEBUG [agent.transport.Request] (DirectAgent-287:null) 
Seq 8-1880293401: Processing: { Ans: , MgmtId: 7551760465939, via: 8, Ver: v1, 
Flags: 110, [{"MaintainAnswer":{"willMigrate":true,"result":true,"details":"Put 
host in maintaince","wait":0}}] }
2012-06-06 12:24:44,282 DEBUG [agent.transport.Request] (Job-Executor-2:job-40) 
Seq 8-1880293401: Received: { Ans: , MgmtId: 7551760465939, via: 8, Ver: v1, 
Flags: 110, { MaintainAnswer } }
2012-06-06 12:24:44,282 DEBUG [agent.manager.AgentManagerImpl] 
(Job-Executor-2:job-40) Details from executing class 
com.cloud.agent.api.MaintainCommand: Put host in maintaince
2012-06-06 12:24:44,283 DEBUG [agent.manager.AgentAttache] 
(DirectAgent-287:null) Seq 8-1880293401: No more commands found
2012-06-06 12:24:44,616 DEBUG [cloud.resource.ResourceState] 
(Job-Executor-2:job-40) Resource state update: [id = 8; name = 10.147.29.53; 
old state = Enabled; event = AdminAskMaintenace; new state = 
PrepareForMaintenance]
2012-06-06 12:24:44,703 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-104:null) Ping from 8
2012-06-06 12:24:44,751 DEBUG [agent.manager.AgentAttache] 
(Job-Executor-2:job-40) Seq 8-1880293377: Sending disconnect to class 
com.cloud.network.security.SecurityGroupListener
2012-06-06 12:24:45,576 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-481:null) Ping from 9
2012-06-06 12:24:45,844 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-32:null) Seq 3-412680218: Response Received:
2012-06-06 12:24:45,844 DEBUG [agent.transport.Request] (StatsCollector-2:null) 
Seq 3-412680218: Received: { Ans: , MgmtId: 7551760465939, via: 3, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2012-06-06 12:24:45,848 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-15:null) Seq 3-1803485203: Response Received:
2012-06-06 12:24:45,848 DEBUG [agent.manager.ClusteredAgentManagerImpl] 
(DirectAgent-15:null) Seq 3-1803485203: MgmtId 6835037798417: Resp: Routing to 
peer
2012-06-06 12:24:46,009 DEBUG [agent.manager.ClusteredAgentAttache] 
(StatsCollector-2:null) Seq 7-1926104508: Forwarding null to 7487134629906
2012-06-06 12:24:46,275 INFO [cloud.ha.HighAvailabilityManagerImpl] 
(HA-Worker-0:work-4) Processing HAWork[4-Migration-4-Running-Scheduled]
2012-06-06 12:24:46,279 INFO [cloud.ha.HighAvailabilityManagerImpl] 
(HA-Worker-4:work-5) Processing HAWork[5-Migration-6-Running-Scheduled]
2012-06-06 12:24:46,330 INFO [cloud.ha.HighAvailabilityManagerImpl] 
(HA-Worker-2:work-6) Processing HAWork[6-Migration-10-Running-Scheduled]
2012-06-06 12:24:46,356 INFO [cloud.ha.HighAvailabilityManagerImpl] 
(HA-Worker-1:work-7) Processing HAWork[7-Migration-13-Running-Scheduled]
2012-06-06 12:24:46,616 DEBUG [cloud.resource.ResourceManagerImpl] 
(Job-Executor-2:job-40) Sent resource event EVENT_PREPARE_MAINTENANCE_AFTER to 
listener CapacityManagerImpl$$EnhancerByCGLIB$$e9d6b2bf
2012-06-06 12:24:47,155 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-2:job-40) Complete async job-40, jobStatus: 1, resultCode: 0, 
result: com.cloud.api.response.HostResponse@3133134e
2012-06-06 12:24:51,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-2:job-40) Done executing 
com.cloud.api.commands.PrepareForMaintenanceCmd for job-40
2012-06-06 12:24:51,717 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-12:null) Async job-40 completed
2012-06-06 12:24:53,110 DEBUG [cloud.deploy.FirstFitPlanner] 
(HA-Worker-1:work-7) DeploymentPlanner allocation algorithm: random
2012-06-06 12:24:53,110 DEBUG [cloud.deploy.FirstFitPlanner] 
(HA-Worker-4:work-5) DeploymentPlanner allocation algorithm: random
2012-06-0

[jira] [Closed] (CLOUDSTACK-1095) Ipv6 - dhclient command needs to be run manually on the Vms to get the Ipv6 address.

[Sangeetha Hariharan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangeetha Hariharan closed CLOUDSTACK-1095.
---


Had the following settings in the guest OS:

cat /etc/dhcp/dhclient.conf
send dhcp6.client-id = concat(00:03:00, hardware);

cat /etc/network/interfaces:

iface eth0 inet6 dhcp
autoconf 0
accept_ra 1

Added the following to /etc/sysctl.conf
net.ipv6.conf.all.autoconf = 0
net.ipv6.conf.default.autoconf = 0
net.ipv6.conf.eth0.autoconf = 0
net.ipv6.conf.lo.autoconf = 1



Once all the above setting are done , Unbuntu 1210 client is able to get an 
Ipv6 address automatically on start.


> Ipv6 - dhclient command needs to be run manually on the Vms to get the Ipv6 
> address. 
> -
>
> Key: CLOUDSTACK-1095
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1095
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Build from Ipv6 branch
>Reporter: Sangeetha Hariharan
>Assignee: Sheng Yang
> Fix For: 4.1.0
>
>
> Ipv6 - dhclient command needs to be run manually on the Vms to get the Ipv6 
> address. 
> Steps to reproduce the problem:
> Set up - Advanced Zone.
> Create a shared network using Ipv6 parameters.
> Deploy Vm in this network.
> Once the Vm is deployed successfully , notice that ipv6 address is not 
> assigned to it.
> ifconfig command does not show an ipaddress assigned to it.
> dhclient command needs to be run manually on the Vms to get the Ipv6 address. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-1107) Ipv6 - Unable to extend Ip range for a Ipv6 network using craeteVlanIpRange() command - Error code 530 returned.

[Sangeetha Hariharan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangeetha Hariharan closed CLOUDSTACK-1107.
---


Tested with the latest build from networkrefactor branch.

We are able to extend the Ipv6range for a dual stack network successfully.

2013-02-15 23:44:49,112 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
(userId=2 accountId=2 sessionId=EB778CE8F713E20685D038B997411346) 10.217.252.59 
-- GET 
command=createVlanIpRange&forVirtualNetwork=false&networkid=23fb0f34-414d-45b3-b6bc-ca78915907b6&startipv6=fc00:3:1370::11&endipv6=fc00:3:1370::20&sessionkey=4dk3bXhsicZfitb1HLGRzOjAIjE%3D
 200 6e756f9a-bbd9-40db-b38d-a19e901bd923falsefa60468a-c5d1-42a2-92e8-23cc5a62b9351370systemf4af033d-c767-447f-9a30-ad1174ca5e24ROOT23fb0f34-414d-45b3-b6bc-ca78915907b6c2b915f9-abaa-4139-8e1f-79639cd4bbfefc00:3:1370::11fc00:3:1370::20fc00:3:1370::1fc00:3:1370::1/64



mysql> select * from vlan;
++--+-++-++---+---+-++++-+
| id | uuid | vlan_id | vlan_gateway   | 
vlan_netmask| ip6_gateway| ip6_cidr  | description  
 | ip6_range   | vlan_type  | 
data_center_id | network_id | physical_network_id |
++--+-++-++---+---+-++++-+
|  1 | a6efa79f-781d-4b2d-92ac-1a9dd2b7771e | 1363| 10.223.136.193 | 
255.255.255.192 | NULL   | NULL  | 
10.223.136.194-10.223.136.210 | NULL
| VirtualNetwork |  1 |200 | 200 |
|  8 | 5489a544-9cca-4103-8d23-ae44641feefe | 1370| 10.223.137.1   | 
255.255.255.224 | fc00:3:1370::1 | fc00:3:1370::1/64 | 
10.223.137.2-10.223.137.10| fc00:3:1370::2-fc00:3:1370::10  
| DirectAttached |  1 |210 | 200 |
|  9 | 6e756f9a-bbd9-40db-b38d-a19e901bd923 | 1370| NULL   | NULL   
 | fc00:3:1370::1 | fc00:3:1370::1/64 | NULL  | 
fc00:3:1370::11-fc00:3:1370::20 | DirectAttached |  
1 |210 | 200 |
| 10 | ee8c39a0-272a-4d9f-b05d-2f92c9a64dba | 1373| 10.223.137.193 | 
255.255.255.192 | NULL   | NULL  | 
10.223.137.194-10.223.137.200 | NULL
| DirectAttached |  1 |211 | 200 |
| 11 | efe03274-599c-4113-bd1c-9d6661bf1287 | 1371| NULL   | NULL   
 | fc00:3:1371::1 | fc00:3:1371::1/64 | NULL  | 
fc00:3:1371::2-fc00:3:1371::::: | DirectAttached |  
1 |212 | 200 |
++--+-++-++---+---+-++++-+





> Ipv6 - Unable to extend Ip range for a Ipv6 network using craeteVlanIpRange() 
> command - Error code 530 returned.
> 
>
> Key: CLOUDSTACK-1107
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1107
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Latest build from Network Refactoring branch
>Reporter: Sangeetha Hariharan
>Assignee: Sheng Yang
> Fix For: 4.1.0
>
>
> Ipv6 - Unable to extend Ip range for a Ipv6 network using craeteVlanIpRange() 
> command.
> Create a IPV6 network.
> Try to extend the Ip range of this network.
> This fails.
> 2013-01-31 23:38:20,972 INFO  [cloud.api.ApiServer] (catalina-exec-19:null) 
> (userId=2 accountId=2 sessionId=15E1EE3BB246B890356119483E4443A3) 
> 10.217.252.59 -- GET 
> command=createVlanIpRange&forVirtualNetwork=false&networkid=de57fad8-ed88-4728-bd32-26dfc396e4e0&startip=fc00:3:1370::11&endip=fc00:3:1370::ff&response=json&sessionkey=2lbI7S08%2BJ57eJfiehe%2FFSPSL6o%3D&_=1359675548381
>  530 null
> Following exception seen in the logs:
> 2013-01-31 23:38:20,945 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:

[jira] [Updated] (CLOUDSTACK-1306) Better Error message when trying to deploy Vm by passing static Ipv4 addresses that are assigned to another VM/IP4 address is outside the iprange.

[Sangeetha Hariharan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangeetha Hariharan updated CLOUDSTACK-1306:


Assignee: Sheng Yang

> Better Error message when trying to deploy Vm by passing static Ipv4 
> addresses that are assigned to another VM/IP4 address is outside the iprange. 
> ---
>
> Key: CLOUDSTACK-1306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Latest from Network Refactor branch,
>Reporter: Sangeetha Hariharan
>Assignee: Sheng Yang
>Priority: Minor
> Fix For: 4.1.0
>
>
> Better Error message when handling Better Error message when trying to deploy 
> Vm by passing static Ipv4 addresses that are assigned to another VM/IP4 
> address is outside the iprange.
> Steps to reproduce the problem:
> Scenario1:
> "Pre Req:
> 1.Create Dual Stack Shared Network by passing ipv6 params and ipv4 params
> Steps:
> Deploy Vm by passing a static Ipaddress that is already assigned to a 
> different VM using ipaddress and networkIds."
> Scenario2:
> Pre Req:
> 1.Create Dual Stack Shared Network by passing ipv6 params and ipv4 params
> Steps:
> Deploy Vm by passing a static Ipaddress that is not in the range of the 
> specified network using  ipaddress and networkIds
> Scenario3:
> Pre Req:
> 1.Create Dual Stack Shared Network by passing ipv6 params and ipv4 params
> Steps:
> Deploy Vm by passing a static Ipaddress that belongs to different network 
> that is other than network using  ipaddress and networkIds
> In all above cases ,user is presented with "Insufficient address capacity" as 
> the error message.
> Expected Behavior:
> User should be presented with more meaningful messages that will allow him to 
> take corrective actions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1306) Better Error message when trying to deploy Vm by passing static Ipv4 addresses that are assigned to another VM/IP4 address is outside the iprange.

[Sangeetha Hariharan (JIRA)]

Sangeetha Hariharan created CLOUDSTACK-1306:
---

 Summary: Better Error message when trying to deploy Vm by passing 
static Ipv4 addresses that are assigned to another VM/IP4 address is outside 
the iprange. 
 Key: CLOUDSTACK-1306
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1306
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.1.0
 Environment: Latest from Network Refactor branch,
Reporter: Sangeetha Hariharan
Priority: Minor
 Fix For: 4.1.0


Better Error message when handling Better Error message when trying to deploy 
Vm by passing static Ipv4 addresses that are assigned to another VM/IP4 address 
is outside the iprange.

Steps to reproduce the problem:

Scenario1:

"Pre Req:
1.Create Dual Stack Shared Network by passing ipv6 params and ipv4 params
Steps:
Deploy Vm by passing a static Ipaddress that is already assigned to a different 
VM using ipaddress and networkIds."

Scenario2:
Pre Req:
1.Create Dual Stack Shared Network by passing ipv6 params and ipv4 params
Steps:
Deploy Vm by passing a static Ipaddress that is not in the range of the 
specified network using  ipaddress and networkIds

Scenario3:
Pre Req:
1.Create Dual Stack Shared Network by passing ipv6 params and ipv4 params
Steps:
Deploy Vm by passing a static Ipaddress that belongs to different network that 
is other than network using  ipaddress and networkIds


In all above cases ,user is presented with "Insufficient address capacity" as 
the error message.

Expected Behavior:

User should be presented with more meaningful messages that will allow him to 
take corrective actions.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [DISCUSS] Graduation to a TLP?

[Mike Tutkowski]

OK, thanks, everyone

I've only been involved with CloudStack for a couple months now, so am
trying to understand process in addition to the way the system works and
how the code is structured.

Good stuff :)


On Fri, Feb 15, 2013 at 4:29 PM, Alex Huang  wrote:

> Mike,
>
> It is important to note that it is much more preferable to drive a
> consensus through discussion than to make a vote.  Vote should be something
> of a last resort to use.  Also only emails with [VOTE] is asking for a
> vote.  In emails without such tag, the +1 just means the sender liking
> something said in the email.
>
> --Alex
>
> > -Original Message-
> > From: Joe Brockmeier [mailto:j...@zonker.net]
> > Sent: Friday, February 15, 2013 12:23 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: [DISCUSS] Graduation to a TLP?
> >
> > On Fri, Feb 15, 2013, at 02:08 PM, Mike Tutkowski wrote:
> > > Can I ask what may be a silly question about voting?  :)
> >
> > That's not a silly question.
> >
> > > When these votes are put out there, who can vote?  Just committers or
> > > anyone participating in the community?
> >
> > Anyone can vote, but only some of the votes are binding. If you see a
> > vote taking place that you feel you have a stake in / an opinion on, you
> > should feel free to vote anyway.
> >
> > Why? Even if your vote isn't binding, it may be useful to understand how
> > folks in the community think about something even if their vote isn't
> > binding.
> >
> > I believe it's PPMC votes that are binding for the vote held within the
> > podling, btw. But please don't let that stop you from weighing in if you
> > wish to.
> >
> >
> > Best,
> >
> > jzb
> > --
> > Joe Brockmeier
> > j...@zonker.net
> > Twitter: @jzb
> > http://www.dissociatedpress.net/
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

RE: [ACS41] Yet another reviewboard reminder... for both committers and contributors.

[Animesh Chaturvedi]

We don't have  review board guidelines yet, I will work on it next week

> -Original Message-
> From: Kelcey Damage (BT) [mailto:kel...@backbonetechnology.com]
> Sent: Friday, February 15, 2013 5:04 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [ACS41] Yet another reviewboard reminder... for both committers
> and contributors.
> 
> Thanks, you see, I'm not a committer for code, I have very little programming
> experience other than scripts/automation.
> 
> I'm more a marketing/evangelist/teaching/support kind of guy.
> 
> So if asked to review code, I would not be a good choice. If asked to review
> policy/procedure/compliance/design/architecture(non-code), than I am your
> guy.
> 
> That brings me to a question, how does one use the review board? Is there a
> how-to/guidelines wiki article you can point me too?
> 
> Thanks
> 
> -kelcey
> 
> 
> >-Original Message-
> >From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >Sent: Friday, February 15, 2013 4:26 PM
> >To: cloudstack-dev@incubator.apache.org
> >Subject: RE: [ACS41] Yet another reviewboard reminder... for both
> >committers and contributors.
> >
> >Well the submitter of the review https://reviews.apache.org/r/9336/
> >listed you as one of the reviewers and I was calling out based on that.
> >
> >Ok so what should one do if someone lists you as a reviewer? If  you
> >cannot
> or
> >not qualified to review  you can respond saying that you cannot do that
> >review and submitter can ask another reviewer.
> >
> >I will update  the review board guidelines.
> >
> >Animesh
> >
> >
> >> -Original Message-
> >> From: Kelcey Damage (BT) [mailto:kel...@backbonetechnology.com]
> >> Sent: Friday, February 15, 2013 3:05 PM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: RE: [ACS41] Yet another reviewboard reminder... for both
> >> committers and contributors.
> >>
> >> My name got attached to 1180, and I'm not sure why. I am not what you
> >> would call capable of reviewing the submission other then from a
> >> legal/compliance perspective.
> >>
> >> Thanks
> >>
> >> -Kelcey
> >>
> >> >-Original Message-
> >> >From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >> >Sent: Friday, February 15, 2013 12:05 PM
> >> >To: cloudstack-dev@incubator.apache.org
> >> >Subject: RE: [ACS41] Yet another reviewboard reminder... for both
> >> >committers and contributors.
> >> >
> >> >Folks
> >> >
> >> >I have sent emails on over 30 issues from review board this week and
> >> >as community we responded to 2/3 rd of them which is good but can be
> >better.
> >> >We were able to knock off only a handful of them. Out of the ones
> >> >that were responded to many of them are awaiting action from
> >> >reviewers. If you were called out please respond to your reviews and
> >> >help us close pending
> >> reviews.
> >> >
> >> >We have 33 pending reviews in review board at this time
> >> >
> >> >Animesh
> >> >
> >> >
> >> >
> >> >> -Original Message-
> >> >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >> >> Sent: Monday, February 11, 2013 11:24 PM
> >> >> To: cloudstack-dev@incubator.apache.org
> >> >> Subject: RE: [ACS41] Yet another reviewboard reminder... for both
> >> >> committers and contributors.
> >> >>
> >> >> Folks
> >> >>
> >> >> I have sent a number of reminder emails for some of the review
> >> >> board items that have been pending for a while. Please attend to
> >> >> them at the earliest . We are running at 50+ items in review board.
> >> >> If you are a committer I request you knock off 1-2 reviews per
> >> >> week
> >> >>
> >> >> Animesh
> >> >>
> >> >> > -Original Message-
> >> >> > From: Chip Childers [mailto:chip.child...@sungard.com]
> >> >> > Sent: Tuesday, January 29, 2013 9:18 AM
> >> >> > To: cloudstack-dev@incubator.apache.org
> >> >> > Subject: [ACS41] Yet another reviewboard reminder... for both
> >> >> > committers and contributors.
> >> >> >
> >> >> > Hi all (and specifically people that were listed as "maintainers"
> >> >> > of certain code modules),
> >> >> >
> >> >> > We need committer help in getting the community contributions
> >> >> > currently in reviewboard (as well as some that we expect to show
> >> >> > up in the next day or so) reviewed and committed as soon as
> possible.
> >> >> >
> >> >> > If you are a "maintainer", or simply feel that you have enough
> >> >> > knowledge to get through one or more of these reviews, PLEASE
> >> >> > take some time to help clear out the board.
> >> >> >
> >> >> > Based on our agreed upon schedule, we need everything into
> >> >> > master (or
> >> >> > javelin) by EOD Thursday.
> >> >> >
> >> >> > For those of you that have code you want to be reviewed, but
> >> >> > have not yet submitted, it needs to get in ASAP.  Otherwise,
> >> >> > there's no chance that someone will have the time to review and
> >> >> > commit before we cut the
> >> >> release branch.
> >> >> >
> >> >> > -chip
> 

[jira] [Commented] (CLOUDSTACK-866) Document Limit API Queries

[Jessica Tomechak (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579658#comment-13579658
 ] 

Jessica Tomechak commented on CLOUDSTACK-866:
-

Min has added the code and Jessica W has been working on the UI in the past 
couple of days, so this looks ready to document

> Document Limit API Queries
> --
>
> Key: CLOUDSTACK-866
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-866
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Reporter: Radhika Nair
>Assignee: Jessica Tomechak
> Fix For: 4.1.0
>
>
> Document Limit API Queries

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1302) Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM hypervisor

[Marcus Sorensen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579656#comment-13579656
 ] 

Marcus Sorensen commented on CLOUDSTACK-1302:
-

Does Xen support this or would it be KVM specific for now?



> Add per storage setting for cache="none/writeback/writethrough" options for 
> VMs on KVM hypervisor
> -
>
> Key: CLOUDSTACK-1302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.0.0
> Environment: Ubuntu 12.04.2 Host, KVM hypervisor
>Reporter: Jason Villalta
>Priority: Minor
>
> Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual 
> machines deployed.  This causes conflict with filesystems mounted with fuse 
> such as ZFS, GlusterFs and CEPH as fuse does not support directio with these 
> file systems.  When starting VMs libvirt throws an error "could not open disk 
> image  Invalid argument"
> Changing the cache= setting to writethough or writeback solves this problem 
> but there currently is no way to set this.  Ideally this would get set on a 
> per datastore basis.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Commented] (CLOUDSTACK-1302) Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM hypervisor

[Marcus Sorensen]

Does Xen support this or would it be KVM specific for now?
On Feb 15, 2013 6:04 PM, "edison su (JIRA)"  wrote:

>
> [
> https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579654#comment-13579654]
>
> edison su commented on CLOUDSTACK-1302:
> ---
>
> We can add an option in disk offering: e.g. cache policy, has options like
> none/writeback/writethrough, or just safety vs performace(this is what
> vmware did:
> http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.webaccess.doc_41/managing_virtual_machines/t_customize_the_new_virtual_disk.html
> )
>
> > Add per storage setting for cache="none/writeback/writethrough" options
> for VMs on KVM hypervisor
> >
> -
> >
> > Key: CLOUDSTACK-1302
> > URL:
> https://issues.apache.org/jira/browse/CLOUDSTACK-1302
> > Project: CloudStack
> >  Issue Type: Bug
> >  Security Level: Public(Anyone can view this level - this is the
> default.)
> >  Components: Management Server
> >Affects Versions: 4.0.0
> > Environment: Ubuntu 12.04.2 Host, KVM hypervisor
> >Reporter: Jason Villalta
> >Priority: Minor
> >
> > Version 4.0.0 of Cloudstack has a hard coded value of cache=none for
> virtual machines deployed.  This causes conflict with filesystems mounted
> with fuse such as ZFS, GlusterFs and CEPH as fuse does not support directio
> with these file systems.  When starting VMs libvirt throws an error "could
> not open disk image  Invalid argument"
> > Changing the cache= setting to writethough or writeback solves this
> problem but there currently is no way to set this.  Ideally this would get
> set on a per datastore basis.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>

RE: [ACS41] Yet another reviewboard reminder... for both committers and contributors.

[Kelcey Damage (BT)]

Thanks, you see, I'm not a committer for code, I have very little
programming experience other than scripts/automation.

I'm more a marketing/evangelist/teaching/support kind of guy.

So if asked to review code, I would not be a good choice. If asked to review
policy/procedure/compliance/design/architecture(non-code), than I am your
guy.

That brings me to a question, how does one use the review board? Is there a
how-to/guidelines wiki article you can point me too?

Thanks

-kelcey


>-Original Message-
>From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>Sent: Friday, February 15, 2013 4:26 PM
>To: cloudstack-dev@incubator.apache.org
>Subject: RE: [ACS41] Yet another reviewboard reminder... for both
>committers and contributors.
>
>Well the submitter of the review https://reviews.apache.org/r/9336/ listed
>you as one of the reviewers and I was calling out based on that.
>
>Ok so what should one do if someone lists you as a reviewer? If  you cannot
or
>not qualified to review  you can respond saying that you cannot do that
>review and submitter can ask another reviewer.
>
>I will update  the review board guidelines.
>
>Animesh
>
>
>> -Original Message-
>> From: Kelcey Damage (BT) [mailto:kel...@backbonetechnology.com]
>> Sent: Friday, February 15, 2013 3:05 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: [ACS41] Yet another reviewboard reminder... for both
>> committers and contributors.
>>
>> My name got attached to 1180, and I'm not sure why. I am not what you
>> would call capable of reviewing the submission other then from a
>> legal/compliance perspective.
>>
>> Thanks
>>
>> -Kelcey
>>
>> >-Original Message-
>> >From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> >Sent: Friday, February 15, 2013 12:05 PM
>> >To: cloudstack-dev@incubator.apache.org
>> >Subject: RE: [ACS41] Yet another reviewboard reminder... for both
>> >committers and contributors.
>> >
>> >Folks
>> >
>> >I have sent emails on over 30 issues from review board this week and
>> >as community we responded to 2/3 rd of them which is good but can be
>better.
>> >We were able to knock off only a handful of them. Out of the ones
>> >that were responded to many of them are awaiting action from
>> >reviewers. If you were called out please respond to your reviews and
>> >help us close pending
>> reviews.
>> >
>> >We have 33 pending reviews in review board at this time
>> >
>> >Animesh
>> >
>> >
>> >
>> >> -Original Message-
>> >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> >> Sent: Monday, February 11, 2013 11:24 PM
>> >> To: cloudstack-dev@incubator.apache.org
>> >> Subject: RE: [ACS41] Yet another reviewboard reminder... for both
>> >> committers and contributors.
>> >>
>> >> Folks
>> >>
>> >> I have sent a number of reminder emails for some of the review
>> >> board items that have been pending for a while. Please attend to
>> >> them at the earliest . We are running at 50+ items in review board.
>> >> If you are a committer I request you knock off 1-2 reviews per week
>> >>
>> >> Animesh
>> >>
>> >> > -Original Message-
>> >> > From: Chip Childers [mailto:chip.child...@sungard.com]
>> >> > Sent: Tuesday, January 29, 2013 9:18 AM
>> >> > To: cloudstack-dev@incubator.apache.org
>> >> > Subject: [ACS41] Yet another reviewboard reminder... for both
>> >> > committers and contributors.
>> >> >
>> >> > Hi all (and specifically people that were listed as "maintainers"
>> >> > of certain code modules),
>> >> >
>> >> > We need committer help in getting the community contributions
>> >> > currently in reviewboard (as well as some that we expect to show
>> >> > up in the next day or so) reviewed and committed as soon as
possible.
>> >> >
>> >> > If you are a "maintainer", or simply feel that you have enough
>> >> > knowledge to get through one or more of these reviews, PLEASE
>> >> > take some time to help clear out the board.
>> >> >
>> >> > Based on our agreed upon schedule, we need everything into master
>> >> > (or
>> >> > javelin) by EOD Thursday.
>> >> >
>> >> > For those of you that have code you want to be reviewed, but have
>> >> > not yet submitted, it needs to get in ASAP.  Otherwise, there's
>> >> > no chance that someone will have the time to review and commit
>> >> > before we cut the
>> >> release branch.
>> >> >
>> >> > -chip

[jira] [Updated] (CLOUDSTACK-893) Document GSLB (Global Server Load Balancing) capability for ELB service feature

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak updated CLOUDSTACK-893:


Fix Version/s: (was: 4.1.0)
   4.2.0

Moving to 4.2 to match parent issue.

> Document GSLB (Global Server Load Balancing) capability for ELB service 
> feature
> ---
>
> Key: CLOUDSTACK-893
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-893
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Chip Childers
> Fix For: 4.2.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1302) Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM hypervisor

[edison su (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579654#comment-13579654
 ] 

edison su commented on CLOUDSTACK-1302:
---

We can add an option in disk offering: e.g. cache policy, has options like 
none/writeback/writethrough, or just safety vs performace(this is what vmware 
did: 
http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.webaccess.doc_41/managing_virtual_machines/t_customize_the_new_virtual_disk.html)

> Add per storage setting for cache="none/writeback/writethrough" options for 
> VMs on KVM hypervisor
> -
>
> Key: CLOUDSTACK-1302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.0.0
> Environment: Ubuntu 12.04.2 Host, KVM hypervisor
>Reporter: Jason Villalta
>Priority: Minor
>
> Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual 
> machines deployed.  This causes conflict with filesystems mounted with fuse 
> such as ZFS, GlusterFs and CEPH as fuse does not support directio with these 
> file systems.  When starting VMs libvirt throws an error "could not open disk 
> image  Invalid argument"
> Changing the cache= setting to writethough or writeback solves this problem 
> but there currently is no way to set this.  Ideally this would get set on a 
> per datastore basis.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-897) Document framework for CloudStack to orchestrate virtual network appliances to provide network services

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak updated CLOUDSTACK-897:


Fix Version/s: (was: 4.1.0)
   Future

> Document framework for CloudStack to orchestrate virtual network appliances 
> to provide network services 
> 
>
> Key: CLOUDSTACK-897
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-897
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Chip Childers
> Fix For: Future
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1305) Document Load Balancing using External Provider for Shared Networks

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak reassigned CLOUDSTACK-1305:


Assignee: Radhika Nair  (was: Jessica Tomechak)

> Document Load Balancing using External Provider for Shared Networks
> ---
>
> Key: CLOUDSTACK-1305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1305
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Jessica Tomechak
>Assignee: Radhika Nair
> Fix For: 4.2.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1305) Document Load Balancing using External Provider for Shared Networks

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak reassigned CLOUDSTACK-1305:


Assignee: Jessica Tomechak

> Document Load Balancing using External Provider for Shared Networks
> ---
>
> Key: CLOUDSTACK-1305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1305
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Jessica Tomechak
>Assignee: Jessica Tomechak
> Fix For: 4.2.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1305) Document Load Balancing using External Provider for Shared Networks

[Jessica Tomechak (JIRA)]

Jessica Tomechak created CLOUDSTACK-1305:


 Summary: Document Load Balancing using External Provider for 
Shared Networks
 Key: CLOUDSTACK-1305
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1305
 Project: CloudStack
  Issue Type: Task
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Reporter: Jessica Tomechak
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1305) Document Load Balancing using External Provider for Shared Networks

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak updated CLOUDSTACK-1305:
-

Issue Type: Sub-task  (was: Task)
Parent: CLOUDSTACK-700

> Document Load Balancing using External Provider for Shared Networks
> ---
>
> Key: CLOUDSTACK-1305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1305
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Jessica Tomechak
> Fix For: 4.2.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [DOC] Is the Working with Volumes section missing from docs on purpose?

[Jessica Tomechak]

Marcus, you are referring to task CLOUDSTACK-887. I have added a comment to
that bug and assigned it to myself. There is an old Resizing Volumes
section, which documents a workaround for the fact that CS had no such
feature (see docs/resizing-volumes.xml). But we need to update that.

Jessica T

On Fri, Feb 15, 2013 at 4:15 PM, Marcus Sorensen wrote:

> That is interesting. Has anyone written the resizing volumes section? I saw
> a task for it but nobody assigned.
> On Feb 15, 2013 5:12 PM, "Jessica Tomechak" 
> wrote:
>
> > This question on -users prompted me to look for our "Resizing Volumes"
> > section. I discovered that it is missing, along with the entire "Working
> > with Volumes" section. All the files are in the repo's docs directory
> > already, so I think it's just an oversight.
> >
> > Before I file a bug and add this info back in, I wonder whether anyone
> > remembers deciding on purpose to leave this info out? Or has someone
> > perhaps rewritten this and put it in another part of the docs?
> >
> > The missing section covers:
> >
> > What is a volume
> > Uploading an existing volume to a VM
> > Attaching a volume to a VM
> > Detaching a volume from one VM and attaching it to a different one
> > Moving volumes from one storage pool to another
> > Resizing volumes (using VHD)
> > How deleting a volume affects snapshots (it doesn't)
> > How to configure garbage collection of deleted volumes
> >
> > Jessica T.
> >
> >
> > -Original Message-
> > > From: Clayton Weise [mailto:cwe...@iswest.net]
> > > Sent: Friday, February 15, 2013 1:33 PM
> > > To: cloudstack-us...@incubator.apache.org
> > > Subject: RE: customising the ROOT disk
> > >
> > > Not that I'm recommending or endorsing this method but we have done it
> in
> > > the past.  Stop the instance, resize the root volume on your hypervisor
> > > directly (this process varies based on the hypervisor and storage
> method
> > > used), adjust the size to match in the CloudStack database
> (specifically
> > in
> > > the volumes table), and start the instance.
> > >
> > > -Original Message-
> > > From: Mathias Mullins [mailto:mathias.mull...@citrix.com]
> > > Sent: Friday, February 15, 2013 12:46 PM
> > > To: cloudstack-us...@incubator.apache.org
> > > Subject: Re: customising the ROOT disk
> > >
> > > true. you can do that if you have LVM or Volume manager in windows. But
> > > you have to be careful. If that volume gets deleted out from under the
> > VM,
> > > your VM is pretty much dead.
> > >
> > > Thank you,
> > > Matt
> > > On Feb 15, 2013, at 3:38 PM, "Thomas Joseph"  > > > wrote:
> > >
> > > From  storage tab and create a data disk with the required size, assign
> > it
> > > to the VM and then increase the root volume group.
> > >
> > >
> > > Regards,
> > > Thomas
> > >
> > >
> > > -Original Message-
> > > From: Nux! [mailto:n...@li.nux.ro]
> > > Sent: 15 February 2013 07:49 PM
> > > To: Cloudstack users
> > > Subject: customising the ROOT disk
> > >
> > > Hi,
> > >
> > > When I'm creating a new instance is there a way to specify the size of
> > the
> > > ROOT disk? I see it uses the template's size (which in my case is
> > > tiny) and I need to have it increased.
> > >
> > > Pointers?
> > >
> > > Thanks,
> > >
> > > Lucian
> > >
> > > --
> > > Sent from the Delta quadrant using Borg technology!
> > >
> > > Nux!
> > > www.nux.ro
> > >
> > >
> >
>

[jira] [Assigned] (CLOUDSTACK-887) Document volume resize feature

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak reassigned CLOUDSTACK-887:
---

Assignee: Jessica Tomechak

> Document volume resize feature
> --
>
> Key: CLOUDSTACK-887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-887
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Chip Childers
>Assignee: Jessica Tomechak
> Fix For: 4.1.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-881) QA marketplace plugin

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak updated CLOUDSTACK-881:


Fix Version/s: (was: 4.1.0)
   4.2.0

> QA marketplace plugin
> -
>
> Key: CLOUDSTACK-881
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-881
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Test
>Reporter: Chip Childers
> Fix For: 4.2.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-882) Document marketplace plugin

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak updated CLOUDSTACK-882:


Fix Version/s: (was: 4.1.0)
   4.2.0

> Document marketplace plugin
> ---
>
> Key: CLOUDSTACK-882
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-882
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Chip Childers
> Fix For: 4.2.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1102) Create release notes for 4.1

[Jessica Tomechak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak reassigned CLOUDSTACK-1102:


Assignee: Joe Brockmeier

> Create release notes for 4.1
> 
>
> Key: CLOUDSTACK-1102
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1102
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.1.0
>Reporter: Jessica Tomechak
>Assignee: Joe Brockmeier
> Fix For: 4.1.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-887) Document volume resize feature

[Jessica Tomechak (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579631#comment-13579631
 ] 

Jessica Tomechak commented on CLOUDSTACK-887:
-

Please add the documentation for this feature in the existing file 
docs/resizing-volumes.xml. Overwrite the previous info in that file, which is a 
workaround for the fact that CS didn't yet have a resize volume feature.

> Document volume resize feature
> --
>
> Key: CLOUDSTACK-887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-887
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Chip Childers
> Fix For: 4.1.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: [ACS41] Yet another reviewboard reminder... for both committers and contributors.

[Animesh Chaturvedi]

Well the submitter of the review https://reviews.apache.org/r/9336/ listed you 
as one of the reviewers and I was calling out based on that.  

Ok so what should one do if someone lists you as a reviewer? If  you cannot or 
not qualified to review  you can respond saying that you cannot do that review 
and submitter can ask another reviewer. 

I will update  the review board guidelines.

Animesh 


> -Original Message-
> From: Kelcey Damage (BT) [mailto:kel...@backbonetechnology.com]
> Sent: Friday, February 15, 2013 3:05 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [ACS41] Yet another reviewboard reminder... for both committers
> and contributors.
> 
> My name got attached to 1180, and I'm not sure why. I am not what you would
> call capable of reviewing the submission other then from a legal/compliance
> perspective.
> 
> Thanks
> 
> -Kelcey
> 
> >-Original Message-
> >From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >Sent: Friday, February 15, 2013 12:05 PM
> >To: cloudstack-dev@incubator.apache.org
> >Subject: RE: [ACS41] Yet another reviewboard reminder... for both
> >committers and contributors.
> >
> >Folks
> >
> >I have sent emails on over 30 issues from review board this week and as
> >community we responded to 2/3 rd of them which is good but can be better.
> >We were able to knock off only a handful of them. Out of the ones that
> >were responded to many of them are awaiting action from reviewers. If
> >you were called out please respond to your reviews and help us close
> >pending
> reviews.
> >
> >We have 33 pending reviews in review board at this time
> >
> >Animesh
> >
> >
> >
> >> -Original Message-
> >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >> Sent: Monday, February 11, 2013 11:24 PM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: RE: [ACS41] Yet another reviewboard reminder... for both
> >> committers and contributors.
> >>
> >> Folks
> >>
> >> I have sent a number of reminder emails for some of the review board
> >> items that have been pending for a while. Please attend to them at
> >> the earliest . We are running at 50+ items in review board. If you
> >> are a committer I request you knock off 1-2 reviews per week
> >>
> >> Animesh
> >>
> >> > -Original Message-
> >> > From: Chip Childers [mailto:chip.child...@sungard.com]
> >> > Sent: Tuesday, January 29, 2013 9:18 AM
> >> > To: cloudstack-dev@incubator.apache.org
> >> > Subject: [ACS41] Yet another reviewboard reminder... for both
> >> > committers and contributors.
> >> >
> >> > Hi all (and specifically people that were listed as "maintainers"
> >> > of certain code modules),
> >> >
> >> > We need committer help in getting the community contributions
> >> > currently in reviewboard (as well as some that we expect to show up
> >> > in the next day or so) reviewed and committed as soon as possible.
> >> >
> >> > If you are a "maintainer", or simply feel that you have enough
> >> > knowledge to get through one or more of these reviews, PLEASE take
> >> > some time to help clear out the board.
> >> >
> >> > Based on our agreed upon schedule, we need everything into master
> >> > (or
> >> > javelin) by EOD Thursday.
> >> >
> >> > For those of you that have code you want to be reviewed, but have
> >> > not yet submitted, it needs to get in ASAP.  Otherwise, there's no
> >> > chance that someone will have the time to review and commit before
> >> > we cut the
> >> release branch.
> >> >
> >> > -chip

Re: [DOCS][DISCUSS]Documentation for 4.1

[Jessica Tomechak]

On Fri, Feb 15, 2013 at 8:01 AM, Joe Brockmeier  wrote:

> Howdy Radhika,
>
> On Thu, Feb 14, 2013, at 09:43 PM, Radhika Puthiyetath wrote:
> > Hello Doc contributors,
> >
> > Thanks for the support. I would like to know other than Sebastian,
> > Jessica, and I who are willing to work on the 4.1 features.
> >
> > I don't see anyone signed up for any features in the plan/ doc defect.
>
> It's helpful if you would include the URLs for easy reference so folks
> can quickly peek at what you're talking about.
>
> I believe you mean this page?
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Apache+CloudStack+v+4.1+Documentation+Plan#ApacheCloudStackv4.1DocumentationPlan-InstallationGuides%3AUpdate
>
> > If you pick up, I would get a clear idea as to whether I need spend any
> > long hours/ weekends: I prefer not to slip the schedule ...
>
> I've picked up the release notes and install from source. I may be able
> to pick up some others, depending on how those two go...
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>

Joe,
Thanks for picking up doc tasks. The ones you picked are exactly the ones
that are further from Radhika's and my usual daily tasks, so they are
particularly helpful for you to attend to. Thanks again.

Jessica T.

Re: [DOC] Is the Working with Volumes section missing from docs on purpose?

[Marcus Sorensen]

That is interesting. Has anyone written the resizing volumes section? I saw
a task for it but nobody assigned.
On Feb 15, 2013 5:12 PM, "Jessica Tomechak" 
wrote:

> This question on -users prompted me to look for our "Resizing Volumes"
> section. I discovered that it is missing, along with the entire "Working
> with Volumes" section. All the files are in the repo's docs directory
> already, so I think it's just an oversight.
>
> Before I file a bug and add this info back in, I wonder whether anyone
> remembers deciding on purpose to leave this info out? Or has someone
> perhaps rewritten this and put it in another part of the docs?
>
> The missing section covers:
>
> What is a volume
> Uploading an existing volume to a VM
> Attaching a volume to a VM
> Detaching a volume from one VM and attaching it to a different one
> Moving volumes from one storage pool to another
> Resizing volumes (using VHD)
> How deleting a volume affects snapshots (it doesn't)
> How to configure garbage collection of deleted volumes
>
> Jessica T.
>
>
> -Original Message-
> > From: Clayton Weise [mailto:cwe...@iswest.net]
> > Sent: Friday, February 15, 2013 1:33 PM
> > To: cloudstack-us...@incubator.apache.org
> > Subject: RE: customising the ROOT disk
> >
> > Not that I'm recommending or endorsing this method but we have done it in
> > the past.  Stop the instance, resize the root volume on your hypervisor
> > directly (this process varies based on the hypervisor and storage method
> > used), adjust the size to match in the CloudStack database (specifically
> in
> > the volumes table), and start the instance.
> >
> > -Original Message-
> > From: Mathias Mullins [mailto:mathias.mull...@citrix.com]
> > Sent: Friday, February 15, 2013 12:46 PM
> > To: cloudstack-us...@incubator.apache.org
> > Subject: Re: customising the ROOT disk
> >
> > true. you can do that if you have LVM or Volume manager in windows. But
> > you have to be careful. If that volume gets deleted out from under the
> VM,
> > your VM is pretty much dead.
> >
> > Thank you,
> > Matt
> > On Feb 15, 2013, at 3:38 PM, "Thomas Joseph"  > > wrote:
> >
> > From  storage tab and create a data disk with the required size, assign
> it
> > to the VM and then increase the root volume group.
> >
> >
> > Regards,
> > Thomas
> >
> >
> > -Original Message-
> > From: Nux! [mailto:n...@li.nux.ro]
> > Sent: 15 February 2013 07:49 PM
> > To: Cloudstack users
> > Subject: customising the ROOT disk
> >
> > Hi,
> >
> > When I'm creating a new instance is there a way to specify the size of
> the
> > ROOT disk? I see it uses the template's size (which in my case is
> > tiny) and I need to have it increased.
> >
> > Pointers?
> >
> > Thanks,
> >
> > Lucian
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> >
>

Re: Fix for packaging/centos63/package.sh

[Marcus Sorensen]

I may not have picked into master.
On Feb 15, 2013 5:14 PM, "Marcus Sorensen"  wrote:

> That is old. I changed that line yesterday. It was catching all sorts of
> things like "downloading"
> On Feb 15, 2013 5:11 PM, "Musayev, Ilya"  wrote:
>
>> Please fix the logic in package.sh script to make it work
>>
>> Specificialy
>>
>> VERSION=`(cd ../../; mvn
>> org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate
>> -Dexpression=project.version) | grep -v '^\['`
>>
>> Change to
>>
>>
>> VERSION=`(cd ../../; mvn
>> org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate
>> -Dexpression=project.version) | grep -vE '^\[|dt_socket'`
>>
>> If you don't, the packager takes the string that appears prior to a
>> version number and tar/rpm process fails.
>>
>>
>>
>>

Re: Fix for packaging/centos63/package.sh

[Marcus Sorensen]

That is old. I changed that line yesterday. It was catching all sorts of
things like "downloading"
On Feb 15, 2013 5:11 PM, "Musayev, Ilya"  wrote:

> Please fix the logic in package.sh script to make it work
>
> Specificialy
>
> VERSION=`(cd ../../; mvn
> org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate
> -Dexpression=project.version) | grep -v '^\['`
>
> Change to
>
>
> VERSION=`(cd ../../; mvn
> org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate
> -Dexpression=project.version) | grep -vE '^\[|dt_socket'`
>
> If you don't, the packager takes the string that appears prior to a
> version number and tar/rpm process fails.
>
>
>
>

RE: [Discuss] Name convention of class variable

[Edison Su]

+1, no _, during the refactor, I removed all the _ as much as I can already.

> -Original Message-
> From: Frank Zhang [mailto:frank.zh...@citrix.com]
> Sent: Friday, February 15, 2013 2:12 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [Discuss] Name convention of class variable
> 
> Current name convention of class variable in CloudStack is prefixing variable
> name with a '_', for example
> 
> Class SomeManagerImpl {
>   private long _myVar;
> }
> 
> I know this is widely spread convention but I really think it's dated. First 
> time I
> saw it is in the famous book "Programming in Java Language", it helps you to
> distinguish class variable and variable defined in function in PLAIN text 
> editor.
> But nowadays everybody writing code in IDE like Eclipse and every IDE
> highlights these variables in vivid color, there is no needs to use underscore
> anymore.
> 
> And this convention has a significant disadvantage that is broken Java Bean
> style. A Java bean is a class with setter/getter, I always use Eclipse's 
> shortcut
> "Alt+Shift+S

[DOC] Is the Working with Volumes section missing from docs on purpose?

[Jessica Tomechak]

This question on -users prompted me to look for our "Resizing Volumes"
section. I discovered that it is missing, along with the entire "Working
with Volumes" section. All the files are in the repo's docs directory
already, so I think it's just an oversight.

Before I file a bug and add this info back in, I wonder whether anyone
remembers deciding on purpose to leave this info out? Or has someone
perhaps rewritten this and put it in another part of the docs?

The missing section covers:

What is a volume
Uploading an existing volume to a VM
Attaching a volume to a VM
Detaching a volume from one VM and attaching it to a different one
Moving volumes from one storage pool to another
Resizing volumes (using VHD)
How deleting a volume affects snapshots (it doesn't)
How to configure garbage collection of deleted volumes

Jessica T.


-Original Message-
> From: Clayton Weise [mailto:cwe...@iswest.net]
> Sent: Friday, February 15, 2013 1:33 PM
> To: cloudstack-us...@incubator.apache.org
> Subject: RE: customising the ROOT disk
>
> Not that I'm recommending or endorsing this method but we have done it in
> the past.  Stop the instance, resize the root volume on your hypervisor
> directly (this process varies based on the hypervisor and storage method
> used), adjust the size to match in the CloudStack database (specifically in
> the volumes table), and start the instance.
>
> -Original Message-
> From: Mathias Mullins [mailto:mathias.mull...@citrix.com]
> Sent: Friday, February 15, 2013 12:46 PM
> To: cloudstack-us...@incubator.apache.org
> Subject: Re: customising the ROOT disk
>
> true. you can do that if you have LVM or Volume manager in windows. But
> you have to be careful. If that volume gets deleted out from under the VM,
> your VM is pretty much dead.
>
> Thank you,
> Matt
> On Feb 15, 2013, at 3:38 PM, "Thomas Joseph"  > wrote:
>
> From  storage tab and create a data disk with the required size, assign it
> to the VM and then increase the root volume group.
>
>
> Regards,
> Thomas
>
>
> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: 15 February 2013 07:49 PM
> To: Cloudstack users
> Subject: customising the ROOT disk
>
> Hi,
>
> When I'm creating a new instance is there a way to specify the size of the
> ROOT disk? I see it uses the template's size (which in my case is
> tiny) and I need to have it increased.
>
> Pointers?
>
> Thanks,
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>

RE: Review Request: Scripts for Selenium UI automation.

[kelcey Damage]

Shouldn't all the @author line be removed? That's the first thing I noticed
in the diffs

>-Original Message-
>From: Parth Jagirdar [mailto:parth.jagir...@citrix.com]
>Sent: Friday, February 15, 2013 1:50 PM
>To: cloudstack-dev@incubator.apache.org
>Cc: Animesh Chaturvedi; Kelcey Jamison-Damage; John Kinsella
>Subject: RE: Review Request: Scripts for Selenium UI automation.
>
>
>What is the purpose behind the Selenium and Python UI automation?
>
>-- To Increase Test Coverage; Thorough UI. To increate stability of UI and
>product as a whole.
>
>Could you give me some more background, or perhaps so links with details as
>to the scope and purpose?
>
>-- We would like to run basic Sanity test on UI. For which we are using
>http://wiki.cloudstack.org/display/QA/Manual+BVT as reference.
>
>Scope is UI testing.
>
>Purpose is to,
>
>Cover basic sanity test through UI on a new release.
>To run these tests unattended.
>Generate reports are compatible with HTML or XML (JUNIT)
>
>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+
>using+Selenium+and+Python
>
>Thanks,
>.. Parth
>
>
>-Original Message-
>From: Kelceydamage@bbits [mailto:kel...@bbits.ca]
>Sent: Friday, February 15, 2013 11:34 AM
>To: cloudstack-dev@incubator.apache.org
>Cc: Animesh Chaturvedi; Kelcey Jamison-Damage; John Kinsella; cloudstack
>Subject: Re: Review Request: Scripts for Selenium UI automation.
>
>I'm really behind on what's going on here. What is the purpose behind the
>Selenium and Python UI automation?
>
>This seems similar to the .net/IronPython work I was doing and the various
>Python API Wrappers.
>
>Could you give me some more background, or perhaps so links with details as
>to the scope and purpose?
>
>Thanks
>
>Sent from my iPhone
>
>On Feb 15, 2013, at 11:03 AM, Parth Jagirdar 
>wrote:
>
>> John & Kelcey,
>>
>> I have uploaded basic description for what scripts do.
>>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+
>u
>> sing+Selenium+and+Python
>>
>> Please review and let me know if any compliance issues.
>> I can fix and resubmit the scripts.
>>
>>
>> Thanks,
>> .. Parth
>>
>>
>> -Original Message-
>> From: Animesh Chaturvedi
>> Sent: Wednesday, February 13, 2013 7:13 PM
>> To: Parth Jagirdar; Kelcey Jamison-Damage; John Kinsella
>> Cc: cloudstack
>> Subject: RE: Review Request: Scripts for Selenium UI automation.
>>
>> Kelcey, john
>>
>> Please review Parth's patch
>>
>>> -Original Message-
>>> From: Parth Jagirdar [mailto:nore...@reviews.apache.org] On Behalf Of
>>> Parth Jagirdar
>>> Sent: Wednesday, February 06, 2013 1:06 PM
>>> To: Kelcey Jamison-Damage; John Kinsella
>>> Cc: cloudstack; Parth Jagirdar
>>> Subject: Re: Review Request: Scripts for Selenium UI automation.
>>>
>>>
>>> ---
>>> This is an automatically generated e-mail. To reply, visit:
>>> https://reviews.apache.org/r/9336/
>>> ---
>>>
>>> (Updated Feb. 6, 2013, 9:05 p.m.)
>>>
>>>
>>> Review request for cloudstack, John Kinsella and Kelcey Jamison-Damage.
>>>
>>>
>>> Description
>>> ---
>>>
>>> These scripts will execute following test cases on UI through Firefox.
>>> (Test Cases taken from ::
>>> http://wiki.cloudstack.org/display/QA/Manual+BVT)
>>>
>>>
>>> Login Admin user to UI.
>>> Create an Account name Test.
>>> Logout Admin user.
>>> Login Test user.
>>>
>>> Add a new Disk Offering.
>>> Edit this Disk offering.
>>> Delete this Disk offering.
>>>
>>> Add a new Compute Offering.
>>> Edit this Compute offering.
>>> Delete this Compute offering.
>>>
>>> Logout Test user.
>>> Login Admin user.
>>> Delete Test user Account. And tear down the Browser instance.
>>>
>>> # End of Tests
>>>
>>> Thanks,
>>> ...Parth
>>>
>>>
>>> This addresses bug CLOUDSTACK-1180.
>>>
>>>
>>> Diffs
>>> -
>>>
>>>  test/selenium/ReadMe.txt PRE-CREATION
>>> test/selenium/lib/Global_Locators.py PRE-CREATION
>>> test/selenium/lib/__init__.py PRE-CREATION
>>> test/selenium/lib/initialize.py PRE-CREATION
>>> test/selenium/smoke/Login_and_Accounts.py PRE-CREATION
>>> test/selenium/smoke/Service_Offering.py PRE-CREATION
>>> test/selenium/smoke/TemplatesAndISO.py PRE-CREATION
>>> test/selenium/smoke/VM_lifeCycle.py PRE-CREATION
>>> test/selenium/smoke/main.py PRE-CREATION
>>>
>>> Diff: https://reviews.apache.org/r/9336/diff/
>>>
>>>
>>> Testing
>>> ---
>>>
>>> Tested with network refactor branch.
>>>
>>>
>>> Thanks,
>>>
>>> Parth Jagirdar
>>

Re: Review Request: Non-printable characters such as %00 or %0025 are getting stored in raw/non encoded form in the database

[John Kinsella]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8876/#review16669
---

Ship it!


Ship It!

- John Kinsella


On Feb. 11, 2013, 12:34 p.m., Likitha Shetty wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/8876/
> ---
> 
> (Updated Feb. 11, 2013, 12:34 p.m.)
> 
> 
> Review request for cloudstack, John Kinsella, Alena Prokharchyk, and Rohit 
> Yadav.
> 
> 
> Description
> ---
> 
> Non-printable characters results in empty pages for all users loading the 
> corrupted object in the web interface. It also results in the API call 
> results getting truncated with an error when it encounters the non-printable 
> characters.
> To find if a parameter value contains a control character, every decoded 
> parameter value was matched with the regex [\000-\037\177] as the ASCII 
> non-printable characters are numbers 0 to 31 and 127 decimal.
> 
> 
> This addresses bug CLOUDSTACK-863.
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/api/ApiServer.java d99d188 
>   utils/pom.xml 937fad3 
>   utils/src/com/cloud/utils/StringUtils.java 8f0a503 
> 
> Diff: https://reviews.apache.org/r/8876/diff/
> 
> 
> Testing
> ---
> 
> Manual Testing done, 
> For sample API's (updateVirtualMachine, createVolume, 
> authorizeSecurityGroupIngress etc), provide input values containing 
> character(s) that are
> • ASCII printable - pass 
> • ASCII non-printable - fail with error code 431 and error 'Received value 
>  for parameter  is invalid, contains illegal 
> ASCII non-printable characters' 
> • non-english - pass
> 
> 
> Thanks,
> 
> Likitha Shetty
> 
>

Fix for packaging/centos63/package.sh

[Musayev, Ilya]

Please fix the logic in package.sh script to make it work

Specificialy

VERSION=`(cd ../../; mvn 
org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate 
-Dexpression=project.version) | grep -v '^\['`

Change to


VERSION=`(cd ../../; mvn 
org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate 
-Dexpression=project.version) | grep -vE '^\[|dt_socket'`

If you don't, the packager takes the string that appears prior to a version 
number and tar/rpm process fails.

[jira] [Commented] (CLOUDSTACK-1269) Failed to start CPVM java.lang.NullPointerException Unable to start SSVM

[angeline shen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579538#comment-13579538
 ] 

angeline shen commented on CLOUDSTACK-1269:
---

On host   10.223.58.194  After rename /etc/cloudstack/agent/log4j-cloud.xml 
to  log4j.xml,   /var/log/cloudstack/agent/agent.log was generated.

attached agent.log to bug.  

In the error below :

Exception  org.libvirt.LibvirtException: Cannot get interface MTU on 
'cloudbr1': No such device 

There is no cloudbr1  on host,  only cloudbr0:
[root@Rack3Host15 agent]# ip route
10.223.58.192/26 dev cloudbr0  proto kernel  scope link  src 10.223.58.194 
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
169.254.0.0/16 dev cloud0  proto kernel  scope link  src 169.254.0.1 
default via 10.223.58.193 dev cloudbr0 

Why is agent looking for cloudbr1?




2013-02-15 16:43:41,127 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-4:null) Failed to start domain: s-833-VM: Cannot get 
interface MTU on 'cloudbr1': No such device
2013-02-15 16:43:41,129 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-4:null) Exception
org.libvirt.LibvirtException: Cannot get interface MTU on 'cloudbr1': No such 
device
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Domain.processError(Unknown Source)
at org.libvirt.Domain.create(Unknown Source)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:1038)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3087)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1163)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-02-15 16:43:41,132 WARN  [cloud.agent.Agent] (agentRequest-Handler-4:null) 
Caught:
java.lang.NullPointerException
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupVMNetworks(LibvirtComputingResource.java:4214)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.handleVmStartFailure(LibvirtComputingResource.java:2983)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3107)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1163)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-02-15 16:43:51,842 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Failed to start domain: v-2-VM: Cannot get 
interface MTU on 'cloudbr1': No such device
2013-02-15 16:43:51,843 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Exception
org.libvirt.LibvirtException: Cannot get interface MTU on 'cloudbr1': No such 
device
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Domain.processError(Unknown Source)
at org.libvirt.Domain.create(Unknown Source)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:1038)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3087)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1163)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-02-15 16:43:51,843 WARN  [cloud.agent.Agent] (agentRequest-Handler-5:null) 
Caught:
java.lang.NullPointerException
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.clean

RE: [ACS41] Yet another reviewboard reminder... for both committers and contributors.

[Kelcey Damage (BT)]

My name got attached to 1180, and I'm not sure why. I am not what you would
call capable of reviewing the submission other then from a legal/compliance
perspective.

Thanks

-Kelcey

>-Original Message-
>From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>Sent: Friday, February 15, 2013 12:05 PM
>To: cloudstack-dev@incubator.apache.org
>Subject: RE: [ACS41] Yet another reviewboard reminder... for both
>committers and contributors.
>
>Folks
>
>I have sent emails on over 30 issues from review board this week and as
>community we responded to 2/3 rd of them which is good but can be better.
>We were able to knock off only a handful of them. Out of the ones that were
>responded to many of them are awaiting action from reviewers. If you were
>called out please respond to your reviews and help us close pending
reviews.
>
>We have 33 pending reviews in review board at this time
>
>Animesh
>
>
>
>> -Original Message-
>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> Sent: Monday, February 11, 2013 11:24 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: [ACS41] Yet another reviewboard reminder... for both
>> committers and contributors.
>>
>> Folks
>>
>> I have sent a number of reminder emails for some of the review board
>> items that have been pending for a while. Please attend to them at the
>> earliest . We are running at 50+ items in review board. If you are a
>> committer I request you knock off 1-2 reviews per week
>>
>> Animesh
>>
>> > -Original Message-
>> > From: Chip Childers [mailto:chip.child...@sungard.com]
>> > Sent: Tuesday, January 29, 2013 9:18 AM
>> > To: cloudstack-dev@incubator.apache.org
>> > Subject: [ACS41] Yet another reviewboard reminder... for both
>> > committers and contributors.
>> >
>> > Hi all (and specifically people that were listed as "maintainers" of
>> > certain code modules),
>> >
>> > We need committer help in getting the community contributions
>> > currently in reviewboard (as well as some that we expect to show up
>> > in the next day or so) reviewed and committed as soon as possible.
>> >
>> > If you are a "maintainer", or simply feel that you have enough
>> > knowledge to get through one or more of these reviews, PLEASE take
>> > some time to help clear out the board.
>> >
>> > Based on our agreed upon schedule, we need everything into master
>> > (or
>> > javelin) by EOD Thursday.
>> >
>> > For those of you that have code you want to be reviewed, but have
>> > not yet submitted, it needs to get in ASAP.  Otherwise, there's no
>> > chance that someone will have the time to review and commit before
>> > we cut the
>> release branch.
>> >
>> > -chip

RE: Review Request: Scripts for Selenium UI automation.

[kelcey Damage]

Thank you very much, I'll give this a read through

>-Original Message-
>From: Parth Jagirdar [mailto:parth.jagir...@citrix.com]
>Sent: Friday, February 15, 2013 1:50 PM
>To: cloudstack-dev@incubator.apache.org
>Cc: Animesh Chaturvedi; Kelcey Jamison-Damage; John Kinsella
>Subject: RE: Review Request: Scripts for Selenium UI automation.
>
>
>What is the purpose behind the Selenium and Python UI automation?
>
>-- To Increase Test Coverage; Thorough UI. To increate stability of UI and
>product as a whole.
>
>Could you give me some more background, or perhaps so links with details as
>to the scope and purpose?
>
>-- We would like to run basic Sanity test on UI. For which we are using
>http://wiki.cloudstack.org/display/QA/Manual+BVT as reference.
>
>Scope is UI testing.
>
>Purpose is to,
>
>Cover basic sanity test through UI on a new release.
>To run these tests unattended.
>Generate reports are compatible with HTML or XML (JUNIT)
>
>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+
>using+Selenium+and+Python
>
>Thanks,
>.. Parth
>
>
>-Original Message-
>From: Kelceydamage@bbits [mailto:kel...@bbits.ca]
>Sent: Friday, February 15, 2013 11:34 AM
>To: cloudstack-dev@incubator.apache.org
>Cc: Animesh Chaturvedi; Kelcey Jamison-Damage; John Kinsella; cloudstack
>Subject: Re: Review Request: Scripts for Selenium UI automation.
>
>I'm really behind on what's going on here. What is the purpose behind the
>Selenium and Python UI automation?
>
>This seems similar to the .net/IronPython work I was doing and the various
>Python API Wrappers.
>
>Could you give me some more background, or perhaps so links with details as
>to the scope and purpose?
>
>Thanks
>
>Sent from my iPhone
>
>On Feb 15, 2013, at 11:03 AM, Parth Jagirdar 
>wrote:
>
>> John & Kelcey,
>>
>> I have uploaded basic description for what scripts do.
>>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+
>u
>> sing+Selenium+and+Python
>>
>> Please review and let me know if any compliance issues.
>> I can fix and resubmit the scripts.
>>
>>
>> Thanks,
>> .. Parth
>>
>>
>> -Original Message-
>> From: Animesh Chaturvedi
>> Sent: Wednesday, February 13, 2013 7:13 PM
>> To: Parth Jagirdar; Kelcey Jamison-Damage; John Kinsella
>> Cc: cloudstack
>> Subject: RE: Review Request: Scripts for Selenium UI automation.
>>
>> Kelcey, john
>>
>> Please review Parth's patch
>>
>>> -Original Message-
>>> From: Parth Jagirdar [mailto:nore...@reviews.apache.org] On Behalf Of
>>> Parth Jagirdar
>>> Sent: Wednesday, February 06, 2013 1:06 PM
>>> To: Kelcey Jamison-Damage; John Kinsella
>>> Cc: cloudstack; Parth Jagirdar
>>> Subject: Re: Review Request: Scripts for Selenium UI automation.
>>>
>>>
>>> ---
>>> This is an automatically generated e-mail. To reply, visit:
>>> https://reviews.apache.org/r/9336/
>>> ---
>>>
>>> (Updated Feb. 6, 2013, 9:05 p.m.)
>>>
>>>
>>> Review request for cloudstack, John Kinsella and Kelcey Jamison-Damage.
>>>
>>>
>>> Description
>>> ---
>>>
>>> These scripts will execute following test cases on UI through Firefox.
>>> (Test Cases taken from ::
>>> http://wiki.cloudstack.org/display/QA/Manual+BVT)
>>>
>>>
>>> Login Admin user to UI.
>>> Create an Account name Test.
>>> Logout Admin user.
>>> Login Test user.
>>>
>>> Add a new Disk Offering.
>>> Edit this Disk offering.
>>> Delete this Disk offering.
>>>
>>> Add a new Compute Offering.
>>> Edit this Compute offering.
>>> Delete this Compute offering.
>>>
>>> Logout Test user.
>>> Login Admin user.
>>> Delete Test user Account. And tear down the Browser instance.
>>>
>>> # End of Tests
>>>
>>> Thanks,
>>> ...Parth
>>>
>>>
>>> This addresses bug CLOUDSTACK-1180.
>>>
>>>
>>> Diffs
>>> -
>>>
>>>  test/selenium/ReadMe.txt PRE-CREATION
>>> test/selenium/lib/Global_Locators.py PRE-CREATION
>>> test/selenium/lib/__init__.py PRE-CREATION
>>> test/selenium/lib/initialize.py PRE-CREATION
>>> test/selenium/smoke/Login_and_Accounts.py PRE-CREATION
>>> test/selenium/smoke/Service_Offering.py PRE-CREATION
>>> test/selenium/smoke/TemplatesAndISO.py PRE-CREATION
>>> test/selenium/smoke/VM_lifeCycle.py PRE-CREATION
>>> test/selenium/smoke/main.py PRE-CREATION
>>>
>>> Diff: https://reviews.apache.org/r/9336/diff/
>>>
>>>
>>> Testing
>>> ---
>>>
>>> Tested with network refactor branch.
>>>
>>>
>>> Thanks,
>>>
>>> Parth Jagirdar
>>

RE: Review Request: Scripts for Selenium UI automation.

[Parth Jagirdar]

Aite...

Suggested Changed made.

Please review.

Thanks,
.. Parth


-Original Message-
From: kelcey Damage [mailto:m...@kelceydamage.com] 
Sent: Friday, February 15, 2013 2:55 PM
To: Parth Jagirdar; cloudstack-dev@incubator.apache.org
Cc: Animesh Chaturvedi; 'John Kinsella'
Subject: RE: Review Request: Scripts for Selenium UI automation.

Shouldn't all the @author line be removed? That's the first thing I noticed in 
the diffs

>-Original Message-
>From: Parth Jagirdar [mailto:parth.jagir...@citrix.com]
>Sent: Friday, February 15, 2013 1:50 PM
>To: cloudstack-dev@incubator.apache.org
>Cc: Animesh Chaturvedi; Kelcey Jamison-Damage; John Kinsella
>Subject: RE: Review Request: Scripts for Selenium UI automation.
>
>
>What is the purpose behind the Selenium and Python UI automation?
>
>-- To Increase Test Coverage; Thorough UI. To increate stability of UI 
>and product as a whole.
>
>Could you give me some more background, or perhaps so links with 
>details as to the scope and purpose?
>
>-- We would like to run basic Sanity test on UI. For which we are using 
>http://wiki.cloudstack.org/display/QA/Manual+BVT as reference.
>
>Scope is UI testing.
>
>Purpose is to,
>
>Cover basic sanity test through UI on a new release.
>To run these tests unattended.
>Generate reports are compatible with HTML or XML (JUNIT)
>
>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+
>using+Selenium+and+Python
>
>Thanks,
>.. Parth
>
>
>-Original Message-
>From: Kelceydamage@bbits [mailto:kel...@bbits.ca]
>Sent: Friday, February 15, 2013 11:34 AM
>To: cloudstack-dev@incubator.apache.org
>Cc: Animesh Chaturvedi; Kelcey Jamison-Damage; John Kinsella; 
>cloudstack
>Subject: Re: Review Request: Scripts for Selenium UI automation.
>
>I'm really behind on what's going on here. What is the purpose behind 
>the Selenium and Python UI automation?
>
>This seems similar to the .net/IronPython work I was doing and the 
>various Python API Wrappers.
>
>Could you give me some more background, or perhaps so links with 
>details as to the scope and purpose?
>
>Thanks
>
>Sent from my iPhone
>
>On Feb 15, 2013, at 11:03 AM, Parth Jagirdar 
>
>wrote:
>
>> John & Kelcey,
>>
>> I have uploaded basic description for what scripts do.
>>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+
>u
>> sing+Selenium+and+Python
>>
>> Please review and let me know if any compliance issues.
>> I can fix and resubmit the scripts.
>>
>>
>> Thanks,
>> .. Parth
>>
>>
>> -Original Message-
>> From: Animesh Chaturvedi
>> Sent: Wednesday, February 13, 2013 7:13 PM
>> To: Parth Jagirdar; Kelcey Jamison-Damage; John Kinsella
>> Cc: cloudstack
>> Subject: RE: Review Request: Scripts for Selenium UI automation.
>>
>> Kelcey, john
>>
>> Please review Parth's patch
>>
>>> -Original Message-
>>> From: Parth Jagirdar [mailto:nore...@reviews.apache.org] On Behalf 
>>> Of Parth Jagirdar
>>> Sent: Wednesday, February 06, 2013 1:06 PM
>>> To: Kelcey Jamison-Damage; John Kinsella
>>> Cc: cloudstack; Parth Jagirdar
>>> Subject: Re: Review Request: Scripts for Selenium UI automation.
>>>
>>>
>>> ---
>>> This is an automatically generated e-mail. To reply, visit:
>>> https://reviews.apache.org/r/9336/
>>> ---
>>>
>>> (Updated Feb. 6, 2013, 9:05 p.m.)
>>>
>>>
>>> Review request for cloudstack, John Kinsella and Kelcey Jamison-Damage.
>>>
>>>
>>> Description
>>> ---
>>>
>>> These scripts will execute following test cases on UI through Firefox.
>>> (Test Cases taken from ::
>>> http://wiki.cloudstack.org/display/QA/Manual+BVT)
>>>
>>>
>>> Login Admin user to UI.
>>> Create an Account name Test.
>>> Logout Admin user.
>>> Login Test user.
>>>
>>> Add a new Disk Offering.
>>> Edit this Disk offering.
>>> Delete this Disk offering.
>>>
>>> Add a new Compute Offering.
>>> Edit this Compute offering.
>>> Delete this Compute offering.
>>>
>>> Logout Test user.
>>> Login Admin user.
>>> Delete Test user Account. And tear down the Browser instance.
>>>
>>> # End of Tests
>>>
>>> Thanks,
>>> ...Parth
>>>
>>>
>>> This addresses bug CLOUDSTACK-1180.
>>>
>>>
>>> Diffs
>>> -
>>>
>>>  test/selenium/ReadMe.txt PRE-CREATION 
>>> test/selenium/lib/Global_Locators.py PRE-CREATION 
>>> test/selenium/lib/__init__.py PRE-CREATION 
>>> test/selenium/lib/initialize.py PRE-CREATION 
>>> test/selenium/smoke/Login_and_Accounts.py PRE-CREATION 
>>> test/selenium/smoke/Service_Offering.py PRE-CREATION 
>>> test/selenium/smoke/TemplatesAndISO.py PRE-CREATION 
>>> test/selenium/smoke/VM_lifeCycle.py PRE-CREATION 
>>> test/selenium/smoke/main.py PRE-CREATION
>>>
>>> Diff: https://reviews.apache.org/r/9336/diff/
>>>
>>>
>>> Testing
>>> ---
>>>
>>> Tested with network refactor branch.
>>>
>>>
>>> Thanks,
>>>
>>> Parth Jagirdar
>>

[Discuss] Name convention of class variable

[Frank Zhang]

Current name convention of class variable in CloudStack is prefixing variable 
name with a '_', for example

Class SomeManagerImpl {
private long _myVar;
}

I know this is widely spread convention but I really think it's dated. First 
time I saw it is in the famous book "Programming in Java Language", it helps 
you to distinguish class variable and variable defined in function in PLAIN 
text editor.
But nowadays everybody writing code in IDE like Eclipse and every IDE 
highlights these variables in vivid color, there is no needs to use underscore 
anymore.

And this convention has a significant disadvantage that is broken Java Bean 
style. A Java bean is a class with setter/getter, I always use Eclipse's 
shortcut "Alt+Shift+S

RE: [DISCUSS] Graduation to a TLP?

[Alex Huang]

Mike,

It is important to note that it is much more preferable to drive a consensus 
through discussion than to make a vote.  Vote should be something of a last 
resort to use.  Also only emails with [VOTE] is asking for a vote.  In emails 
without such tag, the +1 just means the sender liking something said in the 
email. 

--Alex

> -Original Message-
> From: Joe Brockmeier [mailto:j...@zonker.net]
> Sent: Friday, February 15, 2013 12:23 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Graduation to a TLP?
> 
> On Fri, Feb 15, 2013, at 02:08 PM, Mike Tutkowski wrote:
> > Can I ask what may be a silly question about voting?  :)
> 
> That's not a silly question.
> 
> > When these votes are put out there, who can vote?  Just committers or
> > anyone participating in the community?
> 
> Anyone can vote, but only some of the votes are binding. If you see a
> vote taking place that you feel you have a stake in / an opinion on, you
> should feel free to vote anyway.
> 
> Why? Even if your vote isn't binding, it may be useful to understand how
> folks in the community think about something even if their vote isn't
> binding.
> 
> I believe it's PPMC votes that are binding for the vote held within the
> podling, btw. But please don't let that stop you from weighing in if you
> wish to.
> 
> 
> Best,
> 
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

RE: [Discuss] Name convention of class variable

[Frank Zhang]

Sorry, wrongly sent former one by mistake.

Current name convention of class variable in CloudStack is prefixing variable 
name with a '_', for example

Class SomeManagerImpl {
private long _myVar;
}

I know this is widely spread convention but I really think it's dated. First 
time I saw it is in the famous book "Programming in Java Language", it helps 
you to distinguish class variable and variable defined in function in PLAIN 
text editor.
But nowadays everybody writing code in IDE like Eclipse and every IDE 
highlights these variables in vivid color, there is no needs to use underscore 
anymore.

And this convention has a significant disadvantage that is broken Java Bean 
style. A Java bean is a class with setter/getter, I always use Eclipse's 
shortcut "Alt+Shift+s" to call "Generate getter and setter ..."
Then variable with '_' leads to below setter/getter:

Class SomeManagerImpl {
private long _myVar;

public void set_myVar(long _myVar) {
}

public long  get_myVar() {
}
}

So, I suggest obsoleting this convention, don't prefix a '_' anymore.

> -Original Message-
> From: Frank Zhang
> Sent: Friday, February 15, 2013 2:12 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [Discuss] Name convention of class variable
> 
> Current name convention of class variable in CloudStack is prefixing variable
> name with a '_', for example
> 
> Class SomeManagerImpl {
>   private long _myVar;
> }
> 
> I know this is widely spread convention but I really think it's dated. First 
> time I
> saw it is in the famous book "Programming in Java Language", it helps you to
> distinguish class variable and variable defined in function in PLAIN text 
> editor.
> But nowadays everybody writing code in IDE like Eclipse and every IDE
> highlights these variables in vivid color, there is no needs to use underscore
> anymore.
> 
> And this convention has a significant disadvantage that is broken Java Bean
> style. A Java bean is a class with setter/getter, I always use Eclipse's 
> shortcut
> "Alt+Shift+S

Re: Review Request: Scripts for Selenium UI automation.

[Parth Jagirdar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9336/
---

(Updated Feb. 15, 2013, 11:43 p.m.)


Review request for cloudstack, John Kinsella, Prasanna Santhanam, and Kelcey 
Jamison-Damage.


Changes
---

@Author removed as per review comments.


Description
---

These scripts will execute following test cases on UI through Firefox. (Test 
Cases taken from :: http://wiki.cloudstack.org/display/QA/Manual+BVT)


Login Admin user to UI.
Create an Account name Test.
Logout Admin user.
Login Test user.

Add a new Disk Offering.
Edit this Disk offering.
Delete this Disk offering.

Add a new Compute Offering.
Edit this Compute offering.
Delete this Compute offering.

Logout Test user.
Login Admin user.
Delete Test user Account. And tear down the Browser instance.

# End of Tests

Thanks,
...Parth


This addresses bug CLOUDSTACK-1180.


Diffs (updated)
-

  test/selenium/lib/Global_Locators.py PRE-CREATION 
  test/selenium/lib/initialize.py PRE-CREATION 
  test/selenium/smoke/Login_and_Accounts.py PRE-CREATION 
  test/selenium/smoke/Service_Offering.py PRE-CREATION 
  test/selenium/smoke/TemplatesAndISO.py PRE-CREATION 
  test/selenium/smoke/VM_lifeCycle.py PRE-CREATION 
  test/selenium/smoke/main.py PRE-CREATION 

Diff: https://reviews.apache.org/r/9336/diff/


Testing
---

Tested with network refactor branch.


Thanks,

Parth Jagirdar

[jira] [Updated] (CLOUDSTACK-1269) Failed to start CPVM java.lang.NullPointerException Unable to start SSVM

[angeline shen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angeline shen updated CLOUDSTACK-1269:
--

Attachment: agent.log

> Failed to start CPVM java.lang.NullPointerException   Unable to start SSVM
> --
>
> Key: CLOUDSTACK-1269
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1269
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: MS   rhel6.3 10.223.195.114build   
> CloudStack-non-OSS-23-rhel6.3.tar.gz
> host rhel6.3 kvm  10.223.51.2build   
> CloudStack-non-OSS-23-rhel6.3.tar.gz
> 1. host  installation: 
> build  CloudStack-non-OSS-23-rhel6.3.tar.gz  contains old version 
> qemu-img-0.12.1.2-3.209.el6.4.x86_64
> Due to 4.1 packaging, build does not have  new qemu-img and qemu-kvm for 
> testing kvm 6.3 snapshot
> manually replace qemu-img-0.12.1.2-3.209.el6.4.x86_64  with  
> qemu-img-0.12.1.2-3.295.el6.4.x86_64
> manually install   qemu-kvm-0.12.1.2-3.295.el6.4.x86_64
> as part of above , had to remove  libvirt-0.9.10-21.el6.x86_64, download 
> libvirt-0.9.10-21.el6.x86_64
> Here are some rpms that was reinstalled:
>1975468  Feb 13 20:56libvirt-0.9.10-21.el6.x86_64.rpm
>1361029  Feb 13 20:32
> qemu-img-0.12.1.2-3.295.el6.10.x86_64.rpm
>  10878235  Feb 13 20:33
> qemu-kvm-0.12.1.2-3.295.el6.10.x86_64.rpm
>  375800  Feb 13 22:16xnba-kvm-1.0.3-7.x86_64.rpm
> 2.  create advance zone isolation mode.  
> CPVM unable to start  SSVMCPVM
>Reporter: angeline shen
>Assignee: Sudha Ponnaganti
>Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: agent.log, management-server.log.gz, 
> management-server.log.gz, Screenshot-CloudStack - Mozilla Firefox.png, 
> Screenshot-CloudStack - Mozilla Firefox.png
>
>
> 2013-02-13 17:10:25,656 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-12:null) Seq 1-1481768980: Processing:  { Ans: , 
> MgmtId: 6809771312912, via: 1, Ver: v1, Flags: 110, 
> [{"Answer":{"result":false,"details":"java.lang.Nul
> lPointerException\n\tat 
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupVMNetworks(LibvirtComputingResource.java:4214)\n\tat
>  
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.handleVmStartFailure(Libvirt
> ComputingResource.java:2983)\n\tat 
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3107)\n\tat
>  
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtCompu
> tingResource.java:1163)\n\tat 
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat 
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat 
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat java.util.concurrent.
> ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)\n\tat 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
>  
> java.lang.Thread.run(Thread.java:679)\n","wait":0}},{"Answer":{"result":false,"
> details":"Stopped by previous failure","wait":0}}] }
> 2013-02-13 17:10:25,657 DEBUG [agent.transport.Request] (secstorage-1:null) 
> Seq 1-1481768980: Received:  { Ans: , MgmtId: 6809771312912, via: 1, Ver: v1, 
> Flags: 110, { Answer, Answer } }
> 2013-02-13 17:10:25,657 DEBUG [agent.manager.AgentAttache] 
> (AgentManager-Handler-12:null) Seq 1-1481768981: Sending now.  is current 
> sequence.
> 2013-02-13 17:10:25,662 ERROR [cloud.vm.VirtualMachineManagerImpl] 
> (secstorage-1:null) Failed to start instance VM[SecondaryStorageVm|s-1-VM]
> com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that is 
> of class com.cloud.agent.api.StartAnswer
> at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:777)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:466)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:459)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMet

RE: Review Request: Scripts for Selenium UI automation.

[Parth Jagirdar]

What is the purpose behind the Selenium and Python UI automation?

-- To Increase Test Coverage; Thorough UI. To increate stability of UI and 
product as a whole.

Could you give me some more background, or perhaps so links with details as to 
the scope and purpose?

-- We would like to run basic Sanity test on UI. For which we are using 
http://wiki.cloudstack.org/display/QA/Manual+BVT as reference.

Scope is UI testing.

Purpose is to,

Cover basic sanity test through UI on a new release.
To run these tests unattended.
Generate reports are compatible with HTML or XML (JUNIT)


https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+using+Selenium+and+Python

Thanks,
.. Parth


-Original Message-
From: Kelceydamage@bbits [mailto:kel...@bbits.ca] 
Sent: Friday, February 15, 2013 11:34 AM
To: cloudstack-dev@incubator.apache.org
Cc: Animesh Chaturvedi; Kelcey Jamison-Damage; John Kinsella; cloudstack
Subject: Re: Review Request: Scripts for Selenium UI automation.

I'm really behind on what's going on here. What is the purpose behind the 
Selenium and Python UI automation?

This seems similar to the .net/IronPython work I was doing and the various 
Python API Wrappers.

Could you give me some more background, or perhaps so links with details as to 
the scope and purpose?

Thanks

Sent from my iPhone

On Feb 15, 2013, at 11:03 AM, Parth Jagirdar  wrote:

> John & Kelcey,
> 
> I have uploaded basic description for what scripts do.
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+u
> sing+Selenium+and+Python
> 
> Please review and let me know if any compliance issues.
> I can fix and resubmit the scripts.
> 
> 
> Thanks,
> .. Parth
> 
> 
> -Original Message-
> From: Animesh Chaturvedi
> Sent: Wednesday, February 13, 2013 7:13 PM
> To: Parth Jagirdar; Kelcey Jamison-Damage; John Kinsella
> Cc: cloudstack
> Subject: RE: Review Request: Scripts for Selenium UI automation.
> 
> Kelcey, john
> 
> Please review Parth's patch
> 
>> -Original Message-
>> From: Parth Jagirdar [mailto:nore...@reviews.apache.org] On Behalf Of 
>> Parth Jagirdar
>> Sent: Wednesday, February 06, 2013 1:06 PM
>> To: Kelcey Jamison-Damage; John Kinsella
>> Cc: cloudstack; Parth Jagirdar
>> Subject: Re: Review Request: Scripts for Selenium UI automation.
>> 
>> 
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/9336/
>> ---
>> 
>> (Updated Feb. 6, 2013, 9:05 p.m.)
>> 
>> 
>> Review request for cloudstack, John Kinsella and Kelcey Jamison-Damage.
>> 
>> 
>> Description
>> ---
>> 
>> These scripts will execute following test cases on UI through Firefox. 
>> (Test Cases taken from :: 
>> http://wiki.cloudstack.org/display/QA/Manual+BVT)
>> 
>> 
>> Login Admin user to UI.
>> Create an Account name Test.
>> Logout Admin user.
>> Login Test user.
>> 
>> Add a new Disk Offering.
>> Edit this Disk offering.
>> Delete this Disk offering.
>> 
>> Add a new Compute Offering.
>> Edit this Compute offering.
>> Delete this Compute offering.
>> 
>> Logout Test user.
>> Login Admin user.
>> Delete Test user Account. And tear down the Browser instance.
>> 
>> # End of Tests
>> 
>> Thanks,
>> ...Parth
>> 
>> 
>> This addresses bug CLOUDSTACK-1180.
>> 
>> 
>> Diffs
>> -
>> 
>>  test/selenium/ReadMe.txt PRE-CREATION  
>> test/selenium/lib/Global_Locators.py PRE-CREATION  
>> test/selenium/lib/__init__.py PRE-CREATION  
>> test/selenium/lib/initialize.py PRE-CREATION  
>> test/selenium/smoke/Login_and_Accounts.py PRE-CREATION  
>> test/selenium/smoke/Service_Offering.py PRE-CREATION  
>> test/selenium/smoke/TemplatesAndISO.py PRE-CREATION  
>> test/selenium/smoke/VM_lifeCycle.py PRE-CREATION  
>> test/selenium/smoke/main.py PRE-CREATION
>> 
>> Diff: https://reviews.apache.org/r/9336/diff/
>> 
>> 
>> Testing
>> ---
>> 
>> Tested with network refactor branch.
>> 
>> 
>> Thanks,
>> 
>> Parth Jagirdar
> 

Re: devcloud-kvm questions

[Marcus Sorensen]

What platform is the host running? Did you need to change the libvirt
xml file at all? It does sound like it can't access the disk in the
VM, or having a hard time doing so, or something like that.

On Fri, Feb 15, 2013 at 3:33 AM, Dave Cahill  wrote:
> Sounds good, thanks Marcus. I'll try the new image tomorrow.
>
> From investigations today, it looks like the issues I'm having with
> devcloud-kvm are more related to a general nested virtualization issue
> (maybe related to the baremetal machine I'm using?) rather than anything
> CloudStack-specific.
>
> My devcloud-kvm VM appears to have inherited the properties necessary for
> KVM virtualization:
>
> [root@devcloud-kvm ~]# lsmod | grep kvm
> kvm_intel  52762  3
> kvm   312245  1 kvm_intel
>
> However, when I run VMs with KVM, it either stalls on the SeaBIOS prompt as
> mentioned below, or at best, kernel panics with a message like "Kernel
> panic - not syncing: No init found. Try passing init= option to kernel."
>
> Not sure what my next step is, but thought I'd let you know what I found in
> case you have any inspiration!
>
> Thanks,
> Dave.
>
>
> On Fri, Feb 15, 2013 at 1:56 PM, Marcus Sorensen wrote:
>
>> So, I just ran through the install instructions and found the issues.
>> I'll be updating the images and instructions tomorrow.
>>
>> Here are some things I did:
>>
>> yum erase cloud-*
>> rm -rf /usr/share/cloud/
>> rm -rf /var/lib/cloud/
>> rm -rf /var/cache/cloud/
>> rm -rf /tmp/cloud/
>> rm -rf /etc/cloud/
>> rm -rf /var/log/cloud
>> rm -rf /var/run/cloud
>>
>> virsh pool-list
>> virsh pool-destroy 
>> virsh pool-undefine 
>>
>> edit /etc/passwd, /etc/shadow, /etc/group and remove cloud user/group
>>
>> This gets rid of all of the old paths and installations. Now I followed
>> the doc:
>>
>> git clone https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
>>
>> cd incubator-cloudstack/packaging/centos63
>> ./package.sh
>> cd ../../dist/rpmbuild/RPMS/x86_64
>> rpm -Uvh cloudstack*
>> cloudstack-setup-databases cloud:password@localhost --deploy-as root
>> cd /root/incubator-cloudstack
>> ** new command: mysql < tools/devcloud-kvm/devcloud-kvm.sql
>> cloudstack-setup-management
>> ** had to go into UI and set up integration port, then 'service
>> cloudstack-management restart' will move this to devcloud-kvm.sql
>>
>> #set up marvin and auto-deploy test advanced zone (optional)
>> mvn -P developer,systemvm clean install
>> python tools/marvin/marvin/deployDataCenter.py -i
>> tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>>
>> On Thu, Feb 14, 2013 at 7:03 PM, Dave Cahill  wrote:
>> > Awesome, thanks Marcus!
>> >
>> > On Fri, Feb 15, 2013 at 10:59 AM, Marcus Sorensen > >wrote:
>> >
>> >> I'll take a look. I was in the process this afternoon of removing the
>> old
>> >> packaging from devcloud-kvm and replacing it with the new. Ill push the
>> new
>> >> image tomorrow. 4.1 as it stands now works for me on a fresh install
>> >> though.
>> >> On Feb 14, 2013 6:41 PM, "Dave Cahill"  wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > I've been working on getting devcloud-kvm up and running using master,
>> >> and
>> >> > I've hit a few issues - most were due to recent changes in master and
>> are
>> >> > fixed now thanks to help from Rohit and Marcus. By the way, I should
>> note
>> >> > that the devcloud-kvm docs on the wiki are really great - couldn't
>> have
>> >> > gotten this far without them!
>> >> >
>> >> > *Remaining issue:*
>> >> > * System VMs don't launch
>> >> > Using the stock devcloud-kvm image and instructions at [1], system VMs
>> >> get
>> >> > launched, but the agent can't reach them over SSH (Control /
>> link-local
>> >> > network), so they go into a launch-destroy-relaunch cycle.
>> >> >
>> >> > When I connect to the system VMs in VNC, I see:
>> >> >
>> >> > SeaBIOS (version seabios-0.6.1.2-19.e16)
>> >> >
>> >> > gPXE (http://etherboot.org) - 00:03.0 C900 PCI2.10 PnP BBS
>> PMM0620@10C900
>> >> > Press Ctrl-B to configure gPXE (PCI 00:03.0)...
>> >> >
>> >> > I tried making a few tweaks to the libvirt XML for the system VMs and
>> >> > relaunching them using the tweaked XML, but to little effect - as far
>> as
>> >> I
>> >> > can see, it's as though the system VMs aren't recognizing the attached
>> >> > disks. Anyone have any hints? Could this be related to Rohit's
>> "[BLOCKER]
>> >> > SystemVMs come up but don't have agent running" thread?
>> >> >
>> >> > *Fixed issues:*
>> >> > * No logs from agent
>> >> > Fix for now with cp /etc/cloudstack/agent/log4j{-cloud,}.xml
>> >> > * Paused logs on management server when running via jetty
>> >> > Fix for now with cp
>> >> >
>> >> >
>> >>
>> client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/log4j{-cloud,}.xml
>> >> > * console-proxy directory moved, caused maven builds to fail
>> >> > Fixed by Rohit in master
>> >> > * console-proxy directory moved, devcloud-kvm's custom
>> >> > /etc/init.d/cloud-agent is now incorrect
>> >> > Changed this line to refle

Re: Review Request: Support for full clones on ESX for Cloudstack (CS-670)

[Venkata Siva Vijayendra Bhamidipati]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9439/
---

(Updated Feb. 15, 2013, 8:47 p.m.)


Review request for cloudstack and Kelven Yang.


Changes
---

Making db related changes to remove DDL statement from create-schema.sql


Description
---

Please find the diffs for full clone guest VM support for ESX on Cloudstack. 
The diffs do not include unit tests yet. The tests will be uploaded at the 
earliest.


This addresses bug CS-670.


Diffs
-

  server/src/com/cloud/vm/UserVmManagerImpl.java 19887ff 
  server/test/com/cloud/vm/dao/UserVmCloneSettingDaoImplTest.java PRE-CREATION 
  server/test/com/cloud/vm/dao/UserVmCloneSettingDaoTestConfiguration.java 
PRE-CREATION 
  server/test/resources/CloneSettingDaoTestContext.xml PRE-CREATION 

Diff: https://reviews.apache.org/r/9439/diff/


Testing
---

Manual Testing
==

Creation of guest VMs when the global flag vmware.create.full.clone is set to 
its default value of false will create those guest VMs as linked clones 
(current default behavior without these changes).
Creation of guest VMs when the global flag vmware.create.full.clone is set to 
true will create those guest VMs as full clones.
Appropriate entries are created in the user_vm_clone_setting table of the cloud 
schema to reflect the clone type of the VMs.
Linked clones and full clones can reside together in the same cluster and work 
as expected.


Thanks,

Venkata Siva Vijayendra Bhamidipati

Re: Review Request: Support for full clones on ESX for Cloudstack (CS-670)

[Venkata Siva Vijayendra Bhamidipati]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9439/
---

(Updated Feb. 15, 2013, 8:45 p.m.)


Review request for cloudstack and Kelven Yang.


Changes
---

Attempting to re-upload patch 3. Hopefully it will be readable via reviewboard. 
If not, please refer to the attached file.


Description
---

Please find the diffs for full clone guest VM support for ESX on Cloudstack. 
The diffs do not include unit tests yet. The tests will be uploaded at the 
earliest.


This addresses bug CS-670.


Diffs (updated)
-

  server/src/com/cloud/vm/UserVmManagerImpl.java 19887ff 
  server/test/com/cloud/vm/dao/UserVmCloneSettingDaoImplTest.java PRE-CREATION 
  server/test/com/cloud/vm/dao/UserVmCloneSettingDaoTestConfiguration.java 
PRE-CREATION 
  server/test/resources/CloneSettingDaoTestContext.xml PRE-CREATION 

Diff: https://reviews.apache.org/r/9439/diff/


Testing
---

Manual Testing
==

Creation of guest VMs when the global flag vmware.create.full.clone is set to 
its default value of false will create those guest VMs as linked clones 
(current default behavior without these changes).
Creation of guest VMs when the global flag vmware.create.full.clone is set to 
true will create those guest VMs as full clones.
Appropriate entries are created in the user_vm_clone_setting table of the cloud 
schema to reflect the clone type of the VMs.
Linked clones and full clones can reside together in the same cluster and work 
as expected.


Thanks,

Venkata Siva Vijayendra Bhamidipati

[jira] [Created] (CLOUDSTACK-1304) "mvn -pl :cloud-client-ui jetty:run" strips permission of files in script/

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-1304:
---

 Summary: "mvn  -pl :cloud-client-ui jetty:run" strips permission 
of files in script/
 Key: CLOUDSTACK-1304
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1304
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.1.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.1.0


"mvn  -pl :cloud-client-ui jetty:run" calls ant task  to copy files under 
script/ to "${basedir}/target/generated-webapp/WEB-INF/classes/scripts">

it will strip all permission on files to default system permission which erases 
execution bit on script. the reason is 

"Unix Note: File permissions are not retained when files are copied; they end 
up with the default UMASK permissions instead. This is caused by the lack of 
any means to query or set file permissions in the current Java runtimes. If you 
need a permission-preserving copy function, use  
instead."
http://ant.apache.org/manual/Tasks/copy.html


this issue will prevent mgmt server executes any shell script due to lacking of 
execution permission on script

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [DISCUSS] Graduation to a TLP?

[Joe Brockmeier]

On Fri, Feb 15, 2013, at 02:08 PM, Mike Tutkowski wrote:
> Can I ask what may be a silly question about voting?  :)

That's not a silly question. 
 
> When these votes are put out there, who can vote?  Just committers or
> anyone participating in the community?

Anyone can vote, but only some of the votes are binding. If you see a
vote taking place that you feel you have a stake in / an opinion on, you
should feel free to vote anyway.

Why? Even if your vote isn't binding, it may be useful to understand how
folks in the community think about something even if their vote isn't
binding. 

I believe it's PPMC votes that are binding for the vote held within the
podling, btw. But please don't let that stop you from weighing in if you
wish to.


Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: [DISCUSS] Graduation to a TLP?

[David Nalley]

On Fri, Feb 15, 2013 at 3:08 PM, Mike Tutkowski
 wrote:
> Can I ask what may be a silly question about voting?  :)
>
> When these votes are put out there, who can vote?  Just committers or
> anyone participating in the community?
>
> Thanks!
>

https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html

Generally speaking  - anyone can vote.
On technical matters, only committers votes are binding.
In other matters (releases, adopting new codebases, etc) (P)PMC votes
are binding.

--David

Re: Question about deployVirtualMachine API Call

[Mike Tutkowski]

That helps a lot - thanks!


On Fri, Feb 15, 2013 at 1:11 PM, Prachi Damle wrote:

> -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 API
> Call.
>
> I have a couple questions about this:
>
> 1) Is it as simple as adding another GET parameter such as the following:
> userdata=mydata?
>
> >> Yes. Your data should be base64 encoded.
>
> 2) How can I retrieve this userdata field later from the OS running in the
> VM that was deployed earlier?
>
> >> This might help.
> http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/user-data-and-meta-data.html
>
> Thanks!
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Re: Feature Discuss Emails Tag Update

[Alex Huang]

The convention was discuss for feature requirement gathering and proposal for 
the actual spec.



--Alex



 Original message 
From: Joe Brockmeier 
Date:
To: cloudstack-dev@incubator.apache.org
Subject: Re: Feature Discuss Emails Tag Update


On Fri, Feb 15, 2013, at 01:33 PM, Alex Huang wrote:
> Along with too many tags, I also don't like the idea of a tag being too
> general.  For example, [DISCUSS] is being used in so many types of topics
> now, I'm not really sure how it's different from an email to the list
> with no tags.
>
> Maybe we should say, if you are proposing a feature then you use [RFC]?
> Is that any different from [DISCUSS]?  Discuss:P

I thought that was [PROPOSAL] for RFCs?

Maybe the [DISCUSS] tag is being overused, though? Not sure. Are there
any specific examples that you think would have been fine without it?
(Feel free to use me as an example, I can take it. :-))

Best,

jzb
--
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

RE: Question about deployVirtualMachine API Call

[Prachi Damle]

-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 API Call.

I have a couple questions about this:

1) Is it as simple as adding another GET parameter such as the following:
userdata=mydata?

>> Yes. Your data should be base64 encoded.

2) How can I retrieve this userdata field later from the OS running in the VM 
that was deployed earlier?

>> This might help. 
>> http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/user-data-and-meta-data.html

Thanks!

--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: [DISCUSS] Graduation to a TLP?

[Mike Tutkowski]

Can I ask what may be a silly question about voting?  :)

When these votes are put out there, who can vote?  Just committers or
anyone participating in the community?

Thanks!


On Wed, Feb 13, 2013 at 2:50 PM, Ahmad Emneina  wrote:

> +1
>
> Apache cloudstack sounds Excellent!
>
>
> On Wed, Feb 13, 2013 at 10:55 AM, Rohit Yadav  wrote:
>
> > I agree with all the comments, from my side I think we're more mature
> > now than we were more than half year ago.
> >
> > We've two releases so far, third one to happen next. We've our release
> > timelines figured out. We've pretty active development, so many
> > checkins/day, a tons of emails on ML, comments/discussions/patches/fun
> > on jira, RB, irc. We've so many users posting their feedback, bug
> > reports and whatnot. We've seen an international conference in CCC12,
> > a lot more meetups around the world, blogs, tweets, and even a book in
> > an non-english language; not to mention real world deployments and
> > those awesome IRC chats between sysadmins, users and developers, and
> > companies who are contributing developer resources to the project.
> > We've regular irc meetings, our ppmc can tackle any project issue, we
> > saw licensing issues get resolved for example and they know how to run
> > the project and work with the community. Our committers are doing
> > great job at collaboratively working with each other, reviewing codes,
> > discussing things on ML, irc and whatnot. I think we're learning more
> > and more and we should rely less on our mentors as we're maturing, I
> > say we're ready.
> >
> > +1 cloudstack.apache.org would just look awesome-er :)
> >
> > Regards.
> >
> > On Wed, Feb 13, 2013 at 10:54 PM, David Nalley  wrote:
> > > On Wed, Feb 13, 2013 at 10:49 AM, Sebastien Goasguen  >
> > wrote:
> > >>
> > >> On Feb 13, 2013, at 4:43 PM, David Nalley  wrote:
> > >>
> > >>> On Wed, Feb 13, 2013 at 10:07 AM, Chip Childers
> > >>>  wrote:
> >  On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote:
> > > On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers
> > >  wrote:
> > >> Hi all,
> > >>
> > >> I started a conversation within cloudstack-private@i.a.o about
> the
> > >> prospect of graduation from the incubator, and have received
> > positive
> > >> reactions from everyone that replied.
> > >>
> > >> I wanted to kick off the discussion here on the public list, to
> see
> > if
> > >> anyone has any concerns or objections to us starting down the path
> > of
> > >> trying to graduate?
> > >>
> > >> My general impression is that we have come a long way as a
> community
> > >> since CloudStack entered the incubator. While there are still
> rough
> > edges
> > >> for us to work through over time, we are dealing with our problems
> > quite
> > >> well as a community. The simple reason that I believe we are in a
> > >> position to ask to graduate, is that we are no longer getting
> value
> > from
> > >> the incubation process!  That's a good thing, because it means
> that
> > we
> > >> have managed to learn quite a bit about the ASF processes, rules,
> > >> methods and preferences.
> > >>
> > >> Thoughts, comments, discussion?
> > >>
> > >> Are you thinking to do this prior to 4.2 release ?
> > >>
> > >> With my individual hat on, I think it might be best to put up a strong
> > 4.2 release and then vote for graduation. It would strengthen our case.
> > >>
> > >
> > >
> > > So I had similar thoughts originally and actually meant 4.2.
> > >
> > > Here is what changed my mind:
> > >
> > > I don't see us actively receiving any benefit from continuing in
> > > incubation. We are far from perfect, but the project seems to be
> > > policing itself. so I am not seeing a huge incentive to staying.
> > >
> > > There are also some downsides to remaining in incubation. First
> > > there's the label 'incubation' that follows almost everything we do,
> > > and is potentially off-putting to potential community members. Second
> > > as a community there are a number of things we can't do for ourselves,
> > > and thus have to ask permission or for help - this includes votes on
> > > releases, creating new user accounts, etc. I think of this as the
> > > overhead of being in the incubator.
> > >
> > > And finally, while this isn't really a big deal from our perspective,
> > > we have 8 mentors, and their continued focus on us means more of their
> > > time they can't focus on other incubating projects. And given our -dev
> > > list volume, I imagine us to be a handful to keep up with.
> > >
> > > --David
> >
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

RE: [ACS41] Yet another reviewboard reminder... for both committers and contributors.

[Animesh Chaturvedi]

Folks

I have sent emails on over 30 issues from review board this week and as 
community we responded to 2/3 rd of them which is good but can be better. We 
were able to knock off only a handful of them. Out of the ones that were 
responded to many of them are awaiting action from reviewers. If you were 
called out please respond to your reviews and help us close pending reviews.

We have 33 pending reviews in review board at this time

Animesh



> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Monday, February 11, 2013 11:24 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [ACS41] Yet another reviewboard reminder... for both committers
> and contributors.
> 
> Folks
> 
> I have sent a number of reminder emails for some of the review board items
> that have been pending for a while. Please attend to them at the earliest . We
> are running at 50+ items in review board. If you are a committer I request you
> knock off 1-2 reviews per week
> 
> Animesh
> 
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Tuesday, January 29, 2013 9:18 AM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: [ACS41] Yet another reviewboard reminder... for both
> > committers and contributors.
> >
> > Hi all (and specifically people that were listed as "maintainers" of
> > certain code modules),
> >
> > We need committer help in getting the community contributions
> > currently in reviewboard (as well as some that we expect to show up in
> > the next day or so) reviewed and committed as soon as possible.
> >
> > If you are a "maintainer", or simply feel that you have enough
> > knowledge to get through one or more of these reviews, PLEASE take
> > some time to help clear out the board.
> >
> > Based on our agreed upon schedule, we need everything into master (or
> > javelin) by EOD Thursday.
> >
> > For those of you that have code you want to be reviewed, but have not
> > yet submitted, it needs to get in ASAP.  Otherwise, there's no chance
> > that someone will have the time to review and commit before we cut the
> release branch.
> >
> > -chip

[jira] [Resolved] (CLOUDSTACK-289) 3.0.5

[sebastien goasguen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sebastien goasguen resolved CLOUDSTACK-289.
---

Resolution: Invalid
  Assignee: sebastien goasguen  (was: Radhika Nair)

There has never been an ACS 3.0.5 release.

> 3.0.5
> -
>
> Key: CLOUDSTACK-289
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-289
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: pre-4.0.0
> Environment: VMware RHEL 6/5
>Reporter: Matt Mullins
>Assignee: sebastien goasguen
> Fix For: 4.1.0
>
>
> Section 2.2. Upgrade from 2.2.x to 3.0.5
> Item 4.d.
> In an environment coming straight from 2.2.14 to 3.0.5 requires that not only 
> is the new 3.0.5 template, but also the 3.0.0 (Acton) template as well. Both 
> have to be loaded before the upgrade can happen otherwise it will fail. 
> Taken from the 3.0.2 release notes upgrade. 
> VMware:
>  Name: systemvm-vmware-3.0.0
>  Display Text: systemvm-vmware-3.0.00
>  URL: http://download.cloud.com/templates/acton/acton-systemvm-02062012.ova
>  Zone: Choose the zone where this hypervisor is used
>  OS Type: Debian GNU/Linux 5.0 (32-bit)
>  Hypervisor: VMware
>  Format: OVA
>  Password Enabled: no
>  Public: no
>  Featured: no

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [MERGE]Storage refactor branch

[Wido den Hollander]

On 02/15/2013 08:03 PM, Edison Su wrote:




-Original Message-
From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
Sent: Friday, February 15, 2013 6:39 AM
To: cloudstack-dev@incubator.apache.org
Cc: John Burwell  (jburw...@basho.com); Mike
Tutkowski (mike.tutkow...@solidfire.com)
Subject: RE: [MERGE]Storage refactor branch

Hey Edison,

Thanks for the update


-Original Message-
From: Edison Su [mailto:edison...@citrix.com]
Sent: Friday, February 15, 2013 12:13 AM
To: cloudstack-dev@incubator.apache.org
Cc: John Burwell  (jburw...@basho.com); Mike
Tutkowski (mike.tutkow...@solidfire.com)
Subject: [MERGE]Storage refactor branch

Hi All,
  Here is the update from storage refactor branch since last week:

1.   clean/hook up snapshot into new storage framework, separate taking
snapshot and backup snapshot. Add a snapshotstrategy interface for
people want to change or replace how snapshot is processed in
cloudstack. Current snapshot code is little bit hacky, welcome to replace it

for your need.

   Since last week I created storage_refactor branch, seems no
objection for what I am doing, so I want to merge the branch into
master, by end of this week, due to the following reasons:
  Maintain such big patch(more than 20K) outside of master,
touch all the storage code, is not an easy task.
  After merge into master, other developers who developing
storage features can work on master directly, thus I don't need to
rebase the branch regularly.
   About test, I only tested basic features, like, stop/start vm,
attach/detach volumes, take snapshots in devcloud. For sure, I'll
break something. The more test from other people, will help to me to
stabilize the code. About unit test, I have some unit test and
integration test for devcloud, but both of them needs database and
devcloud environment, so they are disabled by default and unit test
themselves are broken also. I'll write more tests during the stabilization.


I understand the need to merge into master, it is a serious pain to keep
updating the branch with that latest state of master. However this testing


Thanks for understand the painful of rebaseing such big patch. There is another 
reason I want to merge this branch into master ASAP: all the new storage 
features are depended this branch: like zone-wide storage, make nfs secondary 
storage as optional, re-write s3/swift integration etc. Let's get it merged, 
adding more awesome features:)



I'm waiting on starting with the new RBD features until this is merged in.

I also understand what a hassle this is, got the same when developing 
the original RBD without having commit rights.


Wido


concerns me a lot, we all agreed that we would focus on automated testing
both on the unittest level and on the functional level. This is the first merge
request since we had the last discussion on testing (related to merging the
javelin and other branches). The clear consensus was that commits would
have to be accompanied by unittests (at least for the changed pieces of code)
and preferable some automated functional test.

Considering that, I think that a merge is not the right this to do at the
moment. Instead of merging into master and then fixing stuff, we should
focus on adding testing to this branch so we can merge a well-tested unit
later. Notice my use of 'we' here, we all said focus on testing, so we all 
should
help out. Unfortunately I'm pretty busy with packaging and the $dayjob, but
if you have something I can help you with regarding setting up unittests feel
free to let me know. You already mentioned that you have some, but the
databases need to be mocked?

It would be great if you could spend some time to details what tests you
have in place, so we can fix those. With the help of the cobertura report we
can figure out where the risks are. Prassana and myself are also working on
the automated test framework, so if you have some marvin tests, we can
help to automate them.


My branch is not a feature branch, while other features are depended on it. I 
didn't add any new feature on the branch, all the existing marvin automated 
tests should work. Instead of testing and fixing on my branch then merge, is it 
better to test and fix on master after the merge, using existing marvin test?
Again, the rebase to master is painful for such branch.




Anybody else willing to help put in some tests into the storage_refactor
branch?

Cheers,

Hugo

[jira] [Updated] (CLOUDSTACK-1303) Ipv6 - java.lang.NullPointerException when executing listnetworks() and deployVirtualMachine() after extending the Ipv4 range of a dual stack network.

[Sangeetha Hariharan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangeetha Hariharan updated CLOUDSTACK-1303:


Description: 
Ipv6 - java.lang.NullPointerException when executing listnetworks() and 
deployVirtualMachine() after extending the Ipv4 range of a dual stack network.

Steps to reproduce the problem:

Create dual stack network , by specifying both ipv4 and ipv6 params.

Deploy Vms and exhaust all the ipv4 abd ipv6 params.

Attempting to deploy Vms fail.

Extend IPV4 range of this network.

After this trying to listNetwork fails:

GET 
command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067
 530 null

Following is management server logs:

2013-02-15 19:15:48,447 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) 
===START===  10.217.252.59 -- GET  
command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067
2013-02-15 19:15:48,452 DEBUG [cloud.user.AccountManagerImpl] 
(catalina-exec-17:null) Access granted to Acct[2-admin] to Domain:1/ by 
DomainChecker
2013-02-15 19:15:48,467 ERROR [cloud.api.ApiDispatcher] (catalina-exec-17:null) 
Exception while executing ListNetworksCmd:
java.lang.NullPointerException
at com.cloud.utils.net.NetUtils.countIp6InRange(NetUtils.java:1219)
at 
com.cloud.network.NetworkModelImpl.isIP6AddressAvailableInVlan(NetworkModelImpl.java:556)
at 
com.cloud.network.NetworkModelImpl.isIP6AddressAvailableInNetwork(NetworkModelImpl.java:544)
at 
com.cloud.network.NetworkModelImpl.canUseForDeploy(NetworkModelImpl.java:524)
at com.cloud.api.ApiDBUtils.canUseForDeploy(ApiDBUtils.java:842)
at 
com.cloud.api.ApiResponseHelper.createNetworkResponse(ApiResponseHelper.java:3183)
at 
com.cloud.api.commands.ListNetworksCmd.execute(ListNetworksCmd.java:156)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:168)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:540)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:424)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:312)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at 
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-02-15 19:15:48,469 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) 
===END===  10.217.252.59 -- GET  
command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067

Same exception is also seen when deploying Vms:
2013-02-15 19:28:59,914 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
===START===  10.217.252.59 -- GET  
command=deployVirtualMachine&zoneId=fa60468a-c5d1-42a2-92e8-23
cc5a62b935&templateId=2b2faf4e-12e6-4c94-9bf5-86475e8c&hypervisor=KVM&serviceOfferingId=ac380d95-8016-4761-bc14-e6a764a15b51&networkIds=5f53c588-2324-4f4a-900b-a62e08fd77
e6&displayname=small-extend-4&name=small-extend-4&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D
2013-02-15 19:28:59,934 DEBUG [cloud.network.NetworkModelImpl] 
(catalina-exec-12:null) Service SecurityGroup is not supported in the network 
id=208
2013-

Re: Feature Discuss Emails Tag Update

[Joe Brockmeier]

On Fri, Feb 15, 2013, at 01:33 PM, Alex Huang wrote:
> Along with too many tags, I also don't like the idea of a tag being too
> general.  For example, [DISCUSS] is being used in so many types of topics
> now, I'm not really sure how it's different from an email to the list
> with no tags.
> 
> Maybe we should say, if you are proposing a feature then you use [RFC]? 
> Is that any different from [DISCUSS]?  Discuss:P

I thought that was [PROPOSAL] for RFCs?

Maybe the [DISCUSS] tag is being overused, though? Not sure. Are there
any specific examples that you think would have been fine without it?
(Feel free to use me as an example, I can take it. :-))

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

[jira] [Commented] (CLOUDSTACK-1303) Ipv6 - java.lang.NullPointerException when executing listnetworks().

[Sangeetha Hariharan (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579444#comment-13579444
 ] 

Sangeetha Hariharan commented on CLOUDSTACK-1303:
-

mysql> select * from vlan;
++--+-++-++---+---+-++++-+
| id | uuid | vlan_id | vlan_gateway   | 
vlan_netmask| ip6_gateway| ip6_cidr  | description  
 | ip6_range   | vlan_type  | 
data_center_id | network_id | physical_network_id |
++--+-++-++---+---+-++++-+
|  1 | a6efa79f-781d-4b2d-92ac-1a9dd2b7771e | 1363| 10.223.136.193 | 
255.255.255.192 | NULL   | NULL  | 
10.223.136.194-10.223.136.210 | NULL
| VirtualNetwork |  1 |200 | 200 |
|  4 | f0fb8709-996c-4050-b860-55bfe717fb83 | 1371| 10.223.137.65  | 
255.255.255.192 | fc00:3:1371::1 | fc00:3:1371::1/64 | 
10.223.137.66-10.223.137.90   | fc00:3:1371::2-fc00:3:1371::::: 
| DirectAttached |  1 |206 | 200 |
|  5 | 5ea0e254-fe59-4fd0-a396-6305c7341f57 | 1370| 10.223.137.1   | 
255.255.255.224 | fc00:3:1370::1 | fc00:3:1370::1/64 | 
10.223.137.2-10.223.137.4 | fc00:3:1370::2-fc00:3:1370::4   
| DirectAttached |  1 |208 | 200 |
|  6 | 88d5c3d8-98aa-4681-98a2-fa0e4ed41eb9 | 1370| 10.223.137.1   | 
255.255.255.224 | NULL   | NULL  | 
10.223.137.5-10.223.137.7 | NULL
| DirectAttached |  1 |208 | 200 |
++--+-++-++---+---+-++++-+
4 rows in set (0.00 sec)


> Ipv6 - java.lang.NullPointerException when executing listnetworks(). 
> -
>
> Key: CLOUDSTACK-1303
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1303
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Latest build from network refactor branch.
>Reporter: Sangeetha Hariharan
>Assignee: Sheng Yang
> Fix For: 4.1.0
>
>
> Ipv6 - java.lang.NullPointerException when executing listnetworks(). 
> Steps to reproduce the problem:
> Create dual stack network , by specifying both ipv4 and ipv6 params.
> Deploy Vms and exhaust all the ipv4 abd ipv6 params.
> Attempting to deploy Vms fail.
> Extend IPV4 range of this network.
> After this trying to listNetwork fails:
> GET 
> command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067
>  530 null
> Following is management server logs:
> 2013-02-15 19:15:48,447 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) 
> ===START===  10.217.252.59 -- GET  
> command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067
> 2013-02-15 19:15:48,452 DEBUG [cloud.user.AccountManagerImpl] 
> (catalina-exec-17:null) Access granted to Acct[2-admin] to Domain:1/ by 
> DomainChecker
> 2013-02-15 19:15:48,467 ERROR [cloud.api.ApiDispatcher] 
> (catalina-exec-17:null) Exception while executing ListNetworksCmd:
> java.lang.NullPointerException
> at com.cloud.utils.net.NetUtils.countIp6InRange(NetUtils.java:1219)
> at 
> com.cloud.network.NetworkModelImpl.isIP6AddressAvailableInVlan(NetworkModelImpl.java:556)
> at 
> com.cloud.network.NetworkModelImpl.isIP6AddressAvailableInNetwork(NetworkModelImpl.java:544)
> at 
> com.cloud.network.NetworkModelImpl.canUseForDeploy(NetworkModelImpl.java:524)
> at com.cloud.api.ApiDBUtils.canUseForDeploy(ApiDBUtils.java:842)
> at 
> com.cloud.api.ApiResponseHelper.cr

[jira] [Comment Edited] (CLOUDSTACK-1303) Ipv6 - java.lang.NullPointerException when executing listnetworks().

[Sangeetha Hariharan (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579444#comment-13579444
 ] 

Sangeetha Hariharan edited comment on CLOUDSTACK-1303 at 2/15/13 7:34 PM:
--

DB entries after extending vlan:

mysql> select * from vlan;
++--+-++-++---+---+-++++-+
| id | uuid | vlan_id | vlan_gateway   | 
vlan_netmask| ip6_gateway| ip6_cidr  | description  
 | ip6_range   | vlan_type  | 
data_center_id | network_id | physical_network_id |
++--+-++-++---+---+-++++-+
|  1 | a6efa79f-781d-4b2d-92ac-1a9dd2b7771e | 1363| 10.223.136.193 | 
255.255.255.192 | NULL   | NULL  | 
10.223.136.194-10.223.136.210 | NULL
| VirtualNetwork |  1 |200 | 200 |
|  4 | f0fb8709-996c-4050-b860-55bfe717fb83 | 1371| 10.223.137.65  | 
255.255.255.192 | fc00:3:1371::1 | fc00:3:1371::1/64 | 
10.223.137.66-10.223.137.90   | fc00:3:1371::2-fc00:3:1371::::: 
| DirectAttached |  1 |206 | 200 |
|  5 | 5ea0e254-fe59-4fd0-a396-6305c7341f57 | 1370| 10.223.137.1   | 
255.255.255.224 | fc00:3:1370::1 | fc00:3:1370::1/64 | 
10.223.137.2-10.223.137.4 | fc00:3:1370::2-fc00:3:1370::4   
| DirectAttached |  1 |208 | 200 |
|  6 | 88d5c3d8-98aa-4681-98a2-fa0e4ed41eb9 | 1370| 10.223.137.1   | 
255.255.255.224 | NULL   | NULL  | 
10.223.137.5-10.223.137.7 | NULL
| DirectAttached |  1 |208 | 200 |
++--+-++-++---+---+-++++-+
4 rows in set (0.00 sec)


  was (Author: sangeethah):
mysql> select * from vlan;
++--+-++-++---+---+-++++-+
| id | uuid | vlan_id | vlan_gateway   | 
vlan_netmask| ip6_gateway| ip6_cidr  | description  
 | ip6_range   | vlan_type  | 
data_center_id | network_id | physical_network_id |
++--+-++-++---+---+-++++-+
|  1 | a6efa79f-781d-4b2d-92ac-1a9dd2b7771e | 1363| 10.223.136.193 | 
255.255.255.192 | NULL   | NULL  | 
10.223.136.194-10.223.136.210 | NULL
| VirtualNetwork |  1 |200 | 200 |
|  4 | f0fb8709-996c-4050-b860-55bfe717fb83 | 1371| 10.223.137.65  | 
255.255.255.192 | fc00:3:1371::1 | fc00:3:1371::1/64 | 
10.223.137.66-10.223.137.90   | fc00:3:1371::2-fc00:3:1371::::: 
| DirectAttached |  1 |206 | 200 |
|  5 | 5ea0e254-fe59-4fd0-a396-6305c7341f57 | 1370| 10.223.137.1   | 
255.255.255.224 | fc00:3:1370::1 | fc00:3:1370::1/64 | 
10.223.137.2-10.223.137.4 | fc00:3:1370::2-fc00:3:1370::4   
| DirectAttached |  1 |208 | 200 |
|  6 | 88d5c3d8-98aa-4681-98a2-fa0e4ed41eb9 | 1370| 10.223.137.1   | 
255.255.255.224 | NULL   | NULL  | 
10.223.137.5-10.223.137.7 | NULL
| DirectAttached |  1 |208 | 200 |
++--+-++-++---+---+-++++-+
4 rows i

Re: Review Request: Scripts for Selenium UI automation.

[Kelceydamage@bbits]

I'm really behind on what's going on here. What is the purpose behind the 
Selenium and Python UI automation?

This seems similar to the .net/IronPython work I was doing and the various 
Python API Wrappers.

Could you give me some more background, or perhaps so links with details as to 
the scope and purpose?

Thanks

Sent from my iPhone

On Feb 15, 2013, at 11:03 AM, Parth Jagirdar  wrote:

> John & Kelcey,
> 
> I have uploaded basic description for what scripts do.
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+using+Selenium+and+Python
> 
> Please review and let me know if any compliance issues.
> I can fix and resubmit the scripts.
> 
> 
> Thanks,
> .. Parth
> 
> 
> -Original Message-
> From: Animesh Chaturvedi 
> Sent: Wednesday, February 13, 2013 7:13 PM
> To: Parth Jagirdar; Kelcey Jamison-Damage; John Kinsella
> Cc: cloudstack
> Subject: RE: Review Request: Scripts for Selenium UI automation.
> 
> Kelcey, john
> 
> Please review Parth's patch
> 
>> -Original Message-
>> From: Parth Jagirdar [mailto:nore...@reviews.apache.org] On Behalf Of 
>> Parth Jagirdar
>> Sent: Wednesday, February 06, 2013 1:06 PM
>> To: Kelcey Jamison-Damage; John Kinsella
>> Cc: cloudstack; Parth Jagirdar
>> Subject: Re: Review Request: Scripts for Selenium UI automation.
>> 
>> 
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/9336/
>> ---
>> 
>> (Updated Feb. 6, 2013, 9:05 p.m.)
>> 
>> 
>> Review request for cloudstack, John Kinsella and Kelcey Jamison-Damage.
>> 
>> 
>> Description
>> ---
>> 
>> These scripts will execute following test cases on UI through Firefox. 
>> (Test Cases taken from :: 
>> http://wiki.cloudstack.org/display/QA/Manual+BVT)
>> 
>> 
>> Login Admin user to UI.
>> Create an Account name Test.
>> Logout Admin user.
>> Login Test user.
>> 
>> Add a new Disk Offering.
>> Edit this Disk offering.
>> Delete this Disk offering.
>> 
>> Add a new Compute Offering.
>> Edit this Compute offering.
>> Delete this Compute offering.
>> 
>> Logout Test user.
>> Login Admin user.
>> Delete Test user Account. And tear down the Browser instance.
>> 
>> # End of Tests
>> 
>> Thanks,
>> ...Parth
>> 
>> 
>> This addresses bug CLOUDSTACK-1180.
>> 
>> 
>> Diffs
>> -
>> 
>>  test/selenium/ReadMe.txt PRE-CREATION
>>  test/selenium/lib/Global_Locators.py PRE-CREATION
>>  test/selenium/lib/__init__.py PRE-CREATION
>>  test/selenium/lib/initialize.py PRE-CREATION
>>  test/selenium/smoke/Login_and_Accounts.py PRE-CREATION
>>  test/selenium/smoke/Service_Offering.py PRE-CREATION
>>  test/selenium/smoke/TemplatesAndISO.py PRE-CREATION
>>  test/selenium/smoke/VM_lifeCycle.py PRE-CREATION
>>  test/selenium/smoke/main.py PRE-CREATION
>> 
>> Diff: https://reviews.apache.org/r/9336/diff/
>> 
>> 
>> Testing
>> ---
>> 
>> Tested with network refactor branch.
>> 
>> 
>> Thanks,
>> 
>> Parth Jagirdar
> 

RE: Feature Discuss Emails Tag Update

[Alex Huang]

Along with too many tags, I also don't like the idea of a tag being too 
general.  For example, [DISCUSS] is being used in so many types of topics now, 
I'm not really sure how it's different from an email to the list with no tags.

Maybe we should say, if you are proposing a feature then you use [RFC]?  Is 
that any different from [DISCUSS]?  Discuss:P

--Alex

RE: [ACS41] Yet another reviewboard reminder... for both committers and contributors.

[Animesh Chaturvedi]

> -Original Message-
> From: Joe Brockmeier [mailto:j...@zonker.net]
> Sent: Wednesday, February 13, 2013 11:35 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ACS41] Yet another reviewboard reminder... for both committers
> and contributors.
> 
> On Wed, Feb 13, 2013, at 12:25 AM, Animesh Chaturvedi wrote:
> > Joe https://reviews.apache.org/r/8180/
> 
> This one should actually be taken off the list for now - apparently it 
> includes a
> number of features that are either not in master or being held for 4.2. In 
> fact,
> I'm going to see about having this broken out into more manageable patches,
> one per feature documented rather than bundling several features that aren't
> all coming in together.

[Animesh>] Yes agreed, Radhika can you take care of this?
> 
> Best,
> 
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

Re: Review Request: Scripts for Selenium UI automation.

[Parth Jagirdar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9336/
---

(Updated Feb. 15, 2013, 7:30 p.m.)


Review request for cloudstack, John Kinsella, Prasanna Santhanam, and Kelcey 
Jamison-Damage.


Description
---

These scripts will execute following test cases on UI through Firefox. (Test 
Cases taken from :: http://wiki.cloudstack.org/display/QA/Manual+BVT)


Login Admin user to UI.
Create an Account name Test.
Logout Admin user.
Login Test user.

Add a new Disk Offering.
Edit this Disk offering.
Delete this Disk offering.

Add a new Compute Offering.
Edit this Compute offering.
Delete this Compute offering.

Logout Test user.
Login Admin user.
Delete Test user Account. And tear down the Browser instance.

# End of Tests

Thanks,
...Parth


This addresses bug CLOUDSTACK-1180.


Diffs
-

  test/selenium/ReadMe.txt PRE-CREATION 
  test/selenium/lib/Global_Locators.py PRE-CREATION 
  test/selenium/lib/__init__.py PRE-CREATION 
  test/selenium/lib/initialize.py PRE-CREATION 
  test/selenium/smoke/Login_and_Accounts.py PRE-CREATION 
  test/selenium/smoke/Service_Offering.py PRE-CREATION 
  test/selenium/smoke/TemplatesAndISO.py PRE-CREATION 
  test/selenium/smoke/VM_lifeCycle.py PRE-CREATION 
  test/selenium/smoke/main.py PRE-CREATION 

Diff: https://reviews.apache.org/r/9336/diff/


Testing
---

Tested with network refactor branch.


Thanks,

Parth Jagirdar

RE: License issue for js file from ui-plugins merge

[Alex Huang]

Yup.  I'm mainly making a case against just emails that says "guys, let's do 
this" or "guys let's not do this".  Emails like that should always be backed by 
items in one of the guideline wikis so people can come back to refer to it.

--Alex

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, February 15, 2013 10:51 AM
> To: Alex Huang
> Cc: cloudstack-dev@incubator.apache.org; Animesh Chaturvedi
> Subject: Re: License issue for js file from ui-plugins merge
> 
> On Feb 15, 2013, at 1:38 PM, Alex Huang  wrote:
> 
> > Chip,
> >
> > We should spell out the expectations because the community has been
> evolving in how it's behave.  It is already difficult for people to follow the
> emails then how can we expect them to follow consensus reach inside those
> emails.  Note I'm not talking about technical consensus.  Those are the
> responsibilities of the topic owner.
> 
> Making it easier to know where to go is a good thing, no doubt. Lets
> all work together on that.  Licensing and adding new dependencies
> should be part of that as well.
> 
> That being said, I'll still state for the record that I don't believe
> that the legal implications of adding code from outside the project
> without discussion has ever been an issue where there is ambiguity.
> Again, lets highlight it wherever we can, but I don't agree with a
> high volume list meaning that the requirement is unclear.
> 
> Perhaps we are talking about two different things here, with your
> point being about the general expectations and mine being very
> specifically about adding any code from outside the project to any
> branch of our repo.  Either way, lets write it down in more places to
> help folks remember.

[jira] [Created] (CLOUDSTACK-1303) Ipv6 - java.lang.NullPointerException when executing listnetworks().

[Sangeetha Hariharan (JIRA)]

Sangeetha Hariharan created CLOUDSTACK-1303:
---

 Summary: Ipv6 - java.lang.NullPointerException when executing 
listnetworks(). 
 Key: CLOUDSTACK-1303
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1303
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.1.0
 Environment: Latest build from network refactor branch.
Reporter: Sangeetha Hariharan
Assignee: Sheng Yang
 Fix For: 4.1.0


Ipv6 - java.lang.NullPointerException when executing listnetworks(). 

Steps to reproduce the problem:

Create dual stack network , by specifying both ipv4 and ipv6 params.

Deploy Vms and exhaust all the ipv4 abd ipv6 params.

Attempting to deploy Vms fail.

Extend IPV4 range of this network.

After this trying to listNetwork fails:

GET 
command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067
 530 null

Following is management server logs:

2013-02-15 19:15:48,447 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) 
===START===  10.217.252.59 -- GET  
command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067
2013-02-15 19:15:48,452 DEBUG [cloud.user.AccountManagerImpl] 
(catalina-exec-17:null) Access granted to Acct[2-admin] to Domain:1/ by 
DomainChecker
2013-02-15 19:15:48,467 ERROR [cloud.api.ApiDispatcher] (catalina-exec-17:null) 
Exception while executing ListNetworksCmd:
java.lang.NullPointerException
at com.cloud.utils.net.NetUtils.countIp6InRange(NetUtils.java:1219)
at 
com.cloud.network.NetworkModelImpl.isIP6AddressAvailableInVlan(NetworkModelImpl.java:556)
at 
com.cloud.network.NetworkModelImpl.isIP6AddressAvailableInNetwork(NetworkModelImpl.java:544)
at 
com.cloud.network.NetworkModelImpl.canUseForDeploy(NetworkModelImpl.java:524)
at com.cloud.api.ApiDBUtils.canUseForDeploy(ApiDBUtils.java:842)
at 
com.cloud.api.ApiResponseHelper.createNetworkResponse(ApiResponseHelper.java:3183)
at 
com.cloud.api.commands.ListNetworksCmd.execute(ListNetworksCmd.java:156)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:168)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:540)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:424)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:312)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at 
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-02-15 19:15:48,469 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) 
===END===  10.217.252.59 -- GET  
command=listNetworks&response=json&sessionkey=ZF9ctKFpv2BhlQxrC2Y8wvTlGMU%3D&zoneId=fa60468a-c5d1-42a2-92e8-23cc5a62b935&domainid=f4af033d-c767-447f-9a30-ad1174ca5e24&account=admin&_=1360955805067

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [DISCUSS][WIKI] Do we need a top-level Releases page?

[Joe Brockmeier]

On Fri, Feb 15, 2013, at 12:52 PM, Alex Huang wrote:
> Joe,
> 
> I think the pages for the releases in progress which updates users and
> developers about the status, bugs, and features of a release in progress
> should still be relatively high in the tree so people can easily access
> it.  That's information that people don't have access to from the landing
> page.  It doesn't have to be top level though.  You decide.  As for the
> current release, we can probably remove it.

Sure - releases in progress definitely belong on the wiki, no question.
That's fast-moving info that we need to edit almost daily. 

I just want to avoid duplicating content and having "stale" information
in one place or another. So the "finished" releases should live on the
main site because that information isn't going to change. (e.g., 4.0.0
will always have been released on 11/6/2012)
 
> Very disappointed that we can't use the html exports.  Don't really
> understand why from reading that page David sent out.

Sorry - the other issue he raised is pretty clear, though: To use the
wiki as our "official" site, we'd have to lock down contributions to
committers only, which would be bad on a number of levels. 

Thanks for getting back on this quickly!

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

RE: Review Request: Provide customizable instance names for guest VMs in cloudstack

[Animesh Chaturvedi]

Koushik

Any updates?

Animesh

> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Wednesday, February 13, 2013 7:08 PM
> To: Vijayendra Bhamidipati; Frank Zhang; Kelven Yang
> Cc: Wei Zhou; Koushik Das; cloudstack
> Subject: RE: Review Request: Provide customizable instance names for guest
> VMs in cloudstack
> 
> Koushik
> 
> If you are satisfied with the patch please commit it
> 
> Animesh
> 
> > -Original Message-
> > From: Venkata Siva Vijayendra Bhamidipati
> > [mailto:nore...@reviews.apache.org] On Behalf Of Venkata Siva
> > Vijayendra Bhamidipati
> > Sent: Thursday, February 07, 2013 7:27 PM
> > To: Frank Zhang; Kelven Yang
> > Cc: Wei Zhou; Koushik Das; Vijayendra Bhamidipati; cloudstack
> > Subject: Re: Review Request: Provide customizable instance names for
> > guest VMs in cloudstack
> >
> >
> >
> > > On Feb. 1, 2013, 9:50 a.m., Koushik Das wrote:
> > > > There is another config parameter instance.name based on which a
> > > > fixed
> > suffix is appended to the internal name. What happens to this
> > parameter in the context of this fix? Also as part of this fix you are
> > allowing to suffix the display name to internal name. Sometime back I
> > saw a request in the cs-user list to allow account name/id to be
> > appended to the internal instance name. Would it be possible to
> > provide a list of well defined attributes (for e.g. display name, account 
> > etc.) +
> fixed suffix.
> > >
> > > Wei Zhou wrote:
> > > Is it neccessary to add i-<>-<> as a suffix to displayname or internal
> name?
> > >
> > > As a user, I totally agree with the requirements which were
> > > posted on
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+user+prov
> > ide
> > d+hostname%2C+internal+VM+name+on+hypervisor+for+guest+VMs
> > > It seems that the result of this patch does not match the 
> > > requirements.
> > >
> > > In setup/db/db/schema-40to410.sql, the field should be
> > 'vm.instancename.flag', not 'vm.hostname.flag'.
> > >
> > > Wei Zhou wrote:
> > > Does this patch apply on master?
> > > I fail to apply on master, and change source codes manually.
> > > I have the same testing result which is fine.
> > >
> > > a suggestion:
> > > can you change createDhcpEntryCommand(VirtualRouter, UserVm,
> > > NicVO,
> > Commands) in
> > com.cloud.network.router.VirtualNetworkApplianceManagerImpl, so that
> > the OS hostname of VM can be set to displayname?
> >
> > Hi Koushik, Wei,
> >
> > Thanks for the reviews. Wei, thanks a lot for catching the
> > vm.instancename.flag error in the sql -- the diffs got mixed up and I
> > will reupload the patch after checking that it applies on top of tree 
> > (master).
> >
> > The instance.name parameter is a global setting which would apply to
> > all guest VMs. The requirement was to have a way to easily identify
> > each guest VM using a suffix that would match the display name. The
> > vm.instancename.flag will let the user set each guest VM's name
> > differently. The instance.name flag has been preserved to not change 
> > existing
> behavior.
> >
> > The i-<>-<> notation as a suffix is required for vmsync scripts to
> > identify and differentiate between cloudstack and non cloudstack VMs,
> > and also between system and guest VMs. This is why we have an
> > r/s/v/i-<>-<> naming convention for all VMs on cloudstack. If this
> > naming convention is not followed, scripts implementing vmsync functionality
> break.
> >
> > These changes in the requirements were not captured in
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+user+prov
> > ide
> > d+hostname%2C+internal+VM+name+on+hypervisor+for+guest+VMs
> > I will edit the contents of the link to reflect the above points.
> >
> > Also, it was determined that the hostname should not be changed as
> > part of this feature. Will update the above link with this as well.
> >
> > Regarding generic attributes, yes indeed it should be possible to do
> > that. We could have different flags for the same, or do it in some
> > other way. If the community wants to have it, I could do it in another
> > patch using a different issue id. In this context, I have a question -
> > I have set the maximum length of the VM internal instance name to 80
> > characters - if my memory is right, I wasn't able to use more than 93
> > characters for ESX VMs. So I arbitrarily chose
> > 80 as the max length allowed. I do not know what the max lengths are
> > for other hypervisors - if anyone knows these limits for sure, and
> > provide pointers for the same, it would be helpful - I will change the code
> accordingly.
> >
> > Finally, automated tests for the create VM API command already exist
> > under test/src/com/cloud/test/regression/. The above changes will be
> > covered by those tests.
> >
> >
> > Thanks,
> > Regards,
> > Vijay
> >
> >
> > - Venkata Siva Vijayendra
> >
> >
> > 

[jira] [Commented] (CLOUDSTACK-1252) Failed to download default template in VMware

[Parth Jagirdar (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579432#comment-13579432
 ] 

Parth Jagirdar commented on CLOUDSTACK-1252:


Just to inform that few Template and System VM related issues were observed on 
XS.
Please refer to following bugs may help in analysis.

1264
1261
1231 (Fixed)

...Parth


> Failed to download default template in VMware
> -
>
> Key: CLOUDSTACK-1252
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1252
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.1.0
> Environment: CentOS6.3
> 4.1 branch build
> Hyper visor : VMware 
>Reporter: Rayees Namathponnan
>Assignee: Nitin Mehta
>Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: cloud.rar
>
>
> Step 1 : Created new build from 4.1 branch 
> Step 2 : Install and configured MS server on CentOS 6.3 
> Step 3 : Prepared system template and created advanced zone
> Actual result 
> System VM are created, but "default templates" are not available in template 
> section.
>  
> I tried to started agent from SSVM, with command ">service cloudstack-agent 
> start" and failed, 
>  but command ">service cloud start" works
> If you look at the SSVM cloud.out (/var/log/cloud/clout.out) you can see 
> class not found exception java.lang.ClassNotFoundException: 
> com.cloud.storage.resource.PremiumSecondaryStorageResource
> + java -Djavax.net.ssl.trustStore=./certs/realhostip.keystore -mx168m -cp 
> ./:./conf:aopalliance-1.0.jar:apache-log4j-extras-1.1.jar:aspectjrt-1.7.1.jar:aspectjweaver-1.7.1.jar:aws-java-sdk-1.3.21.1.jar:backport-util-concurrent-3.1.jar:bcprov-jdk16-1.46.jar:cglib-nodep-2.2.2.jar:cloud-agent-4.1.0-SNAPSHOT.jar:cloud-api-4.1.0-SNAPSHOT.jar:cloud-console-proxy-4.1.0-SNAPSHOT.jar:cloud-core-4.1.0-SNAPSHOT.jar:cloud-utils-4.1.0-SNAPSHOT.jar:commons-codec-1.6.jar:commons-collections-3.2.1.jar:commons-configuration-1.8.jar:commons-dbcp-1.4.jar:commons-discovery-0.5.jar:commons-httpclient-3.1.jar:commons-lang-2.6.jar:commons-logging-1.1.1.jar:commons-pool-1.6.jar:dom4j-1.6.1.jar:ehcache-1.5.0.jar:ejb-api-3.0.jar:gson-1.7.1.jar:guava-14.0-rc1.jar:httpclient-4.1.jar:httpcore-4.1.jar:jackson-core-asl-1.8.9.jar:jackson-mapper-asl-1.8.9.jar:jasypt-1.9.0.jar:java-ipv6-0.8.jar:javassist-3.12.1.GA.jar:javax.inject-1.jar:javax.persistence-2.0.0.jar:jsch-0.1.42.jar:jsr107cache-1.0.jar:log4j-1.2.16.jar:reflections-0.9.8.jar:spring-aop-3.1.2.RELEASE.jar:spring-asm-3.1.2.RELEASE.jar:spring-beans-3.1.2.RELEASE.jar:spring-context-3.1.2.RELEASE.jar:spring-core-3.1.2.RELEASE.jar:spring-expression-3.1.2.RELEASE.jar:spring-web-3.1.2.RELEASE.jar:trilead-ssh2-build213-svnkit-1.3-patch.jar:xml-apis-1.0.b2.jar
>  com.cloud.agent.AgentShell template=domP type=secstorage host=10.223.49.197 
> port=8250 name=s-3-VM zone=1 pod=1 guid=s-3-VM 
> resource=com.cloud.storage.resource.PremiumSecondaryStorageResource 
> instance=SecStorage sslcopy=true role=templateProcessor mtu=1500 
> eth2ip=10.223.243.20 eth2mask=255.255.255.192 gateway=10.223.243.1 
> public.network.device=eth2 eth0mask=0.0.0.0 eth0ip=0.0.0.0 
> eth1ip=10.223.250.169 eth1mask=255.255.255.192 mgmtcidr=10.223.49.192/26 
> localgw=10.223.250.129 private.network.device=eth1 eth3ip=10.223.250.156 
> eth3mask=255.255.255.192 storageip=10.223.250.156 
> storagenetmask=255.255.255.192 storagegateway=10.223.250.129 
> internaldns1=10.223.110.254 internaldns2=10.223.110.253 dns1=72.52.126.11 
> dns2=72.52.126.12
> log4j:WARN No appenders could be found for logger 
> (org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Unable to start agent: Resource class not found: 
> com.cloud.storage.resource.PremiumSecondaryStorageResource due to: 
> java.lang.ClassNotFoundException: 
> com.cloud.storage.resource.PremiumSecondaryStorageResource
> Attached cloud.out for reference 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Deadline TODAY: ChefConf CFP

[Joe Brockmeier]

Hey all,

Folks who are using CloudStack + Chef, you might want to consider
submitting a proposal to ChefConf here:

https://chefconf2013.busyconf.com/proposals/new

The deadline is today (sorry). When I know about CFP deadlines that
would be appropriate for CloudStack folks, I'll try to a note to the
lists with a bit more notice in the future. 

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

RE: [MERGE]Storage refactor branch

[Edison Su]

> -Original Message-
> From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
> Sent: Friday, February 15, 2013 6:39 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: John Burwell  (jburw...@basho.com); Mike
> Tutkowski (mike.tutkow...@solidfire.com)
> Subject: RE: [MERGE]Storage refactor branch
> 
> Hey Edison,
> 
> Thanks for the update
> 
> > -Original Message-
> > From: Edison Su [mailto:edison...@citrix.com]
> > Sent: Friday, February 15, 2013 12:13 AM
> > To: cloudstack-dev@incubator.apache.org
> > Cc: John Burwell  (jburw...@basho.com); Mike
> > Tutkowski (mike.tutkow...@solidfire.com)
> > Subject: [MERGE]Storage refactor branch
> >
> > Hi All,
> >  Here is the update from storage refactor branch since last week:
> >
> > 1.   clean/hook up snapshot into new storage framework, separate taking
> > snapshot and backup snapshot. Add a snapshotstrategy interface for
> > people want to change or replace how snapshot is processed in
> > cloudstack. Current snapshot code is little bit hacky, welcome to replace it
> for your need.
> >   Since last week I created storage_refactor branch, seems no
> > objection for what I am doing, so I want to merge the branch into
> > master, by end of this week, due to the following reasons:
> >  Maintain such big patch(more than 20K) outside of master,
> > touch all the storage code, is not an easy task.
> >  After merge into master, other developers who developing
> > storage features can work on master directly, thus I don't need to
> > rebase the branch regularly.
> >   About test, I only tested basic features, like, stop/start vm,
> > attach/detach volumes, take snapshots in devcloud. For sure, I'll
> > break something. The more test from other people, will help to me to
> > stabilize the code. About unit test, I have some unit test and
> > integration test for devcloud, but both of them needs database and
> > devcloud environment, so they are disabled by default and unit test
> > themselves are broken also. I'll write more tests during the stabilization.
> 
> I understand the need to merge into master, it is a serious pain to keep
> updating the branch with that latest state of master. However this testing

Thanks for understand the painful of rebaseing such big patch. There is another 
reason I want to merge this branch into master ASAP: all the new storage 
features are depended this branch: like zone-wide storage, make nfs secondary 
storage as optional, re-write s3/swift integration etc. Let's get it merged, 
adding more awesome features:)

> concerns me a lot, we all agreed that we would focus on automated testing
> both on the unittest level and on the functional level. This is the first 
> merge
> request since we had the last discussion on testing (related to merging the
> javelin and other branches). The clear consensus was that commits would
> have to be accompanied by unittests (at least for the changed pieces of code)
> and preferable some automated functional test.
> 
> Considering that, I think that a merge is not the right this to do at the
> moment. Instead of merging into master and then fixing stuff, we should
> focus on adding testing to this branch so we can merge a well-tested unit
> later. Notice my use of 'we' here, we all said focus on testing, so we all 
> should
> help out. Unfortunately I'm pretty busy with packaging and the $dayjob, but
> if you have something I can help you with regarding setting up unittests feel
> free to let me know. You already mentioned that you have some, but the
> databases need to be mocked?
> 
> It would be great if you could spend some time to details what tests you
> have in place, so we can fix those. With the help of the cobertura report we
> can figure out where the risks are. Prassana and myself are also working on
> the automated test framework, so if you have some marvin tests, we can
> help to automate them.

My branch is not a feature branch, while other features are depended on it. I 
didn't add any new feature on the branch, all the existing marvin automated 
tests should work. Instead of testing and fixing on my branch then merge, is it 
better to test and fix on master after the merge, using existing marvin test? 
Again, the rebase to master is painful for such branch. 


> 
> Anybody else willing to help put in some tests into the storage_refactor
> branch?
> 
> Cheers,
> 
> Hugo

RE: Review Request: Scripts for Selenium UI automation.

[Parth Jagirdar]

John & Kelcey,

I have uploaded basic description for what scripts do.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Automation+using+Selenium+and+Python

Please review and let me know if any compliance issues.
I can fix and resubmit the scripts.


Thanks,
.. Parth


-Original Message-
From: Animesh Chaturvedi 
Sent: Wednesday, February 13, 2013 7:13 PM
To: Parth Jagirdar; Kelcey Jamison-Damage; John Kinsella
Cc: cloudstack
Subject: RE: Review Request: Scripts for Selenium UI automation.

Kelcey, john

Please review Parth's patch

> -Original Message-
> From: Parth Jagirdar [mailto:nore...@reviews.apache.org] On Behalf Of 
> Parth Jagirdar
> Sent: Wednesday, February 06, 2013 1:06 PM
> To: Kelcey Jamison-Damage; John Kinsella
> Cc: cloudstack; Parth Jagirdar
> Subject: Re: Review Request: Scripts for Selenium UI automation.
> 
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/9336/
> ---
> 
> (Updated Feb. 6, 2013, 9:05 p.m.)
> 
> 
> Review request for cloudstack, John Kinsella and Kelcey Jamison-Damage.
> 
> 
> Description
> ---
> 
> These scripts will execute following test cases on UI through Firefox. 
> (Test Cases taken from :: 
> http://wiki.cloudstack.org/display/QA/Manual+BVT)
> 
> 
> Login Admin user to UI.
> Create an Account name Test.
> Logout Admin user.
> Login Test user.
> 
> Add a new Disk Offering.
> Edit this Disk offering.
> Delete this Disk offering.
> 
> Add a new Compute Offering.
> Edit this Compute offering.
> Delete this Compute offering.
> 
> Logout Test user.
> Login Admin user.
> Delete Test user Account. And tear down the Browser instance.
> 
> # End of Tests
> 
> Thanks,
> ...Parth
> 
> 
> This addresses bug CLOUDSTACK-1180.
> 
> 
> Diffs
> -
> 
>   test/selenium/ReadMe.txt PRE-CREATION
>   test/selenium/lib/Global_Locators.py PRE-CREATION
>   test/selenium/lib/__init__.py PRE-CREATION
>   test/selenium/lib/initialize.py PRE-CREATION
>   test/selenium/smoke/Login_and_Accounts.py PRE-CREATION
>   test/selenium/smoke/Service_Offering.py PRE-CREATION
>   test/selenium/smoke/TemplatesAndISO.py PRE-CREATION
>   test/selenium/smoke/VM_lifeCycle.py PRE-CREATION
>   test/selenium/smoke/main.py PRE-CREATION
> 
> Diff: https://reviews.apache.org/r/9336/diff/
> 
> 
> Testing
> ---
> 
> Tested with network refactor branch.
> 
> 
> Thanks,
> 
> Parth Jagirdar