cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Merge pull request #16105 from mckerrj/devel

Browse source 
2.2 Roadmap and moving Roadmap into docsite with links from root roadmap file.
This commit is contained in:
Jason McKerr 2016-06-02 17:32:55 -04:00
commit 8a3f3b96c0
4 changed files with 239 additions and 98 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

98
ROADMAP.md
View file

@ -1,98 +0,0 @@
Roadmap For Ansible by Red Hat
=============
This document is now the location for published Ansible Core roadmaps.
The roadmap will be updated by version. Based on team and community feedback, an initial roadmap will be published for a major or minor version (2.0, 2.1). Subminor versions will generally not have roadmaps published.
This is the first time Ansible has published this and asked for feedback in this manner. So feedback on the roadmap and the new process is quite welcome. The team is aiming for further transparency and better inclusion of both community desires and submissions.
These roadmaps are the team's *best guess* roadmaps based on the Ansible team's experience and are also based on requests and feedback from the community. There are things that may not make it on due to time constraints, lack of community maintainers, etc. And there may be things that got missed, so each roadmap is published both as an idea of what is upcoming in Ansible, and as a medium for seeking further feedback from the community. Here are the good places for you to submit feedback:
* Ansible's google-group: ansible-devel
* Ansible Fest conferences.
* IRC freenode channel: #ansible-devel (this one may have things lost in lots of conversation, so a caution).
2.1 Roadmap, Targeted for the End of April
==========
## Windows, General
* Figuring out privilege escalation (runas w/ username/password)
* Implement kerberos encryption over http
* ~~pywinrm conversion to requests (Some mess here on pywinrm/requests. will need docs etc.)~~ DONE
* ~~NTLM support~~ DONE
## Modules
* Windows
* ~~Finish cleaning up tests and support for post-beta release~~ DONE
* ~~Strict mode cleanup (one module in core)~~ DONE
* Domain user/group management
* Finish win\_host and win\_rm in the domain/workgroup modules.
* Close 2 existing PRs (These were deemed insufficient)
* Replicate python module API in PS/C# (deprecate hodgepodge of stuff from module_utils/powershell.ps1)
* Network
* Cisco modules (ios, iosxr, nxos, iosxe)
* Arista modules (eos)
* Juniper modules (junos)
* OpenSwitch
* Cumulus
* Dell (os10) - At risk
* Netconf shared module
* Hooks for supporting Tower credentials
* VMware (This 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).
* vsphere\_guest brought to parity with other vmware modules (vs Viasat and 'whereismyjetpack' provided modules)
* VMware modules moved to official pyvmomi bindings
* VMware inventory script updates for pyvmomi, adding tagging support
* Azure (Notes: We've made progress here now that Microsoft has swaped out the code generator on the Azure Python SDK. 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?)
* ~~Minimal Azure coverage using new ARM api~~ DONE
* ~~Resource Group~~ DONE
* ~~Virtual Network~~ DONE
* ~~Subnet~~ DONE
* ~~Public IP~~ DONE
* ~~Network Interface~~ DONE
* ~~Storage Account~~ DONE
* ~~Security Group~~ DONE
* ~~Virtual Machine~~ DONE
* ~~Update of inventory script to use new API, adding tagging support~~ DONE
* Docker:
* Start Docker module refactor
* Update to match current docker CLI capabilities
* Docker exec support
* Upgrade other cloud modules or work with community maintainers to upgrade. (In order)
* AWS (Community maintainers)
* Openstack (Community maintainers)
* Google (Google/Community)
* Digital Ocean (Community)
* Ziploader:
* Write code to create the zipfile that gets passed across the wire to be run on the remote python
* Port most of the functionality in module\_utils to be usage in ziploader instead
* Port a few essential modules to use ziploader instead of module-replacer as proof of concept
* New modules will be able to use ziploader. Old modules will need to be ported in future releases (Some modules will not need porting but others will)
* 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
* ziploader is a helpful building block for: python3 porting(high priority), better code sharing between modules(medium priority)
* ziploader is a good idea before: enabling users to have custom module_utils directories
* Expand module diff support (already in progress in devel)
* Framework done. Need to add to modules, test etc.
* Coordinate with community to update their modules
* Things being kicking down the road that we said we’d do
* NOT remerging core with ansible/ansible this release cycle
* Community stuff
* Define the process/ETA for reviewing PR’s from community
* Publish better docs and how-tos for submitting code/features/fixes

25
ROADMAP.rst Normal file
View file

@ -0,0 +1,25 @@
*******************************
Roadmap For Ansible by Red Hat
*******************************
This document is now the location for published Ansible Core roadmaps.
The roadmap will be updated by version. Based on team and community feedback, an initial roadmap will be published for a major or minor version (2.0, 2.1). Subminor versions will generally not have roadmaps published.
2.1 was the first time Ansible has published this and asked for feedback in this manner. So feedback on the roadmap and the new process is quite welcome. The team is aiming for further transparency and better inclusion of both community desires and submissions.
These roadmaps are the team's *best guess* roadmaps based on the Ansible team's experience and are also based on requests and feedback from the community. There are things that may not make it on due to time constraints, lack of community maintainers, etc. And there may be things that got missed, so each roadmap is published both as an idea of what is upcoming in Ansible, and as a medium for seeking further feedback from the community. Here are the good places for you to submit feedback:
- Ansible's google-group: ansible-devel
- Ansible Fest conferences.
- IRC freenode channel: #ansible-devel (this one may have things lost in lots of conversation, so a caution).
=======================================
Current 2.2 Roadmap is open for comment
=======================================
We are currently trying to finalize the 2.2 Roadmap, targeted for September delivery. We are seeking community feedback for 2.2. That document is here:
`2.2 Roadmap Document <docsite/rst/roadmap/ROADMAP_2_2.rst>`_
**Old Roadmaps are found here:**
- `2.1 Roadmap Document <docsite/rst/roadmap/ROADMAP_2_1.rst>`_

67
docsite/rst/roadmap/ROADMAP_2_1.rst Normal file
View file

@ -0,0 +1,67 @@
==========================================
2.1 Roadmap, Targeted for the End of April
==========================================
- Windows, General
- Figuring out privilege escalation (runas w/ username/password)
- Implement kerberos encryption over http
- pywinrm conversion to requests (Some mess here on pywinrm/requests. will need docs etc.)
- NTLM support
- Modules
- Windows
- Finish cleaning up tests and support for post-beta release
- Strict mode cleanup (one module in core)
- Domain user/group management
- Finish win_host and win_rm in the domain/workgroup modules.
- Close 2 existing PRs (These were deemed insufficient)
- Replicate python module API in PS/C# (deprecate hodgepodge of stuff from module_utils/powershell.ps1)
- Network
- Cisco modules (ios, iosxr, nxos, iosxe)
- Arista modules (eos)
- Juniper modules (junos)
- OpenSwitch
- Cumulus
- Dell (os10) - At risk
- Netconf shared module
- Hooks for supporting Tower credentials
- VMware (This 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).
- vsphere\_guest brought to parity with other vmware modules (vs Viasat and 'whereismyjetpack' provided modules)
- VMware modules moved to official pyvmomi bindings
- VMware inventory script updates for pyvmomi, adding tagging support
- Azure (Notes: This 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?)
- Minimal Azure coverage using new ARM api
- Resource Group
- Virtual Network
- Subnet
- Public IP
- Network Interface
- Storage Account
- Security Group
- Virtual Machine
- Update of inventory script to use new API, adding tagging support
- Docker:
- Start Docker module refactor
- Update to match current docker CLI capabilities
- Docker exec support
- Upgrade other cloud modules or work with community maintainers to upgrade. (In order)
- AWS (Community maintainers)
- Openstack (Community maintainers)
- Google (Google/Community)
- Digital Ocean (Community)
- Ziploader:
- Write code to create the zipfile that gets passed across the wire to be run on the remote python
- Port most of the functionality in module\_utils to be usage in ziploader instead
- Port a few essential modules to use ziploader instead of module-replacer as proof of concept
- New modules will be able to use ziploader. Old modules will need to be ported in future releases (Some modules will not need porting but others will)
- 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
- ziploader is a helpful building block for: python3 porting(high priority), better code sharing between modules(medium priority)
- ziploader is a good idea before: enabling users to have custom module_utils directories
- Expand module diff support (already in progress in devel)
- Framework done. Need to add to modules, test etc.
- Coordinate with community to update their modules
- Things being kicking down the road that we said we’d do
- NOT remerging core with ansible/ansible this release cycle
- Community stuff
- Define the process/ETA for reviewing PR’s from community
- Publish better docs and how-tos for submitting code/features/fixes

147
docsite/rst/roadmap/ROADMAP_2_2.rst Normal file
View file

@ -0,0 +1,147 @@
****************
Ansible Core 2.2
****************
**********************
Target: September 2016
**********************
- **Docker** (lead by Chris Houseknecht)
- Docker_network
- Docker_volume
- Docker_file
- Openshift:  oso_deployment, oso_route, oso_service, oso_login (...and possibly others. These are modules being developed to support [ansible-container](https://github.com/ansible/ansible-container).)
- Kubernetes: kube_deployment, kube_service, kube_login (...and possibly others. These too are modules being developed to support [ansible-container](https://github.com/ansible/ansible-container))
- *Extras split from Core (Team, Community, lead by Jason M and Jimi-c) (Targeting 2.2, could move into 2.3).*
Targeted towards the 2.2 release or shortly after, we are planning on splitting Extras out of the “Ansible Core” project.  That means that modules that are shipped with Ansible by default are **only** the modules in ansibl-modules-core.  Ansible extras will become a separate project, managed by the community standard.  Over the next few months we’re going to have a lot of work to do on getting all of the modules in the right places for this to work.
- Create proposal (Jason on Jimi)
- Review modules for correct location (extras v core)
- Extras is a completely different package (does not install with ansible)
- Library dependencies
- Decide and implement release schedules between Ansible Core and Extras to ensure compatibility and longevity for modules and versions of Ansible.
- **Tweaks/Fixes**
- Add the ability to set_fact to deal with updating arrays and hashes (Jimi)
- Connection handling stuff. (Toshio K. and Brian C.): This is a stretch goal for 2.2.  It may go into 2.3
- Change connection polling to avoid resource limitations, see [https://github.com/ansible/ansible/issues/14143](https://github.com/ansible/ansible/issues/14143)
- [https://docs.python.org/3/library/selectors.html#module-selectors](https://docs.python.org/3/library/selectors.html#module-selectors)
- Code: https://github.com/kai11/ansible/blob/fix/select_fd_out_of_range_wip/lib/ansible/plugins/connection/ssh.py
- **Cloud Modules (Ryan Brown) **
- AWS
- Pagination for all AWS modules (generic pagination exists, but isn’t used everywhere)
- Refactoring ec2.py to be more digestible
- Fix inconsistencies with different authentication methods (STS, environment creds, ~/.aws/credentials)
- Ryan Brown and Robyn Bergeron work on bug/PR triage to reduce backlog
- Google (Ryan Brown and Tom Melendez)
- Add support for Google Cloud DNS
- Support restoring instances from snapshots
- Improved handling of scratch disks on instances
- External OpenStack (Stretch goal for this release)
- Ryan with some help from David Shrewsbury (Zuul/Openstack at RedHat).
- Support Heat stack resources
- Support LBaaS load balancers
- Azure load balancer: Feature parity for AWS ELB (Stretch Goal)
- **VMWare (Brian, Jtanner)**
- module/inventory script: port to pyvmomi (jtanner, bcoca)
- inventory script: allow filtering ala ec2 (jtanner) (undergoing PR process)
- https://github.com/ansible/ansible/pull/15967
- vsphere: feature parity with whereismyjetpack and viasat modules 
- **Windows platform feature parity****(Matt D)**
- PS module API (mirror Python module API where appropriate). Note: We don’t necessarily like the current python module API (AnsibleModule is a huge class with many unrelated utility functions.  Maybe we should redesign both at the same time?)
- Environment keyword support 
- win_shell/win_command
- Async support 
- (stretch goal) Pipelining 
- **Windows-specific enhancements (Matt D)**
- Multiple Kerberos credential support (done, shepherd fix to pykerberos)
- Server 2016 testing/fixes 
- (stretch goal) Nano Server connection + module_utils working
- (stretch goal) Encrypted kerberos support in pywinrm 
- **Network (Nate C/Peter S)**
- Unify NetworkModules (module_utils/network.py) as much as possible 
- Add support for config diff and replace on supported platforms (2 weeks)
- Network facts modules 
- OpenVSwitch modules
- Quagga modules 
- GoBGP modules (stretch)
- **Implement ‘role revamp’ proposal to give users more control on role/task execution (Brian) **
- **https://github.com/ansible/proposals/blob/master/roles_revamp.md**
- **Vault (Jtanner/Adrian) **
- Extend ‘transparent vault file usage’ to other action plugins other than 'copy' 
- Add ‘per variable’ vault support (!vault YAML directive, existing PR already)
- Add vault/unvault filters [https://github.com/ansible/ansible/issues/12087](https://github.com/ansible/ansible/issues/12087)
- Add vault support to lookups
- Allow for multiple vault secrets [https://github.com/ansible/ansible/issues/13243](https://github.com/ansible/ansible/issues/13243)
- Config option to turn ‘unvaulting’ failures into warnings https://github.com/ansible/ansible/issues/13244
- **Python3 (Toshio):**
A note here from Jason M: Getting to complete, tested Python 3 is both a critical task and one that has so much work, and so many moving parts that we don’t expect this to be complete by the 2.2 release.  Toshio will lead this overall effort.
- RHEL8 is coming which has no python2 in default install.  Ubuntu (non-LTS) already ships without python2.  These considerations make this high priority.
- Natives are getting restless: [https://groups.google.com/forum/#!topic/ansible-project/DUKzTho3OCI](https://groups.google.com/forum/#!topic/ansible-project/DUKzTho3OCI)
- This is probably going to take multiple releases to complete.
- Side work to do: Figure out best ways to run unit-tests on modules.  Start unit-testing modules.  This is going to become important so we don’t regress python3 or python2.4 support in modules  (Going to largely punt on this for 2.2.  Sounds like Matt Clay is working on building us a testing foundation for the first half of 2.2 development so we’ll re-evaluate towards the middle of the dev cycle).
- Goals for 2.2:  
- Controller-side code can run on python3 [but may not work in practice as targeting localhost presently uses the python that runs /bin/ansible instead of defaulting to /usr/bin/python like any other target]  
- Bcoca suggests: If we’re running controller under sys.version_info[0] &gt;= 3, try to detect a python2 to set implicit localhost to instead of using sys.executable as workaround for modules not working with py3 yet. 
- We’ll have to make some decisions about some of our dependencies 
- The base deps in setup.py are ported: ['paramiko', 'jinja2', "PyYAML", 'setuptools', 'pycrypto &gt;= 2.6']
- Python-keyczar and python-six are additional deps in the rpm spec file.  Six is ported but keyczar is not. (removing keyczar when we drop accelerate for 2.3)  print deprecation in 2.1.
- Module_utils ported to dual python3/python2(2.4 for much of it, python2.6 for specific things)
- Add module_utils files to help port -- copy of the six library (v1.4.1 for python2.4 compat), unicode helpers from ansible.utils.
- More unit tests of module_utils
- A few basic modules ported to python3
- Stat module best example module since it’s essential.
- Python3 integration tests -- jimi’s idea was mark some distributions as able to fail and have them run via run_tests.sh with python3 (Fedora-rawhide, latest ubuntu?) 
- Some setup.py/packaging tweaks to make it easier for users to test with py2 and py3  (ansible-playbook-py2 and py3 installed in bin?)
- Goals for 2.3:
- Go for low hanging fruit: modules that are already python2.6+ may be easy to port to python3.
- Unfortunately, we may also have the least automated testing on these (as a large number of these are cloud modules)
- Will need to figure out how to organize “works on python3” into a cohesive set.
- Increase number of essential modules that have been ported.  Package managers, url fetching, etc.
- **Infrastructure Buildout and Changes (Matt Clay):**
Another note from Jason M: A lot of this work is to ease the burden of CI, CI performance, increase our testing coverage and all of that sort of thing.  It’s not necessarily feature work, but it’s \*\*critical\*\* to growing our product and our ability to get community changes in more securely and quickly.
- **CI Performance**
Reduce time spent waiting on CI for PRs. Combination of optimizing existing Travis setup and offloading work to other services. Will be impacted by available budget.
- **Core Module Test Organization**
Relocate core module tests to ansible-modules-core to encourage inclusion of tests in core module PRs.
- **Documentation**
Expand documentation on setting up a development and test environment, as well as writing tests. The goal is to ease development for new contributors and encourage more testing, particularly with module contributions.
- **Test Coverage**
Expand test coverage, particularly for CI. Being testing, this is open ended. Will be impacted by available budget.
- Python 3 - Run integration tests using Python 3 on CI with tagging for those which should pass, so we can track progress and detect regressions.
- Windows - Create framework for running Windows integration tests, ideally both locally and on CI.
- OS X - Include OS X in CI coverage.