[
https://issues.apache.org/jira/browse/JCLOUDS-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769719#comment-15769719
]
Aled Sage commented on JCLOUDS-1108:
------------------------------------
+1 for this. It would be really useful to have for downstream projects such as
Apache Brooklyn. From a user's perspective, it's so much easier to do something
like (brooklyn yaml format below):
{noformat}
location:
google-compute-engine:us-central1-a:
hardwareId: n1-standard-1
{noformat}
Rather than:
{noformat}
location:
google-compute-engine:us-central1-a:
hardwareId:
https://www.googleapis.com/compute/v1/projects/jclouds-gce/zones/us-central1-a/machineTypes/n1-standard-1
{noformat}
Also, see (the closed PR)
https://github.com/jclouds/jclouds-labs-google/pull/171 for some older
discussion of this.
> GCE support for shorten hardwareId
> ----------------------------------
>
> Key: JCLOUDS-1108
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1108
> Project: jclouds
> Issue Type: Improvement
> Reporter: Andrea Turli
> Assignee: Andrea Turli
>
> I'd like to slightly change the MachineTypeToHardware to support hadwareId
> like `f1-micro` instead of the entire URI.
> I've also noticed that location should not be mapped in the HardwareBuilder
> as it is needed only when a the hardware is available only on a particular
> location.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
