The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Federated Cloud siteconf"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
Parameters provided by each site are: | Parameters provided by each site are: | ||
* '''default network name''', as the name of the network assigned by default when firing up a VM to the site; at the moment, it might be that the network is private, public or not assigned at all; example: | * '''default network name''', as the name of the network assigned by default when firing up a VM to the site; at the moment, it might be that the network is private, public or not assigned at all; example: ''/network/PUBLIC'' | ||
* '''default network type''', can be public, private, or N/A (not available) | * '''default network type''', can be ''public'', ''private'', or ''N/A'' (not available) | ||
== BEgrid-BELNET == | == BEgrid-BELNET == | ||
Revision as of 18:09, 18 July 2017
| Overview | For users | For resource providers | Infrastructure status | Site-specific configuration | Architecture |
The main purpose of this page is to collect site-specific configuration parameters of the Federated Cloud sites, allowing comparison among them, identify differences, get parameters for a specific site.
If you have any comments on the content of this page, please contact operations @ egi.eu.
Site-specific configuration
Parameters provided by each site are:
- default network name, as the name of the network assigned by default when firing up a VM to the site; at the moment, it might be that the network is private, public or not assigned at all; example: /network/PUBLIC
- default network type, can be public, private, or N/A (not available)