cf-charmers team mailing list archive

[Alexander Lomov <lomov.as@xxxxxxxxx>]

Hey, all.

I've wrote an Admin UI juju charm, it can be found here:
https://github.com/altoros/admin-ui-juju-charm.

Admin UI required some changes in CF juju charms, I used my branch to
perform them:
https://code.launchpad.net/~lomov-as/charms/trusty/cloudfoundry/trunk.

Recap of changes in the branch:

   1. I needed to add UUADBRelation in order to give Admin UI access to UAA
   DB:
   http://bazaar.launchpad.net/~lomov-as/charms/trusty/cloudfoundry/trunk/view/head:/cloudfoundry/contexts.py#L171
   2. I needed to rename some relations to be able to use them in jinja2
   templates with latest services module of charmhelpers (it doesn't support
   dashes in the names):
   http://bazaar.launchpad.net/~lomov-as/charms/trusty/cloudfoundry/trunk/view/head:/cloudfoundry/contexts.py#L379

The one thing that is left is authentication to Admin UI through UAA. In
the latest version Admin UI takes advantage of UAA authentication, this
requires Admin UI to be registered in UAA, you can find script that makes
it in the end of README file:
https://github.com/altoros/admin-ui-juju-charm#usage. Sure, it has to be
implemented as a hook and I want to discuss implementation. I think that
the best way here will be to have distinct uaa-relation-joined hook with
bash script (and uaa-relation-broken hook will remove admin_ui group from
UAA). What do you think about it?

Also there is a question about the right way of exposing admin-ui. I would
like if it will be exposed through router, still it is not. Need to dig
deeper into it.



Thank you,
Alex L.