date:20161214

Edit of Shared Network in Cloudstack

2016-12-14 Thread Venkata Yedugundla

Hi All,

I can see we are restricting the edit of network offering for the shared 
network. Can somebody through some light of the reason for that? The following 
is the corresponding JIRA ticket

https://issues.apache.org/jira/browse/CLOUDSTACK-571

Thanks,
Subhash



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

[GitHub] cloudstack pull request #1828: CLOUDSTACK-9676 Start instance fails after re...

2016-12-14 Thread sateesh-chodapuneedi

GitHub user sateesh-chodapuneedi opened a pull request:

https://github.com/apache/cloudstack/pull/1828

CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot when 
there are child VM snapshots

Jira
===
CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot when 
there are child VM snapshots

Issue

Start instance fails after reverting to a VM snapshot, when there is 1 or 
more child VM snapshots in the snapshot tree of the VM.
Per the code that detects the presence of a snapshot, we are checking for 
only current snapshot instead of checking presence of any snapshot in the 
snapshot tree.
The failure to detect all snapshots means ACP reconfigures the VM in wrong 
way assuming there are no snapshots for the VM.
This results in start failure.

Fix
===
Ensure correct detection of VM snapshots in the VM snapshot tree



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sateesh-chodapuneedi/cloudstack 
pr-cloudstack-9676

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1828.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1828


commit 34c85f5847dd4d3e55700e324bf695c60b8a4ca6
Author: Sateesh Chodapuneedi 
Date:   2016-12-13T20:22:15Z

CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot, when 
there are child VM snapshots

Issue

Start instance fails after reverting to a VM snapshot, when there is 1 or 
more child VM snapshots in the snapshot tree of the VM.
Per the code that detects the presence of a snapshot, we are checking for 
only current snapshot instead of checking presence of any snapshot in the 
snapshot tree.
The failure to detect all snapshots means ACP reconfigures the VM in wrong 
way assuming there are no snapshots for the VM.
This results in start failure.

Fix
===
Ensure correct detection of VM snapshots in the VM snapshot tree

Signed-off-by: Sateesh Chodapuneedi 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)

2016-12-14 Thread Murali Reddy

+1

Based on smoke test results [1] and below tests run manually on VMware 
deployment

  - VM life cycle operations
  - network life cycle operations
  - verified source NAT, static NAT, PF, LB, VPC internal LB, network ACL, 
firewall
  - upgrade from 4.9 and 4.5.2


IMO issue raised by Milamber should be fixed on 4.10. If the functionality does 
not exist in 4.9, then no need to have schema change in 4.8 to 4.9 upgrade path.

Redundant VPC VR functionality appears to be broken from last few releases. In 
my testing noticed both the VR getting stuck in backup or in unknown state. RVR 
test failed consistently in smoke tests [1]. We should at least release note 
them as known issues. I will check existing bugs and open new one if necessary.

[1] https://github.com/apache/cloudstack/pull/1753




On 14/12/16, 12:32 AM, "Milamber"  wrote:

>
>Hello,
>
>I'm not sure, but perhaps we have an 'indirect' blocker for 4.9.1.0 RC1.
>
>Currently the upgrade from 4.9.1.0 RC1 to 4.10.0.0 SNAPSHOT don't works 
>because the schema-481to490.sql in the 4.9.1.0 / 4.9 doesn't contains 
>the commit of CLOUDSTACK-9438 (2e77496601ab5420723ce8b955b3960faaba7d5c).
>(this commit is currently in master)
>
>When you try to make the upgrade you have this error: "Unknown column 
>'image_store_details.display' in 'field list'"
>see:  https://issues.apache.org/jira/browse/CLOUDSTACK-9671
>
>Currently there have 2 diff between the schema-481to490.sql in 4.9.1.0 
>RC1 (and 4.9 branch) and master branch.
>
>What is your opinion: blocker or not?
>
>Just copy the 2 sql request inside the schema-4910to41000.sql file (but 
>the commit 2e77496601ab5420723ce8b955b3960faaba7d5c contains other 
>modified files)?
>
>Milamber
>
>
>
>$ diff ./setup/db/db/schema-481to490.sql /tmp/MASTER-schema-481to490.sql
>547a548,552
> >
> > ALTER TABLE `cloud`.`image_store_details` CHANGE COLUMN `value` 
>`value` VARCHAR(255) NULL DEFAULT NULL COMMENT 'value of the detail', 
>ADD COLUMN `display` tinyint(1) NOT
> > NULL DEFAULT '1' COMMENT 'True if the detail can be displayed to the 
>end user' AFTER `value`;
> >
> > ALTER TABLE `snapshots` ADD COLUMN `location_type` VARCHAR(32) 
>COMMENT 'Location of snapshot (ex. Primary)';
>
>
>
>
>
>On 12/12/2016 21:36, Milamber wrote:
>> Hello,
>>
>> My vote +1 (binding)
>>
>> Tests are passed on a virtual topology of servers  (CS over CS) 
>> (1mgr+2nodes+1nfs) :
>>
>> 1/ Fresh install of 4.9.1.0 RC1 (adv net) on Ubuntu 14.04.5 + KVM + 
>> NFS : OK
>> Some standard tests with success (create vm, migration, HA, create 
>> networks, create user, create ssh key, destroy vm, register template, 
>> create snapshot, restore snapshot, create template, ip association, ip 
>> release, static nat, firewall rule)
>> Some tests with cloudstack ansible module with success too (create 
>> network, register templates, create vm, ip, firewall rule)
>>
>> 2/ Test upgrade from 4.8.1 to 4.9.1.0 RC1 : OK
>>
>> 3/ Test upgrade from 4.8.2 RC1 to 4.9.1.0 RC1 : don't works (expected)
>>
>> 4/ Tests of all localization Web UI for 4.9.1.0 RC1:
>> Localization works well except Spanish (not a blocker to release): the 
>> Web UI display partially the localization strings due of one bad 
>> carriage return in the label 
>> message.installWizard.copy.whatIsCloudStack string (from Transifex). 
>> This is the same issue that the 4.8.2 RC1.
>>
>>
>> Perhaps add in the Release notes this Spanish l10n issue.
>>
>> Thanks to the RM.
>>
>> Milamber
>>
>>
>>
>> On 10/12/2016 03:11, Rohit Yadav wrote:
>>> Hi All,
>>>
>>> I've created a 4.9.1.0 release, with the following artifacts up for a 
>>> vote:
>>>
>>> Git Branch and Commit SH:
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.9.1.0-RC20161210T0838
>>>  
>>>
>>> Commit: af2679959b634d095b93b8265c6da294d360065d
>>>
>>> List of changes:
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.9.1.0-RC20161210T0838
>>>  
>>>
>>>
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.9.1.0/
>>>
>>> PGP release keys (signed using 0EE3D884):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>> Vote will be open for 120 hours, considering the process started 
>>> during the
>>> weekends, and will end on 14 Dec 2016 end of the day.
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to 
>>> indicate
>>> "(binding)" with their vote?
>>>
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> Regards.
>>>
>>
>>
>

[GitHub] cloudstack issue #1734: CLOUDSTACK-9567 Difference in the api call outputs f...

2016-12-14 Thread SudharmaJain

Github user SudharmaJain commented on the issue:

https://github.com/apache/cloudstack/pull/1734
  
@jburwell I have added a Marvin test case to verify the fix.  


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #669: Made the adding new keyboard language support easier

2016-12-14 Thread anshul1886

Github user anshul1886 commented on the issue:

https://github.com/apache/cloudstack/pull/669
  
@swill @jburwell Updated in according to newer changes in UI. Also moved 
consoleKeyboardOptions to js file after jsp change.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #669: Made the adding new keyboard language support easier

2016-12-14 Thread anshul1886

Github user anshul1886 commented on the issue:

https://github.com/apache/cloudstack/pull/669
  
@jburwell Failed tests are not related to change in this PR.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #672: Allow VM snapshots and volume snapshots to exist toge...

2016-12-14 Thread anshul1886

Github user anshul1886 commented on the issue:

https://github.com/apache/cloudstack/pull/672
  
@jburwell those are fixing different bugs but all all needed to enable this 
that's  why they are kept as separate tickets.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)

2016-12-14 Thread Boris Stoyanov

Hi, 

We’ve currently have a plan for upgrade testing covering the following 
scenarios:
I’ve tried upgrading from 4.5.2.2 to 4.9.1, but got the following exception: 

2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
Schema upgrade from 4.5.1 to 4.6.0
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) ALTER 
TABLE `cloud`.`snapshots` ADD COLUMN `min_iops` bigint(20) unsigned COMMENT 
'Minimum IOPS'
2016-12-13 14:37:28,135 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error 
executing: ALTER TABLE `cloud`.`snapshots` ADD COLUMN `min_iops` bigint(20) 
unsigned COMMENT 'Minimum IOPS'
2016-12-13 14:37:28,135 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) 
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column 
name 'min_iops'
2016-12-13 14:37:28,136 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) 
(logid:) Unable to execute upgrade script: 
/usr/share/cloudstack-management/setup/db/schema-452to460.sql
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column 
name 'min_iops'
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185)
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)

We’re currently having a plan to cover upgrade testing to 4.9.1 from 4.3, 
4.5.2.2, 4.6.0. I’d love to continue with testing these upgrade scenarios once 
we fix the issue. 

Currently also we’re executing component tests against the following 
combinations: 

