Re: Ceph RBD related host agent segfault

[Aaron Hurt]

> On Jul 8, 2016, at 2:53 AM, Wido den Hollander  wrote:
> 
> 
>> Op 7 juli 2016 om 6:35 schreef Aaron Hurt :
>> 
>> 
>> 
>>> On Jul 6, 2016, at 5:14 PM, Wido den Hollander  wrote:
>>> 
 
 Op 6 juli 2016 om 16:18 schreef Aaron Hurt >:
 
 
 
> On Jul 2, 2016, at 11:37 AM, Wido den Hollander  > wrote:
> 
>> 
>> Op 30 juni 2016 om 18:29 schreef Aaron Hurt >  >>:
>> 
>> 
>> In preparation to roll a new platform built on 4.8 with a Ceph storage 
>> backend we’ve been encountering segfaults that appear to be related to 
>> snapshot operations via java-jados (librbd) on the host agent.  We’ve 
>> been able to isolate this to two possible places in the code:
>> 
>> lines ~866-875 in 
>> plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/LibvirtStorageAdaptor.java
>> 
>>  for (RbdSnapInfo snap : snaps) {
>>  if (image.snapIsProtected(snap.name)) {
>>  s_logger.debug("Unprotecting snapshot " + 
>> pool.getSourceDir() + "/" + uuid + "@" + snap.name);
>>  image.snapUnprotect(snap.name);
>>  } else {
>>  s_logger.debug("Snapshot " + pool.getSourceDir() + 
>> "/" + uuid + "@" + snap.name + " is not protected.");
>>  }
>>  s_logger.debug("Removing snapshot " + 
>> pool.getSourceDir() + "/" + uuid + "@" + snap.name);
>>  image.snapRemove(snap.name);
>>  }
>> 
>> Should we be checking if the unprotect actually failed/succeeded before 
>> attempting to remove the snapshot?
>> 
>> Code from PR #1230 (https://github.com/apache/cloudstack/pull/1230 
>>  
>> > > 
>> >  
>> > >>) duplicates some of 
>> this functionality and there doesn’t seem to be any protection 
>> preventing deletePhysicalDisk and the cleanup routine being run 
>> simultaneously.
>> 
>> 
>> To Reproduce (with ceph/rbd primary storage)
>> 
>> 1.  Set global concurrent.snapshots.threshold.perhost to the default 
>> NULL value
>> 2.  Set global snapshot.poll.interval and storage.cleanup.interval to a 
>> low interval … 10 seconds
>> 3.  Restart management server
>> 4.  Deploy several VMs from templates
>> 5.  Destroy+expunge the VMs after they are running
>> 6.  Observe segfaults in management server
>> 
>> 
>> Workaround
>> 
>> We’ve been able to eliminate the segfaults of the host agent in our 
>> testing by simply setting concurrent.snapshots.threshold.perhost to 1 
>> even with the decreased poll intervals.
>> 
>> Segfault Logs
>> 
>> https://slack-files.com/T0RJECUV7-F1M39K4F5-f9c6b3986d 
>>  
>> > > 
>> >  
>> > >>
>> 
>> https://slack-files.com/T0RJECUV7-F1KCTRNNN-8d36665b56 
>>  
>> > > 
>> >  
>> > >>
>> 
>> We would really appreciate any feedback and/or confirmation from the 
>> community around the above issues.  I’d also be happy to provide any 
>> additional information needed to get this addressed.
> 
> What seems to be happening is that it failed to unprotect the snapshot of 
> the volume. This could have various reasons, for example if there is a 
> child image of the snapshot. I don't think it's the case however.
> 
> It could still be that it tries to remove the master/golden image from 
> the template while it still has childs attached to that snapshot.

Re: [Feature Request] VM Snapshot based on KVM+Ceph

[Paul Shadwell]

This is a feature that has been missing from Cloudstack since the beginning 
when using KVM as the hypervisor. 
It's been asked for many times but still no support. 
This would be a huge plus for Cloudstack if this feature was added and make it 
a much more viable product for end users. 
KVM is usually chosen because 1: it's free 2: it has many features that make it 
a much better choice for large installations. 
Many have ended up either writing their own VM snapshot solution, or simply 
hiding the icon from the customer. 
I'm surprised that after years of waiting for this feature to be added, it's 
still missing. 
I know it's not totally the Cloudstack Dev team's fault that VM Snapshots are 
missing from KVM support but I do think this is a list opportunity for a big 
win if they did something about it. 

Just my 2 penneth on this subject that has plagued me on a daily basis 
supporting Cloudstack installs. 

Regards
Paul


> On Jul 12, 2016, at 05:19, ilya  wrote:
> 
> Just FYI:
> 
> You can ask on this list for sponsored feature development if this is
> something that needs prompt resolution.
> 
> Regards
> ilya
> 
>> On 7/8/16 7:07 PM, 吕海蛟 wrote:
>> Hi,  Developers
>> 
>> 
>> 
>> We deployed ACS+KVM+Ceph in our environment.  Everything looks fine
>> except the VM snapshot feature (not volume backup) is missing in current
>> ACS version which seems only supported by XenServer/ESXi.
>> 
>> 
>> 
>> Wondering if we can have this on the roadmap as well.  @Wido, do you
>> have any plan ?
>> 
>> 
>> 
>> Thanks !
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> private cloud2  *We Deliver Enterprise-Grade Cloud !*
>> 
>> --
>> 
>> *吕海蛟*
>> 
>> *Product Engineering & Innovation Center (PEIC)*
>> 
>> *华胜蓝泰科技（天津）有限责任公司*
>> 
>> * *
>> 
>> *上海闵行区合川路**2679**号虹桥国际商务广场**B**栋**601**室*
>> 
>> *邮编：**201103*
>> 
>> *Office: +86-21-62351222*
>> 
>> *Mobile: +86-18602198181*
>> 
>> 
>> 
>> 
>> 

Re: [Feature Request] VM Snapshot based on KVM+Ceph

[ilya]

Just FYI:

You can ask on this list for sponsored feature development if this is
something that needs prompt resolution.

Regards
ilya

