+1 to IAM. An Autoscale service independent of Netscaler. I'd like to see the built-in GRE controller fully fleshed out as a distributed/cross-AZ virtual network provider. Make it the out-of-the-box virtual network provider instead of VLAN. Easier service vm insertion into virtual networks. Better fidelity with AWS VPC APIs
On 11/12/13 6:09 PM, "Simon Murphy" <simon.mur...@vifx.co.nz> wrote: >As a CloudStack user, here are the ares that I feel need attention: > >- improved IAM and implementation of a full RBAC security model. This is >hurting us right now. >- improved VM import functionality (ie bulk import of VM's and import of >running VM's from existing vSphere clusters) >- improved backup functionality and integration with 3rd party tools >- HA for VPC routers > >Cheers, >Simon Murphy >Solutions Architect > >ViFX | Cloud Infrastructure >Level 7, 57 Fort Street, Auckland, New Zealand 1010 >PO Box 106700, Auckland, New Zealand 1143 >M +64 21 285 4519 | S simon_a_murphy >www.vifx.co.nz <http://www.vifx.co.nz/> follow us on twitter ><https://twitter.com/ViFX> >Auckland | Wellington | Christchurch > > > >experience. expertise. execution. > >This email and any files transmitted with it are confidential, without >prejudice and may contain information that is subject to legal privilege. >It is intended solely for the use of the individual/s to whom it is >addressed in accordance with the provisions of the Privacy Act (1993). The >content contained in this email does not, necessarily, reflect the >official policy position of ViFX nor does ViFX have any responsibility for >any alterations to the contents of this email that may occur following >transmission. If you are not the addressee it may be unlawful for you to >read, copy, distribute, disclose or otherwise use the information >contained within this email. If you are not the intended recipient, please >notify the sender prior to deleting this email message from your system. >Please note ViFX reserves the right to monitor, from time to time, the >communications sent to and from its email network. > > > > > > >On 13/11/13 1:18 PM, "David Nalley" <da...@gnsa.us> wrote: > >>On Tue, Nov 12, 2013 at 6:41 PM, Steve Wilson <steve.wil...@citrix.com> >>wrote: >>> Hi All, >>> >>> As we ramp towards freeze on 4.3 and start talking about 4.4, I thought >>>it would be fun to queue up a discussion here on the list before Collab >>>next week. >>> >>> What do you envision in the next MAJOR release of CloudStack? Call it >>>5.0 or whatever you like, but what would you like to see there? What >>>would you change? What would you enhance? Are there big bets we should >>>be placing as a community? >>> >>> Feel free to post any thoughts here and I'll look forward to talking to >>>many of you in person at Collab next week. You are coming to Collab, >>>right? >>> >> >> >>Hi Steve, >> >>I'll be contrarian ;) - I don't see 5.0 (e.g. API breaking changes) >>coming in at least the next 12-18 months. Breaking API compatibility >>is a BIG DEAL IMO and should be done very deliberately and with a lot >>of consideration, and a plan around how we help folks adapt. >> >>Think about the tons of integrations that we have now: Chef, Puppet, >>Salt, libcloud, fog, jclouds, dasein, etc etc. Breaking that directly >>disrupts our users who stand a good chance of using one of those >>integrations or consume CloudStack via one of those tools. >> >>--David >
