Basic Setup help
Hello, We are trying to set up a test environment and need assistance with the network part while Zone configuration. We have the following range of IPs. So my query is what details should we enter while creating Zone for Public, Management, and Storage sections. x.x.x.140 x.x.x.141 x.x.x.142 x.x.x.143 x.x.x.144 x.x.x.150 x.x.x.151 x.x.x.152 x.x.x.153 x.x.x.154 x.x.x.155 x.x.x.156 x.x.x.157 Thank you very much, Ranjit
Root disk resizing
Hello folks, I have implemented cloudstack with Xenserver Host. The template has been made out of VM with basic centos 7 and following package installed on it sudo yum -y cloud-init sudo yum -y install cloud-utils-growpart sudo yum -y install gdisk After creating new VM with this template, root disk is created as per size mention in template or we are able to increase it at them time of creation. But later when we try to increase root disk again, it increases disk space but "/" partiton do not get autoresize. Following parameters were passed in userdata #cloud-config growpart: mode: auto devices: ["/"] ignore_growroot_disabled: true Thanks & Regards, Ranjit
Re: Root disk resizing
d for merge or not. > > http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/215/adminguide/templates/_cloud_init.html > > Best regards, > Jordan > > -Original Message- > From: K B Shiv Kumar > Sent: Monday, October 11, 2021 6:51 PM > To: us...@cloudstack.apache.org > Cc: dev@cloudstack.apache.org > Subject: Re: Root disk resizing > > > [X] This message came from outside your organization > > > I believe there's a section called boothook in cloud-init which is > probably what you want. > > We're also trying things on cloud-init. ☺️ > > Best Regards > Shiv > (Sent from mobile device. Apologies for brevity and typos) > > On Mon, 11 Oct, 2021, 20:55 Marcus, wrote: > > > Cloud-init is always fun to debug :-). It will probably require some > > playing with to get a pattern down. > > > > There is perhaps a way to get it to re-check and grow every reboot if > > you adjust/override the module frequency, deleting the module > > semaphore in /var/lib/cloud/sem or worst case clearing the metadata > > via 'cloud-init clear' or deleting the /var/lib/cloud. > > > > On Mon, Oct 11, 2021 at 3:07 AM Wido den Hollander > wrote: > > > > > > > > > > > On 10/10/21 10:35 AM, Ranjit Jadhav wrote: > > > > Hello folks, > > > > > > > > I have implemented cloudstack with Xenserver Host. The template > > > > has > > been > > > > made out of VM with basic centos 7 and following package installed > > > > on > > it > > > > > > > > sudo yum -y cloud-init > > > > sudo yum -y install cloud-utils-growpart sudo yum -y install gdisk > > > > > > > > > > > > After creating new VM with this template, root disk is created as > > > > per > > > size > > > > mention in template or we are able to increase it at them time of > > > creation. > > > > > > > > But later when we try to increase root disk again, it increases > > > > disk > > > space > > > > but "/" partiton do not get autoresize. > > > > > > > > > > As far as I know it only grows the partition once, eg, upon first boot. > > > I won't do it again afterwards. > > > > > > Wido > > > > > > > > > > > Following parameters were passed in userdata > > > > > > > > #cloud-config > > > > growpart: > > > > mode: auto > > > > devices: ["/"] > > > > ignore_growroot_disabled: true > > > > > > > > > > > > Thanks & Regards, > > > > Ranjit > > > > > > > > > >
Network selection specifically for Hosting provider
Hello guys, We are using Xenserver for host and configured Isolated Network . but we are facing the following issues 1) One IP gets reserved for source-nat per user 2) How can we assign secondary IP to the instance. There are a few more issues/queries related to the network. Thanks and Regards, Ranjit
Re: Network selection specifically for Hosting provider
Thanks for getting back to me. At the ACS level network is configured fine but at the OS level, it does not get updated. By default, OS is using DHCP. In this case, how can we automatically configure secondary IP on the server i.e. CentOS, Ubuntu, Windows etc. Thank you, Ranjit On Wed, Oct 20, 2021 at 12:05 PM Wei ZHOU wrote: > Hi, > > For each isolated network with source NAT, cloudstack assigns a public IP > to the network as the source NAT IP. Therefore it is not an issue. > > To add secondary IPs, go to vm details -> NICs tab -> choose a NIC -> click > icon 'Edit secondary IPs'. > > -Wei > > On Tue, 19 Oct 2021 at 23:35, Ranjit Jadhav > wrote: > > > Hello guys, > > > > We are using Xenserver for host and configured Isolated Network . but > > we are facing the following issues > > > > 1) One IP gets reserved for source-nat per user > > > > 2) How can we assign secondary IP to the instance. > > > > There are a few more issues/queries related to the network. > > > > Thanks and Regards, > > Ranjit > > >
DDoS protection
Hello, What are options available for DDoS protection which we can integrate with Cloudstack? Thank you, Ranjit
Re: Network selection specifically for Hosting provider
Hello, Thanks for getting back to me. Currently, we are assigning secondary IP from the same subnet using DHCP. Alike a "guest, password" is there any script that we can trigger to update the network configuration. At the ACS level we can set up static route using API's Thanks again, Ranjit On Mon, Oct 25, 2021 at 4:46 PM Vivek Kumar wrote: > Hello Ranjit, > > When you add secondary IPs to the instance, it means you will provide the > same subnet IP in secondary interface of the NIC, So you have to configure > your VM in such a way so that they can obtain the IP from DHCP ( You create > sub interface of your primary interface i.e tho is your primary then > eth0:0, eth0:1 is your sub interface . > > If you are adding another network in your VM it means that you are adding > a additional NIC in your VM thus - You will have to configure your second > NIC config file inside of the VM so that it can get the IP from DHCP ( i.e > eth0, eth1 ). > > > > Vivek Kumar > Sr. Manager - Cloud & DevOps > IndiQus Technologies > M +91 7503460090 > www.indiqus.com > > > > > > On 23-Oct-2021, at 2:27 AM, Ranjit Jadhav > wrote: > > > > Thanks for getting back to me. At the ACS level network is configured > fine > > but at the OS level, it does not get updated. By default, OS is using > DHCP. > > > > In this case, how can we automatically configure secondary IP on the > server > > i.e. CentOS, Ubuntu, Windows etc. > > > > Thank you, > > Ranjit > > > > On Wed, Oct 20, 2021 at 12:05 PM Wei ZHOU wrote: > > > >> Hi, > >> > >> For each isolated network with source NAT, cloudstack assigns a public > IP > >> to the network as the source NAT IP. Therefore it is not an issue. > >> > >> To add secondary IPs, go to vm details -> NICs tab -> choose a NIC -> > click > >> icon 'Edit secondary IPs'. > >> > >> -Wei > >> > >> On Tue, 19 Oct 2021 at 23:35, Ranjit Jadhav > >> wrote: > >> > >>> Hello guys, > >>> > >>> We are using Xenserver for host and configured Isolated Network . > but > >>> we are facing the following issues > >>> > >>> 1) One IP gets reserved for source-nat per user > >>> > >>> 2) How can we assign secondary IP to the instance. > >>> > >>> There are a few more issues/queries related to the network. > >>> > >>> Thanks and Regards, > >>> Ranjit > >>> > >> > >
Load Balancer Sticky Policies
Hello, Once a load balancer rule is created in the ACS and next, we want to configure the Sticky policies for a particular rule we click on configure but once we fill required details for sticky policy the submit/ok button seems to be not working as expected. No API is being fired for sticky policy. Any solution on this, please? Thanks, Ranjit
Re: Load Balancer Sticky Policies
It doesn't work at all for whatever type we select. Also, the API seems to be not working as well. (May be due to this issue) Thanks Ranjit On Fri, Dec 24, 2021 at 8:59 PM Ricardo Andres Pertuz de las Salas < ricardo.per...@kuasar.co> wrote: > Which cookie type are you trying to configure, can you copy here the form? > > On 24/12/21, 8:13 AM, "Ranjit Jadhav" wrote: > > Hello, > > Once a load balancer rule is created in the ACS and next, we want to > configure the Sticky policies for a particular rule we click on > configure > but once we fill required details for sticky policy the submit/ok > button > seems to be not working as expected. > > No API is being fired for sticky policy. Any solution on this, please? > > Thanks, > Ranjit > >
Re: Not able to autoscale kubernetes cluster
Hello folks,
Any insight on this? We are facing the same issue.
Regards,
Ranjit
On Mon, 31 Jan 2022 at 22:48, Rishabh Rapatwar
wrote:
> Hi all,
>
> I am trying to autoscale kubernetes cluster, but it's not working.
> Following are the logs of cluster-autoscaler pod in kube-system:
>
> I0131 17:01:11.537869 1 client.go:175] NewAPIRequest response status
> code:200
> I0131 17:01:11.538288 1 cloudstack_manager.go:88] Got cluster :
> &{c6496415-daea-4051-993a-3b9f9c58242e voyager 1 3 2
> 1 [0xc000e889f0 0xc000e88a20 0xc000e88a50]}
> E0131 17:01:11.538366 1 static_autoscaler.go:271] Failed to get node
> infos for groups: Unable to find node voyager-c
> ontrol-17ea9f68878 in cluster
> I0131 17:01:21.538749 1 static_autoscaler.go:229] Starting main loop
>
> ACS version used is 4.16, and kubernetes version is 1.22.2
>
> Can anyone please help here?
>
>
> Thankyou,
> Rishabh
>
Auto-scaling not working for kubernetes cluster
Hello Folks, We are getting the following error while testing autoscaling with kubernetes cluster. Any hint would be appreciated. Failed to get node infos for groups: Unable to find node in cluster Thank you, Ranjit
Update Rules for Default Roles
Hello Folks, I am getting the below error while trying to update Rules for Role Domain Admin, any suggestions on a workaround. Request Failed (531) Role permission cannot be added for Default roles Any hint/solution will be of great help. Thanks and regards, Ranjit
ACS Upgrade Failed :: Xenserver
Hello, While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we faced the following issue. It appears that "cloudstack-management" and "cloudstack-usage" requires different versions of cloudstack-common. With cloudstack-common=4.17 Management, services are working but Usage services are asking for 4.16.1.0~bionic == The following packages have unmet dependencies: cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but 4.17.0.0~bionic is to be installed E: Unable to correct problems, you have held broken packages. == We followed the steps below to upgrade ACS https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.16.html#system-vms-and-virtual-routers The server is setup on Ubuntu 18.04 with Xenserver(VM on Xcp-ng) Any guidance would be appreciated. Thank you
Re: ACS Upgrade Failed :: Xenserver
Hello, Thanks for getting back to me. Nothing specific in logs, getting following error while we are trying to reinstall the services. = root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but 4.17.0.0~bionic is to be installed E: Unable to correct problems, you have held broken packages. = Thank you, Ranjit On Mon, 20 Jun 2022 at 08:17, Harikrishna Patnala < harikrishna.patn...@shapeblue.com> wrote: > Hi Ranjit, > > CloudStack management and usage have to be on the same version, can you > please check the version of CloudStack usage server and verify if the > upgrade to 4.17 happened properly. If not on 4.17, can you please try to > upgrade the usage server? > > Please paste the exact error from the management server or usage server > logs that you are seeing. > > Thanks, > Harikrishna > > ____ > From: Ranjit Jadhav > Sent: Saturday, June 18, 2022 5:53 PM > To: us...@cloudstack.apache.org ; dev < > dev@cloudstack.apache.org> > Subject: ACS Upgrade Failed :: Xenserver > > Hello, > > While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we faced > the following issue. It appears that "cloudstack-management" and > "cloudstack-usage" requires different versions of cloudstack-common. > > With cloudstack-common=4.17 Management, services are working but Usage > services are asking for 4.16.1.0~bionic > > == > The following packages have unmet dependencies: > cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but > 4.17.0.0~bionic is to be installed > E: Unable to correct problems, you have held broken packages. > == > > We followed the steps below to upgrade ACS > > > https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.16.html#system-vms-and-virtual-routers > > The server is setup on Ubuntu 18.04 with Xenserver(VM on Xcp-ng) > > Any guidance would be appreciated. > > Thank you > > > >
Re: ACS Upgrade Failed :: Xenserver
Hello, Thanks for the update, I tried with bionic but got the error below. After changing to focal it worked, both management and usage services are online. But the SystemVM version is still 4.16.1. Shall we import the template again? What should be the approach now. root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: *The following packages have unmet dependencies: cloudstack-usage : Depends: cloudstack-common (= 4.17.0.0~focal) but 4.17.0.0~bionic is to be installedE: Unable to correct problems, you have held broken packages.root@cloudstack1:~#* On Mon, 20 Jun 2022 at 18:51, Gabriel Bräscher wrote: > Ranjit can you please try the upgrade again? > > There was an issue with the mirror for the usage package (4.17.0.0 bionic > only). > Should be good now (the mirror might still be syncing, but I bet it is > already good to go). > > Regards, > Gabriel. > > On Mon, Jun 20, 2022 at 6:15 AM Ranjit Jadhav > wrote: > > > Hello, > > > > Thanks for getting back to me. Nothing specific in logs, getting > following > > error while we are trying to reinstall the services. > > > > = > > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but > > 4.17.0.0~bionic is to be installed > > E: Unable to correct problems, you have held broken packages. > > = > > > > Thank you, > > Ranjit > > > > On Mon, 20 Jun 2022 at 08:17, Harikrishna Patnala < > > harikrishna.patn...@shapeblue.com> wrote: > > > > > Hi Ranjit, > > > > > > CloudStack management and usage have to be on the same version, can you > > > please check the version of CloudStack usage server and verify if the > > > upgrade to 4.17 happened properly. If not on 4.17, can you please try > to > > > upgrade the usage server? > > > > > > Please paste the exact error from the management server or usage server > > > logs that you are seeing. > > > > > > Thanks, > > > Harikrishna > > > > > > > > > From: Ranjit Jadhav > > > Sent: Saturday, June 18, 2022 5:53 PM > > > To: us...@cloudstack.apache.org ; dev < > > > dev@cloudstack.apache.org> > > > Subject: ACS Upgrade Failed :: Xenserver > > > > > > Hello, > > > > > > While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we > > faced > > > the following issue. It appears that "cloudstack-management" and > > > "cloudstack-usage" requires different versions of cloudstack-common. > > > > > > With cloudstack-common=4.17 Management, services are working but Usage > > > services are asking for 4.16.1.0~bionic > > > > > > == > > > The following packages have unmet dependencies: > > > cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but > > > 4.17.0.0~bionic is to be installed > > > E: Unable to correct problems, you have held broken packages. > > > == > > > > > > We followed the steps below to upgrade ACS > > > > > > > > > > > > https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.16.html#system-vms-and-virtual-routers > > > > > > The server is setup on Ubuntu 18.04 with Xenserver(VM on Xcp-ng) > > > > > > Any guidance would be appreciated. > > > > > > Thank you > > > > > > > > > > > > > > >
Re: ACS Upgrade Failed :: Xenserver
While trying to switch back to Bionic from Focal, please advice root@cloudstack1:~# sudo apt-get install cloudstack-management=4.17.0.0~bionic Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cloudstack-management : Depends: cloudstack-common (= 4.17.0.0~bionic) but 4.17.0.0~focal is to be installed E: Unable to correct problems, you have held broken packages. root@cloudstack1:~# On Tue, 21 Jun 2022 at 18:32, Ranjit Jadhav wrote: > Hello, > > Thanks for the update, I tried with bionic but got the error below. After > changing to focal it worked, both management and usage services are online. > But the SystemVM version is still 4.16.1. Shall we import the template > again? What should be the approach now. > > > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > > or been moved out of Incoming. > The following information may help to resolve the situation: > > > > > *The following packages have unmet dependencies: cloudstack-usage : > Depends: cloudstack-common (= 4.17.0.0~focal) but 4.17.0.0~bionic is to be > installedE: Unable to correct problems, you have held broken > packages.root@cloudstack1:~#* > > > > On Mon, 20 Jun 2022 at 18:51, Gabriel Bräscher > wrote: > >> Ranjit can you please try the upgrade again? >> >> There was an issue with the mirror for the usage package (4.17.0.0 bionic >> only). >> Should be good now (the mirror might still be syncing, but I bet it is >> already good to go). >> >> Regards, >> Gabriel. >> >> On Mon, Jun 20, 2022 at 6:15 AM Ranjit Jadhav >> wrote: >> >> > Hello, >> > >> > Thanks for getting back to me. Nothing specific in logs, getting >> following >> > error while we are trying to reinstall the services. >> > >> > = >> > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage >> > Reading package lists... Done >> > Building dependency tree >> > Reading state information... Done >> > Some packages could not be installed. This may mean that you have >> > requested an impossible situation or if you are using the unstable >> > distribution that some required packages have not yet been created >> > or been moved out of Incoming. >> > The following information may help to resolve the situation: >> > >> > The following packages have unmet dependencies: >> > cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but >> > 4.17.0.0~bionic is to be installed >> > E: Unable to correct problems, you have held broken packages. >> > = >> > >> > Thank you, >> > Ranjit >> > >> > On Mon, 20 Jun 2022 at 08:17, Harikrishna Patnala < >> > harikrishna.patn...@shapeblue.com> wrote: >> > >> > > Hi Ranjit, >> > > >> > > CloudStack management and usage have to be on the same version, can >> you >> > > please check the version of CloudStack usage server and verify if the >> > > upgrade to 4.17 happened properly. If not on 4.17, can you please try >> to >> > > upgrade the usage server? >> > > >> > > Please paste the exact error from the management server or usage >> server >> > > logs that you are seeing. >> > > >> > > Thanks, >> > > Harikrishna >> > > >> > > >> > > From: Ranjit Jadhav >> > > Sent: Saturday, June 18, 2022 5:53 PM >> > > To: us...@cloudstack.apache.org ; dev < >> > > dev@cloudstack.apache.org> >> > > Subject: ACS Upgrade Failed :: Xenserver >> > > >> > > Hello, >> > > >> > > While attempt
Re: ACS Upgrade Failed :: Xenserver
Thanks for getting back to me, here are the required details from our setup. Upgrade went well without any errors, but SystemVM are not upgraded yet. Check for the screenshot attached. I can see "label.guest.vlan <http://103.13.114.141:8080/client/#/guestvlans>" section added under Network though. root@cloudstack1:~# apt list --installed -a cloudstack-management Listing... Done cloudstack-management/bionic,now 4.17.0.0~bionic all [installed] cloudstack-management/bionic 4.16.1.0~bionic all cloudstack-management/bionic 4.16.0.0~bionic all == root@cloudstack1:~# apt list --installed -a cloudstack-usage Listing... Done cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed] cloudstack-usage/bionic 4.16.1.0~bionic all cloudstack-usage/bionic 4.16.0.0~bionic all == root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list #deb http://download.cloudstack.org/ubuntu bionic 4.15 deb http://download.cloudstack.org/ubuntu bionic 4.16 deb http://download.cloudstack.org/ubuntu bionic 4.17 Thank you, Ranjit On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher wrote: > Ranji, sorry by the delay. > > Can you please share what is the configuration set in > /etc/apt/sources.list.d/cloudstack.list? > should be something such as "deb http://download.cloudstack.org/ubuntu > bionic 4.17". > > I've just managed to install it but noticed that the mirror needed to > resync (some cache or something was not right). > > Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'... > Setting up cloudstack-usage (4.17.0.0~bionic) ... > Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic ! > > * Project website: https://cloudstack.apache.org/ > * Documentation: > https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/ > * Release notes: > https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/ > * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html > * Take the survey: https://cloudstack.apache.org/survey.html > * Report issues: https://github.com/apache/cloudstack/issues/new > > Created symlink > /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service → > /lib/systemd/system/cloudstack-usage.service. > > Can you please re-try? > Might require updating the apt sources list and running "apt-get update" > again? > > Best regards, > Gabriel. > > > > On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav > wrote: > > > While trying to switch back to Bionic from Focal, please advice > > > > > > root@cloudstack1:~# sudo apt-get install > > cloudstack-management=4.17.0.0~bionic > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > cloudstack-management : Depends: cloudstack-common (= 4.17.0.0~bionic) > but > > 4.17.0.0~focal is to be installed > > E: Unable to correct problems, you have held broken packages. > > root@cloudstack1:~# > > > > > > On Tue, 21 Jun 2022 at 18:32, Ranjit Jadhav > > wrote: > > > > > Hello, > > > > > > Thanks for the update, I tried with bionic but got the error below. > After > > > changing to focal it worked, both management and usage services are > > online. > > > But the SystemVM version is still 4.16.1. Shall we import the template > > > again? What should be the approach now. > > > > > > > > > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage > > > Reading package lists... Done > > > Building dependency tree > > > Reading state information... Done > > > Some packages could not be installed. This may mean that you have > > > requested an impossible situation or if you are using the unstable > > > distribution that some required packages have not yet been created > > > > > > or been moved out of Incoming. > > > The following information may help to resolve the situation: > > > > > > > > > > > > > > > *The following packages have unm
Re: ACS Upgrade Failed :: Xenserver
Hello Gabriel . Harikrishna , Everything looks good now, the upgrade process was completed. Thank you very much for your assistance. On Thu, 23 Jun 2022 at 02:18, Ranjit Jadhav wrote: > Thanks for getting back to me, here are the required details from our > setup. Upgrade went well without any errors, but SystemVM are not upgraded > yet. > Check for the screenshot attached. I can see "label.guest.vlan > <http://103.13.114.141:8080/client/#/guestvlans>" section added under > Network though. > > > root@cloudstack1:~# apt list --installed -a cloudstack-management > Listing... Done > cloudstack-management/bionic,now 4.17.0.0~bionic all [installed] > cloudstack-management/bionic 4.16.1.0~bionic all > cloudstack-management/bionic 4.16.0.0~bionic all > > == > > root@cloudstack1:~# apt list --installed -a cloudstack-usage > Listing... Done > cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed] > cloudstack-usage/bionic 4.16.1.0~bionic all > cloudstack-usage/bionic 4.16.0.0~bionic all > > == > > root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list > #deb http://download.cloudstack.org/ubuntu bionic 4.15 > deb http://download.cloudstack.org/ubuntu bionic 4.16 > deb http://download.cloudstack.org/ubuntu bionic 4.17 > > Thank you, > Ranjit > > On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher > wrote: > >> Ranji, sorry by the delay. >> >> Can you please share what is the configuration set in >> /etc/apt/sources.list.d/cloudstack.list? >> should be something such as "deb http://download.cloudstack.org/ubuntu >> bionic 4.17". >> >> I've just managed to install it but noticed that the mirror needed to >> resync (some cache or something was not right). >> >> Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'... >> Setting up cloudstack-usage (4.17.0.0~bionic) ... >> Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic ! >> >> * Project website: https://cloudstack.apache.org/ >> * Documentation: >> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/ >> * Release notes: >> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/ >> * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html >> * Take the survey: https://cloudstack.apache.org/survey.html >> * Report issues: https://github.com/apache/cloudstack/issues/new >> >> Created symlink >> /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service → >> /lib/systemd/system/cloudstack-usage.service. >> >> Can you please re-try? >> Might require updating the apt sources list and running "apt-get update" >> again? >> >> Best regards, >> Gabriel. >> >> >> >> On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav >> wrote: >> >> > While trying to switch back to Bionic from Focal, please advice >> > >> > >> > root@cloudstack1:~# sudo apt-get install >> > cloudstack-management=4.17.0.0~bionic >> > Reading package lists... Done >> > Building dependency tree >> > Reading state information... Done >> > Some packages could not be installed. This may mean that you have >> > requested an impossible situation or if you are using the unstable >> > distribution that some required packages have not yet been created >> > or been moved out of Incoming. >> > The following information may help to resolve the situation: >> > >> > The following packages have unmet dependencies: >> > cloudstack-management : Depends: cloudstack-common (= 4.17.0.0~bionic) >> but >> > 4.17.0.0~focal is to be installed >> > E: Unable to correct problems, you have held broken packages. >> > root@cloudstack1:~# >> > >> > >> > On Tue, 21 Jun 2022 at 18:32, Ranjit Jadhav >> > wrote: >> > >> > > Hello, >> > > >> > > Thanks for the update, I tried with bionic but got the error below. >> After >> > > changing to focal it worked, both management and usage services are >> > online. >> > > But the SystemVM version is still 4.16.1. Shall we import the template >> > > again? What should be the approach now. >> > > >> > > >> > > root@cloudstack1:~# sudo ap
CEPH Support on Xenserver
Hello, There are mixed reviews on Cloudstack setup on Xenserver with CEPH as Storage (both Primary n Secondary) . insight on this will be very helpful. Regards, Ranjit
Issues with Kubernetes
Hello Folks, We have an HA cloudstack setup but when we are creating a K8S cluster, the cluster is not getting created, I can see that I'm able to console the control node, but when I console the worker node, it says, 'Access is denied for the console session. Please close the window and retry again. I wasn't able to find any particular logs that could give me a clear insight into the problem. However, I could find the find below logs that I think could be the problem. --- Waiting for Kubernetes cluster : voyager control node VMs to be accessible --- Unable to find matched VM in CloudStack DB. name: i-2-11-VM --- Regards, Ranjit
Re: Issues with Kubernetes
We are seeing following error in logs
2022-11-07 13:51:09,064 DEBUG [c.c.a.t.Request]
(API-Job-Executor-36:ctx-eae067a5 job-1464 ctx-03d611b7) (logid:42f2c60e)
Seq 3-478788935384826404: Received: { Ans: , MgmtId: 112810681648291, via:
3(comp3), Ver: v1, Flags: 10, { Answer } }
2022-11-07 13:51:09,076 INFO [c.c.k.c.a.KubernetesClusterActionWorker]
(API-Job-Executor-36:ctx-eae067a5 job-1464 ctx-03d611b7) (logid:42f2c60e)
Detached Kubernetes binaries from VM : test-node-184522598f7 in the
Kubernetes cluster : test
2022-11-07 13:51:09,077 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-36:ctx-eae067a5 job-1464) (logid:42f2c60e) Complete async
job-1464, jobStatus: FAILED, resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Failed
to setup Kubernetes cluster : test in usable state as unable to access
control node VMs of the cluster"}
2022-11-07 13:51:09,078 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-36:ctx-eae067a5 job-1464) (logid:42f2c60e) Publish async
job-1464 complete on message bus
2022-11-07 13:51:09,078 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-36:ctx-eae067a5 job-1464) (logid:42f2c60e) Wake up jobs
related to job-1464
2022-11-07 13:51:09,078 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-36:ctx-eae067a5 job-1464) (logid:42f2c60e) Update db
status for job-1464
2022-11-07 13:51:09,079 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-36:ctx-eae067a5 job-1464) (logid:42f2c60e) Wake up jobs
joined with job-1464 and disjoin all subjobs created from job- 1464
2022-11-07 13:51:09,083 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-36:ctx-eae067a5 job-1464) (logid:42f2c60e) Done executing
org.apache.cloudstack.api.command.user.kubernetes.cluster.CreateKubernetesClusterCmd
for job-1464
--
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
2022-11-07 14:02:21,654 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-52:ctx-ad3791c7 job-1505) (logid:671c031b) Complete async
job-1505, jobStatus: FAILED, resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"ip
address is used for source nat purposes and can not be disassociated."}
2022-11-07 14:02:21,655 DEBUG [c.c.n.f.FirewallManagerImpl]
(API-Job-Executor-53:ctx-a2774db9 job-1506 ctx-60050a4c) (logid:8a26d8cc)
Releasing 0 firewall rules for ip id=236
2022-11-07 14:02:21,655 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-52:ctx-ad3791c7 job-1505) (logid:671c031b) Publish async
job-1505 complete on message bus
2022-11-07 14:02:21,655 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-52:ctx-ad3791c7 job-1505) (logid:671c031b) Wake up jobs
related to job-1505
2022-11-07 14:02:21,655 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-52:ctx-ad3791c7 job-1505) (logid:671c031b) Update db
status for job-1505
2022-11-07 14:02:21,656 DEBUG [c.c.n.f.FirewallManagerImpl]
(API-Job-Executor-53:ctx-a2774db9 job-1506 ctx-60050a4c) (logid:8a26d8cc)
There are no firewall rules to apply
Any guidelines will be helpful
Regards,
Ranjit
On Thu, 3 Nov 2022 at 23:44, Ranjit Jadhav wrote:
> Hello Folks,
>
> We have an HA cloudstack setup but when we are creating a K8S cluster, the
> cluster is not getting created, I can see that I'm able to console the
> control node, but when I console the worker node, it says,
>
> 'Access is denied for the console session. Please close the window and
> retry again.
>
> I wasn't able to find any particular logs that could give me a clear
> insight into the problem. However, I could find the find below logs that I
> think could be the problem.
>
> ---
> Waiting for Kubernetes cluster : voyager control node VMs to be accessible
> ---
> Unable to find matched VM in CloudStack DB. name: i-2-11-VM
> ---
>
> Regards,
> Ranjit
>
Query regarding Secondary Storage
Hello Guys, Is it possible to add additional secondary storage specifically for Snapshots? Thank you, Ranjit
Re: VMs HA not working with Ceph
Hello Guys, We are also struggling with this HA thing any guidance will be highly appreciated. Regards, Ranjit On Thu, 1 Dec 2022 at 20:50, pspa...@hotmail.com wrote: > Hi, > I have build new infra with Ceph storage everything working well. > But VMs HA not working. Can anyone guide me. > > Regards Pradeep Kumar
Re: VMs HA not working with Ceph
Thank you very much for the input, I will try and let you know. Regards, Ranjit On Mon, 5 Dec 2022 at 22:06, Nux wrote: > Great pointer, Daniel, thank you! > > > --- > Nux > www.nux.ro > > On 2022-12-05 16:26, Daniel Augusto Veronezi Salvador wrote: > > Hello, Ranjit and Nux > > > > About the second point in the last message: there is no need to edit > > the file 'kvmheartbeat.sh' to avoid restarting the host. PR #4586[¹], > > released in 4.16.0, introduced the property > > 'reboot.host.and.alert.management.on.heartbeat.timeout' in > > 'agent.properties'; if true (default) it will reboot the host if > > something goes wrong with the heartbeat; on the other hand, if set to > > false, it will not reboot the host. After changing the properties, it > > is necessary to restart the agent service. > > > > Best regards, > > Daniel Salvador (gutoveronezi) > > > > [¹]https://github.com/apache/cloudstack/pull/4586 > > <https://github.com/apache/cloudstack/pull/4586> > > > > On 05/12/2022 12:38, Nux wrote: > >> Hello, > >> > >> For HA to work you need to: > >> 1 - add a service offering with "HA" box enabled > >> 2 - you need to have some NFS storage for the heartbeat/fencing > >> mechanism - you don't need to use it for VMs, but it needs to be > >> present and it needs to be super reliable or hypervisors might reboot > >> if they see it goes away - this behaviour can be customised if you > >> want to (and know what you are doing): > >> > https://github.com/apache/cloudstack/blob/a63b2aba7aa3948f78d280a356c550c6638a137b/scripts/vm/hypervisor/kvm/kvmheartbeat.sh#L162 > >> HTH > >> > >> --- > >> Nux > >> www.nux.ro > >> > >> On 2022-12-02 07:02, Ranjit Jadhav wrote: > >>> Hello Guys, > >>> > >>> We are also struggling with this HA thing any guidance will be highly > >>> appreciated. > >>> > >>> Regards, > >>> Ranjit > >>> > >>> On Thu, 1 Dec 2022 at 20:50, pspa...@hotmail.com > >>> > >>> wrote: > >>> > >>>> Hi, > >>>> I have build new infra with Ceph storage everything working well. > >>>> But VMs HA not working. Can anyone guide me. > >>>> > >>>> Regards Pradeep Kumar >
User-Data for Windows Instance
Hello Folks. On the KVM hypervisor, we need to pass user-data i.e. bat script while creating a windows instance. Is it possible? Which guest-tools should we use? Thank you, Ranjit
Kubernetes Issues
Hello All I am facing a weird issue while creating Kubernetes, sometimes it is creating and sometimes it goes to error state saying "Provisioning node VM failed in the Kubernetes cluster" ACS Version: 4.17.2 Does anyone have an idea or has faced a similar issue? Any help would be appreciated. Thank you!
