brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <...@git.apache.org>
Subject [GitHub] brooklyn-library issue #129: Move chef from brooklyn-software-base to own mo...
Date Tue, 19 Sep 2017 08:22:53 GMT
Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-library/pull/129
  
    @tbouron changes made; ready for review + (hopefully!) merge.
    
    @tbouron For why we have ansible, chef and salt in different modules (versus databases
in one module), we don't have a hard-and-fast rule. However, with hindsight having entities
like databases in the same brooklyn module was a mistake. Their release cadence and versioning
are tied to that of brooklyn-core. They should have been in a community-contributed place
like "brooklyncentral" in my opinion. And should have been in separate modules there.
    
    For ansible, chef etc - though they are solving a similar problem, they are very different
integrations so I think it's good to separate them into different modules.
    
    The most compelling immediate answer though is that ansible and salt area already in different
modules, so we're not going to combine them! And we should follow the same pattern for chef.


---

Mime
View raw message