Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31672

Unable to set keypair in CloudStack

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • jclouds-plugin
    • None
    • - Jenkins 1.609.1
      - jclouds-plugin 2.8

    Description

      Hi, we're currently using the jclouds-plugin to provision slaves in an Apache CloudStack environment, although the form supports a "keypair" option it seems, after looking in the source code, that it's only used for an OpenStack configuration.

      It'd be great to have it available to use in CloudStack, at the moment we need to setup our templates to have a valid user which gives access to JClouds, this setup is insecure and we're trying to rely only on CloudStack provisioning for setting up ssh keypairs.

      Attachments

        Activity

          felfert Fritz Elfert added a comment -

          I have made the required changes, however before making a release, I would like to add a help-text for that keyPairName in the Form.
          Since I never used keyPairNames myself, I would need a little help here: Is that the name of a keypair which is somewhere defined on the CloudStack side? What is its purpose exactly?

          felfert Fritz Elfert added a comment - I have made the required changes, however before making a release, I would like to add a help-text for that keyPairName in the Form. Since I never used keyPairNames myself, I would need a little help here: Is that the name of a keypair which is somewhere defined on the CloudStack side? What is its purpose exactly?
          felfert Fritz Elfert added a comment -

          Fixed in git

          felfert Fritz Elfert added a comment - Fixed in git

          People

            felfert Fritz Elfert
            victorcampos Victor Campos
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: