simplestreams image metadata details inconsistent with tools
Bug #1246978 reported by
Ian Booth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth |
Bug Description
When using the metadata plugins to generate image metadata, the metadata files are written to the top level directory. This is also how juju expects to find the metadata when looking in the cloud storage. However, tools metadata is located in a tools subdirectory. Image metadata needs to follow this practice also. So using the same pattern as for tools, the base metadata directory will be called "images".
Another inconsistency is the tools-url vs image-metadata-url naming
Related branches
lp:~wallyworld/juju-core/simplestreams-consistency
- Juju Engineering: Pending requested
-
Diff: 589 lines (+78/-54)25 files modifiedcmd/juju/bootstrap.go (+1/-1)
cmd/juju/upgradejuju_test.go (+3/-3)
cmd/plugins/juju-metadata/imagemetadata.go (+4/-4)
cmd/plugins/juju-metadata/imagemetadata_test.go (+2/-2)
cmd/plugins/juju-metadata/validateimagemetadata.go (+7/-3)
environs/config/config.go (+3/-3)
environs/config/config_test.go (+4/-4)
environs/imagemetadata/generate.go (+3/-2)
environs/imagemetadata/generate_test.go (+1/-1)
environs/imagemetadata/testing/testing.go (+3/-2)
environs/imagemetadata/urls_test.go (+2/-2)
environs/imagemetadata/validation_test.go (+7/-2)
environs/storage/storage.go (+3/-0)
environs/tools/tools_test.go (+1/-1)
environs/tools/urls_test.go (+3/-3)
provider/azure/environ.go (+1/-1)
provider/azure/environ_test.go (+1/-1)
provider/dummy/environs.go (+2/-1)
provider/ec2/ec2.go (+3/-1)
provider/ec2/local_test.go (+1/-1)
provider/maas/environ.go (+4/-2)
provider/maas/environ_test.go (+1/-1)
provider/openstack/live_test.go (+1/-1)
provider/openstack/local_test.go (+8/-8)
provider/openstack/provider.go (+9/-4)
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.