1===========
2Ansible 2.1
3===========
4**Target: April 2016**
5
6.. contents:: Topics
7
8Windows
9-------
10- General
11
12  - Figuring out privilege escalation (runas w/ username/password)
13  - Implement kerberos encryption over http
14  - pywinrm conversion to requests (Some mess here on pywinrm/requests. will need docs etc.)
15  - NTLM support
16
17- Modules
18
19  - Finish cleaning up tests and support for post-beta release
20  - Strict mode cleanup (one module in core)
21  - Domain user/group management
22  - Finish win_host and win_rm in the domain/workgroup modules.
23
24    - Close 2 existing PRs (These were deemed insufficient)
25
26  - Replicate python module API in PS/C# (deprecate hodgepodge of stuff from module_utils/powershell.ps1)
27
28Network
29-------
30- Cisco modules (ios, iosxr, nxos, iosxe)
31- Arista modules (eos)
32- Juniper modules (junos)
33- OpenSwitch
34- Cumulus
35- Dell (os10) - At risk
36- Netconf shared module
37- Hooks for supporting Tower credentials
38
39VMware
40------
41This one is a little at risk due to staffing. We're investigating some community maintainers and shifting some people at Ansible around, but it is a VERY high priority.
42
43- vsphere\_guest brought to parity with other vmware modules (vs Viasat and 'whereismyjetpack' provided modules)
44- VMware modules moved to official pyvmomi bindings
45- VMware inventory script updates for pyvmomi, adding tagging support
46
47Azure
48-----
49This is on hold until Microsoft swaps out the code generator on the Azure Python SDK, which may introduce breaking changes. We have basic modules working against all of these resources at this time. Could ship it against current SDK, but may break. Or should the version be pinned?)
50- Minimal Azure coverage using new ARM api
51- Resource Group
52- Virtual Network
53- Subnet
54- Public IP
55- Network Interface
56- Storage Account
57- Security Group
58- Virtual Machine
59- Update of inventory script to use new API, adding tagging support
60
61
62Docker
63------
64- Start Docker module refactor
65- Update to match current docker CLI capabilities
66- Docker exec support
67
68Cloud
69-----
70Upgrade other cloud modules or work with community maintainers to upgrade.  (In order)
71
72- AWS (Community maintainers)
73- Openstack (Community maintainers)
74- Google (Google/Community)
75- Digital Ocean (Community)
76
77Ansiballz
78---------
79Renamed from Ziploader
80
81- Write code to create the zipfile that gets passed across the wire to be run on the remote python
82- Port most of the functionality in module\_utils to be usage in ansiballz instead
83- Port a few essential modules to use ansiballz instead of module-replacer as proof of concept
84- New modules will be able to use ansiballz.  Old modules will need to be ported in future releases (Some modules will not need porting but others will)
85- Better testing of modules, caching of modules clientside(Have not yet arrived at an architecture for this that we like), better code sharing between ansible/ansible and modules
86- ansiballz is a helpful building block for: python3 porting(high priority), better code sharing between modules(medium priority)
87- ansiballz is a good idea before: enabling users to have custom module_utils directories
88
89Diff-support
90------------
91Expand module diff support (already in progress in devel)
92
93- Framework done. Need to add to modules, test etc.
94- Coordinate with community to update their modules
95
96Other
97-----
98Things being kicking down the road that we said we'd do
99
100- NOT remerging core with ansible/ansible this release cycle
101
102Community
103---------
104- Define the process/ETA for reviewing PR's from community
105- Publish better docs and how-tos for submitting code/features/fixes
106