[GitHub] [cloudstack-primate] shwstppr commented on issue #322: [BUG] Updatе compute offering access dialog does not get current state on loading

2020-05-04 Thread GitBox


shwstppr commented on issue #322:
URL: 
https://github.com/apache/cloudstack-primate/issues/322#issuecomment-623859415


   @rhtyd this is because offering item is not refreshed in second window after 
it is updated in the first window. Should we fetch offering's new details when 
the form is opened (I originally added this but it was removed during code 
review 
https://github.com/apache/cloudstack-primate/pull/94/commits/845d0e9e2b317937f435be5c33a56f2a071f5952#diff-a341f854d0c3be2321235491b26f7075L158-L171).
 Moreover this behaviour will be seen across all update actions in UI. cc 
@vladimirpetrov 



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 #307: [FIX] VM Deployment Wizard Changes

2020-05-04 Thread GitBox


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


   Hi @rhtyd I added the show password after deploy VM based on 
https://github.com/apache/cloudstack/blob/master/ui/scripts/instanceWizard.js#L1447.
 But I haven't tested it because I don't know how to do it. Please test me and 
give me your opinion if any.



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 #322: [BUG] Updatе compute offering access dialog does not get current state on loading

2020-05-04 Thread GitBox


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


   @shwstppr pl see



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] svenvogel commented on issue #321: [BUG] Translation (manage storage / service -> compute offering)

2020-05-04 Thread GitBox


svenvogel commented on issue #321:
URL: 
https://github.com/apache/cloudstack-primate/issues/321#issuecomment-623649836


   @utchoang does it fit?



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 #322: [BUG] Updatе compute offering access dialog does not get current state on loading

2020-05-04 Thread GitBox


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


   **Describe the bug**
   The 'Updatе compute offering access' dialog does not read current state of 
variables when loaded. This is visible when using two different browsers with 
the same user - if you change a setting in the first browser, the second does 
not see it until the 'Refresh' button is clicked.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Log in as same user in two different browsers (not tabs in the same 
browser).
   2. Using browser 1 go to 'Offerings > Compute offerings', click on an 
offering and change some parameter there in the 'Update offering access' dialog.
   2. Using browser 2 open the same dialog - you'll see the old state, not the 
modified parameter.
   
   **Expected behavior**
   The dialog should read its current state when loaded.
   
   **Screenshots**
   
