Couchdb node document revision timestamp equal to ohai_time?


#1

Hi guys!

I’m adding a new script to chef_knives that prints out the document
revisions of a node (i.e. previous node states). Something along this
lines:

$ chef_node_revisions -n xen10

[ xen10.example.com ]

REVISION DATE
2103-3352627820 20095110/02/09-13:51:53
2100-3611993058 20092110/02/09-13:21:32
1992-1504167919 20093910/01/09-18:39:35
1989-2703343007 20090910/01/09-18:09:13
1986-2968622156 20093810/01/09-17:38:50
1983-664772315 20091710/01/09-17:17:34
1980-2756857044 20094710/01/09-16:47:07

The first column is the revision number added by couchdb, the second
is the ohai_time from that document.

Then you can:

$ chef_node_revisions -n xen10 -r 1833-2873490029

and print out all the attributes from the node at that time.

The question is:

Is that right? I mean, does the ohai_time matches the document
revision timestamp? (an approx at least)

Thanks!

Cheers,
Sergio.


#2

On Fri, Oct 2, 2009 at 5:06 AM, Sergio Rubio rubiojr.ml@gmail.com wrote:

REVISION DATE
2103-3352627820 20095110/02/09-13:51:53
2100-3611993058 20092110/02/09-13:21:32
1992-1504167919 20093910/01/09-18:39:35
1989-2703343007 20090910/01/09-18:09:13
1986-2968622156 20093810/01/09-17:38:50
1983-664772315 20091710/01/09-17:17:34
1980-2756857044 20094710/01/09-16:47:07

The first column is the revision number added by couchdb, the second
is the ohai_time from that document.

Then you can:

$ chef_node_revisions -n xen10 -r 1833-2873490029

and print out all the attributes from the node at that time.

The question is:

Is that right? I mean, does the ohai_time matches the document
revision timestamp? (an approx at least)

Yeah, that looks reasonable to me.

Adam


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com