0

Or does the master cache the repository from the internet and provision for the agent nodes?

In either case, how are updates deployed and managed? What pre-empts what?

Edit: How are rpm updates, yum updates, tarball updates, zypper updates, apt-get updates etc.. deployed/managed/supervised.

2
  • Updates of what?
    – ewwhite
    May 15, 2015 at 12:57
  • 1
    The master doesn't cache OS package repositories, it just runs the yum/apt, etc command to ensure what you told it to ensure.
    – jordanm
    May 15, 2015 at 13:22

1 Answer 1

0

How are rpm updates, yum updates, tarball updates, zypper updates, apt-get updates etc.. deployed/managed/supervised.

There is no default configuration for this. You define it yourself.

For my Debian systems I use puppet to update the apt sources lists on my nodes that point at an approx instance (apt proxy/cache) that just happens to run on my puppet host. If I didn't do that, the machines would just go out using whatever apt sources were defined at install time.

Just as easily you could download things on your puppet master and deliver them to your nodes via file{} resources. It is all up to you. Nothing auto-magical takes place here. You define the behavior you want.

2
  • Thank you very much for clarifying. You answered my question.
    – Mugambo
    May 15, 2015 at 18:54
  • @Mugambo if this answered your question, you should mark it as the accepted answer.
    – faker
    May 22, 2015 at 8:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .