Introduction
This is a list of all currently available categories in sdc project:
...
- Service categories
- Resource categories
The yaml file for the categories can be found here: https://gerrit.onap.org/r/gitweb?p=sdc.git;a=tree;f=catalog-be/src/main/resources/import/tosca/categories
Each time a new category is being added to the file the next time sdc is being booted the new category should be loaded and ready to use in SDC
| Info |
|---|
For each category the explanation is as followed: Mobility - The name of the category as it's saved in the project
name: "Mobility" - The display name of the category
icons: ['mobility'] - The icon to useicons that can be used for this category (All the icons can be found in this
directory in the sdc project: https://gerrit.onap.org/r/gitweb?p=sdc.git;a=tree;f=catalog-ui/src/assets/styles/images) |
Service Categories
| Code Block |
|---|
|
Mobility:
name: "Mobility"
icons: ['mobility']
Network_L1_3:
name: "Network L1-3"
icons: ['network_l_1-3']
Network_L4:
name: "Network L4+"
icons: ['network_l_4']
VoIP_Call_Control:
name: "VoIP Call Control"
icons: ['call_controll']
E2E_Service:
name: "E2E Service"
icons: ['network_l_1-3']
Network_Service:
name: "Network Service"
icons: ['network_l_1-3'] |
Docker compilation - Docker Maven Build Profile (io.fabric8 maven Plugin)
If you are using ONAP-Vagrant environment you can deploy the simulator by:
Set up the DOCKER_HOST environmental variable
To set environmental variable in Windows (the docker engine environment):
- Run `cmd`
- Issue command `set NAME=VALUE`
| Code Block |
|---|
set DOCKER_HOST=tcp://127.0.0.1:2375 |
- To check if the variable set succeeded issue:
| Code Block |
|---|
echo %DOCKER_HOST% |
To compile sdc-simulator docker:
1. Run
| Code Block |
|---|
mvn clean install -Ddocker.buildArg.http_proxy=<http_proxy> -Ddocker.buildArg.https_proxy=<https_proxy> -P docker |
- The proxy arguments are passed and used as environmental variables in Dockerfiles
2. Copy the script /webseal-simulator/scripts/simulator_docker_run.sh to the docker engine environment and run:
| Code Block |
|---|
simulator_docker_run.sh -r 1.1-STAGING-latest |
3. To verify that sdc-simulator docker is up and running run:
4. Enter to UI: `http://<ip address>:8285/login`
| Code Block |
|---|
http://localhost:8285/login |
Docker compilation - Docker Engine
1. Build web simulator WAR file run in project “webseal simulator”:
| Code Block |
|---|
mvn clean install |
- This will generate war file (WSSimulator.war) in the target folder.
- Check that WSSimulator.war exists after first step No.1 in webseal-simulator/sdc-simulator folder.
2. Ftp war file: webseal-simulator/sdc-simulator folder to your localhost vagrant machine which runs docker engine daemon.
3. Run `docker build -t openecomp/sdc-simulator:1.1-STAGING-latest <PATH/sdc-simulator>`
| Code Block |
|---|
docker build -t openecomp/sdc-simulator:1.1-STAGING-latest /tmp/docker/sdc-simulator/ |
4. Validate that images pushed to the local repo by executing:
5. Copy the script /webseal-simulator/scripts/simulator_docker_run.sh to the docker engine environment and run:
| Code Block |
|---|
simulator_docker_run.sh -r 1.1-STAGING-latest |
6.To verify that sdc-simulator docker is up and running execute:
- If no docker sdc-sim running execute `docker ps -a`
7. Enter to UI: http://<ip address>:8285/login
| Code Block |
|---|
http://localhost:8285/login |
WAR compilation - to compile WSSimulator.war
1. To build web simulator WAR file run on project webseal-simulator:
| Code Block |
|---|
mvn clean install |
- This will generate war file (WSSimulator.war) in the target folder.
2. Ftp war file: webseal-simulator\target\WSSimulator.war to your localhost vagrant machine: /home/vagrant/webseal-simulator/webapps folder.
3. Ftp configuration file: webseal-simulator\src\main\resources\webseal.conf to your localhost vagrant machine: /home/vagrant/webseal-simulator/config
4. Add users to simulator: open configuration file - webseal.conf and add new user to the user list.
Note: You need to define the user in the SDC as well.
5. To run the simulator, enter to your local vagrant and run: startWebsealSimulator.sh
-- Restart the simulator:
Stop the simulator: stopWebsealSimulator.sh
Start the simulator: startWebsealSimulator.sh
7. Enter to UI: http://<ip address>:8285/login
...
Resource Categories
| Code Block |
|---|
| title | Network Layer 23 Categories |
|---|
|
NetworkLayer23:
name: "Network L2-3"
subcategories:
Router:
name: "Router"
icons: ['router','vRouter']
Gateway:
name: "Gateway"
icons: ['gateway']
WAN_Connectors:
name: "WAN Connectors"
icons: ['network','connector','port']
LAN_Connectors:
name: "LAN Connectors"
icons: ['network','connector','port']
Infrastructure:
name: "Infrastructure"
icons: ['ucpe'] |
| Code Block |
|---|
| title | Network Layer 4 Categories |
|---|
|
NetworkLayer4:
name: "Network L4+"
subcategories:
Common_Network_Resources:
name: "Common Network Resources"
icons: ['network'] |
| Code Block |
|---|
| title | Application Layer 4 Categories |
|---|
|
ApplicationLayer4:
name: "Application L4+"
subcategories:
Border_Element:
name: "Border Element"
icons: ['borderElement']
Application_Server:
name: "Application Server"
icons: ['applicationServer']
Web_Server:
name: "Web Server"
icons: ['applicationServer']
Call_Control:
name: "Call Control"
icons: ['call_controll']
Media_Servers:
name: "Media Servers"
icons: ['applicationServer']
Load_Balancer:
name: "Load Balancer"
icons: ['loadBalancer']
Database:
name: "Database"
icons: ['database']
Firewall:
name: "Firewall"
icons: ['firewall'] |
| Code Block |
|---|
|
Generic:
name: "Generic"
subcategories:
Infrastructure:
name: "Infrastructure"
icons: ['connector']
Abstract:
name: "Abstract"
icons: ['objectStorage', 'compute']
Network_Elements:
name: "Network Elements"
icons: ['network', 'connector']
Database:
name: "Database"
icons: ['database']
Rules:
name: "Rules"
icons: ['networkrules','securityrules'] |
| Code Block |
|---|
| title | Network Connectivity Categories |
|---|
|
NetworkConnectivity:
name: "Network Connectivity"
subcategories:
ConnectionPoints:
name: "Connection Points"
icons: ['cp']
VirtualLinks:
name: "Virtual Links"
icons: ['vl'] |
| Code Block |
|---|
| title | DCAE Component Categories |
|---|
|
DcaeComponent:
name: "DCAE Component"
subcategories:
Source:
name: "Source"
icons: ['dcae_source']
Collector:
name: "Collector"
icons: ['dcae_collector']
Utility:
name: "Utility"
icons: ['dcae_utilty']
Microservice:
name: "Microservice"
icons: ['dcae_microservice']
Analytics:
name: "Analytics"
icons: ['dcae_analytics']
Database:
name: "Database"
icons: ['dcae_database']
Policy:
name: "Policy"
icons: ['dcae_policy'] |
| Code Block |
|---|
|
Template:
name: "Template"
subcategories:
MonitoringTemplate:
name: "Monitoring Template"
icons: ['monitoring_template'] |
| Code Block |
|---|
| title | Allotted Resource Categories |
|---|
|
AllottedResource:
name: "Allotted Resource"
subcategories:
AllottedResource:
name: "Allotted Resource"
icons: ['allotted_resource']
TunnelXConnect:
name: "Tunnel XConnect"
icons: ['tunnel_x_connect']
IpMuxDemux:
name: "IP Mux Demux"
icons: ['ip_mux_demux']
ServiceAdmin:
name: "Service Admin"
icons: ['service_admin']
ContrailRoute:
name: "Contrail Route"
icons: ['contrail_route']
SecurityZone:
name: "Security Zone"
icons: ['security_zone']
NetworkService:
name: "Network Service"
icons: ['network'] |