Ho to use with multi-domain?

9 views
Skip to first unread message

yar

unread,
Jun 27, 2008, 12:06:16 PM6/27/08
to GHeimdall
I have 3 domains we use with google apps - lets say aaa.com, bbb.com
and ccc.com.

Is it possible to use Gheimdall with that? How to configure?

Your suggestions are highly needed :)

tmatsuo

unread,
Jul 15, 2008, 6:25:16 AM7/15/08
to GHeimdall

Hi yar,

I'm very very sorry for delayed answer. Something went wonky and your
e-mail didn't appear in my GMail INBOX.
I'll look into it in hurry, so could you please wait a little while.

Regards,

tmatsuo

unread,
Jul 16, 2008, 3:31:16 AM7/16/08
to GHeimdall

Hi yar,

Sorry again for delayed answer.

On Jun 28, 1:06 am, yar <yan.ro...@gmail.com> wrote:
> I have 3 domains we use with google apps - lets say aaa.com, bbb.com
> and ccc.com.
>
> Is it possible to use Gheimdall with that? How to configure?

It is more of a troublesome work than a easy setup. However, yes. Some
instructions follow.

First of all, if you follow this instruction, it will become harder to
apply future versions to your environment. Everytime you make upgrade,
you need to do some work.

Take your time, and please think about preparing as much servers as
your domain, again ;-)


1. Clone /etc/gheimdall directory as much as you want.

# cp -ar /etc/gheimdall /etc/gheimdall-instance1


2. Edit your app.cfgs. Comment out all of the domain specific
settings. The settings that you commented out should be stored in
prod.cfg later.

session_filter.cookie_name
session_filter.timeout
session_filter.storage_type
session_filter.storage_path

apps.domain
apps.privkey_filename
apps.domain_admin
apps.admin_passwd

apps.ldap_uri
apps.ldap_basedn
apps.ldap_filter
apps.ldap_rootdn
apps.ldap_rootpw
apps.ldap_passwd_hash_style

3. Edit /etc/gheimdall-instance1/prod.cfg to fill the domain specific
settings. Make sure to put these settings in [global] section.

4. Edit /etc/gheimdall-instance1/gheimdall_modpython.py like
following:

configfile="/etc/gheimdall-instance1/prod.cfg",

5. Edit your /etc/httpd/conf.d/gheimdall.conf. The example bellow is
for two instances of GHeimdall those are placed into
/etc/gheimdall-instance1 and /etc/gheimdall-instance2. Please don't
forget to add the first line, it's very important.

-- /etc/httpd/conf.d/gheimdall.conf begins
PythonInterpPerDirective On

# instance1
ScriptAlias /gheimdall-instance1/ /usr/lib/python2.4/site-packages/
gheimdall/
<Location /gheimdall-instance1>
SetHandler python-program
PythonHandler modpython_gateway::handler
PythonOption wsgi.application cherrypy._cpwsgi::wsgiApp
PythonFixupHandler gheimdall_modpython
PythonPath sys.path+['/etc/gheimdall-instance1']
PythonDebug on
</Location>

# instance2
ScriptAlias /gheimdall-instance2/ /usr/lib/python2.4/site-packages/
gheimdall/
<Location /gheimdall-instance2>
SetHandler python-program
PythonHandler modpython_gateway::handler
PythonOption wsgi.application cherrypy._cpwsgi::wsgiApp
PythonFixupHandler gheimdall_modpython
PythonPath sys.path+['/etc/gheimdall-instance2']
PythonDebug on
</Location>

<Location /gheimdall-instance1/manage*>
AuthType "Basic"
AuthName "GHeimdall Manage"
AuthUserFile "/etc/httpd/conf/ins1-userpasswd"
Require user sso
</Location>

<Location /gheimdall-instance2/manage*>
AuthType "Basic"
AuthName "GHeimdall Manage"
AuthUserFile "/etc/httpd/conf/ins2-userpasswd"
Require user sso
</Location>

-- /etc/httpd/conf.d/gheimdall.conf ends

At last, it's done. I'm sorry it's very long way. I'd recommend that
you'd better prepare prural servers specialized for each domain.

Regards,

-- Takashi Matsuo

Lassina Ouattara

unread,
Sep 6, 2009, 10:56:04 AM9/6/09
to tmatsuo, ghei...@googlegroups.com
Have successfully done this with two domains. I have used different a
approach to this problem in the past and this one is pretty tedious in
terms of upgrading.
Not sure It's the best for me. Also where is the link to gaeheimdall
source. I want to try it.

-
Lassina

Reply all
Reply to author
Forward
0 new messages