openstack/openstack-helm
Code Issues Proposed changes
702c17eb78
openstack-helm/doc/source/install/developer/requirements-and-host-config.rst
Gage Hugo 39acd0967d Update OSH Installation Guide 
This change updates the requirements-and-host-config guide to include
proxy setup instructions as well as updating the ubuntu version to
include 18.04 as the reference linux flavor.

Also updated kubernetes-and-common-setup to include proxy and dns
configuration steps as well as header cleanup.

Change-Id: Ie075cdb7c32bcba5429abb9168ef7cc9b4845d89
2020-05-19 15:03:34 +00:00

3.2 KiB
Raw Blame History

Requirements and Host Configuration

Overview

Below are some instructions and suggestions to help you get started with a Kubeadm All-in-One environment on Ubuntu 18.04. Other supported versions of Linux can also be used, with the appropriate changes to package installation.

Requirements

System Requirements

The recommended minimum system requirements for a full deployment are:

  • 16GB of RAM
  • 8 Cores
  • 48GB HDD

For a deployment without cinder and horizon the system requirements are:

  • 8GB of RAM
  • 4 Cores
  • 48GB HDD

This guide covers the minimum number of requirements to get started.

All commands below should be run as a normal user, not as root. Appropriate versions of Docker, Kubernetes, and Helm will be installed by the playbooks used below, so there's no need to install them ahead of time.

Warning

By default the Calico CNI will use 192.168.0.0/16 and Kubernetes services will use 10.96.0.0/16 as the CIDR for services. Check that these CIDRs are not in use on the development node before proceeding, or adjust as required.

Host Configuration

OpenStack-Helm uses the hosts networking namespace for many pods including, Ceph, Neutron and Nova components. For this, to function, as expected pods need to be able to resolve DNS requests correctly. Ubuntu Desktop and some other distributions make use of mdns4_minimal which does not operate as Kubernetes expects with its default TLD of .local. To operate at expected either change the hosts line in the /etc/nsswitch.conf, or confirm that it matches:

hosts:          files dns

Host Proxy & DNS Configuration

Note

If you are not deploying OSH behind a proxy, skip this step.

Set your local environment variables to use the proxy information. This involves adding or setting the following values in /etc/environment:

export http_proxy="YOUR_PROXY_ADDRESS:PORT"
export https_proxy="YOUR_PROXY_ADDRESS:PORT"
export ftp_proxy="YOUR_PROXY_ADDRESS:PORT"
export no_proxy="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,172.17.0.1,.svc.cluster.local,$YOUR_ACTUAL_IP"
export HTTP_PROXY="YOUR_PROXY_ADDRESS:PORT"
export HTTPS_PROXY="YOUR_PROXY_ADDRESS:PORT"
export FTP_PROXY="YOUR_PROXY_ADDRESS:PORT"
export NO_PROXY="localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,172.17.0.1,.svc.cluster.local,$YOUR_ACTUAL_IP"

Note

Depending on your specific proxy, https_proxy may be the same as http_proxy. Refer to your specific proxy documentation.

Your changes to /etc/environment will not be applied until you source them:

source /etc/environment

OSH runs updates for local apt packages, so we will need to set the proxy for apt as well by adding these lines to `/etc/apt/apt.conf`:

Acquire::http::proxy "YOUR_PROXY_ADDRESS:PORT";
Acquire::https::proxy "YOUR_PROXY_ADDRESS:PORT";
Acquire::ftp::proxy "YOUR_PROXY_ADDRESS:PORT";

Note

Depending on your specific proxy, https_proxy may be the same as http_proxy. Refer to your specific proxy documentation.