stack list filter keys inconsistent with stack views

[Qiming Teng]

For some reasons, we do a stack object format before returning the result to users. This format is causing some confusion from API users' perspective. For example, a user will see the following map when doing stack_show or stack_list:

  {
   'stack': {
    'stack_name': ...,
    'stack_action': ...,
    'stack_status': ...,
    'stack_status_reason': ...,
    'stack_owner': ...,
    'parent': ...,
  }

When a user sees this, they may believe that a stack has a 'stack_name' property that can be used as filter key, but that is not true. Instead, when they do filtering in stack list, they need to specify the following keys respectively:

  name -> stack_name
  action -> stack_action
  status -> stack_status
  username -> stack_owner
  owner_id -> parent

 This is causing some problems in projects that invoke Heat apis.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/188411

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/188411
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=b910a27d5ff0b924f3fba3933e6f90621f3c1bf3
Submitter: Jenkins
Branch: master

commit b910a27d5ff0b924f3fba3933e6f90621f3c1bf3
Author: tengqm <email address hidden>
Date: Thu Jun 4 10:09:28 2015 -0400

    Fix filter name inconsistency in stack_list

    As described in the bug report, filter names used in stack_list API are
    not consistent with what users see when creating or retrieving stacks.
    We cannot simply change the exposed filter key names because that will
    break existing users.

    This patch adds a translation logic from STACK_KEYS like 'stack_name' to
    its corresponding db column name, i.e. 'name'. The intent is to provide
    compatibility with existing use cases while enforcing API consistency
    regarding the "properties" a user sees from the API.

    At engine API layer, we also try a simple parsing of the 'status' key,
    which may be of simple form 'FAILED' or complex form 'CREATE_COMPLETE'.

    Change-Id: Ia6fe4345ca9feaf20c3bd020ff454e5d701a458e
    Closes-Bug: 1461838