Wrong ranges for plugins priorities in the doc

[Evgeniy L]

Current ranges [1][2] are

0 - 999 hardware configuration, for example drivers configuration
1000 - 1999 reserved for future uses
2000 - 2999 disks partitioning and volumes configuration
3000 - 3999 reserved for future uses
4000 - 4999 network configuration
6000 - 6999 reserved for future uses
5000 - 5999 software deployment
7000 - 7999 reserved for future uses
8000 - 8999 monitoring services deployment

We have 6000 which goes before 5000, the correct order should be:

0 - 999 hardware configuration, for example drivers configuration
1000 - 1999 reserved for future uses
2000 - 2999 disks partitioning and volumes configuration
3000 - 3999 reserved for future uses
4000 - 4999 network configuration
5000 - 5999 reserved for future uses
6000 - 6999 software deployment
7000 - 7999 reserved for future uses
8000 - 8999 monitoring services deployment

[1] https://wiki.openstack.org/wiki/Fuel/Plugins#Plugins_deployment_order
[2] https://review.openstack.org/#/c/164779/6/specs/6.1/plugins-deployment-order.rst

[OpenStack Infra (hudson-openstack)]

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

[Irina Povolotskaya (ipovolotskaya)]

Here is the fix https://wiki.openstack.org/wiki/Fuel/Plugins#Plugins_deployment_order

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/174319
Committed: https://git.openstack.org/cgit/stackforge/fuel-specs/commit/?id=a56b75f28938fb35b8790b3b90ad826c20c3e6e6
Submitter: Jenkins
Branch: master

commit a56b75f28938fb35b8790b3b90ad826c20c3e6e6
Author: Irina Povolotskaya <email address hidden>
Date: Thu Apr 16 14:55:59 2015 +0300

    Fix ranges in the plugins deployment order spec

    This commit brings ranges for Fuel plugins
    into the desired order, so that 5000 would
    go right after 4999 (not after 6999).

    Change-Id: I9e9fea36b74720761e9b5dacf81102d16f91ada7
    Closes-Bug: 1444942