[[PageOutline]]

= Rspec Extension Proposal to Enable Port Mapping =

By Hussamuddin Nasir [nasir@netlab.uky.edu]  [[BR]]
4/3/12 [[BR]]


Attached is a sample rspec node and its [http://groups.geni.net/geni/attachment/wiki/RspecExtensionProposal_PortMapping/rspec%20extension%20proposal.txt  manifest ] with the proposed extension. [[BR]]

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]]

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]]

<rs:ports  requested_port="80"  mapped_port="77756"  [[BR]] 
mapped_hostname="pc51.uky.emulab.net"> [[BR]]

<rs:ports  requested_port="169"  mapped_port="77757"   [[BR]]
mapped_hostname="pc51.uky.emulab.net"> [[BR]]

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]]

I am not sure if this is the ultimate solution, but the purpose could be two fold. [[BR]]

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]]

2. In our case we have connectivity to port 80 or other ports on the VMs we need. [[BR]]

Comments and suggestions are encouraged...:) [[BR]]

(Be advised. this is only a proposal/idea that could be forwarded to the CF people  ) [[BR]]

-- 
cheers, [[BR]]

Hussam [[BR]]
(Hussamuddin Nasir) [[BR]]

Netlab Operations Team [[BR]]