Open Stack

Hi Steven,


Thanks for the information. Some further questions:

> Reconfigure was not designed to handle changes to globals.yml.  I think 
its a good goal that it should be able to do so, but it does not today.

So waht is the prefered method to change kolla_internal_vip_address and 
make it effective?

> Reconfigure was designed to handle changes to /etc/kolla/config/* (where 
custom config for services live).  Reconfigure in its current incarnation 
in all our branches and master is really a misnomer ¨C it should be 
service-reconfgiure ¨C but that is wordy and we plan to make globals.yml 
reconfigurable if feasible ¨C but probably not anytime soon.

There is no /etc/kolla/config/* located in my env before or after 
successful deployment. Is that right? 





·¢¼þÈË:         "Steven Dake (stdake)" <stdake at cisco.com>
ÊÕ¼þÈË:         "openstack-dev at lists.openstack.org" 
<openstack-dev at lists.openstack.org>, 
ÈÕÆÚ:   2016-06-03 06:16
Ö÷Ìâ:   [probably forge email¿ÉÄÜÊÇ·ÂðÓʼþ]Re: [openstack-dev] [Kolla] 
About kolla-ansible reconfigure



Hu,

Reconfigure was not designed to handle changes to globals.yml.  I think 
its a good goal that it should be able to do so, but it does not today.

Reconfigure was designed to handle changes to /etc/kolla/config/* (where 
custom config for services live).  Reconfigure in its current incarnation 
in all our branches and master is really a misnomer ¨C it should be 
service-reconfgiure ¨C but that is wordy and we plan to make globals.yml 
reconfigurable if feasible ¨C but probably not anytime soon.

Regards
-steve


From: "hu.zhijiang at zte.com.cn" <hu.zhijiang at zte.com.cn>
Reply-To: "openstack-dev at lists.openstack.org" <
openstack-dev at lists.openstack.org>
Date: Wednesday, June 1, 2016 at 6:24 PM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org
>
Subject: [openstack-dev] [Kolla] About kolla-ansible reconfigure

Hi 

After modifying the kolla_internal_vip_address in /etc/kolla/global.yml , 
I use kolla-ansible reconfigure to reconfigure OpenStack. But I got the 
following error.

TASK: [mariadb | Restart containers] 
******************************************
skipping: [localhost] => (item=[{'group': 'mariadb', 'name': 'mariadb'}, 
{'KOLLA_BASE_DISTRO': 'centos', 'PS1': '$(tput bold)($(printenv 
KOLLA_SERVICE_NAME))$(tput sgr0)[$(id -un)@$(hostname -s) $(pwd)]$ ', 
'KOLLA_INSTALL_TYPE': 'binary', 'changed': False, 'item': {'group': 
'mariadb', 'name': 'mariadb'}, 'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS', 
'PATH': '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', 
'invocation': {'module_name': u'kolla_docker', 'module_complex_args': 
{'action': 'get_container_env', 'name': u'mariadb'}, 'module_args': ''}, 
'KOLLA_SERVICE_NAME': 'mariadb', 'KOLLA_INSTALL_METATYPE': 'rdo'}, {'cmd': 
['docker', 'exec', 'mariadb', '/usr/local/bin/kolla_set_configs', 
'--check'], 'end': '2016-06-02 11:32:18.866276', 'stderr': 
'INFO:__main__:Loading config file at 
/var/lib/kolla/config_files/config.json\nINFO:__main__:Validating config 
file\nINFO:__main__:The config files are in the expected state', 'stdout': 
u'', 'item': {'group': 'mariadb', 'name': 'mariadb'}, 'changed': False, 
'rc': 0, 'failed': False, 'warnings': [], 'delta': '0:00:00.075316', 
'invocation': {'module_name': u'command', 'module_complex_args': {}, 
'module_args': u'docker exec mariadb /usr/local/bin/kolla_set_configs 
--check'}, 'stdout_lines': [], 'failed_when_result': False, 'start': 
'2016-06-02 11:32:18.790960'}]) 

TASK: [mariadb | Waiting for MariaDB service to be ready through VIP] 
*********
failed: [localhost] => {"attempts": 6, "changed": false, "cmd": ["docker", 
"exec", "mariadb", "mysql", "-h", "10.43.114.148/24", "-u", "haproxy", 
"-e", "show databases;"], "delta": "0:00:03.924516", "end": "2016-06-02 
11:33:57.928139", "failed": true, "rc": 1, "start": "2016-06-02 
11:33:54.003623", "stdout_lines": [], "warnings": []}
stderr: ERROR 2005 (HY000): Unknown MySQL server host '10.43.114.148/24' 
(-2)
msg: Task failed as maximum retries was encountered

FATAL: all hosts have already failed -- aborting


It seems that mariadb was not restart as expected.


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail 
(and any attachment transmitted herewith) is privileged and confidential 
and is intended for the exclusive use of the addressee(s).  If you are not 
an intended recipient, any disclosure, reproduction, distribution or other 
dissemination or use of the information contained is strictly prohibited. 
If you have received this mail in error, please delete it and notify us 
immediately.


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160604/ea01be16/attachment-0001.html>