You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cloudstack.apache.org by Will Stevens <ws...@cloudops.com> on 2013/10/17 22:28:29 UTC

Issues deploying with marvin

When I run:

I am getting the following error:
[DEBUG] Executing command line: python ../marvin/marvin/deployDataCenter.py
-i devcloud.cfg
5Traceback (most recent call last):
  File "../marvin/marvin/deployDataCenter.py", line 612, in <module>
    deploy.deploy()
  File "../marvin/marvin/deployDataCenter.py", line 597, in deploy
    self.createZones(self.config.zones)
  File "../marvin/marvin/deployDataCenter.py", line 466, in createZones
    self.createSecondaryStorages(zone.secondaryStorages, zoneId)
  File "../marvin/marvin/deployDataCenter.py", line 176, in
createSecondaryStorages
    secondarycmd = addImageStore.addImageStoreCmd()
NameError: global name 'addImageStore' is not defined
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------

I have looked and I can not find where 'addImageStore' is defined.  I was
expecting it to be imported via the 'from cloudstackAPI import *' line, but
'addImageStore.py' is not in that directory.

I have run 'python setup.py install' again in 'tools/marvin' just to make
sure it had not changed.

I ran the following:
# python -c "import pkg_resources;
print(pkg_resources.get_distribution('marvin').version)"

Which returned the version number of: 0.1.0

What do I need to do to get my environment up to speed?

Thanks...

Re: Issues deploying with marvin

Posted by Will Stevens <wi...@gmail.com>.

...Workaround included...

The issue that I run into by not using the 'developer' profile when I do a
'clean install' is that the 'py' files do not get updated in the
 tools/marvin/marvin/cloudstackAPI/ directory.  This is only a problem when
there are changes, but that happens often enough to warrant a work around...

This leads to the original error in this thread when this command runs: "python
../marvin/marvin/deployDataCenter.py -i devcloud.cfg"
Throws an error similar to: "NameError: global name 'addImageStore' is not
defined"
(because the file 'tools/marvin/marvin/cloudstackAPI/addImageStore.py' is
not present)

The following workflow works for me to get around this issue...

Run:
mvn -P developer,systemvm -Dnonoss clean install
(this will fail because of the hard linking of the files between the guest
os and the host os's file system, however, it seems to populate the 'py'
files or at least sets everything up so they will be populated correctly...)

Next run (same thing without the developer profile):
mvn -P systemvm -Dnonoss clean install
(this finishes and gives you a clean build)

Now you can do the deploy db with the developer profile:
mvn -P developer -pl developer,tools/devcloud -Ddeploydb
(this works)

Then startup the server:
export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m -Xdebug
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
mvn -pl :cloud-client-ui jetty:run -D nonoss
(wait for the server to come up)

Then run deploy server with the developer profile:
export MAVEN_OPTS=""
mvn -P developer -pl tools/devcloud -Ddeploysvr
(this now finds everything it needs and completes)

I hope this helps others get past this if they have similar problems...

Cheers...


On Wed, Oct 30, 2013 at 8:56 AM, Will Stevens <wi...@gmail.com>wrote:

