updates due to sandbox changes

Author: brtiller1

labs/coding-101-rest-basics-ga/assets/images/ssl3.png

@@ -104,4 +104,4 @@ To run this code sample:
 * 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 manage APIC-EM Users.
+In the next section, we will learn how to build a network topology.

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

@@ -1,9 +1,9 @@
-# Step 5. Manage APIC-EM Users
+# Step 5. Build Network Topology
 
-In this step we're going to get the topology then parse the data to determine how devices link to one another and their status.
+In this step we're going to get the topology then parse the data to determine and display how devices link to one another and their link status.
 
 
-#### manage-users.py
+#### build-topology.py
 This sample code uses the application REST function call to retrieve a list of devices called nodes and links which are the interfaces that connect them. Our goal is to find the devices and display information about them and how they connect to other devices.
 
 
@@ -108,6 +108,11 @@ 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"]:*
+    * 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 in n contains a 'platformId' key.  Some records don't have this key which is the reason for the check.
+
 
 To run this code sample:
 1. Go to directory **coding102-REST-python-ga**.  In the terminal type:
@@ -128,6 +133,7 @@ To run this code sample:
 
 
 ## Things to Try
-* After running the script, review the node data printed. Replace the label attribute that is printed with another attribute such as role or nodeType. 
-* You may have noticed that no host devices are printed.  Review the data and the source code, and determine why this is so along with how you would print this data.
+* After running the script, review the node data printed. Replace the label attribute that is printed with another attribute such as role or nodeType.
+* You may have noticed that no host devices are printed.  Review the data and the source code, and determine why this is so along with how you would print this data. Hint: you can easily identify the host by its attribute nodeType or role.
 * Modify the source code so that host devices are printed as well.
+* Modify the source code so that interface connections to the hosts are printed as is currently done with the other network devices.

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

