Customer Feedback

Please post ideas, areas for improvement, and problems you see in your current IT operations that you think we’re in the best position to solve. Rants, personal attacks, advertising, or off-topic posts may be removed by RightScale moderators.

I wish ...

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…)
Reset

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

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

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

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

  • Hot ideas
  • Top ideas
  • New ideas
    1. Need more granular role based permission/security

      Currently from the Rightscale security list you either need to completely lock it down or completely open it up and there is no in between. I need something that is more granular for example:
      1) Give only permission for a user to modify inputs and run a script.
      2) Give permission to only specific deployments
      3) Give permission to only specific servers

      Basically we need a matrix that goes through all the Rightscale components such as servers, templates, deployments, security groups, ssh keys, credendial, arrays etc...

      87 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      5 comments  ·  Security  ·  Admin →

      All – this has gone into development.

      One architectural nuance that has come up is that for Enterprise plans, we plan to create enterprise-wide groups and allow you to manage group membership across the enterprise. However, the permissions would be local to the account. For example, you could add Bob to the sysadmins group across all accounts in the enterprise, but whether the sysadmins could import STs or operate deployments would be on a per-account basis and would have to be set account-by-account. This means that when a new account is provisioned the standard set of groups would need to be assigned appropriate permissions, but then to add/remove users could be enterprise-wide.

      Please comment on this approach.

      Or, if you’re willing to review the wireframes with us to provide feedback, please let me know.

      Thank you,
      Darryl

    2. For a given deployment, merge graphing together for all instances, both existing and terminated.

      Right now, the only way to view monitoring data for a terminated deployment is to hunt the given server down in the EC2 terminated instance list. Instead, I think it would be a great benefit to have all this data tracked in the monitoring panel for the deployment and kept there as a history of all activity. Particularly for merging data from various array instances of the same type, I think this would be highly useful to track overall deployment health, especially as the array grows and shrinks over a given time period. Aggregating these results otherwise would be a… more

      77 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  5 comments  ·  Monitoring  ·  Admin →
    3. I'd like to be able to update the Current Inputs for an entire deployment.

      You can only change current inputs at the server level. I would like to be able to view and update current inputs (not just next inputs) at the deployment level so that I can run a script across a deployment that uses the new value.

      72 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    4. to have some more secure login options

      Having a single password for login in Rightscale seems very dangerous to me from a security standpoint. If an admin password were somehow comprimised, a malicious user would have access to the entire deployment and could essentially do anything. It would be nice if there were some additional security in this regard. For example:

      a) The ability to disable an admin account from direct login. This would require some ability to switch users once logged-in in order to do admin tasks (similar to an 'su root' in Unix).

      b) Two-factor authentication, maybe using some kind of physical object like SecureID;… more

      52 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      5 comments  ·  Security  ·  Admin →

      We recently added token-based authentication to the API, and we’re currently developing SAML 2.0 support to the dashboard. After this, we will create a setting to disallow password login from both Dashboard and API.

      This will force users to go through either an OpenID login (Google Authenticate, for example, will give you a two-factor login for OpenID sites), or a SAML login.

      If you have any questions, or would like to try the SAML private beta, please let me know.

    5. Additional chef support (debugging, roles, chef 0.10)

      3 ideas:
      1. Better output from chef when things go wrong. Right now the output from RightLink is entirely too terse (1 stack frame in backtraces, etc). [DONE w/ RightLink 5.7]

      2. Support for chef roles. This would allow a user to specify which chef roles a server template is to fulfill instead of having to include the recipes for each of those roles. [Moved to idea http://bit.ly/zNQb6o]

      3. The RightLink/RightScale sandbox is currently limited to 0.8.16. Chef 0.10.0 is currently the newest. [Planned]

      47 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  RightScaleAdminRightScale (Admin, RightScale) responded

      We are moving this from imminent to planned as we completed the improved debugging. Rightlink 5.8 is currently under development and includes Chef 0.10.2.

      We are putting chef roles into a new topic: http://bit.ly/zNQb6o

      Please add votes to the new topic if you are interested in support for Chef roles.

    6. Mobile Device UI

      Quite often I find myself needing to access the rightscale dashboard from my mobile device(s): iphone, ipad, etc.

      The current site works (mostly), but it is heavy and hard to use.

      Please add a mobile UI or maybe an app?

      41 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    7. Add Support for Chef Roles

      Allow user to specify which chef roles a ServerTemplate is to fulfill instead of having to include the recipes for each of these roles.

      (This task was broken out from a previous task:
      http://feedback.rightscale.com/forums/94975-customer-feedback/suggestions/1788629-additional-chef-support-debugging-roles-chef-0-?ref=title)

      37 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      backlog  ·  0 comments  ·  ServerTemplates  ·  Admin →
    8. Collapsable Folders in RightScale UI for large lists

      i have a hard time managing the sheer quantity of templates and scripts that are shown within the rightscale ui after importing a significant number of published templates. i'd like to see some tools that would help me logically organize these items so that i can better manage them.

      i think something similar to collapsable folders would help me organize the views of the templates and scripts. currently everything is in a flat listing that i have to page through.

      i'd like to have to ability to define the folders and i'd like to be able show/hide folders from my… more

      33 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    9. Database Manager for MongoDB

      I'd like to see a Database Manager for MongoDB so that I can use this as the backend for my application servers.

      33 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  2 comments  ·  ServerTemplates  ·  Admin →
    10. More verbose API output for server array instances

      Current API for server array instances is lacking output for EC2 instance types and pricing (on demand or spot). It's limiting our capabilities to use the API for accounting and planning purposes.
      It would be very useful to bring arrays instances describe API output closer to describe API output for normal servers.

      27 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  API  ·  Admin →
    11. Issuing RS Commands and executing RS Scripts on individual array instances, via the API

      Currently operations are impossible to perform on array instances through the API. This would be very useful for cleanly removing array instances, and dramatically empower API interfacing.

      26 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2 comments  ·  API  ·  Admin →
    12. Provide aggregate logging for a deployment

      I like how RS can bring server logs into the UI, and can be useful. However, this doesn't scale well when you add more and more servers.

      It would be great if there were a way to access an aggregate of all logs at the deployment level, not just at a single instance.

      This would be useful for frontend application level logging as well as server logging.

      25 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    13. Allow alerts to be created on cumulative CPU

      Alerts and auto-scaling based on single CPU e.g. CPU-0 cause unnecessary false positives and cost because the other CPUs might be idle.

      22 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  1 comment  ·  Scalable Arrays  ·  Admin →
    14. Ruby 1.9.2 for RightLink

      It would be nice if the default ruby installed is 1.9.2.
      Ruby 1.9.2 has been out for a while. Making our scripts to work with 1.8.7 seems like a downgrade. We can barely run rightscripts in 1.9.2 after installing rvm, but we cannot run Chef recipes.

      19 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      backlog  ·  1 comment  ·  RightLink  ·  Admin →
    15. API read access for server array inputs

      Provide read access to server array inputs (equivalent to <parameter> element on standalone server show output).

      This information should be made available both for the next launch (current array settings) and for any running instances when accessing the hrefs included in the api/acct/1/server_arrays/1/instances endpoint. (Note: hrefs currently provided in that endpoint are not valid.)

      16 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  API  ·  Admin →
    16. RightScale should create a non-privileged Unix user on instances for authorized RightScale users

      RightScale should create a non-privileged Unix user on my instances for every authorized RightScale user, so I can preserve the audit trail for my users' actions and limit their privilege on the instance. Without this feature, I must disable server_login for everyone I don't have absolute trust in. This significantly impairs my employees' ability to use RightScale and makes me want to consider other options.

      16 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  1 comment  ·  Security  ·  Admin →
    17. Deployment monitoring graphs would retain their collapsed or uncollapsed state

      Currently the deployment monitoring graphs will not retain their collapsed or uncollapsed state. We have to constantly click open all the monitoring bars each time we go to the page.

      16 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    18. Input Validation

      We need an ability to validate inputs prior to launching the server. For e.g. Regular Expression Validation , Date validation , Number validation.

      We currently have 150 + deployments and it is so easy to make a mistake and realizing the impact.

      14 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      backlog  ·  0 comments  ·  Admin →
    19. Add tags to EC2 instance

      When I tag instances in RightScale, it would be nice if the related Amazon EC2 instance shared the same tags.

      13 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2 comments  ·  Clouds  ·  Admin →
    20. Ability to add Monitoring Graphs of Array Servers to QuickMonitoring

      I know there are issues in adding dashboard monitoring to array servers (i.e., when array scales up or down), but even if the quick monitoring is static, it would be a big help for me to have the ability to add some graphs from the array servers to the quick monitoring side bar.

      13 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Dashboard  ·  Admin →
    ← Previous 1 3 4 5 6 7 8 9 10 11 12
  • Don’t see your idea?
  • Post a new idea…
  • Knowledge Base and Helpdesk