You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,6 +75,22 @@ $ make run
75
75
* Configure local DNS. For a one-node cluster we do this for you: `local.deisapp.com` resolves to the IP of the first VM, 172.17.8.100. Since we cannot know where the `deis-router` container will be running in your cluster, you'll need to setup DNS and resolve a wildcard entry to use for your apps.
76
76
* Because of the DNS quandary, we don't start the deis-router component for you. You'll need to start this manually once DNS is setup: `systemctl start deis-router`.
77
77
78
+
## Testing the cluster
79
+
Logging into one of the CoreOS machines and stopping a container service should cause the same component on another CoreOS
80
+
host to take over as master
81
+
82
+
These systemd services run the various containers which compose Deis, and can be stopped on a machine with `sudo systemctl stop servicename`.
83
+
* deis-builder.service
84
+
* deis-cache.service
85
+
* deis-controller.service
86
+
* deis-database.service
87
+
* deis-discovery.service
88
+
* deis-logger.service
89
+
* deis-registry.service
90
+
* deis-router.service
91
+
92
+
Similarly, bringing down a VM should enable the services on another VM to take over as master
93
+
78
94
## Install the Deis Client
79
95
If you're using the latest Deis release, use `pip install deis` to install the latest [Deis Client](https://pypi.python.org/pypi/deis/) or download [pre-compiled binaries](https://github.com/deis/deis/tree/master/client#get-started).
80
96
@@ -150,22 +166,6 @@ $ deis run make test
150
166
151
167
To integrate with your CI system, check the return code.
152
168
153
-
### Testing the cluster
154
-
Logging into one of the CoreOS machines and stopping a container service should cause the same component on another CoreOS
155
-
host to take over as master
156
-
157
-
These systemd services run the various containers which compose Deis, and can be stopped on a machine with `sudo systemctl stop servicename`.
158
-
* deis-builder.service
159
-
* deis-cache.service
160
-
* deis-controller.service
161
-
* deis-database.service
162
-
* deis-discovery.service
163
-
* deis-logger.service
164
-
* deis-registry.service
165
-
* deis-router.service
166
-
167
-
Similarly, bringing down a VM should enable the services on another VM to take over as master
0 commit comments