[GitHub] cloudstack pull request: Merge 4.5 to master

[karuturi]

GitHub user karuturi opened a pull request:

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

Merge 4.5 to master



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

$ git pull https://github.com/karuturi/cloudstack merge-45-to-master-2

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

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

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

This closes #53


commit 2d3b3376e37faeec3ed62a58750819dc7630260c
Author: Sheng Yang 
Date:   2014-11-14T19:43:03Z

Revert "CLOUDSTACK-7821: Fix OSX cannot connect to VPN due to wrongly 
declaim ENCAPSULATION_MODE_UDP_TRANSPORT_RFC"

This reverts commit e1c788ca3c69a8c8c2041c7b106f76fa49332888.

It breaks Windows 7 client.

commit 425a6b01d60b88016c23a1126960375b00d97069
Author: Anthony Xu 
Date:   2014-11-14T19:24:42Z

CLOUDSTACK-7918:
guest os name changes from 'SUSE Linux Enterprise Server 12 (experimental)' 
to 'SUSE Linux Enterprise Server 12 (64-bit)' in latest XS 5.6 ,
changed the guest OS mapping to fix it.

commit 303fc90057db2707ae8f6b709fb5e3e86fc9db40
Author: Milamber 
Date:   2014-11-15T08:37:49Z

Update L10N resource files on master branch (with 4.5 translation strings)

commit 25e5d00f6016b31fc178da97c7125c2f37a8c40d
Author: Milamber 
Date:   2014-11-15T08:38:34Z

Add 4.5.x messages.properties to Transifex config tool

commit 19781e094b987cf65d05d890cd3cd86fc22cb873
Author: Chandan Purushothama 
Date:   2014-11-14T06:56:01Z

CLOUDSTACK-7913 : Added reconnect functionality to Host class in base.py

Signed-off-by: SrikanteswaraRao Talluri 

commit 5f99917991a59f8ecd6d8b0e17b497fe210e636e
Author: Gaurav Aradhye 
Date:   2014-11-14T14:23:25Z

CLOUDSTACK-7912: Remove hardcoded netscaler info and read it from config 
file

Signed-off-by: SrikanteswaraRao Talluri 

commit 635abaf2e9ca4f0399085f441ea6d5eeaab9f3ab
Author: Jessica Wang 
Date:   2014-11-17T21:05:08Z

CLOUDSTACK-7927: UI > Infrastructure > Primary Storage > detailView > add 
"View Volumes" link that will list all volumes under this primary storage when 
being clicked.

commit f43ffb9a0f71f380f896e1e5c581725e9c08faab
Author: Anshul Gangwar 
Date:   2014-10-09T05:07:21Z

CLOUDSTACK-7688, CLOUDSTACK-7747: restricted various operations for VM with 
VM snapshots which breaks VM snapshots.
 Now they are informed that they cannot perform the operation.
 To perform operation they have to remove VM snapshots of VM.

commit c04cdae60bc9a10f584c2f0b591aa5a5d9c7e3e4
Author: Anshul Gangwar 
Date:   2014-10-28T06:19:30Z

CLOUDSTACK-7767: fixed events are not generated for snapshot creation

commit ae199b6ce7634ef702243c20800937c8a3ab4b14
Author: Anshul Gangwar 
Date:   2014-10-20T10:34:25Z

CLOUDSTACK-7703, CLOUDSTACK-7752: Fixed deployment planner stuck in 
infinite loop.
If we create VM with shared service offering and attach disk with local 
disk offering,
and one of storage pool is full(cannot be allocated) and other is not full 
then
we are not putting the cluster in avoid list which is causing this infinite 
loop.

Fixed by putting the cluster in avoid list even if one of the storage pool 
is full(cannot be allocated)

commit bcc20380680a84f7975f75aa8c6ebdaadb1f8540
Author: Anshul Gangwar 
Date:   2014-09-24T07:20:16Z

CLOUDSTACK-7620: Added SNMP MIB file for snmp-alerts plugin

commit 44d12330b9d7494ad392e0549ffbdc7100130f86
Author: Anshul Gangwar 
Date:   2014-10-21T09:27:16Z

CLOUDSTACK-7758: Fixed although api calls are failing, event tab shows them 
as successful

This closes #29

commit 4721e66d0e2ed89836286f1654a30a3568b284b6
Author: Anshul Gangwar 
Date:   2014-10-22T04:29:42Z

CLOUDSTACK-7541: Added restriction to not allow custom disk offering with 
disksize UI doesn't allow but with API we were able to create custom disk 
offering with disk size which was causing this issue
This closes #28

commit 8307dd9105cdb70a0fe09c059bacfcec43a29024
Author: Anshul Gangwar 
Date:   2014-11-17T09:57:22Z

CLOUDSTACK-7930, CLOUDSTACK-7931: Do not allow to set invalid values for 
global settings which are of type integer and float

This closes #41

commit 4d583a4a71313d9f62438818c9d657a7c4a5d43d
Author: Anshul Gangwar 
Date:   2014-11-17T07:30:42Z

CLOUDSTACK-7932: Fixed wrong semantics for isVmAlive() method in 
HypervInvestigator

Findbugs will report error on this as it is expecting true/false for 
Boolean value.
But we have diffrent meaning for null so it is false positive case from 
findbug

This closes #39

commit 9c328cb9ddd6aa3d9d14ec5efb190ed2a46dc4df
Author: Anshul Gangwar 
Date:   2014-11-14T05:26:05Z

CLOUDSTACK-7929: While creating network offering if one specifies negative 
value for network rate then we will convert that value to 0 i.e. unlimite

[GitHub] cloudstack pull request: Update ConsoleProxyPasswordBasedEncryptor...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/10#issuecomment-66041100
  
Hi Tim,

IMO, the fixes are in main methods of those classes, so do they even affect 
CloudStack mgmt server, I'm not sure?

Both the PRs cannot be accepted the keyIvPair variable was deleted, the one 
defined in the class is non-static so cannot be used in the main method. I 
suggest that you close both of them and open a new one that fixes the classes 
the both the locations in a single PR on master. Since the fix is small, put 
both of them in a single patch so it's easier for me to cherry-pick them to 
4.5, 4.4 and 4.3 branches.

Cheers.


---
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: Merge 4.5 to master

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/53#issuecomment-66041167
  
Thanks Rajani for the PR, let's merge as soon as Travis passes.


---
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: CLOUDSTACK-6212: Let vm_instance table's ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: CLOUDSTACK-7986 [F5 LB] Failed to execute...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/47#issuecomment-66041997
  
Thanks Rajani, go for it!


---
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: Review Request 20078: console-proxy add support of AltGr key and FR azerty keyboard

[Axel Delahaye]

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

(Updated déc. 8, 2014, 9:31 matin)


Review request for cloudstack, Anshul Gangwar, Brian Federle, Chiradeep Vittal, 
Jessica Wang, and Sanjay Tripathi.


Changes
---

update to apply cleanly on master


Repository: cloudstack-git


Description (updated)
---

(Port of https://reviews.apache.org/r/16688/ to master branch)

Firstly, I add a match condition 'altgr' for "Conditional mapping entry" in 
ajaxviwer.js.
altgr : , -- match on altgr state

It works like the shift match condition.
shift : , -- match on shift state

Browser can't detect difference between AltGr and Ctrl+Alt pressed at the same 
time.
So when the modifier is 896, (Alt(512) + Ctrl(384)) I assume it is the AltGr 
key and 'altgr' condition will be true.

In the ajaxkey.js file you got for example:
{type: KEY_DOWN, code: 0x32, modifiers: 0, altgr: true}
to send the spécified key to vnc if user pressed the AltGr (or Ctrl+Alt) key

Secondly,
I wrote the French AZERTY translation table in ajaxkeys.js with the support of 
AltGr character (like #{}[]|,etc.)

For example the '#':

{keycode: 51, entry: [ //User type the "3# key and each condition match 
'altgr'
{type: KEY_DOWN, code: 0xffea, modifiers: 0, altgr: true}, //press the VNC 
AltGR key
{type: KEY_DOWN, code: 0x33, modifiers: 0, altgr: true},   //press the 3 key
{type: KEY_UP, code: 0x33, modifiers: 0, altgr: true}, //release it
{type: KEY_UP, code: 0xffea, modifiers: 0, altgr: true}//release the AltGr 
key
]},

Thanks for watching my work

Axel Delahaye


Diffs (updated)
-

  
services/console-proxy/server/src/com/cloud/consoleproxy/ConsoleProxyClientBase.java
 eb38007 
  systemvm/css/ajaxviewer.css fd2fb3c 
  systemvm/js/ajaxkeys.js 8f78cc8 
  systemvm/js/ajaxviewer.js ff899b1 

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


Testing
---

Tested with
Hardware : French AZERTY keyboard
Software : Configured in windows as FR keyboard
Console-proxy : Customized Standard (US) keyboard
Guest : CentOS 6.5 , Debian 7 and FreeBSD 8
Guest keymap : fr, fr-pc


Thanks,

Axel Delahaye

Re: Review Request 20078: console-proxy add support of AltGr key and FR azerty keyboard

[Axel Delahaye]

> On déc. 5, 2014, 5:57 après-midi, Rohit Yadav wrote:
> > Interesting feature, can you fix and send one that applies cleanly on 
> > master? Thanks.

done


- Axel


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


On déc. 8, 2014, 9:31 matin, Axel Delahaye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/20078/
> ---
> 
> (Updated déc. 8, 2014, 9:31 matin)
> 
> 
> Review request for cloudstack, Anshul Gangwar, Brian Federle, Chiradeep 
> Vittal, Jessica Wang, and Sanjay Tripathi.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> (Port of https://reviews.apache.org/r/16688/ to master branch)
> 
> Firstly, I add a match condition 'altgr' for "Conditional mapping entry" in 
> ajaxviwer.js.
> altgr : , -- match on altgr state
> 
> It works like the shift match condition.
> shift : , -- match on shift state
> 
> Browser can't detect difference between AltGr and Ctrl+Alt pressed at the 
> same time.
> So when the modifier is 896, (Alt(512) + Ctrl(384)) I assume it is the AltGr 
> key and 'altgr' condition will be true.
> 
> In the ajaxkey.js file you got for example:
> {type: KEY_DOWN, code: 0x32, modifiers: 0, altgr: true}
> to send the spécified key to vnc if user pressed the AltGr (or Ctrl+Alt) key
> 
> Secondly,
> I wrote the French AZERTY translation table in ajaxkeys.js with the support 
> of AltGr character (like #{}[]|,etc.)
> 
> For example the '#':
> 
> {keycode: 51, entry: [ //User type the "3# key and each condition 
> match 'altgr'
> {type: KEY_DOWN, code: 0xffea, modifiers: 0, altgr: true}, //press the VNC 
> AltGR key
> {type: KEY_DOWN, code: 0x33, modifiers: 0, altgr: true},   //press the 3 key
> {type: KEY_UP, code: 0x33, modifiers: 0, altgr: true}, //release it
> {type: KEY_UP, code: 0xffea, modifiers: 0, altgr: true}//release the 
> AltGr key
> ]},
> 
> Thanks for watching my work
> 
> Axel Delahaye
> 
> 
> Diffs
> -
> 
>   
> services/console-proxy/server/src/com/cloud/consoleproxy/ConsoleProxyClientBase.java
>  eb38007 
>   systemvm/css/ajaxviewer.css fd2fb3c 
>   systemvm/js/ajaxkeys.js 8f78cc8 
>   systemvm/js/ajaxviewer.js ff899b1 
> 
> Diff: https://reviews.apache.org/r/20078/diff/
> 
> 
> Testing
> ---
> 
> Tested with
> Hardware : French AZERTY keyboard
> Software : Configured in windows as FR keyboard
> Console-proxy : Customized Standard (US) keyboard
> Guest : CentOS 6.5 , Debian 7 and FreeBSD 8
> Guest keymap : fr, fr-pc
> 
> 
> Thanks,
> 
> Axel Delahaye
> 
>

Re: [DISCUSS] Any issues to be fixed for 4.3.1?

[France]

Hi Rohit,

Here are a few issues (without resolution). Maybe you can help get a fix in 
time for 4.3.2 release:

Snapshosts errors after upgrade 4.1.1 to 4.3.1:
https://issues.apache.org/jira/browse/CLOUDSTACK-8013

Failed to create a volume from snapshot:
https://issues.apache.org/jira/browse/CLOUDSTACK-8014

Virtual Router only with DHCP should not have DNS service
https://issues.apache.org/jira/browse/CLOUDSTACK-4675

Excessive use of LVM snapshots on XenServer, that leads to snapshot failure and 
unnecessary disk usage.
https://issues.apache.org/jira/browse/CLOUDSTACK-6060

Possibly this one too:
Failed to create snapshot due to an internal error creating snapshot for volume 
372 -> Failure from sparse_dd: Fatal error: exception Invalid_argument("index 
out of bounds”):
https://issues.apache.org/jira/browse/CLOUDSTACK-8044?filter=-2

Some others, you have already back-ported. For that we thank you.

Thank you,
Regards,
F.


On 20 Nov 2014, at 10:15, Rohit Yadav  wrote:

> Hi,
> 
> We’ve some bugfixes backported to 4.3 branch since 4.3.1 was released and I 
> think we should at least support this branch with a 4.3.2 release in next 
> couple of weeks until a stable 4.5.0 is released in next couple of months.
> 
> I’m going through JIRA and list of issues and will help backport fixes to the 
> 4.3 branch. So, please share if you’ve found any blocker/critical/major issue 
> that you found in 4.3.0 or 4.3.1 and want to be fixed. Thanks.
> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | 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 Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses

[GitHub] cloudstack pull request: Merge 4.5 to master

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/53#issuecomment-66043331
  
sure Rohit.. waiting for travis to finish. 


---
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: Review Request 20078: console-proxy add support of AltGr key and FR azerty keyboard

[Rohit Yadav]

> On Dec. 5, 2014, 5:57 p.m., Rohit Yadav wrote:
> > Interesting feature, can you fix and send one that applies cleanly on 
> > master? Thanks.
> 
> Axel Delahaye wrote:
> done

Hi Axel - on latest master, I'm unable to apply it using git am . It 
fails. I will be able to merge your contribution as soon as you could send me a 
patch that applies cleanly, thanks.


- Rohit


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


On Dec. 8, 2014, 9:31 a.m., Axel Delahaye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/20078/
> ---
> 
> (Updated Dec. 8, 2014, 9:31 a.m.)
> 
> 
> Review request for cloudstack, Anshul Gangwar, Brian Federle, Chiradeep 
> Vittal, Jessica Wang, and Sanjay Tripathi.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> (Port of https://reviews.apache.org/r/16688/ to master branch)
> 
> Firstly, I add a match condition 'altgr' for "Conditional mapping entry" in 
> ajaxviwer.js.
> altgr : , -- match on altgr state
> 
> It works like the shift match condition.
> shift : , -- match on shift state
> 
> Browser can't detect difference between AltGr and Ctrl+Alt pressed at the 
> same time.
> So when the modifier is 896, (Alt(512) + Ctrl(384)) I assume it is the AltGr 
> key and 'altgr' condition will be true.
> 
> In the ajaxkey.js file you got for example:
> {type: KEY_DOWN, code: 0x32, modifiers: 0, altgr: true}
> to send the spécified key to vnc if user pressed the AltGr (or Ctrl+Alt) key
> 
> Secondly,
> I wrote the French AZERTY translation table in ajaxkeys.js with the support 
> of AltGr character (like #{}[]|,etc.)
> 
> For example the '#':
> 
> {keycode: 51, entry: [ //User type the "3# key and each condition 
> match 'altgr'
> {type: KEY_DOWN, code: 0xffea, modifiers: 0, altgr: true}, //press the VNC 
> AltGR key
> {type: KEY_DOWN, code: 0x33, modifiers: 0, altgr: true},   //press the 3 key
> {type: KEY_UP, code: 0x33, modifiers: 0, altgr: true}, //release it
> {type: KEY_UP, code: 0xffea, modifiers: 0, altgr: true}//release the 
> AltGr key
> ]},
> 
> Thanks for watching my work
> 
> Axel Delahaye
> 
> 
> Diffs
> -
> 
>   
> services/console-proxy/server/src/com/cloud/consoleproxy/ConsoleProxyClientBase.java
>  eb38007 
>   systemvm/css/ajaxviewer.css fd2fb3c 
>   systemvm/js/ajaxkeys.js 8f78cc8 
>   systemvm/js/ajaxviewer.js ff899b1 
> 
> Diff: https://reviews.apache.org/r/20078/diff/
> 
> 
> Testing
> ---
> 
> Tested with
> Hardware : French AZERTY keyboard
> Software : Configured in windows as FR keyboard
> Console-proxy : Customized Standard (US) keyboard
> Guest : CentOS 6.5 , Debian 7 and FreeBSD 8
> Guest keymap : fr, fr-pc
> 
> 
> Thanks,
> 
> Axel Delahaye
> 
>

[GitHub] cloudstack pull request: Merge 4.5 to master

[runseb]

Github user runseb commented on the pull request:

https://github.com/apache/cloudstack/pull/53#issuecomment-66044338
  
Hi folks, any chance to try those merges with the noawsapi branch ? I am 
working on IP clearance for ec2stack and gstack and once we get that under the 
project, I would like to propose a merge of noawsapi to master (removing the 
awsapi). But it would be nice to keep noawsapi branch in synch already. I just 
don't have time to try the merges myself.


---
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: Review Request 20078: console-proxy add support of AltGr key and FR azerty keyboard

[Axel Delahaye]

> On déc. 5, 2014, 5:57 après-midi, Rohit Yadav wrote:
> > Interesting feature, can you fix and send one that applies cleanly on 
> > master? Thanks.
> 
> Axel Delahaye wrote:
> done
> 
> Rohit Yadav wrote:
> Hi Axel - on latest master, I'm unable to apply it using git am . 
> It fails. I will be able to merge your contribution as soon as you could send 
> me a patch that applies cleanly, thanks.

Oh yes, my 'git pull' failed, I have more things to fix now ^^
I'm working on it.
Thanks for merging :)


- Axel


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


On déc. 8, 2014, 9:31 matin, Axel Delahaye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/20078/
> ---
> 
> (Updated déc. 8, 2014, 9:31 matin)
> 
> 
> Review request for cloudstack, Anshul Gangwar, Brian Federle, Chiradeep 
> Vittal, Jessica Wang, and Sanjay Tripathi.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> (Port of https://reviews.apache.org/r/16688/ to master branch)
> 
> Firstly, I add a match condition 'altgr' for "Conditional mapping entry" in 
> ajaxviwer.js.
> altgr : , -- match on altgr state
> 
> It works like the shift match condition.
> shift : , -- match on shift state
> 
> Browser can't detect difference between AltGr and Ctrl+Alt pressed at the 
> same time.
> So when the modifier is 896, (Alt(512) + Ctrl(384)) I assume it is the AltGr 
> key and 'altgr' condition will be true.
> 
> In the ajaxkey.js file you got for example:
> {type: KEY_DOWN, code: 0x32, modifiers: 0, altgr: true}
> to send the spécified key to vnc if user pressed the AltGr (or Ctrl+Alt) key
> 
> Secondly,
> I wrote the French AZERTY translation table in ajaxkeys.js with the support 
> of AltGr character (like #{}[]|,etc.)
> 
> For example the '#':
> 
> {keycode: 51, entry: [ //User type the "3# key and each condition 
> match 'altgr'
> {type: KEY_DOWN, code: 0xffea, modifiers: 0, altgr: true}, //press the VNC 
> AltGR key
> {type: KEY_DOWN, code: 0x33, modifiers: 0, altgr: true},   //press the 3 key
> {type: KEY_UP, code: 0x33, modifiers: 0, altgr: true}, //release it
> {type: KEY_UP, code: 0xffea, modifiers: 0, altgr: true}//release the 
> AltGr key
> ]},
> 
> Thanks for watching my work
> 
> Axel Delahaye
> 
> 
> Diffs
> -
> 
>   
> services/console-proxy/server/src/com/cloud/consoleproxy/ConsoleProxyClientBase.java
>  eb38007 
>   systemvm/css/ajaxviewer.css fd2fb3c 
>   systemvm/js/ajaxkeys.js 8f78cc8 
>   systemvm/js/ajaxviewer.js ff899b1 
> 
> Diff: https://reviews.apache.org/r/20078/diff/
> 
> 
> Testing
> ---
> 
> Tested with
> Hardware : French AZERTY keyboard
> Software : Configured in windows as FR keyboard
> Console-proxy : Customized Standard (US) keyboard
> Guest : CentOS 6.5 , Debian 7 and FreeBSD 8
> Guest keymap : fr, fr-pc
> 
> 
> Thanks,
> 
> Axel Delahaye
> 
>

[GitHub] cloudstack pull request: Merge 4.5 to master

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Review Request 20078: console-proxy add support of AltGr key and FR azerty keyboard

[Axel Delahaye]

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

(Updated déc. 8, 2014, 10:30 matin)


Review request for cloudstack, Anshul Gangwar, Brian Federle, Chiradeep Vittal, 
Jessica Wang, and Sanjay Tripathi.


Changes
---

tested on master with : git am 


Repository: cloudstack-git


Description
---

(Port of https://reviews.apache.org/r/16688/ to master branch)

Firstly, I add a match condition 'altgr' for "Conditional mapping entry" in 
ajaxviwer.js.
altgr : , -- match on altgr state

It works like the shift match condition.
shift : , -- match on shift state

Browser can't detect difference between AltGr and Ctrl+Alt pressed at the same 
time.
So when the modifier is 896, (Alt(512) + Ctrl(384)) I assume it is the AltGr 
key and 'altgr' condition will be true.

In the ajaxkey.js file you got for example:
{type: KEY_DOWN, code: 0x32, modifiers: 0, altgr: true}
to send the spécified key to vnc if user pressed the AltGr (or Ctrl+Alt) key

Secondly,
I wrote the French AZERTY translation table in ajaxkeys.js with the support of 
AltGr character (like #{}[]|,etc.)

For example the '#':

{keycode: 51, entry: [ //User type the "3# key and each condition match 
'altgr'
{type: KEY_DOWN, code: 0xffea, modifiers: 0, altgr: true}, //press the VNC 
AltGR key
{type: KEY_DOWN, code: 0x33, modifiers: 0, altgr: true},   //press the 3 key
{type: KEY_UP, code: 0x33, modifiers: 0, altgr: true}, //release it
{type: KEY_UP, code: 0xffea, modifiers: 0, altgr: true}//release the AltGr 
key
]},

Thanks for watching my work

Axel Delahaye


Diffs (updated)
-

  
services/console-proxy/server/src/com/cloud/consoleproxy/ConsoleProxyClientBase.java
 fc3bf4b 
  systemvm/css/ajaxviewer.css fd2fb3c 
  systemvm/js/ajaxkeys.js 3053b7d 
  systemvm/js/ajaxviewer.js db5ed45 

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


Testing
---

Tested with
Hardware : French AZERTY keyboard
Software : Configured in windows as FR keyboard
Console-proxy : Customized Standard (US) keyboard
Guest : CentOS 6.5 , Debian 7 and FreeBSD 8
Guest keymap : fr, fr-pc


Thanks,

Axel Delahaye

Re: Review Request 20078: console-proxy add support of AltGr key and FR azerty keyboard

[Axel Delahaye]

> On déc. 5, 2014, 5:57 après-midi, Rohit Yadav wrote:
> > Interesting feature, can you fix and send one that applies cleanly on 
> > master? Thanks.
> 
> Axel Delahaye wrote:
> done
> 
> Rohit Yadav wrote:
> Hi Axel - on latest master, I'm unable to apply it using git am . 
> It fails. I will be able to merge your contribution as soon as you could send 
> me a patch that applies cleanly, thanks.
> 
> Axel Delahaye wrote:
> Oh yes, my 'git pull' failed, I have more things to fix now ^^
> I'm working on it.
> Thanks for merging :)

It's ok now! (I hope)

Happy patching


- Axel


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


On déc. 8, 2014, 10:30 matin, Axel Delahaye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/20078/
> ---
> 
> (Updated déc. 8, 2014, 10:30 matin)
> 
> 
> Review request for cloudstack, Anshul Gangwar, Brian Federle, Chiradeep 
> Vittal, Jessica Wang, and Sanjay Tripathi.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> (Port of https://reviews.apache.org/r/16688/ to master branch)
> 
> Firstly, I add a match condition 'altgr' for "Conditional mapping entry" in 
> ajaxviwer.js.
> altgr : , -- match on altgr state
> 
> It works like the shift match condition.
> shift : , -- match on shift state
> 
> Browser can't detect difference between AltGr and Ctrl+Alt pressed at the 
> same time.
> So when the modifier is 896, (Alt(512) + Ctrl(384)) I assume it is the AltGr 
> key and 'altgr' condition will be true.
> 
> In the ajaxkey.js file you got for example:
> {type: KEY_DOWN, code: 0x32, modifiers: 0, altgr: true}
> to send the spécified key to vnc if user pressed the AltGr (or Ctrl+Alt) key
> 
> Secondly,
> I wrote the French AZERTY translation table in ajaxkeys.js with the support 
> of AltGr character (like #{}[]|,etc.)
> 
> For example the '#':
> 
> {keycode: 51, entry: [ //User type the "3# key and each condition 
> match 'altgr'
> {type: KEY_DOWN, code: 0xffea, modifiers: 0, altgr: true}, //press the VNC 
> AltGR key
> {type: KEY_DOWN, code: 0x33, modifiers: 0, altgr: true},   //press the 3 key
> {type: KEY_UP, code: 0x33, modifiers: 0, altgr: true}, //release it
> {type: KEY_UP, code: 0xffea, modifiers: 0, altgr: true}//release the 
> AltGr key
> ]},
> 
> Thanks for watching my work
> 
> Axel Delahaye
> 
> 
> Diffs
> -
> 
>   
> services/console-proxy/server/src/com/cloud/consoleproxy/ConsoleProxyClientBase.java
>  fc3bf4b 
>   systemvm/css/ajaxviewer.css fd2fb3c 
>   systemvm/js/ajaxkeys.js 3053b7d 
>   systemvm/js/ajaxviewer.js db5ed45 
> 
> Diff: https://reviews.apache.org/r/20078/diff/
> 
> 
> Testing
> ---
> 
> Tested with
> Hardware : French AZERTY keyboard
> Software : Configured in windows as FR keyboard
> Console-proxy : Customized Standard (US) keyboard
> Guest : CentOS 6.5 , Debian 7 and FreeBSD 8
> Guest keymap : fr, fr-pc
> 
> 
> Thanks,
> 
> Axel Delahaye
> 
>

KVM - VM snapshot (round 2)

[Andrija Panic]

Hi guys,

still wondering is there any interest into imlementing the VM snapshoot for
KVM ?

We desperately need it, so will try to contribute anyway we can (not me
obviosuly, not a developer, but my colegues will).

Can you give some guidance on this subject - I'm aware of the design
documents here
https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots but any
more input would be very much appriciated.

I understand, that VMware/Xen natively support this, and that it might have
bigger user-base for Xen VS KVM - but this is one of the major KVM missing
features...

Any input greatly appreciated...

-- 

Andrija Panić

RE: KVM - VM snapshot (round 2)

[Vadim Kimlaychuk]

CS does not support memory snapshots for XenServer. Disk snapshots are working. 
Not sure about VmWare, but I guess it should be the same. I thought the 
reachest feature-set is developed for KVM. But if it does not support memory 
snapshots - I wonder wich hypervisor does it ? This option at user interface 
exists, but I didn't see it worked.

Vadim.


-Original Message-
From: Andrija Panic [mailto:andrija.pa...@gmail.com] 
Sent: Monday, December 08, 2014 12:51 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: KVM - VM snapshot (round 2)

Hi guys,

still wondering is there any interest into imlementing the VM snapshoot for KVM 
?

We desperately need it, so will try to contribute anyway we can (not me 
obviosuly, not a developer, but my colegues will).

Can you give some guidance on this subject - I'm aware of the design documents 
here https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots but 
any more input would be very much appriciated.

I understand, that VMware/Xen natively support this, and that it might have 
bigger user-base for Xen VS KVM - but this is one of the major KVM missing 
features...

Any input greatly appreciated...

-- 

Andrija Panić

Re: KVM - VM snapshot (round 2)

[Andrija Panic]

With KVM - I understand that there are 2 steps in general. 1) libvirts save
 - which saves memory of running VM to a file 2) qemu-img to snapshot
disks...

AS for the KVM VM snapshoting - my understanding is that the code is not
implemented at all, right ?

On 8 December 2014 at 12:11, Vadim Kimlaychuk 
wrote:

> CS does not support memory snapshots for XenServer. Disk snapshots are
> working. Not sure about VmWare, but I guess it should be the same. I
> thought the reachest feature-set is developed for KVM. But if it does not
> support memory snapshots - I wonder wich hypervisor does it ? This option
> at user interface exists, but I didn't see it worked.
>
> Vadim.
>
>
> -Original Message-
> From: Andrija Panic [mailto:andrija.pa...@gmail.com]
> Sent: Monday, December 08, 2014 12:51 PM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: KVM - VM snapshot (round 2)
>
> Hi guys,
>
> still wondering is there any interest into imlementing the VM snapshoot
> for KVM ?
>
> We desperately need it, so will try to contribute anyway we can (not me
> obviosuly, not a developer, but my colegues will).
>
> Can you give some guidance on this subject - I'm aware of the design
> documents here
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots but
> any more input would be very much appriciated.
>
> I understand, that VMware/Xen natively support this, and that it might
> have bigger user-base for Xen VS KVM - but this is one of the major KVM
> missing features...
>
> Any input greatly appreciated...
>
> --
>
> Andrija Panić
>



-- 

Andrija Panić

Re: Review Request 16973: Contrail Event Interceptor fix

[Daan Hoogland]

I spoke to the contrail guys at openstack summit last month. It seems
they have dropped their support for ACS.

On Fri, Dec 5, 2014 at 7:06 PM, Rohit Yadav  wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/16973/#review64027
> ---
>
>
> ping, any progress on this review?
>
> - Rohit Yadav
>
>
> On Jan. 21, 2014, 7:55 p.m., Suresh Balineni wrote:
>>
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/16973/
>> ---
>>
>> (Updated Jan. 21, 2014, 7:55 p.m.)
>>
>>
>> Review request for cloudstack.
>>
>>
>> Repository: cloudstack-git
>>
>>
>> Description
>> ---
>>
>> When project/domains are created,  our plugin code won't get invoked. Our 
>> contrail plugin uses Event infrastructure provided by cloudstack to receive 
>> these events and handle them accordingly. It is must to create 
>> domains/projects before creating a virtual network/vm object in contrail 
>> implementation. Hence our plugin must need a way to get notified about 
>> project/domain events.
>>
>>
>> Diffs
>> -
>>
>>   
>> plugins/network-elements/juniper-contrail/resources/META-INF/cloudstack/system/spring-contrail-system-context-inheritable.xml
>>  PRE-CREATION
>>   
>> plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/EventUtils.java
>>  dd18ca6
>>
>> Diff: https://reviews.apache.org/r/16973/diff/
>>
>>
>> Testing
>> ---
>>
>>
>> Thanks,
>>
>> Suresh Balineni
>>
>>
>



-- 
Daan

[GitHub] cloudstack pull request: Merge 4.5 to master

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/53#issuecomment-66103841
  
sure @runseb. I can help with that.
rebase master on noawsapi branch would required a force push. 
This is what I think we can do here is 
1. create a new branch from master (may be noawsapi-2)
2. merge noawsapi to the new branch noawsapi-2
3. (optional) delete noawsapi branch to avoid any confusion

do you guys see any issues with that approach?



---
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: CLOUDSTACK-7986 [F5 LB] Failed to execute...

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/47#issuecomment-66104188
  
missed adding a link to the pr in commit message
4.3: 7d17e95991035beeb802483a4b3d98df0dc9c8e8
4.4: c8882b39ec6ba84355a70c2f59f01a422e906b31
4.5 and master: 0347b2f5f333c38ed1395d31fe26b3d5f6a9d6ab


---
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: KVM - VM snapshot (round 2)

[Wei ZHOU]

As far as I know, KVM does support memory snapshot.
The shortcoming is libvirt-java supports only internal snapshot (not
external snapshots) for now.
In this case, the memory snapshot will be attached to the qcow2 file, and
the qcow2 will grow even after we remove the memory snapshot.

I've changed and tested on 4.2 before, but not pushed into production.

An email from the Mice, the developer of this functionality:
http://cloudstack.markmail.org/message/c3hkpxbad6ul4mza

-Wei

2014-12-08 12:11 GMT+01:00 Vadim Kimlaychuk :

> CS does not support memory snapshots for XenServer. Disk snapshots are
> working. Not sure about VmWare, but I guess it should be the same. I
> thought the reachest feature-set is developed for KVM. But if it does not
> support memory snapshots - I wonder wich hypervisor does it ? This option
> at user interface exists, but I didn't see it worked.
>
> Vadim.
>
>
> -Original Message-
> From: Andrija Panic [mailto:andrija.pa...@gmail.com]
> Sent: Monday, December 08, 2014 12:51 PM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: KVM - VM snapshot (round 2)
>
> Hi guys,
>
> still wondering is there any interest into imlementing the VM snapshoot
> for KVM ?
>
> We desperately need it, so will try to contribute anyway we can (not me
> obviosuly, not a developer, but my colegues will).
>
> Can you give some guidance on this subject - I'm aware of the design
> documents here
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots but
> any more input would be very much appriciated.
>
> I understand, that VMware/Xen natively support this, and that it might
> have bigger user-base for Xen VS KVM - but this is one of the major KVM
> missing features...
>
> Any input greatly appreciated...
>
> --
>
> Andrija Panić
>

[ACS45] release notes

[Daan Hoogland]

Pierre-Luc,

I see you mentioned an upgrade to java 1.7 as new in 4.5. 4.4 is java
1.7 as well.

-- 
Daan

Re: KVM - VM snapshot (round 2)

[Erik Weber]

On Mon, Dec 8, 2014 at 12:11 PM, Vadim Kimlaychuk  wrote:

> CS does not support memory snapshots for XenServer. Disk snapshots are
> working. Not sure about VmWare, but I guess it should be the same. I
> thought the reachest feature-set is developed for KVM. But if it does not
> support memory snapshots - I wonder wich hypervisor does it ? This option
> at user interface exists, but I didn't see it worked.
>
>

Both XenServer and VMware supports memory-snapshot and live migration with
CloudStack. And is one of the main reasons we chose XenServer over KVM.
Now if only XenServer would get Ceph-support I'd be happy ;-)

As for feature sets I find most hypervisors to support some good features
with CloudStack, but none to be perfect, ie. support all.

On that topic, does anyone know if there's an up to date feature matrix?

-- 
Erik

Re: KVM - VM snapshot (round 2)

[Andrija Panic]

Hm... I see that in XS 6.0.2 it was impossible to do memory snapshot unless
you had a licenced XS ? Is this still the case with XS 6.2 ?

On 8 December 2014 at 12:43, Erik Weber  wrote:

> On Mon, Dec 8, 2014 at 12:11 PM, Vadim Kimlaychuk <
> vadim.kimlayc...@elion.ee
> > wrote:
>
> > CS does not support memory snapshots for XenServer. Disk snapshots are
> > working. Not sure about VmWare, but I guess it should be the same. I
> > thought the reachest feature-set is developed for KVM. But if it does not
> > support memory snapshots - I wonder wich hypervisor does it ? This option
> > at user interface exists, but I didn't see it worked.
> >
> >
>
> Both XenServer and VMware supports memory-snapshot and live migration with
> CloudStack. And is one of the main reasons we chose XenServer over KVM.
> Now if only XenServer would get Ceph-support I'd be happy ;-)
>
> As for feature sets I find most hypervisors to support some good features
> with CloudStack, but none to be perfect, ie. support all.
>
> On that topic, does anyone know if there's an up to date feature matrix?
>
> --
> Erik
>



-- 

Andrija Panić

[proposal] Purge Volumes instead of deleting them

[Andrija Panic]

Anybody interested ?
https://issues.apache.org/jira/browse/CLOUDSTACK-7926

Best

-- 

Andrija Panić

Re: KVM - VM snapshot (round 2)

[Erik Weber]

Not that I know. I take VM snaphots all the time, and don't have XS
licenses.

-- 
Erik

On Mon, Dec 8, 2014 at 1:05 PM, Andrija Panic 
wrote:

> Hm... I see that in XS 6.0.2 it was impossible to do memory snapshot unless
> you had a licenced XS ? Is this still the case with XS 6.2 ?
>
> On 8 December 2014 at 12:43, Erik Weber  wrote:
>
> > On Mon, Dec 8, 2014 at 12:11 PM, Vadim Kimlaychuk <
> > vadim.kimlayc...@elion.ee
> > > wrote:
> >
> > > CS does not support memory snapshots for XenServer. Disk snapshots are
> > > working. Not sure about VmWare, but I guess it should be the same. I
> > > thought the reachest feature-set is developed for KVM. But if it does
> not
> > > support memory snapshots - I wonder wich hypervisor does it ? This
> option
> > > at user interface exists, but I didn't see it worked.
> > >
> > >
> >
> > Both XenServer and VMware supports memory-snapshot and live migration
> with
> > CloudStack. And is one of the main reasons we chose XenServer over KVM.
> > Now if only XenServer would get Ceph-support I'd be happy ;-)
> >
> > As for feature sets I find most hypervisors to support some good features
> > with CloudStack, but none to be perfect, ie. support all.
> >
> > On that topic, does anyone know if there's an up to date feature matrix?
> >
> > --
> > Erik
> >
>
>
>
> --
>
> Andrija Panić
>

Re: KVM - VM snapshot (round 2)

[Nux!]

Andrija,

No, 6.2 went fully free, no more restrictions. You can do disk and/or memory 
snapshots as much as you want, ACS supports it.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Andrija Panic" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 8 December, 2014 12:05:50
> Subject: Re: KVM - VM snapshot (round 2)

> Hm... I see that in XS 6.0.2 it was impossible to do memory snapshot unless
> you had a licenced XS ? Is this still the case with XS 6.2 ?
> 
> On 8 December 2014 at 12:43, Erik Weber  wrote:
> 
>> On Mon, Dec 8, 2014 at 12:11 PM, Vadim Kimlaychuk <
>> vadim.kimlayc...@elion.ee
>> > wrote:
>>
>> > CS does not support memory snapshots for XenServer. Disk snapshots are
>> > working. Not sure about VmWare, but I guess it should be the same. I
>> > thought the reachest feature-set is developed for KVM. But if it does not
>> > support memory snapshots - I wonder wich hypervisor does it ? This option
>> > at user interface exists, but I didn't see it worked.
>> >
>> >
>>
>> Both XenServer and VMware supports memory-snapshot and live migration with
>> CloudStack. And is one of the main reasons we chose XenServer over KVM.
>> Now if only XenServer would get Ceph-support I'd be happy ;-)
>>
>> As for feature sets I find most hypervisors to support some good features
>> with CloudStack, but none to be perfect, ie. support all.
>>
>> On that topic, does anyone know if there's an up to date feature matrix?
>>
>> --
>> Erik
>>
> 
> 
> 
> --
> 
> Andrija Panić

Cloudstack and Disaster Recovery

[Nux!]

Hi,

I'm getting more and more requests from customers to have "mini clouds" 
installed, but also DR capability.
This would be a great occasion to introduce them to Cloudstack, except for the 
DR bit for which I have found no straightforward way of performing. I'd have to 
replicate a whole lot of stuff to make it work.

Right now I'm stuck with setups of 3+ hypervisors running plain libvirt/KVM 
because of this; DR is a no-brainer, I'm just dumping xml metadata for VMs and 
rsync qcow2 files over SSH, making sure all the storage and networks pools are 
in place.

Pointers?

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

答复: Cloudstack and Disaster Recovery

[Star Guo]

Hi,

I think if you make nfs as primary storage backend on brtfs or zfs (freenas?) 
you could take a snapshot and send all to DR site. Also, a plan of increment 
snapshot.
This may be good method.

Best Regards,
Star Guo


-邮件原件-
发件人: Nux! [mailto:n...@li.nux.ro] 
发送时间: 2014年12月8日 20:34
收件人: dev@cloudstack.apache.org
主题: Cloudstack and Disaster Recovery

Hi,

I'm getting more and more requests from customers to have "mini clouds" 
installed, but also DR capability.
This would be a great occasion to introduce them to Cloudstack, except for the 
DR bit for which I have found no straightforward way of performing. I'd have to 
replicate a whole lot of stuff to make it work.

Right now I'm stuck with setups of 3+ hypervisors running plain libvirt/KVM 
because of this; DR is a no-brainer, I'm just dumping xml metadata for VMs and 
rsync qcow2 files over SSH, making sure all the storage and networks pools are 
in place.

Pointers?

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: 答复: Cloudstack and Disaster Recovery

[Nux!]

Thanks, but that is not my main problem. My difficulties are more like:

- how do I dump metadata for cloudstack KVM guests that are not running? virsh 
dumpxml will not work as the guests that are not running are not defined at all 
in libvirt (ie this will not list them: virsh list --all)

- how do I make sure the proper IPs and networks will be in place in the DR 
site? I'd need to recreate all the virtual networks and make sure there is a 
Virtual Router somehow working and still aware of IP assignments etc.

I know that ideally DR should be done at application levels, but it's not what 
the customers are asking. :-)

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Star Guo" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 8 December, 2014 12:51:13
> Subject: 答复: Cloudstack and Disaster Recovery

> Hi,
> 
> I think if you make nfs as primary storage backend on brtfs or zfs (freenas?)
> you could take a snapshot and send all to DR site. Also, a plan of increment
> snapshot.
> This may be good method.
> 
> Best Regards,
> Star Guo
> 
> 
> -邮件原件-
> 发件人: Nux! [mailto:n...@li.nux.ro]
> 发送时间: 2014年12月8日 20:34
> 收件人: dev@cloudstack.apache.org
> 主题: Cloudstack and Disaster Recovery
> 
> Hi,
> 
> I'm getting more and more requests from customers to have "mini clouds"
> installed, but also DR capability.
> This would be a great occasion to introduce them to Cloudstack, except for the
> DR bit for which I have found no straightforward way of performing. I'd have 
> to
> replicate a whole lot of stuff to make it work.
> 
> Right now I'm stuck with setups of 3+ hypervisors running plain libvirt/KVM
> because of this; DR is a no-brainer, I'm just dumping xml metadata for VMs and
> rsync qcow2 files over SSH, making sure all the storage and networks pools are
> in place.
> 
> Pointers?
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

Re: [ACS45] release notes

[Pierre-Luc Dion]

Hi Daan,

Yes, 1.7 java upgrade is from the RN of 4.4,  I'll remove 4.5 RN from RTD
since it's not completed yet.
Sorry about that.

PL


On Mon, Dec 8, 2014 at 6:47 AM, Daan Hoogland 
wrote:

> Pierre-Luc,
>
> I see you mentioned an upgrade to java 1.7 as new in 4.5. 4.4 is java
> 1.7 as well.
>
> --
> Daan
>

[ACS44] router upgrade issue

[Daan Hoogland]

H, I investigated an issue some colleagues noticed and it turns out
that in the update procedure the flag
VirtualNetworkApplianceService.MinVRVersion is not set for versions
4.4.0-4.4.2

I have no workaround other then rebooting the routers instead of
upgading/updating them. I will patch the branch to contain the correct
minimal version. The higher version branches have this var still set
to 4.3.0 as well.

-- 
Daan

Re: [ACS44] router upgrade issue

[Erik Weber]

This should probably happen in 4.5 branch as well I guess?

-- 
Erik

On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland 
wrote:

> H, I investigated an issue some colleagues noticed and it turns out
> that in the update procedure the flag
> VirtualNetworkApplianceService.MinVRVersion is not set for versions
> 4.4.0-4.4.2
>
> I have no workaround other then rebooting the routers instead of
> upgading/updating them. I will patch the branch to contain the correct
> minimal version. The higher version branches have this var still set
> to 4.3.0 as well.
>
> --
> Daan
>

Re: [ACS44] router upgrade issue

[Daan Hoogland]

I am looking if the value 4.4.1 is applicable there or whether it
should be higher, as we mail. will update you all.

On Mon, Dec 8, 2014 at 3:12 PM, Erik Weber  wrote:
> This should probably happen in 4.5 branch as well I guess?
>
> --
> Erik
>
> On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland 
> wrote:
>
>> H, I investigated an issue some colleagues noticed and it turns out
>> that in the update procedure the flag
>> VirtualNetworkApplianceService.MinVRVersion is not set for versions
>> 4.4.0-4.4.2
>>
>> I have no workaround other then rebooting the routers instead of
>> upgading/updating them. I will patch the branch to contain the correct
>> minimal version. The higher version branches have this var still set
>> to 4.3.0 as well.
>>
>> --
>> Daan
>>



-- 
Daan

Re: [ACS44] router upgrade issue

[Rohit Yadav]

In 4.3 it's defined as _minVRVersion. For each major ACS version such as ACS 
4.4.x, this value should be 4.4.0 unless we want to use higher templates such 
as 4.4.1 or 4.4.2.
For 4.5, it should be 4.5.0. This is assuming that ACS templates are compatible 
with future bugfix releases and we don't want to enforce templates upgrades 
unless necessary.

On Monday 08 December 2014 07:55 PM, Daan Hoogland wrote:

I am looking if the value 4.4.1 is applicable there or whether it
should be higher, as we mail. will update you all.

On Mon, Dec 8, 2014 at 3:12 PM, Erik Weber  wrote:
> This should probably happen in 4.5 branch as well I guess?
>
> --
> Erik
>
> On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland 
> wrote:
>
>> H, I investigated an issue some colleagues noticed and it turns out
>> that in the update procedure the flag
>> VirtualNetworkApplianceService.MinVRVersion is not set for versions
>> 4.4.0-4.4.2
>>
>> I have no workaround other then rebooting the routers instead of
>> upgading/updating them. I will patch the branch to contain the correct
>> minimal version. The higher version branches have this var still set
>> to 4.3.0 as well.
>>
>> --
>> Daan
>>





--
Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
PS. If you see any footer below, I did not add it :)

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

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
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: git commit: updated refs/heads/master to ca5c800

[Daan Hoogland]

Whei Zou, shouldn't this be in the systemvm64template dir mostly. I
think the 32bit one is no longer supported, really.

On Mon, Dec 8, 2014 at 3:29 PM,   wrote:
> Repository: cloudstack
> Updated Branches:
>   refs/heads/master f73ad2e8b -> ca5c800f8
>
>
> Fix CloudStack version (4.6.0) in systemvm template
>
>
> Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
> Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/ca5c800f
> Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/ca5c800f
> Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/ca5c800f
>
> Branch: refs/heads/master
> Commit: ca5c800f8d16d1f30fed1cba120bfb892eda9ca6
> Parents: f73ad2e
> Author: Wei Zhou 
> Authored: Mon Dec 8 15:26:56 2014 +0100
> Committer: Wei Zhou 
> Committed: Mon Dec 8 15:26:56 2014 +0100
>
> --
>  .../definitions/systemvmtemplate/configure_systemvm_services.sh| 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/ca5c800f/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> --
> diff --git 
> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh 
> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> index fc3d8f9..69612dc 100644
> --- 
> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> +++ 
> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> @@ -19,7 +19,7 @@
>  set -e
>  set -x
>
> -CLOUDSTACK_RELEASE=4.5.0
> +CLOUDSTACK_RELEASE=4.6.0
>
>  function configure_apache2() {
> # Enable ssl, rewrite and auth
>



-- 
Daan

Re: [ACS44] router upgrade issue

[Daan Hoogland]

Rohit, in 4.4 there was a problem with the templates in 4.4.0 so it
must be 4.4.1. I don't see the underscore but a capital M in
MinVRVersion in 4.4!

On Mon, Dec 8, 2014 at 3:31 PM, Rohit Yadav  wrote:
> In 4.3 it's defined as _minVRVersion. For each major ACS version such as ACS
> 4.4.x, this value should be 4.4.0 unless we want to use higher templates
> such as 4.4.1 or 4.4.2.
> For 4.5, it should be 4.5.0. This is assuming that ACS templates are
> compatible with future bugfix releases and we don't want to enforce
> templates upgrades unless necessary.
>
>
> On Monday 08 December 2014 07:55 PM, Daan Hoogland wrote:
>>
>> I am looking if the value 4.4.1 is applicable there or whether it
>> should be higher, as we mail. will update you all.
>>
>> On Mon, Dec 8, 2014 at 3:12 PM, Erik Weber  wrote:
>> > This should probably happen in 4.5 branch as well I guess?
>> >
>> > --
>> > Erik
>> >
>> > On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland 
>> > wrote:
>> >
>> >> H, I investigated an issue some colleagues noticed and it turns out
>> >> that in the update procedure the flag
>> >> VirtualNetworkApplianceService.MinVRVersion is not set for versions
>> >> 4.4.0-4.4.2
>> >>
>> >> I have no workaround other then rebooting the routers instead of
>> >> upgading/updating them. I will patch the branch to contain the correct
>> >> minimal version. The higher version branches have this var still set
>> >> to 4.3.0 as well.
>> >>
>> >> --
>> >> Daan
>> >>
>>
>>
>>
>
> --
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 8826230892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> PS. If you see any footer below, I did not add it :)
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design &
> Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software
> Engineering
> 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.



-- 
Daan

Re: [ACS44] router upgrade issue

[Daan Hoogland]

Also I don't think we need to let users go through a sysvm upgrade
procedure if it is not needed.

On Mon, Dec 8, 2014 at 3:34 PM, Daan Hoogland  wrote:
> Rohit, in 4.4 there was a problem with the templates in 4.4.0 so it
> must be 4.4.1. I don't see the underscore but a capital M in
> MinVRVersion in 4.4!
>
> On Mon, Dec 8, 2014 at 3:31 PM, Rohit Yadav  wrote:
>> In 4.3 it's defined as _minVRVersion. For each major ACS version such as ACS
>> 4.4.x, this value should be 4.4.0 unless we want to use higher templates
>> such as 4.4.1 or 4.4.2.
>> For 4.5, it should be 4.5.0. This is assuming that ACS templates are
>> compatible with future bugfix releases and we don't want to enforce
>> templates upgrades unless necessary.
>>
>>
>> On Monday 08 December 2014 07:55 PM, Daan Hoogland wrote:
>>>
>>> I am looking if the value 4.4.1 is applicable there or whether it
>>> should be higher, as we mail. will update you all.
>>>
>>> On Mon, Dec 8, 2014 at 3:12 PM, Erik Weber  wrote:
>>> > This should probably happen in 4.5 branch as well I guess?
>>> >
>>> > --
>>> > Erik
>>> >
>>> > On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland 
>>> > wrote:
>>> >
>>> >> H, I investigated an issue some colleagues noticed and it turns out
>>> >> that in the update procedure the flag
>>> >> VirtualNetworkApplianceService.MinVRVersion is not set for versions
>>> >> 4.4.0-4.4.2
>>> >>
>>> >> I have no workaround other then rebooting the routers instead of
>>> >> upgading/updating them. I will patch the branch to contain the correct
>>> >> minimal version. The higher version branches have this var still set
>>> >> to 4.3.0 as well.
>>> >>
>>> >> --
>>> >> Daan
>>> >>
>>>
>>>
>>>
>>
>> --
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 8826230892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>> PS. If you see any footer below, I did not add it :)
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design &
>> Build
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software
>> Engineering
>> 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.
>
>
>
> --
> Daan



-- 
Daan

Re: [ACS44] router upgrade issue

[Daan Hoogland]

I see some changes that make me want to put 4.5.0 in there for the 4.5
branch. proceding

On Mon, Dec 8, 2014 at 3:35 PM, Daan Hoogland  wrote:
> Also I don't think we need to let users go through a sysvm upgrade
> procedure if it is not needed.
>
> On Mon, Dec 8, 2014 at 3:34 PM, Daan Hoogland  wrote:
>> Rohit, in 4.4 there was a problem with the templates in 4.4.0 so it
>> must be 4.4.1. I don't see the underscore but a capital M in
>> MinVRVersion in 4.4!
>>
>> On Mon, Dec 8, 2014 at 3:31 PM, Rohit Yadav  
>> wrote:
>>> In 4.3 it's defined as _minVRVersion. For each major ACS version such as ACS
>>> 4.4.x, this value should be 4.4.0 unless we want to use higher templates
>>> such as 4.4.1 or 4.4.2.
>>> For 4.5, it should be 4.5.0. This is assuming that ACS templates are
>>> compatible with future bugfix releases and we don't want to enforce
>>> templates upgrades unless necessary.
>>>
>>>
>>> On Monday 08 December 2014 07:55 PM, Daan Hoogland wrote:

 I am looking if the value 4.4.1 is applicable there or whether it
 should be higher, as we mail. will update you all.

 On Mon, Dec 8, 2014 at 3:12 PM, Erik Weber  wrote:
 > This should probably happen in 4.5 branch as well I guess?
 >
 > --
 > Erik
 >
 > On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland 
 > wrote:
 >
 >> H, I investigated an issue some colleagues noticed and it turns out
 >> that in the update procedure the flag
 >> VirtualNetworkApplianceService.MinVRVersion is not set for versions
 >> 4.4.0-4.4.2
 >>
 >> I have no workaround other then rebooting the routers instead of
 >> upgading/updating them. I will patch the branch to contain the correct
 >> minimal version. The higher version branches have this var still set
 >> to 4.3.0 as well.
 >>
 >> --
 >> Daan
 >>



>>>
>>> --
>>> Regards,
>>> Rohit Yadav
>>> Software Architect, ShapeBlue
>>> M. +91 8826230892 | rohit.ya...@shapeblue.com
>>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>> PS. If you see any footer below, I did not add it :)
>>>
>>> Find out more about ShapeBlue and our range of CloudStack related services
>>>
>>> IaaS Cloud Design &
>>> Build
>>> CSForge – rapid IaaS deployment framework
>>> CloudStack Consulting
>>> CloudStack Software
>>> Engineering
>>> 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.
>>
>>
>>
>> --
>> Daan
>
>
>
> --
> Daan



-- 
Daan

Re: 4.5.0rc0 - available for testing.

[Pierre-Luc Dion]

few question about 4.5;

- which systemvm should we use? jenkins job build-systemvm-4.5 is a month
old.
- upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
false, although I've never succeed to upgrade a system so far.




On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion  wrote:

> The upgrade path require a systemvm-template otherwise the database
> upgrade fail, I've create this one: CLOUDSTACK-8041
>
> Could it be possible to just look for the latest template to exist during
> a db upgrade? with the current check, to upgrade from 4.2.1 require to have
> the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in order to
> successfully upgrade the database. is this something easy to fix?
>
>
>
>
> On Fri, Dec 5, 2014 at 8:53 PM, David Nalley  wrote:
>
>> Hi All,
>>
>> I've created a 4.5.0 release candidate, with the following artifacts
>> up for review:
>>
>> Git Branch and Commit SH:
>>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
>> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
>>
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
>>
>> PGP release keys (signed using A15F30B9):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> Because this is an early RC, I am not going to yet call a vote on it,
>> but rather going to let it set and let folks see if it's tenable.
>>
>> PLEASE test, and leave feedback in this thread.
>>
>> --David
>>
>
>
>
>

Re: 4.5.0rc0 - available for testing.

[Will Stevens]

We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to get the
system vms building again.  The building is currently broken because of a
compatibility issues.

This merge should be made asap...

Cheers,

*Will STEVENS*
Lead Developer

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

On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion  wrote:

> few question about 4.5;
>
> - which systemvm should we use? jenkins job build-systemvm-4.5 is a month
> old.
> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
> false, although I've never succeed to upgrade a system so far.
>
>
>
>
> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion 
> wrote:
>
> > The upgrade path require a systemvm-template otherwise the database
> > upgrade fail, I've create this one: CLOUDSTACK-8041
> >
> > Could it be possible to just look for the latest template to exist during
> > a db upgrade? with the current check, to upgrade from 4.2.1 require to
> have
> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in order to
> > successfully upgrade the database. is this something easy to fix?
> >
> >
> >
> >
> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley  wrote:
> >
> >> Hi All,
> >>
> >> I've created a 4.5.0 release candidate, with the following artifacts
> >> up for review:
> >>
> >> Git Branch and Commit SH:
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
> >>
> >>
> >> Source release (checksums and signatures are available at the same
> >> location):
> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
> >>
> >> PGP release keys (signed using A15F30B9):
> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>
> >> Because this is an early RC, I am not going to yet call a vote on it,
> >> but rather going to let it set and let folks see if it's tenable.
> >>
> >> PLEASE test, and leave feedback in this thread.
> >>
> >> --David
> >>
> >
> >
> >
> >
>

答复: 答复: Cloudstack and Disaster Recovery

[Star Guo]

I think if all the cloudstack network is behind a firewall ( a device setting 
DNAT+SNAT ) it may be easy to achieve the goal of DR.

Make all CS management (mysql) as a KVM instance which start with virsh, and 
backend btrfs, and make primary storage and secondary storage backend of other 
subvolume in btrfs.

And the DR site , you should prepare a physical host with brtfs, and the 
standby physical which install kvm agent (and the network) and set the 
configure file as same as the machine of 
production site (maybe fix the uuid in the cloud db of mysql) .

The last is backup firewall ( a device setting DNAT+SNAT ) configuration , 
while recovery the configuration to the same module device of the DR site ( 
RouterOS? ).

Then, the public IP of ISP, change the DANT IP and SNAT outbond IP ？ Fix DNS？

Best Regards,
Star Guo

-邮件原件-
发件人: Nux! [mailto:n...@li.nux.ro] 
发送时间: 2014年12月8日 21:14
收件人: dev@cloudstack.apache.org
主题: Re: 答复: Cloudstack and Disaster Recovery

Thanks, but that is not my main problem. My difficulties are more like:

- how do I dump metadata for cloudstack KVM guests that are not running? virsh 
dumpxml will not work as the guests that are not running are not defined at all 
in libvirt (ie this will not list them: virsh list --all)

- how do I make sure the proper IPs and networks will be in place in the DR 
site? I'd need to recreate all the virtual networks and make sure there is a 
Virtual Router somehow working and still aware of IP assignments etc.

I know that ideally DR should be done at application levels, but it's not what 
the customers are asking. :-)

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Star Guo" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 8 December, 2014 12:51:13
> Subject: 答复: Cloudstack and Disaster Recovery

> Hi,
> 
> I think if you make nfs as primary storage backend on brtfs or zfs 
> (freenas?) you could take a snapshot and send all to DR site. Also, a 
> plan of increment snapshot.
> This may be good method.
> 
> Best Regards,
> Star Guo
> 
> 
> -邮件原件-
> 发件人: Nux! [mailto:n...@li.nux.ro]
> 发送时间: 2014年12月8日 20:34
> 收件人: dev@cloudstack.apache.org
> 主题: Cloudstack and Disaster Recovery
> 
> Hi,
> 
> I'm getting more and more requests from customers to have "mini clouds"
> installed, but also DR capability.
> This would be a great occasion to introduce them to Cloudstack, except 
> for the DR bit for which I have found no straightforward way of 
> performing. I'd have to replicate a whole lot of stuff to make it work.
> 
> Right now I'm stuck with setups of 3+ hypervisors running plain 
> libvirt/KVM because of this; DR is a no-brainer, I'm just dumping xml 
> metadata for VMs and rsync qcow2 files over SSH, making sure all the 
> storage and networks pools are in place.
> 
> Pointers?
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

Re: git commit: updated refs/heads/master to ca5c800

[Wei ZHOU]

Daan,

system64template dir does not exist in master branch. It is strange.
I saw many commits on systemvmtemplate, but not on system64template.
Maybe we need to fix it.

-Wei


2014-12-08 15:32 GMT+01:00 Daan Hoogland :

> Whei Zou, shouldn't this be in the systemvm64template dir mostly. I
> think the 32bit one is no longer supported, really.
>
> On Mon, Dec 8, 2014 at 3:29 PM,   wrote:
> > Repository: cloudstack
> > Updated Branches:
> >   refs/heads/master f73ad2e8b -> ca5c800f8
> >
> >
> > Fix CloudStack version (4.6.0) in systemvm template
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
> > Commit:
> http://git-wip-us.apache.org/repos/asf/cloudstack/commit/ca5c800f
> > Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/ca5c800f
> > Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/ca5c800f
> >
> > Branch: refs/heads/master
> > Commit: ca5c800f8d16d1f30fed1cba120bfb892eda9ca6
> > Parents: f73ad2e
> > Author: Wei Zhou 
> > Authored: Mon Dec 8 15:26:56 2014 +0100
> > Committer: Wei Zhou 
> > Committed: Mon Dec 8 15:26:56 2014 +0100
> >
> > --
> >  .../definitions/systemvmtemplate/configure_systemvm_services.sh| 2
> +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > --
> >
> >
> >
> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/ca5c800f/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> > --
> > diff --git
> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> > index fc3d8f9..69612dc 100644
> > ---
> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> > +++
> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> > @@ -19,7 +19,7 @@
> >  set -e
> >  set -x
> >
> > -CLOUDSTACK_RELEASE=4.5.0
> > +CLOUDSTACK_RELEASE=4.6.0
> >
> >  function configure_apache2() {
> > # Enable ssl, rewrite and auth
> >
>
>
>
> --
> Daan
>

Re: git commit: updated refs/heads/master to ca5c800

[Daan Hoogland]

Ok, It might be someone deleted the 32bit dir and renamed the 64bit
dir. Makes sense if we no longer support 32bit. I have not been
spending enough time in the newer branches lately:(

On Mon, Dec 8, 2014 at 3:58 PM, Wei ZHOU  wrote:
> Daan,
>
> system64template dir does not exist in master branch. It is strange.
> I saw many commits on systemvmtemplate, but not on system64template.
> Maybe we need to fix it.
>
> -Wei
>
>
> 2014-12-08 15:32 GMT+01:00 Daan Hoogland :
>
>> Whei Zou, shouldn't this be in the systemvm64template dir mostly. I
>> think the 32bit one is no longer supported, really.
>>
>> On Mon, Dec 8, 2014 at 3:29 PM,   wrote:
>> > Repository: cloudstack
>> > Updated Branches:
>> >   refs/heads/master f73ad2e8b -> ca5c800f8
>> >
>> >
>> > Fix CloudStack version (4.6.0) in systemvm template
>> >
>> >
>> > Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
>> > Commit:
>> http://git-wip-us.apache.org/repos/asf/cloudstack/commit/ca5c800f
>> > Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/ca5c800f
>> > Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/ca5c800f
>> >
>> > Branch: refs/heads/master
>> > Commit: ca5c800f8d16d1f30fed1cba120bfb892eda9ca6
>> > Parents: f73ad2e
>> > Author: Wei Zhou 
>> > Authored: Mon Dec 8 15:26:56 2014 +0100
>> > Committer: Wei Zhou 
>> > Committed: Mon Dec 8 15:26:56 2014 +0100
>> >
>> > --
>> >  .../definitions/systemvmtemplate/configure_systemvm_services.sh| 2
>> +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> > --
>> >
>> >
>> >
>> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/ca5c800f/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
>> > --
>> > diff --git
>> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
>> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
>> > index fc3d8f9..69612dc 100644
>> > ---
>> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
>> > +++
>> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
>> > @@ -19,7 +19,7 @@
>> >  set -e
>> >  set -x
>> >
>> > -CLOUDSTACK_RELEASE=4.5.0
>> > +CLOUDSTACK_RELEASE=4.6.0
>> >
>> >  function configure_apache2() {
>> > # Enable ssl, rewrite and auth
>> >
>>
>>
>>
>> --
>> Daan
>>



-- 
Daan

Re: 答复: 答复: Cloudstack and Disaster Recovery

[Nux!]

Yeah, that's what I meant by "not straighforward". :-)

I'll stick with my libvirt/KVM setups for now.

Cheers

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Star Guo" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 8 December, 2014 14:56:21
> Subject: 答复: 答复: Cloudstack and Disaster Recovery

> I think if all the cloudstack network is behind a firewall ( a device setting
> DNAT+SNAT ) it may be easy to achieve the goal of DR.
> 
> Make all CS management (mysql) as a KVM instance which start with virsh, and
> backend btrfs, and make primary storage and secondary storage backend of other
> subvolume in btrfs.
> 
> And the DR site , you should prepare a physical host with brtfs, and the 
> standby
> physical which install kvm agent (and the network) and set the configure file
> as same as the machine of
> production site (maybe fix the uuid in the cloud db of mysql) .
> 
> The last is backup firewall ( a device setting DNAT+SNAT ) configuration , 
> while
> recovery the configuration to the same module device of the DR site ( 
> RouterOS?
> ).
> 
> Then, the public IP of ISP, change the DANT IP and SNAT outbond IP ？ Fix DNS？
> 
> Best Regards,
> Star Guo
> 
> -邮件原件-
> 发件人: Nux! [mailto:n...@li.nux.ro]
> 发送时间: 2014年12月8日 21:14
> 收件人: dev@cloudstack.apache.org
> 主题: Re: 答复: Cloudstack and Disaster Recovery
> 
> Thanks, but that is not my main problem. My difficulties are more like:
> 
> - how do I dump metadata for cloudstack KVM guests that are not running? virsh
> dumpxml will not work as the guests that are not running are not defined at 
> all
> in libvirt (ie this will not list them: virsh list --all)
> 
> - how do I make sure the proper IPs and networks will be in place in the DR
> site? I'd need to recreate all the virtual networks and make sure there is a
> Virtual Router somehow working and still aware of IP assignments etc.
> 
> I know that ideally DR should be done at application levels, but it's not what
> the customers are asking. :-)
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Star Guo" 
>> To: dev@cloudstack.apache.org
>> Sent: Monday, 8 December, 2014 12:51:13
>> Subject: 答复: Cloudstack and Disaster Recovery
> 
>> Hi,
>> 
>> I think if you make nfs as primary storage backend on brtfs or zfs
>> (freenas?) you could take a snapshot and send all to DR site. Also, a
>> plan of increment snapshot.
>> This may be good method.
>> 
>> Best Regards,
>> Star Guo
>> 
>> 
>> -邮件原件-
>> 发件人: Nux! [mailto:n...@li.nux.ro]
>> 发送时间: 2014年12月8日 20:34
>> 收件人: dev@cloudstack.apache.org
>> 主题: Cloudstack and Disaster Recovery
>> 
>> Hi,
>> 
>> I'm getting more and more requests from customers to have "mini clouds"
>> installed, but also DR capability.
>> This would be a great occasion to introduce them to Cloudstack, except
>> for the DR bit for which I have found no straightforward way of
>> performing. I'd have to replicate a whole lot of stuff to make it work.
>> 
>> Right now I'm stuck with setups of 3+ hypervisors running plain
>> libvirt/KVM because of this; DR is a no-brainer, I'm just dumping xml
>> metadata for VMs and rsync qcow2 files over SSH, making sure all the
>> storage and networks pools are in place.
>> 
>> Pointers?
>> 
>> Lucian
>> 
>> --
>> Sent from the Delta quadrant using Borg technology!
>> 
>> Nux!
> > www.nux.ro

Re: git commit: updated refs/heads/master to ca5c800

[Wei ZHOU]

I just checked it.
That is because Leo Simons made the changes for CLOUDSTACK-7143.
Nice!

2014-12-08 16:01 GMT+01:00 Daan Hoogland :

> Ok, It might be someone deleted the 32bit dir and renamed the 64bit
> dir. Makes sense if we no longer support 32bit. I have not been
> spending enough time in the newer branches lately:(
>
> On Mon, Dec 8, 2014 at 3:58 PM, Wei ZHOU  wrote:
> > Daan,
> >
> > system64template dir does not exist in master branch. It is strange.
> > I saw many commits on systemvmtemplate, but not on system64template.
> > Maybe we need to fix it.
> >
> > -Wei
> >
> >
> > 2014-12-08 15:32 GMT+01:00 Daan Hoogland :
> >
> >> Whei Zou, shouldn't this be in the systemvm64template dir mostly. I
> >> think the 32bit one is no longer supported, really.
> >>
> >> On Mon, Dec 8, 2014 at 3:29 PM,   wrote:
> >> > Repository: cloudstack
> >> > Updated Branches:
> >> >   refs/heads/master f73ad2e8b -> ca5c800f8
> >> >
> >> >
> >> > Fix CloudStack version (4.6.0) in systemvm template
> >> >
> >> >
> >> > Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
> >> > Commit:
> >> http://git-wip-us.apache.org/repos/asf/cloudstack/commit/ca5c800f
> >> > Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/ca5c800f
> >> > Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/ca5c800f
> >> >
> >> > Branch: refs/heads/master
> >> > Commit: ca5c800f8d16d1f30fed1cba120bfb892eda9ca6
> >> > Parents: f73ad2e
> >> > Author: Wei Zhou 
> >> > Authored: Mon Dec 8 15:26:56 2014 +0100
> >> > Committer: Wei Zhou 
> >> > Committed: Mon Dec 8 15:26:56 2014 +0100
> >> >
> >> > --
> >> >  .../definitions/systemvmtemplate/configure_systemvm_services.sh|
> 2
> >> +-
> >> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >> > --
> >> >
> >> >
> >> >
> >>
> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/ca5c800f/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> >> > --
> >> > diff --git
> >>
> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> >>
> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> >> > index fc3d8f9..69612dc 100644
> >> > ---
> >>
> a/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> >> > +++
> >>
> b/tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh
> >> > @@ -19,7 +19,7 @@
> >> >  set -e
> >> >  set -x
> >> >
> >> > -CLOUDSTACK_RELEASE=4.5.0
> >> > +CLOUDSTACK_RELEASE=4.6.0
> >> >
> >> >  function configure_apache2() {
> >> > # Enable ssl, rewrite and auth
> >> >
> >>
> >>
> >>
> >> --
> >> Daan
> >>
>
>
>
> --
> Daan
>

Re: 4.5.0rc0 - available for testing.

[Daan Hoogland]

lgtm,

do i look for a pull request, or just merge?

On Mon, Dec 8, 2014 at 3:46 PM, Will Stevens  wrote:
> We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to get the
> system vms building again.  The building is currently broken because of a
> compatibility issues.
>
> This merge should be made asap...
>
> Cheers,
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion  wrote:
>
>> few question about 4.5;
>>
>> - which systemvm should we use? jenkins job build-systemvm-4.5 is a month
>> old.
>> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
>> false, although I've never succeed to upgrade a system so far.
>>
>>
>>
>>
>> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion 
>> wrote:
>>
>> > The upgrade path require a systemvm-template otherwise the database
>> > upgrade fail, I've create this one: CLOUDSTACK-8041
>> >
>> > Could it be possible to just look for the latest template to exist during
>> > a db upgrade? with the current check, to upgrade from 4.2.1 require to
>> have
>> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in order to
>> > successfully upgrade the database. is this something easy to fix?
>> >
>> >
>> >
>> >
>> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley  wrote:
>> >
>> >> Hi All,
>> >>
>> >> I've created a 4.5.0 release candidate, with the following artifacts
>> >> up for review:
>> >>
>> >> Git Branch and Commit SH:
>> >>
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
>> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
>> >>
>> >>
>> >> Source release (checksums and signatures are available at the same
>> >> location):
>> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
>> >>
>> >> PGP release keys (signed using A15F30B9):
>> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >>
>> >> Because this is an early RC, I am not going to yet call a vote on it,
>> >> but rather going to let it set and let folks see if it's tenable.
>> >>
>> >> PLEASE test, and leave feedback in this thread.
>> >>
>> >> --David
>> >>
>> >
>> >
>> >
>> >
>>



-- 
Daan

Re: 4.5.0rc0 - available for testing.

[Will Stevens]

I am not hosting a public repo with the fix.  I think a merge is the
simplest way.  A pull request is great for non-committers to contribute,
but I think it is a bit disjointed for committers who already have access
to create fix branches.  Do you agree?

ws


*Will STEVENS*
Lead Developer

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

On Mon, Dec 8, 2014 at 10:37 AM, Daan Hoogland 
wrote:

> lgtm,
>
> do i look for a pull request, or just merge?
>
> On Mon, Dec 8, 2014 at 3:46 PM, Will Stevens 
> wrote:
> > We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to get
> the
> > system vms building again.  The building is currently broken because of a
> > compatibility issues.
> >
> > This merge should be made asap...
> >
> > Cheers,
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion 
> wrote:
> >
> >> few question about 4.5;
> >>
> >> - which systemvm should we use? jenkins job build-systemvm-4.5 is a
> month
> >> old.
> >> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
> >> false, although I've never succeed to upgrade a system so far.
> >>
> >>
> >>
> >>
> >> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion 
> >> wrote:
> >>
> >> > The upgrade path require a systemvm-template otherwise the database
> >> > upgrade fail, I've create this one: CLOUDSTACK-8041
> >> >
> >> > Could it be possible to just look for the latest template to exist
> during
> >> > a db upgrade? with the current check, to upgrade from 4.2.1 require to
> >> have
> >> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in order
> to
> >> > successfully upgrade the database. is this something easy to fix?
> >> >
> >> >
> >> >
> >> >
> >> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley  wrote:
> >> >
> >> >> Hi All,
> >> >>
> >> >> I've created a 4.5.0 release candidate, with the following artifacts
> >> >> up for review:
> >> >>
> >> >> Git Branch and Commit SH:
> >> >>
> >> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
> >> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
> >> >>
> >> >>
> >> >> Source release (checksums and signatures are available at the same
> >> >> location):
> >> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
> >> >>
> >> >> PGP release keys (signed using A15F30B9):
> >> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >> >>
> >> >> Because this is an early RC, I am not going to yet call a vote on it,
> >> >> but rather going to let it set and let folks see if it's tenable.
> >> >>
> >> >> PLEASE test, and leave feedback in this thread.
> >> >>
> >> >> --David
> >> >>
> >> >
> >> >
> >> >
> >> >
> >>
>
>
>
> --
> Daan
>

Re: CloudStack Quality Process

[Daan Hoogland]

When do we call the result of the doodle? wait for wednesday?

On Sat, Dec 6, 2014 at 5:46 PM, Chip Childers  wrote:
> Thanks for listening to my concerns folks...  and I'll be rooting for those
> of you that are "doing" to come up with some better practices for the
> community to adopt!
>
> On Fri, Dec 5, 2014 at 5:07 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
>> Agreed
>>
>> > -Original Message-
>> > From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
>> > Behalf Of Will Stevens
>> > Sent: Thursday, December 04, 2014 2:41 PM
>> > To: dev@cloudstack.apache.org
>> > Cc: Steve Wilson
>> > Subject: Re: CloudStack Quality Process
>> >
>> > I am speaking as a committer who has limited insight into the 'correct'
>> way to do
>> > this via Apache (so be gentle).  :)
>> >
>> > I like the idea of a wiki page to help get everyone on the same page and
>> to track
>> > the consensus as we move forward...
>> >
>> > I also agree that it is hard to come to a consensus on the list because
>> it is really
>> > hard to have a constructive conversation on here in a timely manner
>> where the
>> > different voices can be heard.
>> >
>> > I think it would be interesting to schedule sessions/meetings on the
>> list so any
>> > interested party can join.  These sessions/meetings would happen in a
>> format
>> > like IRC where the transcript of the session can be later posted to the
>> list as well
>> > as a summary of the transcript so it can be reviewed by any member who
>> could
>> > not make the meeting.  This way we keep all of the actual conversation
>> in the
>> > list, but we also make it easier to actually have a 'conversation' at
>> the same time.
>> > It is hard to beat real time when working through this sort of stuff.
>> >
>> > Does this make sense to others?  Thoughts?
>> >
>> > Will
>> >
>> >
>> > *Will STEVENS*
>> > Lead Developer
>> >
>> > *CloudOps* *| *Cloud Solutions Experts
>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw
>> > @CloudOps_
>> >
>> > On Thu, Dec 4, 2014 at 5:17 PM, Animesh Chaturvedi <
>> > animesh.chaturv...@citrix.com> wrote:
>> >
>> > > Wearing my PMC hat and with past experience on these discussions we
>> > > have not made much progress on mailing list despite agreeing on the
>> > > goals and have locked horns. One possibility after reading Chip's
>> > > email and concerns I see is that, we create a wiki outlining the
>> > > problem space, possible
>> > > solution(s) and their specific pros and cons and have people
>> collaborate.
>> > > Once a general consensus is there and wiki is stable we can bring it
>> > > back to the mailing list for final approval. This is open as well as
>> > > requires participant a higher degree of commitment to collaborate and
>> > > will be more structured.
>> > >
>> > > Thanks
>> > > Animesh
>> > >
>> > > > On Thu, Dec 4, 2014 at 7:24 PM, Chip Childers
>> > > > 
>> > > wrote:
>> > > > > Steve,
>> > > > >
>> > > > > (Speaking with my PMC hat on, but not as someone that has the time
>> > > > > to help with this process)
>> > > > >
>> > > > > I love the idea of moving forward with resolving some of the
>> > > > > quality process / tooling / etc... challenges that we face as a
>> > > > > project and community. I also love the idea that companies getting
>> > > > > commercial value from this project are talking (as companies)
>> > > > > about how to best support the project through either directing
>> > > > > their employees to work on this problem, allowing those interested
>> > > > > the time to do so, and / or offering (as Citrix did) required
>> > > > > hardware/software resources to make improvements for the common
>> > > > > good.  Importantly, I like that the companies involved are
>> > > > > mutually agreeing that this is for the common good.
>> > > > >
>> > > > > That said, I have a concern about the outline below, specifically
>> > > > > in how the definition of approach and eventual execution are
>> handled.
>> > > > > The proposal of taking this off-list until there is a "proposal to
>> > > ratify"
>> > > > > is what I'd like to see changed. I would fully expect that a
>> > > > > fleshed out proposal hitting the list would be met with more
>> > > > > discussion than you would like (and perhaps even met with
>> frustration).
>> > > > >
>> > > > > What has worked well for us in the past, where there is a need to
>> > > > > have those interested in "doing work" to be able to focus on that
>> > > > > work, has been to start with a call for interested parties (as you
>> > > > > did). Then, using a combination of threads on this list and "live"
>> > > > > meetings, make progress on defining the requirements and approach
>> > incrementally.
>> > > > > Execution of any work should similarly be open and shared on this
>> list.
>> > > > > Throughout that process, allowing comments and openings for
>> > > > > participants are critical.
>> > > > >
>> > > > > One of the things we learned about

Re: 4.5.0rc0 - available for testing.

[Daan Hoogland]

as a pragmatic programmer, yes. In light of the work we are starting
on wednesday, no. I leave picking the answer as an excercise to the
reader;)

On Mon, Dec 8, 2014 at 4:43 PM, Will Stevens  wrote:
> I am not hosting a public repo with the fix.  I think a merge is the
> simplest way.  A pull request is great for non-committers to contribute,
> but I think it is a bit disjointed for committers who already have access
> to create fix branches.  Do you agree?
>
> ws
>
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Mon, Dec 8, 2014 at 10:37 AM, Daan Hoogland 
> wrote:
>
>> lgtm,
>>
>> do i look for a pull request, or just merge?
>>
>> On Mon, Dec 8, 2014 at 3:46 PM, Will Stevens 
>> wrote:
>> > We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to get
>> the
>> > system vms building again.  The building is currently broken because of a
>> > compatibility issues.
>> >
>> > This merge should be made asap...
>> >
>> > Cheers,
>> >
>> > *Will STEVENS*
>> > Lead Developer
>> >
>> > *CloudOps* *| *Cloud Solutions Experts
>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> > w cloudops.com *|* tw @CloudOps_
>> >
>> > On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion 
>> wrote:
>> >
>> >> few question about 4.5;
>> >>
>> >> - which systemvm should we use? jenkins job build-systemvm-4.5 is a
>> month
>> >> old.
>> >> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
>> >> false, although I've never succeed to upgrade a system so far.
>> >>
>> >>
>> >>
>> >>
>> >> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion 
>> >> wrote:
>> >>
>> >> > The upgrade path require a systemvm-template otherwise the database
>> >> > upgrade fail, I've create this one: CLOUDSTACK-8041
>> >> >
>> >> > Could it be possible to just look for the latest template to exist
>> during
>> >> > a db upgrade? with the current check, to upgrade from 4.2.1 require to
>> >> have
>> >> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in order
>> to
>> >> > successfully upgrade the database. is this something easy to fix?
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley  wrote:
>> >> >
>> >> >> Hi All,
>> >> >>
>> >> >> I've created a 4.5.0 release candidate, with the following artifacts
>> >> >> up for review:
>> >> >>
>> >> >> Git Branch and Commit SH:
>> >> >>
>> >> >>
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
>> >> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
>> >> >>
>> >> >>
>> >> >> Source release (checksums and signatures are available at the same
>> >> >> location):
>> >> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
>> >> >>
>> >> >> PGP release keys (signed using A15F30B9):
>> >> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >> >>
>> >> >> Because this is an early RC, I am not going to yet call a vote on it,
>> >> >> but rather going to let it set and let folks see if it's tenable.
>> >> >>
>> >> >> PLEASE test, and leave feedback in this thread.
>> >> >>
>> >> >> --David
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>>
>>
>>
>> --
>> Daan
>>



-- 
Daan

[GitHub] cloudstack pull request: Ovmsupport

[snuf]

Github user snuf commented on the pull request:

https://github.com/apache/cloudstack/pull/9#issuecomment-66134697
  
Hi Rohit,

Well there are a couple of things here:

1st: I work on a fork and pull in upstream master and merge that into 
ovmsupport (https://github.com/snuf/cloudstack/tree/ovmsupport) so in principle 
that makes the ovmsupport tree aligned with master including my patches.
2nd: Test coverage on part of the code is 81% (the object branch, 
supportive translation layer to communicate with Ovm3) and on part not where I 
want it to be (the hypervisor branch, where integration with Cloudstack lives).
3rd: It works within the boundaries of the feature design doc on wiki, 
which means all basic stuff works but some features can not be provided as Ovm3 
doesn’t support them with the storage backend (running snapshots for example).
4th: The systemvm.img that’s generated from buildsystemvm.sh is a raw 
image so can be used for the systemvms for Ovm3.

Does this answer your question ? I genuinely think there should be some 
coverage for the integration layer into Cloudstack which is kind of absent?

Cheers,

Funs

On 06 Dec 2014, at 14:02, Rohit Yadav  wrote:

> That's great Funs. I see it's already passing smoke tests on TravisCI so 
we can merge it on master whenever you advise? If it's functionally working 
with good enough coverage and tests I would say go ahead and merge it on master 
right away.
> 
> —
> Reply to this email directly or view it on GitHub.
> 


---
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: 4.5.0rc0 - available for testing.

[Will Stevens]

Fair enough.  :)  Just merge the branch this time and we will figure out
the details going forward.  I think reducing the work for the person doing
the merge will help collaboration (even if the committer has to do a bit
more work), so I am open to how we do this...

ws


*Will STEVENS*
Lead Developer

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

On Mon, Dec 8, 2014 at 10:46 AM, Daan Hoogland 
wrote:

> as a pragmatic programmer, yes. In light of the work we are starting
> on wednesday, no. I leave picking the answer as an excercise to the
> reader;)
>
> On Mon, Dec 8, 2014 at 4:43 PM, Will Stevens 
> wrote:
> > I am not hosting a public repo with the fix.  I think a merge is the
> > simplest way.  A pull request is great for non-committers to contribute,
> > but I think it is a bit disjointed for committers who already have access
> > to create fix branches.  Do you agree?
> >
> > ws
> >
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Mon, Dec 8, 2014 at 10:37 AM, Daan Hoogland 
> > wrote:
> >
> >> lgtm,
> >>
> >> do i look for a pull request, or just merge?
> >>
> >> On Mon, Dec 8, 2014 at 3:46 PM, Will Stevens 
> >> wrote:
> >> > We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to
> get
> >> the
> >> > system vms building again.  The building is currently broken because
> of a
> >> > compatibility issues.
> >> >
> >> > This merge should be made asap...
> >> >
> >> > Cheers,
> >> >
> >> > *Will STEVENS*
> >> > Lead Developer
> >> >
> >> > *CloudOps* *| *Cloud Solutions Experts
> >> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >> > w cloudops.com *|* tw @CloudOps_
> >> >
> >> > On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion 
> >> wrote:
> >> >
> >> >> few question about 4.5;
> >> >>
> >> >> - which systemvm should we use? jenkins job build-systemvm-4.5 is a
> >> month
> >> >> old.
> >> >> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
> >> >> false, although I've never succeed to upgrade a system so far.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion  >
> >> >> wrote:
> >> >>
> >> >> > The upgrade path require a systemvm-template otherwise the database
> >> >> > upgrade fail, I've create this one: CLOUDSTACK-8041
> >> >> >
> >> >> > Could it be possible to just look for the latest template to exist
> >> during
> >> >> > a db upgrade? with the current check, to upgrade from 4.2.1
> require to
> >> >> have
> >> >> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in
> order
> >> to
> >> >> > successfully upgrade the database. is this something easy to fix?
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley 
> wrote:
> >> >> >
> >> >> >> Hi All,
> >> >> >>
> >> >> >> I've created a 4.5.0 release candidate, with the following
> artifacts
> >> >> >> up for review:
> >> >> >>
> >> >> >> Git Branch and Commit SH:
> >> >> >>
> >> >> >>
> >> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
> >> >> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
> >> >> >>
> >> >> >>
> >> >> >> Source release (checksums and signatures are available at the same
> >> >> >> location):
> >> >> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
> >> >> >>
> >> >> >> PGP release keys (signed using A15F30B9):
> >> >> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >> >> >>
> >> >> >> Because this is an early RC, I am not going to yet call a vote on
> it,
> >> >> >> but rather going to let it set and let folks see if it's tenable.
> >> >> >>
> >> >> >> PLEASE test, and leave feedback in this thread.
> >> >> >>
> >> >> >> --David
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >>
> >>
> >>
> >> --
> >> Daan
> >>
>
>
>
> --
> Daan
>

Re: 4.5.0rc0 - available for testing.

[Daan Hoogland]

merged

On Mon, Dec 8, 2014 at 4:46 PM, Daan Hoogland  wrote:
> as a pragmatic programmer, yes. In light of the work we are starting
> on wednesday, no. I leave picking the answer as an excercise to the
> reader;)
>
> On Mon, Dec 8, 2014 at 4:43 PM, Will Stevens  wrote:
>> I am not hosting a public repo with the fix.  I think a merge is the
>> simplest way.  A pull request is great for non-committers to contribute,
>> but I think it is a bit disjointed for committers who already have access
>> to create fix branches.  Do you agree?
>>
>> ws
>>
>>
>> *Will STEVENS*
>> Lead Developer
>>
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>>
>> On Mon, Dec 8, 2014 at 10:37 AM, Daan Hoogland 
>> wrote:
>>
>>> lgtm,
>>>
>>> do i look for a pull request, or just merge?
>>>
>>> On Mon, Dec 8, 2014 at 3:46 PM, Will Stevens 
>>> wrote:
>>> > We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to get
>>> the
>>> > system vms building again.  The building is currently broken because of a
>>> > compatibility issues.
>>> >
>>> > This merge should be made asap...
>>> >
>>> > Cheers,
>>> >
>>> > *Will STEVENS*
>>> > Lead Developer
>>> >
>>> > *CloudOps* *| *Cloud Solutions Experts
>>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>>> > w cloudops.com *|* tw @CloudOps_
>>> >
>>> > On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion 
>>> wrote:
>>> >
>>> >> few question about 4.5;
>>> >>
>>> >> - which systemvm should we use? jenkins job build-systemvm-4.5 is a
>>> month
>>> >> old.
>>> >> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
>>> >> false, although I've never succeed to upgrade a system so far.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion 
>>> >> wrote:
>>> >>
>>> >> > The upgrade path require a systemvm-template otherwise the database
>>> >> > upgrade fail, I've create this one: CLOUDSTACK-8041
>>> >> >
>>> >> > Could it be possible to just look for the latest template to exist
>>> during
>>> >> > a db upgrade? with the current check, to upgrade from 4.2.1 require to
>>> >> have
>>> >> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in order
>>> to
>>> >> > successfully upgrade the database. is this something easy to fix?
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley  wrote:
>>> >> >
>>> >> >> Hi All,
>>> >> >>
>>> >> >> I've created a 4.5.0 release candidate, with the following artifacts
>>> >> >> up for review:
>>> >> >>
>>> >> >> Git Branch and Commit SH:
>>> >> >>
>>> >> >>
>>> >>
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
>>> >> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
>>> >> >>
>>> >> >>
>>> >> >> Source release (checksums and signatures are available at the same
>>> >> >> location):
>>> >> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
>>> >> >>
>>> >> >> PGP release keys (signed using A15F30B9):
>>> >> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>> >> >>
>>> >> >> Because this is an early RC, I am not going to yet call a vote on it,
>>> >> >> but rather going to let it set and let folks see if it's tenable.
>>> >> >>
>>> >> >> PLEASE test, and leave feedback in this thread.
>>> >> >>
>>> >> >> --David
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>>
>>>
>>>
>>> --
>>> Daan
>>>
>
>
>
> --
> Daan



-- 
Daan

Re: 4.5.0rc0 - available for testing.

[Will Stevens]

Thank you.  I have kicked off a system vm build to make sure everything is
working correctly.  Lots of things in the queue though, so it may take a
while.

ws


*Will STEVENS*
Lead Developer

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

On Mon, Dec 8, 2014 at 10:49 AM, Daan Hoogland 
wrote:

> merged
>
> On Mon, Dec 8, 2014 at 4:46 PM, Daan Hoogland 
> wrote:
> > as a pragmatic programmer, yes. In light of the work we are starting
> > on wednesday, no. I leave picking the answer as an excercise to the
> > reader;)
> >
> > On Mon, Dec 8, 2014 at 4:43 PM, Will Stevens 
> wrote:
> >> I am not hosting a public repo with the fix.  I think a merge is the
> >> simplest way.  A pull request is great for non-committers to contribute,
> >> but I think it is a bit disjointed for committers who already have
> access
> >> to create fix branches.  Do you agree?
> >>
> >> ws
> >>
> >>
> >> *Will STEVENS*
> >> Lead Developer
> >>
> >> *CloudOps* *| *Cloud Solutions Experts
> >> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >> w cloudops.com *|* tw @CloudOps_
> >>
> >> On Mon, Dec 8, 2014 at 10:37 AM, Daan Hoogland  >
> >> wrote:
> >>
> >>> lgtm,
> >>>
> >>> do i look for a pull request, or just merge?
> >>>
> >>> On Mon, Dec 8, 2014 at 3:46 PM, Will Stevens 
> >>> wrote:
> >>> > We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to
> get
> >>> the
> >>> > system vms building again.  The building is currently broken because
> of a
> >>> > compatibility issues.
> >>> >
> >>> > This merge should be made asap...
> >>> >
> >>> > Cheers,
> >>> >
> >>> > *Will STEVENS*
> >>> > Lead Developer
> >>> >
> >>> > *CloudOps* *| *Cloud Solutions Experts
> >>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >>> > w cloudops.com *|* tw @CloudOps_
> >>> >
> >>> > On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion  >
> >>> wrote:
> >>> >
> >>> >> few question about 4.5;
> >>> >>
> >>> >> - which systemvm should we use? jenkins job build-systemvm-4.5 is a
> >>> month
> >>> >> old.
> >>> >> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
> >>> >> false, although I've never succeed to upgrade a system so far.
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion <
> pd...@cloudops.com>
> >>> >> wrote:
> >>> >>
> >>> >> > The upgrade path require a systemvm-template otherwise the
> database
> >>> >> > upgrade fail, I've create this one: CLOUDSTACK-8041
> >>> >> >
> >>> >> > Could it be possible to just look for the latest template to exist
> >>> during
> >>> >> > a db upgrade? with the current check, to upgrade from 4.2.1
> require to
> >>> >> have
> >>> >> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in
> order
> >>> to
> >>> >> > successfully upgrade the database. is this something easy to fix?
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley 
> wrote:
> >>> >> >
> >>> >> >> Hi All,
> >>> >> >>
> >>> >> >> I've created a 4.5.0 release candidate, with the following
> artifacts
> >>> >> >> up for review:
> >>> >> >>
> >>> >> >> Git Branch and Commit SH:
> >>> >> >>
> >>> >> >>
> >>> >>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
> >>> >> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
> >>> >> >>
> >>> >> >>
> >>> >> >> Source release (checksums and signatures are available at the
> same
> >>> >> >> location):
> >>> >> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
> >>> >> >>
> >>> >> >> PGP release keys (signed using A15F30B9):
> >>> >> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>> >> >>
> >>> >> >> Because this is an early RC, I am not going to yet call a vote
> on it,
> >>> >> >> but rather going to let it set and let folks see if it's tenable.
> >>> >> >>
> >>> >> >> PLEASE test, and leave feedback in this thread.
> >>> >> >>
> >>> >> >> --David
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >>
> >>>
> >>>
> >>>
> >>> --
> >>> Daan
> >>>
> >
> >
> >
> > --
> > Daan
>
>
>
> --
> Daan
>

Re: Review Request 19995: VM Userdata field at GUI VM creation

[Axel Delahaye]

> On déc. 5, 2014, 9:43 après-midi, Pierre-Luc Dion wrote:
> > Does the feature include the capability to update or change userdata once 
> > the VM is created?

No, it is an optional textarea in the instanceWizard


- Axel


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


On déc. 5, 2014, 5:56 après-midi, Jean-Francois Vincent wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19995/
> ---
> 
> (Updated déc. 5, 2014, 5:56 après-midi)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> VM creation user interface : added the Userdata field
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties 8abe874 
>   ui/index.jsp 4910b9f 
>   ui/scripts/instanceWizard.js c2d3030 
> 
> Diff: https://reviews.apache.org/r/19995/diff/
> 
> 
> Testing
> ---
> 
> tested done on 4.2.1. This patch was adapted for last master branch.
> 
> 
> Thanks,
> 
> Jean-Francois Vincent
> 
>

Re: Review Request 19995: VM Userdata field at GUI VM creation

[Axel Delahaye]

> On déc. 5, 2014, 5:55 après-midi, Rohit Yadav wrote:
> > Interesting feature, can you send another patch that applies cleanly on 
> > master? I'll add known UI contributors who may help review your patch.

I have the new diff but I can't upload it for J.F. Vincent


- Axel


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


On déc. 5, 2014, 5:56 après-midi, Jean-Francois Vincent wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19995/
> ---
> 
> (Updated déc. 5, 2014, 5:56 après-midi)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> VM creation user interface : added the Userdata field
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties 8abe874 
>   ui/index.jsp 4910b9f 
>   ui/scripts/instanceWizard.js c2d3030 
> 
> Diff: https://reviews.apache.org/r/19995/diff/
> 
> 
> Testing
> ---
> 
> tested done on 4.2.1. This patch was adapted for last master branch.
> 
> 
> Thanks,
> 
> Jean-Francois Vincent
> 
>

[DISCUSS] Issues with Ubuntu instance creation

[Tim Mackey]

I've been working through a series of issues getting Ubuntu 12.04 LTS
templates to provision correctly, and I *think* most are really doc issues,
but before I run off and update docs I wanted to confirm that I'm doing the
right thing.  Here's my list of issues, and what I did to get past my
"issue".  My documentation source is:
http://cloudstack-administration.readthedocs.org/en/latest/templates.html.
My CloudStack is 4.4.

1. The docs make no mention of an Ubuntu change password script, and Google
returns Shankar's GitHub scripts as option #4.  Unfortunately, that script
has a user of "ubuntu" hardcoded into it, so unless your template has an
"ubuntu" user, its not going to work.  I haven't tried to use the stock
CloudStack password change script in my template, but have found references
to it not working as expected.  For my purposes, I changed Shankar's script
to use a "root" user, but this leaves the following questions open:

- Does the current CloudStack script work with Ubuntu 12.04 and later?  If
so, I vote the docs be updated to reflect support for Ubuntu 12.04 and
later; with the objective of both clarifying the docs and helping boost our
docs to a higher rank than Shankar's GitHub.

- If the current CloudStack script doesn't work with Ubuntu 12.04 LTS,
should a JIRA ticket be entered to resolve this, or should we have multiple
scripts available and effectively incorporate Shankar's work more
officially?

2. The docs recommend setting the password to expire, but when the change
password script runs, that flag is cleared and the user isn't promoted to
reset the root password.  That leaves the following question in my mind.

- Is our password intended to be a one-time use password.  If so, then the
password change script should reset expiration forcing a new one to be
set.  If not, then should we not remove the "expire password"
recommendation from the docs?

3. The script in the docs covering clearing the logs (step 6) doesn't
include clearing syslog.  Recommend updating the script to include:  cat
/dev/null > /var/log/syslog 2>/dev/null

4. The script in the docs covering clearing of command history (step 9)
doesn't clear the in memory history.  Recommend updating the script to
become:  cat /dev/null > ~/.bash_history && history -c && unset HISTFILE &&
halt -p.  This would also remove the the shutdown step (step 10).

5. The script to set the hostname has a race condition which effectively
means it rarely sets the hostname correctly on initial boot.  I've attached
the script I used.  It doesn't depend upon the leases file being present,
and took care of some alternate "blank" hostname cases I encountered while
debugging.

I'm happy to update the docs, but want to make certain what I've
encountered as issues are things we care about updating.

-tim

jenkins.buildacloud.org

[Will Stevens]

Has something happened to http://jenkins.buildacloud.org/ recently?

We have not had a successful build in 3 days and the queue is growing but
there does not seem to be any build slaves in action handling the
workload.  Is this an expected outage?

Cheers,

*Will STEVENS*
Lead Developer

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

Re: Review Request 19995: VM Userdata field at GUI VM creation

[Rohit Yadav]

> On Dec. 5, 2014, 5:55 p.m., Rohit Yadav wrote:
> > Interesting feature, can you send another patch that applies cleanly on 
> > master? I'll add known UI contributors who may help review your patch.
> 
> Axel Delahaye wrote:
> I have the new diff but I can't upload it for J.F. Vincent

Send it separetely, Github PR on github.com/apache/cloudstack (Github is more 
fun that ReviewBoard), I see you both have atos.net in email (assuming you're 
both colleagues).
Once we've that PR we can close this review request.


- Rohit


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


On Dec. 5, 2014, 5:56 p.m., Jean-Francois Vincent wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19995/
> ---
> 
> (Updated Dec. 5, 2014, 5:56 p.m.)
> 
> 
> Review request for cloudstack, Brian Federle and Jessica Wang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> VM creation user interface : added the Userdata field
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties 8abe874 
>   ui/index.jsp 4910b9f 
>   ui/scripts/instanceWizard.js c2d3030 
> 
> Diff: https://reviews.apache.org/r/19995/diff/
> 
> 
> Testing
> ---
> 
> tested done on 4.2.1. This patch was adapted for last master branch.
> 
> 
> Thanks,
> 
> Jean-Francois Vincent
> 
>

[ACS 4.3] Snapshots on secondary storage

[benoit lair]

Hello Folks,


My environment is ACS 4.3.0 with xenservers 6.2.0

When taking snapshots, there are stocked in the primary storage (supposing
calling native xenservers apis).

In my remembers i have already seen (with xenservers) snapshots stocked on
secondary storage.

How can i achieve this ?

My zone is an advanced one without sg, and there are two networks, one for
management, the other for the guest vlans (so no storage reserved physical
network).

Thanks a lot for your responses.

Regards, Benoit.

Re: jenkins.buildacloud.org

[Rohit Yadav]

On Monday 08 December 2014 09:49 PM, Will Stevens wrote:

Has something happened to http://jenkins.buildacloud.org/ recently?

We have not had a successful build in 3 days and the queue is growing but
there does not seem to be any build slaves in action handling the
workload.  Is this an expected outage?


The master is out of disk space (and probably few slaves too). I tried
to raise this but I don't have access to the master server to try and
fix this.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 8826230892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
PS. If you see any footer below, I did not add it :)
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
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: [ACS 4.3] Snapshots on secondary storage

[Nux!]

I think you need to take VOLUME snapshots for them to be stored on the SS.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "benoit lair" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 8 December, 2014 16:57:34
> Subject: [ACS 4.3] Snapshots on secondary storage

> Hello Folks,
> 
> 
> My environment is ACS 4.3.0 with xenservers 6.2.0
> 
> When taking snapshots, there are stocked in the primary storage (supposing
> calling native xenservers apis).
> 
> In my remembers i have already seen (with xenservers) snapshots stocked on
> secondary storage.
> 
> How can i achieve this ?
> 
> My zone is an advanced one without sg, and there are two networks, one for
> management, the other for the guest vlans (so no storage reserved physical
> network).
> 
> Thanks a lot for your responses.
> 
> Regards, Benoit.

Re: jenkins.buildacloud.org

[Erik Weber]

Also raised the issue a few days ago.

Hugo seemed awfully busy.

Erik

Den mandag 8. desember 2014 skrev Rohit Yadav 
følgende:

>
>
> On Monday 08 December 2014 09:49 PM, Will Stevens wrote:
>
>> Has something happened to http://jenkins.buildacloud.org/ recently?
>>
>> We have not had a successful build in 3 days and the queue is growing but
>> there does not seem to be any build slaves in action handling the
>> workload.  Is this an expected outage?
>>
>
> The master is out of disk space (and probably few slaves too). I tried
> to raise this but I don't have access to the master server to try and
> fix this.
>
>
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 8826230892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> PS. If you see any footer below, I did not add it :)
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering engineering/>
> CloudStack Infrastructure Support cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses 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.
>

