Re: [Openstack] API endpoint naming in Keystone

[Alberto Molina Coballes]

Hi Andrew!

AFAIK there's no difference between Liberty and Mitaka nova endpoints
(we're using newton and $(tenant_id)s is still present in the nova
endpoints and it's working properly). It seems to me that the
difference you're showing was introduced in ocata, you can compare the
official doc install for newton [1] and ocata [2].

Regards,

Alberto

[1] 
https://docs.openstack.org/newton/install-guide-ubuntu/nova-controller-install.html
[2] 
https://docs.openstack.org/ocata/install-guide-ubuntu/nova-controller-install.html

___
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] kolla-ansible Openstack MTU customization

[Alberto Molina Coballes]

Hi Manuel,

I'm not a kolla-ansible user, but I suppose that you must modify properly
the templates:

kolla-ansible/ansible/roles/neutron/templates/neutron.conf.j2
kolla-ansible/ansible/roles/neutron/templates/ml2_conf.ini.j2

following the instructions of the link provided.

Regards,

Alberto
___
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] Dibbler, ipv6_pd_enabled, and Ubuntu.

[Alberto Molina Coballes]

Hi Ken,

I'm using Newton on Debian Stretch with IPv6 prefix delegation (I'm not
tested it from horizon, only from CLI). The configuration was carried out
following the steps described here: http://www.debug-all.com/?p=187

Alberto
___
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] Root disk resize down

[Alberto Molina Coballes]

On mié, feb 10, 2016 at 12:41:42 +0200, Mārtiņš Jakubovičs wrote:
> Hello,
> 
> Looks like it is not working, when I try to resize instance I receive:
> Server disk was unable to be resized because: Resize to zero disk flavor is
> not allowed.
> 

Sorry Mārtiņš, my previous comment wasn't completely correct. 

I'm assuming that you're using Ceph as a cinder backend and using
instances with the root filesystem defined in a volume, so you want
to resize your instances without modify the size of the volume, just
modify RAM and vCPU, right?

In that case you can define several flavors with 0 GiB of disk size
and resize up and down your instances between these flavors, but not
with other flavors with a disk size greater than 0 GiB defined. 

Regards,

Alberto

___
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] Database schema

[Alberto Molina Coballes]

Hi Dionisis,

Reading your question I've remembered a python script that generates
OpenStack ER diagrams and I've found it again:

https://coderwall.com/p/pngadg/er-diagram-for-openstack-database

It's really nice and simple, but it needed an update:

https://github.com/albertomolina/openstack-db-schema

Maybe you can find it useful.

Cheers

Alberto

2015-12-03 8:45 GMT+01:00 Drakopoulos, Dionisis (Nokia - GR/Athens) <
dionisis.drakopou...@nokia.com>:

>
>
> Good morning from Greece!
>
> Does anybody know where to find a valid Database schema for OpenStack
> releases?
>
>
>
> If not one for all projects, then at least for core ones.
>
>
>
> Thank you!
>
>
>
> *Dionisis (Dennis) Drakopoulos*
> *OMP MP SW Engineer/SyVe/Maintenance/SL*
>
> *MBB OMP MP R 14 GR*
>
> 
>
>
>
>
>
> ___
> 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] Juno neutron - Tenant Network with multiple routers, how to nat/filter ?

[Alberto Molina Coballes]

2015-11-27 20:28 GMT+01:00 Saverio Proto :

> Hello,
>
> I have a cloud user that is trying to implement the following topology
>
> ext_net <|R1|>  internal_net  <|R2|>  dbservers_network
>
> where
> - internal_net: 10.0.2.0/24
> - dbservers_net: 10.0.3.0/24
>
> Now according to the documentation:
> http://docs.openstack.org/admin-guide-cloud/networking_adv-features.html
>
> My user was able to set up the necessary static routes on R1 to reach
> the dbservers_network and on R2 to have a default via R1
>
> However, it seems impossible to manipulate Nat rules on R1 and R2.
> R1 for example will SNAT traffic only for source IPs into 10.0.2.0
> making impossible for hosts in dbservers_network to access the
> Internet.
>
> To see the configuration, I can as an Operator use iptables commands
> into the namespaces on the network node. But what can users do ?
>
> So far, I ended up with the feeling, that is not possible to have two
> hop topologies where hosts two hops away from the gateway can make
> traffic with the outside Internet. Is this really the case ?
>
>
Hi Saverio,

Recently I was facing the same situation and AFAIK cloud users can't set
NAT rules on internal routers via neutron API  Those NAT rules are
restricted to routers connected to an external router (setting the router
gateway or doing floating IPs associations). In our case this limitation
was solved using an instance as a router and maybe you can find useful the
description of the followed steps:

https://albertomolina.wordpress.com/2015/11/22/playing-around-with-openstack-using-an-instance-as-router/

I hope this helps

Cheers

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

Re: [Openstack] Cinder created volume with status error

[Alberto Molina Coballes]

Hi Wilson,

The size of your cinder-volumes VG is only 10 GiB and you're trying to
create inside of it a 10 GiB logical volume

cinder-scheduler.log says:
...
Unexpected error while running command.\nCommand: sudo cinder-rootwrap
/etc/cinder/rootwrap.conf lvcreate -n
volume-a577999a-64f3-4ffb-9044-af5758a260cd cinder-volumes -L 10g\nExit
code: 5\nStdout: u\'\'\nStderr: u\'  Volume group cinder-volumes has
insufficient free space (2559 extents): 2560 required.\\n\'\n']
...

Try to increase cinder-volume size or try to create a smaller cinder volume

Regards

Alberto
___
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] What are people using for configuration management? Puppet? Chef? Other?

[Alberto Molina Coballes]

Hi,

Take a look at the OpenStack User Survey [1], particularly to the
deployment tools section [2]. That's what people say are using.

Alberto

[1]
superuser.openstack.org/articles/openstack-user-survey-insights-november-2014
[2]
http://a3.res.cloudinary.com/hqq9ey1mh/image/upload/c_limit,w_793/v1414983604/i6cbkmbhnq0mpqnqh6y5.png
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack] Very low bandwidth between instances and routers with OVS, GRE on Debian Jessie (Icehouse)

[Alberto Molina Coballes]

2014-11-10 13:45 GMT+01:00 Akilesh K akilesh1...@gmail.com:

 Hi Alberto,
 May I know the flavor and image you were using to do this test. TSO seems
 to be a method that moves the process of tcp segmentation off to the nic
 card.


Hi Akilesh,

I was using m1.tiny flavor with 512MiB of RAM and 1 vCPU for all the
previous tests.

Testing now with m1.smaill (2048 MiB of RAM and 1 vCPU) there is a slight
increase in the bandwidth between the instance and its router: ~
300Kbits/sec. The increase is more evident using m1.medium (4096 MiB of RAM
and 2 vCPUs) where a bandwidth ~ 700 Kbits/sec is achieved.

In both cases bandwidth of 700-800 Mbits/sec are measured turning off TSO:

ubuntu@test4g:~$ iperf -c 10.0.0.1

Client connecting to 10.0.0.1, TCP port 5001
TCP window size: 85.0 KByte (default)

[  3] local 10.0.0.17 port 50855 connected with 10.0.0.1 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-11.9 sec  1.00 MBytes   704 Kbits/sec

ubuntu@test4g:~$ sudo ethtool -K eth0 tso off

ubuntu@test4g:~$ iperf -c 10.0.0.1

Client connecting to 10.0.0.1, TCP port 5001
TCP window size: 85.0 KByte (default)

[  3] local 10.0.0.17 port 50856 connected with 10.0.0.1 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-10.0 sec   938 MBytes   786 Mbits/sec



 I believe in OpenStack the nic is a tap interface that kvm attaches your
 instance to and hence you have offloaded the task of segmenting to the host
 cpu now ( I am only guessing, not sure).


Yes. KVM is using tap interfaces with virtio driver.

I would like to know if this is the case and using a better flavor and
 image would offer you better results without tinkering with the interface.


Images used are Ubuntu Trusty downloaded from
http://images.ubuntu.com/trusty/current and a Debian Wheezy tested
previously in another private cloud. No significant differences were found
using Ubuntu or Debian images.

Thanks Akilesh!

Alberto
___
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] Very low bandwidth between instances and routers with OVS, GRE on Debian Jessie (Icehouse)

[Alberto Molina Coballes]

Hi,

I'm continuing with testing ...

It seems this issue is related to virtio driver. Virtio driver is used by
default with the option use_virtio_for_bridges=true in nova-compute.conf,
if this option is disabled instances are created with a RTL-8139 network
interface and the bandwidth between it and its router appears to be as
expected without disabling TSO:

iperf -c 10.0.0.1

Client connecting to 10.0.0.1, TCP port 5001
TCP window size: 23.5 KByte (default)

[  3] local 10.0.0.19 port 51554 connected with 10.0.0.1 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-10.0 sec   145 MBytes   121 Mbits/sec

On the other hand, bandwidth between instances running on the same compute
node is ~ 3 Gbits/sec with virtio driver.

More info:
- OVS: 2.3.0
- Linux kernel 3.16-3
- In-tree version of kernel openvswitch module

Cheers

Alberto
___
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] Very low bandwidth between instances and routers with OVS, GRE on Debian Jessie (Icehouse)

[Alberto Molina Coballes]

Hi,

Debian testing (jessie) is now frozen, so it seems a good time to use it as
a base for an OpenStack deployment. Debian jessie provides OpenStack
Icehouse packages from official repos, backported repos are no longer
needed.

Installation procedure works fine in a setup with OVS and GRE tunnels, but
a very low bandwidth is found between instances and routers. I know this is
a frequently asked topic, but after reading some related threads and bugs,
different causes and solutions where shown.

In order to find the problem, several test with iperf has been made and
proposed solutions applied:

1. Bandwidth between two instances running on the same compute node: 2.77
Gbits/sec
2. Bandwidht between compute node and network node (Gigabith Ethernet
used): 941 Mbits/sec
3. Bandwidth between an instance and a router running on network node: 200
Kbits/sec !!!
4. After applying proposed solution setting instance MTU to 1454, identical
result was obtained.
5. After applying proposed solution setting GRO off to physical interfaces
(network and compute nodes), identical result was obtained.

A solution was found here: https://bugs.launchpad.net/fuel/+bug/1256289

6. After setting tcp segmentation offload off in internal router interface:

ip netns exec qrouter-XX ethtool -K qr-14460da5-08 tso off

Bandwidth increased to 27 Mbits/sec

7. After setting  tcp segmentation offload off in the instance interface, a
very good performance is achieved: 776 Mbits/sec.

Solution found :), but the question is: What's the best way to implement
it? It isn't a practical solution to modify instance Ethernet configuration
after an instance is launched.

Any tip on this?

Thanks!

Alberto
___
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] keypair workaround

[Alberto Molina Coballes]

El 21/06/2014 20:17, Frans Thamura fr...@meruvian.org escribió:


 i want to make more common ssh without have to add -i keypair2.pem

 any idea?


What about using ssh-agent?

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