> + osFamily = OsFamily.fromValue(from.getOSType().toLowerCase());
> + } catch (IllegalArgumentException e) {
> + logger.debug("<< didn't match os(%s)", from.getName());
> + }
> + boolean is64Bit = true;
> +// (from.getName() != null && from.getName().contains("64"))
> ||
> +// (from.getDescription() != null &&
> from.getDescription().contains("64")) ||
> +// (from.getLabel() != null &&
> from.getLabel().contains("64")) || osFamily == OsFamily.WINDOWS;
> +
> + return new OperatingSystem(osFamily, osName, osVersion, osArch,
> osDescription, is64Bit);
> + }
> +
> + @Override
> + public Image apply(OSImage from) {
> + ImageBuilder builder = new ImageBuilder();
> + builder.ids(from.getName());
This sets two fields: the `id` and the `providerId`. The former is the ID
jclouds will use to identify uniquely the image across all regions, and the
latter the *real* ID of the resource in the provider. Is this true in this case?
Usually jclouds uses a different ID and prepends the region to the provider ID.
Take this into accound to make sure the providerId and the id (which is the one
used when calling getImage(id) in the computeservice) are configured properly.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/132/files#r24748535
