summaryrefslogtreecommitdiffstats
path: root/openecomp-ui
AgeCommit message (Expand)AuthorFilesLines
2018-03-21added property skipUICleanupEinav Weiss Keidar1-3/+15
2018-03-21components navigation issue fixsvishnev1-71/+73
2018-03-20Adding Prettier and fixing up eslint versionEinav Weiss Keidar382-22030/+32740
2018-03-20ui support for archive itemssvishnev63-528/+1022
2018-03-11sdc-ui version upgradesvishnev1-1/+1
2018-03-09sdc-ui version upgrade and fixessvishnev2-26/+6
2018-03-08heat validation tabs and download fixsvishnev2-18/+17
2018-03-07Sync Integ to MasterMichael Lando1-49/+14
2018-03-07Fix for radio buttonsAriel Kenan1-1/+24
2018-02-15upgrade react frameworkEinav Weiss Keidar59-671/+466
2018-02-15ui filter component for catalog filtersvishnev10-12/+238
2018-02-13heat validation flowsvishnev12-75/+200
2018-02-07fixing testssvishnev3-21/+357
2018-01-28update nod version and add yarnsvishnev2-34/+10943
2018-01-25babel preset update in openecom-uisvishnev4-13/+11
2018-01-23removing gulp-helpers from openecomp-ui buildsvishnev5-32/+69
2018-01-21react-version-downgradesvishnev48-107/+105
2018-01-16Dropdown text cut off fixsvishnev2-0/+4
2018-01-15Adding owner id to onboarding tilessvishnev3-3/+9
2018-01-15Contributor can also submit fixsvishnev2-12/+24
2018-01-11React version upgradesvishnev62-762/+881
2018-01-09UI support for Togglz flowsvishnev12-7/+262
2018-01-09Change variable names to catalogilanap11-36/+37
2018-01-04Replace restful-js with Axiosilanap15-227/+388
2018-01-03select item from workspace- skipping versions pagemiriame8-36/+98
2017-12-26fix licensing issuesMichael Lando2-2/+1
2017-12-21Add collaboration featuretalig427-4799/+11147
2017-11-15licens violation issue fixstanvishne5-24/+2
2017-11-07hardcoded version of restful-jsilanap1-1/+1
2017-11-07Update VLM Overview tab behaviorilanap7-30/+68
2017-11-02Merge "VLM overview - refactor of edit description input"Avi Gaffa6-9/+21
2017-11-02VLM overview - refactor of edit description inputmiriame6-9/+21
2017-11-01Merge "Readonly screen for limits"Vitaly Emporopulo4-12/+46
2017-11-01Merge "confirmation msg for delete FG doesn't appear"Vitaly Emporopulo1-1/+3
2017-10-26confirmation msg for delete FG doesn't appearmiriame1-1/+3
2017-10-26delete confirmation modals - styles alignmentmiriame8-8/+16
2017-10-23Readonly screen for limitsilanap4-12/+46
2017-10-22Merge "fix error when moving to previous version"Avi Gaffa1-1/+2
2017-10-22Merge "parse multilple error messages in separate lines"Avi Gaffa2-3/+6
2017-10-22fix error when moving to previous versionmiriame1-1/+2
2017-10-22parse multilple error messages in separate linesmiriame2-3/+6
2017-10-22White spaces in limit viewilanap1-13/+25
2017-10-17remove the node modules clean upMichael Lando1-7/+7
2017-10-17Merge "Problem validation error message"Avi Gaffa1-3/+3
2017-10-16Display firefox month navigation iconilanap1-11/+18
2017-10-09Problem validation error messageilanap1-3/+3
2017-09-27Fix orphan list for VLMsilanap4-21/+30
2017-09-19change version of the master branchMichael Lando1-1/+1
2017-09-19Merge "description styling bug fix"Avi Gaffa1-1/+6
2017-09-18description styling bug fixMiriam Eini1-1/+6
ndalone-firefox:2.53.1 container. About BE APIs tests, onboarding E2E flow : Onboarding E2E flow cover following SDC functionality: Onboard of VNF Create VF from VSP Certify VF Create Service Add VF to service Certify Service Export TOSCA and validate it structure using external TOSCA parser **as part of execution we open a connection to Titan and perform resources clean up both before and after tests execution (only resource with “ci” prefix will be deleted from the catalog) List of VNFs/PNFs that proceed by onboarding flow, located in `integration-tests/src/test/resources/Files/`) sample-signed-pnf-cms-includes-cert-1.0.1-SNAPSHOT.zip sample-signed-pnf-1.0.1-SNAPSHOT.zip sample-pnf-1.0.1-SNAPSHOT.csar sample-pnf-custom-type.csar base_vfw.zi base_vvg.zip database-substitution-mappings.csar helm.zip Huawei_vHSS.csar Huawei_vMME.csar infra.zip resource-ZteEpcMmeVf-csar_fix.csar vbng.zip vbrgemu.zip vfw.zip vgmux.zip vgw.zip vLB.zip vLBMS.zip vSBC_update_v03.csar vsp-vgw.csar vvg.zip ZteEpcMmeVf.csar #### Start the integration tests manually Those tests execute the following There are 2 options to start them: * After having started SDC with the command `mvn clean install -P start-sdc`, run the command `mvn clean install -P run-integration-tests` * If you want to debug them and run them from your IDE, you must start them from the testNG Suites files, otherwise this won't work. The test suites are located here: * BE: `integration-tests/src/test/resources/ci/testSuites/backend` * FE: `integration-tests/src/test/resources/ci/testSuites/frontend` #### Integration tests with Helm Validator Those tests use container built externally in other ONAP repository: [sdc/sdc-helm-validator](https://gerrit.onap.org/r/admin/repos/sdc/sdc-helm-validator) You can run those tests same as default integration tests by adding additional profile to maven commands: `integration-tests-with-helm-validator` * To start SDC with Helm Validator run: `mvn clean install -P start-sdc,integration-tests-with-helm-validator` * To execute tests that use Helm Validator use: `mvn clean install -P run-integration-tests,integration-tests-with-helm-validator` ## Accessing SDC UI in Dev Mode (Legacy way) In order to access the SDC UI from your dev environment you need to do the following: 1. Go to file `webpack.server.js` found under the catalog-ui folder in the main sdc project and update the "localhost" variable to be the ip of your local vagrant machine. 2. Navigate to the catalog-ui folder and run the command: `npm start -- --env.role <wanted_role>` with the wanted role to login to SDC as. ## SDC on OOM For more information regarding SDC on OOM please refer to the following page: [SDC on OOM](https://wiki.onap.org/display/DW/SDC+on+OOM) ## Frontend Local Env - onboarding ### Steps: Install nodejs & gulp 1. download nodejs from here: https://nodejs.org/en/ (take the "current" version with latest features) & install it. 2. install gulp by running the following command: npm install --global gulp-cli ### Install DOX-UI a: 1. pull for latest changes 2. go to folder dox-sequence-diagram-ui 3. run npm install 4. wait for it... 5. go to folder dox-ui 6. run npm install 7. create a copy of devConfig.defaults.json file and name it devConfig.json (we already configured git to ignore it so it will not be pushed) 8. in that file, populate the fields of the IP addresses of your BE machine you'd like to connect (pay attention, it is a JSON file): For example http://<host>:<port> 9. after everything is successful, run gulp 10. after server is up, your favorite UI will wait for you at: http://localhost:9000/sdc1/proxy-designer1#/onboardVendor ### Troubleshooting: | Problem | Why is this happening | Solution | |-------------------------------|-------------------------|--------------------------------------------------------------------------------------------| | npm cannot reach destination | onboarding proxy | When within onboarding network, you should set onboarding proxy to NPM as the following: | | | | npm config set proxy http://genproxy:8080 | | | | npm config set https-proxy http://genproxy:8080 | | | | | | git protocol is blocked | onboarding network | When within onboarding network, you should set globally that when git | | and cannot connect | rules for protocols | protocol is used, it will be replaced with "https" | | | | git config --global url."https://".insteadOf git:// | -------------------------------------------------------------------------------------------------------------------------------------------------------- ## SDC Troubleshooting In order to check the life state of SDC you can run the command `health` from inside the vagrant. Alternatively you can run the following commands to check the FE and BE status: FE - `curl http://<ip_address>:8181/sdc1/rest/healthCheck` BE - `curl http://<ip_address>:8080/sdc2/rest/healthCheck` Another method to check about problems in SDC is to look at the log files. The jetty(Applicative) are found in the respective folder according to the wanted section For example, the BE logs will found under the directory `/BE`. For more information regarding SDC Troubleshooting please refer to the following guide: [SDC Troubleshooting](https://wiki.onap.org/display/DW/SDC+Troubleshooting) ## Getting Help ##### [Mailing list](mailto:onap-sdc@lists.onap.org) ##### [JIRA](http://jira.onap.org) ##### [WIKI](https://wiki.onap.org/display/DW/Service+Design+and+Creation+%28SDC%29+Portal)