boto should not be a dependency when not using ec2 api/s3

Bug #949631 reported by Chris Behrens on 2012-03-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Chris Behrens

Bug Description

For production installations, it should not be required to install boto when not using ec2/s3 auth.

Chris Behrens (cbehrens) wrote :

I'm getting an import error when trying to import nova.virt.connection... somehow this tries to import nova.auth.signer which wants boto and boto.provider.

Fix proposed to branch: master

Changed in nova:
status: New → In Progress
Chris Behrens (cbehrens) wrote :

Note my above comment is addressed by this:,5061

Scheduler was also importing ec2utils which ended up thru a tree of dependencies.. also importing nova.auth.signer.

That's fixed by this:,5065

That leaves bin/nova-manage... which I've filed a review linked to this bug:,5069

All of these together should address this bug.

Submitter: Jenkins
Branch: master

commit 1e551c06bc549b43daa8aa19282c68614ef86c97
Author: Chris Behrens <email address hidden>
Date: Wed Mar 7 22:43:12 2012 -0800

    boto shouldn't be required for production deploys

    ... if you're not using ec2/s3.

    Fixes bug 949631

    bin/nova-manage imports auth.manager which imports auth.signer which
    tries to import boto... but nova-manage doesn't try to authenticate.

    This patch allows bin/nova-manage to work if you don't have boto

    Change-Id: I9b7929a15b991498ab0491821521ec20ed0da65c

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-03-20
Changed in nova:
milestone: none → essex-rc1
status: Fix Committed → Fix Released
Mark McLoughlin (markmc) on 2012-04-03
Changed in nova:
assignee: nobody → Chris Behrens (cbehrens)
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers