I agree that I'd like to see features that are extending the Scalr services rather than turnkey servers services that I could install myself. I think the only exception for me would be the syslog. I would still put the accounts/permission groups first though. We currently have no way that we can allow more Jr level support people access to restart servers or fire up dev machines if needed.
On Wed, Jul 21, 2010 at 8:47 PM, Donovan Bray <[email protected]> wrote: > Looking at the whole roadmap the only things that peaked my interest > are the following: > > Accounts and Environments > Add team access to your Scalr account, with read/write permissions to > your infrastructure (We need this) > Add multiple Environments to your Scalr account, to use dedicated keys > for your development and production environments, or to manage your > clients (this is a reality for us, we have two scalr accounts that > separate our corp instances from our production instances, and I would > further like to separate our production instances from our development > instances) > > To me its like legos. I need SCALR to make me the fundamental bricks > that I can't build for myself, and then I can arrange those bricks > into functional creations. > > I would like SCALR to be going gangbusters on the bricks like this > > - Raid over EBS > - Accounts and Environments > > And to a much lesser extent services. (because if we really wanted > these services any moderately skilled sys-admin can build them now > with the tools you already provide, like I did with rsyslog). Don't do > a service you don't love or consume yourselves, because once you offer > it, your going to be married to it, support and all. > > - integrated centralized logging with capable search UI. > - Scalable services (Cassandra, more suggestions? ffmpeg?) > > And leave the: > > - Scalable apps (Drupal, more suggestions?) > > To the community, because this list won't end. The moment you have > Drupal, you'll have a request for 10 other CMS's. Then the flames of > why Drupal but not WordPress when you have to draw the line somewhere > to stop the insanity. There are enough services you could implement > that will keep you busy so that you never ever have to touch a high > level application such as these, and the SCALR community will be the > better for it. > > On Wed, Jul 21, 2010 at 5:33 PM, Sebastian Stadil <[email protected]> > wrote: > > Thanks for the input, Donovan. > > > > Anything on the Roadmap that you could be pushed back and replaced with > > syslog-ng integration? > > > > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<scalr-discuss%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/scalr-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.