[KVM]
MS CentOS68 + KVM hosts CentOS68
MS CentOS72 + KVM hosts CentOS72

[VMware]
MS CentOS68 + VMware55u3
MS CentOS68 + VMware60u2
MS CentOS68 + VMware65

MS CentOS72 + VMware55u3
MS CentOS72 + VMware60u2
MS CentOS72 + VMware65
 
[XenServer]
MS CentOS68 + XenServer62sp1
MS CentOS68 + XenServer65sp1

MS CentOS72+ XenServer65sp1

*Once we get 4.9.1 we’re looking fw to test XenServer 7 as well, as part of 
4.9.2.0


Smoke tests has passed on KVM, VMware and XenServer hosts with CentOS6 and 
CentOS7 MS. 

Thanks,


boris.stoya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

> On Dec 14, 2016, at 12:18 PM, Murali Reddy  wrote:
> 
> +1
> 
> Based on smoke test results [1] and below tests run manually on VMware 
> deployment
> 
>  - VM life cycle operations
>  - network life cycle operations
>  - verified source NAT, static NAT, PF, LB, VPC internal LB, network ACL, 
> firewall
>  - upgrade from 4.9 and 4.5.2
> 
> 
> IMO issue raised by Milamber should be fixed on 4.10. If the functionality 
> does not exist in 4.9, then no need to have schema change in 4.8 to 4.9 
> upgrade path.
> 
> Redundant VPC VR functionality appears to be broken from last few releases. 
> In my testing noticed both the VR getting stuck in backup or in unknown 
> state. RVR test failed consistently in smoke tests [1]. We should at least 
> release note them as known issues. I will check existing bugs and open new 
> one if necessary.
> 
> [1] https://github.com/apache/cloudstack/pull/1753
> 
> 
> 
> 
> On 14/12/16, 12:32 AM, "Milamber"  wrote:
> 
>> 
>> Hello,
>> 
>> I'm not sure, but perhaps we have an 'indirect' blocker for 4.9.1.0 RC1.
>> 
>> Currently the upgrade from 4.9.1.0 RC1 to 4.10.0.0 SNAPSHOT don't works 
>> because the schema-481to490.sql in the 4.9.1.0 / 4.9 doesn't contains 
>> the commit of CLOUDSTACK-9438 (2e77496601ab5420723ce8b955b3960faaba7d5c).
>> (this commit is currently in master)
>> 
>> When you try to make the upgrade you have this error: "Unknown column 
>> 'image_store_details.display' in 'field list'"
>> see:  https://issues.apache.org/jira/browse/CLOUDSTACK-9671
>> 
>> Currently there have 2 diff between the schema-481to490.sql in 4.9.1.0 
>> RC1 (and 4.9 branch) and master branch.
>> 
>> What is your opinion: blocker or not?
>> 
>> Just copy the 2 sql request inside the schema-4910to41000.sql file (but 
>> the commit 2e77496601ab5420723ce8b955b3960faaba7d5c contains other 
>> modified files)?
>> 
>> Milamber
>> 
>> 
>> 
>> $ diff ./setup/db/db/schema-481to490.sql /tmp/MASTER-schema-481to490.sql
>> 547a548,552
>>> 
>>> ALTER TABLE `cloud`.`image_store_details` CHANGE COLUMN `value` 
>> `value` VARCHAR(255) NULL DEFAULT NULL COMMENT 'value of the detail', 
>> ADD COLUMN `display` tinyint(1) NOT
>>> NULL DEFAULT '1' COMMENT 'True if the detail can be displayed to the 
>> end user' AFTER `value`;
>>> 
>>> ALTER TABLE `snapshots` ADD COLUMN `location_type` VARCHAR(32) 
>> COMMENT 'Location of snapshot (ex. Primary)';
>> 
>> 
>> 
>> 
>> 
>> On 12/12/2016 21:36, Milamber wrote:
>>> Hello,
>>> 
>>> My vote +1 (binding)
>>> 
>>> Tests are passed on a virtual topology of servers  (CS over CS) 
>>> (1mgr+2nodes+1nfs) :
>>> 
>>> 1/ Fresh install of 4.9.1.0 RC1 (adv net) on Ubuntu 14.04.5 + KVM + 
>>> NFS : OK
>>> Some standard tests with succes

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread serg38

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
LGTM on code review


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)

2016-12-14 Thread Simon Weller

Can you remove that column addition in the alter statement and see if the 
upgrade continues?

Do you recall installing any customer version of ACS that may have included DB 
schema patches?



From: Boris Stoyanov 
Sent: Wednesday, December 14, 2016 6:31 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)

Hi,

We’ve currently have a plan for upgrade testing covering the following 
scenarios:
I’ve tried upgrading from 4.5.2.2 to 4.9.1, but got the following exception:

