cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10012) Migrate to Embedded Jetty based mgmt server
Date Wed, 01 Nov 2017 09:54:00 GMT


ASF subversion and git services commented on CLOUDSTACK-10012:

Commit 404d71d4be0c07f839e3cf20e05dd2ea04e33c7a in cloudstack's branch refs/heads/CLOUDSTACK-10012
from []
[;h=404d71d ]

CLOUDSTACK-10012: Migrate to Embedded Jetty

- Migrate to embedded Jetty server
- Improve ServerDaemon implementation
- Introduce a new file for easier configuration
- Have a single /etc/default/cloudstack-management to configure env
- Reduce shaded jar file, removing unnecessary dependencies
- Upgrade to Spring 5.x, upgrade several jar dependencies
- Does not shade and include mysql-connector, used from classpath instead
- Upgrade and use bountcastle as a separate un-shaded jar dependency
- Remove tomcat related configuration and files
- Have both embedded UI assets in uber jar and separate webapp directory
- Refactor systemd and init scripts, cleanup packaging
- Made cloudstack-setup-databases faster, using `urandom`
- Remove unmaintained distro packagings

Signed-off-by: Rohit Yadav <>

> Migrate to Embedded Jetty based mgmt server
> -------------------------------------------
>                 Key: CLOUDSTACK-10012
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Major
>             Fix For: Future,
> CloudStack installation has huge dependency on distro provided tomcat, by moving to embedded
jetty (like we do use jetty for development) we can sync how developers develop/test mgmt
servers and users use it. In addition, it will be easier to publish pkgs without depending
on distro provided dependencies.

This message was sent by Atlassian JIRA

View raw message