date:20240222

Re: CKS Storage Provisioner Info

2024-02-22 Thread Vivek Kumar

Hello Bharat,

Can you try to install plugin manually and see if that works or not. 


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi Wei/Vivek/Kiran,
>  
> Kindly lookout in this.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Bharat Bhushan Saini  >
> Date: Friday, 23 February 2024 at 12:56 AM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>  
> Hi Vivek, 
>  
> I deployed cloudstack with version 4.18.1.
> I think it should be present in this version.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Vivek Kumar  >
> Date: Friday, 23 February 2024 at 12:48 AM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> Hello Bharat,
> 
> Then you will have to deploy the cloudstack-kubernetes-provider, however 
> after 4.16, it’s automatically deployed, Follow the instruction in the link 
> -https://github.com/apache/cloudstack-kubernetes-provider
> 
> 
> 1- Create a file called - cloud-config and put the below information - ( you 
> can create an user under your account and provide it’s apikey and secret key )
> 
> 
> [Global]
> api-url = 
> api-key = 
> secret-key = 
> 
> 
> 2- kubectl -n kube-system create secret generic cloudstack-secret 
> --from-file=cloud-config
> 3- then deploy the controller -
> 
> You can then use the provided example deployment.yaml 
> 
>  to deploy the controller:
> 
> kubectl apply -f deployment.yaml
> 
> 
> 
> 
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
> 
> vivek.ku...@indiqus.com  
> 
> www.indiqus.com  
> 
> 
> 
> 
> > On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
> >  > > wrote:
> >
> > Hi Vivek,
> >
> > I am glad and thankful to you for sharing the information, for the 
> > configuration of CSI driver.
> >
> > But I didn’t have cloudstack-secret in my cluster, sharing the details below
> >
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> > -n kube-system
> > Error from server (NotFound): secrets "cloudstack-secret" not found
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> > NAMESPACE  NAME  TYPE   
> >DATA   AGE
> > kloudspot  dockerregistrykey 
> > kubernetes.io/dockerconfigjson 
> > 
> > 1  8h
> > kube-systembootstrap-token-cb0b7f
> > bootstrap.kubernetes.io/token 
> > 
> >  6  8h
> > kubernetes-dashboard   kubernetes-dashboard-certsOpaque 
> >0  8h
> > kubernetes-dashboard   kubernetes-dashboard-csrf Opaque 
> >1  8h
> > kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque 
> >2  8h
> > kubernetes-dashboard   kubernetes-dashboard-token
> > kubernetes.io/service-account-token 
> >  
> >   3  8h
> > cloud@Kspot-App-control-18dd041902a:~$
> >
> > I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> > network is in shared mode and using 1 node cluster without HA.
> >
> > Thanks and Regards,
> > Bharat Saini
> >
> >
> >
> > From: Vivek Kumar  > >
> > Date: Thursday, 22 February 2024 at 11:39 PM
> > To: users@cloudstack.apache.org  
> >   >  >
> > Subject: Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any 
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > Hello

Re: CKS Storage Provisioner Info

2024-02-22 Thread Bharat Bhushan Saini

Hi Wei/Vivek/Kiran,

Kindly lookout in this.

Thanks and Regards,
Bharat Saini

[signature_550033876]

From: Bharat Bhushan Saini 
Date: Friday, 23 February 2024 at 12:56 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.

Hi Vivek,

I deployed cloudstack with version 4.18.1.
I think it should be present in this version.

Thanks and Regards,
Bharat Saini

[signature_3238255740]

From: Vivek Kumar 
Date: Friday, 23 February 2024 at 12:48 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Then you will have to deploy the cloudstack-kubernetes-provider, however after 
4.16, it’s automatically deployed, Follow the instruction in the link - 
https://github.com/apache/cloudstack-kubernetes-provider


1- Create a file called - cloud-config and put the below information - ( you 
can create an user under your account and provide it’s apikey and secret key )


[Global]
api-url = 
api-key = 
secret-key = 


2- kubectl -n kube-system create secret generic cloudstack-secret 
--from-file=cloud-config
3- then deploy the controller -

You can then use the provided example deployment.yaml 

 to deploy the controller:

kubectl apply -f deployment.yaml




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Vivek,
>
> I am glad and thankful to you for sharing the information, for the 
> configuration of CSI driver.
>
> But I didn’t have cloudstack-secret in my cluster, sharing the details below
>
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> -n kube-system
> Error from server (NotFound): secrets "cloudstack-secret" not found
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> NAMESPACE  NAME  TYPE 
>  DATA   AGE
> kloudspot  dockerregistrykey 
> kubernetes.io/dockerconfigjson 
> 1  8h
> kube-systembootstrap-token-cb0b7f
> bootstrap.kubernetes.io/token  
> 6  8h
> kubernetes-dashboard   kubernetes-dashboard-certsOpaque   
>  0  8h
> kubernetes-dashboard   kubernetes-dashboard-csrf Opaque   
>  1  8h
> kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque   
>  2  8h
> kubernetes-dashboard   kubernetes-dashboard-token
> kubernetes.io/service-account-token 
>   3  8h
> cloud@Kspot-App-control-18dd041902a:~$
>
> I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> network is in shared mode and using 1 node cluster without HA.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  >
> Date: Thursday, 22 February 2024 at 11:39 PM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> 1- When you deploy a cluster, an additional user is created under your 
> cloudstack account - i.e -kubeadmin,  and apikey and secret key 
> of this kubeadmin user is pushed to the cluster.
>
> This you can find -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
> NAMETYPE DATA   AGE
> cloudstack-secret   Opaque   1  3d5h
>
> To check the more details for this secret -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
> jsonpath='{.data.*}' | base64 -d
> [Global]
> api-url = http://172.27.2.53:8080/client/api
> api-key = 
> ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
> secret-key = 
> IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA
>
>
> Now, you can see the API URL, so this URL endpoint must be reachable from 
> your cluster in order to provision PVC. This URL you can put in the global 
> setting - (endpoint.url)
>
> So I am assuming this endpoint URL is reachable from your cluster -  you 
> don’t need to define anything in the cloud-config and secret -

Re: [D] EVPN-VXLAN - IPv6 via SLAAC [cloudstack]

2024-02-22 Thread via GitHub



GitHub user wido added a comment to the discussion: EVPN-VXLAN - IPv6 via SLAAC

Can both routers ping eachother via iPv6?

And have you also looked at this blog: 
https://danhearty.wordpress.com/2019/10/12/evpn-vxlan-layer-3-gateway-irb-junos/

A few things:

- I think I have seen this before... Can't remember what it was anymore
- This is not a CloudStack issue btw
- Is there no ipv6 firewall on the host dropping the packets on forward?
- Do you see any EVPN entries with MAC+IP on the host?

GitHub link: 
https://github.com/apache/cloudstack/discussions/8685#discussioncomment-8561707


This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

Re: CKS Storage Provisioner Info

2024-02-22 Thread Bharat Bhushan Saini

Hi Vivek,

I deployed cloudstack with version 4.18.1.
I think it should be present in this version.

Thanks and Regards,
Bharat Saini

[signature_3238255740]

From: Vivek Kumar 
Date: Friday, 23 February 2024 at 12:48 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Then you will have to deploy the cloudstack-kubernetes-provider, however after 
4.16, it’s automatically deployed, Follow the instruction in the link - 
https://github.com/apache/cloudstack-kubernetes-provider


1- Create a file called - cloud-config and put the below information - ( you 
can create an user under your account and provide it’s apikey and secret key )


[Global]
api-url = 
api-key = 
secret-key = 


2- kubectl -n kube-system create secret generic cloudstack-secret 
--from-file=cloud-config
3- then deploy the controller -

You can then use the provided example deployment.yaml 

 to deploy the controller:

kubectl apply -f deployment.yaml




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Vivek,
>
> I am glad and thankful to you for sharing the information, for the 
> configuration of CSI driver.
>
> But I didn’t have cloudstack-secret in my cluster, sharing the details below
>
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> -n kube-system
> Error from server (NotFound): secrets "cloudstack-secret" not found
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> NAMESPACE  NAME  TYPE 
>  DATA   AGE
> kloudspot  dockerregistrykey 
> kubernetes.io/dockerconfigjson 
> 1  8h
> kube-systembootstrap-token-cb0b7f
> bootstrap.kubernetes.io/token  
> 6  8h
> kubernetes-dashboard   kubernetes-dashboard-certsOpaque   
>  0  8h
> kubernetes-dashboard   kubernetes-dashboard-csrf Opaque   
>  1  8h
> kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque   
>  2  8h
> kubernetes-dashboard   kubernetes-dashboard-token
> kubernetes.io/service-account-token 
>   3  8h
> cloud@Kspot-App-control-18dd041902a:~$
>
> I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> network is in shared mode and using 1 node cluster without HA.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  >
> Date: Thursday, 22 February 2024 at 11:39 PM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> 1- When you deploy a cluster, an additional user is created under your 
> cloudstack account - i.e -kubeadmin,  and apikey and secret key 
> of this kubeadmin user is pushed to the cluster.
>
> This you can find -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
> NAMETYPE DATA   AGE
> cloudstack-secret   Opaque   1  3d5h
>
> To check the more details for this secret -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
> jsonpath='{.data.*}' | base64 -d
> [Global]
> api-url = http://172.27.2.53:8080/client/api
> api-key = 
> ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
> secret-key = 
> IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA
>
>
> Now, you can see the API URL, so this URL endpoint must be reachable from 
> your cluster in order to provision PVC. This URL you can put in the global 
> setting - (endpoint.url)
>
> So I am assuming this endpoint URL is reachable from your cluster -  you 
> don’t need to define anything in the cloud-config and secret - because secret 
> is already created and pushed from cloudstack  once you deploy the cluster. ( 
> From above steps you can verify ).
>
> 2- Deploy the CSI driver - as mentioned in the Link -
>
> kubectl apply -f 
> https://github.com/apalia/cloudstack-csi-driver/releases/latest/download/manifest.yaml
>
>
> 3- Now create the storage class - as mentioned in the Link as example 
>

Re: CKS Storage Provisioner Info

2024-02-22 Thread Vivek Kumar

Hello Bharat, 

Then you will have to deploy the cloudstack-kubernetes-provider, however after 
4.16, it’s automatically deployed, Follow the instruction in the link - 
https://github.com/apache/cloudstack-kubernetes-provider


1- Create a file called - cloud-config and put the below information - ( you 
can create an user under your account and provide it’s apikey and secret key )


[Global]
api-url = 
api-key = 
secret-key = 


2- kubectl -n kube-system create secret generic cloudstack-secret 
--from-file=cloud-config
3- then deploy the controller - 

You can then use the provided example deployment.yaml 

 to deploy the controller:

kubectl apply -f deployment.yaml




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi Vivek,
>  
> I am glad and thankful to you for sharing the information, for the 
> configuration of CSI driver.
>  
> But I didn’t have cloudstack-secret in my cluster, sharing the details below
>  
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> -n kube-system
> Error from server (NotFound): secrets "cloudstack-secret" not found
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> NAMESPACE  NAME  TYPE 
>  DATA   AGE
> kloudspot  dockerregistrykey 
> kubernetes.io/dockerconfigjson 
> 1  8h
> kube-systembootstrap-token-cb0b7f
> bootstrap.kubernetes.io/token  
> 6  8h
> kubernetes-dashboard   kubernetes-dashboard-certsOpaque   
>  0  8h
> kubernetes-dashboard   kubernetes-dashboard-csrf Opaque   
>  1  8h
> kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque   
>  2  8h
> kubernetes-dashboard   kubernetes-dashboard-token
> kubernetes.io/service-account-token 
>   3  8h
> cloud@Kspot-App-control-18dd041902a:~$ 
>  
> I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> network is in shared mode and using 1 node cluster without HA.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Vivek Kumar  >
> Date: Thursday, 22 February 2024 at 11:39 PM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> Hello Bharat,
> 
> 1- When you deploy a cluster, an additional user is created under your 
> cloudstack account - i.e -kubeadmin,  and apikey and secret key 
> of this kubeadmin user is pushed to the cluster.
> 
> This you can find -
> 
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
> NAMETYPE DATA   AGE
> cloudstack-secret   Opaque   1  3d5h
> 
> To check the more details for this secret -
> 
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
> jsonpath='{.data.*}' | base64 -d
> [Global]
> api-url = http://172.27.2.53:8080/client/api
> api-key = 
> ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
> secret-key = 
> IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA
> 
> 
> Now, you can see the API URL, so this URL endpoint must be reachable from 
> your cluster in order to provision PVC. This URL you can put in the global 
> setting - (endpoint.url)
> 
> So I am assuming this endpoint URL is reachable from your cluster -  you 
> don’t need to define anything in the cloud-config and secret - because secret 
> is already created and pushed from cloudstack  once you deploy the cluster. ( 
> From above steps you can verify ).
> 
> 2- Deploy the CSI driver - as mentioned in the Link -
> 
> kubectl apply -f 
> https://github.com/apalia/cloudstack-csi-driver/releases/latest/download/manifest.yaml
> 
> 
> 3- Now create the storage class - as mentioned in the Link as example 
> 
> 
> 
> Create a file i.e storage-class.yml and paste below information - ( Please 
> mention the disk offering ID, it has to be a CUSTOM )
> 
> apiVersion: storage.k8s.io/v1 
> kind: StorageClass
> metadata:
>   name: cloudstack-custom
> provisioner: csi.cloudstack.apache.org

Re: CKS Storage Provisioner Info

2024-02-22 Thread Bharat Bhushan Saini

Hi Vivek,

I am glad and thankful to you for sharing the information, for the 
configuration of CSI driver.


But I didn’t have cloudstack-secret in my cluster, sharing the details below


cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret -n 
kube-system
Error from server (NotFound): secrets "cloudstack-secret" not found
cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
NAMESPACE  NAME  TYPE   
   DATA   AGE
kloudspot  dockerregistrykey 
kubernetes.io/dockerconfigjson1  8h
kube-systembootstrap-token-cb0b7f
bootstrap.kubernetes.io/token 6  8h
kubernetes-dashboard   kubernetes-dashboard-certsOpaque 
   0  8h
kubernetes-dashboard   kubernetes-dashboard-csrf Opaque 
   1  8h
kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque 
   2  8h
kubernetes-dashboard   kubernetes-dashboard-token
kubernetes.io/service-account-token   3  8h
cloud@Kspot-App-control-18dd041902a:~$



I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
network is in shared mode and using 1 node cluster without HA.

Thanks and Regards,
Bharat Saini

[signature_1415706869]

From: Vivek Kumar 
Date: Thursday, 22 February 2024 at 11:39 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

1- When you deploy a cluster, an additional user is created under your 
cloudstack account - i.e -kubeadmin,  and apikey and secret key 
of this kubeadmin user is pushed to the cluster.

This you can find -

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
NAMETYPE DATA   AGE
cloudstack-secret   Opaque   1  3d5h

To check the more details for this secret -

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
jsonpath='{.data.*}' | base64 -d
[Global]
api-url = http://172.27.2.53:8080/client/api
api-key = 
ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
secret-key = 
IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA


Now, you can see the API URL, so this URL endpoint must be reachable from your 
cluster in order to provision PVC. This URL you can put in the global setting - 
(endpoint.url)

So I am assuming this endpoint URL is reachable from your cluster -  you don’t 
need to define anything in the cloud-config and secret - because secret is 
already created and pushed from cloudstack  once you deploy the cluster. ( From 
above steps you can verify ).

2- Deploy the CSI driver - as mentioned in the Link -

kubectl apply -f 
https://github.com/apalia/cloudstack-csi-driver/releases/latest/download/manifest.yaml


3- Now create the storage class - as mentioned in the Link as example 



Create a file i.e storage-class.yml and paste below information - ( Please 
mention the disk offering ID, it has to be a CUSTOM )

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 


kubectl apply -f storage-class.yml

root@18dc14302a2:~# kubectl get storageclass
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  3d5h


4- Now you can test by creating a PVC and POD - ( Examples are already there in 
the link - 
https://github.com/apalia/cloudstack-csi-driver/tree/master/examples/k8s )



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 22-Feb-2024, at 8:11 PM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Vivek/Kiran,
>
> The cluster is deployed in the Root domain. But I am unable to locate 
> cloud-config file configuration after creating a domain user and pls correct 
> me that the cloud-config file have to be configured in controller node.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  >
> Date: Thursday, 22 February 2024 at 5:51 PM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify

Re: CKS Storage Provisioner Info

2024-02-22 Thread Vivek Kumar

Hello Bharat,

1- When you deploy a cluster, an additional user is created under your 
cloudstack account - i.e -kubeadmin,  and apikey and secret key 
of this kubeadmin user is pushed to the cluster.

This you can find -

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system 
NAMETYPE DATA   AGE
cloudstack-secret   Opaque   1  3d5h

To check the more details for this secret - 

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
jsonpath='{.data.*}' | base64 -d
[Global]
api-url = http://172.27.2.53:8080/client/api
api-key = 
ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
secret-key = 
IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA


Now, you can see the API URL, so this URL endpoint must be reachable from your 
cluster in order to provision PVC. This URL you can put in the global setting - 
(endpoint.url)

So I am assuming this endpoint URL is reachable from your cluster -  you don’t 
need to define anything in the cloud-config and secret - because secret is 
already created and pushed from cloudstack  once you deploy the cluster. ( From 
above steps you can verify ).

2- Deploy the CSI driver - as mentioned in the Link - 

kubectl apply -f 
https://github.com/apalia/cloudstack-csi-driver/releases/latest/download/manifest.yaml


3- Now create the storage class - as mentioned in the Link as example 



Create a file i.e storage-class.yml and paste below information - ( Please 
mention the disk offering ID, it has to be a CUSTOM ) 

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 


kubectl apply -f storage-class.yml

root@18dc14302a2:~# kubectl get storageclass
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  3d5h


4- Now you can test by creating a PVC and POD - ( Examples are already there in 
the link - 
https://github.com/apalia/cloudstack-csi-driver/tree/master/examples/k8s )



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 22-Feb-2024, at 8:11 PM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi Vivek/Kiran,
>  
> The cluster is deployed in the Root domain. But I am unable to locate 
> cloud-config file configuration after creating a domain user and pls correct 
> me that the cloud-config file have to be configured in controller node.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Vivek Kumar  >
> Date: Thursday, 22 February 2024 at 5:51 PM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> Hello Bharat,
> 
> Yes, the link provided by Kiran works well for PVC but only one caveat that 
> it only works if your cluster is deployed under ROOT domain.
> 
> 
> 
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
> 
> vivek.ku...@indiqus.com  
> 
> www.indiqus.com  
> 
> 
> 
> 
> > On 22-Feb-2024, at 5:21 PM, Kiran Chavala  > > wrote:
> >
> > Hi Bharat
> >
> > You can try the following CSI driver
> >
> > https://github.com/Leaseweb/cloudstack-csi-driver
> >
> >
> > Regards
> > Kiran
> >
> > From: Bharat Bhushan Saini  > >
> > Date: Thursday, 22 February 2024 at 5:14 PM
> > To: users@cloudstack.apache.org  
> > mailto:users@cloudstack.apache.org>>
> > Subject: CKS Storage Provisioner Info
> > Hi All,
> >
> > As working with the CKS service I had a query regarding with the K8s 
> > storage provisioner.
> > Which provisioner I can use for the shared and unshared PVC in the CKS 
> > service.
> > Please support in this, it will be great help for me.
> >
> > Thanks and Regards,
> > Bharat Saini
> >
> > [signature_1218208545]
> >
> > --- Disclaimer: --
> > This message and its contents are intended solely for the designated 
> > addressee and are proprietary to Kloudspot. The information in this email 
> > is meant exclusively for

Re: Setup Linstor Plugin for ACS

2024-02-22 Thread TechnologyRss

If possible share me exact setup kvm + local storage + linbit

Thanks & Regards.

On Tue, 23 Jan 2024, 2:36 pm ,  wrote:

> Hi,
>
> we are using Linstor on KVM and we are really happy with its performance
> and how it handling errors. We are using drbd-reactor to get the controller
> ha.
> We did a lot of performance testing with lvmthin (inkl. striping) and zfs.
> Linbit support is great, too. They added a feature within days to the
> plugin after we requested it.
>
> Regards,
> Swen
>
> -Ursprüngliche Nachricht-
> Von: Technology Rss 
> Gesendet: Dienstag, 23. Januar 2024 08:11
> An: users@cloudstack.apache.org; d...@cloudstack.apache.org
> Betreff: Setup Linstor Plugin for ACS
>
> Hello community!
>
> I want to setup Linstorplugin for my ACS environment. Please let me know
> any user experience for any issue for production uses.
>
> Also please share any technical details for setup it.
>
> --
>
> *Thanks & Regards.*
>
> *Support Admin*
>
> 
>
> *Facebook  | Twitter <
> https://twitter.com/technologyrss1> | YouTube <
> https://www.youtube.com/channel/UCBq7qGqFEUe6ObVHMuxudTw> | LinkedIn
> *
>
> *Address : *116/1 West Malibagh, D. I. T Road
>
> Dhaka-1217, Bangladesh
>
> *Mob :* +88 01716915504
>
> *Email :* support.ad...@technologyrss.com
>
> *Web :* www.technologyrss.com
>
>
>

Re: [D] EVPN-VXLAN - IPv6 via SLAAC [cloudstack]

2024-02-22 Thread via GitHub



GitHub user tobzsc added a comment to the discussion: EVPN-VXLAN - IPv6 via 
SLAAC

I know you do ;) 

First some background information. We are using an EVPN+MPLS setup in our 
Juniper backbone which is providing connectivity. We have two gateways (MX204) 
which in this case terminate on two spines which do EVPN-MH. This is our cloud 
infrastructure based on EdgeCore devices running SONiC. Here we do EVPN+VXLAN.

We have checked several things and made some observations:
- IPv4 is running without any issues
- We cannot ping link-local addresses and made the observation that multicast 
packets (responsible for NDP and the RAs) are arriving but somehow disappearing 
on our physical links (of the KVM nodes). See tcpdump above - RAs are arriving 
on physical interface but are never seen on our vxlan or bridge interfaces
- When using unicast RAs and sending a ping requests from the router to one of 
the VM it worked for a couple of minutes. We are still trying to find out what 
is exactly wrong here. Seems to be an NDP issue which is also related to 
multicast.
- Connected a physical server directly to our Juniper backbone shows no 
problems with v4 and v6 
- We are now connecting a physical server to our EVPN+VXLAN cloud network to do 
the same tests here.

 The main configuration parts from the Juniper gear you requested:
```
trehn@fra01-pod01-a11-gw01> show configuration interfaces irb unit 200
description "CloudStack Public";
bandwidth 10g;
family inet {
rpf-check {
mode loose;
}
policer {
arp ARP-LIMIT-DEFAULT;
}
address 62.x.x.1/24;
}
family inet6 {
rpf-check {
mode loose;
}
nd6-max-cache 1000;
nd6-new-hold-limit 1000;
address 2a00:x:x:103b::1/64;
}
mac 00:00:x:x:x:00;
```
and
```
trehn@fra01-pod01-a11-gw01> show configuration protocols router-advertisement
traceoptions {
file ipv6-nd-trace;
flag all;
}
interface irb.200 {
solicit-router-advertisement-unicast;
prefix 2a00:x:x:103b::/64;
}
```
The configuration is the same on both gateways.

To sum it up. The multicast IPv6 packets (for NDP, RAs, etc) are arriving on 
our physical interfaces (on the KVM nodes) with correct VNIs, payload, etc. But 
they never ever arrive on the vxlan nor the bridge interface. 

GitHub link: 
https://github.com/apache/cloudstack/discussions/8685#discussioncomment-8558729


This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

VMware Import Timeout

2024-02-22 Thread Kevin Seales

We are trying to use the "Import-Export Instances" tool in ACS to test 
migration from VMware to ACS.  After selecting "List VMware Instances", it 
hangs for 10 minutes, then ACS gives a very detailed error saying "Request 
Failed."  The management logs show ACS is still receiving data from vCenter for 
another 2 or 3 minutes after the failure message.  I'm assuming we are hitting 
a time out somewhere.  I tried adjusting what I could find under global 
settings that may be related but the error still occurs.Does anyone know 
how we can resolve this issue?

Re: CKS Storage Provisioner Info

2024-02-22 Thread Bharat Bhushan Saini

Hi Vivek/Kiran,

The cluster is deployed in the Root domain. But I am unable to locate 
cloud-config file configuration after creating a domain user and pls correct me 
that the cloud-config file have to be configured in controller node.

Thanks and Regards,
Bharat Saini

[signature_1127082807]

From: Vivek Kumar 
Date: Thursday, 22 February 2024 at 5:51 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Yes, the link provided by Kiran works well for PVC but only one caveat that it 
only works if your cluster is deployed under ROOT domain.



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 22-Feb-2024, at 5:21 PM, Kiran Chavala  wrote:
>
> Hi Bharat
>
> You can try the following CSI driver
>
> https://github.com/Leaseweb/cloudstack-csi-driver
> https://github.com/apalia/cloudstack-csi-driver
>
> Regards
> Kiran
>
> From: Bharat Bhushan Saini 
> Date: Thursday, 22 February 2024 at 5:14 PM
> To: users@cloudstack.apache.org 
> Subject: CKS Storage Provisioner Info
> Hi All,
>
> As working with the CKS service I had a query regarding with the K8s storage 
> provisioner.
> Which provisioner I can use for the shared and unshared PVC in the CKS 
> service.
> Please support in this, it will be great help for me.
>
> Thanks and Regards,
> Bharat Saini
>
> [signature_1218208545]
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail communications. Information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> Therefore, Kloudspot shall not be liable for any issues arising from the 
> transmission of this email.
>
>
>


--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: CKS Storage Provisioner Info

2024-02-22 Thread Vivek Kumar

Hello Bharat,

Yes, the link provided by Kiran works well for PVC but only one caveat that it 
only works if your cluster is deployed under ROOT domain.



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 22-Feb-2024, at 5:21 PM, Kiran Chavala  wrote:
> 
> Hi Bharat
> 
> You can try the following CSI driver
> 
> https://github.com/Leaseweb/cloudstack-csi-driver
> https://github.com/apalia/cloudstack-csi-driver
> 
> Regards
> Kiran
> 
> From: Bharat Bhushan Saini 
> Date: Thursday, 22 February 2024 at 5:14 PM
> To: users@cloudstack.apache.org 
> Subject: CKS Storage Provisioner Info
> Hi All,
> 
> As working with the CKS service I had a query regarding with the K8s storage 
> provisioner.
> Which provisioner I can use for the shared and unshared PVC in the CKS 
> service.
> Please support in this, it will be great help for me.
> 
> Thanks and Regards,
> Bharat Saini
> 
> [signature_1218208545]
> 
> --- Disclaimer: --
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail communications. Information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> Therefore, Kloudspot shall not be liable for any issues arising from the 
> transmission of this email.
> 
> 
> 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Re: CKS Storage Provisioner Info

2024-02-22 Thread Kiran Chavala

Hi Bharat

You can try the following CSI driver

https://github.com/Leaseweb/cloudstack-csi-driver
https://github.com/apalia/cloudstack-csi-driver

Regards
Kiran

From: Bharat Bhushan Saini 
Date: Thursday, 22 February 2024 at 5:14 PM
To: users@cloudstack.apache.org 
Subject: CKS Storage Provisioner Info
Hi All,

As working with the CKS service I had a query regarding with the K8s storage 
provisioner.
Which provisioner I can use for the shared and unshared PVC in the CKS service.
Please support in this, it will be great help for me.

Thanks and Regards,
Bharat Saini

[signature_1218208545]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

CKS Storage Provisioner Info

2024-02-22 Thread Bharat Bhushan Saini

Hi All,

As working with the CKS service I had a query regarding with the K8s storage 
provisioner.
Which provisioner I can use for the shared and unshared PVC in the CKS service.
Please support in this, it will be great help for me.

Thanks and Regards,
Bharat Saini

[signature_1218208545]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Experience on GPU Support?

2024-02-22 Thread Bryan Tiang

Hi Guys,

Anyone running Cloudstack with GPU Support in Production? Say NVIDIA H100 or 
AMD M1300X?

Just want to know if there is any support for this still on going, or anyone 
who is running a cloud business with GPUs.

Regards,
Bryan

Re: CKS Storage Provisioner Info

Re: CKS Storage Provisioner Info

Re: [D] EVPN-VXLAN - IPv6 via SLAAC [cloudstack]

Re: CKS Storage Provisioner Info

Re: CKS Storage Provisioner Info

Re: CKS Storage Provisioner Info

Re: CKS Storage Provisioner Info

Re: Setup Linstor Plugin for ACS

Re: [D] EVPN-VXLAN - IPv6 via SLAAC [cloudstack]

VMware Import Timeout

Re: CKS Storage Provisioner Info

Re: CKS Storage Provisioner Info

Re: CKS Storage Provisioner Info

CKS Storage Provisioner Info

Experience on GPU Support?

15 matches

Site Navigation

Mail list logo

Footer information