2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
Schema upgrade from 4.5.1 to 4.6.0
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) ALTER 
TABLE `cloud`.`snapshots` ADD COLUMN `min_iops` bigint(20) unsigned COMMENT 
'Minimum IOPS'
2016-12-13 14:37:28,135 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error 
executing: ALTER TABLE `cloud`.`snapshots` ADD COLUMN `min_iops` bigint(20) 
unsigned COMMENT 'Minimum IOPS'
2016-12-13 14:37:28,135 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) 
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column 
name 'min_iops'
2016-12-13 14:37:28,136 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) 
(logid:) Unable to execute upgrade script: 
/usr/share/cloudstack-management/setup/db/schema-452to460.sql
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column 
name 'min_iops'
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185)
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)

We’re currently having a plan to cover upgrade testing to 4.9.1 from 4.3, 
4.5.2.2, 4.6.0. I’d love to continue with testing these upgrade scenarios once 
we fix the issue.

Currently also we’re executing component tests against the following 
combinations:

[KVM]
MS CentOS68 + KVM hosts CentOS68
MS CentOS72 + KVM hosts CentOS72

[VMware]
MS CentOS68 + VMware55u3
MS CentOS68 + VMware60u2
MS CentOS68 + VMware65

MS CentOS72 + VMware55u3
MS CentOS72 + VMware60u2
MS CentOS72 + VMware65

[XenServer]
MS CentOS68 + XenServer62sp1
MS CentOS68 + XenServer65sp1

MS CentOS72+ XenServer65sp1

*Once we get 4.9.1 we’re looking fw to test XenServer 7 as well, as part of 
4.9.2.0


Smoke tests has passed on KVM, VMware and XenServer hosts with CentOS6 and 
CentOS7 MS.

Thanks,


boris.stoya...@shapeblue.com
www.shapeblue.com
[http://shapeblue.com/wp-content/uploads/2014/03/sungardonline1.jpg]

ShapeBlue - The CloudStack Company
www.shapeblue.com
Offers seamless Container-as-a-Service without disruption to user experience or 
business process Sevilla, Spain -- 17 November 2016 -- ShapeBlue, the



53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue



> On Dec 14, 2016, at 12:18 PM, Murali Reddy  wrote:
>
> +1
>
> Based on smoke test results [1] and below tests run manually on VMware 
> deployment
>
>  - VM life cycle operations
>  - network life cycle operations
>  - verified source NAT, static NAT, PF, LB, VPC internal LB, network ACL, 
> firewall
>  - upgrade from 4.9 and 4.5.2
>
>
> IMO issue raised by Milamber should be fixed on 4.10. If the functionality 
> does not exist in 4.9, then no need to have schema change in 4.8 to 4.9 
> upgrade path.
>
> Redundant VPC VR functionality appears to be broken from last few releases. 
> In my testing noticed both the VR getting stuck in backup or in unknown 
> state. RVR test failed consistently in smoke tests [1]. We should at least 
> release note them as known issues. I will check existing bugs and open new 
> one if necessary.
>
> [1] https://github.com/apache/cloudstack/pull/1753
[https://avatars1.githubusercontent.com/u/95203?v=3&s=400]

[4.9] Latest health test run by rhtyd · Pull Request #1753 · 
apache/cloudstack
github.com
Dummy PR to trigger tests on latest 4.9 branch @blueorangutan package



>
>
>
>
> On 14/12/16, 12:32 AM, "Milamber"  wrote:
>
>>
>> Hello,
>>
>> I'm not sure, but perhaps we have an 'indirect' blocker for 4.9.1.0 RC1.
>>
>> Currently the upgrade from 4.9.1.0 RC1 to 4.10.0.0 SNAPSHOT don't works
>> because the schema-481to490.sql in the 4.9.1.0 / 4.9 doesn't contains
>> the commit of CLOUDSTACK-9438 (2e77496601ab5420723ce8b955b3960faaba7d5c).
>> (this commit is currently in master)
>>
>> When you try to make the upgrade you have this error: "Unknown column
>> 'image_store_details.display' in 'field list'"
>> see:  https://issues.apache.org/jira/browse/CLOUDSTACK-9671
>>
>> Currently there have 2 diff between the schema-481to490.sql in 4.9.1.0
>> RC1 (and 4.9 branch) and master branch.
>>
>> What is your opinion: blocker or not?
>>
>> Ju

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread sateesh-chodapuneedi

Github user sateesh-chodapuneedi commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
Thanks, @serg38, @borisstoyanov for reviews.
@karuturi @rhtyd Can you pleas trigger trillian tests for validation?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1829: CLOUDSTACK-9363: Fix HVM VM restart bug in Xe...

2016-12-14 Thread syed

GitHub user syed opened a pull request:

https://github.com/apache/cloudstack/pull/1829

CLOUDSTACK-9363: Fix HVM VM restart bug in XenServer

Here is the longer description of the problem:

By default XenServer limits HVM guests to only 4 disks. Two of those are 
reserved for the ROOT disk (deviceId=0) and CD ROM (device ID=3) which means 
that we can only attach 2 data disks. This limit however is removed when 
Xentools is installed on the guest. The information that a guest has Xentools 
installed and can handle more than 4 disks is stored in the VM metadata on 
XenServer. When a VM is shut down, Cloudstack removes the VM and all the 
metadata associated with the VM from XenServer. Now, when you start the VM 
again, even if it has Xentools installed, it will default to only 4 attachable 
disks.

Now this problem manifests itself when you have a HVM VM and you stop and 
start it with more than 2 data disks attached. The VM fails to start and the 
only way to start the VM is to detach the extra disks and then reattach them 
after the VM start.

In this fix, I am removing the check which is done before creating a `VBD` 
which enforces this limit. This will not affect current workflow and will fix 
the HVM issue.

@koushik-das this is related to the "autodetect" feature that you 
introduced a while back 
(https://issues.apache.org/jira/browse/CLOUDSTACK-8826). I would love your 
review on this fix.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/syed/cloudstack hvm-volume-attach-restart-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1829.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1829


commit ad7de468161c5241b3d4aba899df9872eb02ea6e
Author: Syed 
Date:   2016-12-14T16:39:42Z

CLOUDSTACK-9363: Fix HVM VM restart bug in XenServer




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread murali-reddy

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
@murali-reddy a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
Packaging result: âcentos6 âcentos7 âdebian. JID-392


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread murali-reddy

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
@blueorangutan test centos7 vmware-55u3


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
@murali-reddy a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has 
been kicked to run smoke tests


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1830: CLOUDSTACK-9677: Adding storage policy suppor...

2016-12-14 Thread pdube

GitHub user pdube opened a pull request:

https://github.com/apache/cloudstack/pull/1830

CLOUDSTACK-9677: Adding storage policy support for swift as secondaryâ¦

â¦ storage

Added support to use storage policies with swift

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pdube/cloudstack swift-storagepolicies

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1830.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1830


commit b157381b9933e17bd2f0583ecf519c58faeffcb7
Author: Patrick Dube 
Date:   2016-12-14T18:57:20Z

CLOUDSTACK-9677: Adding storage policy support for swift as secondary 
storage




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1753: [4.9] Latest health test run

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1753
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1754: [4.10] Latest health test run

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1754
  
@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1753: [4.9] Latest health test run

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1753
  
@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1754: [4.10] Latest health test run

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1754
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1829: CLOUDSTACK-9363: Fix HVM VM restart bug in XenServer

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1829
  
@syed can you rebase against 4.9 and change PR's branch to 4.9? As soon as 
4.9.1.0 is out, we'll work towards 4.9.2.0 and work towards the next minor 
release to include several such bugfixes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)

2016-12-14 Thread Rohit Yadav

Hi Bruno,


I checked the issue, the PR #1615 was merged only on master. Since, we've not 
started release work for 4.10/master yet, I'll move the changes to appropriate 
sql schema. This is not a blocker for either 4.8.2.0 or 4.9.1.0 as the 
changes/feature don't exist on them yet.

Thanks again for sharing this, I'll fix them today.


All, since there is no blocker please continue with your tests and voting.


Regards.


From: Milamber 
Sent: 14 December 2016 00:32:19
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)


Hello,

I'm not sure, but perhaps we have an 'indirect' blocker for 4.9.1.0 RC1.

Currently the upgrade from 4.9.1.0 RC1 to 4.10.0.0 SNAPSHOT don't works
because the schema-481to490.sql in the 4.9.1.0 / 4.9 doesn't contains
the commit of CLOUDSTACK-9438 (2e77496601ab5420723ce8b955b3960faaba7d5c).
(this commit is currently in master)

When you try to make the upgrade you have this error: "Unknown column
'image_store_details.display' in 'field list'"
see:  https://issues.apache.org/jira/browse/CLOUDSTACK-9671

Currently there have 2 diff between the schema-481to490.sql in 4.9.1.0
RC1 (and 4.9 branch) and master branch.

What is your opinion: blocker or not?

Just copy the 2 sql request inside the schema-4910to41000.sql file (but
the commit 2e77496601ab5420723ce8b955b3960faaba7d5c contains other
modified files)?

Milamber



$ diff ./setup/db/db/schema-481to490.sql /tmp/MASTER-schema-481to490.sql
547a548,552
 >
 > ALTER TABLE `cloud`.`image_store_details` CHANGE COLUMN `value`
`value` VARCHAR(255) NULL DEFAULT NULL COMMENT 'value of the detail',
ADD COLUMN `display` tinyint(1) NOT
 > NULL DEFAULT '1' COMMENT 'True if the detail can be displayed to the
end user' AFTER `value`;
 >
 > ALTER TABLE `snapshots` ADD COLUMN `location_type` VARCHAR(32)
COMMENT 'Location of snapshot (ex. Primary)';





On 12/12/2016 21:36, Milamber wrote:
> Hello,
>
> My vote +1 (binding)
>
> Tests are passed on a virtual topology of servers  (CS over CS)
> (1mgr+2nodes+1nfs) :
>
> 1/ Fresh install of 4.9.1.0 RC1 (adv net) on Ubuntu 14.04.5 + KVM +
> NFS : OK
> Some standard tests with success (create vm, migration, HA, create
> networks, create user, create ssh key, destroy vm, register template,
> create snapshot, restore snapshot, create template, ip association, ip
> release, static nat, firewall rule)
> Some tests with cloudstack ansible module with success too (create
> network, register templates, create vm, ip, firewall rule)
>
> 2/ Test upgrade from 4.8.1 to 4.9.1.0 RC1 : OK
>
> 3/ Test upgrade from 4.8.2 RC1 to 4.9.1.0 RC1 : don't works (expected)
>
> 4/ Tests of all localization Web UI for 4.9.1.0 RC1:
> Localization works well except Spanish (not a blocker to release): the
> Web UI display partially the localization strings due of one bad
> carriage return in the label
> message.installWizard.copy.whatIsCloudStack string (from Transifex).
> This is the same issue that the 4.8.2 RC1.
>
>
> Perhaps add in the Release notes this Spanish l10n issue.
>
> Thanks to the RM.
>
> Milamber
>
>
>
> On 10/12/2016 03:11, Rohit Yadav wrote:
>> Hi All,
>>
>> I've created a 4.9.1.0 release, with the following artifacts up for a
>> vote:
>>
>> Git Branch and Commit SH:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.9.1.0-RC20161210T0838
>>
>> Commit: af2679959b634d095b93b8265c6da294d360065d
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.9.1.0-RC20161210T0838
>>
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.9.1.0/
>>
>> PGP release keys (signed using 0EE3D884):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> Vote will be open for 120 hours, considering the process started
>> during the
>> weekends, and will end on 14 Dec 2016 end of the day.
>>
>> For sanity in tallying the vote, can PMC members please be sure to
>> indicate
>> "(binding)" with their vote?
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Regards.
>>
>
>


rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

[GitHub] cloudstack issue #1749: CLOUDSTACK-9619: Updates for SAN-assisted snapshots

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1749
  
Ping where are we with this PR, @mike-tutkowski @syed @abhinandanprateek 
@murali-reddy thanks.

@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1749: CLOUDSTACK-9619: Updates for SAN-assisted snapshots

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1749
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1831: CLOUDSTACK-9671: Fix sql change to correspond...

2016-12-14 Thread rhtyd

GitHub user rhtyd opened a pull request:

https://github.com/apache/cloudstack/pull/1831

CLOUDSTACK-9671: Fix sql change to corresponding version paths

- Fixes issue of failing upgrade paths
- Moves schema changes from PR #1615 in the 4.9.1.0 to 4.10.0.0 sql path

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shapeblue/cloudstack fix-sql-pr-1615-410

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1831.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1831


commit dd321a6de335aaa32edec45a916c0bccf8201f42
Author: Rohit Yadav 
Date:   2016-12-15T06:30:47Z

CLOUDSTACK-9671: Fix sql change to corresponding version paths

- Fixes issue of failing upgrade paths
- Moves schema changes from PR #1615 in the 4.9.1.0 to 4.10.0.0 sql path

Signed-off-by: Rohit Yadav 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1831: CLOUDSTACK-9671: Fix sql change to corresponding ver...

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1831
  
Based on 4.9.1.0 rc1 thread. Merging this on discretion.
Tested upgrade from 4.9.1.0-rc1 to master (4.10.0.0-SNAPSHOT) manually.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1831: CLOUDSTACK-9671: Fix sql change to correspond...

2016-12-14 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/1831


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1753: [4.9] Latest health test run

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1753
  
Packaging result: âcentos6 âcentos7 âdebian. JID-393


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1754: [4.10] Latest health test run

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1754
  
Packaging result: âcentos6 âcentos7 âdebian. JID-394


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1754: [4.10] Latest health test run

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1754
  
@blueorangutan test matrix


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1753: [4.9] Latest health test run

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1753
  
@blueorangutan test matrix


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1754: [4.10] Latest health test run

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1754
  
@rhtyd a Trillian-Jenkins matrix job (centos6 mgmt + xs65sp1, centos7 mgmt 
+ vmware55u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1753: [4.9] Latest health test run

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1753
  
@rhtyd a Trillian-Jenkins matrix job (centos6 mgmt + xs65sp1, centos7 mgmt 
+ vmware55u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1828: CLOUDSTACK-9676 Start instance fails after reverting...

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1828
  
Trillian test result (tid-677)
Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42942 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1828-t677-vmware-55u3.zip
Test completed. 40 look ok, 9 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_02_VPC_default_routes | `Failure` | 399.88 | test_vpc_router_nics.py
test_02_redundant_VPC_default_routes | `Failure` | 567.43 | 
test_vpc_redundant.py
test_03_ssvm_internals | `Failure` | 13.40 | test_ssvm.py
test_router_dhcphosts | `Failure` | 61.74 | test_router_dhcphosts.py
test_04_rvpc_privategw_static_routes | `Failure` | 1053.04 | 
test_privategw_acl.py
test_isolate_network_password_server | `Failure` | 61.83 | 
test_password_server.py
ContextSuite context=TestVpcSite2SiteVpn>:setup | `Error` | 0.00 | 
test_vpc_vpn.py
ContextSuite context=TestVpcRemoteAccessVpn>:setup | `Error` | 0.00 | 
test_vpc_vpn.py
ContextSuite context=TestRVPCSite2SiteVpn>:setup | `Error` | 0.00 | 
test_vpc_vpn.py
ContextSuite context=TestVPCRedundancy>:teardown | `Error` | 721.33 | 
test_vpc_redundant.py
test_06_download_detached_volume | `Error` | 60.40 | test_volumes.py
ContextSuite context=TestRouterDHCPHosts>:teardown | `Error` | 81.92 | 
test_router_dhcphosts.py
ContextSuite context=TestListIdsParams>:setup | `Error` | 0.00 | 
test_list_ids_parameter.py
test_01_VPC_nics_after_destroy | Success | 792.39 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 716.25 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1567.45 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 858.17 | test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1493.44 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 46.10 | test_volumes.py
test_05_detach_volume | Success | 105.27 | test_volumes.py
test_04_delete_attached_volume | Success | 15.19 | test_volumes.py
test_03_download_attached_volume | Success | 20.31 | test_volumes.py
test_02_attach_volume | Success | 63.82 | test_volumes.py
test_01_create_volume | Success | 529.66 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.20 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 232.19 | test_vm_snapshots.py
test_01_test_vm_volume_snapshot | Success | 161.67 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 161.73 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 256.96 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.97 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.16 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 121.18 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.07 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 10.11 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 5.11 | test_vm_life_cycle.py
test_02_start_vm | Success | 20.18 | test_vm_life_cycle.py
test_01_stop_vm | Success | 10.12 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 276.43 | test_templates.py
test_08_list_system_templates | Success | 0.02 | test_templates.py
test_07_list_public_templates | Success | 0.02 | test_templates.py
test_05_template_permissions | Success | 0.04 | test_templates.py
test_04_extract_template | Success | 15.21 | test_templates.py
test_03_delete_template | Success | 5.08 | test_templates.py
test_02_edit_template | Success | 90.16 | test_templates.py
test_01_create_template | Success | 140.80 | test_templates.py
test_10_destroy_cpvm | Success | 236.49 | test_ssvm.py
test_09_destroy_ssvm | Success | 274.56 | test_ssvm.py
test_08_reboot_cpvm | Success | 156.35 | test_ssvm.py
test_07_reboot_ssvm | Success | 158.40 | test_ssvm.py
test_06_stop_cpvm | Success | 231.73 | test_ssvm.py
test_05_stop_ssvm | Success | 268.95 | test_ssvm.py
test_04_cpvm_internals | Success | 1.18 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.09 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.10 | test_ssvm.py
test_01_snapshot_root_disk | Success | 66.43 | test_snapshots.py
test_04_change_offering_small | Success | 102.33 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.06 | test_service_offerings.py
test_01_create_service_offering | Success | 0.10 | test_service_offerings.py
test_02_sys_template_ready | S

Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)

2016-12-14 Thread Rohit Yadav

All,


Please proceed with testing this RC. I've kicked new tests to rule out 
intermittent failures.



Hi Bobby,


I've tried to deploy a 4.5.2.2 based environment and upgraded to 4.9.1.0 
without any upgrade failures. I'm using MySQL 5.7, can you share your MySQL 
server version and other environment details?


To make 4.5.2.2 work with MySQL 5.7, I had to make a minor change:

--- a/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java
+++ b/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java
@@ -1568,7 +1568,7 @@ public class Upgrade410to420 implements DbUpgrade {
 s_logger.debug("Index already exists on host_details - not 
adding new one");
 } else {
 // add the index
-PreparedStatement pstmtUpdate = conn.prepareStatement("ALTER 
IGNORE TABLE `cloud`.`host_details` ADD INDEX `fk_host_details__host_id` 
(`host_id`)");
+PreparedStatement pstmtUpdate = conn.prepareStatement("ALTER 
TABLE `cloud`.`host_details` ADD INDEX `fk_host_details__host_id` (`host_id`)");
 pstmtUpdate.executeUpdate();
 s_logger.debug("Index did not exist on host_details -  added 
new one");
 pstmtUpdate.close();




Reference logs:


INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Running 
system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@5109880a
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Grabbing lock to 
check for database upgrade.
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) DB version = 4.5.2 
Code Version = 4.9.1.0
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Database upgrade must 
be performed from 4.5.2 to 4.9.1.0
WARN  [c.c.u.d.Upgrade452to460] (main:null) (logid:) 4.6.0KVM SystemVm template 
not found. KVM hypervisor is not used, so not failing upgrade
WARN  [c.c.u.d.Upgrade452to460] (main:null) (logid:) 4.6.0Ovm3 SystemVm 
template not found. Ovm3 hypervisor is not used, so not failing upgrade
WARN  [c.c.u.d.Upgrade452to460] (main:null) (logid:) 4.6.0Hyperv SystemVm 
template not found. Hyperv hypervisor is not used, so not failing upgrade
WARN  [c.c.u.d.Upgrade452to460] (main:null) (logid:) 4.6.0XenServer SystemVm 
template not found. XenServer hypervisor is not used, so not failing upgrade
WARN  [c.c.u.d.Upgrade452to460] (main:null) (logid:) 4.6.0LXC SystemVm template 
not found. LXC hypervisor is not used, so not failing upgrade
WARN  [c.c.u.d.Upgrade452to460] (main:null) (logid:) 4.6.0VMware SystemVm 
template not found. VMware hypervisor is not used, so not failing upgrade
INFO  [c.c.u.d.Upgrade461to470] (main:null) (logid:) Altered 
cloud_usage.cloud_usage table and added column quota_calculated
ERROR [c.c.u.PropertiesUtil] (main:null) (logid:) Unable to find properties 
file: commands.properties
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleaning upgrades 
because all management server are now at the same version
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade452to460 to upgrade from 4.5.2-4.6.0 to 4.6.0
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade460to461 to upgrade from 4.6.0-4.6.1 to 4.6.1
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade461to470 to upgrade from 4.6.1-4.7.0 to 4.7.0
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade470to471 to upgrade from 4.7.0-4.7.1 to 4.7.1
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade471to480 to upgrade from 4.7.1-4.8.0 to 4.8.0
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade480to481 to upgrade from 4.8.0-4.8.1 to 4.8.1
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade481to490 to upgrade from 4.8.1-4.9.0 to 4.9.0
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade 
Upgrade490to4910 to upgrade from 4.9.0-4.9.1.0 to 4.9.1.0


Regards.


From: Boris Stoyanov 
Sent: 14 December 2016 18:01:53
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.9.1.0 (RC1)

Hi,

We’ve currently have a plan for upgrade testing covering the following 
scenarios:
I’ve tried upgrading from 4.5.2.2 to 4.9.1, but got the following exception:

2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
Schema upgrade from 4.5.1 to 4.6.0
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2016-12-13 14:37:28,128 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) ALTER 
TABLE `cloud`.`snapshots` ADD COLUMN `min_iops` bigint(20) unsigned COMMENT 
'Minimum IOPS'
2016-12-13 14:37:28,135 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error 
executing: ALTER TABLE `cloud`.`snapshots` ADD COLUMN `min_iops` bigint(20) 
unsigned COMMENT 'Minimum IOPS'
2016-

[GitHub] cloudstack issue #873: CLOUDSTACK-8896: allocated percentage of storage pool...

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/873
  
@karuturi can you make suggested changes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1749: CLOUDSTACK-9619: Updates for SAN-assisted snapshots

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1749
  
Packaging result: âcentos6 âcentos7 âdebian. JID-395


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1749: CLOUDSTACK-9619: Updates for SAN-assisted snapshots

2016-12-14 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1749
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1749: CLOUDSTACK-9619: Updates for SAN-assisted snapshots

2016-12-14 Thread rhtyd

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1749
  
@blueorangutan test


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1519: Cloudstack 9339: Virtual Routers do not handle Multi...

2016-12-14 Thread murali-reddy

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1519
  
@dsclose #1659 is merged, so you can close this PR if you wish. Though 
issue related to redundant VR fixed by commit d582358, bf285e1  in this PR are 
not addressed by #1659, and still a open issue.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

42 matches

Mail list logo