[GitHub] [hadoop-ozone] elek edited a comment on issue #238: HDDS-2588. Consolidate compose environments

[GitBox <gi...@apache.org>]

elek edited a comment on issue #238: HDDS-2588. Consolidate compose environments
URL: https://github.com/apache/hadoop-ozone/pull/238#issuecomment-557153711
 
 
   Thanks to work on this @adoroszlai . I always felt the same, that we have too many environments, but I didn't know the right answer. therefore I just share my thoughts this is not a :+1:  or :-1:  as I don't know which one is the better. 
   
   1.THE PHILOSOPHY 
   
   It's -- at least partially -- a philosophical question, what is Ozone. (And as it's philosophy, I am interested about the opinion of our philosopher of Ozone cc @anuengineer)
   
   By default I would say:
   
   - ozone = scm/om/datanode + s3g + recon
   - ozone-perf = ozone + all the tools to monitor
   
   But we can also say what what this patch says:
   
   - ozone: the full ozone experience (scm/om/datanode + s3g + recon + all the monitoring tools).
   
   (at lest for Apache Ozone, this is not true for proprietary distributions).
   
   2. THE USABILITY
   
   The other question is usability: Do we need Prometheus and Jaeger all the time. Do we need to start them when we would like to test any of the features of ozone?  
   
   Prometheus: maybe
   Jaeger: I am not sure.
   
   3. THE GUARANTEE
   
   My third (actual) problem is the guarantee of a cluster. To avoid same flakiness I would like to declare that we need at least 3 datanodes for ozone compose clusters (see. HDDS-2606). But I am not happy with the usability that Ozone can't work if you don't do a `docker-compose scale datanode=3`
   
   We may need a smaller subset of ozone (`ozone-core`) where the three datanodes are not required (but not used to run all the different acceptance testing). In this case the usability problem (2) can be solved as we can have a leaner ozone cluster to test locally. 
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org