No I'm running just one iscsi target service:
root@leonard:~# netstat -antp | grep 3260
tcp0 0 0.0.0.0:3260 0.0.0.0:* LISTEN
8927/tgtd
tcp6 0 0 :::3260 :::*LISTEN 8927/tgtd
Here is my cinder.conf:
root@leonard:~# cat /etc/c
I set that key in both controller and compute
still no luck
Le 26/04/2013 18:26, Darragh O'Reilly a écrit :
its not really obvious, but I believe the iscsi_ip_address needs to be set in
the nova.conf on the **controller** - just want to check you did it there.
__
Anybody has an idea about why the nova metadata server rejects the VM
requests?
Le 26/04/2013 15:58, Michaël Van de Borne a écrit :
Hi there,
I've installed Grizzly on 3 servers:
compute (howard)
controller (leonard)
network (rajesh)).
Namespaces are ON
Overlapping IPs are ON
When booting,
Thanks David, Clay and Vaidy for your suggestions.
I'm curious about what version of that Hadoop-Swift-integration project
> you're trying to run. You shouldn't have been able to create containers
> with it in any of the more recent versions.
>
Yes, my bad. Container creation isn't supported. As
is nova configured to use cinder?
in nova.conf
volume_api_class=nova.volume.cinder.API
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://he
yes it was already.
Le 27/04/2013 14:08, Darragh O'Reilly a écrit :
is nova configured to use cinder?
in nova.conf
volume_api_class=nova.volume.cinder.API
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad
On 2013-04-26, at 7:53 PM, David Wittman wrote:
> This is the expected behavior. With nova-network, FLIPs are assigned as a
> secondary address on the host interface, and traffic is routed to your
> instances via NAT rules. I'd recommend reading the following blog post from
> Mirantis for more
it seems the ips for the targets are set at the time they were created
$ mysqlmysql> use cinder;
mysql> select provider_location from volumes;
Try creating a new volume - does it get the new iscsi_ip_address ?
___
Mailing list: https://launchpad.ne
Man, this is awesome!
that did it!
thank you very much.
Le 27/04/2013 17:13, Darragh O'Reilly a écrit :
it seems the ips for the targets are set at the time they were created
$ mysqlmysql> use cinder;
mysql> select provider_location from volumes;
Try creating a new volume - does it get the
Greetings, and a lovely Saturday to all of you openstackers.
I've had a fairly successful day of getting openstack working on Ubuntu 13.04
but I'm running into a problem fairly late in the game.
No matter what I do I appear to be unable to get the virtual machines to
connect to the external Int
Is there a way to have SNAT (where multiple private IPs could go out using a
single public IP) or is Floating IPs (1:1 NAT aka static NAT) the only choice
in Openstack/Quantum?
Hari
___
Mailing list: https://launchpad.net/~openstack
Post to : opens
Hi,
If the gateway for the external net is a firewall or something that does NAT,
then what would stop you from doing that?
From: Openstack
[mailto:openstack-bounces+drew.weaver=thenap@lists.launchpad.net] On Behalf
Of Kannan, Hari
Sent: Saturday, April 27, 2013 7:59 PM
To: openstack@lis
On 2013?04?28? 07:59, Kannan, Hari wrote:
>
> Is there a way to have SNAT (where multiple private IPs could go out
> using a single public IP) or is Floating IPs (1:1 NAT aka static NAT)
> the only choice in Openstack/Quantum?
>
> Hari
>
>
>
> ___
> Maili
On 04/27/2013 12:44 PM, Michaël Van de Borne wrote:
Anybody has an idea about why the nova metadata server rejects the VM
requests?
Hi,
Just a few questions:-
1. Can you please check /etc/quantum/metadata_agent.ini to see that you
have the correct quantum keystone credential configured?
2. Ca
14 matches
Mail list logo
