Find places where ziploader is used and change them to ansiballz so that people aren't confused when they google for information.information (#16715)

This commit is contained in:
Toshio Kuratomi
2016-07-21 10:58:24 -07:00
committed by GitHub
parent aae5e50299
commit 48a2773463
6 changed files with 44 additions and 44 deletions

View File

@@ -49,14 +49,14 @@
- Openstack (Community maintainers)
- Google (Google/Community)
- Digital Ocean (Community)
- Ziploader:
- Ansiballz (renamed from 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)
- Port most of the functionality in module\_utils to be usage in ansiballz instead
- Port a few essential modules to use ansiballz instead of module-replacer as proof of concept
- 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)
- 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
- ansiballz is a helpful building block for: python3 porting(high priority), better code sharing between modules(medium priority)
- ansiballz 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