Re: [Openstack] [essex vlan]cannot ping vm on other compute node

since i notice that in switcher: sw-31>show interface fastEthernet 0/22 trunk PortMode Encapsulation StatusNative vlan Fa0/22 on 802.1q trunking 1 Port Vlans allowed on trunk Fa0/22 1-4094 PortVlans allowed and active in mana

Re: [Openstack] [essex vlan]cannot ping vm on other compute node

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

Re: [Openstack] [essex vlan]cannot ping vm on other compute node

thank you very much. actullaly, i have already try these command yesterday, it does not work. currently, i find that vlan id in active list and not pruned list can be passed by switcher, vlan id not in the two list cannot will be droped even they are in allowed list. but the network administr

Re: [Openstack] [essex vlan]cannot ping vm on other compute node

I'm not sure I followed the thread correctly from the beginning, but I read that you have configured you NIC for private VM networking, in VLAN mode, on VLAN 105. Is that correct? In general trunking all your switch ports used for VM networking will save you the hassle of adding the VLANs you are

Re: [Openstack] [essex vlan]cannot ping vm on other compute node

thanks you for reply special thanks to Aaron Rosen the situation is that: 1) openstack is in vlan mode 2) switcher is in trunk mode, all vlan id is allowed 3) vlan in switcher's allowed list, active list and (not pruned) list can communicate with each other. vlan only in allowed list but not in th

[Openstack] Network configuration on compute node

Hello, I'm having troubles with the network configuration in a compute node. I followed this tutorial: http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/ But my instances are unable to get an IP via DHCP. The network configuration in the compute node when an insta

[Openstack] Fwd: Nova network problem on rhel6.4 and folsom

Sorry I didn't reply to list at first instance so I am forwarding it now Hi Vish Did some poking around but not sure about my conclusion. If you look at ip link show eth1 3: eth1: mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:30:48:35:3d:ff brd ff:ff:ff:ff:ff:ff br100: mtu 1

[Openstack] [Keystone] service unavailable

Hi, I am trying to setup keystone myself on CentOS using this step-by-step instructions: http://docs.openstack.org/essex/openstack-compute/install/yum/content/install-keystone.html I have followed the steps above but when I try to create a tenant I get "Unable to communicate with identity service

Re: [Openstack] [Keystone] service unavailable

Could you please paste your keystone.conf ? Also, could you please check keystone service is started ? -Sylvain Le 27/02/2013 15:06, Tomás( S(oltys a écrit : Hi, I am trying to setup keystone myself on CentOS using this step-by-step instructions: http://docs.openstack.org/essex/openstack-com

Re: [Openstack] [Keystone] service unavailable

Hi, Yes, the service is running and listening. I can see it via ps as well as by using netstat Here is my keystone.conf - [DEFAULT] log_file = /var/log/keys

Re: [Openstack] [Keystone] service unavailable

I'm not aware that keystone is capable of raising a 503 Service Unavailable... are you running through a proxy? If so, I assume there's an issue with it's configuration. -Dolph On Wed, Feb 27, 2013 at 8:27 AM, Tomáš Šoltys wrote: > Hi, > > Yes, the service is running and listening. I can see i

Re: [Openstack] [essex vlan]cannot ping vm on other compute node

Ajiva, In your 'show interface fa 0/2[2,3] trunk' output I don't see vlan 105 and this is most likely because it's not created. This might be why vlan 5 works and 105 doesn't. Try: > en # conf t # vlan 105 # exit Thanks, Kevin S On 2/27/13 4:22 AM, "Ajiva Fan" wrote: >thanks you for repl

[Openstack] keystone - service unavailable

Hi, I am trying to setup keystone myself on CentOS using this step-by-step instructions: http://docs.openstack.org/essex/openstack-compute/install/yum/content/install-keystone.html I have followed the steps above but when I try to create a tenant I get "Unable to communicate with identity service

Re: [Openstack] [Keystone] service unavailable

I do not think so. What I did is: 1. Installed CentOS as a virtual host 2. Installed openstack packages yum install -y openstack-utils openstack-keystone python-keystoneclient 3. Executed following commands: echo 12345678 | openstack-db --init --service keystone --password 12345678 openstack

Re: [Openstack] keystone - service unavailable

I do not thinks so. I just checked whether they are defined, and they are not. Regards, Tomas 2013/2/27 JuanFra Rodriguez Cardoso > It could be a problem with environment variables loaded previously (such > as OS_USERNAME, OS_PASSWORD...). > > Regards, > JuanFra > > > 2013/2/27 Tomáš Šoltys >

Re: [Openstack] [essex vlan]cannot ping vm on other compute node

Try these commands: Conf term Vlan 105 State active George -Original Message- From: openstack-bounces+george.mihaiescu=q9@lists.launchpad.net [mailto:openstack-bounces+george.mihaiescu=q9@lists.launchpad.net] On Behalf Of Ajiva Fan Sent: Wednesday, February 27, 2013 5:23 AM

[Openstack] Quotas for Glance and Snapshot

You can kind of quota for Snapshots generated images in OpenStack? There is a quota system where the limit of images Glance Snapshots and enter the quota? Only there are quotas on volumes and projects for not using Glance, Snapshot and even the root (/) of the instances. Best!

[Openstack] Horizon Silent Failure on Auth

All the bits appear to be working properly: # keystone user-list +--+-+-+---+ |id| name| enabled | email | +--+-+-+---+ | 4107f59814a84a75bec4c01

[Openstack] Cloudpipe - Routing not working

Hello guys, I need some advice with a cloudpipe setup. I have a basic Folsom installation (single server), using VlanManager. I am setting up a vpn for the subnet 10.0.4.0 (please see diagram below). instance1 nova-controller cloudpipe openvpn

[Openstack] Rebooted, now can't ping my guest

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/compute nodes and cloned the

Re: [Openstack] Rebooted, now can't ping my guest

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

Re: [Openstack] [essex vlan]cannot ping vm on other compute node

thank you, Kevin S, and also thanks George i did this command in the beginning of the time when i meet this problem, and it failed because """sw-31(config)#vlan 105 VTP VLAN configuration not allowed when device is in CLIENT mode.""" meanwhile i'm guided to a wrong way by our network administrator

Re: [Openstack] Network configuration on compute node

the output of `#brclt show` shows that your br100 is not bridged on any nic and the output of `ifconfig` shows that your br100 get no ipv4 addr br100 plays roles of: 1) gateway 2) dhcp server 3) dns server so since your br100 is not created correctly, i think the vm will not get an ip trough dhcp

Re: [Openstack] Rebooted, now can't ping my guest

Hi Aaron and The King in Yellow, I also experienced this problem yesterday and I just solved. Besides ensuring quantum-openvswitch-agent processes are all up (except the controller node), there is a typo in the network node in basic install doc: http://docs.openstack.org/folsom/basic-install/co

Re: [Openstack] Rebooted, now can't ping my guest

On Wed, Feb 27, 2013 at 7:11 PM, Chuan-Heng Hsiao wrote: > Hi Aaron and The King in Yellow, > > I also experienced this problem yesterday and I just solved. > > Besides ensuring quantum-openvswitch-agent processes are all up > (except the controller node), > there is a typo in the network node in

[Openstack] [OpenStack] Memory use in Controller and Compute nodes

Hi, I have a 3 node Folsom with Quantum setup. One is a controller node, one is a quantum networking node and the other is a KVM compute node. I see that on the Controller and Compute nodes, the memory usage is very high, based on the free command output. I have about 8gb RAM in the controller no

[Openstack] [OpenStack] Back porting the floating ip related changes to Folsom

Hi, We know that in Folsom Horizon, though there is interface for Floating ip association/disassociation, it doesnt work due to missing integration in Nova. But in the Grizzly, based on the release notes, this seems to have been implemented. Can this feature can be back ported to Folsom? has anybo

Re: [Openstack] [OpenStack] Memory use in Controller and Compute nodes

Never mind, Looks like I should be looking at this line which gives the correct usage which is more or less what I expect. -/+ buffers/cache: 2009 30163 Regards, Balu On Thu, Feb 28, 2013 at 10:18 AM, Balamurugan V G wrote: > Hi, > > I have a 3 node Folsom with Quantum setup. One is

Re: [Openstack] Rebooted, now can't ping my guest

Hi Aaron, I am very sorry that I made the conclusion too early because of not having good understanding of everything, and it is with high probability that I may made wrong conclusion. However, based on my hypothesis (and my few experiments.) The gateway setting is supposed to be corresponded to

Re: [Openstack] Rebooted, now can't ping my guest

Hi Hsiao, You are absolutely correct! If 192.168.0.254 is set as the gateway traffic will not be routed correctly. I also believe there is another bug as the ip addresses are being placed on the ethX interfaces and not bridge interfaces. I'll create a patch fixing these issues tomorrow morning. T

[Openstack] [Heat&Quantum] Quantum Template ROLLBACK_FAILED Error

I have heat and quantum in my devstack, just like: ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng ENABLED_SERVICES+=,quantum,q-svc,q-agt,q-dhcp,q-l3,q-meta Then I restart my compute, ./rejoin-stack.sh All Service OK. Then I run some thing like: heat stack-create -f /opt/stack/heat/templat