Changes between Version 4 and Version 5 of PluggingIn
- Timestamp:
- Mar 20, 2012 1:43:34 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PluggingIn
v4 v5 9 9 Networking configuration can be found in the following places: 10 10 * TopDL: IP address, netmask, MAC address, VDE switch/port 11 * {{{/var/benito/config/route s/$HOSTNAME}}}: routes11 * {{{/var/benito/config/route/$HOSTNAME}}}: routes 12 12 13 13 Each interface on the experimental network will be assigned a VDE switch and port number. If your platform supports VDE natively, then you're done! … … 40 40 * {{{benito:vde_port}}} (switch port) 41 41 42 === Routes === 43 44 Route information is in {{{/var/benito/config/route/$HOSTNAME}}}. Benito provides a script for automatically setting up routes: 45 46 {{{ 47 /var/benito/launch/routes.py /var/benito/config [$HOSTNAME] 48 }}} 49 50 The hostname parameter is optional and will be auto-detected if it is not provided. 51 42 52 === Control Net === 43 53 44 TODO: info about requesting controlnet interfaces; bridging 54 FOREWORD: Control net bridging is currently a hack. It makes a lot of assumptions about the underlying platform (i.e., qemu) and many aspects of this are baked into the code. Best of luck.. 55 56 You'll probably want to bridge onto the control net if that makes sense for your platform. If you see yourself wanting to SSH to a VM running on your platform, this is for you. 57 58 Due to DETER's controlnet separation, you must explicitly request IPs/MACs from boss. The setup script {{{setup/15_control_net.py}}} handles these requisitions. You'll need to hack this file a bit. Sorry! 59 60 On pnodes which host vnodes, the controlnet interface is bridged with TAP controlnet interfaces of its children. The bridge is brought up by {{{launch/qemu/control_bridge.py}}}. This script is currently tailored to QEMU. To support new VM infrastructure this will need to be hacked on. 45 61 46 62 == File Systems ==