Re: [Openstack] [OpenStack][cinder]Does cinder allocate disk to the volumes dynamically?

[Soheil Pourbafrani]

When I installed OpenStack using PackStack, the size of LVM group was 20G
but I could create 18 volume each of which 20G size (so in the PackStack
the Cinder allocate volumes dynamically), but installing OpenStack from
repository, the Cinder allocate disk to volume statically because I have
volume group in size 140G but I only can create 7 volume of size 20G. So
How Can I configure Cinder to allocate disk dynamically?

On Wed, Nov 28, 2018 at 3:56 PM Soheil Pourbafrani 
wrote:

> Hi,
>
> I was wondering if the Cinder allocates disk to volumes statically or
> dynamically?
>
___
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] [OpenStack][cinder]Does cinder allocate disk to the volumes dynamically?

[Soheil Pourbafrani]

Hi,

I was wondering if the Cinder allocates disk to volumes statically or
dynamically?
___
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] [PackStack][Cinder]Save Volumes in The Compute nodes

[Soheil Pourbafrani]

Thanks a lot!

On Mon, Nov 26, 2018 at 1:06 PM Javier Pena  wrote:

>
>
> --
>
> Thanks! and Does it need to cinder module to be installed on compute nodes?
>
>
> You will need to run the cinder-volume service in the compute nodes. You
> will have to set it up manually, though, because Packstack only installs it
> on the controller.
>
> Regards,
> Javier
>
> On Sat, Nov 17, 2018 at 1:13 PM Bernd Bausch 
> wrote:
>
>> Yes. You need to enable Cinder’s InstanceLocalityFilter, see
>>
>> https://docs.openstack.org/cinder/latest/configuration/block-storage/scheduler-filters.html
>> .
>>
>> Here a tip:
>> https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-instance/
>>
>> Bernd
>>
>> On Nov 17, 2018, at 8:38, Soheil Pourbafrani 
>> wrote:
>>
>> Hi,
>> I have 8 servers with just local HDD disk. I want to use one server as
>> the controller and network node and the other (7 servers) as the compute
>> node.
>>
>> I was wondering if it's possible to install PackStack that every compute
>> node to store its volumes in it's HDD local disk? (I guess the Cinder
>> should be installed on every Compute node alongside other settings)
>>
>> Thanks
>>
>> ___
>> 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
>
>
>
___
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] [OpenStack][Cinder]How config cinder.conf [nova] part for InstanceLocalityFilter

[Soheil Pourbafrani]

Hi,

I want to enable InstanceLocalityFiletr for the Cinder. I set

scheduler_default_filters =
AvailabilityZoneFilter,CapacityFilter,CapabilitiesFilter,InstanceLocality

But the document said we should specify an account with privileged rights
for Nova in Cinder configuration (configure a keystone authentication
plugin in the [nova] section), but I can't find an example for such
configuration. Can anyone give an example?
___
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] [OpenStack][Cinder] Config Volumes to Store on Compute nodes

[Soheil Pourbafrani]

Hi,

I want to configure cinder to store Volumes on the Compute nodes. I know I
should use the InstanceLocalityFilter. Suppose we have one Controller and
two Compute node, should I install the Cinder on each node (Controller and
Compute)?

I will be appreciated if you suggest me any instruction about this.

Thanks!
___
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] [OpenStack][Keystone] the controller is node listening on port 5000

[Soheil Pourbafrani]

Hi,

I installed keystone step by step according to the OpenStack Doc

but
the http server is not listening on the port 5000!
The only difference is my hostname (address) is "controller.a.b" instead of
"controller".
In verifying part of the document I could do all (like creating a user,
project, ) but after installing glance, I found out the Glance API is
not running properly and it's because of Keystone is not listening on port
5000!

Here are AUTH variables:

export OS_PROJECT_DOMAIN_NAME=Default
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=XXX
export OS_AUTH_URL=http://controller.a.b:5000/v3
export OS_IDENTITY_API_VERSION=3
export OS_IMAGE_API_VERSION=2

When I try "glance image-list", I got:

"http://controller.a.b:9292/v2/images?limit=20_key=name_dir=asc:
Unable to establish connection"

Here is TCP listening ports:

tcp0  0 127.0.0.1:250.0.0.0:*   LISTEN
1614/master
tcp0  0 0.0.0.0:91910.0.0.0:*   LISTEN
961/python2
tcp0  0 0.0.0.0:25672   0.0.0.0:*   LISTEN
957/beam.smp
tcp0  0 192.168.0.31:3306   0.0.0.0:*   LISTEN
1622/mysqld
tcp0  0 192.168.0.31:2379   0.0.0.0:*   LISTEN
963/etcd
tcp0  0 192.168.0.31:11211  0.0.0.0:*   LISTEN
952/memcached
tcp0  0 127.0.0.1:11211 0.0.0.0:*   LISTEN
952/memcached
tcp0  0 192.168.0.31:2380   0.0.0.0:*   LISTEN
963/etcd
tcp0  0 0.0.0.0:43690.0.0.0:*   LISTEN
1/systemd
tcp0  0 0.0.0.0:22  0.0.0.0:*   LISTEN
953/sshd
tcp6   0  0 ::1:25  :::*LISTEN
1614/master
tcp6   0  0 :::5000 :::*LISTEN
960/httpd
tcp6   0  0 :::5672 :::*LISTEN
957/beam.smp
tcp6   0  0 ::1:11211   :::*LISTEN
952/memcached
tcp6   0  0 :::80   :::*LISTEN
960/httpd
tcp6   0  0 :::22   :::*LISTEN
953/sshd

As you can see httpd is listening on port 5000 IPV6, but it's not active
for IPV4!

Here is keystone.log:

2018-11-24 15:55:59.685 17325 INFO keystone.common.wsgi
[req-9fedd505-5d98-4c12-a6ad-967f28c766e7 - - - - -] POST
http://controller.a.b:5000/v3/auth/tokens
2018-11-24 15:56:00.275 17327 INFO keystone.common.wsgi
[req-ca93da87-1d9f-4611-835c-d6972054b8e1 - - - - -] POST
http://controller.a.b:5000/v3/auth/tokens
2018-11-24 15:56:00.929 17328 INFO keystone.common.wsgi
[req-cf8c6af8-342d-4b14-9826-ba27e5f2897a 1b96f6b67f08495092e98a9b60476152
b33579097090499499625154e92724ee - default default] GET
http://controller.a.b:5000/v3/domains/default
2018-11-24 15:56:14.753 17325 INFO keystone.common.wsgi
[req-cca0e4a5-0ef9-40d8-a2f4-56c1f0acafcc 1b96f6b67f08495092e98a9b60476152
b33579097090499499625154e92724ee - default default] POST
http://controller.a.b:5000/v3/users
2018-11-24 15:56:14.773 17325 WARNING py.warnings
[req-cca0e4a5-0ef9-40d8-a2f4-56c1f0acafcc 1b96f6b67f08495092e98a9b60476152
b33579097090499499625154e92724ee - default default]
/usr/lib/python2.7/site-packages/oslo_policy/policy.py:896: UserWarning:
Policy identity:create_user failed scope check. The token used to make the
request was project scoped but the policy requires ['system'] scope. This
behavior may change in the future where using the intended scope is required
  warnings.warn(msg)

Another difference between my system and document is that I use static IP
and here are interface settings:
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="enp2s0"
UUID="62aa5ce8-64da-41b4-abd3-293fd43584fa"
DEVICE="enp2s0"
ONBOOT="yes"
IPADDR="192.168.0.X"
PREFIX="24"
GATEWAY="192.168.0.1"
DNS1="192.168.0.1"
DNS2="8.8.8.8"
IPV6_PRIVACY="no"


What can be the cause?
___
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] [OpenStack][Glance]Getting instance snapshot result in size 0 byte

[Soheil Pourbafrani]

Hi,

I have many instances running on OpenStack and I wanted to export them. So
I create a snapshot of an instance and it results in a new record in images
in the format of Qcow2 and size of 0 bytes! It just created a volume
snapshot of the instance, too.

I tried with both command line and horizon but the same results!

How can I export instances in the correct way?
___
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] [PackStack][Cinder]Save Volumes in The Compute nodes

[Soheil Pourbafrani]

Thanks! and Does it need to cinder module to be installed on compute nodes?

On Sat, Nov 17, 2018 at 1:13 PM Bernd Bausch  wrote:

> Yes. You need to enable Cinder’s InstanceLocalityFilter, see
>
> https://docs.openstack.org/cinder/latest/configuration/block-storage/scheduler-filters.html
> .
>
> Here a tip:
> https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-instance/
>
> Bernd
>
> On Nov 17, 2018, at 8:38, Soheil Pourbafrani 
> wrote:
>
> Hi,
> I have 8 servers with just local HDD disk. I want to use one server as the
> controller and network node and the other (7 servers) as the compute node.
>
> I was wondering if it's possible to install PackStack that every compute
> node to store its volumes in it's HDD local disk? (I guess the Cinder
> should be installed on every Compute node alongside other settings)
>
> Thanks
>
> ___
> 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] [OpenStack][Compute-Neutron] Is it possible to create flat network from different NICs

[Soheil Pourbafrani]

Thanks a lot.

On Wed, Nov 21, 2018 at 2:51 PM Slawomir Kaplonski 
wrote:

> Hi,
>
> Yes, that should be possible. You can create 4 bridges on compute node and
> add all of them to bridge_mappings config option.
> Then You can create 4 networks with different physical_network for each of
> them and agent will know which bridge should be used for ports from each
> network.
> It is described e.g. in [1].
>
> [1]
> https://ask.openstack.org/en/question/94206/how-to-understand-the-bridge_mappings/?answer=94230#post-id-94230
>
> > Wiadomość napisana przez Soheil Pourbafrani  w
> dniu 21.11.2018, o godz. 12:08:
> >
> > Hi,
> >
> > I installed OpenStack on One node (for test) and creating a flat
> external network I could connect VMs to the provider network (internet).
> >
> > In the production environment, we have 4 NIC on each server and each
> server (compute node) will run 4 instances. My question is, is it possible
> to create a separate external network based on each NIC (so 4 external
> networks) and run each instance using one of them?
> > ___
> > 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
>
> —
> Slawek Kaplonski
> Senior software engineer
> Red Hat
>
>
___
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] [OpenStack][Compute-Neutron] Is it possible to create flat network from different NICs

[Soheil Pourbafrani]

Hi,

I installed OpenStack on One node (for test) and creating a flat external
network I could connect VMs to the provider network (internet).

In the production environment, we have 4 NIC on each server and each server
(compute node) will run 4 instances. My question is, is it possible to
create a separate external network based on each NIC (so 4 external
networks) and run each instance using one of them?
___
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] [PackStack][Cinder]Save Volumes in The Compute nodes

[Soheil Pourbafrani]

Hi,
I have 8 servers with just local HDD disk. I want to use one server as the
controller and network node and the other (7 servers) as the compute node.

I was wondering if it's possible to install PackStack that every compute
node to store its volumes in it's HDD local disk? (I guess the Cinder
should be installed on every Compute node alongside other settings)

Thanks
___
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] How to detach Image from instance

[Soheil Pourbafrani]

Hi,

I lunch an instance using CentOS ISO image and install it on ephemeral disk
(no volume created). So after finishing the installation, I rebooted the
instance, *but it boot the CentOS image, again. *While on the path
/var/lib/nova on the compute node I can see a disk for the instance is
created. So I guess removing the image from instance will force it to boot
the installed OS. Is there any way to do that?
___
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] [PackStack][cinder, nova] How to create ephemeral instance from volume

[Soheil Pourbafrani]

Hi,

I have some volumes with a snapshot of each. I was wondering is it possible
to create a new instance with the only ephemeral disk (not root disk) from
them. Actually, I didn't want to create volume for new instances.

Thanks
___
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] [PackStack][Cinder] On which node OpenStack store data of each instance

[Soheil Pourbafrani]

Hi,

My question is does OpenStack store volumes somewhere other than
the compute node?
For example in PackStack on two nodes, one for controller and network and
the other for compute node, the instance's volumes will be stored on the
controller or on compute?
___
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] [PackStack][Neutron] erro port no present in bridge br-int

[Soheil Pourbafrani]

Thank you for the clarification, Laszlo.

On Wed, Nov 7, 2018 at 5:39 PM Budai Laszlo  wrote:

> 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  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
> >  >

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

[Soheil Pourbafrani]

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  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  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>"
> >  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>"
> >  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>"
> >  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 <http://127.0.0.1:6633>"*
> > *is_connected: true*
> > *fail_mode: secure*
> > *Port phy-br-ex*
> > *Interface phy-br

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

[Soheil Pourbafrani]

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*
*type: patch*
*options: {peer=patch-int}*
*ovs_version: "2.9.0"*

How can I solve the problem?

Thanks
___
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] [PackStack][Neutron] openvswitch error - Port not present in bridge br-int

[Soheil Pourbafrani]

Hi, I have 2 node packsack. One as controller and network, the other as
compute.
I created a flat external network to connect external provider network.
When I lunch instance using that I got the error:
openvswitch error - Port not present in bridge br-int

The output of the ovs-vsctl show in compute node is:
00a36389-cb9e-45ce-a5be-d2da04c295c9
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-ex
Port "enp2s0"
Interface "enp2s0"
Port br-ex
Interface br-ex
type: internal
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
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
ovs_version: "2.9.0"

and the output in the controller node is:
36420024-d9b9-4fd9-a64a-5152f8012af5
Manager "ptcp:6640:127.0.0.1"
is_connected: true
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 patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-ex
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port "ens33"
Interface "ens33"
Port phy-br-ex
Interface phy-br-ex
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
type: internal
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 "qg-0e5c98e8-02"
tag: 4095
Interface "qg-0e5c98e8-02"
type: internal
Port int-br-ex
Interface int-br-ex
type: patch
options: {peer=phy-br-ex}
Port "qr-71e0313c-18"
tag: 5
Interface "qr-71e0313c-18"
type: internal
ovs_version: "2.9.0"


Which part is faulty and how can I fix that?

Thanks
___
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] [PackStack][Neutron] How to configure for external network

[Soheil Pourbafrani]

Thanks a lot.

On Sun, Nov 4, 2018 at 1:59 PM Slawomir Kaplonski 
wrote:

> Hi,
>
> > Wiadomość napisana przez Soheil Pourbafrani  w
> dniu 04.11.2018, o godz. 11:10:
> >
> > Thanks,
> >
> > Actually, I created a vxlan network and define the internal network and
> external network in range of my network provider, 192.168.0.1. I create a
> router and interface and lunch an instance with an internal network that
> has floating IP, too.
>
> As I said before, Your external network has to be vlan or flat network.
> Vxlan network can be used only as tenant network. Packets from such network
> can’t go „outside” to Your provider’s network and it’s not matter of IP
> addresses used in network.
>
> >
> > From the controller node I can ping the instance using floating IP: "ip
> netns exec qdhcp-9691cdb8-56f3-44b6-b501-4678eceb3866 ping 192.168.0.4",
> but the instance is not accessible in the external network and the command
> ping 192.168.0.4 failed!
> >
> > What is the problem?
> >
> >
> > On Sun, Nov 4, 2018 at 12:52 PM Slawomir Kaplonski 
> wrote:
> > Hi,
> >
> > For external network You should use flat or vlan type - which one of
> them, depends on Your provider’s configuration - if You should use some
> VLAN, You need vlan network.
> > Vxlan networks can be only used for tenant networks.
> >
> > > Wiadomość napisana przez Soheil Pourbafrani  w
> dniu 04.11.2018, o godz. 07:22:
> > >
> > > Hi,
> > >
> > > I installed PackStack on two nodes, one as Controller and Network, the
> other as the Compute Node. After installation, I created a new br-ex
> interface and I did OVS settings. I also define two internal and external
> network (flat) and router and interfaces.
> > > The internal network range IP is not a valid range and for the test, I
> set it in 10.10.0.0/24. I can lunch instances using internal network and
> VMs can connect to each other using that.
> > > The external range IP is the same as our Provider range IP (the range
> that our devices get when connecting to the internet). But lunching
> instances using the external network it can't connect to the internet or
> ping other devices in the network (proper security groups are set). IMy
> question was, is there any tutorial for configuring the network in two
> nodes so VMs can connect to the internet? What kind of Network does it
> need? flat, vlan or vxlan?
> > >
> > > Thanks
> > > ___
> > > 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
> >
> > —
> > Slawek Kaplonski
> > Senior software engineer
> > Red Hat
> >
>
> —
> Slawek Kaplonski
> Senior software engineer
> Red Hat
>
>
___
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] [PackStack][Neutron] How to configure for external network

[Soheil Pourbafrani]

Hi,

I installed PackStack on two nodes, one as Controller and Network, the
other as the Compute Node. After installation, I created a new br-ex
interface and I did OVS settings. I also define two internal and external
network (flat) and router and interfaces.
The internal network range IP is not a valid range and for the test, I set
it in 10.10.0.0/24. I can lunch instances using internal network and VMs
can connect to each other using that.
The external range IP is the same as our Provider range IP (the range that
our devices get when connecting to the internet). But lunching instances
using the external network it can't connect to the internet or ping other
devices in the network (proper security groups are set). IMy question was,
is there any tutorial for configuring the network in two nodes so VMs can
connect to the internet? What kind of Network does it need? flat, vlan or
vxlan?

Thanks
___
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