On 18.11.2013 21:32, Chiradeep Vittal wrote:
Realhostip.com is not required. See:
http://support.citrix.com/article/CTX133468
But I agree that realhostip should not be made the default (default
should
be http).
Can this be tweaked from Global Settings?
Lucian
--
Sent from the Delta quadra
Realhostip.com is not required. See:
http://support.citrix.com/article/CTX133468
But I agree that realhostip should not be made the default (default should
be http).
On 11/16/13 2:30 AM, "Nux!" wrote:
>On 12.11.2013 23:41, Steve Wilson wrote:
>> Hi All,
>>
>> As we ramp towards freeze on 4.3
+ 1 to process improvements and ecosystems (advertising CloudStack, reaching
out to the student community, which I always stand for)
-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com]
Sent: Friday, November 15, 2013 7:38 PM
To: dev@cloudstack.apache.org
Subject: Re
Lots of interesting ideas there. Thanks for sharing! BTW, I really share your
interest in making CloudStack and Docker work really well together.
On Nov 17, 2013, at 9:57 AM, Rohit Yadav wrote:
> Hi,
>
> On Wed, Nov 13, 2013 at 5:11 AM, Steve Wilson wrote:
>
>> Hi All,
>>
>> As we ramp tow
Hi,
On Wed, Nov 13, 2013 at 5:11 AM, Steve Wilson 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?
On 12.11.2013 23:41, Steve Wilson 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
+1 especially to CI process improvement.
IMO, we need to improve the patch review process.
Sometimes we encounter that the master branch is broken. Low quality
commit slows down our developing and testing on the master branch.
I think we should change the patch review process to check that a
patch
Hi, this is a bit of a brain dump:
I tend to see different types of buckets:
1-Processes
Involves getting better as a community in terms of release, bug fixing,
committing code, documentation and user support. Some of these have already
been discussed partially but we need to come to consensus
+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
Hi Mike,
Really interesting stuff and very differentiaing!
-Steve
On 11/13/13 12:33 PM, "Mike Tutkowski"
wrote:
>Just as an FYI (to whom it may concern):
>
>For me, personally, my primary focus has been (and continues to be) on
>bringing true storage Quality of Service (QoS) to CloudStack (gua
Just as an FYI (to whom it may concern):
For me, personally, my primary focus has been (and continues to be) on
bringing true storage Quality of Service (QoS) to CloudStack (guaranteed
IOPS on a per-CloudStack-volume basis).
Prior to 4.2, CloudStack expected an admin to preallocate large amounts
Hi Daan, Prasanna, Simon, David and Andrei!
Thanks for chiming in. Great way to kick off the discussion.
In my thinking, we might want to look at things in three buckets:
1. Things that could go into a maintenance release like a 4.2.x
2. Things that could go into a minor release like a 4.4
3. T
I don't see any sugestions I don't like (including not breaking api) but,
- I like to second Simnons 'HA for VPC routers'
extra. It is hurting not having that.
- smaller releases is another one. monthly preferably or maybe an db
upgrade model that allows for running snapshots and upgrading them
r
On Tue, Nov 12, 2013 at 11:41:17PM +, Steve Wilson 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 CloudSta
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
On Tue, Nov 12, 2013 at 6:41 PM, Steve Wilson 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? Cal
Steve,
I would like to see better error messages in the gui. Some errors that I get
are absolutely meaningless and don't tell anything about what needs doing to
overcome the errors. This is very important in my opinion. Errors like Could
not start vm or router due to Null is just no go. I've a
17 matches
Mail list logo
