> Thank you for the excellent run-down of the CLI commands. I assume this
> will make its way into the developer documentation? I would like to know if
> you could point me to more information about the inner workings of granular
> deployment. Currently it's challenging to debug issues related to granular
> deployment.

All tasks that are in scope of role are serialized right into deployment
configuration that is consumed by astute. So it can be traced in the logs
(nailgun or astute) or in astute.yaml that is stored on node itself. Here
is what it looks like [0].
Some other internals described in spec -

For developer it makes sense to get familiar with networkx data structures
[1], and then dive into debuging of [2].
But it is not an option for a day-to-day usage, and UX will be improved by
graph visualizer [3].

One more option that can improve understanding is human-readable planner..
For example it can output smth like this:

>> fuel deployment plan --start hiera --end netconfig

   Manifest hiera.pp will be executed on nodes [1,2,3]
   Manifest netconfig will be executed on nodes [1,2]

But i am not sure is this thing really necessary, dependencies are trivial
in comparison to puppet, and i hope it will take very little time to
understand how things are working :)

As an example there is a bug [0] where tasks appear to be run in the wrong
> order based on which combination of roles exist in the environment.
> However, it's not clear how to determine what decides which tasks to run
> and when (is it astute, fuel-library, etc.), where the data comes from.
> etc.

As for the bug - it may be a duplicate for
https://launchpad.net/bugs/1417579, which was fixed by

[0] http://paste.openstack.org/show/168298/
[3] https://review.openstack.org/#/c/152434/
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to