This should have been already merged into 4.1, but didn't come through properly.
We use the JNA version shipped with CentOS 6.X since that works best with
libvirt 0.4.9
Description: Added the pre run for awsapi where it will create the user 'cloud' during awsapi install and removed the unwanted entries from packaging awsapi.
Signed-off-by: Chip Childers <chip.childers@gmail.com>
This patch inclused the packaging work from master tailored for 4.1
Not everything has been tested yet, but it should generate DEB packages.
Signed-off-by: Wido den Hollander <wido@42on.com>
Moved the post awsapi section to the post management since it is trying to provide symb link before installing management server.
Signed-off-by: Pradeep <pradeep.soundararajan@citrix.com>
server. It was printing a meaningless failure if the cloud
user's home dir didn't need to be updated.
Signed-off-by: Marcus Sorensen <marcus@betterservers.com> 1362809648 -0700
web.xml now references a log4j-cloud.xml relative to the webapp root
to capture early logging from spring. This change introduces a symlink
in the client webapp to the system wide log4j-cloud.xml which works around
a problem starting cloud-management described in CLOUDSTACK-1436
CLOUDSTACK-1436: 4.1 management server fails to start from RPM...
CLOUDSTACK-1423: Unable to launch UI [HTTP Status 404 - ]
Signed-off-by: David Nalley <david@gnsa.us>
Detail: getting "hard link not allowed for directory" due to line 321 in
cloud.spec. Changing to symlink.
Signed-off-by: Marcus Sorensen <marcus@betterservers.com> 1361982798 -0700
Some concepts included:
* the replace.properties location used by maven is parameterized to allow
for a build that does not modify the currently git tracked files
* package naming is updated along the lines of what was discussed on the
-dev mailing list and between committers at the Build a Cloud Day in Belgium.
* package version pattern is updated (since we redo all package names,
we might as well drop the epoch)
Make the usage server look in the /etc/cloudstack/usage server for the db.properties
Add the /etc/cloudstack/usage to the package as an empty dir
(cherry picked from commit d92725e846)
Separate stderr and stdout output from jsvc
(cherry picked from commit 0fa3ed9b74)
Signed-off-by: Hugo Trippaers <htrippaers@schubergphilis.com>
Change on cloud.spec for the message about vhd-utils point to the new
location of cloudstack scripts
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
Description: current package.sh fails if user hasn't downloaded all maven poms
prior to running package.sh. Now we match for something that vaguely resembles
a cloudstack version.
Signed-off-by: Marcus Sorensen <marcus@betterservers.com> 1360889840 -0700
The change in package script allowed us to create proper tar under rpmbuild/SOURCES directory
The change in the path enabled us to launch the management server properly.
Signed-off-by: Hugo Trippaers <htrippaers@schubergphilis.com>
Committed-by: Hugo Trippaers <htrippaers@schubergphilis.com>
(cherry picked from commit a9955f155a)
Signed-off-by: Hugo Trippaers <htrippaers@schubergphilis.com>
Remove duplicate entries in the config dir
Fix directory permisisons of some directories
Remove the scripts from the webapp as they are packaged inside the cloudstack-common package
(cherry picked from commit 5af6d16c5d)
Signed-off-by: Hugo Trippaers <htrippaers@schubergphilis.com>
Empty paths lead to unpleasant surpises later on
Use basename to find the pid file when stopping tomcat
(cherry picked from commit 0cc4636a2d)
Signed-off-by: Hugo Trippaers <trippie@gmail.com>
Renamed a whole bunch of stuff from cloud to cloudstack
Fix startup of cloudstack-agent
(cherry picked from commit 5bf6771e60)
Conflicts:
packaging/centos63/cloud.spec
Make the start method work again with jsvc
Move the usageApplicationContext to resources and add resources to the pom.xml
Remove the old components file
Add mysql-connector as a runtime dependency
Rename the usage package and the files to cloudstack
Change paths to the new proposed locations
(cherry picked from commit 7ce03b4f8e)
Signed-off-by: Hugo Trippaers <trippie@gmail.com>
Modify the spec file to package the agent files and the scripts
Some changes to the poms to put the java dependencies in the right place.
Move the agent script to the dedicated os dir in packaging.
Right now it isn't working yet, but this is the way it should start working
like the RPM package building is.
This commit is to clean up the rules file a bit and lay the groundwork for
the Debian packaging
This is a manual merge of the maven-to-rpm branch. This commits show how an RPM
package can be built without waf. The current version only builds the management
server rpm and some related rpms like setup. The main missing items are agent rpm and
the awsapi rpm. But it should at least show how to use maven and packaging.
Several small tweaks are put into the client/pom.xml to make sure that the war
has all items required to run as a standalone war.