[Openstack-operators] [telecom-nfv] Meeting #12 tomorrow!

2016-11-01 Thread Curtis 
Hi,

Meeting #12, the first after the summit sessions, will be tomorrow at
15:00 UTC in #openstack-meeting-4.

Hope to see you there as we will review some project ideas that we
listed during the summit session. :)

Thanks,
Curtis.

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [neutron] Operator feedback for Neutron clarifications from Barcelona

2016-11-01 Thread Ihar Hrachyshka 

Clayton O'Neill  wrote:


I was the person with issues with 10's of l3-agents not working
properly on Liberty.  With about 100 l3-agents we had issues with them
just falling over without anything going on.  We moved to 20 l3-agents
and with that config we've had good luck unless you restart all of
them at the same time.  My understanding is that in Liberty there is a
single thread per neutrons-server (we run 3) that handles agent
traffic and that this was supposed to be fixed in Mitaka and newer,
but I haven't seen that confirmed.


The patch that implemented separate workers for agent state reports is:  
https://review.openstack.org/#/c/233605/ and was indeed included in Mitaka+.


Ihar

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large deployments] Openstack Large deployment using DVR

2016-11-01 Thread Satyanarayana Patibandla 
Thanks for your inputs. We will consider the below details while designing
our network. Our second option is to use L3 Agents with HA for routing.In
this approach, Currently most of the large openstack deployers are using
their own customized code for network segments. But we are planning to
segment/cluster/group our network nodes by assigning network node to
availability zones.  Did anyone used this approach in large /medium scale
deployments. Please let us know if you have any  suggestions or inputs on
this approach.

On Tue, Nov 1, 2016 at 7:51 PM, Kosnik, Lubosz 
wrote:

> Please just remember that today many high level features like LBaaSv2 +
> Octavia is not working [1] when you’re using DVR + L3/HA.
> Designing that cloud you need to remember that for today there is a huge
> chance that you will not be able to use anything except base L2/L3
> connectivity from networking perspective.
>
> [1] https://bugs.launchpad.net/neutron/+bug/1583694
>
> Regards.
> Lubosz Kosnik
> Cloud Software Engineer OSIC
> lubosz.kos...@intel.com
>
> On Nov 1, 2016, at 8:39 AM, Satyanarayana Patibandla <
> satya.patiban...@gmail.com> wrote:
>
> Thanks for your response. We are assuming that if we use DVR with L3 HA
> there is no need of network segment/cluster. Could you please share your
> thoughts on this.
>
> On Tue, Nov 1, 2016 at 6:48 PM, Clayton O'Neill 
> wrote:
>
>> On Tue, Nov 1, 2016 at 7:19 AM, Satyanarayana Patibandla
>>  wrote:
>> > We are planning for a new Openstack large deployment ( Around 25 K
>> VMs). For
>> > external routing we want to use DVR for instances with floating IP and
>> > Network node L3 agent for instances with private IP. Our deployment is
>> DVR
>> > with L3 HA.It seems still many people not yet started using DVR in
>> > production for large deployments. Did anyone use DVR in their
>> Large/Medium
>> > production deployment. If you can share your experiences that will be
>> > helpful to us and that will save most of our time.
>>
>> I've asked this question in operator sessions at the Summits and at
>> the NYC operators mid-cycle with not much response.  In the Neutron
>> feedback session last week, there was one person that said he was
>> running DVR, but that it had architectural issues with IPv6.  I got
>> the impression that his environment was much smaller than what you're
>> considering.
>>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Neutron fails to notify nova on events network-vif-plugged

2016-11-01 Thread Davíð Örn Jóhannsson 
I’m trying to use the puppet modules for liberty, I’ve had some issues there 
where the modules do not seem to exactly represent the configuration intended 
for liberty

From: Matt Kassawara
Date: Tuesday 1 November 2016 at 15:40
To: David Orn Johannsson
Cc: 
"openstack-operators@lists.openstack.org"
Subject: Re: [Openstack-operators] Neutron fails to notify nova on events 
network-vif-plugged

You are mixing a lot of current and defunct configuration options. I recommend 
removing the defunct options and then comparing your configuration files with 
the installation guide [1].

[1] http://docs.openstack.org/liberty/install-guide-ubuntu/

On Tue, Nov 1, 2016 at 7:05 AM, Davíð Örn Jóhannsson 
> wrote:
I’m working on setting up a OpenStack Liberty development env on Ubuntu 14.04. 
At the present I have 3 nodes, Controller, Network and Compute. I am up to the 
place where I’m trying to spin up an instance where neutron-server seems to 
fail to notify nova because of an authentication error against keystone , I’ve 
been struggling for some time to figure out the cause of this and was hoping 
that some could lend me more experienced eyes

Controller node /etc/neutron/neutron.conf 
http://paste.openstack.org/show/587547/
Openstack endpoint list http://paste.openstack.org/show/587548/

2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.session [-] RESP: [300] 
Content-Length: 635 Vary: X-Auth-Token Connection: keep-alive Date: Tue, 01 Nov 
2016 12:42:04 GMT Content-Type: application/json X-Distribution: Ubuntu
RESP BODY: {"versions": {"values": [{"status": "stable", "updated": 
"2015-03-30T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v3+json"}], "id": "v3.4", "links": 
[{"href": "http://controller-01:35357/v3/;, "rel": "self"}]}, {"status": 
"stable", "updated": "2014-04-17T00:00:00Z", "media-types": [{"base": 
"application/json", "type": "application/vnd.openstack.identity-v2.0+json"}], 
"id": "v2.0", "links": [{"href": "http://controller-01:35357/v2.0/;, "rel": 
"self"}, {"href": "http://docs.openstack.org/;, "type": "text/html", "rel": 
"describedby"}]}]}}
 _http_log_response 
/usr/lib/python2.7/dist-packages/keystoneclient/session.py:215
2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.auth.identity.v3.base [-] 
Making authentication request to http://controller-01:35357/v3/auth/tokens 
get_auth_ref 
/usr/lib/python2.7/dist-packages/keystoneclient/auth/identity/v3/base.py:188
2016-11-01 12:42:04.091 15888 DEBUG keystoneclient.session [-] Request returned 
failure status: 401 request 
/usr/lib/python2.7/dist-packages/keystoneclient/session.py:400
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova [-] Failed to notify 
nova on events: [{'status': 'completed', 'tag': 
u'bf092fd0-51ba-4fbf-8d3d-9c3004b3811f', 'name': 'network-vif-plugged', 
'server_uuid': u'24616ae2-a6e4-4843-ade6-357a9ce80bc0'}]
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova Traceback (most 
recent call last):
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/neutron/notifiers/nova.py", line 248, in 
send_events
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova batched_events)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/novaclient/v2/contrib/server_external_events.py",
 line 39, in create
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return_raw=True)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/novaclient/base.py", line 169, in _create
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova _resp, body = 
self.api.client.post(url, body=body)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 176, in post
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return 
self.request(url, 'POST', **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/novaclient/client.py", line 91, in request
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 206, in 
request
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova resp = 
super(LegacyJsonAdapter, self).request(*args, **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 95, in 
request
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return 
self.session.request(url, method, **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/utils.py", line 337, in inner

Re: [Openstack-operators] Neutron fails to notify nova on events network-vif-plugged

2016-11-01 Thread Matt Kassawara 
You are mixing a lot of current and defunct configuration options. I
recommend removing the defunct options and then comparing your
configuration files with the installation guide [1].

[1] http://docs.openstack.org/liberty/install-guide-ubuntu/

On Tue, Nov 1, 2016 at 7:05 AM, Davíð Örn Jóhannsson 
wrote:

> I’m working on setting up a OpenStack Liberty development env on Ubuntu
> 14.04. At the present I have 3 nodes, Controller, Network and Compute. I am
> up to the place where I’m trying to spin up an instance where
> neutron-server seems to fail to notify nova because of an authentication
> error against keystone , I’ve been struggling for some time to figure out
> the cause of this and was hoping that some could lend me more experienced
> eyes
>
> Controller node /etc/neutron/neutron.conf http://paste.openstack.org/show/
> 587547/
> Openstack endpoint list http://paste.openstack.org/show/587548/
>
> 2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.session [-] RESP: [300]
> Content-Length: 635 Vary: X-Auth-Token Connection: keep-alive Date: Tue, 01
> Nov 2016 12:42:04 GMT Content-Type: application/json X-Distribution: Ubuntu
> RESP BODY: {"versions": {"values": [{"status": "stable", "updated":
> "2015-03-30T00:00:00Z", "media-types": [{"base": "application/json",
> "type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.4",
> "links": [{"href": "http://controller-01:35357/v3/;, "rel": "self"}]},
> {"status": "stable", "updated": "2014-04-17T00:00:00Z", "media-types":
> [{"base": "application/json", "type": 
> "application/vnd.openstack.identity-v2.0+json"}],
> "id": "v2.0", "links": [{"href": "http://controller-01:35357/v2.0/;,
> "rel": "self"}, {"href": "http://docs.openstack.org/;, "type":
> "text/html", "rel": "describedby"}]}]}}
>  _http_log_response /usr/lib/python2.7/dist-packages/keystoneclient/
> session.py:215
> 2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.auth.identity.v3.base
> [-] Making authentication request to http://controller-01:35357/v3/
> auth/tokens get_auth_ref /usr/lib/python2.7/dist-
> packages/keystoneclient/auth/identity/v3/base.py:188
> 2016-11-01 12:42:04.091 15888 DEBUG keystoneclient.session [-] Request
> returned failure status: 401 request /usr/lib/python2.7/dist-
> packages/keystoneclient/session.py:400
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova [-] Failed to
> notify nova on events: [{'status': 'completed', 'tag':
> u'bf092fd0-51ba-4fbf-8d3d-9c3004b3811f', 'name': 'network-vif-plugged',
> 'server_uuid': u'24616ae2-a6e4-4843-ade6-357a9ce80bc0'}]
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova Traceback (most
> recent call last):
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/neutron/notifiers/nova.py", line 248,
> in send_events
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova
> batched_events)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/novaclient/v2/contrib/server_external_events.py",
> line 39, in create
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova
> return_raw=True)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/novaclient/base.py", line 169, in
> _create
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova _resp, body
> = self.api.client.post(url, body=body)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 176,
> in post
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return
> self.request(url, 'POST', **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 91, in
> request
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 206,
> in request
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova resp =
> super(LegacyJsonAdapter, self).request(*args, **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 95, in
> request
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return
> self.session.request(url, method, **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/utils.py", line 337, in
> inner
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return
> func(*args, **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/session.py", line 304,
> in request
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova
> auth_headers = self.get_auth_headers(auth)
>

[Openstack-operators] [neutron] Operator feedback for Neutron clarifications from Barcelona

2016-11-01 Thread Leon Zachery (lzachery) 
Hi:

At the neutron operator feedback session during the operator summit [1] and the 
operator feedback session during the design summit [2], 2 issues were raised on 
which
we'd like to get some further clarification.

The first issue was the issue raised on the scale issues with thousands of 
agents, from [1] above:

  *   Issues with lots of agents (~1000) and rabbitMQ

  *   We've had problems on liberty with 10's of l3-agents, supposed to be 
better on mitaka+

  *   Related to this bug: https://bugs.launchpad.net/mos/+bug/1494416

The second issue is the hardware router integration issue, from [2] above:

 *   Enabling end users to create their own networks serviced by a hardware 
router

  *   Currently using provider networks, but that loses self service


[1] https://etherpad.openstack.org/p/BCN-ops-neutron-pain-points
[2] https://etherpad.openstack.org/p/ocata-neutron-end-user-operator-feedback

Feel free to unicast or broadcast a response and I will follow up with you.

Thanks,
Leon


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] 2017 Openstack Operators Mid-Cycle Meetups - venue selection etherpads

2016-11-01 Thread Erik McCormick 
On Oct 31, 2016 1:13 PM, "Jesse Keating"  wrote:
>
> This has been my experience as well. I purposefully attend the project
fishbowl sessions and often the project mid cycles to be able to provide
real time operator feedback as future plans are discussed and
retrospectives from the previous release are held.

Right but the point is thise fishbowl won't be held at the PTG as I
understand it. It's more like Friday at the Design Summit. Those fishbowl
type sessions are meant to occur at the Forum.

>
> Given a choice between attending either the Ops mid cycle or the PTG, I
see far more value in the PTG, which will be held at a very similar time.
> -jlk
>
>
Maybe you should ask over in the dev list and see if that would be at all
appreciated or useful. I'd be interested in their perspective.

-Erik
>>
>> - Original message -
>> From: Matthias Runge 
>> To: openstack-operators@lists.openstack.org
>> Cc:
>> Subject: Re: [Openstack-operators] 2017 Openstack Operators Mid-Cycle
Meetups - venue selection etherpads
>> Date: Thu, Oct 27, 2016 5:33 AM
>>
>> On 27/10/16 11:08, Erik McCormick wrote:
>> > The PTG is for devs to get together and get real work done. We would be
>> > a distraction from that goal. They will also be attending the forum
>> > which will run with the summits and will be able to spend more time in
>> > groups with ops for requirements gathering and such.
>> >
>> > -Erik
>> >
>> >
>> > On Oct 27, 2016 11:05 AM, "Jesse Keating" > > > wrote:
>> >
>> > I may have missed something, but why aren't we meeting at the
>> > Project Technical Gathering, which is at the end of February in
Atlanta?
>>
>> From my experience with OpenStack, feedback from operators have been
>> invaluable.
>>
>> You can easily run things in devstack (or all-in-one deployments), but
>> this is completely different from running in scale. Operators do tell
>> you, were the pain-points are. Having a dedicated gathering without
>> involving actual operators/users is not that useful IMO.
>>
>> Matthias
>> --
>> Matthias Runge 
>>
>> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
>> Commercial register: Amtsgericht Muenchen, HRB 153243,
>> Managing Directors: Charles Cachera, Michael Cunningham,
>> Michael O'Neill, Eric Shander
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large deployments] Openstack Large deployment using DVR

2016-11-01 Thread Kosnik, Lubosz 
Please just remember that today many high level features like LBaaSv2 + Octavia 
is not working [1] when you’re using DVR + L3/HA.
Designing that cloud you need to remember that for today there is a huge chance 
that you will not be able to use anything except base L2/L3 connectivity from 
networking perspective.

[1] https://bugs.launchpad.net/neutron/+bug/1583694

Regards.
Lubosz Kosnik
Cloud Software Engineer OSIC
lubosz.kos...@intel.com

On Nov 1, 2016, at 8:39 AM, Satyanarayana Patibandla 
> wrote:

Thanks for your response. We are assuming that if we use DVR with L3 HA there 
is no need of network segment/cluster. Could you please share your thoughts on 
this.

On Tue, Nov 1, 2016 at 6:48 PM, Clayton O'Neill 
> wrote:
On Tue, Nov 1, 2016 at 7:19 AM, Satyanarayana Patibandla
> wrote:
> We are planning for a new Openstack large deployment ( Around 25 K VMs). For
> external routing we want to use DVR for instances with floating IP and
> Network node L3 agent for instances with private IP. Our deployment is DVR
> with L3 HA.It seems still many people not yet started using DVR in
> production for large deployments. Did anyone use DVR in their Large/Medium
> production deployment. If you can share your experiences that will be
> helpful to us and that will save most of our time.

I've asked this question in operator sessions at the Summits and at
the NYC operators mid-cycle with not much response.  In the Neutron
feedback session last week, there was one person that said he was
running DVR, but that it had architectural issues with IPv6.  I got
the impression that his environment was much smaller than what you're
considering.

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large deployments] Openstack Large deployment using DVR

2016-11-01 Thread Satyanarayana Patibandla 
Thanks for your response. We are assuming that if we use DVR with L3 HA
there is no need of network segment/cluster. Could you please share your
thoughts on this.

On Tue, Nov 1, 2016 at 6:48 PM, Clayton O'Neill  wrote:

> On Tue, Nov 1, 2016 at 7:19 AM, Satyanarayana Patibandla
>  wrote:
> > We are planning for a new Openstack large deployment ( Around 25 K VMs).
> For
> > external routing we want to use DVR for instances with floating IP and
> > Network node L3 agent for instances with private IP. Our deployment is
> DVR
> > with L3 HA.It seems still many people not yet started using DVR in
> > production for large deployments. Did anyone use DVR in their
> Large/Medium
> > production deployment. If you can share your experiences that will be
> > helpful to us and that will save most of our time.
>
> I've asked this question in operator sessions at the Summits and at
> the NYC operators mid-cycle with not much response.  In the Neutron
> feedback session last week, there was one person that said he was
> running DVR, but that it had architectural issues with IPv6.  I got
> the impression that his environment was much smaller than what you're
> considering.
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large deployments] Openstack Large deployment using DVR

2016-11-01 Thread Clayton O'Neill 
On Tue, Nov 1, 2016 at 7:19 AM, Satyanarayana Patibandla
 wrote:
> We are planning for a new Openstack large deployment ( Around 25 K VMs). For
> external routing we want to use DVR for instances with floating IP and
> Network node L3 agent for instances with private IP. Our deployment is DVR
> with L3 HA.It seems still many people not yet started using DVR in
> production for large deployments. Did anyone use DVR in their Large/Medium
> production deployment. If you can share your experiences that will be
> helpful to us and that will save most of our time.

I've asked this question in operator sessions at the Summits and at
the NYC operators mid-cycle with not much response.  In the Neutron
feedback session last week, there was one person that said he was
running DVR, but that it had architectural issues with IPv6.  I got
the impression that his environment was much smaller than what you're
considering.

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Neutron fails to notify nova on events network-vif-plugged

2016-11-01 Thread Davíð Örn Jóhannsson 
I’m working on setting up a OpenStack Liberty development env on Ubuntu 14.04. 
At the present I have 3 nodes, Controller, Network and Compute. I am up to the 
place where I’m trying to spin up an instance where neutron-server seems to 
fail to notify nova because of an authentication error against keystone , I’ve 
been struggling for some time to figure out the cause of this and was hoping 
that some could lend me more experienced eyes

Controller node /etc/neutron/neutron.conf 
http://paste.openstack.org/show/587547/
Openstack endpoint list http://paste.openstack.org/show/587548/

2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.session [-] RESP: [300] 
Content-Length: 635 Vary: X-Auth-Token Connection: keep-alive Date: Tue, 01 Nov 
2016 12:42:04 GMT Content-Type: application/json X-Distribution: Ubuntu
RESP BODY: {"versions": {"values": [{"status": "stable", "updated": 
"2015-03-30T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v3+json"}], "id": "v3.4", "links": 
[{"href": "http://controller-01:35357/v3/;, "rel": "self"}]}, {"status": 
"stable", "updated": "2014-04-17T00:00:00Z", "media-types": [{"base": 
"application/json", "type": "application/vnd.openstack.identity-v2.0+json"}], 
"id": "v2.0", "links": [{"href": "http://controller-01:35357/v2.0/;, "rel": 
"self"}, {"href": "http://docs.openstack.org/;, "type": "text/html", "rel": 
"describedby"}]}]}}
 _http_log_response 
/usr/lib/python2.7/dist-packages/keystoneclient/session.py:215
2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.auth.identity.v3.base [-] 
Making authentication request to http://controller-01:35357/v3/auth/tokens 
get_auth_ref 
/usr/lib/python2.7/dist-packages/keystoneclient/auth/identity/v3/base.py:188
2016-11-01 12:42:04.091 15888 DEBUG keystoneclient.session [-] Request returned 
failure status: 401 request 
/usr/lib/python2.7/dist-packages/keystoneclient/session.py:400
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova [-] Failed to notify 
nova on events: [{'status': 'completed', 'tag': 
u'bf092fd0-51ba-4fbf-8d3d-9c3004b3811f', 'name': 'network-vif-plugged', 
'server_uuid': u'24616ae2-a6e4-4843-ade6-357a9ce80bc0'}]
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova Traceback (most 
recent call last):
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/neutron/notifiers/nova.py", line 248, in 
send_events
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova batched_events)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/novaclient/v2/contrib/server_external_events.py",
 line 39, in create
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return_raw=True)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/novaclient/base.py", line 169, in _create
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova _resp, body = 
self.api.client.post(url, body=body)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 176, in post
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return 
self.request(url, 'POST', **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/novaclient/client.py", line 91, in request
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 206, in 
request
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova resp = 
super(LegacyJsonAdapter, self).request(*args, **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 95, in 
request
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return 
self.session.request(url, method, **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/utils.py", line 337, in inner
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return 
func(*args, **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/session.py", line 304, in 
request
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova auth_headers = 
self.get_auth_headers(auth)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/session.py", line 617, in 
get_auth_headers
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return 
auth.get_headers(self, **kwargs)
2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/auth/base.py", line 142, in 
get_headers
2016-11-01 12:42:04.091 15888

[Openstack-operators] [scientific][scientific-wg] Reminder: IRC meeting Tuesday 1st November 2100 UTC

2016-11-01 Thread Stig Telfer 
Hi All - 

We have a Scientific WG IRC meeting today at 2100 UTC on channel 
#openstack-meeting

The agenda is available here[1] and full IRC meeting details are here[2].

We’d like to follow up on the events at Barcelona, and plan activity areas for 
the Ocata design cycle.

If anyone would like to add an item for discussion on the agenda, it is also 
available in an etherpad[3].

Best wishes,
Stig

[1] 
https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_November_1st_2016
 

[2] http://eavesdrop.openstack.org/#Scientific_Working_Group 

[3] https://etherpad.openstack.org/p/Scientific-WG-next-meeting-agenda 
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Quota exceeded for resource router

2016-11-01 Thread Davíð Örn Jóhannsson 
I think I found it, the horizon error message couldn’t be clearer :)

2016-11-01 11:09:22.548 5894 INFO neutron.api.v2.resource 
[req-1f7cff32-defc-4c81-9021-8d58cc151d2b ebc40bf0b0e24114ad1c2d3dfa42e062 
90ccab0d2336493bb38d0f86969eb632 - - -] create failed (client error): No more 
IP addresses available on network 29eea5ab-3891-478d-a76f-04f92d9e1f52.

From: Tobias Schön
Date: Tuesday 1 November 2016 at 09:51
To: David Orn Johannsson, 
"openstack-operators@lists.openstack.org"
Subject: SV: Quota exceeded for resource router

Hi,

What does your log say?


MVH/Best regards,
Tobias Schön
Sysadmin/drifttekniker Area X
[cid:image001.png@01CEED18.59C12030]

Kvarnkroken 7, 805 92  GÄVLE
Box 6027, 800 06 GÄVLE
www.areax.se
www.fiberdata.se

Överväg miljöpåverkan innan du skriver ut detta e-postmeddelande

This communication and any attachment(s) to it are only for the use of the 
intended recipient. The information in it may be confidential and subject to 
legal privilege. Reading or dissemination of it by anyone other than the 
intended recipient is strictly prohibited. If you are not the intended 
recipient please contact the sender by reply e-mail and delete all copies of 
this message and any attachments from any drives or storage media and destroy 
any printouts.

Från: Davíð Örn Jóhannsson [mailto:davi...@siminn.is]
Skickat: den 1 november 2016 10:33
Till: 
openstack-operators@lists.openstack.org
Ämne: [Openstack-operators] Quota exceeded for resource router

Ubuntu 14.04
Liberty
Neutron network

I’m trying add a router to a new project that has no configured router but I 
seem some how to manage to hit a "Quota exceeded for resource router” in 
horizon. I even tried to set the quota to 500.

+-+---+
| Field   | Value |
+-+---+
| floatingip  | 50|
| health_monitor  | -1|
| member  | -1|
| network | 10|
| pool| 10|
| port| 50|
| rbac_policy | 10|
| router  | 500   |
| security_group  | 10|
| security_group_rule | 100   |
| subnet  | 10|
| subnetpool  | -1|
| vip | 10|
+-+---+

Any ideas to what could be the cause of this?
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Quota exceeded for resource router

2016-11-01 Thread Tobias Schön 
Hi,

What does your log say?


MVH/Best regards,
Tobias Schön
Sysadmin/drifttekniker Area X
[cid:image001.png@01CEED18.59C12030]

Kvarnkroken 7, 805 92  GÄVLE
Box 6027, 800 06 GÄVLE
www.areax.se
www.fiberdata.se

Överväg miljöpåverkan innan du skriver ut detta e-postmeddelande

This communication and any attachment(s) to it are only for the use of the 
intended recipient. The information in it may be confidential and subject to 
legal privilege. Reading or dissemination of it by anyone other than the 
intended recipient is strictly prohibited. If you are not the intended 
recipient please contact the sender by reply e-mail and delete all copies of 
this message and any attachments from any drives or storage media and destroy 
any printouts.

Från: Davíð Örn Jóhannsson [mailto:davi...@siminn.is]
Skickat: den 1 november 2016 10:33
Till: openstack-operators@lists.openstack.org
Ämne: [Openstack-operators] Quota exceeded for resource router

Ubuntu 14.04
Liberty
Neutron network

I’m trying add a router to a new project that has no configured router but I 
seem some how to manage to hit a "Quota exceeded for resource router” in 
horizon. I even tried to set the quota to 500.

+-+---+
| Field   | Value |
+-+---+
| floatingip  | 50|
| health_monitor  | -1|
| member  | -1|
| network | 10|
| pool| 10|
| port| 50|
| rbac_policy | 10|
| router  | 500   |
| security_group  | 10|
| security_group_rule | 100   |
| subnet  | 10|
| subnetpool  | -1|
| vip | 10|
+-+---+

Any ideas to what could be the cause of this?
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Quota exceeded for resource router

2016-11-01 Thread Davíð Örn Jóhannsson 
Ubuntu 14.04
Liberty
Neutron network

I’m trying add a router to a new project that has no configured router but I 
seem some how to manage to hit a "Quota exceeded for resource router” in 
horizon. I even tried to set the quota to 500.

+-+---+
| Field   | Value |
+-+---+
| floatingip  | 50|
| health_monitor  | -1|
| member  | -1|
| network | 10|
| pool| 10|
| port| 50|
| rbac_policy | 10|
| router  | 500   |
| security_group  | 10|
| security_group_rule | 100   |
| subnet  | 10|
| subnetpool  | -1|
| vip | 10|
+-+---+

Any ideas to what could be the cause of this?
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] 2017 Openstack Operators Mid-Cycle Meetups - venue selection etherpads

2016-11-01 Thread Thierry Carrez 
Jesse Keating wrote:
> This has been my experience as well. I purposefully attend the project
> fishbowl sessions and often the project mid cycles to be able to provide
> real time operator feedback as future plans are discussed and
> retrospectives from the previous release are held.

Note that Fishbowl sessions, discussion of future plans and
retrospectives from the previous release will be held at the Forum.

The PTG will be workroom sessions (without a preset schedule) and
focused on immediate implementation plans. Operators are welcome to join
(especially if they feel part of a specific upstream project team and
used to attend that team midcycles) but should probably prioritize
attending the Summit (Forum) and ops midcycle(s) events.

> Given a choice between attending either the Ops mid cycle or the PTG, I
> see far more value in the PTG, which will be held at a very similar time.

I doubt there will be more value for you in the PTG, but to open options
for those who want to attend everything, I guess it wouldn't hurt to
place them on separate weeks.

-- 
Thierry Carrez (ttx)

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [Large deployments] Openstack Large deployment using DVR

2016-11-01 Thread Satyanarayana Patibandla 
Hi All,

We are planning for a new Openstack large deployment ( Around 25 K VMs).
For external routing we want to use DVR for instances with floating IP and
Network node L3 agent for instances with private IP. Our deployment is DVR
with L3 HA.It seems still many people not yet started using DVR in
production for large deployments. Did anyone use DVR in their Large/Medium
production deployment. If you can share your experiences that will be
helpful to us and that will save most of our time.

Thanks,
Satya.P
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators