formatting fixes

Author: brtiller1

labs/coding-101-rest-basics-ga/5.md

@@ -2,9 +2,9 @@
 
 There are many HTTP clients that can help you quickly test web services.  These types of tools provide an easy way to construct and send requests to REST APIs, and to view the responses.  
 
-* Postman - <http://www.getpostman.com/>
-* Firefox RestClient - <https://addons.mozilla.org/en-US/firefox/addon/restclient/>
-* Command Line using curl  - <http://curl.haxx.se/docs/httpscripting.html#POST>
+* Postman - [http://www.getpostman.com/](http://www.getpostman.com/)
+* Firefox RestClient - [https://addons.mozilla.org/en-US/firefox/addon/restclient/](https://addons.mozilla.org/en-US/firefox/addon/restclient/)
+* Command Line using curl  - [http://curl.haxx.se/docs/httpscripting.html#POST](http://curl.haxx.se/docs/httpscripting.html#POST)
 * SOAPUI
 * Many IDEs have consoles for testing REST Services built in
 
@@ -46,7 +46,7 @@ You may need to accept the SSL certificate before calling the APIs in Postman.
 3. Click **Send**.
 4. Postman will send the request to the server, and the display the response.
 	* You can see the **Response Code** that is returned displayed here as '200' and is shown in the **Status** field.
-	* You can see the **JSON** response data that contains a 'serviceTicket' attribute. We've highlighted the value of the service ticket.  The actual value returned will most likely be different. **Copy and paste this value into a text file to use for the next steps!**<br/><br/>
+	* You can see the **JSON** response data that contains a **serviceTicket** attribute. We've highlighted the value of the service ticket.  The actual value returned will most likely be different. **Copy and paste this value into a text file to use for the next steps!**<br/><br/>
     ![](/posts/files/coding-101-rest-basics-ga/assets/images/postman3.png "Response")
 
 #### Congrats! You just made your first REST API call! ####

labs/coding-102-rest-python-ga/1.md

@@ -39,11 +39,7 @@ Completion Time: 35 minutes
 * **If you are working on a DevNet Learning Lab PC at a DevNet event**,
     * Open the Git Command window by clicking on the *Git CMD* icon on the Task Bar or click on the Start button, then in the Run bar type: **git cmd** and press the **Enter** key.
 * **If you are working from your own workstation**, on your desktop open a command terminal.
-* Go to the root directory by typing: `cd \`
-* Create a directory called 'C:\DevNetCode\yourname' by typing: `mkdir DevNetCode\<your-name>`
-    * For example: `mkdir DevNetCode\brTiller`
-* Go to the new directory by typing: `cd \DevNetCode\<your-name>`
-    * For example: `cd \DevNetCode\brTiller`
+![](/posts/files/coding-102-rest-python-ga/assets/images/create_directory.png)<br/><br/>
 * Clone the coding skills sample code from GitHub.  Enter the command below.
 ```
 git clone https://github.com/CiscoDevNet/coding-skills-sample-code

labs/coding-102-rest-python-ga/3.md

@@ -5,7 +5,7 @@ We are going to build on the previous simple example, and learn how to parse and
 These files are located on your workstation in the directory: /DevNetCode/<your-name>/coding-skills-sample-code/coding102-REST-python-ga/
 * **create-ticket.py** - Example to create a service ticket. Used in Step 2.
 * **get-network-hosts.py** – First application to parse the service ticket response and show list of hosts by doing a pretty print of the JSON data
-* **get-network-devices.py** – Retrieves network device list and parses JSON to display networkDeviceId values
+* **get-network-devices.py** – Retrieves network device list and parses JSON to display **networkDeviceId** values
 * **build-topology.py** – Shows how to retrieve devices and interfaces, and to build and display spreadsheet-like text topology
 * **build-topology-web-server.py** – Shows how to retrieve devices and interfaces, and to build a graphical topology
 

labs/coding-102-rest-python-ga/4.md

@@ -67,20 +67,20 @@ getNetworkDevices(theTicket)
 
 Let's look at what the code is doing.  We'll focus on the key code changes.
 
-* *def getTicket():*
-    * We define the function named getTicket.  This function creates and returns the service ticket.
-* *def getNetworkDevices(ticket):*
-    * We define the function named getNetworkDevices which uses the parameter ticket.  The ticket parameter should contain the service ticket data.  This function returns the network devices.
-* *url = "https://" + controller + "/api/v1/network-device"*
+* **def getTicket():**
+    * We define the function named `getTicket()`.  This function creates and returns the service ticket.
+* **def getNetworkDevices(ticket):**
+    * We define the function named `getNetworkDevices` which uses the parameter ticket.  The ticket parameter should contain the service ticket data.  This function returns the network devices.
+* **url = "https://" + controller + "/api/v1/network-device"**
     * Creates the URL to get the network devices by concatenating the strings.
-* *header = {"content-type": "application/json", "X-Auth-Token":ticket}*
+* **header = {"content-type": "application/json", "X-Auth-Token":ticket}**
     * HTTP header with the ticket data designated as "X-Auth-Token" for API authentication.
-* *for i in r_json["response"]: print(i["id"] + "   " + i["series"])*
+* **for i in r_json["response"]: print(i["id"] + "   " + i["series"])**
     * Parse the network data JSON data and print out the device ID and the device series name.
-* *theTicket=getTicket()*
-    * Call the getTicket() function and assign the service ticket data to the variable 'theTicket'.
-* *getNetworkDevices(theTicket)*
-    * Call the getNetworkDevices(theTicket) function and pass in the service ticket data in the 'theTicket' variable.
+* **theTicket=getTicket()**
+    * Call the `getTicket()` function and assign the service ticket data to the variable `theTicket`.
+* **getNetworkDevices(theTicket)**
+    * Call the `getNetworkDevices(theTicket)` function and pass in the service ticket data in the `theTicket` variable.
 
 To run this code sample:
 1. Go to directory **coding102-REST-python-ga**.  In the terminal type:
@@ -100,8 +100,8 @@ To run this code sample:
 ![](/posts/files/coding-102-rest-python-ga/assets/images/get-devices.png)
 
 ## Things to Try
-* Edit the function getNetworkDevices to display the management IP address and name of the location for each network device.
-* Write a new function called getHosts(theTicket) to get and display the network hosts.  See step 3 for the URL to use for retrieving host data.
+* Edit the function `getNetworkDevices` to display the management IP address and name of the location for each network device.
+* Write a new function called `getHosts(theTicket)` to get and display the network hosts.  See step 3 for the URL to use for retrieving host data.
 
 
 In the next section, we will learn how to build a network topology.

labs/coding-102-rest-python-ga/5.md

@@ -113,14 +113,14 @@ getTopology(theTicket)
 ```
 
 Let's look at what the code is doing.  We'll focus on the key code changes.
-* *def getTopology(theTicket):*
-    * We define the function named getTopology.  This function reads in the topology data.  It parses the nodes which are devices on the network and displays some information about them.  It also parses the link data which are interfaces that connect the nodes and displays information about how they connect the devices and their status. The passed in parameter 'theTicket' is used for authorization purposes.
-* *for n in r_json["response"]["nodes"]:*
+* **def getTopology(theTicket):**
+    * We define the function named `getTopology`.  This function reads in the topology data.  It parses the nodes which are devices on the network and displays some information about them.  It also parses the link data which are interfaces that connect the nodes and displays information about how they connect the devices and their status. The passed in parameter `theTicket` is used for authorization purposes.
+* **for n in r_json["response"]["nodes"]:**
     * We read the dictionary data for each node into n from which we will parse the data.
-* *if "platformId" in n:*
-    * Checking that the node data in n contains a 'platformId' key.  Some records don't have this key so different field data would need to be accessed.
-* *if "startPortName" in i:*
-    * Checking that the interface data in i contains a 'startPortName' key.  Some records don't have this key so different field data would need to be accessed.
+* **if "platformId" in n:**
+    * Checking that the node data in n contains a `platformId` key.  Some records don't have this key so different field data would need to be accessed.
+* **if "startPortName" in i:**
+    * Checking that the interface data in i contains a `startPortName` key.  Some records don't have this key so different field data would need to be accessed.
 
 
 To run this code sample:
@@ -142,9 +142,9 @@ To run this code sample:
 
 
 ## Things to Try
-* After running the script review the node data printed. Modify the source code by replacing the label key with another key such as role or nodeType.  Run the script again and determine the change of the data displayed.
+* After running the script review the node data printed. Modify the source code by replacing the label key with another key such as `role` or `nodeType`.  Run the script again and determine the change of the data displayed.
 * Review the printed topology data and determine how many host devices exist and to which devices they connect.
-* Starting from the cloud node, use the topology data provided to draw a picture of the first three layers of the topology. Hint: look for matching devices specified by the Label attribute.  For example, the cloud node connects to four devices with one device being Branch-Router1. Determine which devices Branch-Router1 connects to by finding it in the Label field of the topology data.  Then do the same steps for the other three devices.
+* Starting from the cloud node, use the topology data provided to draw a picture of the first three layers of the topology. Hint: look for matching devices specified by the Label attribute.  For example, the cloud node connects to four devices with one device being `Branch-Router1`. Determine which devices `Branch-Router1` connects to by finding it in the Label field of the topology data.  Then do the same steps for the other three devices.
 
 
 In the next section, we will learn how to use the NeXt UI toolkit and Flask to build a network topology and display it graphically

labs/coding-102-rest-python-ga/6.md

@@ -100,23 +100,23 @@ if __name__ == "__main__":
 ```
 
 Let's look at what the code is doing.  We'll focus on the key code changes.
-* *from flask import Flask*
+* **from flask import Flask**
     * From the flask python module imports the Flask object
-* *from flask import render_template, jsonify*
-    * From the flask python module imports a couple of functions which are render_template and jsonify.
-* *app = Flask(__name__)*
+* **from flask import render_template, jsonify**
+    * From the flask python module imports a couple of functions which are `render_template` and `jsonify`.
+* **app = Flask(__name__)**
     * Instanitates the Flask web application.
-* *@app.route("/")*
-    * Tags the function below it "def index()" and specifies that it is called as the default web page for the Flask web application variable 'app'.
-* *def index():*
-    * The index function that calls the Flask function render_template that loads the topology.html web page.
-* *@app.route("/api/topology")*
+* **@app.route("/")**
+    * Tags the function below it "def index()" and specifies that it is called as the default web page for the Flask web application variable `app`.
+* **def index():**
+    * The index function that calls the Flask function `render_template` that loads the `topology.html` web page.
+* **@app.route("/api/topology")**
     * Tags the function below it "def topology()" and is called by NeXt UI.  Identifies as web page for the Flask web application variable 'app'
-* *def topology():*
+* **def topology():**
     * Returns the network topology data in JSON format.
-* *if __name__ == "__main__":*
-    * Optional code that specifies that if this module is run, rather than just importing it and calling it's functions, that below this point is where the script should begin running.  Python typically knows already has this information, but this prevents any ambiguity.
-* *app.run()*
+* **if __name__ == "__main__":**
+    * Optional code that specifies that if this module is run, rather than just importing it and calling its functions, that below this point is where the script should begin running.  Python typically knows already has this information, but this prevents any ambiguity.
+* **app.run()**
     * Starts the Flask web application.
 
 

labs/coding-102-rest-python-ga/assets/images/create_directory.png

@@ -62,7 +62,7 @@ cd ~/Desktop
 ```
 python get-ap-xml.py
 ```
-Note: You may need to run the python command as <b>python3.4 get-ap-xml.py</b> on OS X to force using the 3.4 version of Python.  If you get any errors, verify the version of python being executed and double-check the code.
+Note: You may need to run the python command as **python3.4 get-ap-xml.py** on OS X to force using the 3.4 version of Python.  If you get any errors, verify the version of python being executed and double-check the code.
 <br/>
 <br/>
 7. When you run the Python script, you should get an screen full of XML data returned to the terminal.
@@ -74,4 +74,4 @@ Note: You may need to run the python command as <b>python3.4 get-ap-xml.py</b> o
 
 ----------
 
-By default, CMX will return the data in XML.  For this first step, this is what we want.  Let's clean up this data parse out something more specific in the next step.
+By default, CMX will return the data in XML.  For this first step, this is what we want.  Let's clean up this data parse out something more specific in the next step.

labs/coding-201-parsing-xml/1.md

@@ -41,9 +41,9 @@ It is still a formidable amount of text, but we can now see some of the structur
 
 ----------
 
-A key thing to notice is that there is a hierarchical structure to the returned data.  Notably, the XML element with the Tag name 'Floor' has sub-objects and those sub-object can have objects themselves.  For this exercise, we are interested in the collection of Access Points for this floor and, in particular, the name, Ethernet MAC Address, and IP Address of each Access Point.  There is other information returned, but the *name*, *ethMacAddress*, and *ipAddress* attributes of an element with a Tag of *AccessPoint* are what we are interested in.  
+A key thing to notice is that there is a hierarchical structure to the returned data.  Notably, the XML element with the Tag name 'Floor' has sub-objects and those sub-object can have objects themselves.  For this exercise, we are interested in the collection of Access Points for this floor and, in particular, the name, Ethernet MAC Address, and IP Address of each Access Point.  There is other information returned, but the **name**, **ethMacAddress**, and **ipAddress** attributes of an element with a Tag of **sAccessPoint** are what we are interested in.  
 
-Structurally, the XML elements are represented in the following order: 
+Structurally, the XML elements are represented in the following order:
 
 &lt;Floor&gt;<br/>
 &nbsp;&nbsp;&nbsp;&nbsp;&lt;Dimension /&gt;<br/>
@@ -53,7 +53,7 @@ Structurally, the XML elements are represented in the following order:
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;ApInterface /&gt;<br/>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;ApInterface /&gt;<br/>
 &nbsp;&nbsp;&nbsp;&nbsp;&lt;/AccessPoint&gt;<br/>
-        
+
 
 In the above description, the elements tagged as AccessPoint have sub-elements of MapCoordinate and ApInterface.  The AccessPoint element itself has XML attributes that can tell us the name of the Access Point and its MAC and IP addresses.  A full AccessPoint element from the data can look like this:
 ```
@@ -64,8 +64,3 @@ Where the Tag is "AccessPoint" and there are 6 Attributes: "apMode", "ethMacAddr
 If you are interested in looking over the complete reference of available map information from CMX, review the online documentation at [https://developer.cisco.com/site/cmx-mobility-services/documents/api-reference-manual/index.gsp#maps-api](https://developer.cisco.com/site/cmx-mobility-services/documents/api-reference-manual/index.gsp#maps-api "Online Documentation for CMX Maps API")
 
 Now that we have a better understanding of what the structure looks like, let's parse the data.
-
-
-
-
-

labs/coding-201-parsing-xml/2.md

@@ -1,8 +1,8 @@
-## Step 4. Getting XML Elements in Python 
+## Step 4. Getting XML Elements in Python
 
 ### Retrieving Elements by Tag Name
 
-Rather than manually evaluate each child in a series of nodes, Minidom offers functionality to extract a collection of elements by their tag name.  We can use the getElementsByTagName() method to return an array of elements.
+Rather than manually evaluate each child in a series of nodes, Minidom offers functionality to extract a collection of elements by their tag name.  We can use the `getElementsByTagName()` method to return an array of elements.
 
 1. In **get-ap-xml.py**, strip out what was inserted in Step 3 (everything between the print(xml) and response.close() lines) and insert the following in its place.  Again, be careful in maintaining the indentation.
 ```
@@ -38,9 +38,3 @@ When you run the Python script, you should get a very similar output to before w
 Using Python and Minidom, we have extracted specific information from CMX using the Element Tag name and were able to output only the data we were looking for from this CMX data.
 
 Let's move to the last step and learn about resources available to further your knowledge of parsing XML with Python.
-
-
-
-
-
-