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 +0000
>
> 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 +0000
> > >
> > > 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 +0000
> > > > > >
> > > > > > 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 <mphilli7...@hotmail.com>
> > > > > > 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 +0000
> > > > > > >
> > > > > > > Did you use package.sh -p nonoss ?
> > > > > > >
> > > > > > >
> > > > > > > - All mistakes in this message are not mine but Android's.
> > > > > > >
> > > > > > >
> > > > > > > -------- Original message --------
> > > > > > > From: Michael Phillips <mphilli7...@hotmail.com>
> > > > > > > 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 error....What am I
> > missing?
> > > > > >
> > > > >
> > > >
> > >
> >
>
