Hi,
I discussed this during CCCEU13 with David, Chip and Hugo and I promised
I put it on the ml.
My idea is to come up with a reporting tool which users can run daily
which feeds us back information about how they are using CloudStack:
* Hypervisors
* Zone sizes
* Cluster sizes
* Primary
Hi,
I discussed this during CCCEU13 with David, Chip and Hugo and I promised
I put it on the ml.
My idea is to come up with a reporting tool which users can run daily
which feeds us back information about how they are using CloudStack:
* Hypervisors
* Zone sizes
* Cluster sizes
* Primary
Jooq does a good job of handling the differences in dialects so as long as you
don't use a feature specific to a database your are fine. More info at
http://www.jooq.org/doc/3.2/manual/sql-building/dsl-context/sql-dialects/
I've used jooq across databases and it's been fine. The sql we use in
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14876/
---
(Updated Nov. 23, 2013, 4:13 p.m.)
Review request for cloudstack, Girish
Hi,
Sorry for cross-posting.
While validating the Release Notes by using publican, there is a validity
issue which I am not able to resolve.
The command used is:
Publican build -format=test -langs=en-us -config=publican.cfg.
The error I am getting is the following:
Hi Prachi, that is exactly what I looking for.
Thank you.
On 2013-11-23, at 4:13, Prachi Damle prachi.da...@citrix.com wrote:
Hi Yitao,
CloudStack scheduling policies are implemented by the DeploymentPlanner and
HostAllocator/StoragePoolAllocator components.
If you want to take a look
Going to an ORM is not as simple as you would expect. First, one can make a
strong argument that ORM is not the right solution, but that can be ignored
right now.
You have to look at the context of ACS and figure out what technology is the
most practical to adopt. ACS does not have ORM
Wouldn't it be a lot of work to move to JOOQ? All queries will have to be
rewritten.
On Sat, Nov 23, 2013 at 11:32 AM, Darren Shepherd
darren.s.sheph...@gmail.com wrote:
Going to an ORM is not as simple as you would expect. First, one can make
a strong argument that ORM is not the right
