On Wed, Apr 1, 2015 at 5:23 PM, Dhaval <
d.jo...@gmail.com> wrote:
> Thanks for your time in explaining, what i understand is "roles and
> profiles" is different from Hiera and ENC which is used for providing data
> only. Let me search for example where Hiera is used and roles and profiles
> are defined to make difference in data as per the defined profile.
You are discussing three very different things here, an ENC is, at
it's most basic form, just a classifier that says node X should apply
class Y - though there are much more sophisticated things that one can
do with an ENC, in the scope of this example lets leave it at that.
What class Y actually is, is where roles and profiles come in. Roles
and profiles are merely a design pattern for laying out your classes
to add some layers of abstraction between component modules (the
actual cogs) and roles (business logic) - when people adopt roles and
profiles they tend to classify just the nodes role in the ENC. Hiera
is a different concept entirely and is used to provide hierarchical
data lookups which determine what data values are applied based on a
pre-determined series of overrides that are customized to your
particular environment.
https://www.youtube.com/watch?v=ZpHtOnlSGNY is a talk I did on this
some time ago, and towards the end Hiera and ENCs are touched on
Some of the relevant parts are;
http://www.slideshare.net/PuppetLabs/roles-talk
- #71 Hiera
- #88 ENC
- #92 Stack diagram
Hope this helps.
Regards
Craig
--
Enviatics | Automation and configuration management
http://www.enviatics.com | @Enviatics
Puppet Training
http://www.enviatics.com/training/