-
Notifications
You must be signed in to change notification settings - Fork 14
Frontend configuration
Home > Installation and configuration manuals > Frontend configuration
**Disclaimer:**The following configuration manual assumes that installation of the whole software has been done according to the installation manual.
##localsettings.py
configuration options (common)
###General parameters
FLAG | Values | Comments |
---|---|---|
ISLAND_NAME |
String | Island/testbed name. Shown on the upper right corner of the Web frontend |
SITE_DOMAIN |
String | Expedient host domain name |
###Root (Island Manager) account information
FLAG | Values | Comments |
---|---|---|
ROOT_USERNAME |
String | Expedient's root username |
ROOT_PASSWORD |
String | Expedient's root password |
ROOT_EMAIL |
String | Expedient's root email. This mail will be used to send notifications |
###Database parameters
FLAG | Values | Comments |
---|---|---|
DATABASE_USER |
String | MySQL username |
DATABASE_PASSWORD |
String | MySQL password |
DATABASE_HOST |
String | MySQL host (e.g. 127.0.0.1) |
DATABASE_NAME |
String | Expedient database name. |
###LDAP support
FLAG | Values | Comments |
---|---|---|
ENABLE_LDAP_BACKEND |
True /False
|
Enable LDAP Backend for user authentication in coexistance or not with the MySQL users. Requires AUTH_LDAP_BIND_PASSWORD and AUTH_LDAP_BIND_DN to be correctly setup |
AUTH_LDAP_BIND_PASSWORD |
String | LDAP BIND DN password |
AUTH_LDAP_BIND_DN |
String | LDAP BIND DN. Example AUTH_LDAP_BIND_DN="uid=changeme,ou=admins,dc=fp7-ofelia,dc=eu"
|
LDAP_STORE_PROJECTS |
True /False
|
Enable LDAP project member group storage (to be used for instance by VM pam_ldap.so module). For non-OFELIA we recommend to set it to False
|
ALLOW_LOCAL_REGISTRATION |
True /False
|
Disables local (MySQL) user registration mechanism, usually to force users to use LDAP registration mechanisms and/or to temporally limit user registration. |
##ldapSettings.py
configuration options
When setting your own LDAP server you should also take a look to the defaultsettings/ldapSettings.py
file and update it accordingly. Some values are as follows:
FLAG | Values | Comments |
---|---|---|
AUTH_LDAP_SERVER_URI |
String | The URI for your LDAP server. You may use a normal IP, a registered domain or use your own identifying string (setting the equivalence under /etc/hosts ). Example: AUTH_LDAP_SERVER_URI = "ldap://ldap.your-organization.eu:389"
|
AUTH_LDAP_USER_SEARCH |
LDAPSearch with DN | Triplet that defines:
|
Login as root
user to the frontend to perform administrative operations.
Check Opt-in Manager instance is up and running and configured as explained in Optin configuration manual.
Make sure Optin Manager has connectivity with Flowvisor and that authentication between Flowvisor and Optin Manager is correctly set before proceeding. If Optin Manager is unable to contact Flowvisor, topology will not be imported into the GUI. Re-update the AM in Expedient to refresh/import the topology.
From Administration page in the Expedient Dashboard select OpenFlow Aggregate from the Aggregate Type list and click in Add Aggregate
Important parameters:
- Username: Clearinghouse user set in Opt-in Manager in previous section
- Password: Clearinghouse password set in Opt-in Manager in previous section
-
Server URL: URL of the Opt-in Manager's XMLRPC interface. It should be
https://DOMAIN_NAME:PORT/xmlrpc/xmlrpc/
. Notice thatDOMAIN_NAME
can be an IP address as long as it matches the certificate's Common Name of the server where Opt-in Manager is running.
From Administration page in the Expedient Dashboard select Virtualization Aggregate from the Aggregate Type list and click in Add Aggregate
Important parameters:
-
Username:
ROOT_USERNAME
set in the VM Aggregate Manager settings during installation -
Password:
ROOT_PASSWORD
set in the VM Aggregate Manager settings during installation -
Server URL: URL of the VM Aggregate Manager's XMLRPC interface is exporting to the Expedient. It should be
https://DOMAIN_NAME:PORT/xmlrpc/plugin
. Notice that DOMAIN_NAME can be an IP address as long as it matches the certificate's Common Name of the server where VM AM is running. Default port is 8445
- Overview
- Experimenting
-
Administering
- Installing
- Upgrading
-
Configuration
- Components
- Infrastructure
- Troubleshooting
- Theme manager
-
Contributing
- Developing
-
Reporting
- Issue tracker and Roadmap