[openstack-dev] [fuel] Nominate Svetlana Karslioglu for fuel-docs core

[Irina Povolotskaya]

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Plugins for Fuel: repo, doc, spec - where?

[Irina Povolotskaya]

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 developers'
side and assignees for the particular tasks).

So, we could also describe there (just what you've mentioned):

   - repo issue: we should definitely mention that
   stackforge/fuel-plugin- is strongly recommended for usage (we have
   some common information in Fuel Plug-in Guide, but an internal document
   should focus on that)
   - docs for plugins: I'm already working on .pdf templates for both
   Plugin Guide (how to install/configure a plugin) and Test Plan/Report
   (we'll just move to the simplest format ever, but note that this is mostly
   related to certification workflow). Nevertheless, some repos already
   contain README.md files with a brief description,
   installation/configuration instructions. For example, see Borgan D plugin's
   [1]. There is no spec, but the concept seems clear on the whole.
   - As to specification: developers should provide it in the Test Plan, so
   it would be okay if they followed one of these two ways:1) took fuel-specs
   template as the basis and simply made a link from their Test Plan/Report to
   the spec 2) post this spec right in the Test Plan/Report.
   - test in the repo: sure, this should be covered.

I believe, I'll mostly be working on this internal document, so feel free
to comment/correct me, if something seems wrong here.

[1] https://github.com/stackforge/fuel-plugins/tree/master/ha_fencing
-- 
--
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Using DriverLog as the Fuel Plugins registry

[Irina Povolotskaya]

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]
https://wiki.openstack.org/wiki/DriverLog#How_To:_Add_a_new_Fuel_Plugin_to_DriverLog

-- 
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Migrating existing projects in the stackforge namespace - question about Fuel Plugins

[Irina Povolotskaya]

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 Plugins grows and developers will
   keep on requesting stackforge project creation.


Question:
I would like to know how you plan to work with these issues in this very
case.
Do you plan to mark those somehow just to show that they are actually
maintainted and not the part of upstream yet?
Do you need any extra confirmation from development teams that their
plugins are being constantly updated and worked on?

Thanks.

-- 
Best regards,

Irina

*Business Analyst*
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Nominate Evgeniy Konstantinov for fuel-docs core

[Irina Povolotskaya]

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&release=all&project_type=all&module=fuel-docs

I believe it's time to grant him core reviewer rights in the fuel-docs
repository.

Core reviewer approval process definition:
https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess

-- 
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] SDK is updated with the latest information

[Irina Povolotskaya]

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 you suppose some issues are still missing, please let me know.

Thanks.


[1] https://wiki.openstack.org/wiki/Fuel/Plugins#How_to_create_a_project

[2]
https://wiki.openstack.org/wiki/Fuel/Plugins#Add_your_plugin_to_DriverLog
[3]
https://wiki.openstack.org/wiki/Fuel/Plugins#Creating_documentation_for_Fuel_Plugins
-- 
Best regards,

Irina

*Business Analyst*
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Nominate Olga Gusarenko for fuel-docs core

[Irina Povolotskaya]

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&release=all&project_type=all&module=fuel-docs

It's high time to grant her core reviewer's rights in fuel-docs.

Core reviewer approval process definition:
https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess

-- 
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [fuel] [plugin] Release tagging - possible problem

[Irina Povolotskaya]

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
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Rules for Fuel Plugins: short-term perspective action plan

[Irina Povolotskaya]

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
stages is more for a discussion on the OpenStack summit - would you agree?

As for the short-term perspective, we will speak about new and already
existing plugins.

For new plugins, there needs to be the following flow from Fuel core team
(on creating a repo):
1) make sure the plugin has several maintainers and is intended for further
maintenance (i.e. is not for the one and only Fuel release).
2) once repo is created,  request adding the plugin entry to DriverLog to
have very specific personas in charge of this plugins' future
3) provide baseline information into README file to let everyone now about
the plugin's functionality and add someone from Fuel core team to review

