Re: [DISCUSS] [IMPORTANT] CloudStack 4.14 release WITH updated UI

Paul, not much reaction so far, :( I would prefer to have them both be installed separately when I `require cloudstack` or ` install cloudstack`, but still be able to install them separately if i want them on different machines i.e. `install cloudstack-management` or alternatively `install

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #887: compute: startVirtualMachine - Fetching pods clusters hosts from vm zone

blueorangutan commented on pull request #887: URL: https://github.com/apache/cloudstack-primate/pull/887#issuecomment-738569670 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/887

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #887: compute: startVirtualMachine - Fetching pods clusters hosts from vm zone

blueorangutan commented on pull request #887: URL: https://github.com/apache/cloudstack-primate/pull/887#issuecomment-738567026 @davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

[GitHub] [cloudstack-primate] davidjumani commented on pull request #887: compute: startVirtualMachine - Fetching pods clusters hosts from vm zone

davidjumani commented on pull request #887: URL: https://github.com/apache/cloudstack-primate/pull/887#issuecomment-738566886 @blueorangutan package This is an automated message from the Apache Git Service. To respond to

[GitHub] [cloudstack-primate] davidjumani opened a new pull request #887: compute: startVirtualMachine - Fetching pods clusters hosts from vm zone

davidjumani opened a new pull request #887: URL: https://github.com/apache/cloudstack-primate/pull/887 Fixes https://github.com/apache/cloudstack-primate/issues/836 This is an automated message from the Apache Git

Re: [DISCUSS][RELEASE] Apache CloudStack Release Process

Hi Sven, I do not see a need for two separate votes as long as the people understand that there are two sets of artifacts that are being voted. Many projects release multiple artifacts from the same repository and the fact that there are two repositories doesn't change the basic release vote

[DISCUSS][RELEASE] Apache CloudStack Release Process

Hi Board of Directors, We need to sort out a release issue. The Apache CloudStack Project have two repos "cloudstack" and "cloudstack-primate". Do we need for release have two separate votes of each of them or is it possible to make one vote at once for both? Maybe its more easy for the

[DISCUSS] [IMPORTANT] CloudStack 4.14 release WITH updated UI

PMC members, PLEASE ONLY RESPOND ON THE DEV THREAD. Hi all, Please read all of this, I know it's a bit wordy.. We're pretty much there wrt to RC1 of CloudStack and the updated UI. We have one issue remaining, and that is about the packaging and voting on CloudStack 'engine' and its

[GitHub] [cloudstack-primate] slavkap commented on issue #836: [BASIC NETWORK TESTING]

slavkap commented on issue #836: URL: https://github.com/apache/cloudstack-primate/issues/836#issuecomment-738128935 Hi @rhtyd I've just tried simple scenarios - to deploy vm, create template from snapshot and deploy vm from it. If you can help me with scenarios for basic network I

Re: [DISCUSS][RELEASE] 4.15 merges and milestone

Hi Daan, Thanks for all the hard work on this. I don't believe there are any other outstanding items from what I can see. Looks like we're ready! -Si From: Daan Hoogland Sent: Thursday, December 3, 2020 8:14 AM To: dev Subject: Re: [DISCUSS][RELEASE] 4.15

Re: [DISCUSS][RELEASE] 4.15 merges and milestone

That's awesome! Things are looking good for a RC1. Do we have any due time for it? Em qui., 3 de dez. de 2020 às 11:14, Daan Hoogland escreveu: > Hello again, > > I have just merged the last critical item for 4.14 and 4.15. All other PRs > are (or should be) moved to future milestones. > I

Re: [DISCUSS][RELEASE] 4.15 merges and milestone

Hello again, I have just merged the last critical item for 4.14 and 4.15. All other PRs are (or should be) moved to future milestones. I think we are ready for releases. thoughts anyone? On Mon, Nov 23, 2020 at 2:45 PM Daan Hoogland wrote: > as of now there are one PR marked as critical for

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #886: Disable edit and delete of UI read-only settings

blueorangutan commented on pull request #886: URL: https://github.com/apache/cloudstack-primate/pull/886#issuecomment-737872315 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/886

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #886: Disable edit and delete of UI read-only settings

blueorangutan commented on pull request #886: URL: https://github.com/apache/cloudstack-primate/pull/886#issuecomment-737867527 @Pearl1594 a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

[GitHub] [cloudstack-primate] Pearl1594 commented on pull request #886: Disable edit and delete of UI read-only settings

Pearl1594 commented on pull request #886: URL: https://github.com/apache/cloudstack-primate/pull/886#issuecomment-737867092 @blueorangutan package This is an automated message from the Apache Git Service. To respond to the

[GitHub] [cloudstack-primate] Pearl1594 opened a new pull request #886: Disable edit and delete of UI read-only settings

Pearl1594 opened a new pull request #886: URL: https://github.com/apache/cloudstack-primate/pull/886 Added a setting - cpuNumber to the "user.vm.readonly.ui.details" global setting. Doing so should prevent a user from editing the value for the UI, however this isn't the case. This PR

[GitHub] [cloudstack-primate] davidjumani edited a comment on pull request #885: createnetworkform: Displaying api errors

davidjumani edited a comment on pull request #885: URL: https://github.com/apache/cloudstack-primate/pull/885#issuecomment-737780550 @rhtyd Changing the error response will require a backend fix. This just copies the old UI functionality so the user knows that an error has occurred

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #880: Close snapshot form in case of an error

blueorangutan commented on pull request #880: URL: https://github.com/apache/cloudstack-primate/pull/880#issuecomment-737829394 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/880

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #880: Close snapshot form in case of an error

blueorangutan commented on pull request #880: URL: https://github.com/apache/cloudstack-primate/pull/880#issuecomment-737818622 @davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

[GitHub] [cloudstack-primate] davidjumani commented on pull request #880: Close snapshot form in case of an error

davidjumani commented on pull request #880: URL: https://github.com/apache/cloudstack-primate/pull/880#issuecomment-737817793 @blueorangutan package This is an automated message from the Apache Git Service. To respond to

[GitHub] [cloudstack-primate] Pearl1594 commented on pull request #880: Close snapshot form in case of an error

Pearl1594 commented on pull request #880: URL: https://github.com/apache/cloudstack-primate/pull/880#issuecomment-737790499 @blueorangutan package This is an automated message from the Apache Git Service. To respond to the

[GitHub] [cloudstack-primate] davidjumani commented on pull request #885: createnetworkform: Displaying api errors

davidjumani commented on pull request #885: URL: https://github.com/apache/cloudstack-primate/pull/885#issuecomment-737780550 @rhtyd Changing the error response will require a backend fix. This just copies the old UI functionality so the user knows that an error has occurred trying to

[GitHub] [cloudstack-primate] rhtyd commented on pull request #885: createnetworkform: Displaying api errors

rhtyd commented on pull request #885: URL: https://github.com/apache/cloudstack-primate/pull/885#issuecomment-737767085 @davidjumani actually the error is not very clear, I'll let @DaanHoogland @PaulAngus advise further on this.

[GitHub] [cloudstack-primate] rhtyd commented on issue #836: [BASIC NETWORK TESTING]

rhtyd commented on issue #836: URL: https://github.com/apache/cloudstack-primate/issues/836#issuecomment-737766635 @slavkap @weizhouapache @GabrielBrascher @wido - any further update on running tests with basic zone/networking against latest master? Thanks.

[GitHub] [cloudstack-primate] andrijapanicsb commented on issue #882: [BUG] When editing physical network traffic labels - existing labels are not shown

andrijapanicsb commented on issue #882: URL: https://github.com/apache/cloudstack-primate/issues/882#issuecomment-737739234 Tested, LGTM - thx. This is an automated message from the Apache Git Service. To respond to the

[GitHub] [cloudstack-primate] andrijapanicsb closed issue #882: [BUG] When editing physical network traffic labels - existing labels are not shown

andrijapanicsb closed issue #882: URL: https://github.com/apache/cloudstack-primate/issues/882 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL