Removing a zone

2023-02-12 Thread Granwille Strauss 

Hi Guys

I am busy cleaning up zones, and managed to delete all pods and cluster 
and so tied to the zone and all that but when deleting the zone itself 
it shows there is storage devices tied to zone. I have checked it all 
and there's none. However, I believe its because image ISO that were 
initially installed, see attached screenshot, which is why the zone 
can't be deleted. I tried adding the secondary storage again, where it 
was stored, but no luck. Any ideas how I can go about cleaning out these 
old ISOs to delete my old zone?


--
Regards / Groete

 Granwille Strauss  // Senior Systems Admin

*e:* granwi...@namhost.com
*m:* +264 81 323 1260 
*w:* www.namhost.com 





Namhost Internet Services (Pty) Ltd,

24 Black Eagle Rd, Hermanus, 7210, RSA



The content of this message is confidential. If you have received it by 
mistake, please inform us by email reply and then delete the message. It 
is forbidden to copy, forward, or in any way reveal the contents of this 
message to anyone without our explicit consent. The integrity and 
security of this email cannot be guaranteed over the Internet. 
Therefore, the sender will not be held liable for any damage caused by 
the message. For our full privacy policy and disclaimers, please go to 
https://www.namhost.com/privacy-policy


Powered by AdSigner 


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Issue adding host in cluster.

2023-02-12 Thread Nicolas Vazquez 
Hi Sanjay,

Which hypervisor is the host you are trying to add?

Regards,
Nicolas Vazquez


From: Sanjay Kumar 
Date: Sunday, 12 February 2023 at 20:47
To: users@cloudstack.apache.org , 
dev-subscr...@cloudstack.apache.org 
Subject: Issue adding host in cluster.
Hi All,

We are facing issue while adding the host in cluster. Please help me out to
solve the problem.

ACS_Version: 4.17.2

2023-02-13 05:04:35,759 ERROR [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-4:null) (logid:) SSL error caught during
wrap data: Empty server certificate chain, for local address=/
10.10.11.52:8250, remote address=/10.10.11.21:45646.
2023-02-13 05:04:35,760 INFO  [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) (logid:) Connection from /10.10.11.21 closed
but no cleanup was done.
2023-02-13 05:04:35,920 DEBUG [c.c.a.ApiServlet]
(qtp1443435931-4966:ctx-bd1977c3) (logid:5b548f75) ===START===  10.10.11.15
-- POST  command=addHost=json
2023-02-13 05:04:35,929 DEBUG [c.c.a.ApiServer]
(qtp1443435931-4966:ctx-bd1977c3 ctx-b719489c) (logid:5b548f75) CIDRs from
which account 'Acct[a208e338-a909-11ed-8eef-9618ac1031f9-admin] -- Account
{"id": 2, "name": "admin", "uuid": "a208e338-a909-11ed-8eef-9618ac1031f9"}'
is allowed to perform API calls: 0.0.0.0/0,::/0
2023-02-13 05:04:35,936 WARN  [c.c.a.d.ParamGenericValidationWorker]
(qtp1443435931-4966:ctx-bd1977c3 ctx-b719489c) (logid:5b548f75) Received
unknown parameters for command addHost. Unknown parameters : clustertype
2023-02-13 05:04:35,938 ERROR [c.c.a.ApiServer]
(qtp1443435931-4966:ctx-bd1977c3 ctx-b719489c) (logid:5b548f75) unhandled
exception executing api command: [Ljava.lang.String;@15ab4c10
com.cloud.utils.exception.CloudRuntimeException: Guid is not updated for
cluster with specified cluster id; need to wait for hosts in this cluster
to come up



Regards,
Sanjay Kumar

Issue adding host in cluster.

2023-02-12 Thread Sanjay Kumar 
Hi All,

We are facing issue while adding the host in cluster. Please help me out to
solve the problem.

ACS_Version: 4.17.2

2023-02-13 05:04:35,759 ERROR [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-4:null) (logid:) SSL error caught during
wrap data: Empty server certificate chain, for local address=/
10.10.11.52:8250, remote address=/10.10.11.21:45646.
2023-02-13 05:04:35,760 INFO  [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) (logid:) Connection from /10.10.11.21 closed
but no cleanup was done.
2023-02-13 05:04:35,920 DEBUG [c.c.a.ApiServlet]
(qtp1443435931-4966:ctx-bd1977c3) (logid:5b548f75) ===START===  10.10.11.15
-- POST  command=addHost=json
2023-02-13 05:04:35,929 DEBUG [c.c.a.ApiServer]
(qtp1443435931-4966:ctx-bd1977c3 ctx-b719489c) (logid:5b548f75) CIDRs from
which account 'Acct[a208e338-a909-11ed-8eef-9618ac1031f9-admin] -- Account
{"id": 2, "name": "admin", "uuid": "a208e338-a909-11ed-8eef-9618ac1031f9"}'
is allowed to perform API calls: 0.0.0.0/0,::/0
2023-02-13 05:04:35,936 WARN  [c.c.a.d.ParamGenericValidationWorker]
(qtp1443435931-4966:ctx-bd1977c3 ctx-b719489c) (logid:5b548f75) Received
unknown parameters for command addHost. Unknown parameters : clustertype
2023-02-13 05:04:35,938 ERROR [c.c.a.ApiServer]
(qtp1443435931-4966:ctx-bd1977c3 ctx-b719489c) (logid:5b548f75) unhandled
exception executing api command: [Ljava.lang.String;@15ab4c10
com.cloud.utils.exception.CloudRuntimeException: Guid is not updated for
cluster with specified cluster id; need to wait for hosts in this cluster
to come up



Regards,
Sanjay Kumar

Re: PCI-E Passthrough

2023-02-12 Thread JeanPaul van der Mijle 
Hi Wei,

Thanks, going to take a deeper look into this.

I assume I will have to add the list as following, to allow the XML below to be 
accepted by the API when I submit this encoded?

I set this to be allowed for KVM: 
domain,devices,hostdev,source,address,memballoon,rng,backend

It should reflect this XML part:


  

  

  
  


  

  
  


  

  
  


  

  
  


  


  /dev/urandom
  

  


I only need to figure out if domain and device are required or not but I will 
see when I test it out.

Thanks so far!

JeanPaul

From: Wei ZHOU 
Sent: Sunday, February 12, 2023 5:23 PM
To: users@cloudstack.apache.org 
Subject: Re: PCI-E Passthrough

I think you need to add additional configuration to vm.
Refer to
https://www.shapeblue.com/cloudstack-feature-first-look-enable-sending-of-arbitrary-configuration-data-to-vms/

-Wei



On Sunday, 12 February 2023, JeanPaul van der Mijle <
jp.vandermi...@hyperai.ai> wrote:

> Hi all,
>
> Does anyone have a good guide on adding a PCI-E card (A Mellanox Connect-X
> 5 VF interface) to cloudstack?
> I had this all running before in stock Qemu, and all settings are still
> present for the card and VF's, I just need to know how the management sees
> that I have additional cards that I have available to assign to VMs.
>
> I tried adding:
> pci.devices=100GE,81:00.2|100GE,81:00.3|100GE,81:00.4|
> 100GE,81:00.5|100GE,81:00.6|100GE,81:00.7|100GE,81:01.0|
> 100GE,81:01.1|100GE,c1:00.2|100GE,c1:00.3|100GE,c1:00.4|
> 100GE,c1:00.5|100GE,c1:00.6|100GE,c1:00.7|100GE,c1:01.0|100GE,c1:01.1
>
> However, after restarting the agent, I noticed that it added escape
> characters:
> pci.devices=100GE,81\:00.2|100GE,81\:00.3|100GE,81\:00.4|
> 100GE,81\:00.5|100GE,81\:00.6|100GE,81\:00.7|100GE,81\:01.0|
> 100GE,81\:01.1|100GE,c1\:00.2|100GE,c1\:00.3|100GE,c1\:00.4|
> 100GE,c1\:00.5|100GE,c1\:00.6|100GE,c1\:00.7|100GE,c1\:01.0|100GE,c1\:01.1
>
> Not sure if this is fine, but so far it was the only thing I could find
> back on google, but this is 10 years ago. I suspect this is no longer
> sufficient.
> After restarting the agent, I do not see any changes unfortunately.
>
> Thanks!
>
> JeanPaul
>
>

Re: PCI-E Passthrough

2023-02-12 Thread Wei ZHOU 
I think you need to add additional configuration to vm.
Refer to
https://www.shapeblue.com/cloudstack-feature-first-look-enable-sending-of-arbitrary-configuration-data-to-vms/

-Wei



On Sunday, 12 February 2023, JeanPaul van der Mijle <
jp.vandermi...@hyperai.ai> wrote:

> Hi all,
>
> Does anyone have a good guide on adding a PCI-E card (A Mellanox Connect-X
> 5 VF interface) to cloudstack?
> I had this all running before in stock Qemu, and all settings are still
> present for the card and VF's, I just need to know how the management sees
> that I have additional cards that I have available to assign to VMs.
>
> I tried adding:
> pci.devices=100GE,81:00.2|100GE,81:00.3|100GE,81:00.4|
> 100GE,81:00.5|100GE,81:00.6|100GE,81:00.7|100GE,81:01.0|
> 100GE,81:01.1|100GE,c1:00.2|100GE,c1:00.3|100GE,c1:00.4|
> 100GE,c1:00.5|100GE,c1:00.6|100GE,c1:00.7|100GE,c1:01.0|100GE,c1:01.1
>
> However, after restarting the agent, I noticed that it added escape
> characters:
> pci.devices=100GE,81\:00.2|100GE,81\:00.3|100GE,81\:00.4|
> 100GE,81\:00.5|100GE,81\:00.6|100GE,81\:00.7|100GE,81\:01.0|
> 100GE,81\:01.1|100GE,c1\:00.2|100GE,c1\:00.3|100GE,c1\:00.4|
> 100GE,c1\:00.5|100GE,c1\:00.6|100GE,c1\:00.7|100GE,c1\:01.0|100GE,c1\:01.1
>
> Not sure if this is fine, but so far it was the only thing I could find
> back on google, but this is 10 years ago. I suspect this is no longer
> sufficient.
> After restarting the agent, I do not see any changes unfortunately.
>
> Thanks!
>
> JeanPaul
>
>

PCI-E Passthrough

2023-02-12 Thread JeanPaul van der Mijle 
Hi all,

Does anyone have a good guide on adding a PCI-E card (A Mellanox Connect-X 5 VF 
interface) to cloudstack?
I had this all running before in stock Qemu, and all settings are still present 
for the card and VF's, I just need to know how the management sees that I have 
additional cards that I have available to assign to VMs.

I tried adding:
pci.devices=100GE,81:00.2|100GE,81:00.3|100GE,81:00.4|100GE,81:00.5|100GE,81:00.6|100GE,81:00.7|100GE,81:01.0|100GE,81:01.1|100GE,c1:00.2|100GE,c1:00.3|100GE,c1:00.4|100GE,c1:00.5|100GE,c1:00.6|100GE,c1:00.7|100GE,c1:01.0|100GE,c1:01.1

However, after restarting the agent, I noticed that it added escape characters:
pci.devices=100GE,81\:00.2|100GE,81\:00.3|100GE,81\:00.4|100GE,81\:00.5|100GE,81\:00.6|100GE,81\:00.7|100GE,81\:01.0|100GE,81\:01.1|100GE,c1\:00.2|100GE,c1\:00.3|100GE,c1\:00.4|100GE,c1\:00.5|100GE,c1\:00.6|100GE,c1\:00.7|100GE,c1\:01.0|100GE,c1\:01.1

Not sure if this is fine, but so far it was the only thing I could find back on 
google, but this is 10 years ago. I suspect this is no longer sufficient.
After restarting the agent, I do not see any changes unfortunately.

Thanks!

JeanPaul