Re: [ANNOUNCE] New PMC Member: Ian Duffy

[Sebastien Goasguen]

gratz..

On Oct 1, 2014, at 2:17 AM, Gaurav Aradhye  wrote:

> Congratulations Ian!
> 
> Regards,
> Gaurav
> 
> On Wed, Oct 1, 2014 at 11:36 AM, Abhinandan Prateek 
> wrote:
> 
>> Congrats Ian !
>> 
>> -abhi
>> 
>> 
>> On 30-Sep-2014, at 7:20 pm, Chip Childers  wrote:
>> 
>>> The Project Management Committee (PMC) for Apache CloudStack has asked
>>> Ian Duffy to join the PMC and we are pleased to announce that he has
>>> accepted.
>>> 
>>> Join me in congratulating Ian!
>>> 
>>> -chip
>>> On behalf of the Apache CloudStack PMC
>> 
>> 

Re: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

[Sebastien Goasguen]

felicitations !

On Oct 1, 2014, at 2:14 AM, Punith S  wrote:

> Congrats Pierre!
> 
> On Wed, Oct 1, 2014 at 11:13 AM, Prasanna Santhanam  wrote:
> 
>> Congratulations Pierre-Luc!
>> 
>> On Tue, Sep 30, 2014 at 7:20 PM, Chip Childers 
>> wrote:
>>> The Project Management Committee (PMC) for Apache CloudStack has asked
>>> Pierre-Luc Dion to join the PMC and we are pleased to announce that he
>>> has accepted.
>>> 
>>> Join me in congratulating Pierre-Luc!
>>> 
>>> -chip
>>> On behalf of the Apache CloudStack PMC
>> 
> 
> 
> 
> -- 
> regards,
> 
> punith s
> cloudbyte.com

Re: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

[Hugo Trippaers]

Congratulations :-)

Sent from my iPhone

> On 1 okt. 2014, at 09:06, Sebastien Goasguen  wrote:
> 
> felicitations !
> 
>> On Oct 1, 2014, at 2:14 AM, Punith S  wrote:
>> 
>> Congrats Pierre!
>> 
>>> On Wed, Oct 1, 2014 at 11:13 AM, Prasanna Santhanam  wrote:
>>> 
>>> Congratulations Pierre-Luc!
>>> 
>>> On Tue, Sep 30, 2014 at 7:20 PM, Chip Childers 
>>> wrote:
 The Project Management Committee (PMC) for Apache CloudStack has asked
 Pierre-Luc Dion to join the PMC and we are pleased to announce that he
 has accepted.
 
 Join me in congratulating Pierre-Luc!
 
 -chip
 On behalf of the Apache CloudStack PMC
>> 
>> 
>> 
>> -- 
>> regards,
>> 
>> punith s
>> cloudbyte.com
> 

Re: [ANNOUNCE] New PMC Member: Ian Duffy

[Hugo Trippaers]

Congrats Ian :-)

Sent from my iPhone

> On 1 okt. 2014, at 09:05, Sebastien Goasguen  wrote:
> 
> gratz..
> 
>> On Oct 1, 2014, at 2:17 AM, Gaurav Aradhye  
>> wrote:
>> 
>> Congratulations Ian!
>> 
>> Regards,
>> Gaurav
>> 
>> On Wed, Oct 1, 2014 at 11:36 AM, Abhinandan Prateek 
>> wrote:
>> 
>>> Congrats Ian !
>>> 
>>> -abhi
>>> 
>>> 
 On 30-Sep-2014, at 7:20 pm, Chip Childers  wrote:
 
 The Project Management Committee (PMC) for Apache CloudStack has asked
 Ian Duffy to join the PMC and we are pleased to announce that he has
 accepted.
 
 Join me in congratulating Ian!
 
 -chip
 On behalf of the Apache CloudStack PMC
> 

Re: Review Request 26008: CLOUDSTACK-7627: Automated Remote Access VPN on VPC Test Cases

[SrikanteswaraRao Talluri]

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


Please fix pep8 errors. Otherwise, scripts looks good.

- SrikanteswaraRao Talluri


On Sept. 29, 2014, 11:16 p.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26008/
> ---
> 
> (Updated Sept. 29, 2014, 11:16 p.m.)
> 
> 
> Review request for cloudstack, sangeetha hariharan, sanjeev n, Santhosh 
> Edukulla, and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7627
> https://issues.apache.org/jira/browse/CLOUDSTACK-7627
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Test Suite for Testing Remote Access VPN on VPC. 
> 
> I successfully automated the following components:
> 
> 1.VPN Client Installation on Linux
> 2.Component that efficiently verifies Remote VPN Access between client and 
> the Server.
> 3.Developed a component that automates VPN Client Configuration and services.
> 4.Test Cases of the Feature
> 5.Tested the Code multiple times on XenServer.
> 6.Tested the Code multiple times on VMWare (To test Skipping of Test Cases)
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_remotevpn_vpc.py PRE-CREATION 
>   tools/marvin/marvin/config/test_data.py 00fa52c 
> 
> Diff: https://reviews.apache.org/r/26008/diff/
> 
> 
> Testing
> ---
> 
> Testing Done on Two Configurations: XenServer and VMWare
> 
> XenServer Test Results:
> 
> Test case 01 : Enable VPN for Public IP Address on the VPC ... === TestName: 
> test_01_RemoteAccessVPN_VPC_EnableVPNAndConnecttoVM | Status : SUCCESS ===
> ok
> Test case 02 : Remote a VPN User ... === TestName: test_02_VPC_RemoveVPNUser 
> | Status : SUCCESS ===
> ok
> Test case 03 : Add a Different VPN User and Test Access with already existing 
> VPN User ... === TestName: test_03_VPC_AddDifferentVPNUser | Status : SUCCESS 
> ===
> ok
> Test case 04 : Add a Previously Removed VPN User from the VPC and Test the 
> VPN Connectivity ... === TestName: 
> test_04_VPC_AddPreviouslyRemovedVPNUserTestConnectivity | Status : SUCCESS ===
> ok
> Test case 05 : Disable the VPN Service on the VPC ... === TestName: 
> test_05_VPC_DisableVPNServiceOnVPC | Status : SUCCESS ===
> ok
> Test case 06 : Enabled Previously Dsiabled VPN Access to VPC. ... === 
> TestName: test_06_VPC_EnablePreviouslyDisabledVPNAccesstoVPC | Status : 
> SUCCESS ===
> ok
> Test case 07 : Create Nine VPN Users to test the remote.vpn.user.limit=8 
> Configuration parameter ... === TestName: 
> test_07_ConfigParam_TestRemoteVPNUserLimit | Status : SUCCESS ===
> ok
> 
> --
> Ran 7 tests in 851.687s
> 
> OK
> 
> 
> VMWare Test Results:
> 
> === TestName: None | Status : EXCEPTION ===
> SKIP: Only XenServer VPNClient Template is ready currently. KVM,VMWare or 
> Hyper-V VPN Client Templates are not ready. Skipping the test suite for those 
> configurations
>  >> begin captured stdout << -
> === TestName: None | Status : EXCEPTION ===
> 
> 
> - >> end captured stdout << --
>  >> begin captured logging << 
> CSLog: DEBUG: Obtain the Admin's API Client
> CSLog: DEBUG: Get the dictionary information that will be used during CCP 
> tests, from test_data.py present on the Client
> CSLog: DEBUG: Payload: {'apiKey': 
> u'fGs23pVVge8K-HxeQCo3WBCria7hJs5JZW_j7cKnX1mMpbBKH8JwNCxcWHxBgA-slwW0d1YJHJKbCX_Doc3-GQ',
>  'command': 'listDomains', 'signature': '5BHLOjDELImWRpvI/16LQ/TrLRM=', 
> 'response': 'json'}
> CSLog: DEBUG: Sending GET Cmd : listDomains===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
> (1): 10.220.135.90
> requests.packages.urllib3.connectionpool: DEBUG: "GET 
> /client/api?apiKey=fGs23pVVge8K-HxeQCo3WBCria7hJs5JZW_j7cKnX1mMpbBKH8JwNCxcWHxBgA-slwW0d1YJHJKbCX_Doc3-GQ&command=listDomains&response=json&signature=5BHLOjDELImWRpvI%2F16LQ%2FTrLRM%3D
>  HTTP/1.1" 200 159
> CSLog: DEBUG: Response : [{path : u'ROOT', haschild : False, id : 
> u'42ebae70-4375-11e4-86a1-66733ba24ed8', name : u'ROOT', level : 0}]
> CSLog: DEBUG: Payload: {'apiKey': 
> u'fGs23pVVge8K-HxeQCo3WBCria7hJs5JZW_j7cKnX1mMpbBKH8JwNCxcWHxBgA-slwW0d1YJHJKbCX_Doc3-GQ',
>  'name': u'XenRT-Zone-0', 'command': 'listZones', 'signature': 
> 'MH3voxNCEMIMA3deggb/EVxAog8=', 'response': 'json'}
> CSLog: DEBUG: Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
> (1): 10.220.135.90
> requests.packages.urllib3.connectionpool: DEBUG: "GET 
> /client/api?response=json&apiKey=fGs23pVVge8K-HxeQCo3WBCria7hJs5JZW

Cloudstack operations and Ceph RBD in degraded state

[Indra Pramana]

Dear all,

Anyone using CloudStack with Ceph RBD as primary storage? I am using
CloudStack 4.2.0 with KVM hypervisors and Ceph latest stable version of
dumpling.

Based on what I see, when Ceph cluster is in degraded state (not
active+clean), for example due to one node is down and in recovering
process, it might affect CloudStack operations. For example:

- Stopped VM cannot be started, because it says cannot find suitable
storage pool.

- Disconnected host cannot be reconnected easily, even after restarting
agent and libvirt on agent side, and restarting management server on the
server side. Need to keep on trying and suddenly it will be connected/up by
itself.

Once Ceph has recovered and back to active+clean state, then CloudStack
operations will be back to normal. Host agents will be up, and VMs can be
started.

Anyone seeing similar behaviour?

Looking forward to your reply, thank you.

Cheers.

Doubt - Secondary IP

[Gaurav Aradhye]

Hi,

I want to confirm the secondary IP behavior. Secondary IP is configured
manually on  VM. When Vm is destroyed and recovered immediately, the
information about secondary IP is lost and only primary IP is retained.

Is this behavior correct?

Regards,
Gaurav

Review Request 26220: CLOUDSTACK-7645: [UI] Fixing incorrect labels, including instances of "???label.*???"

[Mihaela Stoica]

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

Review request for cloudstack, Brian Federle and Jessica Wang.


Bugs: CLOUDSTACK-7596, CLOUDSTACK-7597, CLOUDSTACK-7606, CLOUDSTACK-7607, 
CLOUDSTACK-7608, and CLOUDSTACK-7645
https://issues.apache.org/jira/browse/CLOUDSTACK-7596
https://issues.apache.org/jira/browse/CLOUDSTACK-7597
https://issues.apache.org/jira/browse/CLOUDSTACK-7606
https://issues.apache.org/jira/browse/CLOUDSTACK-7607
https://issues.apache.org/jira/browse/CLOUDSTACK-7608
https://issues.apache.org/jira/browse/CLOUDSTACK-7645


Repository: cloudstack-git


Description
---

- removed duplicate entries in dictionary
- added dictionary entries that have been missed during the dictionary split
- added missing entries in messages.properties
- fixed other localization issues


Diffs
-

  client/WEB-INF/classes/resources/messages.properties c9eb7ae 
  ui/dictionary.jsp c03ad67 
  ui/dictionary2.jsp 39299b3 
  ui/scripts/configuration.js b6c94f8 
  ui/scripts/storage.js 783633c 
  ui/scripts/templates.js 9665ffd 
  ui/scripts/ui-custom/physicalResources.js 7dd5380 

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


Testing
---

I've checked all the issues that have been reported, and they are all fixed.


Thanks,

Mihaela Stoica

RE: [ANNOUNCE] New PMC Member: Ian Duffy

[Paul Angus]

Congrats Ian!

Regards,

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: 30 September 2014 17:16
To: dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] New PMC Member: Ian Duffy

Congratulations, Ian!

On Tue, Sep 30, 2014 at 7:50 AM, Chip Childers 
wrote:

> The Project Management Committee (PMC) for Apache CloudStack has asked
> Ian Duffy to join the PMC and we are pleased to announce that he has
> accepted.
>
> Join me in congratulating Ian!
>
> -chip
> On behalf of the Apache CloudStack PMC
>



--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

RE: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

[Paul Angus]

Congrats Pierre-Luc. :)


Regards,

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
Sent: 30 September 2014 18:19
To: dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

haha, I guest now it's a +1 (binding)



On Tue, Sep 30, 2014 at 1:00 PM, Daan Hoogland 
wrote:

> fortune to you Pierre-Luc (and do you as PMC member still believe the
> 4.4.1 RC is ok for release?)
>
> On Tue, Sep 30, 2014 at 6:16 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > Congratulations, Pierre-Luc!
> >
> > On Tue, Sep 30, 2014 at 7:50 AM, Chip Childers
> > 
> > wrote:
> >
> > > The Project Management Committee (PMC) for Apache CloudStack has
> > > asked Pierre-Luc Dion to join the PMC and we are pleased to
> > > announce that he has accepted.
> > >
> > > Join me in congratulating Pierre-Luc!
> > >
> > > -chip
> > > On behalf of the Apache CloudStack PMC
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
> >
>
>
>
> --
> Daan
>
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Cloudstack operations and Ceph RBD in degraded state

[Wido den Hollander]

On 10/01/2014 09:21 AM, Indra Pramana wrote:
> Dear all,
> 
> Anyone using CloudStack with Ceph RBD as primary storage? I am using
> CloudStack 4.2.0 with KVM hypervisors and Ceph latest stable version of
> dumpling.
> 

I am :)

> Based on what I see, when Ceph cluster is in degraded state (not
> active+clean), for example due to one node is down and in recovering
> process, it might affect CloudStack operations. For example:
> 
> - Stopped VM cannot be started, because it says cannot find suitable
> storage pool.
> 
> - Disconnected host cannot be reconnected easily, even after restarting
> agent and libvirt on agent side, and restarting management server on the
> server side. Need to keep on trying and suddenly it will be connected/up by
> itself.
> 

It really depends on the size of the cluster. It could be that the Ceph
is cluster is so busy with recovery that it can't process the I/O coming
from CloudStack and thus stalls.

This is not a Ceph or CloudStack problem, but probably the size of your
cluster.

Wido

> Once Ceph has recovered and back to active+clean state, then CloudStack
> operations will be back to normal. Host agents will be up, and VMs can be
> started.
> 
> Anyone seeing similar behaviour?
> 
> Looking forward to your reply, thank you.
> 
> Cheers.
> 

Review Request 26221: CLOUDSTACK-6282 - Added hyper-v hypervisor check for tests which are not applicable for hyper-v

[Vinay Varma]

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

Review request for cloudstack, Alex Brett and Santhosh Edukulla.


Bugs: cloudstack-6282
https://issues.apache.org/jira/browse/cloudstack-6282


Repository: cloudstack-git


Description
---

CLOUDSTACK-6282 - Added hyper-v hypervisor check for tests which are not 
applicable for hyper-v


Diffs
-

  test/integration/component/test_escalations_instances.py 73ebf13 
  test/integration/component/test_escalations_ipaddresses.py b29cd1d 
  test/integration/component/test_escalations_isos.py 925c2fb 
  test/integration/component/test_escalations_networks.py c0ab709 
  test/integration/component/test_escalations_snapshots.py 8d289e1 
  test/integration/component/test_escalations_templates.py c497e71 
  test/integration/component/test_escalations_volumes.py 8d6ba99 

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


Testing
---

Executed all the modified tests and attached are the log files


File Attachments


IPAddressesResults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/01/5561459d-faf8-48e5-8b53-9d1738bec7be__IPAddressesResults.txt
ISOResults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/01/d4fde9a5-b4b8-47c9-958f-0061c4783c7a__ISOResults.txt
NetworksResults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/01/a072ad53-7832-408d-ad13-31dac3a71d2c__NetworksResults.txt
SnapshotsResults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/01/76f3ba65-36b7-447e-bbc6-81569ba1f0ec__SnapshotsResults.txt
TemplatesResults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/01/137febdb-6f2a-4817-96aa-090be2f82ee7__TemplatesResults.txt


Thanks,

Vinay Varma

Re: Review Request 26221: CLOUDSTACK-6282 - Added hyper-v hypervisor check for tests which are not applicable for hyper-v

[Alex Brett]

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

Ship it!


Ship It!

- Alex Brett


On Oct. 1, 2014, 8:31 a.m., Vinay Varma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26221/
> ---
> 
> (Updated Oct. 1, 2014, 8:31 a.m.)
> 
> 
> Review request for cloudstack, Alex Brett and Santhosh Edukulla.
> 
> 
> Bugs: cloudstack-6282
> https://issues.apache.org/jira/browse/cloudstack-6282
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-6282 - Added hyper-v hypervisor check for tests which are not 
> applicable for hyper-v
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_escalations_instances.py 73ebf13 
>   test/integration/component/test_escalations_ipaddresses.py b29cd1d 
>   test/integration/component/test_escalations_isos.py 925c2fb 
>   test/integration/component/test_escalations_networks.py c0ab709 
>   test/integration/component/test_escalations_snapshots.py 8d289e1 
>   test/integration/component/test_escalations_templates.py c497e71 
>   test/integration/component/test_escalations_volumes.py 8d6ba99 
> 
> Diff: https://reviews.apache.org/r/26221/diff/
> 
> 
> Testing
> ---
> 
> Executed all the modified tests and attached are the log files
> 
> 
> File Attachments
> 
> 
> IPAddressesResults.txt
>   
> https://reviews.apache.org/media/uploaded/files/2014/10/01/5561459d-faf8-48e5-8b53-9d1738bec7be__IPAddressesResults.txt
> ISOResults.txt
>   
> https://reviews.apache.org/media/uploaded/files/2014/10/01/d4fde9a5-b4b8-47c9-958f-0061c4783c7a__ISOResults.txt
> NetworksResults.txt
>   
> https://reviews.apache.org/media/uploaded/files/2014/10/01/a072ad53-7832-408d-ad13-31dac3a71d2c__NetworksResults.txt
> SnapshotsResults.txt
>   
> https://reviews.apache.org/media/uploaded/files/2014/10/01/76f3ba65-36b7-447e-bbc6-81569ba1f0ec__SnapshotsResults.txt
> TemplatesResults.txt
>   
> https://reviews.apache.org/media/uploaded/files/2014/10/01/137febdb-6f2a-4817-96aa-090be2f82ee7__TemplatesResults.txt
> 
> 
> Thanks,
> 
> Vinay Varma
> 
>

Re: Review Request 25885: CLOUDSTACK-7594: Adding automation test cases for Stopped VM test path

[Ashutosh Kelkar]

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

(Updated Oct. 1, 2014, 9:18 a.m.)


Review request for cloudstack, suresh sadhu and SrikanteswaraRao Talluri.


Bugs: CLOUDSTACK-7594
https://issues.apache.org/jira/browse/CLOUDSTACK-7594


Repository: cloudstack-git


Description
---

Automation test cases for Stopped VM test path.


Diffs (updated)
-

  test/integration/testpaths/testpath_stopped_vm.py PRE-CREATION 
  tools/marvin/marvin/lib/base.py d623386 

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


Testing (updated)
---

Yes.

Advanced zone:
Positive test for stopped VM test path - T1 ... === TestName: 
test_01_pt_deploy_vm_without_startvm | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T1 variant ... === TestName: 
test_02_pt_deploy_vm_with_startvm_true | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T2 ... === TestName: 
test_03_pt_deploy_vm_with_startvm_false | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T3 and variant, T9 ... === TestName: 
test_04_pt_startvm_false_attach_disk | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T4 ... === TestName: 
test_05_pt_startvm_false_attach_disk_change_SO | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T5 ... === TestName: 
test_06_pt_startvm_false_attach_iso | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T5 variant ... === TestName: 
test_07_pt_startvm_false_attach_iso_running_vm | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T10 ... === TestName: 
test_08_pt_startvm_false_password_enabled_template | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T11 ... === TestName: 
test_09_pt_destroy_stopped_vm | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T12 ... === TestName: 
test_10_max_account_limit | Status : SUCCESS ===
ok


Basic zone:

Positive test for stopped VM test path - T1 ... === TestName: 
test_01_pt_deploy_vm_without_startvm | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T1 variant ... === TestName: 
test_02_pt_deploy_vm_with_startvm_true | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T2 ... === TestName: 
test_03_pt_deploy_vm_with_startvm_false | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T3 and variant, T9 ... === TestName: 
test_04_pt_startvm_false_attach_disk | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T4 ... === TestName: 
test_05_pt_startvm_false_attach_disk_change_SO | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T5 ... === TestName: 
test_06_pt_startvm_false_attach_iso | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T5 variant ... === TestName: 
test_07_pt_startvm_false_attach_iso_running_vm | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T10 ... === TestName: 
test_08_pt_startvm_false_password_enabled_template | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T11 ... === TestName: 
test_09_pt_destroy_stopped_vm | Status : SUCCESS ===
ok
Positive test for stopped VM test path - T12 ... === TestName: 
test_10_max_account_limit | Status : SUCCESS ===
ok

--
Ran 10 tests in 2792.968s

OK


Thanks,

Ashutosh Kelkar

Re: CloudStack - cache disk policy

[Wido den Hollander]

On 09/27/2014 05:51 PM, Wido den Hollander wrote:
> 
> 
> On 27-09-14 11:00, Thierry Bernard wrote:
>> Dear CloudStack team,
>>
>> First let me introduce myself I am working for EasyVirt company around
>> the cloud and virtualization technologies.
>> Also in order to integrate CloudStack in one of our projects we need to
>> use the write-back cache disk feature.
>>
>> From this link it seems that this feature will be embedded in the next
>> release of CloudStack (4.5.0):
>> https://issues.apache.org/jira/browse/CLOUDSTACK-1302
>>
>> I tried from the master branch by creating a new disk offering and
>> setting the write cache type to write-back.
>> By generating a new instance with this new disk offerings the vm's xml
>> config file returns that the cache is "none".
>> Have you ever commits the code of this new feature?
>>
> 
> Well, it should work (Shouldn't all code?), but you might run into a bug.
> 
> If you set the loglevel to DEBUG of the KVM Agent you will see that the
> Management Server sends a StartCommand.
> 
> Do you see the cache policy in there? What is it set to?
> 

I tested this today with the 4.4.1 RC and it works for me with a RBD device:


  
  

  
  

  
  
  


Just be aware that your Compute Offering might be overriding the Disk
Offering. So you might want to check if the cache policy is writeback
there as well.

Wido

> Wido
> 
>> In advance thank you for your help and your feedback.
>> Best regards,
>> Thierry Bernard.
>>

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Wido den Hollander]

+1

I tested it on a KVM (Ubuntu) environment and tested mainly the RBD/Ceph
functionality:

