[Pkg-puppet-devel] Starting puppet agent by default

[Stig Sandbeck Mathisen]

Russ Allbery <rra at debian.org> writes:

> Stig Sandbeck Mathisen <ssm at debian.org> writes:
>
>> * The puppet agent process may around until enabled, and possibly being
>>   restarted by systemd a few times.
>
> Can we disable the Puppet agent by creating the lock file in preinst
> rather than using the official command-line method? (We have code at
> Stanford that manipulates the lock files directly because we do things
> like include administrative comments in them.)

Use preinst instead of postinst to further decrease the risk of
something starting the puppet agent before we lock it?

>> * Running "puppet agent" may work when "puppet-common" is installed, and
>>   then not work when installing "puppet" until someone runs "puppet
>>   agent --enable".  Should the "--disable" be in "puppet-common", even
>>   if this does not enable the puppet agent service?
>
> Yes, I think so.
>
>> * The set of puppet packages probably need renaming. The current set
>> of packages reflects how puppet looked at 0.25, and puppet has
>> changed a bit since that.
>
> Agreed. Maybe puppet-common => puppet-client and puppet =>
> puppet-service? (puppet-service isn't a great name, but I can't think
> of a better one off-hand.)

I would like to use puppet's terminology for what the packages contain.

An alternative is putting all the puppet software into the package
"puppet", and then adding a package for each running service, like
"puppet-agent" (if that should not be included in "puppet"), at least
one for "puppet-master" and for "puppet-master-passenger".

I'd want to discuss the future packaging with the puppet labs packagers,
too.

Right now you can go between the puppet labs packages and the
distribution packages in Debian and Ubuntu just by changing the apt
source. I would like to keep it that way.

-- 
Stig Sandbeck Mathisen <ssm at debian.org>