[chef] Re: Re: Re: Re: Re: Reporting: list of nodes with cookbook versions

[Mark Mzyk < >]

One minor correction: push jobs is open source and free for use for as many nodes as you'd like, in the same way the Chef server is, even though it is currently installed as an add on. It's the one current add on that isn't a premium feature.

- Mark Mzyk

" type="cite">

" photoname="Ranjib Dey" src="jpgLdXNhoUy0Q.jpg" name="compose-unknown-contact.jpg" height="25px" width="25px">

" style="color:#737F92 !important;padding-right:6px;font-weight:bold;text-decoration:none !important;">Ranjib Dey

February 6, 2015 at 6:54 PM

i dont think chef server should do that, but thats mostly because i dont need it. To me chef-server as an artifact store. And metadata service , a decent service discovery mechanism if you can withstand couple of minutes delay (and in most cases I can).

Things like resource reporting, audits, push jobs etc are already provided as add on (they are proprietary features though). If theres enough people who needs it, we can get it done via the RFC process, like any other new features

cheers

ranjib

" photoname="Roman Naumenko" src="jpgq04Ic7wsSS.jpg" name="postbox-contact.jpg" height="25px" width="25px">

" style="color:#737F92 !important;padding-right:6px;font-weight:bold;text-decoration:none !important;">Roman Naumenko

February 6, 2015 at 6:45 PM

To Tensibai point: isn't it what chef server supposed to do?

Ranjib, that's probably the way to do it, but again - why that's missing in core functionality? Also, it's version reports are useful only in relation to other information: health status, last run time etc. Is all this information goes to tags as well?

--Roman

Ranjib Dey wrote on 04-02-15 3:29: