| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 1 | """ |
| 2 | This is an example topology for the distributed cloud emulator (dcemulator). |
| 3 | (c) 2015 by Manuel Peuster <manuel.peuster@upb.de> |
| 4 | |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 5 | |
| 6 | This is an example that shows how a user of the emulation tool can |
| 7 | define network topologies with multiple emulated cloud data centers. |
| 8 | |
| 9 | The definition is done with a Python API which looks very similar to the |
| 10 | Mininet API (in fact it is a wrapper for it). |
| 11 | |
| 12 | We only specify the topology *between* data centers not within a single |
| 13 | data center (data center internal setups or placements are not of interest, |
| 14 | we want to experiment with VNF chains deployed across multiple PoPs). |
| 15 | |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 16 | The original Mininet API has to be completely hidden and not be used by this |
| 17 | script. |
| 18 | """ |
| 19 | import logging |
| peusterm | d47ab25 | 2016-01-15 10:35:06 +0100 | [diff] [blame] | 20 | from mininet.log import setLogLevel |
| cgeoffroy | 9524ad3 | 2016-03-03 18:24:15 +0100 | [diff] [blame] | 21 | from emuvim.dcemulator.net import DCNetwork |
| peusterm | 9c252b6 | 2016-01-06 16:59:53 +0100 | [diff] [blame] | 22 | from api.zerorpcapi import ZeroRpcApiEndpoint |
| stevenvanrossem | 8fbf978 | 2016-02-17 11:40:23 +0100 | [diff] [blame] | 23 | from api.zerorpcapi_DCNetwork import ZeroRpcApiEndpointDCNetwork |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 24 | |
| peusterm | bd44f4a | 2016-01-13 14:53:30 +0100 | [diff] [blame] | 25 | logging.basicConfig(level=logging.INFO) |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 26 | |
| 27 | |
| 28 | def create_topology1(): |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 29 | """ |
| 30 | 1. Create a data center network object (DCNetwork) |
| 31 | """ |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 32 | net = DCNetwork() |
| 33 | |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 34 | """ |
| stevenvanrossem | 58bd1f2 | 2016-02-17 11:09:04 +0100 | [diff] [blame] | 35 | 1b. add a monitoring agent to the DCNetwork |
| 36 | """ |
| 37 | mon_api = ZeroRpcApiEndpointDCNetwork("0.0.0.0", 5151) |
| 38 | mon_api.connectDCNetwork(net) |
| 39 | mon_api.start() |
| stevenvanrossem | 58bd1f2 | 2016-02-17 11:09:04 +0100 | [diff] [blame] | 40 | """ |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 41 | 2. Add (logical) data centers to the topology |
| 42 | (each data center is one "bigswitch" in our simplified |
| 43 | first prototype) |
| 44 | """ |
| peusterm | a47db03 | 2016-02-04 14:55:29 +0100 | [diff] [blame] | 45 | dc1 = net.addDatacenter("datacenter1") |
| 46 | dc2 = net.addDatacenter("datacenter2") |
| peusterm | 5350494 | 2016-02-04 16:09:28 +0100 | [diff] [blame] | 47 | dc3 = net.addDatacenter("long_data_center_name3") |
| 48 | dc4 = net.addDatacenter( |
| 49 | "datacenter4", |
| 50 | metadata={"mydata": "we can also add arbitrary metadata to each DC"}) |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 51 | |
| 52 | """ |
| 53 | 3. You can add additional SDN switches for data center |
| 54 | interconnections to the network. |
| 55 | """ |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 56 | s1 = net.addSwitch("s1") |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 57 | |
| 58 | """ |
| 59 | 4. Add links between your data centers and additional switches |
| 60 | to define you topology. |
| 61 | These links can use Mininet's features to limit bw, add delay or jitter. |
| 62 | """ |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 63 | net.addLink(dc1, dc2) |
| peusterm | a47db03 | 2016-02-04 14:55:29 +0100 | [diff] [blame] | 64 | net.addLink("datacenter1", s1) |
| 65 | net.addLink(s1, dc3) |
| 66 | net.addLink(s1, "datacenter4") |
| peusterm | 9c252b6 | 2016-01-06 16:59:53 +0100 | [diff] [blame] | 67 | |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 68 | """ |
| 69 | 5. We want to access and control our data centers from the outside, |
| peusterm | 5b844a1 | 2016-01-11 15:58:15 +0100 | [diff] [blame] | 70 | e.g., we want to connect an orchestrator to start/stop compute |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 71 | resources aka. VNFs (represented by Docker containers in the emulated) |
| 72 | |
| 73 | So we need to instantiate API endpoints (e.g. a zerorpc or REST |
| 74 | interface). Depending on the endpoint implementations, we can connect |
| 75 | one or more data centers to it, which can then be controlled through |
| 76 | this API, e.g., start/stop/list compute instances. |
| 77 | """ |
| 78 | # create a new instance of a endpoint implementation |
| peusterm | 9c252b6 | 2016-01-06 16:59:53 +0100 | [diff] [blame] | 79 | zapi1 = ZeroRpcApiEndpoint("0.0.0.0", 4242) |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 80 | # connect data centers to this endpoint |
| peusterm | 9c252b6 | 2016-01-06 16:59:53 +0100 | [diff] [blame] | 81 | zapi1.connectDatacenter(dc1) |
| 82 | zapi1.connectDatacenter(dc2) |
| peusterm | 5350494 | 2016-02-04 16:09:28 +0100 | [diff] [blame] | 83 | zapi1.connectDatacenter(dc3) |
| 84 | zapi1.connectDatacenter(dc4) |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 85 | # run API endpoint server (in another thread, don't block) |
| peusterm | 9c252b6 | 2016-01-06 16:59:53 +0100 | [diff] [blame] | 86 | zapi1.start() |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 87 | |
| 88 | """ |
| 89 | 5.1. For our example, we create a second endpoint to illustrate that |
| peusterm | eecafde | 2016-01-15 10:23:26 +0100 | [diff] [blame] | 90 | this is supported by our design. This feature allows us to have |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 91 | one API endpoint for each data center. This makes the emulation |
| 92 | environment more realistic because you can easily create one |
| 93 | OpenStack-like REST API endpoint for *each* data center. |
| 94 | This will look like a real-world multi PoP/data center deployment |
| 95 | from the perspective of an orchestrator. |
| 96 | """ |
| peusterm | 9c252b6 | 2016-01-06 16:59:53 +0100 | [diff] [blame] | 97 | zapi2 = ZeroRpcApiEndpoint("0.0.0.0", 4343) |
| 98 | zapi2.connectDatacenter(dc3) |
| 99 | zapi2.connectDatacenter(dc4) |
| 100 | zapi2.start() |
| 101 | |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 102 | """ |
| 103 | 6. Finally we are done and can start our network (the emulator). |
| 104 | We can also enter the Mininet CLI to interactively interact |
| 105 | with our compute resources (just like in default Mininet). |
| 106 | But we can also implement fully automated experiments that |
| 107 | can be executed again and again. |
| 108 | """ |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 109 | net.start() |
| peusterm | e4e89d3 | 2016-01-07 09:14:54 +0100 | [diff] [blame] | 110 | net.CLI() |
| 111 | # when the user types exit in the CLI, we stop the emulator |
| 112 | net.stop() |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 113 | |
| 114 | |
| 115 | def main(): |
| peusterm | d47ab25 | 2016-01-15 10:35:06 +0100 | [diff] [blame] | 116 | setLogLevel('info') # set Mininet loglevel |
| peusterm | cbcd4c2 | 2015-12-28 11:33:42 +0100 | [diff] [blame] | 117 | create_topology1() |
| 118 | |
| 119 | |
| 120 | if __name__ == '__main__': |
| 121 | main() |