| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
libvirt: Upgrade to CentOS-7-x86_64-GenericCloud-1602.
|
| | |
|
| |
| |
| |
| | |
which the checksum currently expects (#1384).
|
|\ \
| | |
| | | |
configure debug_level for master and node from cli
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Add missing is_atomic condition in the upgrade playbook
|
| | |
| | |
| | |
| | |
| | | |
* Update playbooks/common/openshift-cluster/upgrades/v3_1_minor/upgrade.yml
* Change is_atomic by is_containerized in order to take care about container openshift without atomic
|
| | |
| | |
| | |
| | |
| | | |
* Update playbooks/common/openshift-cluster/upgrades/v3_1_minor/upgrade.yml
* Add when not is_atomic on yum upgrade on master and node to be able to run the playbook on atomic host
|
|\ \ \
| | | |
| | | | |
remote heal action for OVS down
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Correct parsing of ec2_security_groups env variable
|
| | |/ /
| |/| | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Support for adding new masters
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
jdnieto/openstack_add_master_and_infra_to_node_security_group
Openstack add master and infra to node security group
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The variable's name for deleting the temporary file was a bit
missleading, so it has been renamed to be more explicit.
While the path was hardcoded in /root/, which could be problematic when
the playbook is not run as run.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It would be nice to have options to be able to:
* Delete or not the temporary config file - so that it can be check/modified directly
* Create or not the bucket, as you might not have the right to do so
This commit allows both of those things, without changing the default
behavior of the playbook.
|
|\ \ \
| |/ /
|/| | |
Apply openshift_docker to nodes during scaleup.
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Change etcd deamon name for atomic-host in playbooks/adhoc/uninstall.yml
|
| | |
| | |
| | |
| | |
| | |
| | | |
* Update playbooks/adhoc/uninstall.yml
* Etcd run into a container on atomic-host and his name is etcd_container.
We have to stop the container with the right name on atomic host
|
|\ \ \
| | | |
| | | | |
Bug 1308314 - Failed to continue installation when pressing CTRL-C
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Updating the 3.1.1 router to match the new liveness probe configuration
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Make the GCE image_name and the machine_type configurable from the CLI
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix issue when there are no infra nodes
|
| |/ / / / |
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Better structure the output of the list playbook
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The list playbook listed the IPs of the VMs without logging their role like:
```
PLAY [List instance(s)] *******************************************************
TASK: [debug ] ****************************************************************
ok: [lenaic-node-compute-cd81b] => {
"msg": "public ip: 104.155.50.164 private ip:10.55.0.49"
}
ok: [lenaic-master-9e767] => {
"msg": "public ip: 104.155.47.180 private ip:10.55.0.113"
}
ok: [lenaic-node-infra-ab7c8] => {
"msg": "public ip: 104.155.11.34 private ip:10.55.0.131"
}
```
The list playbook now prints the information in a more structured way like:
```
PLAY [List Hosts] *************************************************************
TASK: [debug ] ****************************************************************
ok: [localhost] => {
"msg": {
"lenaic": {
"master": {
"default": [
{
"name": "lenaic-master-9e767",
"private IP": "10.55.0.113",
"public IP": "104.155.47.180"
}
]
},
"node": {
"compute": [
{
"name": "lenaic-node-compute-cd81b",
"private IP": "10.55.0.49",
"public IP": "104.155.50.164"
}
],
"infra": [
{
"name": "lenaic-node-infra-ab7c8",
"private IP": "10.55.0.131",
"public IP": "104.155.11.34"
}
]
}
}
}
}
```
This change of the output of the list playbook was previously done for OpenStack and libvirt
in 332aa8c (#461).
This change makes the GCE output identical to OpenStack and libvirt’s one.
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix libvirt cluster creation
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Doing a `bin/cluster create libvirt …` fails with the following error:
```
TASK: [Warn user about bad openshift_hostname values] *************************
[lenaic-node-compute-cf3fb, lenaic-node-compute-f39d3, lenaic-node-infra-0407f, lenaic-master-fc5f9]
The hostname "lenaic-node-compute-cf3fb.example.com" for "lenaic-node-compute-cf3fb.example.com" doesn't resolve to an ip address owned by this host. Please set openshift_hostname variable to a hostname that when resolved on the host in question resolves to an IP address matching an interface on this host. This host will fail liveness checks for pods utilizing hostPorts, press CTRL-C to continue.:
```
because the `/etc/hosts` of the VM is containing:
```
[openshift@lenaic-node-compute-cf3fb ~]$ cat /etc/hosts
# Your system has configured 'manage_etc_hosts' as True.
# As a result, if you wish for changes to this file to persist
# then you will need to either
# a.) make changes to the master file in /etc/cloud/templates/hosts.redhat.tmpl
# b.) change or remove the value of 'manage_etc_hosts' in
# /etc/cloud/cloud.cfg or cloud-config from user-data
#
# The following lines are desirable for IPv4 capable hosts
127.0.0.1 lenaic-node-compute-cf3fb.example.com lenaic-node-compute-cf3fb
127.0.0.1 localhost.localdomain localhost
127.0.0.1 localhost4.localdomain4 localhost4
# The following lines are desirable for IPv6 capable hosts
::1 lenaic-node-compute-cf3fb.example.com lenaic-node-compute-cf3fb
::1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
```
Disabling `manage_etc_hosts` removes the lines for `lenaic-node-compute-cf3fb` from `/etc/hosts`
and makes than name resolved by the DNS to its real IP.
|
|/ / / |
|