| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
|
|
| |
On nodes with thousands of services it may take a very long time to
establish all of the network routing rules. The longest we've seen is
about 180s
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Sometimes the node container is not started on a container-engine
restart. Use a weaker dependency on openvswitch that is causing this issue
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1451192
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
| |
|
|
|
|
|
|
|
| |
Adds service file templates for both maste and node. These will lay down
in /etc/system/systemd to override what may already be present from a
package. These instances take into account the name of the container
daemon (docker or container-engine).
|
|
|
|
|
|
|
| |
- If using a system container: container-engine
- If using a package install: docker
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1448800
|
|
|
|
| |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1427807
|
| |
|
|
|
|
|
| |
Add parameters to allow overriding minTLSVersion and
cipherSuites in master and node servingInfo config stanzas.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
around across node restart
With the move to a CNI plugin, docker no longer handles IPAM, but CNI does through
openshift-sdn's usage of the 'host-local' CNI IPAM plugin. That plugin stores
IPAM allocations under /var/lib/cni/.
If the node container gets restarted, without presreving /var/lib/cni, the IPs
currently allocated to running pods get lost and on restart, openshift-sdn
may allocate those IPs to new pods causing duplicate allocations.
This never happened with docker because it has its own persistent IPAM store that
does not get removed when docker restarts. Also because (historically) when docker
restarted, all the containers died and the IP allocations were released by the
daemon.
Fix this by ensuring that IPAM allocations (which are tied to the life of the pod,
*not* the life of the openshift-node process) persist even if the openshift-node
process restarts.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1427789
|
|
|
|
| |
into Openshift Ansible. This is the first (beta) release of Contiv with Openshift and is only supported for Openshift Origin + Bare metal deployments at the time of this commit. Please refer to the Openshift and Contiv official documentation for details of the level of support for different features and modes of operation.
|
| |
|
|\
| |
| | |
[#2698] Change to allow cni deployments without openshift SDN
|
| |
| |
| |
| |
| |
| |
| | |
The roles/openshift_facts main task did not pass the cni plugin variable to the later role playbooks.
The master.yaml and node.yaml templates did not allow for a cni configuration without either installing openshift sdn or nuage.
This change will allow to use os_sdn_network_plugin_name=cni and set openshift_use_openshift_sdn=false for deployments that use a cni plugin that doesn't need and want openshift sdn to be installed
|
|/ |
|
|
|
|
| |
This reverts commit 1f2276fff1e41c1d9440ee8b589042ee249b95d7.
|
|
|
|
|
|
| |
At recommendation of network team, more details in:
https://bugzilla.redhat.com/show_bug.cgi?id=1331590
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1367937
|
| |
|
|\
| |
| | |
1.3 / 3.3 Upgrades
|
| | |
|
| | |
|
|/ |
|
|\ |
|
| | |
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
Allows the use of arbitrary tags, precise control over containers and
rpms, and likely mixed environments.
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
* Conditionally bind mount /usr/bin/docker-current when it is present
* fix upgrade
* add atomic-openshift-node-dep files to uninstall playbook
* Fix variable expansion
|
|
|
|
|
| |
atomic-openshift-node.service file
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1336780
|
| |
|
|
|
|
| |
Lifted from https://github.com/openshift/origin/pull/8317
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are points where the docker service is restarted during
the install. Sometimes the services that are PartOf docker.service
do not get restarted when docker is restarted.
https://bugzilla.redhat.com/show_bug.cgi?id=1318948
Systemd documentation recommends using "wants" as the perferred
means of creating startup linkages between units. This
patch makes the ose services wanted by the docker service rather
than multi-user.target.
This creates a downward link from the docker service to the ose
containerized services.
|
|\
| |
| | |
Add /dev to node containers
|
| | |
|
|/
|
|
|
| |
Adds a new inventory var "openshift_node_local_quota_per_fsgroup", which will
set the perFSGroup quota node-config.yaml.
|
| |
|