Iptables Configuration
So I've been having a few issues with my test system which all seem to boil down to iptables not being configured correctly on my XEN host. Problems I've been having are 1. Template's not able to download - *can be fixed by stopping iptables on XEN host 2. System VM's don't deploy and start running - *can be fixed by stopping iptables on XEN host 3. Security groups not worling - *been posting in the user list and it seems like my XEN host does not have the necessary iptable entries for security groups to work properly. With all these iptables issues, is there a iptables guide posted somewhere that outlines the changes needed to make XEN 6.02 + CSP work correctly?
Could not find corresponding resource manager for VMware
All, I have been trying for the last week to build CS 4.1 with the nonoss packages. I have followed the instructions for the nonoss build perfectly, it installs the nonoss jars with 100% success, I then build the rpms, which all build with 100% success. I then install cloudstack using the RPMS, but when I go to add a vcenter cluster I get the following message "Could not find corresponding resource manager for VMware". Googling this message makes me believe that my RPMS were not built with the nonoss options but I know for a fact they are. I have tried the vmware jars downloaded from the "how to build on master branch" wiki, and also from the vmware 4.1 and 5.1 SDK's...all result with the same resource manager errorWhat am I missing?
RE: Could not find corresponding resource manager for VMware
I did not.. I added the jars to cloudstack using the "mvn install -Dnonoss" command then packaged it just using "package.sh" Guessing I was supposed to add the "-p nonoss" to that? Is that documented anywhere? > From: imusa...@webmd.net > To: dev@cloudstack.apache.org > Subject: RE: Could not find corresponding resource manager for VMware > Date: Tue, 3 Sep 2013 02:11:21 + > > Did you use package.sh -p nonoss ? > > > - All mistakes in this message are not mine but Android's. > > > Original message > From: Michael Phillips > Date: 09/02/2013 8:01 PM (GMT-05:00) > To: dev@cloudstack.apache.org > Subject: Could not find corresponding resource manager for VMware > > > All, >I have been trying for the last week to build CS 4.1 with the nonoss > packages. I have followed the instructions for the nonoss build perfectly, it > installs the nonoss jars with 100% success, I then build the rpms, which all > build with 100% success. I then install cloudstack using the RPMS, but when I > go to add a vcenter cluster I get the following message "Could not find > corresponding resource manager for VMware". Googling this message makes me > believe that my RPMS were not built with the nonoss options but I know for a > fact they are. I have tried the vmware jars downloaded from the "how to build > on master branch" wiki, and also from the vmware 4.1 and 5.1 SDK's...all > result with the same resource manager errorWhat am I missing?
RE: Could not find corresponding resource manager for VMware
Let me try that, I will report back my findings. How do I file a report bug if it fixes the issue? > From: imusa...@webmd.net > To: dev@cloudstack.apache.org > Subject: RE: Could not find corresponding resource manager for VMware > Date: Tue, 3 Sep 2013 02:46:35 + > > I think its documented (but I can't recall for certain). You need to use "-p > nonoss" to package nonoss packages. > > Also you don't need to do "mvn install -Dnonoss". Its good to do it initially > to confirm all builds well, but going forward the packaging process will take > care of It. > > Regards > Ilya > > > - All mistakes in this message are not mine but Android's. > > > Original message > From: Michael Phillips > Date: 09/02/2013 10:33 PM (GMT-05:00) > To: dev@cloudstack.apache.org > Subject: RE: Could not find corresponding resource manager for VMware > > > I did not.. > I added the jars to cloudstack using the "mvn install -Dnonoss" command then > packaged it just using "package.sh" > Guessing I was supposed to add the "-p nonoss" to that? Is that documented > anywhere? > > > From: imusa...@webmd.net > > To: dev@cloudstack.apache.org > > Subject: RE: Could not find corresponding resource manager for VMware > > Date: Tue, 3 Sep 2013 02:11:21 + > > > > Did you use package.sh -p nonoss ? > > > > > > - All mistakes in this message are not mine but Android's. > > > > > > Original message > > From: Michael Phillips > > Date: 09/02/2013 8:01 PM (GMT-05:00) > > To: dev@cloudstack.apache.org > > Subject: Could not find corresponding resource manager for VMware > > > > > > All, > >I have been trying for the last week to build CS 4.1 with the nonoss > > packages. I have followed the instructions for the nonoss build perfectly, > > it installs the nonoss jars with 100% success, I then build the rpms, which > > all build with 100% success. I then install cloudstack using the RPMS, but > > when I go to add a vcenter cluster I get the following message "Could not > > find corresponding resource manager for VMware". Googling this message > > makes me believe that my RPMS were not built with the nonoss options but I > > know for a fact they are. I have tried the vmware jars downloaded from the > > "how to build on master branch" wiki, and also from the vmware 4.1 and 5.1 > > SDK's...all result with the same resource manager errorWhat am I > > missing? >
RE: Could not find corresponding resource manager for VMware
So adding the "-p nonoss" to ./package.sh fixed the issue. Do I need to do something to request the documentation update, or will someone from the dev team take care of that? Also does CS 4.1 support vsphere 5.1? I've been doing some reading at it seems like you can use the vim25.jar from the 5.1 SDK kit, but you have to rename it to vim25_51.jar, however I think renaming the jar file to vim25_51 would kill the install-nonoss script because it looks for the file to be named vim25.jar. > From: mphilli7...@hotmail.com > To: dev@cloudstack.apache.org > Subject: RE: Could not find corresponding resource manager for VMware > Date: Mon, 2 Sep 2013 22:32:45 -0500 > > Let me try that, I will report back my findings. > How do I file a report bug if it fixes the issue? > > > From: imusa...@webmd.net > > To: dev@cloudstack.apache.org > > Subject: RE: Could not find corresponding resource manager for VMware > > Date: Tue, 3 Sep 2013 02:46:35 + > > > > I think its documented (but I can't recall for certain). You need to use > > "-p nonoss" to package nonoss packages. > > > > Also you don't need to do "mvn install -Dnonoss". Its good to do it > > initially to confirm all builds well, but going forward the packaging > > process will take care of It. > > > > Regards > > Ilya > > > > > > - All mistakes in this message are not mine but Android's. > > > > > > Original message > > From: Michael Phillips > > Date: 09/02/2013 10:33 PM (GMT-05:00) > > To: dev@cloudstack.apache.org > > Subject: RE: Could not find corresponding resource manager for VMware > > > > > > I did not.. > > I added the jars to cloudstack using the "mvn install -Dnonoss" command > > then packaged it just using "package.sh" > > Guessing I was supposed to add the "-p nonoss" to that? Is that documented > > anywhere? > > > > > From: imusa...@webmd.net > > > To: dev@cloudstack.apache.org > > > Subject: RE: Could not find corresponding resource manager for VMware > > > Date: Tue, 3 Sep 2013 02:11:21 + > > > > > > Did you use package.sh -p nonoss ? > > > > > > > > > - All mistakes in this message are not mine but Android's. > > > > > > > > > Original message > > > From: Michael Phillips > > > Date: 09/02/2013 8:01 PM (GMT-05:00) > > > To: dev@cloudstack.apache.org > > > Subject: Could not find corresponding resource manager for VMware > > > > > > > > > All, > > >I have been trying for the last week to build CS 4.1 with the nonoss > > > packages. I have followed the instructions for the nonoss build > > > perfectly, it installs the nonoss jars with 100% success, I then build > > > the rpms, which all build with 100% success. I then install cloudstack > > > using the RPMS, but when I go to add a vcenter cluster I get the > > > following message "Could not find corresponding resource manager for > > > VMware". Googling this message makes me believe that my RPMS were not > > > built with the nonoss options but I know for a fact they are. I have > > > tried the vmware jars downloaded from the "how to build on master branch" > > > wiki, and also from the vmware 4.1 and 5.1 SDK's...all result with the > > > same resource manager errorWhat am I missing? > > >
RE: Could not find corresponding resource manager for VMware
Sweet, I didn't even know this existed, I will check it out. So once ACS 4.2 comes out, do you still plan on adding onto cloudsand? > From: imusa...@webmd.net > To: dev@cloudstack.apache.org > Subject: RE: Could not find corresponding resource manager for VMware > Date: Tue, 3 Sep 2013 22:19:35 + > > Michael, > > ACS does support vSphere 5.1 as I run it now. > > Customized edition of CloudStack known as CloudSand, has extra VMware support > built in (primary dvswitch support and ACS hostnames - displayed in VC). Its > being ran in production by several companies. CloudSand edition can be > upgraded to official ACS 4.2 when it comes out. > > Check out the code from http://www.github.com/serverchief/cloudsand > > Homepage on www.cloudsand.com > > I will try to release CloudSand edition of ACS as virtual appliance this > week. Since you've squared away build process, you can pull the source code > and build your own rpms. > > NOTE: you need to enable dvswitch support and vm.name support in settings. > > Regards > ilya > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Tuesday, September 03, 2013 1:32 PM > > To: dev@cloudstack.apache.org > > Subject: RE: Could not find corresponding resource manager for VMware > > > > So adding the "-p nonoss" to ./package.sh fixed the issue. Do I need to do > > something to request the documentation update, or will someone from the > > dev team take care of that? > > Also does CS 4.1 support vsphere 5.1? I've been doing some reading at it > > seems like you can use the vim25.jar from the 5.1 SDK kit, but you have to > > rename it to vim25_51.jar, however I think renaming the jar file to vim25_51 > > would kill the install-nonoss script because it looks for the file to be > > named > > vim25.jar. > > > > > From: mphilli7...@hotmail.com > > > To: dev@cloudstack.apache.org > > > Subject: RE: Could not find corresponding resource manager for VMware > > > Date: Mon, 2 Sep 2013 22:32:45 -0500 > > > > > > Let me try that, I will report back my findings. > > > How do I file a report bug if it fixes the issue? > > > > > > > From: imusa...@webmd.net > > > > To: dev@cloudstack.apache.org > > > > Subject: RE: Could not find corresponding resource manager for VMware > > > > Date: Tue, 3 Sep 2013 02:46:35 + > > > > > > > > I think its documented (but I can't recall for certain). You need to > > > > use "-p > > nonoss" to package nonoss packages. > > > > > > > > Also you don't need to do "mvn install -Dnonoss". Its good to do it > > > > initially > > to confirm all builds well, but going forward the packaging process will > > take > > care of It. > > > > > > > > Regards > > > > Ilya > > > > > > > > > > > > - All mistakes in this message are not mine but Android's. > > > > > > > > > > > > Original message > > > > From: Michael Phillips > > > > Date: 09/02/2013 10:33 PM (GMT-05:00) > > > > To: dev@cloudstack.apache.org > > > > Subject: RE: Could not find corresponding resource manager for VMware > > > > > > > > > > > > I did not.. > > > > I added the jars to cloudstack using the "mvn install -Dnonoss" command > > then packaged it just using "package.sh" > > > > Guessing I was supposed to add the "-p nonoss" to that? Is that > > documented anywhere? > > > > > > > > > From: imusa...@webmd.net > > > > > To: dev@cloudstack.apache.org > > > > > Subject: RE: Could not find corresponding resource manager for > > VMware > > > > > Date: Tue, 3 Sep 2013 02:11:21 + > > > > > > > > > > Did you use package.sh -p nonoss ? > > > > > > > > > > > > > > > - All mistakes in this message are not mine but Android's. > > > > > > > > > > > > > > > Original message > > > > > From: Michael Phillips > > > > > Date: 09/02/2013 8:01 PM (GMT-05:00) > > > > > To: dev@cloudstack.apache.org > > > > > Subject: Could not find corresponding resource manager for VMware > > > > > > > > > > > > > > > All, > > > > >I have been trying for the last week to build CS 4.1 with the > > > > > nonoss > > packages. I have followed the instructions for the nonoss build perfectly, > > it > > installs the nonoss jars with 100% success, I then build the rpms, which all > > build with 100% success. I then install cloudstack using the RPMS, but when > > I > > go to add a vcenter cluster I get the following message "Could not find > > corresponding resource manager for VMware". Googling this message > > makes me believe that my RPMS were not built with the nonoss options but I > > know for a fact they are. I have tried the vmware jars downloaded from the > > "how to build on master branch" wiki, and also from the vmware 4.1 and 5.1 > > SDK's...all result with the same resource manager errorWhat am I > > missing? > > > > > > > > > >
RE: Could not find corresponding resource manager for VMware
Ilya,
I was testing out the cloudsand version, and I noticed the following error:
When creating an instance from a template, the instance ends with an error
state "Error Core:530 Unable to start instance 'name' {GUID}, see mgmt server
for details. This error is also logged in the mgmt servers log file. I also
noticed on the hypervisor side {vmware} that the vm gets created without a
disk. The system then tries to boot the vm and of course it errors out. So it
seems the root cause is when the system creates the instance from the template
it is not creating the vmdk disk. I have tried this with multiple templates,
and even the default "centos 5.3" template. If I deploy the template direct
using vCenter it works. Thoughts?
-Michael
> From: imusa...@webmd.net
> To: dev@cloudstack.apache.org
> Subject: RE: Could not find corresponding resource manager for VMware
> Date: Wed, 4 Sep 2013 16:12:21 +
>
> Michael,
>
> Yes, if I see features that would be beneficial "now" rather than later when
> 4.3 comes out. What will happen then is, I take the feature from 4.3 (master)
> and backport it to CloudSand 4.2, test it, and if goes well, I push it to
> github, release rpms and virt appliance. Think of it as hybrid beta release
> of ACS.
>
> Regards
> ilya
>
> > -Original Message-
> > From: Michael Phillips [mailto:mphilli7...@hotmail.com]
> > Sent: Tuesday, September 03, 2013 11:50 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: Could not find corresponding resource manager for VMware
> >
> > Sweet, I didn't even know this existed, I will check it out. So once ACS 4.2
> > comes out, do you still plan on adding onto cloudsand?
> >
> > > From: imusa...@webmd.net
> > > To: dev@cloudstack.apache.org
> > > Subject: RE: Could not find corresponding resource manager for VMware
> > > Date: Tue, 3 Sep 2013 22:19:35 +
> > >
> > > Michael,
> > >
> > > ACS does support vSphere 5.1 as I run it now.
> > >
> > > Customized edition of CloudStack known as CloudSand, has extra VMware
> > support built in (primary dvswitch support and ACS hostnames - displayed in
> > VC). Its being ran in production by several companies. CloudSand edition can
> > be upgraded to official ACS 4.2 when it comes out.
> > >
> > > Check out the code from http://www.github.com/serverchief/cloudsand
> > >
> > > Homepage on www.cloudsand.com
> > >
> > > I will try to release CloudSand edition of ACS as virtual appliance this
> > > week.
> > Since you've squared away build process, you can pull the source code and
> > build your own rpms.
> > >
> > > NOTE: you need to enable dvswitch support and vm.name support in
> > settings.
> > >
> > > Regards
> > > ilya
> > >
> > > > -Original Message-
> > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com]
> > > > Sent: Tuesday, September 03, 2013 1:32 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: RE: Could not find corresponding resource manager for
> > > > VMware
> > > >
> > > > So adding the "-p nonoss" to ./package.sh fixed the issue. Do I need
> > > > to do something to request the documentation update, or will someone
> > > > from the dev team take care of that?
> > > > Also does CS 4.1 support vsphere 5.1? I've been doing some reading
> > > > at it seems like you can use the vim25.jar from the 5.1 SDK kit, but
> > > > you have to rename it to vim25_51.jar, however I think renaming the
> > > > jar file to vim25_51 would kill the install-nonoss script because it
> > > > looks for the file to be named vim25.jar.
> > > >
> > > > > From: mphilli7...@hotmail.com
> > > > > To: dev@cloudstack.apache.org
> > > > > Subject: RE: Could not find corresponding resource manager for
> > > > > VMware
> > > > > Date: Mon, 2 Sep 2013 22:32:45 -0500
> > > > >
> > > > > Let me try that, I will report back my findings.
> > > > > How do I file a report bug if it fixes the issue?
> > > > >
> > > > > > From: imusa...@webmd.net
> > > > > > To: dev@cloudstack.apache.org
> > > > > > Subject: RE: Could not find corresponding resource manager for
> > > > > > VMware
> > > > > > Date: Tue, 3 Sep 2013 02:46:35 +
> > > > > >
> > > > >
RE: Could not find corresponding resource manager for VMware
Pretty sure it's not an appliance issue. BTW, I am not using the appliance
version of cloudsand, I built from source which was on github. Looks like
paste.cloudstack.org might be down...
> From: imusa...@webmd.net
> To: dev@cloudstack.apache.org
> Subject: RE: Could not find corresponding resource manager for VMware
> Date: Thu, 5 Sep 2013 21:32:40 +
>
> So not an Appliance issue, but general cloudstack issue if I read this right.
>
> Can you paste the management-server.log in paste.cloudstack.org and respond
> with a link?
>
> > -----Original Message-
> > From: Michael Phillips [mailto:mphilli7...@hotmail.com]
> > Sent: Thursday, September 05, 2013 5:18 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: Could not find corresponding resource manager for VMware
> >
> > Ilya,
> > I was testing out the cloudsand version, and I noticed the following
> > error:
> > When creating an instance from a template, the instance ends with an error
> > state "Error Core:530 Unable to start instance 'name' {GUID}, see mgmt
> > server for details. This error is also logged in the mgmt servers log file.
> > I also
> > noticed on the hypervisor side {vmware} that the vm gets created without a
> > disk. The system then tries to boot the vm and of course it errors out. So
> > it
> > seems the root cause is when the system creates the instance from the
> > template it is not creating the vmdk disk. I have tried this with multiple
> > templates, and even the default "centos 5.3" template. If I deploy the
> > template direct using vCenter it works. Thoughts?
> > -Michael
> >
> > > From: imusa...@webmd.net
> > > To: dev@cloudstack.apache.org
> > > Subject: RE: Could not find corresponding resource manager for VMware
> > > Date: Wed, 4 Sep 2013 16:12:21 +
> > >
> > > Michael,
> > >
> > > Yes, if I see features that would be beneficial "now" rather than later
> > > when
> > 4.3 comes out. What will happen then is, I take the feature from 4.3
> > (master)
> > and backport it to CloudSand 4.2, test it, and if goes well, I push it to
> > github,
> > release rpms and virt appliance. Think of it as hybrid beta release of ACS.
> > >
> > > Regards
> > > ilya
> > >
> > > > -Original Message-
> > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com]
> > > > Sent: Tuesday, September 03, 2013 11:50 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: RE: Could not find corresponding resource manager for
> > > > VMware
> > > >
> > > > Sweet, I didn't even know this existed, I will check it out. So once
> > > > ACS 4.2 comes out, do you still plan on adding onto cloudsand?
> > > >
> > > > > From: imusa...@webmd.net
> > > > > To: dev@cloudstack.apache.org
> > > > > Subject: RE: Could not find corresponding resource manager for
> > > > > VMware
> > > > > Date: Tue, 3 Sep 2013 22:19:35 +
> > > > >
> > > > > Michael,
> > > > >
> > > > > ACS does support vSphere 5.1 as I run it now.
> > > > >
> > > > > Customized edition of CloudStack known as CloudSand, has extra
> > > > > VMware
> > > > support built in (primary dvswitch support and ACS hostnames -
> > > > displayed in VC). Its being ran in production by several companies.
> > > > CloudSand edition can be upgraded to official ACS 4.2 when it comes out.
> > > > >
> > > > > Check out the code from
> > > > > http://www.github.com/serverchief/cloudsand
> > > > >
> > > > > Homepage on www.cloudsand.com
> > > > >
> > > > > I will try to release CloudSand edition of ACS as virtual appliance
> > > > > this
> > week.
> > > > Since you've squared away build process, you can pull the source
> > > > code and build your own rpms.
> > > > >
> > > > > NOTE: you need to enable dvswitch support and vm.name support in
> > > > settings.
> > > > >
> > > > > Regards
> > > > > ilya
> > > > >
> > > > > > -Original Message-
> > > > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com]
> > > > > > Sent: Tuesday, September 03, 2013 1:32 PM
> > > > > > To
Security Groups
I posed this question in the user list, but I figured I would throw it out here as well...So If I have created a zone with the "DefaultSharedNetworkOfferingWithSGService" network offering, then created a VM using the default security group, which has 0 ingress rules, I should NOT be able to do things like PING that VM correct? The answer to the above question was answered "correct"...My next question is, in that case what are some things I could look at to see why it's not behaving as expected.
Thank you....
Just wanted to say thank you to everyone over the past couple weeks for answering all of the questions I have had. I am a cloudstack convert from vmware, so it has taken me a bit of time getting used to everything in cloudstack. Also good work on cloudstack to date!
RE: Security Groups
So that is definitely going to be the issue. I missed that in the 8.2.7 section of the install guide. > From: sangeetha.hariha...@citrix.com > To: dev@cloudstack.apache.org > Subject: RE: Security Groups > Date: Thu, 12 Sep 2013 17:19:16 + > > If you are using Xenserver hosts , can you make sure you have the CSP > packages installed? > > -Thanks > Sangeetha > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Thursday, September 12, 2013 9:33 AM > To: dev@cloudstack.apache.org > Subject: Security Groups > > I posed this question in the user list, but I figured I would throw it out > here as well...So If I have created a zone with the > "DefaultSharedNetworkOfferingWithSGService" network offering, then created a > VM using the default security group, which has 0 ingress rules, I should NOT > be able to do things like PING that VM correct? The answer to the above > question was answered "correct"...My next question is, in that case what are > some things I could look at to see why it's not behaving as expected. >
4.2.0 Installation Guide Section 3.7 "Building Non-OSS"
I was attempting to follow these directions to build the non-oss RPMS with vmware support however the below link in the docs does not work https://cwiki.apache.org/CLOUDSTACK/how-to-build-on-master-branch.html <--broken link Does anyone have the details to the dependencies needed or even better, a link to some precompiled non-oss RPM's?
Build Failure SNMP Alerts
All, I have been experiencing a build failure, trying to build nonoss RPMS for ver 4.2.1. The error I get is on the SNMP alerts plugin. The exact error message is "failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project cloud-plugin-snmp-alerts: There are test failures." I searched this on the mailing lists and found one other user who was having the exact same problem and it looks like he fixed it by deleting the repo at the following location ~/.m2/repository/. When I delete the ~/.m2/repository/ directory, I then get an error when building, when it gets to the VMware Base plugin. My guess is that by deleting the repo, I am deleting Vmware files it needs to build successfully. Users also suggested making sure I am using the correct version of maven. I have tried using version 3.1.0 and 3.0.4 both end with the same error. Any suggestions?
Can't login to webui
I have a new install on 4.2.1 on Centos, however I can not login to the UI using the default username\password combo of admin\password. I have checked my 'cloud' database and its has tables etc. I even checked the user table and it looks like there is an admin user... What am I missing??
RE: Can't login to webui
Looks like the admin account in the database has a hashed password of 0.180873463098773 > From: mphilli7...@hotmail.com > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > Subject: Can't login to webui > Date: Tue, 18 Feb 2014 22:50:46 -0600 > > I have a new install on 4.2.1 on Centos, however I can not login to the UI > using the default username\password combo of admin\password. > I have checked my 'cloud' database and its has tables etc. I even checked the > user table and it looks like there is an admin user... > What am I missing?? >
RE: Can't login to webui
hah...nice the logs are telling me the admin account is locked\disabled. So how does it become locked on a fresh install? > From: mphilli7...@hotmail.com > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > Subject: RE: Can't login to webui > Date: Tue, 18 Feb 2014 22:56:39 -0600 > > Looks like the admin account in the database has a hashed password of > 0.180873463098773 > > > From: mphilli7...@hotmail.com > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Subject: Can't login to webui > > Date: Tue, 18 Feb 2014 22:50:46 -0600 > > > > I have a new install on 4.2.1 on Centos, however I can not login to the UI > > using the default username\password combo of admin\password. > > I have checked my 'cloud' database and its has tables etc. I even checked > > the user table and it looks like there is an admin user... > > What am I missing?? > > >
RE: Can't login to webui
So I enabled the account via mysql through the command linehowever the logs still say the password does not match when trying to login... err dev guys what could the pw be if not "password"? > From: mphilli7...@hotmail.com > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > Subject: RE: Can't login to webui > Date: Tue, 18 Feb 2014 23:05:21 -0600 > > hah...nice the logs are telling me the admin account is locked\disabled. So > how does it become locked on a fresh install? > > > From: mphilli7...@hotmail.com > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Subject: RE: Can't login to webui > > Date: Tue, 18 Feb 2014 22:56:39 -0600 > > > > Looks like the admin account in the database has a hashed password of > > 0.180873463098773 > > > > > From: mphilli7...@hotmail.com > > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > > Subject: Can't login to webui > > > Date: Tue, 18 Feb 2014 22:50:46 -0600 > > > > > > I have a new install on 4.2.1 on Centos, however I can not login to the > > > UI using the default username\password combo of admin\password. > > > I have checked my 'cloud' database and its has tables etc. I even checked > > > the user table and it looks like there is an admin user... > > > What am I missing?? > > > > > >
RE: Can't login to webui
something obviously went horribly wrong so I am starting over > From: mphilli7...@hotmail.com > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > Subject: RE: Can't login to webui > Date: Tue, 18 Feb 2014 23:23:46 -0600 > > So I enabled the account via mysql through the command linehowever the > logs still say the password does not match when trying to login... > err dev guys what could the pw be if not "password"? > > > > > From: mphilli7...@hotmail.com > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Subject: RE: Can't login to webui > > Date: Tue, 18 Feb 2014 23:05:21 -0600 > > > > hah...nice the logs are telling me the admin account is locked\disabled. So > > how does it become locked on a fresh install? > > > > > From: mphilli7...@hotmail.com > > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > > Subject: RE: Can't login to webui > > > Date: Tue, 18 Feb 2014 22:56:39 -0600 > > > > > > Looks like the admin account in the database has a hashed password of > > > 0.180873463098773 > > > > > > > From: mphilli7...@hotmail.com > > > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > > > Subject: Can't login to webui > > > > Date: Tue, 18 Feb 2014 22:50:46 -0600 > > > > > > > > I have a new install on 4.2.1 on Centos, however I can not login to the > > > > UI using the default username\password combo of admin\password. > > > > I have checked my 'cloud' database and its has tables etc. I even > > > > checked the user table and it looks like there is an admin user... > > > > What am I missing?? > > > > > > > > > >
RE: Can't login to webui
Mike, Can you tell me what OS and version you are running on your management server? > Date: Wed, 19 Feb 2014 12:25:21 -0700 > Subject: Re: Can't login to webui > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > CC: us...@cloudstack.apache.org > > Sorry I don't have any useful assistance to provide here, but I just wanted > to note that I have had this happen in the past, as well, and "solved" it > by starting over from scratch. > > > On Tue, Feb 18, 2014 at 11:04 PM, Michael Phillips > wrote: > > > something obviously went horribly wrong so I am starting over > > > > > From: mphilli7...@hotmail.com > > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > > Subject: RE: Can't login to webui > > > Date: Tue, 18 Feb 2014 23:23:46 -0600 > > > > > > So I enabled the account via mysql through the command linehowever > > the logs still say the password does not match when trying to login... > > > err dev guys what could the pw be if not "password"? > > > > > > > > > > > > > From: mphilli7...@hotmail.com > > > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > > > Subject: RE: Can't login to webui > > > > Date: Tue, 18 Feb 2014 23:05:21 -0600 > > > > > > > > hah...nice the logs are telling me the admin account is > > locked\disabled. So how does it become locked on a fresh install? > > > > > > > > > From: mphilli7...@hotmail.com > > > > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > > > > Subject: RE: Can't login to webui > > > > > Date: Tue, 18 Feb 2014 22:56:39 -0600 > > > > > > > > > > Looks like the admin account in the database has a hashed password > > of 0.180873463098773 > > > > > > > > > > > From: mphilli7...@hotmail.com > > > > > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > > > > > Subject: Can't login to webui > > > > > > Date: Tue, 18 Feb 2014 22:50:46 -0600 > > > > > > > > > > > > I have a new install on 4.2.1 on Centos, however I can not login > > to the UI using the default username\password combo of admin\password. > > > > > > I have checked my 'cloud' database and its has tables etc. I even > > checked the user table and it looks like there is an admin user... > > > > > > What am I missing?? > > > > > > > > > > > > > > > > > > > > > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)*
VMware and NFS
Hey dev guys, I just recently got CS up and running with vmware. However I am running into an issue where it seems my esxi hosts are not mounting the secondary NFS storage. NFS is working as I can mount to it from other linux boxes, and I can mount a NFS datastore from the hypervisors. In my log I see the following few errors: "Unable to create mount point for nfs://172.16.25.85/export/secondary", "Secondary storage mount point: /mnt/sec", "in directory "/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file or directory" Adding secondary storage seemed straight forward and I even was able to make it work using XEN as the hypervisor, so the problem definitely seems to be esxi... Any tricks to making esxi work with cloudstack and NFS? Thanks in advance for any help!
RE: VMware and NFS
Yes to both... > From: nitin.me...@citrix.com > To: dev@cloudstack.apache.org > Subject: Re: VMware and NFS > Date: Fri, 21 Feb 2014 02:39:01 + > > Couple of questions. > Did you seed the system vm template onto the sec. storage ? And can you > mount that template location in sec. storage on your management server ? > > On 20/02/14 6:32 PM, "Michael Phillips" wrote: > > >Hey dev guys, I just recently got CS up and running with vmware. However > >I am running into an issue where it seems my esxi hosts are not mounting > >the secondary NFS storage. > >NFS is working as I can mount to it from other linux boxes, and I can > >mount a NFS datastore from the hypervisors. In my log I see the following > >few errors: > >"Unable to create mount point for nfs://172.16.25.85/export/secondary", > >"Secondary storage mount point: /mnt/sec", "in directory > >"/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file > >or directory" > >Adding secondary storage seemed straight forward and I even was able to > >make it work using XEN as the hypervisor, so the problem definitely seems > >to be esxi... > >Any tricks to making esxi work with cloudstack and NFS? > >Thanks in advance for any help! >
RE: VMware and NFS
Interesting as I do see errors in the mgmt log in regards to /mnt/sec...however if I am understanding the architecture correctly isn't it the hypervisor that needs access to the secondary storage? The mgmt server only needs to access secondary storage to be able to seed the templates right? > Date: Thu, 20 Feb 2014 19:43:32 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > I may be remembering this incorrectly, but for VMware doesn't the > management server have to be able to mount the secondary storage NFS share > to /mnt/sec? > > > On Thu, Feb 20, 2014 at 7:39 PM, Nitin Mehta wrote: > > > Couple of questions. > > Did you seed the system vm template onto the sec. storage ? And can you > > mount that template location in sec. storage on your management server ? > > > > On 20/02/14 6:32 PM, "Michael Phillips" wrote: > > > > >Hey dev guys, I just recently got CS up and running with vmware. However > > >I am running into an issue where it seems my esxi hosts are not mounting > > >the secondary NFS storage. > > >NFS is working as I can mount to it from other linux boxes, and I can > > >mount a NFS datastore from the hypervisors. In my log I see the following > > >few errors: > > >"Unable to create mount point for nfs://172.16.25.85/export/secondary", > > >"Secondary storage mount point: /mnt/sec", "in directory > > >"/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file > > >or directory" > > >Adding secondary storage seemed straight forward and I even was able to > > >make it work using XEN as the hypervisor, so the problem definitely seems > > >to be esxi... > > >Any tricks to making esxi work with cloudstack and NFS? > > >Thanks in advance for any help! > > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)*
RE: VMware and NFS
h.I have been scoring docs etcit would not surprise me... Can any of the dev guys possibly elaborate? BTW Mike, I finally gave up on making 4.x work with centos and just used ubuntuit worked like a charm. So I can only guess that something is up with the newer versions of CS with Centos > Date: Thu, 20 Feb 2014 21:24:07 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > Yes, the hypervisor does need to mount the NFS share, but I seem to > remember there being something unusual about VMware in that the management > server needed to be able to mount the NFS share, as well. > > > On Thu, Feb 20, 2014 at 8:59 PM, Michael Phillips > wrote: > > > Interesting as I do see errors in the mgmt log in regards to > > /mnt/sec...however if I am understanding the architecture correctly isn't > > it the hypervisor that needs access to the secondary storage? > > The mgmt server only needs to access secondary storage to be able to seed > > the templates right? > > > > > > > > > Date: Thu, 20 Feb 2014 19:43:32 -0700 > > > Subject: Re: VMware and NFS > > > From: mike.tutkow...@solidfire.com > > > To: dev@cloudstack.apache.org > > > > > > I may be remembering this incorrectly, but for VMware doesn't the > > > management server have to be able to mount the secondary storage NFS > > share > > > to /mnt/sec? > > > > > > > > > On Thu, Feb 20, 2014 at 7:39 PM, Nitin Mehta > > wrote: > > > > > > > Couple of questions. > > > > Did you seed the system vm template onto the sec. storage ? And can you > > > > mount that template location in sec. storage on your management server > > ? > > > > > > > > On 20/02/14 6:32 PM, "Michael Phillips" > > wrote: > > > > > > > > >Hey dev guys, I just recently got CS up and running with vmware. > > However > > > > >I am running into an issue where it seems my esxi hosts are not > > mounting > > > > >the secondary NFS storage. > > > > >NFS is working as I can mount to it from other linux boxes, and I can > > > > >mount a NFS datastore from the hypervisors. In my log I see the > > following > > > > >few errors: > > > > >"Unable to create mount point for nfs://172.16.25.85/export/secondary > > ", > > > > >"Secondary storage mount point: /mnt/sec", "in directory > > > > >"/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such > > file > > > > >or directory" > > > > >Adding secondary storage seemed straight forward and I even was able > > to > > > > >make it work using XEN as the hypervisor, so the problem definitely > > seems > > > > >to be esxi... > > > > >Any tricks to making esxi work with cloudstack and NFS? > > > > >Thanks in advance for any help! > > > > > > > > > > > > > > > > > -- > > > *Mike Tutkowski* > > > *Senior CloudStack Developer, SolidFire Inc.* > > > e: mike.tutkow...@solidfire.com > > > o: 303.746.7302 > > > Advancing the way the world uses the > > > cloud<http://solidfire.com/solution/overview/?video=play> > > > *(tm)* > > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)*
RE: VMware and NFS
Actually I am pretty sure that is what it doesSo I changed like 4-5 things "my mistake", then I noticed a datastore with a "GUID" looking name popped up on my hosts. This datastore was mapped to my NFS share. Once that showed up CS started creating the system VMs. So I am trying to back track and see what setting made it kick in...Stay tuned... > Date: Fri, 21 Feb 2014 08:40:13 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > So, just curious here, but why wouldn't the ESX(i) host simply be able to > create an NFS datastore that points to the NFS share on the secondary > storage location directly? > > > On Thu, Feb 20, 2014 at 10:31 PM, Nitin Mehta wrote: > > > For XS that¹s not required as its pushed into XS directly. > > > > I also think secondary storage is mounted for Vmware on MS to copy the > > system vm template to Primary storage. > > > > On 20/02/14 9:13 PM, "Mike Tutkowski" > > wrote: > > > > >So, just to be sure I have this correct, the management server mounts > > >secondary storage regardless of hypervisor type due to systemvm.iso. Is > > >that correct? > > > > > >Thanks > > > > > > > > >On Thu, Feb 20, 2014 at 9:46 PM, Sateesh Chodapuneedi < > > >sateesh.chodapune...@citrix.com> wrote: > > > > > >> > -Original Message- > > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > > >> > Sent: 21 February 2014 09:54 > > >> > To: dev@cloudstack.apache.org > > >> > Subject: Re: VMware and NFS > > >> > > > >> > Yes, the hypervisor does need to mount the NFS share, but I seem to > > >> remember there being something unusual about VMware in that the > > >> > management server needed to be able to mount the NFS share, as well. > > >> > > >> Yeah, management server mount secondary storage. > > >> Reason behind this is CS does patching of system vms by injecting > > >> systemvm.iso into system vm. In this process, management server mounts > > >> secondary storage and copies systemvm.iso image into secondary storage > > >> inside "systemvm" folder. Later that would be mounted by system vm. > > >>During > > >> system vm startup there is a script "cloud-early-config" which installs > > >>the > > >> content of mounted iso inside the system vm. > > >> > > >> Hope that clarifies. > > >> > > >> Regards, > > >> Sateesh > > >> > > >> > > > >> > > > >> > On Thu, Feb 20, 2014 at 8:59 PM, Michael Phillips > > >> > wrote: > > >> > > > >> > > Interesting as I do see errors in the mgmt log in regards to > > >> > > /mnt/sec...however if I am understanding the architecture correctly > > >> > > isn't it the hypervisor that needs access to the secondary storage? > > >> > > The mgmt server only needs to access secondary storage to be able to > > >> > > seed the templates right? > > >> > > > > >> > > > > >> > > > > >> > > > Date: Thu, 20 Feb 2014 19:43:32 -0700 > > >> > > > Subject: Re: VMware and NFS > > >> > > > From: mike.tutkow...@solidfire.com > > >> > > > To: dev@cloudstack.apache.org > > >> > > > > > >> > > > I may be remembering this incorrectly, but for VMware doesn't the > > >> > > > management server have to be able to mount the secondary storage > > >>NFS > > >> > > share > > >> > > > to /mnt/sec? > > >> > > > > > >> > > > > > >> > > > On Thu, Feb 20, 2014 at 7:39 PM, Nitin Mehta > > >> > > > > > >> > > wrote: > > >> > > > > > >> > > > > Couple of questions. > > >> > > > > Did you seed the system vm template onto the sec. storage ? And > > >> > > > > can you mount that template location in sec. storage on your > > >> > > > > management server > > >> > > ? > > >> > > > > > > >> > > > > On 20/02/14
RE: VMware and NFS
Success!! So what I had to do was to mount "/mnt/sec" on the mgmt server to the secondary NFS storageOnce I did that all the secondary vm's were created and the mgmt server created the "GUID" named datastore on the hypervisors back to the NFS share... Funny that this was not documented anywhere unless I missed it... > Date: Fri, 21 Feb 2014 08:40:13 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > So, just curious here, but why wouldn't the ESX(i) host simply be able to > create an NFS datastore that points to the NFS share on the secondary > storage location directly? > > > On Thu, Feb 20, 2014 at 10:31 PM, Nitin Mehta wrote: > > > For XS that¹s not required as its pushed into XS directly. > > > > I also think secondary storage is mounted for Vmware on MS to copy the > > system vm template to Primary storage. > > > > On 20/02/14 9:13 PM, "Mike Tutkowski" > > wrote: > > > > >So, just to be sure I have this correct, the management server mounts > > >secondary storage regardless of hypervisor type due to systemvm.iso. Is > > >that correct? > > > > > >Thanks > > > > > > > > >On Thu, Feb 20, 2014 at 9:46 PM, Sateesh Chodapuneedi < > > >sateesh.chodapune...@citrix.com> wrote: > > > > > >> > -Original Message- > > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > > >> > Sent: 21 February 2014 09:54 > > >> > To: dev@cloudstack.apache.org > > >> > Subject: Re: VMware and NFS > > >> > > > >> > Yes, the hypervisor does need to mount the NFS share, but I seem to > > >> remember there being something unusual about VMware in that the > > >> > management server needed to be able to mount the NFS share, as well. > > >> > > >> Yeah, management server mount secondary storage. > > >> Reason behind this is CS does patching of system vms by injecting > > >> systemvm.iso into system vm. In this process, management server mounts > > >> secondary storage and copies systemvm.iso image into secondary storage > > >> inside "systemvm" folder. Later that would be mounted by system vm. > > >>During > > >> system vm startup there is a script "cloud-early-config" which installs > > >>the > > >> content of mounted iso inside the system vm. > > >> > > >> Hope that clarifies. > > >> > > >> Regards, > > >> Sateesh > > >> > > >> > > > >> > > > >> > On Thu, Feb 20, 2014 at 8:59 PM, Michael Phillips > > >> > wrote: > > >> > > > >> > > Interesting as I do see errors in the mgmt log in regards to > > >> > > /mnt/sec...however if I am understanding the architecture correctly > > >> > > isn't it the hypervisor that needs access to the secondary storage? > > >> > > The mgmt server only needs to access secondary storage to be able to > > >> > > seed the templates right? > > >> > > > > >> > > > > >> > > > > >> > > > Date: Thu, 20 Feb 2014 19:43:32 -0700 > > >> > > > Subject: Re: VMware and NFS > > >> > > > From: mike.tutkow...@solidfire.com > > >> > > > To: dev@cloudstack.apache.org > > >> > > > > > >> > > > I may be remembering this incorrectly, but for VMware doesn't the > > >> > > > management server have to be able to mount the secondary storage > > >>NFS > > >> > > share > > >> > > > to /mnt/sec? > > >> > > > > > >> > > > > > >> > > > On Thu, Feb 20, 2014 at 7:39 PM, Nitin Mehta > > >> > > > > > >> > > wrote: > > >> > > > > > >> > > > > Couple of questions. > > >> > > > > Did you seed the system vm template onto the sec. storage ? And > > >> > > > > can you mount that template location in sec. storage on your > > >> > > > > management server > > >> > > ? > > >> > > > > > > >> > > > > On 20/02/14 6:32 PM, "Michael Phillips" > > >> > > >> > > wrote: >
RE: VMware and NFS
Definitely not sure why the mgmt server does not create /mnt/sec for you and auto mount it Dev guys, is it possible to get this feature added in a future build? Also what would it take to document this is the current doumentation? If you have multiple secondary storages, my guess is that you would need multiple mount points such as /mnt/sec, /mnt/sec1, /mnt/sec2...I'm guessing that the most painless scenario is to just use one HUGE secondary storage and be done with it. > Date: Fri, 21 Feb 2014 11:34:18 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > I believe I had trouble with that in my development environment about 10 or > so months ago. I think it turned out to be a permissions issue. Perhaps I > didn't have my username in the sudoers file or something. My thinking is > the management server is supposed to create /mnt/sec for you. > > I wonder which NFS share it maps /mnt/sec to if you have multiple NFS > secondary storages? > > > On Fri, Feb 21, 2014 at 11:31 AM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > > > Thanks for the clarification. > > > > I was pretty confident an ESX host creates an NFS datastore (with a UUID > > for a name) that maps to the NFS share. This is similar to how a XenServer > > host creates an NFS storage repository that maps to the NFS share. > > > > > > On Fri, Feb 21, 2014 at 9:12 AM, Michael Phillips > > wrote: > > > >> Actually I am pretty sure that is what it doesSo I changed like 4-5 > >> things "my mistake", then I noticed a datastore with a "GUID" looking name > >> popped up on my hosts. This datastore was mapped to my NFS share. Once that > >> showed up CS started creating the system VMs. So I am trying to back track > >> and see what setting made it kick in...Stay tuned... > >> > Date: Fri, 21 Feb 2014 08:40:13 -0700 > >> > Subject: Re: VMware and NFS > >> > From: mike.tutkow...@solidfire.com > >> > To: dev@cloudstack.apache.org > >> > > >> > So, just curious here, but why wouldn't the ESX(i) host simply be able > >> to > >> > create an NFS datastore that points to the NFS share on the secondary > >> > storage location directly? > >> > > >> > > >> > On Thu, Feb 20, 2014 at 10:31 PM, Nitin Mehta >> >wrote: > >> > > >> > > For XS that¹s not required as its pushed into XS directly. > >> > > > >> > > I also think secondary storage is mounted for Vmware on MS to copy the > >> > > system vm template to Primary storage. > >> > > > >> > > On 20/02/14 9:13 PM, "Mike Tutkowski" > >> > > wrote: > >> > > > >> > > >So, just to be sure I have this correct, the management server mounts > >> > > >secondary storage regardless of hypervisor type due to systemvm.iso. > >> Is > >> > > >that correct? > >> > > > > >> > > >Thanks > >> > > > > >> > > > > >> > > >On Thu, Feb 20, 2014 at 9:46 PM, Sateesh Chodapuneedi < > >> > > >sateesh.chodapune...@citrix.com> wrote: > >> > > > > >> > > >> > -Original Message- > >> > > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > >> > > >> > Sent: 21 February 2014 09:54 > >> > > >> > To: dev@cloudstack.apache.org > >> > > >> > Subject: Re: VMware and NFS > >> > > >> > > >> > > >> > Yes, the hypervisor does need to mount the NFS share, but I seem > >> to > >> > > >> remember there being something unusual about VMware in that the > >> > > >> > management server needed to be able to mount the NFS share, as > >> well. > >> > > >> > >> > > >> Yeah, management server mount secondary storage. > >> > > >> Reason behind this is CS does patching of system vms by injecting > >> > > >> systemvm.iso into system vm. In this process, management server > >> mounts > >> > > >> secondary storage and copies systemvm.iso image into secondary > >> storage > >> > > >> inside "systemvm" folder. Later that would be mounted by system vm. > >> > > >>During > >> > > >> sy
RE: VMware and NFS
Any idea why the default centos5.3 template would be "stuck" downloading at 88%?? The secondary storage where it is getting downloaded to has 44GB of free space. > Date: Fri, 21 Feb 2014 11:34:18 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > I believe I had trouble with that in my development environment about 10 or > so months ago. I think it turned out to be a permissions issue. Perhaps I > didn't have my username in the sudoers file or something. My thinking is > the management server is supposed to create /mnt/sec for you. > > I wonder which NFS share it maps /mnt/sec to if you have multiple NFS > secondary storages? > > > On Fri, Feb 21, 2014 at 11:31 AM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > > > Thanks for the clarification. > > > > I was pretty confident an ESX host creates an NFS datastore (with a UUID > > for a name) that maps to the NFS share. This is similar to how a XenServer > > host creates an NFS storage repository that maps to the NFS share. > > > > > > On Fri, Feb 21, 2014 at 9:12 AM, Michael Phillips > > wrote: > > > >> Actually I am pretty sure that is what it doesSo I changed like 4-5 > >> things "my mistake", then I noticed a datastore with a "GUID" looking name > >> popped up on my hosts. This datastore was mapped to my NFS share. Once that > >> showed up CS started creating the system VMs. So I am trying to back track > >> and see what setting made it kick in...Stay tuned... > >> > Date: Fri, 21 Feb 2014 08:40:13 -0700 > >> > Subject: Re: VMware and NFS > >> > From: mike.tutkow...@solidfire.com > >> > To: dev@cloudstack.apache.org > >> > > >> > So, just curious here, but why wouldn't the ESX(i) host simply be able > >> to > >> > create an NFS datastore that points to the NFS share on the secondary > >> > storage location directly? > >> > > >> > > >> > On Thu, Feb 20, 2014 at 10:31 PM, Nitin Mehta >> >wrote: > >> > > >> > > For XS that¹s not required as its pushed into XS directly. > >> > > > >> > > I also think secondary storage is mounted for Vmware on MS to copy the > >> > > system vm template to Primary storage. > >> > > > >> > > On 20/02/14 9:13 PM, "Mike Tutkowski" > >> > > wrote: > >> > > > >> > > >So, just to be sure I have this correct, the management server mounts > >> > > >secondary storage regardless of hypervisor type due to systemvm.iso. > >> Is > >> > > >that correct? > >> > > > > >> > > >Thanks > >> > > > > >> > > > > >> > > >On Thu, Feb 20, 2014 at 9:46 PM, Sateesh Chodapuneedi < > >> > > >sateesh.chodapune...@citrix.com> wrote: > >> > > > > >> > > >> > -Original Message- > >> > > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > >> > > >> > Sent: 21 February 2014 09:54 > >> > > >> > To: dev@cloudstack.apache.org > >> > > >> > Subject: Re: VMware and NFS > >> > > >> > > >> > > >> > Yes, the hypervisor does need to mount the NFS share, but I seem > >> to > >> > > >> remember there being something unusual about VMware in that the > >> > > >> > management server needed to be able to mount the NFS share, as > >> well. > >> > > >> > >> > > >> Yeah, management server mount secondary storage. > >> > > >> Reason behind this is CS does patching of system vms by injecting > >> > > >> systemvm.iso into system vm. In this process, management server > >> mounts > >> > > >> secondary storage and copies systemvm.iso image into secondary > >> storage > >> > > >> inside "systemvm" folder. Later that would be mounted by system vm. > >> > > >>During > >> > > >> system vm startup there is a script "cloud-early-config" which > >> installs > >> > > >>the > >> > > >> content of mounted iso inside the system vm. > >> > > >> > >> > > >> Hope that clarifies. > >>
RE: VMware and NFS
How would you go about manually downloading it? > Date: Fri, 21 Feb 2014 12:05:20 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > Have you tried manually downloading it (outside of CloudStack) to see if > that works? > > > On Fri, Feb 21, 2014 at 12:01 PM, Michael Phillips > wrote: > > > Any idea why the default centos5.3 template would be "stuck" downloading > > at 88%?? > > The secondary storage where it is getting downloaded to has 44GB of free > > space. > > > > > Date: Fri, 21 Feb 2014 11:34:18 -0700 > > > Subject: Re: VMware and NFS > > > From: mike.tutkow...@solidfire.com > > > To: dev@cloudstack.apache.org > > > > > > I believe I had trouble with that in my development environment about 10 > > or > > > so months ago. I think it turned out to be a permissions issue. Perhaps I > > > didn't have my username in the sudoers file or something. My thinking is > > > the management server is supposed to create /mnt/sec for you. > > > > > > I wonder which NFS share it maps /mnt/sec to if you have multiple NFS > > > secondary storages? > > > > > > > > > On Fri, Feb 21, 2014 at 11:31 AM, Mike Tutkowski < > > > mike.tutkow...@solidfire.com> wrote: > > > > > > > Thanks for the clarification. > > > > > > > > I was pretty confident an ESX host creates an NFS datastore (with a > > UUID > > > > for a name) that maps to the NFS share. This is similar to how a > > XenServer > > > > host creates an NFS storage repository that maps to the NFS share. > > > > > > > > > > > > On Fri, Feb 21, 2014 at 9:12 AM, Michael Phillips < > > mphilli7...@hotmail.com > > > > > wrote: > > > > > > > >> Actually I am pretty sure that is what it doesSo I changed like > > 4-5 > > > >> things "my mistake", then I noticed a datastore with a "GUID" looking > > name > > > >> popped up on my hosts. This datastore was mapped to my NFS share. > > Once that > > > >> showed up CS started creating the system VMs. So I am trying to back > > track > > > >> and see what setting made it kick in...Stay tuned... > > > >> > Date: Fri, 21 Feb 2014 08:40:13 -0700 > > > >> > Subject: Re: VMware and NFS > > > >> > From: mike.tutkow...@solidfire.com > > > >> > To: dev@cloudstack.apache.org > > > >> > > > > >> > So, just curious here, but why wouldn't the ESX(i) host simply be > > able > > > >> to > > > >> > create an NFS datastore that points to the NFS share on the > > secondary > > > >> > storage location directly? > > > >> > > > > >> > > > > >> > On Thu, Feb 20, 2014 at 10:31 PM, Nitin Mehta < > > nitin.me...@citrix.com > > > >> >wrote: > > > >> > > > > >> > > For XS that¹s not required as its pushed into XS directly. > > > >> > > > > > >> > > I also think secondary storage is mounted for Vmware on MS to > > copy the > > > >> > > system vm template to Primary storage. > > > >> > > > > > >> > > On 20/02/14 9:13 PM, "Mike Tutkowski" < > > mike.tutkow...@solidfire.com> > > > >> > > wrote: > > > >> > > > > > >> > > >So, just to be sure I have this correct, the management server > > mounts > > > >> > > >secondary storage regardless of hypervisor type due to > > systemvm.iso. > > > >> Is > > > >> > > >that correct? > > > >> > > > > > > >> > > >Thanks > > > >> > > > > > > >> > > > > > > >> > > >On Thu, Feb 20, 2014 at 9:46 PM, Sateesh Chodapuneedi < > > > >> > > >sateesh.chodapune...@citrix.com> wrote: > > > >> > > > > > > >> > > >> > -Original Message- > > > >> > > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > > > >> > > >> > Sent: 21 February 2014 09:54 > > > >> > > >> > To: dev@cloudstack.apache.org > > > >&
RE: VMware and NFS
Gotcha, thought about trying to upload my own template or iso to see how that worked.. > Date: Fri, 21 Feb 2014 12:16:15 -0700 > Subject: Re: VMware and NFS > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > If you look in the vm_template table in the cloud DB, you should be able to > find a URL for that template. > > > On Fri, Feb 21, 2014 at 12:12 PM, Michael Phillips > wrote: > > > How would you go about manually downloading it? > > > > > Date: Fri, 21 Feb 2014 12:05:20 -0700 > > > Subject: Re: VMware and NFS > > > From: mike.tutkow...@solidfire.com > > > To: dev@cloudstack.apache.org > > > > > > Have you tried manually downloading it (outside of CloudStack) to see if > > > that works? > > > > > > > > > On Fri, Feb 21, 2014 at 12:01 PM, Michael Phillips > > > wrote: > > > > > > > Any idea why the default centos5.3 template would be "stuck" > > downloading > > > > at 88%?? > > > > The secondary storage where it is getting downloaded to has 44GB of > > free > > > > space. > > > > > > > > > Date: Fri, 21 Feb 2014 11:34:18 -0700 > > > > > Subject: Re: VMware and NFS > > > > > From: mike.tutkow...@solidfire.com > > > > > To: dev@cloudstack.apache.org > > > > > > > > > > I believe I had trouble with that in my development environment > > about 10 > > > > or > > > > > so months ago. I think it turned out to be a permissions issue. > > Perhaps I > > > > > didn't have my username in the sudoers file or something. My > > thinking is > > > > > the management server is supposed to create /mnt/sec for you. > > > > > > > > > > I wonder which NFS share it maps /mnt/sec to if you have multiple NFS > > > > > secondary storages? > > > > > > > > > > > > > > > On Fri, Feb 21, 2014 at 11:31 AM, Mike Tutkowski < > > > > > mike.tutkow...@solidfire.com> wrote: > > > > > > > > > > > Thanks for the clarification. > > > > > > > > > > > > I was pretty confident an ESX host creates an NFS datastore (with a > > > > UUID > > > > > > for a name) that maps to the NFS share. This is similar to how a > > > > XenServer > > > > > > host creates an NFS storage repository that maps to the NFS share. > > > > > > > > > > > > > > > > > > On Fri, Feb 21, 2014 at 9:12 AM, Michael Phillips < > > > > mphilli7...@hotmail.com > > > > > > > wrote: > > > > > > > > > > > >> Actually I am pretty sure that is what it doesSo I changed > > like > > > > 4-5 > > > > > >> things "my mistake", then I noticed a datastore with a "GUID" > > looking > > > > name > > > > > >> popped up on my hosts. This datastore was mapped to my NFS share. > > > > Once that > > > > > >> showed up CS started creating the system VMs. So I am trying to > > back > > > > track > > > > > >> and see what setting made it kick in...Stay tuned... > > > > > >> > Date: Fri, 21 Feb 2014 08:40:13 -0700 > > > > > >> > Subject: Re: VMware and NFS > > > > > >> > From: mike.tutkow...@solidfire.com > > > > > >> > To: dev@cloudstack.apache.org > > > > > >> > > > > > > >> > So, just curious here, but why wouldn't the ESX(i) host simply > > be > > > > able > > > > > >> to > > > > > >> > create an NFS datastore that points to the NFS share on the > > > > secondary > > > > > >> > storage location directly? > > > > > >> > > > > > > >> > > > > > > >> > On Thu, Feb 20, 2014 at 10:31 PM, Nitin Mehta < > > > > nitin.me...@citrix.com > > > > > >> >wrote: > > > > > >> > > > > > > >> > > For XS that¹s not required as its pushed into XS directly. > > > > > >> > > > > > > > >> > > I also think secondary storage is mounted for Vmware on MS to > > > > copy the > > > > > >
Interesting 4.2.1. Issue...
So I have a redundant pair of management servers running on 4.2.1. At least once a day one of the management servers crashes and the log gets filled with the following messages: java.lang.OutOfMemoryError: Java heap spac0java.lang.ArrayIndexOutOfBoundsExceptioneCaused by: java.io.EOFException: SSL peer shut down incorrectlyCaused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake and there are a few others. When the one management server tanks, although the other management server is up and active, it won't actually process any UI commands until the crashed server is restarted. Example of won't process any UI command is create a new instance, create a new account, etc. After doing some searching I have found that others have noticed java heap errors in 4.2.1, and the suggested fix is to increase the heap size. I am planning on increasing it from 2g to 4g, however if the problem is something like a memory leak, then increasing the heap size will just delay the inevitable. Has anyone else fixed this issue by increasing the heap size? Or what is the recommended value? **updated...as expected I increased the heap size from 2g to 4g, and it just took longer for the problem to reoccur... In my honest opinion of bigger concern is the fact that when one management server crashes the other stops functioning as well. So this begs the question of why even bother with a redundant pair of servers..Anybody else experience this issue? I would love to hear any dev guys opinion on this
RE: Interesting 4.2.1. Issue...
So I just checked my tomcat version and we are running 6.0.35 which must be the default that comes with Ubuntu 12.04 out of the box. Our memory settings are as follows: JAVA_OPTS="-Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xmx4g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m" So what version of tomcat are you running 6.0.35 or 6.0.33? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Tue, 1 Apr 2014 11:23:57 +0800 > > We have the same issue, after an upgrade from 2.2.14 to 4.2.1, and during > this upgrade we had upgrade from Ubuntu 10 LTS to Ubuntu 12 LTS, it seems it > related to tomcat 6.0.35, because it is recommended to have tomcat 6.0.33 > which doesn't come by default with Ubuntu 12.04.4 > > Kind Regards > Amin > > > > -Original Message- > From: Marcus [mailto:shadow...@gmail.com] > Sent: Tuesday, 1 April 2014 6:22 AM > To: dev@cloudstack.apache.org > Subject: Re: Interesting 4.2.1. Issue... > > I'm running 3 mgmt servers on 4.2.1, haven't seen any issues like that. You > can send along your memory settings... here's what I'm > running: > > JAVA_OPTS="-Djava.awt.headless=true > -Dcom.sun.management.jmxremote.port=45219 > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false -Xmx2g > -XX:+HeapDumpOnOutOfMemoryError > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M > -XX:MaxPermSize=800m > > On Mon, Mar 31, 2014 at 9:33 AM, Michael Phillips > wrote: > > So I have a redundant pair of management servers running on 4.2.1. At least > > once a day one of the management servers crashes and the log gets filled > > with the following messages: > > java.lang.OutOfMemoryError: Java heap > > spac0java.lang.ArrayIndexOutOfBoundsExceptioneCaused by: > > java.io.EOFException: SSL peer shut down incorrectlyCaused by: > > javax.net.ssl.SSLHandshakeException: Remote host closed connection during > > handshake and there are a few others. When the one management server tanks, > > although the other management server is up and active, it won't actually > > process any UI commands until the crashed server is restarted. Example of > > won't process any UI command is create a new instance, create a new > > account, etc. After doing some searching I have found that others have > > noticed java heap errors in 4.2.1, and the suggested fix is to increase the > > heap size. I am planning on increasing it from 2g to 4g, however if the > > problem is something like a memory leak, then increasing the heap size will > > just delay the inevitable. Has anyone else fixed this issue by increasing > > the heap size? Or what is the recommended value? **updated...as expected I > > increased the heap size from 2g to 4g, and it just too > k longer for the problem to reoccur... > > In my honest opinion of bigger concern is the fact that when one management > > server crashes the other stops functioning as well. So this begs the > > question of why even bother with a redundant pair of servers..Anybody else > > experience this issue? I would love to hear any dev guys opinion on this > >
RE: Interesting 4.2.1. Issue...
This may be a silly question, but in all of the docs I am reading online in regards to increasing the java heap size, they are specifying it as -Xmx"size""MB" example -Xmx2048m vs -Xmx2g Is it possible that it's not reading the 2g variable as 2GB? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Thu, 3 Apr 2014 09:06:17 +0800 > > It is 6.0.35 and it still produces this error, even after increasing the Xmx > to 4g, we have installed tomcat 6.0.33 and each time we install the > cloudstack it does not sense the installed 6.0.33 and attempts to install > 6.0.35 as it is dependent on it. Silly solution is that we scheduled a daily > restart @ 2PM through a cron job But first you have to "killall jvsc" > then restart the management server. > > What we are considering is to migrate the management server to CentOS 6.5 it > comes with tomcat 6.0.24 and mysql 5.1, we attempted to restore the dump on a > pilot environment and it worked. > > If someone else has a better solution than this would you please share it? > > Kind Regards > Amin > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Thursday, 3 April 2014 5:31 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > So I just checked my tomcat version and we are running 6.0.35 which must be > the default that comes with Ubuntu 12.04 out of the box. Our memory settings > are as follows: > JAVA_OPTS="-Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false -Xmx4g > -XX:+HeapDumpOnOutOfMemoryError > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M > -XX:MaxPermSize=800m" > So what version of tomcat are you running 6.0.35 or 6.0.33? > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Tue, 1 Apr 2014 11:23:57 +0800 > > > > We have the same issue, after an upgrade from 2.2.14 to 4.2.1, and > > during this upgrade we had upgrade from Ubuntu 10 LTS to Ubuntu 12 > > LTS, it seems it related to tomcat 6.0.35, because it is recommended > > to have tomcat 6.0.33 which doesn't come by default with Ubuntu > > 12.04.4 > > > > Kind Regards > > Amin > > > > > > > > -Original Message- > > From: Marcus [mailto:shadow...@gmail.com] > > Sent: Tuesday, 1 April 2014 6:22 AM > > To: dev@cloudstack.apache.org > > Subject: Re: Interesting 4.2.1. Issue... > > > > I'm running 3 mgmt servers on 4.2.1, haven't seen any issues like > > that. You can send along your memory settings... here's what I'm > > running: > > > > JAVA_OPTS="-Djava.awt.headless=true > > -Dcom.sun.management.jmxremote.port=45219 > > -Dcom.sun.management.jmxremote.authenticate=false > > -Dcom.sun.management.jmxremote.ssl=false -Xmx2g > > -XX:+HeapDumpOnOutOfMemoryError > > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M > > -XX:MaxPermSize=800m > > > > On Mon, Mar 31, 2014 at 9:33 AM, Michael Phillips > > wrote: > > > So I have a redundant pair of management servers running on 4.2.1. At > > > least once a day one of the management servers crashes and the log gets > > > filled with the following messages: > > > java.lang.OutOfMemoryError: Java heap > > > spac0java.lang.ArrayIndexOutOfBoundsExceptioneCaused by: > > > java.io.EOFException: SSL peer shut down incorrectlyCaused by: > > > javax.net.ssl.SSLHandshakeException: Remote host closed connection > > > during handshake and there are a few others. When the one management > > > server tanks, although the other management server is up and active, > > > it won't actually process any UI commands until the crashed server > > > is restarted. Example of won't process any UI command is create a > > > new instance, create a new account, etc. After doing some searching > > > I have found that others have noticed java heap errors in 4.2.1, and > > > the suggested fix is to increase the heap size. I am planning on > > > increasing it from 2g to 4g, however if the problem is something > > > like a memory leak, then increasing the heap size will just delay > > > the inevitable. Has anyone else fixed this issue by increasing the > > > heap size? Or what is the recommended value? **updated...as expected > > > I increased the heap size from 2g to 4g, and it just too > > k longer for the problem to reoccur... > > > In my honest opinion of bigger concern is the fact that when one > > > management server crashes the other stops functioning as well. So this > > > begs the question of why even bother with a redundant pair of > > > servers..Anybody else experience this issue? I would love to hear any dev > > > guys opinion on this > > > > > >
RE: Interesting 4.2.1. Issue...
A few other articles also mention setting the initial heap size "-Xms" to the same value as the heap size, to go ahead and fully commit the heap. Have you tried that? One other thing I am curious of is have you fiddled with the Perm Size "XX:Permsize" setting? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Thu, 3 Apr 2014 09:26:31 +0800 > > Believe or not!! We have tried setting them in both formats and still the > catalina log produces java heap space error > > Kind Regards > Amin > > > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Thursday, 3 April 2014 9:24 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > This may be a silly question, but in all of the docs I am reading online in > regards to increasing the java heap size, they are specifying it as > -Xmx"size""MB" example -Xmx2048m vs -Xmx2g Is it possible that it's not > reading the 2g variable as 2GB? > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Thu, 3 Apr 2014 09:06:17 +0800 > > > > It is 6.0.35 and it still produces this error, even after increasing the > > Xmx to 4g, we have installed tomcat 6.0.33 and each time we install the > > cloudstack it does not sense the installed 6.0.33 and attempts to install > > 6.0.35 as it is dependent on it. Silly solution is that we scheduled a > > daily restart @ 2PM through a cron job But first you have to "killall > > jvsc" then restart the management server. > > > > What we are considering is to migrate the management server to CentOS 6.5 > > it comes with tomcat 6.0.24 and mysql 5.1, we attempted to restore the dump > > on a pilot environment and it worked. > > > > If someone else has a better solution than this would you please share it? > > > > Kind Regards > > Amin > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Thursday, 3 April 2014 5:31 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > So I just checked my tomcat version and we are running 6.0.35 which must be > > the default that comes with Ubuntu 12.04 out of the box. Our memory > > settings are as follows: > > JAVA_OPTS="-Djava.awt.headless=true > > -Dcom.sun.management.jmxremote.port=45219 > > -Dcom.sun.management.jmxremote.authenticate=false > > -Dcom.sun.management.jmxremote.ssl=false -Xmx4g > > -XX:+HeapDumpOnOutOfMemoryError > > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M > > -XX:MaxPermSize=800m" > > So what version of tomcat are you running 6.0.35 or 6.0.33? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Tue, 1 Apr 2014 11:23:57 +0800 > > > > > > We have the same issue, after an upgrade from 2.2.14 to 4.2.1, and > > > during this upgrade we had upgrade from Ubuntu 10 LTS to Ubuntu 12 > > > LTS, it seems it related to tomcat 6.0.35, because it is recommended > > > to have tomcat 6.0.33 which doesn't come by default with Ubuntu > > > 12.04.4 > > > > > > Kind Regards > > > Amin > > > > > > > > > > > > -Original Message- > > > From: Marcus [mailto:shadow...@gmail.com] > > > Sent: Tuesday, 1 April 2014 6:22 AM > > > To: dev@cloudstack.apache.org > > > Subject: Re: Interesting 4.2.1. Issue... > > > > > > I'm running 3 mgmt servers on 4.2.1, haven't seen any issues like > > > that. You can send along your memory settings... here's what I'm > > > running: > > > > > > JAVA_OPTS="-Djava.awt.headless=true > > > -Dcom.sun.management.jmxremote.port=45219 > > > -Dcom.sun.management.jmxremote.authenticate=false > > > -Dcom.sun.management.jmxremote.ssl=false -Xmx2g > > > -XX:+HeapDumpOnOutOfMemoryError > > > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M > > > -XX:MaxPermSize=800m > > > > > > On Mon, Mar 31, 2014 at 9:33 AM, Michael Phillips > > > wrote: > > > > So I have a redundant pair of management servers running on 4.2.1. At > > > > least once a day one of the management servers crashes and the
RE: Enabling VMware Support
You need to use the vsphere 5.1 SDK to build the nonoss > From: seiz...@infoblox.com > To: dev@cloudstack.apache.org > Subject: Enabling VMware Support > Date: Thu, 3 Apr 2014 21:15:15 + > > I was trying to bring up VMware Hypervisor, for the first time, mostly worked > with XenServer in the past. I have mostly 5.1 and 5.5 systems. I looked at > the Wiki: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hypervisor+VMWare > > Is this wiki still current? It is referencing the 4.1 SDK files to download > from VMware site and supported versions is 4.1 and 5.0. > -Soheil
RE: Interesting 4.2.1. Issue...
I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for the next few days to see if we get the error again. Do you know any way way to verify the version of tomcat that's running? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Thu, 3 Apr 2014 10:35:29 +0800 > > No we didn't, it wouldn't matter because the memory would still fill up, the > problem is it opens a thread and it fails to close it so whatever you will > increase soon or later the memory will fill up (if I understand right) > > The error in catalina is as follows: > > SEVERE: The web application [/client] created a ThreadLocal with key of type > [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1bd66d2d]) and a value > of type [com.cloud.api.SerializationContext] (value > [com.cloud.api.SerializationContext@2f6baed9]) but failed to remove it when > the web application was stopped. This is very likely to create a memory leak. > > If someone could help with this error generated in the catalina log, that > would be much appreicated. > > Kind Regards > Amin > > > > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Thursday, 3 April 2014 9:34 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > A few other articles also mention setting the initial heap size "-Xms" to the > same value as the heap size, to go ahead and fully commit the heap. Have you > tried that? > One other thing I am curious of is have you fiddled with the Perm Size > "XX:Permsize" setting? > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Thu, 3 Apr 2014 09:26:31 +0800 > > > > Believe or not!! We have tried setting them in both formats and still > > the catalina log produces java heap space error > > > > Kind Regards > > Amin > > > > > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Thursday, 3 April 2014 9:24 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > This may be a silly question, but in all of the docs I am reading online in > > regards to increasing the java heap size, they are specifying it as > > -Xmx"size""MB" example -Xmx2048m vs -Xmx2g Is it possible that it's not > > reading the 2g variable as 2GB? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Thu, 3 Apr 2014 09:06:17 +0800 > > > > > > It is 6.0.35 and it still produces this error, even after increasing the > > > Xmx to 4g, we have installed tomcat 6.0.33 and each time we install the > > > cloudstack it does not sense the installed 6.0.33 and attempts to install > > > 6.0.35 as it is dependent on it. Silly solution is that we scheduled a > > > daily restart @ 2PM through a cron job But first you have to "killall > > > jvsc" then restart the management server. > > > > > > What we are considering is to migrate the management server to CentOS 6.5 > > > it comes with tomcat 6.0.24 and mysql 5.1, we attempted to restore the > > > dump on a pilot environment and it worked. > > > > > > If someone else has a better solution than this would you please share it? > > > > > > Kind Regards > > > Amin > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Thursday, 3 April 2014 5:31 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > So I just checked my tomcat version and we are running 6.0.35 which must > > > be the default that comes with Ubuntu 12.04 out of the box. Our memory > > > settings are as follows: > > > JAVA_OPTS="-Djava.awt.headless=true > > > -Dcom.sun.management.jmxremote.port=45219 > > > -Dcom.sun.management.jmxremote.authenticate=false > > > -Dcom.sun.management.jmxremote.ssl=false -Xmx4g > > > -XX:+HeapDumpOnOutOfMemoryError > > > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M > > > -XX:MaxPermSize=800m" > > > So what version of tomcat are you running 6.0.35 or 6.0.33? > > > > > > > Subject: RE: Interesting
RE: Interesting 4.2.1. Issue...
So did you try changing your version of tomcat? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > cd /usr/share/tomcat6/bin/ > ./version.sh > > The output should be 6.0.33 instead of 6.0.35 > > Using CATALINA_BASE: /usr/share/tomcat6 > Using CATALINA_HOME: /usr/share/tomcat6 > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > Using JRE_HOME:/usr > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > Server version: Apache Tomcat/6.0.35 > Server built: > Server number: 6.0.35.0 > OS Name:Linux > OS Version: 3.11.0-18-generic > Architecture: amd64 > JVM Version:1.6.0_30-b30 > JVM Vendor: Sun Microsystems Inc. > > > Kind Regards > Amin > > > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Friday, 4 April 2014 10:31 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for the > next few days to see if we get the error again. > Do you know any way way to verify the version of tomcat that's running? > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Thu, 3 Apr 2014 10:35:29 +0800 > > > > No we didn't, it wouldn't matter because the memory would still fill > > up, the problem is it opens a thread and it fails to close it so > > whatever you will increase soon or later the memory will fill up (if I > > understand right) > > > > The error in catalina is as follows: > > > > SEVERE: The web application [/client] created a ThreadLocal with key of > > type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1bd66d2d]) and a > > value of type [com.cloud.api.SerializationContext] (value > > [com.cloud.api.SerializationContext@2f6baed9]) but failed to remove it when > > the web application was stopped. This is very likely to create a memory > > leak. > > > > If someone could help with this error generated in the catalina log, that > > would be much appreicated. > > > > Kind Regards > > Amin > > > > > > > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Thursday, 3 April 2014 9:34 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > A few other articles also mention setting the initial heap size "-Xms" to > > the same value as the heap size, to go ahead and fully commit the heap. > > Have you tried that? > > One other thing I am curious of is have you fiddled with the Perm Size > > "XX:Permsize" setting? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Thu, 3 Apr 2014 09:26:31 +0800 > > > > > > Believe or not!! We have tried setting them in both formats and > > > still the catalina log produces java heap space error > > > > > > Kind Regards > > > Amin > > > > > > > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Thursday, 3 April 2014 9:24 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > This may be a silly question, but in all of the docs I am reading online > > > in regards to increasing the java heap size, they are specifying it as > > > -Xmx"size""MB" example -Xmx2048m vs -Xmx2g Is it possible that it's not > > > reading the 2g variable as 2GB? > > > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > From: a...@opencloud.net.au > > > > To: dev@cloudstack.apache.org > > > > Date: Thu, 3 Apr 2014 09:06:17 +0800 > > > > > > > > It is 6.0.35 and it still produces this error, even after increasing > > > > the Xmx to 4g, we have installed tomcat 6.0.33 and each time we install > > > > the cloudstack it does not sense the installed 6.0.33 and attempts to > > > > install 6.0.35 as it is dependent on it. Silly solution is that we > > > > scheduled a daily restart @ 2PM through a cron job But first you > > > > have to "killall jvsc" then restart the
RE: Interesting 4.2.1. Issue...
So I manually downloaded tomcat 6.0.33 herehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment+on+Linux Then did the following1. extracted 6.0.33 to /usr/share/tomcat6.0.33. 2. Changed symlink of /usr/share/cloudstack-managemet/bin to /usr/share/tomcat6.0.33/bin3. Changed symlink of /usr/share/cloudstack-management/lib to /usr/share/tomcat6.0.33/lib4. Verified cloudstack was running tomcat 6.0.33 by creating a tomcat_version.jsp file in /usr/share/cloudstack-management/webapps/client code for tomcat_version.jsp can be found herehttp://stackoverflow.com/questions/14925073/how-to-find-out-running-tomcat-version I'll definitely let you know how it goes... > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Fri, 4 Apr 2014 10:43:35 +0800 > > I tried but I failed to do so, each time cloudstack attempts to install to go > fetches the 6.0.35 from the repo, maybe you have installed it after > installing the cloudstack, if you managed to have a running cloudstack > version above the 6.0.33 feedback with the results. > > Kind Regards > Amin > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Friday, 4 April 2014 10:41 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > So did you try changing your version of tomcat? > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > > > cd /usr/share/tomcat6/bin/ > > ./version.sh > > > > The output should be 6.0.33 instead of 6.0.35 > > > > Using CATALINA_BASE: /usr/share/tomcat6 > > Using CATALINA_HOME: /usr/share/tomcat6 > > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > > Using JRE_HOME:/usr > > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > > Server version: Apache Tomcat/6.0.35 > > Server built: > > Server number: 6.0.35.0 > > OS Name:Linux > > OS Version: 3.11.0-18-generic > > Architecture: amd64 > > JVM Version:1.6.0_30-b30 > > JVM Vendor: Sun Microsystems Inc. > > > > > > Kind Regards > > Amin > > > > > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Friday, 4 April 2014 10:31 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for the > > next few days to see if we get the error again. > > Do you know any way way to verify the version of tomcat that's running? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Thu, 3 Apr 2014 10:35:29 +0800 > > > > > > No we didn't, it wouldn't matter because the memory would still fill > > > up, the problem is it opens a thread and it fails to close it so > > > whatever you will increase soon or later the memory will fill up (if > > > I understand right) > > > > > > The error in catalina is as follows: > > > > > > SEVERE: The web application [/client] created a ThreadLocal with key of > > > type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1bd66d2d]) and > > > a value of type [com.cloud.api.SerializationContext] (value > > > [com.cloud.api.SerializationContext@2f6baed9]) but failed to remove it > > > when the web application was stopped. This is very likely to create a > > > memory leak. > > > > > > If someone could help with this error generated in the catalina log, that > > > would be much appreicated. > > > > > > Kind Regards > > > Amin > > > > > > > > > > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Thursday, 3 April 2014 9:34 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > A few other articles also mention setting the initial heap size "-Xms" to > > > the same value as the heap size, to go ahead and fully commit the heap. > > > Have you tried that? > > > One other thing I am curious of is have you fiddled with the Perm Size > > > "XX:Permsize" setting? > > > > > > > Sub
RE: Interesting 4.2.1. Issue...
No problem. CS is at least running on tomcat 6.0.33 so that's good news. :) > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Fri, 4 Apr 2014 11:10:28 +0800 > > Thanks and thanks for sharing the steps > > Kind Regards > Amin > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Friday, 4 April 2014 11:02 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > So I manually downloaded tomcat 6.0.33 > herehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment+on+Linux > Then did the following1. extracted 6.0.33 to /usr/share/tomcat6.0.33. 2. > Changed symlink of /usr/share/cloudstack-managemet/bin to > /usr/share/tomcat6.0.33/bin3. Changed symlink of > /usr/share/cloudstack-management/lib to /usr/share/tomcat6.0.33/lib4. > Verified cloudstack was running tomcat 6.0.33 by creating a > tomcat_version.jsp file in /usr/share/cloudstack-management/webapps/client > code for tomcat_version.jsp can be found > herehttp://stackoverflow.com/questions/14925073/how-to-find-out-running-tomcat-version > I'll definitely let you know how it goes... > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Fri, 4 Apr 2014 10:43:35 +0800 > > > > I tried but I failed to do so, each time cloudstack attempts to install to > > go fetches the 6.0.35 from the repo, maybe you have installed it after > > installing the cloudstack, if you managed to have a running cloudstack > > version above the 6.0.33 feedback with the results. > > > > Kind Regards > > Amin > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Friday, 4 April 2014 10:41 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > So did you try changing your version of tomcat? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > > > > > cd /usr/share/tomcat6/bin/ > > > ./version.sh > > > > > > The output should be 6.0.33 instead of 6.0.35 > > > > > > Using CATALINA_BASE: /usr/share/tomcat6 > > > Using CATALINA_HOME: /usr/share/tomcat6 > > > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > > > Using JRE_HOME:/usr > > > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > > > Server version: Apache Tomcat/6.0.35 > > > Server built: > > > Server number: 6.0.35.0 > > > OS Name:Linux > > > OS Version: 3.11.0-18-generic > > > Architecture: amd64 > > > JVM Version:1.6.0_30-b30 > > > JVM Vendor: Sun Microsystems Inc. > > > > > > > > > Kind Regards > > > Amin > > > > > > > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Friday, 4 April 2014 10:31 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for > > > the next few days to see if we get the error again. > > > Do you know any way way to verify the version of tomcat that's running? > > > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > From: a...@opencloud.net.au > > > > To: dev@cloudstack.apache.org > > > > Date: Thu, 3 Apr 2014 10:35:29 +0800 > > > > > > > > No we didn't, it wouldn't matter because the memory would still > > > > fill up, the problem is it opens a thread and it fails to close it > > > > so whatever you will increase soon or later the memory will fill > > > > up (if I understand right) > > > > > > > > The error in catalina is as follows: > > > > > > > > SEVERE: The web application [/client] created a ThreadLocal with key of > > > > type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1bd66d2d]) > > > > and a value of type [com.cloud.api.SerializationContext] (value > > > > [com.cloud.api.SerializationContext@2f6baed9]) but failed to remove it > > > > when the web application was st
RE: Interesting 4.2.1. Issue...
So far so good :) > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Fri, 4 Apr 2014 11:10:28 +0800 > > Thanks and thanks for sharing the steps > > Kind Regards > Amin > > -----Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Friday, 4 April 2014 11:02 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > So I manually downloaded tomcat 6.0.33 > herehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment+on+Linux > Then did the following1. extracted 6.0.33 to /usr/share/tomcat6.0.33. 2. > Changed symlink of /usr/share/cloudstack-managemet/bin to > /usr/share/tomcat6.0.33/bin3. Changed symlink of > /usr/share/cloudstack-management/lib to /usr/share/tomcat6.0.33/lib4. > Verified cloudstack was running tomcat 6.0.33 by creating a > tomcat_version.jsp file in /usr/share/cloudstack-management/webapps/client > code for tomcat_version.jsp can be found > herehttp://stackoverflow.com/questions/14925073/how-to-find-out-running-tomcat-version > I'll definitely let you know how it goes... > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Fri, 4 Apr 2014 10:43:35 +0800 > > > > I tried but I failed to do so, each time cloudstack attempts to install to > > go fetches the 6.0.35 from the repo, maybe you have installed it after > > installing the cloudstack, if you managed to have a running cloudstack > > version above the 6.0.33 feedback with the results. > > > > Kind Regards > > Amin > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Friday, 4 April 2014 10:41 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > So did you try changing your version of tomcat? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > > > > > cd /usr/share/tomcat6/bin/ > > > ./version.sh > > > > > > The output should be 6.0.33 instead of 6.0.35 > > > > > > Using CATALINA_BASE: /usr/share/tomcat6 > > > Using CATALINA_HOME: /usr/share/tomcat6 > > > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > > > Using JRE_HOME:/usr > > > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > > > Server version: Apache Tomcat/6.0.35 > > > Server built: > > > Server number: 6.0.35.0 > > > OS Name:Linux > > > OS Version: 3.11.0-18-generic > > > Architecture: amd64 > > > JVM Version:1.6.0_30-b30 > > > JVM Vendor: Sun Microsystems Inc. > > > > > > > > > Kind Regards > > > Amin > > > > > > > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Friday, 4 April 2014 10:31 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for > > > the next few days to see if we get the error again. > > > Do you know any way way to verify the version of tomcat that's running? > > > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > From: a...@opencloud.net.au > > > > To: dev@cloudstack.apache.org > > > > Date: Thu, 3 Apr 2014 10:35:29 +0800 > > > > > > > > No we didn't, it wouldn't matter because the memory would still > > > > fill up, the problem is it opens a thread and it fails to close it > > > > so whatever you will increase soon or later the memory will fill > > > > up (if I understand right) > > > > > > > > The error in catalina is as follows: > > > > > > > > SEVERE: The web application [/client] created a ThreadLocal with key of > > > > type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1bd66d2d]) > > > > and a value of type [com.cloud.api.SerializationContext] (value > > > > [com.cloud.api.SerializationContext@2f6baed9]) but failed to remove it > > > > when the web application was stopped. This is very likely to create a > > > > memory leak. > > &
RE: Interesting 4.2.1. Issue...
Took about 2 days, but the heap space issue has re-occurred. ...sigh... So switching to tomcat 6.0.33 had zero effect.. Anyone else have any ideas?? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Fri, 4 Apr 2014 11:10:28 +0800 > > Thanks and thanks for sharing the steps > > Kind Regards > Amin > > -----Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Friday, 4 April 2014 11:02 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > So I manually downloaded tomcat 6.0.33 > herehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment+on+Linux > Then did the following1. extracted 6.0.33 to /usr/share/tomcat6.0.33. 2. > Changed symlink of /usr/share/cloudstack-managemet/bin to > /usr/share/tomcat6.0.33/bin3. Changed symlink of > /usr/share/cloudstack-management/lib to /usr/share/tomcat6.0.33/lib4. > Verified cloudstack was running tomcat 6.0.33 by creating a > tomcat_version.jsp file in /usr/share/cloudstack-management/webapps/client > code for tomcat_version.jsp can be found > herehttp://stackoverflow.com/questions/14925073/how-to-find-out-running-tomcat-version > I'll definitely let you know how it goes... > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Fri, 4 Apr 2014 10:43:35 +0800 > > > > I tried but I failed to do so, each time cloudstack attempts to install to > > go fetches the 6.0.35 from the repo, maybe you have installed it after > > installing the cloudstack, if you managed to have a running cloudstack > > version above the 6.0.33 feedback with the results. > > > > Kind Regards > > Amin > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Friday, 4 April 2014 10:41 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > So did you try changing your version of tomcat? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > > > > > cd /usr/share/tomcat6/bin/ > > > ./version.sh > > > > > > The output should be 6.0.33 instead of 6.0.35 > > > > > > Using CATALINA_BASE: /usr/share/tomcat6 > > > Using CATALINA_HOME: /usr/share/tomcat6 > > > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > > > Using JRE_HOME:/usr > > > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > > > Server version: Apache Tomcat/6.0.35 > > > Server built: > > > Server number: 6.0.35.0 > > > OS Name:Linux > > > OS Version: 3.11.0-18-generic > > > Architecture: amd64 > > > JVM Version:1.6.0_30-b30 > > > JVM Vendor: Sun Microsystems Inc. > > > > > > > > > Kind Regards > > > Amin > > > > > > > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Friday, 4 April 2014 10:31 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for > > > the next few days to see if we get the error again. > > > Do you know any way way to verify the version of tomcat that's running? > > > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > From: a...@opencloud.net.au > > > > To: dev@cloudstack.apache.org > > > > Date: Thu, 3 Apr 2014 10:35:29 +0800 > > > > > > > > No we didn't, it wouldn't matter because the memory would still > > > > fill up, the problem is it opens a thread and it fails to close it > > > > so whatever you will increase soon or later the memory will fill > > > > up (if I understand right) > > > > > > > > The error in catalina is as follows: > > > > > > > > SEVERE: The web application [/client] created a ThreadLocal with key of > > > > type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1bd66d2d]) > > > > and a value of type [com.cloud.api.SerializationContext] (value > > > > [com.cloud.api.SerializationContext@2f6baed9]) but failed to remove it > &
Remove Mgmt Server
Hey dev guys, what's the proper way to remove a management server from a management server cluster? I am referring to the actual management servers and not the hypervisors
cloudmanagementserver.keystore
I know this was a problem in 4.2.1 in which the system would endlessly log the following error: 014-04-07 22:29:29,715 WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL: Fail to find the generated keystore. Loading fail-safe one to continue. The fix was to rename /etc/cloudstack/management/cloudmanagementserver.keystore, to cloud.keystore then restart cloudstack. I just installed 4.3.0 fresh, and it seems like this problem persists with a twist. The system now does not create any keystore file and logs the following 3 errors. Executing: sudo keytool -genkey -keystore /etc/cloudstack/management/cloudmanagementserver.keystore -storepass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn="Cloudstack User",ou="ustxdalcstackwebp1.cloudagy.local",o="ustxdalcstackwebp1.cloudagy.local",c="Unknown" 2014-04-07 21:31:53,610 DEBUG [c.c.u.s.Script] (main:null) Exit value is 12014-04-07 21:31:53,610 DEBUG [c.c.u.s.Script] (main:null) sudo: no tty present and no askpass program specified My fix was to run the above command "keytool..." from the command line, then rename the file to cloud.keystore. Once I did that it stopped logging the "SSL: Fail to find the generated keystore" errors. Can anyone else confirm they saw this behavior in 4.3.0? If so I can make a bug report in JIRA..
4.3.0 vmware
All, has anything changed with the procedures to build the noredist code for 4.3.0? The reason I ask is because I just built from source using -Dnoredist and when trying to add a vmware datacenter I get the following error: Unknown API command: addVmwareDc In the past this error occurred if the source did not include the noredist code. I went back and built from source again to verify and the build success said "Vmware Hypervisor" Success..
RE: 4.3.0 vmware
I did just "mvn install -Dnoredist" That should work correct? According to the output log it did. > From: kelven.y...@citrix.com > To: dev@cloudstack.apache.org > Subject: Re: 4.3.0 vmware > Date: Tue, 8 Apr 2014 16:43:37 + > > If you start from maven command line. you need to define noredist as well, > as following example > > mvn -Dnoredist -pl client jetty:run > > Kelven > > On 4/8/14, 9:30 AM, "Michael Phillips" wrote: > > >All, has anything changed with the procedures to build the noredist code > >for 4.3.0? > >The reason I ask is because I just built from source using -Dnoredist and > >when trying to add a vmware datacenter I get the following error: > >Unknown API command: addVmwareDc > >In the past this error occurred if the source did not include the > >noredist code. I went back and built from source again to verify and the > >build success said "Vmware Hypervisor" Success.. > > > > >
RE: 4.3.0 vmware
So your referring to actually launching the cloudstack-management services? > From: kelven.y...@citrix.com > To: dev@cloudstack.apache.org > Subject: Re: 4.3.0 vmware > Date: Tue, 8 Apr 2014 17:00:44 + > > mvn install command only runs command to build and install the artifacts > into maven repo. > > If you launch management server using maven, you need to -Dnoredist option > as you do in build. > > Kelven > > On 4/8/14, 9:46 AM, "Michael Phillips" wrote: > > >I did just "mvn install -Dnoredist" > >That should work correct? According to the output log it did. > > > >> From: kelven.y...@citrix.com > >> To: dev@cloudstack.apache.org > >> Subject: Re: 4.3.0 vmware > >> Date: Tue, 8 Apr 2014 16:43:37 + > >> > >> If you start from maven command line. you need to define noredist as > >>well, > >> as following example > >> > >> mvn -Dnoredist -pl client jetty:run > >> > >> Kelven > >> > >> On 4/8/14, 9:30 AM, "Michael Phillips" wrote: > >> > >> >All, has anything changed with the procedures to build the noredist > >>code > >> >for 4.3.0? > >> >The reason I ask is because I just built from source using -Dnoredist > >>and > >> >when trying to add a vmware datacenter I get the following error: > >> >Unknown API command: addVmwareDc > >> >In the past this error occurred if the source did not include the > >> >noredist code. I went back and built from source again to verify and > >>the > >> >build success said "Vmware Hypervisor" Success.. > >> > > >> > > >> > > >
RE: Interesting 4.2.1. Issue...
Amin, Any luck on your project taking your 3 mgmt servers to 4.3 on Centos 6.5? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Fri, 4 Apr 2014 11:10:28 +0800 > > Thanks and thanks for sharing the steps > > Kind Regards > Amin > > -----Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Friday, 4 April 2014 11:02 AM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > So I manually downloaded tomcat 6.0.33 > herehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment+on+Linux > Then did the following1. extracted 6.0.33 to /usr/share/tomcat6.0.33. 2. > Changed symlink of /usr/share/cloudstack-managemet/bin to > /usr/share/tomcat6.0.33/bin3. Changed symlink of > /usr/share/cloudstack-management/lib to /usr/share/tomcat6.0.33/lib4. > Verified cloudstack was running tomcat 6.0.33 by creating a > tomcat_version.jsp file in /usr/share/cloudstack-management/webapps/client > code for tomcat_version.jsp can be found > herehttp://stackoverflow.com/questions/14925073/how-to-find-out-running-tomcat-version > I'll definitely let you know how it goes... > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Fri, 4 Apr 2014 10:43:35 +0800 > > > > I tried but I failed to do so, each time cloudstack attempts to install to > > go fetches the 6.0.35 from the repo, maybe you have installed it after > > installing the cloudstack, if you managed to have a running cloudstack > > version above the 6.0.33 feedback with the results. > > > > Kind Regards > > Amin > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Friday, 4 April 2014 10:41 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > So did you try changing your version of tomcat? > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > > > > > cd /usr/share/tomcat6/bin/ > > > ./version.sh > > > > > > The output should be 6.0.33 instead of 6.0.35 > > > > > > Using CATALINA_BASE: /usr/share/tomcat6 > > > Using CATALINA_HOME: /usr/share/tomcat6 > > > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > > > Using JRE_HOME:/usr > > > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > > > Server version: Apache Tomcat/6.0.35 > > > Server built: > > > Server number: 6.0.35.0 > > > OS Name:Linux > > > OS Version: 3.11.0-18-generic > > > Architecture: amd64 > > > JVM Version:1.6.0_30-b30 > > > JVM Vendor: Sun Microsystems Inc. > > > > > > > > > Kind Regards > > > Amin > > > > > > > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Friday, 4 April 2014 10:31 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for > > > the next few days to see if we get the error again. > > > Do you know any way way to verify the version of tomcat that's running? > > > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > From: a...@opencloud.net.au > > > > To: dev@cloudstack.apache.org > > > > Date: Thu, 3 Apr 2014 10:35:29 +0800 > > > > > > > > No we didn't, it wouldn't matter because the memory would still > > > > fill up, the problem is it opens a thread and it fails to close it > > > > so whatever you will increase soon or later the memory will fill > > > > up (if I understand right) > > > > > > > > The error in catalina is as follows: > > > > > > > > SEVERE: The web application [/client] created a ThreadLocal with key of > > > > type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1bd66d2d]) > > > > and a value of type [com.cloud.api.SerializationContext] (value > > > > [com.cloud.api.SerializationContext@2f6baed9]) but failed to remove it > > > > when the web application was stopped
RE: Remove Mgmt Server
One be nice to see an option in the UI to cleanly remove a management server. Thoughts? > Date: Tue, 8 Apr 2014 21:38:29 -0300 > Subject: Re: Remove Mgmt Server > From: rafaelweingart...@gmail.com > To: dev@cloudstack.apache.org > > I prefer to set the removed field to some data that represents the time > when the server was removed. This way when a new management server gets up > it does not waste time checking if some other server is up. > > > On Tue, Apr 8, 2014 at 1:58 PM, Kelven Yang wrote: > > > Just by stopping the running management server would do it already. no > > further action is mandatory, however, if you prefer a complete clean, > > login into DB and remove the corresponding record in mshost table > > > > Kelven > > > > On 4/5/14, 10:32 AM, "Michael Phillips" wrote: > > > > >Hey dev guys, what's the proper way to remove a management server from a > > >management server cluster? > > >I am referring to the actual management servers and not the > > >hypervisors > > > > > > > -- > Rafael Weingärtner
RE: cloudmanagementserver.keystore
I created a bug report for this. https://issues.apache.org/jira/browse/CLOUDSTACK-6378 > From: prashanthreddy.mand...@citrix.com > To: dev@cloudstack.apache.org > Subject: RE: cloudmanagementserver.keystore > Date: Tue, 8 Apr 2014 05:49:49 + > > I have seen this issue on fresh installation of 4.3. > > Snippet of the log from my setup > > "2014-04-07 08:00:09,295 INFO [c.c.s.ConfigurationServerImpl] (main:null) > SSL keystore located at > /etc/cloudstack/management/cloudmanagementserver.keystore > 2014-04-07 08:00:09,304 DEBUG [c.c.u.s.Script] (main:null) Executing: sudo > keytool -genkey -keystore > /etc/cloudstack/management/cloudmanagementserver.keystore -storepass > vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn="Cloudstack > User",ou="repro. cloud.internal",o="repro. cloud.internal",c="Unknown" > 2014-04-07 08:00:09,438 DEBUG [c.c.u.s.Script] (main:null) Exit value is 1 > 2014-04-07 08:00:09,441 DEBUG [c.c.u.s.Script] (main:null) sudo: no tty > present and no askpass program specified > 2014-04-07 08:00:09,445 WARN [c.c.s.ConfigurationServerImpl] (main:null) > Would use fail-safe keystore to continue. > java.io.IOException: Fail to generate certificate!: sudo: no tty present and > no askpass program specified" > > > Thanks, > Prashanth > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Tuesday, April 08, 2014 9:27 AM > To: dev@cloudstack.apache.org > Subject: cloudmanagementserver.keystore > > I know this was a problem in 4.2.1 in which the system would endlessly log > the following error: > 014-04-07 22:29:29,715 WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL: > Fail to find the generated keystore. Loading fail-safe one to continue. > The fix was to rename > /etc/cloudstack/management/cloudmanagementserver.keystore, to cloud.keystore > then restart cloudstack. > I just installed 4.3.0 fresh, and it seems like this problem persists with a > twist. The system now does not create any keystore file and logs the > following 3 errors. > Executing: sudo keytool -genkey -keystore > /etc/cloudstack/management/cloudmanagementserver.keystore -storepass > vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn="Cloudstack > User",ou="ustxdalcstackwebp1.cloudagy.local",o="ustxdalcstackwebp1.cloudagy.local",c="Unknown" > 2014-04-07 21:31:53,610 DEBUG [c.c.u.s.Script] (main:null) Exit value is > 12014-04-07 21:31:53,610 DEBUG [c.c.u.s.Script] (main:null) sudo: no tty > present and no askpass program specified My fix was to run the above command > "keytool..." from the command line, then rename the file to cloud.keystore. > Once I did that it stopped logging the "SSL: Fail to find the generated > keystore" errors. Can anyone else confirm they saw this behavior in 4.3.0? If > so I can make a bug report in JIRA.. >
RE: Remove Mgmt Server
+1 on those steps. > From: alex.hu...@citrix.com > To: dev@cloudstack.apache.org > Subject: RE: Remove Mgmt Server > Date: Thu, 10 Apr 2014 23:47:57 + > > Sorry. I meant it should be like maintenance state. Somehow pulled a brain > fart and mixed up the two sets of states. > > Put the mgmtserver into maintenance -> moves into prepare for maintenance. > This means the mgmtserver stops taking new jobs and prepares to hand off all > agents and just wait for existing jobs to finish. > > When all jobs are done, state goes to maintenance and mgmt server can be > shutdown. > If there are any problems with the agent handoffs and/or jobs waiting to the > done then it goes into error in maintenance. Admin can inspect and decide > to shutoff or put it into maintenance again after fixing the problems. > > --Alex > > > -Original Message- > > From: Alex Huang [mailto:alex.hu...@citrix.com] > > Sent: Thursday, April 10, 2014 4:41 PM > > To: dev@cloudstack.apache.org > > Subject: RE: Remove Mgmt Server > > > > +1 > > > > It should be similar to how our resources have states: > > enable/disable/inactive. Enable means the mgmt server node is enabled. > > Inactive means it shouldn't be serving new requests (in this case handle new > > jobs). Disable means the mgmt. server is ready to be taken down because all > > jobs it is executing are done and all agent connections are transferred to > > another mgmt. server. At that point someone can just shut off the mgmt. > > server. This would be an orderly way to shutdown the mgmt. server. > > > > --Alex > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Thursday, April 10, 2014 8:12 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Remove Mgmt Server > > > > > > One be nice to see an option in the UI to cleanly remove a management > > > server. > > > Thoughts? > > > > > > > Date: Tue, 8 Apr 2014 21:38:29 -0300 > > > > Subject: Re: Remove Mgmt Server > > > > From: rafaelweingart...@gmail.com > > > > To: dev@cloudstack.apache.org > > > > > > > > I prefer to set the removed field to some data that represents the > > > > time when the server was removed. This way when a new management > > > > server gets up it does not waste time checking if some other server is > > > > up. > > > > > > > > > > > > On Tue, Apr 8, 2014 at 1:58 PM, Kelven Yang > > > wrote: > > > > > > > > > Just by stopping the running management server would do it already. > > > > > no further action is mandatory, however, if you prefer a complete > > > > > clean, login into DB and remove the corresponding record in mshost > > > > > table > > > > > > > > > > Kelven > > > > > > > > > > On 4/5/14, 10:32 AM, "Michael Phillips" > > > wrote: > > > > > > > > > > >Hey dev guys, what's the proper way to remove a management server > > > > > >from a management server cluster? > > > > > >I am referring to the actual management servers and not the > > > > > >hypervisors > > > > > > > > > > > > > > > > > > > > > > -- > > > > Rafael Weingärtner > > >
RE: Remove Mgmt Server
I can create a JIRA request for this, but how many +1's do we need before it gets added to the "To Do" list? > From: alex.hu...@citrix.com > To: dev@cloudstack.apache.org > Subject: RE: Remove Mgmt Server > Date: Thu, 10 Apr 2014 23:47:57 + > > Sorry. I meant it should be like maintenance state. Somehow pulled a brain > fart and mixed up the two sets of states. > > Put the mgmtserver into maintenance -> moves into prepare for maintenance. > This means the mgmtserver stops taking new jobs and prepares to hand off all > agents and just wait for existing jobs to finish. > > When all jobs are done, state goes to maintenance and mgmt server can be > shutdown. > If there are any problems with the agent handoffs and/or jobs waiting to the > done then it goes into error in maintenance. Admin can inspect and decide > to shutoff or put it into maintenance again after fixing the problems. > > --Alex > > > -Original Message- > > From: Alex Huang [mailto:alex.hu...@citrix.com] > > Sent: Thursday, April 10, 2014 4:41 PM > > To: dev@cloudstack.apache.org > > Subject: RE: Remove Mgmt Server > > > > +1 > > > > It should be similar to how our resources have states: > > enable/disable/inactive. Enable means the mgmt server node is enabled. > > Inactive means it shouldn't be serving new requests (in this case handle new > > jobs). Disable means the mgmt. server is ready to be taken down because all > > jobs it is executing are done and all agent connections are transferred to > > another mgmt. server. At that point someone can just shut off the mgmt. > > server. This would be an orderly way to shutdown the mgmt. server. > > > > --Alex > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Thursday, April 10, 2014 8:12 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Remove Mgmt Server > > > > > > One be nice to see an option in the UI to cleanly remove a management > > > server. > > > Thoughts? > > > > > > > Date: Tue, 8 Apr 2014 21:38:29 -0300 > > > > Subject: Re: Remove Mgmt Server > > > > From: rafaelweingart...@gmail.com > > > > To: dev@cloudstack.apache.org > > > > > > > > I prefer to set the removed field to some data that represents the > > > > time when the server was removed. This way when a new management > > > > server gets up it does not waste time checking if some other server is > > > > up. > > > > > > > > > > > > On Tue, Apr 8, 2014 at 1:58 PM, Kelven Yang > > > wrote: > > > > > > > > > Just by stopping the running management server would do it already. > > > > > no further action is mandatory, however, if you prefer a complete > > > > > clean, login into DB and remove the corresponding record in mshost > > > > > table > > > > > > > > > > Kelven > > > > > > > > > > On 4/5/14, 10:32 AM, "Michael Phillips" > > > wrote: > > > > > > > > > > >Hey dev guys, what's the proper way to remove a management server > > > > > >from a management server cluster? > > > > > >I am referring to the actual management servers and not the > > > > > >hypervisors > > > > > > > > > > > > > > > > > > > > > > -- > > > > Rafael Weingärtner > > >
RE: Interesting 4.2.1. Issue...
Gotcha... What hypervisor are you using with CS? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Fri, 11 Apr 2014 09:05:29 +0800 > > Michael, > Just give me two days, will feedback you. I have to leave it till late night > where is the Ubuntu server crash times. > > Kind Regards > Amin > > -----Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Thursday, 10 April 2014 11:10 PM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > Amin, >Any luck on your project taking your 3 mgmt servers to 4.3 on Centos 6.5? > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Fri, 4 Apr 2014 11:10:28 +0800 > > > > Thanks and thanks for sharing the steps > > > > Kind Regards > > Amin > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Friday, 4 April 2014 11:02 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > So I manually downloaded tomcat 6.0.33 > > herehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+ > > CloudStack+Development+Environment+on+Linux > > Then did the following1. extracted 6.0.33 to /usr/share/tomcat6.0.33. > > 2. Changed symlink of /usr/share/cloudstack-managemet/bin to > > /usr/share/tomcat6.0.33/bin3. Changed symlink of > > /usr/share/cloudstack-management/lib to /usr/share/tomcat6.0.33/lib4. > > Verified cloudstack was running tomcat 6.0.33 by creating a > > tomcat_version.jsp file in > > /usr/share/cloudstack-management/webapps/client > > code for tomcat_version.jsp can be found > > herehttp://stackoverflow.com/questions/14925073/how-to-find-out-runnin > > g-tomcat-version I'll definitely let you know how it goes... > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Fri, 4 Apr 2014 10:43:35 +0800 > > > > > > I tried but I failed to do so, each time cloudstack attempts to install > > > to go fetches the 6.0.35 from the repo, maybe you have installed it after > > > installing the cloudstack, if you managed to have a running cloudstack > > > version above the 6.0.33 feedback with the results. > > > > > > Kind Regards > > > Amin > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Friday, 4 April 2014 10:41 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > So did you try changing your version of tomcat? > > > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > From: a...@opencloud.net.au > > > > To: dev@cloudstack.apache.org > > > > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > > > > > > > cd /usr/share/tomcat6/bin/ > > > > ./version.sh > > > > > > > > The output should be 6.0.33 instead of 6.0.35 > > > > > > > > Using CATALINA_BASE: /usr/share/tomcat6 > > > > Using CATALINA_HOME: /usr/share/tomcat6 > > > > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > > > > Using JRE_HOME:/usr > > > > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > > > > Server version: Apache Tomcat/6.0.35 > > > > Server built: > > > > Server number: 6.0.35.0 > > > > OS Name:Linux > > > > OS Version: 3.11.0-18-generic > > > > Architecture: amd64 > > > > JVM Version:1.6.0_30-b30 > > > > JVM Vendor: Sun Microsystems Inc. > > > > > > > > > > > > Kind Regards > > > > Amin > > > > > > > > > > > > > > > > -Original Message- > > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > > Sent: Friday, 4 April 2014 10:31 AM > > > > To: dev@cloudstack.apache.org > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > > > I've put tomcat 6.0.33 on our mgmt servers. I'm going to monitor it for > > > > the next few days to see if we get the error again. > > > > Do you know any way way to verify the version of tomcat that's running? >
RE: Interesting 4.2.1. Issue...
Excellent news! Quick question. I tried using centos 6.5 with 4.2.1, however after installing I could never log in with the default username\password combo of admin\password. Did you experience that? > Subject: RE: Interesting 4.2.1. Issue... > From: a...@opencloud.net.au > To: dev@cloudstack.apache.org > Date: Mon, 14 Apr 2014 10:08:16 +0800 > > Hi Michael, > > For whole three days now we have been using CentOS 6.5 as OS platform for our > management server, and no signs of crashes nor did we need have to restart on > a daily basis. > > No signs of java heap space errors neither in the Catalina.out nor in > management.log. > > The environment in detail as follows: > 1) Management server operating system CentOs 6.5 (updated as of 9th of April). > 2) CloudStack Management version 4.2.1. > 3) The default Tomcat version that comes with CentOs 6.5 is (6.0.24) > 3) Primary & Secondary Storage server Ubuntu12.04 LTS (NFS Service) > 4) Hypervisors Xen Server 6.1 update with the latest patches as of today 14th > April. > > If we come through any issues will sure keep you updated. > > Kind Regards > Amin > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Thursday, 10 April 2014 11:10 PM > To: dev@cloudstack.apache.org > Subject: RE: Interesting 4.2.1. Issue... > > Amin, >Any luck on your project taking your 3 mgmt servers to 4.3 on Centos 6.5? > > > Subject: RE: Interesting 4.2.1. Issue... > > From: a...@opencloud.net.au > > To: dev@cloudstack.apache.org > > Date: Fri, 4 Apr 2014 11:10:28 +0800 > > > > Thanks and thanks for sharing the steps > > > > Kind Regards > > Amin > > > > -Original Message- > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > Sent: Friday, 4 April 2014 11:02 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Interesting 4.2.1. Issue... > > > > So I manually downloaded tomcat 6.0.33 > > herehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+ > > CloudStack+Development+Environment+on+Linux > > Then did the following1. extracted 6.0.33 to /usr/share/tomcat6.0.33. > > 2. Changed symlink of /usr/share/cloudstack-managemet/bin to > > /usr/share/tomcat6.0.33/bin3. Changed symlink of > > /usr/share/cloudstack-management/lib to /usr/share/tomcat6.0.33/lib4. > > Verified cloudstack was running tomcat 6.0.33 by creating a > > tomcat_version.jsp file in > > /usr/share/cloudstack-management/webapps/client > > code for tomcat_version.jsp can be found > > herehttp://stackoverflow.com/questions/14925073/how-to-find-out-runnin > > g-tomcat-version I'll definitely let you know how it goes... > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > From: a...@opencloud.net.au > > > To: dev@cloudstack.apache.org > > > Date: Fri, 4 Apr 2014 10:43:35 +0800 > > > > > > I tried but I failed to do so, each time cloudstack attempts to install > > > to go fetches the 6.0.35 from the repo, maybe you have installed it after > > > installing the cloudstack, if you managed to have a running cloudstack > > > version above the 6.0.33 feedback with the results. > > > > > > Kind Regards > > > Amin > > > > > > -Original Message- > > > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > > > Sent: Friday, 4 April 2014 10:41 AM > > > To: dev@cloudstack.apache.org > > > Subject: RE: Interesting 4.2.1. Issue... > > > > > > So did you try changing your version of tomcat? > > > > > > > Subject: RE: Interesting 4.2.1. Issue... > > > > From: a...@opencloud.net.au > > > > To: dev@cloudstack.apache.org > > > > Date: Fri, 4 Apr 2014 10:35:42 +0800 > > > > > > > > cd /usr/share/tomcat6/bin/ > > > > ./version.sh > > > > > > > > The output should be 6.0.33 instead of 6.0.35 > > > > > > > > Using CATALINA_BASE: /usr/share/tomcat6 > > > > Using CATALINA_HOME: /usr/share/tomcat6 > > > > Using CATALINA_TMPDIR: /usr/share/tomcat6/temp > > > > Using JRE_HOME:/usr > > > > Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar > > > > Server version: Apache Tomcat/6.0.35 > > > > Server built: > > > > Server number: 6.0.35.0 > > > > OS Name:Linux > > > > OS Version: 3.11.0-18-generic > > > > Architecture: amd64 > > > > JVM Version:
RE: interactions Cloudstack Vmware
I did a trace the other day to open the correct ports from cloudstack to vcenter, and I found the mgmt servers and systems vm's talking to vcenter over 443 only... > Date: Mon, 14 Apr 2014 18:17:12 +0100 > Subject: Re: interactions Cloudstack Vmware > From: saidi.mohamed.ali...@gmail.com > To: dev@cloudstack.apache.org > > thank you for informations. > > Exactly i would like to know what protocol vcenter uses to send reponse to > cloudstack. > Cloudstack send requests via https but reponse is it on https too? > > Regards > > > 2014-04-14 17:28 GMT+01:00 ilya musayev : > > > Interaction happens on several layers. > > > > Using VMware SDK, CloudStack Management Server initially talks to vCenter > > over 443. However, you will also see some interaction between Storage VM as > > well as Proxy VM to vCenter and ESXi hosts directly. > > > > Are you experiencing any issues or is this for firewall/security review? > > > > If you are attempting to troubleshoot the issue, the easiest way is to > > look at the logs as well as "netstat -antup | grep -i time", look for all > > unestablished connections to see where the flow goes and what needs to be > > open. I do have a doc on communication flow, it may take a week or little > > longer for me to post it online, since it is on one of the hard drives @ > > work, and i'm working remotely this week. > > > > If you need any help in the meantime, let me know, > > > > Regards > > ilya > > > > > > On 4/9/14, 7:52 AM, Mohamed Ali Saidi wrote: > > > >> Thanks for your response. > >> To configure vcenter on cloudstack we don't need to know interactions > >> between them , but i need informations for research issues. > >> > >> > >> 2014-04-09 13:48 GMT+02:00 Erik Weber : > >> > >> On Wed, Apr 9, 2014 at 1:44 PM, Mohamed Ali Saidi < > >>> saidi.mohamed.ali...@gmail.com> wrote: > >>> > >>> Hello, > > I'm searching in the internet for interaction issues (Ports, protocol > > >>> ,... > >>> > ) between cloudstack and vmware (vcenter,..) but i can't find any > helpful > docs. > > > I believe most of the traffic happens on HTTPS to vcenter. > >>> we put the vcenter in our management network, so didn't really have to > >>> puzzle with openings. > >>> > >>> > >>> -- > >>> Erik Weber > >>> > >>> > >
CS cores vs sockets
I think this issue may have been raised in the past, but was not addressed.. When creating a service offering in CS using multiple "cores" CS, actually creates the VM in the background with multiple sockets. Example a 6 "core" offering actually translates into a 6 socket offering. This is a problem on certain OS's and applications like SQL 2012. SQL 2012 has a 4 socket maximum. The easiest fix, might be just to allow the admin to specify how to arrive at the core count when creating the service offering. http://msdn.microsoft.com/en-us/library/ms143760.aspx I can't speak for other hypervisors, but this definitely effects vmware. The only workaround without a fix is to change the vm via virtual center... Thoughts?
RE: CS cores vs sockets
I created the feature request, hopefully it will gets some traction and get implemented. https://issues.apache.org/jira/browse/CLOUDSTACK-6454?filter=-2 > Date: Thu, 17 Apr 2014 15:35:45 -0600 > Subject: Re: CS cores vs sockets > From: shadow...@gmail.com > To: dev@cloudstack.apache.org > > Sorry, that was a *thumbsup*, but I forgot that the list doesn't like HTML > > > On Thu, Apr 17, 2014 at 3:31 PM, Nux! wrote: > > > On 17.04.2014 22:19, Marcus wrote: > > > >> [?] > >> > > > > Thanks for implementing this for KVM that is. :) > > > > > > -- > > Sent from the Delta quadrant using Borg technology! > > > > Nux! > > www.nux.ro > >
Cleanly remove management server
Last week we talked about a GUI option to cleanly remove a management server. I created a feature request for this as well. Hopefully this will get some traction as well. https://issues.apache.org/jira/browse/CLOUDSTACK-6455 I think I may dust up on my coding skills so I can contribute to the dev cause.
Upgraded from 4.2.1 to 4.3.0 getting a http 404 error
Did an upgrade from 4.2.1 to 4.3.0 on ubuntu, and now I am getting the following error. http://imgur.com/PonNMYL Any advise? Logs show a few errors:Mgmt server log error = java.sql.SQLException: No suitable driver found for jdbc:mysql://mysqldbserver:3306/cloud?autoReconnect=true&prepStmtCacheSize=517&cachePrepStmts=truecatalina log = INFO: validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/servlet-api-2.5-20081211.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.classcatalina log = INFO: validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/tomcat-embed-core-7.0.30.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
RE: Upgraded from 4.2.1 to 4.3.0 getting a http 404 error
Came across this article that fixed it for me... http://blog.widodh.nl/2014/03/sql-connection-error-after-upgrade-to-cloudstack-4-3-0/ Date: Fri, 18 Apr 2014 20:33:45 +0200 Subject: Re: Upgraded from 4.2.1 to 4.3.0 getting a http 404 error From: laszlo.horn...@gmail.com To: dev@cloudstack.apache.org; mphilli7...@hotmail.com Hi, The mysql driver is not available for CS, that is the trouble. Please check that the mysql jar files are in classpath. On Fri, Apr 18, 2014 at 8:06 PM, Michael Phillips wrote: Did an upgrade from 4.2.1 to 4.3.0 on ubuntu, and now I am getting the following error. http://imgur.com/PonNMYL Any advise? Logs show a few errors:Mgmt server log error = java.sql.SQLException: No suitable driver found for jdbc:mysql://mysqldbserver:3306/cloud?autoReconnect=true&prepStmtCacheSize=517&cachePrepStmts=truecatalina log = INFO: validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/servlet-api-2.5-20081211.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.classcatalina log = INFO: validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/tomcat-embed-core-7.0.30.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class -- EOF
RE: Cleanly remove management server
All I have done at this point is to create a JIRA request for this... > From: daan.hoogl...@gmail.com > Date: Mon, 5 May 2014 16:25:19 +0200 > Subject: Re: Cleanly remove management server > To: dev@cloudstack.apache.org > > H Michael, > > Did you investigate this further? still planning to implement? > > > On Fri, Apr 18, 2014 at 3:33 PM, Michael Phillips > wrote: > > Last week we talked about a GUI option to cleanly remove a management > > server. I created a feature request for this as well. Hopefully this will > > get some traction as well. > > https://issues.apache.org/jira/browse/CLOUDSTACK-6455 > > I think I may dust up on my coding skills so I can contribute to the dev > > cause. > > > > -- > Daan
uploadCustomCertificate
When using this command to upload the intermediate cert how do you specify the newline character that is included in SSL certs? I thought it might be to do \n, but it looks to just include the \n as part of the txt...
cloudstack-6378 Bug
All, I initially reported this issue back on 4/10/14 and it was marked as fixed however I just installed a fresh install on 4.4.0 on centos and the problem remains. I updated the JIRA ticket with the details. https://issues.apache.org/jira/browse/CLOUDSTACK-6378
4.4 Logging
Seems the logging level in 4.4 has been toned down, how do you crank it up to verbose levels?
RE: VMs stuck in expunging
Not sure if it's related but I do see the "SSL Fail to find the generated keystore" error which means your cloud.keystore file is not in the /etc/cloudstack/management folder.. > Date: Tue, 26 Aug 2014 19:18:51 -0400 > From: fgaudrea...@cloudops.com > To: dev@cloudstack.apache.org > Subject: Re: VMs stuck in expunging > > Oh man, we have four in this state, and you don't want to see the other > names lol > > I'll pump the log to trace and see what's going on. > > Thanks! > > FG > > On 2014-08-26, 2:41 PM, ilya musayev wrote: > > Its apparent that expunge failed, because VM name "ketchup-web" was to > > good to be deleted :) > > > > Try increasing the verbosity level on log4j so we can get a better > > picture. > > > > > > On 8/26/14, 7:29 AM, Francois Gaudreault wrote: > >> Hi, > >> > >> We have couple VMs stuck in Expunging state in our setup, and I am > >> not sure why. This is a 4.3.1-snapshot. This is what the log says: > >> > >> 2014-08-25 23:30:31,789 DEBUG [c.c.v.VirtualMachineManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Stopped called on > >> VM[User|ketchup-web] but the state is Expunging > >> 2014-08-25 23:30:31,808 WARN [c.c.u.n.Link] > >> (AgentManager-Selector:null) SSL: Fail to find the generated > >> keystore. Loading fail-safe one to continue. > >> 2014-08-25 23:30:31,810 DEBUG [c.c.c.CapacityManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) VM state transitted from :Expunging > >> to Expunging with event: ExpungeOperationvm's original host id: 1 new > >> host id: null host id before state transition: null > >> 2014-08-25 23:30:31,811 DEBUG [c.c.v.VirtualMachineManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Destroying vm VM[User|ketchup-web] > >> 2014-08-25 23:30:31,811 DEBUG [c.c.v.VirtualMachineManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Cleaning up NICS > >> 2014-08-25 23:30:31,811 DEBUG [o.a.c.e.o.NetworkOrchestrator] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Cleaning network for vm: 61 > >> 2014-08-25 23:30:31,814 DEBUG [c.c.v.VirtualMachineManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Cleaning up hypervisor data > >> structures (ex. SRs in XenServer) for managed storage > >> 2014-08-25 23:30:31,821 DEBUG [o.a.c.e.o.VolumeOrchestrator] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Cleaning storage for vm: 61 > >> 2014-08-25 23:30:31,825 DEBUG [c.c.v.VirtualMachineManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Expunged VM[User|ketchup-web] > >> 2014-08-25 23:30:31,825 DEBUG [c.c.v.UserVmManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Starting cleaning up vm > >> VM[User|ketchup-web] resources... > >> 2014-08-25 23:30:31,856 DEBUG [c.c.n.f.FirewallManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) No firewall rules are found for vm > >> id=61 > >> 2014-08-25 23:30:31,872 DEBUG [c.c.v.UserVmManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Firewall rules are removed > >> successfully as a part of vm id=61 expunge > >> 2014-08-25 23:30:31,884 DEBUG [c.c.u.d.T.Transaction] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Rolling back the transaction: Time > >> = 5 Name = UserVm-Scavenger-1; called by > >> -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-FirewallManagerImpl.revokeRule:732-GeneratedMethodAccessor278.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint:183-ReflectiveMethodInvocation.proceed:150 > >> 2014-08-25 23:30:31,887 WARN [c.c.v.UserVmManagerImpl] > >> (UserVm-Scavenger-1:ctx-bfdf6aa3) Unable to expunge VM[User|ketchup-web] > >> > >> Any idea what's going on? Bug? > >> > > > > > > > > > -- > Francois Gaudreault > Gestionnaire de Produit | Product Manager - Cloud Platform & Services > t:514-629-6775 > > CloudOps Votre partenaire infonuagique | Cloud Solutions Experts > 420 rue Guy | Montreal | Quebec | H3J 1S6 > w: cloudops.com | tw: @CloudOps_ >
RE: TomCat 404
Pretty sure they say 6.0.33 is the recommended version...any devs want to chime in on that? > Date: Tue, 26 Aug 2014 20:42:11 -0400 > From: m...@daoenix.com > To: dev@cloudstack.apache.org > Subject: TomCat 404 > > Greetings, > > I am having issues with tomcat 404 error, I presently have > Apache Tomcat/6.0.39 > > I believe that may be the issue? I am also using KVM / CentoOS 6.5. > > Anyone else have any idea? > > - Mo
CPU Sockets and Cores
All, The following pertains to cloudstack + vmware. Currently when using a multi CPU compute service offering, cloudstack creates the CPUs on the vm using all sockets. This can be an issue for operating systems that have physical CPU sockets limits. It can also be a license issue for certain software as well. An easy work around would be to let the admin define the socket to core ratio in the compute service offering. Are there in plans to implement such a feature in any upcoming cloudstack releases?
Refreshing Templates
What is the best way to refresh a template in cloudstack? Reasons one may want to refresh a template is to deploy the template with the latest patches, software etc.
RE: Refreshing Templates
That seems like the only method I have found as well. Only problem with that is I have a 3rd party software that integrates with CS and it uses CS to provision vm's etc. Deleting and re-uploading the template seems to break my 3rd party app because although the new template is named the same, it must have a new UUID or GUID. Wonder if it would be possible to just replace the templates .vmdk file. Forgot to mention that this is a vmware template. > Date: Fri, 14 Nov 2014 17:21:30 -0700 > Subject: Re: Refreshing Templates > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > I'm thinking you have to delete the old one and replace it with a new one. > > On Fri, Nov 14, 2014 at 5:01 PM, Michael Phillips > wrote: > > > What is the best way to refresh a template in cloudstack? > > Reasons one may want to refresh a template is to deploy the template with > > the latest patches, software etc. > > > > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > <http://solidfire.com/solution/overview/?video=play>*™*
Server 2012 R2 Bug on CS 4.4.0 with vmware hypervisor
So I was unable to add a data disk to my vm running server 2012 R2 standard, so I started tracking down the issue and I think I found it. So when provisioning a vm running server 2012 R2, CS creates the VM with the "LSI Logic Parallel" adapter. It looks like the only reason the machine is even able to boot is becuase the ROOT drive is set to be an IDE drive, specifically (IDE 0:1). Any data disks added to the same machine are set as SCSI drives. So if I added one data disk it would be listed as SCSI 0:0. So it seems the mismatch is between the controller type CS is using and the disk type. So this bring me to the major question at hand. For server 2012 R2 vmware natively uses the "LSI Logic SAS" controller. Why in the world is CS not using the same controller, and is there a way around this?
RE: Refreshing Templates
I will definitely create an enhancement ticket for that. > Date: Fri, 14 Nov 2014 17:50:25 -0700 > Subject: Re: Refreshing Templates > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > Hi Michael, > > I would encourage you to create a JIRA enhancement ticket for the use case > of modifying a template (unless anyone knows why that would not be a viable > solution). > > https://issues.apache.org/jira/browse/CLOUDSTACK/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel > > The only thing that comes to mind is that it would be hard to know who is > running with the old versus the new template (unless we started keeping > track of that info, too). > > Thanks, > Mike > > On Fri, Nov 14, 2014 at 5:31 PM, Michael Phillips > wrote: > > > That seems like the only method I have found as well. Only problem with > > that is I have a 3rd party software that integrates with CS and it uses CS > > to provision vm's etc. Deleting and re-uploading the template seems to > > break my 3rd party app because although the new template is named the same, > > it must have a new UUID or GUID. > > Wonder if it would be possible to just replace the templates .vmdk file. > > Forgot to mention that this is a vmware template. > > > > > Date: Fri, 14 Nov 2014 17:21:30 -0700 > > > Subject: Re: Refreshing Templates > > > From: mike.tutkow...@solidfire.com > > > To: dev@cloudstack.apache.org > > > > > > I'm thinking you have to delete the old one and replace it with a new > > one. > > > > > > On Fri, Nov 14, 2014 at 5:01 PM, Michael Phillips < > > mphilli7...@hotmail.com> > > > wrote: > > > > > > > What is the best way to refresh a template in cloudstack? > > > > Reasons one may want to refresh a template is to deploy the template > > with > > > > the latest patches, software etc. > > > > > > > > > > > > > > > > > > > > > > > -- > > > *Mike Tutkowski* > > > *Senior CloudStack Developer, SolidFire Inc.* > > > e: mike.tutkow...@solidfire.com > > > o: 303.746.7302 > > > Advancing the way the world uses the cloud > > > <http://solidfire.com/solution/overview/?video=play>*™* > > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > <http://solidfire.com/solution/overview/?video=play>*™*
RE: Server 2012 R2 Bug on CS 4.4.0 with vmware hypervisor
further clarification; CS adds the data disk to the VM but since it's listed as SCSI device 0:0, the vm is unable to find it when you do a disk rescan. I hope this makes sense... > From: mphilli7...@hotmail.com > To: dev@cloudstack.apache.org > Subject: Server 2012 R2 Bug on CS 4.4.0 with vmware hypervisor > Date: Fri, 14 Nov 2014 19:13:09 -0600 > > So I was unable to add a data disk to my vm running server 2012 R2 standard, > so I started tracking down the issue and I think I found it. So when > provisioning a vm running server 2012 R2, CS creates the VM with the "LSI > Logic Parallel" adapter. It looks like the only reason the machine is even > able to boot is becuase the ROOT drive is set to be an IDE drive, > specifically (IDE 0:1). Any data disks added to the same machine are set as > SCSI drives. So if I added one data disk it would be listed as SCSI 0:0. So > it seems the mismatch is between the controller type CS is using and the disk > type. So this bring me to the major question at hand. > For server 2012 R2 vmware natively uses the "LSI Logic SAS" controller. Why > in the world is CS not using the same controller, and is there a way around > this? > >
RE: Refreshing Templates
So I created the JIRA improvement ticket. https://issues.apache.org/jira/browse/CLOUDSTACK-7921 So how do the dev guys go about choosing which improvement tickets to work? > Date: Fri, 14 Nov 2014 17:50:25 -0700 > Subject: Re: Refreshing Templates > From: mike.tutkow...@solidfire.com > To: dev@cloudstack.apache.org > > Hi Michael, > > I would encourage you to create a JIRA enhancement ticket for the use case > of modifying a template (unless anyone knows why that would not be a viable > solution). > > https://issues.apache.org/jira/browse/CLOUDSTACK/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel > > The only thing that comes to mind is that it would be hard to know who is > running with the old versus the new template (unless we started keeping > track of that info, too). > > Thanks, > Mike > > On Fri, Nov 14, 2014 at 5:31 PM, Michael Phillips > wrote: > > > That seems like the only method I have found as well. Only problem with > > that is I have a 3rd party software that integrates with CS and it uses CS > > to provision vm's etc. Deleting and re-uploading the template seems to > > break my 3rd party app because although the new template is named the same, > > it must have a new UUID or GUID. > > Wonder if it would be possible to just replace the templates .vmdk file. > > Forgot to mention that this is a vmware template. > > > > > Date: Fri, 14 Nov 2014 17:21:30 -0700 > > > Subject: Re: Refreshing Templates > > > From: mike.tutkow...@solidfire.com > > > To: dev@cloudstack.apache.org > > > > > > I'm thinking you have to delete the old one and replace it with a new > > one. > > > > > > On Fri, Nov 14, 2014 at 5:01 PM, Michael Phillips < > > mphilli7...@hotmail.com> > > > wrote: > > > > > > > What is the best way to refresh a template in cloudstack? > > > > Reasons one may want to refresh a template is to deploy the template > > with > > > > the latest patches, software etc. > > > > > > > > > > > > > > > > > > > > > > > -- > > > *Mike Tutkowski* > > > *Senior CloudStack Developer, SolidFire Inc.* > > > e: mike.tutkow...@solidfire.com > > > o: 303.746.7302 > > > Advancing the way the world uses the cloud > > > <http://solidfire.com/solution/overview/?video=play>*™* > > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > <http://solidfire.com/solution/overview/?video=play>*™*
RE: Server 2012 R2 Bug on CS 4.4.0 with vmware hypervisor
OK, so I 100% confirmed that the issue is with the controller type being used by cloudstack. Microsoft removed the drivers for the LSILogicParallel controller from server 2012 R2. As mentioned earlier the only reason the server even boots is because cloudstack is adding the boot drive as an IDE device. Personally I think that's bad practice as well. So I got this to work by downloading the drivers from LSI's website then installing them in the server. Once I did that it found the controller, and I was able to use the data disk. Although I got this to work, I would be hesitant in using this in production for the following reasons. 1-Microsoft removed the driver, so this is an unsupported config. 2-The only driver LSI has for this device is for 2008x64, and it just so happens to work, so once again it's an unsupported config. 3-I have read a few articles online stating that this controller does not perform as well as the newer LSILogicSAS version. Take a look at the following screenshots for further detail https://www.dropbox.com/s/fxc1vneg787stn4/1-Controller%20Type.PNG?dl=0 https://www.dropbox.com/s/h2lujnol6am7tg7/2-No%20Driver.PNG?dl=0 https://www.dropbox.com/s/5c5jg61jz43w5sq/3-Driver%20Added.PNG?dl=0 https://www.dropbox.com/s/ypfdkvvwv7f9ex4/4-Disk%20Found.PNG?dl=0The first screen shot simply shows that CS added the controller type as a LSI Logic Parallel. The 2nd screen shot shows that server 2012 R2 does not have the drivers by default. The 3rd screen shot shows the controller after I installed the driver. The 4th screen shot show that the system found the drive after the drivers were installed. As far as I am concerned this controller selection bug with server 2012 r2 is a major issue, which renders this OS unusable in a production environment for the reasons I listed above. How can we get the heat turned up on this to get this corrected? It sounds like there is already a JIRA ticket opened, does anyone know the ticket number? > Date: Sat, 15 Nov 2014 07:31:10 +0100 > Subject: Re: Server 2012 R2 Bug on CS 4.4.0 with vmware hypervisor > From: terbol...@gmail.com > To: dev@cloudstack.apache.org > > There's an issue in jira to allow controller selection, but it has been > stale for some time. > > This is one of the reasons we switched to xenserver. > > I believe there's a quick talk on ccceu about the issue. > > Erik > > Den lørdag 15. november 2014 skrev Michael Phillips > følgende: > > > So I was unable to add a data disk to my vm running server 2012 R2 > > standard, so I started tracking down the issue and I think I found it. So > > when provisioning a vm running server 2012 R2, CS creates the VM with the > > "LSI Logic Parallel" adapter. It looks like the only reason the machine is > > even able to boot is becuase the ROOT drive is set to be an IDE drive, > > specifically (IDE 0:1). Any data disks added to the same machine are set as > > SCSI drives. So if I added one data disk it would be listed as SCSI 0:0. So > > it seems the mismatch is between the controller type CS is using and the > > disk type. So this bring me to the major question at hand. > > For server 2012 R2 vmware natively uses the "LSI Logic SAS" controller. > > Why in the world is CS not using the same controller, and is there a way > > around this? > > > >
Orphaned Data Disks
Has anyone noticed that after destroying and expunging an instance that has a data disk attached, cloudstack leaves the datadisk orphaned? If so is this expected behavior, and if so is there an option to change it?
RE: Orphaned Data Disks
What was the logic behind leaving the disks orphaned? > From: sanjeev.neelar...@citrix.com > To: dev@cloudstack.apache.org > Subject: RE: Orphaned Data Disks > Date: Thu, 29 Jan 2015 05:30:49 + > > That is expected behavior. Right now there is no option to change it. > > Sanjeev, > CloudPlatform Engineering, > Citrix Systems, Inc. > > > -----Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Thursday, January 29, 2015 10:43 AM > To: dev@cloudstack.apache.org > Subject: Orphaned Data Disks > > Has anyone noticed that after destroying and expunging an instance that has a > data disk attached, cloudstack leaves the datadisk orphaned? If so is this > expected behavior, and if so is there an option to change it? >
RE: Orphaned Data Disks
To me that's kind of strange to NOT assume to delete the disks that are attached to an instance at time of deletion. I think in most real world environments a data disk will belong to one machine only. Of course the exception is clustering and that is probably outside of this scope. Even if I was going to do some kind of OS upgrade and wanted to reuse the data disk on another instance I would probably detach, then reattach to the new instance. Just seems like it can get messy quick, if a lot of users delete their instances and leave all these orphaned data disks behind. It would be awesome to have a selection box to have cloudstack delete ALL attached disks when an instance is destroyed. Just my 2 cents... > Date: Wed, 28 Jan 2015 22:56:43 -0700 > Subject: Re: Orphaned Data Disks > From: shadow...@gmail.com > To: dev@cloudstack.apache.org > > Data disks are their own entity. You can detach them and attach them > to other VMs. CloudStack doesn't assume that you want all the disks to > die when you destroy a VM simply because they happen to be attached to > that vm at the moment. > > On Wed, Jan 28, 2015 at 10:47 PM, Michael Phillips > wrote: > > What was the logic behind leaving the disks orphaned? > > > >> From: sanjeev.neelar...@citrix.com > >> To: dev@cloudstack.apache.org > >> Subject: RE: Orphaned Data Disks > >> Date: Thu, 29 Jan 2015 05:30:49 + > >> > >> That is expected behavior. Right now there is no option to change it. > >> > >> Sanjeev, > >> CloudPlatform Engineering, > >> Citrix Systems, Inc. > >> > >> > >> -Original Message- > >> From: Michael Phillips [mailto:mphilli7...@hotmail.com] > >> Sent: Thursday, January 29, 2015 10:43 AM > >> To: dev@cloudstack.apache.org > >> Subject: Orphaned Data Disks > >> > >> Has anyone noticed that after destroying and expunging an instance that > >> has a data disk attached, cloudstack leaves the datadisk orphaned? If so > >> is this expected behavior, and if so is there an option to change it? > >
