CORD-1793 Complete Manage/Operate guide
Change-Id: I4a239cb7d204030e84330bfae1ec0caf945475e9
(cherry picked from commit b34450b8c41c218552e25221db51419903165d2a)
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
index 07397c1..1373266 100644
--- a/docs/SUMMARY.md
+++ b/docs/SUMMARY.md
@@ -13,9 +13,9 @@
* [Connecting to Upstream Networks](vrouter.md)
* [Build System Internals](build_internals.md)
* [Operating and Managing CORD](operate/README.md)
- * [Configuring XOS](xos/modules/xosconfig.md)
* [Powering Up a POD](operate/power_up.md)
- * [ELK Stack Logs](operate/elk_stack.md)
+# My understanding is that ELK Stack is not working right now
+# * [ELK Stack Logs](operate/elk_stack.md)
* [REST API](rest_apis.md)
* [TOSCA](xos-tosca/README.md)
* [Development Environment](xos-tosca/devel.md)
@@ -33,6 +33,7 @@
* [Workflow: local dev](xos/dev/local_env.md)
* [Workflow: Cord-in-a-Box](xos/dev/workflow_ciab.md)
* [Example Service](xos/example_service.md)
+ * [Configuring XOS](xos/modules/xosconfig.md)
* [GUI Development](xos-gui/developer/README.md)
* [Quickstart](xos-gui/developer/quickstart.md)
* [Tests](xos-gui/developer/tests.md)
diff --git a/docs/operate/power_up.md b/docs/operate/power_up.md
index 7826963..06596aa 100644
--- a/docs/operate/power_up.md
+++ b/docs/operate/power_up.md
@@ -7,9 +7,9 @@
## Boot the Head Node
* **Physical POD:** Power on the head node
-* **CiaB:** Bring up the prod VM:
+* **CiaB:** Bring up the head1 VM:
```
-$ cd ~/cord/build; vagrant up prod
+$ cd ~/cord/build; VAGRANT_CWD=~/cord/build/scenarios/cord vagrant up head1 --provider libvirt
```
## Check the Head Node Services
@@ -24,7 +24,7 @@
> Run `ps ax|grep 8080`
> and look for an SSH command (will look something like this):
```
-31353 pts/5 S 0:00 ssh -o User=vagrant -o Port=22 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PasswordAuthentication=no -o ForwardX11=no -o IdentityFile="/users/acb/cord/build/targets/cord-in-a-box/.vagrant/machines/prod/libvirt/private_key" -L *:8080:192.168.121.14:80 -N 192.168.121.14
+31353 pts/5 S 0:00 ssh -o User=vagrant -o Port=22 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PasswordAuthentication=no -o ForwardX11=no -o IdentityFile="/users/acb/cord/build/scenarios/cord/.vagrant/machines/head1/libvirt/private_key" -L *:8080:192.168.121.14:80 -N 192.168.121.14
```
> A workaround is to kill this process, and then copy and paste the command
> above into another window on the CiaB server to set up a new SSH port forwarding connection.
@@ -49,18 +49,16 @@
## Power on Leaf and Spine Switches
* **Physical POD:** power on the switches.
-* **CiaB:** bring up the switch VMs:
-```
-$ cd ~/cord/build; vagrant up leaf-1 leaf-2 spine-1
-```
+* **CiaB:** nothing to do; CiaB using OvS switches that come up when the CiaB server is booted.
## Check the Switches
-On the head node (i.e., prod VM for CiaB):
-
+* **Physical POD:** On the head node:
1. Get switch IPs by running: cord prov list
2. Verify that ping works for all switch IPs
+* **CiaB:** run `sudo ovs-vsctl show` on the CiaB server; you should see `leaf1` and `spine1`.
+
## Boot the Compute Nodes
* **Physical POD:** Log into the MAAS UI and power on the compute node.