| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
compile node configurations, rather than using the Configuration
handler, which was never used directly. I removed the Configuration
handler as a result.
Modified the 'master' handler (responsible for sending configurations
to clients) to always return Time.now as its compile date, so
configurations will always get recompiled.
|
| |
|
|
|
|
|
|
| |
the catalog. The client will now always recompile, assuming it
can reach the server. It will still use the cached config if
there's a failure.
|
|
|
|
| |
name as a directory with no failures.
|
|
|
|
|
|
| |
internally), and fixing the Facts class so it
auto-expires any associated cached nodes when facts
are saved.
|
|
|
|
|
|
| |
class instead of the Indirector module. Also, added
an 'expire' method to the indirector, so there's an easy way
to expire cached instances.
|
| |
|
|
|
|
| |
expecting requests instead of having a random interface.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a Request instance into the indirection,
pushing it all the way to the terminus instances. It's
a big commit because it requires modifying every terminus class.
There are still some thorny design issues. In particular, who
should be responsible for making the request object? I've tried
having both the indirection class and the Indirector module creating
it, and both have their issues.
Also, the Catalog class previously allowed passing Node instances
directly to the find method, which is now no longer possible because
the Request class would treat the node as the instance being found.
We need the request class to have two modes, one when it's passed an
instance and one when it's passed a key.
|
|
|
|
|
| |
were added to Naginator, but no new related resource
types were added.
|
|
|
|
| |
with instances instead of just keys.
|
| |
|
|
|
|
| |
of the indirection request object.
|
|
|
|
|
|
|
|
|
| |
class is currently only used internally by the Indirection
instances, but I expect that I will soon be pushing it to
all of the terminus types.
I still need to fix a couple of tests that will get broken by
this commit.
|
|
|
|
|
| |
the name of the instance to be destroyed, rather than the
instance itself.
|
|
|
|
|
|
| |
based on timestamps. This just modifies the indirection class
itself, there is still some work to do to remove version code
from other classes.
|
| |
|
|
|
|
| |
expiration.
|
| |
|
|
|
|
|
| |
group list does not contain any commas. This seems to be
a common problem.
|
|
|
|
|
|
|
|
|
| |
fix UIDs but also GIDs
Fixes #1169
Fixes #804 (workaround was probably incomplete, as required changes in lib/puppet/util/posix.rb were missing)
Signed-off-by: Andreas Rogge <a.rogge@solvention.de>
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This reverts commit 4f8df9803a9ad2f31d3e86418732a230b5cee3f3.
|
| |\ |
|
| | | |
|
| |/
|/|
| |
| | |
why I removed it, since the information in it isn't anywhere else.
|
|/ |
|
|
|
|
| |
Also reformatted a bit
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
evaluation time, rather than resource instantiation time. This
means that you don't catch your "errors" as early, but it also
means you should be able to realistically configure a whole host
in one run.
|
|
|
|
|
| |
executable, since it otherwise causes caches to be used in all
cases, which we don't want (e.g., bin/puppet was using them).
|
|
|
|
|
|
| |
having it be a parameter. This is only useful if you want
a composite resource that just generates other resources and
passes the value on.
|
|
|
|
|
| |
server now that it's in the :puppetmasterd section rather than
a separate :yaml section.
|
|
|
|
|
|
|
| |
There is now a constant in Puppet::Network::HttpPool that will
disable or enable this feature, but note that we determined
that it can cause corruption, especially in file serving (but
it's client-side corruption).
|
|
|
|
| |
matching. The actual problem was caused by the fix to #1001.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
any local variables and added a local variable -- see
http://snurl.com/21zf8. My own testing showed that this
caused memory growth to level off at a reasonable level.
Note that the link above says the problem is only with class
methods, but my own testing showed that it's any method that
meets these criteria. This is not a functional change, but
should hopefully be the last nail in the coffin of #1131.
|
|
|
|
|
|
|
|
|
|
| |
files, thanks to work by Adam Jacob and Arjuna Christenson
(the finding, not the leak). I'm going to act like this
fixes #1131, at least for now, but I doubt it does,
since that shows general memory growth over time, whereas
the leak here should go away as soon as files are reparsed
(because the parser is holding the reference to the leaking
array).
|
|
|
|
|
|
| |
date if the node facts have been updated (thus causing
node facts to again be available in manifests, for those
cases where they were not).
|
|
|
|
| |
388cf7c3df7ce26e953949ed6fe63d76cbbb3691 to resolve #1137; also, add tests which detect the problem.
|
| |
|
| |
|
|
|
|
| |
password management
|
| |
|