| 1 | [[PageOutline]] |
| 2 | |
| 3 | = Rspec Extension Proposal to Enable Port Mapping = |
| 4 | |
| 5 | By Hussamuddin Nasir [nasir@netlab.uky.edu] [[BR]] |
| 6 | 4/3/12 [[BR]] |
| 7 | |
| 8 | |
| 9 | Attached is a sample rspec node and its manifest with the proposed extension. [[BR]] |
| 10 | |
| 11 | What i propose is that in a request rspec , the user also adds another tag called "rs:port" as shown below <node> <services> <rs:ports requested_port="80"> <rs:ports requested_port="169"> </services> </node> [[BR]] |
| 12 | |
| 13 | The manifest returned by the Control Frameworks, will add the information on the mapping provided to the user which can be of the the form [[BR]] |
| 14 | |
| 15 | <rs:ports requested_port="80" mapped_port="77756" [[BR]] |
| 16 | mapped_hostname="pc51.uky.emulab.net"> [[BR]] |
| 17 | |
| 18 | <rs:ports requested_port="169" mapped_port="77757" [[BR]] |
| 19 | mapped_hostname="pc51.uky.emulab.net"> [[BR]] |
| 20 | |
| 21 | the "mapped_port" and "mapped_hostname" would be the port number and hostname to which the requested_port number for that PC/VM is mapped to. [[BR]] |
| 22 | |
| 23 | I am not sure if this is the ultimate solution, but the purpose could be two fold. [[BR]] |
| 24 | |
| 25 | 1. In cases where the aggregates have firewall in place, this attribute could serve as a directive for the aggregate to open up that port or map it to an alternate port so that the experiment works as designed. [[BR]] |
| 26 | |
| 27 | 2. In our case we have connectivity to port 80 or other ports on the VMs we need. [[BR]] |
| 28 | |
| 29 | Comments and suggestions are encouraged...:) [[BR]] |
| 30 | |
| 31 | (Be advised. this is only a proposal/idea that could be forwarded to the CF people ) [[BR]] |
| 32 | |
| 33 | -- |
| 34 | cheers, [[BR]] |
| 35 | |
| 36 | Hussam [[BR]] |
| 37 | (Hussamuddin Nasir) [[BR]] |
| 38 | |
| 39 | Netlab Operations Team [[BR]] |
| 40 | |