OpenStack community pinboard

[dagwieers]

We could collectively benefit from forming a Working Group related to OpenStack integration. We have quite some contributors on Github and users on IRC that are interested in improving this integration.

So this issue is a call for potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:

• test, review and add shipits to existing OpenStack PRs
• work collectively on the OpenStack roadmap
• provide a single-point-of-contact for interested OpenStack contributors
• collaborate on an OpenStack-specific Wiki
• have a $team_openstack in BOTMETA.yml for auto-notifying team members
• implement auto-labeling OpenStack issues and PRs

[dagwieers]

If you want to actively lead or are interested to be part of this Working Group, add your name to the Wiki page ! If we have a large enough group, we can start our own OpenStack Working Group.

I started labeling all the OpenStack related issues and PRs so we can more easily track them:

• https://github.com/ansible/ansible/pulls?q=is:pr+is:open+label:openstack (40 open PRs)
• https://github.com/ansible/ansible/issues?q=is:issue+is:open+label:openstack (63 open issues)

PS If you no longer want to receive any messages from this pinboard, feel free to unsubscribe from this issue ticket.

[jamescassell]

I'll step up to lead this one if there's no one more experienced willing to do it. (I'm fairly new to the OpenStack code, but I manage an OpenStack Private Cloud instance day-to-day.)

What's the process for folks to get added to team_openstack in BOTMETA.yml?

[dagwieers]

@jamescassell I usually wait a few days to act on who is added to the list. In this case we already have a member-list that is already in $team_openstack. If I don't do it in a single batch, people will get notifications for every issue/pr and for every new member added. That's not what we want. (I requested an improvement for @ansibot for this issue)

[pilou-]

Does someone have the time to review this PR ansible/ansible#50285 ?

[sathiarajah]

I submitted 2 issues on ansible openstack module, os_server & os_stack. We would like to know if the issues are still under investigation/fix has been identified ?

On the os_stack, we are not able to update the existing the existing stack. More information available here - ansible/ansible#59579

Whereas using the os_server, when we add a nic, that nic does not get updated to the existing server. More information available here - ansible/ansible#60045

Appreciate the feedback.

[satyamsaty]

I am also facing the same issue .Appreciate help .

[sathiarajah]

We would like to know if the issue ansible/ansible#59579 still under investigation/fix has been identified ?

I have upgraded our openstacksdk to 0.36 and the issue is still observed.

Appreciate the feedback.