Re: Upgrade from 4.11.2 to 4.17
Hi " or we need to make some changes in the database to support 4.17." There is massive change between the 2 versions, yes there several databases changes Best On Tue, 12 Sept 2023 at 13:11, Francisco Arencibia Quesada < arencibia.franci...@gmail.com> wrote: > Good morning guys, > > We have installed a new machine with 4.17 and we are pointing to the > database of the old machine and it is not working, we receive the following > error message: > HTTP ERROR 503 Service Unavailable > URI: /client/ > STATUS: 503 > MESSAGE: Service Unavailable > SERVLET: - > > > Summarizing: > The old machine with cloudstack 4.11.2 is stopped > new machine with 4.17 is up and pointing out to the database from the old > machine with 4.11.2. > > Is this a good approach? Can we make it work,? or we need to make some > changes in the database to support 4.17. > > Kind regards > > > > -- > *Francisco Arencibia Quesada.* > *DevOps Engineer* > -- Alexandre Legrix / +33 632232109 Global Systems & Managed Services Director 4 av Pablo Picasso 92000 Nanterre - France Hybrid Cloud Fabric : bso.cloud / bso.st / kb8s.io -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email. *AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.
Re: Cloudstack DB HA, do you use db.ha.enabled?
Hi Don't waste your time, it's not working, you've to figure it out by yourself, don't count on cloudstack to be as intelligent as expected to handle a MySQL HA setup. We did it without the mysql-ha buggy jar, and we are now able to get a HA manager but with some manual action in case of DR to be played. No other smooth way, for the moment, which is unfortunate Best Alex On Thu, 20 Jul 2023 at 23:46, Nux wrote: > Cheers Simon, > > I'll double check the jar is loaded in my next tests. > > > > On 2023-07-20 22:08, Simon Weller wrote: > > Lucian, > > > > Check to see whether the mysql-ha jar is being loaded. There's a > > separate > > mysql-ha package that needs to be installed. > > > > Is this Ubuntu or rpm? I'm not sure whether the default Ubuntu builds > > include the extra package. I believe the shapeblue build does though. > > > > -Si > > > > > > On Thu, Jul 20, 2023, 3:03 PM Nux wrote: > > > >> Cheers Daniel, > >> > >> Can you share any other db.ha parameters you may have tuned? > >> For me it didn't work out of the box as you described. > >> > >> Thanks > >> > >> On 2023-07-20 14:04, Daniel Salvador wrote: > >> > Hello Nux, > >> > > >> > Normally I set up three nodes with MariaDB and Galera cluster; then, > in > >> > the > >> > "db.properties" file I mark "db.ha.enabled" as true, and I define one > >> > of > >> > the nodes as main and the other as replicas. When the main node goes > >> > down, > >> > one of the replicas takes over, and so on. > >> > > >> > The current properties we have on "db.properties" regarding DB HA are > >> > hard > >> > coded and only address some MySQL properties; which is not the perfect > >> > scenario for MariaDB HA. However, it provides a minimum DB HA setup. > Me > >> > and > >> > other contributors are already working on a flexible solution to > >> > address > >> > other MySQL properties, and MariaDB properties as well. > >> > > >> > Best regards, > >> > Daniel Salvador (gutoveronezi) > >> > > >> > On Thu, Jul 20, 2023 at 7:46 AM Nux wrote: > >> > > >> >> Hello, > >> >> > >> >> As per the subject, how do you make your DB layer HA and do you use > >> >> the > >> >> db.ha.enabled feature/setting in the Cloudstack management server > >> >> db.properties file? > >> >> > >> >> Cheers > >> >> > >> > -- Alexandre Legrix / +33 632232109 Global Systems & Managed Services Director 4 av Pablo Picasso 92000 Nanterre - France Hybrid Cloud Fabric : bso.cloud / bso.st / kb8s.io -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email. *AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.
Re: compute offering hot change
Hello In theory we can upgrade with VIRSH the VM : and in // do we have a process to stick the new offering in the cloudstack DB ? We do not want to have to restart this VM to change the offering I'm pretty sure we can find a proper workaround to do that Kind regards On Thu, 23 Mar 2023 at 11:59, Ruben Bosch wrote: > Hi Luc, > > Hotswapping resources is possible, mind you, this will also require > activation of said resources within your VM. When using a service offering > with dynamic scaling enabled, you won't need to manually reassign resources > to your VM. I would suggest steering clear of unnecessary database changes. > > Met vriendelijke groet / Kind regards, > > Ruben Bosch > CLDIN > > > On 23 Mar 2023, at 11:54, Luc Begault wrote: > > > > Hello everyone, > > > > I'd like to change a vm ressources that is actually stuck on a fixed > compute offering. > > > > As my kvm hypervisor supports that I can hot add more ram and cpu using > virsh and then updating the service_offering_id in the vm_instance table. > > > > Can this work ? > > > > Regards, > > > > Luc Begault. > > > > -- Alexandre Legrix / +33 632232109 Global Systems & Managed Services Director 4 av Pablo Picasso 92000 Nanterre - France Hybrid Cloud Fabric : bso.cloud / bso.st / kb8s.io -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email. *AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.
Re: [BSO] We are hiring Cloudstack and Kubernetes ingeneer
I'm sorry I did a typo The email is in cc of this one to send your resume. Best regards Le jeu. 10 févr. 2022, 10:29, Alexandre LEGRIX a écrit : > Hello. > > We have more and more customers using cloudstack and we are looking to get > more devops able to help us to grow our business. > We are a cloud and hosting provider, we are selling private cloud based on > cloudstack (and/or other technology). > > We are looking for senior engineers and we do have a lot of locations we > can hire in. > This offer could be handled to local offices (we have more than 10 > locations) and/or remotely. > > We do have a S3 competitor solution > We do have a AKS/EKS competitor solution > > There is a lot of opportunity need to be covered here, don't hesitate to > shoot me a resume on : tal...@bso.co > > Kind regards > -- > Alexandre Legrix / +33 632232109 > Global Systems & Managed Services Director > 4 av Pablo Picasso 92000 Nanterre - France > Hybrid Cloud Fabric : bso.cloud / bso.st / kb8s.io > -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email. *AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.
[BSO] We are hiring Cloudstack and Kubernetes ingeneer
Hello. We have more and more customers using cloudstack and we are looking to get more devops able to help us to grow our business. We are a cloud and hosting provider, we are selling private cloud based on cloudstack (and/or other technology). We are looking for senior engineers and we do have a lot of locations we can hire in. This offer could be handled to local offices (we have more than 10 locations) and/or remotely. We do have a S3 competitor solution We do have a AKS/EKS competitor solution There is a lot of opportunity need to be covered here, don't hesitate to shoot me a resume on : tal...@bso.co Kind regards -- Alexandre Legrix / +33 632232109 Global Systems & Managed Services Director 4 av Pablo Picasso 92000 Nanterre - France Hybrid Cloud Fabric : bso.cloud / bso.st / kb8s.io -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email. *AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.
Re: Cold VM migration across datacenters
; > still using CEPH as before > > -- requires ultra-low latency between DC1 and DC2 - and if plane > > crashes on > > DC1 (taking this example, as I've been to some Zurich DCs next to the > > airport...) - you can still start VM on hosts in DC2 in case it was a > > single cluster. In case you had multiple clusters - then it get's more > > complicated (minor DB hacks) etc. > > > > In both cases you still have to sort out Secondary Storage NFS HA > > > > In general, you can't achieve what you want that easy nor you should > > be stretching the possibilities (that I just explained, as I would, > > probably, never use them in production) > > > > I guess I didn't help - but there you go. > > > > Andrija > > > > > > > > On Tue, 20 Jul 2021 at 16:28, Vladimir Dombrovski < > > vladimir.dombrov...@bso.co> wrote: > > > > > Hello, > > > > > > We're trying to draw a multisite architecture where any VM could be > > > relocated to the secondary site whenever the primary site fails > > > (primary/backup for disaster recovery purposes). We don't require > > > live migration, and we are okay with shutting down machines in order > > > to relocate them. > > > > > > We are using Cloudstack 4.15 on Ubuntu Focal. In our current setup, > > > each datacenter has a Cloudstack management node, as well as a few > > > hypervisors running KVM and a Cloudstack agent. We're using Ceph as > > > our primary storage, and NFS as our secondary storage on each site. > > > > > > To ensure metadata resiliency, we've replicated the MySQL database > > > across both sites, much like described following this guide: > > > > > > > > > https://docs.cloudstack.apache.org/projects/cloudstack-installation/ > > > en/4.11/choosing_deployment_architecture.html#multi-site-deployment > > > > > > We tried setting up multiple zones, one for each datacenter, each > > > one having its own primary storage, but we are faced with the issue > > > where we are not able to migrate VMs across zones (only > > > Pod/Cluster/Host level is available via the GUI and the Cloudmonkey > CLI). > > > > > > Are we using the right level of abstraction for our case? If so, how > > > can we migrate a VM (compute + storage) from one zone to another? If > > > not, what is the right level to use that allows us to use two > > > separate primary storage endpoints and ensures that only the primary > > > site gets used for compute resource allocation in normal conditions? > > > > > > Also, we would like to know whether there is some documentation > > > already touching on the subject of best practices when performing > > > these "more advanced" deployments. > > > > > > Kind regards, > > > > > > Vladimir DOMBROVSKI > > > > > > > > > -- > > > > Andrija Panić > > > Disclaimer Notice: > This email has been sent by Oakford Technology Limited, while we have > checked this e-mail and any attachments for viruses, we can not guarantee > that they are virus-free. You must therefore take full responsibility for > virus checking. > This message and any attachments are confidential and should only be read > by those to whom they are addressed. If you are not the intended recipient, > please contact us, delete the message from your computer and destroy any > copies. Any distribution or copying without our prior permission is > prohibited. > Internet communications are not always secure and therefore Oakford > Technology Limited does not accept legal responsibility for this message. > The recipient is responsible for verifying its authenticity before acting > on the contents. Any views or opinions presented are solely those of the > author and do not necessarily represent those of Oakford Technology Limited. > Registered address: Oakford Technology Limited, The Manor House, Potterne, > Wiltshire. SN10 5PN. > Registered in England and Wales No. 5971519 > > -- Alexandre Legrix / +33 632232109 Global Systems & Managed Services Director 4 av Pablo Picasso 92000 Nanterre - France Hybrid Cloud Fabric : bso.cloud / bso.st / kb8s.io -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, for
