[Openstack-operators] [kolla] Berlin summit resume

[Eduardo Gonzalez]

Hi kollagues,

During the Berlin Summit kolla team had a few talks and forum discussions,
as well as other cross-project related topics [0]

First session was ``Kolla project onboarding``, the room was full of people
interested in contribute to kolla, many of them already using kolla in
production environments whiling to make upstream some work they've done
downstream. I can say this talk was a total success and we hope to see many
new faces during this release putting features and bug fixes into kolla.
Slides of the session at [1]

Second session was ``Kolla project update``, was a brief resume of what
work has been done during rocky release and some items will be implemented
in the future. Number of attendees to this session was massive, no more
people could enter the room. Slides at [2]


Then forum sessions..

First one was ``Kolla user feedback``, many users came over the room. We've
notice a big increase in production deployments and some PoC migrating to
production soon, many of those environments are huge.
Overall the impressions was that kolla is great and don't have any big
issue or requirement, ``it works great`` became a common phrase to listen.
Here's a resume of the user feedback needs [3]

- Improve operational usage for add, remove, change and stop/start nodes
and services.
- Database backup and recovery
- Lack of documentation is the bigger request, users need to read the code
to know how to configure other than core/default services
- Multi cells_v2
- New services request, cyborg, masakari and tricircle were the most
requested
- SElinux enabled
- More SDN services such as Contrail and calico
- Possibility to include user's ansible tasks during deploy as well as
support custom config.json
- HTTPS for internal networks

Second one was about ``kolla for the edge``, we've meet with Edge computing
group and others interested in edge deployments to identify what's missing
in kolla and where we can help.
Things we've identified are:

- Kolla seems good at how the service split can be done, tweaking inventory
file and config values can deploy independent environments easily.
- Missing keystone federation
- Glance cache support is not a hard requirement but improves efficiency
(already merged)
- Multi cells v2
- Multi storage per edge/far-edge
- A documentation or architecture reference would be nice to have.

Last one was ``kolla for NFV``, few people came over to discuss about NUMA,
GPU, SRIOV.
Nothing noticiable from this session, mainly was support DPDK for
CentOS/RHEL,OracleLinux and few service addition covered by previous
discussions.

[0] https://etherpad.openstack.org/p/kolla-stein-summit
[1]
https://es.slideshare.net/EduardoGonzalezGutie/kolla-project-onboarding-openstack-summit-berlin-2018
[2]
https://es.slideshare.net/EduardoGonzalezGutie/openstack-kolla-project-update-rocky-release
[3] https://etherpad.openstack.org/p/berlin-2018-kolla-user-feedback
[4] https://etherpad.openstack.org/p/berlin-2018-kolla-edge
[5] https://etherpad.openstack.org/p/berlin-2018-kolla-nfv
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Openstack zun on centos???

[Eduardo Gonzalez]

Difference between magnum and zun is that magnum creates COE and zun at
this moment runs directly in docker daemon without orchestration.

El mié., 14 nov. 2018 20:36, Eduardo Gonzalez  escribió:

> Hello, zun will create the containers in the directly in the docker daemon
> associated as zun-compute node.
>
> About installation, you can install zun with pip and configure manually.
> It will work no matter if is ubuntu or centos, maybe the packages required
> doesn't match between distributions, is a matter of try what dependency it
> have.
>
> Regards
>
>
> El mié., 14 nov. 2018 20:29, Ignazio Cassano 
> escribió:
>
>> Hello again,
>> I read zun documents very fastly.
>> After zun installation (with or without kolla) , do containers run
>> directly in compute nodes or in virtual machines ?
>> Magnum can run them in both but Magnum seems very different.
>> Ignazio
>>
>>
>> Il giorno Mer 14 Nov 2018 20:00 Fox, Kevin M  ha
>> scritto:
>>
>>> kolla installs it via containers.
>>>
>>> Thanks,
>>> Kevin
>>> --
>>> *From:* Ignazio Cassano [ignaziocass...@gmail.com]
>>> *Sent:* Wednesday, November 14, 2018 10:48 AM
>>> *To:* Eduardo Gonzalez
>>> *Cc:* OpenStack Operators
>>> *Subject:* Re: [Openstack-operators] Openstack zun on centos???
>>>
>>> Hi Edoardo,
>>> does it mean openstack kolla installs zun using pip ?
>>> I did not find any zun rpm package
>>> Regards
>>> Ignazio
>>>
>>> Il giorno Mer 14 Nov 2018 18:38 Eduardo Gonzalez 
>>> ha scritto:
>>>
>>>> Hi Cassano, you can use zun in centos deployed by kolla-ansible.
>>>>
>>>> https://docs.openstack.org/kolla-ansible/latest/reference/zun-guide.html
>>>>
>>>> Regards
>>>>
>>>> El mié., 14 nov. 2018 17:11, Ignazio Cassano 
>>>> escribió:
>>>>
>>>>> Hi All,
>>>>> I'd like to know if openstack zun will be released for centos.
>>>>> Reading documentation at docs.openstack.org only ubuntu installation
>>>>> is reported.
>>>>> Many thanks
>>>>> 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] Openstack zun on centos???

[Eduardo Gonzalez]

Hello, zun will create the containers in the directly in the docker daemon
associated as zun-compute node.

About installation, you can install zun with pip and configure manually. It
will work no matter if is ubuntu or centos, maybe the packages required
doesn't match between distributions, is a matter of try what dependency it
have.

Regards

El mié., 14 nov. 2018 20:29, Ignazio Cassano 
escribió:

> Hello again,
> I read zun documents very fastly.
> After zun installation (with or without kolla) , do containers run
> directly in compute nodes or in virtual machines ?
> Magnum can run them in both but Magnum seems very different.
> Ignazio
>
>
> Il giorno Mer 14 Nov 2018 20:00 Fox, Kevin M  ha
> scritto:
>
>> kolla installs it via containers.
>>
>> Thanks,
>> Kevin
>> --
>> *From:* Ignazio Cassano [ignaziocass...@gmail.com]
>> *Sent:* Wednesday, November 14, 2018 10:48 AM
>> *To:* Eduardo Gonzalez
>> *Cc:* OpenStack Operators
>> *Subject:* Re: [Openstack-operators] Openstack zun on centos???
>>
>> Hi Edoardo,
>> does it mean openstack kolla installs zun using pip ?
>> I did not find any zun rpm package
>> Regards
>> Ignazio
>>
>> Il giorno Mer 14 Nov 2018 18:38 Eduardo Gonzalez  ha
>> scritto:
>>
>>> Hi Cassano, you can use zun in centos deployed by kolla-ansible.
>>>
>>> https://docs.openstack.org/kolla-ansible/latest/reference/zun-guide.html
>>>
>>> Regards
>>>
>>> El mié., 14 nov. 2018 17:11, Ignazio Cassano 
>>> escribió:
>>>
>>>> Hi All,
>>>> I'd like to know if openstack zun will be released for centos.
>>>> Reading documentation at docs.openstack.org only ubuntu installation
>>>> is reported.
>>>> Many thanks
>>>> 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] Openstack zun on centos???

[Eduardo Gonzalez]

yes, only source code (pip) is supported, there is not any rpm available
for it yet.

Regards

El mié., 14 nov. 2018 19:48, Ignazio Cassano 
escribió:

> Hi Edoardo,
> does it mean openstack kolla installs zun using pip ?
> I did not find any zun rpm package
> Regards
> Ignazio
>
> Il giorno Mer 14 Nov 2018 18:38 Eduardo Gonzalez  ha
> scritto:
>
>> Hi Cassano, you can use zun in centos deployed by kolla-ansible.
>>
>> https://docs.openstack.org/kolla-ansible/latest/reference/zun-guide.html
>>
>> Regards
>>
>> El mié., 14 nov. 2018 17:11, Ignazio Cassano 
>> escribió:
>>
>>> Hi All,
>>> I'd like to know if openstack zun will be released for centos.
>>> Reading documentation at docs.openstack.org only ubuntu installation is
>>> reported.
>>> Many thanks
>>> 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] Openstack zun on centos???

[Eduardo Gonzalez]

Hi Cassano, you can use zun in centos deployed by kolla-ansible.

https://docs.openstack.org/kolla-ansible/latest/reference/zun-guide.html

Regards

El mié., 14 nov. 2018 17:11, Ignazio Cassano 
escribió:

> Hi All,
> I'd like to know if openstack zun will be released for centos.
> Reading documentation at docs.openstack.org only ubuntu installation is
> reported.
> Many thanks
> 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

[Openstack-operators] [kolla][ptg] Denver PTG on-site or virtual

[Eduardo Gonzalez]

Fellow kolleages.

In september is Denver PTG, as per the etherpad [0] only 3 contributors
confirmed their presence in the PTG, we expected more people to be there as
previous PTGs were full of contributors and operators.

In the last kolla meeting [1] with discussed if we should make a virtual
PTG rather than a on-site one as we will probably reach a bigger number of
attendance.

This set us in a bad possition as per:

If we do an on-site PTG

- Small representation for a whole cycle design, being this one larger than
usual.
- Many people whiling to attend is not able to be there.

If we do a virtual PTG

- Some people already spend money to travel for kolla PTG
- PTG rooms are already reserved for kolla session
- No cross project discussion

If there are more people who is going to Denver and haven't signed up at
the etherpad, please confirm your presence as it will probably influence on
this topic.

Here is the though question...

What kind of PTG do you prefer for this one, virtual or on-site in Denver?

CC to Kendall Nelson from the foundation if she could help us on this
though decission, given the small time we have until the PTG both ways have
some kind of bad consecuencies for both the project and the contributors.

[0] https://etherpad.openstack.org/p/kolla-stein-ptg-planning
[1]
http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-08-15-15.00.log.html#l-13

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

Re: [Openstack-operators] [kolla][nova] Upgrade leaves nova_compute at earlier version

[Eduardo Gonzalez]

Hi,

could you share a your globals file without secrets, a docker ps -a on all
compute hosts and images too. If you are able to get n upgrade log will be
helpful too.

By the way, using master is not really recommended, many changes from other
projects and kolla may break the deployment.

Regards

On Thu, Jun 14, 2018, 9:00 PM Dave Williams 
wrote:

> I am using kolla-ansible 6.0.0 with openstack_release set to master in
> globals.yml in a production environment.
>
> I am trying to fix an oslo_messaging.rpc.client.RemoteError when
> undertaking server add volume
> (https://bugs.launchpad.net/nova/+bug/1773393) and appear to have
> tracked it down to an inconsistency of container versions.
>
> kollo-ansible upgrade runs to completion without error but leaves the
> running nova_compute containers (and possibly others) at an earlier
> version.
>
> The version running is
> CONTAINER ID IMAGECOMMAND   CREATED STATUS PORTS NAMES
> 944f620a445c 7dc2d4695962 "kolla_start" 4 weeks ago Up 4 hours nova_compute
>
> whereas docker images -a shows
> REPOSITORY TAG IMAGE ID CREATED SIZE
> kolla/ubuntu-source-nova-compute master f2df8187f14e 15 hours ago 1.29GB
> kolla/ubuntu-source-nova-compute  582561ac010f 39 hours ago 1.29GB
> kolla/ubuntu-source-nova-compute  7dc2d4695962 3 months ago 1.22GB
>
> This implies f2df8187f14e is the one I should be using.
> The image 582561ac010f was after I tried to switch to queens from master
> but without success due to a bootstrap_cinder problem:
> Error during database migration:
>   "Database schema file with version 122 doesn't exist."
> I tried to investigate this but without any obvious resolution.
>
> All compute nodes show the same issue.
>
> As per the notes on
> https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
> I have checked and virt_type is set to kvm in nova.conf and so I cannot
> see why the upgrade shouldnt have been successful.
>
> How do I get kolla to use the latest version pulled?
>
> Given I have running instances I am a little nervous of doing a deploy or
> reconfigure.
>
> Thanks for help.
>
> Dave
>
>
> ___
> 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] [keystone] Field 'domain_id' doesn't have a default value

[Eduardo Gonzalez]

Hi.
I’m testing upgrades from Newton to master branch using keystone’s
zero-downtime upgrade method:

keystone-manage db_sync --expand
keystone-manage db_sync --migrate
keystone-manage db_sync --contract

After upgrade is made with no errors in logs, I cannot create users. Other
keystone commands works fine.

Error message: “Field ‘domain_id’ doesn’t have a default value”

Full trace:

2017-01-26 15:32:10.978 17 ERROR oslo_db.sqlalchemy.exc_filters
[req-576e5683-6631-49b9-b532-65f06a23bbeb
4b3ff53812734e72b5aea42103349571 04fe68cf58724855a2ee67781a14b446 -
default default] DBAPIError exception wrapped from
(pymysql.err.InternalError) (1364, u"Field 'domain_id' doesn't have a
default value") [SQL: u'INSERT INTO user (id, enabled, extra,
default_project_id, created_at, last_active_at) VALUES (%(id)s,
%(enabled)s, %(extra)s, %(default_project_id)s, %(created_at)s,
%(last_active_at)s)'] [parameters: {'last_active_at': None, 'extra':
'{}', 'created_at': datetime.datetime(2017, 1, 26, 15, 32, 10,
974903), 'enabled': 1, 'default_project_id': None, 'id':
'8989be945c954f14a1c9ebaf45988fad'}]2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters Traceback (most recent call
last):2017-01-26 15:32:10.978 17 ERROR oslo_db.sqlalchemy.exc_filters
 File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1139, in _execute_context2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters context)2017-01-26 15:32:10.978 17