On 7/8/16 7:07 PM, 吕海蛟 wrote:
> Hi,  Developers
> 
>  
> 
> We deployed ACS+KVM+Ceph in our environment.  Everything looks fine
> except the VM snapshot feature (not volume backup) is missing in current
> ACS version which seems only supported by XenServer/ESXi.
> 
>  
> 
> Wondering if we can have this on the roadmap as well.  @Wido, do you
> have any plan ?
> 
>  
> 
> Thanks !
> 
>  
> 
>  
> 
>  
> 
>  
> 
> private cloud2  *We Deliver Enterprise-Grade Cloud !*
> 
> --
> 
> *吕海蛟*
> 
> *Product Engineering & Innovation Center (PEIC)*
> 
> *华胜蓝泰科技（天津）有限责任公司*
> 
> * *
> 
> *上海闵行区合川路**2679**号虹桥国际商务广场**B**栋**601**室*
> 
> *邮编：**201103*
> 
> *Office: +86-21-62351222*
> 
> *Mobile: +86-18602198181*
> 
>  
> 
>  
> 

RE: [VOTE] Apache Cloudstack 4.9.0 RC1

[Sean Lair]

Hi all,

One small comment since strongSwan didn't make it into 4.9.  There is still a 
very simple bug in enabling PFS for site-to-site VPNs.  The code checks the 
Dead Peer Detection (DPD) variable instead of the PFS variable when determining 
whether or not to enable PFS for the site-to-site VPN.

Here is the 1-line of code that is broken.  You can see how it refers to dpd to 
set pfs.

file.addeq(" pfs=%s" % CsHelper.bool_to_yn(obj['dpd']))

This pull request fixes the issue, but was not merged since we were going to 
strongSwan.  It would be nice if this bug fix was put into 4.9.0

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


Thanks!
Sean

-Original Message-
From: Will Stevens [mailto:williamstev...@gmail.com] 
Sent: Wednesday, July 6, 2016 3:52 PM
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache Cloudstack 4.9.0 RC1

Hi All,

I've created a 4.9.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.0-RC20160706T1546
Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb

I will be updating the Release Notes with the changes in this release tomorrow. 
 If the RC changes, I can adapt the release notes after.

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/

PGP release keys (signed using CB818F64):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

Vote will be open for 72 hours.

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)

Thanks,

Will

[GitHub] cloudstack issue #1608: Cleanup RBD contexts after exceptions to prevent pot...

[leprechau]

Github user leprechau commented on the issue:

https://github.com/apache/cloudstack/pull/1608
  
Tests passed.


---
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 #1600: Support Backup of Snapshots for Managed Storage

[syed]

Github user syed commented on the issue:

https://github.com/apache/cloudstack/pull/1600
  
@mike-tutkowski I think the `Destroyed` state should suffice. 


---
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: [GitHub] cloudstack issue #1600: Support Backup of Snapshots for Managed Storage

[Tutkowski, Mike]

Well...it does say it's in the Destroyed state.

I thought we removed these kinds of rows from this table, but it looks like we 
don't.

That being the case, I think we can ignore what I asked for here.

From: mike-tutkowski 
Sent: Monday, July 11, 2016 1:39 PM
To: dev@cloudstack.apache.org
Subject: [GitHub] cloudstack issue #1600: Support Backup of Snapshots for 
Managed Storage

Github user mike-tutkowski commented on the issue:

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

A comment:


I have observed that the SR that was previously not being detached from 
XenServer is now being detached with your newer version of the code.


One thing I noticed in the DB:


In the snapshot_store_ref table, we still have a row for the snapshot that 
indicates there is a version of the snapshot on primary storage. We also - 
correctly - have a row indicating that there is a version of the snapshot on 
secondary storage.


I think we should remove the row from the snapshot_store_ref table that 
links the snapshot to a version on primary storage.



From: Tutkowski, Mike
Sent: Monday, July 4, 2016 1:24 PM
To: apache/cloudstack
Cc: apache/cloudstack; Mention
Subject: Re: [apache/cloudstack] Support Backup of Snapshots for Managed 
Storage (#1600)

My mistake. I forgot that I added that a while ago. :)

On Jul 4, 2016, at 12:40 PM, Syed Mushtaq Ahmed 
> wrote:


@mike-tutkowski , the list snapshot 
already returns the loacationType. I think you've already added that.

-
You are receiving this because you were mentioned.
Reply to this email directly, view it on 
GitHub, 
or mute the 
thread.



---
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 #1600: Support Backup of Snapshots for Managed Storage

[mike-tutkowski]

Github user mike-tutkowski commented on the issue:

https://github.com/apache/cloudstack/pull/1600
  
A comment:


I have observed that the SR that was previously not being detached from 
XenServer is now being detached with your newer version of the code.


One thing I noticed in the DB:


In the snapshot_store_ref table, we still have a row for the snapshot that 
indicates there is a version of the snapshot on primary storage. We also - 
correctly - have a row indicating that there is a version of the snapshot on 
secondary storage.


I think we should remove the row from the snapshot_store_ref table that 
links the snapshot to a version on primary storage.



From: Tutkowski, Mike
Sent: Monday, July 4, 2016 1:24 PM
To: apache/cloudstack
Cc: apache/cloudstack; Mention
Subject: Re: [apache/cloudstack] Support Backup of Snapshots for Managed 
Storage (#1600)

My mistake. I forgot that I added that a while ago. :)

On Jul 4, 2016, at 12:40 PM, Syed Mushtaq Ahmed 
> wrote:


@mike-tutkowski , the list snapshot 
already returns the loacationType. I think you've already added that.

-
You are receiving this because you were mentioned.
Reply to this email directly, view it on 
GitHub, 
or mute the 
thread.



---
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 #1609: [CLOUDSTACK-9430] Added fix for adding/editin...

[pdube]

GitHub user pdube opened a pull request:

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

[CLOUDSTACK-9430] Added fix for adding/editing Network ACL rule ordering

BUG: https://issues.apache.org/jira/browse/CLOUDSTACK-9430

The issue occurred because all of the ACL rules get inserted before the old 
ones. Then, the cleanup deletes the duplicate rows, and leaves any new rule in 
front of the old ones.

Here is an example with a simplified iptables view for ACL
Ex: adding a rule 4
before add:
1,2,3

during add:
1',2',3',4',1,2,3

after add:
4',1,2,3

After fix:
before add:
1,2,3

during add:
1,2,3,1',2',3',4'

after add:
1',2',3',4'


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

$ git pull https://github.com/pdube/cloudstack network-acl-add-order

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

https://github.com/apache/cloudstack/pull/1609.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 #1609


commit 6dd6ef0c9a30f128657de22fa8b6ea8ab5daa133
Author: Patrick Dube 
Date:   2016-07-11T19:12:41Z

Added fix for adding/editing Network ACL rule ordering




---
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 #1608: Cleanup RBD contexts after exceptions to prev...

[leprechau]

Github user leprechau closed the pull request at:

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


---
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 #1608: Cleanup RBD contexts after exceptions to prev...

[leprechau]

