elek opened a new pull request #2165:
URL: https://github.com/apache/ozone/pull/2165


   ## What changes were proposed in this pull request?
   
   Today ozonesecure compose clusters (and ozonesecure-ha and ozonesecure-mr) 
use an adhoc keytab issuer. The issuer is download during the image creation 
and uses a third party go lang application to create the keytabs on-demand.
   
   As discussed earlier, it would be faster to use a dedicated, pre-built 
container image which includes the pre-created keytabs instead of issuing them 
on-the fly (keytab generation is slow + container creation is slow)
   
   For each of the tagged images we can export to current keytabs to 
hadoop-ozone/dist/src/main/compose/ which can be mounted to compose clusters.
   
   It makes the overall acceptance test faster (instead of creating keytab, 
which is quite slow, we can start the cluster immediately). And we don't need 
to depend on an external utility app.
   
   Pre-created keytabs are also more similar to production environment...
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-5123
   
   ## How was this patch tested?
   
   CI is passed on my fork: 
   https://github.com/elek/ozone/actions/runs/763590947
   
   
   The time between starting test.sh script and first robot test:
   
   master: 3:30 (01:43:08 --01:46:38)
   this patch: 2:10 (12:59:29 13:02:39)
   
   (note: there are some variances between different builds, and in general the 
mentioned patch build was a slower one. It can be even faster).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to