This is slower now because of the quantum metadata agent. In Essex when a
vm did a request for 169.254.169.254 the request would go straight to the
nova-metadata server and nova would determine which metadata to return
based on the instances source ip. With quantum you are allowed to have
nova --os-tenant-name name command
Aaron
On Thu, Jul 25, 2013 at 9:06 PM, Remo Mattei r...@mattei.org wrote:
Nell'ospedale what is the best way to list all instance of a tenant
without having to ask for their password if I am the admin so I can check
if there is ny problems with an
Haitao
On Tue, Jul 9, 2013 at 10:29 PM, Aaron Rosen aro...@nicira.com wrote:
You should be able to compile openvswitch from source here :
http://openvswitch.org/download/ and then you'll get tunnel support.
Aaron
On Tue, Jul 9, 2013 at 10:21 PM, Haitao Jiang jianghai...@gmail.com
I'd check the quantum openvswitch agent log files. I'd guess the reason
this isn't working is because your kernel isn't using the openvswitch
kernel module that has tunnel support.
Aaron
On Tue, Jul 9, 2013 at 9:19 AM, Haitao Jiang jianghai...@gmail.com wrote:
I just set up a multi-node
to set flags for network
device patch-int: Operation not supported
On Tue, Jul 9, 2013 at 8:59 PM, Aaron Rosen aro...@nicira.com wrote:
I'd check the quantum openvswitch agent log files. I'd guess the reason
this
isn't working is because your kernel isn't using the openvswitch kernel
module
-prefix 0.0.0.0/0
default
or
nova secgroup-add-rule default tcp 1 65355 0.0.0.0/0
Thanks and Regards
Rahul Sharma
On Thu, Jun 27, 2013 at 10:25 PM, Aaron Rosen aro...@nicira.com wrote:
Hi Rahul,
The issue is that you are running as an admin user so it shows all the
security groups
Hi Rahul,
The issue is that you are running as an admin user so it shows all the
security groups for every tenant. If you want to list the security groups
for just one particular tenant you can do this:
quantum security-group-list -- --tenant-id=tenant_id
Aaron
On Thu, Jun 27, 2013 at
Hi Rami,
On Tue, Jun 18, 2013 at 11:36 PM, Rami Vaknin rvak...@redhat.com wrote:
Hi,
I read the security groups documentation from the admin guide, I have few
things that I'm not sure I fully understand, any clarification would be
appreciated:
i.
didn't follow the rules of
iptables created by nova.
There are no traffic in FORWARD chain rule and nova-compute-local chain
rule as I posted before.
Thanks again!
Chandler
2013/6/18 Aaron Rosen aro...@nicira.com
Do you have:
firewall_driver=nova.virt.firewall.IptablesFirewallDriver
Do you have:
firewall_driver=nova.virt.firewall.IptablesFirewallDriver
in your nova.conf? In folsom, quantum leveraged nova security groups
implementation directly so you need that. (looks like you have that set
though by your output).
Aaron
On Sun, Jun 16, 2013 at 7:38 PM, Chandler Li
If you run rejoin-stack.sh it should start all the openstack processes that
were running before reboot.
Aaron
On Mon, Jun 17, 2013 at 12:15 PM, Vivek Satpute vivekonlin...@gmail.comwrote:
Hi,
I recently setup a openstack on one node, which is hosting all the services
like keystone, nova,
this feature?
Daniels Cai
http://dnscai.com
2013/6/8 Aaron Rosen aro...@nicira.com
Hi Joe,
I thought setting firewall_driver =
quantum.agent.firewall.NoopFirewallDriver would do the trick? Also, the ovs
plugin does not do any mac spoof filtering at the OVS level. Those are all
done
Aaron Rosen aro...@nicira.com
There is no port_security_enabled config option. This is an attribute on
a port that is used if the plugin you are using implements the
port_security_extension (which is only nvp at the time).
I'm guessing your issue is the network you are trying to boot
|
+--+-+--+
Daniels Cai
http://dnscai.com
2013/6/8 Aaron Rosen aro...@nicira.com
You said:
it works, but when i try to attach a security group to an exist vm , api
throw an error :Network requires port_security_enabled and subnet
associated
in
nova-compute that are making this a pain for me.
On Jun 7, 2013, at 11:11 PM, Aaron Rosen wrote:
Hi Joe,
I thought setting firewall_driver =
quantum.agent.firewall.NoopFirewallDriver would do the trick? Also, the ovs
plugin does not do any mac spoof filtering at the OVS level
Hi Joe,
I thought setting firewall_driver =
quantum.agent.firewall.NoopFirewallDriver would do the trick? Also, the ovs
plugin does not do any mac spoof filtering at the OVS level. Those are all
done in iptables.
Aaron
On Fri, Jun 7, 2013 at 8:22 PM, Joe Breu joseph.b...@rackspace.com wrote:
Hi,
Those vlan tags you are showing are not the actual tags that will be seen
on the wire. Those tags are auto incremented and used for each new port
that lands on a server that is in a different network. If you run ovs-ofctl
dump-flows br-int you'll see those vlan tags are stripped off and the
Hi Li,
If you can ping out to the internet from your second vm but not back in
it's most likely related to security groups.
I'd try running: quantum security-group-rule-create --protocol icmp
--direction ingress default
and see if that allows ping from the internet to be received.
Aaron
On
from vm, but can’t ping their floating IP from Internet.
** **
Leon
** **
*From:* Aaron Rosen [mailto:aro...@nicira.com]
*Sent:* 2013年6月4日 9:03
*To:* Li, Leon
*Cc:* openstack-operat...@lists.openstack.org;
openstack@lists.launchpad.net (openstack@lists.launchpad.net)
*Subject:* Re
available in Grizzly
Release. If so, Can you please share that information.
Any other information on this will be appreciated.
Thanks,
Balaji.P
On Thu, May 30, 2013 at 11:37 AM, Aaron Rosen aro...@nicira.com wrote:
No but the provider network extention does provide a way to do this that
might
No but the provider network extention does provide a way to do this that
might work for your usecase:
http://docs.openstack.org/trunk/openstack-network/admin/content/provider_networks.html
On Wed, May 29, 2013 at 11:02 PM, Veera Reddy veerare...@gmail.com wrote:
Hi,
IS there any way to
Hi,
I still don't see why you want to have two nics on the same L2? We don't
allow this because we don't want to allow a tenants to bridge them
creating a loop in the network.
Aaron
On Thu, May 23, 2013 at 8:18 PM, Liu Wenmao marvel...@gmail.com wrote:
Hello:
I have a network with a
No, you would have to start several instances one on each compute node and
implement that distribution in your application.
On Thu, May 30, 2013 at 6:46 AM, Dhanasekaran Anbalagan
bugcy...@gmail.comwrote:
HI Salvatore,
It's possible start an instance which is distributed across several
Usually means that the instance trying to be launched can't be scheduled to
any nova-compute nodes. The log message should include a reason why though.
On Mon, May 20, 2013 at 12:06 PM, Remo Mattei r...@mattei.org wrote:
Hello everyone,
I wonder if someone can give me a more detail
Looks like something is already binding on 8774 (probably nova-api :) )
What does lsof -i :8774 say? Then see what process is running.
For example:
arosen@arosen-desktop:~$ lsof -i :8774
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python 13936 arosen6u IPv4 32808940
is causing 2 to use the same port.***
*
** **
**-**Philip
** **
*From:* Openstack [mailto:openstack-bounces+philip.schwartz=
lexisnexis@lists.launchpad.net] *On Behalf Of *Aaron Rosen
*Sent:* Wednesday, May 15, 2013 1:33 PM
*To:* Sam Su
*Cc:* openstack
*Subject:* Re: [Openstack
Is the network you are trying to boot on attached to a router (i.e and can
you ping the default gw)?
On Tue, May 7, 2013 at 11:59 PM, zengshan2008 zengshan2...@gmail.comwrote:
**
**
Hi all,
I've installed openstack using quantum by the guide
Sure, just use the ip addresses off of the one interface you have.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
Also, the security group stuff locks down the port to be the mac+ip of the
quantum port mac+ip. If you create a new bridge and add ethX to it you'll
also have to set the mac on your bridge to be the same as ethX (which is
the mac that quantum handed out).
Aaron
On Tue, Apr 30, 2013 at 4:25 PM,
From this error it looks you don't have brctl in any of the filters in
/etc/nova/*filters:
2013-04-29 19:17:33.640 7974 TRACE nova.virt.libvirt.vif [instance:
b5317dbd-bd85-4cf7-bbf0-cc653fa8c425] Stdout: '/usr/bin/nova-rootwrap:
Unauthorized command: brctl delif qbr8b7fa98b-60 qvb8b7fa98b-60
You should be able to delete the floating ip via an admin user and then
delete the subnet.
Aaron
On Thu, Apr 25, 2013 at 12:13 PM, Steve Heistand steve.heist...@nasa.govwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
so I had a tenant that was assigned a floating IP. I deleted the
Yup, If your host supports namespaces this can be done via the
quantum-metadata-agent. The following setting is also required in your
nova.conf: service_quantum_metadata_proxy=True
On Tue, Apr 23, 2013 at 10:44 PM, Balamurugan V G
balamuruga...@gmail.comwrote:
Hi,
In Grizzly, when using
192.168.2.3,
length 28
6 packets captured
6 packets received by filter
0 packets dropped by kernel
root@openstack-dev:~#
Any help will be greatly appreciated.
Thanks,
Balu
On Wed, Apr 24, 2013 at 11:48 AM, Aaron Rosen aro...@nicira.com wrote:
Yup, If your host supports namespaces
.
Thanks,
Balu
On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen aro...@nicira.com wrote:
The vm should not have a routing table entry for 169.254.0.0/16 if it
does i'm not sure how it got there unless it was added by something other
than dhcp. It seems like that is your problem as the vm
do not see this route in a WindowsXP VM booted in the
same network as the earlier Ubuntu VM and the Windows VM can reach the
metadata service with out me doing anything. The issue is with the Ubuntu
VM.
Thanks,
Balu
On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen aro...@nicira.com wrote
, Aaron Rosen aro...@nicira.comwrote:
The vm should not have a routing table entry for 169.254.0.0/16 if
it does i'm not sure how it got there unless it was added by something
other than dhcp. It seems like that is your problem as the vm is arping
directly for that address rather than
bytes:12476279 (12.4 MB) TX bytes:83025755 (83.0 MB)
root@openstack-dev:~#
Regards,
Balu
On Wed, Apr 24, 2013 at 11:32 PM, Aaron Rosen aro...@nicira.com wrote:
Can you show us a quantum subnet-show for the subnet your vm has an ip
on. Is it possible that you added a host_route to the subnet
Hi,
I tested this as well and was also able to reproduce the same issue. I
filed a bug here: https://bugs.launchpad.net/nova/+bug/1171636
Thanks,
Aaron
On Sun, Apr 21, 2013 at 11:00 PM, 陈雷 raid.c...@gmail.com wrote:
Hi, All
I'm testing hot-plug network interface, I can successfully
See: https://wiki.openstack.org/wiki/Quantum/LBaaS/HowToRun
On Tue, Apr 16, 2013 at 8:38 PM, HuYanrui h...@arraynetworks.com.cn wrote:
I just installed a new devstack with git clone git://
github.com/openstack-dev/devstack.git.
But did not see anything related with Loadbanlance in dashboard.
Hi,
The cirros image only starts the dhcp client on the eth0 interface. If you
have a vm with multiple interfaces you need to manually run udhcp -i
interface or change the network configuration file in order to start the
dhcp client for you .
Aaron
On Wed, Apr 17, 2013 at 11:44 AM, Anil
assigned.
On Thu, Apr 18, 2013 at 12:21 AM, Aaron Rosen aro...@nicira.com wrote:
Hi,
The cirros image only starts the dhcp client on the eth0 interface. If
you have a vm with multiple interfaces you need to manually run udhcp -i
interface or change the network configuration file in order
if you do quantum -v net-create --tenant-id 112a75ab04224fa3b44109a6c4859c28
net1 , you'll see the end host your client is trying to connect to. I'd
check that this is the right IP of your quantum box and that your client
has ip connectivity to that client.
Aaron
On Fri, Apr 12, 2013 at 4:13
Do you have NTP configured? If the nodes running nova-compute have clocks
that differ from each other the status shows XXX . (Not sure why it's done
this way though).
Aaron
On Thu, Apr 11, 2013 at 10:44 PM, Deepak A.P swift007.dee...@gmail.comwrote:
-- Forwarded message --
Hi David,
The quantum network node would route traffic between the non-DMZ-DMZ
network if both of those subnets are uplinked to the same quantum router. I
believe if you create another router for your dmz hosts then traffic in/out
of that network should route our to your physical infrastructure
In my reply I suggested you to create two quantum routers which I believe
should solve this for you.
quantum net-create DMZ-net --external=True
quantum subnet-create --name DMZ-Subnet1 DMZ-net dmz_cidr # Public ip
pool
quantum net-create non-DMZ --external=True
quantum subnet-create --name
Do you have the following line (bolded) in /etc/libvirt/qemu.conf ?
cgroup_device_acl = [
/dev/null, /dev/full, /dev/zero,
/dev/random, /dev/urandom,
/dev/ptmx, /dev/kvm, /dev/kqemu,
/dev/rtc, /dev/hpet*,/dev/net/tun,*
]
On Mon, Apr 1, 2013 at 8:42 PM, Liu Wenmao
I believe that with older versions of libvirt you need to uncomment the
following lines in /etc/libvirt/qemu.conf
# The user ID for QEMU processes run by the system instance.
user = root
# The group ID for QEMU processes run by the system instance.
group = root
I'd also check what's in
Hi,
I believe you have this setup on the wrong node. When the VM does a request
to 169.254.169.254 this will end up on the network node. On the network
node you need that iptables rule and nova-api-metadata installed and
running.
snip
My questions are:
- Am I missing something simple
I don't think that bug is preventing you from pinging your instances. That
bug just cleans up left over dnsmaq processes after a network has been
deleted while the quantum dhcp agent was down.
If you stop the quantum dhcp agent; sudo pkill dnsmaq ; start quantum-dhcp
agent that should do the
Actually it looks like you shouldn't need the iptables rule and
nova-api-metadata running if you use this method
http://docs.openstack.org/folsom/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html
On Fri, Mar 29, 2013 at 12:22 AM, Aaron Rosen aro...@nicira.com wrote:
Hi,
I
In that case you have two options:
1) use floating ips
2) create a provider network that bridges to the same physical of the hosts
that you want to be able to contact your vms.
Aaron
On Mon, Mar 18, 2013 at 10:02 AM, Chathura M. Sarathchandra Magurawalage
77.chath...@gmail.com wrote:
Thanks
I suspect that that host 10.5.5.6 has ssh configured for
PasswordAuthentication set to no and you don't have your public key of the
host you are on, in the authorized_key file of 10.5.5.6.
Aaron
On Fri, Mar 15, 2013 at 7:26 PM, Chathura M. Sarathchandra Magurawalage
77.chath...@gmail.com wrote:
Hi Sylvain,
This seems very odd to me. The reason this should happen is if your
client is sending packets with the DF (don't fragment) bit set in the
TCP header of the packets you are sending. I'd confirm that your
version of 'curl' is doing this (which it should definitely not do!).
What
Hi Rick,
You are right. I just ran curl to test for myself and it does set the
DF bit. Why is this? Any ideas why it specifies that the packet cannot
be fragmented?
Thanks,
Aaron
On Fri, Mar 8, 2013 at 11:27 AM, Rick Jones rick.jon...@hp.com wrote:
On 03/08/2013 09:55 AM, Aaron Rosen wrote
No, you'll need to switch over to quantum to use this. Quantum,
implements the same use case as nova-network FlatDHCP via the provider
extension.
Aaron
On Mon, Mar 4, 2013 at 10:09 PM, gtt116 gtt...@126.com wrote:
Hi all,
I want to play LBaas from quantum, but I was used nova-network FlatDHCP
Perhaps:
interface gigbbit 0/22
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
interface gigbbit 0/23
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
On Wed, Feb 27, 2013 at 12:02 AM, Ajiva Fan
Hi
response inline
On Wed, Feb 27, 2013 at 3:22 PM, The King in Yellow
yellowk...@gmail.com wrote:
I have been working on creating an OpenStack environment according to the
Basic Install doc. It was working fine last night! In order to make sure I
didn't mess anything up, I downed
TO DO THE FOLLOWING IN YOUR CONTROLLER NODE:
route add -net 10.10.10.0/24 gw $router_proj_one_IP
Sincerely,
Hsiao
On Thu, Feb 28, 2013 at 7:57 AM, Aaron Rosen aro...@nicira.com wrote:
Hi
response inline
On Wed, Feb 27, 2013 at 3:22 PM, The King in Yellow
yellowk...@gmail.com wrote:
I
, Aaron Rosen aro...@nicira.com wrote:
DO NOT SET GATEWAY as 192.168.0.254.
Why do you say that. I don't see any problem with what the doc says:
# Management Network
auto eth0
iface eth0 inet static
address 192.168.0.2
netmask 255.255.255.0
gateway 192.168.0.254
dns
On Tue, Feb 26, 2013 at 11:02 PM, Aaron Rosen aro...@nicira.com wrote:
inline
On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan aji.zq...@gmail.com wrote:
greeting, stackers
i deploy essex with flatdhcp, it works for a long time, but currently
i want to use vlan network, so i deploy a new
inline
On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan aji.zq...@gmail.com wrote:
greeting, stackers
i deploy essex with flatdhcp, it works for a long time, but currently
i want to use vlan network, so i deploy a new environment everything
is same as the previous one, just use vlan network.
to same network? As per the doc,
it should be 10.10.10.3? Plus, these both belong to Data-Network, which is
not controller-network communication but compute-network communication.
-Regards
Rahul
On Sat, Feb 23, 2013 at 12:53 AM, Aaron Rosen aro...@nicira.com wrote:
From the network
.
2013/2/22 Guilherme Russi luisguilherme...@gmail.com
Hello Aaron,
Here are the outputs.
Thanks.
Guilherme.
2013/2/21 Aaron Rosen aro...@nicira.com
The output to the following would be a good start:
quantum net-list
quantum port-list
ovs-dpctl show (on all nodes)
Also make sure
: Job is already running: quantum-plugin-openvswitch-agent
Is there another thing i should do? I'm running my controller node and
the network node at the same machine with 2 NICs, maybe can be a problem
how i am making my network config?
Thanks again.
Guilherme.
2013/2/22 Aaron Rosen aro
not pretty sure, but i guess the
data from the VMs should communicate with this IP).
2013/2/22 Aaron Rosen aro...@nicira.com
Running with two nics for this should be fine for tunneling as ip routing
would handle which nic the packets should go out. From what you pasted I
see that one HV has a gre
Hi,
You'll have to provide more information than this for anyone to help you:
i.e are you using quantum or nova-network, if your using quantum which
plugin, config files etc.
Aaron
On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi
luisguilherme...@gmail.com wrote:
Hello guys,
I'm getting
.
Guilherme.
2013/2/21 Aaron Rosen aro...@nicira.com
Hi,
You'll have to provide more information than this for anyone to help you:
i.e are you using quantum or nova-network, if your using quantum which
plugin, config files etc.
Aaron
On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi
Anything is possible with upgrading but hopefully not :P
On Mon, Feb 18, 2013 at 4:18 AM, Guilherme Russi luisguilherme...@gmail.com
wrote:
Hello guys,
I got a message from my Ubuntu Server 12.04 about upgrade somethings, the
upgrades include Linux Headers and some upgrades for openstack's
The issue is your laptop doesn't have a route to that network. Try running
this on your laptop to see if this makes it work:
sudo ip route add 192.168.4.0/24 dev wlan0 # replace wlan0 with the
correct interface
If that doesn't work perhaps give this one a shot:
route add -net 192.168.4.0
Which plugin are you trying to use? You mentioned both linuxbridge and
openvswitch in your email.
Aaron
On Mon, Feb 11, 2013 at 8:33 AM, Greg Chavez greg.cha...@gmail.com wrote:
Running latest EPEL Folsom packages on RHEL 6.3. Three nodes right now,
one controller, one network node, one
Hi Greg,
I checked out why this can happen and I think the reason you are getting
this is because you are trying to create a vm as an admin user on a network
that you are not the owner.
https://github.com/openstack/nova/blob/master/nova/network/quantumv2/api.py#L95
Thanks,
Aaron
On Sun, Feb
Looks like you are missing this part:
http://docs.openstack.org/trunk/openstack-network/admin/content/keystone.html
Aaron
On Fri, Feb 8, 2013 at 12:55 PM, Rain Li lyp20062...@gmail.com wrote:
Hi all,
When setting the virtual network on network-node with the basic-install
guide, I failed to
Yup, it can be done via this:
git push ssh://review.openstack.org:29418/openstack/project.git
HEAD:refs/for/branch
Aaron
On Sun, Feb 3, 2013 at 6:40 PM, Huang Zhiteng winsto...@gmail.com wrote:
Git-review is python script, therefore it's possible to install it onto
windows system, however
Hi,
Yup this is definitely possible. The reason why this isn't set by default
is that some distros don't ship kernels that build with CONFIG_NET_NS=y or
their iproute2 package is to outdated to support linux namespaces. Also,
until recently nova's metadata service didn't support overlapping ips.
Nova (network) does not support overlapping ip addresses so if you use nova
security groups directly this won't work. This should be fixed in G3 using
nova security groups with a nova to quantum security group proxy.
Until recently nova meta data did not work with overlapping ips but that
works
It allows one to setup an openstack deployment from source quickly (helpful
for developers) see http://devstack.org/faq.html.
There is no graphical interface except for horizon which you have to access
via a browser after stack.sh completes (if you install horizon).
Aaron
On Tue, Jan 15, 2013
Can you show the qemu-kvm command you are running?
On Tue, Oct 23, 2012 at 8:48 AM, AK Sathiya ak_m...@hotmail.com wrote:
Thanks Aaron, i have only qemu-kvm not kvm. The issue was the image type is
qcow2. When I changed it to the following I got pass that issue.
qemu-image create -f qcow2
Do you have two default gateways in your instance when you type route -n ?
Aaron
On Tue, Oct 23, 2012 at 2:12 PM, Jason Ford ja...@chatinara.com wrote:
This seems broke unless I have something weird going on in my ovs setup. I
can get quantum to assign the second IP address to the instance
PM, Aaron Rosen aro...@nicira.com wrote:
Do you have two default gateways in your instance when you type route -n ?
Aaron
On Tue, Oct 23, 2012 at 2:12 PM, Jason Ford ja...@chatinara.com wrote:
This seems broke unless I have something weird going on in my ovs setup.
I can get quantum
The following should do the trick for you in order to create a new
disk and boot an iso using it :
IMAGE=centos-6.2.img
qemu-img create -f raw $IMAGE 5G
sudo kvm -hda $IMAGE -m 512 -smp 2 -cdrom centos_installer.iso -boot c
Aaron
On Mon, Oct 22, 2012 at 8:36 AM, AK Sathiya ak_m...@hotmail.com
Hi Liem,
Nachi, is working on the security groups implementation for the
OVSPlugin which I believe will be using iptables. (@Nachi, correct me
if I'm wrong here.)
Thanks,
Aaron
On Mon, Oct 22, 2012 at 11:16 AM, Nguyen, Liem Manh
liem_m_ngu...@hp.com wrote:
Hi fellow stackers,
I see a
Hi Balaji,
This issue seems to have been solved for Srikanth here:
https://answers.launchpad.net/quantum/+question/208446
Thanks,
Aaron
On Tue, Sep 18, 2012 at 1:53 AM, Srikanth Kumar Lingala
srikanthkumar.ling...@gmail.com wrote:
Hi Dan,
Yes, we have mentioned valid rabbit_host,
Hi Joy,
I did noticed a bug in ovs_lib.py but it would cause q-agt to crash. Did
the agent crash?
Aaron
On Thu, Aug 30, 2012 at 2:48 PM, Naveen Joy (najoy) na...@cisco.com wrote:
Hi All,
** **
I am running the latest quantum code base. I am seeing an issue in which
the openvswitch
Hi,
I'm running devstack and when I boot vms I seem to be running into this
error in glance which I believe is causing the cirros image to just hang
on Booting from ROM... I was wondering if anyone has run into this
before? (Logs below)
Thanks,
Aaron
arosen@controller:/opt/stack$ nova
in pre-F3 after
e-mails with Aaron Rosen when he helped me get going earlier, I’ve tried
both ways and seems not to make a difference)
Added NOVA_USE_QUANTUM=v2 (but this doesn’t seem to make a difference
either)
** **
And I ran devstack.
** **
I got no errors when I ran devstack
inline
On Thu, Aug 23, 2012 at 1:34 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
Any inputs for understanding and resolving the issue...
Kindly help me in this regard.
--
Trinath
On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi
, Aug 18, 2012 at 3:48 AM, Eugene Kirpichov ekirpic...@gmail.comwrote:
Thanks. And how will n-net react?
18.08.2012, в 0:43, Aaron Rosen aro...@nicira.com написал(а):
Hi Eugene,
This means that if a VM stops it's DHCP client that nova-network will be
aware of this since the VM
Hi Eugene,
This means that if a VM stops it's DHCP client that nova-network will be
aware of this since the VM will not attempt to renew it's DHCP lease.
Aaron
On Fri, Aug 17, 2012 at 5:58 PM, Eugene Kirpichov ekirpic...@gmail.comwrote:
Hi,
The documentation
By far in my opinion the easiest route to take in order to quickly try out
and play with the latest code is www.devstack.org.
Aaron
On Fri, Aug 17, 2012 at 3:17 AM, Salvatore Orlando sorla...@nicira.comwrote:
Hi,
Folsom-3 is going to be released this evening GMT. Expect it to be
available
The dhcp agent now is able to use network namespaces so there is no longer
ip conflicts. Perhaps in the future the dhcp agent could implement some
kind of DHCP reply (ip helper) service . Though currently it allocates an
ip address in each subnet that you want dhcp enabled on.
Aaron
On Mon, Aug
You can definitely disable the dhcp and provide your own means of providing
dhcp. Do you have a specific use case in mind that isn't addressed by
either these two already provided?
Aaron
P.S; the quantum dhcp agent now support for overlapping ip :)
On Mon, Aug 13, 2012 at 2:30 AM, Trinath
The reason for this is because you can have multiple subnets on the same L2
bcast domain. You can use ip aliasing in order to use multiple subnets on
one virtual nic. For example ifconfig eth0:1 a.b.c.d/24; ifconfig eth0:2
d.e.f.g/24
Aaron
On Mon, Aug 13, 2012 at 7:52 PM, Takaaki Suzuki
** **
*From:* Aaron Rosen [mailto:aro...@nicira.com]
*Sent:* Tuesday, August 07, 2012 1:33 PM
*To:* Gabriel Hurley
*Cc:* openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Quantum devstack authentication error
** **
Hi Gabriel,
** **
Adding Q_AUTH_STRATEGY=noauth to localrc
in devstack.
It should be instead removed from ENABLED_SERVICES if running quantum v2.
Regards,
Salvatore
On 7 August 2012 23:15, Aaron Rosen aro...@nicira.com wrote:
Inline
On Tue, Aug 7, 2012 at 2:05 PM, Gabriel Hurley gabriel.hur...@nebula.com
wrote:
Thanks, that got it. Two things
Hi Syd,
There should not be an additional gateway interface on the compute nodes,
only the node that has n-net in ENABLED_SERVICES. I'm assuming you want to
use the OVSQuantumPlugin? Can you also
attach /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini from your
two nodes? Also if you are
Hi Edgar,
The easiest thing to do right now is to delete the following line from
your quantum.conf (And any line that does not have anything after the
'=' ).
api_extensions_path =
Alternatively, you could apply the following patch:
https://review.openstack.org/#/c/9892/
Thanks,
Aaron
On
Hi Trinath,
Yes, you need to install openvswitch and the quantum-agent on the nova
compute nodes as well.
Aaron
On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
With respect to your document, on Openstack - OVS and Quantum,
I'm unable to understand
= mysql://ovs_quantum:password@10.68.1.40:3306/ovs_quantum
Please guide me understand the same,
On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.com wrote:
Hi Trinath,
Yes, you need to install openvswitch and the quantum-agent on the nova
compute nodes as well.
Aaron
On Fri
98 matches
Mail list logo