- Instance deployment from template (QCOW2)
- Cache mode setting of disk to WriteBack
- Creating snapshot of RBD volume
- Create a new volume of RBD snapshot
- Adding new volume to Instance
- Removing volume from Instance
- Live Migrate Instance from host to host

All this functionality worked for me and the Ubuntu packages also build
fine.

So that is my +1 for the 4.4.1 release.

Wido

On 09/29/2014 12:01 AM, Daan Hoogland wrote:
> Hi All,
> 
> I've created a 4.4.1 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.4-RC20140924T2100
> Commit: 620ad650bdda23cabdf4c9dc480072c02c59a2d1
> 
> List of changes:
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.4.1/
> 
> PGP release keys (signed using 4096R/AA4736F3):
> 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)
> 

Re: Cloudstack operations and Ceph RBD in degraded state

[Indra Pramana]

Hi Wido,

Can you elaborate more on what do you mean by the size of our cluster? Is
it because the cluster size is too big, or too small?

Thank you.

On Wed, Oct 1, 2014 at 4:28 PM, Wido den Hollander  wrote:

>
>
> On 10/01/2014 09:21 AM, Indra Pramana wrote:
> > Dear all,
> >
> > Anyone using CloudStack with Ceph RBD as primary storage? I am using
> > CloudStack 4.2.0 with KVM hypervisors and Ceph latest stable version of
> > dumpling.
> >
>
> I am :)
>
> > Based on what I see, when Ceph cluster is in degraded state (not
> > active+clean), for example due to one node is down and in recovering
> > process, it might affect CloudStack operations. For example:
> >
> > - Stopped VM cannot be started, because it says cannot find suitable
> > storage pool.
> >
> > - Disconnected host cannot be reconnected easily, even after restarting
> > agent and libvirt on agent side, and restarting management server on the
> > server side. Need to keep on trying and suddenly it will be connected/up
> by
> > itself.
> >
>
> It really depends on the size of the cluster. It could be that the Ceph
> is cluster is so busy with recovery that it can't process the I/O coming
> from CloudStack and thus stalls.
>
> This is not a Ceph or CloudStack problem, but probably the size of your
> cluster.
>
> Wido
>
> > Once Ceph has recovered and back to active+clean state, then CloudStack
> > operations will be back to normal. Host agents will be up, and VMs can be
> > started.
> >
> > Anyone seeing similar behaviour?
> >
> > Looking forward to your reply, thank you.
> >
> > Cheers.
> >
>

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Daan Hoogland]

thanks Wido,

for anyone that is not taking today to test master in order to get out 4.5
ASAP, I have enough votes to release but saw a couple of remarks passing by
on systemvm ugrade and saw no reports on the systemvm shellshock for better
or worse. so if any of you has priority on 4.4 today please feel free to
focus on those areas.

thanks,
Daan

On Wed, Oct 1, 2014 at 1:31 PM, Wido den Hollander  wrote:

> +1
>
> I tested it on a KVM (Ubuntu) environment and tested mainly the RBD/Ceph
> functionality:
>
> - Instance deployment from template (QCOW2)
> - Cache mode setting of disk to WriteBack
> - Creating snapshot of RBD volume
> - Create a new volume of RBD snapshot
> - Adding new volume to Instance
> - Removing volume from Instance
> - Live Migrate Instance from host to host
>
> All this functionality worked for me and the Ubuntu packages also build
> fine.
>
> So that is my +1 for the 4.4.1 release.
>
> Wido
>
> On 09/29/2014 12:01 AM, Daan Hoogland wrote:
> > Hi All,
> >
> > I've created a 4.4.1 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.4-RC20140924T2100
> > Commit: 620ad650bdda23cabdf4c9dc480072c02c59a2d1
> >
> > List of changes:
> >
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.1/
> >
> > PGP release keys (signed using 4096R/AA4736F3):
> > 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)
> >
>



-- 
Daan

Re: [ANNOUNCE] New PMC Member: Ian Duffy

[Ian Duffy]

Thanks Guys! :)

On 1 October 2014 09:26, Paul Angus  wrote:

> Congrats Ian!
>
> Regards,
>
> Paul Angus
> Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus
> paul.an...@shapeblue.com
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: 30 September 2014 17:16
> To: dev@cloudstack.apache.org
> Subject: Re: [ANNOUNCE] New PMC Member: Ian Duffy
>
> Congratulations, Ian!
>
> On Tue, Sep 30, 2014 at 7:50 AM, Chip Childers 
> wrote:
>
> > The Project Management Committee (PMC) for Apache CloudStack has asked
> > Ian Duffy to join the PMC and we are pleased to announce that he has
> > accepted.
> >
> > Join me in congratulating Ian!
> >
> > -chip
> > On behalf of the Apache CloudStack PMC
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

Re: Cloudstack operations and Ceph RBD in degraded state

[Wido den Hollander]

On 10/01/2014 01:43 PM, Indra Pramana wrote:
> Hi Wido,
> 
> Can you elaborate more on what do you mean by the size of our cluster? Is
> it because the cluster size is too big, or too small?
> 

I think it's probably because the Ceph cluster is to small. That causes
to much stress on the other nodes during recovery.

That again leads to libvirt and Qemu not being able to talk to Ceph
which leads to slow I/O.

I've seen multiple occasions where Ceph clusters are recovering but
CloudStack is still working just fine.

Wido

> Thank you.
> 
> On Wed, Oct 1, 2014 at 4:28 PM, Wido den Hollander  wrote:
> 
>>
>>
>> On 10/01/2014 09:21 AM, Indra Pramana wrote:
>>> Dear all,
>>>
>>> Anyone using CloudStack with Ceph RBD as primary storage? I am using
>>> CloudStack 4.2.0 with KVM hypervisors and Ceph latest stable version of
>>> dumpling.
>>>
>>
>> I am :)
>>
>>> Based on what I see, when Ceph cluster is in degraded state (not
>>> active+clean), for example due to one node is down and in recovering
>>> process, it might affect CloudStack operations. For example:
>>>
>>> - Stopped VM cannot be started, because it says cannot find suitable
>>> storage pool.
>>>
>>> - Disconnected host cannot be reconnected easily, even after restarting
>>> agent and libvirt on agent side, and restarting management server on the
>>> server side. Need to keep on trying and suddenly it will be connected/up
>> by
>>> itself.
>>>
>>
>> It really depends on the size of the cluster. It could be that the Ceph
>> is cluster is so busy with recovery that it can't process the I/O coming
>> from CloudStack and thus stalls.
>>
>> This is not a Ceph or CloudStack problem, but probably the size of your
>> cluster.
>>
>> Wido
>>
>>> Once Ceph has recovered and back to active+clean state, then CloudStack
>>> operations will be back to normal. Host agents will be up, and VMs can be
>>> started.
>>>
>>> Anyone seeing similar behaviour?
>>>
>>> Looking forward to your reply, thank you.
>>>
>>> Cheers.
>>>
>>
> 

Build failed in Jenkins: build-master #1738

[jenkins]

See 

Changes:

[sanjay.tripathi] CLOUDSTACK-6650: Reorder Cluster list in deployment planner 
to protect

--
[...truncated 1821 lines...]

---
 T E S T S
---
Running com.cloud.event.EventControlsUnitTest
log4j:WARN No appenders could be found for logger 
(com.cloud.event.EventControlsUnitTest).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.637 sec
Running com.cloud.keystore.KeystoreTest
org.apache.cloudstack.api.response.UserVmResponse/null/{"id":"3","securitygroup":[],"nic":[],"tags":[],"affinitygroup":[]}
org.apache.cloudstack.api.response.AlertResponse/null/{"id":"100","description":"Hello"}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.137 sec
Running com.cloud.alert.AlertControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec
Running com.cloud.capacity.CapacityManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.154 sec
Running com.cloud.servlet.StaticResourceServletTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.155 sec
Running com.cloud.servlet.ConsoleProxyServletTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running com.cloud.resourcelimit.ResourceLimitManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running com.cloud.network.firewall.FirewallManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.001 sec
Running com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.603 sec
Running com.cloud.network.element.VirtualRouterElementTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.478 sec
Running com.cloud.network.UpdatePhysicalNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.127 sec
Running com.cloud.network.CreatePrivateNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec
Running com.cloud.network.NetworkModelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec
Running com.cloud.network.router.VirtualNetworkApplianceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec
Running com.cloud.network.security.SecurityGroupManagerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.169 sec
Running com.cloud.network.security.SecurityGroupQueueTest
Total jobs dequeued = 10, num queued=1001 queue current size=991
Num Vms= 50 Queue size = 50
Num Vms= 2 Queue size = 2 time=962 ms
Num Vms= 5000 Queue size = 5000 time=1613 ms
Num Vms= 1 Queue size = 1 time=1 ms
Num Vms= 100 Queue size = 100 time=236 ms
Total jobs dequeued = 10, num queued=1009 queue current size=1000
Tests run: 4, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 3.265 sec <<< 
FAILURE!
Running com.cloud.network.vpc.VpcManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec
Running com.cloud.network.DedicateGuestVlanRangesTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec
Running com.cloud.network.lb.AssignLoadBalancerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 sec
Running com.cloud.network.dao.NetworkDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Running com.cloud.vm.FirstFitPlannerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.652 sec
Running com.cloud.vm.DeploymentPlanningManagerImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.505 sec
Running com.cloud.vm.snapshot.VMSnapshotManagerTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.177 sec
Running com.cloud.vm.UserVmManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.181 sec
Running com.cloud.configuration.ValidateIpRangeTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running com.cloud.configuration.ConfigurationManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec
Running com.cloud.server.ConfigurationServerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running com.cloud.template.TemplateManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running com.cloud.vpc.Site2SiteVpnTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.781 sec
Running com.cloud.vpc.NetworkACLServiceTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.168 sec
Running com.cloud.vpc.NetworkACLManagerTest
Tests run: 6, Failures: 0, 

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Pierre-Luc Dion]

Erik,

I've tests upgrade from 4.3 and 4.2.1 using  system vm from jenkins. Some
copy them on apt-get.eu and  Upgrade instructions point to them , refer to:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/upgrade/upgrade-4.3.html


*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

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


On Tue, Sep 30, 2014 at 3:33 PM, Erik Weber  wrote:

> Which systemvm did you use for the 4.3 install, and did it successfully
> upgrade it?
>
> Haven't had the time to test it yet, so just wanted to make sure that the
> systemvm issues with 4.3 templates running on 4.4 is fixed.
>
> --
> Erik
>
> On Mon, Sep 29, 2014 at 2:45 PM, Wei ZHOU  wrote:
>
> > +1
> >
> > KVM  + Advanzed zone
> > Upgrade from 4.3.0 to 4.4.1-RC
> > Everything looks fine.
> >
> > -Wei
> >
> > 2014-09-29 12:57 GMT+02:00 Rohit Yadav :
> >
> > > +1
> > >
> > > Testing using KVM on Ubuntu, was able to successfully deploy a basic
> > zone,
> > > launch VMs.
> > >
> > > On 29-Sep-2014, at 12:01 am, Daan Hoogland 
> > > wrote:
> > > > Hi All,
> > > >
> > > > I've created a 4.4.1 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.4-RC20140924T2100
> > > > Commit: 620ad650bdda23cabdf4c9dc480072c02c59a2d1
> > > >
> > > > List of changes:
> > > >
> > >
> >
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/
> > > >
> > > > Source release (checksums and signatures are available at the same
> > > > location):
> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.1/
> > > >
> > > > PGP release keys (signed using 4096R/AA4736F3):
> > > > 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)
> > > >
> > > > --
> > > > Daan
> > >
> > > Regards,
> > > Rohit Yadav
> > > Software Architect, ShapeBlue
> > > M. +41 779015219 | rohit.ya...@shapeblue.com
> > > Blog: bhaisaab.org | Twitter: @_bhaisaab
> > >
> > >
> > >
> > > Find out more about ShapeBlue and our range of CloudStack related
> > services
> > >
> > > IaaS Cloud Design & Build<
> > > http://shapeblue.com/iaas-cloud-design-and-build//>
> > > CSForge – rapid IaaS deployment framework<
> http://shapeblue.com/csforge/>
> > > CloudStack Consulting
> > > CloudStack Infrastructure Support<
> > > http://shapeblue.com/cloudstack-infrastructure-support/>
> > > CloudStack Bootcamp Training Courses<
> > > http://shapeblue.com/cloudstack-training/>
> > >
> > > This email and any attachments to it may be confidential and are
> intended
> > > solely for the use of the individual to whom it is addressed. Any views
> > or
> > > opinions expressed are solely those of the author and do not
> necessarily
> > > represent those of Shape Blue Ltd or related companies. If you are not
> > the
> > > intended recipient of this email, you must neither take any action
> based
> > > upon its contents, nor copy or show it to anyone. Please contact the
> > sender
> > > if you believe you have received this email in error. Shape Blue Ltd
> is a
> > > company incorporated in England & Wales. ShapeBlue Services India LLP
> is
> > a
> > > company incorporated in India and is operated under license from Shape
> > Blue
> > > Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> > Brasil
> > > and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
> > is
> > > a company registered by The Republic of South Africa and is traded
> under
> > > license from Shape Blue Ltd. ShapeBlue is a registered trademark.
> > >
> >
>

Re: [ANNOUNCE] New PMC Member: Ian Duffy

[Noel King]

Well done Ian

On 30 September 2014 14:50, Chip Childers  wrote:

> The Project Management Committee (PMC) for Apache CloudStack has asked
> Ian Duffy to join the PMC and we are pleased to announce that he has
> accepted.
>
> Join me in congratulating Ian!
>
> -chip
> On behalf of the Apache CloudStack PMC
>

Build failed in Jenkins: simulator-singlerun #484

[jenkins]

See 

Changes:

[sanjay.tripathi] CLOUDSTACK-6650: Reorder Cluster list in deployment planner 
to protect

--
[...truncated 8934 lines...]
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2:07.270s
[INFO] Finished at: Wed Oct 01 08:22:17 EDT 2014
[INFO] Final Memory: 42M/177M
[INFO] 
[WARNING] The requested profile "simulator" could not be activated because it 
does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer ---
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
> WARNING: Provided file does not exist: 

> Initializing database=simulator with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `simulator`
> Running query: create database `simulator`
> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified 
by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 21.322s
[INFO] Finished at: Wed Oct 01 08:22:42 EDT 2014
[INFO] Final Memory: 42M/192M
[INFO] 
[simulator-singlerun] $ /bin/bash -x /tmp/hudson8689880627783724933.sh
+ grep -q Launcher
+ jps -l
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=24659
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 

Review Request 26225: CLOUDSTACK-7664: [UI] Handle change in API response for listloadbalancer

[Mihaela Stoica]

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

Review request for cloudstack.


Bugs: CLOUDSTACK-7664
https://issues.apache.org/jira/browse/CLOUDSTACK-7664


Repository: cloudstack-git


Description
---

- replaced all occurrences of "listloadbalancerssresponse" with 
"listloadbalancersresponse" in ui\scripts\vpc.js, following the change in the 
listLoadBalancers API response string.


Diffs
-

  ui/scripts/vpc.js 3e57631 

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


Testing
---


Thanks,

Mihaela Stoica

Re: test day reminder

[Wido den Hollander]

On 09/30/2014 09:26 AM, Daan Hoogland wrote:
> H all,
> 
> As you might remember, we agreed on a test day for the master branch on
> Wednesday the 1st October, during our last meeting in Schihol-Rijk with
> some folks. Please feel invited to test master so that we can report to our
> RM for 4.5 for the current state and he can have a short and quick journey
> to releasing.
> 

I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and
that worked, but my KVM agent couldn't connect anymore afterwards:

2014-10-01 14:59:08,789 INFO  [utils.nio.NioClient]
(Agent-Selector:null) Connecting to cloudstack.:8250
2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection]
(Agent-Selector:null) Unable to initialize the threads.
java.io.IOException: Connection closed with -1 on reading size.
at com.cloud.utils.nio.Link.doHandshake(Link.java:509)
at com.cloud.utils.nio.NioClient.init(NioClient.java:78)
at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
at java.lang.Thread.run(Thread.java:744)

Any ideas? When I try to telnet to 8250 the connection is closed
immediately by the mgmt server. Nothing in the logs.

So this is currently preventing me from testing the KVM agents.

Wido


> ​optimistically yours,​
> 

RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Geoff Higginbottom]

+0  only because of the issues in the release notes, a clean install and an 
upgrade from 4.3.1 went OK, but only because I know how to do it, it would not 
work if I followed the release notes.  The Router Upgrade notification elements 
in the UI, introduced in 4.3 are also broken (this should possibly be a -1 as 
it could result in installs running with the wrong version of the VRs without 
realising)

Notes:

2x XenServer 6.2 in a single Cluster
NFS Primary Storage x2
System VM Template from 
http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4.4-2014-09-30-xen.vhd.bz2
Clean install of 4.4.1 to single management server on CentOS 6.5 with MySQL 
installed locally
Created new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
Updated Various Global Settings via API
Created Domains and Accounts via API
Deployed VMs for user account as Root and configured network Egress rules via 
API
Deployed VM as root via UI
Live Migrated VMs between Hosts
Offline Migrated (VM stopped) Root Volume between Pri Storage via UI - 
cloudstack service crashed! (Install is running inside VirtualBox and 
Management VM is also NFS Server so added more RAM and tried again) - repeated 
test after a manual clean up and it was successful
Live Migrated (VM running) Root Volume between Pri Storage via UI
Disabled / Re-enabled Host
Adding / removing NICs and changing default etc via UI
Deployed new VPC, with two tiers, added VM to each tier, setup ACLs etc via API


Then I did an upgrade test of a 4.3.1 system using the latest system VM 
template from Jenkins (this system was originally built on 4.3.0 and upgraded 
to 4.3.1, before being upgraded to 4.4.1)
New System VM template installed OK

The steps in the release notes about downloading vhd-utils for XenServer are 
misleading.  If you blindly follow the steps the simply end up with a 2nd copy 
'vhd-utils.1' as this is an upgrade and you will already have vhd-utils on the 
management server, at least if upgrading from a recent release such as 4.3.x.

If vhd-utils needs replacing we need to be specific about removing the old one. 
 I don’t think it actually needs replacing, it's just in a different location 
to older installs, but the 4.3 upgrade guide still has this step in it. (I 
can't remember which release changed the location)

The MySQL Statements for the manual upgrade of the template are also incorrect 
as they do not include the DB name so fail

e.g.
select id,name from vm_template where name = 'systemvm-xenserver-4.4';

should be
select id,name from cloud.vm_template where name = 'systemvm-xenserver-4.4';

The same with the following commands

update vm_template set type='SYSTEM' where id='';
update vm_instance set vm_template_id = '' where 
type='ConsoleProxy' and hypervisor_type = 'xenserver';
update vm_instance set vm_template_id = '' where 
type='SecondaryStorageVm' and hypervisor_type = 'xenserver';
update configuration set value = 'systemvm-xenserver-4.4' where name = 
'router.template.xen';

should be

update cloud.vm_template set type='SYSTEM' where id='';
update cloud.vm_instance set vm_template_id = '' where 
type='ConsoleProxy' and hypervisor_type = 'xenserver';
update cloud.vm_instance set vm_template_id = '' where 
type='SecondaryStorageVm' and hypervisor_type = 'xenserver';
update cloud.configuration set value = 'systemvm-xenserver-4.4' where name = 
'router.template.xen';

However I did not need to do this as the cloud.vm_instance table and 
cloud.configuration table had automatically been updated to the correct values, 
so are these steps actually necessary?

4.3 introduced the ability to manage the restart of VRs via the UI, but after 
upgrading to 4.4.1 the UI lists all VRs as NOT requiring upgrade, even though 
they have not been upgraded yet and are clearly shown as still be at version 4.3

I could fix the release notes issues, but there may be good reasons why they 
are how they are that I am not aware of, so just wanted to highlight them for 
now.  I have only tested the XenServer upgrade steps and only from 4.3 so there 
may be similar errors in other sections.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
Sent: 30 September 2014 03:31
To: dev@cloudstack.apache.org
Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 
4.4-RC20140924T2100

+1

basic deployment, did tests upgrade from 4.3.0  and 4.2.1 to 4.4.1 , it went 
smoothly in both cases.
I've tests using XenServer 6.2.0 with system vm from :
http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/131/

Please let me know what should be the URLs for system vm that will goes in the 
RN if this vote pass.




*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683

*CloudOps* Votre parte

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Pierre-Luc Dion]

Geoff,

Could it be possible you've followed 4.4.0 upgrade path ? because we don't
have to perform any MySQL query when upgrading to 4.4.1,  otherwise the RN
is not correct.
the current RN for 4.4.1 is:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/
 (not /latest yet as it's not release yet)

for the vhd-utils, I wasn't sure if it was making sense to keep it on all
upgrade path, thanks for the comment, make sense to remove if from upgrade
4.3.x and probably 4.2.x as it should already be in place.


PL




On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
geoff.higginbot...@shapeblue.com> wrote:

> +0  only because of the issues in the release notes, a clean install and
> an upgrade from 4.3.1 went OK, but only because I know how to do it, it
> would not work if I followed the release notes.  The Router Upgrade
> notification elements in the UI, introduced in 4.3 are also broken (this
> should possibly be a -1 as it could result in installs running with the
> wrong version of the VRs without realising)
>
> Notes:
>
> 2x XenServer 6.2 in a single Cluster
> NFS Primary Storage x2
> System VM Template from
> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4.4-2014-09-30-xen.vhd.bz2
> Clean install of 4.4.1 to single management server on CentOS 6.5 with
> MySQL installed locally
> Created new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
> Updated Various Global Settings via API
> Created Domains and Accounts via API
> Deployed VMs for user account as Root and configured network Egress rules
> via API
> Deployed VM as root via UI
> Live Migrated VMs between Hosts
> Offline Migrated (VM stopped) Root Volume between Pri Storage via UI -
> cloudstack service crashed! (Install is running inside VirtualBox and
> Management VM is also NFS Server so added more RAM and tried again) -
> repeated test after a manual clean up and it was successful
> Live Migrated (VM running) Root Volume between Pri Storage via UI
> Disabled / Re-enabled Host
> Adding / removing NICs and changing default etc via UI
> Deployed new VPC, with two tiers, added VM to each tier, setup ACLs etc
> via API
>
>
> Then I did an upgrade test of a 4.3.1 system using the latest system VM
> template from Jenkins (this system was originally built on 4.3.0 and
> upgraded to 4.3.1, before being upgraded to 4.4.1)
> New System VM template installed OK
>
> The steps in the release notes about downloading vhd-utils for XenServer
> are misleading.  If you blindly follow the steps the simply end up with a
> 2nd copy 'vhd-utils.1' as this is an upgrade and you will already have
> vhd-utils on the management server, at least if upgrading from a recent
> release such as 4.3.x.
>
> If vhd-utils needs replacing we need to be specific about removing the old
> one.  I don’t think it actually needs replacing, it's just in a different
> location to older installs, but the 4.3 upgrade guide still has this step
> in it. (I can't remember which release changed the location)
>
> The MySQL Statements for the manual upgrade of the template are also
> incorrect as they do not include the DB name so fail
>
> e.g.
> select id,name from vm_template where name = 'systemvm-xenserver-4.4';
>
> should be
> select id,name from cloud.vm_template where name =
> 'systemvm-xenserver-4.4';
>
> The same with the following commands
>
> update vm_template set type='SYSTEM' where id='';
> update vm_instance set vm_template_id = '' where
> type='ConsoleProxy' and hypervisor_type = 'xenserver';
> update vm_instance set vm_template_id = '' where
> type='SecondaryStorageVm' and hypervisor_type = 'xenserver';
> update configuration set value = 'systemvm-xenserver-4.4' where name =
> 'router.template.xen';
>
> should be
>
> update cloud.vm_template set type='SYSTEM' where id='';
> update cloud.vm_instance set vm_template_id = '' where
> type='ConsoleProxy' and hypervisor_type = 'xenserver';
> update cloud.vm_instance set vm_template_id = '' where
> type='SecondaryStorageVm' and hypervisor_type = 'xenserver';
> update cloud.configuration set value = 'systemvm-xenserver-4.4' where name
> = 'router.template.xen';
>
> However I did not need to do this as the cloud.vm_instance table and
> cloud.configuration table had automatically been updated to the correct
> values, so are these steps actually necessary?
>
> 4.3 introduced the ability to manage the restart of VRs via the UI, but
> after upgrading to 4.4.1 the UI lists all VRs as NOT requiring upgrade,
> even though they have not been upgraded yet and are clearly shown as still
> be at version 4.3
>
> I could fix the release notes issues, but there may be good reasons why
> they are how they are that I am not aware of, so just wanted to highlight
> them for now.  I have only tested the XenServer upgrade steps and only from
> 4.3 so there may be similar errors in other sections.
>
> Regards
>
> Geoff Higginbottom

RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Geoff Higginbottom]

Hi Pierre-Luc,

Nope, I was deffinately looking at 4.4.1 release notes, complete with sections 
titled 'Issues fixed in 4.4.1' etc

http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgrade-4.3.html

I would include a screen shot of the page but it will get stripped from the 
e-mail

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
Sent: 01 October 2014 14:49
To: dev@cloudstack.apache.org
Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 
4.4-RC20140924T2100

Geoff,

Could it be possible you've followed 4.4.0 upgrade path ? because we don't have 
to perform any MySQL query when upgrading to 4.4.1,  otherwise the RN is not 
correct.
the current RN for 4.4.1 is:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/
 (not /latest yet as it's not release yet)

for the vhd-utils, I wasn't sure if it was making sense to keep it on all 
upgrade path, thanks for the comment, make sense to remove if from upgrade 
4.3.x and probably 4.2.x as it should already be in place.


PL




On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom < 
geoff.higginbot...@shapeblue.com> wrote:

> +0  only because of the issues in the release notes, a clean install
> +and
> an upgrade from 4.3.1 went OK, but only because I know how to do it,
> it would not work if I followed the release notes.  The Router Upgrade
> notification elements in the UI, introduced in 4.3 are also broken
> (this should possibly be a -1 as it could result in installs running
> with the wrong version of the VRs without realising)
>
> Notes:
>
> 2x XenServer 6.2 in a single Cluster
> NFS Primary Storage x2
> System VM Template from
> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/
> lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4
> .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single management
> server on CentOS 6.5 with MySQL installed locally Created new Zone,
> POD, Cluster, Sec Storage, Hosts, Pri Storage all via API Updated
> Various Global Settings via API Created Domains and Accounts via API
> Deployed VMs for user account as Root and configured network Egress
> rules via API Deployed VM as root via UI Live Migrated VMs between
> Hosts Offline Migrated (VM stopped) Root Volume between Pri Storage
> via UI - cloudstack service crashed! (Install is running inside
> VirtualBox and Management VM is also NFS Server so added more RAM and
> tried again) - repeated test after a manual clean up and it was
> successful Live Migrated (VM running) Root Volume between Pri Storage
> via UI Disabled / Re-enabled Host Adding / removing NICs and changing
> default etc via UI Deployed new VPC, with two tiers, added VM to each
> tier, setup ACLs etc via API
>
>
> Then I did an upgrade test of a 4.3.1 system using the latest system
> VM template from Jenkins (this system was originally built on 4.3.0
> and upgraded to 4.3.1, before being upgraded to 4.4.1) New System VM
> template installed OK
>
> The steps in the release notes about downloading vhd-utils for
> XenServer are misleading.  If you blindly follow the steps the simply
> end up with a 2nd copy 'vhd-utils.1' as this is an upgrade and you
> will already have vhd-utils on the management server, at least if
> upgrading from a recent release such as 4.3.x.
>
> If vhd-utils needs replacing we need to be specific about removing the
> old one.  I don’t think it actually needs replacing, it's just in a
> different location to older installs, but the 4.3 upgrade guide still
> has this step in it. (I can't remember which release changed the
> location)
>
> The MySQL Statements for the manual upgrade of the template are also
> incorrect as they do not include the DB name so fail
>
> e.g.
> select id,name from vm_template where name = 'systemvm-xenserver-4.4';
>
> should be
> select id,name from cloud.vm_template where name =
> 'systemvm-xenserver-4.4';
>
> The same with the following commands
>
> update vm_template set type='SYSTEM' where id='';
> update vm_instance set vm_template_id = '' where
> type='ConsoleProxy' and hypervisor_type = 'xenserver'; update
> vm_instance set vm_template_id = '' where
> type='SecondaryStorageVm' and hypervisor_type = 'xenserver'; update
> configuration set value = 'systemvm-xenserver-4.4' where name =
> 'router.template.xen';
>
> should be
>
> update cloud.vm_template set type='SYSTEM' where id=' #1>'; update cloud.vm_instance set vm_template_id = ' #1>' where type='ConsoleProxy' and hypervisor_type = 'xenserver';
> update cloud.vm_instance set vm_template_id = ''
> where type='SecondaryStorageVm' and hypervisor_type = 'xenserver';
> update cloud.configuration set value = 'systemvm-xenserver-4.4' where
> name = 'router.template.xen';
>
> However I did not need to do this as the cloud.vm_instance table and
> cloud.configuration table had 

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Pierre-Luc Dion]

ok, fixed it ,  /latest is pointing on the master branch for the RN git
repo. so it's not reflecting the "latest" version of our product.
I've disable the /latest version so URL  will default to 4.4.0 RN  for the
moment, and the 4.4.1 RN is the correct one.

Seb, do you see a problem disabling  master and latest build in RTD ?

make more sense?

PL

On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom <
geoff.higginbot...@shapeblue.com> wrote:

> Hi Pierre-Luc,
>
> Nope, I was deffinately looking at 4.4.1 release notes, complete with
> sections titled 'Issues fixed in 4.4.1' etc
>
>
> http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgrade-4.3.html
>
> I would include a screen shot of the page but it will get stripped from
> the e-mail
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 14:49
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> Geoff,
>
> Could it be possible you've followed 4.4.0 upgrade path ? because we don't
> have to perform any MySQL query when upgrading to 4.4.1,  otherwise the RN
> is not correct.
> the current RN for 4.4.1 is:
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/
>  (not /latest yet as it's not release yet)
>
> for the vhd-utils, I wasn't sure if it was making sense to keep it on all
> upgrade path, thanks for the comment, make sense to remove if from upgrade
> 4.3.x and probably 4.2.x as it should already be in place.
>
>
> PL
>
>
>
>
> On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
> > +0  only because of the issues in the release notes, a clean install
> > +and
> > an upgrade from 4.3.1 went OK, but only because I know how to do it,
> > it would not work if I followed the release notes.  The Router Upgrade
> > notification elements in the UI, introduced in 4.3 are also broken
> > (this should possibly be a -1 as it could result in installs running
> > with the wrong version of the VRs without realising)
> >
> > Notes:
> >
> > 2x XenServer 6.2 in a single Cluster
> > NFS Primary Storage x2
> > System VM Template from
> > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/
> > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4
> > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single management
> > server on CentOS 6.5 with MySQL installed locally Created new Zone,
> > POD, Cluster, Sec Storage, Hosts, Pri Storage all via API Updated
> > Various Global Settings via API Created Domains and Accounts via API
> > Deployed VMs for user account as Root and configured network Egress
> > rules via API Deployed VM as root via UI Live Migrated VMs between
> > Hosts Offline Migrated (VM stopped) Root Volume between Pri Storage
> > via UI - cloudstack service crashed! (Install is running inside
> > VirtualBox and Management VM is also NFS Server so added more RAM and
> > tried again) - repeated test after a manual clean up and it was
> > successful Live Migrated (VM running) Root Volume between Pri Storage
> > via UI Disabled / Re-enabled Host Adding / removing NICs and changing
> > default etc via UI Deployed new VPC, with two tiers, added VM to each
> > tier, setup ACLs etc via API
> >
> >
> > Then I did an upgrade test of a 4.3.1 system using the latest system
> > VM template from Jenkins (this system was originally built on 4.3.0
> > and upgraded to 4.3.1, before being upgraded to 4.4.1) New System VM
> > template installed OK
> >
> > The steps in the release notes about downloading vhd-utils for
> > XenServer are misleading.  If you blindly follow the steps the simply
> > end up with a 2nd copy 'vhd-utils.1' as this is an upgrade and you
> > will already have vhd-utils on the management server, at least if
> > upgrading from a recent release such as 4.3.x.
> >
> > If vhd-utils needs replacing we need to be specific about removing the
> > old one.  I don’t think it actually needs replacing, it's just in a
> > different location to older installs, but the 4.3 upgrade guide still
> > has this step in it. (I can't remember which release changed the
> > location)
> >
> > The MySQL Statements for the manual upgrade of the template are also
> > incorrect as they do not include the DB name so fail
> >
> > e.g.
> > select id,name from vm_template where name = 'systemvm-xenserver-4.4';
> >
> > should be
> > select id,name from cloud.vm_template where name =
> > 'systemvm-xenserver-4.4';
> >
> > The same with the following commands
> >
> > update vm_template set type='SYSTEM' where id='';
> > update vm_instance set vm_template_id = '' where
> > type='ConsoleProxy' and hypervisor_type = 'xenserver'; update
> > vm_instance set vm_template_id = '' where
> > type='SecondaryStorageVm' and 

Re: Unable to upload SSL certificate for realhostip replacement

[Rohit Yadav]

Hi,

I’ve fixed cloudmonkey to url encode parameters so now you can use cloudmonkey 
to upload custom certificate but only in non-interactive mode on shell 
(bash/zsh). You’ll have to install cloudmonkey from source for now since the 
fix is only on master.

Something like:
$ cloudmonkey upload customcertificate id=xx domainsuffix=yy name=zzz 
certificate=‘asdf
asdfasdf
asdfasdf
asdf---'

I’ve some issues to report while replacing certificates to get rid of 
realhostip, this is specific for Xen could apply for other hypervisors as well:

- In case of 4.2, I see in the database that seq is 0 for the root certificate 
for the realhostip.com domain. I uploaded certificates in order (root, then 
intermediate and finally SSL cert from UI), and I see the old certificate is 
still there. after CPVM/SSVM restarts and are in UP state I still get SSL 
errors and I see that systemvm.iso is not getting patched. How to fix this? Or 
force systemvm.iso patching?

- In case of 4.3.0 and above, I see the same issue. I’m confused whether to use 
*. wildcard in global setting or not.

On 27-Sep-2014, at 9:32 pm, Amogh Vasekar  wrote:
> Hi,
>
> For the encoding, in your case it was the space character causing the
> issue - it should be replaced by %20. The correct encoding would be
> (hoping mail clients don't screw up the blob):
> -BEGIN%20CERTIFICATE-%0AMIIDfTCCAuagAwIBAgIDErvmMA0GCSqGSIb3DQEBBQU
> AME4xCzAJBgNVBAYTAlVT%0AMRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4IFN
> lY3VyZSBDZXJ0%0AaWZpY2F0ZSBBdXRob3JpdHkwHhcNMDIwNTIxMDQwMDAwWhcNMTgwODIxMDQ
> wMDAw%0AWjBCMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNR2VvVHJ1c3QgSW5jLjEbMBkGA1UE%0A
> AxMSR2VvVHJ1c3QgR2xvYmFsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB%0ACgKCAQEA
> 2swYYzD99BcjGlZ%2BW988bDjkcbd4kdS8odhM%2BKhDtgPpTSEHCIjaWC9m%0AOSm9BXiLnTjo
> BbdqfnGk5sRgprDvgOSJKA%2BeJdbtg%2FOtppHHmMlCGDUUna2YRpIu%0AT8rxh0PBFpVXLVDv
> iS2Aelet8u5fa9IAjbkU%2BBQVNdnARqN7csiRv8lVK83Qlz6c%0AJmTM386DGXHKTubU1XupGc
> 1V3sjs0l44U%2BVcT4wt%2FlAjNvxm5suOpDkZALeVAjmR%0ACw7%2BOC7RHQWa9k0%2Bbw8HHa
> 8sHo9gOeL6NlMTOdReJivbPagUvTLrGAMoUgRx5asz%0APeE4uwc2hGKceeoWMPRfwCvocWvk%2
> BQIDAQABo4HwMIHtMB8GA1UdIwQYMBaAFEjm%0AaPkr0rKV10fYIyAQTzOYkJ%2FUMB0GA1UdDg
> QWBBTAephojYn7qwVkDBF9qn1luMrM%0ATjAPBgNVHRMBAf8EBTADAQH%2FMA4GA1UdDwEB%2Fw
> QEAwIBBjA6BgNVHR8EMzAxMC%2Bg%0ALaArhilodHRwOi8vY3JsLmdlb3RydXN0LmNvbS9jcmxz
> L3NlY3VyZWNhLmNybDBO%0ABgNVHSAERzBFMEMGBFUdIAAwOzA5BggrBgEFBQcCARYtaHR0cHM6
> Ly93d3cuZ2Vv%0AdHJ1c3QuY29tL3Jlc291cmNlcy9yZXBvc2l0b3J5MA0GCSqGSIb3DQEBBQUA
> A4GB%0AAHbhEm5OSxYShjAGsoEIz%2FAIx8dxfmbuwu3UOx%2F%2F8PDITtZDOLC5MH0Y0FWDom
> rL%0ANhGc6Ehmo21%2FuBPUR%2F6LWlxz%2FK7ZGzIZOKuXNBSqltLroxwUCEm2u%2BWR74M26x
> 1W%0Ab8ravHNjkOR%2Fez4iyz0H7V84dJzjA1BOoa%2BY7mHyhD8S%0A-END%20CERTIFIC
> ATE-
>
> As for the global parameter, you can set it to something like a few
> seconds and reset to original value when the URLs have been expired.
>
> Thanks
> Amogh
>
>
> On 9/27/14 10:53 AM, "Indra Pramana"  wrote:
>
>> Hi Wido,
>>
>> I have changed the value of secstorage.ssl.cert.domain and restart
>> management server, before I start uploading all the certificates.
>>
>> I found this article, which might be related to the problem:
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Troubleshooting+-+u
>> ploading+custom+domain+certificate+instead+of+using+realhostip.com
>>
>> 
>>
>> *Specific Issues seen*
>>
>>  1. Download urls point to the old domain.
>> 1. Reduce the expiration duration of the urls by changing global
>> config extract.url.expiration.interval
>> 2. And change the frequency for cleanup thread
>> through extract.url.cleanup.interval restart MS.
>> 3. Wait for the cleanup thread duration and try downloading again.
>> See whether the url is deleted.
>> 4. DB tables to check (don¹t recommend but worst case)
>> Version < 4.2 ­ upload table persists url. Entry is hard deleted on
>> expiration of url.
>> Version >= 4.2 ­
>> template_store_ref, download_url is made null on expiration of url.
>> volume_store_ref, entry hard deleted on expiration of url.
>>
>> 
>>
>> But I'm not too sure what is the recommended values I need to set for
>> extract.url.expiration.interval and extract.url.cleanup.interval. Any
>> advise?
>>
>> Thank you.
>>
>>
>>
>> On Sun, Sep 28, 2014 at 1:39 AM, Wido den Hollander 
>> wrote:
>>
>>>
>>>
>>>
>>>
 Op 27 sep. 2014 om 19:25 heeft Indra Pramana  het
>>> volgende geschreven:

 Dear all,

 FYI, I managed to complete the tasks and install the certificates. As
>>> a
 workaround to the unable to upload the root/intermediate cert via API
 issue, I uploaded a certificate with just "BEGIN" as text via API, and
>>> then
 proceed to update the keystore table on the MySQL database directly to
 input the whole cert.

 It seems to be working, after I uploaded the cert and private key via
>>> GUI,
 I can see that both CPVM and SSVM are being restarted. When I test:

 - C

RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Geoff Higginbottom]

Great, glad to hear it was an easy fix.

Now however I have found another problem.  In the UI if I go to 
Infrastructure/Clusters/cluster1/and then choose the settings tab, I get an 
error and no information is displayed.

Can others please check this to see if it is a unique problem to me or a common 
issue.  This is on my upgraded install, I'll the check the clean install in a 
few minutes once its power up.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
Sent: 01 October 2014 15:29
To: dev@cloudstack.apache.org; Sebastien Goasguen
Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 
4.4-RC20140924T2100

ok, fixed it ,  /latest is pointing on the master branch for the RN git repo. 
so it's not reflecting the "latest" version of our product.
I've disable the /latest version so URL  will default to 4.4.0 RN  for the 
moment, and the 4.4.1 RN is the correct one.

Seb, do you see a problem disabling  master and latest build in RTD ?

make more sense?

PL

On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom < 
geoff.higginbot...@shapeblue.com> wrote:

> Hi Pierre-Luc,
>
> Nope, I was deffinately looking at 4.4.1 release notes, complete with
> sections titled 'Issues fixed in 4.4.1' etc
>
>
> http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgr
> ade-4.3.html
>
> I would include a screen shot of the page but it will get stripped
> from the e-mail
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 14:49
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> Geoff,
>
> Could it be possible you've followed 4.4.0 upgrade path ? because we
> don't have to perform any MySQL query when upgrading to 4.4.1,
> otherwise the RN is not correct.
> the current RN for 4.4.1 is:
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en
> /4.4.1/  (not /latest yet as it's not release yet)
>
> for the vhd-utils, I wasn't sure if it was making sense to keep it on
> all upgrade path, thanks for the comment, make sense to remove if from
> upgrade 4.3.x and probably 4.2.x as it should already be in place.
>
>
> PL
>
>
>
>
> On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
> > +0  only because of the issues in the release notes, a clean install
> > +and
> > an upgrade from 4.3.1 went OK, but only because I know how to do it,
> > it would not work if I followed the release notes.  The Router
> > Upgrade notification elements in the UI, introduced in 4.3 are also
> > broken (this should possibly be a -1 as it could result in installs
> > running with the wrong version of the VRs without realising)
> >
> > Notes:
> >
> > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System
> > VM Template from
> > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6
> > 4/
> > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
> > -4
> > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single
> > management server on CentOS 6.5 with MySQL installed locally Created
> > new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
> > Updated Various Global Settings via API Created Domains and Accounts
> > via API Deployed VMs for user account as Root and configured network
> > Egress rules via API Deployed VM as root via UI Live Migrated VMs
> > between Hosts Offline Migrated (VM stopped) Root Volume between Pri
> > Storage via UI - cloudstack service crashed! (Install is running
> > inside VirtualBox and Management VM is also NFS Server so added more
> > RAM and tried again) - repeated test after a manual clean up and it
> > was successful Live Migrated (VM running) Root Volume between Pri
> > Storage via UI Disabled / Re-enabled Host Adding / removing NICs and
> > changing default etc via UI Deployed new VPC, with two tiers, added
> > VM to each tier, setup ACLs etc via API
> >
> >
> > Then I did an upgrade test of a 4.3.1 system using the latest system
> > VM template from Jenkins (this system was originally built on 4.3.0
> > and upgraded to 4.3.1, before being upgraded to 4.4.1) New System VM
> > template installed OK
> >
> > The steps in the release notes about downloading vhd-utils for
> > XenServer are misleading.  If you blindly follow the steps the
> > simply end up with a 2nd copy 'vhd-utils.1' as this is an upgrade
> > and you will already have vhd-utils on the management server, at
> > least if upgrading from a recent release such as 4.3.x.
> >
> > If vhd-utils needs replacing we need to be specific about removing
> > the old one.  I don’t think it actually needs replacing, it's 

Re: Unable to upload SSL certificate for realhostip replacement

[Rohit Yadav]

Just to update on the certificate upload issue with 4.2:

I’m able to download and add new volumes/templates/isos and the link provided 
has a valid https url with the same certificate that I uploaded though when I 
try to access the console I get SSL cert error and I see that it’s still 
returning the old *.realhostip.com certificate. I’ve tried to delete old CPVMs 
and I see the same issue coming up again.


On 01-Oct-2014, at 4:55 pm, Rohit Yadav  wrote:
> Hi,
>
> I’ve fixed cloudmonkey to url encode parameters so now you can use 
> cloudmonkey to upload custom certificate but only in non-interactive mode on 
> shell (bash/zsh). You’ll have to install cloudmonkey from source for now 
> since the fix is only on master.
>
> Something like:
> $ cloudmonkey upload customcertificate id=xx domainsuffix=yy name=zzz 
> certificate=‘asdf
> asdfasdf
> asdfasdf
> asdf---'
>
> I’ve some issues to report while replacing certificates to get rid of 
> realhostip, this is specific for Xen could apply for other hypervisors as 
> well:
>
> - In case of 4.2, I see in the database that seq is 0 for the root 
> certificate for the realhostip.com domain. I uploaded certificates in order 
> (root, then intermediate and finally SSL cert from UI), and I see the old 
> certificate is still there. after CPVM/SSVM restarts and are in UP state I 
> still get SSL errors and I see that systemvm.iso is not getting patched. How 
> to fix this? Or force systemvm.iso patching?
>
> - In case of 4.3.0 and above, I see the same issue. I’m confused whether to 
> use *. wildcard in global setting or not.
>
> On 27-Sep-2014, at 9:32 pm, Amogh Vasekar  wrote:
>> Hi,
>>
>> For the encoding, in your case it was the space character causing the
>> issue - it should be replaced by %20. The correct encoding would be
>> (hoping mail clients don't screw up the blob):
>> -BEGIN%20CERTIFICATE-%0AMIIDfTCCAuagAwIBAgIDErvmMA0GCSqGSIb3DQEBBQU
>> AME4xCzAJBgNVBAYTAlVT%0AMRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4IFN
>> lY3VyZSBDZXJ0%0AaWZpY2F0ZSBBdXRob3JpdHkwHhcNMDIwNTIxMDQwMDAwWhcNMTgwODIxMDQ
>> wMDAw%0AWjBCMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNR2VvVHJ1c3QgSW5jLjEbMBkGA1UE%0A
>> AxMSR2VvVHJ1c3QgR2xvYmFsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB%0ACgKCAQEA
>> 2swYYzD99BcjGlZ%2BW988bDjkcbd4kdS8odhM%2BKhDtgPpTSEHCIjaWC9m%0AOSm9BXiLnTjo
>> BbdqfnGk5sRgprDvgOSJKA%2BeJdbtg%2FOtppHHmMlCGDUUna2YRpIu%0AT8rxh0PBFpVXLVDv
>> iS2Aelet8u5fa9IAjbkU%2BBQVNdnARqN7csiRv8lVK83Qlz6c%0AJmTM386DGXHKTubU1XupGc
>> 1V3sjs0l44U%2BVcT4wt%2FlAjNvxm5suOpDkZALeVAjmR%0ACw7%2BOC7RHQWa9k0%2Bbw8HHa
>> 8sHo9gOeL6NlMTOdReJivbPagUvTLrGAMoUgRx5asz%0APeE4uwc2hGKceeoWMPRfwCvocWvk%2
>> BQIDAQABo4HwMIHtMB8GA1UdIwQYMBaAFEjm%0AaPkr0rKV10fYIyAQTzOYkJ%2FUMB0GA1UdDg
>> QWBBTAephojYn7qwVkDBF9qn1luMrM%0ATjAPBgNVHRMBAf8EBTADAQH%2FMA4GA1UdDwEB%2Fw
>> QEAwIBBjA6BgNVHR8EMzAxMC%2Bg%0ALaArhilodHRwOi8vY3JsLmdlb3RydXN0LmNvbS9jcmxz
>> L3NlY3VyZWNhLmNybDBO%0ABgNVHSAERzBFMEMGBFUdIAAwOzA5BggrBgEFBQcCARYtaHR0cHM6
>> Ly93d3cuZ2Vv%0AdHJ1c3QuY29tL3Jlc291cmNlcy9yZXBvc2l0b3J5MA0GCSqGSIb3DQEBBQUA
>> A4GB%0AAHbhEm5OSxYShjAGsoEIz%2FAIx8dxfmbuwu3UOx%2F%2F8PDITtZDOLC5MH0Y0FWDom
>> rL%0ANhGc6Ehmo21%2FuBPUR%2F6LWlxz%2FK7ZGzIZOKuXNBSqltLroxwUCEm2u%2BWR74M26x
>> 1W%0Ab8ravHNjkOR%2Fez4iyz0H7V84dJzjA1BOoa%2BY7mHyhD8S%0A-END%20CERTIFIC
>> ATE-
>>
>> As for the global parameter, you can set it to something like a few
>> seconds and reset to original value when the URLs have been expired.
>>
>> Thanks
>> Amogh
>>
>>
>> On 9/27/14 10:53 AM, "Indra Pramana"  wrote:
>>
>>> Hi Wido,
>>>
>>> I have changed the value of secstorage.ssl.cert.domain and restart
>>> management server, before I start uploading all the certificates.
>>>
>>> I found this article, which might be related to the problem:
>>>
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Troubleshooting+-+u
>>> ploading+custom+domain+certificate+instead+of+using+realhostip.com
>>>
>>> 
>>>
>>> *Specific Issues seen*
>>>
>>> 1. Download urls point to the old domain.
>>>1. Reduce the expiration duration of the urls by changing global
>>>config extract.url.expiration.interval
>>>2. And change the frequency for cleanup thread
>>>through extract.url.cleanup.interval restart MS.
>>>3. Wait for the cleanup thread duration and try downloading again.
>>>See whether the url is deleted.
>>>4. DB tables to check (don¹t recommend but worst case)
>>>Version < 4.2 ­ upload table persists url. Entry is hard deleted on
>>>expiration of url.
>>>Version >= 4.2 ­
>>>template_store_ref, download_url is made null on expiration of url.
>>>volume_store_ref, entry hard deleted on expiration of url.
>>>
>>> 
>>>
>>> But I'm not too sure what is the recommended values I need to set for
>>> extract.url.expiration.interval and extract.url.cleanup.interval. Any
>>> advise?
>>>
>>> Thank you.
>>>
>>>
>>>
>>> On Sun, Sep 28, 2014 at 1:39 AM, Wido den Hollander 
>>> wrote:
>>>




> Op 27 sep. 2014 om 19:25 heeft Indra 

RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Geoff Higginbottom]

The Cluster Details UI issue is only present on my upgraded system, a clean 
install of 4.4.1 correctly shows the value.

Need someone else who upgraded to also check

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com]
Sent: 01 October 2014 16:16
To: dev@cloudstack.apache.org; Sebastien Goasguen
Subject: RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 
4.4-RC20140924T2100

Great, glad to hear it was an easy fix.

Now however I have found another problem.  In the UI if I go to 
Infrastructure/Clusters/cluster1/and then choose the settings tab, I get an 
error and no information is displayed.

Can others please check this to see if it is a unique problem to me or a common 
issue.  This is on my upgraded install, I'll the check the clean install in a 
few minutes once its power up.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
Sent: 01 October 2014 15:29
To: dev@cloudstack.apache.org; Sebastien Goasguen
Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 
4.4-RC20140924T2100

ok, fixed it ,  /latest is pointing on the master branch for the RN git repo. 
so it's not reflecting the "latest" version of our product.
I've disable the /latest version so URL  will default to 4.4.0 RN  for the 
moment, and the 4.4.1 RN is the correct one.

Seb, do you see a problem disabling  master and latest build in RTD ?

make more sense?

PL

On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom < 
geoff.higginbot...@shapeblue.com> wrote:

> Hi Pierre-Luc,
>
> Nope, I was deffinately looking at 4.4.1 release notes, complete with
> sections titled 'Issues fixed in 4.4.1' etc
>
>
> http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgr
> ade-4.3.html
>
> I would include a screen shot of the page but it will get stripped
> from the e-mail
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 14:49
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> Geoff,
>
> Could it be possible you've followed 4.4.0 upgrade path ? because we
> don't have to perform any MySQL query when upgrading to 4.4.1,
> otherwise the RN is not correct.
> the current RN for 4.4.1 is:
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en
> /4.4.1/  (not /latest yet as it's not release yet)
>
> for the vhd-utils, I wasn't sure if it was making sense to keep it on
> all upgrade path, thanks for the comment, make sense to remove if from
> upgrade 4.3.x and probably 4.2.x as it should already be in place.
>
>
> PL
>
>
>
>
> On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
> > +0  only because of the issues in the release notes, a clean install
> > +and
> > an upgrade from 4.3.1 went OK, but only because I know how to do it,
> > it would not work if I followed the release notes.  The Router
> > Upgrade notification elements in the UI, introduced in 4.3 are also
> > broken (this should possibly be a -1 as it could result in installs
> > running with the wrong version of the VRs without realising)
> >
> > Notes:
> >
> > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System
> > VM Template from
> > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6
> > 4/
> > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
> > -4
> > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single
> > management server on CentOS 6.5 with MySQL installed locally Created
> > new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
> > Updated Various Global Settings via API Created Domains and Accounts
> > via API Deployed VMs for user account as Root and configured network
> > Egress rules via API Deployed VM as root via UI Live Migrated VMs
> > between Hosts Offline Migrated (VM stopped) Root Volume between Pri
> > Storage via UI - cloudstack service crashed! (Install is running
> > inside VirtualBox and Management VM is also NFS Server so added more
> > RAM and tried again) - repeated test after a manual clean up and it
> > was successful Live Migrated (VM running) Root Volume between Pri
> > Storage via UI Disabled / Re-enabled Host Adding / removing NICs and
> > changing default etc via UI Deployed new VPC, with two tiers, added
> > VM to each tier, setup ACLs etc via API
> >
> >
> > Then I did an upgrade test of a 4.3.1 system using the latest system
> > VM template from Jenkins (this system was originally built on 4.3.0
> > and upgraded to 4.3.1

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Pierre-Luc Dion]

yep, this is the JIRA: https://issues.apache.org/jira/browse/CLOUDSTACK-7219

unfortunately it hasn't been fixed in 4.4.1 :-(


PL

On Wed, Oct 1, 2014 at 11:16 AM, Geoff Higginbottom <
geoff.higginbot...@shapeblue.com> wrote:

> Great, glad to hear it was an easy fix.
>
> Now however I have found another problem.  In the UI if I go to
> Infrastructure/Clusters/cluster1/and then choose the settings tab, I get an
> error and no information is displayed.
>
> Can others please check this to see if it is a unique problem to me or a
> common issue.  This is on my upgraded install, I'll the check the clean
> install in a few minutes once its power up.
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 15:29
> To: dev@cloudstack.apache.org; Sebastien Goasguen
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> ok, fixed it ,  /latest is pointing on the master branch for the RN git
> repo. so it's not reflecting the "latest" version of our product.
> I've disable the /latest version so URL  will default to 4.4.0 RN  for the
> moment, and the 4.4.1 RN is the correct one.
>
> Seb, do you see a problem disabling  master and latest build in RTD ?
>
> make more sense?
>
> PL
>
> On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
> > Hi Pierre-Luc,
> >
> > Nope, I was deffinately looking at 4.4.1 release notes, complete with
> > sections titled 'Issues fixed in 4.4.1' etc
> >
> >
> > http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgr
> > ade-4.3.html
> >
> > I would include a screen shot of the page but it will get stripped
> > from the e-mail
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > Sent: 01 October 2014 14:49
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > 4.4-RC20140924T2100
> >
> > Geoff,
> >
> > Could it be possible you've followed 4.4.0 upgrade path ? because we
> > don't have to perform any MySQL query when upgrading to 4.4.1,
> > otherwise the RN is not correct.
> > the current RN for 4.4.1 is:
> >
> > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en
> > /4.4.1/  (not /latest yet as it's not release yet)
> >
> > for the vhd-utils, I wasn't sure if it was making sense to keep it on
> > all upgrade path, thanks for the comment, make sense to remove if from
> > upgrade 4.3.x and probably 4.2.x as it should already be in place.
> >
> >
> > PL
> >
> >
> >
> >
> > On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> > geoff.higginbot...@shapeblue.com> wrote:
> >
> > > +0  only because of the issues in the release notes, a clean install
> > > +and
> > > an upgrade from 4.3.1 went OK, but only because I know how to do it,
> > > it would not work if I followed the release notes.  The Router
> > > Upgrade notification elements in the UI, introduced in 4.3 are also
> > > broken (this should possibly be a -1 as it could result in installs
> > > running with the wrong version of the VRs without realising)
> > >
> > > Notes:
> > >
> > > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System
> > > VM Template from
> > > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6
> > > 4/
> > > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
> > > -4
> > > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single
> > > management server on CentOS 6.5 with MySQL installed locally Created
> > > new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
> > > Updated Various Global Settings via API Created Domains and Accounts
> > > via API Deployed VMs for user account as Root and configured network
> > > Egress rules via API Deployed VM as root via UI Live Migrated VMs
> > > between Hosts Offline Migrated (VM stopped) Root Volume between Pri
> > > Storage via UI - cloudstack service crashed! (Install is running
> > > inside VirtualBox and Management VM is also NFS Server so added more
> > > RAM and tried again) - repeated test after a manual clean up and it
> > > was successful Live Migrated (VM running) Root Volume between Pri
> > > Storage via UI Disabled / Re-enabled Host Adding / removing NICs and
> > > changing default etc via UI Deployed new VPC, with two tiers, added
> > > VM to each tier, setup ACLs etc via API
> > >
> > >
> > > Then I did an upgrade test of a 4.3.1 system using the latest system
> > > VM template from Jenkins (this system was originally built on 4.3.0
> > > and upgraded to 4.3.1, before being upgraded to 4.4.1) New System VM
> > > template installed OK
> > >
> > > The steps

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Pierre-Luc Dion]

Had the same issue when upgraded from 4.3.0  but did not when upgraded from
4.2.1.




*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

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


On Wed, Oct 1, 2014 at 11:21 AM, Geoff Higginbottom <
geoff.higginbot...@shapeblue.com> wrote:

> The Cluster Details UI issue is only present on my upgraded system, a
> clean install of 4.4.1 correctly shows the value.
>
> Need someone else who upgraded to also check
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com]
> Sent: 01 October 2014 16:16
> To: dev@cloudstack.apache.org; Sebastien Goasguen
> Subject: RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> Great, glad to hear it was an easy fix.
>
> Now however I have found another problem.  In the UI if I go to
> Infrastructure/Clusters/cluster1/and then choose the settings tab, I get an
> error and no information is displayed.
>
> Can others please check this to see if it is a unique problem to me or a
> common issue.  This is on my upgraded install, I'll the check the clean
> install in a few minutes once its power up.
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 15:29
> To: dev@cloudstack.apache.org; Sebastien Goasguen
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> ok, fixed it ,  /latest is pointing on the master branch for the RN git
> repo. so it's not reflecting the "latest" version of our product.
> I've disable the /latest version so URL  will default to 4.4.0 RN  for the
> moment, and the 4.4.1 RN is the correct one.
>
> Seb, do you see a problem disabling  master and latest build in RTD ?
>
> make more sense?
>
> PL
>
> On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
> > Hi Pierre-Luc,
> >
> > Nope, I was deffinately looking at 4.4.1 release notes, complete with
> > sections titled 'Issues fixed in 4.4.1' etc
> >
> >
> > http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgr
> > ade-4.3.html
> >
> > I would include a screen shot of the page but it will get stripped
> > from the e-mail
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > Sent: 01 October 2014 14:49
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > 4.4-RC20140924T2100
> >
> > Geoff,
> >
> > Could it be possible you've followed 4.4.0 upgrade path ? because we
> > don't have to perform any MySQL query when upgrading to 4.4.1,
> > otherwise the RN is not correct.
> > the current RN for 4.4.1 is:
> >
> > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en
> > /4.4.1/  (not /latest yet as it's not release yet)
> >
> > for the vhd-utils, I wasn't sure if it was making sense to keep it on
> > all upgrade path, thanks for the comment, make sense to remove if from
> > upgrade 4.3.x and probably 4.2.x as it should already be in place.
> >
> >
> > PL
> >
> >
> >
> >
> > On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> > geoff.higginbot...@shapeblue.com> wrote:
> >
> > > +0  only because of the issues in the release notes, a clean install
> > > +and
> > > an upgrade from 4.3.1 went OK, but only because I know how to do it,
> > > it would not work if I followed the release notes.  The Router
> > > Upgrade notification elements in the UI, introduced in 4.3 are also
> > > broken (this should possibly be a -1 as it could result in installs
> > > running with the wrong version of the VRs without realising)
> > >
> > > Notes:
> > >
> > > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System
> > > VM Template from
> > > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6
> > > 4/
> > > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
> > > -4
> > > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single
> > > management server on CentOS 6.5 with MySQL installed locally Created
> > > new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
> > > Updated Various Global Settings via API Created Domains and Accounts
> > > via API Deployed VMs for user account as Root and configured network
> > > Egress rules via API Deployed VM as root via UI Live Migrated VMs
> > > between Hosts Offline Migrated (VM stopped) Root Volume bet

RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Geoff Higginbottom]

This has to be a blocker then as a system which is upgraded from 4.2 or earlier 
will lose its Overprovisioning settings as they get reset to 1, and you have to 
go the Cluster Settings to reset them back to the value they were pre-upgrade, 
if you can't you could end up with the situation where Customer VMs will not 
restart.

The only alternative is to force users to upgrade to 4.3.1, reset the 
overprovisioning on the Cluster, then upgrade to 4.4.1, but even then they 
cannot make any changes via the UI (assume API will work)

Changing my vote -1 until this is resolved

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
Sent: 01 October 2014 16:20
To: dev@cloudstack.apache.org
Cc: Sebastien Goasguen
Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 
4.4-RC20140924T2100

yep, this is the JIRA: https://issues.apache.org/jira/browse/CLOUDSTACK-7219

unfortunately it hasn't been fixed in 4.4.1 :-(


PL

On Wed, Oct 1, 2014 at 11:16 AM, Geoff Higginbottom < 
geoff.higginbot...@shapeblue.com> wrote:

> Great, glad to hear it was an easy fix.
>
> Now however I have found another problem.  In the UI if I go to
> Infrastructure/Clusters/cluster1/and then choose the settings tab, I
> get an error and no information is displayed.
>
> Can others please check this to see if it is a unique problem to me or
> a common issue.  This is on my upgraded install, I'll the check the
> clean install in a few minutes once its power up.
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 15:29
> To: dev@cloudstack.apache.org; Sebastien Goasguen
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> ok, fixed it ,  /latest is pointing on the master branch for the RN
> git repo. so it's not reflecting the "latest" version of our product.
> I've disable the /latest version so URL  will default to 4.4.0 RN  for
> the moment, and the 4.4.1 RN is the correct one.
>
> Seb, do you see a problem disabling  master and latest build in RTD ?
>
> make more sense?
>
> PL
>
> On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
> > Hi Pierre-Luc,
> >
> > Nope, I was deffinately looking at 4.4.1 release notes, complete
> > with sections titled 'Issues fixed in 4.4.1' etc
> >
> >
> > http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/up
> > gr
> > ade-4.3.html
> >
> > I would include a screen shot of the page but it will get stripped
> > from the e-mail
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > Sent: 01 October 2014 14:49
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > 4.4-RC20140924T2100
> >
> > Geoff,
> >
> > Could it be possible you've followed 4.4.0 upgrade path ? because we
> > don't have to perform any MySQL query when upgrading to 4.4.1,
> > otherwise the RN is not correct.
> > the current RN for 4.4.1 is:
> >
> > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/
> > en /4.4.1/  (not /latest yet as it's not release yet)
> >
> > for the vhd-utils, I wasn't sure if it was making sense to keep it
> > on all upgrade path, thanks for the comment, make sense to remove if
> > from upgrade 4.3.x and probably 4.2.x as it should already be in place.
> >
> >
> > PL
> >
> >
> >
> >
> > On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> > geoff.higginbot...@shapeblue.com> wrote:
> >
> > > +0  only because of the issues in the release notes, a clean
> > > +install and
> > > an upgrade from 4.3.1 went OK, but only because I know how to do
> > > it, it would not work if I followed the release notes.  The Router
> > > Upgrade notification elements in the UI, introduced in 4.3 are
> > > also broken (this should possibly be a -1 as it could result in
> > > installs running with the wrong version of the VRs without
> > > realising)
> > >
> > > Notes:
> > >
> > > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System
> > > VM Template from
> > > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemv
> > > m6
> > > 4/
> > > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64templa
> > > te
> > > -4
> > > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single
> > > management server on CentOS 6.5 with MySQL installed locally
> > > Created new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage
> > > all via API Updated Various Global Settings via API Created
> > > Domains and Accounts via API De

Re: test day reminder

[Marcus]

I'd be curious to know if it works by re-adding the host.  I remember
running into situations like this in the past, where the mgmt server was
either not fully up or rejecting agents for some reason.

On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander  wrote:

>
>
> On 09/30/2014 09:26 AM, Daan Hoogland wrote:
> > H all,
> >
> > As you might remember, we agreed on a test day for the master branch on
> > Wednesday the 1st October, during our last meeting in Schihol-Rijk with
> > some folks. Please feel invited to test master so that we can report to
> our
> > RM for 4.5 for the current state and he can have a short and quick
> journey
> > to releasing.
> >
>
> I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and
> that worked, but my KVM agent couldn't connect anymore afterwards:
>
> 2014-10-01 14:59:08,789 INFO  [utils.nio.NioClient]
> (Agent-Selector:null) Connecting to cloudstack.:8250
> 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection]
> (Agent-Selector:null) Unable to initialize the threads.
> java.io.IOException: Connection closed with -1 on reading size.
> at com.cloud.utils.nio.Link.doHandshake(Link.java:509)
> at com.cloud.utils.nio.NioClient.init(NioClient.java:78)
> at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
> at java.lang.Thread.run(Thread.java:744)
>
> Any ideas? When I try to telnet to 8250 the connection is closed
> immediately by the mgmt server. Nothing in the logs.
>
> So this is currently preventing me from testing the KVM agents.
>
> Wido
>
>
> > ​optimistically yours,​
> >
>

RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Erik Weber]

Has been like that since 4.4.0

Erik
1. okt. 2014 17:16 skrev "Geoff Higginbottom" <
geoff.higginbot...@shapeblue.com> følgende:

> Great, glad to hear it was an easy fix.
>
> Now however I have found another problem.  In the UI if I go to
> Infrastructure/Clusters/cluster1/and then choose the settings tab, I get an
> error and no information is displayed.
>
> Can others please check this to see if it is a unique problem to me or a
> common issue.  This is on my upgraded install, I'll the check the clean
> install in a few minutes once its power up.
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 15:29
> To: dev@cloudstack.apache.org; Sebastien Goasguen
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> ok, fixed it ,  /latest is pointing on the master branch for the RN git
> repo. so it's not reflecting the "latest" version of our product.
> I've disable the /latest version so URL  will default to 4.4.0 RN  for the
> moment, and the 4.4.1 RN is the correct one.
>
> Seb, do you see a problem disabling  master and latest build in RTD ?
>
> make more sense?
>
> PL
>
> On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
> > Hi Pierre-Luc,
> >
> > Nope, I was deffinately looking at 4.4.1 release notes, complete with
> > sections titled 'Issues fixed in 4.4.1' etc
> >
> >
> > http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgr
> > ade-4.3.html
> >
> > I would include a screen shot of the page but it will get stripped
> > from the e-mail
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > Sent: 01 October 2014 14:49
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > 4.4-RC20140924T2100
> >
> > Geoff,
> >
> > Could it be possible you've followed 4.4.0 upgrade path ? because we
> > don't have to perform any MySQL query when upgrading to 4.4.1,
> > otherwise the RN is not correct.
> > the current RN for 4.4.1 is:
> >
> > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en
> > /4.4.1/  (not /latest yet as it's not release yet)
> >
> > for the vhd-utils, I wasn't sure if it was making sense to keep it on
> > all upgrade path, thanks for the comment, make sense to remove if from
> > upgrade 4.3.x and probably 4.2.x as it should already be in place.
> >
> >
> > PL
> >
> >
> >
> >
> > On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> > geoff.higginbot...@shapeblue.com> wrote:
> >
> > > +0  only because of the issues in the release notes, a clean install
> > > +and
> > > an upgrade from 4.3.1 went OK, but only because I know how to do it,
> > > it would not work if I followed the release notes.  The Router
> > > Upgrade notification elements in the UI, introduced in 4.3 are also
> > > broken (this should possibly be a -1 as it could result in installs
> > > running with the wrong version of the VRs without realising)
> > >
> > > Notes:
> > >
> > > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System
> > > VM Template from
> > > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6
> > > 4/
> > > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
> > > -4
> > > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single
> > > management server on CentOS 6.5 with MySQL installed locally Created
> > > new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
> > > Updated Various Global Settings via API Created Domains and Accounts
> > > via API Deployed VMs for user account as Root and configured network
> > > Egress rules via API Deployed VM as root via UI Live Migrated VMs
> > > between Hosts Offline Migrated (VM stopped) Root Volume between Pri
> > > Storage via UI - cloudstack service crashed! (Install is running
> > > inside VirtualBox and Management VM is also NFS Server so added more
> > > RAM and tried again) - repeated test after a manual clean up and it
> > > was successful Live Migrated (VM running) Root Volume between Pri
> > > Storage via UI Disabled / Re-enabled Host Adding / removing NICs and
> > > changing default etc via UI Deployed new VPC, with two tiers, added
> > > VM to each tier, setup ACLs etc via API
> > >
> > >
> > > Then I did an upgrade test of a 4.3.1 system using the latest system
> > > VM template from Jenkins (this system was originally built on 4.3.0
> > > and upgraded to 4.3.1, before being upgraded to 4.4.1) New System VM
> > > template installed OK
> > >
> > > The steps in the release notes about downloading vhd-utils for
> > > XenServer are misleading.  If you blin

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Pierre-Luc Dion]

>From what I understand from this issue is UI only, which is why it wasn't a
blocker before. anyway, you have a valid point :-(

now the question would be: who could fix this ?

Cluster settings change you are refering are theses [1] ,  right  ?

[1]
http://cloudstack-release-notes.readthedocs.org/en/4.4.1/upgrade/upgrade_notes.html#settings-changes


On Wed, Oct 1, 2014 at 11:33 AM, Erik Weber  wrote:

> Has been like that since 4.4.0
>
> Erik
> 1. okt. 2014 17:16 skrev "Geoff Higginbottom" <
> geoff.higginbot...@shapeblue.com> følgende:
>
> > Great, glad to hear it was an easy fix.
> >
> > Now however I have found another problem.  In the UI if I go to
> > Infrastructure/Clusters/cluster1/and then choose the settings tab, I get
> an
> > error and no information is displayed.
> >
> > Can others please check this to see if it is a unique problem to me or a
> > common issue.  This is on my upgraded install, I'll the check the clean
> > install in a few minutes once its power up.
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > Sent: 01 October 2014 15:29
> > To: dev@cloudstack.apache.org; Sebastien Goasguen
> > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > 4.4-RC20140924T2100
> >
> > ok, fixed it ,  /latest is pointing on the master branch for the RN git
> > repo. so it's not reflecting the "latest" version of our product.
> > I've disable the /latest version so URL  will default to 4.4.0 RN  for
> the
> > moment, and the 4.4.1 RN is the correct one.
> >
> > Seb, do you see a problem disabling  master and latest build in RTD ?
> >
> > make more sense?
> >
> > PL
> >
> > On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom <
> > geoff.higginbot...@shapeblue.com> wrote:
> >
> > > Hi Pierre-Luc,
> > >
> > > Nope, I was deffinately looking at 4.4.1 release notes, complete with
> > > sections titled 'Issues fixed in 4.4.1' etc
> > >
> > >
> > > http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgr
> > > ade-4.3.html
> > >
> > > I would include a screen shot of the page but it will get stripped
> > > from the e-mail
> > >
> > > Regards
> > >
> > > Geoff Higginbottom
> > >
> > > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> > >
> > > geoff.higginbot...@shapeblue.com
> > >
> > > -Original Message-
> > > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > > Sent: 01 October 2014 14:49
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > > 4.4-RC20140924T2100
> > >
> > > Geoff,
> > >
> > > Could it be possible you've followed 4.4.0 upgrade path ? because we
> > > don't have to perform any MySQL query when upgrading to 4.4.1,
> > > otherwise the RN is not correct.
> > > the current RN for 4.4.1 is:
> > >
> > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en
> > > /4.4.1/  (not /latest yet as it's not release yet)
> > >
> > > for the vhd-utils, I wasn't sure if it was making sense to keep it on
> > > all upgrade path, thanks for the comment, make sense to remove if from
> > > upgrade 4.3.x and probably 4.2.x as it should already be in place.
> > >
> > >
> > > PL
> > >
> > >
> > >
> > >
> > > On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> > > geoff.higginbot...@shapeblue.com> wrote:
> > >
> > > > +0  only because of the issues in the release notes, a clean install
> > > > +and
> > > > an upgrade from 4.3.1 went OK, but only because I know how to do it,
> > > > it would not work if I followed the release notes.  The Router
> > > > Upgrade notification elements in the UI, introduced in 4.3 are also
> > > > broken (this should possibly be a -1 as it could result in installs
> > > > running with the wrong version of the VRs without realising)
> > > >
> > > > Notes:
> > > >
> > > > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System
> > > > VM Template from
> > > > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6
> > > > 4/
> > > > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
> > > > -4
> > > > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single
> > > > management server on CentOS 6.5 with MySQL installed locally Created
> > > > new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API
> > > > Updated Various Global Settings via API Created Domains and Accounts
> > > > via API Deployed VMs for user account as Root and configured network
> > > > Egress rules via API Deployed VM as root via UI Live Migrated VMs
> > > > between Hosts Offline Migrated (VM stopped) Root Volume between Pri
> > > > Storage via UI - cloudstack service crashed! (Install is running
> > > > inside VirtualBox and Management VM is also NFS Server so added more
> > > > RAM and tried again) - repeated test after a manual clean up and it

RE: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Stephen Turner]

Can someone who's seeing this confirm whether it's a UI issue, or whether it's 
the same through the API? The ticket CLOUDSTACK-7219 has Component=Management 
Server, not UI, and (without having seen it myself) it feels more like a 
server-side issue to me.

-- 
Stephen Turner


-Original Message-
From: Pierre-Luc Dion [mailto:pd...@cloudops.com] 
Sent: 01 October 2014 16:47
To: dev@cloudstack.apache.org
Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 
4.4-RC20140924T2100

From what I understand from this issue is UI only, which is why it wasn't a 
blocker before. anyway, you have a valid point :-(

now the question would be: who could fix this ?

Cluster settings change you are refering are theses [1] ,  right  ?

[1]
http://cloudstack-release-notes.readthedocs.org/en/4.4.1/upgrade/upgrade_notes.html#settings-changes


On Wed, Oct 1, 2014 at 11:33 AM, Erik Weber  wrote:

> Has been like that since 4.4.0
>
> Erik
> 1. okt. 2014 17:16 skrev "Geoff Higginbottom" < 
> geoff.higginbot...@shapeblue.com> følgende:
>
> > Great, glad to hear it was an easy fix.
> >
> > Now however I have found another problem.  In the UI if I go to 
> > Infrastructure/Clusters/cluster1/and then choose the settings tab, I 
> > get
> an
> > error and no information is displayed.
> >
> > Can others please check this to see if it is a unique problem to me 
> > or a common issue.  This is on my upgraded install, I'll the check 
> > the clean install in a few minutes once its power up.
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > Sent: 01 October 2014 15:29
> > To: dev@cloudstack.apache.org; Sebastien Goasguen
> > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > 4.4-RC20140924T2100
> >
> > ok, fixed it ,  /latest is pointing on the master branch for the RN 
> > git repo. so it's not reflecting the "latest" version of our product.
> > I've disable the /latest version so URL  will default to 4.4.0 RN  
> > for
> the
> > moment, and the 4.4.1 RN is the correct one.
> >
> > Seb, do you see a problem disabling  master and latest build in RTD ?
> >
> > make more sense?
> >
> > PL
> >
> > On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom < 
> > geoff.higginbot...@shapeblue.com> wrote:
> >
> > > Hi Pierre-Luc,
> > >
> > > Nope, I was deffinately looking at 4.4.1 release notes, complete 
> > > with sections titled 'Issues fixed in 4.4.1' etc
> > >
> > >
> > > http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/
> > > upgr
> > > ade-4.3.html
> > >
> > > I would include a screen shot of the page but it will get stripped 
> > > from the e-mail
> > >
> > > Regards
> > >
> > > Geoff Higginbottom
> > >
> > > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> > >
> > > geoff.higginbot...@shapeblue.com
> > >
> > > -Original Message-
> > > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > > Sent: 01 October 2014 14:49
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > > 4.4-RC20140924T2100
> > >
> > > Geoff,
> > >
> > > Could it be possible you've followed 4.4.0 upgrade path ? because 
> > > we don't have to perform any MySQL query when upgrading to 4.4.1, 
> > > otherwise the RN is not correct.
> > > the current RN for 4.4.1 is:
> > >
> > > http://docs.cloudstack.apache.org/projects/cloudstack-release-note
> > > s/en /4.4.1/  (not /latest yet as it's not release yet)
> > >
> > > for the vhd-utils, I wasn't sure if it was making sense to keep it 
> > > on all upgrade path, thanks for the comment, make sense to remove 
> > > if from upgrade 4.3.x and probably 4.2.x as it should already be in place.
> > >
> > >
> > > PL
> > >
> > >
> > >
> > >
> > > On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom < 
> > > geoff.higginbot...@shapeblue.com> wrote:
> > >
> > > > +0  only because of the issues in the release notes, a clean 
> > > > +install and
> > > > an upgrade from 4.3.1 went OK, but only because I know how to do 
> > > > it, it would not work if I followed the release notes.  The 
> > > > Router Upgrade notification elements in the UI, introduced in 
> > > > 4.3 are also broken (this should possibly be a -1 as it could 
> > > > result in installs running with the wrong version of the VRs 
> > > > without realising)
> > > >
> > > > Notes:
> > > >
> > > > 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 
> > > > System VM Template from
> > > > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-syste
> > > > mvm6
> > > > 4/
> > > > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64temp
> > > > late
> > > > -4
> > > > .4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single 
> > > > management server on CentOS 6.5 with MySQL installed locally 
> > > > Created new Zone, POD, Cluster, Sec 

Re: test day reminder

[Daan Hoogland]

I have been looking at using my collegues integration work for the master
branch. So far the packaging part is holding my back as it uses 'SNAPSHOT'
in the build and does not allow for patch levels (in package.sh) I am
looking at a solution.

what I am thinking of is making rpms like

cloudstack.el6_64.rpm

this seems quite verbose but it gives us space to do continuous integration
on the artifact. I am sure a scheme like this can be deviced for .deb
packages as well.

thoughts?

The actual testing, for as little far as I got to do, did not yield issues
yet.

Daan

On Wed, Oct 1, 2014 at 5:28 PM, Marcus  wrote:

> I'd be curious to know if it works by re-adding the host.  I remember
> running into situations like this in the past, where the mgmt server was
> either not fully up or rejecting agents for some reason.
>
> On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander  wrote:
>
> >
> >
> > On 09/30/2014 09:26 AM, Daan Hoogland wrote:
> > > H all,
> > >
> > > As you might remember, we agreed on a test day for the master branch on
> > > Wednesday the 1st October, during our last meeting in Schihol-Rijk with
> > > some folks. Please feel invited to test master so that we can report to
> > our
> > > RM for 4.5 for the current state and he can have a short and quick
> > journey
> > > to releasing.
> > >
> >
> > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and
> > that worked, but my KVM agent couldn't connect anymore afterwards:
> >
> > 2014-10-01 14:59:08,789 INFO  [utils.nio.NioClient]
> > (Agent-Selector:null) Connecting to cloudstack.:8250
> > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection]
> > (Agent-Selector:null) Unable to initialize the threads.
> > java.io.IOException: Connection closed with -1 on reading size.
> > at com.cloud.utils.nio.Link.doHandshake(Link.java:509)
> > at com.cloud.utils.nio.NioClient.init(NioClient.java:78)
> > at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
> > at java.lang.Thread.run(Thread.java:744)
> >
> > Any ideas? When I try to telnet to 8250 the connection is closed
> > immediately by the mgmt server. Nothing in the logs.
> >
> > So this is currently preventing me from testing the KVM agents.
> >
> > Wido
> >
> >
> > > ​optimistically yours,​
> > >
> >
>



-- 
Daan

Re: Unable to upload SSL certificate for realhostip replacement

[Amogh Vasekar]

Hi,

For 4.2 you may want to refer here :
http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-certif
icate-chains-in-cloudstack.html

4.3 had a missing commit, due to which the global config
consoleproxy.url.domain had to be set to "mydomain.com", instead of
"*.mydomain.com". This has been fixed in 4.3.1

Apologies for the inconvenience.

Amogh

On 10/1/14 8:16 AM, "Rohit Yadav"  wrote:

>Just to update on the certificate upload issue with 4.2:
>
>I’m able to download and add new volumes/templates/isos and the link
>provided has a valid https url with the same certificate that I uploaded
>though when I try to access the console I get SSL cert error and I see
>that it’s still returning the old *.realhostip.com certificate. I’ve
>tried to delete old CPVMs and I see the same issue coming up again.
>
>
>On 01-Oct-2014, at 4:55 pm, Rohit Yadav  wrote:
>> Hi,
>>
>> I’ve fixed cloudmonkey to url encode parameters so now you can use
>>cloudmonkey to upload custom certificate but only in non-interactive
>>mode on shell (bash/zsh). You’ll have to install cloudmonkey from source
>>for now since the fix is only on master.
>>
>> Something like:
>> $ cloudmonkey upload customcertificate id=xx domainsuffix=yy name=zzz
>>certificate=‘asdf
>> asdfasdf
>> asdfasdf
>> asdf---'
>>
>> I’ve some issues to report while replacing certificates to get rid of
>>realhostip, this is specific for Xen could apply for other hypervisors
>>as well:
>>
>> - In case of 4.2, I see in the database that seq is 0 for the root
>>certificate for the realhostip.com domain. I uploaded certificates in
>>order (root, then intermediate and finally SSL cert from UI), and I see
>>the old certificate is still there. after CPVM/SSVM restarts and are in
>>UP state I still get SSL errors and I see that systemvm.iso is not
>>getting patched. How to fix this? Or force systemvm.iso patching?
>>
>> - In case of 4.3.0 and above, I see the same issue. I’m confused
>>whether to use *. wildcard in global setting or not.
>>
>> On 27-Sep-2014, at 9:32 pm, Amogh Vasekar 
>>wrote:
>>> Hi,
>>>
>>> For the encoding, in your case it was the space character causing the
>>> issue - it should be replaced by %20. The correct encoding would be
>>> (hoping mail clients don't screw up the blob):
>>> 
>>>-BEGIN%20CERTIFICATE-%0AMIIDfTCCAuagAwIBAgIDErvmMA0GCSqGSIb3DQEB
>>>BQU
>>> 
>>>AME4xCzAJBgNVBAYTAlVT%0AMRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4
>>>IFN
>>> 
>>>lY3VyZSBDZXJ0%0AaWZpY2F0ZSBBdXRob3JpdHkwHhcNMDIwNTIxMDQwMDAwWhcNMTgwODIx
>>>MDQ
>>> 
>>>wMDAw%0AWjBCMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNR2VvVHJ1c3QgSW5jLjEbMBkGA1UE
>>>%0A
>>> 
>>>AxMSR2VvVHJ1c3QgR2xvYmFsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB%0ACgKCA
>>>QEA
>>> 
>>>2swYYzD99BcjGlZ%2BW988bDjkcbd4kdS8odhM%2BKhDtgPpTSEHCIjaWC9m%0AOSm9BXiLn
>>>Tjo
>>> 
>>>BbdqfnGk5sRgprDvgOSJKA%2BeJdbtg%2FOtppHHmMlCGDUUna2YRpIu%0AT8rxh0PBFpVXL
>>>VDv
>>> 
>>>iS2Aelet8u5fa9IAjbkU%2BBQVNdnARqN7csiRv8lVK83Qlz6c%0AJmTM386DGXHKTubU1Xu
>>>pGc
>>> 
>>>1V3sjs0l44U%2BVcT4wt%2FlAjNvxm5suOpDkZALeVAjmR%0ACw7%2BOC7RHQWa9k0%2Bbw8
>>>HHa
>>> 
>>>8sHo9gOeL6NlMTOdReJivbPagUvTLrGAMoUgRx5asz%0APeE4uwc2hGKceeoWMPRfwCvocWv
>>>k%2
>>> 
>>>BQIDAQABo4HwMIHtMB8GA1UdIwQYMBaAFEjm%0AaPkr0rKV10fYIyAQTzOYkJ%2FUMB0GA1U
>>>dDg
>>> 
>>>QWBBTAephojYn7qwVkDBF9qn1luMrM%0ATjAPBgNVHRMBAf8EBTADAQH%2FMA4GA1UdDwEB%
>>>2Fw
>>> 
>>>QEAwIBBjA6BgNVHR8EMzAxMC%2Bg%0ALaArhilodHRwOi8vY3JsLmdlb3RydXN0LmNvbS9jc
>>>mxz
>>> 
>>>L3NlY3VyZWNhLmNybDBO%0ABgNVHSAERzBFMEMGBFUdIAAwOzA5BggrBgEFBQcCARYtaHR0c
>>>HM6
>>> 
>>>Ly93d3cuZ2Vv%0AdHJ1c3QuY29tL3Jlc291cmNlcy9yZXBvc2l0b3J5MA0GCSqGSIb3DQEBB
>>>QUA
>>> 
>>>A4GB%0AAHbhEm5OSxYShjAGsoEIz%2FAIx8dxfmbuwu3UOx%2F%2F8PDITtZDOLC5MH0Y0FW
>>>Dom
>>> 
>>>rL%0ANhGc6Ehmo21%2FuBPUR%2F6LWlxz%2FK7ZGzIZOKuXNBSqltLroxwUCEm2u%2BWR74M
>>>26x
>>> 
>>>1W%0Ab8ravHNjkOR%2Fez4iyz0H7V84dJzjA1BOoa%2BY7mHyhD8S%0A-END%20CERTI
>>>FIC
>>> ATE-
>>>
>>> As for the global parameter, you can set it to something like a few
>>> seconds and reset to original value when the URLs have been expired.
>>>
>>> Thanks
>>> Amogh
>>>
>>>
>>> On 9/27/14 10:53 AM, "Indra Pramana"  wrote:
>>>
 Hi Wido,

 I have changed the value of secstorage.ssl.cert.domain and restart
 management server, before I start uploading all the certificates.

 I found this article, which might be related to the problem:

 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Troubleshooting+
-+u
 ploading+custom+domain+certificate+instead+of+using+realhostip.com

 

 *Specific Issues seen*

 1. Download urls point to the old domain.
1. Reduce the expiration duration of the urls by changing global
config extract.url.expiration.interval
2. And change the frequency for cleanup thread
through extract.url.cleanup.interval restart MS.
3. Wait for the cleanup thread duration and try downloading again.
See whether the url is deleted.
4. DB tables to check (don¹t reco

Re: Unable to upload SSL certificate for realhostip replacement

[Rohit Yadav]

Hi Amogh,

I’ve a different issue, CPVM is opening the console but the HTTP service is 
returning old *.realhostip.com certificate.

I debugged CPVM agent to find that it’s not picking up the keystore sent from 
Management server. This issue is like: 
https://issues.apache.org/jira/browse/CLOUDSTACK-3438

In the logs (from CPVM), I’m only seeing "Initializing SSL from built-in 
default certificate”. Reading source from ConsoleProxySecureServerFactoryImpl, 
this means the agent is starting but is not getting any 
StartConsoleProxyAgentHttpHandlerCommand with new KeyStore data. I’ve tested 
this only for 4.2, Paul suggests something similar for 4.3 as well.

I’ve one root certificate (id=1), two intermediate certificate (id=2, id=3) and 
a wildcard domain cert+key. I uploaded them one by one as per the docs and also 
following Chip’s blog. By doing so, the SSVM keys got updated and by 
downloading an ISO I see the https url it gave returned correct SSL certificate 
which means the chain of certificates etc. worked.

In case of CPVM, accessing console in browser led to SSL error. Do you may any 
suggestions on how to get this fixed? If I remove CPVMs, I see it’s still using 
old systemvm.iso and though docs/wiki recommend systemvm.iso will get patched, 
it does not actually.

On 01-Oct-2014, at 6:32 pm, Amogh Vasekar  wrote:
> Hi,
>
> For 4.2 you may want to refer here :
> http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-certif
> icate-chains-in-cloudstack.html
>
> 4.3 had a missing commit, due to which the global config
> consoleproxy.url.domain had to be set to "mydomain.com", instead of
> "*.mydomain.com". This has been fixed in 4.3.1
>
> Apologies for the inconvenience.
>
> Amogh
>
> On 10/1/14 8:16 AM, "Rohit Yadav"  wrote:
>
>> Just to update on the certificate upload issue with 4.2:
>>
>> I’m able to download and add new volumes/templates/isos and the link
>> provided has a valid https url with the same certificate that I uploaded
>> though when I try to access the console I get SSL cert error and I see
>> that it’s still returning the old *.realhostip.com certificate. I’ve
>> tried to delete old CPVMs and I see the same issue coming up again.
>>
>>
>> On 01-Oct-2014, at 4:55 pm, Rohit Yadav  wrote:
>>> Hi,
>>>
>>> I’ve fixed cloudmonkey to url encode parameters so now you can use
>>> cloudmonkey to upload custom certificate but only in non-interactive
>>> mode on shell (bash/zsh). You’ll have to install cloudmonkey from source
>>> for now since the fix is only on master.
>>>
>>> Something like:
>>> $ cloudmonkey upload customcertificate id=xx domainsuffix=yy name=zzz
>>> certificate=‘asdf
>>> asdfasdf
>>> asdfasdf
>>> asdf---'
>>>
>>> I’ve some issues to report while replacing certificates to get rid of
>>> realhostip, this is specific for Xen could apply for other hypervisors
>>> as well:
>>>
>>> - In case of 4.2, I see in the database that seq is 0 for the root
>>> certificate for the realhostip.com domain. I uploaded certificates in
>>> order (root, then intermediate and finally SSL cert from UI), and I see
>>> the old certificate is still there. after CPVM/SSVM restarts and are in
>>> UP state I still get SSL errors and I see that systemvm.iso is not
>>> getting patched. How to fix this? Or force systemvm.iso patching?
>>>
>>> - In case of 4.3.0 and above, I see the same issue. I’m confused
>>> whether to use *. wildcard in global setting or not.
>>>
>>> On 27-Sep-2014, at 9:32 pm, Amogh Vasekar 
>>> wrote:
 Hi,

 For the encoding, in your case it was the space character causing the
 issue - it should be replaced by %20. The correct encoding would be
 (hoping mail clients don't screw up the blob):

 -BEGIN%20CERTIFICATE-%0AMIIDfTCCAuagAwIBAgIDErvmMA0GCSqGSIb3DQEB
 BQU

 AME4xCzAJBgNVBAYTAlVT%0AMRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4
 IFN

 lY3VyZSBDZXJ0%0AaWZpY2F0ZSBBdXRob3JpdHkwHhcNMDIwNTIxMDQwMDAwWhcNMTgwODIx
 MDQ

 wMDAw%0AWjBCMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNR2VvVHJ1c3QgSW5jLjEbMBkGA1UE
 %0A

 AxMSR2VvVHJ1c3QgR2xvYmFsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB%0ACgKCA
 QEA

 2swYYzD99BcjGlZ%2BW988bDjkcbd4kdS8odhM%2BKhDtgPpTSEHCIjaWC9m%0AOSm9BXiLn
 Tjo

 BbdqfnGk5sRgprDvgOSJKA%2BeJdbtg%2FOtppHHmMlCGDUUna2YRpIu%0AT8rxh0PBFpVXL
 VDv

 iS2Aelet8u5fa9IAjbkU%2BBQVNdnARqN7csiRv8lVK83Qlz6c%0AJmTM386DGXHKTubU1Xu
 pGc

 1V3sjs0l44U%2BVcT4wt%2FlAjNvxm5suOpDkZALeVAjmR%0ACw7%2BOC7RHQWa9k0%2Bbw8
 HHa

 8sHo9gOeL6NlMTOdReJivbPagUvTLrGAMoUgRx5asz%0APeE4uwc2hGKceeoWMPRfwCvocWv
 k%2

 BQIDAQABo4HwMIHtMB8GA1UdIwQYMBaAFEjm%0AaPkr0rKV10fYIyAQTzOYkJ%2FUMB0GA1U
 dDg

 QWBBTAephojYn7qwVkDBF9qn1luMrM%0ATjAPBgNVHRMBAf8EBTADAQH%2FMA4GA1UdDwEB%
 2Fw

 QEAwIBBjA6BgNVHR8EMzAxMC%2Bg%0ALaArhilodHRwOi8vY3JsLmdlb3RydXN0LmNvbS9jc
 mxz

 L3NlY3VyZWNhLmNybDBO%0ABgNVHSAERzBFMEMGBFUdIAAwOzA5BggrBgEFBQcCARYtaHR0c
 H

Re: [ANNOUNCE] New PMC Member: Ian Duffy

[Min Chen]

Congratulations, Ian.

-min

On 9/30/14 10:42 PM, "Prasanna Santhanam"  wrote:

>Congratulations Ian!
>
>On Tue, Sep 30, 2014 at 7:20 PM, Chip Childers 
>wrote:
>> The Project Management Committee (PMC) for Apache CloudStack has asked
>> Ian Duffy to join the PMC and we are pleased to announce that he has
>> accepted.
>>
>> Join me in congratulating Ian!
>>
>> -chip
>> On behalf of the Apache CloudStack PMC

Re: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

[Min Chen]

Congrats, Pierre-Luc!

-min

On 9/30/14 10:43 PM, "Prasanna Santhanam"  wrote:

>Congratulations Pierre-Luc!
>
>On Tue, Sep 30, 2014 at 7:20 PM, Chip Childers 
>wrote:
>> The Project Management Committee (PMC) for Apache CloudStack has asked
>> Pierre-Luc Dion to join the PMC and we are pleased to announce that he
>> has accepted.
>>
>> Join me in congratulating Pierre-Luc!
>>
>> -chip
>> On behalf of the Apache CloudStack PMC

Re: Unable to upload SSL certificate for realhostip replacement

[Amogh Vasekar]

Hi,

Can you please paste the contents of the keystore table (minus the private
key of course)?

For SSVM, in 4.2, the certificate chain was not configured correctly and
it would only use the server certificate when configuring Apache. It did
not impact functionality though.
This is not true for CPVM, which would try to use the full chain.
It was fixed in 4.3, along with removing a double decoding of certificate
when uploaded through API. The double decoding issue would manifest as
non-server certificates to be saved incorrectly in the DB, and hence
wanted to take a look at the table's contents. Since CPVM uses the full
chain but not SSVM, I suspect this might be your issue.

For the systemvm.iso - did you rebuild the ISO from source?
It gets patched automatically in 4.3 for XS, but 4.2 had a versioning
issue due to which it didn't change automatically.
For KVM, the ISO gets patched when you reinstall the agent package.
For Vmware, one needs to remove the old ISO from secondary storage folder
(under /systemvm/ I think) so that the new one gets
applied.

HTH
Amogh

On 10/1/14 9:51 AM, "Rohit Yadav"  wrote:

>Hi Amogh,
>
>I’ve a different issue, CPVM is opening the console but the HTTP service
>is returning old *.realhostip.com certificate.
>
>I debugged CPVM agent to find that it’s not picking up the keystore sent
>from Management server. This issue is like:
>https://issues.apache.org/jira/browse/CLOUDSTACK-3438
>
>In the logs (from CPVM), I’m only seeing "Initializing SSL from built-in
>default certificate”. Reading source from
>ConsoleProxySecureServerFactoryImpl, this means the agent is starting but
>is not getting any StartConsoleProxyAgentHttpHandlerCommand with new
>KeyStore data. I’ve tested this only for 4.2, Paul suggests something
>similar for 4.3 as well.
>
>I’ve one root certificate (id=1), two intermediate certificate (id=2,
>id=3) and a wildcard domain cert+key. I uploaded them one by one as per
>the docs and also following Chip’s blog. By doing so, the SSVM keys got
>updated and by downloading an ISO I see the https url it gave returned
>correct SSL certificate which means the chain of certificates etc. worked.
>
>In case of CPVM, accessing console in browser led to SSL error. Do you
>may any suggestions on how to get this fixed? If I remove CPVMs, I see
>it’s still using old systemvm.iso and though docs/wiki recommend
>systemvm.iso will get patched, it does not actually.
>
>On 01-Oct-2014, at 6:32 pm, Amogh Vasekar 
>wrote:
>> Hi,
>>
>> For 4.2 you may want to refer here :
>> 
>>http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-cert
>>if
>> icate-chains-in-cloudstack.html
>>
>> 4.3 had a missing commit, due to which the global config
>> consoleproxy.url.domain had to be set to "mydomain.com", instead of
>> "*.mydomain.com". This has been fixed in 4.3.1
>>
>> Apologies for the inconvenience.
>>
>> Amogh
>>
>> On 10/1/14 8:16 AM, "Rohit Yadav"  wrote:
>>
>>> Just to update on the certificate upload issue with 4.2:
>>>
>>> I’m able to download and add new volumes/templates/isos and the link
>>> provided has a valid https url with the same certificate that I
>>>uploaded
>>> though when I try to access the console I get SSL cert error and I see
>>> that it’s still returning the old *.realhostip.com certificate. I’ve
>>> tried to delete old CPVMs and I see the same issue coming up again.
>>>
>>>
>>> On 01-Oct-2014, at 4:55 pm, Rohit Yadav 
>>>wrote:
 Hi,

 I’ve fixed cloudmonkey to url encode parameters so now you can use
 cloudmonkey to upload custom certificate but only in non-interactive
 mode on shell (bash/zsh). You’ll have to install cloudmonkey from
source
 for now since the fix is only on master.

 Something like:
 $ cloudmonkey upload customcertificate id=xx domainsuffix=yy name=zzz
 certificate=‘asdf
 asdfasdf
 asdfasdf
 asdf---'

 I’ve some issues to report while replacing certificates to get rid of
 realhostip, this is specific for Xen could apply for other hypervisors
 as well:

 - In case of 4.2, I see in the database that seq is 0 for the root
 certificate for the realhostip.com domain. I uploaded certificates in
 order (root, then intermediate and finally SSL cert from UI), and I
see
 the old certificate is still there. after CPVM/SSVM restarts and are
in
 UP state I still get SSL errors and I see that systemvm.iso is not
 getting patched. How to fix this? Or force systemvm.iso patching?

 - In case of 4.3.0 and above, I see the same issue. I’m confused
 whether to use *. wildcard in global setting or not.

 On 27-Sep-2014, at 9:32 pm, Amogh Vasekar 
 wrote:
> Hi,
>
> For the encoding, in your case it was the space character causing the
> issue - it should be replaced by %20. The correct encoding would be
> (hoping mail clients don't screw up the blob):
>
> 
>-BEGIN%20CERTIFICATE-%0AMIIDfTCCAua

Re: [ANNOUNCE] New PMC Member: Ian Duffy

[Nux!]

Congrats, Ian, good job! :)

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Chip Childers" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 30 September, 2014 14:50:42
> Subject: [ANNOUNCE] New PMC Member: Ian Duffy

> The Project Management Committee (PMC) for Apache CloudStack has asked
> Ian Duffy to join the PMC and we are pleased to announce that he has
> accepted.
> 
> Join me in congratulating Ian!
> 
> -chip
> On behalf of the Apache CloudStack PMC

Re: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

[Nux!]

Congrats, Pierre-Luc! :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Chip Childers" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 30 September, 2014 14:50:40
> Subject: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

> The Project Management Committee (PMC) for Apache CloudStack has asked
> Pierre-Luc Dion to join the PMC and we are pleased to announce that he
> has accepted.
> 
> Join me in congratulating Pierre-Luc!
> 
> -chip
> On behalf of the Apache CloudStack PMC

RE: Shellshock

[Demetrius Tsitrelis]

Interestingly this video shows attack against a perl script... 
https://www.youtube.com/watch?v=ArEOVHQu9nk

-Original Message-
From: Demetrius Tsitrelis [mailto:demetrius.tsitre...@citrix.com] 
Sent: Monday, September 29, 2014 6:13 PM
To: 
Subject: RE: Shellshock

http://systemvm-public-ip/cgi-bin/ipcalc is a perl script.

-Original Message-
From: Sheng Yang [mailto:sh...@yasker.org]
Sent: Monday, September 29, 2014 5:21 PM
To: 
Subject: Re: Shellshock

http://systemvm-public-ip/cgi-bin/ipcalc is NOT a bash script, so it's normal 
that it cannot be exploited.

--Sheng

On Fri, Sep 26, 2014 at 1:57 PM, Demetrius Tsitrelis < 
demetrius.tsitre...@citrix.com> wrote:

> Do you mean you tried setting the USER_AGENT like in 
> https://community.qualys.com/blogs/securitylabs/2014/09/25/qualysguard
> -remote-detection-for-bash-shellshock
> ?
>
>
> -Original Message-
> From: Ian Duffy [mailto:i...@ianduffy.ie]
> Sent: Friday, September 26, 2014 6:56 AM
> To: CloudStack Dev
> Subject: Re: Shellshock
>
> Tried this against the latest system vms built on Jenkins.
>
> Didn't get a successful exploited response. Tested against 
> http://systemvm
> - public-ip/cgi-bin/ipcalc
> On 25 Sep 2014 16:56, "Abhinandan Prateek"  wrote:
>
> >
> > After heart bleed we are Shell shocked
> > http://www.bbc.com/news/technology-29361794 !
> > It may not affect cloudstack directly as it is a vulnerability that 
> > affects bash, and allows the attacker to take control of the system 
> > running bash shell.
> >
> > -abhi
>

Re: [ANNOUNCE] New PMC Member: Pierre-Luc Dion

[Pierre-Luc Dion]

Thanks guys!


PL

On Wed, Oct 1, 2014 at 1:36 PM, Nux!  wrote:

> Congrats, Pierre-Luc! :)
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Chip Childers" 
> > To: dev@cloudstack.apache.org
> > Sent: Tuesday, 30 September, 2014 14:50:40
> > Subject: [ANNOUNCE] New PMC Member: Pierre-Luc Dion
>
> > The Project Management Committee (PMC) for Apache CloudStack has asked
> > Pierre-Luc Dion to join the PMC and we are pleased to announce that he
> > has accepted.
> >
> > Join me in congratulating Pierre-Luc!
> >
> > -chip
> > On behalf of the Apache CloudStack PMC
>

RE: Shellshock

[Demetrius Tsitrelis]

Actually, I am not sure.  Only the env.cgi script is loaded and, while the 
other scripts are in perl, there is nothing in the video which shows the source 
for the env.cgi script so it may not be perl.

-Original Message-
From: Demetrius Tsitrelis [mailto:demetrius.tsitre...@citrix.com] 
Sent: Wednesday, October 01, 2014 10:52 AM
To: 
Subject: RE: Shellshock

Interestingly this video shows attack against a perl script... 
https://www.youtube.com/watch?v=ArEOVHQu9nk

-Original Message-
From: Demetrius Tsitrelis [mailto:demetrius.tsitre...@citrix.com]
Sent: Monday, September 29, 2014 6:13 PM
To: 
Subject: RE: Shellshock

http://systemvm-public-ip/cgi-bin/ipcalc is a perl script.

-Original Message-
From: Sheng Yang [mailto:sh...@yasker.org]
Sent: Monday, September 29, 2014 5:21 PM
To: 
Subject: Re: Shellshock

http://systemvm-public-ip/cgi-bin/ipcalc is NOT a bash script, so it's normal 
that it cannot be exploited.

--Sheng

On Fri, Sep 26, 2014 at 1:57 PM, Demetrius Tsitrelis < 
demetrius.tsitre...@citrix.com> wrote:

> Do you mean you tried setting the USER_AGENT like in 
> https://community.qualys.com/blogs/securitylabs/2014/09/25/qualysguard
> -remote-detection-for-bash-shellshock
> ?
>
>
> -Original Message-
> From: Ian Duffy [mailto:i...@ianduffy.ie]
> Sent: Friday, September 26, 2014 6:56 AM
> To: CloudStack Dev
> Subject: Re: Shellshock
>
> Tried this against the latest system vms built on Jenkins.
>
> Didn't get a successful exploited response. Tested against 
> http://systemvm
> - public-ip/cgi-bin/ipcalc
> On 25 Sep 2014 16:56, "Abhinandan Prateek"  wrote:
>
> >
> > After heart bleed we are Shell shocked
> > http://www.bbc.com/news/technology-29361794 !
> > It may not affect cloudstack directly as it is a vulnerability that 
> > affects bash, and allows the attacker to take control of the system 
> > running bash shell.
> >
> > -abhi
>

RE: Unable to upload SSL certificate for realhostip replacement

[Paul Angus]

I'm using 4.3.0 with VMware, /usr/share/cloudstack-common/vms/systemvm.iso 
isn't being updated so removing /systemvm/ 
systemvm-4.3.0.iso just means the original iso get copied back.



Regards

Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Amogh Vasekar [mailto:amogh.vase...@citrix.com]
Sent: 01 October 2014 18:15
To: us...@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: Unable to upload SSL certificate for realhostip replacement

Hi,

Can you please paste the contents of the keystore table (minus the private key 
of course)?

For SSVM, in 4.2, the certificate chain was not configured correctly and it 
would only use the server certificate when configuring Apache. It did not 
impact functionality though.
This is not true for CPVM, which would try to use the full chain.
It was fixed in 4.3, along with removing a double decoding of certificate when 
uploaded through API. The double decoding issue would manifest as non-server 
certificates to be saved incorrectly in the DB, and hence wanted to take a look 
at the table's contents. Since CPVM uses the full chain but not SSVM, I suspect 
this might be your issue.

For the systemvm.iso - did you rebuild the ISO from source?
It gets patched automatically in 4.3 for XS, but 4.2 had a versioning issue due 
to which it didn't change automatically.
For KVM, the ISO gets patched when you reinstall the agent package.
For Vmware, one needs to remove the old ISO from secondary storage folder 
(under /systemvm/ I think) so that the new one gets applied.

HTH
Amogh

On 10/1/14 9:51 AM, "Rohit Yadav"  wrote:

>Hi Amogh,
>
>I’ve a different issue, CPVM is opening the console but the HTTP
>service is returning old *.realhostip.com certificate.
>
>I debugged CPVM agent to find that it’s not picking up the keystore
>sent from Management server. This issue is like:
>https://issues.apache.org/jira/browse/CLOUDSTACK-3438
>
>In the logs (from CPVM), I’m only seeing "Initializing SSL from
>built-in default certificate”. Reading source from
>ConsoleProxySecureServerFactoryImpl, this means the agent is starting
>but is not getting any StartConsoleProxyAgentHttpHandlerCommand with
>new KeyStore data. I’ve tested this only for 4.2, Paul suggests
>something similar for 4.3 as well.
>
>I’ve one root certificate (id=1), two intermediate certificate (id=2,
>id=3) and a wildcard domain cert+key. I uploaded them one by one as per
>the docs and also following Chip’s blog. By doing so, the SSVM keys got
>updated and by downloading an ISO I see the https url it gave returned
>correct SSL certificate which means the chain of certificates etc. worked.
>
>In case of CPVM, accessing console in browser led to SSL error. Do you
>may any suggestions on how to get this fixed? If I remove CPVMs, I see
>it’s still using old systemvm.iso and though docs/wiki recommend
>systemvm.iso will get patched, it does not actually.
>
>On 01-Oct-2014, at 6:32 pm, Amogh Vasekar 
>wrote:
>> Hi,
>>
>> For 4.2 you may want to refer here :
>>
>>http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-c
>>ert
>>if
>> icate-chains-in-cloudstack.html
>>
>> 4.3 had a missing commit, due to which the global config
>> consoleproxy.url.domain had to be set to "mydomain.com", instead of
>> "*.mydomain.com". This has been fixed in 4.3.1
>>
>> Apologies for the inconvenience.
>>
>> Amogh
>>
>> On 10/1/14 8:16 AM, "Rohit Yadav"  wrote:
>>
>>> Just to update on the certificate upload issue with 4.2:
>>>
>>> I’m able to download and add new volumes/templates/isos and the link
>>>provided has a valid https url with the same certificate that I
>>>uploaded  though when I try to access the console I get SSL cert
>>>error and I see  that it’s still returning the old *.realhostip.com
>>>certificate. I’ve  tried to delete old CPVMs and I see the same issue
>>>coming up again.
>>>
>>>
>>> On 01-Oct-2014, at 4:55 pm, Rohit Yadav 
>>>wrote:
 Hi,

 I’ve fixed cloudmonkey to url encode parameters so now you can use
cloudmonkey to upload custom certificate but only in non-interactive
mode on shell (bash/zsh). You’ll have to install cloudmonkey from
source  for now since the fix is only on master.

 Something like:
 $ cloudmonkey upload customcertificate id=xx domainsuffix=yy
 name=zzz certificate=‘asdf asdfasdf asdfasdf asdf---'

 I’ve some issues to report while replacing certificates to get rid
 of realhostip, this is specific for Xen could apply for other
 hypervisors as well:

 - In case of 4.2, I see in the database that seq is 0 for the root
certificate for the realhostip.com domain. I uploaded certificates
in  order (root, then intermediate and finally SSL cert from UI),
and I see  the old certificate is still there. after CPVM/SSVM
restarts and are in  UP state I still get SSL errors and I see that
systemvm.iso is not  getting patche

Re: Unable to upload SSL certificate for realhostip replacement

[Rohit Yadav]

Hi Amogh,

Thanks for replying. Here the contents from the keystore table (minus sensitive 
information):

id, name, domain_suffix, seq
1 | CPVMCertificate | custom.domain.com | null
2 | root | realhostip.com | 0
4 | newroot | custom.domain.com  | 1
5 | inter1 | custom.domain.com | 2
6 | inter2 | custom.domain.com | 3

The Apache CloudStack version is 4.2.1, the systemvm.iso was built by 
jenkins.buildacloud.org and it was installed by the built rpms. In my case, the 
hosts were all XenServer 6.2. I checked the CPVM logs, and I see that it’s not 
getting keystore bytes[] from Management server at all, so falling back to the 
default realhostip.keystore file when the AgentShell starts and bootstraps 
ConsoleProxy. The only issue is when console proxy for a VM is viewed, I’m 
getting SSL cert error so instead of *.custom.domain.com I get the 
*.realhostip.com SSL cert.

Please suggest how may I debug it further or fix it?

On 01-Oct-2014, at 7:15 pm, Amogh Vasekar  wrote:
> Hi,
>
> Can you please paste the contents of the keystore table (minus the private
> key of course)?
>
> For SSVM, in 4.2, the certificate chain was not configured correctly and
> it would only use the server certificate when configuring Apache. It did
> not impact functionality though.
> This is not true for CPVM, which would try to use the full chain.
> It was fixed in 4.3, along with removing a double decoding of certificate
> when uploaded through API. The double decoding issue would manifest as
> non-server certificates to be saved incorrectly in the DB, and hence
> wanted to take a look at the table's contents. Since CPVM uses the full
> chain but not SSVM, I suspect this might be your issue.
>
> For the systemvm.iso - did you rebuild the ISO from source?
> It gets patched automatically in 4.3 for XS, but 4.2 had a versioning
> issue due to which it didn't change automatically.
> For KVM, the ISO gets patched when you reinstall the agent package.
> For Vmware, one needs to remove the old ISO from secondary storage folder
> (under /systemvm/ I think) so that the new one gets
> applied.
>
> HTH
> Amogh
>
> On 10/1/14 9:51 AM, "Rohit Yadav"  wrote:
>
>> Hi Amogh,
>>
>> I’ve a different issue, CPVM is opening the console but the HTTP service
>> is returning old *.realhostip.com certificate.
>>
>> I debugged CPVM agent to find that it’s not picking up the keystore sent
>> from Management server. This issue is like:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-3438
>>
>> In the logs (from CPVM), I’m only seeing "Initializing SSL from built-in
>> default certificate”. Reading source from
>> ConsoleProxySecureServerFactoryImpl, this means the agent is starting but
>> is not getting any StartConsoleProxyAgentHttpHandlerCommand with new
>> KeyStore data. I’ve tested this only for 4.2, Paul suggests something
>> similar for 4.3 as well.
>>
>> I’ve one root certificate (id=1), two intermediate certificate (id=2,
>> id=3) and a wildcard domain cert+key. I uploaded them one by one as per
>> the docs and also following Chip’s blog. By doing so, the SSVM keys got
>> updated and by downloading an ISO I see the https url it gave returned
>> correct SSL certificate which means the chain of certificates etc. worked.
>>
>> In case of CPVM, accessing console in browser led to SSL error. Do you
>> may any suggestions on how to get this fixed? If I remove CPVMs, I see
>> it’s still using old systemvm.iso and though docs/wiki recommend
>> systemvm.iso will get patched, it does not actually.
>>
>> On 01-Oct-2014, at 6:32 pm, Amogh Vasekar 
>> wrote:
>>> Hi,
>>>
>>> For 4.2 you may want to refer here :
>>>
>>> http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-cert
>>> if
>>> icate-chains-in-cloudstack.html
>>>
>>> 4.3 had a missing commit, due to which the global config
>>> consoleproxy.url.domain had to be set to "mydomain.com", instead of
>>> "*.mydomain.com". This has been fixed in 4.3.1
>>>
>>> Apologies for the inconvenience.
>>>
>>> Amogh
>>>
>>> On 10/1/14 8:16 AM, "Rohit Yadav"  wrote:
>>>
 Just to update on the certificate upload issue with 4.2:

 I’m able to download and add new volumes/templates/isos and the link
 provided has a valid https url with the same certificate that I
 uploaded
 though when I try to access the console I get SSL cert error and I see
 that it’s still returning the old *.realhostip.com certificate. I’ve
 tried to delete old CPVMs and I see the same issue coming up again.


 On 01-Oct-2014, at 4:55 pm, Rohit Yadav 
 wrote:
> Hi,
>
> I’ve fixed cloudmonkey to url encode parameters so now you can use
> cloudmonkey to upload custom certificate but only in non-interactive
> mode on shell (bash/zsh). You’ll have to install cloudmonkey from
> source
> for now since the fix is only on master.
>
> Something like:
> $ cloudmonkey upload customcertificate id=xx domainsuffix=yy name=zzz
> certificate=‘asdf
> asdfasdf

Re: Unable to upload SSL certificate for realhostip replacement

[Rohit Yadav]

Hi Amogh,

Thanks for pointing in the direction of checking the keystore table. I found a 
certificate entry the content of which was in bad PEM format (newline errors, 
url encode error I think), the other certs were uploaded using a patched 
CloudMonkey (fix went today into master) which would url encoded args before 
sending them to CloudStack.


On 01-Oct-2014, at 8:56 pm, Rohit Yadav  wrote:
> Hi Amogh,
>
> Thanks for replying. Here the contents from the keystore table (minus 
> sensitive information):
>
> id, name, domain_suffix, seq
> 1 | CPVMCertificate | custom.domain.com | null
> 2 | root | realhostip.com | 0
> 4 | newroot | custom.domain.com  | 1
> 5 | inter1 | custom.domain.com | 2
> 6 | inter2 | custom.domain.com | 3
>
> The Apache CloudStack version is 4.2.1, the systemvm.iso was built by 
> jenkins.buildacloud.org and it was installed by the built rpms. In my case, 
> the hosts were all XenServer 6.2. I checked the CPVM logs, and I see that 
> it’s not getting keystore bytes[] from Management server at all, so falling 
> back to the default realhostip.keystore file when the AgentShell starts and 
> bootstraps ConsoleProxy. The only issue is when console proxy for a VM is 
> viewed, I’m getting SSL cert error so instead of *.custom.domain.com I get 
> the *.realhostip.com SSL cert.
>
> Please suggest how may I debug it further or fix it?
>
> On 01-Oct-2014, at 7:15 pm, Amogh Vasekar  wrote:
>> Hi,
>>
>> Can you please paste the contents of the keystore table (minus the private
>> key of course)?
>>
>> For SSVM, in 4.2, the certificate chain was not configured correctly and
>> it would only use the server certificate when configuring Apache. It did
>> not impact functionality though.
>> This is not true for CPVM, which would try to use the full chain.
>> It was fixed in 4.3, along with removing a double decoding of certificate
>> when uploaded through API. The double decoding issue would manifest as
>> non-server certificates to be saved incorrectly in the DB, and hence
>> wanted to take a look at the table's contents. Since CPVM uses the full
>> chain but not SSVM, I suspect this might be your issue.
>>
>> For the systemvm.iso - did you rebuild the ISO from source?
>> It gets patched automatically in 4.3 for XS, but 4.2 had a versioning
>> issue due to which it didn't change automatically.
>> For KVM, the ISO gets patched when you reinstall the agent package.
>> For Vmware, one needs to remove the old ISO from secondary storage folder
>> (under /systemvm/ I think) so that the new one gets
>> applied.
>>
>> HTH
>> Amogh
>>
>> On 10/1/14 9:51 AM, "Rohit Yadav"  wrote:
>>
>>> Hi Amogh,
>>>
>>> I’ve a different issue, CPVM is opening the console but the HTTP service
>>> is returning old *.realhostip.com certificate.
>>>
>>> I debugged CPVM agent to find that it’s not picking up the keystore sent
>>> from Management server. This issue is like:
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-3438
>>>
>>> In the logs (from CPVM), I’m only seeing "Initializing SSL from built-in
>>> default certificate”. Reading source from
>>> ConsoleProxySecureServerFactoryImpl, this means the agent is starting but
>>> is not getting any StartConsoleProxyAgentHttpHandlerCommand with new
>>> KeyStore data. I’ve tested this only for 4.2, Paul suggests something
>>> similar for 4.3 as well.
>>>
>>> I’ve one root certificate (id=1), two intermediate certificate (id=2,
>>> id=3) and a wildcard domain cert+key. I uploaded them one by one as per
>>> the docs and also following Chip’s blog. By doing so, the SSVM keys got
>>> updated and by downloading an ISO I see the https url it gave returned
>>> correct SSL certificate which means the chain of certificates etc. worked.
>>>
>>> In case of CPVM, accessing console in browser led to SSL error. Do you
>>> may any suggestions on how to get this fixed? If I remove CPVMs, I see
>>> it’s still using old systemvm.iso and though docs/wiki recommend
>>> systemvm.iso will get patched, it does not actually.
>>>
>>> On 01-Oct-2014, at 6:32 pm, Amogh Vasekar 
>>> wrote:
 Hi,

 For 4.2 you may want to refer here :

 http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-cert
 if
 icate-chains-in-cloudstack.html

 4.3 had a missing commit, due to which the global config
 consoleproxy.url.domain had to be set to "mydomain.com", instead of
 "*.mydomain.com". This has been fixed in 4.3.1

 Apologies for the inconvenience.

 Amogh

 On 10/1/14 8:16 AM, "Rohit Yadav"  wrote:

> Just to update on the certificate upload issue with 4.2:
>
> I’m able to download and add new volumes/templates/isos and the link
> provided has a valid https url with the same certificate that I
> uploaded
> though when I try to access the console I get SSL cert error and I see
> that it’s still returning the old *.realhostip.com certificate. I’ve
> tried to delete old CPVMs and I see the same issu

Re: Review Request 26220: CLOUDSTACK-7645: [UI] Fixing incorrect labels, including instances of "???label.*???"

[Rohit Yadav]

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



client/WEB-INF/classes/resources/messages.properties


Titlecase? Detached?



ui/dictionary.jsp


Why remove this?


Thanks for the patch, I'm one of the folks who don't really understand UI much 
but do like to keep interest and really appreciated fixing these strings that 
have been bugging us for past few weeks now :)

- Rohit Yadav


On Oct. 1, 2014, 8:08 a.m., Mihaela Stoica wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26220/
> ---
> 
> (Updated Oct. 1, 2014, 8:08 a.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-7596, CLOUDSTACK-7597, CLOUDSTACK-7606, CLOUDSTACK-7607, 
> CLOUDSTACK-7608, and CLOUDSTACK-7645
> https://issues.apache.org/jira/browse/CLOUDSTACK-7596
> https://issues.apache.org/jira/browse/CLOUDSTACK-7597
> https://issues.apache.org/jira/browse/CLOUDSTACK-7606
> https://issues.apache.org/jira/browse/CLOUDSTACK-7607
> https://issues.apache.org/jira/browse/CLOUDSTACK-7608
> https://issues.apache.org/jira/browse/CLOUDSTACK-7645
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> - removed duplicate entries in dictionary
> - added dictionary entries that have been missed during the dictionary split
> - added missing entries in messages.properties
> - fixed other localization issues
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties c9eb7ae 
>   ui/dictionary.jsp c03ad67 
>   ui/dictionary2.jsp 39299b3 
>   ui/scripts/configuration.js b6c94f8 
>   ui/scripts/storage.js 783633c 
>   ui/scripts/templates.js 9665ffd 
>   ui/scripts/ui-custom/physicalResources.js 7dd5380 
> 
> Diff: https://reviews.apache.org/r/26220/diff/
> 
> 
> Testing
> ---
> 
> I've checked all the issues that have been reported, and they are all fixed.
> 
> 
> Thanks,
> 
> Mihaela Stoica
> 
>

Re: Review Request 26225: CLOUDSTACK-7664: [UI] Handle change in API response for listloadbalancer

[Rohit Yadav]

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

Ship it!


Ship It!

- Rohit Yadav


On Oct. 1, 2014, 12:55 p.m., Mihaela Stoica wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26225/
> ---
> 
> (Updated Oct. 1, 2014, 12:55 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Bugs: CLOUDSTACK-7664
> https://issues.apache.org/jira/browse/CLOUDSTACK-7664
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> - replaced all occurrences of "listloadbalancerssresponse" with 
> "listloadbalancersresponse" in ui\scripts\vpc.js, following the change in the 
> listLoadBalancers API response string.
> 
> 
> Diffs
> -
> 
>   ui/scripts/vpc.js 3e57631 
> 
> Diff: https://reviews.apache.org/r/26225/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Mihaela Stoica
> 
>

Build failed in Jenkins: build-master #1739

[jenkins]

See 

Changes:

[Rohit Yadav] CLOUDSTACK-7664: [UI] Handle change in API response for 
listloadbalancer

--
[...truncated 5970 lines...]
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - Storage Image default provider 
4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-storage-image-default ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-plugin-storage-image-default ---
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-hypervisor-xenserver ---
[INFO] Surefire report directory: 


---
 T E S T S
---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-storage-image-default ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-storage-image-default ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-plugin-storage-image-default ---
[INFO] Compiling 3 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-network-midonet ---
[INFO] Surefire report directory: 


---
 T E S T S
---
Running com.cloud.hypervisor.xenserver.resource.CitrixResourceBaseTest
Running com.cloud.network.element.MidoNetElementTest
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-plugin-storage-image-swift ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-plugin-storage-image-swift ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-storage-image-swift ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-plugin-storage-image-s3 ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - Storage Image sample provider 
4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-plugin-storage-image-s3 ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-storage-image-s3 ---
[INFO] Surefire report directory: 


---
 T E S T S
---
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-storage-image-sample ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-plugin-stora

Re: Unable to upload SSL certificate for realhostip replacement

[Nitin Mehta]

Just an FYI - For troubleshooting in this area do refer to
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Troubleshooting+-+up
loading+custom+domain+certificate+instead+of+using+realhostip.com

Thanks,
-Nitin
On 01/10/14 12:17 PM, "Rohit Yadav"  wrote:

>Hi Amogh,
>
>Thanks for pointing in the direction of checking the keystore table. I
>found a certificate entry the content of which was in bad PEM format
>(newline errors, url encode error I think), the other certs were uploaded
>using a patched CloudMonkey (fix went today into master) which would url
>encoded args before sending them to CloudStack.
>
>
>On 01-Oct-2014, at 8:56 pm, Rohit Yadav  wrote:
>> Hi Amogh,
>>
>> Thanks for replying. Here the contents from the keystore table (minus
>>sensitive information):
>>
>> id, name, domain_suffix, seq
>> 1 | CPVMCertificate | custom.domain.com | null
>> 2 | root | realhostip.com | 0
>> 4 | newroot | custom.domain.com  | 1
>> 5 | inter1 | custom.domain.com | 2
>> 6 | inter2 | custom.domain.com | 3
>>
>> The Apache CloudStack version is 4.2.1, the systemvm.iso was built by
>>jenkins.buildacloud.org and it was installed by the built rpms. In my
>>case, the hosts were all XenServer 6.2. I checked the CPVM logs, and I
>>see that it’s not getting keystore bytes[] from Management server at
>>all, so falling back to the default realhostip.keystore file when the
>>AgentShell starts and bootstraps ConsoleProxy. The only issue is when
>>console proxy for a VM is viewed, I’m getting SSL cert error so instead
>>of *.custom.domain.com I get the *.realhostip.com SSL cert.
>>
>> Please suggest how may I debug it further or fix it?
>>
>> On 01-Oct-2014, at 7:15 pm, Amogh Vasekar 
>>wrote:
>>> Hi,
>>>
>>> Can you please paste the contents of the keystore table (minus the
>>>private
>>> key of course)?
>>>
>>> For SSVM, in 4.2, the certificate chain was not configured correctly
>>>and
>>> it would only use the server certificate when configuring Apache. It
>>>did
>>> not impact functionality though.
>>> This is not true for CPVM, which would try to use the full chain.
>>> It was fixed in 4.3, along with removing a double decoding of
>>>certificate
>>> when uploaded through API. The double decoding issue would manifest as
>>> non-server certificates to be saved incorrectly in the DB, and hence
>>> wanted to take a look at the table's contents. Since CPVM uses the full
>>> chain but not SSVM, I suspect this might be your issue.
>>>
>>> For the systemvm.iso - did you rebuild the ISO from source?
>>> It gets patched automatically in 4.3 for XS, but 4.2 had a versioning
>>> issue due to which it didn't change automatically.
>>> For KVM, the ISO gets patched when you reinstall the agent package.
>>> For Vmware, one needs to remove the old ISO from secondary storage
>>>folder
>>> (under /systemvm/ I think) so that the new one gets
>>> applied.
>>>
>>> HTH
>>> Amogh
>>>
>>> On 10/1/14 9:51 AM, "Rohit Yadav"  wrote:
>>>
 Hi Amogh,

 I’ve a different issue, CPVM is opening the console but the HTTP
service
 is returning old *.realhostip.com certificate.

 I debugged CPVM agent to find that it’s not picking up the keystore
sent
 from Management server. This issue is like:
 https://issues.apache.org/jira/browse/CLOUDSTACK-3438

 In the logs (from CPVM), I’m only seeing "Initializing SSL from
built-in
 default certificate”. Reading source from
 ConsoleProxySecureServerFactoryImpl, this means the agent is starting
but
 is not getting any StartConsoleProxyAgentHttpHandlerCommand with new
 KeyStore data. I’ve tested this only for 4.2, Paul suggests something
 similar for 4.3 as well.

 I’ve one root certificate (id=1), two intermediate certificate (id=2,
 id=3) and a wildcard domain cert+key. I uploaded them one by one as
per
 the docs and also following Chip’s blog. By doing so, the SSVM keys
got
 updated and by downloading an ISO I see the https url it gave returned
 correct SSL certificate which means the chain of certificates etc.
worked.

 In case of CPVM, accessing console in browser led to SSL error. Do you
 may any suggestions on how to get this fixed? If I remove CPVMs, I see
 it’s still using old systemvm.iso and though docs/wiki recommend
 systemvm.iso will get patched, it does not actually.

 On 01-Oct-2014, at 6:32 pm, Amogh Vasekar 
 wrote:
> Hi,
>
> For 4.2 you may want to refer here :
>
> 
>http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-c
>ert
> if
> icate-chains-in-cloudstack.html
>
> 4.3 had a missing commit, due to which the global config
> consoleproxy.url.domain had to be set to "mydomain.com", instead of
> "*.mydomain.com". This has been fixed in 4.3.1
>
> Apologies for the inconvenience.
>
> Amogh
>
> On 10/1/14 8:16 AM, "Rohit Yadav"  wrote:
>
>> Just to update on the

Re: Unable to upload SSL certificate for realhostip replacement

[Rohit Yadav]

Thanks Nitin,

On 01-Oct-2014, at 10:06 pm, Nitin Mehta  wrote:
> Just an FYI - For troubleshooting in this area do refer to
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Troubleshooting+-+up
> loading+custom+domain+certificate+instead+of+using+realhostip.com

I actually read this wiki a couple of times before emailing. The issue was that 
I used the Chrome Advanced REST client extension as recommended in the 
docs/wiki and somehow it did not work for me, and it was difficult to use as 
well. So, I just fixed cloudmonkey to do url encoding of args and used it for 
all certificates except for one intermediate certificate which was the issue. 
Thanks.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +41 779015219 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Build failed in Jenkins: simulator-singlerun #485

[jenkins]

See 

Changes:

[Rohit Yadav] CLOUDSTACK-7664: [UI] Handle change in API response for 
listloadbalancer

--
[...truncated 8938 lines...]
[INFO] Final Memory: 44M/192M
[INFO] 
[WARNING] The requested profile "simulator" could not be activated because it 
does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer ---
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
> WARNING: Provided file does not exist: 

> Initializing database=simulator with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `simulator`
> Running query: create database `simulator`
> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified 
by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 39.554s
[INFO] Finished at: Wed Oct 01 15:58:32 EDT 2014
[INFO] Final Memory: 43M/171M
[INFO] 
[simulator-singlerun] $ /bin/bash -x /tmp/hudson2342136899674022504.sh
+ jps -l
+ grep -q Launcher
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=308
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+

Re: Review Request 26220: CLOUDSTACK-7645: [UI] Fixing incorrect labels, including instances of "???label.*???"

[Mihaela Stoica]

> On Oct. 1, 2014, 8:28 p.m., Rohit Yadav wrote:
> > ui/dictionary.jsp, line 967
> > 
> >
> > Why remove this?

Duplicated on line 969


> On Oct. 1, 2014, 8:28 p.m., Rohit Yadav wrote:
> > client/WEB-INF/classes/resources/messages.properties, line 2039
> > 
> >
> > Titlecase? Detached?

This is what we originally had in storage.js (See commit 
e3b5b213faf7fd89dfae024e129e2e7e55db898d).

However, it makes sense to change it to "Detached". I will update the diff.


- Mihaela


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


On Oct. 1, 2014, 9:08 a.m., Mihaela Stoica wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26220/
> ---
> 
> (Updated Oct. 1, 2014, 9:08 a.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Bugs: CLOUDSTACK-7596, CLOUDSTACK-7597, CLOUDSTACK-7606, CLOUDSTACK-7607, 
> CLOUDSTACK-7608, and CLOUDSTACK-7645
> https://issues.apache.org/jira/browse/CLOUDSTACK-7596
> https://issues.apache.org/jira/browse/CLOUDSTACK-7597
> https://issues.apache.org/jira/browse/CLOUDSTACK-7606
> https://issues.apache.org/jira/browse/CLOUDSTACK-7607
> https://issues.apache.org/jira/browse/CLOUDSTACK-7608
> https://issues.apache.org/jira/browse/CLOUDSTACK-7645
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> - removed duplicate entries in dictionary
> - added dictionary entries that have been missed during the dictionary split
> - added missing entries in messages.properties
> - fixed other localization issues
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties c9eb7ae 
>   ui/dictionary.jsp c03ad67 
>   ui/dictionary2.jsp 39299b3 
>   ui/scripts/configuration.js b6c94f8 
>   ui/scripts/storage.js 783633c 
>   ui/scripts/templates.js 9665ffd 
>   ui/scripts/ui-custom/physicalResources.js 7dd5380 
> 
> Diff: https://reviews.apache.org/r/26220/diff/
> 
> 
> Testing
> ---
> 
> I've checked all the issues that have been reported, and they are all fixed.
> 
> 
> Thanks,
> 
> Mihaela Stoica
> 
>

Re: Review Request 26220: CLOUDSTACK-7645: [UI] Fixing incorrect labels, including instances of "???label.*???"

[Mihaela Stoica]

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

(Updated Oct. 1, 2014, 10:25 p.m.)


Review request for cloudstack, Brian Federle and Jessica Wang.


Changes
---

Changed "detached" to "Detached"


Bugs: CLOUDSTACK-7596, CLOUDSTACK-7597, CLOUDSTACK-7606, CLOUDSTACK-7607, 
CLOUDSTACK-7608, and CLOUDSTACK-7645
https://issues.apache.org/jira/browse/CLOUDSTACK-7596
https://issues.apache.org/jira/browse/CLOUDSTACK-7597
https://issues.apache.org/jira/browse/CLOUDSTACK-7606
https://issues.apache.org/jira/browse/CLOUDSTACK-7607
https://issues.apache.org/jira/browse/CLOUDSTACK-7608
https://issues.apache.org/jira/browse/CLOUDSTACK-7645


Repository: cloudstack-git


Description
---

- removed duplicate entries in dictionary
- added dictionary entries that have been missed during the dictionary split
- added missing entries in messages.properties
- fixed other localization issues


Diffs (updated)
-

  client/WEB-INF/classes/resources/messages.properties c9eb7ae 
  ui/dictionary.jsp c03ad67 
  ui/dictionary2.jsp 39299b3 
  ui/scripts/configuration.js b6c94f8 
  ui/scripts/storage.js 783633c 
  ui/scripts/templates.js 9665ffd 
  ui/scripts/ui-custom/physicalResources.js 7dd5380 

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


Testing
---

I've checked all the issues that have been reported, and they are all fixed.


Thanks,

Mihaela Stoica

Re: Build failed in Jenkins: simulator-singlerun #485

[Nitin Mehta]

Talluri/Hugo/Others with knowledge of Jenkins - Can you please look into
this and check why we keep getting false alarms because of issues on
Jenkins side ?

Thanks,
-Nitin

On 01/10/14 1:15 PM, "jenk...@cloudstack.org" 
wrote:

>See 
>
>Changes:
>
>[Rohit Yadav] CLOUDSTACK-7664: [UI] Handle change in API response for
>listloadbalancer
>
>--
>[...truncated 8938 lines...]
>[INFO] Final Memory: 44M/192M
>[INFO] 
>
>[WARNING] The requested profile "simulator" could not be activated
>because it does not exist.
>[simulator-singlerun] $ mvn -P developer -pl developer
>-Ddeploydb-simulator
>[INFO] Scanning for projects...
>[INFO]
> 
>[INFO] 
>
>[INFO] Building Apache CloudStack Developer Mode 4.5.0-SNAPSHOT
>[INFO] 
>
>[INFO] 
>[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @
>cloud-developer ---
>[INFO] Starting audit...
>Audit done.
>
>[INFO] 
>[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
>(default) @ cloud-developer ---
>[WARNING] Ignoring missing properties file:
>ils/conf/db.properties.override>
>[INFO] 
>[INFO] --- maven-remote-resources-plugin:1.3:process (default) @
>cloud-developer ---
>[INFO] 
>[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
>[INFO] Executing tasks
>
>main:
>[INFO] Executed tasks
>[INFO] 
>[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @
>cloud-developer >>>
>[INFO] 
>[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @
>cloud-developer ---
>[INFO] Starting audit...
>Audit done.
>
>[INFO] 
>[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @
>cloud-developer <<<
>[INFO] 
>[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @
>cloud-developer ---
>log4j:WARN No appenders could be found for logger
>(org.springframework.core.env.StandardEnvironment).
>log4j:WARN Please initialize the log4j system properly.
>log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
>more info.
>> WARNING: Provided file does not exist:
>ils/conf/db.properties.override>
>> Initializing database=simulator with host=localhost port=3306
>username=cloud password=cloud
>> Running query: drop database if exists `simulator`
>> Running query: create database `simulator`
>> Running query: GRANT ALL ON simulator.* to
>'cloud'@`localhost` identified by 'cloud'
>> Running query: GRANT ALL ON simulator.* to 'cloud'@`%`
>identified by 'cloud'
>> Processing SQL file at
>t/db/create-schema-simulator.sql>
>> Processing SQL file at
>t/db/templates.simulator.sql>
>> Processing SQL file at
>t/db/hypervisor_capabilities.simulator.sql>
>> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
>[INFO] 
>[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @
>cloud-developer ---
>[INFO] 
>[INFO] --- maven-install-plugin:2.3.1:install (default-install) @
>cloud-developer ---
>[INFO] Installing 
>ml> to 
>/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.
>0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
>[INFO] 
>
>[INFO] BUILD SUCCESS
>[INFO] 
>
>[INFO] Total time: 39.554s
>[INFO] Finished at: Wed Oct 01 15:58:32 EDT 2014
>[INFO] Final Memory: 43M/171M
>[INFO] 
>
>[simulator-singlerun] $ /bin/bash -x /tmp/hudson2342136899674022504.sh
>+ jps -l
>+ grep -q Launcher
>+ echo ''
>+ rm -rf /tmp/MarvinLogs
>+ echo Check for initialization of the management server
>Check for initialization of the management server
>+ COUNTER=0
>+ SERVER_PID=308
>+ '[' 0 -lt 44 ']'
>+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
>+ sleep 5
>+ COUNTER=1
>+ '[' 1 -lt 44 ']'
>+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>+ sleep 5
>+ COUNTER=2
>+ '[' 2 -lt 44 ']'
>+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>+ sleep 5
>+ COUNTER=3
>+ '[' 3 -lt 44 ']'
>+

[MEETUP] CloudStack Silicon Valley User Group Meetup - October 9th, 2014

[Karen Vuong]

Hi all,



If you’ll be in the Silicon Valley next week - then join us! The next
CloudStack Silicon Valley Meetup has been scheduled for Thursday, October 9
th at CA Technologies. The CloudStack Silicon Valley User Group has kicked
off the Beginner's Guide to Apache CloudStack Series starting with Part 1 -
An Introduction to Apache CloudStack in September.



Now, it’s time for Part 2 – CloudStack Networking. This session will be
presented by Chiradeep Vittal, Distinguished Engineer at Citrix and Apache
CloudStack PMC member.



Date: Thursday, October 9th, 2014

Time: 6:00pm – 9:00pm

Address: CA Technologies Inc., 3965 Freedom Circle, Santa Clara, CA

Event link:
http://www.meetup.com/CloudStack-Silicon-Valley-User-Group/events/210800362/



Help Promote:



Click-to-tweet:  http://ctt.ec/U1w9I - Learn the ins-and-outs of
#CloudStack Networking w/ @chiradeep @CloudStack Silicon Valley Meetup on
10/9 clds.co/1oBux1f #opensource



Thanks,



Karen

Jenkins build is back to normal : build-master #1740

[jenkins]

See 

Build failed in Jenkins: simulator-singlerun #486

[jenkins]

See 

Changes:

[anthony.xu] added more log for create vm snapshot

--
[...truncated 8942 lines...]
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer ---
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
> WARNING: Provided file does not exist: 

> Initializing database=simulator with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `simulator`
> Running query: create database `simulator`
> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified 
by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 31.388s
[INFO] Finished at: Wed Oct 01 19:48:12 EDT 2014
[INFO] Final Memory: 42M/190M
[INFO] 
[simulator-singlerun] $ /bin/bash -x /tmp/hudson1226411314090527542.sh
+ grep -q Launcher
+ jps -l
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=7885
+ '[' 0 -lt 44 ']'
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=6
+ '[' 6 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=7
+ '[' 7 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=8
+ '[' 8 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100

[Pierre-Luc Dion]

Just tested against a 4.3.0 to 4.4.1 upgrade. Unfortunately the command
"list configurations clusterid=" using cloudmonkey doesn't work.  and
work  when it does in the UI, so it's not a UI issue :-(




On Wed, Oct 1, 2014 at 11:59 AM, Stephen Turner 
wrote:

> Can someone who's seeing this confirm whether it's a UI issue, or whether
> it's the same through the API? The ticket CLOUDSTACK-7219 has
> Component=Management Server, not UI, and (without having seen it myself) it
> feels more like a server-side issue to me.
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 01 October 2014 16:47
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> 4.4-RC20140924T2100
>
> From what I understand from this issue is UI only, which is why it wasn't
> a blocker before. anyway, you have a valid point :-(
>
> now the question would be: who could fix this ?
>
> Cluster settings change you are refering are theses [1] ,  right  ?
>
> [1]
>
> http://cloudstack-release-notes.readthedocs.org/en/4.4.1/upgrade/upgrade_notes.html#settings-changes
>
>
> On Wed, Oct 1, 2014 at 11:33 AM, Erik Weber  wrote:
>
> > Has been like that since 4.4.0
> >
> > Erik
> > 1. okt. 2014 17:16 skrev "Geoff Higginbottom" <
> > geoff.higginbot...@shapeblue.com> følgende:
> >
> > > Great, glad to hear it was an easy fix.
> > >
> > > Now however I have found another problem.  In the UI if I go to
> > > Infrastructure/Clusters/cluster1/and then choose the settings tab, I
> > > get
> > an
> > > error and no information is displayed.
> > >
> > > Can others please check this to see if it is a unique problem to me
> > > or a common issue.  This is on my upgraded install, I'll the check
> > > the clean install in a few minutes once its power up.
> > >
> > > Regards
> > >
> > > Geoff Higginbottom
> > >
> > > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> > >
> > > geoff.higginbot...@shapeblue.com
> > >
> > > -Original Message-
> > > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > > Sent: 01 October 2014 15:29
> > > To: dev@cloudstack.apache.org; Sebastien Goasguen
> > > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > > 4.4-RC20140924T2100
> > >
> > > ok, fixed it ,  /latest is pointing on the master branch for the RN
> > > git repo. so it's not reflecting the "latest" version of our product.
> > > I've disable the /latest version so URL  will default to 4.4.0 RN
> > > for
> > the
> > > moment, and the 4.4.1 RN is the correct one.
> > >
> > > Seb, do you see a problem disabling  master and latest build in RTD ?
> > >
> > > make more sense?
> > >
> > > PL
> > >
> > > On Wed, Oct 1, 2014 at 10:00 AM, Geoff Higginbottom <
> > > geoff.higginbot...@shapeblue.com> wrote:
> > >
> > > > Hi Pierre-Luc,
> > > >
> > > > Nope, I was deffinately looking at 4.4.1 release notes, complete
> > > > with sections titled 'Issues fixed in 4.4.1' etc
> > > >
> > > >
> > > > http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/
> > > > upgr
> > > > ade-4.3.html
> > > >
> > > > I would include a screen shot of the page but it will get stripped
> > > > from the e-mail
> > > >
> > > > Regards
> > > >
> > > > Geoff Higginbottom
> > > >
> > > > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> > > >
> > > > geoff.higginbot...@shapeblue.com
> > > >
> > > > -Original Message-
> > > > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > > > Sent: 01 October 2014 14:49
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch
> > > > 4.4-RC20140924T2100
> > > >
> > > > Geoff,
> > > >
> > > > Could it be possible you've followed 4.4.0 upgrade path ? because
> > > > we don't have to perform any MySQL query when upgrading to 4.4.1,
> > > > otherwise the RN is not correct.
> > > > the current RN for 4.4.1 is:
> > > >
> > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-note
> > > > s/en /4.4.1/  (not /latest yet as it's not release yet)
> > > >
> > > > for the vhd-utils, I wasn't sure if it was making sense to keep it
> > > > on all upgrade path, thanks for the comment, make sense to remove
> > > > if from upgrade 4.3.x and probably 4.2.x as it should already be in
> place.
> > > >
> > > >
> > > > PL
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Oct 1, 2014 at 9:35 AM, Geoff Higginbottom <
> > > > geoff.higginbot...@shapeblue.com> wrote:
> > > >
> > > > > +0  only because of the issues in the release notes, a clean
> > > > > +install and
> > > > > an upgrade from 4.3.1 went OK, but only because I know how to do
> > > > > it, it would not work if I followed the release notes.  The
> > > > > Router Upgrade notification elements in the UI, introduced in
> > > > > 4.3 are also broken (this should possibly be a -1 as it could
> > > > > result in installs running with the wrong version of the VRs
> > > > > without realising)
> > > > >

Build failed in Jenkins: simulator-singlerun #487

[jenkins]

See 

--
[...truncated 8932 lines...]
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2:00.849s
[INFO] Finished at: Wed Oct 01 20:20:35 EDT 2014
[INFO] Final Memory: 42M/206M
[INFO] 
[WARNING] The requested profile "simulator" could not be activated because it 
does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer ---
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
> WARNING: Provided file does not exist: 

> Initializing database=simulator with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `simulator`
> Running query: create database `simulator`
> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified 
by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 21.569s
[INFO] Finished at: Wed Oct 01 20:21:01 EDT 2014
[INFO] Final Memory: 44M/209M
[INFO] 
[simulator-singlerun] $ /bin/bash -x /tmp/hudson6466251777204795605.sh
+ grep -q Launcher
+ jps -l
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=14858
+ '[' 0 -lt 44 ']'
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1

Re: test day reminder

[Ian Duffy]

Hi All,

Using the following environment:

- XenServer 6.2
- The RPM build that was created on October 1st 2015 4:51am
http://jenkins.buildacloud.org/job/package-rhel63-master/3361/
- The system vm that was build on September 29th 2015 7:07am
http://jenkins.buildacloud.org/job/build-systemvm64-master/425/

I brought up a basic zone using marvin to do all the configuration. If
anybody wants re-create the exact same environment there is code over at
https://github.com/imduffy15/cookbook_cloudstack_wrapper adjust
chef_configuration.json as necessary to change the repo and systemvm and
then do a vagrant up (if your on windows expect issues).

Configuration was successful, my systemvms were successfully created:
http://ianduffy.ie/cloudstack/testing45/version%2bsystemvms-up.png

There was an issue with a table header on the system vms page:
http://ianduffy.ie/cloudstack/testing45/strange-labeling-on-ui.png

Another labelling issue was noted on the alerts section on the initial
screen:
http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png

The cluster configuration table under infrastructure had a white block as
its header, on hovering text would appear:
http://ianduffy.ie/cloudstack/testing45/cluster-table-renders-oddly.png

The system vms complained about a file not being found:
http://ianduffy.ie/cloudstack/testing45/system-vm-reports-script-not-found.png

Rapidly clicking the search button resulted in duplicate entries:
http://ianduffy.ie/cloudstack/testing45/clicking-the-search-button-multiple-times-results-in-duplicates.png

Add instance UI had a random scroll bar for no reason:
http://ianduffy.ie/cloudstack/testing45/add-instance-scroll-bar-for-no-reason.png

I attempted to create an instance, it failed. I believe this is due to an
issue with the version field populated for the virtual router logs
available at https://gist.github.com/imduffy15/5879718ce38f8a67bebd
After this error was created I got random prompt boxes on the UI:
http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png

I stopped my testing at this stage.

Thanks,

Ian

On 1 October 2014 17:26, Daan Hoogland  wrote:

> I have been looking at using my collegues integration work for the master
> branch. So far the packaging part is holding my back as it uses 'SNAPSHOT'
> in the build and does not allow for patch levels (in package.sh) I am
> looking at a solution.
>
> what I am thinking of is making rpms like
>
>
> cloudstack.el6_64.rpm
>
> this seems quite verbose but it gives us space to do continuous integration
> on the artifact. I am sure a scheme like this can be deviced for .deb
> packages as well.
>
> thoughts?
>
> The actual testing, for as little far as I got to do, did not yield issues
> yet.
>
> Daan
>
> On Wed, Oct 1, 2014 at 5:28 PM, Marcus  wrote:
>
> > I'd be curious to know if it works by re-adding the host.  I remember
> > running into situations like this in the past, where the mgmt server was
> > either not fully up or rejecting agents for some reason.
> >
> > On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander 
> wrote:
> >
> > >
> > >
> > > On 09/30/2014 09:26 AM, Daan Hoogland wrote:
> > > > H all,
> > > >
> > > > As you might remember, we agreed on a test day for the master branch
> on
> > > > Wednesday the 1st October, during our last meeting in Schihol-Rijk
> with
> > > > some folks. Please feel invited to test master so that we can report
> to
> > > our
> > > > RM for 4.5 for the current state and he can have a short and quick
> > > journey
> > > > to releasing.
> > > >
> > >
> > > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and
> > > that worked, but my KVM agent couldn't connect anymore afterwards:
> > >
> > > 2014-10-01 14:59:08,789 INFO  [utils.nio.NioClient]
> > > (Agent-Selector:null) Connecting to cloudstack.:8250
> > > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection]
> > > (Agent-Selector:null) Unable to initialize the threads.
> > > java.io.IOException: Connection closed with -1 on reading size.
> > > at com.cloud.utils.nio.Link.doHandshake(Link.java:509)
> > > at com.cloud.utils.nio.NioClient.init(NioClient.java:78)
> > > at
> com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
> > > at java.lang.Thread.run(Thread.java:744)
> > >
> > > Any ideas? When I try to telnet to 8250 the connection is closed
> > > immediately by the mgmt server. Nothing in the logs.
> > >
> > > So this is currently preventing me from testing the KVM agents.
> > >
> > > Wido
> > >
> > >
> > > > ​optimistically yours,​
> > > >
> > >
> >
>
>
>
> --
> Daan
>

Re: test day reminder

[Ian Duffy]

Appear to be able to work around the virtual router issue by modifying the
version field in the domain_router table. It will read Cloudstack Release
Mon Sep 29 23:17:27 UTC 2014 changing to Cloudstack Release 4.5 Mon Sep 29
23:17:27 UTC 2014 allowed me to boot an instance (note the 4.5 before Mon).

will continue testing

On 2 October 2014 01:51, Ian Duffy  wrote:

> Hi All,
>
> Using the following environment:
>
> - XenServer 6.2
> - The RPM build that was created on October 1st 2015 4:51am
> http://jenkins.buildacloud.org/job/package-rhel63-master/3361/
> - The system vm that was build on September 29th 2015 7:07am
> http://jenkins.buildacloud.org/job/build-systemvm64-master/425/
>
> I brought up a basic zone using marvin to do all the configuration. If
> anybody wants re-create the exact same environment there is code over at
> https://github.com/imduffy15/cookbook_cloudstack_wrapper adjust
> chef_configuration.json as necessary to change the repo and systemvm and
> then do a vagrant up (if your on windows expect issues).
>
> Configuration was successful, my systemvms were successfully created:
> http://ianduffy.ie/cloudstack/testing45/version%2bsystemvms-up.png
>
> There was an issue with a table header on the system vms page:
> http://ianduffy.ie/cloudstack/testing45/strange-labeling-on-ui.png
>
> Another labelling issue was noted on the alerts section on the initial
> screen:
> http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png
>
> The cluster configuration table under infrastructure had a white block as
> its header, on hovering text would appear:
> http://ianduffy.ie/cloudstack/testing45/cluster-table-renders-oddly.png
>
> The system vms complained about a file not being found:
> http://ianduffy.ie/cloudstack/testing45/system-vm-reports-script-not-found.png
>
> Rapidly clicking the search button resulted in duplicate entries:
> http://ianduffy.ie/cloudstack/testing45/clicking-the-search-button-multiple-times-results-in-duplicates.png
>
> Add instance UI had a random scroll bar for no reason:
> http://ianduffy.ie/cloudstack/testing45/add-instance-scroll-bar-for-no-reason.png
>
> I attempted to create an instance, it failed. I believe this is due to an
> issue with the version field populated for the virtual router logs
> available at https://gist.github.com/imduffy15/5879718ce38f8a67bebd
> After this error was created I got random prompt boxes on the UI:
> http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png
>
> I stopped my testing at this stage.
>
> Thanks,
>
> Ian
>
> On 1 October 2014 17:26, Daan Hoogland  wrote:
>
>> I have been looking at using my collegues integration work for the master
>> branch. So far the packaging part is holding my back as it uses 'SNAPSHOT'
>> in the build and does not allow for patch levels (in package.sh) I am
>> looking at a solution.
>>
>> what I am thinking of is making rpms like
>>
>>
>> cloudstack.el6_64.rpm
>>
>> this seems quite verbose but it gives us space to do continuous
>> integration
>> on the artifact. I am sure a scheme like this can be deviced for .deb
>> packages as well.
>>
>> thoughts?
>>
>> The actual testing, for as little far as I got to do, did not yield issues
>> yet.
>>
>> Daan
>>
>> On Wed, Oct 1, 2014 at 5:28 PM, Marcus  wrote:
>>
>> > I'd be curious to know if it works by re-adding the host.  I remember
>> > running into situations like this in the past, where the mgmt server was
>> > either not fully up or rejecting agents for some reason.
>> >
>> > On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander 
>> wrote:
>> >
>> > >
>> > >
>> > > On 09/30/2014 09:26 AM, Daan Hoogland wrote:
>> > > > H all,
>> > > >
>> > > > As you might remember, we agreed on a test day for the master
>> branch on
>> > > > Wednesday the 1st October, during our last meeting in Schihol-Rijk
>> with
>> > > > some folks. Please feel invited to test master so that we can
>> report to
>> > > our
>> > > > RM for 4.5 for the current state and he can have a short and quick
>> > > journey
>> > > > to releasing.
>> > > >
>> > >
>> > > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and
>> > > that worked, but my KVM agent couldn't connect anymore afterwards:
>> > >
>> > > 2014-10-01 14:59:08,789 INFO  [utils.nio.NioClient]
>> > > (Agent-Selector:null) Connecting to cloudstack.:8250
>> > > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection]
>> > > (Agent-Selector:null) Unable to initialize the threads.
>> > > java.io.IOException: Connection closed with -1 on reading size.
>> > > at com.cloud.utils.nio.Link.doHandshake(Link.java:509)
>> > > at com.cloud.utils.nio.NioClient.init(NioClient.java:78)
>> > > at
>> com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
>> > > at java.lang.Thread.run(Thread.java:744)
>> > >
>> > > Any ideas? When I try to telnet to 8250 the connection is closed
>> > > immediately by the mgmt server. Nothing in 

Re: test day reminder

[Ian Duffy]

Instance successfully booted with above noted workaround.
Created a ingress security group rule to allow SSH access to the instance.
The rule applied as expected and ssh access was allowed.
Created an egress security group rule to allow HTTP access out from the
instance. The rule applied as expected all traffic out of the VM was
blocked excluding http.
Created a new volume, successfully attached it to the booted instance.

Added a new ISO.
ISO was successfully downloaded and installed.
Was successfully able to download the ISO from secondary storage via the UI.
I was unable to delete the ISO using the UI. (No button present)

I created a new project, the UI was inconsistent
http://ianduffy.ie/cloudstack/testing45/project-ui.png

I noticed the baremetal-system-account as documented over here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support
It felt confusing/unclear. It should be hidden like the system account in
my view.

Clicking add guest network and then pressing cancel resulted in an api
error:
http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2002.12.11.png

Successfully created a new account and created new instances with this
account. I was able to submit an invalid email for this e.g. not
@.

Successfully created a subdomain, UI didn't display it until the parent
domain was collapsed and expanded.
Creating enough nested subdomains allowed the tree to go off the screen. no
scroll bar was provided.
http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2002.16.48.png

If I:
1) Create a subdomain of root labelled test
2) Create a subdomain of the subdomain created in step one, again labelling
it test e.g. test/test
3) I rename test subdomain directly under root to rubbishdata
4) I attempt to rename rubbishdata back to test I get a message saying:
"specified domain id with name 'test' already exists in the system"


On 2 October 2014 01:55, Ian Duffy  wrote:

> Appear to be able to work around the virtual router issue by modifying the
> version field in the domain_router table. It will read Cloudstack Release
> Mon Sep 29 23:17:27 UTC 2014 changing to Cloudstack Release 4.5 Mon Sep 29
> 23:17:27 UTC 2014 allowed me to boot an instance (note the 4.5 before Mon).
>
> will continue testing
>
> On 2 October 2014 01:51, Ian Duffy  wrote:
>
>> Hi All,
>>
>> Using the following environment:
>>
>> - XenServer 6.2
>> - The RPM build that was created on October 1st 2015 4:51am
>> http://jenkins.buildacloud.org/job/package-rhel63-master/3361/
>> - The system vm that was build on September 29th 2015 7:07am
>> http://jenkins.buildacloud.org/job/build-systemvm64-master/425/
>>
>> I brought up a basic zone using marvin to do all the configuration. If
>> anybody wants re-create the exact same environment there is code over at
>> https://github.com/imduffy15/cookbook_cloudstack_wrapper adjust
>> chef_configuration.json as necessary to change the repo and systemvm and
>> then do a vagrant up (if your on windows expect issues).
>>
>> Configuration was successful, my systemvms were successfully created:
>> http://ianduffy.ie/cloudstack/testing45/version%2bsystemvms-up.png
>>
>> There was an issue with a table header on the system vms page:
>> http://ianduffy.ie/cloudstack/testing45/strange-labeling-on-ui.png
>>
>> Another labelling issue was noted on the alerts section on the initial
>> screen:
>> http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png
>>
>> The cluster configuration table under infrastructure had a white block as
>> its header, on hovering text would appear:
>> http://ianduffy.ie/cloudstack/testing45/cluster-table-renders-oddly.png
>>
>> The system vms complained about a file not being found:
>> http://ianduffy.ie/cloudstack/testing45/system-vm-reports-script-not-found.png
>>
>> Rapidly clicking the search button resulted in duplicate entries:
>> http://ianduffy.ie/cloudstack/testing45/clicking-the-search-button-multiple-times-results-in-duplicates.png
>>
>> Add instance UI had a random scroll bar for no reason:
>> http://ianduffy.ie/cloudstack/testing45/add-instance-scroll-bar-for-no-reason.png
>>
>> I attempted to create an instance, it failed. I believe this is due to an
>> issue with the version field populated for the virtual router logs
>> available at https://gist.github.com/imduffy15/5879718ce38f8a67bebd
>> After this error was created I got random prompt boxes on the UI:
>> http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png
>>
>> I stopped my testing at this stage.
>>
>> Thanks,
>>
>> Ian
>>
>> On 1 October 2014 17:26, Daan Hoogland  wrote:
>>
>>> I have been looking at using my collegues integration work for the master
>>> branch. So far the packaging part is holding my back as it uses
>>> 'SNAPSHOT'
>>> in the build and does not allow for patch levels (in package.sh) I am
>>> looking at a solution.
>>>
>>> what I am thinking of is making rpms

[GitHub] cloudstack pull request: VPC and Virtual Network Managers refactor...

[wilderrodrigues]

Github user wilderrodrigues closed the pull request at:

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


---
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: VPC and Virtual Network Managers refactor...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/19#issuecomment-57588211
  
Hi @bhaisaab ,

We are busy rebasing and getting the conflicts fixed + retesting everything 
before sending a new PR.

We also documented the changes and made class diagrams so the other 
developers will understand better what is in place now.

We will add all those to the merge request that will be sent to the 
community.

Cheers,
Wilder


---
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: test day reminder

[Ove Ewerlid]

On 09/30/2014 09:26 AM, Daan Hoogland wrote:

H all,

As you might remember, we agreed on a test day for the master branch on
Wednesday the 1st October, during our last meeting in Schihol-Rijk with
some folks. Please feel invited to test master so that we can report to our
RM for 4.5 for the current state and he can have a short and quick journey
to releasing.

​optimistically yours,​



Stod up master in an environment where 4.4.1 and prior works.
Environment is updated OEL65 for management head and hypervisors.
Last commit in master build is;
  70efe1507c3bc1cf6c3a9477bae4f31afc35375f

The management head does not start, aborts early with;
  2014-10-02 08:31:38,748 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) 
Error while decrypting: GPU

as last entry in management log.

Looks connected to;
  https://issues.apache.org/jira/browse/CLOUDSTACK-7242

/Ove


--
Ove Everlid
System Administrator / Architect / SDN- & Automation- & Linux-hacker
Mobile: +46706668199 (dedicated work mobile)
Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)