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...133 votes
Please contact me directly if you’re interested in providing input through a wireframe review.
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 manual and tedious process. This would also be extremely useful in tracking the history of a given server when new instances go up-and-down, like between various deployments of your MySQL master.
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…80 votes
We recognize that RightScale monitoring needs some work. Timeframe is undefined, but we will get back to this group when we have some new ideas or prototypes to share.
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:
Although we still don’t support Roles natively in RightScale, we now offer a Chef Client ServerTemplate if you prefer to use a Chef Server to configure your nodes instead of RightScale: http://goo.gl/WVylxC
As part of our BYOCM strategy (http://goo.gl/qdM90L), we will support Roles through Chef Server initially and may eventually implement something similar in the RightScale platform.
Allow git repos to be used when pulling RightScript code. Similar to the way that RepoPaths work for cookbooks, having RightScripts pull from git allows our own version control along with easier editing techniques rather than copy pasting from our favorite editor.50 votes
We are planning on creating a structure that can be stored in git to house RightScripts and the associated metadata.
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?44 votes
We have partnered with Cloud Scope to deliver an iOS app which can be found here http://www.mobilegridinc.com/products/cloudscope/rs. We are still looking at a mobile site, but unfortunately do not have a timeline to share. Please leave additional comments or email me if you have needs for an Android or mobile site app.
Today - Dec 18, 2012, Amazon announced Elastic Block Store (EBS) Snapshot Copy.
It sounds dreamy. I'm putting in a vote to have it supported in Rightscale.37 votes
This is valuable. We’re looking at how and when to incorporate this feature.
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.35 votes
Currently, RightScale only allows you to select from a predetermined set of repositories. We manage our own repositories for RPMs. When specifying packages for a RightScript, it will only automatically install packages from the initial set of repositories configured prior to boot. As a result, we need to always manually run "yum -y install package_name" after we've added our custom repo to /etc/yum.repos.d/.29 votes
Seems like a good one. We need to make some changes to our agent to make this possible, which will take some time. The value is clear to me, so I will put this on the backlog and work through iteratively getting the agent updated before making this capability available at the ServerTemplate level. Please let me know if you have any questions.
When viewing a server, it would be nice to see what its a part of. For example,
Deployments > Deployment A > Server Name
When you have multiple deployments, it can sometimes become cumbersome seeing where you're at and getting back and forth.29 votes
We are working on a redesign which will provide a way to quickly retrace the path and we are considering breadcrumbs in certain areas of RightScale UI
a public bug tracker would be great!
if anyone run into a bug resulting in a stranded server for example, it would be possible to search through the bug tracker, if the bug is already known.
this will save a lot of time of error analysing and workarounds.28 votes
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.28 votes
This effort will be included in the next version of RIghtLink, which is slated for Q1 2014. More updates will be posted when we have clearer line of sight.
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.27 votes
This has been worked through and we are conducting usability studies on this capability before it goes into engineering. Thank you!
It will be useful to have API to update RightScript, because in some cases( including while developing script ) we want update it through an api.27 votes
With the last release, you are now able to take some actions with RightScripts through the API. Although you still cannot update the content of a RightScript, you can change how RightScripts are used in ServerTemplates: http://bit.ly/1eNm75O
Updating RightScript content will come in the future.
Currently published ServerTemplates are not deletable, even if they were only shared privately. I would like the ability to clean up ServerTemplates that are no longer needed.25 votes
Unfortunately this feature didn’t make the Feb release, but expect to see it in a release soon.
I want to update alerts of multiple running or next servers.22 votes
Updating alerts on running array instances has been shipped.
For updating alerts on running servers, the task is in the backlog.
1. A server is cloned to have an equivalent in another cloud. Inputs/tags/alerts defined at the server level will be copied to the clone.
2. A deployment with AWS(us-east-1) servers is cloned from the dashboard to have an equivalent in another cloud(ex: eu-west-1). For large deployments, API could be used to change the cloud and resources like ssh keys, security groups.21 votes
This capability is on the backlog.
It would be nice when viewing RightScripts and ServerTemplates that you could have a field indicating that they are used. I imported\cloned a lot of scripts and templates when I was first setting up my account, now it is very cluttered with unused ones. It would nice to be able to sort by a field indicating that the script or template is not used and bulk delete them from the account.21 votes
Using RightScale there is no way to specify/override boot device mappings in the case of EBS based AMIs.
I want to use a secondary ephemeral(SSD) drive on C3 instances.20 votes
We expect to address this request later this year in 2014.
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.19 votes
Added to backlog
I find that I've no idea how the autoscaling actually works for my applications. It seems to do its thing, but what I'd really want to see is a historic graph of instance counts per status. Eg: 5 running, 1 booting, 1 stranded. But historically with lines and all that. This way I can see easily over time when there was issues (ie instances strand), when are the usual times my arrays scale up/down, etc.
This would be array level graph, not really related to any of the collectd stuff normally graphed.19 votes
- Don't see your idea?