Details

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

      Description

      Developing a libCloud driver for the IBM Developer Cloud.

      1. IBM Developer Cloud REST.pdf
        430 kB
        Eric Woods
      2. 100427 IBM Developer Cloud.txt
        48 kB
        Eric Woods
      3. 100419 IBM Developer Cloud complete.txt
        47 kB
        Eric Woods
      4. 100402 IBM patch.txt
        31 kB
        Eric Woods
      5. 100331 IBM patch.txt
        7 kB
        Eric Woods

        Activity

        Hide
        Paul Querna added a comment -

        Committed to trunk.

        Show
        Paul Querna added a comment - Committed to trunk.
        Hide
        Eric Woods added a comment -

        Addressed comments by Paul Querna:

        Comments on the patch:

        • HOST = 'www-180.ibm.com' ---- Is this a long term DNS name for your service? It seems
          like a 'random' webserver. Is it feasible to use something like developer-cloud-api.ibm.com

          >> This is the current address used for the IBM Developer Cloud while it's in beta. I expect a more permanent address in the future.
        • in parse_error, it raises InvalidCredsException(self.error), but self.error is essentailly
          HTTPResponse.reason. Is there more data that can be parsed out of the body?
          >> Great catch – a more descriptive reason is now given for authentication issues (when available).
        • in create_node:
        • it uses as an optional kwarg publicKey. It should also look for an auth parameter with
          the type of NodeAuthSSHKey, and then use that if present.
          >> Modified to only use the public key in the 'auth' parameter if provided.
        • Any examples of what configurationData would be used for? Its kinda an opaque blob, and
          I don't know what it should be used for.
          >> The 'configurationData' is a dictionary of image-specific configuration parameters when creating an instance. The supported parameters are defined in a parameters.xml file on the cloud for each image. The URL to this file is given in the NodeImage's extra['parametersURL']. I've added this to the documentation for create_node().
        • in _to_location, it uses 'USA' as the country, this should be 'US', as country is supposed
          to be the ISO 3166 country code.
          >> Done.
        Show
        Eric Woods added a comment - Addressed comments by Paul Querna: Comments on the patch: HOST = 'www-180.ibm.com' ---- Is this a long term DNS name for your service? It seems like a 'random' webserver. Is it feasible to use something like developer-cloud-api.ibm.com >> This is the current address used for the IBM Developer Cloud while it's in beta. I expect a more permanent address in the future. in parse_error, it raises InvalidCredsException(self.error), but self.error is essentailly HTTPResponse.reason. Is there more data that can be parsed out of the body? >> Great catch – a more descriptive reason is now given for authentication issues (when available). in create_node: it uses as an optional kwarg publicKey. It should also look for an auth parameter with the type of NodeAuthSSHKey, and then use that if present. >> Modified to only use the public key in the 'auth' parameter if provided. Any examples of what configurationData would be used for? Its kinda an opaque blob, and I don't know what it should be used for. >> The 'configurationData' is a dictionary of image-specific configuration parameters when creating an instance. The supported parameters are defined in a parameters.xml file on the cloud for each image. The URL to this file is given in the NodeImage's extra ['parametersURL'] . I've added this to the documentation for create_node(). in _to_location, it uses 'USA' as the country, this should be 'US', as country is supposed to be the ISO 3166 country code. >> Done.
        Hide
        Paul Querna added a comment -

        Comments on the patch:

        • HOST = 'www-180.ibm.com' ---- Is this a long term DNS name for your service? It seems like a 'random' webserver. Is it feasible to use something like developer-cloud-api.ibm.com
        • in parse_error, it raises InvalidCredsException(self.error), but self.error is essentailly HTTPResponse.reason. Is there more data that can be parsed out of the body?
        • in create_node:
        • it uses as an optional kwarg publicKey. It should also look for an auth parameter with the type of NodeAuthSSHKey, and then use that if present.
        • Any examples of what configurationData would be used for? Its kinda an opaque blob, and I don't know what it should be used for.
        • in _to_location, it uses 'USA' as the country, this should be 'US', as country is supposed to be the ISO 3166 country code.
        Show
        Paul Querna added a comment - Comments on the patch: HOST = 'www-180.ibm.com' ---- Is this a long term DNS name for your service? It seems like a 'random' webserver. Is it feasible to use something like developer-cloud-api.ibm.com in parse_error, it raises InvalidCredsException(self.error), but self.error is essentailly HTTPResponse.reason. Is there more data that can be parsed out of the body? in create_node: it uses as an optional kwarg publicKey. It should also look for an auth parameter with the type of NodeAuthSSHKey, and then use that if present. Any examples of what configurationData would be used for? Its kinda an opaque blob, and I don't know what it should be used for. in _to_location, it uses 'USA' as the country, this should be 'US', as country is supposed to be the ISO 3166 country code.
        Hide
        Eric Woods added a comment -

        Mistakenly marked the issue as resolved. Still waiting for patch to be committed.

        Thanks,

        • Eric
        Show
        Eric Woods added a comment - Mistakenly marked the issue as resolved. Still waiting for patch to be committed. Thanks, Eric
        Hide
        Eric Woods added a comment -

        The IBM Developer Cloud driver has complete functionality and tests.

        Show
        Eric Woods added a comment - The IBM Developer Cloud driver has complete functionality and tests.
        Hide
        Eric Woods added a comment -

        The IBM Developer Cloud adapter with full functionality and tests. Feedback appreciated.

        Show
        Eric Woods added a comment - The IBM Developer Cloud adapter with full functionality and tests. Feedback appreciated.
        Hide
        Eric Woods added a comment -

        REST API spec for the IBM Developer Cloud.

        Show
        Eric Woods added a comment - REST API spec for the IBM Developer Cloud.
        Hide
        Eric Woods added a comment -

        Patch includes test class structure a fixtures. One test method has been implemented for proof of concept.

        Show
        Eric Woods added a comment - Patch includes test class structure a fixtures. One test method has been implemented for proof of concept.
        Hide
        Eric Woods added a comment -

        Patch that includes the framework for the new IBM Developer Cloud adapter. For proof of concept, I've implemented list_nodes, list_images, list_sizes, and list_locations

        Show
        Eric Woods added a comment - Patch that includes the framework for the new IBM Developer Cloud adapter. For proof of concept, I've implemented list_nodes, list_images, list_sizes, and list_locations

          People

          • Assignee:
            Unassigned
            Reporter:
            Eric Woods
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 336h
              336h
              Remaining:
              Remaining Estimate - 336h
              336h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development