
According to restructuredtext guidelines, directives should have following formatting: .. directive_name:: param :option: body So it starts with the leading two dots and the space. Next directive name follows with two colons, and finally optional parameter. Than, line below it is either some options delimited with colons, or an empty line. After which body of the directive follows. It should be positioned just at the same column as directive name, so exactly 3 spaces. Most of the directives are formatted wrong, including: - note - image - todo - toctree - warning - figure This patch fixes that. Change-Id: Ic970f72aeb93bcda82f02e57b70370ab79d6855d
1.5 KiB
1.5 KiB
How to try out nested-pods locally (MACVLAN)
Following are the instructions for an all-in-one setup, using the nested MACVLAN driver rather than VLAN and trunk ports.
- To install OpenStack services run devstack with
devstack/local.conf.pod-in-vm.undercloud.sample
. - Launch a Nova VM with MACVLAN support
Add a list of neutron commands, required to launch a such a VM
- Log into the VM and set up Kubernetes along with Kuryr using devstack:
-
- Since undercloud Neutron will be used by pods, Neutron services should be disabled in localrc.
- Run devstack with
devstack/local.conf.pod-in-vm.overcloud.sample
. Fill in the needed information, such as the subnet pool id to use or the router.
Once devstack is done and all services are up inside VM. Next steps are to configure the missing information at
/etc/kuryr/kuryr.conf
:Configure worker VMs subnet:
[pod_vif_nested] worker_nodes_subnet = <UNDERCLOUD_SUBNET_WORKER_NODES_UUID>
Configure "pod_vif_driver" as "nested-macvlan":
[kubernetes] pod_vif_driver = nested-macvlan
Configure binding section:
[binding] link_iface = <VM interface name eg. eth0>
Restart kuryr-k8s-controller:
sudo systemctl restart devstack@kuryr-kubernetes.service
Now launch pods using kubectl, Undercloud Neutron will serve the networking.