kolla

Vagrant dev env should provide a way to configure it easily

Bug #1517475 reported by Martin André
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Medium
Martin André
kolla mitaka-1 "mitaka-1"

Bug Description

The Vagrantfile already has all its setting at the same place but the file is under version control which is not ideal for customization. We should extract these settings to a new file that is placed in the gitignore.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/246931

Changed in kolla:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/246931
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=5eb67e275eb16b4a67a0de04ca325df44718a8b1
Submitter: Jenkins
Branch: master

commit 5eb67e275eb16b4a67a0de04ca325df44718a8b1
Author: Martin André <email address hidden>
Date: Wed Nov 18 17:47:15 2015 +0900

    Allow to customize vagrant deployment

    Extract the Vagrantfile configuration to a Vagrantfile.custom file, to
    permit easy customization of the Vagrant deployment without the need to
    modify a file under version control.

    Closes-Bug: #1517475
    Change-Id: I03e3ef373ec47e3d622b77fa9cf88748db99adaa

Changed in kolla:
status: In Progress → Fix Committed
Sam Yaple (s8m)
Changed in kolla:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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