Jump to: navigation, search

Difference between revisions of "BarbicanDevStack"

(Running Barbican via DevStack)
(Running Barbican via DevStack)
Line 31: Line 31:
 
enable_service rabbit mysql key barbican
 
enable_service rabbit mysql key barbican
  
 +
# We do this to keep the token small so we don't run into issues
 +
# with the token being too large in the headers, this works great
 +
# for testing, etc.
 
KEYSTONE_TOKEN_FORMAT=UUID
 
KEYSTONE_TOKEN_FORMAT=UUID
  

Revision as of 16:32, 2 June 2014

Running Barbican via DevStack

Steps to run Barbican via DevStack (assuming Ubuntu 12.04 LTS or Ubuntu 14.04 LTS):

$ sudo apt-get update
$ sudo apt-get install git -y
$ git clone https://github.com/openstack-dev/devstack.git
$ git clone https://github.com/openstack/barbican.git
$ mv barbican/contrib/devstack/lib/barbican devstack/lib/
$ mv barbican/contrib/devstack/extras.d/70-barbican.sh devstack/extras.d/
$ sudo ./devstack/tools/create-stack-user.sh
$ sudo mv devstack/ /opt/stack/
$ rm -rf barbican/
$ chown -R stack:stack /opt/stack/devstack/
$ su - stack
$ cd /opt/stack/devstack/

You'll need to create and edit a file called local.conf:

$ nano local.conf

To just run Barbican and required services add the following into the local.conf file and modify the passwords as required:

[[local|localrc]]
disable_all_services
enable_service rabbit mysql key barbican

# We do this to keep the token small so we don't run into issues
# with the token being too large in the headers, this works great
# for testing, etc.
KEYSTONE_TOKEN_FORMAT=UUID

DATABASE_PASSWORD=password
RABBIT_PASSWORD=password
SERVICE_TOKEN=password
SERVICE_PASSWORD=password
ADMIN_PASSWORD=password

This next step will take a while to run but the end result is you should have Barbican running under DevStack:

$ ./stack.sh

Note: If you have issues (compute might be throwing some errors) you can ease back the firewall. Keep in mind this opens your computer up completely. Only do this if you know what you are doing and if you are having issues. Adjust as needed.

# Flush all firewall rules for DevStack
# (Only do this if you really know what you're doing and have problems running DevStack)
$ iptables -F
$ iptables -P INPUT ACCEPT
$ iptables -P FORWARD ACCEPT
$ iptables -P OUTPUT ACCEPT