openstack
/
senlin
Code Issues Proposed changes
senlin/TODO.rst

2.9 KiB
Raw Blame History

Senlin TODO Item List

This document records all workitems the team want to finish in a short-term (usually a development cycle which lasts 6 month). All jobs listed here are NOT in working progress which means developers can pick up any workitem they are interested in if they do have enough time to work on it. Developer should file a BluePrint in the launchpad to give a detailed description about their plan after deciding to work on a specific item. A patch should be proposed as well to remove related workitem from the TODO list after the BP gets approval.

HIGH PRIORITY

API

  • Find and fill gaps with API-WG besides the one we already identified.
  • Validate API request for unexpected attributes. Such attributes should result in a 400 error. [https://review.openstack.org/#/c/260292]

ENGINE

  • Scaling Improvments [https://etherpad.openstack.org/p/newton-senlin-ha]
    • Ensure all scaling operations are based on 'desired_capacity'.
    • Ensure 'desired_capacity' will be controlled by users, not senlin engine or policies.
    • Always do health check before any scaling actions.

POLICY

  • Investigate the impact of node-create and node-delete on certain policies.

MIDDLE PRIORITY

API

PROFILE

  • Add support to template_url for heat stack profile. If template and template_url are both specified, use template. Need to refer to heat api test for testing heat profile.

POLICY

  • Provide support for watching all objects we created on behalf of users, like loadbalancer which is created when attaching lb policy.
  • Leverage other monitoring service for object health status monitoring.

DB

  • Add db purge (senlin-manage) for deleting events and actions because they accumulate very fast.

LOW PRIORITY

ENGINE

  • Allow actions to be paused and resumed. This is important for some background actions such as health checking.
  • Add support to replace a cluster node with another node.
  • Provide support to oslo.notification and allow nodes to receive and react to those notifications accordingly: Autoscaling Notifications

POLICY

  • Batching policy: create batchs for node creation/deletion/update.

PROFILE

  • Support disk property update for os.nova.server profile

Receiver

  • Zaqar queue based receiver.

DOC

  • Provide a sample conf file for customizing senlin options.