fuel puppets needs to know if this is first deployment

[Michał Górniak]

Hey,
when we make deploy in fuel we know on what node we are (controller, primary-controller, compute, etc) but we don't know if those deploy is first deploy of this enviroment.

The problem is, we can have some operations which we want run only once. And currently we don't have those option. If someone will remove/add controller all tasks will be run one more time, we can try make some local locks but if we remove primary controller we will lose it.

My case is like this:
i create plugin for SDN and i need to remove and add one more time defaults network(but only once during first deploy).
Currently during each redeploy i will make those operation again and it can cause deploy fail because for example someone will attach those nets to instance so i wont be able to remove it.

[Bogdan Dobrelya (bogdando)]

Moved to the python team as only the Nailgun backend may "know" if deployment is the first one or not. Library of puppet manifests should not have such info.

[Matthew Mosesohn (raytrac3r)]

In general, Puppet is used to create and ensure resources with idempotency. If you have an exec in puppet, you can add an "unless" or "onlyif" statement that can be used to see "Was this already created?" If you have some example code, we can help you improve the task so it can be run over and over.

Re-implementing task based workflow in hardcoded nailgun or astute tasks is a bad approach and we've been moving away from that for over a year now.

[Bogdan Dobrelya (bogdando)]

Agreed, non-idempotant tasks is not a CM way at all

[Dmitry Pyzhov (dpyzhov)]

No new updates for a month. Looks like it is not a bug.