Re: All cluster reboot when a Primary storage fails
Hey Daniel, PR #4586 (https://github.com/apache/cloudstack/pull/4586) addressed your issue, as well. I'm currently working on it. Could you share with me how I can reproduce your reboot problem? Kind regards, Sina ‐‐‐ Original Message ‐‐‐ On Saturday, October 16th, 2021 at 05:40, Daniel Augusto Veronezi Salvador wrote: > Hi Mauro, > > On KVM's monitor, when there is an inconsistency on the heartbeat's file > > or heartbeat timeout is extrapolated several times, by default, the host > > is restarted. > > The PR 4586 (https://github.com/apache/cloudstack/pull/4586) already > > addressed this issue by externalizing a property, which allows the > > operator to decide if the host must be restarted or not (default is > > 'true', meaning that the host will be restarted). However, this feature > > will be available only after release 4.16. > > Best regards, > > Daniel Salvador > > On 15/10/2021 20:43, Mauro Ferraro - G2K Hosting wrote: > > > Hi guys, how are you?. > > > > We are having this problems with ACS when a primary storages fails. > > > > We have several primary storage with Linux and NFS server serving KVM > > > > images. So every hosts have been mounted all the NFS servers because > > > > in one Host can be running VMs from different storages. The main > > > > problem of this, is when some storage fails because any reason all the > > > > cluster gets crazy and start rebooting the hosts to reconnect with > > > > this storage and all the VMs on the cluster, (including the VMs that > > > > were working good) goes down becuase the conection to one storage fails. > > > > If the problem with storage is permanent, the cluster never start > > > > again and hosts will reboot indefinitely. > > > > When this problem appears, the logs say this: > > > > host heartbeat: kvmheartbeat.sh will reboot system because it was > > > > unable to write the heartbeat to the storage. > > > > Many users, edit the script kvmheartbeat.shto avoid the hosts reboot > > > > or restart the agent on the host but i really not be sure that this is > > > > the real solution. > > > > Can someone help to propose a best solution at this high risk problem?. > > > > Regards, > > > > Mauro signature.asc Description: OpenPGP digital signature
Re: ACS 4.15.1 / XCP-NG 8.2
Hello, I had the same issue as Benoit with Cloudstack 4.15.1 and XCP-NG 8.2. I have read the link below and follow the recommendations but it's still impossible to scale up a VM. When we deploy a VM, memory-static-min and memory-static-max = memory set on the compute offering. Has anyone had the same issue and how did you solve it ? Thanks for your help. Best regards, Florian On 2021/10/19 14:17:22, nu...@li.nux.ro wrote: > Hello,> > > Give this a read, see if helps.> > > https://users.cloudstack.apache.narkive.com/f1vzARuw/dynamic-scaling-of-cpu-and-ram-not-working#post8> > > HTH> > > On 2021-10-19 14:42, benoit lair wrote:> > > Hello,> > > > > > I am trying to scale up a Debian VM from 4Go to 8Go ram> > > I ran into the following error :> > > > > > 2021-10-19 15:33:05,803 DEBUG > > > [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper]> > > (DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception> > > com.cloud.utils.exception.CloudRuntimeException when scaling > > > VM:i-2-83-VM> > > due to com.cloud.utils.exception.CloudRuntimeException: Cannot scale up > > > the> > > vm because of memory constraint violation: 0 <=> > > memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <=> > > memory-dynamic-max(8589934592) <= memory-static-max(4294967296)> > > > > > Any ideas ?> > > > > > Regards, Benoit Lair> >
RE: All cluster reboot when a Primary storage fails
Hi, I experienced this problem myself, in the KVM, Ceph, NFS-Ganesha environment at full Ceph load, the Ganesha NFS server was able to hang. Servers were able to randomly restart due to lack of NFS access. Which magnified the problem and there was a cascade and restart of the entire environment. We currently have the restart line removed in kvmheartbeat, instead we report the restart attempt via prometheus. Regards, Piotr -Original Message- From: Sina Kashipazha Sent: Wednesday, October 20, 2021 10:35 AM To: users@cloudstack.apache.org Subject: Re: All cluster reboot when a Primary storage fails Hey Daniel, PR #4586 (https://github.com/apache/cloudstack/pull/4586) addressed your issue, as well. I'm currently working on it. Could you share with me how I can reproduce your reboot problem? Kind regards, Sina ‐‐‐ Original Message ‐‐‐ On Saturday, October 16th, 2021 at 05:40, Daniel Augusto Veronezi Salvador wrote: > Hi Mauro, > > On KVM's monitor, when there is an inconsistency on the heartbeat's file > > or heartbeat timeout is extrapolated several times, by default, the host > > is restarted. > > The PR 4586 (https://github.com/apache/cloudstack/pull/4586) already > > addressed this issue by externalizing a property, which allows the > > operator to decide if the host must be restarted or not (default is > > 'true', meaning that the host will be restarted). However, this feature > > will be available only after release 4.16. > > Best regards, > > Daniel Salvador > > On 15/10/2021 20:43, Mauro Ferraro - G2K Hosting wrote: > > > Hi guys, how are you?. > > > > We are having this problems with ACS when a primary storages fails. > > > > We have several primary storage with Linux and NFS server serving KVM > > > > images. So every hosts have been mounted all the NFS servers because > > > > in one Host can be running VMs from different storages. The main > > > > problem of this, is when some storage fails because any reason all the > > > > cluster gets crazy and start rebooting the hosts to reconnect with > > > > this storage and all the VMs on the cluster, (including the VMs that > > > > were working good) goes down becuase the conection to one storage fails. > > > > If the problem with storage is permanent, the cluster never start > > > > again and hosts will reboot indefinitely. > > > > When this problem appears, the logs say this: > > > > host heartbeat: kvmheartbeat.sh will reboot system because it was > > > > unable to write the heartbeat to the storage. > > > > Many users, edit the script kvmheartbeat.shto avoid the hosts reboot > > > > or restart the agent on the host but i really not be sure that this is > > > > the real solution. > > > > Can someone help to propose a best solution at this high risk problem?. > > > > Regards, > > > > Mauro
Re: Migration between regions
Hey Evgeniy, Do you want to migrate between two physical locations or upgrade your system to a newer version? We usually do the physical migration in the following order: 1. Set up a new host in the new location (Let's call it h1). 2. Add host to cloudstack platform. 3. Pick another host (h2) to migrate its VMs to the h1. 4. Remove h2 from cloudstack. 5. Move h2 to the new location. 6. Repeat steps 1-5 until we move all hosts. 7. Move management server and databases to the new location (This will cause a small downtime. But it will not affect VMs) 8. Migrate storage to the new location. Kind regards, Sina ‐‐‐ Original Message ‐‐‐ On Monday, October 18th, 2021 at 10:02, Дикевич Евгений Александрович wrote: > Hi all! > > Has anyone migrated between regions? We have old CS installation and we want > to migrate to new with new hosts and storages. How we can do that? Can we > migrate without downtime? In documentation I don't find any information:( > > Does new CS (4.15.x) support this functionality? We want to migrate from CS > 4.14.1 + XCP-NG to CS 4.15.2 + XCP-NG. > > Best regards, Evgeniy. > > Внимание! > > Это электронное письмо и все прикрепленные к нему файлы являются > конфиденциальными и предназначены исключительно для использования лицом > (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом > (лицами), которому (которым) предназначено это письмо, не копируйте и не > разглашайте его содержимое и удалите это сообщение и все вложения из Вашей > почтовой системы. Любое несанкционированное использование, распространение, > раскрытие, печать или копирование этого электронного письма и прикрепленных к > нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, > является незаконным и запрещено. Принимая во внимание, что передача данных > посредством Интернет не является безопасной, мы не несем никакой > ответственности за любой потенциальный ущерб, причиненный в результате ошибок > при передаче данных или этим сообщением и прикрепленными к нему файлами. > > Attention! > > This email and all attachments to it are confidential and are intended solely > for use by the person (or persons) referred to (mentioned) as the intended > recipient (recipients). If you are not the intended recipient of this email, > do not copy or disclose its contents and delete the message and any > attachments to it from your e-mail system. Any unauthorized use, > dissemination, disclosure, printing or copying of this e-mail and files > attached to it, except by the intended recipient, is illegal and is > prohibited. Taking into account that data transmission via Internet is not > secure, we assume no responsibility for any potential damage caused by data > transmission errors or this message and the files attached to it. signature.asc Description: OpenPGP digital signature
RE: [!!Mass Mail]Re: Migration between regions
Hi! We want to change CS-1 with their public network (PN-1) and management servers/vms to another CS-2 with another public network (PN-2) -Original Message- From: Sina Kashipazha [mailto:s.kashipa...@protonmail.com.INVALID] Sent: Wednesday, October 20, 2021 11:48 AM To: users@cloudstack.apache.org Subject: [!!Mass Mail]Re: Migration between regions Hey Evgeniy, Do you want to migrate between two physical locations or upgrade your system to a newer version? We usually do the physical migration in the following order: 1. Set up a new host in the new location (Let's call it h1). 2. Add host to cloudstack platform. 3. Pick another host (h2) to migrate its VMs to the h1. 4. Remove h2 from cloudstack. 5. Move h2 to the new location. 6. Repeat steps 1-5 until we move all hosts. 7. Move management server and databases to the new location (This will cause a small downtime. But it will not affect VMs) 8. Migrate storage to the new location. Kind regards, Sina ‐‐‐ Original Message ‐‐‐ On Monday, October 18th, 2021 at 10:02, Дикевич Евгений Александрович wrote: > Hi all! > > Has anyone migrated between regions? We have old CS installation and > we want to migrate to new with new hosts and storages. How we can do > that? Can we migrate without downtime? In documentation I don't find > any information:( > > Does new CS (4.15.x) support this functionality? We want to migrate from CS > 4.14.1 + XCP-NG to CS 4.15.2 + XCP-NG. > > Best regards, Evgeniy. > > Внимание! > > Это электронное письмо и все прикрепленные к нему файлы являются > конфиденциальными и предназначены исключительно для использования лицом > (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом > (лицами), которому (которым) предназначено это письмо, не копируйте и не > разглашайте его содержимое и удалите это сообщение и все вложения из Вашей > почтовой системы. Любое несанкционированное использование, распространение, > раскрытие, печать или копирование этого электронного письма и прикрепленных к > нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, > является незаконным и запрещено. Принимая во внимание, что передача данных > посредством Интернет не является безопасной, мы не несем никакой > ответственности за любой потенциальный ущерб, причиненный в результате ошибок > при передаче данных или этим сообщением и прикрепленными к нему файлами. > > Attention! > > This email and all attachments to it are confidential and are intended > solely for use by the person (or persons) referred to (mentioned) as the > intended recipient (recipients). If you are not the intended recipient of > this email, do not copy or disclose its contents and delete the message and > any attachments to it from your e-mail system. Any unauthorized use, > dissemination, disclosure, printing or copying of this e-mail and files > attached to it, except by the intended recipient, is illegal and is > prohibited. Taking into account that data transmission via Internet is not > secure, we assume no responsibility for any potential damage caused by data > transmission errors or this message and the files attached to it.
RE: [!!Mass Mail]Re: Migration between regions
Hi! I'm not sure if this feature supported by cloudstack! ‐‐‐ Original Message ‐‐‐ On Wednesday, October 20th, 2021 at 10:56, Дикевич Евгений Александрович wrote: > Hi! > > We want to change CS-1 with their public network (PN-1) and management > servers/vms to another CS-2 with another public network (PN-2) > > -Original Message- > > From: Sina Kashipazha [mailto:s.kashipa...@protonmail.com.INVALID] > > Sent: Wednesday, October 20, 2021 11:48 AM > > To: users@cloudstack.apache.org > > Subject: [!!Mass Mail]Re: Migration between regions > > Hey Evgeniy, > > Do you want to migrate between two physical locations or upgrade your system > to a newer version? We usually do the physical migration in the following > order: > > 1. Set up a new host in the new location (Let's call it h1). > 2. Add host to cloudstack platform. > 3. Pick another host (h2) to migrate its VMs to the h1. > 4. Remove h2 from cloudstack. > 5. Move h2 to the new location. > 6. Repeat steps 1-5 until we move all hosts. > 7. Move management server and databases to the new location (This will cause > a small downtime. But it will not affect VMs) 8. Migrate storage to the new > location. > > Kind regards, > > Sina > > ‐‐‐ Original Message ‐‐‐ > > On Monday, October 18th, 2021 at 10:02, Дикевич Евгений Александрович > evgeniy.dikev...@becloud.by wrote: > > > Hi all! > > > > Has anyone migrated between regions? We have old CS installation and > > > > we want to migrate to new with new hosts and storages. How we can do > > > > that? Can we migrate without downtime? In documentation I don't find > > > > any information:( > > > > Does new CS (4.15.x) support this functionality? We want to migrate from CS > > 4.14.1 + XCP-NG to CS 4.15.2 + XCP-NG. > > > > Best regards, Evgeniy. > > > > Внимание! > > > > Это электронное письмо и все прикрепленные к нему файлы являются > > конфиденциальными и предназначены исключительно для использования лицом > > (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом > > (лицами), которому (которым) предназначено это письмо, не копируйте и не > > разглашайте его содержимое и удалите это сообщение и все вложения из Вашей > > почтовой системы. Любое несанкционированное использование, распространение, > > раскрытие, печать или копирование этого электронного письма и прикрепленных > > к нему файлов, кроме как лицом (лицами) которому (которым) они > > предназначены, является незаконным и запрещено. Принимая во внимание, что > > передача данных посредством Интернет не является безопасной, мы не несем > > никакой ответственности за любой потенциальный ущерб, причиненный в > > результате ошибок при передаче данных или этим сообщением и прикрепленными > > к нему файлами. > > > > Attention! > > > > This email and all attachments to it are confidential and are intended > > > > solely for use by the person (or persons) referred to (mentioned) as the > > intended recipient (recipients). If you are not the intended recipient of > > this email, do not copy or disclose its contents and delete the message and > > any attachments to it from your e-mail system. Any unauthorized use, > > dissemination, disclosure, printing or copying of this e-mail and files > > attached to it, except by the intended recipient, is illegal and is > > prohibited. Taking into account that data transmission via Internet is not > > secure, we assume no responsibility for any potential damage caused by data > > transmission errors or this message and the files attached to it. signature.asc Description: OpenPGP digital signature
Configure LDAP with the GUI
Hi all, in the ACS Usage Guide there is described how to set up an LDAP configuration using CloudMonkey but is there a way to do this via the GUI? I can add an LDAP Configuration under Configuration > LDAP Configuration by defining the hostname and Port (389). I assume that the further configuration can be done under Domains > Settings, am I right? However, is there also a way to define one of the three authentication approaches (manual-import, autoimport and autosync)? I assume that the manual import is done via the GUI as a button "Add LDAP account". Moreover, this behavior may be a bug: When adding an LDAP configuration under Configuration > LDAP Configuration, in case of removing the configuration afterwards (e.g. when hostname was misspelled), I am getting the following exception: com.cloud.exception.InvalidParameterValueException: Cannot find configuration with hostname Maybe some of you have experienced the same issue in the actual ACS version 4.15.2? Mevludin
RE: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2
Hi! If you find a solution, please share with community :) I have same problem :( -Original Message- From: Florian Noel [mailto:f.n...@webetsolutions.com] Sent: Wednesday, October 20, 2021 11:10 AM To: 'users@cloudstack.apache.org' Subject: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2 Hello, I had the same issue as Benoit with Cloudstack 4.15.1 and XCP-NG 8.2. I have read the link below and follow the recommendations but it's still impossible to scale up a VM. When we deploy a VM, memory-static-min and memory-static-max = memory set on the compute offering. Has anyone had the same issue and how did you solve it ? Thanks for your help. Best regards, Florian On 2021/10/19 14:17:22, nu...@li.nux.ro wrote: > Hello,> > > Give this a read, see if helps.> > > https://users.cloudstack.apache.narkive.com/f1vzARuw/dynamic-scaling-o > f-cpu-and-ram-not-working#post8> > > HTH> > > On 2021-10-19 14:42, benoit lair wrote:> > > Hello,> > > > > > I am trying to scale up a Debian VM from 4Go to 8Go ram> I ran into > > the following error :> > > > > > 2021-10-19 15:33:05,803 DEBUG > > > [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper]> > > (DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception> > > com.cloud.utils.exception.CloudRuntimeException when scaling > > > VM:i-2-83-VM> due to > > com.cloud.utils.exception.CloudRuntimeException: Cannot scale up > > > the> > > vm because of memory constraint violation: 0 <=> > > memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <=> > > memory-dynamic-max(8589934592) <= memory-static-max(4294967296)> > > > > > Any ideas ?> > > > > > Regards, Benoit Lair> > Внимание! Это электронное письмо и все прикрепленные к нему файлы являются конфиденциальными и предназначены исключительно для использования лицом (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом (лицами), которому (которым) предназначено это письмо, не копируйте и не разглашайте его содержимое и удалите это сообщение и все вложения из Вашей почтовой системы. Любое несанкционированное использование, распространение, раскрытие, печать или копирование этого электронного письма и прикрепленных к нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, является незаконным и запрещено. Принимая во внимание, что передача данных посредством Интернет не является безопасной, мы не несем никакой ответственности за любой потенциальный ущерб, причиненный в результате ошибок при передаче данных или этим сообщением и прикрепленными к нему файлами. Attention! This email and all attachments to it are confidential and are intended solely for use by the person (or persons) referred to (mentioned) as the intended recipient (recipients). If you are not the intended recipient of this email, do not copy or disclose its contents and delete the message and any attachments to it from your e-mail system. Any unauthorized use, dissemination, disclosure, printing or copying of this e-mail and files attached to it, except by the intended recipient, is illegal and is prohibited. Taking into account that data transmission via Internet is not secure, we assume no responsibility for any potential damage caused by data transmission errors or this message and the files attached to it.
RE: [!!Mass Mail]Re: Migration between regions
Hi, ACS indeed does not support migrating between regions. If you are using VMWare you can unmanage the VMs from one region and ingest in another. In the case of KVM and XEN you'll need to export the VM and register it as a template in the new region, no way to do without downtime. Regards Alex -Original Message- From: Sina Kashipazha Sent: 20 October 2021 11:06 To: Дикевич Евгений Александрович Cc: users@cloudstack.apache.org Subject: RE: [!!Mass Mail]Re: Migration between regions Hi! I'm not sure if this feature supported by cloudstack! ‐‐‐ Original Message ‐‐‐ On Wednesday, October 20th, 2021 at 10:56, Дикевич Евгений Александрович wrote: > Hi! > > We want to change CS-1 with their public network (PN-1) and management > servers/vms to another CS-2 with another public network (PN-2) > > -Original Message- > > From: Sina Kashipazha [mailto:s.kashipa...@protonmail.com.INVALID] > > Sent: Wednesday, October 20, 2021 11:48 AM > > To: users@cloudstack.apache.org > > Subject: [!!Mass Mail]Re: Migration between regions > > Hey Evgeniy, > > Do you want to migrate between two physical locations or upgrade your system > to a newer version? We usually do the physical migration in the following > order: > > 1. Set up a new host in the new location (Let's call it h1). > 2. Add host to cloudstack platform. > 3. Pick another host (h2) to migrate its VMs to the h1. > 4. Remove h2 from cloudstack. > 5. Move h2 to the new location. > 6. Repeat steps 1-5 until we move all hosts. > 7. Move management server and databases to the new location (This will cause > a small downtime. But it will not affect VMs) 8. Migrate storage to the new > location. > > Kind regards, > > Sina > > ‐‐‐ Original Message ‐‐‐ > > On Monday, October 18th, 2021 at 10:02, Дикевич Евгений Александрович > evgeniy.dikev...@becloud.by wrote: > > > Hi all! > > > > Has anyone migrated between regions? We have old CS installation and > > > > we want to migrate to new with new hosts and storages. How we can do > > > > that? Can we migrate without downtime? In documentation I don't find > > > > any information:( > > > > Does new CS (4.15.x) support this functionality? We want to migrate from CS > > 4.14.1 + XCP-NG to CS 4.15.2 + XCP-NG. > > > > Best regards, Evgeniy. > > > > Внимание! > > > > Это электронное письмо и все прикрепленные к нему файлы являются > > конфиденциальными и предназначены исключительно для использования лицом > > (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом > > (лицами), которому (которым) предназначено это письмо, не копируйте и не > > разглашайте его содержимое и удалите это сообщение и все вложения из Вашей > > почтовой системы. Любое несанкционированное использование, распространение, > > раскрытие, печать или копирование этого электронного письма и прикрепленных > > к нему файлов, кроме как лицом (лицами) которому (которым) они > > предназначены, является незаконным и запрещено. Принимая во внимание, что > > передача данных посредством Интернет не является безопасной, мы не несем > > никакой ответственности за любой потенциальный ущерб, причиненный в > > результате ошибок при передаче данных или этим сообщением и прикрепленными > > к нему файлами. > > > > Attention! > > > > This email and all attachments to it are confidential and are intended > > > > solely for use by the person (or persons) referred to (mentioned) as the > > intended recipient (recipients). If you are not the intended recipient of > > this email, do not copy or disclose its contents and delete the message and > > any attachments to it from your e-mail system. Any unauthorized use, > > dissemination, disclosure, printing or copying of this e-mail and files > > attached to it, except by the intended recipient, is illegal and is > > prohibited. Taking into account that data transmission via Internet is not > > secure, we assume no responsibility for any potential damage caused by data > > transmission errors or this message and the files attached to it. openpgp-digital-signature.asc Description: PGP signature
RE: [!!Mass Mail]Re: Migration between regions
THX a lot for the answer! Then we will backup our VMs by Veeam Agent and restore them on other CS installation:( Another question - MB you have plans to add unmanage feature for other hypervisors - XEN and KVM? -Original Message- From: Alex Mattioli [mailto:alex.matti...@shapeblue.com] Sent: Wednesday, October 20, 2021 2:05 PM To: users@cloudstack.apache.org; Sina Kashipazha ; Дикевич Евгений Александрович Subject: RE: [!!Mass Mail]Re: Migration between regions Hi, ACS indeed does not support migrating between regions. If you are using VMWare you can unmanage the VMs from one region and ingest in another. In the case of KVM and XEN you'll need to export the VM and register it as a template in the new region, no way to do without downtime. Regards Alex -Original Message- From: Sina Kashipazha Sent: 20 October 2021 11:06 To: Дикевич Евгений Александрович Cc: users@cloudstack.apache.org Subject: RE: [!!Mass Mail]Re: Migration between regions Hi! I'm not sure if this feature supported by cloudstack! ‐‐‐ Original Message ‐‐‐ On Wednesday, October 20th, 2021 at 10:56, Дикевич Евгений Александрович wrote: > Hi! > > We want to change CS-1 with their public network (PN-1) and management > servers/vms to another CS-2 with another public network (PN-2) > > -Original Message- > > From: Sina Kashipazha [mailto:s.kashipa...@protonmail.com.INVALID] > > Sent: Wednesday, October 20, 2021 11:48 AM > > To: users@cloudstack.apache.org > > Subject: [!!Mass Mail]Re: Migration between regions > > Hey Evgeniy, > > Do you want to migrate between two physical locations or upgrade your system > to a newer version? We usually do the physical migration in the following > order: > > 1. Set up a new host in the new location (Let's call it h1). > 2. Add host to cloudstack platform. > 3. Pick another host (h2) to migrate its VMs to the h1. > 4. Remove h2 from cloudstack. > 5. Move h2 to the new location. > 6. Repeat steps 1-5 until we move all hosts. > 7. Move management server and databases to the new location (This will cause > a small downtime. But it will not affect VMs) 8. Migrate storage to the new > location. > > Kind regards, > > Sina > > ‐‐‐ Original Message ‐‐‐ > > On Monday, October 18th, 2021 at 10:02, Дикевич Евгений Александрович > evgeniy.dikev...@becloud.by wrote: > > > Hi all! > > > > Has anyone migrated between regions? We have old CS installation and > > > > we want to migrate to new with new hosts and storages. How we can do > > > > that? Can we migrate without downtime? In documentation I don't find > > > > any information:( > > > > Does new CS (4.15.x) support this functionality? We want to migrate from CS > > 4.14.1 + XCP-NG to CS 4.15.2 + XCP-NG. > > > > Best regards, Evgeniy. > > > > Внимание! > > > > Это электронное письмо и все прикрепленные к нему файлы являются > > конфиденциальными и предназначены исключительно для использования лицом > > (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом > > (лицами), которому (которым) предназначено это письмо, не копируйте и не > > разглашайте его содержимое и удалите это сообщение и все вложения из Вашей > > почтовой системы. Любое несанкционированное использование, распространение, > > раскрытие, печать или копирование этого электронного письма и прикрепленных > > к нему файлов, кроме как лицом (лицами) которому (которым) они > > предназначены, является незаконным и запрещено. Принимая во внимание, что > > передача данных посредством Интернет не является безопасной, мы не несем > > никакой ответственности за любой потенциальный ущерб, причиненный в > > результате ошибок при передаче данных или этим сообщением и прикрепленными > > к нему файлами. > > > > Attention! > > > > This email and all attachments to it are confidential and are intended > > > > solely for use by the person (or persons) referred to (mentioned) as the > > intended recipient (recipients). If you are not the intended recipient of > > this email, do not copy or disclose its contents and delete the message and > > any attachments to it from your e-mail system. Any unauthorized use, > > dissemination, disclosure, printing or copying of this e-mail and files > > attached to it, except by the intended recipient, is illegal and is > > prohibited. Taking into account that data transmission via Internet is not > > secure, we assume no responsibility for any potential damage caused by data > > transmission errors or this message and the files attached to it.
Re: All cluster reboot when a Primary storage fails
Thanks to all guys for your feedback. We think that the problem is hard to solve without damage a VM. We were trying with Gluster+NFS Ganesha+PaceMaker+Corosync and when the NFS goes down de IP floats to other node but it takes few seconds, and all VMs goes down and in this scenario the VM be Damaged. And the performance with gluster is not really good. Now we want to test with ACS 4.16 and linstor, have someone any references about this?. Regards Mauro El 20/10/2021 a las 05:44, Piotr Pisz escribió: Hi, I experienced this problem myself, in the KVM, Ceph, NFS-Ganesha environment at full Ceph load, the Ganesha NFS server was able to hang. Servers were able to randomly restart due to lack of NFS access. Which magnified the problem and there was a cascade and restart of the entire environment. We currently have the restart line removed in kvmheartbeat, instead we report the restart attempt via prometheus. Regards, Piotr -Original Message- From: Sina Kashipazha Sent: Wednesday, October 20, 2021 10:35 AM To: users@cloudstack.apache.org Subject: Re: All cluster reboot when a Primary storage fails Hey Daniel, PR #4586 (https://github.com/apache/cloudstack/pull/4586) addressed your issue, as well. I'm currently working on it. Could you share with me how I can reproduce your reboot problem? Kind regards, Sina ‐‐‐ Original Message ‐‐‐ On Saturday, October 16th, 2021 at 05:40, Daniel Augusto Veronezi Salvador wrote: Hi Mauro, On KVM's monitor, when there is an inconsistency on the heartbeat's file or heartbeat timeout is extrapolated several times, by default, the host is restarted. The PR 4586 (https://github.com/apache/cloudstack/pull/4586) already addressed this issue by externalizing a property, which allows the operator to decide if the host must be restarted or not (default is 'true', meaning that the host will be restarted). However, this feature will be available only after release 4.16. Best regards, Daniel Salvador On 15/10/2021 20:43, Mauro Ferraro - G2K Hosting wrote: Hi guys, how are you?. We are having this problems with ACS when a primary storages fails. We have several primary storage with Linux and NFS server serving KVM images. So every hosts have been mounted all the NFS servers because in one Host can be running VMs from different storages. The main problem of this, is when some storage fails because any reason all the cluster gets crazy and start rebooting the hosts to reconnect with this storage and all the VMs on the cluster, (including the VMs that were working good) goes down becuase the conection to one storage fails. If the problem with storage is permanent, the cluster never start again and hosts will reboot indefinitely. When this problem appears, the logs say this: host heartbeat: kvmheartbeat.sh will reboot system because it was unable to write the heartbeat to the storage. Many users, edit the script kvmheartbeat.shto avoid the hosts reboot or restart the agent on the host but i really not be sure that this is the real solution. Can someone help to propose a best solution at this high risk problem?. Regards, Mauro
ACS 4.15.1 Migration between NFS Secondary storage servers interrupted
Hello, I am trying to migrate my first NFS secondary storage to a second NFS one I asked for a migration with a migration policy "complete" The job is working but finishes before migrating all the data I had to relaunch the migration which continues Any ideas ? Regards, Benoit
Re: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2
Hello, Scaling up seems not working with Debian 10 (tested too with Debian 7) Scaling is working on CP-NG 8.2 with Centos 7 and CoreOS although without installing the xen-tools Regards, Benoit Lair Le mer. 20 oct. 2021 à 12:59, Дикевич Евгений Александрович < evgeniy.dikev...@becloud.by> a écrit : > Hi! > > If you find a solution, please share with community :) > I have same problem :( > > > > -Original Message- > From: Florian Noel [mailto:f.n...@webetsolutions.com] > Sent: Wednesday, October 20, 2021 11:10 AM > To: 'users@cloudstack.apache.org' > Subject: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2 > > Hello, > I had the same issue as Benoit with Cloudstack 4.15.1 and XCP-NG 8.2. > I have read the link below and follow the recommendations but it's still > impossible to scale up a VM. > When we deploy a VM, memory-static-min and memory-static-max = memory set > on the compute offering. > Has anyone had the same issue and how did you solve it ? > Thanks for your help. > Best regards, Florian > > On 2021/10/19 14:17:22, nu...@li.nux.ro wrote: > > Hello,> > > > > Give this a read, see if helps.> > > > > https://users.cloudstack.apache.narkive.com/f1vzARuw/dynamic-scaling-o > > f-cpu-and-ram-not-working#post8> > > > > HTH> > > > > On 2021-10-19 14:42, benoit lair wrote:> > > > Hello,> > > > > > > > I am trying to scale up a Debian VM from 4Go to 8Go ram> I ran into > > > the following error :> > > > > > > > 2021-10-19 15:33:05,803 DEBUG > > > > [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper]> > > > (DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception> > > > com.cloud.utils.exception.CloudRuntimeException when scaling > > > > VM:i-2-83-VM> due to > > > com.cloud.utils.exception.CloudRuntimeException: Cannot scale up > > > > the> > > > vm because of memory constraint violation: 0 <=> > > > memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <=> > > > memory-dynamic-max(8589934592) <= memory-static-max(4294967296)> > > > > > > > Any ideas ?> > > > > > > > Regards, Benoit Lair> > > > Внимание! > Это электронное письмо и все прикрепленные к нему файлы являются > конфиденциальными и предназначены исключительно для использования лицом > (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом > (лицами), которому (которым) предназначено это письмо, не копируйте и не > разглашайте его содержимое и удалите это сообщение и все вложения из Вашей > почтовой системы. Любое несанкционированное использование, распространение, > раскрытие, печать или копирование этого электронного письма и прикрепленных > к нему файлов, кроме как лицом (лицами) которому (которым) они > предназначены, является незаконным и запрещено. Принимая во внимание, что > передача данных посредством Интернет не является безопасной, мы не несем > никакой ответственности за любой потенциальный ущерб, причиненный в > результате ошибок при передаче данных или этим сообщением и прикрепленными > к нему файлами. > > Attention! > This email and all attachments to it are confidential and are intended > solely for use by the person (or persons) referred to (mentioned) as the > intended recipient (recipients). If you are not the intended recipient of > this email, do not copy or disclose its contents and delete the message and > any attachments to it from your e-mail system. Any unauthorized use, > dissemination, disclosure, printing or copying of this e-mail and files > attached to it, except by the intended recipient, is illegal and is > prohibited. Taking into account that data transmission via Internet is not > secure, we assume no responsibility for any potential damage caused by data > transmission errors or this message and the files attached to it. >
Re: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2
Hello evgeniy, On which Guest OS did your tried to scale your VM ? Regards, Benoit Lair Le mer. 20 oct. 2021 à 15:27, benoit lair a écrit : > Hello, > > Scaling up seems not working with Debian 10 (tested too with Debian 7) > Scaling is working on CP-NG 8.2 with Centos 7 and CoreOS although without > installing the xen-tools > > Regards, Benoit Lair > > Le mer. 20 oct. 2021 à 12:59, Дикевич Евгений Александрович < > evgeniy.dikev...@becloud.by> a écrit : > >> Hi! >> >> If you find a solution, please share with community :) >> I have same problem :( >> >> >> >> -Original Message- >> From: Florian Noel [mailto:f.n...@webetsolutions.com] >> Sent: Wednesday, October 20, 2021 11:10 AM >> To: 'users@cloudstack.apache.org' >> Subject: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2 >> >> Hello, >> I had the same issue as Benoit with Cloudstack 4.15.1 and XCP-NG 8.2. >> I have read the link below and follow the recommendations but it's still >> impossible to scale up a VM. >> When we deploy a VM, memory-static-min and memory-static-max = memory set >> on the compute offering. >> Has anyone had the same issue and how did you solve it ? >> Thanks for your help. >> Best regards, Florian >> >> On 2021/10/19 14:17:22, nu...@li.nux.ro wrote: >> > Hello,> >> > >> > Give this a read, see if helps.> >> > >> > https://users.cloudstack.apache.narkive.com/f1vzARuw/dynamic-scaling-o >> > f-cpu-and-ram-not-working#post8> >> > >> > HTH> >> > >> > On 2021-10-19 14:42, benoit lair wrote:> >> > > Hello,> >> > > > >> > > I am trying to scale up a Debian VM from 4Go to 8Go ram> I ran into >> > > the following error :> >> > > > >> > > 2021-10-19 15:33:05,803 DEBUG > >> > > [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper]> >> > > (DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception> >> > > com.cloud.utils.exception.CloudRuntimeException when scaling > >> > > VM:i-2-83-VM> due to >> > > com.cloud.utils.exception.CloudRuntimeException: Cannot scale up > >> > > the> >> > > vm because of memory constraint violation: 0 <=> >> > > memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <=> >> > > memory-dynamic-max(8589934592) <= memory-static-max(4294967296)> >> > > > >> > > Any ideas ?> >> > > > >> > > Regards, Benoit Lair> >> > >> Внимание! >> Это электронное письмо и все прикрепленные к нему файлы являются >> конфиденциальными и предназначены исключительно для использования лицом >> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом >> (лицами), которому (которым) предназначено это письмо, не копируйте и не >> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей >> почтовой системы. Любое несанкционированное использование, распространение, >> раскрытие, печать или копирование этого электронного письма и прикрепленных >> к нему файлов, кроме как лицом (лицами) которому (которым) они >> предназначены, является незаконным и запрещено. Принимая во внимание, что >> передача данных посредством Интернет не является безопасной, мы не несем >> никакой ответственности за любой потенциальный ущерб, причиненный в >> результате ошибок при передаче данных или этим сообщением и прикрепленными >> к нему файлами. >> >> Attention! >> This email and all attachments to it are confidential and are intended >> solely for use by the person (or persons) referred to (mentioned) as the >> intended recipient (recipients). If you are not the intended recipient of >> this email, do not copy or disclose its contents and delete the message and >> any attachments to it from your e-mail system. Any unauthorized use, >> dissemination, disclosure, printing or copying of this e-mail and files >> attached to it, except by the intended recipient, is illegal and is >> prohibited. Taking into account that data transmission via Internet is not >> secure, we assume no responsibility for any potential damage caused by data >> transmission errors or this message and the files attached to it. >> >
RE: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2
Ubuntu 20.04, CentOS 7/8, Oracle Linux 7/8 -Original Message- From: benoit lair [mailto:kurushi4...@gmail.com] Sent: Wednesday, October 20, 2021 4:29 PM To: users@cloudstack.apache.org Subject: Re: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2 Hello evgeniy, On which Guest OS did your tried to scale your VM ? Regards, Benoit Lair Le mer. 20 oct. 2021 à 15:27, benoit lair a écrit : > Hello, > > Scaling up seems not working with Debian 10 (tested too with Debian 7) > Scaling is working on CP-NG 8.2 with Centos 7 and CoreOS although > without installing the xen-tools > > Regards, Benoit Lair > > Le mer. 20 oct. 2021 à 12:59, Дикевич Евгений Александрович < > evgeniy.dikev...@becloud.by> a écrit : > >> Hi! >> >> If you find a solution, please share with community :) I have same >> problem :( >> >> >> >> -Original Message- >> From: Florian Noel [mailto:f.n...@webetsolutions.com] >> Sent: Wednesday, October 20, 2021 11:10 AM >> To: 'users@cloudstack.apache.org' >> Subject: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2 >> >> Hello, >> I had the same issue as Benoit with Cloudstack 4.15.1 and XCP-NG 8.2. >> I have read the link below and follow the recommendations but it's >> still impossible to scale up a VM. >> When we deploy a VM, memory-static-min and memory-static-max = memory >> set on the compute offering. >> Has anyone had the same issue and how did you solve it ? >> Thanks for your help. >> Best regards, Florian >> >> On 2021/10/19 14:17:22, nu...@li.nux.ro wrote: >> > Hello,> >> > >> > Give this a read, see if helps.> >> > >> > https://users.cloudstack.apache.narkive.com/f1vzARuw/dynamic-scalin >> > g-o >> > f-cpu-and-ram-not-working#post8> >> > >> > HTH> >> > >> > On 2021-10-19 14:42, benoit lair wrote:> >> > > Hello,> >> > > > >> > > I am trying to scale up a Debian VM from 4Go to 8Go ram> I ran >> > > into the following error :> >> > > > >> > > 2021-10-19 15:33:05,803 DEBUG > >> > > [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper]> >> > > (DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception> >> > > com.cloud.utils.exception.CloudRuntimeException when scaling > >> > > VM:i-2-83-VM> due to >> > > com.cloud.utils.exception.CloudRuntimeException: Cannot scale up >> > > > >> > > the> >> > > vm because of memory constraint violation: 0 <=> >> > > memory-static-min(4294967296) <= memory-dynamic-min(8589934592) >> > > <=> >> > > memory-dynamic-max(8589934592) <= memory-static-max(4294967296)> >> > > > >> > > Any ideas ?> >> > > > >> > > Regards, Benoit Lair> >> > >> Внимание! >> Это электронное письмо и все прикрепленные к нему файлы являются >> конфиденциальными и предназначены исключительно для использования >> лицом (лицами), которому (которым) оно предназначено. Если Вы не >> являетесь лицом (лицами), которому (которым) предназначено это >> письмо, не копируйте и не разглашайте его содержимое и удалите это >> сообщение и все вложения из Вашей почтовой системы. Любое >> несанкционированное использование, распространение, раскрытие, печать >> или копирование этого электронного письма и прикрепленных к нему >> файлов, кроме как лицом (лицами) которому (которым) они >> предназначены, является незаконным и запрещено. Принимая во внимание, >> что передача данных посредством Интернет не является безопасной, мы >> не несем никакой ответственности за любой потенциальный ущерб, >> причиненный в результате ошибок при передаче данных или этим сообщением и >> прикрепленными к нему файлами. >> >> Attention! >> This email and all attachments to it are confidential and are >> intended solely for use by the person (or persons) referred to >> (mentioned) as the intended recipient (recipients). If you are not >> the intended recipient of this email, do not copy or disclose its >> contents and delete the message and any attachments to it from your >> e-mail system. Any unauthorized use, dissemination, disclosure, >> printing or copying of this e-mail and files attached to it, except >> by the intended recipient, is illegal and is prohibited. Taking into >> account that data transmission via Internet is not secure, we assume >> no responsibility for any potential damage caused by data transmission >> errors or this message and the files attached to it. >> > Внимание! Это электронное письмо и все прикрепленные к нему файлы являются конфиденциальными и предназначены исключительно для использования лицом (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом (лицами), которому (которым) предназначено это письмо, не копируйте и не разглашайте его содержимое и удалите это сообщение и все вложения из Вашей почтовой системы. Любое несанкционированное использование, распространение, раскрытие, печать или копирование этого электронного письма и прикрепленных к нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, является незаконным и запрещено. Принимая во внимание, что передача данных посредством Интернет не является безопасной, мы не несем никакой ответстве
Re: ACS 4.15.1 / XCP-NG 8.2
Thanks Nux, We had already configured the parameter for enabling scaling vm However, it seems this works with Centos 7 and CoreOS but not with Debian 10 and Debian 7 Regards, Benoit Le mar. 19 oct. 2021 à 16:17, a écrit : > Hello, > > Give this a read, see if helps. > > > https://users.cloudstack.apache.narkive.com/f1vzARuw/dynamic-scaling-of-cpu-and-ram-not-working#post8 > > HTH > > On 2021-10-19 14:42, benoit lair wrote: > > Hello, > > > > I am trying to scale up a Debian VM from 4Go to 8Go ram > > I ran into the following error : > > > > 2021-10-19 15:33:05,803 DEBUG > > [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper] > > (DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception > > com.cloud.utils.exception.CloudRuntimeException when scaling > > VM:i-2-83-VM > > due to com.cloud.utils.exception.CloudRuntimeException: Cannot scale up > > the > > vm because of memory constraint violation: 0 <= > > memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <= > > memory-dynamic-max(8589934592) <= memory-static-max(4294967296) > > > > Any ideas ? > > > > Regards, Benoit Lair >
New Terraform artifacts published for testing
Hi All, We have published the new artifacts to the Terraform registry https://registry.terraform.io/providers/cloudstack/cloudstack/latest. These are created only for testing purposes with tag v0.4.0-pre. May I ask the terraform users to help in testing it and report if you find any issues here at on https://github.com/apache/cloudstack-terraform-provider/issues? We have already fixed some issues and done some testing. If everything goes well we can create RC1 in the next week or so. Regards, Harikrishna
Network Selection in ACS
Hello We have implemented ACS to sell public cloud. Need guidance on which network we should implement while creating the instance. Assuming LB and Firewall features we can provide to the users only when we have the isolated network but when creating the isolated network one public IP address is getting assigned to source-nat and separate IP is assigned to the VM. In this case we have to waste 1 IP address for each network. So tomorrow let suppose we have 1000 users and each will have their own individual isolated network, in this case 1000 IP's will be wasted. Can someone please guide here what process we should follow so IP's can be saved while creating the networks. Also, considering our requirement if there is any other approach then please let me know. Thanks in Advance. Regards Saurabh
Re: Network Selection in ACS
Hi Saurabh, If you use kvm, the best option for you is, advanced zone with security groups. -Wei On Wed, 20 Oct 2021 at 16:24, Saurabh Rapatwar wrote: > Hello > > We have implemented ACS to sell public cloud. Need guidance on which > network we should implement while creating the instance. > > Assuming LB and Firewall features we can provide to the users only when we > have the isolated network but when creating the isolated network one public > IP address is getting assigned to source-nat and separate IP is assigned to > the VM. In this case we have to waste 1 IP address for each network. So > tomorrow let suppose we have 1000 users and each will have their own > individual isolated network, in this case 1000 IP's will be wasted. > > Can someone please guide here what process we should follow so IP's can be > saved while creating the networks. > > Also, considering our requirement if there is any other approach then > please let me know. > > Thanks in Advance. > > Regards > Saurabh >
Re: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2
Have you the CS parameter enable.dynamic.scale.vm set to true ? Is your compute offering got the dynamic checkbox selected ? Have you the XS tools installed in your vm ? This works for Centos7 and Coreos not for Debian at the moment Regards, Benoit Le mer. 20 oct. 2021 à 12:59, Дикевич Евгений Александрович < evgeniy.dikev...@becloud.by> a écrit : > Hi! > > If you find a solution, please share with community :) > I have same problem :( > > > > -Original Message- > From: Florian Noel [mailto:f.n...@webetsolutions.com] > Sent: Wednesday, October 20, 2021 11:10 AM > To: 'users@cloudstack.apache.org' > Subject: [!!Mass Mail]Re: ACS 4.15.1 / XCP-NG 8.2 > > Hello, > I had the same issue as Benoit with Cloudstack 4.15.1 and XCP-NG 8.2. > I have read the link below and follow the recommendations but it's still > impossible to scale up a VM. > When we deploy a VM, memory-static-min and memory-static-max = memory set > on the compute offering. > Has anyone had the same issue and how did you solve it ? > Thanks for your help. > Best regards, Florian > > On 2021/10/19 14:17:22, nu...@li.nux.ro wrote: > > Hello,> > > > > Give this a read, see if helps.> > > > > https://users.cloudstack.apache.narkive.com/f1vzARuw/dynamic-scaling-o > > f-cpu-and-ram-not-working#post8> > > > > HTH> > > > > On 2021-10-19 14:42, benoit lair wrote:> > > > Hello,> > > > > > > > I am trying to scale up a Debian VM from 4Go to 8Go ram> I ran into > > > the following error :> > > > > > > > 2021-10-19 15:33:05,803 DEBUG > > > > [c.c.h.x.r.w.x.CitrixScaleVmCommandWrapper]> > > > (DirectAgent-156:ctx-62880cee) (logid:e5db9099) Catch exception> > > > com.cloud.utils.exception.CloudRuntimeException when scaling > > > > VM:i-2-83-VM> due to > > > com.cloud.utils.exception.CloudRuntimeException: Cannot scale up > > > > the> > > > vm because of memory constraint violation: 0 <=> > > > memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <=> > > > memory-dynamic-max(8589934592) <= memory-static-max(4294967296)> > > > > > > > Any ideas ?> > > > > > > > Regards, Benoit Lair> > > > Внимание! > Это электронное письмо и все прикрепленные к нему файлы являются > конфиденциальными и предназначены исключительно для использования лицом > (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом > (лицами), которому (которым) предназначено это письмо, не копируйте и не > разглашайте его содержимое и удалите это сообщение и все вложения из Вашей > почтовой системы. Любое несанкционированное использование, распространение, > раскрытие, печать или копирование этого электронного письма и прикрепленных > к нему файлов, кроме как лицом (лицами) которому (которым) они > предназначены, является незаконным и запрещено. Принимая во внимание, что > передача данных посредством Интернет не является безопасной, мы не несем > никакой ответственности за любой потенциальный ущерб, причиненный в > результате ошибок при передаче данных или этим сообщением и прикрепленными > к нему файлами. > > Attention! > This email and all attachments to it are confidential and are intended > solely for use by the person (or persons) referred to (mentioned) as the > intended recipient (recipients). If you are not the intended recipient of > this email, do not copy or disclose its contents and delete the message and > any attachments to it from your e-mail system. Any unauthorized use, > dissemination, disclosure, printing or copying of this e-mail and files > attached to it, except by the intended recipient, is illegal and is > prohibited. Taking into account that data transmission via Internet is not > secure, we assume no responsibility for any potential damage caused by data > transmission errors or this message and the files attached to it. >
Re: Network Selection in ACS
Hi Wei We are using Xenserver, please suggest what can be done in this case. Thanks Saurabh On Wed, Oct 20, 2021 at 8:07 PM Wei ZHOU wrote: > Hi Saurabh, > > If you use kvm, the best option for you is, advanced zone with security > groups. > > -Wei > > On Wed, 20 Oct 2021 at 16:24, Saurabh Rapatwar > wrote: > > > Hello > > > > We have implemented ACS to sell public cloud. Need guidance on which > > network we should implement while creating the instance. > > > > Assuming LB and Firewall features we can provide to the users only when > we > > have the isolated network but when creating the isolated network one > public > > IP address is getting assigned to source-nat and separate IP is assigned > to > > the VM. In this case we have to waste 1 IP address for each network. So > > tomorrow let suppose we have 1000 users and each will have their own > > individual isolated network, in this case 1000 IP's will be wasted. > > > > Can someone please guide here what process we should follow so IP's can > be > > saved while creating the networks. > > > > Also, considering our requirement if there is any other approach then > > please let me know. > > > > Thanks in Advance. > > > > Regards > > Saurabh > > >
How to integrate HDFS to CloudStack
How to use HDFS as Primary storage? NFS has not fault-tolerant feature. I want to use HDFS for Primary Storage in CS to garantee fault-tolerant. Its possible?
Re: All cluster reboot when a Primary storage fails
really an interesting challange... I am not sure if you will actually get to a point where an VM will survive this "undamaged". My experiences with other technologies are normally the same as yours. At least something like an "fsck" is needed to get things back running - still with the problem that you often have some kind of "undefined" data. So the workflow i was used to was something like: - get the effected volume - check filesystem - try to run the old vm / create a new one - try to see if data can be safed - revert to the last backup / snapshot (valid known working state) - revert the backed up data (and even here to concider if it really is needed depending on the kind of application the data is used for) I can see why you might try a different setup for the storage system. questions would be how fast has an fail-over to work - so that: -the nfs mount will concidered as availeable -nfs client is able to "cache" data that needs to be transmitted to the storage server and write i after the nfs-mount is availeable again imho quiet many obstacles to get to this point though would be nice to kept updated with your findings! Am Mi., 20. Okt. 2021 um 15:09 Uhr schrieb Mauro Ferraro - G2K Hosting < mferr...@g2khosting.com>: > Thanks to all guys for your feedback. > > We think that the problem is hard to solve without damage a VM. We were > trying with Gluster+NFS Ganesha+PaceMaker+Corosync and when the NFS goes > down de IP floats to other node but it takes few seconds, and all VMs > goes down and in this scenario the VM be Damaged. And the performance > with gluster is not really good. > > Now we want to test with ACS 4.16 and linstor, have someone any > references about this?. > > Regards > > Mauro > > > El 20/10/2021 a las 05:44, Piotr Pisz escribió: > > Hi, > > I experienced this problem myself, in the KVM, Ceph, NFS-Ganesha > environment at full Ceph load, the Ganesha NFS server was able to hang. > > Servers were able to randomly restart due to lack of NFS access. > > Which magnified the problem and there was a cascade and restart of the > entire environment. > > We currently have the restart line removed in kvmheartbeat, instead we > report the restart attempt via prometheus. > > > > Regards, > > Piotr > > > > > > -Original Message- > > From: Sina Kashipazha > > Sent: Wednesday, October 20, 2021 10:35 AM > > To: users@cloudstack.apache.org > > Subject: Re: All cluster reboot when a Primary storage fails > > > > Hey Daniel, > > > > PR #4586 (https://github.com/apache/cloudstack/pull/4586) addressed > your issue, as well. I'm currently working on it. Could you share with me > how I can reproduce your reboot problem? > > > > Kind regards, > > Sina > > > > ‐‐‐ Original Message ‐‐‐ > > > > On Saturday, October 16th, 2021 at 05:40, Daniel Augusto Veronezi > Salvador wrote: > > > >> Hi Mauro, > >> > >> On KVM's monitor, when there is an inconsistency on the heartbeat's file > >> > >> or heartbeat timeout is extrapolated several times, by default, the host > >> > >> is restarted. > >> > >> The PR 4586 (https://github.com/apache/cloudstack/pull/4586) already > >> > >> addressed this issue by externalizing a property, which allows the > >> > >> operator to decide if the host must be restarted or not (default is > >> > >> 'true', meaning that the host will be restarted). However, this feature > >> > >> will be available only after release 4.16. > >> > >> Best regards, > >> > >> Daniel Salvador > >> > >> On 15/10/2021 20:43, Mauro Ferraro - G2K Hosting wrote: > >> > >>> Hi guys, how are you?. > >>> > >>> We are having this problems with ACS when a primary storages fails. > >>> > >>> We have several primary storage with Linux and NFS server serving KVM > >>> > >>> images. So every hosts have been mounted all the NFS servers because > >>> > >>> in one Host can be running VMs from different storages. The main > >>> > >>> problem of this, is when some storage fails because any reason all the > >>> > >>> cluster gets crazy and start rebooting the hosts to reconnect with > >>> > >>> this storage and all the VMs on the cluster, (including the VMs that > >>> > >>> were working good) goes down becuase the conection to one storage > fails. > >>> > >>> If the problem with storage is permanent, the cluster never start > >>> > >>> again and hosts will reboot indefinitely. > >>> > >>> When this problem appears, the logs say this: > >>> > >>> host heartbeat: kvmheartbeat.sh will reboot system because it was > >>> > >>> unable to write the heartbeat to the storage. > >>> > >>> Many users, edit the script kvmheartbeat.shto avoid the hosts reboot > >>> > >>> or restart the agent on the host but i really not be sure that this is > >>> > >>> the real solution. > >>> > >>> Can someone help to propose a best solution at this high risk problem?. > >>> > >>> Regards, > >>> > >>> Mauro >
Re: How to integrate HDFS to CloudStack
IS HDFS still a thing? :) I thought those things were horrible and slow. Anyway, you can in theory use it via a "shared mount point" type of primary storage. I hope you are on KVM or XCP-ng. Why not look at more modern stuff such as CEPH or at least Glusterfs? Regards On 2021-10-20 16:24, Ivson Borges wrote: How to use HDFS as Primary storage? NFS has not fault-tolerant feature. I want to use HDFS for Primary Storage in CS to garantee fault-tolerant. Its possible?
Default firewall and egress rule
Hi, I need help in setting up default networking for new users that will create an instance. I wanted it to have a default firewall rule and default egress rule so they don’t need to set it up on initial creation of instance. How can I do this? Thanks.
Re: How to integrate HDFS to CloudStack
Looks like a joke. HDFS is not an FS you WANT or CAN use for VM filesystems. Its architecture is completely different from what POSIX-compliant OS wants to keep QCOW2 images (or even RAW images). If you want fault-tolerant FS, use Ceph or Gluster or even NFS over DRBD. NFS is a stateless protocol, failover is just fine with VRRP or another shared IP option, but writeback options on the storage host can influence of course, Ceph or Gluster is a way to go. On Wed, Oct 20, 2021 at 10:53 PM wrote: > IS HDFS still a thing? :) > I thought those things were horrible and slow. > > Anyway, you can in theory use it via a "shared mount point" type of > primary storage. I hope you are on KVM or XCP-ng. > > Why not look at more modern stuff such as CEPH or at least Glusterfs? > > Regards > > On 2021-10-20 16:24, Ivson Borges wrote: > > How to use HDFS as Primary storage? > > > > NFS has not fault-tolerant feature. I want to use HDFS for Primary > > Storage in CS to garantee fault-tolerant. Its possible? >
Re: Default firewall and egress rule
Hi, I assume you use isolated networks in advanced zone. the firewall rule list is empty by default, egress rule can be "allow all" or "deny all" per network(check 'default egress policy' of network offering) Do you expose cloudstack api/ui to users ? It's better to give more details. -Wei On Thu, 21 Oct 2021 at 02:52, SVI wrote: > Hi, > > I need help in setting up default networking for new users that will > create an instance. I wanted it to have a default firewall rule and default > egress rule so they don’t need to set it up on initial creation of > instance. How can I do this? > > Thanks.
