Merge lp://staging/~ltrager/maas-images/image_index into lp://staging/maas-images
| Status: | Merged |
|---|---|
| Merged at revision: | 410 |
| Proposed branch: | lp://staging/~ltrager/maas-images/image_index |
| Merge into: | lp://staging/maas-images |
| Diff against target: |
242 lines (+85/-71) 3 files modified
bin/maas-qcow2targz (+17/-6) conf/centos.yaml (+1/-3) meph2/commands/mimport.py (+67/-62) |
| To merge this branch: | bzr merge lp://staging/~ltrager/maas-images/image_index |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Blake Rouse (community) | Approve | ||
| Scott Moser (community) | Needs Information | ||
|
Review via email:
|
|||
Commit message
Scan for CentOS images using the image-index provided by upstream
When CentOS support was initially added, we decided that CentOS should
follow the same path as Ubuntu. Upstream generates a generic cloud-image
and then lp:maas-images modifies the image to work for MAAS. When this was
first implemented upstream only supplied a sha256sum.txt file[1] for us to
scan for new images. Now, upstream is providing an
image-index [2] file which uses config file format.
The image-index[2] file is missing some older images the sha256sum.txt[1]
has but both contain the latest image file.
[1] https:/
[2] https:/
Description of the change
When I initially added CentOS support to lp:maas-images we decided that CentOS should follow the same path as Ubuntu. Upstream generates a generic cloud-image and then lp:maas-images modifies the image to work for MAAS. When this was first implemented upstream only supplied a sha256sum.txt file[1] for us to scan for new images. I noticed that upstream is now providing an image-index [2] file which uses config file format.
The image-index[2] file is missing some older images the sha256sum.txt[1] has but both contain the latest image file.
[1] https:/
[2] https:/
| Lee Trager (ltrager) wrote | # |
i think there are some logic problems.