Update README.rst
diff --git a/README.rst b/README.rst
index cb25f5f..5cb7ba3 100644
--- a/README.rst
+++ b/README.rst
@@ -1,14 +1,14 @@
-==========
-Ceilometer
-==========
+==================
+Ceilometer Formula
+==================
The ceilometer project aims to deliver a unique point of contact for billing
systems to acquire all of the measurements they need to establish customer
billing, across all current OpenStack core components with work underway to
support future OpenStack components.
-Sample pillars
+Sample Pillars
==============
Ceilometer API/controller node
@@ -103,8 +103,8 @@
virtual_host: '/openstack'
rabbit_ha_queues: true
-Read more
-=========
+More Information
+================
* https://wiki.openstack.org/wiki/Ceilometer
* http://docs.openstack.org/developer/ceilometer/install/manual.html
@@ -113,59 +113,6 @@
* https://github.com/spilgames/ceilometer_graphite_publisher
* http://engineering.spilgames.com/using-ceilometer-graphite/
-Things to improve/consider
-==========================
-
-* Graphite publisher http://engineering.spilgames.com/using-ceilometer-graphite/
-* Juno additions - Split Events/Meters and Alarms databases, Polling angets are
-HA now, active/Activr Workload partitioning to central agents
-* Kilo additions - Splint Events - Meters - Agents, notification agents are HA
-now (everything is HA now), events - elastic search
-* User notifier publisher vs rpc publisher (Juno+)
-* Enable jittering (rendom delay) to polling. (Kilo+)
-* Collect what you need - pipeline.yaml, tweak polling interval (Icehouse+)
-* add more agents as load inceases (Juno+)
-* Avoid open-ended queries - query on a time range
-* Install api behind mod_wsgi, tweak wsgi daemon - threads and processes
-* Set TTL - expire data to minimise database size
-* Run Mongodb on separate node - use sharding and replica-sets
-
-Deployment scenarios
---------------------
-
-* Lambda design - use short term and long term databases in the same time
-* Data segragation - separatem
-* JSON files - Apache spark
-* Fraud detection - proprietary alarming system
-* Custom consumers - kafka - Apache Storm (kilo+)
-* Debugging - Collecttions - Elastic serach - Kibana
-* Noisy services - Multiple notification buses
-
-Documentation and Bugs
-============================
-
-To learn how to deploy OpenStack Salt, consult the documentation available
-online at:
-
- https://wiki.openstack.org/wiki/OpenStackSalt
-
-In the unfortunate event that bugs are discovered, they should be reported to
-the appropriate bug tracker. If you obtained the software from a 3rd party
-operating system vendor, it is often wise to use their own bug tracker for
-reporting problems. In all other cases use the master OpenStack bug tracker,
-available at:
-
- http://bugs.launchpad.net/openstack-salt
-
-Developers wishing to work on the OpenStack Salt project should always base
-their work on the latest formulas code, available from the master GIT
-repository at:
-
- https://git.openstack.org/cgit/openstack/salt-formula-ceilometer
-
-Developers should also join the discussion on the IRC list, at:
-
- https://wiki.openstack.org/wiki/Meetings/openstack-salt
Documentation and Bugs
======================