Re: Public IP Missing.
Hi Rajsekhar, Try setting public ip address table columns state=Free, removed= and allocated=null. Thanks, Jayapal On 12-May-2015, at 4:06 AM, raja sekhar wrote: > Hi All, > > I have created a shared network in ACS 4.3.1. > When ever i want to remove the network from UI, it is showing error unable > to remove network. There are no vm's under this network. > I tried to remove the network from backend by executing these commands in > DB. > > update networks set state='Destroy',removed=now() where id=315; > update vm_instance set state='Stopped' where id=393; > update vm_instance set removed=now() where id=393; > update domain_router set public_ip_address='NULL' where id=393; > update nics set state='Deallocating' where id=747; > update nics set removed=now() where id=747; > > Now the network is removed from ui, but the public ip is not getting free. > what is the procedure and commands to be executed in order to free the > public ip from backend. > > > Regards, > Rajasekhar.
Re: Public IP Missing.
update user_ip_address set allocated=NULL where id= On Tue, May 12, 2015 at 9:04 AM, ilya wrote: > Have you destroyed router vm for this network? > > I'd instead try to identify what holds up the network instead of deleting > by force. > > > On 5/11/15 3:36 PM, raja sekhar wrote: > >> Hi All, >> >> I have created a shared network in ACS 4.3.1. >> When ever i want to remove the network from UI, it is showing error unable >> to remove network. There are no vm's under this network. >> I tried to remove the network from backend by executing these commands in >> DB. >> >> update networks set state='Destroy',removed=now() where id=315; >> update vm_instance set state='Stopped' where id=393; >> update vm_instance set removed=now() where id=393; >> update domain_router set public_ip_address='NULL' where id=393; >> update nics set state='Deallocating' where id=747; >> update nics set removed=now() where id=747; >> >> Now the network is removed from ui, but the public ip is not getting free. >> what is the procedure and commands to be executed in order to free the >> public ip from backend. >> >> >> Regards, >> Rajasekhar. >> >> >
Re: Public IP Missing.
Have you destroyed router vm for this network? I'd instead try to identify what holds up the network instead of deleting by force. On 5/11/15 3:36 PM, raja sekhar wrote: Hi All, I have created a shared network in ACS 4.3.1. When ever i want to remove the network from UI, it is showing error unable to remove network. There are no vm's under this network. I tried to remove the network from backend by executing these commands in DB. update networks set state='Destroy',removed=now() where id=315; update vm_instance set state='Stopped' where id=393; update vm_instance set removed=now() where id=393; update domain_router set public_ip_address='NULL' where id=393; update nics set state='Deallocating' where id=747; update nics set removed=now() where id=747; Now the network is removed from ui, but the public ip is not getting free. what is the procedure and commands to be executed in order to free the public ip from backend. Regards, Rajasekhar.
Public IP Missing.
Hi All, I have created a shared network in ACS 4.3.1. When ever i want to remove the network from UI, it is showing error unable to remove network. There are no vm's under this network. I tried to remove the network from backend by executing these commands in DB. update networks set state='Destroy',removed=now() where id=315; update vm_instance set state='Stopped' where id=393; update vm_instance set removed=now() where id=393; update domain_router set public_ip_address='NULL' where id=393; update nics set state='Deallocating' where id=747; update nics set removed=now() where id=747; Now the network is removed from ui, but the public ip is not getting free. what is the procedure and commands to be executed in order to free the public ip from backend. Regards, Rajasekhar.
Re: Recover from outage
Hi Ian, From experience I know that as soon as CloudStack talks to a hypervisor, it will get a report of all running VMs and update its database accordingly. Even if you migrate a VM from outside of CloudStack, it will just pick this up. Starting CloudStack should be safe I’d say. Monitor the HA worker table for any scheduled HA work. Then you’ll have an idea of what it will do. You can then always decide to stop it again. Good luck! Regards, Remi > On 11 May 2015, at 20:18 , Vadim Kimlaychuk wrote: > > Hello Ian, > > Cloudstack should get VM state from cloudstack agent > automatically. Check running SSVM and proxy VM that agent status is > "running". It just takes some time. Whether CS will automatically start VM > depends on compute offering. If you have HA enabled than CS will try to start > VM in a case it "thinks" it is stopped by itself. But this is normal > operational flow. If you've had some trouble than it may be harder to fix. I > wouldn't dare to make chages to database directly anyway. Will try to clarify > that everything else works as it suppose to. If you would like to experiment > on DB -- make a backup first. > > Vadim. > > > From: Ian Service > Sent: Monday, May 11, 2015 17:09 > To: users@cloudstack.apache.org > Subject: Recover from outage > > My management server became disconnected from one of the clusters it > manages yesterday evening. I stopped the cloudstack-management process > because in the past this has wreaked havoc on that cluster, restarting > networks, bringing them up on different VLANs, causing unnecessary reboots > on instances, etc. > > The database now shows most of the vm_instances as Stopped, even though > they are still very much running in XenCenter. > > To get things back up and running, what's the recommended procedure to > avoid the unnecessary outages that CloudStack has caused me in the past? > > If I simply start up cloudstack-management will it assess the currently > running machines or try to start them all again because the database says > they're stopped? > > If I update the database to set each machine that's actually running as > Running and update host_id=last_host_id (as it appears to be null'd) would > that make CloudStack just check that they're still running and move on? > > Any assistance/suggestions you can provide would be fantastic. > > Thanks, > > - Ian
Re: Recover from outage
Hello Ian, Cloudstack should get VM state from cloudstack agent automatically. Check running SSVM and proxy VM that agent status is "running". It just takes some time. Whether CS will automatically start VM depends on compute offering. If you have HA enabled than CS will try to start VM in a case it "thinks" it is stopped by itself. But this is normal operational flow. If you've had some trouble than it may be harder to fix. I wouldn't dare to make chages to database directly anyway. Will try to clarify that everything else works as it suppose to. If you would like to experiment on DB -- make a backup first. Vadim. From: Ian Service Sent: Monday, May 11, 2015 17:09 To: users@cloudstack.apache.org Subject: Recover from outage My management server became disconnected from one of the clusters it manages yesterday evening. I stopped the cloudstack-management process because in the past this has wreaked havoc on that cluster, restarting networks, bringing them up on different VLANs, causing unnecessary reboots on instances, etc. The database now shows most of the vm_instances as Stopped, even though they are still very much running in XenCenter. To get things back up and running, what's the recommended procedure to avoid the unnecessary outages that CloudStack has caused me in the past? If I simply start up cloudstack-management will it assess the currently running machines or try to start them all again because the database says they're stopped? If I update the database to set each machine that's actually running as Running and update host_id=last_host_id (as it appears to be null'd) would that make CloudStack just check that they're still running and move on? Any assistance/suggestions you can provide would be fantastic. Thanks, - Ian
Recover from outage
My management server became disconnected from one of the clusters it manages yesterday evening. I stopped the cloudstack-management process because in the past this has wreaked havoc on that cluster, restarting networks, bringing them up on different VLANs, causing unnecessary reboots on instances, etc. The database now shows most of the vm_instances as Stopped, even though they are still very much running in XenCenter. To get things back up and running, what's the recommended procedure to avoid the unnecessary outages that CloudStack has caused me in the past? If I simply start up cloudstack-management will it assess the currently running machines or try to start them all again because the database says they're stopped? If I update the database to set each machine that's actually running as Running and update host_id=last_host_id (as it appears to be null'd) would that make CloudStack just check that they're still running and move on? Any assistance/suggestions you can provide would be fantastic. Thanks, - Ian
[ANNOUNCE] Apache CloudStack 4.5.1
Hi everyone, The Apache CloudStack project is pleased to announce the 4.5.1 release of the CloudStack, the cloud orchestration platform. The 4.5.1 release contains more than 500 bug fixes since the 4.4 release and represents over six months of work from the Apache CloudStack community with new and improved features. # Documentation What's new in CloudStack 4.5: http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.1/about.html The 4.5.1 release notes includes full list of corrected issues as well as upgrade instructions from previous versions of Apache CloudStack. Please see the Release Notes for a full list of corrected issues and upgrade instructions: http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.1/ The official installation, administration and API documentation for each release are available on our Documentation Page: http://docs.cloudstack.apache.org/ # Downloads The official source code for the 4.5.1 release can be downloaded from our Downloads Page: http://cloudstack.apache.org/downloads.html # Availability and Oversight As with all Apache products, Apache CloudStack v4.5.1 is released under the Apache License v2.0, and is overseen by a self-selected team of active contributors to the project. A Project Management Committee (PMC) guides the Project's day-to-day operations, including community development and product releases. For documentation and to learn how to join and contribute to the Apache CloudStack community please visit our website: http://cloudstack.apache.org For additional marketing or communications information, please contact the marketing mailing list: market...@cloudstack.apache.org Join members of the Apache CloudStack community at the CloudStack Collaboration Conference, taking place 8-9 October 2015 in Dublin, Ireland. For more information, visit http://events.linuxfoundation.org/events/cloudstack-collaboration-conference-europe # About Apache CloudStack is open source software designed to deploy and manage large networks of virtual machines, as a highly available, highly scalable Infrastructure as a Service (IaaS) cloud computing platform. CloudStack is used by a number of service providers to offer public cloud services, and by many companies to provide an on-premises (private) cloud offering, or as part of a hybrid cloud solution. CloudStack became an Apache Top-level Project (TLP) in March 2013. Established in 1999, the all-volunteer Foundation oversees more than one hundred and seventy leading Open Source projects, including Apache HTTP Server --the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 400 individual Members and 3,500 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(c)(3) charitable organization, funded by individual donations and corporate sponsors including Budget Direct, Citrix, Cloudera, Comcast, Facebook, Google, Hortonworks, HP, Huawei, IBM, InMotion Hosting, Matt Mullenweg, Microsoft, Pivotal, Produban, WANdisco, and Yahoo. For more information, visit http://www.apache.org/ or follow @TheASF on Twitter. "Apache", "CloudStack", "Apache CloudStack", and "ApacheCon" are trademarks of The Apache Software Foundation. All other brands and trademarks are the property of their respective owners. -- Regards.
Re: Unable to mount Secondary Storage on SSVM
Hi Andrei, Our SSVM is using NFSv4, we can see here http://pastebin.com/HWvtYg8z When we are trying to mount the same path(CS Secondary Storage), It is mounted perfectly with all the other machines (CS Hosts) except with SSVM. and we have scheduled recurring snapshots policy on our cloud-stack and these snapshots are perfectly backed up to secondary storage path which is the one we are trying to mount manually on SSVM. (I have tested and mounted the same secondary storage path on other machines and there in the snapshots folder I can able to see the scheduled snapshots vhd files ). So if the secondary storage path is failing to mount on SSVM how could the snapshot vhd files are moving to same secondary storage location.?? Any suggestions please. Thanks, Anil. On Sun, May 10, 2015 at 2:20 AM, ilya wrote: > Disregard my previous message, i see its already done. > > Try mounting it in the shell of SSVM by hand. If fails, disable iptables > and try again. Also check the routing table to make sure all is proper. > > Like Andrei mentioned you may need it to be NFSv3 compatible as it will > make use of no_root_squash (which must also be enabled on your share). > > Regards > ilya > > > On 5/9/15 1:46 PM, ilya wrote: > >> Make sure that management network/range of IPs that VM and Storage >> Network (if you have one), is whitelisted as NFS access clients on the >> export. >> >> If that fails, try also adding public ip range to see if that helps - as >> a test. >> >> Regards >> ilya >> On 5/8/15 6:50 AM, Andrei Mikhailovsky wrote: >> >>> Srini, >>> >>> you need to make sure the nfs server is configured properly to allow >>> access from SSVM, as you can see, the access is denied. please check that >>> the nfs server supports the same protocol version as ssvm is requesting. >>> Most likely, it's nfs v3. >>> >>> Check logs on the nfs server to verify why it is denying access. >>> >>> Once this is fixed, you should be good to go. >>> >>> Andrei >>> >>> - Original Message - >>> From: "srinivas niddapu" >>> To: "Rohit Yadav" , d...@cloudstack.apache.org >>> Cc: users@cloudstack.apache.org >>> Sent: Friday, 8 May, 2015 2:03:10 PM >>> Subject: RE: Unable to mount Secondary Storage on SSVM >>> >>> Appreciated info Rohit. >>> >>> As we verified our NFS storage there is no permission restrictions (* >>> FULL ACCESS). >>> Validated the same NFS share on the Cloud Stack Hypervisors, already >>> mounted and data visible. >>> >>> We try to mount the NFS volume in the SSVM manually but its throwing >>> error. Unable to mount. >>> "mount.nfs: access denied by server while mounting" >>> >>> While restoring snapshot in the CloudStack UI getting below error. >>> >>> Status >>> Failed to create >>> templatecom.cloud.utils.exception.CloudRuntimeException: GetRootDir for >>> nfs://172.30.36.51/vS02304090GCSP_NAS07 failed due to >>> com.cloud.utils.exception.CloudRuntimeException: Unable to mount >>> 172.30.36.51:/vS02304090GCSP_NAS07 at >>> /mnt/SecStorage/1c7f122c-e72e-3daa-a54a-3693b89d4015 due to mount.nfs: >>> access denied by server while mounting 172.30.36.51:/vS02304090GCSP_NAS07 >>> at >>> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1956) >>> at >>> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copySnapshotToTemplateFromNfsToNfsXenserver(NfsSecondaryStorageResource.java:377) >>> at >>> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copySnapshotToTemplateFromNfsToNfs(NfsSecondaryStorageResource.java:444) >>> at >>> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.createTemplateFromSnapshot(NfsSecondaryStorageResource.java:553) >>> at >>> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:632) >>> at >>> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:236) >>> at >>> com.cloud.storage.resource.PremiumSecondaryStorageResource.defaultAction(PremiumSecondaryStorageResource.java:63) >>> at >>> com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:59) >>> at com.cloud.agent.Agent.processRequest(Agent.java:498) at >>> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:806) at >>> com.cloud.utils.nio.Task.run(Task.java:83) at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> at java.lang.Thread.run(Thread.java:679) >>> >>> Any suggestions. >>> >>> Thanks, >>> Srini. >>> >>> -Original Message- >>> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] >>> Sent: Friday, May 08, 2015 5:57 PM >>> To: d...@cloudstack.apache.org >>> Cc: users@cloudstack.apache.org; srinivas niddapu >>> Subject: Re: Unable to mount Secondary Storage on SSVM >>> >>> >>> On 08-May-2015, at 2:05 pm, anil la
RE: VPC: DefaultIsolatedNetworkOfferingForVpcNetworksNoLB
Hi Sanjeev, You ara right - this is NoLB network. But there is also DefaultIsolatedNetworkOfferingForVpcNetworks wich is also NoLB (or external one). Looks very similar. Don't understand the difference between them. Vadim. -Original Message- From: Sanjeev N [mailto:sanj...@apache.org] Sent: Monday, May 11, 2015 12:04 PM To: users@cloudstack.apache.org Subject: Re: VPC: DefaultIsolatedNetworkOfferingForVpcNetworksNoLB Hi Vadim, With this network offering we can't assign assign any VMs part of this network to LB rules. In VPC we can have only one network with LB service supported. -Sanjeev On Sat, May 9, 2015 at 1:23 AM, Vadim Kimlaychuk wrote: > Hello all, > > >I have created VPC and added such network type (at subj) to it. > The only difference with DefaultIsolatedNetworkOfferingForVpcNetworks? > offering is that it is not listed in VPC networks when I create VM > using wizard. I can only add it using VPC - tier - add VM. And the > address has to be assigned by hand. > >Why is it so complicated? What is the purpose of this netwok type? > > > Thank you, > > > Vadim. >
Re: VPC: DefaultIsolatedNetworkOfferingForVpcNetworksNoLB
Hi Vadim, With this network offering we can't assign assign any VMs part of this network to LB rules. In VPC we can have only one network with LB service supported. -Sanjeev On Sat, May 9, 2015 at 1:23 AM, Vadim Kimlaychuk wrote: > Hello all, > > >I have created VPC and added such network type (at subj) to it. > The only difference with DefaultIsolatedNetworkOfferingForVpcNetworks? > offering is that it is not listed in VPC networks when I create VM using > wizard. I can only add it using VPC - tier - add VM. And the address has > to be assigned by hand. > >Why is it so complicated? What is the purpose of this netwok type? > > > Thank you, > > > Vadim. >
