Merge lp:~pwlars/uci-engine/snappy-imageimport into lp:uci-engine
Proposed by
Paul Larson
Status: | Merged |
---|---|
Approved by: | Paul Larson |
Approved revision: | 923 |
Merged at revision: | 922 |
Proposed branch: | lp:~pwlars/uci-engine/snappy-imageimport |
Merge into: | lp:uci-engine |
Diff against target: |
139 lines (+127/-0) 2 files modified
ubuntucore-importimage/glanceimage.py (+86/-0) ubuntucore-importimage/tests/test_glanceimage.py (+41/-0) |
To merge this branch: | bzr merge lp:~pwlars/uci-engine/snappy-imageimport |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Paul Larson | Approve | ||
Celso Providelo (community) | Approve | ||
Review via email: mp+246484@code.launchpad.net |
Commit message
Add a cli/api to download a specified image and put it in glance.
Description of the change
This is just the simple tool to take an image, download it, and import it into glance.
To post a comment you must log in.
Paul,
Thanks for working on this, the CLI does what is expected.
I am unsure about its location as an separated module. At least, we should s/snappy/ ubuntucore/ , but I don't like much the idea of creating a new module/directory for each CLI we planned, it is unnecessarily confusing and hard to find.
It needs ci_utils, so if we are going to fork/subprocess to it, we need `run-python` and the scripts could live in an agnostic common path, let's say bin/ or ubuntucore/bin/, because for now we deploy the whole uci-engine tree on nodes.
If we intend to import and use publish_image() inside workers, it should be a module (as the other ci-airline modules) and all CLIs could live in a module, let's say 'ubuntucore', which will eventually provide worker implementations for the services we need.
Any thoughts ?
[]