Difference between revisions of "Tuskar/Instack"

Revision as of 11:48, 2 October 2014

Using Tuskar and Tuskar-UI with instack

Installing from source

Follow steps in https://github.com/agroup/instack-undercloud/blob/master/README-source.md

Create ssh tunnel so you can access Tuskar UI from you machine, example:

# 192.168.122.215 is undercloud ip
# ibm-x3550m4-07.lab.eng.brq.redhat.com is lab addr
# Tuskar-UI be accessible on localhost:8045 in your browser
ssh -L 8045:192.168.122.215:80 root@ibm-x3550m4-07.lab.eng.brq.redhat.com

Running TuskaUI in development mode

For development it's better to install Horizon and Tuskar-UI on your lab, so you don't have to reinstall it every time yuo reinstall Instack.

# Install Tuskar-UI and Horizon on your lab

# Set routes, rerun this everytime Undercloud IP changes
BM_NETWORK_CIDR=192.0.2.0/24
ROUTE_DEV=virbr0
SEED_IP=libvirt default network ip of instack vm (undercloud VM)
ip route replace $BM_NETWORK_CIDR dev $ROUTE_DEV via $SEED_IP

# In horizon local_settings set OPENSTACK_HOST=192.0.2.1

# Run horizon manually
tools/with_venv.sh ./manage.py runserver 0.0.0.0:8320

# Either allow the Horizon port in firewall or setup ssh tunnel
ssh -L 8330:localhost:8320 root@ibm-x3550m4-07.lab.eng.brq.redhat.com

# Go to browser on localhost:8330

@@ Line 14: / Line 14: @@
 === Running TuskaUI in development mode ===
 For development it's better to install Horizon and Tuskar-UI on your lab, so you don't have to reinstall it every time
-yo reinstall isntack.
+yuo reinstall Instack.
   # Install Tuskar-UI and Horizon on your lab
@@ Line 24: / Line 24: @@
   ip route replace $BM_NETWORK_CIDR dev $ROUTE_DEV via $SEED_IP
-  # In horizon local_settings set OPENSTACK_URL=192.0.2.1
+  # In horizon local_settings set OPENSTACK_HOST=192.0.2.1
   # Run horizon manually