[GitHub] [cloudstack-primate] DaanHoogland commented on a change in pull request #313: Bootintobios

[GitBox]

DaanHoogland commented on a change in pull request #313:
URL: https://github.com/apache/cloudstack-primate/pull/313#discussion_r421113442



##
File path: src/config/section/compute.js
##
@@ -104,7 +104,8 @@ export default {
   icon: 'reload',
   label: 'label.action.reboot.instance',
   dataView: true,
-  show: (record) => { return ['Running'].includes(record.state) }
+  show: (record) => { return ['Running'].includes(record.state) },
+  args: ['bootintosetup']

Review comment:
   hypervisor contains the type, tnx. There is something confusing in the 
API doc, it only lists it as a request parameter. I think I should be fine.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on pull request #327: view: fix actionbutton args method resource

[GitBox]

rhtyd commented on pull request #327:
URL: 
https://github.com/apache/cloudstack-primate/pull/327#issuecomment-624897355


   Did not test lgtm 



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on issue #240: [BUG] Domain admin: Identify and access > Roles should not be visible

[GitBox]

rhtyd commented on issue #240:
URL: 
https://github.com/apache/cloudstack-primate/issues/240#issuecomment-624895540


   @vladimirpetrov cc @borisstoyanov please test latest master and close.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] vladimirpetrov opened a new issue #240: [BUG] Domain admin: Identify and access > Roles should not be visible

[GitBox]

vladimirpetrov opened a new issue #240:
URL: https://github.com/apache/cloudstack-primate/issues/240


   **Describe the bug**
   'Identify and access > Roles' screen is visible but the domain admin has no 
access there so it doesn't make sense.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Log in as domain admin, go to 'Identify and access > Roles'
   
   **Expected behavior**
   'Identify and access > Roles' should not be visible when logged as domain 
admin.
   
   **Screenshots**
   
![image](https://user-images.githubusercontent.com/12384665/77050456-79754a80-69d2-11ea-9bd3-0baac7d71721.png)
   
   **Desktop (please complete the following information):**
- OS: Ubuntu 18.04 LTS
- Browser: Chrome
- Version: 80.0.3987.132 (Official Build) (64-bit)
   
   **Additional context**
   None.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] vladimirpetrov opened a new issue #244: [BUG] Normal user: the whole Offerings section should not be visible

[GitBox]

vladimirpetrov opened a new issue #244:
URL: https://github.com/apache/cloudstack-primate/issues/244


   **Describe the bug**
   The 'Offerings' section is visible, but mostly unusable, due to missing 
permissions. 
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Go to 'Offerings', try some of the sub-sections.
   
   **Expected behavior**
   The whole 'Offerings' section must be hidden, like in the old UI.
   
   **Screenshots**
   
![image](https://user-images.githubusercontent.com/12384665/77084406-9a0bc780-6a07-11ea-9daf-b00f350a28ec.png)
   
   **Desktop (please complete the following information):**
- OS: Ubuntu 18.04 LTS
- Browser: Chrome
- Version: 80.0.3987.132 (Official Build) (64-bit)
   
   **Additional context**
   None.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on issue #241: [BUG] Domain admin: Offerings - more options than in the old UI

[GitBox]

rhtyd commented on issue #241:
URL: 
https://github.com/apache/cloudstack-primate/issues/241#issuecomment-624895144


   @vladimirpetrov cc @borisstoyanov please test latest master and close.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] vladimirpetrov opened a new issue #241: [BUG] Domain admin: Offerings - more options than in the old UI

[GitBox]

vladimirpetrov opened a new issue #241:
URL: https://github.com/apache/cloudstack-primate/issues/241


   **Describe the bug**
   No Offerings menu options are hidden, as they are in the old UI.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Log in as domain admin, go to 'Offerings' - all options are visible there.
   
   **Expected behavior**
   Only two options should be visible, as in the old UI - compute and disk 
offerings.
   
   **Screenshots**
   New UI:
   
![image](https://user-images.githubusercontent.com/12384665/77053228-b2afb980-69d6-11ea-8367-b6b810305706.png)
   
   Old UI:
   
![image](https://user-images.githubusercontent.com/12384665/77053280-c9561080-69d6-11ea-8a15-9405af851b03.png)
   
   **Desktop (please complete the following information):**
- OS: Ubuntu 18.04 LTS
- Browser: Chrome
- Version: 80.0.3987.132 (Official Build) (64-bit)
   
   **Additional context**
   Offerings > System Offerings generates a 404 error, as mentioned in #233.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on issue #244: [BUG] Normal user: the whole Offerings section should not be visible

[GitBox]

rhtyd commented on issue #244:
URL: 
https://github.com/apache/cloudstack-primate/issues/244#issuecomment-624895222


   @vladimirpetrov cc @borisstoyanov please test latest master and close.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on pull request #291: view: permission check, section display

[GitBox]

rhtyd commented on pull request #291:
URL: 
https://github.com/apache/cloudstack-primate/pull/291#issuecomment-624894307


   @shwstppr I've followed your change, which required config wide refactoring.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[VOTE] Apache CloudStack 4.14.0.0 RC2

[Andrija Panic]

Hi All,

I've created a 4.14.0.0 release (RC2), with the following artefacts up for
testing and a vote:

Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520

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

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

The vote will be open until 12th May 2020.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Additional information:

For users' convenience, I've built packages from
377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository here:
http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
Debian/generic, both with noredist support)
and here
https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
(Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):

The release notes are still work-in-progress, but for the upgrade
instructions (including the new systemVM templates) you may refer to the
following URL:
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html

4.14.0.0 systemVM templates are available from here:
http://download.cloudstack.org/systemvm/4.14/

NOTES on issues fixed in this RC2 release:

(these do *NOT* require a full retest if you were testing RC1 already -
just if you were affected by these 2 issues):
-  https://github.com/apache/cloudstack/pull/4055 (explicit timezone in
db.properties, fixes only new installations of 4.14, while for the upgrade
process the documentation has been upgraded accordingly in
https://github.com/apache/cloudstack-documentation/pull/112/files)
-  https://github.com/apache/cloudstack/pull/4057   (fix regression where
one could not delete a snapshot created from a volume on Local storage)

Regards,

Andrija Panić

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #115: fix ToC

[GitBox]

ACSGitBot commented on pull request #115:
URL: 
https://github.com/apache/cloudstack-documentation/pull/115#issuecomment-624870572


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr115
   
   Build Log Output:
   
   
   No log errors found to report.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb opened a new pull request #115: fix ToC

[GitBox]

andrijapanicsb opened a new pull request #115:
URL: https://github.com/apache/cloudstack-documentation/pull/115


   fix ToC for Virtual Machines



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #115: fix ToC

[GitBox]

andrijapanicsb commented on pull request #115:
URL: 
https://github.com/apache/cloudstack-documentation/pull/115#issuecomment-624869577


   requesting docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #115: fix ToC

[GitBox]

ACSGitBot commented on pull request #115:
URL: 
https://github.com/apache/cloudstack-documentation/pull/115#issuecomment-624869615


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #114: Update systemvm.rst

[GitBox]

ACSGitBot commented on pull request #114:
URL: 
https://github.com/apache/cloudstack-documentation/pull/114#issuecomment-624864401


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr114
   
   Build Log Output:
   
   
   No log errors found to report.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624863566


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr113
   
   Build Log Output:
   
   
   No log errors found to report.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #114: Update systemvm.rst

[GitBox]

andrijapanicsb commented on pull request #114:
URL: 
https://github.com/apache/cloudstack-documentation/pull/114#issuecomment-624862677


   requesting docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #114: Update systemvm.rst

[GitBox]

ACSGitBot commented on pull request #114:
URL: 
https://github.com/apache/cloudstack-documentation/pull/114#issuecomment-624862709


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624862611


   requesting docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb removed a comment on pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb removed a comment on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624851015


   I wanna see docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624862646


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb opened a new pull request #114: Update systemvm.rst

[GitBox]

andrijapanicsb opened a new pull request #114:
URL: https://github.com/apache/cloudstack-documentation/pull/114


   Added backaccessing-system-vms section



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: https://hub.docker.com/u/apache

[Riepl, Gregor (SWISS TXT)]

Hi Rohit,

I'm also still waiting on official container builds for 
https://github.com/apache/cloudstack-kubernetes-provider/ 

The readme already contains a reference to 
https://hub.docker.com/r/apache/cloudstack-kubernetes-provider/ , so could you 
extend the request to the infra team to include this repository as well?

Thank you very much.

Regards,
Gregor

From: Rohit Yadav 
Sent: 06 May 2020 13:35
To: in...@apache.org ; d...@community.apache.org 

Cc: dev@cloudstack.apache.org 
Subject: Re: https://hub.docker.com/u/apache

Hi Infra-team, dev community,

I've a Dockerfile in one of the apache/cloudstack-primate repo:
https://github.com/apache/cloudstack-primate/blob/master/Dockerfile

What is required for it to be built/hosted on the apache dockerhub
organisation?
For example, https://hub.docker.com/r/apache/cloudstack-primate is still
404.

What is the process of build integration that must be done? Thanks.

Regards

On Thu, Jan 16, 2020 at 3:20 PM Paul Angus  wrote:

> Hi Infra Folks,
>
>
>
> Please could you tell us at Apache CloudStack how we upload and maintain
> images on docker hub under the Apache banner?
>
> Are there any policies that we should be aware of?
>
>
>
>
>
> Many thanks
>
>
>
>
>
>
>
> Paul Angus
>
> Apache CloudStack PMC
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>

[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot removed a comment on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624672725







This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb commented on a change in pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#discussion_r421045958



##
File path: source/adminguide/storage.rst
##
@@ -679,6 +679,19 @@ How to Snapshot a Volume
 
 #. Click the Snapshot button. |SnapshotButton.png|
 
+KVM volume Snapshot specifics
+~
+
+In recent CloudStack versions, by default, creating a volume snapshot for a 
running VM is disabled
+due to a possible volume corruption in certain cases. To enable creating a 
volume snapshots while the VM
+is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.

Review comment:
   I don't see any differences here?
   





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624851015


   I wanna see docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb commented on a change in pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#discussion_r421045958



##
File path: source/adminguide/storage.rst
##
@@ -679,6 +679,19 @@ How to Snapshot a Volume
 
 #. Click the Snapshot button. |SnapshotButton.png|
 
+KVM volume Snapshot specifics
+~
+
+In recent CloudStack versions, by default, creating a volume snapshot for a 
running VM is disabled
+due to a possible volume corruption in certain cases. To enable creating a 
volume snapshots while the VM
+is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.

Review comment:
   I don't see any differences here?
   





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] shwstppr commented on a change in pull request #313: Bootintobios

[GitBox]

shwstppr commented on a change in pull request #313:
URL: https://github.com/apache/cloudstack-primate/pull/313#discussion_r421019131



##
File path: src/config/section/compute.js
##
@@ -104,7 +104,8 @@ export default {
   icon: 'reload',
   label: 'label.action.reboot.instance',
   dataView: true,
-  show: (record) => { return ['Running'].includes(record.state) }
+  show: (record) => { return ['Running'].includes(record.state) },
+  args: ['bootintosetup']

Review comment:
   @DaanHoogland `record.hypervisor` will give you that.
   
   VMs in primate are listed with listvirtualmachinesmetrics API and it only 
has hypervisor param. No parameter named hypervisortype in API response.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] shwstppr commented on a change in pull request #313: Bootintobios

[GitBox]

shwstppr commented on a change in pull request #313:
URL: https://github.com/apache/cloudstack-primate/pull/313#discussion_r421019131



##
File path: src/config/section/compute.js
##
@@ -104,7 +104,8 @@ export default {
   icon: 'reload',
   label: 'label.action.reboot.instance',
   dataView: true,
-  show: (record) => { return ['Running'].includes(record.state) }
+  show: (record) => { return ['Running'].includes(record.state) },
+  args: ['bootintosetup']

Review comment:
   @DaanHoogland `record.hypervisor` with give you that.
   
   VMs in primate are listed with listvirtualmachinesmetrics API and it only 
has hypervisor param. No parameter named hypervisortype in API response.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] DaanHoogland commented on a change in pull request #313: Bootintobios

[GitBox]

DaanHoogland commented on a change in pull request #313:
URL: https://github.com/apache/cloudstack-primate/pull/313#discussion_r421015575



##
File path: src/config/section/compute.js
##
@@ -104,7 +104,8 @@ export default {
   icon: 'reload',
   label: 'label.action.reboot.instance',
   dataView: true,
-  show: (record) => { return ['Running'].includes(record.state) }
+  show: (record) => { return ['Running'].includes(record.state) },
+  args: ['bootintosetup']

Review comment:
   ah too bad, I want to know the hypervisor type for the machine. 
@shwstppr any tips?





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] DaanHoogland commented on a change in pull request #313: Bootintobios

[GitBox]

DaanHoogland commented on a change in pull request #313:
URL: https://github.com/apache/cloudstack-primate/pull/313#discussion_r421015575



##
File path: src/config/section/compute.js
##
@@ -104,7 +104,8 @@ export default {
   icon: 'reload',
   label: 'label.action.reboot.instance',
   dataView: true,
-  show: (record) => { return ['Running'].includes(record.state) }
+  show: (record) => { return ['Running'].includes(record.state) },
+  args: ['bootintosetup']

Review comment:
   ah to bad, I want to know the hypervisor type for the machine. @shwstppr 
any tips?





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] shwstppr commented on a change in pull request #313: Bootintobios

[GitBox]

shwstppr commented on a change in pull request #313:
URL: https://github.com/apache/cloudstack-primate/pull/313#discussion_r421001878



##
File path: src/config/section/compute.js
##
@@ -104,7 +104,8 @@ export default {
   icon: 'reload',
   label: 'label.action.reboot.instance',
   dataView: true,
-  show: (record) => { return ['Running'].includes(record.state) }
+  show: (record) => { return ['Running'].includes(record.state) },
+  args: ['bootintosetup']

Review comment:
   ```suggestion
 args: (record) => { return record.hypervisor === 'VMware' ? 
['bootintosetup'] : [] }
   ```
   @DaanHoogland 
   This should work but currently it seems record is coming undefined from 
AutogenView. I've created PR #327 to fix that.
   `record` here will be the response for `listvirtualmachinesmetrics` response 
item





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] shwstppr opened a new pull request #327: view: fix actionbutton args method resource

[GitBox]

shwstppr opened a new pull request #327:
URL: https://github.com/apache/cloudstack-primate/pull/327


   Fixes undefined `action.resource`,
   
https://github.com/apache/cloudstack-primate/blob/master/src/views/AutogenView.vue#L562



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] DaanHoogland commented on a change in pull request #313: Bootintobios

[GitBox]

DaanHoogland commented on a change in pull request #313:
URL: https://github.com/apache/cloudstack-primate/pull/313#discussion_r420959970



##
File path: src/config/section/compute.js
##
@@ -104,7 +104,8 @@ export default {
   icon: 'reload',
   label: 'label.action.reboot.instance',
   dataView: true,
-  show: (record) => { return ['Running'].includes(record.state) }
+  show: (record) => { return ['Running'].includes(record.state) },
+  args: ['bootintosetup']

Review comment:
   @shwstppr , I should be able to replace this with
   ```
   args: (record) -> { return record.hypervisorType === 'vmware' ? 
['bootintosetup'] : [] }
   ```
   am I? It seems not to work. How can I find what to use as parameter of the 
anonymous function and what attributes it has?
   
   tnx





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] nvazquez commented on a change in pull request #113: kvm-snapshot-explanation

[GitBox]

nvazquez commented on a change in pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#discussion_r420918715



##
File path: source/adminguide/storage.rst
##
@@ -679,6 +679,19 @@ How to Snapshot a Volume
 
 #. Click the Snapshot button. |SnapshotButton.png|
 
+KVM volume Snapshot specifics
+~
+
+In recent CloudStack versions, by default, creating a volume snapshot for a 
running VM is disabled
+due to a possible volume corruption in certain cases. To enable creating a 
volume snapshots while the VM
+is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.

Review comment:
   ```suggestion
   is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.
   
   ```

##
File path: source/adminguide/storage.rst
##
@@ -679,6 +679,19 @@ How to Snapshot a Volume
 
 #. Click the Snapshot button. |SnapshotButton.png|
 
+KVM volume Snapshot specifics
+~
+
+In recent CloudStack versions, by default, creating a volume snapshot for a 
running VM is disabled
+due to a possible volume corruption in certain cases. To enable creating a 
volume snapshots while the VM
+is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.
+The way the volume snapshot is now created has been changed. 

Review comment:
   ```suggestion
   The volume snapshot creation has changed in recent versions:
   
   ```





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624673863


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr113
   
   Build Log Output:
   
   
   No log errors found to report.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624672725


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb removed a comment on pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb removed a comment on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624668794


   requesting docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot removed a comment on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624670001







This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624670001


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr113
   
   Build Log Output:
   
   
   No log errors found to report.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #113: kvm-snapshot-explanation

[GitBox]

ACSGitBot commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624668857


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb commented on pull request #113:
URL: 
https://github.com/apache/cloudstack-documentation/pull/113#issuecomment-624668794


   requesting docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb opened a new pull request #113: kvm-snapshot-explanation

[GitBox]

andrijapanicsb opened a new pull request #113:
URL: https://github.com/apache/cloudstack-documentation/pull/113


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[DISCUSS] Primate - publishing release and docs

[Rohit Yadav]

v community to 
have this sorted, we've a dockerfile in git repo; for "testing only" I was able 
to build and publish image here: https://hub.docker.com/r/cloudstack/primate -- 
I'll remove this once the apache/cloudstack-primate is setup)

Alternative, host on Github: 
https://github.com/apache/cloudstack-primate/packages?package_type=Docker

  4.  Tech Preview releasing:

 *   The versioning is set to: ..- for 
example:
cloudstack-primate-0.4.0-20200506.x86_64.rpm<http://download.cloudstack.org/primate/testing/master/centos/cloudstack-primate-0.4.0-20200506.x86_64.rpm>
cloudstack-primate_0.4.0-20200506_all.deb<http://download.cloudstack.org/primate/testing/master/debian/cloudstack-primate_0.4.0-20200506_all.deb>
cloudstack-primate-0.4.0-20200506.tar.gz<http://download.cloudstack.org/primate/testing/master/cloudstack-primate-0.4.0-20200506.tar.gz>

apache/cloudstack-primate:latest (or some tag similar to above for docker 
builds ^^)

 *   Since this is not the official/GA release, tech preview does not need 
to be voted. Any other thoughts?

 *   Should we do a single tech preview RC/release, or we setup a periodic 
build/release (say every day/week/month) on all the tech preview release 
channels (deb/rpm repositories, dockerhub etc.) This would allow us to take 
feedback/bugs/issues, fix them and release them quickly for users to test.

We already have a daily job that runs builds latest master and rsyncs on 
http://download.cloudstack.org/primate/testing/master/ now (just deb/rpm and 
tar.gz archive). We also have a live QA Primate server that we can build/test 
Primate master against http://primate-qa.cloudstack.cloud:8080/client/master 
(this auto-updates against master every 30mins).


Please discuss and share your feedback, agreements/disagreements, solutions. 
Anything else we should consider?
Thanks.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Andrija Panic]

All,

we will be crafting RC2 release with 2 minor patches (will explain more in
the RC2 voting thread), so please keep your vote for the RC2 and let's stop
the voting process for RC1.

Anyone testing RC1 is NOT expected / not mandatory to retest anything on
RC2, except those 2 patches (to be explained) IF they affect you.

Thanks
Andrija

On Wed, 6 May 2020 at 11:25, Andrija Panic  wrote:

> Thanks Liridon.
>
> p.s. as for the usage server - the first run after you change things will
> not run (not owner of job, etc), but you can hack that (which is what I've
> done, as it seems it was successful), assuming there is only a single usage
> server in your test env.
> - after restarting the usage-server, check it's PID, and then edit the
> last records in the cloud_usage.usage_job tablw to have the new PID and not
> the PID of the previous usage job process.
> - then next run will actually really run (instead of being skipped, that
> one)
>
> Regards,
> Andrija
>
> On Wed, 6 May 2020 at 09:17, Ismaili, Liridon (SWISS TXT) <
> liridon.isma...@swisstxt.ch> wrote:
>
>> Hi Andrija & Daan
>>
>> @Daan I tried that out but without success. However the service seems to
>> be recovered and did run successful. The dates inside the DB are in UTC
>> format but when I list entries from the usage or cloud DB with CloudMonkey
>> I get CEST results.
>> (the GUI did still show me UTC values in the Events but that's may caused
>> by my environment).
>>
>> @Andrija: I would say that it looks good. I also testet the parameters
>> with "Europe/Zurich" but made no difference to me.
>>
>> Regards
>> Liridon
>>
>> -Original Message-
>> From: Andrija Panic > andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
>> Reply-To: dev@cloudstack.apache.org
>> To: us...@cloudstack.apache.org > 22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>,
>> dev mailto:dev%20%3c...@cloudstack.apache.org
>> %3e>>
>> Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
>> Date: Tue, 05 May 2020 19:11:14 +0200
>>
>>
>> Hi Liridon,
>>
>>
>> do you have any feedback about the usage records timing/time zone and
>> such?
>>
>>
>> Thanks
>>
>> Andrija
>>
>>
>> On Mon, 4 May 2020 at 14:32, Daan Hoogland <
>>
>> 
>>
>> daan.hoogl...@gmail.com
>>
>> > wrote:
>>
>>
>> Liridon,
>>
>> "Not owner of usage job, skipping" means there is a PID in the record for
>>
>> this job that isn't the current process. If recognise this and have
>>
>> remedied by setting the process id to null in the record. I'm sure there
>> is
>>
>> some underlying issue that you hit though. Just a workaround.
>>
>>
>> On Mon, May 4, 2020 at 12:56 PM Ismaili, Liridon (SWISS TXT) <
>>
>> 
>>
>> liridon.isma...@swisstxt.ch
>>
>> > wrote:
>>
>>
>> Hi Rohit
>>
>>
>> I tried so and did configure the usage to run 12:45 so I can monitor the
>>
>> behavior. I got the following output:
>>
>> 2020-05-04 12:45:00,002 INFO  [cloud.usage.UsageManagerImpl]
>>
>> (Usage-Job-1:null) (logid:) starting usage job...
>>
>> 2020-05-04 12:45:00,015 DEBUG [cloud.usage.UsageManagerImpl]
>>
>> (Usage-Job-1:null) (logid:) Not owner of usage job, skipping...
>>
>> 2020-05-04 12:45:00,015 INFO  [cloud.usage.UsageManagerImpl]
>>
>> (Usage-Job-1:null) (logid:) usage job complete
>>
>>
>> So the job did not run for some reason... I'm still looking into this. So
>>
>> currently I can't confirm but will update you later as soon as the usage
>>
>> job did run.
>>
>>
>> Regards
>>
>> Liridon
>>
>> -Original Message-
>>
>> From: Rohit Yadav <
>>
>> 
>>
>> rohit.ya...@shapeblue.com
>>
>> >
>> 
>>
>> rohit%20yadav%20%3crohit.ya...@shapeblue.com
>>
>> %3e>>
>>
>> Reply-To:
>>
>> 
>>
>> us...@cloudstack.apache.org
>>
>> >
>> 
>>
>> us...@cloudstack.apache.org
>>
>> >
>>
>> To:
>>
>> 
>>
>> dev@cloudstack.apache.org
>>
>>  <
>>
>> 
>>
>> dev@cloudstack.apache.org
>>
>> >
>> 
>>
>> 22...@cloudstack.apache.org
>>
>> 
>>
>> %22%20%3c...@cloudstack.apache.org
>>
>> %3e>>,
>>
>> 
>>
>> andrija.pa...@gmail.com
>>
>>  <
>>
>> 
>>
>> andrija.pa...@gmail.com
>>
>> >
>> 
>>
>> 22andrija.pa...@gmail.com
>>
>> 
>>
>> %22%20%3candrija.pa...@gmail.com
>>
>> %3e>>,
>>
>> 
>>
>> us...@cloudstack.apache.org
>>
>>  <
>>
>> 
>>
>> us...@cloudstack.apache.org
>>
>> >
>> 
>>
>> 22us...@cloudstack.apache.org
>>
>> 
>>
>> 

[GitHub] [cloudstack-primate] rhtyd commented on pull request #325: [FIX] Translation in Compute Offering/Disk Offering

[GitBox]

rhtyd commented on pull request #325:
URL: 
https://github.com/apache/cloudstack-primate/pull/325#issuecomment-624600526


   cc @shwstppr are lgtm on this?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] Pearl1594 opened a new pull request #326: Form to Migrate data between Image stores

[GitBox]

Pearl1594 opened a new pull request #326:
URL: https://github.com/apache/cloudstack-primate/pull/326


   Enable migration of data between secondary storage pools - addresses 
feature: https://github.com/apache/cloudstack/pull/4053



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: https://hub.docker.com/u/apache

[Rohit Yadav]

Hi Infra-team, dev community,

I've a Dockerfile in one of the apache/cloudstack-primate repo:
https://github.com/apache/cloudstack-primate/blob/master/Dockerfile

What is required for it to be built/hosted on the apache dockerhub
organisation?
For example, https://hub.docker.com/r/apache/cloudstack-primate is still
404.

What is the process of build integration that must be done? Thanks.

Regards

On Thu, Jan 16, 2020 at 3:20 PM Paul Angus  wrote:

> Hi Infra Folks,
>
>
>
> Please could you tell us at Apache CloudStack how we upload and maintain
> images on docker hub under the Apache banner?
>
> Are there any policies that we should be aware of?
>
>
>
>
>
> Many thanks
>
>
>
>
>
>
>
> Paul Angus
>
> Apache CloudStack PMC
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #112: Timezone requirements for 4.14+

[GitBox]

ACSGitBot commented on pull request #112:
URL: 
https://github.com/apache/cloudstack-documentation/pull/112#issuecomment-624589272


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112
   
   Build Log Output:
   
   
   No log errors found to report.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on pull request #112: Timezone requirements for 4.14+

[GitBox]

ACSGitBot removed a comment on pull request #112:
URL: 
https://github.com/apache/cloudstack-documentation/pull/112#issuecomment-624279672







This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #112: Timezone requirements for 4.14+

[GitBox]

andrijapanicsb commented on a change in pull request #112:
URL: 
https://github.com/apache/cloudstack-documentation/pull/112#discussion_r420712619



##
File path: source/upgrading/upgrade/_timezone.rst
##
@@ -0,0 +1,33 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+.. sub-section included in upgrade notes.
+
+Time zone requirements
+##
+
+As of CloudStack 4.14,  you must explicitly configure time zone either in the 
MySQL server or JDBC driver (db.properties).
+In previous CloudStack versions, UTC time zone was assumed by default (all 
event's have UTC time stamps), so
+the same UTC time zone should now be explicitly configured.
+
+You can do this by editing the /etc/cloudstack/management/db.properties file 
and adding "serverTimezone=UTC"
+to the "db.cloud.url.params=" and "db.usage.url.params=" lines.  Example 
lines, from a clean 4.14 installation, are given below:
+
+.. parsed-literal::
+
+   
db.cloud.url.params=prepStmtCacheSize=517=true=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'=UTC
+   db.usage.url.params=serverTimezone=UTC
+
+If you want time stamps in DB to use a different time zone, please make sure 
to test this thoroughly in test environment.

Review comment:
   Removed the whole line, as even when changing this from UTC to 
Europe/Belgrade (CEST) - nothing happens, no dates are changed in DB, so this 
atm can NOT be changed at all.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #112: Timezone requirements for 4.14+

[GitBox]

ACSGitBot commented on pull request #112:
URL: 
https://github.com/apache/cloudstack-documentation/pull/112#issuecomment-624588276


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb removed a comment on pull request #112: Timezone requirements for 4.14+

[GitBox]

andrijapanicsb removed a comment on pull request #112:
URL: 
https://github.com/apache/cloudstack-documentation/pull/112#issuecomment-624279642


   requesting docbuild



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] shwstppr commented on pull request #296: view: fix api error handling

[GitBox]

shwstppr commented on pull request #296:
URL: 
https://github.com/apache/cloudstack-primate/pull/296#issuecomment-624571432


   @rhtyd I've added global method and refactored some code (some more to be 
done).
   Does this look okay or should we handle error notification in 
`src/api/index.js` itself with some flag in `api` method?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Andrija Panic]

Thanks Liridon.

p.s. as for the usage server - the first run after you change things will
not run (not owner of job, etc), but you can hack that (which is what I've
done, as it seems it was successful), assuming there is only a single usage
server in your test env.
- after restarting the usage-server, check it's PID, and then edit the last
records in the cloud_usage.usage_job tablw to have the new PID and not the
PID of the previous usage job process.
- then next run will actually really run (instead of being skipped, that
one)

Regards,
Andrija

On Wed, 6 May 2020 at 09:17, Ismaili, Liridon (SWISS TXT) <
liridon.isma...@swisstxt.ch> wrote:

> Hi Andrija & Daan
>
> @Daan I tried that out but without success. However the service seems to
> be recovered and did run successful. The dates inside the DB are in UTC
> format but when I list entries from the usage or cloud DB with CloudMonkey
> I get CEST results.
> (the GUI did still show me UTC values in the Events but that's may caused
> by my environment).
>
> @Andrija: I would say that it looks good. I also testet the parameters
> with "Europe/Zurich" but made no difference to me.
>
> Regards
> Liridon
>
> -Original Message-
> From: Andrija Panic  andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
> Reply-To: dev@cloudstack.apache.org
> To: us...@cloudstack.apache.org  22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>,
> dev mailto:dev%20%3c...@cloudstack.apache.org
> %3e>>
> Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
> Date: Tue, 05 May 2020 19:11:14 +0200
>
>
> Hi Liridon,
>
>
> do you have any feedback about the usage records timing/time zone and such?
>
>
> Thanks
>
> Andrija
>
>
> On Mon, 4 May 2020 at 14:32, Daan Hoogland <
>
> 
>
> daan.hoogl...@gmail.com
>
> > wrote:
>
>
> Liridon,
>
> "Not owner of usage job, skipping" means there is a PID in the record for
>
> this job that isn't the current process. If recognise this and have
>
> remedied by setting the process id to null in the record. I'm sure there is
>
> some underlying issue that you hit though. Just a workaround.
>
>
> On Mon, May 4, 2020 at 12:56 PM Ismaili, Liridon (SWISS TXT) <
>
> 
>
> liridon.isma...@swisstxt.ch
>
> > wrote:
>
>
> Hi Rohit
>
>
> I tried so and did configure the usage to run 12:45 so I can monitor the
>
> behavior. I got the following output:
>
> 2020-05-04 12:45:00,002 INFO  [cloud.usage.UsageManagerImpl]
>
> (Usage-Job-1:null) (logid:) starting usage job...
>
> 2020-05-04 12:45:00,015 DEBUG [cloud.usage.UsageManagerImpl]
>
> (Usage-Job-1:null) (logid:) Not owner of usage job, skipping...
>
> 2020-05-04 12:45:00,015 INFO  [cloud.usage.UsageManagerImpl]
>
> (Usage-Job-1:null) (logid:) usage job complete
>
>
> So the job did not run for some reason... I'm still looking into this. So
>
> currently I can't confirm but will update you later as soon as the usage
>
> job did run.
>
>
> Regards
>
> Liridon
>
> -Original Message-
>
> From: Rohit Yadav <
>
> 
>
> rohit.ya...@shapeblue.com
>
> 
> 
>
> rohit%20yadav%20%3crohit.ya...@shapeblue.com
>
> %3e>>
>
> Reply-To:
>
> 
>
> us...@cloudstack.apache.org
>
> 
> 
>
> us...@cloudstack.apache.org
>
> >
>
> To:
>
> 
>
> dev@cloudstack.apache.org
>
>  <
>
> 
>
> dev@cloudstack.apache.org
>
> 
> 
>
> 22...@cloudstack.apache.org
>
> 
>
> %22%20%3c...@cloudstack.apache.org
>
> %3e>>,
>
> 
>
> andrija.pa...@gmail.com
>
>  <
>
> 
>
> andrija.pa...@gmail.com
>
> 
> 
>
> 22andrija.pa...@gmail.com
>
> 
>
> %22%20%3candrija.pa...@gmail.com
>
> %3e>>,
>
> 
>
> us...@cloudstack.apache.org
>
>  <
>
> 
>
> us...@cloudstack.apache.org
>
> 
> 
>
> 22us...@cloudstack.apache.org
>
> 
>
> %22%20%3cus...@cloudstack.apache.org
>
> %3e>>
>
> Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
>
> Date: Mon, 04 May 2020 10:16:51 +
>
>
>
> Thanks for testing and sharing your results Liridon!
>
>
>
> Can you also test the case if the usage records have the correct time
>
> according to configured timezone (in global settings) if you're using a
>
> non-UTC timezone?
>
>
>
> I'll add the db.usage.url.paramsl as well in the PR.
>
>
>
>
> Regards,
>
>
>
> Rohit Yadav
>
>
>
> Software Architect, ShapeBlue
>
>
>
> <
>
> 
>
> https://www.shapeblue.com
>
> >
>
>
> 
>
> 

[GitHub] [cloudstack-primate] shwstppr commented on pull request #317: view: fix tab actions permissions check

[GitBox]

shwstppr commented on pull request #317:
URL: 
https://github.com/apache/cloudstack-primate/pull/317#issuecomment-624515128


   @rhtyd I've verified and made changes to disable buttons/actions across UI. 
I've not changed it in custom forms which are called for certain API and will 
be taken care of by permissionchecker



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [ Proposal ] Managing CloudStack Load Balancer configuration

[Wei ZHOU]

cool, Thanks Liridon and Gregor.
We will take them into consideration.

-Wei


On Tue, 5 May 2020 at 15:12, Ismaili, Liridon (SWISS TXT) <
liridon.isma...@swisstxt.ch> wrote:

> Hi Wei,
>
> That's some great improvements to the HAProxy! We couldn't realize some
> projects because of the missing features on the HAProxy therefore we are
> happy to hear that there will be some improvements.
> As an addition to the proposal of you we would like to see the possibility
> to separate timeout settings (client/server/connect/...) as these timeout
> can be different.
> We would also like to have the timeout settings available under the
> LoadbalancerRule
>
> as a summary:
> - Separate options for all timeout parameters (client/server/connect/...)
> - Timeouts also per LoadbalancerRule, not only Network
>
> We also thought about some "nice to have" additions:
> - check customization: HTTP Check, Check Interval, etc.
> - LoadbalancerRule: Custom Server string & Custom Listen string (only
> Domain Admin)
> - Network: Custom Defaults (only Domain Admin)
>
> Please let me know what you think about these additions.
>
> Best Regards
> Liridon
>
> -Original Message-
> From: "Riepl, Gregor (SWISS TXT)"  %22Riepl,%20gregor%20%28swiss%20txt%29%22%20%3cgregor.ri...@swisstxt.ch
> %3e>>
> Reply-To: dev@cloudstack.apache.org
> To: dev@cloudstack.apache.org  22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>
> Subject: Re: [ Proposal ] Managing CloudStack Load Balancer configuration
> Date: Mon, 04 May 2020 10:22:39 +
>
>
> Hi Wei,
>
>
> Thank you for this proposal!
>
> We are also very much interested in this feature.
>
>
> There's a few things we're not quite happy with, though - but we still
> need to discuss this internally a bit.
>
> Liridon or myself will give some feedback soon.
>
>
> Regards,
>
> Gregor
>
> 
>
> From: Wei ZHOU <
>
> 
>
> ustcweiz...@gmail.com
>
> >
>
> Sent: 01 May 2020 08:01
>
> To:
>
> 
>
> dev@cloudstack.apache.org
>
>  <
>
> 
>
> dev@cloudstack.apache.org
>
> >
>
> Subject: [ Proposal ] Managing CloudStack Load Balancer configuration
>
>
> Our improvements to cloudstack load balancer (implemented by HAproxy in the
>
> VRs) allow cloudstack users to manage certain restricted configuration
>
> settings. With this feature, users can
>
>
> * Change basic configuration of HAproxy (e.g. set the amount of allowed
>
> connections),
>
>
> * choose if load balancer is transparent,
>
>
> * enable or disable the support for SSL offloading in isolated networks.
>
>
> * choose if load balancer supports HTTP/2.
>
>
> * more settings.
>
>
>
>
> To make this possible to the user, we provide two forms on cloudstack GUI
>
> (old GUI, will add changes on Primate) from which the settings can be
>
> managed and applied in virtual routers.
>
>
>
>
> FS can be found at
>
> <
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/VR+haproxy+customization+in+CloudStack
> >
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/VR+haproxy+customization+in+CloudStack
>
>
>
>
> Any suggestions ?
>
>
>
>
> Kind regards,
>
>
> *Wei Zhou*
>
>
> Principal Cloud Engineer
>
>
> Leaseweb Global B.V.
>

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Ismaili, Liridon (SWISS TXT)]

Hi Andrija & Daan

@Daan I tried that out but without success. However the service seems to be 
recovered and did run successful. The dates inside the DB are in UTC format but 
when I list entries from the usage or cloud DB with CloudMonkey I get CEST 
results.
(the GUI did still show me UTC values in the Events but that's may caused by my 
environment).

@Andrija: I would say that it looks good. I also testet the parameters with 
"Europe/Zurich" but made no difference to me.

Regards
Liridon

-Original Message-
From: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
Reply-To: dev@cloudstack.apache.org
To: us...@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>,
 dev mailto:dev%20%3c...@cloudstack.apache.org%3e>>
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
Date: Tue, 05 May 2020 19:11:14 +0200


Hi Liridon,


do you have any feedback about the usage records timing/time zone and such?


Thanks

Andrija


On Mon, 4 May 2020 at 14:32, Daan Hoogland <



daan.hoogl...@gmail.com

> wrote:


Liridon,

"Not owner of usage job, skipping" means there is a PID in the record for

this job that isn't the current process. If recognise this and have

remedied by setting the process id to null in the record. I'm sure there is

some underlying issue that you hit though. Just a workaround.


On Mon, May 4, 2020 at 12:56 PM Ismaili, Liridon (SWISS TXT) <



liridon.isma...@swisstxt.ch

> wrote:


Hi Rohit


I tried so and did configure the usage to run 12:45 so I can monitor the

behavior. I got the following output:

2020-05-04 12:45:00,002 INFO  [cloud.usage.UsageManagerImpl]

(Usage-Job-1:null) (logid:) starting usage job...

2020-05-04 12:45:00,015 DEBUG [cloud.usage.UsageManagerImpl]

(Usage-Job-1:null) (logid:) Not owner of usage job, skipping...

2020-05-04 12:45:00,015 INFO  [cloud.usage.UsageManagerImpl]

(Usage-Job-1:null) (logid:) usage job complete


So the job did not run for some reason... I'm still looking into this. So

currently I can't confirm but will update you later as soon as the usage

job did run.


Regards

Liridon

-Original Message-

From: Rohit Yadav <



rohit.ya...@shapeblue.com

mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com>

rohit%20yadav%20%3crohit.ya...@shapeblue.com

%3e>>

Reply-To:



us...@cloudstack.apache.org

mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

>

To:



dev@cloudstack.apache.org

 <



dev@cloudstack.apache.org

mailto:22...@cloudstack.apache.org>

22...@cloudstack.apache.org



%22%20%3c...@cloudstack.apache.org

%3e>>,



andrija.pa...@gmail.com

 <



andrija.pa...@gmail.com

mailto:22andrija.pa...@gmail.com>

22andrija.pa...@gmail.com



%22%20%3candrija.pa...@gmail.com

%3e>>,



us...@cloudstack.apache.org

 <



us...@cloudstack.apache.org

mailto:22us...@cloudstack.apache.org>

22us...@cloudstack.apache.org



%22%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Date: Mon, 04 May 2020 10:16:51 +



Thanks for testing and sharing your results Liridon!



Can you also test the case if the usage records have the correct time

according to configured timezone (in global settings) if you're using a

non-UTC timezone?



I'll add the db.usage.url.paramsl as well in the PR.




Regards,



Rohit Yadav



Software Architect, ShapeBlue



<



https://www.shapeblue.com

>




https://www.shapeblue.com








From: Ismaili, Liridon (SWISS TXT) <


mailto:liridon.isma...@swisstxt.ch>

liridon.isma...@swisstxt.ch

>




liridon.isma...@swisstxt.ch





Sent: Monday, May 4, 2020 15:38


To:


mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>




dev@cloudstack.apache.org



 <


mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>




dev@cloudstack.apache.org



;


mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

>




andrija.pa...@gmail.com



 <


mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

>




andrija.pa...@gmail.com



;


mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

>




us...@cloudstack.apache.org



 <


mailto:us...@cloudstack.apache.org>

[GitHub] [cloudstack-primate] utchoang commented on pull request #324: Create new view component for Tree Domain

[GitBox]

utchoang commented on pull request #324:
URL: 
https://github.com/apache/cloudstack-primate/pull/324#issuecomment-624473727


   Hi @rhytd. I completed fixed it. Please review and let me know your comments.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] utchoang edited a comment on pull request #324: Create new view component for Tree Domain

[GitBox]

utchoang edited a comment on pull request #324:
URL: 
https://github.com/apache/cloudstack-primate/pull/324#issuecomment-624473727


   Hi @rhtyd. I completed fixed it. Please review and let me know your comments.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] DaanHoogland commented on a change in pull request #112: Timezone requirements for 4.14+

[GitBox]

DaanHoogland commented on a change in pull request #112:
URL: 
https://github.com/apache/cloudstack-documentation/pull/112#discussion_r420576090



##
File path: source/upgrading/upgrade/_timezone.rst
##
@@ -0,0 +1,33 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+.. sub-section included in upgrade notes.
+
+Time zone requirements
+##
+
+As of CloudStack 4.14,  you must explicitly configure time zone either in the 
MySQL server or JDBC driver (db.properties).
+In previous CloudStack versions, UTC time zone was assumed by default (all 
event's have UTC time stamps), so
+the same UTC time zone should now be explicitly configured.
+
+You can do this by editing the /etc/cloudstack/management/db.properties file 
and adding "serverTimezone=UTC"
+to the "db.cloud.url.params=" and "db.usage.url.params=" lines.  Example 
lines, from a clean 4.14 installation, are given below:
+
+.. parsed-literal::
+
+   
db.cloud.url.params=prepStmtCacheSize=517=true=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'=UTC
+   db.usage.url.params=serverTimezone=UTC
+
+If you want time stamps in DB to use a different time zone, please make sure 
to test this thoroughly in test environment.

Review comment:
   `If you want time stamps in the DB to use a different time zone, please 
make sure to test this thoroughly in a test environment.`
   (added articles, could be `your` in both cases as well)





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] DaanHoogland commented on a change in pull request #112: Timezone requirements for 4.14+

[GitBox]

DaanHoogland commented on a change in pull request #112:
URL: 
https://github.com/apache/cloudstack-documentation/pull/112#discussion_r420576090



##
File path: source/upgrading/upgrade/_timezone.rst
##
@@ -0,0 +1,33 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+.. sub-section included in upgrade notes.
+
+Time zone requirements
+##
+
+As of CloudStack 4.14,  you must explicitly configure time zone either in the 
MySQL server or JDBC driver (db.properties).
+In previous CloudStack versions, UTC time zone was assumed by default (all 
event's have UTC time stamps), so
+the same UTC time zone should now be explicitly configured.
+
+You can do this by editing the /etc/cloudstack/management/db.properties file 
and adding "serverTimezone=UTC"
+to the "db.cloud.url.params=" and "db.usage.url.params=" lines.  Example 
lines, from a clean 4.14 installation, are given below:
+
+.. parsed-literal::
+
+   
db.cloud.url.params=prepStmtCacheSize=517=true=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'=UTC
+   db.usage.url.params=serverTimezone=UTC
+
+If you want time stamps in DB to use a different time zone, please make sure 
to test this thoroughly in test environment.

Review comment:
   `If you want time stamps in the DB to use a different time zone, please 
make sure to test this thoroughly in a test environment.`





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] utchoang commented on pull request #325: [FIX] Translation in Compute Offering/Disk Offering

[GitBox]

utchoang commented on pull request #325:
URL: 
https://github.com/apache/cloudstack-primate/pull/325#issuecomment-624471894


   Hi @rhtyd  cc @svenvogel. I fixed translation issues at compute/disk 
offering. Thanks.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] utchoang opened a new pull request #325: [FIX] Translation in Compute Offering/Disk Offering

[GitBox]

utchoang opened a new pull request #325:
URL: https://github.com/apache/cloudstack-primate/pull/325


   Open for https://github.com/apache/cloudstack-primate/issues/321



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org