[EnMasse] Adapting the EnMasse deployment

[Lohmann Carsten (INST/ECS4)]

Good, thank you for the info.

One further difference in the Hono qdrouter config is the inclusion of the artemis broker.

While I see an artemis image being referenced in the nested JSONs of the Kubernetes enmasse.yaml, 
it seems there is no such container being deployed after applying enmasse.yaml.
Is inclusion of the broker in Kubernetes currently not enabled/supported?
One thing I'm still trying to grasp is the way the Kubernetes resources defined in the ConfigMap with the JSONs 
actually get applied/deployed.
Do you have pointers here on the corresponding Kubernetes mechanisms used for that?

Best regards

 Carsten Lohmann

(INST/ECS4) 
Bosch Software Innovations GmbH | Schöneberger Ufer 89-91 | 10785 Berlin | GERMANY | www.bosch-si.com
Tel. +49 30 726112-130 | Fax +49 30 726112-100 | carsten.lohmann at bosch-si.com

Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B 
Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn 




-----Ursprüngliche Nachricht-----
Von: Ulf Lilleengen [mailto:ulilleen at redhat.com] 
Gesendet: Freitag, 16. Juni 2017 14:30
An: Lohmann Carsten (INST/ECS4) <Carsten.Lohmann at bosch-si.com>; enmasse at redhat.com
Betreff: Re: [EnMasse] Adapting the EnMasse deployment

On 16. juni 2017 12:44, Ulf Lilleengen wrote:
> On 16. juni 2017 12:08, Lohmann Carsten (INST/ECS4) wrote:
>> Hi Ulf,
>>
>>>  Out of curiosity, what is it that you wish to modify in this config?
>>
>> We want to use a config similar to the one used in Hono:
>>
>> https://github.com/eclipse/hono/blob/master/dispatchrouter/qpid/qdrou
>> terd-with-broker.json
>>
>>  > I.e. with our sslProfile / certificates and vhost definitions.
>>
> 
> One thing to look out for there is that the enmasse router config is 
> created dynamically from a static fixed template + configuration from 
> the router agent (address config for instance).
> 
> To make it work properly in EnMasse, you have to merge that config 
> with the static enmasse router config:
> 
> https://github.com/EnMasseProject/dockerfiles/blob/master/qdrouterd/qd
> routerd.conf.template
> 
> 

Just to elaborate on this part: Eventually we hope to provide a way in EnMasse to do this without overriding the router config. For certs, you can edit the certificates used by the router by creating/editing the secret 'certs-$namespace' where $namespace is the namespace where you deployed EnMasse to, which will be used for external connections.

We intend to improve the certificate management in the near future in combination with keycloak integration.

How to add vhost definitions is something that needs more discussion, but we're working on a backlog so this is useful input.

--
Ulf