[all][tripleo][openstack-ansible] Openstack Ansible modules - next steps
sshnaidm at redhat.com
Tue Dec 3 18:18:49 UTC 2019
In the meeting today we agreed to meet every Thursday starting *this week*
at 4.00 PM UTC on #openstack-sdks channel on Freenode. We'll discuss
everything related to Openstack Ansible modules.
Agenda and topics are in the etherpad:
(I've created a new one, because we don't limit to Ironic modules only,
it's about all of them in general)
Short minutes from meeting today:
1. We meet every Thursday from this week at 4.00 PM UTC on #openstack-sdks
2. Interested parties for now are: Ironic, Tripleo, Openstack-Ansible,
Kolla-ansible, OpenstackSDK teams. Feel free to join and add yourself in
the etherpad. 
3. We'll track our work in Storyboard for ansible-collections-openstack (in
4. Openstack Ansible modules will live as collections under Ansible SIG in
repo openstack/ansible-collections-openstack  because there are issues
with different licensing: GPLv3 for Ansible in upstream and Openstack
5. Ansible upstream Openstack modules will be merge-frozen when we'll have
our collections fully working and will be deprecated from Ansible at some
point in the future.
6. Openstack Ansible collections will be published to Galaxy.
7. There is a list of people that can be pinged for reviews in
ansible-collections-openstack project, feel free to join there 
1. We use openstacksdk instead of [project]client modules.
2. We will rename modules to be more like os_[service_type] named, examples
are in Ironic modules etherpad 
Logs from meeting today you can find here:
Please feel free to participate and add topics to agenda. 
On Wed, Nov 27, 2019 at 7:57 PM Sagi Shnaidman <sshnaidm at redhat.com> wrote:
> Hi, all
> in the light of finding the new home place for openstack related ansible
> modules  I'd like to discuss the best strategy to create Ironic ansible
> modules. Existing Ironic modules in Ansible repo don't cover even half of
> Ironic functionality, don't fit current needs and definitely require an
> additional work. There are a few topics that require attention and better
> be solved before modules are written to save additional work. We prepared
> an etherpad  with all these questions and if you have ideas or
> suggestions on how it should look you're welcome to update it.
> We'd like to decide the final place for them, name conventions (the most
> complex one!), what they should look like and how better to implement.
> Anybody interested in Ansible and baremetal management in Openstack,
> you're more than welcome to contribute.
>  https://review.opendev.org/#/c/684740/
>  https://etherpad.openstack.org/p/ironic-ansible-modules
> Best regards
> Sagi Shnaidman
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss