Re: [Openstack-operators] [ops][tags][packaging] [tc] ops:packaging tag - a little common sense, please

2015-06-10 Thread Britt Houser (bhouser)
+1 the entire brainstorm session on what they should be called besides tags is rather demeaning. There is obvious disagreement between what the TC wants to implement and what the ops folks want to implement. Discussions that stoop to this level increase the divide instead of shrinking it. Ple

Re: [Openstack-operators] Dual stacking in Neutron and Nova

2015-05-08 Thread Britt Houser (bhouser)
In the mean time, here is a blog post which covers it as well: http://www.debug-all.com/?p=52 Thx, britt On 5/8/15, 5:39 AM, "Sean M. Collins" wrote: >On Thu, May 07, 2015 at 11:04:01AM EDT, Mike Spreitzer wrote: >> I am told that dual stacking is supported for compute instances. What >> doe

Re: [Openstack-operators] Problem creating volumes from images with ceph storage

2015-02-12 Thread Britt Houser (bhouser)
What distribution is this? If RedHat based, try turning selinux to permissive and see if it works. Thx, britt From: Pedro Sousa mailto:pgso...@gmail.com>> Date: Thursday, February 12, 2015 at 12:07 PM To: "OpenStack-operators@lists.openstack.org"

Re: [Openstack-operators] Neutron DVR HA

2014-12-23 Thread Britt Houser (bhouser)
Instance(VR_1) ignoring received advertisment... Any hint? Thanks On Tue, Dec 23, 2014 at 3:17 PM, Britt Houser (bhouser) mailto:bhou...@cisco.com>> wrote: Currently HA and DVR are mutually exclusive features. From: Pedro Sousa mailto:pgso...@gmail.com>> Date: Tuesday, Dec

Re: [Openstack-operators] Neutron DVR HA

2014-12-23 Thread Britt Houser (bhouser)
Currently HA and DVR are mutually exclusive features. From: Pedro Sousa mailto:pgso...@gmail.com>> Date: Tuesday, December 23, 2014 at 9:42 AM To: "OpenStack-operators@lists.openstack.org" mailto:OpenStack-operators@lists.openstack.org>> Subject:

Re: [Openstack-operators] [openstack-operators] [large deployments] [neutron[ [rfc] Floating IP idea solicitation and collaboration

2014-12-04 Thread Britt Houser (bhouser)
I think LISP could probably be another way to skin the cat: http://lisp.cisco.com/lisp_over.html Has anyone explored using LISP with Neutron? Thx, britt From: Ryan Clevenger mailto:ryan.cleven...@rackspace.com>> Date: Thursday, December 4, 2014 at 10:35 AM To: "openstack-operators@lists.opens

Re: [Openstack-operators] Need help to create external network

2014-11-26 Thread Britt Houser (bhouser)
p to create external network Thanks Britt. After adding external network to router, openstack shows the router gateway is down. Have you faced this issues? On Tue, Nov 25, 2014 at 3:00 AM, Britt Houser (bhouser) mailto:bhou...@cisco.com>> wrote: The external network for your current OpenSt

Re: [Openstack-operators] Need help to create external network

2014-11-24 Thread Britt Houser (bhouser)
The external network for your current OpenStack setup is the 192.168.122.X network. Thx, britt From: Geo Varghese Date: Monday, November 24, 2014 at 3:17 PM To: "openstack-operators@lists.openstack.org" , "openst...@lists.openstack.org" Subject: [Openstack-operators] Need help to create ext

Re: [Openstack-operators] While adding external bridge connection lost to the network node

2014-11-24 Thread Britt Houser (bhouser)
"qvo887bf763-8d" Port br-int Interface br-int type: internal Port "int-br-eth1" Interface "int-br-eth1" Port "tapa72fb9d6-4a" tag: 2 Interface "tapa72fb9d6-4a" ty

Re: [Openstack-operators] While adding external bridge connection lost to the network node

2014-11-24 Thread Britt Houser (bhouser)
d after this change ifdown eth0 Show error in following line in /etc/network/interfaces iface br-ex inet static Thanks again for your support. On Fri, Nov 21, 2014 at 6:05 PM, Britt Houser (bhouser) mailto:bhou...@cisco.com>> wrote: The br-ex config looks right, but you don't wan

Re: [Openstack-operators] While adding external bridge connection lost to the network node

2014-11-21 Thread Britt Houser (bhouser)
to br-ex iface br-ex inet static address 192.168.122.54 netmask 255.255.255.0 gateway 192.168.122.1 dns-nameservers 8.8.8.8 8.8.4.4 == On Fri, Nov 21, 2014 at 5:48 PM, Britt Houser (bhouser) wrote: Correct. You

Re: [Openstack-operators] While adding external bridge connection lost to the network node

2014-11-21 Thread Britt Houser (bhouser)
Same eth0 i have used to add br-ex, you mean thats the issue right? On Fri, Nov 21, 2014 at 5:31 PM, Britt Houser (bhouser) mailto:bhou...@cisco.com>> wrote: Was the interface you added to br-ex the same interface to which you connected to the box? If so, this is expe

Re: [Openstack-operators] While adding external bridge connection lost to the network node

2014-11-21 Thread Britt Houser (bhouser)
Was the interface you added to br-ex the same interface to which you connected to the box? If so, this is expected. When you add an interface to the bridge you lose IP connectivity to that interface. The IP address which which was assigned to the interface now needs to be assigned to the br-e

Re: [Openstack-operators] Proposal for an 'Operations' project

2014-11-09 Thread Britt Houser (bhouser)
I would wager to say that all operators also develop on OpenStack to some degree. You have to at this point in the maturity of OpenStack. They may not all be fixing bugs upstream, but they are certainly getting their hands dirty with the code. So I don't think there is group of people that are p

Re: [Openstack-operators] database hoarding

2014-10-31 Thread Britt Houser (bhouser)
That would imply some extensible plugin type architecture, b/c "all projects" changes over time and from setup to setup. So each project would define its own cleanup routines, but those routines could be called using a common set of parameters from a single tool. Thx, britt On 10/31/14, 8:19 AM,

[Openstack-operators] segmentation of management and data plane

2014-09-12 Thread Britt Houser (bhouser)
Hey everyone - we've been doing some OpenStack deployments on different datacenter architectures in our lab. Many of the architectures we work with divide the management plane from the data plane by VRF. I.e. there is no routing between a tenant VM traffic and the management interfaces of the dat