[GitHub] [cloudstack-cloudmonkey] synergiator opened a new issue #65: If not sudo strange file lock error / CloudMonkey 6.0.0 (build: 74ff37c, 2019-03-05T17:27:26+0530)
synergiator opened a new issue #65: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/65 Just discovered this exception: ``` Failed to grab config file lock, please try again panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x6973c1] goroutine 1 [running]: github.com/apache/cloudstack-cloudmonkey/config.(*Config).UpdateConfig(0xca84e0, 0x76bbda, 0x6, 0x7ffec3d4f642, 0x5, 0x0) /home/rohit/lab/apache/cloudmonkey/config/config.go:283 +0x421 main.main() /home/rohit/lab/apache/cloudmonkey/cmk.go:63 +0x45e ``` Which files does `cmk` need to lock here? Workaround: sudo 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-cloudmonkey] rhtyd commented on issue #65: If not sudo strange file lock error / CloudMonkey 6.0.0 (build: 74ff37c, 2019-03-05T17:27:26+0530)
rhtyd commented on issue #65: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/65#issuecomment-652243335 @synergiator thanks for reporting the issue. Yes, cmk needs to create its config directory at $HOME/.cmk where it stores config, profiles etc. When running just make sure your user/process has access to allow cloudmonkey to create and manipulate its config/history/profile/cache files. This is not different from what cmk v6.0.0 does, can you test and check if you're getting the same issue with older (6.0.0) version of cloudmonkey as well? Or, it could be a permission fix (for example run: sudo chown -R : ~/.cmk in case the cmk config path/files are owned by root user) Can you also share your platform and OS (such as x86_64, Linux) etc. 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-cloudmonkey] rhtyd edited a comment on issue #65: If not sudo strange file lock error / CloudMonkey 6.0.0 (build: 74ff37c, 2019-03-05T17:27:26+0530)
rhtyd edited a comment on issue #65: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/65#issuecomment-652243335 @synergiator thanks for reporting the issue. Yes, cmk needs to create its config directory at $HOME/.cmk where it stores config, profiles etc. When running just make sure your user/process has access to allow cloudmonkey to create and manipulate its config/history/profile/cache files. It could be a permission issue (for example run: sudo chown -R : ~/.cmk in case the cmk config path/files are owned by root user) Can you also share your platform and OS (such as x86_64, Linux) etc. 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] borisstoyanov commented on pull request #353: UI changes for Dynamic roles improvements
borisstoyanov commented on pull request #353: URL: https://github.com/apache/cloudstack-primate/pull/353#issuecomment-652246144 @blueorangutan package 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] blueorangutan commented on pull request #353: UI changes for Dynamic roles improvements
blueorangutan commented on pull request #353: URL: https://github.com/apache/cloudstack-primate/pull/353#issuecomment-652246608 @borisstoyanov a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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: [DISCUSS] Management server default port conflict
I think we can document in our CloudStack qig/release/install notes to say users must disable cockpit on CentOS8. Here are my 2paisas; * Most users using CentOS (7/8) won't use a single-host specific management tool/UI such as cockpit; they would probably use some fleet management software or automate using ansible/puppet/ceph etc. * Last time I checked the minimal CentOS-8 ISO does not install cockpit or that it is enabled by default (service does not run by default until you active the port 9090 target) * Some users may have monitoring scripts/tools or security rules that expect port 9090 to be used by CloudStack, so it's probably safer to ask users to change port for cockpit than CloudStack by default Regards. From: Abhishek Kumar Sent: Wednesday, July 1, 2020 11:14 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: [DISCUSS] Management server default port conflict Hi all, I would like to know everyone's opinion regarding an issue seen with CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). CentOS8 comes with cockpit (https://cockpit-project.org/) installed which uses port 9090, although it is not active by default. CloudStack management server also needs port 9090. And when CloudStack management server is started with systemd it triggers the start of cockpit first and management server fails to start, 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) (logid:) Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Failed to configure ClusterManagerImpl javax.naming.ConfigurationException: Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:144) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:121) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:232) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:116) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:78) at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:57) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContex
[GitHub] [cloudstack-primate] blueorangutan commented on pull request #353: UI changes for Dynamic roles improvements
blueorangutan commented on pull request #353: URL: https://github.com/apache/cloudstack-primate/pull/353#issuecomment-652250436 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/353 (JID-2172) 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: [DISCUSS] Management server default port conflict
Besides updating the documentation, I'm tempted to even explicitly add a command that would disable the cockpit service on boot and stop it (and echo the message that we've disabled it...)- as part of the cloudstack-setup-management or similar. Otherwise, novice users will certainly stumble sooner or later on this issue. On Wed, 1 Jul 2020 at 09:34, Rohit Yadav wrote: > I think we can document in our CloudStack qig/release/install notes to say > users must disable cockpit on CentOS8. Here are my 2paisas; > > * Most users using CentOS (7/8) won't use a single-host specific > management tool/UI such as cockpit; they would probably use some fleet > management software or automate using ansible/puppet/ceph etc. > * Last time I checked the minimal CentOS-8 ISO does not install > cockpit or that it is enabled by default (service does not run by default > until you active the port 9090 target) > * Some users may have monitoring scripts/tools or security rules that > expect port 9090 to be used by CloudStack, so it's probably safer to ask > users to change port for cockpit than CloudStack by default > > Regards. > > > From: Abhishek Kumar > Sent: Wednesday, July 1, 2020 11:14 > To: dev@cloudstack.apache.org ; > us...@cloudstack.apache.org > Subject: [DISCUSS] Management server default port conflict > > Hi all, > > I would like to know everyone's opinion regarding an issue seen with > CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). > CentOS8 comes with cockpit (https://cockpit-project.org/) installed which > uses port 9090, although it is not active by default. CloudStack management > server also needs port 9090. And when CloudStack management server is > started with systemd it triggers the start of cockpit first and management > server fails to start, > > > 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) > (logid:) Detected that another management node with the same IP 10.10.2.167 > is already running, please check your cluster configuration > 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] > (main:null) (logid:) Failed to configure ClusterManagerImpl > javax.naming.ConfigurationException: Detected that another management node > with the same IP 10.10.2.167 is already running, please check your cluster > configuration > at > com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) > at > com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) > at > org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) > at > org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) > at > org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) > at > org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) > at > org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122) > at > org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:144) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:121) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:232) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:116) > at > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(Def
Re: [DISCUSS] Management server default port conflict
if cockpit uses 9090, then stop it, otherwise not stop it? On Wed, 1 Jul 2020 at 10:18, Andrija Panic wrote: > Besides updating the documentation, I'm tempted to even explicitly add a > command that would disable the cockpit service on boot and stop it (and > echo the message that we've disabled it...)- as part of the > cloudstack-setup-management or similar. > Otherwise, novice users will certainly stumble sooner or later on this > issue. > > > On Wed, 1 Jul 2020 at 09:34, Rohit Yadav > wrote: > > > I think we can document in our CloudStack qig/release/install notes to > say > > users must disable cockpit on CentOS8. Here are my 2paisas; > > > > * Most users using CentOS (7/8) won't use a single-host specific > > management tool/UI such as cockpit; they would probably use some fleet > > management software or automate using ansible/puppet/ceph etc. > > * Last time I checked the minimal CentOS-8 ISO does not install > > cockpit or that it is enabled by default (service does not run by default > > until you active the port 9090 target) > > * Some users may have monitoring scripts/tools or security rules that > > expect port 9090 to be used by CloudStack, so it's probably safer to ask > > users to change port for cockpit than CloudStack by default > > > > Regards. > > > > > > From: Abhishek Kumar > > Sent: Wednesday, July 1, 2020 11:14 > > To: dev@cloudstack.apache.org ; > > us...@cloudstack.apache.org > > Subject: [DISCUSS] Management server default port conflict > > > > Hi all, > > > > I would like to know everyone's opinion regarding an issue seen with > > CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). > > CentOS8 comes with cockpit (https://cockpit-project.org/) installed > which > > uses port 9090, although it is not active by default. CloudStack > management > > server also needs port 9090. And when CloudStack management server is > > started with systemd it triggers the start of cockpit first and > management > > server fails to start, > > > > > > 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) > > (logid:) Detected that another management node with the same IP > 10.10.2.167 > > is already running, please check your cluster configuration > > 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] > > (main:null) (logid:) Failed to configure ClusterManagerImpl > > javax.naming.ConfigurationException: Detected that another management > node > > with the same IP 10.10.2.167 is already running, please check your > cluster > > configuration > > at > > > com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) > > at > > > com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) > > at > > > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) > > at > > > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) > > at > > > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) > > at > > > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) > > at > > > org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) > > at > > > org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) > > at > > > org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) > > at > > > org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) > > at > > > org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122) > > at > > > org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894) > > at > > > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) > > at > > > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:144) > > at > > > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:121) > > at > > > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244) > > at > > > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) > > at > > > org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) > > at > > > org.apache.cloud
[GitHub] [cloudstack-primate] rhtyd merged pull request #252: Add support to manage network service providers
rhtyd merged pull request #252: URL: https://github.com/apache/cloudstack-primate/pull/252 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 #252: Add support to manage network service providers
rhtyd commented on pull request #252: URL: https://github.com/apache/cloudstack-primate/pull/252#issuecomment-652277114 Good work @utchoang LGTM will merge now! 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 #235: Compute > Instances - Missing extended search functionality
rhtyd commented on pull request #235: URL: https://github.com/apache/cloudstack-primate/pull/235#issuecomment-652277680 @utchoang can you fix the conflicts? 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] rhtyd commented on pull request #298: Quota UI
rhtyd commented on pull request #298: URL: https://github.com/apache/cloudstack-primate/pull/298#issuecomment-652277539 @utchoang can you fix the conflicts? 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] rhtyd commented on pull request #326: Form to Migrate data between Image stores
rhtyd commented on pull request #326: URL: https://github.com/apache/cloudstack-primate/pull/326#issuecomment-652278287 @Pearl1594 can you fix the merge conflict? 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] rhtyd commented on pull request #472: Fixing permission issues
rhtyd commented on pull request #472: URL: https://github.com/apache/cloudstack-primate/pull/472#issuecomment-652278987 @blueorangutan package 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 #469: Diabling actions for readonly admin
rhtyd commented on pull request #469: URL: https://github.com/apache/cloudstack-primate/pull/469#issuecomment-652278885 @blueorangutan package 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 #458: Adding quick-view options to list view
rhtyd commented on pull request #458: URL: https://github.com/apache/cloudstack-primate/pull/458#issuecomment-652278709 @davidjumani can you fix the 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] rhtyd commented on pull request #436: feature: template ovf properties
rhtyd commented on pull request #436: URL: https://github.com/apache/cloudstack-primate/pull/436#issuecomment-652278506 @blueorangutan package 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] blueorangutan commented on pull request #436: feature: template ovf properties
blueorangutan commented on pull request #436: URL: https://github.com/apache/cloudstack-primate/pull/436#issuecomment-652279174 @rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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 #478: Creating custom form to delete vm
rhtyd commented on pull request #478: URL: https://github.com/apache/cloudstack-primate/pull/478#issuecomment-652279173 @blueorangutan package 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 #474: Hide order column for user account
rhtyd commented on pull request #474: URL: https://github.com/apache/cloudstack-primate/pull/474#issuecomment-652279053 @blueorangutan package 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] blueorangutan commented on pull request #478: Creating custom form to delete vm
blueorangutan commented on pull request #478: URL: https://github.com/apache/cloudstack-primate/pull/478#issuecomment-652279530 @rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] blueorangutan commented on pull request #472: Fixing permission issues
blueorangutan commented on pull request #472: URL: https://github.com/apache/cloudstack-primate/pull/472#issuecomment-652279819 @rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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 #470: VM deployment form group template/iso
rhtyd commented on pull request #470: URL: https://github.com/apache/cloudstack-primate/pull/470#issuecomment-652279882 @blueorangutan package 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] blueorangutan commented on pull request #474: Hide order column for user account
blueorangutan commented on pull request #474: URL: https://github.com/apache/cloudstack-primate/pull/474#issuecomment-652279666 @rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] blueorangutan commented on pull request #469: Diabling actions for readonly admin
blueorangutan commented on pull request #469: URL: https://github.com/apache/cloudstack-primate/pull/469#issuecomment-652279950 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] blueorangutan commented on pull request #470: VM deployment form group template/iso
blueorangutan commented on pull request #470: URL: https://github.com/apache/cloudstack-primate/pull/470#issuecomment-652280581 @rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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 merged pull request #470: VM deployment form group template/iso
rhtyd merged pull request #470: URL: https://github.com/apache/cloudstack-primate/pull/470 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] blueorangutan commented on pull request #472: Fixing permission issues
blueorangutan commented on pull request #472: URL: https://github.com/apache/cloudstack-primate/pull/472#issuecomment-652284924 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/472 (JID-2176) 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 a change in pull request #474: Hide order column for user account
rhtyd commented on a change in pull request #474:
URL: https://github.com/apache/cloudstack-primate/pull/474#discussion_r448214497
##
File path: src/views/AutogenView.vue
##
@@ -485,6 +485,10 @@ export default {
}
}
+ if (!['Admin'].includes(this.$store.getters.userInfo.roletype) &&
this.apiName === 'listTemplates' && this.selectedFilter !== 'self') {
Review comment:
@Pearl1594 do we need to check for the selected filter; shouldn't we not
display the order column irrespective of that? Maybe check against old 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] rhtyd commented on pull request #235: Compute > Instances - Missing extended search functionality
rhtyd commented on pull request #235: URL: https://github.com/apache/cloudstack-primate/pull/235#issuecomment-652285656 @blueorangutan package 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 #298: Quota UI
rhtyd commented on pull request #298: URL: https://github.com/apache/cloudstack-primate/pull/298#issuecomment-652285606 @blueorangutan package 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] blueorangutan commented on pull request #235: Compute > Instances - Missing extended search functionality
blueorangutan commented on pull request #235: URL: https://github.com/apache/cloudstack-primate/pull/235#issuecomment-652286392 @rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] blueorangutan commented on pull request #298: Quota UI
blueorangutan commented on pull request #298: URL: https://github.com/apache/cloudstack-primate/pull/298#issuecomment-652286537 @rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] blueorangutan commented on pull request #436: feature: template ovf properties
blueorangutan commented on pull request #436: URL: https://github.com/apache/cloudstack-primate/pull/436#issuecomment-652287866 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/436 (JID-2173) 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 commented on a change in pull request #474: Hide order column for user account
Pearl1594 commented on a change in pull request #474:
URL: https://github.com/apache/cloudstack-primate/pull/474#discussion_r448217919
##
File path: src/views/AutogenView.vue
##
@@ -485,6 +485,10 @@ export default {
}
}
+ if (!['Admin'].includes(this.$store.getters.userInfo.roletype) &&
this.apiName === 'listTemplates' && this.selectedFilter !== 'self') {
Review comment:
@rhtyd In the old UI - the order column is shown for all users , but the
backend API prevents it from ordering them with the following exception:
```
Domain Admin and regular users can modify only their own Public templates
```
Hence, to adhere to this - I've exposed the order column only for those that
it owns
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 opened a new issue #479: Review and compare translation keys and doclinks usage and migration of translation from old UI
rhtyd opened a new issue #479: URL: https://github.com/apache/cloudstack-primate/issues/479 @utchoang cc @svenvogel can you help do the following: - Review entire Primate codebase and fix any wrong usage of `$tr(...` translation key usage or code (i.e. fix any incorrect key or check/use an existing key from locales/en.json) - Compare the legacy UI translation file (https://github.com/apache/cloudstack/blob/master/ui/l10n/en.js) against Primate's locales/en.json (may few other languages for sanity checks like de_DE, ja_JP, fr_FR etc) and see if we missed anything - Check and fix or add `docHelp` keys and paths in the src/router/... section js files for actions, listviews etc. The `docHelp` allows to add path relative to the docs website http://docs.cloudstack.apache.org/en/latest/ Let me know if anything is not clear, 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] rhtyd commented on a change in pull request #474: Hide order column for user account
rhtyd commented on a change in pull request #474:
URL: https://github.com/apache/cloudstack-primate/pull/474#discussion_r448220356
##
File path: src/views/AutogenView.vue
##
@@ -485,6 +485,10 @@ export default {
}
}
+ if (!['Admin'].includes(this.$store.getters.userInfo.roletype) &&
this.apiName === 'listTemplates' && this.selectedFilter !== 'self') {
Review comment:
@Pearl1594 so if an account owns templates, could they update and change
order for their own (public) templates? Instead, we can just enforce that the
order columns are shown only to the root admin.
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] blueorangutan commented on pull request #470: VM deployment form group template/iso
blueorangutan commented on pull request #470: URL: https://github.com/apache/cloudstack-primate/pull/470#issuecomment-652290720 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/470 (JID-2178) 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] blueorangutan commented on pull request #469: Diabling actions for readonly admin
blueorangutan commented on pull request #469: URL: https://github.com/apache/cloudstack-primate/pull/469#issuecomment-652290840 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/469 (JID-2177) 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] blueorangutan commented on pull request #478: Creating custom form to delete vm
blueorangutan commented on pull request #478: URL: https://github.com/apache/cloudstack-primate/pull/478#issuecomment-652291187 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/478 (JID-2174) 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] blueorangutan commented on pull request #474: Hide order column for user account
blueorangutan commented on pull request #474: URL: https://github.com/apache/cloudstack-primate/pull/474#issuecomment-652291040 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/474 (JID-2175) 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 commented on a change in pull request #474: Hide order column for user account
Pearl1594 commented on a change in pull request #474:
URL: https://github.com/apache/cloudstack-primate/pull/474#discussion_r448221510
##
File path: src/views/AutogenView.vue
##
@@ -485,6 +485,10 @@ export default {
}
}
+ if (!['Admin'].includes(this.$store.getters.userInfo.roletype) &&
this.apiName === 'listTemplates' && this.selectedFilter !== 'self') {
Review comment:
The API allows users and dom admins to change the order of their own
public templates. However, I can restrict this only to Root admin
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] blueorangutan commented on pull request #298: Quota UI
blueorangutan commented on pull request #298: URL: https://github.com/apache/cloudstack-primate/pull/298#issuecomment-652291401 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/298 (JID-2180) 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] blueorangutan commented on pull request #235: Compute > Instances - Missing extended search functionality
blueorangutan commented on pull request #235: URL: https://github.com/apache/cloudstack-primate/pull/235#issuecomment-652293042 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/235 (JID-2179) 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 #298: Quota UI
rhtyd commented on pull request #298: URL: https://github.com/apache/cloudstack-primate/pull/298#issuecomment-652293929 @utchoang I still see no usage of slots, are you working on doing a separate component implementation and use slots instead of extending AutogenView? 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 #298: Quota UI
rhtyd commented on pull request #298: URL: https://github.com/apache/cloudstack-primate/pull/298#issuecomment-652302553 @utchoang you can create a new component and in that import and use autogenview instead of the other way around, then in your new component you can pass templates etc into slots that you define in Autogenview. 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] davidjumani commented on pull request #474: Hide order column for user account
davidjumani commented on pull request #474: URL: https://github.com/apache/cloudstack-primate/pull/474#issuecomment-652302746 @blueorangutan package 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] blueorangutan commented on pull request #474: Hide order column for user account
blueorangutan commented on pull request #474: URL: https://github.com/apache/cloudstack-primate/pull/474#issuecomment-652303390 @davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] davidjumani commented on a change in pull request #382: Enabling Role based Users in Projects
davidjumani commented on a change in pull request #382:
URL: https://github.com/apache/cloudstack-primate/pull/382#discussion_r448266337
##
File path: src/components/view/ResourceView.vue
##
@@ -101,6 +102,19 @@ export default {
this.networkService = response.listnetworksresponse.network[0]
})
}
+ if (this.resource.projectaccountname) {
+var projectAccountList = []
+api('listProjectAccounts', { projectid: this.resource.id
}).then(response => {
+ projectAccountList =
response.listprojectaccountsresponse.projectaccount
+ for (var pa in projectAccountList) {
+if ((projectAccountList[pa].userid &&
'fetchUser(projectAccountList[pa].userid)'.username ===
this.$store.getters.userInfo.username) ||
Review comment:
Why is this a string when it is a function call ?
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: [DISCUSS] Management server default port conflict
+1, agree with Rohit On 2020-07-01 08:34, Rohit Yadav wrote: I think we can document in our CloudStack qig/release/install notes to say users must disable cockpit on CentOS8. Here are my 2paisas; * Most users using CentOS (7/8) won't use a single-host specific management tool/UI such as cockpit; they would probably use some fleet management software or automate using ansible/puppet/ceph etc. * Last time I checked the minimal CentOS-8 ISO does not install cockpit or that it is enabled by default (service does not run by default until you active the port 9090 target) * Some users may have monitoring scripts/tools or security rules that expect port 9090 to be used by CloudStack, so it's probably safer to ask users to change port for cockpit than CloudStack by default Regards. From: Abhishek Kumar Sent: Wednesday, July 1, 2020 11:14 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: [DISCUSS] Management server default port conflict Hi all, I would like to know everyone's opinion regarding an issue seen with CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). CentOS8 comes with cockpit (https://cockpit-project.org/) installed which uses port 9090, although it is not active by default. CloudStack management server also needs port 9090. And when CloudStack management server is started with systemd it triggers the start of cockpit first and management server fails to start, 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) (logid:) Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Failed to configure ClusterManagerImpl javax.naming.ConfigurationException: Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:144) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:121) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:232) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:116) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:78) at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:57) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(C
Re: [DISCUSS] Management server default port conflict
+1 with adding documentation. And maybe we should also refactor the port check logic and error message. Currently, code just tries to connect the socket for the port and if it fails that with the message, Detected that another management node with the same IP XX.XX.XX.XX is already running, please check your cluster configuration Instead of the cockpit, it can be any other service/process. Should we try to get details of that service in the logs, exception message so the user can make changes? Regards, Abhishek From: Rohit Yadav Sent: 01 July 2020 13:04 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: Re: [DISCUSS] Management server default port conflict I think we can document in our CloudStack qig/release/install notes to say users must disable cockpit on CentOS8. Here are my 2paisas; * Most users using CentOS (7/8) won't use a single-host specific management tool/UI such as cockpit; they would probably use some fleet management software or automate using ansible/puppet/ceph etc. * Last time I checked the minimal CentOS-8 ISO does not install cockpit or that it is enabled by default (service does not run by default until you active the port 9090 target) * Some users may have monitoring scripts/tools or security rules that expect port 9090 to be used by CloudStack, so it's probably safer to ask users to change port for cockpit than CloudStack by default Regards. From: Abhishek Kumar Sent: Wednesday, July 1, 2020 11:14 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: [DISCUSS] Management server default port conflict Hi all, I would like to know everyone's opinion regarding an issue seen with CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). CentOS8 comes with cockpit (https://cockpit-project.org/) installed which uses port 9090, although it is not active by default. CloudStack management server also needs port 9090. And when CloudStack management server is started with systemd it triggers the start of cockpit first and management server fails to start, 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) (logid:) Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Failed to configure ClusterManagerImpl javax.naming.ConfigurationException: Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:144) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:121) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:232)
[GitHub] [cloudstack-documentation] nvazquez merged pull request #94: Add update ISO permissions
nvazquez merged pull request #94: URL: https://github.com/apache/cloudstack-documentation/pull/94 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: [DISCUSS] Management server default port conflict
If the open source community just got their act together and registered their ports and stopped using ports registered to other projects, this would not happen. There is no shortage of available ports, there is just a complete lack of professionalism in the community and it causes unnecessary headaches for users. Stop using ports registered to other projects. Register the ports for Cloudstack and encourage/insist that others do so as well. Publicly shame projects and products that use ports that they have not registered. To set a good example, in documentation and examples stop using ports in the registered range for applications that should use ports in the private/dynamic range. Ron On 2020-07-01 7:36 a.m., Abhishek Kumar wrote: +1 with adding documentation. And maybe we should also refactor the port check logic and error message. Currently, code just tries to connect the socket for the port and if it fails that with the message, Detected that another management node with the same IP XX.XX.XX.XX is already running, please check your cluster configuration Instead of the cockpit, it can be any other service/process. Should we try to get details of that service in the logs, exception message so the user can make changes? Regards, Abhishek From: Rohit Yadav Sent: 01 July 2020 13:04 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: Re: [DISCUSS] Management server default port conflict I think we can document in our CloudStack qig/release/install notes to say users must disable cockpit on CentOS8. Here are my 2paisas; * Most users using CentOS (7/8) won't use a single-host specific management tool/UI such as cockpit; they would probably use some fleet management software or automate using ansible/puppet/ceph etc. * Last time I checked the minimal CentOS-8 ISO does not install cockpit or that it is enabled by default (service does not run by default until you active the port 9090 target) * Some users may have monitoring scripts/tools or security rules that expect port 9090 to be used by CloudStack, so it's probably safer to ask users to change port for cockpit than CloudStack by default Regards. From: Abhishek Kumar Sent: Wednesday, July 1, 2020 11:14 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: [DISCUSS] Management server default port conflict Hi all, I would like to know everyone's opinion regarding an issue seen with CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). CentOS8 comes with cockpit (https://cockpit-project.org/) installed which uses port 9090, although it is not active by default. CloudStack management server also needs port 9090. And when CloudStack management server is started with systemd it triggers the start of cockpit first and management server fails to start, 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) (logid:) Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Failed to configure ClusterManagerImpl javax.naming.ConfigurationException: Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) at org.apache.cl
[GitHub] [cloudstack-primate] Pearl1594 opened a new pull request #480: Hide status column for users other than Root admin
Pearl1594 opened a new pull request #480: URL: https://github.com/apache/cloudstack-primate/pull/480 This attempts to fix hiding the status column for users other than Root Admins for templates and ISOs not owned by it. Addresses: https://github.com/apache/cloudstack-primate/issues/476 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] blueorangutan commented on pull request #480: Hide status column for users other than Root admin
blueorangutan commented on pull request #480: URL: https://github.com/apache/cloudstack-primate/pull/480#issuecomment-652441456 @Pearl1594 a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] blueorangutan commented on pull request #480: Hide status column for users other than Root admin
blueorangutan commented on pull request #480: URL: https://github.com/apache/cloudstack-primate/pull/480#issuecomment-652446377 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/480 (JID-2182) 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] blueorangutan commented on pull request #326: Form to Migrate data between Image stores
blueorangutan commented on pull request #326: URL: https://github.com/apache/cloudstack-primate/pull/326#issuecomment-652473632 @Pearl1594 a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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 commented on pull request #326: Form to Migrate data between Image stores
Pearl1594 commented on pull request #326: URL: https://github.com/apache/cloudstack-primate/pull/326#issuecomment-652473349 @blueorangutan package 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] blueorangutan commented on pull request #326: Form to Migrate data between Image stores
blueorangutan commented on pull request #326: URL: https://github.com/apache/cloudstack-primate/pull/326#issuecomment-652478352 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/326 (JID-2183) 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] PaulAngus commented on issue #475: [BUG] Many screens show Account and Domain to non-root admins when they should not.
PaulAngus commented on issue #475: URL: https://github.com/apache/cloudstack-primate/issues/475#issuecomment-652521370 Agreed, **_most_** screens will display the user's own account and domain. Therefore it's redundant data, so it's 'silly' to display it. on the screens that **are** leaking data, not showing the data in the UI makes the problem 'less bad', but agreed, it is an API problem to start with. 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: [DISCUSS] Management server default port conflict
(true that, Ron...) On Wed, 1 Jul 2020, 15:27 Ron Wheeler, wrote: > If the open source community just got their act together and registered > their ports and stopped using ports registered to other projects, this > would not happen. > > There is no shortage of available ports, there is just a complete lack > of professionalism in the community and it causes unnecessary headaches > for users. > > Stop using ports registered to other projects. > Register the ports for Cloudstack and encourage/insist that others do so > as well. > Publicly shame projects and products that use ports that they have not > registered. > To set a good example, in documentation and examples stop using ports in > the registered range for applications that should use ports in the > private/dynamic range. > > > Ron > > > On 2020-07-01 7:36 a.m., Abhishek Kumar wrote: > > +1 with adding documentation. > > > > And maybe we should also refactor the port check logic and error > message. Currently, code just tries to connect the socket for the port and > if it fails that with the message, > > Detected that another management node with the same IP XX.XX.XX.XX is > already running, please check your cluster configuration > > Instead of the cockpit, it can be any other service/process. Should we > try to get details of that service in the logs, exception message so the > user can make changes? > > > > Regards, > > Abhishek > > > > From: Rohit Yadav > > Sent: 01 July 2020 13:04 > > To: dev@cloudstack.apache.org ; > us...@cloudstack.apache.org > > Subject: Re: [DISCUSS] Management server default port conflict > > > > I think we can document in our CloudStack qig/release/install notes to > say users must disable cockpit on CentOS8. Here are my 2paisas; > > > >* Most users using CentOS (7/8) won't use a single-host specific > management tool/UI such as cockpit; they would probably use some fleet > management software or automate using ansible/puppet/ceph etc. > >* Last time I checked the minimal CentOS-8 ISO does not install > cockpit or that it is enabled by default (service does not run by default > until you active the port 9090 target) > >* Some users may have monitoring scripts/tools or security rules > that expect port 9090 to be used by CloudStack, so it's probably safer to > ask users to change port for cockpit than CloudStack by default > > > > Regards. > > > > > > From: Abhishek Kumar > > Sent: Wednesday, July 1, 2020 11:14 > > To: dev@cloudstack.apache.org ; > us...@cloudstack.apache.org > > Subject: [DISCUSS] Management server default port conflict > > > > Hi all, > > > > I would like to know everyone's opinion regarding an issue seen with > CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). > CentOS8 comes with cockpit (https://cockpit-project.org/) installed which > uses port 9090, although it is not active by default. CloudStack management > server also needs port 9090. And when CloudStack management server is > started with systemd it triggers the start of cockpit first and management > server fails to start, > > > > > > 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) > (logid:) Detected that another management node with the same IP 10.10.2.167 > is already running, please check your cluster configuration > > 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] > (main:null) (logid:) Failed to configure ClusterManagerImpl > > javax.naming.ConfigurationException: Detected that another management > node with the same IP 10.10.2.167 is already running, please check your > cluster configuration > > at > com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) > > at > com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) > > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) > > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) > > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) > > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) > > at > org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) > > at > org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) > > at > org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) > > at > org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) > > at > org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(
Re: [DISCUSS] Management server default port conflict
Is there any hope of getting projects to follow the rules? One would think that Cloudstack developers would be the most likely to understand networking, the Internet and system administration. Ron On 2020-07-01 12:53 p.m., Andrija Panic wrote: (true that, Ron...) On Wed, 1 Jul 2020, 15:27 Ron Wheeler, wrote: If the open source community just got their act together and registered their ports and stopped using ports registered to other projects, this would not happen. There is no shortage of available ports, there is just a complete lack of professionalism in the community and it causes unnecessary headaches for users. Stop using ports registered to other projects. Register the ports for Cloudstack and encourage/insist that others do so as well. Publicly shame projects and products that use ports that they have not registered. To set a good example, in documentation and examples stop using ports in the registered range for applications that should use ports in the private/dynamic range. Ron On 2020-07-01 7:36 a.m., Abhishek Kumar wrote: +1 with adding documentation. And maybe we should also refactor the port check logic and error message. Currently, code just tries to connect the socket for the port and if it fails that with the message, Detected that another management node with the same IP XX.XX.XX.XX is already running, please check your cluster configuration Instead of the cockpit, it can be any other service/process. Should we try to get details of that service in the logs, exception message so the user can make changes? Regards, Abhishek From: Rohit Yadav Sent: 01 July 2020 13:04 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: Re: [DISCUSS] Management server default port conflict I think we can document in our CloudStack qig/release/install notes to say users must disable cockpit on CentOS8. Here are my 2paisas; * Most users using CentOS (7/8) won't use a single-host specific management tool/UI such as cockpit; they would probably use some fleet management software or automate using ansible/puppet/ceph etc. * Last time I checked the minimal CentOS-8 ISO does not install cockpit or that it is enabled by default (service does not run by default until you active the port 9090 target) * Some users may have monitoring scripts/tools or security rules that expect port 9090 to be used by CloudStack, so it's probably safer to ask users to change port for cockpit than CloudStack by default Regards. From: Abhishek Kumar Sent: Wednesday, July 1, 2020 11:14 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: [DISCUSS] Management server default port conflict Hi all, I would like to know everyone's opinion regarding an issue seen with CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). CentOS8 comes with cockpit (https://cockpit-project.org/) installed which uses port 9090, although it is not active by default. CloudStack management server also needs port 9090. And when CloudStack management server is started with systemd it triggers the start of cockpit first and management server fails to start, 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) (logid:) Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Failed to configure ClusterManagerImpl javax.naming.ConfigurationException: Detected that another management node with the same IP 10.10.2.167 is already running, please check your cluster configuration at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158) at org.springframework.context.support.DefaultLifecyc
[GitHub] [cloudstack-primate] utchoang opened a new pull request #481: Compare translation keys and doclinks usage and migration of translation from old UI
utchoang opened a new pull request #481: URL: https://github.com/apache/cloudstack-primate/pull/481 Open for https://github.com/apache/cloudstack-primate/issues/479 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 a change in pull request #481: Compare translation keys and doclinks usage and migration of translation from old UI
rhtyd commented on a change in pull request #481:
URL: https://github.com/apache/cloudstack-primate/pull/481#discussion_r448735817
##
File path: src/locales/en.json
##
@@ -1941,6 +1962,7 @@
"label.tuesday": "Tuesday",
"label.type": "Type",
"label.type.id": "Type ID",
+"label.tx.size": "TX {number}",
Review comment:
@utchoang don't use this synyax, it will be difficult for our
translators, please keep it simply text strings without code, instead you can
add variable to translations in components
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] davidjumani opened a new pull request #482: Adding contextual info for resource status
davidjumani opened a new pull request #482: URL: https://github.com/apache/cloudstack-primate/pull/482 Fixes #466  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] davidjumani commented on pull request #482: Adding contextual info for resource status
davidjumani commented on pull request #482: URL: https://github.com/apache/cloudstack-primate/pull/482#issuecomment-652796196 @blueorangutan package 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] blueorangutan commented on pull request #482: Adding contextual info for resource status
blueorangutan commented on pull request #482: URL: https://github.com/apache/cloudstack-primate/pull/482#issuecomment-652796579 @davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] davidjumani commented on pull request #482: Adding contextual info for resource status
davidjumani commented on pull request #482: URL: https://github.com/apache/cloudstack-primate/pull/482#issuecomment-652798315 @PaulAngus Looks good ? 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] blueorangutan commented on pull request #482: Adding contextual info for resource status
blueorangutan commented on pull request #482: URL: https://github.com/apache/cloudstack-primate/pull/482#issuecomment-652799221 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/482 (JID-2184) 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] davidjumani commented on pull request #478: Creating custom form to delete vm
davidjumani commented on pull request #478: URL: https://github.com/apache/cloudstack-primate/pull/478#issuecomment-652803495 @blueorangutan package 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] blueorangutan commented on pull request #478: Creating custom form to delete vm
blueorangutan commented on pull request #478: URL: https://github.com/apache/cloudstack-primate/pull/478#issuecomment-652803830 @davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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 #483: add form element info tooltips
shwstppr opened a new pull request #483: URL: https://github.com/apache/cloudstack-primate/pull/483 Added info tooltips fo custom forms 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] blueorangutan commented on pull request #478: Creating custom form to delete vm
blueorangutan commented on pull request #478: URL: https://github.com/apache/cloudstack-primate/pull/478#issuecomment-652806569 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/478 (JID-2185) 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] davidjumani commented on pull request #458: Adding quick-view options to list view
davidjumani commented on pull request #458: URL: https://github.com/apache/cloudstack-primate/pull/458#issuecomment-652809847 @blueorangutan package 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] blueorangutan commented on pull request #458: Adding quick-view options to list view
blueorangutan commented on pull request #458: URL: https://github.com/apache/cloudstack-primate/pull/458#issuecomment-652810157 @davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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 a change in pull request #481: Compare translation keys and doclinks usage and migration of translation from old UI
utchoang commented on a change in pull request #481:
URL: https://github.com/apache/cloudstack-primate/pull/481#discussion_r448778092
##
File path: src/locales/en.json
##
@@ -1941,6 +1962,7 @@
"label.tuesday": "Tuesday",
"label.type": "Type",
"label.type.id": "Type ID",
+"label.tx.size": "TX {number}",
Review comment:
@rhtyd Can I change it to an image? Or just allow string concatenation
in the 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
[GitHub] [cloudstack-primate] blueorangutan commented on pull request #458: Adding quick-view options to list view
blueorangutan commented on pull request #458: URL: https://github.com/apache/cloudstack-primate/pull/458#issuecomment-652813352 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/458 (JID-2186) 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 a change in pull request #481: Compare translation keys and doclinks usage and migration of translation from old UI
utchoang commented on a change in pull request #481:
URL: https://github.com/apache/cloudstack-primate/pull/481#discussion_r448778934
##
File path: src/locales/en.json
##
@@ -1941,6 +1962,7 @@
"label.tuesday": "Tuesday",
"label.type": "Type",
"label.type.id": "Type ID",
+"label.tx.size": "TX {number}",
Review comment:
Ah. Sorry, I was misunderstood. You mean don't use the syntax (Exp: TX,
SR,...)
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] blueorangutan commented on pull request #458: Adding quick-view options to list view
blueorangutan commented on pull request #458: URL: https://github.com/apache/cloudstack-primate/pull/458#issuecomment-652814497 @davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. 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] davidjumani commented on pull request #458: Adding quick-view options to list view
davidjumani commented on pull request #458: URL: https://github.com/apache/cloudstack-primate/pull/458#issuecomment-652814314 @blueorangutan package 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 a change in pull request #481: Compare translation keys and doclinks usage and migration of translation from old UI
utchoang commented on a change in pull request #481:
URL: https://github.com/apache/cloudstack-primate/pull/481#discussion_r448778934
##
File path: src/locales/en.json
##
@@ -1941,6 +1962,7 @@
"label.tuesday": "Tuesday",
"label.type": "Type",
"label.type.id": "Type ID",
+"label.tx.size": "TX {number}",
Review comment:
Ah. Sorry, I was misunderstood. You mean don't use the syntax (Exp: TX,
SR,...), right?
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] blueorangutan commented on pull request #458: Adding quick-view options to list view
blueorangutan commented on pull request #458: URL: https://github.com/apache/cloudstack-primate/pull/458#issuecomment-652817784 Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive. QA: http://primate-qa.cloudstack.cloud:8080/client/pr/458 (JID-2187) 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 a change in pull request #481: Compare translation keys and doclinks usage and migration of translation from old UI
utchoang commented on a change in pull request #481:
URL: https://github.com/apache/cloudstack-primate/pull/481#discussion_r448778934
##
File path: src/locales/en.json
##
@@ -1941,6 +1962,7 @@
"label.tuesday": "Tuesday",
"label.type": "Type",
"label.type.id": "Type ID",
+"label.tx.size": "TX {number}",
Review comment:
Ah. Sorry, I was misunderstood. You mean don't use the syntax (Exp: TX,
RX,...), right?
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: [DISCUSS] Management server default port conflict
Agree with Ron. Besides the change in cloudstack documents, it would be nice to check all cloudstack ports (8080, 8250, 9090, 8096/integration, 9595/prometheus) and display error messages before starting java thread when start service cloudstack-management. It helps users to find the root cause and stop services to free the ports. -Wei On Thu, 2 Jul 2020 at 04:42, Ron Wheeler wrote: > Is there any hope of getting projects to follow the rules? > > One would think that Cloudstack developers would be the most likely to > understand networking, the Internet and system administration. > > Ron > > On 2020-07-01 12:53 p.m., Andrija Panic wrote: > > (true that, Ron...) > > > > On Wed, 1 Jul 2020, 15:27 Ron Wheeler, > > wrote: > > > >> If the open source community just got their act together and registered > >> their ports and stopped using ports registered to other projects, this > >> would not happen. > >> > >> There is no shortage of available ports, there is just a complete lack > >> of professionalism in the community and it causes unnecessary headaches > >> for users. > >> > >> Stop using ports registered to other projects. > >> Register the ports for Cloudstack and encourage/insist that others do so > >> as well. > >> Publicly shame projects and products that use ports that they have not > >> registered. > >> To set a good example, in documentation and examples stop using ports in > >> the registered range for applications that should use ports in the > >> private/dynamic range. > >> > >> > >> Ron > >> > >> > >> On 2020-07-01 7:36 a.m., Abhishek Kumar wrote: > >>> +1 with adding documentation. > >>> > >>> And maybe we should also refactor the port check logic and error > >> message. Currently, code just tries to connect the socket for the port > and > >> if it fails that with the message, > >>> Detected that another management node with the same IP XX.XX.XX.XX is > >> already running, please check your cluster configuration > >>> Instead of the cockpit, it can be any other service/process. Should we > >> try to get details of that service in the logs, exception message so the > >> user can make changes? > >>> Regards, > >>> Abhishek > >>> > >>> From: Rohit Yadav > >>> Sent: 01 July 2020 13:04 > >>> To: dev@cloudstack.apache.org ; > >> us...@cloudstack.apache.org > >>> Subject: Re: [DISCUSS] Management server default port conflict > >>> > >>> I think we can document in our CloudStack qig/release/install notes to > >> say users must disable cockpit on CentOS8. Here are my 2paisas; > >>> * Most users using CentOS (7/8) won't use a single-host specific > >> management tool/UI such as cockpit; they would probably use some fleet > >> management software or automate using ansible/puppet/ceph etc. > >>> * Last time I checked the minimal CentOS-8 ISO does not install > >> cockpit or that it is enabled by default (service does not run by > default > >> until you active the port 9090 target) > >>> * Some users may have monitoring scripts/tools or security rules > >> that expect port 9090 to be used by CloudStack, so it's probably safer > to > >> ask users to change port for cockpit than CloudStack by default > >>> Regards. > >>> > >>> > >>> From: Abhishek Kumar > >>> Sent: Wednesday, July 1, 2020 11:14 > >>> To: dev@cloudstack.apache.org ; > >> us...@cloudstack.apache.org > >>> Subject: [DISCUSS] Management server default port conflict > >>> > >>> Hi all, > >>> > >>> I would like to know everyone's opinion regarding an issue seen with > >> CloudStack on CentOS8 (https://github.com/apache/cloudstack/pull/4068). > >> CentOS8 comes with cockpit (https://cockpit-project.org/) installed > which > >> uses port 9090, although it is not active by default. CloudStack > management > >> server also needs port 9090. And when CloudStack management server is > >> started with systemd it triggers the start of cockpit first and > management > >> server fails to start, > >>> > >>> 2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) > >> (logid:) Detected that another management node with the same IP > 10.10.2.167 > >> is already running, please check your cluster configuration > >>> 2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] > >> (main:null) (logid:) Failed to configure ClusterManagerImpl > >>> javax.naming.ConfigurationException: Detected that another management > >> node with the same IP 10.10.2.167 is already running, please check your > >> cluster configuration > >>> at > >> > com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192) > >>> at > >> > com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065) > >>> at > >> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) > >>> at > >> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.w
