Re: vm console无法访问
你是说vm的ip吗？这个配置过，已经给vm分配了IP，知识console一直连不上 2013/6/24 李森 at1...@163.com 系统设置里设置过ip吗 在 2013-06-24 13:35:06，Felix Feng unixw...@gmail.com 写道： VM 可以正常启动，处于running状态，但是console连接不上。console每次都会去找 xx-xx-xx-xx.realhostip.com ，不知道会不会和这个有关系，这个xxx.realhostip.com也ping不通。大家有什么建议吗？谢谢
cloudstack and apache mod_jk
Is it possible to use apache mod_jk with the cloudstack Web UI ? If yes, does some documentation exist for this ? Regards Philippe. 0xDFC3F3D3.asc Description: application/pgp-keys
RE: There are private IP addresses allocated for this pod
On 22.06.2013 15:15, Nux! wrote: On 22.06.2013 11:56, Nux! wrote: On 22.06.2013 11:36, Pranav Saxena wrote: Did you try deleting the physical network ? If not , try that . There is no network left (other than the one for the basic zone, which I need obviously). There's just the pod. Where is this private range in DB? I cold try to delete it from there and see if I can get rid of the pod. Tried to delete the pod from the DB directly, but I'm getting this: SQL query: DELETE FROM `cloud`.`host_pod_ref` WHERE `host_pod_ref`.`id` =2 MySQL said: Documentation #1451 - Cannot delete or update a parent row: a foreign key constraint fails (`cloud`.`cluster`, CONSTRAINT `fk_cluster__pod_id` FOREIGN KEY (`pod_id`) REFERENCES `host_pod_ref` (`id`)) CC-ing in dev@, maybe they can advise on how to remove a Pod from the DB directly. Anyone? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Identifying a VM's ROOT disk offering via the database
Hey, Does anyone know where in the database you can find out what Disk Offering a VM's ROOT disk is based on? To follow on from that, if you made a template from a new VM (via ISO image) that, for example, used MyDiskOfferingA, would further instances of that template also use the same Disk Offering (as you cannot change the ROOT disk offering from a template instantiation)? The templates assign the same disk size, I'm just not sure how it knows if it's a specific Disk Offering or not. Thanks, Andy.
RE: Identifying a VM's ROOT disk offering via the database
Andy, If you are deploying a VM from an ISO, the DATA DISK you select becomes the ROOT DISK for that VM and if you are deploying a VM from a template, then the size of template becomes the size of ROOT DISK and you can select additional DISK as DATA DISK from disk offering for the VM. --Sanjay -Original Message- From: Andy Coates [mailto:andy.coa...@gmail.com] Sent: Monday, June 24, 2013 6:33 PM To: users@cloudstack.apache.org Subject: Identifying a VM's ROOT disk offering via the database Hey, Does anyone know where in the database you can find out what Disk Offering a VM's ROOT disk is based on? To follow on from that, if you made a template from a new VM (via ISO image) that, for example, used MyDiskOfferingA, would further instances of that template also use the same Disk Offering (as you cannot change the ROOT disk offering from a template instantiation)? The templates assign the same disk size, I'm just not sure how it knows if it's a specific Disk Offering or not. Thanks, Andy.
Re: Identifying a VM's ROOT disk offering via the database
Hi Sanjay, That may be the case, but how do you identify what Disk Offering those ROOT disks are based on? After you create a VM you can identify its Service Offering, but not its Disk Offering - and that's what I'm trying to establish here. Some of our Disk Offerings use SATA disks, some use SAS, or even Fiber Channel. When a VM is created from an ISO you can choose the Disk Offering, but where is that information stored afterwards? Likewise if I made a template of that new VM's disk, would it continue to use the same Disk Offering the original VM was made on, and where can I identify that? Andy. On 24 June 2013 21:58, Sanjay Tripathi sanjay.tripa...@citrix.com wrote: Andy, If you are deploying a VM from an ISO, the DATA DISK you select becomes the ROOT DISK for that VM and if you are deploying a VM from a template, then the size of template becomes the size of ROOT DISK and you can select additional DISK as DATA DISK from disk offering for the VM. --Sanjay -Original Message- From: Andy Coates [mailto:andy.coa...@gmail.com] Sent: Monday, June 24, 2013 6:33 PM To: users@cloudstack.apache.org Subject: Identifying a VM's ROOT disk offering via the database Hey, Does anyone know where in the database you can find out what Disk Offering a VM's ROOT disk is based on? To follow on from that, if you made a template from a new VM (via ISO image) that, for example, used MyDiskOfferingA, would further instances of that template also use the same Disk Offering (as you cannot change the ROOT disk offering from a template instantiation)? The templates assign the same disk size, I'm just not sure how it knows if it's a specific Disk Offering or not. Thanks, Andy.
Re: Adding a Cluster
Does anyone know another non-OSS build for CS 4.0.0? The link provided in http://jenkins.cloudstack.org/view/4.0/job/build-4.0-nonoss-rhel63/ is not working, it does not download when clicked. Thanks! * Jóse * El 23/06/2013 3:33, Ryan Lei escribió: If you want to stay in 4.0.0, you SHOULD instead use the non-OSS build here: http://jenkins.cloudstack.org/view/4.0/job/build-4.0-nonoss-rhel63/ But there's no such a build for 4.1 in jenkins yet. Maybe the official repository does work. Haven't tried. http://cloudstack.apt-get.eu/**rhel/4.1/http://cloudstack.apt-get.eu/rhel/4.1/ If not, then you'll have to build the non-OSS RPMs yourself. --- Yu-Heng (Ryan) Lei, Associate Reasearcher Chunghwa Telecom Laboratories / Cloud Computing Laboratory ryan...@cht.com.twhttps://email.cht.com.tw/owa/redir.aspx?C=-wE1FEC3G0SWYpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.URL=mailto%3aryanlei%40cht.com.tw or ryanlei750...@gmail.com On Sun, Jun 23, 2013 at 4:15 PM, Nux! n...@li.nux.ro wrote: On 23.06.2013 02:04, José Egas López wrote: Thanks Nils, Nonoss rpm's are in http://cloudstack.apt-get.eu/**rhel/4.1/http://cloudstack.apt-get.eu/rhel/4.1/repository? I used that and seems to support VMware. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro FARMAENLACE ha procesado su mensaje y esta limpio No imprima este mail a menos que sea necesario FARMAENLACE ha procesado su mensaje y esta limpio No imprima este mail a menos que sea necesario
Re: There are private IP addresses allocated for this pod
Nux, Have a look at the file create_schema.sql from the git repository. As far as I know there are no cascading deletes supported and as you started deleting you'll have to follow the relations yourself. a mysql workbench is going to be your best friend right now. 'host_pod_ref' is not ref'd from just the host and pod tables. Daan On Mon, Jun 24, 2013 at 11:35 AM, Nux! n...@li.nux.ro wrote: On 22.06.2013 15:15, Nux! wrote: On 22.06.2013 11:56, Nux! wrote: On 22.06.2013 11:36, Pranav Saxena wrote: Did you try deleting the physical network ? If not , try that . There is no network left (other than the one for the basic zone, which I need obviously). There's just the pod. Where is this private range in DB? I cold try to delete it from there and see if I can get rid of the pod. Tried to delete the pod from the DB directly, but I'm getting this: SQL query: DELETE FROM `cloud`.`host_pod_ref` WHERE `host_pod_ref`.`id` =2 MySQL said: Documentation #1451 - Cannot delete or update a parent row: a foreign key constraint fails (`cloud`.`cluster`, CONSTRAINT `fk_cluster__pod_id` FOREIGN KEY (`pod_id`) REFERENCES `host_pod_ref` (`id`)) CC-ing in dev@, maybe they can advise on how to remove a Pod from the DB directly. Anyone? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
RE: Identifying a VM's ROOT disk offering via the database
Check out the 'volumes' table in the database. There is a 'disk_offering_id' column. Based on this id check the 'disk_offering' table to see the details. Is this what you are looking for? -Original Message- From: Andy Coates [mailto:andy.coa...@gmail.com] Sent: Monday, June 24, 2013 7:43 PM To: users@cloudstack.apache.org Subject: Re: Identifying a VM's ROOT disk offering via the database Hi Sanjay, That may be the case, but how do you identify what Disk Offering those ROOT disks are based on? After you create a VM you can identify its Service Offering, but not its Disk Offering - and that's what I'm trying to establish here. Some of our Disk Offerings use SATA disks, some use SAS, or even Fiber Channel. When a VM is created from an ISO you can choose the Disk Offering, but where is that information stored afterwards? Likewise if I made a template of that new VM's disk, would it continue to use the same Disk Offering the original VM was made on, and where can I identify that? Andy. On 24 June 2013 21:58, Sanjay Tripathi sanjay.tripa...@citrix.com wrote: Andy, If you are deploying a VM from an ISO, the DATA DISK you select becomes the ROOT DISK for that VM and if you are deploying a VM from a template, then the size of template becomes the size of ROOT DISK and you can select additional DISK as DATA DISK from disk offering for the VM. --Sanjay -Original Message- From: Andy Coates [mailto:andy.coa...@gmail.com] Sent: Monday, June 24, 2013 6:33 PM To: users@cloudstack.apache.org Subject: Identifying a VM's ROOT disk offering via the database Hey, Does anyone know where in the database you can find out what Disk Offering a VM's ROOT disk is based on? To follow on from that, if you made a template from a new VM (via ISO image) that, for example, used MyDiskOfferingA, would further instances of that template also use the same Disk Offering (as you cannot change the ROOT disk offering from a template instantiation)? The templates assign the same disk size, I'm just not sure how it knows if it's a specific Disk Offering or not. Thanks, Andy.
Re: Adding a Cluster
The download works for me, though. Try again or use this direct link: http://jenkins.cloudstack.org/view/4.0/job/build-4.0-nonoss-rhel63/lastSuccessfulBuild/artifact/CloudStack-non-OSS-142.tar.bz2 If it still fails, use my Dropbox sharing link. I'll keep it up for 3 days. https://www.dropbox.com/s/fhwdphvji5dzgku/CloudStack-non-OSS-142.tar.bz2 --- Yu-Heng (Ryan) Lei, Associate Reasearcher Chunghwa Telecom Laboratories / Cloud Computing Laboratory ryan...@cht.com.twhttps://email.cht.com.tw/owa/redir.aspx?C=-wE1FEC3G0SWYpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.URL=mailto%3aryanlei%40cht.com.tw or ryanlei750...@gmail.com On Tue, Jun 25, 2013 at 6:19 AM, José Egas López josee...@farmaenlace.comwrote: Does anyone know another non-OSS build for CS 4.0.0? The link provided in http://jenkins.cloudstack.org/**view/4.0/job/build-4.0-nonoss-**rhel63/http://jenkins.cloudstack.org/view/4.0/job/build-4.0-nonoss-rhel63/ is not working, it does not download when clicked. Thanks! * Jóse * El 23/06/2013 3:33, Ryan Lei escribió: If you want to stay in 4.0.0, you SHOULD instead use the non-OSS build here: http://jenkins.cloudstack.org/**view/4.0/job/build-4.0-nonoss-**rhel63/http://jenkins.cloudstack.org/view/4.0/job/build-4.0-nonoss-rhel63/ But there's no such a build for 4.1 in jenkins yet. Maybe the official repository does work. Haven't tried. http://cloudstack.apt-get.eu/rhel/4.1/http://cloudstack.apt-get.eu/**rhel/4.1/ http://cloudstack.**apt-get.eu/rhel/4.1/http://cloudstack.apt-get.eu/rhel/4.1/ If not, then you'll have to build the non-OSS RPMs yourself. --**--** --**- Yu-Heng (Ryan) Lei, Associate Reasearcher Chunghwa Telecom Laboratories / Cloud Computing Laboratory ryan...@cht.com.twhttps://**email.cht.com.tw/owa/redir.**aspx?C=-** wE1FEC3G0SWYpVkiWo8SsDdf3ZqO9A**IuAPTzRnFYCUi-z4YljtI_** hyVKkNHfn9F1Bn-vUWJnQ4.URL=**mailto%3aryanlei%40cht.com.twhttps://email.cht.com.tw/owa/redir.aspx?C=-wE1FEC3G0SWYpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.URL=mailto%3aryanlei%40cht.com.tw or ryanlei750...@gmail.com On Sun, Jun 23, 2013 at 4:15 PM, Nux! n...@li.nux.ro wrote: On 23.06.2013 02:04, José Egas López wrote: Thanks Nils, Nonoss rpm's are in http://cloudstack.apt-get.eu/rhel/4.1/http://cloudstack.apt-get.eu/**rhel/4.1/ http://cloudstack.**apt-get.eu/rhel/4.1/http://cloudstack.apt-get.eu/rhel/4.1/ **repository? I used that and seems to support VMware. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ##**## FARMAENLACE ha procesado su mensaje y esta limpio No imprima este mail a menos que sea necesario ##**## FARMAENLACE ha procesado su mensaje y esta limpio No imprima este mail a menos que sea necesario
