| Age | Commit message (Collapse) | Author |
|---|
|
+ bumpup gemspec
|
|
|
|
|
|
ScreenOS support
|
|
|
|
Brocade Vyatta model added
|
|
|
|
|
|
Updates
|
|
|
|
|
|
|
|
|
|
|
|
instructions for CentOS, OL and RHEL
|
|
|
|
|
|
Added Brocade Fabric OS support
|
|
|
|
|
|
|
|
we now support network based SQL and 'file' make little sense in
postgres/mysql, changing that to 'database' makes it reusable for both
use cases.
|
|
Added Force10 support
|
|
We need to return value of 'r' instead of value of previous evaluation.
|
|
|
|
- actually start to follow semantic version
- a.b.c a == major, b == minor c == patch
- c only for bug-fixes etc
- b for non-breaking new features
- a for breaking new featires
- a == 0 is special, can break anywhere
- http://semver.org
- add more specific version restrictions for gems
|
|
We are doing this in sql.rb
:user => @cfg.sql.user?
:password => @cfg.sql.password?
As 'asetus' will accept arbitrary chain
@cfg.sql.one.two.three
it is clear that 'one' or 'two' cannot _ever_ return nil/false,
otherwise you cannot create 'three'.
So if there isn't value of one/two, instance of 'asetus' is returned,
upon which we can build two, and then tree'.
one?, two?, three? version existed in old asetus, as strict boolean test
@cfg.sql.one? would return true, false or nil
In newer version, instead of returning true, it returns actual value.
|
|
SQL file in configuration renamed to database.
Should the generated example file have host+user+password+query?
|
|
Generic SQL support for source
|
|
config option "file" got renamed to "database", added authentication options for other SQL adapters and an optional query argument to overwrite the generic query.
config snipplet:
sql:
adapter: mysql2
user: sqluser
password: sekrit
host: mysql.local
database: inventory
table: devices
query: SELECT `fqhn` AS `name`, lower(`vendor`) AS `model` FROM `devices` INNER JOIN `devtypes` ON (`devtypes`.`id` = `devices`.`model_id`) WHERE (`aktiv` = 'J')
map:
name: name
model: model
|
|
|
|
|
|
|
|
core.rb: Improve error message
|
|
|
|
a) put metainformation on top, rancid style
b) remove changing data from 'show system'
|
|
Even after manually setting author+committer, it still crashed with:
Config value 'user.name' was not found [Rugged::ConfigError]
Not sure where it would want to use it, after author+committer already
are set, but I guess this method is more robust anyhow.
|
|
Ratioinale is, we want to keep it default, but it should be easy for
people to understand what to do, if they don't want it.
Closes #17
|
|
a) grit is not supported, rugged is
b) grit requires git CLI installed, rugged does not
c) grit needs monkey patching to work, rugged does not
Closes #21
Closes #22
|
|
|
|
|
|
Looks like this in syslog:
Jul 11 21:05:53 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 22"
Jul 11 21:05:53 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 23"
Jul 11 21:05:54 ytti oxidized[9820]: 10.10.10.10 status no_connection, retry attempt 1
Jul 11 21:05:54 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 22"
Jul 11 21:05:54 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 23"
Jul 11 21:05:55 ytti oxidized[9820]: 10.10.10.10 status no_connection, retry attempt 2
Jul 11 21:05:55 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 22"
Jul 11 21:05:55 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 23"
Jul 11 21:05:56 ytti oxidized[9820]: 10.10.10.10 status no_connection, retry attempt 3
Jul 11 21:05:56 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 22"
Jul 11 21:05:56 ytti oxidized[9820]: 10.10.10.10 raised Errno::ENETUNREACH with msg "Network is unreachable - connect(2) for "10.10.10.10" port 23"
Jul 11 21:05:57 ytti oxidized[9820]: 10.10.10.10 status no_connection, retries exhausted, giving up
|
|
Closes #23
|
|
Closes #20
[ytti@ytti.fi ~/tmp/oxidized]% oxidized
Error loading config: (<unknown>): mapping values are not s context at line 15 column 7
[ytti@ytti.fi ~/tmp/oxidized]%
|
|
if ~/.config/oxidized/model/ios.rb exists it is used, iinstead of the
system-wide model
|
|
|
|
thanks to @richih
|
|
|
|
How this works in ruby2.0 normally? What component has loaded this
implicitly?
Thanks to @RichiH for spotting.
|
|
README.md: Require ruby-dev on Debian
|
