github-personal/matchbox
1
0
Fork 0
mirror of https://github.com/outbackdingo/matchbox.git synced 2026-01-27 10:19:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Add Debian/Ubuntu docs in rkt and Docker starter tutorials

Browse Source
This commit is contained in:
Dalton Hubble
2016-02-24 10:05:26 -08:00
parent fce6cacfef
commit 48f507ba0d
3 changed files with 30 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/getting-started-docker.md
View File

@@ -8,21 +8,27 @@ In this tutorial, we'll run `bootcfg` to boot and provision a cluster of four VM
## Requirements
Install the dependencies.
Install the dependencies and start the Docker daemon.
sudo dnf install virt-install docker virt-manager
# Fedora
sudo dnf install docker virt-install virt-manager
sudo systemctl start docker
# Debian/Ubuntu
# check Docker's docs to install Docker 1.8+ on Debian/Ubuntu
sudo apt-get install virt-manager virtinst qemu-kvm
Clone the [coreos-baremetal](https://github.com/coreos/coreos-baremetal) source which contains the examples and scripts.
git clone https://github.com/coreos/coreos-baremetal.git
cd coreos-baremetal
Create four VM nodes which have known hardware attributes. The nodes will be attached to the `docker0` bridge where your containers run.
Create four VM nodes which have known hardware attributes. The nodes will be attached to the `docker0` bridge where containers run.
sudo ./scripts/libvirt create-docker
sudo virt-manager
Download the CoreOS PXE image assets to `assets/coreos`. The examples instruct machines to load these from the Config server, though you could change this.
Download the CoreOS PXE image assets to `assets/coreos`. The examples instruct machines to load these from `bootcfg`.
./scripts/get-coreos
./scripts/get-coreos channel version
@@ -54,7 +60,7 @@ Reboot the VM machines and use `virt-manager` to watch the console.
At this point, the VMs will PXE boot and use Ignition (preferred over cloud config) to set up a three node etcd cluster, with other nodes behaving as etcd proxies.
On VMs with autologin, check etcd2 works between different nodes.
The example spec added autologin so you can check that etcd works between nodes.
systemctl status etcd2
etcdctl set /message hello

28
Documentation/getting-started-rkt.md
View File

@@ -6,18 +6,27 @@ In this tutorial, we'll run `bootcfg` to boot and provision a cluster of four VM
## Requirements
**Note**: Currently, rkt and the Fedora/RHEL/CentOS SELinux policies aren't supported. See the [issue](https://github.com/coreos/rkt/issues/1727) tracking the work and policy changes. To test these examples on your laptop, set SELinux enforcement to permissive if you are comfortable (`sudo setenforce 0`). Enable it again when you are finished.
Install [rkt](https://github.com/coreos/rkt/releases) and [acbuild](https://github.com/appc/acbuild/releases) from the latest releases. For rkt, see the setup and privilege separation [docs](https://coreos.com/rkt/docs/latest/trying-out-rkt.html). For acbuild:
Install [rkt](https://github.com/coreos/rkt/releases), [acbuild](https://github.com/appc/acbuild), and package dependencies.
tar xzvf acbuild.tar.gz
sudo ln -s /path/to/acbuild /usr/local/bin/acbuild
Install package dependencies.
# Fedora
sudo dnf install virt-install virt-manager
# Debian/Ubuntu
sudo apt-get install virt-manager virtinst qemu-kvm systemd-container
**Note**: Currently, rkt does not integrate with SELinux on Fedora. As a workaround, temporarily set enforcement to permissive if you are comfortable (`sudo setenforce Permissive`). Check the rkt [distribution notes](https://github.com/coreos/rkt/blob/master/Documentation/distributions.md) or track the [issue](https://github.com/coreos/rkt/issues/1727).
Clone the [coreos-baremetal](https://github.com/coreos/coreos-baremetal) source which contains the examples and scripts.
git clone https://github.com/coreos/coreos-baremetal.git
cd coreos-baremetal
Download the CoreOS PXE image assets to `assets/coreos`. The examples instruct machines to load these from the Config server, though you could change this.
Download the CoreOS PXE image assets to `assets/coreos`. The examples instruct machines to load these from `bootcfg`.
./scripts/get-coreos
./scripts/get-coreos channel version
@@ -25,6 +34,7 @@ Download the CoreOS PXE image assets to `assets/coreos`. The examples instruct m
Define the `metal0` virtual bridge with [CNI](https://github.com/appc/cni).
```bash
sudo mkdir -p /etc/rkt/net.d
sudo bash -c 'cat > /etc/rkt/net.d/20-metal.conf << EOF
{
"name": "metal0",
@@ -41,11 +51,14 @@ sudo bash -c 'cat > /etc/rkt/net.d/20-metal.conf << EOF
EOF'
```
On Fedora, add the `metal0` interface to the trusted zone in your firewall configuration.
sudo firewall-cmd --add-interface=metal0 --zone=trusted
## Application Container
Run `bootcfg` on the `metal0` network, with a known IP we'll have DNS point to.
sudo rkt trust --prefix quay.io/coreos
sudo rkt --insecure-options=image fetch docker://quay.io/coreos/bootcfg
Currently, the insecure flag is needed since Docker images do not support signature verification. We'll ship an ACI soon to address this.
@@ -67,13 +80,10 @@ Take a look at [etcd-rkt.yaml](../examples/etcd-rkt.yaml) to get an idea of how
Create four VM nodes which have known hardware attributes. The nodes will be attached to the `metal0` bridge where your pods run.
sudo ./scripts/libvirt create-rkt
sudo virt-manager
## Network
Add the `metal0` interface to the trusted zone in your firewall configuration.
sudo firewall-cmd --add-interface=metal0 --zone=trusted
Since the virtual network has no network boot services, use the `dnsmasq` ACI to create an iPXE network boot environment which runs DHCP, DNS, and TFTP. The `dnsmasq` container can help test different network setups.
Build the `dnsmasq.aci` ACI.
@@ -97,7 +107,7 @@ Reboot the VM machines and use `virt-manager` to watch the console.
At this point, the VMs will PXE boot and use Ignition (preferred over cloud config) to set up a three node etcd cluster, with other nodes behaving as etcd proxies.
On VMs with autologin, check etcd2 works between different nodes.
The example spec added autologin so you can check that etcd works between nodes.
systemctl status etcd2
etcdctl set /message hello

2
README.md
View File

@@ -8,8 +8,6 @@ CoreOS on Baremetal contains guides for network booting and configuring CoreOS c
## Guides
* [Network Booting](Documentation/network-booting.md)
* [Libvirt Guide](Documentation/virtual-hardware.md)
* [Baremetal Guide](Documentation/physical-hardware.md)
## bootcfg