RETIRED The UI component for TripleO
Go to file
Emilien Macchi 2dfbb0bfef Release Ocata-2
2.0.1 will be Ocata-2.

Change-Id: I9b269e0701061644dd00fb7ae58d09551cd50c20
2016-12-09 12:18:47 +01:00
dist Remove references to deprecated APIs 2016-12-08 15:55:33 +01:00
src Merge "Fix runValidationMessage action" 2016-12-02 14:34:53 +00:00
.babelrc Use Webpack for application processing 2016-07-25 15:18:37 +02:00
.editorconfig Adds .editorconfig file 2015-09-30 10:37:44 +02:00
.eslintrc Upgrade eslint and fix errors 2016-04-14 13:43:02 -03:00
.gitignore Add app.conf to .gitignore 2016-09-05 14:36:34 +02:00
.gitreview Updated .gitreview 2016-03-22 09:36:08 -05:00
.npmignore Add packaging spec and config files 2016-08-19 19:43:09 +02:00
LICENSE Add LICENSE 2016-03-22 13:57:46 -03:00
README.md Show team and repo badges on README 2016-11-25 18:46:32 +01:00
jenkins-config.yml Replace "RDO" with "TripleO" and remove RDO logo 2016-03-04 14:29:25 +01:00
karma.conf.js Use Webpack for application processing 2016-07-25 15:18:37 +02:00
npm-shrinkwrap.json Merge "Update version to match current release" 2016-09-16 09:17:37 +00:00
package.json Release Ocata-2 2016-12-09 12:18:47 +01:00
webpack.config.js Have dev server listen everywhere instead of just local 2016-09-15 08:15:55 -06:00

README.md

Team and repository tags

Team and repository tags

Development environment setup

Ideally, you should have one powerful machine ("virt host") on which you will install TripleO (the backend). For the development work on the TripleO UI, we recommend installing and configuring the UI directly on your workstation ("local machine") and then pointing it to the machine hosting the TripleO installation.

Install TripleO

Do these steps on the virt host.

Follow the official docs to install and configure TripleO (follow the step up to and including the Undercloud installation): http://docs.openstack.org/developer/tripleo-docs/index.html

Once the undercloud is installed, you will need to create a tunnel on your virt host, to make the services running on undercloud available to the UI:

ssh -N root@<undercloud_ip> -L 0.0.0.0:6385:192.0.2.1:6385 -L 0.0.0.0:5000:192.0.2.1:5000 -L 0.0.0.0:5001:192.0.2.1:5001 -L 0.0.0.0:8585:192.0.2.1:8585 -L 0.0.0.0:8004:192.0.2.1:8004 -L 0.0.0.0:8080:192.0.2.1:8080 -L 0.0.0.0:9000:192.0.2.1:9000 -L 0.0.0.0:8989:192.0.2.1:8989

Install Validations

To install Validations as part of your undercloud, make sure enable_validations is set to true in undercloud.conf, prior to running openstack undercloud install.

Install TripleO UI

Do these steps on the local machine.

Install nodejs and npm:

sudo dnf install nodejs

To compile and install native addons from npm you may also need to install build tools:

sudo dnf install gcc-c++ make

Clone the TripleO UI repo, change into the newly clone directory, install the dependencies and start the development server:

git clone https://github.com/openstack/tripleo-ui.git
cd tripleo-ui
npm install
npm start

Optionally start Karma to run tests after every change:

npm run test:watch

Copy dist/tripleo_ui_config.js.sample to dist/tripleo_ui_config.js, uncomment the lines pertaining to OpenStack services (keystone, tripleo, etc), and add the urls where these services can be accessed (in this case, the IP address of the virt host). You can set values for the other services as well to override the values coming from the keystone serviceCatalog.

To access the UI, navigate to http://localhost:3000/

Troubleshooting installation

In case of problems with the nodejs installation, refer to https://nodejs.org/en/download/package-manager/#enterprise-linux-and-fedora.

In case of errors during npm install, remove node_modules directory and clean npm cache, then run npm install again:

rm node_modules
npm cache clean
npm install

Contributing

Use OpenStack Gerrit for patches and reviews (http://docs.openstack.org/infra/manual/developers.html).

  1. git clone https://github.com/openstack/tripleo-ui.git (if you didn't already)
  2. Install git-review: sudo dnf install git-review
  3. Setup Gerrit: git review -s
  4. Develop on feature-branch locally
  5. Run git review to push patch for review.
  6. Review and merge patches on OpenStack Gerrit: https://review.openstack.org/#/q/project:openstack/tripleo-ui

Tests

Single test run

  • npm test (alternatively run karma start --single-run)
  • npm run lint to run ESLint

Info on Linting setup: https://medium.com/@dan_abramov/lint-like-it-s-2015-6987d44c5b48 .eslintrc rules tweaks: http://blog.javascripting.com/2015/09/07/fine-tuning-airbnbs-eslint-config/

Tests during development

Start Karma to run tests after every change npm run test:watch

Debugging tests

  1. option:
  • use console.log in the test and see the output in karma server output
  1. option:
  • install karma-chrome-launcher npm module npm install karma-chrome-launcher --save-dev
  • replace/add 'Chrome' to browsers in karma.conf.js
  • now Karma will launch Chrome to run the tests
  • use debugger; statement in test code to add breakpoints
  • in Karma Chrome window click 'debug' button and debug in chrome developer tools as usual
  • optionally you can use karma-jasmine-html-reporter for better test output (https://www.npmjs.com/package/karma-jasmine-html-reporter)
  • make sure you don't push those changes to karma.conf.js and package.json as part of your patch

Style guide and conventions

Style guide: https://github.com/airbnb/javascript

Multiple words in folder names should be separated by an underscore:

src/js/components/environment_configuration

Documentation

Use JSDoc docstrings in code to provide source for autogenerated documentation (http://usejsdoc.org/).