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
blue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Wei ZHOU
> Sent: 02 July 2020 07:44
> To: dev@cloudstack.apache.org
> Subje
uilding, London SE1 9SGUK
@shapeblue
-Original Message-
From: Wei ZHOU
Sent: 02 July 2020 07:44
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Management server default port conflict
Agree with Ron.
Besides the change in cloudstack documents, it would be nice to check
paul.an...@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-Original Message-
From: Wei ZHOU
Sent: 02 July 2020 07:44
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Management server default port conflict
Agre
gt;> 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
> >> t
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
>
> > 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 def
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
: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
+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 coc
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 disab
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 soone
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
13 matches
Mail list logo
