title: OpenMDAO 1.x: recording desvars, constraints and objective
body: <p>How can you get information about which variables are design vars, objectives or constraints from the information saved by recorders? It would be useful to print this information to a file to track optimization progress during a run. It looks like the <code>RecordingManager.record_iteration</code> doesn't really allow for this at the moment, since you only pass the <code>root</code> system and a metadata dict meant for optimizer settings.</p>
  
  <p>Would it be possible to add an argument to the <code>RecordingManager.record_iteration</code> called e.g. <code>optproblem</code>, which is a dictionary with dictionaries with desvars, constraints and objective?</p>
  
  <p>A simple OptimizationRecorder could then dump out column formatted files with the quantities for easy plotting during the optimisation.</p>