cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafael Fonseca <rsafons...@gmail.com>
Subject Re: Cloudstack Repackaging / Distro support
Date Tue, 12 May 2015 10:03:51 GMT
Wido,

If we were to recommend proxying with httpd, shouldn't cloudstack provide
that as well out of the box?
Btw, there isn't really a big performance gain by proxying through httpd
nowadays, the new version of the packaging also includes using tomcat8,
which has an improved http/nio connector, have a look here for some
performance benchmarks :) ->
http://www.tomcatexpert.com/blog/2010/03/24/myth-or-truth-one-should-always-use-apache-httpd-front-apache-tomcat-improve-perform

What i think is that if we are going to suggest configuring httpd on the
same box we should do it automatically, if not, tomcat can still run on
port 80 by default and user can reverse proxy from any other machine :)

Also, if we're sticking to tomcat, we should have scripts build the
APR/native connector for improved performance :)
http://tomcat.apache.org/native-doc/

This would be an improvement independent from using or not httpd/nginx in
front of tomcat.





On Tue, May 12, 2015 at 11:45 AM, Wido den Hollander <wido@widodh.nl> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 05/12/2015 11:37 AM, Erik Weber wrote:
> > On Tue, May 12, 2015 at 10:59 AM, Rafael Fonseca
> > <rsafonseca@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> I'm reworking the packaging system in cloudstack, and would like
> >> to gather your opinion on the following:
> >>
> >> - Fedora 2x runs systemd's cockpit on port 9090 by default This
> >> is a deal breaker for the cluster servlet port on this OS, the
> >> two possibilities would be to either pack changes to fedora's
> >> config on rpm install or simply change the servlet port to
> >> another one that does not clash on any distro.. any
> >> comments/suggestions?
> >>
> >> - Tomcat is not listening on port 80 Tomcat is using port 8080,
> >> which makes the user have to specify that in the browser.. should
> >> we change it? In ubuntu it's already running under jsvc, so it
> >> shouldn't be a problem.. same can be arranged for centos/other
> >> distros.
> >>
> >
> > Is it possible to ask the user for this during installation and
> > default to either 80 or 8080? I know Debian has a way to interact
> > with the user during install, not sure about RedHat.
> >
> > I don't know the rationale behind putting it on port 8080 in the
> > first place, but personally I don't see a problem moving it to port
> > 80.
> >
>
> I'd say to stick to 8080 and recommend anybody to use Apache / Nginx
> to proxy towards Tomcat.
>
> >
> >> - No link on the tomcat root (http://management-server/ can link
> >> internally to http://management-server/client , this makes it
> >> easier for new users who don't know the URL for the UI :)
> >>
> >>
> > Sounds like a good idea to me, I always forget to add /client when
> > I browse to new installations.
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJVUcugAAoJEAGbWC3bPspCmzYP+QF8FOnikqiqUI+qtsHB70gf
> Z3RbTltbncGb4ENg48kDxrXThufE2lHCOOZYkwb3mrsqX78BdWojlxxvymbp3SO8
> HdysI7LcGDGnoKPdveGtrHqtGBWhbcgIT5f43bU1Ks7GaQVjWdMdayp6ooYEtjA4
> CpzzlqAJvA0oibfeTLFnfSF0IiSvqXtminjjWcNzhifusfn2aijzowemNFyYOU4d
> UxDVdaKGUSwMxKGj3Zvqva1KO3tng5nKpS8r6Xe7WyVCKAJ8ewaNUI6KJ5hOw50J
> ENLrdcRZ82Nw+iqtV8MgB0VJSXKuWYJ+OQ6f9SplmJOe3Au+jyfIFEqwliGCtEmL
> 01naERq+/7HAz1JjSoj0c+LBNBxB6FePpZDgkhJJZ51NoLeE/yQuxShV8Ihnk/39
> yIfDyb/95DMG+n9qdglp7hav+tCwJL6q70LIK1DUXRleLvPyrgqnvx9AZwQtoYcZ
> BuTn9F6xiZg8Q5xRQokUiyNzj6RWlm8EZF8PBf/og6DfVYuH559mPqu3OJcAlJkz
> /RB3vhNjc/3Hso2lVFu2p6cVvc+hkM31c4/h338d6NPEqD3wMkBdhCDvTf+jkC7i
> GNfYLtKlc7KIkA5bCJxvxbidIxdi1adXs6Lxz8xY0mKliMORd9NyLca6KIXOqAkJ
> j6c/I3UglqkTLQjOKjXZ
> =pBnh
> -----END PGP SIGNATURE-----
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message