Addressing comments -
1a. added flag to `sriov.sh` to indicate bind to vfio-pci
1b. systemd unit sets up two pools 1 per mode
2a. updated `sriov-conf.yaml` to use the two pools
3a. included network examples for both resource pools
3b. included pod examples for both resource pools
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Adding a cni to mirror MAC address of VF on a veth pair with results
from ipam applied to enable DPDK apps to configure themselves when
operating sriov-network-device-plugin in vfio mode
Updated helper sriov.sh to allow for binding VFs to vfio-pci on boot
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Avoid creating unique names for disks as vagrant-libvirt today does not
delete those images when VMs are deleted. Once that is fixed we can move
back to using unique names. Until then this should suffice.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
In case we need to exit early this would have copied the credentials
into the home dir
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Instead of mounting at /vagrant it will now be at /home/vagrant/clr-k8s-examples
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Instead of relying on configmap to be created/customized by the user to
generate multus conf, we autogenerate it using the current default CNI
conf file on the host. This way CNI's with host specific conf details
will continue to work.
```
{
"type": "calico",
"nodename": "clr-01",
...
}
```
Since SR-IOV device may not be present on all nodes, the daemonset
should not exit as this will put the pod in restart loop. This would
cause the kubelet and runtimes to repeatedly restart, as per
initContainer logic.
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Runtime class kata-qemu created and older kata point to kata-qemu
handler. Now all the handlers match the crio.conf settings.
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Keep `setup_firecracker.sh` separate and mark it experimental in README.
Fix modules load, needed to run k8s without reboot. Fix runtimeclass to
add fire.
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Initial support for firecracker configuration on Clearlinux.
This is a little bit complicated due to CRIO requiring a
disk or partition to use devicemapper.
Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
clearlinux-pkgs/kubernetes installs kubeadm kubelet of the same version
and kubeadm uses/fallsback to stable branch of its major+minor version when
generating kubernetes component manifests if none is provided. This
helps with staying upto date with any fixes without any further
modifications
```
vagrant@clr-01 ~ $ bash /vagrant/create_stack.sh
I1207 21:37:25.285850 16086 version.go:236] remote version is much newer: v1.13.0; falling back to: stable-1.12
[init] using Kubernetes version: v1.12.3
```
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Bolster some checks so we don't try to edit files that do not
exist (for proxy setup for instance).
Also replace the 'sudo tee' commands with 'sudo bash -c "cat >"'
commands to reduce the echoing of the output to stdout.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
We see kata logs with `SYSLOG_IDENTIFIER:kata-runtime` under
`_SYSTEMD_UNIT:crio.service` in kibana. Need to verify if this holds
good for `SYSLOG_IDENTIFIER=kata-proxy` and `SYSLOG_IDENTIFIER=kata-shim`
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Simple set of scripts and slightly modified upstream configurations
of various kubernetes services to setup a kubernetes cluster on
Clearlinux.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
Saikrishna Edupuganti