![image](https://user-images.githubusercontent.com/12384665/80978215-6efdfb80-8e2e-11ea-9e28-7952c31a45a3.png)
   
   **Desktop (please complete the following information):**
- OS: Ubuntu 18.04 LTS
- Browser: Chrome
- Version: 81.0.4044.129 (Official Build) (64-bit)
   
   **Additional context**
   Related to #303.
   



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 commented on issue #278: [BUG] ISO - Update permissions form does not autodiscover operation, accounts and projects

2020-05-04 Thread GitBox


vladimirpetrov commented on issue #278:
URL: 
https://github.com/apache/cloudstack-primate/issues/278#issuecomment-623456563


   Fix confirmed, closing the issue.



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 commented on issue #303: [BUG] Non-working checkbox when updating compute offering access

2020-05-04 Thread GitBox


vladimirpetrov commented on issue #303:
URL: 
https://github.com/apache/cloudstack-primate/issues/303#issuecomment-623454219


   Fix confirmed, closing the bug.



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

2020-05-04 Thread Daan Hoogland
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%20yadav%20%3crohit.ya...@shapeblue.com%3e>>
> Reply-To: us...@cloudstack.apache.org
> To: dev@cloudstack.apache.org  22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
> andrija.pa...@gmail.com  22andrija.pa...@gmail.com%22%20%3candrija.pa...@gmail.com%3e>>,
> 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
>
>
>
> 
>
> From: Ismaili, Liridon (SWISS TXT) <
>
> 
>
> liridon.isma...@swisstxt.ch
>
> >
>
> Sent: Monday, May 4, 2020 15:38
>
> To:
>
> 
>
> dev@cloudstack.apache.org
>
>  <
>
> 
>
> dev@cloudstack.apache.org
>
> >;
>
> 
>
> andrija.pa...@gmail.com
>
>  <
>
> 
>
> andrija.pa...@gmail.com
>
> >;
>
> 
>
> us...@cloudstack.apache.org
>
>  <
>
> 
>
> us...@cloudstack.apache.org
>
> >
>
> Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
>
>
> Hi Rohit
>
>
> That did the trick! I did remove all the timezone information on my.cnf
> and only added the timezone information on the db.properties file.
>
> So I can confirm it fixes the issue.
>
>
> If you are using the usage service too you will also need to specify the
> timezone information for the usage DB:
>
> "db.usage.url.params=" in the /etc/cloudstack/management/db.properties
> file. Otherwise the usage service won't be able to start.
>
>
> This did also fix my issue and all my dates inside the db are now in the
> correct time zone! I'll also update the Github PR so we can track it there.
>
>
> Many thanks and Regards
>
> Liridon
>
>
> 
>
> rohit.ya...@shapeblue.com
>
>
>
> 
>
> www.shapeblue.com
>
>
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
>
> @shapeblue
>
>
>
>
>
>
>
> -Original Message-
>
> From: "Ismaili, Liridon (SWISS TXT)" <
>
> 
>
> liridon.isma...@swisstxt.ch
>
> 
>  >
>
> %20liridon%20%28swiss%20txt%29%22%20%3cliridon.isma...@swisstxt.ch
>
> %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
>
> 
> 
>
> 

[GitHub] [cloudstack-documentation] ACSGitBot commented on pull request #95: WIP: Update "What's new in" 4.14

2020-05-04 Thread GitBox


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


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr95
   
   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 #95: WIP: Update "What's new in" 4.14

2020-05-04 Thread GitBox


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


   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 #95: WIP: Update "What's new in" 4.14

2020-05-04 Thread GitBox


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


   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




Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

2020-05-04 Thread Ismaili, Liridon (SWISS TXT)
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 
mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com%3e>>
Reply-To: us...@cloudstack.apache.org
To: dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
 andrija.pa...@gmail.com 
mailto:%22andrija.pa...@gmail.com%22%20%3candrija.pa...@gmail.com%3e>>,
 us...@cloudstack.apache.org 
mailto:%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





From: Ismaili, Liridon (SWISS TXT) <



liridon.isma...@swisstxt.ch

>

Sent: Monday, May 4, 2020 15:38

To:



dev@cloudstack.apache.org

 <



dev@cloudstack.apache.org

>;



andrija.pa...@gmail.com

 <



andrija.pa...@gmail.com

>;



us...@cloudstack.apache.org

 <



us...@cloudstack.apache.org

>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1


Hi Rohit


That did the trick! I did remove all the timezone information on my.cnf and 
only added the timezone information on the db.properties file.

So I can confirm it fixes the issue.


If you are using the usage service too you will also need to specify the 
timezone information for the usage DB:

"db.usage.url.params=" in the /etc/cloudstack/management/db.properties file. 
Otherwise the usage service won't be able to start.


This did also fix my issue and all my dates inside the db are now in the 
correct time zone! I'll also update the Github PR so we can track it there.


Many thanks and Regards

Liridon




rohit.ya...@shapeblue.com





www.shapeblue.com


3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK

@shapeblue







-Original Message-

From: "Ismaili, Liridon (SWISS TXT)" <



liridon.isma...@swisstxt.ch



%20liridon%20%28swiss%20txt%29%22%20%3cliridon.isma...@swisstxt.ch

%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 09:53:35 +



Hi Rohit



I'll test that and let you know.



Regards


Liridon



-Original Message-


From: Rohit Yadav <


mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

>




rohit.ya...@shapeblue.com



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

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

>




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



%3e>>


Reply-To:



[GitHub] [cloudstack-primate] rhtyd commented on issue #286: [BUG] As root admin cannot see instances in Kubernetes cluster created as user

2020-05-04 Thread GitBox


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


   I've confirmed this, closing.



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 #280: [BUG] Kubernetes ISO are not searchable

2020-05-04 Thread GitBox


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


   This needs fixing in backend and Primate will automatically support that, 
closing this one as I've opened 
https://github.com/apache/cloudstack/issues/4056 cc @borisstoyanov 



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 #307: [FIX] VM Deployment Wizard Changes

2020-05-04 Thread GitBox


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


   Travis may pass in next run.
   @utchoang can you have a look at #51 



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 #249: [BUG] Incorrect user name shown in top right corner

2020-05-04 Thread GitBox


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


   @vladimirpetrov  cc @borisstoyanov can you look into this and see if you can 
reproduce it. I cannot.



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 #51: Password enabled VM to display password popup

2020-05-04 Thread GitBox


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


   @utchoang can you check/fix the deployment wizard to show the VM password if 
VM has a password enabled template. The password is returned by the VM response 
`json.virtualmachine.password`. This is already fixed for start VM and reset VM 
actions.



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

2020-05-04 Thread Riepl, Gregor (SWISS TXT)
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 
Sent: 01 May 2020 08:01
To: 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


Any suggestions ?



Kind regards,

*Wei Zhou*

Principal Cloud Engineer

Leaseweb Global B.V.


Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

2020-05-04 Thread Rohit Yadav
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


From: Ismaili, Liridon (SWISS TXT) 
Sent: Monday, May 4, 2020 15:38
To: dev@cloudstack.apache.org ; 
andrija.pa...@gmail.com ; us...@cloudstack.apache.org 

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Rohit

That did the trick! I did remove all the timezone information on my.cnf and 
only added the timezone information on the db.properties file.
So I can confirm it fixes the issue.

If you are using the usage service too you will also need to specify the 
timezone information for the usage DB:
"db.usage.url.params=" in the /etc/cloudstack/management/db.properties file. 
Otherwise the usage service won't be able to start.

This did also fix my issue and all my dates inside the db are now in the 
correct time zone! I'll also update the Github PR so we can track it there.

Many thanks and Regards
Liridon

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


-Original Message-
From: "Ismaili, Liridon (SWISS TXT)" 
mailto:%22Ismaili,%20liridon%20%28swiss%20txt%29%22%20%3cliridon.isma...@swisstxt.ch%3e>>
Reply-To: us...@cloudstack.apache.org
To: dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
 andrija.pa...@gmail.com 
mailto:%22andrija.pa...@gmail.com%22%20%3candrija.pa...@gmail.com%3e>>,
 us...@cloudstack.apache.org 
mailto:%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 09:53:35 +


Hi Rohit


I'll test that and let you know.


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:



dev@cloudstack.apache.org

mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>

To: Andrija Panic <



andrija.pa...@gmail.com

mailto:andrija%20panic%20%3candrija.pa...@gmail.com>

andrija%20panic%20%3candrija.pa...@gmail.com

%3e>>, users <



us...@cloudstack.apache.org

mailto:users%20%3cus...@cloudstack.apache.org>

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

%3e>>,



dev@cloudstack.apache.org

 <



dev@cloudstack.apache.org

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

%22...@cloudstack.apache.org



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

%3e>>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Date: Mon, 04 May 2020 09:50:10 +



Hi Andrija, all,



While adding support for Java 11, the mysql-connector 8.x java dependency was 
introduced from previous 5.7x version.



According to


<



https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html

>




https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html



 it seems we can specify the server time in connection parameters. Can any 
users test this workaround and confirm if it fixes their issue in their 
test/upgrade environments by adding  "=UTC" to the 
"db.cloud.url.params=" in the /etc/cloudstack/management/db.properties file, 
revert changes for mysql server and restart the management server.



Draft PR proposed:


<



https://github.com/apache/cloudstack/pull/4055/files

>




https://github.com/apache/cloudstack/pull/4055/files





We may then either discuss to either include the above PR or document this in 
our release/upgrade notes. Thanks.




Regards,



Rohit Yadav



Software Architect, ShapeBlue



<



https://www.shapeblue.com

>




https://www.shapeblue.com








From: Andrija Panic <


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

andrija.pa...@gmail.com

>




andrija.pa...@gmail.com





Sent: Friday, May 1, 2020 22:38


To: users <


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

us...@cloudstack.apache.org

>




us...@cloudstack.apache.org



; Rohit Yadav <



[GitHub] [cloudstack-primate] vladimirpetrov opened a new issue #180: [BUG] Identify and access > Domains > delete domain does not remove it from the tree

2020-05-04 Thread GitBox


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


   **Describe the bug**
   When you delete a domain in 'Identify and access > Domains' it does not 
remove it from the tree even though it's actually deleted.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Go to 'Identify and access > Domains' and select a domain
   2. Click on 'Delete domain' icon and confirm the operations. 
   3. Look at the domain tree - it's still there. If you try to click on the 
deleted domain, it's not shown though.
   
   **Expected behavior**
   The deleted domain should be removed from the domain tree.
   
   **Screenshots**
   None
   
   **Desktop (please complete the following information):**
   - OS: Windows 10 Pro x64
   - Browser: Chrome
   - Version: 80.0.3987.116 (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 #180: [BUG] Identify and access > Domains > delete domain does not remove it from the tree

2020-05-04 Thread GitBox


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


   @vladimirpetrov cc @borisstoyanov please re-test the domain view tree and 
list views against old UI, confirm and close this against latest master.



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 #219: Identify and access - Domain - Delete domain does not remove it from the tree

2020-05-04 Thread GitBox


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


   @utchoang the code has created a lot of dependencies in AutogenView which it 
shouldn't - at some point in future technical debt needs to be paid by creating 
an entire new view component 



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

2020-05-04 Thread Ismaili, Liridon (SWISS TXT)
Hi Rohit

That did the trick! I did remove all the timezone information on my.cnf and 
only added the timezone information on the db.properties file.
So I can confirm it fixes the issue.

If you are using the usage service too you will also need to specify the 
timezone information for the usage DB:
"db.usage.url.params=" in the /etc/cloudstack/management/db.properties file. 
Otherwise the usage service won't be able to start.

This did also fix my issue and all my dates inside the db are now in the 
correct time zone! I'll also update the Github PR so we can track it there.

Many thanks and Regards
Liridon

-Original Message-
From: "Ismaili, Liridon (SWISS TXT)" 
mailto:%22Ismaili,%20liridon%20%28swiss%20txt%29%22%20%3cliridon.isma...@swisstxt.ch%3e>>
Reply-To: us...@cloudstack.apache.org
To: dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
 andrija.pa...@gmail.com 
mailto:%22andrija.pa...@gmail.com%22%20%3candrija.pa...@gmail.com%3e>>,
 us...@cloudstack.apache.org 
mailto:%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 09:53:35 +


Hi Rohit


I'll test that and let you know.


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:



dev@cloudstack.apache.org

mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>

To: Andrija Panic <



andrija.pa...@gmail.com

mailto:andrija%20panic%20%3candrija.pa...@gmail.com>

andrija%20panic%20%3candrija.pa...@gmail.com

%3e>>, users <



us...@cloudstack.apache.org

mailto:users%20%3cus...@cloudstack.apache.org>

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

%3e>>,



dev@cloudstack.apache.org

 <



dev@cloudstack.apache.org

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

%22...@cloudstack.apache.org



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

%3e>>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Date: Mon, 04 May 2020 09:50:10 +



Hi Andrija, all,



While adding support for Java 11, the mysql-connector 8.x java dependency was 
introduced from previous 5.7x version.



According to


<



https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html

>




https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html



 it seems we can specify the server time in connection parameters. Can any 
users test this workaround and confirm if it fixes their issue in their 
test/upgrade environments by adding  "=UTC" to the 
"db.cloud.url.params=" in the /etc/cloudstack/management/db.properties file, 
revert changes for mysql server and restart the management server.



Draft PR proposed:


<



https://github.com/apache/cloudstack/pull/4055/files

>




https://github.com/apache/cloudstack/pull/4055/files





We may then either discuss to either include the above PR or document this in 
our release/upgrade notes. Thanks.




Regards,



Rohit Yadav



Software Architect, ShapeBlue



<



https://www.shapeblue.com

>




https://www.shapeblue.com








From: Andrija Panic <


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

andrija.pa...@gmail.com

>




andrija.pa...@gmail.com





Sent: Friday, May 1, 2020 22:38


To: users <


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

us...@cloudstack.apache.org

>




us...@cloudstack.apache.org



; Rohit Yadav <


mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

>




rohit.ya...@shapeblue.com





Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1



@Rohit Yadavmailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

>




rohit.ya...@shapeblue.com



can you possibly advice on the time zone issue? I've seen this on another ML 
thread as well. We are mostly in UTC (test envs) so this might be the reason we 
didn't see this...could be just a documentation update that is needed.



@Robert is there any specifics to your NFS server (i.e. a forbidden NFSv3 or 
similar)? Also, can you please open a GitHub issue and provide the same there? 
So we can 

[GitHub] [cloudstack-primate] vladimirpetrov commented on issue #302: [BUG] The 'Public' checkbox in 'Update compute offering access' is not working

2020-05-04 Thread GitBox


vladimirpetrov commented on issue #302:
URL: 
https://github.com/apache/cloudstack-primate/issues/302#issuecomment-623375450


   Somehow I got confused and logged this bug twice. Closing it as duplicate of 
#303.



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 removed a comment on issue #302: [BUG] The 'Public' checkbox in 'Update compute offering access' is not working

2020-05-04 Thread GitBox


vladimirpetrov removed a comment on issue #302:
URL: 
https://github.com/apache/cloudstack-primate/issues/302#issuecomment-623375122


   Somehow I got confused and logged this bug twice. Closing it as duplicate of 
#302.



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 commented on issue #302: [BUG] The 'Public' checkbox in 'Update compute offering access' is not working

2020-05-04 Thread GitBox


vladimirpetrov commented on issue #302:
URL: 
https://github.com/apache/cloudstack-primate/issues/302#issuecomment-623375122


   Somehow I got confused and logged this bug twice. Closing it as duplicate of 
#302.



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 #243: [BUG] 'Create SSH Key Pair' differences

2020-05-04 Thread GitBox


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


   @vladimirpetrov cc @borisstoyanov please test latest master and close. 
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] vladimirpetrov opened a new issue #243: [BUG] 'Create SSH Key Pair' differences

2020-05-04 Thread GitBox


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


   **Describe the bug**
   The dialogs for 'Create SSH Key Pair' are different in Primate and the old 
UI.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Go to 'Compute > SSH Key Pairs' and click the 'Create SSH Key Pair' icon. 
Look at the dialog.
   
   **Expected behavior**
   The dialog in Primate UI must be the same as in the old UI.
   
   **Screenshots**
   Primate UI:
   
![image](https://user-images.githubusercontent.com/12384665/77072326-3036f200-69f6-11ea-993c-5884d90f9924.png)
   
   Old UI:
   
![image](https://user-images.githubusercontent.com/12384665/77072375-40e76800-69f6-11ea-8cf3-0c0d5ffd81f5.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




Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

2020-05-04 Thread Ismaili, Liridon (SWISS TXT)
Hi Rohit

I'll test that and let you know.

Regards
Liridon

-Original Message-
From: Rohit Yadav 
mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com%3e>>
Reply-To: dev@cloudstack.apache.org
To: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>,
 users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>,
 dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
Date: Mon, 04 May 2020 09:50:10 +


Hi Andrija, all,


While adding support for Java 11, the mysql-connector 8.x java dependency was 
introduced from previous 5.7x version.


According to



https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html

 it seems we can specify the server time in connection parameters. Can any 
users test this workaround and confirm if it fixes their issue in their 
test/upgrade environments by adding  "=UTC" to the 
"db.cloud.url.params=" in the /etc/cloudstack/management/db.properties file, 
revert changes for mysql server and restart the management server.


Draft PR proposed:



https://github.com/apache/cloudstack/pull/4055/files



We may then either discuss to either include the above PR or document this in 
our release/upgrade notes. Thanks.



Regards,


Rohit Yadav


Software Architect, ShapeBlue




https://www.shapeblue.com





From: Andrija Panic <



andrija.pa...@gmail.com

>

Sent: Friday, May 1, 2020 22:38

To: users <



us...@cloudstack.apache.org

>; Rohit Yadav <



rohit.ya...@shapeblue.com

>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1


@Rohit Yadavmailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

> can you possibly advice on the time zone issue? I've seen this on another ML 
> thread as well. We are mostly in UTC (test envs) so this might be the reason 
> we didn't see this...could be just a documentation update that is needed.


@Robert is there any specifics to your NFS server (i.e. a forbidden NFSv3 or 
similar)? Also, can you please open a GitHub issue and provide the same there? 
So we can track it and collaborate - I've not seen this one before.

What packages did you use for the installation? On the issue you'll raise, 
please also include the relevant output from the /var/log/cloud.log from inside 
the SSVM

Also not sure what is the relation between MySQL and JRE at all - they should 
have nothing in common?


Thanks!


Andrija






rohit.ya...@shapeblue.com





www.shapeblue.com


3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK

@shapeblue






On Fri, 1 May 2020 at 17:49, Robert Ward <



rww...@gmail.com

mailto:rww...@gmail.com>

rww...@gmail.com

>> wrote:

Hi all,


I too have run into an issues while performing a clean install:

Centos 7, MySQL 5.6, JRE 11


JRE 11 and MySQL 5.6 don't see to play well on two points:


Installing JRE before MySQL causes MYSQL to "lockup" on startup. I have found 
that if I install JRE after MySQL that issue is resolved.


MySQL chokes with timezone error @ cloudstack-setup-management. In my case 
MySQL doesn't like "EDT" as a timezone. Resolved by adding this to etc/my.cnf:


default-time-zone= "-05:00"


On my last point CS has difficulty with mounting secondary storage. I have 
clipped the logs to the point where I think the problem lies:


2020-05-01 10:55:07,871 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] 
(StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) getCommandHostDelegation: 
class com.cloud.agent.api.GetStorageStatsCommand

2020-05-01 10:55:07,871 DEBUG [c.c.h.XenServerGuru] 
(StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) We are returning the default 
host to execute commands because the command is not of Copy type.

2020-05-01 10:55:07,910 DEBUG [c.c.a.t.Request] (AgentManager-Handler-8:null) 
(logid:) Seq 2-4356951164504244991: Processing:  { Ans: , MgmtId: 144345337593, 
via: 2, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
 GetRootDir for nfs://192.168.25.1/export/secondary<



http://192.168.25.1/export/secondary

> failed due to com.cloud.utils.exception.CloudRuntimeException: Unable to 
> mount 192.168.25.1:/export/secondary at 
> /mnt/SecStorage/b7e9e158-ed80-3a62-a5d7-1992c991d829 due to mount.nfs: 
> requested NFS version or transport protocol is not supported\n\tat 
> 

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

2020-05-04 Thread Rohit Yadav
Hi Andrija, all,

While adding support for Java 11, the mysql-connector 8.x java dependency was 
introduced from previous 5.7x version.

According to 
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html
 it seems we can specify the server time in connection parameters. Can any 
users test this workaround and confirm if it fixes their issue in their 
test/upgrade environments by adding  "=UTC" to the 
"db.cloud.url.params=" in the /etc/cloudstack/management/db.properties file, 
revert changes for mysql server and restart the management server.

Draft PR proposed:
https://github.com/apache/cloudstack/pull/4055/files

We may then either discuss to either include the above PR or document this in 
our release/upgrade notes. Thanks.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Andrija Panic 
Sent: Friday, May 1, 2020 22:38
To: users ; Rohit Yadav 
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

@Rohit Yadav can you possibly advice on the 
time zone issue? I've seen this on another ML thread as well. We are mostly in 
UTC (test envs) so this might be the reason we didn't see this...could be just 
a documentation update that is needed.

@Robert is there any specifics to your NFS server (i.e. a forbidden NFSv3 or 
similar)? Also, can you please open a GitHub issue and provide the same there? 
So we can track it and collaborate - I've not seen this one before.
What packages did you use for the installation? On the issue you'll raise, 
please also include the relevant output from the /var/log/cloud.log from inside 
the SSVM
Also not sure what is the relation between MySQL and JRE at all - they should 
have nothing in common?

Thanks!

Andrija



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

On Fri, 1 May 2020 at 17:49, Robert Ward 
mailto:rww...@gmail.com>> wrote:
Hi all,

I too have run into an issues while performing a clean install:
Centos 7, MySQL 5.6, JRE 11

JRE 11 and MySQL 5.6 don't see to play well on two points:

Installing JRE before MySQL causes MYSQL to "lockup" on startup. I have found 
that if I install JRE after MySQL that issue is resolved.

MySQL chokes with timezone error @ cloudstack-setup-management. In my case 
MySQL doesn't like "EDT" as a timezone. Resolved by adding this to etc/my.cnf:

default-time-zone= "-05:00"

On my last point CS has difficulty with mounting secondary storage. I have 
clipped the logs to the point where I think the problem lies:

2020-05-01 10:55:07,871 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] 
(StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) getCommandHostDelegation: 
class com.cloud.agent.api.GetStorageStatsCommand
2020-05-01 10:55:07,871 DEBUG [c.c.h.XenServerGuru] 
(StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) We are returning the default 
host to execute commands because the command is not of Copy type.
2020-05-01 10:55:07,910 DEBUG [c.c.a.t.Request] (AgentManager-Handler-8:null) 
(logid:) Seq 2-4356951164504244991: Processing:  { Ans: , MgmtId: 144345337593, 
via: 2, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
 GetRootDir for 
nfs://192.168.25.1/export/secondary 
failed due to com.cloud.utils.exception.CloudRuntimeException: Unable to mount 
192.168.25.1:/export/secondary at 
/mnt/SecStorage/b7e9e158-ed80-3a62-a5d7-1992c991d829 due to mount.nfs: 
requested NFS version or transport protocol is not supported\n\tat 
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:2458)\n\tat
 
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:2208)\n\tat
 
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:292)\n\tat
 
com.cloud.storage.resource.PremiumSecondaryStorageResource.defaultAction(PremiumSecondaryStorageResource.java:64)\n\tat
 
com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:60)\n\tat
 com.cloud.agent.Agent.processRequest(Agent.java:644)\n\tat 
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1057)\n\tat 
com.cloud.utils.nio.Task.call(Task.java:83)\n\tat 
com.cloud.utils.nio.Task.call(Task.java:29)\n\tat 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n\tat 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
 java.base/java.lang.Thread.run(Thread.java:834)\n","wait":0}}] }

My troubleshooting steps:

restart SSVM
restart MS
restart agent
verify I can manually mount secondary storage on agent and 

[GitHub] [cloudstack-primate] vladimirpetrov commented on issue #301: [BUG] Missing domain parameter when updating compute offering access

2020-05-04 Thread GitBox


vladimirpetrov commented on issue #301:
URL: 
https://github.com/apache/cloudstack-primate/issues/301#issuecomment-623364126


   Fix confirmed, closing the issue.



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 #284: view: actions in template/iso zones

2020-05-04 Thread GitBox


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


   @rhtyd merged latest master



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 #284: view: actions in template/iso zones

2020-05-04 Thread GitBox


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


   @shwstppr can you merge latest master on this branch and resolve conflict?



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] borisstoyanov opened a new issue #278: [BUG] ISO - Update permissions form does not autodiscover operation, accounts and projects

