Community: VMware Working Group meeting agenda - Jul-Aug 2017

Created on 18 Jul 2017  路  26Comments  路  Source: ansible/community

The VMware Working Group focuses on delivering modules and features to Ansible to support working with VMware. The group meets every week on Mondays at 16:00 UTC (see calendar)

More information related to the VMware Working Group is available at: https://github.com/ansible/community/tree/master/group-vmware

Feel free to add your questions to this ticket to be discussed during the upcoming meeting.

meeting_agenda vmware

Most helpful comment

~I would like to bring up the issue of a lot of current modules not having implemented "update" functionality, only add/remove.~

~To name a few:~

  • ~vmware_portgroup~
  • ~vmware_vswitch~
  • ~vmware_dvswitch~
  • ~vmware_dvs_portgroup~

~It makes doing things such as modifying the default vswitch of an esxi install impossible.
I believe fixing this might be something useful to add to the roadmap, and for the future if that's not the case already require this as criteria for new modules being added.~

Update: We now collect this information in the VMware WG wiki: Missing idempotency, Help is welcome to fix these issues.

All 26 comments

New VMware modules waiting for review/feedback.

Please review these tickets on a weekly basis (if there was new progress, otherwise add instructions to the owner how to continue).

Once merged, please add to CHANGELOG.md !

~I would like to discuss the following PRs:~

~We need to come up with a plan to deprecate vsphere_guest.~

  • ~what features is vmware_guest missing?~
  • ~should we deprecate vsphere_guest before those features are done?~
  • ~what to do with all the open issues and PRs for vsphere_guest?~

All vmware things in ansible-modules-core ~and ansible-modules-extras~ issues need to be cleaned out.

Update: We are now tracking the missing functionality in vmware_guest in the Wiki.

~I would like to bring up the issue of a lot of current modules not having implemented "update" functionality, only add/remove.~

~To name a few:~

  • ~vmware_portgroup~
  • ~vmware_vswitch~
  • ~vmware_dvswitch~
  • ~vmware_dvs_portgroup~

~It makes doing things such as modifying the default vswitch of an esxi install impossible.
I believe fixing this might be something useful to add to the roadmap, and for the future if that's not the case already require this as criteria for new modules being added.~

Update: We now collect this information in the VMware WG wiki: Missing idempotency, Help is welcome to fix these issues.

Maybe it is time to think about what we still want to achieve before the v2.4 release. For example, it would be nice to have integration tests for all modules that will ship in v2.4. Or have VMware coverage closer to 100% (it is now at ~23.74%~ 26.60%). Or have a chapter related to VMware management to the documentation, etc.

If we can list a few achievable goals like that, we can ask for contributors to focus on those items and distribute the work like we have been doing in the Windows working group. People interested in any of these actions already can step forward and then we can plan it and track its progress an a daily and weekly basis.

The community meeting calendar does not contain the VMware group meeting, can this be added?

Update: AFAIK only @mattclay can add items to this calendar. We already requested to have all ical calendars of WG meetings from https://github.com/ansible/community/tree/master/meetings/ical to be imported so they are automatically updated when the .ics files change.
Update2: I made a formal request now in #217

Following modules needs review

  1. https://github.com/ansible/ansible/pull/27898 - Refactor in vmware_vm_facts
  2. https://github.com/ansible/ansible/pull/25857 - Support for multiple vnic in vSwitch
  3. https://github.com/ansible/ansible/pull/26819 - Remove redundant get_obj
  4. https://github.com/ansible/ansible/pull/25772 - Use response.content instead of response object
  5. https://github.com/ansible/ansible/pull/26323 - Simplify vmware connection
  6. https://github.com/ansible/ansible/pull/26859 - find_datacenter_by_name refactor and testcase
  7. https://github.com/ansible/ansible/pull/25944 - Documentation update
  8. https://github.com/ansible/ansible/pull/25221 - vmware_guest_snapshot docs

~One more: ansible/ansible#27236 - vmware_guest_tools~

~Update: I moved it up in the list of new modules to review. We should review all new modules on a weekly basis (if there was any progress from last meeting, otherwise add instructions to the owner to de-block).~

Close request:

~I would like to discuss the following PRs:~

~I'd like to add the following PR to that list:~

  • ~ansible/ansible#27236 -- vmware_guest_tools: New module to wait for VMware Tools to respond running/available (main use case: wait for them to come up so you can execute commands through them)~

~Update: The consensus was to split the module in 2 (one for managing vmware-tools, one for waiting for vmware-tools to work).~

Agenda points next meeting (trivia):

  • What's missing in govcsim?
  • VMworld Hackathon - do we want to have a team do something useful, ideas (expand govcsim for instance)? (both US and EU, vmwa.re/hackathon, i'm at EU)

Ansible Contributor Summit 5 (Part of AnsibleFest 2017 San Francisco)

When: 2017-09-06:
Notes: https://public.etherpad-mozilla.org/p/ansible-summit-september-2017
Event will be in person + online (Video + IRC)

Agenda is open for topics for the next Contributors Summit

Please add (and vote +1) for any topics.

PR to discuss: https://github.com/ansible/ansible/pull/28155

Updated to next months issues

PR to discuss :
https://github.com/ansible/ansible/pull/28121

Updated to next months issues

NOTE: meetings are canceled for the week Aug 21st to 25th due to 'all hands' meeting for the core team. We will resume normal schedule after that.

So we have some concerns related to the state of VMware in Ansible and are collecting these concerns at: https://github.com/ansible/community/wiki/VMware:-community-plan

Anyone is welcome to add (perceived) concerns or problems on that Wiki page so we can have a discussion during the next VMware Working Group meeting on Monday 28/8. We would like to focus first on the various angles, before we can discuss solutions to tackle them.

Meeting starts in about 10 minutes (16:00 UTC).

Meeting ended Mon Aug 28 17:03:00 2017 UTC

  • Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-08-28/ansible_vmware_working_group_meeting.2017-08-28-16.00.html
  • Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-08-28/ansible_vmware_working_group_meeting.2017-08-28-16.00.txt

    • Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-08-28/ansible_vmware_working_group_meeting.2017-08-28-16.00.log.html

NOTE: meetings are canceled for the week September 4th through 8th due to AnsibleFest San Francisco. We will resume normal schedule after that.

Please refer next month issue page

Was this page helpful?
0 / 5 - 0 ratings

Related issues

gundalow picture gundalow  路  11Comments

bcoca picture bcoca  路  27Comments

gundalow picture gundalow  路  20Comments

gundalow picture gundalow  路  5Comments

decentral1se picture decentral1se  路  16Comments