Skip to content

General

General

Categories

184 results found

  1. Currently with MaestroV2, our pods with replicas are being deployed on the same nodes at times which defeats the purpose of our highly available pods running on a single node in our multi-node cluster.

    I'm proposing adding a feature to Maestro to incorporate the Kubernetes concept of Pod Affinity/Anti-Affinity to allow Kubernetes to schedule pods to separate nodes based on what pods are already scheduled on the nodes.

    Here is the documentation from Kubernetes on the Pod Affinity/Anti-Affinity concept: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. support latest release of mongoDB

    36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Creating cron tasks through the interface works great with the error handling etc attached. If we do this through whenever gem or our own cron we don't get the nice c66 features. So it would be great if we could configure the crons in cloud66 manifest and have them behave as c66 cron job.

    Right now I have to manually add the jobs in the UI in the staging env, then remember to manually add them again when we deploy to production and then remember to manually add them again in the case of server rebuild.

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Support the application servers connecting to Postgres over SSL (preferred) or even over a SSH tunnel.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The idea is to take advantage of AWS spot instances for some periods when heavy background processing is going on — i.e. temporarily scale up using spot instances.

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I would love an option for backups to be encrypted, so my user data is save and unreadable for people who find my backups.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. I'm very familiar with the "classic stack" approach with Cloud66. I'd be interested to see a demo and explain the benefits of deploying a standard Rails app using the docker approach.

    Perhaps you could also demo the new Cloud 66 Starter tool.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. It should be pretty straight forward as it is a drop-in replacement for MySQL. MariaDB is often performing better than MySQL and community improvements from Facebook, Twitter, Google, and Percona all roll into MariaDB sooner than they appear in MySQL.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Allow for a stack's configuration to be saved into a template and for stacks to be created from those templates.

    One potential use is turning up and tearing down staging environments. Bonus points for also allow a hook into your cap deploy:setup process to bootstrap additional environment-specific data (such as sample data).

    It'd also be nice to be able to edit the env variables from the template before kicking off the new build.

    This could also be used to implement a 'clone stack' function by optionally combining create template + create stack from template.

    I know this is mentioned elsewhere,…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Currently the only way to disable a job is to make it run on demand. Then when you turn it back on you have to remember the original time/frequency setting.

    Could we instead simply toggle it on and off without losing settings?

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Allow assigning multiple SSL certs to a single stack, leveraging nginx's existing SNI support.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. It looks like repo are re-cloned at every server deployment instead of just a pull. We need a way to change this behaviour to remove our 3 minutes waiting time at every server deployment.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. The version of Nginx installed doesn't have IPv6 enabled. If this was enabled, we could offer IPv6 connections to our clients.

    Some useful info on IPv6 and Nginx is available here:

    http://www.lowendguide.com/3/networking/enabling-ipv6-support-in-nginx/

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. It would be great if I could create two Redis servers with different settings. One would be a cache server and the other server would be used for persistent data.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. We have a BETA stack which we bring up every now and then when we need to test new features before deploying to production.

    It would be great if it was possible to freeze/suspend a stack.

    I imagine hitting freeze on the stack, it takes a full backup of my database, save the current git repos id, cancel my servers (or ask me to do it). On a later time I can hit the unfreeze button, it will then setup new cloud servers, install software, use the specific git repos id, restore the backup, and setup the elastic address to…

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Atlassian is discontinuing support for Hipchat, and moving customers to their new product Stride. Integration would be much appreciated.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. The nginx pagespeed module is a great way to speed up websites. https://github.com/pagespeed/ngx_pagespeed

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Please support stacks with mongodb which is not driven by mongoid(like when using the mongo-ruby-driver) - and enable backups for the entire mongo server - not for specific dbs in the server.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 9 10
  • Don't see your idea?