erp5testnode: Use userhosts on erp5testnode (WIP)

software/erp5testnode/buildout.hash.cfg

@@ -19,4 +19,4 @@ md5sum = 307663d73ef3ef94b02567ecd322252e
 
 [template-default]
 filename = instance-default.cfg
-md5sum = 76f63d443c5fdcea6fac68791c6bb65b
+md5sum = aab6f8218dec4674d74a7af60d16dfdb

software/erp5testnode/instance-default.cfg

@@ -73,6 +73,10 @@ apache-modules-dir = ${apache:location}/modules
 apache-mime-file = ${apache:location}/conf/mime.types
 apache-htpasswd = ${apache:location}/bin/htpasswd
 
+# userhosts definition
+userhosts-bin = ${userhosts:location}/userhosts
+userhosts-HOSTS = $${rootdirectory:etc}/hosts
+
 [shell]
 recipe = slapos.cookbook:shell
 wrapper = $${rootdirectory:bin}/sh

[Jérome Perrin]

@rafael this does not configure hosts does it ?

ref !303 (merged)

[Jérome Perrin]

I mean !303 (merged) we try to:

1. run with services from ERP5 instance mapped so that test can access to erp5-catalog-0 or erp5-volatile-memcached, so that tested software can use these names to access services
2. run under the wrapper to run in an environment closer to real running ERP5

This only covers 2, isn't it ?

[edit ... covers 1 2 ]

[Rafael Monnerat]

@jerome The goal is tell the test to use cloudooo.erp5.net on machine X for a given test node, and on another test node use on Machine Y (depending the parameters the user inputs).

So this is complementary to !303 (merged) , not a replacement.

[Jérome Perrin]

Thanks for explanation @rafael . I understand the use case, that makes sense.

As you know usershosts only operates at the hostname level and does not allow using different port or different protocol ( http / https ) so I'm not sure how we will do this.

[Rafael Monnerat]

Port and protocol can only be implemented these days with some service discovery server (like consul for example), however it is a bit overkill for the current design. We would end up generally agree in use https, some standard port (like 80/443 via frontend), at least for cloudooo.