Opened 14 years ago
Closed 14 years ago
#179 closed (fixed)
Provide plan for making Aggregate Manager externally accessible in Phase 0 deployment
| Reported by: | hdempsey@bbn.com | Owned by: | Srini Seetharaman |
|---|---|---|---|
| Priority: | major | Milestone: | ENTGENI: S1.a Deploy Phase 0 Enterprise GENI network at Stanford |
| Component: | GPO | Version: | SPIRAL1 |
| Keywords: | Cc: | nickm@stanford.edu, appenz@cs.stanford.edu | |
| Dependencies: |
Description
Phase 0 deployment should include an Aggregate Manager that communicates with the PlanetLab GENI clearinghouse. Please document plans for including this in Stanford deployment.
Note: See
TracTickets for help on using
tickets.
The E-GENI Aggregate Manager is accessible by configuring the following two params in the SFA server (Note: SFA server is public code offered by PL-GENI folks that acts a stub for the aggregate manager).
OPENFLOW_AGGREGATE_MANAGER_IP="nfcm13.stanford.edu" OPENFLOW_AGGREGATE_MANAGER_PORT=7889
Using the SFI tool (and the SFA server), public users can create a slice in E-GENI. However, only PlanetLab users can login to machines of-planet1.stanford.edu, of-planet2.., of-planet3..., of-planet4.., of-planet5 to be able to send traffic over the substrate after reserving the necessary FlowSpace through SFI tool.