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
overlappi
nova --os-tenant-name
Aaron
On Thu, Jul 25, 2013 at 9:06 PM, Remo Mattei 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 instance
>
> Thanks
> _
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
>
> anything else I need to check? Does above looks right to you?
>
> Thanks
>
> Haitao
>
> On Tue, Jul 9, 2013 at 10:29 PM, Aaron Rosen wrote:
> > You should be able to compile open
er "punix:/var/run/openvswitch/br-tun.mgmt"
> 2013-07-09T23:28:18Z|00012|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0
> 2013-07-09T23:28:28Z|00013|memory|INFO|7848 kB peak resident set size
> after 10.0 seconds
> 2013-07-09T23:28:28Z|00014|memory|INFO|ports:5 rules:11
> 2013-
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 wrote:
> I just set up a multi-node Grizzly release 2013.2 wit
e error
> message. I am using Grizzly release.
>
>
quantum security-group-rule-create --protocol tcp --ethertype IPv4
--port-range-min 1 --port-range-max 65535 --remote-ip-prefix 0.0.0.0/0
default
or
nova secgroup-add-rule default tcp 1 65355 0.0.0.0/0
> Thanks and Regards
>
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=
Aaron
On Thu, Jun 27, 2013 at 5:54 AM, Rah
Hi Rami,
On Tue, Jun 18, 2013 at 11:36 PM, Rami Vaknin 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. http://docs.openstack.org/**trunk/openstack-network
figure out why network packets 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
>
>>
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 wrote:
> Hi,
>
> I recently setup a openstack on one node, which is hosting all the services
> like keystone, nova, glance, cinder, etc.
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 wrot
>
> 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. Those are all
> done in i
> 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
ault |
> | 5902febc-e793-4b09-8073-567226d83d79 | d11 | des for firewall |
> +--+-+--+
>
>
>
> Daniels Cai
> http://dnscai.com
>
>
> 2013/6/8 Aaron Rosen
>
>> You said:
>>
>> >it w
5b573cca 192.168.192.0/24 |
>
>
> i enabled the following features in quantum
> 1. namespace
> 2. overlap ips
>
> if any more info needed for debug, i will attach
>
>
>
> Daniels Cai
> http://dnscai.com
>
>
> 2013/6/8 Aaron Rosen
> >
> > There is no
uck, it still doesn't work .
>
> Any advice ? does quantum security group support this feature?
>
> Daniels Cai
> http://dnscai.com
>
>
> 2013/6/8 Aaron Rosen
>
>> Hi Joe,
>>
>> I thought setting firewall_driver =
>> quantum.agent.firewall.N
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 wrote:
> Hello,
>
> Is there a way
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
co
ound for name 'default', use an ID to be
> more specific.
>
> (quantum)
>
> ** **
>
> Actualy my first tenant’s several VMs don’t have network issue. Can ping
> their’s floating IP from Internet.
>
> However my second tenant’s several VMs h
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 Mo
n 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 wrote:
>
>> No but the provider network extention does provide a way t
face and the output interface should be on the
> same network.
>
> Now I manually modify the packet vlan using OpenFlow protocol at the two
> NICs, so that the loop won't happen.
>
>
> On Thu, May 30, 2013 at 2:11 PM, Aaron Rosen wrote:
>
>> I still don't see why
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
wrote:
> HI Salvatore,
>
> It's possible start an instance which is distributed across several
> nodes. it's my goal
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 wrote:
> Hello:
>
> I have a network with a subnet, I want create
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 wrote:
> Hi,
>
> IS there any way to access VM from external
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 wrote:
> Hello everyone,
>
> I wonder if someone can give me a more detail overview about the r
> which api’s should be exposed which is causing 2 to use the same port.***
>> *
>>
>> ** **
>>
>> **-**Philip
>>
>> ** **
>>
>> *From:* Openstack [mailto:openstack-bounces+philip.schwartz=
>> lexisnexis@lists.launchpa
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
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 : https://help.launchpad.net/ListH
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 wrote:
> **
> **
>
> Hi all,
>
> I've installed openstack using quantum by the guide
> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/
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, S
>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 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> so I had a tenant that was assigned a floating IP. I deleted the project
> before
> I fr
0.0 B) TX bytes:0 (0.0 B)
>
> qg-193bb8ee-f5 Link encap:Ethernet HWaddr fa:16:3e:91:3d:c0
> inet addr:10.5.12.21 Bcast:10.5.12.255 Mask:255.255.255.0
> inet6 addr: fe80::f816:3eff:fe91:3dc0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:
hen the instance
>>>> boots up, so I assume its coming from the DHCP. Any idea how this can be
>>>> suppressed?
>>>>
>>>> Strangely though, I do not see this route in a WindowsXP VM booted in
>>>> the same network as the earlier Ubuntu VM and
om the DHCP. Any idea how this can be
>> suppressed?
>>
>> Strangely though, I 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
ssue is with the Ubuntu
> VM.
>
> Thanks,
> Balu
>
>
>
> On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen 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
9.254 tell 192.168.2.3,
> length 28
> 23:32:16.766896 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
> length 28
> 23:32:17.766712 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
> length 28
> 23:32:18.784195 ARP, Request who-has 169.254.169.254 tell 192.168.2.3,
> lengt
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
wrote:
> Hi,
>
> In Grizzly, when using quantum and overlapping
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, 陈雷 wrote:
> Hi, All
>
> I'm testing hot-plug network interface, I can successfully hot-add an
> interface
address it got assigned.
>
>
>
>
> On Thu, Apr 18, 2013 at 12:21 AM, Aaron Rosen 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
>> or ch
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
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 Vishnoi wrote:
See: https://wiki.openstack.org/wiki/Quantum/LBaaS/HowToRun
On Tue, Apr 16, 2013 at 8:38 PM, HuYanrui 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.
> It should contain
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 AM,
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 wrote:
>
>
> -- Forwarded message --
> From: Deepak A.P
> Da
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 # Public ip
pool
quantum net-create non-DMZ --external=True
quantum subnet-create --name nonDMZ-Sub
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 wh
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 /var
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
Yes, this is fine because the vlans don't conflict on the same physical
interface.
Aaron
On Sun, Mar 31, 2013 at 10:22 PM, Balamurugan V G
wrote:
> Hi,
>
> While using a OVS plugin based Quantum setup, will it be possible to go
> beyond 4095 vlans by re-using them across multiple physnets. For
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 wrote:
> Hi,
>
> I be
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 clean
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.
> My questions are:
>
>- Am I missing something simple here?
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:
> Thank
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
2013 11:49 AM, Aaron Rosen wrote:
>>
>> 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?
>
>
> Because most, if not virtually
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 wrote:
> On 03/08/2013 09:55 AM, Aaron Rosen 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 should
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 wrote:
> Hi all,
>
> I want to play LBaas from quantum, but I was used nova-network FlatDHCP
> to setup
(because the controller's IP is not with the VMs IP)
>
> Sincerely,
> Hsiao
>
>
> On Thu, Feb 28, 2013 at 12:15 PM, Aaron Rosen 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
tack_Folsom_Install_Guide_WebVersion.rst
>
> REMEMBER 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 wrote:
>> Hi
>>
>&g
Hi
response inline
On Wed, Feb 27, 2013 at 3:22 PM, The King in Yellow
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 controller/network/comput
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 wro
inline
On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan 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.
>
> here is the pr
On Tue, Feb 26, 2013 at 11:02 PM, Aaron Rosen wrote:
> inline
>
> On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan wrote:
>
>> greeting, stackers
>>
>> i deploy essex with flatdhcp, it works for a long time, but currently
>> i want to use vlan network, so i deplo
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 wrote:
>
>>
ording to their network
> # connectivity.
> #
> # Default: integration_bridge = br-int
> integration_bridge = br-int
>
> # Only used for the agent if tunnel_id_ranges (above) is not empty for
> # the server. In most cases, the default value should be fine.
> #
> # Defaul
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.
>
&
t;
> 2013/2/22 Guilherme Russi
>
>> Hello Aaron,
>>
>> Here are the outputs.
>>
>>
>> Thanks.
>>
>> Guilherme.
>>
>>
>> 2013/2/21 Aaron Rosen
>>
>>> The output to the following would be a good start:
>>&
html
>
> Which config files do you need?
>
> Thanks.
>
> Guilherme.
>
>
> 2013/2/21 Aaron Rosen
>
>> 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 u
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 gett
Anything is possible with upgrading but hopefully not :P
On Mon, Feb 18, 2013 at 4:18 AM, Guilherme Russi 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
> components. My questi
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 netma
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 wrote:
>
> Running latest EPEL Folsom packages on RHEL 6.3. Three nodes right now,
> one controller, one network node, one compute node. The net
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 1
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 wrote:
> Hi all,
>
> When setting the virtual network on network-node with the basic-install
> guide, I failed to authenticate with
Yup, it can be done via this:
git push ssh://review.openstack.org:29418/openstack/.git
HEAD:refs/for/
Aaron
On Sun, Feb 3, 2013 at 6:40 PM, Huang Zhiteng wrote:
> Git-review is python script, therefore it's possible to install it onto
> windows system, however it is more convenient to use Li
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 now
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.
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 at
Are the eth* interfaces up that are attached to the bridge?
On Tue, Oct 23, 2012 at 3:09 PM, Jason wrote:
> Only one listed. What is more odd is that I am not seeing arps being
> returned so this issue seems to be at layer 2. Any other ideas?
>
> Jason
>
> On Oct 23, 2012,
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 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 but when
> trying to
Can you show the qemu-kvm command you are running?
On Tue, Oct 23, 2012 at 8:48 AM, AK Sathiya 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 $IMAGE 5 G
>
> How
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
wrote:
> Hi fellow stackers,
>
>
>
> I see a blueprint for securi
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 wrote:
> All, i am 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, rabb
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) wrote:
> Hi All,
>
> ** **
>
> I am running the latest quantum code base. I am seeing an issue in which
> the openvswitch agent is no
r.
>
> ** **
>
> To get sync’d up with the latest, I did the following:
>
> ** **
>
> $ rm –rf /opt/stack (this is where devstack pulled things to)
>
> $ rm –rf /etc/quantum; rm –rf /etc/nova
>
> ** **
>
> In the devstack localrc:
&g
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 ima
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.
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 wrote:
> Hi,
>
> The documentation
>
> http://docs.openstack.org/diablo/openstack-com
on
On Sat, Aug 18, 2012 at 3:48 AM, Eugene Kirpichov wrote:
> Thanks. And how will n-net react?
>
>
>
> 18.08.2012, в 0:43, Aaron Rosen написал(а):
>
> Hi Eugene,
>
> This means that if a VM stops it's DHCP client that nova-network will be
> aware of this since the
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 wrote:
> Hi,
>
> Folsom-3 is going to be released this evening GMT. Expect it to be
> available after 1700 GMT.
>
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 wrote:
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 Somanc
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 1
ck, it seem n-net is still enabled in devstack.
> It should be instead removed from ENABLED_SERVICES if running quantum v2.
>
> Regards,
> Salvatore
>
>
> On 7 August 2012 23:15, Aaron Rosen wrote:
>
>> Inline
>>
>> On Tue, Aug 7, 20
2Api
> **
>
> **- **Gabriel
>
Aaron
>
>
> ** **
>
> *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 e
Hi Gabriel,
Adding Q_AUTH_STRATEGY=noauth to localrc should fix the issue.
The authentication it's trying to use only works in folsom.
Thanks,
Aaron
On Tue, Aug 7, 2012 at 1:04 PM, Gabriel Hurley wrote:
> I'm trying to run devstack with quantum enabled so I can test the recent
> work on re-in
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 i
1 - 100 of 103 matches
Mail list logo