2020-05-04 Thread GitBox


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


   **Describe the bug**
   Update permissions form does not autodiscover operation, accounts and 
projects
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Go to ISOs
   2. Select an iso
   3. Click on Update permissioins
   4. See that fields are not autodiscovering operation/account/project
   
   **Expected behavior**
   There should be dropdown option for the fields 
   
   **Screenshots**
   ![Screenshot 2020-04-02 at 16 38 
52](https://user-images.githubusercontent.com/13551960/78256061-c1cb5700-7500-11ea-9648-e929f345b543.png)
   
   



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 #278: [BUG] ISO - Update permissions form does not autodiscover operation, accounts and projects

2020-05-04 Thread GitBox


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


   @borisstoyanov @vladimirpetrov 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 issue #303: [BUG] Non-working checkbox when updating compute offering access

2020-05-04 Thread GitBox


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


   @vladimirpetrov please test against 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 issue #301: [BUG] Missing domain parameter when updating compute offering access

2020-05-04 Thread GitBox


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


   @vladimirpetrov please test against 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 issue #302: [BUG] The 'Public' checkbox in 'Update compute offering access' is not working

2020-05-04 Thread GitBox


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


   @vladimirpetrov please test against 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] svenvogel opened a new issue #321: [BUG] Translation (manage storage / service -> compute offering)

2020-05-04 Thread GitBox


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


   **Describe the bug**
   Translation in Compute Offering is Missing. 
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Compute -> Compute Offerings
   2. Add a new Offer
   3. "compute offering type" needs to be translated, "customconstrained", 
"customunconstrained"
   and
   4. select "QoS Type" -> Storage -> "iscustomizeddiskiops", "diskiopsmin", 
"diskopsmax"
   and
   5. select "QoS Type" -> Hypervisor -> "diskbytesreadrate", 
"diskbyteswriterate", "diskiopsreadrate", "diskiopswriterate"
   
   **Expected behavior**
   A clear and concise description of what you expected to happen.
   
   **Screenshots**
   
![image](https://user-images.githubusercontent.com/5433844/80947177-e3fe1080-8def-11ea--6e529c00d1fc.png)
   
![image](https://user-images.githubusercontent.com/5433844/80947394-64247600-8df0-11ea-9a3b-26ceaa5cfefd.png)
   



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 edited a comment on pull request #316: view: list filtering

2020-05-04 Thread GitBox


shwstppr edited a comment on pull request #316:
URL: 
https://github.com/apache/cloudstack-primate/pull/316#issuecomment-623288874


   @rhtyd I've implemented table column filtering with antd here 
https://github.com/shapeblue/cloudstack-primate/tree/feature-list-filter-alt
   ![Screenshot from 2020-05-04 
12-14-03](https://user-images.githubusercontent.com/153340/80941816-05b3c380-8e01-11ea-8d00-197ed93e8b69.png)
   
   Since default filtering UI shows checkboxes and API won't support multiple 
states for filtering, I'll have to implement custom UI for that. Will update 
once done
   



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 #316: view: list filtering

2020-05-04 Thread GitBox


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


   @rhtyd I've implemented table column filtering with antd here 
https://github.com/shapeblue/cloudstack-primate/tree/feature-list-filter-alt
   ![Screenshot from 2020-05-04 
12-14-03](https://user-images.githubusercontent.com/153340/80941816-05b3c380-8e01-11ea-8d00-197ed93e8b69.png)
   
   Since default filtering UI shows checkboxes and API won't support multiple 
states for filtering, I'll have to implement custom UI
   



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 #319: Explore Test Automation

2020-05-04 Thread GitBox


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


   Close because another PR 
https://github.com/apache/cloudstack-primate/pull/320 was opened.



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 #320: Explore Test Automation

2020-05-04 Thread GitBox


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


   Open for #299



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 #319: Explore Test Automation

2020-05-04 Thread GitBox


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


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



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