> Yes. I believe the linking is failing because the host os and the guest os
> are different.
>
> Ws
>
> On Wednesday, October 30, 2013, Santhosh Edukulla wrote:
>
>> Based upon the error log below, it seems hard link creation is failing.
>>
>>
>>
>> >>>> hard linking CHANGES.txt -> Marvin-0.1.0
>>
>> > >>>>
>>
>> > >>>> error: Operation not permitted
>>
>>
>>
>> It seems some body earlier has faced a similar issue when using the
>> similar workflow and were not able to create hard links on mounted devices.
>>   They were able to overcome this as well. Check the link below.
>>
>>
>>
>>
>> http://stackoverflow.com/questions/7719380/python-setup-py-sdist-error-operation-not-permitted
>>
>>
>>
>> Thanks!
>>
>> Santhosh
>>
>>
>>
>> -----Original Message-----
>> From: Prasanna Santhanam [mailto:tsp@apache.org]
>> Sent: Wednesday, October 30, 2013 3:48 PM
>> To: Sebastien Goasguen
>> Cc: dev@cloudstack.apache.org; Prasanna Santhanam
>> Subject: Re: Issues deploying with marvin
>>
>>
>>
>> Never tried this with shared dir on vmware fusion but I expect the
>> failure is outside marvin really as Will mentioned. I'm sure this would
>> fail with vbox shared dirs as well.
>>
>>
>>
>> mvn is simply calling 'python setup.py sdist' when doing the build as the
>> user who runs mvn. If that user has permissions to write to your
>> shared-fusion dir, this should ideally have worked.
>>
>>
>>
>> On Wed, Oct 30, 2013 at 04:05:39AM -0400, Sebastien Goasguen wrote:
>>
>> > I am adding Prasanna to the thread as he is the main Marvin developer
>>
>> >
>>
>> > -sebastien
>>
>> >
>>
>> > On Oct 29, 2013, at 1:02 PM, Will Stevens <wstevens@cloudops.com
>> <ma...@cloudops.com>> wrote:
>>
>> >
>>
>> > > I believe the issues I am running into stem from the fact that the
>>
>> > > CS code is in a shared directory from my Mac to VMware Fusion.
>>
>> > > Because of this the 'ln' command is failing when building marvin...
>>
>> > >
>>
>> > > I may have to find a work around for this problem in order to build
>>
>> > > the developer profile.
>>
>> > >
>>
>> > > Will
>>
>> > >
>>
>> > >
>>
>> > > On Tue, Oct 29, 2013 at 11:59 AM, Will Stevens <wstevens@cloudops.com
>> <ma...@cloudops.com>>wrote:
>>
>> > >
>>
>> > >> I will pull and make this change because apparently this has been
>>
>> > >> in for a little while...
>>
>> > >>
>>
>> > >> I will update this if with more news when I have it.
>>
>> > >>
>>
>> > >>
>>
>> > >> On Tue, Oct 29, 2013 at 11:57 AM, Will Stevens <
>> wstevens@cloudops.com<ma...@cloudops.com>>wrote:
>>
>> > >>
>>
>> > >>> I know that I will have to change the 'nonoss' flag when I pull in
>>
>> > >>> the latest master from this weekend...
>>
>> > >>>
>>
>> > >>>
>>
>> > >>> On Tue, Oct 29, 2013 at 11:27 AM, Will Stevens <
>> wstevens@cloudops.com<ma...@cloudops.com>>wrote:
>>
>> > >>>
>>
>> > >>>> When I build with:  mvn -P developer,systemvm -Dnonoss clean
>>
>> > >>>> install -X
>>
>> > >>>>
>>
>> > >>>> I get the error below.  I have completely rebuilt my system from
>>
>> > >>>> scratch and I still get this...  Any ideas?
>>
>> > >>>>
>>
>> > >>>> If I run the same command, but without the 'developer' profile,
>>
>> > >>>> everything builds correctly.
>>
>> > >>>> (eg: mvn -P systemvm -Dnonoss clean install -X)
>>
>> > >>>>
>>
>> > >>>> Are there specific requirements needed to build the developer
>> profile?
>>
>> > >>>>
>>
>> > >>>> ---
>>
>> > >>>>
>>
>> > >>>> [INFO] Installing
>>
>> > >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml to
>>
>> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA
>>
>> > >>>> PSHOT/cloud-marvin-4.3.0-SNAPSHOT.pom
>>
>> > >>>>
>>
>> > >>>> [DEBUG] Writing resolution tracking file
>>
>> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA
>>
>> > >>>> PSHOT/_maven.repositories
>>
>> > >>>>
>>
>> > >>>> [DEBUG] Installing
>>
>> > >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT/maven-metadata.
>>
>> > >>>> xml to
>>
>> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA
>>
>> > >>>> PSHOT/maven-metadata-local.xml
>>
>> > >>>>
>>
>> > >>>> [DEBUG] Installing
>>
>> > >>>> org.apache.cloudstack:cloud-marvin/maven-metadata.xml
>>
>> > >>>> to
>>
>> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/maven-met
>>
>> > >>>> adata-local.xml
>>
>> > >>>>
>>
>> > >>>> [INFO]
>>
>> > >>>>
>>
>> > >>>> [INFO] --- exec-maven-plugin:1.2.1:exec (install) @ cloud-marvin
>>
>> > >>>> ---
>>
>> > >>>>
>>
>> > >>>> [DEBUG] Configuring mojo
>>
>> > >>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>
>> > >>>> from plugin realm
>>
>> > >>>> ClassRealm[plugin>org.codehaus.mojo:exec-maven-plugin:1.2.1,
>> parent:
>>
>> > >>>> sun.misc.Launcher$AppClassLoader@5acac268<mailto:sun.misc.Launcher
>> $AppClassLoader@5acac268>]
>>
>> > >>>>
>>
>> > >>>> [DEBUG] Configuring mojo
>>
>> > >>>> 'org.codehaus.mojo:exec-maven-plugin:1.2.1:exec' with basic
>>
>> > >>>> configurator -->
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) arguments = [setup.py, sdist]
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) basedir =
>>
>> > >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) classpathScope = runtime
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) executable = python
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) longClasspath = false
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) project = MavenProject:
>>
>> > >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT @
>>
>> > >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) session =
>> org.apache.maven.execution.MavenSession@6d3cba41<mailto:
>> org.apache.maven.execution.MavenSession@6d3cba41>
>>
>> > >>>>
>>
>> > >>>> [DEBUG]   (f) skip = false
>>
>> > >>>>
>>
>> > >>>> [DEBUG] -- end configuration --
>>
>> > >>>>
>>
>> > >>>> [DEBUG] Executing command line: python setup.py sdist
>>
>> > >>>>
>>
>> > >>>> running sdist
>>
>> > >>>>
>>
>> > >>>> running egg_info
>>
>> > >>>>
>>
>> > >>>> writing requirements to Marvin.egg-info/requires.txt
>>
>> > >>>>
>>
>> > >>>> writing Marvin.egg-info/PKG-INFO
>>
>> > >>>>
>>
>> > >>>> writing top-level names to Marvin.egg-info/top_level.txt
>>
>> > >>>>
>>
>> > >>>> writing dependency_links to Marvin.egg-info/dependency_links.txt
>>
>> > >>>>
>>
>> > >>>> writing entry points to Marvin.egg-info/entry_points.txt
>>
>> > >>>>
>>
>> > >>>> reading manifest file 'Marvin.egg-info/SOURCES.txt'
>>
>> > >>>>
>>
>> > >>>> reading manifest template 'MANIFEST.in'
>>
>> > >>>>
>>
>> > >>>> warning: no files found matching '*.txt' under directory 'docs'
>>
>> > >>>>
>>
>> > >>>> writing manifest file 'Marvin.egg-info/SOURCES.txt'
>>
>> > >>>>
>>
>> > >>>> making hard links in Marvin-0.1.0...
>>
>> > >>>>
>>
>> > >>>> hard linking CHANGES.txt -> Marvin-0.1.0
>>
>> > >>>>
>>
>> > >>>> error: Operation not permitted
>>
>> > >>>>
>>
>> > >>>> [INFO]
>>
>> > >>>> -----------------------------------------------------------------
>>
>> > >>>> -------
>>
>> > >>>>
>>
>> > >>>> [INFO] Reactor Summary:
>>
>> > >>>>
>>
>> > >>>> [INFO]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack .................................
>>
>> > >>>> SUCCESS [4.341s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Maven Conventions Parent ........
>>
>> > >>>> SUCCESS [0.089s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Framework - Managed Context .....
>>
>> > >>>> SUCCESS [4.999s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Utils ...........................
>>
>> > >>>> SUCCESS [17.555s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Framework .......................
>>
>> > >>>> SUCCESS [0.125s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Framework - Event Notification ..
>>
>> > >>>> SUCCESS [9.514s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Framework - Configuration .......
>>
>> > >>>> SUCCESS [5.700s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack API .............................
>>
>> > >>>> SUCCESS [26.885s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Framework - REST ................
>>
>> > >>>> SUCCESS [3.394s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Framework - IPC .................
>>
>> > >>>> SUCCESS [8.755s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Cloud Engine ....................
>>
>> > >>>> SUCCESS [0.091s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Cloud Engine API ................
>>
>> > >>>> SUCCESS [7.934s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Core ............................
>>
>> > >>>> SUCCESS [13.925s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Agents ..........................
>>
>> > >>>> SUCCESS [7.509s]
>>
>> > >>>>
>>
>> > >>>> [INFO] Apache CloudStack Framework - Clustering ..........
>>
>> > >>>> SUCCESS [4.550s]
>>
>> > >>>>
>>
>> > >> >>>>
>> -----------------------------------------------------------------
>>
>> > >>>> -------
>>
>> > >>>>
>>
>> > >>>> [INFO] BUILD FAILURE
>>
>> > >>>>
>>
>> > >>>> [INFO]
>>
>> > >>>> -----------------------------------------------------------------
>>
>> > >>>> -------
>>
>> > >>>>
>>
>> > >>>> [INFO] Total time: 9:56.659s
>>
>> > >>>>
>>
>> > >>>> [INFO] Finished at: Tue Oct 29 11:08:48 EDT 2013
>>
>> > >>>>
>>
>> > >>>> [INFO] Final Memory: 58M/172M
>>
>> > >>>>
>>
>> > >>>> [INFO]
>>
>> > >>>> -----------------------------------------------------------------
>>
>> > >>>> -------
>>
>> > >>>>
>>
>> > >>>> [ERROR] Failed to execute goal
>>
>> > >>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (install) on
>>
>> > >>>> project
>>
>> > >>>> cloud-marvin: Command execution failed. Process exited with an
>>
>> > >>>> error: 1 (Exit value: 1) -> [Help 1]
>>
>> > >>>>
>>
>> > >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>
>> > >>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>
>> > >>>> (install) on project cloud-marvin: Command execution failed.
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec
>>
>> > >>>> utor.java:217)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec
>>
>> > >>>> utor.java:153)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec
>>
>> > >>>> utor.java:145)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildP
>>
>> > >>>> roject(LifecycleModuleBuilder.java:84)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildP
>>
>> > >>>> roject(LifecycleModuleBuilder.java:59)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThread
>>
>> > >>>> edBuild(LifecycleStarter.java:183)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Life
>>
>> > >>>> cycleStarter.java:161)
>>
>> > >>>>
>>
>> > >>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>
>> > >>>>
>>
>> > >>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>
>> > >>>>
>>
>> > >>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>
>> > >>>>
>>
>> > >>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>
>> > >>>>
>>
>> > >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>
>> > >>>>
>>
>> > >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI
>>
>> > >>>> mpl.java:39)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA
>>
>> > >>>> ccessorImpl.java:25)
>>
>> > >>>>
>>
>> > >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
>>
>> > >>>> Launcher.java:290)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher
>>
>> > >>>> .java:230)
>>
>> > >>>>
>>
>> > >>>> at
>>
>> > >>>> org.codehaus.plexus.classworlds.launcher.Launch> >>>>
>> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
>>
>> > >>>>
>>
>> > >>>>> Hello William,
>>
>> > >>>>>
>>
>> > >>>>> 1.   After getting the latest master branch code, I just ran the
>>
>> > >>>>> command " mvn -P developer,systemvm clean install"  and I could
>>
>> > >>>>> see that both "commands.xml" file was created  under cs/
>>
>> > >>>>> tools/apidoc/target/  and "addImageStore.py" under
>> cs/tools/marvin/marvin/cloudstackAPI/ directory.
>>
>> > >>>>>  Please check post the command run, whether both were available
>> or not.
>>
>> > >>>>>
>>
>> > >>>>> 2.   Basically, codegeneratory.py under cs/tools/marvin/marvin
>>
>> > >>>>> directory is the one which based upon apispec file
>>
>> > >>>>> "commands.xml" if available  generates the cloudstackAPI and
>> > >>>>> From: williamstevens@gmail.com<mailto:williams
>>
>> > >>>>> On Behalf Of Will Stevens
>>
>> > >>>>> Sent: Friday, October 18, 2013 2:05 AM
>> >
>>
>

Re: Issues deploying with marvin

Posted by Will Stevens <wi...@gmail.com>.

Yes. I believe the linking is failing because the host os and the guest os
are different.

Ws

On Wednesday, October 30, 2013, Santhosh Edukulla wrote:

> Based upon the error log below, it seems hard link creation is failing.
>
>
>
> >>>> hard linking CHANGES.txt -> Marvin-0.1.0
>
> > >>>>
>
> > >>>> error: Operation not permitted
>
>
>
> It seems some body earlier has faced a similar issue when using the
> similar workflow and were not able to create hard links on mounted devices.
>   They were able to overcome this as well. Check the link below.
>
>
>
>
> http://stackoverflow.com/questions/7719380/python-setup-py-sdist-error-operation-not-permitted
>
>
>
> Thanks!
>
> Santhosh
>
>
>
> -----Original Message-----
> From: Prasanna Santhanam [mailto:tsp@apache.org <javascript:;>]
> Sent: Wednesday, October 30, 2013 3:48 PM
> To: Sebastien Goasguen
> Cc: dev@cloudstack.apache.org <javascript:;>; Prasanna Santhanam
> Subject: Re: Issues deploying with marvin
>
>
>
> Never tried this with shared dir on vmware fusion but I expect the failure
> is outside marvin really as Will mentioned. I'm sure this would fail with
> vbox shared dirs as well.
>
>
>
> mvn is simply calling 'python setup.py sdist' when doing the build as the
> user who runs mvn. If that user has permissions to write to your
> shared-fusion dir, this should ideally have worked.
>
>
>
> On Wed, Oct 30, 2013 at 04:05:39AM -0400, Sebastien Goasguen wrote:
>
> > I am adding Prasanna to the thread as he is the main Marvin developer
>
> >
>
> > -sebastien
>
> >
>
> > On Oct 29, 2013, at 1:02 PM, Will Stevens <wstevens@cloudops.com<javascript:;>
> <mailto:wstevens@cloudops.com <javascript:;>>> wrote:
>
> >
>
> > > I believe the issues I am running into stem from the fact that the
>
> > > CS code is in a shared directory from my Mac to VMware Fusion.
>
> > > Because of this the 'ln' command is failing when building marvin...
>
> > >
>
> > > I may have to find a work around for this problem in order to build
>
> > > the developer profile.
>
> > >
>
> > > Will
>
> > >
>
> > >
>
> > > On Tue, Oct 29, 2013 at 11:59 AM, Will Stevens <wstevens@cloudops.com<javascript:;>
> <mailto:wstevens@cloudops.com <javascript:;>>>wrote:
>
> > >
>
> > >> I will pull and make this change because apparently this has been
>
> > >> in for a little while...
>
> > >>
>
> > >> I will update this if with more news when I have it.
>
> > >>
>
> > >>
>
> > >> On Tue, Oct 29, 2013 at 11:57 AM, Will Stevens <wstevens@cloudops.com<javascript:;>
> <mailto:wstevens@cloudops.com <javascript:;>>>wrote:
>
> > >>
>
> > >>> I know that I will have to change the 'nonoss' flag when I pull in
>
> > >>> the latest master from this weekend...
>
> > >>>
>
> > >>>
>
> > >>> On Tue, Oct 29, 2013 at 11:27 AM, Will Stevens <
> wstevens@cloudops.com <javascript:;><mailto:wstevens@cloudops.com<javascript:;>
> >>wrote:
>
> > >>>
>
> > >>>> When I build with:  mvn -P developer,systemvm -Dnonoss clean
>
> > >>>> install -X
>
> > >>>>
>
> > >>>> I get the error below.  I have completely rebuilt my system from
>
> > >>>> scratch and I still get this...  Any ideas?
>
> > >>>>
>
> > >>>> If I run the same command, but without the 'developer' profile,
>
> > >>>> everything builds correctly.
>
> > >>>> (eg: mvn -P systemvm -Dnonoss clean install -X)
>
> > >>>>
>
> > >>>> Are there specific requirements needed to build the developer
> profile?
>
> > >>>>
>
> > >>>> ---
>
> > >>>>
>
> > >>>> [INFO] Installing
>
> > >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml to
>
> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA
>
> > >>>> PSHOT/cloud-marvin-4.3.0-SNAPSHOT.pom
>
> > >>>>
>
> > >>>> [DEBUG] Writing resolution tracking file
>
> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA
>
> > >>>> PSHOT/_maven.repositories
>
> > >>>>
>
> > >>>> [DEBUG] Installing
>
> > >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT/maven-metadata.
>
> > >>>> xml to
>
> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA
>
> > >>>> PSHOT/maven-metadata-local.xml
>
> > >>>>
>
> > >>>> [DEBUG] Installing
>
> > >>>> org.apache.cloudstack:cloud-marvin/maven-metadata.xml
>
> > >>>> to
>
> > >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/maven-met
>
> > >>>> adata-local.xml
>
> > >>>>
>
> > >>>> [INFO]
>
> > >>>>
>
> > >>>> [INFO] --- exec-maven-plugin:1.2.1:exec (install) @ cloud-marvin
>
> > >>>> ---
>
> > >>>>
>
> > >>>> [DEBUG] Configuring mojo
>
> > >>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>
> > >>>> from plugin realm
>
> > >>>> ClassRealm[plugin>org.codehaus.mojo:exec-maven-plugin:1.2.1, parent:
>
> > >>>> sun.misc.Launcher$AppClassLoader@5acac268<mailto:sun.misc.Launcher<javascript:;>
> $AppClassLoader@5acac268>]
>
> > >>>>
>
> > >>>> [DEBUG] Configuring mojo
>
> > >>>> 'org.codehaus.mojo:exec-maven-plugin:1.2.1:exec' with basic
>
> > >>>> configurator -->
>
> > >>>>
>
> > >>>> [DEBUG]   (f) arguments = [setup.py, sdist]
>
> > >>>>
>
> > >>>> [DEBUG]   (f) basedir =
>
> > >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin
>
> > >>>>
>
> > >>>> [DEBUG]   (f) classpathScope = runtime
>
> > >>>>
>
> > >>>> [DEBUG]   (f) executable = python
>
> > >>>>
>
> > >>>> [DEBUG]   (f) longClasspath = false
>
> > >>>>
>
> > >>>> [DEBUG]   (f) project = MavenProject:
>
> > >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT @
>
> > >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml
>
> > >>>>
>
> > >>>> [DEBUG]   (f) session =
> org.apache.maven.execution.MavenSession@6d3cba41<mailto:
> org.apache.maven.execution.MavenSession@6d3cba41 <javascript:;>>
>
> > >>>>
>
> > >>>> [DEBUG]   (f) skip = false
>
> > >>>>
>
> > >>>> [DEBUG] -- end configuration --
>
> > >>>>
>
> > >>>> [DEBUG] Executing command line: python setup.py sdist
>
> > >>>>
>
> > >>>> running sdist
>
> > >>>>
>
> > >>>> running egg_info
>
> > >>>>
>
> > >>>> writing requirements to Marvin.egg-info/requires.txt
>
> > >>>>
>
> > >>>> writing Marvin.egg-info/PKG-INFO
>
> > >>>>
>
> > >>>> writing top-level names to Marvin.egg-info/top_level.txt
>
> > >>>>
>
> > >>>> writing dependency_links to Marvin.egg-info/dependency_links.txt
>
> > >>>>
>
> > >>>> writing entry points to Marvin.egg-info/entry_points.txt
>
> > >>>>
>
> > >>>> reading manifest file 'Marvin.egg-info/SOURCES.txt'
>
> > >>>>
>
> > >>>> reading manifest template 'MANIFEST.in'
>
> > >>>>
>
> > >>>> warning: no files found matching '*.txt' under directory 'docs'
>
> > >>>>
>
> > >>>> writing manifest file 'Marvin.egg-info/SOURCES.txt'
>
> > >>>>
>
> > >>>> making hard links in Marvin-0.1.0...
>
> > >>>>
>
> > >>>> hard linking CHANGES.txt -> Marvin-0.1.0
>
> > >>>>
>
> > >>>> error: Operation not permitted
>
> > >>>>
>
> > >>>> [INFO]
>
> > >>>> -----------------------------------------------------------------
>
> > >>>> -------
>
> > >>>>
>
> > >>>> [INFO] Reactor Summary:
>
> > >>>>
>
> > >>>> [INFO]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack .................................
>
> > >>>> SUCCESS [4.341s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Maven Conventions Parent ........
>
> > >>>> SUCCESS [0.089s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Framework - Managed Context .....
>
> > >>>> SUCCESS [4.999s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Utils ...........................
>
> > >>>> SUCCESS [17.555s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Framework .......................
>
> > >>>> SUCCESS [0.125s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Framework - Event Notification ..
>
> > >>>> SUCCESS [9.514s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Framework - Configuration .......
>
> > >>>> SUCCESS [5.700s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack API .............................
>
> > >>>> SUCCESS [26.885s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Framework - REST ................
>
> > >>>> SUCCESS [3.394s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Framework - IPC .................
>
> > >>>> SUCCESS [8.755s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Cloud Engine ....................
>
> > >>>> SUCCESS [0.091s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Cloud Engine API ................
>
> > >>>> SUCCESS [7.934s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Core ............................
>
> > >>>> SUCCESS [13.925s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Agents ..........................
>
> > >>>> SUCCESS [7.509s]
>
> > >>>>
>
> > >>>> [INFO] Apache CloudStack Framework - Clustering ..........
>
> > >>>> SUCCESS [4.550s]
>
> > >>>>
>
> > >> >>>> -----------------------------------------------------------------
>
> > >>>> -------
>
> > >>>>
>
> > >>>> [INFO] BUILD FAILURE
>
> > >>>>
>
> > >>>> [INFO]
>
> > >>>> -----------------------------------------------------------------
>
> > >>>> -------
>
> > >>>>
>
> > >>>> [INFO] Total time: 9:56.659s
>
> > >>>>
>
> > >>>> [INFO] Finished at: Tue Oct 29 11:08:48 EDT 2013
>
> > >>>>
>
> > >>>> [INFO] Final Memory: 58M/172M
>
> > >>>>
>
> > >>>> [INFO]
>
> > >>>> -----------------------------------------------------------------
>
> > >>>> -------
>
> > >>>>
>
> > >>>> [ERROR] Failed to execute goal
>
> > >>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (install) on
>
> > >>>> project
>
> > >>>> cloud-marvin: Command execution failed. Process exited with an
>
> > >>>> error: 1 (Exit value: 1) -> [Help 1]
>
> > >>>>
>
> > >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>
> > >>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>
> > >>>> (install) on project cloud-marvin: Command execution failed.
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec
>
> > >>>> utor.java:217)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec
>
> > >>>> utor.java:153)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec
>
> > >>>> utor.java:145)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildP
>
> > >>>> roject(LifecycleModuleBuilder.java:84)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildP
>
> > >>>> roject(LifecycleModuleBuilder.java:59)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThread
>
> > >>>> edBuild(LifecycleStarter.java:183)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Life
>
> > >>>> cycleStarter.java:161)
>
> > >>>>
>
> > >>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>
> > >>>>
>
> > >>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>
> > >>>>
>
> > >>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>
> > >>>>
>
> > >>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>
> > >>>>
>
> > >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>
> > >>>>
>
> > >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> > >>>>
>
> > >>>> at
>
> > >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI
>
> > >>>> mpl.java:39)
>
> > >>>>
>
> > >>>> at
>
> > >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA
>
> > >>>> ccessorImpl.java:25)
>
> > >>>>
>
> > >>>> at java.lang.reflect.Method.invoke(Method.java:597)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
>
> > >>>> Launcher.java:290)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher
>
> > >>>> .java:230)
>
> > >>>>
>
> > >>>> at
>
> > >>>> org.codehaus.plexus.classworlds.launcher.Launch> >>>>
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
>
> > >>>>
>
> > >>>>> Hello William,
>
> > >>>>>
>
> > >>>>> 1.   After getting the latest master branch code, I just ran the
>
> > >>>>> command " mvn -P developer,systemvm clean install"  and I could
>
> > >>>>> see that both "commands.xml" file was created  under cs/
>
> > >>>>> tools/apidoc/target/  and "addImageStore.py" under
> cs/tools/marvin/marvin/cloudstackAPI/ directory.
>
> > >>>>>  Please check post the command run, whether both were available or
> not.
>
> > >>>>>
>
> > >>>>> 2.   Basically, codegeneratory.py under cs/tools/marvin/marvin
>
> > >>>>> directory is the one which based upon apispec file
>
> > >>>>> "commands.xml" if available  generates the cloudstackAPI and
> > >>>>> From: williamstevens@gmail.com<mailto:williams
> > >>>>> On Behalf Of Will Stevens
>
> > >>>>> Sent: Friday, October 18, 2013 2:05 AM
> >
>

RE: Issues deploying with marvin

Posted by Santhosh Edukulla <sa...@citrix.com>.

Based upon the error log below, it seems hard link creation is failing.



>>>> hard linking CHANGES.txt -> Marvin-0.1.0

> >>>>

> >>>> error: Operation not permitted



It seems some body earlier has faced a similar issue when using the similar workflow and were not able to create hard links on mounted devices.   They were able to overcome this as well. Check the link below.



http://stackoverflow.com/questions/7719380/python-setup-py-sdist-error-operation-not-permitted



Thanks!

Santhosh



-----Original Message-----
From: Prasanna Santhanam [mailto:tsp@apache.org]
Sent: Wednesday, October 30, 2013 3:48 PM
To: Sebastien Goasguen
Cc: dev@cloudstack.apache.org; Prasanna Santhanam
Subject: Re: Issues deploying with marvin



Never tried this with shared dir on vmware fusion but I expect the failure is outside marvin really as Will mentioned. I'm sure this would fail with vbox shared dirs as well.



mvn is simply calling 'python setup.py sdist' when doing the build as the user who runs mvn. If that user has permissions to write to your shared-fusion dir, this should ideally have worked.



On Wed, Oct 30, 2013 at 04:05:39AM -0400, Sebastien Goasguen wrote:

> I am adding Prasanna to the thread as he is the main Marvin developer

>

> -sebastien

>

> On Oct 29, 2013, at 1:02 PM, Will Stevens <ws...@cloudops.com>> wrote:

>

> > I believe the issues I am running into stem from the fact that the

> > CS code is in a shared directory from my Mac to VMware Fusion.

> > Because of this the 'ln' command is failing when building marvin...

> >

> > I may have to find a work around for this problem in order to build

> > the developer profile.

> >

> > Will

> >

> >

> > On Tue, Oct 29, 2013 at 11:59 AM, Will Stevens <ws...@cloudops.com>>wrote:

> >

> >> I will pull and make this change because apparently this has been

> >> in for a little while...

> >>

> >> I will update this if with more news when I have it.

> >>

> >>

> >> On Tue, Oct 29, 2013 at 11:57 AM, Will Stevens <ws...@cloudops.com>>wrote:

> >>

> >>> I know that I will have to change the 'nonoss' flag when I pull in

> >>> the latest master from this weekend...

> >>>

> >>>

> >>> On Tue, Oct 29, 2013 at 11:27 AM, Will Stevens <ws...@cloudops.com>>wrote:

> >>>

> >>>> When I build with:  mvn -P developer,systemvm -Dnonoss clean

> >>>> install -X

> >>>>

> >>>> I get the error below.  I have completely rebuilt my system from

> >>>> scratch and I still get this...  Any ideas?

> >>>>

> >>>> If I run the same command, but without the 'developer' profile,

> >>>> everything builds correctly.

> >>>> (eg: mvn -P systemvm -Dnonoss clean install -X)

> >>>>

> >>>> Are there specific requirements needed to build the developer profile?

> >>>>

> >>>> ---

> >>>>

> >>>> [INFO] Installing

> >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml to

> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA

> >>>> PSHOT/cloud-marvin-4.3.0-SNAPSHOT.pom

> >>>>

> >>>> [DEBUG] Writing resolution tracking file

> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA

> >>>> PSHOT/_maven.repositories

> >>>>

> >>>> [DEBUG] Installing

> >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT/maven-metadata.

> >>>> xml to

> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNA

> >>>> PSHOT/maven-metadata-local.xml

> >>>>

> >>>> [DEBUG] Installing

> >>>> org.apache.cloudstack:cloud-marvin/maven-metadata.xml

> >>>> to

> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/maven-met

> >>>> adata-local.xml

> >>>>

> >>>> [INFO]

> >>>>

> >>>> [INFO] --- exec-maven-plugin:1.2.1:exec (install) @ cloud-marvin

> >>>> ---

> >>>>

> >>>> [DEBUG] Configuring mojo

> >>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec

> >>>> from plugin realm

> >>>> ClassRealm[plugin>org.codehaus.mojo:exec-maven-plugin:1.2.1, parent:

> >>>> sun.misc.Launcher$AppClassLoader@5acac268<ma...@5acac268>]

> >>>>

> >>>> [DEBUG] Configuring mojo

> >>>> 'org.codehaus.mojo:exec-maven-plugin:1.2.1:exec' with basic

> >>>> configurator -->

> >>>>

> >>>> [DEBUG]   (f) arguments = [setup.py, sdist]

> >>>>

> >>>> [DEBUG]   (f) basedir =

> >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin

> >>>>

> >>>> [DEBUG]   (f) classpathScope = runtime

> >>>>

> >>>> [DEBUG]   (f) executable = python

> >>>>

> >>>> [DEBUG]   (f) longClasspath = false

> >>>>

> >>>> [DEBUG]   (f) project = MavenProject:

> >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT @

> >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml

> >>>>

> >>>> [DEBUG]   (f) session = org.apache.maven.execution.MavenSession@6d3cba41<ma...@6d3cba41>

> >>>>

> >>>> [DEBUG]   (f) skip = false

> >>>>

> >>>> [DEBUG] -- end configuration --

> >>>>

> >>>> [DEBUG] Executing command line: python setup.py sdist

> >>>>

> >>>> running sdist

> >>>>

> >>>> running egg_info

> >>>>

> >>>> writing requirements to Marvin.egg-info/requires.txt

> >>>>

> >>>> writing Marvin.egg-info/PKG-INFO

> >>>>

> >>>> writing top-level names to Marvin.egg-info/top_level.txt

> >>>>

> >>>> writing dependency_links to Marvin.egg-info/dependency_links.txt

> >>>>

> >>>> writing entry points to Marvin.egg-info/entry_points.txt

> >>>>

> >>>> reading manifest file 'Marvin.egg-info/SOURCES.txt'

> >>>>

> >>>> reading manifest template 'MANIFEST.in'

> >>>>

> >>>> warning: no files found matching '*.txt' under directory 'docs'

> >>>>

> >>>> writing manifest file 'Marvin.egg-info/SOURCES.txt'

> >>>>

> >>>> making hard links in Marvin-0.1.0...

> >>>>

> >>>> hard linking CHANGES.txt -> Marvin-0.1.0

> >>>>

> >>>> error: Operation not permitted

> >>>>

> >>>> [INFO]

> >>>> -----------------------------------------------------------------

> >>>> -------

> >>>>

> >>>> [INFO] Reactor Summary:

> >>>>

> >>>> [INFO]

> >>>>

> >>>> [INFO] Apache CloudStack .................................

> >>>> SUCCESS [4.341s]

> >>>>

> >>>> [INFO] Apache CloudStack Maven Conventions Parent ........

> >>>> SUCCESS [0.089s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - Managed Context .....

> >>>> SUCCESS [4.999s]

> >>>>

> >>>> [INFO] Apache CloudStack Utils ...........................

> >>>> SUCCESS [17.555s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework .......................

> >>>> SUCCESS [0.125s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - Event Notification ..

> >>>> SUCCESS [9.514s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - Configuration .......

> >>>> SUCCESS [5.700s]

> >>>>

> >>>> [INFO] Apache CloudStack API .............................

> >>>> SUCCESS [26.885s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - REST ................

> >>>> SUCCESS [3.394s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - IPC .................

> >>>> SUCCESS [8.755s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Engine ....................

> >>>> SUCCESS [0.091s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Engine API ................

> >>>> SUCCESS [7.934s]

> >>>>

> >>>> [INFO] Apache CloudStack Core ............................

> >>>> SUCCESS [13.925s]

> >>>>

> >>>> [INFO] Apache CloudStack Agents ..........................

> >>>> SUCCESS [7.509s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - Clustering ..........

> >>>> SUCCESS [4.550s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - Jobs ................

> >>>> SUCCESS [4.811s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Engine Schema Component ...

> >>>> SUCCESS [17.694s]

> >>>>

> >>>> [INFO] Apache CloudStack Framework - Event Notification ..

> >>>> SUCCESS [2.665s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Engine Internal Components API

> >>>> SUCCESS [4.491s]

> >>>>

> >>>> [INFO] Apache CloudStack Server ..........................

> >>>> SUCCESS [56.473s]

> >>>>

> >>>> [INFO] Apache CloudStack Usage Server ....................

> >>>> SUCCESS [8.747s]

> >>>>

> >>>> [INFO] Apache XenSource XAPI .............................

> >>>> SUCCESS [8.695s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Engine Orchestration Component

> >>>> SUCCESS [10.341s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Services ..................

> >>>> SUCCESS [0.207s]

> >>>>

> >>>> [INFO] Apache CloudStack Secondary Storage Service .......

> >>>> SUCCESS [5.918s]

> >>>>

> >>>> [INFO] Apache CloudStack Engine Storage Component ........

> >>>> SUCCESS [5.974s]

> >>>>

> >>>> [INFO] Apache CloudStack Engine Storage Volume Component .

> >>>> SUCCESS [5.936s]

> >>>>

> >>>> [INFO] Apache CloudStack Engine Storage Image Component ..

> >>>> SUCCESS [3.533s]

> >>>>

> >>>> [INFO] Apache CloudStack Engine Storage Data Motion Component

> >>>> SUCCESS [4.206s]

> >>>>

> >>>> [INFO] Apache CloudStack Engine Storage Cache Component ..

> >>>> SUCCESS [2.888s]

> >>>>

> >>>> [INFO] Apache CloudStack Engine Storage Snapshot Component

> >>>> SUCCESS [5.265s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Engine API ................

> >>>> SUCCESS [2.756s]

> >>>>

> >>>> [INFO] Apache CloudStack Cloud Engine Service ............

> >>>> SUCCESS [7.624s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin POM ......................

> >>>> SUCCESS [1.440s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - API Rate Limit .........

> >>>> SUCCESS [8.121s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - API Discovery ..........

> >>>> SUCCESS [5.600s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - ACL Static Role Based ..

> >>>> SUCCESS [3.822s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor

> >>>> SUCCESS [2.641s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Explicit Dedication Processor

> >>>> SUCCESS [3.097s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - User Concentrated Pod

> >>>> Deployment Planner  SUCCESS [2.696s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - User Dispersing Deployment

> >>>> Planner SUCCESS [2.624s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Implicit Dedication Planner

> >>>> SUCCESS [8.390s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Host Allocator Random ..

> >>>> SUCCESS [2.733s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Dedicated Resources ....

> >>>> SUCCESS [7.454s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Hypervisor OracleVM ....

> >>>> SUCCESS [4.439s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Open vSwitch ...........

> >>>> SUCCESS [3.581s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Hypervisor Xen .........

> >>>> SUCCESS [12.095s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Hypervisor KVM .........

> >>>> SUCCESS [13.159s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - RabbitMQ Event Bus .....

> >>>> SUCCESS [2.939s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Hypervisor Baremetal ...

> >>>> SUCCESS [4.963s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Hypervisor UCS .........

> >>>> SUCCESS [3.429s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Network Elastic Load Balancer

> >>>> SUCCESS [5.100s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Network Nicira NVP .....

> >>>> SUCCESS [11.103s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - BigSwitch Virtual Network

> >>>> Segment SUCCESS [7.611s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Midokura Midonet .......

> >>>> SUCCESS [7.864s]

> >>>>

> >>>> [INFO] Apache Cloudstack Plugin - Stratosphere SSP .......

> >>>> SUCCESS [7.125s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Allocator Random

> >>>> SUCCESS [2.552s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - User Authenticator LDAP

> >>>> SUCCESS [3.892s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - User Authenticator MD5 .

> >>>> SUCCESS [2.733s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - User Authenticator Plain Text

> >>>> SUCCESS [2.547s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - User Authenticator SHA256

> >>>> Salted SUCCESS [33.230s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Dns Notifier Example ...

> >>>> SUCCESS [2.494s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Image S3 .......

> >>>> SUCCESS [2.864s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Image Swift provider

> >>>> SUCCESS [2.543s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Image default provider

> >>>> SUCCESS [2.431s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Image sample provider

> >>>> SUCCESS [2.945s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Volume SolidFire

> >>>> Provider SUCCESS [5.323s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Volume default provider

> >>>> SUCCESS [2.771s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Storage Volume sample provider

> >>>> SUCCESS [2.414s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - SNMP Alerts ............

> >>>> SUCCESS [5.064s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Syslog Alerts ..........

> >>>> SUCCESS [4.563s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Network Internal Load Balancer

> >>>> SUCCESS [10.414s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Network VXLAN ..........

> >>>> SUCCESS [5.421s]

> >>>>

> >>>> [INFO] Apache CloudStack Plugin - Palo Alto ..............

> >>>> SUCCESS [8.807s]

> >>>>

> >>>> [INFO] Apache CloudStack Test ............................

> >>>> SUCCESS [0.586s]

> >>>>

> >>>> [INFO] Apache CloudStack Console Proxy ...................

> >>>> SUCCESS [0.045s]

> >>>>

> >>>> [INFO] Apache CloudStack Console Proxy - Server ..........

> >>>> SUCCESS [3.691s]

> >>>>

> >>>> [INFO] Apache CloudStack System VM .......................

> >>>> SUCCESS [8.814s]

> >>>>

> >>>> [INFO] Apache CloudStack Client UI .......................

> >>>> SUCCESS [31.508s]

> >>>>

> >>>> [INFO] Apache CloudStack Developer Mode ..................

> >>>> SUCCESS [3.295s]

> >>>>

> >>>> [INFO] Apache CloudStack Developer Tools .................

> >>>> SUCCESS [0.135s]

> >>>>

> >>>> [INFO] Apache CloudStack apidocs .........................

> >>>> SUCCESS [33.492s]

> >>>>

> >>>> [INFO] Apache CloudStack marvin ..........................

> >>>> FAILURE [3.828s]

> >>>>

> >>>> [INFO] Apache CloudStack DevCloud ........................

> >>>> SKIPPED

> >>>>

> >>>> [INFO] Apache CloudStack DevCloud-KVM ....................

> >>>> SKIPPED

> >>>>

> >>>> [INFO]

> >>>> -----------------------------------------------------------------

> >>>> -------

> >>>>

> >>>> [INFO] BUILD FAILURE

> >>>>

> >>>> [INFO]

> >>>> -----------------------------------------------------------------

> >>>> -------

> >>>>

> >>>> [INFO] Total time: 9:56.659s

> >>>>

> >>>> [INFO] Finished at: Tue Oct 29 11:08:48 EDT 2013

> >>>>

> >>>> [INFO] Final Memory: 58M/172M

> >>>>

> >>>> [INFO]

> >>>> -----------------------------------------------------------------

> >>>> -------

> >>>>

> >>>> [ERROR] Failed to execute goal

> >>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (install) on

> >>>> project

> >>>> cloud-marvin: Command execution failed. Process exited with an

> >>>> error: 1 (Exit value: 1) -> [Help 1]

> >>>>

> >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to

> >>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec

> >>>> (install) on project cloud-marvin: Command execution failed.

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec

> >>>> utor.java:217)

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec

> >>>> utor.java:153)

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec

> >>>> utor.java:145)

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildP

> >>>> roject(LifecycleModuleBuilder.java:84)

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildP

> >>>> roject(LifecycleModuleBuilder.java:59)

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThread

> >>>> edBuild(LifecycleStarter.java:183)

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Life

> >>>> cycleStarter.java:161)

> >>>>

> >>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)

> >>>>

> >>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)

> >>>>

> >>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

> >>>>

> >>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)

> >>>>

> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)

> >>>>

> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

> >>>>

> >>>> at

> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI

> >>>> mpl.java:39)

> >>>>

> >>>> at

> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA

> >>>> ccessorImpl.java:25)

> >>>>

> >>>> at java.lang.reflect.Method.invoke(Method.java:597)

> >>>>

> >>>> at

> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(

> >>>> Launcher.java:290)

> >>>>

> >>>> at

> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher

> >>>> .java:230)

> >>>>

> >>>> at

> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCod

> >>>> e(Launcher.java:409)

> >>>>

> >>>> at

> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.j

> >>>> ava:352)

> >>>>

> >>>> Caused by: org.apache.maven.plugin.MojoExecutionException:

> >>>> Command execution failed.

> >>>>

> >>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

> >>>>

> >>>> at

> >>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Def

> >>>> aultBuildPluginManager.java:101)

> >>>>

> >>>> at

> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExec

> >>>> utor.java:209)

> >>>>

> >>>> ... 19 more

> >>>>

> >>>> Caused by: org.apache.commons.exec.ExecuteException: Process

> >>>> exited with an error: 1 (Exit value: 1)

> >>>>

> >>>> at

> >>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultEx

> >>>> ecutor.java:377)

> >>>>

> >>>> at

> >>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.j

> >>>> ava:160)

> >>>>

> >>>> at

> >>>> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:

> >>>> 610)

> >>>>

> >>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

> >>>>

> >>>> ... 21 more

> >>>>

> >>>> [ERROR]

> >>>>

> >>>> [ERROR]

> >>>>

> >>>> [ERROR] For more information about the errors and possible

> >>>> solutions, please read the following articles:

> >>>>

> >>>> [ERROR] [Help 1]

> >>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExc

> >>>> eption

> >>>>

> >>>> [ERROR]

> >>>>

> >>>> [ERROR] After correcting the problems, you can resume the build

> >>>> with the command

> >>>>

> >>>> [ERROR]   mvn <goals> -rf :cloud-marvin

> >>>>

> >>>>

> >>>> On Fri, Oct 18, 2013 at 7:58 AM, Santhosh Edukulla <

> >>>> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:

> >>>>

> >>>>> Hello William,

> >>>>>

> >>>>> 1.   After getting the latest master branch code, I just ran the

> >>>>> command " mvn -P developer,systemvm clean install"  and I could

> >>>>> see that both "commands.xml" file was created  under cs/

> >>>>> tools/apidoc/target/  and "addImageStore.py" under cs/tools/marvin/marvin/cloudstackAPI/ directory.

> >>>>>  Please check post the command run, whether both were available or not.

> >>>>>

> >>>>> 2.   Basically, codegeneratory.py under cs/tools/marvin/marvin

> >>>>> directory is the one which based upon apispec file

> >>>>> "commands.xml" if available  generates the cloudstackAPI and

> >>>>> corresponding modules under its directory.  In case as mentioned

> >>>>> under pom.xml, if commands.xml is not available, it takes the

> >>>>> apispec file as  " /etc/cloud/cli/commands.xml". It also has the

> >>>>> option of creating cloudstackAPI/modules from json response

> >>>>> endpoint url " http://ip:8096/client/api?command=listApis", default to localhost.

> >>>>>

> >>>>>

> >>>>>

> >>>>> Thanks!

> >>>>> Santhosh

> >>>>>

> >>>>> -----Original Message-----

> >>>>> From: williamstevens@gmail.com<ma...@gmail.com> [mailto:williamstevens@gmail.com]

> >>>>> On Behalf Of Will Stevens

> >>>>> Sent: Friday, October 18, 2013 2:05 AM

> >>>>> To: dev@cloudstack.apache<ma...@cloudstack.apache>.

> >>>>> Subject: Re: Issues deploying with marvin

> >>>>>

> >>>>> Note: I pulled from master yesterday...y

> >>>>>

> >>>>>

> >>>>> On Thu, Oct 17, 2013 at 4:28 PM, Will Stevens

> >>>>> <ws...@cloudops.com>>

> >>>>> wrote:

> >>>>>

> >>>>>> When I run:

> >>>>>>

> >>>>>> I am getting the following error:

> >>>>>> [DEBUG] Executing command line: python

> >>>>>> ../marvin/marvin/deployDataCenter.py -i devcloud.cfg 5Traceback

> >>>>>> (most recent call last):

> >>>>>>  File "../marvin/marvin/deployDataCenter.py", line 612, in <module>

> >>>>>>    deploy.deploy()

> >>>>>>  File "../marvin/marvin/deployDataCenter.py", line 597, in deploy

> >>>>>>    self.createZones(self.config.zones)

> >>>>>>  File "../marvin/marvin/deployDataCenter.py", line 466, in

> >>>>> createZones

> >>>>>>    self.createSecondaryStorages(zone.secondaryStorages, zoneId)

> >>>>>> File "../marvin/marvin/deployDataCenter.py", line 176, in

> >>>>>> createSecondaryStorages

> >>>>>>    secondarycmd = addImageStore.addImageStoreCmd()

> >>>>>> NameError: global name 'addImageStore' is not defined [INFO]

> >>>>>> ---------------------------------------------------------------

> >>>>>> -------

> >>>>>> --

> >>>>>> [INFO] BUILD FAILURE

> >>>>>> [INFO]

> >>>>>> ---------------------------------------------------------------

> >>>>>> -------

> >>>>>> --

> >>>>>>

> >>>>>> I have looked and I can not find where 'addImageStore' is

> >>>>>> defined.  I was expecting it to be imported via the 'from cloudstackAPI import *'

> >>>>>> line, but 'addImageStore.py' is not in that directory.

> >>>>>>

> >>>>>> I have run 'python setup.py install' again in 'tools/marvin'

> >>>>>> just to make sure it had not changed.

> >>>>>>

> >>>>>> I ran the following:

> >>>>>> # python -c "import pkg_resources;

> >>>>>> print(pkg_resources.get_distribution('marvin').version)"

> >>>>>>

> >>>>>> Which returned the version number of: 0.1.0

> >>>>>>

> >>>>>> What do I need to do to get my environment up to speed?

> >>>>>>

> >>>>>> Thanks...

> >>>>>>

> >>>>>

> >>>>

> >>>>

> >>>

> >>



--

Prasanna.,



------------------------

Powered by BigRock.com

Re: Issues deploying with marvin

Posted by Prasanna Santhanam <ts...@apache.org>.

Never tried this with shared dir on vmware fusion but I expect the
failure is outside marvin really as Will mentioned. I'm sure this
would fail with vbox shared dirs as well.

mvn is simply calling 'python setup.py sdist' when doing the build as
the user who runs mvn. If that user has permissions to write to your
shared-fusion dir, this should ideally have worked.

On Wed, Oct 30, 2013 at 04:05:39AM -0400, Sebastien Goasguen wrote:
> I am adding Prasanna to the thread as he is the main Marvin developer
> 
> -sebastien
> 
> On Oct 29, 2013, at 1:02 PM, Will Stevens <ws...@cloudops.com> wrote:
> 
> > I believe the issues I am running into stem from the fact that the CS code
> > is in a shared directory from my Mac to VMware Fusion.  Because of this the
> > 'ln' command is failing when building marvin...
> > 
> > I may have to find a work around for this problem in order to build the
> > developer profile.
> > 
> > Will
> > 
> > 
> > On Tue, Oct 29, 2013 at 11:59 AM, Will Stevens <ws...@cloudops.com>wrote:
> > 
> >> I will pull and make this change because apparently this has been in for a
> >> little while...
> >> 
> >> I will update this if with more news when I have it.
> >> 
> >> 
> >> On Tue, Oct 29, 2013 at 11:57 AM, Will Stevens <ws...@cloudops.com>wrote:
> >> 
> >>> I know that I will have to change the 'nonoss' flag when I pull in the
> >>> latest master from this weekend...
> >>> 
> >>> 
> >>> On Tue, Oct 29, 2013 at 11:27 AM, Will Stevens <ws...@cloudops.com>wrote:
> >>> 
> >>>> When I build with:  mvn -P developer,systemvm -Dnonoss clean install -X
> >>>> 
> >>>> I get the error below.  I have completely rebuilt my system from scratch
> >>>> and I still get this...  Any ideas?
> >>>> 
> >>>> If I run the same command, but without the 'developer' profile,
> >>>> everything builds correctly.
> >>>> (eg: mvn -P systemvm -Dnonoss clean install -X)
> >>>> 
> >>>> Are there specific requirements needed to build the developer profile?
> >>>> 
> >>>> ---
> >>>> 
> >>>> [INFO] Installing
> >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml to
> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNAPSHOT/cloud-marvin-4.3.0-SNAPSHOT.pom
> >>>> 
> >>>> [DEBUG] Writing resolution tracking file
> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNAPSHOT/_maven.repositories
> >>>> 
> >>>> [DEBUG] Installing
> >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT/maven-metadata.xml to
> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/4.3.0-SNAPSHOT/maven-metadata-local.xml
> >>>> 
> >>>> [DEBUG] Installing org.apache.cloudstack:cloud-marvin/maven-metadata.xml
> >>>> to
> >>>> /root/.m2/repository/org/apache/cloudstack/cloud-marvin/maven-metadata-local.xml
> >>>> 
> >>>> [INFO]
> >>>> 
> >>>> [INFO] --- exec-maven-plugin:1.2.1:exec (install) @ cloud-marvin ---
> >>>> 
> >>>> [DEBUG] Configuring mojo org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> >>>> from plugin realm
> >>>> ClassRealm[plugin>org.codehaus.mojo:exec-maven-plugin:1.2.1, parent:
> >>>> sun.misc.Launcher$AppClassLoader@5acac268]
> >>>> 
> >>>> [DEBUG] Configuring mojo
> >>>> 'org.codehaus.mojo:exec-maven-plugin:1.2.1:exec' with basic configurator -->
> >>>> 
> >>>> [DEBUG]   (f) arguments = [setup.py, sdist]
> >>>> 
> >>>> [DEBUG]   (f) basedir =
> >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin
> >>>> 
> >>>> [DEBUG]   (f) classpathScope = runtime
> >>>> 
> >>>> [DEBUG]   (f) executable = python
> >>>> 
> >>>> [DEBUG]   (f) longClasspath = false
> >>>> 
> >>>> [DEBUG]   (f) project = MavenProject:
> >>>> org.apache.cloudstack:cloud-marvin:4.3.0-SNAPSHOT @
> >>>> /mnt/hgfs/palo_alto/incubator-cloudstack/tools/marvin/pom.xml
> >>>> 
> >>>> [DEBUG]   (f) session = org.apache.maven.execution.MavenSession@6d3cba41
> >>>> 
> >>>> [DEBUG]   (f) skip = false
> >>>> 
> >>>> [DEBUG] -- end configuration --
> >>>> 
> >>>> [DEBUG] Executing command line: python setup.py sdist
> >>>> 
> >>>> running sdist
> >>>> 
> >>>> running egg_info
> >>>> 
> >>>> writing requirements to Marvin.egg-info/requires.txt
> >>>> 
> >>>> writing Marvin.egg-info/PKG-INFO
> >>>> 
> >>>> writing top-level names to Marvin.egg-info/top_level.txt
> >>>> 
> >>>> writing dependency_links to Marvin.egg-info/dependency_links.txt
> >>>> 
> >>>> writing entry points to Marvin.egg-info/entry_points.txt
> >>>> 
> >>>> reading manifest file 'Marvin.egg-info/SOURCES.txt'
> >>>> 
> >>>> reading manifest template 'MANIFEST.in'
> >>>> 
> >>>> warning: no files found matching '*.txt' under directory 'docs'
> >>>> 
> >>>> writing manifest file 'Marvin.egg-info/SOURCES.txt'
> >>>> 
> >>>> making hard links in Marvin-0.1.0...
> >>>> 
> >>>> hard linking CHANGES.txt -> Marvin-0.1.0
> >>>> 
> >>>> error: Operation not permitted
> >>>> 
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> 
> >>>> [INFO] Reactor Summary:
> >>>> 
> >>>> [INFO]
> >>>> 
> >>>> [INFO] Apache CloudStack ................................. SUCCESS
> >>>> [4.341s]
> >>>> 
> >>>> [INFO] Apache CloudStack Maven Conventions Parent ........ SUCCESS
> >>>> [0.089s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - Managed Context ..... SUCCESS
> >>>> [4.999s]
> >>>> 
> >>>> [INFO] Apache CloudStack Utils ........................... SUCCESS
> >>>> [17.555s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework ....................... SUCCESS
> >>>> [0.125s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS
> >>>> [9.514s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - Configuration ....... SUCCESS
> >>>> [5.700s]
> >>>> 
> >>>> [INFO] Apache CloudStack API ............................. SUCCESS
> >>>> [26.885s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - REST ................ SUCCESS
> >>>> [3.394s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - IPC ................. SUCCESS
> >>>> [8.755s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Engine .................... SUCCESS
> >>>> [0.091s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Engine API ................ SUCCESS
> >>>> [7.934s]
> >>>> 
> >>>> [INFO] Apache CloudStack Core ............................ SUCCESS
> >>>> [13.925s]
> >>>> 
> >>>> [INFO] Apache CloudStack Agents .......................... SUCCESS
> >>>> [7.509s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - Clustering .......... SUCCESS
> >>>> [4.550s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - Jobs ................ SUCCESS
> >>>> [4.811s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS
> >>>> [17.694s]
> >>>> 
> >>>> [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS
> >>>> [2.665s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS
> >>>> [4.491s]
> >>>> 
> >>>> [INFO] Apache CloudStack Server .......................... SUCCESS
> >>>> [56.473s]
> >>>> 
> >>>> [INFO] Apache CloudStack Usage Server .................... SUCCESS
> >>>> [8.747s]
> >>>> 
> >>>> [INFO] Apache XenSource XAPI ............................. SUCCESS
> >>>> [8.695s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS
> >>>> [10.341s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Services .................. SUCCESS
> >>>> [0.207s]
> >>>> 
> >>>> [INFO] Apache CloudStack Secondary Storage Service ....... SUCCESS
> >>>> [5.918s]
> >>>> 
> >>>> [INFO] Apache CloudStack Engine Storage Component ........ SUCCESS
> >>>> [5.974s]
> >>>> 
> >>>> [INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS
> >>>> [5.936s]
> >>>> 
> >>>> [INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS
> >>>> [3.533s]
> >>>> 
> >>>> [INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS
> >>>> [4.206s]
> >>>> 
> >>>> [INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS
> >>>> [2.888s]
> >>>> 
> >>>> [INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS
> >>>> [5.265s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Engine API ................ SUCCESS
> >>>> [2.756s]
> >>>> 
> >>>> [INFO] Apache CloudStack Cloud Engine Service ............ SUCCESS
> >>>> [7.624s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin POM ...................... SUCCESS
> >>>> [1.440s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - API Rate Limit ......... SUCCESS
> >>>> [8.121s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - API Discovery .......... SUCCESS
> >>>> [5.600s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS
> >>>> [3.822s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS
> >>>> [2.641s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Explicit Dedication Processor  SUCCESS
> >>>> [3.097s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment
> >>>> Planner  SUCCESS [2.696s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner
> >>>> SUCCESS [2.624s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Implicit Dedication Planner  SUCCESS
> >>>> [8.390s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Host Allocator Random .. SUCCESS
> >>>> [2.733s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Dedicated Resources .... SUCCESS
> >>>> [7.454s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Hypervisor OracleVM .... SUCCESS
> >>>> [4.439s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Open vSwitch ........... SUCCESS
> >>>> [3.581s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Hypervisor Xen ......... SUCCESS
> >>>> [12.095s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Hypervisor KVM ......... SUCCESS
> >>>> [13.159s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - RabbitMQ Event Bus ..... SUCCESS
> >>>> [2.939s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Hypervisor Baremetal ... SUCCESS
> >>>> [4.963s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Hypervisor UCS ......... SUCCESS
> >>>> [3.429s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Network Elastic Load Balancer  SUCCESS
> >>>> [5.100s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Network Nicira NVP ..... SUCCESS
> >>>> [11.103s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - BigSwitch Virtual Network Segment
> >>>> SUCCESS [7.611s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Midokura Midonet ....... SUCCESS
> >>>> [7.864s]
> >>>> 
> >>>> [INFO] Apache Cloudstack Plugin - Stratosphere SSP ....... SUCCESS
> >>>> [7.125s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Allocator Random  SUCCESS
> >>>> [2.552s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - User Authenticator LDAP  SUCCESS
> >>>> [3.892s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - User Authenticator MD5 . SUCCESS
> >>>> [2.733s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - User Authenticator Plain Text  SUCCESS
> >>>> [2.547s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - User Authenticator SHA256 Salted
> >>>> SUCCESS [33.230s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Dns Notifier Example ... SUCCESS
> >>>> [2.494s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Image S3 ....... SUCCESS
> >>>> [2.864s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Image Swift provider  SUCCESS
> >>>> [2.543s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Image default provider
> >>>> SUCCESS [2.431s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Image sample provider  SUCCESS
> >>>> [2.945s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider
> >>>> SUCCESS [5.323s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Volume default provider
> >>>> SUCCESS [2.771s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Storage Volume sample provider
> >>>> SUCCESS [2.414s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - SNMP Alerts ............ SUCCESS
> >>>> [5.064s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Syslog Alerts .......... SUCCESS
> >>>> [4.563s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Network Internal Load Balancer
> >>>> SUCCESS [10.414s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Network VXLAN .......... SUCCESS
> >>>> [5.421s]
> >>>> 
> >>>> [INFO] Apache CloudStack Plugin - Palo Alto .............. SUCCESS
> >>>> [8.807s]
> >>>> 
> >>>> [INFO] Apache CloudStack Test ............................ SUCCESS
> >>>> [0.586s]
> >>>> 
> >>>> [INFO] Apache CloudStack Console Proxy ................... SUCCESS
> >>>> [0.045s]
> >>>> 
> >>>> [INFO] Apache CloudStack Console Proxy - Server .......... SUCCESS
> >>>> [3.691s]
> >>>> 
> >>>> [INFO] Apache CloudStack System VM ....................... SUCCESS
> >>>> [8.814s]
> >>>> 
> >>>> [INFO] Apache CloudStack Client UI ....................... SUCCESS
> >>>> [31.508s]
> >>>> 
> >>>> [INFO] Apache CloudStack Developer Mode .................. SUCCESS
> >>>> [3.295s]
> >>>> 
> >>>> [INFO] Apache CloudStack Developer Tools ................. SUCCESS
> >>>> [0.135s]
> >>>> 
> >>>> [INFO] Apache CloudStack apidocs ......................... SUCCESS
> >>>> [33.492s]
> >>>> 
> >>>> [INFO] Apache CloudStack marvin .......................... FAILURE
> >>>> [3.828s]
> >>>> 
> >>>> [INFO] Apache CloudStack DevCloud ........................ SKIPPED
> >>>> 
> >>>> [INFO] Apache CloudStack DevCloud-KVM .................... SKIPPED
> >>>> 
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> 
> >>>> [INFO] BUILD FAILURE
> >>>> 
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> 
> >>>> [INFO] Total time: 9:56.659s
> >>>> 
> >>>> [INFO] Finished at: Tue Oct 29 11:08:48 EDT 2013
> >>>> 
> >>>> [INFO] Final Memory: 58M/172M
> >>>> 
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> 
> >>>> [ERROR] Failed to execute goal
> >>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (install) on project
> >>>> cloud-marvin: Command execution failed. Process exited with an error: 1
> >>>> (Exit value: 1) -> [Help 1]
> >>>> 
> >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> >>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (install) on
> >>>> project cloud-marvin: Command execution failed.
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> >>>> 
> >>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> >>>> 
> >>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >>>> 
> >>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >>>> 
> >>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >>>> 
> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >>>> 
> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>> 
> >>>> at
> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>>> 
> >>>> at
> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>>> 
> >>>> at java.lang.reflect.Method.invoke(Method.java:597)
> >>>> 
> >>>> at
> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> >>>> 
> >>>> at
> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >>>> 
> >>>> at
> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> >>>> 
> >>>> at
> >>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> >>>> 
> >>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> >>>> execution failed.
> >>>> 
> >>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
> >>>> 
> >>>> at
> >>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> >>>> 
> >>>> at
> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> >>>> 
> >>>> ... 19 more
> >>>> 
> >>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> >>>> an error: 1 (Exit value: 1)
> >>>> 
> >>>> at
> >>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
> >>>> 
> >>>> at
> >>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
> >>>> 
> >>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
> >>>> 
> >>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
> >>>> 
> >>>> ... 21 more
> >>>> 
> >>>> [ERROR]
> >>>> 
> >>>> [ERROR]
> >>>> 
> >>>> [ERROR] For more information about the errors and possible solutions,
> >>>> please read the following articles:
> >>>> 
> >>>> [ERROR] [Help 1]
> >>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >>>> 
> >>>> [ERROR]
> >>>> 
> >>>> [ERROR] After correcting the problems, you can resume the build with the
> >>>> command
> >>>> 
> >>>> [ERROR]   mvn <goals> -rf :cloud-marvin
> >>>> 
> >>>> 
> >>>> On Fri, Oct 18, 2013 at 7:58 AM, Santhosh Edukulla <
> >>>> santhosh.edukulla@citrix.com> wrote:
> >>>> 
> >>>>> Hello William,
> >>>>> 
> >>>>> 1.   After getting the latest master branch code, I just ran the
> >>>>> command " mvn -P developer,systemvm clean install"  and I could see that
> >>>>> both "commands.xml" file was created  under cs/ tools/apidoc/target/  and
> >>>>> "addImageStore.py" under cs/tools/marvin/marvin/cloudstackAPI/ directory.
> >>>>>  Please check post the command run, whether both were available or not.
> >>>>> 
> >>>>> 2.   Basically, codegeneratory.py under cs/tools/marvin/marvin
> >>>>> directory is the one which based upon apispec file  "commands.xml" if
> >>>>> available  generates the cloudstackAPI and corresponding modules under its
> >>>>> directory.  In case as mentioned under pom.xml, if commands.xml is not
> >>>>> available, it takes the apispec file as  " /etc/cloud/cli/commands.xml". It
> >>>>> also has the option of creating cloudstackAPI/modules from json response
> >>>>> endpoint url " http://ip:8096/client/api?command=listApis", default to
> >>>>> localhost.
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> Thanks!
> >>>>> Santhosh
> >>>>> 
> >>>>> -----Original Message-----
> >>>>> From: williamstevens@gmail.com [mailto:williamstevens@gmail.com] On
> >>>>> Behalf Of Will Stevens
> >>>>> Sent: Friday, October 18, 2013 2:05 AM
> >>>>> To: dev@cloudstack.apache.
> >>>>> Subject: Re: Issues deploying with marvin
> >>>>> 
> >>>>> Note: I pulled from master yesterday...y
> >>>>> 
> >>>>> 
> >>>>> On Thu, Oct 17, 2013 at 4:28 PM, Will Stevens <ws...@cloudops.com>
> >>>>> wrote:
> >>>>> 
> >>>>>> When I run:
> >>>>>> 
> >>>>>> I am getting the following error:
> >>>>>> [DEBUG] Executing command line: python
> >>>>>> ../marvin/marvin/deployDataCenter.py -i devcloud.cfg 5Traceback (most
> >>>>>> recent call last):
> >>>>>>  File "../marvin/marvin/deployDataCenter.py", line 612, in <module>
> >>>>>>    deploy.deploy()
> >>>>>>  File "../marvin/marvin/deployDataCenter.py", line 597, in deploy
> >>>>>>    self.createZones(self.config.zones)
> >>>>>>  File "../marvin/marvin/deployDataCenter.py", line 466, in
> >>>>> createZones
> >>>>>>    self.createSecondaryStorages(zone.secondaryStorages, zoneId)
> >>>>>>  File "../marvin/marvin/deployDataCenter.py", line 176, in
> >>>>>> createSecondaryStorages
> >>>>>>    secondarycmd = addImageStore.addImageStoreCmd()
> >>>>>> NameError: global name 'addImageStore' is not defined [INFO]
> >>>>>> ----------------------------------------------------------------------
> >>>>>> --
> >>>>>> [INFO] BUILD FAILURE
> >>>>>> [INFO]
> >>>>>> ----------------------------------------------------------------------
> >>>>>> --
> >>>>>> 
> >>>>>> I have looked and I can not find where 'addImageStore' is defined.  I
> >>>>>> was expecting it to be imported via the 'from cloudstackAPI import *'
> >>>>>> line, but 'addImageStore.py' is not in that directory.
> >>>>>> 
> >>>>>> I have run 'python setup.py install' again in 'tools/marvin' just to
> >>>>>> make sure it had not changed.
> >>>>>> 
> >>>>>> I ran the following:
> >>>>>> # python -c "import pkg_resources;
> >>>>>> print(pkg_resources.get_distribution('marvin').version)"
> >>>>>> 
> >>>>>> Which returned the version number of: 0.1.0
> >>>>>> 
> >>>>>> What do I need to do to get my environment up to speed?
> >>>>>> 
> >>>>>> Thanks...
> >>>>>> 
> >>>>> 
> >>>> 
> >>>> 
> >>> 
> >> 

-- 
Prasanna.,

------------------------
Powered by BigRock.com