Create Trove plugin for Fuel

Bug #1403384 reported by sbartel
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
sbartel

Bug Description

Starting from OpenStack juno release Trove is no more in incubation.
However, Mirantis 6.0 repos do not include trove packages.

Customers, using ubuntu, can not obtain these packages elsewhere as canonical does not provide support for juno for 12.04.
Please add python-trove, trove-common,trove-api and trove-taskmanager 6.0 and to all future release repos.

Changed in fuel:
milestone: none → 6.1
assignee: nobody → Fuel OSCI Team (fuel-osci)
status: New → Confirmed
Roman Vyalov (r0mikiam)
Changed in fuel:
importance: Undecided → Medium
Revision history for this message
Roman Alekseenkov (ralekseenkov) wrote :

We have introduced pluggable architecture in 6.0, which allows to add packages and make configuration without making changes to Fuel master node itself. Trove will not be supported out of Fuel core, so it needs to be added as a plugin. Will change title of the bug accordingly.

summary: - Add trove packages to Mirantis repos
+ Create Trove plugin
summary: - Create Trove plugin
+ Create Trove plugin for Fuel
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Roman, I think this is not exactly what is needed. Initial title was about creating a package and placing in to the official repository along with other openstack packages.

If we do not want to place the package along with other packages, I believe we should be able to create package still. Then, sbartel can use Fuel plugin builder to bundle this package into the plugin. I'll get Evgeny Li to comment on this, but it should be possible to create a plugin with just a repository extension - basically second packages repo, which will be used during deployment.
Then, whether manually, or through the plugin mechanism, this package can be installed on slave nodes.

Revision history for this message
Evgeniy L (rustyrobot) wrote :

Yes, you can build your own packages for ubuntu/centos and add this packages into the plugin, the only thing which you should do before the deployment is to enable the plugin on Fuel UI Settings tab, and the repository will be added on the target nodes automatically.
Take a look at the examples [1], [2] and also take a loot at our documentation [3].

[1] https://github.com/Mirantis/fuel-plugins/
[2] https://github.com/stackforge/fuel-plugins
[3] https://review.openstack.org/#/c/138013/19/pages/plugin-dev/020-fuel-plugin-dev.rst - the document is in progress, but ready to use

Revision history for this message
Frank Weyns (fweyns) wrote : Re: [Bug 1403384] Re: Create Trove plugin for Fuel

Do we have Trove builds for Ubuntu 12.04 working on Mos 6.0
The issue here is that Mos 6.0 (JUNO) is still on 12.04. (and not on 14.04)

Regards,
Frank Weyns
+31 6 4191 5353
(mobile email)

Evgeniy L <email address hidden> schreef op 23 december 2014 08:56:35 GMT+00:00:
>Yes, you can build your own packages for ubuntu/centos and add this
>packages into the plugin, the only thing which you should do before the
>deployment is to enable the plugin on Fuel UI Settings tab, and the
>repository will be added on the target nodes automatically.
>Take a look at the examples [1], [2] and also take a loot at our
>documentation [3].
>
>[1] https://github.com/Mirantis/fuel-plugins/
>[2] https://github.com/stackforge/fuel-plugins
>[3]
>https://review.openstack.org/#/c/138013/19/pages/plugin-dev/020-fuel-plugin-dev.rst
>- the document is in progress, but ready to use
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1403384
>
>Title:
> Create Trove plugin for Fuel
>
>Status in Fuel: OpenStack installer that works:
> Confirmed
>
>Bug description:
> Starting from OpenStack juno release Trove is no more in incubation.
> However, Mirantis 6.0 repos do not include trove packages.
>
>Customers, using ubuntu, can not obtain these packages elsewhere as
>canonical does not provide support for juno for 12.04.
>Please add python-trove, trove-common,trove-api and trove-taskmanager
>6.0 and to all future release repos.
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/fuel/+bug/1403384/+subscriptions

Roman Vyalov (r0mikiam)
Changed in fuel:
assignee: Fuel OSCI Team (fuel-osci) → sbartel (samuel-bartel)
Revision history for this message
Denis M. (dmakogon) wrote :

I can be Trove expert once there would be something to review.

Revision history for this message
Roman Vyalov (r0mikiam) wrote :

reassign to Fuel team

Changed in fuel:
assignee: sbartel (samuel-bartel) → Fuel for Openstack (fuel)
Changed in fuel:
assignee: Fuel for Openstack (fuel) → MOS Linux (mos-linux)
Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

mos-linux does not package openstack, python or ruby.

Changed in fuel:
assignee: MOS Linux (mos-linux) → Fuel for Openstack (fuel)
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Guys,
I don't understand why this bug is flowing between assignees. If we need to, let's discuss it in #fuel-dev (ping #mihgen, #evgeniyl), or in openstack-dev ML (please use [Fuel] in subject).

It's pretty much clear to me: we do not want Trove package and deployment scripts to be part of Fuel core, and instead the idea is to use Fuel plugable architecture, and create a plugin which would install Trove. See comment #3 here from evgeniyl.
Plugins dev guide was merged, see here for instance:
http://docs.mirantis.com/openstack/fuel/fuel-6.0/plugin-dev.html#how-can-i-download-the-packages-which-are-required-for-a-plug-in

Changed in fuel:
assignee: Fuel for Openstack (fuel) → sbartel (samuel-bartel)
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Shouldn't we address the plugins by blueprints instead of bugs? The process of blueprint design is too complex to be covered by the bug comments only

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :
Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
sbartel (samuel-bartel) wrote :

adress this point by a bluprint make sens as it is for support of a new feature.
The problem here is not the availability of a plugin. We are ok with my team to write one and add it in the plugins repos.

my initial question/remark with this bug was for the availability of trove packages (rpm+deb) from mirantis.
I understand it is not a fuel core feature. But lbaas was not one neither and the package was available in mirantis/fw repo
actually we can't find any trove repo (except the client one) in any fuel repo (neither the fw or the plugin ones)
So we just wanted to know if it can be add and provide in mirantis repo or if we should make package on our side for the plugin (as for ubuntu for example canonical package are not compatible with mirantis distro)

Revision history for this message
Denis M. (dmakogon) wrote :

Agreed with Mike, it was decided to ship Trove as one of plugins.

Agreed with Bogdan, blueprint fits there in its best.

Sam, Ubuntu Trusty Tahr with Juno release does ship trove packages (thanks to Thomas Giorand). So, taking into accoun Trove's nature, it wouldn't be so complicated to build couple additional packages for Trove (in case if we'd use 6.x release that comes with 12.04 LTS).
I can help to assignee with providing up-to-date information about Trove and the best practices of its deployment strategy.

Revision history for this message
Mike Scherbakov (mihgen) wrote :

Samuel,
current position is the following:
a) Mirantis built LBaaS and distributes this as certified plugin. Going forward, Mirantis plans to maintain this plugin and related packages. That's why it's in official repo.
b) Trove is not currently considered by Mirantis to be maintained and supported. You can build your own packages and plugin, send it to Mirantis or to https://www.fuel-infra.org/plugins/catalog.html to be published as uncertified plugin.
c) You can build your package & plugin, and send it to Mirantis for certification. Mirantis then will run set of certification activities (including testing), and publish plugin to the certified section
d) There can be commercial agreements with Mirantis which are above what was discussed. Please contact Frank for details.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.