Ryan Petrello f850f8d3e0 introduce a new global flag for denoating K8S-based deployments ...

- In K8S-based installs, only container groups are intended to be used
  for playbook execution (JTs, adhoc, inventory updates), so in this
  scenario, other job types have a task impact of zero.
- In K8S-based installs, traditional instances have *zero* capacity
  (because they're only members of the control plane where services
  - http/s, local control plane execution - run)
- This commit also includes some changes that allow for the task manager
  to launch tasks with task_impact=0 on instances that have capacity=0
  (previously, an instance with zero capacity would never be selected
  as the "execution node"

This means that when IS_K8S=True, any Job Template associated with an
Instance Group will never actually go from pending -> running (because
there's no capacity - all playbooks must run through Container Groups).
For an improved ux, our intention is to introduce logic into the
operator install process such that the *default* group that's created at
install time is a *Container Group* that's configured to point at the
K8S cluster where awx itself is deployed.

2021-03-03 18:52:55 -05:00

..

__init__.py

fixed copyright date

2015-06-11 16:10:23 -04:00

defaults.py

introduce a new global flag for denoating K8S-based deployments

2021-03-03 18:52:55 -05:00

development_quiet.py

remove statsd

2016-05-10 11:56:04 -04:00

development.py

Set SDB_NOTIFY_HOST for all processes

2021-03-03 18:52:54 -05:00

minikube.py

Minikube-based development environment

2021-01-25 18:03:17 -05:00

production.py

consolidate settings and delete dead settings

2021-01-05 13:02:25 -05:00