184 results found
-
Provide Anycable integration support
Provide Anycable integration support. Tutorial about setting the gRPC server and serving it on a separate port
4 votes -
Instant and Full Rollbacks
Instead of running a full rebuild which can take a very long time when things are broken, use the last build. Capistrano stores the builds and it completely defeats the purpose of their existence if we never use them. It would take a few seconds at most to rollback a problem vs waiting for an entire new build. For our stack that's over 10 minutes of downtime.
My proposed solution based on some chats in Slack is to have both an Instant and Full Rollback option since I was told some stacks have deploy hooks that need to be rerun.…
4 votes -
Add Softlayer as a cloud provider
Softlayer has an extremely robust network, and they also have a CloudLayer VPS solution. It would be great to implement C66 with Softlayer.
4 votes -
Reboot cluster servers requiring reboot automatically
At least for load balanced servers it should be easy to handle automatic rebooting. Just remove them from the load balancer, reboot and then add them back.
For load balancer and other services that can't be rebooted without service downtime, it would be nice to be able to assign a maintenance window. During the window, the stack would be taken to maintenance mode, servers requiring reboot would rebooted and then the maintenance mode would be lifted.
4 votes -
Integrate with Spotinst
Spotinst (https://www.spotinst.com) is a a sophisticated cluster software and prediction purchasing algorithm for EC2 and GCE resources. By leverage spotinst you can bring the cost down of EC2 and GCE resources and still have enough power to run your applications.
3 votes -
Update Hipchat Integration (Hipchat API v1 is deprecated)
Hipchat API v1 is deprecated. New users of Hipchat can't create v1 keys, so notifications aren't showing up.
Here's some background from a similar request of New Relic:
https://discuss.newrelic.com/t/hipchat-v1-api-is-deprecated-please-use-v2-oauth-room-tokens/259433 votes -
3 votes
-
Support for Elasticsearch plugins autoinstall
It would allow to install plugins in a Elasticsearch install. For example https://github.com/sonian/elasticsearch-jetty
3 votes -
Add a validator for configuration files
As a user, it would be helpful to me if you had a validator for the .cloud66 configuration files. While it's easy enough to test that the files are valid YAML currently, I would also like to see specific validation of the configuration options.
3 votes -
Change DNS settings
if have a suggestion. I got a performance problem with the Twitter gem. Got a lot of timeouts.
After investigating the problem. I found out that the DNS servers Digital Ocean is using (/etc/resolv.conf) are the public Google ones. Those DNS services are rate limeted and slow down performance if you are using outbound traffic, like trying to access the api.twitter.com service. My suggestion is to use other DNS services that 4.4.4.4 and 8.8.8.8 or make it editable.
3 votes -
Support Multi-Master Databases
When deploying globally, it'd be nice if db writes could take place using the local db shard rather than a single master half way around the world. Scaling is incredibly limited without this.
3 votes -
Import a database from another stack via API
Ability to import a database from another Stack via API - accessible
from the interface.
3 votes -
Improve ssh keys names
At the moment you use (at least on digital ocean) key names like c66-uselesslonghashprobablybasedonthestackid, it would be much more useful having c66-nameoftheserver. That would make much easier to see which keys are from old servers and that can be safely deleted
3 votes -
Navigation structure is quite confusing
The nested nature of a lot of the config screens, along with what appears on each is quite confusing.
I managed to totally miss how to add a Redis server after initial deployment despite seeing I could create it as an Addin - I couldnt find the Addins page, and then couldnt find the "+" icon after I cound the section
I also managed to totally miss the Redis Servers page "Configure Redis" button as it is a de-highlighted blue button far to the right - it really should be in the main flow of the page
3 votes -
3 votes
-
allow deploy hooks on haproxy instances
I'd like to automate things such as installing newrelic monitoring when spinning up haproxy load balancer instances. Currently, I do this using deploy hooks on application servers and it works great. If I could do the same on haproxy servers, I'd be thrilled.
3 votes -
Don't automatically enable processes
When a Rails app is deployed for the first time with a Procfile (and I think also when a processing server is added), 1 process is automatically booted for each entry in the Procfile.
This is bad for at least two reasons:
Testing - processing may begin before you can verify deployment was configured correctly (e.g all correct environment variables have been set, connecting to correct DB, etc)
Resource exhaustion - deployments with many Procfile entries could lead to lots of unnecessary connections being made to databases, and preventing other applications from accessing these resources.
We have about 3 dozen…
3 votes -
Bahnhof Cloud provider support
Bahnhof is known for their security measures and would be a welcome Scandinavian provider. For those who take security and privacy into the equation (next to performance and price) Bahnhof would be a great option.
3 votes -
add support for rollbar
I need to be able to see, monitor and record errors that are happening on a live production server.
3 votes -
accept deploy hooks when the stack is in deployment lockdown
I put my stack in deployment lockdown mode to prevent deploys of new docker images. What happens is that all CI deploys (which build the docker images and trigger the deploy hook on git push) fail as the deploy hook returns:
{"ok":false,"message":"stack requires authorization to deploy and can therefore not use redeployment hooks"}I'd rather have it return an non-error message with the hint to pending deploy authorization, like:
{"ok":true,"lockdown":true,"message":"stack requires authorization to deploy, your deployment request has been issued"}With deployment lockdown, I want to turn off automatic deploys, but I'd love to have them scheduled for review so…
3 votes
- Don't see your idea?