For already existing plugins:
there needs to be a survey on already existing plugins that aren't updated
any longer; their repos can be moved back into private ones or might be
owned by new maintainers (if those willing to take up this regular task are
present).

Similar exercise was so far done when stackforge NS was becoming obsolete
and the corresponding repo owners were asked to update the wiki page and
add the repo entry into the corresponding list if they were willing to get
their repo be moved to openstack NS (=if they were willing to continue
working on specific project).

If the current plugin maintainers are not willing to work on their plugin
any longer, they should post the corresponding request in openstack-dev ML
and ask if any volunteers are present.

If no volunteers are in place, then the code should live in the private
repo of the current maintainers, with README/DriverLog updated accordingly.

I would appreciate any extra ideas in terms of things to do right now.

Thanks.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

[Irina Povolotskaya]

Hi to everyone,

as you possibly know (at least, those dev. teams working on their Fuel
plugins) we have a fuel-plugins Launchpad project [1] which serves as
all-in-one entry point for filing bugs, related
to plugin-specific problems.

nevertheless, this single project is a bad idea in terms of providing
granularity and visibility for each plugin:
- it's not possible to make up milestones, unique for every plugin that
would coincide with the plugin's version (which is specified in
metadata.yaml file)
- it's not possible to provide every dev. team with exclusive rights on
managing importance, milestones etc.

therefore, I would like to propose the following:
- if you have your own fuel plugin, create a separate LP project for it
e.g.[2] [3]and make up all corresponding groups for managing release cycle
of your plugin
- if you have some issues with fuel plugin framework itself, please
consider filing bugs in fuel project [4] as usual.

I would appreciate getting feedback on this idea.
if it seems fine, then I'll follow-up with adding instructions into our SDK
[5] and the list of already existing LP projects.

thanks.


[1] https://launchpad.net/fuel-plugins
[2] https://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 (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins][SDK] How to create a plugin-specific Launchpad project

[Irina Povolotskaya]

Hi to everyone,

as the follow-up to my previous email [1],I'm providing the URLs to assist
with
plugin-specific LP project setup:

1) guidelines on how to make it happen [2]
2) list of already existing LP projects [3]

if you already have a project, please add it into the list to let everyone
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
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Using Gerrit workflow for Fuel Plugins Guides

[Irina Povolotskaya]

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].

Please, feel free to ask questions and provide feedback.

Thanks!

[1] https://wiki.openstack.org/wiki/Fuel/Plugins#Following_Gerrit_workflow

-- 
Best regards,

Irina

Partner Management Business Analyst
skype: ira_live
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Certification schedule is shifted due to the Fuel GA date

[Irina Povolotskaya]

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 related to certification of the plugins
in 6.1, feel free to contact me.

[1] https://wiki.openstack.org/wiki/Fuel/6.1_Release_Schedule

-- 
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

[Irina Povolotskaya]

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: ira_live
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Scope of 7.0 Fuel Plugin Framework features

[Irina Povolotskaya]

Hi to all,

Please, be informed that the following features
will enter Fuel Plugin Framework in 7.0 Fuel release:

- define a new role through Fuel Plugins [1]
- reserve VIP addresses via Fuel Plugin's metadata [2]

If you plan to develop a plugin for Fuel, take these changes into
consideration.

Thanks.

[1] https://blueprints.launchpad.net/fuel/+spec/role-as-a-plugin
[2] https://blueprints.launchpad.net/fuel/+spec/vip-reservation

-- 
Best regards,

Irina

*Business Analyst*

*Partner Enablement*

*skype: ira_live*
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Nominate Denys Klepikov for fuel-docs core

[Irina Povolotskaya]

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 already existing docs.

His contribution can be easily measured not in code lines written,
but in reviews held and comments posted;
some statistics could easily prove that:

http://stackalytics.com/report/contribution/fuel-docs/30
http://stackalytics.com/report/contribution/fuel-docs/90

I believe it's time to grant him core reviewer rights in the fuel-docs
repository.

Core reviewer approval process definition:
https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess

-- 
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Hiera nodes issue for 6.1 plugins

[Irina Povolotskaya]

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 impacts UX greatly.

Thanks.


[1] https://bugs.launchpad.net/fuel/+bug/1476957

-- 
Best regards,

Irina

*Business Analyst*

*Partner Enablement*

*skype: ira_live*
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][Plugins] additional categories for plugins

[Irina Povolotskaya]

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 categories are :
montiroing
storage
storage-cinder
storage-glance
network
hypervisor

these plugins are not matching to any of those categories.
Shoul we let the category field empty as requested in fuel plugin
documentation or can we consider to add additionnal categories?

Regards
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][Plugins] additional categories for plugins

[Irina Povolotskaya]

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
> (on going)
> -plugin to setup availaiblity zones (on going)


If these plugins could enter Operations category, please
let me know.
Of not, we could consider creating security category or something
similar.
It would also be nice to get links to the plugins's specifications
just to get more details.

Thanks.


[1] https://bugs.launchpad.net/fuel/+bug/1473387

Regards

-- 
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] A new wiki page is created for Fuel Plugins

[Irina Povolotskaya]

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 page covers not only user-side instructions on installation and
usage, but also FAQ.

As I've already mentioned, it also has information for developers who'd
like to create their own plugin for Fuel (like what is Fuel Plugin Builder,
what UI elements are added for the plugin, what files are generated by FPB
etc.)

Note, that the page also contains some tutorials (soon there'll be even
more, so stay tuned).

Please, feel free to read, review or ask questions - you are always welcome!
If you write into openstack-dev mailing list, do not forget to
use [fuel][plugin] prefix.

Thanks!

-- 
Best regards,

Irina
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Fuel Plugin Guide is replaced with the wiki page

[Irina Povolotskaya]

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 creation recommendations
- common CI recommendations
- tutorials about debugging UI and deployment
- FAQ

It is constantly updated and provides the latest information on
how to develop and deliver Fuel Plugins.

Feel free to have a look and ask questions.

Thank you!


[1] https://wiki.openstack.org/wiki/Fuel/Plugins


-- 
Best regards,

Irina

PI Team Technical Writer
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Driverlog] Feel free to add your drivers for Kilo release into Driverlog

[Irina Povolotskaya]

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 drivers in Kilo, so it's high time to get
them published at Driverlog.

I can't help mentioning that Ironic is now also present in Driverlog -
great thanks to Ironic PTL Devananda van der Veen for help.

For instructions on adding a new entry, see the wiki page [3].

Remember, that with adding new drivers, we keep Driverlog updated and open
to OpenStack newbies in comparison to numerous wiki pages that can
sometimes get users confused.

Feel free to add me for code review - always pleased to help.

Thank you.


[1] http://stackalytics.com/driverlog/
[2] https://www.openstack.org/marketplace/drivers/
[3] https://wiki.openstack.org/wiki/DriverLog


-- 
Best regards,

Irina

PI Team Technical Writer
skype: ira_live
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Fuel][Plugin] Contributor license agreement for fuel plugin code?

[Irina Povolotskaya]

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, 
wrote:

