devstack-startup

Bug #1536341 reported by Devdatta Kulkarni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Solum
Fix Released
High
Unassigned

Bug Description

We need to follow these steps to successfully start vagrant + devstack.

1) vagrant up ; this will fail with pep issue; login to vagrant vm (vagrant ssh)

2) Make changes to devstack repo as specified in https://github.com/openstack-dev/devstack/commit/1d27155f650e9b8e4053a201f1f08c494b820de2

3) Create neutron config files my following the README in /opt/stack/neutron/etc

4) Rename *.sample files to get rid of sample from file extension

5) remove 'ec2' from devstack/stackrc

6) Add OS_TEST_TIMEOUT=1200 to /opt/stack/tempest/tox.ini

7) Set lock_path = $state_path/lock in /etc/neutron/neutron.conf

We should automate these steps. Till that happens, perform these steps manually, then run % ~/devstack/unstack.sh followed by % ~/devstack/stack.sh

Changed in solum:
milestone: none → next-mitaka
Changed in solum:
importance: Undecided → High
description: updated
Revision history for this message
Devdatta Kulkarni (devdatta-kulkarni) wrote :

This no longer seems to be an issue.

Also, we have consolidated the steps required to setup devstack with solum plugin:

https://github.com/devdattakulkarni/solum-provenance/blob/master/steps-to-enable-solum-with-devstack

Marking this bug as 'Fix Released'.

Changed in solum:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.