Enforce rpm name format for plugins in fpb

[Vyacheslav Struk]

How to reproduce:

install fpb 38db815(master)
go to plugin dir, execute "fpb --build ."

fpb generates rpm named: "contrail-1.0-1.0.0-0.noarch.rpm"

Proposed solution:

Fix spec template:
Use ${name}-${version} format, i.e. contrail-1.0.0-0.noarch.rpm

[Matthew Mosesohn (raytrac3r)]

Just some feedback about plugin package naming.
I would love to see a common convention, so that it is very obvious to tell that this package is a Fuel plugin and what format it is written in. Let's look at yum plugins for example.
They follow the naming of yum-plugin-$pluginname-$version-$release
We should try to name Fuel plugins this way:
fuel-plugin-$pluginfmtver.$pluginver-$release.noarch.rpm
Let's just agree that the major version of the package should correspond with the plugin format. It's the most important value here in any case. The release should always start at 1, but it could include a git hash.
The plugins themselves should do some check to ensure the nailgun API version meets its requirements before they can be fully registered into Fuel.

With regards to this, I think we should agree that an initial release version of the Fuel Contrail plugin should be the following:
fuel-plugin-contrail-1.1.0-1.noarch.rpm

[Evgeniy L (rustyrobot)]

Matthew, Vyacheslav, RPM was named this way because 1.0 is a part of rpm name, "contrail-1.0", and after that goes the version "contrail-1.0-1.0.0", with such approach "contrail-1.0" and "contrail-1.1" plugins can be installed at the same time and can be used for different environments.

Implementation of "fuel-plugin" prefix will require to fix fpb and fuel client.

Release version is easy to fix replace 0 with 1
https://github.com/stackforge/fuel-plugins/blob/master/fuel_plugin_builder/fuel_plugin_builder/templates/build/plugin_rpm.spec.mako#L19

[Evgeniy L (rustyrobot)]

Extracted part release in separate ticket https://bugs.launchpad.net/fuel/+bug/1444977

[Vladimir Sharshov (vsharshov)]

Does not affect deployment. Moving to 8.0

[Alexander Kislitsky (akislitsky)]

We passed SCF in 8.0. Moving the bug to 9.0.

[Dmitry Pyzhov (dpyzhov)]

It's a feature and we passed SCF for 9.0. Moving to 10.0.