blob: a63bd7fd135ae392ad4c240f26398ca806c8b70a [file] [log] [blame]
peustermcbcd4c22015-12-28 11:33:42 +01001"""
2This is an example topology for the distributed cloud emulator (dcemulator).
3(c) 2015 by Manuel Peuster <manuel.peuster@upb.de>
4
peusterme4e89d32016-01-07 09:14:54 +01005
6This is an example that shows how a user of the emulation tool can
7define network topologies with multiple emulated cloud data centers.
8
9The definition is done with a Python API which looks very similar to the
10Mininet API (in fact it is a wrapper for it).
11
12We only specify the topology *between* data centers not within a single
13data center (data center internal setups or placements are not of interest,
14we want to experiment with VNF chains deployed across multiple PoPs).
15
peustermcbcd4c22015-12-28 11:33:42 +010016The original Mininet API has to be completely hidden and not be used by this
17script.
18"""
19import logging
peustermd47ab252016-01-15 10:35:06 +010020from mininet.log import setLogLevel
cgeoffroy9524ad32016-03-03 18:24:15 +010021from emuvim.dcemulator.net import DCNetwork
peusterm9c252b62016-01-06 16:59:53 +010022from api.zerorpcapi import ZeroRpcApiEndpoint
stevenvanrossem8fbf9782016-02-17 11:40:23 +010023from api.zerorpcapi_DCNetwork import ZeroRpcApiEndpointDCNetwork
peustermcbcd4c22015-12-28 11:33:42 +010024
peustermbd44f4a2016-01-13 14:53:30 +010025logging.basicConfig(level=logging.INFO)
peustermcbcd4c22015-12-28 11:33:42 +010026
27
28def create_topology1():
peusterme4e89d32016-01-07 09:14:54 +010029 """
30 1. Create a data center network object (DCNetwork)
31 """
peustermcbcd4c22015-12-28 11:33:42 +010032 net = DCNetwork()
33
peusterme4e89d32016-01-07 09:14:54 +010034 """
stevenvanrossem58bd1f22016-02-17 11:09:04 +010035 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()
stevenvanrossem58bd1f22016-02-17 11:09:04 +010040 """
peusterme4e89d32016-01-07 09:14:54 +010041 2. Add (logical) data centers to the topology
42 (each data center is one "bigswitch" in our simplified
43 first prototype)
44 """
peusterma47db032016-02-04 14:55:29 +010045 dc1 = net.addDatacenter("datacenter1")
46 dc2 = net.addDatacenter("datacenter2")
peusterm53504942016-02-04 16:09:28 +010047 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"})
peusterme4e89d32016-01-07 09:14:54 +010051
52 """
53 3. You can add additional SDN switches for data center
54 interconnections to the network.
55 """
peustermcbcd4c22015-12-28 11:33:42 +010056 s1 = net.addSwitch("s1")
peusterme4e89d32016-01-07 09:14:54 +010057
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 """
peustermcbcd4c22015-12-28 11:33:42 +010063 net.addLink(dc1, dc2)
peusterma47db032016-02-04 14:55:29 +010064 net.addLink("datacenter1", s1)
65 net.addLink(s1, dc3)
66 net.addLink(s1, "datacenter4")
peusterm9c252b62016-01-06 16:59:53 +010067
peusterme4e89d32016-01-07 09:14:54 +010068 """
69 5. We want to access and control our data centers from the outside,
peusterm5b844a12016-01-11 15:58:15 +010070 e.g., we want to connect an orchestrator to start/stop compute
peusterme4e89d32016-01-07 09:14:54 +010071 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
peusterm9c252b62016-01-06 16:59:53 +010079 zapi1 = ZeroRpcApiEndpoint("0.0.0.0", 4242)
peusterme4e89d32016-01-07 09:14:54 +010080 # connect data centers to this endpoint
peusterm9c252b62016-01-06 16:59:53 +010081 zapi1.connectDatacenter(dc1)
82 zapi1.connectDatacenter(dc2)
peusterm53504942016-02-04 16:09:28 +010083 zapi1.connectDatacenter(dc3)
84 zapi1.connectDatacenter(dc4)
peusterme4e89d32016-01-07 09:14:54 +010085 # run API endpoint server (in another thread, don't block)
peusterm9c252b62016-01-06 16:59:53 +010086 zapi1.start()
peusterme4e89d32016-01-07 09:14:54 +010087
88 """
89 5.1. For our example, we create a second endpoint to illustrate that
peustermeecafde2016-01-15 10:23:26 +010090 this is supported by our design. This feature allows us to have
peusterme4e89d32016-01-07 09:14:54 +010091 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 """
peusterm9c252b62016-01-06 16:59:53 +010097 zapi2 = ZeroRpcApiEndpoint("0.0.0.0", 4343)
98 zapi2.connectDatacenter(dc3)
99 zapi2.connectDatacenter(dc4)
100 zapi2.start()
101
peusterme4e89d32016-01-07 09:14:54 +0100102 """
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 """
peustermcbcd4c22015-12-28 11:33:42 +0100109 net.start()
peusterme4e89d32016-01-07 09:14:54 +0100110 net.CLI()
111 # when the user types exit in the CLI, we stop the emulator
112 net.stop()
peustermcbcd4c22015-12-28 11:33:42 +0100113
114
115def main():
peustermd47ab252016-01-15 10:35:06 +0100116 setLogLevel('info') # set Mininet loglevel
peustermcbcd4c22015-12-28 11:33:42 +0100117 create_topology1()
118
119
120if __name__ == '__main__':
121 main()