Mirantis OpenStack 6.0: now with plugins

    Authors: Nikolai Markov, Ilya Stechkin, Irina Povolotskaya The

    global OpenStack summit is approaching uncontrollably. This sky-high gathering takes place twice a year in different cities of the world (this time, for example, Vancouver was honored to host the event ) and enables everyone who is interested in developing the OpenStack ecosystem in one way or another to exchange news and at the same time determine in which direction evolve the platform. And besides, the summit disciplines developers, forcing them to quickly finish new versions of distributions in order to present them to the most respected collection. Mirantis is no exception.

    We are preparing improvements to our current - sixth - release of Mirantis OpenStack (or MOS, as it is called for simplicity)) But still, the main changes have already taken place. And we are lagging behind life - we just had time to talk about the changes that occurred in the previous release and related to the containerization of applications using Docker.

    Meanwhile, nothing stands still. In MOS 6.0, containerization is definitely used. But the main innovation was the transition to architecture, which provides the ability to work with plugins (pluggable architecture). This is important even if only because you now have the opportunity to embed your own plugins in Fuel - a tool for deploying MOS cloud and further managing it. But we already talked about Fuel in more detail in a previous post . And in this we are more interested in plugins.

    Why plugins?

    It is impossible to predict all the unique needs of users: someone needs NFS , and someone cannot live without LbaaS (Load-Balancing-as-a-Service) ... Instead of creating a unique distribution kit for the tasks of a specific client each time (and this increases cloud deployment time and project cost), we made a constructor from MOS. And now, to customize the distribution, just create the appropriate plugin. We started to collect a collection of certified plug-ins: a bank of standard solutions will allow our customers to save even more time and money (and this despite the fact that Mirantis solutions already now differ favorably from other cloud solution providers playing on the Russian market).

    What is plugin certification?

    The certification procedure is not required for plugin developers. However, if you still decide, then you need to understand that during certification a number of requirements are presented to the plugin and it passes a more thorough check. For us, a “certified plugin” is, first of all, a proven, reliable, safe to use, that is, one that does not break anything in the environment. When we promise a thorough check, this means that the plug-in will be tested directly by the PI (Partner Integration) team according to the test report: a number of cases from the report are taken and repeated by our experts. This means that before certification the plug-in should already be tested according to the established procedure and the results of this test should be presented to our company’s PI. Thus, our check is repeated. The result is compared with what is described in the report. Once again, we draw attention to the fact that the certification procedure is purely voluntary. The presence of a certificate in a plug-in means only that Mirantis guarantees its stable operation and support.

    Plugins from the point of view of the user

    1) Go to the plugin catalog on the Mirantis website ;
    2) select the plugin and download it;
    3) copy the selected plugin to the master node using secure copy:

    scp fuel_plugin_name-1.0.0.fp root @: master_node_ip: / tmp
    cd / tmp
    fuel plugins --install fuel_plugin_name-1.0.0.fp

    4) After you create a new environment, in the Fuel user interface, in the “Settings” tab, put a “checkmark” in the checkbox (if necessary, fill in additional fields for the plugin);
    5) reconfigure the environment;
    6) bury the cloud;
    7) use the plugin with pleasure.

    Note:To work with the plugin, you must install it BEFORE you deploy and configure the environment. Otherwise, you will have to repeat the environment deployment procedure in order to be able to connect the installed plug-in.

    Plugins from the point of view of the developer

    Write the code for the plugin that implements its business logic, and write a description of the plugin as described in the manual (Engl) .
    When ready, take fpb and build your plugin so that it can be installed (during development, it's just code and packages).
    In order to simplify the process of creating new plugins for developers, we developed a tool called Fuel Plugin Builder , which, in fact, is a simple command-line utility that allows you to quickly and easily create a “skeleton” for your future plug-in . As you already understood, we are not philanthropists - it is beneficial for us that as many new developers as possible fill up the bank of certified plugins. That's why we care about the developers! ;)

    What else is new in MOS 6.0, except for plugins

    But not one plug-ins rich in MOS 6.0. We traditionally make distributions update to the release of the new version of the platform, so it is not surprising that MOS 6.0 supports the release of Juno. Well, besides, now users who are accustomed to VMware have the opportunity to choose vCenter as a hypervisor for their OpenStack cluster, and NSX as a network solution (thanks to our Partner Integration team). Also, when using vCenter, vSphere datastore support is available as a backend for Glance. You can indicate your preferences using the check boxes in the UI.

    Naturally, we remember that in the world of cloud technologies stability and scalability of the platform are of great importance. Testing MOS 6.0 in our laboratory with real equipment, we got the opportunity to claim that Fuel will be able to deploy the cloud in an environment of 100 nodes. But this is not all: for additional changes, read the material following the May summit. And then we will talk with you about the Murano application directory.

    Only registered users can participate in the survey. Please come in.

    Would you like to read the “developer diary” of one of the plugins for MOS to get a detailed idea of ​​the procedure for creating plugins?

    • 88.4% Yes 46
    • 11.5% No 6

    Also popular now: