[Openstack] [neutron][devstack]subnet created with wrong gateway

Hi, I am using devstack for the first time and I see that it has created a subnet like below. The cidr and gateway do not match. Because of this devstack fails to run completely and fails while attaching a router to this subnet. Why is devstack doing this?? stack@controller:~/devstack$ neutron sub

[Openstack] [keystone]user role revoke from one tenants disables user's token got using another tenant

Hi, There is a use case where keystone seems to behave improperly. Not sure if it is a bug, please do comment. A user has 'admin' role for two tenants. When I remove 'admin' role association from one tenant for the user, the user's token got earlier for other tenant becomes invalid. However if

Re: [Openstack] HTTP 500 - The server has either erred or is incapable of performing the requested operation WHEN launch an instance

gt; - Yes, single machine that installed all service including compute service. > - Yes, official document. > http://docs.openstack.org/icehouse/install-guide/install/yum/content/ > > > On Mon, May 11, 2015 at 10:21 AM, Akilesh K wrote: > >> What do you mean by 'we d

Re: [Openstack] HTTP 500 - The server has either erred or is incapable of performing the requested operation WHEN launch an instance

What do you mean by 'we don't have any compute'. Is is that you have a single machine where you installed all service including compute service? Do tell us which instruction you followed for manual installation(is it the official openstack documentation or something else). On Mon, May 11, 2015 at

Re: [Openstack] Change from GRE to vlan

-+--+ > > > > root@neutron:# ip netns > > qdhcp-5496a11e-6671-406b-9eb8-a6460effc853 > > qrouter-b5e219a7-a81c-45d9-9009-a6696b008be3 > > > > root@neutron:# ip netns exec qrouter-b5e219a7-a81c-45d9-9009-a6696b0

Re: [Openstack] Change from GRE to vlan

ions=drop > > cookie=0x0, duration=1114.149s, table=0, n_packets=613, n_bytes=41365, > idle_age=2, priority=1 actions=NORMAL > > > > root@neutron:# ovs-ofctl dump-flows br-eth1 > > NXST_FLOW reply (xid=0x4): > > cookie=0x0, duration=71982.785s, table=0, n_packets=10, n_b

Re: [Openstack] Change from GRE to vlan

Apart from type_driver, there are many other setting in 'ml2_conf.ini'. Like below [ml2] mechanism_drivers=openvswitch type_drivers=vlan,flat tenant_network_types=vlan,flat [ml2_type_flat] flat_networks=Extnet [ml2_type_vlan] network_vlan_ranges=Intnet1:100:200 [ovs] bridge_mappings=Intnet1:br-

Re: [Openstack] [neutron]Multiple l3 agents

good idea to remove that setting and allow it to > use the default of the system hostname (assuming each node has different > hostnames). > > Also, you shouldn't be setting 'router_id' in l3_agent.ini. That's for > restricting the agent to one router when namespaces

Re: [Openstack] [neutron]Multiple l3 agents

usr/bin/neutron-l3-agent --config-file > /etc/neutron/neutron.conf --config-file /etc/neutron/l3_agent2.ini > --config-file /etc/neutron/fwaas_driver.ini" > > Regards, > Akash > > [image: Inactive hide details for Akilesh K ---03/18/2015 11:06:17 > AM---Yes I did the sam

Re: [Openstack] [neutron]Multiple l3 agents

Yes I did the same. But I've heard of people doing multiple l3 agent scenarios with success, Only that we are not getting replies. I am not sure If I am being paranoid, but I have a feeling that the community interaction these days are going down and corporate interactions are dominating. Will kee

Re: [Openstack] [neutron]Multiple l3 agents

ured that each > agent is started with its respective config file argument set? This would > need to be changed in the upstart script of the respective agent. There may > be other arguments that need to change as well. I don't have a setup in > front of me. > > James > > >

Re: [Openstack] [neutron]Multiple l3 agents

Anyone has done this configuration yet and got it right? On Wed, Mar 4, 2015 at 3:21 PM, Akilesh K wrote: > Hi, > What are the exact steps and configuration to run multiple l3 agents. > > > I have set separate config files with params > gateway_external_net

[Openstack] [neutron]Multiple l3 agents

Hi, What are the exact steps and configuration to run multiple l3 agents. I have set separate config files with params gateway_external_network_id, router_id, external_network_bridge for each of them. handle_internal_only_routers is false for one and true for another. After I start the agents o

Re: [Openstack] [neutron][juno]l3-agent issues

could and this was preventing from floatingip to be updated without a restart. As soon as I stopped the second l3 agent things were back to normal. Hope the information is useful to everyone. Thank you, Ageeleshwar K On Wed, Feb 11, 2015 at 6:42 PM, Akilesh K wrote: > Hi, > I have som

[Openstack] [neutron][juno]l3-agent issues

Hi, I have some issues with l3-agent, explained below. Kindly let me know how to debug the same and conclude if its a bug or misconfiguration. Issue 1: 1. The router namespace is not created unless I set router_id, external_network_gateway, and external_network_bridge in l3-agent.ini. As per the d

Re: [Openstack] Neutron Network scenarios

Have you already done these ? Thankyou, Ageeleshwar K On Tue, Feb 10, 2015 at 9:41 AM, Kamsali, RaghavendraChari (Artesyn) < raghavendrachari.kams...@artesyn.com> wrote: > Hi, > > > > Where can I fo

Re: [Openstack] [neutron][nova] vif_plugging_is_fatal significance?

or the nova_url parameter.[1] > > 1. > https://github.com/openstack/neutron/blob/33b83554442b7c0d862a2adb0b2a8feab1185af9/etc/neutron.conf#L267 > > > On Thu, Feb 5, 2015 at 11:10 PM, Akilesh K wrote: > >> Great this is what I was looking for and I was suspecting the sam

[Openstack] [neutron][nova] vif_plugging_is_fatal significance?

Hi, I have a working openstack setup. But I have some questions on how I got it working. Initially my instances failed to launch. I have updated the correct values for neutron authentication in nova.conf and correct nova authentication in neutron.conf and notify_nova on port change is true but s

Re: [Openstack] [neutron][ml2][sriov]Issues with neutron behaviour

Irena Berezovsky wrote: > > > On Thu, Feb 5, 2015 at 9:38 AM, Akilesh K wrote: > >> I know that vif_type is binding_failed on a multinode setup and I also >> know why it happens. >> >> As for interface-attach I got it work for sriov ports and even verified >>

Re: [Openstack] [neutron][ml2][sriov]Issues with neutron behaviour

else wants to do this. Thank you, Ageeleshwar K On Thu, Feb 5, 2015 at 12:19 PM, Irena Berezovsky wrote: > Hi Akilesh, > Please see my responses inline. > Hope this help, > > BR, > Irena > > On Thu, Feb 5, 2015 at 6:14 AM, Akilesh K wrote: > >> Hi Irena, >>

Re: [Openstack] [neutron][ml2][sriov]Issues with neutron behaviour

fo is not updated by anyone but me. and pci_slot is also not populated. Do you still think this is correct ? On Wed, Feb 4, 2015 at 8:08 PM, Irena Berezovsky wrote: > Hi Akilesh, > please see inline > > On Wed, Feb 4, 2015 at 11:32 AM, Akilesh K wrote: > >> Hi, >> Issue

Re: [Openstack] [neutron][ml2][sriov]Issues with neutron behaviour

e 1; > You must specify the physical networks. > Please look at: > https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking > > Issue 2: > AFAIK the agent is supported by only one vendor. > Can you please look for errors in Neutron's log? > > Thanks, > Itzi

[Openstack] [neutron][ml2][sriov]Issues with neutron behaviour

Hi, I found two issues with the way neutron behaves on a multi server install. I got it to work but I do not this this is the right way to do it. It might be a bug we might want to fix and for which I could volunteer. Setup - Multiserver juno on ubuntu. Machine 1 - Controller All api servers , l3

[Openstack] [nova][glance][cinder]Configuring image properties elsewhere

Hi, I have an image that boots only when I set the following properties. --property hw_disk_bus=ide --property cdrom_bus=ide --property hw_vif_model=e1000 Unfortunately when I create a volume from the image, and launch and instance, it gets stuck at boot loader. Is there a way I can set these pr

Re: [Openstack] How to configure SR-IOV with Neutron

Your neutron-server could not bind to socket. This has nothing to do with sriov. I am wondering how you got aget-list when your neutron-server isn't listening on 9696. Besides the agent-list does not list 'neutron-sriov-nic-agent'. I believe your neutron-server is already running and the error you

Re: [Openstack] [neutron][l3-agent] router-create does not create namespaces in juno

ternal_network_id' option must be configured for this agent as Neutron has more than one external network. Surprisingly this part of the log only pops up when i run l3-agent as root from cli and does not write to log file when it is started as neutron user from init. When the second external netwo

[Openstack] [neutron][l3-agent] router-create does not create namespaces in juno

Hi, I am facing a strange issue where in juno, creating a router does not create a namespace. I even attached router to subnet and set external gateway and still nothing happens. The router's ports are in 'down' status and they are not seen when i do 'ovs-vsctl show' use_namespace is True in l3-a

Re: [Openstack] [openstack-dev] [neutron][sriov] PciDeviceRequestFailed error

itelist" in nova.conf? > > > > > > > At 2014-12-04 18:26:21, "Akilesh K" wrote: > > Hi, > I am using neutron-plugin-sriov-agent. > > I have configured pci_whitelist in nova.conf > > I have configured ml2_conf_sriov.ini. > > But when I la

[Openstack] [neutron][sriov] PciDeviceRequestFailed error

Hi, I am using neutron-plugin-sriov-agent. I have configured pci_whitelist in nova.conf I have configured ml2_conf_sriov.ini. But when I launch instance I get the exception in subject. On further checking with the help of some forum messages, I discovered that pci_stats are empty. mysql> sele

Re: [Openstack] Juno cloud-archive error

@Antonio I had 92.37,1 after an upgrade it worked. I must have known it. Thank you, Akilesh On Wed, Nov 12, 2014 at 9:03 PM, Antonio Messina < antonio.s.mess...@gmail.com> wrote: > Which version of package `software-properties-common` do you have? > Juno release was added with version `0.92.37.2

Re: [Openstack] Juno cloud-archive error

rchives are only provided for LTS releases), so I suspect you > issue is that you're not using Ubuntu 14.04 as I have added the juno > cloud archive on some of my test systems. > > -Jon > > On Wed, Nov 12, 2014 at 3:40 PM, Akilesh K wrote: > > As per 'https://wiki.

Re: [Openstack] Juno cloud-archive error

Looks like Ubuntu users have to wait for a while. https://bugs.launchpad.net/openstack-manuals/+bug/1362521 On Wed, Nov 12, 2014 at 8:10 PM, Akilesh K wrote: > As per 'https://wiki.openstack.org/wiki/Juno_Release_Schedule' Juno was > supposed to be release on 16th of October

[Openstack] Juno cloud-archive error

As per 'https://wiki.openstack.org/wiki/Juno_Release_Schedule' Juno was supposed to be release on 16th of October. But when I do 'add-apt-repository cloud-archive:juno', I get ''juno': not a valid cloud-archive name' So where does OpenStack update its release schedule updated? __

Re: [Openstack] Very low bandwidth between instances and routers with OVS, GRE on Debian Jessie (Icehouse)

Hi Alberto, May I know the flavor and image you were using to do this test. TSO seems to be a method that moves the process of tcp segmentation off to the nic card. I believe in OpenStack the nic is a tap interface that kvm attaches your instance to and hence you have offloaded the task of segment

Re: [Openstack] able to ping but not able to ssh to instance

s dropping the ssh traffic .? > how can i confirm that ssh traffic is blocked at firewall .? > i there any way to see the firewall dropped packets ? > > thanks , > srinivas. > > > > > > > > On Thu, Sep 18, 2014 at 7:36 PM, Akilesh K wrote: > >> I be

Re: [Openstack] able to ping but not able to ssh to instance

I believe you have checked the security group rules. Make sure the instance is able to ping the router. If yes the problem lies in your host's firewall rules. Flush the hosts iptable rules(you may take a backup before you do that). On Thu, Sep 18, 2014 at 7:32 PM, Srinivasreddy R < srinivasreddy4.

Re: [Openstack] able to ping but not able to ssh to instance

Check your security group rules. Allow ingress port 22. On Sep 17, 2014 8:45 PM, "Srinivasreddy R" wrote: > hi, > i am able to ping my instance form external network . > but not able to ssh to the instance . > i am using floating ip s for ping,ssh. > please help me . > > thanks, > srinivas. > >

Re: [Openstack] A strange solution for instances not getting their ip

I have faced stranger stuff with cirros. I would see dhcp lease messages using tcpdump exactly on the instances port but still cirros keeps sending discover messages. On Sep 17, 2014 8:24 PM, "Claudio Pupparo" wrote: > Hi, > > I have the common issue of instances not getting their ip. > When I st

Re: [Openstack] router cannot communicate with external

network node's port that has been added to br-ex must be set to the vlan id corresponding to the external network's segmentation id. Good luck. ping me if anything I have listed is not clear, or you need more information. Thank you, Akilesh K On Thu, Jul 24, 2014 at 3:47 PM, Akilesh K

[Openstack] Post on network virtualization in linux

Hi, Please do review my recent post on linux bridging/routing http://fosskb.wordpress.com/2014/06/25/a-bite-of-virtual-linux-networking/ Please leave back your valuable comments. Thank you, Ageeleshwar K ___ Mailing list: http://lists.openstack.org/cgi

Re: [Openstack] GRE tunnel

. On Thu, Jun 19, 2014 at 5:59 PM, wrote: > Hi, > > > > Thanks for the reply. > > > > What is the use of promiscuous mode in openstack ? > > > > > > Thanks > > Kumar > > > > *From:* Akilesh K [mailto:akilesh1...@gmail.com] >

Re: [Openstack] GRE tunnel

Openstack support multi tenant networks. That means two tenants may use the same network space. There must be some other way to isolate the networks of different tenants. So every network in Openstack is assigned a special segmentation id. In case of gre the segmentation id is the tunnel id. In cas

Re: [Openstack] [openstack] instances without subnet

; during the conference… > > Anyway, we could probably go through blueprints, and find something there. > > > > Marek > > > > *From:* Tiago Sousa [mailto:tiagu@gmail.com] > *Sent:* 17. júna 2014 15:09 > *To:* Ruzicka, Marek > *Cc:* Akilesh K; openstack@lists.

Re: [Openstack] ML2 Plugin and vif_type=binding_failed

: > > Hi, > > > > This error occurs when the config is wrong wither on controller or > > the compute. Check the ml2_conf.ini on controller and > > ovs_plugin.ini on the compute. > > > > > > Regards, Akash > > > > > > > > From: Heiko

Re: [Openstack] [openstack] instances without subnet

I believe Openstack has not been developed like that. Can you tell more about why you would like to do it? @Remo Mattei I am unaware of how to use provider network to achieve this. Can you please give us some leads. Thank you, Ageeleshwar K On Tue, Jun 17, 2014 at 4:02 PM, Tiago Sousa wrote:

Re: [Openstack] ML2 Plugin and vif_type=binding_failed

| > vif_type| driver | segment | vnic_type | vif_details | profile > - > > ------+--+++-+---+-+- > 39bb4ba0-3d37-4ffe-9c81-073807f8971a | nettesting.hydranode

Re: [Openstack] ML2 Plugin and vif_type=binding_failed

File looks good except that [agent] section is not needed. Can you reply with some log from '/var/log/neutron/server.log' during instance launch exactly. The vif_type=binding_failed occurs when neutron is unable to create a port for some reason. Either neutron server log or the plugin's log file s