use entry_points for binscripts

Registered by Michael Basnight on 2013-12-27

The binscripts can be generated using entry_points/console_scripts in the setup.cfg. This means the binscripts should contain no real code, and the code can be moved to trove/cmd. This is where the other projects store their entry_points for their binscripts. This also means its easier to test the binscripts since they are in the source tree now.

** One thing to note is that the guest, since its going to be installed differently and moved, will not participate in this. the guest binscript will be moved into contrib/ so it can be run in the image build.

Blueprint information

Status:
Complete
Approver:
Michael Basnight
Priority:
Medium
Drafter:
Michael Basnight
Direction:
Approved
Assignee:
Michael Basnight
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Michael Basnight on 2013-12-27
Completed by
Michael Basnight on 2014-02-07

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/entrypoints-for-binscripts,n,z

Addressed by: https://review.openstack.org/54225
    make the bin scripts called with main()

Addressed by: https://review.openstack.org/64310
    Migrating to entry_points for binscripts

(?)

Work Items

Work items:
trove: DONE
devstack: DONE
integration: INPROGRESS

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.