GitHub user leprechau reopened a pull request:

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

Cleanup RBD contexts after exceptions to prevent potential agent crash

We noticed that when an exception occurs within the cleanup loop inside
the deletePhysicalDisk routine that the previously allocated contexts
are not cleaned up.  This seemed to cause an eventual crash of the host
agent after multiple exceptions within the loop.

In addition to ensuring the contexts are always freed we also improved
the logging when exceptions do occur to include the actual return code
from the underlying library in deletePhysicalDisk and deleteSnapshot.

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

$ git pull https://github.com/myENA/cloudstack upstream/context-cleanup

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

https://github.com/apache/cloudstack/pull/1608.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 #1608


commit 44491448e3811cfcebe5c3aeee72ba7a01948cda
Author: Aaron Hurt 
Date:   2016-07-09T03:57:06Z

Cleanup rbd contexts and improve exception logging

We noticed that when an exception occurs within the cleanup loop inside
the deletePhysicalDisk routine that the previously allocated contexts
are not cleaned up.  This seemed to cause an eventual crash of the host
agent after multiple exceptions within the loop.

In addition to ensuring the contexts are always freed we also improved
the logging when exceptions do occur to include the actual return code
from the underlying library in deletePhysicalDisk and deleteSnapshot.

commit c8fce3ff31c1437681f1c2b32864eb2d34b66be5
Author: Aaron Hurt 
Date:   2016-07-11T15:49:43Z

improve logging readability




---
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.0 RC1

[Tutkowski, Mike]

This one isn't a show stopper, but I noticed when setting up a new cloud in a 
XenServer environment that an SR remains that points to secondary storage after 
the system VMs have been deployed.

http://imgur.com/5pEnkm9

We had chatted a bit about this on the list a while back and it seemed like 
this problem was solved, but now it seems it has not been.

In any event, this does not change my +1. I just wanted to note this.

From: Tutkowski, Mike 
Sent: Saturday, July 9, 2016 12:22 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1

I am +1 based on having successfully run the following tests:

TestVolumes.py (once using newly introduced XenSever SR-resigning logic and 
once without doing so)
TestSnapshots.py
TestVMSnapshots.py
TestAddRemoveHosts.py

Test Details:

TestVolumes (using XenServer SR-resigning logic):

test_00_check_template_cache (TestVolumes.TestVolumes) ... === TestName: 
test_00_check_template_cache | Status : SUCCESS ===
ok
Attach a volume to a stopped virtual machine, then start VM ... === TestName: 
test_01_attach_new_volume_to_stopped_VM | Status : SUCCESS ===
ok
Attach, detach, and attach volume to a running VM ... === TestName: 
test_02_attach_detach_attach_volume | Status : SUCCESS ===
ok
Attach volume to running VM, then reboot. ... === TestName: 
test_03_attached_volume_reboot_VM | Status : SUCCESS ===
ok
Detach volume from a running VM, then reboot. ... === TestName: 
test_04_detach_volume_reboot | Status : SUCCESS ===
ok
Detach volume from a stopped VM, then start. ... === TestName: 
test_05_detach_vol_stopped_VM_start | Status : SUCCESS ===
ok
Attach a volume to a stopped virtual machine, then start VM ... === TestName: 
test_06_attach_volume_to_stopped_VM | Status : SUCCESS ===
ok
Destroy and expunge VM with attached volume ... === TestName: 
test_07_destroy_expunge_VM_with_volume | Status : SUCCESS ===
ok
Delete volume that was attached to a VM and is detached now ... === TestName: 
test_08_delete_volume_was_attached | Status : SUCCESS ===
ok
Attach a data disk to a VM in one account and attach another data disk to a VM 
in another account ... === TestName: test_09_attach_volumes_multiple_accounts | 
Status : SUCCESS ===
ok
Attach more than one disk to a VM ... === TestName: 
test_10_attach_more_than_one_disk_to_VM | Status : SUCCESS ===
ok

--
Ran 11 tests in 2304.098s

OK

TestVolumes (not using XenServer SR-resigning logic):

test_00_check_template_cache (TestVolumes.TestVolumes) ... === TestName: 
test_00_check_template_cache | Status : SUCCESS ===
ok
Attach a volume to a stopped virtual machine, then start VM ... === TestName: 
test_01_attach_new_volume_to_stopped_VM | Status : SUCCESS ===
ok
Attach, detach, and attach volume to a running VM ... === TestName: 
test_02_attach_detach_attach_volume | Status : SUCCESS ===
ok
Attach volume to running VM, then reboot. ... === TestName: 
test_03_attached_volume_reboot_VM | Status : SUCCESS ===
ok
Detach volume from a running VM, then reboot. ... === TestName: 
test_04_detach_volume_reboot | Status : SUCCESS ===
ok
Detach volume from a stopped VM, then start. ... === TestName: 
test_05_detach_vol_stopped_VM_start | Status : SUCCESS ===
ok
Attach a volume to a stopped virtual machine, then start VM ... === TestName: 
test_06_attach_volume_to_stopped_VM | Status : SUCCESS ===
ok
Destroy and expunge VM with attached volume ... === TestName: 
test_07_destroy_expunge_VM_with_volume | Status : SUCCESS ===
ok
Delete volume that was attached to a VM and is detached now ... === TestName: 
test_08_delete_volume_was_attached | Status : SUCCESS ===
ok
Attach a data disk to a VM in one account and attach another data disk to a VM 
in another account ... === TestName: test_09_attach_volumes_multiple_accounts | 
Status : SUCCESS ===
ok
Attach more than one disk to a VM ... === TestName: 
test_10_attach_more_than_one_disk_to_VM | Status : SUCCESS ===
ok

--
Ran 11 tests in 2023.939s

OK

TestSnapshots:

test_01_create_volume_snapshot_using_sf_snapshot (TestSnapshots.TestSnapshots) 
... === TestName: test_01_create_volume_snapshot_using_sf_snapshot | Status : 
SUCCESS ===
ok
test_02_create_volume_snapshot_using_sf_volume (TestSnapshots.TestSnapshots) 
... === TestName: test_02_create_volume_snapshot_using_sf_volume | Status : 
SUCCESS ===
ok
test_03_create_volume_snapshot_using_sf_volume_and_sf_snapshot 
(TestSnapshots.TestSnapshots) ... === TestName: 
test_03_create_volume_snapshot_using_sf_volume_and_sf_snapshot | Status : 
SUCCESS ===
ok

--
Ran 3 tests in 7311.959s

OK

TestVMSnapshots:

test_01_take_VM_snapshot (TestVMSnapshots.TestVMSnapshots) ... === TestName: 
test_01_take_VM_snapshot | Status : SUCCESS ===
ok

RE: [VOTE] Apache Cloudstack 4.9.0 RC1

[Paul Angus]

Hey Will,

I was referring to the need to add:


db.cloud.driver=jdbc:mysql

db.usage.driver=jdbc:mysql

db.simulator.driver=jdbc:mysql

to db.properties when upgrading.

Asking admins to add this manually won’t give the impression of a 
‘well-packaged’ product.  And I suspect will end up like the manually 
encrypting vmware passwords step, which was required for one upgrade, and now 
clients constantly ask us if they need to repeat the step, because its carried 
forward to every upgrade note.


Kind regards,

Paul Angus

From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On Behalf Of 
Will Stevens
Sent: 11 July 2016 14:10
To: dev@cloudstack.apache.org; Paul Angus 
Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1

Hi Paul,
Can you review the discussion here to see if it clears anything up: 
https://github.com/apache/cloudstack/pull/1489#issuecomment-215479369

Can you help me understand what you are expecting the functionality to be and 
what you are experiencing?

Thanks,

Will STEVENS
Lead Developer

CloudOps | Cloud Solutions Experts
420 rue Guy | Montreal | Quebec | H3J 1S6
w cloudops.com | tw @CloudOps_

On Sun, Jul 10, 2016 at 8:06 AM, Paul Angus 
> wrote:
Guys,

Is it not possible to add the additional entries into db.properties when 
CloudStack is upgrading rather than manually? If it is possible, then manually 
intervention is a -1 in my book.
Sure it's not a big fix required - but it's still required for CloudStack to 
work in a slick manner.  We're trying to improve the user experience.

Kind regards,

Paul Angus

paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Milamber [mailto:milam...@apache.org]
Sent: 10 July 2016 12:06
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1

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.0RC1 (adv net) on Ubuntu 14.04.4 + 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 sucess too (create 
network, register templates, create vm, ip, firewall rule)

2/ Test upgrade from 4.7.1 to 4.9.0RC1 : OK with the same remarks than Wido 
(need to add JDBC driver type in db.properties)

3/ Tests of all localizations of Web UI of 4.9RC1 : Localization works well 
except Spanish: the Web UI won't display due of 2 localization strings with a 
escaped quote (from Transifex)
'label.number.of.system.vms': 'Número de VM\\'s del Systema',
'label.vm.state': 'Estado de VM\\'s',
Fixed in the PR1583
https://github.com/apache/cloudstack/pull/1583


Perhaps add in the Release notes this 2 issues (jdbc type & spanish l10n)

Thanks to the RM.

Milamber



On 06/07/2016 20:52, Will Stevens wrote:
> Hi All,
>
> I've created a 4.9.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.0-RC20160706T1546
> Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
>
> I will be updating the Release Notes with the changes in this release
> tomorrow.  If the RC changes, I can adapt the release notes after.
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
>
> PGP release keys (signed using CB818F64):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours.
>
> 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)
>
> Thanks,
>
> Will
>

Re: [VOTE] Apache Cloudstack 4.9.0 RC1

[Will Stevens]

Great, I am working on the Release Notes (and upgrade details) right now,
so I will make sure that gets in there.  Thanks for confirming.  :)

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Mon, Jul 11, 2016 at 1:45 PM, Nux!  wrote:

> Will,
>
> Yes, indeed, it should be added to Upgrade notes.
>
> Thanks!
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Will Stevens" 
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 11 July, 2016 18:15:57
> > Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
>
> > Thanks Nux.
> >
> > Should the following information be added to the Release Notes and the
> > Upgrade documentation?
> >
> > Make sure these are added to db.properties:
> >
> > db.cloud.driver=jdbc:mysql
> > db.usage.driver=jdbc:mysql
> > db.simulator.driver=jdbc:mysql
> >
> > I had a look at the files and they seem to have the correct values.  EG:
> >
> https://github.com/apache/cloudstack/blob/master/utils/conf/db.properties
> >
> > What do you guys think?
> >
> > Cheers,
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Mon, Jul 11, 2016 at 12:45 PM, Nux!  wrote:
> >
> >> Other than using Wido's quick fix in db.properties, everything else
> checks
> >> out as far as I can tell.
> >>
> >>
> >> +1 (binding)
> >>
> >>
> >> Good job
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> - Original Message -
> >> > From: "Nux!" 
> >> > To: dev@cloudstack.apache.org
> >> > Sent: Monday, 11 July, 2016 16:08:19
> >> > Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
> >>
> >> > Cool, thanks for clarifying. Too bad Strongswan didn't make it.
> >> > I'll test shortly.
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
> >> >
> >> > - Original Message -
> >> >> From: "Will Stevens" 
> >> >> To: dev@cloudstack.apache.org
> >> >> Sent: Monday, 11 July, 2016 16:07:02
> >> >> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
> >> >
> >> >> Yes, we did not change the systemvm templates because features like
> >> >> strongswan, etc, did not make it into this release...
> >> >>
> >> >> *Will STEVENS*
> >> >> Lead Developer
> >> >>
> >> >> *CloudOps* *| *Cloud Solutions Experts
> >> >> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >> >> w cloudops.com *|* tw @CloudOps_
> >> >>
> >> >> On Mon, Jul 11, 2016 at 11:01 AM, Nux!  wrote:
> >> >>
> >> >>> I take it we're still to use the old 4.6 systemvm template?
> >> >>>
> >> >>> --
> >> >>> Sent from the Delta quadrant using Borg technology!
> >> >>>
> >> >>> Nux!
> >> >>> www.nux.ro
> >> >>>
> >> >>> - Original Message -
> >> >>> > From: "Will Stevens" 
> >> >>> > To: dev@cloudstack.apache.org
> >> >>> > Sent: Wednesday, 6 July, 2016 21:52:14
> >> >>> > Subject: [VOTE] Apache Cloudstack 4.9.0 RC1
> >> >>>
> >> >>> > Hi All,
> >> >>> >
> >> >>> > I've created a 4.9.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.0-RC20160706T1546
> >> >>> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
> >> >>> >
> >> >>> > I will be updating the Release Notes with the changes in this
> release
> >> >>> > tomorrow.  If the RC changes, I can adapt the release notes after.
> >> >>> >
> >> >>> > Source release (checksums and signatures are available at the same
> >> >>> > location):
> >> >>> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
> >> >>> >
> >> >>> > PGP release keys (signed using CB818F64):
> >> >>> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >> >>> >
> >> >>> > Vote will be open for 72 hours.
> >> >>> >
> >> >>> > 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)
> >> >>> >
> >> >>> > Thanks,
> >> >>> >
> >> > >> > Will
>

Re: [VOTE] Apache Cloudstack 4.9.0 RC1

[Nux!]

Will,

Yes, indeed, it should be added to Upgrade notes.

Thanks!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Will Stevens" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 11 July, 2016 18:15:57
> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1

> Thanks Nux.
> 
> Should the following information be added to the Release Notes and the
> Upgrade documentation?
> 
> Make sure these are added to db.properties:
> 
> db.cloud.driver=jdbc:mysql
> db.usage.driver=jdbc:mysql
> db.simulator.driver=jdbc:mysql
> 
> I had a look at the files and they seem to have the correct values.  EG:
> https://github.com/apache/cloudstack/blob/master/utils/conf/db.properties
> 
> What do you guys think?
> 
> Cheers,
> 
> *Will STEVENS*
> Lead Developer
> 
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> On Mon, Jul 11, 2016 at 12:45 PM, Nux!  wrote:
> 
>> Other than using Wido's quick fix in db.properties, everything else checks
>> out as far as I can tell.
>>
>>
>> +1 (binding)
>>
>>
>> Good job
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>> > From: "Nux!" 
>> > To: dev@cloudstack.apache.org
>> > Sent: Monday, 11 July, 2016 16:08:19
>> > Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
>>
>> > Cool, thanks for clarifying. Too bad Strongswan didn't make it.
>> > I'll test shortly.
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
>> >
>> > - Original Message -
>> >> From: "Will Stevens" 
>> >> To: dev@cloudstack.apache.org
>> >> Sent: Monday, 11 July, 2016 16:07:02
>> >> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
>> >
>> >> Yes, we did not change the systemvm templates because features like
>> >> strongswan, etc, did not make it into this release...
>> >>
>> >> *Will STEVENS*
>> >> Lead Developer
>> >>
>> >> *CloudOps* *| *Cloud Solutions Experts
>> >> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> >> w cloudops.com *|* tw @CloudOps_
>> >>
>> >> On Mon, Jul 11, 2016 at 11:01 AM, Nux!  wrote:
>> >>
>> >>> I take it we're still to use the old 4.6 systemvm template?
>> >>>
>> >>> --
>> >>> Sent from the Delta quadrant using Borg technology!
>> >>>
>> >>> Nux!
>> >>> www.nux.ro
>> >>>
>> >>> - Original Message -
>> >>> > From: "Will Stevens" 
>> >>> > To: dev@cloudstack.apache.org
>> >>> > Sent: Wednesday, 6 July, 2016 21:52:14
>> >>> > Subject: [VOTE] Apache Cloudstack 4.9.0 RC1
>> >>>
>> >>> > Hi All,
>> >>> >
>> >>> > I've created a 4.9.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.0-RC20160706T1546
>> >>> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
>> >>> >
>> >>> > I will be updating the Release Notes with the changes in this release
>> >>> > tomorrow.  If the RC changes, I can adapt the release notes after.
>> >>> >
>> >>> > Source release (checksums and signatures are available at the same
>> >>> > location):
>> >>> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
>> >>> >
>> >>> > PGP release keys (signed using CB818F64):
>> >>> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >>> >
>> >>> > Vote will be open for 72 hours.
>> >>> >
>> >>> > 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)
>> >>> >
>> >>> > Thanks,
>> >>> >
>> > >> > Will

Re: [VOTE] Apache Cloudstack 4.9.0 RC1

[Will Stevens]

Thanks Nux.

Should the following information be added to the Release Notes and the
Upgrade documentation?

Make sure these are added to db.properties:

db.cloud.driver=jdbc:mysql
db.usage.driver=jdbc:mysql
db.simulator.driver=jdbc:mysql

I had a look at the files and they seem to have the correct values.  EG:
https://github.com/apache/cloudstack/blob/master/utils/conf/db.properties

What do you guys think?

Cheers,

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Mon, Jul 11, 2016 at 12:45 PM, Nux!  wrote:

> Other than using Wido's quick fix in db.properties, everything else checks
> out as far as I can tell.
>
>
> +1 (binding)
>
>
> Good job
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Nux!" 
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 11 July, 2016 16:08:19
> > Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
>
> > Cool, thanks for clarifying. Too bad Strongswan didn't make it.
> > I'll test shortly.
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "Will Stevens" 
> >> To: dev@cloudstack.apache.org
> >> Sent: Monday, 11 July, 2016 16:07:02
> >> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
> >
> >> Yes, we did not change the systemvm templates because features like
> >> strongswan, etc, did not make it into this release...
> >>
> >> *Will STEVENS*
> >> Lead Developer
> >>
> >> *CloudOps* *| *Cloud Solutions Experts
> >> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >> w cloudops.com *|* tw @CloudOps_
> >>
> >> On Mon, Jul 11, 2016 at 11:01 AM, Nux!  wrote:
> >>
> >>> I take it we're still to use the old 4.6 systemvm template?
> >>>
> >>> --
> >>> Sent from the Delta quadrant using Borg technology!
> >>>
> >>> Nux!
> >>> www.nux.ro
> >>>
> >>> - Original Message -
> >>> > From: "Will Stevens" 
> >>> > To: dev@cloudstack.apache.org
> >>> > Sent: Wednesday, 6 July, 2016 21:52:14
> >>> > Subject: [VOTE] Apache Cloudstack 4.9.0 RC1
> >>>
> >>> > Hi All,
> >>> >
> >>> > I've created a 4.9.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.0-RC20160706T1546
> >>> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
> >>> >
> >>> > I will be updating the Release Notes with the changes in this release
> >>> > tomorrow.  If the RC changes, I can adapt the release notes after.
> >>> >
> >>> > Source release (checksums and signatures are available at the same
> >>> > location):
> >>> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
> >>> >
> >>> > PGP release keys (signed using CB818F64):
> >>> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>> >
> >>> > Vote will be open for 72 hours.
> >>> >
> >>> > 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)
> >>> >
> >>> > Thanks,
> >>> >
> > >> > Will
>

Re: [VOTE] Apache Cloudstack 4.9.0 RC1

[Nux!]

Other than using Wido's quick fix in db.properties, everything else checks out 
as far as I can tell.


+1 (binding)


Good job

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 11 July, 2016 16:08:19
> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1

> Cool, thanks for clarifying. Too bad Strongswan didn't make it.
> I'll test shortly.
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Will Stevens" 
>> To: dev@cloudstack.apache.org
>> Sent: Monday, 11 July, 2016 16:07:02
>> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
> 
>> Yes, we did not change the systemvm templates because features like
>> strongswan, etc, did not make it into this release...
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>> 
>> On Mon, Jul 11, 2016 at 11:01 AM, Nux!  wrote:
>> 
>>> I take it we're still to use the old 4.6 systemvm template?
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>> - Original Message -
>>> > From: "Will Stevens" 
>>> > To: dev@cloudstack.apache.org
>>> > Sent: Wednesday, 6 July, 2016 21:52:14
>>> > Subject: [VOTE] Apache Cloudstack 4.9.0 RC1
>>>
>>> > Hi All,
>>> >
>>> > I've created a 4.9.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.0-RC20160706T1546
>>> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
>>> >
>>> > I will be updating the Release Notes with the changes in this release
>>> > tomorrow.  If the RC changes, I can adapt the release notes after.
>>> >
>>> > Source release (checksums and signatures are available at the same
>>> > location):
>>> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
>>> >
>>> > PGP release keys (signed using CB818F64):
>>> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>> >
>>> > Vote will be open for 72 hours.
>>> >
>>> > 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)
>>> >
>>> > Thanks,
>>> >
> >> > Will

Re: [VOTE] Apache Cloudstack 4.9.0 RC1

[Will Stevens]

Yes, we did not change the systemvm templates because features like
strongswan, etc, did not make it into this release...

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Mon, Jul 11, 2016 at 11:01 AM, Nux!  wrote:

> I take it we're still to use the old 4.6 systemvm template?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Will Stevens" 
> > To: dev@cloudstack.apache.org
> > Sent: Wednesday, 6 July, 2016 21:52:14
> > Subject: [VOTE] Apache Cloudstack 4.9.0 RC1
>
> > Hi All,
> >
> > I've created a 4.9.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.0-RC20160706T1546
> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
> >
> > I will be updating the Release Notes with the changes in this release
> > tomorrow.  If the RC changes, I can adapt the release notes after.
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
> >
> > PGP release keys (signed using CB818F64):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open for 72 hours.
> >
> > 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)
> >
> > Thanks,
> >
> > Will
>

Re: [VOTE] Apache Cloudstack 4.9.0 RC1

[Nux!]

I take it we're still to use the old 4.6 systemvm template?

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Will Stevens" 
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 6 July, 2016 21:52:14
> Subject: [VOTE] Apache Cloudstack 4.9.0 RC1

> Hi All,
> 
> I've created a 4.9.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.0-RC20160706T1546
> Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
> 
> I will be updating the Release Notes with the changes in this release
> tomorrow.  If the RC changes, I can adapt the release notes after.
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
> 
> PGP release keys (signed using CB818F64):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Vote will be open for 72 hours.
> 
> 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)
> 
> Thanks,
> 
> Will

Re: [VOTE] Apache Cloudstack 4.9.0 RC1

[Nux!]

Cool, thanks for clarifying. Too bad Strongswan didn't make it.
I'll test shortly.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Will Stevens" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 11 July, 2016 16:07:02
> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1

> Yes, we did not change the systemvm templates because features like
> strongswan, etc, did not make it into this release...
> 
> *Will STEVENS*
> Lead Developer
> 
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> On Mon, Jul 11, 2016 at 11:01 AM, Nux!  wrote:
> 
>> I take it we're still to use the old 4.6 systemvm template?
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>> > From: "Will Stevens" 
>> > To: dev@cloudstack.apache.org
>> > Sent: Wednesday, 6 July, 2016 21:52:14
>> > Subject: [VOTE] Apache Cloudstack 4.9.0 RC1
>>
>> > Hi All,
>> >
>> > I've created a 4.9.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.0-RC20160706T1546
>> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
>> >
>> > I will be updating the Release Notes with the changes in this release
>> > tomorrow.  If the RC changes, I can adapt the release notes after.
>> >
>> > Source release (checksums and signatures are available at the same
>> > location):
>> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
>> >
>> > PGP release keys (signed using CB818F64):
>> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >
>> > Vote will be open for 72 hours.
>> >
>> > 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)
>> >
>> > Thanks,
>> >
>> > Will

RE: [VOTE] Apache Cloudstack 4.9.0 RC1

[Wido den Hollander]

> Op 10 juli 2016 om 14:06 schreef Paul Angus :
> 
> 
> Guys,
> 
> Is it not possible to add the additional entries into db.properties when 
> CloudStack is upgrading rather than manually? If it is possible, then 
> manually intervention is a -1 in my book.
> Sure it's not a big fix required - but it's still required for CloudStack to 
> work in a slick manner.  We're trying to improve the user experience.
> 

We could to this in the postinst of the RPM and DEB packages if we would really 
want to.

Wido

> Kind regards,
> 
> Paul Angus
> 
> paul.an...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>   
>  
> 
> 
> -Original Message-
> From: Milamber [mailto:milam...@apache.org] 
> Sent: 10 July 2016 12:06
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
> 
> 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.0RC1 (adv net) on Ubuntu 14.04.4 + 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 sucess too 
> (create network, register templates, create vm, ip, firewall rule)
> 
> 2/ Test upgrade from 4.7.1 to 4.9.0RC1 : OK with the same remarks than Wido 
> (need to add JDBC driver type in db.properties)
> 
> 3/ Tests of all localizations of Web UI of 4.9RC1 : Localization works well 
> except Spanish: the Web UI won't display due of 2 localization strings with a 
> escaped quote (from Transifex)
> 'label.number.of.system.vms': 'Número de VM\\'s del Systema',
> 'label.vm.state': 'Estado de VM\\'s',
> Fixed in the PR1583
> https://github.com/apache/cloudstack/pull/1583
> 
> 
> Perhaps add in the Release notes this 2 issues (jdbc type & spanish l10n)
> 
> Thanks to the RM.
> 
> Milamber
> 
> 
> 
> On 06/07/2016 20:52, Will Stevens wrote:
> > Hi All,
> >
> > I've created a 4.9.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.0-RC20160706T1546
> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
> >
> > I will be updating the Release Notes with the changes in this release 
> > tomorrow.  If the RC changes, I can adapt the release notes after.
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
> >
> > PGP release keys (signed using CB818F64):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open for 72 hours.
> >
> > 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)
> >
> > Thanks,
> >
> > Will
> >
>

[GitHub] cloudstack issue #1607: SSVM downloader now handles redirects properly.

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1607
  
Indeed, looke good to me, is there a simple way to test this?


---
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.0 RC1

[Will Stevens]

Hi Paul,
Can you review the discussion here to see if it clears anything up:
https://github.com/apache/cloudstack/pull/1489#issuecomment-215479369

Can you help me understand what you are expecting the functionality to be
and what you are experiencing?

Thanks,

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Sun, Jul 10, 2016 at 8:06 AM, Paul Angus 
wrote:

> Guys,
>
> Is it not possible to add the additional entries into db.properties when
> CloudStack is upgrading rather than manually? If it is possible, then
> manually intervention is a -1 in my book.
> Sure it's not a big fix required - but it's still required for CloudStack
> to work in a slick manner.  We're trying to improve the user experience.
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Milamber [mailto:milam...@apache.org]
> Sent: 10 July 2016 12:06
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
>
> 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.0RC1 (adv net) on Ubuntu 14.04.4 + 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 sucess too (create network, register templates, create vm, ip,
> firewall rule)
>
> 2/ Test upgrade from 4.7.1 to 4.9.0RC1 : OK with the same remarks than
> Wido (need to add JDBC driver type in db.properties)
>
> 3/ Tests of all localizations of Web UI of 4.9RC1 : Localization works
> well except Spanish: the Web UI won't display due of 2 localization strings
> with a escaped quote (from Transifex)
> 'label.number.of.system.vms': 'Número de VM\\'s del Systema',
> 'label.vm.state': 'Estado de VM\\'s',
> Fixed in the PR1583
> https://github.com/apache/cloudstack/pull/1583
>
>
> Perhaps add in the Release notes this 2 issues (jdbc type & spanish l10n)
>
> Thanks to the RM.
>
> Milamber
>
>
>
> On 06/07/2016 20:52, Will Stevens wrote:
> > Hi All,
> >
> > I've created a 4.9.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.0-RC20160706T1546
> > Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
> >
> > I will be updating the Release Notes with the changes in this release
> > tomorrow.  If the RC changes, I can adapt the release notes after.
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
> >
> > PGP release keys (signed using CB818F64):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open for 72 hours.
> >
> > 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)
> >
> > Thanks,
> >
> > Will
> >
>
>

Marvin - test_data.py

[Paul Angus]

Hi all,

The default test data has the following entries - does anyone have copies of 
these images which I can download and host locally to our Trillian deployment?

"templateregister1": {
"displaytext": "win8withpv",
"name": "win8withpv",
"passwordenabled": False,
"url": "http://pleaseupdateURL/dummy.vhd;,
"format": "VHD",
"ostype": "Windows 8 (64-bit)",
"ispublic": "true",
"hypervisor": "XenServer"
},
"Windows 8 (64-bit)": {
"displaytext": "Windows 8 (64-bit)",
"name": "win8withpv",
"passwordenabled": False,
"url": "http://pleaseupdateURL/dummy.vhd;,
"format": "VHD",
"ostype": "Windows 8 (64-bit)",
"ispublic": "true",
"hypervisor": "XenServer"
},
"Windows Server 2012 (64-bit)": {
"displaytext": "Windows Server 2012 (64-bit)",
"name": "Windows Server 2012 (64-bit)",
"passwordenabled": False,
"url": "http://pleaseupdateURL/dummy.vhd;,
"format": "VHD",
"ostype": "Windows Server 2012 (64-bit)",
"ispublic": "true",
"hypervisor": "XenServer"
},

"Windows 7 (64-bit)": {
"displaytext": "Windows 7 (64-bit)",
"name": "Windows 7 (64-bit)",
"passwordenabled": False,
"url": "http://pleaseupdateURL/dummy.vhd;,
"format": "VHD",
"ostype": "Windows 7 (64-bit)",
"ispublic": "true",
"hypervisor": "XenServer"
},


Kind regards,

Paul Angus


paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

[GitHub] cloudstack issue #1608: Cleanup RBD contexts after exceptions to prevent pot...

[leprechau]

Github user leprechau commented on the issue:

https://github.com/apache/cloudstack/pull/1608
  
Absolutely, I'll add a bit more to the logging when I get into the office.


---
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.0 RC1

[John Burwell]

Paul,

Is this condition a regression in previous behavior?

Thanks,
-John

> 
john.burw...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
@shapeblue
  
 

On Jul 10, 2016, at 8:06 AM, Paul Angus  wrote:
> 
> Guys,
> 
> Is it not possible to add the additional entries into db.properties when 
> CloudStack is upgrading rather than manually? If it is possible, then 
> manually intervention is a -1 in my book.
> Sure it's not a big fix required - but it's still required for CloudStack to 
> work in a slick manner.  We're trying to improve the user experience.
> 
> Kind regards,
> 
> Paul Angus
> 
> paul.an...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
> 
> 
> 
> 
> -Original Message-
> From: Milamber [mailto:milam...@apache.org] 
> Sent: 10 July 2016 12:06
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC1
> 
> 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.0RC1 (adv net) on Ubuntu 14.04.4 + 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 sucess too 
> (create network, register templates, create vm, ip, firewall rule)
> 
> 2/ Test upgrade from 4.7.1 to 4.9.0RC1 : OK with the same remarks than Wido 
> (need to add JDBC driver type in db.properties)
> 
> 3/ Tests of all localizations of Web UI of 4.9RC1 : Localization works well 
> except Spanish: the Web UI won't display due of 2 localization strings with a 
> escaped quote (from Transifex)
> 'label.number.of.system.vms': 'Número de VM\\'s del Systema',
> 'label.vm.state': 'Estado de VM\\'s',
> Fixed in the PR1583
> https://github.com/apache/cloudstack/pull/1583
> 
> 
> Perhaps add in the Release notes this 2 issues (jdbc type & spanish l10n)
> 
> Thanks to the RM.
> 
> Milamber
> 
> 
> 
> On 06/07/2016 20:52, Will Stevens wrote:
>> Hi All,
>> 
>> I've created a 4.9.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.0-RC20160706T1546
>> Commit: 643f75aa9150156b1fb05f339a338614fc7ad3fb
>> 
>> I will be updating the Release Notes with the changes in this release 
>> tomorrow.  If the RC changes, I can adapt the release notes after.
>> 
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.9.0/
>> 
>> PGP release keys (signed using CB818F64):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> 
>> Vote will be open for 72 hours.
>> 
>> 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)
>> 
>> Thanks,
>> 
>> Will
>> 
> 

Re: Opportunity to contribute in Apache CloudStack

[Jainesh Patel]

Hello Sir,

Can you please tell us more about the proposal to bring pure Xen in as
fully supported hypervisor and your project in security space?

Regards,
TheAtom

On Wed, Jul 6, 2016 at 4:15 PM, Tim Mackey  wrote:

> Jainesh, and by extension all members of TheAtom, welcome to the CloudStack
> project. You'll want to join the development list (
> dev@cloudstack.apache.org),
> and look at the contributing section here:
> https://github.com/apache/cloudstack and here:
> https://cloudstack.apache.org/developers.html.
>
> A proposal was put to the dev list for the 2016-2017 roadmap earlier this
> week (
>
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201607.mbox/%3cc10c1a0c-4d57-4fb4-8812-b20aa1ea8...@shapeblue.com%3E
> ). That would probably be an excellent starting point to see the direction
> of the project overall. As with most projects, its probably best to start
> small and fix a few issues before starting in on something substantial.
>
> For something more substantial, and depending upon your skill set, there
> has been an open proposal to bring pure Xen in as fully supported
> hypervisor. Knowing a bit of what's involved there, it might fit well with
> your time frame, plus I know there are some who would welcome that work. I
> also have a smaller project in the security space which might be
> interesting, but haven't made the proposal to the list yet. In all cases,
> the hope would be that you'd continue to be involved with the project upon
> project completion.
>
> (cross posted to dev@ to keep me honest - suspect further discussion
> should
> occur on dev@ and not users@ )
>
> -tim
>
>
>
>
> On Wed, Jul 6, 2016 at 6:05 AM, Jainesh Patel 
> wrote:
>
> > Hello,
> >
> > We are a group of students that are currently pursuing our undergraduate
> > degree in Computer Science from Pune Insititute of Computer
> > Technology(PICT), Maharashtra, India. We will be graduating in June 2017
> > and are currently in our final year. For our B.E project, we have
> selected
> > the domain as Cloud Computing and would be very interesting in working
> with
> > open source cloud computing software, which is where we stumbled upon
> > Apache CloudStack.
> >
> > It will be a great learning opportunity for us to work with Apache
> > CloudStack and in turn work with you. We would appreciate if you could
> > steer us towards the direction of choosing the right topic and working
> > towards culminating a project in the same, which would be helpful for the
> > community.
> >
> > Following are the few details which include information about us, which
> > would help you in making an informed decision:
> >
> > 1) Group Name- TheAtom
> >
> > 2) Group Members:
> > Shubham Mulay ( shubhammu...@gmail.com )
> > Faizaan Shaikh ( faizaanshai...@gmail.com )
> > Jainesh Patel ( jainesh...@gmail.com )
> >
> > 3) We have two mentors working with us, who will be guiding throughout
> the
> > process,
> > Dhruvesh Rathore ( dhruves...@hotmail.com )
> > Prerit Auti ( prerita...@gmail.com )
> >
> > 4) Development time : 6 to 7 months from Aug '16 to Feb '17.
> >
> > We would love to hear from you about any ideas that you see fit for us to
> > pursue and which are feasible in the specified time frame. Hoping to hear
> > from you soon, and thanking you in anticipation.
> >
> > Regards,
> > TheAtom
> >
>

[GitHub] cloudstack issue #1605: CLOUDSTACK-9428: Fix for CLOUDSTACK-9211 - Improve p...

[sateesh-chodapuneedi]

Github user sateesh-chodapuneedi commented on the issue:

https://github.com/apache/cloudstack/pull/1605
  
@nvazquez Thanks.
I will try this in my setup and share the results.


---
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 #1608: Cleanup RBD contexts after exceptions to prevent pot...

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1608
  
Thank you! Good catch :)

Could you look into the logging, since it would show the user more which is 
happening.


---
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 #1608: Cleanup RBD contexts after exceptions to prev...

[wido]

Github user wido commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1608#discussion_r70217007
  
--- Diff: 
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/LibvirtStorageAdaptor.java
 ---
@@ -863,26 +864,30 @@ public boolean deletePhysicalDisk(String uuid, 
KVMStoragePool pool, Storage.Imag
 RbdImage image = rbd.open(uuid);
 s_logger.debug("Fetching list of snapshots of RBD image " 
+ pool.getSourceDir() + "/" + uuid);
 List snaps = image.snapList();
-for (RbdSnapInfo snap : snaps) {
-if (image.snapIsProtected(snap.name)) {
-s_logger.debug("Unprotecting snapshot " + 
pool.getSourceDir() + "/" + uuid + "@" + snap.name);
-image.snapUnprotect(snap.name);
-} else {
-s_logger.debug("Snapshot " + pool.getSourceDir() + 
"/" + uuid + "@" + snap.name + " is not protected.");
+try {
+for (RbdSnapInfo snap : snaps) {
+if (image.snapIsProtected(snap.name)) {
+s_logger.debug("Unprotecting snapshot " + 
pool.getSourceDir() + "/" + uuid + "@" + snap.name);
+image.snapUnprotect(snap.name);
+} else {
+s_logger.debug("Snapshot " + 
pool.getSourceDir() + "/" + uuid + "@" + snap.name + " is not protected.");
+}
+s_logger.debug("Removing snapshot " + 
pool.getSourceDir() + "/" + uuid + "@" + snap.name);
+image.snapRemove(snap.name);
 }
-s_logger.debug("Removing snapshot " + 
pool.getSourceDir() + "/" + uuid + "@" + snap.name);
-image.snapRemove(snap.name);
+s_logger.info("Succesfully unprotected and removed any 
remaining snapshots (" + snaps.size() + ") of "
++ pool.getSourceDir() + "/" + uuid + " Continuing 
to remove the RBD image");
+} catch (RbdException e) {
+throw new CloudRuntimeException(e.toString() + " - " + 
ErrorCode.getErrorMessage(e.getReturnValue()));
+} finally {
+s_logger.debug("Closing image and destroying context");
+rbd.close(image);
+r.ioCtxDestroy(io);
--- End diff --

Good catch with the finally!


---
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 #1608: Cleanup RBD contexts after exceptions to prev...

[wido]

Github user wido commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1608#discussion_r70216966
  
--- Diff: 
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java
 ---
@@ -1325,6 +1328,8 @@ public Answer deleteSnapshot(final DeleteCommand cmd) 
{
 image.snapRemove(snapshotName);
 s_logger.info("Snapshot " + snap_full_name + " 
successfully removed from " +
 primaryPool.getType().toString() + "  pool.");
+} catch (RbdException e) {
+s_logger.error(e.toString() + " - " + 
ErrorCode.getErrorMessage(e.getReturnValue()));
--- End diff --

Should we maybe include a bit more? Like:

Failed to remove snapshot X, due to error: Y

Now we just dump a Exception into the logs which might not always tell a 
user where it came from.


---
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 #1607: SSVM downloader now handles redirects properly.

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1607
  
changes looks good. It would be great if a test case can be added. 


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