Re: [Openstack] [PackStack][Neutron] erro port no present in bridge br-int

2018-11-07 Thread Budai Laszlo 

Hi,

please don't misunderstand me. If you have multiple nodes, then each of them 
will have its own ``host`` setting (like, host = node1 for node1 and host = 
node2 for node2). The important thing is that both the neutron.conf and 
nova.conf to have the same ``host`` setting on one node. So if you have used 
the ``host = node1`` in neutron.conf of node1, then do the same in the 
nova.conf on the same host. And if you have ``host = node2`` in neutron.conf on 
node2, then you should have the same in the nova.conf.

Kind regards,
Laszlo


On 11/7/18 2:52 PM, Soheil Pourbafrani wrote:

Thanks. In one node installation no error happened but in two node 
installation, I got the error. So I guess the answer of Laszlo is reasonable.

On Wed, Nov 7, 2018 at 10:23 AM Budai Laszlo mailto:laszlo.bu...@gmail.com>> wrote:

Hi

we had a similar situation when the ``host`` entry in the neutron.conf was 
different than the host entry in the nova.conf on the compute nodes.
So if you're setting a ``host`` entry in one of these files, then make sure 
the other file contains the same ``host`` setting.

see 
https://docs.openstack.org/neutron/rocky/configuration/neutron.html#DEFAULT.host
 and 
https://docs.openstack.org/nova/rocky/configuration/config.html#DEFAULT.host

Kind regards,
Laszlo

On 11/6/18 6:04 PM, Akihiro Motoki wrote:
 > How is your [ovs] bridge_mapping in your configuration?
 > Flat network requires a corresponding bridge_mapping entry and you also 
need to create a corresponding bridge in advance.
 >
 >
 > 2018年11月6日(火) 21:31 Soheil Pourbafrani mailto:soheil.i...@gmail.com> <mailto:soheil.i...@gmail.com 
<mailto:soheil.i...@gmail.com>>>:
 >
 >     Hi, I initilize an instance using a defined flat network and I got 
the error:
 >     port no present in bridge br-int
 >
 >     I have a 2 node deployment (controller + network, compute).
 >
 >     The output of the command ovs-vsctl show is
 >     *
 >     *
 >     *On the network node*
 >     d3a06f16-d727-4333-9de6-cf4ce3b0ce36
 >          Manager "ptcp:6640:127.0.0.1"
 >              is_connected: true
 >          Bridge br-ex
 >              Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> 
<http://127.0.0.1:6633>"
 >                  is_connected: true
 >              fail_mode: secure
 >              Port br-ex
 >                  Interface br-ex
 >                      type: internal
 >              Port phy-br-ex
 >                  Interface phy-br-ex
 >                      type: patch
 >                      options: {peer=int-br-ex}
 >              Port "ens33"
 >                  Interface "ens33"
 >          Bridge br-int
 >              Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> 
<http://127.0.0.1:6633>"
 >                  is_connected: true
 >              fail_mode: secure
 >              Port br-int
 >                  Interface br-int
 >                      type: internal
 >              Port patch-tun
 >                  Interface patch-tun
 >                      type: patch
 >                      options: {peer=patch-int}
 >              Port int-br-ex
 >                  Interface int-br-ex
 >                      type: patch
 >                      options: {peer=phy-br-ex}
 >              Port "tapefb98047-57"
 >                  tag: 1
 >                  Interface "tapefb98047-57"
 >                      type: internal
 >              Port "qr-d62d0c14-51"
 >                  tag: 1
 >                  Interface "qr-d62d0c14-51"
 >                      type: internal
 >              Port "qg-5468707b-6d"
 >                  tag: 2
 >                  Interface "qg-5468707b-6d"
 >                      type: internal
 >          Bridge br-tun
 >              Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633> 
<http://127.0.0.1:6633>"
 >                  is_connected: true
 >              fail_mode: secure
 >              Port patch-int
 >                  Interface patch-int
 >                      type: patch
 >                      options: {peer=patch-tun}
 >              Port br-tun
 >                  Interface br-tun
 >                      type: internal
 >              Port "vxlan-c0a8003d"
 >                  Interface "vxlan-c0a8003d"
 >                     

Re: [Openstack] [PackStack][Neutron] erro port no present in bridge br-int

2018-11-06 Thread Budai Laszlo 

Hi

we had a similar situation when the ``host`` entry in the neutron.conf was 
different than the host entry in the nova.conf on the compute nodes.
So if you're setting a ``host`` entry in one of these files, then make sure the 
other file contains the same ``host`` setting.

see 
https://docs.openstack.org/neutron/rocky/configuration/neutron.html#DEFAULT.host
 and 
https://docs.openstack.org/nova/rocky/configuration/config.html#DEFAULT.host

Kind regards,
Laszlo

On 11/6/18 6:04 PM, Akihiro Motoki wrote:

How is your [ovs] bridge_mapping in your configuration?
Flat network requires a corresponding bridge_mapping entry and you also need to 
create a corresponding bridge in advance.


2018年11月6日(火) 21:31 Soheil Pourbafrani mailto:soheil.i...@gmail.com>>:

Hi, I initilize an instance using a defined flat network and I got the 
error:
port no present in bridge br-int

I have a 2 node deployment (controller + network, compute).

The output of the command ovs-vsctl show is
*
*
*On the network node*
d3a06f16-d727-4333-9de6-cf4ce3b0ce36
     Manager "ptcp:6640:127.0.0.1"
         is_connected: true
     Bridge br-ex
         Controller "tcp:127.0.0.1:6633 "
             is_connected: true
         fail_mode: secure
         Port br-ex
             Interface br-ex
                 type: internal
         Port phy-br-ex
             Interface phy-br-ex
                 type: patch
                 options: {peer=int-br-ex}
         Port "ens33"
             Interface "ens33"
     Bridge br-int
         Controller "tcp:127.0.0.1:6633 "
             is_connected: true
         fail_mode: secure
         Port br-int
             Interface br-int
                 type: internal
         Port patch-tun
             Interface patch-tun
                 type: patch
                 options: {peer=patch-int}
         Port int-br-ex
             Interface int-br-ex
                 type: patch
                 options: {peer=phy-br-ex}
         Port "tapefb98047-57"
             tag: 1
             Interface "tapefb98047-57"
                 type: internal
         Port "qr-d62d0c14-51"
             tag: 1
             Interface "qr-d62d0c14-51"
                 type: internal
         Port "qg-5468707b-6d"
             tag: 2
             Interface "qg-5468707b-6d"
                 type: internal
     Bridge br-tun
         Controller "tcp:127.0.0.1:6633 "
             is_connected: true
         fail_mode: secure
         Port patch-int
             Interface patch-int
                 type: patch
                 options: {peer=patch-tun}
         Port br-tun
             Interface br-tun
                 type: internal
         Port "vxlan-c0a8003d"
             Interface "vxlan-c0a8003d"
                 type: vxlan
                 options: {df_default="true", in_key=flow, local_ip="192.168.0.62", 
out_key=flow, remote_ip="192.168.0.61"}
     ovs_version: "2.9.0"

*On the Compute node*
*
*
*55e62867-9c88-4925-b49c-55fb74d174bd*
*    Manager "ptcp:6640:127.0.0.1"*
*        is_connected: true*
*    Bridge br-ex*
*        Controller "tcp:127.0.0.1:6633 "*
*            is_connected: true*
*        fail_mode: secure*
*        Port phy-br-ex*
*            Interface phy-br-ex*
*                type: patch*
*                options: {peer=int-br-ex}*
*        Port "enp2s0"*
*            Interface "enp2s0"*
*        Port br-ex*
*            Interface br-ex*
*                type: internal*
*    Bridge br-tun*
*        Controller "tcp:127.0.0.1:6633 "*
*            is_connected: true*
*        fail_mode: secure*
*        Port br-tun*
*            Interface br-tun*
*                type: internal*
*        Port "vxlan-c0a8003e"*
*            Interface "vxlan-c0a8003e"*
*                type: vxlan*
*                options: {df_default="true", in_key=flow, local_ip="192.168.0.61", 
out_key=flow, remote_ip="192.168.0.62"}*
*        Port patch-int*
*            Interface patch-int*
*                type: patch*
*                options: {peer=patch-tun}*
*    Bridge br-int*
*        Controller "tcp:127.0.0.1:6633 "*
*            is_connected: true*
*        fail_mode: secure*
*        Port int-br-ex*
*            Interface int-br-ex*
*                type: patch*
*                options: {peer=phy-br-ex}*
*        Port br-int*
*            Interface br-int*
*                type: internal*
*        Port patch-tun*
*            Interface patch-tun*

Re: [Openstack] [Openstack-Ansible] Unable to install Openstack Queens using Ansible

2018-09-18 Thread Budai Laszlo 

Hi,

run dmesg on your deployment host. It should print which process has been 
evicted by the OOM killer.
We had similar issues with our deployment host. We had to increase its memory 
to 9G to have openstack-ansiblle working properly.
You should also monitor the memory usage of your processes on the 
controller/deployment host.

good luck,
Laszlo

On 18.09.2018 13:43, Anirudh Gupta wrote:

Hi Team,

I am installing Open Stack Queens using the Openstack Ansible and facing some 
issues


*System Configuration*


*Controller/Deployment Host*

RAM - 12 GB

Hard disk - 100 GB

Linux - Ubuntu 16.04

Kernel Version - 4.4.0-135-generic



*Compute*

RAM - 4 GB

Hard disk - 100 GB

Linux - Ubuntu 16.04

Kernel Version - 4.4.0-135-generic

*Issue Observed:*

When we run the below playbook

openstack-ansible setup-openstack.yml

*Error Observed:*

After running for some duration, it throws the error of "Out of Memory Killing 
mysqld"


In the "top" command, we see only haproxy processes and the system gets so slow 
that we are not even able to login into the system.


Can you please help me in resolving the issue.


Regards

Anirudh Gupta




___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack-operators] [openstack-ansible] configuration file override

2018-08-21 Thread Budai Laszlo 

On 21.08.2018 12:32, jean-phili...@evrard.me wrote:

My problem is that the servers that I'm using have their name defined as 
dcx-cy-blz (datacenter - chassis - blade). After installing openstack these 
names are reflected as the names of the hosts in nova.
We would like to have our compute nodes referenced as compute1, compute2 


The simplest is then to use compute1, compute2, etc. in your 
/etc/openstack_deploy/openstack_user_config. You can still internally refer to 
dcx-cy-blz if you like, it will just not appear openstack or in the inventory.

Regards,
JP




This is how I tried, but did not worked out  in the 
/etc/openstack_deploy/openstack_user_config.yml I had:

_compute_hosts: _hosts
  compute1:
ip: 10.210.201.40
host_vars:
neutron_neutron_conf_overrides:
  DEFAULT:
host: "{{ inventory_hostname }}.example.intra"
nova_nova_conf_overrides:
  DEFAULT:
host: "{{ inventory_hostname }}.example.intra"
  compute2:
ip: 10.210.201.41
host_vars:
neutron_neutron_conf_overrides:
  DEFAULT:
host: "{{ inventory_hostname }}.example.intra"
nova_nova_conf_overrides:
  DEFAULT:
host: "{{ inventory_hostname }}.example.intra"


What have done wrong?

Thank you,
Laszlo

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

Re: [Openstack-operators] [openstack-ansible] configuration file override

2018-08-20 Thread Budai Laszlo 

Hello Jean-Philippe,

thank you for your answer.
for the version I have this:

root@ansible-ws1:~# openstack-ansible --version
Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e 
@/etc/openstack_deploy/user_variables.yml "
ansible-playbook 2.4.4.0
  config file = /root/.ansible.cfg
  configured module search path = ['/etc/ansible/roles/plugins/library']
  ansible python module location = 
/opt/ansible-runtime/lib/python3.5/site-packages/ansible
  executable location = /opt/ansible-runtime/bin/ansible-playbook
  python version = 3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609]

EXIT NOTICE [Playbook execution success] **
===
root@ansible-ws1:~#

I'm trying to install the queens release of openstack.

My problem is that the servers that I'm using have their name defined as 
dcx-cy-blz (datacenter - chassis - blade). After installing openstack these 
names are reflected as the names of the hosts in nova.
We would like to have our compute nodes referenced as compute1, compute2 
We found that the "host" parameter of the nova.conf can be used for this. We've 
set an override for this in the user variables:

nova_nova_conf_overrides:
  DEFAULT:
host: "{{ inventory_hostname }}.ourdomain"

The result was that the name in nova became OK, but when nova-compute was 
trying to start instances it was failing as interfaces were not created in the 
ovs br-int. It turned out that we need the same host setting for neutron as 
well ...

so I decided to add a similar entry for the neutron.conf as well, but then in the 
neutron,conf on the neutron-server we had a name of the form 
"network1_neutron_server_container-HASH.ourdomain". And the neutron server was 
complaining that this is not a valid hostname (I suppose due to the underscores that 
appears in the name ... ).

So right now I'm looking for a way to set that host parameter in the 
neutron.conf and nova.conf only on the compute nodes.

Thank you,
Laszlo

On 20.08.2018 17:28, jean-phili...@evrard.me wrote:

In this example the override is part of a compute host definition and there it is in the 
host_vars section (compute_hosts -> 900089-compute001 -> host_vars -> 
override). Is it possible to apply such an override for all the compute hosts by not 
using the hostname? For instance something like:

" compute_hosts:
nova_nova_conf_overrides:
  DEFAULT:
remove_unused_original_minimum_age_seconds: 43200
"


You can set nova_nova_conf_overrides: into a file named 
/etc/openstack_deploy/user_variables.yml and it will apply on all your nodes.

If you want to be more surgical, you'd have to give more details about your 
OpenStack-Ansible version and what you're trying to achieve.

Regards,
Jean-Philippe Evrard (evrardjp)





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

[Openstack-operators] [openstack-ansible] configuration file override

2018-08-20 Thread Budai Laszlo 


Dear all,

Openstack-ansible (OSA) allows us to override parameters in the configuration 
files as described here: 
https://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/app-advanced-config-override.html

there is the following statement:

"You can also apply overrides on a per-host basis with the following 
configuration in the /etc/openstack_deploy/openstack_user_config.yml file:

compute_hosts:
  900089-compute001:
ip: 192.0.2.10
host_vars:
  nova_nova_conf_overrides:
DEFAULT:
  remove_unused_original_minimum_age_seconds: 43200
libvirt:
  cpu_mode: host-model
  disk_cachemodes: file=directsync,block=none
database:
  idle_timeout: 300
  max_pool_size: 10

"

In this example the override is part of a compute host definition and there it is in the 
host_vars section (compute_hosts -> 900089-compute001 -> host_vars -> 
override). Is it possible to apply such an override for all the compute hosts by not 
using the hostname? For instance something like:

" compute_hosts:
  nova_nova_conf_overrides:
DEFAULT:
  remove_unused_original_minimum_age_seconds: 43200
"

would this be correct?


Thank you,
Laszlo

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

[Openstack] [openstack-ansible] configuration file override

2018-08-20 Thread Budai Laszlo 

Dear all,

Openstack-ansible (OSA) allows us to override parameters in the configuration 
files as described here: 
https://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/app-advanced-config-override.html

there is the following statement:

"You can also apply overrides on a per-host basis with the following 
configuration in the /etc/openstack_deploy/openstack_user_config.yml file:

compute_hosts:
  900089-compute001:
ip: 192.0.2.10
host_vars:
  nova_nova_conf_overrides:
DEFAULT:
  remove_unused_original_minimum_age_seconds: 43200
libvirt:
  cpu_mode: host-model
  disk_cachemodes: file=directsync,block=none
database:
  idle_timeout: 300
  max_pool_size: 10

"

In this example the override is part of a compute host definition and there it is in the 
host_vars section (compute_hosts -> 900089-compute001 -> host_vars -> 
override). Is it possible to apply such an override for all the compute hosts by not 
using the hostname? For instance something like:

" compute_hosts:
  nova_nova_conf_overrides:
DEFAULT:
  remove_unused_original_minimum_age_seconds: 43200
"

would this be correct?


Thank you,
Laszlo

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] openstac-ansible question

2018-07-04 Thread Budai Laszlo 

Dear all,

is it possible to define exceptions in the group_binds definition for a network?

for instance we have something like this:
- network:
container_bridge: "vlan4"
container_type: "veth"
container_interface: "eth1"
ip_from_q: "container"
type: "raw"
group_binds:
  *- all_containers*
  - hosts
is_container_address: true
is_ssh_address: true

So, instead of *all_containers* I would be interested in something like 
"all_containers except those running on the ceph nodes".

Any ideas are welcome.

Thank you,
Laszlo

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] [openstack-ansible] group_binds exceptions

2018-07-04 Thread Budai Laszlo 

Dear all,

is there a way to define exceptions for the group_binds for a network 
definition?

for instance we have something like this:
- network:
container_bridge: "vlan4"
container_type: "veth"
container_interface: "eth1"
ip_from_q: "container"
type: "raw"
group_binds:
  *- all_containers*
  - hosts
is_container_address: true
is_ssh_address: true

So, instead of *all_containers* I would be interested in something like 
"all_containers except those running on the ceph nodes".

Any ideas are welcome.

Thank you,
Laszlo

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

[Openstack-operators] usernames in horizon instance action log

2018-03-22 Thread Budai Laszlo 
Dear all,

is there a way to configure horizon to display the username instead of user ID 
in the instances action log?

Right now it displays the: Req Id, Action, Start time, userID, Message

Kind regards,
Laszlo

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

[Openstack-operators] monitoring openstack processes

2018-02-18 Thread Budai Laszlo 

Dear all,

recently we had an issue where the novncproxy on one of our controller nodes 
stopped to respond. The tcp connection got built, but no response was coming 
from the process.
What are your recommendations/experiences regarding the monitoring of the 
openstack processes?

Kind regards,
Laszlo

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