Bas van Oostveen wrote:

Can we write plugins in Python ?

The only ones I can find are in Perl, but since the web frontend (and my language of choice) is Python. I would love to write them directly in it.

If it's not currently possible but should be implemented and need somebody to do that, then please contact me separately to discuss options.

Hi Ban,

The Nexenta plugin consists of 1 frontend (NMS) and 2 backends (NMC/CLI and NMV/WebGUI). NMS and NMC components must be written in Perl, but NMV in Python (you must know cherrypy/turbogears/sqlobject/kid templates). We have the skeleton plugin called HelloWorld. Feel free to download it and review.

Please put your future questions about the plugin development here.

Thanks for the reply.

Are there any plans to support Python in NMS and NMC (Specially NMS) ? And if not can we (the community?) do anything to make nexenta consider multi language support ? :)

1. I'm sorry, but no, Python will never in NMS/NMC. Perl is better fo that components because 99% of work is a parsing commands output.

2. Nexenta supports i18n in WebGUI. We have English, Japanese and Russian translations. We're working on extracting the translations into packages for the community to make i18n better and actual. Just be online when we done ;)

Never is quite strong... :(

I understand your position; but I cannot deny a bit disappointment.

With the multi-language part of my message I meant programming languages for plugins in Nexenta not natural onces :)

Was hoping that metafile.pm would support pointing to a target that implements the correct api and through that means would be reasonably programming language independent.

Since everybody has there languages of choice. And it would be cool if the communities and companies alike would have some options in programming there extensions/plugins in environments there familiar with.

For example; In the company I work in it's decided that we only use Python and Java. (and Python is used exclusively for sysadmin automation.) Writing custom NexentaStor plugins in anything else then those language is very unlikely to happen for us.

Now I understand that you have to choice something and that you cannot please everybody. But it would be so cool :P :)

Thanks again for the quick reply :)

Plugin for NMS/NMC can only be written in Perl or Perl/C binding.

Runner for NMS can be written in any language which supports good D-Bus bindings. Like Ruby, Pythin, C, C++, etc

Remote NMS client can be also written in any language which supports D-Bus bindings. And for Windows/UNIX we support SDKs which can be used as an example.

Starting from 3.0.2, NMS clients also can be written in any language via REST API - documentation will be published later this month.

Dmitry Yusupov wrote:

Starting from 3.0.2, NMS clients also can be written in any language via REST API - documentation will be published later this month.

Any news or pointers on that REST API documentation? That would be very useful. I had a browse around but have missed it so far.

Hello Jamie,

REST API doc will be published in the middle of the month with 3.0.4 release. For now I've attached a .pdf copy of the file.

Thank you for the REST document. I'm trying it now.

I have a further question on the REST API : I will start a new thread on it.