Hey Kelven,
MidoNet is not in 4.1 so not surpising you couldn't find it ;-) My mistake..
I've added the other components to both the standard and the non-oss build in
the 4.1 branch. So everything should be ready to go now. See commit
a0ffb47157c7a14429fddf926a331dc0dacc8c85.
Cheers,
Hugo
>
On Sat, Apr 06, 2013 at 05:27:11AM +, Prasanna Santhanam wrote:
> Ah - misunderstood. Like Hugo said, a test that fails on presence of db
> connection should solve this. But I hope ppl will turn mysql on (as an
> additional step) to run the bvt. Or better yet, I can look into those db
> test
> On April 5, 2013, 5:46 p.m., Rohit Yadav wrote:
> > As long as we have query based API, the overall base64 encoded payload in
> > the url cannot exceed this limit as per a RFC (I recall discussing this
> > issue on ML when I applied this feature from previous ports).
> > If we handle POST req
Hi,
Can anyone provide some insight into what this exception might indicate?
Context: I have a little program that creates an iSCSI-based storage
repository in a XenServer resource pool, then creates primary storage for
it in CloudStack, then creates a compute offering that uses this primary
sto
Hi,
I'm currently using 4.1 (from like a week or so ago).
I have three tiers of shared, iSCSI-based storage represented in three
storage repositories in XenServer:
SR_2
SR_3
SR_4
SR_2 maps into CS via primary storage PS_2, which has the storage tag PS_2
SR_3 maps into CS via primary storage PS_
Looks like the only host with shared storage that could be used for system
VMs was offline.
I brought it up and all is well now. :)
On Sat, Apr 6, 2013 at 11:57 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Hi,
>
> Can anyone provide some insight into what this exception might in
If someone would like me to demo this problem, please let me know.
I noticed it while writing code that makes use of the 4.1 API.
I assumed at first I had done something wrong, so I tried it manually using
the wizard in the GUI and noticed the same behavior: CloudStack was not
always honoring my
Have you by chance looked at the debug logs to see if it by chance tried
the proper storage and failed? I'm not sure that's OK either, but it would
be interesting to know.
On Apr 7, 2013 12:25 AM, "Mike Tutkowski"
wrote:
> Hi,
>
> I'm currently using 4.1 (from like a week or so ago).
>
> I have t
Hi Marcus,
I was just looking at the output in the console.
Can you remind me again where the related logs are stored?
Thanks!
On Sun, Apr 7, 2013 at 12:39 AM, Marcus Sorensen wrote:
> Have you by chance looked at the debug logs to see if it by chance tried
> the proper storage and failed? I'
However, even if CS failed to deploy the VM to the required tier, deploying
it to another tier would be erroneous behavior.
For example, one tier might be higher performing than another. If the
customer paid for a high-performance tier and was placed on something
lower, that wouldn't be acceptabl
If you're running it the Dev way with jetty, look for vmops.log in your git
root. If you've installed via package look for
/var/log/cloudstack/management/management-server.log.
On Apr 7, 2013 12:45 AM, "Mike Tutkowski"
wrote:
> Hi Marcus,
>
> I was just looking at the output in the console.
>
> C
11 matches
Mail list logo