@@ -3,7 +3,7 @@ Often, when you are working with REST APIs (see [Coding 101: Rest Basics Learnin
 
 We can combine the techniques for writing to a file that we just learned with the techniques for calling REST APIs that we learned in [Coding 101 Calling REST APIs from Python](/#/labs/coding-101-rest-python/step/1)
 
-Let's take a look at an example that retrieves some JSON from the [APIC-EM APIs](https://anypoint.mulesoft.com/apiplatform/cisco-dev/#/portals/organizations/de91ddd1-9fb8-4731-8bce-03f47c3ba41a/apis/56056/versions/58124/pages/75870).
+Let's take a look at an example that retrieves some JSON from the [APIC-EM APIs](http://devnetapic.cisco.com).
 
 ```python
 # import the requests library so we can use it to make REST calls (http://docs.python-requests.org/en/latest/index.html)
@@ -15,10 +15,10 @@ import json
 
 # All of our REST calls will use the url for the APIC EM Controller as the base URL
 # So lets define a variable for the controller IP or DNS so we don't have to keep typing it
-controller_url = "https://sandboxapic.cisco.com:9443"
+controller_url = "https://sandboxapic.cisco.com"
 
 #the username and password to access the APIC-EM Controller
-payload = {"username":"admin","password":"C!sc0123"}
+payload = {"username":"devnetuser","password":"Cisco123!"}
 
 ticket_url = controller_url + "/api/v1/ticket"
 
@@ -77,8 +77,8 @@ To run this code sample:
     **cd \DevNetCode\<your-name>\coding-skills-sample-code\coding-205-writing-file-ga**
 2. Assign the APIC-EM Controller IP address or DNS to the **controller_url** variable.
     * Open the file **write-json-to-file.py**.  For example, in Windows type: **notepad write-json-to-file.py**
-    * *If you are not using your own APIC-EM Controller*, use the [DevNet Sandbox](https://developer.cisco.com/site/devnet/sandbox/) Always-On APIC-EM Lab: [sandboxapic.cisco.com:9443](https://sandboxapic.cisco.com:9443)
-        * controller_url='https://sandboxapic.cisco.com:9443'
+    * *If you are not using your own APIC-EM Controller*, use the [DevNet Sandbox](https://developer.cisco.com/site/devnet/sandbox/) Always-On APIC-EM Lab: [sandboxapic.cisco.com](https://sandboxapic.cisco.com)
+        * controller_url='https://sandboxapic.cisco.com'
 3. Save the file. If encoding type is an option select **UTF-8**.
 4. Type the python command and then the filename at the command prompt, and press the return key.
     * *On Windows type*: **py -3 write-json-to-file.py**.  Or type: **python write-json-to-file.py**

labs/coding-205-writing-file-ga/5.md

@@ -9,13 +9,13 @@ The following part of the code accomplishes these steps of the application:
 # Get Count of Devices
 # All of our REST calls will use the url for the APIC EM Controller as the base URL
 # So lets define a variable for the controller IP or DNS so we don't have to keep typing it
-controller_url = "https://sandboxapic.cisco.com:9443"
+controller_url = "https://sandboxapic.cisco.com"
 
 # put the ip address or dns of your apic-em controller in this url
 ticket_url = controller_url + '/api/v1/ticket'
 
 #the username and password to access the APIC-EM Controller
-payload = {"username":"admin","password":"C!sc0123"}
+payload = {"username":"devnetuser","password":"Cisco123!"}
 
 #Content type must be included in the header
 header = {"content-type": "application/json"}
@@ -63,7 +63,7 @@ logging.debug("API response: " + json.dumps(get_devices_json, indent=4, separato
 ```
 Let's look at what is going on in the code.
 
-* Using the [APIC-EM API Reference](https://anypoint.mulesoft.com/apiplatform/cisco-dev/#/portals/organizations/de91ddd1-9fb8-4731-8bce-03f47c3ba41a/apis/56056/versions/58124/pages/75870), we can see that the url **api/v1/ticket** will return the service ticket that's used to authorize calls to the APIC-EM APIs.  Like the other 'post' and 'get' calls it uses the Requests library to make a call to the APIC-EM Controller to retrieve the response data.
+* Using the [APIC-EM API Reference](http://devnetapic.cisco.com), we can see that the url **api/v1/ticket** will return the service ticket that's used to authorize calls to the APIC-EM APIs.  Like the other 'post' and 'get' calls it uses the Requests library to make a call to the APIC-EM Controller to retrieve the response data.
 * The url **api/v1/network-device/count** will return the total count of devices
 * This statement **devices_count_response = requests.get(devices_count_url, headers=header, verify=False)** makes the 'get' call to retrieve the device count.
 * **devices_count_response** will contain the response returned from the API
@@ -78,5 +78,5 @@ Let's look at what is going on in the code.
 
 
 ### Things to think about
-* What other APIC-EM APIs in the [APIC-EM API Reference](https://anypoint.mulesoft.com/apiplatform/cisco-dev/#/portals/organizations/de91ddd1-9fb8-4731-8bce-03f47c3ba41a/apis/56056/versions/58124/pages/75870) would you like to try?
+* What other APIC-EM APIs in the [APIC-EM API Reference](http://devnetapic.cisco.com) would you like to try?
 * Check out the [Coding 102: Calling REST APIs from Python Learning Lab](/#/labs/coding-102-rest-python/step/1) for more information on using the Requests library to make API calls.

labs/coding-207-putting-it-together-ga/3.md

@@ -53,7 +53,7 @@ requests.packages.urllib3.disable_warnings()
 
 
 # All of our REST calls will use the url for the APIC EM Controller as the base URL
-controller_url = "https://sandboxapic.cisco.com:9443"
+controller_url = "https://sandboxapic.cisco.com"
 
 #asks the user for the device type and logging file name
 def getUserInput():
@@ -86,7 +86,7 @@ def getTicket():
 	url = controller_url + "/api/v1/ticket"
 
 	#the username and password to access the APIC-EM Controller
-	payload = {"username":"admin","password":"C!sc0123"}
+	payload = {"username":"devnetuser","password":"Cisco123!"}
 
 	#Content type must be included in the header
 	header = {"content-type": "application/json"}
@@ -179,8 +179,8 @@ To run this code sample:
     **cd \DevNetCode\<your-name>\coding-skills-sample-code\coding207-putting-it-together-ga**
 2. Assign the APIC-EM Controller IP address or DNS to the **controller_url** variable.
     * Open the file **create-device-list.py**.  For example, in Windows type: **notepad create_device-list.py**
-    * *If you are not using your own APIC-EM Controller*, use the [DevNet Sandbox](https://developer.cisco.com/site/devnet/sandbox/) Always-On APIC-EM Lab: [sandboxapic.cisco.com:9443](https://sandboxapic.cisco.com:9443)
-        * controller_url='https://sandboxapic.cisco.com:9443'
+    * *If you are not using your own APIC-EM Controller*, use the [DevNet Sandbox](https://developer.cisco.com/site/devnet/sandbox/) Always-On APIC-EM Lab: [sandboxapic.cisco.com](https://sandboxapic.cisco.com)
+        * controller_url='https://sandboxapic.cisco.com'
 3. Save the file. If encoding type is an option select **UTF-8**.
 4. Type the python command and then the filename at the command prompt, and press the return key.
     * *On Windows type*: **py -3 create-device-list.py**.  Or type: **python create-device-list.py**