| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
Manually resolved conflicts:
lib/facter/virtual.rb
spec/unit/virtual.rb
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With HP-UX you can build virtual machines that are often refered to as
HP-VMs.
This patch detecs HP-VMs by introducing a new function hpvm? that will
check the output of /usr/bin/getconf MACHINE_MODEL. This should not
depend on any tools that might be not installed.
If inside a HP-VM the command will say something like
ia64 hp server Integrity Virtual Machine
while on real hardware the output could be
ia64 hp server rx660
so searching for "Virtual Machine" should work.
Currently it only works if the guest is also running HP-UX.
(I guess this is the most common usecase).
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Manually resolved conflicts:
lib/facter/virtual.rb
spec/unit/virtual.rb
|
| |/
| |
| |
| |
| |
| |
| | |
While the fact virtual recognised solaris zones before, the is_virtual
fact did not.
With this patch applied is_virtual returns true on (non-global) zones
|
| | | |
| \ | |
|\ \ \
| | | |
| | | |
| | | | |
'pnasrat/tickets/master/4956' into next
|
| | |/ |
|
| |/
| |
| |
| | |
Fix is_virtual fact to return strings rather than bools.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
bin/facter
lib/facter/application.rb
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When Facter returns operatingsystem as "oel" or "ovs", the
operatingsystemrelease fact does not catch these properly, causing an
error.
Specs added to catch failure and case statement updated to catch "oel"
and "ovs" as well as "OEL" and "OVS"
|
|\ \ \
| | |/
| |/| |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
When Facter returns operatingsystem as "oel" or "ovs", the
operatingsystemrelease fact does not catch these properly, causing an
error.
Specs added to catch failure and case statement updated to catch "oel"
and "ovs" as well as "OEL" and "OVS"
|
|\ \ |
|
| |/
| |
| |
| | |
* With tests for 9.8.0, 10.3.0 and 10.6.4
|
|/
|
|
|
|
|
|
|
| |
Regexp tested the s_context or VxID field if /proc/self/status and
returned false for 0 and true for any other number. 0 indicates a host,
which is still virtual.
Fix changes regexp to correctly report hosts as virtual. Tested against
vserver 2.1 and 2.3.
|
|
|
|
|
|
|
| |
Updating the spec to check for the existence of /proc/vz to match the
change in the previously applied patch.
Signed-off-by: Rein Henrichs <rein@puppetlabs.com>
|
|\ |
|
| |
| |
| |
| |
| |
| | |
There was no support for detecting FreeBSD running in KVM as a virtual in facter. This patch detects KVM by getting "hw.model" kernel state via sysctl. Jails running in KVM are also correctly detected as "jail" not "kvm".
Signed-off-by: Jiri Kubicek <jiri.kubicek@kraxnet.cz>
|
| |
| |
| |
| |
| |
| | |
There was no support for detecting FreeBSD jails as a virtual in facter. This patch detects jail by getting "security.jail.jailed" kernel state via sysctl.
Signed-off-by: Jiri Kubicek <jiri.kubicek@kraxnet.cz>
|
| | | |
| \ | |
|\ \|
| | |
| | |
| | | |
'ticket/master/4453-rakefile'
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rewrite of uptime facts and supporting utility methods. Works on unix,
BSD, windows. No longer makes redundant system calls.
Uses Facter::Util::Uptime utility methods:
* Implemented uptime_seconds_unix using /proc/uptime or who -b on unix,
sysctl on BSD.
Added unit tests for the behaviors of get_uptime_seconds_unix: read
from proc/uptime, read uptime from "sysctl -b kern.boottime", read
uptime from "who -b", and return nil if nothing else works.
* Implemented uptime_seconds_win using the Win32 API.
Facts implemented:
* uptime_{seconds,hours,days}
Returns the respective integer value.
* uptime
Returns human readable uptime statistic that preserves original
behavior.
Examples:
3 days
1 day
5:08 hours
0:35 hours
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The 2nd regex (with the 0x\d+) got removed because it appears
to never be used, even on SunOS, for which it has been
introduced (99833a1b / #1793).
The 3dn regex is changed to clearly confine the value between
mandatory newlines/whitespaces.
|
|/
|
|
|
| |
This test compares a fact made with dmidecode (linux and bsd) with one using
smbios (solaris).
|
|
|
|
| |
Includes Rspec tests
|
|
|
|
|
|
|
|
|
|
| |
This patch is originally by Daniel Berger <djberg96@gmail.com>, I
changed using Facter.value instead of repeatedly testing
Config['host_os'], removed Resolution::which, and fixed the specs.
Thanks to Paul Nasrat for helping with cross-platform debugging.
Signed-off-by: David Schmitt <david@dasz.at>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Splitting dmi output on the string "/^Handle/" didn't work, and
caused the function to match the wrong key if it was found more
than once.
The intended behaviour of the function is restored by splitting
the dmi output on the regex /^Handle/.
|
|
|
|
| |
Signed-off-by: Paul Nasrat <pnasrat@googlemail.com>
|
|
|
|
|
|
| |
Process.waitall()
Thanks to Jos Backus for the fix.
|
|
|
|
| |
Based on initial patch by James Turnbull
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 33fb7709404e706801683e6c47ab7a0a5a1884b1.
This has broken master for some facts (eg OS X facts), it also breaks facter
platform support on win32 as popen3 does not work there.
I'd like to get master working, backlog of patches applied and revisit exec.
Paul
|
|
|
|
| |
This adds a test to ensure we are not prematurely splitting on Handle
|
|
|
|
|
|
|
|
|
| |
In addition to the stripping of the output of these facts this patchset:
Refactor - Extracted function to enable easier testing.
Tests - data driven tests for the dmidecode/smbios fact.
Paul
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far messages to stderr haven't been catched by
Facter::Util::Resolution.exec and were insted printed out to
stderr. This will cause facter and even puppet to print to stderr
themself, which is not very nice when running puppetd by cron,
as you might get every run a mail if a command outputs to stderr.
We are now wrapping the command execution with Open3.popen3 to
catch stderr and passing them to the new introduced Facter.warn
method.
We are also catching multiline outputs chomping newlines and
returning an array if there have been more than one line. Otherwise
we return an array containing the different lines.
This prevents in general cases as described in #2766 and should
handle command execution in a bit saner way.
|
|
|
|
|
| |
We can now warn messages that will be passed to Kernel.warn if
debugging is enabled.
|
|
|
|
| |
This adds a unit test on top of Kurt's patch
|
|
|
|
|
|
| |
Fix facts added with empty blocks by handling calls to value when setcode not called
Ensure we handle load failures more gracefully
|
|
|
|
|
|
|
|
|
| |
This cleans up xen and vserver detection to enable us to stub out so when we
happen to be running tests on xen we don't report as that.
More cleanup is needed in this area but this should give us a green build.
This renames the tests to be consistent with current naming convention
|
|
|
|
|
|
| |
We already have a network fact it's just missing a test.
Paul
|
|
|
|
| |
fact's value when collection has not being yet initialized.
|
|
|
|
|
| |
Solaris orders inet and inet6 seperately. This tests for and fixes this by
uniqueing the list. Will probably need work when we get to ipv6 support.
|
|
|
|
|
|
| |
coverage
switch %x{} call to Facter::Util::Resolution.exec for better testing
|
|
|
|
| |
Add tests and utility for virtual fact detection
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This seems to have been fixed functionally on master
(in /Users/pnasrat/Development/facter/spec)
Finished in 1.604955 seconds
183 examples, 0 failures
However I want to take the opportunity to add tests to prevent regressions
Paul
|
| |
|
|
|
|
|
|
|
|
| |
Added tests for operatingsystem fact covering the two simple cases and a test
for this specific interaction of release files
We should take some time to add tests when we're adding or changing new
operatingsystem facts
|
|
|
|
| |
Added a test to pickup typo and fix
|
|
|
|
|
|
|
|
| |
The interface collection regex was leaving trailing
':' characters on the interface names, which meant
individual interfaces weren't quite right.
Signed-off-by: Luke Kanies <luke@madstop.com>
|