You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Fred Messinger <fr...@gmail.com> on 2013/10/15 20:55:50 UTC
Is this how we should be building debian packages for a vmware
centric cloudstack?
Hi All,
Since I'm trying to build the non-oss version from the most recent 4.2
Installation Guide on http://jenkins.buildacloud.org I followed these
steps:
$ sudo apt-get update
$ sudo apt-get install python-software-properties
$ sudo add-apt-repository ppa:natecarlson/maven3
$ sudo apt-get update
$ sudo apt-get install ant debhelper openjdk-6-jdk tomcat6
libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java
libcommons-httpclient-java liblog4j1.2-java maven3
$ mvn3 -P deps
$ dpkg-buildpackage -uc -us
The docs state these packages will be generated:
cloud-agent_4.0.0-incubating_amd64.deb
cloud-agent-deps_4.0.0-incubating_amd64.deb
cloud-agent-libs_4.0.0-incubating_amd64.deb
cloud-awsapi_4.0.0-incubating_amd64.deb
cloud-cli_4.0.0-incubating_amd64.deb
cloud-client_4.0.0-incubating_amd64.deb
cloud-client-ui_4.0.0-incubating_amd64.deb
cloud-core_4.0.0-incubating_amd64.deb
cloud-deps_4.0.0-incubating_amd64.deb
cloud-python_4.0.0-incubating_amd64.deb
cloud-scripts_4.0.0-incubating_amd64.deb
cloud-server_4.0.0-incubating_amd64.deb
cloud-setup_4.0.0-incubating_amd64.deb
cloud-system-iso_4.0.0-incubating_amd64.deb
cloud-usage_4.0.0-incubating_amd64.deb
cloud-utils_4.0.0-incubating_amd64.deb
But, in fact the only packages that are generated are
../cloudstack-agent_4.2.0_all.deb
../cloudstack-awsapi_4.2.0_all.deb
../cloudstack-cli_4.2.0_all.deb
../cloudstack-common_4.2.0_all.deb
../cloudstack-docs_4.2.0_all.deb
../cloudstack-management_4.2.0_all.deb
../cloudstack-usage_4.2.0_all.deb
And by the way, this is after I followed the instructions on
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#
for updating the deps directory with respect to vhdutil and others like
vim25_51 etc.
Is this expected?
Second point...After it's all daid and done and I follow the rest of the
installation enstructions, I still end up getting a recurring exception:
2013-10-15 14:32:55,586 WARN [agent.manager.AgentManagerImpl]
(ClusteredAgentManager Timer:null) Unable to find class
com.cloud.hypervisor.vmware.resource.VmwareResource
java.lang.ClassNotFoundException:
com.cloud.hypervisor.vmware.resource.VmwareResource
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:188)
at
com.cloud.agent.manager.AgentManagerImpl.loadResourcesWithoutHypervisor(AgentManagerImpl.java:667)
at
com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:741)
Management-server.log file attached.
Thanks in advance to anyone who can provide insights; I'be been battling
this dragon for a week.
I tried including my log file, but I think it's too big; the apache mailer
barfed.
Re: Is this how we should be building debian packages for a vmware
centric cloudstack?
Posted by Fred Messinger <fr...@gmail.com>.
Thanks, Travis, Doc bug 4873 submitted.
On Tue, Oct 15, 2013 at 3:01 PM, Travis Graham <tg...@tgraham.us> wrote:
> I can only speak to the first part. There should only be 7 packages
> generated, not the 16 referenced on the cwiki page.
>
> Travis
>
> On Oct 15, 2013, at 2:55 PM, Fred Messinger <fr...@gmail.com>
> wrote:
>
> > Hi All,
> >
> > Since I'm trying to build the non-oss version from the most recent 4.2
> > Installation Guide on http://jenkins.buildacloud.org I followed these
> > steps:
> >
> > $ sudo apt-get update
> > $ sudo apt-get install python-software-properties
> > $ sudo add-apt-repository ppa:natecarlson/maven3
> > $ sudo apt-get update
> > $ sudo apt-get install ant debhelper openjdk-6-jdk tomcat6
> > libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java
> > libcommons-httpclient-java liblog4j1.2-java maven3
> > $ mvn3 -P deps
> > $ dpkg-buildpackage -uc -us
> >
> >
> > The docs state these packages will be generated:
> >
> > cloud-agent_4.0.0-incubating_amd64.deb
> > cloud-agent-deps_4.0.0-incubating_amd64.deb
> > cloud-agent-libs_4.0.0-incubating_amd64.deb
> > cloud-awsapi_4.0.0-incubating_amd64.deb
> > cloud-cli_4.0.0-incubating_amd64.deb
> > cloud-client_4.0.0-incubating_amd64.deb
> > cloud-client-ui_4.0.0-incubating_amd64.deb
> > cloud-core_4.0.0-incubating_amd64.deb
> > cloud-deps_4.0.0-incubating_amd64.deb
> > cloud-python_4.0.0-incubating_amd64.deb
> > cloud-scripts_4.0.0-incubating_amd64.deb
> > cloud-server_4.0.0-incubating_amd64.deb
> > cloud-setup_4.0.0-incubating_amd64.deb
> > cloud-system-iso_4.0.0-incubating_amd64.deb
> > cloud-usage_4.0.0-incubating_amd64.deb
> > cloud-utils_4.0.0-incubating_amd64.deb
> >
> >
> > But, in fact the only packages that are generated are
> >
> > ../cloudstack-agent_4.2.0_all.deb
> > ../cloudstack-awsapi_4.2.0_all.deb
> > ../cloudstack-cli_4.2.0_all.deb
> > ../cloudstack-common_4.2.0_all.deb
> > ../cloudstack-docs_4.2.0_all.deb
> > ../cloudstack-management_4.2.0_all.deb
> > ../cloudstack-usage_4.2.0_all.deb
> >
> >
> >
> > And by the way, this is after I followed the instructions on
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#
> > for updating the deps directory with respect to vhdutil and others like
> > vim25_51 etc.
> >
> > Is this expected?
> >
> > Second point...After it's all daid and done and I follow the rest of the
> > installation enstructions, I still end up getting a recurring exception:
> >
> > 2013-10-15 14:32:55,586 WARN [agent.manager.AgentManagerImpl]
> > (ClusteredAgentManager Timer:null) Unable to find class
> > com.cloud.hypervisor.vmware.resource.VmwareResource
> > java.lang.ClassNotFoundException:
> > com.cloud.hypervisor.vmware.resource.VmwareResource
> > at
> >
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
> > at
> >
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
> > at java.lang.Class.forName0(Native Method)
> > at java.lang.Class.forName(Class.java:188)
> > at
> >
> com.cloud.agent.manager.AgentManagerImpl.loadResourcesWithoutHypervisor(AgentManagerImpl.java:667)
> > at
> >
> com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:741)
> >
> > Management-server.log file attached.
> >
> > Thanks in advance to anyone who can provide insights; I'be been battling
> > this dragon for a week.
> > I tried including my log file, but I think it's too big; the apache
> mailer
> > barfed.
>
>
Re: Is this how we should be building debian packages for a vmware centric cloudstack?
Posted by Travis Graham <tg...@tgraham.us>.
I can only speak to the first part. There should only be 7 packages generated, not the 16 referenced on the cwiki page.
Travis
On Oct 15, 2013, at 2:55 PM, Fred Messinger <fr...@gmail.com> wrote:
> Hi All,
>
> Since I'm trying to build the non-oss version from the most recent 4.2
> Installation Guide on http://jenkins.buildacloud.org I followed these
> steps:
>
> $ sudo apt-get update
> $ sudo apt-get install python-software-properties
> $ sudo add-apt-repository ppa:natecarlson/maven3
> $ sudo apt-get update
> $ sudo apt-get install ant debhelper openjdk-6-jdk tomcat6
> libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java
> libcommons-httpclient-java liblog4j1.2-java maven3
> $ mvn3 -P deps
> $ dpkg-buildpackage -uc -us
>
>
> The docs state these packages will be generated:
>
> cloud-agent_4.0.0-incubating_amd64.deb
> cloud-agent-deps_4.0.0-incubating_amd64.deb
> cloud-agent-libs_4.0.0-incubating_amd64.deb
> cloud-awsapi_4.0.0-incubating_amd64.deb
> cloud-cli_4.0.0-incubating_amd64.deb
> cloud-client_4.0.0-incubating_amd64.deb
> cloud-client-ui_4.0.0-incubating_amd64.deb
> cloud-core_4.0.0-incubating_amd64.deb
> cloud-deps_4.0.0-incubating_amd64.deb
> cloud-python_4.0.0-incubating_amd64.deb
> cloud-scripts_4.0.0-incubating_amd64.deb
> cloud-server_4.0.0-incubating_amd64.deb
> cloud-setup_4.0.0-incubating_amd64.deb
> cloud-system-iso_4.0.0-incubating_amd64.deb
> cloud-usage_4.0.0-incubating_amd64.deb
> cloud-utils_4.0.0-incubating_amd64.deb
>
>
> But, in fact the only packages that are generated are
>
> ../cloudstack-agent_4.2.0_all.deb
> ../cloudstack-awsapi_4.2.0_all.deb
> ../cloudstack-cli_4.2.0_all.deb
> ../cloudstack-common_4.2.0_all.deb
> ../cloudstack-docs_4.2.0_all.deb
> ../cloudstack-management_4.2.0_all.deb
> ../cloudstack-usage_4.2.0_all.deb
>
>
>
> And by the way, this is after I followed the instructions on
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#
> for updating the deps directory with respect to vhdutil and others like
> vim25_51 etc.
>
> Is this expected?
>
> Second point...After it's all daid and done and I follow the rest of the
> installation enstructions, I still end up getting a recurring exception:
>
> 2013-10-15 14:32:55,586 WARN [agent.manager.AgentManagerImpl]
> (ClusteredAgentManager Timer:null) Unable to find class
> com.cloud.hypervisor.vmware.resource.VmwareResource
> java.lang.ClassNotFoundException:
> com.cloud.hypervisor.vmware.resource.VmwareResource
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:188)
> at
> com.cloud.agent.manager.AgentManagerImpl.loadResourcesWithoutHypervisor(AgentManagerImpl.java:667)
> at
> com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:741)
>
> Management-server.log file attached.
>
> Thanks in advance to anyone who can provide insights; I'be been battling
> this dragon for a week.
> I tried including my log file, but I think it's too big; the apache mailer
> barfed.