Cloud Deployment Manager

How can we improve the Cloud Deployment Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Support Cloud DNS

    Please add support for managing Cloud DNS records from Deployment Manager. This would let us add external DNS records for deployed resources automatically.

    11 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    • Upgrade paths for deployments.

      It seems you cannot upgrade versions of your deployments, we went through all the manual effort of upgrading our deployed mongo servers from 2.6 to 3.2 only to find after reboot they've all rolled back to 2.6 because of the mass of startup scripts =/

      3 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        0 comments  ·  Flag idea as inappropriate…  ·  Admin →
      • Replace VMs when the source image changes in the deployment definition

        Currently if one uses an immutable infrastructure approach where most parts are baked into images you cannot easily replace VMs that are deployed by the deployment manager.

        If you update the source image field in the VM definition the API returns an error that this is not an update-able field.
        So currently changing the image is two updates to the deployment manager. One without the VM in the spec which causes it to delete the VM and another one with the new VM in the spec.

        It would be nice to have an option where I can update the field…

        3 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  Flag idea as inappropriate…  ·  Admin →
        • 2 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            0 comments  ·  Flag idea as inappropriate…  ·  Admin →
          • 1 vote
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  Flag idea as inappropriate…  ·  Admin →
            • Don't see your idea?

            Cloud Deployment Manager

            Feedback and Knowledge Base