Chef Ideas

We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.

We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.

Thanks for collaborating with us!

Ohai record creation date of Chef Infra Node

It would be useful to record the creation date of chef infra client nodes. We already record the ohai_time, when the last chef client run occurred.

Guest
Aug 27 2019
Planned

Chef Infrastructure Management

Comments (4)
Votes (12)

Attach files

Enter a subject
richard m commented

30 Apr, 2020 04:41pm

you could create a custom ohai-plugin that looks at the create time of the client.pem file and set that value as the create time of the node. Its not perfect but should suffice

×
Attachments Open full size
Sean Horn commented

17 Apr, 2020 07:19pm

Yes, Steven's comment covers much of it. Customers also want to be able to find out when nodes were created in A2, so that they can filter on old nodes in the fleet that need replacing. Maybe they have a schedule at which they replace AMIs, and the creation_time can help them catch nodes that were missed in the last AMI refresh

×
Attachments Open full size
Steven ONeill commented

26 Feb, 2020 02:56am

I think it would be awesome to be able to use this as switching logic. Rolling new features, stop running certain things on old nodes, etc...

# pseudocode
only_if { node['create_time'] > '20180701' }

×
Attachments Open full size
Joshua O'Brien commented

17 Oct, 2019 07:00pm

Can you expand a bit on your use case here?

×
Attachments Open full size