Let users know which workflows are private

[Dougal Matthews]

The workflows don't have a clear convention about which are private and which are public. Some with underscores are private, but others which are only used by Heat don't follow this convention.

We should find a way to improve this, it would make it clearer how the workflows should be used.

It is possible that we could do this with keystone users/policies or Mistral namespaces?

[Toure Dunnon (toure)]

I would propose the use of the namespace in regards to there intended use, that is to create a structured convention with dictates the category in which the workflow belongs. A category could have a hierarchy of parent namespaces with children:

mistral workflow-create --namespace "private, undercloud" test_workflow.yaml

(undercloud) [stack@undercloud ~]$ mistral workflow-get 39986028-d1be-4688-9871-11d698bf2461
+------------+--------------------------------------+
| Field | Value |
+------------+--------------------------------------+
| ID | 39986028-d1be-4688-9871-11d698bf2461 |
| Name | create_vm |
| Namespace | private, undercloud |
| Project ID | 15490e4a28af44d093de308afa0028c4 |
| Tags | <none> |
| Input | vm_name, image_ref, flavor_ref |
| Created at | 2018-05-24 18:04:34 |
| Updated at | None |
+------------+--------------------------------------+

So, in this case, the parent level could denote whether it is public or private followed by the functional grouping, in this case, undercloud or overcloud.

[Dougal Matthews (d0ugal)]

I don't think this is worth doing anymore with the reduced Mistral usage.