| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Cleanup not required dns bits
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Do not manage hostnames for openstack cloud provider,
let cloud-init to do its job.
* Make python-dns / dnspython dependency check conditional.
* Drop not used dns node flavor and image.
* Do not manage dns nodes and sec groups in heat stacks.
* Keep supporting dynamic updates for private DNS records, yet only
limited to an external DNS managed elsewhere (not deployed by
the openshift_openstack provider). So users may still benefit from
this feature, sending nsupdates to private and public servers as
they want it.
* Fix openstack default for external nsupdate keys. It should be
undefined by default as the dns-populate logic is based on that.
* Fix dns records generation for openstack provider's populate-dns
* Update docs
|
|/
|
|
|
|
|
| |
openshift.master.cluster_method.
With pacemaker removed there is no longer a need for
openshift.master.cluster_method. We only have one option.
|
|\
| |
| | |
Cleanup unused openstack provider code
|
| |
| |
| |
| |
| |
| |
| | |
Remove references for bastion, ssh UI tunnek and static inventory.
Update docs.
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
|
| |
| |
| |
| | |
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
|
|/
|
|
|
|
|
|
| |
Use testing openshift repos to sidestep packaging issues for 3.6 clients being
used in 3.7 deployments or something.
Poke host requirements Centos 7.4 as 7.3 can't see that testing repo.
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unlike other cloud providers, OpenStack VMs are not able to resolve each
other by their names. If you try to run the playbooks against nodes
without a pre-created /etc/hosts or a DNS that provides the hostname/ip
resolution, it will fail.
By setting the `openshift_hostname` variable to each node's IP address,
we're able to deploy a functional cluster without running a custom DNS.
It is still possible to provide an external server with nsupdate keys
and have it be populated, but that is no longer a hard requirement.
|
| |
|
| |
|
|
|
|
|
| |
This makes sure that all the variables used in the `openshift_openstack`
role are prefixed with `openshift_openstack_` as is the convention.
|
|
|
|
|
| |
Most of the vars in `roles/openshift_openstack/defaults/main.yml` are
now prefixed with `openstack_`.
|
|
|
|
|
| |
These options will have no effect until we add static inventory and
bastion support back in.
|
| |
|
| |
|
|
|
|
|
| |
They're not necessary for the initial PR so let's add them properly
later.
|
|
|
|
|
|
|
|
| |
They're duplicating a lot of functionality that's already in
openshift-ansible and they're not actually used from the provisioning
playbooks.
We'll revisit them later.
|
|
|
|
|
|
|
|
|
| |
All the tasks that were previously in playbooks are now under
`roles/openshift_openstack`.
The `openshift-cluster` directory now only contains playbooks that
include tasks from that role. This makes the structure much closer to
that of the AWS provider.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We move them from `playbooks/provisioning/openstack` to
`playbooks/openstack` to mirror `playbooks/aws`.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Added checks to make ci for yaml linting
* Modified y(a)ml files to pass lint checks
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `list.yml` playbooks are using cloud provider specific variables to find
the IPs of the VMs since 82449c6.
Those “cloud provider specific” variables are the ones provided by the dynamic
inventories.
But there was a problem when the `list.yml` playbooks are invoked from the
`launch.yml` ones because, in that case, the inventory is not coming from the
dynamic inventory scripts, but from the `add_host` done inside
`launch_instances.yml`.
Whereas the GCE and AWS `launch_instances.yml` were correctly adding in the
`add_host` the variables used by `list.yml`, libvirt and OpenStack were missing
that.
Fixes #2856
|
|\
| |
| | |
[openstack] allows timeout option for heat create stack
|
| | |
|
| |
| |
| |
| |
| |
| | |
by removing the need to gather facts on all VMs in order to list them.
And prettify the output of AWS list the same way it is done for other cloud providers.
|
| | |
|
|/
|
|
| |
This reverts commit aaaf82ba6032d0b1e9c36a39a7eda25b8c5f4b84.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Open OpenStack security group for the service node port range
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With OpenShift 3.2, creating a service accessible from the outside of the
cluster thanks to `nodePort` automatically opens the “local” `iptables`
firewall to allow incoming connection on the `nodePort` of the service.
In order to benefit from this improvement, the OpenStack security group
shouldn’t block those incoming connections.
This change opens, on the OS nodes, the port range dedicated to service
node ports.
|
|/
|
|
| |
Some expressions now need to be enclosed inside `{{…}}`.
|
| |
|
| |
|
|\
| |
| | |
Re-align the OpenStack firewall rules with the iptables rules
|
| | |
|
|/ |
|