Enable Manage-Service feature in scale out deployment

Registered by Kanagaraj Manickam on 2015-03-27

In a scale out environment, cloud provider start to run many heat-engines to server the load of huge requests at the given point in time. Once many engines are started to run, current service API does not have following functionalities, Which I would expect for listing the services.
 - Pagination :
  ○ Start_index: (service_id)
  ○ Number_of_records: (default=20)
  ○ Always sort by created_at filed during the list.
 - Search by hostname
 - Search by up/down status

Add pid into Service
---------------------------
When multiple heat-engines are running, it is difficult to find out the processed for a given heat-engine. This is required during trouble shooting the issues. So as a could admin, I would like to get the process id (pid) for the given service

Blueprint information

Status:
Not started
Approver:
Angus Salkeld
Priority:
Undefined
Drafter:
Kanagaraj Manickam
Direction:
Needs approval
Assignee:
None
Definition:
Pending Approval
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/heat-manage-service-list-scale-out,n,z

Addressed by: https://review.openstack.org/168657
    Enhance Manage Service searching capability

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.