oxidized

Oxidized is a network device configuration backup tool. It's a RANCID replacement!

Runssource: GitHubRubyApache-2.0commit 2cb5053566df

Ruby, Apache-2.0 licensed. The project labels itself: backup, network, nms and rancid.

oxidized runs. An Argusic agent installed it in 18 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Oxidized version 0.37.0 is fully installed in /work/repo with all dependencies; 412 tests pass with 0 failures, rubocop clean on 304 files, and the binary reports its version and help text correctly.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
2
last tested
stars
3,667
forks
1,067
open issues
50
watchers
119
size
4 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing oxidized, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Ruby not installed in container - had to compile from source10 minutes
  • charlock_holmes native extension failed due to missing ICU headers (libicu-dev). CXXFLAGS from pkg-config not passed to C++ compiler5 minutes
  • bundle config --without development persisted blocking dev gems1 minute
Install time
18 minutes
Cold machine to finish
18 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
bundle exec rake test exited 0: 412 runs, 1541 assertions, 0 failures, 0 errors, 0 skips. bundle exec bin/oxidized --version returned 0.37.0. bundle exec rubocop: 304 files inspected, 0 offenses detected.
Model tokens used
482,869
Exact commit tested
2cb5053566df
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc 'export PATH=$HOME/.local/bin:$PATH
export LD_LIBRARY_PATH=$HOME/.local/lib
cd /work/repo
bundle exec rake test 2>&1 | head -5' in /work/repo
 succeeded in 7839ms:
Run options: --seed 1393
# Running:
...................................................................................................…
All confirmed. Let me prepare the final report.
tokens used
482,869
All confirmed. Let me prepare the final report.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 18 minutes to install, slower than the median of the 47 comparable projects Argusic has measured.

Of the 48 backup projects Argusic has installed and timed, oxidized was the 43rd fastest to reach a running state, and 32 of 48 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.14
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

backupnetworknmsrancid

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/oxidized.svg)](https://argusic.com/subject/oxidized)

Questions

Does oxidized run?
Yes. oxidized runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test oxidized?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2cb5053566df. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test oxidized?
The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does oxidized take to install?
18 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does oxidized need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing oxidized?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does oxidized compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, oxidized was the 43rd fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for oxidized?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion