Routes configuration

This page contains the routes configuration to reach the different services offered by the Portal.

Routes configuration

The routes to the endpoints used for this project are defined as follows:

export class ConfigService {
	roles = 'users/roles';
	register = 'users/';
	login = 'users/sessions/';
	services = 'services';
	requests = 'requests';
	serviceRecords = 'records/services';
	platformUptime = 'records/services/uptime';
	functionRecords = 'records/functions';
	licenses = 'slas/licenses';
	buyLicense = 'slas/licenses/buy';
	licenseStatus = 'slas/licenses/status';
	packages = 'packages';
	slaTemplates = 'slas/templates';
	slaTemplatesForService = 'slas/templates/services/';
	slaAgreements = 'slas/agreements';
	slaViolations = 'slas/violations';
	guarantees = 'slas/configurations/guaranteesList';
	flavors = 'slas/configurations/deploymentflavours';
	functions = 'functions';
	slicesTemplates = 'slices';
	slicesInstances = 'slice-instances';
	testPlans = 'tests/plans';
	testPlansTests = 'tests/plans/tests';
	testPlansPolicies = 'tests/plans/policies';
	testPlansServices = 'tests/plans/services';
	testDescriptors = 'tests/descriptors';
	testExecute = 'tests/plans';
	testExecutions = 'tests/results';
	placementPolicies = 'policies/placement';
	runtimePolicies = 'policies';
	runtimePolicyActivation = 'policies/activate/';
	runtimePolicyDeactivation = 'policies/deactivate/';
	runtimePoliciesUI = 'policies/ui';
	runtimePoliciesBind = 'policies/bind/';
	runtimePoliciesDefault = 'policies/default/';
	runtimePoliciesActions = 'policies/actions';
	runtimePoliciesRecords = 'policies/records';
	runtimePoliciesMonitoringMetrics = 'policies/monitoring_metrics/';
	vimSettings = 'settings/vims';
	vimOpenstackSettings = 'settings/vims/heat';
	vimK8sSettings = 'settings/vims/k8s';
	wimSettings = 'settings/wims';
	tapiSettings = 'settings/wims/tapi';
	platformSettings = 'settings/platforms';
	graphs = 'monitoring/graphs';
	monitoringData = 'monitoring/data/services';
	monitoringMetricsByName = 'monitoring/data/prometheus/metrics/name/';
	monitoringTargets = 'monitoring/data/prometheus/targets';
	analyticsResult = 'analytics/results/';
	analyticResult = 'analytic/results';
	analyticResultList = 'analytics/results/list';
	analyticServices = 'analytics/list';
	analyticMonitoringMetrics = 'analytics/tests/vnv/';
	analyticProcessExecution = 'analytics/analytic_service';
}

In a production deployment of the Portal, the base routes baseSP and baseVNV are defined as the protocol, the domain name and the port number where the Portal is deployed plus the "/api/v3/" route to reach the endpoints offered by the actual version of the tng-api-gtw.

In case the Portal is launched locally for development**, the base routes are automatically configured to reach http://pre-int-sp-ath.5gtango.eu:32002/api/v3/ endpoints for the Service Platform, and http://pre-int-vnv-bcn.5gtango.eu:32002/api/v3/ for the V&V platform.

Note: ng serve --host development --open but first you need to register the development domain in your /etc/hosts next to the localhost declaration