RE: RPM build is fixed, sort of...
Hey Edison, No problem, I'll leave it to you then. Cheers, Hugo -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 6:42 AM To: cloudstack-dev@incubator.apache.org Cc: Hugo Trippaers Subject: RPM build is fixed, sort of... Hi Hugo, I reverted three of your patches(1f207506daa1874421b01ad8ea733e6bc8b8ce60/ 79004fc7bc5f24f8bf9c75f7a0b0fef01042db13/ a4f1971e80f2aaf86017ddc989513eefb04265fa), I don't know how to get waf+maven work, but I know how to get ant work right now. Still need to use maven install to download all the deps. waf rpm works right now, but may still have other issues during the rpm install. Seems jasper related jars are not included in the classpath.conf, so you may not login into UI.
conserve mode for network offering
Hi, all I noticed when 'conserve mode' is not checked for a network offering, the guest network created from this offering cannot do port forwarding and load balance if sourceNat is enabled. After checking network.js and wiki [1], I realized it was by design and much complicated than document said: 'Conserve mode. Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network.' Can someone explain why 'conserve mode' behave this way? Thanks. [1] http://wiki.cloudstack.org/display/QA/Network+Offering Regards Mice
RE: maven install failed
Anthony,
Did you download those jars and run install-non-oss.sh like it is explained on
the wiki page?
Cheers,
Hugo
-Original Message-
From: Anthony Xu [mailto:xuefei...@citrix.com]
Sent: Wednesday, September 05, 2012 3:47 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: maven install failed
Still fail
ax:~/vmops/incubator-cloudstack$ mvn -P deps -pl deps [INFO] Scanning for
projects...
[INFO]
[INFO] Building Apache CloudStack Dependencies
[INFO]task-segment: [install]
[INFO]
[WARNING] The parameter expression: 'project.build.resources' used in
mojo: 'process' has been deprecated. Use 'project.resources' instead.
[INFO] [remote-resources:process {execution: default}]
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim/1.0/vmware-vim-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
vim:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim25/1.0/vmware-vim25-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
vim25:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
apputils/1.0/vmware-apputils-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
apputils:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/f5/icontrol/1.0/icontrol-
1.0.pom
[INFO] Unable to find resource 'com.cloud.com.f5:icontrol:pom:1.0' in
repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/libvirt/libvirt/0.4.8/libvirt-0.4.8.pom
[INFO] Unable to find resource 'org.libvirt:libvirt:pom:0.4.8' in repository
central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/netapp/manageontap/1.
0/manageontap-1.0.pom
[INFO] Unable to find resource
'com.cloud.com.netapp:manageontap:pom:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler/1.0/netsc
aler-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.citrix:netscaler:pom:1.0' in
repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler-
sdx/1.0/netscaler-sdx-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-sdx:pom:1.0'
in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/netapp/manageontap/1.
0/manageontap-1.0.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler/1.0/netsc
aler-1.0.jar
Downloading:
http://repo1.maven.org/maven2/org/libvirt/libvirt/0.4.8/libvirt-0.4.8.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/f5/icontrol/1.0/icontrol-
1.0.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim/1.0/vmware-vim-1.0.jar
[INFO] Unable to find resource 'com.cloud.com.netapp:manageontap:jar:1.0'
in repository central (http://repo1.maven.org/maven2) [INFO] Unable to
find resource 'com.cloud.com.citrix:netscaler:jar:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler-
sdx/1.0/netscaler-sdx-1.0.jar
[INFO] Unable to find resource 'org.libvirt:libvirt:jar:0.4.8' in repository
central (http://repo1.maven.org/maven2) [INFO] Unable to find resource
'com.cloud.com.vmware:vmware-vim:jar:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim25/1.0/vmware-vim25-1.0.jar
[INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-sdx:jar:1.0' in
repository central (
-Original Message-
From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
Sent: Tuesday, September 04, 2012 6:26 PM
To: CloudStack DeveloperList
Subject: Re: maven install failed
Check this:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+M
a
ven
You can do mvn -P deps -pl deps
On 9/4/12 5:51 PM, Anthony Xu xuefei...@citrix.com wrote:
I'm using ubuntu 12.04 64 bit.
Execution of maven install under directory deps failed.
Does anyone meet this issue?
Thanks
Anthony
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
apputils/1.0/vmw
are-apputils-1.0.jar
[INFO] Unable to find resource
'com.cloud.com.citrix:netscaler-sdx:jar:1.0' in repository central
(http://repo1.maven.org/maven2)
[INFO] Unable to find resource
'com.cloud.com.vmware:vmware-apputils:jar:1.0' in repository central
(http://repo1.maven.org/maven2)
RE: RPM build is fixed, sort of...
Hey Edison, I still get an error when building rpms with your changes: Processing files: cloud-utils-4.0.0-0.1.el6.maven.x86_64 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.kvoZ6x + umask 022 + cd /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILD + cd cloud-4.0.0 + DOCDIR=/home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + export DOCDIR + rm -rf /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + /bin/mkdir -p /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr README.html /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr debian/copyright /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + exit 0 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires: /usr/bin/env Obsoletes: vmops-utils 4.0.0-0.1.el6.maven Processing files: cloud-client-ui-4.0.0-0.1.el6.maven.x86_64 Requires(interp): /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires(pre): /bin/sh Obsoletes: vmops-client-ui 4.0.0-0.1.el6.maven Processing files: cloud-server-4.0.0-0.1.el6.maven.x86_64 Provides: config(cloud-server) = 4.0.0-0.1.el6.maven Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Obsoletes: vmops-server 4.0.0-0.1.el6.maven Processing files: cloud-agent-scripts-4.0.0-0.1.el6.maven.x86_64 Processing files: cloud-python-4.0.0-0.1.el6.maven.x86_64 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires: /bin/bash /usr/bin/python python(abi) = 2.6 Processing files: cloud-deps-4.0.0-0.1.el6.maven.x86_64 error: File not found: /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319-1.jar RPM build errors: File not found: /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319-1.jar Cheers, Hugo -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 8:24 AM To: 'Edison Su'; cloudstack-dev@incubator.apache.org Subject: RE: RPM build is fixed, sort of... Hey Edison, No problem, I'll leave it to you then. Cheers, Hugo -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 6:42 AM To: cloudstack-dev@incubator.apache.org Cc: Hugo Trippaers Subject: RPM build is fixed, sort of... Hi Hugo, I reverted three of your patches(1f207506daa1874421b01ad8ea733e6bc8b8ce60/ 79004fc7bc5f24f8bf9c75f7a0b0fef01042db13/ a4f1971e80f2aaf86017ddc989513eefb04265fa), I don't know how to get waf+maven work, but I know how to get ant work right now. Still need to use maven install to download all the deps. waf rpm works right now, but may still have other issues during the rpm install. Seems jasper related jars are not included in the classpath.conf, so you may not login into UI.
Re: maven install failed
On 09/05/2012 08:38 AM, Hugo Trippaers wrote:
Anthony,
Did you download those jars and run install-non-oss.sh like it is explained on
the wiki page?
I'm running into the same problem. I've ran install-non-oss.sh, but it
keeps complaining about the VMWare JAR files which are missing.
For example:
[INFO] [install:install-file {execution: default-cli}]
[INFO] Installing /usr/src/cloudstack/deps/vmware-apputils.jar to
/root/.m2/repository/com/cloud/com/vmware/vmware-apputils/1.0/vmware-apputils-1.0.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact
'com.cloud.com.vmware:vmware-apputils:jar': Error installing artifact:
File /usr/src/cloudstack/deps/vmware-apputils.jar does not exist
Wido
Cheers,
Hugo
-Original Message-
From: Anthony Xu [mailto:xuefei...@citrix.com]
Sent: Wednesday, September 05, 2012 3:47 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: maven install failed
Still fail
ax:~/vmops/incubator-cloudstack$ mvn -P deps -pl deps [INFO] Scanning for
projects...
[INFO]
[INFO] Building Apache CloudStack Dependencies
[INFO]task-segment: [install]
[INFO]
[WARNING] The parameter expression: 'project.build.resources' used in
mojo: 'process' has been deprecated. Use 'project.resources' instead.
[INFO] [remote-resources:process {execution: default}]
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim/1.0/vmware-vim-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
vim:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim25/1.0/vmware-vim25-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
vim25:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
apputils/1.0/vmware-apputils-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
apputils:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/f5/icontrol/1.0/icontrol-
1.0.pom
[INFO] Unable to find resource 'com.cloud.com.f5:icontrol:pom:1.0' in
repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/libvirt/libvirt/0.4.8/libvirt-0.4.8.pom
[INFO] Unable to find resource 'org.libvirt:libvirt:pom:0.4.8' in repository
central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/netapp/manageontap/1.
0/manageontap-1.0.pom
[INFO] Unable to find resource
'com.cloud.com.netapp:manageontap:pom:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler/1.0/netsc
aler-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.citrix:netscaler:pom:1.0' in
repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler-
sdx/1.0/netscaler-sdx-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-sdx:pom:1.0'
in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/netapp/manageontap/1.
0/manageontap-1.0.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler/1.0/netsc
aler-1.0.jar
Downloading:
http://repo1.maven.org/maven2/org/libvirt/libvirt/0.4.8/libvirt-0.4.8.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/f5/icontrol/1.0/icontrol-
1.0.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim/1.0/vmware-vim-1.0.jar
[INFO] Unable to find resource 'com.cloud.com.netapp:manageontap:jar:1.0'
in repository central (http://repo1.maven.org/maven2) [INFO] Unable to
find resource 'com.cloud.com.citrix:netscaler:jar:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler-
sdx/1.0/netscaler-sdx-1.0.jar
[INFO] Unable to find resource 'org.libvirt:libvirt:jar:0.4.8' in repository
central (http://repo1.maven.org/maven2) [INFO] Unable to find resource
'com.cloud.com.vmware:vmware-vim:jar:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim25/1.0/vmware-vim25-1.0.jar
[INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-sdx:jar:1.0' in
repository central (
-Original Message-
From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
Sent: Tuesday, September 04, 2012 6:26 PM
To: CloudStack DeveloperList
Subject: Re: maven install failed
Check this:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+M
a
ven
RE: maven install failed
Hey Wido,
Heb je de vmware.jars wel eerst in de deps directory gezet?
Cheers,
Hugo
-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: Wednesday, September 05, 2012 11:34 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: maven install failed
On 09/05/2012 08:38 AM, Hugo Trippaers wrote:
Anthony,
Did you download those jars and run install-non-oss.sh like it is explained
on the wiki page?
I'm running into the same problem. I've ran install-non-oss.sh, but it keeps
complaining about the VMWare JAR files which are missing.
For example:
[INFO] [install:install-file {execution: default-cli}] [INFO] Installing
/usr/src/cloudstack/deps/vmware-apputils.jar to
/root/.m2/repository/com/cloud/com/vmware/vmware-
apputils/1.0/vmware-apputils-1.0.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact
'com.cloud.com.vmware:vmware-apputils:jar': Error installing artifact:
File /usr/src/cloudstack/deps/vmware-apputils.jar does not exist
Wido
Cheers,
Hugo
-Original Message-
From: Anthony Xu [mailto:xuefei...@citrix.com]
Sent: Wednesday, September 05, 2012 3:47 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: maven install failed
Still fail
ax:~/vmops/incubator-cloudstack$ mvn -P deps -pl deps [INFO] Scanning
for projects...
[INFO]
-
--- [INFO] Building Apache CloudStack Dependencies
[INFO]task-segment: [install]
[INFO]
-
--- [WARNING] The parameter expression: 'project.build.resources'
used in
mojo: 'process' has been deprecated. Use 'project.resources' instead.
[INFO] [remote-resources:process {execution: default}]
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim/1.0/vmware-vim-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
vim:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim25/1.0/vmware-vim25-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
vim25:pom:1.0' in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
apputils/1.0/vmware-apputils-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.vmware:vmware-
apputils:pom:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/f5/icontrol/1.0/icontrol-
1.0.pom
[INFO] Unable to find resource 'com.cloud.com.f5:icontrol:pom:1.0' in
repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/libvirt/libvirt/0.4.8/libvirt-0.4.8
.pom [INFO] Unable to find resource 'org.libvirt:libvirt:pom:0.4.8'
in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/netapp/manageontap/1.
0/manageontap-1.0.pom
[INFO] Unable to find resource
'com.cloud.com.netapp:manageontap:pom:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler/1.0/nets
c
aler-1.0.pom
[INFO] Unable to find resource
'com.cloud.com.citrix:netscaler:pom:1.0' in repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler-
sdx/1.0/netscaler-sdx-1.0.pom
[INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-
sdx:pom:1.0'
in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/netapp/manageontap/1.
0/manageontap-1.0.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler/1.0/nets
c
aler-1.0.jar
Downloading:
http://repo1.maven.org/maven2/org/libvirt/libvirt/0.4.8/libvirt-0.4.8
.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/f5/icontrol/1.0/icontrol-
1.0.jar
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware-
vim/1.0/vmware-vim-1.0.jar
[INFO] Unable to find resource
'com.cloud.com.netapp:manageontap:jar:1.0'
in repository central (http://repo1.maven.org/maven2) [INFO] Unable
to find resource 'com.cloud.com.citrix:netscaler:jar:1.0' in
repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/com/cloud/com/citrix/netscaler-
sdx/1.0/netscaler-sdx-1.0.jar
[INFO] Unable to find resource 'org.libvirt:libvirt:jar:0.4.8' in
repository central (http://repo1.maven.org/maven2) [INFO] Unable to
find resource 'com.cloud.com.vmware:vmware-vim:jar:1.0' in repository
central
Review Request: maven without -Dnonoss build dependency fix
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6923/ --- Review request for cloudstack. Description --- I run mvn without -Dnonoss and got errors about vmware jar dependencies (with empty m2 local repository). [ERROR] Failed to execute goal on project cloud-vmware-base: Could not resolve dependencies for project org.apache.cloudstack:cloud-vmware-base:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware-vim:jar:1.0 in central (http://repo.maven.apache.org/maven2) - [Help 1] Here I attach a patch to fix this. Diffs - pom.xml 99b1177 Diff: https://reviews.apache.org/r/6923/diff/ Testing --- mvn mvn test Thanks, Hiroaki Kawai
Re: Review Request: maven without -Dnonoss build dependency fix
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6923/#review11060 --- Heya, This works, but a better fix would be to figure out why these targets depend on those vmwre tools. We need to be able to distribute console-proxy and build it without any dependencies on vmware stuff. Can you rewrite this patch to remove the dependencies on those three libs to vmware jars? If there are any errors we'll need to fix that. Cheers, Hugo - Hugo Trippaers On Sept. 5, 2012, 9:39 a.m., Hiroaki Kawai wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6923/ --- (Updated Sept. 5, 2012, 9:39 a.m.) Review request for cloudstack. Description --- I run mvn without -Dnonoss and got errors about vmware jar dependencies (with empty m2 local repository). [ERROR] Failed to execute goal on project cloud-vmware-base: Could not resolve dependencies for project org.apache.cloudstack:cloud-vmware-base:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware-vim:jar:1.0 in central (http://repo.maven.apache.org/maven2) - [Help 1] Here I attach a patch to fix this. Diffs - pom.xml 99b1177 Diff: https://reviews.apache.org/r/6923/diff/ Testing --- mvn mvn test Thanks, Hiroaki Kawai
Re: Review Request: maven without -Dnonoss build dependency fix
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6923/ --- (Updated Sept. 5, 2012, 10:08 a.m.) Review request for cloudstack. Changes --- console-proxy and patches module seems just does not depend on those vmware jars, so I removed the dependencies. Description --- I run mvn without -Dnonoss and got errors about vmware jar dependencies (with empty m2 local repository). [ERROR] Failed to execute goal on project cloud-vmware-base: Could not resolve dependencies for project org.apache.cloudstack:cloud-vmware-base:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware-vim:jar:1.0 in central (http://repo.maven.apache.org/maven2) - [Help 1] Here I attach a patch to fix this. Diffs (updated) - console-proxy/pom.xml 070beb8 patches/pom.xml efe61af pom.xml 99b1177 Diff: https://reviews.apache.org/r/6923/diff/ Testing --- mvn mvn test Thanks, Hiroaki Kawai
RPM build fixed (maven-waf branch)
Heya, I've made a new branch 'maven-waf' containing the stuff needed to build RPM's using the maven and waf. I've fixed the issues that prevented building from a clean tree directly, so it should be complete now. With the exeption of awsapi, see my earlier mail on that one. Cheers, Hugo
Re: Review Request: maven without -Dnonoss build dependency fix
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6923/#review11061 --- Heya, I'll take this into the new maven-waf branch for now until the whole maven build is stable enough for a merge into master. Thanks for the patch :-) Cheers, Hugo - Hugo Trippaers On Sept. 5, 2012, 10:08 a.m., Hiroaki Kawai wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6923/ --- (Updated Sept. 5, 2012, 10:08 a.m.) Review request for cloudstack. Description --- I run mvn without -Dnonoss and got errors about vmware jar dependencies (with empty m2 local repository). [ERROR] Failed to execute goal on project cloud-vmware-base: Could not resolve dependencies for project org.apache.cloudstack:cloud-vmware-base:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware-vim:jar:1.0 in central (http://repo.maven.apache.org/maven2) - [Help 1] Here I attach a patch to fix this. Diffs - console-proxy/pom.xml 070beb8 patches/pom.xml efe61af pom.xml 99b1177 Diff: https://reviews.apache.org/r/6923/diff/ Testing --- mvn mvn test Thanks, Hiroaki Kawai
RE: RPM build fixed (maven-waf branch)
Hi Hugo, Regarding Awsapi how are you planning to go ahead ? Thanks Rajesh Battala -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 3:43 PM To: cloudstack-dev@incubator.apache.org Subject: RPM build fixed (maven-waf branch) Heya, I've made a new branch 'maven-waf' containing the stuff needed to build RPM's using the maven and waf. I've fixed the issues that prevented building from a clean tree directly, so it should be complete now. With the exeption of awsapi, see my earlier mail on that one. Cheers, Hugo
Review Request: maven kvm hypervisor plugin build without -Dnonoss
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6925/ --- Review request for cloudstack. Description --- Adding libvirt.org maven repository in pom.xml will automate the build, and we can run kvm hypervisor plugin build without -Dnonoss. I also added exec:java configuration so that we can test the hypervisor code easily. Diffs - plugins/hypervisors/kvm/pom.xml 8cdaa86 plugins/pom.xml 2a6ca31 Diff: https://reviews.apache.org/r/6925/diff/ Testing --- mvn mvn test Thanks, Hiroaki Kawai
RE: RPM build fixed (maven-waf branch)
Hey Rajesh, As far as I understand (and please correct me if I'm wrong) awsapi consists of three parts. The generated code for ec2, the generated code for s3 and our code. I would like to split this in three subprojects for maven. Two using the maven axis2 plugins to generate the classes and a third that uses the output from the first two (the .mar and .aar files) and makes the webapp by adding our code. Does that make sense? Cheers, Hugo -Original Message- From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] Sent: Wednesday, September 05, 2012 12:32 PM To: cloudstack-dev@incubator.apache.org Subject: RE: RPM build fixed (maven-waf branch) Hi Hugo, Regarding Awsapi how are you planning to go ahead ? Thanks Rajesh Battala -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 3:43 PM To: cloudstack-dev@incubator.apache.org Subject: RPM build fixed (maven-waf branch) Heya, I've made a new branch 'maven-waf' containing the stuff needed to build RPM's using the maven and waf. I've fixed the issues that prevented building from a clean tree directly, so it should be complete now. With the exeption of awsapi, see my earlier mail on that one. Cheers, Hugo
Re: Review Request: maven kvm hypervisor plugin build without -Dnonoss
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6925/#review11062 --- Hey Hiroaki, Looks good, but i believe that was another reason why we could not include the libvirt jar as a dependency in the oss branch. Something license related, but i'll have to check the archives to check what is was. Next to that, i would like to avoid putting repositories into our poms. Ideally everything should be available from central (or from a location that we control). I known libvirt is there, but version 0.4.8 is not available yet from central. - Hugo Trippaers On Sept. 5, 2012, 10:38 a.m., Hiroaki Kawai wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6925/ --- (Updated Sept. 5, 2012, 10:38 a.m.) Review request for cloudstack. Description --- Adding libvirt.org maven repository in pom.xml will automate the build, and we can run kvm hypervisor plugin build without -Dnonoss. I also added exec:java configuration so that we can test the hypervisor code easily. Diffs - plugins/hypervisors/kvm/pom.xml 8cdaa86 plugins/pom.xml 2a6ca31 Diff: https://reviews.apache.org/r/6925/diff/ Testing --- mvn mvn test Thanks, Hiroaki Kawai
Need some clarification on MYSQL connector (RE: Review Request: CS-15694:Remove MYSQL connector. Added the explicit class path for mysql connector which will call the jar from the desired location)
Hello Hugo/Chip,
These are the review comments I have received so far.
- For build-cloud.properties, that line should be optional. This means add a
'#' in front of it and others an make it required when copying it into override.
- The change for developer.xml to read in the build-cloud.xml should be done as
a precondition to all build targets.
- The change does not take into account that the file may be on the class path
and so the property value should only be optional. Here it made it explicit.
- Also, we need to add the mysql connector as a rpm dependency. That change is
not in.
Hugo I did a quick fix to get the build working again, just pushed the
commit to master. The mysql connector rpm is already installed on the Jenkins
server, I just modified the scripts to it is picked up by the build.
I can add it to the spec file for rpm based distro's. I think it should
be added to the client rpm.
I see that you have added the class path explicitly in order to resolve this
temporarily.
# Add mysql jar from mysql-connector-java package to CP
# for Jenkins
CP=${CP}${PATHSEP}/usr/share/java/mysql-connector-java.jar
Also, I have seen that you have added that rpm in ‘cloud.spec’ as well.
Since you are calling mysql-connector explicitly from ‘deploy-db-dev.sh’
class-path, the changes from ‘build-cloud.properties’ and ‘developer.xml’ are
not required from my patch. Please correct me if I am wrong.
If everything is fine, shall we close this topic. Please share if anyone have
any comments?
Thanks,
Pradeep.S
-Original Message-
From: Alex Huang
[mailto:nore...@reviews.apache.org]mailto:[mailto:nore...@reviews.apache.org]
On Behalf Of Alex Huang
Sent: Friday, August 31, 2012 8:37 PM
To: David Nalley; Alex Huang
Cc: cloudstack; Pradeep Soundararajan
Subject: Re: Review Request: CS-15694:Remove MYSQL connector. Added the
explicit class path for mysql connector which will call the jar from the
desired location
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/#review10943
---
Also, we need to add the mysql connector as a rpm dependency. That change is
not in.
- Alex Huang
On Aug. 24, 2012, 10:19 a.m., Pradeep Soundararajan wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/
---
(Updated Aug. 24, 2012, 10:19 a.m.)
Review request for cloudstack, David Nalley and Alex Huang.
Description
---
CS-15694:Remove MYSQL connector. Added the explicit class path for mysql
connector which will call the jar from the desired location
Diffs
-
build/build-cloud.properties 552de7f74db7b715da70cc48ff4dc8945fa066f8
build/developer.xml f2e5aa6463ec849a3e97343e82423ff0ac62
setup/db/deploy-db-dev.sh f149e9efd029bd311b1d247e21764b9103fd01d9
Diff: https://reviews.apache.org/r/6752/diff/
Testing
---
Executed: ant build-all deploy-server deploydb successfully.
Thanks,
Pradeep Soundararajan
Re: Need some clarification on MYSQL connector (RE: Review Request: CS-15694:Remove MYSQL connector. Added the explicit class path for mysql connector which will call the jar from the desired location
On Wed, Sep 5, 2012 at 10:08 AM, Pradeep Soundararajan
pradeep.soundarara...@citrix.com wrote:
Hello Hugo/Chip,
These are the review comments I have received so far.
- For build-cloud.properties, that line should be optional. This means add a
'#' in front of it and others an make it required when copying it into
override.
- The change for developer.xml to read in the build-cloud.xml should be done
as a precondition to all build targets.
- The change does not take into account that the file may be on the class
path and so the property value should only be optional. Here it made it
explicit.
- Also, we need to add the mysql connector as a rpm dependency. That change
is not in.
Hugo I did a quick fix to get the build working again, just pushed the
commit to master. The mysql connector rpm is already installed on the Jenkins
server, I just modified the scripts to it is picked up by the build.
I can add it to the spec file for rpm based distro's. I think it
should be added to the client rpm.
I see that you have added the class path explicitly in order to resolve this
temporarily.
# Add mysql jar from mysql-connector-java package to CP
# for Jenkins
CP=${CP}${PATHSEP}/usr/share/java/mysql-connector-java.jar
Also, I have seen that you have added that rpm in ‘cloud.spec’ as well.
Since you are calling mysql-connector explicitly from ‘deploy-db-dev.sh’
class-path, the changes from ‘build-cloud.properties’ and ‘developer.xml’ are
not required from my patch. Please correct me if I am wrong.
If everything is fine, shall we close this topic. Please share if anyone have
any comments?
I *think* that's right. Let's see how the Maven build process shakes
out, since this is actually tied to that as well. We know that
mysql-connector needs to be a system dependency, and not be
distributed with the ASF release.
One item that does come to mind though... shouldn't it be included in
the DEB packages too? Can you add that?
Thanks,
Pradeep.S
-Original Message-
From: Alex Huang
[mailto:nore...@reviews.apache.org]mailto:[mailto:nore...@reviews.apache.org]
On Behalf Of Alex Huang
Sent: Friday, August 31, 2012 8:37 PM
To: David Nalley; Alex Huang
Cc: cloudstack; Pradeep Soundararajan
Subject: Re: Review Request: CS-15694:Remove MYSQL connector. Added the
explicit class path for mysql connector which will call the jar from the
desired location
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/#review10943
---
Also, we need to add the mysql connector as a rpm dependency. That change is
not in.
- Alex Huang
On Aug. 24, 2012, 10:19 a.m., Pradeep Soundararajan wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/
---
(Updated Aug. 24, 2012, 10:19 a.m.)
Review request for cloudstack, David Nalley and Alex Huang.
Description
---
CS-15694:Remove MYSQL connector. Added the explicit class path for mysql
connector which will call the jar from the desired location
Diffs
-
build/build-cloud.properties 552de7f74db7b715da70cc48ff4dc8945fa066f8
build/developer.xml f2e5aa6463ec849a3e97343e82423ff0ac62
setup/db/deploy-db-dev.sh f149e9efd029bd311b1d247e21764b9103fd01d9
Diff: https://reviews.apache.org/r/6752/diff/
Testing
---
Executed: ant build-all deploy-server deploydb successfully.
Thanks,
Pradeep Soundararajan
Re: Need some clarification on MYSQL connector (RE: Review Request: CS-15694:Remove MYSQL connector. Added the explicit class path for mysql connector which will call the jar from the desired location
On 09/05/2012 04:17 PM, Chip Childers wrote:
On Wed, Sep 5, 2012 at 10:08 AM, Pradeep Soundararajan
pradeep.soundarara...@citrix.com wrote:
Hello Hugo/Chip,
These are the review comments I have received so far.
- For build-cloud.properties, that line should be optional. This means add a
'#' in front of it and others an make it required when copying it into override.
- The change for developer.xml to read in the build-cloud.xml should be done as
a precondition to all build targets.
- The change does not take into account that the file may be on the class path
and so the property value should only be optional. Here it made it explicit.
- Also, we need to add the mysql connector as a rpm dependency. That change is
not in.
Hugo I did a quick fix to get the build working again, just pushed the
commit to master. The mysql connector rpm is already installed on the Jenkins server,
I just modified the scripts to it is picked up by the build.
I can add it to the spec file for rpm based distro's. I think it
should be added to the client rpm.
I see that you have added the class path explicitly in order to resolve this
temporarily.
# Add mysql jar from mysql-connector-java package to CP
# for Jenkins
CP=${CP}${PATHSEP}/usr/share/java/mysql-connector-java.jar
Also, I have seen that you have added that rpm in ‘cloud.spec’ as well.
Since you are calling mysql-connector explicitly from ‘deploy-db-dev.sh’
class-path, the changes from ‘build-cloud.properties’ and ‘developer.xml’ are
not required from my patch. Please correct me if I am wrong.
If everything is fine, shall we close this topic. Please share if anyone have
any comments?
I *think* that's right. Let's see how the Maven build process shakes
out, since this is actually tied to that as well. We know that
mysql-connector needs to be a system dependency, and not be
distributed with the ASF release.
One item that does come to mind though... shouldn't it be included in
the DEB packages too? Can you add that?
Ubuntu and Debian both ship the MySQL connector in a package. I already
added a dependency for that:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=9064236879dc9f2f11538d891271545e1ff10e9c
Wido
Thanks,
Pradeep.S
-Original Message-
From: Alex Huang
[mailto:nore...@reviews.apache.org]mailto:[mailto:nore...@reviews.apache.org]
On Behalf Of Alex Huang
Sent: Friday, August 31, 2012 8:37 PM
To: David Nalley; Alex Huang
Cc: cloudstack; Pradeep Soundararajan
Subject: Re: Review Request: CS-15694:Remove MYSQL connector. Added the
explicit class path for mysql connector which will call the jar from the
desired location
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/#review10943
---
Also, we need to add the mysql connector as a rpm dependency. That change is
not in.
- Alex Huang
On Aug. 24, 2012, 10:19 a.m., Pradeep Soundararajan wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/
---
(Updated Aug. 24, 2012, 10:19 a.m.)
Review request for cloudstack, David Nalley and Alex Huang.
Description
---
CS-15694:Remove MYSQL connector. Added the explicit class path for mysql
connector which will call the jar from the desired location
Diffs
-
build/build-cloud.properties 552de7f74db7b715da70cc48ff4dc8945fa066f8
build/developer.xml f2e5aa6463ec849a3e97343e82423ff0ac62
setup/db/deploy-db-dev.sh f149e9efd029bd311b1d247e21764b9103fd01d9
Diff: https://reviews.apache.org/r/6752/diff/
Testing
---
Executed: ant build-all deploy-server deploydb successfully.
Thanks,
Pradeep Soundararajan
Re: Review Request: CS-10219 Add option to set login attempts to portal.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6858/ --- (Updated Sept. 5, 2012, 2:56 p.m.) Review request for cloudstack, Devdeep Singh, Nitin Mehta, and Alena Prokharchyk. Changes --- Changes done in accordance with review comments. Description --- Added global setting login.attempts.allowed which defines the maximum incorrect password attempts allowed. Also after the maximum attempts are reached the user account is disabled. This addresses bug CS-10219. Diffs (updated) - core/src/com/cloud/user/UserAccountVO.java 5e7c018 server/src/com/cloud/configuration/Config.java ebcd070 server/src/com/cloud/user/AccountManagerImpl.java 38153f3 setup/db/create-schema.sql fa933e3 setup/db/db/schema-302to40.sql aaf23e6 Diff: https://reviews.apache.org/r/6858/diff/ Testing --- Verified locally. Thanks, saksham srivastava
Re: Review Request: CS-10219 Add option to set login attempts to portal.
On Sept. 3, 2012, 5:28 p.m., Nitin Mehta wrote: server/src/com/cloud/user/AccountManagerImpl.java, line 427 https://reviews.apache.org/r/6858/diff/3/?file=149072#file149072line427 The function signature should be something like this :- updateLoginAttempts(Long accountId, int failedLoginAttempts , boolean isDisableAllowed) Changed the name of variables to attempts and toDisable. On Sept. 3, 2012, 5:28 p.m., Nitin Mehta wrote: server/src/com/cloud/user/AccountManagerImpl.java, line 1029 https://reviews.apache.org/r/6858/diff/3/?file=149072#file149072line1029 Dont you have to do this for all the users belonging to this account ? No, the aim is only to enable the login attempts of that particular user. All users have independent login_attempts irrespective of their account. On Sept. 3, 2012, 5:28 p.m., Nitin Mehta wrote: server/src/com/cloud/user/AccountManagerImpl.java, line 1859 https://reviews.apache.org/r/6858/diff/3/?file=149072#file149072line1859 The value can be 0 meaning for the 1st incorrect login u disable the account 0 means login in not allowed.1 means a single attempt is provided. - saksham --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6858/#review10998 --- On Sept. 5, 2012, 2:56 p.m., saksham srivastava wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6858/ --- (Updated Sept. 5, 2012, 2:56 p.m.) Review request for cloudstack, Devdeep Singh, Nitin Mehta, and Alena Prokharchyk. Description --- Added global setting login.attempts.allowed which defines the maximum incorrect password attempts allowed. Also after the maximum attempts are reached the user account is disabled. This addresses bug CS-10219. Diffs - core/src/com/cloud/user/UserAccountVO.java 5e7c018 server/src/com/cloud/configuration/Config.java ebcd070 server/src/com/cloud/user/AccountManagerImpl.java 38153f3 setup/db/create-schema.sql fa933e3 setup/db/db/schema-302to40.sql aaf23e6 Diff: https://reviews.apache.org/r/6858/diff/ Testing --- Verified locally. Thanks, saksham srivastava
Re: Review Request: CS-10219 Add option to set login attempts to portal.
On Sept. 4, 2012, 4:05 a.m., Vijay Venkatachalam wrote: server/src/com/cloud/user/AccountManagerImpl.java, line 1869 https://reviews.apache.org/r/6858/diff/3/?file=149072#file149072line1869 Your intentions are good to give a custom log on the last erroneous login attempt. But, the message says that you are disabling the account (it should be user), which is not true. Also, you might want to throw an Exception with a message similar to the special log message and not just log return null. Returning null will give a generic message to user - 'please provide valid credentials'. Changed the log message. Using user instead of account. - saksham --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6858/#review11006 --- On Sept. 5, 2012, 2:56 p.m., saksham srivastava wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6858/ --- (Updated Sept. 5, 2012, 2:56 p.m.) Review request for cloudstack, Devdeep Singh, Nitin Mehta, and Alena Prokharchyk. Description --- Added global setting login.attempts.allowed which defines the maximum incorrect password attempts allowed. Also after the maximum attempts are reached the user account is disabled. This addresses bug CS-10219. Diffs - core/src/com/cloud/user/UserAccountVO.java 5e7c018 server/src/com/cloud/configuration/Config.java ebcd070 server/src/com/cloud/user/AccountManagerImpl.java 38153f3 setup/db/create-schema.sql fa933e3 setup/db/db/schema-302to40.sql aaf23e6 Diff: https://reviews.apache.org/r/6858/diff/ Testing --- Verified locally. Thanks, saksham srivastava
Re: Review Request: CS-10219 Add option to set login attempts to portal.
Just a note on this for the future - most of the penetration testing teams[1] out there now will attempt a dictionary attack not by trying different passwords with the same username, but by trying the same password across the 1000 most common usernames. Would be nice if we could track failed logins across multiple usernames (maybe for 4.1 ;) ) John 1: Malicious users are doing it as well, but depending on the CS user, they may (unfortunately) care more about the pen test report than the hacker… On Sep 5, 2012, at 7:56 AM, saksham srivastava saksham.srivast...@citrix.commailto:saksham.srivast...@citrix.com wrote: On Sept. 3, 2012, 5:28 p.m., Nitin Mehta wrote: server/src/com/cloud/user/AccountManagerImpl.java, line 427 https://reviews.apache.org/r/6858/diff/3/?file=149072#file149072line427 The function signature should be something like this :- updateLoginAttempts(Long accountId, int failedLoginAttempts , boolean isDisableAllowed) Changed the name of variables to attempts and toDisable. On Sept. 3, 2012, 5:28 p.m., Nitin Mehta wrote: server/src/com/cloud/user/AccountManagerImpl.java, line 1029 https://reviews.apache.org/r/6858/diff/3/?file=149072#file149072line1029 Dont you have to do this for all the users belonging to this account ? No, the aim is only to enable the login attempts of that particular user. All users have independent login_attempts irrespective of their account. On Sept. 3, 2012, 5:28 p.m., Nitin Mehta wrote: server/src/com/cloud/user/AccountManagerImpl.java, line 1859 https://reviews.apache.org/r/6858/diff/3/?file=149072#file149072line1859 The value can be 0 meaning for the 1st incorrect login u disable the account 0 means login in not allowed.1 means a single attempt is provided. - saksham --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6858/#review10998 --- On Sept. 5, 2012, 2:56 p.m., saksham srivastava wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6858/ --- (Updated Sept. 5, 2012, 2:56 p.m.) Review request for cloudstack, Devdeep Singh, Nitin Mehta, and Alena Prokharchyk. Description --- Added global setting login.attempts.allowed which defines the maximum incorrect password attempts allowed. Also after the maximum attempts are reached the user account is disabled. This addresses bug CS-10219. Diffs - core/src/com/cloud/user/UserAccountVO.java 5e7c018 server/src/com/cloud/configuration/Config.java ebcd070 server/src/com/cloud/user/AccountManagerImpl.java 38153f3 setup/db/create-schema.sql fa933e3 setup/db/db/schema-302to40.sql aaf23e6 Diff: https://reviews.apache.org/r/6858/diff/ Testing --- Verified locally. Thanks, saksham srivastava Stratosechttp://stratosec.co - Secure Infrastructure as a Service o: 415.315.9385 @johnlkinsellahttp://twitter.com/johnlkinsella
[jira] [Created] (CLOUDSTACK-11) Not able to install ASF 4.0 on Rhel 6.2
Abhinav Roy created CLOUDSTACK-11: - Summary: Not able to install ASF 4.0 on Rhel 6.2 Key: CLOUDSTACK-11 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-11 Project: CloudStack Issue Type: Bug Components: Install and Setup Affects Versions: pre-4.0.0 Environment: Platform : Rhel 6.2 CloudStack build : asf4.0.rpm.tar Reporter: Abhinav Roy Priority: Blocker Fix For: pre-4.0.0 Steps Executed :- 1. Copied the tar file asf4.0.rpm.tar on the rhel machine.--- It was successful 2. Untar the file. --- It was successful 3. rpm -Uvh *.rpm --- This gave following output error: Failed dependencies: /usr/sbin/libvirtd is needed by cloud-agent-4.0-1.el6.x86_64 ebtables is needed by cloud-agent-4.0-1.el6.x86_64 jna is needed by cloud-agent-4.0-1.el6.x86_64 jsvc is needed by cloud-agent-4.0-1.el6.x86_64 kvm is needed by cloud-agent-4.0-1.el6.x86_64 libvirt is needed by cloud-agent-4.0-1.el6.x86_64 qemu-img is needed by cloud-agent-4.0-1.el6.x86_64 PING is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 syslinux is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 tftp-server is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 xinetd is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 jsvc is needed by cloud-usage-4.0-1.el6.x86_64 After this I installed all above mentioned packages by 'yum install package name expect jsvc and PING. Downloaded jsvc from net and installed but couldn't find PING. So, removed the baremetal package(just for trial) 4. rpm -Uvh *.rpm --- This time install was successful. 5. cloud-setup-databases --- Gave the following error Cloud DB required file /usr/share/java/cloud-jasypt-1.8.jar was not found We are not able to proceed with the installation due to the above mentioned issues. Please let us know the workaround/correct installation steps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Not able to install ASF 4.0 on Rhel 6.2
Hi, I tried installing ASF 4.0 on Rhel6.2 and faced following issues : 1. Copied the tar file asf4.0.rpm.tar on the rhel machine.--- It was successful 2. Untar the file. --- It was successful 3. rpm -Uvh *.rpm --- This gave following output error: Failed dependencies: /usr/sbin/libvirtd is needed by cloud-agent-4.0-1.el6.x86_64 ebtables is needed by cloud-agent-4.0-1.el6.x86_64 jna is needed by cloud-agent-4.0-1.el6.x86_64 jsvc is needed by cloud-agent-4.0-1.el6.x86_64 kvm is needed by cloud-agent-4.0-1.el6.x86_64 libvirt is needed by cloud-agent-4.0-1.el6.x86_64 qemu-img is needed by cloud-agent-4.0-1.el6.x86_64 PING is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 syslinux is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 tftp-server is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 xinetd is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 jsvc is needed by cloud-usage-4.0-1.el6.x86_64 After this I installed all above mentioned packages by 'yum install package name expect jsvc and PING. Downloaded jsvc from net and installed but couldn't find PING. So, removed the baremetal package(just for trial) 4. rpm -Uvh *.rpm --- This time install was successful. 5. cloud-setup-databases --- Gave the following error Cloud DB required file /usr/share/java/cloud-jasypt-1.8.jar was not found We are not able to proceed with the installation due to the above mentioned issues. Please let us know the workaround/correct installation steps. Note : I have already filed a defect for this : https://issues.apache.org/jira/browse/CLOUDSTACK-11 Thanks and regards, Abhinav
Revived - Re: [WEBSITE][DOCS] Publican-based docs publishing?
Hi all, Noticed that docs.cloudstack.org is down at the moment, which reminded me that we haven't come to a conclusion on this topic. The options before us are: - A Publican-generated site from the CloudStack documentation. - A docs.cloudstack.org site powered by MindTouch wiki. The previous discussion is easily skimmable here: http://markmail.org/thread/j57gbt5g4vtbk2iw My opinion is that we should go with the Publican-generated site. It's much less maintenance and can easily be hosted on Apache infrastructure. But, please do look over the earlier thread and if you have an interest in participating in CloudStack docs - please do speak up with a preference. Thanks, Joe On Thu, Aug 16, 2012, at 02:46 PM, David Nalley wrote: Hi folks, Wanted to toss this out there and get some reaction. We use Publican to transform our documentation XML into consumable formats like HTML, EPUB, PDF, etc. Publican has a number of other functions, and one of those is publishing a documentation website. I've participated in this with other projects, and it seems to be relatively easy. (it's literally two commands to build and publish a document) So I started playing with this today - and you can take a look at my VERY UNPOLISHED results. I only spent a few hours on this today, so there is still plenty that needs to happen for this to look presentable, but please have a look. http://people.apache.org/~ke4qqq/docs A couple of things I'll point out. The interface is completely localized in scores of languages - and it will automagically load to match your browsers locale provided there are docs in that language. To date though we only have zh_CN, and only for a single document. You can also manually set your language. The TOC on the left is divided by 'product' [1], then by version [2], and then document. I will note that you are presented with all of the formats that the document was built for (so you'll see HTML, HTML-Single, PDF and EPUB and the latter two options are download links for the docs.) And that permits you to load your content pretty easily. [1] I'd imagine we'd generally only have a single product - Apache CloudStack, but perhaps there will be others, like Apache CloudStack Contributor Documentation which is separate from user documentation [2] Selecting a version shows you all available documents for that version in your language of choice What do folks think of presenting our 'official documentation' in this manner? Is it something worth pursuing? I was thinking having this be a docs/ subdirectory on the project site (e.g. incubator.apache.org/cloudstack/docs, is there a better place for it? Thoughts, comments, or flames are welcome. --David -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
Re: RPM build is fixed, sort of...
I'm getting xapi-5.6.100-1-SNAPSHOT.jar from a fresh pull of the 4.0 repo, then following the install-non-oss.sh instructions On Wed, Sep 5, 2012 at 10:09 AM, Edison Su edison...@citrix.com wrote: What the name of the jar for xapi under deps folder on your environment? Sent from my iPhone On Sep 5, 2012, at 12:20 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Edison, I still get an error when building rpms with your changes: Processing files: cloud-utils-4.0.0-0.1.el6.maven.x86_64 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.kvoZ6x + umask 022 + cd /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILD + cd cloud-4.0.0 + DOCDIR=/home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + export DOCDIR + rm -rf /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + /bin/mkdir -p /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr README.html /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr debian/copyright /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + exit 0 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires: /usr/bin/env Obsoletes: vmops-utils 4.0.0-0.1.el6.maven Processing files: cloud-client-ui-4.0.0-0.1.el6.maven.x86_64 Requires(interp): /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires(pre): /bin/sh Obsoletes: vmops-client-ui 4.0.0-0.1.el6.maven Processing files: cloud-server-4.0.0-0.1.el6.maven.x86_64 Provides: config(cloud-server) = 4.0.0-0.1.el6.maven Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Obsoletes: vmops-server 4.0.0-0.1.el6.maven Processing files: cloud-agent-scripts-4.0.0-0.1.el6.maven.x86_64 Processing files: cloud-python-4.0.0-0.1.el6.maven.x86_64 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires: /bin/bash /usr/bin/python python(abi) = 2.6 Processing files: cloud-deps-4.0.0-0.1.el6.maven.x86_64 error: File not found: /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319-1.jar RPM build errors: File not found: /home/spark/git-workdir/incubator-cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0-0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319-1.jar Cheers, Hugo -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 8:24 AM To: 'Edison Su'; cloudstack-dev@incubator.apache.org Subject: RE: RPM build is fixed, sort of... Hey Edison, No problem, I'll leave it to you then. Cheers, Hugo -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 6:42 AM To: cloudstack-dev@incubator.apache.org Cc: Hugo Trippaers Subject: RPM build is fixed, sort of... Hi Hugo, I reverted three of your patches(1f207506daa1874421b01ad8ea733e6bc8b8ce60/ 79004fc7bc5f24f8bf9c75f7a0b0fef01042db13/ a4f1971e80f2aaf86017ddc989513eefb04265fa), I don't know how to get waf+maven work, but I know how to get ant work right now. Still need to use maven install to download all the deps. waf rpm works right now, but may still have other issues during the rpm install. Seems jasper related jars are not included in the classpath.conf, so you may not login into UI.
Re: conserve mode for network offering
On 9/4/12 11:27 PM, Mice Xia mice_...@tcloudcomputing.com wrote: Hi, all I noticed when 'conserve mode' is not checked for a network offering, the guest network created from this offering cannot do port forwarding and load balance if sourceNat is enabled. After checking network.js and wiki [1], I realized it was by design and much complicated than document said: 'Conserve mode. Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network.' Can someone explain why 'conserve mode' behave this way? Thanks. [1] http://wiki.cloudstack.org/display/QA/Network+Offering Regards Mice Mice, this description is wrong, the documentation has to be fixed. Adding Jessica to the thread. Conserve mode ON means that all public ip addresses associated with this network, can be used for multiple purposes at the same time (PF/LB). When the mode is off, the ip can serve only one purpose at a time. For static nat it's quite different though. Doesn't matter if conserve mode is on or off, when static nat is enabled, no PF/LB rule can be created for the IP. Only Firewall rules can be added using createFirewallRule command. -Alena.
RE: RPM build is fixed, sort of...
When I mvn install under deps folder, I got: [INFO] Copying xapi-5.6.100-1-SNAPSHOT.jar to /root/incubator-cloudstack/deps/xapi-5.6.100-1-20120825.123319-1.jar Anybody knows why this happened? -Original Message- From: Marcus Sorensen [mailto:shadow...@gmail.com] Sent: Wednesday, September 05, 2012 9:36 AM To: cloudstack-dev@incubator.apache.org Cc: Hugo Trippaers Subject: Re: RPM build is fixed, sort of... I'm getting xapi-5.6.100-1-SNAPSHOT.jar from a fresh pull of the 4.0 repo, then following the install-non-oss.sh instructions On Wed, Sep 5, 2012 at 10:09 AM, Edison Su edison...@citrix.com wrote: What the name of the jar for xapi under deps folder on your environment? Sent from my iPhone On Sep 5, 2012, at 12:20 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Edison, I still get an error when building rpms with your changes: Processing files: cloud-utils-4.0.0-0.1.el6.maven.x86_64 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.kvoZ6x + umask 022 + cd /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILD + cd cloud-4.0.0 + DOCDIR=/home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + export DOCDIR + rm -rf /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + /bin/mkdir -p /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr README.html /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr debian/copyright /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + exit 0 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires: /usr/bin/env Obsoletes: vmops-utils 4.0.0-0.1.el6.maven Processing files: cloud-client-ui-4.0.0-0.1.el6.maven.x86_64 Requires(interp): /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires(pre): /bin/sh Obsoletes: vmops-client-ui 4.0.0-0.1.el6.maven Processing files: cloud-server-4.0.0-0.1.el6.maven.x86_64 Provides: config(cloud-server) = 4.0.0-0.1.el6.maven Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Obsoletes: vmops-server 4.0.0-0.1.el6.maven Processing files: cloud-agent-scripts-4.0.0-0.1.el6.maven.x86_64 Processing files: cloud-python-4.0.0-0.1.el6.maven.x86_64 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires: /bin/bash /usr/bin/python python(abi) = 2.6 Processing files: cloud-deps-4.0.0-0.1.el6.maven.x86_64 error: File not found: /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319- 1.jar RPM build errors: File not found: /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319- 1.jar Cheers, Hugo -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 8:24 AM To: 'Edison Su'; cloudstack-dev@incubator.apache.org Subject: RE: RPM build is fixed, sort of... Hey Edison, No problem, I'll leave it to you then. Cheers, Hugo -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 6:42 AM To: cloudstack-dev@incubator.apache.org Cc: Hugo Trippaers Subject: RPM build is fixed, sort of... Hi Hugo, I reverted three of your patches(1f207506daa1874421b01ad8ea733e6bc8b8ce60/ 79004fc7bc5f24f8bf9c75f7a0b0fef01042db13/ a4f1971e80f2aaf86017ddc989513eefb04265fa), I don't know how to get waf+maven work, but I know how to get ant work right now. Still need to use maven install to download all the deps. waf rpm works right now, but may still have other issues during the rpm install. Seems jasper related jars are not included in the classpath.conf, so you may not login into UI.
Re: conserve mode for network offering
The 'conserve' mode dictates whether each service (LB/VPN/PF/etc) requires its own public ip address or whether many services can share the same public ip address. For network offerings where different services are offered by different devices, obviously the public ip addresses cannot be shared. For network offerings purely supported by the VR, the public IP can be shared, but then there are possibilities of rule conflicts (PF rule can conflict with LB rule or FW rule). Also, it rules out upgrade of network offering to an offering with per-service devices On 9/4/12 11:27 PM, Mice Xia mice_...@tcloudcomputing.com wrote: Hi, all I noticed when 'conserve mode' is not checked for a network offering, the guest network created from this offering cannot do port forwarding and load balance if sourceNat is enabled. After checking network.js and wiki [1], I realized it was by design and much complicated than document said: 'Conserve mode. Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network.' Can someone explain why 'conserve mode' behave this way? Thanks. [1] http://wiki.cloudstack.org/display/QA/Network+Offering Regards Mice
RE: Not able to install ASF 4.0 on Rhel 6.2
You can either: 1. rpm -Uvh cloud-client-4.0-1.el6.x86_64.rpm cloud-server-4.0-1.el6.x86_64.rpm cloud-client-ui-4.0-1.el6.x86_64.rpm cloud-python-4.0-1.el6.x86_64.rpm cloud-utils-4.0-1.el6.x86_64.rpm cloud-aws-api-4.0-1.el6.x86_64.rpm cloud-deps-4.0-1.el6.x86_64.rpm cloud-core-4.0-1.el6.x86_64.rpm cloud-setup-4.0-1.el6.x86_64.rpm cloud-agent-scripts-4.0-1.el6.x86_64.rpm 2. or create a rpm repo: createrepo ., then add the repo into your /etc/yum.repos.d/, then yum install cloud-client -Original Message- From: Abhinav Roy [mailto:abhinav@citrix.com] Sent: Wednesday, September 05, 2012 8:41 AM To: cloudstack-dev@incubator.apache.org Subject: Not able to install ASF 4.0 on Rhel 6.2 Hi, I tried installing ASF 4.0 on Rhel6.2 and faced following issues : 1. Copied the tar file asf4.0.rpm.tar on the rhel machine.--- It was successful 2. Untar the file. --- It was successful 3. rpm -Uvh *.rpm --- This gave following output error: Failed dependencies: /usr/sbin/libvirtd is needed by cloud-agent-4.0-1.el6.x86_64 ebtables is needed by cloud-agent-4.0-1.el6.x86_64 jna is needed by cloud-agent-4.0-1.el6.x86_64 jsvc is needed by cloud-agent-4.0-1.el6.x86_64 kvm is needed by cloud-agent-4.0-1.el6.x86_64 libvirt is needed by cloud-agent-4.0-1.el6.x86_64 qemu-img is needed by cloud-agent-4.0-1.el6.x86_64 PING is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 syslinux is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 tftp-server is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 xinetd is needed by cloud-baremetal-agent-4.0-1.el6.x86_64 jsvc is needed by cloud-usage-4.0-1.el6.x86_64 After this I installed all above mentioned packages by 'yum install package name expect jsvc and PING. Downloaded jsvc from net and installed but couldn't find PING. So, removed the baremetal package(just for trial) 4. rpm -Uvh *.rpm --- This time install was successful. 5. cloud-setup-databases --- Gave the following error Cloud DB required file /usr/share/java/cloud-jasypt-1.8.jar was not found We are not able to proceed with the installation due to the above mentioned issues. Please let us know the workaround/correct installation steps. Note : I have already filed a defect for this : https://issues.apache.org/jira/browse/CLOUDSTACK-11 Thanks and regards, Abhinav
RE: maven install failed
I did $ mvn $ deps/install-non-oss.sh $ mvn -P deps -pl deps I still see errors ant build-all Buildfile: build.xml [echo] Using build parameters from /home/anthony/vmops/master-cloudstack-oss/build/build-cloud.properties [echo] Using company info from /home/anthony/vmops/master-cloudstack-oss/build/cloud.properties [echo] Using override file from /home/anthony/vmops/master-cloudstack-oss/build/replace.properties [echo] Using build parameters from /home/anthony/vmops/master-cloudstack-oss/build/build-cloud.properties [echo] Using company info from /home/anthony/vmops/master-cloudstack-oss/build/cloud.properties [echo] Using override file from /home/anthony/vmops/master-cloudstack-oss/build/replace.properties BUILD FAILED /home/anthony/vmops/master-cloudstack-oss/build.xml:48: The following error occurred while executing this line: /home/anthony/vmops/master-cloudstack-oss/build/build-aws-api.xml:34: taskdef class org.apache.axis2.tool.ant.AntCodegenTask cannot be found Total time: 0 seconds -Original Message- From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] Sent: Tuesday, September 04, 2012 6:26 PM To: CloudStack DeveloperList Subject: Re: maven install failed Check this: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+Ma ven You can do mvn -P deps -pl deps On 9/4/12 5:51 PM, Anthony Xu xuefei...@citrix.com wrote: I'm using ubuntu 12.04 64 bit. Execution of maven install under directory deps failed. Does anyone meet this issue? Thanks Anthony Downloading: http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware- apputils/1.0/vmw are-apputils-1.0.jar [INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-sdx:jar:1.0' in repository central (http://repo1.maven.org/maven2) [INFO] Unable to find resource 'com.cloud.com.vmware:vmware-apputils:jar:1.0' in repository central (http://repo1.maven.org/maven2) [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) com.cloud.com.netapp:manageontap:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.cloud.com.netapp -DartifactId=manageontap -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.cloud.com.netapp -DartifactId=manageontap -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-netapp:jar:4.0.0- SNAPSHOT 3) com.cloud.com.netapp:manageontap:jar:1.0 2) com.cloud.com.f5:icontrol:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.cloud.com.f5 -DartifactId=icontrol -Dversion=1.0 -Dpackaging=jar - Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.cloud.com.f5 -DartifactId=icontrol -Dversion=1.0 -Dpackaging=jar - Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-network-srx:jar:4.0.0-SNAPSHOT 3) com.cloud.com.f5:icontrol:jar:1.0 3) org.libvirt:libvirt:jar:0.4.8 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.libvirt - DartifactId=libvirt -Dversion=0.4.8 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.libvirt - DartifactId=libvirt -Dversion=0.4.8 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-hypervisor-kvm:jar:4.0.0-SNAPSHOT 3) org.libvirt:libvirt:jar:0.4.8 4) com.cloud.com.vmware:vmware-vim:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim -Dversion=1.0 -Dpackaging=jar - Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim -Dversion=1.0
RE: maven install failed
Check out the lastest master code, cd deps, then mvn install will work. -Original Message- From: Anthony Xu [mailto:xuefei...@citrix.com] Sent: Wednesday, September 05, 2012 10:04 AM To: cloudstack-dev@incubator.apache.org Subject: RE: maven install failed I did $ mvn $ deps/install-non-oss.sh $ mvn -P deps -pl deps I still see errors ant build-all Buildfile: build.xml [echo] Using build parameters from /home/anthony/vmops/master- cloudstack-oss/build/build-cloud.properties [echo] Using company info from /home/anthony/vmops/master- cloudstack-oss/build/cloud.properties [echo] Using override file from /home/anthony/vmops/master- cloudstack-oss/build/replace.properties [echo] Using build parameters from /home/anthony/vmops/master- cloudstack-oss/build/build-cloud.properties [echo] Using company info from /home/anthony/vmops/master- cloudstack-oss/build/cloud.properties [echo] Using override file from /home/anthony/vmops/master- cloudstack-oss/build/replace.properties BUILD FAILED /home/anthony/vmops/master-cloudstack-oss/build.xml:48: The following error occurred while executing this line: /home/anthony/vmops/master-cloudstack-oss/build/build-aws-api.xml:34: taskdef class org.apache.axis2.tool.ant.AntCodegenTask cannot be found Total time: 0 seconds -Original Message- From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] Sent: Tuesday, September 04, 2012 6:26 PM To: CloudStack DeveloperList Subject: Re: maven install failed Check this: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+Ma ven You can do mvn -P deps -pl deps On 9/4/12 5:51 PM, Anthony Xu xuefei...@citrix.com wrote: I'm using ubuntu 12.04 64 bit. Execution of maven install under directory deps failed. Does anyone meet this issue? Thanks Anthony Downloading: http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware- apputils/1.0/vmw are-apputils-1.0.jar [INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-sdx:jar:1.0' in repository central (http://repo1.maven.org/maven2) [INFO] Unable to find resource 'com.cloud.com.vmware:vmware-apputils:jar:1.0' in repository central (http://repo1.maven.org/maven2) [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) com.cloud.com.netapp:manageontap:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.cloud.com.netapp -DartifactId=manageontap -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.cloud.com.netapp -DartifactId=manageontap -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-netapp:jar:4.0.0- SNAPSHOT 3) com.cloud.com.netapp:manageontap:jar:1.0 2) com.cloud.com.f5:icontrol:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.cloud.com.f5 -DartifactId=icontrol -Dversion=1.0 -Dpackaging=jar - Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.cloud.com.f5 -DartifactId=icontrol -Dversion=1.0 -Dpackaging=jar - Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-network-srx:jar:4.0.0-SNAPSHOT 3) com.cloud.com.f5:icontrol:jar:1.0 3) org.libvirt:libvirt:jar:0.4.8 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.libvirt - DartifactId=libvirt -Dversion=0.4.8 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.libvirt - DartifactId=libvirt -Dversion=0.4.8 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-hypervisor-kvm:jar:4.0.0-SNAPSHOT 3) org.libvirt:libvirt:jar:0.4.8 4) com.cloud.com.vmware:vmware-vim:jar:1.0 Try
mvn install doesn't work any more?
Work for me half an hour ago. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.744s [INFO] Finished at: Wed Sep 05 13:10:27 EDT 2012 [INFO] Final Memory: 8M/102M [INFO] [ERROR] Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler-sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware-vim:jar:1.0 in central (http://repo1.maven.org/maven2) - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler-sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware-vim:jar:1.0 in central (http://repo1.maven.org/maven2) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:196) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:108) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201) 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:319) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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.project.DependencyResolutionException: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler-sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware-vim:jar:1.0 in central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:170) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:171) ... 22 more Caused by: org.sonatype.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0,
Review Request: Add KVM to hypervisor types allowed in VPC
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6926/ --- Review request for cloudstack. Description --- When creating a new VM in advanced networking, we verify that the hypervisor type of the VM is OK for VPC networking if applicable. In light of the initial KVM support for VPC patch being merged in, this adds KVM to the list of hypervisors approved for use with VPC. Diffs - server/src/com/cloud/network/vpc/VpcManagerImpl.java d24009d server/src/com/cloud/vm/UserVmManagerImpl.java 1836176 Diff: https://reviews.apache.org/r/6926/diff/ Testing --- Thanks, Marcus Sorensen
RE: mvn install doesn't work any more?
Does anybody move/remove this files? Who is responsible for these files? -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 10:20 AM To: cloudstack-dev@incubator.apache.org Subject: mvn install doesn't work any more? Work for me half an hour ago. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.744s [INFO] Finished at: Wed Sep 05 13:10:27 EDT 2012 [INFO] Final Memory: 8M/102M [INFO] [ERROR] Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0- SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware- vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware- vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDepe ndencies(LifecycleDependencyResolver.java:196) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolve ProjectDependencies(LifecycleDependencyResolver.java:108) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreR esolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:201) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava: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.singleThreadedBuil d(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleS tarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 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.ja va:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launch er.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java: 230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Laun cher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:35 2) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.apache.cloudstack:cloud- deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware- vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(Def aultProjectDependenciesResolver.java:170) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDepe ndencies(LifecycleDependencyResolver.java:171)
Review Request: Fix default assignment of physical network names
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6928/ --- Review request for cloudstack, Sateesh Chodapuneedi and Kelven Yang. Description --- Assign default port profile names if nexus is configured and physical network is not specified. This addresses bug CS-16286. Diffs - plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java 205fb26 Diff: https://reviews.apache.org/r/6928/diff/ Testing --- Thanks, Venkata Siva Vijayendra Bhamidipati
Re: Incubator PMC/Board report for Sep 2012 ([ppmc])
On Mon, Sep 3, 2012 at 9:22 AM, Marvin no-re...@apache.org wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 September 2012, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Sep 5th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/September2012 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC David, I know you usually do this, but do you want to provide some pointers so that someone else (sure, I'll do it this month... ;-) ) knows what steps you take to get it done? I went looking in cms.a.o, but couldn't find the location. -chip
Re: RPM build fixed (maven-waf branch)
On Wed, Sep 5, 2012 at 6:40 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Rajesh, As far as I understand (and please correct me if I'm wrong) awsapi consists of three parts. The generated code for ec2, the generated code for s3 and our code. I would like to split this in three subprojects for maven. Two using the maven axis2 plugins to generate the classes and a third that uses the output from the first two (the .mar and .aar files) and makes the webapp by adding our code. Does that make sense? Hugo, I think we were trying to get the WSDL files out of the source tree. Prachi did some work on this initially, but two files still remain. I believe that without a clear license for the WSDL files, we might need to remove them from the tree. Given that, the generated classes can stay (and be licensed by ASF). If that's the case, then this really only needs to be one maven project. Does that make sense? The files in question are: incubator-cloudstack/awsapi/resource/AmazonEC2/AmazonEC2.wsdl incubator-cloudstack/awsapi/resource/AmazonEC2/services.xml Prachi - I'm not sure that you were able to come back around to my previous questions about this, but do you think we can remove them as well? Rajesh, perhaps you know the answer? -chip Cheers, Hugo -Original Message- From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] Sent: Wednesday, September 05, 2012 12:32 PM To: cloudstack-dev@incubator.apache.org Subject: RE: RPM build fixed (maven-waf branch) Hi Hugo, Regarding Awsapi how are you planning to go ahead ? Thanks Rajesh Battala -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 3:43 PM To: cloudstack-dev@incubator.apache.org Subject: RPM build fixed (maven-waf branch) Heya, I've made a new branch 'maven-waf' containing the stuff needed to build RPM's using the maven and waf. I've fixed the issues that prevented building from a clean tree directly, so it should be complete now. With the exeption of awsapi, see my earlier mail on that one. Cheers, Hugo
Re: Need some clarification on MYSQL connector (RE: Review Request: CS-15694:Remove MYSQL connector. Added the explicit class path for mysql connector which will call the jar from the desired location
On Wed, Sep 5, 2012 at 10:23 AM, Wido den Hollander w...@widodh.nl wrote:
On 09/05/2012 04:17 PM, Chip Childers wrote:
On Wed, Sep 5, 2012 at 10:08 AM, Pradeep Soundararajan
pradeep.soundarara...@citrix.com wrote:
Hello Hugo/Chip,
These are the review comments I have received so far.
- For build-cloud.properties, that line should be optional. This means
add a '#' in front of it and others an make it required when copying it into
override.
- The change for developer.xml to read in the build-cloud.xml should be
done as a precondition to all build targets.
- The change does not take into account that the file may be on the class
path and so the property value should only be optional. Here it made it
explicit.
- Also, we need to add the mysql connector as a rpm dependency. That
change is not in.
Hugo I did a quick fix to get the build working again, just pushed the
commit to master. The mysql connector rpm is already installed on the
Jenkins server, I just modified the scripts to it is picked up by the build.
I can add it to the spec file for rpm based distro's. I think it
should be added to the client rpm.
I see that you have added the class path explicitly in order to resolve
this temporarily.
# Add mysql jar from mysql-connector-java package to CP
# for Jenkins
CP=${CP}${PATHSEP}/usr/share/java/mysql-connector-java.jar
Also, I have seen that you have added that rpm in ‘cloud.spec’ as well.
Since you are calling mysql-connector explicitly from ‘deploy-db-dev.sh’
class-path, the changes from ‘build-cloud.properties’ and ‘developer.xml’
are not required from my patch. Please correct me if I am wrong.
If everything is fine, shall we close this topic. Please share if anyone
have any comments?
I *think* that's right. Let's see how the Maven build process shakes
out, since this is actually tied to that as well. We know that
mysql-connector needs to be a system dependency, and not be
distributed with the ASF release.
One item that does come to mind though... shouldn't it be included in
the DEB packages too? Can you add that?
Ubuntu and Debian both ship the MySQL connector in a package. I already
added a dependency for that:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=9064236879dc9f2f11538d891271545e1ff10e9c
Wido
Great! Then I think you're right Pradeep. We can probably close out
this topic for now.
Thanks,
Pradeep.S
-Original Message-
From: Alex Huang
[mailto:nore...@reviews.apache.org]mailto:[mailto:nore...@reviews.apache.org]
On Behalf Of Alex Huang
Sent: Friday, August 31, 2012 8:37 PM
To: David Nalley; Alex Huang
Cc: cloudstack; Pradeep Soundararajan
Subject: Re: Review Request: CS-15694:Remove MYSQL connector. Added the
explicit class path for mysql connector which will call the jar from the
desired location
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/#review10943
---
Also, we need to add the mysql connector as a rpm dependency. That
change is not in.
- Alex Huang
On Aug. 24, 2012, 10:19 a.m., Pradeep Soundararajan wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6752/
---
(Updated Aug. 24, 2012, 10:19 a.m.)
Review request for cloudstack, David Nalley and Alex Huang.
Description
---
CS-15694:Remove MYSQL connector. Added the explicit class path for mysql
connector which will call the jar from the desired location
Diffs
-
build/build-cloud.properties 552de7f74db7b715da70cc48ff4dc8945fa066f8
build/developer.xml f2e5aa6463ec849a3e97343e82423ff0ac62
setup/db/deploy-db-dev.sh f149e9efd029bd311b1d247e21764b9103fd01d9
Diff: https://reviews.apache.org/r/6752/diff/
Testing
---
Executed: ant build-all deploy-server deploydb successfully.
Thanks,
Pradeep Soundararajan
Re: mvn install doesn't work any more?
Edison, Are we sure that this ever worked? Searching the maven central repo doesn't show much with the name vmware: http://search.maven.org/#search%7Cga%7C1%7Cvmware Is it possible you had them cached locally? -chip On Wed, Sep 5, 2012 at 2:38 PM, Edison Su edison...@citrix.com wrote: Does anybody move/remove this files? Who is responsible for these files? -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 10:20 AM To: cloudstack-dev@incubator.apache.org Subject: mvn install doesn't work any more? Work for me half an hour ago. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.744s [INFO] Finished at: Wed Sep 05 13:10:27 EDT 2012 [INFO] Final Memory: 8M/102M [INFO] [ERROR] Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0- SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware- vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware- vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDepe ndencies(LifecycleDependencyResolver.java:196) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolve ProjectDependencies(LifecycleDependencyResolver.java:108) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreR esolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:201) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava: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.singleThreadedBuil d(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleS tarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 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.ja va:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launch er.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java: 230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Laun cher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:35 2) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.apache.cloudstack:cloud- deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware- vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central
RE: mvn install doesn't work any more?
It works for me yesterday(on my fresh build machine). -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Wednesday, September 05, 2012 1:01 PM To: cloudstack-dev@incubator.apache.org Subject: Re: mvn install doesn't work any more? Edison, Are we sure that this ever worked? Searching the maven central repo doesn't show much with the name vmware: http://search.maven.org/#search%7Cga%7C1%7Cvmware Is it possible you had them cached locally? -chip On Wed, Sep 5, 2012 at 2:38 PM, Edison Su edison...@citrix.com wrote: Does anybody move/remove this files? Who is responsible for these files? -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 10:20 AM To: cloudstack-dev@incubator.apache.org Subject: mvn install doesn't work any more? Work for me half an hour ago. [INFO] - --- [INFO] BUILD FAILURE [INFO] - --- [INFO] Total time: 5.744s [INFO] Finished at: Wed Sep 05 13:10:27 EDT 2012 [INFO] Final Memory: 8M/102M [INFO] - --- [ERROR] Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0- SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware- vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware- vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDepe ndencies(LifecycleDependencyResolver.java:196) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolve ProjectDependencies(LifecycleDependencyResolver.java:108) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreR esolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:201) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava: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.singleThreadedBuil d(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleS tarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 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.ja va:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launch er.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java: 230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Laun cher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:35 2) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.apache.cloudstack:cloud- deps:jar:4.0.0-SNAPSHOT: The
Re: mvn install doesn't work any more?
Heya, These files need to be in the deps directory, you need to download them yourself and put them there. Then run the install non oss script. That will add them to the local maven cache. We need to figure out how to get those files, if possible at all, so we can add a description on the wiki. For example the manageontap file you can only get from the NetApp support site. For VMware, we need to add VMware-base to the VMware plugin I think as it can't be part of the OSS build due to these library dependencies. If that is done everything should build without these extra libraries. Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 22:01, Chip Childers chip.child...@sungard.com wrote: Edison, Are we sure that this ever worked? Searching the maven central repo doesn't show much with the name vmware: http://search.maven.org/#search%7Cga%7C1%7Cvmware Is it possible you had them cached locally? -chip On Wed, Sep 5, 2012 at 2:38 PM, Edison Su edison...@citrix.com wrote: Does anybody move/remove this files? Who is responsible for these files? -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 10:20 AM To: cloudstack-dev@incubator.apache.org Subject: mvn install doesn't work any more? Work for me half an hour ago. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.744s [INFO] Finished at: Wed Sep 05 13:10:27 EDT 2012 [INFO] Final Memory: 8M/102M [INFO] [ERROR] Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0- SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, com.cloud.com.vmware:vmware- vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project cloud-deps: Could not resolve dependencies for project org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: com.cloud.com.vmware:vmware- vim:jar:1.0, com.cloud.com.vmware:vmware-vim25:jar:1.0, com.cloud.com.vmware:vmware-apputils:jar:1.0, com.cloud.com.f5:icontrol:jar:1.0, com.cloud.com.netapp:manageontap:jar:1.0, com.cloud.com.citrix:netscaler:jar:1.0, com.cloud.com.citrix:netscaler- sdx:jar:1.0: Could not find artifact com.cloud.com.vmware:vmware- vim:jar:1.0 in central (http://repo1.maven.org/maven2) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDepe ndencies(LifecycleDependencyResolver.java:196) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolve ProjectDependencies(LifecycleDependencyResolver.java:108) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreR esolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:201) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.j ava: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.singleThreadedBuil d(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleS tarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 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.ja va:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launch er.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java: 230) at
Re: RPM build is fixed, sort of...
That's maven. A snapshot dependency will get a build version number depending on the time it was built. Only release versions have a fixed version number. Maven it self will automagically take this into account when building classpaths, but for external tools it is a bit trickier. Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 19:00, Edison Su edison...@citrix.com wrote: When I mvn install under deps folder, I got: [INFO] Copying xapi-5.6.100-1-SNAPSHOT.jar to /root/incubator-cloudstack/deps/xapi-5.6.100-1-20120825.123319-1.jar Anybody knows why this happened? -Original Message- From: Marcus Sorensen [mailto:shadow...@gmail.com] Sent: Wednesday, September 05, 2012 9:36 AM To: cloudstack-dev@incubator.apache.org Cc: Hugo Trippaers Subject: Re: RPM build is fixed, sort of... I'm getting xapi-5.6.100-1-SNAPSHOT.jar from a fresh pull of the 4.0 repo, then following the install-non-oss.sh instructions On Wed, Sep 5, 2012 at 10:09 AM, Edison Su edison...@citrix.com wrote: What the name of the jar for xapi under deps folder on your environment? Sent from my iPhone On Sep 5, 2012, at 12:20 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Edison, I still get an error when building rpms with your changes: Processing files: cloud-utils-4.0.0-0.1.el6.maven.x86_64 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.kvoZ6x + umask 022 + cd /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILD + cd cloud-4.0.0 + DOCDIR=/home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + export DOCDIR + rm -rf /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + /bin/mkdir -p /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr README.html /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + cp -pr debian/copyright /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/doc/cloud-utils-4.0.0 + exit 0 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires: /usr/bin/env Obsoletes: vmops-utils 4.0.0-0.1.el6.maven Processing files: cloud-client-ui-4.0.0-0.1.el6.maven.x86_64 Requires(interp): /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Requires(pre): /bin/sh Obsoletes: vmops-client-ui 4.0.0-0.1.el6.maven Processing files: cloud-server-4.0.0-0.1.el6.maven.x86_64 Provides: config(cloud-server) = 4.0.0-0.1.el6.maven Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(VersionedDependencies) = 3.0.3-1 Obsoletes: vmops-server 4.0.0-0.1.el6.maven Processing files: cloud-agent-scripts-4.0.0-0.1.el6.maven.x86_64 Processing files: cloud-python-4.0.0-0.1.el6.maven.x86_64 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires: /bin/bash /usr/bin/python python(abi) = 2.6 Processing files: cloud-deps-4.0.0-0.1.el6.maven.x86_64 error: File not found: /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319- 1.jar RPM build errors: File not found: /home/spark/git-workdir/incubator- cloudstack/artifacts/rpmbuild/BUILDROOT/cloud-4.0.0- 0.1.el6.maven.x86_64/usr/share/java/xapi-5.6.100-1-20120825.123319- 1.jar Cheers, Hugo -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 8:24 AM To: 'Edison Su'; cloudstack-dev@incubator.apache.org Subject: RE: RPM build is fixed, sort of... Hey Edison, No problem, I'll leave it to you then. Cheers, Hugo -Original Message- From: Edison Su [mailto:edison...@citrix.com] Sent: Wednesday, September 05, 2012 6:42 AM To: cloudstack-dev@incubator.apache.org Cc: Hugo Trippaers Subject: RPM build is fixed, sort of... Hi Hugo, I reverted three of your patches(1f207506daa1874421b01ad8ea733e6bc8b8ce60/ 79004fc7bc5f24f8bf9c75f7a0b0fef01042db13/ a4f1971e80f2aaf86017ddc989513eefb04265fa), I don't know how to get waf+maven work, but I know how to get ant work right now. Still need to use maven install to download all the deps. waf rpm works right now, but may still have other issues during the rpm install. Seems jasper related jars are not included in the classpath.conf, so you may not login into UI.
RE: RPM build fixed (maven-waf branch)
The aar files contain the wsdl file and the services.xml file because the build script includes them specifically while building the aar. I don't know if these are a must have files in aar. I will remove and check if things work. -Prachi -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Wednesday, September 05, 2012 1:57 PM To: Hugo Trippaers Cc: cloudstack-dev@incubator.apache.org; Prachi Damle Subject: Re: RPM build fixed (maven-waf branch) On Wed, Sep 5, 2012 at 4:44 PM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Chip, That makes more sense and less work :-). I think i have the maven part done now. The only thing i'm curious about is the mar and aar files. They seem to contain the wsdl files as well. I now nothing about axis2 so no idea what is needed to get awaapi to work right. Might need some help from the folks that have worked on it in the past ;) IIRC, aar files are the result of an axis build. I don't see any of them in the source tree though... do you? The only mar files I see are the modules/rahas-1.5.mar and modules/rampart-1.5.mar, which I think are basically dependency files. I did a quick search on maven central, and I think the ones we need are there: http://search.maven.org/#search%7Cga%7C1%7Crahas http://search.maven.org/#search%7Cga%7C1%7Crampart Can we make them pull from the mvn central and get them out of the source tree? Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 21:43, Chip Childers chip.child...@sungard.com wrote: On Wed, Sep 5, 2012 at 6:40 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Rajesh, As far as I understand (and please correct me if I'm wrong) awsapi consists of three parts. The generated code for ec2, the generated code for s3 and our code. I would like to split this in three subprojects for maven. Two using the maven axis2 plugins to generate the classes and a third that uses the output from the first two (the .mar and .aar files) and makes the webapp by adding our code. Does that make sense? Hugo, I think we were trying to get the WSDL files out of the source tree. Prachi did some work on this initially, but two files still remain. I believe that without a clear license for the WSDL files, we might need to remove them from the tree. Given that, the generated classes can stay (and be licensed by ASF). If that's the case, then this really only needs to be one maven project. Does that make sense? The files in question are: incubator-cloudstack/awsapi/resource/AmazonEC2/AmazonEC2.wsdl incubator-cloudstack/awsapi/resource/AmazonEC2/services.xml Prachi - I'm not sure that you were able to come back around to my previous questions about this, but do you think we can remove them as well? Rajesh, perhaps you know the answer? -chip Cheers, Hugo -Original Message- From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] Sent: Wednesday, September 05, 2012 12:32 PM To: cloudstack-dev@incubator.apache.org Subject: RE: RPM build fixed (maven-waf branch) Hi Hugo, Regarding Awsapi how are you planning to go ahead ? Thanks Rajesh Battala -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 3:43 PM To: cloudstack-dev@incubator.apache.org Subject: RPM build fixed (maven-waf branch) Heya, I've made a new branch 'maven-waf' containing the stuff needed to build RPM's using the maven and waf. I've fixed the issues that prevented building from a clean tree directly, so it should be complete now. With the exeption of awsapi, see my earlier mail on that one. Cheers, Hugo
Re: Review Request: Reset password on guest VM
This fix is wrong, since the real reason for this regression is not we should respect only one true return, but we called both VpcVirtualRouterElement and VirtualRouterElement to handle this savePassword command, but VpcVirtualRouterElement didn't support this network, then return false. Alena fixed it as stated in http://bugs.cloudstack.org/browse/CS-16222. Btw, there would need more work on the similar scenario. Iterate all the network elements for every commands is not a acceptable way - we suppose to only call the network element which providing the service for the network at most time, if not always. --Sheng On Fri, Aug 31, 2012 at 5:48 AM, Jayapal Reddy jayapalreddy.ur...@citrix.com wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6871/ --- Review request for cloudstack and Abhinandan Prateek. Description --- While resetting the password on the user VM, it got failed due VPC VR returned false. This addresses bug CS-16222. Diffs - server/src/com/cloud/vm/UserVmManagerImpl.java 667b048 Diff: https://reviews.apache.org/r/6871/diff/ Testing --- 1. Tested on basic, advanced zone. 2. Tested on adv zone vpc VM Thanks, Jayapal Reddy
Re: RPM build fixed (maven-waf branch)
Prachi, Do you remember / know specifically where the services file came from? - chip Sent from my iPhone. On Sep 5, 2012, at 5:49 PM, Prachi Damle prachi.da...@citrix.com wrote: Hugo / Chip, I tested and found that we need to include the services.xml file in aar file generated by build - without that axis2 cannot deploy the aar files when you start cloudstack. We can remove the AmazonEC2.wsdl file safely. Are there any issues with having services.xml file in source tree? [java] org.apache.axis2.deployment.DeploymentException: The services.xml fie cannot be found for the service: C:\tomcat\apache-tomcat-6.0.29\webapps7080\asapi\WEB-INF\services\cloud-ec2.aar [java] at org.apache.axis2.deployment.repository.util.ArchiveReader.proessServiceGroup(ArchiveReader.java:150) Hugo, the test procedure I use is: - remove files and build - deploy CloudStack - create user and generate keys - enable ec2 in CloudStack For client: - register the user's certificate and set up EC2 tools environment - use ec2 tools to test commands against CloudStack ec2 api. Thanks, -Prachi -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 2:08 PM To: Prachi Damle Cc: Chip Childers; cloudstack-dev@incubator.apache.org Subject: Re: RPM build fixed (maven-waf branch) Prachi, Would it be possible to describe the test procedure? Maybe we can add it to Jenkins as well. Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 23:04, Prachi Damle prachi.da...@citrix.com wrote: The aar files contain the wsdl file and the services.xml file because the build script includes them specifically while building the aar. I don't know if these are a must have files in aar. I will remove and check if things work. -Prachi -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Wednesday, September 05, 2012 1:57 PM To: Hugo Trippaers Cc: cloudstack-dev@incubator.apache.org; Prachi Damle Subject: Re: RPM build fixed (maven-waf branch) On Wed, Sep 5, 2012 at 4:44 PM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Chip, That makes more sense and less work :-). I think i have the maven part done now. The only thing i'm curious about is the mar and aar files. They seem to contain the wsdl files as well. I now nothing about axis2 so no idea what is needed to get awaapi to work right. Might need some help from the folks that have worked on it in the past ;) IIRC, aar files are the result of an axis build. I don't see any of them in the source tree though... do you? The only mar files I see are the modules/rahas-1.5.mar and modules/rampart-1.5.mar, which I think are basically dependency files. I did a quick search on maven central, and I think the ones we need are there: http://search.maven.org/#search%7Cga%7C1%7Crahas http://search.maven.org/#search%7Cga%7C1%7Crampart Can we make them pull from the mvn central and get them out of the source tree? Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 21:43, Chip Childers chip.child...@sungard.com wrote: On Wed, Sep 5, 2012 at 6:40 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Rajesh, As far as I understand (and please correct me if I'm wrong) awsapi consists of three parts. The generated code for ec2, the generated code for s3 and our code. I would like to split this in three subprojects for maven. Two using the maven axis2 plugins to generate the classes and a third that uses the output from the first two (the .mar and .aar files) and makes the webapp by adding our code. Does that make sense? Hugo, I think we were trying to get the WSDL files out of the source tree. Prachi did some work on this initially, but two files still remain. I believe that without a clear license for the WSDL files, we might need to remove them from the tree. Given that, the generated classes can stay (and be licensed by ASF). If that's the case, then this really only needs to be one maven project. Does that make sense? The files in question are: incubator-cloudstack/awsapi/resource/AmazonEC2/AmazonEC2.wsdl incubator-cloudstack/awsapi/resource/AmazonEC2/services.xml Prachi - I'm not sure that you were able to come back around to my previous questions about this, but do you think we can remove them as well? Rajesh, perhaps you know the answer? -chip Cheers, Hugo -Original Message- From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] Sent: Wednesday, September 05, 2012 12:32 PM To: cloudstack-dev@incubator.apache.org Subject: RE: RPM build fixed (maven-waf branch) Hi Hugo, Regarding Awsapi how are you planning to go ahead ? Thanks Rajesh Battala -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 3:43 PM To: cloudstack-dev@incubator.apache.org Subject:
[jira] [Created] (CLOUDSTACK-12) Audit Review Board
Ewan Mellor created CLOUDSTACK-12: - Summary: Audit Review Board Key: CLOUDSTACK-12 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-12 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Fix For: 4.0.0 Audit Review Board and check that all patches have been applied to master and 4.0, or reasonably deferred to the next release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-13) Make it possible to run Marvin
Ewan Mellor created CLOUDSTACK-13: - Summary: Make it possible to run Marvin Key: CLOUDSTACK-13 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-13 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Fix For: 4.0.0 Make it possible to run Marvin (our automated function test suite) on 4.0 and master. Ahmad Emneina has details of machines inside a Citrix lab that can be used for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-13) Make it possible to run Marvin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewan Mellor updated CLOUDSTACK-13: -- Description: Make it possible to run Marvin (our automated function test suite) on 4.0 and master. Ahmad Emneina has details of machines inside a Citrix lab that can be used for this. We need to punch a hole in the Citrix firewall, or set up an SSH tunnel, so that a Jenkins slave on the Citrix site can talk to jenkins.cloudstack.org. was: Make it possible to run Marvin (our automated function test suite) on 4.0 and master. Ahmad Emneina has details of machines inside a Citrix lab that can be used for this. Make it possible to run Marvin -- Key: CLOUDSTACK-13 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-13 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Fix For: 4.0.0 Make it possible to run Marvin (our automated function test suite) on 4.0 and master. Ahmad Emneina has details of machines inside a Citrix lab that can be used for this. We need to punch a hole in the Citrix firewall, or set up an SSH tunnel, so that a Jenkins slave on the Citrix site can talk to jenkins.cloudstack.org. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-15) NOTICE file final audit
Ewan Mellor created CLOUDSTACK-15: - Summary: NOTICE file final audit Key: CLOUDSTACK-15 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-15 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Priority: Blocker Perform a final audit of the CloudStack NOTICE file. See http://apache.org/legal/src-headers.html#notice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-16) Final release version number changes
Ewan Mellor created CLOUDSTACK-16: - Summary: Final release version number changes Key: CLOUDSTACK-16 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-16 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Priority: Blocker Update all the version numbers before final RC is created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-17) Merge final documentation into 4.0 branch
Ewan Mellor created CLOUDSTACK-17: - Summary: Merge final documentation into 4.0 branch Key: CLOUDSTACK-17 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-17 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Fix For: 4.0.0 Merge the latest documentation into the 4.0 branch before we make the final RC, so that we have a frozen, up-to-date copy in the release branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: RPM build fixed (maven-waf branch)
Nope. But the file seems to have been generated using the AWS wsdl... I guess if we can use the generated code, we could use this as well? -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Wednesday, September 05, 2012 3:09 PM To: Prachi Damle Cc: Hugo Trippaers; cloudstack-dev@incubator.apache.org Subject: Re: RPM build fixed (maven-waf branch) Prachi, Do you remember / know specifically where the services file came from? - chip Sent from my iPhone. On Sep 5, 2012, at 5:49 PM, Prachi Damle prachi.da...@citrix.com wrote: Hugo / Chip, I tested and found that we need to include the services.xml file in aar file generated by build - without that axis2 cannot deploy the aar files when you start cloudstack. We can remove the AmazonEC2.wsdl file safely. Are there any issues with having services.xml file in source tree? [java] org.apache.axis2.deployment.DeploymentException: The services.xml fie cannot be found for the service: C:\tomcat\apache-tomcat-6.0.29\webapps7080\asapi\WEB-INF\services\cloud-ec2.aar [java] at org.apache.axis2.deployment.repository.util.ArchiveReader.proessServiceGroup(ArchiveReader.java:150) Hugo, the test procedure I use is: - remove files and build - deploy CloudStack - create user and generate keys - enable ec2 in CloudStack For client: - register the user's certificate and set up EC2 tools environment - use ec2 tools to test commands against CloudStack ec2 api. Thanks, -Prachi -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 2:08 PM To: Prachi Damle Cc: Chip Childers; cloudstack-dev@incubator.apache.org Subject: Re: RPM build fixed (maven-waf branch) Prachi, Would it be possible to describe the test procedure? Maybe we can add it to Jenkins as well. Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 23:04, Prachi Damle prachi.da...@citrix.com wrote: The aar files contain the wsdl file and the services.xml file because the build script includes them specifically while building the aar. I don't know if these are a must have files in aar. I will remove and check if things work. -Prachi -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Wednesday, September 05, 2012 1:57 PM To: Hugo Trippaers Cc: cloudstack-dev@incubator.apache.org; Prachi Damle Subject: Re: RPM build fixed (maven-waf branch) On Wed, Sep 5, 2012 at 4:44 PM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Chip, That makes more sense and less work :-). I think i have the maven part done now. The only thing i'm curious about is the mar and aar files. They seem to contain the wsdl files as well. I now nothing about axis2 so no idea what is needed to get awaapi to work right. Might need some help from the folks that have worked on it in the past ;) IIRC, aar files are the result of an axis build. I don't see any of them in the source tree though... do you? The only mar files I see are the modules/rahas-1.5.mar and modules/rampart-1.5.mar, which I think are basically dependency files. I did a quick search on maven central, and I think the ones we need are there: http://search.maven.org/#search%7Cga%7C1%7Crahas http://search.maven.org/#search%7Cga%7C1%7Crampart Can we make them pull from the mvn central and get them out of the source tree? Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 21:43, Chip Childers chip.child...@sungard.com wrote: On Wed, Sep 5, 2012 at 6:40 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Rajesh, As far as I understand (and please correct me if I'm wrong) awsapi consists of three parts. The generated code for ec2, the generated code for s3 and our code. I would like to split this in three subprojects for maven. Two using the maven axis2 plugins to generate the classes and a third that uses the output from the first two (the .mar and .aar files) and makes the webapp by adding our code. Does that make sense? Hugo, I think we were trying to get the WSDL files out of the source tree. Prachi did some work on this initially, but two files still remain. I believe that without a clear license for the WSDL files, we might need to remove them from the tree. Given that, the generated classes can stay (and be licensed by ASF). If that's the case, then this really only needs to be one maven project. Does that make sense? The files in question are: incubator-cloudstack/awsapi/resource/AmazonEC2/AmazonEC2.wsdl incubator-cloudstack/awsapi/resource/AmazonEC2/services.xml Prachi - I'm not sure that you were able to come back around to my previous questions about this, but do you think we can remove them as well? Rajesh, perhaps you know the answer? -chip Cheers, Hugo -Original Message- From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] Sent:
[jira] [Updated] (CLOUDSTACK-15) NOTICE file final audit
[ https://issues.apache.org/jira/browse/CLOUDSTACK-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewan Mellor updated CLOUDSTACK-15: -- Fix Version/s: 4.0.0 NOTICE file final audit --- Key: CLOUDSTACK-15 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-15 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Priority: Blocker Fix For: 4.0.0 Perform a final audit of the CloudStack NOTICE file. See http://apache.org/legal/src-headers.html#notice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-16) Final release version number changes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewan Mellor updated CLOUDSTACK-16: -- Fix Version/s: 4.0.0 Final release version number changes Key: CLOUDSTACK-16 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-16 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Priority: Blocker Fix For: 4.0.0 Update all the version numbers before final RC is created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-19) Request mirroring for our release and pre-release artifacts
Ewan Mellor created CLOUDSTACK-19: - Summary: Request mirroring for our release and pre-release artifacts Key: CLOUDSTACK-19 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-19 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor We need to request mirroring for our release and pre-release artifacts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-21) Create a secondary binary build containing KVM support
Ewan Mellor created CLOUDSTACK-21: - Summary: Create a secondary binary build containing KVM support Key: CLOUDSTACK-21 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-21 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Priority: Blocker We have permission to ship a secondary convenience build containing KVM support, even though that library is LGPL-licensed. This will sit alongside the default binaries, which will have KVM support turned off. We need to build this as part of the CI infrastructure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
4.0 release items
Hi all, The following link will take you to the Jira filter for all outstanding 4.0 release items. https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+CLOUDSTACK+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+12323251+ORDER+BY+priority+DESC This replaces the Release Checklist wiki page, which I've marked as obsolete. Cheers, Ewan.
[jira] [Created] (CLOUDSTACK-22) Sign the release artifacts
Ewan Mellor created CLOUDSTACK-22: - Summary: Sign the release artifacts Key: CLOUDSTACK-22 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-22 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Priority: Blocker The release artifacts need to be signed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-22) Sign the release artifacts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewan Mellor updated CLOUDSTACK-22: -- Fix Version/s: 4.0.0 Sign the release artifacts -- Key: CLOUDSTACK-22 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-22 Project: CloudStack Issue Type: Task Reporter: Ewan Mellor Priority: Blocker Fix For: 4.0.0 The release artifacts need to be signed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-23) Execute CloudStack 4.0 QA plan
Ewan Mellor created CLOUDSTACK-23: - Summary: Execute CloudStack 4.0 QA plan Key: CLOUDSTACK-23 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-23 Project: CloudStack Issue Type: Test Reporter: Ewan Mellor Priority: Critical Execute the CloudStack 4.0 QA plan. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/ASF+CS+4.0+QA for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-23) Execute CloudStack 4.0 QA plan
[ https://issues.apache.org/jira/browse/CLOUDSTACK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewan Mellor updated CLOUDSTACK-23: -- Fix Version/s: 4.0.0 Execute CloudStack 4.0 QA plan -- Key: CLOUDSTACK-23 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-23 Project: CloudStack Issue Type: Test Reporter: Ewan Mellor Priority: Critical Fix For: 4.0.0 Execute the CloudStack 4.0 QA plan. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/ASF+CS+4.0+QA for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: 4.0 release items
Correction: this link is better: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+CLOUDSTACK+AND+resolution+%3D+Unresolved+AND+fixVersion+in+%28EMPTY%2C+12323251%2C+12323252%29+ORDER+BY+priority+DESC Ewan. -Original Message- From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com] Sent: Wednesday, September 05, 2012 3:51 PM To: cloudstack-dev@incubator.apache.org Subject: 4.0 release items Hi all, The following link will take you to the Jira filter for all outstanding 4.0 release items. https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+CLOUDSTACK+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+12323251+ORDER+BY+priority+DESC This replaces the Release Checklist wiki page, which I've marked as obsolete. Cheers, Ewan.
Re: RPM build fixed (maven-waf branch)
IMO, if it's generated we can. I would suggest adding the ASF header to it, just like we did for the generated java files. - chip Sent from my iPhone. On Sep 5, 2012, at 6:33 PM, Prachi Damle prachi.da...@citrix.com wrote: Nope. But the file seems to have been generated using the AWS wsdl... I guess if we can use the generated code, we could use this as well? -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Wednesday, September 05, 2012 3:09 PM To: Prachi Damle Cc: Hugo Trippaers; cloudstack-dev@incubator.apache.org Subject: Re: RPM build fixed (maven-waf branch) Prachi, Do you remember / know specifically where the services file came from? - chip Sent from my iPhone. On Sep 5, 2012, at 5:49 PM, Prachi Damle prachi.da...@citrix.com wrote: Hugo / Chip, I tested and found that we need to include the services.xml file in aar file generated by build - without that axis2 cannot deploy the aar files when you start cloudstack. We can remove the AmazonEC2.wsdl file safely. Are there any issues with having services.xml file in source tree? [java] org.apache.axis2.deployment.DeploymentException: The services.xml fie cannot be found for the service: C:\tomcat\apache-tomcat-6.0.29\webapps7080\asapi\WEB-INF\services\cloud-ec2.aar [java] at org.apache.axis2.deployment.repository.util.ArchiveReader.proessServiceGroup(ArchiveReader.java:150) Hugo, the test procedure I use is: - remove files and build - deploy CloudStack - create user and generate keys - enable ec2 in CloudStack For client: - register the user's certificate and set up EC2 tools environment - use ec2 tools to test commands against CloudStack ec2 api. Thanks, -Prachi -Original Message- From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] Sent: Wednesday, September 05, 2012 2:08 PM To: Prachi Damle Cc: Chip Childers; cloudstack-dev@incubator.apache.org Subject: Re: RPM build fixed (maven-waf branch) Prachi, Would it be possible to describe the test procedure? Maybe we can add it to Jenkins as well. Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 23:04, Prachi Damle prachi.da...@citrix.com wrote: The aar files contain the wsdl file and the services.xml file because the build script includes them specifically while building the aar. I don't know if these are a must have files in aar. I will remove and check if things work. -Prachi -Original Message- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Wednesday, September 05, 2012 1:57 PM To: Hugo Trippaers Cc: cloudstack-dev@incubator.apache.org; Prachi Damle Subject: Re: RPM build fixed (maven-waf branch) On Wed, Sep 5, 2012 at 4:44 PM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Chip, That makes more sense and less work :-). I think i have the maven part done now. The only thing i'm curious about is the mar and aar files. They seem to contain the wsdl files as well. I now nothing about axis2 so no idea what is needed to get awaapi to work right. Might need some help from the folks that have worked on it in the past ;) IIRC, aar files are the result of an axis build. I don't see any of them in the source tree though... do you? The only mar files I see are the modules/rahas-1.5.mar and modules/rampart-1.5.mar, which I think are basically dependency files. I did a quick search on maven central, and I think the ones we need are there: http://search.maven.org/#search%7Cga%7C1%7Crahas http://search.maven.org/#search%7Cga%7C1%7Crampart Can we make them pull from the mvn central and get them out of the source tree? Cheers, Hugo Sent from my iPhone On 5 sep. 2012, at 21:43, Chip Childers chip.child...@sungard.com wrote: On Wed, Sep 5, 2012 at 6:40 AM, Hugo Trippaers htrippa...@schubergphilis.com wrote: Hey Rajesh, As far as I understand (and please correct me if I'm wrong) awsapi consists of three parts. The generated code for ec2, the generated code for s3 and our code. I would like to split this in three subprojects for maven. Two using the maven axis2 plugins to generate the classes and a third that uses the output from the first two (the .mar and .aar files) and makes the webapp by adding our code. Does that make sense? Hugo, I think we were trying to get the WSDL files out of the source tree. Prachi did some work on this initially, but two files still remain. I believe that without a clear license for the WSDL files, we might need to remove them from the tree. Given that, the generated classes can stay (and be licensed by ASF). If that's the case, then this really only needs to be one maven project. Does that make sense? The files in question are: incubator-cloudstack/awsapi/resource/AmazonEC2/AmazonEC2.wsdl incubator-cloudstack/awsapi/resource/AmazonEC2/services.xml Prachi - I'm not sure that you were able to come back around to my previous
First full ASF build is on 4.0 branch
Remove all the un-asf-friendly dependency(vmware/kvm/juniper/netapp/nexus/F5/netscalar etc), waf rpm will call mvn install -P deps to install all the dependency jars, then call ant build-all build cloudstack, then package. We can't wait for another few days to get build done, the whole QA team are waiting a RPM to test. If you have other better ways to get it done, please get it done ASAP.
Re: Review Request: Add initial support for Caringo's CAStor object storage as the S3 backend.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6473/ --- (Updated Sept. 6, 2012, 12:07 a.m.) Review request for cloudstack. Changes --- Clean patch against current master (due to removal of Hibernate) and with awsapi/pom.xml update (CAStorSDK.jar now in maven central). Description --- Below is the commit message. This is my first patch, let me know if I did anything wrong or if e.g. using storage.root is not how configuring a new storage backend should be done. Add initial support for Caringo's CAStor object storage as the S3 backend. Similar to the s3-hdfs example. Now storage.root can specify castor followed by a list of IP addresses for the nodes in the CAStor cluster. S3 operations will then create and read buckets and objects in CAStor instead of a file system. Diffs (updated) - NOTICE 9c124ab awsapi/pom.xml 2909376 awsapi/src/com/cloud/bridge/io/S3CAStorBucketAdapter.java PRE-CREATION awsapi/src/com/cloud/bridge/model/SHost.java 4ed5b7e awsapi/src/com/cloud/bridge/service/controller/s3/ServiceProvider.java 2f1791e awsapi/src/com/cloud/bridge/service/core/s3/S3Engine.java a117d13 Diff: https://reviews.apache.org/r/6473/diff/ Testing --- Tested a boto script I believe we got from Chiradeep (localhost_test.py) that creates buckets and streams, does a range read and delete. I will continue to do more testing (http://wiki.cloudstack.org/display/QA/How+to+run+S3+Tests+against+CloudStack+S3+Implementation). Thanks, Jamshid Afshar
RE: maven install failed
It's fixed on master branch now. But remember only xenserver works. -Original Message- From: Anthony Xu [mailto:xuefei...@citrix.com] Sent: Wednesday, September 05, 2012 10:04 AM To: cloudstack-dev@incubator.apache.org Subject: RE: maven install failed I did $ mvn $ deps/install-non-oss.sh $ mvn -P deps -pl deps I still see errors ant build-all Buildfile: build.xml [echo] Using build parameters from /home/anthony/vmops/master- cloudstack-oss/build/build-cloud.properties [echo] Using company info from /home/anthony/vmops/master- cloudstack-oss/build/cloud.properties [echo] Using override file from /home/anthony/vmops/master- cloudstack-oss/build/replace.properties [echo] Using build parameters from /home/anthony/vmops/master- cloudstack-oss/build/build-cloud.properties [echo] Using company info from /home/anthony/vmops/master- cloudstack-oss/build/cloud.properties [echo] Using override file from /home/anthony/vmops/master- cloudstack-oss/build/replace.properties BUILD FAILED /home/anthony/vmops/master-cloudstack-oss/build.xml:48: The following error occurred while executing this line: /home/anthony/vmops/master-cloudstack-oss/build/build-aws-api.xml:34: taskdef class org.apache.axis2.tool.ant.AntCodegenTask cannot be found Total time: 0 seconds -Original Message- From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] Sent: Tuesday, September 04, 2012 6:26 PM To: CloudStack DeveloperList Subject: Re: maven install failed Check this: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+Ma ven You can do mvn -P deps -pl deps On 9/4/12 5:51 PM, Anthony Xu xuefei...@citrix.com wrote: I'm using ubuntu 12.04 64 bit. Execution of maven install under directory deps failed. Does anyone meet this issue? Thanks Anthony Downloading: http://repo1.maven.org/maven2/com/cloud/com/vmware/vmware- apputils/1.0/vmw are-apputils-1.0.jar [INFO] Unable to find resource 'com.cloud.com.citrix:netscaler-sdx:jar:1.0' in repository central (http://repo1.maven.org/maven2) [INFO] Unable to find resource 'com.cloud.com.vmware:vmware-apputils:jar:1.0' in repository central (http://repo1.maven.org/maven2) [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) com.cloud.com.netapp:manageontap:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.cloud.com.netapp -DartifactId=manageontap -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.cloud.com.netapp -DartifactId=manageontap -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-netapp:jar:4.0.0- SNAPSHOT 3) com.cloud.com.netapp:manageontap:jar:1.0 2) com.cloud.com.f5:icontrol:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.cloud.com.f5 -DartifactId=icontrol -Dversion=1.0 -Dpackaging=jar - Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.cloud.com.f5 -DartifactId=icontrol -Dversion=1.0 -Dpackaging=jar - Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-network-srx:jar:4.0.0-SNAPSHOT 3) com.cloud.com.f5:icontrol:jar:1.0 3) org.libvirt:libvirt:jar:0.4.8 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.libvirt - DartifactId=libvirt -Dversion=0.4.8 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.libvirt - DartifactId=libvirt -Dversion=0.4.8 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cloudstack:cloud-deps:jar:4.0.0-SNAPSHOT 2) org.apache.cloudstack:cloud-plugin-hypervisor-kvm:jar:4.0.0-SNAPSHOT 3) org.libvirt:libvirt:jar:0.4.8 4) com.cloud.com.vmware:vmware-vim:jar:1.0 Try downloading
Re: OVS support for KVM
Hi, I think there will not. We want that feature too, and just started reading the code :) (2012/09/06 2:09), Jonas Vachal wrote: Good Day! Will the OVS support for KVM make it in to the 4.0 release (or is it already there)? Thanks! J.
RE: conserve mode for network offering
Ah! Didn't realize this was fixed as part of another bug. Excellent. Jessica T. CloudStack Tech Pubs -Original Message- From: Radhika Puthiyetath Sent: Wednesday, September 05, 2012 7:13 PM To: Jessica Tomechak; Alena Prokharchyk Subject: RE: conserve mode for network offering Hi Jessica, This is already documented as per CS-14200 -Original Message- From: Jessica Tomechak Sent: Thursday, September 06, 2012 6:20 AM To: Alena Prokharchyk; cloudstack-dev@incubator.apache.org Cc: Radhika Puthiyetat Subject: RE: conserve mode for network offering Alena, Thanks for the cc. Could you or Mice please file this as a doc bug? We can use the new Apache Jira instance: https://issues.apache.org/jira/browse/CLOUDSTACK Full instructions on how to fill out a doc bug are here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Documentation+Contributors+Overview#CloudStackDocumentationContributorsOverview-FilingaDocBug Jessica T. CloudStack Tech Pubs -Original Message- From: Alena Prokharchyk Sent: Wednesday, September 05, 2012 9:59 AM To: cloudstack-dev@incubator.apache.org; Jessica Tomechak Subject: Re: conserve mode for network offering On 9/4/12 11:27 PM, Mice Xia mice_...@tcloudcomputing.com wrote: Hi, all I noticed when 'conserve mode' is not checked for a network offering, the guest network created from this offering cannot do port forwarding and load balance if sourceNat is enabled. After checking network.js and wiki [1], I realized it was by design and much complicated than document said: 'Conserve mode. Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network.' Can someone explain why 'conserve mode' behave this way? Thanks. [1] http://wiki.cloudstack.org/display/QA/Network+Offering Regards Mice Mice, this description is wrong, the documentation has to be fixed. Adding Jessica to the thread. Conserve mode ON means that all public ip addresses associated with this network, can be used for multiple purposes at the same time (PF/LB). When the mode is off, the ip can serve only one purpose at a time. For static nat it's quite different though. Doesn't matter if conserve mode is on or off, when static nat is enabled, no PF/LB rule can be created for the IP. Only Firewall rules can be added using createFirewallRule command. -Alena.
Review Request: Add the dependence library (JNA) for maven exec:java goal
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6937/ --- Review request for cloudstack. Description --- Add the dependence library (JNA) for maven exec:java goal It is required to run on development environment for KVM Agent Diffs - plugins/hypervisors/kvm/pom.xml 8cdaa8681571b5070bfc501014df91c9986479e3 Diff: https://reviews.apache.org/r/6937/diff/ Testing --- 1) mvn compile -Dnonoss 2) prepare agent.properties 3) mvn exec:java -pl plugins/hypervisors/kvm \ -Dexec.mainClass=com.cloud.agent.AgentShell \ -Dnonoss result: An exception does not be raised. Thanks, Satoshi Kobayashi
Re: Review Request: Fix default assignment of physical network names
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6928/#review11080 --- Ship it! Ship It! - Sateesh Chodapuneedi On Sept. 5, 2012, 6:48 p.m., Venkata Siva Vijayendra Bhamidipati wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6928/ --- (Updated Sept. 5, 2012, 6:48 p.m.) Review request for cloudstack, Sateesh Chodapuneedi and Kelven Yang. Description --- Assign default port profile names if nexus is configured and physical network is not specified. This addresses bug CS-16286. Diffs - plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java 205fb26 Diff: https://reviews.apache.org/r/6928/diff/ Testing --- Thanks, Venkata Siva Vijayendra Bhamidipati
Re: Automating ASL license check
Hi Chip, On 06-Sep-2012, at 12:55 AM, Chip Childers chip.child...@sungard.com wrote: On Mon, Sep 3, 2012 at 6:51 AM, Rohit Yadav rohit.ya...@citrix.com wrote: Do we need to fix/add Apache license for: - text files (README, INSTALL, NOTICE etc.) - configuration files - awsapi (top level LICENSE suggest they're BSD 3-clause) - deps - docs - patches/ - plugins - apidocs/ - tools - ui What about these files/dirs? They don't have Apache or any other license. As we already removed most dependencies from the source tree, do we need to remove non-jars deps like jquery as well? This is very cool, but doesn't RAT do most of this for us? I know that we had some issues with the initial reports not providing an accurate indication of the stray Citrix license headers, but I think that is resolved now. I would suggest that another manual QA of the files would be helpful. Okay I'll check them manually this weekend but I trust grep/sed :) Once we are at a stable state (with the appropriate exclude properties set the RAT Maven plugin config at the top level pom.xml), we would have an automatic solution tied into Maven for auditing compliance. Does that work? As soon as we fix the build system issues, I'll give RAT a try, probably research on maven and maven plugins this weekend. Regards, Rohit -chip
