://stackalytics.com/report/driverlog?project_id=openstack/fuel
[2]
https://wiki.openstack.org/wiki/DriverLog#How_To:_Add_a_new_Fuel_Plugin_to_DriverLog
--
Best regards,
Irina Povolotskaya
__
OpenStack Development Mailing List
://wiki.openstack.org/wiki/Fuel/Plugins
[3]
http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide/additional-information.html
--
Best regards,
Irina Povolotskaya
__
OpenStack Development Mailing List (not for usage
know where to submit issues if any.
thanks.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-April/092712.html
[2]https://wiki.openstack.org/wiki/Fuel/Plugins#Launchpad_project
[3] https://wiki.openstack.org/wiki/Fuel/Plugins/Launchpad_projects_list
--
Best regards,
Irina Povolotskaya
://launchpad.net/lma-toolchain
[3] https://launchpad.net/fuel-plugin-nsxv
[4] https://launchpad.net/fuel
[5] https://wiki.openstack.org/wiki/Fuel/Plugins
--
Best regards,
Irina Povolotskaya
__
OpenStack Development Mailing List
Hi Dmitry,
I wanted to follow-up on the 'let's have some rules' email.
For now, there are many requests on repo creation for Fuel Plugins and we
need to think
on the best way to proceed here.
In the long-term perspective;
the theme of the rules for Fuel Plugins and transition manner between
Hi all,
Svetlana is doing great work and I hope
our Fuel documentation will become even better;
+1 from me
--
Best regards,
Irina
*Business Analyst*
*unloc...@mirantis.com *
__
OpenStack
Hi John,
To put a tag, you need to:
- be a member of release group (that has Push Signed Tag rights) - and you
are https://review.openstack.org/#/admin/groups/956,members
- use gpg key using console gnupg - you might have missed this.
--
Best regards,
Irina
Fuelers,
I'd like to nominate Olga Gusarenko for the fuel-docs-core.
She has been doing great work and made a great contribution
into Fuel documentation:
http://stackalytics.com/?user_id=ogusarenko=all_type=all=fuel-docs
It's high time to grant her core reviewer's rights in fuel-docs.
Core
Hi to all,
Please be informed that the Fuel Plugin SDK now has a set of useful
instructions that cover the following issues:
- how to create a new project for Fuel Plugins in /openstack namespace [1].
- how to add your plugin to DriverLog [2]
- how to form documentation for your plugin [3].
If
Fuelers,
I'd like to nominate Evgeniy Konstantinov for the fuel-docs-core team.
He has contributed thousands of lines of documentation to Fuel over
the past several months, and has been a diligent reviewer:
http://stackalytics.com/?user_id=evkonstantinov=all_type=all=fuel-docs
I believe it's
Hi to everyone,
I've seen a message from Jim on migrating in the stackforge namespace.
I have a question about Fuel Plugins:
- Fuel is not the part of upstream; neither are Fuel Plugins (and each
of them has a separate project under Stackforge).
- Nevertheless, the number of Fuel
Hi,
If you are now developing a plugin for Fuel, please feel free to use
DriverLog
to add an entry for your plugin.
You can find details instructions on how to do that here [1].
If something seems unclear to you, feel free to request more details.
Thanks.
[1]
Hi Samuel,
it looks like no problem.
Nevertheless, we have operations category as well [1] - to be added soon.
-TLS plugin related to security. For example everything related to tls
access to the dashboard/vnc and apis
-Plugin to deploy freezer with fuel in order to achieve abckup and restore
Hi Samuel,
it looks like no problem.
-TLS plugin related to security. For example everything related to tls
access to the dashboard/vnc and apis
-Plugin to deploy freezer with fuel in order to achieve abckup and restore
(on going)
-plugin to setup availaiblity zones (on going)
The actual
Hi to all,
Swann Croiset reported a bug on Hiera nodes [1].
This issue affects several plugins so far.
In 6.1, there is no workaround.
In 7.0, there should be a new structure for networks_metadata;
this means, there will be ready-to-go puppet functions to get the data.
Unfortunately, it
Fuelers,
I'd like to nominate Denys Klepikov for the fuel-docs-core team.
He has contributed a lot into documentation to Fuel over the past several
months with being diligent reviewer.
He has been working hard to improve UX, clarifying complex aspects and
providing detailed feedback for the
Samuel,
Currently, there is a spec on introducing a new role through a plugin [1] -
the feature is targeted at 7.0.
Feel free to comment on it and ask questions right in the commit.
[1] https://review.openstack.org/#/c/185267/
--
Best regards,
Irina
Partner Management Business Analyst
skype:
Hi to all,
Please, be informed that the plugin certification schedule is shifted due
to the Fuel GA date [1].
*This means the following:*
if you've sent your plugin targeted at 6.1 for certification, it will be
tested using GA, but not Release Candidates.
If you have any further questions
Hi to all,
Please, be informed about the following:
you can now use Gerrit workflow for creating your Plugin Guides.
Previously, you had to send a pdf that was less flexible way of writing and
reviewing.
You can find detailed instructions and recommendations at Fuel Plugins wiki
page [1].
Technical Writer
skype: ira_live
Trello board:
https://trello.com/b/3nxd5wFq/irina-povolotskaya-tasks-tracking-board
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
Samuel,
Could you please report a bug in Fuel project [1] and provide more details?
Thanks a lot!
[1] https://bugs.launchpad.net/fuel/+filebug
--
Best regards,
Irina
PI Team Technical Writer
skype: ira_live
Trello board:
https://trello.com/b/3nxd5wFq/irina-povolotskaya-tasks-tracking-board
/irina-povolotskaya-tasks-tracking-board
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
://wiki.openstack.org/wiki/Fuel/Plugins#Brand_new_features
--
Best regards,
Irina
PI Team Technical Writer
skype: ira_live
Trello board:
https://trello.com/b/3nxd5wFq/irina-povolotskaya-tasks-tracking-board
__
OpenStack Development
Hi to all,
Please be informed that Fuel Plugins wiki page [1] now contains
useful instructions on how to get plugin restrictions diplayed
in the Fuel web UI.
That means, you can improve the user experience for your plugin.
Feel free to have a look and ask questions if any.
Thanks a lot!
[1]
Hi to all,
please be informed that CI [1] section of the Fuel Plugins wiki page was
updated with the following issues:
- Prerequisite steps for setting devtesting environment [2]
- CI server configuration steps [3]
Feel free to review, ask questions and comment.
Thanks!
---
Hi to all,
Please, use* [Fuel][Plugins]* tag for questions/announcements on Fuel
Plugins.
Applying [Fuel] with asking about Fuel Plugins leads to mixing up Fuel and
plugins-related issues.
Let's split these large topics for better communication and for quicker
replies.
Note, that this
Emma,
the plugin itself is licensed under Apache 2.0.
As to the ownership issue: developer stays the owner.
There is no contributor license agreement to sign yet.
On Wed, May 6, 2015 at 3:00 PM, openstack-dev-requ...@lists.openstack.org
wrote:
Send OpenStack-dev mailing list submissions to
Hi to all,
I'd like to remind you about Driverlog, nice tool that joins our efforts in
keeping information on OpenStack drivers up-to-date.
You can get the latest information on drivers in 2 different sources:
Driverlog itself [1] and OpenStack marketplace [2].
There is a number of brand new
Hi to everyone,
Please, be informed that Fuel Plugin Guide has been removed
and split into more specific sections at the wiki page [1].
The Plugins wiki page covers the following issues:
- basic development issues (Fuel Plugin Builder, package types)
- detailed plugin files description
- repo
Hi to everyone,
I'd like to inform you that a new wiki page was created for Fuel Plugins -
https://wiki.openstack.org/wiki/Fuel/Plugins.
Beginning with 6.0 release, Fuel supports Pluggable Architecture; that
means, you can download and install plugins for Fuel or even develop your
own.
The wiki
Hi Fuelers and Mike,
I'd like to provide some ideas/comments for the issues Mike has put into
discussion.
Yesterday we had a nice discussion for plugins SDK.
According to this discussion, we should create an internal document for
plugins certification ASAP (I mean, steps to perform on the
31 matches
Mail list logo