Saturday, 2017-11-25

« Friday, 2017-11-24 Index Sunday, 2017-11-26 »
openstackgerritTin Lam proposed openstack/openstack-helm-infra master: WIP: Fix centos package  https://review.openstack.org/52290801:18
openstackgerritTin Lam proposed openstack/openstack-helm master: Fix dumps_log playbook  https://review.openstack.org/52289701:24
openstackgerritTin Lam proposed openstack/openstack-helm master: Fix dumps_log playbook  https://review.openstack.org/52289701:25
*** XueFeng has quit IRC01:48
*** XueFeng has joined #openstack-helm01:48
SamYapleother than templating, what else does OSH use from Helm, feature wise?01:59
osh-chatbot<v1k0d3n> What do you mean SamYaple?02:00
SamYaple@v1k0d3n if its just templating, then most anything can template and then submit to k8s. So im just trying to get a grasp on the things that OSH takes advantage of from Helm, outside of templating02:29
*** yamamoto has joined #openstack-helm02:31
*** yamamoto has quit IRC02:54
*** yamamoto has joined #openstack-helm03:05
*** yamamoto has quit IRC03:23
*** openstackgerrit has quit IRC03:26
*** yamamoto has joined #openstack-helm04:23
*** yamamoto has quit IRC04:31
*** yamamoto has joined #openstack-helm05:14
*** yamamoto has quit IRC05:30
*** yamamoto has joined #openstack-helm05:34
*** yamamoto has quit IRC06:22
*** yamamoto has joined #openstack-helm06:56
*** yamamoto has quit IRC07:07
*** Neptu has quit IRC07:53
*** yamamoto has joined #openstack-helm07:54
*** yamamoto has quit IRC07:56
*** yamamoto has joined #openstack-helm07:59
*** yamamoto has quit IRC08:56
*** Neptu has joined #openstack-helm09:19
*** yamamoto has joined #openstack-helm09:56
*** yamamoto has quit IRC10:04
*** yamamoto has joined #openstack-helm10:44
*** yamamoto has quit IRC10:56
*** MarkBaker has quit IRC11:01
*** yamamoto has joined #openstack-helm11:08
*** yamamoto has quit IRC11:12
*** yamamoto has joined #openstack-helm12:13
*** yamamoto has quit IRC12:19
*** yamamoto has joined #openstack-helm12:21
*** yamamoto has quit IRC13:43
*** yamamoto has joined #openstack-helm13:45
*** yamamoto has quit IRC13:49
*** yamamoto has joined #openstack-helm14:00
*** yamamoto has quit IRC14:05
*** yamamoto has joined #openstack-helm14:15
*** yamamoto has quit IRC14:20
*** yamamoto has joined #openstack-helm14:30
*** yamamoto has quit IRC14:35
osh-chatbot<v1k0d3n> SamYaple, I think it’s just as much about the lifecycle too. For instance, helms specific ability to roll back releases. Another that I always talk about at Charter is the ability to test using rally, without the need for some other tool or procedure other than using helms testing hooks. And I a lot rides on common chart functionality as well (helm-toolkit) which helm uses to string together common functions across charts.14:42
osh-chatbot<v1k0d3n> OSH’s roots really came from Stackanetes...another templated OS/k8s project that used jsonette rather than gotpl. So to your point, yes, really any template tool could probably get the job done with some work. It’s just that Helm seemed to have the most community support and was well on its way to being the most accepted solution for k8s, being brought up from incubation to k8s close to the time we pitched it in Barcelona.14:47
osh-chatbot<v1k0d3n> There are some big names in the community that really against gotpl in favor of jsonette, like Joe Beda (from Heptio). He’s started a project to revive kpm’s template packaging format, borrowed from stackanetes, in his project ksonnet. But from what I’ve heard second hand, is that they’re basically running into and solving the same issues that Helm solved a while back, just now with a different template format. So where jsone14:56
osh-chatbotbe easier in some ways to gotpl, they’re having to recreate the wheel in other ways.14:56
*** openstackgerrit has joined #openstack-helm14:58
openstackgerritTin Lam proposed openstack/openstack-helm master: Add fedora support  https://review.openstack.org/52289614:58
osh-chatbot<v1k0d3n> Sorry, misspelled “jsonette”... :,) ...it’s jsonnet.14:59
*** yamamoto has joined #openstack-helm15:15
*** yamamoto has quit IRC15:19
*** yamamoto has joined #openstack-helm15:30
*** yamamoto has quit IRC15:34
*** yamamoto has joined #openstack-helm16:00
*** yamamoto has quit IRC16:05
osh-chatbot<joestack> I followed the instructions from the all-in-one doc.  The OpenStack infrastructure components are installed and running. Keystone and Glance worked also fine, but nova won't start.16:11
osh-chatbot<joestack> kubectl get pods --namespace openstack  NAME                                   READY     STATUS             RESTARTS   AGE etcd-2376361164-cvkqn                  1/1       Running            0          46m glance-api-1382642568-kgb7v            1/1       Running            0          23m glance-registry-884069287-flgqr        1/1       Running            0          23m ingress-api-h41z5                      1/1       Running16:12
osh-chatbot   0          29m ingress-error-pages-3130237402-k71zj   1/1       Running            0          29m keystone-api-3194647745-qtwr3          1/1       Running            0          25m libvirt-4l7tf                          1/1       Running            0          27m mariadb-0                              1/1       Running            0          51m mariadb-1                              1/1       Running            0          50m mariadb-216:12
osh-chatbot                        1/1       Running            0          48m memcached-3845003049-bznpt             1/1       Running            0          47m neutron-dhcp-agent-5vxbp               0/1       Init:0/1           0          13m neutron-l3-agent-lp496                 0/1       Init:0/1           0          13m neutron-metadata-agent-3rxh9           0/1       Init:0/2           0          13m neutron-ovs-agent-plr4k                1/116:12
osh-chatbot Running            0          13m neutron-server-1893937472-lb4ff        1/1       Running            0          13m nova-api-metadata-3646760142-rr7cl     0/1       CrashLoopBackOff   7          20m nova-api-osapi-2194652958-z4crl        0/1       CrashLoopBackOff   7          20m nova-bootstrap-hzmd1                   0/1       Init:0/1           0          20m nova-cell-setup-1htts                  0/1       CrashLoopBackOff   616:12
osh-chatbot20m nova-compute-1j211                     0/2       Init:0/3           0          20m nova-conductor-2450396177-qnhst        0/1       CrashLoopBackOff   6          20m nova-consoleauth-4019571531-psc8l      0/1       CrashLoopBackOff   6          20m nova-novncproxy-2432560747-d2dbq       1/1       Running            0          20m nova-placement-api-2658371748-zwfbx    1/1       Running            0          20m16:12
osh-chatbotnova-scheduler-4076657089-drlw0        0/1       Init:0/1           0          20m openvswitch-db-bd9l6                   1/1       Running            0          28m openvswitch-vswitchd-3d1zr             1/1       Running            0          28m rabbitmq-3822530852-9988d              0/1       Running            0          45m rabbitmq-3822530852-9k15x              1/1       Running            0          45m rabbitmq-3822530852-t0gh416:12
osh-chatbot      1/1       Running            0          45m16:12
osh-chatbot<joestack> and some logs from nova-api-metadata:16:13
osh-chatbot<joestack> kubectl log po/nova-api-metadata-3646760142-rr7cl --namespace openstack W1125 17:04:48.197451   28092 cmd.go:392] log is DEPRECATED and will be removed in a future version. Use logs instead. + COMMAND=start + start + exec nova-api-metadata --config-file /etc/nova/nova.conf --config-file /tmp/pod-shared/nova-api-metadata.ini 2017-11-25 15:55:41.541 151 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers16:13
osh-chatbotSIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports. 2017-11-25 15:55:41.543 151 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net' 2017-11-25 15:55:43.784 151 INFO nova.wsgi [-] metadata listening on 0.0.0.0:8775 2017-11-25 15:55:43.805 151 CRITICAL nova [-] ConfigFileValueError: Value for option hw_disk_discard16:13
osh-chatbotis not valid: Valid values are [ignore, unmap], but found '' 2017-11-25 15:55:43.805 151 ERROR nova Traceback (most recent call last): 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/bin/nova-api-metadata", line 10, in <module> 2017-11-25 15:55:43.805 151 ERROR nova     sys.exit(main()) 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/cmd/api_metadata.py", line 52, in16:13
osh-chatbotmain 2017-11-25 15:55:43.805 151 ERROR nova     service.wait() 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/service.py", line 415, in wait 2017-11-25 15:55:43.805 151 ERROR nova     _launcher.wait() 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_service/service.py", line 328, in wait 2017-11-25 15:55:43.805 151 ERROR nova16:13
osh-chatbotstatus, signo = self._wait_for_exit_or_signal() 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_service/service.py", line 303, in _wait_for_exit_or_signal 2017-11-25 15:55:43.805 151 ERROR nova     self.conf.log_opt_values(LOG, logging.DEBUG) 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_config/cfg.py", line 2626, in16:13
osh-chatbotlog_opt_values 2017-11-25 15:55:43.805 151 ERROR nova     _sanitize(opt, getattr(group_attr, opt_name))) 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_config/cfg.py", line 3057, in __getattr__ 2017-11-25 15:55:43.805 151 ERROR nova     return self._conf._get(name, self._group) 2017-11-25 15:55:43.805 151 ERROR nova   File16:13
osh-chatbot"/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_config/cfg.py", line 2668, in _get 2017-11-25 15:55:43.805 151 ERROR nova     value = self._do_get(name, group, namespace) 2017-11-25 15:55:43.805 151 ERROR nova   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_config/cfg.py", line 2711, in _do_get 2017-11-25 15:55:43.805 151 ERROR nova     % (opt.name, str(ve))) 2017-11-25 15:55:43.805 151 ERROR nova16:13
osh-chatbotConfigFileValueError: Value for option hw_disk_discard is not valid: Valid values are [ignore, unmap], but found '' 2017-11-25 15:55:43.805 151 ERROR nova16:13
osh-chatbot<joestack> can someone give me some guidance please....16:14
*** yamamoto has joined #openstack-helm17:00
*** yamamoto has quit IRC17:05
*** yamamoto has joined #openstack-helm17:14
andrey-mposh-chatbot: you can check my changes to resolve this error: https://review.openstack.org/#/c/517438/4/tools/overrides/mvp/nova.yaml18:00
andrey-mposh-chatbot: with this chageset you can deploy all components, but VM can not be booted with error in nova-conductor18:01
*** yamamoto has joined #openstack-helm18:15
*** yamamoto has quit IRC18:24
*** Neptu has quit IRC18:49
SamYaplev1k0d3n: thanks thats good info.20:59
« Friday, 2017-11-24 Index Sunday, 2017-11-26 »

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!