Jenkins build is back to normal : cloudstack-4.3-maven-build #671

[jenkins]

See 

Jenkins build is back to normal : build-4.5 #211

[jenkins]

See 

[GitHub] cloudstack pull request: make the VPN feature work more reliable a...

[remibergsma]

GitHub user remibergsma opened a pull request:

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

make the VPN feature work more reliable and secure

At Schuberg Philis we wanted to use the VPN feature, but found it hard to 
make it work in a reliable way. When we dove into it, we found some bugs and 
problems that we solved along the way. Since this change, the VPN connections 
are created and destroyed as expected. Also, we tightened the iptable rules to 
make it more secure.

The patched ipsectunnel.sh script works fine in our tests on 4.4, 4.5 and 
4.6. Possibly also on 4.3.x when the fix for CLOUDSTACK-5501 is merged.

Also, after rebooting a VPC the VPN connection reconnected as one would 
expect.

We tested this change by using the shell script below (based on 
CloudMonkey). The script will create a VPN connection between each VPN customer 
gateway it finds, like in a mesh network. 

Regards,
Remi Bergsma / Funs Kessen

#!/bin/bash
vpncustgws=`cloudmonkey list vpncustomergateways | grep ^id | awk ' { print 
$3 }'`
vpngws=`cloudmonkey list vpngateways | grep ^id | awk ' { print $3 }'`
for vpngw in $vpngws
do
   pubip=`cloudmonkey list vpngateways id=$vpngw | grep ^publicip | awk 
'{print $3}'`
   echo "dealing with $vpngw, $pubip"
   for vpncustgw in $vpncustgws
   do 
   custgw=`cloudmonkey list vpncustomergateways id=$vpncustgw | grep 
^gateway | awk '{print $3}'`
   if [ $custgw == $pubip ]
   then
   echo "$pubip is me, $vpncustgw, $custgw, $vpngw!"
   else
   echo "creating vpn: $custgw, $pubip"
   echo "cloudmonkey create vpnconnection 
s2scustomergatewayid=$vpncustgw s2svpngatewayid=$vpngw"
   fi
   done
done

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

$ git pull https://github.com/remibergsma/cloudstack master

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

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

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

This closes #54


commit 8b412ce194eaf195dc77531379687de43e14a088
Author: Remi Bergsma 
Date:   2014-12-08T17:53:18Z

remove biglock usage from ipsectunnel.sh

Biglock breaks creating VPN's when other scripts run at the
same time that also use the same biglock. These other scripts
do nothing that could harm our deployment and even multiple
vpn's can safely be created simultaniously.

commit 8b2563a216b012ab1905e65f446c8b6b1435b983
Author: Remi Bergsma 
Date:   2014-12-08T17:54:27Z

renamed $leftgw to $leftnexthop to make clear what it does

commit b95addd3efb45f61b129584ade49bad7bbaa16f8
Author: Remi Bergsma 
Date:   2014-12-08T17:55:35Z

starting the tunnel will make it keep trying until it connects

Changed 'auto=add' to 'auto=start' to make sure the tunnel starts.
When both sides are there they will connect. This resolves the
issue that there is only a small time frame in which the VPN
would connect.

commit f8d718e3e31ad517969663d24647fcbd9b50cc3d
Author: Remi Bergsma 
Date:   2014-12-08T17:59:16Z

add a flag -c whether or not to check the VPN on create

Changed default to no, as the other side may not be up yet.
If this check fails, the VPN enters Error state and will not
work. It's safe to just let it connect on its own so it will
connect when it can.

commit 7f33f7c3969d3b217ad6977f01bb487ebeee665d
Author: Remi Bergsma 
Date:   2014-12-08T18:00:59Z

prevent CloudStack from removing the VPN connection

If connecting the VPN takes some time, for example because
the other end is not (yet) up, CloudStack will delete
the VPN because the ipsectunnel.sh does not return in time.
The VPN connection then enters the Error state.

This change makes sure ipsectunnel.sh returns in time,
and lets ipsec connect in the background. If it all fails,
the connection enters Disconnected.

commit ef3b4bb4e3342f166489034fa7149540d2ef1383
Author: Remi Bergsma 
Date:   2014-12-08T18:06:55Z

made iptables for the VPN connection more secure

Added destination and source definition. Flag -S can be used
to ignore this. It's the new default as it is more secure
and does not impact the way things work (backwords compatible).




---
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: jenkins.buildacloud.org

[Hugo Trippaers]

Heya,

Restarted Jenkins after cleaning up some space. Hopefully this will keep 
Jenkins running for a couple of days.

When i have some more time i’ll try and think of a more permanent solution. 

@David, would it be possible to add an extra disk to this box? A 100Gb disk 
would go a long way.


Cheers,
Hugo


> On 8 dec. 2014, at 17:30, Erik Weber  wrote:
> 
> Also raised the issue a few days ago.
> 
> Hugo seemed awfully busy.
> 
> Erik
> 
> Den mandag 8. desember 2014 skrev Rohit Yadav 
> følgende:
> 
>> 
>> 
>> On Monday 08 December 2014 09:49 PM, Will Stevens wrote:
>> 
>>> Has something happened to http://jenkins.buildacloud.org/ recently?
>>> 
>>> We have not had a successful build in 3 days and the queue is growing but
>>> there does not seem to be any build slaves in action handling the
>>> workload.  Is this an expected outage?
>>> 
>> 
>> The master is out of disk space (and probably few slaves too). I tried
>> to raise this but I don't have access to the master server to try and
>> fix this.
>> 
>> 
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 8826230892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>> PS. If you see any footer below, I did not add it :)
>> Find out more about ShapeBlue and our range of CloudStack related services
>> 
>> IaaS Cloud Design & Build> iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering> engineering/>
>> CloudStack Infrastructure Support> cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses> 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.
>> 

Jenkins build became unstable: simulator-singlerun #755

[jenkins]

See 

[CVE-2014-7807] Apache CloudStack unauthenticated LDAP binds

[John Kinsella]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

CVE-2014-7807: Apache CloudStack unauthenticated LDAP binds

CVSS:
7.5, AV:N/AC:L/Au:N/C:P/I:P/A:P

Vendors:
The Apache Software Foundation
Citrix, Inc.

Versions Afffected:
Apache CloudStack 4.3, 4.4

Description:
Apache CloudStack may be configured to authenticate LDAP users.
When so configured, it performs a simple LDAP bind with the name
and password provided by a user.  Simple LDAP binds are defined
with three mechanisms (RFC 4513): 1) username and password; 2)
unauthenticated if only a username is specified; and 3) anonymous
if neither username or password is specified.  Currently, Apache
CloudStack does not check if the password was provided which could
allow an attacker to bind as an unauthenticated user.

Mitigation:
Users of Apache CloudStack 4.4 and derivatives should update to the
latest version (4.4.2)

An updated release for Apache CloudStack 4.3.2 is in testing. Until
that is released, we recommend following the mitigation below:

By default, many LDAP servers are not configured to allow unauthenticated
binds.  If the LDAP server in use allow this behaviour, a potential
interim solution would be to consider disabling unauthenticated
binds.

Credit:
This issue was identified by the Citrix Security Team.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCgAGBQJUhgUCAAoJEOom9N0pCN7SOQMQAKyBuhg25u3FcVOU5XMdGGpT
2kSVFoLFR74ObI8bdr3HP+2LdLf/Go9QBBrWlZ034FUj6OV0Ct5o8TNB6AHbv0qF
Ar4N05JoGtPaDCe9sWV/+ykOJH8snQjnYwVFrLZlLw8Y/JUQ+I1yJBksw8a2/hT2
vmYgYiAQyrEMMk4bhBBlEyaJFMhuMtKtgUqLDW8wmlhkt2acZMt/0BKxDwAO8o7m
6ypepPCmkPHUpD50tfcCI+K4ib/C5EOn40n4orM97/JHZLsCyhz5nk36eQMOQQz2
fJlaA04fQSV4Cv7c+S0LPh5e4e6TPSrOW3O4/V2dkjK/GgP8kUoo7ivyjIw6d2oJ
Z5vqqgxrmgwDjH58YfVu3tyVuDlOFTZfCLkhdoXMxHfMLYYKeXkffRli9XabxrE+
AkVoXaQAumf8IzTLVSQztV18jC79kvEeCV0pFYOjb/X/gShemruqmCWVDulj1ax6
tzoP+Bm2mQRyrRClY37R+q3cQ2z6eNAC/vAoYzhYBN1o63MYneLYDADhyE6YIGz0
LTbDDGFn0WVdFDrqworHdYDIMW7HQFMNtsQuueeP7LBldsgyTmjmBMp+S3Tq27UT
RaVgp3n9ZUPdzj/i1vvJBrATKUNmv1GDoy+C1GPNx423nEOe7dFkMJARlcbf5Pml
03DX+ot4Xan0P5HXPT+r
=QqOf
-END PGP SIGNATURE-

Re: [GitHub] cloudstack pull request: Feature cenik123 vpcvrr 1.1.1

[Karl Harris]

On Tue, Dec 2, 2014 at 3:50 AM, lsimons  wrote:

> Github user lsimons commented on the pull request:
>
> https://github.com/apache/cloudstack/pull/33#issuecomment-65199170
>
> Hey folks,
>
> Karl thanks for contributing. Looks like quite a bit of work!
>
> Rohit thanks for CC-ing me in :)
>
> It's a bit hard to read the pull request right now and provide review
> comments:
> * Github says there's nearly 7000 changed files so at a guess
> something went wrong there? I had a look, and it looks like
> KarlHarrisSungardAS/cloudstack is quite a ways behind master, which may
> explain that...? It's probably a good idea to make a copy of the feature
> branch, rebase it against current master, squash some of the commits
> together, and then re-send the pull request. Or, start another branch, and
> cherry-pick over just the changes that _should_ be in the change set.
> * git hasn't picked up on the relation between veewee and packer, it's
> probably good idea to give it some more hints. For example it would be good
> to see
>
> https://github.com/KarlHarrisSungardAS/cloudstack/commit/892b11ec0230ce87d14370fd1055ac223096cc77#diff-67bdab8b08f1e110ceabe1a23c3d4011R1
> compared to the veewee equivalent.
> * there's a lot of 'shuffling' and/or adding comments intermixed with
> functional changes. For example
> https://github.com/KarlHarrisSungardAS/cloudstack/commit/7f55a1ef032c29cb955e02c90da43c91739108d7#diff-95748c84d8b6be2da502091e69b748d9L30
> you might think the 'set -x' is getting removed here, but it just moved
> down a bit amidst a few new comments.
> * there's a lot of commits that are seemingly unrelated to the actual
> change (probably cherry-picked from master onto the feature branch?), those
> will need to be filtered out I think.
> * there's a lot of 'archive' commits which have unfinished
> 'checkpoint' code. I imagine all that work gets finished 'later on' (like
> renaming _gitignore to .gitignore is one that I tracked) but it's not so
> easy to see. It'd be great if those things could be squashed together.
>
> I will issue a revised pull request shortlyThanks for the input and
suggestions.

As far as content goes...
>
> 1) Like sebastien says, veewee is in maintenance mode and moving to
> packer (replacing veewee) is definitely a good idea. This looks like a
> straightforward port, which if it works ok seems like the way to go. We
> _should_ make sure to do it in a way that's somewhat compatible with the
> jenkins.buildacloud.org setup. I don't think we could sustain maintenance
> of both packer and veewee builds for long, it'll be a pain to keep changes
> in sync. I'd want to drop veewee use completely.
>
My intent with moving to Packer was to make/continue the systemvm builds
compatible with jenkins. This is part of building a self supporting unit
test framework using Packer/Vagrant. See below.

>
> 2) Testing the systemvm using vagrant is also obviously a good idea
> (we're doing much the same, over at
> https://github.com/schubergphilis/cloudstack/tree/feature/systemvm-persistent-config/tools/vagrant/systemvm
> see
> https://github.com/schubergphilis/cloudstack/commits/feature/systemvm-test
> for an abandoned branch having just test-related commits), though I don't
> understand why we'd need to use vagrant templates? The .box file that we
> get out of the veewee-based systemvm build imports (
> https://github.com/apache/cloudstack/blob/master/tools/appliance/build.sh#L466)
> just fine...
>
> Yes, the use of vagrant templates is a bit redundant given the self
patching nature of the systemvms. I will look at the references above as
our work progresses.


> 3) For the stuff that seems to be planned _beyond_ these changes, it
> might be a good idea to pop by on the development mailing list and discuss
> plans. A few people at Schuberg Philis (my employer, where there's a few
> people working on cloudstack) have been working on redundancy for the
> virtual router for a few months now. We've found that making it work also
> involves a lot of changes outside of the systemvm, too, i.e. changing the
> orchestration logic in the java code to match changed behavior of the vpc
> router (see
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Refactor+for+Redundant+Virtual+Router+Implementation
> /



> https://www.slideshare.net/LeoSimons1/toolkit-posterccceu14-v2 ).
> @spark404 please do have a look at Karl's approach :)
>
 After looking a how Cloudstack implements both public and VPC routers; I
have chosen to concentrate on the systemvm and what is required to create a
VPC redundant router with the minimum changes to the interface between the
system virtual machine (scripts) and the Cloudstack management server. The
idea is to add the ability for the existing VPC routers to route
dynamically configured network topologies (tiers) by using the existing
 Create, Read, Update and Delete (CRUD) network scripts. The goal is to
only add a boolean

Re: KVM - VM snapshot (round 2)

[Laszlo Hornyak]

It is still doing the same, I suspect that this is an intentional behavior
of qemu, it keeps the disk space for future use. However I haven't found
any documentation on how users should free the space.



On Mon, Dec 8, 2014 at 12:32 PM, Wei ZHOU  wrote:

> As far as I know, KVM does support memory snapshot.
> The shortcoming is libvirt-java supports only internal snapshot (not
> external snapshots) for now.
> In this case, the memory snapshot will be attached to the qcow2 file, and
> the qcow2 will grow even after we remove the memory snapshot.
>
> I've changed and tested on 4.2 before, but not pushed into production.
>
> An email from the Mice, the developer of this functionality:
> http://cloudstack.markmail.org/message/c3hkpxbad6ul4mza
>
> -Wei
>
> 2014-12-08 12:11 GMT+01:00 Vadim Kimlaychuk :
>
> > CS does not support memory snapshots for XenServer. Disk snapshots are
> > working. Not sure about VmWare, but I guess it should be the same. I
> > thought the reachest feature-set is developed for KVM. But if it does not
> > support memory snapshots - I wonder wich hypervisor does it ? This option
> > at user interface exists, but I didn't see it worked.
> >
> > Vadim.
> >
> >
> > -Original Message-
> > From: Andrija Panic [mailto:andrija.pa...@gmail.com]
> > Sent: Monday, December 08, 2014 12:51 PM
> > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> > Subject: KVM - VM snapshot (round 2)
> >
> > Hi guys,
> >
> > still wondering is there any interest into imlementing the VM snapshoot
> > for KVM ?
> >
> > We desperately need it, so will try to contribute anyway we can (not me
> > obviosuly, not a developer, but my colegues will).
> >
> > Can you give some guidance on this subject - I'm aware of the design
> > documents here
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots but
> > any more input would be very much appriciated.
> >
> > I understand, that VMware/Xen natively support this, and that it might
> > have bigger user-base for Xen VS KVM - but this is one of the major KVM
> > missing features...
> >
> > Any input greatly appreciated...
> >
> > --
> >
> > Andrija Panić
> >
>



-- 

EOF

Jenkins build became unstable: simulator-4.5-singlerun #84

[jenkins]

See 

Re: 4.5.0rc0 - available for testing.

[Mike Tutkowski]

FYI

During my regression testing of 4.5, I noticed a storage-related issue with
regards to VMware.

I had to correct it in be38b9706615d5ab0cc9959577b0fff9a36a9fc6.

On Mon, Dec 8, 2014 at 8:57 AM, Will Stevens  wrote:

> Thank you.  I have kicked off a system vm build to make sure everything is
> working correctly.  Lots of things in the queue though, so it may take a
> while.
>
> ws
>
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Mon, Dec 8, 2014 at 10:49 AM, Daan Hoogland 
> wrote:
>
> > merged
> >
> > On Mon, Dec 8, 2014 at 4:46 PM, Daan Hoogland 
> > wrote:
> > > as a pragmatic programmer, yes. In light of the work we are starting
> > > on wednesday, no. I leave picking the answer as an excercise to the
> > > reader;)
> > >
> > > On Mon, Dec 8, 2014 at 4:43 PM, Will Stevens 
> > wrote:
> > >> I am not hosting a public repo with the fix.  I think a merge is the
> > >> simplest way.  A pull request is great for non-committers to
> contribute,
> > >> but I think it is a bit disjointed for committers who already have
> > access
> > >> to create fix branches.  Do you agree?
> > >>
> > >> ws
> > >>
> > >>
> > >> *Will STEVENS*
> > >> Lead Developer
> > >>
> > >> *CloudOps* *| *Cloud Solutions Experts
> > >> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > >> w cloudops.com *|* tw @CloudOps_
> > >>
> > >> On Mon, Dec 8, 2014 at 10:37 AM, Daan Hoogland <
> daan.hoogl...@gmail.com
> > >
> > >> wrote:
> > >>
> > >>> lgtm,
> > >>>
> > >>> do i look for a pull request, or just merge?
> > >>>
> > >>> On Mon, Dec 8, 2014 at 3:46 PM, Will Stevens 
> > >>> wrote:
> > >>> > We need to get my fix '[MERGE REQUEST] hotfix/4.5-7959'merged in to
> > get
> > >>> the
> > >>> > system vms building again.  The building is currently broken
> because
> > of a
> > >>> > compatibility issues.
> > >>> >
> > >>> > This merge should be made asap...
> > >>> >
> > >>> > Cheers,
> > >>> >
> > >>> > *Will STEVENS*
> > >>> > Lead Developer
> > >>> >
> > >>> > *CloudOps* *| *Cloud Solutions Experts
> > >>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > >>> > w cloudops.com *|* tw @CloudOps_
> > >>> >
> > >>> > On Mon, Dec 8, 2014 at 9:43 AM, Pierre-Luc Dion <
> pdion...@apache.org
> > >
> > >>> wrote:
> > >>> >
> > >>> >> few question about 4.5;
> > >>> >>
> > >>> >> - which systemvm should we use? jenkins job build-systemvm-4.5 is
> a
> > >>> month
> > >>> >> old.
> > >>> >> - upgrade path seams damaged, previous bug CLOUDSTACK-8041 is
> > >>> >> false, although I've never succeed to upgrade a system so far.
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> On Fri, Dec 5, 2014 at 11:07 PM, Pierre-Luc Dion <
> > pd...@cloudops.com>
> > >>> >> wrote:
> > >>> >>
> > >>> >> > The upgrade path require a systemvm-template otherwise the
> > database
> > >>> >> > upgrade fail, I've create this one: CLOUDSTACK-8041
> > >>> >> >
> > >>> >> > Could it be possible to just look for the latest template to
> exist
> > >>> during
> > >>> >> > a db upgrade? with the current check, to upgrade from 4.2.1
> > require to
> > >>> >> have
> > >>> >> > the systemvm-template of 4.3,4.4 and 4.5 of all hypervisors in
> > order
> > >>> to
> > >>> >> > successfully upgrade the database. is this something easy to
> fix?
> > >>> >> >
> > >>> >> >
> > >>> >> >
> > >>> >> >
> > >>> >> > On Fri, Dec 5, 2014 at 8:53 PM, David Nalley 
> > wrote:
> > >>> >> >
> > >>> >> >> Hi All,
> > >>> >> >>
> > >>> >> >> I've created a 4.5.0 release candidate, with the following
> > artifacts
> > >>> >> >> up for review:
> > >>> >> >>
> > >>> >> >> Git Branch and Commit SH:
> > >>> >> >>
> > >>> >> >>
> > >>> >>
> > >>>
> >
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20141206T0129
> > >>> >> >> Commit: fcfc3060ff5a7aa2c57548ded90298c0920921fd
> > >>> >> >>
> > >>> >> >>
> > >>> >> >> Source release (checksums and signatures are available at the
> > same
> > >>> >> >> location):
> > >>> >> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc0/
> > >>> >> >>
> > >>> >> >> PGP release keys (signed using A15F30B9):
> > >>> >> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > >>> >> >>
> > >>> >> >> Because this is an early RC, I am not going to yet call a vote
> > on it,
> > >>> >> >> but rather going to let it set and let folks see if it's
> tenable.
> > >>> >> >>
> > >>> >> >> PLEASE test, and leave feedback in this thread.
> > >>> >> >>
> > >>> >> >> --David
> > >>> >> >>
> > >>> >> >
> > >>> >> >
> > >>> >> >
> > >>> >> >
> > >>> >>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Daan
> > >>>
> > >
> > >
> > >
> > > --
> > > Daan
> >
> >
> >
> > --
> > Daan
> >
>



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

Jenkins build is still unstable: simulator-singlerun #756

[jenkins]

See 

New Defects reported by Coverity Scan for cloudstack

[scan-admin]

Hi,

Please find the latest report on new defect(s) introduced to cloudstack found 
with Coverity Scan.

7 new defect(s) introduced to cloudstack found with Coverity Scan.
8 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent 
build analyzed by Coverity Scan.

New defect(s) Reported-by: Coverity Scan
Showing 7 of 7 defect(s)


** CID 1257440:  Logically dead code  (DEADCODE)
/server/src/com/cloud/configuration/ConfigurationManagerImpl.java: 2575 in 
com.cloud.configuration.ConfigurationManagerImpl.deleteDiskOffering(org.apache.cloudstack.api.command.admin.offering.DeleteDiskOfferingCmd)()

** CID 1257439:  Bx: Questionable Boxing of primitive value  
(FB.BX_UNBOXING_IMMEDIATELY_REBOXED)
/server/src/com/cloud/api/query/dao/DomainJoinDaoImpl.java: 131 in 
com.cloud.api.query.dao.DomainJoinDaoImpl.setResourceLimits(com.cloud.api.query.vo.DomainJoinVO,
 boolean, org.apache.cloudstack.api.response.ResourceLimitAndCountResponse)()

** CID 1257438:  Bx: Questionable Boxing of primitive value  
(FB.BX_BOXING_IMMEDIATELY_UNBOXED)
/server/src/com/cloud/storage/snapshot/SnapshotManagerImpl.java: 1107 in 
com.cloud.storage.snapshot.SnapshotManagerImpl.allocSnapshot(java.lang.Long, 
java.lang.Long, java.lang.String)()

** CID 1257437:  Logically dead code  (DEADCODE)
/server/src/com/cloud/configuration/ConfigurationManagerImpl.java: 2488 in 
com.cloud.configuration.ConfigurationManagerImpl.updateDiskOffering(org.apache.cloudstack.api.command.admin.offering.UpdateDiskOfferingCmd)()

** CID 1257436:  Dereference null return value  (NULL_RETURNS)
/services/secondary-storage/server/src/org/apache/cloudstack/storage/resource/NfsSecondaryStorageResource.java:
 725 in 
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.registerTemplateOnSwift(org.apache.cloudstack.storage.command.DownloadCommand)()

** CID 1257435:  Resource leak on an exceptional path  (RESOURCE_LEAK)
/services/secondary-storage/server/src/org/apache/cloudstack/storage/resource/NfsSecondaryStorageResource.java:
 734 in 
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.registerTemplateOnSwift(org.apache.cloudstack.storage.command.DownloadCommand)()

** CID 1257434:  Resource leak  (RESOURCE_LEAK)
/services/secondary-storage/server/src/org/apache/cloudstack/storage/resource/NfsSecondaryStorageResource.java:
 743 in 
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.registerTemplateOnSwift(org.apache.cloudstack.storage.command.DownloadCommand)()



*** CID 1257440:  Logically dead code  (DEADCODE)
/server/src/com/cloud/configuration/ConfigurationManagerImpl.java: 2575 in 
com.cloud.configuration.ConfigurationManagerImpl.deleteDiskOffering(org.apache.cloudstack.api.command.admin.offering.DeleteDiskOfferingCmd)()
2569 if (offering == null) {
2570 throw new InvalidParameterValueException("Unable to find 
disk offering by id " + diskOfferingId);
2571 }
2572 
2573 Long userId = CallContext.current().getCallingUserId();
2574 if (userId == null) {
>>> CID 1257440:  Logically dead code  (DEADCODE)
>>> Execution cannot reach this statement "userId = java.lang.Long.val...".
2575 userId = Long.valueOf(User.UID_SYSTEM);
2576 }
2577 User user = _userDao.findById(userId);
2578 if (user == null || user.getRemoved() != null) {
2579 throw new InvalidParameterValueException("Unable to find 
active user by id " + userId);
2580 }


*** CID 1257439:  Bx: Questionable Boxing of primitive value  
(FB.BX_UNBOXING_IMMEDIATELY_REBOXED)
/server/src/com/cloud/api/query/dao/DomainJoinDaoImpl.java: 131 in 
com.cloud.api.query.dao.DomainJoinDaoImpl.setResourceLimits(com.cloud.api.query.vo.DomainJoinVO,
 boolean, org.apache.cloudstack.api.response.ResourceLimitAndCountResponse)()
125 response.setSnapshotLimit(snapshotLimitDisplay);
126 response.setSnapshotTotal(snapshotTotal);
127 response.setSnapshotAvailable(snapshotAvail);
128 
129 Long templateLimit = 
ApiDBUtils.findCorrectResourceLimitForDomain(domain.getTemplateLimit(), 
fullView, ResourceType.template, domain.getId());
130 String templateLimitDisplay = (fullView || templateLimit == -1) 
? "Unlimited" : String.valueOf(templateLimit);
>>> CID 1257439:  Bx: Questionable Boxing of primitive value  
>>> (FB.BX_UNBOXING_IMMEDIATELY_REBOXED)
>>> Boxed value is unboxed and then immediately reboxed
131 Long templateTotal = (domain.getTemplateTotal() == null) ? 0 : 
domain.getTemplateTotal();
132 String templateAvail = (fullView || templateLimit == -1) ? 
"Unlimited" : String.valueOf(templateLimit - templateTotal);
1

Port forwarding (web) - doesnt show real client IP

[Andrija Panic]

Hi,

when doing port forwarding on VPC VR - port 80 - when some client access
web site - only the main Public IP of the VPC is logged in apache access
logs as remote IP.

Why is this behaviour - and can this be changed ?
My understanding is that this is kind of bug (unless needed for some other
reasons) - port forwading is DNAT in essence, so only the destination
IP/port should be changed, not proxied all the way, as it seems to be the
case here...

I read on other guys mailing list - same behavior for loadbalancer...

Any suggestion ?

Thanks,

-- 

Andrija Panić

Re: Port forwarding (web) - doesnt show real client IP

[Andrija Panic]

And just to spice things a little bit, ALL remote connections appears to
come from main Public IP of the VPC VR.
So we can not block some stuff on firewall onVM (while doing port
forwading) because all connections appear to come from main Public IP of
the VPC VR.

This is terrible design/bug - can we change this ?
I'm on the ACS 4.3 currently...

cheers

On 8 December 2014 at 23:42, Andrija Panic  wrote:

> Hi,
>
> when doing port forwarding on VPC VR - port 80 - when some client access
> web site - only the main Public IP of the VPC is logged in apache access
> logs as remote IP.
>
> Why is this behaviour - and can this be changed ?
> My understanding is that this is kind of bug (unless needed for some other
> reasons) - port forwading is DNAT in essence, so only the destination
> IP/port should be changed, not proxied all the way, as it seems to be the
> case here...
>
> I read on other guys mailing list - same behavior for loadbalancer...
>
> Any suggestion ?
>
> Thanks,
>
> --
>
> Andrija Panić
>



-- 

Andrija Panić

Re: Port forwarding (web) - doesnt show real client IP

[Erik Weber]

On Mon, Dec 8, 2014 at 11:42 PM, Andrija Panic 
wrote:

> Hi,
>
> when doing port forwarding on VPC VR - port 80 - when some client access
> web site - only the main Public IP of the VPC is logged in apache access
> logs as remote IP.
>
> Why is this behaviour - and can this be changed ?
> My understanding is that this is kind of bug (unless needed for some other
> reasons) - port forwading is DNAT in essence, so only the destination
> IP/port should be changed, not proxied all the way, as it seems to be the
> case here...
>
> I read on other guys mailing list - same behavior for loadbalancer...
>
>
This is common for all load balancers.
Haven't checked, but you could see if the CloudStack LB expose the client
IP as X-Forwarded-For header, which is the normal way of doing it.


-- 
Erik

Re: Port forwarding (web) - doesnt show real client IP

[Erik Weber]

On Mon, Dec 8, 2014 at 11:55 PM, Andrija Panic 
wrote:

> And just to spice things a little bit, ALL remote connections appears to
> come from main Public IP of the VPC VR.
> So we can not block some stuff on firewall onVM (while doing port
> forwading) because all connections appear to come from main Public IP of
> the VPC VR.
>
> This is terrible design/bug - can we change this ?
> I'm on the ACS 4.3 currently...
>
>
This is a NAT problem. You could use a shared network with Public IPs or
Basic Networking with Public IPs.

-- 
Erik

Re: Port forwarding (web) - doesnt show real client IP

[Andrija Panic]

Hi Erik - yes I know of shared network - been using that, but want to move
behind VPC to organize stuff a little bit more... ok, for loadbalancing -
did not check, as that is not my problem at the moment.

But port forwarding really is - this is really bad implemenation or bug in
my opinion, never saw this kind of behaviour on any router anywhere...

On 9 December 2014 at 00:03, Erik Weber  wrote:

> On Mon, Dec 8, 2014 at 11:55 PM, Andrija Panic 
> wrote:
>
> > And just to spice things a little bit, ALL remote connections appears to
> > come from main Public IP of the VPC VR.
> > So we can not block some stuff on firewall onVM (while doing port
> > forwading) because all connections appear to come from main Public IP of
> > the VPC VR.
> >
> > This is terrible design/bug - can we change this ?
> > I'm on the ACS 4.3 currently...
> >
> >
> This is a NAT problem. You could use a shared network with Public IPs or
> Basic Networking with Public IPs.
>
> --
> Erik
>



-- 

Andrija Panić

Re: Port forwarding (web) - doesnt show real client IP

[Marcus]

It sounds like some iptables rules got broken at some point for the static
NAT, and since there's still a catch-all SNAT for outbound it gets caught
by that and still keeps working, but is broken in a subtle way that goes
unnoticed.

On Mon, Dec 8, 2014 at 2:55 PM, Andrija Panic 
wrote:

> And just to spice things a little bit, ALL remote connections appears to
> come from main Public IP of the VPC VR.
> So we can not block some stuff on firewall onVM (while doing port
> forwading) because all connections appear to come from main Public IP of
> the VPC VR.
>
> This is terrible design/bug - can we change this ?
> I'm on the ACS 4.3 currently...
>
> cheers
>
> On 8 December 2014 at 23:42, Andrija Panic 
> wrote:
>
> > Hi,
> >
> > when doing port forwarding on VPC VR - port 80 - when some client access
> > web site - only the main Public IP of the VPC is logged in apache access
> > logs as remote IP.
> >
> > Why is this behaviour - and can this be changed ?
> > My understanding is that this is kind of bug (unless needed for some
> other
> > reasons) - port forwading is DNAT in essence, so only the destination
> > IP/port should be changed, not proxied all the way, as it seems to be the
> > case here...
> >
> > I read on other guys mailing list - same behavior for loadbalancer...
> >
> > Any suggestion ?
> >
> > Thanks,
> >
> > --
> >
> > Andrija Panić
> >
>
>
>
> --
>
> Andrija Panić
>

Re: Port forwarding (web) - doesnt show real client IP

[Marcus]

Or wait, you're not using static NAT, you're just using port forwarding,
correct? Everything will be NAT'ed outbound to the VPC router's public IP
per SNAT, like one would expect behind a NAT. You could force outbound to
match the IP that the port forwarder is on, but what if you have multiple
IPs port forwarding to that instance?

At any rate, if you can find a set of iptables rules you think should be
applied in a certain case to fix an issue, you can find the scripts that
apply these rules in systemvm/patches/debian/config/opt/cloud/bin/. These
scripts adjust iptables whenever a change is made. If you can come up with
a fix for something you can send us in a patch.

On Mon, Dec 8, 2014 at 3:08 PM, Andrija Panic 
wrote:

> Hi Erik - yes I know of shared network - been using that, but want to move
> behind VPC to organize stuff a little bit more... ok, for loadbalancing -
> did not check, as that is not my problem at the moment.
>
> But port forwarding really is - this is really bad implemenation or bug in
> my opinion, never saw this kind of behaviour on any router anywhere...
>
> On 9 December 2014 at 00:03, Erik Weber  wrote:
>
> > On Mon, Dec 8, 2014 at 11:55 PM, Andrija Panic 
> > wrote:
> >
> > > And just to spice things a little bit, ALL remote connections appears
> to
> > > come from main Public IP of the VPC VR.
> > > So we can not block some stuff on firewall onVM (while doing port
> > > forwading) because all connections appear to come from main Public IP
> of
> > > the VPC VR.
> > >
> > > This is terrible design/bug - can we change this ?
> > > I'm on the ACS 4.3 currently...
> > >
> > >
> > This is a NAT problem. You could use a shared network with Public IPs or
> > Basic Networking with Public IPs.
> >
> > --
> > Erik
> >
>
>
>
> --
>
> Andrija Panić
>

Jenkins build is still unstable: simulator-4.5-singlerun #85

[jenkins]

See 

Re: [DISCUSS] Issues with Ubuntu instance creation

[John Kinsella]

> On Dec 8, 2014, at 8:10 AM, Tim Mackey  wrote:
> 
> I've been working through a series of issues getting Ubuntu 12.04 LTS 
> templates to provision correctly, and I *think* most are really doc issues, 
> but before I run off and update docs I wanted to confirm that I'm doing the 
> right thing.  Here's my list of issues, and what I did to get past my 
> "issue".  My documentation source is: 
> http://cloudstack-administration.readthedocs.org/en/latest/templates.html.  
> My CloudStack is 4.4.
> 
> 1. The docs make no mention of an Ubuntu change password script, and Google 
> returns Shankar's GitHub scripts as option #4.  Unfortunately, that script 
> has a user of "ubuntu" hardcoded into it, so unless your template has an 
> "ubuntu" user, its not going to work.  I haven't tried to use the stock 
> CloudStack password change script in my template, but have found references 
> to it not working as expected.  For my purposes, I changed Shankar's script 
> to use a "root" user, but this leaves the following questions open:
> 
> - Does the current CloudStack script work with Ubuntu 12.04 and later?  If 
> so, I vote the docs be updated to reflect support for Ubuntu 12.04 and later; 
> with the objective of both clarifying the docs and helping boost our docs to 
> a higher rank than Shankar's GitHub.

See [1]. It should work with 12.04LTS.

> - If the current CloudStack script doesn't work with Ubuntu 12.04 LTS, should 
> a JIRA ticket be entered to resolve this, or should we have multiple scripts 
> available and effectively incorporate Shankar's work more officially?
> 
> 2. The docs recommend setting the password to expire, but when the change 
> password script runs, that flag is cleared and the user isn't promoted to 
> reset the root password.  That leaves the following question in my mind.  
> 
> - Is our password intended to be a one-time use password.  If so, then the 
> password change script should reset expiration forcing a new one to be set.  
> If not, then should we not remove the "expire password" recommendation from 
> the docs?

Some providers and cloud mgmt platforms keep a copy of the “current” root 
password as set by the reset script. That type of functionality is why there’s 
probably no “expire” in the change passed script. I think you confusion is 
coming from the template section is not closely tied to the password management 
section - if one is making templates, they should reset the password so first 
login requires new password. This saves us from having thousands of VMs on the 
Internet with a default password. If a shop is making templates, and using 
password management - the password should be generated at VM creation and 
shouldn’t be an issue.

Either way - you really shouldn’t be logging into systems (VMs or physical) as 
root on a regular basis.

> 3. The script in the docs covering clearing the logs (step 6) doesn't include 
> clearing syslog.  Recommend updating the script to include:  cat /dev/null > 
> /var/log/syslog 2>/dev/null
> 
> 4. The script in the docs covering clearing of command history (step 9) 
> doesn't clear the in memory history.  Recommend updating the script to 
> become:  cat /dev/null > ~/.bash_history && history -c && unset HISTFILE && 
> halt -p.  This would also remove the the shutdown step (step 10).

Good points, although I’m not sure if “halt” is as safe as shutdown...

> 5. The script to set the hostname has a race condition which effectively 
> means it rarely sets the hostname correctly on initial boot.  I've attached 
> the script I used.  It doesn't depend upon the leases file being present, and 
> took care of some alternate "blank" hostname cases I encountered while 
> debugging.

Unfortunately ASF lists strip out attachments. 

> I'm happy to update the docs, but want to make certain what I've encountered 
> as issues are things we care about updating.

Would love to have your changes. At the minimum, please create Jira tickets, 
but if/where possible we’d happily take either submitted code review requests 
or pull requests on github.

John

1: 
http://cloudstack-administration.readthedocs.org/en/latest/templates.html#adding-password-management-to-your-templates

[Question] System VM

[Mike Tutkowski]

Hi,

I was wondering, I changed code related to copying a template down to
primary storage from secondary storage. This code - related to ESXi - gets
run in the SSVM.

Is it sufficient if I rebuild the codebase using the systemvm profile,
destroy my SSVM, and allow a new one to be created? Does this kind of code
get applied to system VMs are a patch as part of systemvm.iso?

The way I've tested this kind of code to date is by putting a breakpoint in
VMwareGuru and redirecting the command to run in the management server
instead of in the SSVM.

Thanks!

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

Jenkins build is still unstable: simulator-singlerun #757

[jenkins]

See 

Jenkins build is still unstable: simulator-4.5-singlerun #86

[jenkins]

See 

RE: [Question] System VM

[Sateesh Chodapuneedi]

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: 09 December 2014 05:41
> To: dev@cloudstack.apache.org
> Subject: [Question] System VM
> 
> Hi,
> 
> I was wondering, I changed code related to copying a template down to primary 
> storage from secondary storage. This code - related
> to ESXi - gets run in the SSVM.
> 
> Is it sufficient if I rebuild the codebase using the systemvm profile, 
> destroy my SSVM, and allow a new one to be created? Does this
> kind of code get applied to system VMs are a patch as part of systemvm.iso?
Yes, that should be sufficient. 
Just make sure there is no stale systemvm.iso in systemvm folder of the 
secondary storage share in the zone.

Regards,
Sateesh
> 
> The way I've tested this kind of code to date is by putting a breakpoint in 
> VMwareGuru and redirecting the command to run in the
> management server instead of in the SSVM.
> 
> Thanks!
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*

Jenkins build is still unstable: simulator-singlerun #758

[jenkins]

See 

Re: [Question] System VM

[Mike Tutkowski]

Thanks, Sateesh!

On Monday, December 8, 2014, Sateesh Chodapuneedi <
sateesh.chodapune...@citrix.com> wrote:

> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com 
> ]
> > Sent: 09 December 2014 05:41
> > To: dev@cloudstack.apache.org 
> > Subject: [Question] System VM
> >
> > Hi,
> >
> > I was wondering, I changed code related to copying a template down to
> primary storage from secondary storage. This code - related
> > to ESXi - gets run in the SSVM.
> >
> > Is it sufficient if I rebuild the codebase using the systemvm profile,
> destroy my SSVM, and allow a new one to be created? Does this
> > kind of code get applied to system VMs are a patch as part of
> systemvm.iso?
> Yes, that should be sufficient.
> Just make sure there is no stale systemvm.iso in systemvm folder of the
> secondary storage share in the zone.
>
> Regards,
> Sateesh
> >
> > The way I've tested this kind of code to date is by putting a breakpoint
> in VMwareGuru and redirecting the command to run in the
> > management server instead of in the SSVM.
> >
> > Thanks!
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com 
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
>


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

Jenkins build is still unstable: simulator-4.5-singlerun #87

[jenkins]

See 

Re: merge from 4.5 to master

[Rajani Karuturi]

4.5 is merged to master as of
commit 701199fca726c68b4fc09ec8939b4822e527e8c7

I hope few more would try merging, now that the conflicts are resolved.

~Rajani

On Mon, Dec 8, 2014 at 12:27 PM, Rajani Karuturi  wrote:

> last attempt was a failure with travis failures before and after the pull
> requests and hence abandoned the merge. Now that travis is green, I
> planning to put up another pull request.
>
> let me know if you see any issues.
>
> ~Rajani
>

Re: [ACS44] router upgrade issue

[Rajani Karuturi]

This looks like recurring problem we are going to face again in the future
version. Especially given that its so deep in a java file, its very easy to
slip it for a release.

Can we use the max version of a 'completed' step from the version table?
Or make this configurable and update it in the docs to use the latest
template version?

~Rajani

On Mon, Dec 8, 2014 at 8:08 PM, Daan Hoogland 
wrote:

> I see some changes that make me want to put 4.5.0 in there for the 4.5
> branch. proceding
>
> On Mon, Dec 8, 2014 at 3:35 PM, Daan Hoogland 
> wrote:
> > Also I don't think we need to let users go through a sysvm upgrade
> > procedure if it is not needed.
> >
> > On Mon, Dec 8, 2014 at 3:34 PM, Daan Hoogland 
> wrote:
> >> Rohit, in 4.4 there was a problem with the templates in 4.4.0 so it
> >> must be 4.4.1. I don't see the underscore but a capital M in
> >> MinVRVersion in 4.4!
> >>
> >> On Mon, Dec 8, 2014 at 3:31 PM, Rohit Yadav 
> wrote:
> >>> In 4.3 it's defined as _minVRVersion. For each major ACS version such
> as ACS
> >>> 4.4.x, this value should be 4.4.0 unless we want to use higher
> templates
> >>> such as 4.4.1 or 4.4.2.
> >>> For 4.5, it should be 4.5.0. This is assuming that ACS templates are
> >>> compatible with future bugfix releases and we don't want to enforce
> >>> templates upgrades unless necessary.
> >>>
> >>>
> >>> On Monday 08 December 2014 07:55 PM, Daan Hoogland wrote:
> 
>  I am looking if the value 4.4.1 is applicable there or whether it
>  should be higher, as we mail. will update you all.
> 
>  On Mon, Dec 8, 2014 at 3:12 PM, Erik Weber 
> wrote:
>  > This should probably happen in 4.5 branch as well I guess?
>  >
>  > --
>  > Erik
>  >
>  > On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland <
> daan.hoogl...@gmail.com>
>  > wrote:
>  >
>  >> H, I investigated an issue some colleagues noticed and it turns out
>  >> that in the update procedure the flag
>  >> VirtualNetworkApplianceService.MinVRVersion is not set for versions
>  >> 4.4.0-4.4.2
>  >>
>  >> I have no workaround other then rebooting the routers instead of
>  >> upgading/updating them. I will patch the branch to contain the
> correct
>  >> minimal version. The higher version branches have this var still
> set
>  >> to 4.3.0 as well.
>  >>
>  >> --
>  >> Daan
>  >>
> 
> 
> 
> >>>
> >>> --
> >>> Regards,
> >>> Rohit Yadav
> >>> Software Architect, ShapeBlue
> >>> M. +91 8826230892 | rohit.ya...@shapeblue.com
> >>> Blog: bhaisaab.org | Twitter: @_bhaisaab
> >>> PS. If you see any footer below, I did not add it :)
> >>>
> >>> Find out more about ShapeBlue and our range of CloudStack related
> services
> >>>
> >>> IaaS Cloud Design &
> >>> Build
> >>> CSForge – rapid IaaS deployment framework<
> http://shapeblue.com/csforge/>
> >>> CloudStack Consulting
> >>> CloudStack Software
> >>> Engineering
> >>> 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.
> >>
> >>
> >>
> >> --
> >> Daan
> >
> >
> >
> > --
> > Daan
>
>
>
> --
> Daan
>

Re: [Question] System VM

[Nitin Mehta]

I kind of doubt that the new systemvm.iso will be propagated to the sec.
storage. You can always follow the process in the wiki [1] to propagate
the new iso which will contain your code change.

[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SystemVm.iso#SystemV
m.iso-VMWare

Thanks,
-Nitin

On 09/12/14 8:15 AM, "Mike Tutkowski"  wrote:

>Thanks, Sateesh!
>
>On Monday, December 8, 2014, Sateesh Chodapuneedi <
>sateesh.chodapune...@citrix.com> wrote:
>
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
>>
>> ]
>> > Sent: 09 December 2014 05:41
>> > To: dev@cloudstack.apache.org 
>> > Subject: [Question] System VM
>> >
>> > Hi,
>> >
>> > I was wondering, I changed code related to copying a template down to
>> primary storage from secondary storage. This code - related
>> > to ESXi - gets run in the SSVM.
>> >
>> > Is it sufficient if I rebuild the codebase using the systemvm profile,
>> destroy my SSVM, and allow a new one to be created? Does this
>> > kind of code get applied to system VMs are a patch as part of
>> systemvm.iso?
>> Yes, that should be sufficient.
>> Just make sure there is no stale systemvm.iso in systemvm folder of the
>> secondary storage share in the zone.
>>
>> Regards,
>> Sateesh
>> >
>> > The way I've tested this kind of code to date is by putting a
>>breakpoint
>> in VMwareGuru and redirecting the command to run in the
>> > management server instead of in the SSVM.
>> >
>> > Thanks!
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkow...@solidfire.com 
>> > o: 303.746.7302
>> > Advancing the way the world uses the cloud
>> > **
>>
>
>
>-- 
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkow...@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the cloud
>**

Re: merge from 4.5 to master

[Mike Tutkowski]

Have we ever decided what to do when people check code into, say, 4.5 and
it is not supposed to go into master?

Merging everything from 4.5 to master is not always desired.

On Mon, Dec 8, 2014 at 8:48 PM, Rajani Karuturi  wrote:

> 4.5 is merged to master as of
> commit 701199fca726c68b4fc09ec8939b4822e527e8c7
>
> I hope few more would try merging, now that the conflicts are resolved.
>
> ~Rajani
>
> On Mon, Dec 8, 2014 at 12:27 PM, Rajani Karuturi 
> wrote:
>
> > last attempt was a failure with travis failures before and after the pull
> > requests and hence abandoned the merge. Now that travis is green, I
> > planning to put up another pull request.
> >
> > let me know if you see any issues.
> >
> > ~Rajani
> >
>



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

Re: [Question] System VM

[Mike Tutkowski]

Thanks, Nitin!

On Mon, Dec 8, 2014 at 9:50 PM, Nitin Mehta  wrote:

> I kind of doubt that the new systemvm.iso will be propagated to the sec.
> storage. You can always follow the process in the wiki [1] to propagate
> the new iso which will contain your code change.
>
> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SystemVm.iso#SystemV
> m.iso-VMWare
>
> Thanks,
> -Nitin
>
> On 09/12/14 8:15 AM, "Mike Tutkowski" 
> wrote:
>
> >Thanks, Sateesh!
> >
> >On Monday, December 8, 2014, Sateesh Chodapuneedi <
> >sateesh.chodapune...@citrix.com> wrote:
> >
> >> > -Original Message-
> >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> >>
> >> ]
> >> > Sent: 09 December 2014 05:41
> >> > To: dev@cloudstack.apache.org 
> >> > Subject: [Question] System VM
> >> >
> >> > Hi,
> >> >
> >> > I was wondering, I changed code related to copying a template down to
> >> primary storage from secondary storage. This code - related
> >> > to ESXi - gets run in the SSVM.
> >> >
> >> > Is it sufficient if I rebuild the codebase using the systemvm profile,
> >> destroy my SSVM, and allow a new one to be created? Does this
> >> > kind of code get applied to system VMs are a patch as part of
> >> systemvm.iso?
> >> Yes, that should be sufficient.
> >> Just make sure there is no stale systemvm.iso in systemvm folder of the
> >> secondary storage share in the zone.
> >>
> >> Regards,
> >> Sateesh
> >> >
> >> > The way I've tested this kind of code to date is by putting a
> >>breakpoint
> >> in VMwareGuru and redirecting the command to run in the
> >> > management server instead of in the SSVM.
> >> >
> >> > Thanks!
> >> >
> >> > --
> >> > *Mike Tutkowski*
> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> > e: mike.tutkow...@solidfire.com 
> >> > o: 303.746.7302
> >> > Advancing the way the world uses the cloud
> >> > * *
> >>
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the cloud
> >* *
>
>


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

[QUESTION] How is snapshot size counted in secondary storage?

[Gaurav Aradhye]

Hello,

When I create a snapshot, from say, template registered through an account,
then

1) How can I know the snapshot size on secondary storage? (API
listSnapshots does not specify the snapshot size)

2) How is snapshot size counted in secondary storage used by the account?
Currently I can see secondary storage count increasing by the (number of
snapshots) and not the snapshot size.

E.g. I have template sized 8 GB. I create a snapshot from it. Now if I list
the secondary storage used by the account, then it lists as "9" (GB). If I
create another snapshot, then it lists it as 10. It is not possible for my
snapshot size to be 1 (GB) because it's created from root volume having
size 8 GB.

Can I say it's a bug? Secondary storage count being listed as (Storage
other than snapshot + number of snapshots) GB.

Regards,
Gaurav

Review Request 28836: CLOUDSTACK-8048: Fix test_ss_limits.py

[Gaurav Aradhye]

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

Review request for cloudstack and SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description
---

Template object after creation of template does not have size attribute. List 
the templates with template id and then access size.


Diffs
-

  test/integration/component/test_ss_limits.py 4d6efc4 

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


Testing
---

Yes.


Thanks,

Gaurav Aradhye

Re: [QUESTION] How is snapshot size counted in secondary storage?

[Mike Tutkowski]

I'm not exactly sure how this number is calculated, but - if you are using
XenServer - remember that after the first snapshot for a volume, each
subsequent snapshot is only the blocks that have changed since the prior
snapshot (this might even be true for ESX these days with CloudStack).

That being the case, unless you change all 8 GB of blocks each time before
doing a snapshot, you should expect your snapshots to be < 8 GB
(potentially very small, if you didn't change much since the last snapshot).

On Mon, Dec 8, 2014 at 10:15 PM, Gaurav Aradhye 
wrote:

> Hello,
>
> When I create a snapshot, from say, template registered through an account,
> then
>
> 1) How can I know the snapshot size on secondary storage? (API
> listSnapshots does not specify the snapshot size)
>
> 2) How is snapshot size counted in secondary storage used by the account?
> Currently I can see secondary storage count increasing by the (number of
> snapshots) and not the snapshot size.
>
> E.g. I have template sized 8 GB. I create a snapshot from it. Now if I list
> the secondary storage used by the account, then it lists as "9" (GB). If I
> create another snapshot, then it lists it as 10. It is not possible for my
> snapshot size to be 1 (GB) because it's created from root volume having
> size 8 GB.
>
> Can I say it's a bug? Secondary storage count being listed as (Storage
> other than snapshot + number of snapshots) GB.
>
> Regards,
> Gaurav
>



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