RE: Redundant Router
Hi, Redundant Router is supported only in a zone with advanced networking with Vlan isolation. Also SourceNat is mandatory for RVR. Best Regards, Sanjeev N Chief Product Engineer, Accelerite Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com -Original Message- From: Kirk Kosinski [mailto:kirk.kosin...@shapeblue.com] Sent: Tuesday, June 07, 2016 5:05 AM To: users@cloudstack.apache.org Subject: RE: Redundant Router Hi, it looks like RVR requires Source NAT according to the admin guide: Redundant router capability: Available only when Virtual Router is selected as the Source NAT provider. kirk.kosin...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HS @shapeblue -Original Message- From: Semih Tolga DEMİR [mailto:semihtolgade...@gmail.com] Sent: Monday, June 06, 2016 5:56 AM To: users@cloudstack.apache.org Subject: Redundant Router Hi, I use advanced networking and security groups. I want to test Redundant Router in my environment. Redundant Router option only posible when creating new Network Offering and select Source NAT. I do not need Source NAT, so are there anyway to use redundant router in my project except using Source NAT. Thanks, Tolga DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Accelerite, a Persistent Systems business. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent Systems business does not accept any liability for virus infected mails.
RE: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue
Check /etc/cloudstack-releases file inside system vms to know the system template version after system vm upgrades. Check MS log to know the reasons for VR upgrade failure. Best Regards, Sanjeev N Chief Product Engineer, Accelerite Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com -Original Message- From: Cloud List [mailto:cloud-l...@sg.or.id] Sent: Wednesday, June 08, 2016 10:19 AM To: users@cloudstack.apache.org Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue Hi Sam, Thanks for your reply. Connection to MS is OK, since SSVM works fine. Problem seems to be isolated to the VR. I am using KVM hypervisor. Testing the upgrade again now and will update the result. Cheers. -ip- On Wed, Jun 8, 2016 at 12:41 PM, Sam Ceylani wrote: > So check your firewall on your management server, test that > connection. I believe there are some new stuff introduced that changed > how routers and system vms connect to MS. But you said SSVM connects > fine right? What Hypervisor are you using? > Because I believe they changed system vm connections to ssh on xen for > system vms etc. and there was even a port number that I know I put in > to my firewall which wasn’t there before... > > -Original Message- > From: Cloud List [mailto:cloud-l...@sg.or.id] > Sent: Wednesday, June 8, 2016 12:37 AM > To: users@cloudstack.apache.org > Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > > Hi Sam, > > Thanks for your reply. > > My SSVM and CPVM seems to work fine -- although I can't verify if they > are really using the new template or not, but my VR doesn't work even > after I destroy the VR and restart the network with clean-up option. > So the VR is never able to be started up after the upgrade. It kept on > "Starting" state and agent.log file shows it keeps on trying to > connect to the link local IP but never able to connect. > > I tested the upgrade on a staging environment with just 1 VR, I have > reverted back the setup to 4.2 and now re-doing the upgrade again for > the second attempt, will see if it works. My production has around 10+ > networks so I need to ensure this works before I initiate the upgrade > on my production server. > > Thank you. > > > On Wed, Jun 8, 2016 at 12:26 PM, Sam Ceylani > wrote: > > > Same thing happened to me, upgrading from 4.5.2 to 4.8 and I had to > > restart network with clean-up option checked for each network which > > rebuilds the router VM. If your SSVM works And if you can test it > > then I don’t see any problem rebuilding network(router vm) with new > > template which took about 30 minutes for about > > 20 networks in total...may not be an option for large > > installations...how many routers you are running? > > > > -Original Message- > > From: Cloud List [mailto:cloud-l...@sg.or.id] > > Sent: Wednesday, June 8, 2016 12:23 AM > > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > > Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > > > > Dear all, > > > > Could it be the VR is not able to use the new systemVM template > > because we registered the template as Routing = NO? Will it resolve > > the problem if during upgrade, we register the template as Routing = YES? > > > > Based on the upgrade instruction at > > > > http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upg > > ra de-4.2.html , it says that routing option should be "no", is this > > correct? Since the systemVM template will also be used by VR? > > > > Any advice is appreciated. > > > > Looking forward to your reply, thank you. > > > > Cheers. > > > > -ip- > > > > > > On Tue, Jun 7, 2016 at 10:22 AM, Cloud List wrote: > > > > > Hi Kirk, > > > > > > Thanks for your reply. > > > > > > Here's the status of the CPVM and SSVM in the UI: > > > > > > Namev-2-VM > > > IDfc6d23bf-58ac-4641-af9b-506d1dc46df3 > > > StateRunning > > > TypeConsole Proxy VM > > > Zonesc-test-cs42-zone > > > Public IP Address192.168.0.162 > > > Private IP Address192.168.0.160 > > > Link Local IP Address169.254.3.147 > > > Hostsc-test-kvm-03 > > > Gateway192.168.0.1 > > > Created31 May 2016 15:24:20 > > > Active Sessions0 > > > > > > Names-29-VM > > > IDd26f54f8-1c1f-4f3d-9862-fc0405159620 > > > StateRunning > > > TypeSecondary Storage VM > > > Zonesc-test-cs42-zone > > > Public IP Address192.168.0.161 > > > Private IP Address192.168.0.151 > > > Link Local IP Address169.254.1.207 > > > Hostsc-test-kvm-03 > > > Gateway192.168.0.1 > > > Created06 Jun 2016 00:31:04 > > > Active Sessions > > > > > > Both system VMs seem to be on "Running" state but I can't verify > > > what template version they are using, whether they are already on > > > 4.6/4.8 template or still using 4.2 template, are you able to > > > advise how can I tell? The SSVM creation date seem to be after we > > > performed the upgrade but the CPVM created date is befo
Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue
Hi Sam, Thanks for your reply. Connection to MS is OK, since SSVM works fine. Problem seems to be isolated to the VR. I am using KVM hypervisor. Testing the upgrade again now and will update the result. Cheers. -ip- On Wed, Jun 8, 2016 at 12:41 PM, Sam Ceylani wrote: > So check your firewall on your management server, test that connection. I > believe there are some new stuff introduced > that changed how routers and system vms connect to MS. But you said SSVM > connects fine right? What Hypervisor are you using? > Because I believe they changed system vm connections to ssh on xen for > system vms etc. and there was even a port number that I know > I put in to my firewall which wasn’t there before... > > -Original Message- > From: Cloud List [mailto:cloud-l...@sg.or.id] > Sent: Wednesday, June 8, 2016 12:37 AM > To: users@cloudstack.apache.org > Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > > Hi Sam, > > Thanks for your reply. > > My SSVM and CPVM seems to work fine -- although I can't verify if they are > really using the new template or not, but my VR doesn't work even after I > destroy the VR and restart the network with clean-up option. So the VR is > never able to be started up after the upgrade. It kept on "Starting" state > and agent.log file shows it keeps on trying to connect to the link local IP > but never able to connect. > > I tested the upgrade on a staging environment with just 1 VR, I have > reverted back the setup to 4.2 and now re-doing the upgrade again for the > second attempt, will see if it works. My production has around 10+ networks > so I need to ensure this works before I initiate the upgrade on my > production server. > > Thank you. > > > On Wed, Jun 8, 2016 at 12:26 PM, Sam Ceylani > wrote: > > > Same thing happened to me, upgrading from 4.5.2 to 4.8 and I had to > > restart network with clean-up option checked for each network which > > rebuilds the router VM. If your SSVM works And if you can test it then > > I don’t see any problem rebuilding network(router vm) with new > > template which took about 30 minutes for about > > 20 networks in total...may not be an option for large > > installations...how many routers you are running? > > > > -Original Message- > > From: Cloud List [mailto:cloud-l...@sg.or.id] > > Sent: Wednesday, June 8, 2016 12:23 AM > > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > > Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > > > > Dear all, > > > > Could it be the VR is not able to use the new systemVM template > > because we registered the template as Routing = NO? Will it resolve > > the problem if during upgrade, we register the template as Routing = YES? > > > > Based on the upgrade instruction at > > > > http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgra > > de-4.2.html , it says that routing option should be "no", is this > > correct? Since the systemVM template will also be used by VR? > > > > Any advice is appreciated. > > > > Looking forward to your reply, thank you. > > > > Cheers. > > > > -ip- > > > > > > On Tue, Jun 7, 2016 at 10:22 AM, Cloud List wrote: > > > > > Hi Kirk, > > > > > > Thanks for your reply. > > > > > > Here's the status of the CPVM and SSVM in the UI: > > > > > > Namev-2-VM > > > IDfc6d23bf-58ac-4641-af9b-506d1dc46df3 > > > StateRunning > > > TypeConsole Proxy VM > > > Zonesc-test-cs42-zone > > > Public IP Address192.168.0.162 > > > Private IP Address192.168.0.160 > > > Link Local IP Address169.254.3.147 > > > Hostsc-test-kvm-03 > > > Gateway192.168.0.1 > > > Created31 May 2016 15:24:20 > > > Active Sessions0 > > > > > > Names-29-VM > > > IDd26f54f8-1c1f-4f3d-9862-fc0405159620 > > > StateRunning > > > TypeSecondary Storage VM > > > Zonesc-test-cs42-zone > > > Public IP Address192.168.0.161 > > > Private IP Address192.168.0.151 > > > Link Local IP Address169.254.1.207 > > > Hostsc-test-kvm-03 > > > Gateway192.168.0.1 > > > Created06 Jun 2016 00:31:04 > > > Active Sessions > > > > > > Both system VMs seem to be on "Running" state but I can't verify > > > what template version they are using, whether they are already on > > > 4.6/4.8 template or still using 4.2 template, are you able to advise > > > how can I tell? The SSVM creation date seem to be after we performed > > > the upgrade but the CPVM created date is before the upgrade. > > > > > > How to ensure that all systemVMs using the new version template? > > > Shall I destroy the system VMs so new ones will be created, or shall > > > I re-run the /usr/bin/cloudstack-sysvmadm again in full? > > > > > > Looking forward to your reply, thank you. > > > > > > Cheers. > > > > > > -ip- > > > > > > > > > > > > On Tue, Jun 7, 2016 at 7:22 AM, Kirk Kosinski > > > > > > wrote: > > > > > >> Hi, what is the status of the CPVM and SSVM in the UI? Were they > > >> really upgraded successfully? > > >> > >
RE: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue
So check your firewall on your management server, test that connection. I believe there are some new stuff introduced that changed how routers and system vms connect to MS. But you said SSVM connects fine right? What Hypervisor are you using? Because I believe they changed system vm connections to ssh on xen for system vms etc. and there was even a port number that I know I put in to my firewall which wasn’t there before... -Original Message- From: Cloud List [mailto:cloud-l...@sg.or.id] Sent: Wednesday, June 8, 2016 12:37 AM To: users@cloudstack.apache.org Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue Hi Sam, Thanks for your reply. My SSVM and CPVM seems to work fine -- although I can't verify if they are really using the new template or not, but my VR doesn't work even after I destroy the VR and restart the network with clean-up option. So the VR is never able to be started up after the upgrade. It kept on "Starting" state and agent.log file shows it keeps on trying to connect to the link local IP but never able to connect. I tested the upgrade on a staging environment with just 1 VR, I have reverted back the setup to 4.2 and now re-doing the upgrade again for the second attempt, will see if it works. My production has around 10+ networks so I need to ensure this works before I initiate the upgrade on my production server. Thank you. On Wed, Jun 8, 2016 at 12:26 PM, Sam Ceylani wrote: > Same thing happened to me, upgrading from 4.5.2 to 4.8 and I had to > restart network with clean-up option checked for each network which > rebuilds the router VM. If your SSVM works And if you can test it then > I don’t see any problem rebuilding network(router vm) with new > template which took about 30 minutes for about > 20 networks in total...may not be an option for large > installations...how many routers you are running? > > -Original Message- > From: Cloud List [mailto:cloud-l...@sg.or.id] > Sent: Wednesday, June 8, 2016 12:23 AM > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > > Dear all, > > Could it be the VR is not able to use the new systemVM template > because we registered the template as Routing = NO? Will it resolve > the problem if during upgrade, we register the template as Routing = YES? > > Based on the upgrade instruction at > > http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgra > de-4.2.html , it says that routing option should be "no", is this > correct? Since the systemVM template will also be used by VR? > > Any advice is appreciated. > > Looking forward to your reply, thank you. > > Cheers. > > -ip- > > > On Tue, Jun 7, 2016 at 10:22 AM, Cloud List wrote: > > > Hi Kirk, > > > > Thanks for your reply. > > > > Here's the status of the CPVM and SSVM in the UI: > > > > Namev-2-VM > > IDfc6d23bf-58ac-4641-af9b-506d1dc46df3 > > StateRunning > > TypeConsole Proxy VM > > Zonesc-test-cs42-zone > > Public IP Address192.168.0.162 > > Private IP Address192.168.0.160 > > Link Local IP Address169.254.3.147 > > Hostsc-test-kvm-03 > > Gateway192.168.0.1 > > Created31 May 2016 15:24:20 > > Active Sessions0 > > > > Names-29-VM > > IDd26f54f8-1c1f-4f3d-9862-fc0405159620 > > StateRunning > > TypeSecondary Storage VM > > Zonesc-test-cs42-zone > > Public IP Address192.168.0.161 > > Private IP Address192.168.0.151 > > Link Local IP Address169.254.1.207 > > Hostsc-test-kvm-03 > > Gateway192.168.0.1 > > Created06 Jun 2016 00:31:04 > > Active Sessions > > > > Both system VMs seem to be on "Running" state but I can't verify > > what template version they are using, whether they are already on > > 4.6/4.8 template or still using 4.2 template, are you able to advise > > how can I tell? The SSVM creation date seem to be after we performed > > the upgrade but the CPVM created date is before the upgrade. > > > > How to ensure that all systemVMs using the new version template? > > Shall I destroy the system VMs so new ones will be created, or shall > > I re-run the /usr/bin/cloudstack-sysvmadm again in full? > > > > Looking forward to your reply, thank you. > > > > Cheers. > > > > -ip- > > > > > > > > On Tue, Jun 7, 2016 at 7:22 AM, Kirk Kosinski > > > > wrote: > > > >> Hi, what is the status of the CPVM and SSVM in the UI? Were they > >> really upgraded successfully? > >> > >> Also, are there any errors in the management-server.log? > >> > >> kirk.kosin...@shapeblue.com > >> www.shapeblue.com > >> 53 Chandos Place, Covent Garden, London WC2N 4HS @shapeblue > >> > >> > >> > >> -Original Message- > >> From: Cloud List [mailto:cloud-l...@sg.or.id] > >> Sent: Monday, June 06, 2016 9:51 AM > >> To: users@cloudstack.apache.org; d...@cloudstack.apache.org > >> Subject: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > >> > >> Hi, > >> > >> I tried upgrading our C
Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue
Hi Sam, Thanks for your reply. My SSVM and CPVM seems to work fine -- although I can't verify if they are really using the new template or not, but my VR doesn't work even after I destroy the VR and restart the network with clean-up option. So the VR is never able to be started up after the upgrade. It kept on "Starting" state and agent.log file shows it keeps on trying to connect to the link local IP but never able to connect. I tested the upgrade on a staging environment with just 1 VR, I have reverted back the setup to 4.2 and now re-doing the upgrade again for the second attempt, will see if it works. My production has around 10+ networks so I need to ensure this works before I initiate the upgrade on my production server. Thank you. On Wed, Jun 8, 2016 at 12:26 PM, Sam Ceylani wrote: > Same thing happened to me, upgrading from 4.5.2 to 4.8 and I had to > restart network with clean-up option checked for each network which > rebuilds the router VM. If your SSVM works > And if you can test it then I don’t see any problem rebuilding > network(router vm) with new template which took about 30 minutes for about > 20 networks in total...may not be an option > for large installations...how many routers you are running? > > -Original Message- > From: Cloud List [mailto:cloud-l...@sg.or.id] > Sent: Wednesday, June 8, 2016 12:23 AM > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > > Dear all, > > Could it be the VR is not able to use the new systemVM template because we > registered the template as Routing = NO? Will it resolve the problem if > during upgrade, we register the template as Routing = YES? > > Based on the upgrade instruction at > > http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgrade-4.2.html > , it says that routing option should be "no", is this correct? Since the > systemVM template will also be used by VR? > > Any advice is appreciated. > > Looking forward to your reply, thank you. > > Cheers. > > -ip- > > > On Tue, Jun 7, 2016 at 10:22 AM, Cloud List wrote: > > > Hi Kirk, > > > > Thanks for your reply. > > > > Here's the status of the CPVM and SSVM in the UI: > > > > Namev-2-VM > > IDfc6d23bf-58ac-4641-af9b-506d1dc46df3 > > StateRunning > > TypeConsole Proxy VM > > Zonesc-test-cs42-zone > > Public IP Address192.168.0.162 > > Private IP Address192.168.0.160 > > Link Local IP Address169.254.3.147 > > Hostsc-test-kvm-03 > > Gateway192.168.0.1 > > Created31 May 2016 15:24:20 > > Active Sessions0 > > > > Names-29-VM > > IDd26f54f8-1c1f-4f3d-9862-fc0405159620 > > StateRunning > > TypeSecondary Storage VM > > Zonesc-test-cs42-zone > > Public IP Address192.168.0.161 > > Private IP Address192.168.0.151 > > Link Local IP Address169.254.1.207 > > Hostsc-test-kvm-03 > > Gateway192.168.0.1 > > Created06 Jun 2016 00:31:04 > > Active Sessions > > > > Both system VMs seem to be on "Running" state but I can't verify what > > template version they are using, whether they are already on 4.6/4.8 > > template or still using 4.2 template, are you able to advise how can I > > tell? The SSVM creation date seem to be after we performed the upgrade > > but the CPVM created date is before the upgrade. > > > > How to ensure that all systemVMs using the new version template? Shall > > I destroy the system VMs so new ones will be created, or shall I > > re-run the /usr/bin/cloudstack-sysvmadm again in full? > > > > Looking forward to your reply, thank you. > > > > Cheers. > > > > -ip- > > > > > > > > On Tue, Jun 7, 2016 at 7:22 AM, Kirk Kosinski > > > > wrote: > > > >> Hi, what is the status of the CPVM and SSVM in the UI? Were they > >> really upgraded successfully? > >> > >> Also, are there any errors in the management-server.log? > >> > >> kirk.kosin...@shapeblue.com > >> www.shapeblue.com > >> 53 Chandos Place, Covent Garden, London WC2N 4HS @shapeblue > >> > >> > >> > >> -Original Message- > >> From: Cloud List [mailto:cloud-l...@sg.or.id] > >> Sent: Monday, June 06, 2016 9:51 AM > >> To: users@cloudstack.apache.org; d...@cloudstack.apache.org > >> Subject: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue > >> > >> Hi, > >> > >> I tried upgrading our CloudStack 4.2.0 on our test environment to 4.8.0, > >> and I am having issues on VR upgrade. I followed the upgrade > instructions > >> at below URL: > >> > >> > >> > http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgrade-4.2.html > >> > >> On the last step to restart all the system VMs and VRs, it seems that > the > >> cloudstack-sysvmadm script managed to restart the system VMs (SSVM and > >> CPVM) but not the VR. > >> > >> # nohup cloudstack-sysvmadm -d IPaddress -u cloud -p password -a > > >> sysvm.log 2>&1 & > >> > >> Here's the output of the sysvm.log file: > >> > >> > >> nohup: ignoring input > >> /usr/bin/cloudstack-sysvmadm: l
RE: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue
Same thing happened to me, upgrading from 4.5.2 to 4.8 and I had to restart network with clean-up option checked for each network which rebuilds the router VM. If your SSVM works And if you can test it then I don’t see any problem rebuilding network(router vm) with new template which took about 30 minutes for about 20 networks in total...may not be an option for large installations...how many routers you are running? -Original Message- From: Cloud List [mailto:cloud-l...@sg.or.id] Sent: Wednesday, June 8, 2016 12:23 AM To: users@cloudstack.apache.org; d...@cloudstack.apache.org Subject: Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue Dear all, Could it be the VR is not able to use the new systemVM template because we registered the template as Routing = NO? Will it resolve the problem if during upgrade, we register the template as Routing = YES? Based on the upgrade instruction at http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgrade-4.2.html , it says that routing option should be "no", is this correct? Since the systemVM template will also be used by VR? Any advice is appreciated. Looking forward to your reply, thank you. Cheers. -ip- On Tue, Jun 7, 2016 at 10:22 AM, Cloud List wrote: > Hi Kirk, > > Thanks for your reply. > > Here's the status of the CPVM and SSVM in the UI: > > Namev-2-VM > IDfc6d23bf-58ac-4641-af9b-506d1dc46df3 > StateRunning > TypeConsole Proxy VM > Zonesc-test-cs42-zone > Public IP Address192.168.0.162 > Private IP Address192.168.0.160 > Link Local IP Address169.254.3.147 > Hostsc-test-kvm-03 > Gateway192.168.0.1 > Created31 May 2016 15:24:20 > Active Sessions0 > > Names-29-VM > IDd26f54f8-1c1f-4f3d-9862-fc0405159620 > StateRunning > TypeSecondary Storage VM > Zonesc-test-cs42-zone > Public IP Address192.168.0.161 > Private IP Address192.168.0.151 > Link Local IP Address169.254.1.207 > Hostsc-test-kvm-03 > Gateway192.168.0.1 > Created06 Jun 2016 00:31:04 > Active Sessions > > Both system VMs seem to be on "Running" state but I can't verify what > template version they are using, whether they are already on 4.6/4.8 > template or still using 4.2 template, are you able to advise how can I > tell? The SSVM creation date seem to be after we performed the upgrade > but the CPVM created date is before the upgrade. > > How to ensure that all systemVMs using the new version template? Shall > I destroy the system VMs so new ones will be created, or shall I > re-run the /usr/bin/cloudstack-sysvmadm again in full? > > Looking forward to your reply, thank you. > > Cheers. > > -ip- > > > > On Tue, Jun 7, 2016 at 7:22 AM, Kirk Kosinski > > wrote: > >> Hi, what is the status of the CPVM and SSVM in the UI? Were they >> really upgraded successfully? >> >> Also, are there any errors in the management-server.log? >> >> kirk.kosin...@shapeblue.com >> www.shapeblue.com >> 53 Chandos Place, Covent Garden, London WC2N 4HS @shapeblue >> >> >> >> -Original Message- >> From: Cloud List [mailto:cloud-l...@sg.or.id] >> Sent: Monday, June 06, 2016 9:51 AM >> To: users@cloudstack.apache.org; d...@cloudstack.apache.org >> Subject: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue >> >> Hi, >> >> I tried upgrading our CloudStack 4.2.0 on our test environment to 4.8.0, >> and I am having issues on VR upgrade. I followed the upgrade instructions >> at below URL: >> >> >> http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgrade-4.2.html >> >> On the last step to restart all the system VMs and VRs, it seems that the >> cloudstack-sysvmadm script managed to restart the system VMs (SSVM and >> CPVM) but not the VR. >> >> # nohup cloudstack-sysvmadm -d IPaddress -u cloud -p password -a > >> sysvm.log 2>&1 & >> >> Here's the output of the sysvm.log file: >> >> >> nohup: ignoring input >> /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No >> such file or directory >> >> Stopping and starting 1 secondary storage vm(s)... >> Done stopping and starting secondary storage vm(s) >> >> Stopping and starting 1 console proxy vm(s)... >> Done stopping and starting console proxy vm(s) . >> >> Stopping and starting 1 running routing vm(s)... >> *ERROR: Failed to restart domainRouter with id 5* >> >> Done restarting router(s). >> >> >> Output of the cloud.log file: >> >> >> [2016.06.05-22.28.40] Stopping and starting 1 secondary storage vm(s)... >> [2016.06.05-22.28.40] INFO: Stopping secondary storage vm with id 3 >> [2016.06.05-22.28.46] INFO: Starting secondary storage vm with id 3 >> [2016.06.05-23.29.00] ERROR: Failed to startSystemVm id=3; jobId is >> 121c5d89-745a-4e8e-9f96-0b348ef42abf >> [2016.06.05-23.29.00] ERROR: Failed to start secondary storage vm with id >> 3 [2016.06.05-23.29.00] ERROR: Failed to start secondary storage vm with id >> 3 [2016.06.05-23.29.00] Done stopping and starting secondary storage vm(s). >>
Re: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue
Dear all, Could it be the VR is not able to use the new systemVM template because we registered the template as Routing = NO? Will it resolve the problem if during upgrade, we register the template as Routing = YES? Based on the upgrade instruction at http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgrade-4.2.html , it says that routing option should be "no", is this correct? Since the systemVM template will also be used by VR? Any advice is appreciated. Looking forward to your reply, thank you. Cheers. -ip- On Tue, Jun 7, 2016 at 10:22 AM, Cloud List wrote: > Hi Kirk, > > Thanks for your reply. > > Here's the status of the CPVM and SSVM in the UI: > > Namev-2-VM > IDfc6d23bf-58ac-4641-af9b-506d1dc46df3 > StateRunning > TypeConsole Proxy VM > Zonesc-test-cs42-zone > Public IP Address192.168.0.162 > Private IP Address192.168.0.160 > Link Local IP Address169.254.3.147 > Hostsc-test-kvm-03 > Gateway192.168.0.1 > Created31 May 2016 15:24:20 > Active Sessions0 > > Names-29-VM > IDd26f54f8-1c1f-4f3d-9862-fc0405159620 > StateRunning > TypeSecondary Storage VM > Zonesc-test-cs42-zone > Public IP Address192.168.0.161 > Private IP Address192.168.0.151 > Link Local IP Address169.254.1.207 > Hostsc-test-kvm-03 > Gateway192.168.0.1 > Created06 Jun 2016 00:31:04 > Active Sessions > > Both system VMs seem to be on "Running" state but I can't verify what > template version they are using, whether they are already on 4.6/4.8 > template or still using 4.2 template, are you able to advise how can I > tell? The SSVM creation date seem to be after we performed the upgrade but > the CPVM created date is before the upgrade. > > How to ensure that all systemVMs using the new version template? Shall I > destroy the system VMs so new ones will be created, or shall I re-run the > /usr/bin/cloudstack-sysvmadm again in full? > > Looking forward to your reply, thank you. > > Cheers. > > -ip- > > > > On Tue, Jun 7, 2016 at 7:22 AM, Kirk Kosinski > wrote: > >> Hi, what is the status of the CPVM and SSVM in the UI? Were they really >> upgraded successfully? >> >> Also, are there any errors in the management-server.log? >> >> kirk.kosin...@shapeblue.com >> www.shapeblue.com >> 53 Chandos Place, Covent Garden, London WC2N 4HS >> @shapeblue >> >> >> >> -Original Message- >> From: Cloud List [mailto:cloud-l...@sg.or.id] >> Sent: Monday, June 06, 2016 9:51 AM >> To: users@cloudstack.apache.org; d...@cloudstack.apache.org >> Subject: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue >> >> Hi, >> >> I tried upgrading our CloudStack 4.2.0 on our test environment to 4.8.0, >> and I am having issues on VR upgrade. I followed the upgrade instructions >> at below URL: >> >> >> http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgrade-4.2.html >> >> On the last step to restart all the system VMs and VRs, it seems that the >> cloudstack-sysvmadm script managed to restart the system VMs (SSVM and >> CPVM) but not the VR. >> >> # nohup cloudstack-sysvmadm -d IPaddress -u cloud -p password -a > >> sysvm.log 2>&1 & >> >> Here's the output of the sysvm.log file: >> >> >> nohup: ignoring input >> /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No >> such file or directory >> >> Stopping and starting 1 secondary storage vm(s)... >> Done stopping and starting secondary storage vm(s) >> >> Stopping and starting 1 console proxy vm(s)... >> Done stopping and starting console proxy vm(s) . >> >> Stopping and starting 1 running routing vm(s)... >> *ERROR: Failed to restart domainRouter with id 5* >> >> Done restarting router(s). >> >> >> Output of the cloud.log file: >> >> >> [2016.06.05-22.28.40] Stopping and starting 1 secondary storage vm(s)... >> [2016.06.05-22.28.40] INFO: Stopping secondary storage vm with id 3 >> [2016.06.05-22.28.46] INFO: Starting secondary storage vm with id 3 >> [2016.06.05-23.29.00] ERROR: Failed to startSystemVm id=3; jobId is >> 121c5d89-745a-4e8e-9f96-0b348ef42abf >> [2016.06.05-23.29.00] ERROR: Failed to start secondary storage vm with id >> 3 [2016.06.05-23.29.00] ERROR: Failed to start secondary storage vm with id >> 3 [2016.06.05-23.29.00] Done stopping and starting secondary storage vm(s). >> [2016.06.05-23.29.00] Stopping and starting 1 console proxy vm(s)... >> [2016.06.05-23.29.00] INFO: Stopping console proxy with id 2 >> [2016.06.05-23.29.06] INFO: Starting console proxy vm with id 2 >> [2016.06.05-23.30.49] Done stopping and starting console proxy vm(s) . >> [2016.06.05-23.30.49] Stopping and starting 1 running routing vm(s)... >> [2016.06.05-23.30.49] INFO: Restarting router with id 5 >> [2016.06.06-00.30.59] ERROR: Failed to restart domainRouter with id 5; >> jobId 4a3f681e-c4a6-4856-9d42-0d3b79bffdae >> [2016.06.06-00.31.04] Done restarting router(s). >> >> >> Initially I noted that the VR remains in 4.2.0 version (instead of the >> expect
Re: Allow users to resize root volume of a template-based instance?
On 06/07/2016 18:26, Dag Sonstebo wrote: > Which version of CloudStack are you on Andy? The bug seems to have been fixed > in 4.2 (https://issues.apache.org/jira/browse/CLOUDSTACK-2337 [1]), but we > recently came across it again in 4.6 - with a fix appearing in 4.6.2 > (https://issues.apache.org/jira/browse/CLOUDSTACK-9101 [2]). > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue Hi Dag, I'm running CS 4.8. It's a little different than those bugs; I reviewed those with hope. It seemed like back then the issue was that nobody had the UI element to resize the disk, whereas now the issue (at least as I see it) is that only the Admin account gets the UI element. Can anybody else confirm whether or not they see the UI element to resize the disk as regular user or domain admin in CS 4.8? Thanks, Andy --- - ANDY DILLS - XECUNET, LLC 5744-R Industry Lane Frederick MD 21704 www.xecu.net [3] P: 301-682-9972 P: 1-877-XECUNET F: 240-215-0351 Twitter [4] Facebook [5] - Links: -- [1] https://issues.apache.org/jira/browse/CLOUDSTACK-2337 [2] https://issues.apache.org/jira/browse/CLOUDSTACK-9101 [3] http://www.xecu.net/ [4] https://twitter.com/Xecunet [5] http://www.facebook.com/xecunet
Re: Allow users to resize root volume of a template-based instance?
Which version of CloudStack are you on Andy? The bug seems to have been fixed in 4.2 (https://issues.apache.org/jira/browse/CLOUDSTACK-2337), but we recently came across it again in 4.6 - with a fix appearing in 4.6.2 (https://issues.apache.org/jira/browse/CLOUDSTACK-9101). Regards, Dag Sonstebo Cloud Architect ShapeBlue On 07/06/2016, 20:07, "Andy Dills" wrote: > > >We're using 4.8, with Xen as the hypervisor. > >We're finding that only the Admin account can adjust the size of a root >volume. Domain Admins and User accounts aren't given the option to >resize the volume. I have the same storage tag on all of the disk >offerings, and on the primary storage. Resize shows up and works great >when I'm logged in as admin, but none of the users get the icon. > >Is there a way to enable this? The documentation seems to suggest it >should be visible to both users and admins, and that as long as multiple >disk offerings share a common storage tag, they should be presented as >options. > >I notice in the storage properties for the volume, the "Disk Offering" >is blank, even though I clearly picked an offering. > >Any suggestions? > >Thanks, >Andy >-- > >- >ANDY DILLS - XECUNET, LLC > >5744-R Industry Lane >Frederick MD 21704 >www.xecu.net [1] >P: 301-682-9972 >P: 1-877-XECUNET >F: 240-215-0351 > >Twitter [2] > >Facebook [3] >- > >Links: >-- >[1] http://www.xecu.net/ >[2] https://twitter.com/Xecunet >[3] http://www.facebook.com/xecunet dag.sonst...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
Allow users to resize root volume of a template-based instance?
We're using 4.8, with Xen as the hypervisor. We're finding that only the Admin account can adjust the size of a root volume. Domain Admins and User accounts aren't given the option to resize the volume. I have the same storage tag on all of the disk offerings, and on the primary storage. Resize shows up and works great when I'm logged in as admin, but none of the users get the icon. Is there a way to enable this? The documentation seems to suggest it should be visible to both users and admins, and that as long as multiple disk offerings share a common storage tag, they should be presented as options. I notice in the storage properties for the volume, the "Disk Offering" is blank, even though I clearly picked an offering. Any suggestions? Thanks, Andy -- - ANDY DILLS - XECUNET, LLC 5744-R Industry Lane Frederick MD 21704 www.xecu.net [1] P: 301-682-9972 P: 1-877-XECUNET F: 240-215-0351 Twitter [2] Facebook [3] - Links: -- [1] http://www.xecu.net/ [2] https://twitter.com/Xecunet [3] http://www.facebook.com/xecunet
RE: FW: Password reset, not work after adding new Guest IP Class
Hi Marcus, I don't have any support becuase is did this installation on dedicated servers, they don't provide support for cloudstack. Regards, Cristian -Original Message- From: Marc-Andre Jutras [mailto:mar...@marcuspocus.com] Sent: Tuesday, June 7, 2016 4:36 PM To: users@cloudstack.apache.org Subject: Re: FW: Password reset, not work after adding new Guest IP Class yes I did... So something is wrong on your setup, Still trying to figure it out what is wrong... Do you have any support from you service provider ? if so, try to check with them if there's anything they can do... Marcus On 2016-06-05 1:28 PM, Cristian Ciobanu wrote: > Hi Marcus, > > Did you recevied my last reply to this email ? > >Thank you. > > Regards, > Cristian > > -Original Message- > From: Marc-Andre Jutras [mailto:mar...@marcuspocus.com] > Sent: Thursday, June 2, 2016 12:06 AM > To: users@cloudstack.apache.org > Subject: Re: FW: Password reset, not work after adding new Guest IP > Class > > Thanks for the logs Cristian, > > You just forgot to include the : /var/log/cloud.log available on the > VR... ;) > > Also, quite Interesting to see that your VM can communicate with ACS > correctly... > > Can you try to reproduce it again but this time with the default VM ( > ie: CentOS 5.6... ) Just want to see if it's going to behave the same > way with the default template... if it work, that will means something > is wrong with your VM template or something is wrong in your > cloud-init configuration > > > Marcus > > > > On 2016-06-01 4:43 PM, Cristian Ciobanu wrote: >> Hi Marcus, >> >> I just reproduced this error, by removing an old VM (with and IP >> from previous class ) also exported the last part from log : >> >>VR LOG : hxxp://pastebin.com/TH8CcEL6 >> >> >>Very interesting is what I saw on VM : >> >>VM LOG : hxxp://pastebin.com/dn6Du4ci ( in order to grab this >> part of the log I was able to login with default VM password which >> was set before when I created this template ) >> >> Thank you ! >> >> Regards, >> Cristian >> >> -Original Message- >> From: Marc-Andre Jutras [mailto:mar...@marcuspocus.com] >> Sent: Wednesday, June 1, 2016 8:00 PM >> To: users@cloudstack.apache.org >> Subject: Re: FW: Password reset, not work after adding new Guest IP >> Class >> >> when your condition happen, is there any errors in the /var/log/cloud.log of >> your VR ? >> >> Marcus >> >> >> On 2016-06-01 12:21 PM, Cristian Ciobanu wrote: >>> Hi Marcus, >>> >>> >>> Ok, please see, i also attached screenshots. >>> >>>1. Yes, i'm using CloudStack 4.5.2 with Vmware 5.5 update3 >>>2. vCenter version : hxxp://imgur.com/tcjY4kS >>>3. Host version : hxxp://imgur.com/ZIDKqWe >>>4. 2X NIC/hypervisor : hxxp://imgur.com/UefelGO >>>5.How many vm per hosts: 5-7 : hxxp://imgur.com/ZIDKqWe >>>6. How many vswitch port ? : 120 (looks like i forgot to change >>> ) : hxxp://imgur.com/m3CPdSb >>>7. Networking setup : hxxp://imgur.com/UefelGO >>>8. I use only vswitch: hxxp://imgur.com/LJTx2gD >>>9. VR version : 4.5.2 >>>10. Can you try to delete / expunge the VR and let the system >>> re-create it ? : like i said before i do reboot or delete, when a new vm >>> are deployd from another class ( from X to Y to Z, etc and viceversa ) >>>11. On your VM : can you check which cloud-init version you're >>> running ? ( could it be related ? : i'm not sure if this can be related, i >>> have about 7 OS Templates, Windows, Linux and i have the same issue for all. >>> For Windows i use : cloudbaseinit 0.9 >>> For Linux i use >>> hxxps://github.com/HeinleinSupport/acs-template-scripts i also use >>> hxxp://cloudstack-administration.readthedocs.io/en/4.8/templates.htm >>> l >>> # >>> linux-os-installation for centos 6.7 >>> >>> Thank you !! >>> >>> Regards, >>> Cristian >>> >>> >>> >>> >>> >>> -Original Message- >>> From: Marc-Andre Jutras [mailto:mar...@marcuspocus.com] >>> Sent: Wednesday, June 1, 2016 5:07 PM >>> To: users@cloudstack.apache.org >>> Subject: Re: FW: Password reset, not work after adding new Guest IP >>> Class >>> >>> Hey ! >>> >>> Ok, At this point, I will need a bit more info then... so far, looks like >>> the public core router can see correctly both public ip range and route >>> them correctly... >>> >>> You mention that you're using Cloustack 4.5.2 wuth Vmware 5.5 >>> - vmware : which latest fix / patch level installed ? >>> - approx : how many vm per hosts are you running >>> - how many NIC per hypervsor ? ( bonding ? ) >>> - how many vswitch port ? ( >>> http://docs.cloudstack.apache.org/projects/cloudstack-installation/e >>> n / 4.6/hypervisor/vsphere.html#increasing-ports >>> ) >>> - can you send me a s
Re: FW: Password reset, not work after adding new Guest IP Class
yes I did... So something is wrong on your setup, Still trying to figure it out what is wrong... Do you have any support from you service provider ? if so, try to check with them if there's anything they can do... Marcus On 2016-06-05 1:28 PM, Cristian Ciobanu wrote: Hi Marcus, Did you recevied my last reply to this email ? Thank you. Regards, Cristian -Original Message- From: Marc-Andre Jutras [mailto:mar...@marcuspocus.com] Sent: Thursday, June 2, 2016 12:06 AM To: users@cloudstack.apache.org Subject: Re: FW: Password reset, not work after adding new Guest IP Class Thanks for the logs Cristian, You just forgot to include the : /var/log/cloud.log available on the VR... ;) Also, quite Interesting to see that your VM can communicate with ACS correctly... Can you try to reproduce it again but this time with the default VM ( ie: CentOS 5.6... ) Just want to see if it's going to behave the same way with the default template... if it work, that will means something is wrong with your VM template or something is wrong in your cloud-init configuration Marcus On 2016-06-01 4:43 PM, Cristian Ciobanu wrote: Hi Marcus, I just reproduced this error, by removing an old VM (with and IP from previous class ) also exported the last part from log : VR LOG : hxxp://pastebin.com/TH8CcEL6 Very interesting is what I saw on VM : VM LOG : hxxp://pastebin.com/dn6Du4ci ( in order to grab this part of the log I was able to login with default VM password which was set before when I created this template ) Thank you ! Regards, Cristian -Original Message- From: Marc-Andre Jutras [mailto:mar...@marcuspocus.com] Sent: Wednesday, June 1, 2016 8:00 PM To: users@cloudstack.apache.org Subject: Re: FW: Password reset, not work after adding new Guest IP Class when your condition happen, is there any errors in the /var/log/cloud.log of your VR ? Marcus On 2016-06-01 12:21 PM, Cristian Ciobanu wrote: Hi Marcus, Ok, please see, i also attached screenshots. 1. Yes, i'm using CloudStack 4.5.2 with Vmware 5.5 update3 2. vCenter version : hxxp://imgur.com/tcjY4kS 3. Host version : hxxp://imgur.com/ZIDKqWe 4. 2X NIC/hypervisor : hxxp://imgur.com/UefelGO 5.How many vm per hosts: 5-7 : hxxp://imgur.com/ZIDKqWe 6. How many vswitch port ? : 120 (looks like i forgot to change ) : hxxp://imgur.com/m3CPdSb 7. Networking setup : hxxp://imgur.com/UefelGO 8. I use only vswitch: hxxp://imgur.com/LJTx2gD 9. VR version : 4.5.2 10. Can you try to delete / expunge the VR and let the system re-create it ? : like i said before i do reboot or delete, when a new vm are deployd from another class ( from X to Y to Z, etc and viceversa ) 11. On your VM : can you check which cloud-init version you're running ? ( could it be related ? : i'm not sure if this can be related, i have about 7 OS Templates, Windows, Linux and i have the same issue for all. For Windows i use : cloudbaseinit 0.9 For Linux i use hxxps://github.com/HeinleinSupport/acs-template-scripts i also use hxxp://cloudstack-administration.readthedocs.io/en/4.8/templates.html # linux-os-installation for centos 6.7 Thank you !! Regards, Cristian -Original Message- From: Marc-Andre Jutras [mailto:mar...@marcuspocus.com] Sent: Wednesday, June 1, 2016 5:07 PM To: users@cloudstack.apache.org Subject: Re: FW: Password reset, not work after adding new Guest IP Class Hey ! Ok, At this point, I will need a bit more info then... so far, looks like the public core router can see correctly both public ip range and route them correctly... You mention that you're using Cloustack 4.5.2 wuth Vmware 5.5 - vmware : which latest fix / patch level installed ? - approx : how many vm per hosts are you running - how many NIC per hypervsor ? ( bonding ? ) - how many vswitch port ? ( http://docs.cloudstack.apache.org/projects/cloudstack-installation/en / 4.6/hypervisor/vsphere.html#increasing-ports ) - can you send me a screenshot of your vsphere client // networking setup ? ( http://docs.cloudstack.apache.org/projects/cloudstack-installation/en / 4.6/hypervisor/vsphere.html#physical-host-networking ) - are you using any dvswitch or only vswitch ? if dvswitch, in ACS / Global settings : vmware.use.dvswitch is enable ? - on cloudstack : global settings / host : this IP is reachable internally ( RFC1918 - 10.x.x.x, 172.16.x.x, 192.168.x.x ) or externally ( public ip ) - - if public IP, any firewall or load balancer that could restraint or limit the access ?? - can you provide a quick networking layout on how you setup your network ? ( example: hxxp://imgur.com/wZdjoqN ) - VR version : log on the VR and do : cat /etc/cloudstack-release ( it shoud report 4.5 )
