|
| 1 | +CoreOS-Vagrant Cluster GUI for OS X |
| 2 | +============================ |
| 3 | + |
| 4 | +CoreOS-Vagrant Cluster GUI for Mac OS X is a Mac Status bar App which works like a wrapper around the [coreos-vagrant](https://github.com/coreos/coreos-vagrant) command line tool and bootstraps CoreOS cluster with one control (etcd) and two worker machines. Flannel network is set too. |
| 5 | + |
| 6 | +Supports etcd2 in all CoreOS release channels. |
| 7 | + |
| 8 | +####Note: OS X El Capitan: |
| 9 | + |
| 10 | +* If you do a fresh install OS X El Capitan support will be enabled |
| 11 | + |
| 12 | +* Otherwise run: `ln -s /opt/vagrant/bin/vagrant /usr/local/bin/vagrant >/dev/null 2>&1` |
| 13 | + |
| 14 | + |
| 15 | + |
| 16 | +[CoreOS](https://coreos.com) is a Linux distribution made specifically to run [Docker](https://www.docker.io/) containers. |
| 17 | +[CoreOS-Vagrant](https://github.com/coreos/coreos-vagrant) is made to run on VirtualBox and VMWare VMs. |
| 18 | + |
| 19 | + |
| 20 | + |
| 21 | +Download |
| 22 | +-------- |
| 23 | +Head over to the [Releases Page](https://github.com/rimusz/coreos-osx-gui-cluster/releases) to grab the latest release. |
| 24 | + |
| 25 | + |
| 26 | +How to install |
| 27 | +---------- |
| 28 | + |
| 29 | +Required software |
| 30 | +* [VirtualBox](https://www.virtualbox.org/wiki/Downloads), [Vagrant](http://www.vagrantup.com/downloads.html) and [iTerm 2](http://www.iterm2.com/#/section/downloads) |
| 31 | + |
| 32 | +* Download `CoreOS Cluster GUI latest.zip` from the [Releases Page](https://github.com/rimusz/coreos-osx-gui-cluster/releases) and unzip it. |
| 33 | +* Start the `CoreOS Cluster GUI` and from menu `Setup` choose `Initial setup of CoreOS-Vagrant Cluster` |
| 34 | +* The install will do the following: |
| 35 | +```` |
| 36 | +1) All dependent files/folders will be put under 'coreos-osx-cluster' folder in the user's |
| 37 | + home folder e.g '/Users/someuser/coreos-osx-cluster' |
| 38 | +2) Will clone latest coreos-vagrant from git |
| 39 | +3) user-data file will have fleet, etcd and 'reboot off' set |
| 40 | +4) control (etcd) machine will be set with IP `172.17.9.101` and two cluster nodes with IPs: `172.17.9.102 and 172.17.9.103` |
| 41 | +5) Will download and install fleetctl and etcdctl clients to ~/coreos-osx-cluster/bin/ |
| 42 | +6) Will download latest vagrant VBox and run vagrant up to initialise VM |
| 43 | +```` |
| 44 | + |
| 45 | +How it works |
| 46 | +------------ |
| 47 | + |
| 48 | +Just start `CoreOS Cluster GUI` application and you will find a small icon with the CoreOS logo with the (C) which means for cluster in the Status Bar. |
| 49 | + |
| 50 | +* There you can `Up`, `Suspend`, `Halt`, `Reload` CoreOS vagrant VMs |
| 51 | +* Under `Up' and 'OS shell` OS Shell will have such environment set: |
| 52 | +```` |
| 53 | +1) Path to ~/coreos-osx-cluster/bin where etcdclt and fleetctl binaries are stored |
| 54 | +2) etcd endpoint - export ETCDCTL_PEERS=http://172.17.9.101:4001 |
| 55 | +3) fleetctl endpoint - export FLEETCTL_ENDPOINT=http://172.17.9.101:4001 |
| 56 | +```` |
| 57 | + |
| 58 | +* `SSH to control-01 and node-01/02` menu options will open VM shells. |
| 59 | +* Updates/Update OS X fleetctl and etcdclt will update fleetctl, etcdclt clients to the same versions as CoreOS VMs run. |
| 60 | +* Updates/Force CoreOS update will be run sudo update_engine_client -update on each CoreOS VM. |
| 61 | +* Updates/Check updates for CoreOS vbox will update CoreOS VM vagrant box. |
| 62 | +* [Fleet-UI](http://fleetui.com) dashboard will show running fleet units and etc |
| 63 | + |
| 64 | + |
| 65 | +Other links |
| 66 | +----------- |
| 67 | +* A standalone CoreOS VM version of OS X App can be found here [CoreOS-Vagrant GUI](https://github.com/rimusz/coreos-osx-gui). |
| 68 | + |
| 69 | +* Kubernetes Cluster one CoreOS VM of OS X App can be found here [CoreOS-Vagrant Kubernetes Cluster GUI ](https://github.com/rimusz/coreos-osx-gui-kubernetes-cluster). |
0 commit comments