service cloudstack-management is being displayed as cloud-management
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit 718bc97a7e)
Retains the systevm.iso from the previous run causing systemvm.iso to
never update itself. Do a complete clean install for all profiles
specified in mvn.
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit 55db2fe6d1)
catalina.out must be prepared by package installation.
This is the same fix in tomcat6 package.
Signed-off-by: Hiroaki KAWAI <kawai@stratosphere.co.jp>
Sorry about this, my packaging test system is out of order :-(
(cherry picked from commit 171a967437)
Signed-off-by: Hugo Trippaers <trippie@gmail.com>
Added ipset in cloud.spec as part of agent install.
Signed-off-by: Pradeep <pradeep.soundararajan@citrix.com>
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
Detail: Uninstallation of old RPMs wipes out some of the configs, and makes it
difficult to reapply existing configs. This change moves the config directory
to cloud.rpmsave, and then pulls in necessary files from that location during
post install of agent and management server.
Test passed:
install 4.0 RPMs, set up advanced zone
build 4.1 RPMs via package.sh, with this patch
install 4.1 RPMs
restart cloudstack-management, cloudstack-agent
verify management, agent, and zone is operational
BUG-ID: CLOUDSTACK-1694
Signed-off-by: Marcus Sorensen <marcus@betterservers.com> 1364409632 -0600
Summary: EC2 REST API: AWS APIs are not getting translated on the CloudStack Management Server and AWS API Installation Problems.
Fixing the class not found exception, key not found and other issues as mentioned in the above two defects.
Signed-off-by: Pradeep <pradeep.soundararajan@citrix.com>
Proposing to modify the behaviour of package.sh script. Package as per OSS or NONOSS arguments.
Signed-off-by: Pradeep <pradeep.soundararajan@citrix.com>
working again.
The newly created package for cloudstack-management was not correctly
installing the service. This prevented cloud-setup-management from being
able to configure the service, and the init script didn't even believe
the service was installed. I also added sudo to the chmod command for
checking script permissions, as most scripts belong to root. It was
trying to configure the agent with cloudstack-setup-agent but the script
was still called cloud-setup-agent, so I renamed it to cloudstack-setup-agent.
Summary: EC2 REST API: AWS APIs are not getting translated on the
CloudStack Management Server and AWS API Installation Problems.
This fixes the above two defects and other packaging related issues.
Signed-off-by: Chip Childers <chip.childers@gmail.com>
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>
Wei Zhou
Prachi Damle
David Nalley
Prasanna Santhanam
Marcus Sorensen
Hiroaki KAWAI
Hugo Trippaers
Marcus Sorensen
Wido den Hollander
Hugo Trippaers
Wido den Hollander
Pradeep
Brian Spindler
Noa Resare
Ricardo P. Katz