Open Stack

Hi Swann,

> However, we still need deployment order between independent
> plugins and it seems impossible to define the priorities

There's no such things like priorities for now.. perhaps we can
introduce some kind of anchors instead of priorities, but that's
another story.

Currently the only way to synchronize two plugins is to make one to
know about other one. That means you need to properly setup "requires"
field:

    - id: my-plugin-b-task
      type: puppet
      role: [my-plugin-b-role]
      required_for: [post_deployment_end]
      requires: [post_deployment_start, PLUGIN-A-TASK]
      parameters:
        puppet_manifest: some-puppet.pp
        puppet_modules: /etc/puppet/modules
        timeout: 3600
        cwd: /

Thanks,
Igor

On Mon, Sep 7, 2015 at 11:31 AM, Swann Croiset <scroiset at mirantis.com> wrote:
> Hi fuelers,
>
> We're currently porting nearly all LMA plugins to the new plugin fwk 3.0.0
> to leverage custom role capabilities.
> That brings up a lot of simplifications for node assignment, disk
> management, network config, reuse core tasks and so on .. thanks to the fwk.
>
> However, we still need deployment order between independent plugins and it
> seems impossible to define the priorities [0] in deployment_tasks.yaml,
> The only way to preserve deployment order would be to keep tasks.yaml too.
>
> So, I'm wondering if this is the recommended solution to address plugins
> order deployment with plugin fwk 3.0.0?
> And furthermore if tasks.yaml will still be supported in future by the
> plugin fwk or if the fwk shouldn't evolve  by adding priorities definitions
> in deployment_tasks.yaml ?
>
> Thanks
>
> [0] https://wiki.openstack.org/wiki/Fuel/Plugins#Plugins_deployment_order
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>