[Openstack-operators] Reminder: User Committee @ 1800 UTC
Hi everyone, UC meeting today in #openstack-uc Agenda: https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] swift question
Hi all. I wonder if i can sync a directory on a server to the obj store (swift). What I do now is just a backup but I d like to implement a sort of file rotate locally and on the obj store. Any idea? -- *Alfredo* ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-ansible] How to manage system upgrades ?
On 7/27/2018 3:34 AM, Gilles Mocellin wrote: - for compute nodes : disable compute node and live-evacuate instances... To be clear, what do you mean exactly by "live-evacuate"? I assume you mean live migration of all instances off each (disabled) compute node *before* you upgrade it. I wanted to ask because "evacuate" as a server operation is something else entirely (it's rebuild on another host which is definitely disruptive to the workload on that server). http://www.danplanet.com/blog/2016/03/03/evacuate-in-nova-one-command-to-confuse-us-all/ -- Thanks, Matt ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] dashboard show only project after upgrading
Ignazio, Are your horizon instances in separate containers/VMS? If so, I'd highly recommend completely wiping them and rebuilding from scratch since horizon itself is stateless. I am not a fan of upgrades for reasons like this. If that's not possible, a purge of the horizon packages on your controller and a reinstallation should fix it. Chris On July 30, 2018 11:38:03 Ignazio Cassano wrote: Sorry, I sent a wrong image. The correct screenshot is attached here. Regards 2018-07-30 17:33 GMT+02:00 Ignazio Cassano : Hello everyone, I upgraded openstack centos 7 from ocata to pike ad command line work fine but dashboard does not show any menu on the left . I missed the following menus: Project Admin Identity You can find the image attached here. Could anyone help me ? Regards Ignazio ___ 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] dashboard show only project after upgrading
Hello Chris, I am not using containers yet. I wiil try to purge it. Many thanks. Ignazio Il Lun 30 Lug 2018 17:53 Chris Apsey ha scritto: > Ignazio, > > Are your horizon instances in separate containers/VMS? If so, I'd highly > recommend completely wiping them and rebuilding from scratch since horizon > itself is stateless. I am not a fan of upgrades for reasons like this. > > If that's not possible, a purge of the horizon packages on your controller > and a reinstallation should fix it. > > Chris > > On July 30, 2018 11:38:03 Ignazio Cassano > wrote: > >> Sorry, I sent a wrong image. >> The correct screenshot is attached here. >> Regards >> >> 2018-07-30 17:33 GMT+02:00 Ignazio Cassano : >> >>> Hello everyone, >>> I upgraded openstack centos 7 from ocata to pike ad command line work >>> fine >>> but dashboard does not show any menu on the left . >>> I missed the following menus: >>> >>> Project >>> Admin >>> Identity >>> >>> You can find the image attached here. >>> >>> Could anyone help me ? >>> Regards >>> Ignazio >>> >> >> ___ >> 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] swift question
Sure! python swiftclient's upload command has a --changed option: https://docs.openstack.org/python-swiftclient/latest/cli/index.html#swift-upload But you might be happier with something more sophisticated like rclone: https://rclone.org/ Nice thing about object storage is you can access it from anywhere via HTTP and PUT anything you want in there ;) -Clay On Mon, Jul 30, 2018 at 9:54 AM Alfredo De Luca wrote: > Hi all. > I wonder if i can sync a directory on a server to the obj store (swift). > What I do now is just a backup but I d like to implement a sort of file > rotate locally and on the obj store. > Any idea? > > > -- > *Alfredo* > > ___ > 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] [neutron] [neutron-dynamic-routing] bgp-dragent not sending BGP UPDATE messages
Hello,
I'm trying to get the neutron-bgp-dragent that is delivered by the
neutron-dynamic-routing project to work.
I've gotten it to open a BGP peer session without any issues but the no
BGP UPDATE messages seems to be sent from the
neutron-bgp-dragent daemon.
I'm having a BGP peer with a machine running FreeBSD 11 with OpenBGPD,
my goals is being able to announce IPv6 over IPv4 peers which should
work but I'm unsure
if python-ryu supports this.
[root@controller ~]# openstack bgp speaker show bgp-speaker-ipv6
+---+---+
| Field |
Value |
+---+---+
| advertise_floating_ip_host_routes |
False |
| advertise_tenant_networks |
True |
| id|
d22b30f2-50fe-49eb-9577-77cceb3fcc81 |
| ip_version|
6 |
| local_as |
64600 |
| name |
bgp-speaker-ipv6 |
| networks |
[u'fdcead67-8a12-42fe-a31d-8cb3a03d8ee0'] |
| peers |
[u'b42d808f-c2ef-41e7-93b5-859a51cf6a36'] |
| project_id|
050c556faa5944a8953126c867313770 |
| tenant_id |
050c556faa5944a8953126c867313770 |
+---+---+
[root@controller ~]# openstack bgp peer show
b42d808f-c2ef-41e7-93b5-859a51cf6a36
++--+
| Field | Value|
++--+
| auth_type | none |
| id | b42d808f-c2ef-41e7-93b5-859a51cf6a36 |
| name | bgp-peer-1|
| peer_ip| 172.20.x.y |
| project_id | 050c556faa5944a8953126c867313770 |
| remote_as | |
| tenant_id | 050c556faa5944a8953126c867313770 |
++--+
[root@controller ~]# openstack bgp speaker list advertised routes
bgp-speaker-ipv6
+++--+
| ID | Destination| Nexthop |
+++--+
|| ::0:1::/64 | :::f |
+++--+
2018-07-30 19:00:57.302 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver [-]
Initializing Ryu driver for BGP Speaker functionality.
2018-07-30 19:00:57.302 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver [-]
Initialized Ryu BGP Speaker driver interface with bgp_router_id=172.20.zz.yy
2018-07-30 19:00:57.351 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.bgp_dragent [-] BGP dynamic
routing agent started
2018-07-30 19:00:57.450 2143006 INFO bgpspeaker.api.base
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] API method
core.start called with args: {'router_id': '172.20.zz.yy',
'label_range': (100, 10), 'waiter': , 'bgp_server_port': 0, 'local_as': 64600,
'allow_local_as_in_count': 0, 'refresh_stalepath_time': 0, 'cluster_id':
None, 'local_pref': 100, 'refresh_max_eor_time': 0}
2018-07-30 19:00:57.455 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] Added BGP Speaker
for local_as=64600 with router_id= 172.20.zz.yy.
2018-07-30 19:00:57.456 2143006 INFO bgpspeaker.api.base
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] API method
neighbor.create called with args: {'connect_mode': 'active',
'cap_mbgp_evpn': False, 'remote_as': 35041, 'cap_mbgp_vpnv6': False,
'cap_mbgp_l2vpnfs': False, 'cap_four_octet_as_number': True,
'cap_mbgp_ipv6': False, 'is_next_hop_self': False, 'cap_mbgp_ipv4':
True, 'cap_mbgp_ipv4fs': False, 'is_route_reflector_client': False,
'cap_mbgp_ipv6fs': False, 'is_route_server_client': False,
'cap_enhanced_refresh': False, 'peer_next_hop': None, 'password': None,
'ip_address': u'172.20.x.y', 'cap_mbgp_vpnv4fs': False,
'cap_mbgp_vpnv4': False, 'cap_mbgp_vpnv6fs': False}
2018-07-30 19:00:57.456 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] Added BGP Peer
172.20.x.y for remote_as= to BGP Speaker running for local_as=64600.
2018-07-30 19:00:57.457 2143006 INFO bgpspeaker.api.base
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] API method
network.add called with args: {'prefix': u'::0:1::/64',
'next_hop': u'2a05:4545::f'}
2018-07-30 19:00:57.457 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] R
Re: [Openstack-operators] [neutron] [neutron-dynamic-routing] bgp-dragent not sending BGP UPDATE messages
So the real question is pretty much if Ryu supports MP-BGP and it does however
it seems that neutron-dynamic-routing
is disabling IPv6 if the peer IP is a IPv4 address :(
So the link below answers my own question [1]
[1]
https://github.com/openstack/neutron-dynamic-routing/blob/98d3cf24d6d7b5eca55ca19eb19bdd2e7b1975ec/neutron_dynamic_routing/services/bgp/agent/driver/ryu/driver.py#L131
From: Tobias Urdin
Sent: Monday, July 30, 2018 7:08 PM
To: openstack-operators@lists.openstack.org
Subject: [Openstack-operators] [neutron] [neutron-dynamic-routing] bgp-dragent
not sending BGP UPDATE messages
Hello,
I'm trying to get the neutron-bgp-dragent that is delivered by the
neutron-dynamic-routing project to work.
I've gotten it to open a BGP peer session without any issues but the no
BGP UPDATE messages seems to be sent from the
neutron-bgp-dragent daemon.
I'm having a BGP peer with a machine running FreeBSD 11 with OpenBGPD,
my goals is being able to announce IPv6 over IPv4 peers which should
work but I'm unsure
if python-ryu supports this.
[root@controller ~]# openstack bgp speaker show bgp-speaker-ipv6
+---+---+
| Field |
Value |
+---+---+
| advertise_floating_ip_host_routes |
False |
| advertise_tenant_networks |
True |
| id|
d22b30f2-50fe-49eb-9577-77cceb3fcc81 |
| ip_version|
6 |
| local_as |
64600 |
| name |
bgp-speaker-ipv6 |
| networks |
[u'fdcead67-8a12-42fe-a31d-8cb3a03d8ee0'] |
| peers |
[u'b42d808f-c2ef-41e7-93b5-859a51cf6a36'] |
| project_id|
050c556faa5944a8953126c867313770 |
| tenant_id |
050c556faa5944a8953126c867313770 |
+---+---+
[root@controller ~]# openstack bgp peer show
b42d808f-c2ef-41e7-93b5-859a51cf6a36
++--+
| Field | Value|
++--+
| auth_type | none |
| id | b42d808f-c2ef-41e7-93b5-859a51cf6a36 |
| name | bgp-peer-1|
| peer_ip| 172.20.x.y |
| project_id | 050c556faa5944a8953126c867313770 |
| remote_as | |
| tenant_id | 050c556faa5944a8953126c867313770 |
++--+
[root@controller ~]# openstack bgp speaker list advertised routes
bgp-speaker-ipv6
+++--+
| ID | Destination| Nexthop |
+++--+
|| ::0:1::/64 | :::f |
+++--+
2018-07-30 19:00:57.302 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver [-]
Initializing Ryu driver for BGP Speaker functionality.
2018-07-30 19:00:57.302 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver [-]
Initialized Ryu BGP Speaker driver interface with bgp_router_id=172.20.zz.yy
2018-07-30 19:00:57.351 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.bgp_dragent [-] BGP dynamic
routing agent started
2018-07-30 19:00:57.450 2143006 INFO bgpspeaker.api.base
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] API method
core.start called with args: {'router_id': '172.20.zz.yy',
'label_range': (100, 10), 'waiter': , 'bgp_server_port': 0, 'local_as': 64600,
'allow_local_as_in_count': 0, 'refresh_stalepath_time': 0, 'cluster_id':
None, 'local_pref': 100, 'refresh_max_eor_time': 0}
2018-07-30 19:00:57.455 2143006 INFO
neutron_dynamic_routing.services.bgp.agent.driver.ryu.driver
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] Added BGP Speaker
for local_as=64600 with router_id= 172.20.zz.yy.
2018-07-30 19:00:57.456 2143006 INFO bgpspeaker.api.base
[req-f15418e8-731b-4ebe-82a9-e2933e8df8b7 - - - - -] API method
neighbor.create called with args: {'connect_mode': 'active',
'cap_mbgp_evpn': False, 'remote_as': 35041, 'cap_mbgp_vpnv6': False,
'cap_mbgp_l2vpnfs': False, 'cap_four_octet_as_number': True,
'cap_mbgp_ipv6': False, 'is_next_hop_self': False, 'cap_mbgp_ipv4':
True, 'cap_mbgp_ipv4fs': False, 'is_route_reflector_client': False,
'cap_mbgp_ipv6fs': False, 'is_route_server_client': False,
'cap_enhanced_refresh': False, 'peer_next_hop': None, 'password': None,
'ip_address': u'172.20.x.y', 'cap_mbgp_vpnv4fs': False,
'cap_mbgp_
Re: [Openstack-operators] dashboard show only project after upgrading
Try enabling DEBUG in local_settings.py. Some dashboard or panel might fail loading for some reasons. I had a similar behavior last week and enabling DEBUG should show the error. -- Mathieu On Mon, Jul 30, 2018 at 11:35 AM, Ignazio Cassano wrote: > Sorry, I sent a wrong image. > The correct screenshot is attached here. > Regards > > 2018-07-30 17:33 GMT+02:00 Ignazio Cassano : >> >> Hello everyone, >> I upgraded openstack centos 7 from ocata to pike ad command line work fine >> but dashboard does not show any menu on the left . >> I missed the following menus: >> >> Project >> Admin >> Identity >> >> You can find the image attached here. >> >> Could anyone help me ? >> Regards >> Ignazio > > > > ___ > 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-server memcached connections
Following up on my own question, in case it's useful to others
Turns out that keystonemiddleware uses eventlet, and, by default,
creates a connection to memcached from each green thread (and doesn't
clean them up), and the green threads are essentially unlimited.
There is a solution for this, which implements a shared connection pool.
It's enabled via the keystone_authtoken.memcache_use_advanced_pool
config option.
Unfortunately it was broken in a few different ways (I guess this means
that no one is using it?)
I've worked with the keystone devs, and we were able to get a fix (in
keystonemiddleware) in just in time for the Rocky release. Related fixes
have also been backported to Queens (for the next update), and a couple
needed for Pike are pending completion.
With this in place, so-far I have not seen more than one connection to
memcached for each neutron-api worker process, and everything seems to
be working well.
Some relevant changes:
master:
https://review.openstack.org/#/c/583695/
Queens:
https://review.openstack.org/#/c/583698/
https://review.openstack.org/#/c/583684/
Pike:
https://review.openstack.org/#/c/583699/
https://review.openstack.org/#/c/583835/
I do wonder how others are managing memcached connections for larger
deployments...
~iain
On 06/26/2018 12:59 PM, iain MacDonnell wrote:
In diagnosing a situation where a Pike deployment was intermittently
slower (in general), I discovered that it was (sometimes) exceeding
memcached's maximum connection limit, which is set to 4096.
Looking closer, ~2750 of the connections are from 8 neutron-server
process. neutron-server is configured with 8 API workers, and those 8
processes have a combined total of ~2750 connections to memcached:
# lsof -i TCP:11211 | awk '/^neutron-s/ {print $2}' | sort | uniq -c
245 2611
306 2612
228 2613
406 2614
407 2615
385 2616
369 2617
398 2618
#
There doesn't seem to be much turnover - comparing samples of the
connections (incl. source port) 15 mins apart, two were dropped, and one
new one added.
In neutron.conf, keystone_authtoken.memcached_servers is configured, but
nothing else pertaining to caching, so
keystone_authtoken.memcache_pool_maxsize should default to 10.
Am I misunderstanding something, or shouldn't I see a maximum of 10
connections from each of the neutron-server API workers, with this
configuration?
Any known issues, or pointers to what I'm missing?
TIA,
~iain
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] dashboard show only project after upgrading
Ok, I will check. thanks Il Lun 30 Lug 2018 23:40 Mathieu Gagné ha scritto: > Try enabling DEBUG in local_settings.py. Some dashboard or panel might > fail loading for some reasons. > I had a similar behavior last week and enabling DEBUG should show the > error. > > -- > Mathieu > > > On Mon, Jul 30, 2018 at 11:35 AM, Ignazio Cassano > wrote: > > Sorry, I sent a wrong image. > > The correct screenshot is attached here. > > Regards > > > > 2018-07-30 17:33 GMT+02:00 Ignazio Cassano : > >> > >> Hello everyone, > >> I upgraded openstack centos 7 from ocata to pike ad command line work > fine > >> but dashboard does not show any menu on the left . > >> I missed the following menus: > >> > >> Project > >> Admin > >> Identity > >> > >> You can find the image attached here. > >> > >> Could anyone help me ? > >> Regards > >> Ignazio > > > > > > > > ___ > > 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
