+++ This bug was initially created as a clone of Bug #986024 +++

The experience with installing via packstack with Quantum/Neutron is poor, compared with installing with Nova networking. This is primarily due to the fact that with Quantum/Neutron it is necessary to manually create networks/subnets/routers to be able to launch a VM.

We should implement things in such a way that:

$ packstack --allinone

with quantum/neutron enabled leaves things in a state that is as close to what a user would get functionality-wise with Nova networking (i.e. the user should be able to follow the instructions at http://openstack.redhat.com/Running_an_instance) with as few changes as possible.

(this work is already done, but this bug is to track actually getting everything in the release)

--- Additional comment from Terry Wilson on 2013-07-18 16:11:29 EDT ---

New answer file options:

CONFIG_KEYSTONE_DEMO_PW
  The demo tenant password. Automatically configured/no prompting just like the ADMIN_PW. Only actually used if CONFIG_PROVISION_DEMO=y
CONFIG_PROVISION_DEMO
  Whether to provision demo quantum networks/subnets/routers
  Requires: CONFIG_QUANTUM_INSTALL=y and CONFIG_QUANTUM_USE_NAMESPACES=y
CONFIG_PROVISION_TEMPEST
  Whether to set up tempest for running tests against the Openstack install
  Requires: CONFIG_QUANTUM_INSTALL=y and CONFIG_QUANTUM_USE_NAMESPACES=y
CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE
  Whether to set up the L3 external bridge with the appropriate IP address to act as the gateway for VMs.

The --allinone option will automatically enable CONFIG_PROVISION_DEMO and CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE if CONFIG_QUANTUM_INSTALL=y (which it is by default). --allinone --os-quantum-install=n still works for installing w/o quantum.

Additional changes:
1) A new 'demo' keystone tenant is added along with a keystonerc_demo file which can be sourced like the existing keystonerc_admin. Users should log into horizon using the 'demo' account instead of the 'admin' account due to the ownership of the private and public networks.

2) When launching a VM via horizon, the user will additionally need to go to the "Network" tab and select the "private" network.

3) Current instructions specify creating an security group rule to allow SSH traffic. It might be helpful to have them add an ICMP rule as well (entering -1 for the two fields to allow all ICMP)