ERROR oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/sqlalchemy/engine/default.py",
line 450, in do_execute2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters cursor.execute(statement,
parameters)2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/cursors.py",
line 167, in execute2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters result =
self._query(query)2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/cursors.py",
line 323, in _query2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters conn.query(q)2017-01-26
15:32:10.978 17 ERROR oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/connections.py",
line 836, in query2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters self._affected_rows =
self._read_query_result(unbuffered=unbuffered)2017-01-26 15:32:10.978
17 ERROR oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/connections.py",
line 1020, in _read_query_result2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters result.read()2017-01-26
15:32:10.978 17 ERROR oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/connections.py",
line 1303, in read2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters first_packet =
self.connection._read_packet()2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/connections.py",
line 982, in _read_packet2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters packet.check_error()2017-01-26
15:32:10.978 17 ERROR oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/connections.py",
line 394, in check_error2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters
err.raise_mysql_exception(self._data)2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/err.py", line
120, in raise_mysql_exception2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters
_check_mysql_exception(errinfo)2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters   File
"/var/lib/kolla/venv/lib/python2.7/site-packages/pymysql/err.py", line
115, in _check_mysql_exception2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters raise InternalError(errno,
errorvalue)2017-01-26 15:32:10.978 17 ERROR
oslo_db.sqlalchemy.exc_filters InternalError: (1364, u"Field
'domain_id' doesn't have a default value")2017-01-26 15:32:10.978 17
ERROR oslo_db.sqlalchemy.exc_filters

Database migration logs:

2017-01-26 15:27:11.425 18 INFO migrate.versioning.api [-] 4 -> 5...
2017-01-26 15:27:11.540 18 INFO migrate.versioning.api [-]
done2017-01-26 15:27:11.540 18 INFO migrate.versioning.api [-] 5 ->
6... 2017-01-26 15:27:11.643 18 INFO migrate.versioning.api [-]
done2017-01-26 15:27:11.645 18 INFO migrate.versioning.api [-] 6 ->
7... 2017-01-26 15:27:11.758 18 INFO migrate.versioning.api [-]
done2017-01-26 15:27:11.759 18 INFO migrate.versioning.api [-] 7 ->
8... 2017-01-26 15:27:11.872 18 INFO migrate.versioning.api [-]
done2017-01-26 15:27:11.879 18 INFO migrate.versioning.api [-] 8 ->
9... 2017-01-26 15:27:12.082 18 INFO migrate.ver

Re: [Openstack-operators] European Operators

[Eduardo Gonzalez]

I think is a good idea, very interested too

Regards

On Thu, Sep 17, 2015, 10:15 AM Olivier Cant  wrote:

> Also very intrested.
>
> Olivier
>
>
> On 17/09/15S38 10:02, Salman Toor wrote:
>
> Hi,
>
> Why Not!
>
> I think its a great Idea. I want to join.
>
> Regards..
> Salman
>
>
> PhD, Scientific Computing
> Researcher, IT Department,
> Uppsala University.
> Cloud Application Expert,
> UPPMAX.
> Visiting Researcher,
> Helsinki Institute of Physics (HIP).
> salman.t...@it.uu.se
> http://www.it.uu.se/katalog/salto690
>
> On 17 Sep 2015, at 09:52, Matt Jarvis 
> wrote:
>
> Hi All
>
> Don't know how many European folks are on this list, but just wondering if
> there's any interest in a European Operators meet up ?
>
> Matt
>
> --
> Matt Jarvis
> Head of Cloud Computing
> DataCentred
> Office: (+44)0161 8703985
> Mobile: (+44)07983 725372
> Email: matt.jar...@datacentred.co.uk
> Website: http://www.datacentred.co.uk
>
> DataCentred Limited registered in England and Wales no. 05611763
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
>
> ___
> OpenStack-operators mailing 
> listOpenStack-operators@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> --
>
>
> [image: Exxoss] 
> *Olivier Cant*, CEO | Gsm: +32(0)497/64.18.22
> *Exxoss, SPRL *
> Rue de la station, 2, 4347, Fexhe-le-haut-clocher | Telephone:
> +32(0)4/341.25.81 | Fax: +32(0)4/371.94.06
> [image: Twitter]  [image: Facebook]
>  [image: Linked In]
> 
>
>
> ___
> 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