Hi everyone,
I'm trying to deploy openstack on two nodes. Both the machines have a single
interface connected to the same subnet. One will have all the components
installed(including nova-compute) and the other only nova-compute. I'm a
little confused with the networking and IP assignment policy o
Matt,
a did check the xenapi connection to dom0 as described here
http://wiki.openstack.org/XenServerDevelopment -> Test XenAPI
and it worked.
Anyway I'm able to directly deploy vms on the node that receives the VHD.
Said so, is there somthing alse I should check?
Thanks
Giuseppe
On Wednesday
Greetings everybody,
in one of our tests we occasionally hit ResourceClosedError when executing the
volume_allocate_iscsi_target:
2011-09-20 04:25:20,515 DEBUG nova.volume.driver [-]
volume_allocate_iscsi_target failed for volume volume-114c from (pid=23701)
create_export /mnt/share/s-c
Hi,
I am trying to test the S3 layer of swift, i have tested with Cyberduck,
other tools available for S3 don't have option to work with servers other
than amazon server, they need account with aws.
Please let me know if any such tool available for S3.
Regards,
Gaurav
_
All good, Jesse.
I think it would be appropriate to either create a new smoketest that
stresses the flow you outline below, or add a new integration test to
here:
https://github.com/sorenh/openstack-integration-tests
Otherwise, testing will by nature be a manual process
Cheers!
-jay
On Wed
Yep, it's already set up through Gerrit and the openstack GitHub
organization :) Sorry, was copy-paste fail on my part!
https://github.com/openstack/openstack-integration-tests
Cheers!
jay
On Wed, Sep 21, 2011 at 3:15 PM, Joseph Heck wrote:
> Can we clone this into the Openstack repo so that i
Can we clone this into the Openstack repo so that it's clear:
a) there is a central set of openstack integration and functional tests
b) that it is THE place to add in common, cross-cutting tests
I don't really care which setup we use as the OpenStack project - Soren's is
fine, just needs to be
On Wed, Sep 21, 2011 at 3:44 PM, Joshua Harlow wrote:
> Hi all,
>
> I was wondering how these different types of formats supported by glance @
> http://glance.openstack.org/formats.html will be workable with nova-compute.
Just an FYI, Glance does not (currently) do any inspection to ensure
that w
Hi all,
I was wondering how these different types of formats supported by glance @
http://glance.openstack.org/formats.html will be workable with nova-compute.
It seems like most examples I see are using precreated ami/ari/aki images. I
haven't seen a lot of examples using say an iso, or a ovf
I believe this review satisfies the remaining requirements that keystone was
lacking:
https://review.openstack.org/#change,516
See the new functional test in keystone/test/functional/test_auth.py:
test_user_auth_with_role_on_tenant(), which illustrates the flow you outlined.
At the moment, the
It would be really cool if there were openstack examples for each
container/image format.
I don't currently understand how the container format connects into the actual
image (and the result with nova-compute).
Since it seems like say when u upload an iso, ovf doesn't make sense (so would
that
A quick security question.
Is there any plan to force authentication/authorization of the rabbitmq
messages?
Right now it seems like keystone (tbd) will protect the external<->openstack
layers but what about the openstack<->openstack layers.
If someone got access to the rabbitmq it seems like
The keystone examples are focused on the end user who launch and control
VMs, and the supporting
infrastructure for Tentant management.
My question is whether Keystone is also supposed to be extensible to
manage the identities used by
applications running on those VMs to access Swift Objects (
13 matches
Mail list logo
