This deep copy would cause ansible-playbook to get hung up and fail to
spawn new subprocesses thus forcing extremely large scan jobs to
serialize their connections through one process. This had the effect
of forcing `forks=1` behavior.
This change was for citco, a customer who is running scan jobs against
600 hosts with a forks value of 200.
* release_2.4.5:
Remove distribute from the setup virtualenv if installed (#1631)
Update changelogs for 2.4.5 release
Only export changed targets in reprepro
Improve the efficiency of the stdout dump database migration
Added logic to not show the loop summary events in the UI by looking at event_data.event_loop.
Handle runner items from ansible v2
bump boto
fix case of Ansible v2 _result.cmd is list for release 2.4.5
Handle both string and list hosts in our hosts->name conversion
Default play names to the hosts the play was run against
Use better isinstance(x) type checking
Backporting test fixes from PR #1020: Fix error with ad hoc command events when running in check mode.
Fix for tasks breaking when using 'yum' with ansible 1.9.4
Bump 2.4.5 version, changelogs, and reprepo
* Vendor ansible's azure_rm inventory script
* Add new inventory type
* Add new credential type
* Expand host instance_id column from varchar 100 to 1024 to accept the
long instance ids returned by Azure
* Make the inventory_import azure match rename more explicit.
Previously a job template would always block another job template launch
regardless of the details of the job template. We now restrict that
blocking logic to only block in the case that the job template was
launched with the same inventory. We keep the exclusion where if the
launch type is 'callback' and the limits differ then they won't be blocked
* Break requirements down into ansible and tower reqs
* Generate separate Ansible and Tower virtual environments
* Install appropriate requirements files into each one
* Modify development tools to use these venvs instead of our old
site-packages
* Modify settings to indicate venv enablement and location of venvs
* Modify tasks to use the proper virtual environment for its purpose
* Break requirements down into ansible and tower reqs
* Generate separate Ansible and Tower virtual environments
* Install appropriate requirements files into each one
* Modify development tools to use these venvs instead of our old
site-packages
* Modify settings to indicate venv enablement and location of venvs
* Modify tasks to use the proper virtual environment for its purpose
DRF will try to resolve potential candidates into the OPTIONS endpoint.
This is mainly to support their POST field in the browseable API. We
don't need this and it can yield some expensive queries so we bypass
generating choices for any RelatedField fields
For new installs the database may not be online and thus the migration
can't happen. This will allow it to continue but we may want more
messaging to the user running potential upgrades
Previously this would only be visible if survey is enabled. It should
be possible to define and view a survey even if this is disabled. The
enablement flag controls whether the survey prompt is shown and required.
* Break requirements down into ansible and tower reqs
* Generate separate Ansible and Tower virtual environments
* Install appropriate requirements files into each one
* Modify development tools to use these venvs instead of our old
site-packages
* Modify settings to indicate venv enablement and location of venvs
* Modify tasks to use the proper virtual environment for its purpose
* notifications_work: (23 commits)
Updates to notification unit tests after @wwitzel3's feedback
Fix some notifications issues and write some tests
Add notification system documentation
Clean up flake8 related issues
Fixing up some unicode issues
Implement tower ui view url on models
Sanity check and force proper types in admin check
Proper type for in check
Adding migration and base notification type
Add a periodic administrative notification
Refactor message generator
Support notification password field encryption
Notification configuration type checking
Refactor NotificationTemplate to Notifier
Implement irc notification backend
Add webhook notification backend
Pagerduty and Hipchat backends plus some cleanup
Notification serializers, views, and tasks
Implement notification serializer and validations
Notification endpoints and url expositions
...
* Job object can now control the output and generate K:V output for
notification types that can support it
* Notifications store the body as json/dict now to encode more
information
* Notification Type can further compose the message based on what is
sensible for the notification type
* This will also allow customizing the message template in the future
* All notification types use sane defaults for the level of detail now
* release_2.4.4: (35 commits)
Update changelog for 2.4.4 release
Make pycompile non-fatal during deb build
Revert "Add virtualenv site-pagkages to Python path before system dist-packages, to get new setuptools"
Roll back mock version due to packaging issues
Add virtualenv site-pagkages to Python path before system dist-packages, to get new setuptools
change to warning behavior
Resolve bug when building with /bin/sh on Ubuntu
Attempt to workaround pip install issue
point at packages with source on pypi
Mock requires a newer setuptools when building requirements
requests needs openssl
Properly set the shell during directory migration
pyrax bumpb new python license
Typo's are bad and should be vanquished
Conditionally install 2.6 python requirements
separate pip requirements file for python2.6
Added missing 'skipped' field for no_log
Obey no_log even more when using ansible 2.0
bump shade from 0.5.0 to 1.4
RHEL5 compatibility and handling of error scenarios
...
* release_2.4.4: (35 commits)
Update changelog for 2.4.4 release
Make pycompile non-fatal during deb build
Revert "Add virtualenv site-pagkages to Python path before system dist-packages, to get new setuptools"
Roll back mock version due to packaging issues
Add virtualenv site-pagkages to Python path before system dist-packages, to get new setuptools
change to warning behavior
Resolve bug when building with /bin/sh on Ubuntu
Attempt to workaround pip install issue
point at packages with source on pypi
Mock requires a newer setuptools when building requirements
requests needs openssl
Properly set the shell during directory migration
pyrax bumpb new python license
Typo's are bad and should be vanquished
Conditionally install 2.6 python requirements
separate pip requirements file for python2.6
Added missing 'skipped' field for no_log
Obey no_log even more when using ansible 2.0
bump shade from 0.5.0 to 1.4
RHEL5 compatibility and handling of error scenarios
...
* Implement concrete Notification model for notification runs
* Implement NotificationTemplate and Notification serializers and views
* Implement ancillary views
* Implement NotificationTemplate trigger m2m fields on all job templates
via a fields mixin
* Link NotificationTemplates with an org
* Link notifications with the activity stream
* Implement Notification celery tasks
* Extend Backend field parameters to identify sender and receiver as
parameters needed by the message and not the backend itself
* Updates to backends to better fit the django email backend model as it
relates to Messages
* Implement success job chain task + notifications
* Implement notifications in error job chain task
Linking in a success callback that will be invoked by our UnifiedJobs in
the case they terminate normally. This is where we'll hook in the
success notification type.
* A basic NotificationTemplate model class with early notification type
definitions
* Initial implementations of the Email, Slack, and Twilio Notification
backends using the Django email backend system
* Some dependencies thereof
2.4.0 level of rax.py introduces a default cache timeout of 600s, this
fixes that and includes a new rax.py inventory module that has been
submitted upstream.
We pre-create some cleanup jobs if a license is already present, this
doesn't work with the database config as-is. These can be removed at
some point in the future once the 2.4 migration path is not needed
Matthew Jones