> Send OpenStack-dev mailing list submissions to
> openstack-dev@lists.openstack.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> or, via email, send a message with subject or body 'help' to
> openstack-dev-requ...@lists.openstack.org
>
> You can reach the person managing the list at
> openstack-dev-ow...@lists.openstack.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenStack-dev digest..."
>
>
> Today's Topics:
>
>1. Re: [neutron][api] Extensions out, Micro-versions in
>   (Salvatore Orlando)
>2. Re: [PKG-Openstack-devel][horizon][xstatic]
>   XStatic-Angular-Bootstrap in violation of the MIT/Expat license
>   (forwarded from:
>   python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes
>   REJECTED) (Thomas Goirand)
>3. Re: How to turn tempest CLI tests into python-*client in-tree
>   functional tests (Robert Collins)
>4. Re: [TripleO] Core reviewer update proposal (Jan Provaznik)
>5. Re: [Nova][Ironic] Large number of ironic driver bugs in nova
>   (Lucas Alvares Gomes)
>6. Re: [Fuel] Transaction scheme (Alexander Kislitsky)
>7. Re: How to turn tempest CLI tests into python-*client in-tree
>   functional tests (Chris Dent)
>8. Re: [Fuel] Transaction scheme (Lukasz Oles)
>9. Re: How to turn tempest CLI tests into python-*client in-tree
>   functional tests (Sean Dague)
>   10. Re: [all] cross project communication: periodic developer
>   newsletter? (Thierry Carrez)
>   11. Re: [Nova][Ironic] Large number of ironic driver bugs in nova
>   (John Garbutt)
>   12. Re: [Fuel] Transaction scheme (Igor Kalnitsky)
>   13. Re: [all] cross project communication: periodic developer
>   newsletter? (Thierry Carrez)
>   14. Re: [Fuel] Transaction scheme (Alexander Kislitsky)
>   15. Re: [nova] Which error code should we return when OverQuota
>   (Sean Dague)
>   16. [Fuel][Plugin] Contributor license agreement for  fuel plugin
>   code? (Emma Gordon (projectcalico.org))
>   17. Re: [nova] Which error code should we return when OverQuota
>   (Chris Dent)
>   18. [Fuel] LBaaS in version 5.1 (Daniel Comnea)
>   19. Re: [TripleO] Core reviewer update proposal (Dan Prince)
>   20. Re: [Fuel][Plugin] Contributor license agreement for fuel
>   plugin code? (Jeremy Stanley)
>
>
> --
>
> Message: 1
> Date: Wed, 6 May 2015 08:53:37 +0200
> From: Salvatore Orlando 
> To: "OpenStack Development Mailing List (not for usage questions)"
> 
> Subject: Re: [openstack-dev] [neutron][api] Extensions out,
> Micro-versions in
> Message-ID:
>  ipja6+apixgnwr...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks Kevin,
>
> answers inline.
>
> On 6 May 2015 at 00:28, Fox, Kevin M  wrote:
>
> >  so... as an operator looking at #3, If I need to support lbaas, I'm
> > getting pushed to run more and more services, like octavia, plus a
> > neutron-lbaas service, plus neutron? This seems like an operator
> > scalability issue... What benifit does splitting out the advanced
> services
> > into their own services have?
> >
>
> You have a valid point here. In the past I was keen on insisting that
> neutron was supposed to be a management layer only service for most
> networking services.
> However, the consensus seems to move toward a microservices-style
> architecture. It would be interesting to get some feedback regarding the
> additional operational burden of managing a plethora of services, even if
> it is worth noting that when one deploys neutron with its reference
> architecture there are already plenty of moving parts.
>
> Regardless, I need to slaps your hand because this discussion is not really
> pertinent to this thread, which is specifically about having a strategy for
> the Neutron API.
> I would be happy to have a separate thread for defining a strategy for
> neutron services. I'm pretty sure Doug will be more than happy to slap your
> hands too.
>
>
> > Thanks,
> > Kevin
> >  --
> > *From:* Salvatore Orlando [sorla...@nicira.com]
> > *Sent:* Tuesday, May 05, 2015 3:13 PM
> > *To:* OpenStack Development Mailing List
> > *Subject:* [openstack-dev] [neutron][api] Extensions out, Micro-versions
> > in
> >
> >   There have now been a few iterations on the specification for Neutron
> > micro-versioning [1].
> > It seems that no-one in the community opposes introducing versioning. In
> > particular API micro-versioning as implemented by Nova and Ironic seems a
> > decent way to evolve the API incrementally.
> >
> >  What the dev

[openstack-dev] [Fuel][Plugins] Please, stick to [Fuel][Plugins] tag for plugins

[Irina Povolotskaya]

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 recommendation is present in Fuel Plugins wiki page [1].

Thanks!

[1] https://wiki.openstack.org/wiki/Fuel/Plugins#Channels_of_communication

-- 
Best regards,

Irina

PI Team Technical Writer
skype: ira_live
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] How to display plugin restrictions to users

[Irina Povolotskaya]

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]
https://wiki.openstack.org/wiki/Fuel/Plugins#How_to_display_plugin_restrictions_to_users

-- 
Best regards,

Irina

PI Team Technical Writer
skype: ira_live
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Instructions on CI were updated

[Irina Povolotskaya]

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 dev&testing environment [2]
   - CI server configuration steps [3]

Feel free to review, ask questions and comment.

Thanks!
---
[1] https://wiki.openstack.org/wiki/Fuel/Plugins#CI
[2]
https://wiki.openstack.org/wiki/Fuel/Plugins#Steps_to_prepare_development_.26_testing_environments_.28mandatory.29
[3]
https://wiki.openstack.org/wiki/Fuel/Plugins#Steps_to_configure_CI_server_.28optional.29

-- 
Best regards,

Irina

PI Team Technical Writer
skype: ira_live
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] A new 'monitoring' value is now introduced for groups in metadata.yaml

[Irina Povolotskaya]

Hi to all,

Previously, only limited number of values could be added to 'groups'
parameter
in metadata.yaml file of the plugin. These are:

- network
- storage
- storage:: cinder
- storage:: glance
- hypervisor.

Now you can also add 'monitoring' if your plugin has the corresponding
functionality.
This means, you plugin will fall into the required category of the Plugins
Catalog.

Here is the related CR [1] and updated documentation (if you haven't had a
chance to read about 'groups' yet) [2].

Thanks!

--

[1] https://review.openstack.org/#/c/185394/
[2] https://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 Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Instructions on plugin versioning

[Irina Povolotskaya]

Hi to all,

The Fuel Plugins wiki page now contains instructions on versioning [1].

Feel free to review&ask questions.

[1] https://wiki.openstack.org/wiki/Fuel/Plugins#Plugin_versioning_system
<https://wiki.openstack.org/wiki/Fuel/Plugins#Plugin_versioning_system>

-- 
Best regards,

Irina

PI Team 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...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] [Plugins] type available

[Irina Povolotskaya]

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
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Bug triage recommendations were updated

[Irina Povolotskaya]

Hi to all,

Please, note that bug triage recommendations were updated with more
specific examples [1].
Feel free to review&comment.

[1] https://wiki.openstack.org/wiki/Fuel/Plugins#Bugs

-- 
Best regards,

Irina

PI Team 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...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Transition of SDK to docs.openstack.org

[Irina Povolotskaya]

Hi to everyone,

please be informed that Fuel Plugin SDK is being migrated to
docs.openstack.org to deliver a better dev. experience and versioning.

the current version placed here [1] features the very initial revision of
the SDK, with no specifics of the wiki page content  [2].

*REQUEST:*
if you have some extra feedback for SDK (e.g. for non-documented features),
you are very welcome to file a bug report following instructions [3].

thanks to everyone who contributed to SDK!

[1]
http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html
[2] https://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 questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel][Plugins] Please update your Fuel plugin's entries in DriverLog

[Irina Povolotskaya]

Hi to everyone,

please make sure your Fuel Plugin information in DriverLog [1] is
up-to-date, specifically:
- compatible OpenStack releases
- CI/CD
- maintainers list and their contact information.

Detailed instructions on working with DriverLog are found here [2].

Thank you.


[1] http://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 (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev