chore: initial commit with the configurations files

[Eduardo-Morais]

No description provided.

[winiciusallan]

Thanks @Eduardo-Morais for your hard work!

There are a lot of requested changes, especially typos. Considering a multinode deploy, you'll have to change the logic from your tasks to run in specific nodes. For example:

• Run the task to change the ml2_conf.ini needs to be done in the deploy node

and so on...

Also, you need to have strong documentation that supports your decision and how the entire process occurs. This involves deleting tables from the database, which may be a very critical operation.

I missed a group_vars file so we can define variables to use in the playbook. Some environments use virtual environments to install kolla-ansible, so you should source them before running any playbook. You can add this as an additional step or as a requirement, but you should detail it in the docs.

[winiciusallan]

This is ok in all-in-one environments, but you should keep in mind that we will run this on a multinode cluster.

Here you can see that kolla defines a host group for network nodes, so you may need to change this to keep the consistency.

Do you need to perform any specific task on compute nodes? If so, you need to add logic to run in those nodes.

[winiciusallan]

If you don't have any defaults, this file is useless. Let's delete it and let the user define them.

[winiciusallan]

A few comments inline. Let me know what you think.