Apache Whirr (retired)
  1. Apache Whirr (retired)
  2. WHIRR-326

Use jclouds provider metadata to help with cloud provider configuration

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.6.0
    • Component/s: cli
    • Labels:
      None

      Description

      The new ProviderMetadata class in jclouds 1.0.0 allows discovery of metadata for all supported providers. We could use this in the CLI to list the provider IDs and name of the credential to supply for Whirr. We could also have a list of providers we've tested with Whirr so this is shown to the user too.

      1. WHIRR-326.patch
        4 kB
        Andrei Savu
      2. WHIRR-326.patch
        10 kB
        Andrei Savu
      3. WHIRR-326.patch
        10 kB
        Andrei Savu

        Issue Links

          Activity

          Hide
          Andrei Savu added a comment -

          I've just committed this. Thanks Tom for taking a look.

          Show
          Andrei Savu added a comment - I've just committed this. Thanks Tom for taking a look.
          Hide
          Andrei Savu added a comment -

          Updated patch.

          Show
          Andrei Savu added a comment - Updated patch.
          Hide
          Tom White added a comment -

          +1 Looks good. Thanks for making the changes. One minor thing - I would have the configuration options grouped under the same heading as the other settings. E.g.

          * Rackspace Cloud Servers US - tested
          	Homepage: http://www.rackspace.com/cloud/cloud_hosting_products/servers
          	Console: https://manage.rackspacecloud.com
          	API: http://docs.rackspacecloud.com/servers/api/v1.0/cs-devguide/content/ch01.html
          	Configuration options:
          		whirr.provider = cloudservers-us
          		whirr.identity =  <Username>
          		whirr.credential = <API Key>
          
          
          Show
          Tom White added a comment - +1 Looks good. Thanks for making the changes. One minor thing - I would have the configuration options grouped under the same heading as the other settings. E.g. * Rackspace Cloud Servers US - tested Homepage: http://www.rackspace.com/cloud/cloud_hosting_products/servers Console: https://manage.rackspacecloud.com API: http://docs.rackspacecloud.com/servers/api/v1.0/cs-devguide/content/ch01.html Configuration options: whirr.provider = cloudservers-us whirr.identity = <Username> whirr.credential = <API Key>
          Hide
          Andrei Savu added a comment -

          How does the output look like? Usable?

          Show
          Andrei Savu added a comment - How does the output look like? Usable?
          Hide
          Andrei Savu added a comment -

          It should be ready. I really like this jclouds feature. Great work!

          Show
          Andrei Savu added a comment - It should be ready. I really like this jclouds feature. Great work!
          Hide
          Tom White added a comment -

          > we should add jclouds-allcompute

          Agreed.

          Regarding the patch, the output showing the whirr properties to set might be indented, and the provider names quoted in some way (e.g. <like this>). It would also be useful to have a link to the provider's home page, and the provider's full name, if it's available.

          We should also cover this feature in the configuration guide.

          Show
          Tom White added a comment - > we should add jclouds-allcompute Agreed. Regarding the patch, the output showing the whirr properties to set might be indented, and the provider names quoted in some way (e.g. <like this>). It would also be useful to have a link to the provider's home page, and the provider's full name, if it's available. We should also cover this feature in the configuration guide.
          Hide
          Andrei Savu added a comment -

          First iteration on this. I've noticed that we should add jclouds-allcompute as a dependency so that Whirr could (in theory) work with all the cloud providers supported by jclouds.

          Show
          Andrei Savu added a comment - First iteration on this. I've noticed that we should add jclouds-allcompute as a dependency so that Whirr could (in theory) work with all the cloud providers supported by jclouds.
          Hide
          Adrian Cole (Inactive) added a comment -

          this class is specifically org.jclouds.providers.Providers

          Show
          Adrian Cole (Inactive) added a comment - this class is specifically org.jclouds.providers.Providers

            People

            • Assignee:
              Andrei Savu
              Reporter:
              Tom White
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development