Disable file injection in baremetal by default

Bug #1278347 reported by OpenStack Infra on 2014-02-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Medium
Tom Fifield

Bug Description

https://review.openstack.org/70252

Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/nova" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit bf2465d40ec82b238fc87eb3e7329de219b39967
Author: Robert Collins <email address hidden>
Date: Fri Jan 31 12:04:36 2014 +1300

    Disable file injection in baremetal by default

    DocImpact: This disables file injection by default for baremetal. File
    injection has never been very useful for baremetal given the much
    wider set of device configurations vs virtual, so it's unlikely anyone
    was using this (it cannot be used in a heterogeneous OS image
    environment, for instance). We should still document the change
    though.

    UpgradeImpact

    blueprint disable-file-injection-by-default

    Change-Id: I60a108ef1f0e46ad4da94d2a730426e255011476
    Co-Authored-By: Steve Kowalik <email address hidden>

Tom Fifield (fifieldt) on 2014-02-25
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → icehouse
Tom Fifield (fifieldt) wrote :

Confirmed the new setting has made it to the config reference. There's also a release note.

Changed in openstack-manuals:
assignee: nobody → Tom Fifield (fifieldt)
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers