Re: [SOLVED]: RE: Issues deploying with marvin

[Prasanna Santhanam <ts...@apache.org>]

On Thu, Oct 31, 2013 at 06:37:53PM +0000, Santhosh Edukulla wrote:
> 
> Instead of going through these many steps,  I believe the other
> quick solution would be to change "sdist" argument to "install"
> wherever its referencing python setup.py, under
> cs/tools/marvin/pom.xml and run maven command with clean install and
> other arguments. I am assuming it should fix the problem.
> 
Only problem, we would be assuming that the user running mvn also has
root access to install python packages on the system in this case.

> Also, added tag solved to the subject line as well.
> 
> Santhosh
> ________________________________________
> From: Will Stevens [williamstevens@gmail.com]
> Sent: Wednesday, October 30, 2013 12:55 PM
> To: dev@cloudstack.apache.org
> Cc: Sebastien Goasguen
> Subject: Re: Issues deploying with marvin
> 
> ...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
> >> >
> >>
> >

-- 
Prasanna.,

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