Changes between Version 12 and Version 13 of ProtoGeniIntegration

Changes between Version 12 and Version 13 of ProtoGeniIntegration

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 12 and Version 13 of ProtoGeniIntegration

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 12 and Version 13 of ProtoGeniIntegration

Show
Ignore:
Timestamp:
01/22/13 14:12:35 (6 years ago)
Author:
gpress
Comment:

Removed some SeattleGENI references

Legend:

Unmodified
Added
Removed
Modified
  • ProtoGeniIntegration

    v12 v13  
    66[[BR]] 
    77== Introduction == 
    8 This is an XML-RPC interface that integrates the SeattleGENI project with the ProtoGENI project. You do not need to run your own instance of this code to access SeattleGENI resources through ProtoGENI.   You can leverage an instance of the software which we run to provide resources to ProtoGENI users. An instance of the XML-RPC server is currently running at https://blackbox.cs.washington.edu/xmlrpc/ (note that this page cannot be viewed in html format, can only be accessed via XML-RPC communication.) 
     8This is an XML-RPC interface that integrates the Seattle Clearinghouse project with the ProtoGENI project. You do not need to run your own instance of this code to access Seattle Clearinghouse resources through ProtoGENI.   You can leverage an instance of the software which we run to provide resources to ProtoGENI users. An instance of the XML-RPC server is currently running at https://blackbox.cs.washington.edu/xmlrpc/ (note that this page cannot be viewed in html format, can only be accessed via XML-RPC communication.) 
    99 
    10 This allows users from different project to acquire resources from the SeattleGENI project as long as they have the proper credentials. SeattleGENI has implemented the two api calls: !CreateSliver() and !DeleteSlice(). These two calls allow users to acquire resources and release resources from the SeattleGENI project. The XML-RPC server is located at !https://blackbox.cs.washington.edu/xmlrpc/ A tarball of the XML-RPC server as well as the components required to set it up is attached at the bottom of this page. 
     10This allows users from different project to acquire resources from the Seattle Clearinghouse project as long as they have the proper credentials. Seattle Clearinghouse has implemented the two api calls: !CreateSliver() and !DeleteSlice(). These two calls allow users to acquire resources and release resources from the SeattleClearinghouse project. The XML-RPC server is located at !https://blackbox.cs.washington.edu/xmlrpc/ A tarball of the XML-RPC server as well as the components required to set it up is attached at the bottom of this page. 
    1111 
    12 The SeattleGENI project also has its own XML-RPC server which provides a richer interface to interact with SeattleGENI resources. A description of the SeattleGENI XML-RPC server and the various api calls that are available can be found at the [wiki:SeattleGeniApi SeattleGENI API] page. 
     12The Seattle Clearinghouse project also has its own XML-RPC server which provides a richer interface to interact with Seattle Clearinghouse resources. A description of the Seattle Clearinghouse XML-RPC server and the various api calls that are available can be found at the [wiki:SeattleGeniApi SeattleGENI API] page. 
    1313 
    1414[[BR]] 
    1515== !CreateSliver(argument_dict) == 
    1616---- 
    17 !CreateSliver is used to acquire resources from the SeattleGENI project. It takes in a dictionary with three items: slice_urn, rspec and a list of credentials. The dictionary is of the form: 
     17!CreateSliver is used to acquire resources from the Seattle Clearinghouse project. It takes in a dictionary with three items: slice_urn, rspec and a list of credentials. The dictionary is of the form: 
    1818{{{ 
    1919   {'slice_urn'   : "urn:publicid:IDN+SeattleGENI+slice+mytestslice", 
     
    9797}}} 
    9898 1. Set up the .conf file for apache. An example of what the .conf file should look like is provided (seattlegeni_apache.conf). A more detailed description on how to edit this file is located at the bottom of this file. 
    99  1. Edit the file protogeni_user_file.txt and add all the seattlegeni users that have been specifically allocated for the protogeni integration. You can acquire seattlegeni usernames by registering an username through the SeattleGENI website at: https://seattlegeni.cs.washington.edu . The format of each line in protogeni_user_file.txt is: 
     99 1. Edit the file protogeni_user_file.txt and add all the Seattle Clearinghnouse users that have been specifically allocated for the protogeni integration. You can acquire Seattle Clearinghouse usernames by registering an username through the Clearinghouse website at: https://seattleclearinghouse.poly.edu . The format of each line in protogeni_user_file.txt is: 
    100100{{{ 
    101101seattlegeni_username:password_for_user:1:0:0