csa/devops/ansible-patches/openshift.git/docs/proposals, branch andsUnnamed repository; edit this file 'description' to name the repository.
http://de.suren.me/cgit/csa/devops/ansible-patches/openshift.git/atom?h=ands2018-01-05T17:44:56+00:00Migrate to import_role for static role inclusion2018-01-05T17:44:56+00:00Scott Dodsonsdodson@redhat.com2018-01-05T17:44:56+00:00urn:sha1:eacc12897ca86a255f89b8a4537ce2b7004cf319
In Ansible 2.2, the include_role directive came into existence as
a Tech Preview. It is still a Tech Preview through Ansible 2.4
(and in current devel branch), but with a noteable change. The
default behavior switched from static: true to static: false
because that functionality moved to the newly introduced
import_role directive (in order to stay consistent with include*
being dynamic in nature and `import* being static in nature).
The dynamic include is considerably more memory intensive as it will
dynamically create a role import for every host in the inventory
list to be used. (Also worth noting, there is at the time of this
writing an object allocation inefficiency in the dynamic include
that can in certain situations amplify this effect considerably)
This change is meant to mitigate the pressure on memory for the
Ansible control host.
We need to evaluate where it makes sense to dynamically include roles
and revert back to dynamic inclusion if and where it makes sense to do
so.
Remove all uses of openshift.common.admin_binary2017-12-07T14:51:54+00:00Scott Dodsonsdodson@redhat.com2017-12-07T14:14:49+00:00urn:sha1:13ca9bbd624b334cab6a7403764e9bba110fc8b3
Replace with `oc adm`
Proposal: container_runtime role2017-11-07T21:06:56+00:00Michael Guginomgugino@redhat.com2017-11-07T21:06:56+00:00urn:sha1:7eb4c906dc84c7018161367004e4037d37902611
This is a proposal meant to facilitate discussion.
Input is welcome.
Use "requests" for CPU resources instead of limits2017-10-19T15:02:14+00:00Peter Portantepeter.portante@redhat.com2017-10-13T15:04:49+00:00urn:sha1:578ac5b348fa3e9c7d0d05e3a0f579839ecd79dd
We now use a CPU request to ensure logging infrastructure pods are
not capped by default for CPU usage. It is still important to ensure
we have a minimum amount of CPU.
We keep the use of the variables *_cpu_limit so that the existing
behavior is maintained.
Note that we don't want to cap an infra pod's CPU usage by default,
since we want to be able to use the necessary resources to complete
it's tasks.
Bug 1501960 (https://bugzilla.redhat.com/show_bug.cgi?id=1501960)
Merge pull request #5322 from mtnbikenc/proposal-playbook-consolidation2017-09-20T15:14:30+00:00Scott Dodsonsdodson@redhat.com2017-09-20T15:14:30+00:00urn:sha1:4f5839e585a78243eae2d215176047299c52a1eb
[Proposal] OpenShift-Ansible Playbook ConsolidationRework openshift-cluster into deploy_cluster.yml2017-09-13T18:50:32+00:00Russell Teaguerteague@redhat.com2017-09-13T18:50:32+00:00urn:sha1:a96463d1402599b006272b2fbd8312ba55f302ed[Proposal] OpenShift-Ansible Proposal Process2017-09-11T18:28:55+00:00Russell Teaguerteague@redhat.com2017-09-06T19:58:46+00:00urn:sha1:240d66b067b783360ccade19ba245ab951d1d208[Proposal] OpenShift-Ansible Playbook Consolidation2017-09-06T19:57:05+00:00Russell Teaguerteague@redhat.com2017-09-06T19:57:05+00:00urn:sha1:d17fe01a857fb7d5b6e7055a96e0cb2cab852857Adding some more sections to additional considerations, being less rigid on large roles for composing -- can also be a playbook2017-04-27T21:48:11+00:00ewolinetzewolinet@redhat.com2017-04-27T21:48:11+00:00urn:sha1:bb9d1bd8af41c79586eb1c5d7b4f75932b632442Updating snippet contents, formatting and providing urls2017-04-21T20:49:38+00:00ewolinetzewolinet@redhat.com2017-04-20T23:59:57+00:00urn:sha1:66f18efad7176eb4f1ad1926a9a3b5d96aa72e2f