Re: [VOTE] Adopt Github Discusssions as Users Forum
-0: Agree with Nux (see his concern in another e-mail) Op 04/12/2023 om 22:56 schreef Nux: -0 - I have voiced my concerns already. On 2023-12-04 08:01, Rohit Yadav wrote: All, Following the discussion thread on adopting Github Discussions as users forum [1], I put the following proposal for a vote: 1. Adopt and use Github Discussions as user forums. 2. The Github Discussions feature is tied with the users@cloudstack.apache.org mailing list (PR: https://github.com/apache/cloudstack/pull/8274). 3. Any project governance and decision-making thread such as voting, releases etc. should continue to use the project mailing lists. Vote will be open for 120 hours (by Friday, 8th Dec). For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8 Regards.
Re: Host tags
Hi Marty, Just to confirm, you are asking about the cloudstack host tag or the xe host-param ‘tag’? -Jithin From: Nux Date: Tuesday, 5 December 2023 at 2:38 AM To: users@cloudstack.apache.org Cc: Marty Godsey Subject: Re: Host tags Sounds good, thanks for clarifying. On 2023-12-04 20:40, Marty Godsey wrote: > Nux, > > They do. I have no other issues and the tags “magically appeared” so, > idk.. But it didn’t seem to have any issues. Since there were no issues > observed, I am not worried about troubleshooting. > > Marty > > From: Nux > Date: Friday, December 1, 2023 at 1:56 PM > To: users@cloudstack.apache.org > Subject: Re: Host tags > Hi, > > That could be XO's doing. I was hoping XO and cloudstack can co-exist > peacefully, but this doesn't fill me with confidence. > > > > On 1 December 2023 08:42:35 GMT, Boris Stoyanov > wrote: >> Marty, >> We haven’t really observed a situation of tags being missing all of >> the sudden, I don’t recall such issue. Feel free to add them once more >> at the host. >> >> Bobby. >> >> From: Marty Godsey >> Date: Wednesday, 29 November 2023 at 22:26 >> To: users@cloudstack.apache.org >> Subject: Host tags >> Hello guys, >> >> I am using XCP-NG for my hosts and use XOA to “manage” them. When I >> say manage, I mean just use it for visibility into the cluster. >> Cloudstack does all the work. >> >> I noticed today that my tags on the hosts are missing. It’s on one of >> the hosts but not the other two. Is this a concern? How would I get >> them back if needed? >> >> Marty >> >> >>
Re: different os in cluster
Yes there is a limitation. All hosts within a cluster must be on the same OS. On Mon, Dec 4, 2023 at 8:51 AM Piotr Pisz wrote: > Hi, > > Is there a limitation within the cluster that does not allow adding hosts > with different OS? > We are in the process of replacing Redhat systems with Ubuntu and I have > the following message: > > Can't add host: x.x.x.x with hostOS, "Ubuntu"into a cluster, in which > there are "CentOS Linux" hosts added. > > Regards, > Piotr > > -- Steve Fuller steveful...@gmail.com
Re: [VOTE] Adopt Github Discusssions as Users Forum
-0 - I have voiced my concerns already. On 2023-12-04 08:01, Rohit Yadav wrote: All, Following the discussion thread on adopting Github Discussions as users forum [1], I put the following proposal for a vote: 1. Adopt and use Github Discussions as user forums. 2. The Github Discussions feature is tied with the users@cloudstack.apache.org mailing list (PR: https://github.com/apache/cloudstack/pull/8274). 3. Any project governance and decision-making thread such as voting, releases etc. should continue to use the project mailing lists. Vote will be open for 120 hours (by Friday, 8th Dec). For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8 Regards.
Re: Host tags
Sounds good, thanks for clarifying. On 2023-12-04 20:40, Marty Godsey wrote: Nux, They do. I have no other issues and the tags “magically appeared” so, idk.. But it didn’t seem to have any issues. Since there were no issues observed, I am not worried about troubleshooting. Marty From: Nux Date: Friday, December 1, 2023 at 1:56 PM To: users@cloudstack.apache.org Subject: Re: Host tags Hi, That could be XO's doing. I was hoping XO and cloudstack can co-exist peacefully, but this doesn't fill me with confidence. On 1 December 2023 08:42:35 GMT, Boris Stoyanov wrote: Marty, We haven’t really observed a situation of tags being missing all of the sudden, I don’t recall such issue. Feel free to add them once more at the host. Bobby. From: Marty Godsey Date: Wednesday, 29 November 2023 at 22:26 To: users@cloudstack.apache.org Subject: Host tags Hello guys, I am using XCP-NG for my hosts and use XOA to “manage” them. When I say manage, I mean just use it for visibility into the cluster. Cloudstack does all the work. I noticed today that my tags on the hosts are missing. It’s on one of the hosts but not the other two. Is this a concern? How would I get them back if needed? Marty
Re: Host tags
Nux, They do. I have no other issues and the tags “magically appeared” so, idk.. But it didn’t seem to have any issues. Since there were no issues observed, I am not worried about troubleshooting. Marty From: Nux Date: Friday, December 1, 2023 at 1:56 PM To: users@cloudstack.apache.org Subject: Re: Host tags Hi, That could be XO's doing. I was hoping XO and cloudstack can co-exist peacefully, but this doesn't fill me with confidence. On 1 December 2023 08:42:35 GMT, Boris Stoyanov wrote: >Marty, >We haven’t really observed a situation of tags being missing all of the >sudden, I don’t recall such issue. Feel free to add them once more at the host. > >Bobby. > >From: Marty Godsey >Date: Wednesday, 29 November 2023 at 22:26 >To: users@cloudstack.apache.org >Subject: Host tags >Hello guys, > >I am using XCP-NG for my hosts and use XOA to “manage” them. When I say >manage, I mean just use it for visibility into the cluster. Cloudstack does >all the work. > >I noticed today that my tags on the hosts are missing. It’s on one of the >hosts but not the other two. Is this a concern? How would I get them back if >needed? > >Marty > > >
Re: different os in cluster
Hi Piotr, Hosts within a cluster are expected to be homogenous: https://docs.cloudstack.apache.org/en/latest/conceptsandterminology/concepts.html?highlight=homogenous#cloud-infrastructure-overview You could probably create another Cluster to add the ubuntu based hosts. Regards, Pearl From: Vishesh Jindal Sent: December 4, 2023 10:57 AM To: users@cloudstack.apache.org Subject: Re: different os in cluster Hi Piotr, I am not sure about the reason but CloudStack doesn't allow adding host with a different OS in a cluster. Regards, Vishesh From: Piotr Pisz Sent: Monday, December 4, 2023 8:20 PM To: users@cloudstack.apache.org Subject: different os in cluster Hi, Is there a limitation within the cluster that does not allow adding hosts with different OS? We are in the process of replacing Redhat systems with Ubuntu and I have the following message: Can't add host: x.x.x.x with hostOS, "Ubuntu"into a cluster, in which there are "CentOS Linux" hosts added. Regards, Piotr
Re: different os in cluster
Hi Piotr, I am not sure about the reason but CloudStack doesn't allow adding host with a different OS in a cluster. Regards, Vishesh From: Piotr Pisz Sent: Monday, December 4, 2023 8:20 PM To: users@cloudstack.apache.org Subject: different os in cluster Hi, Is there a limitation within the cluster that does not allow adding hosts with different OS? We are in the process of replacing Redhat systems with Ubuntu and I have the following message: Can't add host: x.x.x.x with hostOS, "Ubuntu"into a cluster, in which there are "CentOS Linux" hosts added. Regards, Piotr
different os in cluster
Hi, Is there a limitation within the cluster that does not allow adding hosts with different OS? We are in the process of replacing Redhat systems with Ubuntu and I have the following message: Can't add host: x.x.x.x with hostOS, "Ubuntu"into a cluster, in which there are "CentOS Linux" hosts added. Regards, Piotr
RE: Load balancer configurations - maxcon
I see, thank you. For now I will adjust in the haproxy.cnf. Regards, Cristian From: Sina Kashipazha Sent: Monday, December 4, 2023 3:16 PM To: users Subject: Re: Load balancer configurations - maxcon I think it is related to the following open PR: https://github.com/apache/cloudstack/pull/7484 Regards, Sina On Mon, Dec 4, 2023 at 14:11, mailto:On%20Mon,%20Dec%204,%202023%20at%2014:11,%20%20%3c%3ca%20href=> > wrote: Hello, Is there a way to adjust the maxcon for a LB? isolated network I have found this https://cwiki.apache.org/confluence/display/CLOUDSTACK/VR+haproxy+customizat ion+in+CloudStack but there is no such option in the UI. 4.18.1 Regards, Cristian
Re: Load balancer configurations - maxcon
<<< text/html; charset=utf-8: Unrecognized >>> signature.asc Description: OpenPGP digital signature
Load balancer configurations - maxcon
Hello, Is there a way to adjust the maxcon for a LB? isolated network I have found this https://cwiki.apache.org/confluence/display/CLOUDSTACK/VR+haproxy+customizat ion+in+CloudStack but there is no such option in the UI. 4.18.1 Regards, Cristian
Re: VR webserver.service apache2
Hi, Have you updated the global configuration "router.template.*" ? -Wei On Mon, 4 Dec 2023 at 10:18, Frederic Larcher wrote: > Hi, > > I have made the requested changes from the Github pull 7982 on a SystemVM > template (that should fix our issue with the web service failing) on ACS > 4.15.2, added it to our Secondary storage server, and created a new > SystemVM from it. However, this new VM doesn’t have the changes. > > This is what I have on the SystemVM template: > [image: A computer screen with white text Description automatically > generated] > > > > It is identical as the Git pull: > > [image: image] > > Problem is that on a new SystemVM I have just recreated, it is still > using the old config: > > [image: image] > > > > I’m a bit lost. I have used the right command to upload this SystemVM, so > I don’t understand why the config files are different between the VM and > the template. Guess I am missing something? > > Any help would be appreciated, thanks. > > > Frederic Larcher > Technical Consultant > 0161 537 4980 <0161%20537%204980> > frederic.larc...@quadris.com > www.quadris.com > Innovation House, 12‑13 Bredbury Business Park > Bredbury Park Way, Bredbury, Stockport, SK6 2SN >
VR webserver.service apache2
Hi, I have made the requested changes from the Github pull 7982 on a SystemVM template (that should fix our issue with the web service failing) on ACS 4.15.2, added it to our Secondary storage server, and created a new SystemVM from it. However, this new VM doesn't have the changes. This is what I have on the SystemVM template: [A computer screen with white text Description automatically generated] It is identical as the Git pull: [image] Problem is that on a new SystemVM I have just recreated, it is still using the old config: [image] I'm a bit lost. I have used the right command to upload this SystemVM, so I don't understand why the config files are different between the VM and the template. Guess I am missing something? Any help would be appreciated, thanks. Frederic Larcher Technical Consultant 0161 537 4980 frederic.larc...@quadris.com www.quadris.com Innovation House, 12-13 Bredbury Business Park Bredbury Park Way, Bredbury, Stockport, SK6 2SN
Re: Error when Staring Existing Instances
Hi,
You need to increase the resource limitation primary_storage of project
CGS. It looks like you have reached the 4TB limit.
-Wei
On Mon, 4 Dec 2023 at 09:39, Palash Biswas wrote:
> Greetings Community users,
>
> We are currently in the process of integrating our Linstor nodes with the
> Cloudstack setup. Following a maintenance shutdown and subsequent restart
> of all servers, we are encountering difficulties in starting existing
> instances. It's worth noting that creating new instances is not
> encountering any issues.
>
> We are encountering two distinct errors during the instance start-up
> process:
>
> *Error 1 (Instance ID: i-2-286)*
>
> Start instance
>
> (OMS1) Unable to orchestrate start VM instance
> {"id":286,"instanceName":"i-2-286-VM","type":"User","uuid":"6987bdf1-7b37-41e1-bdbd-1071a9b0fa18"}
> due to [Unable to get answer that is of class
> com.cloud.agent.api.StartAnswer].
>
>
>
> *Error 2 (Instance ID: i-2-281)*
>
> Start instance
>
> (MM37) Unable to start a VM [622fb948-6194-4969-a4a4-b652c22c0ec6] due to
> [Unable to create a deployment for VM instance
> {"id":281,"instanceName":"i-2-281-VM","type":"User","uuid":"622fb948-6194-4969-a4a4-b652c22c0ec6"}].
>
> We have also captured additional logs during the attempts to start the
> instances. Your prompt attention and assistance in resolving these issues
> would be highly appreciated.
>
> Regards,
> Palash Biswas
>
Error when Staring Existing Instances
Greetings Community users,
We are currently in the process of integrating our Linstor nodes with the
Cloudstack setup. Following a maintenance shutdown and subsequent restart
of all servers, we are encountering difficulties in starting existing
instances. It's worth noting that creating new instances is not
encountering any issues.
We are encountering two distinct errors during the instance start-up
process:
*Error 1 (Instance ID: i-2-286)*
Start instance
(OMS1) Unable to orchestrate start VM instance
{"id":286,"instanceName":"i-2-286-VM","type":"User","uuid":"6987bdf1-7b37-41e1-bdbd-1071a9b0fa18"}
due to [Unable to get answer that is of class
com.cloud.agent.api.StartAnswer].
*Error 2 (Instance ID: i-2-281)*
Start instance
(MM37) Unable to start a VM [622fb948-6194-4969-a4a4-b652c22c0ec6] due to
[Unable to create a deployment for VM instance
{"id":281,"instanceName":"i-2-281-VM","type":"User","uuid":"622fb948-6194-4969-a4a4-b652c22c0ec6"}].
We have also captured additional logs during the attempts to start the
instances. Your prompt attention and assistance in resolving these issues
would be highly appreciated.
Regards,
Palash Biswas
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
Dec 01 08:43:18 n2ncs-mcs01 java[11044]: at
java.base/java.lang.Thread.run(Thread.java:829)
Dec 01 08:43:32 n2ncs-mcs01 java[11044]: INFO
[o.a.c.a.DynamicRoleBasedAPIAccessChecker] (qtp1278852808-11005:ctx-7bac6178
ctx-3cdf0c62) (logid:701251b3) Account [Account
[{"accountName":"admin","id":2,"uuid":"0e02266c-6350-11ee-a6a8-5254001f02f7"}]]
is Root Admin or Domain Admin, all APIs are allowed.
Dec 01 08:43:32 n2ncs-mcs01 java[11044]: WARN
[o.a.c.a.ProjectRoleBasedApiAccessChecker] (qtp1278852808-11005:ctx-7bac6178
ctx-3cdf0c62) (logid:701251b3) Project is null,
ProjectRoleBasedApiAccessChecker only applies to projects, returning API
[startVirtualMachine] for user [User
{"username":"admin","uuid":"0e02fe3b-6350-11ee-a6a8-5254001f02f7"}.] as allowed.
Dec 01 08:43:32 n2ncs-mcs01 java[11044]: INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-58:ctx-493a5aef job-9239) (logid:27e59549) Add job-9239 into
job monitoring
Dec 01 08:43:32 n2ncs-mcs01 java[11044]: INFO
[o.a.c.a.DynamicRoleBasedAPIAccessChecker] (qtp1278852808-11127:ctx-b85372db
ctx-54efe125) (logid:d9b916c0) Account [Account
[{"accountName":"admin","id":2,"uuid":"0e02266c-6350-11ee-a6a8-5254001f02f7"}]]
is Root Admin or Domain Admin, all APIs are allowed.
Dec 01 08:43:32 n2ncs-mcs01 java[11044]: WARN
[o.a.c.a.ProjectRoleBasedApiAccessChecker] (qtp1278852808-11127:ctx-b85372db
ctx-54efe125) (logid:d9b916c0) Project is null,
ProjectRoleBasedApiAccessChecker only applies to projects, returning API
[queryAsyncJobResult] for user [User
{"username":"admin","uuid":"0e02fe3b-6350-11ee-a6a8-5254001f02f7"}.] as allowed.
Dec 01 08:43:32 n2ncs-mcs01 java[11044]: INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Work-Job-Executor-107:ctx-9c7fb656 job-9239/job-9241) (logid:4ecad230) Add
job-9241 into job monitoring
Dec 01 08:43:33 n2ncs-mcs01 java[11044]: INFO
[c.c.n.e.VpcVirtualRouterElement] (Work-Job-Executor-107:ctx-9c7fb656
job-9239/job-9241 ctx-cd2e5e01) (logid:7afe088a) Adding VPC routers to Guest
Network: 1 to be added!
Dec 01 08:43:35 n2ncs-mcs01 java[11044]: INFO
[o.a.c.a.DynamicRoleBasedAPIAccessChecker] (qtp1278852808-11005:ctx-52d07839
ctx-aed1ecd0) (logid:64e14161) Account [Account
[{"accountName":"admin","id":2,"uuid":"0e02266c-6350-11ee-a6a8-5254001f02f7"}]]
is Root Admin or Domain Admin, all APIs are allowed.
Dec 01 08:43:35 n2ncs-mcs01 java[11044]: WARN
[o.a.c.a.ProjectRoleBasedApiAccessChecker] (qtp1278852808-11005:ctx-52d07839
[VOTE] Adopt Github Discusssions as Users Forum
All, Following the discussion thread on adopting Github Discussions as users forum [1], I put the following proposal for a vote: 1. Adopt and use Github Discussions as user forums. 2. The Github Discussions feature is tied with the users@cloudstack.apache.org mailing list (PR: https://github.com/apache/cloudstack/pull/8274). 3. Any project governance and decision-making thread such as voting, releases etc. should continue to use the project mailing lists. Vote will be open for 120 hours (by Friday, 8th Dec). For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8 Regards.
