hi all:
I have set up quantum+floodlight, there are a compute node and a
controller, so I create a VM in the compute node, but the VM(100.0.0.4) can
not ping its gateway(100.0.0.1) in the controller node.
When the VM send a ARP request to OVS of the compute node, a packet_in
request is sent to
OVS is not compatible with iptables + ebtables rules that are applied
directly on VIF ports.
So the libvirt_vif_driver 'nova.virt.libvirt.vif.LibvirtHybirdOVSBridgeDriver'
create a Linux software bridge to be able to apply security group rules
with iptables.
If you don't need the security group
Hi Folks,
Has anybody on the list installed Grizzly on CentOS 6.3 as a virtual machine
running on Xen Server 6.0.2 ? If yes, please provide any pointers for the
same.
Thank you,
--
Ashutosh Narayan
http://ashutoshn.wordpress.com/
___
Mailing list:
one possible reason can be that your VM didn't get IP address from its DHCP
server. Can you check your VM instance log (You can check it from
dashboard) and see whether its sending the DHCP request for IP and getting
any response from it
On Tue, May 7, 2013 at 12:24 PM, zengshan2008
I run ovs-vsctl show on the three node, and here is the result:
root@networknode:/var/log/quantum# ovs-vsctl show
690ad327-14ad-410e-b310-2d23e4c78223
Bridge br-int
Port br-int
Interface br-int
type: internal
Port int-br-em3
Interface
I am using three nodes to do the installation, and I am using the openvswitch
plugin with the vlan mode, do I need to do some configration in the physical
switch?
2013-05-07
zengshan2008
发件人：Anil Vishnoi
发送时间：2013-05-07 16:16
主题：Re: [Openstack] Unable to ping VM using OpenStack and
hi
I use quantum grizzly with namespace and floodlight, but VMs can not ping
its gateway. It seems that floodlight ignore devices whose status
is PORT_DOWN or LINK_DOWN, somehow the subnetwork gateway is
really PORT_DOWN and LINK_DOWN.. is it normal?or how can I change its
status to normal?
It seems OK after I set controller for both br-tun and br-int. but
floodlight official installation only set br-int's controller, am I correct?
On Tue, May 7, 2013 at 2:33 PM, Liu Wenmao marvel...@gmail.com wrote:
hi all:
I have set up quantum+floodlight, there are a compute node and a
any idea? I just restarted my nodes, and it's the same again. I know
how to make new static route without namespaces at startup, but if we
look at openstack as a dynamic system, its not ok to make static
routes manually for every tenant's every network.
thanks
Rusty
On Fri, May 3, 2013 at 2:09
What version of keepalived are you using? I found this online:
https://github.com/acassen/keepalived/issues/8
I would first try removing the check script and validating that failure works
without the check script. If that works you might need to update keepalived.
Here’s a brief introduction
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
So this says that you didn't get DHCP response for your DHCP request
and hence your VM didn't get any ip address assigned.
I think as a next step of debugging, you need to check whether your
Hi,
I am new to OpenStack. I wish to understand how actually
OpenStack achieves virtualization. I am looking for any info/doc/URL.
Request your help regarding.
Thanking you,
Jaya Kumar Satri
On Tue, May 7, 2013 at 12:37 PM, Jayakumar Satri
js00123...@techmahindra.com wrote:
I am new to OpenStack. I wish to understand how actually OpenStack
achieves virtualization. I am
looking for any info/doc/URL. Request your help regarding.
What exactly do you want to know?
Openstack
Jay,
Kindly check http://openstack.org for overall information about the OpenStack
project.
You can also check https://docs.openstack.org which hosts the project
documentation.
Hope it helps.
From: Openstack
Thank you for the through explanation. I have no problem running the
Collector, Central and Compute Agents. So, I believe only the API Server is
trying to use the old oslo-incubator version.
I am still weighing the options.
Just a quick question; since the only thing that does not work in my
Hello Guys,
I'm here again with some doubt, have anybody already installed the Ryu
plugin with Quantum? I'm trying to follow this page:
http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
working. Can anybody help me with some doubts about the installation?
Thank you so much.
On May 7, 2013, at 7:57 AM, Guilherme Russi luisguilherme...@gmail.com wrote:
Hello Guys,
I'm here again with some doubt, have anybody already installed the Ryu
plugin with Quantum? I'm trying to follow this page:
http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
Hello Kyle, The doubts are, If I install the ryu plugin, my current working
openstack will broken, I mean, only installing ryu by the step python
./setup.py install, another thing, and the part to configure nova.conf, I
don't have nova-network, I must install it?
Thanks.
Guilherme.
2013/5/7
Hi,
I've got the cinder-api service up and running but when I run cinder
list I get an error ERROR: Malformed request url.
This is the URL called from the debug output:
REQ: curl -i
http://10.16.171.3:8776/v1/11b39f6529ea4eb6a527de82122ba6f6/volumes/detail
-X GET
The endpoints in the
You don't want to run nova-network with OpenStack Networking (Quantum) at the
same time. If you're running Folsom, I think upstream Ryu has changed such that
the Folsom version of the Quantum plugin may not work. Running Grizzly will
solve this, or alternatively if you want to try Folsom, look
Hello again Kyle, thank you for answering, how do I update the Openstack
version, from Folsom to Grizzly?
Regards.
Guilherme.
2013/5/7 Kyle Mestery (kmestery) kmest...@cisco.com
You don't want to run nova-network with OpenStack Networking (Quantum) at
the same time. If you're running
On 05/07/2013 05:53 AM, Ashutosh Narayan wrote:
Hi Folks,
I have installed Grizzly on CentOS 6.4 and facing some issues while
installing OpenvSwitch in order to make Quantum service work properly.
Can anybody point me to some link which has useful information for the same ?
I was following
Hi,
I am getting 500 server Error when I create the user. The command i used:
swauth-add-user -K swauthkey -a test testerrr testin
swauth version = 1.0.2+git2028-0ubuntu1
swift from grizzly runing on 12.04 lts.
However I can see from swauth-list
swauth-list -A
Hi,
Am 07.05.13 17:32, schrieb Paras pradhan:
I am getting 500 server Error when I create the user. The command i used:
swauth-add-user -K swauthkey -a test testerrr testin
swauth version = 1.0.2+git2028-0ubuntu1
that version of swauth is quite old, current version is 1.0.8,
Yes but where do I find it. I can only see 1.0.9-dev at github.
Paras.
On Tue, May 7, 2013 at 10:55 AM, Christian Schwede i...@cschwede.de wrote:
Hi,
Am 07.05.13 17:32, schrieb Paras pradhan:
I am getting 500 server Error when I create the user. The command i
used:
swauth-add-user
Hi all!
I want to setup juju for my openstack installation, but it requires
objectstore. Intsalling swift is just seems overhead for this environment.
Does grizzly support nova-objectstore? How should I configure it? I
couldn't find any documentation about it. As I can see after installation
the
Oh, the 1.0.8 commit is not yet tagged.
You can download the release version using the commit hash:
https://github.com/gholt/swauth/archive/4fc009d5ad9d3309ed023d433c01ade21e0e16af.zip
Christian
Am 07.05.13 18:12, schrieb Paras pradhan:
Yes but where do I find it. I can only see 1.0.9-dev at
It worked ! Thanks a lot.
Paras.
On Tue, May 7, 2013 at 11:42 AM, Christian Schwede i...@cschwede.de wrote:
Oh, the 1.0.8 commit is not yet tagged.
You can download the release version using the commit hash:
If you are using devstack, it's as simple as adding a stable/grizzly for each
component you are running, similar to this:
NOVA_BRANCH=stable/grizzly
Repeat that for the services you are running, (e.g. Quantum, Glance, etc.).
Thanks,
Kyle
On May 7, 2013, at 10:20 AM, Guilherme Russi
I'm not using devstack, I have installed each component and put a
repository in my ubuntu, I need to purge all of them or just change the
repository and run an apt-get update / apt-get upgrade?
Regards.
Guilherme.
2013/5/7 Kyle Mestery (kmestery) kmest...@cisco.com
If you are using devstack,
I would have to defer to the normal Ubuntu OpenStack install/upgrade procedures
here, I'm not an expert in that area.
On May 7, 2013, at 12:01 PM, Guilherme Russi luisguilherme...@gmail.com wrote:
I'm not using devstack, I have installed each component and put a repository
in my ubuntu, I
Well, thank you for your support, I'll try to do this and I'll let you know
if it worked, or not.
Regards.
2013/5/7 Kyle Mestery (kmestery) kmest...@cisco.com
I would have to defer to the normal Ubuntu OpenStack install/upgrade
procedures here, I'm not an expert in that area.
On May 7,
As the subject says, I'm having issues getting at Instances Volumes (also
Images Snapshots) in Horizon. I'm running grizzly on precise. Everything
else works fine; the entire Admin tab works as expected. The Overview and
Access Security also work fine.
Is there any way to see what calls are
Édouard:
I didn't realize that there's a Linux software bridge inolved when security
groups are enabled.
However, this doesn't really answer my original question. I asked about the
fact that there seemed to be two openvswitch bridges that packets have to
cross to get from the virtual interface
+1Well the best option would be a raid 1 that would ensure data safety in case one drive fails actually.There is not I think any "optimal" strategy - but since that service (Cinder/ nova-volume) aims to provide customers a safe place to put their datas into - then your best best would be a raid 1
Excellent :)
Le 30 avr. 2013 à 16:29, rahul singh singh.rahul.1...@gmail.com a écrit :
Thanks Razique, that works :)
On Tue, Apr 30, 2013 at 10:22 AM, Razique Mahroua razique.mahr...@gmail.com
wrote:
if it's an ephemeral one, just run $ fdisk -l and you will see it :)
it's neither
Hi Folks,
The current implementation of Keystone's domain support when using LDAP as
a backend is broken in the read-only case for Grizzly. This is because
Keystone in Grizzly assumes it can create a default domain which is not
possible for many read-only LDAPs. We are trying to backport a
Problem:
VMs launch, get local IPs from DHCP, get floating ips, and are
available from the external network, but seem to time out after a
minute of inactivity. After that time, the VM cannot be reached. I
can sometimes network access back by pinging the external gateway from
the VM console, but
Hi Brad,
FWIW-- I'm using AD as the LDAP backend and was using the msSFU30NisDomain
attribute for the domain_id mapping. I'm now leveraging some OpenLDAP
overlay magic instead, but I digress. I could see value for us in being
able to leverage a domain_id stored in LDAP although admittedly we
On 07.05.2013 16:05, Dennis Jacobfeuerborn wrote:
Hi,
I've got the cinder-api service up and running but when I run cinder
list I get an error ERROR: Malformed request url.
This is the URL called from the debug output:
REQ: curl -i
Is your physical nic whiched used for vm communication can ping each other?
Check your GRE tunnel if you are in GRE mode or check your vlan
setting in physical switch if in vlan mode
Daniels Cai
http://dnscai.com
在 2013-5-7，14:56，zengshan2008 zengshan2...@gmail.com 写道：
Hi,
I've installed
2013-05-08 02:13:17 WARNING [cinder.scheduler.host_manager] service is
down or disabled.
2013-05-08 02:13:17ERROR [cinder.scheduler.manager] Failed to
schedule_create_volume: No valid host was found.
I'm running the api and scheduler services on the controller node and
the volume
Hi all
In OpenStack 'how-to-contribute' document, the first step is join the team
in Launchpad. All of ~swift, ~nova, ~glance are ok. But ~devstack is a
restricted team here[1].
Does that 'joining the team' is a necessary step for contributing?
[1] https://launchpad.net/~devstack
On 08.05.2013 02:34, Steve Heistand wrote:
2013-05-08 02:13:17 WARNING [cinder.scheduler.host_manager] service is
down or disabled.
2013-05-08 02:13:17ERROR [cinder.scheduler.manager] Failed to
schedule_create_volume: No valid host was found.
I'm running the api and scheduler services on
On Tue, May 7, 2013 at 9:16 PM, Gareth academicgar...@gmail.com wrote:
In OpenStack 'how-to-contribute' document, the first step is join the team in
Launchpad. All of ~swift, ~nova, ~glance are ok. But ~devstack is a
restricted team here[1].
Does that 'joining the team' is a necessary step
I just comment some of floodlight codes and VMs can ping the gateway.
But I do not know why the gateway port and link is down, it is up in
namespace view:
root@controller
:/usr/src/eclipse# ip netns exec
qrouter-7bde1209-e8ed-4ae6-a627-efaa148c743c ip link
14: qr-8af2e01f-bb:
Great thanks!
On Wed, May 8, 2013 at 10:33 AM, Dean Troyer dtro...@gmail.com wrote:
On Tue, May 7, 2013 at 9:16 PM, Gareth academicgar...@gmail.com wrote:
In OpenStack 'how-to-contribute' document, the first step is join the
team in Launchpad. All of ~swift, ~nova, ~glance are ok. But
I am using the default version of the ubuntu 12.04 ( keepalived
1:1.2.2-3ubuntu1).
Maybe this issue is the root cause. I will try the latest keepalived.
On Tue, May 7, 2013 at 6:11 PM, eric_e_sm...@dell.com wrote:
What version of keepalived are you using? I found this online:
Title: precise_havana_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_glance_trunk/41/Project:precise_havana_glance_trunkDate of build:Tue, 07 May 2013 03:01:36 -0400Build duration:5 min 23 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_ceilometer_trunk/37/Project:precise_havana_ceilometer_trunkDate of build:Tue, 07 May 2013 09:31:37 -0400Build duration:1 min 3 secBuild cause:Started by an SCM
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/94/Project:precise_havana_quantum_trunkDate of build:Tue, 07 May 2013 09:31:36 -0400Build duration:2 min 41 secBuild cause:Started by an SCM changeBuilt
at 20130507
Title: precise_havana_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_ceilometer_trunk/38/Project:precise_havana_ceilometer_trunkDate of build:Tue, 07 May 2013 10:01:33 -0400Build duration:1 min 15 secBuild cause:Started by an SCM
Title: saucy_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/25/Project:saucy_havana_quantum_trunkDate of build:Tue, 07 May 2013 11:31:38 -0400Build duration:19 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/38/Project:saucy_havana_nova_trunkDate of build:Tue, 07 May 2013 11:31:58 -0400Build duration:1 min 8 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/95/Project:precise_havana_quantum_trunkDate of build:Tue, 07 May 2013 11:31:37 -0400Build duration:2 min 36 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/42/Project:precise_havana_cinder_trunkDate of build:Tue, 07 May 2013 12:31:36 -0400Build duration:1 min 16 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_cinder_trunk/10/Project:saucy_havana_cinder_trunkDate of build:Tue, 07 May 2013 12:31:37 -0400Build duration:1 min 44 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_horizon_trunk/30/Project:precise_havana_horizon_trunkDate of build:Tue, 07 May 2013 16:31:37 -0400Build duration:2 min 41 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_ceilometer_trunk/25/Project:saucy_havana_ceilometer_trunkDate of build:Tue, 07 May 2013 20:01:37 -0400Build duration:18 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_ceilometer_trunk/39/Project:precise_havana_ceilometer_trunkDate of build:Tue, 07 May 2013 20:01:36 -0400Build duration:1 min 14 secBuild cause:Started by an SCM
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/122/Project:precise_havana_nova_trunkDate of build:Tue, 07 May 2013 23:01:39 -0400Build duration:2 min 32 secBuild cause:Started by an SCM changeBuilt
See http://10.189.74.7:8080/job/cloud-archive_grizzly_version-drift/18/
--
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe :
63 matches
Mail list logo
